From owner-freebsd-current Sun Nov 7 0:43:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from gina.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 1AC0F14C02 for ; Sun, 7 Nov 1999 00:43:43 -0800 (PST) (envelope-from root@neland.dk) Received: from gina.neland.dk (gina.neland.dk [192.168.0.14]) by gina.neland.dk (8.9.3/8.9.3) with ESMTP id JAA00524 for ; Sun, 7 Nov 1999 09:43:42 +0100 (CET) (envelope-from root@neland.dk) Date: Sun, 7 Nov 1999 09:43:42 +0100 (CET) From: Charlie ROOT To: freebsd-current@freebsd.org Subject: Dr Neuhaus niccy go not recognized 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 During make of kernel: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" Is this a "simple" matter of the right options to config, or does it involve changes to the code? Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #130: Sat Nov 6 18:14:11 CET 1999 root@gina.neland.dk:/usr/src/sys/compile/GINA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (337.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 67096576 (65524K bytes) avail memory = 61603840 (60160K bytes) Preloaded elf kernel "kernel" at 0xc0357000. VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (c0000e38) VESA: S3 Incorporated Trio3D. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 9 at device 4.2 on pci0 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: vendor 0x0553 product 0x0002, rev 1.00/1.00, addr 2 intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 pcm0: irq 5 at device 11.0 on pci0 ed1: irq 10 at device 12.0 on pci0 ed1: address 00:80:ad:50:40:cf, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver unknown0: at port 0x200-0x201,0x202-0x203 irq 11 on isa0 i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 2 ISDN trace device(s) attached ad0: ATA-4 disk at ata0 as master ad0: 8207MB (16809660 sectors), 16676 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-4 disk at ata0 as slave ad1: 6197MB (12692295 sectors), 13431 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 Mounting root from ufs:/dev/wd1s3a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 1:12:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles510.castles.com [208.214.165.74]) by hub.freebsd.org (Postfix) with ESMTP id 88AB414FBB for ; Sun, 7 Nov 1999 01:12:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA10454; Sun, 7 Nov 1999 01:03:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911070903.BAA10454@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay Cc: jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG Subject: Re: doscmd broken on current? In-reply-to: Your message of "Sat, 06 Nov 1999 22:24:35 +0200." <199911062024.WAA41602@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 01:03:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Is doscmd working for anyone on current? Here I just get: > > > > > >--------- > > > > > >I have tried it on a single processor and SMP -current and both do the same > > >thing. I had it working a while back, so I think my configuration is ok. > > > > > >Ideas on how to look into this? > > > > Start by invoking it with the various debug/trace options. I'd guess > > that it may be broken by the signal-related changes that were made > > recently. > > hehehe It dies at the very first vm86 instruction, so I guess something > isn't setup correctly to enter vm86 mode via the sigreturn(): I bet that someone got smart and disallowed PSL_VM in eflags on a return to user-mode. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Sun Nov 7 1:25:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id E7A9514A04 for ; Sun, 7 Nov 1999 01:25:19 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA42601 for current@FreeBSD.org; Sun, 7 Nov 1999 10:04:54 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sun, 07 Nov 1999 10:04:39 +0100 From: Marcel Moolenaar Message-ID: <382540A7.26B40425@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199911061841.MAA26019@free.pcs>, <199911062024.WAA41602@zibbi.mikom.csir.co.za> Subject: Re: doscmd broken on current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > Hmmm I see the sigreturn man page hasn't been updated, it still says that > sigreturn takes a struct sigcontext * argument, while the signal.h file > says it takes ucontext_t *. Sigreturn still takes a struct sigcontext*. It also takes a ucontext_t. I think the header should define sigreturn to take a struct sigcontext*... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 7 2:27:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 1496814DE4; Sun, 7 Nov 1999 02:27:33 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA00486; Sun, 7 Nov 1999 11:15:22 +0100 (CET) Message-Id: <199911071015.LAA00486@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: obrien@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: show stopper for Gcc 2.95.2 conversion Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 07 Nov 1999 00:11:48 +0100." <19991106151148.B5642@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 11:15:22 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: >On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote: >> Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have > >Here is the patch I've been working on (before I 1st got BDE's reply). >The changes are mostly from OpenBSD + style changes for the way we do >things. Can you also test this one? > [patch snipped] This patch also works with both compilers. Seems kind of hairy, though. Any idea why GCC 2.95.2 produces so much more code ? # ls -l /kernel*gc* -rwxr-xr-x 1 root wheel 1753591 Nov 7 10:50 /kernel.egcs* -rwxr-xr-x 1 root wheel 1788387 Nov 7 10:57 /kernel.gcc* well, it's not all that much more. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 3: 4:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 17ACD14F08 for ; Sun, 7 Nov 1999 03:04:25 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p08-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.137]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA03810; Sun, 7 Nov 1999 20:02:39 +0900 (JST) Message-ID: <38255BA8.BF07FCAA@newsguy.com> Date: Sun, 07 Nov 1999 19:59:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Taavi Talvik Cc: Chris Costello , Lauri Laupmaa , current@FreeBSD.ORG Subject: Re: stuck with ~year old current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Taavi Talvik wrote: > > Only alternative to get these from outside is to upgrade graduall.. but > who knows which intermediate source repository dates are good for it? Mike once said (and, ergo, can be found on the mailing list archives): "We do not support upgrading to -current from anything else than the latest -stable." There's your answer. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 3:22: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 7A72414E08 for ; Sun, 7 Nov 1999 03:22:00 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 1540213 invoked from network); 7 Nov 1999 11:21:58 -0000 Received: from d253.paris-34.cybercable.fr (HELO cybercable.fr) ([212.198.34.253]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 7 Nov 1999 11:21:58 -0000 Message-ID: <382560DB.73779819@cybercable.fr> Date: Sun, 07 Nov 1999 12:22:03 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: stuck with ~year old current References: <38255BA8.BF07FCAA@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Taavi Talvik wrote: > > > > Only alternative to get these from outside is to upgrade graduall.. but > > who knows which intermediate source repository dates are good for it? > > Mike once said (and, ergo, can be found on the mailing list > archives): > > "We do not support upgrading to -current from anything else than the > latest -stable." Does this still hold after the recent signal changes ? TfH (I assume Yes, if one first upgrade the kernel, then the world) > > There's your answer. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > What y'all wanna do? > Wanna be hackers? Code crackers? Slackers > Wastin' time with all the chatroom yakkers? > > 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 7 3:25: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F3E5F14E08 for ; Sun, 7 Nov 1999 03:24:59 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Nov 1999 11:24:58 +0000 (GMT) Date: Sun, 7 Nov 1999 11:24:58 +0000 From: David Malone To: Jonathan Lemon Cc: current@freebsd.org, Ollivier Robert Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107112458.A14670@walton.maths.tcd.ie> References: <199911061929.NAA26145@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911061929.NAA26145@free.pcs> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 06, 1999 at 01:29:16PM -0600, Jonathan Lemon wrote: > From the manual page for flock: > > NOTES > Locks are on files, not file descriptors. That is, file descriptors du- > plicated through dup(2) or fork(2) do not result in multiple instances of > a lock, but rather multiple references to a single lock. If a process > holding a lock on a file forks and the child explicitly unlocks the file, > the parent will lose its lock. Doesn't this make it impossible to hold a lock on a file when you want to fork a child to do some task 'cos the lock will be dropped when the child closes its copy of the file discriptor on exit? Either it's a posix goof or the lock shouldn't be let go until either explicitly released or the last instance of the file discriptor is closed? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 3:51:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9DA2514C02 for ; Sun, 7 Nov 1999 03:51:10 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Nov 1999 11:51:09 +0000 (GMT) Date: Sun, 7 Nov 1999 11:51:06 +0000 From: David Malone To: Ollivier Robert Cc: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107115106.A15177@walton.maths.tcd.ie> References: <199911061929.NAA26145@free.pcs> <19991107020102.A9992@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991107020102.A9992@keltia.freenix.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 02:01:02AM +0100, Ollivier Robert wrote: > Right but in Postfix case this is not the case. The "master" process run to > check whether Postfix is running or not is definitely NOT a child of the real > "master" process. But if the real master process forks and then it's child closes the fd which the lock was on, then the master process will have lost it's lock. Is this likely? Does the real master fork children to do stuff? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 3:56:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4489514D3B for ; Sun, 7 Nov 1999 03:56:35 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p07-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.136]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA19599; Sun, 7 Nov 1999 20:56:27 +0900 (JST) Message-ID: <38255C38.19FD92BA@newsguy.com> Date: Sun, 07 Nov 1999 20:02:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Lauri Laupmaa Cc: Michael Reifenberger , current@FreeBSD.ORG Subject: Re: stuck with ~year old current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lauri Laupmaa wrote: > > On Fri, 5 Nov 1999, Michael Reifenberger wrote: > > > The flag is probably -fformat-extensions so eliminate it from > > /usr/share/mk/bsd.kern.mk. > > Then build linker/kernel/world. > > Thank you all who replied! The trick was to take new loader from running > system, because it was impossible to build one with old gcc... Impossible is a little bit too harsh. I do it all the time on freefall, which runs -stable. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 3:57:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id ACB7C1509F; Sun, 7 Nov 1999 03:57:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p07-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.136]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA19824; Sun, 7 Nov 1999 20:57:07 +0900 (JST) Message-ID: <38256425.7AD008ED@newsguy.com> Date: Sun, 07 Nov 1999 20:36:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Gary Jennejohn Cc: obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion References: <199911071015.LAA00486@peedub.muc.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Jennejohn wrote: > > Any idea why GCC 2.95.2 produces so much more code ? Mmmm... O'Brien, could you make sure the space-critical code in sys/boot compiles ok? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 4:28:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A167E14DA0 for ; Sun, 7 Nov 1999 04:28:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p10-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.107]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id VAA29565; Sun, 7 Nov 1999 21:28:37 +0900 (JST) Message-ID: <38256DA0.F684B854@newsguy.com> Date: Sun, 07 Nov 1999 21:16:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Thierry Herbelot Cc: current@FreeBSD.ORG Subject: Re: stuck with ~year old current References: <38255BA8.BF07FCAA@newsguy.com> <382560DB.73779819@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry Herbelot wrote: > > > Mike once said (and, ergo, can be found on the mailing list > > archives): > > > > "We do not support upgrading to -current from anything else than the > > latest -stable." > > Does this still hold after the recent signal changes ? > > TfH > > (I assume Yes, if one first upgrade the kernel, then the world) You assume correctly. -stable loader can load -current kernel. Well, it could until very recently. I don't know if the new stuff Mike is doing will introduce any incompatibility. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 4:41:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 568E614FDE; Sun, 7 Nov 1999 04:41:52 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA13458; Sun, 7 Nov 1999 13:41:48 +0100 (CET) (envelope-from des) To: "Kenneth D. Merry" Cc: jlemon@americantv.com (Jonathan Lemon), current@freebsd.org Subject: Re: TCP sockets stuck in the CLOSING state References: <199911052219.PAA01743@panzer.kdm.org> From: Dag-Erling Smorgrav Date: 07 Nov 1999 13:41:48 +0100 In-Reply-To: "Kenneth D. Merry"'s message of "Fri, 5 Nov 1999 15:19:41 -0700 (MST)" Message-ID: Lines: 61 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [bringing this back to -current, with a Bcc to -security] "Kenneth D. Merry" writes: > Jonathan Lemon wrote... > > In article you write: > > > Before I spend a lot of time hunting this down, I figured it might be worth > > > asking -- is there any particular reason why TCP sockets may be getting > > > stuck in the CLOSING state more often now? > > Not sure. But here's a tcpdump trace of a socket that ends up in the > > CLOSING state. (on the host ``cache''). > > [...] > > 1. the other end (folly) never acks the FIN. The packets at > > timestamp .492154 and .492160 do not cover the FIN in the > > sequence space. Yet the host `folly' closes the socket. This is weird, and probably deserves some investigation (at least if cache and folly are on the same LAN; otherwise there's a non-zero possibility of the ACK simply getting lost on the way) > > 2. the end that is stuck in CLOSING (cache) never retransmits > > the FIN. (The tcpdump extends for about 5 minutes after the > > last packet, with 0 packets lost). It's not supposed to (according to RFC793). > > Both machines are running -current from early this week. > > Those are definitely odd. > > After looking through the changes since June, I think (and DES seems to > agree) that the problems are most likely in your timeout code from August. > Most every other change in the TCP stack has been cosmetic, or #ifdefed, so > it wouldn't be enabled by default. > > He is going to try to find the problem, although it's most likely a pretty > subtle bug. Well, the TCP state machine was never a fun read, amd I haven't had time to look very closely at the problem yet, but it seems that there is no way for a connection to leave the TCPS_CLOSING state other than the receipt of an ACK matching a previously sent FIN. If the ACK gets lost, the connection is stuck in TCPS_CLOSING forever (I have a connection that's been stuck in TCPS_CLOSING for at least three days now). The only instance I can find where a connection in TCPS_CLOSING state is closed even if no ACK has been received is when the socket has the SO_KEEPALIVE option set (tcp_timer_keep() in tcp_timer.c). Note that the state transition diagram in RFC793 does not specify a timeout for the CLOSING -> TIME_WAIT transition, so any faithful implementation of RFC793 has this bug (but why doesn't this happen on -STABLE, or on pre-August -CURRENT?) This hints at a potential DoS vulnerability. Hack a TCP stack to never acknowledge FIN segments, and blast away at your victim; chances are he'll run out of mbufs before you run out of source ports (each source port can only be used once in the attack). Give me a few hours and I might be able to verify this vulnerability experimentally. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 5: 2: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 050CC14F6D for ; Sun, 7 Nov 1999 05:01:49 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1885 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sun, 7 Nov 1999 14:01:48 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 2B72E38E2; Sun, 7 Nov 1999 14:01:46 +0100 (MET) Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: from Charlie ROOT at "Nov 7, 99 09:43:42 am" To: root@neland.dk (Charlie ROOT) Date: Sun, 7 Nov 1999 14:01:46 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1016 Message-Id: <19991107130146.2B72E38E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Charlie ROOT: > During make of kernel: > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c > ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" > > Is this a "simple" matter of the right options to config, or does it > involve changes to the code? PnP support for i4b in -current was disabled during the conversion of -current to the new-bus/new-pnp architecture; as a result all PnP ISDN cards i4b supports do no longer work. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 5: 7:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 75B5814F6D for ; Sun, 7 Nov 1999 05:07:25 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11kS31-000JFC-00 for freebsd-current@freebsd.org; Sun, 7 Nov 1999 13:07:56 +0000 Date: Sun, 7 Nov 1999 14:07:18 +0100 (CET) From: Marc Schneiders To: freebsd-current@freebsd.org Subject: Make release troubles 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 have studied the Makefile. I have searched the archives of the lists. I have put the files necessary for the ports build for docproj during the make in a separate directory (/usr/ports/distfiles.release), with no extra files there. I have set this in the Makefile. Nevertheless this is what happened: touch release.2 Making docs... ===> Extracting for docproj-1.1 [...] [...] [...] ===> Registering installation for sgmlformat-1.7 ===> Returning to build of docproj-1.1 ===> docproj-1.1 depends on executable: sgmlnorm - found ===> docproj-1.1 depends on executable: jade - found ===> docproj-1.1 depends on executable: tidy - not found ===> Verifying install for tidy in /usr/ports/www/tidy ===> Extracting for tidy-0.9.99.1 >> Checksum OK for tidy27sep99.tgz. Here it just stopped (and had been waiting for 9 hours...). No error message, nothing. Machine was responding OK. No kernel messages, no messages. Nothing peculiar in top etc. So I tried something weird (in my eyes anyway) and kill -HUPped the PID. It continued. Great, well for a moment. ===> Patching for tidy-0.9.99.1 ===> Applying FreeBSD patches for tidy-0.9.99.1 ===> Configuring for tidy-0.9.99.1 ===> Building for tidy-0.9.99.1 cc -O -pipe -D__USE_MISC -c attrs.c cc -O -pipe -D__USE_MISC -c istack.c cc -O -pipe -D__USE_MISC -c parser.c cc -O -pipe -D__USE_MISC -c tags.c cc -O -pipe -D__USE_MISC -c entities.c cc -O -pipe -D__USE_MISC -c lexer.c cc -O -pipe -D__USE_MISC -c pprint.c cc -O -pipe -D__USE_MISC -c clean.c cc -O -pipe -D__USE_MISC -c localize.c cc -O -pipe -D__USE_MISC -c config.c cc -O -pipe -D__USE_MISC -c tidy.c cc -O -pipe -D__USE_MISC -o tidy attrs.o istack.o parser.o tags.o entities.o lexer.o pprint.o clean.o localize.o config.o tidy.o -lc ===> Installing for tidy-0.9.99.1 install -c -s -o root -g wheel -m 555 /usr/ports/www/tidy/work/tidy27sep99/tidy /usr/local/bin/tidy ===> Installing documentation for tidy-0.9.99.1 ===> Generating temporary packing list ===> Registering installation for tidy-0.9.99.1 ===> Returning to build of docproj-1.1 ===> docproj-1.1 depends on executable: lynx - not found ===> Verifying install for lynx in /usr/ports/www/lynx ===> Extracting for lynx-2.8.2rel.1 >> Checksum OK for lynx2.8.2rel.1.tar.bz2. ===> lynx-2.8.2rel.1 depends on executable: bzip2 - not found ===> Verifying install for bzip2 in /usr/ports/archivers/bzip2 >> bzip2-0.9.5d.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://sourceware.cygnus.com/pub/bzip2/v095/. fetch: sourceware.cygnus.com: Host name lookup failure >> Attempting to fetch from http://www.kernel.org/pub/software/utils/compress/bzip2/. fetch: `www.kernel.org': cannot resolve: Host name lookup failure >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp.FreeBSD.org: Host name lookup failure >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/ and try again. *** Error code 1 bzip2-0.9.5d.tar.gz *is* in the directory /usr/ports/distfiles.release, mentioned earlier. Now what can I do? Should this file (and others?, but which?) be in the 'normal' distfiles directory and not in the one set in the Makefile? I can see only one way out, which is to spend about $30 on phone charges and stay online for the make release, after deleting *all* of the distfiles on my system. Maybe there is someone out there who knows a cheaper and better way? TIA! Marc Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 1:40pm up 11 days, 7:21, load average: 2.23 2.13 2.04 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 5:57:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id D865B14F6D for ; Sun, 7 Nov 1999 05:55:58 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id PAA54812; Sun, 7 Nov 1999 15:01:40 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911071301.PAA54812@zibbi.mikom.csir.co.za> Subject: Re: doscmd broken on current? In-Reply-To: <199911070903.BAA10454@dingo.cdrom.com> from Mike Smith at "Nov 7, 1999 01:03:02 am" To: mike@smith.net.au (Mike Smith) Date: Sun, 7 Nov 1999 15:01:40 +0200 (SAT) Cc: jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 doscmd working for anyone on current? Here I just get: > > > > > > > >--------- > > > > > > > >I have tried it on a single processor and SMP -current and both do the same > > > >thing. I had it working a while back, so I think my configuration is ok. > > > > > > > >Ideas on how to look into this? > > > > > > Start by invoking it with the various debug/trace options. I'd guess > > > that it may be broken by the signal-related changes that were made > > > recently. > > > > hehehe It dies at the very first vm86 instruction, so I guess something > > isn't setup correctly to enter vm86 mode via the sigreturn(): > > I bet that someone got smart and disallowed PSL_VM in eflags on a > return to user-mode. Nope it wasn't that bad. I'm not sure if this is the correct fix, but with this patch I can boot dos again. Can someone with more knowledge of the signal stuff look and say if this is correct/enough? The redirector don't work though. I just get a "File not Found" error when trying to dir any of the redirected directories. John -- John Hay -- John.Hay@mikom.csir.co.za Index: doscmd.c =================================================================== RCS file: /home/ncvs/src/usr.bin/doscmd/doscmd.c,v retrieving revision 1.11 diff -u -r1.11 doscmd.c --- doscmd.c 1999/10/13 23:48:35 1.11 +++ doscmd.c 1999/11/07 12:50:06 @@ -258,6 +258,7 @@ sigemptyset(&uc.uc_sigmask); sigaltstack(NULL, &uc.uc_stack); + uc.uc_mcontext.mc_onstack = uc.uc_stack.ss_flags; if (tmode) tracetrap(REGS); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 6: 9:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 965D714F6D for ; Sun, 7 Nov 1999 06:09:09 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id IAA13318; Sun, 7 Nov 1999 08:09:05 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id IAA05708; Sun, 7 Nov 1999 08:09:03 -0600 (CST) Message-ID: <19991107080903.23572@right.PCS> Date: Sun, 7 Nov 1999 08:09:03 -0600 From: Jonathan Lemon To: Dag-Erling Smorgrav Cc: "Kenneth D. Merry" , current@freebsd.org Subject: Re: TCP sockets stuck in the CLOSING state References: <199911052219.PAA01743@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Dag-Erling Smorgrav on Nov 11, 1999 at 01:41:48PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote: > [bringing this back to -current, with a Bcc to -security] > > "Kenneth D. Merry" writes: > > Jonathan Lemon wrote... > > > In article you write: > > > > Before I spend a lot of time hunting this down, I figured it might be worth > > > > asking -- is there any particular reason why TCP sockets may be getting > > > > stuck in the CLOSING state more often now? > > > Not sure. But here's a tcpdump trace of a socket that ends up in the > > > CLOSING state. (on the host ``cache''). > > > [...] > > > 1. the other end (folly) never acks the FIN. The packets at > > > timestamp .492154 and .492160 do not cover the FIN in the > > > sequence space. Yet the host `folly' closes the socket. > > This is weird, and probably deserves some investigation (at least if > cache and folly are on the same LAN; otherwise there's a non-zero > possibility of the ACK simply getting lost on the way) Good point. I'll try taking a tcpdump on both sides to see if the ACK is getting lost, or if it just isn't getting sent at all. > Note that the state transition diagram in RFC793 does not specify a > timeout for the CLOSING -> TIME_WAIT transition, so any faithful > implementation of RFC793 has this bug (but why doesn't this happen on > -STABLE, or on pre-August -CURRENT?) I'm not sure abuot that one. But I've just committed a fix to tcp_fsm.h, which will cause it to re-transmit a FIN in CLOSING state. The FIN was originally taken out by Garrett in rev 1.5, and restored by dg in rev 1.6. However, it was re-removed in 1.10 when Garrett made a large commit, presumably he hadn't taken it out of his local tree. It fixes the problem here (at least, I can't replicate the problem any more). I'm not sure if I'm fixing the symptoms rather than the actual problem then, though. NetBSD has the same fix in their tree as well. I'm pretty sure that I've seen this problem on -current going back as early as March as well. > This hints at a potential DoS vulnerability. Hack a TCP stack to never > acknowledge FIN segments, and blast away at your victim; chances are > he'll run out of mbufs before you run out of source ports (each source > port can only be used once in the attack). Give me a few hours and I > might be able to verify this vulnerability experimentally. Do let me know if this is the case. I was considering this last night, but was too tired to try an figure out how to generate a TCP stream that would ACK everything but the FIN. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 6:14:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id DF47114F6D for ; Sun, 7 Nov 1999 06:14:08 -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.3/8.9.1) with ESMTP id JAA77246; Sun, 7 Nov 1999 09:14:00 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199911071414.JAA77246@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dag-Erling Smorgrav Cc: "Kenneth D. Merry" , jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: TCP sockets stuck in the CLOSING state References: <199911052219.PAA01743@panzer.kdm.org> In-reply-to: Your message of "07 Nov 1999 13:41:48 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 09:14:00 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Kenneth D. Merry" writes: > > Jonathan Lemon wrote... > > > In article you write: > > > > Before I spend a lot of time hunting this down, I figured it might be worth > > > > asking -- is there any particular reason why TCP sockets may be getting > > > > stuck in the CLOSING state more often now? > > > Not sure. But here's a tcpdump trace of a socket that ends up in the > > > CLOSING state. (on the host ``cache''). > > > [...] > > > 1. the other end (folly) never acks the FIN. The packets at > > > timestamp .492154 and .492160 do not cover the FIN in the > > > sequence space. Yet the host `folly' closes the socket. > > This is weird, and probably deserves some investigation (at least if > cache and folly are on the same LAN; otherwise there's a non-zero > possibility of the ACK simply getting lost on the way) > > > > 2. the end that is stuck in CLOSING (cache) never retransmits > > > the FIN. (The tcpdump extends for about 5 minutes after the > > > last packet, with 0 packets lost). > > It's not supposed to (according to RFC793). I think your interpretation of the TCP spec is in error. Since the FIN occupies sequence space, it's the same as unacknowledged data and should be retransmitted, just like any unacked data in the window would be. Eventually, the TCP stack should timeout the connection with an ACK-timeout. 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 7 6:17: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 1CE4B14E65 for ; Sun, 7 Nov 1999 06:17:00 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id PAA65649; Sun, 7 Nov 1999 15:16:48 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 7 Nov 1999 15:16:48 +0100 (CET) From: Leif Neland To: Hellmuth Michaelis Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: <19991107130146.2B72E38E2@hcswork.hcs.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 On Sun, 7 Nov 1999, Hellmuth Michaelis wrote: > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > > -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c > > ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" > > > > Is this a "simple" matter of the right options to config, or does it > > involve changes to the code? > > PnP support for i4b in -current was disabled during the conversion of > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > cards i4b supports do no longer work. > Anybody working on re-enabling it, and if so, any time-horisonts? 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 7 6:17:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 38D7E14ED4 for ; Sun, 7 Nov 1999 06:17:00 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id PAA65649; Sun, 7 Nov 1999 15:16:48 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 7 Nov 1999 15:16:48 +0100 (CET) From: Leif Neland To: Hellmuth Michaelis Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: <19991107130146.2B72E38E2@hcswork.hcs.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 On Sun, 7 Nov 1999, Hellmuth Michaelis wrote: > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > > -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c > > ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" > > > > Is this a "simple" matter of the right options to config, or does it > > involve changes to the code? > > PnP support for i4b in -current was disabled during the conversion of > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > cards i4b supports do no longer work. > Anybody working on re-enabling it, and if so, any time-horisonts? 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 7 6:32:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2E75114C2D for ; Sun, 7 Nov 1999 06:32:08 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA13671; Sun, 7 Nov 1999 15:32:03 +0100 (CET) (envelope-from des) To: "Louis A. Mamakos" Cc: "Kenneth D. Merry" , jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG Subject: Re: TCP sockets stuck in the CLOSING state References: <199911052219.PAA01743@panzer.kdm.org> <199911071414.JAA77246@whizzo.transsys.com> From: Dag-Erling Smorgrav Date: 07 Nov 1999 15:32:02 +0100 In-Reply-To: "Louis A. Mamakos"'s message of "Sun, 07 Nov 1999 09:14:00 -0500" Message-ID: Lines: 11 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Louis A. Mamakos" writes: > I think your interpretation of the TCP spec is in error. Since the FIN > occupies sequence space, it's the same as unacknowledged data and should > be retransmitted, just like any unacked data in the window would be. > Eventually, the TCP stack should timeout the connection with an ACK-timeout. I believe you are correct. Thank you for pointing this out. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 6:43:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id C35C614C2D for ; Sun, 7 Nov 1999 06:43:30 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 11kTIw-000IkO-00; Sun, 07 Nov 1999 14:28:26 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 11kTIw-0000Zt-00; Sun, 07 Nov 1999 14:28:26 +0000 Date: Sun, 7 Nov 1999 14:28:26 +0000 From: Ben Smithurst To: David Malone Cc: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107142826.A2118@strontium.scientia.demon.co.uk> References: <199911061929.NAA26145@free.pcs> <19991107112458.A14670@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991107112458.A14670@walton.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > On Sat, Nov 06, 1999 at 01:29:16PM -0600, Jonathan Lemon wrote: > >> From the manual page for flock: >> >> NOTES >> Locks are on files, not file descriptors. That is, file descriptors du- >> plicated through dup(2) or fork(2) do not result in multiple instances of >> a lock, but rather multiple references to a single lock. If a process >> holding a lock on a file forks and the child explicitly unlocks the file, >> the parent will lose its lock. > > Doesn't this make it impossible to hold a lock on a file when you > want to fork a child to do some task 'cos the lock will be dropped > when the child closes its copy of the file discriptor on exit? > Either it's a posix goof or the lock shouldn't be let go until > either explicitly released or the last instance of the file discriptor > is closed? The lock doesn't seem to be released until *explicitly* released, like the manual page says. I don't think closing the descriptor counts as an explicit unlock, though I am probably wrong. Run this program, you'll see the parent still has the lock. Change close(fd) to flock(fd, LOCK_UN) and you'll see it doesn't. It's possible I've misunderstood something though. #include #include #include #include int main(void) { int fd; fd = open("lock", O_CREAT|O_RDWR, 0600); if (fd < 0) err(1, "open"); if (flock(fd, LOCK_EX) != 0) err(1, "flock"); switch (fork()) { case -1: err(1, "fork"); case 0: close(fd); _exit(0); default: sleep(2); break; } system("lsof | less"); return (0); } -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 7:37:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 469E314A1C for ; Sun, 7 Nov 1999 07:37:44 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id QAA13909 for ; Sun, 7 Nov 1999 16:37:43 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E80.dip.t-dialin.net [62.158.14.128]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id QAA13897 for ; Sun, 7 Nov 1999 16:37:36 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id PAA79791 for ; Sun, 7 Nov 1999 15:49:03 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <38259147.1CEA1833@dead-end.net> Date: Sun, 07 Nov 1999 15:48:39 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: ESS 1868 driver, again References: <19991107053836.783251C03@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > As to why the 1869 isn't working for you, that's anybody's guess. You > might try posting the 'dmesg' output (not from syslog) and your complete > config file, as well as any other pertinant information you can think of. Ok here is the (hopefully) complete information. -current cvsupped ~2 hours ago. If seems there will no interrupts be generated. If I try to play something, nothing happens, if I run "vmstat -i" then, there are 0 interrupts for irq 5 (pcm0). Daniel kernel config file: -------------------- machine i386 ident LAPTOP maxusers 6 options PQ_LARGECACHE cpu I686_CPU options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options DDB options KTRACE options PERFMON options UCONSOLE options INET pseudo-device ether pseudo-device loop pseudo-device bpf pseudo-device tun options ICMP_BANDLIM options FFS options NFS options NFS_NOSERVER options CD9660 options MSDOSFS options PROCFS options FFS_ROOT options SOFTUPDATES options QUOTA options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L controller scbus0 device da0 device pass0 pseudo-device pty options MSGBUF_SIZE=20480 controller isa0 controller pnp0 options PNPBIOS controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="german.iso" device psm0 at atkbdc? irq 12 options PSM_HOOKAPM options PSM_RESETAFTERSUSPEND device vga0 at isa? port ? conflicts options VGA_WIDTH90 options VESA pseudo-device splash device sc0 at isa? options MAXCONS=6 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE device npx0 at nexus? port IO_NPX flags 0x0 irq 13 controller ata0 device atadisk0 device atapicd0 options ATA_ENABLE_ATAPI_DMA controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ed0 device pcm0 device apm0 at nexus? device joy0 at isa? port IO_GAME controller pci0 controller pcic0 at isa? irq 10 controller pcic1 at isa? irq 10 controller card0 options PCIC_RESUME_RESET controller ppbus0 controller vpo0 at ppbus? device lpt0 at ppbus? device ppi0 at ppbus? device ppc0 at isa? port? irq 7 drq 3 controller uhci0 controller usb0 device ugen0 options HZ=500 -------------------- dmesg output of verbose boot: -------------------- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #241: Sun Nov 7 13:48:17 CET 1999 root@laptop.rock.net:/usr/src/sys/compile/ROCK Calibrating clock(s) ... TSC clock: 232125177 Hz, i8254 clock: 1193284 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (232.11-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002ef000 - 0x03ffafff, 64012288 bytes (15628 pages) avail memory = 62169088 (60712K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f66a0 bios32: Entry = 0xfd7e0 (c00fd7e0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f66d0 pnpbios: Entry = f0000:a62f Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 VESA: information block 56 45 53 41 00 02 6b 00 00 c0 00 00 00 00 f6 8c 00 c0 10 00 00 00 b4 27 00 c0 b5 27 00 c0 b6 27 00 c0 b7 27 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 11 mode(s) found VESA: v2.0, 1024k memory, flags:0x0, mode table:0xc00c8cf6 (c0008cf6) VESA: Copyright 1994 TRIDENT MICROSYSTEMS INC. VESA: Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x80001010 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7192, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 00000000, size 26 found-> vendor=0x1023, dev=0x9397, revid=0xf3 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fe400000, size 22 map[14]: type 1, range 32, base fede0000, size 17 map[18]: type 1, range 32, base fe800000, size 22 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fcd0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 0000fce0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 0000ff80, size 4 found-> vendor=0x104c, dev=0xac15, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=255 found-> vendor=0x104c, dev=0xac15, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=255 pci0: on pcib0 vga-pci0: irq 9 at device 2.0 on pci0 isab0: at device 3.0 on pci0 pnpbios: 20 devices, largest 224 bytes PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0xff00-0xff41, size=0x42, align=0x1 PNP0c02: adding io range 0xff80-0xff8f, size=0x10, align=0x1 PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0x1 PNP0c02: adding io range 0x398-0x399, size=0x2, align=0x1 PNP0c02: adding io range 0x22-0x22, size=0x1, align=0x1 PNP0c02: adding io range 0x24-0x3d, size=0x1a, align=0x1 PNP0c02: adding io range 0x50-0x52, size=0x3, align=0x1 PNP0c02: adding io range 0x72-0x77, size=0x6, align=0x1 PNP0c02: adding io range 0x90-0x9f, size=0x10, align=0x1 PNP0c02: adding io range 0xa4-0xad, size=0xa, align=0x1 PNP0c02: adding io range 0xb0-0xbd, size=0xe, align=0x1 PNP0c02: adding io range 0x2100-0x216f, size=0x70, align=0x1 PNP0c02: adding io range 0x2178-0x21ef, size=0x78, align=0x1 PNP0c02: adding io range 0x21f8-0x21ff, size=0x8, align=0x1 PNP0c02: adding io range 0x46e8-0x46e8, size=0x1, align=0x1 PNP0c02: start dependant pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 PNP0c02: adding io range 0x1260-0x1263, size=0x4, align=0x1 PNP0c02: adding io range 0x2260-0x2263, size=0x4, align=0x1 PNP0c02: adding io range 0x3260-0x3263, size=0x4, align=0x1 PNP0c02: adding io range 0x4260-0x4263, size=0x4, align=0x1 PNP0c02: adding io range 0x5260-0x5263, size=0x4, align=0x1 PNP0c02: adding io range 0x6260-0x6263, size=0x4, align=0x1 PNP0c02: adding io range 0x7260-0x7263, size=0x4, align=0x1 PNP0c02: adding io range 0x8260-0x8263, size=0x4, align=0x1 PNP0c02: adding io range 0x9260-0x9263, size=0x4, align=0x1 PNP0c02: adding io range 0xa260-0xa263, size=0x4, align=0x1 PNP0c02: adding io range 0xb260-0xb263, size=0x4, align=0x1 PNP0c02: adding io range 0xc260-0xc263, size=0x4, align=0x1 PNP0c02: adding io range 0xd260-0xd263, size=0x4, align=0x1 PNP0c02: adding io range 0xe260-0xe263, size=0x4, align=0x1 PNP0c02: adding io range 0xf260-0xf263, size=0x4, align=0x1 PNP0c02: adding memory range 0xfff80000-0xfffdffff, size=0x60000 PNP0c02: adding memory range 0xfffe0000-0xffffffff, size=0x20000 PNP0c02: start dependant pnpbios: handle 1 device ID PNP0c02 (020cd041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000 PNP0c01: adding memory range 0xe0000-0xfffff, size=0x20000 PNP0c01: adding memory range 0x100000-0x3ffffff, size=0x3f00000 PNP0c01: start dependant pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: start dependant pnpbios: handle 3 device ID PNP0200 (0002d041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 00x4 PNP0000: start dependant pnpbios: handle 4 device ID PNP0000 (0000d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 00x1 PNP0100: start dependant pnpbios: handle 5 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 PNP0b00: start dependant pnpbios: handle 6 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 00x2 PNP0303: start dependant pnpbios: handle 7 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 PNP0c04: start dependant pnpbios: handle 8 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 9 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: start dependant pnpbios: handle 10 device ID PNP0a03 (030ad041) TWH0003: adding dma mask 0x8 TWH0003: adding io range 0x2f8-0x2ff, size=0x8, align=0x1 TWH0003: adding irq mask 00x8 TWH0003: start dependant pnpbios: handle 11 device ID TWH0003 (0300e852) PNP0401: adding dma mask 0x1 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0401: adding io range 0x778-0x77f, size=0x8, align=0x8 PNP0401: adding irq mask 0x80 PNP0401: start dependant pnpbios: handle 14 device ID PNP0401 (0104d041) PNP0f13: adding irq mask 0x1000 PNP0f13: start dependant pnpbios: handle 16 device ID PNP0f13 (130fd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x1 PNP0501: adding irq mask 0x10 PNP0501: start dependant pnpbios: handle 17 device ID PNP0501 (0105d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: start dependant pnpbios: handle 21 device ID PNP0700 (0007d041) ESS0006: adding io range 0x800-0x807, size=0x8, align=0x8 ESS0006: start dependant pnpbios: handle 24 device ID ESS0006 (06007316) ESS0001: adding io range 0x201-0x201, size=0x1, align=0x1 ESS0001: start dependant pnpbios: handle 25 device ID ESS0001 (01007316) ESS1869: adding io range 0x220-0x22f, size=0x10, align=0x20 ESS1869: adding io range 0x388-0x38b, size=0x4, align=0x4 ESS1869: adding io range 0x330-0x331, size=0x2, align=0x10 ESS1869: adding irq mask 0x20 ESS1869: adding dma mask 0x2 ESS1869: adding dma mask 0x20 ESS1869: start dependant pnpbios: handle 26 device ID ESS1869 (69187316) PNP0e03: adding io range 0x3e0-0x3e1, size=0x2, align=0x1 PNP0e03: start dependant pnpbios: handle 27 device ID PNP0e03 (030ed041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa0: on isab0 ata-pci0: at device 3.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x9 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=00 status0=ff status1=ff uhci0: irq 9 at device 3.2 on pci0 uhci0: USB version 1.0, chip rev. 1 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: at device 3.3 on pci0 pcic-pci0: at device 10.0 on pci0 PCI Config space: 00: ac15104c 02000007 06070001 00820000 10: 00000000 02000000 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 034001ff 40: 00000000 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 002430a9 00000000 00000000 00000000 90: 00748200 00000000 00000000 00000000 Cardbus Socket registers: 00: f000ff53: f000ff53: f000e2c3: f000ff53: 10: f000ff53: f000ff54: f0009441: f000ff53: ExCa registers: 00: 13 88 f5 5a 72 d0 80 e1 3f 74 c8 fa 66 8b 46 08 10: 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 eb 88 d5 43 20: 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 00 00 fb 77 30: a2 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 8a 66 pcic-pci1: at device 10.1 on pci0 PCI Config space: 00: ac15104c 02000007 06070001 00820000 10: 00000000 02000000 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 034002ff 40: 00000000 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 002410a9 00000000 00000000 00000000 90: 00748200 00000000 00000000 00000000 Cardbus Socket registers: 00: f000ff53: f000ff53: f000e2c3: f000ff53: 10: f000ff53: f000ff54: f0009441: f000ff53: ExCa registers: 00: 13 88 f5 5a 72 d0 80 e1 3f 74 c8 fa 66 8b 46 08 10: 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 eb 88 d5 43 20: 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 00 00 fb 77 30: a2 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 8a 66 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: APM hooks installed. psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 03 70 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 03 70 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <6 virtual consoles, flags=0x200> sc0: fb0 kbd0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x49 0x59 0x49 0x49 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A joy0 at port 0x201 on isa0 joy0: joystick pcic0: at irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 ppc: parallel port found at 0x378 PC873xx probe at 0x398 got unknown ID 0xb1 ppc0: ECP SPP SPP ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: can't connect to the drive imm0: (disconnect) s1=0x38 s2=0x38, s3=0x38 imm0: (connect) s1=0x38 s2=0x38, s3=0x38 imm0: can't connect to the drive unknown0: at port 0x4d0-0x4d1,0xff00-0xff41,0xff80-0xff8f,0x10-0x1f,0x398-0x399,0x22,0x24-0x3d,0x50-0x52,0x72-0x77,0x90-0x9f,0xa4-0xad,0xb0-0xbd,0x2100-0x216f,0x2178-0x21ef,0x21f8-0x21ff,0x46e8 on isa0 unknown1: at port 0x80,0x1260-0x1263,0x2260-0x2263,0x3260-0x3263,0x4260-0x4263,0x5260-0x5263,0x6260-0x6263,0x7260-0x7263,0x8260-0x8263,0x9260-0x9263,0xa260-0xa263,0xb260-0xb263,0xc260-0xc263,0xd260-0xd263,0xe260-0xe263,0xf260-0xf263 iomem 0xfff80000-0xfffdffff,0xfffe0000-0xffffffff on isa0 unknown2: at iomem 0-0x9ffff,0xe0000-0xfffff,0x100000-0x3ffffff on isa0 unknown3: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown4: at port 0x40-0x43 irq 0 on isa0 unknown5: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown6: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown7: at port 0xcf8-0xcff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown8: at port 0x800-0x807 on isa0 unknown: can't assign resources pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 on isa0 pcm: setmap 30000, ff00; 0xcd473000 -> 30000 pcm: setmap 40000, ff00; 0xcd483000 -> 40000 unknown9: at port 0x3e0-0x3e1 on isa0 BIOS Geometries: 0:03127f3f 0..786=787 cylinders, 0..127=128 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached ata0: master: success setting up UDMA2 mode on PIIX4 chip ad0: piomode=4 dmamode=2 udmamode=2 ad0: ATA-4 disk at ata0 as master ad0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ata0-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata0: slave: success setting up WDMA2 mode on PIIX4 chip acd0: CDROM drive at ata0 as slave acd0: read 4134KB/s (4134KB/s), 128KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Root mount failed: 22 Mounting root from ufs:wd0s2a wd0s1: type 0xb, start 63, end = 2459519, size 2459457 : OK wd0s2: type 0xa5, start 2459520, end = 6072191, size 3612672 : OK wd0s3: type 0xa0, start 6201216, end = 6346367, size 145152 : OK start_init: trying /sbin/init -------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 7:38: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 44D7314C31; Sun, 7 Nov 1999 07:37:53 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id QAA13924; Sun, 7 Nov 1999 16:37:49 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E80.dip.t-dialin.net [62.158.14.128]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id QAA13913; Sun, 7 Nov 1999 16:37:44 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id PAA78772; Sun, 7 Nov 1999 15:41:35 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <38258F87.F5BF0380@dead-end.net> Date: Sun, 07 Nov 1999 15:41:11 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working References: <3824CCD1.C07B6A8@dead-end.net> <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> <199911061753.KAA22419@harmony.village.org> <199911070644.XAA03042@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 Warner Losh wrote: > > In message <3824CCD1.C07B6A8@dead-end.net> "D. Rock" writes: > : device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > : device sio1 at isa? port IO_COM2 irq 3 > > These look good. IIRC, the kernel I tested with also had: > > device sio2 at isa? port IO_COM3 irq 5 disabled > or > device sio2 > > in it, but I may be misremembering. Just make sure that you use the > config entry that gives you a port at 0x3e8, since most laptops have > COM1 and COM2 which really cannot be disabled (well, the BIOS says you > can disable them, but I've seen a few where the BIOS disabling is > broken). Already did that. I used a config entry for 0x3e8 and one for 0x2e8. Windows 98 configured the card for IRQ 11 I/O 0x3e8 BTW. Just some more pccard questions: When will removing cards (and therefor also suspend/resume) work again? If I remove the netcard or suspend the machine, the system will freeze. I also get a NMI if I insert my netcard (DLink DE-660). If DDB is compiled in I can just continue. Interesting the NMI wasn't generated during initial configuration (via DHCP), but when I tried some ping tests: pccard: card inserted, slot 0 sio2: irq maps: 0x105 0x105 0x105 0x105 sio2: probe failed test(s): 0 1 4 6 7 9 sio2: irq maps: 0x105 0x105 0x105 0x105 sio2: probe failed test(s): 0 1 4 6 7 9 pccard: card inserted, slot 1 ed0 at port 0x240-0x25f irq 15 slot 1 on pccard0 ed0: address 00:80:c8:8b:66:e9, type NE2000 (16 bit) bpf: ed0 attached NMI ... going to debugger ( [the first two sio2 lines were with config index for port 0x3e8, the other ones with config index for 0x2e8] Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 7:38:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 145C0150C6 for ; Sun, 7 Nov 1999 07:38:16 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id QAA13935; Sun, 7 Nov 1999 16:37:52 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E80.dip.t-dialin.net [62.158.14.128]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id QAA13927; Sun, 7 Nov 1999 16:37:50 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id QAA86307; Sun, 7 Nov 1999 16:02:18 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <38259463.FDEA7F45@dead-end.net> Date: Sun, 07 Nov 1999 16:01:55 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: hm@hcs.de Cc: Charlie ROOT , freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized References: <19991107130146.2B72E38E2@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hellmuth Michaelis wrote: > > >From the keyboard of Charlie ROOT: > > > During make of kernel: > > > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > > -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c > > ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" > > > > Is this a "simple" matter of the right options to config, or does it > > involve changes to the code? > > PnP support for i4b in -current was disabled during the conversion of > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > cards i4b supports do no longer work. Any hints when i4b will be converted to new-bus? The code is in stale condition for almost 3 months now. To the original poster: I also have an ISDN PnP card (SedlBauer WinSpeed). In order to get it run on -current, I did the following: - disable "controller pnp0" in your kernel config file (If you need it for some other device, bad luck) - note which resources your PnP card were assigned. - use good old style in your config [my config] device isic0 at isa? port 0x108 irq 10 flags 9 (take a look at /sys/i4b/layer1/i4b_l1.h for your flag number). - patch some files in the i4b tree (hope it is as simple for your device). The example below is from my configuration: Index: i4b_isic_isa.c =================================================================== RCS file: /data/cvs/src/sys/i4b/layer1/i4b_isic_isa.c,v retrieving revision 1.6 diff -u -r1.6 i4b_isic_isa.c --- i4b_isic_isa.c 1999/08/28 00:45:40 1.6 +++ i4b_isic_isa.c 1999/09/26 18:15:40 @@ -204,6 +204,12 @@ break; #endif +#ifdef SEDLBAUER + case FLAG_SWS: + ret = isic_probe_sws(dev); + break; +#endif + default: break; } Index: i4b_sws.c =================================================================== RCS file: /data/cvs/src/sys/i4b/layer1/i4b_sws.c,v retrieving revision 1.5 diff -u -r1.5 i4b_sws.c --- i4b_sws.c 1999/08/28 00:45:41 1.5 +++ i4b_sws.c 1999/09/26 19:44:50 @@ -283,6 +283,11 @@ /* attach callback routine */ +int isic_probe_sws(struct isa_device *dev) +{ + return(1); +} + int isic_attach_sws(struct isa_device *dev) { Index: isa_isic.c =================================================================== RCS file: /data/cvs/src/sys/i4b/layer1/isa_isic.c,v retrieving revision 1.5 diff -u -r1.5 isa_isic.c --- isa_isic.c 1999/08/28 00:45:43 1.5 +++ isa_isic.c 1999/09/26 18:11:33 @@ -196,6 +196,12 @@ break; #endif +#ifdef SEDLBAUER + case FLAG_SWS: + ret = isic_probe_sws(&args); + break; +#endif + default: /* No card type given, try to figure ... */ if (ia->ia_iobase == IOBASEUNK) { [all files are relative to /sys/i4b/layer1] One note: The device doesn't get reset properly during reboot. I don't know if this a general problem with the driver or just a result from my hacks. If I reboot I have to manually turn off/on the machine. Besides from this error, I hadn't had any problems so far. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 7:52:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3747B14D24 for ; Sun, 7 Nov 1999 07:52:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA14631 for ; Sun, 7 Nov 1999 16:52:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: bdev patch looking for review & testers From: Poul-Henning Kamp Date: Sun, 07 Nov 1999 16:52:12 +0100 Message-ID: <14629.941989932@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The main thing in this patch is to make bdevs use the same (ie: normal) vnode locking as character devices. Secondary effects are general cleanup in spec_vnops.c You should see no operational changes by applying this patch, if you do, please report them to me. Poul-Henning Index: gnu/ext2fs/ext2_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vfsops.c,v retrieving revision 1.56 diff -u -r1.56 ext2_vfsops.c --- ext2_vfsops.c 1999/11/01 23:57:22 1.56 +++ ext2_vfsops.c 1999/11/02 06:20:23 @@ -607,7 +607,9 @@ #endif ronly = (mp->mnt_flag & MNT_RDONLY) != 0; - if ((error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p)) != 0) + error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); + VOP_UNLOCK(devvp, 0, p); + if (error != 0) return (error); if (VOP_IOCTL(devvp, DIOCGPART, (caddr_t)&dpart, FREAD, NOCRED, p) != 0) size = DEV_BSIZE; Index: isofs/cd9660/cd9660_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/isofs/cd9660/cd9660_vfsops.c,v retrieving revision 1.67 diff -u -r1.67 cd9660_vfsops.c --- cd9660_vfsops.c 1999/11/01 23:57:25 1.67 +++ cd9660_vfsops.c 1999/11/02 06:20:26 @@ -296,8 +296,11 @@ if ((error = vinvalbuf(devvp, V_SAVE, p->p_ucred, p, 0, 0))) return (error); - if ((error = VOP_OPEN(devvp, FREAD, FSCRED, p))) + error = VOP_OPEN(devvp, FREAD, FSCRED, p); + VOP_UNLOCK(devvp, 0, p); + if (error != 0) return error; + needclose = 1; /* This is the "logical sector size". The standard says this Index: kern/vfs_subr.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v retrieving revision 1.232 diff -u -r1.232 vfs_subr.c --- vfs_subr.c 1999/10/29 18:08:55 1.232 +++ vfs_subr.c 1999/10/31 15:57:32 @@ -2870,7 +2870,7 @@ vn_isdisk(vp) struct vnode *vp; { - if (vp->v_type != VBLK) + if (vp->v_type != VBLK && vp->v_type != VCHR) return (0); if (!devsw(vp->v_rdev)) return (0); Index: miscfs/specfs/spec_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v retrieving revision 1.125 diff -u -r1.125 spec_vnops.c --- spec_vnops.c 1999/11/07 15:09:59 1.125 +++ spec_vnops.c 1999/11/07 15:29:29 @@ -68,10 +68,8 @@ static int spec_poll __P((struct vop_poll_args *)); static int spec_print __P((struct vop_print_args *)); static int spec_read __P((struct vop_read_args *)); -static int spec_bufread __P((struct vop_read_args *)); static int spec_strategy __P((struct vop_strategy_args *)); static int spec_write __P((struct vop_write_args *)); -static int spec_bufwrite __P((struct vop_write_args *)); vop_t **spec_vnodeop_p; static struct vnodeopv_entry_desc spec_vnodeop_entries[] = { @@ -142,8 +140,8 @@ } */ *ap; { struct proc *p = ap->a_p; - struct vnode *bvp, *vp = ap->a_vp; - dev_t bdev, dev = vp->v_rdev; + struct vnode *vp = ap->a_vp; + dev_t dev = vp->v_rdev; int error; struct cdevsw *dsw; const char *cp; @@ -162,61 +160,43 @@ if (!dev->si_iosize_max) dev->si_iosize_max = DFLTPHYS; - switch (vp->v_type) { - case VCHR: - if (ap->a_cred != FSCRED && (ap->a_mode & FWRITE)) { - /* - * When running in very secure mode, do not allow - * opens for writing of any disk character devices. - */ - if (securelevel >= 2 - && dsw->d_bmaj != -1 - && (dsw->d_flags & D_TYPEMASK) == D_DISK) - return (EPERM); - /* - * When running in secure mode, do not allow opens - * for writing of character - * devices whose corresponding block devices are - * currently mounted. - */ - if (securelevel >= 1) { - if ((bdev = chrtoblk(dev)) != NODEV && - vfinddev(bdev, VBLK, &bvp) && - bvp->v_usecount > 0 && - (error = vfs_mountedon(bvp))) - return (error); - } - } - if ((dsw->d_flags & D_TYPEMASK) == D_TTY) - vp->v_flag |= VISTTY; - VOP_UNLOCK(vp, 0, p); - error = (*dsw->d_open)(dev, ap->a_mode, S_IFCHR, p); - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); - break; - case VBLK: + /* + * XXX: Disks get special billing here, but it is mostly wrong. + * XXX: diskpartitions can overlap and the real checks should + * XXX: take this into account, and consequently they need to + * XXX: live in the diskslicing code. Some checks do. + */ + if (vn_isdisk(vp) && ap->a_cred != FSCRED && (ap->a_mode & FWRITE)) { /* - * When running in very secure mode, do not allow - * opens for writing of any disk block devices. + * Never allow opens for write if the device is mounted R/W */ - if (securelevel >= 2 && ap->a_cred != FSCRED && - (ap->a_mode & FWRITE) && - (dsw->d_flags & D_TYPEMASK) == D_DISK) + if (vp->v_specmountpoint != NULL && + !(vp->v_specmountpoint->mnt_flag & MNT_RDONLY)) + return (EBUSY); + + /* + * When running in secure mode, do not allow opens + * for writing if the device is mounted + */ + if (securelevel >= 1 && vp->v_specmountpoint != NULL) return (EPERM); /* - * Do not allow opens of block devices that are - * currently mounted. + * When running in very secure mode, do not allow + * opens for writing of any devices. */ - error = vfs_mountedon(vp); - if (error) - return (error); - error = (*dsw->d_open)(dev, ap->a_mode, S_IFBLK, p); - break; - default: - error = ENXIO; - break; + if (securelevel >= 2) + return (EPERM); } + /* XXX: Special casing of ttys for deadfs. Probably redundant */ + if (dsw->d_flags & D_TTY) + vp->v_flag |= VISTTY; + + VOP_UNLOCK(vp, 0, p); + error = (*dsw->d_open)(dev, ap->a_mode, S_IFCHR, p); + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); + if (error) return (error); @@ -254,123 +234,29 @@ spec_read(ap) struct vop_read_args /* { struct vnode *a_vp; - struct uio *a_uio; - int a_ioflag; - struct ucred *a_cred; - } */ *ap; -{ - struct vnode *vp = ap->a_vp; - struct uio *uio = ap->a_uio; - struct proc *p = uio->uio_procp; - int error = 0; - -#ifdef DIAGNOSTIC - if (uio->uio_rw != UIO_READ) - panic("spec_read mode"); - if (uio->uio_segflg == UIO_USERSPACE && uio->uio_procp != curproc) - panic("spec_read proc"); -#endif - if (uio->uio_resid == 0) - return (0); - - if (vp->v_type == VCHR || (bdev_buffered == 0)) { - VOP_UNLOCK(vp, 0, p); - error = (*devsw(vp->v_rdev)->d_read) - (vp->v_rdev, uio, ap->a_ioflag); - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); - return (error); - } else { - return (spec_bufread(ap)); - } -} - - -/* Vnode op for buffered read */ -/* ARGSUSED */ -static int -spec_bufread(ap) - struct vop_read_args /* { - struct vnode *a_vp; struct uio *a_uio; - int a_ioflag; + int a_ioflag; struct ucred *a_cred; } */ *ap; { - struct vnode *vp = ap->a_vp; - struct uio *uio = ap->a_uio; - struct proc *p = uio->uio_procp; - struct buf *bp; - daddr_t bn, nextbn; - long bsize, bscale; - struct partinfo dpart; - int n, on; - d_ioctl_t *ioctl; - int error = 0; - int seqcount = ap->a_ioflag >> 16; + struct vnode *vp; + struct proc *p; + struct uio *uio; dev_t dev; + int error; - if (uio->uio_offset < 0) - return (EINVAL); + vp = ap->a_vp; dev = vp->v_rdev; + uio = ap->a_uio; + p = uio->uio_procp; - /* - * Calculate block size for block device. The block size must - * be larger then the physical minimum. - */ - - bsize = vp->v_rdev->si_bsize_best; - if (bsize < vp->v_rdev->si_bsize_phys) - bsize = vp->v_rdev->si_bsize_phys; - if (bsize < BLKDEV_IOSIZE) - bsize = BLKDEV_IOSIZE; - - if ((ioctl = devsw(dev)->d_ioctl) != NULL && - (*ioctl)(dev, DIOCGPART, (caddr_t)&dpart, FREAD, p) == 0 && - dpart.part->p_fstype == FS_BSDFFS && - dpart.part->p_frag != 0 && dpart.part->p_fsize != 0) - bsize = dpart.part->p_frag * dpart.part->p_fsize; - bscale = btodb(bsize); - do { - bn = btodb(uio->uio_offset) & ~(bscale - 1); - on = uio->uio_offset % bsize; - if (seqcount > 1) { - nextbn = bn + bscale; - error = breadn(vp, bn, (int)bsize, &nextbn, - (int *)&bsize, 1, NOCRED, &bp); - } else { - error = bread(vp, bn, (int)bsize, NOCRED, &bp); - } + if (uio->uio_resid == 0) + return (0); - /* - * Figure out how much of the buffer is valid relative - * to our offset into the buffer, which may be negative - * if we are beyond the EOF. - * - * The valid size of the buffer is based on - * bp->b_bcount (which may have been truncated by - * dscheck or the device) minus bp->b_resid, which - * may be indicative of an I/O error if non-zero. - */ - if (error == 0) { - n = bp->b_bcount - on; - if (n < 0) { - error = EINVAL; - } else { - n = min(n, bp->b_bcount - bp->b_resid - on); - if (n < 0) - error = EIO; - } - } - if (error) { - brelse(bp); - return (error); - } - n = min(n, uio->uio_resid); - error = uiomove((char *)bp->b_data + on, n, uio); - brelse(bp); - } while (error == 0 && uio->uio_resid > 0 && n != 0); + VOP_UNLOCK(vp, 0, p); + error = (*devsw(dev)->d_read) (dev, uio, ap->a_ioflag); + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); return (error); - /* NOTREACHED */ } /* @@ -381,130 +267,25 @@ spec_write(ap) struct vop_write_args /* { struct vnode *a_vp; - struct uio *a_uio; - int a_ioflag; - struct ucred *a_cred; - } */ *ap; -{ - struct vnode *vp = ap->a_vp; - struct uio *uio = ap->a_uio; - struct proc *p = uio->uio_procp; - int error = 0; - -#ifdef DIAGNOSTIC - if (uio->uio_rw != UIO_WRITE) - panic("spec_write mode"); - if (uio->uio_segflg == UIO_USERSPACE && uio->uio_procp != curproc) - panic("spec_write proc"); -#endif - - if (vp->v_type == VCHR || (bdev_buffered == 0)) { - VOP_UNLOCK(vp, 0, p); - error = (*devsw(vp->v_rdev)->d_write) - (vp->v_rdev, uio, ap->a_ioflag); - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); - return (error); - } else { - return (spec_bufwrite(ap)); - } -} - - -/* Vnode op for buffered write */ -/* ARGSUSED */ -static int -spec_bufwrite(ap) - struct vop_write_args /* { - struct vnode *a_vp; struct uio *a_uio; - int a_ioflag; + int a_ioflag; struct ucred *a_cred; } */ *ap; { - struct vnode *vp = ap->a_vp; - struct uio *uio = ap->a_uio; - struct proc *p = uio->uio_procp; - struct buf *bp; - daddr_t bn; - int bsize, blkmask; - struct partinfo dpart; - register int n, on; - int error = 0; - - if (uio->uio_resid == 0) - return (0); - if (uio->uio_offset < 0) - return (EINVAL); - - /* - * Calculate block size for block device. The block size must - * be larger then the physical minimum. - */ - bsize = vp->v_rdev->si_bsize_best; - if (bsize < vp->v_rdev->si_bsize_phys) - bsize = vp->v_rdev->si_bsize_phys; - if (bsize < BLKDEV_IOSIZE) - bsize = BLKDEV_IOSIZE; - - if ((*devsw(vp->v_rdev)->d_ioctl)(vp->v_rdev, DIOCGPART, - (caddr_t)&dpart, FREAD, p) == 0) { - if (dpart.part->p_fstype == FS_BSDFFS && - dpart.part->p_frag != 0 && dpart.part->p_fsize != 0) - bsize = dpart.part->p_frag * - dpart.part->p_fsize; - } - blkmask = btodb(bsize) - 1; - do { - bn = btodb(uio->uio_offset) & ~blkmask; - on = uio->uio_offset % bsize; + struct vnode *vp; + struct proc *p; + struct uio *uio; + dev_t dev; + int error; - /* - * Calculate potential request size, determine - * if we can avoid a read-before-write. - */ - n = min((unsigned)(bsize - on), uio->uio_resid); - if (n == bsize) - bp = getblk(vp, bn, bsize, 0, 0); - else - error = bread(vp, bn, bsize, NOCRED, &bp); + vp = ap->a_vp; + dev = vp->v_rdev; + uio = ap->a_uio; + p = uio->uio_procp; - /* - * n is the amount of effective space in the buffer - * that we wish to write relative to our offset into - * the buffer. We have to truncate it to the valid - * size of the buffer relative to our offset into - * the buffer (which may end up being negative if - * we are beyond the EOF). - * - * The valid size of the buffer is based on - * bp->b_bcount (which may have been truncated by - * dscheck or the device) minus bp->b_resid, which - * may be indicative of an I/O error if non-zero. - * - * XXX In a newly created buffer, b_bcount == bsize - * and, being asynchronous, we have no idea of the - * EOF. - */ - if (error == 0) { - n = min(n, bp->b_bcount - on); - if (n < 0) { - error = EINVAL; - } else { - n = min(n, bp->b_bcount - bp->b_resid - on); - if (n < 0) - error = EIO; - } - } - if (error) { - brelse(bp); - return (error); - } - error = uiomove((char *)bp->b_data + on, n, uio); - if (n + on == bsize) - bawrite(bp); - else - bdwrite(bp); - } while (error == 0 && uio->uio_resid > 0 && n != 0); + VOP_UNLOCK(vp, 0, p); + error = (*devsw(dev)->d_write) (dev, uio, ap->a_ioflag); + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); return (error); } @@ -523,20 +304,11 @@ struct proc *a_p; } */ *ap; { - dev_t dev = ap->a_vp->v_rdev; - - switch (ap->a_vp->v_type) { + dev_t dev; - case VCHR: - return ((*devsw(dev)->d_ioctl)(dev, ap->a_command, - ap->a_data, ap->a_fflag, ap->a_p)); - case VBLK: - return ((*devsw(dev)->d_ioctl)(dev, ap->a_command, - ap->a_data, ap->a_fflag, ap->a_p)); - default: - panic("spec_ioctl"); - /* NOTREACHED */ - } + dev = ap->a_vp->v_rdev; + return ((*devsw(dev)->d_ioctl)(dev, ap->a_command, + ap->a_data, ap->a_fflag, ap->a_p)); } /* ARGSUSED */ @@ -550,17 +322,11 @@ } */ *ap; { register dev_t dev; - - switch (ap->a_vp->v_type) { - case VCHR: - dev = ap->a_vp->v_rdev; - return (*devsw(dev)->d_poll)(dev, ap->a_events, ap->a_p); - default: - return (vop_defaultop((struct vop_generic_args *)ap)); - - } + dev = ap->a_vp->v_rdev; + return (*devsw(dev)->d_poll)(dev, ap->a_events, ap->a_p); } + /* * Synch buffers associated with a block device */ @@ -574,16 +340,16 @@ struct proc *a_p; } */ *ap; { - register struct vnode *vp = ap->a_vp; - register struct buf *bp; + struct vnode *vp = ap->a_vp; + struct buf *bp; struct buf *nbp; int s; - if (vp->v_type == VCHR) - return (0); /* - * Flush all dirty buffers associated with a block device. + * Flush all dirty buffers associated with a disk device. */ + if (!vn_isdisk(vp)) + return (0); loop: s = splbio(); for (bp = TAILQ_FIRST(&vp->v_dirtyblkhd); bp; bp = nbp) { @@ -669,6 +435,10 @@ struct cdevsw *bsw; struct buf *bp; + /* + * XXX: This assumes that strategy does the deed right away. + * XXX: this may not be TRTTD. + */ bsw = devsw(ap->a_vp->v_rdev); if ((bsw->d_flags & D_CANFREE) == 0) return (0); @@ -706,7 +476,7 @@ *ap->a_vpp = vp; if (ap->a_bnp != NULL) *ap->a_bnp = ap->a_bn; - if (vp->v_type == VBLK && vp->v_mount != NULL) + if (vp->v_mount != NULL) runp = runb = MAXBSIZE / vp->v_mount->mnt_stat.f_iosize; if (ap->a_runp != NULL) *ap->a_runp = runp; @@ -731,46 +501,20 @@ struct vnode *vp = ap->a_vp; struct proc *p = ap->a_p; dev_t dev = vp->v_rdev; - int mode, error; - switch (vp->v_type) { - - case VCHR: - /* - * Hack: a tty device that is a controlling terminal - * has a reference from the session structure. - * We cannot easily tell that a character device is - * a controlling terminal, unless it is the closing - * process' controlling terminal. In that case, - * if the reference count is 2 (this last descriptor - * plus the session), release the reference from the session. - */ - if (vcount(vp) == 2 && p && (vp->v_flag & VXLOCK) == 0 && - vp == p->p_session->s_ttyvp) { - vrele(vp); - p->p_session->s_ttyvp = NULL; - } - mode = S_IFCHR; - break; - - case VBLK: - if (bdev_buffered) { - /* - * On last close of a block device (that isn't mounted) - * we must invalidate any in core blocks, so that - * we can, for instance, change floppy disks. - */ - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); - error = vinvalbuf(vp, V_SAVE, ap->a_cred, p, 0, 0); - VOP_UNLOCK(vp, 0, p); - if (error) - return (error); - } - mode = S_IFBLK; - break; - - default: - panic("spec_close: not special"); + /* + * Hack: a tty device that is a controlling terminal + * has a reference from the session structure. + * We cannot easily tell that a character device is + * a controlling terminal, unless it is the closing + * process' controlling terminal. In that case, + * if the reference count is 2 (this last descriptor + * plus the session), release the reference from the session. + */ + if (vcount(vp) == 2 && p && (vp->v_flag & VXLOCK) == 0 && + vp == p->p_session->s_ttyvp) { + vrele(vp); + p->p_session->s_ttyvp = NULL; } /* * We do not want to really close the device if it @@ -788,7 +532,7 @@ } else if (vcount(vp) > 1) { return (0); } - return (devsw(dev)->d_close(dev, ap->a_fflag, mode, p)); + return (devsw(dev)->d_close(dev, ap->a_fflag, S_IFCHR, p)); } /* @@ -882,7 +626,7 @@ * block device is mounted. However, we can use v_rdev. */ - if (vp->v_type == VBLK) + if (vn_isdisk(vp)) blksiz = vp->v_rdev->si_bsize_phys; else blksiz = DEV_BSIZE; Index: msdosfs/msdosfs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/msdosfs/msdosfs_vfsops.c,v retrieving revision 1.53 diff -u -r1.53 msdosfs_vfsops.c --- msdosfs_vfsops.c 1999/09/20 23:27:57 1.53 +++ msdosfs_vfsops.c 1999/10/31 15:14:10 @@ -383,6 +383,7 @@ ronly = (mp->mnt_flag & MNT_RDONLY) != 0; error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); + VOP_UNLOCK(devvp, 0, p); if (error) return (error); Index: ntfs/ntfs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ntfs/ntfs_vfsops.c,v retrieving revision 1.15 diff -u -r1.15 ntfs_vfsops.c --- ntfs_vfsops.c 1999/10/29 18:09:12 1.15 +++ ntfs_vfsops.c 1999/10/31 15:13:47 @@ -423,6 +423,7 @@ ronly = (mp->mnt_flag & MNT_RDONLY) != 0; error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); + VOP_UNLOCK(devvp, 0, p); if (error) return (error); Index: ufs/ffs/ffs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.110 diff -u -r1.110 ffs_vfsops.c --- ffs_vfsops.c 1999/11/03 12:05:37 1.110 +++ ffs_vfsops.c 1999/11/03 13:10:45 @@ -602,6 +602,7 @@ ronly = (mp->mnt_flag & MNT_RDONLY) != 0; error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); + VOP_UNLOCK(devvp, 0, p); if (error) return (error); if (devvp->v_rdev->si_iosize_max > mp->mnt_iosize_max) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 8:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id DB8A014D24 for ; Sun, 7 Nov 1999 08:20:20 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1643 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sun, 7 Nov 1999 17:20:19 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 6ED8E3896; Sun, 7 Nov 1999 17:20:19 +0100 (MET) Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: from Leif Neland at "Nov 7, 99 03:16:48 pm" To: leifn@neland.dk (Leif Neland) Date: Sun, 7 Nov 1999 17:20:19 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 770 Message-Id: <19991107162019.6ED8E3896@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Leif Neland: > > PnP support for i4b in -current was disabled during the conversion of > > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > > cards i4b supports do no longer work. > > > Anybody working on re-enabling it, and if so, any time-horisonts? Yes, no. I still hope documentation for the new-bus, new-pnp architecture will be made available at sufficient time before 4.0-RELEASE code freeze. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 9:12:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id 2129A14A14 for ; Sun, 7 Nov 1999 09:12:41 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Sun, 7 Nov 1999 18:12:20 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id SAA11818; Sun, 7 Nov 1999 18:08:57 +0100 (CET) (envelope-from tanis) Date: Sun, 7 Nov 1999 18:08:57 +0100 From: German Tischler To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized Message-ID: <19991107180857.A11257@gaspode.franken.de> References: <19991107130146.2B72E38E2@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Leif Neland on Sun, Nov 07, 1999 at 03:16:48PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 03:16:48PM +0100, Leif Neland wrote: > > PnP support for i4b in -current was disabled during the conversion of > > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > > cards i4b supports do no longer work. > > > Anybody working on re-enabling it, and if so, any time-horisonts? Depends on which card you use. I have attempted to do the conversion for some cards. You are welcome to test it, but don't expect it to work out of the box, I don't have the hardware to test it. It works for the hardware I have access to. If the code will be brought into i4b at all, it will not be before the i4b-PCI card code has been converted too and the concept and code is sophisticated enough for Hellmuth to accept it (and from what he wrote before, that won't be before there is other documentation than RTSL for the newbus system) . Some other people have shown interest in converting the PCI code. If it takes time I won't blame them, I don't have any spare time until mid january either. -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 9:27:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id 5D88C14A14 for ; Sun, 7 Nov 1999 09:27:30 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Sun, 7 Nov 1999 18:27:15 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id SAA12121; Sun, 7 Nov 1999 18:19:51 +0100 (CET) (envelope-from tanis) Date: Sun, 7 Nov 1999 18:19:51 +0100 From: German Tischler To: "D. Rock" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized Message-ID: <19991107181951.A11877@gaspode.franken.de> References: <19991107130146.2B72E38E2@hcswork.hcs.de> <38259463.FDEA7F45@dead-end.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38259463.FDEA7F45@dead-end.net>; from D. Rock on Sun, Nov 07, 1999 at 04:01:55PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 04:01:55PM +0100, D. Rock wrote: > Any hints when i4b will be converted to new-bus? The code is in stale > condition for almost 3 months now. > > To the original poster: > > I also have an ISDN PnP card (SedlBauer WinSpeed). In order to get it > run on -current, I did the following: There is already code for the SedlBauer (and I know it works because I have one.) Check out the url I mentioned on i4b-dev. > One note: The device doesn't get reset properly during reboot. I don't know > if this a general problem with the driver or just a result from my hacks. > If I reboot I have to manually turn off/on the machine. I have never seen this behaviour here, neither before nor after the conversion. You cannot expect the card to be reset, if you remove the reset code (which is normally in the attach routine). -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 9:34:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 37AF514C1C for ; Sun, 7 Nov 1999 09:34:26 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kDgK-0000HT-00; Sat, 06 Nov 1999 16:47:32 -0500 Date: Sat, 6 Nov 1999 16:47:32 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Dmitrij Tejblum Cc: FreeBSD Current Users' list Subject: Re: Serious locking problem in CURRENT In-Reply-To: <199911062057.XAA03228@tejblum.pp.ru> 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, 6 Nov 1999, Dmitrij Tejblum wrote: > Brian Fundakowski Feldman wrote: > > There were zero comments about what order things happen in; in fact, > > the ordering in this case is Just Plain Lame (TM). It's much more > > correct to explicitly check for fp->f_count == 1. > > Not sure what you mean. The commit clearly states that POSIX and BSD > locking intentionally handled in different ways here. Frankly, I see > nothing lame in the ordering. The second VOP_ADVLOCK just should be > moved to fdrop(). Yes, but you implied that there was some part of the commenting that I must have missed in rev.1.68, but there was nothing about that. I think I'll get an okay from bruce and move the unlock to fdrop(); I have still been pondering which is more correct, actually. > > > > BTW, I have another little concern with that commit: It make possible for > > > last close() of a file descriptor to return 0 instead of the error from > > > VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. > > When a process do closef() on a descriptor "held" by another process > (by fhold(), e.g. the process do read() on the descriptor), it will > just return 0 without the call to fo_close(). Then, when the other > process drop the descriptor, fdrop() call fo_close() but the error is > thrown away. No? Yes, this is what I thought you could have meant. But would you rather lose that error in a corner case or do locking on the fd/fdtable or just let the system crash in that case? I'm open for a better solution. > > Dima > > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 7 9:36:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 8136E14BD8; Sun, 7 Nov 1999 09:36:13 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.52]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB25FE; Sun, 7 Nov 1999 18:36:12 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id SAA47554; Sun, 7 Nov 1999 18:17:32 +0100 (CET) (envelope-from asmodai) Date: Sun, 7 Nov 1999 18:17:32 +0100 From: Jeroen Ruigrok/Asmodai To: Andrzej Bialecki Cc: sos@freebsd.org, freebsd-current@freebsd.org Subject: Re: libvgl - status and perspectives Message-ID: <19991107181732.B41126@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991106 04:01], Andrzej Bialecki (abial@webgiro.com) wrote: >Today I noticed accidentally that either libvgl is broken, or the demo >program does something wrong - the mouse cursor doesn't move. > >But this brings more general question regarding console graphics library. >As it is today, libvgl is almost useless due to very limited set of >functions. There were discussions whether to port SVGAlib or GGI. Do you >know if someone is working/planning to work on it? libggi has more support for FreeBSD than svgalib has and it also seems to be preferred over svgalib due to security hassles and all that. So you might want to try that route. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best In every stone sleeps a crystal... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 10: 5:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 15BAD14E52 for ; Sun, 7 Nov 1999 10:05:25 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA28474 for current@freebsd.org; Sun, 7 Nov 1999 19:05:18 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E5AE68711; Sun, 7 Nov 1999 16:37:18 +0100 (CET) Date: Sun, 7 Nov 1999 16:37:18 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107163718.A15753@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <199911061929.NAA26145@free.pcs> <19991107020102.A9992@keltia.freenix.fr> <19991107115106.A15177@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991107115106.A15177@walton.maths.tcd.ie> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David Malone: > But if the real master process forks and then it's child closes the fd > which the lock was on, then the master process will have lost it's lock. > Is this likely? Does the real master fork children to do stuff? All the time. "master" is an inetd-like daemon which spawn children according to master.cf. Everything run by Postfix is a child of "master"... I see your point and that's likely what happen. You're confirming what I thought about locking brokeness. That's bad. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 10:10:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E2F014FA8 for ; Sun, 7 Nov 1999 10:05:49 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kBTD-000EKJ-00; Sat, 06 Nov 1999 14:25:51 -0500 Date: Sat, 6 Nov 1999 14:25:50 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Dmitrij Tejblum Cc: David Malone , Ollivier Robert , FreeBSD Current Users' list Subject: Re: Serious locking problem in CURRENT In-Reply-To: <199911061921.WAA02732@tejblum.pp.ru> 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, 6 Nov 1999, Dmitrij Tejblum wrote: > David Malone wrote: > > A child process seems to be able to let go of a parent's lock on > > 4.0 by closing a file discriptor, the same doesn't seem to be true > > on 3.3. > > So, apparently, it was broken in rev. 1.68 of kern_descript.c. (Another > example that comments (in closef() in this case) serve no purpose :-/). There were zero comments about what order things happen in; in fact, the ordering in this case is Just Plain Lame (TM). It's much more correct to explicitly check for fp->f_count == 1. > > BTW, I have another little concern with that commit: It make possible for > last close() of a file descriptor to return 0 instead of the error from > VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. I don't see where you're getting that from at all. > > Dima > > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 7 10:31: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id DB12214A07 for ; Sun, 7 Nov 1999 10:30:56 -0800 (PST) (envelope-from jhs@jhs.muc.de) Received: (qmail 16797 invoked from network); 7 Nov 1999 18:32:46 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 7 Nov 1999 18:32:46 -0000 Received: (from jhs@localhost) by jhs.muc.de (8.9.3/8.9.3) id RAA17819; Sun, 7 Nov 1999 17:07:31 GMT (envelope-from jhs) Date: Sun, 7 Nov 1999 17:07:31 GMT Message-Id: <199911071707.RAA17819@jhs.muc.de> To: freebsd-current@freebsd.org Subject: new home directory for daemon From: "Julian Stacey" Reply-To: "Julian Stacey" Organization: Vector Systems Ltd - Unix & Internet consultancy X-Net: jhs@muc.de www.jhs.muc.de www.freebsd.org/~jhs/ bim.bsn.com/~jhs/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Problem: ~daemon/tmp should not be the same directory as ~root/tmp/ Suggestion: new home directory: daemon:*:1:1::0:0:Owner of many system processes:/daemon:/sbin/nologin + extend BSD.root.dist to create ~daemon/tmp Given existing current/src/: etc/master.passwd: root::0:0::0:0:Charlie &:/root:/bin/csh daemon:*:1:1::0:0:Owner of many system processes:/root:/sbin/nologin etc/group: wheel:*:0:root daemon:*:1:daemon etc/BSD.root.dist: .. root .. (but no root/tmp created) So assuming a manually created secure & private /root/tmp with owner root, group wheel, mode 700 This was just posted to the list, rather than made a send-pr, as I guess there may be better solutions ... Any Comments / Improvements ? -- Julian Stacey www.freebsd.org/~jhs/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 10:32:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id B11FF14A21 for ; Sun, 7 Nov 1999 10:32:18 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Sun, 7 Nov 1999 19:32:08 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id TAA13949; Sun, 7 Nov 1999 19:28:44 +0100 (CET) (envelope-from tanis) Date: Sun, 7 Nov 1999 19:28:44 +0100 From: German Tischler To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sv: Dr Neuhaus niccy go not recognized Message-ID: <19991107192844.A13696@gaspode.franken.de> References: <19991107130146.2B72E38E2@hcswork.hcs.de> <19991107180857.A11257@gaspode.franken.de> <014601bf2945$7de36500$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <014601bf2945$7de36500$0e00a8c0@neland.dk>; from Leif Neland on Sun, Nov 07, 1999 at 06:27:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: > I'd like to test, So how do I proceed from here? Get the latest i4b-dev snapshot (00.83.11), get my patches from http://www.mayn.franken.de/home/tanis/i4b-11.tar.gz, get a recent current source tree, unpack i4b, unpack the layer1 patches over it, use the overinstall script, use device isic0 in your kernel config file (no at isa? or similiar). Compile the userland programs and install them, build a kernel and see if it works, and tell me what goes wrong. -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 10:41:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2378214C01 for ; Sun, 7 Nov 1999 10:41:47 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Nov 1999 18:41:46 +0000 (GMT) Date: Sun, 7 Nov 1999 18:41:46 +0000 From: David Malone To: Ben Smithurst Cc: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107184146.A22208@walton.maths.tcd.ie> References: <199911061929.NAA26145@free.pcs> <19991107112458.A14670@walton.maths.tcd.ie> <19991107142826.A2118@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991107142826.A2118@strontium.scientia.demon.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The lock doesn't seem to be released until *explicitly* released, like > the manual page says. I don't think closing the descriptor counts as > an explicit unlock, though I am probably wrong. Run this program, > you'll see the parent still has the lock. Change close(fd) to flock(fd, > LOCK_UN) and you'll see it doesn't. It's possible I've misunderstood > something though. On -current it seems to be unlocking regardless - which I think it the problem. If you have to explicitly unlock then that seems fine. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 11:21:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91]) by hub.freebsd.org (Postfix) with ESMTP id 454EE14C87 for ; Sun, 7 Nov 1999 11:21: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.3/8.8.8) with ESMTP id LAA13326; Sun, 7 Nov 1999 11:12:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911071912.LAA13326@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Thierry Herbelot , current@FreeBSD.ORG Subject: Re: stuck with ~year old current In-reply-to: Your message of "Sun, 07 Nov 1999 21:16:32 +0900." <38256DA0.F684B854@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 11:12:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > "We do not support upgrading to -current from anything else than the > > > latest -stable." > > > > Does this still hold after the recent signal changes ? > > > > TfH > > > > (I assume Yes, if one first upgrade the kernel, then the world) > > You assume correctly. -stable loader can load -current kernel. Well, > it could until very recently. I don't know if the new stuff Mike is > doing will introduce any incompatibility. The last incompatibility was around March or so, when the load address of the kernel changed. Anything postdating that is basically equi-functional. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Sun Nov 7 11:35:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 0525614CC9 for ; Sun, 7 Nov 1999 11:35:30 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA60044 for current@FreeBSD.org; Sun, 7 Nov 1999 21:35:29 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911071935.VAA60044@zibbi.mikom.csir.co.za> Subject: Re: doscmd broken on current? fixed In-Reply-To: <199911071301.PAA54812@zibbi.mikom.csir.co.za> from John Hay at "Nov 7, 1999 03:01:40 pm" To: current@FreeBSD.org Date: Sun, 7 Nov 1999 21:35:29 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (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 Ok, with these patches doscmd is working for me again. I can boot dos and run the topspeed C compiler like I used to a few months ago. If nobody has any complaints I'll commit it. I'm just not 100% sure about the patch to doscmd.c and would like if someone with more knowledge about the signal stuff would just look at it. There is just too many signal related functions and structures and it isn't always clear (to me at least) what should be filled in for whom. John -- John Hay -- John.Hay@mikom.csir.co.za Index: cwd.c =================================================================== RCS file: /home/ncvs/src/usr.bin/doscmd/cwd.c,v retrieving revision 1.5 diff -u -r1.5 cwd.c --- cwd.c 1999/10/12 22:20:18 1.5 +++ cwd.c 1999/11/07 18:59:06 @@ -198,7 +198,7 @@ u_char *np; Path_t *d; u_char tmppath[1024]; - u_char snewpath = newpath; + u_char *snewpath = newpath; if (where[0] != '\0' && where[1] == ':') { drive = drlton(*where); @@ -253,7 +253,7 @@ } else { if (np[-1] != '\\') *np++ = '\\'; - while (*np = *dir++ && np - snewpath < 1023) + while ((*np = *dir++) && np - snewpath < 1023) ++np; } } Index: doscmd.c =================================================================== RCS file: /home/ncvs/src/usr.bin/doscmd/doscmd.c,v retrieving revision 1.11 diff -u -r1.11 doscmd.c --- doscmd.c 1999/10/13 23:48:35 1.11 +++ doscmd.c 1999/11/07 12:50:06 @@ -258,6 +258,7 @@ sigemptyset(&uc.uc_sigmask); sigaltstack(NULL, &uc.uc_stack); + uc.uc_mcontext.mc_onstack = uc.uc_stack.ss_flags; if (tmode) tracetrap(REGS); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 11:47:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91]) by hub.freebsd.org (Postfix) with ESMTP id EBA9414A09 for ; Sun, 7 Nov 1999 11:47:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA13498; Sun, 7 Nov 1999 11:38:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911071938.LAA13498@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hm@hcs.de Cc: leifn@neland.dk (Leif Neland), freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized In-reply-to: Your message of "Sun, 07 Nov 1999 17:20:19 +0100." <19991107162019.6ED8E3896@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 11:38:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From the keyboard of Leif Neland: > > > > PnP support for i4b in -current was disabled during the conversion of > > > -current to the new-bus/new-pnp architecture; as a result all PnP ISDN > > > cards i4b supports do no longer work. > > > > > Anybody working on re-enabling it, and if so, any time-horisonts? > > Yes, no. > > I still hope documentation for the new-bus, new-pnp architecture will be > made available at sufficient time before 4.0-RELEASE code freeze. There's as much or more documentation on the current architecture as there was on the old one. Sitting on your hands and whining about there being no 2m-long shelf of ring-bound manuals isn't an excuse for not getting on and doing things like they ought to be done. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Sun Nov 7 12: 7:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 75E7514D33 for ; Sun, 7 Nov 1999 12:07:43 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA01702; Sun, 7 Nov 1999 21:04:31 +0100 (CET) Message-Id: <199911072004.VAA01702@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 07 Nov 1999 20:36:05 +0900." <38256425.7AD008ED@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 21:04:31 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: >Gary Jennejohn wrote: >> >> Any idea why GCC 2.95.2 produces so much more code ? > >Mmmm... O'Brien, could you make sure the space-critical code in >sys/boot compiles ok? > I still have GCC 2.95.2 installed. This is what I get in /sys/boot: ===> i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c boot2.c (cd /usr/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.01 size=700 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=15c0 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1ec0 text=200 data=1cc0 org=0 entry=0 -192 bytes available ^^^^^^^^^^^^^^^^^^^^ --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 12:36:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 62D3E14D08; Sun, 7 Nov 1999 12:36:45 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id OAA30142; Sun, 7 Nov 1999 14:36:44 -0600 (CST) Date: Sun, 7 Nov 1999 14:36:44 -0600 (CST) From: Steve Price To: marcel@freebsd.org Cc: freebsd-current@freebsd.org Subject: new sigaction struct 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 Marcel, Just curious as to what the motivation for re-ordering the sa_flags and sa_mask members in sigaction were? The manpage still describes the old order BTW. My Alpha box has been limping through a package build and I've noticed a number of ports that seem to be falling over for signal-related changes. One in particular would be the rawio port which expects sa_mask to be before sa_flags in struct sigaction. Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 13:53:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id E685114C4A for ; Sun, 7 Nov 1999 13:53:09 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id NAA74943; Sun, 7 Nov 1999 13:52:50 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Sun, 7 Nov 1999 13:52:50 -0800 (PST) From: Vincent Poy To: David Malone Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: Serious locking problem in CURRENT In-Reply-To: <19991107184146.A22208@walton.maths.tcd.ie> 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, 7 Nov 1999, David Malone wrote: > > The lock doesn't seem to be released until *explicitly* released, like > > the manual page says. I don't think closing the descriptor counts as > > an explicit unlock, though I am probably wrong. Run this program, > > you'll see the parent still has the lock. Change close(fd) to flock(fd, > > LOCK_UN) and you'll see it doesn't. It's possible I've misunderstood > > something though. > > On -current it seems to be unlocking regardless - which I think it the > problem. If you have to explicitly unlock then that seems fine. There is something broken in -CURRENT with file locking since I've experienced this with sendmail 8.9.3. I compared this to a 3.3-RELEASE machine running sendmail 8.9.3 and it doesn't exhibit the same problem. You can do a little test of the file locking, might be a bit tricky if you have a busy system, but it would be interesting to see the result: Run sendmail with -bd -q1m Send a message to an "unused" IP address on your local network, e.g. date | sendmail 'nobody@[123.123.123.123]' (substitute an appropriate IP address of course). This should have the (backgrounded) original sendmail process sitting waiting with the queue file locked for just over one minute, so you need to hurry a bit with the rest: Run 'mailq' - does this message have a '*' in the first column (it should)? Take the queue ID for the message - shown in the first column of mailq output (immediately following the '*', if any) - say XAA01234, and do a verbose queue run for just that ID: sendmail -v -qIXAA01234 (substituting the queue ID you got of course, i.e. -qI) - this should just print Running XAA03875 (sequence 1 of 1) XAA03875: locked and then exit - does it? From the above tests, the file locking does work in general. However, it could still be a race condition. Here's another test, which will be more of the sendmail situation: Create a little shell script #!/bin/sh sleep 300 cat > /tmp/message.$$ and an alias pointing to it: testalias: "|/path/to/script" - then set the daemon to run with -q1m, and send a single mail to "testalias". If the problem appears in this test, you should have (after 5 minutes) multiple /tmp/message.nnnnn (the nnnnn being process IDs) files, each containing the message you sent. If you check /tmp in 10 minutes, you will notice that some messages will overlap in -CURRENT of having the same message regenerated a few times while on 3.3-RELEASE, it will only show one /tmp/message.nnnnn file. And then just to repeat the test, do the following but this time send the single message to testalias with the command: sendmail -odq -oi testalias < messagefile It might also be worth testing with sendmail -odi -oi testalias < messagefile The last form will seem to hang until the message is delivered. If there is only one '/tmp/message.nnnnn' produced in each of these tests, it will suggest that your system is losing its locks over the fork made for delivery. With '-odq', the message is placed in the queue for later delivery attempts, and the queue run does not normally fork for delivery. With '-odi' it is delivered interactively without a fork. With neither of those operands, or with '-odb', there is a fork before delivery. On all of these tests, 3.3-RELEASE will generate only one /tmp/message.nnnnn while -CURRENT will generate multiple /tmp/message.nnnnn. My -CURRENT system is using sources as of 10/30/99 5:30AM PDT. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 16:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 44FA014EC5 for ; Sun, 7 Nov 1999 16:34:34 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-5.iptelecom.net.ua [212.9.226.5]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA07498 for ; Mon, 8 Nov 1999 02:37:17 +0200 (EET) Message-ID: <38261A44.F0451032@altavista.net> Date: Mon, 08 Nov 1999 02:33:08 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: rm error code on FAT Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody can explain why two absolutely identical attempts to remove unexistent files on UFS and FAT32 yields different error codes ("No such file or directory" and "Invalid argument" respectively)? This breaks "rm -f" behaviour, because instead of expected "0", "rm -f" on FAT returns error code instead. bash-2.03# mount /dev/ad0s2a on / (ufs, local, noatime, soft-updates, writes: sync 231 async 5542) procfs on /proc (procfs, local) /dev/ad0s1 on /mnt (msdos, local) bash-2.03# rm /tmp/*.no_such_files rm: /tmp/*.no_such_files: No such file or directory bash-2.03# rm /mnt/*.no_such_files rm: /mnt/*.no_such_files: Invalid argument -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 17: 7:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 78C9914C15; Sun, 7 Nov 1999 17:07:07 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:mkdF1obCx7DBI5E+x1AnGSKGNMtVroLB@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id KAA11536; Mon, 8 Nov 1999 10:06:53 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA20479; Mon, 8 Nov 1999 10:11:30 +0900 (JST) Message-Id: <199911080111.KAA20479@zodiac.mech.utsunomiya-u.ac.jp> To: Andrzej Bialecki Cc: sos@freebsd.org, freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: libvgl - status and perspectives In-reply-to: Your message of "Sat, 06 Nov 1999 02:41:06 +0100." References: Date: Mon, 08 Nov 1999 10:11:29 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Today I noticed accidentally that either libvgl is broken, or the demo >program does something wrong - the mouse cursor doesn't move. Oops, sos and I have developed a new version of libsvgl which can handle VESA modes in addition to the standard VGA graphics modes. But I haven't committed it to the source tree yet (yes, I should have done so weeks ago ;-( Anyway, if you are interested, I can send you a copy for testing. Kazu >But this brings more general question regarding console graphics library. >As it is today, libvgl is almost useless due to very limited set of >functions. There were discussions whether to port SVGAlib or GGI. Do you >know if someone is working/planning to work on it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 17:28:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 48117150F4; Sun, 7 Nov 1999 17:28:32 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kdYY-000C4l-00; Sun, 07 Nov 1999 20:25:14 -0500 Date: Sun, 7 Nov 1999 20:25:13 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Kazutaka YOKOTA Cc: Andrzej Bialecki , sos@freebsd.org, freebsd-current@freebsd.org Subject: Re: libvgl - status and perspectives In-Reply-To: <199911080111.KAA20479@zodiac.mech.utsunomiya-u.ac.jp> 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, 8 Nov 1999, Kazutaka YOKOTA wrote: > > Oops, sos and I have developed a new version of libsvgl which can > handle VESA modes in addition to the standard VGA graphics modes. > But I haven't committed it to the source tree yet (yes, I should have > done so weeks ago ;-( Commit, commit!! This would be so wonderful! > > Anyway, if you are interested, I can send you a copy for testing. > > Kazu > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 7 17:46:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from biohazard.wnet.com.br (biohazard.wnet.com.br [200.250.8.1]) by hub.freebsd.org (Postfix) with ESMTP id 609CF15116 for ; Sun, 7 Nov 1999 17:46:04 -0800 (PST) (envelope-from jg@wnet.com.br) Received: from wnet.com.br (pmaster1-23.wnet.com.br [200.250.8.151]) by biohazard.wnet.com.br (8.9.3/8.9.3) with ESMTP id XAA07308 for ; Sun, 7 Nov 1999 23:49:21 -0200 Message-ID: <38262B70.D56836D0@wnet.com.br> Date: Sun, 07 Nov 1999 23:46:24 -0200 From: jg X-Mailer: Mozilla 4.03 [pt] (Win95; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to know where I could find Nestea v3. Where I can find? And where I could find a program that has the same effect that the nestea or better. It helps me. THANK YOU!!!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 17:55:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from faith.cs.utah.edu (faith.cs.utah.edu [155.99.198.108]) by hub.freebsd.org (Postfix) with ESMTP id 7D04514F55 for ; Sun, 7 Nov 1999 17:55:39 -0800 (PST) (envelope-from danderse@faith.cs.utah.edu) Received: (from danderse@localhost) by faith.cs.utah.edu (8.9.3/8.9.3) id SAA07854; Sun, 7 Nov 1999 18:55:26 -0700 (MST) From: David G Andersen Message-Id: <199911080155.SAA07854@faith.cs.utah.edu> Subject: Re: help To: jg@wnet.com.br (jg) Date: Sun, 7 Nov 1999 18:55:26 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <38262B70.D56836D0@wnet.com.br> from "jg" at Nov 7, 99 11:46:24 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 Please note that you've mailed this to a freebsd specific mailing list which is designed for discussions of issues with freebsd-current. This is is not subtitled, "A reference for script-kiddie wannabies." Please insert 50c for your next attempt, and good day. (Translation: You've sent your question to an inappropriate mailing list, and you're not likely to get a good answer here, so go search at rootshell instead). Lo and behold, jg once said: > > I want to know where I could find Nestea v3. > Where I can find? > And where I could find a program that has the same effect that the > nestea or better. > It helps me. > > THANK YOU!!!!! > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- work: dga@lcs.mit.edu me: dga@pobox.com MIT Laboratory for Computer Science http://www.angio.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 18:35:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3BE0814BE4 for ; Sun, 7 Nov 1999 18:34:34 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kdw9-000C6Q-00; Sun, 07 Nov 1999 20:49:38 -0500 Date: Sun, 7 Nov 1999 20:49:37 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: jg Cc: current@FreeBSD.ORG Subject: Re: help In-Reply-To: <38262B70.D56836D0@wnet.com.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 Sun, 7 Nov 1999, jg wrote: > I want to know where I could find Nestea v3. > Where I can find? > And where I could find a program that has the same effect that the > nestea or better. > It helps me. > > THANK YOU!!!!! > FOD. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 7 19:19:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0C70215109 for ; Sun, 7 Nov 1999 19:19:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p138-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id OAA06681; Mon, 8 Nov 1999 14:24:38 +1100 Date: Mon, 8 Nov 1999 14:18:54 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: rm error code on FAT In-Reply-To: <38261A44.F0451032@altavista.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 Mon, 8 Nov 1999, Maxim Sobolev wrote: > Does anybody can explain why two absolutely identical attempts to remove > unexistent files on UFS and FAT32 yields different error codes ("No such > file or directory" and "Invalid argument" respectively)? This breaks "rm > -f" behaviour, because instead of expected "0", "rm -f" on FAT returns > error code instead. unlink("/mnt/*.no_such_files") on msdosfs returns EINVAL because the pathname contains the invalid character '*'. EINVAL used to be a documented errno for pathnames containing characters with their high bit set). This documentation should have been made filesystem- dependent instead of removing it. 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 7 20:39: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.ORG (ppp28-besancon.isdnet.net [195.154.11.235]) by hub.freebsd.org (Postfix) with ESMTP id 4A9F71505B for ; Sun, 7 Nov 1999 20:39:03 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id FAA18162; Mon, 8 Nov 1999 05:40:34 +0100 (MET) (envelope-from jmz@FreeBSD.ORG) Date: Mon, 8 Nov 1999 05:40:34 +0100 (MET) Message-Id: <199911080440.FAA18162@qix.jmz.org> From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: sh bug X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this in -current $ cat some_file | head I have to use ^C to regain control. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 7 21: 3:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.ORG (ppp28-besancon.isdnet.net [195.154.11.235]) by hub.freebsd.org (Postfix) with ESMTP id 2F72D14EE8; Sun, 7 Nov 1999 21:03:48 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id GAA18326; Mon, 8 Nov 1999 06:05:19 +0100 (MET) (envelope-from jmz@FreeBSD.ORG) Date: Mon, 8 Nov 1999 06:05:19 +0100 (MET) Message-Id: <199911080505.GAA18326@qix.jmz.org> From: Jean-Marc Zucconi To: jmz@FreeBSD.ORG Cc: current@FreeBSD.ORG In-reply-to: <199911080440.FAA18162@qix.jmz.org> (message from Jean-Marc Zucconi on Mon, 8 Nov 1999 05:40:34 +0100 (MET)) Subject: Re: sh bug X-Mailer: Emacs References: <199911080440.FAA18162@qix.jmz.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Jean-Marc Zucconi writes: > Try this in -current > $ cat some_file | head > I have to use ^C to regain control. ... and reverting to rev. 1.22 of eval.c fixes the problem. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 7 23: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DD2C615151; Sun, 7 Nov 1999 22:59:59 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p26-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.155]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA12719; Mon, 8 Nov 1999 15:59:50 +0900 (JST) Message-ID: <38266940.FC115D61@newsguy.com> Date: Mon, 08 Nov 1999 15:10:08 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG, Mike Smith , Robert Nordier , obrien@freebsd.org Subject: Re: show stopper for Gcc 2.95.2 conversion References: <199911072004.VAA01702@peedub.muc.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Jennejohn wrote: > > >Mmmm... O'Brien, could you make sure the space-critical code in > >sys/boot compiles ok? > > I still have GCC 2.95.2 installed. This is what I get in /sys/boot: > > ===> i386/boot2 > (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o > ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o > objcopy -S -O binary boot1.out boot1 > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd > -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs > -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c boot2.c > (cd /usr/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o > ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o > objcopy -S -O binary boot2.out boot2.bin > btxld -v -E 0x1000 -f bin -b /usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin > kernel: ver=1.01 size=700 load=9000 entry=9010 map=16M pgctl=1:1 > client: fmt=bin size=15c0 text=0 data=0 bss=0 entry=0 > output: fmt=bin size=1ec0 text=200 data=1cc0 org=0 entry=0 > -192 bytes available > ^^^^^^^^^^^^^^^^^^^^ Well, the flags seem correct (in particular -Os). It would be interesting to see what's the difference in the assembler code generated by both. Unfortunately, I cannot upgrade my system for the time being. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 7 23:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id D2EC015199 for ; Sun, 7 Nov 1999 23:14:14 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1932 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Mon, 8 Nov 1999 08:14:13 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 447A73896; Mon, 8 Nov 1999 08:14:12 +0100 (MET) Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: <199911071938.LAA13498@dingo.cdrom.com> from Mike Smith at "Nov 7, 99 11:38:46 am" To: mike@smith.net.au (Mike Smith) Date: Mon, 8 Nov 1999 08:14:12 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1077 Message-Id: <19991108071412.447A73896@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Mike Smith: > > I still hope documentation for the new-bus, new-pnp architecture will be > > made available at sufficient time before 4.0-RELEASE code freeze. > > There's as much or more documentation on the current architecture as > there was on the old one. Check the reality. Have a look at the PnP documentation available for the old PnP architecture at http://www.freebsd.org/~luigi/pnp971020.tgz and then tell me where i find "as much or more" than this for the new one. > Sitting on your hands and whining about > there being no 2m-long shelf of ring-bound manuals isn't an excuse for > not getting on and doing things like they ought to be done. Thanks a lot for your constructive criticism, as usual, i appreciate it! hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 0: 5:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id E2F2E14C17; Mon, 8 Nov 1999 00:05:31 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id JAA82312; Mon, 8 Nov 1999 09:05:30 +0100 (MET) Date: Mon, 8 Nov 1999 09:05:30 +0100 From: Martin Cracauer To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: sh bug Message-ID: <19991108090529.A81298@cons.org> References: <199911080440.FAA18162@qix.jmz.org> <199911080505.GAA18326@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911080505.GAA18326@qix.jmz.org>; from Jean-Marc Zucconi on Mon, Nov 08, 1999 at 06:05:19AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199911080505.GAA18326@qix.jmz.org>, Jean-Marc Zucconi wrote: > >>>>> Jean-Marc Zucconi writes: > > > Try this in -current > > $ cat some_file | head > > > I have to use ^C to regain control. > > ... and reverting to rev. 1.22 of eval.c fixes the problem. Steve Price fixed my 1.23 mistake in 1.24. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.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 8 0:25:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from nuke.danger.ms (a204b210n122client59.hawaii.rr.com [204.210.122.59]) by hub.freebsd.org (Postfix) with ESMTP id D5FBD1518E for ; Mon, 8 Nov 1999 00:25:39 -0800 (PST) (envelope-from billm@danger.ms) Received: from localhost (billm@localhost) by nuke.danger.ms (8.9.3/8.9.3) with ESMTP id WAA10860 for ; Sun, 7 Nov 1999 22:26:07 -1000 (HST) (envelope-from billm@danger.ms) X-Authentication-Warning: nuke.danger.ms: billm owned process doing -bs Date: Sun, 7 Nov 1999 22:26:06 -1000 (HST) From: Bill Marquette To: freebsd-current@FreeBSD.ORG Subject: No buffer space available errors 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 For the last week and a half or so I've been trying to track this down assuming it was a configuration error on my part or a problem with my ISP's DHCP configuration. After switching from a DEC 20141 chipset card to a 3com 3c905, I found I was still having problems although the error message had changed. I'm now back to the DEC card cause I found more results in the mailing lists on the errors I was seeing. At first it appeared to be dhclient having issues, but I've finally found occurances of other programs showing symptoms prior to dhclient log entries. Also, until today I couldn't replicate the problem while sitting at the console, it would only show itself after I'd been away for a few minutes (I swear it has a mind of it's own) usually, when I was going to be away for more than 10-15 minutes. Today I managed to force the machine to have problems by doing multiple simultaneous downloads and uploads, I was running about 100K/sec through the NIC. This machine is running as a simple workstation with nothing special on it but there were alot of messages that mentioned increasing maxusers and/or NMBCLUSTERS to solve this. I've now got maxusers at 128 and NMBCLUSTERS at 16384 (in fairly small increments to see where it would start working). NBUF is also currently at 4096 again, raised over a period of two weeks at a recommendation from a friend. I'm still getting the "No buffer space available" messages and the only fix is to kill dhclient, ifconfig down the interface and restart dhclient. System and kernel are of the same sources, cvsupped multiple times over last two weeks. Most recent from October 31st. I will be performing a cvsup again tomorrow and see if that makes a difference. Thanks for any help!!! The following is either excerpts from logs or various utilities that have been used or asked for in other reports on similar problems. --Bill Hardware: AMD K6-2 400 192MB RAM Voodoo3 2000 PCI video 2x Maxtor 8gb IDE 12x Mitsumi ATAPI CDROM 2x Memorex ATAPI CD/RW AHA 1542 SCSI controller 4gb IBM Fast SCSI-2 32x Toshiba SCSI CDROM Soundblaster AWE32 (using drivers from www.4front-tech.com) 3Com 3c905 10/100 NIC (currently unused while tracking down problem) Generic DEC 2104x chipset 10Mbit NIC Externel parallel port ZIP 100 From dmesg: xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 8.0 on pci0 xl0: Ethernet address: 00:50:04:66:ef:a8 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto de0: irq 12 at device 9.0 on pci0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:80:ad:a9:30:f9 From syslog: Nov 7 14:09:01 nuke named[153]: ns_forw: sendto([216.225.0.4].53): No buffer space available Nov 7 14:09:30 nuke named[153]: ns_forw: sendto([206.85.240.238].53): No buffer space available Nov 7 14:09:59 nuke named[153]: ns_forw: sendto([128.9.0.107].53): No buffer space available Nov 7 14:10:00 nuke named[153]: ns_forw: sendto([209.117.223.51].53): No buffer space available Nov 7 14:11:00 nuke named[153]: ns_forw: sendto([206.239.111.254].53): No buffer space available Nov 7 14:11:39 nuke dhclient: DHCPREQUEST on de0 to 204.210.96.1 port 67 Nov 7 14:11:39 nuke dhclient: send_packet: No buffer space available From netstat -m (Note: I had been downloading some rather large files and wasn't at console for a couple hours; this is highly exagerated since I've seen this error with as few as 300/900 mbufs in use): 45/34496 mbufs in use: 38 mbufs allocated to data 7 mbufs allocated to packet headers 36/16158/16384 mbuf clusters in use (current/peak/max) 36628 Kbytes allocated to network (0% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines sysctl vm.zone: vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS socket: 192, 16384, 145, 86, 46856 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 0:27: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 08013151C9 for ; Mon, 8 Nov 1999 00:27:05 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id DAA11181 for ; Mon, 8 Nov 1999 03:08:16 -0500 (EST) Date: Mon, 8 Nov 1999 03:25:48 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Re: libvgl - status and perspectives In-Reply-To: <19991107181732.B41126@daemon.ninth-circle.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, 7 Nov 1999, Jeroen Ruigrok/Asmodai wrote: > libggi has more support for FreeBSD than svgalib has and it also seems > to be preferred over svgalib due to security hassles and all that. > > So you might want to try that route. I saw where libvgl is now new and improved, and is called "libsvgl". It's got vesa and svga extensions. My question is does libggi support vesa modes on FreeBSD now, or does it have to be compiled under XFree86? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 0:30:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 570F81518E for ; Mon, 8 Nov 1999 00:30:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA90995; Mon, 8 Nov 1999 09:29:59 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911080829.JAA90995@freebsd.dk> Subject: Re: libvgl - status and perspectives In-Reply-To: from Donn Miller at "Nov 8, 1999 03:25:48 am" To: dmmiller@cvzoom.net (Donn Miller) Date: Mon, 8 Nov 1999 09:29:59 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Donn Miller wrote: > On Sun, 7 Nov 1999, Jeroen Ruigrok/Asmodai wrote: > > > libggi has more support for FreeBSD than svgalib has and it also seems > > to be preferred over svgalib due to security hassles and all that. > > > > So you might want to try that route. > > I saw where libvgl is now new and improved, and is called "libsvgl". It's > got vesa and svga extensions. My question is does libggi support vesa > modes on FreeBSD now, or does it have to be compiled under XFree86? No, its still called libvgl, at least thats what my version is called :) I've no idea on GGI, too long since I looked at it... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 0:41:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 4C78214D51; Mon, 8 Nov 1999 00:41:46 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 3919C1927; Mon, 8 Nov 1999 09:42:07 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 287D249D8; Mon, 8 Nov 1999 09:42:07 +0100 (CET) Date: Mon, 8 Nov 1999 09:42:05 +0100 (CET) From: Andrzej Bialecki To: Kazutaka YOKOTA Cc: sos@freebsd.org, freebsd-current@freebsd.org Subject: Re: libvgl - status and perspectives In-Reply-To: <199911080111.KAA20479@zodiac.mech.utsunomiya-u.ac.jp> 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, 8 Nov 1999, Kazutaka YOKOTA wrote: > > >Today I noticed accidentally that either libvgl is broken, or the demo > >program does something wrong - the mouse cursor doesn't move. > > Oops, sos and I have developed a new version of libsvgl which can > handle VESA modes in addition to the standard VGA graphics modes. > But I haven't committed it to the source tree yet (yes, I should have > done so weeks ago ;-( > > Anyway, if you are interested, I can send you a copy for testing. Yes, sort of... You see, with libvgl I ended up implementing most of the events abstraction myself - libvgl seriously lacks this (among others). So, of course new VESA modes are very interesting, but what would be really cool is more general framework for graphical terminal handling. > >But this brings more general question regarding console graphics library. > >As it is today, libvgl is almost useless due to very limited set of > >functions. There were discussions whether to port SVGAlib or GGI. Do you > >know if someone is working/planning to work on it? Do you know something about this? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: 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 Mon Nov 8 1: 7:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8322515177; Mon, 8 Nov 1999 01:07:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA91100; Mon, 8 Nov 1999 10:07:01 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911080907.KAA91100@freebsd.dk> Subject: Re: libvgl - status and perspectives In-Reply-To: from Andrzej Bialecki at "Nov 8, 1999 09:42:05 am" To: abial@webgiro.com (Andrzej Bialecki) Date: Mon, 8 Nov 1999 10:07:00 +0100 (CET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), sos@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Andrzej Bialecki wrote: > > > > Oops, sos and I have developed a new version of libsvgl which can > > handle VESA modes in addition to the standard VGA graphics modes. > > But I haven't committed it to the source tree yet (yes, I should have > > done so weeks ago ;-( > > > > Anyway, if you are interested, I can send you a copy for testing. > > Yes, sort of... You see, with libvgl I ended up implementing most of the > events abstraction myself - libvgl seriously lacks this (among others). > So, of course new VESA modes are very interesting, but what would be > really cool is more general framework for graphical terminal handling. Hmm, libvgl was originally only thought as a way to do simple graphics on the console, nothing more. What exactly is it you need ?? (And I'm not suggesting that I have the time to do it :) ) > > >But this brings more general question regarding console graphics library. > > >As it is today, libvgl is almost useless due to very limited set of > > >functions. There were discussions whether to port SVGAlib or GGI. Do you > > >know if someone is working/planning to work on it? > > Do you know something about this? I think you all know my feelings about svgalib so I wont comment on that one. I havn't been following the GGI project lately so I dont know what they have achived, but last time I looked it had a loooong way to go to be minimally usefull, and their kernel stuff was, well, not something I'd put into our kernel.... Anyhow, I think we have what can be currently done resonably in the kernel its just a matter of how you should interface to it. Remember that VESA is on the way out, and there is no solution for us for new HW other than being able to use the vendor supplied WINxx drivers (nearly impossible) or get the vendors to release FreeBSD drivers (nearly impossible) or use X (others have the problem)... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 2: 8:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E0EC9151BB for ; Mon, 8 Nov 1999 02:08:15 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p138-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA03283; Mon, 8 Nov 1999 21:13:21 +1100 Date: Mon, 8 Nov 1999 21:07:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Hay Cc: current@FreeBSD.ORG Subject: Re: doscmd broken on current? fixed In-Reply-To: <199911071935.VAA60044@zibbi.mikom.csir.co.za> 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, 7 Nov 1999, John Hay wrote: > Ok, with these patches doscmd is working for me again. I can boot dos and > run the topspeed C compiler like I used to a few months ago. > > If nobody has any complaints I'll commit it. I'm just not 100% sure about > the patch to doscmd.c and would like if someone with more knowledge about > the signal stuff would just look at it. There is just too many signal > Index: doscmd.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/doscmd/doscmd.c,v > retrieving revision 1.11 > diff -u -r1.11 doscmd.c > --- doscmd.c 1999/10/13 23:48:35 1.11 > +++ doscmd.c 1999/11/07 12:50:06 > @@ -258,6 +258,7 @@ > > sigemptyset(&uc.uc_sigmask); > sigaltstack(NULL, &uc.uc_stack); > + uc.uc_mcontext.mc_onstack = uc.uc_stack.ss_flags; > > if (tmode) > tracetrap(REGS); > I only know this well enough to use the source quickly. Setting the onstack flag to the stack flags is logically wrong because the onstack flag is a single bit (1 or SS_ONSTACK; see (*)), while the stack flags are some combination of SS_DISABLE and SS_ONSTACK (see sigaltstack(2)). The following would be logically correct: + uc.uc_mcontext.mc_onstack = uc.uc_stack.ss_flags & SS_ONSTACK; but since the alternative signal stack is not in use at this point, the rvalue is known to be 0 and the fix can be reduced to: + uc.uc_mcontext.mc_onstack = 0; as in RELENG_3. RELENG_3 also omits the sigaltstack() call (which gives the current (almost known) alt stack settings). I think this is valid because uc_stack and mc_onstack are read-only for signal handlers (any changes to uc_stack will be ignored on sigreturn(), and any changes to mc_onstack will make a mess). When sigreturn() is called with a made-up context as in doscmd:main(), mc_onstack needs to be initialised to avoid making a mess. (*) In RELENG_3, the SS_ONSTACK bit in ss_flags is passed to signal handlers as "sc_onstack = ss_flags & SS_ONSTACK" but assumed to be returned via sigreturn() as "sc_onstack & 01". Since signal handlers are not expected to modify sc_onstack, this only works if SS_ONSTACK = 1, as it is. In -current, the SS_ONSTACK bit in ss_flags is passed to signal handlers as "mc_onstack = ss_flags & SS_ONSTACK ? 1 : 0", so the old handling of the flag in sigreturn() is now logically correct, but this is broken since it changes the semantics for setting mc_onstack. Related problems: The USE_VM86 case in doscmd.c is more broken than in RELENG_3. It is missing sc -> uc name changes. Unrelated problems: Your patch for cwd.c helps, but lookup of /dosD/bin/ls.exe is still broken. The path gets converted to //dosd/bin/ls.exe. The // is wrong and the /dosd is broken, since that part of the path is in ffs which is case-sensitive. 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 8 3: 4:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id DBC1A14E66; Mon, 8 Nov 1999 03:04:31 -0800 (PST) (envelope-from netch@lucky.net) Received: from netch@localhost by burka.carrier.kiev.ua id NBS46334; Mon, 8 Nov 1999 13:04:29 +0200 (EET) (envelope-from netch) Date: Mon, 8 Nov 1999 13:04:29 +0200 From: Valentin Nechayev To: Eivind Eklund Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/libexec/uucpd uucpd.c Message-ID: <19991108130429.A45693@lucky.net> Reply-To: netch@lucky.net References: <199911062058.MAA72645@freefall.freebsd.org> <382573E1.66E8AF35@newsguy.com> <19991107142522.L72085@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: <19991107142522.L72085@bitbox.follo.net>; from Eivind Eklund on Sun, Nov 07, 1999 at 02:25:22PM +0100 X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Eivind Eklund! Sun, Nov 07, 1999 at 14:25:22, eivind wrote about "Re: cvs commit: src/libexec/uucpd uucpd.c" in cvs-commiters@, cvs-all@: > > Just for the record, this is considered a really bad thing, because > > one common error is typing the password when the username is being > > expected. > > > > Of course, in an automated environment without user intervention, > > that's probably not relevant. But I'd rather just remark on it > > anyway. :-) > > I wouldn't expect anybody to do UUCP manually. The standard practise is to use UUCP on network access server with some pass (rlogin, etc.) to real uucp server. When script fails in something (incorrect waitings, modem failures, cable failures...), it can send password when server expects login, and vice versa. > The servers I originally did this change for has about a thousand > customers using UUCP-over-TCP, using various systems. I've not seen > any passwords end up in the log; however, it has made it possible to > contact users with problems, and to see why we continiously got logged > password failures (answer: Some broken client sending 'quit' on the > username prompt before disconnecting). You have quite good phone lines and customers have good cables and ports. In some places it is not standard, but hope ;( > I don't have any religious feeling about this change, and I'm willing > to back it out and keep it as a local change again (the way it has > been for a year or so). I just thought it would be considered an > improvement for other users, too. Possibly it should be turned off by default and turned on in config. -- NVA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 4:34: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id A3A6B14E66 for ; Mon, 8 Nov 1999 04:34:02 -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.3/8.9.3) with ESMTP id NAA20118; Mon, 8 Nov 1999 13:34:00 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA21199; Mon, 8 Nov 1999 13:33:59 +0100 (MET) Date: Mon, 8 Nov 1999 13:33:59 +0100 From: Eivind Eklund To: Valentin Nechayev Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/libexec/uucpd uucpd.c Message-ID: <19991108133359.V72085@bitbox.follo.net> References: <199911062058.MAA72645@freefall.freebsd.org> <382573E1.66E8AF35@newsguy.com> <19991107142522.L72085@bitbox.follo.net> <19991108130429.A45693@lucky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991108130429.A45693@lucky.net>; from netch@lucky.net on Mon, Nov 08, 1999 at 01:04:29PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 08, 1999 at 01:04:29PM +0200, Valentin Nechayev wrote: [Regarding a change to UUCP to have it log the username when the password entry fails] > > I don't have any religious feeling about this change, and I'm willing > > to back it out and keep it as a local change again (the way it has > > been for a year or so). I just thought it would be considered an > > improvement for other users, too. > > Possibly it should be turned off by default and turned on in config. I do not have making improvements to UUCP as a high priority for my FreeBSD work, and I'm short on time, so I can only offer you the following options: (1) Write up diffs to support this, and I'll review them (and commit them if they are OK). (2) Keep the change in there the way it is (3) Back the change out I don't want to volunteer more of my time to even do further discussion - having this change in FreeBSD is that low priority to me (I have a bunch of things to do with FreeBSD, and spending time on this means that less time go to other things). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 5:43: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 65F9A14C4E for ; Mon, 8 Nov 1999 05:42:58 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id IAA18190 for ; Mon, 8 Nov 1999 08:42:47 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id IAA13020 for ; Mon, 8 Nov 1999 08:42:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA13016 for ; Mon, 8 Nov 1999 08:42:55 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 8 Nov 1999 08:42:55 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: syncing disks giving up. 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 cvsupped this morning, and noticed that now whenever I reboot (I do this to make sure everything works right with the new kernel) the machine does this: syncing disks 15 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 giving up.. Rebooting... Then fsck has to fix a whole lot of stuff upon reboot. This is with a kernel that is 20 minutes old. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 5:49:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 33A6414FEB for ; Mon, 8 Nov 1999 05:49:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA18669; Mon, 8 Nov 1999 14:48:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: syncing disks giving up. In-reply-to: Your message of "Mon, 08 Nov 1999 08:42:55 EST." Date: Mon, 08 Nov 1999 14:48:50 +0100 Message-ID: <18667.942068930@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Update, that is caused by a leak from my experimental branch into -current. In message , Kenneth Wayn e Culver writes: >I just cvsupped this morning, and noticed that now whenever I reboot (I do >this to make sure everything works right with the new kernel) the machine >does this: > >syncing disks 15 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 >giving up.. >Rebooting... > >Then fsck has to fix a whole lot of stuff upon reboot. This is with a >kernel that is 20 minutes old. > > >================================================================= >| Kenneth Culver | FreeBSD: The best OS around. | >| Unix Systems Administrator | ICQ #: 24767726 | >| and student at The | AIM: AgRSkaterq | >| The University of Maryland, | Website: (Under Construction) | >| College Park. | http://www.wam.umd.edu/~culverk/| >================================================================= > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 6:34:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E59241518E; Mon, 8 Nov 1999 06:34:25 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id IAA29737; Mon, 8 Nov 1999 08:34:24 -0600 (CST) Date: Mon, 8 Nov 1999 08:34:24 -0600 (CST) From: Steve Price To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: sh bug In-Reply-To: <199911080505.GAA18326@qix.jmz.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 Mon, 8 Nov 1999, Jean-Marc Zucconi wrote: # >>>>> Jean-Marc Zucconi writes: # # > Try this in -current # > $ cat some_file | head # # > I have to use ^C to regain control. # # ... and reverting to rev. 1.22 of eval.c fixes the problem. Does revision 1.24 work? # Jean-Marc # # -- # Jean-Marc Zucconi PGP Key: finger jmz@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 8 6:36:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7BF38150C1 for ; Mon, 8 Nov 1999 06:36:51 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id JAA02219; Mon, 8 Nov 1999 09:36:06 -0500 (EST) Date: Mon, 8 Nov 1999 09:36:06 -0500 (EST) From: "Matthew N. Dodd" To: Hellmuth Michaelis Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Dr Neuhaus niccy go not recognized In-Reply-To: <19991108071412.447A73896@hcswork.hcs.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 On Mon, 8 Nov 1999, Hellmuth Michaelis wrote: > Check the reality. Have a look at the PnP documentation available for > the old PnP architecture at > http://www.freebsd.org/~luigi/pnp971020.tgz and then tell me where i > find "as much or more" than this for the new one. PnP devices are handled no differently than devices created by config 'hints'. Basically you call ISA_PNP_PROBE() at the top of your DEVICE_PROBE() method and check the return status. Once you do this you should probably verify that all your resources are present before going on with the rest of the probe. Check out sys/dev/ed/if_ed_isa.c and sys/dev/ep/if_ep_isa.c for examples. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 7:17: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 1A7D014CA9; Mon, 8 Nov 1999 07:16:56 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991108101651.10061@mojave.sitaranetworks.com> Date: Mon, 8 Nov 1999 10:16:51 -0500 From: Greg Lehey To: Warner Losh Cc: "D. Rock" , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working Reply-To: Greg Lehey References: <19991105173835.10766@mojave.sitaranetworks.com> <199910230241.UAA26689@harmony.village.org> <3823540C.AE8ADA4F@dead-end.net> <19991105173835.10766@mojave.sitaranetworks.com> <199911061749.KAA22375@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911061749.KAA22375@harmony.village.org>; from Warner Losh on Sat, Nov 06, 1999 at 10:49:26AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 6 November 1999 at 10:49:26 -0700, Warner Losh wrote: > In message <19991105173835.10766@mojave.sitaranetworks.com> Greg Lehey writes: > : Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 > > Unless you are running pccardd, you won't see the pccard devices show > up. The probe messages that I'm interested in would be the ones that > say something about it being on pccard0. > > Maybe I'm just confused. Yes, I think so. My original message included the probe messages from pccardd as well. I commented on sio1 because I had it in the kernel config file; IIRC this used to be necessary in order for the device to be found. I've removed the sio1 definition now (sio0 remains, corresponding to a hard-wired port on the laptop). I now get: sio0: gdb debugging port (hmmm. I thought I should have got more than that) ... pccard: card inserted, slot 0 pccard: card inserted, slot 1 ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 9 slot 0 on pccard0 ep0: Ethernet address 00:60:97:40:fb:e1 sio1 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0 sio1: type 16550A I need to check why I'm not getting irq 3 for the port, but everything else looks OK. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 7:41:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 4A5DC1521D for ; Mon, 8 Nov 1999 07:41:16 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id KAA26327 for ; Mon, 8 Nov 1999 10:09:16 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA02038 for ; Mon, 8 Nov 1999 10:09:24 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA02034 for ; Mon, 8 Nov 1999 10:09:24 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 8 Nov 1999 10:09:24 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: syncing disks giving up 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 Alright I did what PHK told me to, and updated, but now for some reason when I reboot, I can't get the root directory to keep the new kernel. this is what happens before I reboot: culverk:~> ls -l /kernel* -r-xr-xr-x 1 root wheel 1551621 Nov 8 08:18 /kernel* -r-xr-xr-x 1 root wheel 1551621 Nov 8 10:05 /kernel.old* and this is what happens after I reboot (with kernel.old): culverk:~> ls -l /kernel* -rw------- 1 root wheel 0 Nov 8 08:18 /kernel* -r-xr-xr-x 1 root wheel 1551621 Nov 8 10:05 /kernel.old* Any suggestions? I can't get a new kernel to boot so I'd appreciate anything anyone can suggest... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 7:46:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.ORG (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 56CF615221 for ; Mon, 8 Nov 1999 07:46:20 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id QAA19867; Mon, 8 Nov 1999 16:47:29 +0100 (MET) (envelope-from jmz@FreeBSD.ORG) Date: Mon, 8 Nov 1999 16:47:29 +0100 (MET) Message-Id: <199911081547.QAA19867@qix.jmz.org> From: Jean-Marc Zucconi To: sprice@hiwaay.net Cc: current@FreeBSD.ORG In-reply-to: (message from Steve Price on Mon, 8 Nov 1999 08:34:24 -0600 (CST)) Subject: Re: sh bug X-Mailer: Emacs References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Steve Price writes: > On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote: > # >>>>> Jean-Marc Zucconi writes: > # > # > Try this in -current > # > $ cat some_file | head > # > # > I have to use ^C to regain control. > # > # ... and reverting to rev. 1.22 of eval.c fixes the problem. > Does revision 1.24 work? Yes. It works too. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 8 8:18: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ED13414BF6 for ; Mon, 8 Nov 1999 08:17:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA19260; Mon, 8 Nov 1999 17:17:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: syncing disks giving up In-reply-to: Your message of "Mon, 08 Nov 1999 10:09:24 EST." Date: Mon, 08 Nov 1999 17:17:36 +0100 Message-ID: <19258.942077856@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kenneth Wayne Culver writes: >Alright I did what PHK told me to, and updated, but now for some reason >when I reboot, I can't get the root directory to keep the new kernel. this >is what happens before I reboot: > >culverk:~> ls -l /kernel* >-r-xr-xr-x 1 root wheel 1551621 Nov 8 08:18 /kernel* >-r-xr-xr-x 1 root wheel 1551621 Nov 8 10:05 /kernel.old* >and this is what happens after I reboot (with kernel.old): >culverk:~> ls -l /kernel* >-rw------- 1 root wheel 0 Nov 8 08:18 /kernel* >-r-xr-xr-x 1 root wheel 1551621 Nov 8 10:05 /kernel.old* > >Any suggestions? I can't get a new kernel to boot so I'd appreciate >anything anyone can suggest... Do you have 1.127 of src/sys/miscfs/specfs/spec_vnops.c ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 8:26:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 58A8414DBC for ; Mon, 8 Nov 1999 08:26:32 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net (8.9.3/8.9.3) with ESMTP id LAA72808 for ; Mon, 8 Nov 1999 11:26:32 -0500 (EST) Message-Id: <4.2.1.19991108112205.00a8e220@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Mon, 08 Nov 1999 11:23:25 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Release schedule of 4.0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're building a few new systems. I wondered what the status was of the 4.0 project (stability and release date estimate). Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 8:30:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5BEEC14DBC for ; Mon, 8 Nov 1999 08:30:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA19350; Mon, 8 Nov 1999 17:30:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Release schedule of 4.0 In-reply-to: Your message of "Mon, 08 Nov 1999 11:23:25 EST." <4.2.1.19991108112205.00a8e220@216.67.12.69> Date: Mon, 08 Nov 1999 17:30:05 +0100 Message-ID: <19348.942078605@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.1.19991108112205.00a8e220@216.67.12.69>, Forrest Aldrich writes: >We're building a few new systems. I wondered what the status >was of the 4.0 project (stability and release date estimate). We expect release Q1/2000 some time. Feature freeze will probably happen this year. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 9: 6:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C9A4F14C99; Mon, 8 Nov 1999 09:06:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA89196; Mon, 8 Nov 1999 10:06:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA10741; Mon, 8 Nov 1999 10:05:55 -0700 (MST) Message-Id: <199911081705.KAA10741@harmony.village.org> To: Greg Lehey Subject: Re: sio working Cc: "D. Rock" , current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 08 Nov 1999 10:16:51 EST." <19991108101651.10061@mojave.sitaranetworks.com> References: <19991108101651.10061@mojave.sitaranetworks.com> <19991105173835.10766@mojave.sitaranetworks.com> <199910230241.UAA26689@harmony.village.org> <3823540C.AE8ADA4F@dead-end.net> <19991105173835.10766@mojave.sitaranetworks.com> <199911061749.KAA22375@harmony.village.org> Date: Mon, 08 Nov 1999 10:05:54 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991108101651.10061@mojave.sitaranetworks.com> Greg Lehey writes: : I need to check why I'm not getting irq 3 for the port, but everything : else looks OK. Likely because you don't have irq 3 listed in the line of available irqs for pccardd Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 9:53:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 17B4C15103; Mon, 8 Nov 1999 09:53:19 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991108125315.41719@mojave.sitaranetworks.com> Date: Mon, 8 Nov 1999 12:53:15 -0500 From: Greg Lehey To: Warner Losh Cc: "D. Rock" , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working Reply-To: Greg Lehey References: <19991108101651.10061@mojave.sitaranetworks.com> <19991105173835.10766@mojave.sitaranetworks.com> <199910230241.UAA26689@harmony.village.org> <3823540C.AE8ADA4F@dead-end.net> <19991105173835.10766@mojave.sitaranetworks.com> <199911061749.KAA22375@harmony.village.org> <19991108101651.10061@mojave.sitaranetworks.com> <199911081705.KAA10741@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911081705.KAA10741@harmony.village.org>; from Warner Losh on Mon, Nov 08, 1999 at 10:05:54AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 8 November 1999 at 10:05:54 -0700, Warner Losh wrote: > In message <19991108101651.10061@mojave.sitaranetworks.com> Greg Lehey writes: > : I need to check why I'm not getting irq 3 for the port, but everything > : else looks OK. > > Likely because you don't have irq 3 listed in the line of available > irqs for pccardd ISTR that pccardd took the irq for itself. When I have time to investigate, I will. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 10: 1:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id DD04615220; Mon, 8 Nov 1999 10:01:44 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA29633; Mon, 8 Nov 1999 13:01:43 -0500 (EST) (envelope-from luoqi) Date: Mon, 8 Nov 1999 13:01:43 -0500 (EST) From: Luoqi Chen Message-Id: <199911081801.NAA29633@lor.watermarkgroup.com> To: garyj@muc.de, obrien@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is the patch I've been working on (before I 1st got BDE's reply). > The changes are mostly from OpenBSD + style changes for the way we do > things. Can you also test this one? > > > Index: bus.h > =================================================================== > RCS file: /home/ncvs/src/sys/i386/include/bus.h,v > retrieving revision 1.6 > diff -u -r1.6 bus.h > --- bus.h 1999/08/28 00:44:07 1.6 > +++ bus.h 1999/11/06 21:42:15 > @@ -252,15 +252,14 @@ > else > #endif > { > - int __x __asm__("%eax"); > __asm __volatile(" \n\ > cld \n\ > - 1: movb (%1),%%al \n\ > + 1: movb (%2),%%al \n\ > stosb \n\ > loop 1b" : > - "=&a" (__x) : > - "r" (bsh + offset), "D" (addr), "c" (count) : > - "%edi", "%ecx", "memory"); > + "=D" (addr), "=c" (count) : > + "r" (bsh + offset), "0" (addr), "1" (count) : > + "%eax", "memory"); > } > #endif > } You may use "+D" and "+c" for the in-out operands, "+D" (addr), "+c" (count) : "r" (bsh + offset) : -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 10:12:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 792781525D; Mon, 8 Nov 1999 10:12:42 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991108131231.58652@mojave.sitaranetworks.com> Date: Mon, 8 Nov 1999 13:12:31 -0500 From: Greg Lehey To: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Please test Vinum with this (was: bdev patch looking for review & testers) Reply-To: Greg Lehey References: <14629.941989932@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <14629.941989932@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Nov 07, 1999 at 04:52:12PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 7 November 1999 at 16:52:12 +0100, Poul-Henning Kamp wrote: > > The main thing in this patch is to make bdevs use the same (ie: normal) > vnode locking as character devices. > > Secondary effects are general cleanup in spec_vnops.c > > You should see no operational changes by applying this patch, if you > do, please report them to me. Poul-Henning asked me to test this with Vinum, but I currently don't have access to a Vinum box. If somebody else would test it, both Poul-Henning and I would be grateful. Let both of us know if you have any problems. The patches are at http://phk.freebsd.dk/bdev/x.d. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 10:17:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3A0BD1525D for ; Mon, 8 Nov 1999 10:17:46 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA19717; Mon, 8 Nov 1999 19:16:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Please test Vinum with this (was: bdev patch looking for review & testers) In-reply-to: Your message of "Mon, 08 Nov 1999 13:12:31 EST." <19991108131231.58652@mojave.sitaranetworks.com> Date: Mon, 08 Nov 1999 19:16:53 +0100 Message-ID: <19715.942085013@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991108131231.58652@mojave.sitaranetworks.com>, Greg Lehey writes: >On Sunday, 7 November 1999 at 16:52:12 +0100, Poul-Henning Kamp wrote: >> >> The main thing in this patch is to make bdevs use the same (ie: normal) >> vnode locking as character devices. >> >> Secondary effects are general cleanup in spec_vnops.c >> >> You should see no operational changes by applying this patch, if you >> do, please report them to me. > >Poul-Henning asked me to test this with Vinum, but I currently don't >have access to a Vinum box. If somebody else would test it, both >Poul-Henning and I would be grateful. Let both of us know if you have >any problems. > >The patches are at http://phk.freebsd.dk/bdev/x.d. This patch is newer than the one I emailed out, and should be used for testing. Thanks in advance! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 11:25:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 78F7514F58 for ; Mon, 8 Nov 1999 11:25:43 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11kuQd-000KyQ-00; Mon, 8 Nov 1999 19:26:11 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA11970; Mon, 8 Nov 1999 20:25:33 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <382723AD.DCD6719A@scc.nl> Date: Mon, 08 Nov 1999 20:25:33 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Price Cc: freebsd-current@freebsd.org Subject: Re: new sigaction struct References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Price wrote: > Just curious as to what the motivation for re-ordering the > sa_flags and sa_mask members in sigaction were? The manpage > still describes the old order BTW. If sigset_t is to be changed again, then having it the last field in the structure leaves us some room to avoid introducing new syscalls all over again and handle the change with the current structure and syscalls. > My Alpha box has been limping through a package build and I've > noticed a number of ports that seem to be falling over for > signal-related changes. This should not be caused be the ordering of the fields in struct sigaction. > One in particular would be the rawio > port which expects sa_mask to be before sa_flags in struct > sigaction. Silly... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 8 11:48:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 13FFC153CC for ; Mon, 8 Nov 1999 11:48:29 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 8 Nov 1999 19:47:23 +0000 X-Mailer: exmh version 2.0.2 To: current@FreeBSD.ORG Subject: ambiguity between -STABLE and -RELEASE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Nov 1999 19:47:23 +0000 Message-ID: <1218.942090443@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, just a very basic question that would resolve a dispute between colleagues. When one talks about Fbsd3.3-STABLE my impression is that such version is a stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the final version and the -STABLE is the version that is soon (after some further bug settling) to become -RELEASE. Is this the case? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 11:58:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 9E9CF152B2 for ; Mon, 8 Nov 1999 11:58:19 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 924653E33; Mon, 8 Nov 1999 20:58:18 +0100 (CET) Date: Mon, 8 Nov 1999 20:58:18 +0100 From: Jesper Skriver To: Theo PAGTZIS Cc: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE Message-ID: <19991108205818.A46313@skriver.dk> References: <1218.942090443@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1218.942090443@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Mon, Nov 08, 1999 at 07:47:23PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 08, 1999 at 07:47:23PM +0000, Theo PAGTZIS wrote: > just a very basic question that would resolve a dispute between colleagues. > > When one talks about Fbsd3.3-STABLE my impression is that such version is a > stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the > final version and the -STABLE is the version that is soon (after some further > bug settling) to become -RELEASE. > > Is this the case? Yes and no, -STABLE is just the newest version of the stable branch, a -RELEASE is just a "snapshot" of -STABLE at a certain date. So for the most stable and up to date version, use -STABLE not -RELEASE /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 Mon Nov 8 12: 4:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 1A08315295 for ; Mon, 8 Nov 1999 12:04:23 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA15235; Mon, 8 Nov 1999 12:04:19 -0800 (PST) Date: Mon, 8 Nov 1999 12:04:19 -0800 From: Brooks Davis To: Theo PAGTZIS Cc: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE Message-ID: <19991108120419.A11594@orion.ac.hmc.edu> References: <1218.942090443@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <1218.942090443@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Mon, Nov 08, 1999 at 07:47:23PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 08, 1999 at 07:47:23PM +0000, Theo PAGTZIS wrote: > just a very basic question that would resolve a dispute between colleagues. > > When one talks about Fbsd3.3-STABLE my impression is that such version is a > stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the > final version and the -STABLE is the version that is soon (after some further > bug settling) to become -RELEASE. > > Is this the case? Nope. ;-) 3.3-STABLE is the 3.x branch after 3.3-Release. It's probably not correct to talk about 3.3-STABLE except that it tells people that you are running a version of the 3-STABLE (RELENG_3 to CVS) branch after 3.3-RELEASE. The way things work is that there is a 3.x branch which is referred to as 3-STABLE and releases are snapshots of that branch. -- Brooks -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 12:11:29 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 0C5AB14D15; Mon, 8 Nov 1999 12:11:28 -0800 (PST) From: "Jonathan M. Bresler" To: T.Pagtzis@cs.ucl.ac.uk Cc: current@FreeBSD.ORG In-reply-to: <1218.942090443@cs.ucl.ac.uk> (message from Theo PAGTZIS on Mon, 08 Nov 1999 19:47:23 +0000) Subject: Re: ambiguity between -STABLE and -RELEASE Message-Id: <19991108201128.0C5AB14D15@hub.freebsd.org> Date: Mon, 8 Nov 1999 12:11:28 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > just a very basic question that would resolve a dispute between colleagues. > > When one talks about Fbsd3.3-STABLE my impression is that such version is a > stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the > final version and the -STABLE is the version that is soon (after some further > bug settling) to become -RELEASE. > > Is this the case? tis just the reverse from what you have written. 3.3 FreeBSD is released, minted onto CD, and made avilable over the Internet. At that point in time 3.3 FreeBSD is 3.3-RELEASE. all further work on 3.3 FreeBSD is called 3.3-STABLE. at all times there are two versions of FreeBSD under active work. The -CURRENT version gets all the latest changes...becareful some of these changes *will* hurt you. The -STABLE version gets bug fixes and performance enhancements only. (poor performance is also a bug). All changes to -STABLE must be tested and generally beaten up in -CURRENT first. jmb ps. note this explaination is somewaht simplified, but it accurate in all its major points. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 12:18: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7063214A17; Mon, 8 Nov 1999 12:18:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D87F1CD623; Mon, 8 Nov 1999 12:18:04 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 8 Nov 1999 12:18:04 -0800 (PST) From: Kris Kennaway To: "Jonathan M. Bresler" Cc: T.Pagtzis@cs.ucl.ac.uk, current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE In-Reply-To: <19991108201128.0C5AB14D15@hub.freebsd.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 Mon, 8 Nov 1999, Jonathan M. Bresler wrote: > ps. note this explaination is somewaht simplified, but it accurate in > all its major points. It's also explained quite clearly in the FAQ, for people who care to read it. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 12:23:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 0E6CD150CD for ; Mon, 8 Nov 1999 12:23:25 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Tue, 9 Nov 1999 07:17:29 +1100 Content-return: prohibited Date: Tue, 9 Nov 1999 07:23:15 +1100 From: Peter Jeremy Subject: Re: show stopper for Gcc 2.95.2 conversion In-reply-to: <199911081801.NAA29633@lor.watermarkgroup.com> To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov9.071729est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911081801.NAA29633@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-09 05:01:43 +1100, Luoqi Chen wrote: >> + "=D" (addr), "=c" (count) : >> + "r" (bsh + offset), "0" (addr), "1" (count) : >> + "%eax", "memory"); >You may use "+D" and "+c" for the in-out operands, > "+D" (addr), "+c" (count) : > "r" (bsh + offset) : > Just as a word of caution: "+" isn't supported prior to gcc 2.8.x, so you can't use it for code that might be MFC to 3.x. And just to make it more of a pain, I've found code similar to the original patch also fails on gcc 2.7 when the operands are volatile :-(. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 12:55:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 5CE6E15245; Mon, 8 Nov 1999 12:54:58 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-168.skylink.it [194.185.55.168]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id VAA05326; Mon, 8 Nov 1999 21:55:54 +0100 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id QAA05822; Mon, 8 Nov 1999 16:18:44 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 8 Nov 1999 16:18:44 GMT Date: Mon, 8 Nov 1999 17:18:44 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Kazutaka YOKOTA Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man4/man4.i386 syscons.4 src/sys/i386/conf LINT In-Reply-To: <199911081416.GAA84563@freefall.freebsd.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 A hint for laptop users: Change the ATTR for the normal case if you have a weak display: options SC_NORM_ATTR="(FG_WHITE|BG_BLACK)" options SC_NORM_REV_ATTR="(FG_BLACK|BG_WHITE)" options SC_KERNEL_CONS_ATTR="(FG_YELLOW|BG_BLACK)" options SC_KERNEL_CONS_REV_ATTR="(FG_BLACK|BG_YELLOW)" It makes it much more readable. NIck On Mon, 8 Nov 1999, Kazutaka YOKOTA wrote: > yokota 1999/11/08 06:16:49 PST > > Modified files: > share/man/man4/man4.i386 syscons.4 > sys/i386/conf LINT > Log: > - Document SC_TWOBUTTON_MOUSE, SC_NORM_ATTR, SC_NORM_REV_ATTR, > SC_KERNEL_CONS_ATTR and SC_KERNEL_CONS_REV_ATTR. > > Nudged by eivind > > Revision Changes Path > 1.8 +48 -1 src/share/man/man4/man4.i386/syscons.4 > 1.674 +11 -1 src/sys/i386/conf/LINT > > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 14:24:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1A04D14FBA for ; Mon, 8 Nov 1999 14:23:56 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA10608; Mon, 8 Nov 1999 15:23:47 -0700 (MST) (envelope-from ken) Message-Id: <199911082223.PAA10608@panzer.kdm.org> Subject: Re: TCP sockets stuck in the CLOSING state In-Reply-To: <19991107080903.23572@right.PCS> from Jonathan Lemon at "Nov 7, 1999 08:09:03 am" To: jlemon@americantv.com (Jonathan Lemon) Date: Mon, 8 Nov 1999 15:23:47 -0700 (MST) Cc: des@flood.ping.uio.no (Dag-Erling Smorgrav), current@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Jonathan Lemon wrote... > On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote: > > Note that the state transition diagram in RFC793 does not specify a > > timeout for the CLOSING -> TIME_WAIT transition, so any faithful > > implementation of RFC793 has this bug (but why doesn't this happen on > > -STABLE, or on pre-August -CURRENT?) > > I'm not sure abuot that one. But I've just committed a fix to tcp_fsm.h, > which will cause it to re-transmit a FIN in CLOSING state. The FIN was > originally taken out by Garrett in rev 1.5, and restored by dg in rev 1.6. > However, it was re-removed in 1.10 when Garrett made a large commit, > presumably he hadn't taken it out of his local tree. > > It fixes the problem here (at least, I can't replicate the problem any > more). I'm not sure if I'm fixing the symptoms rather than the actual > problem then, though. NetBSD has the same fix in their tree as well. I've had the fix in use for about a day, and it seems to fix the problem here. I don't have any sockets stuck in the CLOSING state, and from previous experience, I would have at least one or two by now. > I'm pretty sure that I've seen this problem on -current going back as > early as March as well. I don't remember it happening before, but of course that doesn't mean it didn't happen. There's a guy who reported the same problem with -stable on the -isp list. I sent him the patch, and told him to report back to you and the -stable list on whether or not it works. He said that he did not have the problem with 2.2.x machines. If it's happening with -stable, that means the problem has been in the tree for a while (probably since rev 1.10, which was in 1997) and may have just been exacerbated somehow by the timer changes in August. Ken -- Kenneth Merry ken@kdm.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 8 14:54:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 3924815220 for ; Mon, 8 Nov 1999 14:53:52 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 8 Nov 1999 22:53:44 +0000 X-Mailer: exmh version 2.0.2 To: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE In-reply-to: Your message of "Mon, 08 Nov 1999 14:52:28 EST." <19991108145228.C17714@stat.Duke.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Nov 1999 22:53:44 +0000 Message-ID: <1483.942101624@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guys, many thanks for the response. It seems to me though, that there is a vicious circle that the user is locked in. If there are bugs that are resolved in 3.3-STABLE then the 3.4-RC should entail NO new functionality even if this is supplemental. What I mean is that as a user you, (I feel) would expect to buy the RELEASE (which must be surely a stable one) and do you work in much the same fashion as any other product of work (free or commercial). I feel that the people actually purchasing the CD (and price is not the preventive factor) should be having what you call the "-STABLE" version of the OS not the RELEASE. (Beware I am only referring to the CD sales) In that sense I would recommend some change in the naming (or rather numbering) convention which in my book should be 3.2-RELEASE -> 3.3-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.4-STABLE and NOT 3.2-RELEASE -> 3.2-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.3-STABLE Also the bug fixes I suppose that come as a patch to the RELEASE so I do not have to update from CVS (I know how to but some others may not care about CVS). So the RELEASE could be upgradable to the next STABLE by applying a patch (no CVS interaction here). I trust that such patches are indeed existing. I also trust that it is only the -CURRENT that adds any new functionality to the OS which at some point merges with what you call "-STABLE" but the major revision number changes from X.q to Y.0 What are your views? Theo >On 1999 Nov 08, Theo PAGTZIS (aka T.Pagtzis@cs.ucl.ac.uk) wrote: >> >> >> Hi all, >> >> >> just a very basic question that would resolve a dispute between colleagues >. >> >> When one talks about Fbsd3.3-STABLE my impression is that such version is a >> stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the >> final version and the -STABLE is the version that is soon (after some furthe >r >> bug settling) to become -RELEASE. >> >> Is this the case? > >Theo- >On 1999 Nov 08, Theo PAGTZIS (aka T.Pagtzis@cs.ucl.ac.uk) wrote: >> >> >> Hi all, >> >> >> just a very basic question that would resolve a dispute between colleagues >. >> >> When one talks about Fbsd3.3-STABLE my impression is that such version is a >> stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the >> final version and the -STABLE is the version that is soon (after some furthe >r >> bug settling) to become -RELEASE. >> >> Is this the case? > >Theo- > >It's the other way around. Here is approx how we went from 3.2 to present > >3.2-RELEASE -> 3.2-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.3-STABLE > >(where RC is release candidate). > >S >-- >----------------------------------------------------------------------- >Sean O'Connell Email: sean@stat.Duke.EDU >Institute of Statistics and Decision Sciences Phone: (919) 684-5419 >Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 15: 4:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 0C5501510D for ; Mon, 8 Nov 1999 15:04:15 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id SAA76811; Mon, 8 Nov 1999 18:11:29 -0500 (EST) Date: Mon, 8 Nov 1999 18:11:29 -0500 (EST) From: Ben Rosengart To: Theo PAGTZIS Cc: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE In-Reply-To: <1483.942101624@cs.ucl.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 Mon, 8 Nov 1999, Theo PAGTZIS wrote: > What are your views? I think it's fine the way it is. It took me a few minutes to wrap my mind around the FreeBSD release and patching schemata, but ever since then, they've treated me pretty well. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 15:55:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BEECA14BFC for ; Mon, 8 Nov 1999 15:54:57 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40361>; Tue, 9 Nov 1999 10:48:59 +1100 Content-return: prohibited Date: Tue, 9 Nov 1999 10:54:46 +1100 From: Peter Jeremy Subject: Re: ambiguity between -STABLE and -RELEASE In-reply-to: <1483.942101624@cs.ucl.ac.uk> To: Theo PAGTZIS Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov9.104859est.40361@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991108145228.C17714@stat.Duke.EDU> <1483.942101624@cs.ucl.ac.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-09 09:53:44 +1100, Theo PAGTZIS wrote: > If there are bugs that are resolved in >3.3-STABLE then the 3.4-RC should entail NO new functionality even if this is >supplemental. This (presumably) means that new functionality should only be introduced at major releases (eg 3.0, 4.0 etc). This is probably unacceptably slow for most people. Instead, FreeBSD takes the view that minor enhancements can be introduced with new minor releases. In some cases, the line between `minor enahncement' and `bugfix' can get blurred. >In that sense I would recommend some change in the naming (or rather >numbering) convention which in my book should be > >3.2-RELEASE -> 3.3-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.4-STABLE > >and NOT > >3.2-RELEASE -> 3.2-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.3-STABLE The only difference here is how the -STABLE branches are numbered. The 3.x-STABLE numbering does not exist in the CVS tree and is used solely as a mechanism to designate positions on the RELENG_3 branch relative to actual releases (which exist as tags in the CVS tree). For whatever reason, the decision was taken that a reference to x.y-STABLE means a location on the RELENG_x CVS branch later than RELENG_x_y_z_RELEASE. Changing that at this point in time would only cause confusion. It's also worth noting that the -STABLE branch of a release may extend beyond the last release. In particular, a couple of serious problems have been fixed on RELENG_2_2 branch since 2.2.8-RELEASE (and it's possible that future problems may lead to additional fixes on this branch), though there is no intention to ever provide a later -RELEASE off this branch. > So the RELEASE could be upgradable to the next STABLE by applying a >patch (no CVS interaction here). I trust that such patches are indeed >existing. -STABLE is not a fixed point in the CVS tree. It refers to everything between x.y-RELEASE and x.(y+1)-RC. It is fairly simple to produce a set of patches from the CVS tree to convert say 3.3-RELEASE to the `current' -STABLE ("cvs diff -u -r RELENG_3_3_0_RELEASE -r RELENG_3"), but this doesn't help someone who is running -STABLE from last month. In general, it is assumed that anyone who wants to follow -STABLE will be tracking the CVS tree. If you want bugfixes, but can't track -STABLE, you have three options: - wait for the next -RELEASE - use the -STABLE snapshots that appear from time-to-time. - find someone who can provide you with customised support. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 16: 5:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 54CBA150F0; Mon, 8 Nov 1999 16:05:48 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 16D5B1927; Tue, 9 Nov 1999 01:06:06 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 15A2B49D2; Tue, 9 Nov 1999 01:06:06 +0100 (CET) Date: Tue, 9 Nov 1999 01:06:06 +0100 (CET) From: Andrzej Bialecki To: Soren Schmidt Cc: Kazutaka YOKOTA , sos@freebsd.org, freebsd-current@freebsd.org Subject: Re: libvgl - status and perspectives In-Reply-To: <199911080907.KAA91100@freebsd.dk> 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, 8 Nov 1999, Soren Schmidt wrote: > It seems Andrzej Bialecki wrote: > > > > > > Oops, sos and I have developed a new version of libsvgl which can > > > handle VESA modes in addition to the standard VGA graphics modes. > > > But I haven't committed it to the source tree yet (yes, I should have > > > done so weeks ago ;-( > > > > > > Anyway, if you are interested, I can send you a copy for testing. > > > > Yes, sort of... You see, with libvgl I ended up implementing most of the > > events abstraction myself - libvgl seriously lacks this (among others). > > So, of course new VESA modes are very interesting, but what would be > > really cool is more general framework for graphical terminal handling. > > Hmm, libvgl was originally only thought as a way to do simple graphics > on the console, nothing more. What exactly is it you need ?? Things like mouse/key events and queues thereof, filled/patterned shapes and lines, draw modes (even BGI drivers could do that!) are the most important that come to mind... "Events" for me means that I can call an API which will deliver pending information about keypresses, mouse movemnts and buttons, without writing that select/read/ioctl/enqueue/compress hassle you have to do now each time you want to see if something happened. > (And I'm not suggesting that I have the time to do it :) ) Me neither... :-) I'm just in complaining mode, I guess... > > > >But this brings more general question regarding console graphics library. > > > >As it is today, libvgl is almost useless due to very limited set of > > > >functions. There were discussions whether to port SVGAlib or GGI. Do you > > > >know if someone is working/planning to work on it? > > > > Do you know something about this? > > I think you all know my feelings about svgalib so I wont comment on that > one. I havn't been following the GGI project lately so I dont know what > they have achived, but last time I looked it had a loooong way to go to > be minimally usefull, and their kernel stuff was, well, not something I'd > put into our kernel.... > Anyhow, I think we have what can be currently done resonably in the kernel > its just a matter of how you should interface to it. Remember that VESA Any docs for e.g.the fb device? I know,you can always UTSL, but it takes more time. OBTW. there is an error in mouse(4) manpage. The ioctl is called MOUSE_GETSTATUS, not MOUSE_GETSTATE as the manpage claims. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: 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 Mon Nov 8 16:20:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id E31E11532A for ; Mon, 8 Nov 1999 16:20:07 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-26.iptelecom.net.ua [212.9.227.90]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA09883; Tue, 9 Nov 1999 02:22:49 +0200 (EET) Message-ID: <38276863.F71C2915@altavista.net> Date: Tue, 09 Nov 1999 02:18:44 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: rm error code on FAT References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Mon, 8 Nov 1999, Maxim Sobolev wrote: > > > Does anybody can explain why two absolutely identical attempts to remove > > unexistent files on UFS and FAT32 yields different error codes ("No such > > file or directory" and "Invalid argument" respectively)? This breaks "rm > > -f" behaviour, because instead of expected "0", "rm -f" on FAT returns > > error code instead. > > unlink("/mnt/*.no_such_files") on msdosfs returns EINVAL because the > pathname contains the invalid character '*'. EINVAL used to be a > documented errno for pathnames containing characters with their high > bit set). This documentation should have been made filesystem- > dependent instead of removing it. If your logic is right, then attempt to remove existent files from FAT using '*' should yield absolutely the same result (i.e. EINVAL). But in fact files being removed from FAT w/o any problems (touch /fat/1.exist /fat/2.exist ; rm /*.exist). IMHO it is clear bug in unlink error codes on FAT f/s. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 16:41:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 0651F14BFC for ; Mon, 8 Nov 1999 16:41:21 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id SAA24668; Mon, 8 Nov 1999 18:39:24 -0600 (CST) Date: Mon, 8 Nov 1999 18:39:23 -0600 From: "Matthew D. Fuller" To: Maxim Sobolev Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: rm error code on FAT Message-ID: <19991108183923.C393@futuresouth.com> References: <38276863.F71C2915@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <38276863.F71C2915@altavista.net> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me that Maxim Sobolev remarked > > If your logic is right, then attempt to remove existent files from FAT using > '*' should yield absolutely the same result (i.e. EINVAL). But in fact files > being removed from FAT w/o any problems (touch /fat/1.exist /fat/2.exist ; rm > /*.exist). IMHO it is clear bug in unlink error codes on FAT f/s. I think you'll find that the '*' in that case is expanded by your shell long before rm ever gets to it. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 16:56:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id CCFC915132 for ; Mon, 8 Nov 1999 16:56:28 -0800 (PST) (envelope-from nppsecure@distortion.dk) Received: from localhost (nppsecure@localhost) by distortion.dk (8.9.3/8.9.1) with ESMTP id BAA77717 for ; Tue, 9 Nov 1999 01:57:36 +0100 (CET) (envelope-from nppsecure@distortion.dk) Date: Tue, 9 Nov 1999 01:57:35 +0100 (CET) From: Nicolai Petri Secure To: current@freebsd.org Subject: Compaq RAID driver (ida) id0 vs ida0 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 Why is the /dev names ida0?? for the disk when the kernel are trying to mount rootdev to id0??? (Guess what... It is'nt compatibel ;) What is the right thing ? And were should it be fixed ??? --- Nicolai Petri WM-data Bfc Denmark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 16:59:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 0424014A03 for ; Mon, 8 Nov 1999 16:59:18 -0800 (PST) (envelope-from nppsecure@distortion.dk) Received: from localhost (nppsecure@localhost) by distortion.dk (8.9.3/8.9.1) with ESMTP id CAA77901 for ; Tue, 9 Nov 1999 02:00:25 +0100 (CET) (envelope-from nppsecure@distortion.dk) Date: Tue, 9 Nov 1999 02:00:25 +0100 (CET) From: Nicolai Petri Secure To: current@freebsd.org Subject: Stats in kernelmode (Screensaver) 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'm currently programming a screensaver the shows statistics (cpu load and stuff) but the interface for doing it in kernel mode sucks.. What is the right way to do it ? And would the screensaver be subject for entering the main source tree ? --- Nicolai Petri WM-data Bfc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 17:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id CAADB1523D for ; Mon, 8 Nov 1999 17:13:22 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-60.iptelecom.net.ua [212.9.227.124]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id DAA17033; Tue, 9 Nov 1999 03:15:47 +0200 (EET) Message-ID: <382774CD.2305EDDA@altavista.net> Date: Tue, 09 Nov 1999 03:11:41 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Matthew D. Fuller" Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: rm error code on FAT References: <38276863.F71C2915@altavista.net> <19991108183923.C393@futuresouth.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" wrote: > On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me > that Maxim Sobolev remarked > > > > If your logic is right, then attempt to remove existent files from FAT using > > '*' should yield absolutely the same result (i.e. EINVAL). But in fact files > > being removed from FAT w/o any problems (touch /fat/1.exist /fat/2.exist ; rm > > /*.exist). IMHO it is clear bug in unlink error codes on FAT f/s. > > I think you'll find that the '*' in that case is expanded by your shell > long before rm ever gets to it. *sigh* (seems it is time for me to go into the bed ;). You are probably right - it seems I forgot to take into account shell role. So it is pure and unavoidable "feature" of FAT.... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 17:36: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 1708915345 for ; Mon, 8 Nov 1999 17:36:05 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id TAA18940; Mon, 8 Nov 1999 19:36:04 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id TAA01856; Mon, 8 Nov 1999 19:36:03 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id TAA28789; Mon, 8 Nov 1999 19:36:03 -0600 (CST) Date: Mon, 8 Nov 1999 19:36:03 -0600 (CST) From: Jonathan Lemon Message-Id: <199911090136.TAA28789@free.pcs> To: nppsecure@distortion.dk, current@freebsd.org Subject: Re: Compaq RAID driver (ida) id0 vs ida0 X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >Why is the /dev names ida0?? for the disk when the kernel are trying to >mount rootdev to id0??? (Guess what... It is'nt compatibel ;) ``ida'' is the name of the controller. ``id'' is the name of the disk. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 8 18:42:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2F94C14F8D; Mon, 8 Nov 1999 18:42:45 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA91240; Mon, 8 Nov 1999 19:42:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA14441; Mon, 8 Nov 1999 19:42:09 -0700 (MST) Message-Id: <199911090242.TAA14441@harmony.village.org> To: "Bill A. K." Subject: Re: PCI Hardware Modem (Really) Cc: "FreeBSD Questions" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 15 Oct 1999 18:32:01 EDT." <001801bf175d$1a9a9940$05012ccf@bopper> References: <001801bf175d$1a9a9940$05012ccf@bopper> Date: Mon, 08 Nov 1999 19:42:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001801bf175d$1a9a9940$05012ccf@bopper> "Bill A. K." writes: : I've got a Rockwell PCI Modem thats full hardware, and I was wondering : if anybody has written a driver for this kind yet. I have written a driver for the pci hardware modems in -stable under contract. I plan to port it to current soon, if Peter Wemm hasn't already integrated it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 0:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 5C8121507E for ; Tue, 9 Nov 1999 00:44:32 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p50-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id TAA22973; Tue, 9 Nov 1999 19:50:02 +1100 Date: Tue, 9 Nov 1999 19:44:08 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Jonathan Lemon Cc: nppsecure@distortion.dk, current@FreeBSD.ORG Subject: Re: Compaq RAID driver (ida) id0 vs ida0 In-Reply-To: <199911090136.TAA28789@free.pcs> 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, 8 Nov 1999, Jonathan Lemon wrote: > In article you write: > > > >Why is the /dev names ida0?? for the disk when the kernel are trying to > >mount rootdev to id0??? (Guess what... It is'nt compatibel ;) > > ``ida'' is the name of the controller. ``id'' is the name of the disk. MAKEDEV is confused about the difference and creates wrong names for ``id'' disks (``ida'' instead of ``id''). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 2:12:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8F91E14E27 for ; Tue, 9 Nov 1999 02:12:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA85502; Tue, 9 Nov 1999 02:11:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Theo PAGTZIS Cc: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE In-reply-to: Your message of "Mon, 08 Nov 1999 22:53:44 GMT." <1483.942101624@cs.ucl.ac.uk> Date: Tue, 09 Nov 1999 02:11:42 -0800 Message-ID: <85498.942142302@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't agree with any of this, I'm afraid. The specific model we have today was evolved with reasonable purpose. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 3:49:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 48BFC14D4A for ; Tue, 9 Nov 1999 03:49:26 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:p7SPgNVakJiEBZKJ3JIoNThmwhNDw2EI@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id UAA17469; Tue, 9 Nov 1999 20:49:22 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA16821; Tue, 9 Nov 1999 20:54:00 +0900 (JST) Message-Id: <199911091154.UAA16821@zodiac.mech.utsunomiya-u.ac.jp> To: Andrzej Bialecki Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: libvgl - status and perspectives In-reply-to: Your message of "Tue, 09 Nov 1999 01:06:06 +0100." References: Date: Tue, 09 Nov 1999 20:53:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Any docs for e.g.the fb device? I know,you can always UTSL, but it takes >more time. No docs yet, sorry. >OBTW. there is an error in mouse(4) manpage. The ioctl is called >MOUSE_GETSTATUS, not MOUSE_GETSTATE as the manpage claims. Thank you for spotting the error! I will fix it. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 4: 2: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 6EFEE14D4A for ; Tue, 9 Nov 1999 04:02:00 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id NAA08687; Tue, 9 Nov 1999 13:03:03 +0100 (CET) To: current@freebsd.org Subject: inconsistent and wrong locking in asleep() Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 09 Nov 1999 13:03:03 +0100 Message-ID: <5l4sevrhxk.fsf@assaris.sics.se> Lines: 27 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [re-sending a mail that went unanswered by -hackers] Why trying to debug some locking code of my own I enabled SIMPLELOCK_DEBUG, only to find out that I was getting lots of `simple_unlock: lock not held' in lockmgr -> acquire -> apause. Looking closer at `apause' it seems rather clear that it can cause this. I proposed simple change is below. Comments? /assar --- kern_lock.c.orig Mon Nov 8 03:55:26 1999 +++ kern_lock.c Mon Nov 8 04:24:13 1999 @@ -116,9 +119,11 @@ simple_lock(&lkp->lk_interlock); if ((lkp->lk_flags & flags) == 0) return 0; + simple_unlock(&lkp->lk_interlock); break; } } + simple_lock(&lkp->lk_interlock); } return 1; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 5:30:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2DFD814FD9 for ; Tue, 9 Nov 1999 05:30:28 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p50-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA04696; Wed, 10 Nov 1999 00:36:08 +1100 Date: Wed, 10 Nov 1999 00:30:12 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: inconsistent and wrong locking in asleep() In-Reply-To: <5l4sevrhxk.fsf@assaris.sics.se> 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 > Why trying to debug some locking code of my own I enabled > SIMPLELOCK_DEBUG, only to find out that I was getting lots of > `simple_unlock: lock not held' in lockmgr -> acquire -> apause. > > Looking closer at `apause' it seems rather clear that it can cause > this. I proposed simple change is below. That's a really old bug. I fixed it a year or two ago in my version, and optimised the !SMP case following a suggestion of tegge (waiting for the lock is useless in the !SMP case). Bruce diff -c2 kern_lock.c~ kern_lock.c *** kern_lock.c~ Tue Sep 28 06:06:16 1999 --- kern_lock.c Tue Sep 28 06:07:59 1999 *************** *** 104,125 **** */ static int ! apause(struct lock *lkp, int flags) { ! int lock_wait; ! lock_wait = LOCK_WAIT_TIME; ! for (; lock_wait > 0; lock_wait--) { ! int i; ! if ((lkp->lk_flags & flags) == 0) ! return 0; simple_unlock(&lkp->lk_interlock); ! for (i = LOCK_SAMPLE_WAIT; i > 0; i--) { ! if ((lkp->lk_flags & flags) == 0) { ! simple_lock(&lkp->lk_interlock); ! if ((lkp->lk_flags & flags) == 0) ! return 0; break; ! } ! } } ! return 1; } --- 103,126 ---- */ static int ! apause(struct lock *lkp, int flags) ! { ! #ifdef SMP ! int i, lock_wait; ! #endif ! ! if ((lkp->lk_flags & flags) == 0) ! return (0); ! #ifdef SMP ! for (lock_wait = LOCK_WAIT_TIME; lock_wait > 0; lock_wait--) { simple_unlock(&lkp->lk_interlock); ! for (i = LOCK_SAMPLE_WAIT; i > 0; i--) ! if ((lkp->lk_flags & flags) == 0) break; ! simple_lock(&lkp->lk_interlock); ! if ((lkp->lk_flags & flags) == 0) ! return (0); } ! #endif ! return (1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 6:57:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 61C1414A06 for ; Tue, 9 Nov 1999 06:57:17 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id PAA08895; Tue, 9 Nov 1999 15:10:29 +0100 (CET) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: inconsistent and wrong locking in asleep() References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 09 Nov 1999 15:10:28 +0100 In-Reply-To: Bruce Evans's message of "Wed, 10 Nov 1999 00:30:12 +1100 (EST)" Message-ID: <5lg0yfn4bv.fsf@assaris.sics.se> Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > That's a really old bug. I fixed it a year or two ago in my version, > and optimised the !SMP case following a suggestion of tegge (waiting > for the lock is useless in the !SMP case). Looks fine. Can you commit your patch? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 10:49:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CD10D15312 for ; Tue, 9 Nov 1999 10:49:19 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p18-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.147]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA11027; Wed, 10 Nov 1999 03:49:05 +0900 (JST) Message-ID: <382808F3.B860620A@newsguy.com> Date: Tue, 09 Nov 1999 20:43:47 +0900 From: "Daniel C. Sobral" Reply-To: questions@freebsd.org X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Theo PAGTZIS Cc: current@FreeBSD.ORG Subject: Re: ambiguity between -STABLE and -RELEASE References: <1483.942101624@cs.ucl.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Theo PAGTZIS wrote: > [diet quote] > What are your views? My views are: 1) This message is off-topic. It should have been sent to -questions, or, at most, -stable. It definetely does not belong in -current. 2) You should read the FAQ and the handbook before making suggestions and "supposing" things. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 11:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1395914EA1 for ; Tue, 9 Nov 1999 11:26:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA03009; Tue, 9 Nov 1999 11:26:51 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Nov 1999 11:26:51 -0800 (PST) From: Matthew Dillon Message-Id: <199911091926.LAA03009@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: need patch review - NFS fixes for IP binding Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch is available at: http://www.backplane.com/FreeBSD4/ The patch attempts to solve PR kern/13049 in a slightly different manner then the solution given by Ian in the PR. In a nutshell, the problem that we have is that nfsd may return a respond to an NFS request from a different IP then it was sent to on multihomed systems. The PR attempts to solve the problem by allowing the kernel nfsd's to be bound to multiple IP addresses, which is ok, but it also makes nfsd bind to every imagineable IP address which is often not what you want to do. Instead, I have adopted and cleaned up the kernel portions of the patch and modified nfsd to allow the binding ip/host to be specified on the command line. Thus nfsd can be run bound to a specific IP address. This appears to solve the problem and should also allow more useable interaction between nfs and ipfw. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 11:29:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 7643214EA1 for ; Tue, 9 Nov 1999 11:29:20 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id UAA24539; Tue, 9 Nov 1999 20:27:46 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E8F.dip.t-dialin.net [62.158.14.143]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id UAA24519; Tue, 9 Nov 1999 20:27:40 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id UAA15181; Tue, 9 Nov 1999 20:27:59 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <382875A7.FE47C781@dead-end.net> Date: Tue, 09 Nov 1999 20:27:35 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Maxim Sobolev Cc: "Matthew D. Fuller" , Bruce Evans , current@FreeBSD.ORG Subject: Re: rm error code on FAT References: <38276863.F71C2915@altavista.net> <19991108183923.C393@futuresouth.com> <382774CD.2305EDDA@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > "Matthew D. Fuller" wrote: > > > On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me > > that Maxim Sobolev remarked > > > > > > If your logic is right, then attempt to remove existent files from FAT using > > > '*' should yield absolutely the same result (i.e. EINVAL). But in fact files > > > being removed from FAT w/o any problems (touch /fat/1.exist /fat/2.exist ; rm > > > /*.exist). IMHO it is clear bug in unlink error codes on FAT f/s. > > > > I think you'll find that the '*' in that case is expanded by your shell > > long before rm ever gets to it. > > *sigh* (seems it is time for me to go into the bed ;). You are probably right - it > seems I forgot to take into account shell role. > > So it is pure and unavoidable "feature" of FAT.... Wildcards only get expanded by the shell if there is something to expand. Just write an "echo" instead of "rm" for your command and see by yourself. csh would show the error message "no match", but sh compatible shells just display: # mkdir empty # cd empty # echo *xtra *xtra So in fact, if you try to remove something, the '*' is indeed part of the filename for the unlink() command. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 11:34:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 0643D14EA1 for ; Tue, 9 Nov 1999 11:34:17 -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.9.3/8.9.3) with SMTP id MAA25910; Tue, 9 Nov 1999 12:34:16 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA07002; Tue, 9 Nov 1999 12:34:15 -0700 Date: Tue, 9 Nov 1999 12:34:15 -0700 Message-Id: <199911091934.MAA07002@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: need patch review - NFS fixes for IP binding In-Reply-To: <199911091926.LAA03009@apollo.backplane.com> References: <199911091926.LAA03009@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Instead, I have adopted and cleaned up the kernel portions of the patch > and modified nfsd to allow the binding ip/host to be specified on the > command line. Thus nfsd can be run bound to a specific IP address. This sounds like a great solution, thanks Matt! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 12:13: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 6821614C94 for ; Tue, 9 Nov 1999 12:12:52 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id VAA9814793 for ; Tue, 9 Nov 1999 21:12:50 +0100 (CET) Received: from work.net.local (maxtnt-156.telip.uni-sb.de [134.96.71.27]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id VAA10041 for ; Tue, 9 Nov 1999 21:12:52 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id VAA04078 for ; Tue, 9 Nov 1999 21:12:40 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911092012.VAA04078@work.net.local> Date: Tue, 9 Nov 1999 21:12:39 +0100 (CET) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: "man" reads /etc/rc.conf? To: current@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 Hi, -current from Nov 9: (101) netchild@ttyp2 > man -k adadadad cat: /etc/isdn/connect.parameters: Permission denied adadadad: nothing appropriate (102) netchild@ttyp2 > grep cat /etc/rc.conf.local spppconfig_isp0="`cat /etc/isdn/connect.parameters`" Is this just my system or is man really reading rc.conf(.local)? Bye, Alexander. -- I thought I wanted a career, turns out I just wanted paychecks. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 13:27: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 014F91537E for ; Tue, 9 Nov 1999 13:26:49 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from maccullagh.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Nov 1999 21:26:47 +0000 (GMT) Date: Tue, 9 Nov 1999 21:26:47 +0000 From: David Malone To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: need patch review - NFS fixes for IP binding Message-ID: <19991109212647.A11812@maccullagh.maths.tcd.ie> References: <199911091926.LAA03009@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911091926.LAA03009@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 09, 1999 at 11:26:51AM -0800, Matthew Dillon wrote: > Instead, I have adopted and cleaned up the kernel portions of the patch > and modified nfsd to allow the binding ip/host to be specified on the > command line. Thus nfsd can be run bound to a specific IP address. This patch isn't very good for us as we need to be able to bind nfsd to several IP addresses and still have it reply on the correct interface and I think your patch only allows one to be specified per set of nfsds? At the least we need to be able to specify multiple IP addresses and a "all IP addresses" mode, as in Ian's original patch, would be useful for us. I guess we could run bunches of nfsds - one bunch per IP, but this seems unnatural. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 13:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 1246815335 for ; Tue, 9 Nov 1999 13:27:48 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA35683; Tue, 9 Nov 1999 13:27:43 -0800 (PST) From: Archie Cobbs Message-Id: <199911092127.NAA35683@bubba.whistle.com> Subject: Re: "man" reads /etc/rc.conf? In-Reply-To: <199911092012.VAA04078@work.net.local> from "A.Leidinger@WJPServer.CS.Uni-SB.de" at "Nov 9, 1999 09:12:39 pm" To: A.Leidinger@WJPServer.CS.Uni-SB.de Date: Tue, 9 Nov 1999 13:27:43 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 A.Leidinger@WJPServer.CS.Uni-SB.de writes: > (101) netchild@ttyp2 > man -k adadadad > cat: /etc/isdn/connect.parameters: Permission denied > adadadad: nothing appropriate > > (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > spppconfig_isp0="`cat /etc/isdn/connect.parameters`" > > Is this just my system or is man really reading rc.conf(.local)? ktrace(1) would tell for sure.. -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 Tue Nov 9 13:57:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 88B091538F for ; Tue, 9 Nov 1999 13:56:58 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id WAA53916; Tue, 9 Nov 1999 22:56:35 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (pC19F8466.dip.t-dialin.net [193.159.132.102]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id WAA53912; Tue, 9 Nov 1999 22:56:34 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id WAA15963; Tue, 9 Nov 1999 22:54:44 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3828980A.9BA70807@dead-end.net> Date: Tue, 09 Nov 1999 22:54:18 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: current@freebsd.org Subject: Re: ESS 1868 driver, again References: <19991107053836.783251C03@overcee.netplex.com.au> <38259147.1CEA1833@dead-end.net> <38286BF4.120ED917@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > "D. Rock" wrote: > > > > options HZ=500 > > Without this line, do things work? No, but I finally got an at least partial solution: I had to configure to use DMA channels 1,0 (it used to be 1,5). Even 0,1 didn't work. With this setup I was able to play music files again. But: I normally use mpg123 to play audio files. I use ^C to skip to the next file. Sometimes the device doesn't seem to get reset properly and I only get noise. Skipping 1-2 files again usually solves this problem. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 17:10: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 629931515E for ; Tue, 9 Nov 1999 17:09:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA95061; Tue, 9 Nov 1999 18:09:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA02887; Tue, 9 Nov 1999 18:08:41 -0700 (MST) Message-Id: <199911100108.SAA02887@harmony.village.org> To: Will Andrews Subject: Re: pcic.ko & recent changes to sys/pccard/* Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Oct 1999 03:26:14 EDT." <199910180726.DAA64055@shadow.blackdawn.com> References: <199910180726.DAA64055@shadow.blackdawn.com> Date: Tue, 09 Nov 1999 18:08:41 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ Catching up with my mail from FreeBSD con ]] In message <199910180726.DAA64055@shadow.blackdawn.com> Will Andrews writes: : Thus, /dev/card0 is reported as "Device not configured" : upon boot (because kldload can't find pcic.ko in /modules : or elsewhere). There is no support for pcic as a module doesn't work and no effort will be expended looking for problems with it whatsoever. This has been my position for months now, so if pcic was working for you before my massive checkin, it was pure luck. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 22:28: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 4AB4314DE5 for ; Tue, 9 Nov 1999 22:27:55 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id BAA22343 for ; Wed, 10 Nov 1999 01:09:08 -0500 (EST) Date: Wed, 10 Nov 1999 01:27:01 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Idea for console graphics library 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 There's been a lot of talk about a console graphics library. First off, you'd have to maintain a library of drivers for each video card. So, I suggest this: Why don't we or the XFree86 project fork off a branch dedicated to console graphics? Most of the code necessary is in the XFree86 Xserver. We could just yank out most of the driver and graphics card drivers from XFree86's latest 3.95.16 snapshot. We could make a set of FreeBSD lkm's that we could load on demand if necessary. This would enable us to have something like Linux's `fbcon'. The idea is to separate the graphics drivers from XFree86, and have them running on the console. Then, when startx is invoked, the rest of the Xserver code would just load. That way, some sort of graohics graphics could be running all the time, and the Xserver would just dynamically link with the console grahics when `startx' is invoked. But, the graphics driver would be running all the time, and we could use this graphics mode in lieu of the basic text mode that is in most VGA cards. I've heard that the VGA standard wants to get rid of text mode, and just go with graphics mode anyway. With the idea above, a `partial' Xserver would always be running as part of the system console. Of course, it's not a full Xserver, so it wouldn't be as bloated as actually fully running X with startx. The `full' Xserver would only come into play when startx is invoked. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 23:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4726014A00 for ; Tue, 9 Nov 1999 23:22:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA05191; Tue, 9 Nov 1999 23:21:53 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Nov 1999 23:21:53 -0800 (PST) From: Matthew Dillon Message-Id: <199911100721.XAA05191@apollo.backplane.com> To: David Malone Cc: freebsd-current@FreeBSD.ORG Subject: Re: need patch review - NFS fixes for IP binding References: <199911091926.LAA03009@apollo.backplane.com> <19991109212647.A11812@maccullagh.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This patch isn't very good for us as we need to be able to bind :nfsd to several IP addresses and still have it reply on the correct :interface and I think your patch only allows one to be specified :per set of nfsds? : :At the least we need to be able to specify multiple IP addresses :and a "all IP addresses" mode, as in Ian's original patch, would :be useful for us. : :I guess we could run bunches of nfsds - one bunch per IP, but this :seems unnatural. : : David. You can run a set of nfsd's on each IP that you want to bind to with the patch. While it is true that this doesn't solve the problem universally, it does solve the problem for most people while at the same time implementing more appropriate security characteristics. It just isn't a good idea to go binding to every interface IP address in existance -- I know web servers with hundreds of IP aliases that would simply blow up if we were to try to do that, and other servers with hundreds of discrete, dynamically changing interfaces (e.g. virtual frame interfaces). 'named' went the 'bind to everything' route and it was six years before the bugs got worked out of it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 9 23:56:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 13E3E14DE5 for ; Tue, 9 Nov 1999 23:55:54 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id IAA11894; Wed, 10 Nov 1999 08:55:46 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id IAA19370; Wed, 10 Nov 1999 08:55:46 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:mSJQrsXK6OR5cOyew3KqRRH+bSW9JcQS@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/8.9.1/wjp-SVR4/1998063000) with ESMTP id IAA17061; Wed, 10 Nov 1999 08:55:43 +0100 (CET) Message-Id: <199911100755.IAA17061@wurzelausix.cs.uni-sb.de> Date: Wed, 10 Nov 1999 08:55:41 +0100 (CET) From: Alexander Leidinger Subject: Re: "man" reads /etc/rc.conf? To: archie@whistle.com Cc: current@FreeBSD.ORG In-Reply-To: <199911092127.NAA35683@bubba.whistle.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Nov, Archie Cobbs wrote: >> (101) netchild@ttyp2 > man -k adadadad >> cat: /etc/isdn/connect.parameters: Permission denied >> adadadad: nothing appropriate >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" >> >> Is this just my system or is man really reading rc.conf(.local)? > > ktrace(1) would tell for sure.. Yes, but I'm shure it reads it without using ktrace. rc.conf.local is the only place where I have a "cat /etc/isdn/...." (I've looked into /etc/defaults/{rc,man}.conf and /etc/{rc,man}.conf{,.local}). I will try ktrace later (back at home), if someone wants to see the output request it please. Bye, Alexander. -- Actually, a more important date is January 1, 2000, when many computer programs across the world could break. Richard W. Stevens, Advanced Programming in the UNIX Environment, _1993_ http://netchild.home.pages.de A.Leidinger @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 1: 1:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rmstar.campus.luth.se (rmstar.campus.luth.se [130.240.197.32]) by hub.freebsd.org (Postfix) with ESMTP id 33BA815329 for ; Wed, 10 Nov 1999 01:01:09 -0800 (PST) (envelope-from murduth@rmstar.campus.luth.se) Received: from rmstar.campus.luth.se (localhost [127.0.0.1]) by rmstar.campus.luth.se (8.9.3/8.9.3) with ESMTP id KAA02514 for ; Wed, 10 Nov 1999 10:01:08 +0100 (CET) (envelope-from murduth@rmstar.campus.luth.se) Message-Id: <199911100901.KAA02514@rmstar.campus.luth.se> X-Mailer: exmh version 2.0.3 3/22/98 To: freebsd-current@freebsd.org Subject: Hosed fs? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Nov 1999 10:01:07 +0100 From: Joakim Henriksson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, i can reproducible get a panic in cluster_alloc(), with a kernel a couple of days old. The code relevant to the panic is this. for (i = 1; i <= len; i++) if (!ffs_isblock(fs, cg_blksfree(cgp), got - run + i)) panic("ffs_clusteralloc: map mismatch"); Do i have a hosed fs? Since i've gotten a crashdump i can provide more information if needded, but i need this resolved soonish. So i'm thinking on newfs'ing the disk. Is this overkill or the right medicine for the patient? From the crashdump i've gotten: IdlePTD 2981888 initial pcb at 261b80 panicstr: ffs_clusteralloc: map mismatch #2 0xc019d785 in ffs_clusteralloc (ip=0xc0db0100, cg=116, bpref=3830648, len=14) at ../../ufs/ffs/ffs_alloc.c:1179 1179 panic("ffs_clusteralloc: map mismatch"); (kgdb) print *ip $1 = {i_lock = {lk_interlock = {lock_data = 0}, lk_flags = 1024, lk_sharecount = 0, lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0xc022623a "inode", lk_timo = 0, lk_lockholder = 478}, i_hash = {le_next = 0x0, le_prev = 0xc0b45d38}, i_vnode = 0xc8f5aa00, i_devvp = 0xc83dbd40, i_flag = 143, i_dev = 0xc0b6be00, i_number = 809794, i_effnlink = 1, inode_u = {fs = 0xc0b6a000, e2fs = 0xc0b6a000}, i_dquot = { 0x0, 0x0}, i_modrev = 1759102206296, i_lockf = 0x0, i_count = 0, i_endoff = 0, i_diroff = 0, i_offset = 0, i_ino = 0, i_reclen = 0, i_spare = {0, 0, 0, 0}, i_din = {di_mode = 33188, di_nlink = 1, di_u = { oldids = {0, 0}, inumber = 0}, di_size = 196452352, di_atime = 942168222, di_atimensec = 0, di_mtime = 942167624, di_mtimensec = 0, di_ctime = 942167624, di_ctimensec = 0, di_db = { 3363320, 3363328, 3363336, 3363344, 3363352, 3363360, 3363368, 3363376, 3363384, 3363392, 3363400, 3363408}, di_ib = {3797336, 3903352, 0}, di_flags = 0, di_blocks = 383904, di_gen = 1801554013, di_uid = 0, (kgdb) print *fs $3 = {fs_firstfield = 0, fs_unused_1 = 0, fs_sblkno = 16, fs_cblkno = 24, fs_iblkno = 32, fs_dblkno = 1024, fs_cgoffset = 2048, fs_cgmask = -1, fs_time = 942168235, fs_size = 17106170, fs_dsize = 16578961, fs_ncg = 523, fs_bsize = 8192, fs_fsize = 1024, fs_frag = 8, fs_minfree = 8, fs_rotdelay = 0, fs_rps = 60, fs_bmask = -8192, fs_fmask = -1024, fs_bshift = 13, fs_fshift = 10, fs_maxcontig = 15, fs_maxbpg = 2048, fs_fragshift = 3, fs_fsbtodb = 1, fs_sbsize = 2048, fs_csmask = -512, fs_csshift = 9, fs_nindir = 2048, fs_inopb = 64, fs_nspf = 2, fs_optim = 0, fs_npsect = 4096, fs_interleave = 1, fs_trackskew = 0, fs_id = {938721534, 1833775959}, fs_csaddr = 1024, fs_cssize = 9216, fs_cgsize = 6144, fs_ntrak = 1, fs_nsect = 4096, fs_spc = 4096, fs_ncyl = 8353, fs_cpg = 16, fs_ipg = 7936, fs_fpg = 32768, fs_cstotal = {cs_ndir = 24416, cs_nbfree = 516378, cs_nifree = 3945722, cs_nffree = 63650}, fs_fmod = 0 '\000', fs_clean = 0 '\000', fs_ronly = 0 '\000', fs_flags = 2 '\002', fs_fsmnt = "/usr", '\000' , fs_cgrotor = 426, fs_csp = {0xc0b8a000, 0xc0b8c000, 0x0 }, fs_maxcluster = 0xc0b8c400, fs_cpc = 0, fs_opostbl = {{0, 0, 0, 0, 0, 0, 0, 0} }, fs_sparecon = {0 }, fs_contigsumsize = 15, fs_maxsymlinklen = 60, fs_inodefmt = 2, fs_maxfilesize = 8796093022207, fs_qbmask = 8191, fs_qfmask = 1023, fs_state = 0, fs_postblformat = 1, fs_nrpos = 1, fs_postbloff = 0, fs_rotbloff = 0, fs_magic = 72020, fs_space = ""} (kgdb) print *cgp $6 = {cg_firstfield = 0, cg_magic = 590421, cg_time = 942168235, cg_cgx = 116, cg_ncyl = 16, cg_niblk = 7936, cg_ndblk = 32768, cg_cs = {cs_ndir = 50, cs_nbfree = 373, cs_nifree = 7720, cs_nffree = 47}, cg_rotor = 29688, cg_frotor = 29688, cg_irotor = 206, cg_frsum = {0, 2, 0, 0, 0, 1, 2, 4}, cg_btotoff = 168, cg_boff = 232, cg_iusedoff = 264, cg_freeoff = 1256, cg_nextfreeoff = 5924, cg_clustersumoff = 5348, cg_clusteroff = 5412, cg_nclusterblks = 4096, cg_sparecon = {0 }, cg_space = "\001"} (kgdb) print run $7 = 14 (kgdb) (kgdb) print i $8 = 11 (kgdb) print got $9 = 3786 (kgdb) (kgdb) print got - run + i $10 = 3783 (kgdb) -- regards/ Joakim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 5:43:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 7218C14E1F for ; Wed, 10 Nov 1999 05:43:08 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id OAA10302717; Wed, 10 Nov 1999 14:43:04 +0100 (CET) Received: from work.net.local (maxtnt-211.telip.uni-sb.de [134.96.71.82]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id OAA22499; Wed, 10 Nov 1999 14:43:05 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id NAA01228; Wed, 10 Nov 1999 13:47:47 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911101247.NAA01228@work.net.local> Date: Wed, 10 Nov 1999 13:47:46 +0100 (CET) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: Re: "man" reads /etc/rc.conf? To: archie@whistle.com Cc: current@FreeBSD.ORG In-Reply-To: <199911092127.NAA35683@bubba.whistle.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Nov, Archie Cobbs wrote: > A.Leidinger@WJPServer.CS.Uni-SB.de writes: >> (101) netchild@ttyp2 > man -k adadadad >> cat: /etc/isdn/connect.parameters: Permission denied >> adadadad: nothing appropriate >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" >> >> Is this just my system or is man really reading rc.conf(.local)? > > ktrace(1) would tell for sure.. /usr/bin/apropos contains: ---snip--- # If possible check global system configuration file for additional # man locales installed if [ -r /etc/defaults/rc.conf ] ; then . /etc/defaults/rc.conf elif [ -r /etc/rc.conf ] ; then . /etc/rc.conf fi ---snip--- and /etc/defaults/rc.conf: ---snip--- man_locales="NO" # space separated list of man locales (or NO) ---snip--- Do we have to live with this or is it subject to change (it gives me a bad taste to have rc.conf sourced everytime apropos is used)? What about making it an environment variable (just set it in login.conf) or enhancing /etc/manpath.config (BTW: everithing is named *.conf except manpath.config)? Bye, Alexander. -- I believe the technical term is "Oops!" http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 5:57:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id C54AE153A2 for ; Wed, 10 Nov 1999 05:57:16 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA24746 for freebsd-current@FreeBSD.ORG; Wed, 10 Nov 1999 14:57:15 +0100 (CET) (envelope-from olli) Date: Wed, 10 Nov 1999 14:57:15 +0100 (CET) From: Oliver Fromme Message-Id: <199911101357.OAA24746@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: "man" reads /etc/rc.conf? Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A.Leidinger@WJPServer.CS.Uni-SB.de wrote in list.freebsd-current: you wrote (9 Nov 1999 21:13:42 +0100): > (101) netchild@ttyp2 > man -k adadadad > cat: /etc/isdn/connect.parameters: Permission denied > adadadad: nothing appropriate > > (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > spppconfig_isp0="`cat /etc/isdn/connect.parameters`" Using command substitution in /etc/rc.conf{,.local} is NOT officially supported. I think it should have always been clear that there should _only_ be plain variable assignments. That's probably just because you never know which programs try to read them. > Is this just my system or is man really reading rc.conf(.local)? I think that's perfectly legal. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 6: 0:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 0E01B14E02; Wed, 10 Nov 1999 06:00:52 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp149.dialup.st.keio.ac.jp [131.113.27.149]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id XAA02344; Wed, 10 Nov 1999 23:00:49 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id XAA12524; Wed, 10 Nov 1999 23:00:47 +0900 (JST) Message-Id: <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> To: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: PC-Card ejection(suspend) with 4-current X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 10 Nov 1999 23:00:46 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: >Card ejection (including suspend) doesn't work, which I'll try to fix >at some point, but I might not get around to fixing that before new >pccard work begins. I think it would be easy to mostly fix (like the >old code mostly worked) with more thought on how to do this (see -arch >for a message related tot his problem). I think FreeBSD-4-current does not support PC-Card suspend yet. I read and diffed old code and current code. But I did not find out anything.... Does someone create patch for this problem? # or we need to rewrite and maintain pccard code(/sys/dev/pccard)? Thanks in advance MIHIRA Sanpei Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 6:58: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 6541314E9A for ; Wed, 10 Nov 1999 06:57:59 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id PAA10282652; Wed, 10 Nov 1999 15:57:57 +0100 (CET) Received: from work.net.local (maxtnt-039.telip.uni-sb.de [134.96.70.166]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id PAA14444; Wed, 10 Nov 1999 15:58:00 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id PAA02453; Wed, 10 Nov 1999 15:57:45 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911101457.PAA02453@work.net.local> Date: Wed, 10 Nov 1999 15:57:44 +0100 (CET) From: Alexander Leidinger Subject: Re: "man" reads /etc/rc.conf? To: freebsd-current@FreeBSD.ORG Cc: olli@dorifer.heim3.tu-clausthal.de In-Reply-To: <199911101357.OAA24746@dorifer.heim3.tu-clausthal.de> 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 On 10 Nov, Oliver Fromme wrote: > Using command substitution in /etc/rc.conf{,.local} is NOT > officially supported. I think it should have always been > clear that there should _only_ be plain variable assignments. But with i4b you have to specify a username-password pair in rc.conf (spppconfig_isp0) and I didnīt want to show it to every user (rc.conf is u+rw,g+r,o+r for reasons you mention). > That's probably just because you never know which programs > try to read them. Ok, so we (root of machine xxx) have either a security hole (dial-in-passwd visible to everyone) or we have to forget the recommended way of doing it. > > Is this just my system or is man really reading rc.conf(.local)? > > I think that's perfectly legal. Yes, but is it necessary? Bye, Alexander. -- Columbus had a fourth ship. It sailed over the edge. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 7:37:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CC5A2151EB for ; Wed, 10 Nov 1999 07:37:04 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA23030; Thu, 11 Nov 1999 00:36:50 +0900 (JST) Message-ID: <3829908C.7BDA9DD@newsguy.com> Date: Thu, 11 Nov 1999 00:34:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: A.Leidinger@WJPServer.CS.Uni-SB.de Cc: archie@whistle.com, current@FreeBSD.ORG Subject: Re: "man" reads /etc/rc.conf? References: <199911101247.NAA01228@work.net.local> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A.Leidinger@WJPServer.CS.Uni-SB.de wrote: > > >> (101) netchild@ttyp2 > man -k adadadad > >> cat: /etc/isdn/connect.parameters: Permission denied > >> adadadad: nothing appropriate > >> > >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" ^^^ Calling programs from any of the rc.conf files is considered evil and it's looked down on. > /usr/bin/apropos contains: > ---snip--- > # If possible check global system configuration file for additional > # man locales installed > if [ -r /etc/defaults/rc.conf ] ; then > . /etc/defaults/rc.conf > elif [ -r /etc/rc.conf ] ; then > . /etc/rc.conf > fi > ---snip--- > > and /etc/defaults/rc.conf: > ---snip--- > man_locales="NO" # space separated list of man locales (or NO) > ---snip--- > > Do we have to live with this or is it subject to change (it gives me a > bad taste to have rc.conf sourced everytime apropos is used)? What about > making it an environment variable (just set it in login.conf) or > enhancing /etc/manpath.config (BTW: everithing is named *.conf except > manpath.config)? Apropos is not the fastest of the programs. Sourcing rc.conf most likely takes a very small time compared to it's total execution time. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 8:28: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 64A461505E for ; Wed, 10 Nov 1999 08:27:40 -0800 (PST) (envelope-from laa@Eagle.ZGIA.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id TAA84218 for ; Wed, 10 Nov 1999 19:27:10 GMT Date: Wed, 10 Nov 1999 19:27:10 +0000 (GMT) From: Alexandr Listopad To: freebsd-current@freebsd.org Subject: HPT366 and FreeBSD-CURRENT ? 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 Hello! What about subj? Did FreeBSD support HPT366 in the CURRENT??? And if "yes" then what shall I do for it??? If I boot from floppies - then error and reboot after 15sec, and don't find this drive on IDE... what shall I do??? Please help! Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 8:35:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1E1CF14BC3 for ; Wed, 10 Nov 1999 08:35:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA86525; Wed, 10 Nov 1999 17:34:44 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199911101634.RAA86525@freebsd.dk> Subject: Re: HPT366 and FreeBSD-CURRENT ? In-Reply-To: from Alexandr Listopad at "Nov 10, 1999 07:27:10 pm" To: laa@ZGIA.zp.ua (Alexandr Listopad) Date: Wed, 10 Nov 1999 17:34:44 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Alexandr Listopad wrote: > Hello! > What about subj? > > Did FreeBSD support HPT366 in the CURRENT??? Yes it does. > And if "yes" then what shall I do for it??? Use the ata driver. > If I boot from floppies - then error and reboot after 15sec, and don't > find this drive on IDE... what shall I do??? Uhm, I'm not sure I get the meaning here, is that for an install ?? If so the new ata driver isn't use in GENERIC just yet, you could however test out the boot floppies I've put on ftp.freebsd.dk/pub/ -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 8:40:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id EB08F14C57 for ; Wed, 10 Nov 1999 08:40:39 -0800 (PST) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 11lamK-00023v-00; Wed, 10 Nov 1999 08:39:24 -0800 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id IAA27248; Wed, 10 Nov 1999 08:39:18 -0800 Date: Wed, 10 Nov 1999 08:39:18 -0800 (PST) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: "man" reads /etc/rc.conf? To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG, olli@dorifer.heim3.tu-clausthal.de In-Reply-To: <199911101457.PAA02453@work.net.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Nov-99 at 06:59, Alexander Leidinger (A.Leidinger@WJPServer.CS.Uni-SB= .de) wrote: > On 10 Nov, Oliver Fromme wrote: >=20 > > Using command substitution in /etc/rc.conf{,.local} is NOT > > officially supported. I think it should have always been > > clear that there should _only_ be plain variable assignments. >=20 > But with i4b you have to specify a username-password pair in rc.conf > (spppconfig_isp0) and I didn=B4t want to show it to every user (rc.conf i= s > u+rw,g+r,o+r for reasons you mention). >=20 > > That's probably just because you never know which programs > > try to read them. >=20 > Ok, so we (root of machine xxx) have either a security hole > (dial-in-passwd visible to everyone) or we have to forget the > recommended way of doing it. It looks to me as though the recommended way of doing it needs to be changed. How about putting the sppp setup in a separate script in /usr/local/etc/rc.d ? Or, put the script in /etc/isdn and add that directory to the local_startups variable in rc.conf ? > > > Is this just my system or is man really reading rc.conf(.local)? > >=20 > > I think that's perfectly legal. >=20 > Yes, but is it necessary? The whole rc setup isn't 'necessary'. But it's damned useful and convienient. And so is the ability for arbitrary programs and scripts to read and easily parse rc.conf to obtain system wide defaults. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 9:25:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1D42314D83 for ; Wed, 10 Nov 1999 09:25:55 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA53623; Wed, 10 Nov 1999 09:25:54 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id JAA68371; Wed, 10 Nov 1999 09:25:23 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199911101725.JAA68371@whistle.com> Subject: Re: No buffer space available errors In-Reply-To: from Bill Marquette at "Nov 7, 99 10:26:06 pm" To: billm@danger.ms (Bill Marquette) Date: Wed, 10 Nov 1999 09:25:23 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Marquette writes: | For the last week and a half or so I've been trying to track this down | assuming it was a configuration error on my part or a problem with my | ISP's DHCP configuration. After switching from a DEC 20141 chipset card | to a 3com 3c905, I found I was still having problems although the error | message had changed. I'm now back to the DEC card cause I found more | results in the mailing lists on the errors I was seeing. | | At first it appeared to be dhclient having issues, but I've finally found | occurances of other programs showing symptoms prior to dhclient log | entries. Also, until today I couldn't replicate the problem while sitting | at the console, it would only show itself after I'd been away for a few | minutes (I swear it has a mind of it's own) usually, when I was going to | be away for more than 10-15 minutes. Today I managed to force the machine | to have problems by doing multiple simultaneous downloads and uploads, I | was running about 100K/sec through the NIC. On one out of 8 machines, I ran into this problem. My network is running at 100BaseTX. I noticed that ifconfig showed OACTIVE flag set and I was running in autosense mode. So I setup the media to 100BaseTX and now it works okay. My guess is the autosense gets confused sometimes. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 9:26:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 02ECE15219 for ; Wed, 10 Nov 1999 09:26:29 -0800 (PST) (envelope-from forrie@forrie.com) Received: from boomer (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id MAA93446 for ; Wed, 10 Nov 1999 12:26:29 -0500 (EST) Message-Id: <4.2.1.19991110122452.00afa440@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Wed, 10 Nov 1999 12:26:57 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Nov 9 Snapshot boot floppy failure Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried installing a 4.0-current system from Nov 9 snapshot, on a DELL 6350, 3 18g drives, 512m RAM, Got Signal Trap 12 while in kernel mode. This happened (each time) after it probed the CD drive. I've installed previous 4.0 snaps on this platform without incident. FYI. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 10: 9: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from nuke.danger.ms (a204b210n122client59.hawaii.rr.com [204.210.122.59]) by hub.freebsd.org (Postfix) with ESMTP id 3B74D1525E for ; Wed, 10 Nov 1999 10:08:58 -0800 (PST) (envelope-from billm@danger.ms) Received: by nuke.danger.ms (Postfix, from userid 1010) id CAE7828B1C; Wed, 10 Nov 1999 08:09:26 -1000 (HST) Received: from localhost (localhost [127.0.0.1]) by nuke.danger.ms (Postfix) with ESMTP id C5BEE24D18; Wed, 10 Nov 1999 08:09:26 -1000 (HST) Date: Wed, 10 Nov 1999 08:09:26 -1000 (HST) From: Bill Marquette To: Doug Ambrisko Cc: freebsd-current@freebsd.org Subject: Re: No buffer space available errors In-Reply-To: <199911101725.JAA68371@whistle.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, 10 Nov 1999, Doug Ambrisko wrote: > On one out of 8 machines, I ran into this problem. My network is running > at 100BaseTX. I noticed that ifconfig showed OACTIVE flag set and I > was running in autosense mode. So I setup the media to 100BaseTX and now > it works okay. > > My guess is the autosense gets confused sometimes. Doug, thanks for the tip, I'll give that a try as I haven't been forcing either card to 10Mbit or TP connections. I have added to the mystery however and this is aggravatingly puzzling. In my previous message I had mentioned that walking away fromt he console for any length of time would cause the machine to generate the "No buffer space" errors. Since then I've turned off my screensaver (Matrix from KDE) and the system has stabilized completely; well almost completely. I can still duplicate the buffer situation and I've still seen it occur when doing fairly high bandwidth (for cable, not for ethernet) file transfers. If I can manage to bring the xfer rate up to around 100K/sec total between inbound and outbound I experience the "Out of buffer" messages within a couple minutes. netstat -m doesn't show anything unusual. I am going to try removing both NMBCLUSTERS and NBUF from my config and just use a maxusers of 128 and see how that goes. --Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 11:17:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id D1F4E14E16 for ; Wed, 10 Nov 1999 11:17:30 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id UAA10415575; Wed, 10 Nov 1999 20:17:23 +0100 (CET) Received: from work.net.local (maxtnt-022.telip.uni-sb.de [134.96.70.149]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id UAA16459; Wed, 10 Nov 1999 20:17:23 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id TAA00926; Wed, 10 Nov 1999 19:22:28 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911101822.TAA00926@work.net.local> Date: Wed, 10 Nov 1999 19:22:27 +0100 (CET) From: Alexander Leidinger Subject: Re: "man" reads /etc/rc.conf? To: dcs@newsguy.com Cc: current@freebsd.org In-Reply-To: <3829908C.7BDA9DD@newsguy.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 On 11 Nov, Daniel C. Sobral wrote: >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local >> >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" > ^^^ > Calling programs from any of the rc.conf files is considered evil > and it's looked down on. Itīs there to hide login/passwd information for i4b. [apropos sourcing rc.conf] >> Do we have to live with this or is it subject to change (it gives me >> bad taste to have rc.conf sourced everytime apropos is used)? What >> about making it an environment variable (just set it in login.conf) >> or enhancing /etc/manpath.config (BTW: everithing is named *.conf >> except manpath.config)? > > Apropos is not the fastest of the programs. Sourcing rc.conf most > likely takes a very small time compared to it's total execution > time. I hadnīt execution time in mind. Itīs more a "Thereīs manpath.config, why didnīt we use it for this?". Bye, Alexander. -- There is no seeing eye dog for blind faith. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 11:18:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 030C0152A1 for ; Wed, 10 Nov 1999 11:17:31 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id UAA9801659; Wed, 10 Nov 1999 20:17:25 +0100 (CET) Received: from work.net.local (maxtnt-022.telip.uni-sb.de [134.96.70.149]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id UAA16467; Wed, 10 Nov 1999 20:17:26 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id TAA00971; Wed, 10 Nov 1999 19:48:37 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911101848.TAA00971@work.net.local> Date: Wed, 10 Nov 1999 19:48:36 +0100 (CET) From: Alexander Leidinger Subject: Re: "man" reads /etc/rc.conf? To: patl@phoenix.volant.org Cc: freebsd-current@FreeBSD.ORG, olli@dorifer.heim3.tu-clausthal.de In-Reply-To: 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 On 10 Nov, patl@phoenix.volant.org wrote: >> Ok, so we (root of machine xxx) have either a security hole >> (dial-in-passwd visible to everyone) or we have to forget the >> recommended way of doing it. > > It looks to me as though the recommended way of doing it needs to > be changed. How about putting the sppp setup in a separate script > in /usr/local/etc/rc.d ? Or, put the script in /etc/isdn and add > that directory to the local_startups variable in rc.conf ? Thereīs already rc.isdn, we just have to find a name for the config file (Iīve no problem to do it in my setup, I just want to have a official way to close this security hole). >>>> Is this just my system or is man really reading rc.conf(.local)? >>> I think that's perfectly legal. >> Yes, but is it necessary? > > The whole rc setup isn't 'necessary'. But it's damned useful > and convienient. And so is the ability for arbitrary programs > and scripts to read and easily parse rc.conf to obtain system > wide defaults. Sorry, I didnīt object to the rc setup, I just want to know why we didnīt use manpath.config (yes, "man_locales" isnīt realy a path-specifier, but itīs relatet to man & localized man-pages which are stored in īManPathElementī/LocalePart/). And I didnīt say it has to be changed (but we have to change the startup of i4b). Bye, Alexander. -- Dead men tell no tales, unless you're in forensics. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 12:45:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 5905714D71 for ; Wed, 10 Nov 1999 12:45:15 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id MAA67671; Wed, 10 Nov 1999 12:44:38 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 10 Nov 1999 12:44:38 -0800 (PST) From: Vincent Poy To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Alexandr Listopad , freebsd-current@FreeBSD.ORG Subject: Re: HPT366 and FreeBSD-CURRENT ? In-Reply-To: <199911101634.RAA86525@freebsd.dk> 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 Greetings, Just so everyone knows, the latest BIOSes for ABIT motherboards and ABIT Controller cards with the HPT366 Controller as well as MS Drivers can be found at: http://140.113.153.55/stuff/ide_card/HighPoint/HPT366/index-e.htm Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 13:38:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 6CB4714DF9 for ; Wed, 10 Nov 1999 13:38:31 -0800 (PST) (envelope-from forrie@navinet.net) Received: from boomer (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id QAA95462 for ; Wed, 10 Nov 1999 16:38:31 -0500 (EST) Message-Id: <4.2.1.19991110163725.00b00430@216.67.14.8> X-Sender: forrie@216.67.14.8 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Wed, 10 Nov 1999 16:38:34 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Re: Nov 9 Snapshot boot floppy failure (FOLLOW UP) In-Reply-To: <4.2.1.19991110122452.00afa440@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I backed to Nov 01 snapshot and the install went fine; however it appears it's not writing out partition information correctly. We performed 3 installs, and went over each step judiciously, and when you reboot after the install, it complains about invalid parition information. At 12:26 PM 11/10/99 -0500, Forrest Aldrich wrote: >Just tried installing a 4.0-current system from Nov 9 >snapshot, on a DELL 6350, 3 18g drives, 512m RAM, > >Got Signal Trap 12 while in kernel mode. This happened >(each time) after it probed the CD drive. > >I've installed previous 4.0 snaps on this platform without >incident. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 14: 6:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EAF7C14E3C; Wed, 10 Nov 1999 14:06:25 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA97938; Wed, 10 Nov 1999 15:06:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA07865; Wed, 10 Nov 1999 15:05:28 -0700 (MST) Message-Id: <199911102205.PAA07865@harmony.village.org> To: MIHIRA Sanpei Yoshiro Subject: Re: PC-Card ejection(suspend) with 4-current Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 10 Nov 1999 23:00:46 +0900." <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> References: <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> Date: Wed, 10 Nov 1999 15:05:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> MIHIRA Sanpei Yoshiro-san writes: : I think FreeBSD-4-current does not support PC-Card suspend yet. Yes. That's correct. I broke it when I did my last batch of newbus code. : I read and diffed old code and current code. But I did not find : out anything.... : : Does someone create patch for this problem? No yet. I slightly rearranged the order and timing of events in the eject (and suspend) paths of the code. Effectively, I've managed to make the device go away from a hardware point of view before I've removed the device from the software tree and stopped delivering interrupts to it, so it gets an interrupt once the hardware is gone. I've diagnosed it this far, but haven't looked at the code to find out why it is doing this or how to fix it. I basically screwed up Nate's efforts which made the suspend code 99% safe... :-( I would welcome with open arms patches to fix this problem... : # or we need to rewrite and maintain pccard code(/sys/dev/pccard)? That's the real answer. Anybody willing to help, please let me know. I have probe/attach code for the pcic code (in /sys/dev/pcic) going, but I've not hooked up the pccard stuff to it. My work on this is on hold for the moment until my Sony VAIO gets back from Sony... Hopefully by Friday when I head off for the weekend... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 14:30:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id D1F8A14A15; Wed, 10 Nov 1999 14:30:26 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA15614; Wed, 10 Nov 1999 17:30:16 -0500 (EST) Message-ID: <19991110173016.A15277@netmonger.net> Date: Wed, 10 Nov 1999 17:30:16 -0500 From: Christopher Masto To: Warner Losh , MIHIRA Sanpei Yoshiro Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: PC-Card ejection(suspend) with 4-current References: <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> <199911102205.PAA07865@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199911102205.PAA07865@harmony.village.org>; from Warner Losh on Wed, Nov 10, 1999 at 03:05:28PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 10, 1999 at 03:05:28PM -0700, Warner Losh wrote: > : # or we need to rewrite and maintain pccard code(/sys/dev/pccard)? > > That's the real answer. Anybody willing to help, please let me know. > I have probe/attach code for the pcic code (in /sys/dev/pcic) going, > but I've not hooked up the pccard stuff to it. My work on this is > on hold for the moment until my Sony VAIO gets back from Sony... > Hopefully by Friday when I head off for the weekend... I'm willing to try/test anything, but as I am stuck with enormous amounts of work for the rest of the year, I can only spend minimal time actually touching the code. I'd love to see this fixed, though. It's an incredible annoyance to have to shut my laptop off instead of suspending. As for the arguments about "safe" removal, let's not let the quest for the perfect shed kill this; if the device has to be disabled before removing it, so be it.. but right now it's not possible to remove a pccard at all. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Wed Nov 10 14:33:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E043114E0D; Wed, 10 Nov 1999 14:33:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA97999; Wed, 10 Nov 1999 15:33:39 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08009; Wed, 10 Nov 1999 15:32:45 -0700 (MST) Message-Id: <199911102232.PAA08009@harmony.village.org> To: Christopher Masto Subject: Re: PC-Card ejection(suspend) with 4-current Cc: MIHIRA Sanpei Yoshiro , current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 10 Nov 1999 17:30:16 EST." <19991110173016.A15277@netmonger.net> References: <19991110173016.A15277@netmonger.net> <199911101400.XAA12524@lavender.yy.cs.keio.ac.jp> <199911102205.PAA07865@harmony.village.org> Date: Wed, 10 Nov 1999 15:32:45 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991110173016.A15277@netmonger.net> Christopher Masto writes: : I'd love to see this fixed, though. It's an incredible annoyance to : have to shut my laptop off instead of suspending. Agreed. : As for the arguments about "safe" removal, let's not let the quest for : the perfect shed kill this; if the device has to be disabled before : removing it, so be it.. but right now it's not possible to remove a : pccard at all. I think all that's required is moving a device_delete_child() call or three... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 15:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from saigon.hacom.net (ns.hacom.net [216.104.140.6]) by hub.freebsd.org (Postfix) with ESMTP id CD6FD14E1E for ; Wed, 10 Nov 1999 15:50:47 -0800 (PST) (envelope-from gllewis@hacom.net) Received: from hacom.net (ppp-216-104-140-81.hacom.net [216.104.140.81]) by saigon.hacom.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA20726 for ; Wed, 10 Nov 1999 18:50:45 -0500 Message-ID: <382A125D.F39515E8@hacom.net> Date: Wed, 10 Nov 1999 19:48:29 -0500 From: gllewis X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 16:59:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 8110C153F1 for ; Wed, 10 Nov 1999 16:59:44 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id QAA57173; Wed, 10 Nov 1999 16:58:54 -0800 (PST) Date: Wed, 10 Nov 1999 16:58:54 -0800 (PST) From: Annelise Anderson To: Marc Schneiders Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make release troubles 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 There are a couple of things you can do if your make release fails while trying to make the docs. You could use "on demand" dialing for ppp so that it connects only when it needs to (and hangs up after some period of inactivity) so you're not connected for so long. Making these ports is the only part of a make release that requires fetching files. You could also have the make release continue more or less where it left off. You do *not* want to start it over by typing "make release" in /usr/src/release, as this will delete what's already been done. But you can chroot to the directory where the release is being built and run the file "mk" in that directory. This is a shell script that is created when you run "make release" in /usr/src/release, and once the chroot directive is reached in the Makefile in /usr/src/release, only what's in the chroot directory structure is relevant. Running "mk" from this directory should allow things to continue where they left off, because this script incorporates the variables you decided upon when you edited the Makefile in /usr/src/release and runs the :doRELEASE target in Makefile in $CHROOTDIR/usr/src/release, which records ("touch release.1", for example) what's been done. An alternative is to define a target in /usr/src/release/Makefile called (e.g.) release.0, and have it simply chroot to the directory where you're building the release and run mk there. You can then define in mk any target you want to build in the Makefile in $CHROOTDIR/usr/src/release, and then put this target in the Makefile. This means you can continue where you left off by typing "make release.0" in /usr/src/release. By this time the ports distfiles will already have been copied to $CHROOTDIR/usr/ports/distfiles, and anything in the /usr/ports/distfiles directory or wherever you tell it to get the distfiles (/usr/ports/ distfiles.release in your case) will not be found. If you need to add a distfile, you need to put it in $CHROOTDIR/usr/ports/distfiles. A possible strategy before beginning the make release is to move the existing /usr/ports/distfiles to a hold location, do "make install" in /usr/ports/textproc/docproj, and hope that you in this way get all the distfiles you need for the release. You might have to deinstall first so that it does go through the whole build process and gets all the dependencies. If you do this, you want to make sure your version of the ports tree in /usr/ports is the same as the version you want to build in "make release." I personally think these little ports like tidy are troublesome because the version numbers change so often; so probably the best approach is to have an open connection during the build of doc.1 so it can get anything you haven't yet gotten. Annelise On Sun, 7 Nov 1999, Marc Schneiders wrote: > I have studied the Makefile. > I have searched the archives of the lists. > I have put the files necessary for the ports build for docproj during > the make in a separate directory (/usr/ports/distfiles.release), > with no extra files there. > I have set this in the Makefile. Nevertheless this is what happened: > > touch release.2 > Making docs... > ===> Extracting for docproj-1.1 > [...] > [...] > [...] > ===> Registering installation for sgmlformat-1.7 > ===> Returning to build of docproj-1.1 > ===> docproj-1.1 depends on executable: sgmlnorm - found > ===> docproj-1.1 depends on executable: jade - found > ===> docproj-1.1 depends on executable: tidy - not found > ===> Verifying install for tidy in /usr/ports/www/tidy > ===> Extracting for tidy-0.9.99.1 > >> Checksum OK for tidy27sep99.tgz. > > Here it just stopped (and had been waiting for 9 hours...). No error > message, nothing. Machine was responding OK. No kernel messages, no > messages. Nothing peculiar in top etc. So I tried something weird (in > my eyes anyway) and kill -HUPped the PID. It continued. Great, well > for a moment. > > ===> Patching for tidy-0.9.99.1 > ===> Applying FreeBSD patches for tidy-0.9.99.1 > ===> Configuring for tidy-0.9.99.1 > ===> Building for tidy-0.9.99.1 > cc -O -pipe -D__USE_MISC -c attrs.c > cc -O -pipe -D__USE_MISC -c istack.c > cc -O -pipe -D__USE_MISC -c parser.c > cc -O -pipe -D__USE_MISC -c tags.c > cc -O -pipe -D__USE_MISC -c entities.c > cc -O -pipe -D__USE_MISC -c lexer.c > cc -O -pipe -D__USE_MISC -c pprint.c > cc -O -pipe -D__USE_MISC -c clean.c > cc -O -pipe -D__USE_MISC -c localize.c > cc -O -pipe -D__USE_MISC -c config.c > cc -O -pipe -D__USE_MISC -c tidy.c > cc -O -pipe -D__USE_MISC -o tidy attrs.o istack.o > parser.o tags.o entities.o lexer.o pprint.o > clean.o localize.o config.o tidy.o -lc > ===> Installing for tidy-0.9.99.1 > install -c -s -o root -g wheel -m 555 > /usr/ports/www/tidy/work/tidy27sep99/tidy /usr/local/bin/tidy > ===> Installing documentation for tidy-0.9.99.1 > ===> Generating temporary packing list > ===> Registering installation for tidy-0.9.99.1 > ===> Returning to build of docproj-1.1 > ===> docproj-1.1 depends on executable: lynx - not found > ===> Verifying install for lynx in /usr/ports/www/lynx > ===> Extracting for lynx-2.8.2rel.1 > >> Checksum OK for lynx2.8.2rel.1.tar.bz2. > ===> lynx-2.8.2rel.1 depends on executable: bzip2 - not found > ===> Verifying install for bzip2 in /usr/ports/archivers/bzip2 > >> bzip2-0.9.5d.tar.gz doesn't seem to exist on this system. > >> Attempting to fetch from > ftp://sourceware.cygnus.com/pub/bzip2/v095/. > fetch: sourceware.cygnus.com: Host name lookup failure > >> Attempting to fetch from > http://www.kernel.org/pub/software/utils/compress/bzip2/. > fetch: `www.kernel.org': cannot resolve: Host name lookup failure > >> Attempting to fetch from > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. > fetch: ftp.FreeBSD.org: Host name lookup failure > >> Couldn't fetch it - please try to retrieve this > >> port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 > > bzip2-0.9.5d.tar.gz *is* in the directory > /usr/ports/distfiles.release, mentioned earlier. > > Now what can I do? Should this file (and others?, but which?) be in > the 'normal' distfiles directory and not in the one set in the > Makefile? > > I can see only one way out, which is to spend about $30 on phone > charges and stay online for the make release, after deleting *all* of > the distfiles on my system. > > Maybe there is someone out there who knows a cheaper and better way? > > TIA! > > Marc > > Marc Schneiders > > marc@venster.nl > marc@oldserver.demon.nl > > propro 1:40pm up 11 days, 7:21, load average: 2.23 2.13 2.04 > > > > 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 Nov 10 18:14:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1.allunix.com (17.93.ng.netgatepool.quiknet.com [207.231.93.17]) by hub.freebsd.org (Postfix) with ESMTP id 339FC15416 for ; Wed, 10 Nov 1999 18:14:22 -0800 (PST) (envelope-from david@allunix.com) Received: from windoze (windoze.allunix.com [192.168.0.3]) by web1.allunix.com (8.9.3/8.9.3) with SMTP id SAA00252 for ; Wed, 10 Nov 1999 18:30:05 -0800 (PST) (envelope-from david@allunix.com) Received: from lists.securityfocus.com (lists.securityfocus.com [207.126.127.68]) by web1.allunix.com (8.9.3/8.9.3) with ESMTP id JAA00751 for ; Wed, 10 Nov 1999 09:41:28 -0800 (PST) (envelope-from owner-bugtraq@SECURITYFOCUS.COM) Received: from lists.securityfocus.com (lists.securityfocus.com [207.126.127.68]) by lists.securityfocus.com (Postfix) with ESMTP id CBC311F926; Wed, 10 Nov 1999 09:06:03 -0800 (PST) Received: from LISTS.SECURITYFOCUS.COM by LISTS.SECURITYFOCUS.COM (LISTSERV-TCP/IP release 1.8d) with spool id 1061482 for BUGTRAQ@LISTS.SECURITYFOCUS.COM; Wed, 10 Nov 1999 09:05:48 -0800 Approved-By: aleph1@SECURITYFOCUS.COM Delivered-To: bugtraq@lists.securityfocus.com Received: from securityfocus.com (securityfocus.com [207.126.127.66]) by lists.securityfocus.com (Postfix) with SMTP id 37D611EEF6 for ; Tue, 9 Nov 1999 15:23:10 -0800 (PST) Received: (qmail 10750 invoked by alias); 9 Nov 1999 23:23:10 -0000 Delivered-To: BUGTRAQ@SECURITYFOCUS.COM Received: (qmail 10747 invoked from network); 9 Nov 1999 23:23:10 -0000 Received: from nwcst315.netaddress.usa.net (204.68.23.60) by securityfocus.com with SMTP; 9 Nov 1999 23:23:10 -0000 Received: (qmail 10541 invoked by uid 60001); 9 Nov 1999 23:23:48 -0000 Received: from 204.68.23.60 by nwcst315 for [199.174.164.143] via web-mailer(M3.3.1.96) on Tue Nov 9 23:23:48 GMT 1999 X-Mailer: USANET web-mailer (M3.3.1.96) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Message-ID: <19991109232348.10540.qmail@nwcst315.netaddress.usa.net> Date: Tue, 9 Nov 1999 16:23:48 MST Reply-To: Brock Tellier From: Brock Tellier Subject: Re: [Re: FreeBSD 3.3's seyon vulnerability] X-To: Bill Fumerola X-cc: BUGTRAQ@SECURITYFOCUS.COM To: BUGTRAQ@SECURITYFOCUS.COM Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by web1.allunix.com id JAA00751 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would be nice if you: (a) filed a pr using send-pr(1) or the web interface or (b) contacted security-officer@FreeBSD.org or (c) sent mail to the maintainer of the port I've sent mail to security-officer@freebsd.org several times regarding the "faxalter" exploit and "amanda" exploit and recieved no response. Interestingly, now that I have neglected to send mail to this address, I've recieved a response from someone. You can't expect people to keep sending mail into the void until someone at FreeBSD decides that "this one is important enough". I gave the standard week or so to recieve email back for the previous vulnerabilities I reported and will do so in the future. If I don't hear back, you can bet I'll still post. Brock Tellier UNIX Systems Administrator Chicago, IL, USA ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 10 22: 8:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id D17151543A for ; Wed, 10 Nov 1999 22:08:49 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id AAA88205; Thu, 11 Nov 1999 00:08:42 -0600 (CST) From: Joe Greco Message-Id: <199911110608.AAA88205@aurora.sol.net> Subject: Re: need patch review - NFS fixes for IP binding In-Reply-To: <199911100721.XAA05191_apollo.backplane.com@ns.sol.net> from Matthew Dillon at "Nov 10, 1999 7:22:38 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 11 Nov 1999 00:08:41 -0600 (CST) 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 > interfaces (e.g. virtual frame interfaces). 'named' went the > 'bind to everything' route and it was six years before the bugs got > worked out of it. And, despite those efforts, some of us went and bludgeoned the code into a more trivial case ("bind to address nn.nn.nn.nn") for local use anyways. Looks like the jail code will do something similar w/o source changes. Oh well! ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 5:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8415E14D56 for ; Thu, 11 Nov 1999 05:15:23 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p13-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA08596; Fri, 12 Nov 1999 00:21:16 +1100 Date: Fri, 12 Nov 1999 00:15:00 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: inconsistent and wrong locking in asleep() In-Reply-To: <5lg0yfn4bv.fsf@assaris.sics.se> 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 9 Nov 1999, Assar Westerlund wrote: > Bruce Evans writes: > > That's a really old bug. I fixed it a year or two ago in my version, > > and optimised the !SMP case following a suggestion of tegge (waiting > > for the lock is useless in the !SMP case). > > Looks fine. Can you commit your patch? Alan Cox committed it. Perhaps it is important enough to commit to -stable too (it only affects the SMP case unless SIMPLELOCK_DEBUG is configured). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 5:36:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from nowcool.dhs.org (FX3-1-031.mgfairfax.rr.com [24.28.200.31]) by hub.freebsd.org (Postfix) with ESMTP id A127A14CFE for ; Thu, 11 Nov 1999 05:36:26 -0800 (PST) (envelope-from freebsd@nowcool.dhs.org) Received: from localhost (freebsd@localhost) by nowcool.dhs.org (8.9.3/8.9.3) with ESMTP id IAA00490 for ; Thu, 11 Nov 1999 08:36:11 GMT (envelope-from freebsd@nowcool.dhs.org) Date: Thu, 11 Nov 1999 08:36:11 +0000 (GMT) From: Byung Yang To: current@freebsd.org Subject: new kernel. 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 supped two days ago and compiled everything. Now, if I try to launch netscape, the computer just freezes right up there. First, I thought it was the netscape, but when I was searching for a file on my computer, but took longer than I thought and pressed ^C, it froze again. I heard and also suspect that this has something to do with the new signal algorithm.. does anybody experience this? --- e To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 5:42:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id B5BA414D75 for ; Thu, 11 Nov 1999 05:42:30 -0800 (PST) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id OAA11679; Thu, 11 Nov 1999 14:42:09 +0100 (CET) Date: Thu, 11 Nov 1999 14:42:09 +0100 From: Stephan van Beerschoten To: Byung Yang Cc: current@FreeBSD.ORG Subject: Re: new kernel. Message-ID: <19991111144209.A8293@supra.rotterdam.luna.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Byung Yang on Thu, Nov 11, 1999 at 08:36:11AM +0000 Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 11, 1999 at 08:36:11AM +0000, Byung Yang wrote: > I supped two days ago and compiled everything. Now, if I try to launch > netscape, the computer just freezes right up there. First, I thought it > was the netscape, but when I was searching for a file on my computer, but > took longer than I thought and pressed ^C, it froze again. I bet you use the linux version of Netscape ? Try ANY linux program .. I've had this too. I bet that any linux program makes your computer freeze. It has been on this list too for .. ehm, about 3 messages or so. The remedy I used, was (how odd it may seem) to recompile your kernel... -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services www.luna.nl PO Box 28013 3003 KA Rotterdam NL PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C 77 8D 35 29 C4 2A 2D 27 The perl script is correct if its get this job done before your boss fires you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 6:43:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id E73B514CAE for ; Thu, 11 Nov 1999 06:43:43 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-139.skylink.it [194.185.55.139]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id PAA12383; Thu, 11 Nov 1999 15:44:34 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id DAA00514; Thu, 11 Nov 1999 03:34:22 -0700 (MST) (envelope-from hibma@skylink.it) Date: Thu, 11 Nov 1999 03:34:22 -0700 (MST) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: Nick Hibma To: Christopher Masto Cc: Garrett Wollman , usb-bsd@egroups.com, current@FreeBSD.org Subject: Re: VESA module breaks USB? In-Reply-To: <19991101005154.A27488@netmonger.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 > > > > ohci0: irq 9 at device 11.0 on pci0 > > > > +ohci_waitintr: timeout > > > > > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > > > BIOS caused it to do something strange that interfered with the > > > delivery of this interrupt on your motherboard. > > > > No, this has something to do with soft resetting vs. hard > > resetting. It might be that this is related to soft rebooting out of > > Windows. Try switching off and on your machine. > > I don't have Windows, but I can try a hard boot at some point and see > if it helps. I can also try to fiddle with the IRQs just in case, but > they are after all being assigned by FreeBSD. > > For now I've just turned off VESA, but I think it is going to become > non-optional at some point and I'd hate to see my USB go away. Hm, in my system at home I added a network card and consequently the two USB adapters went onto one IRQ. It only works about 30% of the time, the rest of the time I get ohci_timeout as well (also a FireLink controller). I have not the foggiest why this is. But I'll have a play someday soon to see whether I can fix it. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 7: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ppp104-220.cpis.net [206.155.220.133]) by hub.freebsd.org (Postfix) with ESMTP id 5056214D01 for ; Thu, 11 Nov 1999 07:06:23 -0800 (PST) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.by-tor.tacorp.net (8.9.3/8.9.3) id KAA00929; Thu, 11 Nov 1999 10:04:30 -0500 (EST) (envelope-from by-tor) Date: Thu, 11 Nov 1999 10:04:30 -0500 (EST) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: Stephan van Beerschoten Cc: Byung Yang , current@FreeBSD.ORG Subject: Re: new kernel. In-Reply-To: <19991111144209.A8293@supra.rotterdam.luna.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, 11 Nov 1999, Stephan van Beerschoten wrote: > On Thu, Nov 11, 1999 at 08:36:11AM +0000, Byung Yang wrote: > > I supped two days ago and compiled everything. Now, if I try to launch > > netscape, the computer just freezes right up there. First, I thought it > > was the netscape, but when I was searching for a file on my computer, but > > took longer than I thought and pressed ^C, it froze again. > > I bet you use the linux version of Netscape ? > Try ANY linux program .. I've had this too. I bet that any linux program > makes your computer freeze. > > It has been on this list too for .. ehm, about 3 messages or so. The remedy > I used, was (how odd it may seem) to recompile your kernel... If you check the mailing list archives you will also note that since most people use the linux emulator module, it is necessary to rebuild all your modules to avoid a panic. Your kernel should always be in sync with your modules. -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@engr.sc.edu _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 7:56:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 7B6A714DB1 for ; Thu, 11 Nov 1999 07:56:37 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 81A2F1C2B; Thu, 11 Nov 1999 09:58:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 7D2C0381B; Thu, 11 Nov 1999 09:58:27 -0500 (EST) Date: Thu, 11 Nov 1999 09:58:27 -0500 (EST) From: Bill Fumerola To: Joe Greco Cc: Matthew Dillon , current@freebsd.org Subject: Re: need patch review - NFS fixes for IP binding In-Reply-To: <199911110608.AAA88205@aurora.sol.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, 11 Nov 1999, Joe Greco wrote: > And, despite those efforts, some of us went and bludgeoned the code into > a more trivial case ("bind to address nn.nn.nn.nn") for local use anyways. > Looks like the jail code will do something similar w/o source changes. isc-dhcpd is even uglier in this regard. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Nov 11 8:39:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7E16315470 for ; Thu, 11 Nov 1999 08:39:44 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id JAA24581; Thu, 11 Nov 1999 09:04:44 -0800 (PST) Date: Thu, 11 Nov 1999 09:04:44 -0800 (PST) From: Alfred Perlstein To: Byung Yang Cc: current@FreeBSD.ORG Subject: Re: new kernel. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Byung Yang wrote: > > I supped two days ago and compiled everything. Now, if I try to launch > netscape, the computer just freezes right up there. First, I thought it > was the netscape, but when I was searching for a file on my computer, but > took longer than I thought and pressed ^C, it froze again. > > I heard and also suspect that this has something to do with the new signal > algorithm.. does anybody experience this? Yes, but... what kind of configuration do you have? Since my crystal ball is in the shop I really have no way of dicerning what's going on. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 11: 6: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id C499314C85 for ; Thu, 11 Nov 1999 11:05:34 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id UAA16147; Thu, 11 Nov 1999 20:05:47 +0100 (CET) Message-ID: <19991111200547.A16123@foobar.franken.de> Date: Thu, 11 Nov 1999 20:05:47 +0100 From: Harold Gutch To: Alexander Leidinger , freebsd-current@FreeBSD.ORG Cc: olli@dorifer.heim3.tu-clausthal.de Subject: Re: "man" reads /etc/rc.conf? References: <199911101357.OAA24746@dorifer.heim3.tu-clausthal.de> <199911101457.PAA02453@work.net.local> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <199911101457.PAA02453@work.net.local>; from Alexander Leidinger on Wed, Nov 10, 1999 at 03:57:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 10, 1999 at 03:57:44PM +0100, Alexander Leidinger wrote: > On 10 Nov, Oliver Fromme wrote: > > > Using command substitution in /etc/rc.conf{,.local} is NOT > > officially supported. I think it should have always been > > clear that there should _only_ be plain variable assignments. > > But with i4b you have to specify a username-password pair in rc.conf > (spppconfig_isp0) and I didnīt want to show it to every user (rc.conf is > u+rw,g+r,o+r for reasons you mention). What about /etc/start_if.isp0? bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 12:12: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 45B8614D06 for ; Thu, 11 Nov 1999 12:11:48 -0800 (PST) (envelope-from forrie@forrie.net) Received: (from forrie@localhost) by forrie.net (8.9.3/8.9.3) id PAA05017 for freebsd-current@freebsd.org; Thu, 11 Nov 1999 15:11:46 -0500 (EST) Date: Thu, 11 Nov 1999 15:11:46 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: Installation problem (follow-up) Message-ID: <19991111151146.A5013@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In followup to the last 2 problems reported from the recent 2 snapshots of 4.0, I backed down to snapshot 102499 and everything installed just fine. So there are definately bugs in the last 2 snaps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 12:29:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id DB2B914E3D for ; Thu, 11 Nov 1999 12:29:14 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from rtci.com (karma.afterthought.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id PAA18268; Thu, 11 Nov 1999 15:29:17 -0500 (EST) Message-ID: <382B2711.E13A1CC8@rtci.com> Date: Thu, 11 Nov 1999 15:29:05 -0500 From: Thomas Stromberg Organization: Research Triangle Commerce, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just happened to notice this today. For some reason 'grep' seems to think that 'set' output is binary, not text. Seems that GNU grep 2.3 is a little too sensitive to text/binary detection. This only seems to affect -CURRENT because -STABLE runs GNU grep 2.0. (This was committed October 28th). Now, I haven't looked at exactly how the code works, but it evidentally looks at the beginning of the file to detect it. You can use -a to override this of course. I'm not sending a PR or anything since this is 'arguable' on whether or not it's a bug or just being over sensitive. Here is an example of the output: FreeBSD 4.0-CURRENT (11NOV99): ============================== [chenresig@karma] chenresig> grep -V grep (GNU grep) 2.3 .. [root@karma] src> set|grep karma Binary file (standard input) matches [root@karma] src> set|head '!'=0 '#'=0 '$'=607 '*'=() -=569Xis 0=su '?'=0 @=() ARGC=0 FreeBSD 3.3-STABLE (09NOV99): ============================= grouper# grep -V GNU grep version 2.0 grouper# set|grep grouper DISPLAY=grouper:10.0 HOST=grouper.aquarium.rtci.com grouper# set|head '!'=0 '#'=0 '$'=2647 '*'=() -=569Xils 0=-zsh '?'=0 @=() ARGC=0 BAUD=38400 -- ====================================================================== thomas r. stromberg smtp://tstromberg@rtci.com assistant is manager / systems guru http://thomas.stromberg.org research triangle commerce, inc. finger://thomas@stromberg.org 'om mani pedme hung' pots://1.919.380.9771:3210 ================================================================[eof]= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 13:20:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F10C814BED for ; Thu, 11 Nov 1999 13:20:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA63138; Thu, 11 Nov 1999 13:20:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA60550; Thu, 11 Nov 1999 13:20:32 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Nov 1999 13:20:32 -0800 From: "David O'Brien" To: Thomas Stromberg Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991111132031.A60417@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <382B2711.E13A1CC8@rtci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <382B2711.E13A1CC8@rtci.com>; from tstromberg@rtci.com on Thu, Nov 11, 1999 at 03:29:05PM -0500 X-Operating-System: FreeBSD 4.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 Thu, Nov 11, 1999 at 03:29:05PM -0500, Thomas Stromberg wrote: > I just happened to notice this today. For some reason 'grep' seems to > think that 'set' output is binary, not text. Seems that GNU grep 2.3 is > a little too sensitive to text/binary detection. I've got a notion to change this. The -CURRENT grep is also very misleading w/ ``grep -l'' in that you will get "hits" on binary files because you can't see that "is a binary file" message to know better. The output of that message should be asked for with an option, not the default. I can't imagine how many people are going to get weird/eronious output from scripts now due to it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 14:10:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id C9F1514E28 for ; Thu, 11 Nov 1999 14:10:40 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from rtci.com (karma.afterthought.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id RAA22001 for ; Thu, 11 Nov 1999 17:10:51 -0500 (EST) Message-ID: <382B3EDE.F390B422@rtci.com> Date: Thu, 11 Nov 1999 17:10:38 -0500 From: Thomas Stromberg Organization: Research Triangle Commerce, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Thu, Nov 11, 1999 at 03:29:05PM -0500, Thomas Stromberg wrote: > > I just happened to notice this today. For some reason 'grep' seems to > > think that 'set' output is binary, not text. Seems that GNU grep 2.3 is > > a little too sensitive to text/binary detection. > > I've got a notion to change this. The -CURRENT grep is also very > misleading w/ ``grep -l'' in that you will get "hits" on binary files > because you can't see that "is a binary file" message to know better. > > The output of that message should be asked for with an option, not the > default. I can't imagine how many people are going to get weird/eronious > output from scripts now due to it. > I think it's good as a default, nothing annoys me more then "grep -R function *" in a source directory and hitting all the binaries and getting my screen splattered with high ascii. I just wish it's binary detection was a wee bit more accurate.. I don't see what's wrong with "grep -l", it does exactly what I expected it to do. It's just expected to tell you that a file matched, not anything more (anything more could cause grave problems with scripts, including some I've written).. [root@karma] /tmp> grep -l expat * expat expat-0.7.6.tar.gz wv (or maybe I'm just not understanding the issue). -- ====================================================================== thomas r. stromberg smtp://tstromberg@rtci.com assistant is manager / systems guru http://thomas.stromberg.org research triangle commerce, inc. finger://thomas@stromberg.org 'om mani pedme hung' pots://1.919.380.9771:3210 ================================================================[eof]= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 15:56:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 953F6153E6 for ; Thu, 11 Nov 1999 15:56:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA02580; Thu, 11 Nov 1999 16:56:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA14514; Thu, 11 Nov 1999 16:56:31 -0700 (MST) Message-Id: <199911112356.QAA14514@harmony.village.org> To: Theo PAGTZIS Subject: Re: ambiguity between -STABLE and -RELEASE Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 08 Nov 1999 22:53:44 GMT." <1483.942101624@cs.ucl.ac.uk> References: <1483.942101624@cs.ucl.ac.uk> Date: Thu, 11 Nov 1999 16:56:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <1483.942101624@cs.ucl.ac.uk> Theo PAGTZIS writes: : In that sense I would recommend some change in the naming (or rather : numbering) convention which in my book should be : : 3.2-RELEASE -> 3.3-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.4-STABLE : : and NOT : : 3.2-RELEASE -> 3.2-STABLE -> 3.3-RC -> 3.3-RELEASE -> 3.3-STABLE I don't follow your logic. What we have works and the -FOO meanings are a) arbitrary in a vacuum and b) well defined in FreeBSD. There is no point in changing them. 3.4 doesn't exist until 3.4-release happens. Naming things 3.4 stable just after 3.3 release would be too confusing. The -RC stuff is just for a few days, so doesn't cause much confusion since it is Really Close to 3.4. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 16:29:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id C9A6F14C0E for ; Thu, 11 Nov 1999 16:29:49 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id QAA02911; Thu, 11 Nov 1999 16:29:08 -0800 (PST) Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id QAA03019; Thu, 11 Nov 1999 16:28:54 -0800 (PST) Received: (eggert@localhost) by shade.twinsun.com (8.9.3+Sun/8.9.3) id QAA06638; Thu, 11 Nov 1999 16:28:53 -0800 (PST) Date: Thu, 11 Nov 1999 16:28:53 -0800 (PST) From: Paul Eggert Message-Id: <199911120028.QAA06638@shade.twinsun.com> To: tstromberg@rtci.com Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <382B2711.E13A1CC8@rtci.com> (tstromberg@rtci.com) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <382B2711.E13A1CC8@rtci.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Thu, 11 Nov 1999 15:29:05 -0500 From: Thomas Stromberg I just happened to notice this today. For some reason 'grep' seems to think that 'set' output is binary, not text. Most likely this is because the output of your `set' command contains binary data. In the past, this has been reported by people whose `set' command would output something like this: IFS=' ^@' where the `^@' in my message denotes a single NUL byte (control-@) in the original. If this is what's happening to you, then this is quite possibly a bug in your shell, since environment variables cannot possibly contain NUL bytes in Unix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 16:37:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id A838314F1C; Thu, 11 Nov 1999 16:37:28 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id QAA02971; Thu, 11 Nov 1999 16:37:22 -0800 (PST) Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id QAA03033; Thu, 11 Nov 1999 16:37:09 -0800 (PST) Received: (eggert@localhost) by shade.twinsun.com (8.9.3+Sun/8.9.3) id QAA06642; Thu, 11 Nov 1999 16:37:08 -0800 (PST) Date: Thu, 11 Nov 1999 16:37:08 -0800 (PST) From: Paul Eggert Message-Id: <199911120037.QAA06642@shade.twinsun.com> To: obrien@freebsd.org Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <19991111132031.A60417@dragon.nuxi.com> (obrien@freebsd.org) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Thu, 11 Nov 1999 13:20:32 -0800 From: "David O'Brien" I've got a notion to change this. Please don't change the algorithm to deduce which files are binary. It was the subject of much design discussion in the GNU project, and is fairly consistent across other GNU applications. The -CURRENT grep is also very misleading w/ ``grep -l'' in that you will get "hits" on binary files because you can't see that "is a binary file" message to know better. I find it useful to see the names of all files matching the pattern. This is particularly the case with grep -r. grep -lr should not output a bunch of error messages saying ``Binary file FOO skipped'', as that information is less useful than simply either reporting the file as matching, or not reporting it because it doesn't match. I can't imagine how many people are going to get weird/eronious output from scripts now due to it. The binary file behavior was added to grep in response to many user requests. Users didn't like seeing a lot of binary data sent to their screens. grep's new `-r' option seems to have contributed a lot more requests of this form. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 17:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C28C514C0E for ; Thu, 11 Nov 1999 17:12:55 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id TAA07081; Thu, 11 Nov 1999 19:12:47 -0600 (CST) (envelope-from dan) Date: Thu, 11 Nov 1999 19:12:47 -0600 From: Dan Nelson To: Paul Eggert Cc: tstromberg@rtci.com, freebsd-current@FreeBSD.ORG, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991111191247.A6353@dan.emsphone.com> References: <382B2711.E13A1CC8@rtci.com> <199911120028.QAA06638@shade.twinsun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911120028.QAA06638@shade.twinsun.com>; from eggert@twinsun.com on Thu, Nov 11, 1999 at 04:28:53PM -0800 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 11), Paul Eggert said: > Most likely this is because the output of your `set' command contains > binary data. In the past, this has been reported by people whose `set' > command would output something like this: > > IFS=' > ^@' > > where the `^@' in my message denotes a single NUL byte (control-@) in > the original. If this is what's happening to you, then this is quite > possibly a bug in your shell, since environment variables cannot > possibly contain NUL bytes in Unix. Aah, but 'set' prints the value of all shell variables, exported or not. You can store any value in a shell variable. In fact, I do things like this quite often (/bin/sh example here - zsh can do the same without forking to set a): a=$(cat file.gif) size=${#a} echo Content-Length: $size echo Content-Type: image/gif echo echo -n $a I agree that _environment_ variables can't have NULs in them. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 17:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 50B7F14FCB for ; Thu, 11 Nov 1999 17:24:05 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40354>; Fri, 12 Nov 1999 12:17:56 +1100 Content-return: prohibited Date: Fri, 12 Nov 1999 12:23:54 +1100 From: Peter Jeremy Subject: panic: nexus_setup_intr: NULL irq resource! To: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov12.121756est.40354@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to enable a generic ISA multiport SIO card in -current from just before the signal changes and get presented with the above panic when the first SIO port on the card is attached. Since it seemed to be a problem with the resource allocation, I tried turning on RMAN_DEBUG, but that just suggests that the problem is elsewhere. The relevant part of my config is: options COM_MULTIPORT device sio0 at isa? disable port IO_COM1 device sio1 at isa? port IO_COM2 irq 9 device sio2 at isa? port IO_COM3 irq 3 device sio3 at isa? port 0x2e8 flags 0x605 device sio4 at isa? port 0x2f0 flags 0x605 device sio5 at isa? port 0x3e0 flags 0x605 device sio6 at isa? port 0x2e0 flags 0x605 irq 4 I originally set this up under 2.2.6 with sio3 as the master port, and it worked (as long as sio0 was disabled). When it didn't work under -current, I RTFM and noticed that the master port should be the highest number, but that didn't help. The relevant part of the boot response is: sio0: not probed (disabled) rman_reserve_resource: request: [0x2f8, 0x2ff], length 0x8, flags 0, device sio1 considering [0x1f8, 0x333] truncated region: [0x2f8, 0x300]; size 0x9 (requested 0x8) candidate region: [0x300, 0x2f8], size 0x9 splitting region in three parts: [0x1f8, 0x2f7]; [0x2f8, 0x2ff]; [0x300, 0x333] sio1 at port 0x2f8-0x2ff irq 9 flags 0x30 on isa0 rman_reserve_resource: request: [0x2f8, 0x2ff], length 0x8, flags 0, device sio1 considering [0x1f8, 0x333] truncated region: [0x2f8, 0x300]; size 0x9 (requested 0x8) candidate region: [0x300, 0x2f8], size 0x9 splitting region in three parts: [0x1f8, 0x2f7]; [0x2f8, 0x2ff]; [0x300, 0x333] sio1: type 16550A, console rman_reserve_resource: request: [0x9, 0x9], length 0x1, flags 4, device sio1 considering [0x7, 0xa] truncated region: [0x9, 0xa]; size 0x2 (requested 0x1) candidate region: [0xa, 0x9], size 0x2 splitting region in three parts: [0x7, 0x8]; [0x9, 0x9]; [0xa, 0xa] rman_reserve_resource: request: [0x3e8, 0x3ef], length 0x8, flags 0, device sio2 considering [0x338, 0x3ef] truncated region: [0x3e8, 0x3ef]; size 0x8 (requested 0x8) candidate region: [0x3ef, 0x3e8], size 0x8 allocating at the end sio2 at port 0x3e8-0x3ef irq 3 on isa0 rman_reserve_resource: request: [0x3e8, 0x3ef], length 0x8, flags 0, device sio2 considering [0x338, 0x3ef] truncated region: [0x3e8, 0x3ef]; size 0x8 (requested 0x8) candidate region: [0x3ef, 0x3e8], size 0x8 allocating at the end sio2: type 16450 rman_reserve_resource: request: [0x3, 0x3], length 0x1, flags 4, device sio2 considering [0x3, 0x5] truncated region: [0x3, 0x4]; size 0x2 (requested 0x1) candidate region: [0x4, 0x3], size 0x2 allocating from the beginning rman_reserve_resource: request: [0x2e8, 0x2ef], length 0x8, flags 0, device sio3 considering [0x1f8, 0x2f7] truncated region: [0x2e8, 0x2f0]; size 0x9 (requested 0x8) candidate region: [0x2f0, 0x2e8], size 0x9 splitting region in three parts: [0x1f8, 0x2e7]; [0x2e8, 0x2ef]; [0x2f0, 0x2f7] sio3 at port 0x2e8-0x2ef flags 0x605 on isa0 rman_reserve_resource: request: [0x2e8, 0x2ef], length 0x8, flags 0, device sio3 considering [0x1f8, 0x2f7] truncated region: [0x2e8, 0x2f0]; size 0x9 (requested 0x8) candidate region: [0x2f0, 0x2e8], size 0x9 splitting region in three parts: [0x1f8, 0x2e7]; [0x2e8, 0x2ef]; [0x2f0, 0x2f7] sio3: type 16550A (multiport) panic: nexus_setup_intr: NULL irq resource! Debugger("panic") Stopped at Debugger+0x37: movl $0,in_Debugger db> trace Debugger(c01f5fe3) at Debugger+0x37 panic(c02072a0,7,c033e0c0,c029ff2c,c029fe94) at panic+0x74 nexus_setup_intr(c04b7280,c04b8b00,0,81,c01e81d8) at nexus_setup_intr+0x19 BUS_SETUP_INTR(c04b7280,c04b8b00,0,81,c01e81d8) at BUS_SETUP_INTR+0x45 isa_setup_intr(c04b7100,c04b8b00,0,81,c01e81d8) at isa_setup_intr+0x26 BUS_SETUP_INTR(c04b7100,c04b8b00,0,81,c01e81d8) at BUS_SETUP_INTR+0x45 sioattach(c04b8b00,c04b8b00,c029ff64,c014b3ef,c04b8b00) at sioattach+0x5d9 DEVICE_ATTACH(c04b8b00,c04b8b00,7,2a4000,c029ff88) at DEVICE_ATTACH+0x33 device_probe_and_attach(c04b8b00) at device_probe_and_attach+0x4f isa_probe_children(c04b7100) at isa_probe_children+0x47 configure(0,29dc00,2a4000,0,c01191e6) at configure+0x50 mi_startup(c029ffb4,ffe,2a4000,c014fd39,c02a7000) at mi_startup+0x70 begin() at begin+0x4b db> Any immediate suggestions? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 17:35: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 4676A14BE0 for ; Thu, 11 Nov 1999 17:35:03 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA21532; Fri, 12 Nov 1999 12:05:01 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911120135.MAA21532@gizmo.internode.com.au> Subject: Re: panic: nexus_setup_intr: NULL irq resource! To: peter.jeremy@alcatel.com.au Date: Fri, 12 Nov 1999 12:05:01 +1030 (CST) Cc: current@FreeBSD.ORG In-Reply-To: <99Nov12.121756est.40354@border.alcanet.com.au> from "Peter Jeremy" at Nov 12, 99 12:23:54 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 Peter Jeremy wrote: > I'm trying to enable a generic ISA multiport SIO card in -current from > just before the signal changes and get presented with the above panic > when the first SIO port on the card is attached. Well... the first port that doesn't mention an IRQ. I discussed this with Bruce last month; The following patch seemed to work-around, even though it's a stupid hack which shouldn't be committed. The problem is that the BUS_SETUP_INTR() method for ISA seems to absolutely require the specification of an IRQ, even though IRQ specification is absolutely prohibited for non-master ports in AST-compatible multi-port sio cards. Gah. I'm not completely sure that this patch does the right thing (in terms of allowing the slave serial ports to work correctly) anyway: I haven't stress-tested it, I was more interested in getting the machine involved to be able to boot. More investigation is required. - mark *** /tmp/co/src/sys/i386/isa/isa.c Wed Sep 1 16:04:24 1999 --- isa.c Wed Oct 6 23:00:26 1999 *************** *** 137,142 **** --- 137,152 ---- isa_setup_intr(device_t bus, device_t child, struct resource *r, int flags, void (*ihand)(void *), void *arg, void **cookiep) { + if (r == NULL) { + /* + * handle the case for multiport sio cards, where + * the kernel config file mentions lots of sio ports + * but only provides the irq on the master port -- other + * ports panic in nexus_setup_intr() without this + */ + return 0; + } + return (BUS_SETUP_INTR(device_get_parent(bus), child, r, flags, ihand, arg, cookiep)); } ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 18: 3:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 776EE14FD4 for ; Thu, 11 Nov 1999 18:03:06 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40350>; Fri, 12 Nov 1999 12:56:53 +1100 Content-return: prohibited Date: Fri, 12 Nov 1999 13:02:46 +1100 From: Peter Jeremy Subject: Re: panic: nexus_setup_intr: NULL irq resource! In-reply-to: <199911120135.MAA21532@gizmo.internode.com.au> To: Mark Newton Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov12.125653est.40350@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Nov12.121756est.40354@border.alcanet.com.au> <199911120135.MAA21532@gizmo.internode.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-12 12:35:01 +1100, Mark Newton wrote: >Peter Jeremy wrote: > > > I'm trying to enable a generic ISA multiport SIO card in -current from > > just before the signal changes and get presented with the above panic > > when the first SIO port on the card is attached. > >Well... the first port that doesn't mention an IRQ. I can't recall right now whether the panic occurred with sio3 or sio4 when sio3 was master (and had an interrupt). >The problem is that the BUS_SETUP_INTR() method for ISA seems to >absolutely require the specification of an IRQ, even though IRQ >specification is absolutely prohibited for non-master ports in >AST-compatible multi-port sio cards. Gah. That's what the code looked like to me as well. Since multi-port SIO cards are supported, but will not have interrupts for the slave ports, I assumed I was missing something in the maze of nested, indirect function calls :-). As an aside, why doesn't our SIO driver work with ports that don't have interrupts? >I'm not completely sure that this patch does the right thing Since your patch effectively turns isa_setup_intr() into a nop for this case, a better patch would seem to be to skip the call to BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end of sioattach() when you're attaching a slave SIO port. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 18:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from spock2.ECE.McGill.CA (Spock2.ECE.McGill.CA [132.206.1.2]) by hub.freebsd.org (Postfix) with ESMTP id ADED714E2A; Thu, 11 Nov 1999 18:13:03 -0800 (PST) (envelope-from alainm@macs.ece.mcgill.ca) Received: from mccoy2.ECE.McGill.CA (alainm@Mccoy2.ECE.McGill.CA [132.206.63.174]) by spock2.ECE.McGill.CA (8.8.8/8.8.8) with ESMTP id VAA26634; Thu, 11 Nov 1999 21:14:00 -0500 (EST) From: Alain Magloire Received: by mccoy2.ECE.McGill.CA (8.8.8) id VAA06622; Thu, 11 Nov 1999 21:13:55 -0500 (EST) Message-Id: <199911120213.VAA06622@mccoy2.ECE.McGill.CA> Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? To: obrien@freebsd.org Date: Thu, 11 Nov 1999 21:13:54 -0500 (EST) Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-Reply-To: <19991111132031.A60417@dragon.nuxi.com> from "David O'Brien" at Nov 11, 99 01:20:32 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 Bonjour M. David O'Brien > On Thu, Nov 11, 1999 at 03:29:05PM -0500, Thomas Stromberg wrote: > > I just happened to notice this today. For some reason 'grep' seems to > > think that 'set' output is binary, not text. Seems that GNU grep 2.3 is > > a little too sensitive to text/binary detection. > If I remember zsh has a "bug" and will output a NULL part of the IFS. > I've got a notion to change this. The -CURRENT grep is also very > misleading w/ ``grep -l'' in that you will get "hits" on binary files > because you can't see that "is a binary file" message to know better. Of course, you can. But I will join my voice to Paul and ask you not to. This behaviour was a long standing request/grip where for example one would do grep pattern * and have the terminal going bananas, if pattern was detected in binary files or just by reading directories whith filenames containing *pattern* (On Solaris, you can read() a directory). > > The output of that message should be asked for with an option, not the > default. I can't imagine how many people are going to get weird/eronious > output from scripts now due to it. I don't follow your logic for '-l'. whether it is grep-2.0 or grep-2.3 They all show the filename containing a matching pattern. Grep-2.3 is just more carefull not to send binary data to stdout. In the coming 2.4, if this is such problem for you, there is en environ variable, that will restore the 2.0 behaviour(everything is text) export GREP_OPTIONS=--text -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 18:14:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id AE27A14E2A for ; Thu, 11 Nov 1999 18:14:42 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA21794; Fri, 12 Nov 1999 12:44:39 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911120214.MAA21794@gizmo.internode.com.au> Subject: Re: panic: nexus_setup_intr: NULL irq resource! To: peter.jeremy@alcatel.com.au Date: Fri, 12 Nov 1999 12:44:39 +1030 (CST) Cc: newton@internode.com.au, current@FreeBSD.ORG In-Reply-To: <99Nov12.125653est.40350@border.alcanet.com.au> from "Peter Jeremy" at Nov 12, 99 01:02:46 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 Peter Jeremy wrote: > Since your patch effectively turns isa_setup_intr() into a nop for > this case, a better patch would seem to be to skip the call to > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > of sioattach() when you're attaching a slave SIO port. Absolutely true. :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 18:19:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8BD5414FE1 for ; Thu, 11 Nov 1999 18:19:21 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Fri, 12 Nov 1999 13:13:11 +1100 Content-return: prohibited Date: Fri, 12 Nov 1999 13:19:11 +1100 From: Peter Jeremy Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? In-reply-to: <199911120213.VAA06622@mccoy2.ECE.McGill.CA> To: Alain Magloire Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov12.131311est.40336@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991111132031.A60417@dragon.nuxi.com> <199911120213.VAA06622@mccoy2.ECE.McGill.CA> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-12 13:13:54 +1100, Alain Magloire wrote: >(On Solaris, you can read() a directory). On any real Unix you can read() a directory - `everything is a file'. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 20: 2: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from spock2.ECE.McGill.CA (Spock2.ECE.McGill.CA [132.206.63.11]) by hub.freebsd.org (Postfix) with ESMTP id 24B1814F3B for ; Thu, 11 Nov 1999 20:01:59 -0800 (PST) (envelope-from alainm@macs.ece.mcgill.ca) Received: from mccoy2.ECE.McGill.CA (alainm@Mccoy2.ECE.McGill.CA [132.206.63.174]) by spock2.ECE.McGill.CA (8.8.8/8.8.8) with ESMTP id XAA04662; Thu, 11 Nov 1999 23:03:00 -0500 (EST) From: Alain Magloire Received: by mccoy2.ECE.McGill.CA (8.8.8) id XAA07619; Thu, 11 Nov 1999 23:02:55 -0500 (EST) Message-Id: <199911120402.XAA07619@mccoy2.ECE.McGill.CA> Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? To: peter.jeremy@alcatel.com.au Date: Thu, 11 Nov 1999 23:02:55 -0500 (EST) Cc: bug-gnu-utils@gnu.org, freebsd-current@freebsd.org In-Reply-To: <99Nov12.131311est.40336@border.alcanet.com.au> from "Peter Jeremy" at Nov 12, 99 01:19:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bonjour M. Peter Jeremy > On 1999-Nov-12 13:13:54 +1100, Alain Magloire wrote: > >(On Solaris, you can read() a directory). > > On any real Unix you can read() a directory - `everything is a file'. > Yes, and real programmers do not eat quiche either. For the Solaris comment, maybe I'm mistaken, maybe it was Linux that could not open/read directories, I do not remember. open()/read()'ing directories was never portable, even in the ranks of "real" Unix. Or perhaps depending on the filesystems it is not permitted it. You don't like opendir() and its friends *dir() ? -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 20:50:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FCB714DAE for ; Thu, 11 Nov 1999 20:50:39 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 4512300; Thu, 11 Nov 1999 22:50:37 -0600 Message-Id: <4.2.0.58.19991111224704.015fe070@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 11 Nov 1999 22:50:37 -0600 To: freebsd-current@freebsd.org From: Jim King Subject: pnp and AWE64 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just picked up an AWE64 to use until the Vortex2 driver is working. The card is detected in Win98, but unfortunately the new PnP code in -current (cvsup'ed this evening) doesn't seem to find this card at all. Nothing shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at all about the AWE64. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 11 23:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D47CD14A00 for ; Thu, 11 Nov 1999 23:39:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA65310; Thu, 11 Nov 1999 23:39:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA61511; Thu, 11 Nov 1999 23:39:10 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Nov 1999 23:39:10 -0800 From: "David O'Brien" To: Paul Eggert Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991111233909.A60558@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com> <199911120037.QAA06642@shade.twinsun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911120037.QAA06642@shade.twinsun.com>; from eggert@twinsun.com on Thu, Nov 11, 1999 at 04:37:08PM -0800 X-Operating-System: FreeBSD 4.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 > Please don't change the algorithm to deduce which files are binary. > It was the subject of much design discussion in the GNU project, and > is fairly consistent across other GNU applications. Sounds reasonable. > The -CURRENT grep is also very misleading w/ ``grep -l'' in that > you will get "hits" on binary files because you can't see that "is > a binary file" message to know better. > > I find it useful to see the names of all files matching the pattern. Yes, but I find saying all binary files match a pattern, weird. $ grep i /COPYRIGHT /kernel /COPYRIGHT:All of the documentation and software included in the ..snip.. Binary file /kernel matches Upto FreeBSD 4.0, we used Grep version 2.0 and added the "-a" which made grep ignore binary files. $ grep-2.0 -a i /COPYRIGHT /kernel /COPYRIGHT:All of the documentation and software included in the ..snip.. I prefere this and it just seems right to ignore binary files. But its not so bad since I can read the "Binary". But using the "-l" flag will give: $ grep -l i /COPYRIGHT /kernel /COPYRIGHT /kernel which I find very misleading. Would it be possible to either ignore binary files when "-l" is in affect. OR to add an ignore binary file flag (like FreeBSD has in 2.x and 3.x)? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 0:12:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id 3B0AC14C0F for ; Fri, 12 Nov 1999 00:12:43 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id AAA08234; Fri, 12 Nov 1999 00:11:35 -0800 (PST) Received: from green.twinsun.com (green.twinsun.com [192.54.239.71]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id AAA03804; Fri, 12 Nov 1999 00:11:22 -0800 (PST) Received: (eggert@localhost) by green.twinsun.com (8.9.3+Sun/8.9.3) id AAA09655; Fri, 12 Nov 1999 00:11:22 -0800 (PST) Date: Fri, 12 Nov 1999 00:11:22 -0800 (PST) From: Paul Eggert Message-Id: <199911120811.AAA09655@green.twinsun.com> To: obrien@NUXI.com Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <19991111233909.A60558@dragon.nuxi.com> (obrien@NUXI.com) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com> <199911120037.QAA06642@shade.twinsun.com> <19991111233909.A60558@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Thu, 11 Nov 1999 23:39:10 -0800 From: "David O'Brien" Would it be possible to either ignore binary files when "-l" is in affect. OR to add an ignore binary file flag (like FreeBSD has in 2.x and 3.x)? The latter sounds reasonable, though it'd have to be spelled differently from -a since -a is now taken. Perhaps --skip-binary-files, by analogy with the existing --directories=skip option? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 1: 4:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles544.castles.com [208.214.165.108]) by hub.freebsd.org (Postfix) with ESMTP id A7BC514C38 for ; Fri, 12 Nov 1999 01:04: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.3/8.8.8) with ESMTP id AAA00712; Fri, 12 Nov 1999 00:54:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911120854.AAA00712@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 19:05:41 PST." <199911050305.TAA50795@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 00:54:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The only real way to do this "right" is going to be to have the X > > > > server load a KLD, which will then be able to hook the relevant > > > > interrupt(s). Any other alternative involves interrupt delivery to > > > > user-space, which is just not practical. > > > > > > Hi Mike, > > > Your idea sounds intriguing . How should we wired the KLD to > > > the X server? or how will the KLD inform the X server that it > > > has received a vertical retrace interrupt . > > > > The X server would have to load the KLD when it starts. The KLD would > > have to contain _all_ of the code that would run when the interrupt > > triggered. You would still have absolutely no latency guarantee on > > delivery of the interrupt to the KLD; you'd have to check on entry to > > the handler to see whether you weren't already too late. > > > > Basically, the whole idea is just totally screwed. You shouldn't be > > trying to do this because it just can't be done right. > > I should be trying to do this for it can have interesting applications such > as a Tivo player. Not sure what the problem with interrupt latency is ... > Can you elaborate a little bit more ? If you're talking about a specific piece of hardware whose design you are in control of, you can tweak the hardware/software combination to achieve the desired goal. The point I was trying to make was that in the _general_ case, this can't be done with software alone. You require the cooperation of hardware that just can't be obtained from your average PC. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Nov 12 1:25:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 58A2714C38 for ; Fri, 12 Nov 1999 01:25:39 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA21986 for current@FreeBSD.org; Fri, 12 Nov 1999 10:14:43 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Fri, 12 Nov 1999 10:14:36 +0100 From: Marcel Moolenaar Message-ID: <382BDA7C.A7C755C1@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: egcs unstable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After (by accident) compiling world (excluding kernel) with optimization disabled (ie -O0) and installing the resulting binaries, xemacs (21.1.7) coredumps with a bus error. I recompiled and reinstalled xemacs and all was fine. Now, after building and installing world (excluding kernel again) with optimization (ie -O), xemacs does exactly the same: core dumps on bus error. I'll recompile xemacs again and expect it to be solved, but something is definitely broken: xemacs should not core dump after recompiling world with only a simple change in compiler flags. I'll try out gcc-2.95.2 to see if it has the same problems... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Nov 12 2: 5:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id DEF5814BDC for ; Fri, 12 Nov 1999 02:05:07 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA38677; Fri, 12 Nov 1999 10:07:02 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 12 Nov 1999 10:07:02 +0000 (GMT) From: Doug Rabson To: Mark Newton Cc: peter.jeremy@alcatel.com.au, current@freebsd.org Subject: Re: panic: nexus_setup_intr: NULL irq resource! In-Reply-To: <199911120214.MAA21794@gizmo.internode.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 Fri, 12 Nov 1999, Mark Newton wrote: > Peter Jeremy wrote: > > > Since your patch effectively turns isa_setup_intr() into a nop for > > this case, a better patch would seem to be to skip the call to > > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > > of sioattach() when you're attaching a slave SIO port. > > Absolutely true. :-) Something like this should work: Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.273 diff -u -r1.273 sio.c --- sio.c 1999/10/28 05:06:12 1.273 +++ sio.c 1999/11/12 10:06:15 @@ -903,6 +903,7 @@ u_int flags = device_get_flags(dev); int rid; struct resource *port; + u_long junk; rid = 0; port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, @@ -1112,12 +1113,19 @@ com->pps.ppscap = PPS_CAPTUREASSERT | PPS_CAPTURECLEAR; pps_init(&com->pps); - rid = 0; - com->irqres = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0ul, ~0ul, 1, - RF_SHAREABLE | RF_ACTIVE); - BUS_SETUP_INTR(device_get_parent(dev), dev, com->irqres, - INTR_TYPE_TTY | INTR_TYPE_FAST, - siointr, com, &ih); + /* + * Only setup the irq if there is one (in multiport, only the + * master has an irq. + */ + if (bus_get_resource(dev, SYS_RES_IRQ, &junk, &junk) == 0) { + rid = 0; + com->irqres = bus_alloc_resource(dev, SYS_RES_IRQ, + &rid, 0ul, ~0ul, 1, + RF_SHAREABLE | RF_ACTIVE); + BUS_SETUP_INTR(device_get_parent(dev), dev, com->irqres, + INTR_TYPE_TTY | INTR_TYPE_FAST, + siointr, com, &ih); + } return (0); } -- 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 Fri Nov 12 4:10:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 6296614BFE for ; Fri, 12 Nov 1999 04:10:06 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p61-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA19705; Fri, 12 Nov 1999 23:16:17 +1100 Date: Fri, 12 Nov 1999 23:09:59 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Peter Jeremy Cc: Mark Newton , current@FreeBSD.ORG Subject: Re: panic: nexus_setup_intr: NULL irq resource! In-Reply-To: <99Nov12.125653est.40350@border.alcanet.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 Fri, 12 Nov 1999, Peter Jeremy wrote: > On 1999-Nov-12 12:35:01 +1100, Mark Newton wrote: > >The problem is that the BUS_SETUP_INTR() method for ISA seems to > >absolutely require the specification of an IRQ, even though IRQ > >specification is absolutely prohibited for non-master ports in > >AST-compatible multi-port sio cards. Gah. This is fixed differently (directly in the driver) in nsio (dev/sio/sio.c) rev.1.267. Both fixes are probably necessary and more or less correct. Drivers shouldn't attempt to register null interrupts, and attempting this probably shouldn't cause panics. > As an aside, why doesn't our SIO driver work with ports that don't > have interrupts? Same problem. Ports that don't have interrupts give polled mode, and the driver shouldn't attempt to register the null interrupts for polled mode, but this was broken when the driver was converted to new-bus. > >I'm not completely sure that this patch does the right thing > > Since your patch effectively turns isa_setup_intr() into a nop for > this case, a better patch would seem to be to skip the call to > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > of sioattach() when you're attaching a slave SIO port. nsio still has the bus_alloc_resource(). This seems to be a harmless but bogus no-op if the resource isn't there. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 5:24:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 446C614BE5 for ; Fri, 12 Nov 1999 05:24:13 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 4718500; Fri, 12 Nov 1999 07:24:11 -0600 Message-Id: <4.2.0.58.19991112071811.015e8c20@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 12 Nov 1999 07:24:11 -0600 To: freebsd-current@freebsd.org From: Jim King Subject: Re: pnp and AWE64 In-Reply-To: <4.2.0.58.19991111224704.015fe070@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:50 PM 11/11/1999 -0600, Jim King wrote: >I just picked up an AWE64 to use until the Vortex2 driver is working. The >card is detected in Win98, but unfortunately the new PnP code in -current >(cvsup'ed this evening) doesn't seem to find this card at all. Nothing >shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at >all about the AWE64. One more bit of info: this PC (Dell Dimension R450) has a Phoenix BIOS, which has a setting "Plug-n-Play OS? Yes/No". Changing it from No to Yes made the kernel find the AWE64. Unfortunately changing that setting also made the 3C905B NIC quit working: xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 Another oddity: Although the AWE64 gets picked up by the pcm driver, pnpinfo still only shows the PnP modem - no mention of the AWE64. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 6:53:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1B16814D26 for ; Fri, 12 Nov 1999 06:53:12 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B2A7A1C6D; Fri, 12 Nov 1999 22:53:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: Peter Jeremy , Mark Newton , current@FreeBSD.ORG Subject: Re: panic: nexus_setup_intr: NULL irq resource! In-reply-to: Your message of "Fri, 12 Nov 1999 23:09:59 +1100." Date: Fri, 12 Nov 1999 22:53:10 +0800 From: Peter Wemm Message-Id: <19991112145310.B2A7A1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Fri, 12 Nov 1999, Peter Jeremy wrote: > > > On 1999-Nov-12 12:35:01 +1100, Mark Newton wrote: > > >The problem is that the BUS_SETUP_INTR() method for ISA seems to > > >absolutely require the specification of an IRQ, even though IRQ > > >specification is absolutely prohibited for non-master ports in > > >AST-compatible multi-port sio cards. Gah. > > This is fixed differently (directly in the driver) in nsio (dev/sio/sio.c) > rev.1.267. Both fixes are probably necessary and more or less correct. > Drivers shouldn't attempt to register null interrupts, and attempting > this probably shouldn't cause panics. > > > As an aside, why doesn't our SIO driver work with ports that don't > > have interrupts? > > Same problem. Ports that don't have interrupts give polled mode, and > the driver shouldn't attempt to register the null interrupts for polled > mode, but this was broken when the driver was converted to new-bus. > > > >I'm not completely sure that this patch does the right thing > > > > Since your patch effectively turns isa_setup_intr() into a nop for > > this case, a better patch would seem to be to skip the call to > > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > > of sioattach() when you're attaching a slave SIO port. > > nsio still has the bus_alloc_resource(). This seems to be a harmless > but bogus no-op if the resource isn't there. > > Bruce I think I've got all this fixed (or closer to being fixed) in a merge of some nsio stuff back into sio.c so nsio.c can be zapped for now. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 7:14: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 9C0A414E9C; Fri, 12 Nov 1999 07:13:47 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p61-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA25866; Sat, 13 Nov 1999 02:20:01 +1100 Date: Sat, 13 Nov 1999 02:13:41 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: cracauer@freebsd.org Cc: current@freebsd.org Subject: shell pipeline bug 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 `man sh' now hangs when the pager is exited. This is caused by the recent change to sh/eval.c Simplified example: sh -c "jot 6000 | cat | head" hangs. This example is almost minimal. The size of the data written by the first command must be large enough to not fit in the pipe; the middle command must be there, and the last command in the pipe must exit before reading all the data. The middle command should be killed by SIGPIPE when its output pipe is closed; this output pipe should be closed when the final command exits, but this is not happening because the shell is holding it open. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 7:21:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id ED51514EE1 for ; Fri, 12 Nov 1999 07:21:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id HAA66723; Fri, 12 Nov 1999 07:21:00 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 07:21:00 -0800 From: "David O'Brien" To: Paul Eggert Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991112072100.F63337@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com> <199911120037.QAA06642@shade.twinsun.com> <19991111233909.A60558@dragon.nuxi.com> <199911120811.AAA09655@green.twinsun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199911120811.AAA09655@green.twinsun.com> X-Operating-System: FreeBSD 3.3-STABLE 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 Fri, Nov 12, 1999 at 12:11:22AM -0800, Paul Eggert wrote: > Date: Thu, 11 Nov 1999 23:39:10 -0800 > From: "David O'Brien" > > Would it be possible to either ignore binary files when "-l" is in > affect. OR to add an ignore binary file flag (like FreeBSD has in > 2.x and 3.x)? > > The latter sounds reasonable, though it'd have to be spelled > differently from -a since -a is now taken. Perhaps > --skip-binary-files, by analogy with the existing --directories=skip > option? The BSD's favor one letter options. At the time -a was not used for anything. Is there a letter we could use today? I used -a almost all the time, so typing "--skip-binary-files" would have been unacceptable. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 8:42:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 9F46314D27 for ; Fri, 12 Nov 1999 08:42:33 -0800 (PST) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991112164233.PEYW21783.mail.rdc2.on.home.com@mired.eh.local>; Fri, 12 Nov 1999 08:42:33 -0800 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id LAA73612; Fri, 12 Nov 1999 11:42:33 -0500 (EST) (envelope-from kws) To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: egcs unstable References: <382BDA7C.A7C755C1@scc.nl> From: Kevin Street Date: 12 Nov 1999 11:42:32 -0500 In-Reply-To: Marcel Moolenaar's message of "Fri, 12 Nov 1999 10:14:36 +0100" Message-ID: <87ogczsltz.fsf@mired.eh.local> Lines: 18 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar writes: > After (by accident) compiling world (excluding kernel) with optimization > disabled (ie -O0) and installing the resulting binaries, xemacs (21.1.7) > coredumps with a bus error. I recompiled and reinstalled xemacs and all > was fine. Now, after building and installing world (excluding kernel > again) with optimization (ie -O), xemacs does exactly the same: core > dumps on bus error. I'll recompile xemacs again and expect it to be > solved, but something is definitely broken: xemacs should not core dump > after recompiling world with only a simple change in compiler flags. I don't believe that it's the compiler flag change that is causing this. My xemacs has been core dumping after each build and install of world the last couple of times I did it. I have not had time to investigate the real cause yet. -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 8:45:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 6B48814D27; Fri, 12 Nov 1999 08:45:27 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id RAA15655; Fri, 12 Nov 1999 17:44:52 +0100 (CET) Date: Fri, 12 Nov 1999 17:44:52 +0100 From: Martin Cracauer To: Bruce Evans Cc: cracauer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: shell pipeline bug Message-ID: <19991112174451.A15638@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Bruce Evans on Sat, Nov 13, 1999 at 02:13:41AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Bruce Evans wrote: > `man sh' now hangs when the pager is exited. This is caused by the recent > change to sh/eval.c My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. Do you have 1.24? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 9: 9: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D4D4C14DED for ; Fri, 12 Nov 1999 09:08:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA67234; Fri, 12 Nov 1999 09:08:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA87874; Fri, 12 Nov 1999 09:08:24 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" To: Alain Magloire Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991112090823.B87828@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991111132031.A60417@dragon.nuxi.com> <199911120213.VAA06622@mccoy2.ECE.McGill.CA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911120213.VAA06622@mccoy2.ECE.McGill.CA>; from alainm@rcsm.ece.mcgill.ca on Thu, Nov 11, 1999 at 09:13:54PM -0500 X-Operating-System: FreeBSD 4.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 Thu, Nov 11, 1999 at 09:13:54PM -0500, Alain Magloire wrote: > Of course, you can. But I will join my voice to Paul and ask you not to. > This behaviour was a long standing request/grip where for example one > would do > > grep pattern * > > and have the terminal going bananas, if pattern was detected in binary What I was proposing to change was that binary files were ignored when "-l" was in affect. I was also implying that binary files should be silently ignored unless one uses the 2.3 "-a" flag. > I don't follow your logic for '-l'. whether it is grep-2.0 or grep-2.3 > They all show the filename containing a matching pattern. FreeBSD's previous grep had a "-a" flag to ignore binary files. Thus I'm trying to find a replacement for the old ``grep -al'' usage. > In the coming 2.4, if this is such problem for you, there is en environ > variable, that will restore the 2.0 behaviour(everything is text) Not quite what I'm looking for. I want a silent ignore of binary files. I think it should take an option to not ignore binary files. Add 2.3's "-a" if you *really* want full greping of binary files. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 9:17:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B76E214E9C; Fri, 12 Nov 1999 09:17:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p61-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA29391; Sat, 13 Nov 1999 04:22:13 +1100 Date: Sat, 13 Nov 1999 04:15:54 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Martin Cracauer Cc: cracauer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: shell pipeline bug In-Reply-To: <19991112174451.A15638@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 On Fri, 12 Nov 1999, Martin Cracauer wrote: > In , Bruce Evans wrote: > > `man sh' now hangs when the pager is exited. This is caused by the recent > > change to sh/eval.c > > My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. > > Do you have 1.24? Yes, of course. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 10:35:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 4B82815036; Fri, 12 Nov 1999 10:35:18 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id TAA16054; Fri, 12 Nov 1999 19:35:05 +0100 (CET) Date: Fri, 12 Nov 1999 19:35:05 +0100 From: Martin Cracauer To: Bruce Evans Cc: Martin Cracauer , cracauer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: shell pipeline bug Message-ID: <19991112193504.A16025@cons.org> References: <19991112174451.A15638@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Bruce Evans on Sat, Nov 13, 1999 at 04:15:54AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Bruce Evans wrote: > On Fri, 12 Nov 1999, Martin Cracauer wrote: > > > In , Bruce Evans wrote: > > > `man sh' now hangs when the pager is exited. This is caused by the recent > > > change to sh/eval.c > > > > My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. > > > > Do you have 1.24? > > Yes, of course. Sorry, I can reproduce the hangs with 1.23, while I can't with 1.24. The problem is: A pipe with more data that sh's threshold for forking is and the receiving end process exits before the sending process, not consuming all of the pipe's contents. That exactly what 1.24 fixed (for me :-). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 12:21:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 370BB14D47 for ; Fri, 12 Nov 1999 12:21:24 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA56849; Fri, 12 Nov 1999 20:23:46 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 12 Nov 1999 20:23:46 +0000 (GMT) From: Doug Rabson To: Jim King Cc: freebsd-current@freebsd.org Subject: Re: pnp and AWE64 In-Reply-To: <4.2.0.58.19991112071811.015e8c20@mail.sstar.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, 12 Nov 1999, Jim King wrote: > At 10:50 PM 11/11/1999 -0600, Jim King wrote: > >I just picked up an AWE64 to use until the Vortex2 driver is working. The > >card is detected in Win98, but unfortunately the new PnP code in -current > >(cvsup'ed this evening) doesn't seem to find this card at all. Nothing > >shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > >all about the AWE64. > > One more bit of info: this PC (Dell Dimension R450) has a Phoenix BIOS, > which has a setting "Plug-n-Play OS? Yes/No". Changing it from No to Yes > made the kernel find the AWE64. Unfortunately changing that setting also > made the 3C905B NIC quit working: > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 > xl0: couldn't map ports/memory > device_probe_and_attach: xl0 attach returned 6 > > Another oddity: Although the AWE64 gets picked up by the pcm driver, > pnpinfo still only shows the PnP modem - no mention of the AWE64. FreeBSD isn't a fully PnP OS since it doesn't do resource allocation for pci. You must leave the setting at No. -- 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 Fri Nov 12 14: 2:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from kar.net (sunone.kar.net [195.178.131.131]) by hub.freebsd.org (Postfix) with ESMTP id D063015035; Fri, 12 Nov 1999 14:02:02 -0800 (PST) (envelope-from volodya@mail.kar.net) Received: from kushnir1.kiev.ua by kar.net with ESMTP id XAA19833; (8.8.7/2.b2) Fri, 12 Nov 1999 23:48:41 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.9.3/8.9.3) with ESMTP id XAA01694; Fri, 12 Nov 1999 23:48:16 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Fri, 12 Nov 1999 23:48:13 +0200 (EET) From: Vladimir Kushnir To: Doug Rabson Cc: cvs-all@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <199911111648.IAA85795@freefall.freebsd.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 Sorry, but is there any driver for YMF724 except for OSS? If so (even in some under-pre-alpha state) I'd be more than happy to test it. On Thu, 11 Nov 1999, Doug Rabson wrote: > dfr 1999/11/11 08:48:01 PST > > Modified files: > sys/isa isa_common.c > Log: > Reorganise the code so that I can add custom identify drivers dynamically > during autoconfig to support strange hardware (such as the Yamaha DS-1) > which implements 'legacy' ISA devices as well as a PCI device. This will > allow the PCI driver for the YMF724 to add the legacy devices to the ISA > bus and will allow the PnP system to automatically allocate the resources > for those devices. > > Revision Changes Path > 1.12 +72 -2 src/sys/isa/isa_common.c > > Thanks in advance, Vladimir (who's getting sort of desperate). -- ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 15:39:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from nowcool.dhs.org (FX3-1-031.mgfairfax.rr.com [24.28.200.31]) by hub.freebsd.org (Postfix) with ESMTP id 4B51D14BEE for ; Fri, 12 Nov 1999 15:39:32 -0800 (PST) (envelope-from freebsd@nowcool.dhs.org) Received: from localhost (freebsd@localhost) by nowcool.dhs.org (8.9.3/8.9.3) with ESMTP id SAA00542; Fri, 12 Nov 1999 18:39:14 GMT (envelope-from freebsd@nowcool.dhs.org) Date: Fri, 12 Nov 1999 18:39:14 +0000 (GMT) From: Byung Yang To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: new kernel. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok..in addition to my earlier post, I am NOT using Linux netscape and I built the whole system from the source code. dist/module/kernel they are all from the same source tree. The thing is I never had this kind of problem before. It was working fine then. I built the world/kernel at Tue Nov 9 20:02:29 and configuration is not that different from GENERIC except it has firewall, sound, and new ata0 controller/driver support(I am using Promise Tech. Ultra66 controller card) included. At startup, I don't even have linux module loaded up. the only modules i use at startup is vinum. If nobody else is experiencing this, maybe I will sup it again and compile everything(takes 2.5 hrs so i can't do it everyday) from the new source tree and see what happens. Thanks for your comments. On Thu, 11 Nov 1999, Alfred Perlstein wrote: > On Thu, 11 Nov 1999, Byung Yang wrote: > > > > > I supped two days ago and compiled everything. Now, if I try to launch > > netscape, the computer just freezes right up there. First, I thought it > > was the netscape, but when I was searching for a file on my computer, but > > took longer than I thought and pressed ^C, it froze again. > > > > I heard and also suspect that this has something to do with the new signal > > algorithm.. does anybody experience this? > > Yes, but... what kind of configuration do you have? Since my crystal > ball is in the shop I really have no way of dicerning what's going on. > > -Alfred > > > > 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 Nov 12 15:40:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id 3D7F014E63; Fri, 12 Nov 1999 15:40:05 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id PAA13895; Fri, 12 Nov 1999 15:39:58 -0800 (PST) Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id PAA00358; Fri, 12 Nov 1999 15:39:43 -0800 (PST) Received: (eggert@localhost) by shade.twinsun.com (8.9.3+Sun/8.9.3) id PAA07222; Fri, 12 Nov 1999 15:39:43 -0800 (PST) Date: Fri, 12 Nov 1999 15:39:43 -0800 (PST) From: Paul Eggert Message-Id: <199911122339.PAA07222@shade.twinsun.com> To: obrien@freebsd.org Cc: alainm@rcsm.ece.mcgill.ca, tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <19991112090823.B87828@dragon.nuxi.com> (obrien@freebsd.org) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <19991111132031.A60417@dragon.nuxi.com> <199911120213.VAA06622@mccoy2.ECE.McGill.CA> <19991112090823.B87828@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" I want a silent ignore of binary files. It'd be reasonable to add an option to do this, after the feature freeze is over and 2.4 comes out. I think it should take an option to not ignore binary files. I disagree. If I type `grep pattern file' and get no output, then I should be able to conclude that there are no instances of `pattern' in `file'. But under your proposal, I wouldn't be able to conclude that: all I would know is that either the file contained no instances, or the file was binary. This is confusing and is less useful in practice than grep 2.3's behavior. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 16: 9:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw3.prontomail.com (mailgw3.prontomail.com [209.185.149.199]) by hub.freebsd.org (Postfix) with ESMTP id 9DA6715049 for ; Fri, 12 Nov 1999 16:09:19 -0800 (PST) (envelope-from peter.edwards@ireland.com) Received: from mail33.prontomail.com (209.185.149.133) by mailgw3.prontomail.com (NPlex 2.0.123) for current@freebsd.org; Fri, 12 Nov 1999 16:03:49 -0800 Received: from web22 (209.185.149.222) by mail33.prontomail.com (NPlex 2.0.123); Fri, 12 Nov 1999 16:03:21 -0800 From: "Peter Edwards" Message-Id: <1829F7D8FD893D1178D000807CFB3258@peter.edwards.ireland.com> Date: Sun, 14 Nov 1999 00:07:52 +2400 X-Priority: Normal To: current@freebsd.org Subject: fstat(1) breakage + fix Cc: peter.edwards@openet-telecom.com X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Type: multipart/mixed ;boundary=Interpart.Boundary.11.22.33.M2Y13749 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > THIS IS A MESSAGE IN 'MIME' FORMAT. Your mail reader does not support MIME. > Please read the first section, which is plain text, and ignore the rest. --Interpart.Boundary.11.22.33.M2Y13749 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, fstat(1) should be able to take a set of filenames as arguments to limit the results of its output to the specified files. However, it doesn't work at the moment, because of the existance of udev_t. (It compares the st_dev from the stat structure used by stat(2) with in-kernel dev_t structures. As it stands, "fstat " will never produce any output other than a header.) I've attached a patch that appears reliable. Can someone review it (and possibly commit??) -- Peter. _____________________________________ Get your free E-mail at http://www.ireland.com --Interpart.Boundary.11.22.33.M2Y13749 Content-Type: application/octet-stream; name="fstat.c.patch" Content-Disposition: attachment; filename="fstat.c.patch" Content-Transfer-Encoding: base64 Content-Description: fstat.c.patch KioqIC91c3Ivc3JjL3Vzci5iaW4vZnN0YXQvZnN0YXQuYy5vbGQJVHVlIEF1ZyAzMSAwMjox MjoxMyAxOTk5Ci0tLSAvdXNyL3NyYy91c3IuYmluL2ZzdGF0L2ZzdGF0LmMJRnJpIE5vdiAx MiAyMzo1NzoyNCAxOTk5CioqKioqKioqKioqKioqKgoqKiogNjEsNjYgKioqKgotLS0gNjEs NjcgLS0tLQogICNpbmNsdWRlIDxzeXMvZmlsZWRlc2MuaD4KICAjaW5jbHVkZSA8c3lzL3F1 ZXVlLmg+CiAgI2luY2x1ZGUgPHN5cy9waXBlLmg+CisgI2luY2x1ZGUgPHN5cy9jb25mLmg+ CiAgI2RlZmluZQlLRVJORUwKICAjaW5jbHVkZSA8c3lzL2ZpbGUuaD4KICAjaW5jbHVkZSA8 dWZzL3Vmcy9xdW90YS5oPgoqKioqKioqKioqKioqKioKKioqIDE1OCwxNjMgKioqKgotLS0g MTU5LDE2NSAtLS0tCiAgdm9pZCBnZXRpbmV0cHJvdG8gX19QKChpbnQgbnVtYmVyKSk7CiAg aW50ICBnZXRmbmFtZSBfX1AoKGNoYXIgKmZpbGVuYW1lKSk7CiAgdm9pZCB1c2FnZSBfX1Ao KHZvaWQpKTsKKyBzdGF0aWMgdWRldl90IGRldjJ1ZGV2IF9fUCgoZGV2X3QgZGV2KSk7CiAg CiAgCiAgaW50CioqKioqKioqKioqKioqKgoqKiogNDg3LDQ5MyAqKioqCiAgCQkgICAgKHZv aWQgKilWVE9JKHZwKSwgUGlkKTsKICAJCXJldHVybiAwOwogIAl9CiEgCWZzcC0+ZnNpZCA9 IGlub2RlLmlfZGV2ICYgMHhmZmZmOwogIAlmc3AtPmZpbGVpZCA9IChsb25nKWlub2RlLmlf bnVtYmVyOwogIAlmc3AtPm1vZGUgPSAobW9kZV90KWlub2RlLmlfbW9kZTsKICAJZnNwLT5z aXplID0gKHVfbG9uZylpbm9kZS5pX3NpemU7Ci0tLSA0ODksNTAwIC0tLS0KICAJCSAgICAo dm9pZCAqKVZUT0kodnApLCBQaWQpOwogIAkJcmV0dXJuIDA7CiAgCX0KISAJLyoKISAJICog VGhlIHN0X2RldiBmcm9tIHN0YXQoMikgaXMgYSB1ZGV2X3QuIFRoZXNlIGtlcm5lbCBzdHJ1 Y3R1cmVzCiEgCSAqIGNvbnRhaW4gZGV2X3Qgc3RydWN0dXJlcy4gV2UgbmVlZCB0byBjb252 ZXJ0IHRvIHVkZXYgdG8gbWFrZQohIAkgKiBjb21wYXJpc29ucwohIAkgKi8KISAJZnNwLT5m c2lkID0gZGV2MnVkZXYoaW5vZGUuaV9kZXYpICYgMHhmZmZmOwogIAlmc3AtPmZpbGVpZCA9 IChsb25nKWlub2RlLmlfbnVtYmVyOwogIAlmc3AtPm1vZGUgPSAobW9kZV90KWlub2RlLmlf bW9kZTsKICAJZnNwLT5zaXplID0gKHVfbG9uZylpbm9kZS5pX3NpemU7CioqKioqKioqKioq KioqKgoqKiogNzI3LDczMiAqKioqCi0tLSA3MzQsNzU2IC0tLS0KICAJcmV0dXJuOwogIGJh ZDoKICAJcHJpbnRmKCIqIGVycm9yXG4iKTsKKyB9CisgCisgCisgLyoKKyAgKiBSZWFkIHRo ZSBzcGVjaW5mbyBzdHJ1Y3R1cmUgaW4gdGhlIGtlcm5lbCAoYXMgcG9pbnRlZCB0byBieSBh IGRldl90KQorICAqIGluIG9yZGVyIHRvIHdvcmsgb3V0IHRoZSBhc3NvY2lhdGVkIHVkZXZf dAorICAqLworIHN0YXRpYyB1ZGV2X3QgZGV2MnVkZXYoZGV2KQorICAgICBkZXZfdCBkZXY7 CisgeworIAlzdHJ1Y3Qgc3BlY2luZm8gc2k7CisgCWlmIChrdm1fcmVhZChrZCwgKHVfbG9u ZylkZXYsIChjaGFyICopJnNpLCBzaXplb2Ygc2kpID09IHNpemVvZiBzaSkgeworIAkJcmV0 dXJuIHNpLnNpX3VkZXY7CisgCX0gZWxzZSB7CisgCQlkcHJpbnRmKHN0ZGVyciwgImNhbid0 IGNvbnZlcnQgZGV2X3QgJXggdG8gYSB1ZGV2X3RcbiIsIGRldik7CisgCQlyZXR1cm4gLTE7 CisgCX0KICB9CiAgCiAgLyoK --Interpart.Boundary.11.22.33.M2Y13749-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 16:19:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 18E0314DBB for ; Fri, 12 Nov 1999 16:19:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA69819; Fri, 12 Nov 1999 16:19:37 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA62831; Fri, 12 Nov 1999 16:19:32 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 16:19:32 -0800 From: "David O'Brien" To: Paul Eggert Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991112161931.A90421@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991111132031.A60417@dragon.nuxi.com> <199911120213.VAA06622@mccoy2.ECE.McGill.CA> <19991112090823.B87828@dragon.nuxi.com> <199911122339.PAA07222@shade.twinsun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911122339.PAA07222@shade.twinsun.com>; from eggert@twinsun.com on Fri, Nov 12, 1999 at 03:39:43PM -0800 X-Operating-System: FreeBSD 4.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 Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: > Date: Fri, 12 Nov 1999 09:08:24 -0800 > From: "David O'Brien" > > I want a silent ignore of binary files. > > It'd be reasonable to add an option to do this, after the feature > freeze is over and 2.4 comes out. Cool! :-) Would you able to reserve the option's letter and GNU-style long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. Is there an alpha of 2.4 available anywhere? I wouldn't mind adding the environmental vars support to our 2.3 also. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 16:40:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 294ED14C2A for ; Fri, 12 Nov 1999 16:40:54 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.228]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FL4001RS1IKAY@mta1.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Fri, 12 Nov 1999 16:32:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 0DCB891684; Fri, 12 Nov 1999 16:32:44 -0800 (PST) Date: Fri, 12 Nov 1999 16:32:44 -0800 (PST) From: Alex Zepeda Subject: Re: pnp and AWE64 In-reply-to: <4.2.0.58.19991111224704.015fe070@mail.sstar.com> To: Jim King Cc: freebsd-current@FreeBSD.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 Thu, 11 Nov 1999, Jim King wrote: > I just picked up an AWE64 to use until the Vortex2 driver is working. The > card is detected in Win98, but unfortunately the new PnP code in -current > (cvsup'ed this evening) doesn't seem to find this card at all. Nothing > shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > all about the AWE64. FWIW it detects my AWE64 just fine (and yes you must set the PnP OS bit to no). This is with or without the PNPBIOS option int he kernel. It doesn't seem to detect the integrated Yamaha sound bits though (with the PNPBIOS bit). pcm1: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 How about posting your kernel config file? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 16:50: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from spock2.ECE.McGill.CA (Spock2.ECE.McGill.CA [132.206.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C1B4E14C2A; Fri, 12 Nov 1999 16:49:55 -0800 (PST) (envelope-from alainm@macs.ece.mcgill.ca) Received: from mccoy2.ECE.McGill.CA (alainm@Mccoy2.ECE.McGill.CA [132.206.63.174]) by spock2.ECE.McGill.CA (8.8.8/8.8.8) with ESMTP id TAA15508; Fri, 12 Nov 1999 19:50:54 -0500 (EST) From: Alain Magloire Received: by mccoy2.ECE.McGill.CA (8.8.8) id TAA16385; Fri, 12 Nov 1999 19:50:48 -0500 (EST) Message-Id: <199911130050.TAA16385@mccoy2.ECE.McGill.CA> Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? To: obrien@freebsd.org Date: Fri, 12 Nov 1999 19:50:48 -0500 (EST) Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-Reply-To: <19991112090823.B87828@dragon.nuxi.com> from "David O'Brien" at Nov 12, 99 09:08:24 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 Bonjour M. David O'Brien > FreeBSD's previous grep had a "-a" flag to ignore binary files. Thus I'm > trying to find a replacement for the old ``grep -al'' usage. > > > In the coming 2.4, if this is such problem for you, there is en environ > > variable, that will restore the 2.0 behaviour(everything is text) > > Not quite what I'm looking for. I want a silent ignore of binary files. > I think it should take an option to not ignore binary files. Add 2.3's > "-a" if you *really* want full greping of binary files. > Thanks, for the clarifications. It is "dommage" (too bad ?) that the changes were not sent back to gnu. -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 16:54:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 735161508A for ; Fri, 12 Nov 1999 16:54:15 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id BAA24717 for current@FreeBSD.ORG; Sat, 13 Nov 1999 01:54:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id DDE428711; Sat, 13 Nov 1999 01:36:07 +0100 (CET) Date: Sat, 13 Nov 1999 01:36:07 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: egcs unstable Message-ID: <19991113013607.A61288@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <382BDA7C.A7C755C1@scc.nl> <87ogczsltz.fsf@mired.eh.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <87ogczsltz.fsf@mired.eh.local> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kevin Street: > this. My xemacs has been core dumping after each build and install of > world the last couple of times I did it. I have not had time to > investigate the real cause yet. I got the same problem between 3.3-R and 3.3-STABLE as well. Recompiling fixed it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 17: 8:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from spock2.ECE.McGill.CA (Spock2.ECE.McGill.CA [132.206.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 925B1150B2 for ; Fri, 12 Nov 1999 17:08:38 -0800 (PST) (envelope-from alainm@macs.ece.mcgill.ca) Received: from mccoy2.ECE.McGill.CA (alainm@Mccoy2.ECE.McGill.CA [132.206.63.174]) by spock2.ECE.McGill.CA (8.8.8/8.8.8) with ESMTP id UAA16712; Fri, 12 Nov 1999 20:09:30 -0500 (EST) From: Alain Magloire Received: by mccoy2.ECE.McGill.CA (8.8.8) id UAA16471; Fri, 12 Nov 1999 20:09:25 -0500 (EST) Message-Id: <199911130109.UAA16471@mccoy2.ECE.McGill.CA> Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? To: obrien@nuxi.com Date: Fri, 12 Nov 1999 20:09:24 -0500 (EST) Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-Reply-To: <19991112161931.A90421@dragon.nuxi.com> from "David O'Brien" at Nov 12, 99 04:19:32 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 Bonjour M. David O'Brien > On Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: > > Date: Fri, 12 Nov 1999 09:08:24 -0800 > > From: "David O'Brien" > > > > I want a silent ignore of binary files. > > > > It'd be reasonable to add an option to do this, after the feature > > freeze is over and 2.4 comes out. > > Cool! :-) Would you able to reserve the option's letter and GNU-style > long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. > -a, --text is already taken. Option letter is something rather scarce for GNU grep, but I think there's some left ;-) > Is there an alpha of 2.4 available anywhere? I wouldn't mind adding the > environmental vars support to our 2.3 also. > grep-2.3h beta released (Freeze). wget ftp://alpha.gnu.org/gnu/grep/grep-2.3h.tar.gz wget ftp://mccoy.ee.mcgill.ca/pub/alain/grep/beta/2.3/grep-2.3h.tar.gz -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 17:14:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E0A91514D for ; Fri, 12 Nov 1999 17:14:13 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 4983500; Fri, 12 Nov 1999 19:14:06 -0600 Message-Id: <4.2.0.58.19991112191106.0161a680@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 12 Nov 1999 19:13:56 -0600 To: Alex Zepeda From: Jim King Subject: Re: pnp and AWE64 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19991111224704.015fe070@mail.sstar.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_766315773==_" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====================_766315773==_ Content-Type: text/plain; charset="us-ascii"; format=flowed At 04:32 PM 11/12/1999 -0800, Alex Zepeda wrote: >On Thu, 11 Nov 1999, Jim King wrote: > > > I just picked up an AWE64 to use until the Vortex2 driver is working. The > > card is detected in Win98, but unfortunately the new PnP code in -current > > (cvsup'ed this evening) doesn't seem to find this card at all. Nothing > > shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > > all about the AWE64. > >FWIW it detects my AWE64 just fine (and yes you must set the PnP OS bit to >no). This is with or without the PNPBIOS option int he kernel. It >doesn't seem to detect the integrated Yamaha sound bits though (with the >PNPBIOS bit). > >pcm1: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq >5 drq 1,5 on isa0 > >How about posting your kernel config file? Attached, in all it's glory. The relevant lines seem to be: controller pnp0 device pcm0 options PNPBIOS The PNPBIOS line doesn't make a difference for the AWE64 (although it does make some difference - all the motherboard resources show up as unknowns with it enabled). --=====================_766315773==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="RASP.txt" # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.196 1999/10/22 04:36:52 n_hibma Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident RASP maxusers 64 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES options PNPBIOS # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # IDE controller and disks controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # ATAPI devices on wdc? device wcd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) device wst0 #IDE Tape (e.g. Travan) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ncr0 # NCR/Symbios Logic #controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices #controller amd0 # AMD 53C974 (Teckram DC-390(T)) #controller isp0 # Qlogic family #controller dpt0 # DPT Smartcache - See LINT for options! #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # Proprietary or custom CD-ROM Interfaces #device wt0 at isa? port 0x300 irq 5 drq 1 #device mcd0 at isa? port 0x300 irq 10 #device matcd0 at isa? port 0x230 #device scd0 at isa? port 0x230 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at isa? #device pcic1 at isa? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 #device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. #device ax0 # ASIX AX88140A device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vx0 # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. controller miibus0 # MII bus support #device al0 # ADMtek AL981/AN985 (``Comet''/``Centaur'') #device dm0 # Davicom DM9100/DM9102 #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 (``Starfire'') #device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 #device ste0 # Sundance ST201 (D-Link DFE-550TX) #device tl0 # Texas Instruments ThunderLAN #device vr0 # VIA Rhine, Rhine II #device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 irq 10 #device ex0 at isa? port? irq? #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 irq ? # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? irq ? # PCCARD NIC drivers. # ze and zp take over the pcic and cannot coexist with generic pccard # support, nor the ed and ep drivers they replace. #device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf 4 #Berkeley packet filter # USB support controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface controller usb0 # USB Bus (required) device ugen0 # Generic device uhid0 # "Human Interface Devices" device ukbd0 # Keyboard device ulpt0 # Printer controller umass0 # Disks/Mass storage - Requires scbus and da0 device ums0 # Mouse # sound device pcm0 --=====================_766315773==_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 17:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 35FB714C95 for ; Fri, 12 Nov 1999 17:23:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id RAA70282; Fri, 12 Nov 1999 17:23:21 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 17:23:21 -0800 From: "David O'Brien" To: Alain Magloire Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991112172321.B70122@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19991112161931.A90421@dragon.nuxi.com> <199911130109.UAA16471@mccoy2.ECE.McGill.CA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199911130109.UAA16471@mccoy2.ECE.McGill.CA> X-Operating-System: FreeBSD 3.3-STABLE 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 Fri, Nov 12, 1999 at 08:09:24PM -0500, Alain Magloire wrote: > > Cool! :-) Would you able to reserve the option's letter and GNU-style > > long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. > > -a, --text > is already taken. I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU longopt. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 17:53:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C049D150BD for ; Fri, 12 Nov 1999 17:53:09 -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.9.3/8.9.3) with SMTP id UAA45640; Fri, 12 Nov 1999 20:53:03 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 12 Nov 1999 20:53:03 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Alexander Leidinger Cc: dcs@newsguy.com, current@freebsd.org Subject: Re: "man" reads /etc/rc.conf? In-Reply-To: <199911101822.TAA00926@work.net.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Nov 1999, Alexander Leidinger wrote: > On 11 Nov, Daniel C. Sobral wrote: > >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > >> >> spppconfig_isp0=3D"`cat /etc/isdn/connect.parameters`" > > ^^^ > > Calling programs from any of the rc.conf files is considered evil > > and it's looked down on. >=20 > It=B4s there to hide login/passwd information for i4b. But it seems like the end up as arguments to ifconfig at a later date, where a user can pull them out of ps, /proc, etc. The window there is clearly shorter than keeping it in /etc/rc.conf, but still not "secure" per se. The same goes for the use of environmental variables, which can also be listed using ps. Probably spppconfig should accept a filename with the contents as an argument, or the information via a pipe. =20 Robert N M Watson=20 robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 19:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id E968E14D4D for ; Fri, 12 Nov 1999 19:14:21 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id OAA33709; Sat, 13 Nov 1999 14:12:13 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Sat, 13 Nov 1999 14:12:12 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: shell pipeline bug 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 > Simplified example: > > sh -c "jot 6000 | cat | head" Not knowing what jot(1) was, I read the man page. The synopsis says: SYNOPSIS jot [-cnr] [-b word] [-w word] [-s string] [-p precision] [reps [begin ^ [end [s]]]] ^ ...so I type in: $ jot usage: jot [-cnr] [-b word] [-w word] [-s string] [-p precision] [reps [begin [end [s]]]] ^ ^ Is my understanding correct that options in square brackets are optional? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications 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 Fri Nov 12 19:43:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id F233C14D4D for ; Fri, 12 Nov 1999 19:43:26 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11mU6Q-000PGw-00 for freebsd-current@freebsd.org; Sat, 13 Nov 1999 03:43:50 +0000 Date: Sat, 13 Nov 1999 04:43:24 +0100 (CET) From: Marc Schneiders To: freebsd-current@freebsd.org Subject: objformat troubles in make release 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 Something must have changed somewhere very recently, but I cannot see what. Make release (current on current of four or five days old) worked ok two days ago, now it stops after a few minutes over objformat not found (full output below). I've tried to set it manually (setenv OBJFORMAT=elf) and it is of course in /usr/src/release/Makefile. Any suggestion? Thanks! Marc [after "MAKEDEV all" and some little bits in /usr/src/etc:] cd /usr/src/release/.. && make installworld DESTDIR=/reserve NOMAN=1 cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib PERL5LIB=/reserve/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" /usr/obj/usr/src/tmp/usr/bin/make -f Makefile.inc1 reinstall objformat: not found "/usr/src/Makefile.inc1", line 972: warning: "objformat" returned non-zero status echo:No such file or directory *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 4:20am up 1 day, 16:06, load average: 0.03 0.06 0.07 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 12 20:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id C85CE14FE4 for ; Fri, 12 Nov 1999 20:46:13 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id UAA16227; Fri, 12 Nov 1999 20:45:24 -0800 (PST) Received: from green.twinsun.com (green.twinsun.com [192.54.239.71]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id UAA01035; Fri, 12 Nov 1999 20:45:08 -0800 (PST) Received: (eggert@localhost) by green.twinsun.com (8.9.3+Sun/8.9.3) id UAA03345; Fri, 12 Nov 1999 20:45:10 -0800 (PST) Date: Fri, 12 Nov 1999 20:45:10 -0800 (PST) From: Paul Eggert Message-Id: <199911130445.UAA03345@green.twinsun.com> To: obrien@NUXI.com Cc: alainm@rcsm.ece.mcgill.ca, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <19991112172321.B70122@relay.nuxi.com> (obrien@NUXI.com) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <19991112161931.A90421@dragon.nuxi.com> <199911130109.UAA16471@mccoy2.ECE.McGill.CA> <19991112172321.B70122@relay.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Fri, 12 Nov 1999 17:23:21 -0800 From: "David O'Brien" I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU longopt. Another possibility would be to follow the example of the existing --directories=ACTION option, e.g. something like this: --binary-files=ACTION how to handle binary files ACTION is 'read', 'skip', or 'summarize' (default) -I equivalent to --binary-files=skip -a, --text equivalent to --binary-files=read To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 0:28:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 901CC14C13; Sat, 13 Nov 1999 00:28:46 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3a-15.cybcon.com [205.147.75.144]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id AAA09161; Sat, 13 Nov 1999 00:28:38 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 13 Nov 1999 00:27:02 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Make World dies....... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a cvsup today for -current to compile on my Alphastation 200 4/233 and douring a make world, this is what I got: --------------------------------------------- ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DN OSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARE D all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/g nu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "alpha/xm-alpha.h"' > tconfig.h echo '#include "alpha/alpha.h"' > tm.h echo '#include "alpha/freebsd.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../c -freebsd\" -DHAIFA -I/usr/obj/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/-c /usr/src/lib/lc/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c Bad system call - core dumped cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_divsi3 -o _divsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c Bad system call - core dumped cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_umodsi3 -o _umodsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c Bad system call - core dumped *** Error code 140 *** Error code 140 *** Error code 140 *** Error code 140 cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_modsi3 -o _modsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c Bad system call - core dumped *** Error code 140 5 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -------------------------------------------- and then it just dies......any ideas good people? ---------------------------------- E-Mail: William Woods Date: 13-Nov-99 Time: 00:24:24 FreeBSD 3.3 -Stable ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 0:30:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles538.castles.com [208.214.165.102]) by hub.freebsd.org (Postfix) with ESMTP id B178E14BEC; Sat, 13 Nov 1999 00:30:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00365; Sat, 13 Nov 1999 00:21:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911130821.AAA00365@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: wwoods@cybcon.com Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Re: Make World dies....... In-reply-to: Your message of "Sat, 13 Nov 1999 00:27:02 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Nov 1999 00:21:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did a cvsup today for -current to compile on my Alphastation 200 4/233 and > douring a make world, this is what I got: You currently have -stable on your box. You cannot do this. Install a recent -current snapshot and start from there. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Nov 13 0:32:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id A60B714C08 for ; Sat, 13 Nov 1999 00:32:33 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id AAA72714 for ; Sat, 13 Nov 1999 00:32:01 -0800 (PST) Date: Sat, 13 Nov 1999 00:32:01 -0800 (PST) From: Annelise Anderson To: freebsd-current@freebsd.org Subject: perl error in make world 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'm getting the following error with today's -current sources; this particular system has a rather strange history, so it may not be the sources, but something else. I have tried -DNOCRYPT, which doesn't help. And I've searched the archives without finding anything directly applicable, so suggestions would be appreciated. chmod 755 /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/usr/src/tmp/usr/include -o perl perlmain.o lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Final' /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Init' /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Update' *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 0:33:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 352D914C13; Sat, 13 Nov 1999 00:33:52 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3a-15.cybcon.com [205.147.75.144]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id AAA09329; Sat, 13 Nov 1999 00:33:40 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3.1 [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: <199911130821.AAA00365@dingo.cdrom.com> Date: Sat, 13 Nov 1999 00:32:04 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Mike Smith Subject: Re: Make World dies....... Cc: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shit, I will loose all my custom settings...no other way around this.... On 13-Nov-99 Mike Smith wrote: >> I did a cvsup today for -current to compile on my Alphastation 200 4/233 and >> douring a make world, this is what I got: > > You currently have -stable on your box. You cannot do this. Install a > recent -current snapshot and start from there. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com ---------------------------------- E-Mail: William Woods Date: 13-Nov-99 Time: 00:31:39 FreeBSD 3.3 -Stable ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 1:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id C3BBF14A25; Sat, 13 Nov 1999 01:30:39 -0800 (PST) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p23-max5.dun.ihug.co.nz [209.77.156.23]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA06477; Sat, 13 Nov 1999 22:30:24 +1300 Message-ID: <382D2FAC.8243ED99@es.co.nz> Date: Sat, 13 Nov 1999 22:30:20 +1300 From: Mike Muir X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: wwoods@cybcon.com Cc: Mike Smith , freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: Make World dies....... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > > Shit, I will loose all my custom settings...no other way around this.... Try compiling and installing the kernel first, reboot, buildworld.. should work (did for me but hey, im x86..) NO PROMISES! heh mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 3:12:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 3A2AC15113; Sat, 13 Nov 1999 03:12:36 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA60520; Sat, 13 Nov 1999 11:14:48 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 13 Nov 1999 11:14:48 +0000 (GMT) From: Doug Rabson To: Mike Muir Cc: wwoods@cybcon.com, Mike Smith , freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Make World dies....... In-Reply-To: <382D2FAC.8243ED99@es.co.nz> 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, 13 Nov 1999, Mike Muir wrote: > William Woods wrote: > > > > Shit, I will loose all my custom settings...no other way around this.... > > Try compiling and installing the kernel first, reboot, buildworld.. > should work (did for me but hey, im x86..) NO PROMISES! heh This should work (I have moved an alpha from -stable to -current with this). You should use mergemaster to update your /etc. -- 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 Sat Nov 13 3:12:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 608DD15126; Sat, 13 Nov 1999 03:12:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA60048; Sat, 13 Nov 1999 11:13:47 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 13 Nov 1999 11:13:47 +0000 (GMT) From: Doug Rabson To: Vladimir Kushnir Cc: Doug Rabson , cvs-all@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/sys/isa isa_common.c 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, 12 Nov 1999, Vladimir Kushnir wrote: > Sorry, but is there any driver for YMF724 except for OSS? If so (even in > some under-pre-alpha state) I'd be more than happy to test it. I've been working on a driver which would support the 'legacy' (i.e. soundblaster compatible) section of the chip. This would support playback but not record but its better than nothing. At this stage, I have it mostly working but no sound yet (probably a mixer problem). -- 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 Sat Nov 13 3:58:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 0052F14EEF; Sat, 13 Nov 1999 03:58:52 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id MAA10744952; Sat, 13 Nov 1999 12:58:46 +0100 (CET) Received: from work.net.local (maxtnt-033.telip.uni-sb.de [134.96.70.160]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id MAA23173; Sat, 13 Nov 1999 12:58:47 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id LAA00904; Sat, 13 Nov 1999 11:29:24 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911131029.LAA00904@work.net.local> Date: Sat, 13 Nov 1999 11:29:23 +0100 (CET) From: Alexander Leidinger Subject: i4b & security (Re: "man" reads /etc/rc.conf?) To: logix@foobar.franken.de Cc: freebsd-current@freebsd.org, isdn@freebsd.org, hm@hcs.de In-Reply-To: <19991111200547.A16123@foobar.franken.de> 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 On 11 Nov, Harold Gutch wrote: >> > Using command substitution in /etc/rc.conf{,.local} is NOT >> > officially supported. I think it should have always been >> > clear that there should _only_ be plain variable assignments. >> >> But with i4b you have to specify a username-password pair in rc.conf >> (spppconfig_isp0) and I didnīt want to show it to every user (rc.conf >> is u+rw,g+r,o+r for reasons you mention). > > What about /etc/start_if.isp0? Yes, with permissions of u+r,go-rwx itīs more secure than the currently recommended way. Hellmuth? Will this be the new official way of configuring i4b? Bye, Alexander. -- Intel: where Quality is job number 0.9998782345! http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 3:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 0C25015160 for ; Sat, 13 Nov 1999 03:59:12 -0800 (PST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id MAA10673723; Sat, 13 Nov 1999 12:58:55 +0100 (CET) Received: from work.net.local (maxtnt-033.telip.uni-sb.de [134.96.70.160]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id MAA23186; Sat, 13 Nov 1999 12:58:51 +0100 (CET) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id LAA00913; Sat, 13 Nov 1999 11:39:36 +0100 (CET) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199911131039.LAA00913@work.net.local> Date: Sat, 13 Nov 1999 11:39:35 +0100 (CET) From: Alexander Leidinger Subject: Re: "man" reads /etc/rc.conf? To: robert+freebsd@cyrus.watson.org Cc: robert@cyrus.watson.org, dcs@newsguy.com, current@freebsd.org In-Reply-To: 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 On 12 Nov, Robert Watson wrote: >> >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local >> >> >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" >> > ^^^ >> > Calling programs from any of the rc.conf files is considered evil >> > and it's looked down on. >> >> Itīs there to hide login/passwd information for i4b. > > But it seems like the end up as arguments to ifconfig at a later date, ^^ s/if/spp/ > where a user can pull them out of ps, /proc, etc. The window there > is clearly shorter than keeping it in /etc/rc.conf, but still not It will only be in /proc (ps, etc.) at execution-/boot-time or am I missing something? Bye, Alexander. -- Been there, done that, can't remember why... http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 4:47:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rp-plus.de (clubserv.rp-online.de [149.221.232.11]) by hub.freebsd.org (Postfix) with ESMTP id D5750150FE; Sat, 13 Nov 1999 04:47:19 -0800 (PST) (envelope-from alex@cichlids.com) Received: from neutron.cichlids.com (as8-pri43.rp-plus.de [149.221.239.171]) by mail.rp-plus.de (8.9.1a/8.9.1) with ESMTP id NAA13249; Sat, 13 Nov 1999 13:44:58 +0100 (MET) Received: from cichlids.cichlids.com (root@cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id NAA57389; Sat, 13 Nov 1999 13:40:16 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id NAA05268; Sat, 13 Nov 1999 13:40:21 +0100 (CET) (envelope-from alex) From: Alexander Langer Date: Sat, 13 Nov 1999 13:40:21 +0100 To: Alexander Leidinger Cc: logix@foobar.franken.de, freebsd-current@FreeBSD.ORG, isdn@FreeBSD.ORG, hm@hcs.de Subject: Re: i4b & security (Re: "man" reads /etc/rc.conf?) Message-ID: <19991113134021.A5188@cichlids.cichlids.com> Mail-Followup-To: Alexander Leidinger , logix@foobar.franken.de, freebsd-current@FreeBSD.ORG, isdn@FreeBSD.ORG, hm@hcs.de References: <19991111200547.A16123@foobar.franken.de> <199911131029.LAA00904@work.net.local> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <199911131029.LAA00904@work.net.local>; from A.Leidinger@WJPServer.CS.Uni-SB.de on Sat, Nov 13, 1999 at 11:29:23AM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also sprach Alexander Leidinger (A.Leidinger@WJPServer.CS.Uni-SB.de): > > What about /etc/start_if.isp0? > Yes, with permissions of u+r,go-rwx itīs more secure than the currently > recommended way. > Hellmuth? Will this be the new official way of configuring i4b? A second advantage: You can sh /etc/start_if.isp0 while the machine is running for changing username/pass. I sometimes do this when using a call-by-call ISP and currently I run spppcontrol by hand. With a script you could add some automatic stuff. I can think of other advantages that go in the same direction. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 8:50:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5B19E14D82 for ; Sat, 13 Nov 1999 08:50:31 -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.9.3/8.9.3) with SMTP id LAA01323; Sat, 13 Nov 1999 11:50:26 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 13 Nov 1999 11:50:26 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Alexander Leidinger Cc: dcs@newsguy.com, current@freebsd.org Subject: Re: "man" reads /etc/rc.conf? In-Reply-To: <199911131039.LAA00913@work.net.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Nov 1999, Alexander Leidinger wrote: > On 12 Nov, Robert Watson wrote: >=20 > >> >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > >> >> >> spppconfig_isp0=3D"`cat /etc/isdn/connect.parameters`" > >> > ^^^ > >> > Calling programs from any of the rc.conf files is considered evil > >> > and it's looked down on. > >> > >> It=B4s there to hide login/passwd information for i4b. > >=20 > > But it seems like the end up as arguments to ifconfig at a later date, > ^^ s/if/spp/ > =20 > > where a user can pull them out of ps, /proc, etc. The window there > > is clearly shorter than keeping it in /etc/rc.conf, but still not >=20 > It will only be in /proc (ps, etc.) at execution-/boot-time or am I > missing something? Yes -- the window of exposure is while a program is running that either a) has the password as a command line argument, or b) has the variable as an environmental variable. Opportunities for using ps to pull this information out happen after the sppp* portion of rc.network, but begin as early as sendmail (.forward and deferred delivery), cron (crontab), httpd (cgi), etc. And it's important to keep in mind that every time rc.conf is executed, it will pull in the password using the `...` clause, and store it in the execution environment of the caller. Not the same as being in the exposed environmental variables, but it's more exposure in the sense that if the program coredumps (i.e., the sh running the script that invoked /etc/rc.conf) the contents will be in the dump. Later invocations of spppcontrol in userland will expose their arguments to the world also. The generally preferred way to pass in passwords to a program is either to provide the program with an argument that is the filename storing the password, or to pass it in via stdin. E.g.,=20 % program -p /etc/private/my_password % cat /etc/private/my_password | program -p -=20 Robert N M Watson=20 robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 9:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 7144614D82; Sat, 13 Nov 1999 09:24:11 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2008 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 13 Nov 1999 18:24:10 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id E919738E2; Sat, 13 Nov 1999 18:24:09 +0100 (MET) Subject: Re: i4b & security (Re: "man" reads /etc/rc.conf?) In-Reply-To: <199911131029.LAA00904@work.net.local> from Alexander Leidinger at "Nov 13, 99 11:29:23 am" To: A.Leidinger@WJPServer.CS.Uni-SB.de (Alexander Leidinger) Date: Sat, 13 Nov 1999 18:24:09 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG, isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1050 Message-Id: <19991113172409.E919738E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Alexander Leidinger: > >> But with i4b you have to specify a username-password pair in rc.conf > >> (spppconfig_isp0) and I didn_t want to show it to every user (rc.conf > >> is u+rw,g+r,o+r for reasons you mention). > > > > What about /etc/start_if.isp0? > > Yes, with permissions of u+r,go-rwx it_s more secure than the currently > recommended way. > > Hellmuth? Will this be the new official way of configuring i4b? I'm not at all satisfied with the way password arguments to spppcontrol work currently. But before we get to security issues of spppcontrol, i think the sppp issues in i4b (lcp-echo, lcp-loops) have to be resolved (besides other much more basic things such as the hardware drivers). hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 11:34: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id 1D3C914BD3 for ; Sat, 13 Nov 1999 11:33:58 -0800 (PST) (envelope-from plm@smtp7.xs4all.nl) Received: from localhost. (s340-isdn558.dial.xs4all.nl [194.109.182.46]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA11103 for ; Sat, 13 Nov 1999 20:33:55 +0100 (CET) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id UAA00410; Sat, 13 Nov 1999 20:33:55 +0100 (MET) (envelope-from plm) To: freebsd-current@freebsd.org Subject: Re: egcs unstable References: <87n1si2nu8.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 13 Nov 1999 20:33:54 +0100 In-Reply-To: Marcel Moolenaar's message of "Fri, 12 Nov 1999 10:14:36 +0100" Message-ID: <873duaw5i5.fsf@muon.xs4all.nl> Lines: 23 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "MM" == Marcel Moolenaar writes: MM> After (by accident) compiling world (excluding kernel) with MM> optimization disabled (ie -O0) and installing the resulting MM> binaries, xemacs (21.1.7) coredumps with a bus error. I MM> recompiled and reinstalled xemacs and all was fine. Now, after MM> building and installing world (excluding kernel again) with MM> optimization (ie -O), xemacs does exactly the same: core dumps MM> on bus error. I'll recompile xemacs again and expect it to be MM> solved, but something is definitely broken: xemacs should not MM> core dump after recompiling world with only a simple change in MM> compiler flags. Are you sure this isn't a problem with xemacs itself? Reading the xemacs group, I read about crashes all the time on various platforms. It is getting worse with newer versions (the 19.x versions were pretty stable). Anyway I stick to good old GNU emacs (I can do without inline images for the time being) which is rock solid, also after -current 'make world's. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know peter@mutsaers.com | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 12:25:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id DEAE114A21 for ; Sat, 13 Nov 1999 12:25:45 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id VAA03700 for current@FreeBSD.org; Sat, 13 Nov 1999 21:00:48 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 13 Nov 1999 21:00:46 +0100 From: Marcel Moolenaar Message-ID: <382DC36E.B33958FA@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <87n1si2nu8.fsf@totally-fudged-out-message-id>, <873duaw5i5.fsf@muon.xs4all.nl> Subject: Re: egcs unstable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Mutsaers wrote: > > >> "MM" == Marcel Moolenaar writes: > > MM> After (by accident) compiling world (excluding kernel) with > MM> optimization disabled (ie -O0) and installing the resulting > MM> binaries, xemacs (21.1.7) coredumps with a bus error. I > MM> recompiled and reinstalled xemacs and all was fine. Now, after > MM> building and installing world (excluding kernel again) with > MM> optimization (ie -O), xemacs does exactly the same: core dumps > MM> on bus error. I'll recompile xemacs again and expect it to be > MM> solved, but something is definitely broken: xemacs should not > MM> core dump after recompiling world with only a simple change in > MM> compiler flags. > > Are you sure this isn't a problem with xemacs itself? Reading the > xemacs group, I read about crashes all the time on various > platforms. It is getting worse with newer versions (the 19.x versions > were pretty stable). Anyway I stick to good old GNU emacs (I can do > without inline images for the time being) which is rock solid, also > after -current 'make world's. Very possible. I don't seem to get xemacs21 on Alpha working at the moment (yes I know the port doesn't support it yet, but that's what I'm fixing :-) It coredumps in xpm. BTW: I also don't need inline images, but I find xemacs more appealing in an X env. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Nov 13 13: 3:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id EAE1614F51; Sat, 13 Nov 1999 13:03:06 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.233]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FL5006CVMG06A@mta1.snfc21.pbi.net>; Sat, 13 Nov 1999 13:02:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id C04EC91684; Sat, 13 Nov 1999 13:02:23 -0800 (PST) Date: Sat, 13 Nov 1999 13:02:23 -0800 (PST) From: Alex Zepeda Subject: Re: cvs commit: src/sys/isa isa_common.c In-reply-to: To: Doug Rabson Cc: Vladimir Kushnir , Doug Rabson , cvs-all@FreeBSD.ORG, current@FreeBSD.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 Sat, 13 Nov 1999, Doug Rabson wrote: > On Fri, 12 Nov 1999, Vladimir Kushnir wrote: > > > Sorry, but is there any driver for YMF724 except for OSS? If so (even in > > some under-pre-alpha state) I'd be more than happy to test it. > > I've been working on a driver which would support the 'legacy' (i.e. > soundblaster compatible) section of the chip. This would support playback > but not record but its better than nothing. At this stage, I have it > mostly working but no sound yet (probably a mixer problem). Really? Cool! I've tried the same thing, and through a series of ugly hacks, got the SB Pro bits to probe and attach correctly (and if you set the SBPro version to 3.x or whatever the latest version is, you get a mixer device). Sadly I couldn't get any sound out of it (mpg123 set to 8bit mode..). Although, I'm not too sure how useful 8bit sound would really be. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 13: 5:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 4188414D1C for ; Sat, 13 Nov 1999 13:05:16 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.233]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FL50043ZMKLDZ@mta3.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 13 Nov 1999 13:05:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 66BE391684; Sat, 13 Nov 1999 13:05:09 -0800 (PST) Date: Sat, 13 Nov 1999 13:05:09 -0800 (PST) From: Alex Zepeda Subject: Re: pnp and AWE64 In-reply-to: <4.2.0.58.19991112191106.0161a680@mail.sstar.com> To: Jim King Cc: freebsd-current@FreeBSD.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 > Attached, in all it's glory. > > The relevant lines seem to be: > controller pnp0 > device pcm0 > options PNPBIOS > > The PNPBIOS line doesn't make a difference for the AWE64 (although it does > make some difference - all the motherboard resources show up as unknowns > with it enabled). Yup, PNPBIOS shows all the mobo devices. I've gotten it to attach to my two serial ports this way (as opposed to actually probing for them) :^) What does pnpinfo show? I've actually got my pcm line set to: device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 Which is rather incorrect. Hmm. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 13:47:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from kar.net (sunone.kar.net [195.178.131.131]) by hub.freebsd.org (Postfix) with ESMTP id 51FA714BF6 for ; Sat, 13 Nov 1999 13:47:01 -0800 (PST) (envelope-from volodya@mail.kar.net) Received: from kushnir1.kiev.ua by kar.net with ESMTP id XAA18640; (8.8.7/2.b2) Sat, 13 Nov 1999 23:28:33 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.9.3/8.9.3) with ESMTP id XAA00802; Sat, 13 Nov 1999 23:27:43 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Sat, 13 Nov 1999 23:26:23 +0200 (EET) From: Vladimir Kushnir To: Alex Zepeda Cc: Doug Rabson , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c 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 Sat, 13 Nov 1999, Alex Zepeda wrote: > On Sat, 13 Nov 1999, Doug Rabson wrote: > > > On Fri, 12 Nov 1999, Vladimir Kushnir wrote: > > > > > Sorry, but is there any driver for YMF724 except for OSS? If so (even in > > > some under-pre-alpha state) I'd be more than happy to test it. > > > > I've been working on a driver which would support the 'legacy' (i.e. > > soundblaster compatible) section of the chip. This would support playback > > but not record but its better than nothing. At this stage, I have it > > mostly working but no sound yet (probably a mixer problem). > > Really? Cool! > > I've tried the same thing, and through a series of ugly hacks, got the SB > Pro bits to probe and attach correctly (and if you set the SBPro version > to 3.x or whatever the latest version is, you get a mixer device). Sadly > I couldn't get any sound out of it (mpg123 set to 8bit mode..). > Although, I'm not too sure how useful 8bit sound would really be. > > - alex > Better than nothing, wouldn't it? Could I help with it somehow? (With my, unfortunately, practically nonexistent programmer's skill but with a huuuuge willingness to test anything to make my card sound :-) -- ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 13:51:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id E0F4A14BE6 for ; Sat, 13 Nov 1999 13:51:54 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 5357200; Sat, 13 Nov 1999 15:51:51 -0600 Message-Id: <4.2.0.58.19991113155109.01622610@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 13 Nov 1999 15:51:52 -0600 To: Alex Zepeda From: Jim King Subject: Re: pnp and AWE64 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19991112191106.0161a680@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:05 PM 11/13/1999 -0800, Alex Zepeda wrote: > > Attached, in all it's glory. > > > > The relevant lines seem to be: > > controller pnp0 > > device pcm0 > > options PNPBIOS > > > > The PNPBIOS line doesn't make a difference for the AWE64 (although it does > > make some difference - all the motherboard resources show up as unknowns > > with it enabled). > >Yup, PNPBIOS shows all the mobo devices. I've gotten it to attach to my >two serial ports this way (as opposed to actually probing for them) :^) > >What does pnpinfo show? pnpinfo shows a bunch of information about my USR PnP modem, but nothing at all about the AWE64 (or anything else). >I've actually got my pcm line set to: > >device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 > >Which is rather incorrect. Hmm. > >- alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 15:28:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 276B914BE4 for ; Sat, 13 Nov 1999 15:28:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA78104 for ; Sat, 13 Nov 1999 15:28:38 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA16684 for current@freebsd.org; Sat, 13 Nov 1999 15:28:38 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Nov 1999 15:28:38 -0800 From: "David O'Brien" To: current@freebsd.org Subject: A call to squease more bytes from `boot2' Message-ID: <19991113152838.A16659@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.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 Hi folks, Once again, `boot2' is the only thing holding us back from upgrading our base compiler. The commit below plus -fdata-sections gets us to needing to reduce another 100 bytes from `boot2'. This is an appeal to hackers to squeeze another 100 bytes out. It would be preferable to use the ``egcs'' port as the compiler, but I presume using the current system compiler would be OK too. ----- Forwarded message from "David E. O'Brien" ----- Subject: cvs commit: src/sys/boot/i386/boot2 Makefile Modified files: sys/boot/i386/boot2 Makefile Log: Turn on the -fforce-addr and -fschedule-insns optimizations. Adding ----- End forwarded message ----- -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 16:23:44 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0CA0914BDC; Sat, 13 Nov 1999 16:23:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D31D51CD438; Sat, 13 Nov 1999 16:23:42 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 13 Nov 1999 16:23:42 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: current@freebsd.org Subject: Re: A call to squease more bytes from `boot2' In-Reply-To: <19991113152838.A16659@dragon.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, 13 Nov 1999, David O'Brien wrote: > This is an appeal to hackers to squeeze another 100 bytes out. It would > be preferable to use the ``egcs'' port as the compiler, but I presume > using the current system compiler would be OK too. Do you have any idea why the new compiler is generating so much more code than the old? Have any new optimizations been activated by default which could just be deactivated? Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 16:49:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7B13514EF8; Sat, 13 Nov 1999 16:49:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA78281; Sat, 13 Nov 1999 16:49:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA17772; Sat, 13 Nov 1999 16:49:39 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Nov 1999 16:49:39 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@freebsd.org Subject: Re: A call to squease more bytes from `boot2' Message-ID: <19991113164939.F90421@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991113152838.A16659@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Sat, Nov 13, 1999 at 04:23:42PM -0800 X-Operating-System: FreeBSD 4.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, Nov 13, 1999 at 04:23:42PM -0800, Kris Kennaway wrote: > Do you have any idea why the new compiler is generating so much more code > than the old? Nope. I can post the "-S" output if you like. But the EGCS vs. GCC versions are quite different. There were many changes to the back end between the EGCS 1.1 and GCC 2.95 branches. > Have any new optimizations been activated by default which could just > be deactivated? I've added a few optimizations to CFLAGS and that helped some, but not enough. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 16:54:34 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 693BF14EF8; Sat, 13 Nov 1999 16:54:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 568D31CD43B; Sat, 13 Nov 1999 16:54:33 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 13 Nov 1999 16:54:33 -0800 (PST) From: Kris Kennaway To: Annelise Anderson Cc: freebsd-current@freebsd.org Subject: Re: perl error in make world 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 Sat, 13 Nov 1999, Annelise Anderson wrote: > I'm getting the following error with today's -current sources; > this particular system has a rather strange history, so it may > not be the sources, but something else. I have tried -DNOCRYPT, > which doesn't help. And I've searched the archives without > finding anything directly applicable, so suggestions would be > appreciated. Back in september libcrypt grew the ability to use SHA-1 passwords..looks like your libcrypt wasn't linked against libmd, so the SHA_* symbols aren't found in libcrypt. Adding -lmd to the perl link line would fix it, but you should try rebuilding libcrypt first. Doing a "nm /usr/lib/libcrypt.so.2" should show the symbols with a 'T' next to them. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 16:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 644F914EF8; Sat, 13 Nov 1999 16:57:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5539A1CD43B; Sat, 13 Nov 1999 16:57:36 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 13 Nov 1999 16:57:36 -0800 (PST) From: Kris Kennaway To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: A call to squease more bytes from `boot2' In-Reply-To: <19991113164939.F90421@dragon.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, 13 Nov 1999, David O'Brien wrote: > On Sat, Nov 13, 1999 at 04:23:42PM -0800, Kris Kennaway wrote: > > Do you have any idea why the new compiler is generating so much more code > > than the old? > > Nope. I can post the "-S" output if you like. But the EGCS vs. GCC > versions are quite different. There were many changes to the back end > between the EGCS 1.1 and GCC 2.95 branches. Hmm, if they bloated the compiler output without giving the ability to conditionally de-bloat then it indeed sucks. Good luck :( Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 19:23:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 3553C15241 for ; Sat, 13 Nov 1999 19:23:08 -0800 (PST) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.8.8/8.8.8) id WAA24095; Sat, 13 Nov 1999 22:23:04 -0500 (EST) Date: Sat, 13 Nov 1999 22:23:04 -0500 From: Mathew Kanner To: Jim King Cc: Alex Zepeda , freebsd-current@FreeBSD.ORG Subject: Re: pnp and AWE64 Message-ID: <19991113222304.A22008@cs.mcgill.ca> References: <4.2.0.58.19991112191106.0161a680@mail.sstar.com> <4.2.0.58.19991113155109.01622610@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: Jim King's message [Re: pnp and AWE64] as of Sat, Nov 13, 1999 at 03:51:52PM -0600 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 13, Jim King wrote: > At 01:05 PM 11/13/1999 -0800, Alex Zepeda wrote: > >What does pnpinfo show? > > pnpinfo shows a bunch of information about my USR PnP modem, but nothing at > all about the AWE64 (or anything else). > Sorry to jump in. I once difficulties with PnP that felt similiar. I had a working sound card and when I stuck in an ISA PnP ethernet card, the sound card disapeared. I fixed it by hacking the for loop in pnp_identify in isa/pnp.c. When the loop went backwards, I could detect both devices. -Mat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 19:46:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 77BB9152B2 for ; Sat, 13 Nov 1999 19:46:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA78753 for ; Sat, 13 Nov 1999 19:46:32 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA70581 for current@freebsd.org; Sat, 13 Nov 1999 19:46:31 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Nov 1999 19:46:31 -0800 From: "David O'Brien" To: current@freebsd.org Subject: **HEADS UP** probable switch to Gcc 2.95.2 THIS weekend Message-ID: <19991113194631.A68677@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.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 is just a "heads up" message, that the switch from EGCS 1.1.2 to GCC 2.95.2 will probably occur this weekend. I can now `make world' and build a GENERIC kernel fine with GCC 2.95.2. All I have left to do is clean up some stuff and arrange some stuff. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 20:50: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id DFC8714CFF for ; Sat, 13 Nov 1999 20:49:59 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa16-54.ix.netcom.com [207.93.148.182]) by smtp10.atl.mindspring.net (8.8.5/8.8.5) with ESMTP id XAA10319 for ; Sat, 13 Nov 1999 23:49:49 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id UAA21037; Sat, 13 Nov 1999 20:49:46 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Sat, 13 Nov 1999 20:49:46 -0800 (PST) Message-Id: <199911140449.UAA21037@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: <19991113194631.A68677@dragon.nuxi.com> (obrien@FreeBSD.ORG) Subject: Re: **HEADS UP** probable switch to Gcc 2.95.2 THIS weekend References: <19991113194631.A68677@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I missed something, I think. # gcc --version egcs-2.91.66 What is the relationship? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 21:20:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 966F014A18 for ; Sat, 13 Nov 1999 21:20:53 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 5464200; Sat, 13 Nov 1999 23:20:45 -0600 Message-Id: <4.2.0.58.19991113231829.01620f30@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 13 Nov 1999 23:20:46 -0600 To: Mathew Kanner From: Jim King Subject: Re: pnp and AWE64 Cc: Alex Zepeda , freebsd-current@FreeBSD.ORG In-Reply-To: <19991113222304.A22008@cs.mcgill.ca> References: <4.2.0.58.19991112191106.0161a680@mail.sstar.com> <4.2.0.58.19991113155109.01622610@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:23 PM 11/13/1999 -0500, Mathew Kanner wrote: >On Nov 13, Jim King wrote: > > At 01:05 PM 11/13/1999 -0800, Alex Zepeda wrote: > > >What does pnpinfo show? > > > > pnpinfo shows a bunch of information about my USR PnP modem, but > nothing at > > all about the AWE64 (or anything else). > > > > Sorry to jump in. I once difficulties with PnP that felt >similiar. I had a working sound card and when I stuck in an ISA PnP >ethernet card, the sound card disapeared. > I fixed it by hacking the for loop in pnp_identify in >isa/pnp.c. When the loop went backwards, I could detect both devices. That does it. When running the loop forward only the ISA PnP modem is found; after hacking it to run the loop backwards the AWE64 *and* the modem are both found. Thanks! Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 23: 8:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id D59F414C83 for ; Sat, 13 Nov 1999 23:08:26 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id CAA21689; Sun, 14 Nov 1999 02:15:31 -0500 (EST) Date: Sun, 14 Nov 1999 02:15:31 -0500 (EST) From: Ben Rosengart Reply-To: chat@FreeBSD.ORG To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: egcs unstable In-Reply-To: <382DC36E.B33958FA@scc.nl> 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, 13 Nov 1999, Marcel Moolenaar wrote: > BTW: I also don't need inline images, but I find xemacs more appealing > in an X env. Funny ... I only find xemacs useful when *not* using X, because that's where xemacs will do syntax coloring and emacs won't. Followups redirected to -chat. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 23:51: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CBC811526D; Sat, 13 Nov 1999 23:50:54 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA08142; Sun, 14 Nov 1999 16:50:51 +0900 (JST) Message-ID: <382E6951.DCD1973C@newsguy.com> Date: Sun, 14 Nov 1999 16:48:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: A call to squease more bytes from `boot2' References: <19991113152838.A16659@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Once again, `boot2' is the only thing holding us back from upgrading our > base compiler. The commit below plus -fdata-sections gets us to needing > to reduce another 100 bytes from `boot2'. > > This is an appeal to hackers to squeeze another 100 bytes out. It would > be preferable to use the ``egcs'' port as the compiler, but I presume > using the current system compiler would be OK too. I'd rather find out _why_ the new compiler generates a bigger object. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 13 23:55:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7FEC514CE3 for ; Sat, 13 Nov 1999 23:55:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA79329; Sat, 13 Nov 1999 23:55:37 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA72399; Sat, 13 Nov 1999 23:55:35 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Nov 1999 23:55:35 -0800 From: "David O'Brien" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: A call to squease more bytes from `boot2' Message-ID: <19991113235535.M90421@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991113152838.A16659@dragon.nuxi.com> <382E6951.DCD1973C@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <382E6951.DCD1973C@newsguy.com>; from dcs@newsguy.com on Sun, Nov 14, 1999 at 04:48:33PM +0900 X-Operating-System: FreeBSD 4.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 Sun, Nov 14, 1999 at 04:48:33PM +0900, Daniel C. Sobral wrote: > I'd rather find out _why_ the new compiler generates a bigger > object. Be my guest, but I don't have time for it. Gcc 2.95.2 has as many backend changes as we have kernel changes from 3.x to 4.0. Thus it is no surprise that the generated code is different. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message