From owner-freebsd-hackers Sun Aug 23 00:12:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07673 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 00:12:19 -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 AAA07667 for ; Sun, 23 Aug 1998 00:12:15 -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 HAA00162; Sun, 23 Aug 1998 07:27:10 +0200 From: Luigi Rizzo Message-Id: <199808230527.HAA00162@labinfo.iet.unipi.it> Subject: Re: What options for BW quickcam on 2.2.7 ? To: abelits@phobos.illtel.denver.co.us (Alex Belits) Date: Sun, 23 Aug 1998 07:27:10 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Alex Belits" at Aug 22, 98 01:44:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Aug 1998, Luigi Rizzo wrote: > > The qcam package (0.9beta6) does not seem to work on my machine, > > and the cqcam code in the ports is only for color qcam. > > > > Do you have any pointers to _working FreeBSD code_ for the B/W qcam ? > > > > I wrote qcread, and it works with both color and b&w quickcams on > freebsd. The latest version is 0.3, and it's at > http://www.illtel.com/pub/qcread/README.html . If there is any problem > with it, please contact me. whoops... sorry i did not mean that qcread did not work, just wondered if there was some other more featured package including a live viewer or vic support. From what i have read i ghess one can import most things from qcam... anyone wants to make a FreeBSD "port" for qcread ? cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 06:03:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14073 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 06:03:14 -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 GAA14066 for ; Sun, 23 Aug 1998 06:03:12 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-111.camalott.com [208.229.74.111]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id IAA01901; Sun, 23 Aug 1998 08:03:42 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id IAA09038; Sun, 23 Aug 1998 08:01:22 -0500 (CDT) (envelope-from joelh) Date: Sun, 23 Aug 1998 08:01:22 -0500 (CDT) Message-Id: <199808231301.IAA09038@detlev.UUCP> To: imp@village.org CC: dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG In-reply-to: <199808230515.XAA18500@harmony.village.org> (message from Warner Losh on Sat, 22 Aug 1998 23:15:56 -0600) Subject: Re: I want to break binary compatibility. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808220240.VAA16809@nospam.hiwaay.net> <199808230515.XAA18500@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I have a problem with some hackers that are obsessed with making my >>> ISP's life miserable (they've already hacked our SGI). I've slapped >>> together a FreeBSD box to throw their webpages on it, turned off all >>> services except http. >> While you are at it and breaking binary compatibility for security >> reasons, make sure you remove stuff a webserver doesn't need such as >> /usr/include, compilers, manpages, etc. Maybe PicoBSD would be the >> place to start? > You are better off NOT breaking binary compatibility to get what you > want. You would be better served by porting StackGuard to FreeBSD, > which would give you excellent protection against most stack > overflows. I think the idea rabtter had in mind was to keep the intruders from compiling (or cross-compiling) some random utility from rootshell.com on another box and ftping it over. There are security holes other than stack overflows, you know. 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 Sun Aug 23 08:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26743 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 08:35:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26728 for ; Sun, 23 Aug 1998 08:34:59 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id KAA09932 for ; Sun, 23 Aug 1998 10:32:38 -0400 (EDT) Date: Sun, 23 Aug 1998 10:32:37 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-Hackers@FreeBSD.ORG Subject: PCI devices 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 Does anyone know where I might find a good example of probing and attaching a pci device? I'm talking about the C code. I'm looking at a PCI sound card, but I can't find anything on how to do sound stuff using PCI. 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 23 10:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06642 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 10:45:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA06611 for ; Sun, 23 Aug 1998 10:45:40 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA18976; Sun, 23 Aug 1998 13:47:53 -0400 From: Bill Paul Message-Id: <199808231747.NAA18976@skynet.ctr.columbia.edu> Subject: Re: PCI devices To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 23 Aug 1998 13:47:51 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Aug 23, 98 10:32:37 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chuck Robey had to walk into mine and say: > Does anyone know where I might find a good example of probing and > attaching a pci device? I'm talking about the C code. I'm looking at a > PCI sound card, but I can't find anything on how to do sound stuff using > PCI. > > Thanks. I would start by looking at the device drivers in /sys/pci. That's where I started. For the most part, you don't need to do very much to probe a PCI device: the PCI support code finds all PCI devices that are in the system for you. The PCI support code knows about what drivers are in the system by using linker sets: each driver has a linker set which specifies the name of the probe and attach routines in the driver (which are normally declared static), and the PCI code will run down the list of available drivers and call the probe routine of each one. The probe routine is very simple: the PCI support code takes the PCI device ID (which is a 32-bit value containing a 16-bit vendor ID and 16-bit device ID) for all the PCI devices that it finds and passes them in turn to all available device drivers. The driver probe routine compares the ID to a list of vendor/drvice IDs that it knows about, and if the supplied ID matches one in its list, it returns a pointer to a string describing the device. If there's no match, it returns NULL. Once the PCI code gets a positive result back from a probe routine, it will call back to the attach routine later to complete the setup. The attach routine is passed a PCI config_id handle which can be used with various functions to read or write PCI registers from the device. There are a couple of things you have to do in the attach routine: - Obtain the iobase or membase address of the device. You need this in order to be able to issue commands to the device or read its non-PCI registers. PCI devices can be controlled in one of two ways: you can either use PIO accesses through I/O space using inb/outb and friends, or you can map the device's register directly into system memory, in which case you can just read and write directly to memory locations. Not all devices support memory mapping however; check your manual. Also, sometimes the PCI BIOS will not enable memory mapped access when configuring the device: if this is the case, you need to use pci_conf_write() to flip on the right bit in the command register. There's also a bit for enabling iospace access. (You can use pci_conf_read() to read the register.) - If you choose to use memory mapped access, you need to call pci_map_mem() to map the memory region and obtain its base address. You will get both a kernel virtual address and a physical one. You will most likely want the kernel virtual one. - Enable bus mastering support. If your device uses bus-master DMA, you might have to enable it by setting the correct bit in the command register. Again, this should be set by the PCI BIOS, but sometimes it isn't. Note that when using bus-master DMA, you generally have to give the chip the address of a memory buffer from which data will be transfered (or into which data will be transfered). This address must be a physical address, not a kernel virtual address, since the device knows nothing about the kernel's virtual memory mappings. You obtain the physical address using vtophys(), however once you have the physical address I don't think you can transform it back to a kernel virtual address since there may be more than one virtual to physical mapping. Also note that sometimes bus master PCI devices will exhibit strange failure modes if you put them in the wrong slot. My understanding is that PCI bus master devices must go in bus master slots, and putting them in PCI slave slots won't work. - You need to install your interrupt handler. This is done using pci_map_int(). You need to supply a pointer to your interrupt handler routine. This is generic PCI setup which applies to any PCI device: the offsets of the command register and IRQ line register are well known and defined in /sys/pci/pcireg.h, along with other standard register offsets common to all PCI devices. Your device may have other non-standard PCI registers; if so, they should be described in the documentation. If not, LART the vendor. One newer wrinkle is power management. Devices which support power management have a capabilities ID register, which will have a bit set to indicate that power management is available. There's also a power management status register and control register. You may need to insure that the device is set to the correct power mode (D0 is usually the full power mode) before putting the device into operation. Windoze is known to set some devices into low power mode during shutdown; if you warm boot from Windoze to FreeBSD, you may then have to put the device back into the right power mode in the attach routine (the PCI BIOS is supposed to do this, but older BIOSes may not). As for 'PCI sound stuff,' that I don't know about. So far I've only written network drivers, but I'd wager that there are a couple of similarities. You probably have to provide a way to transfer large streams of encoded audio data into and out of the adapter, which is probably where DMA comes in. You have to give the card pointers to buffers containing audio data to be played, then wait for an interrupt from the card telling you the transfer is complete so you can free the buffers and transfer more. And you need to be able to program mixer levels and things using internal registers. I don't know about things like MIDI or wave tables so I can't imagine how those work. I'm assuming you do have the proper documentation for your board; if not you're going to be totally lost. -Bill P.S.: Don't be fooled by marketing literature (or clueless lusers) who talk about PCI adapters with "plug & play" support. PCI implies "plug & play" in that the PCI BIOS works out what iospace and membase addresses and IRQs to assign to cards in order to avoid resource conflicts. But this is not the same as Plug & Play (tm), which I think only applies to ISA boards. I sometimes see people on mailing lists or newsgroups complaining that their PCI devices don't work for some reason, and often someone follows up with a suggestion to "disable plug & play| support. These people are confused: PCI devices don't support Plug & Play (tm), so there's nothing to turn off. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 11:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08782 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 11:02:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08777 for ; Sun, 23 Aug 1998 11:02:39 -0700 (PDT) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com (ppp154.dialin.bonn-online.com [194.162.223.154]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id UAA15955; Sun, 23 Aug 1998 20:01:29 +0200 Message-ID: <35E05910.29931BA0@bonn-online.com> Date: Sun, 23 Aug 1998 20:01:52 +0200 From: Sebastian Lederer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Alfred Perlstein CC: Alex , hackers@FreeBSD.ORG, support@yard.de Subject: Re: Linux vs FreeBSD (performances) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > urm > > FreeBSD bright.x 3.0-CURRENT FreeBSD 3.0-CURRENT #7: Sun Aug 16 > 22:05:13 EST 1998 > bright@bright.x:/usr/src/sys/compile/bright i386 > > Linux poopie 2.1.76 #8 Sun Jan 18 03:42:15 EST 1998 i686 unknown > > that's the kernels, btw, about your previous post, every linux user i've > talked to says the NFS is userland. you are sure about it being in > kernel? > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's BSD. > -- http://www.freebsd.org/ > On a side note: Recent linux kernels have support for in-kernel nfsd/mountd/statd/lockd (with real locking functionality). Don't know if or how well this works, though. -- Sebastian Lederer lederer@bonn-online.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 23 14:44:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26096 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 14:44:12 -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 OAA26091 for ; Sun, 23 Aug 1998 14:44:10 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.8/8.8.5) with SMTP id RAA13088 for ; Sun, 23 Aug 1998 17:45:04 -0400 (EDT) Date: Sun, 23 Aug 1998 17:45:04 -0400 (EDT) From: Mark turpin To: FreeBSD hackers Subject: PCI Device driver 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 Hello, This is my first attempt at writing a device driver.. I read most of the other drivers in the pci directory before starting and thought I knew what I was doing... Well, obviously I didn't :) So, I need your help.. All I want to do right now is make it show that it actually found the device on the startup list. Please help Thanks Mark Turpin I added the following line to files pci/if_rtk.c rtk device-driver and to GENERIC in i386/conf device rtk0 and here is my wonderful code.... #include "pci.h" #if NPCI > 0 #include #include #include #include #include #include #include "rtk.h" static char* rtk_pci_probe __P((pcici_t, pcidi_t)); static void rtk_pci_attach __P((pcici_t config_id, int unit)); static u_long rtk_pci_count = NRTK; static struct pci_device rtk_pci_driver = { "rtk", rtk_pci_probe, rtk_pci_attach, &rtk_pci_count, NULL }; static char* rtk_pci_probe (config_id, device_id) pcici_t config_id; pcidi_t device_id; { if (device_id && 0x813910ec) return ("RealTek 8139 10/100Mbps Ethernet"); return NULL; } static void rtk_pci_attach (config_id, unit) pcici_t config_id; int unit; { /* Attach stuff goes here */ return; } #endif /* NPCI > 0 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 15:50:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03141 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 15:50:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d4.dialup.hilink.com.au [203.2.144.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03049 for ; Sun, 23 Aug 1998 15:50:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA24438 for ; Sun, 23 Aug 1998 15:18:14 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808231518.PAA24438@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Sun, 23 Aug 1998 13:47:51 -0400." <199808231747.NAA18976@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Aug 1998 15:18:14 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > P.S.: Don't be fooled by marketing literature (or clueless lusers) who > talk about PCI adapters with "plug & play" support. PCI implies > "plug & play" in that the PCI BIOS works out what iospace and > membase addresses and IRQs to assign to cards in order to avoid > resource conflicts. But this is not the same as Plug & Play (tm), > which I think only applies to ISA boards. I sometimes see people > on mailing lists or newsgroups complaining that their PCI devices > don't work for some reason, and often someone follows up with > a suggestion to "disable plug & play| support. These people are > confused: PCI devices don't support Plug & Play (tm), so there's > nothing to turn off. For clarity's sake and no more, let me point out that "Plug and Play" is a generic term describing zero-user-intervention configuration. PCI is implicitly "plug and play" - you can't have a non-PnP PCI card, so it's more correct to say that PCI devices only support Plug-n-Play so you can't turn it off. This confusion is common; many people refer to PnP only in the context of ISA PnP, but PnP is a generic term applied to ISA PnP, PCI, PCMCIA, CardBUS, USB, etc. -- \\ 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 23 17:53:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13680 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 17:53:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13665 for ; Sun, 23 Aug 1998 17:53:48 -0700 (PDT) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:beattie@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id RAA24709; Sun, 23 Aug 1998 17:51:26 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id RAA10738; Sun, 23 Aug 1998 17:52:56 -0700 Date: Sun, 23 Aug 1998 17:52:56 -0700 (PDT) From: Brian Beattie To: Mikael Karpberg cc: "B. Richardson" , hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. In-Reply-To: <199808220009.CAA05667@ocean.campus.luth.se> 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 This approach will no no good, if the hackesr can down load a binary, because they see what has been done. I thought scrambling the syscall table was good but it also falls to the dowloaded binaty, although it is a lot harder to decipher. I was thinking you could encrypt all your binariaes and use a scheme like the compressed executables. unfortubately this would fall prey to the know plaintext attack. I would say that of the ideas I have herad so far the scrambled syscall table seems to have the best band for the buck. On Sat, 22 Aug 1998, Mikael Karpberg wrote: > According to B. Richardson: > > > > > > I have a problem with some hackers that are obsessed with making my > > ISP's life miserable (they've already hacked our SGI). I've slapped > > together a FreeBSD box to throw their webpages on it, turned off all > > services except http. > > > > The hackers have expressed intent to break into our machines at > > any opportunity (they seem to be infuriated that we intervened and > > was able to keep a couple of services up on our SGI). > > > > The hackers relentlessly attacked our machine every time we tried to > > bring our SGI online for a 48 hour stretch, and I believe that are > > going to try to break into our new machines with the same fervor. > > > > What I want to do, if possible is build a uniq system such that binaries > > from other systems will not run on it and vice versa. Is this possible? > > One simple way could be to just change the "magic number" on the binaries, > maybe, and disable all linux compat, etc? > > /Mikael > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Beattie | If my corporate life has taught me anything, beattie@aracnet.com | it was that running multi-million dollar www.aracnet.com/~beattie | projects in no way implied managerial competence. | Tony Porczyk ( in comp.unix.bsd.freebsd.misc ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 18:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16408 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 18:06:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16337 for ; Sun, 23 Aug 1998 18:06:02 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id UAA11357; Sun, 23 Aug 1998 20:03:38 -0400 (EDT) Date: Sun, 23 Aug 1998 20:03:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Mark turpin cc: FreeBSD hackers Subject: Re: PCI Device driver question 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, 23 Aug 1998, Mark turpin wrote: > Hello, > > This is my first attempt at writing a device driver.. I read most > of the other drivers in the pci directory before starting and thought I > knew what I was doing... Well, obviously I didn't :) So, I need your > help.. All I want to do right now is make it show that it actually found > the device on the startup list. > > Please help > Thanks > > Mark Turpin > I am looking at the example I've chosen, cy_pci.c, and the pci code figures out what to probe via linker sets, but I don't see the line in your code below that corresponds to the line 62 of cy_pci.c, as I show below: DATA_SET(pcidevice_set, cy_device); I think maybe you might be missing this line, so the pci code never probes your device. If I'm wrong, I'll be watching with interest for someone to correct me. > > I added the following line to files > > pci/if_rtk.c rtk device-driver > > and to GENERIC in i386/conf > > device rtk0 > > and here is my wonderful code.... > > > #include "pci.h" > #if NPCI > 0 > > #include > #include > #include > #include > #include > #include > > #include "rtk.h" > > static char* rtk_pci_probe __P((pcici_t, pcidi_t)); > static void rtk_pci_attach __P((pcici_t config_id, int unit)); > > static u_long rtk_pci_count = NRTK; > > static struct pci_device rtk_pci_driver = { > "rtk", > rtk_pci_probe, > rtk_pci_attach, > &rtk_pci_count, > NULL > }; > > static char* > rtk_pci_probe (config_id, device_id) > pcici_t config_id; > pcidi_t device_id; > { > if (device_id && 0x813910ec) > return ("RealTek 8139 10/100Mbps Ethernet"); > > return NULL; > } > > static void > rtk_pci_attach (config_id, unit) > pcici_t config_id; > int unit; > { > > /* Attach stuff goes here */ > return; > > } > #endif /* NPCI > 0 */ > > > > 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 Sun Aug 23 18:21:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19458 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 18:21:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19449 for ; Sun, 23 Aug 1998 18:21:47 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id UAA11399; Sun, 23 Aug 1998 20:19:19 -0400 (EDT) Date: Sun, 23 Aug 1998 20:19:19 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: PCI devices In-Reply-To: <199808231747.NAA18976@skynet.ctr.columbia.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 Sun, 23 Aug 1998, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Chuck Robey had > to walk into mine and say: > > > Does anyone know where I might find a good example of probing and > > attaching a pci device? I'm talking about the C code. I'm looking at a > > PCI sound card, but I can't find anything on how to do sound stuff using > > PCI. > > > > Thanks. > > I would start by looking at the device drivers in /sys/pci. That's > where I started. [some deletions] > As for 'PCI sound stuff,' that I don't know about. So far I've only > written network drivers, but I'd wager that there are a couple of > similarities. You probably have to provide a way to transfer large > streams of encoded audio data into and out of the adapter, which is > probably where DMA comes in. You have to give the card pointers > to buffers containing audio data to be played, then wait for an > interrupt from the card telling you the transfer is complete so you > can free the buffers and transfer more. And you need to be able to > program mixer levels and things using internal registers. I don't know > about things like MIDI or wave tables so I can't imagine how those work. > I'm assuming you do have the proper documentation for your board; > if not you're going to be totally lost. Among other things, the sound code wants to use linker sets for probing and other things, just like the pci code. I wondered about this, and my current best guess is to register both, with the pci routines doing the real work, and the sound routines merely checking the results and making sure the probe/attach was successful. You see, there are functions automatically registered/called via the sound code stuff that pci doesn't know about, so I can't completely ignore it. Does this sound reasonable (to have the probe + attach work done in two places, sort of? ----------------------------+----------------------------------------------- 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 23 18:38:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22867 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 18:38:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from notreal.com (afraid.of.scientol.ogy.org [206.86.192.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22845 for ; Sun, 23 Aug 1998 18:38:44 -0700 (PDT) (envelope-from dpk@notreal.com) Received: from localhost (dpk@localhost) by notreal.com (8.9.1/8.9.1) with SMTP id SAA19951; Sun, 23 Aug 1998 18:37:57 -0700 (PDT) (envelope-from dpk@notreal.com) Date: Sun, 23 Aug 1998 18:37:57 -0700 (PDT) From: David Kirchner To: "B. Richardson" cc: hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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, 21 Aug 1998, B. Richardson wrote: > What I want to do, if possible is build a uniq system such that binaries > from other systems will not run on it and vice versa. Is this possible? I haven't seen this mentioned yet: Would it be possible to hack the kernel so binaries will only be run if they have a certain "binary signature", one that is different for every machine. You'd want to do all compilation on another, possibly non-networked box, and then install all binaries mode '111' (or 4111 or whatever) so nobody could read the "signature". Maybe this is how the whole magic number thing works... I was thinking more along the lines of a 'phrase'. Maybe a make world option in /usr/share/mk or something? -dpk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 19:16:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00591 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 19:16:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.delta.edu (alpha.delta.edu [161.133.129.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA00556 for ; Sun, 23 Aug 1998 19:16:31 -0700 (PDT) (envelope-from dakott@alpha.delta.edu) Received: from pm343-25.dialip.mich.net by alpha.delta.edu; (5.65v3.0/1.1.8.2/06Jan97-0932AM) id AA13944; Sun, 23 Aug 1998 22:20:11 -0400 Received: from kott.my.domain (dakott@kott.my.domain [192.168.0.1]) by kott.my.domain (8.8.8/8.8.5) with SMTP id SAA26790 for ; Fri, 21 Aug 1998 18:58:57 -0400 (EDT) Date: Fri, 21 Aug 1998 18:58:57 -0400 (EDT) From: David Kott To: hackers@FreeBSD.ORG Subject: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] 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 > > OK. If you can lay your hands on an Adaptec 1542, it should work fine. > It's the only ISA/VLB SCSI controller I have any experience with > (which doesn't mean it's the only good one). ISTR there are a few bugs > in our 1542 support, but I haven't paid any attention to it for some > time so I may be wrong. I've run -stable successfully on a few boxen > equipped with 1542s, but not recently. I am using a 1542 right now on this -stable machine. While I am not particularily overwhelmed by it's performance, I have had no problems that I could definately link to the adapter itself. Perhaps I have not configured it for optimal performance. I did have some strange kernel panics when I installed my hardrive in front of the CDROM that previously had occupied the bus alone. The drive would log timeout errors. Then, as now, my root partition/swap et. al was on this drive, the kernel would panic. Also, sporadically, the drive would load the kernel sucessfully for booting, but would just hang when the kernel attempted to mount the root partition. I configured the hardrive to supply the bus termination, instead of the CDROM, as well as recompiling my kernel sans the "TUNE_1542" option, and I haven't had a problem since. Here are some really coarse performance comparisons for you to ignore. :-) -d root@kott [/root]# dd if=/dev/rsd0a of=/dev/null count=1024 1024+0 records in 1024+0 records out 524288 bytes transferred in 3.619458 secs (144853 bytes/sec) root@kott [/root]# dd if=/dev/rwd2s1a of=/dev/null count=1024 1024+0 records in 1024+0 records out 524288 bytes transferred in 0.173658 secs (3019083 bytes/sec) chip2 rev 0 on pci0:7:1 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S aha0: Rev 41 (AHA-154x[AB]) V0.5, enabling residuals, target ops aha0: reading board settings, dma=7 int=11 id=7 (bus speed defaulted) aha0 at 0x330-0x333 irq 11 drq 7 on isa (aha0:0:0): "QUANTUM FIREBALL ST4.3S 0F0C" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 4136MB (8471232 512 byte sectors) sd0(aha0:0:0): with 7068 cyls, 6 heads, and an average 199 sectors/track To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 19:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00630 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 19:17:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.delta.edu (alpha.delta.edu [161.133.129.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA00588 for ; Sun, 23 Aug 1998 19:16:45 -0700 (PDT) (envelope-from dakott@alpha.delta.edu) Received: from pm343-25.dialip.mich.net by alpha.delta.edu; (5.65v3.0/1.1.8.2/06Jan97-0932AM) id AA08853; Sun, 23 Aug 1998 22:20:17 -0400 Received: from kott.my.domain (dakott@kott.my.domain [192.168.0.1]) by kott.my.domain (8.8.8/8.8.5) with SMTP id TAA26804; Fri, 21 Aug 1998 19:03:25 -0400 (EDT) Date: Fri, 21 Aug 1998 19:03:25 -0400 (EDT) From: David Kott To: System Administrator Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sound card programming In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1535989006-903740605=:26738" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1535989006-903740605=:26738 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 21 Aug 1998, System Administrator wrote: > I need play file on the sound card and record to file > from sound card. Where I can find examples of source code for this ? > I have fbsd 2.2.6 > Here is a slightly modified piece of source that I found on one of the mailing list archives that does precisely 1/2 of your request. It was written by one of the FreeBSD gurus/core team (forgive me, but I don't remember precisely who) and did almost exactly what I wanted. -d --0-1535989006-903740605=:26738 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="s2.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: DQojaW5jbHVkZSA8c3RkaW8uaD4NCiNpbmNsdWRlIDx1bmlzdGQuaD4NCiNp bmNsdWRlIDxmY250bC5oPg0KI2luY2x1ZGUgPG1hY2hpbmUvc291bmRjYXJk Lmg+DQoNCg0KI2RlZmluZSBEU1AgIi9kZXYvZHNwIg0KDQppbnQgZHNwZmQ7 DQppbnQgZmlsZWZkOw0KDQptYWluKGludCBhcmdjLCBjaGFyICphcmd2W10p IHsNCiAgICAgICAgY2hhciBidWZmZXJbMjU2XTsNCiAgICAgICAgaW50IHJl YWRjb3VudDsNCiAgICAgICAgaW50IHRvcmVhZDsNCiAgICAgICAgaW50IHBh cm07DQogICAgICAgIHN0cnVjdCBzbmRfc2l6ZSBzdFNvdW5kU2l6ZTsNCiAg ICAgICAgDQogICAgICAgIA0KICAgICAgICBzdFNvdW5kU2l6ZS5wbGF5X3Np emU9MDsNCiAgICAgICAgc3RTb3VuZFNpemUucmVjX3NpemU9MDsNCiAgICAg ICAgDQogICAgICAgIGRzcGZkID0gb3BlbigiL2Rldi9zbmRzdGF0IiwgT19S RE9OTFkpOw0KICAgICAgICBpZiAoZHNwZmQgPCAwKSB7DQogICAgICAgICAg ICAgICAgcGVycm9yKCJkc3BvcGVuIik7DQogICAgICAgICAgICAgICAgZXhp dCgxKTsNCiAgICAgICAgfQ0KICAgICAgIA0KICAgICAgICBpZiAoaW9jdGwo ZHNwZmQsIEFJT0dTSVpFLCBzdFNvdW5kU2l6ZSkpIHsNCiAgICAgICAgICAg ICAgICBwZXJyb3IoImFpb2dzaXplIik7DQogICAgICAgICAgICAgICAgZXhp dCgxKTsNCiAgICAgICAgfQ0KDQogICAgICAgIHBhcm0gPSAxNjsNCiAgICAg ICAgaWYgKGlvY3RsKGRzcGZkLCBTT1VORF9QQ01fUkVBRF9CSVRTLCAmcGFy bSkpIHsNCiAgICAgICAgICAgICAgICBwZXJyb3IoImlvY3RscmQxNiIpOw0K ICAgICAgICAgICAgICAgIGV4aXQoMSk7DQogICAgICAgfQ0KICAgICAgIA0K DQogICAgICAgIHBhcm0gPSAxNjsNCiAgICAgICAgaWYgKGlvY3RsKGRzcGZk LCBTT1VORF9QQ01fV1JJVEVfQklUUywgJnBhcm0pKSB7DQogICAgICAgICAg ICAgICAgcGVycm9yKCJpb2N0bHdyMTYiKTsNCiAgICAgICAgICAgICAgICBl eGl0KDEpOw0KICAgICAgICB9DQoNCiAgICAgICAgcGFybSA9IDI7DQogICAg ICAgIGlmIChpb2N0bChkc3BmZCwgU09VTkRfUENNX1JFQURfQ0hBTk5FTFMs ICZwYXJtKSkgew0KICAgICAgICAgICAgICAgIHBlcnJvcigiaW9jdGxyZDIi KTsNCiAgICAgICAgICAgICAgICBleGl0KDEpOw0KICAgICAgICB9DQoNCiAg ICAgICAgcGFybSA9IDI7DQogICAgICAgIGlmIChpb2N0bChkc3BmZCwgU09V TkRfUENNX1dSSVRFX0NIQU5ORUxTLCAmcGFybSkpIHsNCiAgICAgICAgICAg ICAgICBwZXJyb3IoImlvY3Rsd3IyIik7DQogICAgICAgICAgICAgICAgZXhp dCgxKTsNCiAgICAgICAgfQ0KDQogICAgICAgIHBhcm0gPSA0NDEwMDsNCiAg ICAgICAgaWYgKGlvY3RsKGRzcGZkLCBTT1VORF9QQ01fUkVBRF9SQVRFLCAm cGFybSkpIHsNCiAgICAgICAgICAgICAgICBwZXJyb3IoImlvY3Rsc3A0NDEw MCIpOw0KICAgICAgICAgICAgICAgIGV4aXQoMSk7DQogICAgICAgIH0NCg0K ICAgICAgICBwYXJtID0gNDQxMDA7DQogICAgICAgIGlmIChpb2N0bChkc3Bm ZCwgU09VTkRfUENNX1dSSVRFX1JBVEUsICZwYXJtKSkgew0KICAgICAgICAg ICAgICAgIHBlcnJvcigiaW9jdGxzcDQ0MTAwIik7DQogICAgICAgICAgICAg ICAgZXhpdCgxKTsNCiAgICAgICAgfQ0KDQogICAgICAgIGZpbGVmZCA9IGR1 cCgxKTsNCg0KICAgICAgICB0b3JlYWQgPSBhdG9pKGFyZ3ZbMV0pICogNDQx MDAgKiA0Ow0KICAgICAgICBmcHJpbnRmKHN0ZGVyciwiJWQgc2FtcGxlc1xu IiwgdG9yZWFkKTsNCiAgICAgICAgd2hpbGUgKCB0b3JlYWQgPiAwKSB7DQog ICAgICAgICAgICAgICAgcmVhZGNvdW50ID0gc2l6ZW9mIGJ1ZmZlcjsNCiAg ICAgICAgICAgICAgICBpZiAocmVhZGNvdW50ID4gdG9yZWFkKQ0KICAgICAg ICAgICAgICAgICAgICAgICAgcmVhZGNvdW50ID0gdG9yZWFkOw0KICAgICAg ICAgICAgICAgIHJlYWRjb3VudCA9IHJlYWQoZHNwZmQsIGJ1ZmZlciwgcmVh ZGNvdW50KTsNCiAgICAgICAgICAgICAgICBpZiAocmVhZGNvdW50IDwgMCkg ew0KICAgICAgICAgICAgICAgICAgICAgICAgcGVycm9yKCJkc3ByZWFkIik7 DQogICAgICAgICAgICAgICAgICAgICAgICBleGl0KDEpOw0KICAgICAgICAg ICAgICAgIH0NCiAgICAgICAgICAgICAgICB3cml0ZShmaWxlZmQsIGJ1ZmZl ciwgcmVhZGNvdW50KTsNCiAgICAgICAgICAgICAgICB0b3JlYWQgLT0gcmVh ZGNvdW50Ow0KICAgICAgICB9DQoNCiAgICAgICAgZXhpdCgwKTsNCn0NCg0K --0-1535989006-903740605=:26738-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 19:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05011 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 19:45:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from woody.aiinet.com ([206.103.249.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04999 for ; Sun, 23 Aug 1998 19:45:26 -0700 (PDT) (envelope-from mattg@aiinet.com) Received: by mail2.aiinet.com with Internet Mail Service (5.0.1460.8) id <38TXWNJD>; Sun, 23 Aug 1998 22:44:46 -0400 Message-ID: <7283DE19D141D111AD0E00A0C95B1955CF12A2@mail2.aiinet.com> From: "Gessner, Matt" To: "'hackers'" Subject: Q was on questions, now putting it here. Date: Sun, 23 Aug 1998 22:44:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, all, I posted to comp.unix.bsd.freebsd.misc but nothing's come back... news takes a while. I'm running 2.2.7-RELEASE, and I've already changed my kernel a bit to allow me to do a whole bunch of simultaneous connections, but I've probably done something wrong, because it ain't working. Here's what I have: P5-166 Gateway 32 MB RAM 2 GB disk, 850MB belongs to FreeBSD, of which 100MB is swap. PCI DEC Ethernet card Here's how I've mangled my poor kernel: maxusers 128 options CHILD_MAX=256 options OPEN_MAX=2048 options NMBCLUSTERS=4096 Here's how I've changed login.conf default and root both have unlimited child process and open file counts. I've done a little poking around in param.c and don't see immediately that I've violated any rules by setting these limits the way I have. When I type limits, I get the following info back: maxprocesses 2067 openfiles 4136 But I can't find anything anywhere that talks about tuning the kernel for doing this. What I need to do is be able to run lots of TCP connections, and I know it can be done with FreeBSD. The connections are being made from FreeBSD to a proprietary board and then to a Solaris machine. My end goal is to be able to bring up about 1024 TCP connections outbound and route them back to the same box, for a total of 2048 connections. Right now, I run 1024 connections to the other system, and what happens is when the sockets are all connected, and the writes start to occur, FreeBSD just reboots the machine -- no messages anywhere. Have I really goofed up somewhere/something? Can anyone give me some insight as to what MIGHT be happening here? E-mail is fine, so's the newgroup. I suppose it's completely possible I'm running out of RAM and swap, but I'd expect to see something in /var/log/messages to that effect. So far, nothing. Recently I uppped NMBCLUSTERS to 4096, but it didn't seem to fix the problem. That was based on some notes in the FAQ. Even more recently (but haven't tested it yet) is that I upped my swap space to 256MB for 32MB of RAM. I killed off that nasty Win95 virus that was consuming all that disk space.... Nasty, nasty thing. Thanks in advance, Matt Gessner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 19:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05487 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 19:48:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05474 for ; Sun, 23 Aug 1998 19:48:48 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id VAA24537; Sun, 23 Aug 1998 21:48:01 -0500 (CDT) (envelope-from dan) Message-ID: <19980823214801.A24497@emsphone.com> Date: Sun, 23 Aug 1998 21:48:01 -0500 From: Dan Nelson To: David Kott , hackers@FreeBSD.ORG Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: ; from "David Kott" on Fri Aug 21 18:58:57 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Aug 21), David Kott said: > I am using a 1542 right now on this -stable machine. While I am not > particularily overwhelmed by it's performance, I have had no problems > that I could definately link to the adapter itself. Perhaps I have not > configured it for optimal performance. > > root@kott [/root]# dd if=/dev/rsd0a of=/dev/null count=1024 > 1024+0 records in > 1024+0 records out > 524288 bytes transferred in 3.619458 secs (144853 bytes/sec) > > root@kott [/root]# dd if=/dev/rwd2s1a of=/dev/null count=1024 > 1024+0 records in > 1024+0 records out > 524288 bytes transferred in 0.173658 secs (3019083 bytes/sec) Try rerunning both dd lines with a bs=64k argument; the SCSI bus has a larger per-operation overhead then the IDE bus, and forcing it down to 512-byte transfer chunks isn't really a good benchmark. The 1542 support is quite good as far as I can tell; we use an old Compaq 486/66 and a 1542 as a tape drive machine, and I used to have a 1542 as my main SCSI controller until I got a 2940. -Dan Nelson dnelson@emsphone.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 23 19:54:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06738 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 19:54:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06729 for ; Sun, 23 Aug 1998 19:54:16 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id VAA24587; Sun, 23 Aug 1998 21:53:15 -0500 (CDT) (envelope-from dan) Message-ID: <19980823215315.B24497@emsphone.com> Date: Sun, 23 Aug 1998 21:53:15 -0500 From: Dan Nelson To: David Kott , System Administrator Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sound card programming References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=SLDf9lqlvOQaIe6s X-Mailer: Mutt 0.94.2i In-Reply-To: ; from "David Kott" on Fri Aug 21 19:03:25 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii In the last episode (Aug 21), David Kott said: > On Fri, 21 Aug 1998, System Administrator wrote: > > I need play file on the sound card and record to file from sound > > card. Where I can find examples of source code for this ? I have > > fbsd 2.2.6 > > Here is a slightly modified piece of source that I found on one of > the mailing list archives that does precisely 1/2 of your request. > It was written by one of the FreeBSD gurus/core team (forgive me, but > I don't remember precisely who) and did almost exactly what I wanted. And here are mine; both play and listen default to 8khz, 8bit, mono, but that's easy enough to change, either via the commandline options, or changing the constants in the code. Play will also play to the PC speaker, if you use -s and have enabled the pca device in the kernel. -Dan Nelson dnelson@emsphone.com --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="listen.c" #include #include #include #include main(int argc, char *argv[]) { int fd = open("/dev/dsp", O_RDONLY); int rate = 8012; int bits = 8; int channels = 1; int c; int len; char buf[1024]; while ((c = getopt(argc, argv, "hr:b:c:")) != EOF) { switch (c) { case 'r': rate = atoi(optarg); break; case 'b': bits = atoi(optarg); break; case 'c': channels = atoi(optarg); break; case '?': case 'h': printf ("listen -r rate -b bits -c channels\n"); exit(1); break; } } ioctl(fd, SNDCTL_DSP_SETFMT, &bits); ioctl(fd, SOUND_PCM_WRITE_RATE, &rate); ioctl(fd, SOUND_PCM_WRITE_CHANNELS, &channels); while ((len = read(fd, buf, sizeof(buf))) > 0) write(fileno(stdout), buf, len); } --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="play.c" #include #include #include #include #include #include main(int argc, char *argv[]) { int fd; int rate = 8012; int bits = 8; int speaker = 0; int channels = 1; int c; int len; char buf[1024]; while ((c = getopt(argc, argv, "r:b:c:s")) != EOF) { switch (c) { case 's': speaker = 1; break; case 'r': rate = atoi(optarg); break; case 'c': channels = atoi(optarg); break; case 'b': bits = atoi(optarg); break; case '?': case 'h': printf ("play [-s] [-c channels] [-r rate] [-b bits]\n"); exit(1); break; } } if (speaker) { audio_info_t ait; ait.play.sample_rate = rate; ait.play.encoding = AUDIO_ENCODING_RAW; ait.play.gain = 150; ait.play.pause = -1; fd = open("/dev/pcaudio", O_WRONLY); ioctl(fd, AUDIO_SETINFO, &ait); } else { fd = open("/dev/dsp", O_WRONLY); ioctl(fd, SNDCTL_DSP_SETFMT, &bits); ioctl(fd, SOUND_PCM_WRITE_RATE, &rate); ioctl(fd, SOUND_PCM_WRITE_CHANNELS, &channels); } while ((len = read(fileno(stdin), buf, sizeof(buf))) > 0) write(fd, buf, len); } --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 23:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29529 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 23:21:17 -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 XAA29519 for ; Sun, 23 Aug 1998 23:21:13 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA04415; Mon, 24 Aug 1998 01:20:08 -0500 (EST) (envelope-from toor) Message-Id: <199808240620.BAA04415@dyson.iquest.net> Subject: Re: I want to break binary compatibility. In-Reply-To: <199808231301.IAA09038@detlev.UUCP> from Joel Ray Holveck at "Aug 23, 98 08:01:22 am" To: joelh@gnu.org Date: Mon, 24 Aug 1998 01:20:08 -0500 (EST) Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, 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 Joel Ray Holveck said: > >>> I have a problem with some hackers that are obsessed with making my > >>> ISP's life miserable (they've already hacked our SGI). I've slapped > >>> together a FreeBSD box to throw their webpages on it, turned off all > >>> services except http. > >> While you are at it and breaking binary compatibility for security > >> reasons, make sure you remove stuff a webserver doesn't need such as > >> /usr/include, compilers, manpages, etc. Maybe PicoBSD would be the > >> place to start? > > You are better off NOT breaking binary compatibility to get what you > > want. You would be better served by porting StackGuard to FreeBSD, > > which would give you excellent protection against most stack > > overflows. > > I think the idea rabtter had in mind was to keep the intruders from > compiling (or cross-compiling) some random utility from rootshell.com > on another box and ftping it over. There are security holes other > than stack overflows, you know. > I posted this through another mechanism by mistake, and so I apologize if this message is a repeat for you: Try modifying your system so that one of the flags bits is required to run a program. It would the require both the flags bit and the executable bit. Make sure the system cannot allow anyone but root set the chosen flags bit. Maybe you could use the immutable flag, for this so that you get theoretical immutability along with the ability to run code. You might want to relax the restriction for root, but maybe not (depending on how your admin scheme is setup.) In this way, you would not need to change binary compatibility, but programs will simply not run, unless the user figures out a way to set the flags bit. Hopefully, you will have made sure that the kernel API doesn't allow setting that bit by non-root. -- 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 Sun Aug 23 23:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02107 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 23:40:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from magc.cd.2573.savbank.ru (h26.216.elnet.msk.ru [194.190.216.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02087 for ; Sun, 23 Aug 1998 23:40:05 -0700 (PDT) (envelope-from mag@h26.216.elnet.msk.ru) Received: from magc.cd.2573.savbank.ru (magc.cd.2573.savbank.ru [172.16.201.254]) by magc.cd.2573.savbank.ru (8.8.5/8.8.5) with ESMTP id KAA22629 for ; Mon, 24 Aug 1998 10:41:41 +0400 Message-ID: <35E10B25.F8C4C53F@magc.cd.2573.savbank.ru> Date: Mon, 24 Aug 1998 10:41:41 +0400 From: MAG X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Question about source routing Content-Type: multipart/alternative; boundary="------------A4F75ADA9A8A4B6D79335FF6" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------A4F75ADA9A8A4B6D79335FF6 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Who can help me: can I manage enabling/disabling source routing in FreeBSD? -- Malinin A. G. --------------A4F75ADA9A8A4B6D79335FF6 Content-Type: text/html; charset=koi8-r Content-Transfer-Encoding: 7bit     Who can help me: can I manage enabling/disabling source routing in FreeBSD? 
-- 
Malinin A. G.
  --------------A4F75ADA9A8A4B6D79335FF6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 23 23:48:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03056 for freebsd-hackers-outgoing; Sun, 23 Aug 1998 23:48:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03007 for ; Sun, 23 Aug 1998 23:47:57 -0700 (PDT) (envelope-from haskin@ptway.com) Received: from brianjr (204R1.infinitecom.com [199.176.148.71] (may be forged)) by apollo.ptway.com (8.8.7/8.8.7) with SMTP id BAA03411; Mon, 24 Aug 1998 01:50:30 -0400 Message-ID: <002801bdcf2b$06858940$0b00000a@brianjr.haskin.org> From: "Brian Haskin" To: "Brian Beattie" Cc: Subject: Re: I want to break binary compatibility. Date: Mon, 24 Aug 1998 02:46:42 -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 -----Original Message----- From: Brian Beattie To: Mikael Karpberg Cc: B. Richardson ; hackers@FreeBSD.ORG Date: Sunday, August 23, 1998 9:16 PM Subject: Re: I want to break binary compatibility. >This approach will no no good, if the hackesr can down load a binary, >because they see what has been done. I thought scrambling the syscall >table was good but it also falls to the dowloaded binaty, although it is a >lot harder to decipher. I was thinking you could encrypt all your >binariaes and use a scheme like the compressed executables. unfortubately >this would fall prey to the know plaintext attack. > umm, any decent modern block cipher can withstand a plaintext attack. That being said it really doesn't provide you with much more protection than simply chmoding your executables to execute only, no read access. Because you have to keep the key somewhere on the system and if they can get around not having read access on the executable they can probably read where ever it is you have the key stored. It would also add quite a bit of overhead when opening a program. Brian Haskin haskin@ptway.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 24 01:14:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15383 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 01:14:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15361 for ; Mon, 24 Aug 1998 01:14:16 -0700 (PDT) (envelope-from kim@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma009702; Mon Aug 24 03:10:09 1998 Received: by localhost (8.8.5/8.8.5) id DAA26767; Mon, 24 Aug 1998 03:13:22 -0500 (CDT) Message-ID: <35E11FDF.68B0DA15@tinker.com> Date: Mon, 24 Aug 1998 03:10:07 -0500 From: Kim Shrier Organization: Shrier and Deihl X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: MAG CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about source routing References: <35E10B25.F8C4C53F@magc.cd.2573.savbank.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MAG wrote: > > Who can help me: can I manage enabling/disabling source routing in > FreeBSD? > > -- > Malinin A. G. > > You can use sysctl to set the value of net.inet.ip.sourceroute. 0 disables source routing, 1 enables it. Kim Shrier kim@tinker.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 24 08:45:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14443 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 08:45:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14408 for ; Mon, 24 Aug 1998 08:45:41 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA24413; Mon, 24 Aug 1998 11:44:30 -0400 (EDT) Date: Mon, 24 Aug 1998 11:44:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: David Kirchner cc: "B. Richardson" , hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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 Or, alternatively, just a file system flag "approved" that indicates a binary has been approved for execution by the system operator. This would be default set on installed binaries, but could only be added by uid 0 (or gid 0 or something). However, this runs into the problem of shared libraries -- as long as LD_LIBRARY_PATH exists, the possibility of running user-specified code also exists. This also doesn't help you if the bugs are in existing code (that is, in sperl :). On Sun, 23 Aug 1998, David Kirchner wrote: > > On Fri, 21 Aug 1998, B. Richardson wrote: > > > What I want to do, if possible is build a uniq system such that binaries > > from other systems will not run on it and vice versa. Is this possible? > > I haven't seen this mentioned yet: > > Would it be possible to hack the kernel so binaries will only be run if > they have a certain "binary signature", one that is different for every > machine. You'd want to do all compilation on another, possibly > non-networked box, and then install all binaries mode '111' (or 4111 or > whatever) so nobody could read the "signature". Maybe this is how the > whole magic number thing works... I was thinking more along the lines of a > 'phrase'. > > Maybe a make world option in /usr/share/mk or something? > > -dpk > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 10:19:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00609 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 10:19:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hoth.ffwd.bc.ca ([209.153.243.242]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA00604 for ; Mon, 24 Aug 1998 10:18:59 -0700 (PDT) (envelope-from skye@ffwd.bc.ca) Received: from skye by hoth.ffwd.bc.ca with local (Exim 1.82 #3) id 0zB0FJ-00060Y-00; Mon, 24 Aug 1998 10:17:33 -0700 Message-ID: <19980824101733.35426@ffwd.bc.ca> Date: Mon, 24 Aug 1998 10:17:33 -0700 From: Skye Poier To: freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions References: <19980820172445.54455@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: <19980820172445.54455@ffwd.bc.ca>; from Skye Poier on Thu, Aug 20, 1998 at 05:24:45PM -0700 X-URL: http://www.ffwd.bc.ca/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No responses - did I subscribe to the right list to get an answer to this question? would freebsd-users be a better choice? Thanks, Skye Word on the street is that Skye Poier said: > Hello, > > I am running 2.2.6-RELEASE on a 486 with 16mb of memory and a 65mb swap > partition. > > Recently I've been working with some rather large files and the machine > has had a tendancy to lock up solid. No error on the console, in dmesg, > nothing. It seems to happen when VM (via swapinfo) reaches 30% usage or > about 19MB of the 65MB avaiable.... other than this the server has been > totally bulletproof. > > Any clues? I'm getting more memory soon but it probably still won't be > enough, I want to use all my swap space! > > Thanks, > Skye > > > 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 24 11:41:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14304 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 11:41:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.netsol.net (mail.netsol.net [38.216.109.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14296 for ; Mon, 24 Aug 1998 11:41:14 -0700 (PDT) (envelope-from matthew@netsol.net) Received: from Matt.pandaamerica.com ([198.186.216.114]) by mail1.netsol.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42781U2500L250S0) with SMTP id AAA185 for ; Mon, 24 Aug 1998 11:43:36 -0700 Message-ID: <007101bdcf8e$8da2bc00$f0a8a8c0@Matt.pandaamerica.com> From: matthew@netsol.net (netsol,matthew) To: Subject: Netware? Date: Mon, 24 Aug 1998 11:39:39 -0700 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone start to make FBSD working with Novell yet? Is their a project on this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 12:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23589 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 12:29:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from m1.cybersurf.com (m1.cybersurf.com [205.160.242.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23567 for ; Mon, 24 Aug 1998 12:29:06 -0700 (PDT) (envelope-from davism@cybersurf.com) Received: from m1.cybersurf.com (m1.cybersurf.com [205.160.242.195]) by m1.cybersurf.com (8.8.8/8.8.7) with SMTP id PAA25368; Mon, 24 Aug 1998 15:28:10 -0400 (EDT) Date: Mon, 24 Aug 1998 15:28:10 -0400 (EDT) From: Mark Davis To: "netsol,matthew" cc: hackers@FreeBSD.ORG Subject: Re: Netware? In-Reply-To: <007101bdcf8e$8da2bc00$f0a8a8c0@Matt.pandaamerica.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, 24 Aug 1998, netsol,matthew wrote: > Has anyone start to make FBSD working with Novell yet? Is their a project on > this? It is a commercial solution, but check out www.netcon.com ... Been playing with this for a while as a way to replace or supplement our existing NW3.12 server. Looks like the best bet is going to be a combination of the two... Note:this is a bindery not NDS emulation, but it can also emulate a NT server as well... http://www.xtalwind.net Mark Davis http://www.cybersurf.com davism@xtalwind.net davism@cybersurf.com http://www.buy-mouse.com Systems Administrator/Hardware Specialist http://www.cybersurf.com/cafe Crystal Wind Communications, Inc. http://www.mudworld.com The CyberSurf C@fe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 13:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28841 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 13:14:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (kenya-155.ppp.hooked.net [206.169.227.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28834 for ; Mon, 24 Aug 1998 13:14:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id NAA12703; Mon, 24 Aug 1998 13:14:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 24 Aug 1998 13:14:47 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Robert Watson cc: David Kirchner , "B. Richardson" , hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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, 24 Aug 1998, Robert Watson wrote: > > Or, alternatively, just a file system flag "approved" that indicates a > binary has been approved for execution by the system operator. This would > be default set on installed binaries, but could only be added by uid 0 (or > gid 0 or something). > > However, this runs into the problem of shared libraries -- as long as > LD_LIBRARY_PATH exists, the possibility of running user-specified code > also exists. This also doesn't help you if the bugs are in existing code > (that is, in sperl :). Yes, but one could easily hardcode LD_LIBRARY_PATH to search /usr/lib or whatever first. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 13:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00631 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 13:23:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from notreal.com (afraid.of.scientol.ogy.org [206.86.192.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00618 for ; Mon, 24 Aug 1998 13:23:51 -0700 (PDT) (envelope-from dpk@notreal.com) Received: from localhost (dpk@localhost) by notreal.com (8.9.1/8.9.1) with SMTP id NAA24312; Mon, 24 Aug 1998 13:22:55 -0700 (PDT) (envelope-from dpk@notreal.com) Date: Mon, 24 Aug 1998 13:22:55 -0700 (PDT) From: David Kirchner To: Alex cc: Robert Watson , "B. Richardson" , hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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, 24 Aug 1998, Alex wrote: > On Mon, 24 Aug 1998, Robert Watson wrote: > > > > > Or, alternatively, just a file system flag "approved" that indicates a > > binary has been approved for execution by the system operator. This would > > be default set on installed binaries, but could only be added by uid 0 (or > > gid 0 or something). Maybe create a utility that can "bless" binaries. 'root' would only be able to execute blessed binaries. setuid binaries could on be run if blessed, etc. Same idea, but the flag could be set on a different server before the file is copied over. > > However, this runs into the problem of shared libraries -- as long as > > LD_LIBRARY_PATH exists, the possibility of running user-specified code > > also exists. This also doesn't help you if the bugs are in existing code > > (that is, in sperl :). The truly paranoid could just compile everything run as root staticly. > Yes, but one could easily hardcode LD_LIBRARY_PATH to search /usr/lib or > whatever first. > > - alex Or for the less paranoid, they could do this. :) -dpk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 13:45:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04631 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 13:45:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA04598 for ; Mon, 24 Aug 1998 13:44:53 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 21423 invoked by uid 1003); 24 Aug 1998 20:43:14 -0000 Message-ID: <19980824224314.A21017@rucus.ru.ac.za> Date: Mon, 24 Aug 1998 22:43:14 +0200 From: Neil Blakey-Milner To: Skye Poier , freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions References: <19980820172445.54455@ffwd.bc.ca> <19980824101733.35426@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19980824101733.35426@ffwd.bc.ca>; from Skye Poier on Mon, Aug 24, 1998 at 10:17:33AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1998-08-24 (10:17), Skye Poier wrote: > No responses - did I subscribe to the right list to get an answer to > this question? would freebsd-users be a better choice? It's a question... if you don't know where else to ask it, this is the place. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 14:12:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07250 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 14:12:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07242 for ; Mon, 24 Aug 1998 14:12:52 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id RAA25669; Mon, 24 Aug 1998 17:11:55 -0400 (EDT) Date: Mon, 24 Aug 1998 17:11:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: David Kirchner cc: Alex , "B. Richardson" , hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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, 24 Aug 1998, David Kirchner wrote: > Maybe create a utility that can "bless" binaries. 'root' would only be > able to execute blessed binaries. setuid binaries could on be run if > blessed, etc. Same idea, but the flag could be set on a different server > before the file is copied over. i.e., a file system flag, or table that the kernel loads from disk. This sounds pretty straight-forward. > > > However, this runs into the problem of shared libraries -- as long as > > > LD_LIBRARY_PATH exists, the possibility of running user-specified code > > > also exists. This also doesn't help you if the bugs are in existing code > > > (that is, in sperl :). > > The truly paranoid could just compile everything run as root staticly. > > > Yes, but one could easily hardcode LD_LIBRARY_PATH to search /usr/lib or > > whatever first. > > > > - alex > > Or for the less paranoid, they could do this. :) My favored choice would be to modify the standard dynamic link support to check /etc/ld.conf (or a sysctl) to determine whether the system policy currently allowed dynamic linking or not, and if so, whether user-defined paths were allowed. This, in combination with the bless-support would work pretty well. Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 14:13:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07341 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 14:13:50 -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 OAA07332 for ; Mon, 24 Aug 1998 14:13:37 -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 XAA21756; Mon, 24 Aug 1998 23:09:16 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id XAA05288; Mon, 24 Aug 1998 23:04:57 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808242104.XAA05288@semyam.dinoco.de> To: Andy Farkas Subject: Re: TMC-950 scsi card In-reply-to: Your message of "Fri, 21 Aug 1998 12:07:16 +1000." <35DCD654.4B865F4C@speednet.com.au> Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Mon, 24 Aug 1998 23:04:56 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason I asked which driver went with the card in the first place > was because it is listed as a supported adapter in section 2.1.1 of the > Handbook. My -current system has a man page mentioning such a device and there is a source file under src/sys for it. I think it is a safe bet to say it is in -stable, too. ;-) Look at sea(4). I found it with "apropos Future". 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 24 14:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11552 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 14:43:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts03-104.dublin.indigo.ie [194.125.148.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11529 for ; Mon, 24 Aug 1998 14:43:31 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA00657; Mon, 24 Aug 1998 22:36:25 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808242136.WAA00657@indigo.ie> Date: Mon, 24 Aug 1998 22:36:24 +0000 In-Reply-To: <199808240620.BAA04415@dyson.iquest.net>; "John S. Dyson" 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: dyson@iquest.net, joelh@gnu.org Subject: Re: I want to break binary compatibility. Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 24, 1:20am, "John S. Dyson" wrote: } Subject: Re: I want to break binary compatibility. > Joel Ray Holveck said: > > >>> I have a problem with some hackers that are obsessed with making my > > >>> ISP's life miserable (they've already hacked our SGI). I've slapped > > >>> together a FreeBSD box to throw their webpages on it, turned off all > > >>> services except http. > > >> While you are at it and breaking binary compatibility for security > > >> reasons, make sure you remove stuff a webserver doesn't need such as > > >> /usr/include, compilers, manpages, etc. Maybe PicoBSD would be the > > >> place to start? [snip] > I posted this through another mechanism by mistake, and so I apologize > if this message is a repeat for you: > > Try modifying your system so that one of the flags bits is required to > run a program. It would the require both the flags bit and the executable > bit. Make sure the system cannot allow anyone but root set the chosen > flags bit. Maybe you could use the immutable flag, for this so that you > get theoretical immutability along with the ability to run code. You > might want to relax the restriction for root, but maybe not (depending > on how your admin scheme is setup.) None of these hacks achieve security. You, of all people, should know better. The original poster should figure out how they are breaking in and close the hole, obfuscation schemes like the above are a waste of time. 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 Mon Aug 24 14:57:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13073 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 14:57:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lituussun (irc.ladapt.org [195.25.51.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA13067 for ; Mon, 24 Aug 1998 14:56:59 -0700 (PDT) (envelope-from stephane@lituus.fr) Received: from (sequoia.lituus.fr) [193.252.177.13] by lituussun with esmtp (Exim 1.82 #1) id 0zB5Si-0004mu-00; Mon, 24 Aug 1998 23:51:45 +0100 Received: (from root@localhost) by sequoia.lituus.fr (8.9.1/8.9.1) id XAA03162; Mon, 24 Aug 1998 23:55:48 +0200 (CEST) (envelope-from root) Date: Mon, 24 Aug 1998 23:55:48 +0200 (CEST) Message-Id: <199808242155.XAA03162@sequoia.lituus.fr> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. In-Reply-To: References: X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kirchner writes: > > On Fri, 21 Aug 1998, B. Richardson wrote: > > > What I want to do, if possible is build a uniq system such that binaries > > from other systems will not run on it and vice versa. Is this possible? > > I haven't seen this mentioned yet: > > Would it be possible to hack the kernel so binaries will only be run if > they have a certain "binary signature", one that is different for every > machine. You'd want to do all compilation on another, possibly > non-networked box, and then install all binaries mode '111' (or 4111 or > whatever) so nobody could read the "signature". Maybe this is how the > whole magic number thing works... I was thinking more along the lines of a > 'phrase'. > > Maybe a make world option in /usr/share/mk or something? > There is a similar project on Linux : http://pobox.upenn.edu/~tex/papers/thesis/index.html -- stephane@lituus.fr | systeme d'exploitation FreeBSD http://195.25.51.6/stephane/ | 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 24 15:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15875 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 15:21:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-db.dialup.hilink.com.au [203.2.144.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15870 for ; Mon, 24 Aug 1998 15:21:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00654; Mon, 24 Aug 1998 15:18:36 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808241518.PAA00654@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Skye Poier cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions In-reply-to: Your message of "Mon, 24 Aug 1998 10:17:33 MST." <19980824101733.35426@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 15:18:35 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No responses - did I subscribe to the right list to get an answer to > this question? would freebsd-users be a better choice? 12 hours is not long enough for a reply to a casual report of this nature. You're reporting an unknown problem with an old version of the system on potentially faulty hardware, and not offering any clue as to what might have happened or any assistance in locating the problem. What reply is there that would be of any use? > Word on the street is that Skye Poier said: > > Hello, > > > > I am running 2.2.6-RELEASE on a 486 with 16mb of memory and a 65mb swap > > partition. > > > > Recently I've been working with some rather large files and the machine > > has had a tendancy to lock up solid. No error on the console, in dmesg, > > nothing. It seems to happen when VM (via swapinfo) reaches 30% usage or > > about 19MB of the 65MB avaiable.... other than this the server has been > > totally bulletproof. > > > > Any clues? I'm getting more memory soon but it probably still won't be > > enough, I want to use all my swap space! > > > > Thanks, > > Skye > > > > > > 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 > -- \\ 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 24 16:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21898 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 16:05:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.netsol.net (mail.netsol.net [38.216.109.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21889 for ; Mon, 24 Aug 1998 16:05:05 -0700 (PDT) (envelope-from matthew@netsol.net) Received: from Matt.pandaamerica.com ([198.186.216.114]) by mail1.netsol.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42781U2500L250S0) with SMTP id AAA199 for ; Mon, 24 Aug 1998 16:08:21 -0700 Message-ID: <00cb01bdcfb3$8aeb1640$f0a8a8c0@Matt.pandaamerica.com> From: matthew@netsol.net (netsol,matthew) To: Subject: Imap4 Date: Mon, 24 Aug 1998 16:04:24 -0700 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone tell me what imap4 is? i found it in 2.2.7 inetd.conf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 16:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21932 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 16:05:16 -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 QAA21911 for ; Mon, 24 Aug 1998 16:05:11 -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 QAA01156; Mon, 24 Aug 1998 16:03:53 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808242303.QAA01156@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Sun, 23 Aug 1998 10:32:37 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 16:03:53 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Chuck, Just take a look at my bt848 driver and since the documentation for the chipset is freely available it makes the job a lot easier to understand the driver. With respect to the sound driver you are a lot better off asking in -multimedia and specially Luigi for information on how to interface to his snd driver. From a high level point what you need to know is how to initiate dma to and and from the card and this is usually card or chipset specific in other words the chipset for your sound card should have documentation on how to initiate a dma transfer. And of course the documentation should also state the rest of the usual glue logic on how to set input / output rate, audio format , etc.. For now there are enough low level hardware hackers in -multimedia which should be able to help you. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 17:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04094 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 17:37:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04088 for ; Mon, 24 Aug 1998 17:37:41 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA25410 for freebsd-hackers@FreeBSD.ORG; Tue, 25 Aug 1998 02:36:53 +0200 (CEST) (envelope-from olli) Date: Tue, 25 Aug 1998 02:36:53 +0200 (CEST) From: Oliver Fromme Message-Id: <199808250036.CAA25410@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: sound card programming Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote in list.freebsd-hackers: > i'm pretty sure you can do both via reading/writing from /dev/dsp* > > if you need to do something, i suggest you grab an audio utility from the > ports collection and look at its source code. /usr/ports/audio/tosha contains a very small utility called pcmplay which just plays audio files on the soundcard. The source should be fairly easy to understand. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 18:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07450 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 18:09:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hunter.softcon.de (hunter.softcon.de [193.31.11.194]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA07444 for ; Mon, 24 Aug 1998 18:09:00 -0700 (PDT) (envelope-from Matthias.Apitz@Sisis.de) From: Matthias.Apitz@Sisis.de Received: (from mail@localhost) by hunter.softcon.de (8.6.9/8.6.12) id DAA14194 for ; Tue, 25 Aug 1998 03:10:39 +0200 Received: from boell.softcon.de(193.31.10.71) by hunter.softcon.de via smap (V1.3) id sma014192; Tue Aug 25 03:10:21 1998 Received: from kant.SOFTCON.de (kant.SOFTCON.de [193.31.10.39]) by boell.SOFTCON.de (8.7.5/8.7.3) with SMTP id BAA29390 for ; Tue, 25 Aug 1998 01:04:57 GMT Date: Tue, 25 Aug 98 01:12 GMT To: freebsd-hackers@FreeBSD.ORG@Sisis.de Message-ID: <9808250112.AA06084@kant.SOFTCON.de> Subject: AUTOANSWERED!!! Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm away from Friday, August 28 to Monday, September 14. I will read (and answer if necessary) your e-mail message when I return. If you have something urgent, please contact Juergen Bajdala . This message was generated automatically and you will receive it only once, although all the messages you send me while I am away WILL be saved. matthias -- firm: matthias.apitz@sisis.de [voc:+49-89-61308-351, fax: +49-89-61308-188] priv: guru@thias.muc.de PGP: Key fingerprint = 0C 01 F2 23 EC 17 A2 D5 46 2D 29 4C 0E 8B 7E 8F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 24 21:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28380 for freebsd-hackers-outgoing; Mon, 24 Aug 1998 21:27:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28371 for ; Mon, 24 Aug 1998 21:26:56 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id XAA14269; Mon, 24 Aug 1998 23:24:17 -0400 (EDT) Date: Mon, 24 Aug 1998 23:24:17 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Amancio Hasty cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI devices In-Reply-To: <199808242303.QAA01156@rah.star-gate.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, 24 Aug 1998, Amancio Hasty wrote: > Hi Chuck, > > Just take a look at my bt848 driver and since the documentation for > the chipset is freely available it makes the job a lot easier to > understand the driver. With respect to the sound driver you are > a lot better off asking in -multimedia and specially Luigi for > information on how to interface to his snd driver. From a high > level point what you need to know is how to initiate > dma to and and from the card and this is usually card or chipset > specific in other words the chipset for your sound card should have > documentation on how to initiate a dma transfer. And of course > the documentation should also state the rest of the usual glue logic on > how to set input / output rate, audio format , etc.. > > For now there are enough low level hardware hackers in -multimedia which > should be able to help you. Thanks. I've gotten a lot of information in the last few days, I'm going to go back to lurker mode while I read and figure all this out. > > > Cheers, > Amancio > > > > ----------------------------+----------------------------------------------- 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 25 00:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13606 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 00:31:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from colin.muc.de (colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA13582 for ; Tue, 25 Aug 1998 00:30:53 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140570-1>; Tue, 25 Aug 1998 08:11:36 +0200 Received: (from daemon@localhost) by tavari.muc.de (8.8.8/8.8.7) id HAA05964; Tue, 25 Aug 1998 07:54:59 +0200 (CEST) Received: from ripley(192.168.42.202) by morranon via smap (V2.1) id xma005962; Tue, 25 Aug 98 07:54:47 +0200 From: "Lutz Albers" To: "netsol,matthew" , Subject: RE: Imap4 Date: Tue, 25 Aug 1998 07:54:36 +0200 Message-ID: <000201bdcfec$d73295d0$ca2aa8c0@ripley.tavari.muc.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <00cb01bdcfb3$8aeb1640$f0a8a8c0@Matt.pandaamerica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyone tell me what imap4 is? i found it in 2.2.7 inetd.conf. Internet Mail Access Protocol (version 4). It's a way to access your mail stored on a remote server (and keep it there). There are two free implementations, imap-uw and Cyrus IMAP. More info's can be found under http://www.imap.org hope this helps lutz -- Lutz Albers, lutz@muc.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 00:52:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16240 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 00:52: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 AAA16227 for ; Tue, 25 Aug 1998 00:52:23 -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 JAA11173; Tue, 25 Aug 1998 09:51:29 +0200 (MET DST) Date: Tue, 25 Aug 1998 09:51:27 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: matthew@netsol.net cc: FreeBSD hackers mailing list Subject: Re: Imap4 In-Reply-To: <00cb01bdcfb3$8aeb1640$f0a8a8c0@Matt.pandaamerica.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 > Can anyone tell me what imap4 is? i found it in 2.2.7 inetd.conf. Mail server. It is built around the idea that you do not pull down all the mail to your system but keep it on the mail server. In that way you can read mail from several locations without logging in to various machines. It is also built with slow links in mind. So an IMAP connection is very useable on a 28k8 modem if you decide to just quickly browse the subjects. Sorting and deleting is all done on the server not on the client. 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 25 04:26:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14950 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 04:26:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14945 for ; Tue, 25 Aug 1998 04:26:54 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id NAA04364 for hackers@freebsd.org; Tue, 25 Aug 1998 13:26:06 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id GAA01897 for hackers@freebsd.org; Tue, 25 Aug 1998 06:58:24 +0200 (MET DST) (envelope-from wosch) Message-ID: <19980825065823.A1824@panke.de> Date: Tue, 25 Aug 1998 06:58:23 +0200 From: Wolfram Schneider To: hackers@FreeBSD.ORG Subject: undump utility Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to write an undump uitility for FreeBSD. It sometimes works for the emacs, but in most cases it core'd immediately. I don't know why. Any hints? Wolfram # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # undump # undump/Makefile # undump/undump.c # echo c - undump mkdir -p undump > /dev/null 2>&1 echo x - undump/Makefile sed 's/^X//' >undump/Makefile << 'END-of-undump/Makefile' XPROG= undump XNOMAN= XCLEANFILES+= sh.core sh.undump sh.undump.core X Xdump: X -/bin/sh -c 'kill -6 $$$$' X Xtest: dump X ./${PROG} -d sh.undump /bin/sh sh.core X wc -c sh.undump /bin/sh X size sh.undump /bin/sh X ./sh.undump X X.include X END-of-undump/Makefile echo x - undump/undump.c sed 's/^X//' >undump/undump.c << 'END-of-undump/undump.c' X/*- X * Copyright (c) Aug 1998 Wolfram Schneider , Berlin. X * All rights reserved. X * X * Redistribution and use in source and binary forms, with or without X * modification, are permitted provided that the following conditions X * are met: X * 1. Redistributions of source code must retain the above copyright X * notice, this list of conditions and the following disclaimer. X * 2. Redistributions in binary form must reproduce the above copyright X * notice, this list of conditions and the following disclaimer in the X * documentation and/or other materials provided with the distribution. X * X * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND X * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE X * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE X * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE X * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL X * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS X * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) X * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT X * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY X * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF X * SUCH DAMAGE. X * X * $Id$ X */ X X/* X * Convert a core dump to an executable binary. See perl -u X * X */ X X#include X#include X X/* core dump */ X#include X#include X X#include X#include X#include X#include X#include X#include X X#include X#include X Xextern char *optarg; Xextern int optind; X Xint check_corefile_from_oldfile(char *oldp, char *corep); Xint copy_text_from_oldfile_to_newfile(char *oldp, int newfd); Xint copy_data_from_corefile_to_newfile(char *corep, int newfd); Xint copy_symbol_from_oldfile_to_newfile(char *oldpp, int newfd, int len); Xint set_exec_header(int newfd); Xvoid usage(); X X Xint debug; X Xstatic struct exec oldhdr; /* exec header from old binary file */ Xstatic struct exec newhdr; /* exec header for the new file */ Xstatic struct user coreuser; /* text, data, and stack size from core dump */ X X Xmain(int argc, char **argv) X{ X int c, oldfilelen; X struct stat sb; X X char *newfile, *oldfile, *corefile; X int newfd, oldfd, corefd; X char *oldp, *corep; X X while((c = getopt(argc, argv, "d")) != -1) { X switch(c) { X case 'd': X debug++; X break; X X default: X usage; X exit(1); X } X } X argc -= optind; X argv += optind; X X /* usage: undump newfile oldfile corefile */ X if (argc < 3) { X fprintf(stderr, "Too few arguments\n"); X usage(); X exit(1); X } X X newfile = argv[0]; X oldfile = argv[1]; X corefile = argv[2]; X X if ((newfd = open(newfile, O_CREAT | O_WRONLY, 0666)) == -1) X err(1, "corefile: %s", corefile); X X if ((oldfd = open(oldfile, O_RDONLY, 0)) == -1) X err(1, "Open oldfile: %s", oldfile); X if (stat(oldfile, &sb) == -1) X err(1, "Stat oldfile: %s", oldfile); X if ((oldp = (char *)mmap((caddr_t)0, sb.st_size, PROT_READ, X MAP_SHARED, oldfd, (off_t)0)) == MAP_FAILED) X err(1, "mmap oldfile: %s", oldfile); X oldfilelen = sb.st_size; X X if ((corefd = open(corefile, O_RDONLY, 0)) == -1) X err(1, "corefile: %s", corefile); X if (stat(corefile, &sb) == -1) X err(1, "Stat corefile: %s", corefile); X if ((corep = (char *)mmap((caddr_t)0, sb.st_size, PROT_READ, X MAP_SHARED, corefd, (off_t)0)) == MAP_FAILED) X err(1, "mmap corefile: %s", corefile); X X X X /* read exec header from old binary */ X oldhdr = newhdr = *(struct exec *) oldp; X X /* read text, data, and stack size from core dump */ X coreuser = *(struct user *) corep; X X X if (check_corefile_from_oldfile(oldp, corep)) { X fprintf(stderr, "Coredump %s was not generated from %s!\n", X corefile, oldfile); X exit(2); X } X X copy_text_from_oldfile_to_newfile(oldp, newfd); X copy_data_from_corefile_to_newfile(corep, newfd); X copy_symbol_from_oldfile_to_newfile(oldp, newfd, oldfilelen); X set_exec_header(newfd); X X if (fchmod(newfd, 0755) == -1) X err(1, "set mode of new file: %s\n", newfile); X if (close(newfd) == -1) X err(1, "closing newfile: %s\n", newfile); X close(oldfd); X close(corefd); X X} X Xvoid usage () X{ X fprintf(stderr, "usage: undump [-d] newfile oldfile corefile\n"); X} X X X/* X * check if the corefile was X * created from the oldfile X */ Xint check_corefile_from_oldfile(char *oldp, char *corep) X{ X if (debug) { X printf("Old binary file: "); X printf("a_text: %u, a_data: %u, a_bss: %u, a_syms: %u\n", X oldhdr.a_text, oldhdr.a_data, oldhdr.a_bss, X oldhdr.a_syms); X printf("\t\t a_entry: %u, a_trsize: %u, a_drsize: %u\n", X oldhdr.a_entry, oldhdr.a_trsize, oldhdr.a_drsize); X X printf("Core dump file: "); X printf("u_tsize: %u, u_dsize: %u, u_ssize: %u\n", X ptoa(coreuser.u_tsize), X ptoa(coreuser.u_dsize), X ptoa(coreuser.u_ssize)); X } X X if (oldhdr.a_text != ptoa(coreuser.u_tsize)) { X return(1); X } X X return (0); X} X X X/* X * Copy text sgement from old file X * to new file. X */ Xint copy_text_from_oldfile_to_newfile(char *oldp, int newfd) X{ X if (debug) { X printf("Old binary file: N_TXTOFF: %u, N_TXTADDR: %u, " X "a_text: %u\n", X N_TXTOFF(oldhdr), N_TXTADDR(oldhdr), oldhdr.a_text); X } X X if (lseek(newfd, (off_t)N_TXTOFF(newhdr), SEEK_SET) == -1) X err(1, NULL); X if (write(newfd, oldp + N_TXTOFF(oldhdr), oldhdr.a_text) == -1) X err(1, NULL); X X return(0); X}; X X/* X * Copy data from coredump file X * into the data segement of the new file. X */ X Xint copy_data_from_corefile_to_newfile(char *corep, int newfd) X{ X if (debug) { X printf("Copy %u bytes from coredump data to new file\n", X ptoa(coreuser.u_dsize)); X X printf("Old binary file: N_DATOFF: %u, N_DATADDR: %u, " X "a_data: %u\n", X N_DATOFF(newhdr), N_DATADDR(newhdr), newhdr.a_data); X X } X X if (lseek(newfd, (off_t)N_DATOFF(newhdr), SEEK_SET) == -1) X err(1, NULL); X X if (write(newfd, corep + ptoa(UPAGES), ptoa(coreuser.u_dsize)) == -1) X err(1, NULL); X X return(0); X}; X X/* X * Copy text relocations and the rest (data relocations, symbol table X * string table) at end of the new file. X */ X Xint copy_symbol_from_oldfile_to_newfile( X char *oldp, int newfd, int oldfilelen) X{ X if (debug) { X printf("Copy %u bytes rel + sym from old file to new file\n", X oldfilelen - N_RELOFF(oldhdr)); X printf("N_RELOFF: %u\n", N_RELOFF(oldhdr)); X } X X if (lseek(newfd, (off_t)N_RELOFF(oldhdr), SEEK_SET) == -1) X err(1, NULL); X X if (write(newfd, oldp + N_RELOFF(oldhdr), X oldfilelen - N_RELOFF(oldhdr)) == -1) X err(1, NULL); X X return(0); X}; X X X X X/* X * Set the exec header values of the X * new file X */ Xint set_exec_header(int newfd) X{ X /* set data segment size */ X newhdr.a_data = ptoa(coreuser.u_dsize); X X /* the bss segment is now in the data of the new file */ X newhdr.a_bss = 0; X X X if (debug) { X printf("New binary file: "); X printf("a_text: %u, a_data: %u, a_bss: %u, a_syms: %u\n", X newhdr.a_text, newhdr.a_data, newhdr.a_bss, X newhdr.a_syms); X printf("\t\t a_entry: %u, a_trsize: %u, a_drsize: %u\n", X newhdr.a_entry, newhdr.a_trsize, newhdr.a_drsize); X } X X /* write the exec header at the beginning of the new file */ X if (lseek(newfd, (off_t)0, SEEK_SET) == -1) X err(1, NULL); X X if (write(newfd, &newhdr, sizeof(newhdr)) == -1) X err(1, NULL); X X return(0); X}; X END-of-undump/undump.c exit -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 06:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24804 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 06:10:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from metronet.com (fohnix.metronet.com [192.245.137.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA24796 for ; Tue, 25 Aug 1998 06:10:33 -0700 (PDT) (envelope-from pgilley@metronet.com) Received: from localhost by metronet.com with SMTP id AA24512 (5.67a/IDA1.5hp for ); Tue, 25 Aug 1998 08:10:38 -0500 Date: Tue, 25 Aug 1998 08:10:38 -0500 (CDT) From: Phil Gilley To: hackers@FreeBSD.ORG Subject: Re: What options for BW quickcam on 2.2.7 ? In-Reply-To: <199808230527.HAA00162@labinfo.iet.unipi.it> 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, 23 Aug 1998, Luigi Rizzo wrote: > whoops... sorry i did not mean that qcread did not work, just wondered > if there was some other more featured package including a live viewer > or vic support. From what i have read i ghess one can import most > things from qcam... As I've already responded to Luigi in private email, I have ports and packages for qcam-0.3 and xfqcam-1.05 that I've been maintaining privately for some time. Since others may want a copy I have made them available on my Web page: http://www.metronet.com/~pgilley/freebsd/qcam Phil Gilley pgilley@metronet.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 25 06:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29185 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 06:44:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29176 for ; Tue, 25 Aug 1998 06:44:29 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA29193; Tue, 25 Aug 1998 13:43:29 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA26498; Tue, 25 Aug 1998 15:43:20 +0200 (MET DST) Message-ID: <19980825154320.29030@follo.net> Date: Tue, 25 Aug 1998 15:43:20 +0200 From: Eivind Eklund To: rotel@indigo.ie, dyson@iquest.net, joelh@gnu.org Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. References: <199808240620.BAA04415@dyson.iquest.net> <199808242136.WAA00657@indigo.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808242136.WAA00657@indigo.ie>; from Niall Smart on Mon, Aug 24, 1998 at 10:36:24PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 24, 1998 at 10:36:24PM +0000, Niall Smart wrote: > On Aug 24, 1:20am, "John S. Dyson" wrote: > > Try modifying your system so that one of the flags bits is required to > > run a program. It would the require both the flags bit and the executable > > bit. Make sure the system cannot allow anyone but root set the chosen > > flags bit. Maybe you could use the immutable flag, for this so that you > > get theoretical immutability along with the ability to run code. You > > might want to relax the restriction for root, but maybe not (depending > > on how your admin scheme is setup.) > > None of these hacks achieve security. You, of all people, should > know better. The original poster should figure out how they are > breaking in and close the hole, obfuscation schemes like the above > are a waste of time. As I see it, this is not an obfuscation scheme - it is a security layer blocking anybody but root from creating runnable programs (or, if you are running at a higher secure-level, block anybody from creating runnable programs). The use of mumbled syscalls is basically a form of included password/cryptgraphic key, so it is an obfuscation scheme - just like using passwords is an obfuscation scheme. If there are no readable excutables or header files (and there had better not be), and the syscalls are totally scrambled, you have a password with 241111005450527600328717895291292670443358181333262746781391518619604\ 665145591729660171722514729263966207029657274760829969835101821556548\ 304978870053886400523066523749566624313465787285119981924269527998407\ 383954685993679028640869483407606883707438996687240258706499417535241\ 226013998982887860608092391831248604598572478575586384534131326320640\ 0000000000000000000000000000000000000000000000000 possibilities. 396 digits (1315 bits) is actually a pretty respectable number, and should give you plenty time to detect that the attacker is testing syscalls (even if he does not need to get a perfect match, and even though he can probably find parts of the keys quickly, he will still leave traces. To get him to spend more time, also change some other parts of the calling conventions, like which numbers the different error return codes are assigned). For a generally deployed system, obscurity is not protection. For a single installation, obscurity is protection, and can very often be a valid line of defence. This does not mean one should rely on it, but deploying it can be helpful. If you are on the lookout, the extra 12 hours you get from breakin to the traces are hid can be a lifesaver. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 08:34:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14059 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 08:34:30 -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 IAA14044 for ; Tue, 25 Aug 1998 08:34:24 -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 LAA13014 for ; Tue, 25 Aug 1998 11:33:33 -0400 (EDT) Date: Tue, 25 Aug 1998 11:33:33 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: fs_cs() macro in FFS 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 macro fs_cs() is defind in fs.h as: /* * N.B. This macro assumes that sizeof(struct csum) is a power of two. */ #define fs_cs(fs, indx) \ fs_csp[(indx) >> (fs)->fs_csshift] [(indx) & ~(fs)->fs_csmask] Since fs_csp is defined as an array of pointers to csum structure, I can not see why it is accessed as a two-dimension array (I just write a small C program to test it and find it is legal to do so). I am more confused with the shift/mask the macro uses and why the comment says the size of csum structure should be power of two. BTW, what does N.B. mean? 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 25 08:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17728 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 08:59:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA17719 for ; Tue, 25 Aug 1998 08:59:28 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HQUNWBTJ; Tue, 25 Aug 98 15:58:39 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980825175533.0091e570@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 25 Aug 1998 17:55:33 +0200 To: zhihuizhang From: Marius Bendiksen Subject: Re: fs_cs() macro in FFS Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >not see why it is accessed as a two-dimension array (I just write a small They're accessing a part of the data which is pointed to, not a 2d array. index1 => array \ index2 => => struct >csum structure should be power of two. Because they use the << operator in it, not multiplication. >BTW, what does N.B. mean? Nota Bene. Latin for 'good note', or 'point worth noticing'. I'm not sure about my interpretation of the macro, though. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 09:12:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19155 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 09:12:39 -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 JAA19150 for ; Tue, 25 Aug 1998 09:12:37 -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 MAA14189; Tue, 25 Aug 1998 12:11:39 -0400 (EDT) Date: Tue, 25 Aug 1998 12:11:39 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: Marius Bendiksen cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fs_cs() macro in FFS In-Reply-To: <3.0.5.32.19980825175533.0091e570@mail.scancall.no> 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, 25 Aug 1998, Marius Bendiksen wrote: > >not see why it is accessed as a two-dimension array (I just write a small > > They're accessing a part of the data which is pointed to, not a 2d array. > > index1 => array \ > index2 => => struct > > >csum structure should be power of two. > > Because they use the << operator in it, not multiplication. > Thank for your help. But I am still confused with the macro. The fs_csp is defined as: struct csum *fs_csp[MAXCSBUF == 32]. So index1 should be 0..31, while index2 has no meaning, since each pointer points to only *one* csum structure. If you have char * charpointer[32], that will make more sense (it can be treated as a 2d array). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 09:17:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20208 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 09:17:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA20198 for ; Tue, 25 Aug 1998 09:17:23 -0700 (PDT) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id LAA12842; Tue, 25 Aug 1998 11:15:51 -0500 Message-Id: <3.0.3.32.19980825111549.00718928@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 25 Aug 1998 11:15:49 -0500 To: Bill Paul , chuckr@glue.umd.edu (Chuck Robey) From: Tony Overfield Subject: Re: PCI devices Cc: hackers@FreeBSD.ORG In-Reply-To: <199808231747.NAA18976@skynet.ctr.columbia.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:47 PM 8/23/98 -0400, Bill Paul wrote: > I sometimes see people > on mailing lists or newsgroups complaining that their PCI devices > don't work for some reason, and often someone follows up with > a suggestion to "disable plug & play| support. These people are > confused: PCI devices don't support Plug & Play (tm), so there's > nothing to turn off. The "Plug & Play support" in this case probably refers to the operating system, not to the PCI devices. The BIOS configuration, of some computers, has an option that tells the BIOS which kind of operating system the user has installed. This option tells the BIOS to only configure the PCI adapters that are necessary for booting and to leave the others mostly unconfigured. Microsoft claims their OS can be smarter about configuration than the BIOS can. So it is accurate advice to tell somebody, if their PCI devices aren't working and their OS isn't a Microsoft Plug and Play OS, that they should disable the "Plug & Play Operating System" option in their BIOS setup program. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 11:13:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07374 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:13:15 -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 LAA07369 for ; Tue, 25 Aug 1998 11:13:12 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-111.camalott.com [208.229.74.111]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA31189; Tue, 25 Aug 1998 13:13:54 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA00561; Tue, 25 Aug 1998 13:11:44 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 13:11:44 -0500 (CDT) Message-Id: <199808251811.NAA00561@detlev.UUCP> To: rotel@indigo.ie CC: dyson@iquest.net, imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG In-reply-to: <199808242136.WAA00657@indigo.ie> (message from Niall Smart on Mon, 24 Aug 1998 22:36:24 +0000) Subject: Re: I want to break binary compatibility. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808242136.WAA00657@indigo.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Try modifying your system so that one of the flags bits is required to >> run a program. It would the require both the flags bit and the executable >> bit. Make sure the system cannot allow anyone but root set the chosen >> flags bit. Maybe you could use the immutable flag, for this so that you >> get theoretical immutability along with the ability to run code. You >> might want to relax the restriction for root, but maybe not (depending >> on how your admin scheme is setup.) > None of these hacks achieve security. You, of all people, should > know better. The original poster should figure out how they are > breaking in and close the hole, obfuscation schemes like the above > are a waste of time. Actually, Dyson's idea is the only one I've seen so far that is actual security instead of obfuscation; that is, it is the only suggestion that makes it (theoretically) impossible for an intruder to generate (and run) an arbitrary executable. The others just make the file difficult to generate, and also require things like custom cross-compilers. However, Dyson forgot another modification that must go along with this: ld.so must also be modified to ignore most environment variables. Otherwise, it would be trivial to execute arbitrary bits of code. Something in the back of my mind says that there's still one more hole dealing with mmap, but I can't place it right now. Then again, I'm running on four hours of sleep I got in a truck stop parking lot. 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 Tue Aug 25 11:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09197 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:29:14 -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 LAA09189 for ; Tue, 25 Aug 1998 11:29:12 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-111.camalott.com [208.229.74.111]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA32087; Tue, 25 Aug 1998 13:29:11 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA00645; Tue, 25 Aug 1998 13:27:23 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 13:27:23 -0500 (CDT) Message-Id: <199808251827.NAA00645@detlev.UUCP> To: joelh@gnu.org CC: rotel@indigo.ie, dyson@iquest.net, imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG In-reply-to: <199808251811.NAA00561@detlev.UUCP> (message from Joel Ray Holveck on Tue, 25 Aug 1998 13:11:44 -0500 (CDT)) Subject: Re: I want to break binary compatibility. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808242136.WAA00657@indigo.ie> <199808251811.NAA00561@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Try modifying your system so that one of the flags bits is required to >>> run a program. It would the require both the flags bit and the executable >>> bit. Make sure the system cannot allow anyone but root set the chosen >>> flags bit. Maybe you could use the immutable flag, for this so that you >>> get theoretical immutability along with the ability to run code. You >>> might want to relax the restriction for root, but maybe not (depending >>> on how your admin scheme is setup.) >> None of these hacks achieve security. You, of all people, should >> know better. The original poster should figure out how they are >> breaking in and close the hole, obfuscation schemes like the above >> are a waste of time. > Actually, Dyson's idea is the only one I've seen so far that is actual > security instead of obfuscation; that is, it is the only suggestion > that makes it (theoretically) impossible for an intruder to generate > (and run) an arbitrary executable. The others just make the file > difficult to generate, and also require things like custom > cross-compilers. > However, Dyson forgot another modification that must go along with > this: ld.so must also be modified to ignore most environment > variables. Otherwise, it would be trivial to execute arbitrary bits > of code. > Something in the back of my mind says that there's still one more hole > dealing with mmap, but I can't place it right now. Then again, I'm > running on four hours of sleep I got in a truck stop parking lot. Actually, having said this, I'll have to say that something else is mulling around involving the a race condition similar to suid sh scripts, rtld's loading of libraries, chroot, and my three pet ferrets. I'm not sure how much of that is relevant. But just to be on the safe side, if there are no objections, I would recommend requiring the dyson bit (TM) to be set in order to mmap with PROT_EXEC in any case. 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 Tue Aug 25 11:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10702 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:34:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10696 for ; Tue, 25 Aug 1998 11:34:20 -0700 (PDT) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.8.8/8.7) id DAA02646 for freebsd-hackers@freebsd.org; Wed, 26 Aug 1998 03:59:59 +0930 (CST) From: Mark Newton Message-Id: <199808251829.DAA02646@atdot.dotat.org> Subject: ANNOUNCEMENT: SysVR4 binary compatibility for FreeBSD To: freebsd-hackers@FreeBSD.ORG Date: Wed, 26 Aug 1998 03:59:59 +0930 (CST) 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 am pleased to announce the availability of an ALPHA release of an LKM which implements SysVR4 emulation under FreeBSD. The LKM currently emulates a couple of hundred System-V syscalls, which allows it to run many shell-based utilities from a Solaris 2.5.1 CD-ROM I have on my development machine. Basic SysV network services are emulated to the point where programs like "telnet" and "ftp" work, although X11 clients and programs which use UDP currently fail. The emulator needs some work before it's ready for mainstream, but I believe most of the grunt work has been done. It has been produced mainly by porting the NetBSD COMPAT_SVR4 stuff from a NetBSD-current system I have here. Some parts of it have also been ripped out of the iBCS2 and Linux emulators already contained within FreeBSD. I send sincere thanks to Soren and DavidG for the work they put into those emulators. Special mention must also be made for Christos Zoulas from the NetBSD core team, who is responsible for most of the NetBSD code I "borrowed." As far as I can tell, it does most of the things an appropriately configured NetBSD system does (and, unfortunately, many of the things it doesn't: UDP is broken, as mentioned above). I'm especially interested in co-opting developers who can fill in some of the gaps that the NetBSD folks left as no-ops -- see the README provided with the distribution for more info. I'm currently soliciting developers who are interested in refining it, especially people with knowledge of SysVR4 STREAMS networking (for refining the STREAMS emulation provided by this LKM) and low- level machine context handling (for setcontext() and getcontext() system calls, both of which are currently noops in my emulator). The emulator can be obtained from ftp://slash.dotat.org/pub/freebsd-svr4/. There's a README file there which says what you need and more READMEs in the distribution which say how to install it. If I've left anything out of those, please let me know! The distributions are covered by the Berkeley license, so feel free to distribute far and wide if it takes your fancy. Note that you'll need access to a real SysVR4 machine (Solaris/x86, SCO OpenServer, UnixSwear, whatever) to get the shared libraries if you expect to be able to use this for anything serious. I can't provide that stuff in the distribution for obvious reasons. I've set up a majordomo list for further discussion of the emulator. Send email to majordomo@atdot.dotat.org with the text "subscribe freebsd-svr4" in the BODY of the message to subscribe. If you have any questions, queries or comments, please send them either to me or the mailing list . I especially want to know if I've left anything out of the distributions, or if people simply can't get it to work at all. It's 4:00 in the morning -- I'm going to bed. :-) Regards, - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 11:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13057 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:49:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from server1.scudc.scu.edu (server1.scudc.scu.edu [129.210.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13052 for ; Tue, 25 Aug 1998 11:49:21 -0700 (PDT) (envelope-from dgleeson@scudc.scu.edu) Received: from tuatara.whistle.com (s205m228.whistle.com [207.76.205.228]) by server1.scudc.scu.edu with SMTP (8.7.6/8.7.1) id LAA17689 for ; Tue, 25 Aug 1998 11:48:19 -0700 (PDT) Message-ID: <000501bdd058$974ac0c0$e4cd4ccf@tuatara.whistle.com> From: "David Gleeson, Santa Clara University" To: Subject: subscribe Date: Tue, 25 Aug 1998 11:45:23 -0700 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 11:51:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13273 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:51:55 -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 LAA13265 for ; Tue, 25 Aug 1998 11:51:47 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-92.camalott.com [208.229.74.92]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA00756; Tue, 25 Aug 1998 13:52:39 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA00781; Tue, 25 Aug 1998 13:50:45 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 13:50:45 -0500 (CDT) Message-Id: <199808251850.NAA00781@detlev.UUCP> To: mike@smith.net.au CC: hackers@FreeBSD.ORG In-reply-to: <199808231518.PAA24438@dingo.cdrom.com> (message from Mike Smith on Sun, 23 Aug 1998 15:18:14 +0000) Subject: Re: PCI devices From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808231518.PAA24438@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For clarity's sake and no more, let me point out that "Plug and Play" > is a generic term describing zero-user-intervention configuration. PCI > is implicitly "plug and play" - you can't have a non-PnP PCI card, so > it's more correct to say that PCI devices only support Plug-n-Play so > you can't turn it off. > This confusion is common; many people refer to PnP only in the context > of ISA PnP, but PnP is a generic term applied to ISA PnP, PCI, PCMCIA, > CardBUS, USB, etc. S100 PnP... 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 Tue Aug 25 11:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14363 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 11:59:19 -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 LAA14358 for ; Tue, 25 Aug 1998 11:59:12 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-92.camalott.com [208.229.74.92]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA01219; Tue, 25 Aug 1998 14:00:05 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA00795; Tue, 25 Aug 1998 13:58:19 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 13:58:19 -0500 (CDT) Message-Id: <199808251858.NAA00795@detlev.UUCP> To: dakott@alpha.delta.edu CC: hackers@FreeBSD.ORG In-reply-to: (message from David Kott on Fri, 21 Aug 1998 18:58:57 -0400 (EDT)) Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did have some strange kernel panics when I installed my hardrive > in front of the CDROM that previously had occupied the bus alone. > The drive would log timeout errors. Then, as now, my root > partition/swap et. al was on this drive, the kernel would panic. > Also, sporadically, the drive would load the kernel sucessfully for > booting, but would just hang when the kernel attempted to mount the > root partition. I configured the hardrive to supply the bus > termination, instead of the CDROM, as well as recompiling my kernel > sans the "TUNE_1542" option, and I haven't had a problem since. Many 1542s (particularly the B series) were very sensitive to poor cabling and termination problems. I also made a hack a while back (Jun 97) to allow one to manually (in the kernel config) configure the speed that TUNE_1542 will use ("TUNE_1542=200" etc). This was because in cold weather, on a cold boot (literally), the probe would try to run my 1542 at 150ns, which would reliably hang. After it warmed up a little bit, or after winter passed, it ran at 200ns every time. I posted the patch to -hackers, but didn't get a response. Does anybody have a use for me to add it back in? (I probably will do so anyway next winter.) 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 Tue Aug 25 12:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15274 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 12:06:07 -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 MAA15194; Tue, 25 Aug 1998 12:06:01 -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 MAA18215; Tue, 25 Aug 1998 12:05:11 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id MAA15773; Tue, 25 Aug 1998 12:04:59 -0700 (PDT) From: Gary Kline Message-Id: <199808251904.MAA15773@tao.thought.org> Subject: Almost Back... To: freebsd-ports@FreeBSD.ORG (FreeBSD Ports), hackers@FreeBSD.ORG (Hackers Mailing List) Date: Tue, 25 Aug 1998 12:04:59 -0700 (PDT) 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 To anyone who might have thought that I fell off the corner of the earth--no, still here. My newer 6x86 that was damaged late last June has been restored to a P200 with 64MB and still has its 10GB of disk. Besides the damage that a power-surge (??) did to the 6x86 motherboard, somehow the disklabel on my second SCSI drive was trashed. This caused the kernel to page fault. It was this co-incidence of hardware and software problems that took so long to resolve. As soon as I can find somebody to move the box home and plug things back together, I'll be ready to resume the internationalization of the FreeBSD utility set. I'm planning to mirror the ordering that I've done in porting the 4.4 utilities to the Tera machine. I will post my list for the primary and secondary utilities to the -ports and|or -hackers lists and seek any and all input. Within a few weeks I would like to have a more-or-less complete list of all the utilities that need to be internationalized. Somewhere in my ~/Mail/* files are the names and addresses of the people who helped in my proof-of-concept phase. Because it probably isn't fair to rely on just a few volunteers to translate the English string to French and German, I would like to hear from as many French- and German-speakers as care to volunteer. Several other issues remain, including code reviews, but the most important thing is to see if people are still with me! 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 Tue Aug 25 12:23:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18540 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 12:23:10 -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 MAA18531 for ; Tue, 25 Aug 1998 12:23:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA02527; Tue, 25 Aug 1998 14:22:49 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00952; Tue, 25 Aug 1998 14:21:01 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:21:01 -0500 (CDT) Message-Id: <199808251921.OAA00952@detlev.UUCP> To: nbm@rucus.ru.ac.za CC: skye@ffwd.bc.ca, freebsd-hackers@FreeBSD.ORG In-reply-to: <19980824224314.A21017@rucus.ru.ac.za> (message from Neil Blakey-Milner on Mon, 24 Aug 1998 22:43:14 +0200) Subject: Re: VM crash? questions From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <19980820172445.54455@ffwd.bc.ca> <19980824101733.35426@ffwd.bc.ca> <19980824224314.A21017@rucus.ru.ac.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> No responses - did I subscribe to the right list to get an answer >> to this question? would freebsd-users be a better choice? > It's a question... if you don't know where else to ask it, this is > the place. I thought that freebsd-questions would be more logical, myself. 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 Tue Aug 25 12:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18645 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 12:23:41 -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 MAA18629 for ; Tue, 25 Aug 1998 12:23:39 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA02588; Tue, 25 Aug 1998 14:24:10 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00955; Tue, 25 Aug 1998 14:22:12 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:22:12 -0500 (CDT) Message-Id: <199808251922.OAA00955@detlev.UUCP> To: robert+freebsd@cyrus.watson.org CC: dpk@notreal.com, garbanzo@hooked.net, rabtter@aye.net, hackers@FreeBSD.ORG In-reply-to: (message from Robert Watson on Mon, 24 Aug 1998 17:11:55 -0400 (EDT)) Subject: Re: I want to break binary compatibility. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My favored choice would be to modify the standard dynamic link support to > check /etc/ld.conf (or a sysctl) to determine whether the system policy > currently allowed dynamic linking or not, and if so, whether user-defined > paths were allowed. This, in combination with the bless-support would > work pretty well. Would /etc/ld.conf be vulnerable to chroots? 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 Tue Aug 25 12:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19149 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 12:25:07 -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 MAA19129 for ; Tue, 25 Aug 1998 12:25:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA02704; Tue, 25 Aug 1998 14:25:55 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00961; Tue, 25 Aug 1998 14:24:09 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:24:09 -0500 (CDT) Message-Id: <199808251924.OAA00961@detlev.UUCP> To: matthew@netsol.net CC: hackers@FreeBSD.ORG In-reply-to: <00cb01bdcfb3$8aeb1640$f0a8a8c0@Matt.pandaamerica.com> (matthew@netsol.net) Subject: Re: Imap4 From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <00cb01bdcfb3$8aeb1640$f0a8a8c0@Matt.pandaamerica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyone tell me what imap4 is? i found it in 2.2.7 inetd.conf. It serves the function of POP3, but better. 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 Tue Aug 25 13:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24870 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 13:05:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24853 for ; Tue, 25 Aug 1998 13:05:27 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA169411630; Tue, 25 Aug 1998 15:00:30 -0400 Date: Tue, 25 Aug 1998 15:00:30 -0400 (EDT) From: Bill Fumerola To: Phil Gilley Cc: hackers@FreeBSD.ORG Subject: Re: What options for BW quickcam on 2.2.7 ? 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 I have submitted a port for qcread, it is currently pending a commit. On Tue, 25 Aug 1998, Phil Gilley wrote: > As I've already responded to Luigi in private email, I have ports and > packages for qcam-0.3 and xfqcam-1.05 that I've been maintaining > privately for some time. Since others may want a copy I have made > them available on my Web page: - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 13:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27091 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 13:19:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27003; Tue, 25 Aug 1998 13:19:36 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id VAA27117; Tue, 25 Aug 1998 21:26:28 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA25655; Tue, 25 Aug 1998 22:20:01 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id WAA28888; Tue, 25 Aug 1998 22:18:49 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 25 Aug 1998 22:18:49 +0200 (CEST) From: Stefan Bethke To: freebsd-hackers@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: Warning: Change to netatalk's file name handling 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 As you might be aware, Mac's tend to use characters in file names usually not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or Volumes. I will put a patch in the netatalk port that maps all characters outside of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. This will break access to files which names contain characters in the range \0x01 to \0x1F; they no longer will be accessible from any AFP client (they will be visible, but the client will get a "file not found" error when trying to access it). If nobody objects, I'll commit this the next few days. Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, 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 25 13:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01366 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 13:42:43 -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 NAA01360 for ; Tue, 25 Aug 1998 13:42:42 -0700 (PDT) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA15950; Tue, 25 Aug 1998 13:35:48 -0700 (PDT) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdI15938; Tue Aug 25 20:35:42 1998 Received: (from ambrisko@localhost) by whistle.com (8.8.8/8.8.7) id NAA11928; Tue, 25 Aug 1998 13:23:05 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199808252023.NAA11928@whistle.com> Subject: Re: Netboot In-Reply-To: <877m00cusb.fsf@olymp.sax.de> from Michael Hohmuth at "Aug 23, 98 04:10:44 am" To: hohmuth@innocent.com (Michael Hohmuth) Date: Tue, 25 Aug 1998 13:23:05 -0700 (PDT) Cc: tege@matematik.su.se, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Michael Hohmuth writes: | Torbjorn Granlund writes: | | > Anybody out there that has made netboot work with fxp or de 100baseTX cards? | | There's a package called Etherboot ("archie etherboot") which is based | on Netboot and which contains a GPL'd Etherexpress 100 driver. | However, I think this driver can only be built under Linux; it would | require some hacking to make it compilable natively under FreeBSD. I'm currently using Etherboot to boot FreeBSD on the Intel 100 card. The easiest solution was to build it using the linux-devel package and add back in the FreeBSD boot loader. They have added some really nice features over the original FreeBSD code. I can post a diff to the Etherboot 4.0 code. | On a related note, my group (at TU Dresden) also maintains a version | of the GRUB bootloader (see ) into | which we have integrated (or rather, hacked) the Etherboot drivers. | Again, the networking support currently can only be built under Linux. Hmm, I need to take a look at that. I don't recall seeing the net boot stuff the last time I looked. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 14:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08136 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 14:22:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08017 for ; Tue, 25 Aug 1998 14:22:07 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id RAA00103; Tue, 25 Aug 1998 17:20:46 -0400 (EDT) Date: Tue, 25 Aug 1998 17:20:46 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Joel Ray Holveck cc: dpk@notreal.com, garbanzo@hooked.net, rabtter@aye.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. In-Reply-To: <199808251922.OAA00955@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 Tue, 25 Aug 1998, Joel Ray Holveck wrote: > > My favored choice would be to modify the standard dynamic link support to > > check /etc/ld.conf (or a sysctl) to determine whether the system policy > > currently allowed dynamic linking or not, and if so, whether user-defined > > paths were allowed. This, in combination with the bless-support would > > work pretty well. > > Would /etc/ld.conf be vulnerable to chroots? > > Best, > joelh I was tempted to make the code be influenced by a sysctl -- something that can be read regardless of environment, and would give an indication of the current system policy. However, this is the same problem we keep running into -- I wonder if there is a better solution? chroot causes us a number of problems with code trusting file trees to provide a reliable source for policy and security information. We see libraries (getpwent, etc) consistently relying on the accuracy of paths for reaching resources. However, then we see chroot attempting to provide security by "sandboxing" while at the same time undermining the security mechanisms provided by the remainder of the operating system. It is the desire to have variable file trees displayed to different applications at the same time as having a unique and enforced file tree displayed. This type of sandboxing does not fit well into the standard UNIX model. It might be better served in a dynamic code + message based architecture (such as some combination of Java and Mach). Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 14:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08198 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 14:22:45 -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 OAA08174; Tue, 25 Aug 1998 14:22:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA17644; Tue, 25 Aug 1998 14:11:52 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdC17640; Tue Aug 25 21:11:46 1998 Date: Tue, 25 Aug 1998 14:11:43 -0700 (PDT) From: Julian Elischer To: Stefan Bethke cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling 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 please check with jallison@eng.sgi.com (or if that bounces get back to me) he has patches we use at whistle to make netatalk do various code pages in a manner compatible with samba (which he is a primary developer of) I think his patches already do something similar to what you want (but I'm not sure) julian On Tue, 25 Aug 1998, Stefan Bethke wrote: > As you might be aware, Mac's tend to use characters in file names usually > not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. > > Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or > Volumes. > > I will put a patch in the netatalk port that maps all characters outside > of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. > > This will break access to files which names contain characters in the > range \0x01 to \0x1F; they no longer will be accessible from any AFP > client (they will be visible, but the client will get a "file not found" > error when trying to access it). > > If nobody objects, I'll commit this the next few days. > > Cheers, > Stefan > > -- > Stefan Bethke > Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 > D-22087 Hamburg > Hamburg, Germany > > > 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 25 14:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12481 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 14:41:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12476 for ; Tue, 25 Aug 1998 14:41:17 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id RAA22043; Tue, 25 Aug 1998 17:35:36 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808252135.RAA22043@seedlab1.cropsci.ncsu.edu> Subject: PS/2 MCA Model 80 port --- (don't laugh too hard) To: freebsd-hackers@FreeBSD.ORG Date: Tue, 25 Aug 1998 17:35:34 -0400 (EDT) Cc: bsdbob@seedlab1.cropsci.ncsu.edu (Robert D. Keys) 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 Although the PS/2 line is mostly a dinosaur, there are a lot of the beasts out there. What is the potential of doing a scsi based port to something like the model 80 line (386/16M/scsi) based upon borrowing some of the Minix or Linux code? I am looking for something very low- endian with no frills. Is there anyone that has done something like that or worked in that area, or does any of the early(?) FBSD attempts at that still exist? Curious, (as he says, tongue-in-cheek, but with several AIX PS/2's wanting to get beyond the sysV flavor)...... Bob Keys rdkeys@seelab1.cropsci.ncsu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 15:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21398 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 15:30:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21391 for ; Tue, 25 Aug 1998 15:30:35 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA26744 (5.67b/IDA-1.5); Wed, 26 Aug 1998 00:18:58 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA01621; Tue, 25 Aug 1998 23:04:40 +0200 (CEST) From: Wilko Bulte Message-Id: <199808252104.XAA01621@yedi.iaf.nl> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] In-Reply-To: <199808251858.NAA00795@detlev.UUCP> from Joel Ray Holveck at "Aug 25, 98 01:58:19 pm" To: joelh@gnu.org Date: Tue, 25 Aug 1998 23:04:40 +0200 (CEST) Cc: dakott@alpha.delta.edu, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.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 As Joel Ray Holveck wrote... > > I did have some strange kernel panics when I installed my hardrive > > in front of the CDROM that previously had occupied the bus alone. > > The drive would log timeout errors. Then, as now, my root > > partition/swap et. al was on this drive, the kernel would panic. > > Also, sporadically, the drive would load the kernel sucessfully for > > booting, but would just hang when the kernel attempted to mount the > > root partition. I configured the hardrive to supply the bus > > termination, instead of the CDROM, as well as recompiling my kernel > > sans the "TUNE_1542" option, and I haven't had a problem since. > > Many 1542s (particularly the B series) were very sensitive to poor > cabling and termination problems. I think there were also cabling sensitivities in the C series(?). Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 16:00:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25753 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 16:00:30 -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 PAA25590 for ; Tue, 25 Aug 1998 15:59:47 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-150.camalott.com [208.229.74.150]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA16666; Tue, 25 Aug 1998 18:00:24 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA01698; Tue, 25 Aug 1998 17:58:25 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 17:58:25 -0500 (CDT) Message-Id: <199808252258.RAA01698@detlev.UUCP> To: wilko@yedi.iaf.nl CC: dakott@alpha.delta.edu, hackers@FreeBSD.ORG In-reply-to: <199808252104.XAA01621@yedi.iaf.nl> (message from Wilko Bulte on Tue, 25 Aug 1998 23:04:40 +0200 (CEST)) Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808252104.XAA01621@yedi.iaf.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Many 1542s (particularly the B series) were very sensitive to poor >> cabling and termination problems. > I think there were also cabling sensitivities in the C series(?). Shoot, I don't know offhand. I've had no problems with my 1542C on various cabling configurations (except when I put a connector on backwards), with no RFI shielding in place. 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 Tue Aug 25 16:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27811 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 16:11:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27801 for ; Tue, 25 Aug 1998 16:11:56 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id SAA12263; Tue, 25 Aug 1998 18:08:58 -0400 (EDT) Date: Tue, 25 Aug 1998 18:08:57 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "Robert D. Keys" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808252135.RAA22043@seedlab1.cropsci.ncsu.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 Tue, 25 Aug 1998, Robert D. Keys wrote: > Although the PS/2 line is mostly a dinosaur, there are a lot of the > beasts out there. What is the potential of doing a scsi based port > to something like the model 80 line (386/16M/scsi) based upon borrowing > some of the Minix or Linux code? I am looking for something very low- > endian with no frills. Is there anyone that has done something like > that or worked in that area, or does any of the early(?) FBSD attempts > at that still exist? > > Curious, (as he says, tongue-in-cheek, but with several AIX PS/2's > wanting to get beyond the sysV flavor)...... > This has been asked for on and off for years, but no one who actually had the model 80's wanted to do the work. The number of you guys started small, and is dwindling ... > Bob Keys > rdkeys@seelab1.cropsci.ncsu.edu > > > 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 25 16:47:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03804 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 16:47:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03799 for ; Tue, 25 Aug 1998 16:47:43 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id TAA22508; Tue, 25 Aug 1998 19:42:01 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808252342.TAA22508@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: from Chuck Robey at "Aug 25, 98 06:08:57 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 25 Aug 1998 19:41:59 -0400 (EDT) Cc: 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 > > On Tue, 25 Aug 1998, Robert D. Keys wrote: > > Although the PS/2 line is mostly a dinosaur, ..... > > This has been asked for on and off for years, but no one who actually > had the model 80's wanted to do the work. The number of you guys > started small, and is dwindling ... Well, I guess we are dwindling to some extent. But, there is a fair amount of traffic on the ps/2, linux, and minix newsfeeds that would suggest there might be still some interest. Folks are almost giving the boxes away. I would hate to see linux or minix steal the show. There are a lot of linux patches that I have found and minix only seems to require two patches. That would suggest that it might be easier than it may have been thought in the past, since some (or much) of the groundwork has been done on the other lists. I don't mind borrowing their code for this kind of thing. The scsi systems seem fairly workable, but the ESDI seems to be in another world, entirely. Does anything exist from times past in the FBSD arena? I would like to see what might be there, already. I will offer to do what work I can, since I have half a dozen loose m80's in various configurations. I don't mind putting in some time here and there. I am beginning to get a little tired of AIX 1.x, although it has served me well for the past 10 years. RDK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 17:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09846 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 17:38:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09840 for ; Tue, 25 Aug 1998 17:38:06 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id TAA12422; Tue, 25 Aug 1998 19:34:15 -0400 (EDT) Date: Tue, 25 Aug 1998 19:34:15 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "Robert D. Keys" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808252342.TAA22508@seedlab1.cropsci.ncsu.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 Tue, 25 Aug 1998, Robert D. Keys wrote: > > > > On Tue, 25 Aug 1998, Robert D. Keys wrote: > > > Although the PS/2 line is mostly a dinosaur, ..... > > > > This has been asked for on and off for years, but no one who actually > > had the model 80's wanted to do the work. The number of you guys > > started small, and is dwindling ... > > Well, I guess we are dwindling to some extent. But, there is a fair > amount of traffic on the ps/2, linux, and minix newsfeeds that would > suggest there might be still some interest. Folks are almost giving > the boxes away. I would hate to see linux or minix steal the show. [some deletions] > Does anything exist from times past in the FBSD arena? I would like > to see what might be there, already. > > I will offer to do what work I can, since I have half a dozen loose > m80's in various configurations. I don't mind putting in some time > here and there. I am beginning to get a little tired of AIX 1.x, > although it has served me well for the past 10 years. First place to start is the FreeBSD mailing list archives, at: http://www.freebsd.org/search/search.html > > RDK > > > ----------------------------+----------------------------------------------- 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 25 18:28:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16199 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:28:01 -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 SAA16183 for ; Tue, 25 Aug 1998 18:27:59 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id TAA18440; Tue, 25 Aug 1998 19:20:13 -0600 (MDT) Date: Tue, 25 Aug 1998 19:20:13 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808260120.TAA18440@narnia.plutotech.com> To: "Robert D. Keys" cc: hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) Newsgroups: pluto.freebsd.hackers In-Reply-To: <199808252342.TAA22508@seedlab1.cropsci.ncsu.edu> 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 <199808252342.TAA22508@seedlab1.cropsci.ncsu.edu> you wrote: >> >> On Tue, 25 Aug 1998, Robert D. Keys wrote: >> > Although the PS/2 line is mostly a dinosaur, ..... Last I heard, there was someone in the NetBSD community working on MCA support. You might ask on one of their lists to see if you can take a look at the code. There was also some work from a guy in Australia, probably two years ago now, that was submitted or integrated. You might find mention of it in the questions or hackers list archives. Good Luck! Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 18:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17037 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:33: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 SAA17012 for ; Tue, 25 Aug 1998 18:33:15 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA24504; Tue, 25 Aug 1998 18:32:26 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd024479; Tue Aug 25 18:32:20 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA29380; Tue, 25 Aug 1998 18:32:09 -0700 (MST) From: Terry Lambert Message-Id: <199808260132.SAA29380@usr04.primenet.com> Subject: Re: Imap4 To: nick.hibma@jrc.it Date: Wed, 26 Aug 1998 01:32:09 +0000 (GMT) Cc: matthew@netsol.net, hackers@FreeBSD.ORG In-Reply-To: from "Nick Hibma" at Aug 25, 98 09:51:27 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 > > Can anyone tell me what imap4 is? i found it in 2.2.7 inetd.conf. > > Mail server. It is built around the idea that you do not pull down all > the mail to your system but keep it on the mail server. In that way you > can read mail from several locations without logging in to various > machines. It is also built with slow links in mind. So an IMAP > connection is very useable on a 28k8 modem if you decide to just quickly > browse the subjects. Sorting and deleting is all done on the server not > on the client. The wire protocol is similar to LISP: lots of silly parenthesis. There is also the issue that it is impossible to implement an IMAP client/server automaton using YACC/LEX and/or LALR parser technology because of this (it wants stack-based parsing), without providing a seperate start-state-stack, at a minimum (I have created grammars for IMAP4 servers and clients, so I have some experience here; not happy experience, but the code works...). The primary idea is that the server stores the messages on behalf of the client. This allows for diskless/dataless clients, like palm-pilots, digital cellular phones, JAVA-Phone's, and NC's, to manage mail. It also means that the client machine you use is less important than your credentials, since it tracks against credentials. Many ISPs dislike IMAP4 because it takes a lot of storage, and only gives back increased modem usage and wire traffic in return for the extra storage it consumes -- wait a minute, I get why they don't like it... ;-). One of the most annoying this is that, without a full IMSP implementation, of which there is not one of, there is no provision for fanning out envelope information into sub-mailboxes (which would make IMAP4 useful for virtual domain hosting, where POP3 fails to retain envelope information because of a stupid agrument between Eric Allman and Eric Raymond about "who is the MTA"), nor is there provision for client specification of server side filtering rules (which would make it otherwise more useful than POP3). Basically, it's an interesting "also ran" that won't displace POP3 any time soon until its flaws are noted and corrected. But it's a nice marketing bullet-item, if you're into that sort of thing... 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 25 18:36:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17512 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:36:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from banshee.cs.uow.edu.au (banshee.cs.uow.edu.au [130.130.188.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17507 for ; Tue, 25 Aug 1998 18:36:42 -0700 (PDT) (envelope-from ncb05@banshee.cs.uow.edu.au) Received: (from ncb05@localhost) by banshee.cs.uow.edu.au (8.9.1/8.9.1) id LAA19643; Wed, 26 Aug 1998 11:35:28 +1000 (EST) Date: Wed, 26 Aug 1998 11:35:27 +1000 (EST) From: Nicholas Charles Brawn X-Sender: ncb05@banshee.cs.uow.edu.au To: Joel Ray Holveck cc: rotel@indigo.ie, dyson@iquest.net, imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. In-Reply-To: <199808251811.NAA00561@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 Tue, 25 Aug 1998, Joel Ray Holveck wrote: > Actually, Dyson's idea is the only one I've seen so far that is actual > security instead of obfuscation; that is, it is the only suggestion > that makes it (theoretically) impossible for an intruder to generate > (and run) an arbitrary executable. The others just make the file > difficult to generate, and also require things like custom > cross-compilers. > > However, Dyson forgot another modification that must go along with > this: ld.so must also be modified to ignore most environment > variables. Otherwise, it would be trivial to execute arbitrary bits > of code. > > Something in the back of my mind says that there's still one more hole > dealing with mmap, but I can't place it right now. Then again, I'm > running on four hours of sleep I got in a truck stop parking lot. > > Best, > joelh > If any of you who are involved in this thread aren't subscribed to freebsd-security (why not? *smack*), I've put together something that prevents arbitrary execution of binaries. In effect it's two patches, one for kern_exec.c that disallows execution of binaries given certain conditions, and a hack for rtld.c, that simply skips over grabbing certain environment variables if the user has been disallowed access. The kernel patch is modifiable via sysctl, and the rtld.c hack is via /etc/ld.access (same format as login.access(5)). The url is http://rabble.uow.edu.au/~nick/security/tpe.html Nick -- Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A "When in doubt, ask someone wiser than yourself..." -unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 18:39:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18069 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:39:11 -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 SAA18061 for ; Tue, 25 Aug 1998 18:39:09 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA24794; Tue, 25 Aug 1998 18:38:18 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd024744; Tue Aug 25 18:38:08 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA29820; Tue, 25 Aug 1998 18:38:05 -0700 (MST) From: Terry Lambert Message-Id: <199808260138.SAA29820@usr04.primenet.com> Subject: Re: PCI devices To: tony@dell.com (Tony Overfield) Date: Wed, 26 Aug 1998 01:38:05 +0000 (GMT) Cc: wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG In-Reply-To: <3.0.3.32.19980825111549.00718928@bugs.us.dell.com> from "Tony Overfield" at Aug 25, 98 11:15:49 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 > Microsoft claims their OS can be smarter about configuration than the > BIOS can. They can. Specifically, they can allow the sharing of IRQ's on standard ISA serial ports by interlocking the port opening and the enabling of the interrupts on the UART that was opened, for one thing. FreeBSD could do this too, of course, but doesn't. > So it is accurate advice to tell somebody, if their PCI > devices aren't working and their OS isn't a Microsoft Plug and Play OS, > that they should disable the "Plug & Play Operating System" option in > their BIOS setup program. A PnP OS follows the PnP specification, available from the Intel and Microsoft sites, for free download (use "site search" and look for "PnP specification"). A PnP OS is superior, since it will work on machines without a PnP BIOS. By default, PnP devices are required to be "disabled until enabled"; the bsearch mechanism can be implemented once in the OS; after that, it is no longer necessary to rely on the BIOS vendor "doing the right thing". This will specifically save you on ALR systems, where the Bus Mouse on IRQ 12 is not recognized by the BIOS, and thus not recognized by the early version of Windows 95's PnP code, and therefore was gracelessly stomped when you installed an Adaptec SCSI controller (2940), resulting in neither working correctly. Later versions of Windows 95 /98 with PnP support fixed this problem, where the BIOS failed to do so. Other examples are rampant. 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 25 18:43:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18988 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:43: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 SAA18960 for ; Tue, 25 Aug 1998 18:43:25 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA26096; Tue, 25 Aug 1998 18:42:37 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd026076; Tue Aug 25 18:42:32 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA00101; Tue, 25 Aug 1998 18:42:29 -0700 (MST) From: Terry Lambert Message-Id: <199808260142.SAA00101@usr04.primenet.com> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 26 Aug 1998 01:42:28 +0000 (GMT) Cc: joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG In-Reply-To: <199808252104.XAA01621@yedi.iaf.nl> from "Wilko Bulte" at Aug 25, 98 11:04:40 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 > > Many 1542s (particularly the B series) were very sensitive to poor > > cabling and termination problems. > > I think there were also cabling sensitivities in the C series(?). Specifically, if you have a "B", and you enable the external SCSI connector, you are required to attach an external SCSI terminator. This goes for the 1742B, as well. For the "C", you can look at the SCSI connector; if there is not a pull-up resistor soldered in as an obvious ECN afterthought, then you must use an external terminator as well, AND you will be unable to use both the internal and external connectors for devices, simultaneously. The "C" rev also broke "target mode" support; the controller will support it, but it must have the pull-up, and the default ROMs claim it is unsupported. 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 25 18:43:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19026 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:43:34 -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 SAA18982 for ; Tue, 25 Aug 1998 18:43:29 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA00976; Tue, 25 Aug 1998 20:42:02 -0500 (EST) (envelope-from toor) Message-Id: <199808260142.UAA00976@dyson.iquest.net> Subject: Re: I want to break binary compatibility. In-Reply-To: from Nicholas Charles Brawn at "Aug 26, 98 11:35:27 am" To: ncb05@uow.edu.au (Nicholas Charles Brawn) Date: Tue, 25 Aug 1998 20:42:02 -0500 (EST) Cc: joelh@gnu.org, rotel@indigo.ie, dyson@iquest.net, imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, 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 Nicholas Charles Brawn said: > > If any of you who are involved in this thread aren't subscribed to > freebsd-security (why not? *smack*), I've put together something that > prevents arbitrary execution of binaries. > I am not subscribed to any mailing lists anymore, but drop-in once in a while :-). -- 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 Tue Aug 25 18:45:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19598 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:45:10 -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 SAA19573 for ; Tue, 25 Aug 1998 18:45:05 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA26654; Tue, 25 Aug 1998 18:44:16 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd026640; Tue Aug 25 18:44:08 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA00215; Tue, 25 Aug 1998 18:44:07 -0700 (MST) From: Terry Lambert Message-Id: <199808260144.SAA00215@usr04.primenet.com> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) To: bsdbob@seedlab1.cropsci.ncsu.edu (Robert D. Keys) Date: Wed, 26 Aug 1998 01:44:07 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, bsdbob@seedlab1.cropsci.ncsu.edu In-Reply-To: <199808252135.RAA22043@seedlab1.cropsci.ncsu.edu> from "Robert D. Keys" at Aug 25, 98 05:35: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 > Although the PS/2 line is mostly a dinosaur, there are a lot of the > beasts out there. What is the potential of doing a scsi based port > to something like the model 80 line (386/16M/scsi) based upon borrowing > some of the Minix or Linux code? I am looking for something very low- > endian with no frills. Is there anyone that has done something like > that or worked in that area, or does any of the early(?) FBSD attempts > at that still exist? I have precisely this hardware sitting at home. I also have the PS/2 ethernet cards. I thought the correct approach to take would be to use the ABIOS calls, but I have been unable to locate a copy of the Red Book. 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 25 18:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20033 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:47:32 -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 SAA20023 for ; Tue, 25 Aug 1998 18:47:21 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA20975; Tue, 25 Aug 1998 18:46:33 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd020946; Tue Aug 25 18:46:28 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA00384; Tue, 25 Aug 1998 18:46:26 -0700 (MST) From: Terry Lambert Message-Id: <199808260146.SAA00384@usr04.primenet.com> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) To: bsdbob@seedlab1.cropsci.ncsu.edu (Robert D. Keys) Date: Wed, 26 Aug 1998 01:46:26 +0000 (GMT) Cc: chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808252342.TAA22508@seedlab1.cropsci.ncsu.edu> from "Robert D. Keys" at Aug 25, 98 07:41:59 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 > Does anything exist from times past in the FBSD arena? I would like > to see what might be there, already. Yes. Immediately prior to the 1.1.5.1 snow-job by USL, an Alpha version of a FreeBSD port to the PS/2 was announced on the -hacker list by someone in a Western European country (Holland or Germany, I believe). You could start by looking for that. 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 25 18:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20618 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 18:53:04 -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 SAA20610 for ; Tue, 25 Aug 1998 18:53:00 -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 LAA16967; Wed, 26 Aug 1998 11:21:47 +0930 (CST) Message-Id: <199808260151.LAA16967@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Newton cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ANNOUNCEMENT: SysVR4 binary compatibility for FreeBSD In-reply-to: Your message of "Wed, 26 Aug 1998 03:59:59 +0930." <199808251829.DAA02646@atdot.dotat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 11:21:47 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am pleased to announce the availability of an ALPHA release of an > LKM which implements SysVR4 emulation under FreeBSD. Wohoo :) Nice to see you got TCP stuff working. --------------------------------------------------------------------- |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 25 19:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27473 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 19:44:20 -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 TAA27444 for ; Tue, 25 Aug 1998 19:44:13 -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 CAA02239; Wed, 26 Aug 1998 02:44:47 +0200 From: Luigi Rizzo Message-Id: <199808260044.CAA02239@labinfo.iet.unipi.it> Subject: Re: Netboot To: ambrisko@whistle.com (Doug Ambrisko) Date: Wed, 26 Aug 1998 02:44:47 +0200 (MET DST) Cc: hohmuth@innocent.com, tege@matematik.su.se, hackers@FreeBSD.ORG In-Reply-To: <199808252023.NAA11928@whistle.com> from "Doug Ambrisko" at Aug 25, 98 01:22:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | Torbjorn Granlund writes: > | > | > Anybody out there that has made netboot work with fxp or de 100baseTX cards? > | > | There's a package called Etherboot ("archie etherboot") which is based ... > | However, I think this driver can only be built under Linux; it would > | require some hacking to make it compilable natively under FreeBSD. ... > add back in the FreeBSD boot loader. They have added some really > nice features over the original FreeBSD code. I can post a diff a few questions to those who have looked at this code: 1) which cards does etherboot support ? 2) how hard would it be to make etherboot compilable under FreeBSD ? 3) what "nice features" are you referring to except the 100Mbit support ? about last 1yr ago we managed to make netboot get all of its data from bootpd without having the annoying TFTP configuration file -- that was in my opinion a significant improvement. thanks luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 25 20:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03614 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 20:51:41 -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 UAA03605 for ; Tue, 25 Aug 1998 20:51:37 -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 XAA04734; Tue, 25 Aug 1998 23:59:21 -0400 (EDT) Date: Tue, 25 Aug 1998 23:59:21 -0400 (EDT) From: Charles Youse To: "Robert D. Keys" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808252135.RAA22043@seedlab1.cropsci.ncsu.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 Actually, that wouldn't be terribly hard -- I remember modifying system-level code to run on MCA 286 machines. In a nutshell, the differences are numerous but largely minor (e.g., the 8259s needs to run in level-triggered mode as opposed to edge). These differences between ISA and MCA are enough to keep a stock kernel from running [properly] but shouldn't be prohibitive to change. I think I have an MCA 386SX machine sitting around somewhere. Want to give it a whirl? Chuck Youse cyouse@syncom.net On Tue, 25 Aug 1998, Robert D. Keys wrote: > Although the PS/2 line is mostly a dinosaur, there are a lot of the > beasts out there. What is the potential of doing a scsi based port > to something like the model 80 line (386/16M/scsi) based upon borrowing > some of the Minix or Linux code? I am looking for something very low- > endian with no frills. Is there anyone that has done something like > that or worked in that area, or does any of the early(?) FBSD attempts > at that still exist? > > Curious, (as he says, tongue-in-cheek, but with several AIX PS/2's > wanting to get beyond the sysV flavor)...... > > Bob Keys > rdkeys@seelab1.cropsci.ncsu.edu > > > 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 25 23:10:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13837 for freebsd-hackers-outgoing; Tue, 25 Aug 1998 23:10:09 -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 XAA13827 for ; Tue, 25 Aug 1998 23:10:06 -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 IAA07220 for ; Wed, 26 Aug 1998 08:09:17 +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 IAA19038 for ; Wed, 26 Aug 1998 08:09:15 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id IAA26969 for ; Wed, 26 Aug 1998 08:09:12 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808260609.IAA01556@internal> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: from Julian Elischer at "Aug 25, 98 02:11:43 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 26 Aug 1998 08:09:09 +0200 (CEST) Cc: stb@hanse.de, freebsd-hackers@FreeBSD.ORG, freebsd-stable@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 > please check with jallison@eng.sgi.com > (or if that bounces get back to me) > > > he has patches we use at whistle to make > netatalk do various code pages in a manner compatible with > samba (which he is a primary developer of) > > I think his patches already do something similar to what you want (but I'm > not sure) I would greatly appreciate if there were a workaround for this silly MAC behaviour. I have a local patch for this stuff, but compatiblity with samba would be great. Thanks in advance, -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 26 02:44:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02752 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 02:44:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA02741 for ; Wed, 26 Aug 1998 02:44:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA23416 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Wed, 26 Aug 1998 11:09:34 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA06968 for FreeBSD-hackers@freebsd.org; Wed, 26 Aug 1998 11:09:13 +0200 (CEST) From: Wilko Bulte Message-Id: <199808260909.LAA06968@yedi.iaf.nl> Subject: obtaining Mylex programming information To: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Date: Wed, 26 Aug 1998 11:09:13 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.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 Hi there I'm trying to get a programmers manual for the Mylex DAC960 raid controller cards. I got a response back from Mylex support that a NDA is needed. Although I've sent them mail asking them if the NDA allows releasing source code I don't have high hopes. But I do remember that on this list there was an optimistic note on Mylex some time ago. Does anybody already have the docs (you can always hope..) that is not covered by an NDA? Any help appreciated. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 03:49:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09692 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 03:49:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09679 for ; Wed, 26 Aug 1998 03:49:41 -0700 (PDT) (envelope-from hohmuth@olymp.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA19049; Wed, 26 Aug 1998 12:48:20 +0200 (CEST) (envelope-from hohmuth@olymp.sax.de) Received: (from hohmuth@localhost) by olymp.sax.de (8.8.8/8.8.8) id MAA02041; Wed, 26 Aug 1998 12:38:11 +0200 (CEST) (envelope-from hohmuth) From: Michael Hohmuth To: Doug Ambrisko Cc: tege@matematik.su.se, hackers@FreeBSD.ORG Subject: Re: Netboot References: <199808252023.NAA11928@whistle.com> Mime-Version: 1.0 (generated by tm-edit 7.105) Content-Type: text/plain; charset=US-ASCII Date: 26 Aug 1998 12:38:11 +0200 In-Reply-To: Doug Ambrisko's message of Tue, 25 Aug 1998 13:23:05 -0700 (PDT) Message-ID: <87iujg110s.fsf@olymp.sax.de> Lines: 27 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Ambrisko writes: > Michael Hohmuth writes: > | On a related note, my group (at TU Dresden) also maintains a version > | of the GRUB bootloader (see ) into > | which we have integrated (or rather, hacked) the Etherboot drivers. > | Again, the networking support currently can only be built under Linux. > > Hmm, I need to take a look at that. I don't recall seeing the net boot > stuff the last time I looked. The official GRUB release from Erich Boleyn doesn't contain it yet. I've offered my code to him but he hasn't reacted yet. For now, the code has been integrated only into our own GRUB release; a snapshot is available from . This snapshot is somewhat dated; it only has been verified to work with ET2000 clones. A newer release, which also has been verified to work with WD8003 clones and EtherExpress cards, is being prepared. Michael -- hohmuth@innocent.com, hohmuth@inf.tu-dresden.de http://home.pages.de/~hohmuth/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 03:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09822 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 03:50:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09805 for ; Wed, 26 Aug 1998 03:50:40 -0700 (PDT) (envelope-from hohmuth@olymp.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA19054; Wed, 26 Aug 1998 12:49:49 +0200 (CEST) (envelope-from hohmuth@olymp.sax.de) Received: (from hohmuth@localhost) by olymp.sax.de (8.8.8/8.8.8) id MAA02057; Wed, 26 Aug 1998 12:44:59 +0200 (CEST) (envelope-from hohmuth) From: Michael Hohmuth To: Luigi Rizzo Cc: ambrisko@whistle.com (Doug Ambrisko), tege@matematik.su.se, hackers@FreeBSD.ORG Subject: Re: Netboot References: <199808260044.CAA02239@labinfo.iet.unipi.it> Mime-Version: 1.0 (generated by tm-edit 7.105) Content-Type: text/plain; charset=US-ASCII Date: 26 Aug 1998 12:44:58 +0200 In-Reply-To: Luigi Rizzo's message of Wed, 26 Aug 1998 02:44:47 +0200 (MET DST) Message-ID: <87hfz010ph.fsf@olymp.sax.de> Lines: 27 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes: > a few questions to those who have looked at this code: > 1) which cards does etherboot support ? The same cards that Netboot also supports, plus the Intel EtherExpress card. > 2) how hard would it be to make etherboot compilable under FreeBSD ? You would have to duplicate some of Linux's /usr/include/linux header files. > 3) what "nice features" are you referring to except the 100Mbit > support ? about last 1yr ago we managed to make netboot get all > of its data from bootpd without having the annoying TFTP > configuration file -- that was in my opinion a significant > improvement. I don't know what Doug referred to here, but what do you have against TFTP? Michael -- hohmuth@innocent.com, hohmuth@sax.de http://www.sax.de/~hohmuth/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 03:53:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10060 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 03:53:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA10047 for ; Wed, 26 Aug 1998 03:53:42 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA24744 (5.67b/IDA-1.5); Wed, 26 Aug 1998 11:34:18 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA07176; Wed, 26 Aug 1998 11:18:19 +0200 (CEST) From: Wilko Bulte Message-Id: <199808260918.LAA07176@yedi.iaf.nl> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] In-Reply-To: <199808260142.SAA00101@usr04.primenet.com> from Terry Lambert at "Aug 26, 98 01:42:28 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 26 Aug 1998 11:18:19 +0200 (CEST) Cc: joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.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 As Terry Lambert wrote... > > > Many 1542s (particularly the B series) were very sensitive to poor > > > cabling and termination problems. > > > > I think there were also cabling sensitivities in the C series(?). > > Specifically, if you have a "B", and you enable the external SCSI > connector, you are required to attach an external SCSI terminator. On the B there is no such thing as enabling the external connector. It has resistor packs to be removed in order to use the external connector. Obviously the external connection needs termination in that case. > This goes for the 1742B, as well. There is no 1742B. Only a 174x and 174xA (x =[02] for (no)floppy interface). The 174x are all sensitive to using both internal and external cabling at the same time. For our Alphaservers we simply made that an unsupported config. In addition 174x are sensitive to which disks you use, some simply don't work, primarily the newer/faster ones. > For the "C", you can look at the SCSI connector; if there is not a pull-up > resistor soldered in as an obvious ECN afterthought, then you must use > an external terminator as well, AND you will be unable to use both > the internal and external connectors for devices, simultaneously. > > The "C" rev also broke "target mode" support; the controller will > support it, but it must have the pull-up, and the default ROMs > claim it is unsupported. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 04:02:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11845 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 04:02:12 -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 EAA11840 for ; Wed, 26 Aug 1998 04:02:06 -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 KAA02525; Wed, 26 Aug 1998 10:56:38 +0200 From: Luigi Rizzo Message-Id: <199808260856.KAA02525@labinfo.iet.unipi.it> Subject: Re: Netboot To: hohmuth@innocent.com (Michael Hohmuth) Date: Wed, 26 Aug 1998 10:56:37 +0200 (MET DST) Cc: ambrisko@whistle.com, tege@matematik.su.se, hackers@FreeBSD.ORG In-Reply-To: <87hfz010ph.fsf@olymp.sax.de> from "Michael Hohmuth" at Aug 26, 98 12:44:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 3) what "nice features" are you referring to except the 100Mbit > > support ? about last 1yr ago we managed to make netboot get all > > of its data from bootpd without having the annoying TFTP > > configuration file -- that was in my opinion a significant > > improvement. > > I don't know what Doug referred to here, but what do you have against > TFTP? it's config info in two places instead of one (because bootp is necessary). And handling config info with bootptab is infinitely easier because it is all in a single file, you can use macros to define classes of machines with similar features, and don't have to learn yet another configuration language. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 06:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25917 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 06:08:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25878 for ; Wed, 26 Aug 1998 06:07:57 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id JAA23837; Wed, 26 Aug 1998 09:02:17 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808261302.JAA23837@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: from Charles Youse at "Aug 25, 98 11:59:21 pm" To: cyouse@artemis.syncom.net (Charles Youse) Date: Wed, 26 Aug 1998 09:02:15 -0400 (EDT) Cc: 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 > Actually, that wouldn't be terribly hard -- I remember modifying > system-level code to run on MCA 286 machines. In a nutshell, the > differences are numerous but largely minor (e.g., the 8259s needs to run > in level-triggered mode as opposed to edge). These differences between > ISA and MCA are enough to keep a stock kernel from running [properly] > but shouldn't be prohibitive to change. Yes, most of that can be gleaned from some linux and minix patches and a few snippets of old PS/2 BSD code that I found. I am thinking that it may not be all that difficult after all, at least for a simple scsi port and the 3com 3c523 ethernet card. > I think I have an MCA 386SX machine sitting around somewhere. Want to > give it a whirl? Yes.... Which model? The only thing I like is the model 80....a rugged dinosaur, but good for a single user workstation or ftp archive box. Bob Keys rdkeys@seedlab1.cropsci.ncsu.edu...... last of the ps2 freaks......(:+{{..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 06:10:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26171 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 06:10:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26160 for ; Wed, 26 Aug 1998 06:10:08 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id JAA23845; Wed, 26 Aug 1998 09:04:22 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808261304.JAA23845@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808260146.SAA00384@usr04.primenet.com> from Terry Lambert at "Aug 26, 98 01:46:26 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 26 Aug 1998 09:04:20 -0400 (EDT) Cc: chuckr@Glue.umd.edu, 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 > > Does anything exist from times past in the FBSD arena? I would like > > to see what might be there, already. > > Yes. Immediately prior to the 1.1.5.1 snow-job by USL, an Alpha version > of a FreeBSD port to the PS/2 was announced on the -hacker list by > someone in a Western European country (Holland or Germany, I believe). > > You could start by looking for that. I have been for the past two years, and all I find is a loose reference to it here and there, but no pointers. Anyone still have any sort of pointer to that Alpha thing????? RDK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 06:35:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29830 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 06:35:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29823 for ; Wed, 26 Aug 1998 06:35:14 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id JAA23923; Wed, 26 Aug 1998 09:29:33 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808261329.JAA23923@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808260144.SAA00215@usr04.primenet.com> from Terry Lambert at "Aug 26, 98 01:44:07 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 26 Aug 1998 09:29:31 -0400 (EDT) Cc: 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 > > Although the PS/2 line is mostly a dinosaur, there are a lot of the > > beasts out there. What is the potential of doing a scsi based port > > to something like the model 80 line (386/16M/scsi) based upon borrowing > > some of the Minix or Linux code? I am looking for something very low- > > endian with no frills. Is there anyone that has done something like > > that or worked in that area, or does any of the early(?) FBSD attempts > > at that still exist? > > I have precisely this hardware sitting at home. I also have the > PS/2 ethernet cards. As a general premise.... maybe the port should use the standard IBM scsi-1 controller, the 3c523 card, and scsi tape (I don't have any info on the IBM 6157 (Cypher) tape drives or adapters. I do have a Future Domain mca scsi controller, though, that I could use. > I thought the correct approach to take would be to use the ABIOS calls, > but I have been unable to locate a copy of the Red Book. OK, any info is appreciated. All I have are the minix and linux sources and patches to work with, and some snippets of boot code from an old dead 4.3BSD port to a hybrid RT-PS/2 that never made it in the real world. I am expecting that between all of those bits and pieces, it should be possible to get something to come up. The interrupt handling seems to be the main thing, the A20 line handling, and some wierd adapter probing. Which level of FBSD should we work with? Would it be wise to use something like picobsd to test it out? I understand that current is a bit up in the air. I have AIX up on several PS/2's, and it might be possible to do some sort of a cross compile there, or from my home work box (I can load up whatever version might be best to work with [currently it has 3.0-980523]). RDK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 06:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00866 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 06:42:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00855 for ; Wed, 26 Aug 1998 06:42:21 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id JAA23939; Wed, 26 Aug 1998 09:36:39 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808261336.JAA23939@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808260120.TAA18440@narnia.plutotech.com> from "Justin T. Gibbs" at "Aug 25, 98 07:20:13 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Wed, 26 Aug 1998 09:36:37 -0400 (EDT) Cc: 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 > In article <199808252342.TAA22508@seedlab1.cropsci.ncsu.edu> you wrote: > >> > >> On Tue, 25 Aug 1998, Robert D. Keys wrote: > >> > Although the PS/2 line is mostly a dinosaur, ..... > > Last I heard, there was someone in the NetBSD community working on > MCA support. You might ask on one of their lists to see if you can > take a look at the code. OK, I will ask over there. I run NetBSD on my pmax boxes. I was not aware of any MCA stuff, but anything may help. > There was also some work from a guy in > Australia, probably two years ago now, that was submitted or integrated. > You might find mention of it in the questions or hackers list archives. Anyone remember any pointers to such a fellow or port? > Good Luck! Will need it.....(:+{{.... where did I put my lucky rabbit's foot..... RDK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 07:09:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04574 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 07:09:16 -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 HAA04563 for ; Wed, 26 Aug 1998 07:09: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 QAA20833; Wed, 26 Aug 1998 16:07:00 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id MAA04028; Wed, 26 Aug 1998 12:38:38 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808261038.MAA04028@semyam.dinoco.de> To: zhihuizhang cc: hackers , seggers@semyam.dinoco.de Subject: Re: fs_cs() macro in FFS In-reply-to: Your message of "Tue, 25 Aug 1998 11:33:33 EDT." Date: Wed, 26 Aug 1998 12:38:37 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #define fs_cs(fs, indx) \ > fs_csp[(indx) >> (fs)->fs_csshift] [(indx) & ~(fs)->fs_csmask] > > Since fs_csp is defined as an array of pointers to csum structure, I can > not see why it is accessed as a two-dimension array (I just write a small Just the usual trick in C of making a dynamically sized two dimen- sional array. One makes a pointer to a pointer and allocates it in the right way. Here the first index is limited to MAXCSBUFS (a small integer) and thus can be made a real C array of pointers. The second one depends on the filesystem and can't be treated this way. If you look at the code which allocates it (in ffs_mountfs in the file ffs_vfsops.c) you'll notice it gets allocated as a huge array and then every fs_csp[i] gets a pointer into this huge array makeing up in effect a two dimensional array. It would surely be easier to understand and produce less complex code in some places to make it just one array. Doing it the way it is requires fewer operations for getting a superblock from disk to memory as the array fs_csp is already in the structure - one just has to initialize it. Why it is there I don't know. It is already in the CSRG labelled sources in the repository. If I had to guess mine would be that once the pointers were also used to hold the block numbers of the blocks containing these information. 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 26 07:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06097 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 07:17:25 -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 HAA06086 for ; Wed, 26 Aug 1998 07:17:15 -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 QAA20855; Wed, 26 Aug 1998 16:07:06 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id LAA02792; Wed, 26 Aug 1998 11:56:06 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808260956.LAA02792@semyam.dinoco.de> To: sbabkin@dcn.att.com cc: dag-erli@ifi.uio.no, housley@pr-comm.com, freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: SCSI Controller In-reply-to: Your message of "Thu, 20 Aug 1998 12:47:16 EDT." Date: Wed, 26 Aug 1998 11:56:05 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you're going for low-budget, I'd suggest looking around for NCR > > (SymBios) based controllers. They're cheap and are rumored to work > Symbios is really great and cheap thing. But they are PCI. NCR-5380 and NCR-53C400 based cards (our driver for them is named nca) have their driver under sys/i386/isa. Maybe he thought of these sort of cards? 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 26 07:58:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13145 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 07:58:07 -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 HAA13057 for ; Wed, 26 Aug 1998 07:58:01 -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 OAA02770; Wed, 26 Aug 1998 14:57:30 +0200 From: Luigi Rizzo Message-Id: <199808261257.OAA02770@labinfo.iet.unipi.it> Subject: Re: SCSI Controller To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 26 Aug 1998 14:57:30 +0200 (MET DST) Cc: sbabkin@dcn.att.com, dag-erli@ifi.uio.no, housley@pr-comm.com, freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de In-Reply-To: <199808260956.LAA02792@semyam.dinoco.de> from "Stefan Eggers" at Aug 26, 98 11:55:46 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > If you're going for low-budget, I'd suggest looking around for NCR > > > (SymBios) based controllers. They're cheap and are rumored to work > > > Symbios is really great and cheap thing. But they are PCI. > > NCR-5380 and NCR-53C400 based cards (our driver for them is named nca) > have their driver under sys/i386/isa. Maybe he thought of these sort > of cards? I have a 53c416 -based card (came with an HP scanner) and symbios is sending me some documentation -- no idea how useful it will be but when it comes i will keep you posted. Hopefully it is not too different from the 53c400 so the nca driver can be adapted (the current one does not detect the board i already tried) On the same topic, I also happen to have an Advansys board, and linux as a driver _supported_ by (hear, hear!) Advansys (see www.advansys.com) I have looked briefly at it but i am a bit uncomfortable in patching the 15K-lines source -- even after trimming out the initial 4K lines of defines and the final 3K for PCI support it is still a lot of code... so by chance has anyone else looked at this code and tried a port to FreeBSD ? luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 08:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19784 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 08:32:09 -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 IAA19729 for ; Wed, 26 Aug 1998 08:32:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA15273; Wed, 26 Aug 1998 08:22:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdN15267; Wed Aug 26 15:22:13 1998 Date: Wed, 26 Aug 1998 08:22:08 -0700 (PDT) From: Julian Elischer To: hackers@FreeBSD.ORG cc: jason@idiom.com Subject: Help, Linux beats freebsd to death (fwd) 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 Anyone got good ideas? Jason, can you figure out what system calls are being performed at this time? Is it network re;lated, or filesystem related? Are there pthread related elements? Maybe a ktrace might give some clues.. (or a profile?) this has to be something really silly, because one order of magnitude is just ridiculous.. julian ---------- Forwarded message ---------- Date: Wed, 26 Aug 1998 00:12:20 -0700 From: Jason Venner To: julian@whistle.com Cc: hosler@lugs.org.sg Subject: Linux beats freebsd to death Note I just posted on the postgresql ports board. Either the K6-200 is the fastest machine on the earth or there is something seriously wrong with postgresql/jdbc and freebsd I have a couple of machines that I run postgres 6.3.2 on. Linux 2.0.32 K6-200 1meg cache, 128meg ram, scsi disks - fileserver/workstation/web server/dbms gcc - 2.7.2 FreeBSD 2.2.5-RELEASE P200 512k cache, 96meg ram, scsi - workstation/web server/dbms FreeBSD 2.2.7-RELEASE PII-333 512k cache, 256meg ram, scsi - web server/dbms I have a testsuite that creates a table and inserts a set bunch of rows. I try the table in autocomit on/off mode and rollback and commit it etc. to collect informatin. I am using the distributed jdbc driver as my interface. Under the linux machine it takes on the order of 2 seconds to do this on the 2.2.5 freebsd machine it takes on the order of 18 seconds on the 2.2.7 freebsd machine it takes on the order of 21 seconds To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 09:52:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02334 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 09:52:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02321 for ; Wed, 26 Aug 1998 09:52:46 -0700 (PDT) (envelope-from lyndon@esys.ca) Received: from warhol.esys.ca (warhol.esys.ca [198.161.92.20]) by rembrandt.esys.ca (2.0.4-beta-4/SMS 2.0.4-beta-1) with ESMTP id KAA28672; Wed, 26 Aug 1998 10:51:53 -0600 From: Lyndon Nerenberg Date: Wed, 26 Aug 1998 10:51:53 -0600 To: Terry Lambert Subject: Re: Imap4 Cc: hackers@FreeBSD.ORG In-Reply-To: <199808260132.SAA29380@usr04.primenet.com> References: <199808260132.SAA29380@usr04.primenet.com> from "Nick Hibma" at Aug 25, 98 09:51:27 am Message-ID: X-Mailer: Simeon for Aix Motif Version Mercury a8 Build (11) 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, 26 Aug 1998 01:32:09 +0000 (GMT) Terry Lambert wrote: > The wire protocol is similar to LISP: lots of silly parenthesis. With lots of lists of things flowing around. What's wrong with parens? If it works for Lisp ... :-) > Many ISPs dislike IMAP4 because it takes a lot of storage, and only > gives back increased modem usage and wire traffic in return for > the extra storage it consumes -- wait a minute, I get why they > don't like it... ;-). You mean your IMAP server doesn't implement quotas? Let me give you a URL to our sales page ... And with the push to thin clients and NC, where else are you going to store that mail? Disk is cheap, and the security of having the mail backed up is a big win. > One of the most annoying this is that, without a full IMSP implementation, > of which there is not one of, there is no provision for fanning out > envelope information into sub-mailboxes (which would make IMAP4 > useful for virtual domain hosting, where POP3 fails to retain > envelope information because of a stupid agrument between Eric Allman > and Eric Raymond about "who is the MTA"), nor is there provision for > client specification of server side filtering rules (which would make > it otherwise more useful than POP3). I'm not sure how IMSP helps with virtual domains. This belongs a lot closer to the MTA. IMSP isn't really useful until you've drilled down into the context of an authenticated (IMAP) user. As for filtering, SIEVE is getting close to being reality (there are three prototypes running that I'm aware of). Also, what's a "full" IMSP implementation? There never was an RFC issued. The Cyrus and SMS IMSP servers are as "full" as it gets, being the only two released IMSP servers (that I'm aware of). > Basically, it's an interesting "also ran" that won't displace POP3 > any time soon until its flaws are noted and corrected. I'm going to take great pleasure in quoting that back to you in a couple of years :-) My prediction is that IMAP is going to displace the majority of POP3 implementations over the next 2-3 years. POP3 just can't handle the mobile community that represents more and more of the e-mail users out there today. Now, to add something FreeBSD related, I've been pushing for ESYS to do a port of our servers to FreeBSD for a while now. We've had a couple of requests for it, but not enough to justify the cost of adding another platform. If there's anyone out there who would *buy* *a* *copy* of Simeon Message Server if we did a port, please e-mail me directly. (http://www.esys.ca for more info on the server product.) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 09:53:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02395 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 09:53:16 -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 JAA02365 for ; Wed, 26 Aug 1998 09:53:05 -0700 (PDT) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA17748; Wed, 26 Aug 1998 09:35:56 -0700 (PDT) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdO17741; Wed Aug 26 16:35:49 1998 Received: (from ambrisko@localhost) by whistle.com (8.8.8/8.8.7) id JAA24376; Wed, 26 Aug 1998 09:29:56 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199808261629.JAA24376@whistle.com> Subject: Re: Netboot In-Reply-To: <87hfz010ph.fsf@olymp.sax.de> from Michael Hohmuth at "Aug 26, 98 12:44:58 pm" To: hohmuth@innocent.com (Michael Hohmuth) Date: Wed, 26 Aug 1998 09:29:51 -0700 (PDT) Cc: luigi@labinfo.iet.unipi.it, ambrisko@whistle.com, tege@matematik.su.se, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Michael Hohmuth writes: | Luigi Rizzo writes: | | > a few questions to those who have looked at this code: | > 1) which cards does etherboot support ? | | The same cards that Netboot also supports, plus the Intel EtherExpress | card. .. and more from http://www.slug.org.au/etherboot/: However NIC support is limited to NE2000s/NE1000s (and PCI versions), some Western Digital/SMD cards (80x3, 8216, 8416), a few 3Com cards (3c503, 3c507, 3c509), Lance based cards (such as the NE2100, NI6510 and PCI versions), the NI5210, the Crystal Semiconductor CS89X0 and the Intel Etherexpress Pro Note the "Netboot" project http://www.han.de/~gero/netboot.html supports packet drivers so more NIC's can be used. The main author of Etherboot is starting on a project that would use Linux NIC drivers called Nilo. | > 2) how hard would it be to make etherboot compilable under FreeBSD ? | | You would have to duplicate some of Linux's /usr/include/linux header | files. Technically we should remove the Linux kernel PCI code. Stephan has offered to help. Then we should be able to nuke the Linux includes. | > 3) what "nice features" are you referring to except the 100Mbit | > support ? about last 1yr ago we managed to make netboot get all | > of its data from bootpd without having the annoying TFTP | > configuration file -- that was in my opinion a significant | > improvement. | | I don't know what Doug referred to here, but what do you have against | TFTP? First I hate the TFTP file. It is annoying as Luigi said. I'm netbooting some FreeBSD boxes via ISC's dhcpd. I can put all configuration info in the dhcpd.conf. It's simplier for me. Of course this is my opinion. Features that I like: - Being able to configure a boot menu to solect what mode to boot (ie. pick 1 for FreeBSD, 2 for Linux, 3 for Floppy). Also you can specify a default and timeout. - Booting a device which can be a floppy or hard disk partition. - Boot an netboot rom image. This is good for testing a change to a netboot rom image without burning or writting to a floppy. - Minor but nice, is a rom loader that can be prepended to a rom and dd'ed to a floppy. - Booting "Netboot" stuff from the "Netboot" project such as floppy image booter. - Uses TFTP to load the kernel instead of NFS. This is useful for netbooting off a box that doesn't have NFS. What use is this? Well we use it here for installation and some tools. We make a netboot image that has a built in MFS so it doesn't need swap or root via NFS. This also means the same dhcpd config can be trivially used for a bunch of machines. (Also the way the DEC/Alpha does netboot via BOOTP & TFTP). - Does BOOTP extended options. Not sure about how it works but it permits further options to be passed that exceed the initial packet length by sending them in another packet. One problem I have is that the Etherboot code is that when the option to boot from a hard disk partion, Win98 will fail. This also occured when you selected not to boot from network. This has been fixed in the FreeBSD version so I pulled over the patches for Etherboot and now it works. My patches are on the "Etherboot" web site. I also fixed a couple of buffer copy issues that truncated the bootp packet. However I have not been able to fix the boot from a partition option. I assume the problem is similar to the "do not netboot" option but I don't know enough about booting a hard-drive yet. It would be nice if all this work could converge into a more unified effort. However, I doubt it. Atleast the cross-pollination has improved things. Currently that I know off we have: - NetBSD netboot - FreeBSD netboot - Netboot - Etherboot - Grub (soon) - Commercial netboot roms (which by the way are becoming standard on a lot of PC's shipped with a NIC such as Dell/Gateway) also Intel has published a spec on them here's some info on an annoucement from to the netboot mailing list. From: Marc VUILLEUMIER STUCKELBERG Linux loader for PXE (NetPCs) We ported BpBatch, the tools described in the Linux Remote-boot mini-Howto, to Intel Preboot Execution Environment (PXE). That means, you can now use it with most onboard bootproms to load Linux, to manage disk images and to authenticate users at boot time. To our knowledge, PXE bootproms providers are Intel, Incom and Lanworks (eg. 3com). We hope that NILO will soon be PXE-compliant so that we get free Linux NetPC ! For more informations about PXE, read http://www.intel.com/managedpc/ For more informations about bpbatch, see http://cuiwww.unige.ch/info/pc/remote-boot/ It seems we could get a big bang for the buck by making a loader for the Commercial rom's or PXE compliant to boot the various OS's. It would also be nice to make a "free" commercial compatable rom. This way Dell etc. would ship FreeBSD or whatever netboot'able machines. Installation via netboot are cool. The entire installation and network setup can be automated making installation trivial and we get around the 1.4M boot floppy restriction. We commonly boot a 3.5M MFS kernel to do our automated installs. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 09:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02668 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 09:54:18 -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 JAA02541 for ; Wed, 26 Aug 1998 09:54:06 -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 JAA20352; Wed, 26 Aug 1998 09:52:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808261652.JAA20352@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: hackers@FreeBSD.ORG, jason@idiom.com Subject: Re: Help, Linux beats freebsd to death (fwd) In-reply-to: Your message of "Wed, 26 Aug 1998 08:22:08 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 09:52:58 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try the test suite on 3.0 -current with softupdates enable. Also, I am curious as to what jdk is your friend using . If your friend can mail me his test suite , I can run the benchmark over here and try to provide further analysis. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 09:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02779 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 09:54:31 -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 JAA02695 for ; Wed, 26 Aug 1998 09:54:20 -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 SAA26709 for ; Wed, 26 Aug 1998 18:51:57 +0200 (MET DST) Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id SAA20429; Wed, 26 Aug 1998 18:51:55 +0200 (MET DST) Message-ID: <19980826185155.A20421@loria.fr> Date: Wed, 26 Aug 1998 18:51:55 +0200 From: Olivier Galibert To: hackers@FreeBSD.ORG Subject: Re: Help, Linux beats freebsd to death (fwd) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Wed, Aug 26, 1998 at 08:22:08AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 26, 1998 at 08:22:08AM -0700, Julian Elischer wrote: > > Anyone got good ideas? Asynchronous metadata writing ? Beware that linux 2.1 is even faster when it comes to the filesystem because of the dcache architecture. OG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 10:02:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04325 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:02:12 -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 KAA04316 for ; Wed, 26 Aug 1998 10:02:07 -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 KAA20469; Wed, 26 Aug 1998 10:01:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808261701.KAA20469@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Olivier Galibert cc: hackers@FreeBSD.ORG Subject: Re: Help, Linux beats freebsd to death (fwd) In-reply-to: Your message of "Wed, 26 Aug 1998 18:51:55 +0200." <19980826185155.A20421@loria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 10:01:12 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Aug 26, 1998 at 08:22:08AM -0700, Julian Elischer wrote: > > > > Anyone got good ideas? > > Asynchronous metadata writing ? > > Beware that linux 2.1 is even faster when it comes to the filesystem > because of the dcache architecture. > > OG. and how does it compare to soft updates which I think is bloody fast. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 10:10:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05444 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:10:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05438 for ; Wed, 26 Aug 1998 10:10:47 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) id NAA14864; Wed, 26 Aug 1998 13:06:06 -0400 (EDT) Date: Wed, 26 Aug 1998 13:06:06 -0400 (EDT) From: "Larry S. Lile" To: Terry Lambert cc: "Robert D. Keys" , freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808260144.SAA00215@usr04.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, 26 Aug 1998, Terry Lambert wrote: > > Although the PS/2 line is mostly a dinosaur, there are a lot of the > > beasts out there. What is the potential of doing a scsi based port > > to something like the model 80 line (386/16M/scsi) based upon borrowing > > some of the Minix or Linux code? I am looking for something very low- > > endian with no frills. Is there anyone that has done something like > > that or worked in that area, or does any of the early(?) FBSD attempts > > at that still exist? > > I have precisely this hardware sitting at home. I also have the > PS/2 ethernet cards. > > I thought the correct approach to take would be to use the ABIOS calls, > but I have been unable to locate a copy of the Red Book. I think all of the docs neccesary are available from IBM Pubs. the url is http://www.elink.ibmlink.ibm.com/pbl/pbl?PNL=PBLIC01&CTY=600&LNG=ENU &ORD=PBL80826IOD00536&SRHWRD=PS%2F2&SRHFRM=&SRHPRD=&PRD=ALL&SRHDTF= &SRHDTU=&FRM=ORD&FNC%3DSRH=Search&SRHDBN=000 The more interesting titles being S84F-9807-00 PS/2 TECH REF-SYSTEM SPECIFIC S84F-9808-00 PS/2 TECH REF-ARCHITECTURE S84F-9809-00 PS/2 TECH REF-COMMON INTERFACE S04G-3283-00 IBM PS/2 AND PC BIOS INTERFACE TECH REF S68X-2341-00 PS/2 AND PC BIOS INTERFACE TECHNICAL REFERENCE They also have the tech refs for XGA, Ethernet and various SCSI cards. Most of them are between $55 and $80. I for one would like to see a microchannel port and would be willing to help out, I am not sure if I know enough to be very useful but I would try. I am still working on Token-ring for freebsd despite most peoples opinions on token ring being dead, even though Olicom just released a 100Mbps token ring adapter :) Larry Lile lile@stdio.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 26 10:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05805 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:12:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from albert.osu.cz (albert.osu.cz [195.113.106.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05792 for ; Wed, 26 Aug 1998 10:12:34 -0700 (PDT) (envelope-from belkovic@albert.osu.cz) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id TAA01107 for ; Wed, 26 Aug 1998 19:11:41 +0200 (MET DST) Date: Wed, 26 Aug 1998 19:11:41 +0200 (MET DST) From: Josef Belkovics To: hackers@FreeBSD.ORG Subject: nfs timeout 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 Assume I have on ix015 nfs file system ix012:/osu/zam. Assume I do killall -d -9 nfsd on the server ix012. Then programs like df will hang. Even killall -d -9 bash and then killall -d -9 df doesn't help. I tried all options for mount_nfs (-i -s etc.) + sysctl vfs. I found that df after mount -u /osu/zam behaves well (server is down). Probably all who are using nis + nfs + ppp (server) struck on this problem. Josef Belkovics To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 10:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10509 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:44:56 -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 KAA10458; Wed, 26 Aug 1998 10:44:44 -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 KAA20129; Wed, 26 Aug 1998 10:43:40 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id KAA18134; Wed, 26 Aug 1998 10:43:28 -0700 (PDT) From: Gary Kline Message-Id: <199808261743.KAA18134@tao.thought.org> Subject: Re: Almost Back... In-Reply-To: <199808261609.RAA03640@bsd.synx.com> from Remy NONNENMACHER at "Aug 26, 98 06:09:23 pm" To: remy@synx.com Date: Wed, 26 Aug 1998 10:43:28 -0700 (PDT) Cc: freebsd-ports@FreeBSD.ORG (FreeBSD Ports), hackers@FreeBSD.ORG (Hackers Mailing List), Pierre.David@prism.uvsq.fr 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=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Remy NONNENMACHER: > On 26 Aug, Gary Kline wrote: > > According to Remy NONNENMACHER: > >> On 25 Aug, Gary Kline wrote: > >> >.... Remy, I am copiying the -ports and -hackers lists and Pierre David who helped with the initial translations into French. I'd like whatever comments there are on the colon-spacing issues here. [[ ... ]] > > Here is the message file from usr.bin/cmp. You can ignore > > number 2. In French, 2 translates to ``2 cmp : %s : %s\n'' > > because of their grammar requiring whitespace after the > > colon. > > > This is arguable !!. Imagine something like using a cut -f or an awk > with a specific $N. This will cause the script to stop working (and > will be hard to fix). > > Also, old rules about placing the colons and semi-colons are deprecating > in favor of a unique ponctuation without blank. > > I Urge you (AFAIAC) not to change order nor number of 'fields' output. > The #2 message below only happens in ^error(filename) which does an error exit(). But your point is well taken for most if not all output strings:: it might break scripts and cause unnecessary grief. I can see the English to French translation of ``usage:'' to ``utilisation :'' perhaps. Or in usage strings in #3, #4, and #5 below. Places where it would not break any scripts. What do others think? This can be done either way; the important thing, I think, is to do it correctly. > > > > $ > > $ > > $ $Id: cmp.msg,v 1.1 1998/08/26 14:04:13 kline Exp kline $ > > $ > > $set 1 > > $quote " > > 1 "%s %s differ: char %ld, line %ld\n" > 1 "%s %s diffèrent: caractère %ld, ligne %ld\n" > > 2 "cmp: %s: %s\n" > 2 "cmp: %s: %s\n" > > 3 "cmp: EOF on %s\n" > 3 "cmp: EOF sur %s\n" > 3 "cmp: Fin-de-fichier sur %s\n" > 3 "cmp: FDF sur %s\n" My inclination is to go with ``fin-de-fichier'' to get away from a little of the Unix terseness in the French version. I wouldn't care for EOF to be rewritten ``end-of-file'' only because I'm so used to it. Comments?? > > 4 "cmp: only one of -l and -s may be specified.\n" > 4 "cmp: les options -l et -s sont exclusives l'une de l'autre.\n" > 4 "cmp: -l et -s ne peuvent ^etre employés simultanément" Comments? (Mine only upon request :) > (Note: ^e = ISO-8859-1 #EA) > > 5 "cmp: standard input may only be specified once.\n" > 5 "cmp: l'entrée standard ne peut ^etre spécifiée qu'une seule fois.\n" > > 6 "usage: cmp [-l|s] file1 file2 [skip1] [skip2]\n" > 6 "utilisation: cmp [-l|s] fichier1 fichier2 [saut1] [saut2]\n" > > > > > > gary > > > > PS: I'd like to set up a review group in each language > > in case there are disagreements on specific wordings. > > My bias is to aim toward clarity rather than brevity or > > literalness. > > > > I agree: it's *IMPERATIV*; Multiple translators would produce different > terms for one word depending on context. To avoid the multiplication of > expressions, it's necessary to setup a short word to expression > dictionnary that all translators would agree on and apply. Yes:: dictionary! I've used to German variants for ``usage'' and this needs to be resolved; having an expression-dictionary that was agreeable to the majority would have obviated this problem. > [[ ... ]] A public thanks to everyone who has answered. To answer one thing that I didn't make explicit, this internationalization effort very much welcomes _every_ language. If you can create a .msg file for your language, I'll include it in the /nls//.msg directory. 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 26 10:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10699 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:45:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10679 for ; Wed, 26 Aug 1998 10:45:28 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.7/8.6.9) with SMTP id NAA13879; Wed, 26 Aug 1998 13:42:36 -0400 (EDT) Message-Id: <199808261742.NAA13879@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 26 Aug 1998 13:55:29 -0400 To: Julian Elischer , hackers@FreeBSD.ORG From: Dennis Subject: Re: Help, Linux beats freebsd to death (fwd) Cc: jason@idiom.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Linux is caching something that freebsd isnt...the only explanation for this I think. Or maybe a SCSI cache? are the hard disks and controllers the same? Dennis At 08:22 AM 8/26/98 -0700, Julian Elischer wrote: > >Anyone got good ideas? >Jason, can you figure out what system calls are being performed at this >time? >Is it network re;lated, or filesystem related? >Are there pthread related elements? > > >Maybe a ktrace might give some clues.. >(or a profile?) > >this has to be something really silly, because one order of magnitude >is just ridiculous.. > > >julian > >---------- Forwarded message ---------- >Date: Wed, 26 Aug 1998 00:12:20 -0700 >From: Jason Venner >To: julian@whistle.com >Cc: hosler@lugs.org.sg >Subject: Linux beats freebsd to death > > >Note I just posted on the postgresql ports board. >Either the K6-200 is the fastest machine on the earth or there is >something seriously wrong with postgresql/jdbc and freebsd > > >I have a couple of machines that I run postgres 6.3.2 on. >Linux 2.0.32 K6-200 1meg cache, 128meg ram, scsi disks - fileserver/workstation/web server/dbms > gcc - 2.7.2 >FreeBSD 2.2.5-RELEASE P200 512k cache, 96meg ram, scsi - workstation/web server/dbms >FreeBSD 2.2.7-RELEASE PII-333 512k cache, 256meg ram, scsi - web server/dbms > > >I have a testsuite that creates a table and inserts a set bunch of rows. >I try the table in autocomit on/off mode and rollback and commit it etc. >to collect informatin. > >I am using the distributed jdbc driver as my interface. > >Under the linux machine it takes on the order of 2 seconds to do this >on the 2.2.5 freebsd machine it takes on the order of 18 seconds >on the 2.2.7 freebsd machine it takes on the order of 21 seconds > > >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 Wed Aug 26 10:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10991 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 10:46:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10983 for ; Wed, 26 Aug 1998 10:46:33 -0700 (PDT) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.8.8/8.7) id DAA08675; Thu, 27 Aug 1998 03:12:02 +0930 (CST) Date: Thu, 27 Aug 1998 03:12:02 +0930 (CST) From: Mark Newton Message-Id: <199808261742.DAA08675@atdot.dotat.org> To: freebsd-svr4@atdot.dotat.org Subject: X11 clients seem to work -- But... Cc: freebsd-hackers@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I announced the availability of an ALPHA-quality SVR4 emulator for FreeBSD yesterday. I've done more work on it this evening and managed to get X clients to work -- Kind of. Diligent readers will recall that emulated X clients were failing because a read() on the connection to the X server was returning EAGAIN for no apparent reason. Well, I've written all kinds of debug writes into the emulated SysVR4 read() system call, and I've discovered that this is because the socket underlying the connection to the X server is marked with the SS_NBIO (non-blocking I/O) flag. I have no idea why, though. As far as I can tell, the emulated executables aren't doing anything that sets that flag. Also, emulated executables which (a) use networking, and (b) aren't X clients don't have that flag bit set -- It's something specific to the set of streams ioctl() operations that X clients are doing. I can get X clients to work by indulging in a grotty hack: If SS_NBIO is set when a read() call is made, unset it :-) That's hardly a workable solution, though. I'll make an updated snapshot of my development tree (with the above hack included - ugh) at ftp://slash.dotat.org/pub/freebsd-svr4/svr4.tar.gz. if anyone is interested and wants to see if they can nut it out, please be my guest. - mark [ off to compile a kernel which prints warnings when the ioctl which sets SS_NBIO is used... ] -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 11:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20274 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 11:36:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hoth.ffwd.bc.ca ([209.153.243.242]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20267 for ; Wed, 26 Aug 1998 11:36:07 -0700 (PDT) (envelope-from skye@ffwd.bc.ca) Received: from skye by hoth.ffwd.bc.ca with local (Exim 1.82 #3) id 0zBkOq-00006y-00; Wed, 26 Aug 1998 11:34:28 -0700 Message-ID: <19980826113428.29710@ffwd.bc.ca> Date: Wed, 26 Aug 1998 11:34:28 -0700 From: Skye Poier To: freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions pt.2 References: <19980820172445.54455@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: <19980820172445.54455@ffwd.bc.ca>; from Skye Poier on Thu, Aug 20, 1998 at 05:24:45PM -0700 X-URL: http://www.ffwd.bc.ca/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Update..... Thanks to suggestions from Nick Himba I tried the following: # dd if=/dev/rwd0s1b of=/dev/null Did that several times, no errors. Got 1,153,740 bytes/sec Then I booted into single-user mode (swap partition not swapon'd) and tried: # dd if=/dev/urandom of=/dev/rwd0s1b Again, no errors. It was incredibly slow though! 122,064 bytes/sec I thought urandom may be a bit slow so I tried # dd if=/dev/zero of=/dev/rwd0s1b And got 197,955 bytes/sec. Pretty cruddy for a Quantum Fireball in Mode 4 on a fairly new EIDE controller, no? But anyway, on with the program... Then I tried newfs'ing the swap partition. No errors, ran a couple fsck's. Then I mounted the partition on /mnt and did: # dd if=/dev/urandom of=/mnt/bigfile And bingo, the computer locked up. I rebooted (off floppy, more about that below) back into single-user and remounted the swap part after fscking it, the size of /mnt/bigfile was around 31 MB (the swap partition is 65MB). Couple things I noticed: when my AMD 486/120 went to CPU heaven I put in an Intel DX4-66 but I don't think I got the jumpers quite right because the BIOS reports it running at 80MHz. A long shot, but I'll fix that and see if it helps any. Second thing, when I crashed the machine by creating /mnt/bigfile it seems to have smacked the BSD bootloader :P I have a "dangerously dedicated" partitioning scheme, how can I put the bootloader back in place? Somewhere in /stand/sysinstall? Luckily I have a 2.2.6 boot disk, I booted the kernel from its bootloader with boot: 0:wd(0,a)kernel Thanks, Skye Previously I said: > I am running 2.2.6-RELEASE on a 486 with 16mb of memory and a 65mb swap > partition. > > Recently I've been working with some rather large files and the machine > has had a tendancy to lock up solid. No error on the console, in dmesg, > nothing. It seems to happen when VM (via swapinfo) reaches 30% usage or > about 19MB of the 65MB avaiable.... other than this the server has been > totally bulletproof. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 11:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24324 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 11:52:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hoth.ffwd.bc.ca ([209.153.243.242]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA24298 for ; Wed, 26 Aug 1998 11:52:18 -0700 (PDT) (envelope-from skye@ffwd.bc.ca) Received: from skye by hoth.ffwd.bc.ca with local (Exim 1.82 #3) id 0zBkeS-0000Ad-00; Wed, 26 Aug 1998 11:50:36 -0700 Message-ID: <19980826115036.56889@ffwd.bc.ca> Date: Wed, 26 Aug 1998 11:50:36 -0700 From: Skye Poier To: freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions pt.2 References: <19980820172445.54455@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: <19980820172445.54455@ffwd.bc.ca>; from Skye Poier on Thu, Aug 20, 1998 at 05:24:45PM -0700 X-URL: http://www.ffwd.bc.ca/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I searched the mail archives... can someone confirm that this would be the proper command to fix the BSD bootstrap problem I described in my previous email (yes, I'm paranoid :) My kernel is on /dev/wd0s1a # disklabel -B wd0 Out of curiousity, on a dedicated drive, would fdisk /mbr destroy FreeBSD's partition table? Thanks, Skye To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 12:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26470 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 12:10:59 -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 MAA26444; Wed, 26 Aug 1998 12:10:52 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from olvaldi.ifi.uio.no (2602@olvaldi.ifi.uio.no [129.240.65.43]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA18173; Wed, 26 Aug 1998 21:09:58 +0200 (MET DST) Received: (from dag-erli@localhost) by olvaldi.ifi.uio.no ; Wed, 26 Aug 1998 21:09:57 +0200 (MET DST) Mime-Version: 1.0 To: Gary Kline Cc: remy@synx.com, freebsd-ports@FreeBSD.ORG (FreeBSD Ports), hackers@FreeBSD.ORG (Hackers Mailing List), Pierre.David@prism.uvsq.fr Subject: Re: Almost Back... References: <199808261743.KAA18134@tao.thought.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 I 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: 26 Aug 1998 21:09:57 +0200 In-Reply-To: Gary Kline's message of "Wed, 26 Aug 1998 10:43:28 -0700 (PDT)" Message-ID: Lines: 55 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 MAA26457 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline writes: > > > Here is the message file from usr.bin/cmp. You can ignore > > > number 2. In French, 2 translates to ``2 cmp : %s : %s\n'' > > > because of their grammar requiring whitespace after the > > > colon. No, it doesn't. Our typographical rules (as definied by the JO) do. > I can see the English to French translation of > > ``usage:'' to ``utilisation :'' > > perhaps. Or in usage strings in #3, #4, and #5 below. Places > where it would not break any scripts. "Usage" is correct, but perhaps a little stilted. "utilisation" sounds a little long but is otherwise OK. > My inclination is to go with ``fin-de-fichier'' to get away > from a little of the Unix terseness in the French version. > I wouldn't care for EOF to be rewritten ``end-of-file'' > only because I'm so used to it. I'd go for "Fin de fichier" without hyphens. > > > 4 "cmp: only one of -l and -s may be specified.\n" > > 4 "cmp: les options -l et -s sont exclusives l'une de l'autre.\n" > > 4 "cmp: -l et -s ne peuvent ^etre employés simultanément" > > Comments? (Mine only upon request :) "cmp: -l et -s ne peuvent être employées simultanément.\n" (note the extra 'e' in "employées") > > > PS: I'd like to set up a review group in each language > > > in case there are disagreements on specific wordings. > > > My bias is to aim toward clarity rather than brevity or > > > literalness. Put me on the list. > Yes:: dictionary! I've used to German variants for ``usage'' > and this needs to be resolved; having an expression-dictionary > that was agreeable to the majority would have obviated this > problem. There exists at least one (very thick) English-French dictionary of EE and CS terms, but unfortunately it seems to have been written by an electrical engineer with limited computing experience. May be useful though. ISTR my mother has a copy. 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 26 12:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01804 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 12:37: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 MAA01530 for ; Wed, 26 Aug 1998 12:36:14 -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 MAA04559; Wed, 26 Aug 1998 12:35:05 -0700 (PDT) (envelope-from jdp) Message-Id: <199808261935.MAA04559@austin.polstra.com> To: lyndon@esys.ca Subject: Re: Imap4 In-Reply-To: References: <199808260132.SAA29380@usr04.primenet.com> <09:51:27> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 26 Aug 1998 12:35:05 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Lyndon Nerenberg wrote: > Now, to add something FreeBSD related, I've been pushing for ESYS > to do a port of our servers to FreeBSD for a while now. We've had > a couple of requests for it, but not enough to justify the cost > of adding another platform. If there's anyone out there who would > *buy* *a* *copy* of Simeon Message Server if we did a port, please > e-mail me directly. (http://www.esys.ca for more info on the server > product.) What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. "Reasonable" in my book means that the client fully supports disconnected operation, a requirement not met by any of the Unix clients I'm aware of. (Maybe pine supports it, but it's unreasonable for other reasons. :-) 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 26 12:43:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03170 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 12:43:34 -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 MAA03165; Wed, 26 Aug 1998 12:43:32 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA11518; Wed, 26 Aug 1998 12:42:41 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma011514; Wed Aug 26 12:42:29 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA23260; Wed, 26 Aug 1998 12:42:29 -0700 (PDT) From: Archie Cobbs Message-Id: <199808261942.MAA23260@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: from Stefan Bethke at "Aug 25, 98 10:18:49 pm" To: stb@hanse.de (Stefan Bethke) Date: Wed, 26 Aug 1998 12:42:29 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@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 Stefan Bethke writes: > As you might be aware, Mac's tend to use characters in file names usually > not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. > > Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or > Volumes. > > I will put a patch in the netatalk port that maps all characters outside > of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. I don't quite understand the motivation for changing netatalk. UNIX supports arbitrary characters in file names, so why not use it? If you want file names decoded in a directory listing, use "ls -B". Netatalk seems like the wrong place to modify behavior to solve this problem, which is a display problem, not an encoding problem. -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 Wed Aug 26 12:54:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04965 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 12:54:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04960 for ; Wed, 26 Aug 1998 12:54:34 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id PAA24987; Wed, 26 Aug 1998 15:48:27 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199808261948.PAA24987@seedlab1.cropsci.ncsu.edu> Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: from Chuck Robey at "Aug 25, 98 07:34:15 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 26 Aug 1998 15:48:25 -0400 (EDT) Cc: 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 > > First place to start is the FreeBSD mailing list archives, at: > > http://www.freebsd.org/search/search.html I went through them and all I could find was people asking, no pointers. I went back through the BSD archives back to the beginning, and no pointers, other than Joerg Wunsch's name popped up one time indicating that there were two folks that were working on it, but nothing else. Maybe he still knows something? I did find a fellow in England that is porting an MCA FBSD. I sent him some email and we will see where that goes. I also checked on the NetBSD list, since someone mentioned that there was a NetBSD MCA port ``in progress''. Maybe something will turn up there. Now to get outta here before Hurricane Bonnie blows me away....(:+\\..... RDK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 13:29:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10043 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 13:29:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lautrec.esys.ca (lautrec.esys.ca [198.161.92.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10038 for ; Wed, 26 Aug 1998 13:29:38 -0700 (PDT) (envelope-from lyndon@lautrec.esys.ca) Received: (from lyndon@localhost) by lautrec.esys.ca (2.0.4-beta-4/0.9) id OAA08427; Wed, 26 Aug 1998 14:28:07 -0600 (MDT) To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: Imap4 References: <199808260132.SAA29380@usr04.primenet.com> <09:51:27> <199808261935.MAA04559@austin.polstra.com> From: Lyndon Nerenberg Date: 26 Aug 1998 14:28:07 -0600 In-Reply-To: John Polstra's message of "Wed, 26 Aug 1998 12:35:05 -0700" Message-ID: Lines: 20 X-Mailer: Gnus v5.6.27/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "John" == John Polstra writes: John> What I want is a reasonable IMAP4 _client_ that runs under John> FreeBSD. "Reasonable" in my book means that the client John> fully supports disconnected operation, a requirement not met John> by any of the Unix clients I'm aware of. (Maybe pine John> supports it, but it's unreasonable for other reasons. :-) Ours (Simeon) does disconnected mode. No FreeBSD port, due to a lack of XVT libraries for FreeBSD. We are working on a Linux port, though, and I'm going to do my damndest[*] to see that it runs under the FreeBSD Linux emulation. --lyndon [*] Well, as much as I can given that I work on the servers and not the client. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 13:31:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10356 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 13:31:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lituussun (irc.ladapt.org [195.25.51.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA10351 for ; Wed, 26 Aug 1998 13:31:15 -0700 (PDT) (envelope-from stephane@lituus.fr) Received: from (sequoia.lituus.fr) [193.252.208.74] by lituussun with esmtp (Exim 1.82 #1) id 0zBn4W-0001DC-00; Wed, 26 Aug 1998 22:25:42 +0100 Received: (from root@localhost) by sequoia.lituus.fr (8.9.1/8.9.1) id VAA02683; Mon, 24 Aug 1998 21:58:18 +0200 (CEST) (envelope-from root) Date: Mon, 24 Aug 1998 21:58:18 +0200 (CEST) Message-Id: <199808241958.VAA02683@sequoia.lituus.fr> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Cc: mackler@barter.dewline.com Subject: getpwnam() and getpwuid() functions in libc (was ProFTPD - pwd.db) In-Reply-To: <199808190614.CAA26143@barter.dewline.com> References: <199808190614.CAA26143@barter.dewline.com> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I tested the patch proposed by Adam Mackler on FreeBSD-current and it works well. It corrects a problem with ProFTPD. As the ProFTPD author (Floody ) say, the FreeBSD libc seems to be really different from the others *BSD for that particular point. Should the endpwent() function be called only if _pw_stayopen is false (as the patch suggests and as others *BSD seem do) ? Adam Mackler writes: > > Date: Thu, 6 Aug 1998 17:50:08 -0400 > > From: Floody > > Reply-To: proftpd-l@evcom.net > > To: Karl Pielorz > > Cc: proftpd-l@evcom.net > > Subject: Re: [proftpd-l] New ProFTPd user - Security, Incoming and pwd.db? > > > > Ok. I put up a test FreeBSD 2.2.7 system. There appears to be a libc > > problem with the setpassent() function, which doesn't work on FreeBSD as > > documented in the man pages (or on any other BSD). This is the heart of > > the problem. There is no workaround until libc is fixed. > > Hi: > > I think the following patch may fix the problem, but I'm afraid > I don't know how to rebuild my c library. If you find out if this > works can you let me know? Thanks. > > > *** getpwent.c Wed Aug 19 02:00:13 1998 > --- getpwent.c.dist Wed Aug 19 01:58:33 1998 > *************** > *** 194,201 **** > if (rval && (_pw_passwd.pw_name[0] == '+'|| > _pw_passwd.pw_name[0] == '-')) rval = 0; > > ! if (!_pw_stayopen) > ! endpwent(); > return(rval ? &_pw_passwd : (struct passwd *)NULL); > } > > --- 194,200 ---- > if (rval && (_pw_passwd.pw_name[0] == '+'|| > _pw_passwd.pw_name[0] == '-')) rval = 0; > > ! endpwent(); > return(rval ? &_pw_passwd : (struct passwd *)NULL); > } > > > -- > Adam Mackler > Dewline Communications, LLC > 212-505-9149 > -- stephane@lituus.fr | systeme d'exploitation FreeBSD http://195.25.51.6/stephane/ | 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 Wed Aug 26 13:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10374 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 13:31:32 -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 NAA10368 for ; Wed, 26 Aug 1998 13:31:30 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA06344; Wed, 26 Aug 1998 13:30:39 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd006226; Wed Aug 26 13:30:32 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA20478; Wed, 26 Aug 1998 13:30:24 -0700 (MST) From: Terry Lambert Message-Id: <199808262030.NAA20478@usr02.primenet.com> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 26 Aug 1998 20:30:24 +0000 (GMT) Cc: tlambert@primenet.com, joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG In-Reply-To: <199808260918.LAA07176@yedi.iaf.nl> from "Wilko Bulte" at Aug 26, 98 11:18:19 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 > > This goes for the 1742B, as well. > > There is no 1742B. Only a 174x and 174xA (x =[02] for (no)floppy interface). > > The 174x are all sensitive to using both internal and external cabling > at the same time. For our Alphaservers we simply made that an unsupported > config. In addition 174x are sensitive to which disks you use, some > simply don't work, primarily the newer/faster ones. I'm pretty sure that the 1742 controller in my machine with the 50MHz 486DX (*NOT* DX2), and on which I clock my EISA bus at 50MHz because the 1742B could handle it, where the 1742A could not, is a 1742B. I remember getting it at the time becayse it out performed a Pentium 66 clock doubled from 33 MHz because of the aditional 17MHz of memory and I/O bus speed; that, and Intel and AMD had both promised clock doubled DX2/100 *NOT* DX4/100) chips that would use the 50MHz bus in this ASUS motherboard. I'm also pretty sure the "B" comes from the EISA configuration capability that I had to read the serial number to the Adaptec people so they could tell me if the card supported it, whereby I was able to configure a non-standard translation mode to support larger drives than would otherwise be possible on a 1742/1742A. 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 26 14:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19732 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 14:11:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19625 for ; Wed, 26 Aug 1998 14:10:31 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id QAA00884; Wed, 26 Aug 1998 16:06:50 -0400 (EDT) Date: Wed, 26 Aug 1998 16:06:50 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "Robert D. Keys" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808261948.PAA24987@seedlab1.cropsci.ncsu.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 Wed, 26 Aug 1998, Robert D. Keys wrote: > > > > First place to start is the FreeBSD mailing list archives, at: > > > > http://www.freebsd.org/search/search.html > > I went through them and all I could find was people asking, no > pointers. That's what I said earlier ... that there has been occaisonal interest, but no one who had the hardware wanted to DO it. ----------------------------+----------------------------------------------- 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 Wed Aug 26 14:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20255 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 14:13:22 -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 OAA20236 for ; Wed, 26 Aug 1998 14:13:12 -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 OAA05183; Wed, 26 Aug 1998 14:12:21 -0700 (PDT) (envelope-from jdp) Message-Id: <199808262112.OAA05183@austin.polstra.com> To: Lyndon Nerenberg cc: hackers@FreeBSD.ORG Subject: Re: Imap4 In-reply-to: Your message of "26 Aug 1998 14:28:07 MDT." Date: Wed, 26 Aug 1998 14:12:20 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ours (Simeon) does disconnected mode. No FreeBSD port, due to a lack > of XVT libraries for FreeBSD. > > We are working on a Linux port, though, and I'm going to do my > damndest[*] to see that it runs under the FreeBSD Linux emulation. That's good news. I'll certainly buy one if it works well and the price is right. ($50 if it's tolerable, $100 if it's quite good.) If you need help with the Linux emulation, let us know. I'm sure there are plenty of folks with an interest in seeing this work under FreeBSD. -- 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 26 14:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24396 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 14:31:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24371 for ; Wed, 26 Aug 1998 14:30:54 -0700 (PDT) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id OAA13599 for hackers@freebsd.org; Wed, 26 Aug 1998 14:29:06 -0700 (PDT) (envelope-from joe) Date: Wed, 26 Aug 1998 14:29:06 -0700 (PDT) From: Joe McGuckin Message-Id: <199808262129.OAA13599@monk.via.net> To: hackers@FreeBSD.ORG Subject: 2.2.7 kernel panic - out of map entries Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Several times daily, I get the same panic: Out of map entries for kernel Does anyone know how to fix this? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 14:58:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28598 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 14:58:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28593 for ; Wed, 26 Aug 1998 14:58:37 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA02718; Wed, 26 Aug 1998 15:57:47 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA05468; Wed, 26 Aug 1998 15:57:46 -0600 Date: Wed, 26 Aug 1998 15:57:46 -0600 Message-Id: <199808262157.PAA05468@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: hackers@FreeBSD.ORG, jason@idiom.com Subject: Re: Help, Linux beats freebsd to death (fwd) In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > this has to be something really silly, because one order of magnitude > is just ridiculous.. It's possible that it's a Java problem. Socket code in Java on FreeBSD *SUCKS*, but no-one has the time to profile/optimizeit. Also, make sure they are running the most recent JDK, which contains a # of fixes over the JDK1.1.5 port. For java, see http://www.freebsd.org/java > something seriously wrong with postgresql/jdbc and freebsd ^^^^ Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 15:21:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02212 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:21:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from irc.pcnet.ro (irc.pcnet.ro [193.230.186.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02204 for ; Wed, 26 Aug 1998 15:21:32 -0700 (PDT) (envelope-from miky@pcnet.pcnet.ro) Received: from uucp1.pcnet.ro ([193.230.188.6]) by irc.pcnet.ro (8.8.5/8.8.5) with ESMTP id BAA02136 for ; Thu, 27 Aug 1998 01:32:24 +0300 Received: from miky.UUCP (uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id BAA16343 for hackers@FreeBSD.ORG; Thu, 27 Aug 1998 01:19:41 +0300 X-Mailer: WinNET Mail, v3.5 Message-ID: <691@miky.pcnet.ro> Reply-To: miky@pcnet.pcnet.ro (Mike T.) To: hackers@FreeBSD.ORG Date: Wed, 26 Aug 1998 12:26:25 Subject: what relation is between the microproc,highway & disk size From: miky@pcnet.pcnet.ro (Mike T.) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hy folkes, hy Gary ! Gary Kline wrote: > My newer 6x86 that was damaged late last June has been restored to > a P200 with 64MB and still has its 10GB of disk. Pls.excuse me if I'm intruding,I have a question,it may be a little off-topic,but since I read the 2 lines above I have no peace finding out this : - What relation is between the microprocessor,the number of bits of the computer (or microprocessors) highways and the maximum disk size that the microprocessor can access ( see ) ? - I'm asking this because I read somewhere that a certain micro.,not remember now what it was,could not access ( see ) more than 4GB. - So I suppouse that I can't access with a 286 ,say a 10GB disk. - Happily,I own a Intel-Pentium-133MHz.Would he "see" a 10GB disk if I'll buy one ? please enlight me. miky@pcnet.pcnet.ro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 15:25:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02955 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:25:40 -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 PAA02902; Wed, 26 Aug 1998 15:25:32 -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 AAA13306; Thu, 27 Aug 1998 00:24:38 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 605F31459; Thu, 27 Aug 1998 00:00:27 +0200 (CEST) Date: Thu, 27 Aug 1998 00:00:27 +0200 From: Ollivier Robert To: FreeBSD Ports , Hackers Mailing List Subject: Re: Almost Back... Message-ID: <19980827000027.A19826@keltia.freenix.fr> Mail-Followup-To: FreeBSD Ports , Hackers Mailing List References: <199808261743.KAA18134@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.94.4i In-Reply-To: =?iso-8859-1?Q?=3Cxzpg1ejftkq=2Efsf=40olvaldi=2Eifi=2Euio=2Eno=3E=3B_fro?= =?iso-8859-1?Q?m_Dag-Erling_Coidan_Sm=F8rgrav__on_Wed=2C_Aug_26=2C_1998_?= =?iso-8859-1?Q?at_09:09:57PM_+0200?= X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dag-Erling Coidan Smørgrav : > "Usage" is correct, but perhaps a little stilted. "utilisation" sounds > a little long but is otherwise OK. "Syntaxe : " seems maybe more appropriate than "Utilisation :" while staying correct (and shorter). > I'd go for "Fin de fichier" without hyphens. Agreed. -- 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 26 15:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03039 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:25:52 -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 PAA03005 for ; Wed, 26 Aug 1998 15:25:45 -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 AAA13309 for FreeBSD-hackers@FreeBSD.ORG; Thu, 27 Aug 1998 00:24:52 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 997521459; Thu, 27 Aug 1998 00:02:28 +0200 (CEST) Date: Thu, 27 Aug 1998 00:02:28 +0200 From: Ollivier Robert To: FreeBSD hackers list Subject: Re: obtaining Mylex programming information Message-ID: <19980827000228.B19826@keltia.freenix.fr> Mail-Followup-To: FreeBSD hackers list References: <199808260909.LAA06968@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <199808260909.LAA06968@yedi.iaf.nl>; from Wilko Bulte on Wed, Aug 26, 1998 at 11:09:13AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wilko Bulte: > But I do remember that on this list there was an optimistic note on > Mylex some time ago. Does anybody already have the docs (you can always > hope..) that is not covered by an NDA? I remember Ulf Zimmerman talking about writing a driver for them. Try ulf@alameda.net. -- 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 26 15:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09437 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:57:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09427 for ; Wed, 26 Aug 1998 15:57:47 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA09680; Thu, 27 Aug 1998 00:04:19 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA12440; Thu, 27 Aug 1998 00:57:53 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA15544; Thu, 27 Aug 1998 00:56:38 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Thu, 27 Aug 1998 00:56:38 +0200 (CEST) From: Stefan Bethke To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808261942.MAA23260@bubba.whistle.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, 26 Aug 1998, Archie Cobbs wrote: > Stefan Bethke writes: > > As you might be aware, Mac's tend to use characters in file names usually > > not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. > > > > Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or > > Volumes. > > > > I will put a patch in the netatalk port that maps all characters outside > > of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. > > I don't quite understand the motivation for changing netatalk. UNIX > supports arbitrary characters in file names, so why not use it? > > If you want file names decoded in a directory listing, use "ls -B". > > Netatalk seems like the wrong place to modify behavior to solve this > problem, which is a display problem, not an encoding problem. Where is the encoding defined for character values in the ranges between \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? If you were right, it would be OK for afpd to store all chars literally. While this does work, it is definitly awkward to work with in the shell, and possibly so together with other applications as Samba as well. Its not merely an display issue; its an interoperability issue. I feel that too many things expect file names to confine to printable ascii, and unless this changes, I opt to fix what in my eyes is an obvious bug in afpd (that is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f untouched). It won't change anything to the worse; the only problem is that existing files with file names containing control characters (custom icons on folders being the single source of such name probably) will stop working and will need manual assistance from an operator. Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, 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 26 15:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09464 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:57:57 -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 PAA09449; Wed, 26 Aug 1998 15:57:54 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA13715; Wed, 26 Aug 1998 15:57:05 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma013713; Wed Aug 26 15:56:59 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA28628; Wed, 26 Aug 1998 15:56:59 -0700 (PDT) From: Archie Cobbs Message-Id: <199808262256.PAA28628@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808261942.MAA23260@bubba.whistle.com> from Archie Cobbs at "Aug 26, 98 12:42:29 pm" To: stb@hanse.de Date: Wed, 26 Aug 1998 15:56:59 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@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 I wrote: > > As you might be aware, Mac's tend to use characters in file names usually > > not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. > > > > Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or > > Volumes. > > > > I will put a patch in the netatalk port that maps all characters outside > > of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. > > I don't quite understand the motivation for changing netatalk. UNIX > supports arbitrary characters in file names, so why not use it? > > If you want file names decoded in a directory listing, use "ls -B". > > Netatalk seems like the wrong place to modify behavior to solve this > problem, which is a display problem, not an encoding problem. Or, at least make it controlled by a optional command line option... -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 Wed Aug 26 16:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13755 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 16:16:14 -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 QAA13713 for ; Wed, 26 Aug 1998 16:15:57 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA13989; Wed, 26 Aug 1998 16:15:07 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma013985; Wed Aug 26 16:15:04 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA08454; Wed, 26 Aug 1998 16:15:04 -0700 (PDT) From: Archie Cobbs Message-Id: <199808262315.QAA08454@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: from Stefan Bethke at "Aug 27, 98 00:56:38 am" To: stb@hanse.de (Stefan Bethke) Date: Wed, 26 Aug 1998 16:15:04 -0700 (PDT) Cc: 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 Stefan Bethke writes: > > If you want file names decoded in a directory listing, use "ls -B". > > > > Netatalk seems like the wrong place to modify behavior to solve this > > problem, which is a display problem, not an encoding problem. > > Where is the encoding defined for character values in the ranges between > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > If you were right, it would be OK for afpd to store all chars literally. > While this does work, it is definitly awkward to work with in the shell, > and possibly so together with other applications as Samba as well. Its not > merely an display issue; its an interoperability issue. I feel that too > many things expect file names to confine to printable ascii, and unless > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > untouched). I guess that makes sense, if netatalk is already escaping 0x80-0xff in the same way.. This goes deeper of course... ie, a byte is not the same thing as a character, and the question is, what is the character set and what is the encoding between a character and one or more bytes? Julian's right, in that you should query Jeremy about this for more complete info (but probably only for amusement value :-) [ On the InterJet, for example, you can have it set to Japanese mode, and shared files appear with the same name under AppleTalk and Windows, ie, Samba and Netatalk use the same character encoding. ] -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 Wed Aug 26 17:00:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21166 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 17:00:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA21161 for ; Wed, 26 Aug 1998 17:00:07 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from kcig1.fw.att.com by kcgw1.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Wed Aug 26 14:19 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id OAA28797 for ; Wed, 26 Aug 1998 14:18:56 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Wed, 26 Aug 1998 15:18:52 -0400 Message-ID: To: newton@atdot.dotat.org, freebsd-svr4@atdot.dotat.org Cc: freebsd-hackers@FreeBSD.ORG, mike@smith.net.au Subject: RE: X11 clients seem to work -- But... Date: Wed, 26 Aug 1998 15:18:51 -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: Mark Newton [SMTP:newton@atdot.dotat.org] > > apparent reason. Well, I've written all kinds of debug writes into > the > emulated SysVR4 read() system call, and I've discovered that this is > because the socket underlying the connection to the X server is marked > with the SS_NBIO (non-blocking I/O) flag. > > I have no idea why, though. As far as I can tell, the emulated > executables > aren't doing anything that sets that flag. Also, emulated executables > which (a) use networking, and (b) aren't X clients don't have that > flag > bit set -- It's something specific to the set of streams ioctl() > operations > that X clients are doing. > Is there any chance that the same binary value has different meaning in SVR4, the X clients use it and it gets somehow passed through ? Like the emulator code has the same macro as used in FreeBSD redefined by a SVR4 header ? Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 17:05:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21795 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 17:05:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-21.ppp.wenet.net [206.15.84.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21778 for ; Wed, 26 Aug 1998 17:04:52 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id RAA01215; Wed, 26 Aug 1998 17:00:31 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 26 Aug 1998 17:00:31 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: "Robert D. Keys" cc: Terry Lambert , freebsd-hackers@FreeBSD.ORG Subject: Re: PS/2 MCA Model 80 port --- (don't laugh too hard) In-Reply-To: <199808261329.JAA23923@seedlab1.cropsci.ncsu.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 Wed, 26 Aug 1998, Robert D. Keys wrote: [...] > As a general premise.... maybe the port should use the standard IBM > scsi-1 controller, the 3c523 card, and scsi tape (I don't have any > info on the IBM 6157 (Cypher) tape drives or adapters. I do have a > Future Domain mca scsi controller, though, that I could use. Well, what about the old Adaptec SCSI adapter? I'm thinking that might be easier, because IIRC it's just a 1542 (whatever chip that uses) with MCA stuff around it. > OK, any info is appreciated. All I have are the minix and linux sources > and patches to work with, and some snippets of boot code from an old > dead 4.3BSD port to a hybrid RT-PS/2 that never made it in the real world. > I am expecting that between all of those bits and pieces, it should be > possible to get something to come up. The interrupt handling seems > to be the main thing, the A20 line handling, and some wierd adapter > probing. There was some NetBSD work at getting MCA support, the URL I have is: http://www.epcc.ed.ac.uk/~st/netbsd-mca.html dunno if it's still alive. - 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 Wed Aug 26 18:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04240 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 18:21:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04192 for ; Wed, 26 Aug 1998 18:20:51 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id CAA10879; Thu, 27 Aug 1998 02:27:32 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id DAA11939; Thu, 27 Aug 1998 03:21:07 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id DAA19842; Thu, 27 Aug 1998 03:19:52 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Thu, 27 Aug 1998 03:19:51 +0200 (CEST) From: Stefan Bethke To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808262315.QAA08454@bubba.whistle.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, 26 Aug 1998, Archie Cobbs wrote: > Stefan Bethke writes: > > > Netatalk seems like the wrong place to modify behavior to solve this > > > problem, which is a display problem, not an encoding problem. > > > > Where is the encoding defined for character values in the ranges between > > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > > > If you were right, it would be OK for afpd to store all chars literally. > > While this does work, it is definitly awkward to work with in the shell, > > and possibly so together with other applications as Samba as well. Its not > > merely an display issue; its an interoperability issue. I feel that too > > many things expect file names to confine to printable ascii, and unless > > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > > untouched). > > I guess that makes sense, if netatalk is already escaping 0x80-0xff in > the same way.. It does. > This goes deeper of course... ie, a byte is not the same thing as > a character, and the question is, what is the character set and > what is the encoding between a character and one or more bytes? > Julian's right, in that you should query Jeremy about this for > more complete info (but probably only for amusement value :-) OK. AFP (from 1.0 on) defined the encoding for file names to be the Mac encoding, minus \0x00. I don't really know about non-latin scripts, but I believe the Mac uses it's own escape mechanism to switch to those encodings. AFAIK, there is no character set or encoding defined for file names in FreeBSD, in UNIX, or in POSIX. The only implicit definition is plain ASCII. Even if we were to translate from the Mac enconding to (say) ISO-8859-1, this would loose some of the chars legal in Mac filenames, causing grief to the typical unsuspecting graphics designer. So we need afpd to confine to ASCII, and, as I would suggest, to printable ASCII, as this will make most peoples' live easier (for ASCII, byte values from \0x00 to \0x1F and \0x7F do not produce a glyph, so it is practically useless to store them as-is). > [ On the InterJet, for example, you can have it set to Japanese mode, > and shared files appear with the same name under AppleTalk and > Windows, ie, Samba and Netatalk use the same character encoding. ] That is definitly cool. I hope Julian can provide me with either the patches or the contact, so I can (at least) evaluate and turn down the patches :-) Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, 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 26 18:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08333 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 18:47:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ppp2-134.aye.net (ppp2-134.aye.net [206.185.9.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08205 for ; Wed, 26 Aug 1998 18:46:35 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: from orion.aye.net (localhost [127.0.0.1]) by ppp2-134.aye.net (8.8.7/8.8.7) with ESMTP id VAA00621; Wed, 26 Aug 1998 21:43:15 -0400 (EDT) (envelope-from rabtter@orion.aye.net) Message-ID: <35E4B9B2.3892CF05@orion.aye.net> Date: Wed, 26 Aug 1998 21:43:14 -0400 From: Barrett Richardson X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: dyson@iquest.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. References: <199808260142.UAA00976@dyson.iquest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Many thanks to all who pitched in with information. I believe I now have enough info to start building some systems for my ISP (the owner is also a personal friend of mine from a previous job -- just to clarify some ambiguity in my original posting). The crackers have expressed intent of breaking into our systems again and I think they are going to gain access one way or another (via social engineering if nothing else). Scrambling the syscalls I think is going to have big payoffs per amount of work and I had a look at stackguard per a suggestion. Its a beautifully simple concept, throw a randomly generated word before the return address for a function and have the compiler emit code to insure that it is not clobbered before returning from said function. I do, however have good news to report after our system breach. We did have a quad Challenge DM with 384 megs of RAM. Out of necessity we threw our virtual domains (about 330) on a Pentium 133 with 128 megs of RAM and decided to let it run till it choked before we slapped more RAM and a faster processor in it. The SGI was doing other significant thing other than virtaul domains, but those were responsible for about half the load -- and the SGI was struggling. The choking point we were dreading with our FreeBSD box never came -- still sitting there humming along while we are piecing together some permanent boxes. To say that we are "suprised" is an understatement. - Barrett Richardson rabtter@aye.net John S. Dyson wrote: > > Nicholas Charles Brawn said: > > > > If any of you who are involved in this thread aren't subscribed to > > freebsd-security (why not? *smack*), I've put together something that > > prevents arbitrary execution of binaries. > > > I am not subscribed to any mailing lists anymore, but drop-in once > in a while :-). > > -- > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 18:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10260 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 18:57:45 -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 SAA10247 for ; Wed, 26 Aug 1998 18:57:38 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain.gsoft.com.au (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA01102; Thu, 27 Aug 1998 11:25:39 +0930 (CST) Message-Id: <199808270155.LAA01102@cain.gsoft.com.au> Date: Thu, 27 Aug 1998 11:25:36 +0930 (CST) From: "Daniel O'Connor" Subject: Re: Imap4 To: lyndon@esys.ca cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Aug, Lyndon Nerenberg wrote: > You mean your IMAP server doesn't implement quotas? Let me give you a URL to > our sales page ... And with the push to thin clients and NC, where else are you going to store > that mail? Disk is cheap, and the security of having the mail backed up is a big win. Yes, but if all your users have to keep connecting to your server to read their old mail its not so good :) (But I don't think thats too much of a problem, since most people would just get their mail from the server a la POP3 anyway) > I'm not sure how IMSP helps with virtual domains. This belongs a lot closer to > the MTA. IMSP isn't really useful until you've drilled down into the context > of an authenticated (IMAP) user. As for filtering, SIEVE is getting close to > being reality (there are three prototypes running that I'm aware of). Really? I am curious about this, as Terry has a point in that a lack of server side filter is kind of annoying. Are there any free implementations of this stuff? -- --------------------------------------------------------------------- |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 26 19:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12285 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 19:07:02 -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 TAA12268 for ; Wed, 26 Aug 1998 19:06:54 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain.gsoft.com.au (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA01167; Thu, 27 Aug 1998 11:35:36 +0930 (CST) Message-Id: <199808270205.LAA01167@cain.gsoft.com.au> Date: Thu, 27 Aug 1998 11:35:34 +0930 (CST) From: "Daniel O'Connor" Subject: Re: Imap4 To: jdp@polstra.com cc: lyndon@esys.ca, hackers@FreeBSD.ORG In-Reply-To: <199808261935.MAA04559@austin.polstra.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Aug, John Polstra wrote: > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > "Reasonable" in my book means that the client fully supports > disconnected operation, a requirement not met by any of the Unix > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > for other reasons. :-) Its not like there are many IMAP clients anyway.. The only ones I know of are Pine, TkRat, and fetchmail :) -- --------------------------------------------------------------------- |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 26 19:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13429 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 19:16:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13422 for ; Wed, 26 Aug 1998 19:16:17 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA258740305; Wed, 26 Aug 1998 21:11:45 -0400 Date: Wed, 26 Aug 1998 21:11:45 -0400 (EDT) From: Bill Fumerola Cc: hackers@FreeBSD.ORG Subject: Re: Imap4 In-Reply-To: <199808270155.LAA01102@cain.gsoft.com.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 On Thu, 27 Aug 1998, Daniel O'Connor wrote: > On 26 Aug, Lyndon Nerenberg wrote: > > You mean your IMAP server doesn't implement quotas? Let me give you a URL to > > our sales page ... And with the push to thin clients and NC, where else are you going to store > > that mail? Disk is cheap, and the security of having the mail backed up is a big win. > Yes, but if all your users have to keep connecting to your server to > read their old mail its not so good :) (But I don't think thats too > much of a problem, since most people would just get their mail from the > server a la POP3 anyway) Internal traffic is relativly cheap, and it's the users's bandwidth they're hitting. Do you really see yourself doing 1000+ k/s in email traffic? Doubtful. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 19:20:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13923 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 19:20: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 TAA13915 for ; Wed, 26 Aug 1998 19:20:36 -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 TAA07090; Wed, 26 Aug 1998 19:19:19 -0700 (PDT) (envelope-from jdp) Message-Id: <199808270219.TAA07090@austin.polstra.com> To: "Daniel O'Connor" cc: hackers@FreeBSD.ORG Subject: Re: Imap4 In-reply-to: Your message of "Thu, 27 Aug 1998 11:35:34 +0930." <199808270205.LAA01167@cain.gsoft.com.au> Date: Wed, 26 Aug 1998 19:19:18 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Its not like there are many IMAP clients anyway.. The only ones I > know of are Pine, TkRat, and fetchmail :) Try xfmail. It's the best one I've found. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 20:11:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20554 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 20:11:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20549 for ; Wed, 26 Aug 1998 20:11:18 -0700 (PDT) (envelope-from akm@zeus.theinternet.com.au) Received: (from akm@localhost) by zeus.theinternet.com.au (8.8.7/8.8.7) id NAA01476; Thu, 27 Aug 1998 13:04:06 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199808270304.NAA01476@zeus.theinternet.com.au> Subject: Re: Imap4 In-Reply-To: <199808270205.LAA01167@cain.gsoft.com.au> from Daniel O'Connor at "Aug 27, 98 11:35:34 am" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Thu, 27 Aug 1998 13:04:06 +1000 (EST) Cc: jdp@polstra.com, lyndon@esys.ca, hackers@FreeBSD.ORG 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 +----[ Daniel O'Connor ]--------------------------------------------- | On 26 Aug, John Polstra wrote: | > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. | > "Reasonable" in my book means that the client fully supports | > disconnected operation, a requirement not met by any of the Unix | > clients I'm aware of. (Maybe pine supports it, but it's unreasonable | > for other reasons. :-) | Its not like there are many IMAP clients anyway.. | The only ones I know of are Pine, TkRat, and fetchmail :) Netscape V4. The general populous have their hands on an IMAP client... -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 26 20:15:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21245 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 20:15:27 -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 UAA21231 for ; Wed, 26 Aug 1998 20:15:15 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: (from doconnor@localhost) by cain.gsoft.com.au (8.8.8/8.6.9) id MAA05847; Thu, 27 Aug 1998 12:44:01 +0930 (CST) 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: <199808270304.NAA01476@zeus.theinternet.com.au> Date: Thu, 27 Aug 1998 12:44:01 +0930 (CST) From: "Daniel O'Connor" To: Andrew Kenneth Milton Subject: Re: Imap4 Cc: hackers@FreeBSD.ORG, lyndon@esys.ca, jdp@polstra.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Aug-98 Andrew Kenneth Milton wrote: > | The only ones I know of are Pine, TkRat, and fetchmail :) > Netscape V4. > The general populous have their hands on an IMAP client... Yes, I realised that just after I sent the mail :) --------------------------------------------------------------------- |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 26 20:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24530 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 20:44:22 -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 UAA24525 for ; Wed, 26 Aug 1998 20:44:19 -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 UAA13914; Wed, 26 Aug 1998 20:43:28 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id UAA18902; Wed, 26 Aug 1998 20:43:16 -0700 (PDT) From: Gary Kline Message-Id: <199808270343.UAA18902@tao.thought.org> Subject: Re: what relation is between the microproc,highway & disk size In-Reply-To: <691@miky.pcnet.ro> from "Mike T." at "Aug 26, 98 12:26:25 pm" To: miky@pcnet.pcnet.ro Date: Wed, 26 Aug 1998 20:43:15 -0700 (PDT) Cc: hackers@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 Mike T.: > Hy folkes, hy Gary ! > > Gary Kline wrote: > > > My newer 6x86 that was damaged late last June has been restored to > > a P200 with 64MB and still has its 10GB of disk. > > > Pls.excuse me if I'm intruding,I have a question,it may be a little > off-topic,but since I read the 2 lines above I have no peace finding > out this : > > - What relation is between the microprocessor,the number of bits of > the computer (or microprocessors) highways and the maximum disk size > that the microprocessor can access ( see ) ? > > - I'm asking this because I read somewhere that a certain micro.,not > remember now what it was,could not access ( see ) more than 4GB. > > - So I suppouse that I can't access with a 286 ,say a 10GB disk. > > - Happily,I own a Intel-Pentium-133MHz.Would he "see" a 10GB disk if > I'll buy one ? > > please enlight me. > miky@pcnet.pcnet.ro > Hi Mike, I'll let somebody more hardware-savvy answer this one! People?? 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 26 21:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02131 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 21:40:12 -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 VAA02015; Wed, 26 Aug 1998 21:40:00 -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 VAA14839; Wed, 26 Aug 1998 21:38:50 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id VAA19045; Wed, 26 Aug 1998 21:38:37 -0700 (PDT) Message-ID: <19980826213837.56129@thought.org> Date: Wed, 26 Aug 1998 21:38:37 -0700 From: Gary Kline To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: Gary Kline , remy@synx.com, FreeBSD Ports , Hackers Mailing List , Pierre.David@prism.uvsq.fr Subject: Re: Almost Back... References: <199808261743.KAA18134@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: =?iso-8859-1?Q?=3Cxzpg1ejftkq=2Efsf=40olvaldi=2Eifi=2Euio=2Eno=3E=3B_fro?= =?iso-8859-1?Q?m_Dag-Erling_Coidan_Sm=F8rgrav__on_Wed=2C_Aug_26=2C_1998_?= =?iso-8859-1?Q?at_09=3A09=3A57PM_+0200?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 26, 1998 at 09:09:57PM +0200, Dag-Erling Coidan Smørgrav wrote: > Gary Kline writes: > > > > Here is the message file from usr.bin/cmp. You can ignore > > > > number 2. In French, 2 translates to ``2 cmp : %s : %s\n'' > > > > because of their grammar requiring whitespace after the > > > > colon. > > No, it doesn't. Our typographical rules (as definied by the JO) do. > Yes; I stand corrected. Pierre David did say that this was a typographical rule. What is the JO? (1) And how necessary is it to maintain the colon-space and semicolon-space? All (or virtually all) instances that I have encountered where this change is necessary are error or warning messages; and since I am converting from English: to French :, it would be necessary to hack any scripts anyway. If the *output* involves colons, changing the format from (say) ``%s:'' to ``%s :'' is an issue. I don't want to break scripts even if the output would be typographically correct. > > I can see the English to French translation of > > > > ``usage:'' to ``utilisation :'' > > > > perhaps. Or in usage strings in #3, #4, and #5 below. Places > > where it would not break any scripts. > > "Usage" is correct, but perhaps a little stilted. Yup... > "utilisation" sounds > a little long but is otherwise OK. > > > My inclination is to go with ``fin-de-fichier'' to get away > > from a little of the Unix terseness in the French version. > > I wouldn't care for EOF to be rewritten ``end-of-file'' > > only because I'm so used to it. > > I'd go for "Fin de fichier" without hyphens. Agree. > > > > > 4 "cmp: only one of -l and -s may be specified.\n" > > > 4 "cmp: les options -l et -s sont exclusives l'une de l'autre.\n" > > > 4 "cmp: -l et -s ne peuvent ^etre employés simultanément" > > > > Comments? (Mine only upon request :) > > "cmp: -l et -s ne peuvent être employées simultanément.\n" > > (note the extra 'e' in "employées") Okay. I'll send you the translated results when I've got this nailed down. ... > > > > > PS: I'd like to set up a review group in each language > > > > in case there are disagreements on specific wordings. > > > > My bias is to aim toward clarity rather than brevity or > > > > literalness. > > Put me on the list. Done; thanks//merci! > > > Yes:: dictionary! I've used to German variants for ``usage'' > > and this needs to be resolved; having an expression-dictionary > > that was agreeable to the majority would have obviated this > > problem. > > There exists at least one (very thick) English-French dictionary of EE > and CS terms, but unfortunately it seems to have been written by an > electrical engineer with limited computing experience. May be useful > though. ISTR my mother has a copy. > :-) I would have never imagined there was such a reference. Seems almost surreal somehow. Do you want to be the Keeper of the French translation dictionary? > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no 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 26 22:10:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06849 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 22:10:08 -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 WAA06802; Wed, 26 Aug 1998 22:10:05 -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 WAA15510; Wed, 26 Aug 1998 22:09:13 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id WAA19116; Wed, 26 Aug 1998 22:09:02 -0700 (PDT) Message-ID: <19980826220902.43224@thought.org> Date: Wed, 26 Aug 1998 22:09:02 -0700 From: Gary Kline To: Ollivier Robert Cc: FreeBSD Ports , Hackers Mailing List Subject: Re: Almost Back... References: <199808261743.KAA18134@tao.thought.org> <19980827000027.A19826@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: <19980827000027.A19826@keltia.freenix.fr>; from Ollivier Robert on Thu, Aug 27, 1998 at 12:00:27AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 27, 1998 at 12:00:27AM +0200, Ollivier Robert wrote: > According to Dag-Erling Coidan Smørgrav : > > "Usage" is correct, but perhaps a little stilted. "utilisation" sounds > > a little long but is otherwise OK. > > "Syntaxe : " seems maybe more appropriate than "Utilisation :" while staying > correct (and shorter). > > > I'd go for "Fin de fichier" without hyphens. > Florian Uhl suggested ``Syntax'' as a good German translation for "usage"; so it seems to work in both French and German. Are there any more ideas here? It seems more sensible to use fewer syllables if the meaning is clear. 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 26 22:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06968 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 22:11:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06961 for ; Wed, 26 Aug 1998 22:11:09 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id WAA00827; Wed, 26 Aug 1998 22:07:57 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808262207.WAA00827@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: tony@dell.com (Tony Overfield), wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Wed, 26 Aug 1998 01:38:05 GMT." <199808260138.SAA29820@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 22:07:56 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A PnP OS follows the PnP specification, available from the Intel > and Microsoft sites, for free download (use "site search" and > look for "PnP specification"). > > A PnP OS is superior, since it will work on machines without a PnP > BIOS. This is a fallacious conclusion. An OS which meets the criteria for "PnP OS" in the preceeding discussion need not (and may not) work on a system without a PnP BIOS. As Tony pointed out, all the "PnP OS" setting does is determine whether the BIOS or the OS will perform resource allocation for devices that are not marked as being a potential boot path. > By default, PnP devices are required to be "disabled until enabled"; > the bsearch mechanism can be implemented once in the OS; after that, > it is no longer necessary to rely on the BIOS vendor "doing the right > thing". This is also not correct, as a PnP OS can only operate properly in a situation where resource availibility can be determined. In the PnP BIOS case, this can be obtained from the BIOS. Without a PnP (actually ESCD) BIOS, the OS must guess. -- \\ 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 26 23:10:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15031 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 23:10:27 -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 XAA15002 for ; Wed, 26 Aug 1998 23:10:21 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d28.syd2.zeta.org.au [203.26.11.28]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA31382 for ; Thu, 27 Aug 1998 16:09:28 +1000 Received: (qmail 5040 invoked by uid 1000); 27 Aug 1998 05:59:18 -0000 From: "Andrew Reilly" Message-ID: <19980827155918.A4988@reilly.home> Date: Thu, 27 Aug 1998 15:59:18 +1000 To: Lyndon Nerenberg , John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: Imap4 References: <199808260132.SAA29380@usr04.primenet.com> <09:51:27> <199808261935.MAA04559@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Lyndon Nerenberg on Wed, Aug 26, 1998 at 02:28:07PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 26, 1998 at 02:28:07PM -0600, Lyndon Nerenberg wrote: Sorry Lyndon, I didn't see John's original message until you quoted it... > >>>>> "John" == John Polstra writes: > > John> What I want is a reasonable IMAP4 _client_ that runs under > John> FreeBSD. "Reasonable" in my book means that the client > John> fully supports disconnected operation, a requirement not met > John> by any of the Unix clients I'm aware of. (Maybe pine > John> supports it, but it's unreasonable for other reasons. :-) In what sense does TkRat not support disconnected operation? I honestly don't know, since I use it with a local qmail/fetchmail spool, but it certainly builds with an enormous gob of IMAP (and SMTP) know-how in it, and you can specify mail folders as file, mh, database (tkrat's own), IMAP, POP3 or dynamic (a directory of files). These seem to be happy to access usenet postings as well as mail, but I only use that feature for reading messages I save from knews. It's in the ports collection. I still use a bunch of tools for mail, though: Elm's filter for sorting mailing lists (old habit: I should change to procmail), fetchmail for accessing my ISP's imap box, qmail for local delivery, mailsmtp for off-site delivery to my ISP, mutt for reading mailing lists (at least until tkrat learns about threading), knews for news. You're not looking for a single client that will do all of these things, are you? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 00:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22112 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 00:01:39 -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 AAA22080 for ; Thu, 27 Aug 1998 00:01:28 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA11565; Thu, 27 Aug 1998 02:00:31 -0500 (EST) (envelope-from toor) Message-Id: <199808270700.CAA11565@dyson.iquest.net> Subject: Re: Help, Linux beats freebsd to death (fwd) In-Reply-To: from Julian Elischer at "Aug 26, 98 08:22:08 am" To: julian@whistle.com (Julian Elischer) Date: Thu, 27 Aug 1998 02:00:31 -0500 (EST) Cc: hackers@FreeBSD.ORG, jason@idiom.com 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 Julian Elischer said: > > Anyone got good ideas? > Jason, can you figure out what system calls are being performed at this > time? > Is it network re;lated, or filesystem related? > Are there pthread related elements? > > > Maybe a ktrace might give some clues.. > (or a profile?) > > this has to be something really silly, because one order of magnitude > is just ridiculous.. > I have seen that postgres is sometimes slow on FreeBSD (at least earlier versions), and it seemed to be related to metadata updates, and writes not being delayed. This is one reason why commercial database engines like to use raw partitions, so that the disk image can be forced to be consistant. Try mounting -async or with softupdates, however FreeBSD still doesn't delay writes (for very obvious reasons), but Linux will (and leave your file inconsistant upon crash.) -- 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 Thu Aug 27 01:42:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05859 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 01:42:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05850 for ; Thu, 27 Aug 1998 01:42:20 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id BAA25302; Thu, 27 Aug 1998 01:41:14 -0700 (PDT) Message-Id: <199808270841.BAA25302@mailgate.cadence.com> Received: from (194.32.96.136) by mailgate.cadence.com via smap (mjr-v1.2) id xma904207272.025284; Thu, 27 Aug 98 01:41:12 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: "Daniel O'Connor" Date: Thu, 27 Aug 1998 09:40:49 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Imap4 Reply-to: dmlb@ragnet.demon.co.uk CC: lyndon@esys.ca, hackers@FreeBSD.ORG In-reply-to: <199808270205.LAA01167@cain.gsoft.com.au> References: <199808261935.MAA04559@austin.polstra.com> X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 26 Aug, John Polstra wrote: > > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > > "Reasonable" in my book means that the client fully supports > > disconnected operation, a requirement not met by any of the Unix > > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > > for other reasons. :-) > Its not like there are many IMAP clients anyway.. > The only ones I know of are Pine, TkRat, and fetchmail :) > XFmail in ports has IMAP4 support. Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 02:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09402 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 02:01:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from colin.muc.de (colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA09382 for ; Thu, 27 Aug 1998 02:01:04 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140583-1>; Thu, 27 Aug 1998 08:14:19 +0200 Received: (from daemon@localhost) by tavari.muc.de (8.8.8/8.8.7) id HAA05127; Thu, 27 Aug 1998 07:58:34 +0200 (CEST) Received: from ripley(192.168.42.202) by morranon via smap (V2.1) id xma005125; Thu, 27 Aug 98 07:58:23 +0200 From: "Lutz Albers" To: "Daniel O'Connor" , Cc: , Subject: RE: Imap4 Date: Thu, 27 Aug 1998 07:58:07 +0200 Message-ID: <000101bdd17f$a9b783b0$ca2aa8c0@ripley.tavari.muc.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <199808270205.LAA01167@cain.gsoft.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 26 Aug, John Polstra wrote: > > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > > "Reasonable" in my book means that the client fully supports > > disconnected operation, a requirement not met by any of the Unix > > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > > for other reasons. :-) > Its not like there are many IMAP clients anyway.. > The only ones I know of are Pine, TkRat, and fetchmail :) xfmail-1.3 supports IMAP as well (as does netscape) -- Lutz Albers, lutz@muc.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 02:19:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11845 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 02:19:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsd.synx.com (rt.synx.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA11831; Thu, 27 Aug 1998 02:19:37 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn [192.1.1.241]) by bsd.synx.com (8.6.12/8.6.12) with ESMTP id KAA11736; Thu, 27 Aug 1998 10:17:11 +0100 Message-Id: <199808270917.KAA11736@bsd.synx.com> Date: Thu, 27 Aug 1998 11:17:04 +0200 (CEST) From: Remy NONNENMACHER Reply-To: remy@synx.com Subject: Re: Almost Back... To: kline@thought.org cc: roberto@keltia.freenix.fr, freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <19980826220902.43224@thought.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 CAA11835 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Aug, Gary Kline wrote: > On Thu, Aug 27, 1998 at 12:00:27AM +0200, Ollivier Robert wrote: >> According to Dag-Erling Coidan Smørgrav : >> > "Usage" is correct, but perhaps a little stilted. "utilisation" sounds >> > a little long but is otherwise OK. >> >> "Syntaxe : " seems maybe more appropriate than "Utilisation :" while staying >> correct (and shorter). >> OK for 'Syntaxe'. more informational and precise than 'Utilisation'. >> > I'd go for "Fin de fichier" without hyphens. >> It's correct in term of syntax. Once again, beware of # or orders of fields ouputs. BTW, I had a look on translations provided with some commercial Unixes. I noticed that error messages are quiet always translated without regard to nb of fields, but normal outputs are never translated is it doesn't preserve orders or # of fields. Also, many programs keep English output when scripts are known to use a result from a specific column. RN. ---- Hum, does this discussion won't quickly bother f-hackers ? ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 03:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19644 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 03:19:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cinnamon.michvhf.com (cinnamon.michvhf.com [209.57.60.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA19631 for ; Thu, 27 Aug 1998 03:19:22 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 14865 invoked from network); 27 Aug 1998 10:18:10 -0000 Received: from cinnamon.michvhf.com (209.57.60.10) by cinnamon.michvhf.com with SMTP; 27 Aug 1998 10:18:10 -0000 Date: Thu, 27 Aug 1998 06:18:09 -0400 (EDT) From: Vince Vielhaber To: John Polstra cc: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Imap4 In-Reply-To: <199808270219.TAA07090@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 Wed, 26 Aug 1998, John Polstra wrote: > > Its not like there are many IMAP clients anyway.. The only ones I > > know of are Pine, TkRat, and fetchmail :) > > Try xfmail. It's the best one I've found. I set up Postilion (TkRat based) yesterday and although I haven't had the time to dig too far into it, it seems a bit nicer than xfmail. I had xfmail lock up a number of times randomly but it seemed to be when it was doing an imap call to check for mail. You can check out Postilion complete with screen shots (well screen shot, anyway) at www.postilion.org. The bubble help can get annoying really quick, tho. Good thing it can be turned off! The only thing I'm really gonna miss about xfmail is the multiple from addresses. 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 Thu Aug 27 04:42:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29236 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 04:42:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.phoenixos.com (jobaldwi.campus.vt.edu [198.82.67.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29222 for ; Thu, 27 Aug 1998 04:42:09 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from phoenix.phoenixos.com (localhost [127.0.0.1]) by phoenix.phoenixos.com (8.8.8/8.8.8) with ESMTP id HAA06445; Thu, 27 Aug 1998 07:42:12 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-ID: X-Mailer: XFMail 1.2 [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: <691@miky.pcnet.ro> Date: Thu, 27 Aug 1998 07:42:12 -0400 (EDT) Organization: Virginia Tech From: John Baldwin To: (Mike T.) Subject: RE: what relation is between the microproc,highway & disk size Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 26-Aug-98 Mike T. wrote: Everyone feel free to correct me if I get this wrong... > Hy folkes, hy Gary ! > > Gary Kline wrote: > > > My newer 6x86 that was damaged late last June has been restored to > > a P200 with 64MB and still has its 10GB of disk. > > > Pls.excuse me if I'm intruding,I have a question,it may be a little > off-topic,but since I read the 2 lines above I have no peace finding > out this : > > - What relation is between the microprocessor,the number of bits of > the computer (or microprocessors) highways and the maximum disk size > that the microprocessor can access ( see ) ? For all intents and purposes, none. > - I'm asking this because I read somewhere that a certain micro.,not > remember now what it was,could not access ( see ) more than 4GB. I think you are getting RAM limits mixed up with hard drive limits. The 8088/8086 could only 'see' 1 Meg RAM. The 286, with the advent of Protected Mode could see 16 Meg RAM. With the 386, Intel revamped protected mode to allow a total addressable space of 4 Gig. On some Pentium Pro's (and PII's ??) there is a special processor extension that allows it to see 64 Gig. However, these sizes are for RAM, not hard drive size. What really determines the maximum size hard drive that your system can see is your I/O controller. Due to a combination of BIOS and IDE limits, plain IDE cards can only see a disk of 528 MB or less. When that became a problem, bios translations (the most popular form of which is LBA, Logical (large?) Block Addressing) were used to fudge the limits. With LBA, I/O controllers can handle disks up to 8.4 Gig. Now, here I enter murky waters myself: there is a new standard of some sort that allows disks > 8.4 Gig to be accessed, unfortunately I have no idea what it is called or how it works, hopefully somebody else can help you with that. > - So I suppouse that I can't access with a 286 ,say a 10GB disk. Technically, if you could get an ISA board with one of the new controllers, then it should work, although the BIOS on a 286 motherboard probably can't handle it, but I could be wrong, it might handle it just fine. > - Happily,I own a Intel-Pentium-133MHz.Would he "see" a 10GB disk if > I'll buy one ? Depends on your I/O controller. If it just supports standard LBA, you will only see the first 8.4 Gig of it, AFAIK. > please enlight me. > miky@pcnet.pcnet.ro Hope this helps. John Baldwin - -- jobaldwi@vt.edu -- jbaldwin@freedomnet.com -- ---- http://www.freedomnet.com/~jbaldwin/ ---- "I waited for the Lord on high/I waited and He heard my cry." - Petra -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNeVFCIjYza302vYpAQF7OAL/ey47xHq04PX/D4K6KDvMXQq1t5j7DHPc gHCkEMWuOJ9UI5n5DcLPnCEVIvsDLMU4nfwBw/Jx+SuYAjo1ftTmMcs3A/U138ia ASpZLvBf8/HUhpDcBCbZamNTdheCQ+Ha =Gp21 -----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 27 05:16:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03153 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 05:16:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cinnamon.michvhf.com (cinnamon.michvhf.com [209.57.60.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA03148 for ; Thu, 27 Aug 1998 05:16:13 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 15175 invoked from network); 27 Aug 1998 12:15:18 -0000 Received: from cinnamon.michvhf.com (209.57.60.10) by cinnamon.michvhf.com with SMTP; 27 Aug 1998 12:15:17 -0000 Date: Thu, 27 Aug 1998 08:15:16 -0400 (EDT) From: Vince Vielhaber To: Duncan Barclay cc: "Daniel O'Connor" , lyndon@esys.ca, hackers@FreeBSD.ORG Subject: Re: Imap4 In-Reply-To: <199808270841.BAA25302@mailgate.cadence.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 Thu, 27 Aug 1998, Duncan Barclay wrote: > XFmail in ports has IMAP4 support. If it's ver 1.2, upgrade it to 1.3 (I don't think 1.4 is out yet) as 1.2 has some problems. 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 Thu Aug 27 05:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03575 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 05:19:47 -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 FAA03570 for ; Thu, 27 Aug 1998 05:19:42 -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 IAA02149; Thu, 27 Aug 1998 08:18:18 -0400 Date: Thu, 27 Aug 1998 08:18:18 -0400 (EDT) From: Jamie Bowden To: "Daniel O'Connor" cc: jdp@polstra.com, lyndon@esys.ca, hackers@FreeBSD.ORG Subject: Re: Imap4 In-Reply-To: <199808270205.LAA01167@cain.gsoft.com.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 On Thu, 27 Aug 1998, Daniel O'Connor wrote: > On 26 Aug, John Polstra wrote: > > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > > "Reasonable" in my book means that the client fully supports > > disconnected operation, a requirement not met by any of the Unix > > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > > for other reasons. :-) > Its not like there are many IMAP clients anyway.. > The only ones I know of are Pine, TkRat, and fetchmail :) Netscape 4.0x also does IMAP. I have no idea how well it does it, but it's there. 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 Thu Aug 27 05:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05538 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 05:31:21 -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 FAA05533 for ; Thu, 27 Aug 1998 05:31:19 -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 IAA02161; Thu, 27 Aug 1998 08:29:52 -0400 Date: Thu, 27 Aug 1998 08:29:52 -0400 (EDT) From: Jamie Bowden To: Barrett Richardson cc: dyson@iquest.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. In-Reply-To: <35E4B9B2.3892CF05@orion.aye.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 On Wed, 26 Aug 1998, Barrett Richardson wrote: > I do, however have good news to report after our system breach. We did > have > a quad Challenge DM with 384 megs of RAM. Out of necessity we threw our > virtual domains (about 330) on a Pentium 133 with 128 megs of RAM and > decided to let it run till it choked before we slapped more RAM and a > faster processor in it. The SGI was doing other significant thing other > than virtaul domains, but those were responsible for about half the load > -- > and the SGI was struggling. The choking point we were dreading with our > FreeBSD box never came -- still sitting there humming along while we are > piecing together some permanent boxes. To say that we are "suprised" is > an understatement. I have over 200 virtual domains running off an Indy R4600 @ 133mhz w/ 64M. I don't have any problems with this. Sounds like you need to do some tuning somewhere. Not that FreeBSD isn't capable, it is very capable, and very good at this. My point is that your SGI should be giving you alot better performance than it is. I have found that the single largest botleneck for apache on my SGI's here is the number of file descriptors it's allowed to have open. The system default is fairly low (200 per process, 2500 total), and really should be upped no matter what you are using the machine for. Our Oracle, mail, and news servers all benefited from upping this. I doubt this is relevant only to Irix. 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 Thu Aug 27 06:08:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09579 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 06:08:41 -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 GAA09574 for ; Thu, 27 Aug 1998 06:08:38 -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 PAA04235 for ; Thu, 27 Aug 1998 15:07:41 +0200 (MET DST) Date: Thu, 27 Aug 1998 15:07:39 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: Imap4 (fwd) 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 > > Its not like there are many IMAP clients anyway.. > > The only ones I know of are Pine, TkRat, and fetchmail :) > > Netscape 4.0x also does IMAP. I have no idea how well it does it, but > it's there. Well decently I'd say. I can;t whether it delays fetching of parts in a mime message, but I think it does. So, if you have enough morons on site who send you 10mb Word documents you can see the intro in the message and delete the message without pulling the large chunk across. ... well, pine doesn't, netscape starts to, but you can stop it from doing that. It's a bit overly enthousiastic in pulling down chunks of a Mime encoded message. 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 Thu Aug 27 06:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12127 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 06:31:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12117 for ; Thu, 27 Aug 1998 06:31:43 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id PAA21186; Thu, 27 Aug 1998 15:27:03 +0200 (CEST) Date: Thu, 27 Aug 1998 15:30:12 +0200 From: Stefan Bethke To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: Imap4 Message-ID: <709613.3113220612@d254.promo.de> In-Reply-To: <199808261935.MAA04559@austin.polstra.com> Originator-Info: login-token=Mulberry:01e0yQxO7A9Soau7ZqF3UU X-Mailer: Mulberry Demo (MacOS) [1.4.0a8, s/n Evaluation] 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 On Mit, 26. Aug 1998 12:35 Uhr -0700 John Polstra wrote: > In article , > Lyndon Nerenberg wrote: > >> Now, to add something FreeBSD related, I've been pushing for ESYS >> to do a port of our servers to FreeBSD for a while now. We've had >> a couple of requests for it, but not enough to justify the cost >> of adding another platform. If there's anyone out there who would >> *buy* *a* *copy* of Simeon Message Server if we did a port, please >> e-mail me directly. (http://www.esys.ca for more info on the server >> product.) > > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > "Reasonable" in my book means that the client fully supports > disconnected operation, a requirement not met by any of the Unix > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > for other reasons. :-) Try to talk to CyruSoft (http://www.cyrusoft.com/). Mulberry (now available for Mac and Win only) definitly is the most advanced IMAP client I have seen so far. While I'm somewhat reluctant to spend money on software for private use (no, I'm not pirating, but rather sticking to free alternatives), a decent FreeBSD or Linux port would be worth quite a few bucks for me. Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 07:03:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15075 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 07:03:09 -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 HAA15066; Thu, 27 Aug 1998 07:03:05 -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 QAA23034; Thu, 27 Aug 1998 16:02:08 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 27 Aug 1998 16:02:07 +0200 (MET DST) Mime-Version: 1.0 To: Gary Kline Cc: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= =?iso-8859-1?Q?=2C?= Gary Kline" , remy@synx.com, FreeBSD Ports , Hackers Mailing List , Pierre.David@prism.uvsq.fr Subject: Re: Almost Back... References: <199808261743.KAA18134@tao.thought.org> <19980826213837.56129@thought.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 I 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: 27 Aug 1998 16:02:06 +0200 In-Reply-To: Gary Kline's message of "Wed, 26 Aug 1998 21:38:37 -0700" Message-ID: Lines: 47 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 HAA15071 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline writes: > On Wed, Aug 26, 1998 at 09:09:57PM +0200, Dag-Erling Coidan Smørgrav wrote: > > No, it doesn't. Our typographical rules (as definied by the JO) do. > What is the JO? (1) And how necessary is it to > maintain the colon-space and semicolon-space? The JO is the Journal Officiel, a weekly (IIRC) bulletin in which all new bills and decrees are published (amongst other things). > All (or virtually all) instances that I have encountered > where this change is necessary are error or warning > messages; and since I am converting from English: to > French :, it would be necessary to hack any scripts > anyway. If the *output* involves colons, changing > the format from (say) ``%s:'' to ``%s :'' is an > issue. I don't want to break scripts even if the > output would be typographically correct. I don't think anybody will complain about missing spaces in front of colons or semicolons. Remember that these typographical rules are for documents printed in proportionnally spaced fonts. > > > > > 4 "cmp: only one of -l and -s may be specified.\n" > > > > 4 "cmp: les options -l et -s sont exclusives l'une de l'autre.\n" > > > > 4 "cmp: -l et -s ne peuvent ^etre employés simultanément" > > > Comments? (Mine only upon request :) > > "cmp: -l et -s ne peuvent être employées simultanément.\n" > > > > (note the extra 'e' in "employées") > Okay. I'll send you the translated results when I've got > this nailed down. ... Hmm... actually, whether or not to put an extra 'e' there might be a subject for debate. I consider "-l" and "-s" as feminine (since "option" is assumed) in which case there should be an extra 'e'. Others might not agreee. > I would have never imagined there was such a reference. Seems > almost surreal somehow. Do you want to be the Keeper of the > French translation dictionary? No thanks, I have way too much to do already :) I can proofread the translations and offer advice, but that's about as far as I can go. DES (undercover Frenchman) -- 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 Thu Aug 27 08:13:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23229 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 08:13:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23224 for ; Thu, 27 Aug 1998 08:13:45 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA09026; Thu, 27 Aug 1998 09:12:17 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA08751; Thu, 27 Aug 1998 09:12:16 -0600 Date: Thu, 27 Aug 1998 09:12:16 -0600 Message-Id: <199808271512.JAA08751@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: wilko@yedi.iaf.nl (Wilko Bulte), joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] In-Reply-To: <199808262030.NAA20478@usr02.primenet.com> References: <199808260918.LAA07176@yedi.iaf.nl> <199808262030.NAA20478@usr02.primenet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There is no 1742B. Only a 174x and 174xA (x =[02] for (no)floppy interface). .. > I'm pretty sure that the 1742 controller in my machine with the 50MHz > 486DX (*NOT* DX2), and on which I clock my EISA bus at 50MHz because > the 1742B could handle it, where the 1742A could not, is a 1742B. You're confused. See above. There was no such thing as a 1742B. > I'm also pretty sure the "B" comes from the EISA configuration > capability that I had to read the serial number to the Adaptec people > so they could tell me if the card supported it, whereby I was able to > configure a non-standard translation mode to support larger drives > than would otherwise be possible on a 1742/1742A. That was supported on *all* boards that I'm aware of. At least it was on the 1740 that I had oh so long ago. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 09:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29231 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:00:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA29225 for ; Thu, 27 Aug 1998 09:00:48 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA18584 (5.67b/IDA-1.5); Thu, 27 Aug 1998 17:15:26 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id RAA17496; Thu, 27 Aug 1998 17:14:48 +0200 (CEST) From: Wilko Bulte Message-Id: <199808271514.RAA17496@yedi.iaf.nl> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] In-Reply-To: <199808262030.NAA20478@usr02.primenet.com> from Terry Lambert at "Aug 26, 98 08:30:24 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 27 Aug 1998 17:14:48 +0200 (CEST) Cc: tlambert@primenet.com, joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.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 As Terry Lambert wrote... > > > This goes for the 1742B, as well. > > > > There is no 1742B. Only a 174x and 174xA (x =[02] for (no)floppy interface). > > > > The 174x are all sensitive to using both internal and external cabling > > at the same time. For our Alphaservers we simply made that an unsupported > > config. In addition 174x are sensitive to which disks you use, some > > simply don't work, primarily the newer/faster ones. > > I'm pretty sure that the 1742 controller in my machine with the 50MHz > 486DX (*NOT* DX2), and on which I clock my EISA bus at 50MHz because > the 1742B could handle it, where the 1742A could not, is a 1742B. Hm. You might have a one-off prototype or whatever. > I remember getting it at the time becayse it out performed a Pentium > 66 clock doubled from 33 MHz because of the aditional 17MHz of memory > and I/O bus speed; that, and Intel and AMD had both promised clock > doubled DX2/100 *NOT* DX4/100) chips that would use the 50MHz bus > in this ASUS motherboard. > > I'm also pretty sure the "B" comes from the EISA configuration capability > that I had to read the serial number to the Adaptec people so they could > tell me if the card supported it, whereby I was able to configure a > non-standard translation mode to support larger drives than would otherwise > be possible on a 1742/1742A. You could check the EISA config string, a 1740 is an ADP0000 and a 1740A is a ADP0001 if I remember well. For the 1740 there are multiple sets of firmware/BIOS around, the newer ones have different translations so you can acommodate a big drive. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 09:08:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00579 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:08:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cassiopeia.caprica.com ([207.137.48.14]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA00544 for ; Thu, 27 Aug 1998 09:08:05 -0700 (PDT) (envelope-from frank@exit.com) Received: from exit.com by cassiopeia.caprica.com (8.6.10/95022701) id FAA15389; Thu, 27 Aug 1998 05:29:20 -0800 Received: (from frank@localhost) by exit.com (8.8.8/8.7.3) id IAA14820; Thu, 27 Aug 1998 08:35:35 -0700 (PDT) From: Frank Mayhar Message-Id: <199808271535.IAA14820@exit.com> Subject: Re: cvs commit: src/sbin/ping ping.c To: bsmith@bfmni.com (Brad Smith) Date: Thu, 27 Aug 1998 08:35:34 -0700 (PDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <006601bdd14c$904d0bd0$6403a8c0@comstyle.com> from Brad Smith at "Aug 26, 98 07:52:15 pm" X-Mailer: ELM [version 2.4ME+ PL17 (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 Brad Smith wrote: > Maybe make it like Microsoft's PING where it pings 4 times unless you use > the -t option. > -t Ping the specifed host until interrupted. I dunno, it sounds like change for the sake of change to me. This would be annoying in the extreme; I use infinite pings almost daily. I would have less objection to a change making the ping run for, say, six or eight hours before automatically shutting off. That's long enough (for my purposes) that I would probably never hit the auto-shutoff time, and it still quits by itself after a while. -- Frank Mayhar frank@exit.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 27 09:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02543 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:21:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02538 for ; Thu, 27 Aug 1998 09:21:07 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA11187 for ; Thu, 27 Aug 1998 12:20:14 -0400 (EDT) Date: Thu, 27 Aug 1998 12:20:14 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: FFS 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 I am reading the source code in fs.h and the parameter fs_cpc confuses me. The comment says it is the number of cylinders per *cycle* in position table. What does the "cycle" mean? Basically the position table is used to space out contiguous logical blocks on the disk so that when the disk head moves to the next block, CPU has already initiates a new transfer request for exactly that block. But how can we measure the time it takes CPU (time-sharing by processes) to service an interrupt and initiate a new I/O? Is the disk always moving around at constant speed? When does the disk generate an interrupt? After it finish DMA a block or a sequence of contiguous blocks specified by the CPU's request? 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 27 09:40:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06467 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:40:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsd.synx.com (rt.synx.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA06317; Thu, 27 Aug 1998 09:39:50 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn [192.1.1.241]) by bsd.synx.com (8.6.12/8.6.12) with ESMTP id RAA17639; Thu, 27 Aug 1998 17:37:29 +0100 Message-Id: <199808271637.RAA17639@bsd.synx.com> Date: Thu, 27 Aug 1998 18:37:22 +0200 (CEST) From: Remy NONNENMACHER Reply-To: remy@synx.com Subject: Re: Almost Back... To: dag-erli@ifi.uio.no cc: kline@thought.org, freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG, Pierre.David@prism.uvsq.fr In-Reply-To: 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 JAA06406 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Aug, Dag-Erling Coidan Smørgrav wrote: > Gary Kline writes: >> On Wed, Aug 26, 1998 at 09:09:57PM +0200, Dag-Erling Coidan Smørgrav wrote: > > I don't think anybody will complain about missing spaces in front of > colons or semicolons. Remember that these typographical rules are for > documents printed in proportionnally spaced fonts. > Sure. Anyhow, who still knows rules for employing semi-colons.... >> > > > > 4 "cmp: only one of -l and -s may be specified.\n" >> > > > 4 "cmp: les options -l et -s sont exclusives l'une de l'autre.\n" >> > > > 4 "cmp: -l et -s ne peuvent ^etre employés simultanément" >> > > Comments? (Mine only upon request :) >> > "cmp: -l et -s ne peuvent être employées simultanément.\n" >> > >> > (note the extra 'e' in "employées") >> Okay. I'll send you the translated results when I've got >> this nailed down. ... > > Hmm... actually, whether or not to put an extra 'e' there might be a > subject for debate. I consider "-l" and "-s" as feminine (since > "option" is assumed) in which case there should be an extra 'e'. > Others might not agreee. > I agree. My first version was wrong. it's really 'employées'. RN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 09:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08906 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:53:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08895 for ; Thu, 27 Aug 1998 09:53:00 -0700 (PDT) (envelope-from lyndon@esys.ca) Received: from warhol.esys.ca (warhol.esys.ca [198.161.92.20]) by rembrandt.esys.ca (2.0.4/SMS 2.0.4) with ESMTP id KAA18748; Thu, 27 Aug 1998 10:52:00 -0600 From: Lyndon Nerenberg Date: Thu, 27 Aug 1998 10:52:00 -0600 To: "Daniel O'Connor" Subject: Re: Imap4 Cc: hackers@FreeBSD.ORG In-Reply-To: <199808270155.LAA01102@cain.gsoft.com.au> References: <199808270155.LAA01102@cain.gsoft.com.au> Message-ID: X-Mailer: Simeon for Aix Motif Version Mercury a8 Build (11) 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, 27 Aug 1998 11:25:36 +0930 (CST) Daniel O'Connor wrote: > > I'm not sure how IMSP helps with virtual domains. This belongs a lot closer to > > the MTA. IMSP isn't really useful until you've drilled down into the context > > of an authenticated (IMAP) user. As for filtering, SIEVE is getting close to > > being reality (there are three prototypes running that I'm aware of). > Really? I am curious about this, as Terry has a point in that a lack of > server side filter is kind of annoying. Are there any free > implementations of this stuff? As I said, there are three internal protoypes I know of. There's no public code, mostly because the spec is still a moving target. Much depends on whether consensus was achieved at the IETF this week on the current SIEVE draft. If that happened (I suspect it did, but haven't heard anything concrete yet), then you can expect to see SIEVE implementations rolling out over the next couple of months. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 10:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14883 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 10:31:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from woody.aiinet.com ([206.103.249.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14873 for ; Thu, 27 Aug 1998 10:31:44 -0700 (PDT) (envelope-from mattg@aiinet.com) Received: by mail2.aiinet.com with Internet Mail Service (5.0.1460.8) id <38TXWWG9>; Thu, 27 Aug 1998 13:31:00 -0400 Message-ID: <7283DE19D141D111AD0E00A0C95B1955CF12B6@mail2.aiinet.com> From: "Gessner, Matt" To: "'freebsd-hackers@freebsd.org'" Subject: FW: Q was on questions, now putting it here. Date: Thu, 27 Aug 1998 13:30:54 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ---------- > From: Gessner, Matt > Sent: Thursday, August 27, 1998 10:40 AM > To: 'freebsd-questions@freebsd.org' > Subject: FW: Q was on questions, now putting it here. > > I guess this died of lack of notice??? > > Can anyone suggest somewhere to at least start looking into making this > work? > Or is 2048 TCP connections too much to ask of this setup? > > TIA > > > ---------- > > From: Gessner, Matt > > Sent: Sunday, August 23, 1998 10:44 PM > > To: 'hackers' > > Subject: Q was on questions, now putting it here. > > > > Hi, all, > > > > I posted to comp.unix.bsd.freebsd.misc but nothing's come back... news > > takes > > a while. > > > > I'm running 2.2.7-RELEASE, and I've already changed my kernel a bit to > > allow me to do a whole bunch of simultaneous connections, but I've > > probably done something wrong, because it ain't working. > > > > Here's what I have: > > > > P5-166 Gateway > > 32 MB RAM > > 2 GB disk, 850MB belongs to FreeBSD, of which 100MB is swap. > > PCI DEC Ethernet card > > > > Here's how I've mangled my poor kernel: > > maxusers 128 > > options CHILD_MAX=256 > > options OPEN_MAX=2048 > > options NMBCLUSTERS=4096 > > > > Here's how I've changed login.conf > > > > default and root both have unlimited child process and open file > > counts. > > > > I've done a little poking around in param.c and don't see immediately > > that I've violated any rules by setting these limits the way I have. > > > > When I type limits, I get the following info back: > > > > maxprocesses 2067 > > openfiles 4136 > > > > But I can't find anything anywhere that talks about tuning the kernel > > for doing this. > > > > What I need to do is be able to run lots of TCP connections, and I know > > it can be done with FreeBSD. > > > > The connections are being made from FreeBSD to a proprietary board and > > then to a Solaris machine. > > > > My end goal is to be able to bring up about 1024 TCP connections > > outbound and route them back to the same box, for a total of 2048 > > connections. > > > > Right now, I run 1024 connections to the other system, and what happens > > is when the sockets are all connected, and the writes start to occur, > > FreeBSD > > just reboots the machine -- no messages anywhere. > > > > Have I really goofed up somewhere/something? Can anyone give me some > > insight as to what MIGHT be happening here? E-mail is fine, so's the > > newgroup. > > > > I suppose it's completely possible I'm running out of RAM and swap, but > > I'd expect to see something in /var/log/messages to that effect. So > > far, nothing. > > > > Recently I uppped NMBCLUSTERS to 4096, but it didn't seem to fix the > > problem. > > That was based on some notes in the FAQ. > > > > Even more recently (but haven't tested it yet) is that I upped my swap > > space > > to > > 256MB for 32MB of RAM. I killed off that nasty Win95 virus that was > > consuming all that disk space.... Nasty, nasty thing. > > > > Thanks in advance, > > > > Matt Gessner > > > > > > > > > > > > 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-questions" 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 27 11:38:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28122 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 11:38:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28082 for ; Thu, 27 Aug 1998 11:38:33 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id DAA12513; Fri, 28 Aug 1998 03:36:13 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id DAA01087; Fri, 28 Aug 1998 03:36:12 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id DAA20183; Fri, 28 Aug 1998 03:34:07 +0900 (JST) To: mike@smith.net.au Cc: pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Cc: max@wide.ad.jp Subject: Re: question From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Thu, 23 Jul 1998 14:34:30 -0700" <199807232134.OAA01224@dingo.cdrom.com> References: <199807232134.OAA01224@dingo.cdrom.com> X-Mailer: Mew version 1.92.4 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: <19980828033407Q.masafumi@aslm.rim.or.jp> Date: Fri, 28 Aug 1998 03:34:07 +0900 X-Dispatcher: imput version 971024 Lines: 68 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was going to respond to this message much earlier, but, I guess I was too lazy to start dealing with all the e-mails piled up while I was gone. By now, person who originally asked for some help probably have either solved the problem or given up on this, I guess. But I'm commenting on this just in case someone might be facing the same situation in future. >> I want to install 2.2.7 on one of my machines. I have to >> install it over a serial port because I am blind and need to >> read the screen during install. My speech software runs under >> dos. Thus, i must install it on my new machine from my dos >> box. I'm not sure how to install it on a machine im not >> physically at. > FreeBSD supports using the first serial port on your system as > the console port. If you don't have a video card in the > system, it will use the serial port instead. > Then you simply connect the serial port from the FreeBSD system > to your DOS system, and use a DOS terminal program to provide > you with a console. Additionally, if you can find someone to look at the screen just for a few seconds, you can change FreeBSD installer to use the serial console even your PC has video card. To do this, ask the sighted companion to let you know when there is a prompt as: Boot: appearing on the screen. From there, type in -h using the keyboard connecting to the machine you are installing FreeBSD. After that, every message goes to the serial port and you can use your screen reader and terminal emulator to do the rest. You may need to do a bit of customization to your screen reader to properly navigate around the menu, but it's not too complicated and if you have much experience dealing with various DOS applications, then you probably won't have much problem figuring out all the mess on the screen. :) There are several terminal emulators known to be work well with screen readers. I personally prefer MS-Kermit as I can remap the keyboard to emulate the meta-key of VT100 terminal. Because of very flexible key customization feature of the MS-Kermit, however, some screen readers might have problem with it especially when you want to issue review commands. Hope this helps. Now, as a blind FreeBSD user/developer, I'd like to include boot.config that has ``-D'' in our boot floppy so that we don't have to ask any sighted geek to look for the Boot: prompt in order to let the installer dump everything to the serial port. Cheers, Max ----------------------------------------------------------------------- Masafumi NAKANE, Keio Grad. School of Media and Governance E-Mail : max@wide.ad.jp / max@FreeBSD.ORG / max@w3.org [URL] : http://www.sfc.wide.ad.jp/~max/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 11:58:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02448 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 11:58: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 LAA02427 for ; Thu, 27 Aug 1998 11:58:48 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id LAA07177; Thu, 27 Aug 1998 11:57:47 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd007075; Thu Aug 27 11:57:36 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA26413; Thu, 27 Aug 1998 11:57:27 -0700 (MST) From: Terry Lambert Message-Id: <199808271857.LAA26413@usr01.primenet.com> Subject: Re: PCI devices To: mike@smith.net.au (Mike Smith) Date: Thu, 27 Aug 1998 18:57:27 +0000 (GMT) Cc: tlambert@primenet.com, tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG In-Reply-To: <199808262207.WAA00827@word.smith.net.au> from "Mike Smith" at Aug 26, 98 10:07:56 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 PnP OS follows the PnP specification, available from the Intel > > and Microsoft sites, for free download (use "site search" and > > look for "PnP specification"). > > > > A PnP OS is superior, since it will work on machines without a PnP > > BIOS. > > This is a fallacious conclusion. An OS which meets the criteria for > "PnP OS" in the preceeding discussion need not (and may not) work on a > system without a PnP BIOS. Then the OS sucks. An OS that does not know how to do card isolation will be unable, in the absence of a PnP BIOS, to utilize cards other than those whose POST's enable them as being potential boot devices. A nominally "PnP OS" that can't talk to "PnP cards", isn't very "PnP". This was a major flaw in the initial "PnP Windows 95" release. > As Tony pointed out, all the "PnP OS" setting does is determine whether > the BIOS or the OS will perform resource allocation for devices that > are not marked as being a potential boot path. Actually, According to "Plug and Play System Architecture", page 190, item 6: If the software must boot a non-PnP OS, it must enable (i.e., activate) every device in the system so that they are available for use by the OS and application programs. > > By default, PnP devices are required to be "disabled until enabled"; > > the bsearch mechanism can be implemented once in the OS; after that, > > it is no longer necessary to rely on the BIOS vendor "doing the right > > thing". > > This is also not correct, as a PnP OS can only operate properly in a > situation where resource availibility can be determined. In the PnP > BIOS case, this can be obtained from the BIOS. Without a PnP (actually > ESCD) BIOS, the OS must guess. No. 1) All legacy ISA device ROMs are required to begin on a 2K boundary in the range 0x000C0000 through 0x000EFFFF. The first and second bytes must be 0x55AA. The third byte is the number of 512 byte blocks in the ROM. The fourth is the actual entry point to the code. 2) All PnP device ROMS have the same requirements. But as of the fourth byte, there are 4 bytes of jump instruction to the actual initialization entrypoint. One can differentiate PnP devices from legacy ISA devices using this information. 3) On a non-PnP-BIOS machine, devices in the boot path will be enabled. Devices which are not boot devices are supposed to be disabled by default (the infamous "turn off PnP on the card" soloution to missing hardware). 4) The PnP OS can then: A) issues the key sequence to put all PnP devices to sleep. B) identify all EISA, MCA, PCI, and PCMCIA hardware, for the purpose of excluding it from ISA identification. C) Identify all remaining (legacy) ISA hardware. D) Perform PnP card isolation for configuration, and identify all possible locations for the cards. E) Perform closure over all possible configuration combinations for all cards. F) Configure the cards, as necessary. This is, in fact, the basis for the Microsoft claim that Windows 98 is better at autoconfiguration that most PnP BIOS's. In the presence of legacy cards unknown to the BIOS, Microsoft will not assign a resource used by a legacy card to a PnP card. This is what FreeBSD should be doing, as well. Note that this will be necessary for the OS to do on non-Intel hardware in most cases, since the OS must run an x86 interpreter to implement the card POST and other BIOS execution functions for Intel cards in these systems. In any case, there should be no more reason for an OS to guess than there would be for a BIOS to guess. Yes, this may mean allocating legacy cards PnP resources in the OS data store/Registry. 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 27 12:04:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03694 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 12:04:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03660 for ; Thu, 27 Aug 1998 12:04:43 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id VAA24468; Thu, 27 Aug 1998 21:03:27 +0200 (SAT) From: John Hay Message-Id: <199808271903.VAA24468@zibbi.mikom.csir.co.za> Subject: Re: FW: Q was on questions, now putting it here. In-Reply-To: <7283DE19D141D111AD0E00A0C95B1955CF12B6@mail2.aiinet.com> from "Gessner, Matt" at "Aug 27, 98 01:30:54 pm" To: mattg@aiinet.com (Gessner, Matt) Date: Thu, 27 Aug 1998 21:03:26 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG 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 You have run into FreeBSD's week spot. You ran out of mbufs. Try a value for NMBCLUSTERS that is your amount of RAM / 2048. Then at least you will hit some other limitation before you run out of mbufs. John -- John Hay -- John.Hay@mikom.csir.co.za > > > > ---------- > > From: Gessner, Matt > > Sent: Thursday, August 27, 1998 10:40 AM > > To: 'freebsd-questions@freebsd.org' > > Subject: FW: Q was on questions, now putting it here. > > > > I guess this died of lack of notice??? > > > > Can anyone suggest somewhere to at least start looking into making this > > work? > > Or is 2048 TCP connections too much to ask of this setup? > > > > TIA > > > > > ---------- > > > From: Gessner, Matt > > > Sent: Sunday, August 23, 1998 10:44 PM > > > To: 'hackers' > > > Subject: Q was on questions, now putting it here. > > > > > > Hi, all, > > > > > > I posted to comp.unix.bsd.freebsd.misc but nothing's come back... news > > > takes > > > a while. > > > > > > I'm running 2.2.7-RELEASE, and I've already changed my kernel a bit to > > > allow me to do a whole bunch of simultaneous connections, but I've > > > probably done something wrong, because it ain't working. > > > > > > Here's what I have: > > > > > > P5-166 Gateway > > > 32 MB RAM > > > 2 GB disk, 850MB belongs to FreeBSD, of which 100MB is swap. > > > PCI DEC Ethernet card > > > > > > Here's how I've mangled my poor kernel: > > > maxusers 128 > > > options CHILD_MAX=256 > > > options OPEN_MAX=2048 > > > options NMBCLUSTERS=4096 > > > > > > Here's how I've changed login.conf > > > > > > default and root both have unlimited child process and open file > > > counts. > > > > > > I've done a little poking around in param.c and don't see immediately > > > that I've violated any rules by setting these limits the way I have. > > > > > > When I type limits, I get the following info back: > > > > > > maxprocesses 2067 > > > openfiles 4136 > > > > > > But I can't find anything anywhere that talks about tuning the kernel > > > for doing this. > > > > > > What I need to do is be able to run lots of TCP connections, and I know > > > it can be done with FreeBSD. > > > > > > The connections are being made from FreeBSD to a proprietary board and > > > then to a Solaris machine. > > > > > > My end goal is to be able to bring up about 1024 TCP connections > > > outbound and route them back to the same box, for a total of 2048 > > > connections. > > > > > > Right now, I run 1024 connections to the other system, and what happens > > > is when the sockets are all connected, and the writes start to occur, > > > FreeBSD > > > just reboots the machine -- no messages anywhere. > > > > > > Have I really goofed up somewhere/something? Can anyone give me some > > > insight as to what MIGHT be happening here? E-mail is fine, so's the > > > newgroup. > > > > > > I suppose it's completely possible I'm running out of RAM and swap, but > > > I'd expect to see something in /var/log/messages to that effect. So > > > far, nothing. > > > > > > Recently I uppped NMBCLUSTERS to 4096, but it didn't seem to fix the > > > problem. > > > That was based on some notes in the FAQ. > > > > > > Even more recently (but haven't tested it yet) is that I upped my swap > > > space > > > to > > > 256MB for 32MB of RAM. I killed off that nasty Win95 virus that was > > > consuming all that disk space.... Nasty, nasty thing. > > > > > > Thanks in advance, > > > > > > Matt Gessner > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > 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 27 13:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22742 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 13:28:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts04-067.dublin.indigo.ie [194.125.148.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22668 for ; Thu, 27 Aug 1998 13:28:14 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id VAA01420; Thu, 27 Aug 1998 21:16:18 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808272016.VAA01420@indigo.ie> Date: Thu, 27 Aug 1998 21:16:13 +0000 In-Reply-To: <19980825154320.29030@follo.net>; Eivind Eklund 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: Eivind Eklund , rotel@indigo.ie, dyson@iquest.net, joelh@gnu.org Subject: Re: I want to break binary compatibility. Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 25, 3:43pm, Eivind Eklund wrote: } Subject: Re: I want to break binary compatibility. > On Mon, Aug 24, 1998 at 10:36:24PM +0000, Niall Smart wrote: > > On Aug 24, 1:20am, "John S. Dyson" wrote: > > > Try modifying your system so that one of the flags bits is required to > > > run a program. It would the require both the flags bit and the executable > > > bit. Make sure the system cannot allow anyone but root set the chosen > > > flags bit. Maybe you could use the immutable flag, for this so that you > > > get theoretical immutability along with the ability to run code. You > > > might want to relax the restriction for root, but maybe not (depending > > > on how your admin scheme is setup.) > > > > None of these hacks achieve security. You, of all people, should > > know better. The original poster should figure out how they are > > breaking in and close the hole, obfuscation schemes like the above > > are a waste of time. > > As I see it, this is not an obfuscation scheme - it is a security > layer blocking anybody but root from creating runnable programs (or, > if you are running at a higher secure-level, block anybody from > creating runnable programs). You're basically trying to disable chmod +x for anyone but root, but to do that properly you have to audit every program the user has permission to execute and each library which those programs use. It's _far_ easier to understand how they are getting in. > The use of mumbled syscalls is basically a form of included > password/cryptgraphic key, so it is an obfuscation scheme - just like > using passwords is an obfuscation scheme. > > If there are no readable excutables or header files (and there had > better not be), and the syscalls are totally scrambled, you have a [snip] > (1315 bits) is actually a pretty respectable number, and should > give you plenty time to detect that the attacker is testing syscalls You're talking about the process supplying some kind of a key to the OS as part of the syscall? This is somewhat more difficult to get around, perhaps 2 or 3 days worth of work needed, since when you find the buffer overflow you also need to find a way to get the code to communicate the key to you, which of course involves a syscall. Hardly secure though, especially since the size of the password is irrelevant once its large enough to withstand brute force. > For a generally deployed system, obscurity is not protection. For a > single installation, obscurity is protection, and can very often be a > valid line of defence. Sometimes, yes, I think l0pht is an example of this. But it is not the answer in this case, since the original poster has/is being hacked, turning to obscurity to fix the problem is the wrong approach. If l0pht got hacked do you think they would try and find out how it happened or would they turn up the obscurity level? Regards, 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 Thu Aug 27 13:39:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24655 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 13:39: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 NAA24623 for ; Thu, 27 Aug 1998 13:39: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 WAA04487; Thu, 27 Aug 1998 22:35:05 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id WAA02606; Thu, 27 Aug 1998 22:06:03 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808272006.WAA02606@semyam.dinoco.de> To: zhihuizhang cc: hackers , seggers@semyam.dinoco.de Subject: Re: FFS questions In-reply-to: Your message of "Thu, 27 Aug 1998 12:20:14 EDT." Date: Thu, 27 Aug 1998 22:06:03 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The comment says it is the number of cylinders per *cycle* in position > table. What does the "cycle" mean? Basically the position table is That I don't know. My guess would be the number of cylinders we can seek during one rotation. > transfer request for exactly that block. But how can we measure the > time it takes CPU (time-sharing by processes) to service an interrupt > and initiate a new I/O? Is the disk always moving around at constant As I understand it one just experiments and finds out this way. > and initiate a new I/O? Is the disk always moving around at constant > speed? When does the disk generate an interrupt? After it finish DMA a > block or a sequence of contiguous blocks specified by the CPU's request? As the rotational delay table is not used anymore these questions are of no importance nowadays. One has to rely on the drive being intel- ligent enough to do the right thing nowadays. With varying number of sectors in different zones which one might not even know the para- meters of it's asking a bit much to optimize for that in the OS. And then one still has to take into account caches, too. >From the article on disk subsystem performance in /usr/share/doc I conclude at that time there were already intelligent drives as we know them now for IDE and SCSI. They just present as a logical view of what might be very different physically. The drive itself decides how it orders the blocks, how to access them and so on. It is free to vary the the rotational speed at will or with a similar effect to vary the data rate to get more sectors on the outer cylinders. On such a drive one can't assume anything about the physical characteristics. If one is lucky one can measure some things and take advantage of them, of course. The other mentioned type is a Fujitsu drive which sounds pretty much like a dump MFM or RLL drive of that time. A certain number of cylinders, a number of heads and a fixed number of sectors per track. I didn't read anything about tricks with varying the speed or data rate at that time for such drives. For these things like the rotation block lists were invented. If these drives were similar to the ones used in PCs the part which does the interrupting is on the controller, not the drive. I'd expect it to send one when a command has completed - whatever the command was. A multiblock transfer - if supported by the controller - better should do the same but even if not one can ignore the extra ones quite easily. 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 Thu Aug 27 13:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28005 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 13:57:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27982 for ; Thu, 27 Aug 1998 13:57:35 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id WAA02854; Thu, 27 Aug 1998 22:47:32 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA05167; Thu, 27 Aug 1998 22:47:31 +0200 (MET DST) Message-ID: <19980827224731.61006@follo.net> Date: Thu, 27 Aug 1998 22:47:31 +0200 From: Eivind Eklund To: rotel@indigo.ie, dyson@iquest.net, joelh@gnu.org Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. References: <19980825154320.29030@follo.net> <199808272016.VAA01420@indigo.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808272016.VAA01420@indigo.ie>; from Niall Smart on Thu, Aug 27, 1998 at 09:16:13PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 27, 1998 at 09:16:13PM +0000, Niall Smart wrote: > On Aug 25, 3:43pm, Eivind Eklund wrote: > } Subject: Re: I want to break binary compatibility. > > On Mon, Aug 24, 1998 at 10:36:24PM +0000, Niall Smart wrote: > > > On Aug 24, 1:20am, "John S. Dyson" wrote: > > > > Try modifying your system so that one of the flags bits is required to > > > > run a program. It would the require both the flags bit and the executable > > > > bit. Make sure the system cannot allow anyone but root set the chosen > > > > flags bit. Maybe you could use the immutable flag, for this so that you > > > > get theoretical immutability along with the ability to run code. You > > > > might want to relax the restriction for root, but maybe not (depending > > > > on how your admin scheme is setup.) > > > > > > None of these hacks achieve security. You, of all people, should > > > know better. The original poster should figure out how they are > > > breaking in and close the hole, obfuscation schemes like the above > > > are a waste of time. > > > > As I see it, this is not an obfuscation scheme - it is a security > > layer blocking anybody but root from creating runnable programs (or, > > if you are running at a higher secure-level, block anybody from > > creating runnable programs). > > You're basically trying to disable chmod +x for anyone but root, > but to do that properly you have to audit every program the user > has permission to execute and each library which those programs > use. It's _far_ easier to understand how they are getting in. Eh? What? You don't have to audit anything - you just add a check for this in the places in the kernel where you start an executable. And we were talking of a new flag, not a change to the mode structure... This effectively deny the user the possibility of creating new executables; if you also limit the possibility of setting the flag to only be at low securelevel, you have removed the possibility of creating new executables even with root access. Clearly a security win in my book, and has _nothing_ to do with obscurity. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 14:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02081 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 14:17:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts04-067.dublin.indigo.ie [194.125.148.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02061 for ; Thu, 27 Aug 1998 14:17:04 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01710; Thu, 27 Aug 1998 22:09:40 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808272109.WAA01710@indigo.ie> Date: Thu, 27 Aug 1998 22:09:40 +0000 In-Reply-To: <19980827224731.61006@follo.net>; Eivind Eklund 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: Eivind Eklund , rotel@indigo.ie, dyson@iquest.net, joelh@gnu.org Subject: Re: I want to break binary compatibility. Cc: imp@village.org, dkelly@hiwaay.net, rabtter@aye.net, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > You're basically trying to disable chmod +x for anyone but root, > > but to do that properly you have to audit every program the user > > has permission to execute and each library which those programs > > use. It's _far_ easier to understand how they are getting in. > > Eh? What? You don't have to audit anything - you just add a check > for this in the places in the kernel where you start an executable. > And we were talking of a new flag, not a change to the mode > structure... Sure you do, you want to let them run ncftp? Well ncftp has a buffer overflow in how it reads its configuration file. How are you going to prevent them exploiting that? 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 Thu Aug 27 14:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06337 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 14:42:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06239 for ; Thu, 27 Aug 1998 14:42:20 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA08456; Thu, 27 Aug 1998 14:41:08 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35E5D274.DFF743C5@dal.net> Date: Thu, 27 Aug 1998 14:41:08 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0823 i386) MIME-Version: 1.0 To: Joe McGuckin CC: hackers@FreeBSD.ORG Subject: Re: 2.2.7 kernel panic - out of map entries References: <199808262129.OAA13599@monk.via.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe McGuckin wrote: > > Several times daily, I get the same panic: > Out of map entries for kernel Right off hand I'd say that you should increase 'maxusers' in the kernel config file. If you need help with that check out the documentation section at http://www.freebsd.org/ Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** When you don't know where you're going, every road will take you there. - Yiddish Proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 14:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08955 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 14:56:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA08902 for ; Thu, 27 Aug 1998 14:56:07 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 26368 invoked by uid 3759); 27 Aug 1998 21:56:23 -0000 Date: Thu, 27 Aug 1998 17:56:23 -0400 (EDT) From: "B. Richardson" To: Jamie Bowden cc: dyson@iquest.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. 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 I don't think the number of virtual domains is important, its how much traffic they generate. We have a few sites that really get pounded. At peak times there were 1200 webserver processes running (try that in 64 megs of ram) and available memory was down to 32 mb (out of 384). I think a big difference is that we were using netscape 2.0 enterprise server with uses HTTP/1.0 -- which must fork a process per connection. Our apache uses HTTP/1.1 which pipelines requests (with help of the client) making for much lower resource usage on the part of the webserver. We ran the gamut on the tunables -- we were just flat running out of RAM. - Barrett Richardson rabtter@orion.aye.net On Thu, 27 Aug 1998, Jamie Bowden wrote: > > > I have over 200 virtual domains running off an Indy R4600 @ 133mhz w/ 64M. > I don't have any problems with this. Sounds like you need to do some > tuning somewhere. Not that FreeBSD isn't capable, it is very capable, and > very good at this. My point is that your SGI should be giving you alot > better performance than it is. I have found that the single largest > botleneck for apache on my SGI's here is the number of file descriptors > it's allowed to have open. The system default is fairly low (200 per > process, 2500 total), and really should be upped no matter what you are > using the machine for. Our Oracle, mail, and news servers all benefited > from upping this. I doubt this is relevant only to Irix. > > 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 Thu Aug 27 14:58:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09286 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 14:58:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dirc.bris.ac.uk (dirc.bris.ac.uk [137.222.10.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA09239 for ; Thu, 27 Aug 1998 14:57:44 -0700 (PDT) (envelope-from Tim.Borgeaud@bristol.ac.uk) Received: from zeus.bris.ac.uk by dirc.bris.ac.uk with SMTP-PRIV (PP) with ESMTP; Thu, 27 Aug 1998 22:56:49 +0100 Received: (from phtlb@localhost) by zeus.bris.ac.uk (8.8.8/8.8.7) id WAA02681 for freebsd-hackers@FreeBSD.ORG; Thu, 27 Aug 1998 22:54:50 +0100 (BST) From: Tim Borgeaud Message-Id: <199808272154.WAA02681@zeus.bris.ac.uk> Subject: Why is my code failing with SIGFPE? To: freebsd-hackers@FreeBSD.ORG Date: Thu, 27 Aug 1998 22:54:50 +0100 (BST) X-Mailer: ELM [version 2.4 PL21] 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 Sorry if this is bit off topic but I think someone reading the list can probably help me. I have some C-code which fails with floating point exceptions (SIGFPE errors). Code compiles cleanly, although I am not using any additional options to gcc. I am stumped as to the cause of these errors. Depending on where I put print statements in the code (for debugging purposes) it fails at different points. The code makes fairly heavy use of the CPU and is recursive. On the fourth call of the recursive function the code fails with SIGFPE, sometimes in my code without any reason that I can find, but also commonly in __dtoa (called during printf of a floating point number). I have carefully gone through my code, sections of which seemed to be working perfectly on their own. I cannot seem to find anything wrong. I can supply all or parts of the code that I am trying to run if anyone is interested. I was hoping that someone may have come across this kind of thing before. The code has also been compiled using djgpp under msdos and has the same problem. Two machines (Pentium and Pentium MMX) produce the same results. I have tried to use gdb, but because I have never used it before it didn't help very much. All I found was that some of the floating point variable were scrambled after the failure (eg some ridculous number x10^230 or something). Many thanks Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 15:03:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10342 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:03:23 -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 PAA10275 for ; Thu, 27 Aug 1998 15:02:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00519; Thu, 27 Aug 1998 14:57:27 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271457.OAA00519@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Thu, 27 Aug 1998 18:57:27 GMT." <199808271857.LAA26413@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 14:57:26 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > A PnP OS follows the PnP specification, available from the Intel > > > and Microsoft sites, for free download (use "site search" and > > > look for "PnP specification"). > > > > > > A PnP OS is superior, since it will work on machines without a PnP > > > BIOS. > > > > This is a fallacious conclusion. An OS which meets the criteria for > > "PnP OS" in the preceeding discussion need not (and may not) work on a > > system without a PnP BIOS. > > Then the OS sucks. Or perhaps it's just designed only to run on PnP systems. > An OS that does not know how to do card isolation will be unable, > in the absence of a PnP BIOS, to utilize cards other than those > whose POST's enable them as being potential boot devices. > > A nominally "PnP OS" that can't talk to "PnP cards", isn't very "PnP". It may not support ISA PnP. Please don't call them "PnP cards"; PCI cards are PnP cards, PCCARD cards are PnP cards. > > As Tony pointed out, all the "PnP OS" setting does is determine whether > > the BIOS or the OS will perform resource allocation for devices that > > are not marked as being a potential boot path. > > Actually, According to "Plug and Play System Architecture", page 190, > item 6: > > If the software must boot a non-PnP OS, it must enable (i.e., > activate) every device in the system so that they are available > for use by the OS and application programs. Which is exactly what I said. > > > By default, PnP devices are required to be "disabled until enabled"; > > > the bsearch mechanism can be implemented once in the OS; after that, > > > it is no longer necessary to rely on the BIOS vendor "doing the right > > > thing". > > > > This is also not correct, as a PnP OS can only operate properly in a > > situation where resource availibility can be determined. In the PnP > > BIOS case, this can be obtained from the BIOS. Without a PnP (actually > > ESCD) BIOS, the OS must guess. > > No. Yes. Read that again: "Yes". The OS may do a good job of guessing, but that's all it can do. > 1) All legacy ISA device ROMs are required to begin on a 2K > boundary in the range 0x000C0000 through 0x000EFFFF. The > first and second bytes must be 0x55AA. The third byte is > the number of 512 byte blocks in the ROM. The fourth is > the actual entry point to the code. This is almost irrelevant. > 2) All PnP device ROMS have the same requirements. But as of > the fourth byte, there are 4 bytes of jump instruction to > the actual initialization entrypoint. One can differentiate > PnP devices from legacy ISA devices using this information. So? You are again abusing "PnP" to mean "ISA PnP". > 3) On a non-PnP-BIOS machine, devices in the boot path will be > enabled. Devices which are not boot devices are supposed to > be disabled by default (the infamous "turn off PnP on the card" > soloution to missing hardware). Your phrasing is ambiguous here. The ISA PnP spec requires devices which *may* form part of the boot path to be enabled following reset, with "default" configurations. "Turning off PnP on the card" will make a non-boot-path device visible, yes. > 4) The PnP OS can then: > > A) issues the key sequence to put all PnP devices to > sleep. > B) identify all EISA, MCA, PCI, and PCMCIA hardware, for > the purpose of excluding it from ISA identification. > C) Identify all remaining (legacy) ISA hardware. It's arguably erroneous to perform this at this stage. It would be more correct to attempt to locate *resources* claimed by such devices. > D) Perform PnP card isolation for configuration, and > identify all possible locations for the cards. > E) Perform closure over all possible configuration > combinations for all cards. > F) Configure the cards, as necessary. > > This is, in fact, the basis for the Microsoft claim that Windows 98 > is better at autoconfiguration that most PnP BIOS's. In the presence > of legacy cards unknown to the BIOS, Microsoft will not assign a > resource used by a legacy card to a PnP card. Only if the operating system is capable of locating the device, and only if the user has not correctly informed the BIOS of the resources consumed by said device. If the user has behaved appropriately, the information is available both to the BIOS and the operating system via the ESCD data. > Note that this will be necessary for the OS to do on non-Intel > hardware in most cases, since the OS must run an x86 interpreter > to implement the card POST and other BIOS execution functions > for Intel cards in these systems. The number of ISA PnP adapters with onboard BIOS code is so low that such emulation is virtually pointless. There is one specific case (video adapters) which is already well covered on at least some platforms (eg. the alpha console ROM contains an x86 emulator). > In any case, there should be no more reason for an OS to guess than > there would be for a BIOS to guess. In the absence of ESCD information, the OS must guess as to the location of system peripherals. It can only detect those peripherals that it already knows about, ie. it must guess. In the presence of (correct) ESCD information, the BIOS and the operating system both have the same data, and modulo bugs in the BIOS implementation both can do the same work. -- \\ 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 27 15:04:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10546 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:04:01 -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 PAA10488 for ; Thu, 27 Aug 1998 15:03:48 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA23272; Thu, 27 Aug 1998 15:02:53 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd023229; Thu Aug 27 15:02:49 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA27570; Thu, 27 Aug 1998 15:02:43 -0700 (MST) From: Terry Lambert Message-Id: <199808272202.PAA27570@usr02.primenet.com> Subject: Re: Imap4 To: lyndon@esys.ca (Lyndon Nerenberg) Date: Thu, 27 Aug 1998 22:02:42 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: from "Lyndon Nerenberg" at Aug 26, 98 10:51:53 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 wire protocol is similar to LISP: lots of silly parenthesis. > > With lots of lists of things flowing around. What's wrong with parens? If it > works for Lisp ... :-) You cut out the part where I told you what was wrong with it: it's much more complex than it should be to build a parser for the thing. > > Many ISPs dislike IMAP4 because it takes a lot of storage, and only > > gives back increased modem usage and wire traffic in return for > > the extra storage it consumes -- wait a minute, I get why they > > don't like it... ;-). > > You mean your IMAP server doesn't implement quotas? Both the U of W and the Cyrus code support quota. Quotas are not the point; the point is that if you store information on the server, there is less space available on the server for other tasks. This is rather like a spammer asking "So what's wrong with me putting SPAM in your mail queue? I'm not running you out of space...". There are quotas, and then there are expectation values for amount of usage. The expectation values are less than the quota in most cases, but in the IMAP4 case, the protocol strongly encourages you to take up space on the server. > Disk is cheap, and the security of having the mail backed up is a big win. Perhaps you can convince people to pay an extra $5/month for this security... ISP disk costs are amortized across customers. > > One of the most annoying this is that, without a full IMSP implementation, > > of which there is not one of, there is no provision for fanning out > > envelope information into sub-mailboxes (which would make IMAP4 > > useful for virtual domain hosting, where POP3 fails to retain > > envelope information because of a stupid agrument between Eric Allman > > and Eric Raymond about "who is the MTA"), nor is there provision for > > client specification of server side filtering rules (which would make > > it otherwise more useful than POP3). > > I'm not sure how IMSP helps with virtual domains. It allows for client mobility (the standard reason IMAP4 is sited as being useful) and it allows the setting of "post" ACL's, which could prohibit mail from specific sources. In addition, there are drafts for extensions to support client management of server filter lists; this draft was specifically what I was referring to, where you would take the envelope-to information (passed the Cyrus "deliver" command on the command line) and use it to select a subfolder name to implement virtual domain fan-out using envelope information, instead of having to second-guess it and attempt to reconstruct it from header contents. > As for filtering, SIEVE is getting close to > being reality (there are three prototypes running that I'm aware of). References, please... > > Basically, it's an interesting "also ran" that won't displace POP3 > > any time soon until its flaws are noted and corrected. > > I'm going to take great pleasure in quoting that back to you in a couple of > years :-) Please do... > My prediction is that IMAP is going to displace the majority of POP3 > implementations over the next 2-3 years. POP3 just can't handle the mobile > community that represents more and more of the e-mail users out there today. ...So long as you don't mind me quoting this... 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 Thu Aug 27 15:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12360 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:12:05 -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 PAA12288 for ; Thu, 27 Aug 1998 15:11:43 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA25475; Thu, 27 Aug 1998 15:10:48 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd025433; Thu Aug 27 15:10:42 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA27928; Thu, 27 Aug 1998 15:10:33 -0700 (MST) From: Terry Lambert Message-Id: <199808272210.PAA27928@usr02.primenet.com> Subject: Re: Warning: Change to netatalk's file name handling To: stb@hanse.de (Stefan Bethke) Date: Thu, 27 Aug 1998 22:10:33 +0000 (GMT) Cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Stefan Bethke" at Aug 27, 98 00:56:38 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 > > Netatalk seems like the wrong place to modify behavior to solve this > > problem, which is a display problem, not an encoding problem. > > Where is the encoding defined for character values in the ranges between > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? ISO 8859? > If you were right, it would be OK for afpd to store all chars literally. > While this does work, it is definitly awkward to work with in the shell, > and possibly so together with other applications as Samba as well. Its not > merely an display issue; its an interoperability issue. I feel that too > many things expect file names to confine to printable ascii, and unless > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > untouched). Per interoperability: This presumes, incorrectly, that Mac's support the same idiotic idea of code pages as SAMBA must. > It won't change anything to the worse; the only problem is that existing > files with file names containing control characters (custom icons on folders > being the single source of such name probably) will stop working and will > need manual assistance from an operator. It will break a number of things. It already breaks the file name length limitation in SAMBA. Duplicating this break into Appletalk is, IMO, a bad idea. If you are going to push this hard, you should consider Internataional representation ofile names by client locale, and how it is already handled. Novell servers are another case where the server assumes all clients exist in a given locale; this would be a mistake to buy into... 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 27 15:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14510 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:21: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 PAA14404 for ; Thu, 27 Aug 1998 15:21:30 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA05376; Thu, 27 Aug 1998 15:20:37 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd005343; Thu Aug 27 15:20:35 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA28457; Thu, 27 Aug 1998 15:20:32 -0700 (MST) From: Terry Lambert Message-Id: <199808272220.PAA28457@usr02.primenet.com> Subject: Re: Warning: Change to netatalk's file name handling To: stb@hanse.de (Stefan Bethke) Date: Thu, 27 Aug 1998 22:20:32 +0000 (GMT) Cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Stefan Bethke" at Aug 27, 98 03:19: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 > AFAIK, there is no character set or encoding defined for file names in > FreeBSD, in UNIX, or in POSIX. The only implicit definition is plain ASCII. Actually, the definition is "8 bit clean, 0x00-0x7f US ASCII"; this is sufficient for ISO 8859-X, Shift-JIS, EUC-JP, BIG5, EUC-TW, GB, EUC-R, ISO-2022-KR, and KOI8-R representations. > Even if we were to translate from the Mac enconding to (say) ISO-8859-1, > this would loose some of the chars legal in Mac filenames, causing grief to > the typical unsuspecting graphics designer. Or you could just leave it alone, as 8-bit clean, and allow the existing ISO 2022 character set selection mechanisms in wide use to continue functiong normally. > So we need afpd to confine to ASCII, and, as I would suggest, to printable > ASCII, as this will make most peoples' live easier (for ASCII, byte values > from \0x00 to \0x1F and \0x7F do not produce a glyph, so it is practically > useless to store them as-is). You can not store 0x00 in the UNIX namespace. I believe this is a volume seperator in HFS; it can be replaces with ":" in translation. Specifically, there are exactly two characters you can not use in-band in the HPFS namespace, and exactly two characters you can not use in the FFS namespace (0x00 and "/"), and the translation is natural and obvious. > > [ On the InterJet, for example, you can have it set to Japanese mode, > > and shared files appear with the same name under AppleTalk and > > Windows, ie, Samba and Netatalk use the same character encoding. ] > > That is definitly cool. I hope Julian can provide me with either the patches > or the contact, so I can (at least) evaluate and turn down the patches :-) Jeremy Allison of the SAMBA team did the code. Contact him directly at SGI. 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 27 15:30:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16316 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:30:10 -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 PAA16233 for ; Thu, 27 Aug 1998 15:29:41 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA03569; Thu, 27 Aug 1998 15:28:42 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd003546; Thu Aug 27 15:28:38 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA28819; Thu, 27 Aug 1998 15:28:28 -0700 (MST) From: Terry Lambert Message-Id: <199808272228.PAA28819@usr02.primenet.com> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] To: nate@mt.sri.com (Nate Williams) Date: Thu, 27 Aug 1998 22:28:28 +0000 (GMT) Cc: tlambert@primenet.com, wilko@yedi.iaf.nl, joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG In-Reply-To: <199808271512.JAA08751@mt.sri.com> from "Nate Williams" at Aug 27, 98 09:12:16 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 > You're confused. See above. There was no such thing as a 1742B. > > > I'm also pretty sure the "B" comes from the EISA configuration > > capability that I had to read the serial number to the Adaptec people > > so they could tell me if the card supported it, whereby I was able to > > configure a non-standard translation mode to support larger drives > > than would otherwise be possible on a 1742/1742A. > > That was supported on *all* boards that I'm aware of. At least it was > on the 1740 that I had oh so long ago. :) I had to get seperate (newer) setup disks. The 1740-ness of the controller was not in question; whether or not the EISA CMOS supported the alternate translation mode was what was. I'm sure I bitched about this at great length back in 1993. 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 27 15:31:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16625 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:31:51 -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 PAA16590 for ; Thu, 27 Aug 1998 15:31:29 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA15135; Thu, 27 Aug 1998 15:30:36 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd015110; Thu Aug 27 15:30:31 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA28894; Thu, 27 Aug 1998 15:30:26 -0700 (MST) From: Terry Lambert Message-Id: <199808272230.PAA28894@usr02.primenet.com> Subject: Re: Adaptec 1542i Performance on -stable [was Re: SCSI Controller] To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Thu, 27 Aug 1998 22:30:26 +0000 (GMT) Cc: tlambert@primenet.com, joelh@gnu.org, dakott@alpha.delta.edu, hackers@FreeBSD.ORG In-Reply-To: <199808271514.RAA17496@yedi.iaf.nl> from "Wilko Bulte" at Aug 27, 98 05:14:48 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 > Hm. You might have a one-off prototype or whatever. I don't think so... > > I'm also pretty sure the "B" comes from the EISA configuration capability > > that I had to read the serial number to the Adaptec people so they could > > tell me if the card supported it, whereby I was able to configure a > > non-standard translation mode to support larger drives than would otherwise > > be possible on a 1742/1742A. > > You could check the EISA config string, a 1740 is an ADP0000 and a > 1740A is a ADP0001 if I remember well. For the 1740 there are multiple > sets of firmware/BIOS around, the newer ones have different translations > so you can acommodate a big drive. I will look for this. I'm pretty sure it was a firmware issue. 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 27 15:35:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17111 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:35:22 -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 PAA17086 for ; Thu, 27 Aug 1998 15:35:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00757; Thu, 27 Aug 1998 15:32:09 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271532.PAA00757@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: hackers Subject: Re: FFS questions In-reply-to: Your message of "Thu, 27 Aug 1998 12:20:14 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 15:32:09 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am reading the source code in fs.h and the parameter fs_cpc confuses me. > > The comment says it is the number of cylinders per *cycle* in position > table. What does the "cycle" mean? It's the size of the rotational offset table. Starting from position 0 on the disk, there are N cycles of fastest-next-block locations as you move across the disk. You only need to store one cycle in the offset table. The position table and all the optimisations related to second-guessing the behaviour of the disk are now pessimisations in most cases, and should be eliminated entirely. Doing this is quite a job of work, and at the moment we simply short-circuit them. -- \\ 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 27 15:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17477 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:37:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17413 for ; Thu, 27 Aug 1998 15:37:15 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA21113; Thu, 27 Aug 1998 23:43:48 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA03427; Fri, 28 Aug 1998 00:37:22 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA27011; Fri, 28 Aug 1998 00:36:04 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Fri, 28 Aug 1998 00:36:04 +0200 (CEST) From: Stefan Bethke To: Terry Lambert cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808272210.PAA27928@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 Thu, 27 Aug 1998, Terry Lambert wrote: > > > Netatalk seems like the wrong place to modify behavior to solve this > > > problem, which is a display problem, not an encoding problem. > > > > Where is the encoding defined for character values in the ranges between > > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > ISO 8859? Is this a standardized encoding for POSIX file names, or just a convention? If it only is a convention, what will non-latin script users think about it? How do we discriminate between different 8859 encodings? (Yeah, I see your point about "locales".) > > If you were right, it would be OK for afpd to store all chars literally. > > While this does work, it is definitly awkward to work with in the shell, > > and possibly so together with other applications as Samba as well. Its not > > merely an display issue; its an interoperability issue. I feel that too > > many things expect file names to confine to printable ascii, and unless > > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > > untouched). > > Per interoperability: This presumes, incorrectly, that Mac's support > the same idiotic idea of code pages as SAMBA must. Macs, in this sense, use a single "code page." I believe there is an escape mechanism to change the encoding to non-latin scripts, but I will have to look that up in Inside Mac. For AFP 2.1 (which netatalk claims to support to the extent the Macs use it), there is a single encoding defined, without any escape mechanism. > > It won't change anything to the worse; the only problem is that existing > > files with file names containing control characters (custom icons on folders > > being the single source of such name probably) will stop working and will > > need manual assistance from an operator. > > It will break a number of things. It already breaks the file name > length limitation in SAMBA. Duplicating this break into Appletalk is, > IMO, a bad idea. I don't know much about SMB/CIFS/Samba. What is the filename length limit (as opposed, possibly, to the pathname limit)? AFP has a filename length limitation to 31 bytes/chars. All Unix-based AFP servers I know of choose to drop files with longer names. Also, at least two commercial products use the same mechanism for escaping non-ASCII chars. > If you are going to push this hard, you should consider Internataional > representation ofile names by client locale, and how it is already > handled. Would you mind to point me to any information shedding light on standardisation efforts for file name representation? In terms of "locale", this would mean that "Mac" or "AFP" would be it's own locale in terms of file name character encoding? After all, I see three possible ways: - improve interoperability by confining to printable ASCII (or ISO-8859-1, or...) and not escaping other glyphs, thus breaking AFP conformance; - escaping all glyphs (or rather their encoding) in a way that preserves the full AFP filename encoding space (for filenames, this is 0x01 to 0xff, with ":" being illegal as it is the path delimiter), but using printable ASCII where possible (this is, I believe, what netatalk tries to do, but doesn't, due to a stupid bug). - translate the AFP filename encoding space into some larger glyph encoding space, such as Unicode, or, more specifically, UTF-8. The last one probably is the way to go, but this would require (at least to me) some testimonial that Unicode in general and UTF-8 in particular is the way to go for file names in FreeBSD. This of course would probably start other interop problems with NFS and alike, and it would require samba to deal with CP bogosities in its own right instead of putting it in the face of every other app. > Novell servers are another case where the server assumes all clients > exist in a given locale; this would be a mistake to buy into... Yep. Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 15:49:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19726 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:49:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19709 for ; Thu, 27 Aug 1998 15:49:19 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA21242; Thu, 27 Aug 1998 23:55:53 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA03676; Fri, 28 Aug 1998 00:49:28 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA27314; Fri, 28 Aug 1998 00:48:11 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Fri, 28 Aug 1998 00:48:10 +0200 (CEST) From: Stefan Bethke To: Terry Lambert cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808272220.PAA28457@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 Thu, 27 Aug 1998, Terry Lambert wrote: > > AFAIK, there is no character set or encoding defined for file names in > > FreeBSD, in UNIX, or in POSIX. The only implicit definition is plain ASCII. > > Actually, the definition is "8 bit clean, 0x00-0x7f US ASCII"; this is > sufficient for ISO 8859-X, Shift-JIS, EUC-JP, BIG5, EUC-TW, GB, EUC-R, > ISO-2022-KR, and KOI8-R representations. Yes. The questions isn't whether UFS allows for filenames with byte values in the range 0x01 to 0xFF, but rather how to interpret them. > > Even if we were to translate from the Mac enconding to (say) ISO-8859-1, > > this would loose some of the chars legal in Mac filenames, causing grief to > > the typical unsuspecting graphics designer. > > Or you could just leave it alone, as 8-bit clean, and allow the > existing ISO 2022 character set selection mechanisms in wide use to > continue functiong normally. I'm not particular aquainted with ISO 2022, so I don't really get what this would buy me in terms of interoperability of existing apps. > > So we need afpd to confine to ASCII, and, as I would suggest, to printable > > ASCII, as this will make most peoples' live easier (for ASCII, byte values > > from \0x00 to \0x1F and \0x7F do not produce a glyph, so it is practically > > useless to store them as-is). > > You can not store 0x00 in the UNIX namespace. > > I believe this is a volume seperator in HFS; it can be replaces with > ":" in translation. > > Specifically, there are exactly two characters you can not use in-band > in the HPFS namespace, and exactly two characters you can not use in > the FFS namespace (0x00 and "/"), and the translation is natural and > obvious. The current escape mechanism apfd uses escapes "/" and 0x80 to 0xFF. I propose to change this to "/", 0x01 to 0x1F and 0x7F to 0xFF. The escape mechanism map the sequence ":xx" to each of the escaped codes. Because ":" is illegal in AFP filenames (its the path seperator), the reverse operation is indeed natural. > > > [ On the InterJet, for example, you can have it set to Japanese mode, > > > and shared files appear with the same name under AppleTalk and > > > Windows, ie, Samba and Netatalk use the same character encoding. ] > > > > That is definitly cool. I hope Julian can provide me with either the > > patches or the contact, so I can (at least) evaluate and turn down the > > patches :-) > > Jeremy Allison of the SAMBA team did the code. Contact him directly > at SGI. Jeremy seems to have switched addresses. Julian was kind enought to send me the patches; however, I don't feel to add code page support to netatalk. Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 17:13:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03452 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 17:13:46 -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 RAA03393 for ; Thu, 27 Aug 1998 17:13:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA16359; Thu, 27 Aug 1998 17:11:43 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdd16354; Fri Aug 28 00:11:40 1998 Date: Thu, 27 Aug 1998 17:11:37 -0700 (PDT) From: Julian Elischer To: Terry Lambert cc: Stefan Bethke , archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808272220.PAA28457@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 > > Jeremy Allison of the SAMBA team did the code. Contact him directly > at SGI. I've supplied the patches and jeremy's address (jallison@engr.sci.com) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 17:27:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05696 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 17:27:06 -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 RAA05568 for ; Thu, 27 Aug 1998 17:26:23 -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 RAA02540; Thu, 27 Aug 1998 17:06:21 -0700 (PDT) Message-Id: <199808280006.RAA02540@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 , tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 27 Aug 1998 17:06:20 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998 14:57:26 +0000 Mike Smith wrote: > > Then the OS sucks. > > Or perhaps it's just designed only to run on PnP systems. ...you guys really need to make a distinction between "PnP" (e.g. ISA PnP) and direct configuration (e.g. what EISA, PCI, PCMCIA, and CardBus has). > > A nominally "PnP OS" that can't talk to "PnP cards", isn't very "PnP". > > It may not support ISA PnP. Please don't call them "PnP cards"; PCI > cards are PnP cards, PCCARD cards are PnP cards. Not really.. the bus they live on uses direct configuration, as opposed to indirect configuration (e.g. ISA, VME). That is to say, the devices are self-describing in a well-known way, and it is possible to determine where the device is mapped. Indirect configuration requires hints to look for devices. PnP is a hack to try and make ISA have direct configuration. It's pure evil, but I'm sure everyone here realizes that already. The new "PnP OS" BIOS option is a total crock. Basically, what it does is, if set, doesn't do ANY configuration of ISA PnP or PCI, which, at least in the context of PCI, is TOTALLY BROKEN. The PCI spec is clear that it is the system firmware's job to configure the PCI bus (i.e. map all of the devices and route their interrupts). It is unfortunate that BIOS vendors are overloading the term "PnP" to apply to PCI as well. To restate that: PCI SHOULD ALWAYS BE CONFIGURED BY THE BIOS (firmware) REGARDLESS OF THE SETTING OF "PnP OS". Sorry to shout, but this is a major issue, and something I'm quite miffed at vendors about for botching royally. NetBSD's PnP code doesn't require the presence of a PnP BIOS. It performs the PnP configuation process on its own. I.e. it is a "PnP OS". However, because of the BIOS's broken notion of "PnP", NetBSD still requires that that option be set to FALSE so that the firmware will do its job and configure the PCI bus, like it's supposed to. Of course, when our PnP code goes and resets all of the PnP devices, you will lose if you already have attached them as normal ISA devices. So, we work around this by issuing a PnP reset before doing any ISA device probes, if PnP support is configured into the kernel. In a perfect world, all busses would be direct config, and none of this would be an issue, because you could simply reserve the space used by an device with no driver, or, such as in PCI, simply choose to not map the device. But, hey, this is PC hardware we're talking about. It's not likely that it'll be reasonably sane any time soon. 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 27 17:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09741 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 17:45:41 -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 RAA09697 for ; Thu, 27 Aug 1998 17:45:26 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA05546; Thu, 27 Aug 1998 17:44:30 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd005515; Thu Aug 27 17:44:28 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA03553; Thu, 27 Aug 1998 17:44:21 -0700 (MST) From: Terry Lambert Message-Id: <199808280044.RAA03553@usr07.primenet.com> Subject: Re: PCI devices To: mike@smith.net.au (Mike Smith) Date: Fri, 28 Aug 1998 00:44:21 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG In-Reply-To: <199808271457.OAA00519@dingo.cdrom.com> from "Mike Smith" at Aug 27, 98 02:57: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 > > > This is a fallacious conclusion. An OS which meets the criteria for > > > "PnP OS" in the preceeding discussion need not (and may not) work on a > > > system without a PnP BIOS. > > > > Then the OS sucks. > > Or perhaps it's just designed only to run on PnP systems. That's precisely the part that sucks. 8-p. > > 4) The PnP OS can then: > > > > A) issues the key sequence to put all PnP devices to > > sleep. > > B) identify all EISA, MCA, PCI, and PCMCIA hardware, for > > the purpose of excluding it from ISA identification. > > C) Identify all remaining (legacy) ISA hardware. > > It's arguably erroneous to perform this at this stage. It would be > more correct to attempt to locate *resources* claimed by such devices. Huh? How can it do this without locating the devices to which the resources are assigned? > > D) Perform PnP card isolation for configuration, and > > identify all possible locations for the cards. > > E) Perform closure over all possible configuration > > combinations for all cards. > > F) Configure the cards, as necessary. > > > > This is, in fact, the basis for the Microsoft claim that Windows 98 > > is better at autoconfiguration that most PnP BIOS's. In the presence > > of legacy cards unknown to the BIOS, Microsoft will not assign a > > resource used by a legacy card to a PnP card. > > Only if the operating system is capable of locating the device, and only > if the user has not correctly informed the BIOS of the resources > consumed by said device. If the user has behaved appropriately, the > information is available both to the BIOS and the operating system via > the ESCD data. Presuming the BIOS is willing to be informed (ie: that it is a PnP BIOS). If it's *not* a PnP BIOS, then it *won't* enable cards that come up disabled, and it *won't* do resource contention avoidance. > > Note that this will be necessary for the OS to do on non-Intel > > hardware in most cases, since the OS must run an x86 interpreter > > to implement the card POST and other BIOS execution functions > > for Intel cards in these systems. > > The number of ISA PnP adapters with onboard BIOS code is so low that > such emulation is virtually pointless. There is one specific case > (video adapters) which is already well covered on at least some > platforms (eg. the alpha console ROM contains an x86 emulator). The resource records are in the ROM, so the ROM has to be there. > > In any case, there should be no more reason for an OS to guess than > > there would be for a BIOS to guess. > > In the absence of ESCD information, the OS must guess as to the location > of system peripherals. It can only detect those peripherals that it > already knows about, ie. it must guess. In the presence of (correct) > ESCD information, the BIOS and the operating system both have the same > data, and modulo bugs in the BIOS implementation both can do the same > work. Unless the BIOS is not a PnP BIOS, in which case the OS has a much better shot. But since the OS can detect legacy hardware resource usage via probe, and the BIOS does not, the OS has an advantage, even in the PnP BIOS case. 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 27 18:03:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12798 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 18:03:35 -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 SAA12789 for ; Thu, 27 Aug 1998 18:03:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01530; Thu, 27 Aug 1998 17:58:22 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271758.RAA01530@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Fri, 28 Aug 1998 00:44:21 GMT." <199808280044.RAA03553@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 17:58:22 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 4) The PnP OS can then: > > > > > > A) issues the key sequence to put all PnP devices to > > > sleep. > > > B) identify all EISA, MCA, PCI, and PCMCIA hardware, for > > > the purpose of excluding it from ISA identification. > > > C) Identify all remaining (legacy) ISA hardware. > > > > It's arguably erroneous to perform this at this stage. It would be > > more correct to attempt to locate *resources* claimed by such devices. > > Huh? How can it do this without locating the devices to which the > resources are assigned? By using a variety of non- and semi- intrusive techniques. For example the ISA PnP architecture supports using a PnP device as a test pattern generator for I/O port ranges, which are the most critical. > > The number of ISA PnP adapters with onboard BIOS code is so low that > > such emulation is virtually pointless. There is one specific case > > (video adapters) which is already well covered on at least some > > platforms (eg. the alpha console ROM contains an x86 emulator). > > The resource records are in the ROM, so the ROM has to be there. The resource records are not necessarily in a ROM, and such a ROM is not necessarily mapped into any accessible address space. Even if such a ROM were mapped, it might not contain any initialisation code, so the point about detecting the ROM type based on initialisation layout is unuseful. Alternative designs include serial EEPROM or serial ROM, and a hardcoded shift register preload (effectively a serial ROM) embedded in the interface ASIC. > > > In any case, there should be no more reason for an OS to guess than > > > there would be for a BIOS to guess. > > > > In the absence of ESCD information, the OS must guess as to the location > > of system peripherals. It can only detect those peripherals that it > > already knows about, ie. it must guess. In the presence of (correct) > > ESCD information, the BIOS and the operating system both have the same > > data, and modulo bugs in the BIOS implementation both can do the same > > work. > > Unless the BIOS is not a PnP BIOS, in which case the OS has a much better > shot. You get a kick out of restating things? The point being that under these circumstances the OS is the *only* player, but it's _still_guessing_. > But since the OS can detect legacy hardware resource usage via probe, > and the BIOS does not, the OS has an advantage, even in the PnP BIOS > case. The OS has no advantage over a PnP BIOS unless the system is misconfigured. Even then it only has an advantage when it can detect everything. This is problematic. -- \\ 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 27 18:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13793 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 18:09:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13783 for ; Thu, 27 Aug 1998 18:09:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA16813; Thu, 27 Aug 1998 18:07:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 03:34:07 +0900." <19980828033407Q.masafumi@aslm.rim.or.jp> Date: Thu, 27 Aug 1998 18:07:15 -0700 Message-ID: <16809.904266435@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now, as a blind FreeBSD user/developer, I'd like to include > boot.config that has ``-D'' in our boot floppy so that we don't have > to ask any sighted geek to look for the Boot: prompt in order to let > the installer dump everything to the serial port. Hmmmmm. Looking at README.serial, I can't see any downside - can anyone else? What happens in the case where you have no serial ports, does the kernel just ignore it and continue? (Sorry, my FreeBSD spam box is Linux'd at the moment or I'd check quickly for myself :). If it's entirely benign, I see no reason why you shouldn't make the relevant change to /usr/src/release/Makefile. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 18:22:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16440 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 18:22:18 -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 SAA16388 for ; Thu, 27 Aug 1998 18:22:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01648; Thu, 27 Aug 1998 18:16:34 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271816.SAA01648@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Thu, 27 Aug 1998 18:07:15 MST." <16809.904266435@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 18:16:33 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Now, as a blind FreeBSD user/developer, I'd like to include > > boot.config that has ``-D'' in our boot floppy so that we don't have > > to ask any sighted geek to look for the Boot: prompt in order to let > > the installer dump everything to the serial port. > > Hmmmmm. Looking at README.serial, I can't see any downside - can > anyone else? What happens in the case where you have no serial ports, > does the kernel just ignore it and continue? (Sorry, my FreeBSD spam > box is Linux'd at the moment or I'd check quickly for myself :). > > If it's entirely benign, I see no reason why you shouldn't make the > relevant change to /usr/src/release/Makefile. It's potentially not benign in the case where there is a mouse on the first serial port, or there exists some other situation where either attempting to read from the port returns garbage or writing to it causes a problem. In the proposed application, these seem like highly unlikely situations. I wouldn't suggest making -D the default for the general case though. -- \\ 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 27 18:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20679 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 18:44:21 -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 SAA20604 for ; Thu, 27 Aug 1998 18:44:03 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA24238; Thu, 27 Aug 1998 18:43:10 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd024139; Thu Aug 27 18:43:01 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA06707; Thu, 27 Aug 1998 18:42:55 -0700 (MST) From: Terry Lambert Message-Id: <199808280142.SAA06707@usr07.primenet.com> Subject: Re: Warning: Change to netatalk's file name handling To: stb@hanse.de (Stefan Bethke) Date: Fri, 28 Aug 1998 01:42:55 +0000 (GMT) Cc: tlambert@primenet.com, archie@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Stefan Bethke" at Aug 28, 98 00:36:04 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 > > > Where is the encoding defined for character values in the ranges between > > > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > > > ISO 8859? > > Is this a standardized encoding for POSIX file names, or just a > convention? If it only is a convention, what will non-latin script users > think about it? How do we discriminate between different 8859 encodings? > (Yeah, I see your point about "locales".) The UNIX server does *not* discriminate. The UNIX server (naievely) expects the locale to be set to the correct value for the data that is to be viewed. In other words, it expects that the user knows what they are doing. Ideally, at some point, we will cut over to a character encoding standard that doesn't force a server (acting as a user of the UNIX system) to chose a single locale for all clients of the server. For example, Unicode. This will require that we provide a wchar_t interface to the named objects in the file system, and will require expanding the directory block size to 1k, at a minimum, to support 256 character path components, where a character is 2 octets (ideally) or 4 octets (to satisfy people who optimistically believe that the other code pages in ISO 10646 will be defined so they can "grep -v" to avoid seeing text not in their own language). Of course, for NFS interoperability with existing systems, you will need to "attribute" NFS mounts of legacy servers with an 8-bit character encoding so it can be round-tripped in and out of Unicode. So the short answer is "character = single octet, encoding undefined" for now and "character = multiple octet, encoding undefined" for later. > > Per interoperability: This presumes, incorrectly, that Mac's support > > the same idiotic idea of code pages as SAMBA must. > > Macs, in this sense, use a single "code page." I believe there is an escape > mechanism to change the encoding to non-latin scripts, but I will have to > look that up in Inside Mac. For AFP 2.1 (which netatalk claims to support to > the extent the Macs use it), there is a single encoding defined, without any > escape mechanism. Escaping mechanisms are "in-band". This is why ISO-2022 encoded Japanese looked the same between SAMBA and AppleTalk for Archie. > > > It won't change anything to the worse; the only problem is that > > > existing files with file names containing control characters > > > (custom icons on folders being the single source of such name > > > probably) will stop working and will need manual assistance from > > > an operator. > > > > It will break a number of things. It already breaks the file name > > length limitation in SAMBA. Duplicating this break into Appletalk is, > > IMO, a bad idea. > > I don't know much about SMB/CIFS/Samba. What is the filename length limit > (as opposed, possibly, to the pathname limit)? 256 characters. On UNIX, it's 256 characters. Any escaping in-band steals characters from the end of the name, and reduces the possible length for files with escaped characters in them. This is bad. > > If you are going to push this hard, you should consider Internataional > > representation ofile names by client locale, and how it is already > > handled. > > Would you mind to point me to any information shedding light on > standardisation efforts for file name representation? In terms of "locale", > this would mean that "Mac" or "AFP" would be it's own locale in terms of > file name character encoding? Well, generic information is ISO 2022, ISO 10646 (or the Unicode Standard), EUC, and RFC2152. I would go light on RFC2152; UTF-7, which is what it documents, is another encoding mechanism that destroys the ability to predict the buffer size necessary to back fixed fields. Such standards are evil, especially since we are stuck with using fixed maximums for number of characters in a filename. ISO 2022 has the same problem, of course, but with each character representing an ideogram instead of an alphabetic letter, information density is high enough that a 3:1 fixed length limit is not much of a hardship. > After all, I see three possible ways: > > - improve interoperability by confining to printable ASCII (or ISO-8859-1, > or...) and not escaping other glyphs, thus breaking AFP conformance; Don't break AFP conformance. > - escaping all glyphs (or rather their encoding) in a way that preserves the > full AFP filename encoding space (for filenames, this is 0x01 to 0xff, > with ":" being illegal as it is the path delimiter), but using printable > ASCII where possible (this is, I believe, what netatalk tries to do, but > doesn't, due to a stupid bug). The "/" (/ is volume delimiter; this was the info I missed earlier) for ":" trade is a relatively easy call; it's simple and obvious, and you are exporting by volume, so a volume seperator is not needed in-band. So this is an easy fix for an easy bug. > - translate the AFP filename encoding space into some larger glyph encoding > space, such as Unicode, or, more specifically, UTF-8. This is evil for the reasons outlined above. > The last one probably is the way to go, but this would require (at least to > me) some testimonial that Unicode in general and UTF-8 in particular is the > way to go for file names in FreeBSD. This of course would probably start > other interop problems with NFS and alike, and it would require samba to > deal with CP bogosities in its own right instead of putting it in the face > of every other app. People from the US will like UTF-8, since it leaves ASCII alone. It pretty much screws everyone else in the 0x80-0xff space (ie: all ISO 8859 family using nations, and KOI8-R, etc., as well as shift-encoding, per Japan/Taiwan/China/Korea) though, because it means all of their existing data would need to be translated. This is exactly the problem of trying to move from "coding undefined" to "coding defined". This is why Unicode, which leaves the interpretation of the locale to the rendering engines choice of fonts, is so UNIXy. I really can't see people doing this, or worse, us doing a very complicated version of this in the kernel, in order to be able to use existing data and NFS mounts from legacy systems. For some educational uses in Europe, you would be asking them to convert their entire country simultaneously. In Japan, you would be asking, minimally, for institutional conversion. 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 27 18:51:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22000 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 18:51:56 -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 SAA21949 for ; Thu, 27 Aug 1998 18:51:24 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA23120; Fri, 28 Aug 1998 11:20:16 +0930 (CST) 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, 28 Aug 1998 11:20:15 +0930 (CST) From: "Daniel O'Connor" To: Lyndon Nerenberg Subject: Re: Imap4 Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Aug-98 Lyndon Nerenberg wrote: > yet), then you can expect to see SIEVE implementations rolling out over the > next couple of months. Yeah, I had a look for SIEVE stuff and it seemed interesting, but as you say, not implemented yet :) --------------------------------------------------------------------- |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 27 19:06:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24854 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 19:06:17 -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 TAA24797 for ; Thu, 27 Aug 1998 19:05:52 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA00722; Thu, 27 Aug 1998 19:04:56 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd000656; Thu Aug 27 19:04:49 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id TAA07846; Thu, 27 Aug 1998 19:04:37 -0700 (MST) From: Terry Lambert Message-Id: <199808280204.TAA07846@usr07.primenet.com> Subject: Re: PCI devices To: mike@smith.net.au (Mike Smith) Date: Fri, 28 Aug 1998 02:04:36 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG In-Reply-To: <199808271758.RAA01530@dingo.cdrom.com> from "Mike Smith" at Aug 27, 98 05:58:22 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 resource records are not necessarily in a ROM, and such a ROM is > not necessarily mapped into any accessible address space. Even if such > a ROM were mapped, it might not contain any initialisation code, so the > point about detecting the ROM type based on initialisation layout is > unuseful. > > Alternative designs include serial EEPROM or serial ROM, and a > hardcoded shift register preload (effectively a serial ROM) embedded in > the interface ASIC. After a bit of re-reading, I can see where I went wrong. A card *MAY* have a ROM; if it doesn't, you have to use the I/O ports to get the config data. What it may *NOT* omit is the existance of config data. > > > In the absence of ESCD information, the OS must guess as to the location > > > of system peripherals. It can only detect those peripherals that it > > > already knows about, ie. it must guess. In the presence of (correct) > > > ESCD information, the BIOS and the operating system both have the same > > > data, and modulo bugs in the BIOS implementation both can do the same > > > work. > > > > Unless the BIOS is not a PnP BIOS, in which case the OS has a much better > > shot. > > You get a kick out of restating things? The point being that under > these circumstances the OS is the *only* player, but it's > _still_guessing_. I think a PnP FreeBSD should work with PnP cards in a machine that does not have a PnP BIOS. I think it's misleading to say you have a PnP OS, and then when a user plugs in a PnP card, the card is not reported. I think any PnP OS that fails to do the work of the PnP BIOS in the absence of a PnP BIOS doesn't deserve to be called a PnP OS. I'm attempting to make this point, not restate things. If this is a restatement (again), then I think you are trying to gloss over the point. > > But since the OS can detect legacy hardware resource usage via probe, > > and the BIOS does not, the OS has an advantage, even in the PnP BIOS > > case. > > The OS has no advantage over a PnP BIOS unless the system is > misconfigured. Even then it only has an advantage when it can detect > everything. This is problematic. In "detect", I loosely include the ability to mark resources used by legacy cards as "taken", without specifying "by what". In other words, cards for which there is not a driver, but for which resources must be accounted to avoid a conflict. I also like the Microsoft idea that you tell the PnP BIOS that you aren't a PnP OS; this avoids things like the Adaptec 2940 and Bus Mouse IRQ 12 conflicts caused by the ALR motherboard having a BIOS that didn't know that there was a bus mouse on the motherboard, since the OS is capable of, best case, proactively detecting the hardware, or, worst case, allowing configuration of a "conflict map" for the hardware so that it doesn't break PnP devices by mapping them into this "unused" space. 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 27 19:18:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27134 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 19:18:56 -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 TAA27068 for ; Thu, 27 Aug 1998 19:18:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA01973; Thu, 27 Aug 1998 19:13:00 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271913.TAA01973@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices In-reply-to: Your message of "Fri, 28 Aug 1998 02:04:36 GMT." <199808280204.TAA07846@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 19:13:00 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Unless the BIOS is not a PnP BIOS, in which case the OS has a much better > > > shot. > > > > You get a kick out of restating things? The point being that under > > these circumstances the OS is the *only* player, but it's > > _still_guessing_. > > I think a PnP FreeBSD should work with PnP cards in a machine that > does not have a PnP BIOS. I agree entirely, and have never meant to suggest otherwise. > I think it's misleading to say you have a PnP OS, and then when a > user plugs in a PnP card, the card is not reported. Agreed. > I think any PnP OS that fails to do the work of the PnP BIOS in > the absence of a PnP BIOS doesn't deserve to be called a PnP OS. That's not meaningful. See Jason's rant inre: PCI BIOS behaviour. > > > But since the OS can detect legacy hardware resource usage via probe, > > > and the BIOS does not, the OS has an advantage, even in the PnP BIOS > > > case. > > > > The OS has no advantage over a PnP BIOS unless the system is > > misconfigured. Even then it only has an advantage when it can detect > > everything. This is problematic. > > In "detect", I loosely include the ability to mark resources used > by legacy cards as "taken", without specifying "by what". In other > words, cards for which there is not a driver, but for which resources > must be accounted to avoid a conflict. The "correct" way to do this is via ESCD. In situations where that's not possible, you have to guess. See earlier. > I also like the Microsoft idea that you tell the PnP BIOS that you > aren't a PnP OS; this avoids things like the Adaptec 2940 and Bus Mouse > IRQ 12 conflicts caused by the ALR motherboard having a BIOS that > didn't know that there was a bus mouse on the motherboard, since the > OS is capable of, best case, proactively detecting the hardware, or, > worst case, allowing configuration of a "conflict map" for the > hardware so that it doesn't break PnP devices by mapping them into > this "unused" space. Unless the ALR BIOS is completely broken, a trivial workaround would involve telling it that irq 12 is reserved for a legacy device. This is probably too hard for many people. Compensating for broken firmware is difficult at best. We should, however, avoid trying to do more ourselves than we have to. It's generally valid to assume that the hardware manufacturer knows at least as much about the hardware as we can ever determine. -- \\ 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 27 20:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06505 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 20:13:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gateway.whtech.com (user33.usr1.accesscom.com [205.226.158.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06461 for ; Thu, 27 Aug 1998 20:13:20 -0700 (PDT) (envelope-from don@whtech.com) Received: from digerati (digerati.whtech.com [10.1.0.2]) by gateway.whtech.com (8.8.7/8.8.7) with SMTP id UAA00419 for ; Thu, 27 Aug 1998 20:17:32 -0700 (PDT) (envelope-from don@whtech.com) From: "Don O'Neil" To: Subject: Weird sendmail/pop problem Date: Thu, 27 Aug 1998 20:13:33 -0700 Message-ID: <000301bdd231$d6cafe60$0200010a@digerati.whtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm experiencing a weird sendmail problem.. Anyone have any clues where to start looking for this? Here goes: I have a user on my box that is set up to forward mail to 2 people... When I send mail using MS Outlook 98 through a pop3 connection the second person in the .forward file gets the message but the first one doesnt. When I go outside of my box and send mail to the user, then BOTH people in the .forward file get the message... I've checked the aliases db, any .forward files laying around on the machine, and all the basic configs for pop3 and sendmail but have come up empty handed... Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 20:29:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08529 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 20:29:48 -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 UAA08486 for ; Thu, 27 Aug 1998 20:29:15 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-55.camalott.com [208.229.74.55]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA29570; Thu, 27 Aug 1998 22:29:50 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA28804; Thu, 27 Aug 1998 22:28:01 -0500 (CDT) (envelope-from joelh) Date: Thu, 27 Aug 1998 22:28:01 -0500 (CDT) Message-Id: <199808280328.WAA28804@detlev.UUCP> To: frank@exit.com CC: bsmith@bfmni.com, hackers@FreeBSD.ORG In-reply-to: <199808271535.IAA14820@exit.com> (message from Frank Mayhar on Thu, 27 Aug 1998 08:35:34 -0700 (PDT)) Subject: Re: cvs commit: src/sbin/ping ping.c From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808271535.IAA14820@exit.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Maybe make it like Microsoft's PING where it pings 4 times unless you use >> the -t option. >> -t Ping the specifed host until interrupted. > I dunno, it sounds like change for the sake of change to me. This > would be annoying in the extreme; I use infinite pings almost daily. I agree. I've got a few scripts that rely on the BSD ping behaviour, that run on many machines. I'm sure most admins do. A personal alias is the way to go on this case. > I would have less objection to a change making the ping run for, > say, six or eight hours before automatically shutting off. That's > long enough (for my purposes) that I would probably never hit the > auto-shutoff time, and it still quits by itself after a while. I disagree. An auto-shutoff violates POLA. 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 27 21:30:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18353 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 21:30:17 -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 VAA18292 for ; Thu, 27 Aug 1998 21:30:10 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id VAA27499; Thu, 27 Aug 1998 21:29:20 -0700 (PDT) Message-ID: <19980827212920.A26425@Alameda.net> Date: Thu, 27 Aug 1998 21:29:20 -0700 From: Ulf Zimmermann To: Wilko Bulte , FreeBSD hackers list Subject: Re: obtaining Mylex programming information Reply-To: ulf@Alameda.net References: <199808260909.LAA06968@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808260909.LAA06968@yedi.iaf.nl>; from Wilko Bulte on Wed, Aug 26, 1998 at 11:09:13AM +0200 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 Wed, Aug 26, 1998 at 11:09:13AM +0200, Wilko Bulte wrote: > Hi there > > I'm trying to get a programmers manual for the Mylex DAC960 raid > controller cards. I got a response back from Mylex support that a NDA > is needed. Although I've sent them mail asking them if the NDA allows > releasing source code I don't have high hopes. > > But I do remember that on this list there was an optimistic note on > Mylex some time ago. Does anybody already have the docs (you can always > hope..) that is not covered by an NDA? > > Any help appreciated. I got the programming information as M$ Word document plus DAC960PJ 3 channels from Mylex. I signed no NDA. Trying to learn still stuff about the kernel. Probing routines are working, I can talk with the controller and manual transfer a block. > > Wilko > _ ______________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl > |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl > ______________________________________________ Powered by FreeBSD __________ > > 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 Thu Aug 27 22:02:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22475 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 22:02:56 -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 WAA22469 for ; Thu, 27 Aug 1998 22:02:50 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d1.syd2.zeta.org.au [203.26.11.1]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id PAA29641 for ; Fri, 28 Aug 1998 15:01:48 +1000 Received: (qmail 9439 invoked by uid 1000); 28 Aug 1998 04:35:03 -0000 From: "Andrew Reilly" Message-ID: <19980828143503.A9421@reilly.home> Date: Fri, 28 Aug 1998 14:35:03 +1000 To: Terry Lambert , Mike Smith Cc: tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG Subject: Re: PCI devices References: <199808262207.WAA00827@word.smith.net.au> <199808271857.LAA26413@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808271857.LAA26413@usr01.primenet.com>; from Terry Lambert on Thu, Aug 27, 1998 at 06:57:27PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 27, 1998 at 06:57:27PM +0000, Terry Lambert wrote: > 1) All legacy ISA device ROMs are required to begin on a 2K > 2) All PnP device ROMS have the same requirements. But as of > 3) On a non-PnP-BIOS machine, devices in the boot path will be > 4) The PnP OS can then: What happens with legacy ISA devices that don't have a ROM? I know one or two of those. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 22:33:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25520 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 22:33:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ascetic.portal.ca (ascetic.portal.ca [206.87.139.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25511 for ; Thu, 27 Aug 1998 22:33:29 -0700 (PDT) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by ascetic.portal.ca (8.8.8/8.8.5) with SMTP id WAA07664; Thu, 27 Aug 1998 22:31:59 -0700 (PDT) X-Authentication-Warning: ascetic.portal.ca: cjs owned process doing -bs Date: Thu, 27 Aug 1998 22:31:59 -0700 (PDT) From: Curt Sampson To: Mike Smith cc: zhihuizhang , hackers Subject: Re: FFS questions In-Reply-To: <199808271532.PAA00757@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 Thu, 27 Aug 1998, Mike Smith wrote: > The position table and all the optimisations related to second-guessing > the behaviour of the disk are now pessimisations in most cases, and > should be eliminated entirely. Ooo...you're going to regret that when you do your VAX 11/750 port! :-) cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 23:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02239 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 23:29:14 -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 XAA02221 for ; Thu, 27 Aug 1998 23:29:08 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id IAA15878; Fri, 28 Aug 1998 08:30:18 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 28 Aug 1998 08:30:18 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Jordan K. Hubbard" cc: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-Reply-To: <16809.904266435@time.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 Thu, 27 Aug 1998, Jordan K. Hubbard wrote: > > Now, as a blind FreeBSD user/developer, I'd like to include > > boot.config that has ``-D'' in our boot floppy so that we don't have > > to ask any sighted geek to look for the Boot: prompt in order to let > > the installer dump everything to the serial port. And what about making the boot code emit a short beep when it displays the boot: prompt? 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 Thu Aug 27 23:41:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03753 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 23:41:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03723 for ; Thu, 27 Aug 1998 23:41:41 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01518; Thu, 27 Aug 1998 23:38:06 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808272338.XAA01518@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: "Jordan K. Hubbard" , Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 08:30:18 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 23:38:05 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And what about making the boot code emit a short beep when it displays > the boot: prompt? How about: # cat >> /boot/boot.conf echo ^G ? -- \\ 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 27 23:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04566 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 23:47:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04549 for ; Thu, 27 Aug 1998 23:47:19 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id PAA19226; Fri, 28 Aug 1998 15:46:25 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id PAA03916; Fri, 28 Aug 1998 15:46:25 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id PAA25100; Fri, 28 Aug 1998 15:36:30 +0900 (JST) To: abial@nask.pl Cc: jkh@time.cdrom.com, max@wide.ad.jp, mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Cc: max@wide.ad.jp Subject: Re: question From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Fri, 28 Aug 1998 08:30:18 +0200 (CEST)" References: X-Mailer: Mew version 1.92.4 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: <19980828153629F.masafumi@aslm.rim.or.jp> Date: Fri, 28 Aug 1998 15:36:29 +0900 X-Dispatcher: imput version 971024 Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Now, as a blind FreeBSD user/developer, I'd like to include > >> boot.config that has ``-D'' in our boot floppy so that we don't >> have > to ask any sighted geek to look for the Boot: prompt in >> order to let > the installer dump everything to the serial >> port. > And what about making the boot code emit a short beep when it > displays the boot: prompt? Yeah, that's an idea. If this can be achieved without increasing the size of the boot block too much, this might be better than making the -D the default even though this is beyond my ability. Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 27 23:53:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05403 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 23:53:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05389 for ; Thu, 27 Aug 1998 23:53:23 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01736; Thu, 27 Aug 1998 23:49:56 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808272349.XAA01736@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: abial@nask.pl, jkh@time.cdrom.com, mike@smith.net.au, pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 15:36:29 +0900." <19980828153629F.masafumi@aslm.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 23:49:55 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > Now, as a blind FreeBSD user/developer, I'd like to include > > >> boot.config that has ``-D'' in our boot floppy so that we don't > >> have > to ask any sighted geek to look for the Boot: prompt in > >> order to let > the installer dump everything to the serial > >> port. > > > And what about making the boot code emit a short beep when it > > displays the boot: prompt? > > Yeah, that's an idea. If this can be achieved without increasing the > size of the boot block too much, this might be better than making the > -D the default even though this is beyond my ability. Making -D the default for a limited subset of disks is very easy; you can mount the disk, write '-D' into /boot.config and unmount it. It's just a bit dangerous in the *general* case. For the general case, the keyboard probe was a good idea that hasn't quite worked out - with no keyboard, you'd just get the serial console by default. If a beep is a desirable idea, then we can certainly do that. Anything else that might be better? -- \\ 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 28 00:03:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06784 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:03: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 AAA06764 for ; Fri, 28 Aug 1998 00:03:36 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA25115; Fri, 28 Aug 1998 16:31:49 +0930 (CST) 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: <199808272338.XAA01518@word.smith.net.au> Date: Fri, 28 Aug 1998 16:31:49 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: question Cc: freebsd-hackers@FreeBSD.ORG, pvernon@purdue.edu, Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , "Jordan K. Hubbard" , Andrzej Bialecki Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Aug-98 Mike Smith wrote: > > And what about making the boot code emit a short beep when it displays > > the boot: prompt? > > How about: > > # cat >> /boot/boot.conf > echo ^G Shouldn't that be boot.help? --------------------------------------------------------------------- |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 Fri Aug 28 00:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08031 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:10:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08022 for ; Fri, 28 Aug 1998 00:10:25 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA01954; Fri, 28 Aug 1998 00:07:31 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280007.AAA01954@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: Mike Smith , freebsd-hackers@FreeBSD.ORG, pvernon@purdue.edu, Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , "Jordan K. Hubbard" , Andrzej Bialecki Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 16:31:49 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 00:07:30 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 27-Aug-98 Mike Smith wrote: > > > And what about making the boot code emit a short beep when it displays > > > the boot: prompt? > > > > How about: > > > > # cat >> /boot/boot.conf > > echo ^G > Shouldn't that be boot.help? Hmm, actually that would be the place to put it in the current scenario, yes. /boot/boot.banner is where it would go with the "new" bootstrap. -- \\ 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 28 00:14:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08641 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:14: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 AAA08624 for ; Fri, 28 Aug 1998 00:14:37 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA25219; Fri, 28 Aug 1998 16:42:59 +0930 (CST) 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: <199808280007.AAA01954@word.smith.net.au> Date: Fri, 28 Aug 1998 16:42:59 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: question Cc: Andrzej Bialecki , "Jordan K. Hubbard" , Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= , pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Aug-98 Mike Smith wrote: > > Shouldn't that be boot.help? > Hmm, actually that would be the place to put it in the current > scenario, yes. /boot/boot.banner is where it would go with the "new" > bootstrap. OK.. hmm.. does the new stuff boot intel boxes yet? :) --------------------------------------------------------------------- |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 Fri Aug 28 00:23:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09599 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:23:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09582 for ; Fri, 28 Aug 1998 00:22:56 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA02025; Fri, 28 Aug 1998 00:20:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280020.AAA02025@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 16:42:59 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 00:20:08 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 28-Aug-98 Mike Smith wrote: > > > Shouldn't that be boot.help? > > Hmm, actually that would be the place to put it in the current > > scenario, yes. /boot/boot.banner is where it would go with the "new" > > bootstrap. Actually, I should clarify; inserting a ^G into the current /boot.help should achieve the desired result. With the "new" bootstrap, the help text is separate from any potential sign-on banner. > OK.. hmm.. does the new stuff boot intel boxes yet? :) a.out kernels from floppy only. The only stumbling block with other disks is the biosdisk : major/minor numbering mapping. Getting it "right" on old systems is still impossible, and getting it "right" on new (EDD 3) systems leads to some new and even more subtle quirks. 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 Fri Aug 28 00:37:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10911 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:37:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10892; Fri, 28 Aug 1998 00:37:17 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id KAA29123; Fri, 28 Aug 1998 10:35:44 +0300 (EEST) (envelope-from ru) Message-ID: <19980828103544.A28966@ucb.crimea.ua> Date: Fri, 28 Aug 1998 10:35:44 +0300 From: Ruslan Ermilov To: Brandon Huey , questions@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Cyclades Cyclom-Y series multiport board References: <199808272049.NAA17655@transbay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199808272049.NAA17655@transbay.net>; from Brandon Huey on Thu, Aug 27, 1998 at 01:49:27PM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 27, 1998 at 01:49:27PM -0700, Brandon Huey wrote: > > is this supported under freebsd? > [ I have CC'ed this to -hackers in hope to bring someone's attention up ] The following results are true for -stable: PCI (YeP) cards are not working (they are constantly produce `silo overflows'). ISA (Ye) cards with 1.x revisions work well. ISA (Ye) cards with 2.x revisions don't work at all. Also, there are two versions of Serial Module (SM and SM-II). SM modules are supported by the native FreeBSD driver. SM-II modules are supported only by the driver supplied by Cyclades Corp. At least, it SHOULD BE noted in src/release/sysinstall/help/hardware.hlp. With best Regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 00:49:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12150 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:49:39 -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 AAA12139 for ; Fri, 28 Aug 1998 00:49:30 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA25463; Fri, 28 Aug 1998 17:18:35 +0930 (CST) 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: <199808280020.AAA02025@word.smith.net.au> Date: Fri, 28 Aug 1998 17:18:34 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: question Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Aug-98 Mike Smith wrote: > > OK.. hmm.. does the new stuff boot intel boxes yet? :) > a.out kernels from floppy only. The only stumbling block with other > disks is the biosdisk : major/minor numbering mapping. Getting it > "right" on old systems is still impossible, and getting it "right" on > new (EDD 3) systems leads to some new and even more subtle quirks. 8( May you defeat the Evil Empire(tm) in your quest for a better OS.. =) --------------------------------------------------------------------- |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 Fri Aug 28 00:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13187 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 00:58:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13167 for ; Fri, 28 Aug 1998 00:58:43 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA02289; Fri, 28 Aug 1998 00:55:52 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280055.AAA02289@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Fri, 28 Aug 1998 17:18:34 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 00:55:51 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 28-Aug-98 Mike Smith wrote: > > > OK.. hmm.. does the new stuff boot intel boxes yet? :) > > a.out kernels from floppy only. The only stumbling block with other > > disks is the biosdisk : major/minor numbering mapping. Getting it > > "right" on old systems is still impossible, and getting it "right" on > > new (EDD 3) systems leads to some new and even more subtle quirks. 8( > May you defeat the Evil Empire(tm) in your quest for a better OS.. =) I wish. We are left stumbling in their wake, grubbing through the scraps of documentation they let fall like wrinkled candy wrappers among the trash, trying to infer their algorithms from the cryptic scribblings thereon. -- \\ 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 28 01:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13988 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 01:03:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13953 for ; Fri, 28 Aug 1998 01:02:55 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id KAA04373 for ; Fri, 28 Aug 1998 10:02:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zCJTt-002ZjZC; Fri, 28 Aug 98 10:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Fri, 28 Aug 1998 09:22:42 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@freebsd.org; Fri, 28 Aug 1998 09:22:43 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: TCP checksum errors resulting from IP addr change To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) Date: Fri, 28 Aug 1998 09:22:43 +0200 (CEST) Organization: Kitchen Table Systems Reply-To: hm@kts.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 Hi, I've posted this to -net without a reaction. Any reaction is welcome since i totally ran out of ideas: I'm trying to debug a strange effect occuring on a sync PPP ISDN interface which is used to connect to a Cisco 1003 (on 192.76.124.10). To get an address dynamically from the remote side, the local PPP inter- face (on 2.2.5-RELEASE) is set up with: ifconfig isppp0 link1 0.0.0.0 192.76.124.10 netmask 0xffffffff debug Now i telnet to 192.76.124.10 and the link gets established but the telnet session doesn't. I looked at the traces and noticed the very first IP packet going out with source address 0.0.0.0 to the Cisco - i removed that in the driver but still the telnet session is not established. (btw. only the first session is not established, if i terminate the first telnet and restart it on the open link, it works immediately; but i want the first to work ...). I enabled TCP debugging on the Cisco, and for all the packets from this first telnet session it says "TCP checksum error". So i think, IP address 0.0.0.0 is used for checksum calculation of the TCP packets for this forst session, but the "real" IP address of the interface changes to 192.something after the first packet and the TCP checksum is somehow not recalculated causing checksum errors on the remote side (Is this correct ?). Is there a way to inform the TCP layer to recalculate checksums or to get the new IP address from the interface ? Do i have to recalculate the checksums for this session in the driver ? Has anyone another hint or an idea how to solve this ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 01:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15629 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 01:17:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from samson.dc.luth.se (samson.dc.luth.se [130.240.112.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15614 for ; Fri, 28 Aug 1998 01:17:40 -0700 (PDT) (envelope-from murduth@dc.luth.se) Received: from u3.dc.luth.se (murduth@u3.dc.luth.se [130.240.112.243]) by samson.dc.luth.se (8.9.1a/8.9.1) with ESMTP id KAA23789 for ; Fri, 28 Aug 1998 10:16:47 +0200 (MET DST) Received: from localhost (murduth@localhost) by u3.dc.luth.se (8.8.8/8.8.8) with SMTP id KAA11902 for ; Fri, 28 Aug 1998 10:16:41 +0200 (MET DST) Date: Fri, 28 Aug 1998 10:16:41 +0200 (MET DST) From: Joakim Henriksson To: freebsd-hackers@FreeBSD.ORG Subject: Lost filesystems 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 was wondering if there is any chance to regain a filesystem that was lost due to windows slapping on a dos label on the disk. I have recreated the bsd partitions on the disks but i cant find a superblock to resotre the fs with, is there anything that can be done or is my best shot to restore the (ancient) backup from april this year. I would rather not for obvious reasons :/ regards/ Joakim P.S. This means i have no convinient way to read the lists until i have sane system, so any answer should be CC'ed to me at this address in some way. D.S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 04:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02087 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 04:00:07 -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 DAA01661 for ; Fri, 28 Aug 1998 03:59:59 -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 MAA24260; Fri, 28 Aug 1998 12:59:02 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 0DF51147E; Fri, 28 Aug 1998 12:56:08 +0200 (CEST) Date: Fri, 28 Aug 1998 12:56:07 +0200 From: Ollivier Robert To: Joakim Henriksson , freebsd-hackers@FreeBSD.ORG Subject: Re: Lost filesystems Message-ID: <19980828125607.A10021@keltia.freenix.fr> Mail-Followup-To: Joakim Henriksson , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Joakim Henriksson on Fri, Aug 28, 1998 at 10:16:41AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Joakim Henriksson: > lost due to windows slapping on a dos label on the disk. I have recreated > the bsd partitions on the disks but i cant find a superblock to resotre > the fs with, is there anything that can be done or is my best shot to Did you tried "fsck -b 32" ? -- 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 Fri Aug 28 05:56:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14592 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 05:56:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from samson.dc.luth.se (samson.dc.luth.se [130.240.112.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14587 for ; Fri, 28 Aug 1998 05:56:41 -0700 (PDT) (envelope-from murduth@dc.luth.se) Received: from u3.dc.luth.se (murduth@u3.dc.luth.se [130.240.112.243]) by samson.dc.luth.se (8.9.1a/8.9.1) with ESMTP id OAA28784; Fri, 28 Aug 1998 14:55:47 +0200 (MET DST) Received: from localhost (murduth@localhost) by u3.dc.luth.se (8.8.8/8.8.8) with SMTP id OAA11972; Fri, 28 Aug 1998 14:55:47 +0200 (MET DST) Date: Fri, 28 Aug 1998 14:55:47 +0200 (MET DST) From: Joakim Henriksson To: Ollivier Robert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lost filesystems In-Reply-To: <19980828125607.A10021@keltia.freenix.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 > According to Joakim Henriksson: > > lost due to windows slapping on a dos label on the disk. I have recreated > > the bsd partitions on the disks but i cant find a superblock to resotre > > the fs with, is there anything that can be done or is my best shot to > > Did you tried "fsck -b 32" ? I tried that and most of the other ones as well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 06:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18874 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 06:47:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18864 for ; Fri, 28 Aug 1998 06:47:24 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id PAA25556; Fri, 28 Aug 1998 15:43:36 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199808281343.PAA25556@ocean.campus.luth.se> Subject: Re: FFS questions In-Reply-To: from Curt Sampson at "Aug 27, 98 10:31:59 pm" To: cjs@portal.ca (Curt Sampson) Date: Fri, 28 Aug 1998 15:43:36 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG 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 Curt Sampson: > On Thu, 27 Aug 1998, Mike Smith wrote: > > > The position table and all the optimisations related to second-guessing > > the behaviour of the disk are now pessimisations in most cases, and > > should be eliminated entirely. > > Ooo...you're going to regret that when you do your VAX 11/750 port! :-) :-D Lucky we're never gonna have one, though. NetBSD is still being worked on for VAX (by a friend at the uni here), though. Optimizing, writing device drivers for "new" hardware, etc. :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 06:54:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19635 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 06:54:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from okeefe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19630 for ; Fri, 28 Aug 1998 06:54:45 -0700 (PDT) (envelope-from geniusj@suarez.bestweb.net) Received: from suarez.bestweb.net (geniusj@suarez.bestweb.net [209.94.100.150]) by okeefe.bestweb.net (8.9.0/8.9.0) with SMTP id JAA03247; Fri, 28 Aug 1998 09:53:52 -0400 (EDT) Date: Fri, 28 Aug 1998 09:52:43 -0400 (EDT) From: Jason Dicioccio To: hackers@FreeBSD.ORG cc: jason@idiom.com Subject: Help, Linux beats freebsd to death (fwd) 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 it be possible that you don't have your BSd machines setup for optimal performance. They are meant to be servers and balance out tasks evenly as to let multiple users do things at the same time without the drive plates spinning off the head ;P.. Configure it right before you start comparing. ---------- Forwarded message ---------- Date: Wed, 26 Aug 1998 08:22:08 -0700 (PDT) From: Julian Elischer To: hackers@FreeBSD.ORG Cc: jason@idiom.com Subject: Help, Linux beats freebsd to death (fwd) Anyone got good ideas? Jason, can you figure out what system calls are being performed at this time? Is it network re;lated, or filesystem related? Are there pthread related elements? Maybe a ktrace might give some clues.. (or a profile?) this has to be something really silly, because one order of magnitude is just ridiculous.. julian ---------- Forwarded message ---------- Date: Wed, 26 Aug 1998 00:12:20 -0700 From: Jason Venner To: julian@whistle.com Cc: hosler@lugs.org.sg Subject: Linux beats freebsd to death Note I just posted on the postgresql ports board. Either the K6-200 is the fastest machine on the earth or there is something seriously wrong with postgresql/jdbc and freebsd I have a couple of machines that I run postgres 6.3.2 on. Linux 2.0.32 K6-200 1meg cache, 128meg ram, scsi disks - fileserver/workstation/web server/dbms gcc - 2.7.2 FreeBSD 2.2.5-RELEASE P200 512k cache, 96meg ram, scsi - workstation/web server/dbms FreeBSD 2.2.7-RELEASE PII-333 512k cache, 256meg ram, scsi - web server/dbms I have a testsuite that creates a table and inserts a set bunch of rows. I try the table in autocomit on/off mode and rollback and commit it etc. to collect informatin. I am using the distributed jdbc driver as my interface. Under the linux machine it takes on the order of 2 seconds to do this on the 2.2.5 freebsd machine it takes on the order of 18 seconds on the 2.2.7 freebsd machine it takes on the order of 21 seconds 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 28 07:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20796 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 07:09:34 -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 HAA20791 for ; Fri, 28 Aug 1998 07:09: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 QAA06852 for freebsd-hackers@FreeBSD.ORG; Fri, 28 Aug 1998 16:07:15 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id KAA02200; Fri, 28 Aug 1998 10:30:49 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808280830.KAA02200@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG cc: seggers@semyam.dinoco.de Subject: zinitna (vm/vm_zone.c) use in kernel Date: Fri, 28 Aug 1998 10:30:48 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! While reading the VM source I noticed that zinitna uses the supplied object when it is given the flag ZONE_INTERRUPT in some way. So far, so good. Now I took a look at where it gets called and how. That brought me to vm_init2 in vm/vm_map.c where it gets called three times. Two times w/o ZONE_INTERRUPT but with an object. As I don't see where the flag gets set I think they are useless. Did I overlook something or are the two affected vm_object structures really not used because of this? Or was it the intention to be able to use an object one day for the non-interrupt cases, too and the functionality is not implemented in vm_zone.c, yet? 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 28 07:21:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22545 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 07:21:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22529 for ; Fri, 28 Aug 1998 07:21:15 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id KAA06308; Fri, 28 Aug 1998 10:21:17 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 28 Aug 1998 10:21:17 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Joakim Henriksson cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lost filesystems 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 for future reference the best partition recovery tool i have found was the Minix partition editor, it's part of the minix install program. lets you twiddle partitions without in any way messing with the data in the rest of the disk. windows once ate all 4 partitions on a disk and i was able to recover them with it. you sorta need to know the exact sizes of the partitions though. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Fri, 28 Aug 1998, Joakim Henriksson wrote: > Hi, i was wondering if there is any chance to regain a filesystem that was > lost due to windows slapping on a dos label on the disk. I have recreated > the bsd partitions on the disks but i cant find a superblock to resotre > the fs with, is there anything that can be done or is my best shot to > restore the (ancient) backup from april this year. I would rather not for > obvious reasons :/ > > regards/ Joakim > > P.S. > This means i have no convinient way to read the lists until i have sane > system, so any answer should be CC'ed to me at this address in some way. > D.S. > > > 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 28 07:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23947 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 07:33:21 -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 HAA23933 for ; Fri, 28 Aug 1998 07:33:13 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id QAA11605 for ; Fri, 28 Aug 1998 16:32:15 +0200 (MET DST) Date: Fri, 28 Aug 1998 16:32:13 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: subr_autoconf.c 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 What is the reason that subr_autoconf.c is UNUSED? NetBSD uses these config_found functions to determine the devices that can be found after a certain element has been attached to like, a pcibus implies the probing pci devices that are compiled in. My problem is that the NetBSD USB code uses this mechanism. Allthough I am not convinced that that way of specifying the device driver to attach to is according to the USB specs but it is certainly the most straightforward way of doing it in their case. Is there in FreeBSD a general mechanism to attach devices? Do the ISA, EISA and PCI bus code all implement their own way of handling things? USB is supposed to use ad hoc mechanisms to load drivers. Based on the descriptor the device returns you can select the appropriate one, either a device specific one (such and such mouse, even down to serial number) or a general driver (mouse? Give it to me). In the end of course I plan to implement everything with LKM drivers loading and unloading at status change on the hub endports. 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 28 07:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25306 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 07:48:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25280 for ; Fri, 28 Aug 1998 07:48:38 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id QAA00329; Fri, 28 Aug 1998 16:44:17 +0200 (CEST) Date: Fri, 28 Aug 1998 16:47:30 +0200 From: Stefan Bethke To: hm@kts.org cc: FreeBSD Hackers Subject: Re: TCP checksum errors resulting from IP addr change Message-ID: <1193403.3113311650@d254.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry Demo (MacOS) [1.4.0b2, s/n Evaluation] 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 On Fre, 28. Aug 1998 9:22 Uhr +0200 Hellmuth Michaelis wrote: > Hi, > > I've posted this to -net without a reaction. Any reaction is welcome since > i totally ran out of ideas: > > > I'm trying to debug a strange effect occuring on a sync PPP ISDN interface > which is used to connect to a Cisco 1003 (on 192.76.124.10). > > To get an address dynamically from the remote side, the local PPP inter- > face (on 2.2.5-RELEASE) is set up with: > > ifconfig isppp0 link1 0.0.0.0 192.76.124.10 netmask 0xffffffff debug > > Now i telnet to 192.76.124.10 and the link gets established but the telnet > session doesn't. > > I looked at the traces and noticed the very first IP packet going out with > source address 0.0.0.0 to the Cisco - i removed that in the driver but > still the telnet session is not established. (btw. only the first session > is not established, if i terminate the first telnet and restart it on > the open link, it works immediately; but i want the first to work ...). > > I enabled TCP debugging on the Cisco, and for all the packets from this > first telnet session it says "TCP checksum error". > > So i think, IP address 0.0.0.0 is used for checksum calculation of the TCP > packets for this forst session, but the "real" IP address of the interface > changes to 192.something after the first packet and the TCP checksum is > somehow not recalculated causing checksum errors on the remote side (Is > this correct ?). The problem here is that as soon as telnet does it's connect(), the socket is completly bound for both local and remote address and port. The (bogus) local address will be kept until telnet closes the socket, disconnect it, or bind()s a new address. The TCP checksum errors result from ip_output() (or so, I have to check the source and/or Stevens for that) putting the first IP if_addr as the source address into the packet. TCP still will use the address bound to (0.0.0.0) and will calculate it's checksum based on that. > Is there a way to inform the TCP layer to recalculate checksums or to get > the new IP address from the interface ? No, IMO. > Do i have to recalculate the checksums for this session in the driver ? This might help in terms of a telnet session, but I'm pretty sure getsockname() will return 0.0.0.0, which in itself will cause some nasty problems (consider FTP). > Has anyone another hint or an idea how to solve this ? Basically, I feel, you have three options: - Until the real address is assigned, drop all packets with an error (ENETDOWN or such). This at least will be straightforward to implement, although not very pleasent to use. - Make the socket layer listen to routing messages, and update all sockets on an interface address change. This is probably complicated enought, and won't even help with a) programs doing getsockname() too early, and b) with subseqent address changes due to the line going down, then up again, thus being assigned a different address by the PPP server. - Implement a "mini" NAT inside of the interface, just as userland ppp does. The easiest solution however is to get a decent ISP :-) Cheers, Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.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 28 07:59:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27000 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 07:59:50 -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 HAA26992 for ; Fri, 28 Aug 1998 07:59:41 -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 AAA315; Fri, 28 Aug 1998 08:26:21 -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 IAA10588; Fri, 28 Aug 1998 08:26:25 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199808281426.IAA10588@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG cc: brhall@timing.com Subject: Help with passing fd on FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 08:26:25 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone give me pointers on passing open file descriptors on FreeBSD? This is covered in W. Richard Stevens Advanced programming book, but the structs in FreeBSD are slightly different, and I've never done this. Thanks, Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 08:16:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29803 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 08:16:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw2.att.com [192.128.52.90]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29783 for ; Fri, 28 Aug 1998 08:16:45 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig2.fw.att.com by cagw2.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Fri Aug 28 11:11 EDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig2.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id LAA17975 for ; Fri, 28 Aug 1998 11:15:34 -0400 (EDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Fri, 28 Aug 1998 11:15:30 -0400 Message-ID: To: stefan@promo.de, hm@kts.org Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: TCP checksum errors resulting from IP addr change Date: Fri, 28 Aug 1998 11:15:27 -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: Stefan Bethke [SMTP:stefan@promo.de] > > On Fre, 28. Aug 1998 9:22 Uhr +0200 Hellmuth Michaelis > wrote: > > > I'm trying to debug a strange effect occuring on a sync PPP ISDN > interface > > which is used to connect to a Cisco 1003 (on 192.76.124.10). > > > > To get an address dynamically from the remote side, the local PPP > inter- > > face (on 2.2.5-RELEASE) is set up with: > > > > ifconfig isppp0 link1 0.0.0.0 192.76.124.10 netmask 0xffffffff > debug > > > > Now i telnet to 192.76.124.10 and the link gets established but the > telnet > > session doesn't. > Sorry for a stupid question, but may it be related somehow to the header compression mode ? I'm not sure about the PPP compression but for SLIP these symptoms would clearly indicate that one side is working with compression while another one is working without compression. The SLIP compression works on a per-connection basis, so datagram packets and the TCP SYN packets are always not compressed - so ping works and you can establish the connection, but following TCP packets have their headers compressed by removing the redundant information that can be restored from previous TCP packets, so they would appear broken if the other side works in other mode. It may be that PPP is using something like this (and it also has 2 different compression modes). -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 08:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04001 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 08:43:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03957 for ; Fri, 28 Aug 1998 08:42:26 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id RAA00671; Fri, 28 Aug 1998 17:34:27 +0200 (CEST) Date: Fri, 28 Aug 1998 17:37:40 +0200 From: Stefan Bethke To: sbabkin@dcn.att.com cc: hm@kts.org, freebsd-hackers@FreeBSD.ORG Subject: RE: TCP checksum errors resulting from IP addr change Message-ID: <1374590.3113314660@d254.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry Demo (MacOS) [1.4.0b2, s/n Evaluation] 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 On Fre, 28. Aug 1998 11:15 Uhr -0400 sbabkin@dcn.att.com wrote: > Sorry for a stupid question, but may it be related somehow to the > header compression mode ? I'm not sure about the PPP compression but > for SLIP these symptoms would clearly indicate that one side is > working with compression while another one is working without > compression. The SLIP compression works on a per-connection > basis, so datagram packets and the TCP SYN packets are always not > compressed - so ping works and you can establish the connection, > but following TCP packets have their headers compressed by > removing the redundant information that can be restored from previous > TCP packets, so they would appear broken if the other side works > in other mode. It may be that PPP is using something like this > (and it also has 2 different compression modes). You could be right, but in this case, you aren't. It's no question of Van Jacobsen TCP header compression (this isn't particular to SLIP, but used in PPP indeed), but instead of wrong IP adresses in the headers. VJ compression works in isppp, AFAIK. Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.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 28 08:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04281 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 08:45:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04233 for ; Fri, 28 Aug 1998 08:45:14 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id KAA04626 for ; Fri, 28 Aug 1998 10:42:40 -0400 (EDT) Date: Fri, 28 Aug 1998 10:42:40 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-Hackers@FreeBSD.ORG Subject: ppp rate slowdown 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 am using user-mode ppp, connected to a host box that is also running FreeBSD, and it is also using user-mode ppp (host side). The host side ppp is about 3 months old, and my ppp is current. I'm experiencing a slowdown problem. When I first bring up ppp, I get the full rate that the dial up line allows (considering that it's via a compressing modem running at 28.8k, the async rate at both ends is 57.6k). Later, after running a longish ftp, if the ftp gets interrupted by something like mail, so that it has to slow down the transmit rate to share the line, the ftp rate will not improve from the rate that it had to slow down to. This will not improve on later ftp runs (even if those runs don't need to share the line, or if they are several hours later). The only way I've found to get the rate back up is to drop the ppp connection and re-initiate it. Are there any guesses as to why this might be occurring to me? ----------------------------+----------------------------------------------- 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 28 09:04:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07219 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:04:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07196 for ; Fri, 28 Aug 1998 09:04:07 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id SAA15662; Fri, 28 Aug 1998 18:02:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zCQyO-002ZjZC; Fri, 28 Aug 98 18:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Fri, 28 Aug 1998 17:42:25 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@FreeBSD.ORG; Fri, 28 Aug 1998 17:42:26 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: TCP checksum errors resulting from IP addr change In-Reply-To: from "sbabkin@dcn.att.com" at "Aug 28, 98 11:15:27 am" To: sbabkin@dcn.att.com Date: Fri, 28 Aug 1998 17:42:26 +0200 (CEST) Cc: stefan@promo.de, hm@kts.org, freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.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 sbabkin@dcn.att.com wrote: > Sorry for a stupid question, but may it be related somehow to the > header compression mode ? No, header compression (and no other compression or any other fancy things) is not used used on that interface. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 09:08:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08098 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:08:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles225.castles.com [208.214.165.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08086 for ; Fri, 28 Aug 1998 09:08:46 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA05334; Fri, 28 Aug 1998 09:06:00 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280906.JAA05334@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma cc: FreeBSD hackers mailing list Subject: Re: subr_autoconf.c In-reply-to: Your message of "Fri, 28 Aug 1998 16:32:13 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 09:05:58 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is the reason that subr_autoconf.c is UNUSED? NetBSD uses these > config_found functions to determine the devices that can be found after > a certain element has been attached to like, a pcibus implies the > probing pci devices that are compiled in. NetBSD uses the "new config" infrastructure to explicitly detail the relationship between devices and busses at compile time. This mechanism has a number of benefits, but also some shortcomings. > Is there in FreeBSD a general mechanism to attach devices? Do the > ISA, EISA and PCI bus code all implement their own way of handling > things? We are beginning a transition process away from each bus having its own discovery code, towards an implicit technique developed by Doug Rabson. This new architecture should be used for all new busses (including USB). See www.freebsd.org/~dfr/man9.diff for a set of manpages describing the new interface, and talk to Doug (dfr@freebsd.org) and Nicholas Souchu (nsouch@freebsd.org) about the implementation. I wouldn't mind keeping up with your progress either... -- \\ 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 28 09:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09277 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:16:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dirc.bris.ac.uk (dirc.bris.ac.uk [137.222.10.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09188 for ; Fri, 28 Aug 1998 09:16:11 -0700 (PDT) (envelope-from Tim.Borgeaud@bristol.ac.uk) Received: from zeus.bris.ac.uk by dirc.bris.ac.uk with SMTP-PRIV (PP) with ESMTP; Fri, 28 Aug 1998 17:15:02 +0100 Received: (from phtlb@localhost) by zeus.bris.ac.uk (8.8.8/8.8.7) id RAA27907 for freebsd-hackers@FreeBSD.ORG; Fri, 28 Aug 1998 17:14:45 +0100 (BST) From: Tim Borgeaud Message-Id: <199808281614.RAA27907@zeus.bris.ac.uk> Subject: RE: Why is my code failing with SIGFPE? To: freebsd-hackers@FreeBSD.ORG Date: Fri, 28 Aug 1998 17:14:45 +0100 (BST) X-Mailer: ELM [version 2.4 PL21] 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 Apologies to all. I have managed to find the problem in my code. I had missed out one of my include files. This had lead to a function being implicitly declared rather than declared as a function returning a double. After browsing the mail archives and some careful attention to compiling I found the error. I forget who wrote the message that described this function misdeclaration as a cause of SIGFPE. Thanks to whoever it was. Is this kind of behaviour from the compiler unavoidable? It took me ages to track down the bloody problem. As a novice programmer I was confused by the floating point exception and spent a long time wondering how my variables could have gone out of range. > > Sorry if this is bit off topic but I think someone reading the list can > probably help me. > > I have some C-code which fails with floating point exceptions (SIGFPE errors). > Code compiles cleanly, although I am not using any additional options to gcc. > > I am stumped as to the cause of these errors. Depending on where I put > print statements in the code (for debugging purposes) it fails at different > points. > > The code makes fairly heavy use of the CPU and is recursive. On the fourth call > of the recursive function the code fails with SIGFPE, sometimes in my code > without any reason that I can find, but also commonly in __dtoa (called during > printf of a floating point number). > > I have carefully gone through my code, sections of which seemed to be working > perfectly on their own. I cannot seem to find anything wrong. I can supply all or > parts of the code that I am trying to run if anyone is interested. I was hoping > that someone may have come across this kind of thing before. > > The code has also been compiled using djgpp under msdos and has the same > problem. Two machines (Pentium and Pentium MMX) produce the same results. > > I have tried to use gdb, but because I have never used it before it didn't help > very much. All I found was that some of the floating point variable were > scrambled after the failure (eg some ridculous number x10^230 or something). > > > Many thanks > > Tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 09:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10778 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:22:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.netsol.net (mail.netsol.net [38.216.109.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10764 for ; Fri, 28 Aug 1998 09:22:27 -0700 (PDT) (envelope-from matthew@netsol.net) Received: from Matt.pandaamerica.com ([198.186.216.114]) by mail1.netsol.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42781U2500L250S0) with SMTP id AAA168 for ; Fri, 28 Aug 1998 09:26:11 -0700 Message-ID: <00d701bdd29f$f601fb80$f0a8a8c0@Matt.pandaamerica.com> From: matthew@netsol.net (netsol,matthew) To: Subject: mozzila compile? Date: Fri, 28 Aug 1998 09:21:40 -0700 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i finally make the mozzila showed up in my x11 but the icons in the menu bar are all black white. is there any people ever sucessfully compiled and run mozzila? There is also a Xmlist error and is poping out anoyingly. It seams to be the motif thing. the motif i used is 2.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 28 09:26:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11341 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:26:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11224; Fri, 28 Aug 1998 09:26:04 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id MAA13763; Fri, 28 Aug 1998 12:21:06 -0400 (EDT) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Fri, 28 Aug 1998 12:21:05 -0400 (EDT) From: "Bruce M. Walter" To: freebsd-bugs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: kern/6102 (biodone: buffer already done) QUOTA? 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 > Once in a while kernel panics with following messages: > > biodone: buffer already done > biodone: buffer already done > panic: biodone: buffer not busy I had been experiencing these biodone panics under a similar configuration while performing backups to a SCSI DAT drive. Dima had built some diagnostic kernels to address FIFO overruns in the Adaptec controllers at Best. Since my HBA is a DPT, I put together some diagnostic kernels as well. What I found was that removing 'options QUOTA' from my kernel config has alleviated if not eliminated this problem. I have run over 20 consecutive backups with no failures. Previously, 1 in every 3 would fail with a system crash/silent reboot. Since I wasn't actually using the quotas, it's not a heartbreaker to lose them. I know Dima is running with QUOTA on, but I'm now wondering if some of the others experiencing kern/5117, kern/6102 and kern/7424 aren't running it as well. - Bruce ========================================================== || Bruce M. Walter || 426 South Dawson Street || || Principal || Raleigh, NC 27601 USA || || NIXdesign Group, Inc. || Tel: 919.829.4908 || || Concept + Code || Fax: 919.829.4993 || ========================================================== || BSD Unix -- It's not just a job, it's a way of life! || ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 09:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14626 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 09:44:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles225.castles.com [208.214.165.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14606 for ; Fri, 28 Aug 1998 09:44:16 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA05495; Fri, 28 Aug 1998 09:41:29 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280941.JAA05495@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Tim Borgeaud cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why is my code failing with SIGFPE? In-reply-to: Your message of "Fri, 28 Aug 1998 17:14:45 +0100." <199808281614.RAA27907@zeus.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 09:41:28 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apologies to all. I have managed to find the problem in my code. > > I had missed out one of my include files. This had lead to a function being > implicitly declared rather than declared as a function returning a double. > > After browsing the mail archives and some careful attention to compiling > I found the error. I forget who wrote the message that described this function > misdeclaration as a cause of SIGFPE. Thanks to whoever it was. > > Is this kind of behaviour from the compiler unavoidable? It took me ages to > track down the bloody problem. As a novice programmer I was confused by the > floating point exception and spent a long time wondering how my variables could > have gone out of range. It's a lesson: always study the compiler output. If you're just starting out, make sure you add '-ansi -Wall -Werror' to your compiler flags. This'll get you playing more attention to it. 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 Fri Aug 28 10:45:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22114 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 10:45:08 -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 KAA22092 for ; Fri, 28 Aug 1998 10:45:03 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA10592; Fri, 28 Aug 1998 10:42:37 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdy10586; Fri Aug 28 17:42:32 1998 Date: Fri, 28 Aug 1998 10:42:29 -0700 (PDT) From: Julian Elischer To: jallison@engr.sci.com cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling (fwd) 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 ---------- Forwarded message ---------- Date: Fri, 28 Aug 1998 00:36:04 +0200 (CEST) From: Stefan Bethke To: Terry Lambert Cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling On Thu, 27 Aug 1998, Terry Lambert wrote: > > > Netatalk seems like the wrong place to modify behavior to solve this > > > problem, which is a display problem, not an encoding problem. > > > > Where is the encoding defined for character values in the ranges between > > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > ISO 8859? Is this a standardized encoding for POSIX file names, or just a convention? If it only is a convention, what will non-latin script users think about it? How do we discriminate between different 8859 encodings? (Yeah, I see your point about "locales".) > > If you were right, it would be OK for afpd to store all chars literally. > > While this does work, it is definitly awkward to work with in the shell, > > and possibly so together with other applications as Samba as well. Its not > > merely an display issue; its an interoperability issue. I feel that too > > many things expect file names to confine to printable ascii, and unless > > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > > untouched). > > Per interoperability: This presumes, incorrectly, that Mac's support > the same idiotic idea of code pages as SAMBA must. Macs, in this sense, use a single "code page." I believe there is an escape mechanism to change the encoding to non-latin scripts, but I will have to look that up in Inside Mac. For AFP 2.1 (which netatalk claims to support to the extent the Macs use it), there is a single encoding defined, without any escape mechanism. > > It won't change anything to the worse; the only problem is that existing > > files with file names containing control characters (custom icons on folders > > being the single source of such name probably) will stop working and will > > need manual assistance from an operator. > > It will break a number of things. It already breaks the file name > length limitation in SAMBA. Duplicating this break into Appletalk is, > IMO, a bad idea. I don't know much about SMB/CIFS/Samba. What is the filename length limit (as opposed, possibly, to the pathname limit)? AFP has a filename length limitation to 31 bytes/chars. All Unix-based AFP servers I know of choose to drop files with longer names. Also, at least two commercial products use the same mechanism for escaping non-ASCII chars. > If you are going to push this hard, you should consider Internataional > representation ofile names by client locale, and how it is already > handled. Would you mind to point me to any information shedding light on standardisation efforts for file name representation? In terms of "locale", this would mean that "Mac" or "AFP" would be it's own locale in terms of file name character encoding? After all, I see three possible ways: - improve interoperability by confining to printable ASCII (or ISO-8859-1, or...) and not escaping other glyphs, thus breaking AFP conformance; - escaping all glyphs (or rather their encoding) in a way that preserves the full AFP filename encoding space (for filenames, this is 0x01 to 0xff, with ":" being illegal as it is the path delimiter), but using printable ASCII where possible (this is, I believe, what netatalk tries to do, but doesn't, due to a stupid bug). - translate the AFP filename encoding space into some larger glyph encoding space, such as Unicode, or, more specifically, UTF-8. The last one probably is the way to go, but this would require (at least to me) some testimonial that Unicode in general and UTF-8 in particular is the way to go for file names in FreeBSD. This of course would probably start other interop problems with NFS and alike, and it would require samba to deal with CP bogosities in its own right instead of putting it in the face of every other app. > Novell servers are another case where the server assumes all clients > exist in a given locale; this would be a mistake to buy into... Yep. Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany 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 28 10:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24188 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 10:59:57 -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 KAA24182 for ; Fri, 28 Aug 1998 10:59:50 -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 AAA335; Fri, 28 Aug 1998 11:22:46 -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 LAA10931; Fri, 28 Aug 1998 11:22:26 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199808281722.LAA10931@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG Cc: brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-reply-to: Your message of "Fri, 28 Aug 1998 08:26:25 MDT." <199808281426.IAA10588@count.timing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 11:22:26 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD struct. The Stevens book appears to have a good example. > > Can someone give me pointers on passing open file descriptors on FreeBSD? > This is covered in W. Richard Stevens Advanced programming book, but > the structs in FreeBSD are slightly different, and I've never done this. > > Thanks, > Craig > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 11:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27510 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 11:27:04 -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 LAA27503 for ; Fri, 28 Aug 1998 11:27:01 -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 SAA05374; Fri, 28 Aug 1998 18:28:37 +0200 From: Luigi Rizzo Message-Id: <199808281628.SAA05374@labinfo.iet.unipi.it> Subject: Re: Help with passing fd on FreeBSD To: chanders@timing.com (Craig Anderson) Date: Fri, 28 Aug 1998 18:28:36 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-Reply-To: <199808281722.LAA10931@count.timing.com> from "Craig Anderson" at Aug 28, 98 11:22:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD > struct. The Stevens book appears to have a good example. > > > Can someone give me pointers on passing open file descriptors on FreeBSD? still, this looks to me one of the most obscure interfaces in the OS. Does any real application use that ? cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~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 28 11:43:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29433 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 11:43:19 -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 LAA29406 for ; Fri, 28 Aug 1998 11:42:59 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 29487 invoked by uid 1001); 28 Aug 1998 18:42:00 +0000 (GMT) To: luigi@labinfo.iet.unipi.it Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help with passing fd on FreeBSD In-Reply-To: Your message of "Fri, 28 Aug 1998 18:28:36 +0200 (MET DST)" References: <199808281628.SAA05374@labinfo.iet.unipi.it> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 28 Aug 1998 20:41:59 +0200 Message-ID: <29485.904329719@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? Have a look at the diablo News system: http://www.backplane.com/diablo/ Runs very well on FreeBSD. 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 Fri Aug 28 11:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01400 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 11:54:29 -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 LAA01385 for ; Fri, 28 Aug 1998 11:54:18 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA26975; Fri, 28 Aug 1998 11:53:24 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd026954; Fri Aug 28 11:53:21 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA28895; Fri, 28 Aug 1998 11:53:20 -0700 (MST) From: Terry Lambert Message-Id: <199808281853.LAA28895@usr02.primenet.com> Subject: Re: Weird sendmail/pop problem To: don@whtech.com (Don O'Neil) Date: Fri, 28 Aug 1998 18:53:20 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <000301bdd231$d6cafe60$0200010a@digerati.whtech.com> from "Don O'Neil" at Aug 27, 98 08:13:33 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 experiencing a weird sendmail problem.. Anyone have any clues where to > start looking for this? > > Here goes: > > I have a user on my box that is set up to forward mail to 2 people... > > When I send mail using MS Outlook 98 through a pop3 connection the second > person in the .forward file gets the message but the first one doesnt. > > When I go outside of my box and send mail to the user, then BOTH people in > the .forward file get the message... > > I've checked the aliases db, any .forward files laying around on the > machine, and all the basic configs for pop3 and sendmail but have come up > empty handed... > > Any ideas? Where does POP3 come into this? You can't send mail over a POP3 connection, you can only retrieve it; you use SMTP to *send* mail. This is most likely a problem with the way the mail is being retrieved, not the way it is sent. This is really a question for your SMTP and POP3 server vendors. No one here will be able to answer your question unless you put the full body of the .forward file, a message that got through, and the message that got through to only the second mailbox, up on a WWW site somewhere and post the URL. Include the name and versions of your POP3 and SMTP servers, as well. 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 28 11:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02109 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 11:59:45 -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 LAA02093 for ; Fri, 28 Aug 1998 11:59:37 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id LAA22815; Fri, 28 Aug 1998 11:58:32 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd022743; Fri Aug 28 11:58:27 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA29132; Fri, 28 Aug 1998 11:57:55 -0700 (MST) From: Terry Lambert Message-Id: <199808281857.LAA29132@usr02.primenet.com> Subject: Re: PCI devices To: reilly@zeta.org.au (Andrew Reilly) Date: Fri, 28 Aug 1998 18:57:55 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, tony@dell.com, wpaul@skynet.ctr.columbia.edu, chuckr@glue.umd.edu, hackers@FreeBSD.ORG In-Reply-To: <19980828143503.A9421@reilly.home> from "Andrew Reilly" at Aug 28, 98 02: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 > > 1) All legacy ISA device ROMs are required to begin on a 2K > > 2) All PnP device ROMS have the same requirements. But as of > > 3) On a non-PnP-BIOS machine, devices in the boot path will be > > 4) The PnP OS can then: > > What happens with legacy ISA devices that don't have a ROM? > I know one or two of those. You have two options: 1) FreeBSD probes and finds them, and thus knows their resources. 2) You run the visual config, and enter in the resources used by the devices, telling FreeBSD the information that it can not probe, and thus FreeBSD knows their resources. This is the same thing you can do on newer PnP BIOS implementaiotns (but not all PnP BIOS implementations), where you go into the CMOS setup and tell the system about your legacy ISA cards. In other words, legacy ISA devices communicate with the PnP system by relaying the relevent information through a human (you). 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 28 12:04:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02981 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 12:04:16 -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 MAA02970 for ; Fri, 28 Aug 1998 12:04:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00381; Fri, 28 Aug 1998 12:00:49 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808281200.MAA00381@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: chanders@timing.com (Craig Anderson), freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-reply-to: Your message of "Fri, 28 Aug 1998 18:28:36 +0200." <199808281628.SAA05374@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 12:00:49 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD > > struct. The Stevens book appears to have a good example. > > > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? I've used it before for passing client connections off from a server to a preforked long-lived "work slave". It's quite handy for that sort of thing - especially with network connections where you can't just pass a reference in filename space. -- \\ 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 28 12:34:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06632 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 12:34:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA06580 for ; Fri, 28 Aug 1998 12:34:26 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 20773 invoked by uid 1003); 28 Aug 1998 19:14:04 -0000 Message-ID: <19980828211404.A18096@rucus.ru.ac.za> Date: Fri, 28 Aug 1998 21:14:04 +0200 From: Neil Blakey-Milner To: Luigi Rizzo , Craig Anderson Cc: freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD References: <199808281722.LAA10931@count.timing.com> <199808281628.SAA05374@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199808281628.SAA05374@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Aug 28, 1998 at 06:28:36PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 1998-08-28 (18:28), Luigi Rizzo wrote: > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? In the Stevens book, he says: "1. A process forks a child process and the child then execs another process to open a particular file. The execed process does whatever it has to do to open the file and then passes the open file descriptor back to the original process, since the execed process is a child process of the orifinal process, there s no way for it to pass an open file back to the parent, other than passing an open file as we describe in this section." "2. A connection server can be incoked to handle all network connections. Instead of using fork and exec as described above, this secario requires any client process to connect with a well-known server. The client writes its request to the server using this connection (a Unix domain stream socket, for example), and the server responds with an open file descriptor or an error indication." I think this could be used to point children towards files to read for further input, or something like that. I'm not terribly sure, but the children may then need not be run as root to read files not owned by their process id (one assumes the child uses set[gu]id). Of course, I'm sure there are better ways of doing these things. I'm not sure how apache logs to files owned by other users (apache set[gu]id's its children), this may be the way. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 12:35:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06766 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 12:35:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA06736 for ; Fri, 28 Aug 1998 12:35:36 -0700 (PDT) (envelope-from leisner@sdsp.mc.xerox.com) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <52391(1)>; Fri, 28 Aug 1998 12:34:04 PDT Received: from gnu.sdsp.mc.xerox.com (gnu [13.231.133.90]) by gemini.sdsp.mc.xerox.com (8.8.7/8.8.7) with SMTP id PAA29501; Fri, 28 Aug 1998 15:29:44 -0400 (EDT) Received: from gnu (localhost) by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA27016; Fri, 28 Aug 98 15:29:43 EDT Message-Id: <9808281929.AA27016@gnu.sdsp.mc.xerox.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo Cc: chanders@timing.com (Craig Anderson), freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-Reply-To: Your message of "Fri, 28 Aug 1998 09:28:36 PDT." <199808281628.SAA05374@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 12:29:43 PDT From: "Marty Leisner" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD > > struct. The Stevens book appears to have a good example. > > > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? > > cheers > luigi If you have cooperating processes, and you want to create a pipe at runtime, how do you pass it between processes? (wihtout having to make a named pipe)... In the systems I build at work, its fundaemntal. When I was first asked to do it (and told how), I never knew it existed before... I think bsd4.4 can pass an array of fd's, older bsd style OSes were limited to one fd...(?) -- marty leisner@sdsp.mc.xerox.com The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer Murray Gell-mann in the NY Times To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 13:15:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14056 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 13:15:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14018; Fri, 28 Aug 1998 13:15:36 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id PAA06254; Fri, 28 Aug 1998 15:13:05 -0400 (EDT) Date: Fri, 28 Aug 1998 15:13:05 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-Hackers@FreeBSD.ORG cc: FreeBSD Ports Team Subject: ButtFace 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 laughing at this, but it's real. I was trying to get a package called mpsql to port, and couldn't get it to link. It kept on wanting a symbol called _XmCreatePixmapPushButton, and I couldn't find what library it was in. Finally found it in /usr/X11R6/lib/libButtFace.a. Nearly fell over laughing at the name. That's the one, all right, but in trying to figure out what mpsql wants to depend on, I need to find out where this ButtFace thing came from. Its on a pixmap thing (not from the xpm port), and I just can't locate it. Anyone remember this odd fella? ----------------------------+----------------------------------------------- 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 28 14:14:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22898 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 14:14:00 -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 OAA22889 for ; Fri, 28 Aug 1998 14:13:55 -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 OAA00331 for ; Fri, 28 Aug 1998 14:12:19 -0700 (PDT) Date: Fri, 28 Aug 1998 14:12:18 -0700 (PDT) From: Chris Coleman To: FreeBSD-Hackers@FreeBSD.ORG Subject: Optimizing FreeBSD for Maximum Performance. 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 Would someone be interested in writing an article on how to optimize a FreeBSD server for maximum performance? Reply to me directly. http://ezine.freebsd.org/ http://www.daemonnews.org/ -Chris (Daemon-News Editor) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 28 14:25:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24937 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 14:25:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts05-035.dublin.indigo.ie [194.125.220.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24920 for ; Fri, 28 Aug 1998 14:24:39 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01126; Fri, 28 Aug 1998 22:15:48 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808282115.WAA01126@indigo.ie> Date: Fri, 28 Aug 1998 22:15:22 +0000 In-Reply-To: <199808281628.SAA05374@labinfo.iet.unipi.it>; Luigi Rizzo 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: Luigi Rizzo , chanders@timing.com (Craig Anderson) Subject: Re: Help with passing fd on FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, brhall@timing.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 28, 6:28pm, Luigi Rizzo wrote: } Subject: Re: Help with passing fd on FreeBSD > > Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD > > struct. The Stevens book appears to have a good example. > > > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? I can imagine several uses for it, one of the most useful being a centralised authentication daemon which passes out raw sockets, sockets < 1024 etc to appropriately authorised processes. fhttpd also uses it a lot. 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 Fri Aug 28 16:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10965 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 16:44:08 -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 QAA10898 for ; Fri, 28 Aug 1998 16:44:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-94.camalott.com [208.229.74.94]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA22908; Fri, 28 Aug 1998 18:44:53 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA00847; Fri, 28 Aug 1998 18:43:04 -0500 (CDT) (envelope-from joelh) Date: Fri, 28 Aug 1998 18:43:04 -0500 (CDT) Message-Id: <199808282343.SAA00847@detlev.UUCP> To: chanders@timing.com CC: freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-reply-to: <199808281426.IAA10588@count.timing.com> (chanders@timing.com) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808281426.IAA10588@count.timing.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can someone give me pointers on passing open file descriptors on FreeBSD? > This is covered in W. Richard Stevens Advanced programming book, but > the structs in FreeBSD are slightly different, and I've never done this. I've got a library that does exactly this. It's not that hard, really. Gimmie a place to FTP it to and I'll send it over. 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 Fri Aug 28 18:13:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19987 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 18:13:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA19969 for ; Fri, 28 Aug 1998 18:13:15 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA28236; Fri, 28 Aug 1998 21:14:48 -0400 From: Bill Paul Message-Id: <199808290114.VAA28236@skynet.ctr.columbia.edu> Subject: Re: Help with passing fd on FreeBSD To: chanders@timing.com (Craig Anderson) Date: Fri, 28 Aug 1998 21:14:46 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808281426.IAA10588@count.timing.com> from "Craig Anderson" at Aug 28, 98 08:26:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Craig Anderson had to walk into mine and say: > > Can someone give me pointers on passing open file descriptors on FreeBSD? > This is covered in W. Richard Stevens Advanced programming book, but > the structs in FreeBSD are slightly different, and I've never done this. > > Thanks, > Craig Sure. Appended to this message are two small programs: r.c and s.c. s.c sends a descriptor and r.c receives it. Last time I used this was on FreeBSD 2.1.0 but it should still work. The descriptor being sent is actually the AF_LOCAL socket that s.c creates to talk to r.c, which is kind of pointless but you can use any other descriptor index you want (as long as it refers to a valid open descriptor). -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= #include #include #include #include #include #include #include #include #include #include #include #include #include #ifndef lint static const char rcsid[] = "$Id: r.c,v 1.4 1998/08/29 01:03:52 wpaul Exp $"; #endif struct cmessage { struct cmsghdr cmsg; int fd; }; int main() { struct iovec iov[1]; struct msghdr msg; struct cmessage cm; struct sockaddr_un sun; int s; int sock; int len; fd_set readfds; char recbuf[1024]; if (unlink("/tmp/testsock") == -1) warn("couldn't remove old socket"); strcpy(sun.sun_path, "/tmp/testsock"); sun.sun_family = AF_UNIX; len = sun.sun_len = sizeof(sun.sun_len) + sizeof(sun.sun_family) + strlen(sun.sun_path) + 1; if ((s = socket(AF_UNIX, SOCK_STREAM, 0)) == -1) err(1, "socket creation failed"); iov[0].iov_base = (char *)&recbuf; iov[0].iov_len = sizeof(recbuf); bzero((char *)&cm, sizeof(cm)); bzero((char *)&msg, sizeof(msg)); msg.msg_iov = iov; msg.msg_iovlen = 1; msg.msg_name = NULL; msg.msg_namelen = 0; msg.msg_control = (caddr_t)&cm; msg.msg_controllen = sizeof(struct cmessage); msg.msg_flags = 0; if (bind(s, (struct sockaddr *)&sun, len) == -1) err(1, "couldn't bind socket"); listen(s, 2); if ((sock = accept(s, (struct sockaddr *)&sun, &len)) == -1) err(1, "accept failed"); FD_ZERO(&readfds); FD_SET(sock, &readfds); select(FD_SETSIZE, &readfds, NULL, NULL, NULL); if ((len = recvmsg(sock, &msg, 0)) == -1) err(1, "recvmsg failed"); printf ("read %d bytes\n", len); printf ("data: %s\n", iov[0].iov_base); if (cm.cmsg.cmsg_type != SCM_RIGHTS) warnx("message didn't contain SCM_RIGHTS"); printf ("FD: %d\n", cm.fd); close(sock); close(s); exit(0); } #include #include #include #include #include #include #include #include #include #include #include #include #include #ifndef lint static const char rcsid[] = "$Id: s.c,v 1.4 1998/08/29 01:05:28 wpaul Exp $"; #endif struct cmessage { struct cmsghdr cmsg; int fd; }; int main() { struct iovec iov[1]; struct msghdr msg; struct cmessage cm; struct sockaddr_un sun; int s; int len; char sendbuf[] = "This is a test buffer."; strcpy(sun.sun_path, "/tmp/testsock"); sun.sun_family = AF_UNIX; len = sun.sun_len = sizeof(sun.sun_len) + sizeof(sun.sun_family) + strlen(sun.sun_path) + 1; if ((s = socket(AF_UNIX, SOCK_STREAM, 0)) == -1) err(1, "socket creation failed"); if (connect(s, (struct sockaddr *)&sun, len) == -1) err(1, "couldn't connect socket"); iov[0].iov_base = (char *)&sendbuf; iov[0].iov_len = sizeof(sendbuf); cm.cmsg.cmsg_type = SCM_RIGHTS; cm.cmsg.cmsg_level = SOL_SOCKET; cm.cmsg.cmsg_len = sizeof(struct cmessage); cm.fd = s; /* file descriptor to be transfered */ msg.msg_iov = iov; msg.msg_iovlen = 1; msg.msg_name = NULL; msg.msg_namelen = 0; msg.msg_control = (caddr_t)&cm; msg.msg_controllen = sizeof(struct cmessage); msg.msg_flags = 0; if ((len = sendmsg(s, &msg, 0)) == -1) err(1, "sendmsg failed"); printf ("sent message (%d bytes), sending data...\n", len); close(s); exit(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 28 23:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18544 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 23:15:48 -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 XAA18529 for ; Fri, 28 Aug 1998 23:15:39 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-99.camalott.com [208.229.74.99]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id BAA11963; Sat, 29 Aug 1998 01:13:09 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id BAA01339; Sat, 29 Aug 1998 01:10:47 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 01:10:47 -0500 (CDT) Message-Id: <199808290610.BAA01339@detlev.UUCP> To: luigi@labinfo.iet.unipi.it CC: chanders@timing.com, freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-reply-to: <199808281628.SAA05374@labinfo.iet.unipi.it> (message from Luigi Rizzo on Fri, 28 Aug 1998 18:28:36 +0200 (MET DST)) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808281628.SAA05374@labinfo.iet.unipi.it> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Can someone give me pointers on passing open file descriptors on >>> FreeBSD? >> Oops, I turned the page and the BSD4.3+ example looks like the >> FreeBSD struct. The Stevens book appears to have a good example. > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? Emacs will in the next release (20.4). 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 Fri Aug 28 23:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19332 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 23:22:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19327 for ; Fri, 28 Aug 1998 23:22:11 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id BAA27462; Sat, 29 Aug 1998 01:21:08 -0500 (CDT) Message-ID: <19980829012108.51411@futuresouth.com> Date: Sat, 29 Aug 1998 01:21:08 -0500 From: "Matthew D. Fuller" To: Terry Lambert Cc: "Don O'Neil" , hackers@FreeBSD.ORG Subject: Re: Weird sendmail/pop problem References: <000301bdd231$d6cafe60$0200010a@digerati.whtech.com> <199808281853.LAA28895@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199808281853.LAA28895@usr02.primenet.com>; from Terry Lambert on Fri, Aug 28, 1998 at 06:53:20PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 28, 1998 at 06:53:20PM +0000, Terry Lambert woke me up to tell me: > > I'm experiencing a weird sendmail problem.. Anyone have any clues where to > > start looking for this? > > > > Here goes: > > > > I have a user on my box that is set up to forward mail to 2 people... > > > > When I send mail using MS Outlook 98 through a pop3 connection the second > > person in the .forward file gets the message but the first one doesnt. > > > > When I go outside of my box and send mail to the user, then BOTH people in > > the .forward file get the message... > > > > I've checked the aliases db, any .forward files laying around on the > > machine, and all the basic configs for pop3 and sendmail but have come up > > empty handed... > > > > Any ideas? > > Where does POP3 come into this? > > You can't send mail over a POP3 connection, you can only retrieve it; > you use SMTP to *send* mail. Before anyone else chimes in, there's some funky POP3 interface to send mail to the server via it. That said, it's still being DELIVERED through SMTP, so your point stands. Here's my bet: Try sending from the local box, not though POP3 mail -s 'test msg' forwarduser < /dev/null See if that gets there (both theres). Try (perhaps long shot, but *shrug*) killing sendmail and restarting it. Other than that... There's my $0.02 on it. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | 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 28 23:27:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19851 for freebsd-hackers-outgoing; Fri, 28 Aug 1998 23:27:15 -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 XAA19836 for ; Fri, 28 Aug 1998 23:27:04 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-99.camalott.com [208.229.74.99]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id BAA12278; Sat, 29 Aug 1998 01:24:38 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id BAA01509; Sat, 29 Aug 1998 01:22:48 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 01:22:48 -0500 (CDT) Message-Id: <199808290622.BAA01509@detlev.UUCP> To: nbm@rucus.ru.ac.za CC: luigi@labinfo.iet.unipi.it, chanders@timing.com, freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-reply-to: <19980828211404.A18096@rucus.ru.ac.za> (message from Neil Blakey-Milner on Fri, 28 Aug 1998 21:14:04 +0200) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808281722.LAA10931@count.timing.com> <199808281628.SAA05374@labinfo.iet.unipi.it> <19980828211404.A18096@rucus.ru.ac.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> Can someone give me pointers on passing open file descriptors on >>>> FreeBSD? >> still, this looks to me one of the most obscure interfaces in the OS. >> Does any real application use that ? > I think this could be used to point children towards files to read > for further input, or something like that. You've got it backwards. To send a child process a fd at fork time, you've just got to dup2 to a known (predetermined or passed at runtime) fd before forking. Mike mentioned using it to pass fd's (in his case, network sockets) to a preforked process, but that's a slightly different case. > I'm not terribly sure, but the children may then need not be run as > root to read files not owned by their process id (one assumes the ^^^^^^^ user > child uses set[gu]id). Once a process has an fd, it stays, regardless of setuid's. The uid/gid is checked when a file is opened, but not after. (This also means that a process can receive a fd passed to it, either in its creation (via fork) or by SCM_RIGHTS regardless of permissions.) Emacs 20.4 will use the mechanism in just the way that Stevens' example 1 mentioned. It can launch a suid root child which can pass it back an fd that Emacs would not otherwise be able to handle. (It does this to allow sysadmins to manipulate files as root while logged in as a mortal, assuming authentication passes.) > Of course, I'm sure there are better ways of doing these things. I'm not > sure how apache logs to files owned by other users (apache set[gu]id's its > children), this may be the way. It could easily open the files as root (and with O_APPEND) before forking. 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 29 00:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24389 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 00:18:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24384 for ; Sat, 29 Aug 1998 00:18:14 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id QAA10484; Sat, 29 Aug 1998 16:16:54 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id QAA18633; Sat, 29 Aug 1998 16:16:53 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id PAA02760; Sat, 29 Aug 1998 15:55:40 +0900 (JST) To: mike@smith.net.au Cc: doconnor@gsoft.com.au, freebsd-hackers@FreeBSD.ORG, pvernon@purdue.edu, max@wide.ad.jp, jkh@time.cdrom.com, abial@nask.pl Subject: Re: question From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Fri, 28 Aug 1998 00:07:30 +0000" <199808280007.AAA01954@word.smith.net.au> References: <199808280007.AAA01954@word.smith.net.au> X-Mailer: Mew version 1.92.4 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: <19980829155537G.masafumi@aslm.rim.or.jp> Date: Sat, 29 Aug 1998 15:55:37 +0900 X-Dispatcher: imput version 971024 Lines: 27 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> On 27-Aug-98 Mike Smith wrote: >> > > And what about making the boot code emit a short beep when it displays >> > > the boot: prompt? >> > >> > How about: >> > >> > # cat >> /boot/boot.conf >> > echo ^G >> Shouldn't that be boot.help? > Hmm, actually that would be the place to put it in the current > scenario, yes. /boot/boot.banner is where it would go with the "new" > bootstrap. I tested this on my box. I added three ^G to the end of boot.help and it worked very well. Once proper documentation is provided (I will write something for either FAQ or the handbook), this will help many people who want to install FreeBSD to PC without a display monitor. I will make this change to /sys/i386/boot/biosboot/boot.help if I don't hear any objection within next a few days. Maybe same change can be brought into picobsd? Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 00:53:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27564 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 00:53:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27545 for ; Sat, 29 Aug 1998 00:53:47 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA01520; Sat, 29 Aug 1998 00:50:27 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808290050.AAA01520@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Sat, 29 Aug 1998 15:55:37 +0900." <19980829155537G.masafumi@aslm.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 00:50:25 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I tested this on my box. I added three ^G to the end of boot.help and > it worked very well. Once proper documentation is provided (I will > write something for either FAQ or the handbook), this will help many > people who want to install FreeBSD to PC without a display monitor. > > I will make this change to /sys/i386/boot/biosboot/boot.help if I > don't hear any objection within next a few days. I'm not sure that this would be popular in the general case; I would certainly be less than thrilled to have my systems screaming at me every time I reboot, and while I can easily do something about this, it's less simple to explain to what does amount to the majority of our userbase why their systems are so noisy. For the installation, I can appreciate that this is an excellent idea, and it should be quite easy to add these to the release makefile. But once the system is installed, it ought to be configured to default to the serial console, removing the need for the tone at all. This, I expect along with a number of other things, would make a good start for an "accessibility pack", or a set of accessibility-related customisations which should be configurable at install time. -- \\ 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 29 01:01:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28641 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 01:01:17 -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 BAA28636 for ; Sat, 29 Aug 1998 01:01:14 -0700 (PDT) (envelope-from kbyanc@freedomnet.com) Received: (from kbyanc@localhost) by freedomnet.com (8.8.7/8.8.7/antispam) id DAA07731; Sat, 29 Aug 1998 03:55:43 -0400 (EDT) X-Envelope-To: freebsd-hackers@freebsd.org Date: Sat, 29 Aug 1998 03:55:41 -0400 (EDT) From: Kelly Yancey To: freebsd-hackers@FreeBSD.ORG Subject: determining an X window ID? 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 have written a fairly short shell script to launch xmcd which first checks to see if any other cd player is already running and if so, does not launch another instance of xmcd (for when I click on the wrong thing :) ) Anyway, I'm running fvwm2 and thought it would sure be nice if I could somehow have the script bring the already running cd player to the foreground...kind of a "Here it dummy" response. It's starting to look like this seemingly simple task is anything but. I guess the question is: is there anyway to get the X window ID for a process? And if so, other than writing my own X app or fvwm module, is there anyway to tell X to bring that window ID to the foreground. I was thinking that if I could somehow just get the fvwm command "windowid raisefocus" to fvwm2 everything would be good.... (raisefocus does just what it says...issues a Raise and then a Focus command). Any insight would be much appreciated. 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 Sat Aug 29 02:33:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05927 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 02:33:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05880 for ; Sat, 29 Aug 1998 02:33:00 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id LAA26782 for ; Sat, 29 Aug 1998 11:32:04 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zChMZ-002ZjZC; Sat, 29 Aug 98 11:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Sat, 29 Aug 1998 11:04:33 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@freebsd.org; Sat, 29 Aug 1998 11:04:33 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: TCP checksum errors resulting from IP addr change In-Reply-To: from Hellmuth Michaelis at "Aug 28, 98 09:22:43 am" To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) Date: Sat, 29 Aug 1998 11:04:33 +0200 (CEST) Organization: Kitchen Table Systems Reply-To: hm@kts.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 Hellmuth Michaelis wrote: > To get an address dynamically from the remote side, the local PPP inter- > face (on 2.2.5-RELEASE) is set up with: > > ifconfig isppp0 link1 0.0.0.0 192.76.124.10 netmask 0xffffffff debug > > Now i telnet to 192.76.124.10 and the link gets established but the telnet > session doesn't. Just to follow up to myself, i'm glad i'm not the first seeing this phenomenon, see http://www.freebsd.org/FAQ/FAQ176.html. But there seem to be not much interest in solving (not even discussing) this problem, so i'll leave it as it is. hellmuth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 02:43:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06847 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 02:43:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06840 for ; Sat, 29 Aug 1998 02:43:15 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:q4/tK56NzwYIR67WJOJ79uo+XHfGpSNL@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id SAA04446 for ; Sat, 29 Aug 1998 18:42:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA01516; Sat, 29 Aug 1998 18:51:44 +0900 (JST) Message-Id: <199808290951.SAA01516@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-hackers@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: question In-reply-to: Your message of "Sat, 29 Aug 1998 00:50:25 GMT." <199808290050.AAA01520@word.smith.net.au> References: <199808290050.AAA01520@word.smith.net.au> Date: Sat, 29 Aug 1998 18:51:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I tested this on my box. I added three ^G to the end of boot.help and >> it worked very well. Once proper documentation is provided (I will >> write something for either FAQ or the handbook), this will help many >> people who want to install FreeBSD to PC without a display monitor. >> >> I will make this change to /sys/i386/boot/biosboot/boot.help if I >> don't hear any objection within next a few days. > >I'm not sure that this would be popular in the general case; I would >certainly be less than thrilled to have my systems screaming at me >every time I reboot, and while I can easily do something about this, >it's less simple to explain to what does amount to the majority of our >userbase why their systems are so noisy. I wonder if this is such a big deal. After all, BIOS beeps during POST when the box is switched on.... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 07:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01625 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 07:44:59 -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 HAA01619 for ; Sat, 29 Aug 1998 07:44:56 -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 OAA06042; Sat, 29 Aug 1998 14:46:42 +0200 From: Luigi Rizzo Message-Id: <199808291246.OAA06042@labinfo.iet.unipi.it> Subject: Re: Help with passing fd on FreeBSD To: joelh@gnu.org Date: Sat, 29 Aug 1998 14:46:42 +0200 (MET DST) Cc: chanders@timing.com, freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-Reply-To: <199808290610.BAA01339@detlev.UUCP> from "Joel Ray Holveck" at Aug 29, 98 01:10:28 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> Can someone give me pointers on passing open file descriptors on ... > > still, this looks to me one of the most obscure interfaces in the OS. > > Does any real application use that ? ... > Emacs will in the next release (20.4). of course... is there anything that emacs does not use :) cheers (and sorry, i couldn't resist!) luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 10:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13855 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 10:09:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles153.castles.com [208.214.165.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13850 for ; Sat, 29 Aug 1998 10:09:33 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id KAA07212; Sat, 29 Aug 1998 10:06:40 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808291006.KAA07212@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Sat, 29 Aug 1998 18:51:44 +0900." <199808290951.SAA01516@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 10:06:39 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I tested this on my box. I added three ^G to the end of boot.help and > >> it worked very well. Once proper documentation is provided (I will > >> write something for either FAQ or the handbook), this will help many > >> people who want to install FreeBSD to PC without a display monitor. > >> > >> I will make this change to /sys/i386/boot/biosboot/boot.help if I > >> don't hear any objection within next a few days. > > > >I'm not sure that this would be popular in the general case; I would > >certainly be less than thrilled to have my systems screaming at me > >every time I reboot, and while I can easily do something about this, > >it's less simple to explain to what does amount to the majority of our > >userbase why their systems are so noisy. > > I wonder if this is such a big deal. > After all, BIOS beeps during POST when the box is switched on.... Some do, and only once. But how many operating systems beep like that every time you boot? Most would only do it in a severe error case. People are suprisingly touchy about things that go "beep" - it wouldn't surprise me if it was worse than the "what are all those error messages scrolling past?!" response to the probe output. -- \\ 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 29 10:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15440 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 10:29:43 -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 KAA15429 for ; Sat, 29 Aug 1998 10:29:41 -0700 (PDT) (envelope-from dirk.vangulik@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with ESMTP id TAA20502; Sat, 29 Aug 1998 19:28:32 +0200 (MET DST) Received: (from dirkx@localhost) by elpc36.jrc.it (8.8.8/8.8.7) id TAA07291; Sat, 29 Aug 1998 19:29:10 +0200 (CEST) (envelope-from dirkx) Date: Sat, 29 Aug 1998 19:29:10 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@elpc36.jrc.it To: chanders@timing.com cc: Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Help with passing fd on FreeBSD 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 Sat, 29 Aug 1998, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Craig Anderson > had to walk into mine and say: > > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > This is covered in W. Richard Stevens Advanced programming book, but > > the structs in FreeBSD are slightly different, and I've never done this. > > Sure. Appended to this message are two small programs: r.c and s.c. > s.c sends a descriptor and r.c receives it. Last time I used this > was on FreeBSD 2.1.0 but it should still work. The descriptor being > sent is actually the AF_LOCAL socket that s.c creates to talk to > r.c, which is kind of pointless but you can use any other descriptor > index you want (as long as it refers to a valid open descriptor). I struggeled with the same, in particular as the most recent book of Stevens uses the API as described in RFC2292. And two of the macro's are not quite part of socket.h. (why is this actually?) Below is Bill Pauls example again, but now with the newer (supposedly IPv6 compliant macros), they are just patched/diff-ed back in with a #define. Note that it is just the way of writing, as it al boils down to the same thing of course. But I just found it easier myself to write it down that way to follow the examples. See secion 4.3.x of the RFC for more details. Dw. #include #include #include #include #include #include #include #include #include #include #include #include #include #ifdef RFC2292API #include /* for ALIGN */ #endif /* RFC2292API */ #ifndef lint #ifndef RFC2292API static const char rcsid[] = "$Id: r.c,v 1.4 1998/08/29 01:03:52 wpaul Exp $"; #else static const char rcsid[] = "$Id: r.c,v 1.4 1998/08/30 07:21:10 dirkx Exp $"; #endif /* RFC2292API */ #endif #ifndef RFC2292API struct cmessage { struct cmsghdr cmsg; int fd; }; #else #ifndef CMSG_LEN # define CMSG_LEN(x) (ALIGN(sizeof(struct cmsghdr)) + ALIGN(x)) #endif #ifndef CMSG_SPACE # define CMSG_SPACE(x) ( ALIGN(sizeof(struct cmsghdr)) + x) #endif #endif /* RFC2292API */ int main() { struct iovec iov[1]; struct msghdr msg; #ifndef RFC2292API struct cmessage cm; #else union { struct cmsghdr cm; char control[ CMSG_SPACE( sizeof( int ) ) ]; } cmsgbuf; struct cmsghdr * cmptr; #endif /* RFC2292API */ struct sockaddr_un sun; int s,fd; int sock; int len; fd_set readfds; char recbuf[1024]; if (unlink("/tmp/testsock") == -1) warn("couldn't remove old socket"); strcpy(sun.sun_path, "/tmp/testsock"); sun.sun_family = AF_UNIX; len = sun.sun_len = sizeof(sun.sun_len) + sizeof(sun.sun_family) + strlen(sun.sun_path) + 1; if ((s = socket(AF_UNIX, SOCK_STREAM, 0)) == -1) err(1, "socket creation failed"); iov[0].iov_base = (char *)&recbuf; iov[0].iov_len = sizeof(recbuf); #ifndef RFC2292API bzero((char *)&cm, sizeof(cm)); #else bzero((char *)&cmsgbuf, sizeof(cmsgbuf)); #endif /* RFC2292API */ bzero((char *)&msg, sizeof(msg)); msg.msg_iov = iov; msg.msg_iovlen = 1; msg.msg_name = NULL; msg.msg_namelen = 0; msg.msg_flags = 0; #ifndef RFC2292API msg.msg_control = (caddr_t)&cm; msg.msg_controllen = sizeof(struct cmessage); #else msg.msg_control = (caddr_t)&cmsgbuf.control; msg.msg_controllen = sizeof cmsgbuf.control; #endif /* RFC2292API */ if (bind(s, (struct sockaddr *)&sun, len) == -1) err(1, "couldn't bind socket"); listen(s, 2); if ((sock = accept(s, (struct sockaddr *)&sun, &len)) == -1) err(1, "accept failed"); FD_ZERO(&readfds); FD_SET(sock, &readfds); select(FD_SETSIZE, &readfds, NULL, NULL, NULL); if ((len = recvmsg(sock, &msg, 0)) == -1) err(1, "recvmsg failed"); printf ("read %d bytes\n", len); #ifndef RFC2292API if (cm.cmsg.cmsg_type != SCM_RIGHTS) warnx("message didn't contain SCM_RIGHTS"); fd=cm.fd; #else /* account for alignment issues */ if ((cmptr=CMSG_FIRSTHDR(&msg)) == NULL ) err(1,"Not the right msg struct"); if (cmptr->cmsg_len != CMSG_LEN(sizeof(int))) err(1,"Not the right length for a file descriptor"); if ( cmptr->cmsg_level != SOL_SOCKET) err(1,"Not the right SOCKED packet"); if (cmptr->cmsg_type != SCM_RIGHTS) err(1,"Not the right RIGHTS packet"); fd= *(int *)CMSG_DATA(cmptr); #endif /* RFC2292API */ printf ("FD: %d\n", fd); if ((lseek(fd,0,SEEK_END))==-1) err(1,"could not set fileptr"); if ((write(fd,"GOTCHA\n",7))==-1) err(1,"could not write"); close(fd); close(sock); close(s); exit(0); } /*>r,c */ #include #include #include #include #include #include #include #include #include #include #include #include #include #include #ifdef RFC2292API #include /* for ALIGN macro */ #endif /* RFC2292API */ #ifndef lint #ifdef RFC2292API static const char rcsid[] = "$Id: r.c,v 1.4 1998/08/30 07:21:11 dirkx Exp $"; #else static const char rcsid[] = "$Id: s.c,v 1.4 1998/08/29 01:05:28 wpaul Exp $"; #endif /* RFC2292API */ #endif #ifndef RFC2292API struct cmessage { struct cmsghdr cmsg; int fd; }; #else #ifndef CMSG_LEN # define CMSG_LEN(x) (ALIGN(sizeof(struct cmsghdr)) + ALIGN(x)) #endif #ifndef CMSG_SPACE # define CMSG_SPACE(x) ( ALIGN(sizeof(struct cmsghdr)) + x) #endif #endif /* RFC2292API */ int main() { struct iovec iov[1]; struct msghdr msg; #ifndef RFC2292API struct cmessage cm; #else union { struct cmsghdr cm; char control[ CMSG_SPACE( sizeof( int ) ) ]; } cmsgbuf; struct cmsghdr * cmptr; #endif /* RFC2292API */ struct sockaddr_un sun; int s,fd; int len; char sendbuf[] = "This is a test buffer."; if ((fd=open("/tmp/test",O_CREAT|O_RDWR|O_TRUNC,0666))==-1) err(1,"could not open file"); if ((fd = open("/tmp/test",O_CREAT | O_RDWR,0666)) == -1) err(1,"could not create my file"); if ((write(fd,"SEND\n",5))==-1) err(1,"Could not write"); strcpy(sun.sun_path, "/tmp/testsock"); sun.sun_family = AF_UNIX; len = sun.sun_len = sizeof(sun.sun_len) + sizeof(sun.sun_family) + strlen(sun.sun_path) + 1; if ((s = socket(AF_UNIX, SOCK_STREAM, 0)) == -1) err(1, "socket creation failed"); if (connect(s, (struct sockaddr *)&sun, len) == -1) err(1, "couldn't connect socket"); iov[0].iov_base = (char *)&sendbuf; iov[0].iov_len = sizeof(sendbuf); msg.msg_iov = iov; msg.msg_iovlen = 1; msg.msg_name = NULL; msg.msg_namelen = 0; msg.msg_flags = 0; #ifndef RFC2292API msg.msg_control = (caddr_t)&cm; msg.msg_controllen = sizeof(struct cmessage); cm.cmsg.cmsg_type = SCM_RIGHTS; cm.cmsg.cmsg_level = SOL_SOCKET; cm.cmsg.cmsg_len = sizeof(struct cmessage); cm.fd = fd; /* file descriptor to be transfered */ #else msg.msg_control = (caddr_t)&cmsgbuf.control; msg.msg_controllen = sizeof cmsgbuf.control; /* make sure we are aligned... */ cmptr = CMSG_FIRSTHDR( &msg ); cmptr->cmsg_len = CMSG_LEN( sizeof(int) ); cmptr->cmsg_level = SOL_SOCKET; cmptr->cmsg_type = SCM_RIGHTS; *(int *)CMSG_DATA(cmptr) = fd; /* file descriptor to be transfered */ #endif /* RFC2292API */ if ((len = sendmsg(s, &msg, 0)) == -1) err(1, "sendmsg failed"); printf ("sent message (%d bytes), fd=%d sending data...\n", len,fd); close(fd); close(s); exit(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 11:17:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19997 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 11:17:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19989 for ; Sat, 29 Aug 1998 11:17:14 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id DAA23860; Sun, 30 Aug 1998 03:16:19 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id DAA14765; Sun, 30 Aug 1998 03:16:19 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id DAA04024; Sun, 30 Aug 1998 03:15:24 +0900 (JST) To: mike@smith.net.au Cc: max@wide.ad.jp, freebsd-hackers@FreeBSD.ORG Cc: max@wide.ad.jp Subject: Re: question From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Sat, 29 Aug 1998 00:50:25 +0000" <199808290050.AAA01520@word.smith.net.au> References: <199808290050.AAA01520@word.smith.net.au> X-Mailer: Mew version 1.92.4 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: <19980830031523G.masafumi@aslm.rim.or.jp> Date: Sun, 30 Aug 1998 03:15:23 +0900 X-Dispatcher: imput version 971024 Lines: 31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not sure that this would be popular in the general case; I > would certainly be less than thrilled to have my systems > screaming at me every time I reboot, and while I can easily do > something about this, it's less simple to explain to what does > amount to the majority of our userbase why their systems are so > noisy. Hmm, okay. I didn't think about that. Maybe my working environment is too nosiy for me to feel bothered by some beeps. :) But your point seems reasonable. > For the installation, I can appreciate that this is an > excellent idea, and it should be quite easy to add these to the > release makefile. Yes. I looked at the Makefile and could think of some ways to easily achieve this. But since I'm not too sure what would be the appropriate way (or cosmetically best way), I'd like to leave it to someone who are more familiar with the release Makefile. > This, I expect along with a number of other things, would make > a good start for an "accessibility pack", or a set of > accessibility-related customisations which should be > configurable at install time. Yep. This increase the possibility for more blind individuals to start using our system and then we can get more input and help from them. Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 11:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20534 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 11:20:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gateway.whtech.com (user33.usr1.accesscom.com [205.226.158.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20386 for ; Sat, 29 Aug 1998 11:20:00 -0700 (PDT) (envelope-from don@whtech.com) Received: from digerati (digerati.whtech.com [10.1.0.2]) by gateway.whtech.com (8.8.7/8.8.7) with SMTP id LAA12609 for ; Sat, 29 Aug 1998 11:24:59 -0700 (PDT) (envelope-from don@whtech.com) From: "Don O'Neil" To: Subject: RE: Weird sendmail/pop problem Date: Sat, 29 Aug 1998 11:20:16 -0700 Message-ID: <000101bdd379$abe29a20$0200010a@digerati.whtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <19980829012108.51411@futuresouth.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Aug 28, 1998 at 06:53:20PM +0000, Terry Lambert woke me > up to tell me: > > > I'm experiencing a weird sendmail problem.. Anyone have any > clues where to > > > start looking for this? > > > > > > Here goes: > > > > > > I have a user on my box that is set up to forward mail to 2 people... > > > > > > When I send mail using MS Outlook 98 through a pop3 > connection the second > > > person in the .forward file gets the message but the first one doesnt. > > > > > > When I go outside of my box and send mail to the user, then > BOTH people in > > > the .forward file get the message... > > > > > > I've checked the aliases db, any .forward files laying around on the > > > machine, and all the basic configs for pop3 and sendmail but > have come up > > > empty handed... > > > > > > Any ideas? > > > > Where does POP3 come into this? > > > > You can't send mail over a POP3 connection, you can only retrieve it; > > you use SMTP to *send* mail. > > Before anyone else chimes in, there's some funky POP3 interface to send > mail to the server via it. > That said, it's still being DELIVERED through SMTP, so your point stands. > Here's my bet: > Try sending from the local box, not though POP3 > mail -s 'test msg' forwarduser < /dev/null > > See if that gets there (both theres). > Try (perhaps long shot, but *shrug*) killing sendmail and restarting it. > > Other than that... > There's my $0.02 on it. Well, To correct my mis-statement, I do realize that SMTP is how the mail is delivered, I was intending to point out that I was using a "standard" POP3 type client for recieving, not something like IMAP.... Anyway... I've checked the SMTP (sendmail) logs and the delivery is only made to one of the two recipents, no matter what order the names are in the .forward file, my name is allways skipped.... Now, my name is of course the one sending the message... is there something in sendmail that knows I was the originator and doesn't bother to send the message back to me? Now if I send a message using mail or elm, or pine, or sendmail directly from the box (not using the PC client) then both recipients get the message (I did this a root). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 12:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26224 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 12:07:39 -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 MAA26209 for ; Sat, 29 Aug 1998 12:07:37 -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 PAA18834 for ; Sat, 29 Aug 1998 15:06:39 -0400 (EDT) Date: Sat, 29 Aug 1998 15:06:39 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Macro cbtorpos() in fs.h 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 am trying to understand the macro cbtorpos() defined below: #define cbtorpos(fs, bno) \ (((bno) * NSPF(fs) % (fs)->fs_spc / (fs)->fs_nsect * (fs)->fs_trackskew + \ (bno) * NSPF(fs) % (fs)->fs_spc % (fs)->fs_nsect * (fs)->fs_interleave) % \ (fs)->fs_nsect * (fs)->fs_nrpos / (fs)->fs_npsect) First I assume that the hard disk sectors are numbered from one cylinder to another, moving from top track to the bottom track before moving to the next cylinder. (This is the vertical mapping as described at the site http:/www.tomshardware.com/hdd.html). Otherwise, the macro might not make any sense. So bno * NSPF % fs_spc / fs_nsect will give us the track number and bno * NSPF % fs_spc % fs_nsect will give us the sector count within that track. However, the rest part of the macro is confusing to me. In particular, why we multiply fs_trackskew? What is the meaning of fs_nrpos (number of rotational positions in a single track?) Why we divide by fs_nsect after multiplying by fs_interleave? I assume that fs_nsect + unused sectors = fs_npsect and the C operators %, /, and * all have same precedence. 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 Sat Aug 29 15:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14557 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 15:47:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles153.castles.com [208.214.165.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14552 for ; Sat, 29 Aug 1998 15:47:49 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id PAA08998; Sat, 29 Aug 1998 15:45:03 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808291545.PAA08998@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: hackers Subject: Re: Macro cbtorpos() in fs.h In-reply-to: Your message of "Sat, 29 Aug 1998 15:06:39 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 15:45:02 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am trying to understand the macro cbtorpos() defined below: > > #define cbtorpos(fs, bno) \ > (((bno) * NSPF(fs) % (fs)->fs_spc / (fs)->fs_nsect * (fs)->fs_trackskew + \ > (bno) * NSPF(fs) % (fs)->fs_spc % (fs)->fs_nsect * (fs)->fs_interleave) % \ > (fs)->fs_nsect * (fs)->fs_nrpos / (fs)->fs_npsect) > > > First I assume that the hard disk sectors are numbered from one cylinder > to another, moving from top track to the bottom track before moving to the > next cylinder. (This is the vertical mapping as described at the site > http:/www.tomshardware.com/hdd.html). Otherwise, the macro might not make > any sense. Yes. Logically block numbers are ordered in ascending order by track, head, cylinder. However it's worth considering, before you get too involved here, that most disks these days don't have the geometry that inspired these calculations, and when building filesystems we deliberately attempt to defeat these caclulations. > So bno * NSPF % fs_spc / fs_nsect will give us the track number and bno * > NSPF % fs_spc % fs_nsect will give us the sector count within that track. > However, the rest part of the macro is confusing to me. If I understand it correctly, the macro calculates the rotational position of the block number (bno) in the filesystem (fs). This is used for two things in ffs_alloc.c - When allocating a block, in the code which attempts to find the optimal block based on the filesystem's idea of the disk geometry. We defeat this code by setting fs_nrpos to 1 when building filesystems. - When accounting for block usage, it's used to generate an offset into the free block table for a given cylinder. Because we defeat much of the calculation with our filsystem layout, particularly by only distinguishing one rotational position per cylinder, I suspect that for FreeBSD filesystems the macro will normally return 0 (it might be a small optimisation to detect this case and avoid the calculations involved therin). In particular; fs_nsect will normally be == fs_npsect, and fs_rpos will be 1, so the entire macro reduces to (X) % ((z * 1) / z). You can see the fs_nsect and fs_npsect calculations in the newfs source, where fs_nsect is set from nsectors and fs_npsect is set from nphyssectors, and nphyssectors = nsectors + trackspares where trackspares is normally set to 0. For filesystems from other operating systems (eg. NetBSD), who don't optimise their filesystem layout for modern hardware, it will return an appropriate offset to suit the layout. Similarly if the optimised defaults used by FreeBSD's newfs are overridden when the filesystem is being generated. > I assume that fs_nsect + unused sectors = fs_npsect That would appear to be valid from the above. > and the C operators %, /, and * all > have same precedence. You can check /usr/share/misc/operator for that one. The policy implemented in ffs_alloc.c is discussed in "The Design and Implementation of the 4.4BSD Operating System", McKusic, Bostic, Karels and Quarterman, ISBN 0-201-54979-4 in section 8.2, subheading "Allocation Mechanisms" starting on page 277. Rotational positions are discussed on page 280. Our local policy changes are documented mostly in the CVS repository, and many are summarised in src/sbin/newfs/newfs.c. I hope this is at least a little helpful. -- \\ 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 29 20:56:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06485 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 20:56:49 -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 UAA06480 for ; Sat, 29 Aug 1998 20:56:47 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-89.camalott.com [208.229.74.89]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA25138; Sat, 29 Aug 1998 22:57:37 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA05971; Sat, 29 Aug 1998 22:55:47 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 22:55:47 -0500 (CDT) Message-Id: <199808300355.WAA05971@detlev.UUCP> To: kbyanc@freedomnet.com CC: freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Kelly Yancey on Sat, 29 Aug 1998 03:55:41 -0400 (EDT)) Subject: Re: determining an X window ID? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have written a fairly short shell script to launch xmcd which first > checks to see if any other cd player is already running and if so, does > not launch another instance of xmcd (for when I click on the wrong thing > :) ) How does it do this check? 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 Sat Aug 29 21:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06904 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 21:00:20 -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 VAA06899 for ; Sat, 29 Aug 1998 21:00:19 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-89.camalott.com [208.229.74.89]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id XAA25366; Sat, 29 Aug 1998 23:01:06 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA05975; Sat, 29 Aug 1998 22:59:16 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 22:59:16 -0500 (CDT) Message-Id: <199808300359.WAA05975@detlev.UUCP> To: yokota@zodiac.mech.utsunomiya-u.ac.jp CC: freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp In-reply-to: <199808290951.SAA01516@zodiac.mech.utsunomiya-u.ac.jp> (message from Kazutaka YOKOTA on Sat, 29 Aug 1998 18:51:44 +0900) Subject: Re: question From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808290050.AAA01520@word.smith.net.au> <199808290951.SAA01516@zodiac.mech.utsunomiya-u.ac.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I tested this on my box. I added three ^G to the end of boot.help >>> and it worked very well. Once proper documentation is provided (I >>> will write something for either FAQ or the handbook), this will >>> help many people who want to install FreeBSD to PC without a >>> display monitor. I will make this change to >>> /sys/i386/boot/biosboot/boot.help if I don't hear any objection >>> within next a few days. >> I'm not sure that this would be popular in the general case; I >> would certainly be less than thrilled to have my systems screaming >> at me every time I reboot, and while I can easily do something >> about this, it's less simple to explain to what does amount to the >> majority of our userbase why their systems are so noisy. > I wonder if this is such a big deal. > After all, BIOS beeps during POST when the box is switched on.... One is quite enough, I then know that a system has rebooted, in case the drive seeks didn't tell me. Excessive beeps are a pet peeve of mine-- particularly if I'm doing something like hacking the boot process. 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 Sat Aug 29 21:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07843 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 21:11:20 -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 VAA07838 for ; Sat, 29 Aug 1998 21:11:19 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-89.camalott.com [208.229.74.89]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id XAA25750; Sat, 29 Aug 1998 23:08:52 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA06013; Sat, 29 Aug 1998 23:07:02 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 23:07:02 -0500 (CDT) Message-Id: <199808300407.XAA06013@detlev.UUCP> To: luigi@labinfo.iet.unipi.it CC: chanders@timing.com, freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-reply-to: <199808291246.OAA06042@labinfo.iet.unipi.it> (message from Luigi Rizzo on Sat, 29 Aug 1998 14:46:42 +0200 (MET DST)) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808291246.OAA06042@labinfo.iet.unipi.it> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Can someone give me pointers on passing open file descriptors on >>> still, this looks to me one of the most obscure interfaces in the OS. >>> Does any real application use that ? >> Emacs will in the next release (20.4). > of course... is there anything that emacs does not use :) Sure! It doesn't use SCM_RIGHTS yet (more precisely, I think I'm the only one running that extention), it won't be using RFC1149 (look it up) until 20.6, we have no plans to pass session snapshots down a pair of tin cans with string, and won't be adding embedded Perl/Awk/TECO support with automatic language sensing until at least version 21. Other than that, I think it uses just about everything... including the kitchen sink for some versions... (try Win32-based GNU Emacs, or XEmacs.) 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 Sat Aug 29 21:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08537 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 21:17:09 -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 VAA08529 for ; Sat, 29 Aug 1998 21:17:05 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-89.camalott.com [208.229.74.89]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id XAA26084; Sat, 29 Aug 1998 23:14:37 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA06019; Sat, 29 Aug 1998 23:12:47 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 23:12:47 -0500 (CDT) Message-Id: <199808300412.XAA06019@detlev.UUCP> To: dirk.vangulik@jrc.it CC: chanders@timing.com, wpaul@skynet.ctr.columbia.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Dirk-Willem van Gulik on Sat, 29 Aug 1998 19:29:10 +0200 (CEST)) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I struggeled with the same, in particular as the most recent book of > Stevens uses the API as described in RFC2292. And two of the macro's > are not quite part of socket.h. (why is this actually?) Well, my best guess is that the RFC (entitled "Advanced Sockets API for IPv6") is based on IPv6, which we have not integrated into -current. (What's the story on that, anyway?) The feature I thought you were referring to is passing an fd through a local domain socket, not an inet socket. To the best of my knowledge, BSD does not support the latter operation. (It would be nontrivial.) 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 Sat Aug 29 21:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10071 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 21:33:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.224.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10036 for ; Sat, 29 Aug 1998 21:33:13 -0700 (PDT) (envelope-from avalon@coombs.anu.edu.au) Message-Id: <199808300433.VAA10036@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA062441509; Sun, 30 Aug 1998 14:31:49 +1000 From: Darren Reed Subject: duplicating cd's with dd. To: hackers@FreeBSD.ORG Date: Sun, 30 Aug 1998 14:31:48 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does anyone know if there are "preferred" parameters for using dd to copy cd's with ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 22:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12152 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 22:02:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles153.castles.com [208.214.165.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12141 for ; Sat, 29 Aug 1998 22:02:02 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA10620; Sat, 29 Aug 1998 21:59:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808292159.VAA10620@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Darren Reed cc: hackers@FreeBSD.ORG Subject: Re: duplicating cd's with dd. In-reply-to: Your message of "Sun, 30 Aug 1998 14:31:48 +1000." <199808300433.VAA10036@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 21:59:08 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > does anyone know if there are "preferred" parameters for using dd to > copy cd's with ? You can improve performance slightly with a larger block size (fewer syscalls), but that's about it. I use 64K as an arbitrary figure; it seems to run about as fast as the drive will go. -- \\ 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 29 22:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13730 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 22:27:36 -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 WAA13725 for ; Sat, 29 Aug 1998 22:27:34 -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 WAA22341; Sat, 29 Aug 1998 22:24:42 -0700 Date: Sat, 29 Aug 1998 22:24:42 -0700 (PDT) From: Alex Belits To: Craig Anderson cc: freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-Reply-To: <199808281426.IAA10588@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 On Fri, 28 Aug 1998, Craig Anderson wrote: > Can someone give me pointers on passing open file descriptors on FreeBSD? > This is covered in W. Richard Stevens Advanced programming book, but See R. Stevens "TCP/IP Illustrated", volume 3, chapter 18.3 or R. Stevens "Unix Network Programming", second edition (1997), volume 1, chapter 14.7. Previous books describe 4.3BSD and SVR4 fd passing that is more than slightly different. > the structs in FreeBSD are slightly different, and I've never done this. In FreeBSD CMSG_DATA(cm) macro is the equivalent to cm->cmsg_data that is commented out in include files in 4.4BSD-derived, but exists in other compatible systems. Beware of the known bug in FreeBSD kernel (PR kern/4345). -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 22:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13952 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 22:28:49 -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 WAA13944 for ; Sat, 29 Aug 1998 22:28:38 -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 WAA22337; Sat, 29 Aug 1998 22:24:31 -0700 Date: Sat, 29 Aug 1998 22:24:30 -0700 (PDT) From: Alex Belits To: Luigi Rizzo cc: Craig Anderson , freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-Reply-To: <199808281628.SAA05374@labinfo.iet.unipi.it> 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, 28 Aug 1998, Luigi Rizzo wrote: > still, this looks to me one of the most obscure interfaces in the OS. > Does any real application use that ? fhttpd uses it (and this is how mysterious kern/4345 was found). -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 29 22:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14830 for freebsd-hackers-outgoing; Sat, 29 Aug 1998 22:36:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles313.castles.com [208.214.167.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14821 for ; Sat, 29 Aug 1998 22:36:20 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id WAA10825; Sat, 29 Aug 1998 22:33:19 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808292233.WAA10825@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: question In-reply-to: Your message of "Sun, 30 Aug 1998 03:15:23 +0900." <19980830031523G.masafumi@aslm.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 22:33:18 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For the installation, I can appreciate that this is an > > excellent idea, and it should be quite easy to add these to the > > release makefile. > > Yes. I looked at the Makefile and could think of some ways to easily > achieve this. But since I'm not too sure what would be the > appropriate way (or cosmetically best way), I'd like to leave it to > someone who are more familiar with the release Makefile. Down towards the bottom of the doMFSKERN target, the boot.help file is copied into the boot images. Just do @echo \07\07 >> ${RD}/boot.${FSIMAGE}/boot.help (And if you were reading that entire makefile with a braille screen reader, or a speech synth, I think you deserve some serious compliments.) > > This, I expect along with a number of other things, would make > > a good start for an "accessibility pack", or a set of > > accessibility-related customisations which should be > > configurable at install time. > > Yep. This increase the possibility for more blind individuals to > start using our system and then we can get more input and help from > them. Definitely. Even complaints about what's wrong with it right now are a good start. -- \\ 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