From owner-freebsd-current Sun Mar 10 00:04:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA01464 for current-outgoing; Sun, 10 Mar 1996 00:04:50 -0800 (PST) Received: from sxt2.space.lockheed.com (sxt2.space.lockheed.com [192.68.162.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA01459 for ; Sun, 10 Mar 1996 00:04:48 -0800 (PST) Received: by sxt2.space.lockheed.com (5.65/DEC-Ultrix/4.3) id AA22654; Sat, 9 Mar 1996 23:59:08 -0800 Date: Sat, 9 Mar 1996 23:59:08 -0800 (PST) From: "Brian N. Handy" To: Andrew Foster Cc: current@FreeBSD.ORG Subject: Re: top and 2.2-960303SNAP In-Reply-To: <2.2.32.19960311025700.00ebacb8@mail.fl.net.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Just incase this hasn't be brought up before (just subscribed to this list), > top gives 'interesting' results on this SNAP. Also "swapinfo" gives interesting results on my machine. I want to think that "used" and "available" have swapped along the way somewhere. (Last SNAP, supped Sources 8-March, plus one patch on Thursday for the CD9660 stuff. handy % swapinfo Device 512-blocks Used Avail Capacity Type /dev/sd0s2b 131072 130944 0 100% Interleaved handy % uptime 11:59PM up 1 min, 3 users, load averages: 0.67, 0.16, 0.06 handy % uname -a FreeBSD handy.space.lockheed.com 2.2-CURRENT FreeBSD 2.2-CURRENT #1: Thu Mar 7 16:25:02 1996 root@handy.space.lockheed.com:/usr/2.2.0-CURRENT/src/sys/compile/LESPAUL i386 handy % Regards, Brian From owner-freebsd-current Sun Mar 10 00:05:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA01593 for current-outgoing; Sun, 10 Mar 1996 00:05:50 -0800 (PST) Received: from mx10.netvision.net.il (mx10.NetVision.net.il [194.90.1.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA01587 Sun, 10 Mar 1996 00:05:46 -0800 (PST) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mx10.netvision.net.il (8.7.3/8.7.1) with SMTP id LAA00152; Sun, 10 Mar 1996 11:05:59 +0200 Message-ID: X-Mailer: XFMail 0.4-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: <199603091824.KAA14373@freefall.freebsd.org> Date: Sun, 10 Mar 1996 10:07:09 +0200 (IST) Reply-To: gena@NetVision.net.il X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: "Justin T. Gibbs" Subject: RE: 3c5X9 working? Cc: current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 09-Mar-96 "Justin T. Gibbs" wrote: >>Are any of you having problems with 3c509 or 3c579 cards in current? Seems to be stable as a rock right now. I tested the card under all possible network conditions (except probably multicast and IPX) and everything works fine. >I'd like to bring in the driver changes to -stable. > >Thanks, >-- >Justin T. Gibbs >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> FreeBSD: Turning PCs into workstations >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 03/10/96 10:07:09 by XF-Mail From owner-freebsd-current Sun Mar 10 00:58:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA03802 for current-outgoing; Sun, 10 Mar 1996 00:58:22 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA03797 for ; Sun, 10 Mar 1996 00:58:20 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.4/8.6.9) id AAA00615; Sun, 10 Mar 1996 00:58:15 -0800 (PST) Date: Sun, 10 Mar 1996 00:58:15 -0800 (PST) Message-Id: <199603100858.AAA00615@silvia.HIP.Berkeley.EDU> To: current@freebsd.org Subject: -current kernel can't boot From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sup of about 1 hour ago. Adaptec 2940UW (ahc0), Quantum XP32150 (sd0), Micropolis 3243W (sd1). I got "timed out in dataout phase; SCSISIGI=0x0" and "timed out in message out phase, SCSISIGI=0xe6". After a while it says "channel A bus reset #1, 2 SCBs aborted" and then either freezes or reboots. Tried three times, with similar results (the first time it was after mounting; the second and third times were during fsck). It threw my disks into a serious funk too, as I needed three tries to boot from an old kernel after this. (Yes, I powered down the machine each time.) Satoshi From owner-freebsd-current Sun Mar 10 01:14:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA05577 for current-outgoing; Sun, 10 Mar 1996 01:14:22 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA05570 for ; Sun, 10 Mar 1996 01:14:18 -0800 (PST) Received: by sequent.kiae.su id AA03195 (5.65.kiae-2 ); Sun, 10 Mar 1996 12:08:31 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 10 Mar 96 12:08:31 +0300 Received: (from ache@localhost) by astral.msk.su (8.7.4/8.7.3) id MAA00617; Sun, 10 Mar 1996 12:06:02 +0300 (MSK) Message-Id: <199603100906.MAA00617@astral.msk.su> Subject: Re: HEADS UP! Please check... To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Mar 1996 12:06:01 +0300 (MSK) Cc: mark@grondar.za, current@freebsd.org In-Reply-To: <199603091745.JAA12093@freefall.freebsd.org> from "Justin T. Gibbs" at "Mar 9, 96 09:45:50 am" From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL11 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Hi folks > > > >I have just committed a change to su(1) to better integrate Kerberos > >into it. BUT, this missive does not apply only to those of you with > >Kerberos/eBones. > > > >The result of this change is that a user will not be prompted for > >a password again if they get the Kerberos password wrong. > > What happens if your network is down to your kerberos server and your > user.root instance has a different password than your local root account? > How do you know which password to give? > I fear in this situation you even can't enter su in your client machine. It is especially bad on slip machine, because you need to enter su password first time to dial to provider to become kerberos client next. If it is so, please back out this change. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : 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 10 01:17:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06005 for current-outgoing; Sun, 10 Mar 1996 01:17:35 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA05986 for ; Sun, 10 Mar 1996 01:17:20 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA20728 for current@freebsd.org; Sun, 10 Mar 1996 20:15:55 +1100 Date: Sun, 10 Mar 1996 20:15:55 +1100 From: Bruce Evans Message-Id: <199603100915.UAA20728@godzilla.zeta.org.au> To: current@freebsd.org Subject: booting from sd5 when wd3 is also installed Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk These changes should allow specifying the BIOS drive number independently of the FreeBSD unit number. E.g., `9:sd(5,a)' describes the drive with BIOS drive number 9 and sd unit number 5. hd(N,a) is no longer supported because it doesn't fit and it only works for unit number 0. Use N:sd(0,a) instead. I haven't decided exactly how to handle these points: - how sticky should the drive number be? What is the default drive number after 1:sd(0,a)/nonesuch followed by /kernel? - option BOOT_HD_BIAS. This replaces option BOOT_HD. The BIOS drive number for unit N is currently BOOT_HD_BIAS + N. Should the bias only be added for sd drives? How does biasing interact with previously specified drive numbers? Please test the changes on systems with mixed IDE and SCSI drives. I don't have any. Bruce diff -c2 src/sys/i386/boot/biosboot/Makefile~ src/sys/i386/boot/biosboot/Makefile *** src/sys/i386/boot/biosboot/Makefile~ Sat Mar 9 04:42:23 1996 --- src/sys/i386/boot/biosboot/Makefile Sun Mar 10 17:26:35 1996 *************** *** 21,28 **** #CFLAGS+= -DFORCE_COMCONSOLE ! # Assume hd(*,a) instead of wd(*,a) if the boot seems to happen from ! # a hard disk. ! # This can be useful for people booting in a mixed IDE/SCSI environment. ! #CFLAGS+= -DBOOT_HD CLEANFILES+= boot.nohdr boot.strip boot1 boot2 sizetest --- 22,31 ---- #CFLAGS+= -DFORCE_COMCONSOLE ! # Bias the conversion from the BIOS drive number to the FreeBSD unit number ! # for hard disks to save typing. E.g., BOOT_HD_BIAS=1 makes BIOS drive 1 ! # correspond to 1:sd(0,a) instead of 1:sd(1,a). ! # This may be useful for people booting in a mixed IDE/SCSI environment ! # (set BOOT_HD_BIAS to the number of IDE drives). ! #CFLAGS+= -DBOOT_HD_BIAS=1 CLEANFILES+= boot.nohdr boot.strip boot1 boot2 sizetest diff -c2 src/sys/i386/boot/biosboot/README.386BSD~ src/sys/i386/boot/biosboot/README.386BSD *** src/sys/i386/boot/biosboot/README.386BSD~ Fri Feb 17 08:57:51 1995 --- src/sys/i386/boot/biosboot/README.386BSD Sun Mar 10 16:59:28 1996 *************** *** 103,116 **** ########################################################################## ! In the case you have two drives the same type (both scsi or bith IDE/ESDI), ! wd(0,a)xxx ! will boot xxx from drive 0, a partition. ! wd(1,a)xxx ! will boot xxx from drive 1, a partition. ! similarly for sd. ! if you have one wd drive and one scsi drive, then you MUST ! use device 'hd' otherwise the following will happen: --- 103,119 ---- ########################################################################## ! In the case you have several drives the same type (all scsi or all IDE/ESDI), ! wd(0,a)xxx ! will boot xxx from drive 0, a partition. ! wd(1,a)xxx ! will boot xxx from drive 1, a partition. ! similarly for sd and for higher drive numbers (if the BIOS supports them). ! if you have one or more wd drives and one or more scsi drives, then yo ! MUST specify the BIOS drive number for booting the scsi drives: ! 2:sd(0,a)xxx ! will boot xxx from scsi drive 0, a partition, provided `2' is the correct ! BIOS drive number for sd0. otherwise the following will happen: *************** *** 119,126 **** it boots the kernel correctly, then tells the kernel to use sd1 as root. you however may not have an sd1, and problems arise. - - hd is special in that the kernel is always told to use unit 0, - The correct TYPE of device will be specified too, so the kernel - will be told either sd0 or wd0. Whether sd or wd is specified to the kernel is read from the disklabel, --- 122,125 ---- diff -c2 src/sys/i386/boot/biosboot/README.serial~ src/sys/i386/boot/biosboot/README.serial *** src/sys/i386/boot/biosboot/README.serial~ Fri Apr 21 19:43:53 1995 --- src/sys/i386/boot/biosboot/README.serial Sun Mar 10 18:08:25 1996 *************** *** 77,83 **** >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory ! Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. ! Usage: [[[fd(0,a)]/kernel][-s][-r][-a][-c][-d][-b][-v][-h]] ! Use ? for file list or simply press Return for defaults Boot: --- 77,83 ---- >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory ! Usage: [[[0:][fd](0,a)]/kernel][-abcCdhrsv] ! Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 ! Use ? for file list or press ENter for defaults Boot: diff -c2 src/sys/i386/boot/biosboot/boot.c~ src/sys/i386/boot/biosboot/boot.c *** src/sys/i386/boot/biosboot/boot.c~ Sat Mar 9 04:42:24 1996 --- src/sys/i386/boot/biosboot/boot.c Sun Mar 10 18:24:39 1996 *************** *** 101,117 **** gateA20(); ! ! /***************************************************************\ ! * As a default set it to the first partition of the boot * ! * floppy or hard drive * ! * Define BOOT_HT to boot sd0 when wd0 is also installed * ! \***************************************************************/ ! part = 0; unit = drive & 0x7f; ! #ifdef BOOT_HD ! maj = (drive&0x80 ? 1 : 2); /* a good first bet */ ! #else ! maj = (drive&0x80 ? 0 : 2); /* a good first bet */ #endif loadstart: --- 110,135 ---- gateA20(); ! /* ! * The default boot device is the first partition in the ! * compatibility slice on the boot drive. ! */ ! dosdev = drive; ! maj = 2; unit = drive & 0x7f; ! #ifdef dontneed ! slice = 0; ! part = 0; ! #endif ! if (drive & 0x80) { ! /* ! * Hard drive. Adjust. Guess that the FreeBSD unit number ! * is the BIOS drive number biased by BOOT_HD_BIAS, ! */ ! maj = 0; ! #if BOOT_HD_BIAS > 0 ! if (BOOT_HD_BIAS <= unit) ! unit -= BOOT_HD_BIAS; #endif + } loadstart: *************** *** 119,127 **** /* If we have looped, use the previous entries as defaults */ printf("\n>> FreeBSD BOOT @ 0x%x: %d/%d k of memory\n" ! "Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.\n" ! "Usage: [[%s(%d,a)]%s][-abcCdhrsv]\n" "Use ? for file list or press Enter for defaults\n\nBoot: ", ouraddr, bootinfo.bi_basemem, bootinfo.bi_extmem, ! devs[maj], unit, name); name = dflname; /* re-initialize in case of loop */ --- 137,145 ---- /* If we have looped, use the previous entries as defaults */ printf("\n>> FreeBSD BOOT @ 0x%x: %d/%d k of memory\n" ! "Usage: [[[%d:][%s](%d,a)]%s][-abcCdhrsv]\n" ! "Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1\n" "Use ? for file list or press Enter for defaults\n\nBoot: ", ouraddr, bootinfo.bi_basemem, bootinfo.bi_extmem, ! dosdev & 0x7f, devs[maj], unit, name); name = dflname; /* re-initialize in case of loop */ *************** *** 167,171 **** startaddr = head.a_entry & 0x00FFFFFF; addr = startaddr; ! printf("Booting %s(%d,%c)%s @ 0x%x\n" , devs[maj] , unit --- 185,190 ---- startaddr = head.a_entry & 0x00FFFFFF; addr = startaddr; ! printf("Booting %d:%s(%d,%c)%s @ 0x%x\n" ! , dosdev & 0x7f , devs[maj] , unit diff -c2 src/sys/i386/boot/biosboot/sys.c~ src/sys/i386/boot/biosboot/sys.c *** src/sys/i386/boot/biosboot/sys.c~ Mon Jun 26 15:07:31 1995 --- src/sys/i386/boot/biosboot/sys.c Sun Mar 10 18:18:30 1996 *************** *** 39,42 **** --- 39,44 ---- #endif + static char biosdrivedigit; + #define BUFSIZE 8192 #define MAPBUFSIZE BUFSIZE *************** *** 165,169 **** { char **devp, *cp = name; ! int ret; /*******************************************************\ * If bracket given look for preceding device name * --- 167,172 ---- { char **devp, *cp = name; ! int biosdrive, ret; ! /*******************************************************\ * If bracket given look for preceding device name * *************** *** 177,180 **** --- 180,193 ---- else { + /* + * Look for a BIOS drive number (a leading digit followed + * by a colon). + */ + if (*(name + 1) == ':' && *name >= '0' && *name <= '9') { + biosdrivedigit = *name; + name += 2; + } else + biosdrivedigit = '\0'; + if (cp++ != name) { *************** *** 211,232 **** return 1; } switch(maj) { - case 1: - dosdev = unit | 0x80; - unit = 0; - break; case 0: case 4: ! dosdev = unit | 0x80; break; case 2: ! dosdev = unit; break; ! case 3: ! printf("Wangtek unsupported\n"); return 1; - break; } inode.i_dev = dosdev; /***********************************************\ --- 224,254 ---- return 1; } + if (biosdrivedigit != '\0') + biosdrive = biosdrivedigit - '0'; + else { + biosdrive = unit; + #if BOOT_HD_BIAS > 0 + /* XXX */ + if (maj == 4) + biosdrive += BOOT_HD_BIAS; + #endif + } switch(maj) { case 0: case 4: ! dosdev = biosdrive | 0x80; break; case 2: ! dosdev = biosdrive; break; ! default: ! printf("Unknown device\n"); return 1; } + printf("dosdev = %x, biosdrive = %d, unit = %d, maj = %d\n", + dosdev, biosdrive, unit, maj); + getchar(0); + inode.i_dev = dosdev; /***********************************************\ diff -c2 src/sys/i386/boot/biosboot/table.c~ src/sys/i386/boot/biosboot/table.c *** src/sys/i386/boot/biosboot/table.c~ Sat Mar 9 04:42:24 1996 --- src/sys/i386/boot/biosboot/table.c Sun Mar 10 15:47:40 1996 *************** *** 137,141 **** * fragmentation. */ ! char *devs[] = { "wd", "hd", "fd", "wt", "sd", 0 }; char dflname[] = "/kernel"; char *name = dflname; --- 137,141 ---- * fragmentation. */ ! char *devs[] = { "wd", "dk", "fd", "wt", "sd", 0 }; char dflname[] = "/kernel"; char *name = dflname; From owner-freebsd-current Sun Mar 10 01:23:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06781 for current-outgoing; Sun, 10 Mar 1996 01:23:57 -0800 (PST) Received: from central.cis.upenn.edu (CENTRAL.CIS.UPENN.EDU [158.130.12.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA06771 for ; Sun, 10 Mar 1996 01:23:52 -0800 (PST) Received: from gradin.cis.upenn.edu (GRADIN.CIS.UPENN.EDU [158.130.4.4]) by central.cis.upenn.edu (8.6.12/UPenn 1.4) with ESMTP id EAA27095 for ; Sun, 10 Mar 1996 04:23:51 -0500 Received: by gradin.cis.upenn.edu id EAA07541; Sun, 10 Mar 1996 04:23:50 -0500 From: dherbst@gradient.cis.upenn.edu (Darrel Herbst) Posted-Date: Sun, 10 Mar 1996 04:23:50 -0500 Message-Id: <199603100923.EAA07541@gradin.cis.upenn.edu> Subject: Re: 3c5X9 working? To: current@freebsd.org Date: Sun, 10 Mar 1996 04:23:50 -0500 (EST) In-Reply-To: from "Gennady Sorokopud" at Mar 10, 96 10:07:09 am X-Mailer: ELM [version 2.4 PL23-upenn3.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On 09-Mar-96 "Justin T. Gibbs" wrote: > >>Are any of you having problems with 3c509 or 3c579 cards in current? > > Seems to be stable as a rock right now. I tested the card under all > possible network conditions (except probably multicast and IPX) and everything > works fine. I'm having trouble with multicasting on the 3c509. The -current driver just sort of lets you set yourself in the multicast group, but doesn't seem to tell the arp tables that the multicast ip should be treated as a multicast ip. Hence, I get "host down" errors when I try and send multicast udp packets out and the arp timer goes off on my multicast ip address. I tried to look at the way if_ed.c handles this, but my changes didn't solve the problem. I don't think this affects the stability of the driver, but the functionality is incorrect, isn't it? I mean, you shouldn't send arp packets on a multicast address, should you? From owner-freebsd-current Sun Mar 10 01:28:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA07347 for current-outgoing; Sun, 10 Mar 1996 01:28:08 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA07320 for ; Sun, 10 Mar 1996 01:28:01 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id LAA16983; Sun, 10 Mar 1996 11:27:27 +0200 (SAT) Message-Id: <199603100927.LAA16983@grumble.grondar.za> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), current@freebsd.org Subject: Re: HEADS UP! Please check... Date: Sun, 10 Mar 1996 11:27:26 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > What happens if your network is down to your kerberos server and your > > user.root instance has a different password than your local root account? > > How do you know which password to give? > > > > I fear in this situation you even can't enter su in your client machine. > It is especially bad on slip machine, because you need to enter > su password first time to dial to provider to become kerberos > client next. If it is so, please back out this change. In both of these cases there is the -K option which tells su not to use kerberos. There is a little confusion about what my change actually does. In the pre-cahnge version of su, the user could be prompted twice for a password. in the post change version, the user is promped once, and the same password may be used again _if_necessary_ by the "other" authentication method (root password in /etc/passwd). I did post the patch for review before committing it. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 02:22:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA12392 for current-outgoing; Sun, 10 Mar 1996 02:22:02 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA12377 for ; Sun, 10 Mar 1996 02:21:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA16919 for ; Sun, 10 Mar 1996 11:21:50 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id LAA07004 for freebsd-current@FreeBSD.org; Sun, 10 Mar 1996 11:21:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id LAA00855 for freebsd-current@FreeBSD.org; Sun, 10 Mar 1996 11:14:11 +0100 (MET) From: J Wunsch Message-Id: <199603101014.LAA00855@uriah.heep.sax.de> Subject: Re: VM problems To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 10 Mar 1996 11:14:11 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603092147.VAA04140@dyson.iquest.net> from "John S. Dyson" at Mar 9, 96 09:47:11 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: > I committed some changes on Fri night (should be available today > for sup) to current. I think that the VM problems should be > fixed. (INN still probably has problems -- that is later tonite > and tomorrow work.) Please try the stuff out and give me feedback > good or bad. I would appreciate it!!! I've seen the mass commits, and upgraded the kernel yesterday. This one did already hang twice (hard hangs) for an undetectable reason (*), but i haven't seen a VM-related panic. (*) The SCSI LED was lit. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 10 02:47:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA14707 for current-outgoing; Sun, 10 Mar 1996 02:47:40 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA14691 for ; Sun, 10 Mar 1996 02:47:26 -0800 (PST) Received: from tiger.fl.net.au (tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id UAA15399 for ; Sun, 10 Mar 1996 20:50:10 +1000 (EST) Message-Id: <2.2.32.19960311074605.00a4bb08@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 10 Mar 1996 21:46:05 -1000 To: current@freebsd.org From: Andrew Foster Subject: finger and 2.2-960303-SNAP Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, It seems that finger is broken (partially) in this SNAP. I cannot finger my Xylogics Remote Annex 4000, but other hosts seem to work. I receive : [annex1.fl.net.au] finger: read: Connection reset by peer However, telnetting to the finger port works fine, as does running finger on a 2.1.0-R system. I have run the 2.1.0-R binary on this SNAP and it works fine (and does not have the Connection reset by peer error). The finger output is quite long for that site - feel free to try it out yourself. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 02:50:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA14961 for current-outgoing; Sun, 10 Mar 1996 02:50:52 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA14953 for ; Sun, 10 Mar 1996 02:50:48 -0800 (PST) Received: from tiger.fl.net.au (tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id UAA15466; Sun, 10 Mar 1996 20:53:05 +1000 (EST) Message-Id: <2.2.32.19960311074859.00a3120c@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 10 Mar 1996 21:48:59 -1000 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Andrew Foster Subject: Re: Booting. Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, >booting from sd5 when wd3 is also installed > >...as posted half an hour before your mail (to freebsd-current though). As someone else also suggested, removing the IDE drive from the BIOS works fine. FreeBSD can still access the drive normally, and my BIOS doesn't try to boot from it. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 03:15:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA16739 for current-outgoing; Sun, 10 Mar 1996 03:15:20 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA16730 Sun, 10 Mar 1996 03:15:16 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id MAA29482; Sun, 10 Mar 1996 12:00:32 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id MAA00325; Sun, 10 Mar 1996 12:04:24 +0100 (MET) From: Andreas Klemm Message-Id: <199603101104.MAA00325@knobel.gun.de> Subject: My machine simply hangs, no panic, no messages entry To: current@freebsd.org Date: Sun, 10 Mar 1996 12:04:23 +0100 (MET) Cc: jkh@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Today my machine simply stopped working 2 times, hang without a panic message or such. I supped the newest kernel sources some minutes ago, let's see what happens then. My machine: ASUS P55TP4XE, P100, AHA 2940, 32 MB 60ns. The machine had a workload of 2 and was connected to internet via dialup ppp. KDEBUG and KTRACE was enabled. I'm currently running a debugging kernel (config -g ...). The harddisk light was off, when the machine hung. The modem line remained busy (good luck for me this time, imagine this at night, nice phone costs...). Other strange things - mounting a cdrom lasts about 20 seconds. During that time the system seems to be very busy. harddisk is making a lot of noise. The cdrom driver is loaded on demand, not compiled into the kernel. - After cdrom fs is mounted (FreeBSD 2.1 CD) a find /cdrom -print brings the machine in a hanging state, too. - top shows swap: 98M Total, 98M used but in fact I'm running without X and without paging activities... My BIOS settings are pretty standard (burst timing and such). Please tell me what additional infos you need. BTW: Why is -current so unstable at the moment? Everything ran fine about three weeks ago. Since then I randomly get panics (trap 12 in vm) and such. That's the reason, why I enabled KDEBUG. Is there a chance to get it a bit more stable, soon ? It would be fine, if the advanced kernel hackers of you would concentrate on these problems, to get 2.2 working again. Andreas /// BTW: here an excerpt from the messages after booting with -v Mar 10 11:37:14 knobel /kernel: FreeBSD 2.2-CURRENT #3: Sun Mar 10 11:35:19 MET 1996 Mar 10 11:37:14 knobel /kernel: root@knobel.gun.de:/local/FreeBSD/current/src/sys/compile/KNOBEL Mar 10 11:37:14 knobel /kernel: CPU: Pentium (99.46-MHz 586-class CPU) Mar 10 11:37:14 knobel /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 Mar 10 11:37:14 knobel /kernel: Features=0x1bf Mar 10 11:37:14 knobel /kernel: real memory = 33554432 (32768K bytes) Mar 10 11:37:14 knobel /kernel: avail memory = 24739840 (24160K bytes) Mar 10 11:37:14 knobel /kernel: BIOS Geometries: Mar 10 11:37:14 knobel /kernel: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors Mar 10 11:37:14 knobel /kernel: 0 accounted for Mar 10 11:37:14 knobel /kernel: pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x8000005c Mar 10 11:37:14 knobel /kernel: pcibus_setup(1a): mode1res=0x80000000 (0x80000000) Mar 10 11:37:14 knobel /kernel: pcibus_check: device 0 is there (id=122d8086) Mar 10 11:37:14 knobel /kernel: Probing for devices on PCI bus 0: Mar 10 11:37:14 knobel /kernel: configuration mode 1 allows 32 devices. Mar 10 11:37:14 knobel /kernel: chip0 rev 2 on pci0:0 Mar 10 11:37:14 knobel /kernel: CPU Inactivity timer: clocks Mar 10 11:37:14 knobel /kernel: Peer Concurrency: enabled Mar 10 11:37:14 knobel /kernel: CPU-to-PCI Write Bursting: enabled Mar 10 11:37:14 knobel /kernel: PCI Streaming: enabled Mar 10 11:37:14 knobel /kernel: Bus Concurrency: enabled Mar 10 11:37:15 knobel /kernel: Cache: 256K pipelined-burst secondary; L1 enabled Mar 10 11:37:15 knobel /kernel: DRAM: no memory hole, 66 MHz refresh Mar 10 11:37:15 knobel /kernel: Read burst timing: x-2-2-2/x-3-3-3 Mar 10 11:37:15 knobel /kernel: Write burst timing: x-3-3-3 Mar 10 11:37:15 knobel /kernel: RAS-CAS delay: 3 clocks Mar 10 11:37:15 knobel /kernel: chip1 rev 2 on pci0:7 Mar 10 11:37:15 knobel /kernel: I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Mar 10 11:37:15 knobel /kernel: Extended BIOS: disabled Mar 10 11:37:15 knobel /kernel: Lower BIOS: enabled Mar 10 11:37:15 knobel /kernel: Coprocessor IRQ13: enabled Mar 10 11:37:15 knobel /kernel: Mouse IRQ12: disabled Mar 10 11:37:15 knobel /kernel: Interrupt Routing: A: IRQ11, B: disabled, C: disabled, D: disabled Mar 10 11:37:15 knobel /kernel: MB0: disabled, MB1: disabled Mar 10 11:37:15 knobel /kernel: pci0:7: Intel Corporation, device=0x1230, class=storage (ide) [no driver assigned] Mar 10 11:37:15 knobel /kernel: map(20): io(e800) Mar 10 11:37:16 knobel /kernel: vga0 rev 0 int a irq ?? on pci0:10 Mar 10 11:37:16 knobel /kernel: mapreg[10] type=0 addr=f8000000 size=2000000. Mar 10 11:37:16 knobel /kernel: ahc0 rev 3 int a irq 11 on pci0:12 Mar 10 11:37:16 knobel /kernel: mapreg[10] type=1 addr=0000e400 size=0100. Mar 10 11:37:16 knobel /kernel: mapreg[14] type=0 addr=f7ff0000 size=1000. Mar 10 11:37:16 knobel /kernel: ahc0: BurstLen = 8DWDs, Latency Timer = 32PCLKS Mar 10 11:37:16 knobel /kernel: ahc0: Reading SEEPROM...done. Mar 10 11:37:16 knobel /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs Mar 10 11:37:16 knobel /kernel: ahc0: Downloading Sequencer Program...Done Mar 10 11:37:16 knobel /kernel: ahc0: Probing channel A Mar 10 11:37:16 knobel /kernel: ahc0: target 0 synchronous at 10.0MHz, offset = 0xf Mar 10 11:37:17 knobel /kernel: (ahc0:0:0): "QUANTUM XP34301 1051" type 0 fixed SCSI 2 Mar 10 11:37:17 knobel /kernel: sd0(ahc0:0:0): Direct-Access 4106MB (8410200 512 byte sectors) Mar 10 11:37:17 knobel /kernel: sd0(ahc0:0:0): with 4076 cyls, 20 heads, and an average 103 sectors/track Mar 10 11:37:17 knobel /kernel: ahc0: target 6 synchronous at 4.0MHz, offset = 0xf Mar 10 11:37:17 knobel /kernel: (ahc0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 Mar 10 11:37:17 knobel /kernel: cd0(ahc0:6:0): CD-ROM cd present [325252 x 2048 byte records] Mar 10 11:37:17 knobel /kernel: pci0: uses 33558528 bytes of memory from f7ff0000 upto f9ffffff. Mar 10 11:37:17 knobel /kernel: pci0: uses 256 bytes of I/O space from e400 upto e4ff. Mar 10 11:37:17 knobel /kernel: Probing for devices on the ISA bus: Mar 10 11:37:17 knobel /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Mar 10 11:37:17 knobel /kernel: sc0: VGA color <4 virtual consoles, flags=0x0> Mar 10 11:37:17 knobel /kernel: ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa Mar 10 11:37:17 knobel /kernel: ed0: address 00:00:c0:25:fd:2d, type WD8013EPC (16 bit) Mar 10 11:37:17 knobel /kernel: bpf: ed0 attached Mar 10 11:37:17 knobel /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Mar 10 11:37:17 knobel /kernel: sio0: type 16550A Mar 10 11:37:17 knobel /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 10 11:37:17 knobel /kernel: sio1: type 16550A Mar 10 11:37:17 knobel /kernel: lpt0 at 0x378-0x37f irq 7 on isa Mar 10 11:37:17 knobel /kernel: lpt0: Interrupt-driven port Mar 10 11:37:18 knobel /kernel: lp0: TCP/IP capable interface Mar 10 11:37:18 knobel /kernel: bpf: lp0 attached Mar 10 11:37:18 knobel /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Mar 10 11:37:18 knobel /kernel: fdc0: NEC 72065B Mar 10 11:37:18 knobel /kernel: fd0: 1.44MB 3.5in Mar 10 11:37:18 knobel /kernel: npx0 on motherboard Mar 10 11:37:18 knobel /kernel: npx0: INT 16 interface Mar 10 11:37:18 knobel /kernel: joy0 at 0x201 on isa Mar 10 11:37:19 knobel /kernel: joy0: joystick Mar 10 11:37:19 knobel /kernel: sb0 at 0x220 irq 5 drq 1 on isa Mar 10 11:37:19 knobel /kernel: sb0: Mar 10 11:37:19 knobel /kernel: sbxvi0 at 0x0 drq 5 on isa Mar 10 11:37:19 knobel /kernel: sbxvo0: Mar 10 11:37:19 knobel /kernel: sbmidi0 at 0x330 on isa Mar 10 11:37:19 knobel /kernel: Mar 10 11:37:20 knobel /kernel: opl0 at 0x388 on isa Mar 10 11:37:20 knobel /kernel: opl0: Mar 10 11:37:20 knobel /kernel: imasks: bio c0000840, tty c003009a, net c0020400 Mar 10 11:37:20 knobel /kernel: bpf: tun0 attached Mar 10 11:37:20 knobel /kernel: bpf: lo0 attached Mar 10 11:37:20 knobel /kernel: sd0s1: type 0x6, start 63, end = 514079, size 514017 : OK Mar 10 11:37:20 knobel /kernel: sd0s2: type 0x5, start 514080, end = 2056319, size 1542240 : OK Mar 10 11:37:20 knobel /kernel: sd0s3: type 0xa5, start 2056320, end = 8401994, size 6345675 : OK Mar 10 11:37:20 knobel /kernel: sd0s5: type 0x6, start 514143, end = 1028159, size 514017 : OK Mar 10 11:37:20 knobel /kernel: sd0: type 0x5, start 1028160, end = 2056319, size 1028160 : OK Mar 10 11:37:20 knobel /kernel: sd0s6: type 0x7, start 1028223, end = 2056319, size 1028097 : OK -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Sun Mar 10 03:19:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA17065 for current-outgoing; Sun, 10 Mar 1996 03:19:12 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA17046 for ; Sun, 10 Mar 1996 03:19:07 -0800 (PST) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id NAA07415; Sun, 10 Mar 1996 13:05:07 +0200 (EET) Received: (hsu@localhost) by cantina.clinet.fi (8.7.3/8.6.4) id NAA05717; Sun, 10 Mar 1996 13:05:07 +0200 (EET) Date: Sun, 10 Mar 1996 13:05:07 +0200 (EET) Message-Id: <199603101105.NAA05717@cantina.clinet.fi> From: Heikki Suonsivu To: straka Cc: freebsd-current@FreeBSD.ORG In-reply-to: straka's message of 10 Mar 1996 04:04:47 +0200 Subject: Re: panic: unwire: page not in pmap Organization: Clinet Ltd, Espoo, Finland References: Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In article straka writes: While booting from the boot floppy in 960303-SNAP, the kernel panics with the message panic: unwire: page not in pmap I filed a PR about this message, though get it only when I'm trying to compile the latest version of ssh. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 From owner-freebsd-current Sun Mar 10 03:59:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA20282 for current-outgoing; Sun, 10 Mar 1996 03:59:11 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA20271 for ; Sun, 10 Mar 1996 03:59:05 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id NAA25344 for ; Sun, 10 Mar 1996 13:58:45 +0200 (SAT) Message-Id: <199603101158.NAA25344@grumble.grondar.za> To: current@freebsd.org Subject: Compat collection. Date: Sun, 10 Mar 1996 13:58:42 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi On the 2.1 CD is a HUGE collection in compat20, all ending in .2.0 Looking in -current's /usr/lib, the only libs with a major version >2 are libc.so.3.0 libdialog.so.3.0 libforms.so.3.0 libg++.so.3.0 libncurses.so.3.0 libreadline.so.3.0 Am I correct in saying that these are the only one for which we will have to find 2.n versions for a compat distribution? I take it then that the idea would be to get the latest version of a 2.n SHLIB off a release CD and add it? I would also like to add libgcc.so.261.0 to the list. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 04:30:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA22669 for current-outgoing; Sun, 10 Mar 1996 04:30:12 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA22653 for ; Sun, 10 Mar 1996 04:30:02 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id OAA26934; Sun, 10 Mar 1996 14:16:11 +0200 (SAT) Message-Id: <199603101216.OAA26934@grumble.grondar.za> To: Mark Murray cc: current@FreeBSD.org Subject: Re: Compat collection. Date: Sun, 10 Mar 1996 14:16:08 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk BTW - This means that I am volunteering for the job. M Mark Murray wrote: > Hi > > On the 2.1 CD is a HUGE collection in compat20, all ending in .2.0 > > Looking in -current's /usr/lib, the only libs with a major version > >2 are > > libc.so.3.0 > libdialog.so.3.0 > libforms.so.3.0 > libg++.so.3.0 > libncurses.so.3.0 > libreadline.so.3.0 > > Am I correct in saying that these are the only one for which we will > have to find 2.n versions for a compat distribution? > > I take it then that the idea would be to get the latest version of a > 2.n SHLIB off a release CD and add it? > > I would also like to add libgcc.so.261.0 to the list. > > M > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200 > Finger mark@grondar.za for PGP key -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 05:00:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA24855 for current-outgoing; Sun, 10 Mar 1996 05:00:26 -0800 (PST) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA24848 for ; Sun, 10 Mar 1996 05:00:24 -0800 (PST) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.7.4/8.6.9) with ESMTP id FAA00497 for ; Sun, 10 Mar 1996 05:00:23 -0800 (PST) To: current@freebsd.org Subject: vm_fork: u_map allocation failed Date: Sun, 10 Mar 1996 05:00:21 -0800 Message-ID: <493.826462821@pain.csrv.uidaho.edu> From: Faried Nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi, i just panic'd twice with the above message. i sup'd sys a few hours ago (just before the linux elf commits). the first time it panic'd was while playing with ipfw. i don't know if there's a relation; i'll build a kernel w/o ipfirewall tomorrow. faried, back to the feb 12 kernel. From owner-freebsd-current Sun Mar 10 05:26:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA26707 for current-outgoing; Sun, 10 Mar 1996 05:26:57 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA26702 for ; Sun, 10 Mar 1996 05:26:53 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id FAA11063; Sun, 10 Mar 1996 05:26:17 -0800 From: "Rodney W. Grimes" Message-Id: <199603101326.FAA11063@GndRsh.aac.dev.com> Subject: Re: booting from sd5 when wd3 is also installed To: bde@zeta.org.au (Bruce Evans) Date: Sun, 10 Mar 1996 05:26:16 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199603100915.UAA20728@godzilla.zeta.org.au> from "Bruce Evans" at Mar 10, 96 08:15:55 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > These changes should allow specifying the BIOS drive number independently > of the FreeBSD unit number. E.g., `9:sd(5,a)' describes the drive with > BIOS drive number 9 and sd unit number 5. > > hd(N,a) is no longer supported because it doesn't fit and it only works > for unit number 0. Use N:sd(0,a) instead. YEAAA!!! I love this, and would have killed for it 2 years ago, but now the last 2 of my IDE drives sit on a shelf as junk.... > I haven't decided exactly how to handle these points: > - how sticky should the drive number be? What is the default drive number > after 1:sd(0,a)/nonesuch followed by /kernel? IMHO, 0. Does ``1:?'' or even ``1:xx(y,z)/kernel?'' work? > - option BOOT_HD_BIAS. This replaces option BOOT_HD. The BIOS drive > number for unit N is currently BOOT_HD_BIAS + N. Should the bias only > be added for sd drives? How does biasing interact with previously > specified drive numbers? I am not sure, I need to think on this one for a few days... > > Please test the changes on systems with mixed IDE and SCSI drives. I > don't have any. I can't test them, but have a small nit I found doing a visual over the context diff.... ohh... and can you bounds check the BIOS drive number against the number of drives reported by the BIOS, I seem to recall an infinite error loop if you did something like wd(1,a)/kernel with only one BIOS drive. > > diff -c2 src/sys/i386/boot/biosboot/README.serial~ src/sys/i386/boot/biosboot/README.serial > *** src/sys/i386/boot/biosboot/README.serial~ Fri Apr 21 19:43:53 1995 > --- src/sys/i386/boot/biosboot/README.serial Sun Mar 10 18:08:25 1996 > *************** > *** 77,83 **** > > >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory > ! Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. > ! Usage: [[[fd(0,a)]/kernel][-s][-r][-a][-c][-d][-b][-v][-h]] > ! Use ? for file list or simply press Return for defaults > Boot: > > --- 77,83 ---- > > >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory > ! Usage: [[[0:][fd](0,a)]/kernel][-abcCdhrsv] > ! Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 > ! Use ? for file list or press ENter for defaults ^n > Boot: > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Mar 10 05:51:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28231 for current-outgoing; Sun, 10 Mar 1996 05:51:44 -0800 (PST) Received: from utrhcs.cs.utwente.nl ([130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28226 for ; Sun, 10 Mar 1996 05:51:41 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelay-SVR4_1.3/RBCS) id OAA09140; Sun, 10 Mar 1996 14:50:04 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id OAA02557; Sun, 10 Mar 1996 14:50:01 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id OAA25555; Sun, 10 Mar 1996 14:50:00 +0100 To: Andrew Foster cc: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Sun, 10 Mar 1996 21:46:05 -1000." <2.2.32.19960311074605.00a4bb08@mail.fl.net.au> Date: Sun, 10 Mar 1996 14:49:56 +0100 Message-ID: <25554.826465796@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Mar 1996 21:46:05 -1000, Andrew Foster wrote: > Hi, > > It seems that finger is broken (partially) in this SNAP. > > I cannot finger my Xylogics Remote Annex 4000, but other hosts seem to work. > > I receive : > > [annex1.fl.net.au] > finger: read: Connection reset by peer Your peer (annex1.fl.net.au) has a broken TCP implementation and gets confused by the T/TCP packets. Your options: 1. Get Xylogics fix their TCP stack (preferred ;-). 2. Disable tcp_extensions in /etc/sysconfig. Actually, it's enough to do `sysctl -w net.inet.tcp.rfc1644=0' if you don't want to lose the other TCP extensions. Andras P.S: You can look up the T/TCP homepage for information about T/TCP including a list of TCP stacks having problem with T/TCP. http://www.noao.edu/~rstevens/ttcp.html From owner-freebsd-current Sun Mar 10 05:52:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28321 for current-outgoing; Sun, 10 Mar 1996 05:52:17 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28309 for ; Sun, 10 Mar 1996 05:52:13 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA20065; Sun, 10 Mar 1996 14:52:01 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id OAA10120; Sun, 10 Mar 1996 14:52:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id OAA01882; Sun, 10 Mar 1996 14:51:47 +0100 (MET) From: J Wunsch Message-Id: <199603101351.OAA01882@uriah.heep.sax.de> Subject: Re: Compat collection. To: mark@grondar.za (Mark Murray) Date: Sun, 10 Mar 1996 14:51:46 +0100 (MET) Cc: current@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603101158.NAA25344@grumble.grondar.za> from "Mark Murray" at Mar 10, 96 01:58:42 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Mark Murray wrote: [several libs with shmaj == 3] > Am I correct in saying that these are the only one for which we will > have to find 2.n versions for a compat distribution? It seems so. > > I take it then that the idea would be to get the latest version of a > 2.n SHLIB off a release CD and add it? > > I would also like to add libgcc.so.261.0 to the list. Not really compat2x, but also a compat problem: we used to ship a libcompat.so up until 2.0.5. Installing it into /usr/lib from a compatxx distribution however results in it being linked into new binaries. Instead, i usually pick /usr/junklib for it, and ldconfig this directory, too. Perhaps the hooks for this should go into the base system, so a compatxx distribution can easily make use of it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 10 06:26:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA29949 for current-outgoing; Sun, 10 Mar 1996 06:26:39 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA29944 for ; Sun, 10 Mar 1996 06:26:35 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA02483; Mon, 11 Mar 1996 01:25:34 +1100 From: michael butler Message-Id: <199603101425.BAA02483@asstdc.scgt.oz.au> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 11 Mar 1996 01:25:33 +1100 (EST) Cc: current@freebsd.org In-Reply-To: <199603100445.UAA10659@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 9, 96 08:45:51 pm X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes writes: > > So far three people, including myself, have reported the above panic > > message when booting the 3/3 SNAP kernel. All three of us have AMD DX4 > > processors (100 and 120MHz). > Can all three of you tell me if you have A80486DX4-100NV8T's or > A80486DX4-100SV8B's? The difference is the SV8B is the write back > enhanced DX4 and unless you have a motherboard that understands > how to deal with this you are going to have a cache coherency problem > between the internal and external cache. I note that through a number of drivers there is mention of cache-invalidation instructions (software-style) but none of them seem to implement anything of this nature. Is there a problem with doing this .. that is .. to invalidate the page(s) into which data has just been transferred prior to the application being told that the transfer completed? No other cases need to be considered do they ? michael From owner-freebsd-current Sun Mar 10 06:49:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA01328 for current-outgoing; Sun, 10 Mar 1996 06:49:23 -0800 (PST) Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA01321 for ; Sun, 10 Mar 1996 06:49:21 -0800 (PST) From: dob@clipper.cb.att.com Received: from clipper.cb.att.com by ig2.att.att.com id AA29324; Sun, 10 Mar 96 09:50:20 EST Received: from cbsky.cb.att.com by clipper.cb.att.com (4.1/EMS-1.1 SunOS) id AA24354; Sun, 10 Mar 96 09:49:07 EST Received: by cbsky.cb.att.com (5.x/EMS-1.1 client.cf 1/8/94 (SMI-4.1/SVR4)) id AA05629; Sun, 10 Mar 1996 09:49:06 -0500 Date: Sun, 10 Mar 1996 09:49:06 -0500 Message-Id: <9603101449.AA05629@cbsky.cb.att.com> To: current@freefall.freebsd.org, dyson@FreeBSD.ORG, freebsd-current-digest@FreeBSD.ORG Subject: Re: VM problems Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As John S. Dyson wrote: > > > I committed some changes on Fri night (should be available today > > for sup) to current. I think that the VM problems should be > > fixed. (INN still probably has problems -- that is later tonite > > and tomorrow work.) Please try the stuff out and give me feedback > > good or bad. I would appreciate it!!! > > I've seen the mass commits, and upgraded the kernel yesterday. This > one did already hang twice (hard hangs) for an undetectable reason > (*), but i haven't seen a VM-related panic. > > (*) The SCSI LED was lit. No more make sig 11's and 10's!!!! Happy, happy, joy, joy!!! Thanks! But... I've had one hard hang (press reset button) and one reboot (panic?, no dump, sorry). Both while remaking world and fiddling with the modem (ppp on reboot and minicom on hang). I've since setup to take dump if panic. This AM am redoing make world while having a memory pressure cooker running (malloc bunch, touch bunch, free bunch). Did get one error message on console/log when I logged in with all this mess running: Mar 10 09:25:33 llama /kernel: vnode_pager_putpages: attempt to write meta-data!!! -- 0xffffffe9(ff) If I get a dump will let you know. Thanks for your efforts. Dan O'Brien Lucent Technologies (Bell Labs Innovations) From owner-freebsd-current Sun Mar 10 06:49:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA01348 for current-outgoing; Sun, 10 Mar 1996 06:49:27 -0800 (PST) Received: from gw3.att.com (gw4.att.com [204.179.186.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA01340 for ; Sun, 10 Mar 1996 06:49:25 -0800 (PST) From: dob@clipper.cb.att.com Received: from clipper.cb.att.com by ig4.att.att.com id AA17674; Sun, 10 Mar 96 09:41:40 EST Received: from cbsky.cb.att.com by clipper.cb.att.com (4.1/EMS-1.1 SunOS) id AA24354; Sun, 10 Mar 96 09:49:07 EST Received: by cbsky.cb.att.com (5.x/EMS-1.1 client.cf 1/8/94 (SMI-4.1/SVR4)) id AA05629; Sun, 10 Mar 1996 09:49:06 -0500 Date: Sun, 10 Mar 1996 09:49:06 -0500 Message-Id: <9603101449.AA05629@cbsky.cb.att.com> To: current@freefall.freebsd.org, dyson@freebsd.org, freebsd-current-digest@freebsd.org Subject: Re: VM problems Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As John S. Dyson wrote: > > > I committed some changes on Fri night (should be available today > > for sup) to current. I think that the VM problems should be > > fixed. (INN still probably has problems -- that is later tonite > > and tomorrow work.) Please try the stuff out and give me feedback > > good or bad. I would appreciate it!!! > > I've seen the mass commits, and upgraded the kernel yesterday. This > one did already hang twice (hard hangs) for an undetectable reason > (*), but i haven't seen a VM-related panic. > > (*) The SCSI LED was lit. No more make sig 11's and 10's!!!! Happy, happy, joy, joy!!! Thanks! But... I've had one hard hang (press reset button) and one reboot (panic?, no dump, sorry). Both while remaking world and fiddling with the modem (ppp on reboot and minicom on hang). I've since setup to take dump if panic. This AM am redoing make world while having a memory pressure cooker running (malloc bunch, touch bunch, free bunch). Did get one error message on console/log when I logged in with all this mess running: Mar 10 09:25:33 llama /kernel: vnode_pager_putpages: attempt to write meta-data!!! -- 0xffffffe9(ff) If I get a dump will let you know. Thanks for your efforts. Dan O'Brien Lucent Technologies (Bell Labs Innovations) From owner-freebsd-current Sun Mar 10 06:57:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA01857 for current-outgoing; Sun, 10 Mar 1996 06:57:58 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA01852 for ; Sun, 10 Mar 1996 06:57:54 -0800 (PST) Received: by Sisyphos id AA04448 (5.67b/IDA-1.5 for current@FreeBSD.org); Sun, 10 Mar 1996 15:57:33 +0100 Message-Id: <199603101457.AA04448@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 10 Mar 1996 15:57:33 +0100 In-Reply-To: Jim Lowe "NCR disk controller, hp disk" (Mar 8, 16:39) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Jim Lowe Subject: Re: NCR disk controller, hp disk Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 8, 16:39, Jim Lowe wrote: } Subject: NCR disk controller, hp disk Hi Jim! Sorry for the late reply ... I had intended to stay off my office this weekend and only came in by accident ... Well, lets see: } I have an NCR 825 PCI disk controller. I just attached a second disk } to the controller and am trying to access it. The second disk works } just fine under dos, but not freebsd-current. I am getting the following } errors: } } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , retries:4 } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , retries:3 } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , retries:2 } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , retries:1 } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , FAILURE } sd1: error reading primary partition table reading fsbn 0 (sd1 bn 0; cn 0 tn 0 s } n 0) This particular HP drive (the C3724S) is known to cause problems with tagged commands. Please rebuild your kernel with options "SCSI_NCR_DFLT_TAGS=0" and everything will be fine again. You can reenable tags for the first drive using # ncrcontrol -s tags=0 -s tags=4 I'd be really interested to understand what is going wrong here, since this is the only drive known to cause that kind of problem. The driver sends the command and the drive its reply just fine, but this reply indicates that the drive doesn't accept a tagged command, though it did inidcate support for this feature before. } Any clues as to what to try/do next? The boot up information follows. } I am not sure why I am getting the probe0(ncr0:9:0) errors either. This is a result of your building the kernel with "options SCSIDEBUG" and having a target of 9 selected in "/sys/scsi/scsi_debug.h". Please change this '9' into a '1' and send the boot log, since this may help me understand the reason for the incompatibility. If you are interested in getting this resolved, I'd need you to do a few more tests later. But you may choose to use the drive without tagged commands instead, it will still be fast enough :) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Sun Mar 10 09:52:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA10586 for current-outgoing; Sun, 10 Mar 1996 09:52:28 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA10581 for ; Sun, 10 Mar 1996 09:52:27 -0800 (PST) Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA22032 for ; Sun, 10 Mar 1996 09:52:23 -0800 Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.12/8.6.9) with ESMTP id JAA28526; Sun, 10 Mar 1996 09:51:05 -0800 From: Mostyn/Annabella Received: (mrl@localhost) by linda.teleport.com (8.6.12/8.6.12) id JAA23037; Sun, 10 Mar 1996 09:51:05 -0800 Message-Id: <199603101751.JAA23037@linda.teleport.com> Subject: vm/kern_lock.c:lock_read hang ? To: current@freebsd.org Date: Sun, 10 Mar 1996 09:51:05 -0800 (PST) Cc: mrl@teleport.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, My occaisional ppp (kernel) hangs seem to boil down to processes sleeping at the tsleep(l, PVM, "lockrd", 0); statement in lock_read in vm/kern_lock.c. Any attempt to do anything at this point permanently hangs the machine. Another way to create an instant panic is to go into ddb (cntl/alt/esc) and type - show map which goes off to vm_map_print and panics. This with a kernel from March 3rd. Mostyn Lewis From owner-freebsd-current Sun Mar 10 10:24:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA11999 for current-outgoing; Sun, 10 Mar 1996 10:24:21 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA11992 for ; Sun, 10 Mar 1996 10:24:19 -0800 (PST) Received: from ole.cs.tu-berlin.de (wosch@ole.cs.tu-berlin.de [130.149.22.3]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id TAA06530; Sun, 10 Mar 1996 19:24:15 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.9/8.6.9) id SAA00643; Sun, 10 Mar 1996 18:50:20 +0100 Date: Sun, 10 Mar 1996 18:50:20 +0100 From: Wolfram Schneider Message-Id: <199603101750.SAA00643@campa.panke.de> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: *.mk wishes In-Reply-To: <199603100011.LAA30782@godzilla.zeta.org.au> References: <199603100011.LAA30782@godzilla.zeta.org.au> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>sys.mk: >>MMAP_RO: read only mmap, for programs like grep, groff, look etc. >>MMAP_RW: write works (inn) > >I don't understand this. C macros should be defined in C headers. 20 programs which use mmap(2) 3 (gnu) programs with C macro HAVE_MMAP or HAVE_WORKING_MMAP 5 programs with PROT_WRITE 21 mmap calls with uncasted 'NULL' argument Ok, we don't need a variable in sys.mk for 3 programs only. We should fix the cast ... Wolfram From owner-freebsd-current Sun Mar 10 10:54:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA13720 for current-outgoing; Sun, 10 Mar 1996 10:54:16 -0800 (PST) Received: from uni-sb.de (uni-sb.de [134.96.7.230]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA13710 for ; Sun, 10 Mar 1996 10:54:14 -0800 (PST) Received: by uni-sb.de with ESMTP; Sun, 10 Mar 1996 19:54:03 +0100 (MET) Received: by cs.uni-sb.de with ESMTP; Sun, 10 Mar 1996 19:54:01 +0100 (MET) Received: from doom.cs.uni-sb.de (doom [134.96.247.254]) by wurzelausix.CS.Uni-SB.DE (8.7.5/wjp-SVR4/960127s) with SMTP id TAA16644; Sun, 10 Mar 1996 19:54:04 +0100 (MET) Message-ID: <3143250D.3A88@wurzelausix.cs.uni-sb.de> Date: Sun, 10 Mar 1996 19:53:01 +0100 From: Daniel Rock Organization: Universität des Saarlandes X-Mailer: Mozilla 2.0Ib6a [de] (Win95; I) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: NCR disk controller, hp disk References: <199603101457.AA04448@Sisyphos> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser wrote: > > On Mar 8, 16:39, Jim Lowe wrote: > } I have an NCR 825 PCI disk controller. I just attached a second disk > } to the controller and am trying to access it. The second disk works > } just fine under dos, but not freebsd-current. I am getting the following > } errors: > } > } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted > } , retries:4 > } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted > } , retries:3 > } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted > } , retries:2 > } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted > } , retries:1 > } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted > } , FAILURE > } sd1: error reading primary partition table reading fsbn 0 (sd1 bn 0; cn 0 tn 0 s > } n 0) > > This particular HP drive (the C3724S) is known > to cause problems with tagged commands. Please > rebuild your kernel with > > options "SCSI_NCR_DFLT_TAGS=0" > > and everything will be fine again. > > You can reenable tags for the first drive using > > # ncrcontrol -s tags=0 -s tags=4 > > I'd be really interested to understand what is > going wrong here, since this is the only drive > known to cause that kind of problem. The driver > sends the command and the drive its reply just > fine, but this reply indicates that the drive > doesn't accept a tagged command, though it did > inidcate support for this feature before. Not only FreeBSD has problems with HP drives. I had to disable tagged-command-queueing on a SparcServer 600, because the HP drive (a C3325A) showed up exactly the same problems (the SCSI HBA is a FAS236). Daniel From owner-freebsd-current Sun Mar 10 10:57:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA13959 for current-outgoing; Sun, 10 Mar 1996 10:57:01 -0800 (PST) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA13953 for ; Sun, 10 Mar 1996 10:56:58 -0800 (PST) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0tvqI5-0004IaC; Sun, 10 Mar 96 10:56 PST Date: Sun, 10 Mar 1996 10:56:24 -0800 (PST) From: Jake Hamby To: "Rodney W. Grimes" cc: current@FreeBSD.ORG, jkh@time.cdrom.com, toor@dyson.iquest.net Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) In-Reply-To: <199603100445.UAA10659@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 9 Mar 1996, Rodney W. Grimes wrote: > > Can all three of you tell me if you have A80486DX4-100NV8T's or > A80486DX4-100SV8B's? The difference is the SV8B is the write back > enhanced DX4 and unless you have a motherboard that understands > how to deal with this you are going to have a cache coherency problem > between the internal and external cache. > > I have yet to see a MB deal with this correctly when faced with > a bus master SCSI controller, though I have seen some that work fine > as long as no bus mastering is occuring. Far more don't work than > do work. > > If you don't have SV8B's or are not running them in WB mode, then > I don't have any idea what has gone wrong... FYI, I have the 100NV8T, so I guess that's not the problem. Whew! Note that the problem occurs with caches enabled OR disabled, I do have a bus mastering SCSI controller (Adaptec 2842VLB), and someone has reported that the problem occurs with the Intel DX2/66, so I guess AMD isn't the common link after all. For future reference, are you saying that the SV8B AMD chips are to be avoided, at least if busmastering SCSI controllers are involved? ---Jake From owner-freebsd-current Sun Mar 10 11:09:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA14550 for current-outgoing; Sun, 10 Mar 1996 11:09:25 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA14545 for ; Sun, 10 Mar 1996 11:09:22 -0800 (PST) Received: from tiger.fl.net.au (tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id FAA24838 for ; Mon, 11 Mar 1996 05:12:23 +1000 (EST) Message-Id: <2.2.32.19960311160811.009d6f98@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Mar 1996 06:08:11 -1000 To: current@freebsd.org From: Andrew Foster Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, >> > So far three people, including myself, have reported the above panic >> > message when booting the 3/3 SNAP kernel. All three of us have AMD DX4 >> > processors (100 and 120MHz). > >> Can all three of you tell me if you have A80486DX4-100NV8T's or >> A80486DX4-100SV8B's? The difference is the SV8B is the write back >> enhanced DX4 and unless you have a motherboard that understands >> how to deal with this you are going to have a cache coherency problem >> between the internal and external cache. Not me. I've got the NV8T and I've had no problems. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 11:24:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15087 for current-outgoing; Sun, 10 Mar 1996 11:24:15 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA15082 for ; Sun, 10 Mar 1996 11:24:12 -0800 (PST) Received: from tiger.fl.net.au (tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id FAA25089; Mon, 11 Mar 1996 05:27:13 +1000 (EST) Message-Id: <2.2.32.19960311162301.00a4bcf4@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Mar 1996 06:23:01 -1000 To: Andras Olah From: Andrew Foster Subject: Re: finger and 2.2-960303-SNAP Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Your peer (annex1.fl.net.au) has a broken TCP implementation and >gets confused by the T/TCP packets. Your options: > >1. Get Xylogics fix their TCP stack (preferred ;-). >2. Disable tcp_extensions in /etc/sysconfig. Actually, it's enough >to do `sysctl -w net.inet.tcp.rfc1644=0' if you don't want to lose >the other TCP extensions. > >Andras > >P.S: You can look up the T/TCP homepage for information about T/TCP >including a list of TCP stacks having problem with T/TCP. > http://www.noao.edu/~rstevens/ttcp.html And yet the old finger works fine, as does fingering from most other hosts I've tried. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 11:26:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15147 for current-outgoing; Sun, 10 Mar 1996 11:26:44 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA15142 for ; Sun, 10 Mar 1996 11:26:43 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id LAA22667 for ; Sun, 10 Mar 1996 11:26:41 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01621; Sun, 10 Mar 1996 12:21:10 -0700 From: Terry Lambert Message-Id: <199603101921.MAA01621@phaeton.artisoft.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: imb@scgt.oz.au (michael butler) Date: Sun, 10 Mar 1996 12:21:10 -0700 (MST) Cc: rgrimes@GndRsh.aac.dev.com, current@FreeBSD.org In-Reply-To: <199603101425.BAA02483@asstdc.scgt.oz.au> from "michael butler" at Mar 11, 96 01:25:33 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I note that through a number of drivers there is mention of > cache-invalidation instructions (software-style) but none of them seem to > implement anything of this nature. Is there a problem with doing this .. > that is .. to invalidate the page(s) into which data has just been > transferred prior to the application being told that the transfer completed? > No other cases need to be considered do they ? OK. This is an interesting topic. 8-(. Before, when I suggested that a DMA be triggered as part of a probe process on a per controller basis to determine if bounce buffers were necessary, I neglected the non-working cache case. The cache cases need to be considered at the same time because they need to trigger similar controller/memory events in order to be detectable. When a bus master DMA occurs, there is supposed to be a cache notification, and the L1 and L2 cache lines are supposed to be invalidated or written back for the memory range in which the DMA took place. It's possible to fail the L1 cache invalidate/write back, the L2, or both. The old Cyrix/TI 386 processors using the Cyrix chip mask (the newer Cyrix parts -- not sure about TI -- use a licensed version of the IBM "Blue Lightening" masks) had an L1 cache without implementing a cache notification mechanism. Because of this, if the L1 cache is enabled on these chips (it is disabled by default and must be explicitly enabled by software -- usually BIOS POST based on CMOS settings), they will potentially have stale data hanging around after a bus mastering DMA. These chips are detectable ("The Undocumented PC"), and the cache is software disableable (contravening the user preferences -- some might argue that it is a driver problem, and the driver should explicitly BINVD instead). For the L2, the Saturn I chipset (mask date pre-April 1994) had a flaw, where the DMA notification from PCI was simply not internally connected to anything. This is most often seen in Gateway and Dell systems with 60MHz Pentiums, but they aren't the only ones who used Saturn I's, so they aren't the only machines with problems. Finally, VLB systems frequently do not identify "master" slots. A "master" slot is one where cache notification occurs after a bus master DMA takes place. Now, these aren't the *only* cases, *but* they are tha majority of cases where "turn of the cache" will fix the problem. Detecting failed cache update is tricky-- mostly because a small amount of cache is involved, and you can't tell the difference between data that was correctly invalidated, and data that was invalidated to load in your test code, data, etc.. Basically, you have to fully set up a DMA into an area, but not trigger it, and the modify a small part of the area to force it into cache with a value other than the one that will result from the DMA. Then you trigger the DMA on a small enough operation that it doesn't cause the cache line for the invalid data to be flushed (you test this by doing the DMA to an area other than the cache area and use instruction timing to determine if the data is still in cache or if the operation blew it out -- a tricky operation). To avoid cache effects in determining the data that will result, you have to do BINVD's (the software cache flush) during the setup to the point that you do the cache load... not the least because you won't be able to load the test if there is a cache problm and you use a DMA-using driver. It's arguable whether BINVD'ing all your I/O is worthwhile -- you may not gain any significant benefit from the cache otherwise to compensate for the overhead; probably there will be *some* gain, but it will be marginal. One very real problem is that the people hacking the code areas that would need to change simply don't buy the cheap hardware necessary to reproduce the problem and allow them to test. Finally, for the less likely cases of a flaw in the motherboard L2 cache implementation (which may include you not being able to successfully BINVD the area and work around the bug in software), there is no fix except disabling the L2 cache. 8-(. Because of the need for a DMA card and a driver to use it, it's no wonder that this type of testing has not made it into a consumer "hardware test" application that you can use in a store before buying the hardware. It isn't worthwhile to BINVD in the majority of cases, because the majority is people with functional cache hardware. Admittedly, we have self-selected this by not "fixing" the problem in software for people without the good hardware. A decent fix would require a lot of effort and a lot of hooks to make it work in all cases (for instance, I could have two VLB controllers, one in a "master" slot, one not; the fix has to have a per controller granularity, etc.). 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Mar 10 12:57:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA18988 for current-outgoing; Sun, 10 Mar 1996 12:57:08 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA18980 for ; Sun, 10 Mar 1996 12:57:04 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id HAA14288; Mon, 11 Mar 1996 07:53:04 +1100 Date: Mon, 11 Mar 1996 07:53:04 +1100 From: Bruce Evans Message-Id: <199603102053.HAA14288@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@GndRsh.aac.dev.com Subject: Re: booting from sd5 when wd3 is also installed Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I haven't decided exactly how to handle these points: >> - how sticky should the drive number be? What is the default drive number >> after 1:sd(0,a)/nonesuch followed by /kernel? >IMHO, 0. Does ``1:?'' or even ``1:xx(y,z)/kernel?'' work? I had `1:' by itself working for a while, but decided that it shouldn't be so easy to change the BIOS number without changing the unit number, so I made `1:' only work with `xx(y,z)'. `1:xx(y,z)any' should work. `xx(y,z)any' works the same as now - the BIOS drive number is set to match `y'. This isn't the best behaviour (you often want to keep the BIOS boot drive number and change the FreeBSD unit number) but it is required for compatibility and is the best behaviour for changing the drive type from fd to sd. >I can't test them, but have a small nit I found doing a visual over the >context diff.... ohh... and can you bounds check the BIOS drive number Thanks. >against the number of drives reported by the BIOS, I seem to recall >an infinite error loop if you did something like wd(1,a)/kernel with >only one BIOS drive. It's still easy to get these. I got a lot when I forgot to subtract '0' from the drive number :-). Does the BIOS report the number of drives reliably? The byte at physical 0x475 seems to correctly give the total number of non-floppy drives here (not the number of wd drives like I once thought). BTW there is a bug in `gdb -k /kernel /dev/mem': gdb loops internally for `p/x *(int *)0xf0000475'; it ignores ^C but can be suspended. Bruce From owner-freebsd-current Sun Mar 10 13:09:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19520 for current-outgoing; Sun, 10 Mar 1996 13:09:24 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA19513 for ; Sun, 10 Mar 1996 13:09:20 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id NAA09871; Sun, 10 Mar 1996 13:07:08 -0800 (PST) Message-Id: <199603102107.NAA09871@precipice.shockwave.com> To: Andrew Foster cc: current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Sun, 10 Mar 1996 21:46:05 -1000." <2.2.32.19960311074605.00a4bb08@mail.fl.net.au> Date: Sun, 10 Mar 1996 13:07:08 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Your xylogics terminal server has a broken TCP implementation, it can't handle transaction tcp apparently. You can turn off tcp extensions, but I'd send them a bug report with a tcpdump of the conversation and explicitly note that you are sending a SYN packet with data and a FIN. Paul From: Andrew Foster Subject: finger and 2.2-960303-SNAP Hi, It seems that finger is broken (partially) in this SNAP. I cannot finger my Xylogics Remote Annex 4000, but other hosts seem to work. I receive : [annex1.fl.net.au] finger: read: Connection reset by peer However, telnetting to the finger port works fine, as does running finger on a 2.1.0-R system. I have run the 2.1.0-R binary on this SNAP and it works fine (and does not have the Connection reset by peer error). The finger output is quite long for that site - feel free to try it out yourself. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 13:11:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19699 for current-outgoing; Sun, 10 Mar 1996 13:11:59 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA19688 for ; Sun, 10 Mar 1996 13:11:55 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id NAA09940; Sun, 10 Mar 1996 13:10:39 -0800 (PST) Message-Id: <199603102110.NAA09940@precipice.shockwave.com> To: Andrew Foster cc: Andras Olah , current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Mon, 11 Mar 1996 06:23:01 -1000." <2.2.32.19960311162301.00a4bcf4@mail.fl.net.au> Date: Sun, 10 Mar 1996 13:10:39 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Old finger does not have the code in it to invoke t/tcp. Garrett did it to finger specificly so we had a good chance of finding broken tcp implementations in a non-critical fashion. It really is T/TCP behavior that isn't working, this is exactly the pattern. From: Andrew Foster Subject: Re: finger and 2.2-960303-SNAP >Your peer (annex1.fl.net.au) has a broken TCP implementation and >gets confused by the T/TCP packets. Your options: > >1. Get Xylogics fix their TCP stack (preferred ;-). >2. Disable tcp_extensions in /etc/sysconfig. Actually, it's enough >to do `sysctl -w net.inet.tcp.rfc1644=0' if you don't want to lose >the other TCP extensions. > >Andras > >P.S: You can look up the T/TCP homepage for information about T/TCP >including a list of TCP stacks having problem with T/TCP. > http://www.noao.edu/~rstevens/ttcp.html And yet the old finger works fine, as does fingering from most other hosts I've tried. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 13:27:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20774 for current-outgoing; Sun, 10 Mar 1996 13:27:52 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA20766 for ; Sun, 10 Mar 1996 13:27:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA15692; Mon, 11 Mar 1996 08:24:51 +1100 Date: Mon, 11 Mar 1996 08:24:51 +1100 From: Bruce Evans Message-Id: <199603102124.IAA15692@godzilla.zeta.org.au> To: bde@zeta.org.au, wosch@cs.tu-berlin.de Subject: Re: *.mk wishes Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >20 programs which use mmap(2) >3 (gnu) programs with C macro HAVE_MMAP or HAVE_WORKING_MMAP I only found 2 :-) (gdb and groff). They are apparently too old and/or complicated to use autoconf and haven't been configured quite right for FreeBSD (unless mmap was avoided on purpose). >5 programs with PROT_WRITE >21 mmap calls with uncasted 'NULL' argument >Ok, we don't need a variable in sys.mk for 3 programs only. We should >fix the cast ... newfs/mkfs.c passes an uncast 0 for a pointer and an uncast 0 for an off_t. rpc.statd passes an uncast NULL for a pointer and an uncast 0 for an off_t. I would't worry about fixing this. There must be a prototype in scope for the uncast 0 for an off_t to work, and it isn't a bug to omit the casts iff there is a prototype in scope. Just fix the configuration. Do we have a working mmap? :-) Bruce From owner-freebsd-current Sun Mar 10 13:40:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21707 for current-outgoing; Sun, 10 Mar 1996 13:40:31 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21698 for ; Sun, 10 Mar 1996 13:40:25 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA05914 ; Sun, 10 Mar 1996 22:39:57 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA04680 ; Sun, 10 Mar 1996 22:39:56 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id WAA14950; Sun, 10 Mar 1996 22:15:41 +0100 (MET) From: Ollivier Robert Message-Id: <199603102115.WAA14950@keltia.freenix.fr> Subject: Re: Compat collection. To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Mar 1996 22:15:41 +0100 (MET) Cc: mark@grondar.za, current@Freebsd.ORG In-Reply-To: <199603101351.OAA01882@uriah.heep.sax.de> from J Wunsch at "Mar 10, 96 02:51:46 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1745 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@Freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that J Wunsch said: > binaries. Instead, i usually pick /usr/junklib for it, and ldconfig > this directory, too. Perhaps the hooks for this should go into the > base system, so a compatxx distribution can easily make use of it. Perhaps a /compat/freebsd as we've agreed on this for ibcs2 and linux ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Tue Feb 20 01:16:51 MET 1996 From owner-freebsd-current Sun Mar 10 14:08:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA23000 for current-outgoing; Sun, 10 Mar 1996 14:08:41 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA22991 for ; Sun, 10 Mar 1996 14:08:35 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA06088 ; Sun, 10 Mar 1996 23:08:32 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA04759 ; Sun, 10 Mar 1996 23:08:31 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id WAA15105; Sun, 10 Mar 1996 22:45:48 +0100 (MET) From: Ollivier Robert Message-Id: <199603102145.WAA15105@keltia.freenix.fr> Subject: Re: finger and 2.2-960303-SNAP To: adf@fl.net.au (Andrew Foster) Date: Sun, 10 Mar 1996 22:45:48 +0100 (MET) Cc: olah@cs.utwente.nl, current@FreeBSD.org In-Reply-To: <2.2.32.19960311162301.00a4bcf4@mail.fl.net.au> from Andrew Foster at "Mar 11, 96 06:23:01 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1745 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk It seems that Andrew Foster said: > And yet the old finger works fine, as does fingering from most other hosts > I've tried. Finger has been changed (or fixed :-)) to use T/TCP recently... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Tue Feb 20 01:16:51 MET 1996 From owner-freebsd-current Sun Mar 10 14:08:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA23017 for current-outgoing; Sun, 10 Mar 1996 14:08:48 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA22999 for ; Sun, 10 Mar 1996 14:08:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id NAA01141; Sun, 10 Mar 1996 13:53:23 -0800 (PST) To: se@ZPR.Uni-Koeln.DE (Stefan Esser) cc: Jim Lowe , current@FreeBSD.org Subject: Re: NCR disk controller, hp disk In-reply-to: Your message of "Sun, 10 Mar 1996 15:57:33 +0100." <199603101457.AA04448@Sisyphos> Date: Sun, 10 Mar 1996 13:53:23 -0800 Message-ID: <1139.826494803@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > This particular HP drive (the C3724S) is known > to cause problems with tagged commands. Please Any chance of adding this to a `rogues list', Stefan? Jordan From owner-freebsd-current Sun Mar 10 14:27:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA24297 for current-outgoing; Sun, 10 Mar 1996 14:27:32 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA24289 for ; Sun, 10 Mar 1996 14:27:25 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA11317; Sun, 10 Mar 1996 13:11:43 -0800 From: "Rodney W. Grimes" Message-Id: <199603102111.NAA11317@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: jehamby@lightside.com (Jake Hamby) Date: Sun, 10 Mar 1996 13:11:42 -0800 (PST) Cc: current@FreeBSD.ORG, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: from "Jake Hamby" at Mar 10, 96 10:56:24 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Sat, 9 Mar 1996, Rodney W. Grimes wrote: > > > > Can all three of you tell me if you have A80486DX4-100NV8T's or > > A80486DX4-100SV8B's? The difference is the SV8B is the write back > > enhanced DX4 and unless you have a motherboard that understands > > how to deal with this you are going to have a cache coherency problem > > between the internal and external cache. > > > > I have yet to see a MB deal with this correctly when faced with > > a bus master SCSI controller, though I have seen some that work fine > > as long as no bus mastering is occuring. Far more don't work than > > do work. > > > > If you don't have SV8B's or are not running them in WB mode, then > > I don't have any idea what has gone wrong... > > FYI, I have the 100NV8T, so I guess that's not the problem. Whew! Note > that the problem occurs with caches enabled OR disabled, I do have a bus > mastering SCSI controller (Adaptec 2842VLB), and someone has reported > that the problem occurs with the Intel DX2/66, so I guess AMD isn't the > common link after all. > > For future reference, are you saying that the SV8B AMD chips are to be > avoided, at least if busmastering SCSI controllers are involved? You don't have to avoid the SV8B chip, you just have to set the motherboard up so that the WB feature is defeated. This is most often done by setting the motherboard for an Intel DX4-100 CPU rather than an AMD DX4-100. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Mar 10 14:40:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25608 for current-outgoing; Sun, 10 Mar 1996 14:40:45 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA25601 for ; Sun, 10 Mar 1996 14:40:44 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id OAA13325; Sun, 10 Mar 1996 14:39:46 -0800 (PST) Message-Id: <199603102239.OAA13325@ref.tfs.com> Subject: Re: booting from sd5 when wd3 is also installed To: bde@zeta.org.au (Bruce Evans) Date: Sun, 10 Mar 1996 14:39:46 -0800 (PST) From: "JULIAN Elischer" Cc: current@freebsd.org In-Reply-To: <199603100915.UAA20728@godzilla.zeta.org.au> from "Bruce Evans" at Mar 10, 96 08:15:55 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > These changes should allow specifying the BIOS drive number independently > of the FreeBSD unit number. E.g., `9:sd(5,a)' describes the drive with > BIOS drive number 9 and sd unit number 5. Great stuff! I was thinking of doing similar but hadn't spent any time on it I anslo hadn't deided on a syntax... From owner-freebsd-current Sun Mar 10 14:46:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26099 for current-outgoing; Sun, 10 Mar 1996 14:46:10 -0800 (PST) Received: from gw1.att.com (gw1.att.com [192.20.239.133]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26090 for ; Sun, 10 Mar 1996 14:46:08 -0800 (PST) From: dob@clipper.cb.att.com Received: from clipper.cb.att.com by ig1.att.att.com id AA06092; Sun, 10 Mar 96 17:43:46 EST Received: from cbsky.cb.att.com by clipper.cb.att.com (4.1/EMS-1.1 SunOS) id AA06053; Sun, 10 Mar 96 17:46:02 EST Received: by cbsky.cb.att.com (5.x/EMS-1.1 client.cf 1/8/94 (SMI-4.1/SVR4)) id AA06637; Sun, 10 Mar 1996 17:46:01 -0500 Date: Sun, 10 Mar 1996 17:46:01 -0500 Message-Id: <9603102246.AA06637@cbsky.cb.att.com> To: current@freefall.freebsd.org, freebsd-current-digest@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: PANIC: vm_fork: u_map allocation failure Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've had one hard hang (press reset button) and one reboot (panic?, no dump, > sorry). Both while remaking world and fiddling with the modem (ppp on reboot > and minicom on hang). I've since setup to take dump if panic. > > This AM am redoing make world while having a memory pressure cooker running > (malloc bunch, touch bunch, free bunch). Added "find / -print" to workload mix. > Did get one error message on console/log when I logged in with all this mess > running: > > Mar 10 09:25:33 llama /kernel: vnode_pager_putpages: attempt to write meta-data!!! -- 0xffffffe9(ff) System paniced after a few hours. It was unattended so didn't get exact time. PANIC: vm_fork: u_map allocation failed. > If I get a dump will let you know. It said it was dumping, but it didn't seem to finish. Had to poke reset button to restart. Savecore didn't find a core file. Sorry. Hope this helps. Dan O'Brien Lucent Technologies (Bell Labs Innovations) From owner-freebsd-current Sun Mar 10 14:46:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26170 for current-outgoing; Sun, 10 Mar 1996 14:46:29 -0800 (PST) Received: from gw3.att.com (gw4.att.com [204.179.186.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26163 for ; Sun, 10 Mar 1996 14:46:27 -0800 (PST) From: dob@clipper.cb.att.com Received: from clipper.cb.att.com by ig4.att.att.com id AA07880; Sun, 10 Mar 96 17:38:34 EST Received: from cbsky.cb.att.com by clipper.cb.att.com (4.1/EMS-1.1 SunOS) id AA06053; Sun, 10 Mar 96 17:46:02 EST Received: by cbsky.cb.att.com (5.x/EMS-1.1 client.cf 1/8/94 (SMI-4.1/SVR4)) id AA06637; Sun, 10 Mar 1996 17:46:01 -0500 Date: Sun, 10 Mar 1996 17:46:01 -0500 Message-Id: <9603102246.AA06637@cbsky.cb.att.com> To: current@freefall.freebsd.org, freebsd-current-digest@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: PANIC: vm_fork: u_map allocation failure Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've had one hard hang (press reset button) and one reboot (panic?, no dump, > sorry). Both while remaking world and fiddling with the modem (ppp on reboot > and minicom on hang). I've since setup to take dump if panic. > > This AM am redoing make world while having a memory pressure cooker running > (malloc bunch, touch bunch, free bunch). Added "find / -print" to workload mix. > Did get one error message on console/log when I logged in with all this mess > running: > > Mar 10 09:25:33 llama /kernel: vnode_pager_putpages: attempt to write meta-data!!! -- 0xffffffe9(ff) System paniced after a few hours. It was unattended so didn't get exact time. PANIC: vm_fork: u_map allocation failed. > If I get a dump will let you know. It said it was dumping, but it didn't seem to finish. Had to poke reset button to restart. Savecore didn't find a core file. Sorry. Hope this helps. Dan O'Brien Lucent Technologies (Bell Labs Innovations) From owner-freebsd-current Sun Mar 10 16:04:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01240 for current-outgoing; Sun, 10 Mar 1996 16:04:06 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA01151 for ; Sun, 10 Mar 1996 16:04:02 -0800 (PST) Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id QAA01860; Sun, 10 Mar 1996 16:03:45 -0800 (PST) Date: Sun, 10 Mar 1996 16:03:44 -0800 (PST) From: invalid opcode To: Frank Durda IV cc: freebsd-current@freebsd.org Subject: Re: New kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 9 Mar 1996, Frank Durda IV wrote: > It would be nice to avoid the use of the negative-sounding "FAIL" if > possible... How about PASSIVE instead of AGRESSIVE. == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Sun Mar 10 16:14:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01883 for current-outgoing; Sun, 10 Mar 1996 16:14:00 -0800 (PST) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA01878 for ; Sun, 10 Mar 1996 16:13:56 -0800 (PST) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA04281; Mon, 11 Mar 96 01:15:55 +0100 Date: Mon, 11 Mar 96 01:15:55 +0100 Message-Id: <9603110015.AA04281@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@freebsd.org Subject: COMCONSOLE: a patch and a problem X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I played with the boot blocks and I noticed that I was unable to boot from a serial console (keyboard unplugged). The patch below fixes a bug in boot.c/probe_keyboard.c (well, at least on my machine:-). The problem now: when booting from a serial console, there is no timeout at the 'Boot:' prompt. Further investigations showed that the bios_tick function always returns the same value! Is this related to the fact that the keyboard is not plugged in? Jean-Marc Index: boot.c =================================================================== RCS file: /home/ncvs/src/sys/i386/boot/biosboot/boot.c,v retrieving revision 1.47 diff -u -r1.47 boot.c --- boot.c 1996/03/08 06:29:06 1.47 +++ boot.c 1996/03/10 23:50:15 @@ -76,7 +76,7 @@ int ret; #ifdef PROBE_KEYBOARD - if (probe_keyboard()) { + if (!probe_keyboard()) { init_serial(); loadflags |= RB_SERIAL; printf("\nNo keyboard found."); Index: probe_keyboard.c =================================================================== RCS file: /home/ncvs/src/sys/i386/boot/biosboot/probe_keyboard.c,v retrieving revision 1.6 diff -u -r1.6 probe_keyboard.c --- probe_keyboard.c 1996/03/08 06:29:07 1.6 +++ probe_keyboard.c 1996/03/10 23:50:36 @@ -114,7 +114,7 @@ #ifdef DEBUG printf("ok\n"); #endif - return(0); + return(1); } #endif /* PROBE_KEYBOARD */ _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Sun Mar 10 16:20:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA02493 for current-outgoing; Sun, 10 Mar 1996 16:20:35 -0800 (PST) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA02462 for ; Sun, 10 Mar 1996 16:20:27 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id AAA12545; Mon, 11 Mar 1996 00:19:56 GMT Date: Mon, 11 Mar 1996 00:19:56 GMT From: Adam David Message-Id: <199603110019.AAA12545@veda.is> To: rsanders@mindspring.COM Cc: freebsd-current@freebsd.org Subject: Re: ps and u_map allocation problems with kernel supped Mar 7 Newsgroups: list.freebsd.current References: X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >My root partition doesn't have space >for a kernel built with config -g right now, so I can't give much >more information. Keep a copy on a bigger filesystem and 'strip -d kernel' before installing. Works for me :) Adam From owner-freebsd-current Sun Mar 10 16:27:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA02993 for current-outgoing; Sun, 10 Mar 1996 16:27:42 -0800 (PST) Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA02983 for ; Sun, 10 Mar 1996 16:27:35 -0800 (PST) Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id SAA00399; Sun, 10 Mar 1996 18:27:17 -0600 (CST) Message-Id: <199603110027.SAA00399@mpp.minn.net> Subject: Re: vm/kern_lock.c:lock_read hang ? To: mrl@teleport.com (Mostyn/Annabella) Date: Sun, 10 Mar 1996 18:27:17 -0600 (CST) From: "Mike Pritchard" Cc: current@Freebsd.ORG, mrl@teleport.com In-Reply-To: <199603101751.JAA23037@linda.teleport.com> from "Mostyn/Annabella" at Mar 10, 96 09:51:05 am X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@Freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk Mostyn/Annabella wrote: > > Hi, > My occaisional ppp (kernel) hangs seem to boil down to processes > sleeping at the tsleep(l, PVM, "lockrd", 0); statement in > lock_read in vm/kern_lock.c. > Any attempt to do anything at this point permanently hangs the > machine. > > Another way to create an instant panic is to go into ddb > (cntl/alt/esc) and type - > > show map > > which goes off to vm_map_print and panics. > > > This with a kernel from March 3rd. Try adding "-bsdcomp" to your /etc/ppp/options file and see if the problem goes away. Something in that code seems to trash the swaplist and who knows what else. I've been unable to track down exactly what in that code is causing the kernel memory corruption. -- Mike Pritchard mpp@minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Sun Mar 10 16:37:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA03745 for current-outgoing; Sun, 10 Mar 1996 16:37:06 -0800 (PST) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA03740 for ; Sun, 10 Mar 1996 16:36:57 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id AAA12661; Mon, 11 Mar 1996 00:35:51 GMT Date: Mon, 11 Mar 1996 00:35:51 GMT From: Adam David Message-Id: <199603110035.AAA12661@veda.is> To: rgrimes@GndRsh.aac.DEv.COM Cc: freebsd-current@freebsd.org Subject: Re: changes to /etc/ttys Newsgroups: list.freebsd.current References: <199603071710.JAA07682@GndRsh.aac.dev.com> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I'm submitting a patch for /etc/ttys to make ttyv0 the default console of >> which no getty process runs on. ttyv[1-3] are now the default getty logins. >Why would you want to do this? This would mean that by default no login >prompt would appear after a boot, something that I am sure would generate >_lots_ of questions on the mailing list from users who did not know about >it. There used to be a syscons utility to change between virtual consoles. This functionality seems to no longer exist in vidcontrol or kbdcontrol, though there might some magic sequence that can be echoed to produce the same result (nope, not found that either). Well... there are ioctl's that can be used to change virtual consoles, so such a utility could be written or incorporated into vidcontrol, and somehow invoked immediately after entering multiuser mode. What is the normal method of invoking a command immediately after /etc/rc has finished executing? >What gain is there from doing this? output-only console, but then keyboard input would have to be prevented altogether, which is not currently done in this case. -- Adam David From owner-freebsd-current Sun Mar 10 16:47:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA04527 for current-outgoing; Sun, 10 Mar 1996 16:47:02 -0800 (PST) Received: from s1.GANet.NET (s1.GANet.NET [199.18.201.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA04521 for ; Sun, 10 Mar 1996 16:46:58 -0800 (PST) Received: (from ec0@localhost) by s1.GANet.NET (8.6.11/8.6.11) id TAA05160; Sun, 10 Mar 1996 19:45:48 -0500 Date: Sun, 10 Mar 1996 19:45:48 -0500 (EST) From: Eric Chet To: freebsd-current@freebsd.org Subject: -current /proc mount failure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello make world and kernel build on current 3-10-96, mount of /proc fails at system boot. This is the error: mount: /proc: Special device file and mount point may not be the same root has: dr-xr-xr-x 2 root wheel 512 Mar 10 18:54 proc /etc/fstab has: proc /proc procfs rw 0 0 mount.c did change saturday night, anybody else see this? Peace, Eric J. Chet (ejc@nasvr1.cb.att.com || ec0@ganet.net) Lucent Technologies, Bell Labs Innovations Columbus, Ohio RM 1E222 From owner-freebsd-current Sun Mar 10 16:53:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA05037 for current-outgoing; Sun, 10 Mar 1996 16:53:29 -0800 (PST) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA05029 for ; Sun, 10 Mar 1996 16:53:20 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id AAA12708; Mon, 11 Mar 1996 00:52:31 GMT Date: Mon, 11 Mar 1996 00:52:31 GMT From: Adam David Message-Id: <199603110052.AAA12708@veda.is> To: mark@grondar.ZA Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... Newsgroups: list.freebsd.current References: <199603091505.RAA17462@grumble.grondar.za> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have just committed a change to su(1) to better integrate Kerberos >into it. BUT, this missive does not apply only to those of you with >Kerberos/eBones. >The result of this change is that a user will not be prompted for >a password again if they get the Kerberos password wrong. ubiq [1] % su su: kerberos: not in root's ACL. ubiq [2] % It used to prompt for a normal password and work. This is for all su to group 0. Okay, kerberos is installed but not configured... but shouldn't this work? -- Adam David From owner-freebsd-current Sun Mar 10 17:21:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06644 for current-outgoing; Sun, 10 Mar 1996 17:21:02 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA06639 for ; Sun, 10 Mar 1996 17:20:59 -0800 (PST) Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id RAA02080; Sun, 10 Mar 1996 17:18:38 -0800 (PST) Date: Sun, 10 Mar 1996 17:18:35 -0800 (PST) From: invalid opcode To: Frank Durda IV , freebsd-current@freebsd.org Subject: Re: New kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Mar 1996, invalid opcode wrote: > How about PASSIVE instead of AGRESSIVE. > == Chris Layne ============================================================= How about ASSERTIVE? kernel: Would it be okay if I panic'ed now? (y/n) == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Sun Mar 10 17:29:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07266 for current-outgoing; Sun, 10 Mar 1996 17:29:01 -0800 (PST) Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA07257 for ; Sun, 10 Mar 1996 17:28:57 -0800 (PST) Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.12/8.6.9) with ESMTP id RAA14561; Sun, 10 Mar 1996 17:28:53 -0800 From: Mostyn/Annabella Received: (mrl@localhost) by linda.teleport.com (8.6.12/8.6.12) id RAA22856; Sun, 10 Mar 1996 17:28:53 -0800 Message-Id: <199603110128.RAA22856@linda.teleport.com> Subject: Today's -current + cd9660 To: current@freebsd.org Date: Sun, 10 Mar 1996 17:28:53 -0800 (PST) Cc: mrl@teleport.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All, It's alreadi been reported that cd9660_readdir panics at 0x1a7 with a movzbl 0(%ecx),%esi - well it still does - and examining the code points to the line isoflags = isonum_711(imp->iso_ftype == ISO_FTYPE_HIGH_SIERRA? &ep->date[6]: ep->flags); In that routine - it seems that the dereference of ep causes the panic. Seems the system buffer is not mapped?! Mostyn From owner-freebsd-current Sun Mar 10 17:38:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07764 for current-outgoing; Sun, 10 Mar 1996 17:38:23 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07758 for current; Sun, 10 Mar 1996 17:38:21 -0800 (PST) Date: Sun, 10 Mar 1996 17:38:21 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199603110138.RAA07758@freefall.freebsd.org> To: current Subject: secure/lib/libtelnet/Makefile Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What's this stuff? #ifdef ENCRYPTION ... #endif Somebody forget they were hacking a Makefile and drop accidently into C mode or something? :-) Actually, generally speaking, this Makefile is a royal mess and there's probably more commented out at this point in there than there is actual contents. :-) Jordan From owner-freebsd-current Sun Mar 10 17:39:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07844 for current-outgoing; Sun, 10 Mar 1996 17:39:39 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07833 for current; Sun, 10 Mar 1996 17:39:37 -0800 (PST) Date: Sun, 10 Mar 1996 17:39:37 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199603110139.RAA07833@freefall.freebsd.org> To: current Subject: Oh yeah, also.. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Current make world falls over in secure/lib/libtelnet (which is why I was looking at the Makefile at all) with an odd error: root@time-> make building shared telnet library (version 2.0) tsort: cycle in data tsort: encrypt.so tsort: enc_des.so tsort: cycle in data tsort: misc.so tsort: auth.so tsort: kerberos.so tsort: cycle in data tsort: misc.so tsort: auth.so ld: -d option takes 'c' or 'p' argument *** Error code 1 Jordan From owner-freebsd-current Sun Mar 10 17:41:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07923 for current-outgoing; Sun, 10 Mar 1996 17:41:44 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07917 for current; Sun, 10 Mar 1996 17:41:43 -0800 (PST) Date: Sun, 10 Mar 1996 17:41:43 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199603110141.RAA07917@freefall.freebsd.org> To: current Subject: whoops, never mind on src/secure/lib/libtelnet/Makefile error.. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, it's still a mess but I just saw the problem with the error with ld (I must have missed it on the first pass). It's a -des spec instead of -ldes, and it looks like Joerg already fixed it (I guess I need to sup again). Jordan From owner-freebsd-current Sun Mar 10 18:30:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11944 for current-outgoing; Sun, 10 Mar 1996 18:30:04 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA11912 for ; Sun, 10 Mar 1996 18:29:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id SAA22541; Sun, 10 Mar 1996 18:28:23 -0800 (PST) To: invalid opcode cc: Frank Durda IV , freebsd-current@Freebsd.ORG Subject: Re: New kernel In-reply-to: Your message of "Sun, 10 Mar 1996 17:18:35 PST." Date: Sun, 10 Mar 1996 18:28:23 -0800 Message-ID: <22539.826511303@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@Freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 10 Mar 1996, invalid opcode wrote: > > > How about PASSIVE instead of AGRESSIVE. > > == Chris Layne ============================================================ = > > How about ASSERTIVE? > > kernel: Would it be okay if I panic'ed now? (y/n) How about PASSIVE_AGGRESSIVE? The kernel doesn't actually panic, but corrupts your files occasionally when you're away on vacation. :-) Jordan From owner-freebsd-current Sun Mar 10 18:43:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA13363 for current-outgoing; Sun, 10 Mar 1996 18:43:30 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA13341 for ; Sun, 10 Mar 1996 18:43:28 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id SAA26063 for ; Sun, 10 Mar 1996 18:43:27 -0800 Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id SAA15872; Sun, 10 Mar 1996 18:42:18 -0800 Message-Id: <199603110242.SAA15872@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Eric Chet cc: freebsd-current@freebsd.org Subject: Re: -current /proc mount failure In-reply-to: Your message of "Sun, 10 Mar 1996 19:45:48 EST." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 10 Mar 1996 18:42:18 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > make world and kernel build on current 3-10-96, mount of /proc >fails at system boot. This is the error: > >mount: /proc: Special device file and mount point may not be the same > >root has: >dr-xr-xr-x 2 root wheel 512 Mar 10 18:54 proc > >/etc/fstab has: >proc /proc procfs rw 0 0 > >mount.c did change saturday night, anybody else see this? It's been fixed. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Mar 10 18:44:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA13671 for current-outgoing; Sun, 10 Mar 1996 18:44:20 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA13659 for ; Sun, 10 Mar 1996 18:44:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id SAA15891; Sun, 10 Mar 1996 18:44:33 -0800 Message-Id: <199603110244.SAA15891@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Mostyn/Annabella cc: current@freebsd.org Subject: Re: Today's -current + cd9660 In-reply-to: Your message of "Sun, 10 Mar 1996 17:28:53 PST." <199603110128.RAA22856@linda.teleport.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 10 Mar 1996 18:44:33 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi All, >It's alreadi been reported that cd9660_readdir panics at 0x1a7 with >a movzbl 0(%ecx),%esi - well it still does - and examining the code >points to the line > >isoflags = isonum_711(imp->iso_ftype == ISO_FTYPE_HIGH_SIERRA? > &ep->date[6]: ep->flags); > >In that routine - it seems that the dereference of ep causes the >panic. Seems the system buffer is not mapped?! Bruce's fix for this is attached. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project Date: Fri, 8 Mar 1996 06:53:48 +1100 From: Bruce Evans >I can reliably reproduce a "Fatal trap 12: page fault while in kernel >mode" in a current kernel (up to date as of a few hours ago). I reproduce >it by mounting the FreeBSD 2.1 "live file system" CD and doing some file >name completion in the Xlib source tree (using bash), e.g. > $ more /cdrom/usr/X11R6/src/xc/lib/X11/ >The fault address on one instance was 0xf08aa001, and the fault code is >"supervisor read, page not present". The instruction pointer is at: > _cd9660_readdir+0x1a7: movzbl 0(%ecx),%esi >%ecx is the fault address. This is easy to reproduce and seems to be a bug in cd9660_readdir(). An invalid directory entry is accessed one statment before the check that finds it to be invalid. My fix delays the access and some other access until the reclen and namlen checks are done. Apparently it is OK to access the parts of the directory entry containing the reclen and the namlen, although there is no such thing as a partial struct in C. Skipping the faulting instructing in ddb happens to work safely. For some reason the bug wasn't reproducible after that (even after switching to another cdrom and back). Bruce *** cd9660_vnops.c~ Mon Dec 4 15:44:02 1995 --- cd9660_vnops.c Fri Mar 8 05:54:13 1996 *************** *** 559,562 **** --- 559,563 ---- struct iso_directory_record *ep; u_short elen; + int namlen; int reclen; int isoflags; *************** *** 620,625 **** reclen = isonum_711 (ep->length); - isoflags = isonum_711(imp->iso_ftype == ISO_FTYPE_HIGH_SIERRA? - &ep->date[6]: ep->flags); if (reclen == 0) { /* skip to next block, if any */ --- 621,624 ---- *************** *** 641,648 **** } /* XXX: be more intelligent if we can */ idp->current.d_type = DT_UNKNOWN; ! idp->current.d_namlen = isonum_711 (ep->name_len); if (isoflags & 2) isodirino(&idp->current.d_fileno,ep,imp); --- 640,656 ---- } + namlen = isonum_711 (ep->name_len); + if (reclen < ISO_DIRECTORY_RECORD_SIZE + namlen) { + error = EINVAL; + /* illegal entry, stop */ + break; + } + /* XXX: be more intelligent if we can */ idp->current.d_type = DT_UNKNOWN; ! idp->current.d_namlen = namlen; ! isoflags = isonum_711(imp->iso_ftype == ISO_FTYPE_HIGH_SIERRA? ! &ep->date[6]: ep->flags); if (isoflags & 2) isodirino(&idp->current.d_fileno,ep,imp); *************** *** 650,659 **** idp->current.d_fileno = dbtob(bp->b_blkno) + idp->curroff; - - if (reclen < ISO_DIRECTORY_RECORD_SIZE + idp->current.d_namlen) { - error = EINVAL; - /* illegal entry, stop */ - break; - } idp->curroff += reclen; --- 658,661 ---- From owner-freebsd-current Sun Mar 10 19:28:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA18847 for current-outgoing; Sun, 10 Mar 1996 19:28:36 -0800 (PST) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA18749 Sun, 10 Mar 1996 19:28:06 -0800 (PST) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <02216-0@bunyip.cc.uq.oz.au>; Mon, 11 Mar 1996 13:26:51 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id MAA17689; Mon, 11 Mar 1996 12:25:23 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id CAA17562; Mon, 11 Mar 1996 02:29:34 GMT Message-Id: <199603110229.CAA17562@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org, bugs@freebsd.org Subject: ffs_valloc: et cetera. X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Mar 1996 12:29:34 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just found out what fs these panics are occurring in - /tmp. That's mounted using the memfs stuff..... Stephen -- I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Sun Mar 10 20:31:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA24476 for current-outgoing; Sun, 10 Mar 1996 20:31:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA24471 for ; Sun, 10 Mar 1996 20:31:21 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id UAA26597 for ; Sun, 10 Mar 1996 20:31:19 -0800 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id PAA14846; Mon, 11 Mar 1996 15:14:35 +1100 From: michael butler Message-Id: <199603110414.PAA14846@asstdc.scgt.oz.au> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: terry@lambert.org (Terry Lambert) Date: Mon, 11 Mar 1996 15:14:35 +1100 (EST) Cc: current@freebsd.org In-Reply-To: <199603101921.MAA01621@phaeton.artisoft.com> from "Terry Lambert" at Mar 10, 96 12:21:10 pm X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > I note that through a number of drivers there is mention of > > cache-invalidation instructions (software-style) but none of them seem > > to implement anything of this nature. Is there a problem with doing this > > .. that is .. to invalidate the page(s) into which data has just been > > transferred prior to the application being told that the transfer > > completed? No other cases need to be considered do they ? > OK. This is an interesting topic. 8-(. :-) > Before, when I suggested that a DMA be triggered as part of a probe > process on a per controller basis to determine if bounce buffers > were necessary, I neglected the non-working cache case. The cache > cases need to be considered at the same time because they need to > trigger similar controller/memory events in order to be detectable. This was actually what I was hinting at .. it is as difficult to establish if a controller/mother-board combination will perform reliable IDE multi-block transfers or direct DMA above 16 meg. For those cases, the default configuration takes the "safe" option .. in the former case, we don't attempt multi-block transfers and, in the latter, "bounce-buffers" are enabled in the GENERIC kernel (with some special cases dealt with in the relevant driver, e.g. BT445S). My idea was that we assume the hardware is broken and it is up to the owner of the box to decide when (or if) to test the potentially "optimal" case. > When a bus master DMA occurs, there is supposed to be a cache > notification, and the L1 and L2 cache lines are supposed to be > invalidated or written back for the memory range in which the DMA > took place. Ah .. one case I forgot .. write-back has to occur prior to the DMA being initiated in the "write" transaction .. oops :-( > It isn't worthwhile to BINVD in the majority of cases, because the > majority is people with functional cache hardware. Admittedly, we > have self-selected this by not "fixing" the problem in software for > people without the good hardware. The number of people who are likely to buy "write-back" CPUs because they are led to believe by some over-enthusiastic sales-droid that there is something to be gained will probably increase. I'm (conceptually) looking to assist them in making the default case work. > A decent fix would require a lot of effort and a lot of hooks to make > it work in all cases (for instance, I could have two VLB controllers, > one in a "master" slot, one not; the fix has to have a per controller > granularity, etc.). 8-(. My proposed default of assuming brain-damage would work in this case although sub-optimally. If they change it and it breaks, the fix is obvious and it (should) be apparent that whatever they changed broke it, i.e. it was not FreeBSD's fault that their hardware isn't up to standard. As I think we're all aware, perception is far more powerful than technical excellence if you're looking for market-share .. some large PC software companies continue to prove that daily :-(. Working sub-optimally is better than not at all, michael From owner-freebsd-current Sun Mar 10 20:37:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA25289 for current-outgoing; Sun, 10 Mar 1996 20:37:30 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA25282 for ; Sun, 10 Mar 1996 20:37:28 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tvytT-00084lC; Sun, 10 Mar 96 22:07 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tvymL-000BzmC; Sun, 10 Mar 96 22:00 WET Message-Id: Date: Sun, 10 Mar 96 22:00 WET To: freebsd-current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sun Mar 10 1996, 22:00:12 CST Subject: Re: New kernel Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [3]How about PASSIVE_AGGRESSIVE? The kernel doesn't actually panic, but [3]corrupts your files occasionally when you're away on vacation. :-) [3] [3] Jordan I must have that option set on this 2.1 system. Came back and there is no boot block and no partition table. Very messy. I guess you could call it "SAFEMODE". Narf, too Windows '95ish. Ok, how about "SAFECONFIG" or "PLAINCONFIG"? Frank Durda IV |"If you let it go out of focus, or uhclem%nemesis@rwsystr.nkn.net | it will become clearer." |- Tandy R&D Software Director or ...letni!rwsys!nemesis!uhclem | From owner-freebsd-current Sun Mar 10 21:17:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA28982 for current-outgoing; Sun, 10 Mar 1996 21:17:02 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA28967 for ; Sun, 10 Mar 1996 21:16:55 -0800 (PST) Received: from tiger.fl.net.au (adf@tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id PAA05448 for ; Mon, 11 Mar 1996 15:19:47 +1000 (EST) Message-Id: <2.2.32.19960312021527.009da1ac@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Mar 1996 16:15:27 -1000 To: current@freebsd.org From: Andrew Foster Subject: Rebooting with 2.1.0R and SNAP Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've put the 2.2-960303-SNAP on my old 2.1.0R machine and I still get reboots (2 so far today). On another machine here (DX4-100) the SNAP has been up since I booted with it 1 day 5:50 ago. The machine in question is : Pentium 90 Triton Chipset Motherboard 2x16 MB 60ns SIMMS NCR PCI Controller (810) 4GB Seagate Hawk SCSI Drive 1080MB Quantum Fireball SCSI Drive 1080MB IBM SCSI Drive External tape drive (Wangdat) And recently a 1.2Gb Maxtor EIDE (added in the last few days - has no bearing AFAICS) This machine randomly reboots. There is nothing unusual in the logs. E.g. : Mar 11 11:40:03 cafu named[251]: reloading nameserver Mar 11 11:40:03 cafu named[251]: Ready to answer queries. Mar 11 11:42:32 cafu login: login from annex1 as toyota Mar 11 11:44:43 cafu nntplink[334]: merki.connect.com.au stats 250 offered 0 ac Mar 11 11:44:43 cafu nntplink[334]: merki.connect.com.au xmit user 0.1 system 0 Mar 11 11:44:51 cafu nntplink[335]: warrane.connect.com.au stats 250 offered 0 Mar 11 11:44:51 cafu nntplink[335]: warrane.connect.com.au xmit user 0.1 system Mar 11 11:45:04 cafu innd: merki.connect.com.au:15 checkpoint seconds 409 accep Mar 11 11:46:56 cafu innd: merki.connect.com.au:15 closed seconds 521 accepted Mar 11 11:46:56 cafu innd: merki.connect.com.au connected 15 Mar 11 11:56:16 cafu /kernel: FreeBSD 2.2-960303-SNAP #0: Sun Mar 10 18:17:37 Mar 11 11:56:16 cafu /kernel: adf@cafu.fl.net.au:/mnt/sec/ter1/usr/src/sys/ Mar 11 11:56:16 cafu /kernel: CPU: Pentium (90.19-MHz 586-class CPU) Here is my dmesg now : FreeBSD 2.2-960303-SNAP #0: Sun Mar 10 18:17:37 1996 adf@cafu.fl.net.au:/mnt/sec/ter1/usr/src/sys/compile/IMP CPU: Pentium (90.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping=4 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30646272 (29928K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7 piix0 rev 2 on pci0:7 ncr0 rev 2 int a irq 10 on pci0:10 (ncr0:0:0): "QUANTUM FIREBALL1080S 1Q08" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1042MB (2134305 512 byte sectors) (ncr0:1:0): "SEAGATE ST15230N 0298" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 4095MB (8386733 512 byte sectors) (ncr0:2:0): "IBM DPES-31080 S31Q" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1034MB (2118144 512 byte sectors) (ncr0:4:0): "WANGTEK 6130-HS 4W17" type 1 removable SCSI 2 st0(ncr0:4:0): Sequential-Access st0(ncr0:4:0): 275ns (4 Mb/sec) offset 8. density code 0x13, drive empty Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 at 0x300-0x31f irq 5 on isa ed1: address 00:00:01:06:49:18, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface changing root device to sd0a WARNING: / was not properly dismounted. in_rtqtimo: adjusted rtq_reallyold to 2400 in_rtqtimo: adjusted rtq_reallyold to 1600 in_rtqtimo: adjusted rtq_reallyold to 1066 in_rtqtimo: adjusted rtq_reallyold to 710 Uptime : 4:14PM up 4:25, 5 users, load averages: 0.05, 0.18, 0.19 I hope this can help in trying to solve this problem. The machine is running (at the moment) : Apache 1.0.2 INND Harvest Cache (added recently ... had problem before that) Sendmail 8.7.4 All the usual ISP things ... I've got around 30 aliases on my ed1 if this matters at all. ps aux at the moment shows : USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND news 289 4.3 4.9 5108 1484 ?? Ds 11:56AM 7:24.16 /usr/local/news/etc/innd -p4 -r -i0 root 1 0.0 0.3 364 72 ?? Is 11:49AM 0:00.30 /sbin/init -- root 2 0.0 0.1 0 12 ?? DL 11:49AM 0:38.97 (pagedaemon) root 3 0.0 0.1 0 12 ?? RL 11:49AM 0:53.32 (vmdaemon) root 4 0.0 0.1 0 12 ?? DL 11:49AM 0:16.81 (update) root 67 0.0 0.6 192 188 ?? Ss 11:56AM 0:08.84 syslogd daemon 73 0.0 0.1 176 20 ?? Is 11:56AM 0:00.01 portmap root 80 0.0 0.1 460 16 ?? Is 11:56AM 0:00.01 mountd root 82 0.0 0.1 240 16 ?? Is 11:56AM 0:00.01 nfsd-master master ter (nfsd) root 84 0.0 0.1 232 16 ?? I 11:56AM 0:00.00 nfsd-srv srv (nfsd) root 85 0.0 0.1 232 16 ?? I 11:56AM 0:00.00 nfsd-srv srv (nfsd) root 86 0.0 0.1 232 16 ?? I 11:56AM 0:00.00 nfsd-srv srv (nfsd) root 87 0.0 0.1 232 16 ?? I 11:56AM 0:00.00 nfsd-srv srv (nfsd) root 91 0.0 0.1 224 16 ?? S 11:56AM 0:10.18 nfsiod -n 4 root 93 0.0 0.1 224 12 ?? S 11:56AM 0:05.64 nfsiod -n 4 root 94 0.0 0.1 224 12 ?? S 11:56AM 0:03.22 nfsiod -n 4 root 95 0.0 0.1 224 12 ?? S 11:56AM 0:02.89 nfsiod -n 4 root 99 0.0 0.3 196 96 ?? Is 11:56AM 0:00.93 inetd root 204 0.0 0.6 248 168 ?? Ss 11:56AM 0:05.51 cron root 206 0.0 0.1 196 20 ?? Is 11:56AM 0:00.04 lpd root 209 0.0 0.6 492 164 ?? Is 11:56AM 0:00.63 sendmail: accepting connections (sendmail) root 250 0.0 2.7 984 816 ?? Ss 11:56AM 0:38.72 named root 252 0.0 0.3 400 80 ?? Ss 11:56AM 0:06.01 /usr/local/etc/httpd/httpd root 259 0.0 0.3 348 80 ?? Ss 11:56AM 0:05.73 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 261 0.0 0.1 504 20 ?? I 11:56AM 0:00.11 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 262 0.0 0.1 504 20 ?? I 11:56AM 0:00.11 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 263 0.0 0.1 504 20 ?? I 11:56AM 0:00.12 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 264 0.0 0.1 504 20 ?? I 11:56AM 0:00.12 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 265 0.0 0.1 504 20 ?? I 11:56AM 0:00.12 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con root 290 0.0 0.1 480 36 ??- I 11:56AM 0:00.00 /bin/sh /usr/local/news/etc/rc.news root 292 0.0 0.7 504 208 ??- I 11:56AM 0:16.19 /bin/sh /usr/local/news/bin/innwatch root 322 0.0 0.1 264 20 ?? I 11:56AM 0:00.01 /usr/src/annex/erpcd root 323 0.0 1.0 624 308 ??- I 11:56AM 0:08.22 /usr/bin/perl /sbin/idle.pl root 325 0.0 0.8 224 248 ??- S 11:56AM 0:55.17 ./tmlim3_288 root 326 0.0 0.8 224 236 ??- S 11:56AM 0:35.88 ./tmlim3_144 cached 329 0.0 0.1 460 16 ??- I 11:56AM 0:00.14 /bin/csh -f /usr/local/harvest/bin/RunCache news 331 0.0 1.0 280 296 ?? S 11:56AM 0:04.01 /usr/local/news/bin/nntplink -q -k merki.connect.com.au news 332 0.0 1.0 284 296 ?? S 11:56AM 0:03.73 /usr/local/news/bin/nntplink -q -k warrane.connect.com.au root 340 0.0 0.1 156 20 v0 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv0 root 341 0.0 0.1 156 20 v1 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv1 root 342 0.0 0.1 156 20 v2 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv2 root 343 0.0 0.1 156 20 v3 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv3 root 344 0.0 0.1 156 20 v4 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv4 root 345 0.0 0.1 156 20 v5 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv5 root 346 0.0 0.1 156 20 v6 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv6 root 347 0.0 0.1 156 20 v7 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv7 root 348 0.0 0.1 156 20 v8 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv8 root 349 0.0 0.1 156 20 v9 Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyv9 root 350 0.0 0.1 156 20 va Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyva root 351 0.0 0.1 156 20 vb Is+ 11:56AM 0:00.02 /usr/libexec/getty Pc ttyvb cached 370 0.0 3.6 9892 1092 ?? S 11:56AM 1:08.60 cached -s -f /usr/local/harvest/lib/cached.conf cached 371 0.0 0.4 168 120 ?? I 11:56AM 0:00.13 (dnsserver) -p dns/dns370.0 (dnsserver) cached 372 0.0 0.8 168 232 ?? I 11:56AM 0:00.13 (dnsserver) -p dns/dns370.1 (dnsserver) cached 373 0.0 0.4 180 120 ?? I 11:56AM 0:00.13 (dnsserver) -p dns/dns370.2 (dnsserver) cached 374 0.0 0.4 168 120 ?? I 11:56AM 0:00.12 (dnsserver) -p dns/dns370.3 (dnsserver) cached 375 0.0 0.4 180 120 ?? I 11:56AM 0:00.12 (dnsserver) -p dns/dns370.4 (dnsserver) cached 376 0.0 0.4 180 120 ?? I 11:56AM 0:00.13 (dnsserver) -p dns/dns370.5 (dnsserver) cached 377 0.0 0.4 168 120 ?? I 11:56AM 0:00.12 (dnsserver) -p dns/dns370.6 (dnsserver) cached 378 0.0 0.5 180 160 ?? I 11:56AM 0:00.14 (dnsserver) -p dns/dns370.7 (dnsserver) cached 379 0.0 0.5 180 132 ?? I 11:56AM 0:00.13 (dnsserver) -p dns/dns370.8 (dnsserver) cached 380 0.0 0.4 180 120 ?? I 11:56AM 0:00.12 (dnsserver) -p dns/dns370.9 (dnsserver) root 5027 0.0 0.1 516 20 ?? I 12:16PM 0:00.09 /usr/local/etc/httpd/admin/httpd -f /usr/local/etc/httpd/admin/con news 9011 0.0 0.1 788 20 ?? I 2:46PM 0:00.97 -pbaldock.fl.net.au ARTICLE root 12294 0.0 0.2 220 68 ?? Is 3:01PM 0:00.94 telnetd hl 12295 0.0 1.0 688 288 p2 Is+ 3:01PM 0:00.63 -bash (bash) root 15408 0.0 0.2 228 68 ?? Ss 3:19PM 0:01.43 telnetd robroy 15439 0.0 0.1 684 20 p1 Is 3:19PM 0:00.70 -bash (bash) nobody 18577 0.0 1.1 588 332 ?? I 3:38PM 0:00.15 /usr/local/etc/httpd/httpd nobody 18579 0.0 1.1 452 344 ?? I 3:38PM 0:00.12 /usr/local/etc/httpd/httpd hl 19938 0.0 0.1 1064 20 p2 T 3:46PM 0:00.14 rtin news 19939 0.0 0.1 760 20 ?? I 3:46PM 0:00.29 -cafu.fl.net.au list root 21201 0.0 0.2 204 44 ?? Is 3:52PM 0:00.14 rlogind genes 21202 0.0 1.3 652 384 p0 Is+ 3:52PM 0:00.37 -bash (bash) robroy 21982 0.0 2.2 3336 664 p1 S+ 3:57PM 0:04.87 rtin news 21995 0.0 0.7 796 220 ?? S 3:57PM 0:03.13 -cafu.fl.net.au article nobody 22005 0.0 1.2 472 364 ?? I 3:57PM 0:00.11 /usr/local/etc/httpd/httpd root 22006 0.0 0.2 216 68 ?? Is 3:57PM 0:00.74 telnetd nobody 22008 0.0 1.1 588 324 ?? I 3:57PM 0:00.08 /usr/local/etc/httpd/httpd mr_ed 22009 0.0 1.3 680 392 p3 Is 3:57PM 0:00.26 -bash (bash) mr_ed 22022 0.0 1.0 700 300 ?? Ss 3:57PM 0:00.83 -mr_ed.fl.net.au: mr_ed: IDLE nobody 22105 0.0 1.2 588 348 ?? I 3:57PM 0:00.07 /usr/local/etc/httpd/httpd nobody 22108 0.0 1.2 588 348 ?? I 3:57PM 0:00.08 /usr/local/etc/httpd/httpd nobody 22109 0.0 1.3 588 388 ?? I 3:57PM 0:00.07 /usr/local/etc/httpd/httpd root 22220 0.0 1.0 220 304 ?? Ss 3:58PM 0:01.70 timestat cached 22629 0.0 1.0 508 312 ?? S 4:01PM 0:00.11 ftpget -t 900 -htmlify - 204.101.252.29 pub/thunder/tbavw700.zip I root 23534 0.0 1.2 216 360 ?? Ss 4:05PM 0:00.42 telnetd adf 23535 0.0 2.1 684 632 p4 Is 4:05PM 0:00.25 -bash (bash) news 23921 0.0 2.2 780 680 ?? I 4:07PM 0:03.90 -glasses.fl.net.au GROUP mr_ed 24174 0.0 3.4 3204 1024 p3 I+ 4:09PM 0:04.32 rtin news 24175 0.0 1.6 784 480 ?? I 4:09PM 0:05.03 -cafu.fl.net.au article root 24826 0.0 0.2 212 64 ?? I 4:11PM 0:00.01 sleep 600 root 25228 0.0 2.8 680 864 p4 S 4:14PM 0:00.19 su (bash) root 25271 0.0 1.4 144 428 ?? Ss 4:14PM 0:00.02 comsat news 25519 0.7 3.3 816 1020 ?? S 4:15PM 0:00.25 -patheon.fl.net.au GROUP root 0 0.0 0.0 0 0 ?? DLs 11:49AM 0:00.22 (swapper) root 25574 0.0 1.0 480 304 p4 R+ 4:16PM 0:00.01 ps -auxw I look forward to any suggestions. Thanks, Andrew Foster First Link Internet Services. ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Sun Mar 10 21:28:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA29596 for current-outgoing; Sun, 10 Mar 1996 21:28:05 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA29529 Sun, 10 Mar 1996 21:27:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id VAA16142; Sun, 10 Mar 1996 21:28:03 -0800 Message-Id: <199603110528.VAA16142@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Stephen Hocking cc: current@freebsd.org, bugs@freebsd.org Subject: Re: ffs_valloc: et cetera. In-reply-to: Your message of "Mon, 11 Mar 1996 12:29:34 +1000." <199603110229.CAA17562@netfl15a.devetir.qld.gov.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 10 Mar 1996 21:28:03 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just found out what fs these panics are occurring in - /tmp. That's mounted >using the memfs stuff..... Hmmm..."that" problem again. Yeah, we've seen this before - it's what caused a lot of people to stop using MFS. The current theory is that it happens when you run out of space...but that's not been proven. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Mar 10 21:59:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA02234 for current-outgoing; Sun, 10 Mar 1996 21:59:36 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA02219 for ; Sun, 10 Mar 1996 21:59:26 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id HAA01535; Mon, 11 Mar 1996 07:58:39 +0200 (SAT) Message-Id: <199603110558.HAA01535@grumble.grondar.za> To: Adam David cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... Date: Mon, 11 Mar 1996 07:58:39 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adam David wrote: > >I have just committed a change to su(1) to better integrate Kerberos > >into it. BUT, this missive does not apply only to those of you with > >Kerberos/eBones. > > >The result of this change is that a user will not be prompted for > >a password again if they get the Kerberos password wrong. > > ubiq [1] % su > su: kerberos: not in root's ACL. > ubiq [2] % > > It used to prompt for a normal password and work. This is for all su to group 0. > Okay, kerberos is installed but not configured... but shouldn't this work? No. tell it not to use kerberos with `su -K'. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 22:22:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA05069 for current-outgoing; Sun, 10 Mar 1996 22:22:34 -0800 (PST) Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA05059 Sun, 10 Mar 1996 22:22:29 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id IAA01812; Mon, 11 Mar 1996 08:21:55 +0200 (SAT) Message-Id: <199603110621.IAA01812@grumble.grondar.za> To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: secure/lib/libtelnet/Makefile Date: Mon, 11 Mar 1996 08:21:54 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote: > What's this stuff? > > #ifdef ENCRYPTION > ... > #endif > > Somebody forget they were hacking a Makefile and drop accidently > into C mode or something? :-) > > Actually, generally speaking, this Makefile is a royal mess and > there's probably more commented out at this point in there than there is > actual contents. :-) Oh, wow! I've just committed fixes. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 22:31:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06155 for current-outgoing; Sun, 10 Mar 1996 22:31:27 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06124 for ; Sun, 10 Mar 1996 22:31:18 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id HAA01352; Mon, 11 Mar 1996 07:48:13 +0200 (SAT) Message-Id: <199603110548.HAA01352@grumble.grondar.za> To: Ollivier Robert cc: joerg_wunsch@uriah.heep.sax.de, mark@grondar.za, current@Freebsd.ORG Subject: Re: Compat collection. Date: Mon, 11 Mar 1996 07:48:12 +0200 From: Mark Murray Sender: owner-current@Freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert wrote: > It seems that J Wunsch said: > > binaries. Instead, i usually pick /usr/junklib for it, and ldconfig > > this directory, too. Perhaps the hooks for this should go into the > > base system, so a compatxx distribution can easily make use of it. > > Perhaps a /compat/freebsd as we've agreed on this for ibcs2 and linux ? I line the idea of a separate directory, but I prefer something under /usr so we can keep iy in that partition without compulsory, messy symlinks. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 22:32:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06500 for current-outgoing; Sun, 10 Mar 1996 22:32:53 -0800 (PST) Received: from veda.is (root@veda.is [193.4.230.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06482 for ; Sun, 10 Mar 1996 22:32:45 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id GAA16424; Mon, 11 Mar 1996 06:29:48 GMT From: Adam David Message-Id: <199603110629.GAA16424@veda.is> Subject: Re: HEADS UP! Please check... To: mark@grondar.za (Mark Murray) Date: Mon, 11 Mar 1996 06:29:44 +0000 (GMT) Cc: freebsd-current@freebsd.org In-Reply-To: <199603110558.HAA01535@grumble.grondar.za> from Mark Murray at "Mar 11, 96 07:58:39 am" X-Mailer: ELM [version 2.4ME+ PL10 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > ubiq [1] % su > > su: kerberos: not in root's ACL. > > ubiq [2] % > > > > It used to prompt for a normal password and work. This is for all su to group > 0. > > Okay, kerberos is installed but not configured... but shouldn't this work? > > No. tell it not to use kerberos with `su -K'. Yes, I have been doing that. It was just a surprise to see the change in this behaviour for the case without the -K. I would expect it to ask for a normal password when kerberos is present but not available (for whatever reason). Or is this considered a security feature, to require non-kerberos handling to be explicitly requested?... but in that case why did the previous version ask for the password twice at all? -- Adam David From owner-freebsd-current Sun Mar 10 22:44:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA07987 for current-outgoing; Sun, 10 Mar 1996 22:44:18 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA07971 for ; Sun, 10 Mar 1996 22:44:08 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id IAA02287; Mon, 11 Mar 1996 08:43:31 +0200 (SAT) Message-Id: <199603110643.IAA02287@grumble.grondar.za> To: Adam David cc: mark@grondar.za (Mark Murray), freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... Date: Mon, 11 Mar 1996 08:43:29 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adam David wrote: > > No. tell it not to use kerberos with `su -K'. > > Yes, I have been doing that. It was just a surprise to see the change in this > behaviour for the case without the -K. I would expect it to ask for a normal > password when kerberos is present but not available (for whatever reason). Or > is this considered a security feature, to require non-kerberos handling to be > explicitly requested?... but in that case why did the previous version ask fo r > the password twice at all? The original Kerberos intgration was done in a bit of a hurry :-). If you have the pre-change code, have a look at it. There is one major call to Kerberos in main(), and it was squeezed in with a minimum of integration effort. If that call fails (for whatever reason), the code drops through to the original logic. This call was "wrapped" around the original logic, and had its own password prompt, resulting in the possibility of two prompts. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Mar 10 22:52:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA09088 for current-outgoing; Sun, 10 Mar 1996 22:52:02 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA09048 for ; Sun, 10 Mar 1996 22:51:55 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA07820; Mon, 11 Mar 1996 17:47:26 +1100 Date: Mon, 11 Mar 1996 17:47:26 +1100 From: Bruce Evans Message-Id: <199603110647.RAA07820@godzilla.zeta.org.au> To: current@freebsd.org, jmz@cabri.obs-besancon.fr Subject: Re: COMCONSOLE: a patch and a problem Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I played with the boot blocks and I noticed that I was unable to boot >from a serial console (keyboard unplugged). The patch below fixes a >bug in boot.c/probe_keyboard.c (well, at least on my machine:-). I don't think I broke this :-). I wonder when it last worked. >The problem now: when booting from a serial console, there is no >timeout at the 'Boot:' prompt. Further investigations showed that the >bios_tick function always returns the same value! Is this related to >the fact that the keyboard is not plugged in? I broke this. It's because there are no BIOS calls which have the side affect of allowing clock interrupts. Add some dummy BIOS calls. Putting them in the bios_tick macro would take too much space, so arrange to always call ischar() and throw away the result in the RB_SERIAL case. Bruce From owner-freebsd-current Sun Mar 10 23:01:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10201 for current-outgoing; Sun, 10 Mar 1996 23:01:48 -0800 (PST) Received: from veda.is (root@veda.is [193.4.230.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA10190 for ; Sun, 10 Mar 1996 23:01:41 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id HAA01428; Mon, 11 Mar 1996 07:00:46 GMT From: Adam David Message-Id: <199603110700.HAA01428@veda.is> Subject: Re: HEADS UP! Please check... To: mark@grondar.za (Mark Murray) Date: Mon, 11 Mar 1996 07:00:39 +0000 (GMT) Cc: mark@grondar.za, freebsd-current@freebsd.org In-Reply-To: <199603110643.IAA02287@grumble.grondar.za> from Mark Murray at "Mar 11, 96 08:43:29 am" X-Mailer: ELM [version 2.4ME+ PL10 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > is this considered a security feature, to require non-kerberos handling > > to be explicitly requested?... (I will rephrase to ask what I meant to...) > > but in that case why did the previous version ask for the password twice > > at all? If this is a security feature, why allow the password to be offered to both kerberos and "normal" authentication at all, without requiring the user to specify which one? (of course, the default depends on whether kerberos exists). Sorry, I probably missed something really obvious here. -- Adam David From owner-freebsd-current Sun Mar 10 23:31:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12419 for current-outgoing; Sun, 10 Mar 1996 23:31:34 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA12414 for ; Sun, 10 Mar 1996 23:31:31 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA18380 for current@freebsd.org; Mon, 11 Mar 1996 08:16:34 +0100 Message-Id: <199603110716.IAA18380@ra.dkuug.dk> Subject: Native & Linux ELF support finally there... To: current@freebsd.org (FreeBSD current) Date: Mon, 11 Mar 1996 08:16:33 +0100 (MET) From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi gang.. After a hectic week, Peter Wemm and I are proud to announce that FreeBSD-current now has ELF support. This means that we are now able to run native FreeBSD ELF binaries (generated with John Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux QUAKE finally works, at least as far as Peter & I has tried it (Hey I dont have time to play) Have fun !! -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Sun Mar 10 23:38:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12924 for current-outgoing; Sun, 10 Mar 1996 23:38:05 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA12919 for ; Sun, 10 Mar 1996 23:38:02 -0800 (PST) Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id XAA03435; Sun, 10 Mar 1996 23:37:42 -0800 (PST) Date: Sun, 10 Mar 1996 23:37:41 -0800 (PST) From: invalid opcode To: "Jordan K. Hubbard" cc: Frank Durda IV , freebsd-current@Freebsd.ORG Subject: Re: New kernel In-Reply-To: <22539.826511303@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@Freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Mar 1996, Jordan K. Hubbard wrote: > How about PASSIVE_AGGRESSIVE? The kernel doesn't actually panic, but > corrupts your files occasionally when you're away on vacation. :-) > Jordan How about MULTIPLE_PERSONALITY, the kernel supports all forms of Linux emulation and in addition, supports all the distributions. :P Okay, M'm done now. == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Mon Mar 11 00:10:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15121 for current-outgoing; Mon, 11 Mar 1996 00:10:48 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA15116 for ; Mon, 11 Mar 1996 00:10:45 -0800 (PST) Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id AAA03498; Mon, 11 Mar 1996 00:10:09 -0800 (PST) Date: Mon, 11 Mar 1996 00:10:09 -0800 (PST) From: invalid opcode To: Adam David cc: rgrimes@GndRsh.aac.DEv.COM, freebsd-current@FreeBSD.ORG Subject: Re: changes to /etc/ttys In-Reply-To: <199603110035.AAA12661@veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Mar 1996, Adam David wrote: > output-only console, but then keyboard input would have to be prevented > altogether, which is not currently done in this case. > Adam David Exactly, that was my point entirely. A true console. I don't think keyboard input would matter that much though, seeing as all it does is get echoed. == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Mon Mar 11 00:16:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15543 for current-outgoing; Mon, 11 Mar 1996 00:16:34 -0800 (PST) Received: from maui.com (root@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA15537 Mon, 11 Mar 1996 00:16:31 -0800 (PST) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by maui.com (8.6.10/8.6.6) with ESMTP id WAA18828; Sun, 10 Mar 1996 22:16:23 -1000 Received: (from root@localhost) by caliban.dihelix.com (8.7.4/8.6.9) id WAA18031; Sun, 10 Mar 1996 22:16:25 -1000 (HST) Message-Id: <199603110816.WAA18031@caliban.dihelix.com> Subject: Re: Native & Linux ELF support finally there... To: sos@FreeBSD.org Date: Sun, 10 Mar 1996 22:16:24 -1000 (HST) From: "David Langford" Cc: current@FreeBSD.org In-Reply-To: <199603110716.IAA18380@ra.dkuug.dk> from "sos@FreeBSD.org" at Mar 11, 96 08:16:33 am From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Most cool. Thanks for the work. Now a side note: for those of us with our heads in the closet are there any pointers to the wonders of why Elf exists? i.e. what makes it so great that I should bow down before it? Thanks, David Langford langfod@dihelix.com >Hi gang.. > > >After a hectic week, Peter Wemm and I are proud to announce that >FreeBSD-current now has ELF support. This means that we are now >able to run native FreeBSD ELF binaries (generated with John >Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux >QUAKE finally works, at least as far as Peter & I has tried it >(Hey I dont have time to play) > >Have fun !! > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > So much code to hack -- so little time. > From owner-freebsd-current Mon Mar 11 00:21:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15939 for current-outgoing; Mon, 11 Mar 1996 00:21:35 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA15922 for ; Mon, 11 Mar 1996 00:21:29 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA16603 for ; Mon, 11 Mar 1996 09:21:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA19377 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 09:21:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA05510 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 09:14:19 +0100 (MET) From: J Wunsch Message-Id: <199603110814.JAA05510@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 11 Mar 1996 09:14:19 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603110647.RAA07820@godzilla.zeta.org.au> from "Bruce Evans" at Mar 11, 96 05:47:26 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >I played with the boot blocks and I noticed that I was unable to boot > >from a serial console (keyboard unplugged). The patch below fixes a > >bug in boot.c/probe_keyboard.c (well, at least on my machine:-). > > I don't think I broke this :-). I wonder when it last worked. Seems that i broke it in rev. 1.5. Weird. I could swear i've been testing it. :-) O well, i gotta play with all of this again. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 11 00:41:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA17582 for current-outgoing; Mon, 11 Mar 1996 00:41:59 -0800 (PST) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA17570 Mon, 11 Mar 1996 00:41:52 -0800 (PST) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <03134-0@bunyip.cc.uq.oz.au>; Mon, 11 Mar 1996 18:41:46 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id SAA25392; Mon, 11 Mar 1996 18:41:45 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id IAA06376; Mon, 11 Mar 1996 08:44:13 GMT Message-Id: <199603110844.IAA06376@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: sos@freebsd.org cc: current@freebsd.org Subject: Re: Native & Linux ELF support finally there... In-reply-to: Your message of "Mon, 11 Mar 1996 08:16:33 +0100." <199603110716.IAA18380@ra.dkuug.dk> X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Mar 1996 18:44:12 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Announcement elided] Good stuff guys! Now perhaps you can tell us where to get John Polstras Elfkit-1.0.1 & if this drops the Linux ELF libs & ld.so in the right place. Stephen -- I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Mon Mar 11 00:49:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA17992 for current-outgoing; Mon, 11 Mar 1996 00:49:11 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA17986 Mon, 11 Mar 1996 00:49:05 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA18747; Mon, 11 Mar 1996 09:33:10 +0100 Message-Id: <199603110833.JAA18747@ra.dkuug.dk> Subject: Re: Native & Linux ELF support finally there... To: sysseh@devetir.qld.gov.au (Stephen Hocking) Date: Mon, 11 Mar 1996 09:33:09 +0100 (MET) Cc: sos@freebsd.org, current@freebsd.org In-Reply-To: <199603110844.IAA06376@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at Mar 11, 96 06:44:12 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Stephen Hocking who wrote: > > > [Announcement elided] > > Good stuff guys! Now perhaps you can tell us where to get John Polstras > Elfkit-1.0.1 & if this drops the Linux ELF libs & ld.so in the right place. Erhm, maybe I wasn't clear enough, Polstras ELfkit is only needed to compile & run Native FreeBSD ELF binaries. To run Linux ELF binaries you need a Linux ld.so + linux ELF libs the collection I use come from Slackware 3.0. I belive Peter i working onpreparing a set of libs that will be availabel as a package..> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Mon Mar 11 00:57:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA18584 for current-outgoing; Mon, 11 Mar 1996 00:57:48 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA18575 Mon, 11 Mar 1996 00:57:44 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA18791; Mon, 11 Mar 1996 09:42:16 +0100 Message-Id: <199603110842.JAA18791@ra.dkuug.dk> Subject: Re: Native & Linux ELF support finally there... To: langfod@dihelix.com (David Langford) Date: Mon, 11 Mar 1996 09:42:15 +0100 (MET) Cc: sos@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199603110816.WAA18031@caliban.dihelix.com> from "David Langford" at Mar 10, 96 10:16:24 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to David Langford who wrote: > > Most cool. Thanks for the work. Your'e welcome :) > Now a side note: for those of us with our heads in the closet are there > any pointers to the wonders of why Elf exists? i.e. what makes it > so great that I should bow down before it? For FreeBSD bins ? nothing as fas as I can tell, It helped Linux clean up their shared libs mess, we did that right in the first place :) (who was it that said think first then act :) Besides that there are a lot of possibilities in ELF like multible text segments, specific debugging info etc etc. But none of that gives us anything in the short run. I see no immediate need for us to convert to ELF format, but it gives us some interesting possibilities to be able to run them... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Mon Mar 11 01:08:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA19572 for current-outgoing; Mon, 11 Mar 1996 01:08:11 -0800 (PST) Received: from maui.com (root@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA19563 Mon, 11 Mar 1996 01:08:05 -0800 (PST) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by maui.com (8.6.10/8.6.6) with ESMTP id XAA20008; Sun, 10 Mar 1996 23:07:58 -1000 Received: (from root@localhost) by caliban.dihelix.com (8.7.4/8.6.9) id XAA20972; Sun, 10 Mar 1996 23:08:00 -1000 (HST) Message-Id: <199603110908.XAA20972@caliban.dihelix.com> Subject: Re: Native & Linux ELF support finally there... To: sos@FreeBSD.org Date: Sun, 10 Mar 1996 23:07:59 -1000 (HST) From: "David Langford" Cc: langfod@dihelix.com, current@FreeBSD.org In-Reply-To: <199603110842.JAA18791@ra.dkuug.dk> from "sos@FreeBSD.org" at Mar 11, 96 09:42:15 am From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> Now a side note: for those of us with our heads in the closet are there >> any pointers to the wonders of why Elf exists? i.e. what makes it >> so great that I should bow down before it? > >For FreeBSD bins ? nothing as fas as I can tell, It helped Linux >clean up their shared libs mess, we did that right in the first place :) > >(who was it that said think first then act :) > >Besides that there are a lot of possibilities in ELF like multible >text segments, specific debugging info etc etc. But none of >that gives us anything in the short run. >I see no immediate need for us to convert to ELF format, but it gives >us some interesting possibilities to be able to run them... Hmm. Actually I was thinking more of your latter statement. I guess it boils to: what are the new features out the Elf format. Not necessarily versus a.out but just what the nifty feature of Elf are. Thanks. -David Langford langfod@dihelix.com From owner-freebsd-current Mon Mar 11 01:30:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA21844 for current-outgoing; Mon, 11 Mar 1996 01:30:11 -0800 (PST) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA21822 for ; Mon, 11 Mar 1996 01:30:03 -0800 (PST) Received: from tiger.fl.net.au (adf@tiger.fl.net.au [203.63.198.11]) by ter2.fl.net.au (2.0/adf) with SMTP id TAA10882 for ; Mon, 11 Mar 1996 19:33:04 +1000 (EST) Message-Id: <2.2.32.19960312062841.00a40450@mail.fl.net.au> X-Sender: adf@mail.fl.net.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Mar 1996 20:28:41 -1000 To: current@freebsd.org From: Andrew Foster Subject: Abort trap in SNAP Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just got this : cafu:/var/log# ps auxw | more Abort trap (core dumped) Then ps went on normally and did not happen on a subsequent invokation of this command. This is in the 2.2-960303-SNAP. Thanks, Andrew ----------- Andrew Foster Sydney, Australia From owner-freebsd-current Mon Mar 11 02:41:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA28793 for current-outgoing; Mon, 11 Mar 1996 02:41:06 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA28788 Mon, 11 Mar 1996 02:40:58 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0tw529-0003vwC; Mon, 11 Mar 96 02:40 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id KAA11937; Mon, 11 Mar 1996 10:40:54 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: sos@freebsd.org cc: current@freebsd.org (FreeBSD current) Subject: Re: Native & Linux ELF support finally there... In-reply-to: Your message of "Mon, 11 Mar 1996 08:16:33 +0100." <199603110716.IAA18380@ra.dkuug.dk> Date: Mon, 11 Mar 1996 10:40:52 +0000 Message-ID: <11935.826540852@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ... meanwhile in the compat-cave the dynamic duo works hard: > After a hectic week, Peter Wemm and I are proud to announce that > FreeBSD-current now has ELF support. This means that we are now > able to run native FreeBSD ELF binaries (generated with John > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux > QUAKE finally works, at least as far as Peter & I has tried it > (Hey I dont have time to play) Bravo! -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Mar 11 03:38:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA02821 for current-outgoing; Mon, 11 Mar 1996 03:38:04 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA02788 Mon, 11 Mar 1996 03:37:33 -0800 (PST) Received: by sequent.kiae.su id AA17686 (5.65.kiae-2 ); Mon, 11 Mar 1996 14:23:46 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 11 Mar 96 14:23:45 +0300 Received: (from ache@localhost) by astral.msk.su (8.7.4/8.7.3) id OAA00798; Mon, 11 Mar 1996 14:11:29 +0300 (MSK) Message-Id: <199603111111.OAA00798@astral.msk.su> Subject: Re: secure/lib/libtelnet/Makefile To: mark@grondar.za (Mark Murray) Date: Mon, 11 Mar 1996 14:11:29 +0300 (MSK) Cc: jkh@freefall.freebsd.org, current@freefall.freebsd.org In-Reply-To: <199603110621.IAA01812@grumble.grondar.za> from "Mark Murray" at "Mar 11, 96 08:21:54 am" From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL11 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > "Jordan K. Hubbard" wrote: > > What's this stuff? > > > > #ifdef ENCRYPTION > > ... > > #endif > > > > Somebody forget they were hacking a Makefile and drop accidently > > into C mode or something? :-) > > > > Actually, generally speaking, this Makefile is a royal mess and > > there's probably more commented out at this point in there than there is > > actual contents. :-) > > Oh, wow! > > I've just committed fixes. > Please, back out, it is comment, not ifdef. See also secure/usr.bin/telnet, secure/libexec/telnetd -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Mon Mar 11 03:47:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA03124 for current-outgoing; Mon, 11 Mar 1996 03:47:35 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA03119 for ; Mon, 11 Mar 1996 03:47:31 -0800 (PST) Received: by Sisyphos id AA20705 (5.67b/IDA-1.5 for current@freebsd.org); Mon, 11 Mar 1996 12:46:36 +0100 Message-Id: <199603111146.AA20705@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 11 Mar 1996 12:46:35 +0100 In-Reply-To: Terry Lambert "Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap)" (Mar 10, 12:21) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Terry Lambert Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 10, 12:21, Terry Lambert wrote: } Before, when I suggested that a DMA be triggered as part of a probe } process on a per controller basis to determine if bounce buffers } were necessary, I neglected the non-working cache case. The cache } cases need to be considered at the same time because they need to } trigger similar controller/memory events in order to be detectable. } } When a bus master DMA occurs, there is supposed to be a cache } notification, and the L1 and L2 cache lines are supposed to be } invalidated or written back for the memory range in which the DMA } took place. Just for the record: The NCR driver does such a test, and it has detected hardware problems on a few occasions ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Mon Mar 11 04:05:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA04163 for current-outgoing; Mon, 11 Mar 1996 04:05:43 -0800 (PST) Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA04147 for ; Mon, 11 Mar 1996 04:05:27 -0800 (PST) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id NAA05115; Mon, 11 Mar 1996 13:04:24 +0100 From: Wolfram Schneider Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.7.2/8.7.2) id NAA23816; Mon, 11 Mar 1996 13:04:20 +0100 (MET) Date: Mon, 11 Mar 1996 13:04:20 +0100 (MET) Message-Id: <199603111204.NAA23816@caramba.cs.tu-berlin.de> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: *.mk wishes In-Reply-To: <199603102124.IAA15692@godzilla.zeta.org.au> References: <199603102124.IAA15692@godzilla.zeta.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Conversion: prohibited Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: >newfs/mkfs.c passes an uncast 0 for a pointer and an uncast 0 for an off_t. >rpc.statd passes an uncast NULL for a pointer and an uncast 0 for an off_t. >I would't worry about fixing this. There must be a prototype in scope for >the uncast 0 for an off_t to work, and it isn't a bug to omit the casts iff >there is a prototype in scope. Just fix the configuration. Do we have a >working mmap? :-) http://www.lysator.liu.se/c/ten-commandments.html 3 Thou shalt cast all function arguments to the expected type if they are not of that type already, even when thou art convinced that this is unnecessary, lest they take cruel vengeance upon thee when thou least expect it. A programmer should understand the type structure of his language, lest great misfortune befall him. Contrary to the heresies espoused by some of the dwellers on the Western Shore, `int' and `long' are not the same type. The moment of their equivalence in size and representation is short, and the agony that awaits believers in their interchangeability shall last forever and ever once 64-bit machines become common. Also, contrary to the beliefs common among the more backward inhabitants of the Polluted Eastern Marshes, `NULL' does not have a pointer type, and must be cast to the correct type whenever it is used as a function argument. (The words of the prophet Ansi, which permit NULL to be defined as having the type `void *', are oft taken out of context and misunderstood. The prophet was granting a special dispensation for use in cases of great hardship in wild lands. Verily, a righteous program must make its own way through the Thicket Of Types without lazily relying on this rarely-available dispensation to solve all its problems. In any event, the great deity Dmr who created C hath wisely endowed it with many types of pointers, not just one, and thus it would still be necessary to convert the prophet's NULL to the desired type.) It may be thought that the radical new blessing of ``prototypes'' might eliminate the need for caution about argument types. Not so, brethren. Firstly, when confronted with the twisted strangeness of variable numbers of arguments, the problem returns... and he who has not kept his faith strong by repeated practice shall surely fall to this subtle trap. Secondly, the wise men have observed that reliance on prototypes doth open many doors to strange errors, and some indeed had hoped that prototypes would be decreed for purposes of error checking but would not cause implicit conversions. Lastly, reliance on prototypes causeth great difficulty in the Real World today, when many cling to the old ways and the old compilers out of desire or necessity, and no man knoweth what machine his code may be asked to run on tomorrow. From owner-freebsd-current Mon Mar 11 05:26:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA07973 for current-outgoing; Mon, 11 Mar 1996 05:26:43 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA07967 Mon, 11 Mar 1996 05:26:41 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.4/8.6.9) id FAA01571; Mon, 11 Mar 1996 05:25:51 -0800 (PST) Date: Mon, 11 Mar 1996 05:25:51 -0800 (PST) Message-Id: <199603111325.FAA01571@silvia.HIP.Berkeley.EDU> To: ache@astral.msk.su CC: mark@grondar.za, jkh@freefall.freebsd.org, current@freefall.freebsd.org In-reply-to: <199603111111.OAA00798@astral.msk.su> (ache@astral.msk.su) Subject: Re: secure/lib/libtelnet/Makefile From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > > What's this stuff? * > > * > > #ifdef ENCRYPTION * > > ... * > > #endif * Please, back out, it is comment, not ifdef. See also * secure/usr.bin/telnet, secure/libexec/telnetd *ROTFL* This one's gotta be the funny message of the month.... ;) Satoshi From owner-freebsd-current Mon Mar 11 06:51:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA12668 for current-outgoing; Mon, 11 Mar 1996 06:51:33 -0800 (PST) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA12662 Mon, 11 Mar 1996 06:51:32 -0800 (PST) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0tw8wa-0004IMC; Mon, 11 Mar 96 06:51 PST Date: Mon, 11 Mar 1996 06:51:26 -0800 (PST) From: Jake Hamby To: sos@FreeBSD.org cc: FreeBSD current Subject: Re: Native & Linux ELF support finally there... In-Reply-To: <199603110716.IAA18380@ra.dkuug.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Mar 1996 sos@FreeBSD.org wrote: Wow, that is too cool! I suppose it is safe to assume that your changes will be in the next SNAPshot that Jordan makes, right? If so, I'm going to bang on them like crazy, since I want our ELF support to be really rock solid (even more than Linux's ;-)! Some programs I'd like to bang on: Quake (of course ;-) DOOM and Netscape (make sure the a.out stuff still works :-) GNAT (GNU/NYU Ada Translator, this will be tricky since my plan is to run the Linux version of the Ada part with a FreeBSD-native GCC 2.7.2), in the hopes of building a package/port of the latest GNAT (GNAT is written in itself, so you need a binary before you can build it) :-( :-( ELF version of Executor (great Macintosh emulator) Linux/ELF Motif libraries and programs (I bought MetroLink some time ago) Finally, a question for you. Are FreeBSD ELF shared libraries intercompatible with Linux ELF shared libraries, in other words could you compile a FreeBSD ELF program using Linux ELF Motif? It would be too cool if this was possible... ---Jake > Hi gang.. > > > After a hectic week, Peter Wemm and I are proud to announce that > FreeBSD-current now has ELF support. This means that we are now > able to run native FreeBSD ELF binaries (generated with John > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux > QUAKE finally works, at least as far as Peter & I has tried it > (Hey I dont have time to play) > > Have fun !! > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > So much code to hack -- so little time. From owner-freebsd-current Mon Mar 11 06:54:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA12806 for current-outgoing; Mon, 11 Mar 1996 06:54:40 -0800 (PST) Received: from plaut.de ([194.39.177.166]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA12797 for ; Mon, 11 Mar 1996 06:54:34 -0800 (PST) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id NAA08635; Mon, 11 Mar 1996 13:39:27 +0100 Received: (from root@localhost) by totum.plaut.de (8.7.4/8.7.3) id PAA01577; Mon, 11 Mar 1996 15:39:11 +0100 (MET) Date: Mon, 11 Mar 1996 15:39:11 +0100 (MET) From: Michael Reifenberger To: "Jordan K. Hubbard" cc: Stefan Esser , current@FreeBSD.ORG Subject: Re: NCR disk controller, hp disk In-Reply-To: <1139.826494803@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Mar 1996, Jordan K. Hubbard wrote: > Date: Sun, 10 Mar 1996 22:53:23 +0100 > From: Jordan K. Hubbard > To: Stefan Esser > Cc: Jim Lowe , current@FreeBSD.ORG > Subject: Re: NCR disk controller, hp disk > > > This particular HP drive (the C3724S) is known > > to cause problems with tagged commands. Please > > Any chance of adding this to a `rogues list', Stefan? Please add C3725S to this yet imaginary list. Is this a general HP problem? Bye! ---- Michael Reifenberger From owner-freebsd-current Mon Mar 11 06:57:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA12962 for current-outgoing; Mon, 11 Mar 1996 06:57:58 -0800 (PST) Received: from deep-thought.demos.su (root@deep-thought.demos.su [194.87.1.76]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA12947 for ; Mon, 11 Mar 1996 06:57:49 -0800 (PST) Received: by deep-thought.demos.su id RAA00748; (8.7.4/D) Mon, 11 Mar 1996 17:57:19 +0300 (MSK) To: current@freebsd.org, mark@grondar.za Message-ID: Organization: DEMOS Date: Mon, 11 Mar 1996 17:57:18 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: secure/lib/libtelnet/Makefile and #ifdef comments Lines: 29 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There was simple #ifdef comment that don't hurt anybody in old days (it left from original telnet Makefiles), what happens now: .if defined(MAKE_EBONES) CFLAGS+= -DENCRYPTION .if exists(${DESTDIR}/usr/lib/libkrb.a) && defined(MAKE_EBONES) ENCRYPTION *can* be defined *without* MAKE_EBONES, encryption can be RSA, etc and not related to EBONES directly, it is wrong move. BTW, why is double MAKE_EBONES now? nocrypt: .if defined(ENCRYPTION) @for i in ${CRYPT_SRC}; do \ Yet one again: nobody define ENCRYPTION variable, such variable not exists. I don't see any logic here. There is two solutions exists: finally cleanup telnet/telnetd/libtelnet makefiles moving them to FreeBSD variant only or back out libtelnet change. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Mon Mar 11 07:11:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA13798 for current-outgoing; Mon, 11 Mar 1996 07:11:36 -0800 (PST) Received: from deep-thought.demos.su (root@deep-thought.demos.su [194.87.1.76]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA13770 for ; Mon, 11 Mar 1996 07:11:25 -0800 (PST) Received: by deep-thought.demos.su id RAA00748; (8.7.4/D) Mon, 11 Mar 1996 17:57:19 +0300 (MSK) To: current@freebsd.org, mark@grondar.za Message-ID: Organization: DEMOS Date: Mon, 11 Mar 1996 17:57:18 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: secure/lib/libtelnet/Makefile and #ifdef comments Lines: 29 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There was simple #ifdef comment that don't hurt anybody in old days (it left from original telnet Makefiles), what happens now: .if defined(MAKE_EBONES) CFLAGS+= -DENCRYPTION .if exists(${DESTDIR}/usr/lib/libkrb.a) && defined(MAKE_EBONES) ENCRYPTION *can* be defined *without* MAKE_EBONES, encryption can be RSA, etc and not related to EBONES directly, it is wrong move. BTW, why is double MAKE_EBONES now? nocrypt: .if defined(ENCRYPTION) @for i in ${CRYPT_SRC}; do \ Yet one again: nobody define ENCRYPTION variable, such variable not exists. I don't see any logic here. There is two solutions exists: finally cleanup telnet/telnetd/libtelnet makefiles moving them to FreeBSD variant only or back out libtelnet change. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Mon Mar 11 07:11:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA13838 for current-outgoing; Mon, 11 Mar 1996 07:11:55 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA13829 for ; Mon, 11 Mar 1996 07:11:49 -0800 (PST) Received: by Sisyphos id AA01381 (5.67b/IDA-1.5); Mon, 11 Mar 1996 15:26:36 +0100 Message-Id: <199603111426.AA01381@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 11 Mar 1996 15:26:35 +0100 In-Reply-To: "Jordan K. Hubbard" "Re: NCR disk controller, hp disk" (Mar 10, 13:53) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Jordan K. Hubbard" Subject: Re: NCR disk controller, hp disk Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 10, 13:53, "Jordan K. Hubbard" wrote: } Subject: Re: NCR disk controller, hp disk } > This particular HP drive (the C3724S) is known } > to cause problems with tagged commands. Please } } Any chance of adding this to a `rogues list', Stefan? My suggested FAILSAFE define will disable tags and permit an install to succeed. The default number of tags can be set in the kernel config file. The clean solution to this problem is to move the TAG code into the generic SCSI driver, and to have that code react to the ASC/ASCQ values returned by the drive. In the case of the HP, the command would be retried without TAG and would succeed, then ... This is the prefered solution, since it doesn't even require a "rogues" list entry for the drive ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Mon Mar 11 07:24:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA14910 for current-outgoing; Mon, 11 Mar 1996 07:24:50 -0800 (PST) Received: from hoopoe.psc.edu (hoopoe.psc.edu [128.182.61.57]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA14904 for ; Mon, 11 Mar 1996 07:24:47 -0800 (PST) Received: from hoopoe.psc.edu (peterb@LOCALHOST [127.0.0.1]) by hoopoe.psc.edu (8.7.4/8.7.3 PSC 1995/12/12 lambert/ebola) with ESMTP id KAA26017 for ; Mon, 11 Mar 1996 10:27:38 -0500 (EST) Message-Id: <199603111527.KAA26017@hoopoe.psc.edu> To: current@freebsd.org Subject: Curses, kablooie. Date: Mon, 11 Mar 1996 10:27:37 -0500 From: Peter Berger Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there known problems in curses in current? I have some code that works fine under BSDi, and I'll be testing it under NetBSD later today. It fails under current (as of feb 21.) Here's the backtrace: (gdb) bt #0 0x5e7ca in bzero () #1 0x400 in ?? () #2 0x5c1fd in __call_hash () #3 0x5b513 in __hash_open () #4 0x5b2f0 in dbopen () #5 0x4c66c in cgetent () #6 0x4c50e in cgetent () #7 0x48dca in tgetent () #8 0x44dd1 in setterm () #9 0x34f5d in restore (file=0xefbfdd7b "-r", envp=0xefbfdd2c) at save.c:223 #10 0x1a8ed in main (argc=2, argv=0xefbfdd20, envp=0xefbfdd2c) at main.c:139 218 if ((sp = getenv("TERM")) == NULL) { 219 printf("Null terminal!\n\n\nnull!\n"); 220 sp = Def_term; 221 } 223 setterm(sp); 224 - --KAA26003.826558031/hoopoe.psc.edu-- ------- End of Forwarded Message From owner-freebsd-current Mon Mar 11 07:57:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17168 for current-outgoing; Mon, 11 Mar 1996 07:57:16 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17161 for ; Mon, 11 Mar 1996 07:57:11 -0800 (PST) Received: by Sisyphos id AA04619 (5.67b/IDA-1.5 for current@FreeBSD.ORG); Mon, 11 Mar 1996 16:51:46 +0100 Message-Id: <199603111551.AA04619@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 11 Mar 1996 16:51:45 +0100 In-Reply-To: Michael Reifenberger "Re: NCR disk controller, hp disk" (Mar 11, 15:39) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Michael Reifenberger Subject: Re: NCR disk controller, hp disk Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 11, 15:39, Michael Reifenberger wrote: } Subject: Re: NCR disk controller, hp disk } On Sun, 10 Mar 1996, Jordan K. Hubbard wrote: } } > Date: Sun, 10 Mar 1996 22:53:23 +0100 } > From: Jordan K. Hubbard } > To: Stefan Esser } > Cc: Jim Lowe , current@FreeBSD.ORG } > Subject: Re: NCR disk controller, hp disk } > } > > This particular HP drive (the C3724S) is known } > > to cause problems with tagged commands. Please } > } > Any chance of adding this to a `rogues list', Stefan? } } Please add C3725S to this yet imaginary list. The C3724S and C3725S are identical drives, as far as I am concerned :) } Is this a general HP problem? It appears to be specific to that drive series (i.e. HP C372xS) and according to some other message I received, Solaris can't use tags with them, neither ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Mon Mar 11 08:32:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA19701 for current-outgoing; Mon, 11 Mar 1996 08:32:16 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA19695 for ; Mon, 11 Mar 1996 08:32:12 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA17767; Mon, 11 Mar 1996 10:30:39 -0600 From: Joe Greco Message-Id: <199603111630.KAA17767@brasil.moneng.mei.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 11 Mar 1996 10:30:39 -0600 (CST) Cc: jehamby@lightside.com, current@FreeBSD.ORG, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603100445.UAA10659@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 9, 96 08:45:51 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > So far three people, including myself, have reported the above panic > > message when booting the 3/3 SNAP kernel. All three of us have AMD DX4 > > processors (100 and 120MHz). This has got to be the problem! John, > > Jordan, people working on the VM system, take note.. Thanks! > > Can all three of you tell me if you have A80486DX4-100NV8T's or > A80486DX4-100SV8B's? The difference is the SV8B is the write back > enhanced DX4 and unless you have a motherboard that understands > how to deal with this you are going to have a cache coherency problem > between the internal and external cache. > > I have yet to see a MB deal with this correctly when faced with > a bus master SCSI controller, though I have seen some that work fine > as long as no bus mastering is occuring. Far more don't work than > do work. > > If you don't have SV8B's or are not running them in WB mode, then > I don't have any idea what has gone wrong... Ummmm. Ummmm.. that may explain a problem I have been seeing. :-) I have a pair of DX4/120's ("Enhanced"), one with IDE disk, one with 1542 and SCSI disk. The one with SCSI disk is unhappy during big compiles (make world, etc). I haven't _noticed_ problems with the IDE disk. Same MB/cpu, etc. Rod, you seem to imply that by NOT running them in WB mode, the problem may not manifest itself (dependent upon the MB). Is this what you meant to imply? Can you recommend a good 486 motherboard (preferably PCI)? Argh, I just got the fingers on my left hand wired to equipment in the next office.. hard to type.. I noticed ASUS seems to have several other offerings besides the SP3G.. Thx, ... JG From owner-freebsd-current Mon Mar 11 08:50:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA24219 for current-outgoing; Mon, 11 Mar 1996 08:50:17 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA24212 for ; Mon, 11 Mar 1996 08:50:13 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id QAA20866 for ; Mon, 11 Mar 1996 16:46:52 GMT Received: from tees by snowdon with SMTP (PP); Mon, 11 Mar 1996 16:43:27 +0000 Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id QAA21401 for current@freebsd.org; Mon, 11 Mar 1996 16:47:12 GMT Date: Mon, 11 Mar 1996 16:47:12 GMT From: Paul Richards Message-Id: <199603111647.QAA21401@tees> To: current@freebsd.org Subject: Re: NCR disk controller, hp disk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: qasaVkMlMcoqmf+MDdQu8g== Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > } Any chance of adding this to a `rogues list', Stefan? > > My suggested FAILSAFE define will > disable tags and permit an install > to succeed. > > The default number of tags can be > set in the kernel config file. > > > The clean solution to this problem is > to move the TAG code into the generic > SCSI driver, and to have that code > react to the ASC/ASCQ values returned > by the drive. In the case of the HP, > the command would be retried without > TAG and would succeed, then ... > > This is the prefered solution, since > it doesn't even require a "rogues" > list entry for the drive ... Do these drives work with the Adpactec controller? Rod? From owner-freebsd-current Mon Mar 11 09:47:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA27672 for current-outgoing; Mon, 11 Mar 1996 09:47:38 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA27663 for ; Mon, 11 Mar 1996 09:47:33 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA02475; Mon, 11 Mar 1996 12:47:22 -0500 Date: Mon, 11 Mar 1996 12:47:22 -0500 From: "Garrett A. Wollman" Message-Id: <9603111747.AA02475@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... In-Reply-To: <199603110558.HAA01535@grumble.grondar.za> References: <199603110558.HAA01535@grumble.grondar.za> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> ubiq [1] % su >> su: kerberos: not in root's ACL. >> ubiq [2] % >> >> It used to prompt for a normal password and work. This is for all su to group > 0. >> Okay, kerberos is installed but not configured... but shouldn't this work? > No. tell it not to use kerberos with `su -K'. Actually, as the person who requested this change to begin with, I believe that this case /should/ work. It's something that didn't come up in the original MIT code since it uses separate `su' and `ksu' programs. -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 11 09:56:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA28424 for current-outgoing; Mon, 11 Mar 1996 09:56:00 -0800 (PST) Received: from DeepCore.dk (dial61.cybercity.dk [194.16.56.61]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA28400 Mon, 11 Mar 1996 09:55:53 -0800 (PST) Received: (from sos@localhost) by DeepCore.dk (8.7.4/8.7.3) id SAA00731; Mon, 11 Mar 1996 18:31:32 +0100 (MET) Message-Id: <199603111731.SAA00731@DeepCore.dk> Subject: Re: Native & Linux ELF support finally there... To: jehamby@lightside.com (Jake Hamby) Date: Mon, 11 Mar 1996 18:31:31 +0100 (MET) Cc: sos@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Jake Hamby" at Mar 11, 96 06:51:26 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jake Hamby who wrote: > > On Mon, 11 Mar 1996 sos@FreeBSD.org wrote: > > Wow, that is too cool! I suppose it is safe to assume that your changes > will be in the next SNAPshot that Jordan makes, right? If so, I'm going > to bang on them like crazy, since I want our ELF support to be really > rock solid (even more than Linux's ;-)! Some programs I'd like to bang on: > > Quake (of course ;-) > DOOM and Netscape (make sure the a.out stuff still works :-) Why is it that these two candidates come up again and again :) > GNAT (GNU/NYU Ada Translator, this will be tricky since my plan is to run > the Linux version of the Ada part with a FreeBSD-native GCC 2.7.2), in > the hopes of building a package/port of the latest GNAT (GNAT is written > in itself, so you need a binary before you can build it) :-( :-( > ELF version of Executor (great Macintosh emulator) > Linux/ELF Motif libraries and programs (I bought MetroLink some time ago) > Finally, a question for you. Are FreeBSD ELF shared libraries > intercompatible with Linux ELF shared libraries, in other words could you > compile a FreeBSD ELF program using Linux ELF Motif? It would be too > cool if this was possible... Hmm, depends, from a general viewpoint I'd say no, but.... If that library don't use any systemcalls directly, but only accesses them through libc, and we have them in our libc, it might work. Otherwise its a sure failuremode, as one binary can only have one systemcall structure (sysentvec), and there is no easy way to change that. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Mon Mar 11 11:13:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA04651 for current-outgoing; Mon, 11 Mar 1996 11:13:14 -0800 (PST) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA04645 for ; Mon, 11 Mar 1996 11:13:11 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I2840SZXC0000LNG@mail.rwth-aachen.de> for freebsd-current@freefall.FreeBSD.org; Mon, 11 Mar 1996 20:16:27 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id UAA09971 for freebsd-current@freefall.cdrom.com; Mon, 11 Mar 1996 20:19:26 +0100 Date: Mon, 11 Mar 1996 20:19:26 +0100 From: "Christoph P. Kukulies" Subject: some quirks (dmesg, /etc/exports) To: freebsd-current@freefall.FreeBSD.org Message-id: <199603111919.UAA09971@gilberto.physik.rwth-aachen.de> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I moved a 2.1 machine to a Mar 6 -current. (maybe not such a good date to pick up a src tree) but anyway here are some things that look strange: dmesg | more or dmesg >file gives garbage characters at the beginning (\M^?\^A). mountd claims an erroneous statement in my old /etc/exports file (-maproot=0). Am I missing another change in the syntax? From the docs (man exports) -maproot=user is still allowed. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Mar 11 12:15:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA11138 for current-outgoing; Mon, 11 Mar 1996 12:15:51 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA11128 for ; Mon, 11 Mar 1996 12:15:42 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA11143 for ; Mon, 11 Mar 1996 21:15:29 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA25964 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 21:15:28 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id VAA06762 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 21:10:59 +0100 (MET) From: J Wunsch Message-Id: <199603112010.VAA06762@uriah.heep.sax.de> Subject: Re: changes to /etc/ttys To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 11 Mar 1996 21:10:59 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "invalid opcode" at Mar 11, 96 00:10:09 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As invalid opcode wrote: > Exactly, that was my point entirely. A true console. I don't think > keyboard input would matter that much though, seeing as all it does is > get echoed. I'm still missing the point why you don't want a getty on it? If i've got a serial console, i usually also run a getty on it. If i don't like the console behaviour (syslog messages all over the place), i don't need to log in there. Btw., i usually tweak the login message on the console, using a different gettytab entry: # console: add a newline after prompt C|Pc-co|Pc on console:\ :co:lm=Console login^M:tc=Pc: This way, my console looks like: Console login Mar 10 10:32:16 uriah login: ROOT LOGIN (r) ON ttyv0 Mar 10 10:32:16 uriah login: login on ttyv0 as r Mar 10 10:33:11 uriah login: ROOT LOGIN (xdm) ON ttyv0 Mar 10 10:33:11 uriah login: login on ttyv0 as xdm -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 11 12:26:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA11781 for current-outgoing; Mon, 11 Mar 1996 12:26:23 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA11774 Mon, 11 Mar 1996 12:26:21 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id MAA15472; Mon, 11 Mar 1996 12:25:33 -0800 (PST) Message-Id: <199603112025.MAA15472@ref.tfs.com> Subject: Re: Native & Linux ELF support finally there... To: sos@freebsd.org Date: Mon, 11 Mar 1996 12:25:33 -0800 (PST) From: "JULIAN Elischer" Cc: jehamby@lightside.com, current@freebsd.org In-Reply-To: <199603111731.SAA00731@DeepCore.dk> from "sos@freebsd.org" at Mar 11, 96 06:31:31 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmm, depends, from a general viewpoint I'd say no, but.... > If that library don't use any systemcalls directly, but only accesses > them through libc, and we have them in our libc, it might work. > Otherwise its a sure failuremode, as one binary can only have one > systemcall structure (sysentvec), and there is no easy way to change > that. so what are the chages that the libc's are compatible? My guess is about 0%.. just constants to syscalls are probably different enough.. let alone real semantic differences From owner-freebsd-current Mon Mar 11 12:28:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12090 for current-outgoing; Mon, 11 Mar 1996 12:28:18 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12079 for ; Mon, 11 Mar 1996 12:28:15 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA12773; Mon, 11 Mar 1996 12:27:39 -0800 From: "Rodney W. Grimes" Message-Id: <199603112027.MAA12773@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: terry@lambert.org (Terry Lambert) Date: Mon, 11 Mar 1996 12:27:39 -0800 (PST) Cc: imb@scgt.oz.au, current@freebsd.org In-Reply-To: <199603101921.MAA01621@phaeton.artisoft.com> from "Terry Lambert" at Mar 10, 96 12:21:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ... > For the L2, the Saturn I chipset (mask date pre-April 1994) had a > flaw, where the DMA notification from PCI was simply not internally > connected to anything. This is most often seen in Gateway and Dell > systems with 60MHz Pentiums, but they aren't the only ones who used > Saturn I's, so they aren't the only machines with problems. Ahhh... Saturn I and II are 486 chipsets, so this must be Gateway and Dell xxMhz 486 systems and not 60MHz Pentiums. ... > > Regards, > Terry Lambert > terry@lambert.org -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Mar 11 12:40:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13293 for current-outgoing; Mon, 11 Mar 1996 12:40:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA13285 for ; Mon, 11 Mar 1996 12:40:18 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03822; Mon, 11 Mar 1996 13:36:00 -0700 From: Terry Lambert Message-Id: <199603112036.NAA03822@phaeton.artisoft.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 11 Mar 1996 13:36:00 -0700 (MST) Cc: terry@lambert.org, imb@scgt.oz.au, current@freebsd.org In-Reply-To: <199603112027.MAA12773@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 11, 96 12:27:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > For the L2, the Saturn I chipset (mask date pre-April 1994) had a > > flaw, where the DMA notification from PCI was simply not internally > > connected to anything. This is most often seen in Gateway and Dell > > systems with 60MHz Pentiums, but they aren't the only ones who used > > Saturn I's, so they aren't the only machines with problems. > > Ahhh... Saturn I and II are 486 chipsets, so this must be Gateway and > Dell xxMhz 486 systems and not 60MHz Pentiums. You're right. But the Saturn chipset is not the only one that had the disconnected internal bus bridge (which was the problem: they left it off the artwork for some reason and blew a huge number of PCI bridge chip runs -- not just the SAturn, but Mercury and Neptune as well). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 11 12:41:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13381 for current-outgoing; Mon, 11 Mar 1996 12:41:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA13375 for ; Mon, 11 Mar 1996 12:41:18 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03837; Mon, 11 Mar 1996 13:38:08 -0700 From: Terry Lambert Message-Id: <199603112038.NAA03837@phaeton.artisoft.com> Subject: Re: finger and 2.2-960303-SNAP To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Mon, 11 Mar 1996 13:38:08 -0700 (MST) Cc: adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org In-Reply-To: <199603102145.WAA15105@keltia.freenix.fr> from "Ollivier Robert" at Mar 10, 96 10:45:48 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It seems that Andrew Foster said: > > And yet the old finger works fine, as does fingering from most other hosts > > I've tried. > > Finger has been changed (or fixed :-)) to use T/TCP recently... "Fixed" is subjective. It saves one response packet and loses interoperability. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 11 12:43:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13627 for current-outgoing; Mon, 11 Mar 1996 12:43:37 -0800 (PST) Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA13599 for ; Mon, 11 Mar 1996 12:43:21 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id WAA04844; Mon, 11 Mar 1996 22:42:21 +0200 (SAT) Message-Id: <199603112042.WAA04844@grumble.grondar.za> To: "Garrett A. Wollman" cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... Date: Mon, 11 Mar 1996 22:42:20 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Garrett A. Wollman" wrote: > >> Okay, kerberos is installed but not configured... but shouldn't this work? > > > No. tell it not to use kerberos with `su -K'. > > Actually, as the person who requested this change to begin with, I > believe that this case /should/ work. It's something that didn't come > up in the original MIT code since it uses separate `su' and `ksu' > programs. Hmm... My philosohy on this one was that if there was not an acl entry for the guy, no matter what, then he wasn't allowed in. I'm sure I could look for the above case and add it in. Others' comments? How does this new variant "feel" to you? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Mon Mar 11 12:47:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA14164 for current-outgoing; Mon, 11 Mar 1996 12:47:14 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA14147 for ; Mon, 11 Mar 1996 12:47:02 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03862; Mon, 11 Mar 1996 13:42:31 -0700 From: Terry Lambert Message-Id: <199603112042.NAA03862@phaeton.artisoft.com> Subject: Re: New kernel To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 11 Mar 1996 13:42:31 -0700 (MST) Cc: coredump@nervosa.com, uhclem@nemesis.lonestar.org, freebsd-current@FreeBSD.ORG In-Reply-To: <22539.826511303@time.cdrom.com> from "Jordan K. Hubbard" at Mar 10, 96 06:28:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > How about PASSIVE instead of AGRESSIVE. > > > > How about ASSERTIVE? > > > > kernel: Would it be okay if I panic'ed now? (y/n) > > How about PASSIVE_AGGRESSIVE? The kernel doesn't actually panic, but > corrupts your files occasionally when you're away on vacation. :-) It would never work. The machine would go through Lithium clock batteries like there was no tomorrow... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 11 13:00:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA15779 for current-outgoing; Mon, 11 Mar 1996 13:00:58 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA15773 Mon, 11 Mar 1996 13:00:55 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03889; Mon, 11 Mar 1996 13:59:03 -0700 From: Terry Lambert Message-Id: <199603112059.NAA03889@phaeton.artisoft.com> Subject: Re: Native & Linux ELF support finally there... To: sos@freebsd.org Date: Mon, 11 Mar 1996 13:59:03 -0700 (MST) Cc: langfod@dihelix.com, current@freebsd.org In-Reply-To: <199603110842.JAA18791@ra.dkuug.dk> from "sos@freebsd.org" at Mar 11, 96 09:42:15 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Now a side note: for those of us with our heads in the closet are there > > any pointers to the wonders of why Elf exists? i.e. what makes it > > so great that I should bow down before it? > > For FreeBSD bins ? nothing as fas as I can tell, It helped Linux > clean up their shared libs mess, we did that right in the first place :) It buys us the ability to segregate code based on ELF segment ID's (COFF gives us the same thing). The main wins are in a kernel arena: we can reclaim memory for unused drivers, and we can load/unload drivers on the basis of designating them as "fallback". That is, I could have a default console driver, load a replacement, and reclaim the space used by the default even though it was statically linked into a generic kernel. For applications with shared libraries, the current scheme has the text dynamically linked, but the data statically linked into the library. Because of this, it is questionable whether BSD shared libraries, or pre-ELF Linux shared libraries, can be used to meet the relink clause of the LGPL. That is, a library change that did not change interface could still change internal data and usage of data (the bind/sendmail "shared library" change about 5 months ago was exactly this kind of change), and thus make it impossible to link a binary shared and still comply with LGPL without shipping your object modules around with your binary. I think if you really pressed, it, the changed for i18n would render a large number of a.out Linux apps liked shared in violation of the LGPL relink clause because of the sys_errlist reference changes. > (who was it that said think first then act :) That would be me. ;-)... at least, I think it was largely my posts (and loud, obnoxious argument) that prevented rolling in the SVR3 style shared libraries when they were still the only thing available. > Besides that there are a lot of possibilities in ELF like multible > text segments, specific debugging info etc etc. But none of > that gives us anything in the short run. > I see no immediate need for us to convert to ELF format, but it gives > us some interesting possibilities to be able to run them... The LGPL argument is a good "short run" argument. The kernel arguments are a good "long run" argument, as is common ABI for SVR4 (well, and Linux, I guess) systems. Specifically, there are a hell of a lot of commercial apps that run on UnixWare and x86 Solaris that don't run on Linux or BSDI or NetBSD and don't run under IBCS2 because they are SVR4 binaries, not SVR3. It is also a lot easier to use the Motorolla publication of the SVR4 EABI to implement SVR4/Solaris compatible cshared libraries (for instance, the Linux ABI kludge of including the Linux libs won't work if the liubs are licensed materials -- like those in SVR4 and Solaris). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 11 13:27:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19254 for current-outgoing; Mon, 11 Mar 1996 13:27:51 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19220 for ; Mon, 11 Mar 1996 13:27:42 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA12878; Mon, 11 Mar 1996 13:25:42 -0800 From: "Rodney W. Grimes" Message-Id: <199603112125.NAA12878@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 11 Mar 1996 13:25:42 -0800 (PST) Cc: jehamby@lightside.com, current@FreeBSD.ORG, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603111630.KAA17767@brasil.moneng.mei.com> from "Joe Greco" at Mar 11, 96 10:30:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > So far three people, including myself, have reported the above panic > > > message when booting the 3/3 SNAP kernel. All three of us have AMD DX4 > > > processors (100 and 120MHz). This has got to be the problem! John, > > > Jordan, people working on the VM system, take note.. Thanks! > > > > Can all three of you tell me if you have A80486DX4-100NV8T's or > > A80486DX4-100SV8B's? The difference is the SV8B is the write back > > enhanced DX4 and unless you have a motherboard that understands > > how to deal with this you are going to have a cache coherency problem > > between the internal and external cache. > > > > I have yet to see a MB deal with this correctly when faced with > > a bus master SCSI controller, though I have seen some that work fine > > as long as no bus mastering is occuring. Far more don't work than > > do work. > > > > If you don't have SV8B's or are not running them in WB mode, then > > I don't have any idea what has gone wrong... > > Ummmm. Ummmm.. that may explain a problem I have been seeing. :-) > > I have a pair of DX4/120's ("Enhanced"), one with IDE disk, one with 1542 > and SCSI disk. The one with SCSI disk is unhappy during big compiles (make > world, etc). I haven't _noticed_ problems with the IDE disk. Same MB/cpu, > etc. > > Rod, you seem to imply that by NOT running them in WB mode, the problem may > not manifest itself (dependent upon the MB). Is this what you meant to > imply? Yes, that is exactly what I meant to imply. > Can you recommend a good 486 motherboard (preferably PCI)? Nope, IMHO, there are no _good_ 486 boards left on the market, the last _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not been able to get any more of them. > Argh, I just got the fingers on my left hand wired to equipment in the next > office.. hard to type.. > > I noticed ASUS seems to have several other offerings besides the SP3G.. Such as what, the PVI-486AP4, out of production for 4 months, the only 486 board that I know ASUS is still makeing is the PVI-486SP3, which I do not classify as a good board due to only 2 Simm sockets and if I recall correctly a cache coherency problem in the Sis 496/497 chipset. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Mar 11 13:28:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19524 for current-outgoing; Mon, 11 Mar 1996 13:28:36 -0800 (PST) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19469 for ; Mon, 11 Mar 1996 13:28:26 -0800 (PST) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA11400; Mon, 11 Mar 96 22:30:10 +0100 Date: Mon, 11 Mar 96 22:30:10 +0100 Message-Id: <9603112130.AA11400@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: bde@zeta.org.au Cc: current@freebsd.org In-Reply-To: <199603110647.RAA07820@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 11 Mar 1996 17:47:26 +1100) Subject: Re: COMCONSOLE: a patch and a problem X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Bruce Evans writes: >> I played with the boot blocks and I noticed that I was unable to boot >> from a serial console (keyboard unplugged). The patch below fixes a >> bug in boot.c/probe_keyboard.c (well, at least on my machine:-). > I don't think I broke this :-). I wonder when it last worked. >> The problem now: when booting from a serial console, there is no >> timeout at the 'Boot:' prompt. Further investigations showed that the >> bios_tick function always returns the same value! Is this related to >> the fact that the keyboard is not plugged in? > I broke this. It's because there are no BIOS calls which have the > side affect of allowing clock interrupts. Add some dummy BIOS calls. > Putting them in the bios_tick macro would take too much space, so > arrange to always call ischar() and throw away the result in the > RB_SERIAL case. Thanks for the hint. I just tried it and comconsole now works perfectly. (serial_ischar() -> serial_ischar()|(0 & ischar ())) > Bruce Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Mon Mar 11 13:29:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19653 for current-outgoing; Mon, 11 Mar 1996 13:29:43 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19644 for ; Mon, 11 Mar 1996 13:29:36 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA12888; Mon, 11 Mar 1996 13:28:01 -0800 From: "Rodney W. Grimes" Message-Id: <199603112128.NAA12888@GndRsh.aac.dev.com> Subject: Re: NCR disk controller, hp disk To: p.richards@elsevier.co.uk (Paul Richards) Date: Mon, 11 Mar 1996 13:28:00 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199603111647.QAA21401@tees> from "Paul Richards" at Mar 11, 96 04:47:12 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > } Any chance of adding this to a `rogues list', Stefan? > > > > My suggested FAILSAFE define will > > disable tags and permit an install > > to succeed. > > > > The default number of tags can be > > set in the kernel config file. > > > > > > The clean solution to this problem is > > to move the TAG code into the generic > > SCSI driver, and to have that code > > react to the ASC/ASCQ values returned > > by the drive. In the case of the HP, > > the command would be retried without > > TAG and would succeed, then ... > > > > This is the prefered solution, since > > it doesn't even require a "rogues" > > list entry for the drive ... > > Do these drives work with the Adpactec controller? Rod? Yes, at least I know the HP C3725S works fine, but I do not know if tags are on or off by default in the aic7xxx driver of -stable. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Mar 11 13:32:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20010 for current-outgoing; Mon, 11 Mar 1996 13:32:40 -0800 (PST) Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20003 for ; Mon, 11 Mar 1996 13:32:37 -0800 (PST) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.7.4/8.6.10) with ESMTP id NAA10854; Mon, 11 Mar 1996 13:31:24 -0800 (PST) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id NAA19725; Mon, 11 Mar 1996 13:31:23 -0800 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id NAA02528; Mon, 11 Mar 1996 13:29:58 -0800 Message-Id: <199603112129.NAA02528@cozumel.tcs.com> Subject: Re: COMCONSOLE: a patch and a problem To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 11 Mar 1996 13:29:57 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603110814.JAA05510@uriah.heep.sax.de> from "J Wunsch" at Mar 11, 96 09:14:19 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Given all the talk about serial consoles, I've been playing with them as well. This is what I've done. - Modified sysinstall to work with a serial console or graphics console. This means you can install a machine without a graphics card. (it is a little messy when loading packages, I should probably turn that off, but I did load a system via the serial port). - Hacked the biosboot code to echo and take input from both the graphics screen/keyboard and com1. This way I can control the boot by either the normal console or serial console. It would be nice if I could save the boot mode for the default of the next boot. I also filter out garbage from the serial port incase a mouse is connected to it and is talking back. One problem would be trying to screen out a modem on com1 talking back ... is this very common? Also with the method, I don't have to worry about keyboard probes but may have to for a serial port. I'm not sure if this is that good of an idea, but it works pretty well and it was kind of neat to try. - Run getty on /dev/console and not on /dev/ttyv0, so I get a console getty no matter which way I boot. The advantage of this stuff is to simplify remote (or lazy) debugging of stuff. It is nice to be able to steal the console and do everything via a serial port and then return it to normal operations. Doug A. From owner-freebsd-current Mon Mar 11 13:46:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21279 for current-outgoing; Mon, 11 Mar 1996 13:46:12 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21270 for ; Mon, 11 Mar 1996 13:46:00 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id WAA00840 for current@freebsd.org; Mon, 11 Mar 1996 22:30:19 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id WAA00241 for current@freebsd.org; Mon, 11 Mar 1996 22:30:30 +0100 (MET) From: Andreas Klemm Message-Id: <199603112130.WAA00241@knobel.gun.de> Subject: panic ... panic ... panic :( To: current@freebsd.org Date: Mon, 11 Mar 1996 22:30:30 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Supped today -current from the german sup server. Result: a) panic vm_fork u_map allocation failed during reboot savecore wasn't able to do it's work: savecore: system went down at Thu Jan 1 01:42:07 1970 dump time is unreasonable. b) after applying the cd9660 patchm that was mailed here some hours ago the system paniced immediately after mount /cdrom Fatal trap 9: general protection fault while in kernel mode. BTW -current seems to be in a miserable state. But not only since hours or days ... since about two or three weeks ... a little bit too long :( Sorry, too much emotions might come up now, but it's really frustrating. It's my working platform at home. To be more constructive now: can I help you with a more detailed bug message or do you already know what part of the source is causing this trouble ?! Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Mon Mar 11 14:05:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA23332 for current-outgoing; Mon, 11 Mar 1996 14:05:41 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA23327 for ; Mon, 11 Mar 1996 14:05:37 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id IAA23458 for current@freebsd.org; Tue, 12 Mar 1996 08:45:09 +1030 From: Michael Smith Message-Id: <199603112215.IAA23458@genesis.atrad.adelaide.edu.au> Subject: Re: NCR disk controller, hp disk To: current@freebsd.org Date: Tue, 12 Mar 1996 08:45:08 +1030 (CST) In-Reply-To: <199603111426.AA01381@Sisyphos> from "Stefan Esser" at Mar 11, 96 03:26:35 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser stands accused of saying: > > My suggested FAILSAFE define will > disable tags and permit an install > to succeed. Just on the naming thing, "FAILSAFE" gets a big thumbs-up from around here; it's very defintely the appropriate term in the mainframe world, not to mention aviation, electronics etc... -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon Mar 11 14:45:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25719 for current-outgoing; Mon, 11 Mar 1996 14:45:03 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA25712 Mon, 11 Mar 1996 14:45:01 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA02633 ; Mon, 11 Mar 1996 23:44:57 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA10358 ; Mon, 11 Mar 1996 23:44:57 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id TAA04093; Mon, 11 Mar 1996 19:40:13 +0100 (MET) From: Ollivier Robert Message-Id: <199603111840.TAA04093@keltia.freenix.fr> Subject: Re: Native & Linux ELF support finally there... To: sos@freebsd.org Date: Mon, 11 Mar 1996 19:40:13 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199603110716.IAA18380@ra.dkuug.dk> from "sos@freebsd.org" at "Mar 11, 96 08:16:33 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1759 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that sos@freebsd.org said: > FreeBSD-current now has ELF support. This means that we are now > able to run native FreeBSD ELF binaries (generated with John > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux ^^^^^^^^^^^^ When this will be available ? > QUAKE finally works, at least as far as Peter & I has tried it > (Hey I dont have time to play) Thanks [again] for all the work. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Tue Feb 20 01:16:51 MET 1996 From owner-freebsd-current Mon Mar 11 15:02:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA26983 for current-outgoing; Mon, 11 Mar 1996 15:02:06 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA26963 for ; Mon, 11 Mar 1996 15:02:01 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA14644 for ; Tue, 12 Mar 1996 00:01:56 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA27757 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 00:01:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id WAA07526 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 22:22:06 +0100 (MET) From: J Wunsch Message-Id: <199603112122.WAA07526@uriah.heep.sax.de> Subject: system() broken while mmap()ing something To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 11 Mar 1996 22:22:06 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk There's been a long and ongoing discussion about the reasons why recent XFree86(tm) servers don't run under FreeBSD-current. With Xkb enabled, they hang the entire system, or cause other weird behaviour. All the other systems supported by XFree86 don't suffer from this, and it's easily provable that it's not related to phkmalloc (e.g. by using the original gnumalloc again). David Dawes has been boiling down this to: ----- Forwarded message from David Dawes ----- From: David Dawes Message-Id: <199603111058.VAA20801@rf900.physics.usyd.edu.au> Subject: Re: 3.1.2Db S3 freebsd-current To: beta@XFree86.Org Date: Mon, 11 Mar 1996 21:58:31 +1100 (EST) In-Reply-To: <199603110802.JAA05393@uriah.heep.sax.de> from "J Wunsch" at Mar 11, 96 09:02:18 am >Do i understand it right that the system() call happens while /dev/mem >is kept mmap()ed inside the X server? Perhaps this is something >that's unique to the X server environment. (Other programs might >either not mmap /dev/mem at all, or at least, they don't fork.) That is correct. The mmap happens when the display is initialised. The system() call happens when the input devices are initialised, and this happens after the display is initialised. The mmap area isn't completely lost -- at least reads (I tried xwd -root) are *almost* OK with the S3 server when using a 64k VGA aperture. I've attached a test program that does demonstrate a problem. The program isn't what I originally had in mind. This one mmaps the BIOS, and in three phases it "writes" to it, and reads back the result. Since the BIOS is read-only, mismatches should occur in each phase, however on FreeBSD-current, the last phase (after a system("/bin/ls > /tmp/l")) reports no mismatches. On FreeBSD-2.0.5, mismatches are correctly reported at each phase. David ----------- #include #include #include #include #include #define SIZE (4 * 1024) #define BASE 0xC0000 main() { int fd = -1; unsigned char *base = NULL; unsigned char *save = NULL; int i; int mismatch = 0; if ((fd = open("/dev/mem", O_RDWR)) < 0) { perror("can't open /dev/mem"); exit(1); } base = (unsigned char *)mmap((caddr_t)0, SIZE, PROT_READ | PROT_WRITE, MAP_FILE, fd, (off_t)BASE); if ((int)base == -1) { perror("can't mmap vga memory"); exit(1); } #ifdef SAVE_NEEDED /* Save the existing memory contents */ if ((save = (unsigned char *)malloc(SIZE)) == NULL) { perror("malloc failed"); exit(1); } memcpy(save, base, SIZE); #endif /* Write a pattern */ for (i = 0; i < SIZE; i++) base[i] = (i & 0xFF) ^ (i >> 8); /* Read it back */ for (i = 0; i < SIZE; i++) if (base[i] != ((i & 0xFF) ^ (i >> 8))) { #ifdef VERBOSE printf("before: byte %5d doesn't match -- %3d != %3d\n", i, base[i], (i & 0xFF) ^ (i >> 8)); #endif mismatch++; } printf("before: %5d mismatches\n", mismatch); /* Clear the pattern */ memset(base, 0, SIZE); /* Write a pattern */ for (i = 0; i < SIZE; i++) base[i] = (i & 0xFF) ^ (i >> 8); /* Read it back */ mismatch = 0; for (i = 0; i < SIZE; i++) if (base[i] != ((i & 0xFF) ^ (i >> 8))) { #ifdef VERBOSE printf("middle: byte %5d doesn't match -- %3d != %3d\n", i, base[i], (i & 0xFF) ^ (i >> 8)); #endif mismatch++; } printf("middle: %5d mismatches\n", mismatch); /* Clear the pattern */ memset(base, 0, SIZE); /* Run something harmless */ system("/bin/ls > /tmp/l"); /* Write a pattern */ for (i = 0; i < SIZE; i++) base[i] = (i & 0xFF) ^ (i >> 8); /* Read it back */ mismatch = 0; for (i = 0; i < SIZE; i++) if (base[i] != ((i & 0xFF) ^ (i >> 8))) { #ifdef VERBOSE printf("after: byte %5d doesn't match -- %3d != %3d\n", i, base[i], (i & 0xFF) ^ (i >> 8)); #endif mismatch++; } printf("after: %5d mismatches\n", mismatch); #ifdef SAVE_NEEDED /* unmap, remap, and restore the video memory */ munmap(base, SIZE); base = (char *)mmap((caddr_t)0, SIZE, PROT_READ | PROT_WRITE, MAP_FILE, fd, (off_t)BASE); if ((int)base == -1) { perror("can't mmap vga memory"); exit(1); } memcpy(base, save, SIZE); #endif munmap(base, SIZE); exit(0); } ----- End of forwarded message from David Dawes ----- -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 11 15:03:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA27120 for current-outgoing; Mon, 11 Mar 1996 15:03:11 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA27114 for ; Mon, 11 Mar 1996 15:03:08 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA14632 for ; Tue, 12 Mar 1996 00:01:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA27751 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 00:01:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id XAA00295 for freebsd-current@FreeBSD.org; Mon, 11 Mar 1996 23:12:35 +0100 (MET) From: J Wunsch Message-Id: <199603112212.XAA00295@uriah.heep.sax.de> Subject: Re: system() broken while mmap()ing something To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 11 Mar 1996 23:12:34 +0100 (MET) In-Reply-To: from "j" at Mar 11, 96 10:22:06 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Following up to myself... I've just tested David's program on my machine. > I've attached a test program that does demonstrate a problem. The program > isn't what I originally had in mind. This one mmaps the BIOS, and in three > phases it "writes" to it, and reads back the result. Since the BIOS is > read-only, mismatches should occur in each phase, however on FreeBSD-current, > the last phase (after a system("/bin/ls > /tmp/l")) reports no mismatches. > On FreeBSD-2.0.5, mismatches are correctly reported at each phase. The results for me are: kernel version David's program XServer w/ Xkb enabled runs okay? doesn't crash system? Mar 9, 1996 No. No. Feb 3, 1996 Yes. No. Mar, 1995 (GENERIC 2.0.5?) Yes. Yes. So, the test program only seems to show the most evil behaviour. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 11 15:43:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA00487 for current-outgoing; Mon, 11 Mar 1996 15:43:28 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA00470 for ; Mon, 11 Mar 1996 15:43:24 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA15571; Tue, 12 Mar 1996 00:41:50 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA28066; Tue, 12 Mar 1996 00:41:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id AAA01114; Tue, 12 Mar 1996 00:29:34 +0100 (MET) From: J Wunsch Message-Id: <199603112329.AAA01114@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 00:29:33 +0100 (MET) Cc: ambrisko@tcs.com (Douglas Ambrisko) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603112129.NAA02528@cozumel.tcs.com> from "Douglas Ambrisko" at Mar 11, 96 01:29:57 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Douglas Ambrisko wrote: > - Hacked the biosboot code to echo and take input from both the > graphics screen/keyboard and com1. This way I can control the boot Great! > by either the normal console or serial console. It would be nice > if I could save the boot mode for the default of the next boot. > very common? Also with the method, I don't have to worry about > keyboard probes but may have to for a serial port. Probing for a serial port is much easier. The idea behind the keyboard probe was stolen from workstations: if no keyboard is present, default to the first serial port. You can only have one system console, so at least by the time you're going to boot the kernel, you must have made a decision. > - Run getty on /dev/console and not on /dev/ttyv0, so I get a console > getty no matter which way I boot. Hmm, there was a saying the running getty on /dev/console used to be totally broken. Bruce? Ever tried it lately? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 11 16:22:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA03154 for current-outgoing; Mon, 11 Mar 1996 16:22:10 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA03145 Mon, 11 Mar 1996 16:22:01 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA17014; Tue, 12 Mar 1996 11:16:08 +1100 Date: Tue, 12 Mar 1996 11:16:08 +1100 From: Bruce Evans Message-Id: <199603120016.LAA17014@godzilla.zeta.org.au> To: langfod@dihelix.com, sos@freebsd.org Subject: Re: Native & Linux ELF support finally there... Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Now a side note: for those of us with our heads in the closet are there >> any pointers to the wonders of why Elf exists? i.e. what makes it >> so great that I should bow down before it? >For FreeBSD bins ? nothing as fas as I can tell, It helped Linux Then why is imgact_elf.c `standard'? :-) It bloats the kernel another 4.5K. Bruce From owner-freebsd-current Mon Mar 11 17:14:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA08516 for current-outgoing; Mon, 11 Mar 1996 17:14:21 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA08498 for ; Mon, 11 Mar 1996 17:14:16 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id UAA02930; Mon, 11 Mar 1996 20:09:53 GMT From: "John S. Dyson" Message-Id: <199603112009.UAA02930@dyson.iquest.net> Subject: Re: panic ... panic ... panic :( To: andreas@knobel.gun.de (Andreas Klemm) Date: Mon, 11 Mar 1996 20:09:53 +0000 () Cc: current@FreeBSD.org In-Reply-To: <199603112130.WAA00241@knobel.gun.de> from "Andreas Klemm" at Mar 11, 96 10:30:30 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hi ! > > Supped today -current from the german sup server. Result: > > a) panic vm_fork u_map allocation failed > > during reboot savecore wasn't able to do it's work: > savecore: system went down at Thu Jan 1 01:42:07 1970 > dump time is unreasonable. > I haven't forgotten that one, and am working it RIGHT NOW :-). John From owner-freebsd-current Mon Mar 11 17:38:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA11852 for current-outgoing; Mon, 11 Mar 1996 17:38:39 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA11846 for ; Mon, 11 Mar 1996 17:38:38 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id RAA03439; Mon, 11 Mar 1996 17:37:00 -0800 (PST) Message-Id: <199603120137.RAA03439@precipice.shockwave.com> To: Douglas Ambrisko cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: COMCONSOLE: a patch and a problem In-reply-to: Your message of "Mon, 11 Mar 1996 13:29:57 PST." <199603112129.NAA02528@cozumel.tcs.com> Date: Mon, 11 Mar 1996 17:37:00 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Cool... send in patches From: Douglas Ambrisko Subject: Re: COMCONSOLE: a patch and a problem Given all the talk about serial consoles, I've been playing with them as well >>. This is what I've done. - Modified sysinstall to work with a serial console or graphics console. This means you can install a machine without a graphics card. (it is a little messy when loading packages, I should probably turn that off, but I did load a system via the serial port). - Hacked the biosboot code to echo and take input from both the graphics screen/keyboard and com1. This way I can control the boot by either the normal console or serial console. It would be nice if I could save the boot mode for the default of the next boot. I also filter out garbage from the serial port incase a mouse is connected to it and is talking back. One problem would be trying to screen out a modem on com1 talking back ... is this very common? Also with the method, I don't have to worry about keyboard probes but may have to for a serial port. I'm not sure if this is that good of an idea, but it works pretty well and it was kind of neat to try. - Run getty on /dev/console and not on /dev/ttyv0, so I get a console getty no matter which way I boot. The advantage of this stuff is to simplify remote (or lazy) debugging of stuf >>f. It is nice to be able to steal the console and do everything via a serial port and then return it to normal operations. Doug A. From owner-freebsd-current Mon Mar 11 17:39:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA11924 for current-outgoing; Mon, 11 Mar 1996 17:39:46 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA11916 for ; Mon, 11 Mar 1996 17:39:43 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id RAA03399; Mon, 11 Mar 1996 17:35:54 -0800 (PST) Message-Id: <199603120135.RAA03399@precipice.shockwave.com> To: Terry Lambert cc: roberto@keltia.freenix.fr (Ollivier Robert), adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Mon, 11 Mar 1996 13:38:08 MST." <199603112038.NAA03837@phaeton.artisoft.com> Date: Mon, 11 Mar 1996 17:35:54 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: Terry Lambert Subject: Re: finger and 2.2-960303-SNAP > It seems that Andrew Foster said: > > And yet the old finger works fine, as does fingering from most other host >>s > > I've tried. > > Finger has been changed (or fixed :-)) to use T/TCP recently... "Fixed" is subjective. It saves one response packet and loses interoperability. 8-(. It interoperates fine with non-broken TCP implementations. I'm really glad that finger was chosen... of course, it should have been DOCUMENTED. :-) From owner-freebsd-current Mon Mar 11 18:46:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17077 for current-outgoing; Mon, 11 Mar 1996 18:46:01 -0800 (PST) Received: from specgw.spec.co.jp (specgw.spec.co.jp [202.32.13.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA17064 Mon, 11 Mar 1996 18:45:53 -0800 (PST) Received: from localhost (uucp@localhost) by specgw.spec.co.jp (8.6.5/3.3Wb-SPEC) with UUCP id LAA07216; Tue, 12 Mar 1996 11:35:06 +0900 Received: by tama.spec.co.jp (8.7.4/6.4J.5) id LAA02530; Tue, 12 Mar 1996 11:35:34 +0900 (JST) From: Atsushi Murai Message-Id: <199603120235.LAA02530@tama.spec.co.jp> Subject: Re: Native & Linux ELF support finally there... To: sos@freebsd.org Date: Tue, 12 Mar 1996 11:35:34 +0900 (JST) Cc: current@freebsd.org In-Reply-To: <199603110716.IAA18380@ra.dkuug.dk> from "sos@freebsd.org" at Mar 11, 96 08:16:33 am Reply-To: amurai@spec.co.jp X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi gang.. > > > After a hectic week, Peter Wemm and I are proud to announce that > FreeBSD-current now has ELF support. This means that we are now > able to run native FreeBSD ELF binaries (generated with John > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux > QUAKE finally works, at least as far as Peter & I has tried it > (Hey I dont have time to play) > > Have fun !! > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > So much code to hack -- so little time. Sounds great! But is there any way/plan to exclude this support code during a compiling kernel(i.e options COMPAT_LINUX) ? It's will be helpful for optimizing a size of kernel under the restricted memory ;-) Atsushi. -- Atsushi Murai Internet: amurai@spec.co.jp System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 From owner-freebsd-current Mon Mar 11 18:52:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17341 for current-outgoing; Mon, 11 Mar 1996 18:52:04 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA17324 for ; Mon, 11 Mar 1996 18:52:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id SAA04062; Mon, 11 Mar 1996 18:51:39 -0800 (PST) To: Andreas Klemm cc: current@FreeBSD.org Subject: Re: panic ... panic ... panic :( In-reply-to: Your message of "Mon, 11 Mar 1996 22:30:30 +0100." <199603112130.WAA00241@knobel.gun.de> Date: Mon, 11 Mar 1996 18:51:39 -0800 Message-ID: <4060.826599099@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > BTW -current seems to be in a miserable state. But not only since > hours or days ... since about two or three weeks ... a little bit > too long :( No need to apologise, you're perfectly correct. -current has been an unstable mess. :-( Jordan From owner-freebsd-current Mon Mar 11 18:53:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17426 for current-outgoing; Mon, 11 Mar 1996 18:53:21 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA17418 for ; Mon, 11 Mar 1996 18:53:15 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id NAA01086; Tue, 12 Mar 1996 13:52:29 +1100 From: David Dawes Message-Id: <199603120252.NAA01086@rf900.physics.usyd.edu.au> Subject: Re: system() broken while mmap()ing something To: j@uriah.heep.sax.de (J Wunsch) Date: Tue, 12 Mar 1996 13:52:29 +1100 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603112212.XAA00295@uriah.heep.sax.de> from "J Wunsch" at Mar 11, 96 11:12:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> I've attached a test program that does demonstrate a problem. The program >> isn't what I originally had in mind. This one mmaps the BIOS, and in three >> phases it "writes" to it, and reads back the result. Since the BIOS is >> read-only, mismatches should occur in each phase, however on FreeBSD-current, >> the last phase (after a system("/bin/ls > /tmp/l")) reports no mismatches. >> On FreeBSD-2.0.5, mismatches are correctly reported at each phase. > >The results for me are: > >kernel version David's program XServer w/ Xkb enabled > runs okay? doesn't crash system? > >Mar 9, 1996 No. No. > >Feb 3, 1996 Yes. No. > >Mar, 1995 >(GENERIC 2.0.5?) Yes. Yes. > >So, the test program only seems to show the most evil behaviour. The test program also works fine with 2.1.0-RELEASE. I've never seen the Xserver with Xkb crash the system on -current. I just find that the server doesn't work correctly regarding usage of the mmaped /dev/mem/area. For most servers this means a blank display. The only -current kernels I've tried are the 960303 snap and one from around 9 March (which fixed most of the probably unrelated panics I saw with the 960303 version). I did see a panic with the 9 March version at 2am this morning when /etc/daily started (good thing I was up watching the Cricket World Cup :-). David From owner-freebsd-current Mon Mar 11 18:55:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17582 for current-outgoing; Mon, 11 Mar 1996 18:55:41 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA17571 for ; Mon, 11 Mar 1996 18:55:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id SAA04086; Mon, 11 Mar 1996 18:55:09 -0800 (PST) To: Douglas Ambrisko cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: COMCONSOLE: a patch and a problem In-reply-to: Your message of "Mon, 11 Mar 1996 13:29:57 PST." <199603112129.NAA02528@cozumel.tcs.com> Date: Mon, 11 Mar 1996 18:55:09 -0800 Message-ID: <4084.826599309@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Given all the talk about serial consoles, I've been playing with them as well . > > This is what I've done. And just so you know I've not totally ignored the patches you sent me (though I haven't yet replied - sorry! This one seems to have been on my "pending stack" for a little bit too long), I was sort of unsure as to the general ramifications of your biosboot and ttys changes. Clearly, any change to support serial consoles can't be done at the expense of general usage, and I seem to remember from the deep and dark past that there are serious problems with putting a getty on /dev/console rather than /dev/ttyv0 when you'r running X. This may have been solved already, but can someone help refresh my memory? More to the point, could you submit the patches here to -current for more general review? Your sysinstall changes I will take unilaterally, but the rest I'd like some wider commentary on before I'll contemplate taking them into the tree. Thanks! Jordan From owner-freebsd-current Mon Mar 11 19:18:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA19322 for current-outgoing; Mon, 11 Mar 1996 19:18:48 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA19313 for ; Mon, 11 Mar 1996 19:18:45 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.4/8.7.3) id TAA29089; Mon, 11 Mar 1996 19:18:35 -0800 (PST) Date: Mon, 11 Mar 1996 19:18:32 -0800 (PST) From: -Vince- To: current@FreeBSD.ORG Subject: 3/11/96 15:00 PST -current kernel won't compile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk cpp -DLOCORE -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DXSERVER -DATAPI -DNSWAPDEV=20 -DEXT2FS -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../i386/linux/linux_locore.s | as -o linu x_locore.o ../../i386/linux/linux_locore.s:1: linux_assym.h: No such file or directory ../../i386/linux/linux_locore.s: Assembler messages: ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SIGF_HANDLER never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SIGF_SC never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SC_FS never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SC_GS never defined. ../../i386/linux/linux_locore.s:26: Fatal error:4 errors, 0 warnings, no object file generated. *** Error code 33 Stop. From owner-freebsd-current Mon Mar 11 20:14:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA23392 for current-outgoing; Mon, 11 Mar 1996 20:14:15 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA23375 for ; Mon, 11 Mar 1996 20:14:05 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA28341; Tue, 12 Mar 1996 15:07:50 +1100 Date: Tue, 12 Mar 1996 15:07:50 +1100 From: Bruce Evans Message-Id: <199603120407.PAA28341@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: COMCONSOLE: a patch and a problem Cc: ambrisko@tcs.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> - Run getty on /dev/console and not on /dev/ttyv0, so I get a console >> getty no matter which way I boot. >Hmm, there was a saying the running getty on /dev/console used to be >totally broken. Bruce? Ever tried it lately? Not lately. I use syscons, which still has the hack of using a special minor device for the console so that /dev/console is a little different from /dev/vt0. I think there is nothing special for pcvt, so /dev/vt0 is the console. Bruce From owner-freebsd-current Mon Mar 11 20:25:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA24343 for current-outgoing; Mon, 11 Mar 1996 20:25:49 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA24334 for ; Mon, 11 Mar 1996 20:25:37 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id XAA00292; Mon, 11 Mar 1996 23:20:12 GMT From: "John S. Dyson" Message-Id: <199603112320.XAA00292@dyson.iquest.net> Subject: Re: system() broken while mmap()ing something To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Mon, 11 Mar 1996 23:20:12 +0000 () Cc: j@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <199603120252.NAA01086@rf900.physics.usyd.edu.au> from "David Dawes" at Mar 12, 96 01:52:29 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >> I've attached a test program that does demonstrate a problem. The program > >> isn't what I originally had in mind. This one mmaps the BIOS, and in three > >> phases it "writes" to it, and reads back the result. Since the BIOS is > >> read-only, mismatches should occur in each phase, however on FreeBSD-current, > >> the last phase (after a system("/bin/ls > /tmp/l")) reports no mismatches. > >> On FreeBSD-2.0.5, mismatches are correctly reported at each phase. > > > I have committed a temporary fix for the problem. It will work fine, except that I want to clean it up a bit later on. Still working on the map problem (that is probably causing panics.) John dyson@freebsd.org From owner-freebsd-current Mon Mar 11 20:48:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA26024 for current-outgoing; Mon, 11 Mar 1996 20:48:17 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA26019 for ; Mon, 11 Mar 1996 20:48:13 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA25996; Tue, 12 Mar 1996 15:23:32 +1030 From: Michael Smith Message-Id: <199603120453.PAA25996@genesis.atrad.adelaide.edu.au> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Mar 1996 15:23:32 +1030 (CST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 11, 96 01:25:42 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes stands accused of saying: > > I noticed ASUS seems to have several other offerings besides the SP3G.. > > Such as what, the PVI-486AP4, out of production for 4 months, the only > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > I do not classify as a good board due to only 2 Simm sockets and if I > recall correctly a cache coherency problem in the Sis 496/497 chipset. Er, we have a PVI-486SP3 here; the SIMM limit is mildly annoying, but (w/Intel DX4/100) appears to be rock-solid. The box in question has run multiple 'make world's; 16M/NCR SCSI etc. chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 10 on pci0:11 ... > Rod Grimes rgrimes@gndrsh.aac.dev.com -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon Mar 11 21:58:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01981 for current-outgoing; Mon, 11 Mar 1996 21:58:37 -0800 (PST) Received: from tyger.inna.net (tyger.inna.net [206.151.66.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA01976 for ; Mon, 11 Mar 1996 21:58:35 -0800 (PST) Received: from caught.inna.net (caught.inna.net [206.151.66.7]) by tyger.inna.net (8.7.3/8.7.3) with SMTP id AAA29416; Tue, 12 Mar 1996 00:58:21 -0500 (EST) Date: Tue, 12 Mar 1996 00:57:11 -0500 (EST) From: Thomas Arnold To: "Rodney W. Grimes" cc: current@freebsd.org Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Mar 1996, Rodney W. Grimes wrote: > Nope, IMHO, there are no _good_ 486 boards left on the market, the last > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not > been able to get any more of them. I have been having extremely good luck with the Biostar MB-8433UUD. 3 PCI slots 4 simm slots. Only problem is you need to get the absolute LATEST Award BIOS for it or you will have to set BIOS defaults by hand for chips like the X5. I'm running two here right now one with an AMD X5 and one with a Cyrix 5x86-120 both run fine. Side note : I have yet to find a fast 486 motherboard that would work with 4 or 6 chip 2x32 simms. This manifests itself in dozens of unrelated problems. I was unable to get an Adaptec 2940UW to work properly until I switched memory to 16chip 2x32 simms. I've noticed this problem on ASUS, Acer, and Biostar motherboards. These boards ( Biostar ) use the UMC chipset which, true to standard UMC form, towards the end of the lifespan of the chipset finally get all the kinks worked out... +-----------------------------------------------+ : Tom Arnold - No relation to Rosanne : : SysAdmin/Pres - TBI, Ltd ( inna.net ) : : An ISP serving the Virginia Middle Penninsula : +-----------------------------------------------+ From owner-freebsd-current Mon Mar 11 22:26:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA05785 for current-outgoing; Mon, 11 Mar 1996 22:26:14 -0800 (PST) Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA05750 for ; Mon, 11 Mar 1996 22:26:02 -0800 (PST) Received: from localhost (babkin@localhost) by hq.icb.chel.su (8.6.5/8.6.5) id LAA23560; Tue, 12 Mar 1996 11:24:47 +0500 From: "Serge A. Babkin" Message-Id: <199603120624.LAA23560@hq.icb.chel.su> Subject: Chipsets & FreeBSD To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Mar 1996 11:24:46 +0500 (GMT+0500) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@FreeBSD.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 11, 96 01:25:42 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Can you recommend a good 486 motherboard (preferably PCI)? > > Nope, IMHO, there are no _good_ 486 boards left on the market, the last > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not > been able to get any more of them. > > > Argh, I just got the fingers on my left hand wired to equipment in the next > > office.. hard to type.. > > > > I noticed ASUS seems to have several other offerings besides the SP3G.. > > Such as what, the PVI-486AP4, out of production for 4 months, the only > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > I do not classify as a good board due to only 2 Simm sockets and if I > recall correctly a cache coherency problem in the Sis 496/497 chipset. Packard Bell still sells (here, in Russia, may be they have finished the sales of these series in USA) their PB450D series boxes. Their motherboard works fine (I have it on my production machine). The only possible drawback is that it has 2 SIMM sockets. BTW, I plan to buy a Packard Bell 500D series machine with Pentium and Agoura motherboard. Did anybody tried to run it under FreeBSD ? Or may be had anyone heard something good/bad about them or about their chipsets ? Thanks! -SB From owner-freebsd-current Mon Mar 11 22:31:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06307 for current-outgoing; Mon, 11 Mar 1996 22:31:11 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA06259 for ; Mon, 11 Mar 1996 22:30:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA02242; Tue, 12 Mar 1996 17:21:26 +1100 Date: Tue, 12 Mar 1996 17:21:26 +1100 From: Bruce Evans Message-Id: <199603120621.RAA02242@godzilla.zeta.org.au> To: bde@zeta.org.au, wosch@cs.tu-berlin.de Subject: Re: *.mk wishes Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>newfs/mkfs.c passes an uncast 0 for a pointer and an uncast 0 for an off_t. >>rpc.statd passes an uncast NULL for a pointer and an uncast 0 for an off_t. >>I would't worry about fixing this. There must be a prototype in scope for >>the uncast 0 for an off_t to work, and it isn't a bug to omit the casts iff >>there is a prototype in scope. Just fix the configuration. Do we have a >>working mmap? :-) >http://www.lysator.liu.se/c/ten-commandments.html >... >It may be thought that the radical new blessing of ``prototypes'' >might eliminate the need for caution about argument types. Not so, >brethren. Firstly, when confronted with the twisted strangeness of >variable numbers of arguments, the problem returns... and he who has >not kept his faith strong by repeated practice shall surely fall to >this subtle trap. Secondly, the wise men have observed that reliance >on prototypes doth open many doors to strange errors, and some indeed >had hoped that prototypes would be decreed for purposes of error >checking but would not cause implicit conversions. Lastly, reliance >on prototypes causeth great difficulty in the Real World today, when Unix World yesterday? Real World last week? >many cling to the old ways and the old compilers out of desire or >necessity, and no man knoweth what machine his code may be asked to >run on tomorrow. I mostly agree with this, but there are too many uncast NULLs to fix: $ find /usr/src -type f | xargs grep ', NULL,' | grep -v '[{}]' | wc -l 738 $ find /usr/src/sys -type f | xargs grep ', NULL,' | grep -v '[{}]' | wc -l 106 This finds mostly uncast NULL pointers in function calls, but nowhere near all of them. Bruce From owner-freebsd-current Mon Mar 11 22:42:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA07467 for current-outgoing; Mon, 11 Mar 1996 22:42:25 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA07462 for ; Mon, 11 Mar 1996 22:42:22 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id HAA05671 ; Tue, 12 Mar 1996 07:42:13 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id HAA12033 ; Tue, 12 Mar 1996 07:42:12 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id XAA20680; Mon, 11 Mar 1996 23:49:53 +0100 (MET) From: Ollivier Robert Message-Id: <199603112249.XAA20680@keltia.freenix.fr> Subject: Re: finger and 2.2-960303-SNAP To: terry@lambert.org (Terry Lambert) Date: Mon, 11 Mar 1996 23:49:52 +0100 (MET) Cc: adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org In-Reply-To: <199603112038.NAA03837@phaeton.artisoft.com> from Terry Lambert at "Mar 11, 96 01:38:08 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1762 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk It seems that Terry Lambert said: > "Fixed" is subjective. It saves one response packet and loses > interoperability. 8-(. Only with broken TCP implementations like the Annex's. We'll never see the broken code change if no one complain and make them fix their bugs. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #6: Mon Mar 11 20:18:10 MET 1996 From owner-freebsd-current Mon Mar 11 23:06:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09007 for current-outgoing; Mon, 11 Mar 1996 23:06:38 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA09001 for ; Mon, 11 Mar 1996 23:06:35 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id HAA16333; Tue, 12 Mar 1996 07:45:18 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id HAA00388; Tue, 12 Mar 1996 07:36:58 +0100 (MET) From: Andreas Klemm Message-Id: <199603120636.HAA00388@knobel.gun.de> Subject: Re: panic ... panic ... panic :( To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 12 Mar 1996 07:36:58 +0100 (MET) Cc: current@FreeBSD.org In-Reply-To: <199603112009.UAA02930@dyson.iquest.net> from "John S. Dyson" at Mar 11, 96 08:09:53 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Supped today -current from the german sup server. Result: > > > > a) panic vm_fork u_map allocation failed > > > > during reboot savecore wasn't able to do it's work: > > savecore: system went down at Thu Jan 1 01:42:07 1970 > > dump time is unreasonable. > > > I haven't forgotten that one, and am working it RIGHT NOW :-). Thanks John, that's good news for me after getting up and having my first cup of coffee ;-) -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Mon Mar 11 23:10:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09269 for current-outgoing; Mon, 11 Mar 1996 23:10:35 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA09264 for ; Mon, 11 Mar 1996 23:10:30 -0800 (PST) Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id XAA07621; Mon, 11 Mar 1996 23:10:04 -0800 (PST) Date: Mon, 11 Mar 1996 23:10:03 -0800 (PST) From: invalid opcode To: Thomas Arnold cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Mar 1996, Thomas Arnold wrote: > On Mon, 11 Mar 1996, Rodney W. Grimes wrote: > > > Nope, IMHO, there are no _good_ 486 boards left on the market, the last > > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not > > been able to get any more of them. I agree. What happened to all the good Mylex and Happauge! EISA motherboards. 8 simms standard, 8 EISA slots, Weitek sockets. One of the best boards I saw was the Happauge 4860 motherboard. It had an i486 + an i860 risc processor. == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Mon Mar 11 23:27:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10344 for current-outgoing; Mon, 11 Mar 1996 23:27:34 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA10319 Mon, 11 Mar 1996 23:27:30 -0800 (PST) Message-Id: <199603120727.XAA10319@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The continueing 2842/eisaconf argument In-reply-to: Your message of "Sat, 09 Mar 1996 12:40:23 MST." <199603091940.MAA21251@phaeton.artisoft.com> Date: Mon, 11 Mar 1996 23:27:29 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You'rre probably right that most people aren't that interested in this discussion, so I'll make this my last note on this subject and let the source code speak for itself when I get to writing it. >The *only* reason you need the BIOS is to determine the per slot CMOS >area size. Other than that, all EISA information is accessable as a >memory reference from protected mode. > >I think the ability to access/manipulate EISA data is a lot closer >than the ever-out-of-reach-VM86(). If nothing else, the ram area >size *could* be passed via the boot code. Okay, provide the code. 8-) >> It has to be up to each driver to request and then interpret this >> information if it makes sense for them to do so. Many cards could >> care less about what's up in configuration space. The 3c579 is one, >> the 2842 is another. If we have to support EISA devices that don't >> want configuration data we can also support VLB devices that doesn't >> use configuration space information with no additional complexity. >> Its really a question of capability and use. > >I think this assumes you use real mode/VM86 BIOS calls to get the >configuration data per EISA slot. That way you would have a built >in stop for non-EISA cards. If you access via memory reference, as >I would hope would be done, since VM86() seems too far off, then >the stop isn't there. You seem to think that the eisaconf code could read the data and make any sense of it on its own. It can't. The ECU has the luxury of eisa configuration files to parse and tell it how to interpret the data. In FreeBSD, the device driver will have to know, so unless you want to compile eisa configuration files into the kernel you will always have to push eisa configuration space manipulation down into the driver (it calling the eisa configuration space manipulation API provided by eisaconf). >> The 2742 and the 2842 will continue to get most of the information >> about the card in the exact same way regardless of the availibility >> of configuration space data. You're also not talking about >> stub code, but an additional probe that iterates through the slot >> address space since the 2842 can't reference the eisa code in your >> model since you don't want to have to have eisa0 in your config file. > >Excuse me. You are saying that iterating through the slot address >space is the only way to detect if the card is present or not? I >know it is the method that happens to be used currently. I wasn't >aware that the card was otherwise undetectable. How else do you find them? How else do you find the 2842? >> Having the config file is simply a way of aiding the ECU >> in telling you where conflicts are or restricing your configuration >> settings. Once the ECU session is over, there's nothing their to >> tell FreeBSD about these ISA devices. > >I will agree with the caveat the we are talking about the *current* >ECU code. I believe the information that it does not have an EISA ID >is sufficient to indicate the cards existance and the need to probe >fixed cards with potentially invasive probes, at least the first >time the hardware is auto-configured. I can't parse this. I don't think AMI is going to be dropping me a new version of their ECU software anytime soon. Without the EISA ID or a "saved to disk" current configuration file, I don't think the ECU knows anything about the card. Remember that the ECU keys off the EISAID found at each slot to determine the eisa configuration file to read in so it can interpret the configuration space for the device. The ID for the last configured device is also stored up there so it can be matched to the device in the current slot. Other than the stored ID, I don't believe that there is any other data stored in a common format for the ECU to interpret... just a series of port addresses and data values to write out during initialization fothe EISA bus which could affect any of a number of different types of settings on the card. >> You can switch the dip switches on your 2842 all day, and FreeBSD will >> still find it. You can also move your 2742 from slot to slot all day >> and FreeBSD will still find it. Relocating the card doesn't prevent >> you from booting from it in either case so long as the card's bios is >> enabled. Booting is a BIOS issue. I can make a 2742 not bootable >> by disabling its BIOS too. > >It does if I relocate something over top of its address space because >it didn't have a graph entry warning me it was there. If you can't even get to the BIOS, FreeBSD can't help you. Someone who does this ends up calling Adaptec's technical support line who in turn will refer them back to page one of the user guide where it tells you in bold print to set the ID to be the same as for the slot its in if you install it in an EISA system. This has nothing to do with this discussion since FreeBSD cannot create or fix this situation. >> The 2742 is just as non-relocatable as the 2842. The 2742 locks out is irq >> register after the first time its written to (by the EISA configuration >> just after POST). > >This is irrelevant. EISA supports resetting this, in any case, or the >card would be impossible to reconfigure with the Adaptec tools. > >The point is that even if an EISA space card has only one potential >space utilization topology, it is intrinsically *different* from an >ISA card because the slot configuration data (which is only present >on real EISA and is not used currently) can be consulted to determine >allowable potential topologies. Only by asking the device to interpret the data for you. I can give you the same information for a 2842 and export it to eisaconf the same way the 2742 does and it doesn't matter that the 2842 never looked at configuration space. Your still thinking that eisconf can do the relocation without consulting each driver... It can't. >> Most EISA cards can't relocate their I/O range, but the >> Buslogic cards can relocate relocate their registers through a range of ISA >> compatibily areas. The point is that the way you deal with registering >> relocatability has to be generic so you can deal with devices that vary in >> their degrees of flexibility regardless of their bus type. > >I agree completely. But while the per slot data provides this information >for true EISA cards, it does not do so for VLB cards pretending to be >EISA cards. The configuration space doesn't tell you "all the possible places I can be set to." It tells you what registers on the card were set with what bits during boot. Nothing more. The driver still has to be the one to interpret the data. >This is seriously damning of my idea to use the EISA tag as a negative >indicator. It means that there *would* need to be probe code for VLB >cards that pretend to be EISA cards. > >But it does not mean that the probe would have to take the form of a >slot iteration. How else do you find them? I'll lend you my 2842 tech ref so you can tell me another way. :-) >BTW: I'm curious: how does the thing avoid slot configuration conflicts >in a real EISA system? How is the VLB "fake-EISA" data exported so as >to not conflict with the real thing? What if I plug two of these things >into two VLB slots in the same machine? People who don't read the installation instructions get hosed. Its not unlike most PC hardware. >> Not all EISA devices are relocatable in the same ways. I can find >> plenty of EISA devices that have the same relocation deficiencies >> as the 2842. This is not a valid argument. > >No, but all *real* EISA devices are detectably relocatable using the >slot configuration data that doesn't exist for VLB devices pretending >to be EISA devices. As I've pointed out before, it doesn't matter where the driver gets the data as long as there is a facility for it to inform the configuration manager of what capabilities it has. >This is what I meant when I said the configuration process would have >to dereference this data through the driver so that the VLB card >driver could fake the information that wouldn't exist if the config >attempted to access it directly without the indirection. I think >this will be a bigger problem than card detection. It has to go through the driver anyway. >> Not all EISA cards are relocatable after their first initialization. >> We have to deal with these anyway. > >We can. But to deal at all, we have to have an idea of the relocatability, >as noted above, and VLB cards pretending to be EISA don't give that. Sure they do. THe driver says that you can change its irq to X,Y, and Z, but that its baseaddress is fixed. This is exactly the same info that you get from the 2742. What information can't I give and why can't I? >I agree with this... my point is that EISA configuration should be >autonomously seperable from the rest of the configuration. The bus >attach should be on a per bus basis, and the lines shouldn't be >blurred by probes that cross over allowed boundries. I think it >should work on the order of SCSI bus attachment, per bus. > >I think it has to for the DEC Alpha AXP/PCI boxes: their ISA is >bridged from the PCI, not vice versa, and I know PReP/CHRP require >this, so machines based on the Motorolla chips have the same issue. >I expect there to be Intel based hardware with the same issues >soon (if it doesn't already exist somewhere). This is easy to do regardless of the fact that the 2842 is treated as an eisaconf device since as far as I know, there are no VL Alpha machines. >Yes. And bus existance is seperable for the purposes of causing a >bus attach to occur, and you don't need to attach an EISA bus (or >have the code taking space in the kernel) when you don't have an >EISA bus on your machine. When you don't have an eisabus or a 2842, the module is unloaded. >Then you must make registration variant so that the EISA code registers >the card as an ISA card. > >This defeats the ability to seperate out (and discard) the EISA bus >attach code on machines without an EISA bus, in all cases. Again, if you don't have a 2842 or an eisa motherboard, the module is unloaded. >Requiring the EISA code to probe it prevents discarding the EISA >bus attach, or only performing the bus attach when the bus exists. 8-(. If the EISA probe turns up false, there is no 2842. How does this prevent discarding the EISA lkm after its probe? > Regards, > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Mar 12 00:04:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13339 for current-outgoing; Tue, 12 Mar 1996 00:04:11 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA13326 for ; Tue, 12 Mar 1996 00:04:04 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelay-SVR4_1.3/RBCS) id JAA06671; Tue, 12 Mar 1996 09:03:22 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id JAA18605; Tue, 12 Mar 1996 09:03:19 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id JAA26728; Tue, 12 Mar 1996 09:03:18 +0100 To: current@FreeBSD.org Subject: Fwd: Draft of T/TCP BOF minutes (was: finger...) Date: Tue, 12 Mar 1996 09:03:16 +0100 Message-ID: <26727.826617796@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk For those who are sceptic about having T/TCP in our system, here's some extra information from the recent IETF meeting. T/TCP has a good chance to become a standard. The problems people experience come from the fact that ours is the first widely deployed T/TCP implementation. Thus the unpleasant job of discovering all the problems with non-conformant TCP implementations is also our `honor'. (Non-conformant here means non-conformant to the plain old TCP specifications.) Andras ------- Forwarded Message From: braden@ISI.EDU To: mankin@ISI.EDU Cc: end2end-interest@ISI.EDU, braden@ISI.EDU Subject: Draft of T/TCP BOF minutes Date: Sun, 10 Mar 1996 15:22:25 PST Los Angeles IETF Proceedings Transport Services Area Minutes of the Transaction TCP BOF (ttcp) Reported by: Bob Braden/USC Information Sciences Institute This BOF was convened to discuss a set of TCP extensions for efficient transaction-mode communication, i.e., request-response mode, which is currently documented in an Experimental RFC [Braden, R., "T/TCP -- TCP Extensions for Transactions, Functional Specification", RFC-1644, ISI, July 1994]. There has recently been interest in using T/TCP, especially as a component of performance improvements for the World Wide Web. As a result, some have suggested starting a working group to create a standard. [details deleted] The group consensus was that it would be useful to have a working group to consider standardization of T/TCP. Roughly a dozen people out of the 60 attendees indicated that they would participate in such a working group. The chair promised to report this to the Area Director. ------- End of Forwarded Message From owner-freebsd-current Tue Mar 12 00:08:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13551 for current-outgoing; Tue, 12 Mar 1996 00:08:20 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA13546 for ; Tue, 12 Mar 1996 00:08:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA17790 for ; Tue, 12 Mar 1996 00:08:04 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA06820 for current@freebsd.org; Tue, 12 Mar 1996 19:02:35 +1100 Date: Tue, 12 Mar 1996 19:02:35 +1100 From: Bruce Evans Message-Id: <199603120802.TAA06820@godzilla.zeta.org.au> To: current@freebsd.org Subject: mkisofs broken by type changes in Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk used to be independent of other headers. Now it depends on being included previously. POSIX requires to be included previously, although this is braindamaged. mkisofs doesn't include previously. This isn't a problem in -current because mkisofs includes previously and includes . POSIX and ANSI don't allow the namespace pollution in to occur unless is explicitly, included. I've fixed my version of , so mkisofs doesn't compile. Everything else in /usr/src/ compiles. Bruce From owner-freebsd-current Tue Mar 12 00:08:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13592 for current-outgoing; Tue, 12 Mar 1996 00:08:40 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA13575 for ; Tue, 12 Mar 1996 00:08:36 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id JAA06727 ; Tue, 12 Mar 1996 09:08:27 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id JAA12270 ; Tue, 12 Mar 1996 09:08:26 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.4/keltia-uucp-2.7) id IAA01228; Tue, 12 Mar 1996 08:51:04 +0100 (MET) From: Ollivier Robert Message-Id: <199603120751.IAA01228@keltia.freenix.fr> Subject: Re: panic ... panic ... panic :( To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 12 Mar 1996 08:51:04 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list), davidg@root.com In-Reply-To: <4060.826599099@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 11, 96 06:51:39 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1762 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that Jordan K. Hubbard said: > No need to apologise, you're perfectly correct. -current has been an > unstable mess. :-( It's getting better. I was able to complete a "make world" yesterday and the system seems fine for the moment. As for Lite2 integration, do the pending socket changes will force us to recompile anything that use them or will the change be just an internal one? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #6: Mon Mar 11 20:18:10 MET 1996 From owner-freebsd-current Tue Mar 12 00:21:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA14306 for current-outgoing; Tue, 12 Mar 1996 00:21:07 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA14266 for ; Tue, 12 Mar 1996 00:20:53 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA29493 for ; Tue, 12 Mar 1996 09:20:50 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA02457 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 09:20:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA03752 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 09:18:30 +0100 (MET) From: J Wunsch Message-Id: <199603120818.JAA03752@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 09:18:30 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603120407.PAA28341@godzilla.zeta.org.au> from "Bruce Evans" at Mar 12, 96 03:07:50 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >Hmm, there was a saying the running getty on /dev/console used to be > >totally broken. Bruce? Ever tried it lately? > > Not lately. I use syscons, which still has the hack of using a special > minor device for the console so that /dev/console is a little different > from /dev/vt0. I think there is nothing special for pcvt, so /dev/vt0 > is the console. ...and i've been one of the guys who never had problems in running a getty on /dev/console. Though you've once convinced me that it was broken for pcvt, too (i only didn't really notice). I've never looked again into this. I know of some commercial (non-PC) systems that have a getty running on /dev/console. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 00:29:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA14661 for current-outgoing; Tue, 12 Mar 1996 00:29:21 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA14653 for ; Tue, 12 Mar 1996 00:29:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id AAA19361; Tue, 12 Mar 1996 00:28:49 -0800 Message-Id: <199603120828.AAA19361@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Ollivier Robert cc: jkh@time.cdrom.com (Jordan K. Hubbard), freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: Re: panic ... panic ... panic :( In-reply-to: Your message of "Tue, 12 Mar 1996 08:51:04 +0100." <199603120751.IAA01228@keltia.freenix.fr> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 12 Mar 1996 00:28:49 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It seems that Jordan K. Hubbard said: >> No need to apologise, you're perfectly correct. -current has been an >> unstable mess. :-( > >It's getting better. I was able to complete a "make world" yesterday and >the system seems fine for the moment. > >As for Lite2 integration, do the pending socket changes will force us to >recompile anything that use them or will the change be just an internal one? The socket changes are not in any way related to the Lite-2 work that Jeff is doing (other than perhaps getting in his way). Both the Lite-2 integration and the socket changes will require that utilities such as ps, w, libkvm, netstat, and others be rebuilt. ...but this is a fact of life for -current users and should come as no surprise. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Mar 12 00:29:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA14696 for current-outgoing; Tue, 12 Mar 1996 00:29:38 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA14691 Tue, 12 Mar 1996 00:29:33 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA28795; Tue, 12 Mar 1996 09:13:53 +0100 Message-Id: <199603120813.JAA28795@ra.dkuug.dk> Subject: Re: Native & Linux ELF support finally there... To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 12 Mar 1996 09:13:53 +0100 (MET) Cc: sos@freebsd.org, current@freebsd.org In-Reply-To: <199603111840.TAA04093@keltia.freenix.fr> from "Ollivier Robert" at Mar 11, 96 07:40:13 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Ollivier Robert who wrote: > > It seems that sos@freebsd.org said: > > FreeBSD-current now has ELF support. This means that we are now > > able to run native FreeBSD ELF binaries (generated with John > > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux > ^^^^^^^^^^^^ > When this will be available ? Has been for a month or so: ftp://ftp.polstra.com/pub/FreeBSD/elfkit/* -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Mar 12 00:51:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15844 for current-outgoing; Tue, 12 Mar 1996 00:51:29 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA15825 for ; Tue, 12 Mar 1996 00:51:15 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA00422 for ; Tue, 12 Mar 1996 09:50:39 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA02595 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 09:50:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA04064 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 09:36:52 +0100 (MET) From: J Wunsch Message-Id: <199603120836.JAA04064@uriah.heep.sax.de> Subject: Re: Native & Linux ELF support finally there... To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 09:36:52 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603120016.LAA17014@godzilla.zeta.org.au> from "Bruce Evans" at Mar 12, 96 11:16:08 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >For FreeBSD bins ? nothing as fas as I can tell, It helped Linux > > Then why is imgact_elf.c `standard'? :-) It bloats the kernel another > 4.5K. Only until it can get the attribute ``__pageable''. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 00:51:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15910 for current-outgoing; Tue, 12 Mar 1996 00:51:45 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA15876 for ; Tue, 12 Mar 1996 00:51:38 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA00441; Tue, 12 Mar 1996 09:50:51 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA02603; Tue, 12 Mar 1996 09:50:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA04179; Tue, 12 Mar 1996 09:45:22 +0100 (MET) From: J Wunsch Message-Id: <199603120845.JAA04179@uriah.heep.sax.de> Subject: Re: system() broken while mmap()ing something To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 09:45:21 +0100 (MET) Cc: dawes@rf900.physics.usyd.edu.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603112320.XAA00292@dyson.iquest.net> from "John S. Dyson" at Mar 11, 96 11:20:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: > I have committed a temporary fix for the problem. Will try it soon, thanks! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 01:23:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA18340 for current-outgoing; Tue, 12 Mar 1996 01:23:20 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA18324 for ; Tue, 12 Mar 1996 01:23:11 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA01305; Tue, 12 Mar 1996 10:20:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA02758; Tue, 12 Mar 1996 10:20:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA04385; Tue, 12 Mar 1996 09:56:15 +0100 (MET) From: J Wunsch Message-Id: <199603120856.JAA04385@uriah.heep.sax.de> Subject: Re: gzip'ed exec problem on 960303-SNAP To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 09:56:15 +0100 (MET) Cc: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603120655.PAA11713@frig.mt.cs.keio.ac.jp> from "HOSOKAWA Tatsumi" at Mar 12, 96 03:55:18 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As HOSOKAWA Tatsumi wrote: > > I found that my 960303-SNAP box always crashes when it exec's > gzip'ed binaries. Are there any patches to fix this problem? No, it's already lurking around for very long. That's also the reason why the fixit floppy doesn't work for all recent SNAPs. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 05:48:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA14658 for current-outgoing; Tue, 12 Mar 1996 05:48:07 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA14648 for current; Tue, 12 Mar 1996 05:48:06 -0800 (PST) From: John Dyson Message-Id: <199603121348.FAA14648@freefall.freebsd.org> Subject: VM map corruption problem To: current Date: Tue, 12 Mar 1996 05:48:06 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have just committed a fix for the mapp corruption problem. There is still a problem that is appearing as a "freeing busy page" problem. Will work on that tonight. The system should be much nicer with the vm_map.c fix just committed though. John From owner-freebsd-current Tue Mar 12 06:43:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA18863 for current-outgoing; Tue, 12 Mar 1996 06:43:47 -0800 (PST) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA18858 for ; Tue, 12 Mar 1996 06:43:45 -0800 (PST) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id JAA04133; Tue, 12 Mar 1996 09:43:40 -0500 for Date: Tue, 12 Mar 1996 09:43:40 -0500 From: "Frank E. Terhaar-Yonkers" Message-Id: <199603121443.JAA04133@robin.mcnc.org.mcnc.org> To: current@FreeBSD.org Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk All this talk about motherboards ... I've been salivating over advertisements of PCI "586" mb's at < $200. Using Cyrix, Nexgen, etc chips. Anyone had experience with any of these? Are we talking snake oil? Or, are these folks really putting it to Intel? TIA - Frank >> > Nope, IMHO, there are no _good_ 486 boards left on the market, the last >> > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not >> > been able to get any more of them. > >I agree. What happened to all the good Mylex and Happauge! EISA >motherboards. 8 simms standard, 8 EISA slots, Weitek sockets. One of the >best boards I saw was the Happauge 4860 motherboard. It had an i486 + an >i860 risc processor. > >== Chris Layne ============================================================= >== coredump@nervosa.com ================ http://www.nervosa.com/~coredump == > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Tue Mar 12 07:45:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23542 for current-outgoing; Tue, 12 Mar 1996 07:45:24 -0800 (PST) Received: from heist.demon.co.uk (heist.demon.co.uk [158.152.187.50]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA23530 for ; Tue, 12 Mar 1996 07:45:19 -0800 (PST) Received: (from iain@localhost) by heist.demon.co.uk (8.6.12/8.6.12) id PAA16767 for freebsd-current@freebsd.org; Tue, 12 Mar 1996 15:36:48 GMT From: Iain Baird Message-Id: <199603121536.PAA16767@heist.demon.co.uk> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: freebsd-current@freebsd.org Date: Tue, 12 Mar 1996 15:36:48 +0000 (GMT) In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 11, 96 01:25:42 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes said: > > Can you recommend a good 486 motherboard (preferably PCI)? > > Nope, IMHO, there are no _good_ 486 boards left on the market, the last > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not > been able to get any more of them. FYI, I have a Gigabyte GA486-AMS. It has been rock solid with 2.1.0-RELEASE and AHA-2940 using both AMD DX4-120 and AMD 5x86-133 with L1 and L2 write back enabled. I had to upgrade to the latest BIOS to get support for the 5x86. I don't know whether this meets Rod's criteria for a _good_ board, but it works well for me. iain From owner-freebsd-current Tue Mar 12 07:56:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA24428 for current-outgoing; Tue, 12 Mar 1996 07:56:41 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA24421 for ; Tue, 12 Mar 1996 07:56:37 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA01641; Tue, 12 Mar 1996 10:56:30 -0500 Date: Tue, 12 Mar 1996 10:56:30 -0500 From: "Garrett A. Wollman" Message-Id: <9603121556.AA01641@halloran-eldar.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: cvs commit: src/usr.bin/su su.c In-Reply-To: <1660.826612757@time.cdrom.com> References: <199603120629.OAA02941@jhome.DIALix.COM> <1660.826612757@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Hmmm. Sonofagun! Still a couple of things here though.. > First, the -c option is undocumented. If you get a usage string out > of it, it won't list -c among the supported options, nor is it in the > man page. It's not an option for `su', it's an option for `sh' and `csh'. Everything after the user name on the command line is interpreted as arguments for the shell that gets started. -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 12 08:26:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA26476 for current-outgoing; Tue, 12 Mar 1996 08:26:13 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA26467 for ; Tue, 12 Mar 1996 08:26:06 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA07546; Tue, 12 Mar 1996 11:25:58 -0500 Date: Tue, 12 Mar 1996 11:25:58 -0500 From: "Garrett A. Wollman" Message-Id: <9603121625.AA07546@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/sys conf.h In-Reply-To: <199603120520.QAA31894@godzilla.zeta.org.au> References: <199603120520.QAA31894@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> (struct mbuf *)cmd, (struct mbuf *)data, (struct mbuf *)0)); > Actually, this is another point in favor of not making the ioctl cmd > field long. Longs are less likely to fit in pointers than ints. The > above would certainly fail for 16-bit pointers. So what? We are never going to have to deal with this situation. The only situations of relevance are: 32-bit int, 32-bit long, 32-bit pointer (all 32-bit systems) 32-bit int, 64-bit long, 64-bit pointer (Alpha) 64-bit int, 64-bit long, 64-bit pointer (Cray? ...will happen some day) It works fine in the first case, and it avoids a GCC warning in the second case. Sounds like the right thing to me. -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 12 08:28:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA26804 for current-outgoing; Tue, 12 Mar 1996 08:28:54 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA26797 for ; Tue, 12 Mar 1996 08:28:50 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA12070; Tue, 12 Mar 1996 11:28:40 -0500 Date: Tue, 12 Mar 1996 11:28:40 -0500 From: "Garrett A. Wollman" Message-Id: <9603121628.AA12070@halloran-eldar.lcs.mit.edu> To: Paul Traina Cc: current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-Reply-To: <199603120135.RAA03399@precipice.shockwave.com> References: <199603112038.NAA03837@phaeton.artisoft.com> <199603120135.RAA03399@precipice.shockwave.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > It interoperates fine with non-broken TCP implementations. I'm really glad > that finger was chosen... of course, it should have been DOCUMENTED. :-) Well, if you think about it, it's pretty clear that `finger' was about the only service which /could/ be changed in this way. Oh, FTP data connections might be T/TCP-ized as well, but it seemed to me that people were rather more likely to get hurt in that instance, so I decided against it. I still haven't gotten around to doing a Sun RPC transport module for T/TCP. -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 12 08:41:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA27761 for current-outgoing; Tue, 12 Mar 1996 08:41:50 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA27752 for ; Tue, 12 Mar 1996 08:41:48 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.6.12/8.6.9) id KAA16360; Tue, 12 Mar 1996 10:39:24 -0600 From: Bob Willcox Message-Id: <199603121639.KAA16360@luke.pmr.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Mar 1996 10:39:23 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "Mar 11, 96 01:25:42 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes wrote: ... > > Such as what, the PVI-486AP4, out of production for 4 months, the only > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > I do not classify as a good board due to only 2 Simm sockets and if I > recall correctly a cache coherency problem in the Sis 496/497 chipset. What should I look for on the possible cache coherency problem? I have an ASUS PVI-486SP3 here running 2.1-STABLE (w/o problems, so far). -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-current Tue Mar 12 08:45:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA27985 for current-outgoing; Tue, 12 Mar 1996 08:45:07 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA27980 for ; Tue, 12 Mar 1996 08:45:05 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA12584; Tue, 12 Mar 1996 11:44:45 -0500 Date: Tue, 12 Mar 1996 11:44:45 -0500 From: "Garrett A. Wollman" Message-Id: <9603121644.AA12584@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: "Garrett A. Wollman" , freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... In-Reply-To: <199603112042.WAA04844@grumble.grondar.za> References: <199603112042.WAA04844@grumble.grondar.za> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > My philosohy on this one was that if there was not an acl entry for > the guy, no matter what, then he wasn't allowed in. I'm sure I could > look for the above case and add it in. Others' comments? How does this > new variant "feel" to you? Many sites may not want to use the Kerberized `su' for private reasons of their own. `su' should take the non-existence of ~root/.klogin as an indication of this and go back to UNIX / S/Key authentication. (Just as one example, a site may want to force everyone to use S/Key for `su', since they can't trust the network connection over which a user is logged in.) -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 12 09:03:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA28872 for current-outgoing; Tue, 12 Mar 1996 09:03:11 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA28861 for ; Tue, 12 Mar 1996 09:02:58 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id TAA13307; Tue, 12 Mar 1996 19:01:34 +0200 (SAT) Message-Id: <199603121701.TAA13307@grumble.grondar.za> To: "Garrett A. Wollman" cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! Please check... Date: Tue, 12 Mar 1996 19:01:32 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Garrett A. Wollman" wrote: > Many sites may not want to use the Kerberized `su' for private reasons > of their own. `su' should take the non-existence of ~root/.klogin as an > indication of this and go back to UNIX / S/Key authentication. (Just > as one example, a site may want to force everyone to use S/Key for > `su', since they can't trust the network connection over which a user > is logged in.) This is reasonable. In fact this is the way it is now. :-) M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Mar 12 09:41:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00691 for current-outgoing; Tue, 12 Mar 1996 09:41:12 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00686 for ; Tue, 12 Mar 1996 09:41:08 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA13988; Tue, 12 Mar 1996 09:40:04 -0800 From: "Rodney W. Grimes" Message-Id: <199603121740.JAA13988@GndRsh.aac.dev.com> Subject: Re: finger and 2.2-960303-SNAP To: pst@shockwave.com (Paul Traina) Date: Tue, 12 Mar 1996 09:40:03 -0800 (PST) Cc: terry@lambert.org, roberto@keltia.freenix.fr, adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org In-Reply-To: <199603120135.RAA03399@precipice.shockwave.com> from "Paul Traina" at Mar 11, 96 05:35:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > From: Terry Lambert > Subject: Re: finger and 2.2-960303-SNAP > > It seems that Andrew Foster said: > > > And yet the old finger works fine, as does fingering from most other host > >>s > > > I've tried. > > > > Finger has been changed (or fixed :-)) to use T/TCP recently... > > "Fixed" is subjective. It saves one response packet and loses > interoperability. 8-(. > > It interoperates fine with non-broken TCP implementations. I'm really glad > that finger was chosen... of course, it should have been DOCUMENTED. :-) > And an option added that disables the use of T/TCP so that a user can finger a broken TCP system. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Mar 12 09:49:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01211 for current-outgoing; Tue, 12 Mar 1996 09:49:46 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA01201 for ; Tue, 12 Mar 1996 09:49:42 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA13997; Tue, 12 Mar 1996 09:45:55 -0800 From: "Rodney W. Grimes" Message-Id: <199603121745.JAA13997@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 12 Mar 1996 09:45:55 -0800 (PST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603120453.PAA25996@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 12, 96 03:23:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Rodney W. Grimes stands accused of saying: > > > I noticed ASUS seems to have several other offerings besides the SP3G.. > > > > Such as what, the PVI-486AP4, out of production for 4 months, the only > > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > > I do not classify as a good board due to only 2 Simm sockets and if I > > recall correctly a cache coherency problem in the Sis 496/497 chipset. > > Er, we have a PVI-486SP3 here; the SIMM limit is mildly annoying, but > (w/Intel DX4/100) appears to be rock-solid. > > The box in question has run multiple 'make world's; 16M/NCR SCSI etc. > > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 10 on pci0:11 > ... Humm.. what mode is your external cache set to... Write Through or Write Back? Perhaps SiS has fixed this in later revisions of the chip set, or I am confusing it with another chip set. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Mar 12 10:17:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA02987 for current-outgoing; Tue, 12 Mar 1996 10:17:18 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA02977 for ; Tue, 12 Mar 1996 10:17:12 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA14081; Tue, 12 Mar 1996 10:15:03 -0800 From: "Rodney W. Grimes" Message-Id: <199603121815.KAA14081@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: iain@heist.demon.co.uk (Iain Baird) Date: Tue, 12 Mar 1996 10:15:03 -0800 (PST) Cc: freebsd-current@freebsd.org In-Reply-To: <199603121536.PAA16767@heist.demon.co.uk> from "Iain Baird" at Mar 12, 96 03:36:48 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Rodney W. Grimes said: > > > Can you recommend a good 486 motherboard (preferably PCI)? > > > > Nope, IMHO, there are no _good_ 486 boards left on the market, the last > > _good_ 486 PCI board I could get was the ASUS PCI/I-486SP3G and I have not > > been able to get any more of them. > > FYI, I have a Gigabyte GA486-AMS. It has been rock solid with > 2.1.0-RELEASE and AHA-2940 using both AMD DX4-120 and AMD 5x86-133 > with L1 and L2 write back enabled. I had to upgrade to the latest > BIOS to get support for the 5x86. > > I don't know whether this meets Rod's criteria for a _good_ board, > but it works well for me. Gigabyte stopped production of 486 boards in January, or so I was told by my local Gigabyte distributor. The -AMS was a reasonable board, but fell short on performance when compared to the ASUS PCI/I-486SP3G on memory intensive benchmarks. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Mar 12 10:19:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03170 for current-outgoing; Tue, 12 Mar 1996 10:19:48 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA03161 for ; Tue, 12 Mar 1996 10:19:45 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA14107; Tue, 12 Mar 1996 10:17:00 -0800 From: "Rodney W. Grimes" Message-Id: <199603121817.KAA14107@GndRsh.aac.dev.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: bob@luke.pmr.com (Bob Willcox) Date: Tue, 12 Mar 1996 10:17:00 -0800 (PST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603121639.KAA16360@luke.pmr.com> from "Bob Willcox" at Mar 12, 96 10:39:23 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Rodney W. Grimes wrote: > ... > > > > Such as what, the PVI-486AP4, out of production for 4 months, the only > > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > > I do not classify as a good board due to only 2 Simm sockets and if I > > recall correctly a cache coherency problem in the Sis 496/497 chipset. > > What should I look for on the possible cache coherency problem? I have > an ASUS PVI-486SP3 here running 2.1-STABLE (w/o problems, so far). This looks to be a confusion of chip sets on my part. If you are running with a bus master scsi controller and are not seeing random sig 10 or 11's, then there is probably nothing wrong. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Mar 12 10:20:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03388 for current-outgoing; Tue, 12 Mar 1996 10:20:52 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA03378 for ; Tue, 12 Mar 1996 10:20:50 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.6.12/8.6.9) id MAA16909; Tue, 12 Mar 1996 12:18:45 -0600 From: Bob Willcox Message-Id: <199603121818.MAA16909@luke.pmr.com> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Mar 1996 12:18:45 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603121817.KAA14107@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "Mar 12, 96 10:17:00 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes wrote: > > > > Rodney W. Grimes wrote: > > ... > > > > > > Such as what, the PVI-486AP4, out of production for 4 months, the only > > > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > > > I do not classify as a good board due to only 2 Simm sockets and if I > > > recall correctly a cache coherency problem in the Sis 496/497 chipset. > > > > What should I look for on the possible cache coherency problem? I have > > an ASUS PVI-486SP3 here running 2.1-STABLE (w/o problems, so far). > > This looks to be a confusion of chip sets on my part. If you are running > with a bus master scsi controller and are not seeing random sig 10 or 11's, > then there is probably nothing wrong. Yep. Its got a NCR 810 adapter in it. -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-current Tue Mar 12 10:49:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA05726 for current-outgoing; Tue, 12 Mar 1996 10:49:52 -0800 (PST) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA05719 for ; Tue, 12 Mar 1996 10:49:49 -0800 (PST) Received: from caught.inna.net (caught.inna.net [206.151.66.7]) by tyger.inna.net (8.7.3/8.7.3) with SMTP id NAA07169; Tue, 12 Mar 1996 13:50:26 -0500 (EST) Date: Tue, 12 Mar 1996 13:49:33 -0500 (EST) From: Thomas Arnold To: "Frank E. Terhaar-Yonkers" cc: current@FreeBSD.org Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) In-Reply-To: <199603121443.JAA04133@robin.mcnc.org.mcnc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Mar 1996, Frank E. Terhaar-Yonkers wrote: > All this talk about motherboards ... > > I've been salivating over advertisements of PCI "586" mb's at < $200. > Using Cyrix, Nexgen, etc chips. Anyone had experience with any of these? > > Are we talking snake oil? Or, are these folks really putting it to Intel? I have two machines running here using the 586 type chips. One machine uses the AMD X5 chip otherwise known as yje AMD 5x86-133. Nothing fancu about this chip, just a 133mhz 486. The second machine uses the Cyrix 5x86-120. I have been very impressed with this chip EXCEPT for the inability of Cyrix to say "Here is a PCI motherbboard that works properly". It took me 3 motherboards and as many BIOSes to get a working board :-(. HOWEVER, a kernel compile takes about 12 minutes on the machine. For a speed comparision the 100 next to it takes about 9.5mins and about 8 minutes for our P-120. So Cyrix's claims that it is roughly P-90 speed seems to be close to the mark. The X5 isn't as impressive but motherboards seem to support it better. Just my opinion, mileage may vary. Do not fold bend spindle or mutilate. +-----------------------------------------------+ : Tom Arnold - No relation to Rosanne : : SysAdmin/Pres - TBI, Ltd ( inna.net ) : : An ISP serving the Virginia Middle Penninsula : +-----------------------------------------------+ From owner-freebsd-current Tue Mar 12 11:52:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA10119 for current-outgoing; Tue, 12 Mar 1996 11:52:00 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA10112 for ; Tue, 12 Mar 1996 11:51:57 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id GAA02539; Wed, 13 Mar 1996 06:46:25 +1100 Date: Wed, 13 Mar 1996 06:46:25 +1100 From: Bruce Evans Message-Id: <199603121946.GAA02539@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: cvs commit: src/sys/sys conf.h Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> (struct mbuf *)cmd, (struct mbuf *)data, (struct mbuf *)0)); >> Actually, this is another point in favor of not making the ioctl cmd >> field long. Longs are less likely to fit in pointers than ints. The >> above would certainly fail for 16-bit pointers. >So what? We are never going to have to deal with this situation. The >only situations of relevance are: >32-bit int, 32-bit long, 32-bit pointer (all 32-bit systems) >32-bit int, 64-bit long, 64-bit pointer (Alpha) >64-bit int, 64-bit long, 64-bit pointer (Cray? ...will happen some day) 64-bit int, 128-bit long, 96-bit pointer (? ...will happen some day) >It works fine in the first case, and it avoids a GCC warning in the >second case. Sounds like the right thing to me. It doesn't help at runtime, and may waste space and time. Bruce From owner-freebsd-current Tue Mar 12 12:27:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12073 for current-outgoing; Tue, 12 Mar 1996 12:27:50 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12063 for ; Tue, 12 Mar 1996 12:27:47 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA12235; Tue, 12 Mar 1996 15:27:40 -0500 Date: Tue, 12 Mar 1996 15:27:40 -0500 From: "Garrett A. Wollman" Message-Id: <9603122027.AA12235@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/sys conf.h In-Reply-To: <199603121946.GAA02539@godzilla.zeta.org.au> References: <199603121946.GAA02539@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> 32-bit int, 32-bit long, 32-bit pointer (all 32-bit systems) >> 32-bit int, 64-bit long, 64-bit pointer (Alpha) >> 64-bit int, 64-bit long, 64-bit pointer (Cray? ...will happen some day) > 64-bit int, 128-bit long, 96-bit pointer (? ...will happen some day) Doubtful. >> It works fine in the first case, and it avoids a GCC warning in the >> second case. Sounds like the right thing to me. > It doesn't help at runtime, and may waste space and time. For any sane architecture, that seems unlikely. What might happen on insane architectures doesn't bear thinking about. -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 12 12:44:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13934 for current-outgoing; Tue, 12 Mar 1996 12:44:05 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA13804 for ; Tue, 12 Mar 1996 12:44:00 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14796(5)>; Tue, 12 Mar 1996 12:43:22 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Tue, 12 Mar 1996 12:43:06 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: "Rodney W. Grimes" cc: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Tue, 12 Mar 1996 09:40:03 PST." <199603121740.JAA13988@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Mar 1996 12:43:00 PST From: Bill Fenner Message-Id: <96Mar12.124306pst.177478@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >And an option added that disables the use of T/TCP so that a user can >finger a broken TCP system. You're right! Why don't we call it net.inet.tcp.rfc1644? Bill From owner-freebsd-current Tue Mar 12 13:18:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17465 for current-outgoing; Tue, 12 Mar 1996 13:18:34 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA17453 for ; Tue, 12 Mar 1996 13:18:28 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA05823; Wed, 13 Mar 1996 08:11:45 +1100 Date: Wed, 13 Mar 1996 08:11:45 +1100 From: Bruce Evans Message-Id: <199603122111.IAA05823@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: cvs commit: src/sys/sys conf.h Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> [using u_longs where u_ints are sufficient] >> It doesn't help at runtime, and may waste space and time. >For any sane architecture, that seems unlikely. What might happen on >insane architectures doesn't bear thinking about. Every 32-bit system should have relatively slow 64-bit longs implemented in software and no long longs. The i386 architecture provides many examples where less commonly used types are inefficient. You have to think about it even though it is insane :-). Bruce From owner-freebsd-current Tue Mar 12 13:24:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA18114 for current-outgoing; Tue, 12 Mar 1996 13:24:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA18107 for ; Tue, 12 Mar 1996 13:24:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA06574; Tue, 12 Mar 1996 14:14:32 -0700 From: Terry Lambert Message-Id: <199603122114.OAA06574@phaeton.artisoft.com> Subject: Re: finger and 2.2-960303-SNAP To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 12 Mar 1996 14:14:31 -0700 (MST) Cc: terry@lambert.org, adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org In-Reply-To: <199603112249.XAA20680@keltia.freenix.fr> from "Ollivier Robert" at Mar 11, 96 11:49:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > "Fixed" is subjective. It saves one response packet and loses > > interoperability. 8-(. > > Only with broken TCP implementations like the Annex's. We'll never see the > broken code change if no one complain and make them fix their bugs. This is a wonderful theory. To make it work, wouldn't the bug reports have to go to their lists instead of ours? 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 12 13:39:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19847 for current-outgoing; Tue, 12 Mar 1996 13:39:43 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19836 Tue, 12 Mar 1996 13:39:37 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA06630; Tue, 12 Mar 1996 14:35:55 -0700 From: Terry Lambert Message-Id: <199603122135.OAA06630@phaeton.artisoft.com> Subject: Re: Native & Linux ELF support finally there... To: amurai@spec.co.jp Date: Tue, 12 Mar 1996 14:35:54 -0700 (MST) Cc: sos@freebsd.org, current@freebsd.org In-Reply-To: <199603120235.LAA02530@tama.spec.co.jp> from "Atsushi Murai" at Mar 12, 96 11:35:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > After a hectic week, Peter Wemm and I are proud to announce that > > FreeBSD-current now has ELF support. This means that we are now > > able to run native FreeBSD ELF binaries (generated with John > > Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux > > QUAKE finally works, at least as far as Peter & I has tried it > > (Hey I dont have time to play) > > Sounds great! But is there any way/plan to exclude this support code > during a compiling kernel(i.e options COMPAT_LINUX) ? It's will be > helpful for optimizing a size of kernel under the restricted memory ;-) The "COMPAT_LINUX" flag crap strikes me as just that: *crap*. It affects 4 files: 1) i386/i386/exception.s This small amount of code is here because someone didn't inline it or put it in a .s for the Linux ABI module itself. It should be possible to put this anywhere, including a file that is ld -r'ed into the single Linux ABI module. 2) i386/i386/trap.c This code is the code that is called by the exception.s code; there is exception.s code at all because it wasn't inlined as a naked function here (ie: no normal C preamble/postamble, but still C code). 3) i386/i386/machdep.c This code is two lines: one external declaration for the functions that could be dynamically assigned via function pointer, if nothing else, like the NFS loadable module functions (which are also bogusly wired his way for the lease code). The line is a "setidt". It should be possible to set/unset idt's from the LKM init/deinit routines. 4) kern/imgact_aout.c This is here because the image activators are bogusly called to look at magic numbers (my original LKM design had the magic numbers in a list and the lookup taking place in the list to hit the image activator). Using the original design, adding Linux image activation would be done by adding a list item that listed the magic numbers for Linux images and referenced the same activation function. This would also be removed when the module was unloaded. At worst, the activator chould be a stub that diddles the magic number then calls the a.out activator (this really would be silly because of NetBSD and BSDI and NetBSD's alternate platform support being usable using processor emulation environments that cause a loader to mmap the program image into an emulation space... ie SPARC or MIPS or PPC binaries on FreeBSD, or vice versa). The upshot of all this is that the COMPAT_LINUX flag should go away; it's a pain in the ass to have to rebuild a kernel in order to run Linux binary compatability. The change of the magic lookup would have the pleasent side-effect of not coring Linux program when the ABI module wasn't loaded, as is currently the case. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 12 13:47:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20925 for current-outgoing; Tue, 12 Mar 1996 13:47:24 -0800 (PST) Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20919 for ; Tue, 12 Mar 1996 13:47:22 -0800 (PST) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.7.4/8.6.10) with ESMTP id NAA01034; Tue, 12 Mar 1996 13:45:18 -0800 (PST) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id NAA13301; Tue, 12 Mar 1996 13:45:17 -0800 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id NAA07339; Tue, 12 Mar 1996 13:43:51 -0800 Message-Id: <199603122143.NAA07339@cozumel.tcs.com> Subject: Re: COMCONSOLE: a patch and a problem To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 12 Mar 1996 13:43:50 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603120818.JAA03752@uriah.heep.sax.de> from "J Wunsch" at Mar 12, 96 09:18:30 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: | | As Bruce Evans wrote: | | > >Hmm, there was a saying the running getty on /dev/console used to be | > >totally broken. Bruce? Ever tried it lately? | > | > Not lately. I use syscons, which still has the hack of using a special | > minor device for the console so that /dev/console is a little different | > from /dev/vt0. I think there is nothing special for pcvt, so /dev/vt0 | > is the console. | | ...and i've been one of the guys who never had problems in running a | getty on /dev/console. Though you've once convinced me that it was | broken for pcvt, too (i only didn't really notice). I've never looked | again into this. | | I know of some commercial (non-PC) systems that have a getty running | on /dev/console. I second this in that I've seen this on other work-stations as well. It is cute to see getty in your xconsole window. Also I've been using syscons and not pcvt so I should take a look at that but so far I haven't experienced a problem with syscon. I'll also take a look at syscons and see why it should be different. I'll try to put my patches together this weekend, I'm pretty tied up this week. I also want to take a look at the kernel to see if I can save the last boot mode. This way you can boot -h to get the serial port and -g to get the graphics console and the kernel would remember that for the next boot. So far no one has objected about the potential modem problem so that sounds good. Doug A. From owner-freebsd-current Tue Mar 12 14:41:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25844 for current-outgoing; Tue, 12 Mar 1996 14:41:19 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA25836 for ; Tue, 12 Mar 1996 14:41:14 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA06805; Tue, 12 Mar 1996 15:38:18 -0700 From: Terry Lambert Message-Id: <199603122238.PAA06805@phaeton.artisoft.com> Subject: Re: finger and 2.2-960303-SNAP To: fenner@parc.xerox.com (Bill Fenner) Date: Tue, 12 Mar 1996 15:38:17 -0700 (MST) Cc: rgrimes@gndrsh.aac.dev.com, current@freebsd.org In-Reply-To: <96Mar12.124306pst.177478@crevenia.parc.xerox.com> from "Bill Fenner" at Mar 12, 96 12:43:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >And an option added that disables the use of T/TCP so that a user can > >finger a broken TCP system. > > You're right! Why don't we call it net.inet.tcp.rfc1644? Tee hee hee. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 12 14:51:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26690 for current-outgoing; Tue, 12 Mar 1996 14:51:31 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26681 for ; Tue, 12 Mar 1996 14:51:27 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA27926 for ; Tue, 12 Mar 1996 23:51:20 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA09973 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 23:51:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id XAA05836 for freebsd-current@FreeBSD.org; Tue, 12 Mar 1996 23:16:28 +0100 (MET) From: J Wunsch Message-Id: <199603122216.XAA05836@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 12 Mar 1996 23:16:27 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603122143.NAA07339@cozumel.tcs.com> from "Douglas Ambrisko" at Mar 12, 96 01:43:50 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Douglas Ambrisko wrote: > I'll also take a look at syscons and see why it should > be different. syscons uses a different tty structure for the console than for VT1. > I'll try to put my patches together this weekend, I'm pretty tied up this > week. I also want to take a look at the kernel to see if I can save > the last boot mode. This way you can boot -h to get the serial port and -g > to get the graphics console and the kernel would remember that for the > next boot. By now, -h is a toggle (btw.). Most people would hesitate if you always write back the boot block, just to store a single bit in it. Well, van Gilluwe reports bit 2 of the so-called ``equipment byte'' in the CMOS (offset 0x14) as `unused'. Perhaps we could use it to store the serial console flag there? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 15:00:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA27592 for current-outgoing; Tue, 12 Mar 1996 15:00:06 -0800 (PST) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA27556 for ; Tue, 12 Mar 1996 15:00:03 -0800 (PST) Received: from Early-Bird-1.Think.COM by mail.think.com; Tue, 12 Mar 96 18:00:00 -0500 Received: from compound (fergus-26.dialup.cfa.org) by Early-Bird.Think.COM; Tue, 12 Mar 96 17:59:55 EST Received: (from alk@localhost) by compound (8.6.12/8.6.112) id RAA14189; Tue, 12 Mar 1996 17:00:10 -0600 Date: Tue, 12 Mar 1996 17:00:10 -0600 Message-Id: <199603122300.RAA14189@compound> From: Tony Kimball To: freebsd-current@freefall.freebsd.org, fty@mcnc.org Subject: 5x86s Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: "Frank E. Terhaar-Yonkers" Date: Tue, 12 Mar 1996 09:43:40 -0500 All this talk about motherboards ... I've been salivating over advertisements of PCI "586" mb's at < $200. Using Cyrix, Nexgen, etc chips. Anyone had experience with any of these? Are we talking snake oil? Or, are these folks really putting it to Intel? My Cyrix 5x86-120GP chip runs about as fast as a Pentium would at 86MHz, for my applications. A Cyrix 150MHz chip (if there is one) should toast my P100. I was unlucky with my first MoBo, a UMC, as it did not support bus mastering DMA on ISA, and I needed to use a 1542. I returned it and purchased an ASUS. Don't think the bum MoBo prob is unique to 486, though! Half the Taiwanese Pentium boards are next to useless as well. It is definitely worth a few bucks to find the right MoBo before you waste time on a cheapie that doesn't work. I'm unlikely to ever buy another Intel CPU, since I don't like the way they treat their employees, and I have other options. I'll still get stuck with their glue a lot, I suppose. From owner-freebsd-current Tue Mar 12 15:07:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA28396 for current-outgoing; Tue, 12 Mar 1996 15:07:49 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA28391 Tue, 12 Mar 1996 15:07:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id PAA04367; Tue, 12 Mar 1996 15:07:15 -0800 (PST) To: Terry Lambert cc: amurai@spec.co.jp, sos@FreeBSD.org, current@FreeBSD.org Subject: Re: Native & Linux ELF support finally there... In-reply-to: Your message of "Tue, 12 Mar 1996 14:35:54 MST." <199603122135.OAA06630@phaeton.artisoft.com> Date: Tue, 12 Mar 1996 15:07:14 -0800 Message-ID: <4365.826672034@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The upshot of all this is that the COMPAT_LINUX flag should go away; > it's a pain in the ass to have to rebuild a kernel in order to run > Linux binary compatability. I agree. In connection with the current Linux emulation, this is the #1 question I get ("I try to run my Linux binary and it says can't execute binary file, what do I doooooooo?!"). Jordan From owner-freebsd-current Tue Mar 12 15:39:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA01912 for current-outgoing; Tue, 12 Mar 1996 15:39:40 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA01894 for ; Tue, 12 Mar 1996 15:39:33 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA14481; Tue, 12 Mar 1996 15:39:09 -0800 From: "Rodney W. Grimes" Message-Id: <199603122339.PAA14481@GndRsh.aac.dev.com> Subject: Re: COMCONSOLE: a patch and a problem To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 12 Mar 1996 15:39:08 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603122216.XAA05836@uriah.heep.sax.de> from "J Wunsch" at Mar 12, 96 11:16:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > As Douglas Ambrisko wrote: > > > I'll also take a look at syscons and see why it should > > be different. > > syscons uses a different tty structure for the console than for VT1. > > > I'll try to put my patches together this weekend, I'm pretty tied up this > > week. I also want to take a look at the kernel to see if I can save > > the last boot mode. This way you can boot -h to get the serial port and -g > > to get the graphics console and the kernel would remember that for the > > next boot. > > By now, -h is a toggle (btw.). > > Most people would hesitate if you always write back the boot block, > just to store a single bit in it. Well, van Gilluwe reports bit 2 of > the so-called ``equipment byte'' in the CMOS (offset 0x14) as > `unused'. Perhaps we could use it to store the serial console flag > there? :) Absolutely not. Storing stuff in the CMOS by an OS is a nasty and very risky thing to do. It may be unused today, but that is the BIOS writters land, and playing in that land is asking for problems down the road. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Mar 12 16:20:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA05683 for current-outgoing; Tue, 12 Mar 1996 16:20:13 -0800 (PST) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA05631 for ; Tue, 12 Mar 1996 16:20:10 -0800 (PST) Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.7.1/8.6.9) with ESMTP id TAA14043; Tue, 12 Mar 1996 19:18:42 -0500 (EST) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.7.1/8.6.9) id TAA01473; Tue, 12 Mar 1996 19:18:28 -0500 (EST) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199603130018.TAA01473@oscar.cc.gatech.edu> Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Mar 1996 19:18:28 -0500 (EST) Cc: jgreco@brasil.moneng.mei.com, jehamby@lightside.com, current@freebsd.org, jkh@time.cdrom.com, toor@dyson.iquest.net In-Reply-To: <199603112125.NAA12878@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 11, 96 01:25:42 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Such as what, the PVI-486AP4, out of production for 4 months, the only > 486 board that I know ASUS is still makeing is the PVI-486SP3, which > I do not classify as a good board due to only 2 Simm sockets and if I > recall correctly a cache coherency problem in the Sis 496/497 chipset. I can attest to this. I've got a PVI-486SP3, with the SiS 496/497 chipset and a Cyrix 5x86-120 chip. I'm running 2.1.0-RELEASE off of a SCSI drive on an Adaptec 1542CF. As most of you probably know, this is a bus mastering card, and I have run into quite a few problems when running at 120 MHz. However, at 100 MHz everything is ok. There's 16k of write-back L1 cache, and 256k of write-back L2 cache. I have heard from quite a few other folks that they have problems too, particularly with this motherboard, CPU's that use write-back L1 cache, and Adaptec SCSI cards (1542C, 284x, 294x). One person was using a BusLogic card, but he switched to a different BusLogic, and everything was ok. Wish I'd known before I got it (too late now). Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ Computer Science Senior at Georgia Tech From owner-freebsd-current Tue Mar 12 16:46:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA09291 for current-outgoing; Tue, 12 Mar 1996 16:46:34 -0800 (PST) Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA09282 for ; Tue, 12 Mar 1996 16:46:29 -0800 (PST) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.7.4/8.6.10) with ESMTP id QAA04494; Tue, 12 Mar 1996 16:45:52 -0800 (PST) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id QAA18225; Tue, 12 Mar 1996 16:45:51 -0800 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id QAA07753; Tue, 12 Mar 1996 16:44:25 -0800 Message-Id: <199603130044.QAA07753@cozumel.tcs.com> Subject: Re: COMCONSOLE: a patch and a problem To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 12 Mar 1996 16:44:24 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199603122216.XAA05836@uriah.heep.sax.de> from "J Wunsch" at Mar 12, 96 11:16:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: | | As Douglas Ambrisko wrote: | | > I'll also take a look at syscons and see why it should | > be different. | | syscons uses a different tty structure for the console than for VT1. I guess my question is why? and why can't they be made compatible. The issue here is that we can't really have a getty on com1 and ttyv0 since this would upset a mouse on com1. I feel if we can't do this then we have no hope for a system that we can easily switch between serial console and graphics console mode without major work. This also implies that installing a system through a serial console is also partially doomed since it would mean tracking another set of boot blocks etc. during the install phase and another boot floppy. Also it is important that part of the structure for the serial console and graphics console is different or flagged so the graphics ioctl check will fail to detect whether or not the console is a serial port or graphics console. This code is used in sysinstall. I have to admit all that I have tried was vi, shell and X. | > the last boot mode. This way you can boot -h to get the serial port and -g | > to get the graphics console and the kernel would remember that for the | > next boot. | | By now, -h is a toggle (btw.). | | Most people would hesitate if you always write back the boot block, | just to store a single bit in it. Well, van Gilluwe reports bit 2 of | the so-called ``equipment byte'' in the CMOS (offset 0x14) as | `unused'. Perhaps we could use it to store the serial console flag | there? :) Yep that's why I suggested to save the boot mode in the kernel like what happens when you boot -c and modify the kernel. Right now I don't know what would be involved to do that. Doug A. From owner-freebsd-current Tue Mar 12 17:37:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14411 for current-outgoing; Tue, 12 Mar 1996 17:37:42 -0800 (PST) Received: from austin.polstra.com ([206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14378 Tue, 12 Mar 1996 17:37:35 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id RAA16462; Tue, 12 Mar 1996 17:37:34 -0800 Message-Id: <199603130137.RAA16462@austin.polstra.com> To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Elfkit-1.0.1 announcement Date: Tue, 12 Mar 1996 17:37:34 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just returned from a 10-day holiday, and I see that my "elfkit" has gotten some mention in connection with Søren and Peter's recent progress on ELF support in the FreeBSD kernel. So I guess I might as well announce it officially, and describe what it is and what it isn't. Against my better judgement, I'm sending this announcement to both -current (because that's where I think it belongs) and -hackers (because that's where Jordan suggested I send it). Please confine followups to -current only. WHAT IS ELFKIT? Elfkit is a collection of tools for compiling and executing ELF programs under FreeBSD-2.1.0-RELEASE and later. It consists of: * Patches for gcc-2.7.2, to make it support ELF under FreeBSD. * Patches for binutils-2.6, to make it support ELF under FreeBSD. * Patches for libc from FreeBSD-2.1.0-RELEASE, to support building it as an ELF shared library. * An ELF dynamic linker. * A user-level test program that can invoke the dynamic linker to load and execute ELF programs under FreeBSD. (The user-level test program is probably superfluous, now that the kernel can directly load and execute ELF executables.) WHAT CAN I DO WITH IT? You can compile and link arbitrary programs, as long as they use only libc. (The other libraries aren't converted yet.) The output of the linker is a standard, dynamically-linked ELF executable. You can also build ELF shared libraries. WHO SHOULD USE ELFKIT? The current release of elfkit is intended for people who want to help develop ELF support under FreeBSD. If you simply want to run ELF programs, and don't want to learn anything else about it, come back in a few months. WHAT IS THE STATUS OF ELFKIT? Elfkit is a work-in-progress, not a finished product. If you use it, you should be prepared to deal with some disruption when new releases come out. For example, the installation procedure and the directory structure could change in future releases. Of course, I intend to stabilize such things as soon as is practical. But it's not practical yet -- we're still too early in the development cycle. WHERE CAN I GET IT? ftp://ftp.polstra.com/pub/FreeBSD/elfkit/elfkit-1.0.1.tar.gz WHAT ELSE WILL I NEED? * gcc-2.7.2.tar.gz, from any GNU site. * binutils-2.6.tar.gz, from any GNU site. * The sources for libc, from FreeBSD-2.1.0-RELEASE. If at all possible, you should get your libc sources from one of the FreeBSD mirror sites, or from the 2.1.0 CD-ROM. If that's absolutely impossible for you, you can get it from: ftp://ftp.polstra.com/pub/FreeBSD/elfkit/libc-2.1.0.tar.gz Please try to avoid getting the libc sources from ftp.polstra.com. Its network connection is only a 56K frame relay link. WHERE DO I SEND BUG REPORTS AND COMMENTS? elfkit-bugs@polstra.com HOW CAN I HELP? Help is welcome, especially in the areas of library conversion and testing. At this time, only libc has been converted to support ELF. Eventually, all the other libraries will have to be converted as well. Libc is by far the most difficult; I expect that most of the other libraries will simply need to be recompiled using the elfkit tools, and tested. This sounds easy, but nevertheless is it work that somebody is going to have to spend time doing. As more ELF libraries become available, there will be an increasing need for testing -- i.e., building larger and larger parts of the FreeBSD system as ELF executables, and trying them out. Send mail to elfkit-bugs@polstra.com if you'd like to help. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Mar 12 18:46:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA20413 for current-outgoing; Tue, 12 Mar 1996 18:46:10 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA20382 Tue, 12 Mar 1996 18:45:42 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA21238; Wed, 13 Mar 1996 13:36:48 +1100 Date: Wed, 13 Mar 1996 13:36:48 +1100 From: Bruce Evans Message-Id: <199603130236.NAA21238@godzilla.zeta.org.au> To: jkh@time.cdrom.com, terry@lambert.org Subject: Re: Native & Linux ELF support finally there... Cc: amurai@spec.co.jp, current@FreeBSD.ORG, sos@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> The upshot of all this is that the COMPAT_LINUX flag should go away; >> it's a pain in the ass to have to rebuild a kernel in order to run >> Linux binary compatability. >I agree. In connection with the current Linux emulation, this is the >#1 question I get ("I try to run my Linux binary and it says can't >execute binary file, what do I doooooooo?!"). Where have you been? :-) Option COMPAT_LINUX went away almost 2 weeks ago (except in options.i386). Bruce From owner-freebsd-current Tue Mar 12 18:57:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA21603 for current-outgoing; Tue, 12 Mar 1996 18:57:13 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA21585 for ; Tue, 12 Mar 1996 18:57:04 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA22009; Wed, 13 Mar 1996 13:52:58 +1100 Date: Wed, 13 Mar 1996 13:52:58 +1100 From: Bruce Evans Message-Id: <199603130252.NAA22009@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, j@uriah.heep.sax.de Subject: Re: COMCONSOLE: a patch and a problem Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I'll also take a look at syscons and see why it should >> be different. >syscons uses a different tty structure for the console than for VT1. 0 >Most people would hesitate if you always write back the boot block, >just to store a single bit in it. Well, van Gilluwe reports bit 2 of >the so-called ``equipment byte'' in the CMOS (offset 0x14) as >`unused'. Perhaps we could use it to store the serial console flag >there? :) The Interrupt List says: 14h - Equipment Byte ... Bit 3 Display ENabled ... Bit 2 Keyboard ENabled ... ... 14h - (AMSTRAD) BYTE user RAM checksum I have used the keyboard security lock bit. This is easy to test for (((inb(0x64) & 0x10) == 0) means locked) but has other problems (my Award BIOS hangs if the keyboard is locked and the BIOS "Halt on keyboard error" is disabled; I have to disable "Halt on disk error"). Some systems don't have keyboard security locks. Bruce From owner-freebsd-current Tue Mar 12 19:13:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA23068 for current-outgoing; Tue, 12 Mar 1996 19:13:53 -0800 (PST) Received: from skypirates.constantchange.on.ca (DreamLabs.ConstantChange.on.ca [198.96.119.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA23058 for ; Tue, 12 Mar 1996 19:13:42 -0800 (PST) Received: (from mitayai@localhost) by skypirates.constantchange.on.ca (8.7.4/8.6.12) id WAA00750; Tue, 12 Mar 1996 22:15:17 GMT Date: Tue, 12 Mar 1996 22:15:16 +0000 () From: Will Mitayai Keeso Rowe To: freebsd-current@freebsd.org Subject: make world & Current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if anyone could tell me the best way to update my system once i do a 'make world' and notice, during my nightly sup or through my perusual of the -current and -cvs lists, that there has been several updates i need or am interested in? Since it is a development machine i'm playing with, i don't mind recompiling a bunch of stuff every few days... i'm learning a fair bit looking at the code, tinkering, and looking at before-and-after changes to see what their functionality and usages are. -Mit From owner-freebsd-current Tue Mar 12 20:00:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA26045 for current-outgoing; Tue, 12 Mar 1996 20:00:55 -0800 (PST) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA26040 for ; Tue, 12 Mar 1996 20:00:52 -0800 (PST) Received: (from faulkner@localhost) by utgard.bga.com (8.7.4/8.7.3) id WAA14961; Tue, 12 Mar 1996 22:00:26 -0600 (CST) Message-Id: <199603130400.WAA14961@utgard.bga.com> Subject: Re: Elfkit-1.0.1 announcement To: jdp@polstra.com (John Polstra) Date: Tue, 12 Mar 1996 22:00:25 -0559 (CST) From: "Boyd R. Faulkner" Cc: current@freebsd.org In-Reply-To: <199603130137.RAA16462@austin.polstra.com> from "John Polstra" at Mar 12, 96 05:37:17 pm X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to John Polstra: > > > > Elfkit is a collection of tools for compiling and executing ELF > programs under FreeBSD-2.1.0-RELEASE and later. It consists of: > > * Patches for gcc-2.7.2, to make it support ELF under FreeBSD. > * Patches for binutils-2.6, to make it support ELF under FreeBSD. > * Patches for libc from FreeBSD-2.1.0-RELEASE, to support building it > as an ELF shared library. > * An ELF dynamic linker. > * A user-level test program that can invoke the dynamic linker to > load and execute ELF programs under FreeBSD. > > * gcc-2.7.2.tar.gz, from any GNU site. > * binutils-2.6.tar.gz, from any GNU site. > * The sources for libc, from FreeBSD-2.1.0-RELEASE. > Does this mean that with ELF, we could use a current version of gas with patches? If so, this is the best reason to use ELF I have heard yet! Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Tue Mar 12 20:28:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA27385 for current-outgoing; Tue, 12 Mar 1996 20:28:24 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA27380 for ; Tue, 12 Mar 1996 20:28:17 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id UAA17204; Tue, 12 Mar 1996 20:28:06 -0800 Message-Id: <199603130428.UAA17204@austin.polstra.com> To: "Boyd R. Faulkner" cc: current@freebsd.org Subject: Re: Elfkit-1.0.1 announcement In-reply-to: Your message of "Tue, 12 Mar 1996 22:00:25 -0559." <199603130400.WAA14961@utgard.bga.com> Date: Tue, 12 Mar 1996 20:28:05 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Elfkit is a collection of tools for compiling and executing ELF > > programs under FreeBSD-2.1.0-RELEASE and later. It consists of: > > > > * Patches for gcc-2.7.2, to make it support ELF under FreeBSD. > > * Patches for binutils-2.6, to make it support ELF under FreeBSD. > ... > Does this mean that with ELF, we could use a current version of gas with > patches? If so, this is the best reason to use ELF I have heard yet! Yes, that's right. It uses the latest versions of gcc, gas, and gld, and they seem to work just fine, with full support for both building and linking against shared libraries. Incidentally, for FreeBSD's a.out format, shared library support is the biggest thing that's missing from binutils-2.6. I looked into adding it a while back, but it would take quite a bit of work. Skirting the issue by working on ELF instead was waaaaaay more fun :-). -- John From owner-freebsd-current Tue Mar 12 21:25:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA00738 for current-outgoing; Tue, 12 Mar 1996 21:25:49 -0800 (PST) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA00733 for ; Tue, 12 Mar 1996 21:25:38 -0800 (PST) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id HAA16198 for freebsd-current@FreeBSD.ORG; Wed, 13 Mar 1996 07:25:01 +0200 From: John Hay Message-Id: <199603130525.HAA16198@zibbi.mikom.csir.co.za> Subject: Re: finger and 2.2-960303-SNAP To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Wed, 13 Mar 1996 07:25:00 +0200 (SAT) In-Reply-To: <96Mar12.124306pst.177478@crevenia.parc.xerox.com> from "Bill Fenner" at Mar 12, 96 12:43:00 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >And an option added that disables the use of T/TCP so that a user can > >finger a broken TCP system. ^^^^ > > You're right! Why don't we call it net.inet.tcp.rfc1644? > Root may be able to set it, but (I hope) users can't. So the normal user can't finger a broken TCP until he can get hold of the admin of the machine and convince him to switch net.inet.tcp.rfc1644 off. John -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Tue Mar 12 22:20:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA03267 for current-outgoing; Tue, 12 Mar 1996 22:20:14 -0800 (PST) Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA03262 for ; Tue, 12 Mar 1996 22:20:11 -0800 (PST) Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id WAA14155; Tue, 12 Mar 1996 22:23:35 -0800 From: Rob Mallory Message-Id: <199603130623.WAA14155@wiley.csusb.edu> Subject: Re: Elfkit-1.0.1 announcement To: faulkner@asgard.bga.com (Boyd R. Faulkner) Date: Tue, 12 Mar 1996 22:23:35 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199603130400.WAA14961@utgard.bga.com> from "Boyd R. Faulkner" at Mar 12, 96 10:00:25 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > According to John Polstra: > > > > > > > > Elfkit is a collection of tools for compiling and executing ELF > > programs under FreeBSD-2.1.0-RELEASE and later. It consists of: > > ...Cool! Now the linux-hacks at idsoftware can do quake development under a real OS!! :) -rob From owner-freebsd-current Tue Mar 12 22:45:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04701 for current-outgoing; Tue, 12 Mar 1996 22:45:46 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA04690 for ; Tue, 12 Mar 1996 22:45:42 -0800 (PST) Received: from mordillo (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id HAA20156 for ; Wed, 13 Mar 1996 07:45:38 +0100 (MET) Received: (from news@localhost) by mordillo (8.6.12/8.6.12) id SAA05401; Mon, 11 Mar 1996 18:56:51 +0100 To: current@FreeBSD.org Path: graichen From: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-current Subject: Re: Native & Linux ELF support finally there... Date: 11 Mar 1996 17:56:50 GMT Organization: his FreeBSD box :-) Lines: 17 Distribution: local Message-ID: <4i1ph2$581@mordillo.physik.fu-berlin.de> References: <199603110833.JAA18747@ra.dkuug.dk> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org wrote: : To run Linux ELF binaries you need a Linux ld.so + linux ELF libs : the collection I use come from Slackware 3.0. : I belive Peter i working onpreparing a set of libs that will : be availabel as a package..> have you tried the newer libs too (libc >= 5.2.18) - from the netbsd lists i remember that they had some problems with them (i think you need them to run the linux java sdk or so) ? t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-current Tue Mar 12 22:45:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04724 for current-outgoing; Tue, 12 Mar 1996 22:45:50 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA04702 for ; Tue, 12 Mar 1996 22:45:46 -0800 (PST) Received: from mordillo (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id HAA18227 for ; Wed, 13 Mar 1996 07:45:42 +0100 (MET) Received: (from news@localhost) by mordillo (8.6.12/8.6.12) id NAA03195; Sun, 10 Mar 1996 13:13:50 +0100 To: current@FreeBSD.org Path: graichen From: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-current Subject: Re: changes to /etc/csh.* Date: 10 Mar 1996 12:13:50 GMT Organization: his FreeBSD box :-) Lines: 27 Distribution: local Message-ID: <4huh1u$32q@mordillo.physik.fu-berlin.de> References: <199603091345.OAA00930@uriah.heep.sax.de> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch (j@uriah.heep.sax.de) wrote: : As Thomas Graichen wrote: : > how about also adding something like: : > : > if ( -x /usr/sbin/ispcvt ) then : > if { /usr/sbin/ispcvt } then : > setenv TERM vt220 : > endif : > endif : > this way you'll automatically get the right TERM if you are using : > syscons _or_ pcvt - just an idea - for me it works very nice : This should go into /etc/ttys instead. (Though it's not automagic : there.) thats why i put it into csh.login etc. - so you don't have to change _anything_ then switching console types t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-current Tue Mar 12 22:45:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04741 for current-outgoing; Tue, 12 Mar 1996 22:45:53 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA04718 for ; Tue, 12 Mar 1996 22:45:49 -0800 (PST) Received: from mordillo (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id HAA11906 for ; Wed, 13 Mar 1996 07:45:44 +0100 (MET) Received: (from news@localhost) by mordillo (8.6.12/8.6.12) id SAA05388; Mon, 11 Mar 1996 18:49:48 +0100 To: current@FreeBSD.org Path: graichen From: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-current Subject: Re: Compat collection. Date: 11 Mar 1996 17:49:48 GMT Organization: his FreeBSD box :-) Lines: 35 Distribution: local Message-ID: <4i1p3s$581@mordillo.physik.fu-berlin.de> References: <199603110548.HAA01352@grumble.grondar.za> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Mark Murray (mark@grondar.za) wrote: : Ollivier Robert wrote: : > It seems that J Wunsch said: : > > binaries. Instead, i usually pick /usr/junklib for it, and ldconfig : > > this directory, too. Perhaps the hooks for this should go into the : > > base system, so a compatxx distribution can easily make use of it. : > : > Perhaps a /compat/freebsd as we've agreed on this for ibcs2 and linux ? : I line the idea of a separate directory, but I prefer something under /usr : so we can keep iy in that partition without compulsory, messy symlinks. how about moving all the other /compat stuff to /usr/compat too - the root filesystem is the wrong place for it and if you have it on a seperate disk you can also mount it onto /usr/compat instead of compat - so why not simply putting it to /usr/compat this way we may put the FreeBSD stuff there too and have a very consistent sheme for it (i think) /usr/compat/linux /usr/compat/ibcs2 /usr/compat/freebsd /usr/compat/netbsd and whatever - howabout that ? (include all changes in the emulation code to switch from /compat to /usr/compat) t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-current Tue Mar 12 23:43:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA08572 for current-outgoing; Tue, 12 Mar 1996 23:43:25 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA08562 Tue, 12 Mar 1996 23:43:19 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA06378; Wed, 13 Mar 1996 08:23:49 +0100 Message-Id: <199603130723.IAA06378@ra.dkuug.dk> Subject: Re: Native & Linux ELF support finally there... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 13 Mar 1996 08:23:49 +0100 (MET) Cc: terry@lambert.org, amurai@spec.co.jp, sos@FreeBSD.org, current@FreeBSD.org In-Reply-To: <4365.826672034@time.cdrom.com> from "Jordan K. Hubbard" at Mar 12, 96 03:07:14 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > > The upshot of all this is that the COMPAT_LINUX flag should go away; > > it's a pain in the ass to have to rebuild a kernel in order to run > > Linux binary compatability. > > I agree. In connection with the current Linux emulation, this is the > #1 question I get ("I try to run my Linux binary and it says can't > execute binary file, what do I doooooooo?!"). You guys should read your commits mail a little closer :) It is no longer needed to have the compat linux option in there and hasn't been for at least a week or so :) :) If you want to link the emulator in statically, you would need an options LINUX... Someone should probably fix the FAQ and such, but it is ONLY true for -current... Back to work... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Mar 12 23:51:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09437 for current-outgoing; Tue, 12 Mar 1996 23:51:11 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09418 for ; Tue, 12 Mar 1996 23:51:02 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA07748 for ; Wed, 13 Mar 1996 08:50:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA14622 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:50:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id IAA09940 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:30:43 +0100 (MET) From: J Wunsch Message-Id: <199603130730.IAA09940@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 08:30:43 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603130252.NAA22009@godzilla.zeta.org.au> from "Bruce Evans" at Mar 13, 96 01:52:58 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >syscons uses a different tty structure for the console than for VT1. > 0 No, syscons (and xfree86, FWIW) follows the somewhat weird SysV/SCO naming philosophy where the first available virtual terminal has got number one, i.e. VT1 == vt01 (xfree86) == /dev/ttyv0. In order to switch to this VT by ioctl(VT_ACTIVATE), you ought to pass a `1', not `0'. > >Most people would hesitate if you always write back the boot block, > >just to store a single bit in it. Well, van Gilluwe reports bit 2 of > >the so-called ``equipment byte'' in the CMOS (offset 0x14) as > >`unused'. Perhaps we could use it to store the serial console flag > >there? :) > > The Interrupt List says: > > 14h - Equipment Byte > ... > Bit 3 Display ENabled ... > Bit 2 Keyboard ENabled ... > ... That's also how one my AMI BIOSes handles it. Though, well, if all BIOSes would follow the ``Display enabled'' convention, this might be a useful hint... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 23:51:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09455 for current-outgoing; Tue, 12 Mar 1996 23:51:13 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09424 for ; Tue, 12 Mar 1996 23:51:04 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA07755 for ; Wed, 13 Mar 1996 08:50:53 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA14623 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:50:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id IAA10658 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:47:25 +0100 (MET) From: J Wunsch Message-Id: <199603130747.IAA10658@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 08:47:25 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603122339.PAA14481@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 12, 96 03:39:08 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Rodney W. Grimes wrote: > Absolutely not. Storing stuff in the CMOS by an OS is a nasty and > very risky thing to do. It may be unused today, but that is the BIOS > writters land, and playing in that land is asking for problems down > the road. I've only been half-serious about this. If all BIOSes would follow the conventions to use bit 3 of the `equipment byte' for ``Graphics disabled'', however, this would be a nice decision. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 12 23:51:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09577 for current-outgoing; Tue, 12 Mar 1996 23:51:47 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09536 for ; Tue, 12 Mar 1996 23:51:34 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA07759 for ; Wed, 13 Mar 1996 08:50:56 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA14626 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:50:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id IAA10415 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 08:42:50 +0100 (MET) From: J Wunsch Message-Id: <199603130742.IAA10415@uriah.heep.sax.de> Subject: Re: COMCONSOLE: a patch and a problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 08:42:50 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603130044.QAA07753@cozumel.tcs.com> from "Douglas Ambrisko" at Mar 12, 96 04:44:24 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Douglas Ambrisko wrote: > | syscons uses a different tty structure for the console than for VT1. > > I guess my question is why? Syscons originally shared the struct tty between the console and ttyv0, but tried to work around problems in the generic console code by using a different struct tty for it. Many of the problems with the generic console code have been fixed now (have a look at the CVS log of sys/i386/i386/cons.[ch] to see what happened), but syscons' hack^H^H^H^Hworkaround remains. > issue here is that we can't really have a getty on com1 and ttyv0 since this > would upset a mouse on com1. I feel if we can't do this then we The problems with running getty on /dev/console were related to things like properly handling the tty-level open()/close() of the associated devices. You normally don't notice the problems since syslogd holds /dev/console open all the time, except once during /etc/daily, where it is being restarted. The effect was that you came back to the machine next morning, and haven't seen any output on the console when logging in. > Also it is important that part of the structure for the serial console > and graphics console is different or flagged so the graphics ioctl check > will fail to detect whether or not the console is a serial port or graphics > console. This code is used in sysinstall. You can simply issue an ioctl(VT_GETACTIVE) to the stdin file descriptor. It is implemented in both, syscons and pcvt (though the latter is not that important for sysinstall). If the ioctl succeeds, you're usign a graphics console, otherwise it's either a serial or no console at all. > Yep that's why I suggested to save the boot mode in the kernel like what > happens when you boot -c and modify the kernel. Right now I don't know > what would be involved to do that. Well, dset(8) is rather a (appreciated) hack. It writes back to the /kernel file. This is, however, too late for the boot -h flag, since this must already be evaluated by the boot code before any kernel file is known or could be read. It's not even necessary that there's a FreeBSD file system structure around on the boot medium. For example, the system might not yet be installed, or one might create a floppy containing just the bootstrap only, and wants to enter ``7:sd(4,a)/kernel'' at the boot prompt since he doesn't want to use booteasy for boot selection. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 13 00:25:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13081 for current-outgoing; Wed, 13 Mar 1996 00:25:04 -0800 (PST) Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA13073 for ; Wed, 13 Mar 1996 00:25:01 -0800 (PST) Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id AAA27633 for freebsd-current@freebsd.org; Wed, 13 Mar 1996 00:33:36 -0800 From: Brian Litzinger Message-Id: <199603130833.AAA27633@MediaCity.com> Subject: can't find linux_assym.h To: freebsd-current@freebsd.org Date: Wed, 13 Mar 1996 00:33:36 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I build a -current kernel with 'options LINUX' I get an error assembling linux_locore.s in which it can't find linux_assym.h and neither can I. I've re-sup'ed and configed everything and still have the problem. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com From owner-freebsd-current Wed Mar 13 00:49:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA14887 for current-outgoing; Wed, 13 Mar 1996 00:49:27 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA14880 for ; Wed, 13 Mar 1996 00:49:25 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id AAA03007; Wed, 13 Mar 1996 00:46:25 -0800 (PST) Message-Id: <199603130846.AAA03007@precipice.shockwave.com> To: Terry Lambert cc: roberto@keltia.freenix.fr (Ollivier Robert), adf@fl.net.au, olah@cs.utwente.nl, current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Tue, 12 Mar 1996 14:14:31 MST." <199603122114.OAA06574@phaeton.artisoft.com> Date: Wed, 13 Mar 1996 00:46:25 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: Terry Lambert Subject: Re: finger and 2.2-960303-SNAP > > "Fixed" is subjective. It saves one response packet and loses > > interoperability. 8-(. > > Only with broken TCP implementations like the Annex's. We'll never see the > broken code change if no one complain and make them fix their bugs. This is a wonderful theory. To make it work, wouldn't the bug reports have to go to their lists instead of ours? No, it's actually better if the bug reports come to US first. The reason being that most vendors would say "pshaw, you guys are idiots." whereas there are a bunch of us on the mailing list who can point to the exact bits of trivia in RFC-793 and sample "killer packets" to get these guys to fix their TCP implementation. From owner-freebsd-current Wed Mar 13 03:12:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22557 for current-outgoing; Wed, 13 Mar 1996 03:12:15 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA22550 for ; Wed, 13 Mar 1996 03:12:12 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelay-SVR4_1.3/RBCS) id MAA02878; Wed, 13 Mar 1996 12:12:10 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id MAA02507; Wed, 13 Mar 1996 12:12:04 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id MAA28988; Wed, 13 Mar 1996 12:12:03 +0100 To: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Sat, 13 Mar 1996 07:25:00 +0200." <199603130525.HAA16198@zibbi.mikom.csir.co.za> Date: Wed, 13 Mar 1996 12:12:01 +0100 Message-ID: <28987.826715521@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 13 Mar 1996 07:25:00 +0200, John Hay wrote: > > > > >And an option added that disables the use of T/TCP so that a user can > > >finger a broken TCP system. > ^^^^ > > > > You're right! Why don't we call it net.inet.tcp.rfc1644? > > > > Root may be able to set it, but (I hope) users can't. So the normal user > can't finger a broken TCP until he can get hold of the admin of the machine > and convince him to switch net.inet.tcp.rfc1644 off. OK, I got the hint! ;-) There's a patch for finger on freefall (~olah/finger-mod.diff), to disable T/TCP with the -T option. I tested it here, if there are no complaints I'll commit it in a few days. Andras From owner-freebsd-current Wed Mar 13 03:31:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA24163 for current-outgoing; Wed, 13 Mar 1996 03:31:34 -0800 (PST) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA24156 for ; Wed, 13 Mar 1996 03:31:32 -0800 (PST) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.7.4/8.6.9) with ESMTP id DAA01053 for ; Wed, 13 Mar 1996 03:31:30 -0800 (PST) To: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Wed, 13 Mar 1996 00:46:25 PST." <199603130846.AAA03007@precipice.shockwave.com> Date: Wed, 13 Mar 1996 03:31:29 -0800 Message-ID: <1047.826716689@pain.csrv.uidaho.edu> From: Faried Nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina wrote... No, it's actually better if the bug reports come to US first. The reason being that most vendors would say "pshaw, you guys are idiots." whereas there are a bunch of us on the mailing list who can point to the exact bits of trivia in RFC-793 and sample "killer packets" to get these guys to fix their TCP implementation. for xylogics/annex it's annex_support@xylogics.com i believe. any ideas on how i should compose my `bug report'? i've never really done this before. faried. From owner-freebsd-current Wed Mar 13 05:27:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28710 for current-outgoing; Wed, 13 Mar 1996 05:27:28 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28705 for ; Wed, 13 Mar 1996 05:27:24 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id AAA05044; Thu, 14 Mar 1996 00:21:44 +1100 From: David Dawes Message-Id: <199603131321.AAA05044@rf900.physics.usyd.edu.au> Subject: Re: COMCONSOLE: a patch and a problem To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 14 Mar 1996 00:21:44 +1100 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199603130730.IAA09940@uriah.heep.sax.de> from "J Wunsch" at Mar 13, 96 08:30:43 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Bruce Evans wrote: > >> >syscons uses a different tty structure for the console than for VT1. >> 0 > >No, syscons (and xfree86, FWIW) follows the somewhat weird SysV/SCO >naming philosophy where the first available virtual terminal has got >number one, i.e. VT1 == vt01 (xfree86) == /dev/ttyv0. > >In order to switch to this VT by ioctl(VT_ACTIVATE), you ought to pass >a `1', not `0'. Well, on SVR4, VT1 (/dev/vt01) is not the first VT, but the one activated with Alt-SysReq F1. The first one is /dev/vt00, which is activated with Alt-SysReq H (H for "home" I think). I think that in XFree86 we tried to keep the relationship between the VT numbering and the way it is activated consistent across different OSs. /dev/vt00 and /dev/console are the same device on SVR4 (at least by default). David From owner-freebsd-current Wed Mar 13 08:34:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07424 for current-outgoing; Wed, 13 Mar 1996 08:34:37 -0800 (PST) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA07404 for ; Wed, 13 Mar 1996 08:34:14 -0800 (PST) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0twtUx-0004IiC; Wed, 13 Mar 96 08:34 PST Date: Wed, 13 Mar 1996 08:34:01 -0800 (PST) From: Jake Hamby To: Thomas Graichen cc: current@FreeBSD.ORG Subject: Re: Native & Linux ELF support finally there... In-Reply-To: <4i1ph2$581@mordillo.physik.fu-berlin.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 11 Mar 1996, Thomas Graichen wrote: > sos@FreeBSD.org wrote: > : To run Linux ELF binaries you need a Linux ld.so + linux ELF libs > : the collection I use come from Slackware 3.0. > : I belive Peter i working onpreparing a set of libs that will > : be availabel as a package..> > > have you tried the newer libs too (libc >= 5.2.18) - from the netbsd lists i > remember that they had some problems with them (i think you need them to run > the linux java sdk or so) ? I couldn't get the 5.2.18 libc to work correctly with Linux! I downloaded it because the Java SDK needed it, then I discovered that common programs like make and bash weren't working correctly anymore!! Typical Linux mismanagement, just what I've come to expect from that OS.. So if that libc doesn't work with FreeBSD's ELF emulation, don't blame it on FreeBSD, you'll probably want to stick with 5.0.9 until whatever bugs are in 5.2.18 get resolved. ---Jake From owner-freebsd-current Wed Mar 13 08:42:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07794 for current-outgoing; Wed, 13 Mar 1996 08:42:05 -0800 (PST) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA07788 for ; Wed, 13 Mar 1996 08:42:03 -0800 (PST) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0twtcf-0004HvC; Wed, 13 Mar 96 08:42 PST Date: Wed, 13 Mar 1996 08:41:59 -0800 (PST) From: Jake Hamby To: current@FreeBSD.ORG Subject: Questions for current hackers.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a few questions about recent developments in -current. These are just for my own curiosity, don't take them as complaints or criticism because they aren't. I was only added to the CVS mailing list recently so I haven't been keeping up with the reasoning behind recent changes. 1) Why was libc's major version number bumped to 3? Was this to incorporate changes to make it thread-safe or for some other reason(s)? Is it safe to assume that the version won't be bumped again before 2.2-RELEASE? 2) Over the last several months, various changes have been made to the VM code that have, at times, left -current in a rather unstable state (Sig 11's and whatnot). A number of people experienced problems just recently, with the 3/3 SNAP and kernels built around this time. What exactly is the reasoning behind all of these VM changes, are they to boost performance, reduce swap utilization, or what? Thanks in advance.. ---Jake From owner-freebsd-current Wed Mar 13 09:23:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA11191 for current-outgoing; Wed, 13 Mar 1996 09:23:47 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA11186 for ; Wed, 13 Mar 1996 09:23:45 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA15888; Wed, 13 Mar 1996 12:23:41 -0500 Date: Wed, 13 Mar 1996 12:23:41 -0500 From: "Garrett A. Wollman" Message-Id: <9603131723.AA15888@halloran-eldar.lcs.mit.edu> To: Jake Hamby Cc: current@FreeBSD.org Subject: Questions for current hackers.. In-Reply-To: References: Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > 1) Why was libc's major version number bumped to 3? Was this to > incorporate changes to make it thread-safe or for some other reason(s)? > Is it safe to assume that the version won't be bumped again before > 2.2-RELEASE? Some other reason. The library routines for dealing with OSI and XNS addresses were removed. It is our policy that library version numbers are only ever bumped once in 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 Wed Mar 13 09:59:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13150 for current-outgoing; Wed, 13 Mar 1996 09:59:25 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA13132 Wed, 13 Mar 1996 09:59:19 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA08607; Wed, 13 Mar 1996 10:52:40 -0700 From: Terry Lambert Message-Id: <199603131752.KAA08607@phaeton.artisoft.com> Subject: Re: non-blocking read ? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 13 Mar 1996 10:52:39 -0700 (MST) Cc: luigi@labinfo.iet.unipi.it, leisner@sdsp.mc.xerox.com, msmith@atrad.adelaide.edu.au, questions@freebsd.org, current@freebsd.org In-Reply-To: <199603122357.KAA00112@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 13, 96 10:27:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Someone suggested doing async IO and handling SIGIO (I suppose this > > refers to doing > > See my previous message regarding not being sure about this, and > definitely check how harvest does it, I'm sure I was wrong earlier 8( > > > But how much data will be available when I get the SIGIO (or select > > will return that I/O is possible) ? The amount I requested (assuming it > > is available), or the system idea of a block, or what ? > > "some"; you call read and examine the return value to see how much you get. > > Thinking about it further, I don't see how this would work for disk I/O; > it's not until the read itself is issued that the disk request is > queued ... You get the SIGIO when there is data pending, not when the read has completed (man fcntl, look for O_ASYNC). All it is is a "data pending" notification -- it is a hack around non-I/O based messaging mechanisms so that they may be used (and then you hit select on a SIGIO) to let you multiplex, for instance, System V message queues. Unfortunately, it's not always possible to distinguish signal events from their causes: that is, if I have multiple completions in the time it takes me to handle a signal, I'm screwed, even if SIGIO passed, for instance, the address of the buffer that completed to the handler. Signals are persistent conditions. Signals are *not* events. There is no "wait" equivalent call family for SGIO, like there is for SIGCLD. It would be best if you dealt with the kernel reentrancy issues and implemented aioread/aiowrite/aiowait/aiocancel. This was a lot easier under 1.1.5.1 (where I fully implemented a SunOS LWP clone library at one time) because the lock recursion on read/write reeentrancy wasn't overly complex, like it is in -current, with the unified VM and the vnode/inode dissociation code (which I still think is broken). To handle this, you would need to: 1) Move VM to using device/extent instead of vnode/extent for the buffer cache. This would allow o Reuse of a vnode without discarding the buffer cache entry or needing an ihash entry as a second chance cache. o Allow you to get around the IN_RECURSE and lock complexity in the VOP_LOCK/VOP_UNLOCK code, which currently affects both the vnode and the underlying FS. This would limit device size from 8TB down to 1TB. File size limitations would not change. 2) With the VM change in place, you would need to change the VOP_LOCK code. Specifically, you would need to define counting semaphores for routines, probably called vn_lock and vn_unlock. These routines would acquire the vnode lock (allowing recursion for the same PID in all cases) and then call the underlying FS's VOP_LOCK/VOP_UNLOCK respectively. If the VOP_LOCK call failed, the vn_lock would be released and failed. This allows for an FS specific "veto", and is there solely to support FS layering for union, translucent, loopback, and overlay FS's (an overlay FS would be, for example, a umsdos-on-dos, vfat-on-dos, or quota-on-any type FS). The lock code changes would allow a process to have multiple outstanding read/write requests, as long as global structure modifications were semaphored. This is the first step in kernel reeentrancy, allowing kernel multithreading, or kernel preemption (necessary for POSIX RT processing); it is also the first step (with conversion of the semaphore to a mutex or, better, a hierarchical lock with a mutex "top") toward supporting multiple processor reentrancy for the VFS kernel subsystem. 3) With the lock code changed, a single multiplexed system call should be designated as "aio". Yes, it's possible to do 4 call slots, but why? This system call would use stub wrappers to pass down alternate argument list selectors, and would provide an aioread/aiowrite/ aiowait/aiocancel mechanism. An aioread or aiowrite need to be handled in the ordinary read or write path, and when a blocking operation is issued, need to pass a completion routine and an argument address. The completion routine is the same for all processes; the argument address is the address of a context structure, which points to the proc structure for the process that issues the request, as well as context information for the actual copy out (buffer length, buffer address for copyout, etc.). When an I/O completes, it needs to be unlinked from the "pending" list and linked to the "completed" list. These are two new pointers hung off the proc structure. The aiowait/aiocancel operation operate on the context identifiers on the lists, with obvious results. A more generic mechanism would be to convert the aio multiplex call into a call gate instead. This would allow the user to issue *any* system call as an async operation. A flag would be added to the sysent structure to flag calls that were allowed to return to user space pending completion; by default, the flag would be 0, but set to 1 for read and write for the first rev of the code. Any operation that could require paging to be satisfied should, in fact, be capable of being issued asynchronously. A "middle ground" implementation would make the multiplex system call something like "aiosyscall" -- that is, the same as "syscall", the multiplex entry point for call by syscall.h manifest constant of all existing system calls. This would not be a horrific amount of work, but it would require dragging several of the kernel people into the process (well, not really, but you'd need their approval to commit the changes). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 13 10:14:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14165 for current-outgoing; Wed, 13 Mar 1996 10:14:34 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14159 Wed, 13 Mar 1996 10:14:33 -0800 (PST) From: John Dyson Message-Id: <199603131814.KAA14159@freefall.freebsd.org> Subject: Re: Questions for current hackers.. To: jehamby@lightside.com (Jake Hamby) Date: Wed, 13 Mar 1996 10:14:32 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: from "Jake Hamby" at Mar 13, 96 08:41:59 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > 2) Over the last several months, various changes have been made to the VM > code that have, at times, left -current in a rather unstable state (Sig > 11's and whatnot). A number of people experienced problems just recently, > with the 3/3 SNAP and kernels built around this time. What exactly is the > reasoning behind all of these VM changes, are they to boost performance, > reduce swap utilization, or what? > Performance boost, code cleanup, decrease memory usage under certain circumstances (forks), etc... Remember, -current != -stable :-). The changes were tested for a few weeks, and it is impossible to simulate all usages of the system. There are more changes going in after the next SNAP. John From owner-freebsd-current Wed Mar 13 10:38:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA15687 for current-outgoing; Wed, 13 Mar 1996 10:38:57 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA15682 for ; Wed, 13 Mar 1996 10:38:53 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id TAA01401 for current@freebsd.org; Wed, 13 Mar 1996 19:15:16 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id TAA02010 for current@freebsd.org; Wed, 13 Mar 1996 19:05:56 +0100 (MET) From: Andreas Klemm Message-Id: <199603131805.TAA02010@knobel.gun.de> Subject: still panics when accessing cdrom To: current@freebsd.org Date: Wed, 13 Mar 1996 19:05:56 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I still have panics, after mounting the FreeBSD-2.1 cdrom and doing a find /cdrom -print I think I have the last recent version of kernel (cvs-cur 1770) Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf0e9800f fault code = supervisor read, page not present instruction pointer = 0x8:0xf0104a6b code segment = base 0x0, limit 0x\M^?\^Aype 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 182 (find) interrupt mask = panic: page fault syncing disks... 88 87 81 71 59 40 20 7 7 7 7 7 7 7 7 7 7 7 7 7 giving up 1: dev:00000600, flags:00110210, blkno:176, lblkno:0 2: dev:0000ff00, flags:21020034, blkno:1986, lblkno:0 3: dev:0000ff00, flags:01000034, blkno:48, lblkno:48 4: dev:0000ff00, flags:01010034, blkno:2000, lblkno:0 5: dev:0000ff00, flags:01020034, blkno:64, lblkno:64 6: dev:0000ff00, flags:01010034, blkno:16, lblkno:16 7: dev:0000ff00, flags:01010034, blkno:1984, lblkno:1984 dumping to dev 40401, offset 131072 dump 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 FreeBSD 2.2-CURRENT #0: Wed Mar 13 17:05:14 MET 1996 machine "i386" cpu "I586_CPU" ident KNOBEL maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options "CD9660" #ISO 9660 filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=2" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options SHOW_BUSYBUFS # List buffers that prevent root unmount options SYSVSHM options SYSVSEM options SYSVMSG options "EXT2FS" options "IBCS2" options LINUX options AHC_TAGENABLE options QUEUE_FULL_SUPPORTED options SCSI_REPORT_GEOMETRY #options DDB options KTRACE options MFS #Memory File System config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console options "MAXCONS=4" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr # Joystick device joy0 at isa? port "IO_GAME" pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 2 #Berkeley packet filter pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device speaker # SB = SoundBlaster; PAS = ProAudioSpectrum; GUS = Gravis UltraSound # Controls all sound devices controller snd0 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device device sbxvi0 at isa? drq 5 # SoundBlaster 16 MIDI - for SB16 - requires sb0 device device sbmidi0 at isa? port 0x330 # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS device opl0 at isa? port 0x388 -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Wed Mar 13 12:02:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA20007 for current-outgoing; Wed, 13 Mar 1996 12:02:15 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA19994 Wed, 13 Mar 1996 12:02:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA09178; Wed, 13 Mar 1996 12:59:39 -0700 From: Terry Lambert Message-Id: <199603131959.MAA09178@phaeton.artisoft.com> Subject: Re: Native & Linux ELF support finally there... To: sos@FreeBSD.org Date: Wed, 13 Mar 1996 12:59:39 -0700 (MST) Cc: jkh@time.cdrom.com, terry@lambert.org, amurai@spec.co.jp, current@FreeBSD.org In-Reply-To: <199603130723.IAA06378@ra.dkuug.dk> from "sos@FreeBSD.org" at Mar 13, 96 08:23:49 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > The upshot of all this is that the COMPAT_LINUX flag should go away; > > > it's a pain in the ass to have to rebuild a kernel in order to run > > > Linux binary compatability. > > > > I agree. In connection with the current Linux emulation, this is the > > #1 question I get ("I try to run my Linux binary and it says can't > > execute binary file, what do I doooooooo?!"). > > You guys should read your commits mail a little closer :) > It is no longer needed to have the compat linux option in there > and hasn't been for at least a week or so :) :) > If you want to link the emulator in statically, you would need > an options LINUX... > > Someone should probably fix the FAQ and such, but it is ONLY true > for -current... Uh, I was really thinking of failing to load as opposed to failing to activate the image in the case that the ABI module wasn't present. Unconditionally including the code when the ABI module wasn't loaded was *not* what I was talking about when I said it should "go away". 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 13 12:09:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA20640 for current-outgoing; Wed, 13 Mar 1996 12:09:57 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA20631 for ; Wed, 13 Mar 1996 12:09:54 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id MAA04472; Wed, 13 Mar 1996 12:08:38 -0800 (PST) Message-Id: <199603132008.MAA04472@precipice.shockwave.com> To: Faried Nawaz cc: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Wed, 13 Mar 1996 03:31:29 PST." <1047.826716689@pain.csrv.uidaho.edu> Date: Wed, 13 Mar 1996 12:08:37 -0800 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'd give them the following summary: I am using an implementation of T/TCP (RFC-1644), a backwards compatible extension of TCP (RFC-794) and having difficulty accessing your terminal server. T/TCP sends out the initial SYN packet with additional TCP options, a non-zero data portion, and a FIN. While this is unusual (you'd normally not see it) under standard TCP, it _is_ completely legal and any TCP implementation conformant to RFC-794 should handle this properly. The FreeBSD team has encountered a few other TCP implementations with similar problems. The cause is usually due to not handling the data in the SYN packet properly. Please update your TCP implementation so that it is RFC-794 compliant. Here's a tcpdump of the conversation: % tcpdump host & % finger @ % fg ^C % tcpdump -x host & % finger @ % fg ^C Many of the TCP implementations we've found that do not inter-operate properly with T/TCP are based off of code originally written by Phil Karn. Phil recently published a fix for this problem. In the off chance your TCP is based upon his code, here was his fix (the function in question is tcp_input): *** tcpin.c.orig Fri Aug 18 10:49:17 1995 --- tcpin.c Tue Feb 13 01:13:00 1996 *************** *** 162,171 **** proc_syn(tcb,ip->tos,&seg); send_syn(tcb); setstate(tcb,TCP_SYN_RECEIVED); - if(length != 0 || seg.flags.fin) { - /* Continue processing if there's more */ - break; - } tcp_output(tcb); } free_p(bp); /* Unlikely to get here directly */ --- 162,167 ---- If you have any further questions, feel free to contact Garret Wollman (wollman@freebsd.org), Andreas Olah (olah@freebsd.org), or Paul Traina (pst@freebsd.org). -------- What do you think of that? From: Faried Nawaz Subject: Re: finger and 2.2-960303-SNAP Paul Traina wrote... No, it's actually better if the bug reports come to US first. The reason being that most vendors would say "pshaw, you guys are idiots." whereas there are a bunch of us on the mailing list who can point to the exact bits of trivia in RFC-793 and sample "killer packets" to get these guys to fix their TCP implementation. for xylogics/annex it's annex_support@xylogics.com i believe. any ideas on how i should compose my `bug report'? i've never really done this before. faried. From owner-freebsd-current Wed Mar 13 12:52:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA23178 for current-outgoing; Wed, 13 Mar 1996 12:52:28 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA23163 for ; Wed, 13 Mar 1996 12:52:17 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA02733 for ; Wed, 13 Mar 1996 21:52:09 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA21238 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 21:52:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id VAA12321 for freebsd-current@FreeBSD.org; Wed, 13 Mar 1996 21:25:43 +0100 (MET) From: J Wunsch Message-Id: <199603132025.VAA12321@uriah.heep.sax.de> Subject: Re: changes to /etc/csh.* To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 21:25:43 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <4huh1u$32q@mordillo.physik.fu-berlin.de> from "Thomas Graichen" at Mar 10, 96 12:13:50 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Thomas Graichen wrote: > : This should go into /etc/ttys instead. (Though it's not automagic > : there.) > > thats why i put it into csh.login etc. - so you don't have to change > _anything_ then switching console types Still sounds too kludgy for me. I could live with /etc/ttys being built from /etc/ttys.in during /etc/rc time. This would also solve the ``run getty on /dev/console?'' problem, or the problems of getty respawning too rapidly if neither syscons nor pcvt have been found at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 13 12:52:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA23289 for current-outgoing; Wed, 13 Mar 1996 12:52:59 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA23283 for ; Wed, 13 Mar 1996 12:52:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA02741; Wed, 13 Mar 1996 21:52:16 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA21240; Wed, 13 Mar 1996 21:52:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id VAA12384; Wed, 13 Mar 1996 21:33:12 +0100 (MET) From: J Wunsch Message-Id: <199603132033.VAA12384@uriah.heep.sax.de> Subject: Re: supping CVS home tree To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 21:33:11 +0100 (MET) Cc: alexis@ww.net Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603131035.NAA03076@dawn.ww.net> from "Alexis Yushin" at Mar 13, 96 01:35:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Alexis Yushin wrote: > Is it enough to sup CVS tree with cvs-supfile to be at the edge > of -stable, -current with ports tree? Or do I need to have both CVS > tree -current and -stable? I have no idea about sup, but CVS itself contains the master repos- itory, hence you can always checkout any branch you want. By definition, -current is always the HEAD revision (unbranched), while -stable is by now the ``RELENG_2_1_0'' tag. If you care for bandwidth utilization, and don't have an urgent need to be able to remain -current within less than a few hours latency, better stick with CTM. It is much smarter than sup. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 13 13:22:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA25660 for current-outgoing; Wed, 13 Mar 1996 13:22:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA25648 for ; Wed, 13 Mar 1996 13:21:57 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA03404; Wed, 13 Mar 1996 22:21:36 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA21507; Wed, 13 Mar 1996 22:21:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id WAA12735; Wed, 13 Mar 1996 22:05:24 +0100 (MET) From: J Wunsch Message-Id: <199603132105.WAA12735@uriah.heep.sax.de> Subject: Re: Questions for current hackers.. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 13 Mar 1996 22:05:24 +0100 (MET) Cc: jehamby@lightside.com (Jake Hamby) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Jake Hamby" at Mar 13, 96 08:41:59 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jake Hamby wrote: > 1) Why was libc's major version number bumped to 3? Was this to Some function has been dropped from the library (i forgot which one). > incorporate changes to make it thread-safe or for some other reason(s)? > Is it safe to assume that the version won't be bumped again before > 2.2-RELEASE? Yup, that's the policy. The version number will change at moste once between releases. Users of -current have to take care to always use the right shared lib, the major/minor # protection doesn't always work for them. (The VM questions must be left to John or David.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 13 13:40:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA27242 for current-outgoing; Wed, 13 Mar 1996 13:40:15 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA27236 for ; Wed, 13 Mar 1996 13:40:10 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id XAA00297 for ; Wed, 13 Mar 1996 23:40:03 +0200 (SAT) Message-Id: <199603132140.XAA00297@grumble.grondar.za> To: current@freebsd.org Subject: To pick a (perl) fight! Date: Wed, 13 Mar 1996 23:40:02 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi What are the reasons we do not now have Perl5 in the main tree? I have a query from one of our more perl-literate users who made the suggestion that Perl4 should be in ports/. What say y'all? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Mar 13 13:48:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA27942 for current-outgoing; Wed, 13 Mar 1996 13:48:43 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA27933 for ; Wed, 13 Mar 1996 13:48:34 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA15313; Wed, 13 Mar 1996 13:48:19 -0800 From: "Rodney W. Grimes" Message-Id: <199603132148.NAA15313@GndRsh.aac.dev.com> Subject: Re: booting from sd5 when wd3 is also installed To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Mar 1996 13:48:19 -0800 (PST) Cc: bde@zeta.org.au, current@freebsd.org In-Reply-To: <199603102053.HAA14288@godzilla.zeta.org.au> from "Bruce Evans" at Mar 11, 96 07:53:04 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >> I haven't decided exactly how to handle these points: > >> - how sticky should the drive number be? What is the default drive number > >> after 1:sd(0,a)/nonesuch followed by /kernel? > > >IMHO, 0. Does ``1:?'' or even ``1:xx(y,z)/kernel?'' work? > > I had `1:' by itself working for a while, but decided that it shouldn't > be so easy to change the BIOS number without changing the unit number, > so I made `1:' only work with `xx(y,z)'. `1:xx(y,z)any' should work. > `xx(y,z)any' works the same as now - the BIOS drive number is set to > match `y'. This isn't the best behaviour (you often want to keep the > BIOS boot drive number and change the FreeBSD unit number) but it is > required for compatibility and is the best behaviour for changing the > drive type from fd to sd. Agreed. > >I can't test them, but have a small nit I found doing a visual over the > >context diff.... ohh... and can you bounds check the BIOS drive number > > Thanks. > > >against the number of drives reported by the BIOS, I seem to recall > >an infinite error loop if you did something like wd(1,a)/kernel with > >only one BIOS drive. > > It's still easy to get these. I got a lot when I forgot to subtract > '0' from the drive number :-). :-). The code needs a lot of error handling added to it. Many of the BIOS calls do not even check for an error return, or at least they haven't in the past. > Does the BIOS report the number of drives reliably? The byte at > physical 0x475 seems to correctly give the total number of non-floppy > drives here (not the number of wd drives like I once thought). As far as I have been able to check the byte at 0x475 is accurate, that is what the 3rd party BIOS's like Adaptec and NCR are munging when they add the drives via hooking INT 13, etc. There is also a BIOS call that should return this value, but I forget what one it is. > BTW there is a bug in `gdb -k /kernel /dev/mem': gdb loops internally > for `p/x *(int *)0xf0000475'; it ignores ^C but can be suspended. :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Mar 13 14:00:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28916 for current-outgoing; Wed, 13 Mar 1996 14:00:41 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA28907 for ; Wed, 13 Mar 1996 14:00:37 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA18505 ; Wed, 13 Mar 1996 23:00:35 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA20571 ; Wed, 13 Mar 1996 23:00:34 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.4/keltia-uucp-2.7) id WAA07307; Wed, 13 Mar 1996 22:40:02 +0100 (MET) From: Ollivier Robert Message-Id: <199603132140.WAA07307@keltia.freenix.fr> Subject: Re: can't find linux_assym.h To: brian@MediaCity.com (Brian Litzinger) Date: Wed, 13 Mar 1996 22:40:02 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199603130833.AAA27633@MediaCity.com> from Brian Litzinger at "Mar 13, 96 00:33:36 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1762 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that Brian Litzinger said: > When I build a -current kernel with 'options LINUX' I get an > error assembling linux_locore.s in which it can't find > linux_assym.h and neither can I. I'm surprised. My kernel is dated Mon Mar 11 20:18:10 MET 1996 and doen't show the problem. I don't have COMPAT_LINUX any more and load the linux lkm with the "linux" command. I'm able to run Abuse, Doom and even xquake (even if i don't have the ELF libs yet). Executor runs fine too. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #6: Mon Mar 11 20:18:10 MET 1996 From owner-freebsd-current Wed Mar 13 14:51:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA02132 for current-outgoing; Wed, 13 Mar 1996 14:51:36 -0800 (PST) Received: from snake.hut.fi (root@snake.hut.fi [193.167.6.99]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA02127 for ; Wed, 13 Mar 1996 14:51:34 -0800 (PST) Received: from lk-hp-20.hut.fi (lk-hp-20.hut.fi [130.233.247.33]) by snake.hut.fi (8.7.3/8.7.3) with ESMTP id AAA04953 for ; Thu, 14 Mar 1996 00:51:31 +0200 (EET) From: Juha Inkari Received: (inkari@localhost) by lk-hp-20.hut.fi (8.6.12/8.6.7) id AAA27747 for freebsd-current@freebsd.org; Thu, 14 Mar 1996 00:51:29 +0200 Message-Id: <199603132251.AAA27747@lk-hp-20.hut.fi> Subject: X display trouble To: freebsd-current@freebsd.org Date: Thu, 14 Mar 1996 00:51:28 +0200 (EET) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A resent change has caused my display to not work properly under X graphics mode. The system seems to work ok otherwise, except there is no picture on graphics mode, just blank screen. Operating "blindly" seems to work (login, runnig xterms etc.). I have tried with Xinside's 1.2 server with a Diamond Stealt adapter (X sever reports is as S3,1: 86C968,TVP3026 (2048k @fa000000, [0.000 - 175.000MHz])). I have a Mar 11 16:45 kernel, current level of ctm delta cvs-cur.1761 that still seems to be ok, but a Mar 12 21:28 compilation from ctm delta cvs-cur.1766 has the display feature. If I have correctly looked it up, the cause must have been something, that is on the commitlogs/sys between the changes: nate 96/03/10 22:48:58 davidg 96/03/12 07:38:02 From owner-freebsd-current Wed Mar 13 15:07:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03008 for current-outgoing; Wed, 13 Mar 1996 15:07:18 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03000 for ; Wed, 13 Mar 1996 15:07:16 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id XAA06071 for ; Wed, 13 Mar 1996 23:05:12 GMT Received: from tees by snowdon with SMTP (PP); Wed, 13 Mar 1996 23:01:21 +0000 Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id XAA28625; Wed, 13 Mar 1996 23:05:25 GMT Date: Wed, 13 Mar 1996 23:05:25 GMT From: Paul Richards Message-Id: <199603132305.XAA28625@tees> To: current@FreeBSD.org, mark@grondar.za Subject: Re: To pick a (perl) fight! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: JSfGWCjmHWpK8EQI0BMpXA== Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > What are the reasons we do not now have Perl5 in the main tree? I have > a query from one of our more perl-literate users who made the suggestion > that Perl4 should be in ports/. > > What say y'all? > The old perl4 perl5 argument again, get a lot of this at work. I'd say that until Larry writes a Perl 5 book so that there's some easily accessible documentation for it then most people will stick with perl 4 unless they have a particular need for perl5. Given that the momentum is very much against switching to perl 5 (for this and similar reasons) I think we'd stay more compatible with the rest of the world sticking with perl 4 for the moment. We'd also have to fix all the perl code we use if we switch to perl 5. From owner-freebsd-current Wed Mar 13 15:21:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03655 for current-outgoing; Wed, 13 Mar 1996 15:21:17 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03649 for ; Wed, 13 Mar 1996 15:21:09 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA15929; Thu, 14 Mar 1996 00:21:00 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA22327; Thu, 14 Mar 1996 00:20:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id XAA01048; Wed, 13 Mar 1996 23:58:51 +0100 (MET) From: J Wunsch Message-Id: <199603132258.XAA01048@uriah.heep.sax.de> Subject: Re: system() broken while mmap()ing something To: toor@dyson.iquest.net (John S. Dyson) Date: Wed, 13 Mar 1996 23:58:48 +0100 (MET) Cc: dawes@rf900.physics.usyd.edu.au, freebsd-current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603112320.XAA00292@dyson.iquest.net> from "John S. Dyson" at Mar 11, 96 11:20:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: > I have committed a temporary fix for the problem. It will work fine, > except that I want to clean it up a bit later on. ACK: my Xserver works now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 13 15:37:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA04667 for current-outgoing; Wed, 13 Mar 1996 15:37:14 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA04660 for ; Wed, 13 Mar 1996 15:36:56 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA08157; Wed, 13 Mar 1996 16:39:32 -0700 Date: Wed, 13 Mar 1996 16:39:32 -0700 From: Nate Williams Message-Id: <199603132339.QAA08157@rocky.sri.MT.net> To: Juha Inkari Cc: freebsd-current@freebsd.org Subject: Re: X display trouble In-Reply-To: <199603132251.AAA27747@lk-hp-20.hut.fi> References: <199603132251.AAA27747@lk-hp-20.hut.fi> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A resent change has caused my display to not work properly under X > graphics mode. Are you using a laptop? If so, then it's probably be something I've done, otherwise it's still possible but improbable. Nate From owner-freebsd-current Wed Mar 13 15:53:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05699 for current-outgoing; Wed, 13 Mar 1996 15:53:39 -0800 (PST) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05684 for current@FreeBSD.org; Wed, 13 Mar 1996 15:53:36 -0800 (PST) Date: Wed, 13 Mar 1996 15:53:36 -0800 (PST) From: Jeffrey Hsu Message-Id: <199603132353.PAA05684@freefall.freebsd.org> To: current@FreeBSD.org Subject: Re: To pick a (perl) fight! Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'd say that until Larry writes a Perl 5 book so that there's some easily accessible documentation for it then There are over a hundred pages in the perl 5 man pages split out over 27 sections. I believe free, printable, and searchable on-line man pages qualifies as easily accessible documentation. most people will stick with perl 4 unless they have a particular need for perl5. Like I write all my scripts in perl5 now? :-) Given that the momentum is very much against switching to perl 5 (for this and similar reasons) I think we'd stay more compatible with the rest of the world sticking with perl 4 for the moment. Strange, I assess the current momentum as obsoleting perl4 and going to perl5. We'd also have to fix all the perl code we use if we switch to perl 5. We will have to do this sooner or later. A lazy short-cut is to change the first line of the scripts to read #!perl4. Furthermore, perl5 is mostly compatible w/ perl4 and the differences are well-documented. I've been running w/ perl5 as the default perl on my system since early last year. From owner-freebsd-current Wed Mar 13 16:03:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA06316 for current-outgoing; Wed, 13 Mar 1996 16:03:25 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA06306 for ; Wed, 13 Mar 1996 16:03:21 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id AAA06104 for ; Thu, 14 Mar 1996 00:01:17 GMT Received: from tees by snowdon with SMTP (PP); Wed, 13 Mar 1996 23:57:25 +0000 Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id AAA28719; Thu, 14 Mar 1996 00:01:29 GMT Date: Thu, 14 Mar 1996 00:01:29 GMT From: Paul Richards Message-Id: <199603140001.AAA28719@tees> To: current@FreeBSD.org, hsu@freefall.freebsd.org Subject: Re: To pick a (perl) fight! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: ck3h+y9HhmLUoIrJKJsD5A== Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'd say that until Larry writes a Perl 5 book so that > there's some easily accessible documentation for it then > > There are over a hundred pages in the perl 5 man pages split out > over 27 sections. I believe free, printable, and searchable on-line > man pages qualifies as easily accessible documentation. I think that's a matter of opinion :-) Most people I know (me included) prefer a book any day of the month. From owner-freebsd-current Wed Mar 13 16:26:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA07726 for current-outgoing; Wed, 13 Mar 1996 16:26:57 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA07721 for ; Wed, 13 Mar 1996 16:26:50 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA08352; Wed, 13 Mar 1996 17:29:17 -0700 Date: Wed, 13 Mar 1996 17:29:17 -0700 From: Nate Williams Message-Id: <199603140029.RAA08352@rocky.sri.MT.net> To: Jeffrey Hsu Cc: current@FreeBSD.org Subject: Re: To pick a (perl) fight! In-Reply-To: <199603132353.PAA05684@freefall.freebsd.org> References: <199603132353.PAA05684@freefall.freebsd.org> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'd say that until Larry writes a Perl 5 book so that > there's some easily accessible documentation for it then > > There are over a hundred pages in the perl 5 man pages split out > over 27 sections. I believe free, printable, and searchable on-line > man pages qualifies as easily accessible documentation. Except that not everyone is on the WWW yet, and the on-line documentation is nowhere near as browsable as my Perl 4 book. > most people will stick with perl 4 unless they have a > particular need for perl5. > > Like I write all my scripts in perl5 now? :-) I write my scripts which run in both, which is pretty trivial to do. I don't take advantage of any of the Perl 5 features obviously, but it's more portable that way (across multiple OS's). > We'd also have to fix all the perl code we use if we switch to perl 5. > > We will have to do this sooner or later. A lazy short-cut is to > change the first line of the scripts to read #!perl4. Since perl4 is shipped, we *don't* want to be shipping both perl4 and perl5 in our default distribution. This is not acceptable. Finally, the size of the perl5 distribution is much larger than that of perl4, and no-one has stepped forward with a Perl5 that has been properly B-maked, so it can replace current perl4. Nate From owner-freebsd-current Wed Mar 13 16:35:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08412 for current-outgoing; Wed, 13 Mar 1996 16:35:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA08406 for ; Wed, 13 Mar 1996 16:35:19 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA09749; Wed, 13 Mar 1996 17:32:41 -0700 From: Terry Lambert Message-Id: <199603140032.RAA09749@phaeton.artisoft.com> Subject: Re: To pick a (perl) fight! To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Wed, 13 Mar 1996 17:32:41 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199603132353.PAA05684@freefall.freebsd.org> from "Jeffrey Hsu" at Mar 13, 96 03:53:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'd say that until Larry writes a Perl 5 book so that > there's some easily accessible documentation for it then > > There are over a hundred pages in the perl 5 man pages split out > over 27 sections. I believe free, printable, and searchable on-line > man pages qualifies as easily accessible documentation. This may shock you, but I don't own a printer (I probably personally own more computers than 95% of the people on the list, if they don't count their video equipment, ovens, or bread machines. 8-)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 13 18:27:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA00953 for current-outgoing; Wed, 13 Mar 1996 18:27:47 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA00946 for ; Wed, 13 Mar 1996 18:27:41 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id RAA15604; Wed, 13 Mar 1996 17:59:11 -0800 From: "Rodney W. Grimes" Message-Id: <199603140159.RAA15604@GndRsh.aac.dev.com> Subject: Re: To pick a (perl) fight! To: terry@lambert.org (Terry Lambert) Date: Wed, 13 Mar 1996 17:59:10 -0800 (PST) Cc: hsu@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199603140032.RAA09749@phaeton.artisoft.com> from "Terry Lambert" at Mar 13, 96 05:32:41 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'd say that until Larry writes a Perl 5 book so that > > there's some easily accessible documentation for it then > > > > There are over a hundred pages in the perl 5 man pages split out > > over 27 sections. I believe free, printable, and searchable on-line > > man pages qualifies as easily accessible documentation. > > This may shock you, but I don't own a printer (I probably personally > own more computers than 95% of the people on the list, if they don't > count their video equipment, ovens, or bread machines. 8-)). Can I count my inventory, and units in burnin :-) :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Mar 13 18:27:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA00969 for current-outgoing; Wed, 13 Mar 1996 18:27:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA00960 for ; Wed, 13 Mar 1996 18:27:47 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA09915; Wed, 13 Mar 1996 19:23:32 -0700 From: Terry Lambert Message-Id: <199603140223.TAA09915@phaeton.artisoft.com> Subject: Re: To pick a (perl) fight! To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 13 Mar 1996 19:23:32 -0700 (MST) Cc: terry@lambert.org, hsu@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199603140159.RAA15604@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 13, 96 05:59:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'd say that until Larry writes a Perl 5 book so that > > > there's some easily accessible documentation for it then > > > > > > There are over a hundred pages in the perl 5 man pages split out > > > over 27 sections. I believe free, printable, and searchable on-line > > > man pages qualifies as easily accessible documentation. > > > > This may shock you, but I don't own a printer (I probably personally > > own more computers than 95% of the people on the list, if they don't > > count their video equipment, ovens, or bread machines. 8-)). > > Can I count my inventory, and units in burnin :-) :-) No. Or Yes, if you are willing to be one of the 5%. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 13 20:28:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA00914 for current-outgoing; Wed, 13 Mar 1996 20:28:16 -0800 (PST) Received: from who.cdrom.com ([204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA00909 for ; Wed, 13 Mar 1996 20:28:15 -0800 (PST) Received: from jolt.eng.umd.edu (jolt.eng.umd.edu [129.2.102.5]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id UAA00603 for ; Wed, 13 Mar 1996 20:28:14 -0800 Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.98.208]) by jolt.eng.umd.edu (8.7.5/8.7.3) with ESMTP id XAA18372; Wed, 13 Mar 1996 23:26:57 -0500 (EST) Received: (from chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) id XAA15394; Wed, 13 Mar 1996 23:26:56 -0500 (EST) Date: Wed, 13 Mar 1996 23:26:55 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: To pick a (perl) fight! In-Reply-To: <199603132140.XAA00297@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Mar 1996, Mark Murray wrote: > Hi > > What are the reasons we do not now have Perl5 in the main tree? I have > a query from one of our more perl-literate users who made the suggestion > that Perl4 should be in ports/. > > What say y'all? > Perl and tcl ... two good utilities that are both going thru schizophrenia. These have both gone thru recent upgrades, are both significantly more powerful because of it, and cannot be migrated to because of tons of legacy software that the newer versions are incompatible with. To be honest, I think perl will recover first, but I think it's true of both. Perl 5 is in ports, do you really think we need _both_ perl and perl5? Because I don't think we can dump perl yet. ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-current Wed Mar 13 22:48:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04813 for current-outgoing; Wed, 13 Mar 1996 22:48:30 -0800 (PST) Received: from who.cdrom.com ([204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA04808 for ; Wed, 13 Mar 1996 22:48:29 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id WAA01219 for ; Wed, 13 Mar 1996 22:48:27 -0800 Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id HAA27348 for current@freebsd.org; Thu, 14 Mar 1996 07:30:17 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id HAA00620 for current@freebsd.org; Thu, 14 Mar 1996 07:28:53 +0100 (MET) From: Andreas Klemm Message-Id: <199603140628.HAA00620@knobel.gun.de> Subject: sendmail doesn't write exactly in mailbox format To: current@freebsd.org Date: Thu, 14 Mar 1996 07:28:53 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I hoped, that after doing a make world this ugly error would vanish but it doesn't. Since about beginning of March I have a big problem with sendmail. It doesn't write strictly mailbox format. If a mail is appended to a file because of such an entry in /etc/aliases: freebsd-current: /home/andreas/mailing-lists/freebsd-current then the new mail will be saved with a leading ' ' (whitespace) in front of the first From of a new mail. This causes articles to vanish, since every mailer searches a new article in a mailfolder file by looking for a "From" at the very beginning of a line. I already checked, that it isn't elm or pine's fault. It's sendmail writing this garbage. Where in hell does that leading whitespace come from ?! I wrote a little shellscript, that repairs my mailinglist folders by doing this: #! /bin/sh for i in $* do ex $i << !EOM g/^\ From\ /s/^\ From\ /From\ / w q !EOM done What makes me really wonder is the fact, that mail in my incoming mailfolder isn't crippled, only things I save into a file by an entry in /etc/aliases. Example: ---------------------------------- Rest of a previous mail......................... Finally, the size of the perl5 distribution is much larger than that of perl4, and no-one has stepped forward with a Perl5 that has been properly B-maked, so it can replace current perl4. Nate From owner-freebsd-current@freefall.freebsd.org Thu Mar 14 07:12:34 1996 ^----------------- THIS IS THE NASTY THING Return-Path: owner-freebsd-current@freefall.freebsd.org Received: (from uucp@localhost) by knobel.gun.de (8.7.4/8.7.3) with UUCP id HAA00505 for freebsd-current@knobel.gun.de; Thu, 14 Mar 1996 07:12:34 +0100 (MET) Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de [130.83.63.20]) by news1.gtn.com (8.7.2/8.7.2) with ESMTP id GAA05029 for ; Thu, 14 Mar 1996 06:37:05 +0100 (MET) Received: from freefall.freebsd.org ([204.216.27.4]) by zit1.zit.th-darmstadt.de (8.7.4/8.6.9) with ESMTP id GAA03403; Thu, 14 Mar 1996 06:39:13 +0100 (MET) Received: from localhost (daemon@localhost) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA27955 Wed, 13 Mar 1996 13:48:46 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA27942 for current-outgoing; Wed, 13 Mar 1996 13:48:43 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA27933 for ; Wed, 13 Mar 1996 13:48:34 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA15313; Wed, 13 Mar 1996 13:48:19 -0800 From: "Rodney W. Grimes" Message-Id: <199603132148.NAA15313@GndRsh.aac.dev.com> -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Wed Mar 13 23:57:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA06769 for current-outgoing; Wed, 13 Mar 1996 23:57:34 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA06764 for ; Wed, 13 Mar 1996 23:57:32 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id XAA01844 for ; Wed, 13 Mar 1996 23:57:31 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id IAA21821 ; Thu, 14 Mar 1996 08:56:03 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id IAA22142 ; Thu, 14 Mar 1996 08:56:02 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.4/keltia-uucp-2.7) id IAA09219; Thu, 14 Mar 1996 08:43:00 +0100 (MET) From: Ollivier Robert Message-Id: <199603140743.IAA09219@keltia.freenix.fr> Subject: Re: To pick a (perl) fight! To: mark@grondar.za (Mark Murray) Date: Thu, 14 Mar 1996 08:43:00 +0100 (MET) Cc: current@FreeBSD.org In-Reply-To: <199603132140.XAA00297@grumble.grondar.za> from Mark Murray at "Mar 13, 96 11:40:02 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1762 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk It seems that Mark Murray said: > What are the reasons we do not now have Perl5 in the main tree? I have > a query from one of our more perl-literate users who made the suggestion > that Perl4 should be in ports/. 1. Perl5 is far too big for us to maintain it in the main source tree, the installed files take this: 6368 perl5 627 perl 2. the building process is far more complex than Perl4 used to be because of all the extensions available in Perl5. There are many things I doubt we can change into Bmakefiles. 3. Perl5 sources, as of 5.002 are more then 6.6 MB worth where Perl4 is around 2 MB. Having Perl4 in the tree in a good thing because it is small and not a moving target anymore. Perl5 would bloat us. Don't take this wrong, I'm a Perl fan and I'm use Perl5 as much as I can but I really think we should not take it under our wing. The port is easy enough to compile/install and the package is there for people who don't want to compile it. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #6: Mon Mar 11 20:18:10 MET 1996 From owner-freebsd-current Thu Mar 14 00:09:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07119 for current-outgoing; Thu, 14 Mar 1996 00:09:05 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07113 for ; Thu, 14 Mar 1996 00:09:03 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelay-SVR4_1.3/RBCS) id JAA23396; Thu, 14 Mar 1996 09:08:39 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id JAA11399; Thu, 14 Mar 1996 09:08:32 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id JAA00083; Thu, 14 Mar 1996 09:08:32 +0100 To: Paul Traina cc: Faried Nawaz , current@FreeBSD.ORG Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Wed, 13 Mar 1996 12:08:37 PST." <199603132008.MAA04472@precipice.shockwave.com> Date: Thu, 14 Mar 1996 09:08:30 +0100 Message-ID: <82.826790910@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Mar 1996 12:08:37 PST, Paul Traina wrote: > I'd give them the following summary: [ nice bug report deleted ] I'd like to thank Paul for the nice bug report template. Here are some minor clarifications: RFC-794 --> RFC793 (!!) Garret --> Garrett Andreas --> Andras And for further support of our case, here's the relevant paragraph of RFC-793 clearly stating that a TCP implementation must buffer data on SYN segments until the connection becomes open: - begin quote - September 1981 Transmission Control Protocol Functional Specification [ ... ] Several examples of connection initiation follow. Although these examples do not show connection synchronization using data-carrying segments, this is perfectly legitimate, so long as the receiving TCP doesn't deliver the data to the user until it is clear the data is valid (i.e., the data must be buffered at the receiver until the connection reaches the ESTABLISHED state). The three-way handshake reduces the possibility of false connections. It is the [Page 30] - end of quote - Andras From owner-freebsd-current Thu Mar 14 00:22:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07541 for current-outgoing; Thu, 14 Mar 1996 00:22:18 -0800 (PST) Received: from maui.com (root@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07536 for ; Thu, 14 Mar 1996 00:22:12 -0800 (PST) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by maui.com (8.6.10/8.6.6) with ESMTP id WAA17260; Wed, 13 Mar 1996 22:21:55 -1000 Received: (from root@localhost) by caliban.dihelix.com (8.7.4/8.6.9) id WAA00216; Wed, 13 Mar 1996 22:21:33 -1000 (HST) Message-Id: <199603140821.WAA00216@caliban.dihelix.com> Subject: Re: X display trouble To: inkari@snakemail.hut.fi (Juha Inkari) Date: Wed, 13 Mar 1996 22:21:32 -1000 (HST) From: "David Langford" Cc: freebsd-current@freebsd.org In-Reply-To: <199603132251.AAA27747@lk-hp-20.hut.fi> from "Juha Inkari" at Mar 14, 96 00:51:28 am From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have exactly the same problem now. My kernels made from March 12 on seem to give blank screens, garbage or hang the system with starting X. My kernel made March 11 (last sup then would have been about 11:30PM PST) seems to work okay in X (although it crashes when I run Linux Elf files :). Also I am running Xinside v1.2 and a Diamond Stealth Pro (ISA). I am NOT running on a laptop. -David Langford langfod@dihelix.com >A resent change has caused my display to not work properly under X >graphics mode. The system seems to work ok otherwise, except there is >no picture on graphics mode, just blank screen. Operating "blindly" >seems to work (login, runnig xterms etc.). I have tried with Xinside's >1.2 server with a Diamond Stealt adapter (X sever reports is as S3,1: >86C968,TVP3026 (2048k @fa000000, [0.000 - 175.000MHz])). > >I have a Mar 11 16:45 kernel, current level of ctm delta cvs-cur.1761 >that still seems to be ok, but a Mar 12 21:28 compilation from ctm >delta cvs-cur.1766 has the display feature. If I have correctly looked >it up, the cause must have been something, that is on the >commitlogs/sys between the changes: > >nate 96/03/10 22:48:58 >davidg 96/03/12 07:38:02 From owner-freebsd-current Thu Mar 14 00:24:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07650 for current-outgoing; Thu, 14 Mar 1996 00:24:05 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07645 for ; Thu, 14 Mar 1996 00:24:04 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA02002 for ; Thu, 14 Mar 1996 00:23:56 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA16598 for ; Thu, 14 Mar 1996 09:22:16 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA25866 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 09:22:15 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA00353 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 09:17:57 +0100 (MET) From: J Wunsch Message-Id: <199603140817.JAA00353@uriah.heep.sax.de> Subject: Kernel from yesterday still hanging To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 14 Mar 1996 09:17:57 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk While the kernel does now run an Xserver with Xkb enabled, and it also doesn't seem to panic anymore with one of the vm_map panics, it still hung after only a few hours uptime. The SCSI LED was on, but apart from this, i don't have any sign what might have gone wrong. The system was running a ``make World'' for XFree86 by that time. Judging from the time the hang occured, it's been during /etc/daily. Bingo! My CD-ROM? Urrgs. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 14 00:25:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07691 for current-outgoing; Thu, 14 Mar 1996 00:25:27 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07686 for ; Thu, 14 Mar 1996 00:25:26 -0800 (PST) Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA02040 for ; Thu, 14 Mar 1996 00:25:23 -0800 Received: (from winter@localhost) by sasami.jurai.net (8.7.4/8.7.3) id CAA13776; Thu, 14 Mar 1996 02:25:25 -0600 (CST) Date: Thu, 14 Mar 1996 02:25:24 -0600 (CST) From: "Matthew N. Dodd" X-Sender: winter@sasami To: Chuck Robey cc: current@freebsd.org Subject: Re: To pick a (perl) fight! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Mar 1996, Chuck Robey wrote: > Perl 5 is in ports, do you really think we need _both_ perl and perl5? > Because I don't think we can dump perl yet. Why not ask Larry Wall what he thinks of Perl4? *grin* It can go away for all I care. I'm hard pressed to think of anything I use that requires perl4. If I'm wrong, tell me. :) Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-current Thu Mar 14 00:56:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA08872 for current-outgoing; Thu, 14 Mar 1996 00:56:38 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA08867 for ; Thu, 14 Mar 1996 00:56:36 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA02963 for ; Thu, 14 Mar 1996 00:56:31 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA06144 for ; Thu, 14 Mar 1996 09:52:40 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA26101 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 09:52:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA00766 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 09:49:06 +0100 (MET) From: J Wunsch Message-Id: <199603140849.JAA00766@uriah.heep.sax.de> Subject: Re: sendmail doesn't write exactly in mailbox format To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 14 Mar 1996 09:49:06 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603140628.HAA00620@knobel.gun.de> from "Andreas Klemm" at Mar 14, 96 07:28:53 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Andreas Klemm wrote: > What makes me really wonder is the fact, that mail in my incoming > mailfolder isn't crippled, only things I save into a file by an > entry in /etc/aliases. Incoming mail is handed off to /usr/libexec/mail.local. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 14 01:22:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA10473 for current-outgoing; Thu, 14 Mar 1996 01:22:20 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA10463 for ; Thu, 14 Mar 1996 01:22:17 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id BAA03700 for ; Thu, 14 Mar 1996 01:22:12 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA24846 for ; Thu, 14 Mar 1996 10:20:42 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA26201 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 10:20:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA00828 for freebsd-current@FreeBSD.org; Thu, 14 Mar 1996 09:52:51 +0100 (MET) From: J Wunsch Message-Id: <199603140852.JAA00828@uriah.heep.sax.de> Subject: Re: To pick a (perl) fight! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 14 Mar 1996 09:52:50 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199603132305.XAA28625@tees> from "Paul Richards" at Mar 13, 96 11:05:25 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Paul Richards wrote: > Given that the momentum is very much against switching to perl 5 > (for this and similar reasons) I think we'd stay more compatible > with the rest of the world sticking with perl 4 for the moment. Follow comp.lang.perl (which should better be named comp.lang.cgi mostly :), and mention that you are still running Perl 4. You'll see the word ``obsolete'' in reply... Btw., i've got Perl4 scripts that core-dumped the original perl 4, while running fine under /usr/local/bin/perl. I'm all for switching, and fixing what might become broken. If we never start, we'll never arrive. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 14 01:35:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA11245 for current-outgoing; Thu, 14 Mar 1996 01:35:00 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA11240 for ; Thu, 14 Mar 1996 01:34:58 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id BAA04262 for ; Thu, 14 Mar 1996 01:34:56 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id UAA08166 for current@freebsd.org; Thu, 14 Mar 1996 20:14:43 +1030 From: Michael Smith Message-Id: <199603140944.UAA08166@genesis.atrad.adelaide.edu.au> Subject: Truncated 'cp.c'? To: current@freebsd.org Date: Thu, 14 Mar 1996 20:14:42 +1030 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmm, possibly only a sup.au problem; anyone else have this : * * $Id: cp.c,v 1.10 1996/03/08 06:58:06 wosch Exp $ */ ... then further down : } /* * Need to detect the case: * cp -R dir foo * Where dir is a directory a ... and there the file ends. Tried a fresh sup but still no joy 8( -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Mar 14 02:03:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA12459 for current-outgoing; Thu, 14 Mar 1996 02:03:42 -0800 (PST) Received: from mx10.netvision.net.il (mx10.NetVision.net.il [194.90.1.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA12450 for ; Thu, 14 Mar 1996 02:03:37 -0800 (PST) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mx10.netvision.net.il (8.7.3/8.7.1) with SMTP id NAA01522 for ; Thu, 14 Mar 1996 13:03:40 +0200 Message-ID: X-Mailer: XFMail 0.4-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199603140817.JAA00353@uriah.heep.sax.de> Date: Thu, 14 Mar 1996 12:03:51 +0200 (IST) Reply-To: gena@NetVision.net.il X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: (FreeBSD-current users) Subject: RE: Kernel from yesterday still hanging Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On the same issue. My system locks up when i try to run Xinside-1.2 X server. Kernel from March 10 runs Xinsied just fine. any ideas? Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 03/14/96 12:03:53 by XF-Mail From owner-freebsd-current Thu Mar 14 03:06:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA15772 for current-outgoing; Thu, 14 Mar 1996 03:06:55 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA15767 Thu, 14 Mar 1996 03:06:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id WAA07910; Wed, 13 Mar 1996 22:45:00 -0800 (PST) To: Bruce Evans cc: terry@lambert.org, amurai@spec.co.jp, current@FreeBSD.org, sos@FreeBSD.org Subject: Re: Native & Linux ELF support finally there... In-reply-to: Your message of "Wed, 13 Mar 1996 13:36:48 +1100." <199603130236.NAA21238@godzilla.zeta.org.au> Date: Wed, 13 Mar 1996 22:44:59 -0800 Message-ID: <7908.826785899@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >I agree. In connection with the current Linux emulation, this is the > >#1 question I get ("I try to run my Linux binary and it says can't > >execute binary file, what do I doooooooo?!"). > > Where have you been? :-) Option COMPAT_LINUX went away almost 2 weeks > ago (except in options.i386). I thought I saw something about this, but the perils of holding 30-40 conversations simultaneously is that you start to doubt your own memory.. :-) Happy to have confirmation of a nagging doubt (and COMPAT_LINUX to be gone!). Jordan From owner-freebsd-current Thu Mar 14 03:27:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA16317 for current-outgoing; Thu, 14 Mar 1996 03:27:02 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA16312 Thu, 14 Mar 1996 03:26:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id DAA02713; Thu, 14 Mar 1996 03:21:50 -0800 (PST) To: "David Langford" , "David Langford" cc: inkari@snakemail.hut.fi (Juha Inkari), freebsd-current@freebsd.org, dyson@freebsd.org Subject: Re: X display trouble In-reply-to: Your message of "Wed, 13 Mar 1996 22:21:32 -1000." <199603140821.WAA00216@caliban.dihelix.com> Date: Thu, 14 Mar 1996 03:21:50 -0800 Message-ID: <2711.826802510@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have exactly the same problem now. My kernels made from March 12 on > seem to give blank screens, garbage or hang the system with starting > X. My kernel made March 11 (last sup then would have been about > 11:30PM PST) seems to work okay in X (although it crashes when > I run Linux Elf files :). I have the same problem also. A kernel built tonite + Xaccel 1.2 == no video. I'm screwed since I can't live without X.. :-( I hate to say it folks, but I think it's back to -stable for me. Current has simply been way too painful these days! :-( Jordan From owner-freebsd-current Thu Mar 14 03:35:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA00378 for current-outgoing; Thu, 14 Mar 1996 03:35:01 -0800 (PST) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA00364 for ; Thu, 14 Mar 1996 03:34:58 -0800 (PST) Received: by pcnet1.pcnet.com (4.1/SMI-4.1) id AA11426; Thu, 14 Mar 96 06:32:14 EST Date: Thu, 14 Mar 96 06:32:14 EST From: eischen@vigrid.com (Daniel Eischen) Message-Id: <9603141132.AA11426@pcnet1.pcnet.com> To: current@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: Truncated 'cp.c'? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hmm, possibly only a sup.au problem; anyone else have this : > > * > * $Id: cp.c,v 1.10 1996/03/08 06:58:06 wosch Exp $ > */ > >... then further down : > > } > /* > * Need to detect the case: > * cp -R dir foo > * Where dir is a directory a > >... and there the file ends. Tried a fresh sup but still no joy 8( I just sup'd from sup2.FreeBSD.org last night and it worked fine for me - no truncated cp.c. Seems your missing the last 200 lines or so :( Dan Eischen From owner-freebsd-current Thu Mar 14 03:54:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA01261 for current-outgoing; Thu, 14 Mar 1996 03:54:01 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA01250 Thu, 14 Mar 1996 03:53:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id DAA02777; Thu, 14 Mar 1996 03:39:49 -0800 (PST) To: gena@NetVision.net.il cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Kernel from yesterday still hanging In-reply-to: Your message of "Thu, 14 Mar 1996 12:03:51 +0200." Date: Thu, 14 Mar 1996 03:39:49 -0800 Message-ID: <2774.826803589@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On the same issue. My system locks up when i try to run Xinside-1.2 X server. > Kernel from March 10 runs Xinsied just fine. It probably doesn't lock up, it's just that X no longer runs. Try to log into your machine from another terminal (or type ctrl-alt-backspace) and verify this. Remember: There's a BIG difference between "my system locks up" and "my X server doesn't start" - please verify which is which before reporting one or the other. Jordan From owner-freebsd-current Thu Mar 14 04:16:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA16317 for current-outgoing; Thu, 14 Mar 1996 03:27:02 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA16312 Thu, 14 Mar 1996 03:26:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id DAA02713; Thu, 14 Mar 1996 03:21:50 -0800 (PST) To: "David Langford" , "David Langford" cc: inkari@snakemail.hut.fi (Juha Inkari), freebsd-current@freebsd.org, dyson@freebsd.org Subject: Re: X display trouble In-reply-to: Your message of "Wed, 13 Mar 1996 22:21:32 -1000." <199603140821.WAA00216@caliban.dihelix.com> Date: Thu, 14 Mar 1996 03:21:50 -0800 Message-ID: <2711.826802510@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have exactly the same problem now. My kernels made from March 12 on > seem to give blank screens, garbage or hang the system with starting > X. My kernel made March 11 (last sup then would have been about > 11:30PM PST) seems to work okay in X (although it crashes when > I run Linux Elf files :). I have the same problem also. A kernel built tonite + Xaccel 1.2 == no video. I'm screwed since I can't live without X.. :-( I hate to say it folks, but I think it's back to -stable for me. Current has simply been way too painful these days! :-( Jordan From owner-freebsd-current Thu Mar 14 04:27:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA02498 for current-outgoing; Thu, 14 Mar 1996 04:27:32 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA02493 for ; Thu, 14 Mar 1996 04:27:27 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id XAA26568; Thu, 14 Mar 1996 23:26:53 +1100 From: michael butler Message-Id: <199603141226.XAA26568@asstdc.scgt.oz.au> Subject: Re: Truncated 'cp.c'? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 14 Mar 1996 23:26:52 +1100 (EST) Cc: current@FreeBSD.org In-Reply-To: <199603140944.UAA08166@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 14, 96 08:14:42 pm X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > Hmm, possibly only a sup.au problem; anyone else have this : [ .. ] > ... and there the file ends. Tried a fresh sup but still no joy 8( sup.au problem .. sup2.au.freebsd.org contains the complete file, michael From owner-freebsd-current Thu Mar 14 04:40:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA03116 for current-outgoing; Thu, 14 Mar 1996 04:40:21 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA03111 for ; Thu, 14 Mar 1996 04:40:20 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id EAA00399 for ; Thu, 14 Mar 1996 04:40:19 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id WAA08386 for current@freebsd.org; Thu, 14 Mar 1996 22:30:26 +1030 From: Michael Smith Message-Id: <199603141200.WAA08386@genesis.atrad.adelaide.edu.au> Subject: -current kernel linuxulator build broken To: current@freebsd.org Date: Thu, 14 Mar 1996 22:30:25 +1030 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just following up on the recent report of a broken build for a kernel with Linux emulation in -current. The failure is this : cpp -DLOCORE -nostdinc -I. -I../.. -I../../sys -I../../../include -DI586_CPU -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../i386/linux/linux_locore.s | as -o linux_locore.o ../../i386/linux/linux_locore.s:1: linux_assym.h: No such file or directory ../../i386/linux/linux_locore.s: Assembler messages: ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SIGF_HANDLER never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SIGF_SC never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SC_FS never defined. ../../i386/linux/linux_locore.s:26: Error: Local symbol LINUX_SC_GS never defined. ../../i386/linux/linux_locore.s:26: Fatal error:4 errors, 0 warnings, no object file generated. The solution is this : genesis-10: {7} make linux_assym.h Either we need to start warning about 'make depend' again, or whatever magic made it unnecessary before needs to be worked again 8) (I suspect this bit Peter because I believe he doesn't do full kernel builds all the time, which is kinda understandable 8) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Mar 14 07:10:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA10847 for current-outgoing; Thu, 14 Mar 1996 07:10:31 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA10842 for ; Thu, 14 Mar 1996 07:10:28 -0800 (PST) Received: from nauplius.rsmas.miami.edu (nauplius.rsmas.miami.edu [129.171.102.27]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id HAA02832 for ; Thu, 14 Mar 1996 07:10:27 -0800 Received: (from ivan@localhost) by nauplius.rsmas.miami.edu (8.6.12/8.6.12) id KAA04254 for freebsd-current@freebsd.org; Thu, 14 Mar 1996 10:09:14 -0500 From: Ivan Lima Message-Id: <199603141509.KAA04254@nauplius.rsmas.miami.edu> Subject: Mathematica under FreeBSD To: freebsd-current@freebsd.org Date: Thu, 14 Mar 1996 10:09:13 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm very interested in running Mathematica in my FreeBSD box and someone in the newsgroup said that a few weeks ago someone anounced success in running Mathematica for Linux under FreeBSD here in the mailing list. So, if anyone has any information on that please let know. Thanks a lot, Ivan -- /| Ivan Lima | O __/ |_ Rosenstiel School of Marine and Atmospheric Science | o /o \_/| Division of Marine Biology and Fisheries | ( < _ | ivan@nauplius.rsmas.miami.edu | \__ _/ \| http://nauplius.rsmas.miami.edu/homepage/home.html | \_| From owner-freebsd-current Thu Mar 14 07:53:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA14115 for current-outgoing; Thu, 14 Mar 1996 07:53:07 -0800 (PST) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA14109 for ; Thu, 14 Mar 1996 07:52:57 -0800 (PST) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA00289; Thu, 14 Mar 96 16:53:43 +0100 Date: Thu, 14 Mar 96 16:53:43 +0100 Message-Id: <9603141553.AA00289@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@freebsd.org Subject: kernel from today: general protection fault X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kernel with sources from 1996/03/13/ 03:00 (cvs-cur.1768): ... changing root device to wd0a devfs ready to run Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xf01298ce code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1 (swapper) interrupt mask = net tty bio panic: general protection fault bash# nm /kernel.new|sort|grep f01298 f0129874 T _bread Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Thu Mar 14 07:54:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA14204 for current-outgoing; Thu, 14 Mar 1996 07:54:35 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA14190 for ; Thu, 14 Mar 1996 07:54:33 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA21998; Thu, 14 Mar 1996 09:53:11 -0600 From: Joe Greco Message-Id: <199603141553.JAA21998@brasil.moneng.mei.com> Subject: Re: To pick a (perl) fight! To: terry@lambert.org (Terry Lambert) Date: Thu, 14 Mar 1996 09:53:11 -0600 (CST) Cc: hsu@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199603140032.RAA09749@phaeton.artisoft.com> from "Terry Lambert" at Mar 13, 96 05:32:41 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'd say that until Larry writes a Perl 5 book so that > > there's some easily accessible documentation for it then > > > > There are over a hundred pages in the perl 5 man pages split out > > over 27 sections. I believe free, printable, and searchable on-line > > man pages qualifies as easily accessible documentation. > > This may shock you, but I don't own a printer (I probably personally > own more computers than 95% of the people on the list, if they don't > count their video equipment, ovens, or bread machines. 8-)). Well just how many would that be? Working off my last resource allocation chart, I've got... hm. 7 routers.. 6 servers.. 3 term servers.. 12 general purpose.. probably others.. that's something like 28. Ok, I admit, I counted some of my Suns that aren't in service and two PC motherboards that are "in assembly" :-) Most of the machines run FreeBSD. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-current Thu Mar 14 08:04:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA14876 for current-outgoing; Thu, 14 Mar 1996 08:04:49 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA14871 for ; Thu, 14 Mar 1996 08:04:46 -0800 (PST) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id IAA03481 for ; Thu, 14 Mar 1996 08:04:44 -0800 Received: from caught.inna.net (caught.inna.net [206.151.66.7]) by tyger.inna.net (8.7.3/8.7.3) with SMTP id LAA05019 for ; Thu, 14 Mar 1996 11:04:08 -0500 (EST) Date: Thu, 14 Mar 1996 11:02:30 -0500 (EST) From: Thomas Arnold To: current@freebsd.org Subject: Problems building -current. What am I doing wrong. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay... I supped current. I type make world. I watched the world run before exploding after about 20 minutes. --- cut here --- /usr/src/usr.bin/vgring /usr/obj/usr.bin/vgrind : : is a directory : : is a directory *** error code 1 --- cut here --- Suggestions anyone? What have I done wrong? I have supped and compiled -stable without trouble and am VERY happy ( thanks Freebsd hackers! ) I can finally run PMConsole! +-----------------------------------------------+ : Tom Arnold - No relation to Rosanne : : SysAdmin/Pres - TBI, Ltd ( inna.net ) : : An ISP serving the Virginia Middle Penninsula : +-----------------------------------------------+ From owner-freebsd-current Thu Mar 14 09:01:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA18526 for current-outgoing; Thu, 14 Mar 1996 09:01:17 -0800 (PST) Received: from antares.mcs.anl.gov (mcs.anl.gov [140.221.9.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA18519 for ; Thu, 14 Mar 1996 09:01:13 -0800 (PST) Received: from donner (donner.mcs.anl.gov [140.221.5.134]) by antares.mcs.anl.gov (8.6.10/8.6.10) with ESMTP id LAA07565 for ; Thu, 14 Mar 1996 11:01:12 -0600 From: Jonathan Geisler Message-Id: <199603141701.LAA07050@donner> Subject: Re: To pick a (perl) fight! To: current@freebsd.org Date: Thu, 14 Mar 1996 11:01:10 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL10 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Many of you mentioned that Perl 5 does not have a book as a good reason for not using it. I would just like to say that I noticed O'Reilly will be releasing one this spring (April?), so that argument is not going to be valid much longer. +--------------------------------------------------+ | Jonathan Geisler | | Mathematics & Computer Science Division | | Argonne National Laboratory | | http://www.mcs.anl.gov/people/geisler/index.html | +--------------------------------------------------+ From owner-freebsd-current Thu Mar 14 09:23:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA19883 for current-outgoing; Thu, 14 Mar 1996 09:23:56 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA19869 for ; Thu, 14 Mar 1996 09:23:49 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id SAA02982 for current@freebsd.org; Thu, 14 Mar 1996 18:00:29 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.4/8.7.3) id HAA00193 for current@freebsd.org; Thu, 14 Mar 1996 07:46:44 +0100 (MET) From: Andreas Klemm Message-Id: <199603140646.HAA00193@knobel.gun.de> Subject: mrouted: can't enable multicast routing in kernel: Operation not supported To: current@freebsd.org Date: Thu, 14 Mar 1996 07:46:44 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This since my last rebuild using ctm level 1790. This message show up on the console during booting, but it won't be logged is messages. What does that mean ? I only updated /etc/rc and /etc/rc.serial. Was there introduced something new, that I have to update other files in /etc, too ? -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Thu Mar 14 09:54:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA21834 for current-outgoing; Thu, 14 Mar 1996 09:54:59 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA21827 for ; Thu, 14 Mar 1996 09:54:58 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA05238 for ; Thu, 14 Mar 1996 09:54:55 -0800 Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id VAA01505; Wed, 13 Mar 1996 21:58:38 -0800 (PST) Date: Wed, 13 Mar 1996 21:58:38 -0800 (PST) From: invalid opcode To: Chuck Robey cc: Mark Murray , current@freebsd.org Subject: Re: To pick a (perl) fight! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Mar 1996, Chuck Robey wrote: > Perl 5 is in ports, do you really think we need _both_ perl and perl5? > Because I don't think we can dump perl yet. I think you can, considering that perl5 can run in complete perl4 compatibility. Plus as someone said before, we are going to have to rewrite our system perl scripts anyways, so why not do it now. > Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Thu Mar 14 09:55:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA21879 for current-outgoing; Thu, 14 Mar 1996 09:55:07 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA21863 for ; Thu, 14 Mar 1996 09:55:02 -0800 (PST) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA05247 for ; Thu, 14 Mar 1996 09:55:00 -0800 Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/nervosa.com.2) with SMTP id TAA29107; Wed, 13 Mar 1996 19:54:58 -0800 (PST) Date: Wed, 13 Mar 1996 19:54:55 -0800 (PST) From: invalid opcode To: Nate Williams cc: Jeffrey Hsu , current@freebsd.org Subject: Re: To pick a (perl) fight! In-Reply-To: <199603140029.RAA08352@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Mar 1996, Nate Williams wrote: > Except that not everyone is on the WWW yet, and the on-line > documentation is nowhere near as browsable as my Perl 4 book. I would say anyone who is going to do serious, or even non-serious Perl work has access to the web somehow. Almost everyone who uses a good isp has access to the web. > Nate > == Chris Layne ============================================================= == coredump@nervosa.com ================ http://www.nervosa.com/~coredump == From owner-freebsd-current Thu Mar 14 09:56:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA22072 for current-outgoing; Thu, 14 Mar 1996 09:56:28 -0800 (PST) Received: from yuri.microsoft.com (exchange.microsoft.com [131.107.243.48]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA22055 for ; Thu, 14 Mar 1996 09:56:18 -0800 (PST) Received: by yuri.microsoft.com with Microsoft Exchange (IMC 4.0.837.3) id <01BB118C.3D23F180@yuri.microsoft.com>; Thu, 14 Mar 1996 09:54:30 -0800 Message-ID: From: "Scott Overholser (Volt Computer) (Exchange)" To: "'current@FreeBSD.org'" Subject: RE: To pick a (perl) fight! Date: Thu, 14 Mar 1996 09:54:23 -0800 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk yes, methinks most folks do prefer books. however, the camel book is mostly the perl 4 manpages all bound up nicely. i've printed all 200 pages of the perl 5 manpages and put them into a small binder to make a pretty handy perl 5 reference book. scotto >---------- >From: Paul Richards[SMTP:p.richards@elsevier.co.uk] >Sent: Wednesday, March 13, 1996 4:01 PM >To: current@FreeBSD.org; hsu@freefall.freebsd.org >Subject: Re: To pick a (perl) fight! > >> I'd say that until Larry writes a Perl 5 book so that >> there's some easily accessible documentation for it then >> >> There are over a hundred pages in the perl 5 man pages split out >> over 27 sections. I believe free, printable, and searchable on-line >> man pages qualifies as easily accessible documentation. > >I think that's a matter of opinion :-) Most people I know (me included) >prefer a book any day of the month. > From owner-freebsd-current Thu Mar 14 10:08:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22768 for current-outgoing; Thu, 14 Mar 1996 10:08:13 -0800 (PST) Received: from rich.isdn.bcm.tmc.edu (RICH.ISDN.BCM.TMC.EDU [128.249.250.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA22763 for ; Thu, 14 Mar 1996 10:08:11 -0800 (PST) Received: (from rich@localhost) by rich.isdn.bcm.tmc.edu (8.6.12/8.6.12) id MAA19036; Thu, 14 Mar 1996 12:07:29 -0600 Date: Thu, 14 Mar 1996 12:07:29 -0600 Message-Id: <199603141807.MAA19036@rich.isdn.bcm.tmc.edu> From: Rich Murphey To: ivan@nauplius.rsmas.miami.edu CC: freebsd-current@freebsd.org In-reply-to: <199603141509.KAA04254@nauplius.rsmas.miami.edu> (message from Ivan Lima on Thu, 14 Mar 1996 10:09:13 -0500 (EST)) Subject: Re: Mathematica under FreeBSD Reply-to: rich@lamprey.utmb.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk |From: Ivan Lima |Date: Thu, 14 Mar 1996 10:09:13 -0500 (EST) | |I'm very interested in running Mathematica in my FreeBSD box and |someone in the newsgroup said that a few weeks ago someone anounced |success in running Mathematica for Linux under FreeBSD here in the mailing |list. So, if anyone has any information on that please let know. Thanks a lot, |Ivan I run 'Mathematica 2.2 for Linux (x86)' on FreeBSD-stable and everything including the x front end (mathematica and mathbook) work just fine. Rich From owner-freebsd-current Thu Mar 14 10:18:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA23248 for current-outgoing; Thu, 14 Mar 1996 10:18:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA23240 for ; Thu, 14 Mar 1996 10:18:50 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA11387; Thu, 14 Mar 1996 11:14:34 -0700 From: Terry Lambert Message-Id: <199603141814.LAA11387@phaeton.artisoft.com> Subject: Re: To pick a (perl) fight! To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 14 Mar 1996 11:14:34 -0700 (MST) Cc: chuckr@Glue.umd.edu, current@FreeBSD.org In-Reply-To: from "Matthew N. Dodd" at Mar 14, 96 02:25:24 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It can go away for all I care. I'm hard pressed to think of anything > I use that requires perl4. If I'm wrong, tell me. :) This list. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Mar 14 10:23:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA23413 for current-outgoing; Thu, 14 Mar 1996 10:23:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA23404 for ; Thu, 14 Mar 1996 10:23:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA11399; Thu, 14 Mar 1996 11:18:24 -0700 From: Terry Lambert Message-Id: <199603141818.LAA11399@phaeton.artisoft.com> Subject: Re: To pick a (perl) fight! To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Thu, 14 Mar 1996 11:18:24 -0700 (MST) Cc: terry@lambert.org, hsu@freefall.freebsd.org, current@FreeBSD.org In-Reply-To: <199603141553.JAA21998@brasil.moneng.mei.com> from "Joe Greco" at Mar 14, 96 09:53:11 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > There are over a hundred pages in the perl 5 man pages split out > > > over 27 sections. I believe free, printable, and searchable on-line > > > man pages qualifies as easily accessible documentation. > > > > This may shock you, but I don't own a printer (I probably personally > > own more computers than 95% of the people on the list, if they don't > > count their video equipment, ovens, or bread machines. 8-)). > > Well just how many would that be? Working off my last resource allocation > chart, I've got... hm. 7 routers.. 6 servers.. 3 term servers.. 12 general > purpose.. probably others.. that's something like 28. You include routers? Well, you're an ISP; most of us aren't. Including my loaners, I have around 18. > Ok, I admit, I counted some of my Suns that aren't in service and two PC > motherboards that are "in assembly" :-) Most of the machines run FreeBSD. I noticed that there wer no printers on your list. 8-) 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Mar 14 11:04:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25541 for current-outgoing; Thu, 14 Mar 1996 11:04:16 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25536 for ; Thu, 14 Mar 1996 11:04:15 -0800 (PST) Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id LAA06112 for ; Thu, 14 Mar 1996 11:04:14 -0800 Received: (from winter@localhost) by sasami.jurai.net (8.7.4/8.7.3) id NAA11432; Thu, 14 Mar 1996 13:04:14 -0600 (CST) Date: Thu, 14 Mar 1996 13:04:14 -0600 (CST) From: "Matthew N. Dodd" X-Sender: winter@sasami To: Terry Lambert cc: current@FreeBSD.org Subject: Re: To pick a (perl) fight! In-Reply-To: <199603141814.LAA11387@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Mar 1996, Terry Lambert wrote: > > It can go away for all I care. I'm hard pressed to think of anything > > I use that requires perl4. If I'm wrong, tell me. :) > This list. Of course. But its pretty simple to modify it to work with perl5. I'm running all my majordomo lists using perl5. At what point does it become more expensive to hold on to old software, rather than pulling in the new and risk breaking a few things. Either way... I'm using perl5 here, and when I install a new box, I install perl5. Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-current Thu Mar 14 11:47:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA27275 for current-outgoing; Thu, 14 Mar 1996 11:47:02 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA27268 for ; Thu, 14 Mar 1996 11:46:59 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA22351; Thu, 14 Mar 1996 13:45:47 -0600 From: Joe Greco Message-Id: <199603141945.NAA22351@brasil.moneng.mei.com> Subject: Re: To pick a (perl) fight! To: terry@lambert.org (Terry Lambert) Date: Thu, 14 Mar 1996 13:45:46 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, terry@lambert.org, hsu@freefall.freebsd.org, current@FreeBSD.org In-Reply-To: <199603141818.LAA11399@phaeton.artisoft.com> from "Terry Lambert" at Mar 14, 96 11:18:24 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > > There are over a hundred pages in the perl 5 man pages split out > > > > over 27 sections. I believe free, printable, and searchable on-line > > > > man pages qualifies as easily accessible documentation. > > > > > > This may shock you, but I don't own a printer (I probably personally > > > own more computers than 95% of the people on the list, if they don't > > > count their video equipment, ovens, or bread machines. 8-)). > > > > Well just how many would that be? Working off my last resource allocation > > chart, I've got... hm. 7 routers.. 6 servers.. 3 term servers.. 12 general > > purpose.. probably others.. that's something like 28. > > You include routers? Sure, they run FreeBSD and they are simply ordinary computers with some specialized hardware and a customized kernel. ;-) > Well, you're an ISP; most of us aren't. Sorta true (technically I'm not an ISP but at a quick glance I could resemble one, but I do own all the equipment personally). ;-) > Including my loaners, I have around 18. Oooops. Loaners. Um. I need to revise my count. And I forgot my laptop too. > > Ok, I admit, I counted some of my Suns that aren't in service and two PC > > motherboards that are "in assembly" :-) Most of the machines run FreeBSD. > > I noticed that there wer no printers on your list. I try to be a "paperless disaster^H^H^H^H^H^H^H^Hoffice" type of guy... I do own a laser and a couple DMP's, but the laser has been "on loan" for eternity and I've never had a real good reason to hook up the dot matrix jobs. I wouldn't count specialized "embedded processor" equipment anyways... and come to think of it I failed to count all the old Commodore stuff I have buried away in storage. > 8-) 8-) 8-). Ditoo. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-current Thu Mar 14 12:14:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28705 for current-outgoing; Thu, 14 Mar 1996 12:14:23 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28700 for ; Thu, 14 Mar 1996 12:14:21 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA11695; Thu, 14 Mar 1996 13:10:42 -0700 From: Terry Lambert Message-Id: <199603142010.NAA11695@phaeton.artisoft.com> Subject: Re: To pick a (perl) fight! To: geisler@mcs.anl.gov (Jonathan Geisler) Date: Thu, 14 Mar 1996 13:10:42 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199603141701.LAA07050@donner> from "Jonathan Geisler" at Mar 14, 96 11:01:10 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Many of you mentioned that Perl 5 does not have a book as a good reason > for not using it. I would just like to say that I noticed O'Reilly will > be releasing one this spring (April?), so that argument is not going to > be valid much longer. Call us back when it's available in bookstores near us. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Mar 14 12:25:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29433 for current-outgoing; Thu, 14 Mar 1996 12:25:02 -0800 (PST) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA29421 for ; Thu, 14 Mar 1996 12:24:50 -0800 (PST) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id OAA13446; Thu, 14 Mar 1996 14:24:43 -0600 Date: Thu, 14 Mar 1996 14:24:43 -0600 From: Jim Lowe Message-Id: <199603142024.OAA13446@miller.cs.uwm.edu> To: jgreco@brasil.moneng.mei.com, terry@lambert.org Subject: Re: To pick a (perl) fight! Cc: current@FreeBSD.ORG, hsu@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Joe Greco > To: terry@lambert.org (Terry Lambert) > Date: Thu, 14 Mar 1996 09:53:11 -0600 (CST) > Cc: hsu@freefall.freebsd.org, current@FreeBSD.ORG > > > > This may shock you, but I don't own a printer (I probably personally > > own more computers than 95% of the people on the list, if they don't > > count their video equipment, ovens, or bread machines. 8-)). > > Well just how many would that be? Working off my last resource allocation > chart, I've got... hm. 7 routers.. 6 servers.. 3 term servers.. 12 general > purpose.. probably others.. that's something like 28. Forget these Apples to Suns comparisions, I think the real question would be what are your telephone (communications) and electric bill MRC costs :-). I know someone running a Vax 780 :-). When you have to upgrade your household electrical service to justify your hobby -- then you really have a reason to grunt :-). -Jim From owner-freebsd-current Thu Mar 14 12:55:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01657 for current-outgoing; Thu, 14 Mar 1996 12:55:34 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA01649 for ; Thu, 14 Mar 1996 12:55:31 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA22438; Thu, 14 Mar 1996 14:52:03 -0600 From: Joe Greco Message-Id: <199603142052.OAA22438@brasil.moneng.mei.com> Subject: Re: To pick a (perl) fight! To: james@miller.cs.uwm.edu.erry@lambert.org.current@FreeBSD.ORG.hsu@freefall.freebsd.org (Jim Lowe) Date: Thu, 14 Mar 1996 14:52:02 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, terry@lambert.org, current@FreeBSD.ORG, hsu@freefall.freebsd.org In-Reply-To: <199603142024.OAA13446@miller.cs.uwm.edu> from "Jim Lowe" at Mar 14, 96 02:24:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This may shock you, but I don't own a printer (I probably personally > > > own more computers than 95% of the people on the list, if they don't > > > count their video equipment, ovens, or bread machines. 8-)). > > > > Well just how many would that be? Working off my last resource allocation > > chart, I've got... hm. 7 routers.. 6 servers.. 3 term servers.. 12 general > > purpose.. probably others.. that's something like 28. > > Forget these Apples to Suns comparisions, > I think the real question would be what are your > telephone (communications) and electric bill MRC > costs :-). About $1400 for telecom and $175 for electric, IIRC. > I know someone running a Vax 780 :-). Ok, that's impressive... I might make a minor dent if I actually powered up my two Sun 3/260's... Sun 3/260 9A Sun Disk Ped. 12A Sun 3/260 9A CGR Disk Ped. 14A --- 44A Of course the easier way to make a dent would be to push either the VAX or the 3/260's out a seventh floor window somewhere. I can't justify running the 3/260's anymore, with 8 MIPS and 2GB of disk between them, at 5400 watts, I could probably measure their operational cost in dollars per hour ... at 12c/kwh (no idea what current rate is) that would be 65c/hour.. or to put it another way, I could buy myself 2GB and a cheap 8+++ MIPS PC for what it would cost to run them for two months. ;-) > When you have to upgrade your household electrical > service to justify your hobby -- then you really > have a reason to grunt :-). Hey, don't laugh, it actually happened the last place I had Solaria at. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-current Thu Mar 14 14:20:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA07346 for current-outgoing; Thu, 14 Mar 1996 14:20:50 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA07339 for ; Thu, 14 Mar 1996 14:20:41 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id WAA29092; Thu, 14 Mar 1996 22:30:21 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.4/8.7.3) with SMTP id WAA18436; Thu, 14 Mar 1996 22:26:42 +0100 (MET) Date: Thu, 14 Mar 1996 22:26:41 +0100 (MET) From: Andreas Klemm To: Rob Mallory cc: "Boyd R. Faulkner" , current@FreeBSD.org Subject: Re: Elfkit-1.0.1 announcement In-Reply-To: <199603130623.WAA14155@wiley.csusb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Mar 1996, Rob Mallory wrote: > > > > According to John Polstra: > > > > > > > > > > > > Elfkit is a collection of tools for compiling and executing ELF > > > programs under FreeBSD-2.1.0-RELEASE and later. It consists of: > > > > ...Cool! Now the linux-hacks at idsoftware can do quake development > under a real OS!! :) I tried to build up elfkit but had big trouble to compile the patched libc (2.1.0). Are there any newer patches available ? Best would be, if one could use -current's libc, then the header files certainly would fit better ... BTW, what about switching totally to elf ?! Then such a hack wouldn't be necessary in the future. I think ELF is currently _the_ standard. Generic compatibility to commercial applications should be one big aim ... Linux went from a.out to ELF, too. Ok, there was a must, but we should do, too. Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-current Thu Mar 14 16:44:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15108 for current-outgoing; Thu, 14 Mar 1996 16:44:09 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA15101 for ; Thu, 14 Mar 1996 16:44:05 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14737(1)>; Thu, 14 Mar 1996 16:43:22 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Thu, 14 Mar 1996 16:43:17 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Andreas Klemm cc: current@freebsd.org Subject: Re: mrouted: can't enable multicast routing in kernel: Operation not supported In-reply-to: Your message of "Wed, 13 Mar 1996 22:46:44 PST." <199603140646.HAA00193@knobel.gun.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Mar 1996 16:43:12 PST From: Bill Fenner Message-Id: <96Mar14.164317pst.177478@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Did you accidentally remove "options MROUTING" from your kernel? Perhaps because of the new opt_