From owner-freebsd-hackers Wed Jan 1 04:45:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA27040 for hackers-outgoing; Wed, 1 Jan 1997 04:45:17 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA27034; Wed, 1 Jan 1997 04:45:13 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701011245.EAA27034@freefall.freebsd.org> Subject: Re: booting problems To: pitlord@usit.net Date: Wed, 1 Jan 1997 04:45:13 -0800 (PST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <32C9EC2F.533A@usit.net> from "Troy Settle" at Dec 31, 96 11:46:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Troy Settle wrote: > > again). If I enter '/kernel' at the boot: prompt, it > will load the kernel, but upon initialization, it just > hangs. After about 15 minutes, I give up, and give it > a 3-finger salute, and boot '/kernel.GENERIC' with no > problems. > > I rebuilt the kernel a few times, and the problem kept > repeating itself. I moved the HD off to another system, > and all my kernels booted just fine. can you send us several files? 1. a copy of your kernel config file 2. the output of '/usr/bin/uname -a' 3. the output of '/sbin/dmesg' jmb From owner-freebsd-hackers Wed Jan 1 07:41:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA01862 for hackers-outgoing; Wed, 1 Jan 1997 07:41:38 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA01852 for ; Wed, 1 Jan 1997 07:41:35 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22840; Wed, 1 Jan 1997 10:41:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 1 Jan 1997 10:41 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id HAA21462 for ; Wed, 1 Jan 1997 07:59:31 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id IAA04781 for freebsd-hackers@freefall.cdrom.com; Wed, 1 Jan 1997 08:02:54 -0500 (EST) Date: Wed, 1 Jan 1997 08:02:54 -0500 (EST) From: Thomas David Rivers Message-Id: <199701011302.IAA04781@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Test SL/IP install of 2.2-BETA_A. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just F.Y.I. I was (finally) able to test install a BETA release before the BETA period was over :-) I have installed 2.2-BETA (as of Dec. 26th) via NFS over SL/IP onto my ancient 386sx laptop w/8meg & 124meg IDE disk... I didn't encounter a single problem! Neglecting my wonderful success with 2.1.6.1; this is the best SL/IP install support yet! Good job! - Dave Rivers - From owner-freebsd-hackers Wed Jan 1 07:41:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA01865 for hackers-outgoing; Wed, 1 Jan 1997 07:41:39 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA01853 for ; Wed, 1 Jan 1997 07:41:35 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22847; Wed, 1 Jan 1997 10:41:04 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 1 Jan 1997 10:41 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id IAA21473 for ; Wed, 1 Jan 1997 08:08:02 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id IAA04827 for freebsd-hackers@freefall.cdrom.com; Wed, 1 Jan 1997 08:11:25 -0500 (EST) Date: Wed, 1 Jan 1997 08:11:25 -0500 (EST) From: Thomas David Rivers Message-Id: <199701011311.IAA04827@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 2.2-BETA, timezone and the PC clock... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - In previous installs; when setting the timezone, it always asked if my PCs clock was UTC (Greenwich mean time) or local time. Apparently, in 2.2-BETA that adjustment is no longer made, and UTC is assumed. My machine's clock is localtime (I just verified it in the setup), and although my /etc/localtime has the correct timezone for me (EST) - the values are off by 5 hours. Has adjtime "gone away" for 2.2? Or, is this just an install problem? - Dave Rivers - From owner-freebsd-hackers Wed Jan 1 07:43:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA01959 for hackers-outgoing; Wed, 1 Jan 1997 07:43:25 -0800 (PST) Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA01953; Wed, 1 Jan 1997 07:43:23 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m4gfFC3-0021akC; Wed, 31 Dec 69 18:59 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA19485; Wed, 1 Jan 1997 09:38:07 -0600 Date: Wed, 1 Jan 1997 09:38:07 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199701011538.JAA19485@bonkers.taronga.com> To: jhs@freebsd.org Subject: Re: 1 gig IDE won't install with 1993 < 500M BIOs Newsgroups: taronga.freebsd.hackers In-Reply-To: <199612190204.DAA16690@vector.jhs.no_domain> Organization: none Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612190204.DAA16690@vector.jhs.no_domain> you write: >Suggestions as to what to poke, & what to RTFM would be appreciated, >I've already cruised the handbook, & FAQ, but found nothing Re. >booting > 500M drives on old bioses with < 500M capability . I just added a section to the FAQ about this. What about disk managers? My BIOS doesn't support large drives!

FreeBSD recognises the Ontrack Disk Manager and makes allowances for it. Other disk managers are not supported. If you just want to use the disk with FreeBSD you don't need a disk manager. Just configure the disk for as much space as the BIOS can deal with (usually 504 megabytes), and FreeBSD should figure out how much space you really have. If you're using an old disk with an MFM controller, you may need to explicitly tell FreeBSD how many cylinders to use. If you want to use the disk with FreeBSD and another operating system, you may be able to do without a disk manager: just make sure the the FreeBSD boot partition and the slice for the other operating system are in the first 1024 cylinders. From owner-freebsd-hackers Wed Jan 1 09:56:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17483 for hackers-outgoing; Wed, 1 Jan 1997 09:56:24 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA17478 for ; Wed, 1 Jan 1997 09:56:21 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA28086; Wed, 1 Jan 1997 18:55:53 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA20448; Wed, 1 Jan 1997 18:55:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA28809; Wed, 1 Jan 1997 17:12:12 +0100 (MET) From: J Wunsch Message-Id: <199701011612.RAA28809@uriah.heep.sax.de> Subject: Re: booting problems To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 1 Jan 1997 17:12:12 +0100 (MET) Cc: pitlord@usit.net Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32C9EC2F.533A@usit.net> from Troy Settle at "Dec 31, 96 11:46:39 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Troy Settle wrote: > I recently installed FreeBSD on a pentium for the > first time. [...] > I rebuilt the kernel a few times, and the problem kept > repeating itself. I moved the HD off to another system, > and all my kernels booted just fine. What version of FreeBSD? There were some problems in the bootblocks that have been fixed since. > Also, while I'm posting, does anyone know if there's a way > I can use a generic NE2000 PCI card that insists on sitting > at IRQ 12, 0xFF40 ? FreeBSD <= 2.1.6 can only handle them if you configure it manually at these settings (and of course, next time you change your PCI configuration, you will have to boot -c again). FreeBSD 2.2 (BETA and all the SNAPs later than May 1996) supports it directly as a PCI device. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jan 1 13:32:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA25385 for hackers-outgoing; Wed, 1 Jan 1997 13:32:16 -0800 (PST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA25370 for ; Wed, 1 Jan 1997 13:32:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id NAA25411; Wed, 1 Jan 1997 13:31:44 -0800 (PST) Date: Wed, 1 Jan 1997 13:31:41 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Thomas David Rivers cc: FreeBSD Hackers Subject: Re: 2.2-BETA, timezone and the PC clock... In-Reply-To: <199701011311.IAA04827@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 1 Jan 1997, Thomas David Rivers wrote: > > Ok - > > In previous installs; when setting the timezone, it always asked > if my PCs clock was UTC (Greenwich mean time) or local time. > > Apparently, in 2.2-BETA that adjustment is no longer made, and > UTC is assumed. > > My machine's clock is localtime (I just verified it in the setup), and > although my /etc/localtime has the correct timezone for me (EST) - > the values are off by 5 hours. > > Has adjtime "gone away" for 2.2? Or, is this just an install problem? I'm not sure what the problem with sysinstall is... but if you run 'touch /etc/wall_cmos_clock' it will convert from using UTC to local time... hope this helps... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-hackers Wed Jan 1 14:25:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA27480 for hackers-outgoing; Wed, 1 Jan 1997 14:25:04 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA27472 for ; Wed, 1 Jan 1997 14:25:00 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id JAA06593 for hackers@freebsd.org; Thu, 2 Jan 1997 09:24:38 +1100 (EST) From: Julian Assange Message-Id: <199701012224.JAA06593@profane.iq.org> Subject: struct file locking To: hackers@freebsd.org Date: Thu, 2 Jan 1997 09:24:38 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am expanding the inet/socket code to permit firewall entries based on uid/gid. I have an aesthetic issue and one locking issue. I need to pass socket credential information into ip_output. There are two ways of doing this. I can add a back-pointer to the socket structure from the struct ipoption mbuf, or I can add an extra parameter to ip_output. I am inclinded towards the first option, for source-level compatability reasons. In the socket structure I intend to create a back-pointer to originating struct file's->u_cred. What do I need to do to insure these last two structures are reliably locked and in memory? Cheers, Julian. From owner-freebsd-hackers Wed Jan 1 15:20:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA29521 for hackers-outgoing; Wed, 1 Jan 1997 15:20:26 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA29502 for ; Wed, 1 Jan 1997 15:20:20 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id AAA04314; Thu, 2 Jan 1997 00:16:01 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.4/8.8.2) id AAA18565; Thu, 2 Jan 1997 00:09:41 +0100 (MET) Message-ID: Date: Thu, 2 Jan 1997 00:09:40 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: jfieber@indiana.edu (John Fieber) Cc: hackers@FreeBSD.org Subject: Re: New motherboard breaks tape drive References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from "John Fieber" on Dec 31, 1996 14:02:35 -0500 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk John Fieber writes: > I have an Archive Viper 150 tape drive that has served me well > for many years. I have never had difficulty getting the maximum > performance of about 100K/second writing speed from it... > > ...until upgrade my old 486DX33 motherboard to a Pentium 100 > (ASUS). Now the tape drive will no longer stream and typical > writing speed has dropped to about 50K/second. > > My first thought was something with the new SCSI controller (ASUS > SC200) was the problem so I put my old Adaptec 1542C in, but the > result was the same (I even tried putting the drive alone on the > bus). I tried team, but it didn't help. > > I'm fishing for where to look next. Ideas? Did you upgrade only the board or did you additionally a - FreeBSD release change - FreeBSD kernel recompile How is your kernel config file. What's the SC200 ? PCI controller ? AHA 2940 compatible or what ? I get about 300-600 KB/sec throughput using dump and a TDC 4222, which uses data compression. I'm getting these numbers with -current and 2.2-Release (Beta of today). BTW: My numbers depend heavily on filesystem fragmentation. BTW, did you try team from the ports collection ? team(1) - parallel pipe, allows asynchronous io This can be used to speedup data throughput for tar and dump and friends ;-) Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Wed Jan 1 16:07:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02346 for hackers-outgoing; Wed, 1 Jan 1997 16:07:15 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA02338 for ; Wed, 1 Jan 1997 16:07:12 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id TAA00307; Wed, 1 Jan 1997 19:07:02 -0500 (EST) Date: Wed, 1 Jan 1997 19:07:01 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Andreas Klemm cc: hackers@FreeBSD.org Subject: Re: New motherboard breaks tape drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Andreas Klemm wrote: > > I'm fishing for where to look next. Ideas? > > Did you upgrade only the board or did you additionally a > - FreeBSD release change > - FreeBSD kernel recompile No release change---the kernel was somewhere between 2.2-ALPHA and BETA at the time of the upgrade. A kernel re-compile was of course necessary for the new scsi controller. > How is your kernel config file. What's the SC200 ? > PCI controller ? AHA 2940 compatible or what ? NCR. See kernel config below. > BTW, did you try team from the ports collection ? Yes, and it doesn't offer any improvement over dump/tar/dd with sufficiently large block sizes. -john # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.45 1995/05/14 02:59:44 davidg Exp $ # machine "i386" cpu "I586_CPU" ident FALLOUT maxusers 15 options CHILD_MAX=128 options OPEN_MAX=128 options "COMPAT_43" options USER_LDT options SYSVSHM #SYSV shared memory options SYSVSEM #SYSV semaphores options SYSVMSG #SYSV messages options KTRACE #Kernel syscall tracing options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking options NETATALK #AppleTalk options FFS #Berkeley Fast Filesystem options DEVFS config kernel root on sd0 # ISA Bus controller isa0 #options "AUTO_EOI_1" #options "AUTO_EOI_2" options BOUNCE_BUFFERS #include support for DMA bounce buffers # PCI Bus controller pci0 # Floppy disk controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Controller and devices controller ncr0 controller scbus0 at ncr0 #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller scbus1 at aha0 device sd0 device st0 device cd0 options SCSI_DELAY=10 #Be pessimistic about Joe SCSI device #options SCSIDEBUG # Syscons console driver (SCO compatible) device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Math processor device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # Serial ports device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr # Parallel ports device lpt0 at isa? port? tty irq 7 vector lptintr # Ethernet device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr # Sound card controller snd0 device sb0 at isa? port 0x220 irq 10 drq 1 vector sbintr device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x300 device opl0 at isa? port 0x388 # Pseudo devices pseudo-device loop # loopback device pseudo-device ether # core ethernet code pseudo-device log # system logging pseudo-device pty 32 # pseudo terminals pseudo-device speaker # PC speaker interface pseudo-device gzip # Exec gzipped a.out's pseudo-device vn # vnode driver (turns a file into a device) pseudo-device bpfilter 4 # Berkeley packet filter device From owner-freebsd-hackers Wed Jan 1 16:54:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA04828 for hackers-outgoing; Wed, 1 Jan 1997 16:54:57 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA04819 for ; Wed, 1 Jan 1997 16:54:54 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA10047 (5.67b/IDA-1.5 for ); Thu, 2 Jan 1997 01:54:45 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id AAA01043; Thu, 2 Jan 1997 00:48:48 +0100 (CET) Message-Id: Date: Thu, 2 Jan 1997 00:47:27 +0100 From: se@freebsd.org (Stefan Esser) To: pitlord@usit.net Cc: freebsd-hackers@freebsd.org Subject: Re: booting problems References: <32C9EC2F.533A@usit.net> X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: <32C9EC2F.533A@usit.net>; from Troy Settle on Dec 31, 1996 23:46:39 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 31, pitlord@usit.net (Troy Settle) wrote: > Also, while I'm posting, does anyone know if there's a way > I can use a generic NE2000 PCI card that insists on sitting > at IRQ 12, 0xFF40 ? You didn't tell which FreeBSD version you are using. For more than a half year, the ed0 isa device entry in the config file enabled the PCI NE2000 probe, and this should automatically configure your card. You'll have to provide me with more details (best if you boot with "-v" and send me the boot message log) if you want me to look into this. Regards, STefan From owner-freebsd-hackers Wed Jan 1 17:01:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA05109 for hackers-outgoing; Wed, 1 Jan 1997 17:01:09 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA05103 for ; Wed, 1 Jan 1997 17:01:06 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA14579; Thu, 2 Jan 1997 11:30:55 +1030 (CST) From: Michael Smith Message-Id: <199701020100.LAA14579@genesis.atrad.adelaide.edu.au> Subject: Re: Ints (fwd) In-Reply-To: from hmmm at "Dec 31, 96 12:30:41 pm" To: hmmm@alaska.net (hmmm) Date: Thu, 2 Jan 1997 11:30:54 +1030 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hmmm stands accused of saying: > > Wait a second guys.... The interrupt lines on the ISA bus are > open-collector, which means that it is possible to OR-TIE them > together- remember Digital Electronics Fundamentals? Open-collector > is very similar to tri-state, and is used when there is only 1 > active state. If an application should require multiple devices to > share a bus, and 2 active states are required, then tri-state > drivers are required on all outputs. ... only ISA interrupt lines aren't open-collector. The RC time constant implicit in OC circuits (there is a tradeoff between the risetime and the power dissipation in the driving circuit) is unacceptable for anything other than the slowest logic. Work it out; 5V / 24mA (LSTTL sink limit) = ~200R. Assuming 50pf of parasitic capacitance (not unreasonable), you get RC = 10usec. Not so good. (220R is actually the accepted value for LSTTL and compatible families, witness the 220/330R resistor pairing in passive SCSI terminators.) Just about every other multi-card bus ever invented uses daisy-chained interrupts or slot interrupts or some other manifestation of a sensible scheme. But not ISA. YOU CANNOT SHARE INTERRUPTS SAFELY ON ISA. > The only state which we are concerned with is ACTIVE (low). The > processor doesn't care if an interrupt isn't happening, only when > one IS. So a peripheral device does not DRIVE the interrupt line > "the other way", it simply de-activates it's open-collector output. > If another peripheral device happens to have interrupt asserted, the > state of the IRQ line will not change. ... but the inputs to the 8259 are _edge_triggered_. If another device is holding the line asserted, that doesn't count for a new interrupt. It also means that another edge can't occur. So not only is the second interrupt lost, but every interrupt after that is lost as well. Personally, I find the fact that PC's work at all to be quite amazing. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jan 1 17:21:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA06448 for hackers-outgoing; Wed, 1 Jan 1997 17:21:23 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA06438 for ; Wed, 1 Jan 1997 17:21:18 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA14651 for hackers@freebsd.org; Thu, 2 Jan 1997 11:51:16 +1030 (CST) From: Michael Smith Message-Id: <199701020121.LAA14651@genesis.atrad.adelaide.edu.au> Subject: make(1) substitution question... To: hackers@freebsd.org Date: Thu, 2 Jan 1997 11:51:15 +1030 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone suggest a way of making this DWIM without involving the shell? FOO= test BAR= FOO target: echo ${${BAR}} -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jan 1 17:35:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA07371 for hackers-outgoing; Wed, 1 Jan 1997 17:35:43 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA07366 for ; Wed, 1 Jan 1997 17:35:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id RAA13418; Wed, 1 Jan 1997 17:34:53 -0800 (PST) Message-Id: <199701020134.RAA13418@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Julian Assange cc: hackers@freebsd.org Subject: Re: struct file locking In-reply-to: Your message of "Thu, 02 Jan 1997 09:24:38 +1100." <199701012224.JAA06593@profane.iq.org> From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Jan 1997 17:34:53 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In the socket structure I intend to create a back-pointer to >originating struct file's->u_cred. What do I need to do to insure >these last two structures are reliably locked and in memory? See crhold() in sys/ucred.h and crfree() in sys/kern/kern_prot.c. They manage the cr_ref reference count. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Jan 1 18:01:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA08191 for hackers-outgoing; Wed, 1 Jan 1997 18:01:23 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA08182 for ; Wed, 1 Jan 1997 18:01:19 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA07995; Wed, 1 Jan 1997 21:00:47 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 1 Jan 1997 21:00 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id UAA01509; Wed, 1 Jan 1997 20:16:25 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id UAA08809; Wed, 1 Jan 1997 20:19:50 -0500 (EST) Date: Wed, 1 Jan 1997 20:19:50 -0500 (EST) From: Thomas David Rivers Message-Id: <199701020119.UAA08809@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!resnet.uoregon.edu!gurney_j Subject: Re: 2.2-BETA, timezone and the PC clock... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > Ok - > > > > In previous installs; when setting the timezone, it always asked > > if my PCs clock was UTC (Greenwich mean time) or local time. > > > > Apparently, in 2.2-BETA that adjustment is no longer made, and > > UTC is assumed. > > > > My machine's clock is localtime (I just verified it in the setup), and > > although my /etc/localtime has the correct timezone for me (EST) - > > the values are off by 5 hours. > > > > Has adjtime "gone away" for 2.2? Or, is this just an install problem? > > I'm not sure what the problem with sysinstall is... but if you run 'touch > /etc/wall_cmos_clock' it will convert from using UTC to local time... > hope this helps... ttyl... I'm guessing that the question just went missing from sysinstall... Should it have? - Dave R. - From owner-freebsd-hackers Wed Jan 1 18:30:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA09123 for hackers-outgoing; Wed, 1 Jan 1997 18:30:51 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA09116 for ; Wed, 1 Jan 1997 18:30:48 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id CAA00972; Thu, 2 Jan 1997 02:46:29 +0100 From: Luigi Rizzo Message-Id: <199701020146.CAA00972@labinfo.iet.unipi.it> Subject: Re: Ints (fwd) To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 2 Jan 1997 02:46:28 +0100 (MET) Cc: hmmm@alaska.net, hackers@FreeBSD.ORG In-Reply-To: <199701020100.LAA14579@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 2, 97 11:30:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > hmmm stands accused of saying: > > > > Wait a second guys.... The interrupt lines on the ISA bus are > > open-collector, which means that it is possible to OR-TIE them ... > > ... only ISA interrupt lines aren't open-collector. The RC time > constant implicit in OC circuits (there is a tradeoff between the > risetime and the power dissipation in the driving circuit) is > unacceptable for anything other than the slowest logic. > > Work it out; 5V / 24mA (LSTTL sink limit) = ~200R. Assuming 50pf of > parasitic capacitance (not unreasonable), you get RC = 10usec. Not so > good. (220R is actually the accepted value for LSTTL and compatible > families, witness the 220/330R resistor pairing in passive SCSI > terminators.) of course all this reasoning breaks since 50pf = 50e-12 F so RC is 10 nanoseconds... :) > Just about every other multi-card bus ever invented uses daisy-chained > interrupts or slot interrupts or some other manifestation of a sensible > scheme. But not ISA. YOU CANNOT SHARE INTERRUPTS SAFELY ON ISA. true, but that's because of edge triggered lines as you say later. Were they level sensitive, there would be no problem in sharing them. Luigi From owner-freebsd-hackers Wed Jan 1 18:52:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA10639 for hackers-outgoing; Wed, 1 Jan 1997 18:52:04 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA10609 for ; Wed, 1 Jan 1997 18:52:00 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA14993; Thu, 2 Jan 1997 13:21:35 +1030 (CST) From: Michael Smith Message-Id: <199701020251.NAA14993@genesis.atrad.adelaide.edu.au> Subject: Re: Ints (fwd) In-Reply-To: <199701020146.CAA00972@labinfo.iet.unipi.it> from Luigi Rizzo at "Jan 2, 97 02:46:28 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 2 Jan 1997 13:21:34 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hmmm@alaska.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Luigi Rizzo stands accused of saying: > > > > Work it out; 5V / 24mA (LSTTL sink limit) = ~200R. Assuming 50pf of > > parasitic capacitance (not unreasonable), you get RC = 10usec. Not so > > good. (220R is actually the accepted value for LSTTL and compatible > > families, witness the 220/330R resistor pairing in passive SCSI > > terminators.) > > of course all this reasoning breaks since 50pf = 50e-12 F so RC is > 10 nanoseconds... :) Ah whoops, forgot some zeroes there. Still, 50pf is a bit on the light side, and consult Solari for some amusing stories about the negative-time requirements on ISA-bus signals 8) Just checking with Solari, actually; the spec is 15pf/slot, and 24mA sink. OC lines on the bus are tied with 300R, not 220. So on a modern 4-slot mixed ISA/PCI bus backplane that's 300*60p = 18ns. IEEE P996 specifies 11ns bus settling time for a fully-loaded 8-slot backplane, so that loses again. But Solari observes : "[EISA uses open-collector interrupt inputs] The open collector approach for a level triggered INTERRUPT signal line relies on a pull-up resistor to deactivate the interrupt request. The EISA bus specification has the largest resistor value; consequently, 500 nanonseconds are required for deactivation on the E-ISA platform." (1ed, p5-76) > > scheme. But not ISA. YOU CANNOT SHARE INTERRUPTS SAFELY ON ISA. > > true, but that's because of edge triggered lines as you say later. > Were they level sensitive, there would be no problem in sharing > them. Err yes. But like we said, they ain't. 8) > Luigi -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jan 1 18:54:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA10681 for hackers-outgoing; Wed, 1 Jan 1997 18:54:11 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA10676 for ; Wed, 1 Jan 1997 18:54:09 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id SAA24067; Wed, 1 Jan 1997 18:54:02 -0800 (PST) To: Thomas David Rivers cc: hackers@freebsd.org, ponds!resnet.uoregon.edu!gurney_j@ucbvax.Berkeley.EDU Subject: Re: 2.2-BETA, timezone and the PC clock... In-reply-to: Your message of "Wed, 01 Jan 1997 20:19:50 EST." <199701020119.UAA08809@lakes.water.net> Date: Wed, 01 Jan 1997 18:54:02 -0800 Message-ID: <24059.852173642@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm guessing that the question just went missing from sysinstall... > > Should it have? It was never in sysinstall - it was in tzsetup, which Garrett recently changed. :) Jordan From owner-freebsd-hackers Wed Jan 1 19:16:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11974 for hackers-outgoing; Wed, 1 Jan 1997 19:16:29 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA11963 for ; Wed, 1 Jan 1997 19:16:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA13645; Wed, 1 Jan 1997 19:15:55 -0800 (PST) Message-Id: <199701020315.TAA13645@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Julian Assange cc: hackers@freebsd.org Subject: Re: struct file locking From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Jan 1997 19:15:55 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>In the socket structure I intend to create a back-pointer to >>originating struct file's->u_cred. What do I need to do to insure >>these last two structures are reliably locked and in memory? (To which I said): > See crhold() in sys/ucred.h and crfree() in sys/kern/kern_prot.c. They >manage the cr_ref reference count. ...err, I should have read your message more carefully. f_count on the file descriptor is what holds the references to the descriptor, but I don't think you can do precisely what you want without actually doing a dup. You might be able to do a fp->f_count++, and later a closef() to lose the reference, but that depends entirely on the context of things. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Jan 1 19:26:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA12441 for hackers-outgoing; Wed, 1 Jan 1997 19:26:01 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA12436 for ; Wed, 1 Jan 1997 19:25:58 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id EAA29709; Thu, 2 Jan 1997 04:16:18 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.4/8.8.2) id EAA09688; Thu, 2 Jan 1997 04:06:36 +0100 (MET) Message-ID: Date: Thu, 2 Jan 1997 04:06:36 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: jfieber@indiana.edu (John Fieber) Cc: hackers@FreeBSD.org Subject: Re: New motherboard breaks tape drive References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from "John Fieber" on Jan 1, 1997 19:07:01 -0500 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > How is your kernel config file. What's the SC200 ? > > PCI controller ? AHA 2940 compatible or what ? > NCR. See kernel config below. I think it's a PCI controller ?! I don't know the NCR ones well... > > BTW, did you try team from the ports collection ? > Yes, and it doesn't offer any improvement over dump/tar/dd with > sufficiently large block sizes. Then it must be something other I think... > options BOUNCE_BUFFERS #include support for DMA bounce buffers You only need this option when using SCSI DMA controllers like the AHA 1542B, which only could address 16 MB address space and only in the case when having more than 16MB of system memory. It might be the case, that this bounce buffering brings your system's performance down. Another good idea would be, to create a very small kernel without many kernel options like DEVFS and other options... Strip down GENERIC, since it has less "esoteric" options in it and reduce it to the drivers you really need... This might also help tracking down the "bug" ... But I think BOUNCE_BUFFERS might be the real culprit... Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Wed Jan 1 22:28:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA18477 for hackers-outgoing; Wed, 1 Jan 1997 22:28:39 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA18472 for ; Wed, 1 Jan 1997 22:28:37 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id HAA04931; Thu, 2 Jan 1997 07:27:15 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id GAA11224; Thu, 2 Jan 1997 06:55:23 +0100 (MET) Message-Id: <3.0.32.19970102065739.00999720@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 02 Jan 1997 06:57:40 +0100 To: "Mark J. Taylor" From: Eivind Eklund Subject: Re: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:25 PM 12/31/96 -0500, Mark J Taylor wrote: > >I remember several years back that people were complaining about how long >it takes to do a checksum during the installation, so putting it back in >would probably be a bad idea. "Several years" probably means a speed increase an order of magnitude. I'm not certain this would be a problem :) >However, putting the MD5 checksums in and optionally NOT using them >during installation sounds like a good idea (it would be a nice little >security feture, put into sysinstall's "options" screen). I agree. They should be enabled by default. Do these checksums check what is actually on the disk after install, or just the tarballs that have been downloaded? I would consider both useful. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-hackers Wed Jan 1 23:13:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA20360 for hackers-outgoing; Wed, 1 Jan 1997 23:13:04 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA20351 for ; Wed, 1 Jan 1997 23:12:57 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id CAA09967; Thu, 2 Jan 1997 02:10:23 -0500 From: Bill Paul Message-Id: <199701020710.CAA09967@skynet.ctr.columbia.edu> Subject: Re: struct file locking To: proff@iq.org (Julian Assange) Date: Thu, 2 Jan 1997 02:10:22 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199701012224.JAA06593@profane.iq.org> from "Julian Assange" at Jan 2, 97 09:24:38 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Julian Assange had to walk into mine and say: > I am expanding the inet/socket code to permit firewall entries > based on uid/gid. I have an aesthetic issue and one locking > issue. > > I need to pass socket credential information into ip_output. There > are two ways of doing this. I can add a back-pointer to the socket > structure from the struct ipoption mbuf, or I can add an extra > parameter to ip_output. I am inclinded towards the first option, > for source-level compatability reasons. > > In the socket structure I intend to create a back-pointer to > originating struct file's->u_cred. What do I need to do to insure > these last two structures are reliably locked and in memory? > > Cheers, > Julian. I have a question. Say you have the following series of events: - A process creates a socket. o You now have a struct socket. o You also have a struct file that references the socket, and that points to the ucred of the process. - The process forks. o Now the child and the parent refer to the same socket. - The child does a setuid() to some other UID. o You still only have one socket. What happens now? You have one socket referenced by two proccesses with different credentials (I think -- not sure what happens to the credentials in inherited descriptors when a process does a setuid()). This is kind of an odd situation; you probably don't want both processes reading or writing to the same socket, but in theory they could, so you need to account for this somehow. Assuming you can get at both sets of credentials, how do you know which ones to use? -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" ============================================================================= From owner-freebsd-hackers Thu Jan 2 01:22:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA24901 for hackers-outgoing; Thu, 2 Jan 1997 01:22:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA24896 for ; Thu, 2 Jan 1997 01:22:11 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA04563; Thu, 2 Jan 1997 10:21:17 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA04653; Thu, 2 Jan 1997 10:21:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA04298; Thu, 2 Jan 1997 10:14:45 +0100 (MET) From: J Wunsch Message-Id: <199701020914.KAA04298@uriah.heep.sax.de> Subject: Re: 2.2-BETA, timezone and the PC clock... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 2 Jan 1997 10:14:45 +0100 (MET) Cc: ponds!rivers@dg-rtp.dg.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <24059.852173642@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 1, 97 06:54:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > I'm guessing that the question just went missing from sysinstall... > > > > Should it have? > > It was never in sysinstall - it was in tzsetup, which Garrett recently > changed. :) But i think we should put it into sysinstall it now, don't we? It's only losely related to the zoneinfo files. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 2 02:11:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA26353 for hackers-outgoing; Thu, 2 Jan 1997 02:11:31 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA26345 for ; Thu, 2 Jan 1997 02:11:28 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id CAA06692; Thu, 2 Jan 1997 02:10:04 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org (FreeBSD hackers), ponds!rivers@dg-rtp.dg.com Subject: Re: 2.2-BETA, timezone and the PC clock... In-reply-to: Your message of "Thu, 02 Jan 1997 10:14:45 +0100." <199701020914.KAA04298@uriah.heep.sax.de> Date: Thu, 02 Jan 1997 02:10:04 -0800 Message-ID: <6688.852199804@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But i think we should put it into sysinstall it now, don't we? It's > only losely related to the zoneinfo files. What are you suggesting, exactly? Jordan From owner-freebsd-hackers Thu Jan 2 02:32:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27418 for hackers-outgoing; Thu, 2 Jan 1997 02:32:01 -0800 (PST) Received: from calvino.alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27402 for ; Thu, 2 Jan 1997 02:31:56 -0800 (PST) Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id BAA11849; Thu, 2 Jan 1997 01:31:45 -0900 (AKST) Date: Thu, 2 Jan 1997 01:31:43 -0900 (AKST) From: hmmm Reply-To: hmmm To: Michael Smith cc: freebsd-hackers Subject: Re: Ints In-Reply-To: <199701020235.NAA14968@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Michael Smith wrote: > If you're operating in a polled environment, you're not using an IRQ. if you POLL a device for a response received via interrupts, then you ARE polling ... :) > The highest pending interrupt status is presented in the IIR. If you > perform an action that clears an interrupt status, the IIR may change. MAY change - or DOES change ? is it usually a circuit outside of CPU concerns? do INT status flags change EXACTLY as the condition is removed? > Merely responding to the interrupt does not alter the state of the IIR. > ... controller presents a single interrupt signal to the PIC. You isn't the signal removed after the PIC responds to the device ? ... so that the IRQ line is now "free" again - and may be interrupted by the same device with its own higher priority interrupt ? > must clear all the enabled internal interrupt states within the UART > in order to clear the interrupt output and thus allow the PIC to detect > a new interrupt. but the device HAS to ASSERT its IRQ again in order to have another of its interrupts served - so it must DE-ACTIVATE the IRQ line at some time - and i'm pretty sure it's right after the PIC acknowledges the devices request - so that it can interrupt one of its own ISRs by one of its own higher priority interrupts ... ??? i'm probably wrong! :( maybe i've been working with the SCC too long ... From owner-freebsd-hackers Thu Jan 2 02:36:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27598 for hackers-outgoing; Thu, 2 Jan 1997 02:36:35 -0800 (PST) Received: from calvino.alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27593 for ; Thu, 2 Jan 1997 02:36:32 -0800 (PST) Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id BAA12289; Thu, 2 Jan 1997 01:36:23 -0900 (AKST) Date: Thu, 2 Jan 1997 01:36:22 -0900 (AKST) From: hmmm To: Michael Smith cc: freebsd-hackers Subject: Re: Ints (fwd) In-Reply-To: <199701020251.NAA14993@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Michael Smith wrote: > > true, but that's because of edge triggered lines as you say later. > > Were they level sensitive, there would be no problem in sharing > > them. > Err yes. But like we said, they ain't. 8) huh - i remember myself have the option of EDGE or LEVEL triggers in my PIC ... that's interesting ... that must be a device limitation ? From owner-freebsd-hackers Thu Jan 2 02:42:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27811 for hackers-outgoing; Thu, 2 Jan 1997 02:42:15 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27800 for ; Thu, 2 Jan 1997 02:42:01 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id VAA11426 for hackers@freebsd.org; Thu, 2 Jan 1997 21:41:37 +1100 (EST) From: Julian Assange Message-Id: <199701021041.VAA11426@profane.iq.org> Subject: file locking / firewalling based on uid/gid In-Reply-To: <199701020710.CAA09967@skynet.ctr.columbia.edu> from Bill Paul at "Jan 2, 97 02:10:22 am" To: hackers@freebsd.org Date: Thu, 2 Jan 1997 21:41:37 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have a question. > > Say you have the following series of events: > > - A process creates a socket. > o You now have a struct socket. > o You also have a struct file that references the socket, and that > points to the ucred of the process. > > - The process forks. > o Now the child and the parent refer to the same socket. > > - The child does a setuid() to some other UID. > o You still only have one socket. > > What happens now? You have one socket referenced by two proccesses > with different credentials (I think -- not sure what happens to the > credentials in inherited descriptors when a process does a setuid()). Looked at this. You retain pointers to the original credentials. This is the probably way you want things to be, because of situations like: inetd(root,socket) -> rsh(user) Where by you want root to be able to accept/make connections on behalf of users that do not have such an ability. What is interesting about the inetd situation, is that without introducing an enhanced bind()/PORT_RESERVED access controller, we can forbid root to pass traffic, but permit inetd, running as root, to accept incoming connections. e.g # killall inetd # addgroup inetd # chgrp inetd /usr/sbin/inetd # chmod g+s /usr/sbin/inetd # inetd # ipfw add pass tcp from any to any established gid inetd # ipfw add padd tcp from any to any 21,79 setup in gid inetd Is a good start at eliminating covert channels. Speaking of inetd, does someone care to commit my virtual hosting patches? Cheers, Julian. From owner-freebsd-hackers Thu Jan 2 02:45:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27892 for hackers-outgoing; Thu, 2 Jan 1997 02:45:18 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27880 for ; Thu, 2 Jan 1997 02:45:11 -0800 (PST) Message-Id: <199701021045.CAA27880@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA164321724; Thu, 2 Jan 1997 21:42:04 +1100 From: Darren Reed Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: terry@lambert.org (Terry Lambert) Date: Thu, 2 Jan 1997 21:42:04 +1100 (EDT) Cc: avalon@coombs.anu.edu.au, terry@lambert.org, julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612310244.TAA01346@phaeton.artisoft.com> from "Terry Lambert" at Dec 30, 96 07:44:14 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Terry Lambert, sie said: > > > > This is what I've been calling "layering problems". It is definitely > > > a goal of mine to allow a module to be debugged in user space with a > > > source level debugger. > > > > Making code that compiles in the kernel also compile for user programs > > is tricky if you only want _one_ routine for both. > > I beg to disagree... PIC objects don't care whose address space > they are loaded or copied into... code is relatively addressed and > doesn't really care post-relocation if the relocation was by way > of ld -A or by way of dlopen. However, some simple functions such as malloc() are *much* different when compiled for kernel vs user. You can't compile a routine in user-space that uses mbufs without doing some extra work. Then you have to deal with spl's that don't exist, etc. And so on. I was thinking about this the other day and wondered how easy would it be to make the kernel compile as a user process ? Darren From owner-freebsd-hackers Thu Jan 2 02:46:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27922 for hackers-outgoing; Thu, 2 Jan 1997 02:46:14 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27917 for ; Thu, 2 Jan 1997 02:46:10 -0800 (PST) Message-Id: <199701021046.CAA27917@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA165621948; Thu, 2 Jan 1997 21:45:48 +1100 From: Darren Reed Subject: Re: bootloader & memory test... To: hans@brandinnovators.com (Hans Zuidam) Date: Thu, 2 Jan 1997 21:45:48 +1100 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199612271048.KAA05227@truk.brandinnovators.com> from "Hans Zuidam" at Dec 27, 96 10:48:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Hans Zuidam, sie said: > > Hi, > > After about a year of sig-11 plague I decided to find exactly what was > wrong with the memory of my system and found a program called MemTest-86 > by Chris Brady. It is the only one that's indeed reporting errors, none > of the DOS based ones found anything! > > To narrow the search space I would like to make some modifications, but > the sources use a modified version of the Linux boot loader. To make > things worse apparently two different assembler syntaxes (AT&T and Intel) > are used and I am not well versed (to say the least) in either. > > The memory test sets the CPU for flat 32 bit addressing and loads itself > to address 0x100. It uses the area from 0x0 to 0xFF as it's stack. Could > someone give me a hand (or pointers) to achieve the same using the FreeBSD > boot loader? Thanks in advance, I haven't delved too deeply, but how hard would it be to have the kernel's idle loop do a memory test ? Darren From owner-freebsd-hackers Thu Jan 2 03:34:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA29736 for hackers-outgoing; Thu, 2 Jan 1997 03:34:45 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA29731 for ; Thu, 2 Jan 1997 03:34:42 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id WAA16141; Thu, 2 Jan 1997 22:04:03 +1030 (CST) From: Michael Smith Message-Id: <199701021134.WAA16141@genesis.atrad.adelaide.edu.au> Subject: Re: Ints In-Reply-To: from hmmm at "Jan 2, 97 01:31:43 am" To: hmmm@alaska.net Date: Thu, 2 Jan 1997 22:04:02 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hmmm stands accused of saying: > On Thu, 2 Jan 1997, Michael Smith wrote: > > > If you're operating in a polled environment, you're not using an IRQ. > > if you POLL a device for a response received via interrupts, then you ARE > polling ... :) Please don't go inventing your own terminology in order to prove yourself "right". If you are responding to an interrupt, you are not "polling" as such. > > The highest pending interrupt status is presented in the IIR. If you > > perform an action that clears an interrupt status, the IIR may change. > > MAY change - or DOES change ? is it usually a circuit outside of CPU > concerns? do INT status flags change EXACTLY as the condition is removed? "may" change. If you really want the low-down on how much UART implementations vary, search the FreeBSD mailing list archives for mention of a program called COMTEST in a message from Frank Durda. Basically, there is very little that you can actually count on. > isn't the signal removed after the PIC responds to the device ? > ... so that the IRQ line is now "free" again - and may be interrupted > by the same device with its own higher priority interrupt ? No. > > must clear all the enabled internal interrupt states within the UART > > in order to clear the interrupt output and thus allow the PIC to detect > > a new interrupt. > > but the device HAS to ASSERT its IRQ again in order to have another of its > interrupts served - so it must DE-ACTIVATE the IRQ line at some time - and > i'm pretty sure it's right after the PIC acknowledges the devices > request - so that it can interrupt one of its own ISRs by one of its own > higher priority interrupts ... ??? i'm probably wrong! :( You're wrong. There is no automatic interrupt-acknowledge on the ISA bus. The PIC interrupts the processor when an input goes from inactive to active. It is the processor's responsibility to manipulate the peripheral so that the input goes inactive again. If it fails to do so, there will be no more interrupts from it. Finito. > maybe i've been working with the SCC too long ... Perhaps you have been working in non-ISA environments too long. The M68K has a slightly more sane interrupt management scheme, as do some RISC processors. Intel don't appear to have got it right with the APIC either (I can't say for sure having never had to talk to one myself.) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jan 2 04:33:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA02122 for hackers-outgoing; Thu, 2 Jan 1997 04:33:02 -0800 (PST) Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA02116 for ; Thu, 2 Jan 1997 04:32:56 -0800 (PST) Received: (from jlk@localhost) by deputy.pavilion.co.uk (8.7/8.7) id MAA12511 for hackers@freebsd.org; Thu, 2 Jan 1997 12:32:18 GMT From: Joe Karthauser Message-Id: <199701021232.MAA12511@deputy.pavilion.co.uk> Subject: Frontpage extensions core dump. To: hackers@freebsd.org Date: Thu, 2 Jan 1997 12:32:18 +0000 (GMT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Guys, Any ideas? I've been trying to run the Microsoft Frontpage extensions, which are BSDI binaries. Even though the FreeBSD website says this should be possible all I get are core dumps. Can you help? (If microsoft released the source it wouldn't be a problem ;) Have any of you got any experience with this? Joe. -- Josef Karthauser (joe@pavilion.net) Technical Manager [Tel: +44 1273 607072 Fax: +44 1273 607073] Pavilion Internet plc. ._ .. _. _ ._.. .. .._. . __. ._. ._ _. _.. From owner-freebsd-hackers Thu Jan 2 06:26:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA05972 for hackers-outgoing; Thu, 2 Jan 1997 06:26:56 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA05966 for ; Thu, 2 Jan 1997 06:26:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA25585; Thu, 2 Jan 1997 15:21:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA09055; Thu, 2 Jan 1997 15:21:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id OAA07017; Thu, 2 Jan 1997 14:54:47 +0100 (MET) From: J Wunsch Message-Id: <199701021354.OAA07017@uriah.heep.sax.de> Subject: Re: Frontpage extensions core dump. To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 2 Jan 1997 14:54:47 +0100 (MET) Cc: jlk@pavilion.co.uk (Joe Karthauser) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701021232.MAA12511@deputy.pavilion.co.uk> from Joe Karthauser at "Jan 2, 97 12:32:18 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Joe Karthauser wrote: > Any ideas? I've been trying to run the Microsoft Frontpage extensions, > which are BSDI binaries. Even though the FreeBSD website says this should > be possible all I get are core dumps. Which version of FreeBSD? ISTR that these binaries will only run on FreeBSD 2.2. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 2 07:06:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA07568 for hackers-outgoing; Thu, 2 Jan 1997 07:06:13 -0800 (PST) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA07563 for ; Thu, 2 Jan 1997 07:06:10 -0800 (PST) Received: from truk.brandinnovators.com (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 7347 on Thu, 2 Jan 1997 15:43:47 +0100; id PAA07347 efrom: hans@truk.brandinnovators.com; eto: UNKNOWN Received: by truk.brandinnovators.com (8.7.5/BI96070101) for <> id NAA05612; Thu, 2 Jan 1997 13:56:03 GMT Message-Id: <199701021356.NAA05612@truk.brandinnovators.com> From: hans@brandinnovators.com (Hans Zuidam) Subject: Re: bootloader & memory test... To: avalon@coombs.anu.edu.au (Darren Reed) Date: Thu, 2 Jan 1997 13:56:03 +0000 () Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199701021046.CAA27917@freefall.freebsd.org> from Darren Reed at "Jan 2, 97 09:45:48 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Darren Reed wrote: > I haven't delved too deeply, but how hard would it be to have the kernel's > idle loop do a memory test ? Hard, I guess. For one you do not have all memory available to test as the kernel and many processes are using (more or less) random portions. Secondly: what would you do when you do find an error? Raising a panic is in many cases inapropriate. For example: the signal 11 (and 10 & 6) errors I am experiencing are raised by cc1 (the compiler proper) only. From the limited testing I managed to do, I got the suspicion that the errors have something to do with the motherboard and not with the SIMMs as such. Although not perfect I can live with that. Regards and a happy new year, Hans -- H. Zuidam E-Mail: hans@brandinnovators.com Brand Innovators B.V. P-Mail: P.O. Box 1377 de Pinckart 54 5602 BJ Eindhoven, The Netherlands 5674 CC Nuenen Tel. +31 40 2631134, Fax. +31 40 2831138 From owner-freebsd-hackers Thu Jan 2 07:24:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA08356 for hackers-outgoing; Thu, 2 Jan 1997 07:24:05 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA08285 for ; Thu, 2 Jan 1997 07:23:59 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id CAA06199; Fri, 3 Jan 1997 02:21:18 +1100 (EST) Date: Fri, 3 Jan 1997 02:21:17 +1100 (EST) From: "Daniel O'Callaghan" To: Joerg Wunsch cc: FreeBSD hackers , Joe Karthauser Subject: Re: Frontpage extensions core dump. In-Reply-To: <199701021354.OAA07017@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, J Wunsch wrote: > As Joe Karthauser wrote: > > > Any ideas? I've been trying to run the Microsoft Frontpage extensions, > > which are BSDI binaries. Even though the FreeBSD website says this should > > be possible all I get are core dumps. > > Which version of FreeBSD? ISTR that these binaries will only run on > FreeBSD 2.2. Frontpage extensions run on FreeBSD 2.1.5 and greater. Danny From owner-freebsd-hackers Thu Jan 2 08:02:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA09876 for hackers-outgoing; Thu, 2 Jan 1997 08:02:55 -0800 (PST) Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA09865 for ; Thu, 2 Jan 1997 08:02:48 -0800 (PST) Received: (from jlk@localhost) by deputy.pavilion.co.uk (8.7/8.7) id PAA26594; Thu, 2 Jan 1997 15:52:25 GMT From: Joe Karthauser Message-Id: <199701021552.PAA26594@deputy.pavilion.co.uk> Subject: Re: Frontpage extensions core dump. To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 2 Jan 1997 15:52:25 +0000 (GMT) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, jlk@pavilion.co.uk In-Reply-To: from "Daniel O'Callaghan" at Jan 3, 97 02:21:17 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > On Thu, 2 Jan 1997, J Wunsch wrote: > > > As Joe Karthauser wrote: > > > > > Any ideas? I've been trying to run the Microsoft Frontpage extensions, > > > which are BSDI binaries. Even though the FreeBSD website says this should > > > be possible all I get are core dumps. > > > > Which version of FreeBSD? ISTR that these binaries will only run on > > FreeBSD 2.2. > > Frontpage extensions run on FreeBSD 2.1.5 and greater. > I'll give it another go then, but it was my experience that they coredumped under 2.1.5. When's 2.2 release officially? J. -- Josef Karthauser (joe@pavilion.net) Technical Manager [Tel: +44 1273 607072 Fax: +44 1273 607073] Pavilion Internet plc. ._ .. _. _ ._.. .. .._. . __. ._. ._ _. _.. From owner-freebsd-hackers Thu Jan 2 08:56:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13841 for hackers-outgoing; Thu, 2 Jan 1997 08:56:51 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA13815 for ; Thu, 2 Jan 1997 08:56:45 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id LAA11333; Thu, 2 Jan 1997 11:55:31 -0500 (EST) From: John Dyson Message-Id: <199701021655.LAA11333@dyson.iquest.net> Subject: Re: bootloader & memory test... To: hans@brandinnovators.com (Hans Zuidam) Date: Thu, 2 Jan 1997 11:55:31 -0500 (EST) Cc: avalon@coombs.anu.edu.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199701021356.NAA05612@truk.brandinnovators.com> from "Hans Zuidam" at Jan 2, 97 01:56:03 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Darren Reed wrote: > > I haven't delved too deeply, but how hard would it be to have the kernel's > > idle loop do a memory test ? > Hard, I guess. For one you do not have all memory available to > test as the kernel and many processes are using (more or less) > random portions. Secondly: what would you do when you do find an > error? Raising a panic is in many cases inapropriate. > Some machines do "memory scrubbing" and let their ECC mechanisms correct errors. (This would decrease the prob. of multi-bit errors.) John From owner-freebsd-hackers Thu Jan 2 09:07:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14813 for hackers-outgoing; Thu, 2 Jan 1997 09:07:58 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA14730 for ; Thu, 2 Jan 1997 09:07:38 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id SAA29542 for ; Thu, 2 Jan 1997 18:08:05 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id SAA15524 for freebsd-hackers@freefall.cdrom.com; Thu, 2 Jan 1997 18:24:50 +0100 (MET) Date: Thu, 2 Jan 1997 18:24:50 +0100 (MET) From: Christoph Kukulies Message-Id: <199701021724.SAA15524@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: advice sought - Quantum 2GB Atlas broken Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Coming back from a short holiday I powered on a P90 machine with (among other IDE disks) a Quantum 2GB ATLAS XP32150 and the SCSI disks saluted with a continous one second interval clicking noise. It spins up but the head seems to do some wild moves followed by a 'chuck-clack' with the NCR PCI BIOS not coming to an end of the probing phase. At least the NCR BIOS sits there for half an hour already and that noise is repeating unchanged. As always in such situations that disk contained some important data I would like to preserve. Despite of this the disk is still under warranty. So giving it back and waiting 8 weeks for replacement isn't the issue. It's just the data I wish to recover. Does anyone have experience with drive electronics swapping? I have a second disk of that model and I'm tempted to swap the electronics PCB (after having bought the appropriate hex nut driver tomorrow, is that the correct expression :-) I suspect that the electronics stores some bad block info in some kind of nvram on the controller board but not sure about this. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Thu Jan 2 09:30:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17040 for hackers-outgoing; Thu, 2 Jan 1997 09:30:53 -0800 (PST) Received: from itchy.atlas.com ([206.29.170.232]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA17034 for ; Thu, 2 Jan 1997 09:30:49 -0800 (PST) Received: (from brantk@localhost) by itchy.atlas.com (8.8.0/8.8.0) id JAA04200; Thu, 2 Jan 1997 09:29:14 -0800 (PST) Message-Id: <199701021729.JAA04200@itchy.atlas.com> Subject: Re: New motherboard breaks tape drive To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 2 Jan 1997 09:29:14 -0800 (PST) Cc: jfieber@indiana.edu, hackers@FreeBSD.ORG Reply-To: bmk@pobox.com In-Reply-To: from Andreas Klemm at "Jan 2, 97 04:06:36 am" From: "Brant Katkansky" Reply-To: bmk@pobox.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But I think BOUNCE_BUFFERS might be the real culprit... [I'm having the same problem] You might be on to something here. I _think_ that I might still have BOUNCE_BUFFERS in my kernel as well. From owner-freebsd-hackers Thu Jan 2 09:58:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA19443 for hackers-outgoing; Thu, 2 Jan 1997 09:58:56 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA19428 for ; Thu, 2 Jan 1997 09:58:50 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vfrOU-00014j-00; Thu, 2 Jan 1997 09:57:30 -0800 Date: Thu, 2 Jan 1997 09:57:30 -0800 (PST) From: Tom Samplonius To: Joe Karthauser cc: "Daniel O'Callaghan" , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org Subject: Re: Frontpage extensions core dump. In-Reply-To: <199701021552.PAA26594@deputy.pavilion.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Joe Karthauser wrote: > > On Thu, 2 Jan 1997, J Wunsch wrote: > > > > > As Joe Karthauser wrote: > > > > > > > Any ideas? I've been trying to run the Microsoft Frontpage extensions, > > > > which are BSDI binaries. Even though the FreeBSD website says this should > > > > be possible all I get are core dumps. > > > > > > Which version of FreeBSD? ISTR that these binaries will only run on > > > FreeBSD 2.2. > > > > Frontpage extensions run on FreeBSD 2.1.5 and greater. > > > > I'll give it another go then, but it was my experience that they > coredumped under 2.1.5. When's 2.2 release officially? > J. The extensions don't core dump under 2.1.6 for sure. I think maybe some BSDI compat fixes were brought into 2.1.6 that weren't in 2.1.5 However, I can't get any kind of password verification working with the extensions under 2.1.6. Not sure what the problem is. Basically, Frontpage accepts *any* password. > -- > Josef Karthauser (joe@pavilion.net) > Technical Manager [Tel: +44 1273 607072 Fax: +44 1273 607073] > Pavilion Internet plc. ._ .. _. _ ._.. .. .._. . __. ._. ._ _. _.. > > > Tom From owner-freebsd-hackers Thu Jan 2 10:10:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA20336 for hackers-outgoing; Thu, 2 Jan 1997 10:10:48 -0800 (PST) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA20313 for ; Thu, 2 Jan 1997 10:10:41 -0800 (PST) Received: from dolphin.inna.net (jamie@dolphin.inna.net [206.151.66.2]) by tyger.inna.net (8.8.3/8.7.3) with SMTP id NAA20923; Thu, 2 Jan 1997 13:16:14 -0500 (EST) Date: Thu, 2 Jan 1997 13:06:56 -0500 (EST) From: Jamie Bowden To: Christoph Kukulies cc: freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken In-Reply-To: <199701021724.SAA15524@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Your disk is most likey had a head crash. Last time we had a drive do that, when we opened it up, there was the distinctive groove where the head had crashed. It keeps making noises cause it tries and fails to reset the head properly. Hopefully you have recent backups. If you have a spare drive of the same make and model, swapping the electronics is a fairly trivial task. A couple of screws and a connector. On Thu, 2 Jan 1997, Christoph Kukulies wrote: > Coming back from a short holiday I powered on a P90 machine with > (among other IDE disks) a Quantum 2GB ATLAS XP32150 and the SCSI disks > saluted with a continous one second interval clicking noise. > It spins up but the head seems to do some wild moves followed by a > 'chuck-clack' with the NCR PCI BIOS not coming to an end of the probing > phase. At least the NCR BIOS sits there for half an hour already > and that noise is repeating unchanged. > > As always in such situations that disk contained some important data I > would like to preserve. Despite of this the disk is still under warranty. > So giving it back and waiting 8 weeks for replacement isn't the issue. > It's just the data I wish to recover. > > Does anyone have experience with drive electronics swapping? > I have a second disk of that model and I'm tempted to swap the > electronics PCB (after having bought the appropriate hex nut driver > tomorrow, is that the correct expression :-) > > I suspect that the electronics stores some bad block info in some kind > of nvram on the controller board but not sure about this. > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > Jamie Bowden Network Administrator, TBI Ltd. From owner-freebsd-hackers Thu Jan 2 10:21:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21090 for hackers-outgoing; Thu, 2 Jan 1997 10:21:23 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21081 for ; Thu, 2 Jan 1997 10:21:20 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vfrlH-0003ne-00; Thu, 2 Jan 1997 11:21:03 -0700 To: Michael Smith Subject: Re: Ints Cc: hmmm@alaska.net, hackers@freebsd.org In-reply-to: Your message of "Thu, 02 Jan 1997 22:04:02 +1030." <199701021134.WAA16141@genesis.atrad.adelaide.edu.au> References: <199701021134.WAA16141@genesis.atrad.adelaide.edu.au> Date: Thu, 02 Jan 1997 11:21:03 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199701021134.WAA16141@genesis.atrad.adelaide.edu.au> Michael Smith writes: : You're wrong. There is no automatic interrupt-acknowledge on the ISA : bus. The PIC interrupts the processor when an input goes from : inactive to active. It is the processor's responsibility to : manipulate the peripheral so that the input goes inactive again. If : it fails to do so, there will be no more interrupts from it. Finito. In fact, on the MIPS based PCs that were shipped a few years ago, the OS had to deal with almost all of the PIC stuff by hand. The PIC processor wasn't quite powerful enough to do chaining (or wasn't configured to do it), etc. The ISA bus is a horrible abortion wrt other hardware that is available. All the reasonable things one can assume about harware is broken by the ISA bus. Sun had a lot of growning pains when they ported Solaris to x86 because they felt that no sane person would ever design hardware like the ISA bus. Needless to say, they had to fix a bunch of assumptions in their kernels and APIs to allow for things to work reasonably well on the Intel/ISA architecture. It is very un-sun-like (eg not sbus or VME at all). The good news is that they seem to have it fixed and things work on the intel at least as well as they work on Sparc. Warner From owner-freebsd-hackers Thu Jan 2 10:34:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA22227 for hackers-outgoing; Thu, 2 Jan 1997 10:34:49 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA22222 for ; Thu, 2 Jan 1997 10:34:46 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA23285; Thu, 2 Jan 1997 10:33:27 -0800 Date: Thu, 2 Jan 1997 10:33:27 -0800 (PST) From: "Brian N. Handy" To: Christoph Kukulies Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken In-Reply-To: <199701021724.SAA15524@gilberto.physik.rwth-aachen.de> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Coming back from a short holiday I powered on a P90 machine with >(among other IDE disks) a Quantum 2GB ATLAS XP32150 and the SCSI disks >saluted with a continous one second interval clicking noise. >It spins up but the head seems to do some wild moves followed by a >'chuck-clack' with the NCR PCI BIOS not coming to an end of the probing >phase. At least the NCR BIOS sits there for half an hour already >and that noise is repeating unchanged. I had this happen to one of these drives I purchased from Rod Grimes. What this is, if I remember correctly, is some sort of thermal calibration thingy that ... uh ... isn't. I think it's a mechanical problem, not a PCB problem. I don't believe swapping out the electronics here is going to save you. You might ask Rod, or the Quantum Gods. But it sounds like if you want that data you're going to have to send it to a disk-drive restoration outfit. ($2,500 and three days and you're back in business...) Good luck, Brian From owner-freebsd-hackers Thu Jan 2 11:05:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23910 for hackers-outgoing; Thu, 2 Jan 1997 11:05:00 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA23902 for ; Thu, 2 Jan 1997 11:04:57 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id UAA02808; Thu, 2 Jan 1997 20:06:55 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id UAA15982; Thu, 2 Jan 1997 20:23:43 +0100 (MET) From: Christoph Kukulies Message-Id: <199701021923.UAA15982@gilberto.physik.rwth-aachen.de> Subject: Re: advice sought - Quantum 2GB Atlas broken In-Reply-To: from "Brian N. Handy" at "Jan 2, 97 10:33:27 am" To: handy@sag.space.lockheed.com (Brian N. Handy) Date: Thu, 2 Jan 1997 20:23:43 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >Coming back from a short holiday I powered on a P90 machine with > >(among other IDE disks) a Quantum 2GB ATLAS XP32150 and the SCSI disks > >saluted with a continous one second interval clicking noise. > >It spins up but the head seems to do some wild moves followed by a > >'chuck-clack' with the NCR PCI BIOS not coming to an end of the probing > >phase. At least the NCR BIOS sits there for half an hour already > >and that noise is repeating unchanged. > > I had this happen to one of these drives I purchased from Rod Grimes. > What this is, if I remember correctly, is some sort of thermal calibration > thingy that ... uh ... isn't. Interesting that you are saying that (thermal calibration - not Rod Grimes :-) (I think Rod is not responsible in any way for faulty Quantum drives) When I was out for that 6 days vacation over Chrismas and New Year I switched off that machine - only to do my wife a favor because she always asks me "must these computers run all over the night and day" and lowered the room temperature which may well have been as low as 10 Degrees Celsius (em er, where is my K&R book ... 50 Degrees Fahrenheit) when I came back. I switched on the computer and the disaster began. > I think it's a mechanical problem, not a PCB problem. I don't believe > swapping out the electronics here is going to save you. You might ask > Rod, or the Quantum Gods. But it sounds like if you want that data you're > going to have to send it to a disk-drive restoration outfit. ($2,500 and > three days and you're back in business...) > > Good luck, > > Brian > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Thu Jan 2 11:22:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA25052 for hackers-outgoing; Thu, 2 Jan 1997 11:22:36 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA25043 for ; Thu, 2 Jan 1997 11:22:30 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA17173 for ; Thu, 2 Jan 1997 20:21:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA14901 for freebsd-hackers@freebsd.org; Thu, 2 Jan 1997 20:21:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA08261 for freebsd-hackers@freebsd.org; Thu, 2 Jan 1997 19:01:44 +0100 (MET) From: J Wunsch Message-Id: <199701021801.TAA08261@uriah.heep.sax.de> Subject: Re: advice sought - Quantum 2GB Atlas broken To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 2 Jan 1997 19:01:43 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701021724.SAA15524@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Jan 2, 97 06:24:50 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Christoph Kukulies wrote: > Does anyone have experience with drive electronics swapping? > I have a second disk of that model and I'm tempted to swap the > electronics PCB... (Moved to -scsi.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 2 11:36:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA26000 for hackers-outgoing; Thu, 2 Jan 1997 11:36:46 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA25995 for ; Thu, 2 Jan 1997 11:36:44 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA15424; Thu, 2 Jan 1997 11:36:09 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma015422; Thu Jan 2 11:36:06 1997 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id LAA26380; Thu, 2 Jan 1997 11:36:06 -0800 (PST) From: Archie Cobbs Message-Id: <199701021936.LAA26380@bubba.whistle.com> Subject: Re: divert code not thread/smp compatible In-Reply-To: <32C858F6.41C67EA6@whistle.com> from Julian Elischer at "Dec 30, 96 04:06:14 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 2 Jan 1997 11:36:06 -0800 (PST) Cc: proff@iq.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > /* > > * ip_input() and ip_output() set this secret value before calling us to > > * let us know which divert port to divert a packet to; this is done so > > * we can use the existing prototype for struct protosw's pr_input(). > > * This is stored in host order. > > */ > > u_short ip_divert_port; > > > > /* > > * We set this value to a non-zero port number when we want the call to > > * ip_fw_chk() in ip_input() or ip_output() to ignore ``divert '' > > * chain entries. This is stored in host order. > > */ > > u_short ip_divert_ignore; > > > > Is this an acceptable trick in the FreeBSD kernel, passing parameters > > with global variables? > > > > -Julian My only excuse is that at the time I started writing the divert code, it wasn't planned on being checked in to the main branch, but instead was going to be a patch to be applied locally... so I tried to keep the patch as small as possible... and as a result committed some non-esthetically pleasing programming in the process... :-) Any suggestions on the best way to properly threadify this? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jan 2 11:40:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA26222 for hackers-outgoing; Thu, 2 Jan 1997 11:40:28 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA26216 for ; Thu, 2 Jan 1997 11:40:22 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id OAA01115; Thu, 2 Jan 1997 14:39:46 -0500 (EST) Date: Thu, 2 Jan 1997 14:39:45 -0500 (EST) From: John Fieber To: bmk@pobox.com cc: Andreas Klemm , hackers@FreeBSD.ORG Subject: Re: New motherboard breaks tape drive In-Reply-To: <199701021729.JAA04200@itchy.atlas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Brant Katkansky wrote: > > But I think BOUNCE_BUFFERS might be the real culprit... > > [I'm having the same problem] > > You might be on to something here. I _think_ that I might still have > BOUNCE_BUFFERS in my kernel as well. I took BOUNCE_BUFFERS out (I had thought the sound card would need it, but so far no crash...). No change. I still max out at about 60K/second, far short of the 100K/second that was the norm before the "upgrade". :( Aside from the addition of the pci bus driver, the ncr scsi driver and the removal of the aha driver, the kernel config is exactly the same as it was befor the upgrade. -john From owner-freebsd-hackers Thu Jan 2 11:59:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA27029 for hackers-outgoing; Thu, 2 Jan 1997 11:59:52 -0800 (PST) Received: from intercore.com (num1sun.intercore.com [199.181.243.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA27024 for ; Thu, 2 Jan 1997 11:59:49 -0800 (PST) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id OAA08144; Thu, 2 Jan 1997 14:52:09 -0500 (EST) Message-Id: <199701021952.OAA08144@intercore.com> Date: Thu, 2 Jan 1997 14:52:09 -0500 From: robin@intercore.com (Robin Cutshaw) To: hackers@FreeBSD.Org Subject: tcp problems with 2.1.6.1 X-Mailer: Mutt 0.47 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk Recently while supping the XFree86 tree, I noticed that one of my boxes was having timeout problems. It's a P90/64MB/FreeBSD-2.1.6.1 box. I watched the ethernet and noticed a large number of packets received that got no ack from the FreeBSD box. This caused a large number of retransmits. The other boxes on this net don't seem to have this problem so I thought I'd ask the FreeBSD group if anyone has seen anything like this. BTW, the sup host was a FreeBSD box as well. Thanks, robin -- ---- Robin Cutshaw internet: robin@interlabs.com robin@intercore.com Internet Labs, Inc. BellNet: 404-817-9787 "Time is just one damn thing after another" -- PBS/Nova ---- -- From owner-freebsd-hackers Thu Jan 2 12:09:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27689 for hackers-outgoing; Thu, 2 Jan 1997 12:09:05 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA27661 for ; Thu, 2 Jan 1997 12:08:39 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id HAA12208; Fri, 3 Jan 1997 07:07:31 +1100 (EST) From: Julian Assange Message-Id: <199701022007.HAA12208@profane.iq.org> Subject: Re: divert code not thread/smp compatible In-Reply-To: <199701021936.LAA26380@bubba.whistle.com> from Archie Cobbs at "Jan 2, 97 11:36:06 am" To: archie@whistle.com (Archie Cobbs) Date: Fri, 3 Jan 1997 07:07:31 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Is this an acceptable trick in the FreeBSD kernel, passing parameters > > > with global variables? > > > > > > -Julian > > My only excuse is that at the time I started writing the divert code, > it wasn't planned on being checked in to the main branch, but instead > was going to be a patch to be applied locally... so I tried to keep > the patch as small as possible... and as a result committed some > non-esthetically pleasing programming in the process... :-) > > Any suggestions on the best way to properly threadify this? > > Thanks, > -Archie Well, I looked at threading/locking issues in netinet/* generally and have come to view the chances of seeing more than one thread in anything close to the bsd44 inet code is zero. The whole thing is locked by a few fat, totally non-granular splnet()s. While we are on the subjects of locking, I notice a distinct lack of atomic test-and-set or test-and-inc instructions for struct usage counts (which are instead relying on non-atomic C). Is there such an existing kernel macro that does: int tas(slock_t *m) { slock_t res; __asm__("xchgb %0,%1":"=q" (res),"=m" (*m):"0" (0x1)); return(res); } -Julian From owner-freebsd-hackers Thu Jan 2 12:11:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27842 for hackers-outgoing; Thu, 2 Jan 1997 12:11:04 -0800 (PST) Received: from inner.cortx.com (root@[207.207.221.8]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA27836 for ; Thu, 2 Jan 1997 12:11:01 -0800 (PST) Received: (from costa@localhost) by inner.cortx.com (8.6.12/8.6.12) id PAA07447; Thu, 2 Jan 1997 15:12:10 GMT Date: Thu, 2 Jan 1997 15:12:10 +0000 () From: Costa To: hackers@freebsd.org Subject: recommendation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk currently, i am running freebsd 2.1 on a 1.2 gig scsi drive. I partitioned my drive so that root had 300MB and usr had 800Mb and the rest went to swap. I want to add a 2 gig drive and move my current usr directory to the new drive leaving all the same. Is this the best way (and least downtime) to handle this? If there is a better way please advise me. thanks, costa ==================C=O=R=T=E=X==C=O=M=M=U=N=I=C=A=T=I=O=N=S================== Costa J Morris - Partner Full Service Internet Access http://www.cortx.com Interactive CGI Scripting costa@cortx.com Internet Consulting 201-567-2297 Web Design ============================================================================ From owner-freebsd-hackers Thu Jan 2 12:53:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA01941 for hackers-outgoing; Thu, 2 Jan 1997 12:53:16 -0800 (PST) Received: from titan.cs.mci.com (titan.cs.mci.com [166.37.6.15]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA01924 for ; Thu, 2 Jan 1997 12:53:12 -0800 (PST) Received: from localhost by titan.cs.mci.com; (5.65v3.2/1.1.8.2/22Aug96-0234PM) id AA01327; Thu, 2 Jan 1997 13:52:40 -0700 Date: Thu, 2 Jan 1997 13:52:40 -0700 (MST) From: "Thomas S. Traylor" To: freebsd-hackers@freebsd.org Subject: Message queue question Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey, The value of MSGTQL is the max number of message headers system wided. Given that (if this is the correct definition of MSGTQL), is there a way to tell how many message headers there are system wide? I'm interested in obtaining this value via a program and not with the debugger. Thanks, Tom -- Thomas Traylor Thomas.Traylor@mci.com ttraylor@titan.cs.mci.com (719) 535-1269 From owner-freebsd-hackers Thu Jan 2 13:14:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03417 for hackers-outgoing; Thu, 2 Jan 1997 13:14:36 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA03410 for ; Thu, 2 Jan 1997 13:14:28 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id FAA09846 for freebsd-hackers@freebsd.org; Fri, 3 Jan 1997 05:14:21 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: Thu, 2 Jan 1997 20:28:59 GMT From: mark@putte.seeware.DIALix.oz.au (Mark Hannon) Message-ID: Organization: Private FreeBSD site Subject: ft < 50kb/s ?? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have been a user of the ft tape driver for a number of years. Over time I have swapped my tape drive between different motherboards and controllers. The drive has served me well (especially with the lft utility instead of the standard ft driver) in general, however in the current configuration it is dead slow - It just took me 12 hours to back up 200m of data, according to the manufacturers notes it should be able to do 1Mbit/second, which is around 30minutes. What can I be doing wrong? I have moved the tape driver over to a 486-100 motherboard with onboard floppy-disk controller. I have now also moved the drive over to another machine and floppy controller, exactly the same results. I have yet to check the drives performance under DOS. How can I measure/monitor the performance? Regards/Mark -- +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ From owner-freebsd-hackers Thu Jan 2 13:21:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA04025 for hackers-outgoing; Thu, 2 Jan 1997 13:21:58 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA04013 for ; Thu, 2 Jan 1997 13:21:54 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.6/8.7.3) with ESMTP id NAA00361; Thu, 2 Jan 1997 13:20:34 -0800 (PST) Message-Id: <199701022120.NAA00361@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Tom Samplonius cc: Joe Karthauser , "Daniel O'Callaghan" , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org Subject: Re: Frontpage extensions core dump. In-reply-to: Your message of "Thu, 02 Jan 1997 09:57:30 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Jan 1997 13:20:34 -0800 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Tom Samplonius : > The extensions don't core dump under 2.1.6 for sure. I think maybe some > BSDI compat fixes were brought into 2.1.6 that weren't in 2.1.5 > > However, I can't get any kind of password verification working with the > extensions under 2.1.6. Not sure what the problem is. Basically, > Frontpage accepts *any* password. I had to add the passwords manually with htpasswd after that FrontPage was able to verify the passwords. Amancio From owner-freebsd-hackers Thu Jan 2 13:52:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA06098 for hackers-outgoing; Thu, 2 Jan 1997 13:52:56 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA06092 for ; Thu, 2 Jan 1997 13:52:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA28309; Thu, 2 Jan 1997 22:52:34 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA18191; Thu, 2 Jan 1997 22:52:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA11065; Thu, 2 Jan 1997 22:50:48 +0100 (MET) Message-ID: Date: Thu, 2 Jan 1997 22:50:48 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Cc: costa@inner.cortx.com (Costa) Subject: Re: recommendation References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Costa on Jan 2, 1997 15:12:10 +0000 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Costa wrote: > currently, i am running freebsd 2.1 on a 1.2 gig scsi drive. I > partitioned my drive so that root had 300MB and usr had 800Mb and the > rest went to swap. > > I want to add a 2 gig drive and move my current usr directory to the new > drive leaving all the same. Is this the best way (and least downtime) to > handle this? Probably yes. Also, you might consider to allocate another 100 MB of swap space on the second disk. Sharing swap among spindles might speed up paging. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 2 14:17:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07846 for hackers-outgoing; Thu, 2 Jan 1997 14:17:48 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07839 for ; Thu, 2 Jan 1997 14:17:44 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBF8C8.21DD75D0@kaori.communique.net>; Thu, 2 Jan 1997 16:15:12 -0600 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Subject: Panic - Maloc: lost data....... (auch) Date: Thu, 2 Jan 1997 16:14:55 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello there! Two questions: can I set the server (2.1.6R) to automatically restart if it crashes ? Is there a utility I can run in order to have an idea of what caused the problem (or do I have to recompile with kernel debug on?) And then, how do I interpret the results of the core dump ? Thanks. ---------------------------------------------- Raul Zighelboim mailto:mango@communique.net Communique Inc. http://communique.net From owner-freebsd-hackers Thu Jan 2 14:26:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA08370 for hackers-outgoing; Thu, 2 Jan 1997 14:26:05 -0800 (PST) Received: from tibet.stepnet.com ([206.14.120.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA08365 for ; Thu, 2 Jan 1997 14:26:02 -0800 (PST) Received: (from ping@localhost) by tibet.stepnet.com (8.7.6/8.7.3) id OAA06911 for freebsd-hackers@freebsd.org; Thu, 2 Jan 1997 14:26:06 -0800 (PST) From: Ping Mai Message-Id: <199701022226.OAA06911@tibet.stepnet.com> Subject: split function missing? To: freebsd-hackers@freebsd.org Date: Thu, 2 Jan 1997 14:26:06 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has the split function been taken out of nvi? ping From owner-freebsd-hackers Thu Jan 2 14:31:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA08710 for hackers-outgoing; Thu, 2 Jan 1997 14:31:30 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA08704 for ; Thu, 2 Jan 1997 14:31:27 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA18490; Thu, 2 Jan 1997 17:30:52 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 2 Jan 1997 17:30 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id RAA07987; Thu, 2 Jan 1997 17:05:42 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id RAA11164; Thu, 2 Jan 1997 17:09:12 -0500 (EST) Date: Thu, 2 Jan 1997 17:09:12 -0500 (EST) From: Thomas David Rivers Message-Id: <199701022209.RAA11164@lakes.water.net> To: leclaire@venus.net, ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: timezone stuff (2.2-BETA) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Thu, 2 Jan 1997, Timothy Brown wrote: > > > Question: > > > > Windows 95 boots up. It tells me the time is proper (9am or whatever). > > FreeBSD boots up. It has the CST timezone installed, so it interprets the > > time at, like, 2am or something. > > > > The question is (and I know this is an easy hack, humour me): is this the > > intended behaviour? > > > > If I was just running FreeBSD, this would be fine, but i'm not... I know I > > can always hack out the timezone stuff, or just install GMT... > > > > Am I making any sense? > > > > Tim > > > > -- > > Timothy Brown, Web Architect/Network Engineer, ANET-STL > > Affiliation given for identification, not representation. > > http://www.anet-stl.com/~tbrown/ > > > > > I had this problem after upgrading from 2.2-ALPHA to 2.2-BETA.I guess it's > one of the things the upgrade part of sysinstall isn't "intelligent" > enough to do. For details, man adjkerntz. > su > cd /etc > touch wall_cmos_clock > Yes - that seems to be the correct procedure. But, sysinstall used to perform it quite nicely (for v2.1.0 - v2.1.6), after a little question like "Is your CMOS clock set to local time or UMT or Don't care?". That appears to be the item that's gone missing, or isn't working correctly for 2.2-BETA. - Dave Rivers - From owner-freebsd-hackers Thu Jan 2 14:36:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA09054 for hackers-outgoing; Thu, 2 Jan 1997 14:36:55 -0800 (PST) Received: (from julian@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA09044 for hackers; Thu, 2 Jan 1997 14:36:49 -0800 (PST) Date: Thu, 2 Jan 1997 14:36:49 -0800 (PST) From: Julian Elischer Message-Id: <199701022236.OAA09044@freefall.freebsd.org> To: hackers Subject: New Networking framework for BSD Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have (mostly) written a new networking framework for BSD which allows us to achieve nearly all the features of STREAMS, but with hopefully more flexibility. I am initially using this with some Frame relay stuff but it will eventually be filled out more I hope, with modules for ISDN, ATM and other transport level modules. As well it has the built in ability to allow arbitrary 'graphs' of processing nodes, to be created and configured. It has no inherrent 'up or 'down' as streams has.. I'd like to lay it out before a few people and discuss it and get comments. I'll be writing a short description today. If anyone is interested, let me know and I'll send you a copy! julian From owner-freebsd-hackers Thu Jan 2 14:55:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA10023 for hackers-outgoing; Thu, 2 Jan 1997 14:55:12 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA10018 for ; Thu, 2 Jan 1997 14:55:10 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id OAA12780 for ; Thu, 2 Jan 1997 14:55:01 -0800 (PST) Date: Thu, 2 Jan 1997 14:55:01 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Any good reason to run portmap on a non NFS'd/RPC'd machine? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not using YP or any of that stuff. If not, then it seems like something that would be good to turn into a sysconfig variable. From owner-freebsd-hackers Thu Jan 2 14:57:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA10127 for hackers-outgoing; Thu, 2 Jan 1997 14:57:20 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA10122 for ; Thu, 2 Jan 1997 14:57:16 -0800 (PST) Message-Id: <199701022257.OAA10122@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA007195822; Fri, 3 Jan 1997 09:57:02 +1100 From: Darren Reed Subject: Re: file locking / firewalling based on uid/gid To: proff@iq.org (Julian Assange) Date: Fri, 3 Jan 1997 09:57:02 +1100 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199701021041.VAA11426@profane.iq.org> from "Julian Assange" at Jan 2, 97 09:41:37 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Julian Assange, sie said: [...] > # ipfw add pass tcp from any to any established gid inetd > # ipfw add padd tcp from any to any 21,79 setup in gid inetd I don't think that is a good way (or the right place) to do access control for TCP/IP. Firstly, on a gateway, not all TCP packets are likely to have a gid (or for there to be one which is "findable") and secondly, where the current hooks are, you will cause two tcpb lookups to occur for the same packet. I think it would be cool to be able to do: # mknod /dev/tcp/21 c major#_for_tcp 21 # chgrp inetd /dev/tcp/21 # mknod /dev/tcp/79 c major#_for_tcp 79 # chgrp inetd /dev/tcp/79 # mknod /dev/tcp/25 c major#_for_tcp 25 # chown uucp.mail /dev/tcp/25 # chmod 770 /dev/tcp/25 (who needs sendmail to run as root now ?!) and have open() calls on those devices create sockets. sockfs anyone ? Darren p.s. yes, netinet is nearly (not completely) in the splnet() cloud for BSD, which may have something to do with why Sun rewrote it for Solaris2. From owner-freebsd-hackers Thu Jan 2 15:22:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11368 for hackers-outgoing; Thu, 2 Jan 1997 15:22:32 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA11363 for ; Thu, 2 Jan 1997 15:22:30 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id PAA15331 for ; Thu, 2 Jan 1997 15:22:23 -0800 (PST) Date: Thu, 2 Jan 1997 15:22:23 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Funky antics to retrive lsof. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not sure it's good netizenship to go from the US to Germany to Australia to Japan to attempt to retrieve a file, when just jumping from the main archive to wcarchive seems much simpler, and nicer to the worlds loaded links. While I realize that wcarchive may be busy, there's no question that International links are probably the wrong way to go. # cd lsof ls # Makefile files patches pkg # make >> lsof_3.82_W.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/. File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.cert.dfn.de/pub/tools/admin/lsof/. fetch: ftp.cert.dfn.de: User name okay, need password >> Attempting to fetch from ftp://ftp.auscert.org.au/pub/mirrors/vic.cc.purdue.edu/lsof/. Can't open data connection >> Attempting to fetch from ftp://ftp.web.ad.jp/pub/UNIX/tools/lsof/. From owner-freebsd-hackers Thu Jan 2 15:35:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12049 for hackers-outgoing; Thu, 2 Jan 1997 15:35:58 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA12044 for ; Thu, 2 Jan 1997 15:35:35 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id KAA16149; Fri, 3 Jan 1997 10:34:34 +1100 (EST) From: Julian Assange Message-Id: <199701022334.KAA16149@profane.iq.org> Subject: Re: file locking / firewalling based on uid/gid In-Reply-To: <199701022258.JAA15669@profane.iq.org> from Darren Reed at "Jan 3, 97 09:57:02 am" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Fri, 3 Jan 1997 10:34:34 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In some mail from Julian Assange, sie said: > [...] > > # ipfw add pass tcp from any to any established gid inetd > > # ipfw add padd tcp from any to any 21,79 setup in gid inetd > > I don't think that is a good way (or the right place) to do access control > for TCP/IP. Firstly, on a gateway, not all TCP packets are likely to have > a gid (or for there to be one which is "findable") and secondly, where > the current hooks are, you will cause two tcpb lookups to occur for the > same packet. Bypassed these limitations by hooking input firewall checks into the individual proto_sw routines just after the tcbp hash lookups. Requires two scans of the firewall rule-set for inbound host packets, but this has almost no overhead, because the first scan doesn't do the checks of the second and vica-versa. The ipfw rule-set flows sequentially without jumps, permitting this optimisation to work. Output checks were unified by comparison, requiring only the passing of (the new) socket credential information into ip_output(), where it is passed onto the regular fw hook. > I think it would be cool to be able to do: > > # mknod /dev/tcp/21 c major#_for_tcp 21 > # chgrp inetd /dev/tcp/21 > # mknod /dev/tcp/79 c major#_for_tcp 79 > # chgrp inetd /dev/tcp/79 > # mknod /dev/tcp/25 c major#_for_tcp 25 > # chown uucp.mail /dev/tcp/25 > # chmod 770 /dev/tcp/25 > (who needs sendmail to run as root now ?!) > > and have open() calls on those devices create sockets. > > sockfs anyone ? I'm all for the everything-is-a-file and the file-system name space philosophy of Unix, which has unfortunately been badly corroded over the years. See VSTa or plan9 for how file system name spaced should be managed. That said, my ipfw-socket-credential implementation has a lot more power and flexibility than /dev/tcp/etc which really just solves the binding() issue and doesn't do anything to address covert channels. Cheers, Julian From owner-freebsd-hackers Thu Jan 2 15:46:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12693 for hackers-outgoing; Thu, 2 Jan 1997 15:46:46 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA12687 for ; Thu, 2 Jan 1997 15:46:44 -0800 (PST) Received: from super-g.inch.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vfwqO-0008vzC; Thu, 2 Jan 97 15:46 PST Received: from localhost (spork@localhost) by super-g.inch.com (8.8.4/8.6.9) with SMTP id SAA18363; Thu, 2 Jan 1997 18:47:08 -0500 (EST) Date: Thu, 2 Jan 1997 18:47:08 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Christoph Kukulies cc: freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken In-Reply-To: <199701021724.SAA15524@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We had a similar situation here with a Quantum 4G Grand Prix (blechhh). It had some *very* important data on it, and of course this was before the backup system was in place (the death of a drive is what seems to spawn implementation of backup strategies...). We checked locally for anyone that could fix it, and a shop in town swapped PCB's to no avail. But they did say it's easy as pie to do yourself and is a good way to narrow the problem down. A Grand Prix that died about a month later was saved by cannibalizing one of it's friends in this way. The other drive ended up going to DriveSavers for some ridiculous amount of money ($3000 +) and came back with 100% of the data intact. A nice tape drive is a bit cheaper. On a different note, one thing I've started doing as I build machines (and it's helped so far as I can see in the short-term; Quantum Grand Prix drives were dying after less than 3 months of service) is to mount one of those 12V, 4" fans under every drive I install. I've found that on the 7200 RPM drives this will bring the case temperature down by about 30 degrees (F). And if I'm wrong and kooky to do that, I'm only out $10/drive. I'll also usually throw a few more fans on the case while I'm at it too. I've got a whole big grocery bag of these things, and I think it's going to extend the drive life immeasurably. Now I just have to find a way to detect when the CPU fan dies... Charles On Thu, 2 Jan 1997, Christoph Kukulies wrote: > Coming back from a short holiday I powered on a P90 machine with > (among other IDE disks) a Quantum 2GB ATLAS XP32150 and the SCSI disks > saluted with a continous one second interval clicking noise. > It spins up but the head seems to do some wild moves followed by a > 'chuck-clack' with the NCR PCI BIOS not coming to an end of the probing > phase. At least the NCR BIOS sits there for half an hour already > and that noise is repeating unchanged. > > As always in such situations that disk contained some important data I > would like to preserve. Despite of this the disk is still under warranty. > So giving it back and waiting 8 weeks for replacement isn't the issue. > It's just the data I wish to recover. > > Does anyone have experience with drive electronics swapping? > I have a second disk of that model and I'm tempted to swap the > electronics PCB (after having bought the appropriate hex nut driver > tomorrow, is that the correct expression :-) > > I suspect that the electronics stores some bad block info in some kind > of nvram on the controller board but not sure about this. > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > From owner-freebsd-hackers Thu Jan 2 16:08:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA13908 for hackers-outgoing; Thu, 2 Jan 1997 16:08:06 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA13885 for ; Thu, 2 Jan 1997 16:08:04 -0800 (PST) Received: from crh.cl.msu.edu by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vfxB2-0008vRC; Thu, 2 Jan 97 16:08 PST Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id TAA19664 for freebsd-hackers@freebsd.org; Thu, 2 Jan 1997 19:03:32 -0500 (EST) From: Charles Henrich Message-Id: <199701030003.TAA19664@crh.cl.msu.edu> Subject: more than 32 disks? To: freebsd-hackers@freebsd.org Date: Thu, 2 Jan 1997 19:03:32 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Whenever attempting a ./MAKEDEV sd32+ it fails with bad unit for disk.. How does one add more disks than 32? And even if you cant, how can I address a disk as sd32 ? Help! Thanks! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Thu Jan 2 16:35:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17360 for hackers-outgoing; Thu, 2 Jan 1997 16:35:57 -0800 (PST) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA17333 for ; Thu, 2 Jan 1997 16:35:49 -0800 (PST) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id TAA25368; Thu, 2 Jan 1997 19:34:43 -0500 (EST) Message-Id: <199701030034.TAA25368@whizzo.transsys.com> X-Mailer: exmh version 2.0alpha 12/3/96 To: spork cc: Christoph Kukulies , freebsd-hackers@freefall.freebsd.org From: "Louis A. Mamakos" Subject: Re: advice sought - Quantum 2GB Atlas broken References: In-reply-to: Your message of "Thu, 02 Jan 1997 18:47:08 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Jan 1997 19:34:41 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > . Now I just have to find > a way to detect when the CPU fan dies... If you run xntp on your box and your clock is synchronized over the net to a reference clock, you could monitor the contents of the /etc/ntp.drift file. This contains the computed drift rate for the system's clock, which is derived from a crystal oscillator which the interval timer is clocked from. The frequency of the quartz crystal varies with temperature; this cause the drift rate (which is essentially the frequencey error) to vary. If it changes by a lot, then some significant thermal event has occured. (This is why your cheapo plastic wristwatch keeps good time - it's got it's own crystal oven attached to it, keeping it heated to a relatively constant temperature). I once calibrated the computed drift values with temperature for a workstation in my office - you could tell the temperature of the room within about 4 or 5 degrees by logging into the system and looking at the computed drift rate. Of course, this isn't a great bit of help for the CPU fan. Perhaps you could do a bunch of divide operations and check to see if you got the right answer :-) There's a company I saw on the net with an RS-232 attached temperature sensor. You could actually attach up to 16 Dallas Semiconductor DS1802 temperature sensors to it, and query their temp via the RS232 interface. Something like this might make sense, if you could figure out how to attach to temperature probe (which I think is in a TO-18 "can" package) to the heat sink on the CPU. Check http://www.spiderplant.com for details. louie (By the way, Happy (no leap-second this time) New Year!) From owner-freebsd-hackers Thu Jan 2 17:19:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19626 for hackers-outgoing; Thu, 2 Jan 1997 17:19:03 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA19612 for ; Thu, 2 Jan 1997 17:19:00 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA18076; Fri, 3 Jan 1997 11:48:27 +1030 (CST) From: Michael Smith Message-Id: <199701030118.LAA18076@genesis.atrad.adelaide.edu.au> Subject: CPU fan detection... In-Reply-To: from spork at "Jan 2, 97 06:47:08 pm" To: spork@super-g.com (spork) Date: Fri, 3 Jan 1997 11:48:26 +1030 (CST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just to change the subject slightly... spork stands accused of saying: > it's going to extend the drive life immeasurably. Now I just have to find > a way to detect when the CPU fan dies... The Intel CPUs with integrated fans do indeed have a fan sensor of some sort. Anyone know how to read it? It'd make for a good idle-loop check... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jan 2 17:52:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA21222 for hackers-outgoing; Thu, 2 Jan 1997 17:52:35 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA21217 for ; Thu, 2 Jan 1997 17:52:33 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id SAA06535; Thu, 2 Jan 1997 18:52:24 -0700 (MST) From: Ade Barkah Message-Id: <199701030152.SAA06535@hemi.com> Subject: Re: Funky antics to retrive lsof. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 2 Jan 1997 18:52:24 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from Jaye Mathisen at "Jan 2, 97 03:22:23 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm not sure it's good netizenship to go from the US to Germany to > Australia to Japan to attempt to retrieve a file, when just jumping from > the main archive to wcarchive seems much simpler, and nicer to the worlds > loaded links. Wcarchive (as far as I know) does not officially mirror lsof. For "security" tools like lsof, it's best to stick to official mirror sites. > >> lsof_3.82_W.tar.gz doesn't seem to exist on this system. ^^^^ The above needs to be fixed. Lsof 3.82 has been replaced by 3.83. Jaye, just get it directly. Lsof has native support for FreeBSD 1.x, 2.x, and even 3.x (new in 3.83) =-) Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Thu Jan 2 18:07:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA21842 for hackers-outgoing; Thu, 2 Jan 1997 18:07:42 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA21834 for ; Thu, 2 Jan 1997 18:07:39 -0800 (PST) Received: from moth.us.dell.com (moth.us.dell.com [143.166.169.152]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id UAA03356; Thu, 2 Jan 1997 20:06:31 -0600 Message-Id: <3.0.1.32.19970102200622.00699f64@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: Windows Eudora Light Version 3.0.1 beta 4 (32) Date: Thu, 02 Jan 1997 20:06:31 -0600 To: Michael Smith From: Tony Overfield Subject: Re: CPU fan detection... Cc: freebsd-hackers@freefall.freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:48 AM 1/3/97 +1030, Michael Smith wrote: >Just to change the subject slightly... > >The Intel CPUs with integrated fans do indeed have a fan sensor of some >sort. Anyone know how to read it? It'd make for a good idle-loop >check... The Intel 486->Pentium Overdrive CPU, with the integrated fan, will disable the internal clock multiplier when the fan stops. You could check to see if your 100 MHz CPU suddenly seems to be running at only 33 MHz. From owner-freebsd-hackers Thu Jan 2 18:13:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA22176 for hackers-outgoing; Thu, 2 Jan 1997 18:13:18 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA22170 for ; Thu, 2 Jan 1997 18:13:14 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA18262; Fri, 3 Jan 1997 12:42:36 +1030 (CST) From: Michael Smith Message-Id: <199701030212.MAA18262@genesis.atrad.adelaide.edu.au> Subject: Re: CPU fan detection... In-Reply-To: <3.0.1.32.19970102200622.00699f64@bugs.us.dell.com> from Tony Overfield at "Jan 2, 97 08:06:31 pm" To: tony@dell.com (Tony Overfield) Date: Fri, 3 Jan 1997 12:42:35 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Overfield stands accused of saying: > At 11:48 AM 1/3/97 +1030, Michael Smith wrote: > >Just to change the subject slightly... > > > >The Intel CPUs with integrated fans do indeed have a fan sensor of some > >sort. Anyone know how to read it? It'd make for a good idle-loop > >check... > > The Intel 486->Pentium Overdrive CPU, with the integrated fan, will disable > the internal clock multiplier when the fan stops. You could check to see > if your 100 MHz CPU suddenly seems to be running at only 33 MHz. I have one of these, which comes with a utility to monitor the fan. You're suggesting that this just checks the CPU speed? Ick, forget I mentioned it. I thought that the other integrated-fan CPUs had more than two contacts on the fan connector & thus probably had a status bit somewhere for the fan... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jan 2 19:05:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24626 for hackers-outgoing; Thu, 2 Jan 1997 19:05:57 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA24621 for ; Thu, 2 Jan 1997 19:05:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA18683; Thu, 2 Jan 1997 19:05:26 -0800 (PST) Message-Id: <199701030305.TAA18683@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: robin@intercore.com (Robin Cutshaw) cc: hackers@freebsd.org Subject: Re: tcp problems with 2.1.6.1 In-reply-to: Your message of "Thu, 02 Jan 1997 14:52:09 EST." <199701021952.OAA08144@intercore.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Jan 1997 19:05:26 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Recently while supping the XFree86 tree, I noticed that one of my boxes >was having timeout problems. It's a P90/64MB/FreeBSD-2.1.6.1 box. I >watched the ethernet and noticed a large number of packets received >that got no ack from the FreeBSD box. This caused a large number >of retransmits. The other boxes on this net don't seem to have >this problem so I thought I'd ask the FreeBSD group if anyone has >seen anything like this. You need to mention what type of ethernet card you're using. The bug isn't likely with the TCP code, but rather a device driver or hardware problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jan 2 19:11:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24825 for hackers-outgoing; Thu, 2 Jan 1997 19:11:21 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA24819 for ; Thu, 2 Jan 1997 19:11:16 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id VAA20862; Thu, 2 Jan 1997 21:08:51 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma020860; Thu Jan 2 21:08:35 1997 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id VAA28976; Thu, 2 Jan 1997 21:09:13 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.4/8.6.12) with ESMTP id VAA10339; Thu, 2 Jan 1997 21:09:37 -0600 (CST) Message-Id: <199701030309.VAA10339@jake.lodgenet.com> To: Michael Smith cc: spork@super-g.com (spork), kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Subject: Re: CPU fan detection... In-reply-to: Your message of "Fri, 03 Jan 1997 11:48:26 +1030." <199701030118.LAA18076@genesis.atrad.adelaide.edu.au> Date: Thu, 02 Jan 1997 21:09:36 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: >The Intel CPUs with integrated fans do indeed have a fan sensor of some >sort. Anyone know how to read it? It'd make for a good idle-loop >check... My new home machine came with a `musical fan' that plugs between the pc speaker and the motherboard. If I hold my thumb on the fan, it plays a tune ;-) So here's the test: Connect a microphone between the speaker and the SoundBastard; if pcaudio isn't active and there's data coming into the SoundBastard, the fan ain't working, so halt. ;-) > >-- >]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ >]] Genesis Software genesis@gsoft.com.au [[ >]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ >]] realtime instrument control. (ph) +61-8-8267-3493 [[ >]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > eric. From owner-freebsd-hackers Thu Jan 2 19:28:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA25643 for hackers-outgoing; Thu, 2 Jan 1997 19:28:16 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA25638 for ; Thu, 2 Jan 1997 19:28:14 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vg0Ii-0004fw-00; Thu, 2 Jan 1997 20:28:08 -0700 To: Jaye Mathisen Subject: Re: Any good reason to run portmap on a non NFS'd/RPC'd machine? Cc: hackers@freebsd.org In-reply-to: Your message of "Thu, 02 Jan 1997 14:55:01 PST." References: Date: Thu, 02 Jan 1997 20:28:08 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Jaye Mathisen writes: : I'm not using YP or any of that stuff. If not, then it seems like : something that would be good to turn into a sysconfig variable. There is no good reason to run portmapper unless you are using RPC based services. I don't run it on rover except when I have to do NFS things.... Warner From owner-freebsd-hackers Thu Jan 2 19:30:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA25736 for hackers-outgoing; Thu, 2 Jan 1997 19:30:18 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA25728 for ; Thu, 2 Jan 1997 19:30:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA18783; Thu, 2 Jan 1997 19:29:46 -0800 (PST) Message-Id: <199701030329.TAA18783@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: more than 32 disks? In-reply-to: Your message of "Thu, 02 Jan 1997 19:03:32 EST." <199701030003.TAA19664@crh.cl.msu.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Jan 1997 19:29:46 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Whenever attempting a ./MAKEDEV sd32+ it fails with bad unit for disk.. > >How does one add more disks than 32? And even if you cant, how can I address a >disk as sd32 ? Help! Thanks! Oh yeah, I forgot to reply to your message to me about this. The answer for wcarchive is that we only have 3 controllers - 0-2, so I haven't been faced with an sd3 problem yet. :-) It looks like there are only 5 bits for the unit number. This means that one will have to make driver changes to go beyond 32 units. :-( -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jan 2 19:39:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA26160 for hackers-outgoing; Thu, 2 Jan 1997 19:39:06 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA26155 for ; Thu, 2 Jan 1997 19:39:04 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id TAA16367; Thu, 2 Jan 1997 19:31:39 -0800 (PST) To: spork cc: Christoph Kukulies , freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken In-reply-to: Your message of "Thu, 02 Jan 1997 18:47:08 EST." Date: Thu, 02 Jan 1997 19:31:38 -0800 Message-ID: <16362.852262298@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On a different note, one thing I've started doing as I build machines (and > it's helped so far as I can see in the short-term; Quantum Grand Prix > drives were dying after less than 3 months of service) is to mount one of Grand Prix drives tend to die on a variety of general principles, but heat stroke is definitely one of them. Good idea on the fans - if your case design will accomodate them, they're a worthwhile investment for pretty much *any* high capacity drive, though I might also note that the newer Quantum Atlas II drives appear to run considerably cooler than their predecessors. I just got one of these drives, and I can say that I really really like it. Jordan From owner-freebsd-hackers Thu Jan 2 19:57:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA26770 for hackers-outgoing; Thu, 2 Jan 1997 19:57:48 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA26765 for ; Thu, 2 Jan 1997 19:57:45 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vg0ld-0002gJ-00; Thu, 2 Jan 1997 19:58:01 -0800 Date: Thu, 2 Jan 1997 19:58:01 -0800 (PST) From: Tom Samplonius To: "Jordan K. Hubbard" cc: freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken In-Reply-To: <16362.852262298@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Jordan K. Hubbard wrote: > > On a different note, one thing I've started doing as I build machines (and > > it's helped so far as I can see in the short-term; Quantum Grand Prix > > drives were dying after less than 3 months of service) is to mount one of > > Grand Prix drives tend to die on a variety of general principles, but > heat stroke is definitely one of them. Good idea on the fans - if > your case design will accomodate them, they're a worthwhile investment > for pretty much *any* high capacity drive, though I might also note > that the newer Quantum Atlas II drives appear to run considerably > cooler than their predecessors. I just got one of these drives, and I > can say that I really really like it. > > Jordan Any thoughts on the Barracuda 4lp series? Tom From owner-freebsd-hackers Thu Jan 2 20:30:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27834 for hackers-outgoing; Thu, 2 Jan 1997 20:30:13 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27829 for ; Thu, 2 Jan 1997 20:30:11 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id XAA20956; Thu, 2 Jan 1997 23:30:08 -0500 (EST) From: Charles Henrich Message-Id: <199701030430.XAA20956@crh.cl.msu.edu> Subject: Re: more than 32 disks? To: dg@root.com Date: Thu, 2 Jan 1997 23:30:08 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701030329.TAA18783@root.com> from David Greenman at "Jan 2, 97 07:29:46 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Oh yeah, I forgot to reply to your message to me about this. The answer for > wcarchive is that we only have 3 controllers - 0-2, so I haven't been faced > with an sd3 problem yet. :-) It looks like there are only 5 bits for the > unit number. This means that one will have to make driver changes to go > beyond 32 units. :-( Hmm. The system boot appears to assign the sd32 device just peachy, just MAKEDEV dying. I wonder what the adaptec driver is doing, guess its time to scrounge around in code. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Thu Jan 2 20:39:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28145 for hackers-outgoing; Thu, 2 Jan 1997 20:39:37 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA28139 for ; Thu, 2 Jan 1997 20:39:34 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id XAA21021; Thu, 2 Jan 1997 23:39:32 -0500 (EST) From: Charles Henrich Message-Id: <199701030439.XAA21021@crh.cl.msu.edu> Subject: Re: more than 32 disks? To: dg@root.com Date: Thu, 2 Jan 1997 23:39:32 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701030329.TAA18783@root.com> from David Greenman at "Jan 2, 97 07:29:46 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > with an sd3 problem yet. :-) It looks like there are only 5 bits for the > unit number. This means that one will have to make driver changes to go > beyond 32 units. :-( *sigh* I absolutely hate fixed fields :( *grumble*. So whats the generic solution besides encoding data into the minor number? Encode a table offset into the minor number and make the table dynamic? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Thu Jan 2 20:43:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28364 for hackers-outgoing; Thu, 2 Jan 1997 20:43:41 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28355; Thu, 2 Jan 1997 20:43:20 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701030443.UAA28355@freefall.freebsd.org> Subject: Re: file locking / firewalling based on uid/gid To: avalon@coombs.anu.edu.au (Darren Reed) Date: Thu, 2 Jan 1997 20:43:19 -0800 (PST) Cc: proff@iq.org, hackers@FreeBSD.ORG In-Reply-To: <199701022257.OAA10122@freefall.freebsd.org> from "Darren Reed" at Jan 3, 97 09:57:02 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed wrote: > > In some mail from Julian Assange, sie said: > [...] > > # ipfw add pass tcp from any to any established gid inetd > > # ipfw add padd tcp from any to any 21,79 setup in gid inetd > > I don't think that is a good way (or the right place) to do access control > for TCP/IP. Firstly, on a gateway, not all TCP packets are likely to have > a gid (or for there to be one which is "findable") and secondly, where > the current hooks are, you will cause two tcpb lookups to occur for the > same packet. > > I think it would be cool to be able to do: > > # mknod /dev/tcp/21 c major#_for_tcp 21 > # chgrp inetd /dev/tcp/21 > # mknod /dev/tcp/79 c major#_for_tcp 79 > # chgrp inetd /dev/tcp/79 > # mknod /dev/tcp/25 c major#_for_tcp 25 > # chown uucp.mail /dev/tcp/25 > # chmod 770 /dev/tcp/25 > (who needs sendmail to run as root now ?!) > > and have open() calls on those devices create sockets. > > sockfs anyone ? stevens and pendry called this "portals" 4.4BSD book pages 237,8 usenix proceedings jan '95 p1-10 http://www.usenix.org/publications/library/proceedings/neworl/full_papers/stevens.ps apply standard access control to the portals. sendmail is uid/gid "sendmail" chown sendmail.sendmail /p/net/tcp/localhost/25 chmod 600 /p/net/tcp/localhost/25 jmb From owner-freebsd-hackers Thu Jan 2 21:27:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA29800 for hackers-outgoing; Thu, 2 Jan 1997 21:27:05 -0800 (PST) Received: from calvino.alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA29795 for ; Thu, 2 Jan 1997 21:27:03 -0800 (PST) Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id UAA04229 for ; Thu, 2 Jan 1997 20:26:26 -0900 (AKST) Date: Thu, 2 Jan 1997 20:26:26 -0900 (AKST) From: hmmm Reply-To: hmmm To: freebsd-hackers Subject: Re: Ints In-Reply-To: <199701021134.WAA16141@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Michael Smith wrote: > Please don't go inventing your own terminology in order to prove > yourself "right". If you are responding to an interrupt, you are not > "polling" as such. hehe! i'm not! interrupts - in a pure form - implies random activity. if i'm using interrupts under polled conditions - the interrupts are timed - not random - how else can i distinguish ??? that was the whole point of my question ... > > MAY change - or DOES change ? is it usually a circuit outside of CPU > > concerns? do INT status flags change EXACTLY as the condition is removed? > > "may" change. If you really want the low-down on how much UART > implementations vary, search the FreeBSD mailing list archives for > mention of a program called COMTEST in a message from Frank Durda. > Basically, there is very little that you can actually count on. thanks - i'll check it out .. :) > inactive to active. It is the processor's responsibility to > manipulate the peripheral so that the input goes inactive again. If > it fails to do so, there will be no more interrupts from it. Finito. hehe! well - if things are so screwed up - you shouldn't be too angry with me for being at a loss for the facts. i couldn't find the "details" in data sheets. i thought things were more sane. i sure appreciate all the time you took to assist me! From owner-freebsd-hackers Thu Jan 2 23:58:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA06032 for hackers-outgoing; Thu, 2 Jan 1997 23:58:18 -0800 (PST) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA06027 for ; Thu, 2 Jan 1997 23:58:06 -0800 (PST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.12/8.6.9) id IAA28651; Fri, 3 Jan 1997 08:57:15 +0100 From: Thomas Gellekum Message-Id: <199701030757.IAA28651@ghpc6.ihf.rwth-aachen.de> Subject: Re: advice sought - Quantum 2GB Atlas broken To: spork@super-g.com (spork) Date: Fri, 3 Jan 1997 08:57:14 +0100 (MET) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@freefall.freebsd.org In-Reply-To: from spork at "Jan 2, 97 06:47:08 pm" Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk spork wrote: > Now I just have to find > a way to detect when the CPU fan dies... We use a current detector in the power supply wires for the fan. If the current increases the fan is stuck -> annoying beep and possibly toggle turbo switch. tg From owner-freebsd-hackers Fri Jan 3 00:09:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06427 for hackers-outgoing; Fri, 3 Jan 1997 00:09:01 -0800 (PST) Received: from deepcore.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06419 for ; Fri, 3 Jan 1997 00:08:56 -0800 (PST) Received: (from sos@localhost) by deepcore.cybercity.dk (8.8.4/8.7.3) id JAA21106; Fri, 3 Jan 1997 09:06:14 +0100 (MET) Message-Id: <199701030806.JAA21106@deepcore.cybercity.dk> Subject: Re: CPU fan detection... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 3 Jan 1997 09:05:58 +0100 (MET) Cc: spork@super-g.com, kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org In-Reply-To: <199701030118.LAA18076@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jan 3, 97 11:48:26 am" From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Michael Smith who wrote: > Just to change the subject slightly... > > spork stands accused of saying: > > it's going to extend the drive life immeasurably. Now I just have to find > > a way to detect when the CPU fan dies... > > The Intel CPUs with integrated fans do indeed have a fan sensor of some > sort. Anyone know how to read it? It'd make for a good idle-loop > check... Hmm, I have one of those P5 ODP for a 486 socket, and it has a built in fan. I'm pretty sure I've read somewhere that the status can be gotten from one of the MSR's. It's lousy peace of shit though, it is much better to go with one of the 100-133 Mhz AMD 486's, and it will only run for an hour then it dies, but the fan runs :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Fri Jan 3 01:34:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA10125 for hackers-outgoing; Fri, 3 Jan 1997 01:34:59 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA10120 for ; Fri, 3 Jan 1997 01:34:57 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id BAA11894 for ; Fri, 3 Jan 1997 01:34:55 -0800 (PST) Date: Fri, 3 Jan 1997 01:34:55 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Stupid ipfw question. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why doesn't the following 2 rules allow any type of outbound TCP connection? /sbin/ipfw add pass tcp from ${ip} to any setup /sbin/ipfw add pass tcp from any to any established Basically my FTP's are failing, but work fine in passive mode. I must be missing something obvious with the PORT commands, most likely it being that the port command is from the remote host to my host, but since I don't know what port it will be, I have to leave a bunch of them open, which seems to be a problematic issue for firewalling. However, I'm using squid, and it doesn't seem to support PASV ftp retrievals, so I'm not sure what the safest thing to do is. ftpget (part of squid) does support a "range" notation for data, but I don't think there's a range argument to ipfw. Nor have I seen a range argument that can be passed to the remote FTP server. So what's the right thing to do here? Accept TCP connections above 1023? Seems fraught with peril... From owner-freebsd-hackers Fri Jan 3 02:23:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA11949 for hackers-outgoing; Fri, 3 Jan 1997 02:23:19 -0800 (PST) Received: from hda.hda.com (ip81-max1-fitch.ziplink.net [199.232.245.81]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA11944 for ; Fri, 3 Jan 1997 02:23:13 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id FAA24116; Fri, 3 Jan 1997 05:19:12 -0500 From: Peter Dufault Message-Id: <199701031019.FAA24116@hda.hda.com> Subject: Re: more than 32 disks? In-Reply-To: <199701030430.XAA20956@crh.cl.msu.edu> from Charles Henrich at "Jan 2, 97 11:30:08 pm" To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Fri, 3 Jan 1997 05:19:11 -0500 (EST) Cc: dg@root.com, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Oh yeah, I forgot to reply to your message to me about this. The answer for > > wcarchive is that we only have 3 controllers - 0-2, so I haven't been faced > > with an sd3 problem yet. :-) It looks like there are only 5 bits for the > > unit number. This means that one will have to make driver changes to go > > beyond 32 units. :-( > > Hmm. The system boot appears to assign the sd32 device just peachy, just > MAKEDEV dying. I wonder what the adaptec driver is doing, guess its time to > scrounge around in code. The scsiconf code is incrementing the unit number without checking if it exceeded the space allocated in the minor number. I think the driver would be functional if you could get into it. The unit number is encoded using "dkunit" so the change has to be made there. See the alert about adding "dkmodunit". May as well fix DK_NDRIVE at the same time. Look in sys/scsi/sd.c for the disk minor number setup. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Fri Jan 3 02:26:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA12057 for hackers-outgoing; Fri, 3 Jan 1997 02:26:15 -0800 (PST) Received: from amadeus.informatik.ba-stuttgart.de (amadeus.informatik.ba-stuttgart.de [141.31.11.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA12051 for ; Fri, 3 Jan 1997 02:26:05 -0800 (PST) Received: (from helbig@localhost) by amadeus.informatik.ba-stuttgart.de (8.7.3/8.7.1) id LAA03019; Fri, 3 Jan 1997 11:24:56 +0100 (MET) From: Wolfgang Helbig Message-Id: <199701031024.LAA03019@amadeus.informatik.ba-stuttgart.de> Subject: Re: split function missing? To: ping@stepnet.com (Ping Mai) Date: Fri, 03 Jan 1997 11:24:56 MET Cc: hackers@freebsd.org In-Reply-To: <199701022226.OAA06911@tibet.stepnet.com>; from "Ping Mai" at Jan 2, 97 2:26 pm X-Mailer: Elm [revision: 112.2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Has the split function been taken out of nvi? > Yes, use capital letters in ex-commands and you'll get the split! Use ":E" instead of ":e" etc.. > ping Wolfgang Helbig From owner-freebsd-hackers Fri Jan 3 02:52:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA12760 for hackers-outgoing; Fri, 3 Jan 1997 02:52:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA12700 for ; Fri, 3 Jan 1997 02:51:47 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA27039 for ; Fri, 3 Jan 1997 11:51:29 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA04586 for freebsd-hackers@freebsd.org; Fri, 3 Jan 1997 11:51:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA14174; Fri, 3 Jan 1997 11:23:00 +0100 (MET) Message-ID: Date: Fri, 3 Jan 1997 11:23:00 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: more than 32 disks? References: <199701030329.TAA18783@root.com> <199701030430.XAA20956@crh.cl.msu.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701030430.XAA20956@crh.cl.msu.edu>; from Charles Henrich on Jan 2, 1997 23:30:08 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > Hmm. The system boot appears to assign the sd32 device just peachy, just > MAKEDEV dying. The kernel assigns sd32, but you can't access it through any device node. MAKEDEV is only enforcing what the drivers are doing anyway. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 3 02:52:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA12800 for hackers-outgoing; Fri, 3 Jan 1997 02:52:39 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA12790 for ; Fri, 3 Jan 1997 02:52:36 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA27071; Fri, 3 Jan 1997 11:51:36 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA04598; Fri, 3 Jan 1997 11:51:31 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA14022; Fri, 3 Jan 1997 10:39:30 +0100 (MET) Message-ID: Date: Fri, 3 Jan 1997 10:39:30 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freefall.freebsd.org ('hackers@freefall.freebsd.org') Cc: mango@staff.communique.net (Raul Zighelboim) Subject: Re: Panic - Maloc: lost data....... (auch) References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Raul Zighelboim on Jan 2, 1997 16:14:55 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Raul Zighelboim wrote: > Two questions: can I set the server (2.1.6R) to automatically restart > if it crashes ? It's normally supposed to do this. > Is there a utility I can run in order to have an idea of what caused the > problem > (or do I have to recompile with kernel debug on?) You gotta enable core dumps, and savecore. (It's silly that there are two variables for this.) > And then, how do I interpret the results of the core dump ? With the kernel debugger. Have a look into the section about kernel debugging in the handbook. However, judging from your chosen subject, i'm afraid this is rather a hardware problem. That is, the crash will happen at various and unpredictable spots, so the kernel debugger or coredump aren't of much use for it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 3 02:54:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA12906 for hackers-outgoing; Fri, 3 Jan 1997 02:54:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA12895 for ; Fri, 3 Jan 1997 02:54:08 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA27031; Fri, 3 Jan 1997 11:51:27 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA04581; Fri, 3 Jan 1997 11:51:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA13966; Fri, 3 Jan 1997 10:09:52 +0100 (MET) Message-ID: Date: Fri, 3 Jan 1997 10:09:52 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: mark@putte.seeware.DIALix.oz.au (Mark Hannon) Subject: Re: ft < 50kb/s ?? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Mark Hannon on Jan 2, 1997 20:28:59 +0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mark Hannon wrote: > ..., however in > the current configuration it is dead slow - It just took me 12 hours > to back up 200m of data, according to the manufacturers notes it You mean, it got slower over time? Even with a new (and freshly formatted) medium? This would be fairly surprising, since the driver hasn't changed except of a few side-effects from global changes. It's basically orphaned (though maybe, i've found a new maintainer). > should be able to do 1Mbit/second, which is around 30minutes. The 1 Mbit/s is, of course, a marketing gag. Since you're operating on a standard floppy controller, it will only do 500 kbit/s, since that's the highest clock rate of a normal (i.e., not 2.88 MB capable) floppy controller. And, you have to subtract the overhead of floppy sectorization and ECC error correction. The floppy sectorization overhead can be as high as (2 MB - 1.44 MB) / 2 MB. All of this, of course, holds only valid as long as the driver keeps the tape streaming. Our floppy disk driver can maintain a streaming data rate (for sequential transfers) of ~ 30 KB/s. Given the design of the `ft' driver, i would be fairly surprised if it maxes out at a much higher rate at all. Of course, the most important question for you is: does the tape remain streaming? If not, all bets are off, and performance will simply suck. We might then try profiling the driver or the [l]ft utility. However, if it keeps streaming, there's not very much we could do. Support for 1 MBit/s floppy controllers might double the rate, i have this on my whiteboard for a long time (for floppy disks, but i figure that it might be easy to have the floppy tape driver also benefit from this). However, somebody mysteriously always puts a new sheet with other ``more important'' tasks over that sheet on the whiteboard... :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 3 03:21:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA13866 for hackers-outgoing; Fri, 3 Jan 1997 03:21:42 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA13861 for ; Fri, 3 Jan 1997 03:21:34 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA29903 for ; Fri, 3 Jan 1997 12:21:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA07580 for freebsd-hackers@freefall.freebsd.org; Fri, 3 Jan 1997 12:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id MAA14449; Fri, 3 Jan 1997 12:12:20 +0100 (MET) Message-ID: Date: Fri, 3 Jan 1997 12:12:20 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken References: <199701030757.IAA28651@ghpc6.ihf.rwth-aachen.de> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701030757.IAA28651@ghpc6.ihf.rwth-aachen.de>; from Thomas Gellekum on Jan 3, 1997 08:57:14 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Thomas Gellekum wrote: > > Now I just have to find > > a way to detect when the CPU fan dies... > > We use a current detector in the power supply wires for the fan. If > the current increases the fan is stuck -> annoying beep and possibly > toggle turbo switch. Btw., we've got a fairly old IBM 5.25 inch SCSI device case around (i think it used to house a tape drive, or a CD-ROM drive). The fan of its power supply is very small and very noisy... I recently wanted to use that case, but figured that the ventilation wasn't adequate for me. I tried to pull the plug of the fan -- the power suplly stopped. Ok. They're watching the current flow, no problem! Clamp the fan using a match. The power supply stopped. Hrmpf. I think they're using a small NTC resistor to watch the airflow... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 3 03:28:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA14280 for hackers-outgoing; Fri, 3 Jan 1997 03:28:28 -0800 (PST) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA14275 for ; Fri, 3 Jan 1997 03:28:25 -0800 (PST) Received: from zen.nash.org (localhost [127.0.0.1]) by zen.nash.org (8.8.3/8.6.12) with SMTP id FAA27332; Fri, 3 Jan 1997 05:28:21 -0600 (CST) Message-ID: <32CCED54.446B9B3D@mcs.com> Date: Fri, 03 Jan 1997 05:28:20 -0600 From: Alex Nash X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6.1-RELEASE i386) MIME-Version: 1.0 To: Jaye Mathisen CC: hackers@FreeBSD.org Subject: Re: Stupid ipfw question. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > Why doesn't the following 2 rules allow any type of outbound TCP > connection? > > /sbin/ipfw add pass tcp from ${ip} to any setup > /sbin/ipfw add pass tcp from any to any established They do. [On a stylistic note, I would probably swap the order of established and setup for better performance.] > Basically my FTP's are failing, but work fine in passive mode. FTP active mode requires the server to be able to establish a connection to the client. I believe Nate ran into this same problem about 5-6 months ago. What did you end up doing, Nate? Alex From owner-freebsd-hackers Fri Jan 3 04:16:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA16200 for hackers-outgoing; Fri, 3 Jan 1997 04:16:16 -0800 (PST) Received: from penn.com (root@[205.146.6.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA16152; Fri, 3 Jan 1997 04:16:00 -0800 (PST) Received: from none.Compuserve.com (lport22.penn.com [208.0.122.71]) by penn.com (8.7.3/8.6.12) with SMTP id HAA28642; Fri, 3 Jan 1997 07:15:00 -0500 (EST) Date: Fri, 3 Jan 1997 07:15:00 -0500 (EST) Message-Id: <199701031215.HAA28642@penn.com> X-Sender: jnuytten@pop.penn.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@@freebsd.org From: Jean-Paul Nuytten Subject: Unsubscribe Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-questions jnuytten@penn.com unsubscribe freebsd-hardware jnuytten@penn.com Jean-Paul Nuytten Email: jnuytten@penn.com RD #3, Box 359A Tel: 814-641-0198 Huntingdon, PA USA 16652 FAX: 814-641-0199 From owner-freebsd-hackers Fri Jan 3 04:52:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA19143 for hackers-outgoing; Fri, 3 Jan 1997 04:52:58 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA19138 for ; Fri, 3 Jan 1997 04:52:53 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id NAA22595 for hackers@freebsd.org; Fri, 3 Jan 1997 13:51:33 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id NAA05012 for ; Fri, 3 Jan 1997 13:52:44 +0100 (MET) Message-Id: <3.0.32.19970103135444.009c5a70@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 03 Jan 1997 13:54:46 +0100 To: hackers@freebsd.org From: Eivind Eklund Subject: 2.2-BETA install fraught with peril? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following experiences was on a Dell 90Mhz Pentium with 24 MB RAM, 3C509, #9 SVGA card, 2x Quantum IDE drives slaved to each other with the IDE adapter at the motherboard, and an Adaptec 1542CF (BIOS version 2.11) with a Micropolis 1.7GB drive, which I tried to install to. No IRQ or IO area conflicts. The box run Linux (Red Hat 4.0 + upgrades) and Win 3.11 normally, and is quite stable. The install was done with active FTP through a proxy FTP server on a firewall. I encountered the following problems (some my own fault, some either bugs or hardware problems): (1) FreeBSD adjusted the disk geometry (probably due to some stupid "translation" in the BIOS or similar), so I couldn't boot when I was finished installing. I've been bitten by this before, and should be more careful, but I think it would be an idea with a warning. (Ie: Unreasonable disk geometry found - guessing a better geometry - YOU WILL NOW NOT BE ABLE TO BOOT FROM THIS DRIVE) (2) fixit.flp didn't work - I got "disk full" and segmentation fault all the time (until I changed root to my HD, whereupon I ended up with just segmentation faults :) This could be a bad disk in my end; the user I tried to install for is notorious for having lousy floppies. (3) The 3C509 was detected and not detected every second reboot. This card has always worked under Win3.11 and Linux; however, that 1542CF was new to this install. Win3.11 and Linux didn't seem to have any problems with it present (I booted them a couple of times each), but this _might_ be luck. This problem was also present on the 2.1.6 kernel (which I ended up using). (4) For 2.2-BETA, sysinstall died with signal 10 and 11 (sometimes one, sometimes the other), usually after attempting and failing to extract from a media. (5) When attempting to run passive FTP, the system couldn't cope, and I was thrown back to the site-selector - WITH NO ERROR OR WARNING MESSAGE. For a user who had never done this before, it could look as if the install was finished. (And without debug mode, VTY2 gave me little information, too - I found out what was wrong only after enabling debugging information. Otherwise, I got no error messages at all when FTP failed) (6) The documentation of proxy-FTP in the FreeBSD-handbook was quite skimpy, and somewhat misleading. I had to guess for myself that I would have to put ftp@ftp.site.to.fetch.from as username for proxy-FTP to work, and _then_ push the firewall's address into the URL. Better documentation or a separate setup for proxy-FTP might be a good idea. (I know there are more kinds of proxy-FTP servers, but with the extra .3MB it should probably be possible to cater to them all, like WS-FTP does.) (7) For a period, I had a problem with the network card, where I would give all information for configuring it, the card would be configured, default route would be added (if I had a gateway set up), and the installer would hang. The system was still up - I could switch VTYs and it responded to Ctrl-C - but I got no further in the install. The problem went away when I moved the 1542CF BIOS from C8000H to DC000H and dropped into the BIOS of the 1542 at the same time and looked the values over (no changes done). I did both at the same time (stupid me), so I don't know what caused the fix, but assume it was the BIOS (though the drive BIOS had worked before this, too, and believe the network had worked in Win3.11 after I added the drive - but don't quote me on that). (8) When fetching more things by URL, the URL is cleared to ftp:// each time. This also happen when you've already given the box a value. I think that was it. I got it to install (using 2.1.6-floppies instead of 2.2-BETA due to the bus errors/segment violations), and assume I will get it up and running later today (I'll just have to fix the partitioning and copy the data back), so I haven't and problems asa a such, but it would be nice for everybody else to get this fixed (as I now know the quirks, and won't have more trouble :) Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-hackers Fri Jan 3 05:09:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA19642 for hackers-outgoing; Fri, 3 Jan 1997 05:09:50 -0800 (PST) Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA19636 for ; Fri, 3 Jan 1997 05:09:47 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m0vg9NX-0021WTC; Fri, 3 Jan 97 08:09 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA07824; Fri, 3 Jan 1997 07:02:49 -0600 Date: Fri, 3 Jan 1997 07:02:49 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199701031302.HAA07824@bonkers.taronga.com> To: hackers@freebsd.org Subject: Re: more than 32 disks? Newsgroups: taronga.freebsd.hackers In-Reply-To: <199701030439.XAA21021@crh.cl.msu.edu> References: <199701030329.TAA18783@root.com> Organization: none Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> with an sd3 problem yet. :-) It looks like there are only 5 bits for the >> unit number. This means that one will have to make driver changes to go >> beyond 32 units. :-( >*sigh* I absolutely hate fixed fields :( *grumble*. So whats the generic >solution besides encoding data into the minor number? Encode a table offset >into the minor number and make the table dynamic? Use a wider minor number, a wider portion of the minor number for unit, decrease the number of bits used for things other than unit, use multiple major numbers, or use another encoding than major/minor numbers for device files (via devfs). Some aspects of the System V kernel build model, where the major numbers can be easily reassigned and the same file is used to drive the building of the kernel and the files in /dev, are really handy. Of course devfs makes it a point moot... From owner-freebsd-hackers Fri Jan 3 05:31:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA20738 for hackers-outgoing; Fri, 3 Jan 1997 05:31:43 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA20731 for ; Fri, 3 Jan 1997 05:31:38 -0800 (PST) Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vg9hb-000QYWC; Fri, 3 Jan 97 14:30 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id OAA14921; Fri, 3 Jan 1997 14:28:06 +0100 (MET) From: grog@lemis.de Message-Id: <199701031328.OAA14921@freebie.lemis.de> Subject: Re: Ints (fwd) In-Reply-To: <199701020100.LAA14579@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jan 2, 97 11:30:54 am" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 3 Jan 1997 14:28:06 +0100 (MET) Cc: hackers@freebsd.org (FreeBSD Hackers) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Reply-to: grog@lemis.de (Greg Lehey) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > hmmm stands accused of saying: >> >> Wait a second guys.... The interrupt lines on the ISA bus are >> open-collector, which means that it is possible to OR-TIE them >> together- remember Digital Electronics Fundamentals? Open-collector >> is very similar to tri-state, and is used when there is only 1 >> active state. If an application should require multiple devices to >> share a bus, and 2 active states are required, then tri-state >> drivers are required on all outputs. > > ... only ISA interrupt lines aren't open-collector. The RC time > constant implicit in OC circuits (there is a tradeoff between the > risetime and the power dissipation in the driving circuit) is > unacceptable for anything other than the slowest logic. > > Just about every other multi-card bus ever invented uses daisy-chained > interrupts or slot interrupts or some other manifestation of a sensible > scheme. But not ISA. YOU CANNOT SHARE INTERRUPTS SAFELY ON ISA. Well, I don't know if I consider daisy-chaining sensible either. But the biggest problem with interrupt sharing on ISA used to be the brain-dead circuitry of the UART board, not the bus nor the UART itself. The circuits I have show that the interrupt output of the UART goes to the *input* of an LS125 tri-state buffer, which then goes via a DIP switch to the IRQ3*/IRQ4* lines. The enable input (active low) of the LS125 gate is driven by OUT2*, which is effectively the "interrupt enable" bit of the modem control register. The problem with this is that the gate drives the IRQ line at all times, which isn't what tri-state is all about. The correct thing would have been to use the logical 'and' of OUT2* and INTRPT to enable the LS125 to pull the interrupt line down, but that would have required at least another LS00 gate. The way it is now, if you connect two of this kind of UART board to the bus, they'll fight every time there's an interrupt, and the stronger will win. To be fair, this is the way it used to be. Nowadays you don't get many circuit diagrams with your hardware, and it's possible that somebody has recognized the idiocy of this circuit, and has done something about it. But: 1. I'm sure not everybody has done so. 2. The marketing people wouldn't understand it, so they wouldn't document it. >> The only state which we are concerned with is ACTIVE (low). The >> processor doesn't care if an interrupt isn't happening, only when >> one IS. So a peripheral device does not DRIVE the interrupt line >> "the other way", it simply de-activates it's open-collector output. >> If another peripheral device happens to have interrupt asserted, the >> state of the IRQ line will not change. > > ... but the inputs to the 8259 are _edge_triggered_. If another > device is holding the line asserted, that doesn't count for a new > interrupt. It also means that another edge can't occur. So not only > is the second interrupt lost, but every interrupt after that is lost > as well. I thought the interrupt was just a pulse. It certainly was on the 8251. Greg From owner-freebsd-hackers Fri Jan 3 05:54:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA22046 for hackers-outgoing; Fri, 3 Jan 1997 05:54:29 -0800 (PST) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA22038 for ; Fri, 3 Jan 1997 05:54:26 -0800 (PST) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id IAA09060; Fri, 3 Jan 1997 08:53:51 -0500 Date: Fri, 3 Jan 1997 08:53:50 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@freebsd.org Subject: Re: file locking / firewalling based on uid/gid In-Reply-To: <199701030443.UAA28355@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk actually the plan 9 interface to the network is also worth a look. see the usenix paper from a few years back (meaning, i forget when it was written). ron Ron Minnich |"Failure is not an option" -- Gene Kranz rminnich@sarnoff.com | -- except, of course, on Microsoft products (609)-734-3120 | ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Fri Jan 3 06:08:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA22804 for hackers-outgoing; Fri, 3 Jan 1997 06:08:52 -0800 (PST) Received: from intercore.com ([199.181.243.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA22799 for ; Fri, 3 Jan 1997 06:08:48 -0800 (PST) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id JAA10647; Fri, 3 Jan 1997 09:00:44 -0500 (EST) Message-Id: <199701031400.JAA10647@intercore.com> Date: Fri, 3 Jan 1997 09:00:44 -0500 From: robin@intercore.com (Robin Cutshaw) To: dg@root.com Cc: robin@intercore.com (Robin Cutshaw), hackers@freebsd.org Subject: Re: tcp problems with 2.1.6.1 In-Reply-To: <199701030305.TAA18683@root.com>; from David Greenman on Jan 2, 1997 19:05:26 -0800 References: <199701021952.OAA08144@intercore.com> <199701030305.TAA18683@root.com> X-Mailer: Mutt 0.47 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > You need to mention what type of ethernet card you're using. The bug isn't > likely with the TCP code, but rather a device driver or hardware problem. > Sorry, I'm using Digital DE-500 (21140 based) cards in fast ethernet mode. I haven't seen any errors logged on behalf of the card. Here's some interesting output from netstat -s: tcp: 501348 packets sent 484426 data packets (214415659 bytes) 8966 data packets (5313164 bytes) retransmitted 0 resends initiated by MTU discovery 5549 ack-only packets (5005 delayed) 9 URG only packets 54 window probe packets 2244 window update packets 100 control packets 476219 packets received 392987 acks (for 214425296 bytes) 13619 duplicate acks 0 acks for unsent data 322209 packets (36425519 bytes) received in-sequence 225 completely duplicate packets (27234 bytes) 0 old duplicate packets 138 packets with some dup. data (17388 bytes duped) 328 out-of-order packets (110372 bytes) 3 packets (0 bytes) of data after window 0 window probes 4731 window update packets 0 packets received after close 5 discarded for bad checksums 0 discarded for bad header offset fields 0 discarded because packet too short 67 connection requests 28 connection accepts 0 bad connection attempts 0 listen queue overflows 95 connections established (including accepts) 94 connections closed (including 2 drops) 58 connections updated cached RTT on close 58 connections updated cached RTT variance on close 50 connections updated cached ssthresh on close 0 embryonic connections dropped 337150 segments updated rtt (of 342025 attempts) 4199 retransmit timeouts 1 connection dropped by rexmit timeout 0 persist timeouts 0 connections dropped by persist timeout 23 keepalive timeouts 23 keepalive probes sent 0 connections dropped by keepalive 87762 correct ACK header predictions 64217 correct data packet header predictions robin From owner-freebsd-hackers Fri Jan 3 06:14:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23046 for hackers-outgoing; Fri, 3 Jan 1997 06:14:37 -0800 (PST) Received: from hda.hda.com (ip81-max1-fitch.ziplink.net [199.232.245.81]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA23036 for ; Fri, 3 Jan 1997 06:14:33 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id JAA24455 for hackers@freebsd.org; Fri, 3 Jan 1997 09:10:44 -0500 From: Peter Dufault Message-Id: <199701031410.JAA24455@hda.hda.com> Subject: Re: more than 32 disks? In-Reply-To: <199701031302.HAA07824@bonkers.taronga.com> from Peter da Silva at "Jan 3, 97 07:02:49 am" To: hackers@freebsd.org Date: Fri, 3 Jan 1997 09:10:43 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter da Silva wrote in response to the 32 unit limit on SCSI disks:: > Use a wider minor number, a wider portion of the minor number for unit, > decrease the number of bits used for things other than unit, use multiple > major numbers, or use another encoding than major/minor numbers for device > files (via devfs). A related question: are there issues (regarding booting, etc) with removing all partition/slice/ file system code from the different device drivers and having a single "dk" device that gets wired to the other block devices? Essentially have the base device be a trusting client of a dk device that handles all that stuff. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Fri Jan 3 06:56:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA25154 for hackers-outgoing; Fri, 3 Jan 1997 06:56:34 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA25048 for ; Fri, 3 Jan 1997 06:55:14 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA05212 for hackers@freebsd.org; Fri, 3 Jan 1997 15:11:21 +0100 From: Luigi Rizzo Message-Id: <199701031411.PAA05212@labinfo.iet.unipi.it> Subject: kernel bootp stuff To: hackers@freebsd.org Date: Fri, 3 Jan 1997 15:11:21 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just managed to run (on 2.1R) the kernel bootp stuff I received from Tor Egge. Although I needed some cleanups to overcome limitations of our bootpd (which does not send multicast replies as it should) and mountd (which does not allow mounting files, but only directries; this is fixed in 3.0 -current) I have to say that this stuff is quite useful. Among its advantages: - you don't have to mess up with tftp; all boot info are supplied by bootpd - it can be used with cards (so many of them!) not supported by netboot; just boot from a floppy (or the dos partition with fbsdboot) and you have your system up and running; - it can be used to assign addresses to machines at boot time, rather than having them hardwired in /etc/sysconfig. Before wasting too much time trying to cleanup the code for general use, is there any of the committers interested in adding it to the distributions (post 2.2) ? It's just a couple of new files and very short modifications to 4-5 files mainly to instruct config to deal with the new option properly. 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/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Jan 3 07:25:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA26803 for hackers-outgoing; Fri, 3 Jan 1997 07:25:00 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA26798 for ; Fri, 3 Jan 1997 07:24:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA09454; Fri, 3 Jan 1997 08:24:49 -0700 (MST) Date: Fri, 3 Jan 1997 08:24:49 -0700 (MST) Message-Id: <199701031524.IAA09454@rocky.mt.sri.com> From: Nate Williams To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Stupid ipfw question. In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Why doesn't the following 2 rules allow any type of outbound TCP > connection? > > /sbin/ipfw add pass tcp from ${ip} to any setup > /sbin/ipfw add pass tcp from any to any established What are the previous ipfw commands? Also, you probably want to reverse the order of the commands, since you want established connections to hit a 'good' rule as soon as possible for effeciency (Poul pointed this out to me a while back.) If you want, give me a call at work as I've got a pretty good set of IPFW rules that I'd be willing to explain. > I must be missing something obvious with the PORT commands, most likely it > being that the port command is from the remote host to my host, but since > I don't know what port it will be, I have to leave a bunch of them open, > which seems to be a problematic issue for firewalling. It is. The ftp command begins a new connection *from* port 20 on the remote side to a random port on your side. It's a totally bogus implementation, but it's been with us so long that it's still a standard. ############ # XXX - I don't like this, but apparently ftp connects *from* this # port on the remote side to any port on my end. Disabling this requires # passive mode ftp clients (netscape works) #ipfw add 54 pass tcp from any 20 to any via etha16 in Nate From owner-freebsd-hackers Fri Jan 3 07:37:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA27482 for hackers-outgoing; Fri, 3 Jan 1997 07:37:48 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA27475 for ; Fri, 3 Jan 1997 07:37:45 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA05997 for ; Fri, 3 Jan 1997 09:36:00 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma005993; Fri Jan 3 09:35:55 1997 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA03040 for ; Fri, 3 Jan 1997 09:36:34 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.4/8.6.12) with ESMTP id JAA16890 for ; Fri, 3 Jan 1997 09:36:57 -0600 (CST) Message-Id: <199701031536.JAA16890@jake.lodgenet.com> X-Mailer: exmh version 2.0beta 12/23/96 To: hackers@freebsd.org Subject: device driver initialization Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jan 1997 09:36:56 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy, It looks like most of the ISA drivers now days have a frag like: SYSINIT(foo,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,foo_drvinit,NULL) foo_drvinit(void *nothing){ static int foo_devsw_installed=0; dev_t dev; if (! foo_devsw_installed ) { dev = makedev(CDEV_MAJOR, 0); cdevsw_add(&dev, &foo_cdevsw, NULL); foo_devsw_installed = 1; } } Is there any reason that this can't be absorbed in the attach function, somewhere around where the devfs stuff is done? What's the reason for adding yet another entry point during re-boot. Isn't probe/attach enough? eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Jan 3 07:38:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA27545 for hackers-outgoing; Fri, 3 Jan 1997 07:38:57 -0800 (PST) Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA27534 for ; Fri, 3 Jan 1997 07:38:42 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id RAA26040; Fri, 3 Jan 1997 17:36:45 +0200 Date: Fri, 3 Jan 1997 17:36:43 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: Darren Reed cc: Julian Assange , hackers@FreeBSD.ORG Subject: Re: file locking / firewalling based on uid/gid In-Reply-To: <199701022257.OAA10122@freefall.freebsd.org> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 3 Jan 1997, Darren Reed wrote: > > sockfs anyone ? > Plan9 ? -- Best, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-hackers Fri Jan 3 07:49:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA28193 for hackers-outgoing; Fri, 3 Jan 1997 07:49:46 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA28186 for ; Fri, 3 Jan 1997 07:49:43 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id PAA18180; Fri, 3 Jan 1997 15:49:42 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA079356581; Fri, 3 Jan 1997 15:49:41 GMT Message-Id: <32CD2AEB.CCF@fsl.noaa.gov> Date: Fri, 03 Jan 1997 08:51:07 -0700 From: Sean Kelly Organization: CIRA/NOAA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: spork Cc: Christoph Kukulies , freebsd-hackers@freefall.freebsd.org Subject: Re: advice sought - Quantum 2GB Atlas broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk spork wrote: > Now I just have to find > a way to detect when the CPU fan dies... Those of us tinkering with FreeBSD home automation have a solution. We can run a three-wire bus with Dallas Semiconductor DS1820 temperature sensors attached; the other end plugs into a small component box and into a serial port. The sensors can be placed on key system components (cpu, drives, power supply) and report their temperatures when queried. When the temperature exceeds a certain limit, an X10 appliance module is used to cut power to the system (after a clean shutdown, hopefully). X10 can be run over a serial port or using the built-in /dev/tw driver. If the X10/temperature sensor host itself is running hot, it can shutdown every system and then itself. See http://freebsd.org/~fsmp/HomeAuto/HomeAuto.html for more info. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Fri Jan 3 08:53:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA02130 for hackers-outgoing; Fri, 3 Jan 1997 08:53:39 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA02124 for ; Fri, 3 Jan 1997 08:53:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id IAA21468; Fri, 3 Jan 1997 08:52:53 -0800 (PST) Message-Id: <199701031652.IAA21468@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: robin@intercore.com (Robin Cutshaw) cc: hackers@freebsd.org Subject: Re: tcp problems with 2.1.6.1 In-reply-to: Your message of "Fri, 03 Jan 1997 09:00:44 EST." <199701031400.JAA10647@intercore.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 03 Jan 1997 08:52:53 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >David Greenman writes: >> >> You need to mention what type of ethernet card you're using. The bug isn't >> likely with the TCP code, but rather a device driver or hardware problem. >> > >Sorry, I'm using Digital DE-500 (21140 based) cards in fast ethernet mode. >I haven't seen any errors logged on behalf of the card. So netstat -i doesn't show any ierrors or oerrors? This sounds like a cabling problem or a problem with the hub or hub configuration (especially if it is a switched hub). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Jan 3 09:25:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA03623 for hackers-outgoing; Fri, 3 Jan 1997 09:25:51 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA03616 for ; Fri, 3 Jan 1997 09:25:48 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA28183 (5.67b/IDA-1.5 for hackers@freebsd.org); Fri, 3 Jan 1997 18:25:17 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id SAA00624; Fri, 3 Jan 1997 18:20:17 +0100 (MET) From: Wilko Bulte Message-Id: <199701031720.SAA00624@yedi.iaf.nl> Subject: Re: file locking / firewalling based on uid/gid To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Fri, 3 Jan 1997 18:20:17 +0100 (MET) Cc: avalon@coombs.anu.edu.au, proff@iq.org, hackers@freebsd.org In-Reply-To: <199701030443.UAA28355@freefall.freebsd.org> from "Jonathan M. Bresler" at Jan 2, 97 08:43:19 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jonathan M. Bresler wrote... > > Darren Reed wrote: > > > > In some mail from Julian Assange, sie said: > > [...] > > > # ipfw add pass tcp from any to any established gid inetd > > > # ipfw add padd tcp from any to any 21,79 setup in gid inetd > > > > (who needs sendmail to run as root now ?!) > > > > and have open() calls on those devices create sockets. > > > > sockfs anyone ? > > stevens and pendry called this "portals" > apply standard access control to the portals. > sendmail is uid/gid "sendmail" > chown sendmail.sendmail /p/net/tcp/localhost/25 > chmod 600 /p/net/tcp/localhost/25 And who does the chown() to allow users to get at their mail? Or am I missing something? Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Fri Jan 3 10:03:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA05084 for hackers-outgoing; Fri, 3 Jan 1997 10:03:02 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA05060 for ; Fri, 3 Jan 1997 10:02:36 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-13.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA05318 (5.67b/IDA-1.5 for ); Fri, 3 Jan 1997 19:02:03 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id SAA00389; Fri, 3 Jan 1997 18:09:23 +0100 (CET) Message-Id: Date: Fri, 3 Jan 1997 18:08:03 +0100 From: se@freebsd.org (Stefan Esser) To: avalon@coombs.anu.edu.au (Darren Reed) Cc: hans@brandinnovators.com (Hans Zuidam), freebsd-hackers@freebsd.org Subject: Re: bootloader & memory test... References: <199612271048.KAA05227@truk.brandinnovators.com> <199701021046.CAA27917@freefall.freebsd.org> X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: <199701021046.CAA27917@freefall.freebsd.org>; from Darren Reed on Jan 2, 1997 21:45:48 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 2, avalon@coombs.anu.edu.au (Darren Reed) wrote: > I haven't delved too deeply, but how hard would it be to have the kernel's > idle loop do a memory test ? Besides the point, that it would be very complex to do the right thing if this code ever finds a problem, such a test would guarantee, that the caches are "empty" every time you leave the idle loop. ;) Regards, STefan From owner-freebsd-hackers Fri Jan 3 10:49:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA07515 for hackers-outgoing; Fri, 3 Jan 1997 10:49:52 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA07510 for ; Fri, 3 Jan 1997 10:49:49 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id KAA02501 for ; Fri, 3 Jan 1997 10:49:47 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id KAA08397; Fri, 3 Jan 1997 10:41:42 -0800 (PST) Message-ID: <32CD529D.167EB0E7@whistle.com> Date: Fri, 03 Jan 1997 10:40:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Eric L. Hernes" CC: hackers@freebsd.org Subject: Re: device driver initialization References: <199701031536.JAA16890@jake.lodgenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eric L. Hernes wrote: > > Howdy, > > It looks like most of the ISA drivers now days have a frag like: > > SYSINIT(foo,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,foo_drvinit,NULL) > > foo_drvinit(void *nothing){ > static int foo_devsw_installed=0; > dev_t dev; > > if (! foo_devsw_installed ) { > dev = makedev(CDEV_MAJOR, 0); > cdevsw_add(&dev, &foo_cdevsw, NULL); > foo_devsw_installed = 1; > } > } > > Is there any reason that this can't be absorbed in the attach function, > somewhere around where the devfs stuff is done? What's the reason for > adding yet another entry point during re-boot. Isn't probe/attach enough? > > The addition of a devsw entry is done ONCE PER DRIVER the probe/attach is done ONCE PER INSTANCE so the usages are slightly different. other than that, yes it could be done.... remember also that the eventual aim is to make drivers LKMable in which case the SYSINIT part would be done by the LKM installation. It was easier to add this to every driver in a 'boilerplate' manner (in fact I used a combination of scripts and manual editing to add it), than to add more specialist code to each attach routine.. julian From owner-freebsd-hackers Fri Jan 3 10:54:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA07745 for hackers-outgoing; Fri, 3 Jan 1997 10:54:54 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA07738 for ; Fri, 3 Jan 1997 10:54:52 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id KAA02508 for ; Fri, 3 Jan 1997 10:54:50 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id KAA08548; Fri, 3 Jan 1997 10:48:34 -0800 (PST) Message-ID: <32CD5439.2781E494@whistle.com> Date: Fri, 03 Jan 1997 10:47:21 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: brawley@communica.com.au, hackers@FreeBSD.ORG Subject: Re: Device driver initialisation References: <199701030933.UAA26540@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I think it's the bdev case that's broken. Drivers should add entries to > the devswitches themselves in all cases. In 2.2., non-lkm drivers have to > do this, so doing it differently for the lkm case just requires more code. > Most drivers do it in a poor way using SYSINIT(). This also requires more > code and gives worse results than adding the entries at the appropriate > time (several drivers have active devswitch entries although their probe > has failed, and open routines that can't handle being called when the > driver hasn't been attached). I agree.. The SYSINIT method was used to make the implimentation quicker. most drivers should grow an 'init routine' that is called in both the LKM and linked cases the mechanism to do so is not decided yet however. maybe we should have a little SIG on this some time.. From owner-freebsd-hackers Fri Jan 3 11:23:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA09308 for hackers-outgoing; Fri, 3 Jan 1997 11:23:49 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA09295 for ; Fri, 3 Jan 1997 11:23:41 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA17411; Fri, 3 Jan 1997 20:21:36 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA17891; Fri, 3 Jan 1997 20:21:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA15763; Fri, 3 Jan 1997 20:20:23 +0100 (MET) Message-ID: Date: Fri, 3 Jan 1997 20:20:22 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Cc: eivind@dimaga.com (Eivind Eklund) Subject: Re: 2.2-BETA install fraught with peril? References: <3.0.32.19970103135444.009c5a70@dimaga.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.32.19970103135444.009c5a70@dimaga.com>; from Eivind Eklund on Jan 3, 1997 13:54:46 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Eivind Eklund wrote: I can't comment on all your problems, but some. > (1) FreeBSD adjusted the disk geometry (probably due to some stupid > "translation" in the BIOS or similar), so I couldn't boot when I was > finished installing. Do you perchance know the geometry values (before and after)? Did you install into `dangerously dedicated' mode (i don't think so)? > (2) fixit.flp didn't work Known and fixed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 3 11:44:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA10115 for hackers-outgoing; Fri, 3 Jan 1997 11:44:17 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA10105 for ; Fri, 3 Jan 1997 11:44:02 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id NAA18263; Fri, 3 Jan 1997 13:42:06 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma018260; Fri Jan 3 13:41:55 1997 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id NAA07726; Fri, 3 Jan 1997 13:42:34 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.4/8.6.12) with ESMTP id NAA24546; Fri, 3 Jan 1997 13:42:57 -0600 (CST) Message-Id: <199701031942.NAA24546@jake.lodgenet.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Julian Elischer cc: "Eric L. Hernes" , hackers@freebsd.org Subject: Re: device driver initialization In-reply-to: Your message of "Fri, 03 Jan 1997 10:40:29 PST." <32CD529D.167EB0E7@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jan 1997 13:42:56 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: >Eric L. Hernes wrote: >> >> Howdy, >> >> It looks like most of the ISA drivers now days have a frag like: >> >> SYSINIT(foo,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,foo_drvinit,NULL) >> >> foo_drvinit(void *nothing){ >> static int foo_devsw_installed=0; >> dev_t dev; >> >> if (! foo_devsw_installed ) { >> dev = makedev(CDEV_MAJOR, 0); >> cdevsw_add(&dev, &foo_cdevsw, NULL); >> foo_devsw_installed = 1; >> } >> } >> >> Is there any reason that this can't be absorbed in the attach function, >> somewhere around where the devfs stuff is done? What's the reason for >> adding yet another entry point during re-boot. Isn't probe/attach enough? >> >> > >The addition of a devsw entry is done ONCE PER DRIVER > >the probe/attach is done ONCE PER INSTANCE yea, but the `if (!devsw_installed) {}' clause should take care of that. I'm guessing now that the order in which devsw entries are installed is important, maybe sequential? Since the SYSINIT() macro has the SI_ORDER_MIDDLE+CDEV_MAJOR, does cdevsw_add, simply tack the devsw on the end of the list; so that the seemingly random probe/attach order will break things? > >so the usages are slightly different. > >other than that, yes it could be done.... >remember also that the eventual aim is to make drivers LKMable >in which case the SYSINIT part would be done by the LKM installation. > I usually have my foo_load call probe/attach as in the autoconf code. >It was easier to add this to every driver in a 'boilerplate' manner >(in fact I used a combination of scripts and manual editing >to add it), than to add more specialist code to each attach routine.. > That I understand, should a new driver use SYSINIT to be like most of the others, or stick it in attach? If order is important, there is no choice. >julian thanks, eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Jan 3 11:45:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA10191 for hackers-outgoing; Fri, 3 Jan 1997 11:45:49 -0800 (PST) Received: from kodiak.ucla.edu (kodiak.ucla.edu [164.67.128.11]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA10184 for ; Fri, 3 Jan 1997 11:45:45 -0800 (PST) Received: from pita.cns.ucla.edu (pita.cns.ucla.edu [164.67.62.11]) by kodiak.ucla.edu (8.8.4/8.6.9) with SMTP id TAA22060 for ; Fri, 3 Jan 1997 19:45:42 GMT From: Scott Burris To: freebsd-hackers@FreeBSD.ORG Subject: 2.2-BETA hangs after a few minutes Message-ID: Date: Fri, 3 Jan 1997 11:45:42 -0800 (PST) Priority: NORMAL X-Mailer: Simeon for Motif Version 4.0.9 X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've updated several of my FreeBSD systems at home with 2.2-BETA. One, a generic Triton chipset motherboard works just fine. The other, a Pentium system with the Opti chipset which connects the PCI bus to the VLB (instead of the other way around :-() now hangs solid after being up for anywhere between 10 and 30 minutes. No panics, no nothing, the system just appears to be completely dead. I compiled a new kernel with the debugger, but when the system hangs, I can't force it into the debugger. This system used to run the August 2.2 SNAP without problems and I have reverted back to that kernel. I'm happy to look into this further, but can anyone make a suggestion about how to debug a system that doesn't even panic? Scott ---------------------- Scott Burris UCLA Campus Telecomunications and Network Services scott@cns.ucla.edu From owner-freebsd-hackers Fri Jan 3 12:31:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA12998 for hackers-outgoing; Fri, 3 Jan 1997 12:31:11 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA12993 for ; Fri, 3 Jan 1997 12:31:08 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id MAA10622; Fri, 3 Jan 1997 12:26:39 -0800 (PST) Message-ID: <32CD6B36.6201DD56@whistle.com> Date: Fri, 03 Jan 1997 12:25:26 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Eric L. Hernes" CC: hackers@freebsd.org Subject: Re: device driver initialization References: <199701031942.NAA24546@jake.lodgenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eric L. Hernes wrote: > yea, but the `if (!devsw_installed) {}' clause should take care > of that. > > I'm guessing now that the order in which devsw entries > are installed is important, maybe sequential? Since the SYSINIT() > macro has the SI_ORDER_MIDDLE+CDEV_MAJOR, does cdevsw_add, > simply tack the devsw on the end of the list; so that the seemingly > random probe/attach order will break things? no order is not important the CDEV_MAJOR could be left out of the above... > >It was easier to add this to every driver in a 'boilerplate' manner > >(in fact I used a combination of scripts and manual editing > >to add it), than to add more specialist code to each attach routine.. > > > > That I understand, should a new driver use SYSINIT to be like most > of the others, or stick it in attach? If order is important, there is > no choice. no you could do it your way... I would keep the different logical parts in separate functions and call them rater than mergre the code.. remember some devices have cdevsw entries but are not probed.. e.g. /dev/mem, /dev/ptyxx etc.etc. it makes it more consistent to have a special time for initialising the driver, so that having an 'attach' is not 'required'. > > >julian > > thanks, > eric. > -- > erich@lodgenet.com > http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Jan 3 14:07:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA17106 for hackers-outgoing; Fri, 3 Jan 1997 14:07:17 -0800 (PST) Received: from merix.merix.com (merix.merix.com [198.145.172.40]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA17090 for ; Fri, 3 Jan 1997 14:07:12 -0800 (PST) Received: from sandy.merix.com by merix.merix.com with SMTP (1.38.110.45/16.2) id AA040899649; Fri, 3 Jan 1997 14:14:09 -0800 Received: by sandy.merix.com (4.1/8.0) id AA16444; Fri, 3 Jan 97 14:04:06 PST Date: Fri, 3 Jan 97 14:04:06 PST Subject: Graphing programs for *BSD? To: freebsd-hackers@freebsd.org From: Troy Curtiss Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello fellow FreeBSD'ers, Anyone know of a free package out there that can generate pie and histogram charts and export the data to a .gif/.jpg file for viewing automatically? For example, something that could give online web access to kernel vs. user vs. interrupt time via a pretty red/green/blue chart... Anyone done this? Thanks, -Troy From owner-freebsd-hackers Fri Jan 3 14:39:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18084 for hackers-outgoing; Fri, 3 Jan 1997 14:39:23 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18072 for ; Fri, 3 Jan 1997 14:39:05 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA11177; Sat, 4 Jan 1997 09:41:58 +1100 (EST) Date: Sat, 4 Jan 1997 09:41:57 +1100 (EST) From: "Daniel O'Callaghan" To: Troy Curtiss cc: freebsd-hackers@freebsd.org Subject: Re: Graphing programs for *BSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At a more basic level, check out fly, part of pwebstats - http://www.unimelb.edu.au/pwebstats/pwebstats.html Danny On Fri, 3 Jan 1997, Troy Curtiss wrote: > Hello fellow FreeBSD'ers, > Anyone know of a free package out there that can generate > pie and histogram charts and export the data to a .gif/.jpg file for > viewing automatically? For example, something that could give > online web access to kernel vs. user vs. interrupt time via a > pretty red/green/blue chart... Anyone done this? Thanks, > > -Troy > From owner-freebsd-hackers Fri Jan 3 15:05:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19045 for hackers-outgoing; Fri, 3 Jan 1997 15:05:22 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA19040 for ; Fri, 3 Jan 1997 15:05:19 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id PAA08882 for ; Fri, 3 Jan 1997 15:05:12 -0800 (PST) Date: Fri, 3 Jan 1997 15:05:12 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: pib comments. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Talk about mixed feelings. The package, concept, and use is great, but it is *slooooooowwwwwwwwwer* than molasses. I'm using an unloaded P6-200, with 128MB RAM, and Matrox cards, and pib takes 10-12 seconds to bring up the build tool. Plus it leaves this honking monster xterm widget thing running around until if finally gets everything resized. I'm losing faith in TCL/TK stuff. Nice idea conceptually, but painfully slow. Oh well, I just won't plan on being a package building fiend, and stick to the command line. For the newbie, it looks nice. From owner-freebsd-hackers Fri Jan 3 16:15:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA23294 for hackers-outgoing; Fri, 3 Jan 1997 16:15:17 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA23278 for ; Fri, 3 Jan 1997 16:15:11 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id AAA20910; Sat, 4 Jan 1997 00:15:03 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA297606902; Sat, 4 Jan 1997 00:15:02 GMT Message-Id: <32CDA15E.784C@fsl.noaa.gov> Date: Fri, 03 Jan 1997 17:16:30 -0700 From: Kelly Organization: CIRA/NOAA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: Jaye Mathisen Cc: hackers@FreeBSD.org Subject: Re: pib comments. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > I'm losing faith in TCL/TK stuff. Nice idea conceptually, but painfully > slow. We're using Tcl/Tk as part of our modernization for the National Weather Service and it blows the wheels off of OI (sorry, Warner) and competes easily with Motif. I've developed complex user interfaces with it for FreeBSD and they work amazingly fast. Is there an easy way to get a copy of this "pib" so I can try it out and examine it? I'd wager more than anything else it's a problem in the implementation rather than in Tcl/Tk itself. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Fri Jan 3 21:56:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA00950 for hackers-outgoing; Fri, 3 Jan 1997 21:56:44 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00945 for ; Fri, 3 Jan 1997 21:56:35 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA24821; Sat, 4 Jan 1997 16:50:39 +1100 Date: Sat, 4 Jan 1997 16:50:39 +1100 From: Bruce Evans Message-Id: <199701040550.QAA24821@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: Device driver initialisation Cc: brawley@communica.com.au, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The SYSINIT method was used to make the implimentation quicker. >most drivers should grow an 'init routine' that is called in both the >LKM and linked cases >the mechanism to do so is not decided yet however. There's probably no need for a special routine, since the attach routine should be a subset of the load routine. Bruce From owner-freebsd-hackers Fri Jan 3 21:58:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA01052 for hackers-outgoing; Fri, 3 Jan 1997 21:58:03 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA01025 for ; Fri, 3 Jan 1997 21:58:00 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id VAA04625 for ; Fri, 3 Jan 1997 21:27:12 -0800 (PST) Received: from marvin (ts64.slip.ksu.edu) by mail.crl.com with SMTP id AA29389 (5.65c/IDA-1.5 for ); Fri, 3 Jan 1997 21:25:54 -0800 Received: (from joed@localhost) by marvin (8.8.4/8.8.2) id XAA00673; Fri, 3 Jan 1997 23:15:08 -0600 (CST) Message-Id: Date: Fri, 3 Jan 1997 23:14:07 -0600 From: joed@ksu.edu (Joe Diehl) To: freebsd-hackers@FreeBSD.ORG Subject: network errors with ftp, scp, and irc's dcc X-Mailer: Mutt 0.55 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings, I seem to be running into a few problems on my machine at home... I've been having problems only under 2.2-ALPHA though I havn't been able to link the problems to FreeBSD. I still havn't but I'm running out of ideas. Essentially if I ftp from my home machine to vega.cis.ksu.edu or cbs.ksu.ksu.edu and try to put a file, the connection is established but no data is sent. If i ftp to fox.ksu.ksu.edu I can put a file just fine. I also cannot scp from my home machine to either of the above machines nor can I do a dcc send from home to these machines. The reverse direction works just fine. Ie vega% scp marvin:foo . (this works) marvin% scp foo vega: (this fails) Setup an ftp to a remote machine where I tired to put a file and grabbed bits and pieces out of tcpdump: 22:46:25.691003 ts64.slip.ksu.edu.1046 > fubar.ksu.ksu.edu.ident: P 1:6(5) ack 1 win 17520 (DF) 22:46:25.920620 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: . ack 6 win 8760 (DF) 22:46:25.920802 ts64.slip.ksu.edu.1046 > fubar.ksu.ksu.edu.ident: P 6:11(5) ack 1 win 17520 (DF) 22:46:26.110462 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: . ack 11 win 8760 (DF) 22:46:26.750552 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: P 1:34(33) ack 11 win 8760 (DF) 22:46:26.752426 ts64.slip.ksu.edu.1046 > fubar.ksu.ksu.edu.ident: F 11:11(0) ack 34 win 17520 (DF) 22:46:26.759977 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: F 34:34(0) ack 11 win 8760 (DF) 22:46:26.760172 ts64.slip.ksu.edu.1046 > fubar.ksu.ksu.edu.ident: F 11:11(0) ack 35 win 17520 (DF) 22:46:26.920460 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: . ack 12 win 8760 (DF) 22:46:26.920802 fubar.ksu.ksu.edu.ident > ts64.slip.ksu.edu.1046: . ack 12 win 8760 (DF) 22:48:42.073540 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: P 1:1025(1024) ack 1 win 17520 (DF) [tos 0x8] 22:48:42.076650 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: . 1025:2485(1460) ack 1 win 17520 (DF) [tos 0x8] 22:48:42.150151 ts64.slip.ksu.edu.1047 > fubar.ksu.ksu.edu.ftp: . ack 423 win 17520 (DF) [tos 0x10] 22:48:44.950279 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] 22:48:50.950280 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] 22:49:02.950252 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] 22:49:10.950381 ts64.slip.ksu.edu.40010 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] 22:50:14.950348 ts64.slip.ksu.edu.40012 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] 22:50:14.950535 ts64.slip.ksu.edu.40010 > fubar.ksu.ksu.edu.ftp-data: . 1:1461(1460) ack 1 win 17520 (DF) [tos 0x8] I do have a more complete log from the other end (that was filtering out to just this connection instead of picking out segments from a tcpdump of my ppp link ;) if anyone is interested. These machines all work for everyone else and there are no errors being sent to their /var/adm/messages files. I have to think it's on my end, but I'm completely stumped as to what it could be it's my fault. Since it is a network base issue here's my interface settings and routing table: joed@marvin:~% netstat -nr Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 129.130.231.12 UGSc 84 1 tun0 127.0.0.1 127.0.0.1 UH 1 335 lo0 129.130.231.12 129.130.231.64 UH 84 0 tun0 129.130.231.64 127.0.0.1 UH 0 0 lo0 172.16.25/24 link#2 UC 0 0 joed@marvin:~% ifconfig -a lp0: flags=8810 mtu 1500 ix0: flags=843 mtu 1500 inet 172.16.25.1 netmask 0xffffff00 broadcast 127.16.25.1 ether 00:aa:00:3d:bb:21 tun0: flags=8151 mtu 1500 inet 129.130.231.64 --> 129.130.231.12 netmask 0xffffff00 sl0: flags=c010 mtu 552 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 I'm wonder if this is related to the syn flood protections in FreeBSD-2.2, as I do know for sure my network worked like a charm with FreeBSD-2.1.5. Any thoughts? Joe Diehl From owner-freebsd-hackers Fri Jan 3 21:59:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA01511 for hackers-outgoing; Fri, 3 Jan 1997 21:59:42 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA01475 for ; Fri, 3 Jan 1997 21:59:35 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id UAA04409 for ; Fri, 3 Jan 1997 20:19:15 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id OAA22838; Sat, 4 Jan 1997 14:47:44 +1030 (CST) From: Michael Smith Message-Id: <199701040417.OAA22838@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: from Jaye Mathisen at "Jan 3, 97 03:05:12 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Sat, 4 Jan 1997 14:47:43 +1030 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen stands accused of saying: > > Talk about mixed feelings. The package, concept, and use is great, but > it is *slooooooowwwwwwwwwer* than molasses. Really? You're the first person to suggest this; I did a lot of speed testing on a 486/33 running diskless with an unacelerated TVGA8900 card and 8M of RAM. > I'm using an unloaded P6-200, with 128MB RAM, and Matrox cards, and pib > takes 10-12 seconds to bring up the build tool. Plus it leaves this > honking monster xterm widget thing running around until if finally gets > everything resized. Matrox? Oh, you're probably running Accelerated-X, right? AccelX (at least at the 1.x level) gives hopless performance with Tk, although I normally only noticed this with applications running remotely. The Xterm hanging around (it's up for less than a second on the 486/33) is a side-effect of your window manager insisting that the window be created onscreen. You could call this a bug in fvwm; I would have created it as an icon, but then when you deiconify it, even though it's been reparented, fvwm insists on drawing decorations for it. So I have to let it be realised full-size before reparenting it, and the tkSteal code tries to put it offscreen, but your WM is refusing. Not much I can do about that. > I'm losing faith in TCL/TK stuff. Nice idea conceptually, but painfully > slow. I suggest that you push the turbo button on your P6 phallus and perhaps try talking to the _author_ before you slam his work publically, or at the very least ask the ports group, who have been testing it for the last month or so. The speed problem is your setup, not my code, and I'll thank you to keep your criticism to those parts of the application that deserve it (and there are plenty of those, I'll willingly admit), or raise the issue with me privately. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jan 3 22:01:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA02034 for hackers-outgoing; Fri, 3 Jan 1997 22:01:22 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA02009 for ; Fri, 3 Jan 1997 22:01:17 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA03721 for ; Fri, 3 Jan 1997 18:30:52 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id VAA00702 for freebsd-hackers@freebsd.org; Fri, 3 Jan 1997 21:29:08 -0500 (EST) From: Charles Henrich Message-Id: <199701040229.VAA00702@crh.cl.msu.edu> Subject: MMAP Troubles (Joerg?) To: freebsd-hackers@FreeBSD.ORG Date: Fri, 3 Jan 1997 21:29:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have an oppourtunity for the MMAP person (Appears to be Joerg by the .c, but cant tell for sure :) Anyway, I have a big beefy pentium pro system here for use as news that im going to roll out in a few weeks. INN w/ MMAP causes the NULL trashed active file, interested in working on the problem with a system at your beck and call? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sat Jan 4 00:58:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06826 for hackers-outgoing; Sat, 4 Jan 1997 00:58:03 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06819 for ; Sat, 4 Jan 1997 00:57:58 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA25518; Sat, 4 Jan 1997 00:57:53 -0800 (PST) To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: pib comments. In-reply-to: Your message of "Fri, 03 Jan 1997 15:05:12 PST." Date: Sat, 04 Jan 1997 00:57:53 -0800 Message-ID: <25514.852368273@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm losing faith in TCL/TK stuff. Nice idea conceptually, but painfully > slow. I don't think this is TCL and Tk's fault at all - the ports and packages just aren't very efficiently organized, period, and pretty much *any* conceivable front end which doesn't attempt to keep its own information cache is doomed to be slower than heck. :-( Jordan From owner-freebsd-hackers Sat Jan 4 01:07:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA07167 for hackers-outgoing; Sat, 4 Jan 1997 01:07:30 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA07161 for ; Sat, 4 Jan 1997 01:07:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id BAA24212; Sat, 4 Jan 1997 01:06:53 -0800 (PST) Message-Id: <199701040906.BAA24212@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: joed@ksu.edu (Joe Diehl) cc: freebsd-hackers@freebsd.org Subject: Re: network errors with ftp, scp, and irc's dcc In-reply-to: Your message of "Fri, 03 Jan 1997 23:14:07 CST." From: David Greenman Reply-To: dg@root.com Date: Sat, 04 Jan 1997 01:06:53 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I seem to be running into a few problems on my machine at home... I've >been having problems only under 2.2-ALPHA though I havn't been able to >link the problems to FreeBSD. I still havn't but I'm running out of >ideas. > >Essentially if I ftp from my home machine to vega.cis.ksu.edu or >cbs.ksu.ksu.edu and try to put a file, the connection is established >but no data is sent. If i ftp to fox.ksu.ksu.edu I can put a file >just fine. > >I also cannot scp from my home machine to either of the above machines >nor can I do a dcc send from home to these machines. > >The reverse direction works just fine. Ie ... >Any thoughts? Looks like your machine is having troubles sending large packets. It looks like a modem/hardware flow control problem to me. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Jan 4 01:25:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08061 for hackers-outgoing; Sat, 4 Jan 1997 01:25:56 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA08056; Sat, 4 Jan 1997 01:25:51 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA30161; Sat, 4 Jan 1997 20:21:29 +1100 Date: Sat, 4 Jan 1997 20:21:29 +1100 From: Bruce Evans Message-Id: <199701040921.UAA30161@godzilla.zeta.org.au> To: avalon@coombs.anu.edu.au, se@FreeBSD.ORG Subject: Re: bootloader & memory test... Cc: freebsd-hackers@FreeBSD.ORG, hans@brandinnovators.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Besides the point, that it would be very complex to do the right thing >if this code ever finds a problem, such a test would guarantee, that >the caches are "empty" every time you leave the idle loop. ;) Actually, the test would want to work on non-cached pages to be sure of testing main memory. You could even run the code from a cached pages to avoid losing I-cache, but I suppose a really good memory test program should lock itself into the L1 cache to avoid side effects. It would also disable interrupts ... Not good for an idle loop. Bruce From owner-freebsd-hackers Sat Jan 4 01:53:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA09292 for hackers-outgoing; Sat, 4 Jan 1997 01:53:41 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA09283 for ; Sat, 4 Jan 1997 01:53:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA30811; Sat, 4 Jan 1997 20:48:31 +1100 Date: Sat, 4 Jan 1997 20:48:31 +1100 From: Bruce Evans Message-Id: <199701040948.UAA30811@godzilla.zeta.org.au> To: dufault@hda.com, hackers@FreeBSD.ORG Subject: Re: more than 32 disks? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >A related question: are there issues (regarding booting, etc) with >removing all partition/slice/ file system code from the different >device drivers and having a single "dk" device that gets wired to >the other block devices? Essentially have the base device be a >trusting client of a dk device that handles all that stuff. It makes things a little easier for the boot code. I think the main problems are that dk0 (sd0) gets would get renumbered to dk1 (sd0) when wd0 is also installed :-), and if you fix this by wiring down the drive numbers then you may lose uniformity by encoding the driver names in the device names. Bruce From owner-freebsd-hackers Sat Jan 4 02:51:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA11398 for hackers-outgoing; Sat, 4 Jan 1997 02:51:53 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA11383 for ; Sat, 4 Jan 1997 02:51:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA10417; Sat, 4 Jan 1997 11:51:25 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA02930; Sat, 4 Jan 1997 11:51:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA19646; Sat, 4 Jan 1997 11:43:34 +0100 (MET) Message-ID: Date: Sat, 4 Jan 1997 11:43:34 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Cc: henrich@crh.cl.msu.edu (Charles Henrich) Subject: Re: MMAP Troubles (Joerg?) References: <199701040229.VAA00702@crh.cl.msu.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701040229.VAA00702@crh.cl.msu.edu>; from Charles Henrich on Jan 3, 1997 21:29:08 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > I have an oppourtunity for the MMAP person (Appears to be Joerg by > the .c, but cant tell for sure :) Certainly not me, rather John Dyson. But doesn't matter. > Anyway, I have a big beefy pentium pro system here for use as news > that im going to roll out in a few weeks. INN w/ MMAP causes the > NULL trashed active file, interested in working on the problem with > a system at your beck and call? IIRC, the last word on INN w/ mmap() was that INN uses mmap() against the specs in that it tries to shorten (or extend) the file while it's being mmap()'ed. This only incidentally works on SysV's. All this is hearsay, so maybe John or somebody else will tell you more exactly. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 4 04:48:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA16625 for hackers-outgoing; Sat, 4 Jan 1997 04:48:39 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA16618 for ; Sat, 4 Jan 1997 04:48:36 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id XAA23499; Sat, 4 Jan 1997 23:18:25 +1030 (CST) From: Michael Smith Message-Id: <199701041248.XAA23499@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: <25514.852368273@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 4, 97 00:57:53 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 4 Jan 1997 23:18:24 +1030 (CST) Cc: mrcpu@cdsnet.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > I don't think this is TCL and Tk's fault at all - the ports and > packages just aren't very efficiently organized, period, and pretty > much *any* conceivable front end which doesn't attempt to keep its own > information cache is doomed to be slower than heck. :-( ... and I'll squash this one before it gets loose too. Satoshi was _very_ prompt in coming forwards with changes to the ports structure necessary for reasonably efficient management. The _only_ aspect of pib that is slow is the necessity to md5 _each_and_every_distfile_on_your_system_. That's what the K/sec counter is about, and its directly linked to the performance of your disk/cpu combination. On the tired old 2.1-something machine I developed pib on, along with four or five other users competing for core, disk and CPU (P100, NCR, Seagate Hawk), it still averaged over 200K/sec. If someone has a beef with this, please come forward with a faster md5 algorithm 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 4 05:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA16903 for hackers-outgoing; Sat, 4 Jan 1997 05:00:04 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA16898 for ; Sat, 4 Jan 1997 05:00:02 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id XAA23533; Sat, 4 Jan 1997 23:28:37 +1030 (CST) From: Michael Smith Message-Id: <199701041258.XAA23533@genesis.atrad.adelaide.edu.au> Subject: Re: MMAP Troubles (Joerg?) In-Reply-To: from J Wunsch at "Jan 4, 97 11:43:34 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 4 Jan 1997 23:28:35 +1030 (CST) Cc: freebsd-hackers@FreeBSD.ORG, henrich@crh.cl.msu.edu X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > > > Anyway, I have a big beefy pentium pro system here for use as news > > that im going to roll out in a few weeks. INN w/ MMAP causes the > > NULL trashed active file, interested in working on the problem with > > a system at your beck and call? > > IIRC, the last word on INN w/ mmap() was that INN uses mmap() against > the specs in that it tries to shorten (or extend) the file while it's > being mmap()'ed. This only incidentally works on SysV's. Slightly older news (but I suspect still current) was that INN is faster on FreeBSD _without_ mmap, due to caching etc. Remember that you will want to mount your spool disks async and noatime too. Search for anything that Joe Greco has posted about news machines; he appears to know his stuff pretty well. > All this is hearsay, so maybe John or somebody else will tell you more > exactly. There was a thread on this a while back; my recollection matches yours. > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 4 05:17:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA17465 for hackers-outgoing; Sat, 4 Jan 1997 05:17:35 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA17457 for ; Sat, 4 Jan 1997 05:17:31 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id FAA00284; Sat, 4 Jan 1997 05:17:18 -0800 (PST) To: Michael Smith cc: mrcpu@cdsnet.net, hackers@FreeBSD.ORG Subject: Re: pib comments. In-reply-to: Your message of "Sat, 04 Jan 1997 23:18:24 +1030." <199701041248.XAA23499@genesis.atrad.adelaide.edu.au> Date: Sat, 04 Jan 1997 05:17:18 -0800 Message-ID: <280.852383838@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ... and I'll squash this one before it gets loose too. Satoshi was > _very_ prompt in coming forwards with changes to the ports structure > necessary for reasonably efficient management. I meant no disregard for Satoshi's efforts - I was merely referring to limitations in the INDEX file + distributed port information scheme which makes it necessary to traverse the entire tree of 700+ ports if you want to know a little more information about, say, which ports go into /usr/local and which go into /usr/X11R6, or which are "legal" and which are not. In a modern GUI kinda environment, you'd have a button for "show installation trees" and all the ports would suddenly jump into columns, grouped by destination hierarchy, or if you clicked on "Highlight -> LEGAL", all the tainted ones would show up in red. I defy you to provide that level of functionality without keeping a cache. :-) Jordan From owner-freebsd-hackers Sat Jan 4 05:52:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA21139 for hackers-outgoing; Sat, 4 Jan 1997 05:52:47 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA21113 for ; Sat, 4 Jan 1997 05:52:40 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBFA13.FC64AEC0@kaori.communique.net>; Sat, 4 Jan 1997 07:50:42 -0600 Message-ID: From: Raul Zighelboim To: "'freebsd-hackers@freebsd.org'" , "'Charles Henrich'" Subject: RE: MMAP Troubles (Joerg?) Date: Sat, 4 Jan 1997 07:50:41 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk inn 1.5 has an option 'MSYNC = DO' that msyncs the active file at the right time, preventing corruption. I have been running it this way for a while, and the active file is healthy. BTW- inn is a lot faster with mmap enable. -------------------------- Raul Zighelboim mailto:mango@communique.net News Administrator http://communique.net >---------- >From: Charles Henrich[SMTP:henrich@crh.cl.msu.edu] >Sent: Friday, January 03, 1997 8:29 PM >To: freebsd-hackers@freebsd.org >Subject: MMAP Troubles (Joerg?) > >I have an oppourtunity for the MMAP person (Appears to be Joerg by the >.c, but >cant tell for sure :) > >Anyway, I have a big beefy pentium pro system here for use as news that >im >going to roll out in a few weeks. INN w/ MMAP causes the NULL trashed >active >file, interested in working on the problem with a system at your beck >and call? > >-Crh > > Charles Henrich Michigan State University >henrich@msu.edu > > http://pilot.msu.edu/~henrich > From owner-freebsd-hackers Sat Jan 4 05:54:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA21447 for hackers-outgoing; Sat, 4 Jan 1997 05:54:20 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA21415 for ; Sat, 4 Jan 1997 05:54:13 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id OAA07294; Sat, 4 Jan 1997 14:51:33 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id OAA12431; Sat, 4 Jan 1997 14:38:00 +0100 (MET) Message-Id: <3.0.32.19970104143948.00a0e230@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 04 Jan 1997 14:39:49 +0100 To: Jimbo Bahooli From: Eivind Eklund Subject: Re: 2.2-BETA install fraught with peril? Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:24 PM 1/3/97 -0600, you wrote: > > >On Fri, 3 Jan 1997, Eivind Eklund wrote: > > >> I think that was it. I got it to install (using 2.1.6-floppies instead of >> 2.2-BETA due to the bus errors/segment violations), and assume I will get >> it up and running later today (I'll just have to fix the partitioning and >> copy the data back), so I haven't and problems asa a such, but it would be >> nice for everybody else to get this fixed (as I now know the quirks, and >> won't have more trouble :) > >See the thing is, BETA, ALPHA, and SNAPS are designed to be installed by >people who know freebsd. The sysinstall is by a rule neglected in these >because its not neccessary to update it for people who know freebsd. >Maybe next time you will pay attention to the BETA in the name. The ALPHAs and especially BETAs are released to get a 100% stable version before a -RELEASE. Thus, all problems with the sysinstall should, IMHO, be of interest, as it is interesting to have them fixed before release. I've been running FreeBSD for about a year now, including kernel hacking it to get it to run on some systems. I think I qualify as knowing it. Anyway, citing from the FreeBSD 2.2-BETA announcement: >The BETA period for 2.2 will be approximately 20 days, starting today >and running through January 14th. Please test this release as >seriously as you can and report any problems to us, full instructions >for which are in the README.TXT file. Maybe next time you will pay attention to your facts and manners. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-hackers Sat Jan 4 06:09:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23286 for hackers-outgoing; Sat, 4 Jan 1997 06:09:21 -0800 (PST) Received: from wong.rogerswave.ca (a17b32.rogerswave.ca [204.92.17.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA23276 for ; Sat, 4 Jan 1997 06:09:14 -0800 (PST) Received: (from wong@localhost) by wong.rogerswave.ca (8.7.5/8.7.3) id JAA00389; Sat, 4 Jan 1997 09:09:20 -0500 (EST) Date: Sat, 4 Jan 1997 09:09:20 -0500 (EST) From: Ken Wong X-Sender: wong@wong.rogerswave.ca Reply-To: wong@rogerswave.ca To: Darren Reed cc: Terry Lambert , avalon@coombs.anu.edu.au, julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@FreeBSD.ORG Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters In-Reply-To: <199701021045.CAA27880@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Jan 1997, Darren Reed wrote: > > I was thinking about this the other day and wondered how easy would it be > to make the kernel compile as a user process ? I know Nate doesn't like QNX, but QNX does exactly that. we should invent some good communication/synchronization machinism to facilite user space program to do kernel stuff. Ken > > Darren > > From owner-freebsd-hackers Sat Jan 4 06:43:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA26222 for hackers-outgoing; Sat, 4 Jan 1997 06:43:03 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA26214 for ; Sat, 4 Jan 1997 06:42:58 -0800 (PST) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id QAA27339; Sat, 4 Jan 1997 16:40:49 +0200 (EET) Date: Sat, 4 Jan 1997 16:40:39 +0200 (EET) From: Narvi To: Michael Smith cc: "Jordan K. Hubbard" , mrcpu@cdsnet.net, hackers@freebsd.org Subject: Re: pib comments. In-Reply-To: <199701041248.XAA23499@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 4 Jan 1997, Michael Smith wrote: > Jordan K. Hubbard stands accused of saying: > > I don't think this is TCL and Tk's fault at all - the ports and > > packages just aren't very efficiently organized, period, and pretty > > much *any* conceivable front end which doesn't attempt to keep its own > > information cache is doomed to be slower than heck. :-( > > ... and I'll squash this one before it gets loose too. Satoshi was > _very_ prompt in coming forwards with changes to the ports structure > necessary for reasonably efficient management. > > The _only_ aspect of pib that is slow is the necessity to md5 > _each_and_every_distfile_on_your_system_. That's what the K/sec > counter is about, and its directly linked to the performance of your > disk/cpu combination. On the tired old 2.1-something machine I > developed pib on, along with four or five other users competing for > core, disk and CPU (P100, NCR, Seagate Hawk), it still averaged over > 200K/sec. If someone has a beef with this, please come forward with a > faster md5 algorithm 8) Well, there is the 64-bit tiger hash which is ~ 2x fater than md5... It is also supposed to be collisionless. I think I could make a port out of it after the exams (~ end of January). Sander > > > Jordan > > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > From owner-freebsd-hackers Sat Jan 4 09:31:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA03671 for hackers-outgoing; Sat, 4 Jan 1997 09:31:01 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA03666 for ; Sat, 4 Jan 1997 09:30:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA13868; Sat, 4 Jan 1997 10:30:51 -0700 (MST) Date: Sat, 4 Jan 1997 10:30:51 -0700 (MST) Message-Id: <199701041730.KAA13868@rocky.mt.sri.com> From: Nate Williams To: wong@rogerswave.ca Cc: Darren Reed , hackers@freebsd.org Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters In-Reply-To: References: <199701021045.CAA27880@freefall.freebsd.org> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ken Wong writes: > > > On Thu, 2 Jan 1997, Darren Reed wrote: > > > > I was thinking about this the other day and wondered how easy would it be > > to make the kernel compile as a user process ? > > I know Nate doesn't like QNX, but QNX does exactly that. Am I the Nate you are speaking of? If so, you're horribly confused since I *really* like QNX. > we should invent some good communication/synchronization machinism > to facilite user space program to do kernel stuff. Agreed. Nate From owner-freebsd-hackers Sat Jan 4 11:21:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA09801 for hackers-outgoing; Sat, 4 Jan 1997 11:21:42 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA09788 for ; Sat, 4 Jan 1997 11:21:39 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vgbep-00012z-00; Sat, 4 Jan 1997 12:21:27 -0700 To: Kelly Subject: Re: pib comments. Cc: Jaye Mathisen , hackers@freebsd.org In-reply-to: Your message of "Fri, 03 Jan 1997 17:16:30 MST." <32CDA15E.784C@fsl.noaa.gov> References: <32CDA15E.784C@fsl.noaa.gov> Date: Sat, 04 Jan 1997 12:21:27 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <32CDA15E.784C@fsl.noaa.gov> Kelly writes: : We're using Tcl/Tk as part of our modernization for the National Weather : Service and it blows the wheels off of OI (sorry, Warner) and competes : easily with Motif. I've developed complex user interfaces with it for : FreeBSD and they work amazingly fast. We've had different experiences then. Tk is pathologically non-orthogonal which makes it hard to learn and hard to use. Tcl tends to be fairly slow, but generally fast enough for GUI things. I found that tcl/Tk were painfully slow on my 486 DX 33, but OI was quite useable. Oh well, different strokes for different folks I guess. The C++ compile time really sucked, however, which can make development faster with tcl/Tk. Too bad none of the gui builders for it can hold a candle to ObjectBuilder :-). Warner From owner-freebsd-hackers Sat Jan 4 11:53:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA11599 for hackers-outgoing; Sat, 4 Jan 1997 11:53:01 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA11594 for ; Sat, 4 Jan 1997 11:52:59 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id OAA05970; Sat, 4 Jan 1997 14:52:58 -0500 (EST) From: Charles Henrich Message-Id: <199701041952.OAA05970@crh.cl.msu.edu> Subject: Re: MMAP Troubles (Joerg?) To: mango@staff.communique.net (Raul Zighelboim) Date: Sat, 4 Jan 1997 14:52:58 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from Raul Zighelboim at "Jan 4, 97 07:50:41 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > inn 1.5 has an option 'MSYNC = DO' that msyncs the active file > at the right time, preventing corruption. Okay, I will give that a shot.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sat Jan 4 11:54:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA11884 for hackers-outgoing; Sat, 4 Jan 1997 11:54:41 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA11875 for ; Sat, 4 Jan 1997 11:54:39 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id OAA05981; Sat, 4 Jan 1997 14:54:17 -0500 (EST) From: Charles Henrich Message-Id: <199701041954.OAA05981@crh.cl.msu.edu> Subject: Re: MMAP Troubles (Joerg?) To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 4 Jan 1997 14:54:17 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199701041258.XAA23533@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jan 4, 97 11:28:35 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Slightly older news (but I suspect still current) was that INN is > faster on FreeBSD _without_ mmap, due to caching etc. Remember that I dont see how that is, since the READ/WRITE's just turn into MMAP's inside the kernel (from what I understand of it). > you will want to mount your spool disks async and noatime too. Search Yeee, Im not that adventurous yet :) I hope I have sufficent spindles and I/O bandwidth where that wont be neccessary -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sat Jan 4 13:07:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA14916 for hackers-outgoing; Sat, 4 Jan 1997 13:07:38 -0800 (PST) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA14911 for ; Sat, 4 Jan 1997 13:07:35 -0800 (PST) Received: (from ck@localhost) by toplink1.toplink.net (8.6.12/8.6.12) id WAA25908 for freebsd-hackers@freebsd.org; Sat, 4 Jan 1997 22:05:12 +0100 From: Christian Kratzer Message-Id: <199701042105.WAA25908@toplink1.toplink.net> Subject: ethernet statistics To: freebsd-hackers@freebsd.org Date: Sat, 4 Jan 1997 22:05:11 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, among many other things we also use freebsd for ethernet to ethernet routing with gated. Does anybody know of a way to get interface statistics for the attached ethernet interfaces. It would be nice to gather load statistics from the attached segments. Greetings Christian -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 885-0 Fax: +49 7452 885-199 FreeBSD spoken here! From owner-freebsd-hackers Sat Jan 4 13:31:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA15625 for hackers-outgoing; Sat, 4 Jan 1997 13:31:56 -0800 (PST) Received: from melbourne.DIALix.oz.au (uucp@melbourne.DIALix.oz.au [192.203.228.98]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA15617 for ; Sat, 4 Jan 1997 13:31:48 -0800 (PST) Received: (from uucp@localhost) by melbourne.DIALix.oz.au with UUCP id IAA01072 for freebsd-hackers@FreeBSD.ORG; Sun, 5 Jan 1997 08:31:38 +1100 (EST) Received: from putte.seeware.DIALix.oz.au (putte.seeware.DIALix.oz.au [10.0.0.1]) by doorway.seeware.DIALix.oz.au (8.7.5/8.7.3) with ESMTP id IAA14053 for ; Sun, 5 Jan 1997 08:17:34 +1100 (EST) Message-Id: <199701042117.IAA14053@doorway.seeware.DIALix.oz.au> From: "Mark Hannon" To: Subject: Re: ft < 50kb/s ?? Date: Sun, 5 Jan 1997 08:16:30 +1100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ---------- > > ..., however in > > the current configuration it is dead slow - It just took me 12 hours > > to back up 200m of data, according to the manufacturers notes it > > You mean, it got slower over time? Even with a new (and freshly > formatted) medium? This would be fairly surprising, since the driver > hasn't changed except of a few side-effects from global changes. It's > basically orphaned (though maybe, i've found a new maintainer). > Yeh, it seemed to get much slower over time. > > Of course, the most important question for you is: does the tape > remain streaming? If not, all bets are off, and performance will > simply suck. We might then try profiling the driver or the [l]ft > utility. > If by streaming you mean continuously writing data forward, then the answer is no. The tape goes back and forward like a yoyo. If installed the driver programs under Windows and did a few tests, the tape drive itself definetly is the culprit, it is dog slow under Windows as well. I checked out Conner's homepage and am planning to clean the drive heads (something I've never done) before checking further. Regards/Mark From owner-freebsd-hackers Sat Jan 4 14:52:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA21193 for hackers-outgoing; Sat, 4 Jan 1997 14:52:20 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA21188 for ; Sat, 4 Jan 1997 14:52:18 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id OAA05321; Sat, 4 Jan 1997 14:51:54 -0800 (PST) To: Eivind Eklund cc: Jimbo Bahooli , hackers@freebsd.org Subject: Re: 2.2-BETA install fraught with peril? In-reply-to: Your message of "Sat, 04 Jan 1997 14:39:49 +0100." <3.0.32.19970104143948.00a0e230@dimaga.com> Date: Sat, 04 Jan 1997 14:51:54 -0800 Message-ID: <5317.852418314@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The ALPHAs and especially BETAs are released to get a 100% stable version > before a -RELEASE. Thus, all problems with the sysinstall should, IMHO, be > of interest, as it is interesting to have them fixed before release. I've > been running FreeBSD for about a year now, including kernel hacking it to > get it to run on some systems. I think I qualify as knowing it. This is all perfectly correct, and we very much appreciate Eivind's byg reports! Jordan From owner-freebsd-hackers Sat Jan 4 15:05:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21631 for hackers-outgoing; Sat, 4 Jan 1997 15:05:06 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA21612; Sat, 4 Jan 1997 15:05:02 -0800 (PST) Message-Id: <199701042305.PAA21612@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA248799098; Sun, 5 Jan 1997 10:04:58 +1100 From: Darren Reed Subject: Re: New Networking framework for BSD To: julian@freefall.freebsd.org (Julian Elischer) Date: Sun, 5 Jan 1997 10:04:58 +1100 (EDT) Cc: hackers@freefall.freebsd.org In-Reply-To: <199701022236.OAA09044@freefall.freebsd.org> from "Julian Elischer" at Jan 2, 97 02:36:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have one _big_ concern with this: Currently we have very well known and understood networking code inside the kernel which has been around for years and has matured over that time to become a very reliable backbone. Rewriting this (or replacing it) with new code will effectively put FreeBSD back many years in so far as being sure that it has reliable networking. Two excellent cases which show this are Solaris 2 & Linux (both of which have their own TCP/IP stack as opposed to BSD's) and amusingly the BSD socket interface is planned for Solaris 2.6 for software performance reasons :) So, as long as we're prepared to have an "options TESTINET" (or similar) for the kernel - which would be mutually exclusive with "options INET" - for some years to come, it looks like an interesting idea worth pursuing. Darren From owner-freebsd-hackers Sat Jan 4 15:50:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA29148 for hackers-outgoing; Sat, 4 Jan 1997 15:50:46 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA29140; Sat, 4 Jan 1997 15:50:35 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id PAA25483; Sat, 4 Jan 1997 15:46:09 -0800 (PST) Message-ID: <32CEEB76.237C228A@whistle.com> Date: Sat, 04 Jan 1997 15:44:54 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Darren Reed CC: Julian Elischer , hackers@freefall.freebsd.org Subject: Re: New Networking framework for BSD References: <199701042305.PAA21612@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren, see my mail drirectly to you... you appear to have commented without reading the doc yet.. I'm not trying to replace anything. Just make a framework for such services as frame relay and ATM, at the LINK level. I sent you a copy of the overview.. please read it, as I'd like your comments! Darren Reed wrote: > > I have one _big_ concern with this: > > Currently we have very well known and understood networking code inside the > kernel which has been around for years and has matured over that time to > become a very reliable backbone. Rewriting this (or replacing it) with new > code will effectively put FreeBSD back many years in so far as being sure > that it has reliable networking. Two excellent cases which show this are > Solaris 2 & Linux (both of which have their own TCP/IP stack as opposed to > BSD's) and amusingly the BSD socket interface is planned for Solaris 2.6 > for software performance reasons :) > > So, as long as we're prepared to have an "options TESTINET" (or similar) > for the kernel - which would be mutually exclusive with "options INET" - > for some years to come, it looks like an interesting idea worth pursuing. > > Darren From owner-freebsd-hackers Sat Jan 4 16:14:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA29905 for hackers-outgoing; Sat, 4 Jan 1997 16:14:58 -0800 (PST) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA29900 for ; Sat, 4 Jan 1997 16:14:54 -0800 (PST) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id BAA04162; Sun, 5 Jan 1997 01:14:23 +0100 (MET) Date: Sun, 5 Jan 1997 01:14:23 +0100 (MET) From: Andrzej Bialecki To: Scott Burris cc: freebsd-hackers@freebsd.org Subject: Re: 2.2-BETA hangs after a few minutes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 3 Jan 1997, Scott Burris wrote: > VLB (instead of the other way around :-() now hangs solid after being up > for anywhere between 10 and 30 minutes. No panics, no nothing, the > system just appears to be completely dead. I compiled a new kernel with Just guessing... Did you perchance check if the system is reachable via network? I experience from time to time such mysterious hangups, but the system is running - it's just the keyboard that dies (probably some glitches in power supply? or just my junky keyboard.. 8-* ) Andy, +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Sat Jan 4 16:44:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02903 for hackers-outgoing; Sat, 4 Jan 1997 16:44:26 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02817; Sat, 4 Jan 1997 16:43:28 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701050043.QAA02817@freefall.freebsd.org> Subject: Usenix FreeBSD BoF when? To: hackers, chat Date: Sat, 4 Jan 1997 16:43:27 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk the BoF (birds of a feather) page at usenix.org http://www.usenix.org/ana97/bofs.html does not list a FreeBSD BoF! shall we schedule one? 8pm wednsesday or 8pm thursday look good ;) jmb From owner-freebsd-hackers Sat Jan 4 17:13:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA04152 for hackers-outgoing; Sat, 4 Jan 1997 17:13:32 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA04147 for ; Sat, 4 Jan 1997 17:13:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id RAA26548; Sat, 4 Jan 1997 17:12:27 -0800 (PST) Message-Id: <199701050112.RAA26548@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Charles Henrich cc: msmith@atrad.adelaide.edu.au (Michael Smith), joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: MMAP Troubles (Joerg?) In-reply-to: Your message of "Sat, 04 Jan 1997 14:54:17 EST." <199701041954.OAA05981@crh.cl.msu.edu> From: David Greenman Reply-To: dg@root.com Date: Sat, 04 Jan 1997 17:12:27 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Slightly older news (but I suspect still current) was that INN is >> faster on FreeBSD _without_ mmap, due to caching etc. Remember that > >I dont see how that is, since the READ/WRITE's just turn into MMAP's inside the >kernel (from what I understand of it). Pages that are read in using read have lower priority than mmaped pages and can be more easily reclaimed. ...so it would probably be faster to do read/write for articles, but slower to do read/write for the active file (which you want to stay in memory if possible). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Jan 4 18:00:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA06246 for hackers-outgoing; Sat, 4 Jan 1997 18:00:14 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA06237; Sat, 4 Jan 1997 18:00:10 -0800 (PST) Message-Id: <199701050200.SAA06237@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA283109600; Sun, 5 Jan 1997 13:00:00 +1100 From: Darren Reed Subject: Re: New Networking framework for BSD To: julian@whistle.com (Julian Elischer) Date: Sun, 5 Jan 1997 13:00:00 +1100 (EDT) Cc: avalon@coombs.anu.edu.au, julian@freefall.freebsd.org, hackers@freefall.freebsd.org In-Reply-To: <32CEEB76.237C228A@whistle.com> from "Julian Elischer" at Jan 4, 97 03:44:54 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Julian Elischer, sie said: > > Darren, see my mail drirectly to you... > > you appear to have commented without reading the doc yet.. > I'm not trying to replace anything. Just make a framework for such > services as frame relay and ATM, at the LINK level. Yes, I read it briefly first but wrote that with an empty mind... Looks like the claytons STREAMS. How is it different to STREAMS (by design) ? Darren From owner-freebsd-hackers Sat Jan 4 18:13:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA06595 for hackers-outgoing; Sat, 4 Jan 1997 18:13:45 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA06579; Sat, 4 Jan 1997 18:13:38 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id SAA09064; Sat, 4 Jan 1997 18:13:34 -0800 (PST) To: "Jonathan M. Bresler" cc: hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-reply-to: Your message of "Sat, 04 Jan 1997 16:43:27 PST." <199701050043.QAA02817@freefall.freebsd.org> Date: Sat, 04 Jan 1997 18:13:33 -0800 Message-ID: <9061.852430413@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > the BoF (birds of a feather) page at usenix.org > http://www.usenix.org/ana97/bofs.html > does not list a FreeBSD BoF! We usually don't schedule it until we get to the show and have a feel for when people want to do it, but 8pm Wednesday would be fine with me. Jordan From owner-freebsd-hackers Sat Jan 4 18:21:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA06859 for hackers-outgoing; Sat, 4 Jan 1997 18:21:43 -0800 (PST) Received: from franc.ucdavis.edu (franc.ucdavis.edu [128.120.8.183]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA06808; Sat, 4 Jan 1997 18:20:18 -0800 (PST) Received: from dragon.nuxi.com by franc.ucdavis.edu (8.8.4/UCD3.8.4) id SAA23339; Sat, 4 Jan 1997 18:17:32 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id SAA04841; Sat, 4 Jan 1997 18:17:29 -0800 (PST) Message-ID: Date: Sat, 4 Jan 1997 18:17:28 -0800 From: obrien@cs.ucdavis.edu (David O'Brien) To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Cc: hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? References: <199701050043.QAA02817@freefall.freebsd.org> X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 Reply-To: deobrien@ucdavis.edu X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <199701050043.QAA02817@freefall.freebsd.org>; from Jonathan M. Bresler on Jan 4, 1997 16:43:27 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jonathan M. Bresler writes: > the BoF (birds of a feather) page at usenix.org > http://www.usenix.org/ana97/bofs.html > does not list a FreeBSD BoF! > > shall we schedule one? > 8pm wednsesday or 8pm thursday look good ;) I vote for 8pm Thursday. There doesn't seem to be anything scheduled for that time yet. I and there is one I'd like to goto Wed at 8pm. -- -- David (deobrien@ucdavis.edu) From owner-freebsd-hackers Sat Jan 4 18:35:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA07407 for hackers-outgoing; Sat, 4 Jan 1997 18:35:27 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA07193; Sat, 4 Jan 1997 18:31:09 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id SAA26550; Sat, 4 Jan 1997 18:27:45 -0800 (PST) Message-ID: <32CF1156.41C67EA6@whistle.com> Date: Sat, 04 Jan 1997 18:26:30 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Jonathan M. Bresler" CC: hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? References: <199701050043.QAA02817@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jonathan M. Bresler wrote: > > the BoF (birds of a feather) page at usenix.org > http://www.usenix.org/ana97/bofs.html > does not list a FreeBSD BoF! > > shall we schedule one? > 8pm wednsesday or 8pm thursday look good ;) > > jmb I was just about to post about this! sounds a good time to me! From owner-freebsd-hackers Sat Jan 4 19:52:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA10604 for hackers-outgoing; Sat, 4 Jan 1997 19:52:48 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA10598; Sat, 4 Jan 1997 19:52:46 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701050352.TAA10598@freefall.freebsd.org> Subject: Re: Usenix FreeBSD BoF when? To: julian@whistle.com (Julian Elischer) Date: Sat, 4 Jan 1997 19:52:46 -0800 (PST) Cc: hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <32CF1156.41C67EA6@whistle.com> from "Julian Elischer" at Jan 4, 97 06:26:30 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > > Jonathan M. Bresler wrote: > > > > the BoF (birds of a feather) page at usenix.org > > http://www.usenix.org/ana97/bofs.html > > does not list a FreeBSD BoF! > > > > shall we schedule one? > > 8pm wednsesday or 8pm thursday look good ;) > > > > jmb > > I was just about to post about this! > > sounds a good time to me! > David O'Brien (sp?) wants 8pm thursday, so let's go with that, no? no form to set one up over the web ;( has to be done at the registration desk first one to arrive gets the honors! jmb From owner-freebsd-hackers Sat Jan 4 20:51:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA12064 for hackers-outgoing; Sat, 4 Jan 1997 20:51:16 -0800 (PST) Received: from antares.aero.org (antares.aero.org [130.221.192.46]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA12058; Sat, 4 Jan 1997 20:51:14 -0800 (PST) Received: from anpiel.aero.org (anpiel.aero.org [130.221.196.66]) by antares.aero.org (8.8.4/8.7.3) with SMTP id UAA20001; Sat, 4 Jan 1997 20:50:42 -0800 (PST) Message-Id: <199701050450.UAA20001@antares.aero.org> To: "Jonathan M. Bresler" Cc: julian@whistle.com (Julian Elischer), hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-Reply-To: Your message of "Sat, 04 Jan 1997 19:52:46 PST." <199701050352.TAA10598@freefall.freebsd.org> Date: Sat, 04 Jan 1997 20:50:20 -0800 From: "Mike O'Brien" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > no form to set one up over the web ;( > has to be done at the registration desk I did that, when I was doing USENIX things. Very hungry commercial outfits were trying to schedule BoFs months in advance which amounted to no more than live infomercials for their products. I was revulsed and insisted that BoFs be scheduled only at the conference, to preserve some semblance of spontaneity. I borrowed the BoF idea from DECUS, where it amounts to meetings organized by people around topics too new to have been scheduled into the regular program... many regularly scheduled daytime DECUS sessions are (or were) really just BoFs of long standing. I did this long before the IETF and its BoFs were a going concern, ditto Uniforum. Frankly given the alternative I'm real happy with things as they are now. Mike O'Brien