From owner-freebsd-current Sun Nov 29 00:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07229 for freebsd-current-outgoing; Sun, 29 Nov 1998 00:45:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07220 for ; Sun, 29 Nov 1998 00:45:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id AAA16578; Sun, 29 Nov 1998 00:45:17 -0800 (PST) (envelope-from obrien) Message-ID: <19981129004517.B28637@nuxi.com> Date: Sun, 29 Nov 1998 00:45:17 -0800 From: "David O'Brien" To: Nathan Dorfman , freebsd-current@FreeBSD.ORG Subject: Re: libmytinfo breaks vim-5.3 port, maybe others? Reply-To: obrien@NUXI.com References: <19981023205115.A5357@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981023205115.A5357@rtfm.net>; from Nathan Dorfman on Fri, Oct 23, 1998 at 08:51:15PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with > libmytinfo. At first I thought it was vim breakage, or Motif/Athena > or even X11 breakage. But read on: ..snip.. > Anyway, I noticed something weird: > > libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000) This is automatically linked in if libncurses is being used. I'm open to patches to fix the Gvim problem if anybody has found a fix. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 01:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08721 for freebsd-current-outgoing; Sun, 29 Nov 1998 01:11:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au ([203.46.81.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08716 for ; Sun, 29 Nov 1998 01:11:02 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id TAA16579; Sun, 29 Nov 1998 19:10:48 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma016577; Sun, 29 Nov 98 19:10:22 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA12345; Sun, 29 Nov 1998 19:10:22 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA22763; Sun, 29 Nov 1998 19:10:21 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA16558; Sun, 29 Nov 1998 19:10:19 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199811290910.TAA16558@nymph.dtir.qld.gov.au> To: "Richard B. Ernst" cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: 2.2.7-->current shortcut *boom* References: In-Reply-To: from "Richard B. Ernst" at "Fri, 27 Nov 1998 10:45:06 -0800" Date: Sun, 29 Nov 1998 19:10:19 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 27th November 1998, "Richard B. Ernst" wrote: >Any suggestions for getting a clean compile? If I have to shutdown to >single-user, my users will just have to live with it, but I'd rather be >fairly certain that whatever steps I take will actually solve the problem >rather then leaving the system in its current state. I recently upgraded a 2.2.5 box to current (a.out). Going elf is an exercise for the reader. >From memory I did: 1) in /usr/src: make buildworld 2) found new config binary in /usr/obj and installed it as config.new 3) in /sys/i386/conf: config.new TOYBOX 4) in /sys/compile/TOYBOX: copied in new bsd.kern.mk and edited out -fformat-extensions because the old compiler hates it. Edited Makefile to only look in . for bsd.kern.mk. make depend all. 5) copyied kernel to /kernel.new 6) test booted /kernel.new (all ok) 7) booted old kernel (back to 2.2.5) 8) in /usr/src: make installworld 9) renamed /kernel.new as /kernel 10) reboot Yeah, I think it went that way. All of this was in multiuser, but if you have people logged in, then make installworld will probably cause them or you some difficulty. I'd suggest single user from the test boot onwards. Have fun! Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 04:36:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25886 for freebsd-current-outgoing; Sun, 29 Nov 1998 04:36:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA25854; Sun, 29 Nov 1998 04:36:08 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id NAA14002; Sun, 29 Nov 1998 13:35:54 +0100 Message-ID: <36613FA9.FC5804A3@we.lc.ehu.es> Date: Sun, 29 Nov 1998 13:35:53 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG CC: freebsd-smp@FreeBSD.ORG Subject: Re: Patches and mptable for Supermicro P6DGU with 440GX chipset References: <21175.912295933@verdi.nethelp.no> Content-Type: multipart/mixed; boundary="------------32FF8BD54608B37B1BBC3BEF" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------32FF8BD54608B37B1BBC3BEF Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit sthaug@nethelp.no wrote: > > I now have FreeBSD-current up and running on a Supermicro P6DGU mother- > board with 440GX chipset, 2 x PII-400 and onboard Adaptec 7890 U2W SCSI. > Getting FreeBSD up and running was relatively painless, and it seems to > be working great so far. The only SMP options I'm currently using are > SMP and APIC_IO. > I don't know if the SMP people are compiling a list of motherboards which run flawlessly (or not). In any case, I can also report on success running FreeBSD 3.0-RELEASE on a Supermicro P6DBU, based on the BX chipset but identical to the P6DGU otherwise, 2xPII-450, 256 MB SDRAM, IBM DDRS-34560 UW HD, 2xIBM DGHS18V U2W HDs. No problems after "make world" using the three disks. Mptable output is included as attachment. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan --------------32FF8BD54608B37B1BBC3BEF Content-Type: text/plain; charset=us-ascii; name="mptable" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mptable" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb4f0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xbd mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f24b0 signature: 'PCMP' base table length: 268 version: 1.4 checksum: 0xab OEM ID: 'INTEL ' Product ID: '440BX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 25 local APIC address: 0xfee00000 extended table length: 16 extended table checksum: 234 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0x183fbff 1 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 2 10 2 16 INT active-lo level 2 11 2 17 INT active-lo level 2 9 2 18 SMI conforms conforms 2 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! --------------32FF8BD54608B37B1BBC3BEF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 06:10:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02936 for freebsd-current-outgoing; Sun, 29 Nov 1998 06:10:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02702 for ; Sun, 29 Nov 1998 06:09:59 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA05324 for current@FreeBSD.ORG; Sun, 29 Nov 1998 15:09:28 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C5DE71534; Sun, 29 Nov 1998 14:38:30 +0100 (CET) Date: Sun, 29 Nov 1998 14:38:30 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory Message-ID: <19981129143830.A12683@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19981128155344.A4298@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from Steven P. Donegan on Sat, Nov 28, 1998 at 01:57:29PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Steven P. Donegan: > Does anyone run SMP/softupdates without problems? I do. "make -j8 world" succeeded without problem. Intel 440FX mb, 64 MB RAM, 2x PPro/200-512. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 06:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03567 for freebsd-current-outgoing; Sun, 29 Nov 1998 06:19:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03558 for ; Sun, 29 Nov 1998 06:19:11 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id JAA10105; Sun, 29 Nov 1998 09:18:58 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199811291418.JAA10105@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: conrads@neosoft.com cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: What happened to "options USERCONFIG_BOOT"? References: In-reply-to: Your message of "Sat, 28 Nov 1998 15:46:50 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 09:18:57 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The latest -current seems to have deprecated "options USERCONFIG_BOOT", but > I've been unable to find out what the new substitute for this is. I certainly > hope we won't have to manually configure PnP devices on each new kernel boot! You now use the new 3rd stage boot loader to pass this information to your running kernel. First, you should remove the USERCONFIG line from the start of the file (probably /kernel.config). Then in /boot/boot.conf: load /kernel load -t userconfig_script /kernel.config autoboot The magic is the 'load -t userconfig_script' command. Again, you need to use the new 3rd stage booter to do this; this doesn't necessarily require the new boot1/boot2 boot blocks, but you might consider that a the same time. You can try the new loader by "booting" /boot/loader and then the commands above. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 06:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05766 for freebsd-current-outgoing; Sun, 29 Nov 1998 06:40:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05760 for ; Sun, 29 Nov 1998 06:40:20 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:df1VC4EhxU5qFjIO7eGmdGkhQj15tLwZ@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id QAA16966; Sun, 29 Nov 1998 16:40:08 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:y/fcEZ0Wg/c54nPBlYoo6sN3DajE4/US@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id QAA98702; Sun, 29 Nov 1998 16:40:04 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811291440.QAA98702@greenpeace.grondar.za> To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: Your message of " Sun, 29 Nov 1998 14:38:30 +0100." <19981129143830.A12683@keltia.freenix.fr> References: <19981128155344.A4298@ns1.adsu.bellsouth.com> <19981129143830.A12683@keltia.freenix.fr> Date: Sun, 29 Nov 1998 16:40:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Steven P. Donegan: > > Does anyone run SMP/softupdates without problems? > > I do. "make -j8 world" succeeded without problem. AOL Giga-Byte GA-586-DX with 2xp5/200, 64MB and mixed-bag of SCSI toys. CURRENT is _really_ recent and ELF'ed. Most partitions are now Softupdate-enabled. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 06:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06364 for freebsd-current-outgoing; Sun, 29 Nov 1998 06:51:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06354; Sun, 29 Nov 1998 06:51:03 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA24073; Mon, 30 Nov 1998 01:50:51 +1100 Date: Mon, 30 Nov 1998 01:50:51 +1100 From: Bruce Evans Message-Id: <199811291450.BAA24073@godzilla.zeta.org.au> To: elias@cnetworks.net, seggers@semyam.dinoco.de Subject: Re: kern_clock.c (was: video mode switching has gone south) Cc: current@FreeBSD.ORG, green@unixhelp.org, phk@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I'm another one who can report somewhat new behaviour : >> >> 1. X now starts up more slowly, with flicker. > >I think for me that's the case, too but is hard to judge. > >> 2. usleep(s), where s=1, 10, 100, 10000 sleeps for about 1 second, >> regardless of argument. It actually sleeps for an average of about half a second. Everything that uses get{micro,nano}{,up}time (mainly timeouts) is broken because the time reported by these functions now lags the actual time by up to about 1 second. Ignore the `force' flag to go back to the previous brokenness which affects relatively few systems. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 07:27:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08337 for freebsd-current-outgoing; Sun, 29 Nov 1998 07:27:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08332 for ; Sun, 29 Nov 1998 07:27:23 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-42.pagesz.net [208.213.126.42]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id KAA31251 for ; Sun, 29 Nov 1998 10:27:30 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id KAA03427; Sun, 29 Nov 1998 10:28:00 -0500 (EST) (envelope-from rhh) Message-ID: <19981129102800.A1657@pagesz.net> Date: Sun, 29 Nov 1998 10:28:00 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: "ldconfig" strangeness on 3.0-RELEASE Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Two things I notice that are rather strange. Are these bugs? =============================================================================== 1) You can completely re-initialize the LD path for ELF, but not for AOUT. An example to illustrate: # ldconfig -elf / # ldconfig -elf -r /var/run/ld-elf.so.hints: search directories: / # ldconfig -aout / # ldconfig -aout -r /var/run/ld.so.hints: !! ===> search directories: /usr/lib/aout:/ 0:-lalias.2.5 => /usr/lib/aout/libalias.so.2.5 1:-latm.2.0 => /usr/lib/aout/libatm.so.2.0 ... 37:-lstdc++.2.0 => /usr/lib/aout/libstdc++.so.2.0 It seems that ldconfig won't let you remove /usr/lib/aout. Why? =============================================================================== 2) In /etc/rc.conf, we have: $ldconfig_paths & $ldconfig_paths_aout but we also have: /etc/ld.so.conf & /etc/ld-elf.so.conf (as documented in the ldconfig(8) man page) as places to store LD paths. So: a) Which should be used? b) What arguments cause "ldconfig" to read the /etc/ld*.so.conf files? It would make sense to have one place to store this information. It'd also be useful to have simple ldconfig arguments that re-read this information, wherever it is stored (something like "ldconfig -i"). =============================================================================== and a few questions: 3) Why aren't these two directories in the default $ldconfig_paths_aout (AOUT) in /etc/rc.conf? AFAIK, they're all AOUT: /usr/lib/aout /usr/lib/compat 4) Why is this directory in the default $ldconfig_paths (ELF)? It's all AOUT: /usr/lib/compat =============================================================================== I'd appreciate any insights. Should the defs in /etc/rc.conf possibly be changed to: ldconfig_paths="`cat /etc/ld-elf.so.conf`" ldconfig_paths_aout="`cat /etc/ld.so.conf`" Thanks, Randall Hopper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 08:39:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12033 for freebsd-current-outgoing; Sun, 29 Nov 1998 08:39:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gravy.kishka.net (dyn-3.blackbox-2.netaxs.com [207.106.60.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12027; Sun, 29 Nov 1998 08:39:20 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (gravy.kishka.net [10.0.0.1]) by gravy.kishka.net (8.9.1/8.8.8) with ESMTP id LAA00310; Sun, 29 Nov 1998 11:38:32 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sun, 29 Nov 1998 11:38:31 -0500 (EST) From: Bryan Liesner To: Bruce Evans cc: elias@cnetworks.net, seggers@semyam.dinoco.de, current@FreeBSD.ORG, green@unixhelp.org, phk@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) In-Reply-To: <199811291450.BAA24073@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, Bruce Evans wrote: <> It actually sleeps for an average of about half a second. <> <> Everything that uses get{micro,nano}{,up}time (mainly timeouts) is broken <> because the time reported by these functions now lags the actual time <> by up to about 1 second. <> <> Ignore the `force' flag to go back to the previous brokenness which <> affects relatively few systems. <> <> Bruce After running a kernel compiled with kern_clock.c revision 1.85 I noticed some problems: Switching to X is sluggish and takes a few seconds where it used to be almost instantaneous. While running X, xlock's screen savers slow down to a crawl, and hitting a key to stop the screen saver can take up to ten seconds. I run xntpd, and got a large amount of "the previous time adjustment did not complete" errors. My system is running a Cyrix 686MX PR266, so this doesn't seem to be limited to the AMD processors. Applying the patch to ignore the 'force' flag seems to have cleared this up. Can anything "bad" happen using this patch? Is there a better solution in the works? ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 09:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13455 for freebsd-current-outgoing; Sun, 29 Nov 1998 09:11:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13418 for ; Sun, 29 Nov 1998 09:11:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA08925; Sun, 29 Nov 1998 18:07:49 +0100 (CET) To: Bryan Liesner cc: Bruce Evans , elias@cnetworks.net, seggers@semyam.dinoco.de, current@FreeBSD.ORG, green@unixhelp.org Subject: Re: kern_clock.c (was: video mode switching has gone south) In-reply-to: Your message of "Sun, 29 Nov 1998 11:38:31 EST." Date: Sun, 29 Nov 1998 18:07:37 +0100 Message-ID: <8923.912359257@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Applying the patch to ignore the 'force' flag seems to have cleared >this up. Can anything "bad" happen using this patch? Is there a better >solution in the works? For all practical puposes, "forcing the force flag", ie, always completing the entire tco_forward() reverts to previous behaviour, and I will probably make the "force" feature a sysctl in a few hours time, since as bruce said, the hardware which it fixes is rather rare, all things considered. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 09:27:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15770 for freebsd-current-outgoing; Sun, 29 Nov 1998 09:27:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iworks.interworks.org (iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15763; Sun, 29 Nov 1998 09:27:11 -0800 (PST) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id LAA00207; Sun, 29 Nov 1998 11:40:48 -0600 (CST) Date: Sun, 29 Nov 1998 11:40:48 -0600 (CST) From: "Daniel M. Eischen" Message-Id: <199811291740.LAA00207@iworks.interworks.org> To: bde@zeta.org.au, majordom@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) Cc: current@FreeBSD.ORG, elias@cnetworks.net, green@unixhelp.org, phk@FreeBSD.ORG, seggers@semyam.dinoco.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After running a kernel compiled with kern_clock.c revision 1.85 I > noticed some problems: > > Switching to X is sluggish and takes a few seconds where it used to be > almost instantaneous. > > While running X, xlock's screen savers slow down to a crawl, and hitting > a key to stop the screen saver can take up to ten seconds. > > I run xntpd, and got a large amount of "the previous time adjustment > did not complete" errors. > > My system is running a Cyrix 686MX PR266, so this doesn't seem to be > limited to the AMD processors. Well, it affects my laptop also (Intel Pentium 200MHz MMX). I do not run xntpd, but I am running the kernel at HZ=1000. Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 11:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26175 for freebsd-current-outgoing; Sun, 29 Nov 1998 11:38:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from head.lvl.ru (head.lvl.ru [195.210.164.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26169 for ; Sun, 29 Nov 1998 11:38:01 -0800 (PST) (envelope-from elias@head.lvl.ru) Received: (from elias@localhost) by head.lvl.ru (8.8.8/8.8.8) id WAA23624; Sun, 29 Nov 1998 22:32:12 +0300 (MSK) (envelope-from elias) Message-ID: <19981129223211.A23613@cnetworks.net> Date: Sun, 29 Nov 1998 22:32:11 +0300 From: Ilya Orehov To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) References: <8923.912359257@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <8923.912359257@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Nov 29, 1998 at 06:07:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 29, 1998 at 06:07:37PM +0100, Poul-Henning Kamp wrote: | | >Applying the patch to ignore the 'force' flag seems to have cleared | >this up. Can anything "bad" happen using this patch? Is there a better | >solution in the works? | | For all practical puposes, "forcing the force flag", ie, always | completing the entire tco_forward() reverts to previous behaviour, | and I will probably make the "force" feature a sysctl in a few Maybe kernel option will be more efficient? | hours time, since as bruce said, the hardware which it fixes is | rather rare, all things considered. | | -- | Poul-Henning Kamp FreeBSD coreteam member | phk@FreeBSD.ORG "Real hackers run -current on their laptop." | "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 13:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03734 for freebsd-current-outgoing; Sun, 29 Nov 1998 13:04:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA03727 for ; Sun, 29 Nov 1998 13:04:22 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 8615 invoked by uid 24); 29 Nov 1998 21:04:13 -0000 Message-Id: <4.1.19981129125203.0092a210@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 29 Nov 1998 12:53:38 -0800 To: Karl Pielorz From: Brian Behlendorf Subject: Re: Strange tagged openings error msg Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <365E8F74.55E1A115@tdx.co.uk> References: <199811271041.CAA07173@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:39 AM 11/27/98 +0000, Karl Pielorz wrote: >It's harmless, but informative... I'm struggling to think of other "harmless, but informative" messages that mandate a message to the console (under standard syslog configuration). Seems like a debugging message that should be turned off by default. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 14:02:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08507 for freebsd-current-outgoing; Sun, 29 Nov 1998 14:02:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08490 for ; Sun, 29 Nov 1998 14:02:51 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id WAA98415; Sun, 29 Nov 1998 22:02:38 GMT Date: Sun, 29 Nov 1998 22:02:38 +0000 (GMT) From: Karl Pielorz To: Brian Behlendorf cc: freebsd-current@FreeBSD.ORG Subject: Re: Strange tagged openings error msg In-Reply-To: <4.1.19981129125203.0092a210@hyperreal.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Brian Behlendorf wrote: > At 11:39 AM 11/27/98 +0000, Karl Pielorz wrote: > >It's harmless, but informative... > > I'm struggling to think of other "harmless, but informative" messages that > mandate a message to the console (under standard syslog configuration). > Seems like a debugging message that should be turned off by default. There may well already be plans around to do this... Maybe it should be called 'mostly harmless'... I wouldn't rate it any more harmfull than the usual "root logged on at yyy" type messages... ;-) - But that's me... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 14:22:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09714 for freebsd-current-outgoing; Sun, 29 Nov 1998 14:22:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09702 for ; Sun, 29 Nov 1998 14:22:25 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id IAA22994 for ; Mon, 30 Nov 1998 08:35:41 +1030 (CST) Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id XYN7VHT0; Mon, 30 Nov 1998 08:41:37 +1030 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.1/8.8.8) with ESMTP id IAA11428 for ; Mon, 30 Nov 1998 08:41:33 +1030 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <3661C695.1F71CEB4@dsto.defence.gov.au> Date: Mon, 30 Nov 1998 08:41:33 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make aout-to-elf failure Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make aout-to-elf fails when you have previously removed ALL a.out ports software (as I do). It fails because just after it has moved all a.out libraries into the a.out subdirectories it trys to run ldconfig (-R I suppose) and the /usr/local/lib/aout directory doesn't exist. I assume it didn't fail for XFree86 as I hadn't removed that as it wasn't a port on the system in question. This is FreeBSD-CURRENT at CTM src-cur 3636. -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 14:24:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09859 for freebsd-current-outgoing; Sun, 29 Nov 1998 14:24:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09854 for ; Sun, 29 Nov 1998 14:24:02 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id IAA23586; Mon, 30 Nov 1998 08:47:56 +1030 (CST) Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id XYN7VHZ2; Mon, 30 Nov 1998 08:53:52 +1030 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.1/8.8.8) with ESMTP id IAA11440; Mon, 30 Nov 1998 08:53:47 +1030 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <3661C973.6EA47509@dsto.defence.gov.au> Date: Mon, 30 Nov 1998 08:53:47 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh CC: CURRENT@FreeBSD.ORG Subject: Re: aha delaying patch works for genuine 1542B References: <365CE867.62F68C8A@dsto.defence.gov.au> <199811262135.OAA88116@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about the long delay in replying. (This is a work machine and I dont have access over the weekend). Dmesg output for my card is: aha0: at 0x234-0x237 irq 11 drq 6 on isa aha0: AHA-1540/1542 64 head BIOS FW Rev. 0.5 (ID=41) SCSI Host Adapter, SCSI ID 7, 16 CCBs I know its not at the standard I/O port. I had to move it due to a conflict. I have got my kernel config file right for this. Also you might want to know that I have 3 very old (quite old) full height SCSI drives on the bus... dmesg output is: da1 at aha0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 3.300MB/s transfers da1: 1351MB (2767245 512 byte sectors: 64H 32S/T 1351C) da3 at aha0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI2 device da3: 3.300MB/s transfers da3: 1813MB (3713130 512 byte sectors: 64H 32S/T 1813C) da4 at aha0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI2 device da4: 3.300MB/s transfers da4: 1812MB (3711990 512 byte sectors: 64H 32S/T 1812C) (these are wired down to their SCSI id. I had a da0 but it finally blew up with all the thrashing I gave it). Warner Losh wrote: > > In message <365CE867.62F68C8A@dsto.defence.gov.au> Matthew Thyer writes: > : The card in question is a genuine Adaptec 1542B and I really > : need it to work as it contains my /usr/src !! > > Which revision? The 1542B that I have doesn't need this delay. The > probe string will tell you the revision. > > : As Graham Menhennitt said: "Could somebody please commit this change" > > Been there, done that. Justin and I have been talking about a better > way to deal with this problem than putting in a magic delay. There > may be another round of patches for the folks with the problem 1542B > cards to test. > > : fuzz: {1} diff /sys/dev/aha/aha.c.orig /sys/dev/aha/aha.c > > diff -u generally produces better results. Also, I have a better > comment stating that a delay to 1000 works, but 10mS is very long in > card time, but very short in probe time. There was a similar delay in > the old driver in places, but I've not looked closely enough to know > if this was one of the places or not. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 14:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11213 for freebsd-current-outgoing; Sun, 29 Nov 1998 14:44:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf28.cruzers.com [205.215.232.28]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA11201 for ; Sun, 29 Nov 1998 14:44:20 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 418 invoked by uid 100); 29 Nov 1998 22:46:37 -0000 Date: Sun, 29 Nov 1998 14:46:37 -0800 To: current@FreeBSD.ORG Subject: Re: USB support Message-ID: <19981129144636.A407@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.9i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > USB support has been committed to FreeBSD Current. Feel free to switch > it on (by uncommenting the last block in GENERIC) and report success or > failure. Ok I turned it on at it said: usbd_match usb0: usbd_attach usbd_new_device bus=0xf07ba000 depth=0 lowspeed=0 usbd_setup_pipe: dev=0xf05ac680 iface=0 ep=0xf05ac69c pipe=0xf05ac688 uhci_open: pipe=0xf05ac600, addr=0, endpt=0 (0) usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=1, protocol=0, maxpacket=64, ls=0 usbd_new_device: new dev (addr 1), dev=0xf05ac680, parent=0xf07b8840 uhub_match, dd=0xf05ac6b8 usb1 at usb0 usbd_transfer_cb: short xfer 1 < 4 usbd_transfer_cb: short xfer 1 < 4 usb1: vendor 0x0000 product 0x0000 (class 9/1) (rev 1.00/1.00) (addr 1) usbd_set_config_no: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_no: setting new config 1 usb_init_hub: getting hub descriptor usbhub_init_hub: selfpowered=1, parent=0, parent->selfpowered=0 usbd_setup_pipe: dev=0xf05ac680 iface=0xf07b6da0 ep=0xf07b7ea0 pipe=0xf0280a24 uhci_open: pipe=0xf05ac480, addr=1, endpt=129 (1) usbd_init_port: adding hub port=1 status=0x0100 change=0x0000 usbd_init_port: adding hub port=2 status=0x0100 change=0x0000 Now what? -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:01:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12784 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:01:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12731; Sun, 29 Nov 1998 15:01:14 -0800 (PST) (envelope-from a0074@netcologne.de) Received: from bsd3.scs-koeln.de (dial4-80.netcologne.de [195.14.233.80]) by mail2.netcologne.de (8.9.1/8.9.1) with SMTP id AAA01553; Mon, 30 Nov 1998 00:00:29 +0100 (MET) X-Ncc-Regid: de.netcologne Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811281644.DAA25934@godzilla.zeta.org.au> Date: Sun, 29 Nov 1998 23:57:02 +0100 (CET) From: "R. Luettgen" To: Bruce Evans Subject: Re: Correction of nfsstat in 3.0 Cc: freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bruce. Thank you for your information. I made this changes in my code and nfsstat runs. If VFS_GENERIC is the wrong one, what's the right one. I also see thet xsysinfo is not able to schow NFS activities. Is this based on t he same problems? Ralf On 28 -Nov-98 Bruce Evans wrote: >>I've a 3.0 RELEASE on my box and it works well. Today I want use nfsstat but >I g >>ot an error message. Here is the patch I make in nfsstat.c . >> >> >>172c172 >>< name[1] = vfc.vfc_typenum; >>--- >>> name[1] = VFS_GENERIC; > >vfc_typenum was broken in some (old, almost as old as 3.0) versions of the >kernel. VFS_GENERIC isn't correct here. It only works if nfs's vfc_typenum >happens to be VFS_GENERIC (= 0). This should never happen for current >kernels, because the type numbers start at 1. > >Bruce ---------------------------------- E-Mail: R. Luettgen Date: 29-Nov-98 Time: 23:57:02 This message was sent by XF-Mail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13404 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:09:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13393 for ; Sun, 29 Nov 1998 15:08:57 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA14531; Sun, 29 Nov 1998 15:08:31 -0800 (PST) Date: Sun, 29 Nov 1998 15:08:30 -0800 (PST) From: "Richard B. Ernst" To: Stephen McKay cc: freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: <199811290910.TAA16558@nymph.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Still no joy on getting -current (from CVS) to compile on a very mixed up system. More suggestions? Thanks, Rick >From make for the kernel: sh-2.00# make loading kernel rearranging symbols symorder: kernel: No such file or directory *** Error code 2 sh-2.00# make buildworld -------------------------------------------------------------- >>> Cleaning up the temporary aout build tree -------------------------------------------------------------- -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- -------------------------------------------------------------- >>> Making mtree -------------------------------------------------------------- -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- mkdir -p /usr/obj/aout/usr/src/tmp cd /usr/src; PATH=/usr/obj/aout/usr/src/tmp/sbin:/usr/obj/aout/usr/src/tmp/usr/sbin:/usr/obj/aout/usr/src/tmp/bin:/usr/obj/aout/usr/src/tmp/usr/bin:/usr/obj/aout/usr/src/tmp/usr/games:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/games BISON_SIMPLE=/usr/obj/aout/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/obj/aout/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/aout/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 hierarchy cd /usr/src/etc; /usr/obj/aout/usr/src/tmp/usr/bin/make distrib-dirs mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /usr/obj/aout/usr/src/tmp/ missing: ./bin (created) missing: ./boot (created) cd /usr/obj/aout/usr/src/tmp/; rm -f /usr/obj/aout/usr/src/tmp/sys; ln -s usr/src/sys sys cd /usr/obj/aout/usr/src/tmp/usr/share/locale; set - `cat /usr/src/etc/locale.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done cd /usr/obj/aout/usr/src/tmp/usr/share/nls; set - `cat /usr/src/etc/locale.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done; rm -rf POSIX; ln -s C POSIX -------------------------------------------------------------- >>> Cleaning up the aout obj tree -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding the aout obj tree -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding aout bootstrap tools -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding tools necessary to build the include files -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding /usr/include -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding bootstrap libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/aout/usr/src/tmp/sbin:/usr/obj/aout/usr/src/tmp/usr/sbin:/usr/obj/aout/usr/src/tmp/bin:/usr/obj/aout/usr/src/tmp/usr/bin:/usr/obj/aout/usr/src/tmp/usr/games:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/games BISON_SIMPLE=/usr/obj/aout/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/obj/aout/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/aout/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/aout/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 bootstrap-libraries cd /usr/src/lib/csu/i386; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/aout/usr/src/tmp/usr/include -c -DCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o crt0.o ld -O crt0.o -x -r crt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/aout/usr/src/tmp/usr/include -fpic -c /usr/src/lib/csu/i386/c++rt0.c cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/aout/usr/src/tmp/usr/include -c -DMCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o gcrt0.o ld -O gcrt0.o -x -r gcrt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/aout/usr/src/tmp/usr/include -c -DCRT0 /usr/src/lib/csu/i386/crt0.c -o scrt0.o ld -O scrt0.o -x -r scrt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/aout/usr/src/tmp/usr/include -c -DMCRT0 /usr/src/lib/csu/i386/crt0.c -o sgcrt0.o ld -O sgcrt0.o -x -r sgcrt0.o install -c -o root -g wheel -m 444 crt0.o c++rt0.o gcrt0.o scrt0.o sgcrt0.o /usr/obj/aout/usr/src/tmp/usr/lib/aout /usr/obj/aout/usr/src/lib/csu/i386 created for /usr/src/lib/csu/i386 cd /usr/src/gnu/usr.bin/cc/libgcc; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/aout/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj echo '#include "i386/xm-freebsd.h"' > config.h echo '#include "i386/xm-freebsd.h"' > tconfig.h echo '#include "i386/freebsd.h"' > tm.h cc -c -O -pipe -I. -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" ^^^^^^^^ Where is this coming from? -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/aout/usr/src/gnu/usr.bin/cc/libgcc/../cc_tools -I/usr/obj/aout/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc1.c mv: _mulsi3.o.tmp: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. sh-2.00# ---------- On Friday, 27th November 1998, "Richard B. Ernst" wrote: Any suggestions for getting a clean compile? If I have to shutdown to On Sun, 29 Nov 1998, Stephen McKay wrote: :>I recently upgraded a 2.2.5 box to current (a.out). Going elf is an exercise :>for the reader. :> :>>From memory I did: :> :>1) in /usr/src: make buildworld :>2) found new config binary in /usr/obj and installed it as config.new To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13792 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:13:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13786 for ; Sun, 29 Nov 1998 15:13:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA20483; Sun, 29 Nov 1998 15:14:22 -0800 (PST) To: "Richard B. Ernst" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-reply-to: Your message of "Sun, 29 Nov 1998 15:08:30 PST." Date: Sun, 29 Nov 1998 15:14:22 -0800 Message-ID: <20475.912381262@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Still no joy on getting -current (from CVS) to compile on a very mixed up > system. More suggestions? Maybe unmix the system by doing a fresh installation before attempting any further to untangle this knot from the inside? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14972 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:24:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14965 for ; Sun, 29 Nov 1998 15:24:25 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA15835; Sun, 29 Nov 1998 15:24:14 -0800 (PST) Date: Sun, 29 Nov 1998 15:24:13 -0800 (PST) From: "Richard B. Ernst" To: "Jordan K. Hubbard" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: <20475.912381262@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've thought about that, and most likely will end up doing so. I'd just wanted to be able to do a behind-the-scenes upgrade so user impact would be minimal. Managed to do that from 2.2.5-->2.2.6-->2.2.7. Is the "Upgrade" option from sysinstall on a booted floppy the way to go, or... ? Thanks ----- On Sun, 29 Nov 1998, Jordan K. Hubbard wrote: :>> Still no joy on getting -current (from CVS) to compile on a very mixed up :>> system. More suggestions? :> :>Maybe unmix the system by doing a fresh installation before attempting :>any further to untangle this knot from the inside? :) :> :>- Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15018 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:26:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15013 for ; Sun, 29 Nov 1998 15:25:53 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA45675; Sun, 29 Nov 1998 18:23:34 -0500 (EST) Date: Sun, 29 Nov 1998 18:23:33 -0500 (EST) From: Chuck Robey To: "Richard B. Ernst" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Richard B. Ernst wrote: > > Still no joy on getting -current (from CVS) to compile on a very mixed up > system. More suggestions? > > > cc -c -O -pipe -I. -DFREEBSD_AOUT > -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/config > -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" > ^^^^^^^^ > Where is this coming from? from gcc-2.7.2.1, exactly as it should be. > -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" > -I/usr/obj/aout/usr/src/gnu/usr.bin/cc/libgcc/../cc_tools > -I/usr/obj/aout/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o > /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc1.c > > mv: _mulsi3.o.tmp: No such file or directory This was a short-lived bug in current. Can you refresh your sources (how broken is your system does cvsup run?) ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:27:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15107 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:27:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15102 for ; Sun, 29 Nov 1998 15:27:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA20580; Sun, 29 Nov 1998 15:28:57 -0800 (PST) To: "Richard B. Ernst" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-reply-to: Your message of "Sun, 29 Nov 1998 15:24:13 PST." Date: Sun, 29 Nov 1998 15:28:57 -0800 Message-ID: <20577.912382137@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is the "Upgrade" option from sysinstall on a booted floppy the way to go, > or... ? I'd say so. In your present state, it's certainly not likely to hurt anything. ;) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15633 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:32:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15626 for ; Sun, 29 Nov 1998 15:32:55 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA16615; Sun, 29 Nov 1998 15:32:43 -0800 (PST) Date: Sun, 29 Nov 1998 15:32:43 -0800 (PST) From: "Richard B. Ernst" To: Chuck Robey cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Various snippage applied... :>> Still no joy on getting -current (from CVS) to compile on a very mixed up :>> system. More suggestions? :>> :>> -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" :>> ^^^^^^^^ :>> Where is this coming from? :> :>from gcc-2.7.2.1, exactly as it should be. Ahh... I was having nightmares that some odd flavor of 2.7.x FreeBSD was being generated. :>> :>> mv: _mulsi3.o.tmp: No such file or directory :> :>This was a short-lived bug in current. Can you refresh your sources :>(how broken is your system does cvsup run?) cvsup appears to be working fine, and I pulled down new sources this morning. Perhaps I've looked at the supfile so long that I am missing something: # $Id: standard-supfile,v 1.12 1997/10/02 00:01:36 jkh Exp $ # # This file contains all of the "CVSup collections" that make up the # FreeBSD-current source tree. # # CVSup (CVS Update Protocol) allows you to download the latest CVS # tree (or any branch of development therefrom) to your system easily # and efficiently (far more so than with sup, which CVSup is aimed # at replacing). If you're running CVSup interactively, and are # currently using an X display server, you should run CVSup as follows # to keep your CVS tree up-to-date: # # cvsup standard-supfile # # If not running X, or invoking cvsup from a non-interactive script, then # run it as follows: # # cvsup -g -L 2 standard-supfile # # You may wish to change some of the settings in this file to better # suit your system: # # host=cvsup.FreeBSD.org # This specifies the server host which will supply the # file updates. Please change this to one of the mirror # sites if possible. (See the "README" file.) You can # override this setting on the command line with cvsup's # "-h host" option. # # base=/usr # This specifies the root where CVSup will store information # about the collections you have transferred to your system. # A setting of "/usr" will generate this information in # /usr/sup. Even if you are CVSupping a large number of # collections, you will be hard pressed to generate more than # ~1MB of data in this directory. You can override the # "base" setting on the command line with cvsup's "-b base" # option. This directory must exist in order to run CVSup. # # prefix=/usr # This specifies where to place the requested files. A # setting of "/usr" will place all of the files requested # in "/usr/src" (e.g., "/usr/src/bin", "/usr/src/lib"). # The prefix directory must exist in order to run CVSup. # Defaults that apply to all the collections *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix # If your network link is a T1 or faster, comment out the following line. #*default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the "src-all" # mega-collection. It includes all of the individual "src-*" collections, # except "src-crypto", "src-eBones", and "src-secure". src-all # These are the individual collections that make up "src-all". If you # use these, be sure to comment out "src-all" above. #src-base #src-bin #src-contrib #src-etc #src-games #src-gnu #src-include #src-kerberosIV #src-lib #src-libexec #src-release #src-sbin #src-share #src-sys #src-tools #src-usrbin #src-usrsbin ## Export-restricted collections. # # Only people in the USA and Canada may fetch these collections. If # you are not in the USA or Canada, please use the collections in the # "secure-supfile" instead. #src-crypto #src-eBones #src-secure To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:35:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15799 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:35:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15794 for ; Sun, 29 Nov 1998 15:35:07 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA16794; Sun, 29 Nov 1998 15:34:57 -0800 (PST) Date: Sun, 29 Nov 1998 15:34:56 -0800 (PST) From: "Richard B. Ernst" To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: <20577.912382137@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, but doing a clean upgrade from the beginning would have made sense, and I wouldn't have any horror stories to tell... I'll be at the console tomorrow, so I can pull down a copy of the 3.0-RELEASE floppy image. ------ On Sun, 29 Nov 1998, Jordan K. Hubbard wrote: :>> Is the "Upgrade" option from sysinstall on a booted floppy the way to go, :>> or... ? :> :>I'd say so. In your present state, it's certainly not likely to hurt :>anything. ;) :> :>- Jordan :> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 15:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16329 for freebsd-current-outgoing; Sun, 29 Nov 1998 15:42:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16292 for ; Sun, 29 Nov 1998 15:41:59 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA45704; Sun, 29 Nov 1998 18:40:10 -0500 (EST) Date: Sun, 29 Nov 1998 18:40:10 -0500 (EST) From: Chuck Robey To: "Richard B. Ernst" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Richard B. Ernst wrote: > :>> mv: _mulsi3.o.tmp: No such file or directory > :> > :>This was a short-lived bug in current. Can you refresh your sources > :>(how broken is your system does cvsup run?) > > cvsup appears to be working fine, and I pulled down new sources this > morning. Perhaps I've looked at the supfile so long that I am missing > something: I don't get src, I get cvs, but it seems ok. The bug I was thinking of was an older one, maybe a month ago (I was guessing you were maybe running from a snap). I saw your mail to Jordan, using 3.0 Release is fine too. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 16:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18327 for freebsd-current-outgoing; Sun, 29 Nov 1998 16:03:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18297 for ; Sun, 29 Nov 1998 16:03:41 -0800 (PST) (envelope-from regnauld@EU.org) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id BAA07577; Mon, 30 Nov 1998 01:15:54 +0100 (CET) (envelope-from regnauld@EU.org) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id BAA20279; Mon, 30 Nov 1998 01:04:04 +0100 (CET) Received: (from uucp@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id BAA26436; Mon, 30 Nov 1998 01:07:11 +0100 (CET) Received: (from regnauld@localhost) by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id PAA11229; Sun, 29 Nov 1998 15:41:09 +0100 (CET) (envelope-from regnauld) Message-ID: <19981129154109.46288@stimpy.prosa.dk> Date: Sun, 29 Nov 1998 15:41:09 +0100 From: Phil Regnauld To: Marius Bendiksen Cc: Robert Nordier , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <50633.911996966@zippy.cdrom.com> <199811251255.OAA16516@ceia.nordier.com> <3.0.5.32.19981125194144.009a08e0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <3.0.5.32.19981125194144.009a08e0@mail.scancall.no>; from Marius Bendiksen on Wed, Nov 25, 1998 at 07:41:44PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marius Bendiksen writes: > > This is a good point, which I forgot in my posting. While the OS/2 EA's > have the advantage of utilising an existing standard, this approach would > offer us the ability to transparently use any filesystem. Though the 255 > character filename requirement should go. We can stick the long filenames > in a seperate file or EA. What's wrong with: 1) mount -t msdos /dev/somefatsystem /mnt/dos 2) vnconfig /dev/vnc0c /mnt/dos/freebsd.fs ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 16:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20028 for freebsd-current-outgoing; Sun, 29 Nov 1998 16:09:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20023 for ; Sun, 29 Nov 1998 16:08:59 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id BAA01530 for ; Mon, 30 Nov 1998 01:08:31 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Mon, 30 Nov 1998 01:08:31 +0100 (CET) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: lynx can't access any http://'s Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With freshly cvsupped current and ports, lynx has stopped working. Both /usr/ports/www/lynx and /usr/ports/www/lynx-current reports: Alert!: Unable to access document lynx: Can't access startpage http://lynx.browser.org I can telnet to the url port 80. Lynx can show local webpages (files), but no http://'s. I use the default lynx.cfg without any changes, lynx and lynx-current compiled unchanged from the port. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 17:49:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00494 for freebsd-current-outgoing; Sun, 29 Nov 1998 17:49:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from send205.yahoomail.com (send205.yahoomail.com [205.180.60.165]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA00387 for ; Sun, 29 Nov 1998 17:49:31 -0800 (PST) (envelope-from kesuki@yahoo.com) Message-ID: <19981130015104.8047.rocketmail@send205.yahoomail.com> Received: from [209.180.227.132] by send205.yahoomail.com; Sun, 29 Nov 1998 17:51:04 PST Date: Sun, 29 Nov 1998 17:51:04 -0800 (PST) From: Ryan Ryttie Subject: Fwd: Undeliverable Message To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1159126505-912390664=:207" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1159126505-912390664=:207 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I tried sending to freebsd-stable but got this bounce in return so... even tho i'm using 2.2.7 could anyone help me? note: forwarded msg attached. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com --0-1159126505-912390664=:207 Content-Type: message/rfc822 Received: from mail.datacraft-asia.com (152.102.113.181) by mta102.yahoomail.com with SMTP; 29 Nov 1998 17:41:43 -0800 Received: from dsi.datacraft-asia.com ([152.102.113.188]) by mail.datacraft-asia.com (Post.Office MTA v3.0 release 0122 ID# 0-34116U100L2S100) with SMTP id AAA356 for ; Mon, 30 Nov 1998 09:47:27 +0800 Received: by dsi.datacraft-asia.com with VINES-ISMTP; Mon, 30 Nov 98 9:41:11 +0800 Date: Mon, 30 Nov 98 9:40:26 SIN Message-ID: X-Priority: 3 (Normal) To: From: Errors-to: Subject: Undeliverable Message X-Incognito-SN: 971 X-Incognito-Version: 4.11.23 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-type: text/plain; charset=ISO-8859-1 Content-Length: 4493 To: iSMTP@DCSG-SIN01@Servers[] Cc: Subject: trouble configuring local network... Message not delivered to recipients below. Press F1 for help with VNM error codes. VNM3043: Ford Leu@Services@DCTW-TPE VNM3043 -- MAILBOX IS FULL The message cannot be delivered because the recipient's mailbox contains the maximum number of messages, as set by the system administrator. The recipient must delete some messages before any other messages can be delivered. The maximum message limit for a user's mailbox is 10,000. The default message limit is 1000 messages. Administrators can set message limits using the Mailbox Settings function available in the Manage User menu (MUSER). When a user's mailbox reaches the limit, the user must delete some of the messages before the mailbox can accept any more incoming messages. ---------------------- Original Message Follows ---------------------- I've tried everything I can think of... here are the msgs and the configs i have and think may help. > netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 209.180.227.6 UGSc 2 0 tun0 localhost localhost UH 0 4 lo0 192.168.1 link#1 UC 0 0 209.180.227.6 209.180.227.215 UH 3 0 tun0 Nov 29 19:04:30 rryttie /kernel: ed1 rev 0 int a irq 11 on pci0:3:0 Nov 29 19:04:30 rryttie /kernel: ed1: address 00:20:78:10:c9:be, type NE2000 (16 bit) Nov 29 19:04:30 rryttie /kernel: ed0 not found at 0x280 127.0.0.1 localhost localhost.my.domain myname.my.domain 192.168.1.1 rryttie rryttie.fm-net.com # FreeBSD System 192.168.1.2 larry larry.fm-net.com # Windows '95 Laptop System hostname="rryttie.fm-net.com" # Set this! network_interfaces="lo0 ed1 tun0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_ed1="inet 192.168.1.1 netmask 255.255.255.0" ### Network routing options: ### defaultrouter="NO" # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="YES" # Set to YES if this host will be a gateway. router_enable="NO" # Set to YES to enable a routing daemon. router="NO" # Name of routing daemon to use if enabled. router_flags="-q" # Flags for routing daemon. mrouted_enable="NO" # Do multicast routing (see /etc/mrouted.conf). mrouted_flags="" # Flags for multicast routing daemon. ipxgateway_enable="NO" # Set to YES to enable IPX routing. ipxrouted_enable="NO" # Set to YES to run the IPX routing daemon. ipxrouted_flags="" # Flags for IPX routing daemon. arpproxy_all="" # replaces obsolete kernel option ARP_PROXYALL. forward_sourceroute="NO" # do source routing (only if gateway_enable is set to "YES") accept_sourceroute="NO" # accept source routed packets to us natd_enable="NO" # Enable natd if firewall_enable. natd_interface="fxp0" # Public interface to use with natd if natd_enable. natd_flags="" # Additional flags for natd. Also it may be of interest that the 'windows' netstat -e which shows the activity of the ethernet device shows that the windows ethernet controller has recieved 8401 bytes sent 552 bytes. has sent and recieved 6 unicast packets has recieved and sent 108 non-unicast packets sent 108 discards claims to have 0 errors and has recieved 117 unknown protocols. I find that interesting since absolutely nothing works and yet obviously the two ethernet cards are talking with eachother. I have tried pings, traceroute ftp and anything else I have enabled to no avail. The windows machine seems to be corectly configured. If any of my configuration files are wrong or if i left any out please let me know the correct settings --- My e-mail address is Personal and Private. Thank you for using bcc in any multiple recipient messages you send to me, and respecting my privacy. > grep FTP.EXE -e Regents @(#) Copyright (c) 1983 The Regents of the Univ- ersity of California. <-- the resuts of greping this program in C:\windows To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message --0-1159126505-912390664=:207-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 18:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05452 for freebsd-current-outgoing; Sun, 29 Nov 1998 18:45:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05435; Sun, 29 Nov 1998 18:45:34 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA09028; Mon, 30 Nov 1998 13:15:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA00692; Mon, 30 Nov 1998 13:15:22 +1030 (CST) Message-ID: <19981130131521.F431@freebie.lemis.com> Date: Mon, 30 Nov 1998 13:15:21 +1030 From: Greg Lehey To: Ryan Ryttie Cc: FreeBSD Questions Subject: Re: Fwd: Undeliverable Message References: <19981130015104.8047.rocketmail@send205.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: <19981130015104.8047.rocketmail@send205.yahoomail.com>; from Ryan Ryttie on Sun, Nov 29, 1998 at 05:51:04PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format autorecovered at freebie.lemis.com] On Sunday, 29 November 1998 at 17:51:04 -0800, Ryan Ryttie wrote: > I tried sending to freebsd-stable but got this bounce in return so... even tho i'm using 2.2.7 could anyone help me? This line is overlong. It looks a lot better like this: > I tried sending to freebsd-stable but got this bounce in return > To: iSMTP@DCSG-SIN01@Servers[] > Cc: > Subject: trouble configuring local network... > > Message not delivered to recipients below. Press F1 for help with VNM > error codes. > > VNM3043: Ford Leu@Services@DCTW-TPE This has nothing to do with FreeBSD-stable. > so... even tho i'm using 2.2.7 could anyone help me? No, why should they? That's what the FreeBSD-questions list is for. If you have trouble with a version of FreeBSD which is neither -current or -stable, questions is your friend > note: forwarded msg attached. I doubt many people would have seen this note in your original message. > I've tried everything I can think of... here are the msgs and the configs > i have and think may help. > >> netstat -r > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 209.180.227.6 UGSc 2 0 tun0 > localhost localhost UH 0 4 lo0 > 192.168.1 link#1 UC 0 0 > 209.180.227.6 209.180.227.215 UH 3 0 tun0 > > Please don't wrap log file contents (just the opposite of normal text :-) > Nov 29 19:04:30 rryttie /kernel: ed1 rev 0 int a irq 11 on pci0:3:0 > Nov 29 19:04:30 rryttie /kernel: ed1: address 00:20:78:10:c9:be, type NE2000 (16 bit) > Nov 29 19:04:30 rryttie /kernel: ed0 not found at 0x280 > > > 127.0.0.1 localhost localhost.my.domain myname.my.domain > 192.168.1.1 rryttie rryttie.fm-net.com # FreeBSD System > 192.168.1.2 larry larry.fm-net.com # Windows '95 Laptop System > This is so corrupted that I can't guess what it was intended to be. > hostnameÿryttie.fm-net.com" # Set this! > network_interfacesÿo0 ed1 tun0" # List of network interfaces (lo0 is > loopback). > ifconfig_lo0ÿnet 127.0.0.1" # default loopback device configuration. > ifconfig_ed1ÿnet 192.168.1.1 netmask 255.255.255.0" > ### Network routing options: ### > defaultrouterÿO" # Set to default gateway (or NO). > static_routesÿ # Set to static route list (or leave empty). > gateway_enableÿES" # Set to YES if this host will be a gateway. > router_enableÿO" # Set to YES to enable a routing daemon. > routerÿO" # Name of routing daemon to use if enabled. > router_flagsÿq" # Flags for routing daemon. > mrouted_enableÿO" # Do multicast routing (see /etc/mrouted.conf). > mrouted_flagsÿ # Flags for multicast routing daemon. > ipxgateway_enableÿO" # Set to YES to enable IPX routing. > ipxrouted_enableÿO" # Set to YES to run the IPX routing daemon. > ipxrouted_flagsÿ # Flags for IPX routing daemon. > arpproxy_allÿ # replaces obsolete kernel option ARP_PROXYALL. > forward_sourcerouteÿO" # do source routing (only if gateway_enable is set to > "YES") > accept_sourcerouteÿO" # accept source routed packets to us > natd_enableÿO" # Enable natd if firewall_enable. > natd_interfaceÿxp0" # Public interface to use with natd if > natd_enable. > natd_flagsÿ # Additional flags for natd. > > Also Isn't it about time you describe your problem? > it may be of interest that the 'windows' netstat -e which shows the > activity of the ethernet device shows that the windows ethernet controller > has recieved 8401 bytes sent 552 bytes. has sent and recieved 6 unicast > packets has recieved and sent 108 non-unicast packets sent 108 discards > claims to have 0 errors and has recieved 117 unknown protocols. Not really. First we need a description of your problem. In general, mistrust the Microsoft machine. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 19:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06956 for freebsd-current-outgoing; Sun, 29 Nov 1998 19:02:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06940 for ; Sun, 29 Nov 1998 19:02:35 -0800 (PST) (envelope-from erikf@visi.com) Received: from odin (h-178-53.mn.mediaone.net [209.32.178.53]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id WAA26820 for ; Sun, 29 Nov 1998 22:02:23 -0500 (EST) Message-ID: <007901be1c0d$ff2acc20$0200a8c0@mn.mediaone.net> From: "Erik Funkenbusch" To: Subject: quake in cvsup build? Date: Sun, 29 Nov 1998 21:03:23 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was noticing today as I was building cvsup that it *appeared* to be building the quake server while building cvsup. Was I misinterpreting things? or is this true? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 19:36:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10619 for freebsd-current-outgoing; Sun, 29 Nov 1998 19:36:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10611 for ; Sun, 29 Nov 1998 19:36:05 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id GAA08719 for current@freebsd.org; Mon, 30 Nov 1998 06:35:55 +0300 (MSK) (envelope-from ache) Message-ID: <19981130063554.A7827@nagual.pp.ru> Date: Mon, 30 Nov 1998 06:35:54 +0300 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Subject: kmem_malloc panic with recent -current Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got kmem_malloc(4096): kmem_map too small: 12664832 total allocated just after reboot. Next reboot goes OK. I have 128Mb of memory, aout kernel, no modules or LKMs -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 20:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15508 for freebsd-current-outgoing; Sun, 29 Nov 1998 20:31:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-180.isl.net [199.3.25.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15501 for ; Sun, 29 Nov 1998 20:30:59 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id WAA01455; Sun, 29 Nov 1998 22:30:18 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199811300430.WAA01455@pyrl.eye> Subject: Re: sio breakage In-Reply-To: from Andy Farkas at "Nov 27, 1998 11:30:38 am" To: andyf@speednet.com.au (Andy Farkas) Date: Sun, 29 Nov 1998 22:30:16 -0600 (CST) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Have someone commited something that i missed that breaks sio? > > >I have a HylaFAX that says that the modem appears to be wedget. > > > > sio is now missing a workaround for certain (16C450?) incompatible > > UARTs, and now honours TCSANOW. Previously it waited for output > > to drain out of the UART before changing the parameters, but > > tcsetattr(... TCSANOW) is supposed to change the parameters > > immediately. > I see these types of messages (when running XF86 3.3.2): > > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > Nov 26 13:39:18 zippy /kernel: sio0: 1 more silo overflow (total 5) > Nov 26 13:39:19 zippy /kernel: sio0: 1 more silo overflow (total 6) > Nov 26 13:39:20 zippy /kernel: sio0: 1 more silo overflow (total 7) At last! Someone is seeing the messages I've been struggling with for months. Now the big question ... is your date/time tracking correctly when not using xntpd and/or when not connected to the internet? My date/time has been running 1/4 speed (and possibly locking up from time to time) for months. -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 20:32:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15585 for freebsd-current-outgoing; Sun, 29 Nov 1998 20:32:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15559; Sun, 29 Nov 1998 20:32:02 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA20359; Mon, 30 Nov 1998 15:31:43 +1100 Date: Mon, 30 Nov 1998 15:31:43 +1100 From: Bruce Evans Message-Id: <199811300431.PAA20359@godzilla.zeta.org.au> To: bde@zeta.org.au, deischen@iworks.interworks.org, majordom@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) Cc: current@FreeBSD.ORG, elias@cnetworks.net, green@unixhelp.org, phk@FreeBSD.ORG, seggers@semyam.dinoco.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My system is running a Cyrix 686MX PR266, so this doesn't seem to be >> limited to the AMD processors. > >Well, it affects my laptop also (Intel Pentium 200MHz MMX). I do >not run xntpd, but I am running the kernel at HZ=1000. Increasing HZ certainly amplifies the old bug. The timecounters will cycle every NTIMECOUNTER/hz seconds, and problems occur if handling a bunch of interrupts (or one heavweight interrupt) ever takes longer than this. You need to increase NTIMECOUNTER to 10 times what would work for HZ=100. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 20:43:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16222 for freebsd-current-outgoing; Sun, 29 Nov 1998 20:43:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16216 for ; Sun, 29 Nov 1998 20:43:21 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-185.ix.netcom.com [209.109.233.185]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id UAA26094 for ; Sun, 29 Nov 1998 20:43:11 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id UAA09938; Sun, 29 Nov 1998 20:43:03 -0800 (PST) Date: Sun, 29 Nov 1998 20:43:03 -0800 (PST) Message-Id: <199811300443.UAA09938@silvia.hip.berkeley.edu> To: current@FreeBSD.ORG Subject: mounting procfs multiple times From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to mount procfs multiple times so ps will work in multiple chroot environments. Unfortunately, it often results in an error like === umount: /chroot/ja-jvim-canna+wnn6-3.0.1.3i/proc: not currently mounted === even though it is shown as mounted by "mount". I can see the processes underneath it and "rm -rf" on that directory fails. Is this supposed to be this way? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 29 21:19:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17616 for freebsd-current-outgoing; Sun, 29 Nov 1998 21:19:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17611; Sun, 29 Nov 1998 21:19:10 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA24322; Mon, 30 Nov 1998 16:18:37 +1100 Date: Mon, 30 Nov 1998 16:18:37 +1100 From: Bruce Evans Message-Id: <199811300518.QAA24322@godzilla.zeta.org.au> To: a0074@netcologne.de, bde@zeta.org.au Subject: Re: Correction of nfsstat in 3.0 Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Thank you for your information. I made this changes in my code and nfsstat runs. >If VFS_GENERIC is the wrong one, what's the right one. The right one is in -current (rev.1.36 of kern/vfs_init.c). This was broken in rev.1.35 of kern/vfs_init.c just in time for the 3.0 release. As a workaround for 3.0, you can try using the nfs LKM. This bug only affects certain sysctls for statically configured vfs's, and in 3.0 only nfs has these sysctls (now ffs has some). >I also see thet xsysinfo is not able to schow NFS activities. Is this based on t >he same problems? Maybe. It seems to work here. Bruc e Index: vfs_init.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_init.c,v retrieving revision 1.35 retrieving revision 1.36 diff -c -2 -r1.35 -r1.36 *** vfs_init.c 1998/10/16 03:55:00 1.35 --- vfs_init.c 1998/10/25 10:52:34 1.36 *************** *** 37,41 **** * * @(#)vfs_init.c 8.3 (Berkeley) 1/4/94 ! * $Id: vfs_init.c,v 1.35 1998/10/16 03:55:00 peter Exp $ */ --- 37,41 ---- * * @(#)vfs_init.c 8.3 (Berkeley) 1/4/94 ! * $Id: vfs_init.c,v 1.36 1998/10/25 10:52:34 bde Exp $ */ *************** *** 279,283 **** vfsp = NULL; - exists = 0; l = &sysctl__vfs; if (vfsconf) --- 279,282 ---- *************** *** 288,308 **** vfc->vfc_typenum = maxvfsconf++; if (vfc->vfc_vfsops->vfs_oid != NULL) { ! oidpp = (struct sysctl_oid **)l->ls_items; ! for (i = l->ls_length; i-- && !exists; oidpp++) ! if (*oidpp == vfc->vfc_vfsops->vfs_oid) exists = 1; - } - if (exists == 0 && vfc->vfc_vfsops->vfs_oid != NULL) { - oidpp = (struct sysctl_oid **)l->ls_items; - for (i = l->ls_length; i--; oidpp++) { - if (*oidpp == NULL || - *oidpp == &sysctl___vfs_mod0 || - *oidpp == &sysctl___vfs_mod1) { - *oidpp = vfc->vfc_vfsops->vfs_oid; - (*oidpp)->oid_number = vfc->vfc_typenum; - sysctl_order_all(); break; } ! } } if (vfsp) --- 287,317 ---- vfc->vfc_typenum = maxvfsconf++; if (vfc->vfc_vfsops->vfs_oid != NULL) { ! /* ! * Attach the oid to the "vfs" node of the sysctl tree if ! * it isn't already there (it will be there for statically ! * configured vfs's). ! */ ! exists = 0; ! for (i = l->ls_length, ! oidpp = (struct sysctl_oid **)l->ls_items; ! i-- != 0; oidpp++) ! if (*oidpp == vfc->vfc_vfsops->vfs_oid) { exists = 1; break; } ! if (exists == 0) ! for (i = l->ls_length, ! oidpp = (struct sysctl_oid **)l->ls_items; ! i-- != 0; oidpp++) { ! if (*oidpp == NULL || ! *oidpp == &sysctl___vfs_mod0 || ! *oidpp == &sysctl___vfs_mod1) { ! *oidpp = vfc->vfc_vfsops->vfs_oid; ! break; ! } ! } ! ! vfc->vfc_vfsops->vfs_oid->oid_number = vfc->vfc_typenum; ! sysctl_order_all(); } if (vfsp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 00:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03071 for freebsd-current-outgoing; Mon, 30 Nov 1998 00:34:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lenka.ph.ipex.cz (lenka.ph.ipex.cz [62.168.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03066 for ; Mon, 30 Nov 1998 00:34:52 -0800 (PST) (envelope-from kan@sti.cz) Received: from linux.sti.cz (linux.sti.cz [62.168.16.129]) by lenka.ph.ipex.cz (8.8.5/IPEX) with ESMTP id JAA17266 for ; Mon, 30 Nov 1998 09:34:47 +0100 Received: from sti.cz (kan.sti.cz [192.168.0.18]) by linux.sti.cz (8.8.7/8.7.3) with ESMTP id KAA01045 for ; Mon, 30 Nov 1998 10:39:22 +0100 Message-ID: <366258D8.FEB15254@sti.cz> Date: Mon, 30 Nov 1998 09:35:37 +0100 From: "Alexander N. Kabaev" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) References: <199811300431.PAA20359@godzilla.zeta.org.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am experiencing this problem on a Pentium II 350MHz box running FreeBSD-current as of November 25th. Applying proposed patch solved the problem. Bruce Evans wrote: > >> My system is running a Cyrix 686MX PR266, so this doesn't seem to be > >> limited to the AMD processors. > > > >Well, it affects my laptop also (Intel Pentium 200MHz MMX). I do > >not run xntpd, but I am running the kernel at HZ=1000. > > Increasing HZ certainly amplifies the old bug. The timecounters will > cycle every NTIMECOUNTER/hz seconds, and problems occur if handling a > bunch of interrupts (or one heavweight interrupt) ever takes longer > than this. You need to increase NTIMECOUNTER to 10 times what would > work for HZ=100. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 00:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04588 for freebsd-current-outgoing; Mon, 30 Nov 1998 00:53:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04582 for ; Mon, 30 Nov 1998 00:53:09 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id IAA23636; Mon, 30 Nov 1998 08:52:56 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma023602; Mon, 30 Nov 98 08:52:52 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id IAA23337; Mon, 30 Nov 1998 08:52:48 GMT From: Geoff Buckingham Message-Id: <199811300852.IAA23337@gti.noc.demon.net> Subject: Re: sio breakage In-Reply-To: <199811300430.WAA01455@pyrl.eye> from Daniel Ortmann at "Nov 29, 98 10:30:16 pm" To: ortmann@sparc.isl.net (Daniel Ortmann) Date: Mon, 30 Nov 1998 08:52:48 +0000 (GMT) Cc: andyf@speednet.com.au, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Reply-To: geoffb@demon.net X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I see these types of messages (when running XF86 3.3.2): > > > > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > > Nov 26 13:39:18 zippy /kernel: sio0: 1 more silo overflow (total 5) > > Nov 26 13:39:19 zippy /kernel: sio0: 1 more silo overflow (total 6) > > Nov 26 13:39:20 zippy /kernel: sio0: 1 more silo overflow (total 7) > > At last! Someone is seeing the messages I've been struggling with for > months. I am curious to know whats going on here, I have been seeing numerous silo overflows while using my laptop (2.2.6+PAO) as a console for a DEC multia/UDB, I had dismissed them as an annoyance probably caused by a slight misconfiguration in /etc/remote. > > Now the big question ... is your date/time tracking correctly when not > using xntpd and/or when not connected to the internet? My date/time > has been running 1/4 speed (and possibly locking up from time to time) > for months. > Timekeeping under PAO allows for suspends etc, it works on my machine but as I have 2.2.6 and PAO I suspect one of these things is both not the same. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 01:16:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06642 for freebsd-current-outgoing; Mon, 30 Nov 1998 01:16:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06637 for ; Mon, 30 Nov 1998 01:16:31 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA08869; Mon, 30 Nov 1998 20:15:55 +1100 Date: Mon, 30 Nov 1998 20:15:55 +1100 From: Bruce Evans Message-Id: <199811300915.UAA08869@godzilla.zeta.org.au> To: geoffb@demon.net, ortmann@sparc.isl.net Subject: Re: sio breakage Cc: andyf@speednet.com.au, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > I see these types of messages (when running XF86 3.3.2): >> > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) >> > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) >> > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) >> > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) This seems to be caused by some video cards and/or X drivers. >I am curious to know whats going on here, I have been seeing numerous >silo overflows while using my laptop (2.2.6+PAO) as a console for a >DEC multia/UDB, I had dismissed them as an annoyance probably caused >by a slight misconfiguration in /etc/remote. Overflows for pccards are certainly caused by the pccard attach routines not supporting fast interrupt handlers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 03:05:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14589 for freebsd-current-outgoing; Mon, 30 Nov 1998 03:05:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ms-18sptg1.kadena.af.mil (ms-18sptg1.kadena.af.mil [132.15.75.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14584; Mon, 30 Nov 1998 03:05:17 -0800 (PST) (envelope-from Wayne.Baety@kadena.af.mil) Received: by ms-18sptg1.kadena.af.mil with Internet Mail Service (5.5.2232.9) id ; Mon, 30 Nov 1998 20:05:04 +0900 Message-ID: <06A98ECF2D0FD211AA240060B0681211F6CBAF@ms-18sptg1.kadena.af.mil> From: Baety Wayne Amn 18CS/SCBD To: "'FreeBSD Current'" , "'FreeBSD Questions'" Subject: CAM Date: Mon, 30 Nov 1998 20:04:59 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where's documentation on properly configuring a kernel for use with this new CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE controller) and am wondering how to enable it in the kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 03:51:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17754 for freebsd-current-outgoing; Mon, 30 Nov 1998 03:51:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rcom.spb.su (rcom.spb.su [193.124.80.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17749 for ; Mon, 30 Nov 1998 03:51:35 -0800 (PST) (envelope-from cust@chat.ru) Received: from smtp.rcom.ru (dyn181.rcom.spb.su [194.220.8.181]) by rcom.spb.su (8.8.5/Relcom-2A/IR) with SMTP id OAA10248 for ;Mon, 30 Nov 1998 14:48:25 +0300 (MSK) X-Authentication-Warning: rcom.spb.su: Host dyn181.rcom.spb.su [194.220.8.181] claimed to be smtp.rcom.ru Date: Mon, 30 Nov 1998 14:47:05 +0300 From: cust X-Mailer: The Bat! (v1.044) UNREG Reply-To: cust Message-ID: <19616.981130@chat.ru> To: freebsd-current@FreeBSD.ORG Subject: wdc1 not found Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Freebsd-current, I nave v 2.2.7 on AMD K6-II 333 32Mb. And I have CD-ROM Samsung SCR-631 r.1.12 on Secondary Master IDE. While booting I have message like this "wcd1 not found at 0x170". This is something strange, couse some days ago all was Ok, and I don't change any config. This is a floating error. Why ??? (Win 95 is on this machine on other partition and all Ok anytime). And the second question - why can I see long filenames on cd9660 (When my CD was working properly, I can't see long filenames). Best regards, Andrew, Spb, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25763 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:29:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25748 for ; Mon, 30 Nov 1998 05:29:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00703; Sun, 29 Nov 1998 01:30:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290930.BAA00703@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Dobloug cc: freebsd-current@FreeBSD.ORG Subject: Re: bootloader In-reply-to: Your message of "08 Nov 1998 20:59:51 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:30:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried to build an elf-kernel, saved it as kernel.elf, and followed > this procedure: > > | Reboot, and at the boot: prompt type '/boot/loader', then abort the > | kernel load and type 'boot kernel.elf'. > > but the boot-loader couldn't find anything on my hd. > > I.e. it reports something like "'/': no such file or directory" when > typing ls, and it can't find either kernel nor kernel.elf. What sort of filesystem(s) do you have on da0? If you change $currdev to one of the slices there, can you see what's on them? > # dmesg | grep ahc > ahc0: rev 0x00 int a irq 19 > on pci0.6.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > da0 at ahc0 bus 0 target 1 lun 0 > da1 at ahc0 bus 0 target 6 lun 0 > (da1:ahc0:0:6:0): tagged openings now 63 > (da0:ahc0:0:1:0): tagged openings now 63 > > The FBSD root is located on da1 (da1s3a) > > When booting, the boot-loader prompt (and hence the environment) > reports 'disk2s3a' which I presume is the equivalent of da1s3a. If you have a single floppy drive, that's right. If you have a chance, and feel like helping debug this, I can make a few suggestions that may help work out what's going on. > I guess the problem is me trying to boot from da1? That's about all I can think of right now; it ought to work though. Does the second disk get listed in the disk summary that's printed when the loader starts? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:30:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25890 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:30:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25871; Mon, 30 Nov 1998 05:30:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00828; Sun, 29 Nov 1998 01:51:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290951.BAA00828@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: jc@irbs.com, mike@smith.net.au, current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Dog Sloooow SMP In-reply-to: Your message of "Sun, 08 Nov 1998 13:43:52 +1100." <199811080243.NAA32642@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:51:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >No idea. I've received verification that fixing this for all 686-class > >CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to > >impact performance there), so the tests are now generalised for the > >entire 686-class. > > It's only OK for MII's because of various `#if 0's and `#ifdef SMP's > that prevent non-OK code from running on MII's. Care to comment on which operations aren't OK? I did ask for this in the review phase, with no feedback. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25913 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:30:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25889 for ; Mon, 30 Nov 1998 05:30:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00570; Sun, 29 Nov 1998 01:14:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290914.BAA00570@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "William R. Somsky" cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 15 Nov 1998 17:35:16 PST." <19981115173516.A4986@halcyon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:14:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, now that we've got the new 3-stage bootloader, and it looks like > it's near to becoming the standard, I've got two questions: > > 1) Where is there documentation on it? In the code. In the list archives. It's still a work in progress, particularly as the Forth component is still being evaluated. There's also an online help system that's mostly functional; I realised that I needed to work out how to sort the common and architecture-specific help together into one file such that subtopic information is in the right place; this is going to need a small program to do the work (any Perl hackers looking for a quick job are invited to apply). Once this is resolved, the 'help' command will probably be enough for most people. Ideally, you won't need to talk to it at all; it should locate your kernel, autoload modules you require, and walk the dog every other evening. > 2) Will we have a DOS/WIN program to install a copy of the new boot0 > when it gets trashed by a Windows install or other "disaster" ;-) I think Robert has already pointed at such an animal. I think you could copy the boot0 file as 'boot.bin' and use the bootinst program that's normally used to install booteasy as well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:30:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25990 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:30:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25936 for ; Mon, 30 Nov 1998 05:30:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00521; Sun, 29 Nov 1998 01:05:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290905.BAA00521@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Shigeyuki FUKUSHIMA cc: freebsd-current@FreeBSD.ORG Subject: Re: mount root problem? on elf kernel In-reply-to: Your message of "Mon, 16 Nov 1998 23:39:23 +0900." <19981116233923X.shige@kuis.kyoto-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:05:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an error in booting ELF kernel and mounting root device. > > I am using 3.0-current(Nov 15, 1998) and ELF kernel on that system. > > I have the following disks on my pc: wd0, da0. > Wd0 only includes DOS slices, and da0 only includes FreeBSD slices. > System BIOS probes IDE -> SCSI. Hence, wd0 is drive C, da0 is drive D. > > BTX loader says: > > Disk 0 Drive A > Disk 1 Drive C > Disk 2 Drive D > > > In my configurations: > > * da0s1a:/boot.config > > /boot/loader > > * da0s1a:/boot/boot.conf > > set rootdev=disk0s1a: This was broken until recently. You should now be ignoring $rootdev, and setting $num_ide_disks to 1. > (...snip... device probing, changing root device, fsck report) > mount: /dev/da0s1a on /: specified device does not match mounted device > Filesystem mount failed, startup aborted > Enter full pathname of shell or RETURN for /bin/sh: > > > And, I modified da0s1a:/etc/fstab as follows: > > # Device Mountpoint FStype Options Dump Pass# > /dev/da0a / ufs rw 1 1 > (...snip...) > > And reboot again. > Then, I have a properly system boot without mounting errors. > > I should use da0a in /etc/fstab instead of da0s1a, right? > Or I have a some mistake in my configulations? I'm not sure if this is related to your BOOTBIAS config option. You should remove it and use $num_ide_disks instead. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:30:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26033 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:30:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26010 for ; Mon, 30 Nov 1998 05:30:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00501; Sun, 29 Nov 1998 01:02:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290902.BAA00501@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jason George cc: "'freebsd-current@freebsd.org'" Subject: Re: Issue with Bad Block scan on fresh disk In-reply-to: Your message of "Wed, 18 Nov 1998 01:07:23 MST." <01BE128F.CD600D40@infomat> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:02:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was building two new 3.0 boxes when I stumbled upon a little nuance > with the bad block scan within the initial sysinstall. I was wondering >if anyone else had noticed this or had any suggestions. First suggestion; wrap your paragraphs. It's a real pain to reply to badly formatted messages. 8( > Here's the scenario: > > I took a new 5.2G Quantum IDE drive out of the sealed static bag, > configured the BIOS to detect it, and booted the 3.0-RELEASE boot > floppy. > > I chose a Custom Install, and Dangerously Dedicated the entire disk, > set it bootable, and flagged a Bad Block Scan. I then sliced the disk. > When it finally came time to do the bad block scan and subsequent > filesystem generation, the bad block scan DID NOT proceed, yet the > filesystem generation and system install did continue to completion. First things first: - Don't use Dangerously Dedicated unless you need it. Hint: you don't. - Don't use the bad block scan unless you are using an old MFM or RLL disk. Almost all IDE and SCSI disks perform their own defect management which is much more reliable and efficient. The bad144 mechanism is entirely unreliable on disks > 2GB. > A little perplexed, I rebooted and followed my normal installation > procedure (Custom Install, Dangerously Dedicated, etc, as above). This > time, the bad block scan ran before the filesystem generation. The > system install continued to completion. At a guess, the first time around the block scan failed silently due to the disk being uninitialised. The second time around, it probably sort-of succeeded, but on a 5GB disk I would have zero confidence in its reliability. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26191 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:32:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26181 for ; Mon, 30 Nov 1998 05:31:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00547; Sun, 29 Nov 1998 01:10:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290910.BAA00547@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: abial@nask.pl (Andrzej Bialecki), freebsd-current@FreeBSD.ORG Subject: Re: Probing devices in bootloader In-reply-to: Your message of "Sat, 16 Nov 1998 12:32:04 +0200." <199811161032.MAA00785@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:10:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Andrzej Bialecki wrote: > > With the advent of the new booloader, I think it's possible now to do > > device probing from inside the bootloader. Let's suppose that each kernel > > module would have a special initialization section, which could be used in > > BTX environment. After all, most probing is just checking for the presence > > of some signatures at given locations, and this can easily be done in BTX > > environment, right? > > Some probing is a fair bit more complex than this (see src/sys/isa/sio.c, > for example). Currently, BTX is not sophisticated enough to handle > various requirements (for instance, the interrupt flag is not virtualized; > and interrupts can't be disabled in ring 3). To do this with the new bootloader, you would probably write a small snippet of Forth (or possibly we could implement a tiny load/exec interface) for device probing, and then ship a separate "probe/ enumerate" module with each driver. Needless to say, this would complicate things significantly. In reality, it is only non-PnP ISA devices that require this sort of support; all other PnP devices are probed (and modules loaded where appropriate) using their corresponding probe mechanisms. I'm not really in favour of adding too much support for legacy ISA; it's dying fast and trivial manual configuration in either the kernel config or the loader script is probably more than adequate. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26667 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:35:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26661 for ; Mon, 30 Nov 1998 05:35:39 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id IAA06275; Mon, 30 Nov 1998 08:34:57 -0500 (EST) Message-ID: <19981130083457.G2147@ns1.adsu.bellsouth.com> Date: Mon, 30 Nov 1998 08:34:57 -0500 From: Christian Kuhtz To: Bruce Evans , geoffb@demon.net, ortmann@sparc.isl.net Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage References: <199811300915.UAA08869@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811300915.UAA08869@godzilla.zeta.org.au>; from Bruce Evans on Mon, Nov 30, 1998 at 08:15:55PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 08:15:55PM +1100, Bruce Evans wrote: > >> > I see these types of messages (when running XF86 3.3.2): > >> > > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > >> > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > >> > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > >> > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > > This seems to be caused by some video cards and/or X drivers. > > >I am curious to know whats going on here, I have been seeing numerous > >silo overflows while using my laptop (2.2.6+PAO) as a console for a > >DEC multia/UDB, I had dismissed them as an annoyance probably caused > >by a slight misconfiguration in /etc/remote. > > Overflows for pccards are certainly caused by the pccard attach routines > not supporting fast interrupt handlers. Is somebody working on this already? If so, is there an estimate as to when the code might be available? Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 05:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26834 for freebsd-current-outgoing; Mon, 30 Nov 1998 05:37:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26829 for ; Mon, 30 Nov 1998 05:37:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00650; Sun, 29 Nov 1998 01:24:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811290924.BAA00650@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Pascal Hofstee , Shawn Ramsey , oZZ!!! , current@FreeBSD.ORG Subject: Re: StarOffice-5.0... In-reply-to: Your message of "Wed, 11 Nov 1998 12:22:55 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Nov 1998 01:24:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, I've got the diffs against relatively fresh current. BTW, I asked > this question on -emulation, but got back a profound silence... Can we/ > should we incorporate this patch, and hide it under a kernel option, say > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux > emulation... A couple of things: - If it's part of our emulation support, it should probably be the default (cringe). - Your patch doesn't preserve the remainder of the commandline arguments. Feel like fixing this and resubmitting it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 06:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03596 for freebsd-current-outgoing; Mon, 30 Nov 1998 06:41:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03578 for ; Mon, 30 Nov 1998 06:41:39 -0800 (PST) (envelope-from mauri@mbp.ee) Received: from nw1.mbp.ee (nw1.mbp.ee [194.204.12.68]) by bsd.mbp.ee (8.9.1/8.9.1) with ESMTP id QAA23064 for ; Mon, 30 Nov 1998 16:41:15 +0200 (EET) (envelope-from mauri@mbp.ee) Message-Id: <199811301441.QAA23064@bsd.mbp.ee> Received: from SERVER/SpoolDir by nw1.mbp.ee (Mercury 1.43); 30 Nov 98 16:41:17 +0200 Received: from SpoolDir by SERVER (Mercury 1.43); 30 Nov 98 16:40:55 +0200 From: "Lauri Laupmaa" Organization: =?ISO-8859-1?Q?ripeva_Kirjastuse_AS?= To: current@FreeBSD.ORG Date: Mon, 30 Nov 1998 16:40:53 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: make aout-to-elf-install & man.7.gz X-mailer: Pegasus Mail for Win32 (v3.01d) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by hub.freebsd.org id GAA03592 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Tha subject says it all... first complains about not finding second. I circumvented the problem by coping some dummy file to man.7.gz ______________ Lauri Laupmaa Äripäev mauri@mbp.ee Ph. +372 66 70 369 +372 50 13 369 Fx. +372 66 70 165 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 07:34:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08520 for freebsd-current-outgoing; Mon, 30 Nov 1998 07:34:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08499; Mon, 30 Nov 1998 07:34:10 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA00461; Tue, 1 Dec 1998 02:33:53 +1100 Date: Tue, 1 Dec 1998 02:33:53 +1100 From: Bruce Evans Message-Id: <199811301533.CAA00461@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: Dog Sloooow SMP Cc: current@FreeBSD.ORG, jc@irbs.com, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >No idea. I've received verification that fixing this for all 686-class >> >CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to >> >impact performance there), so the tests are now generalised for the >> >entire 686-class. >> >> It's only OK for MII's because of various `#if 0's and `#ifdef SMP's >> that prevent non-OK code from running on MII's. > >Care to comment on which operations aren't OK? I did ask for this in >the review phase, with no feedback. Most wrmsr()s and rdmsr()s. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 08:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12267 for freebsd-current-outgoing; Mon, 30 Nov 1998 08:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12258 for ; Mon, 30 Nov 1998 08:28:12 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id QAA16917; Mon, 30 Nov 1998 16:27:56 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma016885; Mon, 30 Nov 98 16:27:42 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id QAA00766; Mon, 30 Nov 1998 16:27:33 GMT From: Geoff Buckingham Message-Id: <199811301627.QAA00766@gti.noc.demon.net> Subject: Re: sio breakage In-Reply-To: <199811300915.UAA08869@godzilla.zeta.org.au> from Bruce Evans at "Nov 30, 98 08:15:55 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 30 Nov 1998 16:27:33 +0000 (GMT) Cc: geoffb@demon.net, ortmann@sparc.isl.net, andyf@speednet.com.au, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Reply-To: geoffb@demon.net X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > I see these types of messages (when running XF86 3.3.2): > >> > > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > >> > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > >> > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > >> > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > > This seems to be caused by some video cards and/or X drivers. > > >I am curious to know whats going on here, I have been seeing numerous > >silo overflows while using my laptop (2.2.6+PAO) as a console for a > >DEC multia/UDB, I had dismissed them as an annoyance probably caused > >by a slight misconfiguration in /etc/remote. > I was assuming the serial interface which is a fixed one breaking out of the back of the Laptop had nothing to do with the PCMCIA, however I have never investigated the internals of a laptop, or even given it much consideration. I can easily find the details of my video chipset and UART if this information would be of help to anyone investigating this, curently this is quite lowdown own list of things that need fixing/building etc. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 09:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15253 for freebsd-current-outgoing; Mon, 30 Nov 1998 09:03:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15248 for ; Mon, 30 Nov 1998 09:03:16 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id SAA26262 for ; Mon, 30 Nov 1998 18:03:00 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl1.philips.com via mwrap (4.0a) id xma026259; Mon, 30 Nov 98 18:03:00 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id SAA15333 for ; Mon, 30 Nov 1998 18:02:59 +0100 (MET) Received: (qmail 69875 invoked by uid 666); 30 Nov 1998 17:03:20 -0000 Date: Mon, 30 Nov 1998 18:03:20 +0100 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: your mail Message-ID: <19981130180320.F67289@hal.mpn.cp.philips.com> References: <19981115173516.A4986@halcyon.com> <199811290914.BAA00570@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: <199811290914.BAA00570@dingo.cdrom.com>; from Mike Smith on Sun, Nov 29, 1998 at 01:14:30AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 29, 1998 at 01:14:30AM -0800, Mike Smith wrote: > There's also an online help system that's mostly functional; I realised that > I needed to work out how to sort the common and architecture-specific help > together into one file such that subtopic information is in the right place; > this is going to need a small program to do the work (any Perl hackers > looking for a quick job are invited to apply). *Raises hand* Care to elaborate on what is needed here? -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 09:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19201 for freebsd-current-outgoing; Mon, 30 Nov 1998 09:43:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19196 for ; Mon, 30 Nov 1998 09:43:08 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id KAA08874; Mon, 30 Nov 1998 10:42:47 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd008848; Mon Nov 30 10:42:39 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id KAA09873; Mon, 30 Nov 1998 10:42:27 -0700 (MST) From: Terry Lambert Message-Id: <199811301742.KAA09873@usr05.primenet.com> Subject: Re: install: strip: No such file or directory To: donegan@quick.net (Steven P. Donegan) Date: Mon, 30 Nov 1998 17:42:27 +0000 (GMT) Cc: ck@ns1.adsu.bellsouth.com, mike@smith.net.au, bde@zeta.org.au, jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG In-Reply-To: from "Steven P. Donegan" at Nov 28, 98 01:57:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying again - this time with make world - not make -j 18 world. > Things are running along fine so far. A few months ago a make -j anything > was a guaranteed SMP/softupdates killer. I'm glad to see that things have > hardened a bit. > > Does anyone run SMP/softupdates without problems? I run them together without problems at home. I have a number of scheduler hacks I've been trying out, but I don't think they will effect this, since I still don't allow more than one process into the sync code at one time. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 09:52:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19904 for freebsd-current-outgoing; Mon, 30 Nov 1998 09:52:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19876 for ; Mon, 30 Nov 1998 09:51:58 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t2o29p107.telia.com [194.236.214.227]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id SAA00007; Mon, 30 Nov 1998 18:51:26 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id SAA00361; Mon, 30 Nov 1998 18:41:25 +0100 (CET) (envelope-from johan@granlund.nu) Date: Mon, 30 Nov 1998 18:41:25 +0100 (CET) From: Johan Granlund To: freebsd-current@FreeBSD.ORG cc: Andy Farkas , bde@zeta.org.au, freebsd-current@FreeBSD.ORG Subject: Re: sio breakage In-Reply-To: <199811300430.WAA01455@pyrl.eye> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Have someone commited something that i missed that breaks sio? > > > >I have a HylaFAX that says that the modem appears to be wedget. > > > > > > sio is now missing a workaround for certain (16C450?) incompatible > > > UARTs, and now honours TCSANOW. Previously it waited for output > > > to drain out of the UART before changing the parameters, but > > > tcsetattr(... TCSANOW) is supposed to change the parameters > > > immediately. > Phks commit today to kern_clock solved my problem with Faxgetty from HylaFAX. Only a recompile of the kernel and no fiddling with kern.timecounter.method was nesserary. I have no problems with "calcru negative..." messages on this machine. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 10:17:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23320 for freebsd-current-outgoing; Mon, 30 Nov 1998 10:17:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spa.kuis.kyoto-u.ac.jp (lab4imgw.kuis.kyoto-u.ac.jp [130.54.23.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23301 for ; Mon, 30 Nov 1998 10:17:48 -0800 (PST) (envelope-from shige@kuis.kyoto-u.ac.jp) Received: from localhost (sirahama.kuis.kyoto-u.ac.jp [130.54.22.177]) by spa.kuis.kyoto-u.ac.jp (8.8.8/3.6Wspa) with ESMTP id DAA25410; Tue, 1 Dec 1998 03:13:53 +0900 (JST) To: mike@smith.net.au Cc: freebsd-current@FreeBSD.ORG Cc: shige@kuis.kyoto-u.ac.jp Subject: Re: mount root problem? on elf kernel In-Reply-To: Your message of "Sun, 29 Nov 1998 01:05:37 -0800" <199811290905.BAA00521@dingo.cdrom.com> References: <199811290905.BAA00521@dingo.cdrom.com> X-Mailer: Mew version 1.93 on Emacs 20.3 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-Prom-Mew: Prom-Mew 1.93 (procmail reader for Mew) X-URL: http://www.yuasa.kuis.kyoto-u.ac.jp/~shige/ X-fingerprint: C8 BD 6A A7 CF FF 74 88 A4 B2 CC 5F C7 61 5C 9A X-Pgp-Public-Key-URL: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9 X-Face-Version: X-Face utility v1.3.2 - "The Fool On The Hill" X-Face: 34/1@t8]M!wP}sAw$~XQMzl5'O=lCIM]8=_8CE,|S)Vs4Wy@tU~A'wRi\lgWh-o&'|:zg>Gc?0?{^jo8(|5'Tg`yBH81.:!N9tSq*Sp6>C0q@{|&+FaM;R;KkoW1jA?QIWQ3:gNq {O%`:ww Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981201031720R.shige@kuis.kyoto-u.ac.jp> Date: Tue, 01 Dec 1998 03:17:20 +0900 (JST) From: Shigeyuki FUKUSHIMA X-Dispatcher: imput version 980905(IM100) Lines: 28 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Mike Smith Date: Sun, 29 Nov 1998 01:05:37 -0800 Title: Re: mount root problem? on elf kernel Message-ID: <199811290905.BAA00521@dingo.cdrom.com> > > I should use da0a in /etc/fstab instead of da0s1a, right? > > Or I have a some mistake in my configulations? > > I'm not sure if this is related to your BOOTBIAS config option. You > should remove it and use $num_ide_disks instead. I make world 3.0-current(Nov 30, 1998). And, I tried $num_ide_disks variable in /boot/boot.conf with the following /etc/fstab. --- # Device Mountpoint FStype Options Dump Pass# /dev/da0s1a / ufs rw 1 1 (...snip...) --- As result, I have a properly system boot without mounting errors. Thank you. --------- Shigeyuki FUKUSHIMA Dept. of Information Science, Kyoto Univ., JAPAN PGP Public Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 11:10:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29838 for freebsd-current-outgoing; Mon, 30 Nov 1998 11:10:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29815 for ; Mon, 30 Nov 1998 11:10:20 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id UAA00840; Mon, 30 Nov 1998 20:09:23 +0100 Message-ID: <3662ED63.916C075E@we.lc.ehu.es> Date: Mon, 30 Nov 1998 20:09:23 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: does "da" support 640MB magneto-optical disks? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In other words: does the CAM "da" device support disks with block sizes other than 512 bytes? For example, the MO disks with 640MB capacity have blocks of 2048 bytes. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 12:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12046 for freebsd-current-outgoing; Mon, 30 Nov 1998 12:39:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12030; Mon, 30 Nov 1998 12:39:44 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id MAA01172; Mon, 30 Nov 1998 12:39:42 -0800 (PST) (envelope-from ulf) Message-ID: <19981130123942.A856@TelcoSucks.org> Date: Mon, 30 Nov 1998 12:39:42 -0800 From: Ulf Zimmermann To: current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: [ulf@Alameda.net: Re: CAM] Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to copy the lists on it. ----- Forwarded message from Ulf Zimmermann ----- Date: Mon, 30 Nov 1998 12:36:59 -0800 From: Ulf Zimmermann To: Baety Wayne Amn 18CS/SCBD Subject: Re: CAM On Mon, Nov 30, 1998 at 08:04:59PM +0900, Baety Wayne Amn 18CS/SCBD wrote: > > Where's documentation on properly configuring a kernel for use with this new > CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE > controller) and am wondering how to enable it in the kernel. CAM does not support the Mylex DAC960 Raid controllers. I have been on and off working on a driver, but I am stuck about understanding certain kernel things and I am low on time right now. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 ----- End forwarded message ----- -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 14:03:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22012 for freebsd-current-outgoing; Mon, 30 Nov 1998 14:03:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21985; Mon, 30 Nov 1998 14:03:41 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA26316; Mon, 30 Nov 1998 23:03:11 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id VAA00623; Mon, 30 Nov 1998 21:19:20 GMT Message-ID: <19981130211920.23801@breizh.prism.uvsq.fr> Date: Mon, 30 Nov 1998 21:19:20 +0000 From: Nicolas Souchu To: aw1@stade.co.uk Cc: current@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: kernel make failure in smbus References: <199811222006.MAA00385@rah.star-gate.com> <199811222106.XAA00350@greenpeace.grondar.za> <19981124025011.A832@stade.co.uk> <19981127000541.21781@breizh.prism.uvsq.fr> <19981128205032.A788@stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19981128205032.A788@stade.co.uk>; from Adrian Wontroba on Sat, Nov 28, 1998 at 08:50:32PM +0000 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 28, 1998 at 08:50:32PM +0000, Adrian Wontroba wrote: > >On Fri, Nov 27, 1998 at 12:05:41AM +0000, Nicolas Souchu wrote: >> I thought it was solved when we returned to the previous >> check_for_i2c_devices() behaviour. What about trying the following patch >> which disables iic/smb support? > >With a 3.0-CURRENT system cvsupped at 0600 GMT today and and freshly >installed without the patch, my tv card is mis-identified. > >With a kernel containing your patch, the card is identified correctly. >I'm writing this listening to the radio with xmradio (8-) > >Significant part of a diff on dmesg output: > > bktr0: rev 0x12 int a irq 15 on pci0.15.0 >-bti2c0: >-iicbb0: on bti2c0 >-iicbus0: on iicbb0 master-only >-Probing for devices on iicbus0: <80> <81> >-smbus0: on bti2c0 >-IMS TV Turbo, Philips FR1236 NTSC FM tuner. >+Hauppauge WinCast/TV, Philips FR1216 PAL tuner, msp3400c stereo. Thanks! I believe it is due to my initial probe that must let the Hauppauge EEprom in an invalide state. I'll see. > >-- >Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 14:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25490 for freebsd-current-outgoing; Mon, 30 Nov 1998 14:33:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25483 for ; Mon, 30 Nov 1998 14:33:17 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id OAA27985; Mon, 30 Nov 1998 14:33:04 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 30 Nov 1998 14:33:03 -0800 (PST) From: Doug White To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: weird anomaly In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Alfred Perlstein wrote: > Has anyone noticed this recently: > > Ok this is odd, i just upgraded to a ELF kernel, from an aout kernel > ~nov 12th. Everything is fine so far except one oddity I noticed. > > x11amp is REALLY weird. I have the FreeBSD ELF version downloaded from > www.opensound.com and i'm using Luigi's drivers, MSS audio. (aout version > also misbehaves the same way) > > Sound plays fine, however the app itself lags terribly. Meaning i click > on it and drag it and it pauses for a second or two then zips over to > where I dragged it. It's quite an amusing effect. Dialog boxes appear > about 3 seconds after i try to bring one up. What speed of machine? x11amp runs fine on my month-old -CURRENT PPro200 box. I have a Crystal-based card, not a Yamaha, and you have lots of kernel options turned on. xaudio likes to drag on this P100 with Crystal audio, btw. Perhaps your machine can't quite handle it? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 14:44:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26704 for freebsd-current-outgoing; Mon, 30 Nov 1998 14:44:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26697 for ; Mon, 30 Nov 1998 14:44:14 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA03637; Mon, 30 Nov 1998 17:47:06 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 30 Nov 1998 17:47:06 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Doug White cc: current@FreeBSD.ORG Subject: Re: weird anomaly In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, Doug White wrote: > On Wed, 25 Nov 1998, Alfred Perlstein wrote: > > > Has anyone noticed this recently: > > > > Ok this is odd, i just upgraded to a ELF kernel, from an aout kernel > > ~nov 12th. Everything is fine so far except one oddity I noticed. > > > > x11amp is REALLY weird. I have the FreeBSD ELF version downloaded from > > www.opensound.com and i'm using Luigi's drivers, MSS audio. (aout version > > also misbehaves the same way) > > > > Sound plays fine, however the app itself lags terribly. Meaning i click > > on it and drag it and it pauses for a second or two then zips over to > > where I dragged it. It's quite an amusing effect. Dialog boxes appear > > about 3 seconds after i try to bring one up. > > What speed of machine? x11amp runs fine on my month-old -CURRENT > PPro200 box. I have a Crystal-based card, not a Yamaha, and you have lots > of kernel options turned on. > > xaudio likes to drag on this P100 with Crystal audio, btw. Perhaps your > machine can't quite handle it? This isn't a problem for me anymore, someone fixed kern_clock.c and now things are peachy again. Something broke usleep it seems and since x11amp is "CPU friendly" and yeilds a lot it was severly messed up for a few days. thanks for the concern and -current is top notch as usual. thanks, -Alfred > > Doug White To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 15:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00670 for freebsd-current-outgoing; Mon, 30 Nov 1998 15:17:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00663 for ; Mon, 30 Nov 1998 15:17:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA06193; Mon, 30 Nov 1998 15:14:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811302314.PAA06193@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: geoffb@demon.net cc: bde@zeta.org.au (Bruce Evans), ortmann@sparc.isl.net, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage In-reply-to: Your message of "Mon, 30 Nov 1998 16:27:33 GMT." <199811301627.QAA00766@gti.noc.demon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Nov 1998 15:14:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >> > I see these types of messages (when running XF86 3.3.2): > > >> > > > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > > >> > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > > >> > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > > >> > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > > > > This seems to be caused by some video cards and/or X drivers. > > > > >I am curious to know whats going on here, I have been seeing numerous > > >silo overflows while using my laptop (2.2.6+PAO) as a console for a > > >DEC multia/UDB, I had dismissed them as an annoyance probably caused > > >by a slight misconfiguration in /etc/remote. > > > I was assuming the serial interface which is a fixed one breaking out of > the back of the Laptop had nothing to do with the PCMCIA, You're quite correct; it doesn't. There's *something* holding up both your interrupt handlers and the tty soft interrupt; maybe even possibly the same thing that causes the "calcru: negative time for ..." messages. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 15:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02650 for freebsd-current-outgoing; Mon, 30 Nov 1998 15:29:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02642 for ; Mon, 30 Nov 1998 15:29:12 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id PAA28472; Mon, 30 Nov 1998 15:29:00 -0800 (PST) Date: Mon, 30 Nov 1998 15:29:00 -0800 (PST) From: "Richard B. Ernst" To: freebsd-current@FreeBSD.ORG Subject: Re: 2.2.7-->current shortcut *boom* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The weirdness continues: I booted to a 3.0-RELEASE floppy, selected "Upgrade" and the "Developer" distribution. Exactly the same problem with _mulsi3.o.tmp and trying to make the kernel (symorder kernel: no such file or directory). What has happened to my box? *sniff* Hrm... I had just moved it next to a Windows machine.... :) Any other suggestions? On Sun, 29 Nov 1998, Chuck Robey wrote: :>On Sun, 29 Nov 1998, Richard B. Ernst wrote: :> :>> :>> mv: _mulsi3.o.tmp: No such file or directory :>> :> :>> :>This was a short-lived bug in current. Can you refresh your sources :>> :>(how broken is your system does cvsup run?) :>> :>> cvsup appears to be working fine, and I pulled down new sources this :>> morning. Perhaps I've looked at the supfile so long that I am missing :>> something: :> :>I don't get src, I get cvs, but it seems ok. The bug I was thinking of :>was an older one, maybe a month ago (I was guessing you were maybe :>running from a snap). I saw your mail to Jordan, using 3.0 Release is :>fine too. :> :> :>----------------------------+----------------------------------------------- :>Chuck Robey | Interests include any kind of voice or data :>chuckr@glue.umd.edu | communications topic, C programming, and Unix. :>213 Lakeside Drive Apt T-1 | :>Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) :>(301) 220-2114 | and jaunt (NetBSD). :>----------------------------+----------------------------------------------- :> :> :> :> +--[ Richard B. Ernst ]--[ Las Vegas, NV ]--[ telnet://legendz.com 1234 ]--+ | | | "At the source of every error which is blamed on the computer you will | | find at least two human errors, including the error of blaming it on the | | computer." {Unknown} | | | +---[ http://www.wizard.com/~rbernst ]----------[ rbernst@wizard.com ]-----+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 16:01:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07384 for freebsd-current-outgoing; Mon, 30 Nov 1998 16:01:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07379 for ; Mon, 30 Nov 1998 16:00:58 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA08402; Mon, 30 Nov 1998 15:59:01 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma008396; Mon, 30 Nov 98 15:58:38 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA15709; Mon, 30 Nov 1998 15:58:38 -0800 (PST) From: Archie Cobbs Message-Id: <199811302358.PAA15709@bubba.whistle.com> Subject: Re: Resend In-Reply-To: <199811251810.KAA01308@dingo.cdrom.com> from Mike Smith at "Nov 25, 98 10:10:29 am" To: mike@smith.net.au (Mike Smith) Date: Mon, 30 Nov 1998 15:58:38 -0800 (PST) Cc: info@highwind.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > It appears to do the correct thing in the nonblocking case; this points > the finger at your application. A ktrace should resolve this question pretty quickly. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 16:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15055 for freebsd-current-outgoing; Mon, 30 Nov 1998 16:39:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15046 for ; Mon, 30 Nov 1998 16:39:14 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id QAA15076; Mon, 30 Nov 1998 16:39:00 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA19831; Mon, 30 Nov 1998 16:39:00 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 30 Nov 1998 16:39:00 -0800 (PST) Message-Id: <199812010039.QAA19831@vashon.polstra.com> To: erikf@visi.com Subject: Re: quake in cvsup build? Newsgroups: polstra.freebsd.current In-Reply-To: <007901be1c0d$ff2acc20$0200a8c0@mn.mediaone.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <007901be1c0d$ff2acc20$0200a8c0@mn.mediaone.net>, Erik Funkenbusch wrote: > I was noticing today as I was building cvsup that it *appeared* to be > building the quake server while building cvsup. Was I misinterpreting > things? or is this true? Damn, the secret is out. CVSup is really just a hacked up version of quake. ;-) One of the components of the Modula-3 system is a little language called "quake". It has nothing to do with the game, and it predated the game by several years. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 16:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16894 for freebsd-current-outgoing; Mon, 30 Nov 1998 16:52:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16888 for ; Mon, 30 Nov 1998 16:52:08 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA12406; Mon, 30 Nov 1998 17:51:47 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812010051.RAA12406@panzer.plutotech.com> Subject: Re: does "da" support 640MB magneto-optical disks? In-Reply-To: <3662ED63.916C075E@we.lc.ehu.es> from =?ISO-8859-1?Q?Jos=E9_M=AA_Alcaide?= at "Nov 30, 98 08:09:23 pm" To: jose@we.lc.ehu.es (José Mª Alcaide) Date: Mon, 30 Nov 1998 17:51:47 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG José Mª Alcaide wrote... > In other words: does the CAM "da" device support disks with > block sizes other than 512 bytes? For example, the MO disks > with 640MB capacity have blocks of 2048 bytes. It should support those devices just fine. It uses Bruce's slice code to deal with non-512 byte sector sizes. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 17:51:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24456 for freebsd-current-outgoing; Mon, 30 Nov 1998 17:51:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24449 for ; Mon, 30 Nov 1998 17:51:41 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id TAA15827; Mon, 30 Nov 1998 19:51:12 -0600 (CST) Message-ID: <19981130195111.J4374@futuresouth.com> Date: Mon, 30 Nov 1998 19:51:11 -0600 From: "Matthew D. Fuller" To: Mike Smith , geoffb@demon.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: sio breakage References: <199811301627.QAA00766@gti.noc.demon.net> <199811302314.PAA06193@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811302314.PAA06193@dingo.cdrom.com>; from Mike Smith on Mon, Nov 30, 1998 at 03:14:30PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ big CC: scissors workout ] On Mon, Nov 30, 1998 at 03:14:30PM -0800, Mike Smith woke me up to tell me: > > > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) ... > > I was assuming the serial interface which is a fixed one breaking out of > > the back of the Laptop had nothing to do with the PCMCIA, > > You're quite correct; it doesn't. There's *something* holding up both > your interrupt handlers and the tty soft interrupt; maybe even possibly the > same thing that causes the "calcru: negative time for ..." messages. How far does that extend? I get sio overflows all the time on my laptop; it just has a hardwired SLIP connection. I've got it down to 19200 baud (cables worked just fine at 57,6, couldn't tell at 115,2) and it still gets overflows every few minutes when I'm doing anything that passed data across the serial line. I assumed it was just the processor power (486 SLC/25) being slightly less than up to the higher data rates. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 19:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05344 for freebsd-current-outgoing; Mon, 30 Nov 1998 19:30:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05337 for ; Mon, 30 Nov 1998 19:30:32 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA20453; Tue, 1 Dec 1998 14:30:14 +1100 Date: Tue, 1 Dec 1998 14:30:14 +1100 From: Bruce Evans Message-Id: <199812010330.OAA20453@godzilla.zeta.org.au> To: geoffb@demon.net, mike@smith.net.au Subject: Re: sio breakage Cc: andyf@speednet.com.au, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu, ortmann@sparc.isl.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I was assuming the serial interface which is a fixed one breaking out of >> the back of the Laptop had nothing to do with the PCMCIA, > >You're quite correct; it doesn't. There's *something* holding up both >your interrupt handlers and the tty soft interrupt; maybe even possibly the >same thing that causes the "calcru: negative time for ..." messages. something() { asm("cli"); asm("sti"); } This disables interrupts for 0 user instructions, but if a pagefault occurs for reading the "sti" instruction, it disables interrupts for hundreds, thousands or millions of kernel instructions. something_more_likely() { asm("cli"); var = 0; asm("sti"); } This disables interrupts for 1 or 2 user instructions, but if a pagefault occurs for reading a critical instruction or more likely for accessing the variable, it disables interrupts for hundreds, thousands or millions of kernel instructions. Fixes: kernel: send a fatal signal to applications that do this. applications: don't do this. If interrupts must be disabled, then all critical code and data must be within one page. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 19:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06709 for freebsd-current-outgoing; Mon, 30 Nov 1998 19:50:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06700 for ; Mon, 30 Nov 1998 19:50:21 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA24761 for ; Mon, 30 Nov 1998 22:50:09 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22956; Mon, 30 Nov 1998 22:50:08 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA12951 for freebsd-current@freebsd.org; Mon, 30 Nov 1998 22:50:08 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812010350.WAA12951@bb01f39.unx.sas.com> Subject: mtree -d (diff to include symlinks) To: freebsd-current@FreeBSD.ORG Date: Mon, 30 Nov 1998 22:50:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Please read the whole msg. It appears that mtree doesn't correctly parse all it output formats correctly on input :-( I'm trying to use mtree to create a mapping of a directory structure that contains symlinks. 'mtree -d' will give me all the directories, but not the info for the symlinks. Without the -d, I am inundated with information concerning the files in the structure that I don't care about.. Thus, I've added the following 2 options to mtree: -P cause mtree to use ftsoptions = FTS_PHYSICAL so information is returned about the link, and not the link target. (See 1.3.8.3 Mon Mar 9 12:32:09 1998 UTC by ache) The comment does not say why the 'FTS_PHYSICAL -> FTS_LOGICAL' change was done. -l link flag. specifies that we want output about symlinks to be written out when running with the -d option. With the above additions, I can now use mtree to create the following map file: $ /usr/src/usr.sbin/mtree/mtree -cdilnPp . # user: jwd # machine: magenta.pc.sas.com # tree: /usr/home/jwd/bsd # date: Mon Sep 29 11:18:19 1997 /set type=dir uid=227 gid=0 mode=0755 nlink=1 . nlink=4 size=512 time=875531854.0 a nlink=3 size=512 time=875531884.0 symlink2b size=4 time=875531823.0 link=../b dir_in_a nlink=2 size=512 time=875500662.0 .. .. b nlink=3 size=512 time=875531891.0 symlink2a size=4 time=875531838.0 link=../a dir_in_b nlink=2 size=512 time=875500662.0 .. .. .. The following are the diffs to mtree.c and create.c ... Would someone please review these and commit them? My commentary above can be used as part of the commit msg. If this is committed, I will also update the man page. If someone knows of a better way to do this, I'm all ears! :-) Thanks! John ps: Ok, I quit for the evenning. If I feed the above back into mtree, it creates 'a', then 'b' under 'a' instead of beside it, and the symlinks are real directories instead of symlinks. Looks like I need to look at the input parsing... ie: mtree -cdilnPp bsd | /usr/sbin/mtree -dUp /tmp/bsd yields: find bsd -exec file {} \; bsd: directory bsd/a: directory bsd/a/symlink2b: directory <--- Wrong bsd/a/symlink2b/dir_in_a: directory <--- Wrong, didn't .. bsd/a/b: directory <--- " bsd/a/b/symlink2a: directory <--- " bsd/a/b/symlink2a/dir_in_b: directory <--- " instead of:find bsd -exec file {} \; bsd: directory bsd/a: directory bsd/a/dir_in_a: directory bsd/a/symlink2b: symbolic link to ../b <--- Correct bsd/b: directory bsd/b/dir_in_b: directory bsd/b/symlink2a: symbolic link to ../a --- mtree.c.orig +++ mtree.c @@ -58,7 +58,7 @@ extern long int crc_total; int ftsoptions = FTS_LOGICAL; -int cflag, dflag, eflag, iflag, nflag, rflag, sflag, uflag, Uflag; +int cflag, dflag, eflag, iflag, lflag, nflag, rflag, sflag, uflag, Uflag; u_int keys; char fullpath[MAXPATHLEN]; @@ -75,7 +75,7 @@ dir = NULL; keys = KEYDEFAULT; - while ((ch = getopt(argc, argv, "cdef:iK:k:np:rs:Uux")) != -1) + while ((ch = getopt(argc, argv, "cdef:iK:k:lnPp:rs:Uux")) != -1) switch((char)ch) { case 'c': cflag = 1; @@ -104,8 +104,14 @@ if (*p != '\0') keys |= parsekey(p, NULL); break; + case 'l': + lflag = 1; + break; case 'n': nflag = 1; + break; + case 'P': + ftsoptions = FTS_PHYSICAL; break; case 'p': dir = optarg; --- create.c.orig +++ create.c @@ -60,7 +60,7 @@ extern long int crc_total; extern int ftsoptions; -extern int dflag, iflag, nflag, sflag; +extern int dflag, iflag, lflag, nflag, sflag; extern u_int keys; extern char fullpath[MAXPATHLEN]; extern int lineno; @@ -97,6 +97,10 @@ if (iflag) indent = p->fts_level * 4; switch(p->fts_info) { + case FTS_SL: + case FTS_SLNONE: + if (!lflag) + break; case FTS_D: if (!dflag) (void)printf("\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 19:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06920 for freebsd-current-outgoing; Mon, 30 Nov 1998 19:52:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06909 for ; Mon, 30 Nov 1998 19:52:43 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id OAA05782; Tue, 1 Dec 1998 14:16:31 +1030 (CST) Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id XYN7V68S; Tue, 1 Dec 1998 14:22:29 +1030 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.1/8.8.8) with ESMTP id OAA13368; Tue, 1 Dec 1998 14:22:24 +1030 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <366367F7.9BB67DF4@dsto.defence.gov.au> Date: Tue, 01 Dec 1998 14:22:23 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Leif Neland CC: freebsd-current@FreeBSD.ORG Subject: Re: lynx can't access any http://'s References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you edited /usr/local/etc/lynx.cfg and set the proxies if you require them ? This is for /usr/ports/www/lynx #http_proxy:http://some.server.dom:port/ #https_proxy:http://some.server.dom:port/ #ftp_proxy:http://some.server.dom:port/ #gopher_proxy:http://some.server.dom:port/ #news_proxy:http://some.server.dom:port/ #newspost_proxy:http://some.server.dom:port/ #newsreply_proxy:http://some.server.dom:port/ #snews_proxy:http://some.server.dom:port/ #snewspost_proxy:http://some.server.dom:port/ #snewsreply_proxy:http://some.server.dom:port/ #nntp_proxy:http://some.server.dom:port/ #wais_proxy:http://some.server.dom:port/ #finger_proxy:http://some.server.dom:port/ #cso_proxy:http://some.server.dom:port/ #no_proxy:some.server.dom Leif Neland wrote: > > With freshly cvsupped current and ports, lynx has stopped working. > > Both /usr/ports/www/lynx and /usr/ports/www/lynx-current reports: > > Alert!: Unable to access document > lynx: Can't access startpage http://lynx.browser.org > > I can telnet to the url port 80. > Lynx can show local webpages (files), but no http://'s. > I use the default lynx.cfg without any changes, lynx and lynx-current > compiled unchanged from the port. > > Leif > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 20:10:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08145 for freebsd-current-outgoing; Mon, 30 Nov 1998 20:07:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08140 for ; Mon, 30 Nov 1998 20:07:32 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id HAA63383; Tue, 1 Dec 1998 07:07:10 +0300 (MSK) (envelope-from ache) Message-ID: <19981201070708.A62426@nagual.pp.ru> Date: Tue, 1 Dec 1998 07:07:08 +0300 From: "Andrey A. Chernov" To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: mtree -d (diff to include symlinks) Mail-Followup-To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG References: <199812010350.WAA12951@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812010350.WAA12951@bb01f39.unx.sas.com>; from jwd@unx.sas.com on Mon, Nov 30, 1998 at 10:50:08PM -0500 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 10:50:08PM -0500, John W. DeBoskey wrote: > (See 1.3.8.3 Mon Mar 9 12:32:09 1998 UTC by ache) The > comment does not say why the 'FTS_PHYSICAL -> FTS_LOGICAL' > change was done. Because you got serious security hole in case you use symlinks to split disk space on your system, imagine wrong /var/mail presmissions for example. BTW I believe peter already commit the change which implements (differently) what you want, see commit log for details. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 20:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08758 for freebsd-current-outgoing; Mon, 30 Nov 1998 20:13:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08749 for ; Mon, 30 Nov 1998 20:13:52 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.9.1a/3.7W) with ESMTP id NAA01086; Tue, 1 Dec 1998 13:09:58 +0900 (JST) To: bde@zeta.org.au Cc: geoffb@demon.net, mike@smith.net.au, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu, ortmann@sparc.isl.net Subject: Re: sio breakage From: KATO Takenori In-Reply-To: Your message of "Tue, 1 Dec 1998 14:30:14 +1100" <199812010330.OAA20453@godzilla.zeta.org.au> References: <199812010330.OAA20453@godzilla.zeta.org.au> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981201130957U.kato@gneiss.eps.nagoya-u.ac.jp> Date: Tue, 01 Dec 1998 13:09:57 +0900 X-Dispatcher: imput version 971024 Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > Fixes: > kernel: send a fatal signal to applications that do this. How to detect this? -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 2.2.7: Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 20:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10073 for freebsd-current-outgoing; Mon, 30 Nov 1998 20:30:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10065 for ; Mon, 30 Nov 1998 20:30:04 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id XAA29871; Mon, 30 Nov 1998 23:29:48 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA26446; Mon, 30 Nov 1998 23:29:47 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA13377; Mon, 30 Nov 1998 23:29:47 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812010429.XAA13377@bb01f39.unx.sas.com> Subject: Re: mtree -d (diff to include symlinks) In-Reply-To: <19981201070708.A62426@nagual.pp.ru> from "Andrey A. Chernov" at "Dec 1, 98 07:07:08 am" To: ache@nagual.pp.ru (Andrey A. Chernov) Date: Mon, 30 Nov 1998 23:29:47 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From the commit logs: 1.7 Fri Jun 5 14:43:41 1998 UTC by peter ... I had created chown-style -L and -P flag to control logical/physical mode (ie: whether symlinks were followed), but the nochange flag is enough to get the blasted thing out of my hair so I took them back out. ... It looks like nothing was actually committed here: Or maybe I'm just lost... :-) ok, ok, the $Id line and the type of keys were changed... but I don't see any flags that have been added. Oh well, John =================================================================== RCS file: /home/ncvs/src/usr.sbin/mtree/mtree.c,v retrieving revision 1.6 retrieving revision 1.7 diff -p -u -r1.6 -r1.7 --- src/usr.sbin/mtree/mtree.c 1997/10/01 06:30:02 1.6 +++ /home/ncvs/src/usr.sbin/mtree/mtree.c 1998/06/05 14:43:41 1.7 @@ -42,7 +42,7 @@ static const char copyright[] = static char sccsid[] = "@(#)mtree.c 8.1 (Berkeley) 6/6/93"; #endif static const char rcsid[] = - "$Id: mtree.c,v 1.6 1997/10/01 06:30:02 charnier Exp $"; + "$Id: mtree.c,v 1.7 1998/06/05 14:43:41 peter Exp $"; #endif /* not lint */ #include @@ -59,7 +59,7 @@ extern long int crc_total; int ftsoptions = FTS_LOGICAL; int cflag, dflag, eflag, iflag, nflag, rflag, sflag, uflag, Uflag; -u_short keys; +u_int keys; char fullpath[MAXPATHLEN]; static void usage __P((void)); > On Mon, Nov 30, 1998 at 10:50:08PM -0500, John W. DeBoskey wrote: > > (See 1.3.8.3 Mon Mar 9 12:32:09 1998 UTC by ache) The > > comment does not say why the 'FTS_PHYSICAL -> FTS_LOGICAL' > > change was done. > > Because you got serious security hole in case you use symlinks to split > disk space on your system, imagine wrong /var/mail presmissions for > example. BTW I believe peter already commit the change which implements > (differently) what you want, see commit log for details. > > -- > Andrey A. Chernov > http://www.nagual.pp.ru/~ache/ > MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 20:34:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10628 for freebsd-current-outgoing; Mon, 30 Nov 1998 20:34:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10588 for ; Mon, 30 Nov 1998 20:34:00 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id HAA68552; Tue, 1 Dec 1998 07:33:42 +0300 (MSK) (envelope-from ache) Message-ID: <19981201073341.A67712@nagual.pp.ru> Date: Tue, 1 Dec 1998 07:33:41 +0300 From: "Andrey A. Chernov" To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: mtree -d (diff to include symlinks) Mail-Followup-To: "John W. DeBoskey" , freebsd-current@freebsd.org References: <19981201070708.A62426@nagual.pp.ru> <199812010429.XAA13377@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812010429.XAA13377@bb01f39.unx.sas.com>; from jwd@unx.sas.com on Mon, Nov 30, 1998 at 11:29:47PM -0500 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 11:29:47PM -0500, John W. DeBoskey wrote: > I had created chown-style -L and -P flag to control logical/physical mode > (ie: whether symlinks were followed), but the nochange flag is enough to > get the blasted thing out of my hair so I took them back out. Apparently you look into wrong file. Search nochange keyword. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 20:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12170 for freebsd-current-outgoing; Mon, 30 Nov 1998 20:50:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12163 for ; Mon, 30 Nov 1998 20:50:31 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA27337; Tue, 1 Dec 1998 15:50:12 +1100 Date: Tue, 1 Dec 1998 15:50:12 +1100 From: Bruce Evans Message-Id: <199812010450.PAA27337@godzilla.zeta.org.au> To: bde@zeta.org.au, kato@ganko.eps.nagoya-u.ac.jp Subject: Re: sio breakage Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, mike@smith.net.au, ortmann@sparc.isl.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Fixes: >> kernel: send a fatal signal to applications that do this. > >How to detect this? Near the beginning of trap(): if ((frame.tf_eflags & PSL_I) == 0) fatal(...); but this is too strong, since the application may be in the middle of changing hardware state. Returning to the application probably won't make the problem (the application's problem of changing state atomically) worse, so we should enable interrupts and print an error message. PSI_I must be checked even in traps from kernel mode because the trap may be nested. In kernel mode, just enable interrupts and continue. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 21:35:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15460 for freebsd-current-outgoing; Mon, 30 Nov 1998 21:35:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15445 for ; Mon, 30 Nov 1998 21:34:57 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id GAA97243; Tue, 1 Dec 1998 06:34:00 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Tue, 1 Dec 1998 06:33:59 +0100 (CET) From: Leif Neland To: Matthew Thyer cc: freebsd-current@FreeBSD.ORG Subject: Re: lynx can't access any http://'s In-Reply-To: <366367F7.9BB67DF4@dsto.defence.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, Matthew Thyer wrote: > Have you edited /usr/local/etc/lynx.cfg > > and set the proxies if you require them ? > > Leif Neland wrote: > > > > With freshly cvsupped current and ports, lynx has stopped working. > > > > Both /usr/ports/www/lynx and /usr/ports/www/lynx-current reports: > > > > Alert!: Unable to access document > > lynx: Can't access startpage http://lynx.browser.org > > > > I can telnet to the url port 80. > > Lynx can show local webpages (files), but no http://'s. > > I use the default lynx.cfg without any changes, lynx and lynx-current ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > compiled unchanged from the port. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 21:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15854 for freebsd-current-outgoing; Mon, 30 Nov 1998 21:41:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA15845 for ; Mon, 30 Nov 1998 21:41:47 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 4204 invoked by alias); 1 Dec 1998 05:41:31 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 4183 invoked by uid 0); 1 Dec 1998 05:41:28 -0000 Received: from dialupe196.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.99.196) by omahpop1.omah.uswest.net with SMTP; 1 Dec 1998 05:41:28 -0000 Date: Mon, 30 Nov 1998 23:41:32 -0600 (CST) From: "Open Systems Inc." To: Leif Neland cc: Matthew Thyer , freebsd-current@FreeBSD.ORG Subject: Re: lynx can't access any http://'s In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems to have nothing to do with -current please move it to a more appropriate list. Thank you! Chris "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 21:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16148 for freebsd-current-outgoing; Mon, 30 Nov 1998 21:44:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16101 for ; Mon, 30 Nov 1998 21:43:55 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id QAA25083; Tue, 1 Dec 1998 16:07:38 +1030 (CST) Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id XYN7V8ZH; Tue, 1 Dec 1998 16:13:34 +1030 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.1/8.8.8) with ESMTP id QAA13602; Tue, 1 Dec 1998 16:13:01 +1030 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <366381E4.6A2A1EC3@dsto.defence.gov.au> Date: Tue, 01 Dec 1998 16:13:00 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Forrest Aldrich CC: freebsd-current@FreeBSD.ORG Subject: Re: Netscape 4.5 core dumps References: <4.1.19981128231200.0092d2e0@206.25.93.69> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At a guess, Since Netscape is still an a.out binary, you need the a.out XFree86 libs in /usr/X11R6/lib/aout Maybe you have the XFree86 3.3.2.3 aout libs there instead of a.out libs for XFree86 3.3.3 and this is causing the problem ? I haven't tried XFree86 3.3.3 yet so this is just a guess. Forrest Aldrich wrote: > > This still isn't working correctly, and I'd like to fix it. > > I'm using XFree86-3.3.3 on FreeBSD-3.0-CURRENT (build world > this morning), with WindowMaker (built today also). Whenever I > go to run Netscape, I get this in the log: > > ... /kernel: pid xxxx (netscape), uid xxx: exited on signal 11 > > It happens regardless of whether I'm root or not, and also happens > under other window managers like blackbox. > > I've updated the libs (giflib) and such that WindowMaker is dependent > upon. I'm using tk/tcl 8.1... what is wrong? > > Thanks... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 21:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16476 for freebsd-current-outgoing; Mon, 30 Nov 1998 21:51:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16471; Mon, 30 Nov 1998 21:51:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA02953; Mon, 30 Nov 1998 21:51:45 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 21:51:45 -0800 (PST) From: Matthew Dillon Message-Id: <199812010551.VAA02953@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: kmem, tty, bind security enhancements commit. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that everyone is backfrom thanksgiving and 2.2.8 is out the door, I'd like to commit the following changes to -current. These are as previously discussed and the changes have also been running on most of BEST's machines for a couple of weeks now so I'd like to commit them. I'd like someone to sign off on the concept. Eivind? Bruce? Jordan? (1) Add a 'kmem' and 'tty' dummy user to master.passwd. adjust inetd.conf to run identd and ntalkd using the new dummy user's to sandbox the kmem and tty group rights required. This also involves removing the getuid() test in talkd.c (2) Add a 'bind' user and a 'bind' group to master.passwd Use bind-8's -u and -g features to run named as bind:bind in the default rc.conf: named_flags="-u bind -g bind" (Or find a way to figure out whether this uid/gid exists and use the options or not use the options based on that, which is more compatible with prior installations but adds complexity that will quickly become stale. I suggest simply making it the default in the CVS tree). Cavet: in a multi-interface situation, with an interface that is brought up later, and so forth, named will not be able to automatically rebind and must be restarted. (Also ensure that named.conf is either group-bind-readable or world readable). However, I consider this a major, major improvement in security. I think it's worth the hassle and the vast majority of installations are not complex enough for it to matter. Those that are typically run a custom bind configuration anyway. USER and GROUP ID's I suggest: uid 4 for user 'tty' uid 5 for user 'kmem' (group kmem is uid 2, but the operator user already uses that user id so lets use uid 5, which is the operator group, for kmem). uid 53 for user bind, uid 53 for group bind Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 22:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18287 for freebsd-current-outgoing; Mon, 30 Nov 1998 22:08:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18269 for ; Mon, 30 Nov 1998 22:07:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA03051; Mon, 30 Nov 1998 22:07:47 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 22:07:47 -0800 (PST) From: Matthew Dillon Message-Id: <199812010607.WAA03051@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to make a commit to -current similar to the following (the one below is actually relative to -stable, but we are in final testing of the same patch to our -current tree). The commit I want to commit is just the ICMP_BANDLIM section. I am not planning on commiting the UDP_BANDLIM section yet. The ICMP rate limiter limits the number of ICMP error responses the machine will return. There are currently several D.O.S. attacks that can cause the machine to crash or become totally unusable due to it trying to send an ICMP response to each one. This rate limiter has been installed on BEST machines for several months and has probably saved us two or three dozen crashes from attacks. Since it only limits ICMP error responses, the default rate limit is set relatively low at 100 packets per second. The only time I have ever hit the limit has been during an attack, even on our most heavily loaded web boxes. I believe 100 to be an excellent default value. I would like a sign-off on the ICMP_BANDLIM portion of the patch so I can commit it. The UDP_BANDLIM section is presented for discussion, but I do not plan to request a commit for it in its current incarnation. This section was designed to prevent hostile users from being able to perpetrate attacks or take down a machine from a hacked account and it does in fact do a pretty good job at it, but there are obvious ways to circumvent the problem. I really need to change the hack and add a new per-user resource limit 'maximum allowed network I/O bandwidth' that actually rate-limits network traffic from a user rather then dropping excessive packet traffic. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) diff -r -c /static/src/sys/netinet/tcp_input.c ./netinet/tcp_input.c *** /static/src/sys/netinet/tcp_input.c Thu Sep 17 15:46:23 1998 --- ./netinet/tcp_input.c Fri Sep 18 13:29:21 1998 *************** *** 382,387 **** --- 382,394 ---- buf, ntohs(ti->ti_dport), inet_ntoa(ti->ti_src), ntohs(ti->ti_sport)); } + #ifdef ICMP_BANDLIM + { + extern int badport_bandlim(int); /* hack */ + if (badport_bandlim(1) < 0) + goto drop; + } + #endif goto dropwithreset; } tp = intotcpcb(inp); diff -r -c /static/src/sys/netinet/udp_usrreq.c ./netinet/udp_usrreq.c *** /static/src/sys/netinet/udp_usrreq.c Thu Oct 23 14:19:24 1997 --- ./netinet/udp_usrreq.c Fri Jul 10 19:34:26 1998 *************** *** 47,52 **** --- 47,53 ---- #include #include #include + #include #include #include *************** *** 70,75 **** --- 71,77 ---- #else static int udpcksum = 0; /* XXX */ #endif + SYSCTL_INT(_net_inet_udp, UDPCTL_CHECKSUM, checksum, CTLFLAG_RW, &udpcksum, 0, ""); *************** *** 77,85 **** --- 79,105 ---- SYSCTL_INT(_net_inet_udp, OID_AUTO, log_in_vain, CTLFLAG_RW, &log_in_vain, 0, ""); + #ifdef UDP_BANDLIM + static int udpbandlim = 200000; /* bytes/sec */ + static int udpbanddebug = 0; + SYSCTL_INT(_net_inet_udp, UDPCTL_BANDLIM, bandlim, CTLFLAG_RW, + &udpbandlim, 0, ""); + SYSCTL_INT(_net_inet_udp, UDPCTL_BANDDEBUG, banddebug, CTLFLAG_RW, + &udpbanddebug, 0, ""); + #endif + #ifdef ICMP_BANDLIM + static int icmplim = 100; + SYSCTL_INT(_net_inet_udp, UDPCTL_ICMPLIM, icmplim, CTLFLAG_RW, + &icmplim, 0, ""); + #endif + static struct inpcbhead udb; /* from udp_var.h */ static struct inpcbinfo udbinfo; + #ifdef ICMP_BANDLIM + int badport_bandlim(int which); + #endif + #ifndef UDBHASHSIZE #define UDBHASHSIZE 64 #endif *************** *** 91,99 **** --- 111,122 ---- static struct sockaddr_in udp_in = { sizeof(udp_in), AF_INET }; static void udp_detach __P((struct inpcb *)); + static void udp_dealloc_ppcb(struct inpcb *inp); + static int udp_alloc_ppcb(struct inpcb *inp); static int udp_output __P((struct inpcb *, struct mbuf *, struct mbuf *, struct mbuf *)); static void udp_notify __P((struct inpcb *, int)); + static int udp_rate_limit(struct inpcb *inp, int packetLen); void udp_init() *************** *** 296,302 **** --- 319,332 ---- goto bad; } *ip = save_ip; + #ifdef ICMP_BANDLIM + if (badport_bandlim(0) == 0) + icmp_error(m, ICMP_UNREACH, ICMP_UNREACH_PORT, 0, 0); + else + goto bad; + #else icmp_error(m, ICMP_UNREACH, ICMP_UNREACH_PORT, 0, 0); + #endif return; } *************** *** 379,384 **** --- 409,425 ---- goto release; } + /* + * Check rate limit + */ + + if (udpbandlim > 0 && + udp_rate_limit(inp, len + sizeof(struct udpiphdr)) < 0 + ) { + error = ENOBUFS; + goto release; + } + if (addr) { laddr = inp->inp_laddr; if (inp->inp_faddr.s_addr != INADDR_ANY) { *************** *** 502,507 **** --- 543,552 ---- if (error) break; ((struct inpcb *) so->so_pcb)->inp_ip_ttl = ip_defttl; + + inp = sotoinpcb(so); + if ((error = udp_alloc_ppcb(inp)) != 0) + break; break; case PRU_DETACH: *************** *** 608,613 **** --- 653,801 ---- { int s = splnet(); + udp_dealloc_ppcb(inp); + in_pcbdetach(inp); splx(s); } + + /* + * UDP RATE LIMITING - used to protect against floods and such + * + * Only applies to non-root-owned processes. + */ + + typedef struct udp_rate { + int ur_Bytes[2]; + int ur_Packets; + int ur_Ticks; + int ur_BandLimited; + int ur_Printed; + int ur_SUid; + } udp_rate; + + static int + udp_alloc_ppcb(struct inpcb *inp) + { + int error = 0; + struct proc *p = curproc; + + if ( + curproc && + inp->inp_ppcb == 0 && + suser(p->p_ucred, &p->p_acflag) != 0 + ) { + udp_rate *ur = malloc(sizeof(udp_rate), M_PCB, M_NOWAIT); + if (ur == NULL) { + error = ENOBUFS; + } else { + bzero(ur, sizeof(*ur)); + ur->ur_Ticks = ticks; + inp->inp_ppcb = (caddr_t)ur; + } + } + return(error); + } + + static void + udp_dealloc_ppcb(struct inpcb *inp) + { + udp_rate *ur; + + if ((ur = (udp_rate *)inp->inp_ppcb) != 0) { + free(ur, M_PCB); + inp->inp_ppcb = 0; + } + } + + static int + udp_rate_limit(struct inpcb *inp, int packetLen) + { + udp_rate *ur; + int r = 0; + int uticks = ticks; + + if ((ur = (udp_rate *)inp->inp_ppcb) != 0) { + int dticks; + + if (udpbanddebug > 0) { + printf("UR TEST %d BL=%d bytes=%d/%d pkts=%d\n", + (int)(uticks - ur->ur_Ticks), + ur->ur_BandLimited, + ur->ur_Bytes[0] + ur->ur_Bytes[1], + ur->ur_Packets + ); + } + + /* + * get delta ticks, accumulation over a one second period. + * rate limit holds for one second after going over. Kernel + * printf only occurs once per second. + */ + + if ((dticks = uticks - ur->ur_Ticks) < 0 || dticks >= hz) { + ur->ur_Ticks = uticks; + ur->ur_Printed = 0; + ur->ur_Bytes[1] = ur->ur_Bytes[0]; + ur->ur_Bytes[0] = 0; + } + ur->ur_Bytes[0] += packetLen; + ++ur->ur_Packets; + + if (ur->ur_Bytes[0] > udpbandlim || + ur->ur_Bytes[1] > udpbandlim + ) { + r = -1; + + ur->ur_BandLimited; + if (ur->ur_Printed == 0) { + ur->ur_Printed = 1; + if (udpbanddebug >= 0) { + printf("udp band limited src %s:%d", + inet_ntoa(inp->inp_laddr), + (int)ntohs(inp->inp_fport) + ); + printf(" dst %s:%d %d/%d\n", + inet_ntoa(inp->inp_faddr), + (int)ntohs(inp->inp_lport), + ur->ur_Bytes[0] + ur->ur_Bytes[1], + ur->ur_Packets + ); + } + } + } else { + ur->ur_BandLimited = 0; + } + } + return(r); + } + + #ifdef ICMP_BANDLIM + + int + badport_bandlim(int which) + { + static int lticks[2]; + static int lpackets[2]; + int dticks; + + if (which >= 2 || which < 0) + return(0); + dticks = ticks - lticks[which]; + if ((unsigned int)dticks > hz) { + if (lpackets[which] >= icmplim) { + printf("icmp-response bandwidth limit %d/%d pps\n", + lpackets[which], + icmplim + ); + } + lticks[which] = ticks; + lpackets[which] = 0; + } + if (++lpackets[which] >= icmplim) + return(-1); + return(0); + } + + #endif + diff -r -c /static/src/sys/netinet/udp_var.h ./netinet/udp_var.h *** /static/src/sys/netinet/udp_var.h Wed Jun 5 10:20:35 1996 --- ./netinet/udp_var.h Fri Jul 10 19:00:35 1998 *************** *** 79,84 **** --- 79,101 ---- #define UDPCTL_MAXDGRAM 3 /* max datagram size */ #define UDPCTL_RECVSPACE 4 /* default receive buffer space */ #define UDPCTL_MAXID 5 + #ifdef UDP_BANDLIM + #define UDPCTL_BANDLIM 6 + #define UDPCTL_BANDDEBUG 7 + #endif + #ifdef ICMP_BANDLIM + #define UDPCTL_ICMPLIM 8 + #endif + + #ifdef UDP_BANDLIM + #define UDP_BANDLIM_INFO \ + { "bandlim", CTLTYPE_INT }, \ + { "banddebug", CTLTYPE_INT }, + #endif + #ifdef ICMP_BANDLIM + #define ICMP_BANDLIM_INFO \ + { "icmplim", CTLTYPE_INT }, + #endif #define UDPCTL_NAMES { \ { 0, 0 }, \ *************** *** 86,91 **** --- 103,110 ---- { "stats", CTLTYPE_STRUCT }, \ { "maxdgram", CTLTYPE_INT }, \ { "recvspace", CTLTYPE_INT }, \ + UDP_BANDLIM_INFO \ + ICMP_BANDLIM_INFO \ } #ifdef KERNEL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 22:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21881 for freebsd-current-outgoing; Mon, 30 Nov 1998 22:51:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21875 for ; Mon, 30 Nov 1998 22:51:12 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id RAA10105; Tue, 1 Dec 1998 17:50:59 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma010095; Tue, 1 Dec 98 17:50:45 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id RAA24055; Tue, 1 Dec 1998 17:50:36 +1100 From: "John Saunders" To: "Matthew Dillon" , Subject: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) Date: Tue, 1 Dec 1998 17:50:36 +1100 Message-ID: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199812010607.WAA03051@apollo.backplane.com> X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The ICMP rate limiter limits the number of ICMP error responses the > machine will return. There are currently several D.O.S. attacks that > can cause the machine to crash or become totally unusable due to it > trying to send an ICMP response to each one. This rate limiter has > been installed on BEST machines for several months and has probably saved > us two or three dozen crashes from attacks. Q1: Why does FreeBSD crash or become totally unstable under what can only be described as high network load? >From my thinking there are two steps: 1: Make FreeBSD run stable as a rock while being pounded with DoS attacks. Although under such an attack it is not expected to be able to perform much real work due to network saturation and shortage of mbufs. 2: Include the ICMP rate limiting patch so that while under a DoS attack real work can continue to happen. Although this patch only removes work from the transmission path, DoS ICMP messages will continue to be received and processed to the point of being discarded. However most servers have plenty of reception bandwidth available but not much transmission bandwidth so this patch works in our favour. I think that this patch may simply mask the real stability problem in the IP stack. Although I do support the idea of having this facility. Would setting the packet rate to 0 effectively disable the rate limiting? > Since it only limits ICMP error responses, the default rate limit is set > relatively low at 100 packets per second. The only time I have ever > hit the limit has been during an attack, even on our most heavily loaded > web boxes. I believe 100 to be an excellent default value. This sounds OK, on my network I wouldn't see even 2 packets per second. > The UDP_BANDLIM section is presented for discussion, but I do not plan > to request a commit for it in its current incarnation. This section was > designed to prevent hostile users from being able to perpetrate attacks > or take down a machine from a hacked account and it does in fact do a > pretty good job at it, but there are obvious ways to circumvent the > problem. I really need to change the hack and add a new per-user resource > limit 'maximum allowed network I/O bandwidth' that actually rate-limits > network traffic from a user rather then dropping excessive packet traffic. When you get all the way to a per-uid resource limit this would be really good. I would like to see both TCP and UDP included. However for the moment it seems to be a serious step to limit UDP to some artificial rate. There are valid uses for high volume UDP (VoIP, ICP, RealPlayer). Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 23:09:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23321 for freebsd-current-outgoing; Mon, 30 Nov 1998 23:09:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23312 for ; Mon, 30 Nov 1998 23:09:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA03688; Mon, 30 Nov 1998 23:08:50 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 23:08:50 -0800 (PST) From: Matthew Dillon Message-Id: <199812010708.XAA03688@apollo.backplane.com> To: "John Saunders" Cc: "Matthew Dillon" , Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>From my thinking there are two steps: : :1: Make FreeBSD run stable as a rock while being pounded with :DoS attacks. Although under such an attack it is not expected :to be able to perform much real work due to network saturation :and shortage of mbufs. As far as I can tell, it starves the mbuf pool and/or outgoing packet queues. When we get D.O.S. attacks greater then 20,000 packets per second or so, and the machine tries to send 20,000 pps worth of ICMP error replies, other packet traffic gets thrown away. Furthermore, if the reply is to a non-existant IP on the local LAN, the ICMP replies get buffered while the machine tries to ARP the destination. If not, the xmit traffic goes to the switch which starts collisioning-out packets when the router beyond the switch saturates. It isn't possible for the xmit rate to exceed the recv rate in that situation, so packets build up. :2: Include the ICMP rate limiting patch so that while under :a DoS attack real work can continue to happen. Although this :patch only removes work from the transmission path, DoS ICMP :messages will continue to be received and processed to the :point of being discarded. However most servers have plenty :of reception bandwidth available but not much transmission :bandwidth so this patch works in our favour. : :I think that this patch may simply mask the real stability :problem in the IP stack. Although I do support the idea of :having this facility. Would setting the packet rate to 0 :effectively disable the rate limiting? It's a real problem. When you are receiving a 20Kpps attack you do not want to be transmitting 20Kpps in ICMP replies to a possibly spoofed address. I definitely do *not* want to play with the outgoing packet queues or network memory allocation subsystem. Not only is doing so a much more complicated task, but it is also a matter of fixing the problem after the patient has died. With the cpu already at saturation, trying to do fancy dequeueing and prioritization of insanely huge packet queues will only make things worse. Rate limiting the error responses (not even trying to respond if the rate is too high) prevents cpu and network xmit starvation from occuring in the first place while still allowing legitimate traffic through. :loaded :> web boxes. I believe 100 to be an excellent default value. : :This sounds OK, on my network I wouldn't see even 2 packets :per second. : :-- . +-------------------------------------------------------+ : ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 23:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23741 for freebsd-current-outgoing; Mon, 30 Nov 1998 23:13:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23734 for ; Mon, 30 Nov 1998 23:13:50 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id XAA26714; Mon, 30 Nov 1998 23:14:06 -0800 (PST) Message-Id: <199812010714.XAA26714@root.com> To: Matthew Dillon cc: freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-reply-to: Your message of "Mon, 30 Nov 1998 22:07:47 PST." <199812010607.WAA03051@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 30 Nov 1998 23:14:06 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would like to make a commit to -current similar to the following > (the one below is actually relative to -stable, but we are in final > testing of the same patch to our -current tree). > > The commit I want to commit is just the ICMP_BANDLIM section. I am The only comment I have at the moment is that the patches need a little KNF work. The mixing of indentation amounts within a function is particularly annoying and makes the code difficult to read. Indents should be tabs, with half tabs (4 spaces) used on continued lines (such as if () conditionals). The patches have other KNF problems as well...see 'man 9 style'. In principle, I'm not against these sorts of changes, but I tend to think that a more general scheme implemented perhaps inside the ipfw framework would be more appropriate. I also generally like to avoid compile time options for things like this, but I"m sympathetic for performance reducing enhancements. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 23:26:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25126 for freebsd-current-outgoing; Mon, 30 Nov 1998 23:26:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25118 for ; Mon, 30 Nov 1998 23:26:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA03791; Mon, 30 Nov 1998 23:26:26 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 23:26:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812010726.XAA03791@apollo.backplane.com> To: David Greenman Cc: freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <199812010714.XAA26714@root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> testing of the same patch to our -current tree). :> :> The commit I want to commit is just the ICMP_BANDLIM section. I am : : The only comment I have at the moment is that the patches need a little :KNF work. The mixing of indentation amounts within a function is particularly :annoying and makes the code difficult to read. Indents should be tabs, with Don't worry about that... I'll clean that up in an official commit. I'm not keen on 8-character indents, but I try to commit things that follow the tone of the surrounding source. :general scheme implemented perhaps inside the ipfw framework would be more :appropriate. I also generally like to avoid compile time options for things :like this, but I"m sympathetic for performance reducing enhancements. : :-DG I figure we would make it the default in 6 months to a year, but we should have it optioned initially so people can play with it and also because it defaults to enabled when optioned-in, which I think is important. -Matt : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 30 23:29:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25526 for freebsd-current-outgoing; Mon, 30 Nov 1998 23:29:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25507 for ; Mon, 30 Nov 1998 23:29:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA03814; Mon, 30 Nov 1998 23:28:48 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 23:28:48 -0800 (PST) From: Matthew Dillon Message-Id: <199812010728.XAA03814@apollo.backplane.com> To: David Greenman Cc: freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <199812010714.XAA26714@root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :general scheme implemented perhaps inside the ipfw framework would be more :appropriate. I also generally like to avoid compile time options for things :like this, but I"m sympathetic for performance reducing enhancements. : :-DG I think trying to fold this into ipfw is overkill. I can think of no reason why you might want to turn the feature on for some cases and off for others, especially considering that the original packet might have been spoofed and thus can cause the ICMP reply to go out any interface. It would be an unnecessary complication to ipfw. -Matt :David Greenman :Co-founder/Principal Architect, The FreeBSD Project : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 05:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25833 for freebsd-current-outgoing; Tue, 1 Dec 1998 05:06:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1001.mpoweredpc.net [142.177.191.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25826 for ; Tue, 1 Dec 1998 05:06:41 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id JAA25162 for ; Tue, 1 Dec 1998 09:05:56 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 1 Dec 1998 09:05:52 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: 'junk pointer' with inetd ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... I hate to ask, but on a Nov 4th -CURRENT system, right close to the release, I've started to get the following errors coming up: hub# telnet localhost pop3 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. inetd in realloc(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. Uptime is only 10 days... Looking around the system, I just noticed the following: root 273 0.0 0.0 262956 8 ?? Is 20Nov98 0:00.00 rpc.statd Isn't that just a little large? DoS maybe? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 05:46:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28649 for freebsd-current-outgoing; Tue, 1 Dec 1998 05:46:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1001.mpoweredpc.net [142.177.191.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28630 for ; Tue, 1 Dec 1998 05:46:45 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id JAA26041 for ; Tue, 1 Dec 1998 09:46:29 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 1 Dec 1998 09:46:29 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: inetd: junk pointer - self followup/question... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to investigate further, I just ran 'netstat -n' on the server, and it came up with alot of 'ESTABLISHED' connections that there were no asssociated processes with (alot of port 119 - nntp)...I shut down news and restarted it, ad not I have 239 TIME_WAIT connections? hub# netstat -n | grep TIME_WAIT | wc -l 239 hub# netstat -n | grep ^tcp | grep -v LISTEN | wc -l 579 Is this normal? Or could this be where my problem is arising? Am I even lookign in the right direction? :( Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 05:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29824 for freebsd-current-outgoing; Tue, 1 Dec 1998 05:59:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29817 for ; Tue, 1 Dec 1998 05:59:24 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id IAA16239; Tue, 1 Dec 1998 08:59:07 -0500 (EST) Date: Tue, 1 Dec 1998 08:59:07 -0500 (EST) From: John Fieber To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, The Hermit Hacker wrote: > I hate to ask, but on a Nov 4th -CURRENT system, right close to > the release, I've started to get the following errors coming up: > > hub# telnet localhost pop3 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > inetd in realloc(): warning: junk pointer, too high to make sense. > inetd in free(): warning: junk pointer, too high to make sense. Do you get the same result telnetting to other ports? If so, you've probably been bitten by the infamous dying daemons bug. Hom much RAM, how much swap and how much swap is in use? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00657 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:06:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SungSung.Dorm10.NCTU.edu.tw (SungSung.Dorm10.NCTU.edu.tw [140.113.122.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00601 for ; Tue, 1 Dec 1998 06:06:01 -0800 (PST) (envelope-from AlanSung@SungSung.Dorm10.NCTU.edu.tw) Received: (from AlanSung@localhost) by SungSung.Dorm10.NCTU.edu.tw (8.9.1/8.9.1) id WAA03759 for current@freebsd.org; Tue, 1 Dec 1998 22:05:32 +0800 (CST) Date: Tue, 1 Dec 1998 22:05:32 +0800 (CST) From: Cheng-Lung Sung Message-Id: <199812011405.WAA03759@SungSung.Dorm10.NCTU.edu.tw> To: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: does 640MB MO formatted by Win95 works in BSD? I'd formated my 640MB MO disk in Win95, but it seens that can't use in FreeBSD 3.0-CURRENT by mount_msdos or something like mount ... I know that an unformated 640MB MO disk can disklabel in BSD but does anyone know how 95formated MO disk used in BSD? sector size = 2K...:~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:06:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00742 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:06:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1001.mpoweredpc.net [142.177.191.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00733 for ; Tue, 1 Dec 1998 06:06:49 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id KAA26691; Tue, 1 Dec 1998 10:06:27 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 1 Dec 1998 10:06:27 -0400 (AST) From: The Hermit Hacker To: John Fieber cc: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, John Fieber wrote: > On Tue, 1 Dec 1998, The Hermit Hacker wrote: > > > I hate to ask, but on a Nov 4th -CURRENT system, right close to > > the release, I've started to get the following errors coming up: > > > > hub# telnet localhost pop3 > > Trying 127.0.0.1... > > Connected to localhost. > > Escape character is '^]'. > > inetd in realloc(): warning: junk pointer, too high to make sense. > > inetd in free(): warning: junk pointer, too high to make sense. > > Do you get the same result telnetting to other ports? If so, > you've probably been bitten by the infamous dying daemons bug. Sorry, I knew I should have finished the above :( hub# telnet localhost pop3 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. inetd in realloc(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. +OK hub.org Cyrus POP3 v1.5.14 server ready > Hom much RAM, how much swap and how much swap is in use? 384Meg, and hub# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/da0s1b 262144 13780 248236 5% Interleaved /dev/da3s1b 262144 14236 247780 5% Interleaved /dev/da4s1b 262144 14912 247104 6% Interleaved Total 786048 42928 743120 5% Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01187 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:10:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SungSung.Dorm10.NCTU.edu.tw (SungSung.Dorm10.NCTU.edu.tw [140.113.122.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01085 for ; Tue, 1 Dec 1998 06:09:55 -0800 (PST) (envelope-from AlanSung@SungSung.Dorm10.NCTU.edu.tw) Received: (from AlanSung@localhost) by SungSung.Dorm10.NCTU.edu.tw (8.9.1/8.9.1) id WAA03793 for current@freebsd.org; Tue, 1 Dec 1998 22:09:47 +0800 (CST) Date: Tue, 1 Dec 1998 22:09:47 +0800 (CST) From: Cheng-Lung Sung Message-Id: <199812011409.WAA03793@SungSung.Dorm10.NCTU.edu.tw> Subject: does 640MB MO formatted by Win95 works in BSD? To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd formated my 640MB MO disk in Win95, but it seens that can't use in FreeBSD 3.0-CURRENT by mount_msdos or something like mount ... I know that an unformated 640MB MO disk can disklabel in BSD but does anyone know how 95formated MO disk used in BSD? sector size = 2K...:~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:11:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01375 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:11:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01370 for ; Tue, 1 Dec 1998 06:11:34 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA16295; Tue, 1 Dec 1998 09:11:21 -0500 (EST) Date: Tue, 1 Dec 1998 09:11:20 -0500 (EST) From: John Fieber To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, The Hermit Hacker wrote: > Sorry, I knew I should have finished the above :( > inetd in realloc(): warning: junk pointer, too high to make sense. > inetd in free(): warning: junk pointer, too high to make sense. > +OK hub.org Cyrus POP3 v1.5.14 server ready > > > Hom much RAM, how much swap and how much swap is in use? > > 384Meg, and Hmm. Not quite textbook dying daemons symptoms. Have a look at pr/8183. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:15:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01846 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:15:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01841 for ; Tue, 1 Dec 1998 06:15:11 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id GAA29284; Tue, 1 Dec 1998 06:15:23 -0800 (PST) Message-Id: <199812011415.GAA29284@root.com> To: John Fieber cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-reply-to: Your message of "Tue, 01 Dec 1998 09:11:20 EST." From: David Greenman Reply-To: dg@root.com Date: Tue, 01 Dec 1998 06:15:23 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hmm. Not quite textbook dying daemons symptoms. Have a look at >pr/8183. Regarding that PR, I sure wish someone would come up with something better than writing to a pipe to store temporary state information. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:26:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03359 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:26:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03323 for ; Tue, 1 Dec 1998 06:26:23 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=localhost) by axl.noc.iafrica.com with local-esmtp (Exim 2.053 #1) id 0zkqkK-0002LQ-00; Tue, 1 Dec 1998 16:25:44 +0200 From: Sheldon Hearn To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: inetd: junk pointer - self followup/question... In-reply-to: Your message of "Tue, 01 Dec 1998 09:46:29 -0400." MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <9011.912522335.0@localhost> Date: Tue, 01 Dec 1998 16:25:44 +0200 Message-ID: <9015.912522344@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9011.912522335.1@localhost> > Is this normal? Or could this be where my problem is arising? Am I > even lookign in the right direction? :( Nope, the right direction is always Handbook, FAQ, mail archives. Attached is a recent message I found doing a quick search for "inetd AND junk AND pointer". Ciao, Sheldon. ------- =_aaaaaaaaaa0 Content-Type: message/rfc822 Content-ID: <9011.912522335.2@localhost> >From owner-freebsd-questions Mon Nov 23 16:58:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12685 for freebsd-questions-outgoing; Mon, 23 Nov 1998 16:58:29 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12663; Mon, 23 Nov 1998 16:58:23 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA10594; Tue, 24 Nov 1998 11:28:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA63577; Tue, 24 Nov 1998 11:28:17 +1030 (CST) Message-ID: <19981124112817.I63366@freebie.lemis.com> Date: Tue, 24 Nov 1998 11:28:17 +1030 From: Greg Lehey To: "Julian A. Zottl" , questions@FreeBSD.ORG Cc: freebsd-questions@FreeBSD.ORG Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. and netd in free(): warning: junk pointer, too low to make sense. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian A. Zottl on Mon, Nov 23, 1998 at 07:58:51PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 23 November 1998 at 19:58:51 -0500, Julian A. Zottl wrote: > Hello all, I am getting these errors when I try to telnet to my FreeBSD > 3.0 box. Any ideas? This is a known problem, one that we're having difficulty isolating. The workaround is to restart inetd. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message ------- =_aaaaaaaaaa0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:29:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03650 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:29:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-16.dialip.mich.net [192.195.231.218]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA03629 for ; Tue, 1 Dec 1998 06:29:24 -0800 (PST) (envelope-from garman@earthling.net) From: garman@earthling.net Received: (qmail 22972 invoked by uid 1000); 1 Dec 1998 14:30:44 -0000 Message-ID: Date: Tue, 1 Dec 1998 09:30:44 -0500 To: scrappy@hub.org (The Hermit Hacker) Cc: jfieber@indiana.edu (John Fieber), freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... References: X-Mailer: Mutt 0.58 Mime-Version: 1.0 Reply-To: garman@earthling.net X-Phase-Of-Moon: The Moon is Waxing Gibbous (94% of Full) X-Operating-System: FreeBSD/i386 2.2-STABLE In-Reply-To: ; from The Hermit Hacker on Dec 1, 1998 10:06:27 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker writes: > > 384Meg, and > > hub# pstat -s > Device 1K-blocks Used Avail Capacity Type > /dev/da0s1b 262144 13780 248236 5% Interleaved > /dev/da3s1b 262144 14236 247780 5% Interleaved > /dev/da4s1b 262144 14912 247104 6% Interleaved > Total 786048 42928 743120 5% > another thing to check is your dmesg; see if there's any "suggest more swap space" messages in there. these messages seem to precede the dying daemons on my box at least. (it at least makes the problem much worse in my case) and to those who believe that this bug is only caused when one is "near swap capacity" -- the swapinfo above would refute that :) theres several threads about this -- check the archives. it looks like a kernel bug where process memory gets zeroed when it forks a copy of itself. I see it not only in inetd, but samba, junkbuster, sshd, etc etc etc. look for large numbers of segfaulting daemons in your logs :) enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 06:39:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04750 for freebsd-current-outgoing; Tue, 1 Dec 1998 06:39:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1001.mpoweredpc.net [142.177.191.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04743 for ; Tue, 1 Dec 1998 06:39:20 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id KAA26857; Tue, 1 Dec 1998 10:36:52 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 1 Dec 1998 10:36:52 -0400 (AST) From: The Hermit Hacker To: garman@earthling.net cc: John Fieber , freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998 garman@earthling.net wrote: > The Hermit Hacker writes: > > > > 384Meg, and > > > > hub# pstat -s > > Device 1K-blocks Used Avail Capacity Type > > /dev/da0s1b 262144 13780 248236 5% Interleaved > > /dev/da3s1b 262144 14236 247780 5% Interleaved > > /dev/da4s1b 262144 14912 247104 6% Interleaved > > Total 786048 42928 743120 5% > > > another thing to check is your dmesg; see if there's any "suggest more > swap space" messages in there. these messages seem to precede the dying > daemons on my box at least. (it at least makes the problem much worse in > my case) > > and to those who believe that this bug is only caused when one is "near > swap capacity" -- the swapinfo above would refute that :) > > theres several threads about this -- check the archives. it looks like a > kernel bug where process memory gets zeroed when it forks a copy of > itself. I see it not only in inetd, but samba, junkbuster, sshd, etc etc > etc. look for large numbers of segfaulting daemons in your logs :) Unsure of when it started, but dmesg just gives line after line of: pid 7913 (httpd), uid 65534: exited on signal 11 pid 7912 (httpd), uid 65534: exited on signal 11 pid 7910 (httpd), uid 65534: exited on signal 11 pid 7906 (httpd), uid 65534: exited on signal 11 Not thinking it was related until ppl brought up the 'daemon dying' thread, I didn't mention it previously, but I killed off httpd and restarted it, which stop'd the scrolling messages...but has not stop'd thee 'junk pointer' messages... I dread having to reboot it, but its looking like I may just have to do that ;( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06695 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:03:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06690 for ; Tue, 1 Dec 1998 07:03:01 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id KAA16461; Tue, 1 Dec 1998 10:02:40 -0500 (EST) Date: Tue, 1 Dec 1998 10:02:40 -0500 (EST) From: John Fieber To: The Hermit Hacker cc: garman@earthling.net, freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, The Hermit Hacker wrote: > Unsure of when it started, but dmesg just gives line after line of: > > pid 7913 (httpd), uid 65534: exited on signal 11 > pid 7912 (httpd), uid 65534: exited on signal 11 > pid 7910 (httpd), uid 65534: exited on signal 11 > pid 7906 (httpd), uid 65534: exited on signal 11 > > Not thinking it was related until ppl brought up the 'daemon dying' > thread, I didn't mention it previously, but I killed off httpd and > restarted it, which stop'd the scrolling messages...but has not stop'd > thee 'junk pointer' messages... That is consistent with my dying daemons experience, but the you don't appear to have the swap space pressure that seems to trigger it for most other people. I've been saving all messages on the dying daemons topic and could email you the whole bundle if you like. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08101 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:17:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel7.mindspring.com (camel7.mindspring.com [207.69.200.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08095 for ; Tue, 1 Dec 1998 07:16:59 -0800 (PST) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by camel7.mindspring.com (8.8.5/8.8.5) with SMTP id KAA00987 for ; Tue, 1 Dec 1998 10:16:46 -0500 (EST) Date: Tue, 1 Dec 1998 10:17:03 -0500 (EST) From: steven To: current@FreeBSD.ORG Subject: Re: top/w/vmstat weirdness -- ME TOO! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded yesterday via cvsup and now, today, top, w , ps etc give me top... kvm_open: proc size mismatch (27388 total, 672 chunks) top: Out of memory. w... 10:16AM up 33 mins, 1 user, load averages: 0.24, 0.31, 0.20 USER TTY FROM LOGIN@ IDLE WHAT w: proc size mismatch (27388 total, 672 chunks): Undefined error: 0 ps... ps: proc size mismatch (14696 total, 672 chunks) vmstat works for me ;-) please reply via email if you can.. i'm running the Nov 30 cvs source on 3.0 Current Steven S. >>> 403forbidden.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08334 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:19:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mescalero.asd1.rl.ac.uk (mescalero.asd1.rl.ac.uk [130.246.170.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08326 for ; Tue, 1 Dec 1998 07:18:49 -0800 (PST) (envelope-from tmb@rcru.rl.ac.uk) Received: from rcru.rl.ac.uk (LOCALHOST [127.0.0.1]) by mescalero.asd1.rl.ac.uk (8.9.1/8.9.1) with ESMTP id PAA28087; Tue, 1 Dec 1998 15:17:35 GMT (envelope-from tmb@rcru.rl.ac.uk) Message-Id: <199812011517.PAA28087@mescalero.asd1.rl.ac.uk> X-Mailer: exmh version 2.0.2 2/24/98 To: Cheng-Lung Sung cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 01 Dec 1998 22:05:32 +0800." <199812011405.WAA03759@SungSung.Dorm10.NCTU.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 15:17:35 +0000 From: Mark Blackman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG although the lower levels of code (CAM) can handle 2048 byte sectors no problem, the 'msdosfs' code needs to be tweaked a bit more to get this kind of functionality. It looks reasonably close but I think there are a couple of hardwired 512-byte block reads that I didn't get to track down. However, the latest version of mtools (3.9.1) appears to work for me with an entry in /usr/local/etc/mtools.conf of drive m: file="/dev/da1" blocksize=2048 (obviously changing drive details as appropriate). It does put errors on the console, but the mtools operation does complete with expected results. You also seem to need a disk in the drive at boot-up for the MO drive to be configured. (cvsup of 981028) Mark > Subject: does 640MB MO formatted by Win95 works in BSD? > > I'd formated my 640MB MO disk in Win95, but it seens that > can't use in FreeBSD 3.0-CURRENT by mount_msdos or something > like mount ... > > I know that an unformated 640MB MO disk can disklabel in BSD > but does anyone know how 95formated MO disk used in BSD? > > sector size = 2K...:~~ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08864 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:22:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA08858 for ; Tue, 1 Dec 1998 07:22:04 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 23600 invoked by uid 1001); 1 Dec 1998 15:21:51 -0000 Date: Tue, 1 Dec 1998 16:21:51 +0100 From: Jesper Skriver To: steven Cc: current@FreeBSD.ORG Subject: Re: top/w/vmstat weirdness -- ME TOO! Message-ID: <19981201162151.A23581@skriver.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: ; from steven on Tue, Dec 01, 1998 at 10:17:03AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 01, 1998 at 10:17:03AM -0500, steven wrote: > > I just upgraded yesterday via cvsup and now, today, > > top, w , ps etc give me > > top... > kvm_open: proc size mismatch (27388 total, 672 chunks) > top: Out of memory. You only updated the kernel, you need to update the rest of the system ... cd /usr/src make buildworld && make installworld /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:22:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08919 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:22:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08912 for ; Tue, 1 Dec 1998 07:22:50 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id PAA13363; Tue, 1 Dec 1998 15:22:27 GMT Message-ID: <366409B3.8ECE975D@tdx.co.uk> Date: Tue, 01 Dec 1998 15:22:27 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: steven CC: current@FreeBSD.ORG Subject: Re: top/w/vmstat weirdness -- ME TOO! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG steven wrote: > > I just upgraded yesterday via cvsup and now, today, > > top, w , ps etc give me > > top... > kvm_open: proc size mismatch (27388 total, 672 chunks) > top: Out of memory. Have you recompiled libkvm? & the kernel (with the new sources?) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 07:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09533 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:30:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from easeway.com (ns1.easeway.com [209.69.71.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09522 for ; Tue, 1 Dec 1998 07:30:04 -0800 (PST) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id KAA08644; Tue, 1 Dec 1998 10:13:19 -0500 (EST) Message-Id: <199812011513.KAA08644@easeway.com> Subject: Re: top/w/vmstat weirdness -- ME TOO! In-Reply-To: <19981201162151.A23581@skriver.dk> from Jesper Skriver at "Dec 1, 98 04:21:51 pm" To: jesper@skriver.dk (Jesper Skriver) Date: Tue, 1 Dec 1998 10:13:19 -0500 (EST) Cc: stevensl@mindspring.net, current@FreeBSD.ORG From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alternately, you've upgraded the rest of the system and need to upgrade your kernel. > On Tue, Dec 01, 1998 at 10:17:03AM -0500, steven wrote: > > > > I just upgraded yesterday via cvsup and now, today, > > > > top, w , ps etc give me > > > > top... > > kvm_open: proc size mismatch (27388 total, 672 chunks) > > top: Out of memory. > > You only updated the kernel, you need to update the rest of the system > ... > > cd /usr/src > make buildworld && make installworld > > > /Jesper -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:00:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11844 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:00:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11777 for ; Tue, 1 Dec 1998 08:00:00 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 23083 invoked by alias); 1 Dec 1998 15:59:46 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 23055 invoked by uid 0); 1 Dec 1998 15:59:44 -0000 Received: from dialupc216.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.97.216) by omahpop1.omah.uswest.net with SMTP; 1 Dec 1998 15:59:44 -0000 Date: Tue, 1 Dec 1998 09:59:44 -0600 (CST) From: "Open Systems Inc." To: John Saunders cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, John Saunders wrote: > Q1: Why does FreeBSD crash or become totally unstable under > what can only be described as high network load? The ONLY thing I can think of is that people dont know to increase MAXUSERS to keep enough mbuf's avalable for the load they carry. Thats the only thing I have ever seen take down a loaded FBSD server. It just runs out of mbuf's and goes poof. Chris "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12242 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:07:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12224 for ; Tue, 1 Dec 1998 08:07:09 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id KAA55753; Tue, 1 Dec 1998 10:06:33 -0600 (CST) Message-ID: <19981201100633.A55743@Denninger.Net> Date: Tue, 1 Dec 1998 10:06:33 -0600 From: Karl Denninger To: "Open Systems Inc." , John Saunders Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Open Systems Inc. on Tue, Dec 01, 1998 at 09:59:44AM -0600 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's not true. While under attack, a system will consume *outrageous* numbers of buffers. There is no reason to "size" for such events; the fix is as Matt described, in that there is no reason for the system to make available resources that cannot be *productively* consumed. Ergo, dropping the traffic BEFORE it can consume buffers is the correct course of action. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Tue, Dec 01, 1998 at 09:59:44AM -0600, Open Systems Inc. wrote: > On Tue, 1 Dec 1998, John Saunders wrote: > > > Q1: Why does FreeBSD crash or become totally unstable under > > what can only be described as high network load? > > The ONLY thing I can think of is that people dont know to increase > MAXUSERS to keep enough mbuf's avalable for the load they carry. > Thats the only thing I have ever seen take down a loaded FBSD server. > It just runs out of mbuf's and goes poof. > > Chris > > "If you aim the gun at your foot and pull the trigger, it's UNIX's job to > ensure reliable delivery of the bullet to where you aimed the gun (in > this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. > > ===================================| Open Systems FreeBSD Consulting. > FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 > -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 > FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net > http://www.freebsd.org | Consulting, Network Engineering, Security > ===================================| http://open-systems.net > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: 2.6.2 > > mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te > gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC > foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z > d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb > NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv > CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 > b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= > =BBjp > -----END PGP PUBLIC KEY BLOCK----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:20:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13460 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:20:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13455 for ; Tue, 1 Dec 1998 08:20:43 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA04055; Tue, 1 Dec 1998 11:19:58 -0500 (EST) (envelope-from wollman) Date: Tue, 1 Dec 1998 11:19:58 -0500 (EST) From: Garrett Wollman Message-Id: <199812011619.LAA04055@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: "John Saunders" , Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <199812010708.XAA03688@apollo.backplane.com> References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > As far as I can tell, it starves the mbuf pool and/or outgoing > packet queues. More likely, this is a case of receive livelock -- the machine spends all of its time in interrupt mode servicing hardware interrupts and never makes it back down to soft IPL so that the network code can run and actually process the packets. Jeff Mogul at DEC Palo Alto wrote a paper about this a few years back. The right way to fix it is to actively schedule network service, so that packets are dropped in hardware when the machine is overloaded. You can check net.inet.ip.intr_queue_drops to see whether this is in fact happening. > thrown away. Furthermore, if the reply is to a non-existant > IP on the local LAN, the ICMP replies get buffered while > the machine tries to ARP the destination. We should rate-limit ARPs, but don't. > If not, the xmit > traffic goes to the switch which starts collisioning-out packets > when the router beyond the switch saturates. I'm sorry, I can't parse this. > It's a real problem. When you are receiving a 20Kpps > attack you do not want to be transmitting 20Kpps in ICMP > replies to a possibly spoofed address. Then again, when you are receiving 20kpps of legitimate traffic, you still want to behave correctly. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:21:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13566 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:21:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13392 for ; Tue, 1 Dec 1998 08:20:00 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id RAA13896 for ; Tue, 1 Dec 1998 17:19:30 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id RAA26714 for freebsd-current@freebsd.org; Tue, 1 Dec 1998 17:19:27 +0100 (CET) From: Cejka Rudolf Message-Id: <199812011619.RAA26714@kazi.dcse.fee.vutbr.cz> Subject: cvsup problems To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Tue, 1 Dec 1998 17:19:27 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Problems have started one week ago so I'm trying to ask others: When I'm trying to realize cvsup from almost every one cvsup.XX.freebsd.org (de, fi, jp, nl...) server, it ends up with this error message after a while: TreeList failed: Network write failure: Connection lost I'm directly connected to internet (TEN-34, line from Prague into Denmark) without any other problems. But - last seven days cvsup passes only after setting "ifconfig fxp0 mtu 576". (I have only one network interface.) For other things mtu=1500 still works very well. Does anybody have the same problems? It looks as TEN-34 black hole (?), but mtu-magic looks very ill. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14415 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:31:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14405 for ; Tue, 1 Dec 1998 08:31:13 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id KAA55819; Tue, 1 Dec 1998 10:30:44 -0600 (CST) Message-ID: <19981201103044.A55812@Denninger.Net> Date: Tue, 1 Dec 1998 10:30:44 -0600 From: Karl Denninger To: Garrett Wollman , Matthew Dillon Cc: John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812011619.LAA04055@khavrinen.lcs.mit.edu>; from Garrett Wollman on Tue, Dec 01, 1998 at 11:19:58AM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 01, 1998 at 11:19:58AM -0500, Garrett Wollman wrote: > < said: > > > As far as I can tell, it starves the mbuf pool and/or outgoing > > packet queues. > > More likely, this is a case of receive livelock -- the machine spends > all of its time in interrupt mode servicing hardware interrupts and > never makes it back down to soft IPL so that the network code can run > and actually process the packets. Jeff Mogul at DEC Palo Alto wrote a > paper about this a few years back. The right way to fix it is to > actively schedule network service, so that packets are dropped in > hardware when the machine is overloaded. > > You can check net.inet.ip.intr_queue_drops to see whether this is in > fact happening. Possibly. But the situation that Matt is talking about happens QUICKLY, and frequently leads to a hard-lock of the machine. I know what he's talking about, because I've seen it at MCSNet. I've NEVER been able to get a good traceback on what's going on - it happens too quickly. I suspect, however, that it is in fact a DOS attack sourced from the outside. > > thrown away. Furthermore, if the reply is to a non-existant > > IP on the local LAN, the ICMP replies get buffered while > > the machine tries to ARP the destination. > > We should rate-limit ARPs, but don't. Makes sense. > > If not, the xmit > > traffic goes to the switch which starts collisioning-out packets > > when the router beyond the switch saturates. > > I'm sorry, I can't parse this. > > > It's a real problem. When you are receiving a 20Kpps > > attack you do not want to be transmitting 20Kpps in ICMP > > replies to a possibly spoofed address. > > Then again, when you are receiving 20kpps of legitimate traffic, you > still want to behave correctly. > > -GAWollman 20kpps of ICMP traffic?! Surely you jest! -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:41:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15299 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:41:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15292 for ; Tue, 1 Dec 1998 08:41:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id IAA07525; Tue, 1 Dec 1998 08:41:10 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 08:41:10 -0800 (PST) From: Matthew Dillon Message-Id: <199812011641.IAA07525@apollo.backplane.com> To: Karl Denninger Cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> <19981201103044.A55812@Denninger.Net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> -GAWollman : :20kpps of ICMP traffic?! Surely you jest! I wish I were. The hackers have realized over the last year that sending 80 MBps packet attacks using large packets doesn't work anywhere near as well as sending 80 MBps packet attacks using tiny packets that cause ICMP replies. We upgraded our Cisco border routers to all VIP-2 cards 6 months ago *just* so they wouldn't fall over in an attack and were also one of the first to use Cisco's ICMP reply limiting hack, and now we are upgrading them to whatever the next generation card is ( I forget what these new cards are called ). That takes care of attacks against routers. My ICMP patch takes care of attacks against servers. It's only going to get worse when we upgrade our transit links form T3 to OC3. -Matt :Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 08:47:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15847 for freebsd-current-outgoing; Tue, 1 Dec 1998 08:47:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15839 for ; Tue, 1 Dec 1998 08:47:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id IAA07545; Tue, 1 Dec 1998 08:47:17 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 08:47:17 -0800 (PST) From: Matthew Dillon Message-Id: <199812011647.IAA07545@apollo.backplane.com> To: Garrett Wollman Cc: "John Saunders" , Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :You can check net.inet.ip.intr_queue_drops to see whether this is in :fact happening. You asked for it :-) shell2.ba.best.com net.inet.ip.intr_queue_drops: 90 shell3.ba.best.com net.inet.ip.intr_queue_drops: 0 shell4.ba.best.com net.inet.ip.intr_queue_drops: 183 shell5.ba.best.com net.inet.ip.intr_queue_drops: 5504 shell6.ba.best.com net.inet.ip.intr_queue_drops: 16 shell7.ba.best.com net.inet.ip.intr_queue_drops: 497970 shell8.ba.best.com net.inet.ip.intr_queue_drops: 81 shell9.ba.best.com net.inet.ip.intr_queue_drops: 5 shell10.ba.best.com net.inet.ip.intr_queue_drops: 3 shell11.ba.best.com net.inet.ip.intr_queue_drops: 26 shell12.ba.best.com net.inet.ip.intr_queue_drops: 40458 shell13.ba.best.com net.inet.ip.intr_queue_drops: 180670 shell14.ba.best.com net.inet.ip.intr_queue_drops: 0 shell15.ba.best.com net.inet.ip.intr_queue_drops: 3028088 shell16.ba.best.com net.inet.ip.intr_queue_drops: 149220 shell17.ba.best.com net.inet.ip.intr_queue_drops: 1066352 shell18.ba.best.com net.inet.ip.intr_queue_drops: 130 shell2.la.best.com net.inet.ip.intr_queue_drops: 195054 fpage1.ba.best.com net.inet.ip.intr_queue_drops: 39 fpage2.ba.best.com net.inet.ip.intr_queue_drops: 94 fpage3.ba.best.com net.inet.ip.intr_queue_drops: 0 commerce1.ba.best.com net.inet.ip.intr_queue_drops: 0 commerce2.ba.best.com net.inet.ip.intr_queue_drops: 0 commerce5.ba.best.com net.inet.ip.intr_queue_drops: 42 dweb1.ba.best.com net.inet.ip.intr_queue_drops: 0 dweb2.ba.best.com net.inet.ip.intr_queue_drops: 0 dweb3.ba.best.com net.inet.ip.intr_queue_drops: 0 proxy1.ba.best.com net.inet.ip.intr_queue_drops: 171 proxy2.ba.best.com net.inet.ip.intr_queue_drops: 5 proxy3.ba.best.com net.inet.ip.intr_queue_drops: 13 proxy4.ba.best.com net.inet.ip.intr_queue_drops: 0 lists1.best.com net.inet.ip.intr_queue_drops: 99 news1.best.com net.inet.ip.intr_queue_drops: 0 news2.best.com net.inet.ip.intr_queue_drops: 0 nntp1.ba.best.com net.inet.ip.intr_queue_drops: 28 kephalos.best.net net.inet.ip.intr_queue_drops: 0 flea.best.net net.inet.ip.intr_queue_drops: 347249 dns1.ba.best.net net.inet.ip.intr_queue_drops: 493 dns2.ba.best.net net.inet.ip.intr_queue_drops: 2965 dns3.ba.best.net net.inet.ip.intr_queue_drops: 66203 :> IP on the local LAN, the ICMP replies get buffered while :> the machine tries to ARP the destination. : :We should rate-limit ARPs, but don't. ARP's reasonably rate-limited because most subnets are /24's, it's the packets queued up waiting for the ARP to resolve that are the problem. :> If not, the xmit :> traffic goes to the switch which starts collisioning-out packets :> when the router beyond the switch saturates. : :I'm sorry, I can't parse this. An etherswitch has an internal packet buffer. If the buffer fills up the switch will generate a collision on packets being received to try to slow down the transmitters (by forcing backoff/retry) while the packet buffer drains. :Then again, when you are receiving 20kpps of legitimate traffic, you :still want to behave correctly. : :-GAWollman My patch doesn't touch legit traffic, only ICMP *error* replies that the machine tries to generate. -Matt :-- :Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same :wollman@lcs.mit.edu | O Siem / The fires of freedom :Opinions not those of| Dance in the burning flame :MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 09:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18081 for freebsd-current-outgoing; Tue, 1 Dec 1998 09:06:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18073 for ; Tue, 1 Dec 1998 09:06:34 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA04251; Tue, 1 Dec 1998 12:05:28 -0500 (EST) (envelope-from wollman) Date: Tue, 1 Dec 1998 12:05:28 -0500 (EST) From: Garrett Wollman Message-Id: <199812011705.MAA04251@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <199812011647.IAA07545@apollo.backplane.com> References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> <199812011647.IAA07545@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > :You can check net.inet.ip.intr_queue_drops to see whether this is in > :fact happening. > You asked for it :-) > shell15.ba.best.com net.inet.ip.intr_queue_drops: 3028088 > shell17.ba.best.com net.inet.ip.intr_queue_drops: 1066352 I'd say you were getting some serious livelock here... (Or else the machines were too busy servicing other, non-network, interrupts which took precedence.) > ARP's reasonably rate-limited because most subnets are /24's, it's > the packets queued up waiting for the ARP to resolve that are the > problem. That doesn't limit the rate, that only limits the number of machines which might potentially be annoyed by an ARP storm. However, in looking at the code, we do effectively rate-limit our ARPs, contrary to what I thought; the ARP code will refuse to send more than five broadcasts in 20 seconds (per destination). This doesn't help me all that much (I have twelve /16s), but is probably good enough for most users. > An etherswitch has an internal packet buffer. If the buffer fills up the > switch will generate a collision on packets being received to try to > slow down the transmitters (by forcing backoff/retry) while the packet > buffer drains. Well, maybe your vendor's products violate the standard in this way. I always connect network-intensive devices at full-duplex, so the only back-pressure comes from 802.3x PAUSE frames (yeah, right). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 09:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18867 for freebsd-current-outgoing; Tue, 1 Dec 1998 09:12:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18858 for ; Tue, 1 Dec 1998 09:12:03 -0800 (PST) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with SMTP id MAA04733 for ; Tue, 1 Dec 1998 12:11:50 -0500 (EST) Date: Tue, 1 Dec 1998 12:12:08 -0500 (EST) From: steven To: current@FreeBSD.ORG Subject: Re: top/w/vmstat weirdness -- ME TOO! (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the reply's.. a kernel recompile did it. my win/tv card support would not compile in but after some reading of multimedia list got that fixed. thanks gang.. steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 09:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19251 for freebsd-current-outgoing; Tue, 1 Dec 1998 09:15:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19240 for ; Tue, 1 Dec 1998 09:14:59 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id LAA55916; Tue, 1 Dec 1998 11:14:24 -0600 (CST) Message-ID: <19981201111424.A55857@Denninger.Net> Date: Tue, 1 Dec 1998 11:14:24 -0600 From: Karl Denninger To: Matthew Dillon Cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> <19981201103044.A55812@Denninger.Net> <199812011641.IAA07525@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812011641.IAA07525@apollo.backplane.com>; from Matthew Dillon on Tue, Dec 01, 1998 at 08:41:10AM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 01, 1998 at 08:41:10AM -0800, Matthew Dillon wrote: > > :> > :> -GAWollman > : > :20kpps of ICMP traffic?! Surely you jest! > > I wish I were. I was talking about 20kpps of LEGITIMATE ICMP traffic :-) -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 09:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20996 for freebsd-current-outgoing; Tue, 1 Dec 1998 09:30:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20991 for ; Tue, 1 Dec 1998 09:30:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA09274; Tue, 1 Dec 1998 09:30:09 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 09:30:09 -0800 (PST) From: Matthew Dillon Message-Id: <199812011730.JAA09274@apollo.backplane.com> To: Karl Denninger Cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: <005b01be1cf6$e6368da0$6cb611cb@saruman.scitec.com.au> <199812010708.XAA03688@apollo.backplane.com> <199812011619.LAA04055@khavrinen.lcs.mit.edu> <19981201103044.A55812@Denninger.Net> <199812011641.IAA07525@apollo.backplane.com> <19981201111424.A55857@Denninger.Net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :> :20kpps of ICMP traffic?! Surely you jest! :> :> I wish I were. : :I was talking about 20kpps of LEGITIMATE ICMP traffic :-) Oh. no. 20Kpps of illegitimate ICMP traffic. It would be pretty hard to get even 10pps of legitimate ICMP traffic. Our most heavily loaded web server only generates 0.5 pps or so in ICMP packets and receives maybe 1 pps in ICMP. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 09:46:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22895 for freebsd-current-outgoing; Tue, 1 Dec 1998 09:46:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22132; Tue, 1 Dec 1998 09:41:25 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id SAA04431; Tue, 1 Dec 1998 18:38:11 +0100 Message-ID: <36642982.9B0D6B66@we.lc.ehu.es> Date: Tue, 01 Dec 1998 18:38:10 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: obrien@NUXI.com CC: Nathan Dorfman , freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: [patch] libmytinfo breaks vim-5.3 port, maybe others? References: <19981023205115.A5357@rtfm.net> <19981129004517.B28637@nuxi.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with > > libmytinfo. At first I thought it was vim breakage, or Motif/Athena > > or even X11 breakage. But read on: > > ..snip.. > > > Anyway, I noticed something weird: > > > > libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000) > > This is automatically linked in if libncurses is being used. > Apply this patch to the vim5 port's Makefile: --------------------------------Cut------------------------------------ --- Makefile.orig Thu Oct 15 02:35:11 1998 +++ Makefile Tue Dec 1 18:12:12 1998 @@ -29,7 +29,7 @@ WRKSRC= ${WRKDIR}/${DISTNAME}/src PATCH_DIST_ARGS= -d ${WRKDIR}/${DISTNAME} --forward --quiet -E ${PATCH_DIST_STRIP} -MAKE_FLAGS= CONF_ARGS="--prefix=${PREFIX} --enable-max-features" -f +MAKE_FLAGS= CONF_ARGS="--prefix=${PREFIX} --enable-max-features --with-tlib=termlib" -f ALL_TARGET= # MAN1= vim.1 xxd.1 ectags.1 --------------------------------Cut------------------------------------ This patch forces linking against termlib instead of ncurses. Obviously this is only a workaround for a problem in the ncurses library. The vim5.3's "configure" script checks for tgetent() in ncurses. It's found in the 3.0 libncurses (so vim is linked with it), but this check fails under FreeBSD 2.2.x, so it's linked with libtermlib. BTW, I've just found a flaw related to the termcap and termlib libraries in /usr/lib under FreeBSD-3.0-RELEASE. Watch the output of ls -li *term*: 23269 -r--r--r-- 2 root wheel 18522 17 oct 18:59 libtermcap.a 23271 lrwxrwxrwx 1 root wheel 15 9 nov 17:01 libtermcap.so -> libtermcap.so.2 23270 -r--r--r-- 1 root wheel 15108 17 oct 18:59 libtermcap.so.2 23682 -r--r--r-- 2 root wheel 19760 16 oct 18:06 libtermcap_p.a 23269 -r--r--r-- 2 root wheel 18522 17 oct 18:59 libtermlib.a 23272 lrwxrwxrwx 1 root wheel 15 9 nov 17:01 libtermlib.so -> libtermcap.so.2 23682 -r--r--r-- 2 root wheel 19760 16 oct 18:06 libtermlib_p.a There is no libtermlib.so.2!! This explains the output of the command "ldconfig -r | fgrep term": 7:-ltermcap.2 => /usr/lib/libtermcap.so.2 libtermlib.so.2 does not appear. It seems there is a bug in the installation script of this libraries. Until it's fixed, the solution is easy: cd /usr/lib rm libtermlib.so ln libtermcap.so.2 libtermlib.so.2 ln -s libtermlib.so.2 libtermlib.so And that's all. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 10:18:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27192 for freebsd-current-outgoing; Tue, 1 Dec 1998 10:18:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27175 for ; Tue, 1 Dec 1998 10:18:14 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 4366 invoked by alias); 1 Dec 1998 18:17:49 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 4344 invoked by uid 0); 1 Dec 1998 18:17:48 -0000 Received: from dialupc216.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.97.216) by omahpop1.omah.uswest.net with SMTP; 1 Dec 1998 18:17:48 -0000 Date: Tue, 1 Dec 1998 12:17:48 -0600 (CST) From: "Open Systems Inc." To: Karl Denninger cc: John Saunders , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <19981201100633.A55743@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, Karl Denninger wrote: > That's not true. > > While under attack, a system will consume *outrageous* numbers of buffers. > There is no reason to "size" for such events; the fix is as Matt described, > in that there is no reason for the system to make available resources that > cannot be *productively* consumed. I knew someone was gonna say something. :-) I meant to specifically answer his comment about heavy load not a DoS. Although a DoS *will* generate a large load as you state I was merely trying to answer his specific question of large load not a DoS making FBSD fall over. Chris "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 10:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28541 for freebsd-current-outgoing; Tue, 1 Dec 1998 10:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28532 for ; Tue, 1 Dec 1998 10:28:04 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial8-228.netcologne.de [195.14.235.228]) by mail2.netcologne.de (8.9.1/8.9.1) with ESMTP id TAA08793; Tue, 1 Dec 1998 19:22:23 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id TAA08092; Tue, 1 Dec 1998 19:23:30 +0100 (CET) (envelope-from marc) Date: Tue, 1 Dec 1998 19:23:30 +0100 (CET) Message-Id: <199812011823.TAA08092@oranje.my.domain> From: Marc van Woerkom To: mike@smith.net.au CC: jkh@zippy.cdrom.com, mike@smith.net.au, forrie@forrie.com, freebsd-current@FreeBSD.ORG In-reply-to: <199811260553.VAA00916@dingo.cdrom.com> (message from Mike Smith on Wed, 25 Nov 1998 21:53:40 -0800) Subject: KLD - what's the idea? Reply-to: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We should talk them [OSS] through the conversion to a KLD module > as soon as we're sure what they need to look like. 8) Are KLD modules intended for run-time loadable drivers? What are the (rough) plans for this mechanism? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 10:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29574 for freebsd-current-outgoing; Tue, 1 Dec 1998 10:38:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29565 for ; Tue, 1 Dec 1998 10:38:15 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id SAA03350; Tue, 1 Dec 1998 18:37:56 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma003333; Tue, 1 Dec 98 18:37:54 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id SAA19145 for freebsd-current@freebsd.org; Tue, 1 Dec 1998 18:37:53 GMT From: Geoff Buckingham Message-Id: <199812011837.SAA19145@gti.noc.demon.net> Subject: QLogic QLA1240 support To: freebsd-current@FreeBSD.ORG Date: Tue, 1 Dec 1998 18:37:53 +0000 (GMT) Reply-To: geoffb@demon.net X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The QLA1240, which is the 64bit PCI version of the QLA1042 doesn't seem to get recognised by 3.0 is anybody working on this. It may not help that I am using it in a 32 bit slot as ASUS seem to have changed the spec of their two PII board, to not include a 64bit slot. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 10:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01346 for freebsd-current-outgoing; Tue, 1 Dec 1998 10:50:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01334; Tue, 1 Dec 1998 10:50:50 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA05736; Tue, 1 Dec 1998 19:50:30 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA22081; Tue, 1 Dec 1998 19:50:29 +0100 (MET) Message-ID: <19981201195028.A21015@follo.net> Date: Tue, 1 Dec 1998 19:50:28 +0100 From: Eivind Eklund To: Matthew Dillon , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. References: <199812010551.VAA02953@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812010551.VAA02953@apollo.backplane.com>; from Matthew Dillon on Mon, Nov 30, 1998 at 09:51:45PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 09:51:45PM -0800, Matthew Dillon wrote: > Now that everyone is backfrom thanksgiving and 2.2.8 is out the > door, I'd like to commit the following changes to -current. These > are as previously discussed and the changes have also been running > on most of BEST's machines for a couple of weeks now so I'd like > to commit them. > > I'd like someone to sign off on the concept. Eivind? Bruce? Jordan? [on running identd as kmem, ntalkd as tty, and bind as bind/bind] Sounds good to me, as long as it does not require changes to existing installations (which I couldn't see it needing from your description). I'm somewhat surprised at the getuid() test in ntalkd being there at all - it seems like this should have been done with permissions instead of getuid(), and shouldn't be needed anyway. However, I don't have the SCCS repository (yet), so I can't see why it was introduced - it has been there (in slightly changing incarnation) since 4.4 lite. Your user/group suggestion looks good - too bad operator is screwed up. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 10:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02030 for freebsd-current-outgoing; Tue, 1 Dec 1998 10:54:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA01998 for ; Tue, 1 Dec 1998 10:54:13 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 29021 invoked by uid 1001); 1 Dec 1998 18:53:50 +0000 (GMT) To: dillon@apollo.backplane.com Cc: karl@Denninger.Net, wollman@khavrinen.lcs.mit.edu, john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: Your message of "Tue, 1 Dec 1998 09:30:09 -0800 (PST)" References: <199812011730.JAA09274@apollo.backplane.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 01 Dec 1998 19:53:50 +0100 Message-ID: <29019.912538430@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh. no. 20Kpps of illegitimate ICMP traffic. It would be pretty > hard to get even 10pps of legitimate ICMP traffic. Our most heavily > loaded web server only generates 0.5 pps or so in ICMP packets and > receives maybe 1 pps in ICMP. As another example, UNINETT has a 155 Mbps IP over SDH connection to the Internet. We use rate limiting (Cisco CAR) for ICMP traffic, and currently have the limit set to 160 kbps. In practice, this is more than enough. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 11:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06230 for freebsd-current-outgoing; Tue, 1 Dec 1998 11:29:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06224 for ; Tue, 1 Dec 1998 11:29:11 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id UAA06203; Tue, 1 Dec 1998 20:28:58 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA22253; Tue, 1 Dec 1998 20:28:58 +0100 (MET) Message-ID: <19981201202857.B21015@follo.net> Date: Tue, 1 Dec 1998 20:28:57 +0100 From: Eivind Eklund To: dg@root.com, John Fieber Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... References: <199812011415.GAA29284@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812011415.GAA29284@root.com>; from David Greenman on Tue, Dec 01, 1998 at 06:15:23AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 01, 1998 at 06:15:23AM -0800, David Greenman wrote: > >Hmm. Not quite textbook dying daemons symptoms. Have a look at > >pr/8183. > > Regarding that PR, I sure wish someone would come up with something better > than writing to a pipe to store temporary state information. As far as I know, this is the 'canonical way' of handling that case. However, I'm unable to find any references - it seems to pure programmer lore. No matter how inelegant it is, I think it should be committed. Any fix is better than no fix. Do you mind if I do it? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 11:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08510 for freebsd-current-outgoing; Tue, 1 Dec 1998 11:47:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08497 for ; Tue, 1 Dec 1998 11:47:28 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA03930; Tue, 1 Dec 1998 11:46:12 -0800 Date: Tue, 1 Dec 1998 11:46:12 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: geoffb@demon.net cc: freebsd-current@FreeBSD.ORG Subject: Re: QLogic QLA1240 support In-Reply-To: <199812011837.SAA19145@gti.noc.demon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will be working on it. I have the Firmware specification. I don't have a board. If someone can loan me a board this will happen quicker. On Tue, 1 Dec 1998, Geoff Buckingham wrote: > > The QLA1240, which is the 64bit PCI version of the QLA1042 doesn't > seem to get recognised by 3.0 is anybody working on this. > > It may not help that I am using it in a 32 bit slot as ASUS seem to have > changed the spec of their two PII board, to not include a 64bit slot. > > -- > GeoffB > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 12:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13218 for freebsd-current-outgoing; Tue, 1 Dec 1998 12:29:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13212 for ; Tue, 1 Dec 1998 12:29:12 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id PAA26176 for ; Tue, 1 Dec 1998 15:28:58 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20485; Tue, 1 Dec 1998 15:28:57 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.1/8.9.1) id PAA05487; Tue, 1 Dec 1998 15:28:57 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <199812012028.PAA05487@dean.pc.sas.com> Subject: Help --- panic: vm_page_unwire: invalid wire count: 0 To: freebsd-current@FreeBSD.ORG Date: Tue, 1 Dec 1998 15:28:57 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA13214 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently got this panic on an 8/27 snap 3.0 current machine: panic: vm_page_unwire: invalid wire count: 0 Looking through the PR's I see that there is one open on this (PR #5839), opened way back on Feb 24 of this year. This is the second time my machine has crashed in this way in a month's time. Can anyone tell me if this bug has been fixed in current, or does it still linger? Thanks, -Brian -- Brian Dean, brdean@unx.sas.com P.S. - If anyone needs more information about the panic, an examination of the crash dump reveals: ------------------------------------------------------------ [root@bb01f39]:/crashdump- gdb -k -c vmcore.0 kernel.0 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2273280 initial pcb at 204a68 panicstr: vm_page_unwire: invalid wire count: %d panic messages: --- panic: vm_page_unwire: invalid wire count: 0 syncing disks... 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 giving up dumping to dev 20001, offset 262144 dump 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xf0117937 in boot () (kgdb) backtrace #0 0xf0117937 in boot () #1 0xf0117bf6 in panic () #2 0xf01b834b in vm_page_unwire () #3 0xf01313ec in vfs_vmio_release () #4 0xf0131a37 in getnewbuf () #5 0xf0132177 in getblk () #6 0xf01606ba in nfs_getcacheblk () #7 0xf015f503 in nfs_bioread () #8 0xf0184bd0 in nfs_read () #9 0xf013d9ad in vn_read () #10 0xf01201bd in read () #11 0xf01c96ff in syscall () #12 0x20105d21 in ?? () #13 0x200f3a35 in ?? () #14 0x200da7b7 in ?? () #15 0xdf48 in ?? () #16 0x6e1c in ?? () #17 0x7bdf in ?? () #18 0x1b42 in ?? () #19 0x2187d in ?? () #20 0x175f6 in ?? () #21 0x41086 in ?? () #22 0x69c20 in ?? () #23 0x503a5 in ?? () #24 0x20d35 in ?? () #25 0x23a3d in ?? () #26 0x249c6 in ?? () #27 0x23fc1 in ?? () #28 0x239b3 in ?? () #29 0x16761 in ?? () #30 0x17275 in ?? () #31 0x6cb18 in ?? () #32 0x1782c in ?? () #33 0x1099 in ?? () (kgdb) quit [root@bb01f39]:/crashdump- ------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 12:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13679 for freebsd-current-outgoing; Tue, 1 Dec 1998 12:33:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13672 for ; Tue, 1 Dec 1998 12:33:08 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id VAA22135 for ; Tue, 1 Dec 1998 21:32:42 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id VAA04732 for freebsd-current@freebsd.org; Tue, 1 Dec 1998 21:32:41 +0100 (CET) From: Cejka Rudolf Message-Id: <199812012032.VAA04732@kazi.dcse.fee.vutbr.cz> Subject: Re: cvsup problems To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Tue, 1 Dec 1998 21:32:41 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Problems have started one week ago so I'm trying to ask others: > > When I'm trying to realize cvsup from almost every one cvsup.XX.freebsd.org > (de, fi, jp, nl...) server, it ends up with this error message > after a while: > > TreeList failed: Network write failure: Connection lost > > I'm directly connected to internet (TEN-34, line from Prague into Denmark) ^^^^^^^ ***** Argh! I'm sorry - it had to be _Germany_ (& *.Teleglobe.net)! >From Czech Republic into Germany... ***** > without any other problems. But - last seven days cvsup passes only after > setting "ifconfig fxp0 mtu 576". (I have only one network interface.) > For other things mtu=1500 still works very well. > > Does anybody have the same problems? It looks as TEN-34 black hole (?), > but mtu-magic looks very ill. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 12:48:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15027 for freebsd-current-outgoing; Tue, 1 Dec 1998 12:48:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15021 for ; Tue, 1 Dec 1998 12:48:46 -0800 (PST) (envelope-from pedophiles@vszbr.cz) Received: from localhost (pedophiles@localhost) by coredump.int.tele.dk (8.8.5/8.8.5) with SMTP id VAA00691; Tue, 1 Dec 1998 21:16:20 +0100 X-Authentication-Warning: coredump.int.tele.dk: pedophiles owned process doing -bs Date: Tue, 1 Dec 1998 21:16:19 +0100 (CET) From: BARRY BOUWSMA IS A PEDOPHILE X-Sender: pedophiles@coredump.int.tele.dk To: Cejka Rudolf cc: freebsd-current@FreeBSD.ORG Subject: Re: cvsup problems In-Reply-To: <199812011619.RAA26714@kazi.dcse.fee.vutbr.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Dec 1998, Cejka Rudolf wrote: > When I'm trying to realize cvsup from almost every one cvsup.XX.freebsd.org > > TreeList failed: Network write failure: Connection lost > > I'm directly connected to internet (TEN-34, line from Prague into Denmark) Um, not to actually answer your question, but you aren't... A traceroute to cvsup.dk.freebsd.org will show your path goes direct from Praha to the US via Teleglobe (recently installed), and in fact, it seems that traffic from CZ to most European sites is routed by the US nowadays. This link via the US has extremely poor performance, as it took me more than an hour to transfer a file smaller than 150k last weekend during nighttime hours, and interactive work often had a lag in minutes. > Does anybody have the same problems? It looks as TEN-34 black hole (?), I'm not sure if this poor performance is the cause of the problems you are seeing, but it certainly doesn't help... See if there is another cvsup site that does not get preferential treatment via the US (maybe fr?), as this Teleglobe link is clearly overloaded with the RTTs and packet losses I was seeing last week from Brno. Barry Bouwsma, Tele Damnark Internet Brno Outpost (this is an invalid e-mail address, do not reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 12:58:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15516 for freebsd-current-outgoing; Tue, 1 Dec 1998 12:58:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15510; Tue, 1 Dec 1998 12:58:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA10204; Tue, 1 Dec 1998 12:57:43 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 12:57:43 -0800 (PST) From: Matthew Dillon Message-Id: <199812012057.MAA10204@apollo.backplane.com> To: Eivind Eklund Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. References: <199812010551.VAA02953@apollo.backplane.com> <19981201195028.A21015@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Now that everyone is backfrom thanksgiving and 2.2.8 is out the :> door, I'd like to commit the following changes to -current. These :> are as previously discussed and the changes have also been running :> on most of BEST's machines for a couple of weeks now so I'd like :> to commit them. :> :> I'd like someone to sign off on the concept. Eivind? Bruce? Jordan? : :[on running identd as kmem, ntalkd as tty, and bind as bind/bind] : :Sounds good to me, as long as it does not require changes to existing :installations (which I couldn't see it needing from your description). I'm :somewhat surprised at the getuid() test in ntalkd being there at all - it :... Excellent. I'll commit it in. I don't expect it will have any effect on pre-existing systems since most people customize their passwd/group/inetd.conf files rather then sync them from /usr/src/etc -Matt :Eivind. :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-security" in the body of the message Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 13:43:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20559 for freebsd-current-outgoing; Tue, 1 Dec 1998 13:43:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20554; Tue, 1 Dec 1998 13:43:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA10640; Tue, 1 Dec 1998 13:43:33 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 13:43:33 -0800 (PST) From: Matthew Dillon Message-Id: <199812012143.NAA10640@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've committed the kmem, tty, and bind sandboxes. This is inclusive of changing rc.conf to run bind in the sandbox which could be somewhat controversial but, I think, necessary. I accidently created a /usr/src/etc/namedb/s directory and cvs add'd it, then realized that it shouldn't be in the source tree (mtree handles creating it in production). I've cvs deleted it but it will not commit the deletion to the server. i.e. 'cvs commit' thinks there is nothing to do. Very odd. I'd appreciate it if a cvs god looked at that! Added bonus: comsat can also be run in the tty sandbox, and it is enabled by default so that's good! Thanks, -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 13:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22478 for freebsd-current-outgoing; Tue, 1 Dec 1998 13:59:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22472 for ; Tue, 1 Dec 1998 13:59:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id OAA00603 for freebsd-current@freebsd.org; Tue, 1 Dec 1998 14:07:13 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812012207.OAA00603@troutmask.apl.washington.edu> Subject: Crash dump howto? To: freebsd-current@FreeBSD.ORG Date: Tue, 1 Dec 1998 14:07:13 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone care to share their method on getting a kernel crash dump on a very recent -current tree? Hardware: Micron Millenia Pro2+ (dual 200 MHz Pentium Pro), 256 MB memory Adaptec 2940 Ultra SCSI controller, Seagate ST34371N 4.1MB SCSI2 drive, Quantum Lightning 730S 700MB SCSI2 drive, Plextor CD-ROM PX-12CS I'm running an ELF SMP kernel, and I have "options DDB" and "options AHC_ALLOW_MEMIO". Kernels have been configured with the -g to config(8). [This reminds me, how does one strip an ELF kernel?] da0 is the Seagate drive, and da1 is the Quantum drive. Under heavy load: dev=0x20405, bno = 13, bsize = 8192, size = 8192, fs = /usr panic: ffs_blkfree: bad size mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0, _in_Debugger.98 db> trace _Debugger() at _Debugger+0x35 _panic() at _panic+0x9f _ffs_blkfree() at _ffs_blkfree+0xc2 _ffs_reallocblks() at _ffs_reallocblks+0x420 _cluster_write() at _cluster_write+0x15f _ffs_write() at _ffs_write+0x56f _vn_write() at _vn_write+0xef _write() at _write+0xba _syscall() at _syscall+0x187 _Xinit0x80_syscall at _Xinit0x80_syscall+0x4c db>panic panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on CPU #1 (da1:ahc0:0:2:0) SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:2:0) error code 0 dumping to dev 409, offset 907232 Fatal trap 12: page fault while in kernel mode mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x20 fault code = supervisor read, page not present instruction pointer = 0x8:0x20 stack pointer = 0x10:0xf9232998 frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32, 1, gran 1 process eflags = interrupt enabled, resume, IOPL = 0 current process = 95350 (procmail) interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code = 0 Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> panic Reach for reset button. I have tried dumpon /dev/da0s1b dumpon /dev/da1s1b With appropriate disklabels, these are swap partitions of 500 and 700 MBs. My last attempt was dumpon -v /dev/da1b dumpon: crash dumps to /dev/da1b (4, 9) -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 14:09:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23678 for freebsd-current-outgoing; Tue, 1 Dec 1998 14:09:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23673 for ; Tue, 1 Dec 1998 14:09:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA10986; Tue, 1 Dec 1998 14:09:10 -0800 (PST) (envelope-from dillon) Date: Tue, 1 Dec 1998 14:09:10 -0800 (PST) From: Matthew Dillon Message-Id: <199812012209.OAA10986@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: panic - page fault while in kernel mode. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Our -current NNTP box crashed for the first time after a month of uptime and I got a crash dump. The kernel that crashed was about 30 days old. I'm going to load up the most recent kernel tonight. This posting is mainly informational. I presume that the problem is a very small timing window somewhere. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... "ps" -- when kernel debugging, type out a ps-like listing of active processes. IdlePTD 11493376 initial pcb at 2280b8 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 fault virtual address = 0x2a5c4769 fault code = supervisor write, page not present instruction pointer = 0x8:0xf01f05cf stack pointer = 0x10:0xfc682e68 frame pointer = 0x10:0xfc682e74 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 15034 (diablo) interrupt mask = <- SMP: XXX panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 panic: from debugger mp_lock = 01000003; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 dumping to dev 401, offset 524288 dump 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=0x104) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) back #0 boot (howto=0x104) at ../../kern/kern_shutdown.c:268 #1 0xf01348a4 in panic (fmt=0xf0113e78 "from debugger") at ../../kern/kern_shutdown.c:430 #2 0xf0113e95 in db_panic (addr=0xf01f05cf, have_addr=0x0, count=0xffffffff, modif=0xfc682ce4 "") at ../../ddb/db_command.c:432 #3 0xf0113d75 in db_command (last_cmdp=0xf02144b4, cmd_table=0xf0214314, aux_cmd_tablep=0xf0225370) at ../../ddb/db_command.c:332 #4 0xf0113f02 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0116613 in db_trap (type=0xc, code=0x0) at ../../ddb/db_trap.c:71 #6 0xf01e1a14 in kdb_trap (type=0xc, code=0x0, regs=0xfc682e2c) at ../../i386/i386/db_interface.c:157 #7 0xf01f385d in trap_fatal (frame=0xfc682e2c) at ../../i386/i386/trap.c:874 #8 0xf01f328c in trap_pfault (frame=0xfc682e2c, usermode=0x0) at ../../i386/i386/trap.c:772 #9 0xf01f2edf in trap (frame={tf_es = 0xf0150010, tf_ds = 0xf2800010, tf_edi = 0x2a58f000, tf_esi = 0xfc62f160, tf_ebp = 0xfc682e74, tf_isp = 0xfc682e54, tf_ebx = 0x52513d32, tf_edx = 0xf14ea120, tf_ecx = 0x52513d32, tf_eax = 0x2a5c4743, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xf01f05cf, tf_cs = 0x8, tf_eflags = 0x10202, tf_esp = 0x2a58f000, tf_ss = 0x52513d32}) at ../../i386/i386/trap.c:396 #10 0xf01f05cf in pmap_remove_pte (pmap=0xfc62f160, ptq=0xefca963c, va=0x2a58f000) at ../../i386/i386/pmap.c:1794 #11 0xf01f0bfc in pmap_enter (pmap=0xfc62f160, va=0x2a58f000, pa=0x7a19000, prot=0x5, wired=0x0) at ../../i386/i386/pmap.c:2247 #12 0xf01cf866 in vm_fault (map=0xfc62f100, vaddr=0x2a58f000, fault_type=0x1, fault_flags=0x0) at ../../vm/vm_fault.c:725 #13 0xf01f3222 in trap_pfault (frame=0xfc682fbc, usermode=0x1) at ../../i386/i386/trap.c:753 #14 0xf01f2d63 in trap (frame={tf_es = 0xefbf0027, tf_ds = 0xfc680027, tf_edi = 0x1, tf_esi = 0xfe8, tf_ebp = 0xefbfd880, tf_isp = 0xfc682fe4, tf_ebx = 0x1000, tf_edx = 0x2a58e000, tf_ecx = 0x0, tf_eax = 0x76d8, tf_trapno = 0xc, tf_err = 0x4, tf_eip = 0x804a740, tf_cs = 0x1f, tf_eflags = 0x10297, tf_esp = 0xefbfd814, tf_ss = 0x27}) at ../../i386/i386/trap.c:317 #15 0x804a740 in ?? () #16 0x804945e in ?? () #17 0x8048df9 in ?? () #18 0x8048801 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 14:26:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25872 for freebsd-current-outgoing; Tue, 1 Dec 1998 14:26:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25861 for ; Tue, 1 Dec 1998 14:26:28 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA12666 for freebsd-current@FreeBSD.ORG; Tue, 1 Dec 1998 23:26:08 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CD33E1536; Tue, 1 Dec 1998 22:52:14 +0100 (CET) Date: Tue, 1 Dec 1998 22:52:14 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... Message-ID: <19981201225214.A12792@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from garman@earthling.net on Tue, Dec 01, 1998 at 09:30:44AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4856 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to garman@earthling.net: > and to those who believe that this bug is only caused when one is "near > swap capacity" -- the swapinfo above would refute that :) Another datapoint: I've seen the message "add more swap: 386 MB" on a machine with 192 MB RAM + 192 MB swap, swap being used at less than one MB (!). I was forced to restart inetd. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 14:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28054 for freebsd-current-outgoing; Tue, 1 Dec 1998 14:43:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28049 for ; Tue, 1 Dec 1998 14:43:30 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA05595; Tue, 1 Dec 1998 17:46:03 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 1 Dec 1998 17:46:03 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: <19981201225214.A12792@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, Ollivier Robert wrote: > According to garman@earthling.net: > > and to those who believe that this bug is only caused when one is "near > > swap capacity" -- the swapinfo above would refute that :) > > Another datapoint: I've seen the message "add more swap: 386 MB" on a > machine with 192 MB RAM + 192 MB swap, swap being used at less than > one MB (!). > > I was forced to restart inetd. Has anyone thought that the problem is that when inetd incorrectly handles a signal and then allocates memory, the memory it allocates could perhaps cause a massive overcommit because of heap corruption? The overcommit wouldn't show up in swap until pages are faulted in, correct, but could still cause problems on the box. This sorta makes sense as inetd is run as root. So basically inetd's heap is messed up, and you also get a memory problem. Is there any chance that this may be the problem? Or am I wrong as usual? :/ Why can't inetd wrapper malloc so that it sends all signals to "generic" handlers while it's twiddling the heap so that the signals are reposted later. Considering that signals don't carry and context delaying them until a more safe time could work. Anyone who feels obligated to shout "show me the diffs", welp, i'll look into that when i can, if it will even make a difference. I also don't see a need for a pipe to handle context of signals. (in reference to the PR) -Alfred > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 15:35:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03894 for freebsd-current-outgoing; Tue, 1 Dec 1998 15:35:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03882 for ; Tue, 1 Dec 1998 15:35:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00825; Tue, 1 Dec 1998 15:33:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812012333.PAA00825@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: David Greenman , freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-reply-to: Your message of "Mon, 30 Nov 1998 23:26:26 PST." <199812010726.XAA03791@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 15:32:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :general scheme implemented perhaps inside the ipfw framework would be more > :appropriate. I also generally like to avoid compile time options for things > :like this, but I"m sympathetic for performance reducing enhancements. > : > :-DG > > I figure we would make it the default in 6 months to a year, but > we should have it optioned initially so people can play with it > and also because it defaults to enabled when optioned-in, which I > think is important. Just a consideration; if possible, make it run-time tunable with a boolean sysctl variable. (ie. if the 'off' case is comparable to the 'optioned-out' case in terms of speed.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 15:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04888 for freebsd-current-outgoing; Tue, 1 Dec 1998 15:44:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04878 for ; Tue, 1 Dec 1998 15:44:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA06848; Mon, 30 Nov 1998 16:41:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812010041.QAA06848@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jos Backus cc: current@FreeBSD.ORG Subject: Re: your mail In-reply-to: Your message of "Mon, 30 Nov 1998 18:03:20 +0100." <19981130180320.F67289@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Nov 1998 16:41:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Nov 29, 1998 at 01:14:30AM -0800, Mike Smith wrote: > > There's also an online help system that's mostly functional; I realised that > > I needed to work out how to sort the common and architecture-specific help > > together into one file such that subtopic information is in the right place; > > this is going to need a small program to do the work (any Perl hackers > > looking for a quick job are invited to apply). > > *Raises hand* Care to elaborate on what is needed here? Nick Hibma has already thrown me something that looks like it'll do the job. I'll commit it shortly I hope, and you can all swarm over it and argue about what could be improved. 8) Thanks for all the quick responses! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 15:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05165 for freebsd-current-outgoing; Tue, 1 Dec 1998 15:44:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05144; Tue, 1 Dec 1998 15:44:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA07019; Mon, 30 Nov 1998 17:24:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812010124.RAA07019@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: mike@smith.net.au, current@FreeBSD.ORG, jc@irbs.com, smp@FreeBSD.ORG Subject: Re: Dog Sloooow SMP In-reply-to: Your message of "Tue, 01 Dec 1998 02:33:53 +1100." <199811301533.CAA00461@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Nov 1998 17:24:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >No idea. I've received verification that fixing this for all 686-class > >> >CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to > >> >impact performance there), so the tests are now generalised for the > >> >entire 686-class. > >> > >> It's only OK for MII's because of various `#if 0's and `#ifdef SMP's > >> that prevent non-OK code from running on MII's. > > > >Care to comment on which operations aren't OK? I did ask for this in > >the review phase, with no feedback. > > Most wrmsr()s and rdmsr()s. I must admit I'd hoped that you would interpret this as "please identify those operations that are not OK". It's obvious that some are and some aren't, but not actually identifying *which* ones is not helpful. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 16:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09874 for freebsd-current-outgoing; Tue, 1 Dec 1998 16:09:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09867 for ; Tue, 1 Dec 1998 16:09:04 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40355>; Wed, 2 Dec 1998 11:08:06 +1100 Date: Wed, 2 Dec 1998 11:08:43 +1100 From: Peter Jeremy Subject: Name cache questions. To: freebsd-current@FreeBSD.ORG Message-Id: <98Dec2.110806est.40355@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been studying the name cache code (in 3.0-RELEASE), trying to see if I can improve the hit rate. Looking at the code (in kern/vfs_cache.c) it's not clear to me how the cache is managed. In several cases, the comments appear at variance to the code. 1) According to the comments, the name cache is LRU. This implies that cache_lookup() should re-order matched entries to bring the match to the `most recently used' position. This is done only for negative matches. 2) There doesn't appear to be any limit on the size of the number of cache entries - only negative entries are pruned limit the number of negative entries to 1/ncnegfactor of the total entries. 3) cache_lookup() includes the comment `We don't do this if the segment name is long'. Neither cache_lookup(), nor any of its callers appear to include code to check the segment name length (other than to NAME_MAX). 4) cache_purge() includes the comment `If the v_id wraps around, we need to ditch the entire cache'. The code doesn't check for wrap-around, it simply avoids v_id == 0 and re-using the existing v_id. (Although this appears to be adequate). Overall, it appears that the name cache size is controlled solely by the vnode list - when a vnode list entry is reused, any associated name cache entries are invalidated. Is this correct? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 16:10:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10204 for freebsd-current-outgoing; Tue, 1 Dec 1998 16:10:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10191 for ; Tue, 1 Dec 1998 16:10:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01088; Tue, 1 Dec 1998 15:46:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812012346.PAA01088@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: van.woerkom@netcologne.de cc: mike@smith.net.au, jkh@zippy.cdrom.com, forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Tue, 01 Dec 1998 19:23:30 +0100." <199812011823.TAA08092@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 15:46:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We should talk them [OSS] through the conversion to a KLD module > > as soon as we're sure what they need to look like. 8) > > Are KLD modules intended for run-time loadable drivers? Yes. > What are the (rough) plans for this mechanism? Convert the entire kernel into an aggregation of KLD modules. Stick them together in interesting and versatile ways (eg. at build time to create a monolithic kernel, or at runtime to load/unload drivers, etc.). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 18:53:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24856 for freebsd-current-outgoing; Tue, 1 Dec 1998 18:53:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24851 for ; Tue, 1 Dec 1998 18:53:10 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id VAA01817 for ; Tue, 1 Dec 1998 21:52:47 -0500 (EST) Message-Id: <4.1.19981201215111.0092f100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 01 Dec 1998 21:53:05 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Netscape Communicator 4.5 still dumps core Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a build world this afternoon, I un-installed and remade the XFree86-3.3.3 system (yes, with a.out support), remade windowmaker, remake tcl/tk8.0 (which shouldn't make a diff here). I give up. This thing still keeps dumping core with "exited on signal 11 (core dumped)". It's getting very old. Who provided this compiled port? I think it's probably time to update the build anyways. ??? Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 18:59:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25408 for freebsd-current-outgoing; Tue, 1 Dec 1998 18:59:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25402 for ; Tue, 1 Dec 1998 18:59:18 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id NAA12058; Wed, 2 Dec 1998 13:59:05 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma012044; Wed, 2 Dec 98 13:58:57 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id NAA02462; Wed, 2 Dec 1998 13:58:43 +1100 From: "John Saunders" To: "Garrett Wollman" , "Matthew Dillon" Cc: Subject: RE: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) Date: Wed, 2 Dec 1998 13:58:43 +1100 Message-ID: <002401be1d9f$ac2c1bd0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <199812011619.LAA04055@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > Matthew Dillon wrote: > > It's a real problem. When you are receiving a 20Kpps > > attack you do not want to be transmitting 20Kpps in ICMP > > replies to a possibly spoofed address. > > Then again, when you are receiving 20kpps of legitimate traffic, you > still want to behave correctly. I think Matt's (cleaned up) patch should go ahead as the idea is sound. It's never normal to have 20Kpps ICMP traffic (famous last words :-) in even the largest networks today. The talk about stability is really an interesting aside from the patch itself and outside of Matt's scope. Additions to the patch I would like to see are a nice sysctl variable to set the rate limit, with setting it to 0 effectively disabling the limit (although I'll be enabling it personally). Particular care should be taken to see that if rate limiting is disabled then the extra execution overhead is minimal. However if what we are saying is that under 20Kpps ICMP traffic FreeBSD wedges, what happens under 20Kpps of perfectly valid UDP or TCP traffic? We probably won't see high packet rate TCP traffic because you need 240Mbps bandwidth to generate 20Kpps with a 1500 byte MTU. However high UDP packet rates are possible and will get worse as services like VoIP become more mainstream. If the problem is mbuf starvation shouldn't the network layer simply pause until resources become available? Anything not network related should continue as normal. If the problem is CPU starvation from excessive network interrupts, the network driver layer should throttle itself back somehow. This is a difficult task to do elegantly and most commercial drivers I have worked on or seen take a pragmatic approach. The ARP rate limit seems interesting. Possibly an exponential backoff algorithm for ARP requests, with queued packet dumping could be implemented. The way I see it if no ARP response is available after a few seconds we can become _really_ aggressive about dumping queued packets. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 19:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26820 for freebsd-current-outgoing; Tue, 1 Dec 1998 19:11:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26815 for ; Tue, 1 Dec 1998 19:10:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA02126; Tue, 1 Dec 1998 19:08:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812020308.TAA02126@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: "Garrett Wollman" , "Matthew Dillon" , freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-reply-to: Your message of "Wed, 02 Dec 1998 13:58:43 +1100." <002401be1d9f$ac2c1bd0$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 19:08:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the problem is mbuf starvation shouldn't the network layer > simply pause until resources become available? Anything not > network related should continue as normal. This is probably the single most insidious problem that our stack currently faces; portions of the code assume that mbuf allocation will always succeed. These code portions require redesign, often nontrivial, to allow them to abort in one fashion or another when allocation fails. We've presented this situation to plaintiffs a number of times; we haven't received any code back yet. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02356 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:12:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02345 for ; Tue, 1 Dec 1998 20:12:32 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id XAA06009; Tue, 1 Dec 1998 23:11:44 -0500 (EST) Message-ID: <19981201231144.A3607@ns1.adsu.bellsouth.com> Date: Tue, 1 Dec 1998 23:11:44 -0500 From: Christian Kuhtz To: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 still dumps core References: <4.1.19981201215111.0092f100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19981201215111.0092f100@206.25.93.69>; from Forrest Aldrich on Tue, Dec 01, 1998 at 09:53:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: I've had zero problems with XF86 3.3.3 on 3.0-RELEASE/CURRENT w/ KDE as the window manager. Netscape Communicator 4.5 has been *rock solid*, and I know how difficult that might be to believe.. Communicrator 4.5 port in my case was courtesy of Netscrape. Cheers, Chris On Tue, Dec 01, 1998 at 09:53:05PM -0500, Forrest Aldrich wrote: > I did a build world this afternoon, I un-installed and remade the > XFree86-3.3.3 system (yes, with > a.out support), remade windowmaker, remake tcl/tk8.0 (which shouldn't make > a diff here). > > I give up. This thing still keeps dumping core with "exited on signal 11 > (core dumped)". It's > getting very old. > > Who provided this compiled port? I think it's probably time to update the > build anyways. > > > ??? > > > Forrest > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02758 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:15:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02745 for ; Tue, 1 Dec 1998 20:15:10 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id WAA02784 for ; Tue, 1 Dec 1998 22:14:50 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma002762; Tue, 1 Dec 98 22:14:38 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id WAA17946 for ; Tue, 1 Dec 1998 22:14:38 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Tue, 1 Dec 1998 22:14:37 -0600 (CST) From: Kyle Mestery To: freebsd-current@FreeBSD.ORG Subject: Problems in current with a CD-ROM drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am running current as of 11-30 at about 4PM or so. I have a Sony 4x SCSI CD-ROM running on a dual Pentium machine that suddenly has stopped working. What I mean is, it no longer can correctly play audio CDs. Here is the relevant dmesg output: bt0: rev 0x00 int a irq 17 on pci0.19.0 bt0: BT-946C FW Rev. 4.25J Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs cd0 at bt0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 5.0MB/s transfers (5.0MHz, offset 15) cd0: cd present [214790 x 2048 byte records] There is also one 1GB HP disk on that controller. What happens is, if I load an audio CD into the drive, and use cdcontrol to play it, the CD plays fine initially, but when I type stop in cdcontrol to stop it, the process gets hung. I cannot kill it or anything. It gets stuck in cbwait, as is shown below from top: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 417 mestery -6 0 944K 432K cbwait 0 0:00 0.00% 0.00% cdcontrol If I type eject from cdcontrol, it will eject, but never close again until reset. THe drive's light continues to flicker from busy to not busy, and once again cdcontrol is stuck in cbwait. Is this a known problem with the above setup? Is anyone else seeing this? I tried using workman to play audio CDs, but it hangs upon pressing play. Not sure if it also hangs in cbwait. Any pointers would be appreciated! Thanks! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03558 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:23:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrynet.com (mrynet.com [206.154.101.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03551 for ; Tue, 1 Dec 1998 20:23:34 -0800 (PST) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.9.1/8.7.3) id UAA84982; Tue, 1 Dec 1998 20:23:14 -0800 (PST) Message-Id: <199812020423.UAA84982@mrynet.com> From: staylor@mrynet.com (Scott Gregory Akmentins-Taylor) Date: Tue, 1 Dec 1998 20:23:14 +0000 In-Reply-To: Mail dated Dec 1, 6:53pm. X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Forrest Aldrich Subject: Re: Netscape Communicator 4.5 still dumps core Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [In "Netscape Communicator 4.5 still dumps core", on Dec 1, 6:53pm, Forrest Aldrich whinged something about:] > I did a build world this afternoon, I un-installed and remade the > XFree86-3.3.3 system (yes, with > a.out support), remade windowmaker, remake tcl/tk8.0 (which shouldn't make > a diff here). > > I give up. This thing still keeps dumping core with "exited on signal 11 > (core dumped)". It's > getting very old. > > Who provided this compiled port? I think it's probably time to update the > build anyways. Forrest, Netscape 4.5 has proven to be just fine here on 3.0 CURRENT pre-ELF, 3.0 ELF, both with 3.3.2 and 3.3.3 XFree86. Might I refer you to the FAQ, section 6.13? Signal 11 failures in programs are more frequently than not a result of a hardware problem. Netscape is a MoFo of a memory pig, and when you're running it, it's likely hitting a bad memory location. Neither the port, XFree86, nor 3.0-CURRENT are suspect here, IMO. Check out the FAQ section on Signal 11 failures is my recommendation :) -skots -- Scott G. Akmentins-Taylor Email: staylor@mrynet.com, staylor@idt.net Westlake Village, CA USA URL: http://www.mrynet.com/ButchBub (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans -- Raz'ots Latvija' ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:47:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05900 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:47:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05893 for ; Tue, 1 Dec 1998 20:47:25 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id XAA18135 for ; Tue, 1 Dec 1998 23:47:11 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22222; Tue, 1 Dec 1998 23:47:11 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA06509 for freebsd-current@freebsd.org; Tue, 1 Dec 1998 23:47:11 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812020447.XAA06509@bb01f39.unx.sas.com> Subject: release build broken To: freebsd-current@FreeBSD.ORG Date: Tue, 1 Dec 1998 23:47:11 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following says it all... :-( My sources are current as of 10:30pm EST. -John ===> Creating README.html for sudo-1.5.6.5 ===> security/super "Makefile", line 18: Malformed conditional (${OSVERSION} < 300000) "Makefile", line 18: Need an operator "Makefile", line 20: if-less endif "Makefile", line 20: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:50:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06323 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:50:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06299 for ; Tue, 1 Dec 1998 20:50:26 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id PAA26467 for ; Wed, 2 Dec 1998 15:50:12 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd026464; Wed Dec 2 04:50:05 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id PAA29489 for ; Wed, 2 Dec 1998 15:50:10 +1100 (EST) Message-Id: <199812020450.PAA29489@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: keyboard freezes 3.0-RELEASE (softupdates related?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 15:50:02 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day. Installed 3.0-RELEASE from the CDs onto an HP Kayak XA. (400Mhz P-II, BX mboard, ATA HDD & CD, Matrox G200 AGP, PS/2 mouse and PS2-like connector on the keyboard). Built a new kernel with softupdates & proper network cards etc etc. It worked fine for a couple hours with this kernel. Booted the CD#2 to turn softupdates on for all FS, then rebooted with the softupdates kernel. Since that time, the keyboard freezes. Alt-Fn works to change VTs, PrntScrn also changes VTs, but none of the "real" keys work. Sometimes, it is dead from boot time, sometimes it works long enough to log in and run a couple of commands before it breaks. This is NOT using X; I haven't got XF86 3.3.3 set up yet and 3.3.2 doesn't support the G200 accelleration. Boot back with kernel.GENERIC and keyboard is fine. Turn off softupdates via tunefs but using the new kernel seems to work OK. Any clues how I can help track this down? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 20:56:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06608 for freebsd-current-outgoing; Tue, 1 Dec 1998 20:56:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp2.mindspring.com (smtp2.mindspring.com [207.69.200.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06603 for ; Tue, 1 Dec 1998 20:56:16 -0800 (PST) (envelope-from rsi@mindspring.com) Received: from kamikaze.mindspring.com (user-38ld185.dialup.mindspring.com [209.86.133.5]) by smtp2.mindspring.com (8.8.5/8.8.5) with ESMTP id XAA01623 for ; Tue, 1 Dec 1998 23:55:36 -0500 (EST) Received: (from rsi@localhost) by kamikaze.mindspring.com (8.9.1/8.8.7) id XAA11820; Tue, 1 Dec 1998 23:55:16 -0500 (EST) (envelope-from rsi) Message-Id: <199812020455.XAA11820@kamikaze.mindspring.com> To: freebsd-current@FreeBSD.ORG Subject: usr.bin/truss fails to build From: Rajappa Iyer Date: 01 Dec 1998 23:55:04 -0500 Reply-To: rajappa@mindspring.com Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup'ed as of 12/1/98 make world fails at usr.bin/truss ===> usr.bin/truss cc -nostdinc -O -pipe -I/u/src/usr.bin/truss -I. -I/usr/obj/elf/u/src/tmp/usr/ include -c /u/src/usr.bin/truss/i386-fbsd.c In file included from /u/src/usr.bin/truss/i386-fbsd.c:65: syscalls.h:240: parse error before `/' /u/src/usr.bin/truss/i386-fbsd.c: In function `clear_fsc': /u/src/usr.bin/truss/i386-fbsd.c:90: `fsc' undeclared (first use this function) /u/src/usr.bin/truss/i386-fbsd.c:90: (Each undeclared identifier is reported onl y once /u/src/usr.bin/truss/i386-fbsd.c:90: for each function it appears in.) /u/src/usr.bin/truss/i386-fbsd.c: In function `i386_syscall_entry': /u/src/usr.bin/truss/i386-fbsd.c:153: `fsc' undeclared (first use this function) /u/src/usr.bin/truss/i386-fbsd.c:155: `nsyscalls' undeclared (first use this fun ction) /u/src/usr.bin/truss/i386-fbsd.c: In function `i386_syscall_exit': /u/src/usr.bin/truss/i386-fbsd.c:268: `fsc' undeclared (first use this function) *** Error code 1 -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 21:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07718 for freebsd-current-outgoing; Tue, 1 Dec 1998 21:05:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07710 for ; Tue, 1 Dec 1998 21:05:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA02814; Tue, 1 Dec 1998 21:02:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812020502.VAA02814@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: geoffb@demon.net, mike@smith.net.au, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu, ortmann@sparc.isl.net Subject: Re: sio breakage In-reply-to: Your message of "Tue, 01 Dec 1998 14:30:14 +1100." <199812010330.OAA20453@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 21:02:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I was assuming the serial interface which is a fixed one breaking out of > >> the back of the Laptop had nothing to do with the PCMCIA, > > > >You're quite correct; it doesn't. There's *something* holding up both > >your interrupt handlers and the tty soft interrupt; maybe even possibly the > >same thing that causes the "calcru: negative time for ..." messages. > > something() > { > asm("cli"); > asm("sti"); > } > > This disables interrupts for 0 user instructions, but if a pagefault > occurs for reading the "sti" instruction, it disables interrupts for > hundreds, thousands or millions of kernel instructions. Since 'cli' can't be executed in user space, and a page fault in kernel mode is a fatal occurrence, this can't happen. > something_more_likely() > { > asm("cli"); > var = 0; > asm("sti"); > } > > This disables interrupts for 1 or 2 user instructions, but if a pagefault > occurs for reading a critical instruction or more likely for accessing > the variable, it disables interrupts for hundreds, thousands or millions > of kernel instructions. Again, since 'cli' can't be executed in kernel space, this is only an issue within the kernel. I'm not aware of any code which calls the fu*/su*/copy* family with interrupts disabled - perhaps a trivial wrapper could be installed to check for this? > Fixes: > kernel: send a fatal signal to applications that do this. We have one already; it's called SIGBUS. > applications: don't do this. If interrupts must be disabled, then all > critical code and data must be within one page. They can't (short of getting PSL_IOPL and then manipulating the PIC themselves), so this isn't an issue. Failure to deliver interrupts in the kernel seems to be a persistent problem; it's almost certainly the problem with these sio errors, and Poul seems to think it's responsible for breaking his code as well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 22:18:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14475 for freebsd-current-outgoing; Tue, 1 Dec 1998 22:18:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ethel.basspro.com (ethel.basspro.com [12.14.224.132]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA14469 for ; Tue, 1 Dec 1998 22:18:51 -0800 (PST) (envelope-from troyk@basspro.com) Received: from gateway.basspro.com by ethel.basspro.com; (5.65v3.2/1.1.8.2/29Jan96-0343PM) id AA10139; Wed, 2 Dec 1998 00:20:39 -0600 Message-Id: <3664DB15.398E057B@basspro.com> Date: Wed, 02 Dec 1998 00:15:49 -0600 From: Troy Kittrell X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Christian Kuhtz Cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 still dumps core References: <4.1.19981201215111.0092f100@206.25.93.69> <19981201231144.A3607@ns1.adsu.bellsouth.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Kuhtz wrote: > > FYI: I've had zero problems with XF86 3.3.3 on 3.0-RELEASE/CURRENT w/ KDE > as the window manager. Netscape Communicator 4.5 has been *rock solid*, and I > know how difficult that might be to believe.. Communicrator 4.5 port in my case > was courtesy of Netscrape. > > Cheers, > Chris > > On Tue, Dec 01, 1998 at 09:53:05PM -0500, Forrest Aldrich wrote: > > I did a build world this afternoon, I un-installed and remade the > > XFree86-3.3.3 system (yes, with > > a.out support), remade windowmaker, remake tcl/tk8.0 (which shouldn't make > > a diff here). > > > > I give up. This thing still keeps dumping core with "exited on signal 11 > > (core dumped)". It's > > getting very old. > > > > Who provided this compiled port? I think it's probably time to update the > > build anyways. > > > > > > ??? > > > > > > Forrest > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Not the case here. I ran Netscape 4.05 w/2.2.7 for several months with nary a hitch and, since loading -current some 5 days ago, with Netscape 4.5, I can usually expect to close all Netscape windows (with fvwm95 as the window manager) with a regular frequency. I *have* noticed that it is more dependent on the number of times I accesss e-mail (I-MAP4) but I've not pegged a particular action that hoses it. All I can do is close all windows and start over. BTW: I believe this is 4.5b2. Does the beta have anything to do with it? I'll say "duh" for everyone and save the bandwidth.... -- Troy Kittrell troyk@basspro.com Internet Systems Coordinator Bass Pro Outdoors Online To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 22:35:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15907 for freebsd-current-outgoing; Tue, 1 Dec 1998 22:35:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15900 for ; Tue, 1 Dec 1998 22:35:27 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA13376; Wed, 2 Dec 1998 17:35:01 +1100 Date: Wed, 2 Dec 1998 17:35:01 +1100 From: Bruce Evans Message-Id: <199812020635.RAA13376@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: sio breakage Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, ortmann@sparc.isl.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> something() >> { >> asm("cli"); >> asm("sti"); >> } >> >> This disables interrupts for 0 user instructions, but if a pagefault >> occurs for reading the "sti" instruction, it disables interrupts for >> hundreds, thousands or millions of kernel instructions. > >Since 'cli' can't be executed in user space, and a page fault in kernel >mode is a fatal occurrence, this can't happen. man 4 io. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 1 23:48:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22055 for freebsd-current-outgoing; Tue, 1 Dec 1998 23:48:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22050 for ; Tue, 1 Dec 1998 23:48:53 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40352>; Wed, 2 Dec 1998 18:47:51 +1100 Date: Wed, 2 Dec 1998 18:48:28 +1100 From: Peter Jeremy Subject: Re: sio breakage To: current@FreeBSD.ORG Message-Id: <98Dec2.184751est.40352@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: >something_more_likely() >{ > asm("cli"); > var = 0; > asm("sti"); >} >Fixes: >kernel: send a fatal signal to applications that do this. I'd suggest sending SIGBUS, with the interrupts enabled. This would allow the application to recover if necessary. >applications: don't do this. I don't believe this is reasonable. We should provide some safe way for an application program to execute code with interrupts disabled. Amongst other applications, XFree86 needs this. > If interrupts must be disabled, then all > critical code and data must be within one page. The restriction is slightly more liberal than this: all code in the flow of control between the CLI and STI (inclusive), together with all data referenced by such code must be resident at the time the CLI is executed. For short sequences where no memory is accessed (eg a block of I/O instructions), including a `.align 4,0x90' before the CLI will be sufficient (as long as the total code is less than 16 bytes). Where sufficient memory is available to ensure that recently referenced pages will not get reused, including a series of tests (or similar) - for each data location and the terminating STI - before the CLI should be sufficient. This approach does have the downside that if the system is thrashing, the pages may get reused anyway. The guaranteed approach is to use mlock(2) on the affected regions. This is also the most expensive (since multiple system calls are required). Whilst this only works for root, only root can normally open /dev/io (and hence use CLI/STI). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 00:19:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24144 for freebsd-current-outgoing; Wed, 2 Dec 1998 00:19:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24136 for ; Wed, 2 Dec 1998 00:19:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA23061; Wed, 2 Dec 1998 09:16:18 +0100 (CET) To: Peter Jeremy cc: freebsd-current@FreeBSD.ORG Subject: Re: Name cache questions. In-reply-to: Your message of "Wed, 02 Dec 1998 11:08:43 +1100." <98Dec2.110806est.40355@border.alcanet.com.au> Date: Wed, 02 Dec 1998 09:16:11 +0100 Message-ID: <23059.912586571@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <98Dec2.110806est.40355@border.alcanet.com.au>, Peter Jeremy writes: >I've been studying the name cache code (in 3.0-RELEASE), trying to see >if I can improve the hit rate. Looking at the code (in kern/vfs_cache.c) >it's not clear to me how the cache is managed. In several cases, the >comments appear at variance to the code. Yes, the comments may be in variance, I havn't checked that very carefully. The namecache is not a separate entity like it used to be, it is mode like an attachment to the vnodes. The namecache entry goes when the vnodes goes (or in certain other specifically requested cases like rename and whatsnot). Negative entries have no vnode, so they must be limited by some other means. The current ncnegfactor seems to work ok, but no careful benchmarks have been done. >3) cache_lookup() includes the comment `We don't do this if the > segment name is long'. Neither cache_lookup(), nor any of its > callers appear to include code to check the segment name length > (other than to NAME_MAX). Well, we used to not cache long names. >4) cache_purge() includes the comment `If the v_id wraps around, we > need to ditch the entire cache'. The code doesn't check for > wrap-around, it simply avoids v_id == 0 and re-using the existing > v_id. (Although this appears to be adequate). Well, technically we do, but I have decided that the probability of a problem is too epsilon to be done anything about. You have to create 2^32 vnodes in mem, and then one particular vnode which has survived this entire cycle should get recycled and assigned the same v_id before you would have problems. The right way of solving this would probably be to make the v_id private per vnode, since it can only ever be used together with a pointer to the vnode. >Overall, it appears that the name cache size is controlled solely by >the vnode list - when a vnode list entry is reused, any associated >name cache entries are invalidated. Is this correct? yes. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 00:43:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25539 for freebsd-current-outgoing; Wed, 2 Dec 1998 00:43:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp9.portal.net.au [202.12.71.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25532 for ; Wed, 2 Dec 1998 00:43:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA05456; Wed, 2 Dec 1998 00:41:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812020841.AAA05456@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: mike@smith.net.au, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, ortmann@sparc.isl.net Subject: Re: sio breakage In-reply-to: Your message of "Wed, 02 Dec 1998 17:35:01 +1100." <199812020635.RAA13376@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 00:41:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> something() > >> { > >> asm("cli"); > >> asm("sti"); > >> } > >> > >> This disables interrupts for 0 user instructions, but if a pagefault > >> occurs for reading the "sti" instruction, it disables interrupts for > >> hundreds, thousands or millions of kernel instructions. > > > >Since 'cli' can't be executed in user space, and a page fault in kernel > >mode is a fatal occurrence, this can't happen. > > man 4 io. Having run the test program I used to check this as root, I see that it is indeed possible (although it should not be). However: dingo:/tmp>man 4 io Formatting page, please wait...Done. IO(4) FreeBSD Kernel Interfaces Manual (i386 Architecture) IO(4) NAME io - I/O privilege file DESCRIPTION The special file /dev/io is a controlled security hole that allows a pro- cess to gain I/O privileges (which are normally reserved for kernel- internal code). Any process that holds a file descriptor on /dev/io open will get its IOPL bits in the flag register set, thus allowing it to per- form direct I/O operations. This can be useful in order to write user- land programs that handle some hardware directly. The entire access control is handled by the file access permissions of /dev/io, so care should be taken in granting rights for this device. Note that even read/only access will grant the full I/O privileges. FILES /dev/io SEE ALSO mem(4) HISTORY The io file appeared in FreeBSD 1.0. BSD Jan 1, 1996 1 There is no reference to manipulating interrupt state here. I'm still somewhat at a loss as to how it's meant to be possible for the page fault you posit to be handled in the case where PSL_I is cleared in all cases (eg. disk drivers with no interrupt timeout handlers). If it is, it would require interrupts to be enabled for most of the duration, which kinda defeats the entire issue... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 00:46:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25765 for freebsd-current-outgoing; Wed, 2 Dec 1998 00:46:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp9.portal.net.au [202.12.71.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25757 for ; Wed, 2 Dec 1998 00:46:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA05482; Wed, 2 Dec 1998 00:44:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812020844.AAA05482@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: current@FreeBSD.ORG Subject: Re: sio breakage In-reply-to: Your message of "Wed, 02 Dec 1998 18:48:28 +1100." <98Dec2.184751est.40352@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 00:44:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bruce Evans wrote: > > >something_more_likely() > >{ > > asm("cli"); > > var = 0; > > asm("sti"); > >} > > >Fixes: > >kernel: send a fatal signal to applications that do this. > > I'd suggest sending SIGBUS, with the interrupts enabled. This would > allow the application to recover if necessary. That's the normal practice; I suspect that the problem is that the i386 doesn't trap attempts to clear PSL_I if PSL_IOPL is set, so you can't guarantee that this will be detected cleanly. (I may be wrong on this; I'd have to check the code more carefully.) > >applications: don't do this. > > I don't believe this is reasonable. We should provide some safe way > for an application program to execute code with interrupts disabled. > Amongst other applications, XFree86 needs this. It shouldn't (ideally). If it does, this is clearly indicative of a need to move some of the server code into the kernel, or in some other architecturally clean fashion provide the currently missing assurances pertaining to running with interrupts disabled. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 00:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25882 for freebsd-current-outgoing; Wed, 2 Dec 1998 00:49:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25877 for ; Wed, 2 Dec 1998 00:48:58 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA22779; Wed, 2 Dec 1998 09:48:21 +0100 (MET) Date: Wed, 2 Dec 1998 09:47:59 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Mike Smith cc: van.woerkom@netcologne.de, jkh@zippy.cdrom.com, forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812012346.PAA01088@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What are the (rough) plans for this mechanism? > > Convert the entire kernel into an aggregation of KLD modules. Stick > them together in interesting and versatile ways (eg. at build time to > create a monolithic kernel, or at runtime to load/unload drivers, etc.). ... unload probe/init code when it is no longer needed. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 01:27:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28712 for freebsd-current-outgoing; Wed, 2 Dec 1998 01:27:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28707 for ; Wed, 2 Dec 1998 01:27:13 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Wed, 2 Dec 1998 20:26:17 +1100 Date: Wed, 2 Dec 1998 20:26:51 +1100 From: Peter Jeremy Subject: Re: sio breakage To: mike@smith.net.au Cc: current@FreeBSD.ORG Message-Id: <98Dec2.202617est.40351@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: >> man 4 io. > >Having run the test program I used to check this as root, I see that it >is indeed possible (although it should not be). As stated in io(4), FreeBSD allows a process to execute I/O instructions by changing IOPL to allow a ring-3 (user) task to perform I/O. For reasons known best to Intel(*), CLI, STI and changing the IF using POPF are controlled by IOPL, rather than being ring-0 instructions (like the other privileged instructions). An alternative approach would be to leave IOPL at 0 and use the I/O Permission bitmap in the TSS. This allows I/O without allowing CLI/STI. The disadvantage is that either you have a per-process TSS (which is expensive in memory), or the TSS needs to be re-written on a context switch (which is expensive in time). BSDI (at least BSDI 1.1) used this approach - but the bitmap was system-wide, so enabling an I/O port for any process enabled it for all processes (which isn't particularly secure). [And at least on 486's, I/O instructions are much slower is the IOPB is used instead of IOPL - even slower than accessing the ISA bus :-(]. (*) The need to atomically issue multiple I/O instructions could be seen to be a justification for this. >There is no reference to manipulating interrupt state here. I agree that io(4) should mention this. >I'm still somewhat at a loss as to how it's meant to be possible for the >page fault you posit to be handled in the case where PSL_I is cleared in >all cases (eg. disk drivers with no interrupt timeout handlers). There are occasional CLI/STI pairs in the kernel. Presumably an STI gets executed somewhere along the line... Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 01:47:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00484 for freebsd-current-outgoing; Wed, 2 Dec 1998 01:47:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00479 for ; Wed, 2 Dec 1998 01:47:07 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Wed, 2 Dec 1998 20:46:08 +1100 Date: Wed, 2 Dec 1998 20:46:45 +1100 From: Peter Jeremy Subject: Re: sio breakage To: mike@smith.net.au Cc: current@FreeBSD.ORG Message-Id: <98Dec2.204608est.40351@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > I suspect that the problem is that the i386 >doesn't trap attempts to clear PSL_I if PSL_IOPL is set, so you can't >guarantee that this will be detected cleanly. If you aren't running at IOPL, CLI and STI will trap, but POPF _ignores_ any attempt to change PSL_I. This particular brokenness in POPF (and the inability to make PUSHF trap) is all that prevents us easily providing a virtual-386 environment (which means you could just run buggy, half-baked file-loaders, rather than trying to emulate all their undocumented interfaces). [Actually, I gather that Pentium and later chips _do_ have the microcode to allow virtual-386, but the relevant incantations to use this is only available under NDA]. >> I don't believe this is reasonable. We should provide some safe way >> for an application program to execute code with interrupts disabled. >> Amongst other applications, XFree86 needs this. > >It shouldn't (ideally). I agree. And whilst I haven't checked why, XFree86 does appear to disable interrupts at times. > If it does, this is clearly indicative of a >need to move some of the server code into the kernel, You mean, like GGI :-). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 02:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02609 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:11:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02603 for ; Wed, 2 Dec 1998 02:11:47 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA30107; Wed, 2 Dec 1998 21:11:25 +1100 Date: Wed, 2 Dec 1998 21:11:25 +1100 From: Bruce Evans Message-Id: <199812021011.VAA30107@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: sio breakage Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, ortmann@sparc.isl.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >However: > >dingo:/tmp>man 4 io ... > internal code). Any process that holds a file descriptor on /dev/io open > will get its IOPL bits in the flag register set, thus allowing it to per- > form direct I/O operations. This can be useful in order to write user- >There is no reference to manipulating interrupt state here. Well, this is not the place to document all features of IOPL. IOPL is documented in Intel manuals. From the 486 manual: "The CLI instruction clears the IF flag if the current privilege level is at least as privileged as IOPL. [Otherwise it generates a general protection exception]". >I'm still somewhat at a loss as to how it's meant to be possible for the >page fault you posit to be handled in the case where PSL_I is cleared in >all cases (eg. disk drivers with no interrupt timeout handlers). It's not meant to be possible, but it sometimes sort of works. idle() and cpu_switch() and perhaps other places enable interrupts unconditionally. This defeats the point of the "cli" but allows i/o to be done for the page fault. Anyway, most page faults can be handled without doing i/o. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 02:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03615 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:25:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03605; Wed, 2 Dec 1998 02:25:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id CAA13404; Wed, 2 Dec 1998 02:25:09 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 02:25:09 -0800 (PST) From: Matthew Dillon Message-Id: <199812021025.CAA13404@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: simple cvs mod to handle shared checked-out source trees Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to submit the following new option to CVS for review. The new option, -g, forces a umask of 00x which is necessary when multiple users share a common checked-out source tree. If there are no significant objects, I will commit it. Note that this is different from multiple users operating out of the same CVSROOT. There are several common cases where you might want to have multiple users sharing a common checked-out source tree. For example, in our management of DNS records we allow certain staff members to make modifications to primary zone files. We do not want to have to duplicate the 30,000+ zone files for each user yet we DO want to keep those files under CVS control. The same problem occurs in our management of many other portions of our infrastructure. In anycase, to use the -g option effective, the user simply creates a ~/.cvsrc config file containing the line shown below, then runs CVS commands as per normal. --- cut here --- cvs -g --- cut here --- The only other way to do it is for the user to set his umask to, for example, 007. The problem with doing this is that the user's entire shell session then operates with that umask, which can be exceedingly dangerous. But CVS operations can be made group-writeable-safe trivially simply by being in a private group due by chgrp'ing the directory structure. Thus, having the cvs program set the umask (when given the -g option) can be made safe. (not included below are manual and error message diffs that also describe the new option). -Matt tick:/usr/src/contrib/cvs# diff -c src/LINK/main.c src/main.c *** src/LINK/main.c Tue Apr 7 16:19:50 1998 --- src/main.c Wed Dec 2 01:59:31 1998 *************** *** 479,485 **** opterr = 1; while ((c = getopt_long ! (argc, argv, "+QqrwtnRlvb:T:e:d:Hfz:s:xa", long_options, &option_i ndex)) != EOF) { switch (c) --- 479,485 ---- opterr = 1; while ((c = getopt_long ! (argc, argv, "+QqgrwtnRlvb:T:e:d:Hfz:s:xa", long_options, &option_ index)) != EOF) { switch (c) *************** *** 511,516 **** --- 511,522 ---- break; case 'w': cvswrite = 1; + break; + case 'g': + /* + * full group write perms + */ + umask(umask(077) & 007); break; case 't': Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 02:25:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03665 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:25:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03655; Wed, 2 Dec 1998 02:25:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA06729; Wed, 2 Dec 1998 02:27:18 -0800 (PST) To: current@FreeBSD.ORG cc: dillon@FreeBSD.ORG Subject: Uh oh... Date: Wed, 02 Dec 1998 02:27:18 -0800 Message-ID: <6721.912594438@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... EPEND=t OBJFORMAT_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec:/usr/libexec /usr/o bj/elf/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/elf/usr/src/tmp -f Makefile.inc 1 hierarchy cd /usr/src/etc; /usr/obj/elf/usr/src/tmp/usr/bin/make distrib-di rs mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /usr/obj/elf/usr/src/tmp/ mtree: line 34: unknown user bind *** Error code 1 I think we've created a slight bootstrapping problem here. "make world" is still the official method of upgrading a system via sources and it's supposed to handle all bootstrapping issues like this automagically. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 02:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04040 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:31:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04034 for ; Wed, 2 Dec 1998 02:31:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id CAA13477; Wed, 2 Dec 1998 02:31:13 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 02:31:13 -0800 (PST) From: Matthew Dillon Message-Id: <199812021031.CAA13477@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Uh oh... References: <6721.912594438@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :rs :mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /usr/obj/elf/usr/src/tmp/ :mtree: line 34: unknown user bind :*** Error code 1 : :I think we've created a slight bootstrapping problem here. "make :world" is still the official method of upgrading a system via sources :and it's supposed to handle all bootstrapping issues like this :automagically. : :- Jordan Uh oh. Hmmm. Can we specify a uid in the BSD.root.dist rather then a user name ? -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 02:39:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04526 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:39:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04521 for ; Wed, 2 Dec 1998 02:39:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA06866; Wed, 2 Dec 1998 02:41:29 -0800 (PST) To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 02:31:13 PST." <199812021031.CAA13477@apollo.backplane.com> Date: Wed, 02 Dec 1998 02:41:28 -0800 Message-ID: <6862.912595288@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Uh oh. Hmmm. Can we specify a uid in the BSD.root.dist rather then > a user name ? It wouldn't really solve the problem since then you'd just have the 2nd-order bug reports of "why are all my files owned by this funny number?" coming in - there's really just no substitute for getting the new entries into the password file. Fortunately, the pw(8) command makes this pretty easy to do. You can check to see if the user/uid is already there by doing something like: if pw usershow bind > /dev/null 2>&1; then pw useradd bind ..other args.. fi In /usr/src/Makefile.inc1's buildworld rule (I'd stick it before the hierarchy stuff, for obvious reasons). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 03:51:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10070 for freebsd-current-outgoing; Wed, 2 Dec 1998 03:51:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10065 for ; Wed, 2 Dec 1998 03:51:17 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id WAA08572; Wed, 2 Dec 1998 22:58:38 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812021158.WAA08572@cimlogic.com.au> Subject: Re: Uh oh... In-Reply-To: <6862.912595288@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 98 02:41:28 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Dec 1998 22:58:38 +1100 (EST) Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > Uh oh. Hmmm. Can we specify a uid in the BSD.root.dist rather then > > a user name ? > > It wouldn't really solve the problem since then you'd just have the > 2nd-order bug reports of "why are all my files owned by this funny > number?" coming in - there's really just no substitute for getting the > new entries into the password file. ... and group. We should test for each user and group defined in the src/etc files and add them if they don't exist in the installed system. This would make bootstrapping FreeBSD sources on a NetBSD system easier too. [Uh oh, I guess they're going to yell at me again. They seem to react badly when I say these things. 8-)] -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 04:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13072 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:07:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13067 for ; Wed, 2 Dec 1998 04:07:22 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA05665; Wed, 2 Dec 1998 23:07:00 +1100 Date: Wed, 2 Dec 1998 23:07:00 +1100 From: Bruce Evans Message-Id: <199812021207.XAA05665@godzilla.zeta.org.au> To: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Subject: Re: sio breakage Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>something_more_likely() >>{ >> asm("cli"); >> var = 0; >> asm("sti"); >>} > >>Fixes: >>kernel: send a fatal signal to applications that do this. > >I'd suggest sending SIGBUS, with the interrupts enabled. This would >allow the application to recover if necessary. Recovery may be impossible, since timing for the critical region may have been violated by a few usec for taking the trap, and when interrupts are enabled, interrupt processing may violate the timing by another N msec, not to mention that a clock interrupt may trigger rescheduling of the process so that it is not run for another M scheduling quanta. My current fix just enables interrupts and prints an error message at the start of trap(). I've noticed traps with interrupts disabled for: asm("cli"); asm("sti"); /* trace trap here for single stepping */ and char *p = malloc(0x1000); asm("cli"); p[0] = 0; /* pagefault here for normal operation */ asm("sti"); >>applications: don't do this. > >I don't believe this is reasonable. We should provide some safe way >for an application program to execute code with interrupts disabled. I gave a way: only access a single page (including for code). The page must be mapped in for execution of the "cli" in it to work. Oops, this is not enough. The "cli" might work because it is cached (pipelines probably aren't a problem because they will probably never cross page boundaries). >> If interrupts must be disabled, then all >> critical code and data must be within one page. > >The restriction is slightly more liberal than this: all code in the >flow of control between the CLI and STI (inclusive), together with all >data referenced by such code must be resident at the time the CLI is >executed. But the application has no way of knowning if the memory is resident. I forgot about caches when I suggested putting everything on one pages as a way of knowing that at least that page is resident. >The guaranteed approach is to use mlock(2) on the affected regions. >This is also the most expensive (since multiple system calls are >required). Whilst this only works for root, only root can normally >open /dev/io (and hence use CLI/STI). It is cheap enough in time if the memory is kept locked, and cheapest in space if everything is on one page :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 04:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13843 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:13:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-115.isl.net [199.3.25.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13836 for ; Wed, 2 Dec 1998 04:13:17 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id GAA01094; Wed, 2 Dec 1998 06:12:12 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199812021212.GAA01094@pyrl.eye> Subject: a problem tracked down (was "Re: sio breakage") In-Reply-To: <199812010450.PAA27337@godzilla.zeta.org.au> from Bruce Evans at "Dec 1, 1998 3:50:12 pm" To: bde@zeta.org.au (Bruce Evans), gurney_j@efn.org (John-Mark Gurney) Date: Wed, 2 Dec 1998 06:12:10 -0600 (CST) Cc: bde@zeta.org.au, kato@ganko.eps.nagoya-u.ac.jp, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, mike@smith.net.au, ortmann@sparc.isl.net X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Fixes: > >> kernel: send a fatal signal to applications that do this. > > > >How to detect this? > > Near the beginning of trap(): > > if ((frame.tf_eflags & PSL_I) == 0) > fatal(...); > > but this is too strong, since the application may be in the middle > of changing hardware state. Returning to the application probably > won't make the problem (the application's problem of changing state > atomically) worse, so we should enable interrupts and print an error > message. > > PSI_I must be checked even in traps from kernel mode because the trap > may be nested. In kernel mode, just enable interrupts and continue. I found the problem with my slow-running clock! Here is the fix: 1) disable power management in the BIOS 2) remove apm from my kernel's config file Perhaps merely one of the above is sufficient. I did both 1 & 2. I recall that my sio silo overflow messages began to appear suddenly after a period of time ... as if a switch were thrown. Perhaps the above steps will also make those messages go away; this is probable since they seemed to appear at the same time. I will log a pr right away. -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 04:21:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14226 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:21:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14218 for ; Wed, 2 Dec 1998 04:21:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA07407; Wed, 2 Dec 1998 04:23:13 -0800 (PST) To: John Birrell cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 22:58:38 +1100." <199812021158.WAA08572@cimlogic.com.au> Date: Wed, 02 Dec 1998 04:23:12 -0800 Message-ID: <7403.912601392@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... and group. We should test for each user and group defined in the > src/etc files and add them if they don't exist in the installed system. > This would make bootstrapping FreeBSD sources on a NetBSD system easier > too. [Uh oh, I guess they're going to yell at me again. They seem to react > badly when I say these things. 8-)] Hmmm. Just off the top of my head (and my shell wizardry skills are a bit rusty so please excuse the roughness of this), are you suggesting something like this: Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.46 diff -u -u -r1.46 Makefile.inc1 --- Makefile.inc1 1998/11/28 13:14:58 1.46 +++ Makefile.inc1 1998/12/02 12:17:34 @@ -260,6 +260,12 @@ .endif @echo @echo "--------------------------------------------------------------" + @echo ">>> Making required new users and groups" + @echo "--------------------------------------------------------------" + @awk -F: '{printf("if ! grep -q ^%s: /etc/master.passwd; then pw useradd %s -u %d -g %d; fi\n", $1, $1, $3, $4); }' ${.CURDIR}/etc/master.passwd | sh + @awk -F: '{printf("if ! grep -q ^%s: /etc/group; then pw groupadd %s -g %d; fi\n", $1, $1, $4); }' ${.CURDIR}/etc/group | sh + @echo + @echo "--------------------------------------------------------------" @echo ">>> Making hierarchy" @echo "--------------------------------------------------------------" mkdir -p ${WORLDTMP} ? If so, I'd be interested in seeing a more polished version of the above committed by somebody in this discussion (it can be me, if necessary, I'm just giving others ample opportunity for it to be them instead :-). The "fix" above has some immediate problems with it, most notably the hardcoded references to awk and sh as well as the missing ${DESTDIR} in front of /etc/master.passwd and /etc/group. That's a casualty of the single quotes around awk's command line arg which would prevent a ${DESTDIR} in the obvious places from expanding, and I am too tired at the moment to even contemplate the more advanced shell wizardry required to cons up more suitable arguments to awk. .. and I'm sure the perl weenies could easily figure out some way to do it in even less characters. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 04:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15307 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:33:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA15301 for ; Wed, 2 Dec 1998 04:33:22 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA07714; Wed, 2 Dec 1998 23:33:08 +1100 Date: Wed, 2 Dec 1998 23:33:08 +1100 From: Bruce Evans Message-Id: <199812021233.XAA07714@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, jkh@zippy.cdrom.com Subject: Re: Uh oh... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >number?" coming in - there's really just no substitute for getting the >new entries into the password file. > >Fortunately, the pw(8) command makes this pretty easy to do. You can >check to see if the user/uid is already there by doing something like: > > if pw usershow bind > /dev/null 2>&1; then > pw useradd bind ..other args.. > fi > >In /usr/src/Makefile.inc1's buildworld rule (I'd stick it before the >hierarchy stuff, for obvious reasons). `make world' is not permitted to change /etc. Especially not /etc/master.passwd when installing to DESTDIR=/mnt/root. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 04:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17035 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:49:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17030 for ; Wed, 2 Dec 1998 04:49:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA07535; Wed, 2 Dec 1998 04:50:57 -0800 (PST) To: Bruce Evans cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 23:33:08 +1100." <199812021233.XAA07714@godzilla.zeta.org.au> Date: Wed, 02 Dec 1998 04:50:56 -0800 Message-ID: <7532.912603056@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > `make world' is not permitted to change /etc. Especially not > /etc/master.passwd when installing to DESTDIR=/mnt/root. Normally I'd agree, but... Your counter-suggestion? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 05:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18456 for freebsd-current-outgoing; Wed, 2 Dec 1998 05:04:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18450 for ; Wed, 2 Dec 1998 05:04:25 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA09902; Thu, 3 Dec 1998 00:04:08 +1100 Date: Thu, 3 Dec 1998 00:04:08 +1100 From: Bruce Evans Message-Id: <199812021304.AAA09902@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@zippy.cdrom.com Subject: Re: Uh oh... Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> `make world' is not permitted to change /etc. Especially not >> /etc/master.passwd when installing to DESTDIR=/mnt/root. > >Normally I'd agree, but... Your counter-suggestion? `vipw' is good enough for bootstrapping to -current. For 2.2.5R we apparently required manual configuration to add group network which is required for at least the installation of ppp. This didn't seem to cause many problems. `make release' should use a new version of /etc/passwd in the chroot tree so it shouldn't be affected. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 05:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18489 for freebsd-current-outgoing; Wed, 2 Dec 1998 05:04:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18479 for ; Wed, 2 Dec 1998 05:04:36 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zlBx6-000I5dC; Wed, 2 Dec 1998 08:04:20 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: USERCONFIG_BOOT In-Reply-To: <199812020305.TAA02102@dingo.cdrom.com> from Mike Smith at "Dec 1, 1998 7: 5:46 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 2 Dec 1998 08:04:20 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there some reason why this option has not > > been incorporated into the current source tree? > > It's obsolete, and was removed. See the commit logs for > sys/i386/i386/userconfig.c and the HEADS UP that I posted to the > -current list (which as a -current user you *must* be reading). > I don't think it's obsolete yet. I have to re-enter the pnp commands after installing a new kernel. The effects of the last such command of the series are otherwise lost for my AWE soundcard. I guess I had better sign up for current.... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 05:19:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20069 for freebsd-current-outgoing; Wed, 2 Dec 1998 05:19:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19928; Wed, 2 Dec 1998 05:19:35 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id IAA23868; Wed, 2 Dec 1998 08:19:08 -0500 (EST) (envelope-from matt@zigg.com) Date: Wed, 2 Dec 1998 08:19:08 -0500 (EST) From: Matt Behrens To: Matthew Dillon cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit In-Reply-To: <199812012143.NAA10640@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, Matthew Dillon wrote: : I accidently created a /usr/src/etc/namedb/s directory and cvs add'd : it, then realized that it shouldn't be in the source tree (mtree handles : creating it in production). I've cvs deleted it but it will not commit : the deletion to the server. i.e. 'cvs commit' thinks there is nothing : to do. Very odd. I'd appreciate it if a cvs god looked at that! directory adds and commits, AFAIK, do not need to be committed. Then again, our CVS server at work (running Linux, blech) has a few phantom directories that I had to just remove from the box directly. :) Matt Behrens | If only I could learn Japanese and get my Servant of Karen Behrens | hands on all 200 Sailor Moon episodes and Engineer, Nameless IRC Network | all the movies, I think my life would I eat Penguins for breakfast. | finally be complete. . . . . . . . . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 05:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20693 for freebsd-current-outgoing; Wed, 2 Dec 1998 05:26:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20687 for ; Wed, 2 Dec 1998 05:26:44 -0800 (PST) (envelope-from andrea.franceschini@linet.it) Received: from oma.linet.it (unverified [194.185.24.77]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 02 Dec 1998 14:17:14 +0100 Message-ID: <003701be1df4$ee86f400$4d18b9c2@oma.linet.it> Reply-To: "andrea" From: "andrea" To: Subject: ip-masquerading.natd,ip-aliasing .... Date: Wed, 2 Dec 1998 14:09:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm looking for a way to configure my intranet using natd. The problem is that the configuration that i need is a little unsual and i wonder if is applicable. The configuration is as follow: On the Same LAN : 1 - Web Server (with routable Ip-address) 2 - Mail Server ( "" "" "" ) 3 - 1 router connected to the InterNet. 4 - Many other boxes with not Routeble ip addresses (192.168.. ) So i have 2 subnet on the same phisical net. What i'm wondering is: It's possible to share in the same phisical Lan( eg without gateway with 2+ Ether Card) between 2 networks? I'have tried assigning 2 ip address at the same interface ,and using this machine as a gateway on the same phisical net. So the first half of the LAN have direct access to Internet, second half have to use the gateway with natd (or SOCK ,or other proxy solutions). But it doesn't work :( There's a way to implement the above,or i must change mind..? P.S. Forgive me if what i'have written is sense-less,i'm a newbie:) P.P.S (Sorry for English) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 05:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22492 for freebsd-current-outgoing; Wed, 2 Dec 1998 05:45:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22483 for ; Wed, 2 Dec 1998 05:45:30 -0800 (PST) (envelope-from matt@camtech.com.au) Received: from dialup-ad-12-22.camtech.net.au (dialup-ad-12-22.camtech.net.au [203.55.242.22]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA04756; Thu, 3 Dec 1998 00:13:57 +1030 (CST) Date: Thu, 3 Dec 1998 00:17:02 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 still dumps core In-Reply-To: <4.1.19981201215111.0092f100@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try removing your .netscape directory (or remname it) On Tue, 1 Dec 1998, Forrest Aldrich wrote: > I did a build world this afternoon, I un-installed and remade the > XFree86-3.3.3 system (yes, with > a.out support), remade windowmaker, remake tcl/tk8.0 (which shouldn't make > a diff here). > > I give up. This thing still keeps dumping core with "exited on signal 11 > (core dumped)". It's > getting very old. > > Who provided this compiled port? I think it's probably time to update the > build anyways. > > > ??? > > > Forrest > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 06:55:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00596 for freebsd-current-outgoing; Wed, 2 Dec 1998 06:55:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall2.bb.consol.de (gate2.consol.de [194.221.87.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00590 for ; Wed, 2 Dec 1998 06:55:57 -0800 (PST) (envelope-from Michael.Elbel@consol.de) X-Envelope-Sender-Is: Michael.Elbel@consol.de (at relayer firewall2.bb.consol.de) Received: from msgsrv.bb.consol.de (root@msgsrv.bb.consol.de [10.250.0.100]) by firewall2.bb.consol.de (8.9.1a/8.9.1) with ESMTP id PAA21759; Wed, 2 Dec 1998 15:55:33 +0100 (CET) Received: from fourier.int.consol.de (fourier.int.consol.de [10.0.1.17]) by msgsrv.bb.consol.de (8.8.8/8.8.8) with ESMTP id PAA19261; Wed, 2 Dec 1998 15:55:33 +0100 Received: (from me@localhost) by fourier.int.consol.de (8.9.1/8.8.7) id PAA01257; Wed, 2 Dec 1998 15:55:32 +0100 (CET) (envelope-from me) Date: Wed, 2 Dec 1998 15:55:32 +0100 (CET) From: Michael Elbel Message-Id: <199812021455.PAA01257@fourier.int.consol.de> To: muck@ida.net Cc: current@FreeBSD.ORG Subject: Re: Page fault response from OSS Newsgroups: lists.freebsd.current References: Reply-To: me@FreeBSD.ORG X-Newsreader: NN version 6.5.0 CURRENT #123 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In lists.freebsd.current you write: >How current are you? With a kernel cvsup'd on 25 Nov, I can use the oss >drivers just fine. ># cd /usr/local/lib/oss ># ./soundon >OSS/FreeBSD loading, address = f410b020 >Open Sound System is licensed for evaluation purposes only. Hmm. I'm running -current from yesterday and don't have much luck with OSS. The system wedges so hard I have to reset it, can't even get into the kernel debugger. Using my trusty old original Gravis Ultrasound this would happen immediately after starting e.g. x11amp. Using a noname CMI8330-blah card, it will work for a while (like three or four mp3 songs) and *then* wedge. So, your mileage may vary. >I'm listening to a Def Leppard cd while typing this email. >I typed soundon immediately after booting up and logging on. Are you actually *using* the card for playing sound versus just routing your cd audio through? Michael -- \|/ -O- Michael Elbel, ConSol* GmbH, - me@consol.de - 089 / 45841-256 /|\ Fermentation fault (coors dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 07:03:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01492 for freebsd-current-outgoing; Wed, 2 Dec 1998 07:03:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01480; Wed, 2 Dec 1998 07:03:45 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id JAA05699; Wed, 2 Dec 1998 09:03:29 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma005684; Wed, 2 Dec 98 09:03:24 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id JAA22560; Wed, 2 Dec 1998 09:03:23 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Wed, 2 Dec 1998 09:03:23 -0600 (CST) From: Kyle Mestery To: me@FreeBSD.ORG cc: muck@ida.net, current@FreeBSD.ORG Subject: Re: Page fault response from OSS In-Reply-To: <199812021455.PAA01257@fourier.int.consol.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, 2 Dec 1998, Michael Elbel wrote: > Hmm. I'm running -current from yesterday and don't have much luck with > OSS. The system wedges so hard I have to reset it, can't even get into the > kernel debugger. Using my trusty old original Gravis Ultrasound this would > happen immediately after starting e.g. x11amp. > I also see these lockups with the latest OSS sound driver from their website. If I try and run xquake, the machine wedges hard requiring a hard reset. If I play some mp3 songs, I can play about 5-6 songs, then X locks up (this is with x11amp). I can still remotely get to the machine, but the X display (local) is useless at this point, and the machine has to be reset remoetely. > Using a noname CMI8330-blah card, it will work for a while (like three or > four mp3 songs) and *then* wedge. So, your mileage may vary. > -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 07:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03149 for freebsd-current-outgoing; Wed, 2 Dec 1998 07:24:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA03094 for ; Wed, 2 Dec 1998 07:23:50 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: vallo@matti.ee Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG, Terry Lambert , "John S. Dyson" Subject: Re: CODA on FreeBSD-CURRENT ... an interesting vm bug References: <4.1.19981123122653.00abfe40@206.25.93.69> <19981125142249.B38959@matti.ee> From: "Robert V. Baron" Date: 02 Dec 1998 10:23:01 -0500 In-Reply-To: Vallo Kallaste's message of Wed, 25 Nov 1998 14:22:49 +0200 Message-ID: Lines: 67 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the bug is not that interesting ... I tried cvsup into coda on a 11/05 kernel. Doing cvsup'ing src worked, but then I switched the tag from RELENG_2_2 to . and the system crashed ... panic: lockmgr: pid -2, not exclusive lock holder 23390 unlocking Debugger("panic") The stack trace looks like: db> tr _Debugger(f0123a7b) at _Debugger+0x35 _panic(f011f0b1,fffffffe,f011f09b,5b5e,f419cd8c) at _panic+0x6f _lockmgr(f08cbe00,6,f41897f0,0,f419cc84) at _lockmgr+0x2b3 _vop_stdunlock(f419cd18,f419cd2c,f01076b7,f419cd18,f419cd70) at _vop_stdunlock+0x23 _ufs_vnoperate(f419cd18) at _ufs_vnoperate+0x15 _coda_rdwr(f421ef00,f419cd8c,0,0,f079c780) at _coda_rdwr+0x10f _coda_read(f419cd70,0,1,0,166) at _coda_read+0x50 _vnode_pager_input_old(f41c03b8,f043c858,f421ef00,1000,0) at _vnode_pager_input_old+0xf2 _vnode_pager_generic_getpages(f421ef00,f419cf18,1000,0,f419ce88) at _vnode_pager_generic_getpages+0xea _coda_fbsd_getpages(f419ce6c) at _coda_fbsd_getpages+0x17 _vnode_pager_getpages(f41c03b8,f419cf18,1,0,f419cf58) at _vnode_pager_getpages+0x4e _vm_pager_get_pages(f41c03b8,f419cf18,1,0) at _vm_pager_get_pages+0x1f _vm_fault(f40b1800,201f7000,1,0,f40ad080) at _vm_fault+0x464 _trap_pfault(f419cfbc,1) at _trap_pfault+0xf6 _trap(27,27,26f1cc,0,567a60) at _trap+0x137 calltrap() at calltrap+0x1c What is happening here is that coda_rdwr does a VFS_VGET to get a vnode the hardway. The vnode comes back locked (probably thru vget) and is locked by the process "curproc" (cvsup in this case). But coda_rdwr needs to unlock the vnode. It gets its process pointer from the uio_procp field of the uio argument. Well vnode_pager_input_old sets this field to 0 ... not curproc! Thus the unlock fails with the panic above. moral: vnode_pager_input_old gets called in a process context so it should use curproc not 0 as its procp. I fixed a different coda/related bug in vnode_pager_input_coda earlier, so if there are no major objections I will commit this change Fri noon. With the earlier bug (look in the "current" archives for vnode_pager_input_old around Sep 28.), I determined that only coda used vnode_pager_input_old, so I don't expect this change to effect anyone besides Coda. Vallo Kallaste writes: > Forrest Aldrich wrote: > > > Wondered about anyone's experience with CODA on FreeBSD-CURRENT. > > I see that vinum and some other stuff is included in the source tree, but want > > to find out more about people's experience (good and bad) with these. Are > > they stable, etc. > > I have tried CODA on current-elf machines. One acts as server and > one as a client :-) , but my client machine crash everytime I run > cvsup on /coda mounted /usr/src. As the cvsup crashes client > machine everytime, I mark coda as unstable for me and don't spend > any more time, althought it seems very interesting and suitable for > our needs. Maybe I should try an aout version instead, because it's > better supported and tested ? Anyone knowledgeable ? > > > Vallo Kallaste > vallo@matti.ee > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 07:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05096 for freebsd-current-outgoing; Wed, 2 Dec 1998 07:44:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05079; Wed, 2 Dec 1998 07:44:54 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA20290; Wed, 2 Dec 1998 10:44:24 -0500 (EST) (envelope-from wollman) Date: Wed, 2 Dec 1998 10:44:24 -0500 (EST) From: Garrett Wollman Message-Id: <199812021544.KAA20290@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Uh oh... In-Reply-To: <6721.912594438@zippy.cdrom.com> References: <6721.912594438@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I think we've created a slight bootstrapping problem here. "make > world" is still the official method of upgrading a system via sources > and it's supposed to handle all bootstrapping issues like this > automagically. It has never in the past handled creating new users or groups. Witness the `network' group, the `xten' user, the `uucp' user, the `man' group, and the `dialer' group. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 08:21:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08797 for freebsd-current-outgoing; Wed, 2 Dec 1998 08:21:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08790 for ; Wed, 2 Dec 1998 08:20:56 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id OAA22144; Wed, 2 Dec 1998 14:17:14 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199812021617.OAA22144@roma.coe.ufrj.br> Subject: Re: Uh oh... In-Reply-To: <7532.912603056@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 98 04:50:56 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Dec 1998 14:17:14 -0200 (EDT) Cc: bde@zeta.org.au, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Jordan K. Hubbard) // > `make world' is not permitted to change /etc. Especially not // > /etc/master.passwd when installing to DESTDIR=/mnt/root. // // Normally I'd agree, but... Your counter-suggestion? Check the existence of every user and group needed for the system, at the very beggining of the make world, and stop the compilation if they are not present. This should be done the earliest possible, and must show every needed user, including the probably obvious ones. BTW: Are there any rules about user and group id selection ? Say, 0-99 are reserved to the system, etc. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 08:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11397 for freebsd-current-outgoing; Wed, 2 Dec 1998 08:45:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11392 for ; Wed, 2 Dec 1998 08:45:17 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA01900; Wed, 2 Dec 1998 11:45:03 -0500 (EST) Date: Wed, 2 Dec 1998 11:45:03 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Steve Kargl cc: freebsd-current@FreeBSD.ORG Subject: Re: Crash dump howto? In-Reply-To: <199812012207.OAA00603@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Upgrade to a more current -CURRENT. I could've sworn the reallocblk bug was fixed. If not, there's also a sysctl oid to turn it off. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 08:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12344 for freebsd-current-outgoing; Wed, 2 Dec 1998 08:52:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12339 for ; Wed, 2 Dec 1998 08:52:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id IAA41596; Wed, 2 Dec 1998 08:59:59 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812021659.IAA41596@troutmask.apl.washington.edu> Subject: Re: Crash dump howto? In-Reply-To: from Brian Feldman at "Dec 2, 1998 11:45: 3 am" To: green@unixhelp.org (Brian Feldman) Date: Wed, 2 Dec 1998 08:59:59 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Feldman: > Upgrade to a more current -CURRENT. I could've sworn the reallocblk bug was > fixed. If not, there's also a sysctl oid to turn it off. > I have sources from 2 days ago. I have version 1.74 of vfs_cluster.c which is alleged to have fixed the problem. It doesn't. My sources are cvsup'd from cvsup.freebsd.org. I can kill the system under heavy load with either and ELF or aout kernel. I can not get the system to produce a crash dump. So, the question remains how does one force a dump? -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 09:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13137 for freebsd-current-outgoing; Wed, 2 Dec 1998 09:01:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13132 for ; Wed, 2 Dec 1998 09:01:52 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id JAA00768; Wed, 2 Dec 1998 09:01:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812021701.JAA00768@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Troy Kittrell cc: Christian Kuhtz , freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 still dumps core In-reply-to: Your message of "Wed, 02 Dec 1998 00:15:49 CST." <3664DB15.398E057B@basspro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 09:01:07 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday, I was able to crash netscape with no problems fairly consistently with http://www.abcnews.com or http://www.fortify.net/sslcheck.html My system rah was a couple of weeks old after a cvsup last nite, make world, and a new kernel, netscape seems not to crash. Got the clue from my test box , cioloco, which I couldn't get netscape to crash and it usually runs a fairly recent -current. I am using XFree86 3.3.3 on both of my machines. Regards, Aamncio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 09:08:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13576 for freebsd-current-outgoing; Wed, 2 Dec 1998 09:08:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13571 for ; Wed, 2 Dec 1998 09:08:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id JAA00824; Wed, 2 Dec 1998 09:06:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812021706.JAA00824@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma cc: Mike Smith , van.woerkom@netcologne.de, jkh@zippy.cdrom.com, forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Wed, 02 Dec 1998 09:47:59 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 09:06:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... unload probe/init code when it is no longer needed. > How do you propose to do that with device drivers that have a large physically contiquous memory space allocated? Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 09:17:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14188 for freebsd-current-outgoing; Wed, 2 Dec 1998 09:17:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14178 for ; Wed, 2 Dec 1998 09:17:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA17582; Wed, 2 Dec 1998 09:17:09 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 09:17:09 -0800 (PST) From: Matthew Dillon Message-Id: <199812021717.JAA17582@apollo.backplane.com> To: Bruce Evans Cc: bde@zeta.org.au, jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: Uh oh... References: <199812021304.AAA09902@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What if we add a flag to the mtree config to allow a pre and post mtree run? mtree itself doesn't take very long to run, so it wouldn't add too much extra overhead. We could defer the mtree support for the special users from the make stage and put it in the install stage. If worse comes to worse, remove the /etc/namedb/s entry for the mtree commit that I did and we can simply put a suitable comment in named.conf. The system does not use that directory by default, but I thought it would be a good idea to pre-create it to make it easier for users who may not be familiar with bind-8's sandbox capabilities. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 09:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15092 for freebsd-current-outgoing; Wed, 2 Dec 1998 09:28:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15084 for ; Wed, 2 Dec 1998 09:28:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA17722; Wed, 2 Dec 1998 09:28:04 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 09:28:04 -0800 (PST) From: Matthew Dillon Message-Id: <199812021728.JAA17722@apollo.backplane.com> To: Steve Kargl Cc: green@unixhelp.org (Brian Feldman), freebsd-current@FreeBSD.ORG Subject: Re: Crash dump howto? References: <199812021659.IAA41596@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I have sources from 2 days ago. I have version 1.74 of vfs_cluster.c :which is alleged to have fixed the problem. It doesn't. My sources :are cvsup'd from cvsup.freebsd.org. : :I can kill the system under heavy load with either and ELF or aout kernel. : :I can not get the system to produce a crash dump. : :So, the question remains how does one force a dump? : :-- :Steve This is what we do: options DDB options COMCONSOLE # serial console vs normal console options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to #DDB, if available. And in /etc/rc.conf.local: dumpdev="/dev/sd0b" Make sure the dump device (typically primary swap) is at least as large as your main memory or the system will not be able to dump. If the system farts, it will break into the debugger on the serial console (make sure whatever you connect to the serial console is itself secure!). From the ddb> prompt you can usually 'panic'. Sometimes it takes a 'panic' followed by an extra return, but be careful not to interrupt the dump in-progress because a return will also abort that. The debug monitor can also be used to do a simple stack backtrace, ps, and a few other things before you panic the machine. This can be useful if the dump fails to work. Also make sure you are using a reasonably standardized /etc/rc that properly savecore's the dumps, and that /var/crash is big enough to hold the writeout (a bit more then the main memory size in free space must be available). -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 09:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17257 for freebsd-current-outgoing; Wed, 2 Dec 1998 09:53:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17252 for ; Wed, 2 Dec 1998 09:53:32 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id KAA55752; Wed, 2 Dec 1998 10:01:17 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812021801.KAA55752@troutmask.apl.washington.edu> Subject: Re: Crash dump howto? In-Reply-To: <199812021728.JAA17722@apollo.backplane.com> from Matthew Dillon at "Dec 2, 1998 9:28: 4 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 2 Dec 1998 10:01:16 -0800 (PST) Cc: green@unixhelp.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Dillon: > > : > :So, the question remains how does one force a dump? > : > :-- > :Steve > > This is what we do: > > options DDB I have this option, and can break to the debugger. > > And in /etc/rc.conf.local: > > dumpdev="/dev/sd0b" > > Make sure the dump device (typically primary swap) is at least as large > as your main memory or the system will not be able to dump. > I have tried /dev/da0s1b, /dev/da1s1b, and /dev/da1b with appropriately labelled disk. da0s1b is 500 MB in size and da1s1b is 700 MB in size. I have 256 MB of main memory. > If the system farts, it will break into the debugger on the > serial console (make sure whatever you connect to the serial console is > itself secure!). From the ddb> prompt you can usually 'panic'. Sometimes > it takes a 'panic' followed by an extra return, but be careful not to > interrupt the dump in-progress because a return will also abort that. db>panic panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on CPU #1 (da1:ahc0:0:2:0) SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:2:0) error code 0 dumping to dev 409, offset 907232 Fatal trap 12: page fault while in kernel mode mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x20 fault code = supervisor read, page not present instruction pointer = 0x8:0x20 stack pointer = 0x10:0xf9232998 frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32, 1, gran 1 process eflags = interrupt enabled, resume, IOPL = 0 current process = 95350 (procmail) interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code = 0 Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> panic Reach for reset button. > The debug monitor can also be used to do a simple stack backtrace, ps, > and a few other things before you panic the machine. This can be useful > if the dump fails to work. I've provided strack traces. There are a few hundred processes. The dump never seems to actually happen. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 10:01:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18041 for freebsd-current-outgoing; Wed, 2 Dec 1998 10:01:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18026 for ; Wed, 2 Dec 1998 10:01:20 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA04843; Wed, 2 Dec 1998 12:58:44 -0500 (EST) Date: Wed, 2 Dec 1998 12:58:44 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Mike Smith cc: Andrzej Bialecki , Pascal Hofstee , Shawn Ramsey , oZZ!!! , current@FreeBSD.ORG Subject: Re: StarOffice-5.0... In-Reply-To: <199811290924.BAA00650@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Mike Smith wrote: > > Yes, I've got the diffs against relatively fresh current. BTW, I asked > > this question on -emulation, but got back a profound silence... Can we/ > > should we incorporate this patch, and hide it under a kernel option, say > > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux > > emulation... > > A couple of things: > > - If it's part of our emulation support, it should probably be the > default (cringe). > - Your patch doesn't preserve the remainder of the commandline > arguments. Feel like fixing this and resubmitting it? I suppose there is no easy way for the procfs code to determine if the relevant calls are coming from a linux emulated process or not? If there were, then the command line stuff could be made only to appear for Linux processes. I'm guessing, however, that only the creds and arguments to the vfs call make it that far down, and use of curproc seems inappropriate? Or, if loadable kernel modules (or whatever they are called today) could add hook functions to the procfs module via some symbol or another, then new items could be added based on context. That however, seems a little too busy, given that stackable file systems don't work. :) Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 11:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24183 for freebsd-current-outgoing; Wed, 2 Dec 1998 11:21:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24176 for ; Wed, 2 Dec 1998 11:21:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA18143; Wed, 2 Dec 1998 11:20:57 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 11:20:57 -0800 (PST) From: Matthew Dillon Message-Id: <199812021920.LAA18143@apollo.backplane.com> To: Steve Kargl Cc: green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: Crash dump howto? References: <199812021801.KAA55752@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :db>panic :panic: from debugger :... :mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 :boot() called on CPU #1 :(da1:ahc0:0:2:0) SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 :(da1:ahc0:0:2:0) error code 0 : :dumping to dev 409, offset 907232 : :Fatal trap 12: page fault while in kernel mode :mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 :fault virtual address = 0x20 :fault code = supervisor read, page not present :instruction pointer = 0x8:0x20 :stack pointer = 0x10:0xf9232998 :frame pointer = 0x10:0x0 :code segment = base 0x0, limit 0xfffff, type 0x1b : = DPL 0, pres 1, def32, 1, gran 1 :process eflags = interrupt enabled, resume, IOPL = 0 :current process = 95350 (procmail) :interrupt mask = net tty bio cam <- SMP: XXX :kernel: type 12 trap, code = 0 :Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 :db> panic : :Reach for reset button. Oh, this is bad... it tried to dump but got a page fault while trying to dump. That pretty much does it in. You could try attaching a debugger over the serial console, but I have never done that myself so I can't give exact instructions. -Matt :-- :Steve : :finger kargl@troutmask.apl.washington.edu :http://troutmask.apl.washington.edu/~clesceri/kargl.html : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 11:44:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26635 for freebsd-current-outgoing; Wed, 2 Dec 1998 11:44:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26630 for ; Wed, 2 Dec 1998 11:44:33 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id GAA09742; Thu, 3 Dec 1998 06:52:04 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812021952.GAA09742@cimlogic.com.au> Subject: Re: Uh oh... In-Reply-To: <7403.912601392@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 98 04:23:12 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 3 Dec 1998 06:52:03 +1100 (EST) Cc: jb@cimlogic.com.au, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > Hmmm. Just off the top of my head (and my shell wizardry skills are a > bit rusty so please excuse the roughness of this), are you suggesting > something like this: [...] > If so, I'd be interested in seeing a more polished version of the > above committed by somebody in this discussion (it can be me, if > necessary, I'm just giving others ample opportunity for it to be them > instead :-). The "fix" above has some immediate problems with it, > most notably the hardcoded references to awk and sh as well as the > missing ${DESTDIR} in front of /etc/master.passwd and /etc/group. > That's a casualty of the single quotes around awk's command line arg > which would prevent a ${DESTDIR} in the obvious places from expanding, > and I am too tired at the moment to even contemplate the more advanced > shell wizardry required to cons up more suitable arguments to awk. > > .. and I'm sure the perl weenies could easily figure out some way to > do it in even less characters. :-) Yes, however there is the "rule" of not touching the installed system until installworld. I think that mtree should read src/etc/master.passwd and src/etc/group to get the uid/gid values. This avoids the dependency of the hierarchy on awk etc as build tools. The new mtree version would need to be bootstrapped early like make is. The installworld step should do the ${DESTDIR}/etc update (also adding any missing .conf files too). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 11:49:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26994 for freebsd-current-outgoing; Wed, 2 Dec 1998 11:49:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26987 for ; Wed, 2 Dec 1998 11:49:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA18355; Wed, 2 Dec 1998 11:48:39 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 11:48:39 -0800 (PST) From: Matthew Dillon Message-Id: <199812021948.LAA18355@apollo.backplane.com> To: John Birrell Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Uh oh... References: <199812021952.GAA09742@cimlogic.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Yes, however there is the "rule" of not touching the installed system :until installworld. I think that mtree should read src/etc/master.passwd :and src/etc/group to get the uid/gid values. This avoids the dependency :of the hierarchy on awk etc as build tools. The new mtree version :would need to be bootstrapped early like make is. The installworld step :should do the ${DESTDIR}/etc update (also adding any missing .conf files :too). : :-- :John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ :CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 This sounds like a clean solution. Better then my two-pass idea, anyway! -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27765 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:00:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27760 for ; Wed, 2 Dec 1998 12:00:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA18484; Wed, 2 Dec 1998 12:00:06 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Dec 1998 12:00:06 -0800 (PST) From: Matthew Dillon Message-Id: <199812022000.MAA18484@apollo.backplane.com> To: Matthew Dillon Cc: John Birrell , jkh@zippy.cdrom.com (Jordan K. Hubbard), jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Uh oh... References: <199812021952.GAA09742@cimlogic.com.au> <199812021948.LAA18355@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, since this is obviously gotten to be more complex, I've backed-out the mtree portion of my commit and added additional comments to /usr/src/etc/named.conf. We still need to keep in mind that we should probably create the appropriate new groups & master.passwd entries in an install, but not doing so no longer breaks buildworld. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:05:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28074 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:05:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28068 for ; Wed, 2 Dec 1998 12:05:11 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id PAA06961; Wed, 2 Dec 1998 15:07:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 2 Dec 1998 15:07:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Matthew Dillon cc: John Birrell , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <199812021948.LAA18355@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Matthew Dillon wrote: > : > :Yes, however there is the "rule" of not touching the installed system > :until installworld. I think that mtree should read src/etc/master.passwd > :and src/etc/group to get the uid/gid values. This avoids the dependency > :of the hierarchy on awk etc as build tools. The new mtree version > :would need to be bootstrapped early like make is. The installworld step > :should do the ${DESTDIR}/etc update (also adding any missing .conf files > :too). > : > :-- > :John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > :CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 > > This sounds like a clean solution. Better then my two-pass idea, anyway! How about this: make world - complain about which uids/gids are missing. make buildworld - nothing. make installworld - complain about which uids/gids are missing. I think being intrusive to someone's /etc directory is a mean thing to sneak in, as well have allowing someone to walk away for a long time only to have the build fail halfway through. It's a rude shock to experianced users and a major disapointment to new users just starting to track the tree. I also wish back when i was updating 2.2.god-knows-what to 2.2.6 this would have been in place instead of me bungling around running installworld over and over while it bombed out. Keeping the checks right at the start of the build keeps the upgrade/tracking easier to end users. # make world ----- error: you need to add user(s): bind to the system before this will work # pw useradd .... # make world ----- starting build... yes, it does make 'make world' more dependant on the system utils available, but you could 'test -x' or something to skip it then. thanks, -Alfred > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:30:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01018 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:30:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01006 for ; Wed, 2 Dec 1998 12:30:43 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Thu, 3 Dec 1998 07:29:44 +1100 Date: Thu, 3 Dec 1998 07:30:20 +1100 From: Peter Jeremy Subject: Re: sio breakage To: current@FreeBSD.ORG Message-Id: <98Dec3.072944est.40336@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: >>I'd suggest sending SIGBUS, with the interrupts enabled. This would >>allow the application to recover if necessary. > >Recovery may be impossible, since timing for the critical region may >have been violated I should have said `if possible', rather than `if necessary'. In fact if the process was in the middle of fiddling with the hardware, the entire machine might be effectively hosed (eg, if XFree86 gets interrupted half-way through re-configuring the video card). >>I don't believe this is reasonable. We should provide some safe way >>for an application program to execute code with interrupts disabled. > >I gave a way: only access a single page (including for code). Having code and data on the same page is not particularly clean. (And having write permission to an executable memory block is a security hole). >Oops, this is not enough. The "cli" might work because it is cached I don't believe that the cache can contain data for a non-resident page. At least on the ix86, it's a physical-address cache, so the cache must (of necessity) be flushed if the page is reused. >But the application has no way of knowning if the memory is resident. man 2 mincore For most purposes (excluding systems thrashing), referencing all the affected pages before the CLI will be sufficient to ensure they are resident. >>The guaranteed approach is to use mlock(2) on the affected regions. >>This is also the most expensive (since multiple system calls are >>required). Whilst this only works for root, only root can normally >>open /dev/io (and hence use CLI/STI). > >It is cheap enough in time if the memory is kept locked, If you need to atomically execute a small number of instructions, the added overhead of 1 or 2 mlock/munlock pairs is relatively huge. Also, if we're just talking about initialisation code, having it locked in memory is wasteful. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01033 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:30:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00999; Wed, 2 Dec 1998 12:30:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA08556; Wed, 2 Dec 1998 12:32:10 -0800 (PST) To: Garrett Wollman cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 10:44:24 EST." <199812021544.KAA20290@khavrinen.lcs.mit.edu> Date: Wed, 02 Dec 1998 12:32:10 -0800 Message-ID: <8552.912630730@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It has never in the past handled creating new users or groups. > Witness the `network' group, the `xten' user, the `uucp' user, the `man' > group, and the `dialer' group. I think xten, uucp, user and dialer have been around for long enough that we didn't have much trouble with them. The `network' group was another one I fielded a lot of questions over. I think all this shows is that we've been here before and it sucked then too (I also guess that some core folk are avoiding our user base since it seems that some of you have formed a rather rose-colored impression of past events! :-). It's a bootstrapping issue which I'm even more solidly convinced should have *some* kind of safety belt installed, even if it just tells you "please go off and create user foo with uid 30 and gid 33" and cops out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01087 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:31:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01082 for ; Wed, 2 Dec 1998 12:31:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA08535; Wed, 2 Dec 1998 12:29:15 -0800 (PST) To: Bruce Evans cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Uh oh... In-reply-to: Your message of "Thu, 03 Dec 1998 00:04:08 +1100." <199812021304.AAA09902@godzilla.zeta.org.au> Date: Wed, 02 Dec 1998 12:29:14 -0800 Message-ID: <8532.912630554@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> `make world' is not permitted to change /etc. Especially not > >> /etc/master.passwd when installing to DESTDIR=/mnt/root. > > > >Normally I'd agree, but... Your counter-suggestion? > > `vipw' is good enough for bootstrapping to -current. Balls. You and I know both that this just isn't going to fly with the kinds of -current runners we're getting these days. They're going to complain bitterly. > For 2.2.5R we apparently required manual configuration to add group > network which is required for at least the installation of ppp. > This didn't seem to cause many problems. `make release' should Hahahahahahahahahaha. Thanks for the good laugh, Bruce, it's now very plain to me that you haven't been spending much time on the front lines of tech support lately. They raised the roof over that one! It's an excellent example of what I'm worried about, however, and I'm glad you brought it up. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 12:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02718 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:46:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02713 for ; Wed, 2 Dec 1998 12:46:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA08623; Wed, 2 Dec 1998 12:44:14 -0800 (PST) To: Matthew Dillon cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 09:17:09 PST." <199812021717.JAA17582@apollo.backplane.com> Date: Wed, 02 Dec 1998 12:44:13 -0800 Message-ID: <8619.912631453@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If worse comes to worse, remove the /etc/namedb/s entry for > the mtree commit that I did and we can simply put a suitable > comment in named.conf. The system does not use that directory > by default, but I thought it would be a good idea to pre-create > it to make it easier for users who may not be familiar with > bind-8's sandbox capabilities. That might end up being the path of least resistance here. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 13:01:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04271 for freebsd-current-outgoing; Wed, 2 Dec 1998 13:01:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04255; Wed, 2 Dec 1998 13:01:47 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA26382; Wed, 2 Dec 1998 14:01:27 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA07672; Wed, 2 Dec 1998 14:01:26 -0700 Date: Wed, 2 Dec 1998 14:01:26 -0700 Message-Id: <199812022101.OAA07672@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Garrett Wollman , current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <8552.912630730@zippy.cdrom.com> References: <199812021544.KAA20290@khavrinen.lcs.mit.edu> <8552.912630730@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It has never in the past handled creating new users or groups. > > Witness the `network' group, the `xten' user, the `uucp' user, the `man' > > group, and the `dialer' group. > > I think xten, uucp, user and dialer have been around for long enough > that we didn't have much trouble with them. The `network' group was > another one I fielded a lot of questions over. Actually, the 'mail' group was the biggest issue I remember during upgrades, but we won't mention any names who created that one. :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 13:39:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08000 for freebsd-current-outgoing; Wed, 2 Dec 1998 13:39:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07995 for ; Wed, 2 Dec 1998 13:39:03 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA26004; Wed, 2 Dec 1998 22:43:25 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 2 Dec 1998 22:43:25 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Matthew Dillon cc: Steve Kargl , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: Crash dump howto? In-Reply-To: <199812021728.JAA17722@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Matthew Dillon wrote: > :I can not get the system to produce a crash dump. > : > :So, the question remains how does one force a dump? > : > :-- > :Steve > > This is what we do: [snip] ...which is of course true and works most of the time, BUT not always. I will always remind you of remote GDB, because I experienced it myself how good this feature is. I was in situation where I couldn't produce crash dump no matter what I did (and I did everything according to the rules). The remote GDB was the only option left, and I regretted I discovered it so late... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 14:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14944 for freebsd-current-outgoing; Wed, 2 Dec 1998 14:47:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14938 for ; Wed, 2 Dec 1998 14:47:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from dev.lan.awfulhak.org (dev.lan.awfulhak.org [172.16.0.5]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA00205; Wed, 2 Dec 1998 22:23:20 GMT (envelope-from brian@Awfulhak.org) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by dev.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id WAA17289; Wed, 2 Dec 1998 22:23:19 GMT (envelope-from brian@dev.lan.awfulhak.org) Message-Id: <199812022223.WAA17289@dev.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Leif Neland cc: Brian Somers , freebsd-current@FreeBSD.ORG Subject: Re: user-ppp broken since a few days ago? In-reply-to: Your message of "Sat, 28 Nov 1998 22:23:34 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 22:23:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Fri, 27 Nov 1998, Brian Somers wrote: > > > Hi, > > > > What happens if you ``set openmode active 2'' ? > > > > Also, you may want to enable async logging to see what that initial > > data is - 0801 doesn't make much sense (is this consistent?). > > > > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: deflink: Dial attempt 1 of 1 > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: AT^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: AT^M^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATE1Q0^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: ATE1Q0^M^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATDI1001-xxxxxxxx^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Expect(40): CONNECT > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: ATDI1001-xxxxxxxx^M^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: CONNECT 115200/PPP 64000/NONE^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: dial -> login > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: login -> lcp > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: FSM: Using "deflink" as a transport > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Initial --> Closed > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: Entering STOPPED state for 2 seconds > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Closed --> Stopped > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: ReadFromModem > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e 7d 28 7d 21 7f a6 92 7e > Nov 28 22:14:48 gina ppp[11867]: tun0: Phase: Unknown protocol 0x0801 (unrecognised protocol) > Nov 28 22:14:48 gina ppp[11867]: tun0: LCP: deflink: SendProtocolRej(1) state = Stopped > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: WriteModem > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e ff 7d 23 c0 21 7d 28 7d 21 7d 20 7d 27 7d 28 > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7d 21 7f 57 67 7e > Nov 28 22:14:49 gina ppp[11867]: tun0: Async: ReadFromModem > Nov 28 22:14:49 gina ppp[11867]: tun0: Async: 0d 0a 4e 4f 20 43 41 52 52 49 45 52 0d 0a > Nov 28 22:14:49 gina ppp[11867]: tun0: Phase: deflink: Carrier lost > Nov 28 22:14:49 gina ppp[11867]: tun0: LCP: deflink: State change Stopped --> Closed > > Unknown protocol? Is that the same as the windows message "Dialup network > couldn't find a supported protocol. Check the servertype settings and the > settings in control panel" ? > Sometimes I and clients get this message when calling by isdn to the > portmaster 2e. It's roughly the same thing. Ppp sends configure requests for each supported protocol. If the peer doesn't support that protocol, it'll reject it. If all protocols are rejected, windows will give you this message. I would think that most of the time this means that they haven't configured a TCP stack on their machine.... The above log shows that the remote end hangs up (the line above ``Carrier lost'' says ``\r\nNO CARRIER\r\n''). This looks like a result of us rejecting whatever 0x0801 is - probably NetBUI or something like that :-/ > Leif Neland -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 14:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15523 for freebsd-current-outgoing; Wed, 2 Dec 1998 14:53:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15518 for ; Wed, 2 Dec 1998 14:53:31 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA28556; Wed, 2 Dec 1998 17:52:43 -0500 (EST) Date: Wed, 2 Dec 1998 17:52:43 -0500 (EST) From: "Matthew N. Dodd" To: John Birrell cc: "Jordan K. Hubbard" , dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <199812021158.WAA08572@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, John Birrell wrote: > ... and group. We should test for each user and group defined in the > src/etc files and add them if they don't exist in the installed > system. This would make bootstrapping FreeBSD sources on a NetBSD > system easier too. [Uh oh, I guess they're going to yell at me again. > They seem to react badly when I say these things. 8-)] Agree! On a related subject, is there any chance you can bring back the NetBSD bootstrap stuff and the NETBSD_SYSCALLS stuff? I've got NetBSD/sparc building FreeBSD-current userland save for some problems with the toolchain. I'm tracking down some problems in libc right now that cause things to segfault. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 14:58:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15868 for freebsd-current-outgoing; Wed, 2 Dec 1998 14:58:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15863 for ; Wed, 2 Dec 1998 14:58:08 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id SAA07247; Wed, 2 Dec 1998 18:00:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 2 Dec 1998 18:00:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Matthew N. Dodd" cc: current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Matthew N. Dodd wrote: > On a related subject, is there any chance you can bring back the NetBSD > bootstrap stuff and the NETBSD_SYSCALLS stuff? > > I've got NetBSD/sparc building FreeBSD-current userland save for some > problems with the toolchain. > > I'm tracking down some problems in libc right now that cause things to > segfault. Are you working on ultrasparc? or the 32bit processors? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 14:59:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16320 for freebsd-current-outgoing; Wed, 2 Dec 1998 14:59:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16246 for ; Wed, 2 Dec 1998 14:59:03 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id KAA10778; Thu, 3 Dec 1998 10:06:33 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812022306.KAA10778@cimlogic.com.au> Subject: Re: Uh oh... In-Reply-To: from "Matthew N. Dodd" at "Dec 2, 98 05:52:43 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 3 Dec 1998 10:06:33 +1100 (EST) Cc: jb@cimlogic.com.au, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew N. Dodd wrote: > On a related subject, is there any chance you can bring back the NetBSD > bootstrap stuff and the NETBSD_SYSCALLS stuff? If it helps you, yes. I took it out because I knew it would suffer bit-rot as NetBSD kept changing syscalls. > I've got NetBSD/sparc building FreeBSD-current userland save for some > problems with the toolchain. > > I'm tracking down some problems in libc right now that cause things to > segfault. Did you find a problem with using FreeBSD emulation on NetBSD/sparc? I'm also prepared to do the sparc-specific commits (like the ones I did for alpha) if that helps get things moving and allows people to share the work. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:01:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16681 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:01:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16676 for ; Wed, 2 Dec 1998 15:01:08 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA28741; Wed, 2 Dec 1998 18:00:03 -0500 (EST) Date: Wed, 2 Dec 1998 18:00:02 -0500 (EST) From: "Matthew N. Dodd" To: Joao Carlos Mendes Luis cc: "Jordan K. Hubbard" , bde@zeta.org.au, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <199812021617.OAA22144@roma.coe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Joao Carlos Mendes Luis wrote: > Check the existence of every user and group needed for the system, at > the very beggining of the make world, and stop the compilation if they > are not present. This should be done the earliest possible, and must > show every needed user, including the probably obvious ones. And tell them they can use 'make updategroupsandusers' to let the system do it for them. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:10:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17584 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:10:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17575 for ; Wed, 2 Dec 1998 15:10:07 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id VAA26615; Wed, 2 Dec 1998 21:09:13 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199812022309.VAA26615@roma.coe.ufrj.br> Subject: Re: Uh oh... In-Reply-To: from "Matthew N. Dodd" at "Dec 2, 98 06:00:02 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Wed, 2 Dec 1998 21:09:12 -0200 (EDT) Cc: jonny@jonny.eng.br, jkh@zippy.cdrom.com, bde@zeta.org.au, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Matthew N. Dodd) // On Wed, 2 Dec 1998, Joao Carlos Mendes Luis wrote: // > Check the existence of every user and group needed for the system, at // > the very beggining of the make world, and stop the compilation if they // > are not present. This should be done the earliest possible, and must // > show every needed user, including the probably obvious ones. // // And tell them they can use 'make updategroupsandusers' to let the system // do it for them. Is this safe to be done by a make script ? I was thinking about manual editing. Mostly because I'm not only thinking in the upgrade case, but also in some special cases in which a admin removes some previously existant groups, like network, man, bin or even wheel, thinking they have no use for him. Maybe a suggestion to look at src/etc/master.passwd, etc. could be enough. Anyway, make world should not be used by novices. :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18125 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:16:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18119 for ; Wed, 2 Dec 1998 15:16:46 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id KAA03651 for ; Thu, 3 Dec 1998 10:16:31 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd003648; Wed Dec 2 23:16:25 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id KAA14514 for ; Thu, 3 Dec 1998 10:16:30 +1100 (EST) Message-Id: <199812022316.KAA14514@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of Wed, 02 Dec 1998 12:32:10 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 10:16:20 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I discovered this one as well, on my very first "make buildworld" on a -current system.... I worked out what was required OK, but I added the new users with some randomly-chosen ID because I didn't think to look in the /usr/ src/etc directory [since fixed]. Which brings up a problem with the automatic adding of passwd/group entries: What if my passwd file already has an entry for that UID/GID? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18618 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:21:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18595 for ; Wed, 2 Dec 1998 15:21:07 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA00624; Wed, 2 Dec 1998 21:21:15 GMT (envelope-from nik) Message-ID: <19981202212115.51555@nothing-going-on.org> Date: Wed, 2 Dec 1998 21:21:15 +0000 From: Nik Clayton To: "Jordan K. Hubbard" , Bruce Evans Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... References: <199812021233.XAA07714@godzilla.zeta.org.au> <7532.912603056@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <7532.912603056@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Dec 02, 1998 at 04:50:56AM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 04:50:56AM -0800, Jordan K. Hubbard wrote: > > `make world' is not permitted to change /etc. Especially not > > /etc/master.passwd when installing to DESTDIR=/mnt/root. > > Normally I'd agree, but... Your counter-suggestion? Documentation. Section 2 of the make-world tutorial talks about this (although admittedly it only talks about /etc/group, but I can fix that easily enough). As somone else has pointed out, I think it's legitimate for the first stage of 'installworld' to check for problems like this and bail out, or simply install using UIDs instead of names. I try and make sure people are told they have to upgrade /etc whenever make-world problems crop up on the lists. Hmm, here's an evil idea (and yes, I have no idea how difficult it would be to implement it). Where's the "/etc/" part of the configuration filenames hardcoded? It looks like it's mostly in libc/gen/get*. Could you build a special version of this library that looked in $DESTDIR/etc, and link 'install' with this library while doing the installation. With ELF, you might just be able to set LD_LIBRARY_PATH appropriately, no? Then, for the purposes of the installworld you can use usernames instead of UIDs without install complaining. It doesn't buy you much after that though if people haven't merged in the changes to /etc. Of course, this still lets people shoot their own foot by not passing the same DESTDIR value to the buildworld and installworld targets, but they'll have problems if they do that now anyway (and it's documented as such). N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19304 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:26:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19278 for ; Wed, 2 Dec 1998 15:26:28 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA22137 for freebsd-current@FreeBSD.ORG; Thu, 3 Dec 1998 00:26:05 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 5672215B4; Thu, 3 Dec 1998 00:17:14 +0100 (CET) Date: Thu, 3 Dec 1998 00:17:14 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 still dumps core Message-ID: <19981203001714.A1607@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <4.1.19981201215111.0092f100@206.25.93.69> <19981201231144.A3607@ns1.adsu.bellsouth.com> <3664DB15.398E057B@basspro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <3664DB15.398E057B@basspro.com>; from Troy Kittrell on Wed, Dec 02, 1998 at 12:15:49AM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4856 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Troy Kittrell: > all windows and start over. BTW: I believe this is 4.5b2. Does the beta > have anything to do with it? I'll say "duh" for everyone and save the Oh yes. Don't use 4.5b2, it is crappy as Hell and dumping core all over. It will expire very soon anyway and 4.5 is very stable. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:31:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19868 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:31:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19854 for ; Wed, 2 Dec 1998 15:31:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA09690; Wed, 2 Dec 1998 15:32:26 -0800 (PST) To: Joao Carlos Mendes Luis cc: winter@jurai.net (Matthew N. Dodd), bde@zeta.org.au, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 21:09:12 -0200." <199812022309.VAA26615@roma.coe.ufrj.br> Date: Wed, 02 Dec 1998 15:32:26 -0800 Message-ID: <9687.912641546@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe a suggestion to look at src/etc/master.passwd, etc. could be > enough. Anyway, make world should not be used by novices. :) And is, every single day. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20109 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:32:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20104 for ; Wed, 2 Dec 1998 15:32:37 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA29386; Wed, 2 Dec 1998 18:32:10 -0500 (EST) Date: Wed, 2 Dec 1998 18:32:10 -0500 (EST) From: "Matthew N. Dodd" To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Alfred Perlstein wrote: > On Wed, 2 Dec 1998, Matthew N. Dodd wrote: > > On a related subject, is there any chance you can bring back the NetBSD > > bootstrap stuff and the NETBSD_SYSCALLS stuff? > > > > I've got NetBSD/sparc building FreeBSD-current userland save for some > > problems with the toolchain. > > > > I'm tracking down some problems in libc right now that cause things to > > segfault. > > Are you working on ultrasparc? or the 32bit processors? sparc, not sparc64 though given a similar set of include/machine/* files from the NetBSD/sparc64 port the stuff I'm doing could apply. Regardless, I'm guessing that the sparc64 port will want to be able to run sparc32 binaries no? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20362 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:35:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20353 for ; Wed, 2 Dec 1998 15:35:26 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA29423; Wed, 2 Dec 1998 18:34:58 -0500 (EST) Date: Wed, 2 Dec 1998 18:34:57 -0500 (EST) From: "Matthew N. Dodd" To: John Birrell cc: jkh@zippy.cdrom.com, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <199812022306.KAA10778@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, John Birrell wrote: > Matthew N. Dodd wrote: > > On a related subject, is there any chance you can bring back the NetBSD > > bootstrap stuff and the NETBSD_SYSCALLS stuff? > > If it helps you, yes. I took it out because I knew it would suffer > bit-rot as NetBSD kept changing syscalls. If you document the proc used to keep these bits up to date in respect to NetBSD I'm sure interested parties would submit patches. > > I've got NetBSD/sparc building FreeBSD-current userland save for some > > problems with the toolchain. > > > > I'm tracking down some problems in libc right now that cause things to > > segfault. > > Did you find a problem with using FreeBSD emulation on NetBSD/sparc? > I'm also prepared to do the sparc-specific commits (like the ones I > did for alpha) if that helps get things moving and allows people to > share the work. I don't have a toolchain and I've not attacked the ABI emulator to get it working for FreeBSD/sparc-aout bins, much less ELF32. I have looked at the ABI bits and decided I'd get libc and friends working first. Obviously convincing some NetBSD person to update the ABI emulation for FreeBSD/alpha and sparc would be the way to go. :) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21797 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:46:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21787 for ; Wed, 2 Dec 1998 15:46:19 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id SAA07304; Wed, 2 Dec 1998 18:49:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 2 Dec 1998 18:49:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Matthew N. Dodd" cc: current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Matthew N. Dodd wrote: > > > I've got NetBSD/sparc building FreeBSD-current userland save for some > > > problems with the toolchain. > > > > > > I'm tracking down some problems in libc right now that cause things to > > > segfault. > > > > Are you working on ultrasparc? or the 32bit processors? > > sparc, not sparc64 though given a similar set of include/machine/* files > from the NetBSD/sparc64 port the stuff I'm doing could apply. > > Regardless, I'm guessing that the sparc64 port will want to be able to run > sparc32 binaries no? Yes, I'm just starting a bit of work on this port. I'm not sure I have the skill but I'm going to try very hard, hopefully something will come out of this. -Alfred > > -- > | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | > | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22359 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:50:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22354 for ; Wed, 2 Dec 1998 15:50:27 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA27304; Wed, 2 Dec 1998 15:49:58 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 2 Dec 1998 15:49:57 -0800 (PST) From: Doug White To: andrea cc: freebsd-current@FreeBSD.ORG Subject: Re: ip-masquerading.natd,ip-aliasing .... In-Reply-To: <003701be1df4$ee86f400$4d18b9c2@oma.linet.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, andrea wrote: > I'm looking for a way to configure my intranet using natd. > The problem is that the configuration that i need is a little unsual and i > wonder if is applicable. > > The configuration is as follow: > > On the Same LAN : > > 1 - Web Server (with routable Ip-address) > 2 - Mail Server ( "" "" "" ) > 3 - 1 router connected to the InterNet. > 4 - Many other boxes with not Routeble ip addresses (192.168.. ) > > So i have 2 subnet on the same phisical net. > > What i'm wondering is: > > It's possible to share in the same phisical Lan( eg without gateway > with 2+ Ether Card) between 2 networks? If you want to use natd, you should use it's redirect_port feature instead of mixing the networks. This way you get the filtering feature of natd protecting your mail and web server. The downturn is that you loose flexibility on your web server -- if you add services you'll have to set up redirect rules for it. I don't know how fancy your router is, if it can be taught to natd certain packets or not (I think ipfw can do it, not sure). > I'have tried assigning 2 ip address at the same interface ,and using > this machine as a gateway on the same phisical net. You have to use an alias (with the netmask of that network, not 0xffffffff) on the interface to get the second IP programmed in. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 15:56:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23026 for freebsd-current-outgoing; Wed, 2 Dec 1998 15:56:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22995 for ; Wed, 2 Dec 1998 15:55:56 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-9.pagesz.net [208.213.126.9]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id SAA15544 for ; Wed, 2 Dec 1998 18:56:05 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id SAA01355; Wed, 2 Dec 1998 18:56:33 -0500 (EST) (envelope-from rhh) Message-ID: <19981202185633.A868@pagesz.net> Date: Wed, 2 Dec 1998 18:56:33 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: Bugs/features w/ "ldconfig" (3.0-RELEASE) Mail-Followup-To: current@FreeBSD.ORG References: <19981129102800.A1657@pagesz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981129102800.A1657@pagesz.net>; from Randall Hopper on Sun, Nov 29, 1998 at 10:28:00AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No response, so let me try once more before filing a PR. Two things I notice that are rather strange. Are these bugs? =============================================================================== 1) You can completely re-initialize the LD path for ELF, but not for AOUT. An example to illustrate: # ldconfig -elf / # ldconfig -elf -r /var/run/ld-elf.so.hints: search directories: / # ldconfig -aout / # ldconfig -aout -r /var/run/ld.so.hints: !! ===> search directories: /usr/lib/aout:/ 0:-lalias.2.5 => /usr/lib/aout/libalias.so.2.5 1:-latm.2.0 => /usr/lib/aout/libatm.so.2.0 ... 37:-lstdc++.2.0 => /usr/lib/aout/libstdc++.so.2.0 It seems that ldconfig won't let you remove /usr/lib/aout. Why? =============================================================================== 2) In /etc/rc.conf, we have: $ldconfig_paths & $ldconfig_paths_aout but we also have: /etc/ld.so.conf & /etc/ld-elf.so.conf (as documented in the ldconfig(8) man page) as places to store LD paths. So: a) Which should be used? b) What arguments cause "ldconfig" to read the /etc/ld*.so.conf files? It would make sense to have one place to store this information. It'd also be useful to have simple ldconfig arguments that re-read this information, wherever it is stored (something like "ldconfig -i"). =============================================================================== and a few questions: 3) Why aren't these two directories in the default $ldconfig_paths_aout (AOUT) in /etc/rc.conf? AFAIK, they're all AOUT: /usr/lib/aout /usr/lib/compat 4) Why is this directory in the default $ldconfig_paths (ELF)? It's all AOUT: /usr/lib/compat =============================================================================== I'd appreciate any insights. Should the defs in /etc/rc.conf possibly be changed to: ldconfig_paths="`cat /etc/ld-elf.so.conf`" ldconfig_paths_aout="`cat /etc/ld.so.conf`" Thanks, Randall Hopper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26181 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:11:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26169 for ; Wed, 2 Dec 1998 16:11:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00645; Wed, 2 Dec 1998 16:09:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030009.QAA00645@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: sio breakage In-reply-to: Your message of "Wed, 02 Dec 1998 20:26:51 +1100." <98Dec2.202617est.40351@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 16:09:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > An alternative approach would be to leave IOPL at 0 and use the I/O > Permission bitmap in the TSS. This allows I/O without allowing > CLI/STI. The disadvantage is that either you have a per-process TSS > (which is expensive in memory), or the TSS needs to be re-written on a > context switch (which is expensive in time). BSDI (at least BSDI 1.1) > used this approach - but the bitmap was system-wide, so enabling an > I/O port for any process enabled it for all processes (which isn't > particularly secure). [And at least on 486's, I/O instructions are > much slower is the IOPB is used instead of IOPL - even slower than > accessing the ISA bus :-(]. For what it's worth, we allow a per-process IO permission bitmap; see i386_set_ioperm. > (*) The need to atomically issue multiple I/O instructions could be > seen to be a justification for this. Hmm, good point. I wonder how common this actually is? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:11:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26449 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:11:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26432; Wed, 2 Dec 1998 16:11:33 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-9.pagesz.net [208.213.126.9]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id TAA16740; Wed, 2 Dec 1998 19:11:06 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id TAA02228; Wed, 2 Dec 1998 19:11:35 -0500 (EST) (envelope-from rhh) Message-ID: <19981202191134.B868@pagesz.net> Date: Wed, 2 Dec 1998 19:11:34 -0500 From: Randall Hopper To: Baety Wayne Amn 18CS/SCBD , "'FreeBSD Current'" , "'FreeBSD Questions'" Subject: Re: CAM Mail-Followup-To: Baety Wayne Amn 18CS/SCBD , 'FreeBSD Current' , 'FreeBSD Questions' References: <06A98ECF2D0FD211AA240060B0681211F6CBAF@ms-18sptg1.kadena.af.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <06A98ECF2D0FD211AA240060B0681211F6CBAF@ms-18sptg1.kadena.af.mil>; from Baety Wayne Amn 18CS/SCBD on Mon, Nov 30, 1998 at 08:04:59PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Baety Wayne Amn 18CS/SCBD: |Where's documentation on properly configuring a kernel for use with this new |CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE |controller) and am wondering how to enable it in the kernel. I asked for that a week or so ago, and didn't get any response. So I don't know if there are any such docs. For example, CAM is in 3.0-RELEASE, and there's really nothing on it in the handbook or FAQ. There is cam(3), pass(4), and xpt(4), but that isn't really a how-to. My limited understanding is that if you're running a CAM-enabled kernel, CAM is just "there". My original pre-CAM SCSI-related kernel lines flew with a CAM kernel with no change except "sd" disks are now "da" disks: controller ncr0 controller scbus0 at ncr0 # Single bus device disk cd0 at scbus0 target 0 unit 0 # SCSI CD-ROM device sa0 at scbus0 target 4 unit 0 # SCSI tapes disk da0 at scbus0 target 5 unit 0 # da0 = ZIP Drive There's this new concept of a pass-through device (/dev/pass*) which I'm not too sure about; these are doled out to detected SCSI devices. And there's a TLI device (/dev/xpt*) which I think is allocated 1 per bus. In addition to the above lines, I also added a wired-down pass0 so I could configure SANE to find my scanner consistently. I also wired down my CDRW, though I don't know if that's necessary or not: device pass0 at scbus0 target 6 unit 0 # CAM passthrough = Scanner device pass1 at scbus0 target 0 unit 0 # RICOH MP6200S CDRW SCSI bus rescans and lists are much simpler with CAM (from a user's perpective at least): camcontrol rescan 0 camcontrol devlist That's about all I know at this point. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:14:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26734 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:14:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26711 for ; Wed, 2 Dec 1998 16:14:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00794; Wed, 2 Dec 1998 16:12:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030012.QAA00794@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: sio breakage In-reply-to: Your message of "Wed, 02 Dec 1998 20:46:45 +1100." <98Dec2.204608est.40351@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 16:12:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If it does, this is clearly indicative of a > >need to move some of the server code into the kernel, > You mean, like GGI :-). No. Apart from the fact that GGI suffers from farcial mismanagement and a proven inability to design or ship code, as little as practical should move into the kernel. I don't think that this would be consistent with performance requirements however. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:31:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28106 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:31:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28085; Wed, 2 Dec 1998 16:31:02 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA28810; Wed, 2 Dec 1998 17:30:35 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812030030.RAA28810@panzer.plutotech.com> Subject: Re: CAM In-Reply-To: <19981202191134.B868@pagesz.net> from Randall Hopper at "Dec 2, 98 07:11:34 pm" To: aa8vb@pagesz.net (Randall Hopper) Date: Wed, 2 Dec 1998 17:30:35 -0700 (MST) Cc: Wayne.Baety@kadena.af.mil, freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper wrote... > Baety Wayne Amn 18CS/SCBD: > |Where's documentation on properly configuring a kernel for use with this new > |CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE > |controller) and am wondering how to enable it in the kernel. > > I asked for that a week or so ago, and didn't get any response. So I don't > know if there are any such docs. For example, CAM is in 3.0-RELEASE, and > there's really nothing on it in the handbook or FAQ. There is cam(3), > pass(4), and xpt(4), but that isn't really a how-to. I sent a response to the original poster on the SCSI list. There are quite a few CAM man pages, actually. Some other interesting ones: scsi(4) cam_cdbparse(3) camcontrol(8) > My limited understanding is that if you're running a CAM-enabled kernel, > CAM is just "there". My original pre-CAM SCSI-related kernel lines flew > with a CAM kernel with no change except "sd" disks are now "da" disks: > > controller ncr0 > controller scbus0 at ncr0 # Single bus device > disk cd0 at scbus0 target 0 unit 0 # SCSI CD-ROM > device sa0 at scbus0 target 4 unit 0 # SCSI tapes > disk da0 at scbus0 target 5 unit 0 # da0 = ZIP Drive And 'st' is now 'sa'. > There's this new concept of a pass-through device (/dev/pass*) which I'm > not too sure about; these are doled out to detected SCSI devices. And > there's a TLI device (/dev/xpt*) which I think is allocated 1 per bus. TLI? What's that? There's one transport layer device per transport layer, not per bus. Right now, there's only one transport layer. Depending on how (or if) ATAPI support is integrated into CAM, there may be another transport layer instance eventually. > In addition to the above lines, I also added a wired-down pass0 so I > could configure SANE to find my scanner consistently. I also wired down my > CDRW, though I don't know if that's necessary or not: > > device pass0 at scbus0 target 6 unit 0 # CAM passthrough = Scanner > device pass1 at scbus0 target 0 unit 0 # RICOH MP6200S CDRW You shouldn't need to wire down your CDRW at least. I'm not sure exactly how Corey did the SANE port, so that may be necessary. If you configure the pt driver in your kernel, you should be able to specify the passthrough driver that way as well. You should be able to access the CDRW via cdrecord by specifying its bus, target and lun. > SCSI bus rescans and lists are much simpler with CAM (from a user's > perpective at least): > > camcontrol rescan 0 > camcontrol devlist > > That's about all I know at this point. Well, for the average user, most of the documentation available now is probably sufficient. There are docs describing: - all CAM userland utilities (just camcontrol(8) right now) - most CAM userland programming interfaces (except CCB types, see below) - how to configure your kernel for CAM (scsi(4) and LINT) - how to configure debugging printfs (camcontrol(8) and scsi(4)) - basic man pages on all the peripheral drivers - basic man pages for most of the controller drivers The main pieces of documentation that are missing now are: - all of the CCB types, what they do, etc. - the internal structure of the transport layer - "HBA" driver to transport layer interface - peripheral driver to transport layer interface Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29079 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:37:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.scient.com (set.Scient.COM [208.29.209.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA29071 for ; Wed, 2 Dec 1998 16:37:33 -0800 (PST) (envelope-from enkhyl@scient.com) Received: by set.scient.com; (5.65v4.0/1.3/10May95) id AA08839; Wed, 2 Dec 1998 16:36:55 -0800 Received: from somewhere by smtpxd Date: Wed, 2 Dec 1998 16:36:44 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: cnielsen@pobox.com To: "Matthew N. Dodd" Cc: John Birrell , "Jordan K. Hubbard" , dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Matthew N. Dodd wrote: > I've got NetBSD/sparc building FreeBSD-current userland save for some > problems with the toolchain. sparc32, sparc64 or both? -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:39:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29397 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:39:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29372 for ; Wed, 2 Dec 1998 16:39:37 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id LAA18351; Thu, 3 Dec 1998 11:39:23 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma018347; Thu, 3 Dec 98 11:39:10 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id LAA12468 for ; Thu, 3 Dec 1998 11:39:10 +1100 From: "John Saunders" To: "FreeBSD current" Subject: Booting 3.0-RELEASE in a non-standard setup Date: Thu, 3 Dec 1998 11:39:10 +1100 Message-ID: <000d01be1e55$577177a0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having some problems getting 3.0-CURRENT to boot. My setp...2 EIDE drives, wd0 and wd2. wd0 is Windows only. wd2 has 4 partitions, 1 is FreeBSD 2.2.8, 2 was empty, 3 and 4 are linux and linux swap. What I did...Booted from the CD and selected slice 2 (which was empty) to install to. Using the disk label editor I created / swap /usr /var in slice 2. I selected to not touch the MBR when installing boot blocks. The installation process went OK and I was able to see the files being installed in the right place (I can boot 2.2.8 and mount the partitions on wd2s2). What happens...Using the FreeBSD boot manager I press F5 to switch to drive wd2, then F2 to boot the wd2s2 slice. However it seems that the boot block in wd2s2 decided to load the 2.2.8 kernel from wd2s1 and I end up booting into 2.2.8 OK. So I decide to try the new boot blocks, from 2.2.8 I mount the slice 2 partitions and using the 2.2.8 disklabel I go... disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 wd2s2 ...which appears to update the right boot blocks. So now I use the F5 F1 proceedure and I get a different boot manager with a ? key for command list (BTW help doesn't work because the boot.help file got installed in the wrong place). However if I let the auto boot timeout go the 3.0-RELEASE kernel starts but dies with "unable to mount root wd1a" message. I tried typing "boot kernel" from the boot manager with the same panic. Listing the boot variables show 2 interesting variables (name escapes me now) and both were set to disk2s2a (I think the a was there). Question...After all that, does anybody have a 2xFreeBSD on 1xDisk config working? If so then how? I could probably do some hackery with the partition table each time I want to boot 3.0 but it _should_ work without that. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:49:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00199 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:49:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00180; Wed, 2 Dec 1998 16:49:43 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-9.pagesz.net [208.213.126.9]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id TAA19894; Wed, 2 Dec 1998 19:49:41 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id TAA04625; Wed, 2 Dec 1998 19:50:10 -0500 (EST) (envelope-from rhh) Message-ID: <19981202195010.A4218@pagesz.net> Date: Wed, 2 Dec 1998 19:50:10 -0500 From: Randall Hopper To: "Kenneth D. Merry" Cc: Wayne.Baety@kadena.af.mil, freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: CAM Mail-Followup-To: "Kenneth D. Merry" , Wayne.Baety@kadena.af.mil, freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG References: <19981202191134.B868@pagesz.net> <199812030030.RAA28810@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812030030.RAA28810@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Dec 02, 1998 at 05:30:35PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |> There's this new concept of a pass-through device (/dev/pass*) which I'm |> not too sure about; these are doled out to detected SCSI devices. And |> there's a TLI device (/dev/xpt*) which I think is allocated 1 per bus. | |TLI? What's that? xpt(4) says "xpt - CAM transport layer interface" - TLI! Like TCP TLI, but heavier on the CAM side :-). Thanks for the other info, and for the CAM work. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:52:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00626 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:52:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00618 for ; Wed, 2 Dec 1998 16:52:48 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA03177; Thu, 3 Dec 1998 11:52:22 +1100 (EST) Message-ID: <19981203115222.A3051@rf900.physics.usyd.edu.au> Date: Thu, 3 Dec 1998 11:52:22 +1100 From: David Dawes To: Peter Jeremy , mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: sio breakage References: <98Dec2.204608est.40351@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Dec2.204608est.40351@border.alcanet.com.au>; from Peter Jeremy on Wed, Dec 02, 1998 at 08:46:45PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 08:46:45PM +1100, Peter Jeremy wrote: >>> I don't believe this is reasonable. We should provide some safe way >>> for an application program to execute code with interrupts disabled. >>> Amongst other applications, XFree86 needs this. >> >>It shouldn't (ideally). >I agree. And whilst I haven't checked why, XFree86 does appear to >disable interrupts at times. I agree too, but it does disable interrupts when probing for fixed pixel clocks (which is mostly only done for obsolete hardware), and sometimes when programming PLLs. If someone has a better way of handling time critical thing like this (preferably in a portable way), please let me know. I'd love to dump our disable interrupt code. >> If it does, this is clearly indicative of a >>need to move some of the server code into the kernel, >You mean, like GGI :-). There are some tasks that are much better suited to the kernel, and perhaps a better balance could be found by just doing those few selected things in the kernel and leaving the rest of it in user space. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 16:55:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00964 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:55:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00959 for ; Wed, 2 Dec 1998 16:55:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA10155; Wed, 2 Dec 1998 16:57:25 -0800 (PST) To: "John Saunders" cc: "FreeBSD current" Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-reply-to: Your message of "Thu, 03 Dec 1998 11:39:10 +1100." <000d01be1e55$577177a0$6cb611cb@saruman.scitec.com.au> Date: Wed, 02 Dec 1998 16:57:24 -0800 Message-ID: <10151.912646644@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My setp...2 EIDE drives, wd0 and wd2. wd0 is Windows only. wd2 > has 4 partitions, 1 is FreeBSD 2.2.8, 2 was empty, 3 and 4 are > linux and linux swap. What happened to wd1? :-) > What I did...Booted from the CD and selected slice 2 (which > was empty) to install to. Using the disk label editor I created Which won't work. The FreeBSD boot loader, at least last I checked, is too stupid to know that there might be more than one FreeBSD slice on the disk and it just stops at the first one it finds. If you want to run different versions of FreeBSD on the same box, they at least need to reside on physically different drives. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02927 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:09:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02916 for ; Wed, 2 Dec 1998 17:09:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01213; Wed, 2 Dec 1998 17:07:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030107.RAA01213@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Dawes cc: Peter Jeremy , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: sio breakage In-reply-to: Your message of "Thu, 03 Dec 1998 11:52:22 +1100." <19981203115222.A3051@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 17:07:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Dec 02, 1998 at 08:46:45PM +1100, Peter Jeremy wrote: > > >>> I don't believe this is reasonable. We should provide some safe way > >>> for an application program to execute code with interrupts disabled. > >>> Amongst other applications, XFree86 needs this. > >> > >>It shouldn't (ideally). > >I agree. And whilst I haven't checked why, XFree86 does appear to > >disable interrupts at times. > > I agree too, but it does disable interrupts when probing for fixed pixel > clocks (which is mostly only done for obsolete hardware), and sometimes > when programming PLLs. If someone has a better way of handling time > critical thing like this (preferably in a portable way), please let me > know. I'd love to dump our disable interrupt code. I get the impression from this though that you only do interrupt disables when probing or changing video modes, is that correct? The entire train of angst here is descended from percieved problems in interrupt delivery during normal operation; if you're only disabling interrupts during startup then this prettymuch exonerates the X server. > >> If it does, this is clearly indicative of a > >>need to move some of the server code into the kernel, > >You mean, like GGI :-). > > There are some tasks that are much better suited to the kernel, and > perhaps a better balance could be found by just doing those few selected > things in the kernel and leaving the rest of it in user space. Quite possibly; I wasn't sure that it would help performance, and it would *certainly* make your lives harder. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03004 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:09:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02992 for ; Wed, 2 Dec 1998 17:09:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01092; Wed, 2 Dec 1998 16:55:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030055.QAA01092@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: "FreeBSD current" Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-reply-to: Your message of "Thu, 03 Dec 1998 11:39:10 +1100." <000d01be1e55$577177a0$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 16:55:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What happens...Using the FreeBSD boot manager I press F5 to > switch to drive wd2, then F2 to boot the wd2s2 slice. However > it seems that the boot block in wd2s2 decided to load the 2.2.8 > kernel from wd2s1 and I end up booting into 2.2.8 OK. This is normal for the "old" bootblocks; they can only boot from the first FreeBSD slice on the disk. > So I decide > to try the new boot blocks, from 2.2.8 I mount the slice 2 > partitions and using the 2.2.8 disklabel I go... > disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 wd2s2 > ...which appears to update the right boot blocks. So now I use > the F5 F1 proceedure and I get a different boot manager with a > ? key for command list (BTW help doesn't work because the > boot.help file got installed in the wrong place). It actually uses a different help file format, and the help file isn't installed normally (because it wasn't ready at the time). > However if I > let the auto boot timeout go the 3.0-RELEASE kernel starts but > dies with "unable to mount root wd1a" message. That's correct; it's because the BIOS unit number is 0x81, but the disk is actually wd2. There are a couple of ways you can sneak around this; one is to rebuild your kernel with: controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd1 at wdc1 drive 0 the other is more complex, in that it involves you updating /boot/loader and playing with the $rootdev variable (it's broken in the version that you're using). > Question...After all that, does anybody have a 2xFreeBSD on > 1xDisk config working? If so then how? I could probably do > some hackery with the partition table each time I want to boot > 3.0 but it _should_ work without that. The new loader makes this feasible, but it would certainly benefit from someone in your position poking at it a bit more to help iron out any remaining bugs. If you're happy updating to a new /boot/loader, try 'set rootdev=disk2s2a:' before 'boot kernel' and see if it does a better job. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03594 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:13:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03531 for ; Wed, 2 Dec 1998 17:13:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01111; Wed, 2 Dec 1998 16:58:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030058.QAA01111@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Watson cc: Mike Smith , Andrzej Bialecki , Pascal Hofstee , Shawn Ramsey , oZZ!!! , current@FreeBSD.ORG Subject: Re: StarOffice-5.0... In-reply-to: Your message of "Wed, 02 Dec 1998 12:58:44 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 16:58:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 29 Nov 1998, Mike Smith wrote: > > > > Yes, I've got the diffs against relatively fresh current. BTW, I asked > > > this question on -emulation, but got back a profound silence... Can we/ > > > should we incorporate this patch, and hide it under a kernel option, say > > > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux > > > emulation... > > > > A couple of things: > > > > - If it's part of our emulation support, it should probably be the > > default (cringe). > > - Your patch doesn't preserve the remainder of the commandline > > arguments. Feel like fixing this and resubmitting it? > > I suppose there is no easy way for the procfs code to determine if the > relevant calls are coming from a linux emulated process or not? I don't think there's a uniquifier for the ABI mode in the proc structure, no. > If there > were, then the command line stuff could be made only to appear for Linux > processes. I'm guessing, however, that only the creds and arguments to > the vfs call make it that far down, and use of curproc seems > inappropriate? There's probably a pointer to the current process in the arguments. > Or, if loadable kernel modules (or whatever they are called today) could > add hook functions to the procfs module via some symbol or another, then > new items could be added based on context. That however, seems a little > too busy, given that stackable file systems don't work. :) Yeah. I was playing with a generic framework for componentised VFS', but I haven't had time to do much with it lately, and the proper semantics for things like locking were giving me some confusion. The real answer is a linux-procfs, which mounts on /compat/linux/procfs. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:13:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03633 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:13:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03608 for ; Wed, 2 Dec 1998 17:13:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA09293; Wed, 2 Dec 1998 15:48:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812022348.PAA09293@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tom@tomqnx.com (Tom Torrance at home) cc: current@FreeBSD.ORG Subject: Re: USERCONFIG_BOOT In-reply-to: Your message of "Wed, 02 Dec 1998 08:04:20 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 15:48:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Is there some reason why this option has not > > > been incorporated into the current source tree? > > > > It's obsolete, and was removed. See the commit logs for > > sys/i386/i386/userconfig.c and the HEADS UP that I posted to the > > -current list (which as a -current user you *must* be reading). > > > I don't think it's obsolete yet. I have to re-enter the pnp commands > after installing a new kernel. The effects of the last such command > of the series are otherwise lost for my AWE soundcard. It is indeed obsolete. Please read the documentation I referenced in order to see how the problem is now addressed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03751 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:14:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03744 for ; Wed, 2 Dec 1998 17:14:45 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA28540; Wed, 2 Dec 1998 18:14:10 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA10483; Wed, 2 Dec 1998 18:14:09 -0700 Date: Wed, 2 Dec 1998 18:14:09 -0700 Message-Id: <199812030114.SAA10483@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: David Dawes , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sio breakage In-Reply-To: <199812030107.RAA01213@dingo.cdrom.com> References: <19981203115222.A3051@rf900.physics.usyd.edu.au> <199812030107.RAA01213@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >I agree. And whilst I haven't checked why, XFree86 does appear to > > >disable interrupts at times. > > > > I agree too, but it does disable interrupts when probing for fixed pixel > > clocks (which is mostly only done for obsolete hardware), and sometimes > > when programming PLLs. If someone has a better way of handling time > > critical thing like this (preferably in a portable way), please let me > > know. I'd love to dump our disable interrupt code. > > I get the impression from this though that you only do interrupt > disables when probing or changing video modes, is that correct? I get that impression as well. > The entire train of angst here is descended from percieved problems in > interrupt delivery during normal operation; if you're only disabling > interrupts during startup then this prettymuch exonerates the X server. Except that I can say with assurance that at least older versions of the XFree86 server *seem* to be disabling interrupts for long periods, or at least calling code that disables interrupts. When I switched to the XIG (XInside at the time) server, all of my serial overflows went away. That was the *only* configuration difference. To be sure, I even re-configured the XFree86 server and the problem re-occurred. Swapped it back and it went away. Note, this was about a year ago, maybe more so it may have changed. (The box in question has a S3 928 card in it..) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:15:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03994 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:15:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03986 for ; Wed, 2 Dec 1998 17:15:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA08915; Wed, 2 Dec 1998 14:51:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812022251.OAA08915@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma cc: Mike Smith , van.woerkom@netcologne.de, jkh@zippy.cdrom.com, forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Wed, 02 Dec 1998 09:47:59 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 14:51:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > What are the (rough) plans for this mechanism? > > > > Convert the entire kernel into an aggregation of KLD modules. Stick > > them together in interesting and versatile ways (eg. at build time to > > create a monolithic kernel, or at runtime to load/unload drivers, etc.). > > ... unload probe/init code when it is no longer needed. This is actually almost totally farcial; the only modules for which unloading probe/init code makes any sense are ISA drivers, and even then only ISA drivers that don't support PCCARDs. In every other case the probe and init code need to be kept around in order to probe/init new arrivals (PCCARD for ISA, CardBus and Hot-Plug PCI for PCI, new USB peripherals, etc.). In most cases, there won't be any probe code anyhow, as it's redundant for anything other than non-PnP ISA cards. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05783 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:34:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05775 for ; Wed, 2 Dec 1998 17:34:56 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id TAA01485; Wed, 2 Dec 1998 19:34:30 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Wed, 2 Dec 1998 19:34:29 -0600 (CST) From: Richard Wackerbarth To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812022251.OAA08915@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Mike Smith wrote: > > > > What are the (rough) plans for this mechanism? > > > > > > Convert the entire kernel into an aggregation of KLD modules. Stick > > > them together in interesting and versatile ways (eg. at build time to > > > create a monolithic kernel, or at runtime to load/unload drivers, etc.). > > > > ... unload probe/init code when it is no longer needed. > > This is actually almost totally farcial; the only modules for which > unloading probe/init code makes any sense are ISA drivers, and even > then only ISA drivers that don't support PCCARDs. In every other case > the probe and init code need to be kept around Cannot we unload all of the device recognition code once it has done its job and reload it each time the PCCARD finds a new arrival? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06781 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:44:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06776 for ; Wed, 2 Dec 1998 17:44:20 -0800 (PST) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id BAA25942 for ; Thu, 3 Dec 1998 01:43:58 GMT Date: Thu, 3 Dec 1998 01:43:56 GMT Message-Id: <22134.199812030143@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: ELF documentation To: freebsd-current@FreeBSD.ORG Organization: just say no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where can I find documentation of the new ELF executable file format? What I want is the ELF equivalent of "man 5 a.out", but it doesn't seem to exist. I'm trying to convert programs that load in .o files and write themselves out as new executables (lisp and prolog systems). -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07209 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:47:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07200 for ; Wed, 2 Dec 1998 17:47:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02736; Wed, 2 Dec 1998 17:45:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030145.RAA02736@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Wackerbarth cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Wed, 02 Dec 1998 19:34:29 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 17:45:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 2 Dec 1998, Mike Smith wrote: > > > > > What are the (rough) plans for this mechanism? > > > > > > > > Convert the entire kernel into an aggregation of KLD modules. Stick > > > > them together in interesting and versatile ways (eg. at build time to > > > > create a monolithic kernel, or at runtime to load/unload drivers, etc.). > > > > > > ... unload probe/init code when it is no longer needed. > > > > This is actually almost totally farcial; the only modules for which > > unloading probe/init code makes any sense are ISA drivers, and even > > then only ISA drivers that don't support PCCARDs. In every other case > > the probe and init code need to be kept around > > Cannot we unload all of the device recognition code once it has done its > job and reload it each time the PCCARD finds a new arrival? What "device recognition code"? If we keep the current model, it's all in a user-space application. If we were to move the CIS ID : driver/rules match code into the kernel, it would be so small and trivial that the effort involved in loading/unloading it would be disproportionate to the space regained (maybe 1 page). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:47:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07387 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:47:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07378 for ; Wed, 2 Dec 1998 17:47:53 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id MAA11481; Thu, 3 Dec 1998 12:55:32 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812030155.MAA11481@cimlogic.com.au> Subject: Re: Uh oh... In-Reply-To: from "Matthew N. Dodd" at "Dec 2, 98 06:34:57 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 3 Dec 1998 12:55:32 +1100 (EST) Cc: jb@cimlogic.com.au, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew N. Dodd wrote: > I don't have a toolchain and I've not attacked the ABI emulator to get it > working for FreeBSD/sparc-aout bins, much less ELF32. I have looked at > the ABI bits and decided I'd get libc and friends working first. > > Obviously convincing some NetBSD person to update the ABI emulation for > FreeBSD/alpha and sparc would be the way to go. :) Chuckle. I know just the person to ask. And I'd love to see his reaction. 8-) Being a coward, I can say this here because I think he only subscribes to hackers, alpha, sparc and cvs-sys lists (I checked!). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07588 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:49:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07583 for ; Wed, 2 Dec 1998 17:49:56 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA80701; Wed, 2 Dec 1998 20:47:52 -0500 (EST) Date: Wed, 2 Dec 1998 20:47:52 -0500 (EST) From: Chuck Robey To: Richard Tobin cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF documentation In-Reply-To: <22134.199812030143@doyle.cogsci.ed.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Richard Tobin wrote: > Where can I find documentation of the new ELF executable file format? > What I want is the ELF equivalent of "man 5 a.out", but it doesn't > seem to exist. That works fine here. Maybe your manpath.config is all messed up? > > I'm trying to convert programs that load in .o files and write themselves > out as new executables (lisp and prolog systems). > > -- Richard > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 17:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08618 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:59:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (42-sweet.camalott.com [208.239.153.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08597 for ; Wed, 2 Dec 1998 17:58:59 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id TAA00843; Wed, 2 Dec 1998 19:57:20 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: "Jordan K. Hubbard" , Marius Bendiksen , Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <199811251717.JAA00911@dingo.cdrom.com> From: Joel Ray Holveck Date: 02 Dec 1998 19:57:20 -0600 In-Reply-To: Mike Smith's message of "Wed, 25 Nov 1998 09:17:08 -0800" Message-ID: <86g1ay6l8f.fsf@detlev.UUCP> Lines: 165 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry it took me so long to reply; I've been out of town. >>> Ummm. Rebooting into DOS is *not* the same problem as booting into >>> FreeBSD, though you seem to be under the mistaken impression that it >>> is. If you don't believe me, just try constructing a PIF file for >>> fbsdboot.exe and launch the procedure from your desktop. You will not >>> shut down gracefully to DOS and be presented with a freebsd login >>> prompt a few minutes later, as you would hope and expect. The kinds >>> of things you need to do in order to properly shut down Windows and >>> launch the FreeBSD kernel are simply different. >> Jordan, we've been over this before. Did you ever actually *try* what >> the rest of the list said? > Yes. It doesn't work. Have YOU? Yes, I did, and had good results. However, it appears I owe you an apology. The method I used apparently did not get posted to -current or -hackers; I didn't notice anything on those lists to describe the correct .pif file to use. Mike said: > Yes, we have been over this before. Would you care to explain how you > plan to reinstate the vectors that the DOS7 kernel replaces so that > vm86 BIOS calls from the FreeBSD kernel will work? > Please understand that there are some really fundamental issues which > absolutely preclude starting FreeBSD once DOS has been started. We may have a different definition of "DOS7 kernel". I typically use that phrase to refer to IO.SYS alone. The vectors seem to be modified by HIMEM.SYS instead. By default, IO.SYS will load HIMEM.SYS and prevent the kernel from loading. However, the line "DOS=NOAUTO" in the config.sys will cause IO.SYS to skip that step. I have had success loading FreeBSD by using that line in the PIF's specified CONFIG.SYS myself. I just now went through the procedure from scratch to make sure it's still valid. The following description has been simplified, to-wit: the FBSDBOOT.ING code in the PIF's AUTOEXEC.BAT was added after the initial trial. The results should be the same. * Materials Computer: i486, 32MB RAM, AHA-1542C. Windows on da0s1, FreeBSD root on da1s1a, other BSD partitions on da1s1 and da2s1. FreeBSD: cvsup'd approx. 23 Nov 1998. Windows: Windows 95 4.00.950. IO.SYS dated 11 Jul 1995, size 223148, MD5 checksum 5a18167042bdf9823ef7f70ca7af805b. FBSDBOOT.EXE: Recently downloaded from ftp.freebsd.org; size 22487, MD5 checksum 5b8f1d7d1e806bc8b1ae2cf12a4ee5e0. kernel: My normal config file, with the "config kernel" line updated to reflect my current root drive. Sources cvsup'd as -current approx. 23 Nov 1998. * Methods The only box I have with both FreeBSD and Win95 boots BSD from da1, which FBSDBOOT does not examine. (This is discussed more later.) This means I had to create a kernel that specifies the correct root, using the line: config kernel root on da1s1a in my kernel config file and recompiling. The cvsup I used was from late November. The resulting kernel was placed on my Win95 drive, as "C:\KERNEL". I then created a shortcut (using Windows 95's New:Shortcut command) on the desktop, and specified "C:\FBSDBOOT.EXE -r -D" as the command line. I edited the file (Properties), and under the "Program:Advanced" section, specified to run in MS-DOS mode. I then specified, in the PIF, the following CONFIG.SYS: DOS=SINGLE,NOAUTO and AUTOEXEC.BAT: SET CONFIG=Standard if not exist c:\fbsdboot.ing goto goahead del c:\fbsdboot.ing c:\windows\win.com /wx :goahead copy \autoexec.bat \fbsdboot.ing (The SET CONFIG was an error on my part; it is not necessary.) The AUTOEXEC.BAT was necessary because Windows does not have the opportunity to restore its CONFIG.SYS and AUTOEXEC.BAT without being explicitly told to do so. The "WIN /WX" causes Windows to return those files to their previous contents, prepare to update the PIF with the files' current contents if necessary (the actual update is done later), and reboot. The resultant PIF file is attached. I then tested the PIF file. FreeBSD loaded and started X as normal. Little operational testing was done at this time. The sysctl variable "kern.bootfile" was "c:\kernel". This is discussed later. I then performed a normal shutdown of FreeBSD. The system rebooted into DOS 7, and immediately rebooted again, this time into Windows 95. (This was the FBSDBOOT.ING code having its effect.) Windows 95 appeared to be operating normally (or, at least, as normal as it ever does). At this point, I noticed my normal 2k AUTOEXEC.BAT had by that point been replaced with a near-trival one. However, strong evidence suggests that this had taken place prior to my experiment. * Conclusions FBSDBOOT can be made to work with Windows 95 (original release) with our current kernel. The key factor (DOS=NOAUTO) was not, to my knowledge, described in the previous discussion on -current, so sufficient experimentation has not been performed. The most likely key factor is the version of Windows 95. In particular, more experimentation with Win95 OSR2 and Win98 is warranted. Another possible issue to study is the use of -r -D. FBSDBOOT only searches drive 0x80. Because the experiment's platform does not have a FreeBSD partition on that drive, the use of -r -D coupled with a kernel on the DOS was necessary. This caused an illegal value in kern.bootfile. This may be fixable by hacking /etc/rc. Further experimentation regarding the use of -r -D is also warranted. Modification to FBSDBOOT to allow booting off of other devices would also be useful. I would be very interested in hearing other people's results. Happy hacking, joelh -----cut here----- begin 777 freebsd.pif M`'A&0E-$0D]/5"`@("`@("`@("`@("`@("`@("`@(""``@``0SI<1D)31$)/ M3U0N15A%```````````````````````````````````````````````````` M````````````$`!#.EP````````````````````````````````````````` M````````````````````````````````````````+7(@+40````````````` M```````````````````````````````````````````````````````````` M```````!`/\94```!P`````````````````````````````````````````` M```````````````````````````````````````````````````````````` M```````````````````````````````````````````````````````````` M````````````34E#4D]33T94(%!)1D58`(&ES="!C.EQF8G-D8F]O="YI;F<@ M9V]T;R!G;V%H96%D#0ID96P@8SI<9F)S9&)O;W0N:6YG#0IC.EQW:6YD;W=S M7'=I;BYC;VT@+W=X#0HZ9V]A:&5A9`T*8V]P>2!<875T;V5X96,N8F%T(%QF -8G-D8F]O="YI;F<-"@HZ ` end -----cut here----- -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09031 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:02:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09024 for ; Wed, 2 Dec 1998 18:02:37 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id SAA57786; Wed, 2 Dec 1998 18:53:46 -0700 (MST) Date: Wed, 2 Dec 1998 18:53:46 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812030153.SAA57786@narnia.plutotech.com> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: KLD - what's the idea? X-Newsgroups: pluto.freebsd.current In-Reply-To: <199812022251.OAA08915@dingo.cdrom.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812022251.OAA08915@dingo.cdrom.com> you wrote: >> > > What are the (rough) plans for this mechanism? >> > >> > Convert the entire kernel into an aggregation of KLD modules. Stick >> > them together in interesting and versatile ways (eg. at build time to >> > create a monolithic kernel, or at runtime to load/unload drivers, etc.). >> >> ... unload probe/init code when it is no longer needed. > > This is actually almost totally farcial; the only modules for which > unloading probe/init code makes any sense are ISA drivers, and even > then only ISA drivers that don't support PCCARDs. The probe and attach code for certain drivers is quite complex. The Adaptec and NCR drivers do some amount of run-time firmware patching. Several drivers carry along large firmware images that serve no purpose once the image is loaded into the device. These situations would certainly benefit from the ability to either selectively swap out portions of a module (ala AIX) or to unload unused segments and reload them on the fly during further probe/attach requests (ala Linux). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09843 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:09:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09833 for ; Wed, 2 Dec 1998 18:09:07 -0800 (PST) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54] helo=demios.scl.ameslab.gov) by mailhub.scl.ameslab.gov with smtp (Exim 1.90 #1) id 0zlOCH-0001Ck-00; Wed, 2 Dec 1998 20:08:49 -0600 Date: Wed, 2 Dec 1998 20:08:49 -0600 (CST) From: Guy Helmer To: lcremean@tidalwave.net cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: CAM integration imminent. In-Reply-To: <19980915190534.A9468@st-lcremean.tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Sep 1998, Lee Cremeans wrote: > On Tue, Sep 15, 1998 at 05:11:37PM -0400, rvb@sicily.odyssey.cs.cmu.edu wrote: > > ... > > aic needs to be commented out. Doing this yields: > > ... > I understand a CAMified version of aic is forthcoming, but for now, it'll > have to go since I don't think any of the old SCSI layer exists anymore.. Is anyone working on the CAMified aic? I'm hacking on it, but I'm not sure I'm going to be successful... Guy Helmer, Graduate Student, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10253 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:11:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10244 for ; Wed, 2 Dec 1998 18:11:20 -0800 (PST) (envelope-from ggm@sleet.dstc.edu.au) Received: from sleet.dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA31307 for ; Thu, 3 Dec 1998 12:11:03 +1000 (EST) Received: (from ggm@localhost) by sleet.dstc.edu.au (8.8.5/8.8.4) id MAA13640 for current@freebsd.org; Thu, 3 Dec 1998 12:11:00 +1000 (EST) Date: Thu, 3 Dec 1998 12:11:00 +1000 (EST) From: George Michaelson Message-Id: <199812030211.MAA13640@sleet.dstc.edu.au> To: current@freebsd.org Subject: can somebody post a succint *why* on Linux emul in ELFland fails? Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG I've lost the plot. If somebody can post brief bulletpoints on the ELFland issues which make Linux and StarrOffice 5.0 a nogo just now I'd be very appreciative. I'm not after complaining, just want to understand state-of-play. It comes down to /proc and kernel threading ? is there more ? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10559 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:15:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10551 for ; Wed, 2 Dec 1998 18:15:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03115; Wed, 2 Dec 1998 18:13:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030213.SAA03115@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Wed, 02 Dec 1998 18:53:46 MST." <199812030153.SAA57786@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 18:13:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > Convert the entire kernel into an aggregation of KLD modules. Stick > >> > them together in interesting and versatile ways (eg. at build time to > >> > create a monolithic kernel, or at runtime to load/unload drivers, etc.). > >> > >> ... unload probe/init code when it is no longer needed. > > > > This is actually almost totally farcial; the only modules for which > > unloading probe/init code makes any sense are ISA drivers, and even > > then only ISA drivers that don't support PCCARDs. > > The probe and attach code for certain drivers is quite complex. The > Adaptec and NCR drivers do some amount of run-time firmware patching. > Several drivers carry along large firmware images that serve no purpose > once the image is loaded into the device. These situations would > certainly benefit from the ability to either selectively swap out > portions of a module (ala AIX) Hmm. It's been mentioned before that it would be relatively straightforward to put this sort of code into a separate section that could be marked pageable. I'd be concerned however that this would be incompatible with our current use of a 4M page for the kernel space - you'd have to somehow arrange to have these portions of the module located physically disjoint from the remainder of the module if I understand this correctly. > or to unload unused segments and > reload them on the fly during further probe/attach requests (ala Linux). It would certainly be feasible to arrange for the firmware images to be loaded from separate files, should that be an acceptable alternative. I'm open to suggestions on how to make this economical and robust... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:16:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10665 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:16:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10657 for ; Wed, 2 Dec 1998 18:16:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03135 for ; Wed, 2 Dec 1998 18:14:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030214.SAA03135@dingo.cdrom.com> Date: Wed, 02 Dec 1998 18:14:48 -0800 From: Mike Smith Subject: Re: can somebody post a succint *why* on Linux emul in ELFland fails? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: George Michaelson cc: emulation@freebsd.org Subject: Re: can somebody post a succint *why* on Linux emul in ELFland fails? In-reply-to: Your message of "Thu, 03 Dec 1998 12:11:00 +1000." <199812030211.MAA13640@sleet.dstc.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 18:14:48 -0800 From: Mike Smith *please* post emulation-related questions to the freebsd-emulation list. > I've lost the plot. If somebody can post brief bulletpoints on the ELFland > issues which make Linux and StarrOffice 5.0 a nogo just now I'd be very > appreciative. > > I'm not after complaining, just want to understand state-of-play. > > It comes down to /proc and kernel threading ? is there more ? These are the currently understood problems, yes. - -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10711 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:16:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10695 for ; Wed, 2 Dec 1998 18:16:49 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id NAA03518; Thu, 3 Dec 1998 13:11:05 +1100 (EST) Message-ID: <19981203131105.F2934@rf900.physics.usyd.edu.au> Date: Thu, 3 Dec 1998 13:11:05 +1100 From: David Dawes To: Mike Smith Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: sio breakage References: <19981203115222.A3051@rf900.physics.usyd.edu.au> <199812030107.RAA01213@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812030107.RAA01213@dingo.cdrom.com>; from Mike Smith on Wed, Dec 02, 1998 at 05:07:00PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 05:07:00PM -0800, Mike Smith wrote: >> On Wed, Dec 02, 1998 at 08:46:45PM +1100, Peter Jeremy wrote: >> >> >>> I don't believe this is reasonable. We should provide some safe way >> >>> for an application program to execute code with interrupts disabled. >> >>> Amongst other applications, XFree86 needs this. >> >> >> >>It shouldn't (ideally). >> >I agree. And whilst I haven't checked why, XFree86 does appear to >> >disable interrupts at times. >> >> I agree too, but it does disable interrupts when probing for fixed pixel >> clocks (which is mostly only done for obsolete hardware), and sometimes >> when programming PLLs. If someone has a better way of handling time >> critical thing like this (preferably in a portable way), please let me >> know. I'd love to dump our disable interrupt code. > >I get the impression from this though that you only do interrupt >disables when probing or changing video modes, is that correct? Yes that's true (modulo any bugs). >The entire train of angst here is descended from percieved problems in >interrupt delivery during normal operation; if you're only disabling >interrupts during startup then this prettymuch exonerates the X server. > >> >> If it does, this is clearly indicative of a >> >>need to move some of the server code into the kernel, >> >You mean, like GGI :-). >> >> There are some tasks that are much better suited to the kernel, and >> perhaps a better balance could be found by just doing those few selected >> things in the kernel and leaving the rest of it in user space. > >Quite possibly; I wasn't sure that it would help performance, and it >would *certainly* make your lives harder. 8( I'm thinking first of all of the cases where the X server currently disables interrupts, which are areas that don't affect performance. Clock probing is close to redundant for modern hardware, but there are still time-critical issues when programming some PLLs, and that might be more reliably done in the kernel. It would make our lives harder, yes, and maybe it isn't really practical given the range of platforms that XFree86 runs on. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:23:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11472 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:23:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11452 for ; Wed, 2 Dec 1998 18:23:10 -0800 (PST) (envelope-from ggm@sleet.dstc.edu.au) Received: from sleet.dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA16289 for ; Thu, 3 Dec 1998 12:22:56 +1000 (EST) Received: (from ggm@localhost) by sleet.dstc.edu.au (8.8.5/8.8.4) id MAA13680 for current@freebsd.org; Thu, 3 Dec 1998 12:22:54 +1000 (EST) Date: Thu, 3 Dec 1998 12:22:54 +1000 (EST) From: George Michaelson Message-Id: <199812030222.MAA13680@sleet.dstc.edu.au> To: current@FreeBSD.ORG Subject: ELFland/Linux misdirected Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sorry. qn is for emulation. sleep again. -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11590 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:24:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11584 for ; Wed, 2 Dec 1998 18:24:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03196; Wed, 2 Dec 1998 18:22:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030222.SAA03196@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Wed, 02 Dec 1998 18:13:16 PST." <199812030213.SAA03115@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 18:22:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > or to unload unused segments and > > reload them on the fly during further probe/attach requests (ala Linux). > > It would certainly be feasible to arrange for the firmware images to be > loaded from separate files, should that be an acceptable alternative. > I'm open to suggestions on how to make this economical and robust... I should probably have expanded here; I was thinking for some time about the usefulness of optionally having two modules associated with a driver; the core driver code and the 'init' module for the code. You'd normally put these into two separate files, so for 'foo' you'd have foo.ko and foo_init.ko. There are issues about how you express the dependancies between these modules: foo_init depends on foo, but foo also has an init-time dependancy on foo_init. >From the loader's perspective, you'd load the two of them together (either as a result of some dependancy or explicitly out of the config metainformation), the foo_init module would do its work and then (somehow) determine that it was no longer required and free (most of?) itself. >From a pragmatic perspective, I guess my major concern is whether this elegance is warranted; you save a few pages of kernel space, but on the sort of systems where these devices are common such a saving is relatively infestimal. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 18:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12140 for freebsd-current-outgoing; Wed, 2 Dec 1998 18:30:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12129 for ; Wed, 2 Dec 1998 18:30:08 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id NAA03658; Thu, 3 Dec 1998 13:29:25 +1100 (EST) Message-ID: <19981203132925.G2934@rf900.physics.usyd.edu.au> Date: Thu, 3 Dec 1998 13:29:25 +1100 From: David Dawes To: Nate Williams , Mike Smith Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: sio breakage References: <19981203115222.A3051@rf900.physics.usyd.edu.au> <199812030107.RAA01213@dingo.cdrom.com> <199812030114.SAA10483@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812030114.SAA10483@mt.sri.com>; from Nate Williams on Wed, Dec 02, 1998 at 06:14:09PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 06:14:09PM -0700, Nate Williams wrote: >> > >I agree. And whilst I haven't checked why, XFree86 does appear to >> > >disable interrupts at times. >> > >> > I agree too, but it does disable interrupts when probing for fixed pixel >> > clocks (which is mostly only done for obsolete hardware), and sometimes >> > when programming PLLs. If someone has a better way of handling time >> > critical thing like this (preferably in a portable way), please let me >> > know. I'd love to dump our disable interrupt code. >> >> I get the impression from this though that you only do interrupt >> disables when probing or changing video modes, is that correct? > >I get that impression as well. > >> The entire train of angst here is descended from percieved problems in >> interrupt delivery during normal operation; if you're only disabling >> interrupts during startup then this prettymuch exonerates the X server. > >Except that I can say with assurance that at least older versions of the >XFree86 server *seem* to be disabling interrupts for long periods, or at >least calling code that disables interrupts. When I switched to the XIG >(XInside at the time) server, all of my serial overflows went away. It would be good if it this could be confirmed, perhaps by tracing when the disable/enable interrupt functions are called. In my quick search of the code I could only find it done at server startup and when programming a new video mode (and then only for some hardware). >That was the *only* configuration difference. To be sure, I even >re-configured the XFree86 server and the problem re-occurred. Swapped >it back and it went away. > >Note, this was about a year ago, maybe more so it may have changed. >(The box in question has a S3 928 card in it..) Is it a PCI card? Are you using it in mmio or pio mode? I have a box with an S3 964 using the 928-compatible mmio mode. I've seen sio "tty-level" and "interrupt-level" buffer overflows from time to time (with a FreeBSD 2.2.2 kernel), but I haven't been able to make a direct connection between them and the X server. They seem to happen more often with the machine is "busy". Interestingly I've seen them much less frequently (including none in the last two months) since switching from an SMC ISA Ethernet card to an Intel EEPro/100+ for most of the network traffic that this box sees. That may be entirely conincidental though. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 19:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16006 for freebsd-current-outgoing; Wed, 2 Dec 1998 19:00:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15996 for ; Wed, 2 Dec 1998 19:00:46 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id NAA08761; Thu, 3 Dec 1998 13:58:49 +1100 (EST) Date: Thu, 3 Dec 1998 13:58:49 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: "Jordan K. Hubbard" cc: Joao Carlos Mendes Luis , "Matthew N. Dodd" , bde@zeta.org.au, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Uh oh... In-Reply-To: <9687.912641546@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Jordan K. Hubbard wrote: > > Maybe a suggestion to look at src/etc/master.passwd, etc. could be > > enough. Anyway, make world should not be used by novices. :) > > And is, every single day. :-) > > - Jordan The first make world is when a 'novice' becomes a 'newbie' ;-) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 20:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22115 for freebsd-current-outgoing; Wed, 2 Dec 1998 20:03:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22110 for ; Wed, 2 Dec 1998 20:03:30 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA29652; Wed, 2 Dec 1998 21:03:03 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA11220; Wed, 2 Dec 1998 21:03:02 -0700 Date: Wed, 2 Dec 1998 21:03:02 -0700 Message-Id: <199812030403.VAA11220@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: David Dawes Cc: Nate Williams , Mike Smith , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sio breakage In-Reply-To: <19981203132925.G2934@rf900.physics.usyd.edu.au> References: <19981203115222.A3051@rf900.physics.usyd.edu.au> <199812030107.RAA01213@dingo.cdrom.com> <199812030114.SAA10483@mt.sri.com> <19981203132925.G2934@rf900.physics.usyd.edu.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I get the impression from this though that you only do interrupt > >> disables when probing or changing video modes, is that correct? > > > >I get that impression as well. > > > >> The entire train of angst here is descended from percieved problems in > >> interrupt delivery during normal operation; if you're only disabling > >> interrupts during startup then this prettymuch exonerates the X server. > > > >Except that I can say with assurance that at least older versions of the > >XFree86 server *seem* to be disabling interrupts for long periods, or at > >least calling code that disables interrupts. When I switched to the XIG > >(XInside at the time) server, all of my serial overflows went away. > > It would be good if it this could be confirmed, perhaps by tracing > when the disable/enable interrupt functions are called. In my quick > search of the code I could only find it done at server startup and > when programming a new video mode (and then only for some hardware). How would I got about doing that? > >That was the *only* configuration difference. To be sure, I even > >re-configured the XFree86 server and the problem re-occurred. Swapped > >it back and it went away. > > > >Note, this was about a year ago, maybe more so it may have changed. > >(The box in question has a S3 928 card in it..) > > Is it a PCI card? Are you using it in mmio or pio mode? S3/ISA card. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 20:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23969 for freebsd-current-outgoing; Wed, 2 Dec 1998 20:21:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23964 for ; Wed, 2 Dec 1998 20:21:09 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA27439; Wed, 2 Dec 1998 20:19:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda27437; Thu Dec 3 04:19:12 1998 Message-ID: <36661125.31DFF4F5@whistle.com> Date: Wed, 02 Dec 1998 20:18:45 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG CC: Kirk McKusick , Don Lewis Subject: FreeBSD fsck updated References: <199811230603.WAA02649@salsa.gv.tsc.tdk.com> Content-Type: multipart/mixed; boundary="------------7DE145182F1CF0FB237C228A" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------7DE145182F1CF0FB237C228A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have checked in kirk's newest fsck (well, a week or so old) This understands soft updates a bit better, and has some improved checks for orrupted filesystems and a few fixes.. We have also incorporated soem FreeBSD fixes in kirk's sources. What I have left are a few small patches (attached) that I'm not sure about. Two appear to be fro support for symlinks-in-inode denoted by a 0 block count. (I'm not sure about the correctness of them) (when was it done that way? 386BSD?) one is some extra pronouncements when some bits are found unset. whether we merge these old freebsd bits into the current new version is more a political matter.. What does everyone think? I now kirk doesn't like the noisy messages about the clean and modified bits.. julian --------------7DE145182F1CF0FB237C228A Content-Type: text/plain; charset=us-ascii; name="still2do.diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="still2do.diffs" Is this the verboseness you were complaining about? diff -cr fsck/pass5.c fsck.julian/pass5.c *** fsck/pass5.c Wed Dec 2 18:41:11 1998 --- fsck.julian/pass5.c Wed Dec 2 16:26:18 1998 *************** *** 355,361 **** && dofix(&idesc[0], "FREE BLK COUNT(S) WRONG IN SUPERBLK")) { memmove(&fs->fs_cstotal, &cstotal, sizeof *cs); fs->fs_ronly = 0; - fs->fs_fmod = 0; sbdirty(); } } --- 355,378 ---- && dofix(&idesc[0], "FREE BLK COUNT(S) WRONG IN SUPERBLK")) { memmove(&fs->fs_cstotal, &cstotal, sizeof *cs); fs->fs_ronly = 0; sbdirty(); + } + if (fs->fs_fmod != 0) { + pwarn("MODIFIED FLAG SET IN SUPERBLOCK"); + if (preen) + printf(" (FIXED)\n"); + if (preen || reply("FIX") == 1) { + fs->fs_fmod = 0; + sbdirty(); + } + } + if (fs->fs_clean == 0) { + pwarn("CLEAN FLAG NOT SET IN SUPERBLOCK"); + if (preen) + printf(" (FIXED)\n"); + if (preen || reply("FIX") == 1) { + fs->fs_clean = 1; + sbdirty(); + } } } Should a symbolic link with no blocks be treated differently? Possibly this is supporting old hidden symlinks. diff -cr fsck/inode.c fsck.don/inode.c *** fsck/inode.c Wed Dec 2 18:41:11 1998 --- fsck.don/inode.c Wed Dec 2 17:17:32 1998 *************** *** 75,81 **** idesc->id_filesize = dp->di_size; mode = dp->di_mode & IFMT; if (mode == IFBLK || mode == IFCHR || (mode == IFLNK && ! dp->di_size < (unsigned)sblock.fs_maxsymlinklen)) return (KEEPON); dino = *dp; ndb = howmany(dino.di_size, sblock.fs_bsize); --- 75,81 ---- idesc->id_filesize = dp->di_size; mode = dp->di_mode & IFMT; if (mode == IFBLK || mode == IFCHR || (mode == IFLNK && ! (dp->di_size < sblock.fs_maxsymlinklen || dp->di_blocks == 0))) return (KEEPON); dino = *dp; ndb = howmany(dino.di_size, sblock.fs_bsize); I guess this is also "old" symlink support.. diff -cr fsck/pass1.c fsck.don/pass1.c *** fsck/pass1.c Wed Dec 2 18:41:11 1998 --- fsck.don/pass1.c Wed Dec 2 17:17:32 1998 *************** *** 241,247 **** * Fake ndb value so direct/indirect block checks below * will detect any garbage after symlink string. */ ! if (dp->di_size < sblock.fs_maxsymlinklen) { ndb = howmany(dp->di_size, sizeof(ufs_daddr_t)); if (ndb > NDADDR) { j = ndb - NDADDR; --- 241,248 ---- * Fake ndb value so direct/indirect block checks below * will detect any garbage after symlink string. */ ! if ((dp->di_size < sblock.fs_maxsymlinklen) || ! dp->di_blocks == 0) { ndb = howmany(dp->di_size, sizeof(ufs_daddr_t)); if (ndb > NDADDR) { j = ndb - NDADDR; --------------7DE145182F1CF0FB237C228A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28695 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:02:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28690 for ; Wed, 2 Dec 1998 21:02:11 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id AAA03579 for current@freebsd.org; Thu, 3 Dec 1998 00:01:51 -0500 (EST) From: Mikhail Teterin Message-Id: <199812030501.AAA03579@kot.ne.mediaone.net> Subject: feature requests for install To: current@FreeBSD.ORG Date: Thu, 3 Dec 1998 00:01:51 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28790 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:03:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.flathill.gr.jp (ns.flathill.gr.jp [210.157.239.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA28785 for ; Wed, 2 Dec 1998 21:03:28 -0800 (PST) (envelope-from flathill@flathill.gr.jp) Received: (qmail 28386 invoked from network); 3 Dec 1998 05:03:14 -0000 Received: from azuki.flathill.gr.jp (HELO localhost) (210.157.239.83) by ns.flathill.gr.jp with SMTP; 3 Dec 1998 05:03:14 -0000 To: freebsd-current@FreeBSD.ORG Subject: can't reach other host over router X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981203140306N.flathill@flathill.gr.jp> Date: Thu, 03 Dec 1998 14:03:06 +0900 From: Seiichirou Hiraoka X-Dispatcher: imput version 980905(IM100) Lines: 63 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm using current(cvsup in Dec 2) I can't reach other host over router(YAMAHA RT-80i). Now,I can't use cvsup,telnet,traceroute,ping,and other. 1st. I try ping to host in my local network,and it succeed. 2nd. ping to my router,and succeed. 3rd. ping to host in other network,for examples www.freebsd.org, and it fails. ----- azuki(47) % ping www.freebsd.org PING freefall.freebsd.org (204.216.27.21): 56 data bytes ^C --- freefall.freebsd.org ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss ----- This is result of 'tcpdump dst host freefall.freebsd.org', And type "telnet freefall.freebsd.org" ----- tcpdump: listening on fxp0 13:58:15.112208 azuki.flathill.gr.jp.2803 > freefall.FreeBSD.ORG.telnet: S 1487641022:1487641022(0) win 16384 (DF) [tos 0x10] 13:58:18.077651 azuki.flathill.gr.jp.2803 > freefall.FreeBSD.ORG.telnet: S 1487641022:1487641022(0) win 16384 (DF) [tos 0x10] . . ----- Next, I try same to above on host in my local network. It is using 2.2.6R,and succeed. ----- ns(27) % ping www.freebsd.org PING freefall.freebsd.org (204.216.27.21): 56 data bytes 64 bytes from 204.216.27.21: icmp_seq=0 ttl=242 time=266.451 ms 64 bytes from 204.216.27.21: icmp_seq=1 ttl=242 time=260.477 ms ^C --- freefall.freebsd.org ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 260.477/263.464/266.451/2.987 ms ----- This is result of 'tcpdump dst host freefall.freebsd.org', And type "telnet freefall.freebsd.org" ----- tcpdump: listening on fxp0 13:57:05.025031 ns.flathill.gr.jp.4129 > freefall.FreeBSD.ORG.telnet: S 1437554684:1437554684(0) win 16384 (DF) [tos 0x10] 13:57:05.337368 ns.flathill.gr.jp.4129 > freefall.FreeBSD.ORG.telnet: . ack 6327411 win 17280 (DF) [tos 0x10] 13:57:05.338587 ns.flathill.gr.jp.4129 > freefall.FreeBSD.ORG.telnet: P 0:27(27) ack 1 win 17280 (DF) [tos 0x10] 13:57:05.989167 ns.flathill.gr.jp.4129 > freefall.FreeBSD.ORG.telnet: P 27:30(3) ack 16 win 17280 (DF) [tos 0x10] . . ----- So, I think something is wrong in current. Someone have the same problem? - Seiichirou Hiraoka flathill@flathill.gr.jp : http://www.flathill.gr.jp/~flathill/ flathill@FreeBSD.ORG : http://www.FreeBSD.ORG/~flathill/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29840 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:15:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.flathill.gr.jp (ns.flathill.gr.jp [210.157.239.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA29833 for ; Wed, 2 Dec 1998 21:15:19 -0800 (PST) (envelope-from flathill@flathill.gr.jp) Received: (qmail 28738 invoked from network); 3 Dec 1998 05:15:05 -0000 Received: from azuki.flathill.gr.jp (HELO localhost) (210.157.239.83) by ns.flathill.gr.jp with SMTP; 3 Dec 1998 05:15:05 -0000 To: freebsd-current@FreeBSD.ORG Subject: Re: can't reach other host over router In-Reply-To: Your message of "Thu, 03 Dec 1998 14:03:06 +0900" <19981203140306N.flathill@flathill.gr.jp> References: <19981203140306N.flathill@flathill.gr.jp> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981203141458T.flathill@flathill.gr.jp> Date: Thu, 03 Dec 1998 14:14:58 +0900 From: Seiichirou Hiraoka X-Dispatcher: imput version 980905(IM100) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, flathill> I'm using current(cvsup in Dec 2) flathill> I can't reach other host over router(YAMAHA RT-80i). flathill> Now,I can't use cvsup,telnet,traceroute,ping,and other. VERY,VERY,SORRY... I mistook defaultrouter in /etc/rc.conf. I fix it and success to connect other host. - Seiichirou Hiraoka flathill@flathill.gr.jp : http://www.flathill.gr.jp/~flathill/ flathill@FreeBSD.ORG : http://www.FreeBSD.ORG/~flathill/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:17:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00122 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:17:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00105 for ; Wed, 2 Dec 1998 21:17:37 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from photon (photon [129.127.36.4]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA02961; Thu, 3 Dec 1998 15:47:18 +1030 (CST) Received: from localhost by photon; (5.65/1.1.8.2/04Aug95-0645PM) id AA00631; Thu, 3 Dec 1998 15:47:55 +1030 Date: Thu, 3 Dec 1998 15:47:55 +1030 (CST) From: Kris Kennaway To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: feature requests for install In-Reply-To: <199812030501.AAA03579@kot.ne.mediaone.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Mikhail Teterin wrote: > 1) Dhcp-client support at install time. > > 2) Socks5-client support. The second one is interesting (to me). I wonder how feasible it is to do (i.e., how much (non-existant) extra space it would require). There's also the licensing issue - ISTR the socks5 sources being under a restricted license. If no-one else is interested in doing this I might have a look at it over the next few weeks, as a project to get my feet wet with :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:20:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00353 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:20:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00348 for ; Wed, 2 Dec 1998 21:20:35 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA27901; Wed, 2 Dec 1998 21:20:21 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA29197; Wed, 2 Dec 1998 21:20:21 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 2 Dec 1998 21:20:21 -0800 (PST) Message-Id: <199812030520.VAA29197@vashon.polstra.com> To: cejkar@dcse.fee.vutbr.cz Subject: Re: cvsup problems Newsgroups: polstra.freebsd.current In-Reply-To: <199812011619.RAA26714@kazi.dcse.fee.vutbr.cz> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812011619.RAA26714@kazi.dcse.fee.vutbr.cz>, Cejka Rudolf wrote: > Problems have started one week ago so I'm trying to ask others: > > When I'm trying to realize cvsup from almost every one cvsup.XX.freebsd.org > (de, fi, jp, nl...) server, it ends up with this error message > after a while: > > TreeList failed: Network write failure: Connection lost It sounds like network problems, not CVSup problems. Try "-P m" on the cvsup command line. That makes it behave more like "normal" applications as far as the network is concerned. If it helps, it probably indicates that there's a buggy router between you and the server. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01259 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:35:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01246 for ; Wed, 2 Dec 1998 21:34:57 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id AAA10530; Thu, 3 Dec 1998 00:37:53 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 3 Dec 1998 00:37:53 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: John Polstra cc: cejkar@dcse.fee.vutbr.cz, current@FreeBSD.ORG Subject: Re: cvsup problems In-Reply-To: <199812030520.VAA29197@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, John Polstra wrote: > In article <199812011619.RAA26714@kazi.dcse.fee.vutbr.cz>, > Cejka Rudolf wrote: > > Problems have started one week ago so I'm trying to ask others: > > > > When I'm trying to realize cvsup from almost every one cvsup.XX.freebsd.org > > (de, fi, jp, nl...) server, it ends up with this error message > > after a while: > > > > TreeList failed: Network write failure: Connection lost > > It sounds like network problems, not CVSup problems. Try "-P m" on > the cvsup command line. That makes it behave more like "normal" > applications as far as the network is concerned. If it helps, it > probably indicates that there's a buggy router between you and the > server. If that fails try: "-P -" is your last resort. It tells cvsup to only use a single outgoing socket. If you still have problems go over your network config and/or talk to your ISP/admin. -Alfred > > John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 21:45:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02197 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:45:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02192 for ; Wed, 2 Dec 1998 21:45:28 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA05315; Thu, 3 Dec 1998 00:44:10 -0500 (EST) Date: Thu, 3 Dec 1998 00:44:10 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812030213.SAA03115@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Mike Smith wrote: > It would certainly be feasible to arrange for the firmware images to > be loaded from separate files, should that be an acceptable > alternative. I'm open to suggestions on how to make this economical > and robust... Ooh! Ooh! Me Me! I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware image for support of RAM based TMS380 cards. In addition, some each particular card may have specific firmware it wants loaded. I'm looking for some way to load a really basic config file to let the driver know which image goes with which card. Doing this from userland isn't good as I can't do much with the card until the firmware is loaded. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 22:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03856 for freebsd-current-outgoing; Wed, 2 Dec 1998 22:08:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03850 for ; Wed, 2 Dec 1998 22:08:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA28025; Wed, 2 Dec 1998 22:08:27 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id WAA29237; Wed, 2 Dec 1998 22:08:27 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 02 Dec 1998 22:08:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Alfred Perlstein Subject: Re: cvsup problems Cc: current@FreeBSD.ORG, cejkar@dcse.fee.vutbr.cz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Dec-98 Alfred Perlstein wrote: > On Wed, 2 Dec 1998, John Polstra wrote: >> It sounds like network problems, not CVSup problems. Try "-P m" on >> the cvsup command line. That makes it behave more like "normal" >> applications as far as the network is concerned. If it helps, it >> probably indicates that there's a buggy router between you and the >> server. > > If that fails try: > > "-P -" > > is your last resort. It tells cvsup to only use a single outgoing socket. True, but "-P m" is the safest. It only uses a single TCP connection, period. "-P -" uses two TCP connections, and its traffic patterns on the connections are more atypical. Trust me, I wrote the thing. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 22:24:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05344 for freebsd-current-outgoing; Wed, 2 Dec 1998 22:24:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05339 for ; Wed, 2 Dec 1998 22:24:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA13779; Wed, 2 Dec 1998 22:26:00 -0800 (PST) To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: feature requests for install In-reply-to: Your message of "Thu, 03 Dec 1998 00:01:51 EST." <199812030501.AAA03579@kot.ne.mediaone.net> Date: Wed, 02 Dec 1998 22:26:00 -0800 Message-ID: <13775.912666360@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1) Dhcp-client support at install time. > > 2) Socks5-client support. Would be nice... I think this has been on the request list for several years now, at least the first one. > Those installing on corporate networks or over increasingly popular > cable-modems will be a lot happier... > > Where are my patches?.. I was just about to ask you the same thing - you simply forgot to attach them? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 22:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07277 for freebsd-current-outgoing; Wed, 2 Dec 1998 22:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07272 for ; Wed, 2 Dec 1998 22:44:46 -0800 (PST) (envelope-from bford@uop.cs.uop.edu) Received: from heather (ppp-206-171-161-22.sktn01.pacbell.net [206.171.161.22]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id WAA17831 for ; Wed, 2 Dec 1998 22:00:03 -0800 (PST) Message-ID: <000301be1e82$2d849d00$0100a8c0@heather.my.domain> From: "Bret Ford" To: Subject: panic: ffs_blkfree: bad size Date: Wed, 2 Dec 1998 22:00:02 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I've been getting kernel panic and reboot conditions under -current for a while now---here's my attempt at a report: My system is a 486 main board with a 133mhz cpu upgrade and 128mb parity RAM. It has 2 Adaptec SCSI cards---a 2742 and a 1542C. Two disk systems have softupdates enabled: a fast SCSI SEAGATE ST410800N (9 gb) and a 3 x 1gb CONNER CFP1060W based striped set of fast wide SCSIs. My -current kernel is from early morning (~ 4am)---compiled Wed Dec 2 20:31:42 PST 1998. My 1542C has my root disk, a FUJITSU M2624F-512, an HP C2257, and a TOSHIBA CD-ROM XM-3401TA. Usually, the system will have rebooted once or twice during the night while source trees are being synched on the striped set. (lots of disk activity is the culprit, I'm guessing). I haven't had occasion to catch one of those, but I have caught one during the day today--- While backing up my windows95 system with imagecast (IC3) from a network boot floppy to my Seagate via samba-1.9.18.10, the kernel died with: dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var panic: ffs_blkfree: bad size /var is on the Fujitsu -current code base from ~11/28 or so, I think. Thanks, Bret Ford bford@uop.cs.uop.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 22:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07534 for freebsd-current-outgoing; Wed, 2 Dec 1998 22:47:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07526 for ; Wed, 2 Dec 1998 22:47:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA13987; Wed, 2 Dec 1998 22:49:12 -0800 (PST) To: "Bret Ford" cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Wed, 02 Dec 1998 22:00:02 PST." <000301be1e82$2d849d00$0100a8c0@heather.my.domain> Date: Wed, 02 Dec 1998 22:49:11 -0800 Message-ID: <13982.912667751@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > > /var is on the Fujitsu > -current code base from ~11/28 or so, I think. I seem to recall that this was fixed on the 29th. :) [no kidding] - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09273 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:03:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09268 for ; Wed, 2 Dec 1998 23:03:12 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id XAA59381; Wed, 2 Dec 1998 23:10:43 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812030710.XAA59381@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <13982.912667751@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 1998 10:49:11 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Dec 1998 23:10:43 -0800 (PST) Cc: bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > > /var is on the Fujitsu > > -current code base from ~11/28 or so, I think. > > I seem to recall that this was fixed on the 29th. :) [no kidding] > Although I normally appreciate your humor, this bug is not funny. Version 1.74 of vfs_cluster.c does not fix the problem, and a person can totally destroy their filesystems. sysctl -w vfs.ffs.doreallocblks=0 Is the correct response. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:06:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09663 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:06:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09658 for ; Wed, 2 Dec 1998 23:06:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id XAA59399; Wed, 2 Dec 1998 23:13:53 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812030713.XAA59399@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <000301be1e82$2d849d00$0100a8c0@heather.my.domain> from Bret Ford at "Dec 2, 1998 10: 0: 2 pm" To: bford@uop.cs.uop.edu (Bret Ford) Date: Wed, 2 Dec 1998 23:13:53 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bret Ford: > Greetings, > > I've been getting kernel panic and reboot conditions under -current > for a while now---here's my attempt at a report: > > dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > To work around the problem, as root do sysctl -w vfs.ffs.doreallocblks=0 Better. Compile a kernel with options DDB and debugging symbols. At your next crash try to get a dump. You'll need to set dumpdev in /etc/rc.conf -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:18:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10716 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:18:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10660 for ; Wed, 2 Dec 1998 23:17:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA14139; Wed, 2 Dec 1998 23:19:20 -0800 (PST) To: Steve Kargl cc: bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Wed, 02 Dec 1998 23:10:43 PST." <199812030710.XAA59381@troutmask.apl.washington.edu> Date: Wed, 02 Dec 1998 23:19:19 -0800 Message-ID: <14136.912669559@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Although I normally appreciate your humor, this bug is not > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > and a person can totally destroy their filesystems. It wasn't an attempt at humor - I thought he still had an older kernel too and thought that David's attempted fix (I say "attempted" since it is clearly still nuking you) would set him right. > sysctl -w vfs.ffs.doreallocblks=0 > > Is the correct response. Why isn't this currently the default if it's as pathological as you say? Has anyone actually asked David this question? It would be only courteous given that he's the author of this bug/feature. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10787 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:18:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10766 for ; Wed, 2 Dec 1998 23:18:18 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA08410 for ; Thu, 3 Dec 1998 18:18:04 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd008408; Thu Dec 3 07:18:02 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id SAA29220 for ; Thu, 3 Dec 1998 18:18:08 +1100 (EST) Message-Id: <199812030718.SAA29220@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: How to catch all the /etc/pam.conf type mistakes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 18:17:59 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just cvsup'd from the 3.0 CDs and been bit by the pam.conf thang (that was handily explained by John Polk's message in the mailing list archives - I'm new to -current and not long on this list, despite having run Stable and followed the -stable list since 2.2.6). 2 Questions: - How can I easily tell what time my sources were cvsup'd to [apart from redirecting stderr and using the error file as a timestamp?] - How can I find a list of all the things (such as pam.conf) that I need to fix that installworld doesn't notice? Is there some equivalent of the ERRATA file for tracking -current? I caught this one because missing pam.conf causes vocal and common error messages, and I found the email because I searched for pam.conf. What I am a little worried about is there may be other similar things I need to manually fix but I just haven't noticed them yet... Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11421 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:22:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11406 for ; Wed, 2 Dec 1998 23:22:42 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id AAA01117; Thu, 3 Dec 1998 00:22:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id AAA12187; Thu, 3 Dec 1998 00:22:21 -0700 Date: Thu, 3 Dec 1998 00:22:21 -0700 Message-Id: <199812030722.AAA12187@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <14136.912669559@zippy.cdrom.com> References: <199812030710.XAA59381@troutmask.apl.washington.edu> <14136.912669559@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Although I normally appreciate your humor, this bug is not > > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > > and a person can totally destroy their filesystems. > > It wasn't an attempt at humor - I thought he still had an older kernel > too and thought that David's attempted fix (I say "attempted" since it > is clearly still nuking you) would set him right. > > > sysctl -w vfs.ffs.doreallocblks=0 > > > > Is the correct response. > > Why isn't this currently the default if it's as pathological as you > say? Has anyone actually asked David this question? It would be > only courteous given that he's the author of this bug/feature. Kirk is the author of the bug/feature, David was just the committer. His response to the crash has been to send email to Kirk with the crash details. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12019 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:29:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12014 for ; Wed, 2 Dec 1998 23:29:20 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from photon (photon [129.127.36.4]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA04336; Thu, 3 Dec 1998 17:59:04 +1030 (CST) Received: from localhost by photon; (5.65/1.1.8.2/04Aug95-0645PM) id AA00715; Thu, 3 Dec 1998 17:59:34 +1030 Date: Thu, 3 Dec 1998 17:59:33 +1030 (CST) From: Kris Kennaway To: Gregory Bond Cc: current@FreeBSD.ORG Subject: Re: How to catch all the /etc/pam.conf type mistakes In-Reply-To: <199812030718.SAA29220@melba.bby.com.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Gregory Bond wrote: > - How can I find a list of all the things (such as pam.conf) that I need to > fix that installworld doesn't notice? Is there some equivalent of the ERRATA > file for tracking -current? I don't know if there's an errata list (although IMO the various "heads-up" messages which get posted here should be archived on the web or somewhere for just this reason). Searching the -current archives for "Heads up" should give you all the critical changes in the absence of that. Look at /usr/ports/sysutils/mergemaster for a very handy tool for updating your /etc directory. If you're updating across more than a few weeks time difference, chances are there will be changes that should be merged, which 'make world' does not do. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:31:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12207 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:31:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12202 for ; Wed, 2 Dec 1998 23:31:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA14261; Wed, 2 Dec 1998 23:32:42 -0800 (PST) To: Nate Williams cc: Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Thu, 03 Dec 1998 00:22:21 MST." <199812030722.AAA12187@mt.sri.com> Date: Wed, 02 Dec 1998 23:32:41 -0800 Message-ID: <14258.912670361@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kirk is the author of the bug/feature, David was just the committer. > His response to the crash has been to send email to Kirk with the crash > details. I'm quite well aware of that, but as the committer it's David who has the actual responsibility for it and, if it's nuking people, his responsibility for setting the defaults in such a way as to not do so. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:35:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12523 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:35:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12493 for ; Wed, 2 Dec 1998 23:34:47 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id KAA06686; Thu, 3 Dec 1998 10:24:44 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Thu, 3 Dec 1998 10:24:43 +0300 (MSK) From: "Roman V. Palagin" To: Steve Kargl cc: "Jordan K. Hubbard" , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812030710.XAA59381@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Steve Kargl wrote: > According to Jordan K. Hubbard: > > > dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var > > > panic: ffs_blkfree: bad size > > > > > > /var is on the Fujitsu > > > -current code base from ~11/28 or so, I think. > > > > I seem to recall that this was fixed on the 29th. :) [no kidding] > > > > Although I normally appreciate your humor, this bug is not > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > and a person can totally destroy their filesystems. Yes, I can confirm this. Even after Dec 1 you can see ugly ffs_blkfree panic. It's very unstable bug - your uptime can be 2 or 3 days and oops - your can see core in /var/crash :(( > > sysctl -w vfs.ffs.doreallocblks=0 > > Is the correct response. > > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:43:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13054 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:43:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13048 for ; Wed, 2 Dec 1998 23:43:44 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id XAA59629; Wed, 2 Dec 1998 23:51:16 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812030751.XAA59629@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <14136.912669559@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 1998 11:19:19 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Dec 1998 23:51:16 -0800 (PST) Cc: bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > Although I normally appreciate your humor, this bug is not > > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > > and a person can totally destroy their filesystems. > > It wasn't an attempt at humor - I thought he still had an older kernel > too and thought that David's attempted fix (I say "attempted" since it > is clearly still nuking you) would set him right. > > > sysctl -w vfs.ffs.doreallocblks=0 > > > > Is the correct response. > > Why isn't this currently the default if it's as pathological as you > say? Has anyone actually asked David this question? It would be > only courteous given that he's the author of this bug/feature. > I've had several email exchanges with David, and I have been in touch with Kirk. I have provided the stack trace, but I can't get a dump (see a recent email from me entitled "Crash dump howto?"). If I can get a dump, I will give Kirk complete access to my boxes. If you use softupdates, this problem will probably not occur. If you use sync or async filesystems, you may be hosed to the point that fsck has problems. It is pathological in the sense that fsck reports tons of DUP inodes and INCORRECT COUNTS and assorted other messages I don't remember. /var/lost+found becomes well populated. I think it is a subtle bug that rears its ugly head if you put a system under heavy. My machine will crash within an hour by executing "make -j 32 world" and "make -j 8 ; make clean" in a loop in compile/GENERIC. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:49:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13629 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:49:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13623 for ; Wed, 2 Dec 1998 23:49:51 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id XAA59655; Wed, 2 Dec 1998 23:55:06 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812030755.XAA59655@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: from "Roman V. Palagin" at "Dec 3, 1998 10:24:43 am" To: romanp@wuppy.rcs.ru (Roman V. Palagin) Date: Wed, 2 Dec 1998 23:55:06 -0800 (PST) Cc: jkh@zippy.cdrom.com, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Roman V. Palagin: > On Wed, 2 Dec 1998, Steve Kargl wrote: > > > > > Although I normally appreciate your humor, this bug is not > > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > > and a person can totally destroy their filesystems. > Yes, I can confirm this. Even after Dec 1 you can see ugly ffs_blkfree > panic. It's very unstable bug - your uptime can be 2 or 3 days and oops - > your can see core in /var/crash :(( > If you can get a core in /var/crash, and you have a kernel with debug symbols, then PLEASE, PLEASE, PLEASE contact Kirk McKusisk or David Greenman. PS: I'm not shouting, I'm begging. I've been trying to get a core for 2 weeks. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 2 23:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14429 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:58:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14420 for ; Wed, 2 Dec 1998 23:58:46 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id XAA17756; Wed, 2 Dec 1998 23:59:49 -0800 (PST) Message-Id: <199812030759.XAA17756@root.com> To: "Jordan K. Hubbard" cc: Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Wed, 02 Dec 1998 23:19:19 PST." <14136.912669559@zippy.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 02 Dec 1998 23:59:49 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> sysctl -w vfs.ffs.doreallocblks=0 >> >> Is the correct response. > >Why isn't this currently the default if it's as pathological as you >say? Has anyone actually asked David this question? It would be >only courteous given that he's the author of this bug/feature. The feature is fairly important. Steve and one or two other people are the only ones seeing the problem after Kirk's fix was committed. Steve is the only person to report filesystem corruption caused by it. I'm not able to reproduce the panic, despite doing more than 20 "make world"s in an attempt to reproduce it. If we disable it by default then it will never get fixed because there will be no feedback from people who are still having problems with it. I WILL disable it prior to the 3.0.1 release if it isn't fixed by then, however. Meanwhile I'll look at adding something that will ensure that filesystem corruption isn't possible - I think this will amount to detecting the problem and panicing earlier. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 00:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17623 for freebsd-current-outgoing; Thu, 3 Dec 1998 00:30:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17512 for ; Thu, 3 Dec 1998 00:30:00 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA12886 for current@freebsd.org; Thu, 3 Dec 1998 19:38:02 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812030838.TAA12886@cimlogic.com.au> Subject: SYSINIT defs in kernel.h To: current@FreeBSD.ORG Date: Thu, 3 Dec 1998 19:38:01 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone object to me adding `__attribute__ ((unused))' to the SYSINIT etc definitions in sys/sys/kernel.h to stop gcc generating an unused variable warning? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 00:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18109 for freebsd-current-outgoing; Thu, 3 Dec 1998 00:35:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18101 for ; Thu, 3 Dec 1998 00:35:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA10358; Thu, 3 Dec 1998 09:34:49 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812030834.JAA10358@freebsd.dk> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812030759.XAA17756@root.com> from David Greenman at "Dec 2, 1998 11:59:49 pm" To: dg@root.com Date: Thu, 3 Dec 1998 09:34:49 +0100 (CET) Cc: jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Greenman wrote: > >> sysctl -w vfs.ffs.doreallocblks=0 > >> > >> Is the correct response. > > > >Why isn't this currently the default if it's as pathological as you > >say? Has anyone actually asked David this question? It would be > >only courteous given that he's the author of this bug/feature. > > The feature is fairly important. Steve and one or two other people are > the only ones seeing the problem after Kirk's fix was committed. Steve is > the only person to report filesystem corruption caused by it. I'm not able > to reproduce the panic, despite doing more than 20 "make world"s in an > attempt to reproduce it. If we disable it by default then it will never get > fixed because there will be no feedback from people who are still having > problems with it. I WILL disable it prior to the 3.0.1 release if it isn't > fixed by then, however. Meanwhile I'll look at adding something that will > ensure that filesystem corruption isn't possible - I think this will amount > to detecting the problem and panicing earlier. I dont know If I'm one of the two, but it f*ks up here too, on ALL my machines, except on my notebook which uses softupdates. As has been stated before it has nothing to do with the machine being loaded, on the contrary, here it dies when the machine is idle and mail arrives or some such. I recommend that it should be disabled NOW, instead of hosing our users, its not "important" when it doesn't work... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 01:03:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19947 for freebsd-current-outgoing; Thu, 3 Dec 1998 01:03:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19942 for ; Thu, 3 Dec 1998 01:03:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA06089 for ; Thu, 3 Dec 1998 19:32:42 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA00598; Thu, 3 Dec 1998 19:32:42 +1030 (CST) Message-ID: <19981203193242.A441@freebie.lemis.com> Date: Thu, 3 Dec 1998 19:32:42 +1030 From: Greg Lehey To: FreeBSD current users Subject: Anybody having problems with Kernel PPP? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just run into a strange problem after rebooting (but without changing *any* software; the reboot was for disk reconfiguration). After the reboot, I couldn't establish contact with my ISP via kernel PPP: it dropped the line before it had finished dialling. Has anybody else seen this? I don't have time to look at it now, but I'll look again tomorrow. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 02:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24548 for freebsd-current-outgoing; Thu, 3 Dec 1998 02:13:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-27-dbn.dial-up.net [196.34.155.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24540 for ; Thu, 3 Dec 1998 02:13:05 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA14987; Thu, 3 Dec 1998 11:58:15 +0200 (SAT) From: Robert Nordier Message-Id: <199812030958.LAA14987@ceia.nordier.com> Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-Reply-To: <10151.912646644@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 98 04:57:24 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 3 Dec 1998 11:58:13 +0200 (SAT) Cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > What I did...Booted from the CD and selected slice 2 (which > > was empty) to install to. Using the disk label editor I created > > Which won't work. The FreeBSD boot loader, at least last I checked, > is too stupid to know that there might be more than one FreeBSD slice > on the disk and it just stops at the first one it finds. If you want > to run different versions of FreeBSD on the same box, they at least > need to reside on physically different drives. This is correct for the old (/sys/i386/boot/biosboot) boot blocks. However, the new (/sys/boot/i386/boot2) boot blocks specifically provide for booting from any slice. You can have four FreeBSD slices per disk, and pressing F4 will boot from slice 4, not from slice 1. The new boot blocks also allow you to override the slice using the extended syntax wd(0,2,a) where "2" means slice 2, though this is presently undocumented. The new boot blocks attempt to pass control to "/boot/loader" by default; but this can be overridden by specifying "/kernel" in /boot.config. They will also revert to loading "/kernel" if "/boot/loader" isn't found. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 02:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24918 for freebsd-current-outgoing; Thu, 3 Dec 1998 02:16:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24866 for ; Thu, 3 Dec 1998 02:15:58 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id MAA03256; Thu, 3 Dec 1998 12:15:18 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id MAA05095; Thu, 3 Dec 1998 12:15:22 +0200 (EET) (envelope-from vallo) Message-ID: <19981203121522.A4900@matti.ee> Date: Thu, 3 Dec 1998 12:15:22 +0200 From: Vallo Kallaste To: "Robert V. Baron" Cc: freebsd-current@FreeBSD.ORG Subject: Re: CODA on FreeBSD-CURRENT ... an interesting vm bug Reply-To: vallo@matti.ee References: <4.1.19981123122653.00abfe40@206.25.93.69> <19981125142249.B38959@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Robert V. Baron on Wed, Dec 02, 1998 at 10:23:01AM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Robert V. Baron" wrote: > Well, the bug is not that interesting ... > > I tried cvsup into coda on a 11/05 kernel. Doing cvsup'ing src > worked, but then I switched the tag from RELENG_2_2 to . and > the system crashed ... > What is happening here is that coda_rdwr does a VFS_VGET to get a > vnode the hardway. The vnode comes back locked (probably thru vget) > and is locked by the process "curproc" (cvsup in this case). But > coda_rdwr needs to unlock the vnode. It gets its process pointer > from the uio_procp field of the uio argument. Well > vnode_pager_input_old sets this field to 0 ... not curproc! Thus > the unlock fails with the panic above. > > moral: vnode_pager_input_old gets called in a process context so it > should use curproc not 0 as its procp. > > I fixed a different coda/related bug in vnode_pager_input_coda > earlier, so if there are no major objections I will commit this > change Fri noon. With the earlier bug (look in the "current" archives > for vnode_pager_input_old around Sep 28.), I determined that only > coda used vnode_pager_input_old, so I don't expect this change to > effect anyone besides Coda. Well, though I don't have enough knowledge to understand what exactly you meant, I'm glad to see that someone is actively working on coda. I'm actually an newcomer to coda but as far I can understand it looks very promising. Especially after having good client side on different variants of Windows(9x|NT). I'm trying to push our sysadmin into coda world but he is quite conservative 8-) and uses Linux. Well, that doesn't matter. Thanks Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 02:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25478 for freebsd-current-outgoing; Thu, 3 Dec 1998 02:24:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-27-dbn.dial-up.net [196.34.155.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25447 for ; Thu, 3 Dec 1998 02:23:53 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA15238; Thu, 3 Dec 1998 12:20:40 +0200 (SAT) From: Robert Nordier Message-Id: <199812031020.MAA15238@ceia.nordier.com> Subject: Re: ELF documentation In-Reply-To: from Chuck Robey at "Dec 2, 98 08:47:52 pm" To: chuckr@mat.net (Chuck Robey) Date: Thu, 3 Dec 1998 12:20:37 +0200 (SAT) Cc: richard@cogsci.ed.ac.uk, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Thu, 3 Dec 1998, Richard Tobin wrote: > > > Where can I find documentation of the new ELF executable file format? > > What I want is the ELF equivalent of "man 5 a.out", but it doesn't > > seem to exist. > > That works fine here. Maybe your manpath.config is all messed up? There's an elf(5) man page? > > > > > I'm trying to convert programs that load in .o files and write themselves > > out as new executables (lisp and prolog systems). You can pick up a copy of the ELF specification, as part of the Tool Interface Standards, at ftp://ftp.intel.com/pub/tis/elf11g.zip -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 02:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25665 for freebsd-current-outgoing; Thu, 3 Dec 1998 02:26:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25660 for ; Thu, 3 Dec 1998 02:26:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA15181; Thu, 3 Dec 1998 02:25:51 -0800 (PST) To: Robert Nordier cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-reply-to: Your message of "Sat, 03 Dec 1998 11:58:13 +0200." <199812030958.LAA14987@ceia.nordier.com> Date: Thu, 03 Dec 1998 02:25:51 -0800 Message-ID: <15177.912680751@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, the new (/sys/boot/i386/boot2) boot blocks specifically > provide for booting from any slice. You can have four FreeBSD > slices per disk, and pressing F4 will boot from slice 4, not from > slice 1. Cool, I stand most happily corrected! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 03:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28831 for freebsd-current-outgoing; Thu, 3 Dec 1998 03:21:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-21-dbn.dial-up.net [196.34.155.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28807 for ; Thu, 3 Dec 1998 03:21:12 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA15654; Thu, 3 Dec 1998 13:14:00 +0200 (SAT) From: Robert Nordier Message-Id: <199812031114.NAA15654@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <86g1ay6l8f.fsf@detlev.UUCP> from Joel Ray Holveck at "Dec 2, 98 07:57:20 pm" To: joelh@gnu.org (Joel Ray Holveck) Date: Thu, 3 Dec 1998 13:13:48 +0200 (SAT) Cc: mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, rnordier@nordier.com, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > Mike said: > > Yes, we have been over this before. Would you care to explain how you > > plan to reinstate the vectors that the DOS7 kernel replaces so that > > vm86 BIOS calls from the FreeBSD kernel will work? > > Please understand that there are some really fundamental issues which > > absolutely preclude starting FreeBSD once DOS has been started. > > We may have a different definition of "DOS7 kernel". I typically use > that phrase to refer to IO.SYS alone. The vectors seem to be modified > by HIMEM.SYS instead. By default, IO.SYS will load HIMEM.SYS and > prevent the kernel from loading. However, the line "DOS=NOAUTO" in > the config.sys will cause IO.SYS to skip that step. I have had > success loading FreeBSD by using that line in the PIF's specified > CONFIG.SYS myself. As you go on to describe, it is *not* particularly difficult to boot FreeBSD straight out of Windows. However, the reason we don't want to actively support this is that it makes the kernel vm86 mechanism unreliable. The choice is really a simple xor: o Boot out of Windows o Reliable kernel vm86 support I researched the whole issue in really exhaustive detail, a year or so ago, before off-list discussions with Mike Smith, which led to the decision not to support any kind of FBSDBOOT approach in the new boot code project. What we can support with little trouble (if any Windows programmer wants to step forward to do the actual Windows coding) is the following completely safe method: In Windows, have a FreeBSD control panel which allows you to point and click on FreeBSD slice, and set any of the standard boot block options like -s (single user) or -v (verbose). When the user clicks "Go" (or whatever), the Windows application communicates with the boot manager through an API, then does a cold boot. The partition manager gets control, and passes the selected parameters to the boot blocks, which may also pass them on to /boot/loader, as required. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 03:27:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29264 for freebsd-current-outgoing; Thu, 3 Dec 1998 03:27:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29256 for ; Thu, 3 Dec 1998 03:27:52 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id FAA05254; Thu, 3 Dec 1998 05:27:18 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Thu, 3 Dec 1998 05:27:18 -0600 (CST) From: Richard Wackerbarth To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: feature requests for install In-Reply-To: <199812030501.AAA03579@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Mikhail Teterin wrote: > > 1) Dhcp-client support at install time. > > 2) Socks5-client support. > > Those installing on corporate networks or over increasingly popular > cable-modems will be a lot happier... > > Where are my patches?.. The first step is to "contrib"-ify the dhcp client. If someone will make the initial commit of the source, I will be glad to supply some patches to get it going from there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 04:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06423 for freebsd-current-outgoing; Thu, 3 Dec 1998 04:39:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay01.esat.net (relay01.esat.net [192.111.39.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06413 for ; Thu, 3 Dec 1998 04:38:56 -0800 (PST) (envelope-from nialls@euristix.ie) Received: from (euristix.ie) [193.120.210.2] by relay01.esat.net with esmtp id 0zlY1M-0003rl-00; Thu, 3 Dec 1998 12:38:13 +0000 Received: by gateway.euristix.ie id <19713>; Thu, 3 Dec 1998 12:36:30 +0000 Message-Id: <98Dec3.123630gmt.19713@gateway.euristix.ie> Date: Thu, 3 Dec 1998 12:35:34 +0000 From: Niall Smart X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: patches@cygnus.com CC: current@FreeBSD.ORG Subject: egcs' config.guess on FreeBSD ELF systems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Cc'd to current@freebsd.org for any comments ] The config.guess script does not properly detect ELF vs. a.out for FreeBSD leading to build failure on an ELF system unless the host is explicitly specified as *-*-freebsdelf during configuration. The appended patch remedies this. Regards, Niall *** config.guess~ Thu Dec 3 12:19:41 1998 --- config.guess Thu Dec 3 12:25:13 1998 *************** *** 483,489 **** echo ${UNAME_MACHINE}-pc-bsdi${UNAME_RELEASE} exit 0 ;; *:FreeBSD:*:*) ! echo ${UNAME_MACHINE}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` exit 0 ;; *:NetBSD:*:*) echo ${UNAME_MACHINE}-unknown-netbsd`echo ${UNAME_RELEASE}|sed -e 's/[-_].*/\./'` --- 483,493 ---- echo ${UNAME_MACHINE}-pc-bsdi${UNAME_RELEASE} exit 0 ;; *:FreeBSD:*:*) ! if test -x /usr/bin/objformat -a "elf" = "`/usr/bin/objformat`"; then ! echo ${UNAME_MACHINE}-unknown-freebsdelf ! else ! echo ${UNAME_MACHINE}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-_].*//'` ! fi exit 0 ;; *:NetBSD:*:*) echo ${UNAME_MACHINE}-unknown-netbsd`echo ${UNAME_RELEASE}|sed -e 's/[-_].*/\./'` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 05:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08307 for freebsd-current-outgoing; Thu, 3 Dec 1998 05:16:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08302 for ; Thu, 3 Dec 1998 05:16:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id FAA22570; Thu, 3 Dec 1998 05:15:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812031315.FAA22570@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com cc: "Jordan K. Hubbard" , Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Wed, 02 Dec 1998 23:59:49 PST." <199812030759.XAA17756@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 05:15:17 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't had a panic here in weeks and both of my machines are running 3.0-current as of last sunday. rah is a ppro 200mhz and uses primarily scsi disks and cioloco is a p200 mmx which only has ide drives. Both systems have done extensive compiles including make worlds. Both systems are running with soft updates enabled. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 05:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10279 for freebsd-current-outgoing; Thu, 3 Dec 1998 05:47:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10274 for ; Thu, 3 Dec 1998 05:46:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id FAA22883 for ; Thu, 3 Dec 1998 05:46:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812031346.FAA22883@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: nlpt and severe system slow down Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 05:46:38 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my config for nlpt: controller ppbus0 controller ppc0 at isa? irq 7 vector ppcintr device nlpt0 at ppbus? If I shutdown my laser jet 4mp while printing, my system comes to crawl for instance my mouse and keyboard don't respond. The system is not quite dead because I can see that the cursor moves or rather jumps sporadically on my X desktop Has anyone else seeng this behavior? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 06:00:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10855 for freebsd-current-outgoing; Thu, 3 Dec 1998 06:00:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA10848 for ; Thu, 3 Dec 1998 06:00:30 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 12391 invoked by uid 1001); 3 Dec 1998 14:00:09 +0000 (GMT) To: dg@root.com Cc: jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: Your message of "Wed, 02 Dec 1998 23:59:49 -0800" References: <199812030759.XAA17756@root.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 03 Dec 1998 15:00:09 +0100 Message-ID: <12389.912693609@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The feature is fairly important. Steve and one or two other people are > the only ones seeing the problem after Kirk's fix was committed. I'm seeing it consistently here, on a PII-400 SMP system running 3.0-19981123-SNAP (which has vfs_cluster.c 1.74). No softupdates. Setting vfs.ffs.doreallocblks to 0 made the problem disappear. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 06:18:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12411 for freebsd-current-outgoing; Thu, 3 Dec 1998 06:18:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from easeway.com (ns1.easeway.com [209.69.71.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12406 for ; Thu, 3 Dec 1998 06:18:16 -0800 (PST) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id JAA20292; Thu, 3 Dec 1998 09:01:04 -0500 (EST) Message-Id: <199812031401.JAA20292@easeway.com> Subject: Re: Anybody having problems with Kernel PPP? In-Reply-To: <19981203193242.A441@freebie.lemis.com> from Greg Lehey at "Dec 3, 98 07:32:42 pm" To: grog@lemis.com (Greg Lehey) Date: Thu, 3 Dec 1998 09:01:04 -0500 (EST) Cc: FreeBSD-current@FreeBSD.ORG From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this problem on a week-old kernel. My two-week-old kernel dialed out just fine. I booted the older kernel, resupped yesterday, rebuilt, and can dial out 90% of the time just fine. Since I'm one of "the kind of -current users" that Jordan just mentioned, I didn't post the problem; generally, a resup solves the problem of the day anyway. I still have the broken kernel, if anyone has use for it or wants me to run any debugging. ==ml > I've just run into a strange problem after rebooting (but without > changing *any* software; the reboot was for disk reconfiguration). > After the reboot, I couldn't establish contact with my ISP via kernel > PPP: it dropped the line before it had finished dialling. Has anybody > else seen this? I don't have time to look at it now, but I'll look > again tomorrow. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 06:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12642 for freebsd-current-outgoing; Thu, 3 Dec 1998 06:18:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sawmill.grauel.com (sawmill.grauel.com [199.233.104.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12636 for ; Thu, 3 Dec 1998 06:18:30 -0800 (PST) (envelope-from rjk@sawmill.grauel.com) Received: (from rjk@localhost) by sawmill.grauel.com (8.8.8/8.8.7) id JAA25411; Thu, 3 Dec 1998 09:19:12 -0500 (EST) From: "Richard J. Kuhns" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13926.40416.596095.477350@sawmill.grauel.com> Date: Thu, 3 Dec 1998 09:19:12 -0500 (EST) To: Randall Hopper Cc: current@FreeBSD.ORG Subject: Bugs/features w/ "ldconfig" (3.0-RELEASE) In-Reply-To: <19981202185633.A868@pagesz.net> References: <19981129102800.A1657@pagesz.net> <19981202185633.A868@pagesz.net> X-Mailer: VM 6.56 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to help John with documentation for the ELF stuff, so I'll make a couple of comments... Randall Hopper writes: > 1) You can completely re-initialize the LD path for ELF, but not for AOUT. > ... > ... > It seems that ldconfig won't let you remove /usr/lib/aout. Why? > > =============================================================================== Well, ldconfig is documented to always include the standard search directories (/usr/lib or /usr/lib/aout) unless you tell it not to (via `-s'), so it looks like the bug is in the -elf part. > 2) In /etc/rc.conf, we have: > > $ldconfig_paths & $ldconfig_paths_aout > > but we also have: > > /etc/ld.so.conf & /etc/ld-elf.so.conf > > (as documented in the ldconfig(8) man page) as places to store LD paths. > So: > > a) Which should be used? > b) What arguments cause "ldconfig" to read the /etc/ld*.so.conf files? > > It would make sense to have one place to store this information. > It'd also be useful to have simple ldconfig arguments that re-read this > information, wherever it is stored (something like "ldconfig -i"). > Pretend you've never seen /etc/ld*.so.conf; it should never have been mentioned, has nothing to do with ldconfig, and the man page will be updated soon. > and a few questions: > > 3) Why aren't these two directories in the default $ldconfig_paths_aout (AOUT) > in /etc/rc.conf? AFAIK, they're all AOUT: > > /usr/lib/aout /usr/lib/compat > I don't know about /usr/lib/compat, but as you noticed in 1) above, /usr/lib/aout is always there unless you specifically ask for it not to be. > 4) Why is this directory in the default $ldconfig_paths (ELF)? It's all AOUT: > > /usr/lib/compat > No idea. > > I'd appreciate any insights. Should the defs in /etc/rc.conf possibly be > changed to: > > ldconfig_paths="`cat /etc/ld-elf.so.conf`" > ldconfig_paths_aout="`cat /etc/ld.so.conf`" > See the answer to 2). -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16651 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:13:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16646 for ; Thu, 3 Dec 1998 07:13:52 -0800 (PST) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id JAA18762 for freebsd-current@freebsd.org; Thu, 3 Dec 1998 09:13:32 -0600 (CST) Date: Thu, 3 Dec 1998 09:13:32 -0600 (CST) From: Mark Tinguely Message-Id: <199812031513.JAA18762@plains.NoDak.edu> To: freebsd-current@FreeBSD.ORG Subject: 3.0 and double operations in device drivers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was testing a device driver that I wrote for FreeBSD 2.2.x on a FreeBSD 3.0-RELEASE. When some double multiplication and divisions were executed, the system froze. It took a long time to find it was a FP problem, it acted like some aweful infinite loop. These routines are only used on a circuit setup to calculate some scheduling parameters, and I guess they can be done with integer math after some head scratching. My question is: "Is floating point math now taboo in the kernel?" --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17186 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:23:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17179 for ; Thu, 3 Dec 1998 07:22:57 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id KAA28193; Thu, 3 Dec 1998 10:22:31 -0500 (EST) Date: Thu, 3 Dec 1998 10:22:31 -0500 (EST) Message-Id: <199812031522.KAA28193@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the problem: 1. You have a program that starts a few threads, one of these threads blocks in "accept()" waiting for a new connection on a file descriptor. 2. In another thread, you want to start a child program. After the fork(), but before exec(), you close() all the file descriptors you don't want the child to touch. 3. The child hangs in close() forever. Why? At fork(), you get a copy of all the fd's. Problem is, many of them have their file descriptors locked. --- Is there any solution to this? Perhaps the fork() code should unlock all the descriptors. Does this makes sense? Opening a PR now. -Rob rmf@highwind.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:27:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17491 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:27:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA17470 for ; Thu, 3 Dec 1998 07:26:52 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA05857; Thu, 3 Dec 1998 14:16:48 +0100 From: Luigi Rizzo Message-Id: <199812031316.OAA05857@labinfo.iet.unipi.it> Subject: Re: 3.0 and double operations in device drivers To: tinguely@plains.NoDak.edu (Mark Tinguely) Date: Thu, 3 Dec 1998 14:16:48 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199812031513.JAA18762@plains.NoDak.edu> from "Mark Tinguely" at Dec 3, 98 09:13:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My question is: "Is floating point math now taboo in the kernel?" it has always been! luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:52:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19237 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:48:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19225 for ; Thu, 3 Dec 1998 07:48:01 -0800 (PST) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id JAA05173; Thu, 3 Dec 1998 09:47:46 -0600 (CST) Date: Thu, 3 Dec 1998 09:47:46 -0600 (CST) From: Mark Tinguely Message-Id: <199812031547.JAA05173@plains.NoDak.edu> To: luigi@labinfo.iet.unipi.it, tinguely@plains.NoDak.edu Subject: Re: 3.0 and double operations in device drivers Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My question is: "Is floating point math now taboo in the kernel?" > > it has always been! I asked for that one :). remove taboo and replace with "forbidden". --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19828 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:53:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19819 for ; Thu, 3 Dec 1998 07:53:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id IAA61035; Thu, 3 Dec 1998 08:00:27 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812031600.IAA61035@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812031315.FAA22570@rah.star-gate.com> from Amancio Hasty at "Dec 3, 1998 5:15:17 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 3 Dec 1998 08:00:27 -0800 (PST) Cc: dg@root.com, jkh@zippy.cdrom.com, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Amancio Hasty: > I haven't had a panic here in weeks and both of my machines are running > 3.0-current as of last sunday. rah is a ppro 200mhz and uses primarily > scsi disks and cioloco is a p200 mmx which only has ide drives. Both systems > have done extensive compiles including make worlds. Both systems are running > with soft updates enabled. > Disable soft updates, and I'll wager that your machines will crash. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:58:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20209 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:58:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20203 for ; Thu, 3 Dec 1998 07:58:01 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA27821; Thu, 3 Dec 1998 10:57:15 -0500 (EST) (envelope-from wollman) Date: Thu, 3 Dec 1998 10:57:15 -0500 (EST) From: Garrett Wollman Message-Id: <199812031557.KAA27821@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Richard Wackerbarth , freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812030145.RAA02736@dingo.cdrom.com> References: <199812030145.RAA02736@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Cannot we unload all of the device recognition code once it has done its >> job and reload it each time the PCCARD finds a new arrival? > What "device recognition code"? If we keep the current model, it's all > in a user-space application. The current model is totally broken and doesn't work like anyone else's PC-Card implementation anywhere. This Is Bad since it makes drivers much harder to port than they need to be. > If we were to move the CIS ID : driver/rules match code into the > kernel, it would be so small and trivial that the effort involved in > loading/unloading it would be disproportionate to the space regained > (maybe 1 page). Under the new bus architecture (and also the standard Card Services model), the correct thing is to let each candidate driver look at the CIS and see whether it can handle the device -- for a simple driver, probably about 100 bytes. To put this on a page by itself so that it could be unloaded would waste most of a page. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 07:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20257 for freebsd-current-outgoing; Thu, 3 Dec 1998 07:58:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20218 for ; Thu, 3 Dec 1998 07:58:03 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA03284; Thu, 3 Dec 1998 16:57:48 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA21676; Thu, 3 Dec 1998 16:57:47 +0100 (MET) Message-ID: <19981203165746.J18661@follo.net> Date: Thu, 3 Dec 1998 16:57:46 +0100 From: Eivind Eklund To: Mark Tinguely , luigi@labinfo.iet.unipi.it Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers References: <199812031547.JAA05173@plains.NoDak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812031547.JAA05173@plains.NoDak.edu>; from Mark Tinguely on Thu, Dec 03, 1998 at 09:47:46AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 09:47:46AM -0600, Mark Tinguely wrote: > > > My question is: "Is floating point math now taboo in the kernel?" > > > > it has always been! > > I asked for that one :). remove taboo and replace with "forbidden". It always has been. (Ie, it has never worked reliably, and this has been a known property of the design). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 08:10:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21200 for freebsd-current-outgoing; Thu, 3 Dec 1998 08:10:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21193 for ; Thu, 3 Dec 1998 08:10:07 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id LAA06706 for current@freebsd.org; Thu, 3 Dec 1998 11:09:35 -0500 (EST) From: Mikhail Teterin Message-Id: <199812031609.LAA06706@kot.ne.mediaone.net> Subject: firmware loading (was KLD - what's the idea) In-Reply-To: from "Matthew N. Dodd" at "Dec 3, 1998 00:44:10 am" To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 3 Dec 1998 11:09:05 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21495 for freebsd-current-outgoing; Thu, 3 Dec 1998 08:14:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21490 for ; Thu, 3 Dec 1998 08:14:55 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA30390 for ; Thu, 3 Dec 1998 16:14:41 GMT Message-ID: <3666B8F0.60874AC4@tdx.co.uk> Date: Thu, 03 Dec 1998 16:14:40 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size References: <199812031600.IAA61035@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > > According to Amancio Hasty: > > I haven't had a panic here in weeks and both of my machines are running > > 3.0-current as of last sunday. rah is a ppro 200mhz and uses primarily > > scsi disks and cioloco is a p200 mmx which only has ide drives. Both systems > > have done extensive compiles including make worlds. Both systems are running > > with soft updates enabled. > > > > Disable soft updates, and I'll wager that your machines will crash. Both my Single PPro 200 & Dual PPro 200's are runing -current (couple of days old build from last Saturday I think), both work fine (even under duress)... Both aren't running softupdates... ? -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 08:23:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22500 for freebsd-current-outgoing; Thu, 3 Dec 1998 08:23:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22492 for ; Thu, 3 Dec 1998 08:23:21 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id IAA61143; Thu, 3 Dec 1998 08:30:59 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812031630.IAA61143@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <3666B8F0.60874AC4@tdx.co.uk> from Karl Pielorz at "Dec 3, 1998 4:14:40 pm" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Thu, 3 Dec 1998 08:30:59 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Karl Pielorz: > > > Steve Kargl wrote: > > > > According to Amancio Hasty: > > > I haven't had a panic here in weeks and both of my machines are running > > > 3.0-current as of last sunday. rah is a ppro 200mhz and uses primarily > > > scsi disks and cioloco is a p200 mmx which only has ide drives. Both systems > > > have done extensive compiles including make worlds. Both systems are running > > > with soft updates enabled. > > > > > > > Disable soft updates, and I'll wager that your machines will crash. ^ eventually > > Both my Single PPro 200 & Dual PPro 200's are runing -current (couple of days > old build from last Saturday I think), both work fine (even under duress)... > Both aren't running softupdates... ? > Then, count your blessings and make good backups. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 09:01:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26218 for freebsd-current-outgoing; Thu, 3 Dec 1998 09:01:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.wavefront.com (ns.wavefront.com [204.73.244.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA26210 for ; Thu, 3 Dec 1998 09:01:32 -0800 (PST) (envelope-from caa@wavefront.com) Received: by mail.wavefront.com (8.6.10/SMI-4.1.R931202) id LAA05465; Thu, 3 Dec 1998 11:07:26 -0600 From: caa@wavefront.com (Charles Anderson) Message-Id: <199812031707.LAA05465@mail.wavefront.com> Subject: sysctl portrange question To: freebsd-current@FreeBSD.ORG (-current mailing list) Date: Thu, 3 Dec 1998 11:07:26 -0600 (CST) Reply-To: caa@wavefront.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this right? bash-2.02# sysctl -a | grep portrange net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 lowfirst > lowlast? -Charlie -- Charles Anderson - caa@wavefront.com -finger for PGP public key Disclaimer: They tell me disclaimers are useless, so here's mine: thhhppt... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 09:36:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29985 for freebsd-current-outgoing; Thu, 3 Dec 1998 09:36:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29978 for ; Thu, 3 Dec 1998 09:36:28 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id MAA01016; Thu, 3 Dec 1998 12:35:30 -0500 (EST) Date: Thu, 3 Dec 1998 12:35:30 -0500 (EST) Message-Id: <199812031735.MAA01016@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG In-reply-to: <199812031522.KAA28193@highwind.com> (message from HighWind Software Information on Thu, 3 Dec 1998 10:22:31 -0500 (EST)) Subject: Re: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there any solution to this? Perhaps the fork() code should unlock >all the descriptors. In looking at my own suggestion... fork() in libc_r currently removes all but the running thread from the thread list. Here's my problem, don't all the fd's have a queue of pointers back to those thread structures in their r_queue and w_queue members? Don't those need to be all cleaned up ANYWAY?? Despite my reporting of this bug. I think, fork() needs to: Continue to remove all threads but the running thread from the thread list, then go over the fd's and unlock and cleanup all queues. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 09:44:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00694 for freebsd-current-outgoing; Thu, 3 Dec 1998 09:44:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1001.mpoweredpc.net [142.177.191.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00687 for ; Thu, 3 Dec 1998 09:44:37 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id NAA21084 for ; Thu, 3 Dec 1998 13:44:15 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 3 Dec 1998 13:44:15 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: syslogd@hub messages being broadcast... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This messsage is so informative, I hate to ask, but... :) Message from syslogd@hub at Thu Dec 3 11:46:06 1998 ... hub /kernel: What is this trying to tell me? :( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 09:53:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01473 for freebsd-current-outgoing; Thu, 3 Dec 1998 09:53:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (39-sweet.camalott.com [208.239.153.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01450 for ; Thu, 3 Dec 1998 09:53:15 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id LAA07708; Thu, 3 Dec 1998 11:52:48 -0600 (CST) (envelope-from joelh) To: Robert Nordier Cc: mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <199812031114.NAA15654@ceia.nordier.com> From: Joel Ray Holveck Date: 03 Dec 1998 11:52:47 -0600 In-Reply-To: Robert Nordier's message of "Thu, 3 Dec 1998 13:13:48 +0200 (SAT)" Message-ID: <86btllqfio.fsf@detlev.UUCP> Lines: 66 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Yes, we have been over this before. Would you care to explain how you >>> plan to reinstate the vectors that the DOS7 kernel replaces so that >>> vm86 BIOS calls from the FreeBSD kernel will work? >>> Please understand that there are some really fundamental issues which >>> absolutely preclude starting FreeBSD once DOS has been started. >> We may have a different definition of "DOS7 kernel". I typically use >> that phrase to refer to IO.SYS alone. The vectors seem to be modified >> by HIMEM.SYS instead. By default, IO.SYS will load HIMEM.SYS and >> prevent the kernel from loading. However, the line "DOS=NOAUTO" in >> the config.sys will cause IO.SYS to skip that step. I have had >> success loading FreeBSD by using that line in the PIF's specified >> CONFIG.SYS myself. > As you go on to describe, it is *not* particularly difficult to > boot FreeBSD straight out of Windows. I want to make one point clear: the process *does* have an intervening reboot between when Windows is loaded and when FreeBSD is loaded. > However, the reason we don't want to actively support this is that > it makes the kernel vm86 mechanism unreliable. Interesting. I had vm86 problems using the system before adding NOAUTO, but since then, I've been using it fine. I'm not saying it would work for everybody, just that I don't have enough information to find where it fails, which is something I'm interested in. Which vector is in question? I thought it was 15h, but when I looked, that was apparently still mapped to the BIOS just before FBSDBOOT is loaded. > I researched the whole issue in really exhaustive detail, a year > or so ago, before off-list discussions with Mike Smith, which led > to the decision not to support any kind of FBSDBOOT approach in > the new boot code project. Okay. I'm still curious about your findings. Did you write up anything on it? > What we can support with little trouble (if any Windows programmer > wants to step forward to do the actual Windows coding) is the following > completely safe method: > In Windows, have a FreeBSD control panel which allows you to > point and click on FreeBSD slice, and set any of the standard > boot block options like -s (single user) or -v (verbose). When > the user clicks "Go" (or whatever), the Windows application > communicates with the boot manager through an API, then does > a cold boot. The partition manager gets control, and passes > the selected parameters to the boot blocks, which may also pass > them on to /boot/loader, as required. Sounds like a good thing to do. Does the nextboot API still work? How can I test this? If there is some sort of problem and the vectors in question are not reset to the BIOS, it apparently doesn't seem to affect my normal operations. Is there something I can check, or some procedure which would regularly fail, so I can know if it doesn't work? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 10:20:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03947 for freebsd-current-outgoing; Thu, 3 Dec 1998 10:20:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thorin.hway.ru (thorin.hway.ru [195.170.38.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03868 for ; Thu, 3 Dec 1998 10:19:56 -0800 (PST) (envelope-from flash@intech.hway.ru) Received: from balin.intech.hway.ru (balin.intech.hway.ru [192.168.1.25]) by thorin.hway.ru (8.9.1/8.9.1) with ESMTP id VAA24976; Thu, 3 Dec 1998 21:18:07 +0300 (MSK) Received: from localhost (flash@localhost) by balin.intech.hway.ru (8.8.8/8.8.8) with SMTP id VAA19097; Thu, 3 Dec 1998 21:18:06 +0300 (MSK) Date: Thu, 3 Dec 1998 21:18:06 +0300 (MSK) From: "Alexander V. Tischenko" To: Charles Anderson cc: -current mailing list Subject: Re: sysctl portrange question In-Reply-To: <199812031707.LAA05465@mail.wavefront.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, port selections are implemented in opposite directions to minimize possible clash. On Thu, 3 Dec 1998, Charles Anderson wrote: > Is this right? > > bash-2.02# sysctl -a | grep portrange > net.inet.ip.portrange.lowfirst: 1023 > net.inet.ip.portrange.lowlast: 600 > net.inet.ip.portrange.first: 1024 > net.inet.ip.portrange.last: 5000 > net.inet.ip.portrange.hifirst: 49152 > net.inet.ip.portrange.hilast: 65535 > > lowfirst > lowlast? > > -Charlie > -- > Charles Anderson - caa@wavefront.com -finger for PGP public key > > Disclaimer: They tell me disclaimers are useless, so here's mine: thhhppt... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alexander V. Tischenko ------------------------------------------------------------------------------ Integrated Network Technologies | Tel: +7 095 978-47-37 7, Miusskaya sq., Moscow, 125047 Russia | Fax: +7 095 978-47-37 Internet: flash@hway.ru | NIC: AT55-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 10:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06110 for freebsd-current-outgoing; Thu, 3 Dec 1998 10:39:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from under.suspicion.org (UNDER.SUSPICION.ORG [216.27.37.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06094 for ; Thu, 3 Dec 1998 10:39:51 -0800 (PST) (envelope-from ventrex@UNDER.suspicion.org) Received: from UNDER.SUSPICION.ORG (root@UNDER.SUSPICION.ORG [216.27.37.14]) by under.suspicion.org (8.9.1/8.9.1) with ESMTP id NAA05064; Thu, 3 Dec 1998 13:39:08 -0500 (EST) (envelope-from ventrex@UNDER.suspicion.org) Date: Thu, 3 Dec 1998 13:39:05 -0500 (EST) From: Thomas Stromberg X-Sender: ventrex@under.suspicion.org To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: syslogd@hub messages being broadcast... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I usually see that when swap is about to completely fill up and the system is on it's way to a downward load/swap spiral. ======================================================================== Thomas Stromberg | smtp -> thomas@stromberg.org System Administrator, RTC Inc. | http -> thomas.stromberg.org Cary, NC. : talk -> ventrex@stromberg.org (919) 380-9771 ext. 3210 : icq -> 17468041/ventrex "the more we know, the less we are" . irc -> ventrex@EFnet ======================================================================== On Thu, 3 Dec 1998, The Hermit Hacker wrote: > > This messsage is so informative, I hate to ask, but... :) > > Message from syslogd@hub at Thu Dec 3 11:46:06 1998 ... > hub /kernel: > > What is this trying to tell me? :( > > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 10:39:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06128 for freebsd-current-outgoing; Thu, 3 Dec 1998 10:39:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06101 for ; Thu, 3 Dec 1998 10:39:52 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id NAA01466; Thu, 3 Dec 1998 13:39:27 -0500 (EST) Date: Thu, 3 Dec 1998 13:39:27 -0500 (EST) Message-Id: <199812031839.NAA01466@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Re: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Again.. having a conversation with myself: Wouldn't inserting this code in uthread_fork.c at line 122 fix this problem? /* * Enter a loop to remove all locks on all locked fd's */ for (i = 0; i < _thread_dtablesize; i++) { if (_thread_fd_table[i] != NULL) { memset(&_thread_fd_table[i]->lock, 0, sizeof(_thread_fd_table[i]->lock)); _thread_fd_table[i]->r_owner = NULL; _thread_fd_table[i]->w_owner = NULL; _thread_fd_table[i]->r_fname = NULL; _thread_fd_table[i]->w_fname = NULL; _thread_fd_table[i]->r_lineno = 0;; _thread_fd_table[i]->w_lineno = 0;; _thread_fd_table[i]->r_lockcount = 0; _thread_fd_table[i]->w_lockcount = 0; /* Initialise the read/write queues: */ _thread_queue_init(&_thread_fd_table[i]->r_queue); _thread_queue_init(&_thread_fd_table[i]->w_queue); } } We know we are in the child, we know we are the only active thread, we know we don't have any fd's locked and we just nuked all the other threads. So, just go to the fd table and nuke any and all locks. I'm going to give this a try, but, would appreciate if someone gave me some comments. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 11:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09263 for freebsd-current-outgoing; Thu, 3 Dec 1998 11:08:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09172 for ; Thu, 3 Dec 1998 11:08:00 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id UAA00877 for current@freebsd.org; Thu, 3 Dec 1998 20:07:44 +0100 (CET) Message-ID: <19981203200743.A861@cons.org> Date: Thu, 3 Dec 1998 20:07:43 +0100 From: Martin Cracauer To: current@FreeBSD.ORG Subject: Proposed addition to fetch(1) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=gBBFr7Ir9EOA20Yy X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii I plan to add this to fetch, unless anyone objects. -s Ask server for size of file in bytes and print it to stdout. Do not actually fetch the file. Actual diff appended. I plan to use it for a `make fetchsize` target for ports, so that you can ask how much traffic you would cause before actually starting the fetch. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="fetch.diff" ? fetch ? fetch.1.gz ? l ? .gdbinit ? ktrace.out ? shc ? README Index: fetch.1 =================================================================== RCS file: /home/CVS-FreeBSD/src/usr.bin/fetch/fetch.1,v retrieving revision 1.25 diff -c -r1.25 fetch.1 *** fetch.1 1998/11/08 23:18:47 1.25 --- fetch.1 1998/12/03 19:04:35 *************** *** 115,120 **** --- 115,123 ---- .Nm fetch from downloading a file that is either incomplete or the wrong version, given the correct size of the file in advance. + .It Fl s + Ask server for size of file in bytes and print it to stdout. Do not + actually fetch the file. .It Fl T Ar seconds Set timeout value to .Ar seconds. Index: fetch.h =================================================================== RCS file: /home/CVS-FreeBSD/src/usr.bin/fetch/fetch.h,v retrieving revision 1.6 diff -c -r1.6 fetch.h *** fetch.h 1998/09/20 00:01:26 1.6 --- fetch.h 1998/12/03 19:04:35 *************** *** 52,57 **** --- 52,58 ---- int fs_linux_bug; /* -b option */ int fs_use_connect; /* -t option */ off_t fs_expectedsize; /* -S option */ + int fs_reportsize; /* -s option */ time_t fs_modtime; void *fs_proto; int (*fs_retrieve)(struct fetch_state *); Index: ftp.c =================================================================== RCS file: /home/CVS-FreeBSD/src/usr.bin/fetch/ftp.c,v retrieving revision 1.10 diff -c -r1.10 ftp.c *** ftp.c 1998/09/20 00:01:26 1.10 --- ftp.c 1998/12/03 19:04:35 *************** *** 375,380 **** --- 375,394 ---- } } size = ftpGetSize(ftp, ftps->ftp_remote_file); + + if (fs->fs_reportsize) { + fclose(ftp); + if (size == -1) { + warnx("%s: size not known\n", fs->fs_outputfile); + printf("Unknown\n"); + return 1; + } + else { + printf("%qd\n", (quad_t)size); + return 0; + } + } + if (size > 0 && fs->fs_expectedsize != -1 && size != fs->fs_expectedsize) { warnx("%s: size mismatch, expected=%lu / actual=%lu", ftps->ftp_remote_path, Index: http.c =================================================================== RCS file: /home/CVS-FreeBSD/src/usr.bin/fetch/http.c,v retrieving revision 1.21 diff -c -r1.21 http.c *** http.c 1998/10/26 02:39:21 1.21 --- http.c 1998/12/03 19:04:35 *************** *** 945,950 **** --- 945,967 ---- fs->fs_status = "retrieving file from HTTP/1.x server"; + if (fs->fs_reportsize) { + if (total_length == -1) { + warnx("%s: size not known\n", + fs->fs_outputfile); + printf("Unknown\n"); + status = 1; + } + else { + printf("%qd\n", (quad_t)total_length); + status = 0; + } + fclose(remote); + unsetup_sigalrm(); + return status; + } + + /* * OK, if we got here, then we have finished parsing the header * and have read the `\r\n' line which denotes the end of same. Index: main.c =================================================================== RCS file: /home/CVS-FreeBSD/src/usr.bin/fetch/main.c,v retrieving revision 1.48 diff -c -r1.48 main.c *** main.c 1998/11/08 23:18:48 1.48 --- main.c 1998/12/03 19:04:36 *************** *** 71,80 **** init_schemes(); fs = clean_fetch_state; fs.fs_verbose = 1; fs.fs_expectedsize = -1; change_to_dir = file_to_get = hostname = 0; ! while ((c = getopt(argc, argv, "abc:D:f:h:HIlLmMnNo:pPqRrS:tT:vV:")) != -1) { switch (c) { case 'D': case 'H': case 'I': case 'L': case 'N': case 'V': break; /* ncftp compatibility */ --- 71,81 ---- init_schemes(); fs = clean_fetch_state; fs.fs_verbose = 1; + fs.fs_reportsize = 0; fs.fs_expectedsize = -1; change_to_dir = file_to_get = hostname = 0; ! while ((c = getopt(argc, argv, "abc:D:f:h:HIlLmMnNo:pPqRrSs:tT:vV:")) != -1) { switch (c) { case 'D': case 'H': case 'I': case 'L': case 'N': case 'V': break; /* ncftp compatibility */ *************** *** 133,138 **** --- 134,143 ---- case 't': fs.fs_use_connect = 1; + break; + + case 's': + fs.fs_reportsize = 1; break; case 'S': --gBBFr7Ir9EOA20Yy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 11:35:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12829 for freebsd-current-outgoing; Thu, 3 Dec 1998 11:35:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12821 for ; Thu, 3 Dec 1998 11:35:32 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA25276; Thu, 3 Dec 1998 11:35:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 3 Dec 1998 11:35:07 -0800 (PST) From: Doug White To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: syslogd@hub messages being broadcast... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, The Hermit Hacker wrote: > > This messsage is so informative, I hate to ask, but... :) > > Message from syslogd@hub at Thu Dec 3 11:46:06 1998 ... > hub /kernel: > > What is this trying to tell me? :( Something is logging at emerg priority, so either someone is having fun with logger or something is going badly wrong. My upsd is configured to log UPS events at such a priority; when the NeXTPrinter kicks on I start getting messages. :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 11:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14467 for freebsd-current-outgoing; Thu, 3 Dec 1998 11:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14461 for ; Thu, 3 Dec 1998 11:51:32 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18267; Thu, 3 Dec 1998 11:41:25 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda18265; Thu Dec 3 19:41:23 1998 Date: Thu, 3 Dec 1998 11:40:55 -0800 (PST) From: Julian Elischer To: Mark Tinguely cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers In-Reply-To: <199812031513.JAA18762@plains.NoDak.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it always was taboo.. floating point operations need a process context to store results etc. in the case of context changes (e.g. interrupts) etc. BDE can be more accurate on this point I'm sure. julian On Thu, 3 Dec 1998, Mark Tinguely wrote: > I was testing a device driver that I wrote for FreeBSD 2.2.x on a > FreeBSD 3.0-RELEASE. When some double multiplication and divisions > were executed, the system froze. > > It took a long time to find it was a FP problem, it acted like > some aweful infinite loop. > > These routines are only used on a circuit setup to calculate some scheduling > parameters, and I guess they can be done with integer math after some head > scratching. > > My question is: "Is floating point math now taboo in the kernel?" > > --mark. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 11:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14606 for freebsd-current-outgoing; Thu, 3 Dec 1998 11:53:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14598 for ; Thu, 3 Dec 1998 11:53:07 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA00436; Thu, 3 Dec 1998 20:48:17 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id UAA26629; Thu, 3 Dec 1998 20:40:20 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812031940.UAA26629@semyam.dinoco.de> To: Amancio Hasty cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: nlpt and severe system slow down In-reply-to: Your message of "Thu, 03 Dec 1998 05:46:38 PST." <199812031346.FAA22883@rah.star-gate.com> Date: Thu, 03 Dec 1998 20:40:19 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is my config for nlpt: > > controller ppbus0 > controller ppc0 at isa? irq 7 vector ppcintr > device nlpt0 at ppbus? Mine is this: controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? controller ppc0 at isa? port ? tty irq 7 vector ppcintr controller ppc1 at isa? port ? tty irq 5 vector ppcintr I added the plip0 entry to be able to attach another system to plip1 one day. None connected, yet and plip1 is not configured by the network code during startup. > If I shutdown my laser jet 4mp while printing, my system comes to crawl for > instance my mouse and keyboard don't respond. The system is not quite dead > because I can see that the cursor moves or rather jumps sporadically > on my X desktop For me this behavior never happened on my system with a Canon BJC-250. It just works as expected even when I turn off the printer. Maybe the missing "tty" in your configuration for ppc0 is the difference causing this odd behavior? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:08:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15583 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:08:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15576 for ; Thu, 3 Dec 1998 12:08:28 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.Sendmail.ORG (8.9.2.Alpha2/8.9.2.Alpha2) with ESMTP id MAA23931; Thu, 3 Dec 1998 12:08:02 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id KAA26095; Thu, 3 Dec 1998 10:47:08 -0800 (PST) Message-Id: <199812031847.KAA26095@flamingo.McKusick.COM> To: Julian Elischer Subject: Re: FreeBSD fsck updated cc: current@FreeBSD.ORG, Don Lewis In-reply-to: Your message of "Wed, 02 Dec 1998 20:18:45 PST." <36661125.31DFF4F5@whistle.com> Date: Thu, 03 Dec 1998 10:47:07 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Wed, 02 Dec 1998 20:18:45 -0800 From: Julian Elischer Organization: Whistle Communications To: current@freebsd.org CC: Kirk McKusick , Don Lewis Subject: FreeBSD fsck updated References: <199811230603.WAA02649@salsa.gv.tsc.tdk.com> I have checked in kirk's newest fsck (well, a week or so old) This understands soft updates a bit better, and has some improved checks for orrupted filesystems and a few fixes.. We have also incorporated soem FreeBSD fixes in kirk's sources. What I have left are a few small patches (attached) that I'm not sure about. Two appear to be fro support for symlinks-in-inode denoted by a 0 block count. (I'm not sure about the correctness of them) (when was it done that way? 386BSD?) one is some extra pronouncements when some bits are found unset. whether we merge these old freebsd bits into the current new version is more a political matter.. What does everyone think? I now kirk doesn't like the noisy messages about the clean and modified bits.. julian I don't care one way or the other about the symlink compatibility. If there are folks still running that way, then that argues to keep it. On the other hand, if they are upgrading to 3.0, then it may be time for them to fix any remaining old-style links in their filesystem. I have commented already on my dislike of the noisy info about clean and modify bits. but here too, I do not feel strongly enough to make a big case out of it. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:28:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17352 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:28:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17345 for ; Thu, 3 Dec 1998 12:28:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA00715; Thu, 3 Dec 1998 12:27:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812032027.MAA00715@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: current@FreeBSD.ORG Subject: Re: nlpt and severe system slow down In-reply-to: Your message of "Thu, 03 Dec 1998 20:40:19 +0100." <199812031940.UAA26629@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 12:27:31 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added the "tty" entry and all is well now 8) Tnks! Amancio > > This is my config for nlpt: > > > > controller ppbus0 > > controller ppc0 at isa? irq 7 vector ppcintr > > device nlpt0 at ppbus? > > Mine is this: > > controller ppbus0 > device nlpt0 at ppbus? > device plip0 at ppbus? > controller ppc0 at isa? port ? tty irq 7 vector ppcintr > controller ppc1 at isa? port ? tty irq 5 vector ppcintr > > I added the plip0 entry to be able to attach another system to plip1 > one day. None connected, yet and plip1 is not configured by the > network code during startup. > > > If I shutdown my laser jet 4mp while printing, my system comes to crawl for > > instance my mouse and keyboard don't respond. The system is not quite dead > > because I can see that the cursor moves or rather jumps sporadically > > on my X desktop > > For me this behavior never happened on my system with a Canon BJC-250. > It just works as expected even when I turn off the printer. Maybe the > missing "tty" in your configuration for ppc0 is the difference causing > this odd behavior? > > Stefan. > -- > Stefan Eggers Lu4 yao2 zhi1 ma3 li4, > Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. > 51109 Koeln > Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17775 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:30:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17765 for ; Thu, 3 Dec 1998 12:30:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA00440; Thu, 3 Dec 1998 12:30:31 -0800 (PST) (envelope-from dillon) Date: Thu, 3 Dec 1998 12:30:31 -0800 (PST) From: Matthew Dillon Message-Id: <199812032030.MAA00440@apollo.backplane.com> To: Martin Cracauer Cc: current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) References: <19981203200743.A861@cons.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :--gBBFr7Ir9EOA20Yy :Content-Type: text/plain; charset=us-ascii : :I plan to add this to fetch, unless anyone objects. : : -s Ask server for size of file in bytes and print it to stdout. : Do not actually fetch the file. Looks useful, something like this could eventually be used in the far flung future to estimate install times (over N packages) in an install GUI, and to check packages for existance prior to trying to download them. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17940 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:31:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17854 for ; Thu, 3 Dec 1998 12:31:19 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id VAA28933; Thu, 3 Dec 1998 21:30:05 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id VAA16764; Thu, 3 Dec 1998 21:09:37 +0100 (CET) (envelope-from andreas) Message-ID: <19981203210935.A16110@klemm.gtn.com> Date: Thu, 3 Dec 1998 21:09:35 +0100 From: Andreas Klemm To: Martin Cracauer , current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) References: <19981203200743.A861@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981203200743.A861@cons.org>; from Martin Cracauer on Thu, Dec 03, 1998 at 08:07:43PM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 08:07:43PM +0100, Martin Cracauer wrote: > I plan to add this to fetch, unless anyone objects. > > -s Ask server for size of file in bytes and print it to stdout. > Do not actually fetch the file. > > Actual diff appended. > > I plan to use it for a `make fetchsize` target for ports, so that you > can ask how much traffic you would cause before actually starting the > fetch. What about the possibility of setting an environment variable FETCH_MAX=3000 where 3000 = 3000 KByte = 3 MByte Setting this variable in /etc/make.conf and fiddeling around in bsd.port.mk could add a nice functionality ... -- Andreas Klemm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18051 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:32:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18035 for ; Thu, 3 Dec 1998 12:32:31 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id UAA63934; Thu, 3 Dec 1998 20:32:01 GMT Date: Thu, 3 Dec 1998 20:32:01 +0000 (GMT) From: Doug Rabson To: Eivind Eklund cc: Mark Tinguely , luigi@labinfo.iet.unipi.it, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers In-Reply-To: <19981203165746.J18661@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Eivind Eklund wrote: > On Thu, Dec 03, 1998 at 09:47:46AM -0600, Mark Tinguely wrote: > > > > My question is: "Is floating point math now taboo in the kernel?" > > > > > > it has always been! > > > > I asked for that one :). remove taboo and replace with "forbidden". > > It always has been. > > (Ie, it has never worked reliably, and this has been a known property > of the design). On the alpha, any floating point instructions executed by the kernel (except some very careful ones during task switching) should cause a panic. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:33:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18143 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:33:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18038 for ; Thu, 3 Dec 1998 12:32:34 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id WAA28981; Thu, 3 Dec 1998 22:30:12 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Thu, 3 Dec 1998 22:30:12 +0200 (EET) From: Adrian Penisoara To: Martin Cracauer cc: current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) In-Reply-To: <19981203200743.A861@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, 3 Dec 1998, Martin Cracauer wrote: > I plan to add this to fetch, unless anyone objects. > > -s Ask server for size of file in bytes and print it to stdout. > Do not actually fetch the file. Please do, mail/imap-uw, mail/pine4 & www/netscape45-communicator already have SIZE() tags waiting to be used ! :-) [ Of course, this will need enabling appropiate code in bsd.port.mk, I believe Satoshi will get a notice from you when this will make it in the CVS tree... ] Thanks, I've been expecting this! Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19017 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:40:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galois.boolean.net (galois.boolean.net [209.133.111.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19012 for ; Thu, 3 Dec 1998 12:40:38 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (galois.boolean.net [209.133.111.74]) by galois.boolean.net (8.8.8/8.8.8) with SMTP id UAA12342; Thu, 3 Dec 1998 20:53:18 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981203124540.00b03b80@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 03 Dec 1998 12:45:40 -0800 To: HighWind Software Information From: "Kurt D. Zeilenga" Subject: Re: Thread fd locking and fork() Cc: current@FreeBSD.ORG In-Reply-To: <199812031735.MAA01016@highwind.com> References: <199812031522.KAA28193@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:35 PM 12/3/98 -0500, HighWind Software Information (rob) wrote: >Is there any solution to this? I would recommend using a surrogate parent model described by Nichols, "Pthreads Programming", p190. Basically, fork a child as soon as possible (before any pthread_* call). This child process can than act as a surrograte. When the parent wants to fork()/exec(), it communicates this to the surrogate using any number of IPC mechanisms. >Perhaps the fork() code should unlock all the descriptors. Be very careful changing the semantics of fork()... In a Posix Threads environment, state of locks should not be changed. If it's locked in the parent it must be locked in the child. Posix Threads provides the pthread_atfork() function to allow the parent to specify routines to manage fork()'ing... however it's not implemented in FreeBSD. If it was, you could argue that -lc_r probably should push an atfork cleanup handler. Having fork() itself to the cleanup, IMHO, is not wise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:47:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19744 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:47:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19736 for ; Thu, 3 Dec 1998 12:47:53 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Fri, 4 Dec 1998 07:46:51 +1100 Date: Fri, 4 Dec 1998 07:47:28 +1100 From: Peter Jeremy Subject: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE To: freebsd-current@FreeBSD.ORG Message-Id: <98Dec4.074651est.40325@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB. When I increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the system panics `getnewbuf: inconsistent EMPTY queue, qindex=0' immediately after the message `changing root device to wd0s1a'. I don't have a crashdump because (as recommended) I use dumpon(8) to specify the dumpdev, and the system doesn't get that far :-(. The system configuration is shown below (as reported by a good kernel). Can anyone offer any quick suggestions (I suspect increasing MAXUSERS or SEMMNU has caused the kernel to run out of memory somewhere, but I'm not sure where). Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #4: Fri Dec 4 06:45:33 EST 1998 root@:/usr/src/sys/compile/pc1762 Timecounter "i8254" frequency 1193182 Hz cost 2376 ns CPU: Pentium/P54C (132.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 100663296 (98304K bytes) avail memory = 95449088 (93212K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x03 int a irq 11 on pci0.15.0 ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x44 int a irq 9 on pci0.16.0 xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:ca:7b:e7 xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for PnP devices: CSN 1 Vendor ID: CSC6836 [0x3668630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:57:99:47, type WD8013EPC (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 1023 cyls, 64 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.0 Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers Waiting 2 seconds for SCSI devices to settle changing root device to wd0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 64H 32S/T 2047C) ffs_mountfs: superblock updated System configuration file: machine "i386" cpu "I586_CPU" ident "pc1762" maxusers 40 options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" options "MAXMEM=(96*1024)" options FAILSAFE #Be conservative config kernel root on wd0 options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SYSVSHM options SHMMAX="(16*1024*1024)" options SYSVSEM options SEMUME=1 options SEMMNU=1000 options SYSVMSG options "MD5" options KTRACE #kernel tracing options PERFMON options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking pseudo-device ether pseudo-device loop options FFS #Berkeley Fast Filesystem options FFS_ROOT # Allow FFS root options SOFTUPDATES options NFS #Network Filesystem options FDESC #File descriptor filesystem options MFS #Memory filesystem options PROCFS #Process filesystem pseudo-device pty 256 pseudo-device speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device vn pseudo-device ccd 4 pseudo-device bpfilter 4 controller scbus0 device da0 # SCSI disks device st0 # SCSI tapes device pass0 # SCSI passthru for CAM controller isa0 options "AUTO_EOI_1" device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr controller pci0 controller pnp0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options SC_DISABLE_REBOOT device npx0 at isa? port "IO_NPX" flags 0x0 irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" flags 0xb0ffb0ff bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 disable drive 1 controller wdc1 at isa? disable port "IO_WD2" flags 0xb0ffb0ff bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 disable drive 1 options "CMD640" controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 disable drive 1 device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device apm0 at isa? # Advanced Power Management device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? disable port "IO_COM2" tty irq 3 vector siointr controller ahc0 options AHC_ALLOW_MEMIO # Memory-mapped I/O device xl0 options NO_LKM options "CLK_USE_TSC_CALIBRATION" options PPS_SYNC Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 12:55:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20778 for freebsd-current-outgoing; Thu, 3 Dec 1998 12:55:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20768 for ; Thu, 3 Dec 1998 12:55:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA00648; Thu, 3 Dec 1998 12:55:26 -0800 (PST) (envelope-from dillon) Date: Thu, 3 Dec 1998 12:55:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812032055.MAA00648@apollo.backplane.com> To: Andreas Klemm Cc: Martin Cracauer , current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) References: <19981203200743.A861@cons.org> <19981203210935.A16110@klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> -s Ask server for size of file in bytes and print it to stdout. :> Do not actually fetch the file. :> :> Actual diff appended. :> :> I plan to use it for a `make fetchsize` target for ports, so that you :> can ask how much traffic you would cause before actually starting the :> fetch. : :What about the possibility of setting an environment variable :FETCH_MAX=3000 :where 3000 = 3000 KByte = 3 MByte :Setting this variable in /etc/make.conf and fiddeling around in :bsd.port.mk could add a nice functionality ... What would FETCH_MAX do? Generally speaking, when you type 'make' in a port you want to make the port no matter how big it is. -Matt :-- :Andreas Klemm : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 13:05:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23013 for freebsd-current-outgoing; Thu, 3 Dec 1998 13:05:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22992 for ; Thu, 3 Dec 1998 13:04:55 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial1-44.netcologne.de [194.8.196.44]) by mail2.netcologne.de (8.9.1/8.9.1) with ESMTP id WAA24265; Thu, 3 Dec 1998 22:03:51 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id WAA36675; Thu, 3 Dec 1998 22:04:58 +0100 (CET) (envelope-from marc) Date: Thu, 3 Dec 1998 22:04:58 +0100 (CET) Message-Id: <199812032104.WAA36675@oranje.my.domain> From: Marc van Woerkom To: hasty@rah.star-gate.com CC: troyk@basspro.com, ck@ns1.adsu.bellsouth.com, freebsd-current@FreeBSD.ORG In-reply-to: <199812021701.JAA00768@rah.star-gate.com> (message from Amancio Hasty on Wed, 02 Dec 1998 09:01:07 -0800) Subject: Re: Netscape Communicator 4.5 still dumps core Reply-to: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday, I was able to crash netscape with no problems > fairly consistently with http://www.abcnews.com or > http://www.fortify.net/sslcheck.html ^^^^ This is funny, your URL makes the fortify server crashing! :-) (It should be https) Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 13:31:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27155 for freebsd-current-outgoing; Thu, 3 Dec 1998 13:31:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-16-dbn.dial-up.net [196.34.155.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27131 for ; Thu, 3 Dec 1998 13:31:38 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA18890; Thu, 3 Dec 1998 23:27:03 +0200 (SAT) From: Robert Nordier Message-Id: <199812032127.XAA18890@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <86btllqfio.fsf@detlev.UUCP> from Joel Ray Holveck at "Dec 3, 98 11:52:47 am" To: joelh@gnu.org (Joel Ray Holveck) Date: Thu, 3 Dec 1998 23:27:00 +0200 (SAT) Cc: rnordier@nordier.com, mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > >>> Yes, we have been over this before. Would you care to explain how you > >>> plan to reinstate the vectors that the DOS7 kernel replaces so that > >>> vm86 BIOS calls from the FreeBSD kernel will work? > >>> Please understand that there are some really fundamental issues which > >>> absolutely preclude starting FreeBSD once DOS has been started. > >> We may have a different definition of "DOS7 kernel". I typically use > >> that phrase to refer to IO.SYS alone. The vectors seem to be modified > >> by HIMEM.SYS instead. By default, IO.SYS will load HIMEM.SYS and > >> prevent the kernel from loading. However, the line "DOS=NOAUTO" in > >> the config.sys will cause IO.SYS to skip that step. I have had > >> success loading FreeBSD by using that line in the PIF's specified > >> CONFIG.SYS myself. > > As you go on to describe, it is *not* particularly difficult to > > boot FreeBSD straight out of Windows. > > I want to make one point clear: the process *does* have an intervening > reboot between when Windows is loaded and when FreeBSD is loaded. OK. Booting out of Windows into a carefully prepared and disinfected DOS session has a chance of coming tolerably close to resembling a cold boot: at least with kernel vm86 usage as it is at the moment. But if one is exiting Windows in order to load FreeBSD, why boot into DOS anyway? (It's kind of like going to wash your hands before dinner, but then stopping off for a pee on your way back to the table.) I'm certainly not intending to knock anyone's interest in doing this. But to me, (like the hand-washing rule) looking for ways around the cold boot rule verges on the perverse. We already have a similarly-inspired "If you overclock your box, don't call us" rule. To actively encourage users to run FreeBSD on top of DOS (and whatever muck may have been swimming about in the DOS process space at the time) would be at least equally foolhardy. Because, with vm86 calls down along the real address mode interrupt chain, that's what it has the potential to amount to. To me, commonsense just says no. And I'm not trying to convert anyone else to that opinion: it's why I don't want to even *think* about this stuff any more. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 14:13:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02666 for freebsd-current-outgoing; Thu, 3 Dec 1998 14:13:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (48-sweet.camalott.com [208.239.153.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02654 for ; Thu, 3 Dec 1998 14:13:24 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA76860; Thu, 3 Dec 1998 16:12:43 -0600 (CST) (envelope-from joelh) To: Robert Nordier Cc: mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <199812032127.XAA18890@ceia.nordier.com> From: Joel Ray Holveck Date: 03 Dec 1998 16:12:39 -0600 In-Reply-To: Robert Nordier's message of "Thu, 3 Dec 1998 23:27:00 +0200 (SAT)" Message-ID: <86af14vprc.fsf@detlev.UUCP> Lines: 64 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> As you go on to describe, it is *not* particularly difficult to >>> boot FreeBSD straight out of Windows. >> I want to make one point clear: the process *does* have an intervening >> reboot between when Windows is loaded and when FreeBSD is loaded. > OK. Booting out of Windows into a carefully prepared and disinfected > DOS session has a chance of coming tolerably close to resembling a > cold boot: at least with kernel vm86 usage as it is at the moment. Okay. I'm still trying to understand the differences at that point. > But if one is exiting Windows in order to load FreeBSD, why boot > into DOS anyway? (It's kind of like going to wash your hands before > dinner, but then stopping off for a pee on your way back to the > table.) In the past, there were cards that required initialization by DOS device drivers. For instance, a card which would emulate a Sound Blaster, but only if a DOS driver configured it for that. I seem to recall reading this and a few other situations in which FBSDBOOT was required in the past. Is this no longer valid? > I'm certainly not intending to knock anyone's interest in doing > this. There appears to be a notable call for booting from Win95 into FreeBSD. I don't personally care how it's done, but if FBSDBOOT works for the vast majority, I didn't see any reason to write something new. However, you have been saying that this will not work. I believe you, but also want to know why and where it fails, and why it works on the system I tested it on. In the archives, I couldn't find anything that didn't point to HIMEM. > But to me, (like the hand-washing rule) looking for ways around the > cold boot rule verges on the perverse. I'm not particularly interested in looking for ways around it. I'm trying to figure out why it exists. You may also note that I have started asking about nextboot, and if I could write an app to use its system. > We already have a similarly-inspired "If you overclock your box, > don't call us" rule. I know. I know why the overclock rule exists. I don't know why the cold boot rule exists. > To me, commonsense just says no. And I'm not trying to convert > anyone else to that opinion: it's why I don't want to even *think* > about this stuff any more. :-) Okay. If you feel it necessary to drop this thread, go ahead. If you can explain the cold boot rule's reasoning to me, even better. If you (or Mike or anybody) can tell me whether nextboot still works, terrific. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 14:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08212 for freebsd-current-outgoing; Thu, 3 Dec 1998 14:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08205 for ; Thu, 3 Dec 1998 14:51:32 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id XAA05165; Thu, 3 Dec 1998 23:45:10 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id XAA05273; Thu, 3 Dec 1998 23:27:42 +0100 (CET) (envelope-from andreas) Message-ID: <19981203232742.A5266@klemm.gtn.com> Date: Thu, 3 Dec 1998 23:27:42 +0100 From: Andreas Klemm To: Matthew Dillon Cc: Martin Cracauer , current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) References: <19981203200743.A861@cons.org> <19981203210935.A16110@klemm.gtn.com> <199812032055.MAA00648@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812032055.MAA00648@apollo.backplane.com>; from Matthew Dillon on Thu, Dec 03, 1998 at 12:55:26PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 12:55:26PM -0800, Matthew Dillon wrote: > > What would FETCH_MAX do? Generally speaking, when you type > 'make' in a port you want to make the port no matter how big > it is. And when I do setenv BATCH true cd /usr/ports/ make all install clean Just a thought, or ? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 14:54:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08654 for freebsd-current-outgoing; Thu, 3 Dec 1998 14:54:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08646 for ; Thu, 3 Dec 1998 14:54:34 -0800 (PST) (envelope-from stb@hanse.de) Received: from hanse.de (uucp@localhost) by rrz.Hanse.DE (8.8.8/8.8.8) with UUCP id XAA22094; Thu, 3 Dec 1998 23:51:06 +0100 (CET) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA01774; Wed, 2 Dec 1998 00:39:34 +0100 (CET) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA27436; Wed, 2 Dec 1998 00:37:47 +0100 (CET) (envelope-from stb@hanse.de) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Wed, 2 Dec 1998 00:37:47 +0100 (CET) From: Stefan Bethke To: Matthew Dillon cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <199812011647.IAA07545@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just as a side-note: On Tue, 1 Dec 1998, Matthew Dillon wrote: > :We should rate-limit ARPs, but don't. > > ARP's reasonably rate-limited because most subnets are /24's, it's > the packets queued up waiting for the ARP to resolve that are the > problem. Actually, arp is already (somewhat) rate-limited. Look in src/sys/netinet/if_ether.c:arpresolve(), around line 369: /* * There is an arptab entry, but no ethernet address * response yet. Replace the held mbuf with this * latest one. */ if (la->la_hold) m_freem(la->la_hold); The packet waiting for the address to resolve will be replaced by the next packet transmitted for this address. Use ping -f and tcpdump to see for yourself. Theory suggests that there can be no more than one request per local IP address per second, and, due to the limit of a maximum of 5 tries, even less (net.link.ether.inet.{maxtries,host_down_time}). Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 15:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10521 for freebsd-current-outgoing; Thu, 3 Dec 1998 15:15:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10508 for ; Thu, 3 Dec 1998 15:15:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00335; Thu, 3 Dec 1998 14:43:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812032243.OAA00335@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: nlpt and severe system slow down In-reply-to: Your message of "Thu, 03 Dec 1998 05:46:38 PST." <199812031346.FAA22883@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 14:43:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is my config for nlpt: > > controller ppbus0 > controller ppc0 at isa? irq 7 vector ppcintr > device nlpt0 at ppbus? > > > If I shutdown my laser jet 4mp while printing, my system comes to crawl for > instance my mouse and keyboard don't respond. The system is not quite dead > because I can see that the cursor moves or rather jumps sporadically > on my X desktop > > Has anyone else seeng this behavior? Yes; it's better than the old 'lpt' driver which would freeze your system until you turned the printer back on. Nicolas should probably look at this one... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 15:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11663 for freebsd-current-outgoing; Thu, 3 Dec 1998 15:25:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11657 for ; Thu, 3 Dec 1998 15:25:31 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem26.masternet.it [194.184.65.36]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id AAA12687; Fri, 4 Dec 1998 00:24:49 +0100 (MET) Message-Id: <199812032324.AAA12687@www.giovannelli.it> From: "Gianmarco Giovannelli" To: Karl Pielorz Date: Fri, 4 Dec 1998 00:32:54 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: panic: ffs_blkfree: bad size Reply-to: gmarco@giovannelli.it CC: freebsd-current@FreeBSD.ORG In-reply-to: <3666B8F0.60874AC4@tdx.co.uk> X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Both my Single PPro 200 & Dual PPro 200's are runing -current (couple of days > old build from last Saturday I think), both work fine (even under duress)... > Both aren't running softupdates... ? Mine too... no more reboots in the last weeks... (and here I do a make world. a day) no softupdates, PII 400mhz with onboard SCSI, 128mb ram. Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 15:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11949 for freebsd-current-outgoing; Thu, 3 Dec 1998 15:28:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11941 for ; Thu, 3 Dec 1998 15:28:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00785; Thu, 3 Dec 1998 15:23:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812032323.PAA00785@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: joelh@gnu.org (Joel Ray Holveck), mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 03 Dec 1998 23:27:00 +0200." <199812032127.XAA18890@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 15:23:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK. Booting out of Windows into a carefully prepared and disinfected > DOS session has a chance of coming tolerably close to resembling a > cold boot: at least with kernel vm86 usage as it is at the moment. > > But if one is exiting Windows in order to load FreeBSD, why boot > into DOS anyway? (It's kind of like going to wash your hands before > dinner, but then stopping off for a pee on your way back to the > table.) Because you may have the FreeBSD install on the DOS partition, ie. not having a partition of its own. So you can't guarantee that you can activate a different partition and boot from it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 15:41:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13052 for freebsd-current-outgoing; Thu, 3 Dec 1998 15:41:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from devel.dns-host.com (devel.dns-host.com [209.170.57.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13047 for ; Thu, 3 Dec 1998 15:41:49 -0800 (PST) (envelope-from devel@devel.dns-host.com) Received: (from devel@localhost) by devel.dns-host.com (8.9.1/8.8.8) id PAA03354; Thu, 3 Dec 1998 15:43:41 -0800 (PST) (envelope-from devel) Date: Thu, 3 Dec 1998 15:43:41 -0800 (PST) Message-Id: <199812032343.PAA03354@devel.dns-host.com> From: Icom Development To: current@FreeBSD.ORG Subject: libc_r pthread build problem User-Agent: SEMI/1.9.1 (Kurikara) FLIM/1.11.0 (Yamadagawa) Emacs/20.2 (i386--freebsd) MULE/3.0 (MOMIJINOGA) MIME-Version: 1.0 (generated by SEMI 1.9.1 - "Kurikara") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My "make" in /usr/src fails with the errors I have appended, on uthread_mutex.c. Have I missed an update or is this a known problem? Thanks, Alexander G. Burchell Software Development Internet Communications devel@icom.com --- BEGIN INCLUDED TEXT --- ===> lib/libc_r cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc_r/uthread/uthread_mutex.c -o uthread_mutex.o /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function `pthread_mutex_init': /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: `PTHREAD_MUTEX_DEFAULT' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: (Each undeclared identifier is reported only once /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: for each function it appears in.) /usr/src/lib/libc_r/uthread/uthread_mutex.c:78: `PTHREAD_MUTEX_NORMAL' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:79: `PTHREAD_MUTEX_ERRORCHECK' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:84: `PTHREAD_MUTEX_RECURSIVE' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:90: warning: unreachable code at beginning of switch statement /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function `pthread_mutex_trylock': /usr/src/lib/libc_r/uthread/uthread_mutex.c:179: `PTHREAD_MUTEX_NORMAL' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:180: `PTHREAD_MUTEX_DEFAULT' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:181: `PTHREAD_MUTEX_ERRORCHECK' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:193: `PTHREAD_MUTEX_RECURSIVE' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:214: warning: unreachable code at beginning of switch statement /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function `pthread_mutex_lock': /usr/src/lib/libc_r/uthread/uthread_mutex.c:248: `PTHREAD_MUTEX_NORMAL' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:257: `PTHREAD_MUTEX_ERRORCHECK' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:264: `PTHREAD_MUTEX_DEFAULT' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:294: `PTHREAD_MUTEX_RECURSIVE' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:329: warning: unreachable code at beginning of switch statement /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function `pthread_mutex_unlock': /usr/src/lib/libc_r/uthread/uthread_mutex.c:358: `PTHREAD_MUTEX_NORMAL' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:359: `PTHREAD_MUTEX_DEFAULT' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:360: `PTHREAD_MUTEX_ERRORCHECK' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:377: `PTHREAD_MUTEX_RECURSIVE' undeclared (first use this function) /usr/src/lib/libc_r/uthread/uthread_mutex.c:401: warning: unreachable code at beginning of switch statement --- END INCLUDED TEXT --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 15:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13293 for freebsd-current-outgoing; Thu, 3 Dec 1998 15:43:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13288 for ; Thu, 3 Dec 1998 15:43:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA02230; Thu, 3 Dec 1998 15:42:47 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id PAA00924; Thu, 3 Dec 1998 15:42:47 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 3 Dec 1998 15:42:47 -0800 (PST) Message-Id: <199812032342.PAA00924@vashon.polstra.com> To: gnb@itga.com.au Subject: Re: How to catch all the /etc/pam.conf type mistakes Newsgroups: polstra.freebsd.current In-Reply-To: <199812030718.SAA29220@melba.bby.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812030718.SAA29220@melba.bby.com.au>, Gregory Bond wrote: > I've just cvsup'd from the 3.0 CDs and been bit by the pam.conf > thang (that was handily explained by John Polk's message in the > mailing list archives Hey, that's "Polstra" to you, fella! It's easy to remember. Just think, "Art Slop spelled backwards," and you'll get it right every time. Sheesh, how am I ever gonna get famous if people keep mangling my name? ;-) John POLSTRA -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 16:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19026 for freebsd-current-outgoing; Thu, 3 Dec 1998 16:13:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18990 for ; Thu, 3 Dec 1998 16:13:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01130; Thu, 3 Dec 1998 16:11:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812040011.QAA01130@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman cc: freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Thu, 03 Dec 1998 10:57:15 EST." <199812031557.KAA27821@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 16:11:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> Cannot we unload all of the device recognition code once it has done its > >> job and reload it each time the PCCARD finds a new arrival? > > > What "device recognition code"? If we keep the current model, it's all > > in a user-space application. > > The current model is totally broken and doesn't work like anyone > else's PC-Card implementation anywhere. This Is Bad since it makes > drivers much harder to port than they need to be. I tend to agree that the current model isn't all it could be. > > If we were to move the CIS ID : driver/rules match code into the > > kernel, it would be so small and trivial that the effort involved in > > loading/unloading it would be disproportionate to the space regained > > (maybe 1 page). > > Under the new bus architecture (and also the standard Card Services > model), the correct thing is to let each candidate driver look at the > CIS and see whether it can handle the device -- for a simple driver, > probably about 100 bytes. To put this on a page by itself so that it > could be unloaded would waste most of a page. I'm not fond of this sort of 'active match' approach at all; particularly for pccard devices it makes it impossible to apply an existing driver to a new peripheral without patching and rebuilding the driver, which is extremely lame. Rather, the approach I've been slowly taking with the PnP code in the new bootblocks has been to produce a set of uniquely formatted ASCII identifiers, sorted by "match quality" for a device, and then have an external database which pairs identifiers with drivers and optional parameters. This means that you can add a new device for which an existing driver is adequate simply by updating the (flat text) database. By using several identifiers sorted by priority you can have class-specific drivers which can be overridden by device-specific drivers when appropriate. So for a PCCARD you have the first identifier being the manufacturer/ model/version set, eg. "Megahertz/XJ4336-CC4336/5.0" and then you can add a second identifier build from the functional ID and functional extensions - in the case of this modem you'd have something like "serial/16550/modem". Naturally the disposition of this database can be tweaked; at the moment it'll be moving to /boot/pnpdata, where it will be consulted -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 16:18:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20385 for freebsd-current-outgoing; Thu, 3 Dec 1998 16:18:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20371 for ; Thu, 3 Dec 1998 16:18:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01175; Thu, 3 Dec 1998 16:16:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812040016.QAA01175@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 04 Dec 1998 02:09:12 +0200." <199812040009.CAA20442@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 16:16:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > OK. Booting out of Windows into a carefully prepared and disinfected > > > DOS session has a chance of coming tolerably close to resembling a > > > cold boot: at least with kernel vm86 usage as it is at the moment. > > > > > > But if one is exiting Windows in order to load FreeBSD, why boot > > > into DOS anyway? (It's kind of like going to wash your hands before > > > dinner, but then stopping off for a pee on your way back to the > > > table.) > > > > Because you may have the FreeBSD install on the DOS partition, ie. not > > having a partition of its own. So you can't guarantee that you can > > activate a different partition and boot from it. > > OK, if this translates to "demo", then we're talking marketing- > driven solutions, and completely different rules apply. Uh, no, not at all. There are situations where to get FreeBSD into an environment, we'll have to be able to operate like this. Whether we do it with a "UMSDOS" style approach, or with a monolithic 'filesystem file', it'd be worthwhile. > Sample choices: > > o Get vm86 working reliably with a virus or two swirling > around, and a couple of TSRs trying to pop up. See the new fbsdboot sample I sent you; it'd be useful to know how vulnerable this might be to that. TBH, I can't see any problem with saying "if you have a viral infection, we can't help you". > o Use a boot floppy. Ick. We have to be able to do better than that. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 16:34:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23374 for freebsd-current-outgoing; Thu, 3 Dec 1998 16:34:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-29-dbn.dial-up.net [196.34.155.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23283 for ; Thu, 3 Dec 1998 16:34:22 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA20442; Fri, 4 Dec 1998 02:09:15 +0200 (SAT) From: Robert Nordier Message-Id: <199812040009.CAA20442@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199812032323.PAA00785@dingo.cdrom.com> from Mike Smith at "Dec 3, 98 03:23:46 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 4 Dec 1998 02:09:12 +0200 (SAT) Cc: rnordier@nordier.com, joelh@gnu.org, mike@smith.net.au, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > OK. Booting out of Windows into a carefully prepared and disinfected > > DOS session has a chance of coming tolerably close to resembling a > > cold boot: at least with kernel vm86 usage as it is at the moment. > > > > But if one is exiting Windows in order to load FreeBSD, why boot > > into DOS anyway? (It's kind of like going to wash your hands before > > dinner, but then stopping off for a pee on your way back to the > > table.) > > Because you may have the FreeBSD install on the DOS partition, ie. not > having a partition of its own. So you can't guarantee that you can > activate a different partition and boot from it. OK, if this translates to "demo", then we're talking marketing- driven solutions, and completely different rules apply. Sample choices: o Get vm86 working reliably with a virus or two swirling around, and a couple of TSRs trying to pop up. o Use a boot floppy. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 16:34:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23476 for freebsd-current-outgoing; Thu, 3 Dec 1998 16:34:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23461 for ; Thu, 3 Dec 1998 16:34:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA01418; Thu, 3 Dec 1998 16:34:32 -0800 (PST) (envelope-from dillon) Date: Thu, 3 Dec 1998 16:34:32 -0800 (PST) From: Matthew Dillon Message-Id: <199812040034.QAA01418@apollo.backplane.com> To: Stefan Bethke Cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Just as a side-note: : :On Tue, 1 Dec 1998, Matthew Dillon wrote: : :> :We should rate-limit ARPs, but don't. :> :> ARP's reasonably rate-limited because most subnets are /24's, it's :> the packets queued up waiting for the ARP to resolve that are the :... : :Actually, arp is already (somewhat) rate-limited. Look in :src/sys/netinet/if_ether.c:arpresolve(), around line 369: :... :The packet waiting for the address to resolve will be replaced by the next :packet transmitted for this address. Use ping -f and tcpdump to see for : :Theory suggests that there can be no more than one request per local IP :... Ah, I see. I was thinking of the ARP packets themselves but it makes to limit the queued packets waiting for ARP to any given destination IP. If you have a larger subnet, say a class B, an attacker can spoof sufficient packets (which the machine then tries to reply to) to cover the entire class B... 65536 queued packets waiting for ARP, for example. But I consider this a minor problem, since most machines don't sit on insanely huge subnets. It would be nice to fix, but not critical. -Matt :Cheers, :Stefan Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 17:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26986 for freebsd-current-outgoing; Thu, 3 Dec 1998 17:03:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.scient.com (set.Scient.COM [208.29.209.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA26980 for ; Thu, 3 Dec 1998 17:03:42 -0800 (PST) (envelope-from enkhyl@scient.com) Received: by set.scient.com; (5.65v4.0/1.3/10May95) id AA29730; Thu, 3 Dec 1998 17:03:28 -0800 Received: from somewhere by smtpxd Date: Thu, 3 Dec 1998 17:03:17 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: cnielsen@pobox.com To: current@FreeBSD.ORG Subject: buildworld failure from ICMP_BANDLIM Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 'make -j32 buildworld' died when trying to build netstat. This is from a cvsup of about 3PM today. It looks to be from the ICMP_BANDLIM option: ===> usr.bin/netstat cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/if.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/inet.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/main.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/mbuf.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/mroute.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/ipx.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/route.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/unix.c cc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/atalk.c gzip -cn /usr/src/usr.bin/netstat/netstat.1 > netstat.1.gz In file included from /usr/src/usr.bin/netstat/inet.c:55: /usr/obj/elf/usr/src/tmp/usr/include/netinet/icmp_var.h:40: opt_icmp_bandlim.h: No such file or directory *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 17:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01412 for freebsd-current-outgoing; Thu, 3 Dec 1998 17:42:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01405 for ; Thu, 3 Dec 1998 17:42:36 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with ESMTP id TAA05553; Thu, 3 Dec 1998 19:41:48 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 3 Dec 1998 19:41:47 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: David Greenman cc: "Jordan K. Hubbard" , Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812030759.XAA17756@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, David Greenman wrote: > >> sysctl -w vfs.ffs.doreallocblks=0 > >> > >> Is the correct response. > > > >Why isn't this currently the default if it's as pathological as you > >say? Has anyone actually asked David this question? It would be > >only courteous given that he's the author of this bug/feature. > > The feature is fairly important. Steve and one or two other people are > the only ones seeing the problem after Kirk's fix was committed. Steve is > the only person to report filesystem corruption caused by it. I'm not able > to reproduce the panic, despite doing more than 20 "make world"s in an > attempt to reproduce it. If we disable it by default then it will never get > fixed because there will be no feedback from people who are still having > problems with it. I WILL disable it prior to the 3.0.1 release if it isn't > fixed by then, however. Meanwhile I'll look at adding something that will > ensure that filesystem corruption isn't possible - I think this will amount > to detecting the problem and panicing earlier. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project I posted a message a while back when this bug first started to bite. I have a good coredump or two (using debugging kernel and all) if anyone wants them. Kirk told me he would look at Greg's dump first and get back to me if he needed more samples, but I haven't heard from him. I can build a more recent world (mine is a couple weeks old now) and turn on vfs.ffs.doreallocblks again to get a more recent dump. It occurrs without having to do much work. My system has been rock solid ever since I set vfs.ffs.doreallocblks=0 at boot, so it isn't hardware instability like I thought it may have been. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) ( http://www.freebsd.org ) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 17:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03009 for freebsd-current-outgoing; Thu, 3 Dec 1998 17:57:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03002 for ; Thu, 3 Dec 1998 17:57:29 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id UAA08468; Thu, 3 Dec 1998 20:56:35 -0500 (EST) Date: Thu, 3 Dec 1998 20:56:35 -0500 (EST) Message-Id: <199812040156.UAA08468@highwind.com> From: HighWind Software Information To: Kurt@OpenLDAP.Org CC: current@FreeBSD.ORG In-reply-to: <3.0.5.32.19981203124540.00b03b80@localhost> (Kurt@OpenLDAP.Org) Subject: Re: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a Posix Threads environment, state of locks should not be changed. If it's locked in the parent it must be locked in the child. Posix Threads provides the pthread_atfork() function to allow the parent to specify routines to manage fork()'ing... however it's not implemented in FreeBSD. If it was, you could argue that -lc_r probably should push an atfork cleanup handler. Kurt, 1. I agree with you 100%. However, these locks are simply libc_r internals and have nothing to do with locks the application can see. 2. libc_r simply doesn't do the right thing with regard to these internal fd locks in the case of fork(). 3. My patch causes absolutely no harm and fixes the problem. An atfork() handler will not work since it can't get inside the libc_r library and no external calls exist to touch these hidden libc_r private locks. I've tested this and it works like a champ. If someone with commit priv's could take a look at this simple code fragment for libc_r's uthread_fork.c, I'd greatly appreciate it. It needs to be inserted after fork() does its "kill all the threads but this one" thing. /* * Enter a loop to remove all locks on all locked fd's */ for (i = 0; i < _thread_dtablesize; i++) { if (_thread_fd_table[i] != NULL) { memset(&_thread_fd_table[i]->lock, 0, sizeof(_thread_fd_table[i]->lock)); _thread_fd_table[i]->r_owner = NULL; _thread_fd_table[i]->w_owner = NULL; _thread_fd_table[i]->r_fname = NULL; _thread_fd_table[i]->w_fname = NULL; _thread_fd_table[i]->r_lineno = 0;; _thread_fd_table[i]->w_lineno = 0;; _thread_fd_table[i]->r_lockcount = 0; _thread_fd_table[i]->w_lockcount = 0; /* Initialize the read/write queues: */ _thread_queue_init(&_thread_fd_table[i]->r_queu\ e); _thread_queue_init(&_thread_fd_table[i]->w_queu\ e); } } -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 17:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03156 for freebsd-current-outgoing; Thu, 3 Dec 1998 17:59:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-42-dbn.dial-up.net [196.34.155.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03143 for ; Thu, 3 Dec 1998 17:59:50 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id DAA21505; Fri, 4 Dec 1998 03:57:28 +0200 (SAT) From: Robert Nordier Message-Id: <199812040157.DAA21505@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <86af14vprc.fsf@detlev.UUCP> from Joel Ray Holveck at "Dec 3, 98 04:12:39 pm" To: joelh@gnu.org (Joel Ray Holveck) Date: Fri, 4 Dec 1998 03:57:24 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > > To me, commonsense just says no. And I'm not trying to convert > > anyone else to that opinion: it's why I don't want to even *think* > > about this stuff any more. :-) > > Okay. If you feel it necessary to drop this thread, go ahead. If you > can explain the cold boot rule's reasoning to me, even better. If you > (or Mike or anybody) can tell me whether nextboot still works, > terrific. We're probably fundamentally at cross-purposes here. You're saying, "But if I'm smart and careful, FBSDBOOT works for me, now". I'm saying, "FBSDBOOT is a major PITA with an immense potential for generating future support headaches because most folks will expect it to work when they're being neither smart nor careful. And it won't necessarily fail outright, it may just make the entire (future) system behave erratically." DOS was never intended as a generic launching pad for other operating systems. If their abysmal way, DOS versions 5 and above are quite sophisticated in terms of how they transform the default BIOS environment. No doubt you would never run FBSDBOOT with half a dozen home-grown DOS device drivers, and an equal number of TSR utilities installed. No doubt you would never run FBSDBOOT after running some inane non-resident program in your AUTOEXEC.BAT which completely hoses some significant part of the BIOS Data Area. No doubt you would never run FBSDBOOT after using a sexy commercial package which carelessly reprograms some hardware component in a way that doesn't matter to DOS. Before FreeBSD use of vm86, running FBSDBOOT was largely a hit or miss affair (the kernel loaded or it didn't). Once vm86 is heavily in use, the scenario changes. Let's say your file systems are suddenly getting trashed? Is that a FreeBSD problem? Well, FreeBSD will certainly get the blame. But faced with a predominantly Windows-using user, how do we disentangle this? Does everyone start sending MSD (Microsoft Systems Diagnostics) output along with the dmesg stuff? I'm not saying "Don't use FBSDBOOT". I'm just saying that (even though FBSDBOOT is "there" and works some of the time) loading DOS to load BTX to load the FreeBSD kernel is just not the easy route it seems to be. DOS opens a major can of worms. The worms may stay in the can, or they may not; either way, the result is simply dubious. By comparison, a clean boot approach is simple and failsafe. Regarding nextboot, I can't get your question into any kind of context, sorry. Is this just an entirely separate issue, or does "still works" relate to using FBSDBOOT versus not using FBSDBOOT in some way? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 18:01:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03305 for freebsd-current-outgoing; Thu, 3 Dec 1998 18:01:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03300 for ; Thu, 3 Dec 1998 18:01:29 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with ESMTP id TAA05599; Thu, 3 Dec 1998 19:58:42 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 3 Dec 1998 19:58:41 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= cc: dg@root.com, jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812030834.JAA10358@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id SAA03301 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Søren Schmidt wrote: > I dont know If I'm one of the two, but it f*ks up here too, on ALL my > machines, except on my notebook which uses softupdates. > As has been stated before it has nothing to do with the machine being > loaded, on the contrary, here it dies when the machine is idle and > mail arrives or some such. > I recommend that it should be disabled NOW, instead of hosing our users, > its not "important" when it doesn't work... I was about the make the comment in my last posting that it almost always occurred on my system when disk and network activity were combined (such as updating my local CVS repository). Wether the same process has to be causing both the network and disk activity to cause the failure, I'm not exactly sure. I do remember someone else posting it happened while they were sending a backup to the machine over the network, and another person mentioned it also happened while doing cvsup activity over the network. I think yet another mentioned it happened while copying a file between an NFS mount and a local filesystem. In your case, a piece of mail arriving could cause network and disk activity simultaneously. The network/disk activity does not have to be heavy in my case (only a 33k6 link). Anyone else seeing the same pattern I am? :-) I don't think I mentioned before that all of my filesystems except two rarely used ones have softupdates enabled. All of the activity occurred on softupdates filesystems. AFAIK no data was corrupted and fsck had a pretty easy time cleaning things up. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) ( http://www.freebsd.org ) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 18:09:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04149 for freebsd-current-outgoing; Thu, 3 Dec 1998 18:09:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04142 for ; Thu, 3 Dec 1998 18:09:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id SAA26983; Thu, 3 Dec 1998 18:07:27 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812040207.SAA26983@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= , dg@root.com, jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Thu, 03 Dec 1998 19:58:41 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 18:07:27 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have compiled several large packages like XFree86 over NFS with no crashes however both systems have soft updates enabled on all its disks. Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 18:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04621 for freebsd-current-outgoing; Thu, 3 Dec 1998 18:13:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04614 for ; Thu, 3 Dec 1998 18:13:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA02357; Thu, 3 Dec 1998 18:15:19 -0800 (PST) To: Robert Nordier cc: joelh@gnu.org (Joel Ray Holveck), freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 04 Dec 1998 03:57:24 +0200." <199812040157.DAA21505@ceia.nordier.com> Date: Thu, 03 Dec 1998 18:15:18 -0800 Message-ID: <2353.912737718@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DOS opens a major can of worms. The worms may stay in the can, or > they may not; either way, the result is simply dubious. By > comparison, a clean boot approach is simple and failsafe. And, to put it more bluntly, is just fine for our needs (a demo mode running out of a DOS partition, remember folks? :-). Who do I have to kil^H^H^Hpay to have this work done? We want it and we want it yesterday. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 18:37:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06681 for freebsd-current-outgoing; Thu, 3 Dec 1998 18:37:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06669 for ; Thu, 3 Dec 1998 18:37:42 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id SAA27887; Thu, 3 Dec 1998 18:38:06 -0800 (PST) Message-Id: <199812040238.SAA27887@root.com> To: Chris Dillon cc: "Jordan K. Hubbard" , Steve Kargl , bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Thu, 03 Dec 1998 19:41:47 CST." From: David Greenman Reply-To: dg@root.com Date: Thu, 03 Dec 1998 18:38:05 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I posted a message a while back when this bug first started to bite. I >have a good coredump or two (using debugging kernel and all) if anyone >wants them. Kirk told me he would look at Greg's dump first and get >back to me if he needed more samples, but I haven't heard from him. I >can build a more recent world (mine is a couple weeks old now) and turn >on vfs.ffs.doreallocblks again to get a more recent dump. It occurrs >without having to do much work. My system has been rock solid ever >since I set vfs.ffs.doreallocblks=0 at boot, so it isn't hardware >instability like I thought it may have been. There was a bug found in the original code that has been fixed. What we're interested in now is continued problems *after* the bugfix (about Nov 18th). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 18:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07573 for freebsd-current-outgoing; Thu, 3 Dec 1998 18:46:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07568 for ; Thu, 3 Dec 1998 18:46:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA00209; Thu, 3 Dec 1998 21:46:14 -0500 (EST) (envelope-from wollman) Date: Thu, 3 Dec 1998 21:46:14 -0500 (EST) From: Garrett Wollman Message-Id: <199812040246.VAA00209@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812040011.QAA01130@dingo.cdrom.com> References: <199812031557.KAA27821@khavrinen.lcs.mit.edu> <199812040011.QAA01130@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'm not fond of this sort of 'active match' approach at all; > particularly for pccard devices it makes it impossible to apply an > existing driver to a new peripheral without patching and rebuilding the > driver, which is extremely lame. The driver needs to know what sort of bus it's on -- there's simply no escaping that. (At a minimum, Ethernet cards need to be able to figure out how to read their hardware addresses, which are invariably in the CIS for PC-Card Ethernet cards.) I would be willing to have an ``erratum database'' which indicates additional devices which should be handled by an existing driver, but it should be the driver which decides (after all, it might just inspect the programming model and not look at the vendor information at all) whether it can handle the card in question. (We need to have something like this anyway, since the Linux Card Services manual indicates that some cards come with completely bogus CIS.) In any case, the more like the official Card Services, the better, since that's what will make it easy to port drivers. > "serial/16550/modem". Ugh. I don't like the kernel being asked to parse more and more arrays of text strings. Deal with data in their natural format. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 19:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09225 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:02:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09218 for ; Thu, 3 Dec 1998 19:02:34 -0800 (PST) (envelope-from stb@hanse.de) Received: from hanse.de (uucp@localhost) by rrz.Hanse.DE (8.8.8/8.8.8) with UUCP id DAA24931; Fri, 4 Dec 1998 03:59:28 +0100 (CET) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id DAA14802; Fri, 4 Dec 1998 03:03:59 +0100 (CET) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id DAA12349; Fri, 4 Dec 1998 03:02:07 +0100 (CET) (envelope-from stb@hanse.de) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Fri, 4 Dec 1998 03:02:06 +0100 (CET) From: Stefan Bethke To: Matthew Dillon cc: Garrett Wollman , John Saunders , freebsd-current@FreeBSD.ORG Subject: Re: RE: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-Reply-To: <199812040034.QAA01418@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Matthew Dillon wrote: > :Just as a side-note: > : > :On Tue, 1 Dec 1998, Matthew Dillon wrote: > : > :> :We should rate-limit ARPs, but don't. > :> > :> ARP's reasonably rate-limited because most subnets are /24's, it's > :> the packets queued up waiting for the ARP to resolve that are the > :... > : > :Actually, arp is already (somewhat) rate-limited. > > Ah, I see. I was thinking of the ARP packets themselves but it makes > to limit the queued packets waiting for ARP to any given destination IP. > > If you have a larger subnet, say a class B, an attacker can spoof > sufficient packets (which the machine then tries to reply to) to cover > the entire class B... 65536 queued packets waiting for ARP, for example. Only if you have a large number of unused addresses; for the used ones, a reply will be received, and subsequently, much less arps will be done. Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 19:09:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10169 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:09:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10164 for ; Thu, 3 Dec 1998 19:09:27 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with ESMTP id VAA05899 for ; Thu, 3 Dec 1998 21:09:12 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 3 Dec 1998 21:09:11 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812040238.SAA27887@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snipped everyone but the list out of my reply.. no sense in filling up those mailboxes twice for this] On Thu, 3 Dec 1998, David Greenman wrote: > >I posted a message a while back when this bug first started to bite. I > >have a good coredump or two (using debugging kernel and all) if anyone > >wants them. Kirk told me he would look at Greg's dump first and get > >back to me if he needed more samples, but I haven't heard from him. I > >can build a more recent world (mine is a couple weeks old now) and turn > >on vfs.ffs.doreallocblks again to get a more recent dump. It occurrs > >without having to do much work. My system has been rock solid ever > >since I set vfs.ffs.doreallocblks=0 at boot, so it isn't hardware > >instability like I thought it may have been. > > There was a bug found in the original code that has been fixed. What we're > interested in now is continued problems *after* the bugfix (about Nov 18th). > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project I'll try out the latest code this weekend and then pound on the box for a while and see if it fails. I _thought_ I had tried it after the fix was commited and it still failed, but I'm not sure anymore. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) ( http://www.freebsd.org ) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 19:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10800 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:15:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10791 for ; Thu, 3 Dec 1998 19:14:59 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id GAA23166; Fri, 4 Dec 1998 06:14:30 +0300 (MSK) (envelope-from ache) Message-ID: <19981204061430.A22394@nagual.pp.ru> Date: Fri, 4 Dec 1998 06:14:30 +0300 From: "Andrey A. Chernov" To: Chris Dillon , freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size Mail-Followup-To: Chris Dillon , freebsd-current@FreeBSD.ORG References: <199812040238.SAA27887@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Thu, Dec 03, 1998 at 09:09:11PM -0600 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 09:09:11PM -0600, Chris Dillon wrote: > I'll try out the latest code this weekend and then pound on the box for > a while and see if it fails. I _thought_ I had tried it after the fix > was commited and it still failed, but I'm not sure anymore. Just FYI: with very recent -current I got "lockmgr: locking against myself" panic about twice a day. No sure that it is related to doreallocs, but maybe. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 19:55:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13974 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:55:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13961 for ; Thu, 3 Dec 1998 19:55:45 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.1/8.9.1) id EAA02620; Fri, 4 Dec 1998 04:55:29 +0100 (CET) Date: Fri, 4 Dec 1998 04:55:29 +0100 (CET) Message-Id: <199812040355.EAA02620@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size From: Ronald Kuehn MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: NN version 6.5.0 CURRENT #124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current Chris Dillon wrote: > On Thu, 3 Dec 1998, Søren Schmidt wrote: > > I dont know If I'm one of the two, but it f*ks up here too, on ALL my > > machines, except on my notebook which uses softupdates. > > As has been stated before it has nothing to do with the machine being > > loaded, on the contrary, here it dies when the machine is idle and > > mail arrives or some such. > > I recommend that it should be disabled NOW, instead of hosing our users, > > its not "important" when it doesn't work... > I was about the make the comment in my last posting that it almost > always occurred on my system when disk and network activity were > combined (such as updating my local CVS repository). Wether the same > process has to be causing both the network and disk activity to cause > the failure, I'm not exactly sure. I do remember someone else posting > it happened while they were sending a backup to the machine over the > network, and another person mentioned it also happened while doing cvsup > activity over the network. I think yet another mentioned it happened > while copying a file between an NFS mount and a local filesystem. In > your case, a piece of mail arriving could cause network and disk > activity simultaneously. The network/disk activity does not have to be > heavy in my case (only a 33k6 link). Anyone else seeing the same > pattern I am? :-) > I don't think I mentioned before that all of my filesystems except two > rarely used ones have softupdates enabled. All of the activity occurred > on softupdates filesystems. AFAIK no data was corrupted and fsck had a > pretty easy time cleaning things up. I had such a panic today too during cvsup activity. Two filesystems don't have softupdates. All others do. The activity was on one of those softupdates filesystems. dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var panic: ffs_blkfree: bad size The /var filesystem does not have soft updates enabled. I got a dump, but not from a debugging kernel. [ current as of Dec 2 ] Bye, Ronald -- * The Theorem Theorem: If If, Then Then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 19:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14330 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:58:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14325 for ; Thu, 3 Dec 1998 19:58:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA02659; Thu, 3 Dec 1998 19:58:02 -0800 (PST) (envelope-from dillon) Date: Thu, 3 Dec 1998 19:58:02 -0800 (PST) From: Matthew Dillon Message-Id: <199812040358.TAA02659@apollo.backplane.com> To: Christopher Nielsen Cc: current@FreeBSD.ORG Subject: Re: buildworld failure from ICMP_BANDLIM References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The #ifdef KERNEL I just commited should fix this. Sorry about that! -Matt :/usr/src/usr.bin/netstat/atalk.c :gzip -cn /usr/src/usr.bin/netstat/netstat.1 > netstat.1.gz :In file included from /usr/src/usr.bin/netstat/inet.c:55: :/usr/obj/elf/usr/src/tmp/usr/include/netinet/icmp_var.h:40: :opt_icmp_bandlim.h: No such file or directory :*** Error code 1 :1 error :*** Error code 2 :1 error :*** Error code 2 :1 error :*** Error code 2 :1 error :*** Error code 2 :1 error :*** Error code 2 :1 error : :-- :Christopher Nielsen :Scient: The eBusiness Systems Innovator : :cnielsen@scient.com : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 20:07:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15243 for freebsd-current-outgoing; Thu, 3 Dec 1998 20:07:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15238 for ; Thu, 3 Dec 1998 20:06:58 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id XAA14308; Thu, 3 Dec 1998 23:10:08 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 3 Dec 1998 23:10:08 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Ronald Kuehn cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812040355.EAA02620@merlin.rz.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > > The /var filesystem does not have soft updates enabled. > I got a dump, but not from a debugging kernel. > > [ current as of Dec 2 ] Just wondering, why are people running softupdates and non-softupdates on the same box, or just plain not using softupdates? I thought that it is as reliable as regular mounts and faster? Or are there issues that I haven't noticed? Or are you guys testing for the FreeBSD project? -Alfred > > Bye, > Ronald > -- > * The Theorem Theorem: If If, Then Then. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 20:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18012 for freebsd-current-outgoing; Thu, 3 Dec 1998 20:34:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17996 for ; Thu, 3 Dec 1998 20:33:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA03635; Thu, 3 Dec 1998 20:33:39 -0800 (PST) (envelope-from dillon) Date: Thu, 3 Dec 1998 20:33:39 -0800 (PST) From: Matthew Dillon Message-Id: <199812040433.UAA03635@apollo.backplane.com> To: Alfred Perlstein Cc: Ronald Kuehn , freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> The /var filesystem does not have soft updates enabled. :> I got a dump, but not from a debugging kernel. :> :> [ current as of Dec 2 ] : :Just wondering, why are people running softupdates and non-softupdates on :the same box, or just plain not using softupdates? : :I thought that it is as reliable as regular mounts and faster? Or are :there issues that I haven't noticed? : :Or are you guys testing for the FreeBSD project? : :-Alfred I don't know about everyone else, but I'm running softupdates on all of our production FreeBSD-current boxes at BEST (a grand total of 1 machine at the moment), and all of my home machines (3 boxes). All partitions. I've had zero problems with it. The plan at BEST is to turn on softupdates on all partitions on all -current machines as we migrate boxes over from -stable over the next few months and since BEST is a commercial environment, we've paid Kick's site license fee. I am running with vfs.ffs.doreallocblks=0, however until the crashes / crash confusion is resolved - the reported crashes/fs-corruption is just too dangerous for me to risk turning it on. Once fixed I expect doreallocblks to be a boon to the news and web servers. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 20:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18283 for freebsd-current-outgoing; Thu, 3 Dec 1998 20:35:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (75-sweet.camalott.com [208.239.153.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18275 for ; Thu, 3 Dec 1998 20:35:32 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA37662; Thu, 3 Dec 1998 22:34:40 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: Robert Nordier , jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <199812032323.PAA00785@dingo.cdrom.com> From: Joel Ray Holveck Date: 03 Dec 1998 22:34:38 -0600 In-Reply-To: Mike Smith's message of "Thu, 03 Dec 1998 15:23:46 -0800" Message-ID: <867lw8v82p.fsf@detlev.UUCP> Lines: 22 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> OK. Booting out of Windows into a carefully prepared and disinfected >> DOS session has a chance of coming tolerably close to resembling a >> cold boot: at least with kernel vm86 usage as it is at the moment. >> But if one is exiting Windows in order to load FreeBSD, why boot >> into DOS anyway? (It's kind of like going to wash your hands before >> dinner, but then stopping off for a pee on your way back to the >> table.) > Because you may have the FreeBSD install on the DOS partition, ie. not > having a partition of its own. So you can't guarantee that you can > activate a different partition and boot from it. So is my pursuit of FBSDBOOT worthwhile, or should I abandon it in favor of Robert's suggestion? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 20:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18859 for freebsd-current-outgoing; Thu, 3 Dec 1998 20:50:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18846 for ; Thu, 3 Dec 1998 20:50:46 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA09848; Fri, 4 Dec 1998 15:20:14 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id PAA29034; Fri, 4 Dec 1998 15:19:12 +1030 (CST) Message-ID: <19981204151911.N441@freebie.lemis.com> Date: Fri, 4 Dec 1998 15:19:11 +1030 From: Greg Lehey To: Mike Smith Cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? References: <199812030213.SAA03115@dingo.cdrom.com> <199812030222.SAA03196@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812030222.SAA03196@dingo.cdrom.com>; from Mike Smith on Wed, Dec 02, 1998 at 06:22:02PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 2 December 1998 at 18:22:02 -0800, Mike Smith wrote: >>> or to unload unused segments and >>> reload them on the fly during further probe/attach requests (ala Linux). >> >> It would certainly be feasible to arrange for the firmware images to be >> loaded from separate files, should that be an acceptable alternative. >> I'm open to suggestions on how to make this economical and robust... > > I should probably have expanded here; I was thinking for some time > about the usefulness of optionally having two modules associated with a > driver; the core driver code and the 'init' module for the code. You'd > normally put these into two separate files, so for 'foo' you'd > have foo.ko and foo_init.ko. Isn't this something that could be more elegantly handled by different sections in an ELF file? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 21:14:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20461 for freebsd-current-outgoing; Thu, 3 Dec 1998 21:14:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20453 for ; Thu, 3 Dec 1998 21:14:52 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id VAA68094; Thu, 3 Dec 1998 21:22:46 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812040522.VAA68094@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: from Alfred Perlstein at "Dec 3, 1998 11:10: 8 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Thu, 3 Dec 1998 21:22:46 -0800 (PST) Cc: kuehn@rz.tu-clausthal.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alfred Perlstein: > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > > The /var filesystem does not have soft updates enabled. > > I got a dump, but not from a debugging kernel. > > > > [ current as of Dec 2 ] > > Just wondering, why are people running softupdates and non-softupdates on > the same box, or just plain not using softupdates? > > I thought that it is as reliable as regular mounts and faster? Or are > there issues that I haven't noticed? > > Or are you guys testing for the FreeBSD project? > Well, FFS with sync mounts has been reliable for me for 4 years until this commit. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 21:27:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21729 for freebsd-current-outgoing; Thu, 3 Dec 1998 21:27:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21718 for ; Thu, 3 Dec 1998 21:27:36 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id AAA00243 for ; Fri, 4 Dec 1998 00:27:20 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20192; Fri, 4 Dec 1998 00:27:20 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA15833 for freebsd-current@freebsd.org; Fri, 4 Dec 1998 00:27:20 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812040527.AAA15833@bb01f39.unx.sas.com> Subject: Bug in pax -s option w/ fix To: freebsd-current@FreeBSD.ORG Date: Fri, 4 Dec 1998 00:27:20 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, There is a bug in /bin/pax -s option processing. The code assumes that all pattern matches will occur at offset zero of the source string. The bug causes the input source string pointer to be incremented by the offset of the end of the match, instead of it's length. The fix is to only increment the pointer by the length of the pattern match (eo-so). Of course, the one example in the man page shows a situation where the match occurs at offset 0. Would someone please review and commit the following patch created on a 3.0-19981124-SNAP system. I assume that the NET2_REGEX side is broken also, but I don't have access to a system to fix and test that variation (what uses NET2_REGEX?). --- /usr/src/bin/pax/pat_rep.c.old Fri May 15 02:27:44 1998 +++ /usr/src/bin/pax/pat_rep.c Fri Dec 4 00:11:44 1998 @@ -1002,7 +1002,7 @@ # ifdef NET2_REGEX inpt = pt->rcmp->endp[0]; # else - inpt += pm[0].rm_eo; + inpt += pm[0].rm_eo - pm[0].rm_so; # endif if ((outpt == endpt) || (*inpt == '\0')) Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 21:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22968 for freebsd-current-outgoing; Thu, 3 Dec 1998 21:46:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22963 for ; Thu, 3 Dec 1998 21:46:14 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA22510; Thu, 3 Dec 1998 21:44:50 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022508; Thu, 3 Dec 98 21:44:49 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA25389; Thu, 3 Dec 1998 21:44:49 -0800 (PST) From: Archie Cobbs Message-Id: <199812040544.VAA25389@bubba.whistle.com> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812040355.EAA02620@merlin.rz.tu-clausthal.de> from Ronald Kuehn at "Dec 4, 98 04:55:29 am" To: kuehn@rz.tu-clausthal.de (Ronald Kuehn) Date: Thu, 3 Dec 1998 21:44:49 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ronald Kuehn writes: > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > > The /var filesystem does not have soft updates enabled. > I got a dump, but not from a debugging kernel. If your kernel sources haven't changed, you can recompile the kernel after doing a "config -g" and get a kernel with symbols. Then you can run gdb -k on it. (You probably already know this :) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 22:36:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26543 for freebsd-current-outgoing; Thu, 3 Dec 1998 22:36:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26535 for ; Thu, 3 Dec 1998 22:36:55 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA06444; Fri, 4 Dec 1998 17:36:36 +1100 Date: Fri, 4 Dec 1998 17:36:36 +1100 From: Bruce Evans Message-Id: <199812040636.RAA06444@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, seggers@semyam.dinoco.de Subject: Re: nlpt and severe system slow down Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> controller ppbus0 >> controller ppc0 at isa? irq 7 vector ppcintr >> device nlpt0 at ppbus? > >Mine is this: > >controller ppbus0 >device nlpt0 at ppbus? >device plip0 at ppbus? >controller ppc0 at isa? port ? tty irq 7 vector ppcintr >controller ppc1 at isa? port ? tty irq 5 vector ppcintr > >I added the plip0 entry to be able to attach another system to plip1 >one day. None connected, yet and plip1 is not configured by the >network code during startup. The device class should be "net" for plip. See the plip man page. This is incompatible (*) with the device class being tty or cam - you should only use ppc for one of nlpt, plip or vpo. (*) Except when slip is statically configured, net and tty are essentially the same for statically configured devices. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 23:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29673 for freebsd-current-outgoing; Thu, 3 Dec 1998 23:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29668 for ; Thu, 3 Dec 1998 23:11:14 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id XAA22955 for ; Thu, 3 Dec 1998 23:10:22 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022950; Thu, 3 Dec 98 23:10:03 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id XAA25670 for freebsd-current@freebsd.org; Thu, 3 Dec 1998 23:10:03 -0800 (PST) From: Archie Cobbs Message-Id: <199812040710.XAA25670@bubba.whistle.com> Subject: Bug in i386/apm/apm.c? To: freebsd-current@FreeBSD.ORG Date: Thu, 3 Dec 1998 23:10:03 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks like a bug... --- apm.c Thu Dec 3 23:09:47 1998 +++ apm.c.new Thu Dec 3 23:09:44 1998 @@ -795,7 +795,7 @@ sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; sc->cs32_limit = apm_cs32_limit - 1; if (apm_cs16_limit == 0) - apm_cs16_limit == apm_cs32_limit; + apm_cs16_limit = apm_cs32_limit; sc->cs16_limit = apm_cs16_limit - 1; sc->ds_limit = apm_ds_limit - 1; sc->cs_entry = apm_cs_entry; -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 23:29:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01485 for freebsd-current-outgoing; Thu, 3 Dec 1998 23:29:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA01462 for ; Thu, 3 Dec 1998 23:29:37 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27054 invoked by uid 1001); 4 Dec 1998 07:29:21 +0000 (GMT) To: joelh@gnu.org Cc: mike@smith.net.au, rnordier@nordier.com, jkh@zippy.cdrom.com, Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: Your message of "03 Dec 1998 22:34:38 -0600" References: <867lw8v82p.fsf@detlev.UUCP> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 04 Dec 1998 08:29:21 +0100 Message-ID: <27052.912756561@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Because you may have the FreeBSD install on the DOS partition, ie. not > > having a partition of its own. So you can't guarantee that you can > > activate a different partition and boot from it. > > So is my pursuit of FBSDBOOT worthwhile, or should I abandon it in > favor of Robert's suggestion? To me, FBSDBOOT is worthwhile. I have a laptop I've been unable to boot with FreeBSD using a boot manager. Using FBSDBOOT works just fine. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 23:35:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02455 for freebsd-current-outgoing; Thu, 3 Dec 1998 23:35:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02252 for ; Thu, 3 Dec 1998 23:35:03 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA09899; Fri, 4 Dec 1998 18:34:11 +1100 Date: Fri, 4 Dec 1998 18:34:11 +1100 From: Bruce Evans Message-Id: <199812040734.SAA09899@godzilla.zeta.org.au> To: dfr@nlsystems.com, eivind@yes.no Subject: Re: 3.0 and double operations in device drivers Cc: freebsd-current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it, tinguely@plains.NoDak.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > > > My question is: "Is floating point math now taboo in the kernel?" >> > > >> > > it has always been! >> > >> > I asked for that one :). remove taboo and replace with "forbidden". >> >> It always has been. >> >> (Ie, it has never worked reliably, and this has been a known property >> of the design). What design? Most implementations don't support floating point in the kernel because supporting would slow down interrupt handling and context switching. Since some implementations don't support it, it should never be used. >On the alpha, any floating point instructions executed by the kernel >(except some very careful ones during task switching) should cause a >panic. Same for all versions of FreeBSD on i386's, except there are also some very careful ones in some versions of bcopy() and bzero(). Actually, not so careful. The panic for unexepected ones went away, apparently to support unexpected ones in bcopy() or bzero(). See trap.c rev.1.78. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 3 23:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03812 for freebsd-current-outgoing; Thu, 3 Dec 1998 23:47:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA03807 for ; Thu, 3 Dec 1998 23:47:55 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27361 invoked by uid 1001); 4 Dec 1998 07:47:39 +0000 (GMT) To: dg@root.com Cc: cdillon@wolves.k12.mo.us, jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: Your message of "Thu, 03 Dec 1998 18:38:05 -0800" References: <199812040238.SAA27887@root.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 04 Dec 1998 08:47:39 +0100 Message-ID: <27359.912757659@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I posted a message a while back when this bug first started to bite. I > >have a good coredump or two (using debugging kernel and all) if anyone > >wants them. Kirk told me he would look at Greg's dump first and get > >back to me if he needed more samples, but I haven't heard from him. I > >can build a more recent world (mine is a couple weeks old now) and turn > >on vfs.ffs.doreallocblks again to get a more recent dump. It occurrs > >without having to do much work. My system has been rock solid ever > >since I set vfs.ffs.doreallocblks=0 at boot, so it isn't hardware > >instability like I thought it may have been. > > There was a bug found in the original code that has been fixed. What we're > interested in now is continued problems *after* the bugfix (about Nov 18th). As mentioned before, I get this panic on an 3.0-19981123-SNAP system (vfs_cluster.c 1.74), SMP, no softupdates, with vfs.ffs.doreallocblks=1. The panic happens during heavy disk *and* network activity. If anybody wants backtraces or wants to play with the core dumps, they can be made available (warning: the machine has 512 MB of memory, so the core dump is rather big). I've sent a message to Kirk McKusick asking if he wants any of this, but haven't received an answer. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xf0134b2e in panic (fmt=0xf01c5d81 "ffs_blkfree: bad size") at ../../kern/kern_shutdown.c:446 #2 0xf01c5ede in ffs_blkfree (ip=0xf1569b00, bno=6442, size=8192) at ../../ufs/ffs/ffs_alloc.c:1300 #3 0xf01c45a4 in ffs_reallocblks (ap=0xf95ffde4) at ../../ufs/ffs/ffs_alloc.c:523 #4 0xf015216b in cluster_write (bp=0xf6496350, filesize=105562112) at vnode_if.h:1035 #5 0xf01cba67 in ffs_write (ap=0xf95ffebc) at ../../ufs/ufs/ufs_readwrite.c:368 #6 0xf015c14b in vn_write (fp=0xf15686c0, uio=0xf95fff40, cred=0xf1560280) at vnode_if.h:331 #7 0xf013d803 in writev (p=0xf95a3840, uap=0xf95fff94) at ../../kern/sys_generic.c:356 #8 0xf01f5d0b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 714452012, tf_esi = 2553, tf_ebp = 714452172, tf_isp = -111149084, tf_ebx = 0, tf_edx = 16, tf_ecx = 135401472, tf_eax = 121, tf_trapno = 12, tf_err = 2, tf_eip = 135040412, tf_cs = 31, tf_eflags = 514, tf_esp = 714451972, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #9 0xf01e4e1c in Xint0x80_syscall () #10 0x809c311 in ?? () #11 0x809c2b6 in ?? () #12 0x807ce62 in ?? () #13 0x805cc46 in ?? () #14 0x805a882 in ?? () #15 0x8093da1 in ?? () #16 0x8093c61 in ?? () #17 0x80b063c in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 00:34:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07849 for freebsd-current-outgoing; Fri, 4 Dec 1998 00:34:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07844 for ; Fri, 4 Dec 1998 00:34:42 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA13942; Fri, 4 Dec 1998 19:34:21 +1100 Date: Fri, 4 Dec 1998 19:34:21 +1100 From: Bruce Evans Message-Id: <199812040834.TAA13942@godzilla.zeta.org.au> To: archie@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: Bug in i386/apm/apm.c? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This looks like a bug... > >--- apm.c Thu Dec 3 23:09:47 1998 >+++ apm.c.new Thu Dec 3 23:09:44 1998 >@@ -795,7 +795,7 @@ > sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; > sc->cs32_limit = apm_cs32_limit - 1; > if (apm_cs16_limit == 0) >- apm_cs16_limit == apm_cs32_limit; >+ apm_cs16_limit = apm_cs32_limit; > sc->cs16_limit = apm_cs16_limit - 1; > sc->ds_limit = apm_ds_limit - 1; > sc->cs_entry = apm_cs_entry; PR: 8280 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 00:42:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08772 for freebsd-current-outgoing; Fri, 4 Dec 1998 00:42:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08761 for ; Fri, 4 Dec 1998 00:42:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA70864; Fri, 4 Dec 1998 00:43:43 -0800 (PST) To: Bruce Evans cc: archie@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: Bug in i386/apm/apm.c? In-reply-to: Your message of "Fri, 04 Dec 1998 19:34:21 +1100." <199812040834.TAA13942@godzilla.zeta.org.au> Date: Fri, 04 Dec 1998 00:43:42 -0800 Message-ID: <70792.912761022@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PR: 8280 Seems odd that nobody's committed it - it's been there since October and each of the 3 fixes appears to be in the semi-obvious category (the last two being of a more cosmetic nature than the first). Having disclosed its existence, you at least can't claim ignorance of the PR. :-) It definitely came in under my own radar. I think I get too much email. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 01:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11851 for freebsd-current-outgoing; Fri, 4 Dec 1998 01:17:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11843 for ; Fri, 4 Dec 1998 01:17:26 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA16573; Fri, 4 Dec 1998 20:17:05 +1100 Date: Fri, 4 Dec 1998 20:17:05 +1100 From: Bruce Evans Message-Id: <199812040917.UAA16573@godzilla.zeta.org.au> To: scrappy@hub.org, ventrex.freebsd@UNDER.suspicion.org Subject: Re: syslogd@hub messages being broadcast... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I usually see that when swap is about to completely fill up and the system >is on it's way to a downward load/swap spiral. Perhaps it is caused by the broken line buffering in syslogd. MAXLINE is 1024, so syslog will insert bogus line breaks whenever the message buffer contains more than about 1024 characters. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 01:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13748 for freebsd-current-outgoing; Fri, 4 Dec 1998 01:54:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13738 for ; Fri, 4 Dec 1998 01:54:41 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca36-54.ix.netcom.com [207.92.172.54]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA07932 for ; Fri, 4 Dec 1998 01:54:24 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id BAA23296; Fri, 4 Dec 1998 01:54:19 -0800 (PST) Date: Fri, 4 Dec 1998 01:54:19 -0800 (PST) Message-Id: <199812040954.BAA23296@silvia.hip.berkeley.edu> To: current@FreeBSD.ORG Subject: weird rsh hang From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying some parallel gzip's by trying a rsh mach1 cat file | gzip | rsh mach1 cat \> file.newname For some reason, this is turning up a large number of hung connections. === ## ps gxwwl UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND : 0 648 1 157 2 0 1272 648 select Ss ?? 2:19.74 /usr/local/sbin/sshd (sshd1) 0 3357 648 1 2 0 1296 900 select S ?? 0:01.06 /usr/local/sbin/sshd (sshd1) 0 4762 1 214 18 0 452 256 pause Is ?? 0:00.04 csh -c /usr/local/packages/pcompress packages/All/asclock-1.0.tar 0 4780 4762 212 10 0 496 188 wait I ?? 0:00.01 /bin/sh /usr/local/packages/pcompress packages/All/asclock-1.0.tar 0 4792 4780 178 2 0 780 488 select I ?? 0:00.02 rsh m16 cat /usr/local/packages/packages/All/asclock-1.0.tar 0 4793 4780 173 -6 0 568 316 piperd I ?? 0:00.23 gzip -c --best 0 4794 4780 177 2 0 780 516 select I ?? 0:00.02 rsh m16 cat > /usr/local/packages/packages/compressed/asclock-1.0.tgz 0 4799 4792 214 81 0 0 0 - Z ?? 0:00.00 (rsh) 0 4801 4794 177 -6 0 780 516 piperd I ?? 0:00.00 rsh m16 cat > /usr/local/packages/packages/compressed/asclock-1.0.tgz 0 5347 1 188 18 0 452 256 pause Is ?? 0:00.04 csh -c /usr/local/packages/pcompress packages/All/cal-3.5.tar 0 5369 5347 217 10 0 496 188 wait I ?? 0:00.01 /bin/sh /usr/local/packages/pcompress packages/All/cal-3.5.tar 0 5391 5369 188 2 0 780 488 select I ?? 0:00.02 rsh m16 cat /usr/local/packages/packages/All/cal-3.5.tar 0 5392 5369 207 -6 0 568 320 piperd I ?? 0:00.16 gzip -c --best 0 5393 5369 164 2 0 780 516 select I ?? 0:00.02 rsh m16 cat > /usr/local/packages/packages/compressed/cal-3.5.tgz 0 5397 5391 218 82 0 0 0 - Z ?? 0:00.00 (rsh) 0 5401 5393 164 -6 0 780 516 piperd I ?? 0:00.00 rsh m16 cat > /usr/local/packages/packages/compressed/cal-3.5.tgz 0 6634 635 91 10 0 176 36 nanslp S ?? 0:00.00 sleep 5 0 23514 648 0 2 0 1280 908 select I ?? 0:00.85 /usr/local/sbin/sshd (sshd1) 0 23756 648 0 2 0 1280 896 select I ?? 0:00.67 /usr/local/sbin/sshd (sshd1) 0 3666 3633 0 10 0 1608 1004 wait S p0 0:01.08 bash : === I get about 10 of these for 1,500 connections over 3 machines. Any ideas? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 01:58:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14126 for freebsd-current-outgoing; Fri, 4 Dec 1998 01:58:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14121 for ; Fri, 4 Dec 1998 01:58:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.71]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA562A; Fri, 4 Dec 1998 10:58:33 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812032343.PAA03354@devel.dns-host.com> Date: Fri, 04 Dec 1998 11:03:58 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Icom Development Subject: RE: libc_r pthread build problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Dec-98 Icom Development wrote: > Hi, > My "make" in /usr/src fails with the errors I have appended, > on uthread_mutex.c. Have I missed an update or is this a known problem? > > --- BEGIN INCLUDED TEXT --- > ===> lib/libc_r > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include > -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale > -DBROKEN_DES -DYP -c /usr/src/lib/libc_r/uthread/uthread_mutex.c -o > uthread_mutex.o > /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function > `pthread_mutex_init': > /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: `PTHREAD_MUTEX_DEFAULT' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: (Each undeclared identifier > is reported only once > /usr/src/lib/libc_r/uthread/uthread_mutex.c:56: for each function it appears > in.) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:78: `PTHREAD_MUTEX_NORMAL' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:79: `PTHREAD_MUTEX_ERRORCHECK' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:84: `PTHREAD_MUTEX_RECURSIVE' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:90: warning: unreachable code at > beginning of switch statement > /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function > `pthread_mutex_trylock': > /usr/src/lib/libc_r/uthread/uthread_mutex.c:179: `PTHREAD_MUTEX_NORMAL' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:180: `PTHREAD_MUTEX_DEFAULT' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:181: `PTHREAD_MUTEX_ERRORCHECK' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:193: `PTHREAD_MUTEX_RECURSIVE' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:214: warning: unreachable code at > beginning of switch statement > /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function > `pthread_mutex_lock': > /usr/src/lib/libc_r/uthread/uthread_mutex.c:248: `PTHREAD_MUTEX_NORMAL' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:257: `PTHREAD_MUTEX_ERRORCHECK' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:264: `PTHREAD_MUTEX_DEFAULT' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:294: `PTHREAD_MUTEX_RECURSIVE' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:329: warning: unreachable code at > beginning of switch statement > /usr/src/lib/libc_r/uthread/uthread_mutex.c: In function > `pthread_mutex_unlock': > /usr/src/lib/libc_r/uthread/uthread_mutex.c:358: `PTHREAD_MUTEX_NORMAL' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:359: `PTHREAD_MUTEX_DEFAULT' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:360: `PTHREAD_MUTEX_ERRORCHECK' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:377: `PTHREAD_MUTEX_RECURSIVE' > undeclared (first use this function) > /usr/src/lib/libc_r/uthread/uthread_mutex.c:401: warning: unreachable code at > beginning of switch statement > --- END INCLUDED TEXT --- I have cvsupped twice or thrice (about 6 hours in between) in between builds to make sure I didn't miss a commit... looking at the file uthread_mutex.c reveals two include files which might contain the PTHREAD declarations: pthread.h and pthread_private.h pthread.h contains the declarations after examination. Curious thing is that the datestamp is from November the 29th, just a day or two before the problems started... snip of pthread.h enum pthread_mutextype { PTHREAD_MUTEX_DEFAULT = 1, PTHREAD_MUTEX_RECURSIVE = 2, PTHREAD_MUTEX_NORMAL = 3, PTHREAD_MUTEX_ERRORCHECK = 4, MUTEX_TYPE_MAX }; This enumeration looks good to me... Now to look at uthread_mutex.c: #ifdef _THREAD_SAFE #include #include "pthread_private.h" Most logical conclusion I can make is that _THREAD_SAFE isn't defined somewhere... Else we would have the declarations of pthread.h at our disposal. Someone care to enlighten me some more on the matter? Because I have no clue where to look for the #define of _THREAD_SAFE. Also some more info upon what it's trying to do here might help my understanding somewhat better... It's trying to build up some sort of thread routines, I read through pthread(3) but cannot see what uthread is for then... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 02:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14810 for freebsd-current-outgoing; Fri, 4 Dec 1998 02:04:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-60-dbn.dial-up.net [196.34.155.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14789 for ; Fri, 4 Dec 1998 02:04:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA01606; Fri, 4 Dec 1998 11:58:55 +0200 (SAT) From: Robert Nordier Message-Id: <199812040958.LAA01606@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199812040016.QAA01175@dingo.cdrom.com> from Mike Smith at "Dec 3, 98 04:16:42 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 4 Dec 1998 11:58:53 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Because you may have the FreeBSD install on the DOS partition, ie. not > > > having a partition of its own. So you can't guarantee that you can > > > activate a different partition and boot from it. > > > > OK, if this translates to "demo", then we're talking marketing- > > driven solutions, and completely different rules apply. > > Uh, no, not at all. There are situations where to get FreeBSD into an > environment, we'll have to be able to operate like this. Whether we do > it with a "UMSDOS" style approach, or with a monolithic 'filesystem > file', it'd be worthwhile. > > > Sample choices: > > > > o Get vm86 working reliably with a virus or two swirling > > around, and a couple of TSRs trying to pop up. > > See the new fbsdboot sample I sent you; it'd be useful to know how > vulnerable this might be to that. I think the new fbsdboot sample you sent me has a good chance of totally confusing viruses and TSRs. :) > TBH, I can't see any problem with > saying "if you have a viral infection, we can't help you". Well, that's the "yuk" approach; we could also take the "yum" approach: RELEASE NOTES FreeBSD Release 3.x-RELEASE 1.1. KERNEL CHANGES ------------------- o Certain DOS viruses are now supported. In some cases, this support includes the corruption of UFS and other non-DOS partitions. However complete system devastation cannot always be reliably guaranteed, as results may be affected by incomplete emulation of the DOS environment.) > > > o Use a boot floppy. > > Ick. We have to be able to do better than that. 8) I'm pretty sure there are better solutions. If this isn't a demo, I just don't have a very clear idea what we're aiming at, only what to avoid. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 02:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15477 for freebsd-current-outgoing; Fri, 4 Dec 1998 02:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA15472 for ; Fri, 4 Dec 1998 02:12:08 -0800 (PST) (envelope-from andrea.franceschini@linet.it) Received: from oma.linet.it (unverified [194.185.24.77]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 04 Dec 1998 11:02:24 +0100 Message-ID: <007a01be1f6c$0abf70c0$4d18b9c2@oma.linet.it> Reply-To: "andrea" From: "andrea" To: "Doug White" Cc: Subject: R: ip-masquerading.natd,ip-aliasing .... Date: Fri, 4 Dec 1998 10:54:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Messaggio originale----- Da: Doug White A: andrea Cc: freebsd-current@FreeBSD.ORG Data: giovedì 3 dicembre 1998 0.40 Oggetto: Re: ip-masquerading.natd,ip-aliasing .... >On Wed, 2 Dec 1998, andrea wrote: > >> I'm looking for a way to configure my intranet using natd. >> The problem is that the configuration that i need is a little unsual and i >> wonder if is applicable. >> >> The configuration is as follow: >> >> On the Same LAN : >> >> 1 - Web Server (with routable Ip-address) >> 2 - Mail Server ( "" "" "" ) >> 3 - 1 router connected to the InterNet. >> 4 - Many other boxes with not Routeble ip addresses (192.168.. ) >> >> So i have 2 subnet on the same phisical net. >> >> What i'm wondering is: >> >> It's possible to share in the same phisical Lan( eg without gateway >> with 2+ Ether Card) between 2 networks? > >If you want to use natd, you should use it's redirect_port feature instead >of mixing the networks. This way you get the filtering feature of natd >protecting your mail and web server. The downturn is that you loose >flexibility on your web server -- if you add services you'll have to set >up redirect rules for it. > >I don't know how fancy your router is, if it can be taught to natd certain >packets or not (I think ipfw can do it, not sure). > >> I'have tried assigning 2 ip address at the same interface ,and using >> this machine as a gateway on the same phisical net. > >You have to use an alias (with the netmask of that network, not >0xffffffff) on the interface to get the second IP programmed in. First of all thank you for replying!:) Now the configuration you described is pretty the same of mine. And that's the problem it doesn't works at all.:( The rule in the firewall that 'divert' the socket to natd seem to work,because i can see the counters of packets increasing.. But natd doesn't get anything ,or so seems( i set-up natd in verbose mode but nothing happens...) I need a sort of 'example' of a working configuration in order to debug the mine. Bye;) > >Doug White >Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve >http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 03:19:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19161 for freebsd-current-outgoing; Fri, 4 Dec 1998 03:19:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19156 for ; Fri, 4 Dec 1998 03:19:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id DAA20039; Fri, 4 Dec 1998 03:19:39 -0800 (PST) (envelope-from obrien) Message-ID: <19981204031938.A20011@nuxi.com> Date: Fri, 4 Dec 1998 03:19:38 -0800 From: "David O'Brien" To: Julian Elischer , current@FreeBSD.ORG Subject: Re: FreeBSD fsck updated Reply-To: obrien@NUXI.com References: <199811230603.WAA02649@salsa.gv.tsc.tdk.com> <36661125.31DFF4F5@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36661125.31DFF4F5@whistle.com>; from Julian Elischer on Wed, Dec 02, 1998 at 08:18:45PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What does everyone think? I now kirk doesn't like the > noisy messages about the clean and modified bits.. I prefer them. This isn't MS-Win$hit. I don't want information hidden or kept from me. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 04:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24971 for freebsd-current-outgoing; Fri, 4 Dec 1998 04:13:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24966 for ; Fri, 4 Dec 1998 04:13:42 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA26965; Fri, 4 Dec 1998 23:13:22 +1100 Date: Fri, 4 Dec 1998 23:13:22 +1100 From: Bruce Evans Message-Id: <199812041213.XAA26965@godzilla.zeta.org.au> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: FreeBSD fsck updated Cc: Don.Lewis@tsc.tdk.com, mckusick@McKusick.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is this the verboseness you were complaining about? > > >diff -cr fsck/pass5.c fsck.julian/pass5.c >*** fsck/pass5.c Wed Dec 2 18:41:11 1998 >--- fsck.julian/pass5.c Wed Dec 2 16:26:18 1998 >*************** >*** 355,361 **** > && dofix(&idesc[0], "FREE BLK COUNT(S) WRONG IN SUPERBLK")) { > memmove(&fs->fs_cstotal, &cstotal, sizeof *cs); > fs->fs_ronly = 0; ^^^^^^^^^^^^^^^^^ >- fs->fs_fmod = 0; ^^^^^^^^^^^^^^^^ > sbdirty(); > } > } >--- 355,378 ---- > && dofix(&idesc[0], "FREE BLK COUNT(S) WRONG IN SUPERBLK")) { > memmove(&fs->fs_cstotal, &cstotal, sizeof *cs); > fs->fs_ronly = 0; > sbdirty(); >+ } >+ if (fs->fs_fmod != 0) { >+ pwarn("MODIFIED FLAG SET IN SUPERBLOCK"); >+ if (preen) >+ printf(" (FIXED)\n"); >+ if (preen || reply("FIX") == 1) { >+ fs->fs_fmod = 0; >+ sbdirty(); >+ } >+ } >+ if (fs->fs_clean == 0) { >+ pwarn("CLEAN FLAG NOT SET IN SUPERBLOCK"); >+ if (preen) >+ printf(" (FIXED)\n"); >+ if (preen || reply("FIX") == 1) { >+ fs->fs_clean = 1; >+ sbdirty(); >+ } > } > } I like the warning for fs_clean == 0 in the preen case. The code for setting fs_clean in the !preen case seems to have rotted - there is other code that sets the fs_clean flag and it usually sets it even if you answer 'n' here. Clearing fs_fmod here seems to be bogus. It is set (to 0 or 1) unconditionally at mount time. Similarly for fs_ronly. I don't see how it can be right to clear these flags here _only_ when a certain type of inconsistency (that has nothing to do with these flags) is fixed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 04:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26731 for freebsd-current-outgoing; Fri, 4 Dec 1998 04:37:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26725 for ; Fri, 4 Dec 1998 04:37:52 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id TAA52159; Thu, 3 Dec 1998 19:37:10 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: S ren Schmidt cc: dg@root.com, jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: panic: ffs_blkfree: bad size In-reply-to: Your message of "Thu, 03 Dec 1998 09:34:49 +0100." <199812030834.JAA10358@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 03 Dec 1998 19:37:09 -0500 Message-ID: <52155.912731829@gjp.erols.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA26727 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S ren Schmidt wrote in message ID <199812030834.JAA10358@freebsd.dk>: > I dont know If I'm one of the two, but it f*ks up here too, on ALL my > machines, except on my notebook which uses softupdates. > As has been stated before it has nothing to do with the machine being > loaded, on the contrary, here it dies when the machine is idle and > mail arrives or some such. My machine at home also crash(ed) regularly (like several times a day) after a recent kernel build. Did the sysctl magic and now its been up for 9 days. I don't have any panic messages 'cos its my X machine, but I think its fair to say that its related. This is a SMP machine, if that has any relevance. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 04:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26827 for freebsd-current-outgoing; Fri, 4 Dec 1998 04:39:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26822 for ; Fri, 4 Dec 1998 04:39:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA00655; Fri, 4 Dec 1998 04:36:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812041236.EAA00655@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Mike Smith , "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Fri, 04 Dec 1998 15:19:11 +1030." <19981204151911.N441@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 04:36:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wednesday, 2 December 1998 at 18:22:02 -0800, Mike Smith wrote: > >>> or to unload unused segments and > >>> reload them on the fly during further probe/attach requests (ala Linux). > >> > >> It would certainly be feasible to arrange for the firmware images to be > >> loaded from separate files, should that be an acceptable alternative. > >> I'm open to suggestions on how to make this economical and robust... > > > > I should probably have expanded here; I was thinking for some time > > about the usefulness of optionally having two modules associated with a > > driver; the core driver code and the 'init' module for the code. You'd > > normally put these into two separate files, so for 'foo' you'd > > have foo.ko and foo_init.ko. > > Isn't this something that could be more elegantly handled by different > sections in an ELF file? For paging, yes. For freeing and reloading, no; it would a level of finer granularity than the module, which is extra work and complexity that we don't really need. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 04:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27257 for freebsd-current-outgoing; Fri, 4 Dec 1998 04:47:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27249 for ; Fri, 4 Dec 1998 04:47:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA00704; Fri, 4 Dec 1998 04:41:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812041241.EAA00704@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: scrappy@hub.org, ventrex.freebsd@UNDER.suspicion.org, freebsd-current@FreeBSD.ORG Subject: Re: syslogd@hub messages being broadcast... In-reply-to: Your message of "Fri, 04 Dec 1998 20:17:05 +1100." <199812040917.UAA16573@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 04:41:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I usually see that when swap is about to completely fill up and the system > >is on it's way to a downward load/swap spiral. > > Perhaps it is caused by the broken line buffering in syslogd. MAXLINE is > 1024, so syslog will insert bogus line breaks whenever the message buffer > contains more than about 1024 characters. Actually, it's usually symptomatic of something being unable to allocate memory to print/format the error message. This phenomenon is very familiar to anyone that's worked with a low-memory system under real load. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 04:54:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27600 for freebsd-current-outgoing; Fri, 4 Dec 1998 04:54:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27578; Fri, 4 Dec 1998 04:53:43 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id NAA05307; Fri, 4 Dec 1998 13:55:13 +0100 (MET) Received: from cisco.aubi.de ([170.56.121.252]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id PAA12940; Fri, 4 Dec 1998 15:06:02 +0100 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id NAA09599; Fri, 4 Dec 1998 13:58:06 +0100 (CET) Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Fri, 4 Dec 1998 13:47:51 +0100 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'Gary Palmer'" , "'freebsd-current@freebsd.org'" Subject: RE: panic: ffs_blkfree: bad size Date: Fri, 4 Dec 1998 13:46:44 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA27583 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My machine at home also crash(ed) regularly (like several > times a day) after a > recent kernel build. Did the sysctl magic and now its been up > for 9 days. I > don't have any panic messages 'cos its my X machine, but I > think its fair to > say that its related. This is a SMP machine, if that has any > relevance. mine too, but only under heavy disk activity. I put it up to load 12.53 last week and it crashed. After reboot every cvsup did crash the machine. after sysctl now actually load 9.71 and stable... -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de MD1139-RIPE ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 05:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01391 for freebsd-current-outgoing; Fri, 4 Dec 1998 05:44:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01359 for ; Fri, 4 Dec 1998 05:44:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id FAA01043; Fri, 4 Dec 1998 05:41:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812041341.FAA01043@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 04 Dec 1998 11:58:53 +0200." <199812040958.LAA01606@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 05:41:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > See the new fbsdboot sample I sent you; it'd be useful to know how > > vulnerable this might be to that. > > I think the new fbsdboot sample you sent me has a good chance of > totally confusing viruses and TSRs. :) Ack. > > Ick. We have to be able to do better than that. 8) > > I'm pretty sure there are better solutions. If this isn't a demo, > I just don't have a very clear idea what we're aiming at, only what > to avoid. Ok. If it's a demo, the goal can be simply defined as: - Boot a relatively generic kernel off a DOS filesystem, from under DOS, with a relatively comprehensive feature set. Some things can be trimmed if they can't work in this environment. If it's not a demo, the goal is worse: - Provide full system functionality when booted from a DOS filesystem, from under DOS. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 07:47:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14362 for freebsd-current-outgoing; Fri, 4 Dec 1998 07:47:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14357 for ; Fri, 4 Dec 1998 07:47:23 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA24938; Fri, 4 Dec 1998 10:46:50 -0500 (EST) (envelope-from luoqi) Date: Fri, 4 Dec 1998 10:46:50 -0500 (EST) From: Luoqi Chen Message-Id: <199812041546.KAA24938@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, kuehn@rz.tu-clausthal.de Subject: Re: panic: ffs_blkfree: bad size Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had such a panic today too during cvsup activity. Two filesystems > don't have softupdates. All others do. The activity was on one > of those softupdates filesystems. > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > bno is a fs block number and for /var it almost surely can't be 13. This still points to a missing VOP_BMAP() somewhere. While I'm writing this message, I took another look at Kirk's patch. It seems to me that he forgot to call VOP_BMAP() for the last buf in the reallocation list. Try this patch, and see if you still get the panic, Index: vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.74 diff -u -r1.74 vfs_cluster.c --- vfs_cluster.c 1998/11/17 00:31:12 1.74 +++ vfs_cluster.c 1998/12/04 15:33:09 @@ -839,7 +839,10 @@ VOP_BMAP(bp->b_vp, bp->b_lblkno, NULL, &bp->b_blkno, NULL, NULL); } - buflist->bs_children[i] = last_bp; + buflist->bs_children[i] = bp = last_bp; + if (bp->b_blkno == bp->b_lblkno) + VOP_BMAP(bp->b_vp, bp->b_lblkno, NULL, &bp->b_blkno, + NULL, NULL); buflist->bs_nchildren = i + 1; return (buflist); } > The /var filesystem does not have soft updates enabled. > I got a dump, but not from a debugging kernel. > A dump from a non-debugging kernel is as good as a debugging one. Could you post a stack backtrace? > [ current as of Dec 2 ] > > Bye, > Ronald > -- > * The Theorem Theorem: If If, Then Then. > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 08:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17042 for freebsd-current-outgoing; Fri, 4 Dec 1998 08:08:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA16813 for ; Fri, 4 Dec 1998 08:07:55 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA12442 for current@freebsd.org; Fri, 4 Dec 1998 11:12:48 -0500 From: Bill Paul Message-Id: <199812041612.LAA12442@skynet.ctr.columbia.edu> Subject: New drivers and install floppy space To: current@FreeBSD.ORG Date: Fri, 4 Dec 1998 11:12:46 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm on the verge of committing four new fast ethernet device drivers to -current, however I'm a bit concerned about running out of space on the installation floppy (these drivers will be added to the GENERIC kernel). Figuring between 15 and 20K of object code per driver, is there enough room for me to do this, or am I asking for trouble? -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 08:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21176 for freebsd-current-outgoing; Fri, 4 Dec 1998 08:36:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21167 for ; Fri, 4 Dec 1998 08:36:28 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from dom by phmit.demon.co.uk with local (Exim 1.82 #1) id 0zlyEJ-00059w-00; Fri, 4 Dec 1998 16:37:19 +0000 To: current@FreeBSD.ORG Subject: sysinstall question X-Mailer: nmh v0.26 Organization: Palmer & Harvey McLane Date: Fri, 04 Dec 1998 16:37:18 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Question for all the sysinstall gurus: I've just downloaded the 3.0-RELEASE boot.flp and fixit.flp to try and fix my busted 3.0 bootblocks install (I shoulda read more first...). When I try to insert the fixit floppy, when prompted for, I'm getting: mountmsdosfs(): bad bpb Does anybody have an idea why this is? Why is it even trying to mount the fixit floppy as an msdos filesystem? I have tried two different floppy disks, just in case, BTW. Thanks for any help. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 08:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21222 for freebsd-current-outgoing; Fri, 4 Dec 1998 08:36:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21169 for ; Fri, 4 Dec 1998 08:36:29 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id RAA13879; Fri, 4 Dec 1998 17:15:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id RAA06588; Fri, 4 Dec 1998 17:04:29 +0100 (CET) (envelope-from andreas) Message-ID: <19981204170429.A6581@klemm.gtn.com> Date: Fri, 4 Dec 1998 17:04:29 +0100 From: Andreas Klemm To: Satoshi Asami , current@FreeBSD.ORG Subject: Re: weird rsh hang References: <199812040954.BAA23296@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812040954.BAA23296@silvia.hip.berkeley.edu>; from Satoshi Asami on Fri, Dec 04, 1998 at 01:54:19AM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 04, 1998 at 01:54:19AM -0800, Satoshi Asami wrote: > I get about 10 of these for 1,500 connections over 3 machines. Any ideas? Do you perhaps hit a resource limit ? When do this show up ? Within about 1000 connections or later. What I wanna say is ... are there always about x% of connections that hang or does it show up only after the machine already has xxxx TCP connections ?! Just a thought. Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 08:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22475 for freebsd-current-outgoing; Fri, 4 Dec 1998 08:50:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22469 for ; Fri, 4 Dec 1998 08:50:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA06069; Fri, 4 Dec 1998 08:50:13 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA02119; Fri, 4 Dec 1998 08:50:13 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 4 Dec 1998 08:50:13 -0800 (PST) Message-Id: <199812041650.IAA02119@vashon.polstra.com> To: aa8vb@pagesz.net Subject: Re: "ldconfig" strangeness on 3.0-RELEASE Newsgroups: polstra.freebsd.current In-Reply-To: <19981129102800.A1657@pagesz.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981129102800.A1657@pagesz.net>, Randall Hopper wrote: > Two things I notice that are rather strange. Are these bugs? > 1) You can completely re-initialize the LD path for ELF, but not for AOUT. > An example to illustrate: ... > It seems that ldconfig won't let you remove /usr/lib/aout. Why? They dynamic linkers always search in the standard directory (/usr/lib/aout for a.out, /usr/lib for ELF) as a last resort, no matter what the ldconfig hints file says. I suppose the a.out ldconfig adds /usr/lib/aout automatically to make that search go faster. It also makes "ldconfig -r" tell the whole story about where shared libraries will be found. Probably the ELF ldconfig should do the same thing. It wouldn't help efficiency-wise for ELF. But it would make the "ldconfig -r" listing reflect reality better. > 2) In /etc/rc.conf, we have: > > $ldconfig_paths & $ldconfig_paths_aout > > but we also have: > > /etc/ld.so.conf & /etc/ld-elf.so.conf > > (as documented in the ldconfig(8) man page) as places to store LD paths. The man page is wrong. We don't have any such files as ld.so.conf, as far as I know. Richard Kuhns has been revising the man page, so hopefully it will become more accurate soon. > 3) Why aren't these two directories in the default $ldconfig_paths_aout (AOUT) > in /etc/rc.conf? AFAIK, they're all AOUT: > > /usr/lib/aout /usr/lib/compat /usr/lib/aout is added automatically by /etc/rc. Regarding /usr/lib/compat: it is _not_ a.out on an ELF system. On an ELF system, a.out compat libraries are in /usr/lib/compat/aout. Also, your rc.conf file may be out of date. The current version in /usr/src/etc says: ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout" > > 4) Why is this directory in the default $ldconfig_paths (ELF)? It's all AOUT: > > /usr/lib/compat No, it's all ELF on an ELF system. At least, it's supposed to be. Didn't "make move-aout-libs" move the a.out libraries down into /usr/lib/compat/aout when you ran it? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 09:01:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23993 for freebsd-current-outgoing; Fri, 4 Dec 1998 09:01:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (47-sweet.camalott.com [208.239.153.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23982 for ; Fri, 4 Dec 1998 09:01:14 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id LAA45279; Fri, 4 Dec 1998 11:00:08 -0600 (CST) (envelope-from joelh) To: Robert Nordier Cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <199812040157.DAA21505@ceia.nordier.com> From: Joel Ray Holveck Date: 04 Dec 1998 11:00:05 -0600 In-Reply-To: Robert Nordier's message of "Fri, 4 Dec 1998 03:57:24 +0200 (SAT)" Message-ID: <863e6vvo4q.fsf@detlev.UUCP> Lines: 48 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Okay. If you feel it necessary to drop this thread, go ahead. If you >> can explain the cold boot rule's reasoning to me, even better. If you >> (or Mike or anybody) can tell me whether nextboot still works, >> terrific. > We're probably fundamentally at cross-purposes here. Okay. It appears that the difference of what we're discussing (which I only just realized, sorry) is the difference between what works, and what we want to support. > Regarding nextboot, I can't get your question into any kind of > context, sorry. Is this just an entirely separate issue, or > does "still works" relate to using FBSDBOOT versus not using > FBSDBOOT in some way? This is a related but separate issue. Two or three messages ago, you suggested that somebody write a Windows program that will either take command line parameters or pop up a cute dialog box to let a user select a BSD slice and kernel. Then this program would talk to the boot blocks and tell it to boot into that kernel with those parameters. After that, the program would reboot the system. It appears that the majority of people who want to use FBSDBOOT want to do so in order to have an icon on their Windows desktop or their start menu that would load FreeBSD. The others either don't have a BSD partition or need a DOS driver to configure their hardware. If we are bound and determined to drop support for the second category, then perhaps we can keep support for the first. Now, one way to write this program immediately suggests itself to me. Rewrite nextboot for Windows and put a GUI on it. Hence, my question. I don't know any other way to talk to the boot manager, although I'm open to suggestions. I myself don't use Windows. I don't use FBSDBOOT. The box that has both Windows and BSD on it has a partition manager. I won't be using this silly icon. This thread started out as me trying to give a user a simple solution to their problem, and now I'm to the point where by golly, I'm gonna get *something* useful accomplished out of it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 09:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24174 for freebsd-current-outgoing; Fri, 4 Dec 1998 09:02:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24168 for ; Fri, 4 Dec 1998 09:02:27 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA06108; Fri, 4 Dec 1998 09:02:11 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA02156; Fri, 4 Dec 1998 09:02:11 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 4 Dec 1998 09:02:11 -0800 (PST) Message-Id: <199812041702.JAA02156@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: kmem, tty, bind security enhancements commit. Newsgroups: polstra.freebsd.current In-Reply-To: <199812012143.NAA10640@apollo.backplane.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812012143.NAA10640@apollo.backplane.com>, Matthew Dillon wrote: > > I accidently created a /usr/src/etc/namedb/s directory and cvs add'd > it, then realized that it shouldn't be in the source tree (mtree handles > creating it in production). I've cvs deleted it but it will not commit > the deletion to the server. i.e. 'cvs commit' thinks there is nothing > to do. Very odd. Yes, but it sort of makes sense. CVS tries to save all history, so it never really deletes anything -- not even empty directories that have never been used. I got rid of it for you. BTW, for requests like this it's best to write directly to the repository managers (peter@freebsd.org and jdp@freebsd.org). That way we're sure to notice. > I'd appreciate it if a cvs god looked at that! Wow, I've never been a god before. Wait 'til I tell Mom! :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 09:21:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26473 for freebsd-current-outgoing; Fri, 4 Dec 1998 09:21:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lists.arkenstone.org (lists.arkenstone.org [209.213.198.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26460 for ; Fri, 4 Dec 1998 09:21:50 -0800 (PST) (envelope-from root@arkenstone.org) From: root@arkenstone.org Received: from mail.arkenstone.org (mail.arkenstone.org [209.213.203.157]) by lists.arkenstone.org (8.8.5/8.8.5) with SMTP id JAA07357; Fri, 4 Dec 1998 09:21:14 -0800 Received: from POP3 Client by mail.arkenstone.org (ccMail Link to SMTP R8.00.00) id AA912792993; Fri, 04 Dec 98 09:36:32 -0800 Message-Id: <9812049127.AA912792993@mail.arkenstone.org> X-Mailer: ccMail Link to SMTP R8.00.00 Date: Fri, 04 Dec 98 01:21:35 -0800 To: Cc: Subject: Re: /boot/loader what to set rootdev to? MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Content-Transfer-Encoding: 7bit >> Okay. If you feel it necessary to drop this thread, go ahead. If you >> can explain the cold boot rule's reasoning to me, even better. If you >> (or Mike or anybody) can tell me whether nextboot still works, >> terrific. > We're probably fundamentally at cross-purposes here. Okay. It appears that the difference of what we're discussing (which I only just realized, sorry) is the difference between what works, and what we want to support. > Regarding nextboot, I can't get your question into any kind of > context, sorry. Is this just an entirely separate issue, or > does "still works" relate to using FBSDBOOT versus not using > FBSDBOOT in some way? This is a related but separate issue. Two or three messages ago, you suggested that somebody write a Windows program that will either take command line parameters or pop up a cute dialog box to let a user select a BSD slice and kernel. Then this program would talk to the boot blocks and tell it to boot into that kernel with those parameters. After that, the program would reboot the system. It appears that the majority of people who want to use FBSDBOOT want to do so in order to have an icon on their Windows desktop or their start menu that would load FreeBSD. The others either don't have a BSD partition or need a DOS driver to configure their hardware. If we are bound and determined to drop support for the second category, then perhaps we can keep support for the first. Now, one way to write this program immediately suggests itself to me. Rewrite nextboot for Windows and put a GUI on it. Hence, my question. I don't know any other way to talk to the boot manager, although I'm open to suggestions. I myself don't use Windows. I don't use FBSDBOOT. The box that has both Windows and BSD on it has a partition manager. I won't be using this silly icon. This thread started out as me trying to give a user a simple solution to their problem, and now I'm to the point where by golly, I'm gonna get *something* useful accomplished out of it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 09:25:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27022 for freebsd-current-outgoing; Fri, 4 Dec 1998 09:25:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26997 for ; Fri, 4 Dec 1998 09:25:15 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA14336; Fri, 4 Dec 1998 10:25:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA20603; Fri, 4 Dec 1998 10:24:59 -0700 Date: Fri, 4 Dec 1998 10:24:59 -0700 Message-Id: <199812041724.KAA20603@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: Bug in i386/apm/apm.c? In-Reply-To: <199812040710.XAA25670@bubba.whistle.com> References: <199812040710.XAA25670@bubba.whistle.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This looks like a bug... It is. Feel free to commit the fix to it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 10:46:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07687 for freebsd-current-outgoing; Fri, 4 Dec 1998 10:46:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07669 for ; Fri, 4 Dec 1998 10:46:02 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA11178; Fri, 4 Dec 1998 19:45:40 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA14671 (5.67b/IDA-1.5); Fri, 4 Dec 1998 19:44:40 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00997; Fri, 4 Dec 1998 19:29:01 +0100 (CET) From: Wilko Bulte Message-Id: <199812041829.TAA00997@yedi.iaf.nl> Subject: Re: New drivers and install floppy space In-Reply-To: <199812041612.LAA12442@skynet.ctr.columbia.edu> from Bill Paul at "Dec 4, 98 11:12:46 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Fri, 4 Dec 1998 19:29:01 +0100 (CET) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bill Paul wrote... > I'm on the verge of committing four new fast ethernet device drivers > to -current, however I'm a bit concerned about running out of space on > the installation floppy (these drivers will be added to the GENERIC > kernel). Figuring between 15 and 20K of object code per driver, is there > enough room for me to do this, or am I asking for trouble? I see things like: # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing and # This provides support for System V shared memory. # options SYSVSHM in GENERIC. I'd also say you could do without things like procfs. In other words, maybe an INSTALL kernel is in order? (Ducks for cover) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 11:53:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12883 for freebsd-current-outgoing; Fri, 4 Dec 1998 11:53:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12878 for ; Fri, 4 Dec 1998 11:53:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA16925; Fri, 4 Dec 1998 11:52:56 -0800 (PST) (envelope-from dillon) Date: Fri, 4 Dec 1998 11:52:56 -0800 (PST) From: Matthew Dillon Message-Id: <199812041952.LAA16925@apollo.backplane.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@FreeBSD.ORG Subject: Re: weird rsh hang References: <199812040954.BAA23296@silvia.hip.berkeley.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :I'm trying some parallel gzip's by trying a : : rsh mach1 cat file | gzip | rsh mach1 cat \> file.newname : :For some reason, this is turning up a large number of hung connections. :.. :=== : :I get about 10 of these for 1,500 connections over 3 machines. Any ideas? : :Satoshi Try rsh mach1 -n cat file for the first rsh. Is this with -current or with -stable? There was an old -stable that had a bug with the tcp window scaling that would get into a permanent blocking situation for window sizes of 65536 or greater, but the bug was fixed months ago as far as I know. I'll check. It also would not surprise me at all if a bug in rsh were found. Track down why the 'base' rsh command is stuck in select... is it waiting to read from the socket or to write to the pipe? It could be waiting to read from stdin since you didn't use the -n option. 0 5391 5369 188 2 0 780 488 select I ?? 0:00.02 rsh m16 cat /usr/local/packa... -Matt :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 12:03:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13972 for freebsd-current-outgoing; Fri, 4 Dec 1998 12:03:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13961 for ; Fri, 4 Dec 1998 12:03:27 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Fri, 4 Dec 1998 20:02:12 -0000 Message-ID: From: Paul Richards To: "'Randall Hopper'" , Thierry Herbelot , Tim Gibson Cc: freebsd-current@FreeBSD.ORG Subject: RE: 3.0 install Date: Fri, 4 Dec 1998 20:02:11 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Randall Hopper [mailto:aa8vb@pagesz.net] > Sent: Friday, November 27, 1998 10:48 PM > To: Thierry Herbelot; Tim Gibson > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: 3.0 install > > > Thierry Herbelot: > |Tim Gibson wrote: > |> Don't know if I've got a problem here or if it's supposed to be > |> like this. I've got a few old HP Vectras with an AMD ether on > |> board. The generic install kernel sees the ether, but doesn't > |> seem to poll it for the MAC and then doesn't finish setting up > |> the lnc0 device for use with install. 2.2.7 did do this with > |> no probs. > ... > |The lance/Ethernet seems to be broken these times (see in > the archives > |if the messages on the subject already went in) > > What about it is broken? I've got a Lance board (Allied > Telesyn AT-1500BT) > I've been using for a long while. Great performance and > works fine with > FreeBSD. Currently running 3.0-RELEASE. There were changes made to the driver for 2.2.8 and 3.0 that supposedly made it detect more NIC's but in fact broke a lot of cases that had previously worked. I'm working on sorting this out for 3.1 Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 12:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16182 for freebsd-current-outgoing; Fri, 4 Dec 1998 12:23:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16160 for ; Fri, 4 Dec 1998 12:23:04 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id WAA14342; Fri, 4 Dec 1998 22:20:04 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 4 Dec 1998 22:20:03 +0200 (EET) From: Adrian Penisoara To: Brian Somers cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: user-ppp broken since a few days ago? In-Reply-To: <199812022223.WAA17289@dev.lan.awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, 2 Dec 1998, Brian Somers wrote: > The above log shows that the remote end hangs up (the line above > ``Carrier lost'' says ``\r\nNO CARRIER\r\n''). This looks like a > result of us rejecting whatever 0x0801 is - probably NetBUI or > something like that :-/ ISTR that leaving "Log on to network" enabled in Windows' Dial-Up Networking / Server Types makes Windows refuse the PPP link (don't remember the error message but it was quite clear it won't work unless deactivated)... > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... Just my $0.02 Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 12:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16779 for freebsd-current-outgoing; Fri, 4 Dec 1998 12:26:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-24-dbn.dial-up.net [196.34.155.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16732 for ; Fri, 4 Dec 1998 12:26:26 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA06187; Fri, 4 Dec 1998 22:24:50 +0200 (SAT) From: Robert Nordier Message-Id: <199812042024.WAA06187@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <863e6vvo4q.fsf@detlev.UUCP> from Joel Ray Holveck at "Dec 4, 98 11:00:05 am" To: joelh@gnu.org (Joel Ray Holveck) Date: Fri, 4 Dec 1998 22:24:47 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > > Regarding nextboot, I can't get your question into any kind of > > context, sorry. Is this just an entirely separate issue, or > > does "still works" relate to using FBSDBOOT versus not using > > FBSDBOOT in some way? > > This is a related but separate issue. Two or three messages ago, you > suggested that somebody write a Windows program that will either take > command line parameters or pop up a cute dialog box to let a user > select a BSD slice and kernel. Then this program would talk to the > boot blocks and tell it to boot into that kernel with those > parameters. After that, the program would reboot the system. > > It appears that the majority of people who want to use FBSDBOOT want > to do so in order to have an icon on their Windows desktop or their > start menu that would load FreeBSD. The others either don't have a > BSD partition or need a DOS driver to configure their hardware. If we > are bound and determined to drop support for the second category, then > perhaps we can keep support for the first. > > Now, one way to write this program immediately suggests itself to me. > Rewrite nextboot for Windows and put a GUI on it. Hence, my > question. I don't know any other way to talk to the boot manager, > although I'm open to suggestions. This approach hadn't occurred to me, though it does seem a reasonable idea, and quite possibly the best way to go about this. I like the concept of a method shared between Windows and BSD, not least because space is usually at a premium in the boot blocks. > I myself don't use Windows. I don't use FBSDBOOT. The box that has > both Windows and BSD on it has a partition manager. I won't be using > this silly icon. This thread started out as me trying to give a user > a simple solution to their problem, and now I'm to the point where by > golly, I'm gonna get *something* useful accomplished out of it. Yes, I've no special interest in this myself, except that it would be good to have it happen, since there evidently are various people who could make use of it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 12:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19960 for freebsd-current-outgoing; Fri, 4 Dec 1998 12:59:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19944 for ; Fri, 4 Dec 1998 12:59:37 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.1/8.9.1) id VAA03817; Fri, 4 Dec 1998 21:59:14 +0100 (CET) Date: Fri, 4 Dec 1998 21:59:14 +0100 (CET) Message-Id: <199812042059.VAA03817@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size From: Ronald Kuehn X-Newsreader: NN version 6.5.0 CURRENT #124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current you write: > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > > The /var filesystem does not have soft updates enabled. > > I got a dump, but not from a debugging kernel. > > > > [ current as of Dec 2 ] > Just wondering, why are people running softupdates and non-softupdates on > the same box, or just plain not using softupdates? > I thought that it is as reliable as regular mounts and faster? Or are > there issues that I haven't noticed? > Or are you guys testing for the FreeBSD project? > -Alfred On small filesystems, softupdates has some problems here. If I do a "make installworld", it breaks with "file system full" errors. It doesn't recover the free space on the filesystem (from the removed files) quickly enough. So the filesystem seems full. Bye, Ronald -- * The Theorem Theorem: If If, Then Then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 13:02:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20385 for freebsd-current-outgoing; Fri, 4 Dec 1998 13:02:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20377 for ; Fri, 4 Dec 1998 13:02:18 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.1/8.9.1) id WAA03859; Fri, 4 Dec 1998 22:02:02 +0100 (CET) Date: Fri, 4 Dec 1998 22:02:02 +0100 (CET) Message-Id: <199812042102.WAA03859@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size From: Ronald Kuehn X-Newsreader: NN version 6.5.0 CURRENT #124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current Archie Cobbs wrote: > Ronald Kuehn writes: > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > > The /var filesystem does not have soft updates enabled. > > I got a dump, but not from a debugging kernel. > If your kernel sources haven't changed, you can recompile the > kernel after doing a "config -g" and get a kernel with symbols. > Then you can run gdb -k on it. (You probably already know this :) > -Archie Yes, the problem is that I don't have the matching sources anymore. I'm trying to regenerate an almost matching debugging kernel. Ronald -- * The Theorem Theorem: If If, Then Then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 13:08:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20882 for freebsd-current-outgoing; Fri, 4 Dec 1998 13:08:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20872 for ; Fri, 4 Dec 1998 13:08:10 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.1/8.9.1) id WAA03898; Fri, 4 Dec 1998 22:07:52 +0100 (CET) Date: Fri, 4 Dec 1998 22:07:52 +0100 (CET) Message-Id: <199812042107.WAA03898@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size From: Ronald Kuehn X-Newsreader: NN version 6.5.0 CURRENT #124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current Luoqi Chen wrote: > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > bno is a fs block number and for /var it almost surely can't be 13. This > still points to a missing VOP_BMAP() somewhere. > While I'm writing this message, I took another look at Kirk's patch. It seems > to me that he forgot to call VOP_BMAP() for the last buf in the reallocation > list. Try this patch, and see if you still get the panic, [patch deleted] Well, I'll try that on my scratch box. > A dump from a non-debugging kernel is as good as a debugging one. Could you > post a stack backtrace? Here it is: (I'll try to reproduce that with a debugging kernel) IdlePTD 2355200 initial pcb at 20b4a0 panicstr: ffs_blkfree: bad size panic messages: --- panic: ffs_blkfree: bad size syncing disks... 25 23 15 6 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 giving up dumping to dev 20401, offset 147456 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xf0131abf in boot () (kgdb) where #0 0xf0131abf in boot () #1 0xf0131de3 in panic () #2 0xf01894c6 in ffs_blkfree () #3 0xf0187b8c in ffs_reallocblks () #4 0xf0151c2b in cluster_write () #5 0xf01947b7 in ffs_write () #6 0xf015b62b in vn_write () #7 0xf013a902 in write () #8 0xf01b77df in syscall () #9 0xf01ad97c in Xint0x80_syscall () #10 0x280baa07 in ?? () #11 0x280c9c12 in ?? () #12 0x280c9a5e in ?? () #13 0x280c9e89 in ?? () #14 0x280c4d18 in ?? () #15 0x280c4c0f in ?? () #16 0x8084b13 in ?? () #17 0x8085672 in ?? () #18 0x8085994 in ?? () #19 0x805cec0 in ?? () #20 0x805bee3 in ?? () #21 0x8059b14 in ?? () #22 0x80597fc in ?? () #23 0x28157208 in ?? () #24 0x2815701a in ?? () #25 0xefbfd3b0 in ?? () #26 0x2808e500 in ?? () Cannot access memory at address 0x4c060. Ronald -- * The Theorem Theorem: If If, Then Then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 13:34:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23347 for freebsd-current-outgoing; Fri, 4 Dec 1998 13:34:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23338 for ; Fri, 4 Dec 1998 13:34:31 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA19545; Fri, 4 Dec 1998 14:34:01 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd019465; Fri Dec 4 14:33:59 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA06102; Fri, 4 Dec 1998 14:33:45 -0700 (MST) From: Terry Lambert Message-Id: <199812042133.OAA06102@usr01.primenet.com> Subject: Re: Thread fd locking and fork() To: info@highwind.com (HighWind Software Information) Date: Fri, 4 Dec 1998 21:33:45 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199812031522.KAA28193@highwind.com> from "HighWind Software Information" at Dec 3, 98 10:22:31 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is the problem: > > 1. You have a program that starts a few threads, one of these threads > blocks in "accept()" waiting for a new connection on a file descriptor. > > 2. In another thread, you want to start a child program. After the > fork(), but before exec(), you close() all the file descriptors you > don't want the child to touch. > > 3. The child hangs in close() forever. > > Why? > > At fork(), you get a copy of all the fd's. Problem is, many of them have > their file descriptors locked. > > --- > > Is there any solution to this? Perhaps the fork() code should unlock > all the descriptors. > > Does this makes sense? > > Opening a PR now. % man fcntl FCNTL(2) FreeBSD System Calls Manual FCNTL(2) NAME fcntl - file control [ ... ] F_SETFD Set the close-on-exec flag associated with fd to the low order bit of arg (0 or 1 as above). Then don't explicitly call close after the exec, since the fork() wrapper in libc_r will Do The Right Thing(tm). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 14:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27397 for freebsd-current-outgoing; Fri, 4 Dec 1998 14:08:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27392 for ; Fri, 4 Dec 1998 14:08:32 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA12304; Fri, 4 Dec 1998 17:07:58 -0500 (EST) Date: Fri, 4 Dec 1998 17:07:58 -0500 (EST) Message-Id: <199812042207.RAA12304@highwind.com> From: HighWind Software Information To: tlambert@primenet.com CC: current@FreeBSD.ORG In-reply-to: <199812042133.OAA06102@usr01.primenet.com> (message from Terry Lambert on Fri, 4 Dec 1998 21:33:45 +0000 (GMT)) Subject: Re: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Then don't explicitly call close after the exec, since the fork() > wrapper in libc_r will Do The Right Thing(tm). What is the problem with calling close() after the exec()? That is a 100% valid thing to do. Saying, "do this instead" is nice, but doesn't address the bug in libc_r. Also, if you call fcntl() after the fork(), you will hang. The only thing you can do is fcntl() all your descriptors before the fork(). That is a bit crazy because you have to juggle everytime you want to do a fork()/exec(). Calling fcntl() in the parent also introduces other race conditions as other parts of the system might be calling fork(). My patch seems to fix it. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03659 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:02:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03650; Fri, 4 Dec 1998 15:02:17 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id PAA35399; Fri, 4 Dec 1998 15:10:06 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812042310.PAA35399@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <199812041546.KAA24938@lor.watermarkgroup.com> from Luoqi Chen at "Dec 4, 1998 10:46:50 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Fri, 4 Dec 1998 15:10:06 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG, kuehn@rz.tu-clausthal.de, dg@FreeBSD.ORG, kirk@mckusick.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc'd to dg and kirk] According to Luoqi Chen: > > I had such a panic today too during cvsup activity. Two filesystems > > don't have softupdates. All others do. The activity was on one > > of those softupdates filesystems. > > > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > bno is a fs block number and for /var it almost surely can't be 13. This > still points to a missing VOP_BMAP() somewhere. > > While I'm writing this message, I took another look at Kirk's patch. It seems > to me that he forgot to call VOP_BMAP() for the last buf in the reallocation > list. Try this patch, and see if you still get the panic, > [patch deleted] Luoqi, Your patch has survived my torture test. I did: (1) make -j 32 buildworld (CFLAGS = -O -pipe) (2) cd sys/compile/GENERIC (COPTFLAGS = -O) foreach i (*.h) make -j 16 sleep 10 make clean sleep 10 end (3) cd ports/devel/ddd ; make This would crash my machine without your patch within an hour. I hit a peak load average of 40 with a load average of around 14 throughout the cycle. Amazingly, with 256 MB on a dual PPro machine, I never touched the swap space. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:12:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04469 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:12:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04448 for ; Fri, 4 Dec 1998 15:11:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA01570; Fri, 4 Dec 1998 15:13:20 -0800 (PST) To: Joel Ray Holveck cc: Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "04 Dec 1998 11:00:05 CST." <863e6vvo4q.fsf@detlev.UUCP> Date: Fri, 04 Dec 1998 15:13:19 -0800 Message-ID: <1565.912813199@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I myself don't use Windows. I don't use FBSDBOOT. The box that has > both Windows and BSD on it has a partition manager. I won't be using > this silly icon. This thread started out as me trying to give a user > a simple solution to their problem, and now I'm to the point where by > golly, I'm gonna get *something* useful accomplished out of it. Maybe you could write us a Windows InstallShield based demo installer then? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05729 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:23:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05719 for ; Fri, 4 Dec 1998 15:23:37 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA06665; Fri, 4 Dec 1998 15:22:56 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 4 Dec 1998 15:22:55 -0800 (PST) From: Doug White To: andrea cc: freebsd-current@FreeBSD.ORG Subject: Re: R: ip-masquerading.natd,ip-aliasing .... In-Reply-To: <007a01be1f6c$0abf70c0$4d18b9c2@oma.linet.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Dec 1998, andrea wrote: > >I don't know how fancy your router is, if it can be taught to natd certain > >packets or not (I think ipfw can do it, not sure). > > > >> I'have tried assigning 2 ip address at the same interface ,and using > >> this machine as a gateway on the same phisical net. > > > >You have to use an alias (with the netmask of that network, not > >0xffffffff) on the interface to get the second IP programmed in. > > First of all thank you for replying!:) > > Now the configuration you described is pretty the same of mine. > And that's the problem it doesn't works at all.:( That's no good. > The rule in the firewall that 'divert' the socket to natd seem to > work,because i can see the > counters of packets increasing.. > But natd doesn't get anything ,or so seems( i set-up natd in verbose mode > but nothing happens...) Check your natd configuration (see the manpage). Hopefully this isn't pathological -- this is the second case of ipfw+natd failing from a stock install. I need to test this myself. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05824 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:24:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05819 for ; Fri, 4 Dec 1998 15:24:51 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA06708; Fri, 4 Dec 1998 15:24:29 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 4 Dec 1998 15:24:28 -0800 (PST) From: Doug White To: Dom Mitchell cc: current@FreeBSD.ORG Subject: Re: sysinstall question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Dec 1998, Dom Mitchell wrote: > Question for all the sysinstall gurus: I've just downloaded the > 3.0-RELEASE boot.flp and fixit.flp to try and fix my busted 3.0 > bootblocks install (I shoulda read more first...). When I try to insert > the fixit floppy, when prompted for, I'm getting: > > mountmsdosfs(): bad bpb The fixit floppy is a UNIX format disk image. mount_msdos shouldn't be touching it. > Does anybody have an idea why this is? Why is it even trying to mount > the fixit floppy as an msdos filesystem? I have tried two different > floppy disks, just in case, BTW. What version of FreeBSD? If current (and it should be in the current mailing list), what date did you last sup? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05919 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:26:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05911 for ; Fri, 4 Dec 1998 15:26:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00556; Fri, 4 Dec 1998 15:23:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812042323.PAA00556@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 11:12:46 EST." <199812041612.LAA12442@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 15:23:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm on the verge of committing four new fast ethernet device drivers > to -current, however I'm a bit concerned about running out of space on > the installation floppy (these drivers will be added to the GENERIC > kernel). Figuring between 15 and 20K of object code per driver, is there > enough room for me to do this, or am I asking for trouble? I'd say Just Do It, and we'll deal with the space problems when they arise. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06054 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:28:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06046 for ; Fri, 4 Dec 1998 15:28:16 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id SAA08845; Fri, 4 Dec 1998 18:27:52 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Doug White cc: Dom Mitchell , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: sysinstall question In-reply-to: Your message of "Fri, 04 Dec 1998 15:24:28 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 18:27:52 -0500 Message-ID: <8841.912814072@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote in message ID : > > mountmsdosfs(): bad bpb > > The fixit floppy is a UNIX format disk image. mount_msdos shouldn't be > touching it. This is a known issue. Jordan broke the fixit floppy for 3.0. My guess is he's trying to use the same internal fn to mount the floppy for doing a DOS floppy install as he is mounting the fixit floppy. End result: sysinstall gets royally confused. He's aware of the problem and promises to fix it. Sometime. :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06377 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:31:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06366 for ; Fri, 4 Dec 1998 15:30:55 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial8-249.netcologne.de [195.14.235.249]) by mail2.netcologne.de (8.9.1/8.9.1) with ESMTP id AAA12966 for ; Sat, 5 Dec 1998 00:30:21 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id AAA02402; Sat, 5 Dec 1998 00:31:23 +0100 (CET) (envelope-from marc) Date: Sat, 5 Dec 1998 00:31:23 +0100 (CET) Message-Id: <199812042331.AAA02402@oranje.my.domain> From: Marc van Woerkom To: freebsd-current@FreeBSD.ORG Subject: bzip2 - worthy successor to gzip? Reply-to: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today, while fetching egcs, I noticed that those folks use bzip2 for compressing their snapshots: -rw-r--r-- 1 220 1002 8917442 Dec 2 19:33 egcs-1.1.1.tar.bz2 -rw-r--r-- 1 220 1002 11604853 Dec 2 19:27 egcs-1.1.1.tar.gz -rw-r--r-- 1 220 1002 6222128 Dec 2 19:34 egcs-core-1.1.1.tar.bz2 -rw-r--r-- 1 220 1002 8177883 Dec 2 19:16 egcs-core-1.1.1.tar.gz These files are only about 70% of their gzip counterparts - quite impressive. Julian Seward (jseward@acm.org), the author of this program claims extensive tests on his web page http://www.muraroa.demon.co.uk Comments? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:37:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06997 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:37:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06992 for ; Fri, 4 Dec 1998 15:37:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA01753; Fri, 4 Dec 1998 15:38:54 -0800 (PST) To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 11:12:46 EST." <199812041612.LAA12442@skynet.ctr.columbia.edu> Date: Fri, 04 Dec 1998 15:38:53 -0800 Message-ID: <1750.912814733@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm on the verge of committing four new fast ethernet device drivers > to -current, however I'm a bit concerned about running out of space on > the installation floppy (these drivers will be added to the GENERIC Even if we do hit a wall, we can always make it a kern.flp only feature. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07074 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:38:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07064 for ; Fri, 4 Dec 1998 15:38:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA01765; Fri, 4 Dec 1998 15:39:22 -0800 (PST) To: Wilko Bulte cc: wpaul@skynet.ctr.columbia.edu (Bill Paul), current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 19:29:01 +0100." <199812041829.TAA00997@yedi.iaf.nl> Date: Fri, 04 Dec 1998 15:39:22 -0800 Message-ID: <1762.912814762@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see things like: See /usr/src/release/Makefile - what is in GENERIC is not necessarily what's on the boot.flp image. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07399 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:41:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07392 for ; Fri, 4 Dec 1998 15:41:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA01805; Fri, 4 Dec 1998 15:43:11 -0800 (PST) To: Dom Mitchell cc: current@FreeBSD.ORG Subject: Re: sysinstall question In-reply-to: Your message of "Fri, 04 Dec 1998 16:37:18 GMT." Date: Fri, 04 Dec 1998 15:43:11 -0800 Message-ID: <1801.912814991@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Question for all the sysinstall gurus: I've just downloaded the > 3.0-RELEASE boot.flp and fixit.flp to try and fix my busted 3.0 > bootblocks install (I shoulda read more first...). When I try to insert > the fixit floppy, when prompted for, I'm getting: The "Fixit" feature is broken in 3.0. :( I'm working on fixing it now, 2.2.8 just sort of sidetracked me for a bit. > mountmsdosfs(): bad bpb > > Does anybody have an idea why this is? Why is it even trying to mount > the fixit floppy as an msdos filesystem? I have tried two different > floppy disks, just in case, BTW. All floppies are mounted both ways until something succeeds, just in case you might have put the files on DOS. Probably not apropos for the fixit case but the same floppy reading code is standard across all of sysinstall and in other cases it does make sense. In any case, that's not the error that's really messing things up. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:47:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07956 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:47:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07949 for ; Fri, 4 Dec 1998 15:47:58 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA01794; Fri, 4 Dec 1998 15:46:25 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma001792; Fri, 4 Dec 98 15:46:17 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA08793; Fri, 4 Dec 1998 15:46:17 -0800 (PST) From: Archie Cobbs Message-Id: <199812042346.PAA08793@bubba.whistle.com> Subject: Re: Bug in i386/apm/apm.c? In-Reply-To: <70792.912761022@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 4, 98 00:43:42 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Fri, 4 Dec 1998 15:46:16 -0800 (PST) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard writes: > > PR: 8280 > > Seems odd that nobody's committed it - it's been there since October > and each of the 3 fixes appears to be in the semi-obvious category > (the last two being of a more cosmetic nature than the first). I applied the patches and close the PR. By the way, the second one was not just cosmetic because "==" has higher precedence than "&" (definitely non-intutive). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08421 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:51:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08416 for ; Fri, 4 Dec 1998 15:51:56 -0800 (PST) (envelope-from xaa@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (VMailer) with ESMTP id 7A5301E0; Sat, 5 Dec 1998 00:51:37 +0100 (MET) Received: by ariel.xaa.iae.nl (VMailer, from userid 1002) id 3B7DE3EAD; Sat, 5 Dec 1998 00:51:37 +0100 (CET) Date: Sat, 5 Dec 1998 00:51:37 +0100 From: Mark Huizer To: current@FreeBSD.ORG Subject: Dummynet for 3.0? Message-ID: <19981205005136.D817@ariel.xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I understand the constraints you were working within. I believe the > correct approach to the problem would have been to leave 2.2 alone and > bring DUMMYNET/BRIDGE into -current. The benefits being: Ordinarily good and proper sentiments, but this issue came up after code freeze and this option was not open to Luigi. Is the option to add dummynet to 3.0 open now? Mark -- Mark Huizer - xaa@xaa.iae.nl - markh@win.tue.nl Always borrow money from a pessimist; he doesn't expect to be paid back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 15:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08664 for freebsd-current-outgoing; Fri, 4 Dec 1998 15:56:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08659 for ; Fri, 4 Dec 1998 15:56:24 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA01897; Fri, 4 Dec 1998 15:55:25 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma001893; Fri, 4 Dec 98 15:55:04 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA08863; Fri, 4 Dec 1998 15:55:04 -0800 (PST) From: Archie Cobbs Message-Id: <199812042355.PAA08863@bubba.whistle.com> Subject: Re: FreeBSD fsck updated In-Reply-To: <199812041213.XAA26965@godzilla.zeta.org.au> from Bruce Evans at "Dec 4, 98 11:13:22 pm" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 4 Dec 1998 15:55:04 -0800 (PST) Cc: current@FreeBSD.ORG, julian@whistle.com, Don.Lewis@tsc.tdk.com, mckusick@McKusick.COM X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >+ if (fs->fs_fmod != 0) { > >+ pwarn("MODIFIED FLAG SET IN SUPERBLOCK"); > >+ if (preen) > >+ printf(" (FIXED)\n"); > >+ if (preen || reply("FIX") == 1) { > >+ fs->fs_fmod = 0; > >+ sbdirty(); > >+ } > >+ } > > ... > > Clearing fs_fmod here seems to be bogus. It is set (to 0 or 1) > unconditionally at mount time. Similarly for fs_ronly. I don't see > how it can be right to clear these flags here _only_ when a certain > type of inconsistency (that has nothing to do with these flags) > is fixed. We (Julian & me) are the ones who added this bit of code to clear the modified flag after seeing a panic caused by mounting a filesystem read-only that had this bit set (even though it was "clean", as the previous fsck didn't clear this bit). I forget exactly how it can happen, but it can (and did). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 16:03:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10261 for freebsd-current-outgoing; Fri, 4 Dec 1998 16:03:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from guerilla.foo.bar (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10198 for ; Fri, 4 Dec 1998 16:03:25 -0800 (PST) (envelope-from sas@schell.de) Received: from localhost (sas@localhost [127.0.0.1]) by guerilla.foo.bar (8.8.8/8.8.8) with ESMTP id BAA20668; Sat, 5 Dec 1998 01:02:23 +0100 Date: Sat, 5 Dec 1998 01:02:23 +0100 (MET) From: Sascha Schumann X-Sender: sas@guerilla.foo.bar To: van.woerkom@netcologne.de cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? In-Reply-To: <199812042331.AAA02402@oranje.my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Dec 1998, Marc van Woerkom wrote: > Today, while fetching egcs, I noticed that those folks use bzip2 for > compressing their snapshots: > > -rw-r--r-- 1 220 1002 8917442 Dec 2 19:33 egcs-1.1.1.tar.bz2 > -rw-r--r-- 1 220 1002 11604853 Dec 2 19:27 egcs-1.1.1.tar.gz > -rw-r--r-- 1 220 1002 6222128 Dec 2 19:34 egcs-core-1.1.1.tar.bz2 > -rw-r--r-- 1 220 1002 8177883 Dec 2 19:16 egcs-core-1.1.1.tar.gz > > These files are only about 70% of their gzip counterparts - quite impressive. > > Julian Seward (jseward@acm.org), the author of this program claims extensive > tests on his web page > > http://www.muraroa.demon.co.uk > > Comments? If you have an archive and your focus is on saving storage, go with it. Its compression algorithm is much slower compared to gzip, but also more effective. You see it yourself on the egcs site. It would be interesting to know how much traffic a busy site like ftp.cdrom.com or sunsite could save, if they would completely stick to bzip2. Regards, Sascha Schumann | Consultant | finger sas@schell.de | for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 16:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15655 for freebsd-current-outgoing; Fri, 4 Dec 1998 16:57:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15650 for ; Fri, 4 Dec 1998 16:57:26 -0800 (PST) (envelope-from yds@ingress.net) Received: (qmail 11702 invoked from network); 5 Dec 1998 00:57:10 -0000 Received: from ichiban.ingress.com (HELO ingress.net) (205.230.64.31) by paris.dppl.com with SMTP; 5 Dec 1998 00:57:10 -0000 Message-ID: <366884E6.4C8D0FBF@ingress.net> Date: Fri, 04 Dec 1998 19:57:10 -0500 From: Yarema X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en,uk,ru,ja MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: /usr/libexec/ld-elf.so.1 not found Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> gnu/usr.bin/perl/perl install -c -s -o root -g wheel -m 555 perl /usr/bin /usr/bin/perl5 -> /usr/bin/perl /usr/bin/perl5.00502 -> /usr/bin/perl cd /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/ext/B ; make -B install INSTALLPRIVLIB=/usr/libdata/perl/5.00502 INSTALLARCHLIB=/usr/libdata/perl/5.00502/mach ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap *** Error code 134 I'm getting the above error whenever doing a aout-to-elf-install to upgrade from 2.2.7 to 3.0. For some reason /usr/libexec/ld-elf.so.1 never gets installed with the aout-to-elf-install target. I've tried doing aout-to-elf-install on a system that's already elf and a fresh interpreter didn't get installed. Shouldn't it? cp /usr/obj/elf/usr/src/libexec/rtld-elf/ld-elf.so.1 /usr/libexec/ and rerunning make aout-to-elf-install fixes things.. -- Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:16:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16873 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:16:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16868 for ; Fri, 4 Dec 1998 17:16:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00709; Fri, 4 Dec 1998 15:45:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812042345.PAA00709@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck cc: Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "04 Dec 1998 11:00:05 CST." <863e6vvo4q.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 15:45:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Regarding nextboot, I can't get your question into any kind of > > context, sorry. Is this just an entirely separate issue, or > > does "still works" relate to using FBSDBOOT versus not using > > FBSDBOOT in some way? > > This is a related but separate issue. ... > Now, one way to write this program immediately suggests itself to me. > Rewrite nextboot for Windows and put a GUI on it. Hence, my > question. I don't know any other way to talk to the boot manager, > although I'm open to suggestions. The problem is that it's not a related issue; nextboot doesn't have anything to do with what you're discussing - it's an outdated way to talk to the old bootstrap code in order to pass arguments to the 'boot:' prompt. It doesn't have any effect on the active partition. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17021 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:17:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17013 for ; Fri, 4 Dec 1998 17:17:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00857; Fri, 4 Dec 1998 16:07:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812050007.QAA00857@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Thu, 03 Dec 1998 21:46:14 EST." <199812040246.VAA00209@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 16:07:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > I'm not fond of this sort of 'active match' approach at all; > > particularly for pccard devices it makes it impossible to apply an > > existing driver to a new peripheral without patching and rebuilding the > > driver, which is extremely lame. > > The driver needs to know what sort of bus it's on -- there's simply no > escaping that. I don't see anywhere I've even considered suggesting this. The point I'm trying to make is that the match process needs to be run by the *bus* code - it has access to the list of drivers attached to it as well as to the results of it's PnP probes, and is the only module in a position to match the two together. The correct way to do this is to have a set of bindings between PnP identifiers and driver names. Embedding this information in the driver is IMO wrong, simply because updating a driver is difficult while updating a text file is easy. > I would be willing to have an > ``erratum database'' which indicates additional devices which should > be handled by an existing driver, but it should be the driver which > decides (after all, it might just inspect the programming model and > not look at the vendor information at all) whether it can handle the > card in question. The "programming model" is a secondary PnP identifier; see eg. the way that USB distinguishes between "device" and "class" identifiers - I made specific reference to this in my previous message. > (We need to have something like this anyway, since > the Linux Card Services manual indicates that some cards come with > completely bogus CIS.) As long as we can generate meaningful identifiers from the CIS, it doesn't really matter how bogus it is. Duplicating the bogosity-avoidance code in every device driver that has to deal with any PCCARD (in this case) would be poor technique. Better to implement it once. > In any case, the more like the official Card Services, the better, > since that's what will make it easy to port drivers. Which "official Card Services"? The "original" Card Services is terrible; it was designed for an environment with no autoconfiguration infrastructure. Foisting that on us will put us in the situation where PCCARDs and drivers are again "special cases". Needless to say, that would still be Bad. > > "serial/16550/modem". > > Ugh. I don't like the kernel being asked to parse more and more > arrays of text strings. Deal with data in their natural format. Given that text *is* the natural format for the source of the strings, this is silly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17448 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:27:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17443 for ; Fri, 4 Dec 1998 17:27:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01279 for ; Fri, 4 Dec 1998 17:25:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812050125.RAA01279@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Thu, 03 Dec 1998 00:44:10 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 17:25:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 2 Dec 1998, Mike Smith wrote: > > It would certainly be feasible to arrange for the firmware images to > > be loaded from separate files, should that be an acceptable > > alternative. I'm open to suggestions on how to make this economical > > and robust... > > Ooh! Ooh! Me Me! You have ideas, or you want the functionality? 8) > I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware > image for support of RAM based TMS380 cards. In addition, some each > particular card may have specific firmware it wants loaded. I'm looking > for some way to load a really basic config file to let the driver know > which image goes with which card. > > Doing this from userland isn't good as I can't do much with the card until > the firmware is loaded. Are these PnP devices, ie. can you differentiate between them before running the probe? Are they ever likely to be critical to the boot process? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:46:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19555 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:46:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19499 for ; Fri, 4 Dec 1998 17:45:57 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id CAA21517; Sat, 5 Dec 1998 02:45:36 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA04941 (5.67b/IDA-1.5); Sat, 5 Dec 1998 02:42:06 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id CAA04885; Sat, 5 Dec 1998 02:34:55 +0100 (CET) From: Wilko Bulte Message-Id: <199812050134.CAA04885@yedi.iaf.nl> Subject: Re: New drivers and install floppy space In-Reply-To: <1762.912814762@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 4, 98 03:39:22 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 5 Dec 1998 02:34:55 +0100 (CET) Cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jordan K. Hubbard wrote... > > I see things like: > > See /usr/src/release/Makefile - what is in GENERIC is not necessarily > what's on the boot.flp image. Guilty your honor ;) I did not know there was such a script involved that reshapes GENERIC into something smaller for the boot flop. Sure not the kind of concept to teach in a software engineering class 8) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19578 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:46:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19500 for ; Fri, 4 Dec 1998 17:45:57 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id CAA21521; Sat, 5 Dec 1998 02:45:37 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA04947 (5.67b/IDA-1.5); Sat, 5 Dec 1998 02:42:07 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id CAA04929; Sat, 5 Dec 1998 02:37:55 +0100 (CET) From: Wilko Bulte Message-Id: <199812050137.CAA04929@yedi.iaf.nl> Subject: Re: New drivers and install floppy space In-Reply-To: <1750.912814733@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 4, 98 03:38:53 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 5 Dec 1998 02:37:55 +0100 (CET) Cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jordan K. Hubbard wrote... > > I'm on the verge of committing four new fast ethernet device drivers > > to -current, however I'm a bit concerned about running out of space on > > the installation floppy (these drivers will be added to the GENERIC > > Even if we do hit a wall, we can always make it a kern.flp only feature. Eventually with the growing hardware support we would be back at a 2 floppy boot set it seems. Not a problem in my opinion, but is there a general strategy or is it simply 'waiting for the wall'? With sysinstall in re-work this might be the time to consider this 'floppy full' issue. Just my $0.02 Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 17:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20074 for freebsd-current-outgoing; Fri, 4 Dec 1998 17:51:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20066 for ; Fri, 4 Dec 1998 17:51:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01551; Fri, 4 Dec 1998 17:48:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812050148.RAA01551@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 02:37:55 +0100." <199812050137.CAA04929@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 17:48:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Jordan K. Hubbard wrote... > > > I'm on the verge of committing four new fast ethernet device drivers > > > to -current, however I'm a bit concerned about running out of space on > > > the installation floppy (these drivers will be added to the GENERIC > > > > Even if we do hit a wall, we can always make it a kern.flp only feature. > > Eventually with the growing hardware support we would be back at a > 2 floppy boot set it seems. Not a problem in my opinion, but is there a > general strategy or is it simply 'waiting for the wall'? At the moment, the current exploratory strategy is the split kern.flp/ mfsroot.gz arrangement. It's probably going to make more sense just to have them as two floppy images for distribution purposes. The alternative will be to have a single minimal kernel and mfsroot floppy, and another floppy with a pile of KLD modules on it. This won't be feasible until the PCI code moves to the new bus architecture (soon we hope). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 18:39:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24241 for freebsd-current-outgoing; Fri, 4 Dec 1998 18:39:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24234 for ; Fri, 4 Dec 1998 18:39:44 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id VAA13238 for ; Fri, 4 Dec 1998 21:39:28 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23853; Fri, 4 Dec 1998 21:39:28 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA02555; Fri, 4 Dec 1998 21:39:27 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812050239.VAA02555@bb01f39.unx.sas.com> Subject: Something fishy with telnetd (non-zero initialized static?) To: freebsd-current@FreeBSD.ORG Date: Fri, 4 Dec 1998 21:39:27 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following is from a 3.0-19981202-SNAP system. When I telnet into this newly installed system, the prompt I get is: --------------------------------------------------------- Connected to bb08f01.unx.sas.com. Escape character is '^]'. / (bb08f01.unx.sas.com) (ttyp1) login: --------------------------------------------------------- Note the '/' char in column one. Well, I say, "It shouldn't be like that, it should look like:" --------------------------------------------------------- Connected to bb08f01.unx.sas.com. Escape character is '^]'. FreeBSD/i386 (bb08f01.unx.sas.com) (ttyp1) login: --------------------------------------------------------- I have verified that this bug occurs on 2 different installations of the 3.0-19981202-SNAP. Too make a long story short, the following code in /usr/src/libexec/telnetd/utility.c looks to be the fishy culprit to me (added: 1.8 Sun Feb 2 7:33:50 1997 UTC by davidn): #ifdef __FreeBSD__ static struct utsname kerninfo; if (!*kerninfo.sysname) uname(&kerninfo); #endif Well, I ktraced /usr/libexec/telnetd (minor change to inetd.conf), and sysctl() is never being called, thus I assume that the 'if' statement is false (should be true). To prove myself correct, I rebuilt and installed a debug version of telnetd where I memset() kerninfo to zero and the 5 sysctl() calls in uname() show up correctly. I wonder if we are getting non-zero pages mapped in... ??? Below are the relevant portions of the ktrace output. Any comments, ideas, critiques, etc, are welcome at this point. Thanks! John --- Failing telnetd ------------------------------------- std.230400|230400-baud:\\ :np:sp#230400: # # " 3725 telnetd RET read 1024/0x400 3725 telnetd CALL close(0x4) 3725 telnetd RET close 0 3725 telnetd CALL madvise(0x805e000,0x1000,0x5) 3725 telnetd RET madvise 0 * * * sysctl() calls missing here * * 3725 telnetd CALL ioctl(0x3,TIOCGETA,0x8059d44) 3725 telnetd RET ioctl 0 3725 telnetd CALL ioctl(0x3,TIOCGETA,0x8059d44) 3725 telnetd RET ioctl 0 3725 telnetd CALL write(0,0x80592a0,0xc) 3725 telnetd GIO fd 0 wrote 12 bytes "\M^?\M-{\^A\M^?\M-z!\^B\M^?\M-p\M^?\M-~"" 3725 telnetd RET write 12/0xc 3725 telnetd CALL ioctl(0x3,TIOCSWINSZ,0xefbfd6bc) 3725 telnetd RET ioctl 0 3725 telnetd CALL ioctl(0x3,TIOCGETA,0x8059d44) 3725 telnetd RET ioctl 0 3725 telnetd CALL write(0,0x80592a0,0x38) 3725 telnetd GIO fd 0 wrote 56 bytes "\M^?\M-z"\^C\^A\0\0\^C\M-b\^C\^D\M^B\^O\^E\M^B\^T\a\M-b\^\\b\M^B\^D\ \M-B\^Z \M^B\^?\v\M^B\^U\f\M^B\^W\r\M^B\^R\^N\M^B\^V\^O\M^B\^Q\^P\M^B\^S\^Q\ \M^@\M^?\M^?\^R\M^@\M^?\M^?\M^?\M-p" 3725 telnetd RET write 56/0x38 3725 telnetd CALL madvise(0x805c000,0x1000,0x5) 3725 telnetd RET madvise 0 3725 telnetd CALL fork 3725 telnetd RET fork 3726/0xe8e 3725 telnetd CALL select(0x4,0xefbfd7f8,0xefbfd778,0xefbfd6f8,0) 3725 telnetd RET select 2 3725 telnetd CALL read(0,0x8058da0,0x400) 3725 telnetd GIO fd 0 read 6 bytes "\M^?\M-}\^A\M^?\M-|"" 3725 telnetd RET read 6 3725 telnetd CALL write(0,0x80592a0,0x25) 3725 telnetd GIO fd 0 wrote 37 bytes "\r / (bb08f01.unx.sas.com) (ttyp1)\r \r " --- Working telnetd ------------------------------------- std.230400|230400-baud:\\ :np:sp#230400: # # " 3721 telnetd RET read 1024/0x400 3721 telnetd CALL close(0x4) 3721 telnetd RET close 0 3721 telnetd CALL madvise(0x8057000,0x1000,0x5) 3721 telnetd RET madvise 0 3721 telnetd CALL __sysctl(0xefbfd5e8,0x2,0x80516b0,0xefbfd5f0,0,0) 3721 telnetd RET __sysctl 0 3721 telnetd CALL __sysctl(0xefbfd5e8,0x2,0x80516d0,0xefbfd5f0,0,0) 3721 telnetd RET __sysctl 0 3721 telnetd CALL __sysctl(0xefbfd5e8,0x2,0x80516f0,0xefbfd5f0,0,0) 3721 telnetd RET __sysctl 0 3721 telnetd CALL __sysctl(0xefbfd5e8,0x2,0x8051710,0xefbfd5f0,0,0) 3721 telnetd RET __sysctl -1 errno 12 Cannot allocate memory 3721 telnetd CALL __sysctl(0xefbfd5e8,0x2,0x8051730,0xefbfd5f0,0,0) 3721 telnetd RET __sysctl 0 3721 telnetd CALL ioctl(0x3,TIOCGETA,0x8052a94) 3721 telnetd RET ioctl 0 3721 telnetd CALL ioctl(0x3,TIOCGETA,0x8052a94) 3721 telnetd RET ioctl 0 3721 telnetd CALL write(0,0x8051ff0,0xc) 3721 telnetd GIO fd 0 wrote 12 bytes "\M^?\M-{\^A\M^?\M-z!\^B\M^?\M-p\M^?\M-~"" 3721 telnetd RET write 12/0xc 3721 telnetd CALL ioctl(0x3,TIOCSWINSZ,0xefbfd664) 3721 telnetd RET ioctl 0 3721 telnetd CALL ioctl(0x3,TIOCGETA,0x8052a94) 3721 telnetd RET ioctl 0 3721 telnetd CALL write(0,0x8051ff0,0x38) 3721 telnetd GIO fd 0 wrote 56 bytes "\M^?\M-z"\^C\^A\0\0\^C\M-b\^C\^D\M^B\^O\^E\M^B\^T\a\M-b\^\\b\M^B\^D\ \M-B\^Z \M^B\^?\v\M^B\^U\f\M^B\^W\r\M^B\^R\^N\M^B\^V\^O\M^B\^Q\^P\M^B\^S\^Q\ \M^@\M^?\M^?\^R\M^@\M^?\M^?\M^?\M-p" 3721 telnetd RET write 56/0x38 3721 telnetd CALL madvise(0x8055000,0x1000,0x5) 3721 telnetd RET madvise 0 3721 telnetd CALL fork 3721 telnetd RET fork 3722/0xe8a 3721 telnetd CALL select(0x10,0xefbfd7a8,0xefbfd728,0xefbfd6a8,0) 3721 telnetd RET select 2 3721 telnetd CALL read(0,0x8051af0,0x400) 3721 telnetd GIO fd 0 read 6 bytes "\M^?\M-}\^A\M^?\M-|"" 3721 telnetd RET read 6 3721 telnetd CALL write(0,0x8051ff0,0x36) 3721 telnetd GIO fd 0 wrote 54 bytes "\r\0\r FreeBSD/i386 (bb08f01.unx.sas.com) (ttyp1)\r\0\r \r\0\r " 3721 telnetd RET write 54/0x36 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 18:46:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25079 for freebsd-current-outgoing; Fri, 4 Dec 1998 18:46:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25070 for ; Fri, 4 Dec 1998 18:46:47 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id BAA10091; Sat, 5 Dec 1998 01:38:05 +0100 From: Luigi Rizzo Message-Id: <199812050038.BAA10091@labinfo.iet.unipi.it> Subject: Re: Dummynet for 3.0? To: xaa@xaa.iae.nl (Mark Huizer) Date: Sat, 5 Dec 1998 01:38:04 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <19981205005136.D817@ariel.xaa.iae.nl> from "Mark Huizer" at Dec 5, 98 00:51:18 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I understand the constraints you were working within. I believe the > > correct approach to the problem would have been to leave 2.2 alone and > > bring DUMMYNET/BRIDGE into -current. The benefits being: > > Ordinarily good and proper sentiments, but this issue came up after > code freeze and this option was not open to Luigi. > > Is the option to add dummynet to 3.0 open now? yes it is, i promise will tackle the problem asap. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 20:03:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01623 for freebsd-current-outgoing; Fri, 4 Dec 1998 20:03:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01618 for ; Fri, 4 Dec 1998 20:03:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id UAA02784; Fri, 4 Dec 1998 20:04:48 -0800 (PST) To: Wilko Bulte cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 02:37:55 +0100." <199812050137.CAA04929@yedi.iaf.nl> Date: Fri, 04 Dec 1998 20:04:48 -0800 Message-ID: <2780.912830688@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Eventually with the growing hardware support we would be back at a > 2 floppy boot set it seems. Not a problem in my opinion, but is there a > general strategy or is it simply 'waiting for the wall'? We're already back there, to be perfectly honest. Even though it wasn't actually documented as such (note to self: document this before 3.0.1), in the 3.0-RELEASE we did indeed hit the wall quite firmly and none of the following: Any EISA bus machine requiring an EISA peripheral for installation. Any machine without an FPU. IDE floppies. Adaptec 1542. Mitsumi CDROM. Matsushita/Panasonic CDROM. Sony (CDU-xx) CDROM. Wangtek QIC tape. Floppy tape. Can be used by boot.flp in actually installing the system. For this, kern.flp is the only option. As time goes on I also expect this list to grow (and be documented :) into pretty much anything we deem "not mainstream enough" to go onto boot.flp, leaving the non-mainstream folks with the abject misery of a 2-floppy installation (said with tongue-seriously-in-cheek since this has been a requirement for just about everyone else for some time now). I know that "mainstream" is also a pretty darn difficult target to hit but we'll just have to do our best using whatever metrics are available. I certainly want *most* people to be able to continue using boot.flp for as long as space permits. When a majority can no longer be thusly accommodated, we'll just shrug and ditch it completely in favor of the 2(*)-floppy solution. - Jordan (*) I hope it's only 2 by then. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 20:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03003 for freebsd-current-outgoing; Fri, 4 Dec 1998 20:15:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02995 for ; Fri, 4 Dec 1998 20:15:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id UAA02953; Fri, 4 Dec 1998 20:17:10 -0800 (PST) To: Mike Smith cc: Wilko Bulte , wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 17:48:52 PST." <199812050148.RAA01551@dingo.cdrom.com> Date: Fri, 04 Dec 1998 20:17:09 -0800 Message-ID: <2949.912831429@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At the moment, the current exploratory strategy is the split kern.flp/ > mfsroot.gz arrangement. It's probably going to make more sense just to > have them as two floppy images for distribution purposes. If the mfsroot image is a UFS filesystem containing an mfsroot.gz file, I'm all for it. I just don't want to lose our newfound ability to say: "There's really nothing special about building MicroFreeBSD systems for installation or any other purpose anymore - just take any kernel with MFS_ROOT turned on and any gzip'd UFS filesystem for its root and Bob's yer uncle!" Or something to that effect. Anyway, I still agree with the argument that it's nice to not have to treat them separately if you're just a novice user so maybe that's what we'll do. Hasn't been that big a deal yet since most can still use the single boot.flp. Hmmmmm. For that matter, we could make sure that the mfsroot was also a bootable floppy image with a /boot/boot.4th file on it which said: : yell 7 emit ." NO, BOOT THE OTHER FLOPPY, YOU KNOB!" cr ; yell key drop reset Or something to that effect. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 21:23:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07697 for freebsd-current-outgoing; Fri, 4 Dec 1998 21:23:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA07690 for ; Fri, 4 Dec 1998 21:23:11 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA13608 for current@freebsd.org; Sat, 5 Dec 1998 00:28:06 -0500 From: Bill Paul Message-Id: <199812050528.AAA13608@skynet.ctr.columbia.edu> Subject: Re: New drivers and install floppy space To: current@FreeBSD.ORG Date: Sat, 5 Dec 1998 00:28:05 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Mike Smith had to walk into mine and say: > At the moment, the current exploratory strategy is the split kern.flp/ > mfsroot.gz arrangement. It's probably going to make more sense just to > have them as two floppy images for distribution purposes. > > The alternative will be to have a single minimal kernel and mfsroot > floppy, and another floppy with a pile of KLD modules on it. This > won't be feasible until the PCI code moves to the new bus architecture > (soon we hope). I would like to see this too, but I would also like to see the ability to provide 3rd party drivers during the install. Not that I really want to encourage people to copy the behavior of Windoze, but it would make life easier for a lot of people (mainly us) to be able to provide FreeBSD drivers in object code form on a floppy diskette, and be able to specify 'install unlisted driver->have disk' and have it show a list of drivers present on the diskette and let the user load the ones he/she wants. This would mean having an installation utility that can parse some kind of description file that provides information about the type of driver, its name, and special loading instructions. We'd also need to provide a kit or sample Makefiles/scripts for generating driver object files and the description files. This would allow hardware vendors to provide drivers that can be loaded and used during installation of FreeBSD, and it would make it easier for users to load FreeBSD using newly written drivers (that is, written by us) without having to wait for the next release or build a custom installation floppy. It would also be nice to provide a kit for adding driver sources to /usr/src in addition to simply loading the driver object module, and strongly encourage driver developers to use it so that developers don't fall into the habit of only providing object code. We want the source code too, after all. Well, I do anyway. -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 22:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09924 for freebsd-current-outgoing; Fri, 4 Dec 1998 22:02:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA09919 for ; Fri, 4 Dec 1998 22:02:43 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id BAA13658; Sat, 5 Dec 1998 01:07:05 -0500 From: Bill Paul Message-Id: <199812050607.BAA13658@skynet.ctr.columbia.edu> Subject: Re: New drivers and install floppy space To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 5 Dec 1998 01:07:04 -0500 (EST) Cc: mike@smith.net.au, wilko@yedi.iaf.nl, current@FreeBSD.ORG In-Reply-To: <3114.912833233@zippy.cdrom.com> from "Jordan K. Hubbard" at Dec 4, 98 08:47:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Jordan K. Hubbard had to walk into mine and say: > > This would mean having an installation utility that can parse > > some kind of description file that provides information about > > the type of driver, its name, and special loading instructions. > > You mean at boot time? This should all be theoretically possible > with the forth interpreter already in there, assuming we add the > right basic words to its wordset. It's no problem parsing files or > loading modules from forth. :) > > - Jordan Well, there are two instances that I'm thinking of. Say you're trying to do a fresh install of FreeBSD on a machine which has an EtherGronk 100 card, and you intend to do an FTP installation. The problem is that the latest FreeBSD release doesn't yet come with a driver for the EtherGronk 100 card. However, somebody has written a beta driver and has source and a KLD module of it available. So you boot the FreeBSD install floppy and it probes and finds all the hardware that it knows about and brings you to the opening menu of sysinstall (or son of sysinstall, or bride of sysinstall, or Abott & Costello meet sysinstall, or whatever we have by then). One of the menu options is 'Install unlisted/3rd party drivers.' So you select this option and it prompts you to insert a floppy diskette (or maybe some other media) with the driver KLD on it and a description file. The installer reads this file, and from there it learns the name of the driver and/or the devices it supports and displays it for the user to see. The user confirms the selection, and the installer kldloads the driver, which probes the EtherGronk 100 card and attaches it as an interface. The user can now proceed to do an FTP install with the EtherGronk card without needing a new boot floppy. Once the FreeBSD install is done, the user can choose to do one of two things: he can either let the installer copy the EtherGronk 100 driver KLD module to the hard disk and fix things up so that it gets loaded when the system boots, or he can not do this and install the driver himself later. In this case, the user has a choice since he'll be able to boot the system from the local disk and reach mult-user mode without needing to have the EtherGronk driver present; this would not be the case if we were talking about a driver for a SCSI disk controller that has to be present in order for the kernel to mount the rootfs. Basically, you're looking for the ability to load a device driver that can be used _during_ the install, and the ability to install a device driver _after_ the install. For example, if the user has an existing FreeBSD system already installed and running and he purchases an EtherGronk 100 card later, he'll want to be able to load the EtherGronk driver just by su'ing to root and running the driver install utility, which will copy the KLD into place, fix things up so that it'll be loaded at bootstrap time, and then kldload it right away so that he can begin using the card without having to reboot the system (unlike a certain other OS which shall remain nameless). The actual installation process should fix things up so that the KLD module is reloaded if the system is rebooted. In the case of a network card you can get away with having this done in the boot scripts, but for something like a SCSI controller driver, I suppose you would have to preload it from the boot loader so that the kernel can use it to mount the rootfs. If this is just a matter of fixing up some forth commands in a file that the boot loader reads, then hey: that's just what the doctor ordered (although I don't know a damn thing about forth). I'm not exactly fond of this whole thing because it has far too many similarities with Solaris and AIX, but I'm willing to overlook this because the KLD system gives you the option of having either a dynamically modular kernel _or_ a single monolithic kernel image. Given the best of both worlds, I can't really complain. One of the biggest problems with this idea right now is that the PCI support code isn't set up to 'remember' devices that it's already probed, so if you force a reprobe it attempts to attach drivers for all PCI devices in the system, including those that already have drivers attached. (The other day on a whim I cooked up an LKM that called pci_configure() just to see what it would do. Boy what a mess.) There's one other thing that annoys me a bit, which is that the busdma support which was migrated over from NetBSD seems incomplete. Currently it's only used by disk controller drivers, however it's also necessary for network drivers. We appear to be missing the bus_dmamap_load_mbuf() routine though, which would vastly simplify things for network drivers. Also, there are no man pages. -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 22:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10619 for freebsd-current-outgoing; Fri, 4 Dec 1998 22:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10613 for ; Fri, 4 Dec 1998 22:11:27 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id BAA03584 for ; Sat, 5 Dec 1998 01:11:10 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA05019; Sat, 5 Dec 1998 01:11:09 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id BAA03726; Sat, 5 Dec 1998 01:11:09 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812050611.BAA03726@bb01f39.unx.sas.com> Subject: telnetd again (Kerberos & make release == very strange) To: freebsd-current@FreeBSD.ORG Date: Sat, 5 Dec 1998 01:11:09 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Following up my own mail concerning telnetd.... which still doesn't explain the uname() function not being called, but does help explain where telnetd came from... :-( The installed version of telnetd: -r-xr-xr-x 1 root wheel 61352 Dec 2 11:01 /usr/libexec/telnetd If I then 'cd /usr/src/libexec/telnetd && make all install' : -r-xr-xr-x 1 root wheel 35328 Dec 5 00:36 /usr/libexec/telnetd So, why the difference? Let's go back to our 'make release' log and figure out where telnetd came from... [to summarize everything below, our -SNAP systems are comprised of the Kerberose versions of all the programs (where there is one), which are then themselves overwritten by the regular versions of the programs when the first make world is done]. First, some info from the head of the log: ---> Wed Dec 2 06:26:18 EST 1998 - make release mkdir -p /snap/release cd /usr/src/release/../etc && make distrib-dirs DESTDIR=/snap/release mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /snap/release/ A little while later we install everything: -------------------------------------------------------------- >>> Installing everything.. -------------------------------------------------------------- cd /usr/src; /usr/obj/elf/usr/src/tmp/usr/bin/make -f Makefile.inc1 install Install the live version into the release area: ===> libexec/telnetd install -c -s -o root -g wheel -m 555 telnetd /snap/release/usr/libexec This is the 'normal' version of telnetd. We then checkout the different versions of telnetd: (U statements left off) cvs checkout: Updating src/crypto/telnet/telnetd cvs checkout: Updating src/eBones/libexec/telnetd cvs checkout: Updating src/kerberosIV/libexec/telnetd cvs checkout: Updating src/libexec/telnetd cvs checkout: Updating src/secure/libexec/telnetd We cleanout the objects and related derived files (even though we haven't actually built anything yet and these are not present). ===> libexec/telnetd rm -f telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o utility.o t elnetd.8.gz telnetd.8.cat.gz rm -f .depend /usr/src/libexec/telnetd/GRTAGS /usr/src/libexec/telnetd/GSYMS /us r/src/libexec/telnetd/GTAGS We generate the object directory (so what did we cleanout above?) ===> libexec/telnetd /usr/obj/elf/usr/src/libexec/telnetd created for /usr/src/libexec/telnetd Hey! We're building telnetd! ===> libexec/telnetd ... cc -nostdinc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_ HACK -I/usr/src/libexec/telnetd/../../lib -I/usr/obj/elf/usr/src/tmp/usr/inclu de -c /usr/src/libexec/telnetd/utility.c cc -nostdinc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_ HACK -I/usr/src/libexec/telnetd/../../lib -I/usr/obj/elf/usr/src/tmp/usr/inclu de -o telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o utility.o -lutil -ltermcap -ltelnet gzip -cn /usr/src/libexec/telnetd/telnetd.8 > telnetd.8.gz Ok, now we're generated an aout object tree: ===> libexec/telnetd /usr/obj/aout/usr/src/libexec/telnetd created for /usr/src/libexec/telnetd Now we install the telnetd we just created: ===> libexec/telnetd install -c -s -o root -g wheel -m 555 telnetd /usr/libexec install -c -o root -g wheel -m 444 telnetd.8.gz /usr/share/man/man8 and install it into the stage tree: ===> libexec/telnetd cd /usr/src/libexec/telnetd ; make install DESTDIR=/R/stage/trees/bin SHARED=cop ies install -c -s -o root -g wheel -m 555 telnetd /R/stage/trees/bin/usr/libexec Hey, we're cleaning out a kerberos version of telnetd... ===> libexec/telnetd rm -f /usr/src/kerberosIV/libexec/telnetd/../../lib/libkadm/kadm_err.h /usr/src/ kerberosIV/libexec/telnetd/../../lib/libkadm/kadm_err.c /usr/src/kerberosIV/libe xec/telnetd/../../lib/libkadm/kadm_err.et /usr/src/kerberosIV/libexec/telnetd/.. /../lib/libkrb/krb_err.h /usr/src/kerberosIV/libexec/telnetd/../../lib/libkrb/kr b_err.c /usr/src/kerberosIV/libexec/telnetd/../../lib/libkrb/krb_err.et telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o utility.o authenc.o telne td.8.gz telnetd.8.cat.gz rm -f .depend /usr/src/kerberosIV/libexec/telnetd/GRTAGS /usr/src/kerberosIV/lib exec/telnetd/GSYMS /usr/src/kerberosIV/libexec/telnetd/GTAGS Cool, we're creating the object tree for the kerberos version: ===> libexec/telnetd /usr/obj/usr/src/kerberosIV/libexec/telnetd created for /usr/src/kerberosIV/libe xec/telnetd And now we run mkdep for the kerberos version: ===> libexec/telnetd rm -f .depend mkdep -f .depend -a -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV and now we build the kerberos version: ===> libexec/telnetd ... cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAU THENTICATION -DENCRYPTION -I/usr/src/kerberosIV/libexec/telnetd/../../../crypto /telnet -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_ H -I/usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/b in\" -DSBINDIR=\"/usr/sbin\" -o telnetd global.o slc.o state.o sys_term.o tel netd.o termstat.o utility.o authenc.o -lutil -ltermcap -L/usr/obj/usr/src/kerbe rosIV/libexec/telnetd/../../lib/libtelnet -ltelnet -ldes -L/usr/obj/usr/src/ker berosIV/libexec/telnetd/../../lib/libkrb -lkrb gzip -cn /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/teln etd.8 > telnetd.8.gz Hey! Wow! What's this? ===> libexec/telnetd install -c -s -o root -g wheel -m 555 telnetd /usr/libexec install -c -o root -g wheel -m 444 telnetd.8.gz /usr/share/man/man8 We just wrote the kerberos version into /usr/libexec!! (the chroot'd tree) And now we turn around and install it into the stage tree under krb: ===> libexec/telnetd cd /usr/src/kerberosIV/libexec/telnetd ; make install DESTDIR=/R/stage/trees/krb SHARED=copies install -c -s -o root -g wheel -m 555 telnetd /R/stage/trees/krb/usr/libexec So, our little stroll through 'make release' shows that the default version of telnetd (and other programs) are all the kerberos versions. Can someone verify that this is how the release system should work? A make world does not build the kerberos code by default, so the first make world done an an installed system will overwrite all the kerberos versions of the executables. Also note the kerberos versions of the code are much larger than their counter-parts (save some space on those cd's!). Comments? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 22:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13418 for freebsd-current-outgoing; Fri, 4 Dec 1998 22:53:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13413 for ; Fri, 4 Dec 1998 22:53:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA03444; Fri, 4 Dec 1998 22:54:27 -0800 (PST) To: Bill Paul cc: mike@smith.net.au, wilko@yedi.iaf.nl, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 01:07:04 EST." <199812050607.BAA13658@skynet.ctr.columbia.edu> Date: Fri, 04 Dec 1998 22:54:27 -0800 Message-ID: <3440.912840867@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So you boot the FreeBSD install floppy and it probes and finds all > the hardware that it knows about and brings you to the opening menu > of sysinstall (or son of sysinstall, or bride of sysinstall, or > Abott & Costello meet sysinstall, or whatever we have by then). > One of the menu options is 'Install unlisted/3rd party drivers.' > So you select this option and it prompts you to insert a floppy > diskette (or maybe some other media) with the driver KLD on it and > a description file. The installer reads this file, and from there > it learns the name of the driver and/or the devices it supports I think this is the right basic idea, but the wrong place to attack the problem. To put it succinctly, it's just not possible right now to kld in any conceivable driver you might want (most notably those requiring large contiguous DMA regions). It is possible, however, to grab them with the 3rd stage boot code and aggregate the whole mess together in such a way that it's functionally indistinguishable from the monolithic kernel image once booted. If you want to make this a menu oriented process with options to insert other media (or heck, grab things over the net) or otherwise populate memory with lots of optional components before booting the kernel, that's all quite conceivable from the forth layer. You wouldn't be able to be very fancy with your UI, but then I don't think you'd need to be: +---------------- driver configuration menu -------------+ | | | >BOOT - Boot kernel with default driver set. | | LOAD - Load 3rd party drivers for installation. | | CLI - Launch a command interpreter instance. | | QUIT - Reset the system | | | | Enter one of the options above and press [enter] | +--------------------------------------------------------+ Would pretty much do the trick, the LOAD option bringing up a submenu allowing you to choose floppy, bootp, tftp, whatever.. And it's all technology within our grasp today without having to implement fully kld'able device drivers or make DEVFS mandatory first. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 22:53:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13602 for freebsd-current-outgoing; Fri, 4 Dec 1998 22:53:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA13445; Fri, 4 Dec 1998 22:53:25 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.1.13]) by yonge.cs.toronto.edu with SMTP id <86515-637>; Sat, 5 Dec 1998 01:53:07 -0500 Received: by qew.cs.toronto.edu id <37814-15902>; Sat, 5 Dec 1998 01:52:55 -0500 Subject: Re: kmem, tty, bind security enhancements commit. From: David Holland To: eivind@yes.no (Eivind Eklund) Date: Sat, 5 Dec 1998 01:52:49 -0500 Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG In-Reply-To: <19981201195028.A21015@follo.net> from "Eivind Eklund" at Dec 1, 98 01:50:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Dec5.015255edt.37814-15902@qew.cs.toronto.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm somewhat surprised at the getuid() test in ntalkd being there > at all - it seems like this should have been done with permissions > instead of getuid(), and shouldn't be needed anyway. It looks to me like a broken version of the test many inetd-spawned daemons have to make sure they're not accidentally run on the command line. Normally there'd be a getpeername() on stdin or something, but there isn't. -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 23:00:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14396 for freebsd-current-outgoing; Fri, 4 Dec 1998 23:00:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14385; Fri, 4 Dec 1998 23:00:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA03533; Fri, 4 Dec 1998 23:02:03 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: telnetd again (Kerberos & make release == very strange) In-reply-to: Your message of "Sat, 05 Dec 1998 01:11:09 EST." <199812050611.BAA03726@bb01f39.unx.sas.com> Date: Fri, 04 Dec 1998 23:02:03 -0800 Message-ID: <3530.912841323@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmmm. I think it's time for the release engineer and Mark Murray to go off into a corner somewhere and have a quick discussion about this one. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 23:09:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14885 for freebsd-current-outgoing; Fri, 4 Dec 1998 23:09:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-43-dbn.dial-up.net [196.34.155.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14880 for ; Fri, 4 Dec 1998 23:09:36 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA10277; Sat, 5 Dec 1998 08:58:19 +0200 (SAT) From: Robert Nordier Message-Id: <199812050658.IAA10277@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199812042345.PAA00709@dingo.cdrom.com> from Mike Smith at "Dec 4, 98 03:45:55 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 5 Dec 1998 08:58:17 +0200 (SAT) Cc: joelh@gnu.org, rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA14881 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Regarding nextboot, I can't get your question into any kind of > > > context, sorry. Is this just an entirely separate issue, or > > > does "still works" relate to using FBSDBOOT versus not using > > > FBSDBOOT in some way? > > > > This is a related but separate issue. > ... > Now, one way to write this program immediately suggests itself to me. > > Rewrite nextboot for Windows and put a GUI on it. Hence, my > > question. I don't know any other way to talk to the boot manager, > > although I'm open to suggestions. > > The problem is that it's not a related issue; nextboot doesn't have > anything to do with what you're discussing - it's an outdated way to > talk to the old bootstrap code in order to pass arguments to the 'boot:' > prompt. It doesn't have any effect on the active partition. You're going off half-cocked here, Mike. The issue we're discussing is completely one of passing arguments to the boot prompt and, as I'd *already* mentioned to Joel, his idea is probably the best way of getting this info out of Windows and into BSD. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 4 23:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16848 for freebsd-current-outgoing; Fri, 4 Dec 1998 23:42:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (49-sweet.camalott.com [208.239.153.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16841 for ; Fri, 4 Dec 1998 23:42:27 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id BAA01578; Sat, 5 Dec 1998 01:41:33 -0600 (CST) (envelope-from joelh@gnu.org) Date: Sat, 5 Dec 1998 01:41:33 -0600 (CST) Message-Id: <199812050741.BAA01578@detlev.UUCP> X-Authentication-Warning: detlev.UUCP: joelh set sender to joelh@gnu.org using -f To: freebsd-current@FreeBSD.ORG Subject: Cron getting malloc warning in grandchild From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a problem with cron. Is anybody else seeing this? Summary: After swap space was filled, a cron on an 18 Oct -current system started getting free() warnings, always in the same segment of code. A reboot, an upgrade to yesterday's -current, and a zeroed-out swap partition have failed to have any effect. Details: While I was away over Thanksgiving holidays and the early part of this week, a box of mine (heimdall by name) somehow filled up its swap. (I don't particularly see why, since nobody could log in, so it was just acting as a small ppp gateway and doing its normal cron jobs, the most taxing of which is a cvs that it's been doing every night for months). (This is the only time in this narrative that any swap issues were either noticed by my own swapinfo checks, or logged in /var/log/messages.) I left on 25 Nov, and swap filled up on the 28th. Over the next six hours, several small cron subjobs were killed, as well as ppp. One cron dying message was apparently doubled: Nov 28 11:00:02 heimdall /kernel: pid 8401 (cron), uid 0, was killed: out of swap space Nov 28 11:00:04 heimdall /kernel: pid 8403 (cron), uid 0, was killed: out of swap space Nov 28 11:00:04 heimdall /kernel: pid 8402 (cron), uid 0, was killed: out of swap space Nov 28 11:00:04 heimdall last message repeated 2 times Nov 28 11:00:04 heimdall /kernel: pid 8399 (cron), uid 0, was killed: out of swap space By the time I heard about this, it was 1 Dec at 18:00. Calling somebody with access to the console, I discovered that they could not log in; no prompt. No shock. I asked them to give it a 120 reset. The machine rebooted apparently normally, with no fsck problems. At 02:05 on 2 Dec, I started receiving messages from cron: X-From-Line: daemon Wed Dec 2 02:05:04 1998 Received: (from root@localhost) by heimdall.UUCP (8.9.1/8.9.1) id CAA02259; Wed, 2 Dec 1998 02:05:03 -0600 (CST) (envelope-from root) Date: Wed, 2 Dec 1998 02:05:03 -0600 (CST) Message-Id: <199812020805.CAA02259@heimdall.UUCP> From: root (Cron Daemon) To: root Subject: Cron /usr/libexec/atrun X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: CRON in malloc(): warning: pointer to wrong page. I arrived ten hours later and was greetd by several hundred of these messages. Checking the logs, I saw that no swap space warnings had been issued since the cold boot on 1 Dec. Since I didn't have time to troubleshoot it immediately, and no hugely important cron tasks were on that machine, I killed cron. I don't know precisely when I did this; the last such messages were sent at 15:00. Meanwhile, every cron task scheduled from 02:05 to 15:00 issued such a message. All of these tasks were scheduled from /etc/crontab. (The only user crontab entry runs at 02:00.) Today, (4 Dec, 13:30), I installworld'd and made a new kernel from a -current based on sources from cvsup2, as of 3 Dec 05:11. This evening, at 22:02, I rebooted into single user mode, dd'd over the swap partition, and rebooted again. In short order, the same messages began to appear again. Again, I killed cron. I've now instrumented cron to provide all relevant pids its mail, and am running it with MALLOC_OPTIONS=AX and with -x proc, so if it fails tonight I can start tracking down the problem. Stay tuned for more information as news breaks. Since the first reboot, I've only seen three unexplained problems. The first was a sendmail error that got logged night before last, and never recurred: Dec 3 00:38:19 heimdall sendmail[7858]: SAA22698: SYSERR: putoutmsg (mail.camalott.com.): error on output channel sending "451 fill_fd: detlev-ip@gnu.org... end of deliver(relay): fd 0 not open: Bad file descriptor": Input/output error Dec 3 00:38:19 heimdall sendmail[7858]: SAA22698: SYSERR(joelh): fill_fd: detlev-ip@gnu.org... end of deliver(relay): fd 0 not open: Bad file descriptor Dec 3 00:38:20 heimdall sendmail[7858]: SAA22698: SYSERR(joelh): fill_fd: detlev-ip@gnu.org... end of deliver(relay): fd 1 not open: Bad file descriptor Dec 3 00:38:20 heimdall sendmail[7858]: SAA22698: SYSERR(joelh): fill_fd: detlev-ip@gnu.org... end of deliver(relay): fd 2 not open: Bad file descriptor The other was while I was instrumenting cron, I had a shell script segfault on me: Dec 4 22:53:04 heimdall /kernel: pid 606 (sh), uid 0: exited on signal 11 (core dumped) The third unexplained problem looks like I've misconfigured ppp. Ever since the installworld, ppp starts up with an error: Dec 4 22:17:21 heimdall ppp[234]: Error: iface_inAdd: ioctl(SIOCAIFADDR): 0.0.0.0: Destination address required This doesn't appear to affect operation, so I haven't yet investigated it. I only mention it for completeness. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 01:14:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22188 for freebsd-current-outgoing; Sat, 5 Dec 1998 01:14:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22175 for ; Sat, 5 Dec 1998 01:14:20 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA30164; Sat, 5 Dec 1998 20:13:55 +1100 Date: Sat, 5 Dec 1998 20:13:55 +1100 From: Bruce Evans Message-Id: <199812050913.UAA30164@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Subject: Re: FreeBSD fsck updated Cc: current@FreeBSD.ORG, Don.Lewis@tsc.tdk.com, julian@whistle.com, mckusick@McKusick.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Bruce Evans writes: >> >+ if (fs->fs_fmod != 0) { >> >+ pwarn("MODIFIED FLAG SET IN SUPERBLOCK"); >> >+ if (preen) >> >+ printf(" (FIXED)\n"); >> >+ if (preen || reply("FIX") == 1) { >> >+ fs->fs_fmod = 0; >> >+ sbdirty(); >> >+ } >> >+ } >> >> ... >> >> Clearing fs_fmod here seems to be bogus. It is set (to 0 or 1) >> ... >We (Julian & me) are the ones who added this bit of code to clear >the modified flag after seeing a panic caused by mounting a filesystem >read-only that had this bit set (even though it was "clean", as >the previous fsck didn't clear this bit). I forget exactly how it >can happen, but it can (and did). It can't happen now. This was fixed without comment in the big soft updates commit. Bruce RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v Working file: ffs_vfsops.c head: 1.92 ... ---------------------------- revision 1.76 date: 1998/03/08 09:59:06; author: julian; state: Exp; lines: +63 -22 Reviewed by: dyson@freebsd.org (john Dyson), dg@root.com (david greenman) Submitted by: Kirk McKusick (mcKusick@mckusick.com) Obtained from: WHistle development tree ---------------------------- Index: ffs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.75 retrieving revision 1.76 diff -c -r1.75 -r1.76 *** ffs_vfsops.c 1998/03/07 21:36:36 1.75 --- ffs_vfsops.c 1998/03/08 09:59:06 1.76 *************** *** 31,37 **** * SUCH DAMAGE. * * @(#)ffs_vfsops.c 8.31 (Berkeley) 5/20/95 ! * $Id: ffs_vfsops.c,v 1.75 1998/03/07 21:36:36 dyson Exp $ */ #include "opt_quota.h" --- 31,37 ---- * SUCH DAMAGE. * * @(#)ffs_vfsops.c 8.31 (Berkeley) 5/20/95 ! * $Id: ffs_vfsops.c,v 1.76 1998/03/08 09:59:06 julian Exp $ */ #include "opt_quota.h" ... *************** *** 1200,1205 **** --- 1239,1246 ---- if (allerror) return (allerror); bp = getblk(mp->um_devvp, SBLOCK, (int)fs->fs_sbsize, 0, 0); + fs->fs_fmod = 0; + fs->fs_time = time.tv_sec; bcopy((caddr_t)fs, bp->b_data, (u_int)fs->fs_sbsize); /* Restore compatibility to old file systems. XXX */ dfs = (struct fs *)bp->b_data; /* XXX */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 01:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22396 for freebsd-current-outgoing; Sat, 5 Dec 1998 01:14:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from norquay.tor.shaw.wave.ca (mail.tor.shaw.wave.ca [24.64.63.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22390 for ; Sat, 5 Dec 1998 01:14:38 -0800 (PST) (envelope-from pc@shaw.wave.ca) Received: from cs929626-a.mtmc1.on.wave.home.com ([24.64.174.71]) by norquay.tor.shaw.wave.ca (Netscape Messaging Server 3.0) with SMTP id AAA28034; Sat, 5 Dec 1998 04:15:39 -0500 From: "C. Peter Constantinidis" To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) Date: Sat, 05 Dec 1998 09:14:21 GMT Message-ID: <3668f84f.12730770@mail.tor.shaw.wave.ca> References: <199812010607.WAA03051@apollo.backplane.com> In-Reply-To: <199812010607.WAA03051@apollo.backplane.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA22391 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi.. I don't know if you've committed this yet or not. But from what I can tell you from personal experience, being threatened with smurfs on irc, etc. As well as knowing many linux script kiddiez that just foam at the mouth to find some, any, loophole that can be used to screw things up.. If your proposal makes things safer, then it should go in. This is part of the reason that I lean towards FreeBSD rather than Linux.. it's not as widely popular or 'known'.. so the attacks for it are not as numerous.. if the kiddiez knew all one had to do was overload the mbuf, then they would do it daily. (And of course, the FreeBSD community doesn't seem composed of children.) So yeah, I like the sounds of a rate limiting feature by default. P. -- pc@shaw.wave.ca DSS/D-H: 0x81F1BC09 DFD1 D149 40BD 8139 05D5 D8FA 2BA4 E143 81F1 BC09 RSA: 0x6DC376E5 0AE1 0FB7 A43A 0818 3EC4 F2DD 1458 EFCE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 02:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25679 for freebsd-current-outgoing; Sat, 5 Dec 1998 02:07:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25672 for ; Sat, 5 Dec 1998 02:07:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA12989; Sat, 5 Dec 1998 02:07:18 -0800 (PST) (envelope-from obrien) Message-ID: <19981205020718.A12672@nuxi.com> Date: Sat, 5 Dec 1998 02:07:18 -0800 From: "David O'Brien" To: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? Reply-To: obrien@NUXI.com References: <199812042331.AAA02402@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812042331.AAA02402@oranje.my.domain>; from Marc van Woerkom on Sat, Dec 05, 1998 at 12:31:23AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Today, while fetching egcs, I noticed that those folks use bzip2 for > compressing their snapshots: Correction, they provied bzip2 compressed tarballs only for Releases. And since there is now a 1.1.1 release, you may notice that the bzip2 distfile is used by ports/lang/egcs ;-) -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 02:19:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26282 for freebsd-current-outgoing; Sat, 5 Dec 1998 02:19:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26277 for ; Sat, 5 Dec 1998 02:19:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA13080; Sat, 5 Dec 1998 02:19:14 -0800 (PST) (envelope-from obrien) Message-ID: <19981205021914.C12672@nuxi.com> Date: Sat, 5 Dec 1998 02:19:14 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space Reply-To: obrien@NUXI.com References: <199812050137.CAA04929@yedi.iaf.nl> <2780.912830688@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <2780.912830688@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, Dec 04, 1998 at 08:04:48PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When a majority can no longer be thusly accommodated, we'll just shrug > and ditch it completely in favor of the 2(*)-floppy solution. It is not that bad. I'm doing more and more boot off the CDROM installs. I assume sysinstall + boot kernel can be quite large there. Is the boot kernel there a full GENERIC kernel? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 02:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27812 for freebsd-current-outgoing; Sat, 5 Dec 1998 02:37:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27807 for ; Sat, 5 Dec 1998 02:36:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA13146; Sat, 5 Dec 1998 02:36:41 -0800 (PST) (envelope-from obrien) Message-ID: <19981205023641.D12672@nuxi.com> Date: Sat, 5 Dec 1998 02:36:41 -0800 From: "David O'Brien" To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: feature requests for install Reply-To: obrien@NUXI.com References: <199812030501.AAA03579@kot.ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Richard Wackerbarth on Thu, Dec 03, 1998 at 05:27:18AM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The first step is to "contrib"-ify the dhcp client. You will also have to turn on BPF in the kernel. Garrett Wollman has mentioned that there is no real reason this should be the case, except for some bad design somewhere in the kernel. For security reasons, it would be nice to fix that problem. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 02:37:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28010 for freebsd-current-outgoing; Sat, 5 Dec 1998 02:37:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28005 for ; Sat, 5 Dec 1998 02:37:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA28622; Sat, 5 Dec 1998 02:39:16 -0800 (PST) To: obrien@NUXI.com cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 02:19:14 PST." <19981205021914.C12672@nuxi.com> Date: Sat, 05 Dec 1998 02:39:15 -0800 Message-ID: <28619.912854355@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is not that bad. I'm doing more and more boot off the CDROM installs. > I assume sysinstall + boot kernel can be quite large there. It is that bad. boot.flp is what the CDROM is invoking - /kernel is totally ignored as a consequence of the El Torrito boot hack. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 02:41:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28377 for freebsd-current-outgoing; Sat, 5 Dec 1998 02:41:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28372 for ; Sat, 5 Dec 1998 02:41:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA13185; Sat, 5 Dec 1998 02:40:49 -0800 (PST) (envelope-from obrien) Message-ID: <19981205024049.D10572@nuxi.com> Date: Sat, 5 Dec 1998 02:40:49 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space Reply-To: obrien@NUXI.com References: <19981205021914.C12672@nuxi.com> <28619.912854355@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <28619.912854355@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Dec 05, 1998 at 02:39:15AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is that bad. boot.flp is what the CDROM is invoking - /kernel is > totally ignored as a consequence of the El Torrito boot hack. Could cdrom.boot be created (and used in the mkisofs envocation) the same way as boot.flp, but contain all drivers and of course be several megs? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 03:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29562 for freebsd-current-outgoing; Sat, 5 Dec 1998 03:03:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29557 for ; Sat, 5 Dec 1998 03:03:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id DAA28763; Sat, 5 Dec 1998 03:04:44 -0800 (PST) To: obrien@NUXI.com cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 02:40:49 PST." <19981205024049.D10572@nuxi.com> Date: Sat, 05 Dec 1998 03:04:44 -0800 Message-ID: <28760.912855884@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could cdrom.boot be created (and used in the mkisofs envocation) the same > way as boot.flp, but contain all drivers and of course be several megs? Ask Joerg - he was the last one working on "real" boot blocks for CDROMs. I've certainly never seen such a thing work or even know how I'd go about creating such a CD image, so your guess is really as good as mine here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 03:46:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03064 for freebsd-current-outgoing; Sat, 5 Dec 1998 03:46:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03054 for ; Sat, 5 Dec 1998 03:46:26 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id MAA03186; Sat, 5 Dec 1998 12:45:58 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id NAA01058; Sat, 5 Dec 1998 13:47:34 GMT Message-ID: <19981205134734.08174@breizh.prism.uvsq.fr> Date: Sat, 5 Dec 1998 13:47:34 +0000 From: Nicolas Souchu To: Mike Smith Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: nlpt and severe system slow down References: <199812031346.FAA22883@rah.star-gate.com> <199812032243.OAA00335@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199812032243.OAA00335@dingo.cdrom.com>; from Mike Smith on Thu, Dec 03, 1998 at 02:43:04PM -0800 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 02:43:04PM -0800, Mike Smith wrote: > >> This is my config for nlpt: >> >> controller ppbus0 >> controller ppc0 at isa? irq 7 vector ppcintr >> device nlpt0 at ppbus? >> >> >> If I shutdown my laser jet 4mp while printing, my system comes to crawl for >> instance my mouse and keyboard don't respond. The system is not quite dead >> because I can see that the cursor moves or rather jumps sporadically >> on my X desktop >> >> Has anyone else seeng this behavior? > >Yes; it's better than the old 'lpt' driver which would freeze your >system until you turned the printer back on. Mike, you seem to understand this well, I do not :) I'll have to if I want to make ppbus drivers run all together. So I hope Bruce is reading this mail too... I know we discussed about it, I have the mails here. So, is there any tutorial about how spls are working? Or which are the related files in the tree? > >Nicolas should probably look at this one... > Why does the system freeze like this? Is it permanently interrupted by an incorrect parallel port line level? BTW, what's the interrupt 'level' (I should say 'set' maybe) of dev_null drivers which are not said tty, bio or net in the MACHINE file? >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 03:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03521 for freebsd-current-outgoing; Sat, 5 Dec 1998 03:52:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03516 for ; Sat, 5 Dec 1998 03:52:01 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Sat, 5 Dec 1998 11:50:40 -0000 Message-ID: From: Paul Richards To: "'Mike Smith'" , Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: RE: KLD - what's the idea? Date: Sat, 5 Dec 1998 11:50:39 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Saturday, December 05, 1998 12:08 AM > To: Garrett Wollman > Cc: Mike Smith; freebsd-current@FreeBSD.ORG > Subject: Re: KLD - what's the idea? > > > > < said: > > > > > I'm not fond of this sort of 'active match' approach at all; > > > particularly for pccard devices it makes it impossible to apply an > > > existing driver to a new peripheral without patching and > rebuilding the > > > driver, which is extremely lame. > > > > The driver needs to know what sort of bus it's on -- > there's simply no > > escaping that. > > I don't see anywhere I've even considered suggesting this. The point > I'm trying to make is that the match process needs to be run by the > *bus* code - it has access to the list of drivers attached to it as > well as to the results of it's PnP probes, and is the only > module in a > position to match the two together. > > The correct way to do this is to have a set of bindings between PnP > identifiers and driver names. Embedding this information in > the driver > is IMO wrong, simply because updating a driver is difficult while > updating a text file is easy. > I agree with this basic idea, I was starting to think along these lines when I was looking at the way the pci drivers are probed. If the table is generic enough we could use it for all hardware that can be identified by obtaining a signature and if the entry in the table is signature:entry point then we end up with a totally different way of looking at hardware probing that's actually a lot more powerful than we have now yet also simplifies the drivers since they don't need any bus specific probe code. You'd only need code for identifying and scanning each bus to obtain the bus specific hardware signatures and then you'd jump to the entry point. This can either be a card specific probe routine (for identifying revisions/clones/whatever) or doing something else entirely, possibly a null op for some hardware or something much more complicated e.g. if the signature represents another bus it can call the bus scan routine for that bus. The table doesn't even have to be static either, you could have loadable device drivers register their signature:entry point in a dynamic table (link it to a file for persistency if needed) so that you can add new drivers to your system on the fly but have the system updated so it's aware of the new hardware next time it boots. Management of device driver loading becomes an administration issue, if a piece of hardware/driver is causing you problems you can deregister the entry point from the table so it doesn't cause problems on next boot. Some of this duplicates what can be done with the boot time configuration tools but I think it's a more orthogonal solution to the whole issue of managing devices and drivers. With not too much more work you could make this mechanism work for all hardware, for pci and other buses that you can safely probe for hardware id's you only have to write the bus scan routines but there's no reason why we couldn't modify the hardware probe phase to do the probing of other devices from a generic mechanism rather than from within the actual drivers. We already sort of do this with drivers having pci specfic probe routines that are maintained as part of the pci probe code rather than with the drivers. This doesn't have to replace the existing driver probe routines, they can be actually called as the entry point and they can do the same checks as they currenty do if that seems prudent but it does avoid the need to call every driver for every id to see if that driver wants to accept the hardware. It also provides a mechanism for supporting multiple drivers for the same hardware and be able to determine which driver is used by changing the table rather than the kernel config (possibly mute point with loadable drivers). If need be there could still be a catchall stage at the end of the boot process that calls all the probe routines for hardware that is still not allocated to a driver. This would still be a win overall even if this still happened since you'd only call all the probe routines for a few rogue pieces of hardware that weren't known in the table rather than for every piece of hardware in the machine and you could update the table the first time this happens so that next time it has a driver allocated or is flagged as not being supported. On the other hand, you might not want to do this and just have it reported as an unsupported piece of hardware. Food for thought..... Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 04:03:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04850 for freebsd-current-outgoing; Sat, 5 Dec 1998 04:03:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04845 for ; Sat, 5 Dec 1998 04:03:15 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Sat, 5 Dec 1998 12:01:00 -0000 Message-ID: From: Paul Richards To: "'Bill Paul'" , jkh@zippy.cdrom.com Cc: mike@smith.net.au, wilko@yedi.iaf.nl, current@FreeBSD.ORG Subject: RE: New drivers and install floppy space Date: Sat, 5 Dec 1998 12:00:59 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Bill Paul [mailto:wpaul@skynet.ctr.columbia.edu] > Sent: Saturday, December 05, 1998 6:07 AM > To: jkh@zippy.cdrom.com > Cc: mike@smith.net.au; wilko@yedi.iaf.nl; current@FreeBSD.ORG > Subject: Re: New drivers and install floppy space > ....... > Basically, you're looking for the ability to load a device driver > that can be used _during_ the install, and the ability to install > a device driver _after_ the install. For example, if the user has > an existing FreeBSD system already installed and running and he > purchases an EtherGronk 100 card later, he'll want to be able to load > the EtherGronk driver just by su'ing to root and running the driver > install utility, which will copy the KLD into place, fix things up > so that it'll be loaded at bootstrap time, and then kldload it right > away so that he can begin using the card without having to reboot > the system (unlike a certain other OS which shall remain nameless). > > The actual installation process should fix things up so that the > KLD module is reloaded if the system is rebooted. In the case of > a network card you can get away with having this done in the boot > scripts, but for something like a SCSI controller driver, I suppose > you would have to preload it from the boot loader so that the kernel > can use it to mount the rootfs. If this is just a matter of fixing > up some forth commands in a file that the boot loader reads, then > hey: that's just what the doctor ordered (although I don't know a > damn thing about forth). > I'm not exactly fond of this whole thing because it has far too > many similarities with Solaris and AIX, but I'm willing to overlook > this because the KLD system gives you the option of having either > a dynamically modular kernel _or_ a single monolithic kernel image. > Given the best of both worlds, I can't really complain. > > One of the biggest problems with this idea right now is that the > PCI support code isn't set up to 'remember' devices that it's already > probed, so if you force a reprobe it attempts to attach drivers for > all PCI devices in the system, including those that already have > drivers attached. (The other day on a whim I cooked up an LKM that > called pci_configure() just to see what it would do. Boy what a mess.) > Hmm, see the other thread of Mike's that I replied to regarding using a table for allocating drivers to hardware. Seems to me that these issues are closely related and both cry out for the same type of device driver solution. Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 04:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07892 for freebsd-current-outgoing; Sat, 5 Dec 1998 04:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07887 for ; Sat, 5 Dec 1998 04:33:06 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.11]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA2429; Sat, 5 Dec 1998 13:32:48 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 05 Dec 1998 13:38:14 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Icom Development Subject: RE: libc_r pthread build problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Dec-98 Jeroen Ruigrok/Asmodai wrote: > On 03-Dec-98 Icom Development wrote: >> Hi, >> My "make" in /usr/src fails with the errors I have appended, >> on uthread_mutex.c. Have I missed an update or is this a known problem? > I have cvsupped twice or thrice (about 6 hours in between) in between builds > to make sure I didn't miss a commit... Having found no problem anywhere I simply deleted the file and cvsupped again. My make world went flawlessly... Still not understanding why the file got messed up IF it was indeed messed up... Anyways... No problems with uthread_mutex.c... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 05:07:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09553 for freebsd-current-outgoing; Sat, 5 Dec 1998 05:07:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09539 for ; Sat, 5 Dec 1998 05:07:37 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id HAA07841; Sat, 5 Dec 1998 07:06:58 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Sat, 5 Dec 1998 07:06:58 -0600 (CST) From: Richard Wackerbarth To: Paul Richards cc: "'Mike Smith'" , Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: RE: KLD - what's the idea? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Selecting the "ideal" driver for a given device can be non-trivial. I like the general idea that Apple uses to allow drivers to be "hot swapable". Each driver has the ability to phase itself out and allow a new driver to take its place. This permits the system to start up with very generic drivers and replace them on the fly with better ones which are "tuned" to the particular characteristics of some hardware. It also handles the case of driver upgrade. Essentially, each driver is allowed to "bid" for a device. Whenever a driver becomes the highest bidder, it takes the device and runs it. At some later time, it can get notified that it has been "out bid" and must relinquish the device to the new driver. By providing a "registry", the "auctioneer" can speed the process along by first soliciting a bid from the likely high bidder. The nice thing is that all of this auction can take place in user-land. Each driver can be represented by its agent and only loaded to confirm its "bid" and take control of the device. Most drivers can be represented by the generic agent that works from the "registry" and never get loaded unless they are needed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 06:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12619 for freebsd-current-outgoing; Sat, 5 Dec 1998 06:11:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12613 for ; Sat, 5 Dec 1998 06:11:24 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA15627 for freebsd-current@FreeBSD.ORG; Sat, 5 Dec 1998 15:11:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B14C714BE; Sat, 5 Dec 1998 15:03:16 +0100 (CET) Date: Sat, 5 Dec 1998 15:03:16 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? Message-ID: <19981205150316.A18846@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199812042331.AAA02402@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from Sascha Schumann on Sat, Dec 05, 1998 at 01:02:23AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4856 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Sascha Schumann: > If you have an archive and your focus is on saving storage, go with it. > Its compression algorithm is much slower compared to gzip, but also > more effective. You see it yourself on the egcs site. Note though, that bzip2 uses a LOT more memory than gzip and by lot I mean in order of at least 5 MB for compression/decompression, generally more around 7 MB. Gzip is around .5 MB. > It would be interesting to know how much traffic a busy site like > ftp.cdrom.com or sunsite could save, if they would completely stick to > bzip2. On these machines, you don't want to enable automatic bzip2 compression :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 06:15:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12753 for freebsd-current-outgoing; Sat, 5 Dec 1998 06:15:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from out4.ibm.net (out4.ibm.net [165.87.194.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12748 for ; Sat, 5 Dec 1998 06:15:04 -0800 (PST) (envelope-from derm@ibm.net) Received: from ibm.net (slip139-92-4-213.mu.de.ibm.net [139.92.4.213]) by out4.ibm.net (8.8.5/8.6.9) with ESMTP id OAA85776 for ; Sat, 5 Dec 1998 14:15:02 GMT Message-ID: <36684107.E1AEA572@ibm.net> Date: Fri, 04 Dec 1998 21:07:35 +0100 From: Dermot McNally X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: de,fr,ga MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space References: <199812041829.TAA00997@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > I see things like: > > # KTRACE enables the system-call tracing facility ktrace(2). > # This adds 4 KB bloat to your kernel, and slightly increases > # the costs of each syscall. > options KTRACE #kernel tracing > > and > > # This provides support for System V shared memory. > # > options SYSVSHM > > in GENERIC. I'd also say you could do without things like procfs. > > In other words, maybe an INSTALL kernel is in order? (Ducks for cover) Alternatively (at the risk of really annoying those responsible), if the GENERIC kernel on the boot floppy is getting low on space, why not change things so that booting from CD starts a kernel with more drivers in it, while booting from floppy gives you a more minimal set? Obviously the floppy-based kernel would have to contain those drivers most commonly needed on older hardware that wouldn't support booting from CD... Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 06:18:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13096 for freebsd-current-outgoing; Sat, 5 Dec 1998 06:18:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13091 for ; Sat, 5 Dec 1998 06:18:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id GAA32427; Sat, 5 Dec 1998 06:18:13 -0800 (PST) To: Dermot McNally cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 21:07:35 +0100." <36684107.E1AEA572@ibm.net> Date: Sat, 05 Dec 1998 06:18:13 -0800 Message-ID: <32424.912867493@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > GENERIC kernel on the boot floppy is getting low on space, why not > change things so that booting from CD starts a kernel with more drivers > in it, while booting from floppy gives you a more minimal set? Because it doesn't work that way. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 08:40:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20668 for freebsd-current-outgoing; Sat, 5 Dec 1998 08:40:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20654 for ; Sat, 5 Dec 1998 08:40:21 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id LAA01134 for freebsd-current@freebsd.org; Sat, 5 Dec 1998 11:38:58 -0500 (EST) (envelope-from larry) Date: Sat, 5 Dec 1998 11:38:58 -0500 From: "Larry S. Marso" To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? Message-ID: <19981205113858.F887@marso.com> References: <199812042331.AAA02402@oranje.my.domain> <19981205150316.A18846@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i In-Reply-To: <19981205150316.A18846@keltia.freenix.fr>; from Ollivier Robert on Sat, Dec 05, 1998 at 03:03:16PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe, though, it would be a good idea to include bzip2 on the system fixit.flp image. Nowadays I'm dumping my system as bzip2'd images, and it would be helpful to have the executable available right there on the fixit floppy. Best regards -- Larry S. Marso larry@marso.com On Sat, Dec 05, 1998 at 03:03:16PM +0100, Ollivier Robert wrote: > > On these machines, you don't want to enable automatic bzip2 compression :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 11:02:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01751 for freebsd-current-outgoing; Sat, 5 Dec 1998 11:02:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01737 for ; Sat, 5 Dec 1998 11:02:22 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zmKgy-0000EK-00; Sat, 5 Dec 1998 16:36:24 +0000 To: van.woerkom@netcologne.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? References: <199812042331.AAA02402@oranje.my.domain> From: Dom Mitchell In-Reply-To: Marc van Woerkom's message of "Sat, 5 Dec 1998 00:31:23 +0100 (CET)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Sat, 05 Dec 1998 16:36:24 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Woerkom writes: > These files are only about 70% of their gzip counterparts - quite impressive. > > Julian Seward (jseward@acm.org), the author of this program claims extensive > tests on his web page > > http://www.muraroa.demon.co.uk I was under the impression that there were several patent issues with it. Not sure what though. It might be worth reading the docs closely. -- ``Bernstein versus Venema Celebrity Deathmatch: I see a great need.'' -- MR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 11:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01826 for freebsd-current-outgoing; Sat, 5 Dec 1998 11:03:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01819; Sat, 5 Dec 1998 11:03:07 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zmKbh-0000EA-00; Sat, 5 Dec 1998 16:30:57 +0000 To: "Gary Palmer" Cc: Doug White , current@FreeBSD.ORG Subject: Re: sysinstall question References: <8841.912814072@gjp.erols.com> From: Dom Mitchell In-Reply-To: "Gary Palmer"'s message of "Fri, 04 Dec 1998 18:27:52 -0500" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Sat, 05 Dec 1998 16:30:57 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gary Palmer" writes: > Doug White wrote in message ID > : > > > mountmsdosfs(): bad bpb > > > > The fixit floppy is a UNIX format disk image. mount_msdos shouldn't be > > touching it. > > This is a known issue. Jordan broke the fixit floppy for 3.0. My > guess is he's trying to use the same internal fn to mount the floppy > for doing a DOS floppy install as he is mounting the fixit > floppy. End result: sysinstall gets royally confused. He's aware of > the problem and promises to fix it. Sometime. :) Thanks. I really was wondering why it wasn't working... Could somebody update the errata.txt with that? I eventually got it working by dragging my 2.2.5 CDROM out of the dusty cupboard for use as a fixit CD... -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 11:55:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05806 for freebsd-current-outgoing; Sat, 5 Dec 1998 11:55:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05798 for ; Sat, 5 Dec 1998 11:55:21 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.1/8.9.1) id MAA78535 for current@FreeBSD.ORG; Sat, 5 Dec 1998 12:22:07 GMT (envelope-from aw1) Message-ID: <19981205122206.A77808@stade.co.uk> Date: Sat, 5 Dec 1998 12:22:06 +0000 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: Proposed addition to fetch(1) Reply-To: aw1@stade.co.uk References: <19981203200743.A861@cons.org> <19981203210935.A16110@klemm.gtn.com> <199812032055.MAA00648@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812032055.MAA00648@apollo.backplane.com>; from Matthew Dillon on Thu, Dec 03, 1998 at 12:55:26PM -0800 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 12:55:26PM -0800, Matthew Dillon wrote: > What would FETCH_MAX do? Generally speaking, when you type > 'make' in a port you want to make the port no matter how big > it is. Well, it might have stopped me fetching the rather large GimpUserManual-* files in an unattended session over a dialup line (8-) -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 12:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08482 for freebsd-current-outgoing; Sat, 5 Dec 1998 12:39:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08477 for ; Sat, 5 Dec 1998 12:39:11 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 6902 invoked by uid 100); 5 Dec 1998 20:43:24 -0000 Date: Sat, 5 Dec 1998 12:43:24 -0800 To: obrien@NUXI.com, van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? Message-ID: <19981205124324.A6892@top.worldcontrol.com> Mail-Followup-To: obrien@NUXI.com, van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG References: <199812042331.AAA02402@oranje.my.domain> <19981205020718.A12672@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.9i In-Reply-To: <19981205020718.A12672@nuxi.com>; from David O'Brien on Sat, Dec 05, 1998 at 02:07:18AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Today, while fetching egcs, I noticed that those folks use bzip2 for > compressing their snapshots: A problem I find with bzip2 is that it becomes unimaginably slow when compressing certain types of data. The slowness is documented. I've not found it a good general purpose compressor. However, I do use bzip2 extensively, while using gzip for those cases where bzip2 falls down. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 12:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09018 for freebsd-current-outgoing; Sat, 5 Dec 1998 12:45:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09002 for ; Sat, 5 Dec 1998 12:45:43 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id VAA25652; Sat, 5 Dec 1998 21:45:39 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA13287 (5.67b/IDA-1.5); Sat, 5 Dec 1998 21:23:30 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA22930; Sat, 5 Dec 1998 21:02:10 +0100 (CET) From: Wilko Bulte Message-Id: <199812052002.VAA22930@yedi.iaf.nl> Subject: Re: New drivers and install floppy space In-Reply-To: <2780.912830688@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 4, 98 08:04:48 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 5 Dec 1998 21:02:10 +0100 (CET) Cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jordan K. Hubbard wrote... > > Eventually with the growing hardware support we would be back at a > > 2 floppy boot set it seems. Not a problem in my opinion, but is there a > > general strategy or is it simply 'waiting for the wall'? > > We're already back there, to be perfectly honest. Even though it > wasn't actually documented as such (note to self: document this before > 3.0.1), in the 3.0-RELEASE we did indeed hit the wall quite firmly and > none of the following: > > Any EISA bus machine requiring an EISA peripheral for installation. > Any machine without an FPU. > IDE floppies. > Adaptec 1542. > Mitsumi CDROM. > Matsushita/Panasonic CDROM. > Sony (CDU-xx) CDROM. > Wangtek QIC tape. > Floppy tape. > > Can be used by boot.flp in actually installing the system. For this, > kern.flp is the only option. As time goes on I also expect this list > to grow (and be documented :) into pretty much anything we deem "not > mainstream enough" to go onto boot.flp, leaving the non-mainstream > folks with the abject misery of a 2-floppy installation (said with > tongue-seriously-in-cheek since this has been a requirement for just > about everyone else for some time now). I know that "mainstream" is > also a pretty darn difficult target to hit but we'll just have to do > our best using whatever metrics are available. I certainly want > *most* people to be able to continue using boot.flp for as long as > space permits. When a majority can no longer be thusly accommodated, > we'll just shrug and ditch it completely in favor of the 2(*)-floppy > solution. Hmm. I don't see too much problems in 2 floppies but then again I'm notorious for using out-of-date hardware anyway (as you have seen ;-) In my personal opinion a generic strategy with 2 floppies is prefered over a more or less obscure distinction in old/new hardware support with 2/1 floppy respectively. Your new support people will hate you for it.. ;-) Just to add some horror to this: I played around with the SCO Unixware 7 CD I got at SANE. Uses 2 boot floppies and 1 driver floppy (more or less optional, depends on your hardware). On the same machine it took 3+ hours to install compared to FreeBSD basic install in 30 minutes or so. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 13:37:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13812 for freebsd-current-outgoing; Sat, 5 Dec 1998 13:37:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13807 for ; Sat, 5 Dec 1998 13:37:36 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA10667; Sat, 5 Dec 1998 13:36:46 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma010665; Sat, 5 Dec 98 13:36:17 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA00413; Sat, 5 Dec 1998 13:36:17 -0800 (PST) From: Archie Cobbs Message-Id: <199812052136.NAA00413@bubba.whistle.com> Subject: Re: FreeBSD fsck updated In-Reply-To: <199812050913.UAA30164@godzilla.zeta.org.au> from Bruce Evans at "Dec 5, 98 08:13:55 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sat, 5 Dec 1998 13:36:17 -0800 (PST) Cc: archie@whistle.com, bde@zeta.org.au, current@FreeBSD.ORG, Don.Lewis@tsc.tdk.com, julian@whistle.com, mckusick@McKusick.COM X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >> Clearing fs_fmod here seems to be bogus. It is set (to 0 or 1) > > >We (Julian & me) are the ones who added this bit of code to clear > >the modified flag after seeing a panic caused by mounting a filesystem > >read-only that had this bit set (even though it was "clean", as > >the previous fsck didn't clear this bit). I forget exactly how it > >can happen, but it can (and did). > > It can't happen now. This was fixed without comment in the big soft > updates commit. > > [...] > > RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v > retrieving revision 1.75 > retrieving revision 1.76 > diff -c -r1.75 -r1.76 > *** ffs_vfsops.c 1998/03/07 21:36:36 1.75 > --- ffs_vfsops.c 1998/03/08 09:59:06 1.76 > *************** > *** 1200,1205 **** > --- 1239,1246 ---- > if (allerror) > return (allerror); > bp = getblk(mp->um_devvp, SBLOCK, (int)fs->fs_sbsize, 0, 0); > + fs->fs_fmod = 0; > + fs->fs_time = time.tv_sec; > bcopy((caddr_t)fs, bp->b_data, (u_int)fs->fs_sbsize); > /* Restore compatibility to old file systems. XXX */ > dfs = (struct fs *)bp->b_data; /* XXX */ > Ah, good.. that fixes the underlying problem rather than the symptom. I still think fs_fmod should be cleared by fsck (perhaps silently). Otherwise, it's still possible to get the (unneccesary) panic if the bit on the disk somehow got flipped (possibly by running an older version of FreeBSD). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 13:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14321 for freebsd-current-outgoing; Sat, 5 Dec 1998 13:39:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14309 for ; Sat, 5 Dec 1998 13:39:31 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA01524; Sat, 5 Dec 1998 14:39:28 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd001464; Sat Dec 5 14:39:22 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA27659; Sat, 5 Dec 1998 14:39:16 -0700 (MST) From: Terry Lambert Message-Id: <199812052139.OAA27659@usr05.primenet.com> Subject: Re: Thread fd locking and fork() To: info@highwind.com (HighWind Software Information) Date: Sat, 5 Dec 1998 21:39:16 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199812042207.RAA12304@highwind.com> from "HighWind Software Information" at Dec 4, 98 05:07:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Then don't explicitly call close after the exec, since the fork() > > wrapper in libc_r will Do The Right Thing(tm). > > What is the problem with calling close() after the exec()? That is a > 100% valid thing to do. Sure. But calling close() after the fork() but before the exec() isn't. This is because threads aren't expected to start processes. If threads are a good idea at all, then you'd be starting a thread; if they aren't, well, then why are you running threads in the first place? > Saying, "do this instead" is nice, but doesn't address the bug in > libc_r. > > Also, if you call fcntl() after the fork(), you will hang. The only > thing you can do is fcntl() all your descriptors before the fork(). Yep. Better if you do this right after openiong them, in fact, before giving the processor context away to another thread. > That is a bit crazy because you have to juggle everytime you want to > do a fork()/exec(). Calling fcntl() in the parent also introduces > other race conditions as other parts of the system might be calling > fork(). > > My patch seems to fix it. Your patch is actually not the right thing to do; it leaves an orphan reference around. Also, consider that after a fork you have a copy of the process, including the threads scheduler, etc.. It's quite possible that your thread will be involunarily context switched by receipt of a signal, and you will end up actually running two copies of the thread code until you context switch into the thread that wanted to exec. This is bad. Probably the correct thing to do is to use vfork(), so you don't have to contend with other threads. Unfortunately, some idiot broke vfork() (HINT: try to set up vacation with a response message, and see if you get the message). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 13:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15843 for freebsd-current-outgoing; Sat, 5 Dec 1998 13:59:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15838 for ; Sat, 5 Dec 1998 13:59:45 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA20782; Sat, 5 Dec 1998 17:03:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 5 Dec 1998 17:03:14 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: brian@worldcontrol.com cc: obrien@NUXI.com, van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? In-Reply-To: <19981205124324.A6892@top.worldcontrol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should also consider what the author has to say about the algorithm he uses. Supposedly he in not sure if his algorithm is copyrighted technology becuase of the mix of algorithms he uses. Maybe he revised his statement about it, but the closeness to certain other patened (sp?) algorithms might cause trouble later on. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Sat, 5 Dec 1998 brian@worldcontrol.com wrote: > > Today, while fetching egcs, I noticed that those folks use bzip2 for > > compressing their snapshots: > > A problem I find with bzip2 is that it becomes unimaginably slow when > compressing certain types of data. The slowness is documented. > > I've not found it a good general purpose compressor. However, I > do use bzip2 extensively, while using gzip for those cases where > bzip2 falls down. > > -- > Brian Litzinger > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:00:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16133 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:00:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16128 for ; Sat, 5 Dec 1998 14:00:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA19805 for ; Sat, 5 Dec 1998 14:00:26 -0800 Date: Sat, 5 Dec 1998 14:00:26 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: sys/compile directories... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm, now that we have alpha as well as i386 regularly compiling along, would it be conceivable to have the compile directory become either sys/compile// or have it as part of sys//compile (I probably prefer the latter- but in either case, I use the same sys tree for developing both, and two different GENERIC's are a problem..) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:06:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16797 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:06:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16784 for ; Sat, 5 Dec 1998 14:06:47 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id JAA26976; Sun, 6 Dec 1998 09:15:53 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812052215.JAA26976@cimlogic.com.au> Subject: Re: sys/compile directories... In-Reply-To: from Matthew Jacob at "Dec 5, 98 02:00:26 pm" To: mjacob@feral.com Date: Sun, 6 Dec 1998 09:15:52 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > Umm, now that we have alpha as well as i386 regularly compiling along, > would it be conceivable to have the compile directory become either > sys/compile// or have it as part of sys//compile > (I probably prefer the latter- but in either case, I use the same sys tree > for developing both, and two different GENERIC's are a problem..) I've already asked for this and received less that favourable responses. Bruce wanted to have the build use an obj tree. i386 people wanted not change (POLA). We _do_ need to resolve this issue. It's annoying. With the possibility of support for more architectures coming, it will only get worse. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17703 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:16:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17698 for ; Sat, 5 Dec 1998 14:16:57 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA03568; Sat, 5 Dec 1998 15:16:55 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd003547; Sat Dec 5 15:16:53 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA28951; Sat, 5 Dec 1998 15:16:45 -0700 (MST) From: Terry Lambert Message-Id: <199812052216.PAA28951@usr05.primenet.com> Subject: Re: New drivers and install floppy space To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sat, 5 Dec 1998 22:16:44 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199812050528.AAA13608@skynet.ctr.columbia.edu> from "Bill Paul" at Dec 5, 98 00:28:05 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The alternative will be to have a single minimal kernel and mfsroot > > floppy, and another floppy with a pile of KLD modules on it. This > > won't be feasible until the PCI code moves to the new bus architecture > > (soon we hope). > > I would like to see this too, but I would also like to see the > ability to provide 3rd party drivers during the install. [ ... ] > This would allow hardware vendors to provide drivers that can > be loaded and used during installation of FreeBSD, and it would > make it easier for users to load FreeBSD using newly written > drivers (that is, written by us) without having to wait for the > next release or build a custom installation floppy. This is the partial culmination of the benefits of a modular kernel. I would suggest that architectural care be given to allowing: o use of DOS format floppies to conatin the driver o specification of the FS path to the driver directory o selection of a default "/freebsd/" directory o a naming format that can return all drivers, but avoid other (informational, etc.) files, such as loading everything matching "*.[0-9][0-9][0-9]" in the driver directory o support for using drivers from multiple floppies, one per device o a mechanism for dumping drivers from the kernel after installation so that they need not be installed twice: once to boot, once to install; this probably implies driver data areas be mapped copy-on-write to maintain the data image integrity to allow it to be written back out This would allow the FreeBSD project to provide binary drivers back to vendors for inclusion on their distribution media, and in general, help raise FreeBSD visibility considerably. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19453 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:40:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19448 for ; Sat, 5 Dec 1998 14:40:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id OAA20930; Sat, 5 Dec 1998 14:40:40 -0800 (PST) (envelope-from obrien) Message-ID: <19981205144040.A20818@nuxi.com> Date: Sat, 5 Dec 1998 14:40:40 -0800 From: "David O'Brien" To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? Reply-To: obrien@NUXI.com References: <19981205124324.A6892@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Sat, Dec 05, 1998 at 05:03:14PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 05, 1998 at 05:03:14PM -0500, Alfred Perlstein wrote: > You should also consider what the author has to say about the algorithm he > uses. > > Supposedly he in not sure if his algorithm is copyrighted technology > becuase of the mix of algorithms he uses. He says this because he is [overly] paranoid of patents. He was forced to abandon the original `bzip' because he knew he was on the edge of violating some US patents. Anyway, he doesn't say he "isn't sure". You are stretching a little. To quote: PATENTS: To the best of my knowledge, bzip2 does not use any patented algorithms. However, I do not have the resources available to carry out a full patent search. Therefore I cannot give any guarantee of the above statement. End of legalities. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:44:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19771 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:44:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19757 for ; Sat, 5 Dec 1998 14:44:46 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA20829; Sat, 5 Dec 1998 17:48:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 5 Dec 1998 17:48:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "David O'Brien" cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 - worthy successor to gzip? In-Reply-To: <19981205144040.A20818@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Dec 1998, David O'Brien wrote: > On Sat, Dec 05, 1998 at 05:03:14PM -0500, Alfred Perlstein wrote: > > You should also consider what the author has to say about the algorithm he > > uses. > > > > Supposedly he in not sure if his algorithm is copyrighted technology > > becuase of the mix of algorithms he uses. > > He says this because he is [overly] paranoid of patents. > He was forced to abandon the original `bzip' because he knew he was on > the edge of violating some US patents. > > Anyway, he doesn't say he "isn't sure". You are stretching a little. To > quote: > > PATENTS: > > To the best of my knowledge, bzip2 does not use any patented > algorithms. However, I do not have the resources available to > carry out a full patent search. Therefore I cannot give any > guarantee of the above statement. > > End of legalities. bzip1 was really bad in that aspect, but that is NOT the tune he was singing to several months back when i checked about bzip2, it was much more on the shady side according to the author. maybe he researched a bit more. -Alfred > > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20148 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:48:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20143 for ; Sat, 5 Dec 1998 14:48:42 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.89]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3C81; Sat, 5 Dec 1998 23:48:39 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812052215.JAA26976@cimlogic.com.au> Date: Sat, 05 Dec 1998 23:54:06 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: John Birrell Subject: Re: sys/compile directories... Cc: freebsd-current@FreeBSD.ORG, mjacob@feral.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Dec-98 John Birrell wrote: > Matthew Jacob wrote: >> >> Umm, now that we have alpha as well as i386 regularly compiling along, >> would it be conceivable to have the compile directory become either >> sys/compile// or have it as part of sys//compile >> (I probably prefer the latter- but in either case, I use the same sys tree >> for developing both, and two different GENERIC's are a problem..) > > I've already asked for this and received less that favourable responses. > Bruce wanted to have the build use an obj tree. i386 people wanted > not change (POLA). We _do_ need to resolve this issue. It's annoying. > With the possibility of support for more architectures coming, it will > only get worse. IMHO it's better to use sys/ARCH/compile to denote the architecture it's under (after all we make our kernel specifications in sys/ARCH/conf, so ../compile would seem logical, at least in my eyes) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 14:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20456 for freebsd-current-outgoing; Sat, 5 Dec 1998 14:51:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20451 for ; Sat, 5 Dec 1998 14:51:13 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA11152; Sat, 5 Dec 1998 14:50:17 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma011147; Sat, 5 Dec 98 14:49:47 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA00820; Sat, 5 Dec 1998 14:49:47 -0800 (PST) From: Archie Cobbs Message-Id: <199812052249.OAA00820@bubba.whistle.com> Subject: Re: bzip2 - worthy successor to gzip? In-Reply-To: from Dom Mitchell at "Dec 5, 98 04:36:24 pm" To: dom@myrddin.demon.co.uk (Dom Mitchell) Date: Sat, 5 Dec 1998 14:49:47 -0800 (PST) Cc: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell writes: > Marc van Woerkom writes: > > These files are only about 70% of their gzip counterparts - quite impressiv > > > > Julian Seward (jseward@acm.org), the author of this program claims extensiv > > tests on his web page > > > > http://www.muraroa.demon.co.uk > > I was under the impression that there were several patent issues with > it. Not sure what though. It might be worth reading the docs closely. >From the web site: "...it's open-source (BSD-style license), and, as far as I know, patent-free. (To the best of my knowledge. I can't afford to do a full patent search, so I can't guarantee this. Caveat emptor). So you can use it for whatever you like. Naturally, the source code is part of the distribution." -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 15:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22692 for freebsd-current-outgoing; Sat, 5 Dec 1998 15:15:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22667 for ; Sat, 5 Dec 1998 15:15:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id AAA19376; Sun, 6 Dec 1998 00:15:40 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA21853 (5.67b/IDA-1.5); Sun, 6 Dec 1998 00:07:29 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA24795; Sat, 5 Dec 1998 23:23:47 +0100 (CET) From: Wilko Bulte Message-Id: <199812052223.XAA24795@yedi.iaf.nl> Subject: Re: sys/compile directories... In-Reply-To: <199812052215.JAA26976@cimlogic.com.au> from John Birrell at "Dec 6, 98 09:15:52 am" To: jb@cimlogic.com.au (John Birrell) Date: Sat, 5 Dec 1998 23:23:47 +0100 (CET) Cc: mjacob@feral.com, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As John Birrell wrote... > Matthew Jacob wrote: > > > > Umm, now that we have alpha as well as i386 regularly compiling along, > > would it be conceivable to have the compile directory become either > > sys/compile// or have it as part of sys//compile > > (I probably prefer the latter- but in either case, I use the same sys tree > > for developing both, and two different GENERIC's are a problem..) > > I've already asked for this and received less that favourable responses. > Bruce wanted to have the build use an obj tree. i386 people wanted > not change (POLA). We _do_ need to resolve this issue. It's annoying. It sure *(*&*& is. It just bit me 2 minutes ago.. Not changing it is IMHO not a sensible solution. > With the possibility of support for more architectures coming, it will > only get worse. Very much so yes. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 16:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01331 for freebsd-current-outgoing; Sat, 5 Dec 1998 16:34:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jcarter.cais.com (jcarter.cais.com [205.252.8.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01322 for ; Sat, 5 Dec 1998 16:34:32 -0800 (PST) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] (saturn.falcon.com [192.168.1.10]) by jcarter.cais.com (8.9.1a/8.8.5) with ESMTP id TAA16092 for ; Sat, 5 Dec 1998 19:15:09 -0500 (EST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 5 Dec 1998 19:41:01 -0500 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: CAM vs traditional devices Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I oopsed and posted to -scsi. Hopefully this belongs here. I'm lagging -current by a month or so but I have been running with CAM now for a while. I've noticed that the kernel probes the disks as daXX. I therefore converted all of my fstab entries to use daXy where y is the partition letter [a ~ g] except for the entry for root. The kernel still thinks the root device is "sd0s1a". Why is that? Also how come none of the "da" devices have trailing partition letters? eg. there is "da0s1" and "da0a" but no "da0s1a". I am simply too far behind? The /dev/MAKEDEV script doesn't build them. Hmm, I just noticed that the 1st stage boot loader called for (sd0,1,a) Maybe that's why the kernel is confused? I need to install-boot again, right? Again this may be an artifact of not tracking -current closely, but doesn't anybody boot their boxes where say /usr is NFS mounted? /etc/rc doesn't start the network till extremely late in the game - practically when it's done. Other BSD's start the network immediately after / is marked RW. They then explicitly mount /usr and /var in case the automatic method doesn't happen to pick the right order. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 17:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05775 for freebsd-current-outgoing; Sat, 5 Dec 1998 17:37:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05770 for ; Sat, 5 Dec 1998 17:37:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA14538 for ; Sat, 5 Dec 1998 17:37:26 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA13511; Sat, 5 Dec 1998 17:37:25 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 5 Dec 1998 17:37:25 -0800 (PST) Message-Id: <199812060137.RAA13511@vashon.polstra.com> To: current@FreeBSD.ORG Subject: Re: ELF documentation Newsgroups: polstra.freebsd.current In-Reply-To: <199812031020.MAA15238@ceia.nordier.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can pick up a copy of the ELF specification, as part of the Tool > Interface Standards, at > > ftp://ftp.intel.com/pub/tis/elf11g.zip Also, BSDI's on-line man pages for ELF aren't bad. . John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 17:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06283 for freebsd-current-outgoing; Sat, 5 Dec 1998 17:42:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06278 for ; Sat, 5 Dec 1998 17:42:42 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA12060; Sat, 5 Dec 1998 17:41:21 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma012058; Sat, 5 Dec 98 17:40:58 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA01908; Sat, 5 Dec 1998 17:40:55 -0800 (PST) From: Archie Cobbs Message-Id: <199812060140.RAA01908@bubba.whistle.com> Subject: Re: sys/compile directories... In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 5, 98 11:54:06 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sat, 5 Dec 1998 17:40:55 -0800 (PST) Cc: jb@cimlogic.com.au, freebsd-current@FreeBSD.ORG, mjacob@feral.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > >> Umm, now that we have alpha as well as i386 regularly compiling along, > >> would it be conceivable to have the compile directory become either > >> sys/compile// or have it as part of sys//compile > >> (I probably prefer the latter- but in either case, I use the same sys tree > >> for developing both, and two different GENERIC's are a problem..) > > > > I've already asked for this and received less that favourable responses. > > Bruce wanted to have the build use an obj tree. i386 people wanted > > not change (POLA). We _do_ need to resolve this issue. It's annoying. > > With the possibility of support for more architectures coming, it will > > only get worse. > > IMHO it's better to use sys/ARCH/compile to denote the architecture it's under > (after all we make our kernel specifications in sys/ARCH/conf, so ../compile > would seem logical, at least in my eyes) FWIW, I vote for sys/compile//. What about this idea.. "config -d directory ..." where you specify the directory you want to compile in. config(8) automatically adjusts all the filenames, etc. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 17:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06338 for freebsd-current-outgoing; Sat, 5 Dec 1998 17:43:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06333 for ; Sat, 5 Dec 1998 17:43:14 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA14561; Sat, 5 Dec 1998 17:43:11 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA13529; Sat, 5 Dec 1998 17:43:10 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 5 Dec 1998 17:43:10 -0800 (PST) Message-Id: <199812060143.RAA13529@vashon.polstra.com> To: jb@cimlogic.com.au Subject: Re: SYSINIT defs in kernel.h Newsgroups: polstra.freebsd.current In-Reply-To: <199812030838.TAA12886@cimlogic.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812030838.TAA12886@cimlogic.com.au>, John Birrell wrote: > > Does anyone object to me adding `__attribute__ ((unused))' to the > SYSINIT etc definitions in sys/sys/kernel.h to stop gcc generating > an unused variable warning? It sounds like a fine idea to me! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 18:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09907 for freebsd-current-outgoing; Sat, 5 Dec 1998 18:31:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09902 for ; Sat, 5 Dec 1998 18:31:16 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id DAA07500; Sun, 6 Dec 1998 03:31:09 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA09571; Sun, 6 Dec 1998 03:31:09 +0100 (MET) Message-ID: <19981206033108.E8663@follo.net> Date: Sun, 6 Dec 1998 03:31:08 +0100 From: Eivind Eklund To: Archie Cobbs , Jeroen Ruigrok/Asmodai Cc: jb@cimlogic.com.au, freebsd-current@FreeBSD.ORG, mjacob@feral.com Subject: Re: sys/compile directories... References: <199812060140.RAA01908@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812060140.RAA01908@bubba.whistle.com>; from Archie Cobbs on Sat, Dec 05, 1998 at 05:40:55PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 05, 1998 at 05:40:55PM -0800, Archie Cobbs wrote: > Jeroen Ruigrok/Asmodai writes: > > >> Umm, now that we have alpha as well as i386 regularly compiling along, > > >> would it be conceivable to have the compile directory become either > > >> sys/compile// or have it as part of sys//compile > > >> (I probably prefer the latter- but in either case, I use the same sys tree > > >> for developing both, and two different GENERIC's are a problem..) > > > > > > I've already asked for this and received less that favourable responses. > > > Bruce wanted to have the build use an obj tree. i386 people wanted > > > not change (POLA). We _do_ need to resolve this issue. It's annoying. > > > With the possibility of support for more architectures coming, it will > > > only get worse. > > > > IMHO it's better to use sys/ARCH/compile to denote the architecture it's under > > (after all we make our kernel specifications in sys/ARCH/conf, so ../compile > > would seem logical, at least in my eyes) > > FWIW, I vote for sys/compile//. > > What about this idea.. "config -d directory ..." where you specify > the directory you want to compile in. config(8) automatically > adjusts all the filenames, etc. http://www.freebsd.org/~eivind/config-objdir-patch2 IIRC. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 18:37:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10427 for freebsd-current-outgoing; Sat, 5 Dec 1998 18:37:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10422 for ; Sat, 5 Dec 1998 18:37:05 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA12280; Sat, 5 Dec 1998 18:35:52 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma012278; Sat, 5 Dec 98 18:35:43 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA02099; Sat, 5 Dec 1998 18:35:43 -0800 (PST) From: Archie Cobbs Message-Id: <199812060235.SAA02099@bubba.whistle.com> Subject: Re: sys/compile directories... In-Reply-To: <19981206033108.E8663@follo.net> from Eivind Eklund at "Dec 6, 98 03:31:08 am" To: eivind@yes.no (Eivind Eklund) Date: Sat, 5 Dec 1998 18:35:42 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > > What about this idea.. "config -d directory ..." where you specify > > the directory you want to compile in. config(8) automatically > > adjusts all the filenames, etc. > > http://www.freebsd.org/~eivind/config-objdir-patch2 I think for maximum flexibility you'd perhaps need a "-p path" (default: "../..") for specifying the pathname to the top of the /sys directory, since config builds the Makefile. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 18:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11083 for freebsd-current-outgoing; Sat, 5 Dec 1998 18:47:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11077 for ; Sat, 5 Dec 1998 18:47:05 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id DAA07592; Sun, 6 Dec 1998 03:47:03 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA09638; Sun, 6 Dec 1998 03:47:02 +0100 (MET) Message-ID: <19981206034702.F8663@follo.net> Date: Sun, 6 Dec 1998 03:47:02 +0100 From: Eivind Eklund To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: sys/compile directories... References: <19981206033108.E8663@follo.net> <199812060235.SAA02099@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812060235.SAA02099@bubba.whistle.com>; from Archie Cobbs on Sat, Dec 05, 1998 at 06:35:42PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 05, 1998 at 06:35:42PM -0800, Archie Cobbs wrote: > Eivind Eklund writes: > > > What about this idea.. "config -d directory ..." where you specify > > > the directory you want to compile in. config(8) automatically > > > adjusts all the filenames, etc. > > > > http://www.freebsd.org/~eivind/config-objdir-patch2 > > I think for maximum flexibility you'd perhaps need a "-p path" > (default: "../..") for specifying the pathname to the top of the > /sys directory, since config builds the Makefile. Then you'll need to modify Makefile.i386 and Makefile.alpha to not set S, too. Would probably be a good change. Unfortunately, I don't know where my patches to handle all of this went - I'll try to see if the guy I made 'em for still have 'em. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 19:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14181 for freebsd-current-outgoing; Sat, 5 Dec 1998 19:43:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14176 for ; Sat, 5 Dec 1998 19:43:28 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.1/8.9.1) with ESMTP id VAA03006 for ; Sat, 5 Dec 1998 21:43:26 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199812060343.VAA03006@friley-184-92.res.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Where is pthread_cancel()? Date: Sat, 05 Dec 1998 21:43:25 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm attempting to port a multithreaded library from IRIX to FreeBSD-current, and I was wondering why there is no pthread_cancel() in libc_r. I am not up on the full Pthreads Draft 10 standard, but I thought pthread_cancel() was part of it. Am I mistaken? Should I just use pthread_kill() and not worry about this? Thanks. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 95E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 19:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14621 for freebsd-current-outgoing; Sat, 5 Dec 1998 19:52:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14611 for ; Sat, 5 Dec 1998 19:52:24 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id PAA27848; Sun, 6 Dec 1998 15:01:35 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812060401.PAA27848@cimlogic.com.au> Subject: Re: Where is pthread_cancel()? In-Reply-To: <199812060343.VAA03006@friley-184-92.res.iastate.edu> from Patrick Hartling at "Dec 5, 98 09:43:25 pm" To: mystify@friley-184-92.res.iastate.edu (Patrick Hartling) Date: Sun, 6 Dec 1998 15:01:35 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Hartling wrote: > I'm attempting to port a multithreaded library from IRIX to FreeBSD-current, > and I was wondering why there is no pthread_cancel() in libc_r. I am not up > on the full Pthreads Draft 10 standard, but I thought pthread_cancel() was > part of it. Am I mistaken? Should I just use pthread_kill() and not worry > about this? Thanks. I checked the standard after the recent discussion about pthread_cancel() and it's not optional, so the fact that it's not in libc_r is a bug. I think the result of the discussion was that someone would be working on it soon (having done some work already). pthread_kill() isn't really a substitute because that just dispatches a signal to the thread. Check the mail archives for a more detailed answer. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 20:05:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15508 for freebsd-current-outgoing; Sat, 5 Dec 1998 20:05:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15503 for ; Sat, 5 Dec 1998 20:05:01 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.1/8.9.1) with ESMTP id WAA05227; Sat, 5 Dec 1998 22:04:47 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199812060404.WAA05227@friley-184-92.res.iastate.edu> To: John Birrell cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is pthread_cancel()? In-reply-to: Message from John Birrell of "Sun, 06 Dec 1998 15:01:35 +1100." <199812060401.PAA27848@cimlogic.com.au> Date: Sat, 05 Dec 1998 22:04:46 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: } Patrick Hartling wrote: } > I'm attempting to port a multithreaded library from IRIX to FreeBSD-current, } > and I was wondering why there is no pthread_cancel() in libc_r. I am not up } > on the full Pthreads Draft 10 standard, but I thought pthread_cancel() was } > part of it. Am I mistaken? Should I just use pthread_kill() and not worry } > about this? Thanks. } } I checked the standard after the recent discussion about pthread_cancel() and } it's not optional, so the fact that it's not in libc_r is a bug. I think } the result of the discussion was that someone would be working on it } soon (having done some work already). pthread_kill() isn't really a } substitute because that just dispatches a signal to the thread. I didn't think so, and it's not being used that way in the library in question. I was thinking that it could just be a temporary substitute if in fact the absence of pthread_cancel() was a bug. } Check the mail archives for a more detailed answer. Okay, I will do that. Thanks a bunch. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 95E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 21:53:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22826 for freebsd-current-outgoing; Sat, 5 Dec 1998 21:53:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22668 for ; Sat, 5 Dec 1998 21:53:45 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id AAA16233; Sun, 6 Dec 1998 00:53:39 -0500 (EST) Date: Sun, 6 Dec 1998 00:53:39 -0500 (EST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: Something fishy with telnetd (non-zero initialized static?) In-Reply-To: <199812050239.VAA02555@bb01f39.unx.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Dec 1998, John W. DeBoskey wrote: > The following is from a 3.0-19981202-SNAP system. Yes, I've noticed the same with some previous SNAPs before 3.0-REL. Upon upgrading to 3.0-REL this behavior went away. -- Mike Hoskins System/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:22:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26767 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:22:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26760 for ; Sat, 5 Dec 1998 23:22:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA02870; Sat, 5 Dec 1998 23:20:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060720.XAA02870@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 02:19:14 PST." <19981205021914.C12672@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 23:20:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When a majority can no longer be thusly accommodated, we'll just shrug > > and ditch it completely in favor of the 2(*)-floppy solution. > > It is not that bad. I'm doing more and more boot off the CDROM installs. > I assume sysinstall + boot kernel can be quite large there. > Is the boot kernel there a full GENERIC kernel? No. The way that bootable CDROMs work is that the BIOS pretends that a 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy disk. I wouldn't mind finding the asshole responsible for this fiasco and doing something traumatic to their lower digestive tract with a petrol-powered Weed Eater. The only ways out of this are: - mandate a floppy in addition to the CDROM (sucks) - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR at least) Both of these are painful. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:25:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27101 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:25:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27088 for ; Sat, 5 Dec 1998 23:25:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA02634; Sat, 5 Dec 1998 22:53:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060653.WAA02634@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 00:28:05 EST." <199812050528.AAA13608@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 22:53:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of all the gin joints in all the towns in all the world, Mike Smith had > to walk into mine and say: > > > At the moment, the current exploratory strategy is the split kern.flp/ > > mfsroot.gz arrangement. It's probably going to make more sense just to > > have them as two floppy images for distribution purposes. > > > > The alternative will be to have a single minimal kernel and mfsroot > > floppy, and another floppy with a pile of KLD modules on it. This > > won't be feasible until the PCI code moves to the new bus architecture > > (soon we hope). > > I would like to see this too, but I would also like to see the > ability to provide 3rd party drivers during the install. This is core functionality for KLD and the new bootloader. The loader does (will do) a PnP scan before booting the kernel, and it will/can be set up to prompt the user for driver media at that point. > Not that > I really want to encourage people to copy the behavior of Windoze, > but it would make life easier for a lot of people (mainly us) to > be able to provide FreeBSD drivers in object code form on a floppy > diskette, and be able to specify 'install unlisted driver->have disk' > and have it show a list of drivers present on the diskette and > let the user load the ones he/she wants. In 99% of the cases, we don't want to ask the user to select the "right driver", we want to know that the media contains drivers for the given set of PnP ID's, and install them as required. Obviously user intervention is still going to be required for non-PnP ISA devices. > This would mean having an installation utility that can parse > some kind of description file that provides information about > the type of driver, its name, and special loading instructions. > We'd also need to provide a kit or sample Makefiles/scripts for > generating driver object files and the description files. Much of this is already implemeted; see the pnp* files in sys/boot/common and the 'pnpscan' command. What's still missing is support for catalog files and multiple driver media, but that's not much work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:26:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27247 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:26:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27240 for ; Sat, 5 Dec 1998 23:26:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA02653; Sat, 5 Dec 1998 22:55:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060655.WAA02653@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Mike Smith , Wilko Bulte , wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Fri, 04 Dec 1998 20:17:09 PST." <2949.912831429@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 22:55:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > At the moment, the current exploratory strategy is the split kern.flp/ > > mfsroot.gz arrangement. It's probably going to make more sense just to > > have them as two floppy images for distribution purposes. > > If the mfsroot image is a UFS filesystem containing an mfsroot.gz > file, I'm all for it. I just don't want to lose our newfound ability > to say: "There's really nothing special about building MicroFreeBSD > systems for installation or any other purpose anymore - just take any > kernel with MFS_ROOT turned on and any gzip'd UFS filesystem for its > root and Bob's yer uncle!" It shouldn't really require MFS_ROOT turned on (the foo_ROOT options are IMO bogus); it should always be checking for an mfs_root type object. But no, the mfsroot image should indeed be either a UFS filesystem or a FAT filesystem (the latter would make adding extra drivers to the disk easier). > Hmmmmm. For that matter, we could make sure that the mfsroot was also > a bootable floppy image with a /boot/boot.4th file on it which said: > > : yell 7 emit ." NO, BOOT THE OTHER FLOPPY, YOU KNOB!" cr ; > > yell > key drop > reset > > Or something to that effect. :-) That's an excellent argument for making it a UFS floppy, yes. Either that, or ask Robert for a bootsector that says the same thing... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28287 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:40:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from susanna.deranged.schneider.org (susanna.deranged.schneider.org [207.126.69.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28267 for ; Sat, 5 Dec 1998 23:40:36 -0800 (PST) (envelope-from rik@deranged.schneider.org) Received: from localhost (rik@localhost) by susanna.deranged.schneider.org (8.9.1/8.9.1) with ESMTP id XAA13782; Sat, 5 Dec 1998 23:38:37 -0800 (PST) (envelope-from rik@deranged.schneider.org) X-Authentication-Warning: susanna.deranged.schneider.org: rik owned process doing -bs Date: Sat, 5 Dec 1998 23:38:34 -0800 (PST) From: Rik Schneider To: Mike Smith cc: obrien@NUXI.com, "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-Reply-To: <199812060720.XAA02870@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate to disgree, but, the boot image for an El Torito disk can be 2.88M. It must be exactly the same size as a 2.88M floppy and wil work only with bioses that support 2.88M floppies. This limitation is not that major as most current BIOSes support the 2.8 format. -- Rik Schneider Unix Systems Administrator Net Asset LLC 1315 Van Ness Ave Suite 103 Fresno CA 93721 (559) 490-4000 / rik@deranged.schneider.org | rik@netasset.com | wookie@smartasset.com \ On Sat, 5 Dec 1998, Mike Smith wrote: > > > When a majority can no longer be thusly accommodated, we'll just shrug > > > and ditch it completely in favor of the 2(*)-floppy solution. > > > > It is not that bad. I'm doing more and more boot off the CDROM installs. > > I assume sysinstall + boot kernel can be quite large there. > > Is the boot kernel there a full GENERIC kernel? > > No. The way that bootable CDROMs work is that the BIOS pretends that a > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > disk. > > I wouldn't mind finding the asshole responsible for this fiasco and > doing something traumatic to their lower digestive tract with a > petrol-powered Weed Eater. > > The only ways out of this are: > > - mandate a floppy in addition to the CDROM (sucks) > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > at least) > > Both of these are painful. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:42:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28636 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:42:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28631 for ; Sat, 5 Dec 1998 23:42:25 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA22484; Sat, 5 Dec 1998 23:42:09 -0800 (PST) (envelope-from obrien) Message-ID: <19981205234209.U10572@nuxi.com> Date: Sat, 5 Dec 1998 23:42:09 -0800 From: "David O'Brien" To: Rik Schneider , Mike Smith Cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space Reply-To: obrien@NUXI.com References: <199812060720.XAA02870@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Rik Schneider on Sat, Dec 05, 1998 at 11:38:34PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This limitation is not that major as most current BIOSes support the > 2.8 format. Current maybe.. but I think you underestimate the number of older machines people install FreeBSD on. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:43:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28703 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:43:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28691 for ; Sat, 5 Dec 1998 23:43:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA03107; Sat, 5 Dec 1998 23:41:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060741.XAA03107@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: wpaul@skynet.ctr.columbia.edu (Bill Paul), current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 22:16:44 GMT." <199812052216.PAA28951@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 23:41:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the partial culmination of the benefits of a modular kernel. > > I would suggest that architectural care be given to allowing: Thanks for enumerating the entire list here; I'll just summarise the state of our compliance so far - most of these have already been thought of. > o use of DOS format floppies to conatin the driver Done. We support DOS and UFS floppies, as well as NFS, TFTP and iso9660 filesystems. > o specification of the FS path to the driver directory Root path to information file - I think we should be able to do this, although my preference would actually be to require a 'bsdinfo' file at the top level to make this as automated as possible. > o selection of a default "/freebsd/" directory ... but I like this better. > o a naming format that can return all drivers, but > avoid other (informational, etc.) files, such as > loading everything matching "*.[0-9][0-9][0-9]" in > the driver directory *.ko should do it, although the information that identifies a file as a driver object should be in the metaconfig file. > o support for using drivers from multiple floppies, > one per device Arbitrary number of drivers on an arbitrary number of media. I'm open to suggestions that would allow aggregation without editing a single file. One that occurs is to use the approach that the Lan Manager folks did and say that *.BSD at the top level of the media are directories containing FreeBSD drivers, one per directory. > o a mechanism for dumping drivers from the kernel after > installation so that they need not be installed twice: > once to boot, once to install; this probably implies > driver data areas be mapped copy-on-write to maintain > the data image integrity to allow it to be written > back out This is actually fairly tough, as the entire ELF object is not loaded in the first place. My preference is simply to track the driver(s) that are loaded, and request the use re-provide the media from which the driver was read when it comes time to copy it. > This would allow the FreeBSD project to provide binary drivers > back to vendors for inclusion on their distribution media, and > in general, help raise FreeBSD visibility considerably. Sounds close to our goalset. Feel like writing any of this code, or is that outside your domain of interest? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29026 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:48:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29021 for ; Sat, 5 Dec 1998 23:48:40 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id CAA19418; Sun, 6 Dec 1998 02:48:33 -0500 (EST) Date: Sun, 6 Dec 1998 02:48:33 -0500 (EST) From: jack To: "David O'Brien" cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-Reply-To: <19981205234209.U10572@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Dec 1998, David O'Brien wrote: > > This limitation is not that major as most current BIOSes support the > > 2.8 format. > > Current maybe.. but I think you underestimate the number of older > machines people install FreeBSD on. But those `older machines' tend not to support booting from CD. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:52:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29374 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:52:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29366 for ; Sat, 5 Dec 1998 23:52:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA03177; Sat, 5 Dec 1998 23:50:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060750.XAA03177@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Rik Schneider cc: current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sat, 05 Dec 1998 23:38:34 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 23:50:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hate to disgree, but, the boot image for an El Torito disk can be 2.88M. > It must be exactly the same size as a 2.88M floppy and wil work only with > bioses that support 2.88M floppies. This limitation is not that major as > most current BIOSes support the 2.8 format. I'm quite aware of this (and perhaps slightly insulted that you might think I wasn't). However it's imporant for you to consider the downsides that you mention, as well as those you don't: - We loose on any system that doesn't support 2.88M floppies. - We loose on any system that doesn't support 2.88M El Torito images (want to bet how many don't work even with 1.44's? it can only be worse with 2.88) Until I've had a chance to test this and perhaps field a -SNAP release with a 2.88MB boot image to get some wider testing, I'm not at all keen on the idea of making such a change. I agree that it's the closest to "right" way to do it though, yes. > -- > > Rik Schneider > Unix Systems Administrator > Net Asset LLC > 1315 Van Ness Ave > Suite 103 > Fresno CA 93721 > (559) 490-4000 > > / rik@deranged.schneider.org | rik@netasset.com | wookie@smartasset.com \ > > On Sat, 5 Dec 1998, Mike Smith wrote: > > > > > When a majority can no longer be thusly accommodated, we'll just shrug > > > > and ditch it completely in favor of the 2(*)-floppy solution. > > > > > > It is not that bad. I'm doing more and more boot off the CDROM installs. > > > I assume sysinstall + boot kernel can be quite large there. > > > Is the boot kernel there a full GENERIC kernel? > > > > No. The way that bootable CDROMs work is that the BIOS pretends that a > > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > > disk. > > > > I wouldn't mind finding the asshole responsible for this fiasco and > > doing something traumatic to their lower digestive tract with a > > petrol-powered Weed Eater. > > > > The only ways out of this are: > > > > - mandate a floppy in addition to the CDROM (sucks) > > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > > at least) > > > > Both of these are painful. > > > > -- > > \\ Sometimes you're ahead, \\ Mike Smith > > \\ sometimes you're behind. \\ mike@smith.net.au > > \\ The race is long, and in the \\ msmith@freebsd.org > > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 5 23:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29494 for freebsd-current-outgoing; Sat, 5 Dec 1998 23:54:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29489 for ; Sat, 5 Dec 1998 23:54:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA03195; Sat, 5 Dec 1998 23:52:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060752.XAA03195@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jack cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sun, 06 Dec 1998 02:48:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Dec 1998 23:52:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 5 Dec 1998, David O'Brien wrote: > > > > This limitation is not that major as most current BIOSes support the > > > 2.8 format. > > > > Current maybe.. but I think you underestimate the number of older > > machines people install FreeBSD on. > > But those `older machines' tend not to support booting from CD. Try many older PCI motherboards with PCI SCSI controllers (a very common scenario). The real concern is actually bugs in the bootable CDROM support; there are plenty of BIOS revisions out there that don't do it properly with 1.44MB images. The situation with 2.88MB ones is likely to be worse. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message