From owner-freebsd-hackers Sun Aug 2 00:38:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11814 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 00:38:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ers.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11791 for ; Sun, 2 Aug 1998 00:38:07 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from king (202.120.100.126) by ers.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Sun, 02 Aug 1998 15:28:32 +0800 From: "Paul King" To: Subject: Can Infomix Run On FreeBSD Date: Sun, 2 Aug 1998 15:30:58 +0800 Message-ID: <01bdbde7$7e0936b0$6f01a8c0@king.ether.online.sh.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Informix had announced Linux Version of their database product, Can it run under FreeBSD? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 01:34:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14805 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 01:34:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phobos.illtel.denver.co.us (phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14800 for ; Sun, 2 Aug 1998 01:34:26 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.8/8.6.9) with SMTP id BAA28983; Sun, 2 Aug 1998 01:35:18 -0700 Date: Sun, 2 Aug 1998 01:35:18 -0700 (PDT) From: Alex Belits To: Paul King cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can Infomix Run On FreeBSD In-Reply-To: <01bdbde7$7e0936b0$6f01a8c0@king.ether.online.sh.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, Paul King wrote: > Informix had announced Linux Version of their database product, Can it run > under FreeBSD? Considering that they claim it to be compiled from informix for solaris sources cleanly, it should, but I haven't seen it, so I may be wrong. -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 01:42:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15259 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 01:42:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15253 for ; Sun, 2 Aug 1998 01:42:17 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id BAA12354; Sun, 2 Aug 1998 01:42:07 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980802014204.A12287@mooseriver.com> Date: Sun, 2 Aug 1998 01:42:04 -0700 From: Josef Grosch To: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? Reply-To: jgrosch@mooseriver.com References: <199808010637.OAA04884@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808010637.OAA04884@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Sat, Aug 01, 1998 at 02:37:58PM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 02:37:58PM +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: >I'm part way through porting this company's seismic data processing code to >FreeBSD and have got most things sorted out except for the fact that there >doesn't seem to be any carefully optimised fft routines available. I do have >the fftpack as found in ports, but I was wondering if there was anything >faster than taht available with source. > >Oh, and if anyone knows where to find the source of X widgets that'll display >seismic traces, power spectrums and the like, I'd be most grateful. My father, a math and computer science professor, suggested "Numerical Recipies", by Press, et al. Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.8 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 03:23:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22940 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 03:23:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22876 for ; Sun, 2 Aug 1998 03:22:23 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA15812; Sun, 2 Aug 1998 06:18:10 -0400 (EDT) From: Peter Dufault Message-Id: <199808021018.GAA15812@hda.hda.com> Subject: Re: Using FreeBSD for data acquisition? (long) In-Reply-To: <199808012202.PAA26932@usr07.primenet.com> from Terry Lambert at "Aug 1, 98 10:02:49 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 2 Aug 1998 06:18:10 -0400 (EDT) Cc: dufault@hda.com, mike@smith.net.au, chanders@timing.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1 seconds is the round robin scheduling interval. It appears (.1 seconds obviously) > > the wakeup from the driver isn't preempting the current process, > > but waiting until the next roundrobin call. As far as I can tell, > > wakeup should preempt it. > > Kernel preemption is topologically equivalent to any other reason > for kernel reentrancy, from kernel threading to allowing all the > processors in an SMP system simultaneous entry. You're right - you may be in the kernel and obviously can't always preempt the process. But look at wakeup() in kern_synch: it does a need_resched, which is an AST to the context switching code in swtch.s. I thought this would happen as soon as the CPU is executing in user context, preempting the current process before the scheduling quantum expires. I'll read your missive later. However, from past experience, I know that you and I have fundamentally different opinions about the benefits of preallocation of resources (including CPU time) in tightly controlled and limited environments. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 03:57:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28083 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 03:57:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28049; Sun, 2 Aug 1998 03:57:19 -0700 (PDT) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id LAA00638; Sun, 2 Aug 1998 11:54:30 +0100 (BST) (envelope-from rjs) Date: Sun, 2 Aug 1998 11:54:30 +0100 (BST) From: Robert Swindells Message-Id: <199808021054.LAA00638@fdy2.demon.co.uk> To: se@FreeBSD.ORG CC: faber@isi.edu, fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: <19980801211533.D267@mi.uni-koeln.de> (message from Stefan Esser on Sat, 1 Aug 1998 21:15:33 +0200) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Questions about previous mod deleted] > Ted Faber wrote: >> On the other hand Robert Swindells's driver seems to attach the chip >> as a PCI device and work fine. If his modifications are small and >> acceptable, maybe the best plan is to incorporate them. If his mods >I'd like to understand what's different in that new >driver. The current driver worked well with the AMD >PCnet found on many motherboards, and IMHO we need >to make sure that the new driver supports the whole >range of Lance chips ... I haven't written a new driver, just made minor changes to the old one. The changes are: * Add probing support for the chip IDs for newer PCnet chips - 79c970A, 79c971 and 79c972. * Add support for reading and writing the BCR registers. Not currently used, but you need it to be able to add ifmedia support. * Modify pcnet_probe() to always return the chip type even if it is a PCI device. The probe routines that call this now check for the returned chip type when determining whether to attach it. Things not done: * No probe for 79c960A (PCnet-ISA II) * The chip ID for the 79c970 doesn't look right. It may be that the probe for this only worked because there was no distinction between "Unknown" and "PCI". I'll check into these two before doing a send-pr. The diffs are: --- if_lnc.h.orig Sun Jul 26 23:00:22 1998 +++ if_lnc.h Tue Jul 28 23:17:52 1998 @@ -41,8 +41,7 @@ #define PCNET_RDP 0x10 /* Register Data Port */ #define PCNET_RAP 0x12 /* Register Address Port */ #define PCNET_RESET 0x14 -#define PCNET_IDP 0x16 -#define PCNET_VSW 0x18 +#define PCNET_BDP 0x16 /* DEPCA port addresses */ #define DEPCA_IOSIZE 16 @@ -72,9 +71,12 @@ #define LANCE 1 /* Am7990 */ #define C_LANCE 2 /* Am79C90 */ #define PCnet_ISA 3 /* Am79C960 */ -#define PCnet_ISAplus 4 /* Am79C961 */ +#define PCnet_ISAplus 4 /* Am79C961 */ #define PCnet_32 5 /* Am79C965 */ #define PCnet_PCI 6 /* Am79C970 */ +#define PCnet_PCI_II 7 /* Am79C970A */ +#define PCnet_FAST 8 /* Am79C971 */ +#define PCnet_FASTplus 9 /* Am79C972 */ /* CSR88-89: Chip ID masks */ #define AMD_MASK 0x003 @@ -83,7 +85,9 @@ #define Am79C961 0x2260 #define Am79C965 0x2430 #define Am79C970 0x0242 -#define HITACHI_Am79C970 0x2621 +#define Am79C970A 0x2621 +#define Am79C971 0x2623 +#define Am79C972 0x2624 /* Board types */ #define UNKNOWN 0 --- if_lnc.c.orig Sun Jul 26 23:00:15 1998 +++ if_lnc.c Wed Jul 29 00:06:23 1998 @@ -122,6 +122,7 @@ int initialised; int rap; int rdp; + int bdp; #ifdef DEBUG int lnc_debug; #endif @@ -145,7 +146,10 @@ "PCnet-ISA", "PCnet-ISA+", "PCnet-32 VL-Bus", - "PCnet-PCI", /* "can't happen" */ + "PCnet-PCI", + "PCnet-PCI II", + "PCnet-FAST", + "PCnet-FAST+", }; #ifdef LNC_MULTICAST @@ -203,6 +207,20 @@ return (inw(sc->rdp)); } +static __inline void +write_bcr(struct lnc_softc *sc, u_short port, u_short val) +{ + outw(sc->rap, port); + outw(sc->bdp, val); +} + +static __inline u_short +read_bcr(struct lnc_softc *sc, u_short port) +{ + outw(sc->rap, port); + return (inw(sc->bdp)); +} + #ifdef LNC_MULTICAST static __inline u_long ether_crc(u_char *ether_addr) @@ -945,7 +963,8 @@ outw(iobase + CNET98S_RESET, tmp); DELAY(500); - if ((sc->nic.ic = pcnet_probe(sc)) == UNKNOWN) { + sc->nic.ic = pcnet_probe(sc); + if ((sc->nic.ic == UNKNOWN) || (sc->nic.ic > PCnet_32)) { return (0); } @@ -1000,7 +1019,8 @@ sc->rap = iobase + PCNET_RAP; sc->rdp = iobase + PCNET_RDP; - if ((sc->nic.ic = pcnet_probe(sc))) { + sc->nic.ic = pcnet_probe(sc); + if ((sc->nic.ic > 0) && (sc->nic.ic < PCnet_PCI)) { sc->nic.ident = NE2100; sc->nic.mem_mode = DMA_FIXED; @@ -1154,18 +1174,13 @@ case Am79C965: return (PCnet_32); case Am79C970: - /* - * do NOT try to ISA attach the PCI version - */ - return (0); - case HITACHI_Am79C970: - - /* - * PCI cards that should be attached in - * ISA mode should return this value. -- tvf - */ - - return (PCnet_PCI); + return (PCnet_PCI); + case Am79C970A: + return (PCnet_PCI_II); + case Am79C971: + return (PCnet_FAST); + case Am79C972: + return (PCnet_FASTplus); default: break; } @@ -1217,7 +1232,9 @@ */ if ((sc->nic.mem_mode != SHMEM) && (kvtop(sc->recv_ring) > 0x1000000)) { log(LOG_ERR, "lnc%d: Memory allocated above 16Mb limit\n", unit); - if (sc->nic.ic != PCnet_PCI) + if ((sc->nic.ic != PCnet_PCI) && + (sc->nic.ic != PCnet_PCI_II) && + (sc->nic.ic != PCnet_FAST)) return (0); } @@ -1278,8 +1295,7 @@ * and ether_ifattach() have been called in lnc_attach() ??? */ if ((sc->nic.mem_mode != SHMEM) && - (sc->nic.ic != PCnet_32) && - (sc->nic.ic != PCnet_PCI)) + (sc->nic.ic < PCnet_32)) isa_dmacascade(isa_dev->id_drq); #endif @@ -1290,22 +1306,35 @@ void * lnc_attach_ne2100_pci(int unit, unsigned iobase) { + int i; struct lnc_softc *sc = malloc(sizeof *sc, M_DEVBUF, M_NOWAIT); if (sc) { bzero (sc, sizeof *sc); - /* - * ne2100_probe sets sc->nic.ic to PCnet_PCI for PCI - * cards that work in ISA emulation mode. The first - * clause this code avoids attaching such a card at - * this time to allow it to be picked up as an ISA - * card later. -- tvf - */ + sc->rap = iobase + PCNET_RAP; + sc->rdp = iobase + PCNET_RDP; + sc->bdp = iobase + PCNET_BDP; + + sc->nic.ic = pcnet_probe(sc); + if (sc->nic.ic >= PCnet_PCI) { + sc->nic.ident = NE2100; + sc->nic.mem_mode = DMA_FIXED; - if (((ne2100_probe(sc, iobase) == 0) || - sc->nic.ic == PCnet_PCI) - || (lnc_attach_sc(sc, unit) == 0)) { + /* XXX - For now just use the defines */ + sc->nrdre = NRDRE; + sc->ntdre = NTDRE; + + /* Extract MAC address from PROM */ + for (i = 0; i < ETHER_ADDR_LEN; i++) + sc->arpcom.ac_enaddr[i] = inb(iobase + i); + + if (lnc_attach_sc(sc, unit) == 0) { + free(sc, M_DEVBUF); + sc = NULL; + } + } + else { free(sc, M_DEVBUF); sc = NULL; } @@ -1527,7 +1556,8 @@ * be missed. */ - outw(sc->rdp, IDON | CERR | BABL | MISS | MERR | RINT | TINT | INEA); + /*outw(sc->rdp, IDON | CERR | BABL | MISS | MERR | RINT | TINT | INEA);*/ + outw(sc->rdp, csr0); /* We don't do anything with the IDON flag */ @@ -1927,6 +1957,7 @@ ((sc->trans_ring + i)->md->md3 >> 10), TRANS_MD3); printf("\nnext_to_send = %x\n", sc->next_to_send); printf("\n CSR0 = %b CSR1 = %x CSR2 = %x CSR3 = %x\n\n", read_csr(sc, CSR0), CSR0_FLAGS, read_csr(sc, CSR1), read_csr(sc, CSR2), read_csr(sc, CSR3)); + /* Set RAP back to CSR0 */ outw(sc->rap, CSR0); } Robert Swindells ------------------------------------- Robert Swindells - GenRad Ltd rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 05:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06622 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 05:25:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ers.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA06617 for ; Sun, 2 Aug 1998 05:25:42 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from king (202.120.100.126) by ers.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Sun, 02 Aug 1998 20:16:53 +0800 From: "Paul King" To: "Alex Belits" Cc: Subject: Re: Can Infomix Run On FreeBSD - It Work! Date: Sun, 2 Aug 1998 20:19:22 +0800 Message-ID: <01bdbe0f$c7c1b6b0$6f01a8c0@king.ether.online.sh.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="hz-gb-2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I make Informix for Linux Version work under FreeBSD. But now I can not connect to localserver by namepipe, tcp socket connect work and Linux Emulater Report: LINUX: 'ioctl' fd=4, typ=0x89(e), num=0x2 not implemented I wonder what is ioctl(typ=0x89, num=0x2) in Linux, Is it serious? (I will try connect ODBC client to it) Thanks -----Original Message----- ~{7"<~HK~}: Alex Belits ~{JU<~HK~}: Paul King ~{3-KM~}: freebsd-hackers@FreeBSD.ORG ~{HUFZ~}: 1998~{Dj~}8~{TB~}2~{HU~} 16:38 ~{VwLb~}: Re: Can Infomix Run On FreeBSD > > >On Sun, 2 Aug 1998, Paul King wrote: > >> Informix had announced Linux Version of their database product, Can it run >> under FreeBSD? > > Considering that they claim it to be compiled from informix for solaris >sources cleanly, it should, but I haven't seen it, so I may be wrong. > >-- >Alex > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 05:48:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07927 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 05:48:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frida.mra.si ([193.2.116.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07922 for ; Sun, 2 Aug 1998 05:48:55 -0700 (PDT) (envelope-from brane@frida.mra.si) Received: from localhost (brane@localhost) by frida.mra.si (8.8.8/8.8.8) with SMTP id OAA06392 for ; Sun, 2 Aug 1998 14:50:27 +0200 (CEST) (envelope-from brane@frida.mra.si) Date: Sun, 2 Aug 1998 14:50:27 +0200 (CEST) From: Branko Kmetec To: hackers@FreeBSD.ORG Subject: ProLiant 2500 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to install FreeBSD 2.2.7 on Compaq ProLiant 2500, which has 1PPro 200 Mhz (upg. to 2PPros), 64 MB RAM and Compaq RAID SMART-2/P Controller with 3x2.1 GB drives configured as RAID5. There is also onboard SCSI with 4GB DAT. Currently this runs Windows NT 4.0 Server and we're using it as fileserver. Since I'm not satisfied with performance and stability, I want to get ridd off NTs. Since the only storage is RAID5 logical disk, is there any chance to install FreeBSD directly on RAID5 (customized boot.flp) or do we have to buy additional disk for installing through onboard SCSI (controller and tape are recognized by boot disk, so that shouldn't be a problem) and after that install SMART-2/P Controller with drives? Has anybody expirence with similar configuration? Branko Kmetec brane@mra.si To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 06:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09085 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 06:01:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA09080 for ; Sun, 2 Aug 1998 06:01:13 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 3478 invoked by uid 1001); 2 Aug 1998 13:01:05 +0000 (GMT) To: paulk@ether.online.sh.cn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can Infomix Run On FreeBSD - It Work! In-Reply-To: Your message of "Sun, 2 Aug 1998 20:19:22 +0800" References: <01bdbe0f$c7c1b6b0$6f01a8c0@king.ether.online.sh.cn> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 02 Aug 1998 15:01:05 +0200 Message-ID: <3476.902062865@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I make Informix for Linux Version work under FreeBSD. > > But now I can not connect to localserver by namepipe, tcp socket connect > work and Linux Emulater Report: > > LINUX: 'ioctl' fd=4, typ=0x89(e), num=0x2 not implemented > > I wonder what is ioctl(typ=0x89, num=0x2) in Linux, Is it serious? Looks like it is SIOCSPGRP. From Linux /usr/include/asm/sockios.h: #define SIOCSPGRP 0x8902 and this is indeed not emulated - at least not in 2.2.x. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 07:30:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16057 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 07:30:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ers.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA16051 for ; Sun, 2 Aug 1998 07:30:18 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from king (202.120.100.126) by ers.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Sun, 02 Aug 1998 22:22:45 +0800 From: "Paul King" To: "Branko Kmetec" , Subject: Re: ProLiant 2500 Date: Sun, 2 Aug 1998 22:25:00 +0800 Message-ID: <01bdbe21$54e73a40$6f01a8c0@king.ether.online.sh.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="hz-gb-2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can get boot floppy and kernel from : http://www.doc.ic.ac.uk/~md/ida/ Thanks to Mark Dawson for his driver. After install, you should rebuild new kernel to 2.2.7 2.2.7 announced that they support TLAN Network adapter for Compaq, But I can NOT found it in the source tree. The kernel will NOT work with the Comapq Network Adapter, u may get if_tl.c and if_tlreg.h from: http://freebsd.org/~wpaul modify /usr/src/sys/conf/file add: pci/if_tl.c optional tl device-driver and add: device tl0 in your kernel config file. Build your custom kernel. - Paul King -----Original Message----- >I would like to install FreeBSD 2.2.7 on Compaq ProLiant 2500, which has >1PPro 200 Mhz (upg. to 2PPros), 64 MB RAM and Compaq RAID SMART-2/P >Controller with 3x2.1 GB drives configured as RAID5. There is also onboard >SCSI with 4GB DAT. > >Currently this runs Windows NT 4.0 Server and we're using it as >fileserver. Since I'm not satisfied with performance and stability, I want >to get ridd off NTs. > >Since the only storage is RAID5 logical disk, is there any chance to >install FreeBSD directly on RAID5 (customized boot.flp) or do we have to >buy additional disk for installing through onboard SCSI (controller and >tape are recognized by boot disk, so that shouldn't be a problem) and >after that install SMART-2/P Controller with drives? > >Has anybody expirence with similar configuration? > >Branko Kmetec >brane@mra.si > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 08:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22108 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 08:49:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phobos.illtel.denver.co.us (phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22103 for ; Sun, 2 Aug 1998 08:49:02 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.8/8.6.9) with SMTP id IAA31108; Sun, 2 Aug 1998 08:50:10 -0700 Date: Sun, 2 Aug 1998 08:50:10 -0700 (PDT) From: Alex Belits To: Paul King cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can Infomix Run On FreeBSD - It Work! In-Reply-To: <01bdbe0f$c7c1b6b0$6f01a8c0@king.ether.online.sh.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, Paul King wrote: > I make Informix for Linux Version work under FreeBSD. > > But now I can not connect to localserver by namepipe, tcp socket connect > work and Linux Emulater Report: > > LINUX: 'ioctl' fd=4, typ=0x89(e), num=0x2 not implemented > > I wonder what is ioctl(typ=0x89, num=0x2) in Linux, Is it serious? It's SIOCSPGRP (behavior is equivalent in Linux FIOSETOWN). It enables sending the SIGURG signal on the arrival of urgent data on TCP socket. In FreeBSD SIOCSPGRP has different value and different behavior -- it also enables sending SIGIO while in Linux SIOCSPGRP seems to have no effect on it. I don't know which signals are actually used by Informix, you can check if it does anything for SIGIO or SIGURG by running strace on its startup -- if it changes signal handler before non-working ioctl is called, it probably is going to handle it somehow. -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 11:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06168 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 11:19:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06144 for ; Sun, 2 Aug 1998 11:19:33 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id NAA03846 for ; Sun, 2 Aug 1998 13:17:25 -0400 (EDT) Date: Sun, 2 Aug 1998 13:17:25 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-Hackers@FreeBSD.ORG Subject: SCSI disk deals? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If anyone happens to know of a particularly good deal on a 4G wide scsi disk, I'd appreciate you dropping me a line. Don't reply to the list, I think most everyone else might regard it as spam. Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 11:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08427 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 11:36:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08422 for ; Sun, 2 Aug 1998 11:36:38 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id OAA06940 for ; Sun, 2 Aug 1998 14:36:28 -0400 (EDT) Date: Sun, 2 Aug 1998 14:36:28 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Relationship between buf/page/vnode/object? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After studying VM source code for two months, I have understood the general ideas in it. All the pages (vm_page structures) belong to a object/pindex pair and virtual memory/physical memory is decoupled by introducing the VM object. What confuses me now is that vnode and buf structures can also have pages (vm_page structures) associated with them. But file system cache and VM cache are unified and should have a consistent interface. I mean all pages should only hang off the vm_object structures. I hope that someone can describe the relationship of these important structures (vm_object, vm_page, vnode, buf) briefly for me. I have searched the MailingList Archive in vain. Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 12:48:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14205 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 12:48:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles248.castles.com [208.214.165.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14185 for ; Sun, 2 Aug 1998 12:48:20 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA09419; Sun, 2 Aug 1998 12:47:29 -0700 (PDT) Message-Id: <199808021947.MAA09419@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jamie Howard cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI ZIP problems In-reply-to: Your message of "Sat, 01 Aug 1998 22:10:30 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Aug 1998 12:47:28 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just purchased a new system to run FreeBSD and I pulled the SCSI > ZIP drive (using the ZIP Zoom card) I had in my old system (a dual-boot > FreeBSD/Win95 system) and put it in there. The "Zip Zoom" (Adaptec 1505) card is not well supported, and the problems you're seeing are typical. The continuing lack of support is largely due to the poor performance of the card; supporting it is no fun and the card itself not terribly useful. You would be best off, at this point, to discard the Zoom card and consider the purchase of one of the better-supported, low-cost PCI SCSI controllers, eg. one based on the NCR/Symbios 83c810, which seem to sell for around US$60 or so. Alternatively, a second Adaptec 154x would be suitable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 12:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14492 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 12:50:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as2-p10.tfs.net [139.146.205.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14440 for ; Sun, 2 Aug 1998 12:50:03 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id OAA12025; Sun, 2 Aug 1998 14:49:30 -0500 (CDT) From: Jim Bryant Message-Id: <199808021949.OAA12025@unix.tfs.net> Subject: Re: SCSI disk deals? In-Reply-To: from Chuck Robey at "Aug 2, 98 01:17:25 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 2 Aug 1998 14:49:25 -0500 (CDT) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > If anyone happens to know of a particularly good deal on a 4G wide scsi > disk, I'd appreciate you dropping me a line. Don't reply to the list, I > think most everyone else might regard it as spam. > > Thanks. chuck, try this, good deals here... http://cayman.ebay2.com/aw/listings/list/category160/index.html jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 19:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12873 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 19:24:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12868 for ; Sun, 2 Aug 1998 19:24:09 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d86.syd2.zeta.org.au [203.26.11.86]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA27363 for ; Mon, 3 Aug 1998 12:23:57 +1000 Received: (qmail 19773 invoked by uid 1000); 3 Aug 1998 02:20:29 -0000 From: "Andrew Reilly" Message-ID: <19980803122028.A19751@reilly.home> Date: Mon, 3 Aug 1998 12:20:28 +1000 To: jgrosch@mooseriver.com, Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? References: <199808010637.OAA04884@ariadne.tensor.pgs.com> <19980802014204.A12287@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980802014204.A12287@mooseriver.com>; from Josef Grosch on Sun, Aug 02, 1998 at 01:42:04AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 02, 1998 at 01:42:04AM -0700, Josef Grosch wrote: > On Sat, Aug 01, 1998 at 02:37:58PM +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > >I'm part way through porting this company's seismic data processing code to > >FreeBSD and have got most things sorted out except for the fact that there > >doesn't seem to be any carefully optimised fft routines available. I do have > >the fftpack as found in ports, but I was wondering if there was anything > >faster than taht available with source. > > > >Oh, and if anyone knows where to find the source of X widgets that'll display > >seismic traces, power spectrums and the like, I'd be most grateful. > > > My father, a math and computer science professor, suggested "Numerical > Recipies", by Press, et al. No, Numerical Recipes is not even a little bit optimised, and although the Fortran version is OK, the C version is horrible, being a translitteration from the Fortran version, for the most part. The hackery to get Fortran-style offset-1 array indexing is particularly nasty. The other suggestions made here are all good sources of FFT code. Be aware that the fftw code has a particularly curly licence. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 20:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16264 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 20:00:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net ([209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA16258 for ; Sun, 2 Aug 1998 20:00:53 -0700 (PDT) (envelope-from david@sparks.net) From: david@sparks.net Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0z3ArW-0006N0-00; Sun, 2 Aug 1998 23:00:38 -0400 Date: Sun, 2 Aug 1998 23:00:38 -0400 (EDT) Reply-To: david@sparks.net To: freebsd-hackers@FreeBSD.ORG Subject: malloc question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From lurking on this list a long time, I think I understand that the 4.4bsd malloc will always attempt to grab the next higher power of two of memory. That would certainly fit with my observed behavior. I've an application which contains very little code (text), but a huge data area. Specifically, I want to be able to allocate 128 MB to an array and have a meg or two for code on my 160 MB system. But I get "can't allocate memory" errors on my 2.2.6R system. My login_class is root, and bash reports "unlimited" for shell datasize limits. vm.maxdsize, a possible problem on a bsdi system, doesn't seem to exist on FreeBSD. What am I missing? I must be able to run a 130 MB program on a 160 MB system:) Thanks, --- David ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 2 23:24:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03736 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 23:24:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03725 for ; Sun, 2 Aug 1998 23:24:03 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id IAA28142; Mon, 3 Aug 1998 08:20:55 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id IAA02241; Mon, 3 Aug 1998 08:15:11 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808030615.IAA02241@semyam.dinoco.de> To: david@sparks.net cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: malloc question In-reply-to: Your message of "Sun, 02 Aug 1998 23:00:38 EDT." Date: Mon, 03 Aug 1998 08:15:10 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > memory" errors on my 2.2.6R system. My login_class is root, and bash > reports "unlimited" for shell datasize limits. vm.maxdsize, a possible > problem on a bsdi system, doesn't seem to exist on FreeBSD. How about "max memory size" and "max virutal memory" that you can set, too? My /etc/login.conf (from -stable a few weeks ago) has one memory limit still set for root. vm.maxdsize sounds like the FreeBSD option MAXDFLSIZ which you can set in your kernel configuration. See LINT for an example. > What am I missing? I must be able to run a 130 MB program on a 160 MB > system:) Yeah, sure. The default constants for i386 systems seems to limit text size to 128 MByte, but if you really need that large programs you can increase that in your kernel configuration. :-) Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 00:21:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10144 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 00:21:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10138 for ; Mon, 3 Aug 1998 00:21:18 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id AAA16807; Mon, 3 Aug 1998 00:21:08 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980803002108.A16772@mooseriver.com> Date: Mon, 3 Aug 1998 00:21:08 -0700 From: Josef Grosch To: hackers@FreeBSD.ORG Subject: Quantum disk info needed. Reply-To: jgrosch@mooseriver.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently was given an old quantum disk, model xp34300w. Since Quantum's web page seems to be down (did'nt they go out of business?) does anybody have any information about these disk ? Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.8 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 01:25:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17682 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 01:25:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA17657 for ; Mon, 3 Aug 1998 01:25:47 -0700 (PDT) (envelope-from malte.lance@gmx.net) Received: from neuron.webmore.de (unverified [194.95.214.181]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 03 Aug 1998 10:26:49 +0200 Received: (from malte.lance@gmx.net) by neuron.webmore.de (8.8.8/8.8.8) id KAA00956; Mon, 3 Aug 1998 10:24:34 +0200 (CEST) From: Malte Lance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 3 Aug 1998 10:24:34 +0200 (CEST) To: "Andrew Reilly" Cc: jgrosch@mooseriver.com, Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? In-Reply-To: <19980803122028.A19751@reilly.home> References: <199808010637.OAA04884@ariadne.tensor.pgs.com> <19980802014204.A12287@mooseriver.com> <19980803122028.A19751@reilly.home> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13765.29346.857875.450309@neuron.webmore.de> Reply-To: malte.lance@gmx.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Reilly writes: > On Sun, Aug 02, 1998 at 01:42:04AM -0700, Josef Grosch wrote: > > On Sat, Aug 01, 1998 at 02:37:58PM +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > >I'm part way through porting this company's seismic data processing code to > > >FreeBSD and have got most things sorted out except for the fact that there > > >doesn't seem to be any carefully optimised fft routines available. I do have > > >the fftpack as found in ports, but I was wondering if there was anything > > >faster than taht available with source. > > > > > >Oh, and if anyone knows where to find the source of X widgets that'll display > > >seismic traces, power spectrums and the like, I'd be most grateful. > > > > > > My father, a math and computer science professor, suggested "Numerical > > Recipies", by Press, et al. > > No, Numerical Recipes is not even a little bit optimised, and > although the Fortran version is OK, the C version is horrible, > being a translitteration from the Fortran version, for the most > part. The hackery to get Fortran-style offset-1 array indexing is > particularly nasty. Had the same feelings abouot NR. More of an recipe "how to write a fft (... and introduce maximal confusion by strange indexing)". > > The other suggestions made here are all good sources of FFT code. > Be aware that the fftw code has a particularly curly licence. Hm ... what do you mean ? neuron:~/tmp10/fftw-1.3> cat ./COPYRIGHT /* * Copyright (c) 1997,1998 Massachusetts Institute of Technology * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ neuron:~/tmp10/fftw-1.3> The GPL-v2 is included in the file ./COPYING So what's your point ? Malte. > > -- > Andrew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 02:03:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22984 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 02:03:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from notabene.zer0.org (sac-port55.jps.net [209.63.114.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22967 for ; Mon, 3 Aug 1998 02:02:54 -0700 (PDT) (envelope-from gsutter@n1.dyn.ml.org) Received: (from gsutter@localhost) by notabene.zer0.org (8.8.7/8.8.8) id CAA10900; Mon, 3 Aug 1998 02:08:36 -0700 (PDT) (envelope-from gsutter) Message-ID: <19980803020831.A10732@notabene.zer0.org> Date: Mon, 3 Aug 1998 02:08:31 -0700 From: Gregory Sutter To: jgrosch@mooseriver.com, hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. References: <19980803002108.A16772@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980803002108.A16772@mooseriver.com>; from Josef Grosch on Mon, Aug 03, 1998 at 12:21:08AM -0700 Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 03, 1998 at 12:21:08AM -0700, Josef Grosch wrote: > > I recently was given an old quantum disk, model xp34300w. Since Quantum's > web page seems to be down (did'nt they go out of business?) does anybody > have any information about these disk ? Huh huh and huh? Quantum's web page is up, they're not out of business. The drive is an Atlas 4300MB Wide SCSI hard drive. It's not so old -- and it's a good, fast drive. If you don't want it, I'll take it. :) Some creative searching at Q's web site turned up this: Enjoy! Greg -- Gregory S. Sutter Bureaucrats cut red tape -- lengthwise. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 02:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28521 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 02:50:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28515 for ; Mon, 3 Aug 1998 02:50:23 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id JAA07188; Mon, 3 Aug 1998 09:52:38 GMT Date: Mon, 3 Aug 1998 10:52:38 +0100 (BST) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: Relationship between buf/page/vnode/object? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, zhihuizhang wrote: > > After studying VM source code for two months, I have understood the > general ideas in it. All the pages (vm_page structures) belong to a > object/pindex pair and virtual memory/physical memory is decoupled by > introducing the VM object. > > What confuses me now is that vnode and buf structures can also have pages > (vm_page structures) associated with them. But file system cache and VM > cache are unified and should have a consistent interface. I mean all pages > should only hang off the vm_object structures. > > I hope that someone can describe the relationship of these important > structures (vm_object, vm_page, vnode, buf) briefly for me. I have > searched the MailingList Archive in vain. > > Any help is appreciated. As far as I know, the pages which are held in buf structures are 'owned' by a unique vm_object. This object holds cached pages for a vnode and has an associated vnode_pager. The buf just provides a convenient way of performing 'regular' i/o into the same pages as those used for VM. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 03:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00403 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 03:07:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00394 for ; Mon, 3 Aug 1998 03:07:14 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id DAA22969; Mon, 3 Aug 1998 03:07:05 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd022955; Mon Aug 3 03:07:03 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id DAA07412; Mon, 3 Aug 1998 03:06:59 -0700 (MST) From: Terry Lambert Message-Id: <199808031006.DAA07412@usr09.primenet.com> Subject: Re: Fast FFT routines with source? To: malte.lance@gmx.net Date: Mon, 3 Aug 1998 10:06:59 +0000 (GMT) Cc: reilly@zeta.org.au, jgrosch@mooseriver.com, shocking@prth.pgs.com, hackers@FreeBSD.ORG In-Reply-To: <13765.29346.857875.450309@neuron.webmore.de> from "Malte Lance" at Aug 3, 98 10:24:34 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Be aware that the fftw code has a particularly curly licence. > > The GPL-v2 is included in the file ./COPYING > > So what's your point ? Unless you want to give away all your code, it'd be best to use different code. If you don't mind giving away all your code, then no problem. If it were LGPL instead, it would be less of an issue, so long as the code didn't need to go into the kernel, and you were willing to distribute everything else as .o files to meet the relink clause. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 03:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04274 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 03:44:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04261 for ; Mon, 3 Aug 1998 03:44:04 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d22.syd2.zeta.org.au [203.26.11.22]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id UAA28803 for ; Mon, 3 Aug 1998 20:43:53 +1000 Received: (qmail 21748 invoked by uid 1000); 3 Aug 1998 10:43:12 -0000 Message-ID: <19980803104312.21747.qmail@gurney.reilly.home> From: "Andrew Reilly" Date: Mon, 3 Aug 1998 20:43:11 +1000 (EST) Subject: Re: Fast FFT routines with source? To: tlambert@primenet.com cc: malte.lance@gmx.net, reilly@zeta.org.au, jgrosch@mooseriver.com, shocking@prth.pgs.com, hackers@FreeBSD.ORG In-Reply-To: <199808031006.DAA07412@usr09.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: >> > Be aware that the fftw code has a particularly curly licence. >> >> The GPL-v2 is included in the file ./COPYING >> >> So what's your point ? > > Unless you want to give away all your code, it'd be best to use > different code. > > If you don't mind giving away all your code, then no problem. > > If it were LGPL instead, it would be less of an issue, so long > as the code didn't need to go into the kernel, and you were > willing to distribute everything else as .o files to meet the > relink clause. It's not quite that bad, just not useful for BSD-style free software. The last time I read the doco they explained that they'd used this licence so that GPL's code could be written. Their intention was (is) to also offer a non-GPL'd version to those willing to pay a commercial licence fee. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 04:01:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06790 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 04:01:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06782 for ; Mon, 3 Aug 1998 04:01:47 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id HAA12632; Mon, 3 Aug 1998 07:01:35 -0400 (EDT) (envelope-from luoqi) Date: Mon, 3 Aug 1998 07:01:35 -0400 (EDT) From: Luoqi Chen Message-Id: <199808031101.HAA12632@lor.watermarkgroup.com> To: malte.lance@gmx.net, reilly@zeta.org.au Subject: Re: Fast FFT routines with source? Cc: hackers@FreeBSD.ORG, jgrosch@mooseriver.com, shocking@prth.pgs.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No, Numerical Recipes is not even a little bit optimised, and > > although the Fortran version is OK, the C version is horrible, > > being a translitteration from the Fortran version, for the most > > part. The hackery to get Fortran-style offset-1 array indexing is > > particularly nasty. > > Had the same feelings abouot NR. More of an recipe "how to write a > fft (... and introduce maximal confusion by strange indexing)". > Code samples (yes, they are samples, I never use them as they are) in NR are horrible, but no other book could beat NR on explaining how an algorithm works (have you read the FFT section in Sedgewick's Algorithms? Instead of explaining how *FFT* works, it tries to explain what are roots of unity, does that belong to a high school Algebra book?) -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 04:07:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07630 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 04:07:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07625 for ; Mon, 3 Aug 1998 04:07:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA06741; Mon, 3 Aug 1998 04:04:46 -0700 (PDT) Message-Id: <199808031104.EAA06741@implode.root.com> To: Doug Rabson cc: zhihuizhang , hackers Subject: Re: Relationship between buf/page/vnode/object? In-reply-to: Your message of "Mon, 03 Aug 1998 10:52:38 BST." From: David Greenman Reply-To: dg@root.com Date: Mon, 03 Aug 1998 04:04:46 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sun, 2 Aug 1998, zhihuizhang wrote: > >> >> After studying VM source code for two months, I have understood the >> general ideas in it. All the pages (vm_page structures) belong to a >> object/pindex pair and virtual memory/physical memory is decoupled by >> introducing the VM object. >> >> What confuses me now is that vnode and buf structures can also have pages >> (vm_page structures) associated with them. But file system cache and VM >> cache are unified and should have a consistent interface. I mean all pages >> should only hang off the vm_object structures. >> >> I hope that someone can describe the relationship of these important >> structures (vm_object, vm_page, vnode, buf) briefly for me. I have >> searched the MailingList Archive in vain. >> >> Any help is appreciated. > >As far as I know, the pages which are held in buf structures are 'owned' >by a unique vm_object. This object holds cached pages for a vnode and has >an associated vnode_pager. The buf just provides a convenient way of >performing 'regular' i/o into the same pages as those used for VM. That's mostly correct. Struct bufs are just kernel virtual mappings of vm_page's. Directories are handled differently, however - the system mallocs buffers for those, rather than whole pages, in order to be more space efficient. This isn't a problem since one can't mmap a directory. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 04:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11243 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 04:44:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fgwmail.fujitsu.co.jp (fgwmail.fujitsu.co.jp [164.71.1.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11202 for ; Mon, 3 Aug 1998 04:44:01 -0700 (PDT) (envelope-from seki@sysrap.cs.fujitsu.co.jp) Received: from fdmnews.fujitsu.co.jp by fgwmail.fujitsu.co.jp (8.8.8+2.7Wbeta7/3.6W-MX980716-Fujitsu Gateway) id UAA09923; Mon, 3 Aug 1998 20:43:51 +0900 (JST) Received: from nile.sysrap.cs.fujitsu.co.jp by fdmnews.fujitsu.co.jp (8.8.8+2.7Wbeta7/3.6W-980716-Fujitsu Domain Master) id UAA29465; Mon, 3 Aug 1998 20:43:50 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by nile.sysrap.cs.fujitsu.co.jp (8.8.8/8.7.3) with ESMTP id UAA06827 for ; Mon, 3 Aug 1998 20:43:49 +0900 (JST) To: freebsd-hackers@FreeBSD.ORG Subject: Issues on if_media X-Mailer: Mew version 1.91 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980803204349A.seki@sysrap.cs.fujitsu.co.jp> Date: Mon, 03 Aug 1998 20:43:49 +0900 From: Masahiro Sekiguchi X-Dispatcher: imput version 971024 Lines: 42 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm now working on adding if_media-based media selection into if_fe driver. The interface between Ehternet driver and if_media is, however, unclear for me. Could someone answer the following please? (1) Most of the media supported by if_fe compatible cards are half-duplex. Should I set the IFM_HDX bit when I register the supported media (with ifmedia_add)? My impression from if_media.h was "yes." However, I found ifconfig doesn't work well if I do so. Moreover, if_fxp, for example, does not set the bit for half-duplex media. If IFM_HDX should not be set for half-duplex media, for what purpose is this macro defined? (2) What point is the appropriate timing to call ifmedia_add()? In the current if_fe design, all hardware/board specific differences are detected in fe_probe() routine. So, I think it is best to call ifmedia_add() from fe_probe(). However, all driver supporting ifmedia calls it in attach() routines. Although I examined the if_media.c and found there is no problem calling the function from probe(), I'm not sure it is expected use of the interface, or just an accident. (3) More generally, how I can know the "definition" of the interface of if_media? I'm thinking about both on application interfaces (i.e., definition for SIOCGIFMEDIA/SIOCSIFMEDIA ioctl's) and on kernel interfaces (i.e., how to use ifmedia_add, ifmedia_set, etc.) (4) The if_fe driver currently supports a board named AT1700FT, which supports 10baseFL (10Mbps optic-fiber Ethernet). What value should I use for the Ehternet subtype for the media? Note that AT1700FT has two network connectors, one for 10baseFL and another for (usual) 10baseT, and it is possible to switch between those two with software-control... I think this is just a slip from the if_media.h and I should send-pr it... Is it correct? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 05:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15969 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 05:21:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15964 for ; Mon, 3 Aug 1998 05:21:38 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA03617; Mon, 3 Aug 1998 08:21:17 -0400 Date: Mon, 3 Aug 1998 08:21:16 -0400 (EDT) From: Jamie Bowden To: Josef Grosch cc: hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. In-Reply-To: <19980803002108.A16772@mooseriver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998, Josef Grosch wrote: > > I recently was given an old quantum disk, model xp34300w. Since Quantum's > web page seems to be down (did'nt they go out of business?) does anybody > have any information about these disk ? Micropolis is dead (took 'em long enough), but I haven't heard of any other drive manufacturer's getting bought or folding recently. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 05:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17572 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 05:34:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cbn.net.id (portland.cbn.net.id [202.158.3.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA17554 for ; Mon, 3 Aug 1998 05:34:13 -0700 (PDT) (envelope-from masli@cbn.net.id) Received: (qmail 29258 invoked from network); 3 Aug 1998 12:43:40 -0000 Received: from unknown (HELO default) (202.158.20.1) by portland.cbn.net.id with SMTP; 3 Aug 1998 12:43:40 -0000 Message-ID: <32034775.2B7D@cbn.net.id> Date: Sat, 03 Aug 1996 19:35:01 +0700 From: masli Reply-To: masli@cbn.net.id Organization: PT.Playbackboy X-Mailer: Mozilla 3.01C-KIT (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hallo i have question what is i'am downloads to make FreeBSD work's i don't know what can i do to downloads ,what files and what directory Thank You masli@cbn.net.id To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 06:22:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23617 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 06:22:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA23611 for ; Mon, 3 Aug 1998 06:22:12 -0700 (PDT) (envelope-from malte.lance@gmx.net) Received: from neuron.webmore.de (unverified [194.95.214.177]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 03 Aug 1998 15:23:25 +0200 Received: (from malte.lance@gmx.net) by neuron.webmore.de (8.8.8/8.8.8) id PAA04096; Mon, 3 Aug 1998 15:08:11 +0200 (CEST) From: Malte Lance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 3 Aug 1998 15:08:11 +0200 (CEST) To: Luoqi Chen Cc: reilly@zeta.org.au, hackers@FreeBSD.ORG, jgrosch@mooseriver.com, shocking@prth.pgs.com Subject: Re: Fast FFT routines with source? In-Reply-To: <199808031101.HAA12632@lor.watermarkgroup.com> References: <199808031101.HAA12632@lor.watermarkgroup.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13765.46057.61247.598795@neuron.webmore.de> Reply-To: malte.lance@gmx.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen writes: > > > No, Numerical Recipes is not even a little bit optimised, and > > > although the Fortran version is OK, the C version is horrible, > > > being a translitteration from the Fortran version, for the most > > > part. The hackery to get Fortran-style offset-1 array indexing is > > > particularly nasty. > > > > Had the same feelings abouot NR. More of an recipe "how to write a > > fft (... and introduce maximal confusion by strange indexing)". > > > Code samples (yes, they are samples, I never use them as they are) in NR > are horrible, but no other book could beat NR on explaining how an > algorithm works (have you read the FFT section in Sedgewick's Algorithms? > Instead of explaining how *FFT* works, it tries to explain what are > roots of unity, does that belong to a high school Algebra book?) Don't know about US-highschools. To know "how FFT works", you have to know what this nasty numbers in the frequency-domain stand for and where they come from. Also you need to know why you are able to reuse intermediary calculation-results (bit-reversion/reordering). The answers to this questions are easy, when you have knowledge about unit-roots and exponentials. Unit-roots and exponentials are really not that hard, that they shouldn't be explained in a basic-level analysis or algebra book. Malte. > > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 07:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29558 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 07:14:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29535 for ; Mon, 3 Aug 1998 07:14:26 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA08273; Mon, 3 Aug 1998 16:08:20 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id MAA09805; Mon, 3 Aug 1998 12:25:49 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808031025.MAA09805@semyam.dinoco.de> To: zhihuizhang Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Relationship between buf/page/vnode/object? In-reply-to: Your message of "Sun, 02 Aug 1998 14:36:28 EDT." Date: Mon, 03 Aug 1998 12:25:48 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What confuses me now is that vnode and buf structures can also have pages > (vm_page structures) associated with them. But file system cache and VM > cache are unified and should have a consistent interface. I mean all pages > should only hang off the vm_object structures. Right. I didn't look at this code till yesterday. Taking a deep look at vnode_pager.c and today a bit more on vfs_subr.c and vfs_vnops.c I think I have an idea how this all works. > I hope that someone can describe the relationship of these important > structures (vm_object, vm_page, vnode, buf) briefly for me. I have If someone is seeing an error here please correct me: As I understand it the vnode of a regular file gets a pointer to an associated vm_object on open (in vfs_vnops.c in kern the actual open happens) and this is the same vm_object for the same file opened several times at the same time. With this vm_object the pages for the buffers of this vnode get managed. This vm_object is of type OBJT_VNODE and thus uses the functions in vnode_pager.c for page manipulation. A buf has pointers to vm_page structures which have the memory pages associated with the buffer and a pointer to its vnode. Manipulating them means using the operations in vm_pager.c (which for OBJT_VNODE call the functions in vnode_pager.c) with the vm_object in the vnode. If you mmap a file vm_mmap.c contains the code used. It looks as if it were allocating a new object every time you map a file but this is not what actually happens. The object allocating that finally gets called is the one in vnode_pager.c and is named vnode_pager_alloc. If the vnode it gets already has an object it just increments the use count for the object. Thus the vnode of a regular file has an associated vm_object (which is the same as long as at least one reference to this vnode exists) and every time you reference the file you do it with its vnode. It doesn't matter if it is a read() or a mmap(), all references to it go through the vnode's vm_object and use the functions in vnode_pager.c. I hope it got a bit clearer by this how the whole thing works. And I also hope that I don't wrote too much nonsense - I just started reading about this in the code yesterday night. ;-) Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 08:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11690 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 08:43:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11665 for ; Mon, 3 Aug 1998 08:43:23 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id IAA18819; Mon, 3 Aug 1998 08:43:02 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980803084302.B18781@mooseriver.com> Date: Mon, 3 Aug 1998 08:43:02 -0700 From: Josef Grosch To: Jamie Bowden Cc: hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. Reply-To: jgrosch@mooseriver.com References: <19980803002108.A16772@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Jamie Bowden on Mon, Aug 03, 1998 at 08:21:16AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 03, 1998 at 08:21:16AM -0400, Jamie Bowden wrote: >On Mon, 3 Aug 1998, Josef Grosch wrote: > >> >> I recently was given an old quantum disk, model xp34300w. Since Quantum's >> web page seems to be down (did'nt they go out of business?) does anybody >> have any information about these disk ? > >Micropolis is dead (took 'em long enough), but I haven't heard of any >other drive manufacturer's getting bought or folding recently. OK, I was seriously confused there for a few. Thanks Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.8 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 09:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14196 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 09:02:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14146; Mon, 3 Aug 1998 09:02:32 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id RAA14265 Mon, 3 Aug 1998 17:02:13 +0100 (BST) Message-ID: <35C5DEC4.BF4EF1D4@cs.strath.ac.uk> Date: Mon, 03 Aug 1998 17:01:08 +0100 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG CC: roger@cs.strath.ac.uk Subject: Kernel Threads. What is the status? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering what the status of Kernel Threads is. Is it a) On the wish list, but not started yet. b) Under casual development c) Under serious development I want to make maximum use of my dual PII box for image processing. I've used fork() and shared memory to share the processing over the 2 CPUs. I would like to use POSIX Pthreads. Linux has kernel threads and their Pthreads run over multiple CPUs. What is the state of FreeBSD? Thanks Roger Hardiman, Strathclyde Uni Telepresence Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 09:19:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18122 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 09:19:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18105 for ; Mon, 3 Aug 1998 09:19:18 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA01234; Mon, 3 Aug 1998 10:13:33 -0600 (MDT) Date: Mon, 3 Aug 1998 10:13:33 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808031613.KAA01234@narnia.plutotech.com> To: Masahiro Sekiguchi cc: hackers@FreeBSD.ORG Subject: Re: Issues on if_media Newsgroups: pluto.freebsd.hackers In-Reply-To: <19980803204349A.seki@sysrap.cs.fujitsu.co.jp> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980803204349A.seki@sysrap.cs.fujitsu.co.jp> you wrote: > (4) The if_fe driver currently supports a board named AT1700FT, which > supports 10baseFL (10Mbps optic-fiber Ethernet). What value > should I use for the Ehternet subtype for the media? > > Note that AT1700FT has two network connectors, one for 10baseFL > and another for (usual) 10baseT, and it is possible to switch > between those two with software-control... > > I think this is just a slip from the if_media.h and I should > send-pr it... Is it correct? I don't know about your other questions (I haven't used the ifmedia interfaces yet), but Jason Thorpe just added a definition for 10baseFL to NetBSD, and we should use the same definition. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 09:47:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22756 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 09:47:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22724 for ; Mon, 3 Aug 1998 09:47:14 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id LAA07590; Mon, 3 Aug 1998 11:43:04 -0400 (EDT) Date: Mon, 3 Aug 1998 11:43:02 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Josef Grosch cc: Jamie Bowden , hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. In-Reply-To: <19980803084302.B18781@mooseriver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998, Josef Grosch wrote: > On Mon, Aug 03, 1998 at 08:21:16AM -0400, Jamie Bowden wrote: > >On Mon, 3 Aug 1998, Josef Grosch wrote: > > > >> > >> I recently was given an old quantum disk, model xp34300w. Since Quantum's > >> web page seems to be down (did'nt they go out of business?) does anybody > >> have any information about these disk ? > > > >Micropolis is dead (took 'em long enough), but I haven't heard of any > >other drive manufacturer's getting bought or folding recently. > > OK, I was seriously confused there for a few. No, not really, because they were bought by Seagate, so it was reasonable to expect what you did. Quantum's site is still there, tho, and that's good, because Seagate's site has no old Quantum info on it. Last night I got data from the Quantum site on an old 105S, which is quite more aged than yours. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 09:47:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22760 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 09:47:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22714; Mon, 3 Aug 1998 09:47:08 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id SAA06870; Mon, 3 Aug 1998 18:46:13 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id SAA00330; Mon, 3 Aug 1998 18:46:04 +0200 (CEST) X-Face: " Date: Mon, 3 Aug 1998 18:46:04 +0200 From: Stefan Esser To: Chris Csanady , Terry Lambert Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: pci_map_mem() failing.. Mail-Followup-To: Chris Csanady , Terry Lambert , hackers@FreeBSD.ORG References: <199807282224.PAA20070@usr04.primenet.com> <199807290045.RAA14001@tarsier.ca.sandia.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807290045.RAA14001@tarsier.ca.sandia.gov>; from Chris Csanady on Tue, Jul 28, 1998 at 05:45:44PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-28 17:45 -0700, Chris Csanady wrote: > Actually, I had a typo and once the above check was fixed, it now works. > A diff for the 2.2 branch follows. This is not entirely correct, but > should work. I understand this to mean, that you got the attach to work when that consistency check is removed ? > if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M > && (paddr & ~0xfffff) == 0) > ! && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT > ! && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_64BIT){ > printf ("pci_map_mem failed: bad memory type=0x%x\n", > (unsigned) data); > return (0); Could you please try the following patch, which will just make sure that the high 32 bit of the map register are 0. This is trivially true, today (or the BIOS was very broken, but with x86 systems supporting 64 bit PCI address spaces becoming available, a system might map some card to an address beyond 4GB, and the -stable PCI code (and all the PCI device drivers ;-) won't be able to deal with a card whose address doesn't fit into 32 bit ... If this patch works for you (sorry, I can't build a 2.2.x kernel myself), then I'll commit that patch to -stable. Regards, STefan Index: /sys_22/pci/pci.c =================================================================== RCS file: /usr/cvs/src/sys/pci/pci.c,v retrieving revision 1.57.2.9 diff -u -2 -r1.57.2.9 pci.c --- pci.c 1998/07/07 05:24:23 1.57.2.9 +++ pci.c 1998/08/03 16:43:38 @@ -1086,5 +1086,12 @@ */ - if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M + if ((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_64BIT) { + unsigned upperhalf = pci_conf_read (tag, reg + 4); + if (upperhalf != 0) { + printf ("pci_map_mem failed: 0x%08x%08x > 4GB\n", + upperhalf, paddr); + return (0); + } + } else if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M && (paddr & ~0xfffff) == 0) && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT){ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 10:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03568 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 10:30:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shasta.wstein.com (shasta.wstein.com [206.163.206.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03561 for ; Mon, 3 Aug 1998 10:30:57 -0700 (PDT) (envelope-from joes@shasta.wstein.com) Received: (from joes@localhost) by shasta.wstein.com (8.9.0/8.9.0) id KAA13119 for hackers@freebsd.org; Mon, 3 Aug 1998 10:30:44 -0700 (PDT) From: Joseph Stein Message-Id: <199808031730.KAA13119@shasta.wstein.com> Subject: User Quotas To: hackers@FreeBSD.ORG Date: Mon, 3 Aug 1998 10:30:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see numerous references (Handbook, The Complete FreeBSD, etc) to the fact that quotas are "buggy" and should be used only sparingly. To what extent are quotas "buggy", what are the bugs, and are there any plans to correct them? Where do I look if I want to tinker? (Obviously, the source code, but where are they implemented?) joe -- Joseph Stein; Beaverton, Oregon USA email: joes@wstein.com Finger joes@shasta.wstein.com for contact information and PGP Public Key! Oregon FirePage http://www.ofp.org [OFP-504] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 10:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04988 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 10:39:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA04938 for ; Mon, 3 Aug 1998 10:38:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 14820 invoked by uid 1001); 3 Aug 1998 17:38:31 +0000 (GMT) To: chuckr@glue.umd.edu Cc: hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. In-Reply-To: Your message of "Mon, 3 Aug 1998 11:43:02 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 03 Aug 1998 19:38:31 +0200 Message-ID: <14818.902165911@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, not really, because they were bought by Seagate, so it was > reasonable to expect what you did. Quantum's site is still there, tho, > and that's good, because Seagate's site has no old Quantum info on it. Um, you're still confused. *Conner* was bought by Seagate, not Quantum. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 10:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07416 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 10:55:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-05.ix.netcom.com [206.214.137.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07388 for ; Mon, 3 Aug 1998 10:55:05 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id KAA00908; Mon, 3 Aug 1998 10:54:52 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Aug 1998 10:54:52 -0700 (PDT) Message-Id: <199808031754.KAA00908@ix.netcom.com> From: Thomas Dean To: freebsd-hackers@FreeBSD.ORG Subject: Problems Restarting xdm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For David Dawes: The XFree86 readme suggests starting xdm from /etc/ttys. The FreeBSD FAQ suggests starting xdm from rc.local. Either way, if there is, for example, a power glitch reboot, xdm will not start without root intervention. I believe this is because the pid file exists. The xdm pid file is /usr/X11R6/lib/X11/xdm/xdm-pid. Should the pid file be in /var/run? Should it be cleaned-up at boot time? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 11:24:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11556 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 11:24:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11549 for ; Mon, 3 Aug 1998 11:24:15 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id NAA07880; Mon, 3 Aug 1998 13:20:43 -0400 (EDT) Date: Mon, 3 Aug 1998 13:20:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: sbabkin@dcn.att.com cc: jgrosch@mooseriver.com, jamie@itribe.net, hackers@FreeBSD.ORG Subject: RE: Quantum disk info needed. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998 sbabkin@dcn.att.com wrote: > > -----Original Message----- > > From: Chuck Robey [SMTP:chuckr@glue.umd.edu] > > > > No, not really, because they were bought by Seagate, so it was > > reasonable to expect what you did. Quantum's site is still there, > > tho, > > and that's good, because Seagate's site has no old Quantum info on it. > > > Oops. Are they going to keep Quantum as a whole or have it melt > into Seagate ? I was wrong on that, it wasn't Quantum I was thinking about, it was Conner. Actually I thought both had been swallowed, but it wasn't true about Quantum. > > -Sergey > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16863 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:02:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16851 for ; Mon, 3 Aug 1998 12:02:15 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA28556; Mon, 3 Aug 1998 12:01:58 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd028477; Mon Aug 3 12:01:51 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA00238; Mon, 3 Aug 1998 12:01:45 -0700 (MST) From: Terry Lambert Message-Id: <199808031901.MAA00238@usr07.primenet.com> Subject: Re: Fast FFT routines with source? To: reilly@zeta.org.au (Andrew Reilly) Date: Mon, 3 Aug 1998 19:01:45 +0000 (GMT) Cc: tlambert@primenet.com, malte.lance@gmx.net, reilly@zeta.org.au, jgrosch@mooseriver.com, shocking@prth.pgs.com, hackers@FreeBSD.ORG In-Reply-To: <19980803104312.21747.qmail@gurney.reilly.home> from "Andrew Reilly" at Aug 3, 98 08:43:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not quite that bad, just not useful for BSD-style free software. > The last time I read the doco they explained that they'd used this > licence so that GPL's code could be written. Their intention was (is) > to also offer a non-GPL'd version to those willing to pay a commercial > licence fee. In general, manufacturing processes are trade secrets. For a trade secret, you can't use a source available license and expect to keep the secret. That's one of the intents of a source available license: to allow those who disagree with it to effectively rewrite Article I, section 12 of the US Constitution. Note that fixes contributed back under the terms of that license are also covered under the terms of that license; that is, as derivative works, they contaminate the authorship of the code. Only if you explicitly go out of your way to refuse contributions to the software rather than to you do you, as the orginal author, retain rights to relicense the combined code. Tim Wilkerson has done precisely this with Kaffe, which is nominally under GPL. If this is the type of control you want, then a Sun/Java style license is the best way to achieve it (ie: JavaSoft, NPL, etc.); the failure of the Sun License was that it was not granted in perpetuity, which allwed Sun to shoot themselves in the foot in an attempt to capitalize on it, destroying the availability of the reference implementation. The history of TCP/IP shows us why a public reference implementation is necessary. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17851 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:07:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17842 for ; Mon, 3 Aug 1998 12:07:40 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig1.att.att.com by cagw1.att.com (AT&T/UPAS) for freebsd.org!hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Mon Aug 3 14:06 EDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id OAA19191 for ; Mon, 3 Aug 1998 14:14:06 -0400 (EDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Mon, 3 Aug 1998 14:13:56 -0400 Message-ID: To: chuckr@glue.umd.edu, jgrosch@mooseriver.com Cc: jamie@itribe.net, hackers@FreeBSD.ORG Subject: RE: Quantum disk info needed. Date: Mon, 3 Aug 1998 14:13:53 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Chuck Robey [SMTP:chuckr@glue.umd.edu] > > No, not really, because they were bought by Seagate, so it was > reasonable to expect what you did. Quantum's site is still there, > tho, > and that's good, because Seagate's site has no old Quantum info on it. > Oops. Are they going to keep Quantum as a whole or have it melt into Seagate ? -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18370 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:09:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18357 for ; Mon, 3 Aug 1998 12:09:34 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id MAA13724; Mon, 3 Aug 1998 12:09:18 -0700 (PDT) Message-ID: <19980803120918.A8109@Alameda.net> Date: Mon, 3 Aug 1998 12:09:18 -0700 From: Ulf Zimmermann To: Chuck Robey , Josef Grosch Cc: Jamie Bowden , hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. Reply-To: ulf@Alameda.net References: <19980803084302.B18781@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Chuck Robey on Mon, Aug 03, 1998 at 11:43:02AM -0400 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 03, 1998 at 11:43:02AM -0400, Chuck Robey wrote: > > On Mon, 3 Aug 1998, Josef Grosch wrote: > > > On Mon, Aug 03, 1998 at 08:21:16AM -0400, Jamie Bowden wrote: > > >On Mon, 3 Aug 1998, Josef Grosch wrote: > > > > > >> > > >> I recently was given an old quantum disk, model xp34300w. Since Quantum's > > >> web page seems to be down (did'nt they go out of business?) does anybody > > >> have any information about these disk ? > > > > > >Micropolis is dead (took 'em long enough), but I haven't heard of any > > >other drive manufacturer's getting bought or folding recently. > > > > OK, I was seriously confused there for a few. > > No, not really, because they were bought by Seagate, so it was > reasonable to expect what you did. Quantum's site is still there, tho, > and that's good, because Seagate's site has no old Quantum info on it. Haeh ? When has Seagate bought Quantum ? Seagate bought Connor as the last Harddisk company I know off. > > Last night I got data from the Quantum site on an old 105S, which is > quite more aged than yours. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:15:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19809 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:15:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19751 for ; Mon, 3 Aug 1998 12:15:34 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA21780; Mon, 3 Aug 1998 12:14:56 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd021700; Mon Aug 3 12:14:48 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA00830; Mon, 3 Aug 1998 12:14:42 -0700 (MST) From: Terry Lambert Message-Id: <199808031914.MAA00830@usr07.primenet.com> Subject: Re: Fast FFT routines with source? To: malte.lance@gmx.net Date: Mon, 3 Aug 1998 19:14:42 +0000 (GMT) Cc: luoqi@watermarkgroup.com, reilly@zeta.org.au, hackers@FreeBSD.ORG, jgrosch@mooseriver.com, shocking@prth.pgs.com In-Reply-To: <13765.46057.61247.598795@neuron.webmore.de> from "Malte Lance" at Aug 3, 98 03:08:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Code samples (yes, they are samples, I never use them as they are) in NR > > are horrible, but no other book could beat NR on explaining how an > > algorithm works (have you read the FFT section in Sedgewick's Algorithms? > > Instead of explaining how *FFT* works, it tries to explain what are > > roots of unity, does that belong to a high school Algebra book?) > > Don't know about US-highschools. > > To know "how FFT works", you have to know what this nasty > numbers in the frequency-domain stand for and where they come > from. Also you need to know why you are able to reuse > intermediary calculation-results (bit-reversion/reordering). > The answers to this questions are easy, when you have knowledge > about unit-roots and exponentials. Unit-roots and exponentials > are really not that hard, that they shouldn't be explained in a > basic-level analysis or algebra book. I have to agree here. It's no use having a hammer if you don't know how it works. You don't necessarily have to know why it works, of course, unless you are concerned with being the most efficient carpenter you can be. I consistently find Sedgewick's book useful; despite the title, it has very little direct relationship to C++ (or any other implementation language). In particular, if you ever want to know "what's Terry on about?" when I talk about "Hamiltonian Cycles" and "Warshal's Algorithm" and "O(3) Algorithms for Transitive Closure" and "Directed Acyclic Graph", this is the book to read. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:16:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19978 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:16:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19930; Mon, 3 Aug 1998 12:16:20 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id VAA15983; Mon, 3 Aug 1998 21:15:36 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id VAA01493; Mon, 3 Aug 1998 21:12:26 +0200 (CEST) X-Face: " Date: Mon, 3 Aug 1998 21:12:26 +0200 From: Stefan Esser To: Mike Smith , Jamie Howard Cc: freebsd-hackers@FreeBSD.ORG, Stefan Esser Subject: Re: SCSI ZIP problems Mail-Followup-To: Mike Smith , Jamie Howard , freebsd-hackers@FreeBSD.ORG References: <199808021947.MAA09419@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808021947.MAA09419@antipodes.cdrom.com>; from Mike Smith on Sun, Aug 02, 1998 at 12:47:28PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-02 12:47 -0700, Mike Smith wrote: > You would be best off, at this point, to discard the Zoom card and > consider the purchase of one of the better-supported, low-cost PCI > SCSI controllers, eg. one based on the NCR/Symbios 83c810, which seem 53c810 (minor nit ;-) > to sell for around US$60 or so. Alternatively, a second Adaptec 154x > would be suitable. Actually, the Symbios SYM28010 should be no more than US$35 ... It is the most cost-effective SCSI card you'll find, even with an external SCSI connector ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:21:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20917 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:21:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20881 for ; Mon, 3 Aug 1998 12:21:14 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA23779; Mon, 3 Aug 1998 12:20:59 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd023747; Mon Aug 3 12:20:53 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA01206; Mon, 3 Aug 1998 12:20:51 -0700 (MST) From: Terry Lambert Message-Id: <199808031920.MAA01206@usr07.primenet.com> Subject: Re: User Quotas To: joes@shasta.wstein.com (Joseph Stein) Date: Mon, 3 Aug 1998 19:20:51 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199808031730.KAA13119@shasta.wstein.com> from "Joseph Stein" at Aug 3, 98 10:30:43 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see numerous references (Handbook, The Complete FreeBSD, etc) to the > fact that quotas are "buggy" and should be used only sparingly. > > To what extent are quotas "buggy", what are the bugs, and are there any > plans to correct them? If the quota file is not on the FS to which the quotas are applied and/or there is a user/group quota that applies to the quota file, then you can deadlock. To avoid this, you should use one of the "cookbooks" for correct quota setup that have been posted to -current or -hackers over the years. Do not expect quotas to work properly over NFS; the lease management code does not enforce distributed cache coherency correcly because of missing assertions (see other discussions of NFS). You can get around this by forcing the use of NFSv2, which effectively disables thes (and many other) optimizations. > Where do I look if I want to tinker? (Obviously, the source code, but > where are they implemented?) Ideally, you would tinker with VFS stacking. The best way to implement quotas is to implement them as a stacking layer, so that they can apply to all FS's. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 12:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24535 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 12:37:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24507 for ; Mon, 3 Aug 1998 12:37:36 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id PAA16971 for ; Mon, 3 Aug 1998 15:37:53 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 3 Aug 1998 15:37:53 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: hackers@FreeBSD.ORG Subject: really need help with installation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm still having problems doing an install, i installed PICO bsd and heavily modified it to support an installation with a 905b card. (added cpio, fdisk, disklabel....) now what i do is this: boot PICObsd, ftp sysinstall over from my machine (same build) because sysinstall is too large to be compiled into the boot floppy. anyhow everything seems to work, but sysinstall can't find my Disks for some reason, i've read through the source... and like urm i'm confused as hell as to why sysinstall can't see my disks, but fdisk and disklabel CAN.... i practically have all my options from a kernel that has no problems in the PICObsd kernel. practically by now i could have done "make release" unfortunatly i thought i could 'fenangle' my way out of doing it with some creative ideas... (btw, the whole point of me doing this is to be able to install on a machine with a 905b, the xl driver) also i thought it would be a neat excersize... hehhe, maybe not ;) -Alfred, -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] There are operating systems, and then there's BSD. http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 13:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05315 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 13:45:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05273 for ; Mon, 3 Aug 1998 13:45:07 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id WAA15710; Mon, 3 Aug 1998 22:44:54 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id WAA15534; Mon, 3 Aug 1998 22:44:54 +0200 (MET DST) Date: Mon, 3 Aug 1998 22:44:54 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199808032044.WAA15534@surf.IAE.nl> To: joes@shasta.wstein.com Subject: Re: User Quotas X-Newsgroups: list.freebsd.hackers In-Reply-To: <199808031730.KAA13119@shasta.wstein.com> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808031730.KAA13119@shasta.wstein.com> you write: >I see numerous references (Handbook, The Complete FreeBSD, etc) to the >fact that quotas are "buggy" and should be used only sparingly. > >To what extent are quotas "buggy", what are the bugs, and are there any >plans to correct them? We are running quota on a server for ~10.000 uid, since ages as far as I can remember. We're not doing anything extreme, but have not yet run into any problems --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 13:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05815 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 13:48:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05747 for ; Mon, 3 Aug 1998 13:48:24 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA13961; Mon, 3 Aug 1998 13:45:18 -0700 (PDT) Message-Id: <199808032045.NAA13961@implode.root.com> To: Stefan Eggers cc: zhihuizhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Relationship between buf/page/vnode/object? In-reply-to: Your message of "Mon, 03 Aug 1998 12:25:48 +0200." <199808031025.MAA09805@semyam.dinoco.de> From: David Greenman Reply-To: dg@root.com Date: Mon, 03 Aug 1998 13:45:18 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Thus the vnode of a regular file has an associated vm_object (which is >the same as long as at least one reference to this vnode exists) and >every time you reference the file you do it with its vnode. It >doesn't matter if it is a read() or a mmap(), all references to it go >through the vnode's vm_object and use the functions in vnode_pager.c. > >I hope it got a bit clearer by this how the whole thing works. And I >also hope that I don't wrote too much nonsense - I just started >reading about this in the code yesterday night. ;-) Correct. We continue to use struct bufs because we still need to map the file pages into the kernel virtual address space (for copyin/copyout), and struct bufs are convenient for that. It was also easiest to keep this abstraction in the filesystem code; it minimized the amount of change that was necessary, made it fairly easy to port things like soft-updates, and has other benefits as well such as controlling the amount of delayed-write data to a reasonable level. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 14:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09480 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 14:10:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA09454 for ; Mon, 3 Aug 1998 14:10:31 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3Rs3-0006Kh-00; Mon, 3 Aug 1998 15:10:19 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id PAA04556; Mon, 3 Aug 1998 15:11:07 -0600 (MDT) Message-Id: <199808032111.PAA04556@harmony.village.org> To: Mike Smith Subject: Re: SCSI ZIP problems Cc: Jamie Howard , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Aug 1998 12:47:28 PDT." <199808021947.MAA09419@antipodes.cdrom.com> References: <199808021947.MAA09419@antipodes.cdrom.com> Date: Mon, 03 Aug 1998 15:11:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808021947.MAA09419@antipodes.cdrom.com> Mike Smith writes: : The "Zip Zoom" (Adaptec 1505) card is not well supported, and the : problems you're seeing are typical. The continuing lack of support is : largely due to the poor performance of the card; supporting it is no : fun and the card itself not terribly useful. The aic-6x60 support is really bad right now. There are many problems with using it, except possibly with the pcmcia based cards. I've given up hope of having a good driver for this in the near term, and unless something radical changes, I don't think that there will be a good CAM driver in place when the CAM cutover happens. There are many PIO vs DMA issues as well that could make things interesting. Someone stepping forward to prove me wrong would be great :-). I have programming information for the aic-6360, but I have too many other things on my plate to even think about getting to it for a few months. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 15:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20738 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 15:15:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20729 for ; Mon, 3 Aug 1998 15:15:01 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA93 for ; Mon, 3 Aug 1998 16:15:52 -0600 Received: (from chanders@localhost) by count.timing.com (8.8.7/8.8.7) id QAA02199 for freebsd-hackers@FreeBSD.ORG; Mon, 3 Aug 1998 16:14:41 -0600 (MDT) (envelope-from chanders) Date: Mon, 3 Aug 1998 16:14:41 -0600 (MDT) From: chanders@timing.com (Craig Anderson) Message-Id: <199808032214.QAA02199@count.timing.com> To: freebsd-hackers@FreeBSD.ORG Subject: Device driver synchronization with spl? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like an explanation of how the spl functions are used to sychronize a driver that uses interrupts. Code fragments from a driver I'm working on are at the end of the messages. The interrupt handler is installed on irq 11. Here are my assumptions (guesses) so far. 1) gt401read() calls splgt401() to add a mask for irq 11. 2) After splgt401() the interrupt function gt401intr will not run. This prevents a wakeup being lost between checking the data count and sleeping for data to show up. 3) The tsleep() causes another process to run with an interrupt mask that will allow gt401intr() to run. 4) irq 11 happens and the handler gt401intr() is run. 5) gt401intr() updates the data count and issues the wakeup. 6) gt401read() returns from the tsleep() and sees that there is now data. Some questions. 1) Is my understanding of the spl usage good enough? 2) If this is correct, what should splgt401() look like? My guess here, after looking at /usr/src/sys/i386/include/spl.h is GENSPL(splbio, cpl |= some_mask) where some_mask is appropriate for irq11. If this is right what should some_mask be? driver code fragments --------------------- static int gt401read (dev_t dev, struct uio* uio, int flag) { ... s = splgt401(); while (gt401Unit[0].rbuf_count == 0) { status = tsleep(gt401Unit[0].sleep_address, PRIBIO | PCATCH, "gt401", i_timeout); if (!((status == 0) || (status == EWOULDBLOCK))) { splx(s); return(status); } } splx(s); void gt401intr(int unit) { ... ++gt401Unit[0].rbuf_count; ... wakeup (gt401Unit[0].sleep_address); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 15:59:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25370 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 15:59:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25365 for ; Mon, 3 Aug 1998 15:59:03 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA16514; Mon, 3 Aug 1998 17:58:37 -0500 (EST) (envelope-from toor) Message-Id: <199808032258.RAA16514@dyson.iquest.net> Subject: Re: Relationship between buf/page/vnode/object? In-Reply-To: from Doug Rabson at "Aug 3, 98 10:52:38 am" To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 3 Aug 1998 17:58:36 -0500 (EST) Cc: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson said: > On Sun, 2 Aug 1998, zhihuizhang wrote: > > > > > After studying VM source code for two months, I have understood the > > general ideas in it. All the pages (vm_page structures) belong to a > > object/pindex pair and virtual memory/physical memory is decoupled by > > introducing the VM object. > > > > What confuses me now is that vnode and buf structures can also have pages > > (vm_page structures) associated with them. But file system cache and VM > > cache are unified and should have a consistent interface. I mean all pages > > should only hang off the vm_object structures. > > > > I hope that someone can describe the relationship of these important > > structures (vm_object, vm_page, vnode, buf) briefly for me. I have > > searched the MailingList Archive in vain. > > > > Any help is appreciated. > > As far as I know, the pages which are held in buf structures are 'owned' > by a unique vm_object. This object holds cached pages for a vnode and has > an associated vnode_pager. The buf just provides a convenient way of > performing 'regular' i/o into the same pages as those used for VM. > The buffers are both temporary mappings, and a low water mark on the amount of buffer space available. Note that the current implemenation of the VM/buffer cache code also limits the amount of dirty buffer space to the size of the buffer cache (actually less than that.) Almost all caching is done in the VM objects, and buffers (for file data) are mappings into the objects. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 16:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29007 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 16:23:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29000 for ; Mon, 3 Aug 1998 16:23:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01662; Mon, 3 Aug 1998 16:22:07 -0700 (PDT) Message-Id: <199808032322.QAA01662@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: chanders@timing.com (Craig Anderson) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device driver synchronization with spl? In-reply-to: Your message of "Mon, 03 Aug 1998 16:14:41 MDT." <199808032214.QAA02199@count.timing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 16:22:06 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I would like an explanation of how the spl functions are used to > sychronize a driver that uses interrupts. Code fragments from a > driver I'm working on are at the end of the messages. The interrupt > handler is installed on irq 11. 'man 9 spl' on a -current system contains a fairly succinct answer. > Here are my assumptions (guesses) so far. > > 1) gt401read() calls splgt401() to add a mask for irq 11. No. I don't believe that creating new spl's is trivial anymore. In the first instance, I would simply add the 'tty' keyword to your device's ISA configuration entry (see eg. the 'sio' entries for examples). > 2) After splgt401() the interrupt function gt401intr will not run. > This prevents a wakeup being lost between checking the data count > and sleeping for data to show up. Not exactly. After spltty(), should an interrupt masked by the 'tty' mask occur, it will be remembered, and when the mask is cleared the interrupt handler will be run. > 3) The tsleep() causes another process to run with an interrupt > mask that will allow gt401intr() to run. A call to tsleep() will put the current process to sleep, preserving the current interrupt mask. When a new process is selected to run, the mask is set to that for the new process. > 4) irq 11 happens and the handler gt401intr() is run. Yes, although the interrupt may have happened during the peroid when the interrupt was masked. > 5) gt401intr() updates the data count and issues the wakeup. ... and returns. The woken process won't actually run until the interrupt handler has returned. > 6) gt401read() returns from the tsleep() and sees that there is now data. It should check to see if there is data; it may have been woken for other reasons (timeout, signal delivery, etc.). > > Some questions. > 1) Is my understanding of the spl usage good enough? Geting there. 8) > 2) If this is correct, what should splgt401() look like? Don't complicate things yet; stick with spltty(). > My guess here, after looking at /usr/src/sys/i386/include/spl.h is > GENSPL(splbio, cpl |= some_mask) > where some_mask is appropriate for irq11. If this is right what should > some_mask be? spl.h has been obsoleted in -current, you can find it in i386/isa/ ipl_funcs.c. Implementing a private interrupt mask is probably not a useful thing to do, as it's more work that necessary. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 16:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02464 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 16:57:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02457 for ; Mon, 3 Aug 1998 16:57:23 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA89; Mon, 3 Aug 1998 17:58:32 -0600 Received: from count.timing.com (localhost.timing.com [127.0.0.1]) by count.timing.com (8.8.7/8.8.7) with ESMTP id RAA02513; Mon, 3 Aug 1998 17:56:39 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199808032356.RAA02513@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device driver synchronization with spl? In-reply-to: Your message of "Mon, 03 Aug 1998 16:22:06 PDT." <199808032322.QAA01662@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 17:56:39 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, I did not see man spl(9) yet. Another question. The driver is not configured it installed as an LKM. Is spltty() still appropriate? Help again! > > > > I would like an explanation of how the spl functions are used to > > sychronize a driver that uses interrupts. Code fragments from a > > driver I'm working on are at the end of the messages. The interrupt > > handler is installed on irq 11. > > 'man 9 spl' on a -current system contains a fairly succinct answer. > > > Here are my assumptions (guesses) so far. > > > > 1) gt401read() calls splgt401() to add a mask for irq 11. > > No. I don't believe that creating new spl's is trivial anymore. In > the first instance, I would simply add the 'tty' keyword to your > device's ISA configuration entry (see eg. the 'sio' entries for > examples). > > > 2) After splgt401() the interrupt function gt401intr will not run. > > This prevents a wakeup being lost between checking the data count > > and sleeping for data to show up. > > Not exactly. After spltty(), should an interrupt masked by the 'tty' > mask occur, it will be remembered, and when the mask is cleared the > interrupt handler will be run. > > > 3) The tsleep() causes another process to run with an interrupt > > mask that will allow gt401intr() to run. > > A call to tsleep() will put the current process to sleep, preserving > the current interrupt mask. When a new process is selected to run, the > mask is set to that for the new process. > > > 4) irq 11 happens and the handler gt401intr() is run. > > Yes, although the interrupt may have happened during the peroid when > the interrupt was masked. > > > 5) gt401intr() updates the data count and issues the wakeup. > > ... and returns. The woken process won't actually run until the > interrupt handler has returned. > > > 6) gt401read() returns from the tsleep() and sees that there is now data. > > It should check to see if there is data; it may have been woken for > other reasons (timeout, signal delivery, etc.). > > > > > Some questions. > > 1) Is my understanding of the spl usage good enough? > > Geting there. 8) > > > 2) If this is correct, what should splgt401() look like? > > Don't complicate things yet; stick with spltty(). > > > My guess here, after looking at /usr/src/sys/i386/include/spl.h is > > GENSPL(splbio, cpl |= some_mask) > > where some_mask is appropriate for irq11. If this is right what should > > some_mask be? > > spl.h has been obsoleted in -current, you can find it in i386/isa/ > ipl_funcs.c. Implementing a private interrupt mask is probably not a > useful thing to do, as it's more work that necessary. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 18:48:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12515 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 18:48:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12510 for ; Mon, 3 Aug 1998 18:48:42 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA24861; Tue, 4 Aug 1998 11:48:28 +1000 (EST) Message-ID: <19980804114828.C24600@rf900.physics.usyd.edu.au> Date: Tue, 4 Aug 1998 11:48:28 +1000 From: David Dawes To: Thomas Dean , freebsd-hackers@FreeBSD.ORG Subject: Re: Problems Restarting xdm Mail-Followup-To: Thomas Dean , freebsd-hackers@FreeBSD.ORG References: <199808031754.KAA00908@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808031754.KAA00908@ix.netcom.com>; from Thomas Dean on Mon, Aug 03, 1998 at 10:54:52AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 03, 1998 at 10:54:52AM -0700, Thomas Dean wrote: >The XFree86 readme suggests starting xdm from /etc/ttys. The FreeBSD >FAQ suggests starting xdm from rc.local. Either way, if there is, for I've never liked the idea of starting it from /etc/ttys. I start it from a script in /usr/X11R6/etc/rc.d. >example, a power glitch reboot, xdm will not start without root >intervention. I believe this is because the pid file exists. > >The xdm pid file is /usr/X11R6/lib/X11/xdm/xdm-pid. Should the pid >file be in /var/run? Should it be cleaned-up at boot time? I use my own xdm-config file which does specify that the pid file goes in /var/run. If booting without removing it is a problem, you should remove it before starting xdm at boot time. I've never noticed such a problem myself. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 19:11:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14648 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 19:11:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14642 for ; Mon, 3 Aug 1998 19:11:13 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA02226 for ; Tue, 4 Aug 1998 11:41:02 +0930 (CST) Message-Id: <199808040211.LAA02226@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Threaded X libs.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 11:41:02 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was trying to port a program which required thread safe X libs, so I recompiled XFree86 after editing the config file for FreeBS, and it seemed to work fine (OK, so I didn't exactly test it, but at least XInitThreads() now works :) Is there any reason why the FreeBSD version of XFree86 doesn't enable threads by default? Perhaps the port could have an option for it? (I can make a patch for the port to do so if it would be useful :) Also is there any chance that the thread cancellation routines will be implented any time soon? :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 20:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20086 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 20:12:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20079 for ; Mon, 3 Aug 1998 20:12:49 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id NAA25268; Tue, 4 Aug 1998 13:12:36 +1000 (EST) Message-ID: <19980804131236.L24600@rf900.physics.usyd.edu.au> Date: Tue, 4 Aug 1998 13:12:36 +1000 From: David Dawes To: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. Mail-Followup-To: Daniel O'Connor , hackers@FreeBSD.ORG References: <199808040211.LAA02226@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808040211.LAA02226@cain.gsoft.com.au>; from Daniel O'Connor on Tue, Aug 04, 1998 at 11:41:02AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 11:41:02AM +0930, Daniel O'Connor wrote: >Hi, >I was trying to port a program which required thread safe X libs, so I >recompiled XFree86 after editing the config file for FreeBS, and it seemed to >work fine (OK, so I didn't exactly test it, but at least XInitThreads() now >works :) > >Is there any reason why the FreeBSD version of XFree86 doesn't enable threads >by default? Perhaps the port could have an option for it? (I can make a patch >for the port to do so if it would be useful :) Only because nobody who is interested in it has tested it and told us (XFree86) that it works (until now?). If it does all seem to work, send me a patch with any changes (even if only config changes), and I'll add it to the XFree86 development code. Make sure that the config changes only enable it for FreeBSD versions where it will work. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 20:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20256 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 20:15:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa6-11.ix.netcom.com [206.214.137.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20244 for ; Mon, 3 Aug 1998 20:14:57 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id UAA00388; Mon, 3 Aug 1998 20:14:36 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Aug 1998 20:14:36 -0700 (PDT) Message-Id: <199808040314.UAA00388@ix.netcom.com> From: Thomas Dean To: dawes@rf900.physics.usyd.edu.au CC: freebsd-hackers@FreeBSD.ORG In-reply-to: <19980804114828.C24600@rf900.physics.usyd.edu.au> (message from David Dawes on Tue, 4 Aug 1998 11:48:28 +1000) Subject: Re: Problems Restarting xdm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Booting with xdm-pid existing causes xdm to not start. Cleaning-up xdm-pid in my (obsolete) /etc/rc.local and then starting xdm resolves the problem. I guess one of these days I wll change over to rc.d. But, rc.local works... I should have read more about xdm before talking about the log file. I did read the man page, but, not looking for the log file location. It is a good man page. I see quite a few questions about starting xdm. I think the difference between the FreeBSD FAQ and the XFree86 README confuses some people. Thanks for the reply tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 3 23:21:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06819 for freebsd-hackers-outgoing; Mon, 3 Aug 1998 23:21:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06811 for ; Mon, 3 Aug 1998 23:21:41 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id IAA15496 for ; Tue, 4 Aug 1998 08:21:20 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id IAA06382 for ; Tue, 4 Aug 1998 08:21:21 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id IAA19675 for ; Tue, 4 Aug 1998 08:21:22 +0200 (CEST) Received: from server.us.tld(192.168.16.33) via SMTP by curry.mchp.siemens.de, id smtpdE19673; Tue Aug 4 08:21:17 1998 Received: (from daemon@localhost) by server.us.tld (8.8.8/8.8.8) id IAA04259 for ; Tue, 4 Aug 1998 08:21:17 +0200 (CEST) (envelope-from andre@bali.us.tld) Received: from bali.us.tld(192.168.21.100) via SMTP by server.us.tld, id smtpdNs4120; Tue Aug 4 08:21:16 1998 Received: (from andre@localhost) by bali.us.tld (8.8.8/8.8.8) id IAA01758; Tue, 4 Aug 1998 08:21:15 +0200 (CEST) (envelope-from andre) From: Andre Albsmeier Message-Id: <199808040621.IAA01758@bali.us.tld> Subject: Re: User Quotas In-Reply-To: <199808031920.MAA01206@usr07.primenet.com> from Terry Lambert at "Aug 3, 98 07:20:51 pm" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 4 Aug 1998 08:21:15 +0200 (CEST) Cc: joes@shasta.wstein.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I see numerous references (Handbook, The Complete FreeBSD, etc) to the > > fact that quotas are "buggy" and should be used only sparingly. > > > > To what extent are quotas "buggy", what are the bugs, and are there any > > plans to correct them? > > If the quota file is not on the FS to which the quotas are applied > and/or there is a user/group quota that applies to the quota file, > then you can deadlock. > > To avoid this, you should use one of the "cookbooks" for correct > quota setup that have been posted to -current or -hackers over > the years. > > Do not expect quotas to work properly over NFS; the lease management > code does not enforce distributed cache coherency correcly because > of missing assertions (see other discussions of NFS). You can get > around this by forcing the use of NFSv2, which effectively disables > thes (and many other) optimizations. > > > > Where do I look if I want to tinker? (Obviously, the source code, but > > where are they implemented?) > > Ideally, you would tinker with VFS stacking. The best way to > implement quotas is to implement them as a stacking layer, so that > they can apply to all FS's. And: Never use quotas with extremly large (or negative) UIDs. The quota system is unusable if large UIDs are used because the quota.user file is an array of structures where the index represents the UID and the structure is 32 byte. When using UID 4294967294 (-2) as PCNFS with user nobody does it, you can imagine the theorethical size of quota.user. See also PR 2325. But, apart of that, quotas work great here (using a 18GB drive). -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 00:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12862 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 00:47:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12843; Tue, 4 Aug 1998 00:47:19 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA00627; Tue, 4 Aug 1998 09:47:03 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 09:47:02 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Etherlink XL driver Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 09:47:02 +0200 Message-ID: Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA12845 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Etherlink XL driver seems to be working fine. How about committing it to -current and removing the XL probe/attach code from the vx driver? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 00:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14368 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 00:56:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from casimir.easynet.fr (casimir.easynet.fr [195.114.64.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14360; Tue, 4 Aug 1998 00:56:13 -0700 (PDT) (envelope-from rama@casimir.easynet.fr) Received: (from rama@localhost) by casimir.easynet.fr (8.8.8/8.8.8) id JAA10008; Tue, 4 Aug 1998 09:56:04 +0200 (CEST) (envelope-from rama) Message-ID: <19980804095604.B9991@easynet.fr> Date: Tue, 4 Aug 1998 09:56:04 +0200 From: David Ramahefason To: freebsd-atm@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Uni 4.0 support ?? Reply-To: David Ramahefason Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8 Organization: Systems Team Easynet France SA X-Operating-System: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to know if ther is a Uni 4.0 support for ATM under FreeBSD... What a re the best card to run an ATM box under FreeBSD ? Thanks -- /David Ramahefason Administrateur Systeme/Reseau/ /rama@easynet.fr Easynet France SA / /0144547031 ICQ: 14292822 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 01:21:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16095 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 01:21:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16079; Tue, 4 Aug 1998 01:21:22 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA05252; Tue, 4 Aug 1998 10:26:00 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 4 Aug 1998 10:25:59 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: David Ramahefason cc: freebsd-atm@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Uni 4.0 support ?? In-Reply-To: <19980804095604.B9991@easynet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, David Ramahefason wrote: > Hi, > > I'd like to know if ther is a Uni 4.0 support for > ATM under FreeBSD... You may want to check the HARP (Host ATM Research Platform) package, which runs quite well on FreeBSD 2.2.x. It supports UNI3.0, but full sources are available, so that you can rewrite the signalling manager to include UNI3.1 and 4.0 messages. HARP also supports SPANS (Fore proprietary signalling) if you use the Fore card (I'm not sure I can recommend it, though... ;-) Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 01:22:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16294 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 01:22:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16275; Tue, 4 Aug 1998 01:22:51 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id MAA12778; Tue, 4 Aug 1998 12:22:34 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id MAA12251; Tue, 4 Aug 1998 12:22:54 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199808040822.MAA12251@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: hackers@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: What does it mean? X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Tue, 04 Aug 1998 12:22:53 +0400 From: Alex Povolotsky Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Some time ago, squid on my FreeBSD asteroid.svib.ru 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Tue Feb 24 12:34:41 MSK 1998 root@asteroid.svib.ru:/data/src/sys/compile/ASTEROID i386 box stopped responding. ps tells me that ps axlw | grep squid 0 12762 12654 1 -6 0 952 636 piperd S+ p0 0:00.01 grep squid 65534 328 316 0 -22 0 17392 10076 vmpfw D con- 12:35.05 squid -sY what does it mean? Who/whot/how deadlocked squid? It is in D state, and immunet even to kill -9 :-( Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 01:24:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16756 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 01:24:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16661 for ; Tue, 4 Aug 1998 01:24:01 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id KAA15152; Tue, 4 Aug 1998 10:23:33 +0200 (MET DST) Date: Tue, 4 Aug 1998 10:23:31 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: dag-erli@ifi.uio.no, FreeBSD hackers mailing list Subject: Re: Etherlink XL driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Etherlink XL driver seems to be working fine. How about committing > it to -current and removing the XL probe/attach code from the vx > driver? I vote in favour of that. We are goign to use that ethernet card heavily within the next month, so if it is broken (and it isn't we made sure of that :-) we'll see the problem... Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 01:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18544 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 01:40:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nighthawk.iti.gov.sg (nighthawk.iti.gov.sg [192.122.131.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA18539; Tue, 4 Aug 1998 01:40:52 -0700 (PDT) (envelope-from joerg@krdl.org.sg) Received: (from mailer@localhost) by nighthawk.iti.gov.sg (8.6.11/8.6.11) id QAA23546; Tue, 4 Aug 1998 16:52:12 +0800 Received: from mailhub.iti.gov.sg(192.122.132.132) by nighthawk.iti.gov.sg via smap (V1.3) id sma023539; Tue Aug 4 16:51:48 1998 Received: (from joerg@localhost) by iti.gov.sg (8.8.8/8.8.5) id QAA12377; Tue, 4 Aug 1998 16:32:01 +0800 (SGT) Message-ID: <19980804163201.54879@krdl.org.sg> Date: Tue, 4 Aug 1998 16:32:01 +0800 From: Joerg Micheel To: Andrzej Bialecki Cc: David Ramahefason , freebsd-atm@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, brandt@fokus.gmd.de Subject: Re: Uni 4.0 support ?? References: <19980804095604.B9991@easynet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Andrzej Bialecki on Tue, Aug 04, 1998 at 10:25:59AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej, On Tue, Aug 04, 1998 at 10:25:59AM +0200, Andrzej Bialecki wrote: > On Tue, 4 Aug 1998, David Ramahefason wrote: > > I'd like to know if ther is a Uni 4.0 support for > > ATM under FreeBSD... > > You may want to check the HARP (Host ATM Research Platform) package, which > runs quite well on FreeBSD 2.2.x. It supports UNI3.0, but full sources are > available, so that you can rewrite the signalling manager to include > UNI3.1 and 4.0 messages. HARP also supports SPANS (Fore proprietary > signalling) if you use the Fore card (I'm not sure I can recommend it, > though... ;-) Yes, HARP might do the job, and UNI 3.0 is not that far from UNI 3.1, thats correct. However, the difference between Q.SAAL and SSCOP is significant, it seems rather like an implementation from scratch. Joerg -- Joerg B. Micheel Email: SingAREN Technology Center Phone: +65 7705577 Kent Ridge Digital Labs (pron: curdle) Fax: +65 7795966 11 Science Park Road Pager: +65 96016020 Singapore Science Park II Plan: Troubleshooting ATM 117685 Singapore Networks and Applications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 04:14:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06107 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 04:14:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA06082 for ; Tue, 4 Aug 1998 04:14:51 -0700 (PDT) (envelope-from malte.lance@gmx.net) Received: from neuron.webmore.de (unverified [194.95.214.165]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Tue, 04 Aug 1998 13:16:29 +0200 Received: (from malte.lance@gmx.net) by neuron.webmore.de (8.8.8/8.8.8) id KAA01056; Tue, 4 Aug 1998 10:30:14 +0200 (CEST) From: Malte Lance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 Aug 1998 10:30:14 +0200 (CEST) To: Thomas Dean Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems Restarting xdm In-Reply-To: <199808031754.KAA00908@ix.netcom.com> References: <199808031754.KAA00908@ix.netcom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13766.50765.170940.775527@neuron.webmore.de> Reply-To: malte.lance@gmx.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean writes: > For David Dawes: > > The XFree86 readme suggests starting xdm from /etc/ttys. The FreeBSD > FAQ suggests starting xdm from rc.local. Either way, if there is, for > example, a power glitch reboot, xdm will not start without root > intervention. I believe this is because the pid file exists. Do you clean up /tmp on bootup ? If not, maybe /tmp/.X-lock bites you after "power glitch reboot". Malte. > > The xdm pid file is /usr/X11R6/lib/X11/xdm/xdm-pid. Should the pid > file be in /var/run? Should it be cleaned-up at boot time? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 04:37:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09037 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 04:37:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09032 for ; Tue, 4 Aug 1998 04:37:25 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA23611; Tue, 4 Aug 1998 13:37:10 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 13:37:10 +0200 (MET DST) Mime-Version: 1.0 To: jgrosch@mooseriver.com Cc: hackers@FreeBSD.ORG Subject: Re: Quantum disk info needed. References: <19980803002108.A16772@mooseriver.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 13:37:09 +0200 In-Reply-To: Josef Grosch's message of "Mon, 3 Aug 1998 00:21:08 -0700" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA09033 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Grosch writes: > I recently was given an old quantum disk, model xp34300w. Since Quantum's > web page seems to be down (did'nt they go out of business?) does anybody > have any information about these disk ? Very simple: XP means Quantum, 3 means 41 mm tall, 4300 means 4300 million bytes (not megabytes), and W means SCSI Wide interface. Seagate uses the same numbering scheme (with ST instead of XP); Conner (which now belongs to Seagate) used a similar scheme, but encoded drive height as a letter IIRC (ISTR P meant 25 mm, but I might be totally off the track here). I've never cared too much about WD, Maxtor, Micropolis (now defunct) or IBM (which are the only other large disk manufacturers I can think of). ISTR Seagate has a web page that explains how to read model numbers; it's quite possible that Quantum has one too. DES (who has an XP34550W, and wouldn't call an XP34300W "old") -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 04:54:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11429 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 04:54:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11422 for ; Tue, 4 Aug 1998 04:54:47 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA25379; Tue, 4 Aug 1998 13:54:35 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 13:54:35 +0200 (MET DST) Mime-Version: 1.0 To: Thomas Dean Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems Restarting xdm References: <199808031754.KAA00908@ix.netcom.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 13:54:34 +0200 In-Reply-To: Thomas Dean's message of "Mon, 3 Aug 1998 10:54:52 -0700 (PDT)" Message-ID: Lines: 25 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA11425 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean writes: > The XFree86 readme suggests starting xdm from /etc/ttys. The FreeBSD > FAQ suggests starting xdm from rc.local. Either way, if there is, for > example, a power glitch reboot, xdm will not start without root > intervention. I believe this is because the pid file exists. Eh? IANAL, but I don't think the existence of a pid file has anything to do with this. If you bothered to read your logs, you'd soon find out that the X server is complaining about a lock file (/tmp/.X0-lock) which was left behind by the previous server if it didn't exit cleanly (as would happen in the case of a power glitch). This, and whether xdm should be started from /etc/ttys or /etc/rc*, has been discussed ad nauseam on this and other lists, as you'd know if you'd searched the archives before posting. Anyway, the location of the pid file is determined by the xdm-config file, which is part of the XFree86 distribution and therefore Not Our Cup Of Tea (tm). I doubt you'd have any luck convincing the XFree86 people to ship a different X*cfg.tgz just for FreeBSD. /usr/X11R6/lib/X11/xdm/xdm-errors is your friend. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 04:55:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11650 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 04:55:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kutepov.usm.uni-muenchen.de (Kutepov.usm.uni-muenchen.de [129.187.204.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11635 for ; Tue, 4 Aug 1998 04:55:41 -0700 (PDT) (envelope-from shadow@leontief.ru) Received: from leontief.ru ([194.247.129.33]) by Kutepov.usm.uni-muenchen.de (8.8.5/8.8.5) with ESMTP id NAA25464 for ; Tue, 4 Aug 1998 13:56:04 +0200 Received: (from mail@localhost) by leontief.ru (8.8.5/8.7.3) id PAA14808 for ; Tue, 4 Aug 1998 15:56:35 +0400 (MSD) X-Authentication-Warning: leontief.ru: mail set sender to using -f Received: from ppp10.pu.ru(194.85.123.10) by leontief.ru via smap (V1.3) id sma014806; Tue Aug 4 15:56:28 1998 Message-ID: <35C6F664.DFA7DFA3@leontief.ru> Date: Tue, 04 Aug 1998 15:54:13 +0400 From: "Daniel W. Samsyguin" X-Mailer: Mozilla 4.5b1 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: vm86 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Where can I foun tech info 'bout vm86 in FreeBSD and differences with Linux vm86? Another times, I spended a lot of time to find vm86 in 2.2.5 porting netbsd dosemu 8) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 06:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20872 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 06:03:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20856 for ; Tue, 4 Aug 1998 06:03:01 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id GAA00974; Tue, 4 Aug 1998 06:50:36 -0600 (MDT) Message-Id: <199808041250.GAA00974@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 06:50:15 -0600 To: hackers@FreeBSD.ORG From: Brett Glass Subject: 2.2.7 crash during "monthly" maintenance batch Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This morning, a server we upgraded to 2.2.7 crashed at 5:30 AM during its "monthly" maintenance batch (the default one that comes with it). We can't tell why, since we were asleep (admins do sleep sometimes) but we're worried about this.... This is the second time the system has spontaneously fallen apart in the two days after the upgrade. What might be wrong? Are other people seeing this? We're not running anything unusual enough to cause problems. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 06:13:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22756 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 06:13:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA22739 for ; Tue, 4 Aug 1998 06:13:08 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA19967; Tue, 4 Aug 1998 09:11:31 -0400 Date: Tue, 4 Aug 1998 09:11:31 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Craig Anderson cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device driver synchronization with spl? In-Reply-To: <199808032214.QAA02199@count.timing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know completely on your use of spl, but ... if you can find and use smp-style locks you will be happier in the long run. ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 06:35:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26111 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 06:35:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26103 for ; Tue, 4 Aug 1998 06:35:05 -0700 (PDT) (envelope-from kaleb@ics.com) Received: from ics.com (kaleb@teapot.ics.com [140.186.40.160]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA15350; Tue, 4 Aug 1998 09:34:35 -0400 (EDT) Message-ID: <35C70CB0.4592DCB7@ics.com> Date: Tue, 04 Aug 1998 13:29:20 +0000 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.31 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. References: <199808040211.LAA02226@cain.gsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > Hi, > I was trying to port a program which required thread safe X libs, so I > recompiled XFree86 after editing the config file for FreeBS, and it seemed to > work fine (OK, so I didn't exactly test it, but at least XInitThreads() now > works :) > > Is there any reason why the FreeBSD version of XFree86 doesn't enable threads > by default? Perhaps the port could have an option for it? (I can make a patch > for the port to do so if it would be useful :) When there's an officially released version of FreeBSD with threads, then I'm sure the default will be to enable threads in XFree86. The last time I tried building with threads, on some 3.0SNAP version, things didn't work very well (and I haven't spent any time trying to figure out why.) > > Also is there any chance that the thread cancellation routines will be > implented any time soon? :) In Xlib or in libc? -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:06:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01712 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:06:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01642; Tue, 4 Aug 1998 07:06:06 -0700 (PDT) (envelope-from salo@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA19333; Tue, 4 Aug 1998 09:05:54 -0500 (CDT) Received: (from salo@localhost) by us.networkcs.com (8.8.7/8.8.7) id JAA13246; Tue, 4 Aug 1998 09:05:53 -0500 (CDT) Date: Tue, 4 Aug 1998 09:05:53 -0500 (CDT) From: Tim Salo Message-Id: <199808041405.JAA13246@us.networkcs.com> To: freebsd-atm@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Uni 4.0 support ?? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 4 Aug 1998 16:32:01 +0800 > From: Joerg Micheel > freebsd-hackers@FreeBSD.ORG, brandt@fokus.gmd.de > Subject: Re: Uni 4.0 support ?? > [...] > Yes, HARP might do the job, and UNI 3.0 is not that far from UNI 3.1, thats > correct. However, the difference between Q.SAAL and SSCOP is significant, it > seems rather like an implementation from scratch. We expect to release HARP 3 (http://www.msci.magic.net/harp/) in the very near future, (we are working on documentation and packaging). HARP 3 supports UNI 3.1. It does not support UNI 4.0. -tjs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02403 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:10:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02376 for ; Tue, 4 Aug 1998 07:10:53 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA19594; Tue, 4 Aug 1998 16:06:15 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id OAA22973; Tue, 4 Aug 1998 14:52:23 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808041252.OAA22973@semyam.dinoco.de> To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: SCSI ZIP problems In-reply-to: Your message of "Mon, 03 Aug 1998 15:11:07 MDT." <199808032111.PAA04556@harmony.village.org> Date: Tue, 04 Aug 1998 14:52:22 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have programming information for the aic-6360, but I have too many > other things on my plate to even think about getting to it for a few > months. When I replace the AIC-6360 card in my work system I'll put it in an 386/33 ISA play system and could work on it if there is real interest from users. The problem is that at present this is the place I attached my backup device so I don't want to make any experiments with its driver. :-( Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02481 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:11:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02438 for ; Tue, 4 Aug 1998 07:11:13 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA19638; Tue, 4 Aug 1998 16:06:19 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id OAA23269; Tue, 4 Aug 1998 14:58:54 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808041258.OAA23269@semyam.dinoco.de> Cc: Mike Smith , seggers@semyam.dinoco.de To: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI ZIP problems In-reply-to: Your message of "Sun, 02 Aug 1998 12:47:28 PDT." <199808021947.MAA09419@antipodes.cdrom.com> Date: Tue, 04 Aug 1998 14:58:53 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > problems you're seeing are typical. The continuing lack of support is > largely due to the poor performance of the card; supporting it is no I once took a look at top when I copied a file on a MO disk attached to such a card. The CPU time used in interrupts was high and that was with a device which took less than 1 MByte of data per second. :-( > You would be best off, at this point, to discard the Zoom card and > consider the purchase of one of the better-supported, low-cost PCI That's what at least I will do in the end. As a solution to attach my CD-ROM and MO drive (used mostly for backups) it is good enough at present. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:11:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02541 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:11:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02509 for ; Tue, 4 Aug 1998 07:11:30 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA19684; Tue, 4 Aug 1998 16:06:24 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id PAA23631; Tue, 4 Aug 1998 15:12:52 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808041312.PAA23631@semyam.dinoco.de> To: Jamie Howard Subject: Re: SCSI ZIP problems In-reply-to: Your message of "Sat, 01 Aug 1998 22:10:30 EDT." Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Tue, 04 Aug 1998 15:12:51 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ZIP Zoom card. It even recognizes it fine at start up. However, when I So I/O accesses work. Is it an ISA card? > terminal, the process won't die. Eventually, I start seeing console > messages saying aic(0:5:0) timed out and it will keep trying. >From my experience with wrong interrupt settings and their effects on a NE-2000 compatible card I'd guess that you got the interrupt number the card uses wrong somewhere or more likely you have the wrong BIOS settings. My board's BIOS has settings for reserving interrupt lines for ISA cards. Maybe your BIOS is similar and you got this setting wrong in the new system. If the interrupt line is not connected from the ISA slot to the interrupt controller the card can't send an interrupt on completion of a command and that results in such a timeout. > This same drive and card worked fine under FreeBSD in the other system > just last night. Different settings in the BIOS maybe? Or even a system w/o PCI and PnP? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03068 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:13:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay2.eunet.fr (relay2.eunet.fr [192.134.192.149]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA03033 for ; Tue, 4 Aug 1998 07:13:10 -0700 (PDT) (envelope-from fla@laissus.fr) Received: from laissus.laissus.fr by relay2.eunet.fr (5.65c8d/96.05.03) via EUnet-France id AA04081; Tue, 4 Aug 1998 16:12:49 +0200 (MET) Received: from zebulon.laissus.fr by laissus.laissus.fr with SMTP (1.37.109.4/fla-2.1) id AA14876; Tue, 4 Aug 98 16:02:49 +0200 Received: by zebulon.laissus.fr Message-Id: <19980804155923.40800@laissus.fr> Date: Tue, 4 Aug 1998 15:59:23 +0200 From: Francois LAISSUS To: hackers@FreeBSD.ORG Subject: GIF compressed with ImageMagick-3.9.0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to convert Sun raster files into gif with convert from ImageMagick-3.9.0 : 1) convert -compress zip -colors 8 SUN:file GIF:file.gif 2) convert -colors 8 SUN:file GIF:file.gif In both cases file.gif is not compressed ;-( I've tried it manually with xv, successfuly... Nothing about that in search database. Any idea ? Thank you -- F.Laissus fla@laissus.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 07:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06406 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 07:26:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06371; Tue, 4 Aug 1998 07:26:23 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00482; Tue, 4 Aug 1998 07:25:24 -0700 (PDT) Message-Id: <199808041425.HAA00482@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver In-reply-to: Your message of "04 Aug 1998 09:47:02 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 04 Aug 1998 07:25:23 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA06380 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Etherlink XL driver seems to be working fine. How about committing > it to -current and removing the XL probe/attach code from the vx > driver? The fact that Bill hasn't committed it already tends to indicate he's still in testing. I wouldn't want to rush him *too* much. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 09:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29537 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:03:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29473 for ; Tue, 4 Aug 1998 09:03:17 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id KAA02474; Tue, 4 Aug 1998 10:03:03 -0600 (MDT) Message-Id: <199808041603.KAA02474@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 10:02:41 -0600 To: hackers@FreeBSD.ORG From: Brett Glass Subject: More on the crashes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's some more info on the spontaneous crashes we're seeing under 2.2.7. They seem to happen during times of heavy CPU and memory loads; the crash this morning occurred when we were doing a backup of the entire disk. We do our daily backups by piping the output of dump through gzip -9 and then through FTP to a hard disk on another machine. Just before our OS upgrade we did several such backups for safety; none of them caused a crash. The reboots leave the file system a bit inconsistent. At one point, with a kernel that was built slightly differently, we got error messages saying "malloc(): recursive call" (or something similar). Once, we saw a panic screen that described a virtual memory error; it flashed just before the reboot. Has anyone else seen these? I'm concerned that there might be a VM problem in 2.2.7. (We can't see any signs of flaky hardware.) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 09:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00765 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:09:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00748 for ; Tue, 4 Aug 1998 09:09:15 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA27283; Tue, 4 Aug 1998 18:09:00 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 18:09:00 +0200 (MET DST) Mime-Version: 1.0 To: Brett Glass Cc: hackers@FreeBSD.ORG Subject: Re: 2.2.7 crash during "monthly" maintenance batch References: <199808041250.GAA00974@lariat.lariat.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 18:08:59 +0200 In-Reply-To: Brett Glass's message of "Tue, 04 Aug 1998 06:50:15 -0600" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA00757 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass writes: > [...] This is the second time the system has spontaneously > fallen apart in the two days after the upgrade. What might be wrong? Are > other people seeing this? We're not running anything unusual enough to > cause problems. You don't give us much to work on... What were the circumstances of the crash? Logs? Panic messages? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 09:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01331 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:13:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01282 for ; Tue, 4 Aug 1998 09:13:01 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA27577; Tue, 4 Aug 1998 18:12:16 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 18:12:15 +0200 (MET DST) Mime-Version: 1.0 To: "Kaleb S. KEITHLEY" Cc: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. References: <199808040211.LAA02226@cain.gsoft.com.au> <35C70CB0.4592DCB7@ics.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 18:12:14 +0200 In-Reply-To: "Kaleb S. KEITHLEY"'s message of "Tue, 04 Aug 1998 13:29:20 +0000" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA01310 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kaleb S. KEITHLEY" writes: > When there's an officially released version of FreeBSD with threads, > then I'm sure the default will be to enable threads in XFree86. Umm, as far as I can see from the CVS logs, FreeBSD has had threads since 2.2.0. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 09:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01996 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:17:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01943; Tue, 4 Aug 1998 09:16:38 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA27947; Tue, 4 Aug 1998 18:16:25 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 18:16:24 +0200 (MET DST) Mime-Version: 1.0 To: Mike Smith Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver References: <199808041425.HAA00482@antipodes.cdrom.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 18:16:24 +0200 In-Reply-To: Mike Smith's message of "Tue, 04 Aug 1998 07:25:23 -0700" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA01948 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > The Etherlink XL driver seems to be working fine. How about committing > > it to -current and removing the XL probe/attach code from the vx > > driver? > The fact that Bill hasn't committed it already tends to indicate he's > still in testing. I wouldn't want to rush him *too* much. 8) Well, this is what -current is for, after all. And considering that noone has reported any serious trouble so far, and that there is a fallback driver (vx) in case problems arise, I don't see any reason not to commit it. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 09:38:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04583 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:38:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04532 for ; Tue, 4 Aug 1998 09:37:56 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id KAA03017; Tue, 4 Aug 1998 10:37:19 -0600 (MDT) Message-Id: <199808041637.KAA03017@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 10:36:51 -0600 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) From: Brett Glass Subject: Re: 2.2.7 crash during "monthly" maintenance batch Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199808041250.GAA00974@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA04536 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's yet more info. The system is a 486DX4/100 made by Zeos. 16 MB of RAM, WD 2.5 GB IDE drive, Artisoft AE-3 network adapter (it's an NE2000 clone), several multiport serial cards. I can post the output from dmesg if it'd help. Worked like a champ up until the upgrade, is now rebooting spontaneously when I run heavy-duty apps. Also rebooted during a kernel recompile. --Brett At 06:08 PM 8/4/98 +0200, Dag-Erling Coidan Smørgrav wrote: >Brett Glass writes: >> [...] This is the second time the system has spontaneously >> fallen apart in the two days after the upgrade. What might be wrong? Are >> other people seeing this? We're not running anything unusual enough to >> cause problems. > >You don't give us much to work on... What were the circumstances of >the crash? Logs? Panic messages? > >DES >-- >Dag-Erling Smørgrav - dag-erli@ifi.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 10:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12696 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 10:11:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12670 for ; Tue, 4 Aug 1998 10:10:55 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id TAA29359; Tue, 4 Aug 1998 19:06:03 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id SAA19583; Tue, 4 Aug 1998 18:55:54 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808041655.SAA19583@semyam.dinoco.de> To: tarkhil@asteroid.svib.ru Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: What does it mean? In-reply-to: Your message of "Tue, 04 Aug 1998 12:22:53 +0400." <199808040822.MAA12251@minas-tirith.pol.ru> Date: Tue, 04 Aug 1998 18:55:52 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 65534 328 316 0 -22 0 17392 10076 vmpfw D con- 12:35.05 squid -sY > > what does it mean? Who/whot/how deadlocked squid? It is in D state, and > immunet even to kill -9 :-( It's in the middle of a page fault. Pretty inconvenient time to get killed ... That's why killing doesn't work. Were there at that time any problems reported with the swap spaces you used? I/O errors or other irregularities? Anything special you did to this process or its process group? Does it use anything mount via NFS? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 10:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17967 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 10:30:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17839; Tue, 4 Aug 1998 10:30:08 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA18553; Tue, 4 Aug 1998 10:29:29 -0700 (PDT) Message-Id: <199808041729.KAA18553@tnt.isi.edu> To: Robert Swindells Cc: se@FreeBSD.ORG, fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Sun, 02 Aug 1998 11:54:30 BST." <199808021054.LAA00638@fdy2.demon.co.uk> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 10:29:29 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Robert Swindells wrote: >I haven't written a new driver, just made minor changes to the old one. > >The changes are: > > * Add probing support for the chip IDs for newer PCnet chips - 79c970A, > 79c971 and 79c972. > > * Add support for reading and writing the BCR registers. Not currently > used, but you need it to be able to add ifmedia support. > > * Modify pcnet_probe() to always return the chip type even if it is a > PCI device. The probe routines that call this now check for the > returned chip type when determining whether to attach it. > >Things not done: > > * No probe for 79c960A (PCnet-ISA II) > > * The chip ID for the 79c970 doesn't look right. It may be that the probe > for this only worked because there was no distinction between "Unknown" > and "PCI". > >I'll check into these two before doing a send-pr. If it's OK with you all, I'd just as soon take Robert's patches than work on getting my bogus ones to work. Unless I hear otherwise, I'll assume that's whats happening. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcdE+Ib4eisfQ5rpAQGH9QP/bGyDhhotwwE/SD18iSkOIuV8keg1d53t IAZaWuNN0ULE5GYvkYPblBzFIZIp+cwpkvUGDwwF+pLK3MTOWgtluzb7dtGi5pNH MHix0bvtoqsjjX+r5Chzdzi9NYNt+CXR5ixDJ9wFojD6gH2RTZs5DGXdJLiaBV5H K12QD3uOe3U= =vKr7 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 10:37:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19509 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 10:37:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19479 for ; Tue, 4 Aug 1998 10:37:35 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id KAA08122; Tue, 4 Aug 1998 10:36:50 -0700 (PDT) (envelope-from jdp) Message-Id: <199808041736.KAA08122@austin.polstra.com> To: abial@nask.pl Subject: Re: PAM4FreeBSD In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Tue, 04 Aug 1998 10:36:50 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Andrzej Bialecki wrote: > > On Tue, 28 Jul 1998, Mike Smith wrote: > > > > Hi ! > > > > > > One question. Is FreeBSD will support PAM ? > > > > I don't know of anyone with plans to add PAM support, no. I ported the > > Linux-PAM code some time back, but PAM is inherently flawed and the > > effort involved in making it work would not necessarily produce a > > useful result. > > Still, I think something should be decided wrt. the way various auth. > schemes can be plugged in without doing it each time from the grounds. > Thus far it was done by patching by hand the appropriate programs, which > is clumsy and sometimes leaves us with almost indentical sections of auth. > code (cf. ftp & login) which have to be maintained together with millions > of #ifdef's, etc etc... I have been working on PAM for a client, and the client is willing to donate the work to FreeBSD. I think any flaws in PAM are not too serious, and can be fixed. I plan to bring it into -current when I get the official go-ahead from my client. > There is already existing framework of *CAP_AUTH, which was meant to be > used together with login_* modules. Is it dead or something? If it's dead, > let's bury its remains, and if not - let's start to write login_* modules. I looked at that stuff, and I want to remove it. It is very poorly defined even in BSD/OS, whence it came. Also it is inferior to PAM. PAM allows the application to determine the style of the user interface for getting information such as passwords. The LOGIN_CAP_AUTH stuff has the user interface hard-coded into the authentication modules themselves. That's not the right place for it. I discussed the LOGIN_CAP_AUTH support with David Nugent, who brought it into FreeBSD. He reinforced my opinion that it is a dead end. I plan to remove it when I bring in PAM. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 10:38:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19640 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 10:38:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19573 for ; Tue, 4 Aug 1998 10:38:10 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc104.reseau.uvsq.fr [193.51.24.20]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id TAA11234 for ; Tue, 4 Aug 1998 19:37:51 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.8/8.8.5) id SAA05362; Tue, 4 Aug 1998 18:59:38 GMT Message-ID: <19980804185938.36803@breizh.prism.uvsq.fr> Date: Tue, 4 Aug 1998 18:59:38 +0000 From: Nicolas Souchu To: FreeBSD Hackers Subject: C and static initialization with unions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, A question about C and static initialization of unions: suppose, union foo_t { int i; char c; void *p; }; static union foo_t bar = { (void *)&anyvar }; The compiler says "warning, making integer from pointer without a cast"... Which is true and could lead to bad asm code. Is there a way to do this properly? Should I forgive unions or what else? -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25091 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:03:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24964 for ; Tue, 4 Aug 1998 11:02:23 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id OAA20933 for ; Tue, 4 Aug 1998 14:02:07 -0400 (EDT) Date: Tue, 4 Aug 1998 14:02:04 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: hackers@FreeBSD.ORG Subject: executables over NFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are executables loaded over NFS treated the same as local executables with regard to paging? Specifically, do they use the remote file as backing store, or local swap space? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:03:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25152 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:03:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25050 for ; Tue, 4 Aug 1998 11:02:46 -0700 (PDT) (envelope-from kaleb@ics.com) Received: from ics.com (kaleb@teapot.ics.com [140.186.40.160]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id OAA16318; Tue, 4 Aug 1998 14:02:29 -0400 (EDT) Message-ID: <35C74B7A.42031494@ics.com> Date: Tue, 04 Aug 1998 17:57:14 +0000 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.31 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. References: <199808040211.LAA02226@cain.gsoft.com.au> <35C70CB0.4592DCB7@ics.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA25068 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Coidan Smørgrav wrote: > > "Kaleb S. KEITHLEY" writes: > > When there's an officially released version of FreeBSD with threads, > > then I'm sure the default will be to enable threads in XFree86. > > Umm, as far as I can see from the CVS logs, FreeBSD has had threads > since 2.2.0. I don't remember which of the released versions I last had installed on my system, but it didn't have threads. Had it had __working__ threads then I would have turned it on in The Open Group release (and I expect XFree86 would have picked up the change too.) FWIW, trying to keep up with FreeBSD releases and get work done at the same time is getting a bit too much like keeping up with Linux releases. At this point I'd rather see __the__ 3.0 release than another 2.x release. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27027 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:09:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26794 for ; Tue, 4 Aug 1998 11:08:43 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id LAA00540 for ; Tue, 4 Aug 1998 11:39:01 -0400 (EDT) Date: Tue, 4 Aug 1998 11:39:01 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-Hackers@FreeBSD.ORG Subject: Scsi disk deals Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to thank those who replied, because I found exactly what I wanted, it's on it's way, and I think I got a good deal both in bucks and in quality. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:21:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29989 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:21:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29957 for ; Tue, 4 Aug 1998 11:21:32 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id WAA02444; Tue, 4 Aug 1998 22:21:07 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id WAA05028; Tue, 4 Aug 1998 22:20:38 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199808041820.WAA05028@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What does it mean? In-reply-to: Your message "Tue, 04 Aug 1998 18:55:52 +0200." <199808041655.SAA19583@semyam.dinoco.de> Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Tue, 04 Aug 1998 22:20:37 +0400 From: Alex Povolotsky Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <199808041655.SAA19583@semyam.dinoco.de>Stefan Eggers writes: >> 65534 328 316 0 -22 0 17392 10076 vmpfw D con- 12:35.05 squi >d -sY >It's in the middle of a page fault. Pretty inconvenient time to get >killed ... That's why killing doesn't work. How can it be in the middle of page fault for several minutes? >Were there at that time any problems reported with the swap spaces you >used? I/O errors or other irregularities? Anything special you did No. No. No. It just run for nearly 6 days. There were NO disk I/O errors, and there were used only about 10% of swap space. >to this process or its process group? Does it use anything mount via >NFS? No. No. Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01610 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:31:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agustina.kjsl.com (Agustina.KJSL.COM [198.137.202.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01591; Tue, 4 Aug 1998 11:31:22 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from uucp@localhost) by agustina.kjsl.com (8.8.7/8.8.8/rchk1.19) with UUCP id LAA10189; Tue, 4 Aug 1998 11:23:56 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.8/rchk1.19) id LAA07589; Tue, 4 Aug 1998 11:14:24 -0700 (PDT) (envelope-from fmc) Message-Id: <199808041814.LAA07589@daemonweed.reanimators.org> To: Ted Faber Cc: Robert Swindells , se@FreeBSD.ORG, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? References: <199808041729.KAA18553@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 04 Aug 1998 11:14:24 -0700 In-Reply-To: Ted Faber's message of Tue, 04 Aug 1998 10:29:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Faber wrote: > If it's OK with you all, I'd just as soon take Robert's patches than > work on getting my bogus ones to work. Unless I hear otherwise, I'll > assume that's whats happening. Apologies for going silent the last few days, got busy with other stuff. But last night I built with Robert's posted patches and try them out. They successfully probe and attach my Vectra's card as a PCI device and work for light traffic (DNS, telnet, rsh, emacs-over-X) thereafter. Haven't tried beating on it yet, if there's something you'd like me to try feel free to ask. -Frank McConnell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:34:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02133 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:34:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02124 for ; Tue, 4 Aug 1998 11:34:50 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA00300; Tue, 4 Aug 1998 11:31:46 -0700 (PDT) Message-Id: <199808041831.LAA00300@implode.root.com> To: ben@rosengart.com cc: hackers@FreeBSD.ORG Subject: Re: executables over NFS In-reply-to: Your message of "Tue, 04 Aug 1998 14:02:04 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 04 Aug 1998 11:31:46 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Are executables loaded over NFS treated the same as local executables >with regard to paging? Yes. > Specifically, do they use the remote file as >backing store, or local swap space? The remote file is the backing store. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 11:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05459 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:59:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05444 for ; Tue, 4 Aug 1998 11:58:56 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id LAA09291 for freebsd-hackers@freebsd.org; Tue, 4 Aug 1998 11:55:36 -0700 (PDT) (envelope-from dhw) Date: Tue, 4 Aug 1998 11:55:36 -0700 (PDT) From: David Wolfskill Message-Id: <199808041855.LAA09291@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Parsing /var/run/dmesg.boot In-Reply-To: <199807271842.LAA25740@pau-amma.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 27 Jul 1998 11:25:51 -0700 >From: Mike Smith >Something like /var/run/dmesg.boot, perhaps? [As a means of determining what the machine "saw" at boot time. dhw] OK; I've been poking & prowling around a bit, mostly with /var/run/dmesg.boot. Is it intended that the format & structure of this output be constrained in any way? The reason I'm asking is that I think it *might* be nice to be able to post-process the output to try to "better" (in some sense) analyze & depict the machine's configuration. However, if it's strictly for human consumption, this could well be a wasted effort... and each of us, I expect, has quite enough to do without such things. :-} [I've got a start toward a Perl script cobbled up that reads /var/run/dmesg.boot (or an alternative file, if you like), scans it to find the (last) boot messages, & then... well, at the moment, it just spits them out to STDOUT. Why use the script? Well, sometimes the boot messages aren't first in the file. Anyway, I tried it on a -current system, and found that -current doesn't have the empty line just before the /^FreeBSD 2/ line that 2.x does.... the goal, as alluded to above, is to generate some sort of representation of the machine's configuration as of the most recent boot in order to make replication of the machine (for disaster recovery) more nearly feasible -- assuming, of course, that the representation is available, as are current backups.] Thanks, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 12:46:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13195 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 12:46:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13183 for ; Tue, 4 Aug 1998 12:46:47 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id PAA20152; Tue, 4 Aug 1998 15:46:27 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id QAA02892; Tue, 4 Aug 1998 16:19:15 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id PAA16333; Tue, 4 Aug 1998 15:50:33 -0400 (EDT) Date: Tue, 4 Aug 1998 15:50:33 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808041950.PAA16333@lakes.dignus.com> To: brett@lariat.org, hackers@FreeBSD.ORG Subject: Re: More on the crashes In-Reply-To: <199808041603.KAA02474@lariat.lariat.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass writes: > > Here's some more info on the spontaneous crashes we're seeing under 2.2.7. > They seem to happen during times of heavy CPU and memory loads; the crash > this morning occurred when we were doing a backup of the entire disk. We do > our daily backups by piping the output of dump through gzip -9 and then > through FTP to a hard disk on another machine. Just before our OS upgrade > we did several such backups for safety; none of them caused a crash. > > The reboots leave the file system a bit inconsistent. > > At one point, with a kernel that was built slightly differently, we got > error messages saying "malloc(): recursive call" (or something similar). > Once, we saw a panic screen that described a virtual memory error; it > flashed just before the reboot. > > Has anyone else seen these? I'm concerned that there might be a VM problem > in 2.2.7. (We can't see any signs of flaky hardware.) > > --Brett > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Yes - I've seen it (along with someone else.) I saw it with the upgrade from 2.2.5 to 2.2.6. [Did you see it at 2.2.6?] I've already sent a PR for this; it's kern/7367. I've taken the liberty of adding this reply to that PR entry... You may want to look at that entry for other comments/descriptions. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 12:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13980 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 12:51:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA13973 for ; Tue, 4 Aug 1998 12:51:11 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3n6h-0006yv-00; Tue, 4 Aug 1998 13:50:51 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA18579; Tue, 4 Aug 1998 13:50:49 -0600 (MDT) Message-Id: <199808041950.NAA18579@harmony.village.org> To: Nicolas Souchu Subject: Re: C and static initialization with unions Cc: FreeBSD Hackers In-reply-to: Your message of "Tue, 04 Aug 1998 18:59:38 -0000." <19980804185938.36803@breizh.prism.uvsq.fr> References: <19980804185938.36803@breizh.prism.uvsq.fr> Date: Tue, 04 Aug 1998 13:50:49 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980804185938.36803@breizh.prism.uvsq.fr> Nicolas Souchu writes: : static union foo_t bar = { (void *)&anyvar }; : : The compiler says "warning, making integer from pointer without a cast"... : Which is true and could lead to bad asm code. static union foo_t bar = { (int)(void *)&anyvar }; But it is unwise to assume that sizeof(int) == sizeof(void *). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 13:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16834 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 13:06:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16779 for ; Tue, 4 Aug 1998 13:06:34 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id OAA25533 for ; Tue, 4 Aug 1998 14:05:31 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Tue, 4 Aug 1998 14:05:31 -0600 (MDT) From: Brett Taylor To: freebsd-hackers@FreeBSD.ORG Subject: couple of questions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, A week or so ago Slashdot posted a link to an OS Comparison chart - FreeBSD was missing so I emailed the author of the page and offered to get the FreeBSD info to add to the chart and he thought that would be great. I've dug through the mailing lists/FAQ/handbook and have gotten just about everything answered but a couple of technical questions remain and I was hoping that some of the hackers could answer them! :-) These questions concern the 2.2.7 release. You can see the chart at: http://www.xunil.com/xunil/oschart.html - maximum file/partition size: - I've seen files (from an ls -l emailed to me) of ~ 7 GB, but I'm not sure what the absolute maximum file size is. Is there a hard limit? - digging through the -current mailing list archive I found a note from John Dyson saying the maximum partition size was 512 GB. Is this still true (the note was from 97) and if so does it also apply to 2.2.7? - swap partitions - what's the maximum swap partition size? I seem to recall reading on -current about someone w/ a 1 GB swap partition, but my memory has been known to be faulty. - what's the maximum number of swap partitions you can have? - multi-disk file systems - in the chart he references Caldera having "md" - I'm not sure what this is. Any ideas? My interpretation was say /usr on 1 disk, /tmp on another or something, but I'm still waiting for an answer. If it helps he has "volume sets" listed under NT and ODM under SCO Unixware Thanks for any help in advance! Brett ************************************************************* Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ "The bicycle is the most civilized conveyance known to man. Other forms of transport grow daily more nightmarish. Only the bicycle remains pure in heart." - Iris Murdoch, "The Red and the Green" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 13:11:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17624 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 13:11:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17524 for ; Tue, 4 Aug 1998 13:10:56 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA01548; Tue, 4 Aug 1998 15:09:11 -0400 (EDT) Date: Tue, 4 Aug 1998 15:09:11 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Nicolas Souchu cc: FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: <19980804185938.36803@breizh.prism.uvsq.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Nicolas Souchu wrote: > Hi there, > > A question about C and static initialization of unions: > > suppose, > > union foo_t { > int i; > char c; > void *p; > }; > > static union foo_t bar = { (void *)&anyvar }; > > The compiler says "warning, making integer from pointer without a cast"... > Which is true and could lead to bad asm code. > > Is there a way to do this properly? Should I forgive unions or what else? No, you forgot to mention which union memeber to use. Your foo_t.p would do nicely. > > -- > Nicolas.Souchu@prism.uvsq.fr > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 13:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21791 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 13:32:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21786; Tue, 4 Aug 1998 13:32:27 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id OAA06669; Tue, 4 Aug 1998 14:32:04 -0600 (MDT) Message-Id: <199808042032.OAA06669@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 14:31:39 -0600 To: Thomas David Rivers , hackers@FreeBSD.ORG, bugs@FreeBSD.ORG From: Brett Glass Subject: Re: More on the crashes In-Reply-To: <199808041950.PAA16333@lakes.dignus.com> References: <199808041603.KAA02474@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:50 PM 8/4/98 -0400, Thomas David Rivers wrote: > Yes - I've seen it (along with someone else.) I saw it with the >upgrade from 2.2.5 to 2.2.6. [Did you see it at 2.2.6?] None of our machines are running 2.2.6. But the problem is easily reproducible under 2.2.7. All I have to do is try to do a backup in the manner described. Of course, that's a pretty nasty way to have it fail, as it means that our backup mechanism is shot. And you might remember that this was an upgrade due to a security breach.... We need the backups in case someone breaks in again. > I've already sent a PR for this; it's kern/7367. > > I've taken the liberty of adding this reply to that PR entry... You >may want to look at that entry for other comments/descriptions. Sounds good. Please let me know if there's something I can do to help track down the cause. I need a 2.2.7.x that's reliable! --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 13:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24184 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 13:51:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mbm.on.ca ([142.154.10.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24147 for ; Tue, 4 Aug 1998 13:51:22 -0700 (PDT) (envelope-from mnewton@mbm.on.ca) Received: from notbook.mbm.on.ca ([142.154.11.7]) by mbm.on.ca (8.6.12/8.6.12) with SMTP id QAA00542 for ; Tue, 4 Aug 1998 16:54:53 -0400 Message-ID: <01cd01bdbfe0$81512440$070b9a8e@notbook.mbm.on.ca> Reply-To: "Malcolm Newton" From: "Malcolm Newton" To: Subject: limit mail message size by address Date: Tue, 4 Aug 1998 15:45:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way of limiting an email message size by address. i.e. only certain people in a company are allowed to get large files like xls etc and cut out everyone from receiving/sending large gif/jpg files. Would be good to limit file type by user as another way of controlling certain users. thx mn Malcolm Newton mnewton@mbm.on.ca (416) 410 6075 (416) 823 5771 cell (905) 274 6032 Fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 14:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28162 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 14:29:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cserv.oksys.bg ([195.230.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28149 for ; Tue, 4 Aug 1998 14:29:10 -0700 (PDT) (envelope-from ian@bulinfo.net) Received: from ian (ian.oksys.bg [192.72.180.23]) by cserv.oksys.bg (8.8.8/8.8.8) with SMTP id AAA21107 for ; Wed, 5 Aug 1998 00:28:44 +0300 (EEST) (envelope-from ian@bulinfo.net) Message-ID: <000301bdbfee$b3140fc0$17b448c0@ian.oksys.bg> From: "Iani Brankov" To: Subject: Want to write support for PCI variant of the arc0 driver. Help with info :) Date: Wed, 5 Aug 1998 00:27:34 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3115.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, we've bought a Digiboard 570 pci sync card, which isn't supported by FreeBSD. There's support for the ISA variant only. The PCI card is almost the same and I'll try to write a pci routines to detect and attach the pci card to the existing ISA driver. (as i see it runs the same way). I need some information. Can I find some documentation how to write a driver (pci, isa) for FreeBSD. thanks. ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 14:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28166 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 14:29:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from core.nex.net ([208.15.108.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA28151 for ; Tue, 4 Aug 1998 14:29:20 -0700 (PDT) (envelope-from vpicanco@nex.net) Received: from InternetSolutions.insolwwb.net (208.15.108.240) by core.nex.net (EMWAC SMTPRS 0.81) with SMTP id ; Tue, 04 Aug 1998 16:31:36 -0500 Message-ID: <000801bdbfee$5417a7c0$f06c0fd0@InternetSolutions.insolwwb.net> From: "Picanco" To: Subject: Fw: Fatal trap 12:page fault while in kernel mode Date: Tue, 4 Aug 1998 16:24:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Doug White To: Picanco Date: Tuesday, August 04, 1998 2:52 PM Subject: Re: Fatal trap 12:page fault while in kernel mode > >On Tue, 4 Aug 1998, Picanco wrote: > >> I have waited a week without a response... please check the hackers office >> and make sure they have recieved your mail... if so, please ask them to send >> me an email verifying my question and the progress of the solution... thanks > >If they didn't respond then there's not enough detail... please repost the >message to the mailing list hackers@freebsd.org and try to include as much >detail as humanly possible. > >> >> -----Original Message----- >> From: Doug White >> To: Picanco >> Cc: hackers@freebsd.org >> Date: Tuesday, July 28, 1998 12:41 PM >> Subject: Re: Fatal trap 12:page fault while in kernel mode >> >> >> > >> >On Mon, 27 Jul 1998, Picanco wrote: >> > >> >> Intel Pentium 200 non overclocked... socket 7 chip >> >> >> >> the first time I tryed the install I used the 2.2.6 boot.flp file and got >> >> the message below... >> >> then I tryed the install with the 2.2.7 boot.flp file and recieved the >> same >> >> message >> >> with only a difference in the following line: >> >> >> >> fault virtual address = 0xf4c14003 >> >> >> > >> >Okay, I'm forwarding this up to -hackers. Hopefully the detail below will >> >give them a hint... >> > >> >> >> >> >> >> -----Original Message----- >> >> From: Doug White >> >> To: Picanco >> >> Date: Monday, July 27, 1998 4:21 PM >> >> Subject: Re: Fatal trap 12:page fault while in kernel mode >> >> >> >> >> >> > >> >> >On Sat, 25 Jul 1998, Picanco wrote: >> >> > >> >> >> CPU- Pentium 200 >> >> > >> >> >This is an Intel Pentium 200, or an AMD, or Cyrix? Is your motherboard >> >> >overclocked? >> >> > >> >> >> Motherboard- Tomcat IV S1564S Award BIOS >> >> >> Memory- 8 x 32M 72-pin Full parity SIMM chips >> >> > >> >> >What version of FreeBSD are you on? >> >> > >> >> >> >> >> >> -----Original Message----- >> >> >> From: Doug White >> >> >> To: Picanco >> >> >> Cc: freebsd-questions@FreeBSD.ORG >> >> >> Date: Friday, July 24, 1998 7:09 PM >> >> >> Subject: Re: Fatal trap 12:page fault while in kernel mode >> >> >> >> >> >> >> >> >> > >> >> >> >On Thu, 23 Jul 1998, Picanco wrote: >> >> >> > >> >> >> >> here is the error I recieved when attempting to install Freebsd: >> >> >> >> >> >> >> >> avail memory = 259289088 (253212k bytes) >> >> >> >> >> >> >> >> Fatal trap 12:page fault while in kernel mode >> >> >> >> fault virtual address = 0xf52ca0003 >> >> >> >> fault code = supervisor read, page not >> present >> >> >> >> instruction pointer = 0x8:0xf01ace43 >> >> >> >> stack pointer = 0x10:0xefbfff70 >> >> >> >> frame pointer = 0x10:0xefbfff80 >> >> >> >> code segment = base 0x0, limit 0xfffff, type 0x1b >> >> >> >> = DPL 0, pres 1, def32 1, gran >> 1 >> >> >> >> processor eflags = resume, IOPL = 0 >> >> >> >> current process = 0 ( ) >> >> >> >> interupt mask = net tty bio cam >> >> >> >> panic:page fault >> >> >> >> >> >> >> >> Any help or suggestions would be greatly appreciated... if I do not >> >> >> >> recieve a response within 5-10 days, will resend this message Thank >> >> >> >> you for your time >> >> >> > >> >> >> >Please post your system details, inclugin CPU type, motherboard type, >> >> and >> >> >> >memory configuration. >> >> >> > >> >> >> >Doug White | University of Oregon >> >> >> >Internet: dwhite@resnet.uoregon.edu | Residence Networking >> Assistant >> >> >> >http://gladstone.uoregon.edu/~dwhite | Computer Science Major >> >> >> > >> >> >> >> >> > >> >> >Doug White | University of Oregon >> >> >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant >> >> >http://gladstone.uoregon.edu/~dwhite | Computer Science Major >> >> > >> >> >> > >> >Doug White | University of Oregon >> >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant >> >http://gladstone.uoregon.edu/~dwhite | Computer Science Major >> > >> > >Doug White | University of Oregon >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant >http://gladstone.uoregon.edu/~dwhite | Computer Science Major > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 14:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00258 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 14:43:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00252 for ; Tue, 4 Aug 1998 14:43:41 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id OAA15441; Tue, 4 Aug 1998 14:43:22 -0700 (PDT) Message-Id: <199808042143.OAA15441@tnt.isi.edu> To: Warner Losh Cc: Nicolas Souchu , FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: Your message of "Tue, 04 Aug 1998 13:50:49 MDT." <199808041950.NAA18579@harmony.village.org> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 14:43:21 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Warner Losh wrote: >In message <19980804185938.36803@breizh.prism.uvsq.fr> Nicolas Souchu writes: >: static union foo_t bar = { (void *)&anyvar }; >: >: The compiler says "warning, making integer from pointer without a cast"... >: Which is true and could lead to bad asm code. > >static union foo_t bar = { (int)(void *)&anyvar }; > >But it is unwise to assume that sizeof(int) == sizeof(void *). The comp.lang.c FAQ (http://www.eskimo.com/~scs/C-faq/top.html) suggests putting the member he wants to initialize first in the union, where a conformant ANSI C compiler will initialize it correctly. (http://www.eskimo.com/~scs/C-faq/q2.20.html) Initializing with that cast defeats the point of using a union at all. Not that this belongs in hackers... - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNceAeIb4eisfQ5rpAQFWIAQAsfm+uom56JCQN1Y16/Uhg2nYB5YpkbgN 51r1pYyVTtjkOTJawORnbYHdTPT/648ySX7WZFTXb9mJEook50Ue0YaesF83SlIN n4SLsD9wPOMTNrzZZEXihecS9HTXfcWzaaeMfNhIlUycKc6O5DGScU0Hkq18UQvZ 2sNiG8qd1oE= =cYvz -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 15:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05979 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 15:24:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05950 for ; Tue, 4 Aug 1998 15:23:48 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id SAA19257; Tue, 4 Aug 1998 18:23:28 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id SAA03210; Tue, 4 Aug 1998 18:56:20 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id SAA16749; Tue, 4 Aug 1998 18:27:34 -0400 (EDT) Date: Tue, 4 Aug 1998 18:27:34 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808042227.SAA16749@lakes.dignus.com> To: chuckr@glue.umd.edu, Nicolas.Souchu@prism.uvsq.fr Subject: Re: C and static initialization with unions Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Tue, 4 Aug 1998, Nicolas Souchu wrote: > > > Hi there, > > > > A question about C and static initialization of unions: > > > > suppose, > > > > union foo_t { > > int i; > > char c; > > void *p; > > }; > > > > static union foo_t bar = { (void *)&anyvar }; > > > > The compiler says "warning, making integer from pointer without a cast"... > > Which is true and could lead to bad asm code. > > > > Is there a way to do this properly? Should I forgive unions or what else? > > No, you forgot to mention which union memeber to use. Your foo_t.p > would do nicely. You can't in C initialize only a member of a structure that way. Furthermore, the ANSI C standard specifies that initializations of unions use the first field of the union as the initialization type. Thus, gcc is correct in its message; since the type of the initialization for the union field would be and int, the first field of the union. Now; if you reorder the union fields, so that 'p' is first, you can do the initialization you'd like without any problems. Another posted also responded with the appropriate casts for doing that. Also - you should be aware that ANSI forbids assigning to one element of a union and referencing a different element. (Basically, the 'type-punning' problem) C compilers are allowed to optimize field references based on type; so that: main() { union foo_t foo; void *vp; foo.i = 5; foo.p = 0; if(foo.i) { printf("true\n"); } else { printf("false\n"); } } may, depending on the optimizer, print either true or false. Technically, this is an invalid ANSI C program. - Dave Rivers - > > > > > -- > > Nicolas.Souchu@prism.uvsq.fr > > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 15:38:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09352 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 15:38:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09303 for ; Tue, 4 Aug 1998 15:38:06 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id SAA06354 for ; Tue, 4 Aug 1998 18:37:52 -0400 (EDT) Date: Tue, 4 Aug 1998 18:37:51 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Questione on pageout deamon Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (1) In the VM source files, there are many occurrences of pageproc in comparison "curproc == pageproc". Does pageproc stand for the pageout daemon? (2) It seems that pageout daemon can sleep on either vm_pages_needed or vm_pageout_pages_needed. When does pageout deamon itself need pages? (3) Can pageout daemon be waken up at interrupt time? If not, why we check this at the beginning of vm_page_alloc()? Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 15:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10185 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 15:45:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10155 for ; Tue, 4 Aug 1998 15:45:31 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id RAA01869; Tue, 4 Aug 1998 17:43:34 -0400 (EDT) Date: Tue, 4 Aug 1998 17:43:34 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Thomas David Rivers cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: <199808042227.SAA16749@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Thomas David Rivers wrote: > Also - you should be aware that ANSI forbids assigning to one element > of a union and referencing a different element. (Basically, the > 'type-punning' problem) C compilers are allowed to optimize field > references based on type; so that: > > main() > { > union foo_t foo; > void *vp; > > foo.i = 5; > foo.p = 0; > > if(foo.i) { > printf("true\n"); > } else { > printf("false\n"); > } > } > > may, depending on the optimizer, print either true or false. Technically, > this is an invalid ANSI C program. I never saw that, and I think you may be wrong, so if you have the ansi standard lying around, give me a quote, ok? Harbison & Steele says, on page 132-133, that doing what you said above is non-portable (I agree), but programmers "sometimes do this to 'reach under' C's type system ...". There was more, but I'm sure you know it already. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 15:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10655 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 15:50:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from moebius.space.net (moebius.Space.Net [195.30.1.25]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA10649 for ; Tue, 4 Aug 1998 15:50:38 -0700 (PDT) (envelope-from maex@Space.Net) Received: (qmail 21333 invoked by uid 1013); 4 Aug 1998 22:49:42 -0000 Message-ID: <19980805004942.L12619@space.net> Date: Wed, 5 Aug 1998 00:49:42 +0200 From: Markus Stumpf To: Brett Taylor , freebsd-hackers@FreeBSD.ORG Subject: Re: couple of questions References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brett Taylor on Tue, Aug 04, 1998 at 02:05:31PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 02:05:31PM -0600, Brett Taylor wrote: > - maximum file/partition size: > > - I've seen files (from an ls -l emailed to me) of ~ 7 GB, but > I'm not sure what the absolute maximum file size is. Is there > a hard limit? Hmmm ... this is from man 2 intro (2.2.6-RELEASE) > 27 EFBIG File too large. The size of a file exceeded the maximum (about > 2.1E9 bytes). This is 2 GB, right? But I've heard NetBSD has bigger files. \Maex N.B. This 2 GB always hits me with backups of large partitions that don't compress well. Still using amanda-2.3.0, however, amanda-2.4.0 is able to handle this with artificial splits. -- SpaceNet GmbH | http://www.Space.Net/ | In a world whithout Research & Development | mailto:research@Space.Net | walls and fences, Frankfurter Ring 193a | Tel: +49 (89) 32356-0 | who needs D-80807 Muenchen | Fax: +49 (89) 32356-299 | Windows and Gates? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 16:25:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14864 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 16:25:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14859 for ; Tue, 4 Aug 1998 16:25:16 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA06963; Tue, 4 Aug 1998 16:25:06 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd006936; Tue Aug 4 16:24:58 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id QAA11676; Tue, 4 Aug 1998 16:24:57 -0700 (MST) From: Terry Lambert Message-Id: <199808042324.QAA11676@usr07.primenet.com> Subject: Re: Problems Restarting xdm To: malte.lance@gmx.net Date: Tue, 4 Aug 1998 23:24:57 +0000 (GMT) Cc: tomdean@ix.netcom.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <13766.50765.170940.775527@neuron.webmore.de> from "Malte Lance" at Aug 4, 98 10:30:14 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The XFree86 readme suggests starting xdm from /etc/ttys. The FreeBSD > > FAQ suggests starting xdm from rc.local. Either way, if there is, for > > example, a power glitch reboot, xdm will not start without root > > intervention. I believe this is because the pid file exists. > > Do you clean up /tmp on bootup ? > If not, maybe /tmp/.X-lock bites you after "power glitch reboot". This is a job for ... rc.d. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 16:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18131 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 16:46:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18114 for ; Tue, 4 Aug 1998 16:46:21 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA11220; Wed, 5 Aug 1998 09:15:32 +0930 (CST) Message-Id: <199808042345.JAA11220@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kaleb S. KEITHLEY" cc: hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Tue, 04 Aug 1998 13:29:20 GMT." <35C70CB0.4592DCB7@ics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 09:15:32 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The last time I tried building with threads, on some 3.0SNAP version, > things didn't work very well (and I haven't spent any time trying to > figure out why.) Hmm.. worked for me quite easily, I just added the following lines to the work/ xc/config/xc/FreeBSD.cf file. #define HasPosixThreads YES #define ThreadedX YES #define HasThreadSafeAPI YES #define ThreadsLibraries -pthread > > Also is there any chance that the thread cancellation routines will be > > implented any time soon? :) > In Xlib or in libc? In libc. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 16:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18498 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 16:49:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18489 for ; Tue, 4 Aug 1998 16:48:59 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id SAA26478; Tue, 4 Aug 1998 18:48:44 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id SAA04222; Tue, 4 Aug 1998 18:48:44 -0500 (CDT) Message-ID: <19980804184843.20768@mcs.net> Date: Tue, 4 Aug 1998 18:48:44 -0500 From: Karl Denninger To: Markus Stumpf Cc: Brett Taylor , freebsd-hackers@FreeBSD.ORG Subject: Re: couple of questions References: <19980805004942.L12619@space.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980805004942.L12619@space.net>; from Markus Stumpf on Wed, Aug 05, 1998 at 12:49:42AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 05, 1998 at 12:49:42AM +0200, Markus Stumpf wrote: > On Tue, Aug 04, 1998 at 02:05:31PM -0600, Brett Taylor wrote: > > - maximum file/partition size: > > > > - I've seen files (from an ls -l emailed to me) of ~ 7 GB, but > > I'm not sure what the absolute maximum file size is. Is there > > a hard limit? > > Hmmm ... this is from man 2 intro (2.2.6-RELEASE) > > > 27 EFBIG File too large. The size of a file exceeded the maximum (about > > 2.1E9 bytes). > > This is 2 GB, right? But I've heard NetBSD has bigger files. > > \Maex > > N.B. This 2 GB always hits me with backups of large partitions that don't > compress well. Still using amanda-2.3.0, however, amanda-2.4.0 is able > to handle this with artificial splits. Uh, there is no 2GB limit on files in FreeBSD-current. I have files larger than this on the filesystems here. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 16:49:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18525 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 16:49:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18500 for ; Tue, 4 Aug 1998 16:49:06 -0700 (PDT) (envelope-from Olivier.Galibert@loria.fr) Received: from renaissance.loria.fr (renaissance.loria.fr [152.81.4.102]) by lorraine.loria.fr (8.8.7/8.8.7/8.8.7/JCG) with ESMTP id BAA07611 for ; Wed, 5 Aug 1998 01:47:48 +0200 (MET DST) Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id BAA29777; Wed, 5 Aug 1998 01:47:46 +0200 (MET DST) Message-ID: <19980805014745.A29768@loria.fr> Date: Wed, 5 Aug 1998 01:47:45 +0200 From: Olivier Galibert To: freebsd-hackers@FreeBSD.ORG Subject: Re: What does it mean? Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <199808041655.SAA19583@semyam.dinoco.de> <199808041820.WAA05028@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808041820.WAA05028@minas-tirith.pol.ru>; from Alex Povolotsky on Tue, Aug 04, 1998 at 10:20:37PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 10:20:37PM +0400, Alex Povolotsky wrote: > How can it be in the middle of page fault for several minutes? mmap of a NFS-mounted file or equivalent? OG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 16:55:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19923 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 16:55:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19916; Tue, 4 Aug 1998 16:55:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA00472; Tue, 4 Aug 1998 16:53:59 -0700 (PDT) Message-Id: <199808042353.QAA00472@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ted Faber cc: Robert Swindells , se@FreeBSD.ORG, fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Tue, 04 Aug 1998 10:29:29 PDT." <199808041729.KAA18553@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 16:53:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I'll check into these two before doing a send-pr. > > If it's OK with you all, I'd just as soon take Robert's patches than > work on getting my bogus ones to work. Unless I hear otherwise, I'll > assume that's whats happening. Sure. I'm just waiting for his patches here too. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22894 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:11:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22882 for ; Tue, 4 Aug 1998 17:11:43 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA11489; Wed, 5 Aug 1998 09:41:15 +0930 (CST) Message-Id: <199808050011.JAA11489@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Taylor cc: freebsd-hackers@FreeBSD.ORG Subject: Re: couple of questions In-reply-to: Your message of "Tue, 04 Aug 1998 14:05:31 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 09:41:15 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - multi-disk file systems > > - in the chart he references Caldera having "md" - I'm not sure > what this is. Any ideas? My interpretation was say /usr on > 1 disk, /tmp on another or something, but I'm still waiting for > an answer. If it helps he has "volume sets" listed under NT and > ODM under SCO Unixware This is probably similar to the ccd device, which allows you to glue devices together (like software RAID). It can also do disk mirroring, but it won't recover automatically from an error or anything fancy like that. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:19:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24469 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:19:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24464 for ; Tue, 4 Aug 1998 17:19:11 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA14675; Tue, 4 Aug 1998 17:18:51 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd014595; Tue Aug 4 17:18:45 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA25335; Tue, 4 Aug 1998 17:18:36 -0700 (MST) From: Terry Lambert Message-Id: <199808050018.RAA25335@usr02.primenet.com> Subject: Re: Threaded X libs.. To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Wed, 5 Aug 1998 00:18:36 +0000 (GMT) Cc: kaleb@ics.com, doconnor@gsoft.com.au, hackers@FreeBSD.ORG In-Reply-To: from "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=" at Aug 4, 98 06:12:14 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Kaleb S. KEITHLEY" writes: > > When there's an officially released version of FreeBSD with threads, > > then I'm sure the default will be to enable threads in XFree86. > > Umm, as far as I can see from the CVS logs, FreeBSD has had threads > since 2.2.0. And working Draft 4 compliant threads since 2.2.6-stable. 8-). Although PTHREAD_MUTEX_INITIALIZER is now supported, I'm pretty sure 2.2.7 and 3.0-current aren't Draft 10/standard compliant yet. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:19:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24585 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:19:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24559 for ; Tue, 4 Aug 1998 17:19:29 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id UAA17176; Tue, 4 Aug 1998 20:29:49 -0400 (EDT) Date: Tue, 4 Aug 1998 20:29:49 -0400 (EDT) From: Charles Youse To: Nicolas Souchu cc: FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: <19980804185938.36803@breizh.prism.uvsq.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Nicolas Souchu wrote: > union foo_t { > int i; > char c; > void *p; > }; > > static union foo_t bar = { (void *)&anyvar }; If you wish to initialize these unions using void pointers, then the void pointer element comes first. Otherwise, you're stuck using casts, which aren't necessarily safe. C dictates that union initializations take the form of the first member of the union. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:20:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25111 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:20:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25086 for ; Tue, 4 Aug 1998 17:20:45 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id UAA17196; Tue, 4 Aug 1998 20:31:02 -0400 (EDT) Date: Tue, 4 Aug 1998 20:31:02 -0400 (EDT) From: Charles Youse To: Chuck Robey cc: Nicolas Souchu , FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Chuck Robey wrote: > No, you forgot to mention which union memeber to use. Your foo_t.p > would do nicely. That's not ANSI standard C. If GCC supports it, then fine but it won't be portable. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25379 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:22:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25315 for ; Tue, 4 Aug 1998 17:21:58 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA27889; Tue, 4 Aug 1998 17:21:46 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd027863; Tue Aug 4 17:21:39 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA25462; Tue, 4 Aug 1998 17:21:37 -0700 (MST) From: Terry Lambert Message-Id: <199808050021.RAA25462@usr02.primenet.com> Subject: Re: 2.2.7 crash during "monthly" maintenance batch To: brett@lariat.org (Brett Glass) Date: Wed, 5 Aug 1998 00:21:37 +0000 (GMT) Cc: dag-erli@ifi.uio.no, hackers@FreeBSD.ORG In-Reply-To: <199808041637.KAA03017@lariat.lariat.org> from "Brett Glass" at Aug 4, 98 10:36:51 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's yet more info. The system is a 486DX4/100 made by Zeos. 16 MB of RAM, > WD 2.5 GB IDE drive, Artisoft AE-3 network adapter (it's an NE2000 clone), > several multiport serial cards. I can post the output from dmesg if it'd > help. Worked like a champ up until the upgrade, is now rebooting spontaneously > when I run heavy-duty apps. Also rebooted during a kernel recompile. A number of the Artisoft cards running in 16 bit mode instead of8-bit mode were well known to have a byte-swap problem for the last byte of an odd length packet. The workaround was to either run in 8-bit mode, or to do the swap in the driver if you detected one of these cards (also to never send odd length packets). This could be related to the crash, if you are running a different driver. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:23:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25689 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:23:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25626 for ; Tue, 4 Aug 1998 17:22:53 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id UAA17208; Tue, 4 Aug 1998 20:33:07 -0400 (EDT) Date: Tue, 4 Aug 1998 20:33:06 -0400 (EDT) From: Charles Youse To: Brett Taylor cc: freebsd-hackers@FreeBSD.ORG Subject: Re: couple of questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Brett Taylor wrote: > - multi-disk file systems > > - in the chart he references Caldera having "md" - I'm not sure > what this is. Any ideas? My interpretation was say /usr on > 1 disk, /tmp on another or something, but I'm still waiting for > an answer. If it helps he has "volume sets" listed under NT and > ODM under SCO Unixware md refers to Linux's software RAID implementation. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26678 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:27:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26651 for ; Tue, 4 Aug 1998 17:27:18 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA11671; Wed, 5 Aug 1998 09:56:23 +0930 (CST) Message-Id: <199808050026.JAA11671@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=), kaleb@ics.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 00:18:36 GMT." <199808050018.RAA25335@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 09:56:22 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And working Draft 4 compliant threads since 2.2.6-stable. 8-). > Although PTHREAD_MUTEX_INITIALIZER is now supported, I'm pretty > sure 2.2.7 and 3.0-current aren't Draft 10/standard compliant yet. Hmm.. where could I find information on Draft xx standard? It would be nice to have a yardstick to measure the implementation by :) I got the patched MIT threads library which has more of the standard implemented.. Now to rebuild XFree86 against it (urgh..) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27959 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:33:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27838 for ; Tue, 4 Aug 1998 17:32:21 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA01953; Tue, 4 Aug 1998 17:32:08 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd001925; Tue Aug 4 17:32:04 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA25880; Tue, 4 Aug 1998 17:32:01 -0700 (MST) From: Terry Lambert Message-Id: <199808050032.RAA25880@usr02.primenet.com> Subject: Re: PAM4FreeBSD To: jdp@polstra.com (John Polstra) Date: Wed, 5 Aug 1998 00:32:01 +0000 (GMT) Cc: abial@nask.pl, hackers@FreeBSD.ORG In-Reply-To: <199808041736.KAA08122@austin.polstra.com> from "John Polstra" at Aug 4, 98 10:36:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been working on PAM for a client, and the client is willing > to donate the work to FreeBSD. I think any flaws in PAM are not too > serious, and can be fixed. I plan to bring it into -current when I > get the official go-ahead from my client. Be sure and look at BugTraq and the DOE CICE lists for the Solaris PAM vulnerabilities before bringing it all the way in (PAM accounts for approximately 2/3's of their recent vulnerabilities). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29570 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:41:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29515 for ; Tue, 4 Aug 1998 17:41:20 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA06276; Tue, 4 Aug 1998 17:41:07 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd006207; Tue Aug 4 17:40:56 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA26291; Tue, 4 Aug 1998 17:40:55 -0700 (MST) From: Terry Lambert Message-Id: <199808050040.RAA26291@usr02.primenet.com> Subject: Re: executables over NFS To: ben@rosengart.com Date: Wed, 5 Aug 1998 00:40:55 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Aug 4, 98 02:02:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are executables loaded over NFS treated the same as local executables > with regard to paging? Specifically, do they use the remote file as > backing store, or local swap space? They are treated as local files -- that is, first page-in is from the vnode, and subsequently aggressively cached, including page-out to local swap store in preference to discard, so subsequent page-in is from local swap store. The fact that a downed NFS server and/or modifications of a file on the NFS server (because the server doesn't know it's being used as a swap store) are my biggest gripes against memory overcommit. I have long been a proponent of an NFS mount option that would result in non-overcommit behaviour, ie: copy the pages to local swap store and mark them as non-discardable if you are executing an image from that FS. This was also my biggest gripe with dataless SunOS and Solaris installations as well, FWIW. One server crash, and forty engineers are twiddling their thumbs... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01719 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:52:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01713 for ; Tue, 4 Aug 1998 17:52:17 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA09936; Tue, 4 Aug 1998 17:52:06 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd009909; Tue Aug 4 17:52:02 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id RAA26979; Tue, 4 Aug 1998 17:52:01 -0700 (MST) From: Terry Lambert Message-Id: <199808050052.RAA26979@usr02.primenet.com> Subject: Re: C and static initialization with unions To: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu) Date: Wed, 5 Aug 1998 00:52:01 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980804185938.36803@breizh.prism.uvsq.fr> from "Nicolas Souchu" at Aug 4, 98 06:59:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A question about C and static initialization of unions: > > suppose, > > union foo_t { > int i; > char c; > void *p; > }; > > static union foo_t bar = { (void *)&anyvar }; > > The compiler says "warning, making integer from pointer without a cast"... > Which is true and could lead to bad asm code. > > Is there a way to do this properly? Should I forgive unions or what else? Put the largest possible type first, and cast to that. The real answer is that GCC is stupid about agregate initializations, and doesn't store more than one symbol type for the assign. Logically, one would expect: static union foo_t bar.p = { (void *)&anyvar }; to work, since the error for the code without an anyvar definition is: initializer element for `bar.i' is not constant So it "knows" about "bar.i" distinct from "bar". PS: Should you be posting this to comp.lang.c, or better yeat, reading the FAQ from comp.lang.c? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01725 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:52:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01707 for ; Tue, 4 Aug 1998 17:52:16 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA11928; Wed, 5 Aug 1998 10:21:50 +0930 (CST) Message-Id: <199808050051.KAA11928@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kaleb S. KEITHLEY" cc: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Tue, 04 Aug 1998 17:57:14 GMT." <35C74B7A.42031494@ics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 05 Aug 1998 10:21:50 +0930 From: "Daniel O'Connor" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA01718 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FWIW, trying to keep up with FreeBSD releases and get work done at the > same time is getting a bit too much like keeping up with Linux releases. > At this point I'd rather see __the__ 3.0 release than another 2.x > release. Well, one more to go (2.2.8) then 3.0 will be released (sometime near my birthday.. what a present ;) Jordan did post a release schedule but I can't find it in the archives :-/ --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 17:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02807 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 17:58:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02795 for ; Tue, 4 Aug 1998 17:58:52 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id RAA13063; Tue, 4 Aug 1998 17:58:39 -0700 (PDT) (envelope-from jdp) Message-Id: <199808050058.RAA13063@austin.polstra.com> To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-reply-to: Your message of "Wed, 05 Aug 1998 00:32:01 -0000." <199808050032.RAA25880@usr02.primenet.com> Date: Tue, 04 Aug 1998 17:58:39 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Be sure and look at BugTraq and the DOE CICE lists for the Solaris > PAM vulnerabilities before bringing it all the way in (PAM accounts > for approximately 2/3's of their recent vulnerabilities). Will do. Thanks for the tip. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03701 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:03:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03695 for ; Tue, 4 Aug 1998 18:03:29 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA20773; Tue, 4 Aug 1998 18:03:18 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd020736; Tue Aug 4 18:03:16 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id SAA27705; Tue, 4 Aug 1998 18:03:14 -0700 (MST) From: Terry Lambert Message-Id: <199808050103.SAA27705@usr02.primenet.com> Subject: Re: C and static initialization with unions To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 5 Aug 1998 01:03:14 +0000 (GMT) Cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Aug 4, 98 03:09:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > union foo_t { > > int i; > > char c; > > void *p; > > }; > > > > static union foo_t bar = { (void *)&anyvar }; > > No, you forgot to mention which union memeber to use. Your foo_t.p > would do nicely. 1) This is a vendor extension. 2) That vendor isn't FSF or Cygnus. 3) It's "foo_t bar.p", not "foo_t.p bar". 4) It still breaks for: typedef enum { UT_INT, UT_CHAR, UT_PTR } ut_t; typedef struct { ut_t u_type; struct foo_t u; /* someone blew a typedef*/ } bob_t; bob_t bobs.p[] = { { UT_PTR, &anyvar }, { UT_INT, 35 }, /* oops!*/ { UT_PTR, NULL } }; Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04616 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:08:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04610 for ; Tue, 4 Aug 1998 18:08:15 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA13177; Tue, 4 Aug 1998 18:08:04 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd013140; Tue Aug 4 18:07:54 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id SAA27977; Tue, 4 Aug 1998 18:07:52 -0700 (MST) From: Terry Lambert Message-Id: <199808050107.SAA27977@usr02.primenet.com> Subject: Re: Threaded X libs.. To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 5 Aug 1998 01:07:52 +0000 (GMT) Cc: kaleb@ics.com, hackers@FreeBSD.ORG In-Reply-To: <199808042345.JAA11220@cain.gsoft.com.au> from "Daniel O'Connor" at Aug 5, 98 09:15:32 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm.. worked for me quite easily, I just added the following lines to the work/ > #define ThreadsLibraries -pthread ^^^^^^^^ I don't believe you. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:11:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05108 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:11:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05103 for ; Tue, 4 Aug 1998 18:11:18 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id SAA13166; Tue, 4 Aug 1998 18:11:05 -0700 (PDT) (envelope-from jdp) Message-Id: <199808050111.SAA13166@austin.polstra.com> To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-reply-to: Your message of "Wed, 05 Aug 1998 00:32:01 -0000." <199808050032.RAA25880@usr02.primenet.com> Date: Tue, 04 Aug 1998 18:11:05 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Be sure and look at BugTraq and the DOE CICE lists OK, I give up. Yahoo has failed me. Altavista has let me down. What's a "DOE CICE" and where do I find it? :-} John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:12:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05397 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:12:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05335 for ; Tue, 4 Aug 1998 18:12:01 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA01993; Tue, 4 Aug 1998 18:11:49 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma001991; Tue Aug 4 18:11:43 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA10720; Tue, 4 Aug 1998 18:11:43 -0700 (PDT) From: Archie Cobbs Message-Id: <199808050111.SAA10720@bubba.whistle.com> Subject: Re: C and static initialization with unions In-Reply-To: <199808042227.SAA16749@lakes.dignus.com> from Thomas David Rivers at "Aug 4, 98 06:27:34 pm" To: rivers@dignus.com (Thomas David Rivers) Date: Tue, 4 Aug 1998 18:11:43 -0700 (PDT) Cc: chuckr@glue.umd.edu, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, One non-portable nicety of gcc is that you can do this: union foo { int iarg; char carg; }; static union foo x = { carg: 12 }; -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06098 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:16:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06075 for ; Tue, 4 Aug 1998 18:16:44 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA12154; Wed, 5 Aug 1998 10:46:21 +0930 (CST) Message-Id: <199808050116.KAA12154@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 01:07:52 GMT." <199808050107.SAA27977@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 10:46:20 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm.. worked for me quite easily, I just added the following lines to the w > ork/ > > #define ThreadsLibraries -pthread > I don't believe you. 8-). Hah.. man pthread for you :) At least on -current anyway.. Checking a -stable machine reveals that gcc hasn't been patched for it :) OK, so change it to -lc_r on -stable.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09279 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:41:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09268 for ; Tue, 4 Aug 1998 18:41:08 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id VAA24233; Tue, 4 Aug 1998 21:40:47 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id WAA03564; Tue, 4 Aug 1998 22:13:42 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id VAA17156; Tue, 4 Aug 1998 21:44:52 -0400 (EDT) Date: Tue, 4 Aug 1998 21:44:52 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808050144.VAA17156@lakes.dignus.com> To: chuckr@glue.umd.edu, rivers@dignus.com Subject: Re: C and static initialization with unions Cc: freebsd-hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Tue, 4 Aug 1998, Thomas David Rivers wrote: > > > Also - you should be aware that ANSI forbids assigning to one element > > of a union and referencing a different element. (Basically, the > > 'type-punning' problem) C compilers are allowed to optimize field > > references based on type; so that: > > > > main() > > { > > union foo_t foo; > > void *vp; > > > > foo.i = 5; > > foo.p = 0; > > > > if(foo.i) { > > printf("true\n"); > > } else { > > printf("false\n"); > > } > > } > > > > may, depending on the optimizer, print either true or false. Technically, > > this is an invalid ANSI C program. > > I never saw that, and I think you may be wrong, so if you have the ansi > standard lying around, give me a quote, ok? Harbison & Steele says, on > page 132-133, that doing what you said above is non-portable (I agree), > but programmers "sometimes do this to 'reach under' C's type system > ...". There was more, but I'm sure you know it already. > > It's in there; believe me (I'm the manager for C/C++ compiler development at SAS Institute...) The ANSI C standard, section 3.3.2.4 says: "With one exception, if a member of a union object is accessed after a value has been stored in a different member of the object, the behaviour is implementation-defined." [The exception is to allow for a "common initial sequence" in which the union contains structures whose first fields are compatible types. We're note dealing with compatible types, or structures, in this example, so the exception clearly does not apply.] Furthermore, section 3.3 specifies: "An object shall have its stored value accessed only by an lvalue that has one of the following types: o) The declared type of the object o) a qualified version of the declared type of the object o) a type that is the signed or unsigned type corresponding to the declared type of the object ... The point of this particular definition (per the footnote in the standard) is to list exactly when an object may be considered to be aliased. This, the following code is non-ANSI, and may produce surprising results: char *cp; int i; i = 5; cp = (char *)&i; *cp = 0x80; /* 'i' is being incorrectly referenced */ printf("i is 0x%x", i); An ANSI conforming implementation would be correct in generating the output i is 5 as the compiler, per the rules above, doesn't have to note the aliasing that occured when the stored value of 'i' was incorrectly referenced. In fact, the entire purpose of the list in section 3.3 of the standard is to allow optimizers to do just that (type based aliasing) which can be a big win for code generation. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 18:51:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11151 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 18:51:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11146 for ; Tue, 4 Aug 1998 18:51:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA01073; Tue, 4 Aug 1998 18:49:28 -0700 (PDT) Message-Id: <199808050149.SAA01073@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: chuckr@glue.umd.edu (Chuck Robey), Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Wed, 05 Aug 1998 01:03:14 -0000." <199808050103.SAA27705@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 18:49:27 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > union foo_t { > > > int i; > > > char c; > > > void *p; > > > }; > > > > > > static union foo_t bar = { (void *)&anyvar }; > > > > No, you forgot to mention which union memeber to use. Your foo_t.p > > would do nicely. > > 1) This is a vendor extension. > > 2) That vendor isn't FSF or Cygnus. > > 3) It's "foo_t bar.p", not "foo_t.p bar". > > 4) It still breaks for: > > typedef enum { UT_INT, UT_CHAR, UT_PTR } ut_t; > > typedef struct { > ut_t u_type; > struct foo_t u; /* someone blew a typedef*/ > } bob_t; > > bob_t bobs.p[] = { > { UT_PTR, &anyvar }, > { UT_INT, 35 }, /* oops!*/ > { UT_PTR, NULL } > }; > The gcc info "extensions/named elements" section describes a useful extension that lets you cut through much of this crap. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:15:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14868 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:15:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14844 for ; Tue, 4 Aug 1998 19:15:32 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA04763; Tue, 4 Aug 1998 19:15:16 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd004719; Tue Aug 4 19:15:08 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA01844; Tue, 4 Aug 1998 19:15:04 -0700 (MST) From: Terry Lambert Message-Id: <199808050215.TAA01844@usr02.primenet.com> Subject: Re: couple of questions To: maex-freebsd-hackers@Space.Net (Markus Stumpf) Date: Wed, 5 Aug 1998 02:15:04 +0000 (GMT) Cc: brett@peloton.physics.montana.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980805004942.L12619@space.net> from "Markus Stumpf" at Aug 5, 98 00:49:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > - maximum file/partition size: > > > > - I've seen files (from an ls -l emailed to me) of ~ 7 GB, but > > I'm not sure what the absolute maximum file size is. Is there > > a hard limit? > > Hmmm ... this is from man 2 intro (2.2.6-RELEASE) > > > 27 EFBIG File too large. The size of a file exceeded the maximum (about > > 2.1E9 bytes). > > This is 2 GB, right? But I've heard NetBSD has bigger files. > > \Maex > > N.B. This 2 GB always hits me with backups of large partitions that don't > compress well. Still using amanda-2.3.0, however, amanda-2.4.0 is able > to handle this with artificial splits. The size limit is 549755813888 -- that's (u_quad_t) 1 << 39, or 512 Gig. The limit is a result of a 32 bit block number limitation in the file /usr/src/sbin/newfs.c.\, which in turn is because the on disk fs_size and fs_dsize are stored as int32_t. The size limit is also the size limit for an FS: /* XXX - hack to prevent overflow of a 32bit block number */ sblock.fs_maxfilesize = MIN(sblock.fs_maxfilesize, (u_quad_t) 1 << 39); The size may be further reduced if there are insufficient blocks available to support triple indirect blocks, or double indirect blocks. This number is actually incorrect; 2^31 (1 bit for sign; indirect blocks are internally implemented using negative block offsets to indicate they reference an indirect block) times 2^12 (blocks in this case are 4096 bytes, the minimum FS block size). Assuming this change, and a number of small patches to prevent 32 bit field overflow in the physical block calculation, this puts the number at 8TB for a 4k block size and 16TB for an 8k block size (2^33 and 2^34, respectively). The patches have been available for some time; I believe they were first posted a year or so ago by someone building a huge CCD array at UC Berkeley (Satoshi Asami, maybe?). I believe they haven't been incorporated because > 32 bit calculations for physical (not FS) blocks would slow things down (even then, the 39 is 2^31 * 2^8; physical blocks are 2^9, which should put the FS smack on the 1TB mark). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15010 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:16:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14887 for ; Tue, 4 Aug 1998 19:16:03 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA02306; Tue, 4 Aug 1998 21:12:40 -0400 (EDT) Date: Tue, 4 Aug 1998 21:12:40 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Thomas David Rivers cc: freebsd-hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr Subject: Re: C and static initialization with unions In-Reply-To: <199808050144.VAA17156@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Thomas David Rivers wrote: > > > > On Tue, 4 Aug 1998, Thomas David Rivers wrote: > > > > > Also - you should be aware that ANSI forbids assigning to one element > > > of a union and referencing a different element. (Basically, the > > > 'type-punning' problem) C compilers are allowed to optimize field > > > references based on type; so that: > > > > > > main() > > > { > > > union foo_t foo; > > > void *vp; > > > > > > foo.i = 5; > > > foo.p = 0; > > > > > > if(foo.i) { > > > printf("true\n"); > > > } else { > > > printf("false\n"); > > > } > > > } > > > > > > may, depending on the optimizer, print either true or false. Technically, > > > this is an invalid ANSI C program. > > > > I never saw that, and I think you may be wrong, so if you have the ansi > > standard lying around, give me a quote, ok? Harbison & Steele says, on > > page 132-133, that doing what you said above is non-portable (I agree), > > but programmers "sometimes do this to 'reach under' C's type system > > ...". There was more, but I'm sure you know it already. > > > > > > It's in there; believe me (I'm the manager for C/C++ compiler development > at SAS Institute...) > > The ANSI C standard, section 3.3.2.4 says: > > "With one exception, if a member of a union object is accessed after > a value has been stored in a different member of the object, the > behaviour is implementation-defined." And you _seem_ to have made my argument ... you said ANSI forbids it, you even quoted yourself above, but your quotation from the standard says it's implementation-defined. That means it's legal, but undefined behavior. For any reasonable shop making software for sale, they may mean the same thing, but for someone doing one-off controllers, the operation is clearly legal, and the programmer is clearly warned that they had better know what they're doing, because it's not going to be portable. I'm making a distinction between "forbids" (which I take to mean that the compiler must catch it and cause a fatal error) and "non-portable" (which I take to mean that any reasonable compiler should issue a warning, and no public shop should use). That's my argument, if that's wrong, then I'm completely wrong. > > [The exception is to allow for a "common initial sequence" in which > the union contains structures whose first fields are compatible types. > We're note dealing with compatible types, or structures, in this > example, so the exception clearly does not apply.] > > Furthermore, section 3.3 specifies: > > "An object shall have its stored value accessed only by an lvalue > that has one of the following types: > > o) The declared type of the object > o) a qualified version of the declared type of the object > o) a type that is the signed or unsigned type corresponding to the > declared type of the object > ... > > The point of this particular definition (per the footnote in the > standard) is to list exactly when an object may be considered to be > aliased. > > This, the following code is non-ANSI, and may produce surprising > results: > > char *cp; > int i; > > i = 5; > cp = (char *)&i; > *cp = 0x80; /* 'i' is being incorrectly referenced */ > printf("i is 0x%x", i); > > An ANSI conforming implementation would be correct in generating the > output > i is 5 > as the compiler, per the rules above, doesn't have to note the aliasing > that occured when the stored value of 'i' was incorrectly referenced. > > In fact, the entire purpose of the list in section 3.3 of the standard > is to allow optimizers to do just that (type based aliasing) which > can be a big win for code generation. > > - Dave Rivers - > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17141 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:25:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17118 for ; Tue, 4 Aug 1998 19:25:18 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA28283; Tue, 4 Aug 1998 19:25:02 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd028253; Tue Aug 4 19:24:58 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA02476; Tue, 4 Aug 1998 19:24:53 -0700 (MST) From: Terry Lambert Message-Id: <199808050224.TAA02476@usr02.primenet.com> Subject: Re: Threaded X libs.. To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 5 Aug 1998 02:24:53 +0000 (GMT) Cc: tlambert@primenet.com, dag-erli@ifi.uio.no, kaleb@ics.com, hackers@FreeBSD.ORG In-Reply-To: <199808050026.JAA11671@cain.gsoft.com.au> from "Daniel O'Connor" at Aug 5, 98 09:56:22 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And working Draft 4 compliant threads since 2.2.6-stable. 8-). > > Although PTHREAD_MUTEX_INITIALIZER is now supported, I'm pretty > > sure 2.2.7 and 3.0-current aren't Draft 10/standard compliant yet. > > Hmm.. where could I find information on Draft xx standard? It would > be nice to have a yardstick to measure the implementation by :) Join a POSIX committee. 8-). The information is available in the O'Reilly Pthreads book, which has a section on the differences between the standard and Draft 4. The lack of PTHREAD_MUTEX_INITIALIZER generally indicates a Draft 4 implementation (the most widely implemented Draft, other than Draft 10, which is what was standardized). The bad thing about this is that if FreeBSD is not full standard, then things are not very nice; much code has been written using: #ifndef PTHREAD_MUTEX_INITIALIZER /* use Draft 4 semantics and calling conventsion*/ #else /* use Standard semantics and calling conventsion*/ #endif If FreeBSD is not full Standard, than this code will now break; the PTHREAD_MUTEX_INITIALIZER (and the attr argument to pthread_create) should have been the last things changes when Standard compliance became reality). 8-(. > I got the patched MIT threads library which has more of the standard > implemented.. Now to rebuild XFree86 against it (urgh..) Bad plan. The default FreeBSD libc is not threads safe for user space threads. This means that the code will appear to work, but won't really work. The FreeBSD libc_r overrides system call definitions, as well, instead of merely adding pthreads functions. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19039 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:36:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19034 for ; Tue, 4 Aug 1998 19:36:06 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA02346; Tue, 4 Aug 1998 21:34:12 -0400 (EDT) Date: Tue, 4 Aug 1998 21:34:12 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Charles Youse cc: Nicolas Souchu , FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Charles Youse wrote: > > > On Tue, 4 Aug 1998, Chuck Robey wrote: > > > No, you forgot to mention which union memeber to use. Your foo_t.p > > would do nicely. > > That's not ANSI standard C. If GCC supports it, then fine but it won't be > portable. Read my original post, where I said that it wasn't portable, but it's _not_ forbidden! There's a difference, guys! > > Chuck > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20360 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:49:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20340 for ; Tue, 4 Aug 1998 19:49:14 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA12918; Wed, 5 Aug 1998 12:17:52 +0930 (CST) Message-Id: <199808050247.MAA12918@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: doconnor@gsoft.com.au (Daniel O'Connor), dag-erli@ifi.uio.no, kaleb@ics.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 02:24:53 GMT." <199808050224.TAA02476@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 12:17:48 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm.. where could I find information on Draft xx standard? It would > > be nice to have a yardstick to measure the implementation by :) > Join a POSIX committee. 8-). Oh yes :) > The information is available in the O'Reilly Pthreads book, which has > a section on the differences between the standard and Draft 4. Aha.. Hmm.. might be an intersting read.. I wonder if my student card still works at uni =) > If FreeBSD is not full Standard, than this code will now break; the > PTHREAD_MUTEX_INITIALIZER (and the attr argument to pthread_create) > should have been the last things changes when Standard compliance > became reality). 8-(. Doh :-/ Oh well, it just means that we'll have to get around to implementing it all ;) > > I got the patched MIT threads library which has more of the standard > > implemented.. Now to rebuild XFree86 against it (urgh..) > Bad plan. The default FreeBSD libc is not threads safe for user space > threads. This means that the code will appear to work, but won't really > work. The FreeBSD libc_r overrides system call definitions, as well, > instead of merely adding pthreads functions. Yes, but I thought the whole point of the MIT pthreads package was that it overrides the system calls which aren't thread safe, with threadable wrappers. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20875 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:52:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20863 for ; Tue, 4 Aug 1998 19:52:10 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA16353; Tue, 4 Aug 1998 19:51:59 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd016311; Tue Aug 4 19:51:58 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA04173; Tue, 4 Aug 1998 19:51:56 -0700 (MST) From: Terry Lambert Message-Id: <199808050251.TAA04173@usr02.primenet.com> Subject: Re: PAM4FreeBSD To: jdp@polstra.com (John Polstra) Date: Wed, 5 Aug 1998 02:51:56 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199808050111.SAA13166@austin.polstra.com> from "John Polstra" at Aug 4, 98 06:11:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Be sure and look at BugTraq and the DOE CICE lists > > OK, I give up. Yahoo has failed me. Altavista has let me down. > > What's a "DOE CICE" and where do I find it? :-} Ugh. CIAC. The US Department Of Energy Computer Incident Advisory Capability. http://ciac.llnl.gov/cgi-bin/index/bulletins Sorry about that. Note that the incidents reported here are listed mostly under the programs compromized by them, and don't (usually) explicitly reference PAM (instead they reference things like NIS+ cache compromise", etc.). The Bugtraq stuff is at: http://www.geek-girl.com/bugtraq/ These reference PAM explicitly. You should include CERT in the list, as well, while I'm at it... http://www.cert.org/nav/alerts.html ...what the heck, you might as well add: http://www.secnet.com/nav1.html They don't have anything on PAM, but they have an lpd vunlerability in FreeBSD 2.1.7 listed... as well as one against Vixie's cron. 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 19:59:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22031 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:59:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22026 for ; Tue, 4 Aug 1998 19:59:53 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA09184; Tue, 4 Aug 1998 19:59:36 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd009166; Tue Aug 4 19:59:35 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA04741; Tue, 4 Aug 1998 19:59:33 -0700 (MST) From: Terry Lambert Message-Id: <199808050259.TAA04741@usr02.primenet.com> Subject: Re: C and static initialization with unions To: rivers@dignus.com (Thomas David Rivers) Date: Wed, 5 Aug 1998 02:59:33 +0000 (GMT) Cc: chuckr@glue.umd.edu, rivers@dignus.com, freebsd-hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: <199808050144.VAA17156@lakes.dignus.com> from "Thomas David Rivers" at Aug 4, 98 09:44:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's in there; believe me (I'm the manager for C/C++ compiler development > at SAS Institute...) FreeBSD port of all SAS language tools... when? 8-) 8-). > An ANSI conforming implementation would be correct in generating the > output > i is 5 > as the compiler, per the rules above, doesn't have to note the aliasing > that occured when the stored value of 'i' was incorrectly referenced. Any opportunity for a language construct that lets them backhandedly bitch about the exclusion of "noalias", just because humans have to be able to follow the code and the "volatile" people got their baby in and it has the same type of "tell the compiler how to compile using the source code instead of it figuring it out for itself" logic... 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 20:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24125 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 20:12:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24118 for ; Tue, 4 Aug 1998 20:12:44 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id VAA11945; Tue, 4 Aug 1998 21:12:14 -0600 (MDT) Message-Id: <199808050312.VAA11945@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 21:11:58 -0600 To: Terry Lambert From: Brett Glass Subject: Re: 2.2.7 crash during "monthly" maintenance batch Cc: dag-erli@ifi.uio.no, hackers@FreeBSD.ORG In-Reply-To: <199808050021.RAA25462@usr02.primenet.com> References: <199808041637.KAA03017@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why would this suddenly start affecting us when we moved from 2.2.2 to 2.2.7? That part of the "ed" driver has not changed much. Also, doubt that this would cause the whole system to reboot spontaneously after nearly a day of working fine (and passing heavy Internet traffic). Now, using the extended memory range of the Artisoft card (by plugging in bigger static RAM chips) WOULD break the driver. I will eventually figure out what it's doing and send in a patch. --Brett At 12:21 AM 8/5/98 +0000, Terry Lambert wrote: >> Here's yet more info. The system is a 486DX4/100 made by Zeos. 16 MB of RAM, >> WD 2.5 GB IDE drive, Artisoft AE-3 network adapter (it's an NE2000 clone), >> several multiport serial cards. I can post the output from dmesg if it'd >> help. Worked like a champ up until the upgrade, is now rebooting spontaneously >> when I run heavy-duty apps. Also rebooted during a kernel recompile. > >A number of the Artisoft cards running in 16 bit mode instead of8-bit >mode were well known to have a byte-swap problem for the last byte >of an odd length packet. > >The workaround was to either run in 8-bit mode, or to do the swap in >the driver if you detected one of these cards (also to never send odd >length packets). > >This could be related to the crash, if you are running a different >driver. > > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 20:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25088 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 20:18:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24999 for ; Tue, 4 Aug 1998 20:17:58 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id XAA17513; Tue, 4 Aug 1998 23:28:15 -0400 (EDT) Date: Tue, 4 Aug 1998 23:28:15 -0400 (EDT) From: Charles Youse To: Chuck Robey cc: Nicolas Souchu , FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Chuck Robey wrote: > Read my original post, where I said that it wasn't portable, but it's > _not_ forbidden! There's a difference, guys! Oh yeah?!? Oh yeah?!? Well... urm.. uh... pull my finger! }:> I missed that part of your post. My apologies . . . Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 20:31:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27404 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 20:31:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27399 for ; Tue, 4 Aug 1998 20:31:37 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id WAA02452; Tue, 4 Aug 1998 22:29:54 -0400 (EDT) Date: Tue, 4 Aug 1998 22:29:53 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Charles Youse cc: Nicolas Souchu , FreeBSD Hackers Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Charles Youse wrote: > > > On Tue, 4 Aug 1998, Chuck Robey wrote: > > > Read my original post, where I said that it wasn't portable, but it's > > _not_ forbidden! There's a difference, guys! > > Oh yeah?!? Oh yeah?!? Well... urm.. uh... pull my finger! }:> > > I missed that part of your post. My apologies . . . I think I'm unclear here. I said it was non-portable, I didn't say it was forbidden (Thomas added that, which I disputed). I _think_ the standard says it's not defined, but all I have to go on here is H&S, which I like a lot better than K&R. >From Thomas' viewpoint, where he's writing software destined for multiple platforms, it's very easy to see his point of view, which I think is non-portable == forbidden. My point of view was writing one-off custom controllers, where anything that works and is debuggable is just fine. > > Chuck > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 21:39:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06895 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 21:39:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles85.castles.com [208.214.165.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06890 for ; Tue, 4 Aug 1998 21:39:26 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00535; Tue, 4 Aug 1998 21:38:06 -0700 (PDT) Message-Id: <199808050438.VAA00535@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Iani Brankov" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Want to write support for PCI variant of the arc0 driver. Help with info :) In-reply-to: Your message of "Wed, 05 Aug 1998 00:27:34 +0300." <000301bdbfee$b3140fc0$17b448c0@ian.oksys.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 21:38:05 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > we've bought a Digiboard 570 pci sync card, which isn't supported > by FreeBSD. There's support for the ISA variant only. > > The PCI card is almost the same and I'll try to write a pci > routines to detect and attach the pci card to the existing ISA > driver. (as i see it runs the same way). > > I need some information. Can I find some documentation > how to write a driver (pci, isa) for FreeBSD. Your best bet is to look at another driver that behaves like this (eg. if_ed_p). The code is really quite simple. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 21:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08267 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 21:52:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles85.castles.com [208.214.165.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08255 for ; Tue, 4 Aug 1998 21:52:28 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00618; Tue, 4 Aug 1998 21:51:25 -0700 (PDT) Message-Id: <199808050451.VAA00618@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Taylor cc: freebsd-hackers@FreeBSD.ORG Subject: Re: couple of questions In-reply-to: Your message of "Tue, 04 Aug 1998 14:05:31 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 21:51:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > - maximum file/partition size: > > - I've seen files (from an ls -l emailed to me) of ~ 7 GB, but > I'm not sure what the absolute maximum file size is. Is there > a hard limit? > - digging through the -current mailing list archive I found a note > from John Dyson saying the maximum partition size was 512 GB. > Is this still true (the note was from 97) and if so does it also > apply to 2.2.7? As previously discussed, the current cap is at 512GB. > - swap partitions > > - what's the maximum swap partition size? I seem to recall > reading on -current about someone w/ a 1 GB swap partition, but > my memory has been known to be faulty. Swap calculations are generally performed using signed integers to contain block numbers, so total swap appears limited to about 2^31 * 512 bytes (1TB if my mental shifting is correct). The partition limit size is the same for swap partitions. > - what's the maximum number of swap partitions you can have? The system default is to support 4 swap partitions, however this can be tuned with the NSWAPDEV kernel option. There does not appear to be a trivial limit; the hard limit would be around 2^31 again. > - multi-disk file systems > > - in the chart he references Caldera having "md" - I'm not sure > what this is. Any ideas? My interpretation was say /usr on > 1 disk, /tmp on another or something, but I'm still waiting for > an answer. If it helps he has "volume sets" listed under NT and > ODM under SCO Unixware FreeBSD supports the 'ccd' software RAID0/1 implementation, and a new implementation of same named Vinum is under development. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 21:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09285 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 21:59:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles85.castles.com [208.214.165.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09273 for ; Tue, 4 Aug 1998 21:59:09 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00654; Tue, 4 Aug 1998 21:58:01 -0700 (PDT) Message-Id: <199808050458.VAA00654@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Polstra cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-reply-to: Your message of "Tue, 04 Aug 1998 17:58:39 PDT." <199808050058.RAA13063@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 21:58:00 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Be sure and look at BugTraq and the DOE CICE lists for the Solaris > > PAM vulnerabilities before bringing it all the way in (PAM accounts > > for approximately 2/3's of their recent vulnerabilities). > > Will do. Thanks for the tip. ... and if you want my pet peeve about PAM, it's that the modules have to be visible and loadable in to the application that wants to authenticate/admin/etc. The "right" way (IMHO) to deal with this would be to take a clean slice across the PAM API (which is reasonably compact), encapsulate it into a nice simple synchronous stream protocol, and then put all the PAM library into a daemon. Use our authenticated socket technology and Unix-domain sockets to ensure the integrity of the client-server relationship. This would allow lots of programs (eg. passwd, xlockmore) to be installed non-setuid root, since they only ever authenticate their owner. It would also let you run eg. POP daemons non-setuid-root if they were granted permission to authenticate, etc. Anyway, that's my major gripe about PAM as it stands. That, and the lousy quality of most of the free-source modules out there. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 21:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09294 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 21:59:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09277 for ; Tue, 4 Aug 1998 21:59:11 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA07690; Tue, 4 Aug 1998 21:56:00 -0700 (PDT) Message-Id: <199808050456.VAA07690@implode.root.com> To: Terry Lambert cc: ben@rosengart.com, hackers@FreeBSD.ORG Subject: Re: executables over NFS In-reply-to: Your message of "Wed, 05 Aug 1998 00:40:55 -0000." <199808050040.RAA26291@usr02.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 04 Aug 1998 21:56:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Are executables loaded over NFS treated the same as local executables >> with regard to paging? Specifically, do they use the remote file as >> backing store, or local swap space? > >They are treated as local files -- that is, first page-in is from >the vnode, and subsequently aggressively cached, including page-out >to local swap store in preference to discard, so subsequent page-in >is from local swap store. That is not true. In no case will vnode-backed pages be paged out to swap. The only case where VM could start out as vnode backed and end up in swap is after a COW, in which case a swap-backed page is created. This behavior is not modified by the underlying file system type. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 22:06:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10912 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 22:06:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10907 for ; Tue, 4 Aug 1998 22:06:37 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id WAA14516; Tue, 4 Aug 1998 22:06:11 -0700 (PDT) (envelope-from jdp) Message-Id: <199808050506.WAA14516@austin.polstra.com> To: Mike Smith cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-reply-to: Your message of "Tue, 04 Aug 1998 21:58:00 PDT." <199808050458.VAA00654@antipodes.cdrom.com> Date: Tue, 04 Aug 1998 22:06:11 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... and if you want my pet peeve about PAM, it's that the modules > have to be visible and loadable in to the application that wants to > authenticate/admin/etc. > > The "right" way (IMHO) to deal with this would be to take a clean > slice across the PAM API (which is reasonably compact), encapsulate > it into a nice simple synchronous stream protocol, and then put > all the PAM library into a daemon. Use our authenticated socket > technology and Unix-domain sockets to ensure the integrity of the > client-server relationship. > > This would allow lots of programs (eg. passwd, xlockmore) to be > installed non-setuid root, since they only ever authenticate their > owner. It would also let you run eg. POP daemons non-setuid-root if > they were granted permission to authenticate, etc. I agree with you -- this is the way to go. > Anyway, that's my major gripe about PAM as it stands. That, and the > lousy quality of most of the free-source modules out there. 8( Man, that's no lie! I couldn't convince myself comfortably that any of the ones in the Linux-PAM distribution would work right under FreeBSD. I ended up rolling my own. There are lots of things about the exising implementation that rather stink. But as you said, the API isn't too bad. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 22:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14900 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 22:42:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ccvp.com ([207.66.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14783 for ; Tue, 4 Aug 1998 22:42:09 -0700 (PDT) (envelope-from robert@usamd.com) Received: from usamd.com ([207.66.33.213]) by ccvp.com (8.8.3/8.8.3) with ESMTP id XAA13770 for ; Tue, 4 Aug 1998 23:42:28 -0600 (MDT) Message-ID: <35C844FC.81E59896@usamd.com> Date: Wed, 05 Aug 1998 05:41:48 -0600 From: Robert X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: WatchGuard vs CISCO Pix? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Need to recommend firewall to government facility need to know pros and cons. WatchGuard vs CISCO Pix. Thanks R -- Download our price list at ftp://207.66.33.212/pub/readme/ Visit our web site at http://www.usamd.com Robert Clark USA Microdynamics PO Box 13569 Albuquerque, NM 87192-3569 Phone 505 275-0188 Fax 505 275-8708 sales@usamd.com info@usamd.com support@usamd.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 22:48:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16151 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 22:48:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16103; Tue, 4 Aug 1998 22:48:36 -0700 (PDT) (envelope-from wpaul) From: Bill Paul Message-Id: <199808050548.WAA16103@hub.freebsd.org> Subject: Re: Etherlink XL driver In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Aug 4, 98 06:16:24 pm" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Tue, 4 Aug 1998 22:48:34 -0700 (PDT) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, mike@smith.net.au X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > > The Etherlink XL driver seems to be working fine. How about committing > > > it to -current and removing the XL probe/attach code from the vx > > > driver? > > The fact that Bill hasn't committed it already tends to indicate he's > > still in testing. I wouldn't want to rush him *too* much. 8) > > Well, this is what -current is for, after all. And considering that > noone has reported any serious trouble so far, and that there is a > fallback driver (vx) in case problems arise, I don't see any reason > not to commit it. > Putting code in -current when you know there's something wrong with it is just... well, wrong. And I know there's at least one bug in the XL driver. I knew there were two until tonight, but I just fixed one. (Unfortunately, it was a problem I could not reproduce in the lab with the hardware that I have: the MII access code had a problem somewhere which caused it to fail to read any PHY registers on certain boards which a) report a PCI revision of 0 and b) were installed on relatively slow machines. Unfortunately, my 3c905B is integrated onto the motherboard of a 400Mhz PII, which makes it hard to move it to a slower machine. To compound matters, the problem card and its owner are in Brazil. Fortunately, the gentleman who owns (Hi Rodolfo!) it was able to give me access to the system via ssh and I was able to debug the problem using a hastily contrived LKM.) The remaining problem is that I know of at least one 3c900 board that doesn't work right. (Incidentally, since this is going to -hackers: if you're having a problem with the XL driver generating an error message that says 'MII without any PHY!' and you have a 3c905B card, please grab the latest version of the driver from www.freebsd.org/~wpaul/3Com and let me know if the problem goes away.) The -current branch may be bleeding edge, but I don't feel that means that I shouldn't try my best to work out all the bugs before I commit new code to it, which is what I'm doing, at least when I'm not being interrupted by Real Work (tm). That said, my plan is to commit the 3.0 version to -current sometime next week. After a couple more weeks there, I'll commit the 2.2 version. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 23:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22759 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 23:33:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl ([148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22739 for ; Tue, 4 Aug 1998 23:32:51 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id IAA28494; Wed, 5 Aug 1998 08:35:43 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 5 Aug 1998 08:35:42 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-Reply-To: <199808041736.KAA08122@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, John Polstra wrote: > I have been working on PAM for a client, and the client is willing > to donate the work to FreeBSD. I think any flaws in PAM are not too > serious, and can be fixed. I plan to bring it into -current when I > get the official go-ahead from my client. Hey, that's great news! I'm willing to write some auth modules when it's done... > > There is already existing framework of *CAP_AUTH, which was meant to be > > used together with login_* modules. Is it dead or something? If it's dead, > > let's bury its remains, and if not - let's start to write login_* modules. > > I looked at that stuff, and I want to remove it. It is very poorly > defined even in BSD/OS, whence it came. Also it is inferior to Good. Thus far, it was only causing confusion with no benefits. Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 23:36:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23816 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 23:36:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (port42.prairietech.net [208.141.230.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23787 for ; Tue, 4 Aug 1998 23:36:34 -0700 (PDT) (envelope-from alk@pobox.com) Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id BAA08699; Wed, 5 Aug 1998 01:37:29 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 Aug 1998 01:37:28 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: hackers@FreeBSD.ORG Subject: building 1.2.x motif dynamic libs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13767.64813.577243.247964@compound.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pretty sure someone else has done the imake hackery to build motif 1.2.x dynamic libraries for FreeBSD. (It's a morass which I would prefer to gloss.) If you're that special someone, and willing to share your frobbage, please drop me a note. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 4 23:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23881 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 23:37:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23832 for ; Tue, 4 Aug 1998 23:36:52 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA15087; Wed, 5 Aug 1998 16:06:22 +0930 (CST) Message-Id: <199808050636.QAA15087@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Logue cc: "Daniel O'Connor" , Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Tue, 04 Aug 1998 23:19:55 MST." <35C7F98B.8119F16A@mail.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 16:06:22 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK, so change it to -lc_r on -stable.. > Just finished a build of XF86 3.3.2.3 on -stable with the above, and no go. > I couldn't see how -pthread would work either?? Also tried -lc_r and no go > either. Hmm.. I did it on -current with no problems. What was your error? --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 00:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28358 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 00:03:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28341; Wed, 5 Aug 1998 00:03:48 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA11961; Wed, 5 Aug 1998 09:03:35 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 5 Aug 1998 09:03:34 +0200 (MET DST) Mime-Version: 1.0 To: Bill Paul Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, mike@smith.net.au Subject: Re: Etherlink XL driver References: <199808050548.WAA16103@hub.freebsd.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 05 Aug 1998 09:03:34 +0200 In-Reply-To: Bill Paul's message of "Tue, 4 Aug 1998 22:48:34 -0700 (PDT)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA28342 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul writes: > That said, my plan is to commit the 3.0 version to -current sometime > next week. After a couple more weeks there, I'll commit the 2.2 > version. Oh goody :) The lack of a proper driver for the XL range has been a major PITA (well, in my A at least) for some time. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 00:40:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04049 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 00:40:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03987 for ; Wed, 5 Aug 1998 00:40:01 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA29576; Wed, 5 Aug 1998 00:39:47 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd029571; Wed Aug 5 00:39:43 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA20325; Wed, 5 Aug 1998 00:39:40 -0700 (MST) From: Terry Lambert Message-Id: <199808050739.AAA20325@usr02.primenet.com> Subject: Re: executables over NFS To: dg@root.com Date: Wed, 5 Aug 1998 07:39:40 +0000 (GMT) Cc: tlambert@primenet.com, ben@rosengart.com, hackers@FreeBSD.ORG In-Reply-To: <199808050456.VAA07690@implode.root.com> from "David Greenman" at Aug 4, 98 09:56:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >They are treated as local files -- that is, first page-in is from > >the vnode, and subsequently aggressively cached, including page-out > >to local swap store in preference to discard, so subsequent page-in > >is from local swap store. > > That is not true. In no case will vnode-backed pages be paged out to > swap. The only case where VM could start out as vnode backed and end > up in swap is after a COW, in which case a swap-backed page is created. > This behavior is not modified by the underlying file system type. I thought it was true for FFS as well; a posting in 1996 by John Dyson led me to believe this was true, and I didn't see a change in policy. 8-(. I'll ask John, but you're probably right... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 01:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07239 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 01:09:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07234 for ; Wed, 5 Aug 1998 01:08:56 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA27521; Wed, 5 Aug 1998 18:13:13 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808050813.SAA27521@cimlogic.com.au> Subject: Re: Threaded X libs.. In-Reply-To: <199808050636.QAA15087@cain.gsoft.com.au> from Daniel O'Connor at "Aug 5, 98 04:06:22 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 5 Aug 1998 18:13:13 +1000 (EST) Cc: stevel@mail.cdsnet.net, doconnor@gsoft.com.au, tlambert@primenet.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > > > OK, so change it to -lc_r on -stable.. > > Just finished a build of XF86 3.3.2.3 on -stable with the above, and no go. > > I couldn't see how -pthread would work either?? Also tried -lc_r and no go > > either. > Hmm.. I did it on -current with no problems. > What was your error? -pthread was added to gcc first in -current, then to -stable after the release of 2.2.6. All it does is to use libc_r instead of libc. Linking with -lc_r, but no -nostdlib means that you risk getting functions from libc if the symbols aren't in libc_r. The only one that comes to mind is poll(). If XFree86 uses poll() instead of select(), you can expect to have problems. It's been a while since I looked at XFree86 thread code, but I remember something about a single socket to the connected display, with no way to have a connection per dialog. You lose some of the benefits of threading by having a single socket. It depends on your application, but I don't like mine performing at the speed of X. I always code the X calls in the initial thread and let all the background threads buffer commands for it that are processed as soon as it can. YMMV. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 01:24:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09195 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 01:24:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09189 for ; Wed, 5 Aug 1998 01:24:08 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA15967; Wed, 5 Aug 1998 17:53:29 +0930 (CST) Message-Id: <199808050823.RAA15967@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: doconnor@gsoft.com.au (Daniel O'Connor), stevel@mail.cdsnet.net, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 18:13:13 +1000." <199808050813.SAA27521@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 17:53:29 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -pthread was added to gcc first in -current, then to -stable after the > release of 2.2.6. All it does is to use libc_r instead of libc. Linking > with -lc_r, but no -nostdlib means that you risk getting functions from > libc if the symbols aren't in libc_r. The only one that comes to mind > is poll(). If XFree86 uses poll() instead of select(), you can expect to > have problems. Ahh.. thanks for the tip :) I'm glad I found that out _now_ rather than some handfuls of hair later ;) > It's been a while since I looked at XFree86 thread code, but I remember > something about a single socket to the connected display, with no way > to have a connection per dialog. You lose some of the benefits of > threading by having a single socket. It depends on your application, > but I don't like mine performing at the speed of X. I always code > the X calls in the initial thread and let all the background threads > buffer commands for it that are processed as soon as it can. YMMV. Yes, basically the 'threaded' Xlibs are just normal Xlibs with the ability to lock a display, so aren't teribbly much use. Still, you would probably gain performance if you used one thread per display(not that that situation would present it self very often..) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 02:13:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13486 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 02:13:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13481 for ; Wed, 5 Aug 1998 02:13:46 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA177; Wed, 5 Aug 1998 11:11:39 +0200 Message-ID: <35C821FD.3506A837@pipeline.ch> Date: Wed, 05 Aug 1998 11:12:29 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: John Birrell CC: "Daniel O'Connor" , stevel@mail.cdsnet.net, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. References: <199808050813.SAA27521@cimlogic.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: -snip- > -pthread was added to gcc first in -current, then to -stable after the > release of 2.2.6. All it does is to use libc_r instead of libc. Linking > with -lc_r, but no -nostdlib means that you risk getting functions from > libc if the symbols aren't in libc_r. The only one that comes to mind > is poll(). If XFree86 uses poll() instead of select(), you can expect to > have problems. UhhOhh... Thats why the Netscape Directory SDK (LDAP-Client libs) compile crashes on 2.2.7 with _poll not defined... How can I get around that? Cheers -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 02:34:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15779 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 02:34:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15770 for ; Wed, 5 Aug 1998 02:34:18 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id TAA27710; Wed, 5 Aug 1998 19:35:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808050935.TAA27710@cimlogic.com.au> Subject: Re: Threaded X libs.. In-Reply-To: <35C821FD.3506A837@pipeline.ch> from Andre Oppermann at "Aug 5, 98 11:12:29 am" To: oppermann@pipeline.ch (Andre Oppermann) Date: Wed, 5 Aug 1998 19:35:57 +1000 (EST) Cc: jb@cimlogic.com.au, doconnor@gsoft.com.au, stevel@mail.cdsnet.net, tlambert@primenet.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Oppermann wrote: > UhhOhh... Thats why the Netscape Directory SDK (LDAP-Client libs) > compile crashes on 2.2.7 with _poll not defined... > > How can I get around that? Use select(). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 03:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24511 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 03:53:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24487 for ; Wed, 5 Aug 1998 03:53:03 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id MAA18246 for hackers@FreeBSD.ORG; Wed, 5 Aug 1998 12:52:45 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 2FACD1516; Wed, 5 Aug 1998 12:42:59 +0200 (CEST) Message-ID: <19980805124258.A18337@keltia.freenix.fr> Date: Wed, 5 Aug 1998 12:42:58 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. Mail-Followup-To: hackers@FreeBSD.ORG References: <35C74B7A.42031494@ics.com> <199808050051.KAA11928@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808050051.KAA11928@cain.gsoft.com.au>; from Daniel O'Connor on Wed, Aug 05, 1998 at 10:21:50AM +0930 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4527 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Daniel O'Connor: > Well, one more to go (2.2.8) then 3.0 will be released (sometime near my > birthday.. what a present ;) Nope, Kaleb with get his wish because 3.0 is scheduled for October, 15th and 2.2.8 is scheduled for November, 15th. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 05:43:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08265 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 05:43:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08248 for ; Wed, 5 Aug 1998 05:43:20 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id OAA14805; Wed, 5 Aug 1998 14:42:51 +0200 (MET DST) Date: Wed, 5 Aug 1998 14:42:51 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Kevin Lam cc: FreeBSD hackers mailing list Subject: Re: is 3COM 3C905B-TX supported under 2.2.6-STABLE or 2.2.7-STABLE ? In-Reply-To: <3.0.3.32.19980805221648.00922280@studentmail.dis.unimelb.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >pci0:15: vendor=0x10b7, device=0x9055, class=network (ethernet) int a irq 12 > >[no driver assigned] > > Unfortunately, as of now, the vx0 "Vortex" driver supports only the 3C905A, > using a PIO mode for compatibility with the older 3C509 ISA cards. The B > revision of the Fast EtherLink is not supported, my system runs into > exactly the same problem if I load my 3C905B instead of my A (I have a pair > of them). > Hopefully the new xl driver should resolve this problem by implementing > dedicated 3C905B support, with full support for the busmastering DMA mode > the 3C905s are capable of. Time to watch them reach their full potential :) As was said by the author of the xl driver the 905B support is already fairly solid. And problems so far seem to be related to the start up and not the running of the card. So if it detects it fine and no error messages are displayed during boot you are probably onto a winner. No problems with our 4 machines. If there are we will find them as soon as the backups start running over those cables and cards.... :-) Nik -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 05:58:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09840 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 05:58:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09832 for ; Wed, 5 Aug 1998 05:58:50 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA13066; Wed, 5 Aug 1998 08:58:30 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id HAA01472; Wed, 5 Aug 1998 07:59:56 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id HAA18170; Wed, 5 Aug 1998 07:31:30 -0400 (EDT) Date: Wed, 5 Aug 1998 07:31:30 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808051131.HAA18170@lakes.dignus.com> To: chuckr@glue.umd.edu, rivers@dignus.com Subject: Re: C and static initialization with unions Cc: freebsd-hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And you _seem_ to have made my argument ... you said ANSI forbids it, > you even quoted yourself above, but your quotation from the standard > says it's implementation-defined. That means it's legal, but undefined > behavior. For any reasonable shop making software for sale, they may > mean the same thing, but for someone doing one-off controllers, the > operation is clearly legal, and the programmer is clearly warned that > they had better know what they're doing, because it's not going to be > portable. You're right... I did say "forbids"... that isn't quite right. The standard says: "Implementation-defined behaviour - behavior, for a correct program construct and correct data, that depends on the characteristics of the implementation and that each implementation shall document." Thus, the program is correct; but you can't be sure of what it will do on any platform. Furthermore, a platform may define the behavior as performing in a manner similiar to my example. Thus, "forbids" is the wrong word. Someone's further assertion that we (being SAS) have to diagnose reliance on implementation-defined behavior and weed it out of our sources is correct. So, I tend to be a little strong here. I can easily say this is forbidden in SAS Institute sources. But, anyone who isn't concerned about portability between compilers can go ahead and do this. Note that could even be between different versions of the same compiler... so, gcc is free to change with its next version and "break" any code you have that depends on its previous behavior. In any event, it is an unwise coding practice. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 05:58:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09855 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 05:58:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09836 for ; Wed, 5 Aug 1998 05:58:51 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA13083; Wed, 5 Aug 1998 08:58:34 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id HAA01458; Wed, 5 Aug 1998 07:51:44 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id HAA18129; Wed, 5 Aug 1998 07:23:18 -0400 (EDT) Date: Wed, 5 Aug 1998 07:23:18 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808051123.HAA18129@lakes.dignus.com> To: rivers@dignus.com, tlambert@primenet.com Subject: Re: C and static initialization with unions Cc: chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: <199808050259.TAA04741@usr02.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It's in there; believe me (I'm the manager for C/C++ compiler development > > at SAS Institute...) > > FreeBSD port of all SAS language tools... when? > > 8-) 8-). Don't laugh... if anyone wants it; the way to get it is to let that be known. be sure to contact SAS Institute. If you already are a SAS customer, start with your sales representative. If you're not a SAS customer, start the marketing/sales dept. You never know until you ask.... - Dave Rivers - p.s. FreeBSD is beginning to be used quite heavily internally... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 06:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12593 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 06:22:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12519 for ; Wed, 5 Aug 1998 06:22:01 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id PAA16040; Wed, 5 Aug 1998 15:21:40 +0200 (MET DST) Date: Wed, 5 Aug 1998 15:21:39 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Andreas Klemm cc: FreeBSD hackers mailing list Subject: Re: [aklemm@hightek.com: Re: is 3COM 3C905B-TX supported under 2.2.6-STABLE or 2.2.7-STABLE ?] In-Reply-To: <19980805144917.58324@hightek.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.freebsd.org/~wpaul/ > I saw you ported this driver from OpenBSD to FreeBSD. > Do you see any chance to bring driver support for this > card in ? I have a customer machine here to build up > some virtual webservers and such ... ;-) > > But I only have a small time scale. today and possibly tomorrow. > Otherwise I would have to tell the customer to choose another > card. > > Andreas /// > > -- > B&K Gruppe - Wuppertal > phone +49 202 7399 - 170 > fax +49 202 7399 - 100 http://www.FreeBSD.ORG/~andreas/ > > -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 06:52:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17418 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 06:52:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17413 for ; Wed, 5 Aug 1998 06:52:11 -0700 (PDT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id JAA28675 for ; Wed, 5 Aug 1998 09:51:58 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199808051351.JAA28675@spoon.beta.com> To: hackers@FreeBSD.ORG Subject: select() problem with new device driver... Date: Wed, 05 Aug 1998 09:51:58 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I could probably figure this out with another day of dinking with DDD, but I'm sure someone on -hackers will have a quick answer. In an application, I'm opening up several device descriptors to modem ports (writing the driver for myself, as they're not 'normal' modems). I use the standard macros FD_ZERO, and FD_SET to zero my descriptor set, then set the bits. I the make a select() call with a NULL (no) timeout. When input comes in on a modem, I call ttwakeup in the driver, which appears to get around to calling selwakeup() to wake up anything sleeping on the read side. The _problem_ appears to be that between FD_ZERO, FD_SET, and the upper half of select() (I think its the latter), the t_rsel.si_pid isn't being set (its 0 when I look at it in the driver), and it appears selwakeup() needs a non-zero value in order to actually do anything. I suspect that this field not being set is due to something stupid I'm not doing in the driver, such as setting one of the TS_ flags in the t_state field, but I've yet to be able to find the portion of select() that actually handles this, so I can see what conditions it wants to proceed. Can anyone give me a pointer? Thanks. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 07:26:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23080 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 07:26:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23057 for ; Wed, 5 Aug 1998 07:26:40 -0700 (PDT) (envelope-from kaleb@ics.com) Received: from ics.com (kaleb@teapot.ics.com [140.186.40.160]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id KAA12047; Wed, 5 Aug 1998 10:26:07 -0400 (EDT) Message-ID: <35C86A42.86F4F4EC@ics.com> Date: Wed, 05 Aug 1998 14:20:50 +0000 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.31 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. References: <199808050116.KAA12154@cain.gsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > > > Hmm.. worked for me quite easily, I just added the following lines to the w > > ork/ > > > #define ThreadsLibraries -pthread > > I don't believe you. 8-). > Hah.. man pthread for you :) > At least on -current anyway.. Checking a -stable machine reveals that gcc > hasn't been patched for it :) > > OK, so change it to -lc_r on -stable.. One more reason why threads support is not on in The Open Group (and probably XFree86) sources. And yes, I believe I already knew what to add to the FreeBSD.cf file to enable threads. Something about having worked at the X Consortium for three-and-a-half years. I dunno. My system is on 3.0SNAP-980301 or something close to that, and as I said, threads don't work, and I haven't spent any time figuring out whay. Speaking of 3.0 SNAPS, what's a "good" one out of what's available on current.freebsd.org? Last time I took what was on ftp.cdrom.com and got burned. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 08:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28714 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 08:09:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28701 for ; Wed, 5 Aug 1998 08:09:08 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id KAA01192 for freebsd-hackers@freebsd.org; Wed, 5 Aug 1998 10:08:54 -0500 (CDT) Date: Wed, 5 Aug 1998 10:08:54 -0500 (CDT) From: Mark Tinguely Message-Id: <199808051508.KAA01192@plains.NoDak.edu> To: freebsd-hackers@FreeBSD.ORG Subject: 2.2.7 rsh serious problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG serge@oneway.net was asking a remote tar/tape backup question that was not working, I found that 2.2.7 has a problem with rsh/rshd. to verify: rsh 2.2.7HOST /etc/rmt rsh 2.2.7HOST /bin/cat rsh 2.2.7HOST /bin/sh rsh 2.2.7HOST dd ... basically any remote shell that can accept more input. looking at 2.2.6 and 2.2.7 rshd.c, I found the problem on line 307 in the function doit(): int s = rresvport(&lport); should read: s = rresvport(&lport); because we later use the socket and the extra "int" makes the above side affect only local to the for loop. I will send a bug report, but I am sending this to hackers because it will be a big potential problem that I thought everyone would want to be aware of the problem. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 09:44:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14859 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 09:44:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14817; Wed, 5 Aug 1998 09:44:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with ESMTP id JAA22036; Wed, 5 Aug 1998 09:44:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 5 Aug 1998 09:44:20 -0700 (PDT) From: Doug White To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 Aug 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > The Etherlink XL driver seems to be working fine. How about committing > it to -current and removing the XL probe/attach code from the vx > driver? Except the 3c905-T4, which crashes hardcore (sorry I haven't been able to get back to you Bill, but work & buying a new car took away my time...) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 09:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16289 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 09:51:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16270 for ; Wed, 5 Aug 1998 09:51:08 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id KAA04432; Wed, 5 Aug 1998 10:50:55 -0600 (MDT) Message-Id: <199808051650.KAA04432@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Wed, 05 Aug 1998 10:50:31 -0600 To: hackers@FreeBSD.ORG From: Brett Glass Subject: More on spontaneous crashes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD 2.2.7-RELEASE: We've been getting kernel panics, with spontaneous reboots, during periods of heavy memory and CPU activity (e.g. kernel rebuilds and gzip -9 on large files). dmesg output follows. Sometimes, the system just reboots without flashing a message, but we have seen an error message that complains of a "recursive call" to malloc() and one panic reboot displayed a screen that mentioned a fatal "page not found" error. The problem seems to occur when physical memory is fully committed and we're swapping. I suspect that the bug will be easier to flush out if the system has less memory -- i.e. if it has 8 MB or 16 MB of RAM rather than 32 MB. We'd suspect hardware, except that RAM all tests good and we've changed nothing but the OS version. What's more, the system ONLY CRASHES when specific memory- and CPU-intensive programs are run -- e.g. when we do a kernel recompile or run that backup. --Brett System stats: Intel 486DX4/100 Zeos "Rattler" motherboard with integrated IDE 16 MB RAM Mitsumi CD-ROM with proprietary interface 10 serial ports w/multiport cards Western Digital Caviar 2.5 GB IDE drive Artisoft AE-3 NE2000 clone Diamond PCI graphics adapter (not running X, so VGA mode used always) dmesg output follows: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.7-RELEASE #0: Mon Aug 3 03:43:28 MDT 1998 root@lariat.lariat.org:/usr/src/sys/compile/LARIAT CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 15089664 (14736K bytes) Probing for devices on PCI bus 0: chip0 rev 4 on pci0:0:0 chip1 rev 3 on pci0:2:0 vga0 rev 0 on pci0:13:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x320-0x33f irq 5 on isa ed0: address 00:00:6e:24:e4:15, type NE2000 (16 bit) sio0 at 0x1e0-0x1e7 flags 0x185 on isa sio0: type 16550A (multiport) sio1 at 0x280-0x287 irq 9 flags 0x185 on isa sio1: type 16550A (multiport master) sio2 at 0x3f8-0x3ff flags 0x585 on isa sio2: type 16550A (multiport) sio3 at 0x2f8-0x2ff flags 0x585 on isa sio3: type 16550A (multiport) sio4 at 0x3e8-0x3ef flags 0x585 on isa sio4: type 16550A (multiport) sio5 at 0x2e8-0x2ef irq 4 flags 0x585 on isa sio5: type 16550A (multiport master) sio6 at 0x1f8-0x1ff flags 0x985 on isa sio6: type 16550A (multiport) sio7 at 0x1e8-0x1ef flags 0x985 on isa sio7: type 16550A (multiport) sio8 at 0x2a8-0x2af flags 0x985 on isa sio8: type 16550A (multiport) sio9 at 0x1a8-0x1af irq 3 flags 0x985 on isa sio9: type 16550A (multiport master) lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S mcd0: type Mitsumi FX001D, version info: D 2 mcd0 at 0x310-0x313 irq 10 on isa npx0 flags 0x1 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 10:15:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19381 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 10:15:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19375 for ; Wed, 5 Aug 1998 10:15:06 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA06358; Wed, 5 Aug 1998 13:14:26 -0400 (EDT) Date: Wed, 5 Aug 1998 13:14:26 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: executables over NFS In-Reply-To: <199808050040.RAA26291@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Terry Lambert wrote: > They are treated as local files -- that is, first page-in is from > the vnode, and subsequently aggressively cached, including page-out > to local swap store in preference to discard, so subsequent page-in > is from local swap store. Why would the file be paged out to local swap? Being clean, wouldn't the pages be discarded once selected by the page-replacement algorithm? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 11:32:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03205 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 11:32:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agora.rdrop.com (agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03194 for ; Wed, 5 Aug 1998 11:32:28 -0700 (PDT) (envelope-from batie@agora.rdrop.com) Received: (from batie@localhost) by agora.rdrop.com (8.8.5/8.8.5) id LAA24841; Wed, 5 Aug 1998 11:32:11 -0700 (PDT) Message-ID: <19980805113211.21981@rdrop.com> Date: Wed, 5 Aug 1998 11:32:11 -0700 From: Alan Batie To: freebsd-hackers@FreeBSD.ORG Subject: 2.2.7 crash Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=sdtB3X0nJg68CQEu X-Mailer: Mutt 0.88 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii I've got a freshly built 2.2.7 system. First thing I did after rebooting to the hard disk was go into ports and start building things. During the second build, the system crashed with a kernel page not present trying to access 0x0. It only printed the line with the address, then the line that said "page not present" and not the usual register dump. Here's the system config: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.7-RELEASE #0: Wed Jul 22 08:48:29 GMT 1998 root@builder.cdrom.com:/usr/src/sys/compile/GENERIC CPU: Pentium/P54C (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30404608 (29692K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 1 on pci0:7:1 chip3 rev 1 int d irq 11 on pci0:7:2 chip4 rev 1 on pci0:7:3 vga0 rev 0 on pci0:17:0 ncr0 rev 1 int a irq 10 on pci0:18:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): "NEC CD-ROM DRIVE:463 1.05" type 5 removable SCSI 2 cd0(ncr0:0:0): CD-ROM cd0(ncr0:0:0): asynchronous. can't get the size vx0 <3COM 3C590 Etherlink III PCI> rev 0 int a irq 9 on pci0:19:0 utp[*utp*]: disable 'auto select' with DOS util! address 00:20:af:d0:07:07 Warning! Defective early revision adapter! Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 flags 0x1 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround WARNING: / was not properly dismounted. -- Alan Batie ______ www.rdrop.com/users/batie Me batie@agora.rdrop.com \ / www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A \ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ www.anti-spam.net NO SPAM! --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcilKov4wNua7QglAQE5LwP/chgiVsSdtDKlUNWU5jmkrQeL7gyAzqcp zgQUrngzCwbXymBbMBI+8nYm6X6vsLB2qEk7aigIEEG3Of2kWVno/q49Y9i6czbf Uo2jnYCgC07Fun2yzSJ2+wm7bbmucbHT0Pk1t93TrafHXXkovxolFBtPgkGW/XvG Vlidm68IHrM= =Z0G5 -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 12:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07442 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 12:09:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07361 for ; Wed, 5 Aug 1998 12:09:25 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA05618; Wed, 5 Aug 1998 12:09:06 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd005595; Wed Aug 5 12:09:02 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA28852; Wed, 5 Aug 1998 12:08:57 -0700 (MST) From: Terry Lambert Message-Id: <199808051908.MAA28852@usr05.primenet.com> Subject: Re: executables over NFS To: ben@rosengart.com Date: Wed, 5 Aug 1998 19:08:57 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Aug 5, 98 01:14:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > They are treated as local files -- that is, first page-in is from > > the vnode, and subsequently aggressively cached, including page-out > > to local swap store in preference to discard, so subsequent page-in > > is from local swap store. > > Why would the file be paged out to local swap? Being clean, wouldn't > the pages be discarded once selected by the page-replacement algorithm? According to David Greenman, they wouldn't. There was dicussion on this a while back, which left me believing otherwise, but now I'm not sure. The main reason to do this is that the swap pager is much faster than the vnode pager, especially if it's over the net. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 12:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10882 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 12:30:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10853 for ; Wed, 5 Aug 1998 12:30:13 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id VAA25370 for ; Wed, 5 Aug 1998 21:29:55 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id VAA17682 for ; Wed, 5 Aug 1998 21:29:54 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id VAA02231 for ; Wed, 5 Aug 1998 21:29:55 +0200 (CEST) Received: from server.us.tld(192.168.16.33) via SMTP by curry.mchp.siemens.de, id smtpdhu2227; Wed Aug 5 21:29:54 1998 Received: (from daemon@localhost) by server.us.tld (8.8.8/8.8.8) id VAA03084 for ; Wed, 5 Aug 1998 21:29:54 +0200 (CEST) (envelope-from andre@bali.us.tld) Received: from bali.us.tld(192.168.17.100) via SMTP by server.us.tld, id smtpdtZ2973; Wed Aug 5 21:29:51 1998 Received: (from andre@localhost) by bali.us.tld (8.8.8/8.8.8) id VAA00601; Wed, 5 Aug 1998 21:29:51 +0200 (CEST) (envelope-from andre) From: Andre Albsmeier Message-Id: <199808051929.VAA00601@bali.us.tld> Subject: Re: 2.2.7 rsh serious problem In-Reply-To: <199808051508.KAA01192@plains.NoDak.edu> from Mark Tinguely at "Aug 5, 98 10:08:54 am" To: tinguely@plains.NoDak.edu (Mark Tinguely) Date: Wed, 5 Aug 1998 21:29:51 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > serge@oneway.net was asking a remote tar/tape backup question that > was not working, I found that 2.2.7 has a problem with rsh/rshd. > to verify: > > rsh 2.2.7HOST /etc/rmt > rsh 2.2.7HOST /bin/cat > rsh 2.2.7HOST /bin/sh > rsh 2.2.7HOST dd ... > > basically any remote shell that can accept more input. > > > looking at 2.2.6 and 2.2.7 rshd.c, I found the problem on line 307 > in the function doit(): > > int s = rresvport(&lport); > > should read: > > s = rresvport(&lport); > Has been fixed quite a while ago. PR 7381 -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 13:26:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19274 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 13:26:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19265 for ; Wed, 5 Aug 1998 13:26:46 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA04745; Wed, 5 Aug 1998 22:23:35 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id WAA10737; Wed, 5 Aug 1998 22:22:12 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808052022.WAA10737@semyam.dinoco.de> To: ben@rosengart.com cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Subject: Re: executables over NFS In-reply-to: Your message of "Wed, 05 Aug 1998 13:14:26 EDT." Date: Wed, 05 Aug 1998 22:22:12 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > the vnode, and subsequently aggressively cached, including page-out > > to local swap store in preference to discard, so subsequent page-in > Why would the file be paged out to local swap? Being clean, wouldn't > the pages be discarded once selected by the page-replacement algorithm? It seems - to me - to be easier to just get a few selected blocks for which one knows the block numbers already (i.e. swap space) than to go through the vnode, have to do the translation from offset in file to block number and then get the blocks. And as far as I know without looking at the implementation of shared libraries (I like reading VM more :->) in FreeBSD I think one would have to handle references to parts of dynamically linked libraries in there on page-in somehow. An additional penalty to the CPU which one can avoid with this, too. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 13:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21071 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 13:42:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21066 for ; Wed, 5 Aug 1998 13:42:49 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id QAA11473; Wed, 5 Aug 1998 16:42:21 -0400 (EDT) Date: Wed, 5 Aug 1998 16:42:21 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: executables over NFS In-Reply-To: <199808052022.WAA10737@semyam.dinoco.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Stefan Eggers wrote: > > Why would the [NFS executable] file be paged out to local swap? > > Being clean, wouldn't the pages be discarded once selected by the > > page-replacement algorithm? > > It seems - to me - to be easier to just get a few selected blocks for > which one knows the block numbers already (i.e. swap space) than to go > through the vnode, have to do the translation from offset in file to > block number and then get the blocks. The 4.4 book says that Mach 2.0 used the vnode pager as the swap pager, but the filesystem had not been able to deliver enough bandwidth. It doesn't specify whether the problems were with write bandwidth or read or both. The reason I asked in the first place was that it seemed odd to me to allow pages to be discarded if there's swap available and the backing store is significantly slower than local disk I/O (be it swap or filesystem). Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 14:14:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25238 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 14:14:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freedomnet.com (freedomnet.com [198.240.104.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25227 for ; Wed, 5 Aug 1998 14:14:09 -0700 (PDT) (envelope-from kbyanc@freedomnet.com) Received: from freedomnet.com (tech.freedomnet.com [198.240.104.20]) by freedomnet.com (8.8.7/8.8.7/antispam) with ESMTP id QAA00585 for ; Wed, 5 Aug 1998 16:59:32 -0400 (EDT) X-Envelope-To: Message-ID: <35C8CA87.3DD72E40@freedomnet.com> Date: Wed, 05 Aug 1998 17:11:35 -0400 From: Kelly Yancey Organization: FreedomNet - http://www.freedomnet.com/ X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: syscons update Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have written an update to the freebsd syscons driver and vidcontrol program to allow for 4 new VGA text modes: 90x25, 90x30, 90x50, 90x60. Yes, 90 columns wide. I had written an assembly program years ago that ran under DOS that switched to 90 columns wide...it works fine on every VGA and SVGA adapter I have ever run across. Basically, it just toggles the VGA adapter from using 9 pixel wide characters to 8 pixel wide characters and then adjusts the horizontal counts accordingly. I'm wrapping up the code for that so I can submit it to the team to include in future FreeBSD releases. But that's not why I'm posting (that was just the self gratifaction segment :) )...the syscons code is hideous. Talk about one overworked driver. Now it handles screen output, keyboard input, and text-mode mouse functions. It also appears that there is some sort of intent to add basic graphics functions to the syscons driver. I had some ideas, which I wanted to run by everyone else and see what you all think. I realize that most are probably to radical to be practical since I imagine vidcontrol and kbdcontrol aren't the only programs that interact with the syscons driver itimately. * Division of functionality: right now, moused watches the mouse device and notifies the console driver of any changes which in turn notifies sysmouse. Why doesn't moused interact directly with sysmouse... isolating all the mouse functionality to sysmouse. Then, if the user wants a mouse cursor in text mode, the console driver is welcome to interact with sysmouse like every other program does. What am I missing? And more importantly, it seems to me that the code should at least be split up, if not the functionality. Why not separate source files containing the display, keyboard, and mouse related routines in the syscons driver? Just because it is one driver, doesn't mean it has to be a single source file. I think that would go a long way toward improving the code readability. * Continuing on the idea of dividing the work...improve the graphics support: currently things are sort of strange: X supposedly a userland program has to ship with video drivers. Why isn't this in the OS? Not only would it make X's job easier...but it would allow other user programs to easily use graphics without having to be written for X (like games). The way I see this working is by having video adapter drivers like we have sound card drivers or network card drivers. Basic vidmono, vidcga, videga, vidvga drivers could be extracted from the currently syscons code. The console driver then just interacts with the video adapter driver. Also a bonus: you could have more than one video card in a system with different video drivers loaded, which are all managed by the syscons driver. Wahla...multiple physical and virtual console support native to the OS (it's not just for X anymore). However, a basic set of ioctl functions should be defined for video adapter drivers for certain functions. For example: an ioctl to determine what video modes are available and another to select the video mode. ioctl values could be defined for many graphics acceleration features. User programs could then interface with the syscons driver to do graphics on the current console (virtual or physical), if the video driver for that console supports hardware acceleration for a function, the syscons driver could call that, otherwise it can piece it together from other functions if possible. So, the way I envision things: hardware: keyboard mouse video ... | | | | sysmouse vga0 (or other video driver) | | | `------console-----' /|\ / | \ user land programs That goal of all of this rearranging would be to encourage development for the FreeBSD system mainly in the area of graphics programming. At the moment is seems that Linux is getting a lot more attention in that area (for better for for worse). I've been using BSD derivatives (FreeBSD and BSDi) for several years now and think, personally, it wipes the floor with linux. It is a shame to see it get many of the new inovations first now just because of it's recent popularity. I realize that what I'm suggesting is a major overhaul of one of the oldest and most fundimental aspects of FreeBSD, or Unix in general. But it is a driver that dates back to teletype terminals and it showing it's dating. It seems to me that there is at least some interest in modernizing the console interface (else, why add the text mouse support), so why just play catch up when we could leap ahead? I would love to see video adapters fully supported by the OS just like everything else is. Who knows, maybe one day the console driver will actually support just the text modes available on my SuperVGA card, not to mention graphics and 3D acceleration. My rantings. :) I am interested to know what other people think. I'de be even more interested in knowing if the FreeBSD core team would allow be to begin work on this master plan :) I'de be glad to get it started...but I know my own limitations...there is no way I'de be able to write all the SuperVGA video drivers myself. I could at least write drivers including all of the current functionality plus CGA, EGA, and VGA graphics (text modes, mouse, etc.) I guess I'm just looking for opinions and support. Your input is welcome, Thanks for listening, Kelly Yancey ~kbyanc@freedomnet.com~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 14:45:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29268 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 14:45:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29255; Wed, 5 Aug 1998 14:45:02 -0700 (PDT) (envelope-from pechter@shell.monmouth.com) Received: (from pechter@localhost) by shell.monmouth.com (8.8.5/8.7.3) id RAA25751; Wed, 5 Aug 1998 17:44:40 -0400 (EDT) From: Bill/Carolyn Pechter Message-Id: <199808052144.RAA25751@shell.monmouth.com> Subject: DTC 3274 controller To: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Wed, 5 Aug 1998 17:44:39 -0400 (EDT) Cc: dorel@babel.ho.lucent.com, pechter@babel.ho.lucent.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone ever run a DTC3274 controller with FreeBSD. Their website says it's supported by the standard 1540 Adaptec driver in SCO. I'm suspecting it's the same as the 3290 -- except VLB not EISA. I've got one I'm going to be trying. Bill +---------------------------------------------------------------------------+ | Bill and/or Carolyn Pechter | pechter@shell.monmouth.com | | Bill Gates is a Persian cat and a monocle away from being a villain in | | a James Bond movie -- Dennis Miller | +---------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 15:42:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07240 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 15:42:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07234 for ; Wed, 5 Aug 1998 15:41:54 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id AAA07359 for ; Thu, 6 Aug 1998 00:41:38 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id AAA05242 for hackers@freebsd.org; Thu, 6 Aug 1998 00:41:37 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199808052241.AAA05242@surf.IAE.nl> Subject: Adding system calls To: hackers@FreeBSD.ORG Date: Thu, 6 Aug 1998 00:41:37 +0200 (MET DST) Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This must be a FAQ, but I can not find it. :-( What/were is the receipe to add new system calls. I'd like to add my own sysctl_* calls. Are there any directives on what "design" to use while defining these calls. Like: - Use only one syscall as a multiplexer (Which created a not so trivial mess is the current sysctl) - What parameters are a bad idea to transfer from user to kernel space? And answers to questions like: - Where can I find the "user"-data - Hoe to I return results for "call-by-ref" parameters Sounds like there should be at least some info on this. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 16:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10897 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 16:05:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10868 for ; Wed, 5 Aug 1998 16:04:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01549; Wed, 5 Aug 1998 16:03:18 -0700 (PDT) Message-Id: <199808052303.QAA01549@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kelly Yancey cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscons update In-reply-to: Your message of "Wed, 05 Aug 1998 17:11:35 EDT." <35C8CA87.3DD72E40@freedomnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 16:03:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is most amazing is that just in the last 24 hours we've been discussing what you're basically talking about here... > I have written an update to the freebsd syscons driver and vidcontrol > program to allow for 4 new VGA text modes: 90x25, 90x30, 90x50, 90x60. > Yes, 90 columns wide. I had written an assembly program years ago that > ran under DOS that switched to 90 columns wide...it works fine on every > VGA and SVGA adapter I have ever run across. Basically, it just toggles > the VGA adapter from using 9 pixel wide characters to 8 pixel wide > characters and then adjusts the horizontal counts accordingly. I'm > wrapping up the code for that so I can submit it to the team to include > in future FreeBSD releases. Neat. How would you like to help work on adding support for the VESA text modes too? > But that's not why I'm posting (that was just the self gratifaction > segment :) )...the syscons code is hideous. Talk about one overworked > driver. Now it handles screen output, keyboard input, and text-mode > mouse functions. It also appears that there is some sort of intent to > add basic graphics functions to the syscons driver. The functionality is actually already there, although you might have missed it. 8) > I had some ideas, which I wanted to run by everyone else and see what > you all think. I realize that most are probably to radical to be > practical since I imagine vidcontrol and kbdcontrol aren't the only > programs that interact with the syscons driver itimately. Actually, what you go on to propose is what everyone has agreed has been needed for a long time now. Syscons desperately needs someone with time and energy to break it down into modules. > * Division of functionality: right now, moused watches the mouse > device and notifies the console driver of any changes which in turn > notifies sysmouse. Why doesn't moused interact directly with sysmouse... > isolating all the mouse functionality to sysmouse. Then, if the user > wants a mouse cursor in text mode, the console driver is welcome to > interact with sysmouse like every other program does. What am I missing? It's quite hard for a device driver to open and read from another device. What currently happens is actually just a workaround for this; instead of creating a pipe and writing mouse events to it, moused sends ioctls to the console device. The console device then turns this stuff around to make it easy for other consumers to use. > And more importantly, it seems to me that the code should at least be > split up, if not the functionality. Why not separate source files > containing the display, keyboard, and mouse related routines in the > syscons driver? Just because it is one driver, doesn't mean it has to be > a single source file. I think that would go a long way toward improving > the code readability. One of the problems with that is namespace pollution. Your proposal below implies that you're looking at a relatively tidy separation between the modules, so that's OK. > * Continuing on the idea of dividing the work...improve the graphics > support: currently things are sort of strange: X supposedly a userland > program has to ship with video drivers. Why isn't this in the OS? Because the drivers are maintained by the X people, so there's one set of drivers maintained by one group that covers a large number of operating systems. As opposed to forcing them to deal with a plethora of different interfaces with different operating systems, and forcing each operating system group to duplicate the work of the others. In addition, video drivers bulk *large*. You don't want these in the kernel. > My rantings. :) I am interested to know what other people think. I'de > be even more interested in knowing if the FreeBSD core team would allow > be to begin work on this master plan :) I'de be glad to get it > started...but I know my own limitations...there is no way I'de be able > to write all the SuperVGA video drivers myself. I could at least write > drivers including all of the current functionality plus CGA, EGA, and > VGA graphics (text modes, mouse, etc.) I guess I'm just looking for > opinions and support. Your input is welcome, Forget writing the bitmap drivers. If you were simply to take syscons, and start talking to Soren (sos@freebsd.org) about modularising it, you should find a task that's both worthwhile and achievable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 16:07:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11256 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 16:07:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11241; Wed, 5 Aug 1998 16:06:56 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id RAA00494; Wed, 5 Aug 1998 17:06:41 -0600 (MDT) Message-Id: <199808052306.RAA00494@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Wed, 05 Aug 1998 17:06:16 -0600 To: hackers@FreeBSD.ORG, bugs@FreeBSD.ORG From: Brett Glass Subject: More on the spontaneous crashes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As mentioned in earlier messages, we're still trying to do a backup and getting a crash every time. Our backup routine works by creating a command file which is redirected into FTP. The command that fails is put "|dump 0uf - /usr | gzip -9" usr.$starttime.gz (where $starttime is the starting time of the backup; it's replaced with a numerical UNIX date as the command file is created). As you can see, FTP is accepting input from dump, via gzip, and sending it to the named file on the other machine. This is done over a separate LAN segment for security. The screen that flashes, just before the reboot, says that there was a GP fault in the kernel. I can't print the screen or otherwise save it, and it goes by very quickly -- faster than I can write down the information. (I've considered grabbing a camera to take a picture.) How can we nail this bug and get it fixed? We need to do backups, and Heaven knows that if this userland stuff causes a crash, other things will too. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 17:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22046 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 17:25:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22037; Wed, 5 Aug 1998 17:25:05 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA05795; Wed, 5 Aug 1998 17:24:51 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd005764; Wed Aug 5 17:24:45 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id RAA20275; Wed, 5 Aug 1998 17:24:42 -0700 (MST) From: Terry Lambert Message-Id: <199808060024.RAA20275@usr06.primenet.com> Subject: Re: More on the spontaneous crashes To: brett@lariat.org (Brett Glass) Date: Thu, 6 Aug 1998 00:24:42 +0000 (GMT) Cc: hackers@FreeBSD.ORG, bugs@FreeBSD.ORG In-Reply-To: <199808052306.RAA00494@lariat.lariat.org> from "Brett Glass" at Aug 5, 98 05:06:16 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The screen that flashes, just before the reboot, says that there was a GP > fault in the kernel. I can't print the screen or otherwise save it, and it > goes by very quickly -- faster than I can write down the information. (I've > considered grabbing a camera to take a picture.) Boot a "com console", attach a PC running communications software capable of session logging, and make it blow up. This will identify the culprit in no uncertain terms. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 17:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22762 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 17:28:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22745; Wed, 5 Aug 1998 17:28:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA01905; Wed, 5 Aug 1998 17:26:58 -0700 (PDT) Message-Id: <199808060026.RAA01905@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: More on the spontaneous crashes In-reply-to: Your message of "Wed, 05 Aug 1998 17:06:16 MDT." <199808052306.RAA00494@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 17:26:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As mentioned in earlier messages, we're still trying to do a backup and > getting a crash every time. Our backup routine works by creating a command > file which is redirected into FTP. The command that fails is > > put "|dump 0uf - /usr | gzip -9" usr.$starttime.gz > > (where $starttime is the starting time of the backup; it's replaced with a > numerical UNIX date as the command file is created). > > As you can see, FTP is accepting input from dump, via gzip, and sending it > to the named file on the other machine. This is done over a separate LAN > segment for security. > > The screen that flashes, just before the reboot, says that there was a GP > fault in the kernel. I can't print the screen or otherwise save it, and it > goes by very quickly -- faster than I can write down the information. (I've > considered grabbing a camera to take a picture.) > > How can we nail this bug and get it fixed? We need to do backups, and > Heaven knows that if this userland stuff causes a crash, other things will > too. Put 'options DDB' in your kernel config. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 17:58:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26803 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 17:58:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lochnagar.pdl.cs.cmu.edu (LOCHNAGAR.PDL.CS.CMU.EDU [128.2.189.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA26739 for ; Wed, 5 Aug 1998 17:58:02 -0700 (PDT) (envelope-from dpetrou@lochnagar.pdl.cs.cmu.edu) Message-Id: <199808060058.RAA26739@hub.freebsd.org> Subject: verifying sources with cvsup... To: freebsd-hackers@FreeBSD.ORG Date: Wed, 5 Aug 1998 20:57:47 -0400 (EDT) From: David Petrou Reply-To: dpetrou@cs.cmu.edu X-Mailer: ELM [version 2.4 PL25-40] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I keep up-to-date with stable using cvsup. Recently I suffered some fs corruption and a bunch of files in /usr/src and /usr/ports got screwed up. When I next run cvsup, will it automatically find the bad files and get new copies of them? This is what the manpage says: ------------------------------------------------------------------------------ For efficiency, cvsup maintains a bookkeeping file for each collection, called the list file. The list file contains information about which files and revisions the client currently possesses. It also contains in- formation used for verifying that the list file is consistent with the actual files in the client's tree. The list file is not strictly necessary. If it is deleted, or becomes inconsistent with the actual client files, cvsup falls back upon a less efficient method of identifying the client's files and performing its up- dates. Depending on CVSup 's mode of operation, the fallback method em- ploys time stamps, checksums, or analysis of RCS files. ------------------------------------------------------------------------------ Unfortunately, I don't know what "mode of operation" my cvsup is using. I'm hoping that I can just delete the list files and cvsup will do something like compare md5 checksums of all my files against the archive. Thanks, David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 17:59:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26922 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 17:59:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26895 for ; Wed, 5 Aug 1998 17:59:03 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0z4ENc-0003k3-00; Wed, 5 Aug 1998 19:58:08 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199808052241.AAA05242@surf.IAE.nl> References: <199808052241.AAA05242@surf.IAE.nl> Subject: Re: Adding system calls To: wjw@IAEhv.nl cc: hackers@FreeBSD.ORG Date: Wed, 05 Aug 1998 19:58:08 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 6 August 1998 at 0:41, Willem Jan Withagen wrote: > Hi, > > This must be a FAQ, but I can not find it. :-( > > What/were is the receipe to add new system calls. > I'd like to add my own sysctl_* calls. If you want a new object in the MIB, see sys/sys/sysctl.h. If you actually want a new system call: 1. Edit $src/sys/kern/syscalls.master. 2. Run ``shmakesyscalls.sh syscalls.master'' or ``make ../sys/sysproto.h'' in sys/kern. To take care of libc: 3. cd $src/include && make install 4. cd $src/lib/libc && make obj depend && make all install I think that's it. Someone with more experience should answer the important questions below. > Are there any directives on what "design" to use while defining these calls. > Like: > - Use only one syscall as a multiplexer > (Which created a not so trivial mess is the current sysctl) > - What parameters are a bad idea to transfer from > user to kernel space? > > And answers to questions like: > - Where can I find the "user"-data > - Hoe to I return results for "call-by-ref" parameters > > Sounds like there should be at least some info on this. > > --WjW Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcj/oDeRhT8JRySpAQFBKAP9F5Ajs1YRpZibF3leYgURjCD1NLoQ5qch SatjYunt+uiwBX1u4g8laBMh3efHRILIQfbyr+iSyODnSg9yPV7xHRt5zFOtNwql y+w4ACQO6KJYA4b/fABu0F8qc5XPxVxdgXsemhoQlqxrnLUR7T4XFtVKFczYySSe u9s+C3jYe40= =s0vZ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 18:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01297 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 18:29:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01288; Wed, 5 Aug 1998 18:29:25 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id SAA06567; Wed, 5 Aug 1998 18:28:57 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id SAA08679; Wed, 5 Aug 1998 18:28:45 -0700 (PDT) From: Gary Kline Message-Id: <199808060128.SAA08679@tao.thought.org> Subject: 2.2.6 page fault (Prev: Re: 2.2.7 crash) In-Reply-To: <19980805113211.21981@rdrop.com> from Alan Batie at "Aug 5, 98 11:32:11 am" To: batie@rdrop.com (Alan Batie) Date: Wed, 5 Aug 1998 18:28:45 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, stable@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alan Batie: > I've got a freshly built 2.2.7 system. First thing I did after rebooting > to the hard disk was go into ports and start building things. During the > second build, the system crashed with a kernel page not present trying to > access 0x0. It only printed the line with the address, then the line that > said "page not present" and not the usual register dump. Here's the system > config: > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. [[ ... ]] > -- > Alan Batie ______ www.rdrop.com/users/batie Me > batie@agora.rdrop.com \ / www.qrd.org The Triangle Gentlemen:: I suppose it is time (after 7 weeks) to re-report this page-fault | can't-find-disklabel bug from 2.2.6. This hit me after a power surge knocked out my 6x86 in June. ((And, it turns out, No, we did not ``stuff'' the cables in the replaced hardware.)) Following is what is output to the console every time we try to boot multi-user. Single-user works flawlessly, including bringing the system up to multi-user by-hand. > > The problem: > > At the exact same place in the boot process each time, the kernel > panics: > > Automatic reboot in progress... > /dev/rsd0s1a: clean, 170441 free (425 frags, 21252 blocks, 0.2% fragmentation) > sds2: cannot find label (I/O error) > > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x12a > fault code = supervisor read, page not present > intstruction pointer = 0x8:0xf01182b7 > stack pointer = 0x10:0xefbffb5c > frame pointer = 0x10:0xefbffb7c > 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 = 11 (fsck) > interupt mask = > panic: page fault > > syncing disks... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up > Automatic reboot in 15 seconds - press a key on the console to abort > > > What has been changed since it last worked: > > The only 2 things which have been changed since the box last booted > normally are that the motherboard and SCSI card have been replaced. > The previous SCSI card was an Adaptec 2940 built into the > motherboard. The new SCSI card is a separate Adaptec 2940. All > cabling, DIP switches on the drives, et cetera is exactly the same as > it was (well, I changed it for some of the tests, but then I put it > back the way I found it). > Note that we are going to try at leastone last thing: a new P5 motherboard (( and perhaps yet-another 6x86 mb with built-in SCSI)). This would return my second box to it previous state almost exactly. Meanwhile, if anyone has any ideas what's causing this page fault, please clue me in... danke, gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 18:35:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02416 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 18:35:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA02399 for ; Wed, 5 Aug 1998 18:35:05 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4Ex9-00002w-00; Wed, 5 Aug 1998 19:34:51 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id TAA09279 for ; Wed, 5 Aug 1998 19:35:04 -0600 (MDT) Message-Id: <199808060135.TAA09279@harmony.village.org> To: hackers@FreeBSD.ORG Subject: Anybody have... Date: Wed, 05 Aug 1998 19:35:03 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for the Datasheet to a Intel 82593. This part was in the Networking book in 1992, but not in the 1996 version I have access to. It is not on their web site and when I called intel they told me that it was too old for them to be able to sell me/send me the datasheet on. Can some kind soul help me in my quest? I'm not adverse to paying shipping, reproduction costs, etc for this document. Many thanks.. Warner P.S. This is FreeBSD related: I'm looking at writing a driver for a card that has one of these chips on it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 18:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04880 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 18:54:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04875 for ; Wed, 5 Aug 1998 18:54:29 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA27167; Wed, 5 Aug 1998 18:51:24 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdI27165; Thu Aug 6 01:51:18 1998 Message-ID: <35C90C13.1CFBAE39@whistle.com> Date: Wed, 05 Aug 1998 18:51:15 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: Kelly Yancey , freebsd-hackers@FreeBSD.ORG Subject: Re: syscons update References: <199808052303.QAA01549@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > What is most amazing is that just in the last 24 hours we've been > discussing what you're basically talking about here... see the note I posted from -93 on the topic in -current > > Actually, what you go on to propose is what everyone has agreed has > been needed for a long time now. Syscons desperately needs someone > with time and energy to break it down into modules. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 19:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12516 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 19:57:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12509 for ; Wed, 5 Aug 1998 19:57:09 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4GEY-00004y-00; Wed, 5 Aug 1998 20:56:54 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id UAA09636; Wed, 5 Aug 1998 20:57:07 -0600 (MDT) Message-Id: <199808060257.UAA09636@harmony.village.org> To: Julian Elischer Subject: Re: syscons update Cc: Mike Smith , Kelly Yancey , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Aug 1998 18:51:15 PDT." <35C90C13.1CFBAE39@whistle.com> References: <35C90C13.1CFBAE39@whistle.com> <199808052303.QAA01549@dingo.cdrom.com> Date: Wed, 05 Aug 1998 20:57:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also it might be worth while to take a look at the NetBSD wscons stuff.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 21:50:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25297 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 21:50:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25286 for ; Wed, 5 Aug 1998 21:50:46 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA22132; Wed, 5 Aug 1998 21:50:25 -0700 (PDT) (envelope-from jdp) Message-Id: <199808060450.VAA22132@austin.polstra.com> To: dpetrou@cs.cmu.edu Subject: Re: verifying sources with cvsup... In-Reply-To: <199808060058.RAA26739@hub.freebsd.org> References: <199808060058.RAA26739@hub.freebsd.org> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 05 Aug 1998 21:50:25 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808060058.RAA26739@hub.freebsd.org>, David Petrou wrote: > Hi. I keep up-to-date with stable using cvsup. Recently I suffered > some fs corruption and a bunch of files in /usr/src and /usr/ports got > screwed up. When I next run cvsup, will it automatically find the bad > files and get new copies of them? It depends on what kind of corruption you suffered. Often, filesystem problems or hardware problems cause portions of files to be scribbled on _without_ changing the modification times or sizes of the files. CVSup will not notice this corruption until the next time somebody commits a change to the file, which could be a long time. But read on ... > This is what the manpage says: Yay! A person who reads the man page! :-) > ------------------------------------------------------------------------------ > For efficiency, cvsup maintains a bookkeeping file for each collection, > called the list file. The list file contains information about which > files and revisions the client currently possesses. It also contains in- > formation used for verifying that the list file is consistent with the > actual files in the client's tree. > > The list file is not strictly necessary. If it is deleted, or becomes > inconsistent with the actual client files, cvsup falls back upon a less > efficient method of identifying the client's files and performing its up- > dates. Depending on CVSup 's mode of operation, the fallback method em- > ploys time stamps, checksums, or analysis of RCS files. > ------------------------------------------------------------------------------ > > Unfortunately, I don't know what "mode of operation" my cvsup is > using. The main question is, are you using "checkout mode" (i.e., is there a "tag=" clause in your cvsupfile)? I assume you are, since you mention /usr/src and /usr/ports, but not /home/ncvs. > I'm hoping that I can just delete the list files and cvsup will do > something like compare md5 checksums of all my files against the > archive. If you are using checkout mode, then that should work fine. It will be slower than usual. Also, this really places a heavy load on the server, so you should try not to do it too often. Thanks for the excellent FAQ candidate. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 22:32:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01065 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 22:32:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ccs.sogang.ac.kr (ccs.sogang.ac.kr [163.239.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00927; Wed, 5 Aug 1998 22:30:08 -0700 (PDT) (envelope-from kylee@oslab0.sogang.ac.kr) Received: from oslab0.sogang.ac.kr by ccs.sogang.ac.kr (8.8.8/Sogang) id OAA11854; Thu, 6 Aug 1998 14:26:04 +0900 (KST) Received: from oslab0.sogang.ac.kr by oslab0.sogang.ac.kr (8.8.8/SMI-SVR4) id OAA03257; Thu, 6 Aug 1998 14:20:41 +0900 (KST) Message-ID: <35C93DC5.BDE733FB@oslab0.sogang.ac.kr> Date: Thu, 06 Aug 1998 14:23:18 +0900 From: Lee Ki Young Organization: Sogang University X-Mailer: Mozilla 4.03 [ko] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Unable to open Sound Card? Content-Type: text/plain; charset=iso-2022-kr Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HI!! I use Freebsd 3.0-980522-Snap version. there is a sound card which is "Sound Blaster" in my PC. I setup some sound condition in a file for Kernel Compile. And then.. I can listen sounds on CDROM. But when I have some sound program, x11amp, mpg123, There is a error message which are "Unable to open sound device". Well.. I hope to know how to use and play sound program. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 22:49:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02706 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 22:49:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02701 for ; Wed, 5 Aug 1998 22:49:18 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-86.camalott.com [208.229.74.86]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id AAA01625; Thu, 6 Aug 1998 00:50:22 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA13226; Thu, 6 Aug 1998 00:49:08 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 00:49:08 -0500 (CDT) Message-Id: <199808060549.AAA13226@detlev.UUCP> To: mcgovern@spoon.beta.com CC: hackers@FreeBSD.ORG In-reply-to: <199807311744.NAA13956@spoon.beta.com> (mcgovern@spoon.beta.com) Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807311744.NAA13956@spoon.beta.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yup, me again with another dumb programming question.... Yup, me again with another late answer.... > I seem to be running in to problems when opeing up a device special > file with either O_SHLOCK or O_EXLOCK. I get an error back (45) that > the operation is not supported. > My question, then, is, how can I lock, lets say a serial port, > without having to go the route of lock-file creation, as many > applications ignore these files anyhow? O_SHLOCK and O_EXLOCK are advisory, not mandatory. In other words, the apps are going to ignore them anyway. Lock files are the way to go. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 22:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02747 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 22:49:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02742 for ; Wed, 5 Aug 1998 22:49:35 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id BAA24198; Thu, 6 Aug 1998 01:49:06 -0400 (EDT) Message-Id: <199808060549.BAA24198@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Anybody have... References: <199808060135.TAA09279@harmony.village.org> In-reply-to: Your message of "Wed, 05 Aug 1998 19:35:03 MDT." <199808060135.TAA09279@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 01:49:05 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some time ago, Mike Petry and I wrote a driver for this part for NetBSD (me) and BSDI (Petry). See http://www.TransSys.COM/TransSys/NetBSD/znet.html for the NetBSD driver. Note this is pretty old, and probably doesn't drop into anyone's kernel these days. This was for a Zenith Z-Note laptop (with a 486SL CPU!). It worked quite well, and I recall running tcpdump fairly effectively. I've started porting it to FreeBSD a couple of times, but I fear the code is cursed; each time I started converting the driver, some horrible disaster would befall my system, and the disk with the code in progress would die a horrible death. You have been warned :-) I know that I have the Intel databook for this part *somewhere*, but I haven't seen it since I moved a year and a half ago. I think you'll get quite a head starting with the NetBSD driver, though. The driver is a little grotty in the sense that it's an 82593 driver for the Zenith laptop and it needs to do some rather rude DMA controller setup because of the way the 82593 works. Take a look at the code; you'll see. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 22:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04058 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 22:56:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04050 for ; Wed, 5 Aug 1998 22:56:06 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id WAA27774; Wed, 5 Aug 1998 22:55:53 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd027765; Wed Aug 5 22:55:48 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id WAA22288; Wed, 5 Aug 1998 22:55:45 -0700 (MST) From: Terry Lambert Message-Id: <199808060555.WAA22288@usr09.primenet.com> Subject: Re: Anybody have... To: imp@village.org (Warner Losh) Date: Thu, 6 Aug 1998 05:55:45 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199808060135.TAA09279@harmony.village.org> from "Warner Losh" at Aug 5, 98 07:35:03 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm looking for the Datasheet to a Intel 82593. This part was in the > Networking book in 1992, but not in the 1996 version I have access > to. It is not on their web site and when I called intel they told me > that it was too old for them to be able to sell me/send me the > datasheet on. Can some kind soul help me in my quest? I'm not > adverse to paying shipping, reproduction costs, etc for this > document. I believe this is the AT&T card Garrett originall wrote the driver for. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 22:58:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04278 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 22:58:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA04273 for ; Wed, 5 Aug 1998 22:58:50 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4J3Q-0000BV-00; Wed, 5 Aug 1998 23:57:36 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id XAA12589; Wed, 5 Aug 1998 23:57:51 -0600 (MDT) Message-Id: <199808060557.XAA12589@harmony.village.org> To: Terry Lambert Subject: Re: Anybody have... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Aug 1998 05:55:45 -0000." <199808060555.WAA22288@usr09.primenet.com> References: <199808060555.WAA22288@usr09.primenet.com> Date: Wed, 05 Aug 1998 23:57:51 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808060555.WAA22288@usr09.primenet.com> Terry Lambert writes: : > I'm looking for the Datasheet to a Intel 82593. This part was in the : > Networking book in 1992, but not in the 1996 version I have access : > to. It is not on their web site and when I called intel they told me : > that it was too old for them to be able to sell me/send me the : > datasheet on. Can some kind soul help me in my quest? I'm not : > adverse to paying shipping, reproduction costs, etc for this : > document. : : I believe this is the AT&T card Garrett originall wrote the driver for. Does this mean that you have a datasheet for it? The i82593 that I have is on an IBM wireless card that has an IBM chip on it, so itis unlikely that it is the same card. However, if you have info on it, I'd love to hear about it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 23:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAB05075 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 23:03:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA05053 for ; Wed, 5 Aug 1998 23:03:26 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4J8m-0000Bf-00; Thu, 6 Aug 1998 00:03:08 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id AAA12615; Thu, 6 Aug 1998 00:03:23 -0600 (MDT) Message-Id: <199808060603.AAA12615@harmony.village.org> To: "Louis A. Mamakos" Subject: Re: Anybody have... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Aug 1998 01:49:05 EDT." <199808060549.BAA24198@whizzo.transsys.com> References: <199808060549.BAA24198@whizzo.transsys.com> <199808060135.TAA09279@harmony.village.org> Date: Thu, 06 Aug 1998 00:03:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808060549.BAA24198@whizzo.transsys.com> "Louis A. Mamakos" writes: : I know that I have the Intel databook for this part *somewhere*, but I : haven't seen it since I moved a year and a half ago. I think you'll get : quite a head starting with the NetBSD driver, though. The driver is a : little grotty in the sense that it's an 82593 driver for the Zenith laptop : and it needs to do some rather rude DMA controller setup because of the : way the 82593 works. Take a look at the code; you'll see. I just looked at the code. *ICKY* is the best way to describe it. If you can find the databook, I'd add you to the growing list of people I owe beers to for this project.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 23:12:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07102 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 23:12:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07041 for ; Wed, 5 Aug 1998 23:12:11 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40377>; Thu, 6 Aug 1998 16:11:32 +1000 Date: Thu, 6 Aug 1998 16:11:44 +1000 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #211 To: hackers@FreeBSD.ORG Message-Id: <98Aug6.161132est.40377@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 Aug 1998 17:11:35 -0400, Kelly Yancey wrote: > * Continuing on the idea of dividing the work...improve the graphics >support: currently things are sort of strange: You might like to check out http://www.ggi-project.org/ Whilst this is Linux-oriented, some of the ideas may be useful (I don't know what copyright the code is using, so I'm not sure if the code is directly usable). One of the claims made in a Dr Dobbs article (which I don't remember the date of) is that XFree86 does (or will) include support for this interface. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 23:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08888 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 23:26:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08763 for ; Wed, 5 Aug 1998 23:25:52 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) id 0z4J4z-0000d9-00; Thu, 6 Aug 1998 07:59:13 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id HAA09198; Thu, 6 Aug 1998 07:51:35 +0200 (SAT) Date: Thu, 6 Aug 1998 07:51:33 +0200 (SAT) From: Peter van Heusden To: Andre Oppermann cc: hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-Reply-To: <35C821FD.3506A837@pipeline.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Andre Oppermann wrote: > John Birrell wrote: > -snip- > > -pthread was added to gcc first in -current, then to -stable after the > > release of 2.2.6. All it does is to use libc_r instead of libc. Linking > > with -lc_r, but no -nostdlib means that you risk getting functions from > > libc if the symbols aren't in libc_r. The only one that comes to mind > > is poll(). If XFree86 uses poll() instead of select(), you can expect to > > have problems. > > UhhOhh... Thats why the Netscape Directory SDK (LDAP-Client libs) > compile crashes on 2.2.7 with _poll not defined... > > How can I get around that? In the Netscape Directory SDK source, apply the patch which follows this message. It seems to work for me. Peter -- Peter van Heusden | Its the 90's, and collective action is STILL cool! pvh@leftside.wcape.school.za | Get active in your union today! *** directory/c-sdk/ldap/libraries/libldap/ldap-int.h.old Tue Jul 21 21:15:49 1998 --- directory/c-sdk/ldap/libraries/libldap/ldap-int.h Tue Jul 21 21:18:04 1998 *************** *** 79,85 **** # include #endif /* USE_SYSCONF */ ! #if !defined(_WINDOWS) && !defined(macintosh) && !defined(LINUX2_0) #define NSLDAPI_HAVE_POLL 1 #endif --- 79,85 ---- # include #endif /* USE_SYSCONF */ ! #if !defined(_WINDOWS) && !defined(macintosh) && !defined(LINUX2_0) && !defined(FREEBSD) #define NSLDAPI_HAVE_POLL 1 #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 23:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12007 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 23:53:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12001 for ; Wed, 5 Aug 1998 23:53:07 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0z4JuL-0004PY-00; Thu, 6 Aug 1998 01:52:17 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199808060549.AAA13226@detlev.UUCP> References: <199807311744.NAA13956@spoon.beta.com> <199808060549.AAA13226@detlev.UUCP> Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) To: joelh@gnu.org cc: mcgovern@spoon.beta.com, hackers@FreeBSD.ORG Date: Thu, 06 Aug 1998 01:52:17 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Huh? Sure, O_SHLOCK and O_EXLOCK are advisory, but so are lock files. Applications are free to ignore any of them. Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org On 6 August 1998 at 0:49, Joel Ray Holveck wrote: > O_SHLOCK and O_EXLOCK are advisory, not mandatory. In other words, > the apps are going to ignore them anyway. Lock files are the way to > go. > > Best, > joelh -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNclSoTeRhT8JRySpAQE+uQP/U/6HczSAzqRNpZ0H+djGgxZs5h90WEXp YqgLMjvT0EErxtB0TMVE56LmB+Kcevwm+WVpf9NqI+OBjvzBr8MKfVHV1hTmakgW c3dRBeZu8MoO2tXy1AR1VlK6jE9SntHaTO+4adlCSRijlz5cnGTkj1PKy4OarWmD CAEMlx24SuE= =/CfV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 5 23:55:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12239 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 23:55:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12228 for ; Wed, 5 Aug 1998 23:54:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00923; Wed, 5 Aug 1998 23:53:43 -0700 (PDT) Message-Id: <199808060653.XAA00923@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: imp@village.org (Warner Losh), hackers@FreeBSD.ORG Subject: Re: Anybody have... In-reply-to: Your message of "Thu, 06 Aug 1998 05:55:45 -0000." <199808060555.WAA22288@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 23:53:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm looking for the Datasheet to a Intel 82593. This part was in the > > Networking book in 1992, but not in the 1996 version I have access > > to. It is not on their web site and when I called intel they told me > > that it was too old for them to be able to sell me/send me the > > datasheet on. Can some kind soul help me in my quest? I'm not > > adverse to paying shipping, reproduction costs, etc for this > > document. > > I believe this is the AT&T card Garrett originall wrote the driver for. You're probably thinking of the 82586. The 82593 is an old low-power device, used in eg. the Wavelan PCCARD adapters and some IBM notebooks. (I don't think that Garrett wrote the PCCARD Wavelan driver.) It seems laughable to me that Intel wouldn't be able to offer a datasheet on such a part, when you can still get datasheets on the 8255. It's not clear whether the datasheet for the 82595 would shed any light on what you're currently trying to work out, but it's worth a stab. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 00:01:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13258 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 00:01:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13238 for ; Thu, 6 Aug 1998 00:00:45 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00975; Wed, 5 Aug 1998 23:58:57 -0700 (PDT) Message-Id: <199808060658.XAA00975@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter van Heusden cc: Andre Oppermann , hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Sat, 06 Aug 1998 07:51:33 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 23:58:56 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In the Netscape Directory SDK source, apply the patch which follows > this message. It seems to work for me. Don't do this, as it's incorrect for FreeBSD 3.0 and later. Instead, if FreeBSD is defined, you should include osversion.h and test based on that. > Peter > -- > Peter van Heusden | Its the 90's, and collective action is STILL cool! > pvh@leftside.wcape.school.za | Get active in your union today! > > *** directory/c-sdk/ldap/libraries/libldap/ldap-int.h.old Tue Jul 21 21:15:49 1998 > --- directory/c-sdk/ldap/libraries/libldap/ldap-int.h Tue Jul 21 21:18:04 1998 > *************** > *** 79,85 **** > # include > #endif /* USE_SYSCONF */ > > ! #if !defined(_WINDOWS) && !defined(macintosh) && !defined(LINUX2_0) > #define NSLDAPI_HAVE_POLL 1 > #endif > > --- 79,85 ---- > # include > #endif /* USE_SYSCONF */ > > ! #if !defined(_WINDOWS) && !defined(macintosh) && !defined(LINUX2_0) && !defined(FREEBSD) > #define NSLDAPI_HAVE_POLL 1 > #endif > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 00:09:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14734 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 00:09:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14695 for ; Thu, 6 Aug 1998 00:09:34 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA27232; Thu, 6 Aug 1998 16:39:10 +0930 (CST) Message-Id: <199808060709.QAA27232@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #211 In-reply-to: Your message of "Thu, 06 Aug 1998 16:11:44 +1000." <98Aug6.161132est.40377@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 16:39:09 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You might like to check out http://www.ggi-project.org/ Whilst this is > Linux-oriented, some of the ideas may be useful (I don't know what > copyright the code is using, so I'm not sure if the code is directly > usable). One of the claims made in a Dr Dobbs article (which I don't > remember the date of) is that XFree86 does (or will) include support > for this interface. Well, the license is all GPL :( And yes, you can make XFree86 talk to GGI, although I have no idea as to its performance. GGI has some nice ideas.. Mainly because they're actually doing something with regard to the problem of lack of a decent graphics framework for unix :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 00:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14910 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 00:10:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14831 for ; Thu, 6 Aug 1998 00:10:13 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id XAA05901; Wed, 5 Aug 1998 23:53:07 -0700 (PDT) Message-Id: <199808060653.XAA05901@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Warner Losh Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Anybody have... Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 05 Aug 1998 23:53:06 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 Aug 1998 23:57:51 -0600 Warner Losh wrote: > : I believe this is the AT&T card Garrett originall wrote the driver for. > > Does this mean that you have a datasheet for it? The i82593 that I > have is on an IBM wireless card that has an IBM chip on it, so itis > unlikely that it is the same card. However, if you have info on it, > I'd love to hear about it... Garrett wrote a driver for the i82586. I think the i82593 is what is used in the WaveLAN, yes? I think it also has an i82586 mode. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 01:47:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26337 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 01:47:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26320 for ; Thu, 6 Aug 1998 01:47:20 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id KAA21301 for ; Thu, 6 Aug 1998 10:54:17 +0200 (SAT) Received: by citadel via recvmail id 21299; Thu Aug 6 10:53:59 1998 From: Graham Wheeler Message-Id: <199808060852.KAA05590@cdsec.com> Subject: Re: Anybody have... To: hackers@FreeBSD.ORG Date: Thu, 6 Aug 1998 10:52:55 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Garrett wrote a driver for the i82586. I think the i82593 is what is > used in the WaveLAN, yes? I think it also has an i82586 mode. I wrote a DOS packet driver for the i82586 for Multibus machines some years back. If the i82593 is compatible with the i82586, and this packet driver code would be useful, let me know. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 02:29:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02236 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 02:29:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02231 for ; Thu, 6 Aug 1998 02:29:17 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc103.reseau.uvsq.fr [193.51.24.19]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id LAA29199 ; Thu, 6 Aug 1998 11:28:48 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.8/8.8.5) id LAA00337; Thu, 6 Aug 1998 11:35:44 GMT Message-ID: <19980806113159.49110@breizh.prism.uvsq.fr> Date: Thu, 6 Aug 1998 11:31:59 +0000 From: Nicolas Souchu To: Mike Smith Cc: Terry Lambert , Chuck Robey , freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions References: <199808050103.SAA27705@usr02.primenet.com> <199808050149.SAA01073@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199808050149.SAA01073@dingo.cdrom.com>; from Mike Smith on Tue, Aug 04, 1998 at 06:49:27PM -0700 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 06:49:27PM -0700, Mike Smith wrote: [...] >> 4) It still breaks for: >> >> typedef enum { UT_INT, UT_CHAR, UT_PTR } ut_t; >> >> typedef struct { >> ut_t u_type; >> struct foo_t u; /* someone blew a typedef*/ >> } bob_t; >> >> bob_t bobs.p[] = { >> { UT_PTR, &anyvar }, >> { UT_INT, 35 }, /* oops!*/ >> { UT_PTR, NULL } >> }; >> > >The gcc info "extensions/named elements" section describes a useful >extension that lets you cut through much of this crap. > It becomes a FreeBSD related question then... thanks mike ;) Archie said: >>> One non-portable nicety of gcc is that you can do this: union foo { int iarg; char carg; }; static union foo x = { carg: 12 }; -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com <<< Is it allowed in FreeBSD? Is all FreeBSD C source code portable? -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 02:29:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02255 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 02:29:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02248 for ; Thu, 6 Aug 1998 02:29:25 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc103.reseau.uvsq.fr [193.51.24.19]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id LAA29218 ; Thu, 6 Aug 1998 11:29:03 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.8/8.8.5) id LAA00345; Thu, 6 Aug 1998 11:37:15 GMT Message-ID: <19980806113559.56672@breizh.prism.uvsq.fr> Date: Thu, 6 Aug 1998 11:35:59 +0000 From: Nicolas Souchu To: Ted Faber Cc: Warner Losh , FreeBSD Hackers Subject: Re: C and static initialization with unions References: <199808041950.NAA18579@harmony.village.org> <199808042143.OAA15441@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199808042143.OAA15441@tnt.isi.edu>; from Ted Faber on Tue, Aug 04, 1998 at 02:43:21PM -0700 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 02:43:21PM -0700, Ted Faber wrote: > >Not that this belongs in hackers... > I agree, but the question arised while writting FreeBSD C code. Anyway, it remembers me to read the FAQs first :) -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 05:00:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22303 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 05:00:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22192 for ; Thu, 6 Aug 1998 05:00:06 -0700 (PDT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id HAA01248; Thu, 6 Aug 1998 07:59:47 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199808061159.HAA01248@spoon.beta.com> To: Jacques Vidrine cc: joelh@gnu.org, mcgovern@spoon.beta.com, hackers@FreeBSD.ORG Subject: Re: O_SHLOCK and O_EXLOCK - change to layering required? In-reply-to: Your message of "Thu, 06 Aug 1998 01:52:17 CDT." Date: Thu, 06 Aug 1998 07:59:46 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Huh? >Sure, O_SHLOCK and O_EXLOCK are advisory, but so are lock files. >Applications are free to ignore any of them. >Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org Yeah, but 80% of my problem is the fact they cause the open() call on a device to fail with varying error codes, depending on the type of device. On my own device, it appears that the error condition occurs even before the driver open() call gets called. If I could make it to my driver without something above me setting off bells and whistles, I could make the locking not-so-advisory by handling it in the driver. The problem is that it returns EOPNOTSUPP on serial ports, for example. I think locking would be far more useful if locking would be passed down through the layers until either a layer that COULD handle it became involved, or the DRIVER said "Nope, not supported here", or even silently ignored the lock request. It just seems pitiful to have a reasonable file locking mechanism in place, but not be able to use the same semantics to lock a device. Falling back to UU-style locks is not only easily bypassed (rendering the locking useless, but it reeks of kludge). All it takes to ruin several people's days is to have one person that runs a com program that uses UU-locking, one that uses device locking (which will fail in this case), and one that does no locking, and I've got three people talking to a modem. Not good. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 05:09:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23989 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 05:09:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from windoms.sitek.net (windoms.sitek.net [195.212.188.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23858 for ; Thu, 6 Aug 1998 05:09:25 -0700 (PDT) (envelope-from Gangster@windoms.sitek.net) Received: from admin (das-1-9.sitek.net [195.212.189.9]) by windoms.sitek.net (8.9.1/8.9.1) with ESMTP id QAA01194 for ; Thu, 6 Aug 1998 16:07:24 +0400 Message-Id: <199808061207.QAA01194@windoms.sitek.net> From: "Gangsta" To: Subject: Re: freebsd-hackers-digest V4 #209 Date: Thu, 6 Aug 1998 16:07:45 +0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BDC154.59212540" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ýòî ñîîáùåíèå â ôîðìàòå MIME ñîñòîèò èç íåñêîëüêèõ ÷àñòåé. ------=_NextPart_000_01BDC154.59212540 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit unsubscribe free-bsd hackers ------=_NextPart_000_01BDC154.59212540 Content-Type: text/html; charset=KOI8-R Content-Transfer-Encoding: quoted-printable

unsubscribe free-bsd hackers

------=_NextPart_000_01BDC154.59212540-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 07:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15708 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 07:51:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA15701 for ; Thu, 6 Aug 1998 07:51:44 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4RNz-0000Ou-00; Thu, 6 Aug 1998 08:51:23 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id IAA14508; Thu, 6 Aug 1998 08:51:41 -0600 (MDT) Message-Id: <199808061451.IAA14508@harmony.village.org> To: Mike Smith Subject: Re: Anybody have... Cc: Terry Lambert , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Aug 1998 23:53:42 PDT." <199808060653.XAA00923@antipodes.cdrom.com> References: <199808060653.XAA00923@antipodes.cdrom.com> Date: Thu, 06 Aug 1998 08:51:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808060653.XAA00923@antipodes.cdrom.com> Mike Smith writes: : It's not clear whether the datasheet for the 82595 would shed any light : on what you're currently trying to work out, but it's worth a stab. No. Small light, but not much. They are for a radically different part. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 08:11:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18695 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 08:11:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freedomnet.com (freedomnet.com [198.240.104.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18690 for ; Thu, 6 Aug 1998 08:10:58 -0700 (PDT) (envelope-from kbyanc@freedomnet.com) Received: (from kbyanc@localhost) by freedomnet.com (8.8.7/8.8.7/antispam) id KAA01027; Thu, 6 Aug 1998 10:55:38 -0400 (EDT) X-Envelope-To: freebsd-hackers@FreeBSD.ORG Date: Thu, 6 Aug 1998 10:55:35 -0400 (EDT) From: Kelly Yancey To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscons update In-Reply-To: <199808052303.QAA01549@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Mike Smith wrote: > > What is most amazing is that just in the last 24 hours we've been > discussing what you're basically talking about here... > > > I have written an update to the freebsd syscons driver and vidcontrol > > program to allow for 4 new VGA text modes: 90x25, 90x30, 90x50, 90x60. > > Yes, 90 columns wide. I had written an assembly program years ago that > > ran under DOS that switched to 90 columns wide...it works fine on every > > VGA and SVGA adapter I have ever run across. Basically, it just toggles > > the VGA adapter from using 9 pixel wide characters to 8 pixel wide > > characters and then adjusts the horizontal counts accordingly. I'm > > wrapping up the code for that so I can submit it to the team to include > > in future FreeBSD releases. > > Neat. How would you like to help work on adding support for the VESA > text modes too? That would be great. It's really a shame though...especially when getting into all the VESA text modes too...that it isn't more modular. > > > But that's not why I'm posting (that was just the self gratifaction > > segment :) )...the syscons code is hideous. Talk about one overworked > > driver. Now it handles screen output, keyboard input, and text-mode > > mouse functions. It also appears that there is some sort of intent to > > add basic graphics functions to the syscons driver. > > The functionality is actually already there, although you might have > missed it. 8) > > > I had some ideas, which I wanted to run by everyone else and see what > > you all think. I realize that most are probably to radical to be > > practical since I imagine vidcontrol and kbdcontrol aren't the only > > programs that interact with the syscons driver itimately. > > Actually, what you go on to propose is what everyone has agreed has > been needed for a long time now. Syscons desperately needs someone > with time and energy to break it down into modules. I was thinking that, in order to not disturb the current syscons driver, maybe start on a new separate video driver. Something where the new video driver interfaces to a card-specific driver providing generic interface ioctl calls for user programs to use. That will make sure we don't get in the way of the syscons development or break any code that uses the current syscons driver. Then down the road, we could modify syscons to go through the video driver for any screen updating. Also, what would be really exciting is a FreeBSD X server that made calls to the video driver (rather than having the adapter-specific routines in the X server). Talk about division of labor...I would think that would make code cleaner all around. > > > * Division of functionality: right now, moused watches the mouse > > device and notifies the console driver of any changes which in turn > > notifies sysmouse. Why doesn't moused interact directly with sysmouse... > > isolating all the mouse functionality to sysmouse. Then, if the user > > wants a mouse cursor in text mode, the console driver is welcome to > > interact with sysmouse like every other program does. What am I missing? > > It's quite hard for a device driver to open and read from another > device. What currently happens is actually just a workaround for this; > instead of creating a pipe and writing mouse events to it, moused > sends ioctls to the console device. The console device then turns this > stuff around to make it easy for other consumers to use. Good point. Perhaps their should be a standard video/mouse API (probably should be something for sound too) the way there is a disk access layer and networking layer. Computers have come a long way, baby. :) > > > And more importantly, it seems to me that the code should at least be > > split up, if not the functionality. Why not separate source files > > containing the display, keyboard, and mouse related routines in the > > syscons driver? Just because it is one driver, doesn't mean it has to be > > a single source file. I think that would go a long way toward improving > > the code readability. > > One of the problems with that is namespace pollution. Your proposal > below implies that you're looking at a relatively tidy separation > between the modules, so that's OK. > > > * Continuing on the idea of dividing the work...improve the graphics > > support: currently things are sort of strange: X supposedly a userland > > program has to ship with video drivers. Why isn't this in the OS? > > Because the drivers are maintained by the X people, so there's one set > of drivers maintained by one group that covers a large number of > operating systems. As opposed to forcing them to deal with a plethora > of different interfaces with different operating systems, and forcing > each operating system group to duplicate the work of the others. > > In addition, video drivers bulk *large*. You don't want these in the > kernel. No, you're right. I guess better support for modular drivers is needed before that could happen. But as far as the video drivers are concerned...at first it would seem like reinventing the wheel since all the support currently in the X servers would have to be put in the OS (where it should have been to begin with, in my opinion). But the short-term advantage is that other programs for FreeBSD could easily use the video adapter's graphics capabilities...especially games :). The long-term, perhaps pipe-dream, advantage would be that the X group could focus on X things, not platform things. Like I mentioned above, someone could strip all the hardware-specific code from an X server and replace it with calls to the video driver (kind of like how it uses sysmouse now), then any other platforms that implemented similar OS-level video control could use the same server. In theory, at least, the X group wouldn't have to worry about the hardware specifics anymore...the OS developers would. > > > My rantings. :) I am interested to know what other people think. I'de > > be even more interested in knowing if the FreeBSD core team would allow > > be to begin work on this master plan :) I'de be glad to get it > > started...but I know my own limitations...there is no way I'de be able > > to write all the SuperVGA video drivers myself. I could at least write > > drivers including all of the current functionality plus CGA, EGA, and > > VGA graphics (text modes, mouse, etc.) I guess I'm just looking for > > opinions and support. Your input is welcome, > > Forget writing the bitmap drivers. If you were simply to take syscons, > and start talking to Soren (sos@freebsd.org) about modularising it, you > should find a task that's both worthwhile and achievable. > > -- Yeah, one step at a time I suppose...got my head stuck in the clouds :) BTW, I've submitted the 90-column support patches (one for the syscons driver, one for the vidcontrol program to use the new modes) to the FreeBSD team...I'll keep my fingers crossed. I've also posted the patches on a web page: http://www.posi.net/software/public/patch-90col/ Thanks for your feedback, Kelly Yancey ~kbyanc@freedomnet.com~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 09:23:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01816 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 09:23:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01798 for ; Thu, 6 Aug 1998 09:23:05 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA26353; Thu, 6 Aug 1998 09:22:37 -0700 (PDT) (envelope-from jdp) Message-Id: <199808061622.JAA26353@austin.polstra.com> To: Nicolas.Souchu@prism.uvsq.fr Subject: Re: C and static initialization with unions In-Reply-To: <19980806113159.49110@breizh.prism.uvsq.fr> References: <199808050103.SAA27705@usr02.primenet.com> <199808050149.SAA01073@dingo.cdrom.com> <19980806113159.49110@breizh.prism.uvsq.fr> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Thu, 06 Aug 1998 09:22:37 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980806113159.49110@breizh.prism.uvsq.fr>, Nicolas Souchu wrote: > Archie said: > > >>> > One non-portable nicety of gcc is that you can do this: > > union foo { > int iarg; > char carg; > }; > > static union foo x = { carg: 12 }; > > -Archie > <<< > > Is it allowed in FreeBSD? You can do anything you want in the privacy of your own home. But I would strongly oppose the use of this extension in any code being committed into FreeBSD itself. I suspect Bruce would make some noise about it too. Surely you can find a portable way to accomplish what you want to do, even if it means executing a few lines of code at run time. > Is all FreeBSD C source code portable? GCC extensions are occasionally used in FreeBSD. However, they are virtually always optional and for the purpose of (a) better efficiency, or (b) better compiler warnings. When GCC extensions are used, they are protected by "#ifdef __GNUC__", and an alternative portable implementation is provided in the "#else" clause. For case (a) the alternative implementation is less efficient; for case (b), it's a no-op. See for some examples of (b). -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 09:55:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06633 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 09:55:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tomcat.webber.net.ua (S2-2.webber.GWN-KVC2.ukrpack.net [195.230.151.38] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06450; Thu, 6 Aug 1998 09:54:15 -0700 (PDT) (envelope-from apl@opera.webber.net.ua) Received: from opera.webber.net.ua by tomcat.webber.net.ua with ESMTP id TAA13753; (8.8.8/vak/1.9) Thu, 6 Aug 1998 19:53:55 +0300 (EEST) Received: from webber.net.ua by opera.webber.net.ua with ESMTP id TAA10677; (8.8.8/vak/1.9) Thu, 6 Aug 1998 19:53:56 +0300 (EEST) Message-ID: <35C9DD28.2E9749D3@webber.net.ua> Date: Thu, 06 Aug 1998 19:43:20 +0300 From: Andrew Petrenko X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: SCO binaries and FreeBSD 2.2.7-stable Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Need help. i run FoxPro 2.6. for SCO on FreeBSD and get error Too many files open. in login.conf i set ... openfiles=254 openfiles-cur=254 ... what can i do for run FoxPro? Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 10:03:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08790 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 10:03:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08777 for ; Thu, 6 Aug 1998 10:03:38 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id JAA13156; Thu, 6 Aug 1998 09:46:33 -0700 (PDT) Message-Id: <199808061646.JAA13156@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Mike Smith Cc: Terry Lambert , imp@village.org (Warner Losh), hackers@FreeBSD.ORG Subject: Re: Anybody have... Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 06 Aug 1998 09:46:32 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 Aug 1998 23:53:42 -0700 Mike Smith wrote: > You're probably thinking of the 82586. The 82593 is an old low-power > device, used in eg. the Wavelan PCCARD adapters and some IBM notebooks. > (I don't think that Garrett wrote the PCCARD Wavelan > driver.) > > It seems laughable to me that Intel wouldn't be able to offer a > datasheet on such a part, when you can still get datasheets on the 8255. > > It's not clear whether the datasheet for the 82595 would shed any light > on what you're currently trying to work out, but it's worth a stab. I'm pretty certain that the '595 is a fair bit different from the '593. I believe that Matt Thomas is writing a from-scratch WaveLAN driver for NetBSD, and is planning on just using the '586 compatibility mode of the '593 so that the same code can be used for the ISA and the PCMCIA versions of the card. (The only real benefit from using the native '593 mode, apparently, is slightly finer-grained control of the multicast address filter... "big deal" :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 10:33:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15120 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 10:33:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15115 for ; Thu, 6 Aug 1998 10:33:28 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA09052; Thu, 6 Aug 1998 10:32:19 -0700 (PDT) Message-Id: <199808061732.KAA09052@tnt.isi.edu> To: Nicolas Souchu Cc: Mike Smith , Terry Lambert , Chuck Robey , freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: Your message of "Thu, 06 Aug 1998 11:31:59 -0000." <19980806113159.49110@breizh.prism.uvsq.fr> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 10:32:19 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Nicolas Souchu wrote: >On Tue, Aug 04, 1998 at 06:49:27PM -0700, Mike Smith wrote: >>The gcc info "extensions/named elements" section describes a useful >>extension that lets you cut through much of this crap. > >It becomes a FreeBSD related question then... thanks mike ;) Uhhh, no. It becomes a gcc-related question. > >Is it allowed in FreeBSD? Is all FreeBSD C source code portable? Now *that's* a FreeBSD-related question. I don't see anything regarding unions or initialization in style(9), other than > When declaring variables in structures, declare them sorted by use, then > by size, and then by alphabetical order. The first category normally > doesn't apply, but there are exceptions. Each one gets its own line. > Put a tab after the first word, i.e. use `int^Ix;' and `struct^Ifoo *x;' And, of course, all FreeBSD source is portable. :-) :-) :-) - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcnooob4eisfQ5rpAQEOCgP/b7ZsC6I/aBPYMwIzOCSn4Xs0JP568pLg 02U3QokvnIuHuURlnvc0kr8zs8CGon3qZp/RMoBXExEpkgGE0+exhT5lGdEEhNK3 7qDNNpobpbn3h9muT9fjCaypXSMIYmoDg4FKtWlPIhXd+lxPJ1mh0t0ELU82zvug ySA5rRgFkVA= =Z7Fg -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 10:52:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17994 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 10:52:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17974; Thu, 6 Aug 1998 10:52:44 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from tempest ([195.121.59.2]) by smtp01.wxs.nl (Netscape Messaging Server 3.54) with SMTP id AAAF9E; Thu, 6 Aug 1998 19:52:29 +0200 X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Thu, 06 Aug 1998 19:55:15 +0200 To: FreeBSD Hardware , FreeBSD From: Jeroen Ruigrok/Asmodai Subject: ZIP drive Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <77184A69146C.AAAF9E@smtp01.wxs.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya, anyone tried using the CURRENT 3.0 drivers for the Iomega ZIP drive under 2.2.6? Because the original ppbus distribution package has some errors, and since SNAP has this driver in it's distribution I thought that it might be usable under 2.2.6 too... If ye did something like this, could ye please tell me which directories I need to download from the CURRENT directory? I have downloaded some ppbus files/directories already, but am afraid I might have missed some things... Also, are there special things I would need to setup next to the files? The ppbus dist documentation said to make nodes using mknod. Any help on this? Thanks, -- Jeroen Ruigrok van der Werven / Asmodai ICQ-UIN: 1564317 .:. Ninth Circle Enterprises Network/Security Specialist As far as ye can't tell, I am the Future in Computer Hell... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 11:39:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26427 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 11:39:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26343; Thu, 6 Aug 1998 11:39:18 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id OAA20881; Thu, 6 Aug 1998 14:40:45 -0400 (EDT) Date: Thu, 6 Aug 1998 14:40:45 -0400 (EDT) From: Mark turpin To: FreeBSD Current , FreeBSD hackers Subject: Kernel compile problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to compile a GENERIC (-current as of 2:00PM (EDT) Aug 6,1998) kernel I get the following error. Am I doing something wrong? Thanks Mark Turpin cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../scsi/cd.c In file included from ../../scsi/cd.c:48: ioconf.h:11: conflicting types for `fdintr' ../../i386/isa/isa_device.h:155: previous declaration of `fdintr' ioconf.h:11: warning: redundant redeclaration of `fdintr' in same scope ../../i386/isa/isa_device.h:155: warning: previous declaration of `fdintr' ioconf.h:12: conflicting types for `wdintr' ../../i386/isa/isa_device.h:186: previous declaration of `wdintr' ioconf.h:12: warning: redundant redeclaration of `wdintr' in same scope ../../i386/isa/isa_device.h:186: warning: previous declaration of `wdintr' ioconf.h:13: conflicting types for `bt_isa_intr' ../../i386/isa/isa_device.h:146: previous declaration of `bt_isa_intr' ioconf.h:13: warning: redundant redeclaration of `bt_isa_intr' in same scope ../../i386/isa/isa_device.h:146: warning: previous declaration of `bt_isa_intr' ioconf.h:14: conflicting types for `uhaintr' ../../i386/isa/isa_device.h:185: previous declaration of `uhaintr' ioconf.h:14: warning: redundant redeclaration of `uhaintr' in same scope ../../i386/isa/isa_device.h:185: warning: previous declaration of `uhaintr' ioconf.h:15: conflicting types for `ahaintr' ../../i386/isa/isa_device.h:138: previous declaration of `ahaintr' ioconf.h:15: warning: redundant redeclaration of `ahaintr' in same scope ../../i386/isa/isa_device.h:138: warning: previous declaration of `ahaintr' ioconf.h:16: conflicting types for `aicintr' ../../i386/isa/isa_device.h:139: previous declaration of `aicintr' ioconf.h:16: warning: redundant redeclaration of `aicintr' in same scope ../../i386/isa/isa_device.h:139: warning: previous declaration of `aicintr' ioconf.h:17: conflicting types for `ncaintr' ../../i386/isa/isa_device.h:167: previous declaration of `ncaintr' ioconf.h:17: warning: redundant redeclaration of `ncaintr' in same scope ../../i386/isa/isa_device.h:167: warning: previous declaration of `ncaintr' ioconf.h:18: conflicting types for `seaintr' ../../i386/isa/isa_device.h:177: previous declaration of `seaintr' ioconf.h:18: warning: redundant redeclaration of `seaintr' in same scope ../../i386/isa/isa_device.h:177: warning: previous declaration of `seaintr' ioconf.h:19: conflicting types for `wtintr' ../../i386/isa/isa_device.h:189: previous declaration of `wtintr' ioconf.h:19: warning: redundant redeclaration of `wtintr' in same scope ../../i386/isa/isa_device.h:189: warning: previous declaration of `wtintr' ioconf.h:20: conflicting types for `mcdintr' ../../i386/isa/isa_device.h:165: previous declaration of `mcdintr' ioconf.h:20: warning: redundant redeclaration of `mcdintr' in same scope ../../i386/isa/isa_device.h:165: warning: previous declaration of `mcdintr' ioconf.h:23: conflicting types for `scintr' ../../i386/isa/isa_device.h:176: previous declaration of `scintr' ioconf.h:23: warning: redundant redeclaration of `scintr' in same scope ../../i386/isa/isa_device.h:176: warning: previous declaration of `scintr' ioconf.h:24: conflicting types for `npxintr' ../../i386/isa/isa_device.h:168: previous declaration of `npxintr' ioconf.h:24: warning: redundant redeclaration of `npxintr' in same scope ../../i386/isa/isa_device.h:168: warning: previous declaration of `npxintr' ioconf.h:26: conflicting types for `siointr' ../../i386/isa/isa_device.h:178: previous declaration of `siointr' ioconf.h:26: warning: redundant redeclaration of `siointr' in same scope ../../i386/isa/isa_device.h:178: warning: previous declaration of `siointr' ioconf.h:27: conflicting types for `lptintr' ../../i386/isa/isa_device.h:163: previous declaration of `lptintr' ioconf.h:27: warning: redundant redeclaration of `lptintr' in same scope ../../i386/isa/isa_device.h:163: warning: previous declaration of `lptintr' ioconf.h:28: conflicting types for `mseintr' ../../i386/isa/isa_device.h:166: previous declaration of `mseintr' ioconf.h:28: warning: redundant redeclaration of `mseintr' in same scope ../../i386/isa/isa_device.h:166: warning: previous declaration of `mseintr' ioconf.h:29: conflicting types for `psmintr' ../../i386/isa/isa_device.h:173: previous declaration of `psmintr' ioconf.h:29: warning: redundant redeclaration of `psmintr' in same scope ../../i386/isa/isa_device.h:173: warning: previous declaration of `psmintr' ioconf.h:30: conflicting types for `edintr' ../../i386/isa/isa_device.h:150: previous declaration of `edintr' ioconf.h:30: warning: redundant redeclaration of `edintr' in same scope ../../i386/isa/isa_device.h:150: warning: previous declaration of `edintr' ioconf.h:31: conflicting types for `ieintr' ../../i386/isa/isa_device.h:158: previous declaration of `ieintr' ioconf.h:31: warning: redundant redeclaration of `ieintr' in same scope ../../i386/isa/isa_device.h:158: warning: previous declaration of `ieintr' ioconf.h:32: conflicting types for `epintr' ../../i386/isa/isa_device.h:153: previous declaration of `epintr' ioconf.h:32: warning: redundant redeclaration of `epintr' in same scope ../../i386/isa/isa_device.h:153: warning: previous declaration of `epintr' ioconf.h:33: conflicting types for `exintr' ../../i386/isa/isa_device.h:154: previous declaration of `exintr' ioconf.h:33: warning: redundant redeclaration of `exintr' in same scope ../../i386/isa/isa_device.h:154: warning: previous declaration of `exintr' ioconf.h:34: conflicting types for `feintr' ../../i386/isa/isa_device.h:156: previous declaration of `feintr' ioconf.h:34: warning: redundant redeclaration of `feintr' in same scope ../../i386/isa/isa_device.h:156: warning: previous declaration of `feintr' ioconf.h:35: conflicting types for `le_intr' ../../i386/isa/isa_device.h:160: previous declaration of `le_intr' ioconf.h:35: warning: redundant redeclaration of `le_intr' in same scope ../../i386/isa/isa_device.h:160: warning: previous declaration of `le_intr' ioconf.h:36: conflicting types for `lncintr' ../../i386/isa/isa_device.h:161: previous declaration of `lncintr' ioconf.h:36: warning: redundant redeclaration of `lncintr' in same scope ../../i386/isa/isa_device.h:161: warning: previous declaration of `lncintr' ioconf.h:37: conflicting types for `zeintr' ../../i386/isa/isa_device.h:190: previous declaration of `zeintr' ioconf.h:37: warning: redundant redeclaration of `zeintr' in same scope ../../i386/isa/isa_device.h:190: warning: previous declaration of `zeintr' ioconf.h:38: conflicting types for `zpintr' ../../i386/isa/isa_device.h:191: previous declaration of `zpintr' ioconf.h:38: warning: redundant redeclaration of `zpintr' in same scope ../../i386/isa/isa_device.h:191: warning: previous declaration of `zpintr' ioconf.h:39: conflicting types for `csintr' ../../i386/isa/isa_device.h:147: previous declaration of `csintr' ioconf.h:39: warning: redundant redeclaration of `csintr' in same scope ../../i386/isa/isa_device.h:147: warning: previous declaration of `csintr' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 12:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09572 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 12:31:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09542 for ; Thu, 6 Aug 1998 12:31:30 -0700 (PDT) (envelope-from syang@directhit.com) Received: from moe.dirhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id PAA15860 for ; Thu, 6 Aug 1998 15:31:11 -0400 (EDT) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Thu, 6 Aug 1998 15:28:45 -0400 Message-ID: <839A86AB6CE4D111A52200104B938D4303D1DF@MOE> From: Steven Yang To: "'freebsd-hackers@freebsd.org'" Subject: how do you get crack to compile? Date: Thu, 6 Aug 1998 15:28:44 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm struggling to get crack to compile on freebsd. I'm on FreeBSD 2.2.6, and I'm trying to get either crack 5.0 or crack 4.1 to work. I've spent most of my time trying to get crack 5.0 to work, but the only thing I've done that seems to help at all is to modifiy the makefile to use -DTERMIOS rather than -DTERMIO. That gets it further through the compiling, but now I run into: Invoked: Crack -fmt freebsd password-file Stamp: freebsd-2-i386_ Crack: making utilities in run/bin/freebsd-2-i386_ find . -name "*~" -print | xargs -n50 rm -f ( cd src; for dir in * ; do ( cd $dir ; make clean ) ; done ) rm -f dawglib.o debug.o rules.o stringlib.o *~ /bin/rm -f *.o tags core rpw destest des speed libdes.a .nfs* *.old *.bak destest rpw des speed rm -f *.o *~ `../../run/bin/freebsd-2-i386_/libc5.a' is up to date. cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -o ../../run/bin/freebsd-2-i386_/dictfilt dictfilt.c elcid.o ../../run/bin/freebsd-2-i386_/libc5.a cc: elcid.o: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. What do I do, and better yet, has anybody gotten it to work, and can simply e-mail a tar.gz file of crack that works on freebsd? Thanks, Steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 12:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12434 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 12:45:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12429 for ; Thu, 6 Aug 1998 12:45:38 -0700 (PDT) (envelope-from syang@directhit.com) Received: from moe.dirhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id PAA19771 for ; Thu, 6 Aug 1998 15:45:23 -0400 (EDT) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Thu, 6 Aug 1998 15:42:57 -0400 Message-ID: <839A86AB6CE4D111A52200104B938D4303D1E0@MOE> From: Steven Yang To: "'freebsd-hackers@freebsd.org'" Subject: addendum to How do you get crack to compile? Date: Thu, 6 Aug 1998 15:42:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, I did a "make spotless" and tried "Crack -fmt freebsd password-file" and got the following output: ... cc -O -DRAND -DTERMIOS -c speed.c cc -O -DRAND -DTERMIOS -o speed speed.o libdes.a + exec make XDIR=../../run/bin/freebsd-2-i386_ XCFLAGS=-g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H -DUSE_UNISTD_H -DUSE_PWD_H XCC=cc XLIB=../../run/bin/freebsd-2-i386_/libc5.a ../../run/bin/freebsd-2-i386_/libdes-cracker cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -c elcid.c cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -o ../../run/bin/freebsd-2-i386_/cracker cracker.c elcid.o ../../run/bin/freebsd-2-i386_/libc5.a ../libdes/libdes.a date > ../../run/bin/freebsd-2-i386_/libdes-cracker cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -o ../../run/bin/freebsd-2-i386_/dictfilt dictfilt.c elcid.o ../../run/bin/freebsd-2-i386_/libc5.a elcid.c:159: Undefined symbol `_crypt' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. Can anybody help? Thanks, Steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 13:03:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15623 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 13:03:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15580 for ; Thu, 6 Aug 1998 13:03:00 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with SMTP id QAA08693; Thu, 6 Aug 1998 16:02:30 -0400 (EDT) Date: Thu, 6 Aug 1998 16:02:30 -0400 (EDT) From: jack To: Steven Yang cc: "'freebsd-hackers@freebsd.org'" Subject: Re: how do you get crack to compile? In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1DF@MOE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG diamond# cd /usr/ports/security/crack/ diamond# make -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 13:31:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22918 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 13:31:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22829 for ; Thu, 6 Aug 1998 13:30:54 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA27489 for ; Thu, 6 Aug 1998 16:30:36 -0400 (EDT) Date: Thu, 6 Aug 1998 16:30:35 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: What does argdev mean? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could anyone tell me what does 'argdev' mean that appear routine bdevvp()? Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 13:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24778 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 13:38:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24655 for ; Thu, 6 Aug 1998 13:37:28 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4Wmc-0000ah-00; Thu, 6 Aug 1998 14:37:10 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id OAA17701; Thu, 6 Aug 1998 14:37:31 -0600 (MDT) Message-Id: <199808062037.OAA17701@harmony.village.org> To: Jason Thorpe Subject: Re: Anybody have... Cc: Mike Smith , Terry Lambert , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Aug 1998 09:46:32 PDT." <199808061646.JAA13156@lestat.nas.nasa.gov> References: <199808061646.JAA13156@lestat.nas.nasa.gov> Date: Thu, 06 Aug 1998 14:37:31 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808061646.JAA13156@lestat.nas.nasa.gov> Jason Thorpe writes: : I believe that Matt Thomas is writing a from-scratch WaveLAN driver for : NetBSD, and is planning on just using the '586 compatibility mode of : the '593 so that the same code can be used for the ISA and the PCMCIA : versions of the card. (The only real benefit from using the native : '593 mode, apparently, is slightly finer-grained control of the multicast : address filter... "big deal" :-) That would be cool.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 15:18:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20116 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 15:18:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20106 for ; Thu, 6 Aug 1998 15:18:11 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA26708 for freebsd-hackers@FreeBSD.ORG; Fri, 7 Aug 1998 00:17:53 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id E931A1549; Fri, 7 Aug 1998 00:08:07 +0200 (CEST) Message-ID: <19980807000807.A843@keltia.freenix.fr> Date: Fri, 7 Aug 1998 00:08:07 +0200 From: Ollivier Robert To: "'freebsd-hackers@freebsd.org'" Subject: Re: how do you get crack to compile? Mail-Followup-To: "'freebsd-hackers@freebsd.org'" References: <839A86AB6CE4D111A52200104B938D4303D1DF@MOE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1DF@MOE>; from Steven Yang on Thu, Aug 06, 1998 at 03:28:44PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4527 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Steven Yang: > Hi, I'm struggling to get crack to compile on freebsd. I'm on FreeBSD > 2.2.6, and I'm trying to get either crack 5.0 or crack 4.1 to work. > I've spent most of my time trying to get crack 5.0 to work, but the only > thing I've done that seems to help at all is to modifiy the makefile to > use -DTERMIOS rather than -DTERMIO. That gets it further through the > compiling, but now I run into: That's weird. I worked a long time ago with Alec to get it compile and run on FreeBSD (including the MD5/DES code). I was already using CURRENT but I don't think 2.2 is that different. Anyway, did you tried the port ? Port: crack-5.0 Path: /usr/ports/security/crack Info: the "Sensible" Unix Password Cracker. Maint: obrien@FreeBSD.org Index: security -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 15:18:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20169 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 15:18:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20133 for ; Thu, 6 Aug 1998 15:18:17 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA26709 for freebsd-hackers@FreeBSD.ORG; Fri, 7 Aug 1998 00:18:01 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 29763154A; Fri, 7 Aug 1998 00:08:41 +0200 (CEST) Message-ID: <19980807000841.B843@keltia.freenix.fr> Date: Fri, 7 Aug 1998 00:08:41 +0200 From: Ollivier Robert To: "'freebsd-hackers@freebsd.org'" Subject: Re: addendum to How do you get crack to compile? Mail-Followup-To: "'freebsd-hackers@freebsd.org'" References: <839A86AB6CE4D111A52200104B938D4303D1E0@MOE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1E0@MOE>; from Steven Yang on Thu, Aug 06, 1998 at 03:42:55PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4527 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Steven Yang: > elcid.c:159: Undefined symbol `_crypt' referenced from text segment It lacks a "-lcrypt" somewhere in the Makefile. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 16:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28504 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 16:05:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28495 for ; Thu, 6 Aug 1998 16:05:35 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA18475; Thu, 6 Aug 1998 16:05:20 -0700 (PDT) Message-ID: <19980806160520.B8872@Alameda.net> Date: Thu, 6 Aug 1998 16:05:20 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: Dmesg / MSGBUF_SIZE / LINT Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wouldn't it be nice to add to LINT a comment about MSGBUF_SIZE, that this is the parameter to increase for a larger dmesg boot buffer ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 16:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29288 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 16:09:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29267 for ; Thu, 6 Aug 1998 16:09:47 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id TAA28687; Thu, 6 Aug 1998 19:10:20 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Thu, 6 Aug 1998 19:10:20 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Steven Yang cc: "'freebsd-hackers@freebsd.org'" Subject: Re: addendum to How do you get crack to compile? In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1E0@MOE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG edit makefile, add "-lcrypt" to the line with the other "-l" then type make again. -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Thu, 6 Aug 1998, Steven Yang wrote: > Oh, I did a "make spotless" and tried > "Crack -fmt freebsd password-file" > and got the following output: > > ... > cc -O -DRAND -DTERMIOS -c speed.c > cc -O -DRAND -DTERMIOS -o speed speed.o libdes.a > + exec make XDIR=../../run/bin/freebsd-2-i386_ XCFLAGS=-g -O > -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H > -DUSE_UNISTD_H -DUSE_PWD_H XCC=cc > XLIB=../../run/bin/freebsd-2-i386_/libc5.a > ../../run/bin/freebsd-2-i386_/libdes-cracker > cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H > -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -c elcid.c > cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H > -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -o > ../../run/bin/freebsd-2-i386_/cracker cracker.c elcid.o > ../../run/bin/freebsd-2-i386_/libc5.a ../libdes/libdes.a > date > ../../run/bin/freebsd-2-i386_/libdes-cracker > cc -g -O -DUSE_STRING_H -DUSE_STDLIB_H -DUSE_SIGNAL_H -DUSE_SYS_TYPES_H > -DUSE_UNISTD_H -DUSE_PWD_H -I../lib -o > ../../run/bin/freebsd-2-i386_/dictfilt dictfilt.c elcid.o > ../../run/bin/freebsd-2-i386_/libc5.a > elcid.c:159: Undefined symbol `_crypt' referenced from text segment > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > Can anybody help? > Thanks, > Steven > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 16:11:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29674 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 16:11:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29602 for ; Thu, 6 Aug 1998 16:10:54 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-129.camalott.com [208.229.74.129]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA19405; Thu, 6 Aug 1998 18:11:47 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA01179; Thu, 6 Aug 1998 18:10:25 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 18:10:25 -0500 (CDT) Message-Id: <199808062310.SAA01179@detlev.UUCP> To: n@nectar.com CC: mcgovern@spoon.beta.com, hackers@FreeBSD.ORG In-reply-to: (message from Jacques Vidrine on Thu, 06 Aug 1998 01:52:17 -0500) Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807311744.NAA13956@spoon.beta.com> <199808060549.AAA13226@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> O_SHLOCK and O_EXLOCK are advisory, not mandatory. In other words, >> the apps are going to ignore them anyway. Lock files are the way to >> go. > Huh? > Sure, O_SHLOCK and O_EXLOCK are advisory, but so are lock files. > Applications are free to ignore any of them. I didn't mean to imply that lockfiles are mandatory. I meant that they are the recommended locking mechanism, since both are advisory anyway. All apps running now are pretty well guaranteed to not use flock. This is based on the fact that it doesn't work. A programmer being cautious enough to use flock would likely use uu lockfiles. So, use lockfiles so you can work with more apps. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 16:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01074 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 16:17:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01042 for ; Thu, 6 Aug 1998 16:17:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-129.camalott.com [208.229.74.129]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA19775; Thu, 6 Aug 1998 18:17:59 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA01215; Thu, 6 Aug 1998 18:16:37 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 18:16:37 -0500 (CDT) Message-Id: <199808062316.SAA01215@detlev.UUCP> To: mcgovern@spoon.beta.com CC: n@nectar.com, mcgovern@spoon.beta.com, hackers@FreeBSD.ORG In-reply-to: <199808061159.HAA01248@spoon.beta.com> (mcgovern@spoon.beta.com) Subject: Re: O_SHLOCK and O_EXLOCK - change to layering required? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808061159.HAA01248@spoon.beta.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yeah, but 80% of my problem is the fact they cause the open() call > on a device to fail with varying error codes, depending on the type > of device. On my own device, it appears that the error condition > occurs even before the driver open() call gets called. Oh, I see. I thought that it would return EOPNOTSUPP for all cases. > I think locking would be far more useful if locking would be passed > down through the layers until either a layer that COULD handle it > became involved, or the DRIVER said "Nope, not supported here", or > even silently ignored the lock request. Ugh. Don't silently ignore lock requests. Then you get corruption and don't know why. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23205 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:26:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23200 for ; Thu, 6 Aug 1998 18:26:25 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA06089; Thu, 6 Aug 1998 18:26:10 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd006072; Thu Aug 6 18:26:06 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA23982; Thu, 6 Aug 1998 18:26:02 -0700 (MST) From: Terry Lambert Message-Id: <199808070126.SAA23982@usr06.primenet.com> Subject: Re: O_SHLOCK and O_EXLOCK - change to layering required? To: mcgovern@spoon.beta.com (Brian J. McGovern) Date: Fri, 7 Aug 1998 01:26:02 +0000 (GMT) Cc: n@nectar.com, joelh@gnu.org, mcgovern@spoon.beta.com, hackers@FreeBSD.ORG In-Reply-To: <199808061159.HAA01248@spoon.beta.com> from "Brian J. McGovern" at Aug 6, 98 07:59:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Huh? > > >Sure, O_SHLOCK and O_EXLOCK are advisory, but so are lock files. > >Applications are free to ignore any of them. > > >Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org > > Yeah, but 80% of my problem is the fact they cause the open() call on a device > to fail with varying error codes, depending on the type of device. No it doesn't. All device opens fail with: EOPNOTSUPP >From /sys/miscfs/specfs/spec_vnops.c, spec_advlock(). Before the lock is attempted, the open is attempted (you can call VOP_ADVLOCK() on a vinode until after you have a vnode). So if you are getting a different error, your open() call is failing before it even attempts the lock. The problem here is struct fileops: an open device uses a different struct fileops; it is not a VFS-based implementation of fileops (per the code in /sys/kern/vfs_vnops.c). I actually made this work a while back; the struct fileops is referenced off the vnode pointer for the device (ie: it is one of three vnode types that aren't backed directly by a VFS implementation). The fix involves hanging the advisory locking list off the vnode instead of teh inode. It was part of my patches to support NFS locking (specifically, part of making VOP_ADVLOCK be veto-based). This would mean that there was a data structure associated with the system object instance instead of an alias (in other words, the vnode, not the inode, and not a device open instance specific data structure) that was in common that all implementations, independant of whether a non-standard struct fileops was used. For the coup-de-grace, you would modify VOP_ADVLOCK() in specfs to return 0 (success) -- and not veto the operation by the upper level code (after the non veto, the proposed lock would be coelesced, in accordance to UNIX locking semantics being a two dimensional projection of a three dimensional set of lock relationships; just like when an NFS server didn't veto an NFS clients lock, in my code). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:28:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23581 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:28:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23576 for ; Thu, 6 Aug 1998 18:28:52 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA29601; Thu, 6 Aug 1998 18:28:38 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd029563; Thu Aug 6 18:28:32 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA24293; Thu, 6 Aug 1998 18:28:28 -0700 (MST) From: Terry Lambert Message-Id: <199808070128.SAA24293@usr06.primenet.com> Subject: Re: Anybody have... To: thorpej@nas.nasa.gov Date: Fri, 7 Aug 1998 01:28:28 +0000 (GMT) Cc: imp@village.org, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199808060653.XAA05901@lestat.nas.nasa.gov> from "Jason Thorpe" at Aug 5, 98 11:53:06 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : I believe this is the AT&T card Garrett originall wrote the driver for. > > > > Does this mean that you have a datasheet for it? The i82593 that I > > have is on an IBM wireless card that has an IBM chip on it, so itis > > unlikely that it is the same card. However, if you have info on it, > > I'd love to hear about it... > > Garrett wrote a driver for the i82586. I think the i82593 is what is > used in the WaveLAN, yes? I think it also has an i82586 mode. It was my opnion that I'd used Garrett's driver with an i82593. This does *not* mean I have a datasheet for it, but that the CVS repository might have a driver for it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24344 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:33:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24333 for ; Thu, 6 Aug 1998 18:33:37 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA01207; Thu, 6 Aug 1998 18:33:20 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd001123; Thu Aug 6 18:33:09 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA24688; Thu, 6 Aug 1998 18:33:05 -0700 (MST) From: Terry Lambert Message-Id: <199808070133.SAA24688@usr06.primenet.com> Subject: Re: C and static initialization with unions To: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu) Date: Fri, 7 Aug 1998 01:33:05 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980806113159.49110@breizh.prism.uvsq.fr> from "Nicolas Souchu" at Aug 6, 98 11:31:59 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? Good question; I don't know the answer. I know that FreeBSD uses inline assembly, rather than seperating out the assembly code into machine-specific compilation units (preferrably with vanilla C equivalents, where possible). I also know that FreeBSD uses ANSI constructs, which make the code non-portable to older compilers, such as those you would have on machines running older OS's that you want to upgrade to running FreeBSD via a port. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:37:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24929 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:37:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24888 for ; Thu, 6 Aug 1998 18:36:55 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA02306; Thu, 6 Aug 1998 18:36:39 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd002281; Thu Aug 6 18:36:34 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA24978; Thu, 6 Aug 1998 18:36:32 -0700 (MST) From: Terry Lambert Message-Id: <199808070136.SAA24978@usr06.primenet.com> Subject: Re: C and static initialization with unions To: jdp@polstra.com (John Polstra) Date: Fri, 7 Aug 1998 01:36:31 +0000 (GMT) Cc: Nicolas.Souchu@prism.uvsq.fr, hackers@FreeBSD.ORG In-Reply-To: <199808061622.JAA26353@austin.polstra.com> from "John Polstra" at Aug 6, 98 09:22:37 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is all FreeBSD C source code portable? > > GCC extensions are occasionally used in FreeBSD. However, they > are virtually always optional and for the purpose of (a) better > efficiency, or (b) better compiler warnings. When GCC extensions are > used, they are protected by "#ifdef __GNUC__", and an alternative > portable implementation is provided in the "#else" clause. For case > (a) the alternative implementation is less efficient; for case (b), > it's a no-op. See for some examples of (b). This is not quite correct. The defined __P(), for example, and this appears to have been deprecated despite its ability to ensure portability; which is really bizarre, because "const", "volatile", and __CONCAT() all haven't, and it the same portability barrier that all 4 address (non-ANSI K&R compilers). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25754 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:41:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25717 for ; Thu, 6 Aug 1998 18:41:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA01445; Thu, 6 Aug 1998 18:38:37 -0700 (PDT) Message-Id: <199808070138.SAA01445@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu), mike@smith.net.au, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 01:33:05 -0000." <199808070133.SAA24688@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 18:38:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? > > Good question; I don't know the answer. > > I know that FreeBSD uses inline assembly, rather than seperating > out the assembly code into machine-specific compilation units > (preferrably with vanilla C equivalents, where possible). Actually, we largely do separate into compilation units. See all those files ending in '.s' and '.S'? > I also know that FreeBSD uses ANSI constructs, which make the > code non-portable to older compilers, such as those you would > have on machines running older OS's that you want to upgrade > to running FreeBSD via a port. Seeing as nobody actually seems to want this, it's obviously not of much interest. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 18:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26306 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 18:43:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from utopia.poly.edu (utopia.poly.edu [128.238.3.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26272 for ; Thu, 6 Aug 1998 18:43:22 -0700 (PDT) (envelope-from smun01@utopia.poly.edu) Received: from utopia.poly.edu (smun01@utopia.poly.edu [128.238.3.21]) by utopia.poly.edu (8.8.8/8.8.8) with SMTP id VAA10182 for ; Thu, 6 Aug 1998 21:43:05 -0400 (EDT) Date: Thu, 6 Aug 1998 21:43:05 -0400 (EDT) From: "SeungH. Mun(Pirate)" To: freebsd-hackers@FreeBSD.ORG Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe PGP easy steps.. * generate your key: 1. pgp -kg 2. pgp -kv 3. pgp -kxa * add your pals key: 1. pgp -ka 2. pgp -kv * encrypt: 1. pgp -e "UID" * decryp: 2. pgp -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3a mQCNAzKmYiwAAAEEALY7D02uDdoozKvWfQuyazvqbIZwEbDw067MnVrr7FczW+YN FJeIxfkC5hLkVC0sxbsg9mF36b5t+adYp6PdDfZ5V+YJ5akultsHWy2ZlckXKb72 uQNqZ6n59apaTeR4ymcC6ZmsTrzEWf99HX75KO+999zd0p8+JZvL3+UCRev9AAUR tCBTZWFXMGxmIDxzbXVuMDFAdXRvcGlhLnBvbHkuZWR1PokAlQMFEDKmYiyby9/l AkXr/QEBrLYD/21Rha4A8rPeLNKeNcBjjlLZfmQQWuJTrMD/a1gaiuJqH85onA1a JySNmrk5PZxZ749GuItiGnVsxRrPAO/fUQYj9Xxl+IdGo/HV5coD/kTXG8Bm+Q0y aUlIBFTBCEuE/9SecolS4c0E5ZG2LUbltmma/SFEKiK30jmC8ymPATNn =oCE+ -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 19:25:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04802 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 19:25:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04781 for ; Thu, 6 Aug 1998 19:25:05 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id WAA26430; Thu, 6 Aug 1998 22:24:24 -0400 (EDT) Message-Id: <199808070224.WAA26430@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Terry Lambert , imp@village.org (Warner Losh), hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Anybody have... References: <199808060653.XAA00923@antipodes.cdrom.com> In-reply-to: Your message of "Wed, 05 Aug 1998 23:53:42 PDT." <199808060653.XAA00923@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 22:24:24 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You're probably thinking of the 82586. The 82593 is an old low-power > device, used in eg. the Wavelan PCCARD adapters and some IBM notebooks. > (I don't think that Garrett wrote the PCCARD Wavelan > driver.) > > It seems laughable to me that Intel wouldn't be able to offer a > datasheet on such a part, when you can still get datasheets on the 8255. > > It's not clear whether the datasheet for the 82595 would shed any light > on what you're currently trying to work out, but it's worth a stab. As I recall at the time, we looked at the 82595 datasheets, and it's a bit of a different animal. The 82593 presumes the laptop sort of environment, along with a dedicated DMA controllers that's configured in "wrap" mode. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 19:28:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05149 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 19:28:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05088 for ; Thu, 6 Aug 1998 19:27:56 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id MAA02971; Fri, 7 Aug 1998 12:32:23 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070232.MAA02971@cimlogic.com.au> Subject: Re: C and static initialization with unions In-Reply-To: <199808070138.SAA01445@dingo.cdrom.com> from Mike Smith at "Aug 6, 98 06:38:37 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 7 Aug 1998 12:32:23 +1000 (EST) Cc: tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I also know that FreeBSD uses ANSI constructs, which make the > > code non-portable to older compilers, such as those you would > > have on machines running older OS's that you want to upgrade > > to running FreeBSD via a port. > > Seeing as nobody actually seems to want this, it's obviously not of > much interest. ... and these days it seems that the GNU tools get ported to the "older" OS first and you just use them. So unless there is a late rush of people wanting to port FreeBSD to another processor for which GNU tools don't exist, I'd prefer to see the K&R bit dropped in favour of ANSI C and get people to learn to compile things with compiler higher warning levels. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 19:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05734 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 19:32:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05676 for ; Thu, 6 Aug 1998 19:32:25 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id WAA26463; Thu, 6 Aug 1998 22:32:03 -0400 (EDT) Message-Id: <199808070232.WAA26463@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Anybody have... References: <199808060549.BAA24198@whizzo.transsys.com> <199808060135.TAA09279@harmony.village.org> <199808060603.AAA12615@harmony.village.org> In-reply-to: Your message of "Thu, 06 Aug 1998 00:03:23 MDT." <199808060603.AAA12615@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 22:32:02 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199808060549.BAA24198@whizzo.transsys.com> "Louis A. Mamakos" writes: > : I know that I have the Intel databook for this part *somewhere*, but I > : haven't seen it since I moved a year and a half ago. I think you'll get > : quite a head starting with the NetBSD driver, though. The driver is a > : little grotty in the sense that it's an 82593 driver for the Zenith laptop > : and it needs to do some rather rude DMA controller setup because of the > : way the 82593 works. Take a look at the code; you'll see. > > I just looked at the code. *ICKY* is the best way to describe it. If > you can find the databook, I'd add you to the growing list of people I > owe beers to for this project.... It seems that while I can't find the data "sheet"/booklet for the 82593 that I used when hacking on the drive, it is in the 1993 version of the Intel "Connectivity" databook that I have. I'll take it into work next week, and copy the relevent pages. I can either mail or fax them to you. Also, I don't think that this part as an 82585 compatability mode. There is some discussion on changes from the 82590 part. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 19:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07119 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 19:41:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07107 for ; Thu, 6 Aug 1998 19:41:44 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-119.camalott.com [208.229.74.119]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id VAA01081; Thu, 6 Aug 1998 21:42:20 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id VAA01590; Thu, 6 Aug 1998 21:40:56 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 21:40:56 -0500 (CDT) Message-Id: <199808070240.VAA01590@detlev.UUCP> To: tlambert@primenet.com CC: Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, tlambert@primenet.com, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: <199808070133.SAA24688@usr06.primenet.com> (message from Terry Lambert on Fri, 7 Aug 1998 01:33:05 +0000 (GMT)) Subject: Re: C and static initialization with unions From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808070133.SAA24688@usr06.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I also know that FreeBSD uses ANSI constructs, which make the > code non-portable to older compilers, such as those you would > have on machines running older OS's that you want to upgrade > to running FreeBSD via a port. Although many compilers are considerably more K&R friendly, so you could bootstrap in many (not all) cases. -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 19:54:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08597 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 19:54:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08592 for ; Thu, 6 Aug 1998 19:54:48 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA11170; Thu, 6 Aug 1998 19:50:44 -0700 (PDT) Message-Id: <199808070250.TAA11170@implode.root.com> To: "Louis A. Mamakos" cc: Mike Smith , Terry Lambert , imp@village.org (Warner Losh), hackers@FreeBSD.ORG Subject: Re: Anybody have... In-reply-to: Your message of "Thu, 06 Aug 1998 22:24:24 EDT." <199808070224.WAA26430@whizzo.transsys.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Aug 1998 19:50:44 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> You're probably thinking of the 82586. The 82593 is an old low-power >> device, used in eg. the Wavelan PCCARD adapters and some IBM notebooks. >> (I don't think that Garrett wrote the PCCARD Wavelan >> driver.) >> >> It seems laughable to me that Intel wouldn't be able to offer a >> datasheet on such a part, when you can still get datasheets on the 8255. >> >> It's not clear whether the datasheet for the 82595 would shed any light >> on what you're currently trying to work out, but it's worth a stab. > >As I recall at the time, we looked at the 82595 datasheets, and it's a >bit of a different animal. The 82593 presumes the laptop sort of environment, >along with a dedicated DMA controllers that's configured in "wrap" mode. Jim Binkley wrote a FreeBSD driver for the WaveLAN. Perhaps that will be of some use to you (whoever it was that first asked)... -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 20:03:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09637 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 20:03:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (seoul-195.ppp.hooked.net [206.169.228.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09630 for ; Thu, 6 Aug 1998 20:03:01 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id TAA03181; Thu, 6 Aug 1998 19:10:27 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 6 Aug 1998 19:10:21 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Ted Faber cc: Nicolas Souchu , Mike Smith , Terry Lambert , Chuck Robey , freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: <199808061732.KAA09052@tnt.isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Ted Faber wrote: [...] > And, of course, all FreeBSD source is portable. :-) :-) :-) So when will someone try replacing gcc with TenDRA, yadda yadda, and getting a make world built with tcc and a make world to build tcc? - alex A person who has both feet planted firmly in the air can be safely called a liberal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 20:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10391 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 20:08:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shawn.holwegner.com (holwegner.com [205.158.165.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10263 for ; Thu, 6 Aug 1998 20:07:52 -0700 (PDT) (envelope-from shawn@shawn.holwegner.com) Received: (from shawn@localhost) by shawn.holwegner.com (8.9.1/8.8.8) id DAA00266; Fri, 7 Aug 1998 03:07:37 GMT (envelope-from shawn) Message-ID: <19980807030736.10985@holwegner.com> Date: Fri, 7 Aug 1998 03:07:36 +0000 From: Shawn Holwegner To: freebsd-hackers@FreeBSD.ORG Subject: PnP configuration with intel PV440FX Reply-To: shawn@holwegner.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Please pardon this message if you feel this is in the wrong area, but virtually everywhere else I checked, no one had a clue. I have recently aquired an intel providence 440FX motherboard with an onboard crystal codec. Everything is working perfectly *BUT* the sound. I have supped 3.0-Current to date, and have ... controller pnp0 device pcm0 at isa? port 0x530 tty irq ? drq 1 flags 0x0 vector pcmintr (have tried with port 0x534 where OSS identifies 'SoundPort' as being, as well has hard coded irqs, not set drq nor flags, etc, etc.) ... It does see it: CSN 1 Vendor ID: CSC0b35... I have attempted to configure this as follows: configure>pnp 1 0 os enable irq0 5 drq0 1 port0 0x530 flags 0x0 (again with different irqs and ports), to no avail. If I boot a non-smp kernel, I can load OSS which sees the codec fine: SoundPort 0x534, irq 7, drq 1,0. This does present a bit of a problem, as I am not going to run a non-smp enabled kernel just for this codec, OSS currently hasnt redefined its useage of _imen to _apic_imen, and I am nearly at my wits end, as the bios in this evil critter gives me a resource error when i put an Esoniq AudioPCI in it. Thanks for any help. - Shawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 20:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15464 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 20:46:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15447 for ; Thu, 6 Aug 1998 20:46:38 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4dTw-0000mo-00; Thu, 6 Aug 1998 21:46:20 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id VAA21860; Thu, 6 Aug 1998 21:46:45 -0600 (MDT) Message-Id: <199808070346.VAA21860@harmony.village.org> To: "Louis A. Mamakos" Subject: Re: Anybody have... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Aug 1998 22:32:02 EDT." <199808070232.WAA26463@whizzo.transsys.com> References: <199808070232.WAA26463@whizzo.transsys.com> <199808060549.BAA24198@whizzo.transsys.com> <199808060135.TAA09279@harmony.village.org> <199808060603.AAA12615@harmony.village.org> Date: Thu, 06 Aug 1998 21:46:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808070232.WAA26463@whizzo.transsys.com> "Louis A. Mamakos" writes: : I'll take it into work next week, and copy the relevent pages. I can : either mail or fax them to you. How many pages are we talking about here? If it is more than, say, 10, then it would be better to mail them to me. Warner Losh 8786 Niwot Rd Niwot CO 80503 Can I compensate you for your time, materials and efforts? : Also, I don't think that this part as an 82585 compatability mode. There : is some discussion on changes from the 82590 part. Yes. I'd be very interested in that part. The 82586 is much easier to deal with... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 20:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15761 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 20:49:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15748 for ; Thu, 6 Aug 1998 20:49:25 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA29774; Thu, 6 Aug 1998 20:49:05 -0700 (PDT) (envelope-from jdp) Message-Id: <199808070349.UAA29774@austin.polstra.com> To: Terry Lambert cc: Nicolas.Souchu@prism.uvsq.fr, hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 01:36:31 -0000." <199808070136.SAA24978@usr06.primenet.com> Date: Thu, 06 Aug 1998 20:49:05 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > GCC extensions are occasionally used in FreeBSD. However, they > > are virtually always optional and for the purpose of (a) better > > efficiency, or (b) better compiler warnings. When GCC extensions are > > used, they are protected by "#ifdef __GNUC__", and an alternative > > portable implementation is provided in the "#else" clause. For case > > (a) the alternative implementation is less efficient; for case (b), > > it's a no-op. See for some examples of (b). > > This is not quite correct. The defined __P(), for > example, and this appears to have been deprecated despite its > ability to ensure portability; which is really bizarre, because > "const", "volatile", and __CONCAT() all haven't, and it the same > portability barrier that all 4 address (non-ANSI K&R compilers). I was talking about GCC extensions (extra-ANSI), and you are talking about K&R vs. ANSI. Those are different topics. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 6 23:00:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01304 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 23:00:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA01299 for ; Thu, 6 Aug 1998 23:00:26 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA14871; Fri, 7 Aug 1998 06:11:03 +0200 From: Luigi Rizzo Message-Id: <199808070411.GAA14871@labinfo.iet.unipi.it> Subject: Re: PnP configuration with intel PV440FX To: shawn@holwegner.com Date: Fri, 7 Aug 1998 06:11:02 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980807030736.10985@holwegner.com> from "Shawn Holwegner" at Aug 7, 98 03:07:17 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > controller pnp0 > device pcm0 at isa? port 0x530 tty irq ? drq 1 flags 0x0 vector pcmintr > (have tried with port 0x534 where OSS identifies 'SoundPort' as being, > as well has hard coded irqs, not set drq nor flags, etc, etc.) you need to supply an IRQ for legacy isa devices. the driver can not guess it. > It does see it: > > CSN 1 Vendor ID: CSC0b35... > > I have attempted to configure this as follows: > > configure>pnp 1 0 os enable irq0 5 drq0 1 port0 0x530 flags 0x0 > (again with different irqs and ports), to no avail. i am pretty sure it is recognized as unit #1 luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11772 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:11:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11754 for ; Fri, 7 Aug 1998 00:11:47 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id AAA08450; Fri, 7 Aug 1998 00:11:29 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd008435; Fri Aug 7 00:11:27 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA21912; Fri, 7 Aug 1998 00:11:23 -0700 (MST) From: Terry Lambert Message-Id: <199808070711.AAA21912@usr08.primenet.com> Subject: Re: C and static initialization with unions To: mike@smith.net.au (Mike Smith) Date: Fri, 7 Aug 1998 07:11:22 +0000 (GMT) Cc: tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808070138.SAA01445@dingo.cdrom.com> from "Mike Smith" at Aug 6, 98 06:38:37 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? > > > > Good question; I don't know the answer. > > > > I know that FreeBSD uses inline assembly, rather than seperating > > out the assembly code into machine-specific compilation units > > (preferrably with vanilla C equivalents, where possible). > > Actually, we largely do separate into compilation units. See all those > files ending in '.s' and '.S'? Ah! So FreeBSD will compile with TenDRA? Sorry about the mistake, then... > > I also know that FreeBSD uses ANSI constructs, which make the > > code non-portable to older compilers, such as those you would > > have on machines running older OS's that you want to upgrade > > to running FreeBSD via a port. > > Seeing as nobody actually seems to want this, it's obviously not of > much interest. I want it; I'm usually shouted down. At the very least, an internally consistent policy would be nice... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12113 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:13:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12091 for ; Fri, 7 Aug 1998 00:13:47 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA25483; Fri, 7 Aug 1998 00:13:32 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd025438; Fri Aug 7 00:13:24 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA22022; Fri, 7 Aug 1998 00:13:17 -0700 (MST) From: Terry Lambert Message-Id: <199808070713.AAA22022@usr08.primenet.com> Subject: Re: C and static initialization with unions To: garbanzo@hooked.net (Alex) Date: Fri, 7 Aug 1998 07:13:17 +0000 (GMT) Cc: faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, tlambert@primenet.com, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Alex" at Aug 6, 98 07:10:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So when will someone try replacing gcc with TenDRA, yadda yadda, and > getting a make world built with tcc and a make world to build tcc? I tried this once. The .mk file unfortunately replace include paths, making no distinction between build environments and targets, which is truly unfortunate. It means I can't even build FreeBSD with the next revision of GCC (a port), since it gets the wrong libgcc.a... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:19:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13516 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:19:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13493 for ; Fri, 7 Aug 1998 00:19:16 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA26394; Fri, 7 Aug 1998 00:19:01 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd026373; Fri Aug 7 00:18:51 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA22234; Fri, 7 Aug 1998 00:18:48 -0700 (MST) From: Terry Lambert Message-Id: <199808070718.AAA22234@usr08.primenet.com> Subject: Re: C and static initialization with unions To: jdp@polstra.com (John Polstra) Date: Fri, 7 Aug 1998 07:18:48 +0000 (GMT) Cc: tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, hackers@FreeBSD.ORG In-Reply-To: <199808070349.UAA29774@austin.polstra.com> from "John Polstra" at Aug 6, 98 08:49:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was talking about GCC extensions (extra-ANSI), and you are talking > about K&R vs. ANSI. Those are different topics. I thought the topic was portability of the code, not portability of the GNU tools... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14857 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:24:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14760 for ; Fri, 7 Aug 1998 00:24:17 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA18937; Fri, 7 Aug 1998 09:23:40 +0200 (MET DST) Date: Fri, 7 Aug 1998 09:23:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Ulf Zimmermann cc: FreeBSD hackers mailing list Subject: Re: Dmesg / MSGBUF_SIZE / LINT In-Reply-To: <19980806160520.B8872@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Wouldn't it be nice to add to LINT a comment about MSGBUF_SIZE, that this > is the parameter to increase for a larger dmesg boot buffer ? That sounds like a very fancy and useful idea... Not that I have that many devices, but a sio that keeps on overflowing and me not having the time to fix it... So if I want to see the dmesg output I always have to go and look at the messages file. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:31:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16651 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:31:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16641 for ; Fri, 7 Aug 1998 00:31:36 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA28180; Fri, 7 Aug 1998 00:31:21 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd028165; Fri Aug 7 00:31:19 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA22800; Fri, 7 Aug 1998 00:31:14 -0700 (MST) From: Terry Lambert Message-Id: <199808070731.AAA22800@usr08.primenet.com> Subject: Re: C and static initialization with unions To: mike@smith.net.au (Mike Smith) Date: Fri, 7 Aug 1998 07:31:14 +0000 (GMT) Cc: tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808070138.SAA01445@dingo.cdrom.com> from "Mike Smith" at Aug 6, 98 06:38:37 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I know that FreeBSD uses inline assembly, rather than seperating > > out the assembly code into machine-specific compilation units > > (preferrably with vanilla C equivalents, where possible). > > Actually, we largely do separate into compilation units. See all those > files ending in '.s' and '.S'? I just grepp'ed for "asm(.*)" and piped to wc -l. The result was a non-zero count. > > I also know that FreeBSD uses ANSI constructs, which make the > > code non-portable to older compilers, such as those you would > > have on machines running older OS's that you want to upgrade > > to running FreeBSD via a port. > > Seeing as nobody actually seems to want this, it's obviously not of > much interest. I would dearly love this. Say "nobody who counts", please... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:32:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16935 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:32:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16910 for ; Fri, 7 Aug 1998 00:32:11 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA07132; Fri, 7 Aug 1998 09:31:45 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 09:31:44 +0200 (MET DST) Mime-Version: 1.0 To: Alfred Perlstein Cc: Steven Yang , "'freebsd-hackers@freebsd.org'" Subject: Re: addendum to How do you get crack to compile? References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 09:31:44 +0200 In-Reply-To: Alfred Perlstein's message of "Thu, 6 Aug 1998 19:10:20 -0500 (EST)" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA16925 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > On Thu, 6 Aug 1998, Steven Yang wrote: > > Oh, I did a "make spotless" and tried > > "Crack -fmt freebsd password-file" > > and got the following output: > edit makefile, add "-lcrypt" to the line with the other "-l" > then type make again. But crack is in the ports, it shouldn't be necessary to do anything but this: # cd /usr/ports/security/crack # make install clean DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18570 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:40:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18517 for ; Fri, 7 Aug 1998 00:40:10 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA00997; Fri, 7 Aug 1998 00:39:49 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd000967; Fri Aug 7 00:39:41 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA23183; Fri, 7 Aug 1998 00:39:35 -0700 (MST) From: Terry Lambert Message-Id: <199808070739.AAA23183@usr08.primenet.com> Subject: Re: C and static initialization with unions To: jb@cimlogic.com.au (John Birrell) Date: Fri, 7 Aug 1998 07:39:35 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808070232.MAA02971@cimlogic.com.au> from "John Birrell" at Aug 7, 98 12:32:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Seeing as nobody actually seems to want this, it's obviously not of > > much interest. > > ... and these days it seems that the GNU tools get ported to the "older" > OS first and you just use them. I am sorry. I vehemently disagree with the GPL as a political tool. I will not port GCC to a new platform. I also believe that having to port the compiler is a ridiculous barrier to entry, and one of the reasons FreeBSD ports are not more prevalent. > So unless there is a late rush of people wanting to port FreeBSD to another > processor for which GNU tools don't exist, I'd prefer to see the K&R bit > dropped in favour of ANSI C and get people to learn to compile things with > compiler higher warning levels. It's perfectly possible to get these warnings from a K&R compiler. To do this, you need to change your object format to attribute the symbol table entries. Fred Fish did this for the Motorolla 88k compiler back in the early 80's. What we are suffering here is a legacy of compiler writers too lazy to implement decent smart linker technology. It is entirely possible to take interface errors at link time rather than compile time and/or generate conversion stubs an issue warnings, rather than requiring prototypes to be in scope. Prototypes are a case of compiler writers being lazy. Specifically, Microsoft compiler writers who wanted to transparently deal with "far *" in the Windows 3.x developement environement, and SunSoft compiler writers who wanted to win compiler races rather than provide correct code. This is the same reason we have volatile: because there is no inter-module optimization due to the lack of sufficient hints in the object files and the generation of glue code at link time instead of runtime. In any case, it's technically *possible* to have avoided this cock-up, it just wasn't financially expedient to do so... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:53:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20501 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:53:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beast.freibergnet.de (beast.freibergnet.de [194.123.255.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20472; Fri, 7 Aug 1998 00:53:16 -0700 (PDT) (envelope-from mw@freibergnet.de) Received: from zoo.freibergnet.de (zoo.freibergnet.de [194.123.255.71]) by beast.freibergnet.de (8.8.5/8.8.8) with ESMTP id JAA20581; Fri, 7 Aug 1998 09:52:44 +0200 (CEST) (envelope-from mw@freibergnet.de) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <35C9DD28.2E9749D3@webber.net.ua> Date: Fri, 07 Aug 1998 09:52:03 +0200 (CEST) Reply-To: mw@freibergnet.de Organization: FreibergNet Liebscher & Partner Werbeagentur und XLink-PoP Freiberg From: Martin Welk To: Andrew Petrenko Subject: RE: SCO binaries and FreeBSD 2.2.7-stable Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, "freebsd-questions@FreeBSD.ORG" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Aug-98 Andrew Petrenko wrote: () Need help. () i run FoxPro 2.6. for SCO on FreeBSD and get error () () Too many files open. () () in login.conf i set () ... () openfiles=254 () openfiles-cur=254 () ... () () what can i do for run FoxPro? I haven't run FoxPro, but probably editing login.conf is not enough: have you built a custom kernel? Have a look at /sys/i386/conf/LINT: # # Under some circumstances it is convenient to increase the defaults # for the maximum number of processes per user and the maximum number # of open files files per user. E.g., (1) in a large news server, user # `news' may need more than 100 concurrent processes. (2) a user may # need lots of windows under X. In both cases, it may be inconvenient # to start all the processes from a parent whose soft rlimit on the # number of processes is large enough. The following options work by # changing the soft rlimits for init. # options CHILD_MAX=128 options OPEN_MAX=128 This may be the limitation you run into. If you haven't already made a custom kernel, it's a good point to start with /sys/i386/conf/GENERIC: copy it, and add the options mentioned above and increase them. For my desktop machine, I've used 256/256, as that's yet enough (although with 128 MByte RAM I wouldn't have problems increasing it more, it's just being somewhat conventional). For building a new kernel, consult the documentation - look at the FreeBSD handbook, section 19 (Add New Kernel Configuration Options). If you have already made that, check your user limits. May be, you have done something wrong in /etc/login.conf or simply haven't added the appropriate class for the login in /etc/passwd. I'm using bash 2.01.1 as included in the ports for 2.2.6-RELEASE, the built-in ulimit command gives the necessary information: mw@zoo:/home/wheel/mw 659 $ ulimit -a core file size (blocks) unlimited data seg size (kbytes) 262144 file size (blocks) unlimited max locked memory (kbytes) unlimited max memory size (kbytes) 32768 open files 1024 pipe size (512 bytes) 1 stack size (kbytes) 65536 cpu time (seconds) unlimited max user processes 64 virtual memory (kbytes) 327680 Dunno about other shells. As I'm simply to lazy to change the information to something making more sense, I've given myself same limits as the root account, because of that I never have to care about limits. You'll have to check for your own if this is a good way :-) As I'm the only one working on my machine, it's no problem. And if some application crashes or eats up memory, I don't have to care, at least, not yet :-) Regards, Martin -- Liebscher & Partner Werbeagentur GbR // Martin Welk Advertising, Art Design & DTP // network administration Xlink Point Of Presence Freiberg // phone: (+49|0) 3731 781-387 Am St. Niclas Schacht 13 // fax: (+49|0) 3731 781-377 D-09599 Freiberg, Germany // http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20703 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:54:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20559 for ; Fri, 7 Aug 1998 00:54:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id RAA03868; Fri, 7 Aug 1998 17:58:53 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070758.RAA03868@cimlogic.com.au> Subject: Re: C and static initialization with unions In-Reply-To: <199808070739.AAA23183@usr08.primenet.com> from Terry Lambert at "Aug 7, 98 07:39:35 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 7 Aug 1998 17:58:53 +1000 (EST) Cc: jb@cimlogic.com.au, mike@smith.net.au, tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > I am sorry. I vehemently disagree with the GPL as a political tool. > I will not port GCC to a new platform. I don't like the GPL either, so I'll never vote for it if it stands for election 8-). To me gcc is not the poison it is to you. To me it is like public transportation - I prefer not to use it because other modes are more fun, but if it is expedient for me to do so, then I will. What I don't like is people pushing K&R on me for reasons that never seem to eventuate. Where are these people who will need K&R so much that providing it will make the FreeBSD world a better place?! > I also believe that having to port the compiler is a ridiculous barrier > to entry, and one of the reasons FreeBSD ports are not more prevalent. Crap. FreeBSD ports are not more prevalent because some people spend more time doing the yadda yadda than actually getting off their butts and doing something to contribute. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 00:59:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21482 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 00:59:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21430 for ; Fri, 7 Aug 1998 00:58:45 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id IAA24405 for ; Fri, 7 Aug 1998 08:58:28 +0100 (BST) Message-ID: <35CAB3C7.4A6B776D@tdx.co.uk> Date: Fri, 07 Aug 1998 08:59:03 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: getpwuid - after chroot? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there a workaround for using getpwuid() after you've chroot'd at all? - e.g. with the code below? I think the reason it _doesn't_ work is because once you've chroot'd the system can't get back to the '/etc/pwd.db' file etc.? - Is there any way round this? Apparently the following code does actually work on other systems... Someone mentioned Linux, but I don't have access to any Linux boxes to test it ;-) Regards, Karl Pielorz ---- #include #include #include #include int main() { setpassent(1); getpwent(); chroot("/usr"); chdir("/"); if(!getpwuid(0)) { printf("setpassent doesn't appear to work\n"); } else { if(!getpwuid(0)) printf("second getpwuid(0) didn't work\n"); else printf("setpassent works\n"); } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 05:41:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28985 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 05:41:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.relay.net (ns.relay.net [140.174.206.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA28975 for ; Fri, 7 Aug 1998 05:41:09 -0700 (PDT) (envelope-from freebsd@piet.net) Received: by ns.relay.net (Smail3.1.28.1 #5) id m0z4lpA-002JuoC; Fri, 7 Aug 98 05:40 PDT Received: from ppp.piet.net(140.174.113.3), claiming to be "piet.net" via SMTP by shemp.relay.net, id smtpd019533; Fri Aug 7 12:40:33 1998 Received: by piet.net id AA02310 (5.67b/IDA-1.5); Fri, 7 Aug 1998 05:39:59 -0700 Date: Fri, 7 Aug 1998 05:39:59 -0700 From: FreeBSD Mail Message-Id: <199808071239.AA02310@piet.net> To: grog@lemis.com, jkh@time.cdrom.com Subject: Re: Remote gdb (was: no boot: config -g and options DDB) Cc: hasty@rah.star-gate.com, julian@whistle.com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I still think it's too much of an intervention in the kernel to solve > > all cases, but if you find time to do it, I'm sure I also will be > > grateful. > > I'm also wondering how you'd use it to debug problems in the TCP > stack or NIC driver. :-) The debugger uses a stripped down tcp/ip stack of it's own. -piet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 06:26:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04516 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 06:26:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles349.castles.com [208.214.167.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04494 for ; Fri, 7 Aug 1998 06:26:38 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id GAA00589; Fri, 7 Aug 1998 06:24:57 -0700 (PDT) Message-Id: <199808071324.GAA00589@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), Nicolas.Souchu@prism.uvsq.fr, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 07:31:14 -0000." <199808070731.AAA22800@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 06:24:56 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I know that FreeBSD uses inline assembly, rather than seperating > > > out the assembly code into machine-specific compilation units > > > (preferrably with vanilla C equivalents, where possible). > > > > Actually, we largely do separate into compilation units. See all those > > files ending in '.s' and '.S'? > > I just grepp'ed for "asm(.*)" and piped to wc -l. The result was a > non-zero count. "largely" is a relative, not absolute, expression. Mock me not for the sins of others, especially where said sins are in your eyes alone. > > > I also know that FreeBSD uses ANSI constructs, which make the > > > code non-portable to older compilers, such as those you would > > > have on machines running older OS's that you want to upgrade > > > to running FreeBSD via a port. > > > > Seeing as nobody actually seems to want this, it's obviously not of > > much interest. > > I would dearly love this. Say "nobody who counts", please... You count by doing something about it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 06:28:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04939 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 06:28:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA04933 for ; Fri, 7 Aug 1998 06:28:18 -0700 (PDT) (envelope-from vev@paprika.michvhf.com) Received: (qmail 3383 invoked by uid 1000); 7 Aug 1998 13:28:21 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <35CAB3C7.4A6B776D@tdx.co.uk> Date: Fri, 07 Aug 1998 09:28:21 -0400 (EDT) From: Vince Vielhaber To: Karl Pielorz Subject: RE: getpwuid - after chroot? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Aug-98 Karl Pielorz wrote: > Hi, > > Is there a workaround for using getpwuid() after you've chroot'd at all? - > e.g. > with the code below? > > I think the reason it _doesn't_ work is because once you've chroot'd the > system > can't get back to the '/etc/pwd.db' file etc.? - Is there any way round > this? > > Apparently the following code does actually work on other systems... > Someone > mentioned Linux, but I don't have access to any Linux boxes to test it ;-) I just tried compiling it on HPUX 9.0. It won't compile due to not having setpassent. I compiled it on linux 2.0.24 and running as root I get this: second getpwuid(0) didn't work Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 07:07:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09214 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 07:07:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09201 for ; Fri, 7 Aug 1998 07:07:17 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id KAA12102; Fri, 7 Aug 1998 10:06:53 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id KAA07454; Fri, 7 Aug 1998 10:40:34 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id KAA23820; Fri, 7 Aug 1998 10:11:00 -0400 (EDT) Date: Fri, 7 Aug 1998 10:11:00 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808071411.KAA23820@lakes.dignus.com> To: jdp@polstra.com, tlambert@primenet.com Subject: Re: C and static initialization with unions Cc: hackers@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: <199808070136.SAA24978@usr06.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Is all FreeBSD C source code portable? > > > > GCC extensions are occasionally used in FreeBSD. However, they > > are virtually always optional and for the purpose of (a) better > > efficiency, or (b) better compiler warnings. When GCC extensions are > > used, they are protected by "#ifdef __GNUC__", and an alternative > > portable implementation is provided in the "#else" clause. For case > > (a) the alternative implementation is less efficient; for case (b), > > it's a no-op. See for some examples of (b). > > This is not quite correct. The defined __P(), for > example, and this appears to have been deprecated despite its > ability to ensure portability; which is really bizarre, because > "const", "volatile", and __CONCAT() all haven't, and it the same > portability barrier that all 4 address (non-ANSI K&R compilers). > > > Terry Lambert > terry@lambert.org Let me add to this discussion my (now somewhat tired) song regarding compiling older pre-ANSI software. It's very nice that we can 'turn off' "const", "volatile", prototypes in the header files; just for this purpose... Every now-and-then, a stray "const" seems to slip into the headers; which breaks some of my older software... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 07:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11689 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 07:20:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11684 for ; Fri, 7 Aug 1998 07:20:18 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA29776; Fri, 7 Aug 1998 10:20:53 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Fri, 7 Aug 1998 10:20:53 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Vince Vielhaber cc: hackers@FreeBSD.ORG Subject: RE: getpwuid - after chroot? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG pipe, fork, chroot. client/server might be a hack but it'll work. -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 7 Aug 1998, Vince Vielhaber wrote: > > On 07-Aug-98 Karl Pielorz wrote: > > Hi, > > > > Is there a workaround for using getpwuid() after you've chroot'd at all? - > > e.g. > > with the code below? > > > > I think the reason it _doesn't_ work is because once you've chroot'd the > > system > > can't get back to the '/etc/pwd.db' file etc.? - Is there any way round > > this? > > > > Apparently the following code does actually work on other systems... > > Someone > > mentioned Linux, but I don't have access to any Linux boxes to test it ;-) > > I just tried compiling it on HPUX 9.0. It won't compile due to not > having setpassent. I compiled it on linux 2.0.24 and running as root > I get this: > > second getpwuid(0) didn't work > > Vince. > -- > ========================================================================== > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > # include TEAM-OS2 > Online Searchable Campground Listings http://www.camping-usa.com > "There is no outfit less entitled to lecture me about bloat > than the federal government" -- Tony Snow > ========================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 07:23:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12221 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 07:23:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12213; Fri, 7 Aug 1998 07:23:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA16799; Sat, 8 Aug 1998 00:23:04 +1000 Date: Sat, 8 Aug 1998 00:23:04 +1000 From: Bruce Evans Message-Id: <199808071423.AAA16799@godzilla.zeta.org.au> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG, mturpin@shadow.spel.com Subject: Re: Kernel compile problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When I try to compile a GENERIC (-current as of 2:00PM (EDT) Aug 6,1998) >kernel I get the following error. Am I doing something wrong? >cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit >-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >-Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include >-DKERNEL -include opt_global.h ../../scsi/cd.c > >In file included from ../../scsi/cd.c:48: >ioconf.h:11: conflicting types for `fdintr' >../../i386/isa/isa_device.h:155: previous declaration of `fdintr' >ioconf.h:11: warning: redundant redeclaration of `fdintr' in same scope >../../i386/isa/isa_device.h:155: warning: previous declaration of `fdintr' >... Rebuild, reinstall and rerun config. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 07:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12539 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 07:24:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12438 for ; Fri, 7 Aug 1998 07:24:01 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id KAA15677; Fri, 7 Aug 1998 10:23:22 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id KAA07476; Fri, 7 Aug 1998 10:57:04 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id KAA23918; Fri, 7 Aug 1998 10:27:29 -0400 (EDT) Date: Fri, 7 Aug 1998 10:27:29 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808071427.KAA23918@lakes.dignus.com> To: jb@cimlogic.com.au, tlambert@primenet.com Subject: Re: C and static initialization with unions Cc: chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG, mike@smith.net.au, Nicolas.Souchu@prism.uvsq.fr In-Reply-To: <199808070739.AAA23183@usr08.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > It's perfectly possible to get these warnings from a K&R compiler. > To do this, you need to change your object format to attribute the > symbol table entries. Fred Fish did this for the Motorolla 88k > compiler back in the early 80's. What we are suffering here is a > legacy of compiler writers too lazy to implement decent smart linker > technology. As one of the "compiler writers too lazy" :-) Let me quickly add that compiler writers usually distinguish themselves from linker writers. I'd point the finger at the linker writers :-) :-) Anyway; to credibly add to Terry's point. HP's MPE system (on an HP-3000) did this type of link-time checks as well... which was "way cool" for FORTRAN programs. [A side-effect of the fact this was a stack machine also made for some nice FORTRAN programs...] Furthermore, I had the job of porting Fred's 78K emulator (before Motorola changed the name to 88k) to Data General's AOS system. After getting everything running (comiler, linker, emulator) one of the first things everyone disliked was the link-time checking. I don't believe that survived in the actually 88K stuff... So, it's not just that people don't do it; sometimes, users don't want it... And, to close, Microsoft "kinda" does this with __cdecl functions. They append "@nnn" to the symbol, where nnn is the amount of incoming parm size the function requires. You could use this for some simple C-level function overloading... if you really wanted to... So, I suppose; my point is there is ample precident to consider doing something like that in a linker... if we wanted to. Now, to go find some of those "linker writers".... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 07:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15641 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 07:40:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA15632 for ; Fri, 7 Aug 1998 07:40:45 -0700 (PDT) (envelope-from vev@paprika.michvhf.com) Received: (qmail 3461 invoked by uid 1000); 7 Aug 1998 14:40:46 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 07 Aug 1998 10:40:46 -0400 (EDT) From: Vince Vielhaber To: Alfred Perlstein Subject: RE: getpwuid - after chroot? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Aug-98 Alfred Perlstein wrote: > > pipe, fork, chroot. client/server might be a hack but it'll work. The source calls setpassent(1) which opens, doesn't close and holds the fd for the database before chroot. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 09:34:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02666 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 09:34:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay3.force9.net (relay3.force9.net [195.166.128.26]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA02658 for ; Fri, 7 Aug 1998 09:34:57 -0700 (PDT) (envelope-from David.Larkin@DJL.co.uk) Message-Id: <199808071634.JAA02658@hub.freebsd.org> Received: (qmail 6280 invoked from network); 7 Aug 1998 16:38:54 -0000 Received: from relay2.force9.net (195.166.128.25) by relay3.force9.net with SMTP; 7 Aug 1998 16:38:54 -0000 Received: (qmail 14917 invoked from network); 7 Aug 1998 16:21:51 -0000 Received: from 79.usr01.shef.dialup.force9.net (HELO djl02.djl.com) (195.166.132.79) by relay2.force9.net with SMTP; 7 Aug 1998 16:21:51 -0000 Reply-To: From: "David Larkin" To: Subject: Booting Default: F? Date: Fri, 7 Aug 1998 17:29:07 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone help me to get my system back up and running ? I was running FreeBSD 2.2.5 and W95 happily on my machine. wd0 contained W95, and wd1 contained FreeBSD Suddenly while running W95, everything went "pop" and I wasn't able to boot either. So, booting from floppy, using the "fixit" option, and running fdisk I get the following :- fdisk wd0 *** working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=4095 heads=16 sectors/track=63 1008 blks/cyl) Figure below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=4095 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information for partition 1 is: Information for partition 2 is: Information for partition 3 is: Information for partition 4 is: fdisk wd1 *** working on device /dev/rwd1 *** parameters extracted from in-core disklabel are: cylinders=4095 heads=16 sectors/track=63 1008 blks/cyl) Figure below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=4095 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information for partition 1 is: sysid 128, (Minix 1.1 ....... 1.4a) start -61531, size 63 (0 Meg), flag 0 beg: cyl 0/ sector 0/ head0; end: cyl 0/ sector 1/ head1; Information for partition 2 is: sysid 0,(unused) start 0, size 0 (0 Meg), flag d1 beg: cyl 0/ sector 62/ head 251; end: cyl 0/ sector 0/ head 0 Information for partition 3 is: Information for partition 4 is: sysid 165, (FreeBSD/NetBSD/386BSD) start 1, size 4127759 (2015 Meg), flag 80 beg: cyl 0/ sector 2/ head 0; end: cyl 1022/ sector 63/ head 15 I don't claim to understand half of the above, but I get the impression that my W95 (wd0) installation is gone, but my FreeBSD is still there in slice 4 of wd1. The question is how to boot it. I wrote a boot manager to wd0, and now when I boot I get the following F5 .... disk 2 Default: F5 F5 .... disk 2 Default: F? Any advice on how to proceed would be appreciated. David Larkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 10:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09664 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 10:12:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09602 for ; Fri, 7 Aug 1998 10:12:19 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4q3d-0001Eh-00; Fri, 7 Aug 1998 11:12:01 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id LAA26399; Fri, 7 Aug 1998 11:12:33 -0600 (MDT) Message-Id: <199808071712.LAA26399@harmony.village.org> To: Karl Pielorz Subject: Re: getpwuid - after chroot? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Aug 1998 08:59:03 BST." <35CAB3C7.4A6B776D@tdx.co.uk> References: <35CAB3C7.4A6B776D@tdx.co.uk> Date: Fri, 07 Aug 1998 11:12:33 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35CAB3C7.4A6B776D@tdx.co.uk> Karl Pielorz writes: : I think the reason it _doesn't_ work is because once you've chroot'd : the system xcan't get back to the '/etc/pwd.db' file etc.? - Is : there any way round this? Copy or hard link. You really don't want people accessing *ANYTHING* outside of the chroot "jail". Too bad there are many techniques for a jailbreak right now. :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 10:41:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15231 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 10:41:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bbcc.ctc.edu (bbcc.ctc.edu [134.39.180.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15216 for ; Fri, 7 Aug 1998 10:41:21 -0700 (PDT) (envelope-from chris@bbcc.ctc.edu) Received: from localhost (chris@localhost) by bbcc.ctc.edu (8.8.8/8.6.12) with SMTP id KAA21069; Fri, 7 Aug 1998 10:40:25 -0700 (PDT) Date: Fri, 7 Aug 1998 10:40:25 -0700 (PDT) From: Chris Coleman To: hackers@FreeBSD.ORG cc: tech@openbsd.org, tech-kern@netbsd.org Subject: Ezine Authors Needed. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We are making our final call for authors for this issue of the BSD Ezine. We need some people to write some of the more technical stuff. We have a list of proposed columns at http://ezine.freebsd.org We are looking for some people to address topics such as Kernel hacking. Security/Cryptography. Basic C programming. X Window System Magic. BSD Anecdotes. Columns can be named/renamed easily, or create your own like "UNIX Basics" or some such one. We like to have at least 2 authors for each column so that they can cooperate and share the work load, writing bi-monthly. If you don't have time to make it into this issue, we can fit you into the next issue. (NETBSD and OPENBSD response has been very weak. Come on Guys Volunteer!) Please direct all response to editors@ezine.freebsd.org -Chris Coleman and Brett Taylor http://daemon-news.freebsd.org http://ezine.freebsd.org mailto:editors@ezine.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 12:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29561 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 12:10:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29553 for ; Fri, 7 Aug 1998 12:10:31 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA15472; Fri, 7 Aug 1998 21:10:11 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 21:10:10 +0200 (MET DST) Mime-Version: 1.0 To: Chris Coleman Cc: hackers@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Ezine Authors Needed. References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 21:10:10 +0200 In-Reply-To: Chris Coleman's message of "Fri, 7 Aug 1998 10:40:25 -0700 (PDT)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA29557 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Coleman writes: > We are making our final call for authors for this issue of the BSD Ezine. > We need some people to write some of the more technical stuff. What's the deadline? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 12:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04554 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 12:35:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bbcc.ctc.edu (bbcc.ctc.edu [134.39.180.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04535 for ; Fri, 7 Aug 1998 12:35:06 -0700 (PDT) (envelope-from chris@bbcc.ctc.edu) Received: from localhost (chris@localhost) by bbcc.ctc.edu (8.8.8/8.6.12) with SMTP id MAA04481; Fri, 7 Aug 1998 12:34:17 -0700 (PDT) Date: Fri, 7 Aug 1998 12:34:16 -0700 (PDT) From: Chris Coleman To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: hackers@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Ezine Authors Needed. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA04538 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's the deadline? The deadline for articles in Aug 15th, so we can get it proof read and formatted before Sept 1. If you want to squeeze in an article and you won't have it done by then, you must contact us so that we can arrange for someone to format/proofread it quickly and so forth. We know this is a little short notice for people, but we hae been annuoncing this for a while. We believe we still have time for everyone who wants to write an article to still get it in on time. (If they hurry.) :-) The articles for this issue don't need to be huge. Even if its just an introduction, it will do nicely. BTW we are accepting one-time articles also. Just submit them as you get them ready. -Chris (BTW the Net/Open response has improved. We should be balanced soon. I am looking for people to host ezine.openbsd.org and ezine.netbsd.org to balance this among the BSD's) > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 12:49:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06763 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 12:49:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06758 for ; Fri, 7 Aug 1998 12:49:49 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id PAA99766 for ; Fri, 7 Aug 1998 15:49:41 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: Date: Fri, 7 Aug 1998 15:53:39 -0400 To: hackers@FreeBSD.ORG From: Garance A Drosihn Subject: CAP vs netatalk for Appletalk/printing support Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice the ports collection includes both CAP and netatalk, and that kernel changes have been made for netatalk to take advantage of. I was wondering if most FreeBSD'ers prefer netatalk over CAP. Right now RPI drives many printer queues thru CAP running on Solaris, and we'll soon switch many of those queues over to CAP under AIX. I have a number of improvements to CAP as a result of this, and was wondering if it'd be worthwhile to see about making those changes for CAP under FreeBSD. If a lot of people use CAP then this might be worthwhile, but if most people prefer netatalk then I probably shouldn't spend any time on it. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 13:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13649 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 13:22:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13631 for ; Fri, 7 Aug 1998 13:22:49 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA06225; Fri, 7 Aug 1998 22:21:10 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA15427; Fri, 7 Aug 1998 21:49:34 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808071949.VAA15427@semyam.dinoco.de> To: Terry Lambert Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 01:33:05 -0000." <199808070133.SAA24688@usr06.primenet.com> Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Fri, 07 Aug 1998 21:49:34 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? > > Good question; I don't know the answer. We have at least a little bit of unportable code in swap_pager.c where arrays of runtime computed size (array size depends on one of the parameters of the function) get used. Works great with gcc but not with an unsuspecting ANSI C compiler. What's the official opinion on using gcc extensions? Should this have been avoided or is it OK to use them in the kernel? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 13:30:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15427 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 13:30:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15404 for ; Fri, 7 Aug 1998 13:30:19 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA27187; Fri, 7 Aug 1998 13:30:01 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd027101; Fri Aug 7 13:29:52 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA25160; Fri, 7 Aug 1998 13:29:38 -0700 (MST) From: Terry Lambert Message-Id: <199808072029.NAA25160@usr02.primenet.com> Subject: Re: C and static initialization with unions To: mike@smith.net.au (Mike Smith) Date: Fri, 7 Aug 1998 20:29:38 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, Nicolas.Souchu@prism.uvsq.fr, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808071324.GAA00589@antipodes.cdrom.com> from "Mike Smith" at Aug 7, 98 06:24:56 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Actually, we largely do separate into compilation units. See all those > > > files ending in '.s' and '.S'? > > > > I just grepp'ed for "asm(.*)" and piped to wc -l. The result was a > > non-zero count. > > "largely" is a relative, not absolute, expression. Mock me not for the > sins of others, especially where said sins are in your eyes alone. Not being able to compile FreeBSD with TenDRA is a sin. The problem here is that "largely" is just as uncompilable as "not at all". > > > > I also know that FreeBSD uses ANSI constructs, which make the > > > > code non-portable to older compilers, such as those you would > > > > have on machines running older OS's that you want to upgrade > > > > to running FreeBSD via a port. > > > > > > Seeing as nobody actually seems to want this, it's obviously not of > > > much interest. > > > > I would dearly love this. Say "nobody who counts", please... > > You count by doing something about it. I have zero control over this policy decision which was opposed by me at the time it was being made. Unless you are suggesting that you are willing to commit __P() based prototype wrapping patches if I provide them? I also have patches to cdefs.h that wrapper ANSI vs. non-ANSI vararg declarations. I use them to compile FreeBSD code using Aztec C, which is the only C compiler to get the sizeof(int) right on the 16 bit address bus Motorolla 68000. PS: If FreeBSD is going to continue to use antique compiler technology, could it at least use classic antique compiler technology instead of Edsel (gcc 2.7.2) compiler technology? The old GCC we used back on FreeBSD 1.1.x was about three times faster than what we have now, and what we have now is incapable of compiling a large amount of new code. If you are going to be unable to compile new code, at least you should be unable to compile it quickly... 8-P. ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 13:35:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16603 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 13:35:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16560; Fri, 7 Aug 1998 13:35:14 -0700 (PDT) (envelope-from rzig@verio.net) Received: by kaori.INTERNAL with Internet Mail Service (5.0.1458.49) id ; Fri, 7 Aug 1998 15:34:43 -0500 Message-ID: From: Raul Zighelboim To: "'hardware@freebsd.org'" Cc: "'hackers@freebsd.org'" Subject: Stallion PCI card problems... Date: Fri, 7 Aug 1998 15:34:41 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there; I am running into trouble getting a Stallion Multi serial controller working. When trying to talk to the card with the software provided by Stallion (BTW: the drivers on the Stallion ftp site are newers than the ones on 2.2.7-Stable), I get an error: su-2.02# ./stlload -v -R (verbose, Reset the card) Using shared memory device /dev/staliomem0 Downloading image /usr/libdata/stallion/cdk.sys to board 0 Opening shared memory device /dev/staliomem0 Stoping any current slave ./stlload: ioctl(STL_BSTOP) failed, errno=25 booting the kernel verbose: stl0 rev 1 int a irq 15 on pci0:15:0 mapreg[14] type=1 addr=0000ec00 size=0080. mapreg[18] type=1 addr=0000e880 size=0080. stl0: EC8/64-PCI (driver version 2.0.0) unit=0 nrpanels=2 nrports=32 So, the question: What am I missing ? Thanks. ------------------------------------------------------- Raul Zighelboim - 504.636.3800 - Verio Gulf South rzig@verio.net - - New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 14:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24006 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 14:08:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23684 for ; Fri, 7 Aug 1998 14:07:26 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id QAA17231; Fri, 7 Aug 1998 16:58:44 -0400 (EDT) Date: Fri, 7 Aug 1998 17:05:57 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Garance A Drosihn cc: hackers@FreeBSD.ORG Subject: Re: CAP vs netatalk for Appletalk/printing support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Garance A Drosihn wrote: > for CAP under FreeBSD. If a lot of people use CAP then this might > be worthwhile, but if most people prefer netatalk then I probably > shouldn't spend any time on it. Well the reason I have used netatalk in the past is there is a blurb on netatalks page about the difference between CAP and netatalk that talks about netatalk having a better philosophy of how to do things or the netatalk people doing things a little better, something along those lines i havent read it in a while. And even though thats a pretty shallow reason for choosing one over the other I was in a hurry and it worked for me. And I knew that julian had done the netatalk stuff. So that's why I've used it. That doesn't really answer your question, but it gives you an idea of why this person uses it. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." -Wes Peters ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.7 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 14:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25023 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 14:13:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24816 for ; Fri, 7 Aug 1998 14:12:11 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA325 for ; Fri, 7 Aug 1998 14:42:50 -0600 Received: from count.timing.com (localhost.timing.com [127.0.0.1]) by count.timing.com (8.8.7/8.8.7) with ESMTP id OAA03214 for ; Fri, 7 Aug 1998 14:41:08 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199808072041.OAA03214@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG Subject: Anyone using cdk with ncurses? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 14:41:08 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for a UI library based on curses and came across CDK. I did not find a FreeBSD port of this but did find the source at ftp:sunsite.unc.edu/pub/Linux/libs/ui There is build support for FreeBSD, but it is not building for me. Anyone out there using this? Overview: --------- Cdk stands for 'Curses Development Kit' and it currently contains 21 ready to use widgets which facilitate the speedy development of full screen curses programs. This little project of mine started as a test to see how compatible my Linux machine was to other UNIX breeds. While doing this I discovered Ncurses, and played with it. These widgets are the result of over a years worth of playing. The current complement of widgets are: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 14:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25707 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 14:15:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25550 for ; Fri, 7 Aug 1998 14:14:49 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA13394; Fri, 7 Aug 1998 16:13:52 -0500 (EST) (envelope-from toor) Message-Id: <199808072113.QAA13394@dyson.iquest.net> Subject: Re: C and static initialization with unions In-Reply-To: <199808070739.AAA23183@usr08.primenet.com> from Terry Lambert at "Aug 7, 98 07:39:35 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 7 Aug 1998 16:13:51 -0500 (EST) Cc: jb@cimlogic.com.au, mike@smith.net.au, tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: > > > Seeing as nobody actually seems to want this, it's obviously not of > > > much interest. > > > > ... and these days it seems that the GNU tools get ported to the "older" > > OS first and you just use them. > > I am sorry. I vehemently disagree with the GPL as a political tool. > I will not port GCC to a new platform. > Try TenDRA. It seems to be relatively complete (and if you study it carefully enough, you'll find out it even supports long-long!!!) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 15:37:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10177 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 15:37:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dll.abs.net (cc698686-a.whmh1.md.home.com [24.3.58.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10164 for ; Fri, 7 Aug 1998 15:37:37 -0700 (PDT) (envelope-from hdl@abs.net) Received: from hdl (hdl@hdl.abs.net [207.114.24.1]) by dll.abs.net (8.9.0/8.8.5) with SMTP id SAA01346; Fri, 7 Aug 1998 18:37:16 -0400 (EDT) Message-Id: <199808072237.SAA01346@dll.abs.net> X-Sender: hdl@pop.abs.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.37 (Beta) Date: Fri, 07 Aug 1998 18:37:15 -0400 To: freebsd-hackers@FreeBSD.ORG From: Howard Leadmon Subject: select() -vs- poll() in 3.0-CURRENT Cc: freebsd-current@freebsd.org.freebsd-questions@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I have started working with FreeBSD 3.0-CURRENT to run an Undernet IRC Server. As this monolithic program allows thousands of clients to connect to it, I had to allow thousands of FD's to be open, which has been done and works fine. The big question is that the 3.0 release now supports poll() as well as select() to service the FD's. The Undernet IRCD allows me to use either method by selecting it at compile time. So any of you hardcore C programmers out their know what is better for this environment? The the configure program uses poll() by default if it finds it available, but I suspect that is from SysV, so wondered if this is still the correct action for FBSD. For now I am running with poll() enabled, but thought I would see what others feelings were on this.. --- Howard Leadmon - hdl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 15:42:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11009 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 15:42:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10969 for ; Fri, 7 Aug 1998 15:42:48 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA02961; Fri, 7 Aug 1998 15:42:22 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd002782; Fri Aug 7 15:42:11 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA02451; Fri, 7 Aug 1998 15:41:51 -0700 (MST) From: Terry Lambert Message-Id: <199808072241.PAA02451@usr02.primenet.com> Subject: Re: C and static initialization with unions To: jb@cimlogic.com.au (John Birrell) Date: Fri, 7 Aug 1998 22:41:51 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, Nicolas.Souchu@prism.uvsq.fr, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808070232.MAA02971@cimlogic.com.au> from "John Birrell" at Aug 7, 98 12:32:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Seeing as nobody actually seems to want this, it's obviously not of > > much interest. > > ... and these days it seems that the GNU tools get ported to the "older" > OS first and you just use them. And you get to become the "GCC for machine XYZ maintainer", which is what I definitely don't want to do. > So unless there is a late rush of people wanting to port FreeBSD to another > processor for which GNU tools don't exist, I'd prefer to see the K&R bit > dropped in favour of ANSI C and get people to learn to compile things with > compiler higher warning levels. These issues are orthogonal. The prototype-based warnings require that there are prototypes in scope. The do *not* (or should not, according to the ISO (ANSI) standard) require that the functions use ANSI style declarations. I am not suggesting that there will not be prototype in scope, in the case an ANSI compiler is used. There will be. I am merely complaining that ANSI style declarations and deprecation of __P() prototype wrapping for forward declarations will cause older compilers to fail. Similar arguments can be made about the non-use of the "extern" keyword on such declarations, and forward declaration of structures (used to allow object recursion). 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 15:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11692 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 15:49:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11687 for ; Fri, 7 Aug 1998 15:49:03 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA26237; Fri, 7 Aug 1998 15:48:47 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd026141; Fri Aug 7 15:48:39 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA02915; Fri, 7 Aug 1998 15:48:33 -0700 (MST) From: Terry Lambert Message-Id: <199808072248.PAA02915@usr02.primenet.com> Subject: Re: C and static initialization with unions To: jb@cimlogic.com.au (John Birrell) Date: Fri, 7 Aug 1998 22:48:33 +0000 (GMT) Cc: tlambert@primenet.com, jb@cimlogic.com.au, mike@smith.net.au, Nicolas.Souchu@prism.uvsq.fr, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808070758.RAA03868@cimlogic.com.au> from "John Birrell" at Aug 7, 98 05:58:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I also believe that having to port the compiler is a ridiculous barrier > > to entry, and one of the reasons FreeBSD ports are not more prevalent. > > Crap. FreeBSD ports are not more prevalent because some people spend more > time doing the yadda yadda than actually getting off their butts and > doing something to contribute. The original GCC back in the early days did not support a large number of platforms; I think FreeBSD would have been run on a lot of platforms if the tools had been available to let that happen. There were two attempts, the Acorn RISC and Jack Vogel's port of 1.1.x to SPARC, that both died the grim death in the USL vs. BSDI upheaval. 8-(. That said, let me back off a *little*; your reason is much better than mine for why FreeBSD does not *now* run on many platforms. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 16:08:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16019 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 16:08:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15997 for ; Fri, 7 Aug 1998 16:08:11 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA07554; Fri, 7 Aug 1998 16:07:54 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd007529; Fri Aug 7 16:07:50 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA03789; Fri, 7 Aug 1998 16:07:48 -0700 (MST) From: Terry Lambert Message-Id: <199808072307.QAA03789@usr02.primenet.com> Subject: Re: C and static initialization with unions To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Fri, 7 Aug 1998 23:07:47 +0000 (GMT) Cc: tlambert@primenet.com, seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808071949.VAA15427@semyam.dinoco.de> from "Stefan Eggers" at Aug 7, 98 09:49:34 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? > > > > Good question; I don't know the answer. > > We have at least a little bit of unportable code in swap_pager.c where > arrays of runtime computed size (array size depends on one of the > parameters of the function) get used. Works great with gcc but not > with an unsuspecting ANSI C compiler. I thought this was an ANSI-ism (you are talking about the sizing of the stack allocations based on count in swap_pager_getpages() and swap_pager_getpages(), right?); my bad. > What's the official opinion on using gcc extensions? Should this have > been avoided or is it OK to use them in the kernel? I'd like this clarified, as well. I'm getting very tempted by this thread to "do what it takes" to make TenDRA work... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 16:37:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21002 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 16:37:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20991; Fri, 7 Aug 1998 16:37:41 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id RAA13808; Fri, 7 Aug 1998 17:37:21 -0600 (MDT) Message-Id: <199808072337.RAA13808@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 07 Aug 1998 15:17:43 -0600 To: Ollivier Robert , FreeBSD-security@FreeBSD.ORG From: Brett Glass Subject: Re: Does this mean we have another breakin? Cc: hackers@FreeBSD.ORG In-Reply-To: <19980807122035.A4145@keltia.freenix.fr> References: <199808051643.KAA04281@lariat.lariat.org> <19980805234700.A23220@keltia.freenix.fr> <19980806131045.A28059@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have set up Tripwire, and are getting "Alarums and Excursions" (with apologies to old Will Shakespeare) from changed "last modification" dates on executables. Is this a bug or a break-in? I could not find anything about a bug anywhere in the GNATS database. When we encountered the changed files, we were sure we were being hacked by the same intruder who "owned" us via QPopper not long ago. That intruder installed several Trojans; perhaps as many as half a dozen. We dealt with that first break-in by wiping the disk, installing 2.2.7-RELEASE, bringing back all the e-mail and user data, forcing 250 users to change passwords, and having two people audit each one of our administrative Perl scripts and shell scripts. We also audited every configuration file that can specify that a program should be run, meaning everything from our customized sendmail.cf to rc.everything to /etc/crontab. That process took 4 people a full weekend (not counting the time it took to notify every single user) and took a mail server that serves 250 people down for a full day. Not to mention the cost of all of that pizza. ;-) We were about to do it AGAIN. Now we're holding out some hope that it's just a bug -- though perhaps the same one that's crashing us when we try to back up. In any event, I just received private e-mail stating that at least one person has encountered VM problems in -stable under heavy CPU loads when the swapper kicks in. According to the message, they cause corruption of file modification dates. Is this a known bug? If so, could it also be responsible for the spontaneous crashes we see when we pipe dump | gzip | ftp for backups? --Brett At 12:20 PM 8/7/98 +0200, Ollivier Robert wrote: >According to Just Another Perl Hacker: >> I assume that this spontaneous writebacks *could* occur not only to >> setuid(2)'d executables such as sendmail(8), but to arbitrary command >> as a file on the filesystem. > >Of course but unless you run Tripwire, the /etc/security script will detect >changes only on setuid/setgid ones. >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr >FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 18:39:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07890 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 18:39:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07867; Fri, 7 Aug 1998 18:39:41 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA00798; Fri, 7 Aug 1998 18:35:55 -0700 (PDT) Message-Id: <199808080135.SAA00798@implode.root.com> To: Brett Glass cc: Ollivier Robert , FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Does this mean we have another breakin? In-reply-to: Your message of "Fri, 07 Aug 1998 15:17:43 MDT." <199808072337.RAA13808@lariat.lariat.org> From: David Greenman Reply-To: dg@root.com Date: Fri, 07 Aug 1998 18:35:55 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We were about to do it AGAIN. Now we're holding out some hope that it's >just a bug -- though perhaps the same one that's crashing us when we try to >back up. > >In any event, I just received private e-mail stating that at least one >person has encountered VM problems in -stable under heavy CPU loads when >the swapper kicks in. According to the message, they cause corruption of >file modification dates. Corruption is probably not the right word. There might be a bug where a page is seen as modified when it isn't, causing the modify date to get updated. The only way to be certain is to compare the binary with your backup (e.g. if installed from CDROM, then with the copy on the CDROM). I haven't personally seen this happen in more than a year, so if the bug is still there, it must be fairly rare. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 21:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25034 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 21:03:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25029; Fri, 7 Aug 1998 21:03:53 -0700 (PDT) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.8.8/RDY&DVV) id VAA05702; Fri, 7 Aug 1998 21:03:24 -0700 (PDT) Message-Id: <199808080403.VAA05702@burka.rdy.com> Subject: Re: Does this mean we have another breakin? In-Reply-To: <199808080135.SAA00798@implode.root.com> from David Greenman at "Aug 7, 1998 6:35:55 pm" To: dg@root.com Date: Fri, 7 Aug 1998 21:03:24 -0700 (PDT) Cc: brett@lariat.org, roberto@keltia.freenix.fr, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > >We were about to do it AGAIN. Now we're holding out some hope that it's > >just a bug -- though perhaps the same one that's crashing us when we try to > >back up. > > > >In any event, I just received private e-mail stating that at least one > >person has encountered VM problems in -stable under heavy CPU loads when > >the swapper kicks in. According to the message, they cause corruption of > >file modification dates. > > Corruption is probably not the right word. There might be a bug where a > page is seen as modified when it isn't, causing the modify date to get > updated. The only way to be certain is to compare the binary with your > backup (e.g. if installed from CDROM, then with the copy on the CDROM). I > haven't personally seen this happen in more than a year, so if the bug is > still there, it must be fairly rare. We usually get this bug once in two weeks. But since file by itself stays the same and machine doesn't crash, fixing/finding the problem wasn't in out TODO list. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe security" in the body of the message > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 21:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27632 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 21:38:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tokyo-6.ppp.hooked.net [206.169.229.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27627 for ; Fri, 7 Aug 1998 21:38:02 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id VAA17438; Fri, 7 Aug 1998 21:38:28 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 7 Aug 1998 21:38:28 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Terry Lambert cc: faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, chuckr@Glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: <199808070713.AAA22022@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Terry Lambert wrote: > > So when will someone try replacing gcc with TenDRA, yadda yadda, and > > getting a make world built with tcc and a make world to build tcc? > > I tried this once. The .mk file unfortunately replace include paths, > making no distinction between build environments and targets, which > is truly unfortunate. It means I can't even build FreeBSD with the > next revision of GCC (a port), since it gets the wrong libgcc.a... I thought that a make world bootsrapped gcc, so that if you truely wanted to build world with TenDRA, you'd have to remove the gcc, and drop in the tcc source? Either way, I'd love to see the default compiler for FreeBSD support exceptions and STL v3.11.. Ah well, here's to hopin that egcs supports a.out C++ shared libs soon. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 21:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28499 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 21:46:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28494 for ; Fri, 7 Aug 1998 21:46:39 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id XAA09432; Fri, 7 Aug 1998 23:43:58 -0400 (EDT) Date: Fri, 7 Aug 1998 23:43:58 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Alex cc: Terry Lambert , faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Alex wrote: > > On Fri, 7 Aug 1998, Terry Lambert wrote: > > > > So when will someone try replacing gcc with TenDRA, yadda yadda, and > > > getting a make world built with tcc and a make world to build tcc? > > > > I tried this once. The .mk file unfortunately replace include paths, > > making no distinction between build environments and targets, which > > is truly unfortunate. It means I can't even build FreeBSD with the > > next revision of GCC (a port), since it gets the wrong libgcc.a... > > I thought that a make world bootsrapped gcc, so that if you truely wanted > to build world with TenDRA, you'd have to remove the gcc, and drop in the > tcc source? Either way, I'd love to see the default compiler for FreeBSD > support exceptions and STL v3.11.. > > Ah well, here's to hopin that egcs supports a.out C++ shared libs soon. Well, it's not the compiler, it's the linker here that's important, and don't hold your breath on that, GNU hasn't supported our a.out for a _very_ long time ... I don't think, without FreeBSD modifications, that they ever did. Sooner, we'll probably go to ELF, making it a moot point. > > - alex > > | "Contrary to popular belief, penguins are not the salvation of modern | > | technology. Neither do they throw parties for the urban proletariat." | > | Powered by FreeBSD http://www.freebsd.org/ | > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 22:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02627 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 22:30:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tokyo-6.ppp.hooked.net [206.169.229.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02621 for ; Fri, 7 Aug 1998 22:30:20 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id WAA18853; Fri, 7 Aug 1998 22:30:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 7 Aug 1998 22:30:48 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Chuck Robey cc: Terry Lambert , faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Chuck Robey wrote: [..] > Well, it's not the compiler, it's the linker here that's important, and > don't hold your breath on that, GNU hasn't supported our a.out for a > _very_ long time ... I don't think, without FreeBSD modifications, that > they ever did. This, I wonder about. C shared libs seem to work well. Ah well, either way, I'd like to see some better egcs support, ELF or not. > Sooner, we'll probably go to ELF, making it a moot point. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 23:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07263 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 23:35:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.futuresouth.com (mail.futuresouth.com [198.78.58.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07244; Fri, 7 Aug 1998 23:35:26 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id BAA11150; Sat, 8 Aug 1998 01:34:56 -0500 (CDT) Message-ID: <19980808013456.49685@futuresouth.com> Date: Sat, 8 Aug 1998 01:34:56 -0500 From: "Matthew D. Fuller" To: dg@root.com Cc: FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Does this mean we have another breakin? References: <199808072337.RAA13808@lariat.lariat.org> <199808080135.SAA00798@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199808080135.SAA00798@implode.root.com>; from David Greenman on Fri, Aug 07, 1998 at 06:35:55PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 07, 1998 at 06:35:55PM -0700, David Greenman woke me up to tell me: > >We were about to do it AGAIN. Now we're holding out some hope that it's > >just a bug -- though perhaps the same one that's crashing us when we try to > >back up. > > > >In any event, I just received private e-mail stating that at least one > >person has encountered VM problems in -stable under heavy CPU loads when > >the swapper kicks in. According to the message, they cause corruption of > >file modification dates. > > Corruption is probably not the right word. There might be a bug where a > page is seen as modified when it isn't, causing the modify date to get > updated. The only way to be certain is to compare the binary with your > backup (e.g. if installed from CDROM, then with the copy on the CDROM). I > haven't personally seen this happen in more than a year, so if the bug is > still there, it must be fairly rare. We get it all the time here. On sendmail on one machine (sendmail -q run out of cron) and on {r}restore on another machine (amanda, I'm guessing) Happens every couple days. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 23:41:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08043 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 23:41:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08003; Fri, 7 Aug 1998 23:41:35 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id AAA16434; Sat, 8 Aug 1998 00:41:05 -0600 (MDT) Message-Id: <199808080641.AAA16434@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sat, 08 Aug 1998 00:40:49 -0600 To: dima@best.net, dg@root.com From: Brett Glass Subject: Re: Does this mean we have another breakin? Cc: roberto@keltia.freenix.fr, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199808080403.VAA05702@burka.rdy.com> References: <199808080135.SAA00798@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:03 PM 8/7/98 -0700, Dima Ruban wrote: >We usually get this bug once in two weeks. But since file by itself >stays the same and machine doesn't crash, fixing/finding the problem >wasn't in out TODO list. The MD5 of the file stayed the same, and diff reveals no change. But we can't turn off the alarm that's triggered by the date change in /usr/sbin without potentially missing breakins, so our two new admins are constantly getting scary messages. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 7 23:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09120 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 23:50:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09045; Fri, 7 Aug 1998 23:50:01 -0700 (PDT) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.8.8/RDY&DVV) id XAA06334; Fri, 7 Aug 1998 23:49:35 -0700 (PDT) Message-Id: <199808080649.XAA06334@burka.rdy.com> Subject: Re: Does this mean we have another breakin? In-Reply-To: <199808080641.AAA16434@lariat.lariat.org> from Brett Glass at "Aug 8, 1998 0:40:49 am" To: brett@lariat.org (Brett Glass) Date: Fri, 7 Aug 1998 23:49:35 -0700 (PDT) Cc: dima@best.net, dg@root.com, roberto@keltia.freenix.fr, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass writes: > At 09:03 PM 8/7/98 -0700, Dima Ruban wrote: > > >We usually get this bug once in two weeks. But since file by itself > >stays the same and machine doesn't crash, fixing/finding the problem > >wasn't in out TODO list. > > The MD5 of the file stayed the same, and diff reveals no change. But > we can't turn off the alarm that's triggered by the date change in > /usr/sbin without potentially missing breakins, so our two new admins > are constantly getting scary messages. I wouldn't even know about this bug, if somebody from my users wouldn't be checking was changed since the last time he's checked (once a day). He mentioned, that /usr/bin/du gets changed every once in a while. That forced me to spend some time monitoring this particular machine. And I found out that the only thing that was changed, was modification date on /usr/bin/du. Etc etc etc etc. The rest you already know. > > --Brett > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 01:52:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19241 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 01:52:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19236; Sat, 8 Aug 1998 01:52:22 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA03815; Sat, 8 Aug 1998 18:22:02 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA14731; Sat, 8 Aug 1998 18:22:01 +0930 (CST) Message-ID: <19980808182200.E14475@freebie.lemis.com> Date: Sat, 8 Aug 1998 18:22:00 +0930 From: Greg Lehey To: dg@root.com, John Baldwin Cc: FreeBSD Hackers Subject: AMD-specific kernel code (was: How long a wait?) References: <199808070644.XAA14097@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808070644.XAA14097@implode.root.com>; from David Greenman on Thu, Aug 06, 1998 at 11:44:39PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (following up to -hackers) On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >> I have a question and I hope this is the right list.. How long is the normal >> turn around for a response to a non-critical PR? A friend of mine who runs an >> ISP submitted a PR (6269) that turns on an extra option for AMD K5 and K6 >> CPU's. He says that it gave his AMD-based webserver a whopping 15% performance >> increase! He submitted it on Apr 10 of this year (almost 4 months ago) and no >> one has bothered to even reply to it or anything. As a result, he's somewhat >> disappointed and not to eager to contribute code in the future as he just >> thinks he'll get blown off. Of the programmers that I actually know >> personally, he's the best, and I'd hate for him to not make any further >> contributions. So, how are PR patches normally handled? Do you wait for >> enough people to try it out and respond saying it works? I'm just curious, and >> I wouldn't mind FreeBSD having a patch committed that increases performance by >> 15% on some machines. Please cc me in replies as I'm not subscribed to >> questions, thanks. > > I just looked at the patch. Other than some KNF style bugs, it seems okay. > I don't have any AMD K5/K6 machines, however, so I can't test it and won't > be committing it. > If it could get wider circulation - perhaps by posting a note to hackers > asking for testers, then I think there would be less hesitation in getting > it committed. I've grabbed the code and will try it out and report. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 03:18:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27254 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 03:18:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27249 for ; Sat, 8 Aug 1998 03:18:47 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id LAA23825; Sat, 8 Aug 1998 11:18:18 +0100 (BST) Message-ID: <35CC2618.3F8AE5@tdx.co.uk> Date: Sat, 08 Aug 1998 11:19:04 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Vince Vielhaber CC: hackers@FreeBSD.ORG Subject: Re: getpwuid - after chroot? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vince Vielhaber wrote: > I just tried compiling it on HPUX 9.0. It won't compile due to not > having setpassent. I compiled it on linux 2.0.24 and running as root > I get this: > > second getpwuid(0) didn't work Apparently the code does work on NetBSD, OpenBSD and BSDI - but not FreeBSD... The first call to 'setpassent(1)' is meant to go to the start of the password database, and keep the file open... On the other BSD's (verified by the program author, not myself) it works, This is because once you've chroot'd you can still use calls to getpwent etc. - as you opened the file (and got the descriptor) before you chroot'd. On FreeBSD this doesn't happen... I'm not saying their behaviour is right, and ours is wrong - I'm just wondering which is better (i.e. to make FreeBSD do the same as the others - or to adjust the offending program accordingly (i.e. a workaround etc.))? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 03:49:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01124 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 03:49:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts05-047.dublin.indigo.ie [194.125.220.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01118 for ; Sat, 8 Aug 1998 03:49:25 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id LAA00857; Sat, 8 Aug 1998 11:34:11 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808081034.LAA00857@indigo.ie> Date: Sat, 8 Aug 1998 11:33:46 +0000 In-Reply-To: <199808072029.NAA25160@usr02.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Terry Lambert , mike@smith.net.au (Mike Smith) Subject: Re: C and static initialization with unions Cc: Nicolas.Souchu@prism.uvsq.fr, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 7, 8:29pm, Terry Lambert wrote: } Subject: Re: C and static initialization with unions > > Not being able to compile FreeBSD with TenDRA is a sin. > > The problem here is that "largely" is just as uncompilable as "not at > all". Is it? How many developers care that isn't possible? How many end users? I think it makes sense to avoid gcc-isms wherever possible but its not a religious thing with me. In general, sticking to ANSI C enforces some programming discipline, but if a gcc-ism significantly eases development of some code then I think it makes sense to use it, and come back when some other production compiler is being used. (if ever) > I also have patches to cdefs.h that wrapper ANSI vs. non-ANSI vararg > declarations. I use them to compile FreeBSD code using Aztec C, > which is the only C compiler to get the sizeof(int) right on the 16 > bit address bus Motorolla 68000. It seems a trifle silly for everyone to have to use K&R-isms (which I find a pita) just so you can use some obsolete compiler on some obsolete processor. Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 06:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12159 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 06:03:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12154 for ; Sat, 8 Aug 1998 06:03:01 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id GAA25564 for ; Sat, 8 Aug 1998 06:02:44 -0700 (PDT) Date: Sat, 8 Aug 1998 06:02:44 -0700 (PDT) From: Chris Timmons To: hackers@FreeBSD.ORG Subject: cvsup.freebsd.org down for a few Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... site power outage. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 07:11:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16250 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 07:11:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16243 for ; Sat, 8 Aug 1998 07:11:26 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id HAA20196; Sat, 8 Aug 1998 07:11:07 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd020171; Sat Aug 8 07:11:05 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id HAA13932; Sat, 8 Aug 1998 07:10:55 -0700 (MST) From: Terry Lambert Message-Id: <199808081410.HAA13932@usr02.primenet.com> Subject: Re: C and static initialization with unions To: rotel@indigo.ie Date: Sat, 8 Aug 1998 14:10:55 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, Nicolas.Souchu@prism.uvsq.fr, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808081034.LAA00857@indigo.ie> from "Niall Smart" at Aug 8, 98 11:33:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem here is that "largely" is just as uncompilable as "not at > > all". > > Is it? How many developers care that isn't possible? Only the ones actually doing work with modern developement tools. In other words, only the ones you really want to hear from. > In general, sticking to ANSI C enforces some programming discipline, So does sticking to any particular style guide. > but if a gcc-ism significantly eases development of some code then I > think it makes sense to use it, and come back when some other > production compiler is being used. (if ever) The fallacy here is "any production compiler with gcc extensions". > It seems a trifle silly for everyone to have to use K&R-isms (which > I find a pita) just so you can use some obsolete compiler on some > obsolete processor. You find it a PITA/obsolete because you are bringing prejudices to the table with you. Specifically, because you already use GCC. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 10:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05705 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 10:47:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05700 for ; Sat, 8 Aug 1998 10:47:54 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA00534; Fri, 7 Aug 1998 19:13:18 -0700 (PDT) Message-Id: <199808080213.TAA00534@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kelly Yancey cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: syscons update In-reply-to: Your message of "Thu, 06 Aug 1998 10:55:35 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 19:13:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > I have written an update to the freebsd syscons driver and vidcontrol > > > program to allow for 4 new VGA text modes: 90x25, 90x30, 90x50, 90x60. > > > Yes, 90 columns wide. I had written an assembly program years ago that > > > ran under DOS that switched to 90 columns wide...it works fine on every > > > VGA and SVGA adapter I have ever run across. Basically, it just toggles > > > the VGA adapter from using 9 pixel wide characters to 8 pixel wide > > > characters and then adjusts the horizontal counts accordingly. I'm > > > wrapping up the code for that so I can submit it to the team to include > > > in future FreeBSD releases. > > > > Neat. How would you like to help work on adding support for the VESA > > text modes too? > > That would be great. It's really a shame though...especially when > getting into all the VESA text modes too...that it isn't more modular. There's been endless discussion on modularity; the problem is that it's extremely difficult to acheive in practice. > I was thinking that, in order to not disturb the current syscons > driver, maybe start on a new separate video driver. Something where the > new video driver interfaces to a card-specific driver providing generic > interface ioctl calls for user programs to use. That will make sure we > don't get in the way of the syscons development or break any code that > uses the current syscons driver. Then down the road, we could modify > syscons to go through the video driver for any screen updating. Also, > what would be really exciting is a FreeBSD X server that made calls to > the video driver (rather than having the adapter-specific routines in the X > server). Talk about division of labor...I would think that would make > code cleaner all around. This is a hideous amount of work you're proposing, and without meaning to be insulting it's far more than one person is likely to be able to handle. You'd be better off writing a text console for X and just making X the default console driver. 8) > > It's quite hard for a device driver to open and read from another > > device. What currently happens is actually just a workaround for this; > > instead of creating a pipe and writing mouse events to it, moused > > sends ioctls to the console device. The console device then turns this > > stuff around to make it easy for other consumers to use. > > Good point. Perhaps their should be a standard video/mouse API > (probably should be something for sound too) the way there is a disk > access layer and networking layer. Computers have come a long way, baby. > :) There is a standard mouse API, it's called the /dev/sysmouse protocol, and it's based on an older standard. There's another set of event-based standards called the X Window System. > > In addition, video drivers bulk *large*. You don't want these in the > > kernel. > > No, you're right. I guess better support for modular drivers is needed > before that could happen. No, there is plenty of support for modular drivers. The problem is that you don't appear to understand the magnitude of the tasks that you are describing. 8) > But as far as the video drivers are > concerned...at first it would seem like reinventing the wheel since all > the support currently in the X servers would have to be put in the OS > (where it should have been to begin with, in my opinion). X is an application, it's not part of the operating system. See Windows for a good example why it doesn't belong there. > But the > short-term advantage is that other programs for FreeBSD could easily use > the video adapter's graphics capabilities...especially games :). The You can do this already. Games don't use the operating system interfaces except when they have to; OS interfaces are too slow and generalised. > BTW, I've submitted the 90-column support patches (one for the syscons > driver, one for the vidcontrol program to use the new modes) to the > FreeBSD team...I'll keep my fingers crossed. I've also posted the patches > on a web page: http://www.posi.net/software/public/patch-90col/ Thanks for the patches. I could really do with another 10 columns. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 12:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17281 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 12:30:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17268 for ; Sat, 8 Aug 1998 12:30:52 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01531; Sat, 8 Aug 1998 12:28:20 -0700 (PDT) Message-Id: <199808081928.MAA01531@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: chanders@timing.com (Craig Anderson) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone using cdk with ncurses? In-reply-to: Your message of "Fri, 07 Aug 1998 14:41:08 MDT." <199808072041.OAA03214@count.timing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Aug 1998 12:28:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm looking for a UI library based on curses and came across CDK. > I did not find a FreeBSD port of this but did find the source at > ftp:sunsite.unc.edu/pub/Linux/libs/ui Thanks for the pointer to this. I hadn't run into it before. BSD licensed, too. > There is build support for FreeBSD, but it is not building for me. The BSD build support is bogus. I'll try to finish a port for it later today; the code is pretty clean but the Makefiles need a bit of tweaking. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 13:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22378 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 13:42:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22371 for ; Sat, 8 Aug 1998 13:42:25 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id NAA00485; Sat, 8 Aug 1998 13:38:03 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808082038.NAA00485@rah.star-gate.com> To: FreeBSD Mail cc: grog@lemis.com, jkh@time.cdrom.com, hasty@rah.star-gate.com, julian@whistle.com, hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Remote gdb (was: no boot: config -g and options DDB) In-reply-to: Your message of "Fri, 07 Aug 1998 05:39:59 PDT." <199808071239.AA02310@piet.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <482.902608683.1@rah.star-gate.com> Date: Sat, 08 Aug 1998 13:38:03 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Piet, If you have any good pointers or ideas for a cool network kernel debugger please let me know . Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 13:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23169 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 13:50:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23164 for ; Sat, 8 Aug 1998 13:50:54 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA05464 for ; Sat, 8 Aug 1998 16:50:33 -0400 (EDT) Date: Sat, 8 Aug 1998 16:50:33 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: Questions about MFS_ROOT and MFS_AUTOLOAD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have two questions about MFS: (1) Does option MFS_ROOT mean that the memory file system will be the root of the entire file system hierarchy (all other disk-based file systems, if any, hang off the memory-based file system)? (2) How can the MFS image be made separately from the other part of the kernel? This is required by MFS_AUTOLOAD. Any help is appreciated. -------------------------------------------------- | Zhihui Zhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 14:05:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24753 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 14:05:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24744 for ; Sat, 8 Aug 1998 14:05:21 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id OAA20050; Sat, 8 Aug 1998 14:04:51 -0700 (PDT) (envelope-from jdp) Message-Id: <199808082104.OAA20050@austin.polstra.com> To: Thomas David Rivers cc: hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 10:11:00 EDT." <199808071411.KAA23820@lakes.dignus.com> Date: Sat, 08 Aug 1998 14:04:51 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let me add to this discussion my (now somewhat tired) song regarding > compiling older pre-ANSI software. > > It's very nice that we can 'turn off' "const", "volatile", > prototypes in the header files; just for this purpose... > > Every now-and-then, a stray "const" seems to slip into the headers; > which breaks some of my older software... How could that happen? We don't change your old software. We change FreeBSD. FreeBSD is built using the FreeBSD compiler. That compiler is not K&R, and it never will be K&R again. If you are using an old compiler to compile FreeBSD header files, then I can only say, "Don't do that." We have explicitly abandoned the goal of being compatible with K&R compilers. If you mean that your old software isn't const-correct, then (a) that's a compiler warning under FreeBSD, not an error, and (b) isn't it about time you fixed your software? The ANSI/ISO C standard was ratified almost 10 years ago. Surely everybody has had ample time to get used to the idea by now. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 15:08:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00212 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 15:08:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00207 for ; Sat, 8 Aug 1998 15:08:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA02145; Sat, 8 Aug 1998 15:06:45 -0700 (PDT) Message-Id: <199808082206.PAA02145@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Polstra cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-reply-to: Your message of "Sat, 08 Aug 1998 14:04:51 PDT." <199808082104.OAA20050@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Aug 1998 15:06:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Let me add to this discussion my (now somewhat tired) song regarding > > compiling older pre-ANSI software. > > > > It's very nice that we can 'turn off' "const", "volatile", > > prototypes in the header files; just for this purpose... > > > > Every now-and-then, a stray "const" seems to slip into the headers; > > which breaks some of my older software... > > How could that happen? We don't change your old software. We change > FreeBSD. FreeBSD is built using the FreeBSD compiler. That compiler > is not K&R, and it never will be K&R again. If you are using an old > compiler to compile FreeBSD header files, then I can only say, "Don't > do that." We have explicitly abandoned the goal of being compatible > with K&R compilers. > > If you mean that your old software isn't const-correct, then (a) > that's a compiler warning under FreeBSD, not an error, and (b) isn't > it about time you fixed your software? The ANSI/ISO C standard was > ratified almost 10 years ago. Surely everybody has had ample time to > get used to the idea by now. Unfortunately, they haven't. I've had (several) run-ins with const poisoning trying to port a large third-party codebase. It's sufficiently bogus to require -traditional to build, and I expect not too novel in that regard. If we support compilation of K&R application code, we should attempt to make sure that system headers function correctly in that regard. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 15:12:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00648 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 15:12:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00641 for ; Sat, 8 Aug 1998 15:12:49 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA02183; Sat, 8 Aug 1998 15:11:31 -0700 (PDT) Message-Id: <199808082211.PAA02183@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: zhihuizhang cc: hackers Subject: Re: Questions about MFS_ROOT and MFS_AUTOLOAD In-reply-to: Your message of "Sat, 08 Aug 1998 16:50:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Aug 1998 15:11:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, I have two questions about MFS: > > (1) Does option MFS_ROOT mean that the memory file system will be the root > of the entire file system hierarchy (all other disk-based file systems, if > any, hang off the memory-based file system)? It means that the kernel-internal MFS will be mounted as /. If your startup code in that filesystem mounts others, then they will be hung off the MFS, yes. > (2) How can the MFS image be made separately from the other part of the > kernel? This is required by MFS_AUTOLOAD. Use 'dd' to create a file of the appropriate size, then 'vnconfig' to attach it to a 'vn' device, then newfs it and install stuff as desired. Have a look at the way that the src/release makefile does it as it builds the MFS for the install kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 19:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28830 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 19:46:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28825 for ; Sat, 8 Aug 1998 19:46:19 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id VAA16003; Sat, 8 Aug 1998 21:45:15 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id WAA16415; Sat, 8 Aug 1998 22:19:45 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id VAA28991; Sat, 8 Aug 1998 21:49:23 -0400 (EDT) Date: Sat, 8 Aug 1998 21:49:23 -0400 (EDT) From: Thomas David Rivers Message-Id: <199808090149.VAA28991@lakes.dignus.com> To: jdp@polstra.com, rivers@dignus.com Subject: Re: C and static initialization with unions Cc: hackers@FreeBSD.ORG In-Reply-To: <199808082104.OAA20050@austin.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Let me add to this discussion my (now somewhat tired) song regarding > > compiling older pre-ANSI software. > > > > It's very nice that we can 'turn off' "const", "volatile", > > prototypes in the header files; just for this purpose... > > > > Every now-and-then, a stray "const" seems to slip into the headers; > > which breaks some of my older software... > > How could that happen? We don't change your old software. We change > FreeBSD. FreeBSD is built using the FreeBSD compiler. That compiler > is not K&R, and it never will be K&R again. If you are using an old > compiler to compile FreeBSD header files, then I can only say, "Don't > do that." We have explicitly abandoned the goal of being compatible > with K&R compilers. I believe you can find more details in the mail archives... I've sent out mail on it in the past. > > If you mean that your old software isn't const-correct, then (a) > that's a compiler warning under FreeBSD, not an error, and (b) isn't > it about time you fixed your software? The ANSI/ISO C standard was > ratified almost 10 years ago. Surely everybody has had ample time to > get used to the idea by now. Actually, the problem I have is with new software... The situation is that I have a set of portable C code which has to be compiled with a non-ANSI compiler. Now, you're right that I shouldn't have to contend with a non-ANSI compiler in this day and age, but here's the reasons I do: 1) Typically, the ANSI compiler is an add-on cost, using the "free" non-ANSI compiler can save money. 2) On at least one machine, the ANSI compiler has soooo many bugs as to make it unusable. So, in order to ferret out potential problems *before* I try to compile on those platforms where I don't have gcc, and have to use the non-ANSI compiler; I use -traditional on FreeBSD. Every now-and-then, a stray 'const' will appear in the freebsd system headers; which breaks the -traditional compilation. It's kinda bothersome, especially since defines a nice symbol to handle this (__const). For example, in 2.2.6; resolve.h has: resolv.h:extern const struct res_sym __p_class_syms[]; resolv.h:extern const struct res_sym __p_type_syms[]; resolv.h:const char * sym_ntos __P((const struct res_sym *, int, int *)); resolv.h:const char * sym_ntop __P((const struct res_sym *, int, int *)); resolv.h:const char * loc_ntoa __P((const u_char *, char *)); resolv.h:const char * hostalias __P((const char *)); resolv.h:const char * p_class __P((int)); resolv.h:const char * p_time __P((u_int32_t)); resolv.h:const char * p_type __P((int)); ... though it explicitly #includes The one I typically run into is : time.h:const char *strptime __P((const char *, const char *, struct tm *)); so normally the first thing I do after an installation of a new FreeBSD is fix time.h [I believe there already is a PR# of this particular problem.] My point is; it sure is nice for the -traditional option to actually work... and every now-and-then, you have a reasonable reason for wanting it to. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 20:02:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00713 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 20:02:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cola1.bekkoame.or.jp (cola1.bekkoame.or.jp [202.231.192.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00606; Sat, 8 Aug 1998 20:02:01 -0700 (PDT) (envelope-from mei@tau.bekkoame.ne.jp) Received: from yagi.tau.bekkoame.ne.jp (tkya1152.bekkoame.or.jp [202.210.145.152]) by cola1.bekkoame.or.jp (8.8.8/3.6Wbeta7) with ESMTP id LAA19253; Sun, 9 Aug 1998 11:04:05 +0900 (JST) Received: from yagi (localhost [127.0.0.1]) by yagi.tau.bekkoame.ne.jp (8.8.8/3.5Wpl7) with ESMTP id LAA00406; Sun, 9 Aug 1998 11:03:39 +0900 (JST) Message-Id: <199808090203.LAA00406@yagi.tau.bekkoame.ne.jp> To: freebsd-hackers@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: ZIP drive In-Reply-To: Your message of "Thu, 06 Aug 1998 19:55:15 +0200" References: <77184A69146C.AAAF9E@smtp01.wxs.nl> X-Mailer: Mew version 1.70 on Emacs 19.34.2 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 09 Aug 1998 11:03:39 +0900 From: MATSUI Hirokazu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. > anyone tried using the CURRENT 3.0 drivers for the Iomega ZIP drive under > 2.2.6? Because the original ppbus distribution package has some errors, and > since SNAP has this driver in it's distribution I thought that it might be > usable under 2.2.6 too... I'm using 'ppb1125.tgz' distribution from 'http://www.prism.uvsq.fr/~son/PPBUS/ppbus.html' under 2.2.6-RELEASE. Do you have 'some errors' with this distribution ? It works enough for me. -- hiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 20:24:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03551 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 20:24:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03546 for ; Sat, 8 Aug 1998 20:24:48 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-97.camalott.com [208.229.74.97]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA29927; Sat, 8 Aug 1998 22:24:11 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA18894; Sat, 8 Aug 1998 22:22:42 -0500 (CDT) (envelope-from joelh) Date: Sat, 8 Aug 1998 22:22:42 -0500 (CDT) Message-Id: <199808090322.WAA18894@detlev.UUCP> To: chuckr@glue.umd.edu CC: garbanzo@hooked.net, tlambert@primenet.com, faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Fri, 7 Aug 1998 23:43:58 -0400 (EDT)) Subject: Re: C and static initialization with unions From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, it's not the compiler, it's the linker here that's important, and > don't hold your breath on that, GNU hasn't supported our a.out for a > _very_ long time ... I don't think, without FreeBSD modifications, that > they ever did. What are the current stumbling blocks? I'm interested in resyncing the gcc's. Somebody else recently expressed such an interest, but I haven't heard anything; is something being done? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 20:25:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03595 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 20:25:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03588; Sat, 8 Aug 1998 20:25:00 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-97.camalott.com [208.229.74.97]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA29974; Sat, 8 Aug 1998 22:25:29 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA18897; Sat, 8 Aug 1998 22:24:04 -0500 (CDT) (envelope-from joelh) Date: Sat, 8 Aug 1998 22:24:04 -0500 (CDT) Message-Id: <199808090324.WAA18897@detlev.UUCP> To: brett@lariat.org CC: dima@best.net, dg@root.com, roberto@keltia.freenix.fr, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: <199808080641.AAA16434@lariat.lariat.org> (message from Brett Glass on Sat, 08 Aug 1998 00:40:49 -0600) Subject: Re: Does this mean we have another breakin? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808080135.SAA00798@implode.root.com> <199808080641.AAA16434@lariat.lariat.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> We usually get this bug once in two weeks. But since file by itself >> stays the same and machine doesn't crash, fixing/finding the problem >> wasn't in out TODO list. > The MD5 of the file stayed the same, and diff reveals no change. But > we can't turn off the alarm that's triggered by the date change in > /usr/sbin without potentially missing breakins, so our two new admins > are constantly getting scary messages. grep out what you're ignoring? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 21:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09246 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 21:29:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09238 for ; Sat, 8 Aug 1998 21:28:58 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id XAA16244; Sat, 8 Aug 1998 23:26:04 -0400 (EDT) Date: Sat, 8 Aug 1998 23:26:04 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Joel Ray Holveck cc: garbanzo@hooked.net, tlambert@primenet.com, faber@ISI.EDU, Nicolas.Souchu@prism.uvsq.fr, mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: C and static initialization with unions In-Reply-To: <199808090322.WAA18894@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Aug 1998, Joel Ray Holveck wrote: > > Well, it's not the compiler, it's the linker here that's important, and > > don't hold your breath on that, GNU hasn't supported our a.out for a > > _very_ long time ... I don't think, without FreeBSD modifications, that > > they ever did. > > What are the current stumbling blocks? I'm interested in resyncing > the gcc's. Somebody else recently expressed such an interest, but I > haven't heard anything; is something being done? It was done once, but the GNU people didn't apply the patches they were sent. If I remember correctly, some parts were applied, but not enough to get it working. Seeing as our move to ELF is really close, and that will obsolete the a.out, it seems to me to be wasted time. > > Happy hacking, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 23:38:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16753 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 23:38:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16748 for ; Sat, 8 Aug 1998 23:38:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA06196; Sun, 9 Aug 1998 16:08:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA11224; Sun, 9 Aug 1998 16:08:29 +0930 (CST) Message-ID: <19980809160829.A11214@freebie.lemis.com> Date: Sun, 9 Aug 1998 16:08:29 +0930 From: Greg Lehey To: dg@root.com, John Baldwin Cc: FreeBSD Hackers Subject: Re: AMD-specific kernel code (was: How long a wait?) References: <199808070644.XAA14097@implode.root.com> <19980808182200.E14475@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980808182200.E14475@freebie.lemis.com>; from Greg Lehey on Sat, Aug 08, 1998 at 06:22:00PM +0930 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 8 August 1998 at 18:22:00 +0930, Greg Lehey wrote: > (following up to -hackers) > > On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >>> I have a question and I hope this is the right list.. How long is the normal >>> turn around for a response to a non-critical PR? A friend of mine who runs an >>> ISP submitted a PR (6269) that turns on an extra option for AMD K5 and K6 >>> CPU's. He says that it gave his AMD-based webserver a whopping 15% performance >>> increase! He submitted it on Apr 10 of this year (almost 4 months ago) and no >>> one has bothered to even reply to it or anything. As a result, he's somewhat >>> disappointed and not to eager to contribute code in the future as he just >>> thinks he'll get blown off. Of the programmers that I actually know >>> personally, he's the best, and I'd hate for him to not make any further >>> contributions. So, how are PR patches normally handled? Do you wait for >>> enough people to try it out and respond saying it works? I'm just curious, and >>> I wouldn't mind FreeBSD having a patch committed that increases performance by >>> 15% on some machines. Please cc me in replies as I'm not subscribed to >>> questions, thanks. >> >> I just looked at the patch. Other than some KNF style bugs, it seems okay. >> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >> be committing it. >> If it could get wider circulation - perhaps by posting a note to hackers >> asking for testers, then I think there would be less hesitation in getting >> it committed. > > I've grabbed the code and will try it out and report. I've now tried it out. It was suffering from a bit of software rot, but I was able to get it to work, with one puzzling exception: it prints the message "AMD K6 write allocate enabled\n", but it doesn't appear in msgbuf. I've confirmed by setting breakpoints in the code that it does, indeed, go through the code. Does anybody have an idea what could cause this? The effect on CPU performance is also noticable: here are "make world" times: Without write allocate: real 106m58.441s user 63m0.960s sys 20m25.035s With write allocate: real 114m16.402s user 69m41.733s sys 17m54.862s These were only a rough test (I had other stuff running at the same time), but in practice this normally only makes about 1 minute difference. I'd guess that the difference *is* real. Obviously there must be a reason for enabling or disabling this behaviour, and I'd guess that write allocation is most effective when one process is using much CPU time. 'make world' starts thousands of short-lived process, and may thus be the worst-case scenario. In this connection, it's also interesting to note that system time was down and user time was up with write allocation. I have patches available. Does anybody want to commit them? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 8 23:50:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17711 for freebsd-hackers-outgoing; Sat, 8 Aug 1998 23:50:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17676 for ; Sat, 8 Aug 1998 23:49:57 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA23702; Sat, 8 Aug 1998 23:49:51 -0700 (PDT) Message-Id: <199808090649.XAA23702@implode.root.com> To: Greg Lehey cc: John Baldwin , FreeBSD Hackers Subject: Re: AMD-specific kernel code (was: How long a wait?) In-reply-to: Your message of "Sun, 09 Aug 1998 16:08:29 +0930." <19980809160829.A11214@freebie.lemis.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 08 Aug 1998 23:49:51 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The effect on CPU performance is also noticable: here are "make >world" times: > >Without write allocate: > >real 106m58.441s >user 63m0.960s >sys 20m25.035s > >With write allocate: > >real 114m16.402s >user 69m41.733s >sys 17m54.862s > >These were only a rough test (I had other stuff running at the same >time), but in practice this normally only makes about 1 minute >difference. I'd guess that the difference *is* real. Obviously there >must be a reason for enabling or disabling this behaviour, and I'd >guess that write allocation is most effective when one process is >using much CPU time. 'make world' starts thousands of short-lived >process, and may thus be the worst-case scenario. In this connection, >it's also interesting to note that system time was down and user time >was up with write allocation. > >I have patches available. Does anybody want to commit them? Based on the above performance numbers, I'd say no - they appear to be a pessimization. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message