From owner-freebsd-current Sun Apr 15 8:21:33 2001 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 B6ACC37B449 for ; Sun, 15 Apr 2001 08:21:20 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 2C9B95D74; Sun, 15 Apr 2001 17:21:42 +0200 (CEST) Date: Sun, 15 Apr 2001 17:21:42 +0200 From: Jesper Skriver To: current@FreeBSD.org Subject: kernel panic in -current, ithread or newcard related ? Message-ID: <20010415172142.A27168@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About every other time I boot my IBM ThinkPad 600E I get this panic (hand typed, as I don't have a second machine here to be able to use a serial console). Fatal trap 12: page fault while in kernel mode Fault virtual address = 0x28 Fault code = supervisor read, page not present instruction pointer = 0x8:0xc0159bd3 stack pointer = 0x10:0xc5e3ef44 frame pointer = 0x10:0xc5e3ef48 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def21 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 16 (irq11: pccbb0+++) kernel: type 12 trap, code=0 Stopped at csa_readio+0x17: movl 0x28(%eax),%edx db> trace csa_readio(c0d0c804,0,c0d0c700,c0d1f400,4) at csa_readio+0x17 csa_intr(c0d0c800) at csa_intr+0x14 ithread_loop(c0d1f400,c5e3efa0) at ithread_loop+0x23f fork_exit(c018dd20,c0d1f400,c4e2efa8) at fork_exit+0x59 fork_trampoline() at fork_trampoline+0x8 When I see this, I just power it off, and boot again, and usually it will boot. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Apr 14 20:43:36 CEST 2001 root@tam:/usr/obj/usr/src/sys/TAM2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (363.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 66912256 (65344K bytes) config> q avail memory = 61186048 (59752K bytes) Preloaded elf kernel "kernel" at 0xc03dd000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03dd09c. Preloaded elf module "random.ko" at 0xc03dd0ec. Pentium Pro MTRR support enabled Using $PIR table, 5 entries at 0xc00f9e20 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) pccbb0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 cardbus0: on pccbb0 pccbb0: WARNING: cannot attach pccard bus. pccbb1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 cardbus1: on pccbb1 pccbb1: WARNING: cannot attach pccard bus. csa0: mem 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 pcm0: on csa0 pcm0: ac97 codec invalid or not present (id == 0) device_probe_and_attach: pcm0 attach returned 6 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x8400-0x841f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold pmtimer0 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pcm1: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources BRIDGE 010131, have 2 interfaces ad0: 6149MB [13328/15/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a cardbus0: Detaching card: no cards to detach! pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb1: card inserted: event=0x00000000, state=30000920 pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb1: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: 01015752 TUPLE: CONFIG_CB [6]: 03 01 00 00 00 00 TUPLE: CFTABLE_ENTRY_CB [13]: 41 9a 01 b5 1e 01 b5 1e 02 30 ff ff 01 cardbus1: Opening BAR: type=IO, bar=10, len=0040 Product version: 5.0 Product name: 3Com Corporation | 3CCFE575CT | LAN Cardbus Card | 004 | Functions: Network Adaptor, Memory CIS reading done xl0: <3Com 3c575C Fast Etherlink XL> port 0x3000-0x307f mem 0x44020000-0x4403ffff,0x44000080-0x440000ff,0x44000000-0x4400007f irq 11 at device 0.0 on cardbus1 xl0: chip is in D6 power mode -- setting to D0 xl0: Ethernet address: 00:00:86:5b:75:a0 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto BRIDGE 010131, have 3 interfaces -- index 3 type 6 phy 0 addrl 6 addr 00.00.86.5b.75.a0 /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) 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 Sun Apr 15 13: 1:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 79C2D37B43F for ; Sun, 15 Apr 2001 13:01:42 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3FK1bE71555; Sun, 15 Apr 2001 13:01:37 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Apr 2001 13:01:37 -0700 (PDT) From: Matt Dillon Message-Id: <200104152001.f3FK1bE71555@earth.backplane.com> To: Doug Barton Cc: "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104101103.f3AB36P49523@hak.lan.Awfulhak.org> <200104101824.f3AIOZ389340@earth.backplane.com> <3AD90956.998BE3E7@DougBarton.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : I notice that this option is off by default. Can you give a general idea :of when it should be enabled, when it should be disabled, and what bad :things might result with it on? : :Thanks, : :Doug There's no downside, really. The directory cache is so tiny without it that you can't lose. Even the wasteage from caching small directories becomes irrelevant -- for several reasons. First, wasting a little bit of ram is worth it if it saves a disk seek. It saves lots of disk seeks. Second, people forget that the namei cache is the first line of defense for the system, not the directory block cache. Most programmatic small directory accesses directly reference specific files rather then scan the directory. Human-based accesses often scan the directory (do an 'ls'), but the memory footprint for a human is huge in comparison to a single page of directory cache. Scanning whole filesystems with 'find' tend to not be cacheable anyway, and since the cache pages get recycled you don't actually waste any more ram for that case either. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 14:45:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from apicra.wanadoo.fr (smtp-rt-3.wanadoo.fr [193.252.19.155]) by hub.freebsd.org (Postfix) with ESMTP id 7B85F37B446 for ; Sun, 15 Apr 2001 14:45:56 -0700 (PDT) (envelope-from jb.joule@wanadoo.fr) Received: from antholoma.wanadoo.fr (193.252.19.153) by apicra.wanadoo.fr; 15 Apr 2001 23:45:52 +0200 Received: from thingy (193.252.181.65) by antholoma.wanadoo.fr; 15 Apr 2001 23:45:40 +0200 From: "jb.joule" To: Subject: join Date: Sun, 15 Apr 2001 23:46:27 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG join To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 17:43:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3F80D37B423 for ; Sun, 15 Apr 2001 17:43:25 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f3G0hPM17529 for ; Sun, 15 Apr 2001 17:43:25 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D6F7D3811; Sun, 15 Apr 2001 17:43:24 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Justin T. Gibbs" Cc: Doug Barton , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <200104150505.f3F55ts00973@aslan.scsiguy.com> Date: Sun, 15 Apr 2001 17:43:24 -0700 From: Peter Wemm Message-Id: <20010416004324.D6F7D3811@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > > I notice that this option is off by default. Can you give a general > >idea of when it should be enabled, when it should be disabled, and what bad > >things might result with it on? > > It consumes a full page per-directory even though the majority of > directories in a stock system are a small fraction of that size. It is my understanding that with the new directory layout strategies, this will be improved somewhat. ie: a single page is much more likely to cache up to 8 directories. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 18: 5:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id B2A7E37B42C for ; Sun, 15 Apr 2001 18:05:27 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3G15M880234 for ; Mon, 16 Apr 2001 10:05:25 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 18 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED) Date: Mon, 16 Apr 2001 10:05:03 +0900 Message-Id: <20010416100503U.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a small typo in src/release/Makefile rev 1.161; not 'kernel', but 'KERNEL' is correct. -- - Makoto `MAR' MATSUSHITA --- Makefile.dist Mon Apr 16 10:02:01 2001 +++ Makefile Mon Apr 16 10:02:52 2001 @@ -847,7 +847,7 @@ make KERNEL=${KERNEL} DESTDIR=${RD}/kernels install && \ [ -r ${.CURDIR}/../sys/${MACHINE}/conf/${KERNEL}.hints ] && \ cp ${.CURDIR}/../sys/${MACHINE}/conf/${KERNEL}.hints ${RD}/kernels - make KERNEL=${kernel} DESTDIR=${RD}/kernels kernel-reinstall.debug + make KERNEL=${KERNEL} DESTDIR=${RD}/kernels kernel-reinstall.debug # # --==## Put a filesystem into a BOOTMFS kernel ##==-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 18:23:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 3905837B43F for ; Sun, 15 Apr 2001 18:23:31 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3G1NUU72793; Sun, 15 Apr 2001 18:23:30 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Apr 2001 18:23:30 -0700 (PDT) From: Matt Dillon Message-Id: <200104160123.f3G1NUU72793@earth.backplane.com> To: Peter Wemm Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <20010416004324.D6F7D3811@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It is my understanding that with the new directory layout strategies, this :will be improved somewhat. ie: a single page is much more likely to cache :up to 8 directories. : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au :"All of this is for nothing if we don't go to the stars" - JMS/B5 Only in the drive's own cache. Our VM Page cache is object-oriented, meaning that even though directories may be packed in the filesystem, they will not be packed in the buffer cache / VM Page cache. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 19:59:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 0BE6137B423 for ; Sun, 15 Apr 2001 19:59:57 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3G2xqs06321; Sun, 15 Apr 2001 20:59:53 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104160259.f3G2xqs06321@aslan.scsiguy.com> To: Matt Dillon Cc: Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: Your message of "Sun, 15 Apr 2001 13:01:37 PDT." <200104152001.f3FK1bE71555@earth.backplane.com> Date: Sun, 15 Apr 2001 20:59:52 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's no downside, really. It just seems inelegant to have a system that, on paper, is so inefficient. Can't we do better? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 21:27:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 2A9B537B43E for ; Sun, 15 Apr 2001 21:27:41 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3G4Rb884575 for ; Mon, 16 Apr 2001 13:27:38 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 49 From: Makoto MATSUSHITA To: current@freeBSD.org Subject: Failed using CD-ROM as root filesystem Date: Mon, 16 Apr 2001 13:27:24 +0900 Message-Id: <20010416132724H.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to use (bootable) CD-ROM as root filesystem (I want have this because it's good alternative of fixit.flp), but it seems that GENERIC kernel doesn't understand where is root filesystem. What I did are: - make a 2.88MB boot floppy image, which contains: * GENERIC kernel (gzipped) * loader(8) * configulation files for loader: device hints & 'set boot_cdrom' - make an ISO image with, which contains: * floppy image (mentioned above) for boot * extracted distributions - Burn an ISO image to a CD - Boot... * loader(8) works well; initializing is OK, and kicks kernel.gz * kernel works well until all devices are attached * kernel stops when mounting root filesystem, dmesg says: .... acd0: CDROM <....> at ata0-slave PIO4 Mounting root from cd9660:cd0a setrootbyname failed iso_mountroot: can't find rootvp Root mount failed: 6 Mounting root from cd9660:acd0a setrootbyname failed iso_mountroot: can't find rootvp Root mount failed: 6 Mounting root from cd9660:wcd0a setrootbyname failed iso_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual imput mountroot> It seems that something goes wrong in setrootbyname(). Any clues? P.S.: I've also tried with 4-stable kernel, and it goes pretty well. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 22:26:38 2001 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 6E63037B423; Sun, 15 Apr 2001 22:26:37 -0700 (PDT) Date: Sun, 15 Apr 2001 22:26:37 -0700 From: "John W. De Boskey" To: Current List Subject: FIO* doc added to tty.4 (review) Message-ID: <20010415222637.A507@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been doing some tty related work and found the FIO* requests don't seem to be documented. I've added some reasonable doc to tty.4 and put up the the diff and html forms: http://people.freebsd.org/~jwd/doc/tty.4.html http://people.freebsd.org/~jwd/doc/tty.4.diff Any comments are welcome. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 15 23:16:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9A57F37B423 for ; Sun, 15 Apr 2001 23:16:21 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3G6GI973782; Sun, 15 Apr 2001 23:16:18 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Apr 2001 23:16:18 -0700 (PDT) From: Matt Dillon Message-Id: <200104160616.f3G6GI973782@earth.backplane.com> To: "Justin T. Gibbs" Cc: Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> There's no downside, really. : :It just seems inelegant to have a system that, on paper, is :so inefficient. Can't we do better? : :-- :Justin I don't consider it inefficient. Sure, if you look at this one aspect of the caching taken out of context it may appear to be inefficient, but if you look at the whole enchilada the memory issue is nothing more then a minor footnote - not worth the effort of worrying about. It's far more important to cache the right things then it is to be memory-efficient. If you think about it, a 'memory inefficient' cache is an oxymoron -- the cache isn't actually taking memory away from anyone else, so the worst effect that you will see is, say, 60MB of cache acting as if it were 55MB of cache. A difference like that is nothing compared to choosing the right things to cache in the first place. An even greater issue.. greater then everything else put together, is the fact that our current VFS/BIO subsystem is far too complex. A staggering number of bugs have been found and fixed, and there are probably still more yet to be found in the original code. If I could trade all of those bugs for a slightly less memory efficient subsystem I would do it in a heartbeep :-) Efficiency is no good if the subsystem isn't reliable. Far too much attention is being paid to making things fast and (theoretically) efficient and far too little is being paid to reliability these days. For example, all this work on a preemptive kernel is just insane. Our entire kernel is built on the concept of not being preemptable except by interrupts. We virtually guarentee years of instability and bugs leaking out of the woodwork by trying to make it preemptable, and the performance gain we get for that pain is going to be zilch. Nada. Nothing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 0:20:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 5935C37B43C for ; Mon, 16 Apr 2001 00:20:50 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f3G7KSM59665; Mon, 16 Apr 2001 00:20:28 -0700 (PDT) (envelope-from obrien) Date: Mon, 16 Apr 2001 00:19:07 -0700 From: "David O'Brien" To: Makoto MATSUSHITA Cc: current@freebsd.org Subject: Re: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED) Message-ID: <20010416001907.A59585@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010416100503U.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010416100503U.matusita@jp.FreeBSD.org>; from matusita@jp.FreeBSD.org on Mon, Apr 16, 2001 at 10:05:03AM +0900 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 10:05:03AM +0900, Makoto MATSUSHITA wrote: > There is a small typo in src/release/Makefile rev 1.161; not 'kernel', > but 'KERNEL' is correct. I think I got all these already. But I rev 1.161 is from back in 1995. Are you sure you've got the right /usr/src/release/Makefile? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 0:23:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id C6E1D37B42C for ; Mon, 16 Apr 2001 00:23:12 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3G7N8888782 for ; Mon, 16 Apr 2001 16:23:09 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010416100503U.matusita@jp.FreeBSD.org> References: <20010416100503U.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 14 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Re: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED) Date: Mon, 16 Apr 2001 16:22:55 +0900 Message-Id: <20010416162255X.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG matusita> There is a small typo in src/release/Makefile rev 1.161; not ' matusita> kernel', but 'KERNEL' is correct. Because of this, Current "make release" of 5-current is broken: ===> wi install -c -o root -g wheel -m 555 -fschg if_wi.ko /R/stage/kernels/GENERIC make KERNEL= DESTDIR=/R/stage/kernels kernel-reinstall.debug make: don't know how to make kernel-reinstall.debug. Stop *** Error code 2 -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 0:34: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 9D31937B43C; Mon, 16 Apr 2001 00:34:06 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3G7Y4889021; Mon, 16 Apr 2001 16:34:04 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.ORG In-Reply-To: <20010416001907.A59585@dragon.nuxi.com> References: <20010416100503U.matusita@jp.FreeBSD.org> <20010416100503U.matusita@jp.FreeBSD.org> <20010416001907.A59585@dragon.nuxi.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 8 From: Makoto MATSUSHITA To: obrien@FreeBSD.ORG Subject: Re: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED) Date: Mon, 16 Apr 2001 16:33:49 +0900 Message-Id: <20010416163349J.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG obrien> I think I got all these already. But I rev 1.161 is from back in 1995. obrien> Are you sure you've got the right /usr/src/release/Makefile? Oops.... it should be '1.611'. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 0:50:41 2001 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 8744C37B42C for ; Mon, 16 Apr 2001 00:50:37 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA13814; Mon, 16 Apr 2001 17:50:19 +1000 Date: Mon, 16 Apr 2001 17:49:25 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Justin T. Gibbs" Cc: Matt Dillon , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <200104160259.f3G2xqs06321@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Apr 2001, Justin T. Gibbs wrote: > > There's no downside, really. > > It just seems inelegant to have a system that, on paper, is > so inefficient. Can't we do better? Sure. Don't discard buffer contents when recycling a B_MALLOC'ed buffer, but manage it using a secondary buffer cache that doesn't have as much overhead as the primary one (in particular, don't reserve BKVASIZE bytes of kernel virtual address space for each secondary buffer). This would be even more inelegant, and more complicated, but not so inefficient. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 5:34:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 8C36737B449; Mon, 16 Apr 2001 05:34:05 -0700 (PDT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f3GCXx285356; Mon, 16 Apr 2001 14:33:59 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200104161233.f3GCXx285356@zibbi.icomtek.csir.co.za> Subject: Re: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED) In-Reply-To: <20010416001907.A59585@dragon.nuxi.com> from "David O'Brien" at "Apr 16, 2001 00:19:07 am" To: obrien@FreeBSD.ORG Date: Mon, 16 Apr 2001 14:33:59 +0200 (SAT) Cc: matusita@jp.FreeBSD.org (Makoto MATSUSHITA), 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 > On Mon, Apr 16, 2001 at 10:05:03AM +0900, Makoto MATSUSHITA wrote: > > There is a small typo in src/release/Makefile rev 1.161; not 'kernel', > > but 'KERNEL' is correct. > > I think I got all these already. But I rev 1.161 is from back in 1995. > Are you sure you've got the right /usr/src/release/Makefile? No it is just a typo, he meant rev 1.611. And it is broken for me too. It is because ${kernel} is not defined. ${KERNEL} on the other hand... A make release dies with: ===> splash/pcx install -c -o root -g wheel -m 555 -fschg splash_pcx.ko /R/stage/kernels/GENERIC ===> sr install -c -o root -g wheel -m 555 -fschg if_sr.ko /R/stage/kernels/GENERIC ===> streams install -c -o root -g wheel -m 555 -fschg streams.ko /R/stage/kernels/GENERIC ===> vesa install -c -o root -g wheel -m 555 -fschg vesa.ko /R/stage/kernels/GENERIC ===> wi install -c -o root -g wheel -m 555 -fschg if_wi.ko /R/stage/kernels/GENERIC make KERNEL= DESTDIR=/R/stage/kernels kernel-reinstall.debug make: don't know how to make kernel-reinstall.debug. Stop *** Error code 2 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. End Mon Apr 16 14:21:35 SAST 2001 John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 7:11:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from reuben.meganet.net (reuben.meganet.net [209.213.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 4102737B43E for ; Mon, 16 Apr 2001 07:11:39 -0700 (PDT) (envelope-from estair@computer-exchange.com) Received: from proxy (dial-tnt01-p2-049.bos.ma.meganet.net [209.213.73.49]) by reuben.meganet.net (8.9.3/8.9.1-BW0200.01SP) with SMTP id KAA11723 for ; Mon, 16 Apr 2001 10:11:46 -0400 From: estair@computer-exchange.com Message-ID: <001701c0c67f$500931e0$3149d5d1@mshome.net> To: Subject: Unable to stop sendmail from loading at boot. Date: Mon, 16 Apr 2001 10:12:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all. I'm running 5.0current 4-12-01, from a net install, X-Kern-Developer base. The problem I'm having is that sendmail is running at system start, even though the default /etc/defaults/rc.conf sets sendmail_enable="NO", and I've tried setting the same in /etc/rc.conf in case it's not parsing the defaults file. But it doesn't change anything. Does anyone have any recommendations? I'm going to remove sendmail.cf since that is read as an "if" in /etc/rc to before starting sendmail, but that seems quite the hack just to disable the mail daemon. I'll try any suggestions after work, and will re-post Tuesday. Thanks, Eli Stair To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 7:31:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 2895F37B43E for ; Mon, 16 Apr 2001 07:31:40 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA24585; Mon, 16 Apr 2001 07:29:54 -0700 (PDT) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA01062; Mon, 16 Apr 2001 07:20:52 -0700 (PDT) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id IAA26071; Mon, 16 Apr 2001 08:29:52 -0600 (MDT) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21) id ; Mon, 16 Apr 2001 08:29:53 -0600 Message-ID: From: "Long, Scott" To: "'estair@computer-exchange.com '" , "'freebsd-current@freebsd.org '" Subject: RE: Unable to stop sendmail from loading at boot. Date: Mon, 16 Apr 2001 08:29:52 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add 'sendmail_outbound_enable="NO"' to /etc/rc.conf and things should return to the behaviour that you want. This extra sendmail knob was added to /etc/rc about a month ago. Scott -----Original Message----- From: estair@computer-exchange.com To: freebsd-current@freebsd.org Sent: 4/16/01 8:12 AM Subject: Unable to stop sendmail from loading at boot. Hello all. I'm running 5.0current 4-12-01, from a net install, X-Kern-Developer base. The problem I'm having is that sendmail is running at system start, even though the default /etc/defaults/rc.conf sets sendmail_enable="NO", and I've tried setting the same in /etc/rc.conf in case it's not parsing the defaults file. But it doesn't change anything. Does anyone have any recommendations? I'm going to remove sendmail.cf since that is read as an "if" in /etc/rc to before starting sendmail, but that seems quite the hack just to disable the mail daemon. I'll try any suggestions after work, and will re-post Tuesday. Thanks, Eli Stair To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 7:52: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.klondike.ru (ns.klondike.ru [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 95D0137B440 for ; Mon, 16 Apr 2001 07:51:51 -0700 (PDT) (envelope-from zhecka@klondike.ru) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id SAA12073 for ; Mon, 16 Apr 2001 18:51:47 +0400 (MSD) Date: Mon, 16 Apr 2001 18:49:08 +0400 From: Kaltashkin Eugene To: freebsd-current@freebsd.org Subject: broken sshd or libssl ? Message-Id: <20010416184908.0f8b531b.zhecka@klondike.ru> X-Mailer: stuphead ver. 0.5.0 (CleverMan) (GTK+ 1.2.10; FreeBSD 5.0-CURRENT; i386) Organization: Klondike Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I update 4.3 RC to 5.0-CURRENT and have some troubles. Why make buildworld build system without RSA support ? And how i can correct this problem ? System cvsuped today. freebsd:/home/zhecka# sshd -d debug1: sshd version OpenSSH_2.3.0 green@FreeBSD.org 20010319 no RSA support in libssl and libcrypto. See ssl(8) Disabling protocol version 1 debug1: read DSA private key done debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. debug1: Server will not fork when running in debugging mode. Connection from localhost port 1021 Connection from 127.0.0.1 port 1021 debug1: Client protocol version 2.0; client software version OpenSSH_2.3.0 green@FreeBSD.org 20010319 debug1: match: OpenSSH_2.3.0 green@FreeBSD.org 20010319 pat ^OpenSSH[-_]2\.3 Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_2.3.0 green@FreeBSD.org 20010319 debug1: send KEXINIT debug1: done debug1: wait KEXINIT debug1: got kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 debug1: got kexinit: ssh-dss debug1: got kexinit: 3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se debug1: got kexinit: 3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se debug1: got kexinit: hmac-sha1,hmac-md5,hmac-ripemd160@openssh.com debug1: got kexinit: hmac-sha1,hmac-md5,hmac-ripemd160@openssh.com debug1: got kexinit: none debug1: got kexinit: none debug1: got kexinit: debug1: got kexinit: debug1: first kex follow: 0 debug1: reserved: 0 debug1: done debug1: kex: client->server 3des-cbc hmac-sha1 none debug1: kex: server->client 3des-cbc hmac-sha1 none debug1: Wait SSH2_MSG_KEX_DH_GEX_REQUEST. /etc/ssh/primes: No such file or directory WARNING: /etc/ssh/primes does not exist, using old prime fatal: DH_generate_key debug1: Calling cleanup 0x805ec78(0x0) -- Best Regards Kaltashkin Eugene ZHECKA-RIPN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 9:23:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 8709737B43E for ; Mon, 16 Apr 2001 09:23:11 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3GGN6W83082 for current@freebsd.org; Mon, 16 Apr 2001 09:23:06 -0700 (PDT) Date: Mon, 16 Apr 2001 09:23:06 -0700 (PDT) From: David Wolfskill Message-Id: <200104161623.f3GGN6W83082@bunrab.catwhisker.org> To: current@freebsd.org Subject: lock messages from today's -CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw that jhb committed some changes as of r1.307 of src/sys/i386/conf/GENERIC, so I replicated those changes (that I didn't already have) to my kernel config. Got -CURRENT built & running; the message below (bracketed by "normal" messages, to supply a little context) appear to be documenting weirdnesses, but I don't see other evidence of problems: Apr 16 08:57:44 localhost /boot/kernel/kernel: pccard: card inserted, slot 1 Apr 16 08:57:44 localhost /boot/kernel/kernel: acquring duplicate lock of same type: "allproc" Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st @ /usr/src/sys/kern/kern_proc.c:584 Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd @ /usr/src/sys/kern/kern_proc.c:143 Apr 16 08:57:44 localhost /boot/kernel/kernel: lock order reversal Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st vnode interlock last acquired @ /usr/src/sys/kern/vfs_vnops.c:625 Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd 0xc0459b80 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:954 Apr 16 08:57:44 localhost /boot/kernel/kernel: 3rd 0xce7d54ac vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:963 Apr 16 08:57:44 localhost savecore: magic number mismatch (8b98aa0d != 8fca0101) Apr 16 08:57:44 localhost savecore: no core dump Last CVSup was: CVSup started from cvsup14.freebsd.org at Mon Apr 16 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Mon Apr 16 03:52:03 PDT 2001 And uname says FreeBSD m138.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #33: Mon Apr 16 08:41:02 PDT 2001 root@localhost:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Should this be interesting enough to pursue (probably off-list), I'll be happy to work with one or more folks on it; the machine is my (uni-processor) laptop. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 9:34:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 1584F37B43C for ; Mon, 16 Apr 2001 09:34:40 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3GGYZs11356; Mon, 16 Apr 2001 10:34:35 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104161634.f3GGYZs11356@aslan.scsiguy.com> To: Matt Dillon Cc: Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: Your message of "Sun, 15 Apr 2001 23:16:18 PDT." <200104160616.f3G6GI973782@earth.backplane.com> Date: Mon, 16 Apr 2001 10:34:35 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't consider it inefficient. Sure, if you look at this one aspect > of the caching taken out of context it may appear to be inefficient, > but if you look at the whole enchilada the memory issue is nothing > more then a minor footnote - not worth the effort of worrying about. This is like saying that there is nothing to be gained by making better use of available cache memory. I don't care that the cache is dynamic and caches the right things when the cache is effectively made so small that it doesn't cache my working set. Even with VMIO turned on for directories, Linux kicks our ass in caching meta-data unless you have a lot of memory. That sucks. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 9:53:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 467B237B43C; Mon, 16 Apr 2001 09:53:43 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id JAA13349; Mon, 16 Apr 2001 09:53:47 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f3GGrh657661; Mon, 16 Apr 2001 09:53:43 -0700 (PDT) (envelope-from bmah) Message-Id: <200104161653.f3GGrh657661@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: obrien@freebsd.org Cc: bmah@freebsd.org, freebsd-current@freebsd.org Subject: One more typo in src/release/Makefile, rev 1.612? (w/patch) From: bmah@freebsd.org (Bruce A. Mah) Reply-To: bmah@freebsd.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1507808330P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 16 Apr 2001 09:53:43 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-1507808330P Content-Type: text/plain; charset=us-ascii Hi David-- Thanks for fixing the typo in src/release/Makefile. I think however the real cause of the error that people were seeing is a typo on the line above...there should (I think) be a " && \" at the end of the previous line. So what happens is that the "make kernel-reinstall-debug" gets run in the wrong directory, and that's why it's falling over. Patch below. I'm testing this now... Cheers, Bruce. Index: Makefile =================================================================== RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.612 diff -u -r1.612 Makefile --- Makefile 2001/04/16 15:17:27 1.612 +++ Makefile 2001/04/16 16:44:41 @@ -846,7 +846,7 @@ make ${KERNEL_FLAGS} KERNEL=${KERNEL} && \ make KERNEL=${KERNEL} DESTDIR=${RD}/kernels install && \ [ -r ${.CURDIR}/../sys/${MACHINE}/conf/${KERNEL}.hints ] && \ - cp ${.CURDIR}/../sys/${MACHINE}/conf/${KERNEL}.hints ${RD}/kernels + cp ${.CURDIR}/../sys/${MACHINE}/conf/${KERNEL}.hints ${RD}/kernels && \ make KERNEL=${KERNEL} DESTDIR=${RD}/kernels kernel-reinstall.debug # --==_Exmh_-1507808330P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE62yOW2MoxcVugUsMRAuo/AKCEx8YGb+MNaAETpPaNaWHbzQuA5ACfbHUT O8A9qxCLYdUcTwRUgxzzz0Y= =vBGs -----END PGP SIGNATURE----- --==_Exmh_-1507808330P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 10: 1:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 6DE6737B423; Mon, 16 Apr 2001 10:01:15 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f3GH1Eb98139; Mon, 16 Apr 2001 10:01:14 -0700 (PDT) (envelope-from obrien) Date: Mon, 16 Apr 2001 09:59:52 -0700 From: "David O'Brien" To: "Bruce A. Mah" Cc: freebsd-current@freebsd.org Subject: Re: One more typo in src/release/Makefile, rev 1.612? (w/patch) Message-ID: <20010416095952.A98118@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200104161653.f3GGrh657661@bmah-freebsd-0.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104161653.f3GGrh657661@bmah-freebsd-0.cisco.com>; from bmah@freebsd.org on Mon, Apr 16, 2001 at 09:53:43AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 09:53:43AM -0700, Bruce A. Mah wrote: > Thanks for fixing the typo in src/release/Makefile. I think however the > real cause of the error that people were seeing is a typo on the line Damnit, I *tested* this and things landed in the right place. Grrr... Ok, no more hacking until I get a CVSup with the lastest release/Makefile and I'll kick off a fresh release to test. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:23: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id 3E09337B43E for ; Mon, 16 Apr 2001 12:22:59 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C321266E07; Mon, 16 Apr 2001 12:22:54 -0700 (PDT) Date: Mon, 16 Apr 2001 12:22:54 -0700 From: Kris Kennaway To: Kaltashkin Eugene Cc: freebsd-current@freebsd.org Subject: Re: broken sshd or libssl ? Message-ID: <20010416122254.A10667@xor.obsecurity.org> References: <20010416184908.0f8b531b.zhecka@klondike.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010416184908.0f8b531b.zhecka@klondike.ru>; from zhecka@klondike.ru on Mon, Apr 16, 2001 at 06:49:08PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Did you remember to run mergemaster? Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE620aOWry0BWjoQKURAkybAJ0ffaM+c5FS6PPbhrocOz3jDauT7gCePZG7 4bzYrz/4GvinKIt+tkcmur8= =hfcJ -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:30:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3DD0C37B423 for ; Mon, 16 Apr 2001 12:30:20 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f3GJUAM20721 for ; Mon, 16 Apr 2001 12:30:10 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E8C6538FE; Mon, 16 Apr 2001 12:30:09 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: estair@computer-exchange.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Unable to stop sendmail from loading at boot. In-Reply-To: <001701c0c67f$500931e0$3149d5d1@mshome.net> Date: Mon, 16 Apr 2001 12:30:09 -0700 From: Peter Wemm Message-Id: <20010416193009.E8C6538FE@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG estair@computer-exchange.com wrote: > Hello all. > > I'm running 5.0current 4-12-01, from a net install, X-Kern-Developer base. > > The problem I'm having is that sendmail is running at system start, even > though > the default /etc/defaults/rc.conf sets sendmail_enable="NO", and I've tried > setting > the same in /etc/rc.conf in case it's not parsing the defaults file. But it > doesn't change > anything. > > Does anyone have any recommendations? I'm going to remove sendmail.cf since > that > is read as an "if" in /etc/rc to before starting sendmail, but that seems > quite the hack > just to disable the mail daemon. That would work. Make sure you disable cron too, because that calls sendmail. Removing /usr/sbin/sendmail would work too, and would also guarantee that the box cannot send mail, as you seem to want. You should also probably set NO_SENDMAIL=true and NO_MAILWRAPPER=true in your /etc/make.conf, and remove /usr/libexec/sendmail/sendmail as well. > I'll try any suggestions after work, and will re-post Tuesday. > > Thanks, > > Eli Stair > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:36:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc24.worldnet.att.net (mtiwmhc24.worldnet.att.net [204.127.131.49]) by hub.freebsd.org (Postfix) with ESMTP id 2569337B43E for ; Mon, 16 Apr 2001 12:36:22 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com ([12.72.203.153]) by mtiwmhc24.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010416193615.ORGM10838.mtiwmhc24.worldnet.att.net@hotmail.com> for ; Mon, 16 Apr 2001 19:36:15 +0000 Message-ID: <3ADB49AA.FED31D9C@hotmail.com> Date: Mon, 16 Apr 2001 12:36:10 -0700 From: walt Organization: none X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: No MAKEDEV? 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 upgraded a fresh install of 4.2 to CURRENT. Everything seemed to go great until I discovered that I have only a small subset of the standard entries in /dev and there is no /dev/MAKEDEV or /dev/MAKEDEV.local. I re-cvsup'd again this morning and repeated the entire makeworld makekernel installkernel installworld mergemaster cycle a second time. It all went great except that I still have no MAKEDEV in /dev and very few entries in /dev, all of which are dated today. I've tried using 'install' to move /usr/src/etc/MAKEDEV into /dev, and tried cp and mv and even did a 'make distribution' from /usr/src/etc and always get an 'operation not supported' error message. I did all these things in single-user mode, BTW. Second question: what is the status of /stand/sysinstall? I see that the new version is in /usr/sbin. Is the old location obsolete? Thanks for any clues! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:43:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from daphne.unloved.org (daphne.unloved.org [62.58.62.165]) by hub.freebsd.org (Postfix) with ESMTP id 3B98337B449 for ; Mon, 16 Apr 2001 12:43:49 -0700 (PDT) (envelope-from ashp@unloved.org) Received: by daphne.unloved.org (Postfix, from userid 1001) id 1133311787; Mon, 16 Apr 2001 21:44:07 +0200 (CEST) Date: Mon, 16 Apr 2001 21:44:07 +0200 From: Ashley Penney To: walt Cc: freebsd-current@freebsd.org Subject: Re: No MAKEDEV? Message-ID: <20010416214407.A62363@daphne.unloved.org> Mail-Followup-To: Ashley Penney , walt , freebsd-current@freebsd.org References: <3ADB49AA.FED31D9C@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADB49AA.FED31D9C@hotmail.com>; from wa1ter@hotmail.com on Mon, Apr 16, 2001 at 12:36:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt said: > I just upgraded a fresh install of 4.2 to CURRENT. Everything > seemed to go great until I discovered that I have only a small > subset of the standard entries in /dev and there is no > /dev/MAKEDEV or /dev/MAKEDEV.local. > > I re-cvsup'd again this morning and repeated the entire > makeworld makekernel installkernel installworld mergemaster > cycle a second time. > > It all went great except that I still have no MAKEDEV in /dev > and very few entries in /dev, all of which are dated today. > > I've tried using 'install' to move /usr/src/etc/MAKEDEV into > /dev, and tried cp and mv and even did a 'make distribution' > from /usr/src/etc and always get an 'operation not supported' > error message. > > I did all these things in single-user mode, BTW. I don't run -CURRENT, but check your kernel configuration for "devfs", this basically dynamically creates /dev entries when required, rather than having the entire lot there. Have you actually had any problems with the machine as a result of the tiny amount of /dev entries? If not, I wouldn't worry too much. -- "People who bite the hand that feeds them usually lick the boot that kicks them." -- Unknown. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:51:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 791C637B422 for ; Mon, 16 Apr 2001 12:51:20 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by peitho.fxp.org (Postfix, from userid 1501) id E62EC13615; Mon, 16 Apr 2001 15:51:19 -0400 (EDT) Date: Mon, 16 Apr 2001 15:51:19 -0400 From: Chris Faulhaber To: walt Cc: freebsd-current@freebsd.org Subject: Re: No MAKEDEV? Message-ID: <20010416155119.A14159@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , walt , freebsd-current@freebsd.org References: <3ADB49AA.FED31D9C@hotmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADB49AA.FED31D9C@hotmail.com>; from wa1ter@hotmail.com on Mon, Apr 16, 2001 at 12:36:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt wrote: > I just upgraded a fresh install of 4.2 to CURRENT. Everything > seemed to go great until I discovered that I have only a small > subset of the standard entries in /dev and there is no > /dev/MAKEDEV or /dev/MAKEDEV.local. >=20 > I re-cvsup'd again this morning and repeated the entire > makeworld makekernel installkernel installworld mergemaster > cycle a second time. >=20 > It all went great except that I still have no MAKEDEV in /dev > and very few entries in /dev, all of which are dated today. >=20 devfs(5) > I've tried using 'install' to move /usr/src/etc/MAKEDEV into > /dev, and tried cp and mv and even did a 'make distribution' > from /usr/src/etc and always get an 'operation not supported' > error message. >=20 > I did all these things in single-user mode, BTW. >=20 > Second question: what is the status of /stand/sysinstall? > I see that the new version is in /usr/sbin. Is the old > location obsolete? >=20 See /usr/src/UPDATING for all the answers :) --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjrbTTcACgkQObaG4P6BelASRQCfd1V/ZAYZyPumVLzzGgJVR/lO nNgAniywlGskgYtv66nd1gyPcGYK4Ivp =bQVY -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 12:54:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 955FC37B423 for ; Mon, 16 Apr 2001 12:54:20 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by peitho.fxp.org (Postfix, from userid 1501) id 4CCD21360C; Mon, 16 Apr 2001 15:54:20 -0400 (EDT) Date: Mon, 16 Apr 2001 15:54:20 -0400 From: Chris Faulhaber To: walt Cc: freebsd-current@freebsd.org Subject: Re: No MAKEDEV? Message-ID: <20010416155420.C14159@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , walt , freebsd-current@freebsd.org References: <3ADB49AA.FED31D9C@hotmail.com> <20010416155119.A14159@peitho.fxp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="raC6veAxrt5nqIoY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010416155119.A14159@peitho.fxp.org>; from jedgar@fxp.org on Mon, Apr 16, 2001 at 03:51:19PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --raC6veAxrt5nqIoY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 16, 2001 at 03:51:19PM -0400, Chris Faulhaber wrote: > On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt wrote: > > Second question: what is the status of /stand/sysinstall? > > I see that the new version is in /usr/sbin. Is the old > > location obsolete? > >=20 >=20 > See /usr/src/UPDATING for all the answers :) >=20 Ok, I lied. Yes, /usr/sbin is the new location for sysinstall... --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --raC6veAxrt5nqIoY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjrbTewACgkQObaG4P6BelAChwCeI1nRgBl7jdPumNMTpU39pQRv Fn8An0nP0Lu8WSUzn85ryYIP1f96gC6j =/cv5 -----END PGP SIGNATURE----- --raC6veAxrt5nqIoY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 13:19:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 2F18637B440 for ; Mon, 16 Apr 2001 13:19:39 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.3/8.11.3) with ESMTP id f3GKJMw69635; Mon, 16 Apr 2001 22:19:24 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200104162019.f3GKJMw69635@gratis.grondar.za> To: Kaltashkin Eugene Cc: freebsd-current@FreeBSD.ORG Subject: Re: broken sshd or libssl ? References: <20010416184908.0f8b531b.zhecka@klondike.ru> In-Reply-To: <20010416184908.0f8b531b.zhecka@klondike.ru> ; from Kaltashkin Eugene "Mon, 16 Apr 2001 18:49:08 +0400." Date: Mon, 16 Apr 2001 22:20:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I update 4.3 RC to 5.0-CURRENT and have some troubles. > > Why make buildworld build system without RSA support ? > And how i can correct this problem ? > System cvsuped today. Go to /dev and remake all your devices. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 14:12:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc23.worldnet.att.net (mtiwmhc23.worldnet.att.net [204.127.131.48]) by hub.freebsd.org (Postfix) with ESMTP id C9B6A37B423 for ; Mon, 16 Apr 2001 14:12:08 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com ([12.72.203.153]) by mtiwmhc23.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010416211207.KNI4080.mtiwmhc23.worldnet.att.net@hotmail.com> for ; Mon, 16 Apr 2001 21:12:07 +0000 Message-ID: <3ADB6021.57F680B7@hotmail.com> Date: Mon, 16 Apr 2001 14:12:01 -0700 From: walt Organization: none X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: How to mount DOS/Linux 'extended' partitons. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With help from Chris & Ashley I just figured this out-- thanks to both of you. The man page for devfs definitely does not make this clear, BTW: 'Primary' DOS partitons (aka slices) are numbered 1 thru 4, even if you don't actually use them all. 'Extended' DOS partitions can be accessed in FBSD (as in Linux) starting with numbers 5 and above, e.g. /dev/ad0s5, ad0s6... depending on the number of extended partitions you create on your hard disk. With the new devfs kernel these partitions are not visible in /dev *until* you mount them with, e.g., mount_msdos /dev/ad0s6 /mnt or mount_ext2fs /dev/ad0s5 /mnt But there is no clue that these 'devices' exist until you actually mount them. I hope this may save some time for other newbies migrating from the Linux world. Next question: is it possible to create 4.2BSD filesystems on these 'extended' partitions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 14:19:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 67EED37B43F; Mon, 16 Apr 2001 14:19:36 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA18749; Tue, 17 Apr 2001 07:19:33 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K2HXRQQEU8S4NLCD@cim.alcatel.com.au>; Tue, 17 Apr 2001 07:19:19 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f3GLJUn47473; Tue, 17 Apr 2001 07:19:30 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 17 Apr 2001 07:19:30 +1000 From: Peter Jeremy Subject: Re: WITNESS + WITNESS_SKIPSPIN = panic In-reply-to: ; from jhb@FreeBSD.ORG on Sat, Apr 14, 2001 at 06:54:28PM -0700 To: John Baldwin Cc: freebsd-current@FreeBSD.ORG Mail-Followup-To: John Baldwin , freebsd-current@FreeBSD.ORG Message-id: <20010417071929.C66243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010415093916.A39554@gsmx07.alcatel.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-14 18:54:28 -0700, John Baldwin wrote: > >On 14-Apr-01 Peter Jeremy wrote: >> Is there any progress on fixing this? >> >> Peter > >It panics? I'll see if I can reproduce this on Monday. I never use skipspin. A similar problem was reported here in mid-March, ending with the following message: On Mon, 12 Mar 2001 10:49:51 -0800 (PST), in , John Baldwin wrote: >Just don't use the skipspin stuff, it shouldn't hurt at all. The new witness >code will hopefully be in by the end of the week. *crosses fingers* I bumped into the same problem last week and couldn't find anything that looked like a change in the skipspin behaviour since mid-March. Having looked in more detail at the previous thread, I suspect I may be seeing something different. In my case, the kernel is panicing very early during the boot process in either line 302 or 305 of /sys/kern/subr_witness.c in witness_initialize(): 299 /* First add in all the specified order lists. */ 300 for (order = order_lists; order->w_name != NULL; order++) { 301 w = enroll(order->w_name, order->w_class); 302 w->w_file = "order list"; 303 for (order++; order->w_name != NULL; order++) { 304 w1 = enroll(order->w_name, order->w_class); 305 w1->w_file = "order list"; 306 itismychild(w, w1); 307 w = w1; 308 } 309 } The problem is that enroll() will return NULL for spinlocks when witness_skipspin is set, but the above code always assumes it can de-reference the result from enroll(). (There are two other calls to enroll() where a NULL return appears to be acceptable). I don't understand the mutex initialisation well enough to be able to readily work out the correct fix. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 14:46:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id E3EEA37B449 for ; Mon, 16 Apr 2001 14:46:17 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3GLkGT82369; Mon, 16 Apr 2001 14:46:16 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Apr 2001 14:46:16 -0700 (PDT) From: Matt Dillon Message-Id: <200104162146.f3GLkGT82369@earth.backplane.com> To: "Justin T. Gibbs" Cc: Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> I don't consider it inefficient. Sure, if you look at this one aspect :> of the caching taken out of context it may appear to be inefficient, :> but if you look at the whole enchilada the memory issue is nothing :> more then a minor footnote - not worth the effort of worrying about. : :This is like saying that there is nothing to be gained by making better :use of available cache memory. I don't care that the cache is dynamic :and caches the right things when the cache is effectively made so small :that it doesn't cache my working set. Even with VMIO turned on for :directories, Linux kicks our ass in caching meta-data unless you have :a lot of memory. That sucks. : :-- :Justin It is not implying that at all. There is no black and white here. This is a case where spending a huge amount of time and complexity to get the efficiency down to the Nth degree is nothing but a waste of time. What matters is what the user sees, what performance the application gets, and how many bugs you introduce when optimizing something that might not need optimizing. And in regards to Linux... you can't possibly be implying that performance differences between linux and FreeBSD are due to whether we spend 4K or 512 bytes caching a directory block. The issue has nothing to do with small-directory memory efficiency. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 15: 9:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from student.wesleyan.edu (student.wesleyan.edu [129.133.1.63]) by hub.freebsd.org (Postfix) with ESMTP id 5F2F437B440 for ; Mon, 16 Apr 2001 15:09:09 -0700 (PDT) (envelope-from vsavichev@wesleyan.edu) Received: (from nobody@localhost) by student.wesleyan.edu (8.9.3/8.9.3) id SAA14768 for freebsd-current@freebsd.org; Mon, 16 Apr 2001 18:09:08 -0400 (EDT) X-Authentication-Warning: student.wesleyan.edu: nobody set sender to vsavichev@wesleyan.edu using -f To: Subject: /ports/x11-toolkits/qt23 doesn't build Message-ID: <987458948.3adb6d848003f@mail.wesleyan.edu> Date: Mon, 16 Apr 2001 18:09:08 -0400 From: MIME-Version: 1.0 Content-Type: text/plain; Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.0-pre13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The port qt23 as cvsup'd from current doesn't build, affects many related packets. Any clues ? ===> Script "configure" failed: here are the contents of "config.log" cat: config.log: No such file or directory *** Error code 1 Stop in /usr/ports/x11-toolkits/qt23. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt23. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt23. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt23. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 15:16:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D415737B423 for ; Mon, 16 Apr 2001 15:16:36 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3GMGPG77904; Mon, 16 Apr 2001 15:16:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010417071929.C66243@gsmx07.alcatel.com.au> Date: Mon, 16 Apr 2001 15:15:51 -0700 (PDT) From: John Baldwin To: Peter Jeremy Subject: Re: WITNESS + WITNESS_SKIPSPIN = panic Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Apr-01 Peter Jeremy wrote: > On 2001-Apr-14 18:54:28 -0700, John Baldwin wrote: >> >>On 14-Apr-01 Peter Jeremy wrote: >>> Is there any progress on fixing this? >>> >>> Peter >> >>It panics? I'll see if I can reproduce this on Monday. I never use >>skipspin. > > A similar problem was reported here in mid-March, ending with the > following message: > > On Mon, 12 Mar 2001 10:49:51 -0800 (PST), in > , John Baldwin wrote: >>Just don't use the skipspin stuff, it shouldn't hurt at all. The new witness >>code will hopefully be in by the end of the week. *crosses fingers* > > I bumped into the same problem last week and couldn't find anything > that looked like a change in the skipspin behaviour since mid-March. > > Having looked in more detail at the previous thread, I suspect I may > be seeing something different. In my case, the kernel is panicing > very early during the boot process in either line 302 or 305 of > /sys/kern/subr_witness.c in witness_initialize(): > > 299 /* First add in all the specified order lists. */ > 300 for (order = order_lists; order->w_name != NULL; order++) { > 301 w = enroll(order->w_name, order->w_class); > 302 w->w_file = "order list"; > 303 for (order++; order->w_name != NULL; order++) { > 304 w1 = enroll(order->w_name, order->w_class); > 305 w1->w_file = "order list"; > 306 itismychild(w, w1); > 307 w = w1; > 308 } > 309 } > > The problem is that enroll() will return NULL for spinlocks when > witness_skipspin is set, but the above code always assumes it > can de-reference the result from enroll(). (There are two other > calls to enroll() where a NULL return appears to be acceptable). Argh, ok. > I don't understand the mutex initialisation well enough to be able > to readily work out the correct fix. I'll fix it later on today. > Peter -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 15:53: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 2424B37B43F for ; Mon, 16 Apr 2001 15:53:02 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3GMqwG83808; Mon, 16 Apr 2001 15:52:58 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Apr 2001 15:52:58 -0700 (PDT) From: Matt Dillon Message-Id: <200104162252.f3GMqwG83808@earth.backplane.com> To: Bruce Evans Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> It just seems inelegant to have a system that, on paper, is :> so inefficient. Can't we do better? : :Sure. Don't discard buffer contents when recycling a B_MALLOC'ed buffer, :but manage it using a secondary buffer cache that doesn't have as much :overhead as the primary one (in particular, don't reserve BKVASIZE bytes :of kernel virtual address space for each secondary buffer). This would :be even more inelegant, and more complicated, but not so inefficient. : :Bruce Well, I think the last few years have proven that B_MALLOC buffers are essentially unmanageable. Even if you were to come up with the perfect algorithm, KVM just doesn't scale to physical memory the way it should. Only physical memory scales to physical memory, and that means the VM Page cache. We could conceivably use the VM object representing the filesystem block device, which normally only holds cylinder group bitmaps and inodes, and use it to back piecemeal buffer cache mappings for directories (at least as long as we do not allow mmap()ing of directories, which would make this impossible). The backing pages would still be 4K, and we would have to be extremely careful in regards to the valid and dirty bits in the vm_page_t so as not to infringe on adjacent file fragments (which could be mmap'd), but now the 4K of backing store would be able to cache up to 8 small directories that happen to reside in the same filesystem block. The above would be an extremely complex solution and I wouldn't want to implement it for that reason. A separately managed buffer cache is also a complex solution because in order to be effective it needs to be scaleable (as the current B_MALLOC is not). Even though the potential wasteage with the current solution seems high, the actual impact on the system is low. I have yet to see any detrimental results in my own testing. Anyone can test -- simply turn on the vmiodirenable sysctl and have at it! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 15:59:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id 512FB37B424 for ; Mon, 16 Apr 2001 15:59:29 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id 924631BD72; Mon, 16 Apr 2001 17:57:23 -0500 (EST) Date: Mon, 16 Apr 2001 17:57:23 -0500 From: Will Andrews To: vsavichev@wesleyan.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: /ports/x11-toolkits/qt23 doesn't build Message-ID: <20010416175723.E5017@casimir.physics.purdue.edu> Reply-To: Will Andrews References: <987458948.3adb6d848003f@mail.wesleyan.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bjuZg6miEcdLYP6q" Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <987458948.3adb6d848003f@mail.wesleyan.edu>; from vsavichev@wesleyan.edu on Mon, Apr 16, 2001 at 06:09:08PM -0400 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --bjuZg6miEcdLYP6q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 16, 2001 at 06:09:08PM -0400, vsavichev@wesleyan.edu wrote: > The port qt23 as cvsup'd from current doesn't build, affects=20 > many related packets. Any clues ? >=20 > =3D=3D=3D> Script "configure" failed: here are the contents of "config.l= og" > cat: config.log: No such file or directory > *** Error code 1 This is a known problem. I don't have time to fix it right now, considering -current isn't the focus at the moment. --=20 wca --bjuZg6miEcdLYP6q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE623jTF47idPgWcsURAl14AJwNPAUoI/ZPHXWcDNPWPXeTwrT5nQCeOM6M w5hmDh4SL9cZpo48JkpqPPs= =HQ/S -----END PGP SIGNATURE----- --bjuZg6miEcdLYP6q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 18:43: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 4D45C37B422 for ; Mon, 16 Apr 2001 18:42:58 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.mybox.zip ([207.214.149.189]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0GBW002SOY2ZZZ@mta6.snfc21.pbi.net> for current@freebsd.org; Mon, 16 Apr 2001 18:42:36 -0700 (PDT) Received: by zippy.mybox.zip (Postfix, from userid 1000) id A7C361864; Mon, 16 Apr 2001 18:42:34 -0700 (PDT) Date: Mon, 16 Apr 2001 18:42:34 -0700 From: Alex Zepeda Subject: Re: /ports/x11-toolkits/qt23 doesn't build In-reply-to: <987458948.3adb6d848003f@mail.wesleyan.edu>; from vsavichev@wesleyan.edu on Mon, Apr 16, 2001 at 06:09:08PM -0400 To: vsavichev@wesleyan.edu, current@freebsd.org Message-id: <20010416184234.A3987@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <987458948.3adb6d848003f@mail.wesleyan.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 06:09:08PM -0400, vsavichev@wesleyan.edu wrote: > The port qt23 as cvsup'd from current doesn't build, affects > many related packets. Any clues ? Depending on what you need Qt for, you can always build Qt oob, and it should work pretty well. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 18:51:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 17E4337B43C for ; Mon, 16 Apr 2001 18:51:10 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id BD094288AD; Tue, 17 Apr 2001 08:51:07 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id B0E6428834 for ; Tue, 17 Apr 2001 08:51:07 +0700 (ALMST) Date: Tue, 17 Apr 2001 08:51:07 +0700 (ALMST) From: Boris Popov To: freebsd-current@freebsd.org Subject: smbfs and -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, Recently kernel part of smbfs was committed to the base tree. This means that now smbfs code can be either compiled into kernel or loaded as module. Related options are: LIBMCHAIN, LIBICONV - mandatory. NETSMB, NETSMBCRYPTO, SMBFS - these are replacement for smbfs.ko module. Please deinstall old version of smbfs and install new - 1.4.1. There is no technical problems in adding libsmb, mount_smbfs and smbutil commands to the base tree, but I'm unsure if port version is sufficient. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 19: 9:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A172037B423; Mon, 16 Apr 2001 19:09:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA02683; Mon, 16 Apr 2001 22:09:07 -0400 (EDT) (envelope-from wollman) Date: Mon, 16 Apr 2001 22:09:07 -0400 (EDT) From: Garrett Wollman Message-Id: <200104170209.WAA02683@khavrinen.lcs.mit.edu> To: "John W. De Boskey" Cc: Current List Subject: FIO* doc added to tty.4 (review) In-Reply-To: <20010415222637.A507@FreeBSD.org> References: <20010415222637.A507@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I've been doing some tty related work and found the FIO* > requests don't seem to be documented. > I've added some reasonable doc to tty.4 and put up the > the diff and html forms: As the initial letter suggests, they are generic file ioctls and not specific to the teletype driver. They should be described in the ioctl(2) manual page. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 20:11:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4087237B42C for ; Mon, 16 Apr 2001 20:11:22 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3H3B9G85218; Mon, 16 Apr 2001 20:11:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200104161623.f3GGN6W83082@bunrab.catwhisker.org> Date: Mon, 16 Apr 2001 20:10:38 -0700 (PDT) From: John Baldwin To: David Wolfskill Subject: RE: lock messages from today's -CURRENT Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Apr-01 David Wolfskill wrote: > I saw that jhb committed some changes as of r1.307 of > src/sys/i386/conf/GENERIC, so I replicated those changes (that I didn't > already have) to my kernel config. > > Got -CURRENT built & running; the message below (bracketed by "normal" > messages, to supply a little context) appear to be documenting weirdnesses, > but I don't see other evidence of problems: > > Apr 16 08:57:44 localhost /boot/kernel/kernel: pccard: card inserted, slot 1 > Apr 16 08:57:44 localhost /boot/kernel/kernel: acquring duplicate lock of > same type: "allproc" > Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st @ > /usr/src/sys/kern/kern_proc.c:584 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd @ > /usr/src/sys/kern/kern_proc.c:143 > Apr 16 08:57:44 localhost /boot/kernel/kernel: lock order reversal > Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st vnode interlock last > acquired @ /usr/src/sys/kern/vfs_vnops.c:625 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd 0xc0459b80 mntvnode @ > /usr/src/sys/ufs/ffs/ffs_vfsops.c:954 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 3rd 0xce7d54ac vnode interlock > @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:963 > Apr 16 08:57:44 localhost savecore: magic number mismatch (8b98aa0d != > 8fca0101) > Apr 16 08:57:44 localhost savecore: no core dump These are known right now. The allproc one is because witness is still somewhat bogus wrt to sx locks and treats the recursive shared lock as duplicate acquires of the same lock. The other reversals that are vfs related have been around since probably at least 4.4bsd or perhaps earlier. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 20:11:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D664C37B440 for ; Mon, 16 Apr 2001 20:11:26 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3H3B8G85214; Mon, 16 Apr 2001 20:11:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010415172142.A27168@skriver.dk> Date: Mon, 16 Apr 2001 20:10:37 -0700 (PDT) From: John Baldwin To: Jesper Skriver Subject: RE: kernel panic in -current, ithread or newcard related ? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Apr-01 Jesper Skriver wrote: > About every other time I boot my IBM ThinkPad 600E I get this panic > (hand typed, as I don't have a second machine here to be able to use a > serial console). > > Fatal trap 12: page fault while in kernel mode > Fault virtual address = 0x28 It's a null pointer dereference. If you've compiled a debug kernel then do 'gdb -k /usr/obj/usr/src/sys/TAM2/kernel.debug' and then do 'l *csa_readio+0x17' to find the offending line. It's usually pretty easy to figure out then. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 20:11:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0E65437B43F; Mon, 16 Apr 2001 20:11:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3H3BAG85222; Mon, 16 Apr 2001 20:11:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010416095952.A98118@dragon.nuxi.com> Date: Mon, 16 Apr 2001 20:10:39 -0700 (PDT) From: John Baldwin To: "David O'Brien" Subject: Re: One more typo in src/release/Makefile, rev 1.612? (w/patch) Cc: freebsd-current@FreeBSD.org, "Bruce A. Mah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Apr-01 David O'Brien wrote: > On Mon, Apr 16, 2001 at 09:53:43AM -0700, Bruce A. Mah wrote: >> Thanks for fixing the typo in src/release/Makefile. I think however the >> real cause of the error that people were seeing is a typo on the line > > Damnit, I *tested* this and things landed in the right place. Grrr... > Ok, no more hacking until I get a CVSup with the lastest release/Makefile > and I'll kick off a fresh release to test. Also, Bruce's fix is not entirely correct as it breaks for the non-debug kernel case, but I've already sent you a mail about that, just to let everyone know that it should be fixed shortly. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 20:58: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id 9EAAC37B43C; Mon, 16 Apr 2001 20:58:06 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id UAA29957; Mon, 16 Apr 2001 20:58:31 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f3H3w6S69160; Mon, 16 Apr 2001 20:58:06 -0700 (PDT) (envelope-from bmah) Message-Id: <200104170358.f3H3w6S69160@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: John Baldwin Cc: "David O'Brien" , freebsd-current@FreeBSD.org, "Bruce A. Mah" Subject: Re: One more typo in src/release/Makefile, rev 1.612? (w/patch) In-Reply-To: References: Comments: In-reply-to John Baldwin message dated "Mon, 16 Apr 2001 20:10:39 -0700." From: bmah@FreeBSD.org (Bruce A. Mah) Reply-To: bmah@FreeBSD.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-515751298P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 16 Apr 2001 20:58:06 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-515751298P Content-Type: text/plain; charset=us-ascii If memory serves me right, John Baldwin wrote: > Also, Bruce's fix is not entirely correct as it breaks for the non-debug kern > el > case, Hmmm? I didn't know there was a choice on debug/non-debug kernels during a "make release", but I defer to the experts. > but I've already sent you a mail about that, just to let everyone know > that it should be fixed shortly. :) The longer it goes unfixed, the longer I'll be forced to do Really Important Things (TM) rather than blow away time tinkering with "make release" for my own nefarious purposes. :-) Thanks guys... Bruce. --==_Exmh_-515751298P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6279O2MoxcVugUsMRAg5DAJwLU+yo8dMx/KxD6m/WDtOOp8AQLACfSbVa acJxCtuhLf8TWwCqJYNaAb4= =AO1R -----END PGP SIGNATURE----- --==_Exmh_-515751298P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 21:15:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CCCEA37B443; Mon, 16 Apr 2001 21:15:42 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3H4FUG86554; Mon, 16 Apr 2001 21:15:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200104170358.f3H3w6S69160@bmah-freebsd-0.cisco.com> Date: Mon, 16 Apr 2001 21:15:00 -0700 (PDT) From: John Baldwin To: (Bruce A. Mah) Subject: Re: One more typo in src/release/Makefile, rev 1.612? (w/patch) Cc: freebsd-current@FreeBSD.org, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Apr-01 Bruce A. Mah wrote: > If memory serves me right, John Baldwin wrote: > >> Also, Bruce's fix is not entirely correct as it breaks for the non-debug >> kern >> el >> case, > > Hmmm? I didn't know there was a choice on debug/non-debug kernels > during a "make release", but I defer to the experts. Yes, it's determined by putting 'makeoptions DEBUG=-g' in the kernel config file. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 16 22:49:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 10BBE37B424; Mon, 16 Apr 2001 22:49:08 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id CA7C83E09; Mon, 16 Apr 2001 22:49:07 -0700 (PDT) To: current@freebsd.org Cc: kris@freebsd.org Subject: Cosmetic bug in pw_util.c (with patch) Date: Mon, 16 Apr 2001 22:49:07 -0700 From: Dima Dorfman Message-Id: <20010417054907.CA7C83E09@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Revision 1.18 of pw_util.c (fix for security advisory "chpass" 00:58) introduces a cosmetic bug which manifests itself as such: > passwd Changing local password for dima. Old password: passwd: (null): Permission denied ^^^^^^^^^ passwd: /etc/master.passwd: unchanged Only machines *not* using NIS will display this, since passwd(1) acts differently when changing an NIS password. Trivial patch to fix this is attached below. Thanks, Dima Dorfman dima@unixfreak.org Index: pw_util.c =================================================================== RCS file: /st/src/FreeBSD/src/usr.sbin/vipw/pw_util.c,v retrieving revision 1.18 diff -u -r1.18 pw_util.c --- pw_util.c 2000/07/12 00:49:40 1.18 +++ pw_util.c 2001/04/17 05:41:38 @@ -249,8 +249,12 @@ #ifdef YP extern int _use_yp; #endif /* YP */ - if (err) - warn("%s", name); + if (err) { + if (name != NULL) + warn("%s", name); + else + warn(NULL); + } #ifdef YP if (_use_yp) warnx("NIS information unchanged"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 0:38:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 60EF737B422 for ; Tue, 17 Apr 2001 00:38:48 -0700 (PDT) (envelope-from jwd@bsdwins.com) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.1/8.11.0) id f3H7c6o40747; Tue, 17 Apr 2001 03:38:06 -0400 (EDT) (envelope-from jwd) Date: Tue, 17 Apr 2001 03:38:05 -0400 From: "John W. De Boskey" To: Garrett Wollman Cc: Current List Subject: Re: FIO* doc added to tty.4 (review) Message-ID: <20010417033805.A40658@bsdwins.com> References: <20010415222637.A507@FreeBSD.org> <200104170209.WAA02683@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104170209.WAA02683@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Mon, Apr 16, 2001 at 10:09:07PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wondered about this. However, after looking around what I found was that the FIO* requests seemed to be documented in driver pages (and only a handful at that), and not documented with ioctl. Since I don't want to change the other existing driver man pages, what if I add generic documentation to the ioctl along with a comment saying to look at the individual driver man pages for information specific to the driver. ie: FIONREAD will succeed from a backgrounded process, but the data read itself with hang (tty driver). Thanks, John ps: Is cross-referencing #define values frowned upon? It would be nice if "man -k FIONREAD" (for instance) would return useful results. ----- Garrett Wollman's Original Message ----- > < said: > > > I've been doing some tty related work and found the FIO* > > requests don't seem to be documented. > > > I've added some reasonable doc to tty.4 and put up the > > the diff and html forms: > > As the initial letter suggests, they are generic file ioctls and not > specific to the teletype driver. They should be described in the > ioctl(2) manual page. > > -GAWollman > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1: 8:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id D54C337B424 for ; Tue, 17 Apr 2001 01:08:30 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA66833; Tue, 17 Apr 2001 01:08:26 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3ADBF9FA.9D1C4DB4@DougBarton.net> Date: Tue, 17 Apr 2001 01:08:26 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: "Justin T. Gibbs" , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > It is not implying that at all. There is no black and white here. > This is a case where spending a huge amount of time and complexity > to get the efficiency down to the Nth degree is nothing but a waste > of time. What matters is what the user sees, what performance > the application gets, and how many bugs you introduce when optimizing > something that might not need optimizing. Sooo..... sounds like making "on" the default in -current is a worthy experiment? Doug -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1:13:43 2001 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 DD07637B43C for ; Tue, 17 Apr 2001 01:13:37 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3H8DZb03890; Tue, 17 Apr 2001 01:13:35 -0700 (PDT) Date: Tue, 17 Apr 2001 01:13:35 -0700 From: Alfred Perlstein To: Doug Barton Cc: Matt Dillon , "Justin T. Gibbs" , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417011335.V976@fw.wintelcom.net> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADBF9FA.9D1C4DB4@DougBarton.net>; from DougB@DougBarton.net on Tue, Apr 17, 2001 at 01:08:26AM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Doug Barton [010417 01:08] wrote: > Matt Dillon wrote: > > > It is not implying that at all. There is no black and white here. > > This is a case where spending a huge amount of time and complexity > > to get the efficiency down to the Nth degree is nothing but a waste > > of time. What matters is what the user sees, what performance > > the application gets, and how many bugs you introduce when optimizing > > something that might not need optimizing. > > Sooo..... sounds like making "on" the default in -current is a worthy > experiment? More like I'm damn tired of having to remeber to turn it on all my machines in order to get decent performance when doing large amount of directory ops. I'm figuring the only time when it may be a problem is on machines with a small amount of memory. Since memory is cheap, I plan on turning it on within the next couple of days unless a stability issue comes up. I'll leave it to those people with low memory to remember to turn it off. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1:20: 4 2001 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 F1CF937B43E for ; Tue, 17 Apr 2001 01:19:59 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3H8JvO04082; Tue, 17 Apr 2001 01:19:57 -0700 (PDT) Date: Tue, 17 Apr 2001 01:19:57 -0700 From: Alfred Perlstein To: Matt Dillon Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417011957.W976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104160616.f3G6GI973782@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Apr 15, 2001 at 11:16:18PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010415 23:16] wrote: > > For example, all this work on a preemptive > kernel is just insane. Our entire kernel is built on the concept of > not being preemptable except by interrupts. We virtually guarentee > years of instability and bugs leaking out of the woodwork by trying to > make it preemptable, and the performance gain we get for that pain > is going to be zilch. Nada. Nothing. Pre-emption is mearly a side effect of a mutex'd kernel. The actual gains are in terms of parallel execution internally. Meaning if we happen to copyin() a 4 meg buffer we can allow more than one process to be completing some sort of work inside the kernel other than spinning on the giant lock. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1:43:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id B4F1337B43F for ; Tue, 17 Apr 2001 01:43:15 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA68411; Tue, 17 Apr 2001 01:43:13 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3ADC0221.32127C39@DougBarton.net> Date: Tue, 17 Apr 2001 01:43:13 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > I'm figuring the only time when it may be a problem is on machines > with a small amount of memory. Since memory is cheap, I plan on > turning it on within the next couple of days unless a stability > issue comes up. > > I'll leave it to those people with low memory to remember to turn > it off. OK... this brings up the question of what other cool optimizations are there that may have been disabled in the past for reasons that are no longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file with commented out examples of configurations for various systems. For example, # For more modern systems that have a reasonable amount of RAM #vfs.vmiodirenable=1 # Low memory systems # Systems that need lots of randomness # Low resource systems that need less randomness # Super high performance TCP options for various situations .... etc. I'm sure y'all can come up with more. It might also be desirable to put these in etc/defautls/rc.conf, but I think something of this nature might be better suited in a freer format. Doug -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1:56:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by hub.freebsd.org (Postfix) with ESMTP id 4466437B43C for ; Tue, 17 Apr 2001 01:56:10 -0700 (PDT) (envelope-from ancient@outloud.org) Received: from surferboy.outloud.org (Goal@c205360-a.plano1.tx.home.com [24.14.88.149]) by mail.webjockey.net (8.11.3/8.11.3) with ESMTP id f3H8tuU94915 for ; Tue, 17 Apr 2001 04:55:56 -0400 (EDT) (envelope-from ancient@outloud.org) Message-Id: <5.1.0.12.2.20010417034728.00ad4d68@208.141.46.12> X-Sender: ancient@208.141.46.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1.0.12 (Beta) Date: Tue, 17 Apr 2001 03:47:50 -0500 To: freebsd-current@freebsd.org From: Storms of Perfection Subject: 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 subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 1:57:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 8B90337B43E for ; Tue, 17 Apr 2001 01:57:06 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3H8vSb49767; Tue, 17 Apr 2001 09:57:28 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3H8v1r61551; Tue, 17 Apr 2001 09:57:01 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104170857.f3H8v1r61551@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Doug Barton Cc: Alfred Perlstein , Matt Dillon , "'current@freebsd.org'" , brian@Awfulhak.org Subject: Re: sysctl optimisations (was: Filesystem gets a huge performance boost) In-Reply-To: Message from Doug Barton of "Tue, 17 Apr 2001 01:43:13 PDT." <3ADC0221.32127C39@DougBarton.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Apr 2001 09:57:01 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK... this brings up the question of what other cool optimizations are > there that may have been disabled in the past for reasons that are no > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > with commented out examples of configurations for various systems. For > example, > > # For more modern systems that have a reasonable amount of RAM > #vfs.vmiodirenable=1 > > # Low memory systems > > # Systems that need lots of randomness > > # Low resource systems that need less randomness > > # Super high performance TCP options for various situations > > .... etc. I'm sure y'all can come up with more. > > > It might also be desirable to put these in etc/defautls/rc.conf, but I > think something of this nature might be better suited in a freer format. I would have thought a bunch of comments in /etc/sysctl.conf would be sufficient. > Doug > -- > Perhaps the greatest damage the American system of education has done > to its children is to teach them that their opinions are relevant > simply because they are their opinions. > > Do YOU Yahoo!? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 4:54:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from cartier.cirx.org (cartier.cirx.org [211.72.15.243]) by hub.freebsd.org (Postfix) with ESMTP id 6D02A37B43F for ; Tue, 17 Apr 2001 04:54:10 -0700 (PDT) (envelope-from clive@CirX.ORG) Received: from cartier.cirx.org (nullmail@localhost [127.0.0.1]) by cartier.cirx.org (8.11.3/8.11.3) with SMTP id f3HBrDA71153; Tue, 17 Apr 2001 19:53:22 +0800 (CST) (envelope-from clive@CirX.ORG) Received: (nullmailer pid 71149 invoked by uid 1000); Tue, 17 Apr 2001 11:53:13 -0000 Date: Tue, 17 Apr 2001 19:53:13 +0800 From: Clive Lin To: Lars Eggert Cc: Michael Johnson , current@FreeBSD.ORG Subject: Re: ISO image available? Message-ID: <20010417195313.A70835@cartier.cirx.org> References: <3AD5D38F.E05083DB@isi.edu> <20010412121514.532abb29.ahze@ahze.net> <3AD5D5D2.5BAE0938@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD5D5D2.5BAE0938@isi.edu>; from larse@ISI.EDU on Thu, Apr 12, 2001 at 09:20:34AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for replying this topic, a little bit OT this time :-) On Thu, Apr 12, 2001 at 09:20:34AM -0700, Lars Eggert wrote: > Michael Johnson wrote: > > Theres not a iso for -CURRENT .. It changes too much. > > Too bad. > > > you can make your own iso though. ports/sysutils/mkisofs > > Yes, I've done that before for -stable, but it involves a make world :-) Relax, all you need is something like mirror/ncftp/lftp which could do recursive grabbing and, well, /usr/share/examples/worm/makecdfs.sh :-) sh /usr/share/examples/worm/makecdfs.sh would show a simple usage message. That's all. If you want a bootable iso (of course you want it), add a -b flag, which is only documented in the script itself :> > Grabbing an ISO from somewhere and quickly doing a CD install to test some > bugfixes would be much faster. (I'm not that interested in actively > tracking -current; I just want to be able to quickly run it whenever > someone asks for feedback on a change that'd affect our setup.) > > Isn't someone out there doing a nightly scripted make world? How about > doing a make release after? > > Lars I did make release before if I simply want a bootable and up-to-date iso image, but it costs too much time. :> IMHO, unless you want a customized, locally hacked cvs repository become a iso, you don't have to expend time on making release. Last time (2 days ago) I packed a releng_4 iso to install FreeBSD on an old box, which has no workable NIC, no usable floppy, only a 12X CDROM. The time consumes for make/burn the iso is around 10 minutes :-) -- pub 1024D/F8D2B472 2000-08-05 Clive Lin Key fingerprint = 7F9D 57A8 55C7 AA18 49B5 3820 570B 27F6 F8D2 B472 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 5:52:59 2001 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 C40FD37B42C; Tue, 17 Apr 2001 05:52:51 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA08133; Tue, 17 Apr 2001 22:52:28 +1000 Date: Tue, 17 Apr 2001 22:51:33 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Garrett Wollman Cc: "John W. De Boskey" , Current List Subject: Re: FIO* doc added to tty.4 (review) In-Reply-To: <200104170209.WAA02683@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Apr 2001, Garrett Wollman wrote: > < said: > > > I've been doing some tty related work and found the FIO* > > requests don't seem to be documented. > > > I've added some reasonable doc to tty.4 and put up the > > the diff and html forms: > > As the initial letter suggests, they are generic file ioctls and not > specific to the teletype driver. They should be described in the > ioctl(2) manual page. Most of them are best described by "deprecated; use the corresponding file [descriptor] operation in fcntl(2)". The main exceptions are: - FIONREAD: no other way to do this yet - FIODTYPE: no other way to do this yet - FIOGETLBA: not even a generic device ioctl; should never have been here Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 6:33:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 30DE837B423 for ; Tue, 17 Apr 2001 06:33:25 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3HDXIp50581 for current@FreeBSD.org; Tue, 17 Apr 2001 16:33:18 +0300 (EEST) (envelope-from ru) Date: Tue, 17 Apr 2001 16:33:18 +0300 From: Ruslan Ermilov To: current@FreeBSD.org Subject: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010417163318.A47398@sunbay.com> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! It is my great pleasure to announce the availability of just released Groff 1.17. Please refer to the src/contrib/groff/NEWS for details on what's new in this release. This release includes the complete re-implementation of the BSD mdoc(7) macro package, earlier referred to as -mdocNG. The new mdoc(7) manpage completely documents the package, thus replacing mdoc.samples(7). For now, mdoc.samples(7) is installed as MLINK to mdoc(7), but I will likely replace it with a short manpage referring to the mdoc(7). For a complete set of new features, please refer to the new mdoc(7). Note that this manpage could only be displayed with the new groff tools and new -mdoc package. FreeBSD-specific -mdoc configuration file is called mdoc.local. This version also provides a simple way to localize -mdoc. For now, only KOI8-R support is implemented. See gnu/usr.bin/groff/tmac/koi8-r for details. Below is the brief info on -mdoc from the NEWS file: : o The mdoc package has been completely rewritten, using the full power of : GNU troff to remove limitations of Unix troff (which is no longer : supported). Most important changes are: : : . No argument limit. : . Almost all macros are parsed and callable (if it makes sense). : . `.Lb': prints library names : . `.Nm ' now works as expected; `.Nm "" ' has : been withdrawn. : . Updated `.St' command : . `.Fx': prints FreeBSD : . `.Ox': prints OpenBSD : . `.Bsx': prints BSD/OS : . `.Brq', `.Bro', `.Brc': brace enclosure macros : . `.Bd -centered': center lines : . `.Bl -xwidth ': interpret and use the resulting width : . support for double-sided printing (-rD1 command line switch) : . support for 11pt and 12pt document sizes (-rS11, -rS12 command line : switches) : : `groff_mdoc.man' replaces `groff_mdoc.samples.man'; it now completely : documents the mdoc package. : : Great care has been taken to assure backwards compatibility. If you : encounter any abnormal results, please report them to bug-groff@gnu.org. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 6:38: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 63B3237B42C; Tue, 17 Apr 2001 06:37:57 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3HDbuN19619; Tue, 17 Apr 2001 17:37:56 +0400 (MSD) (envelope-from ache) Date: Tue, 17 Apr 2001 17:37:54 +0400 From: "Andrey A. Chernov" To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010417173754.A19540@nagual.pp.ru> References: <20010417163318.A47398@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010417163318.A47398@sunbay.com>; from ru@FreeBSD.ORG on Tue, Apr 17, 2001 at 04:33:18PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 17, 2001 at 16:33:18 +0300, Ruslan Ermilov wrote: > FreeBSD-specific -mdoc configuration file is called mdoc.local. This > version also provides a simple way to localize -mdoc. For now, only > KOI8-R support is implemented. See gnu/usr.bin/groff/tmac/koi8-r for > details. Is this message means that import is finished? :-) ISO-8859-1 support was implemented too, at least in old version. BTW, where Russian hyphentation now gone? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 6:43:36 2001 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 45C8137B43E; Tue, 17 Apr 2001 06:43:32 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3HDatf83966; Tue, 17 Apr 2001 09:36:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 17 Apr 2001 09:36:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported In-Reply-To: <20010417163318.A47398@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Ruslan Ermilov wrote: > It is my great pleasure to announce the availability of just released > Groff 1.17. Please refer to the src/contrib/groff/NEWS for details on > what's new in this release. This is great news -- especially the argument limit removal :-). Thanks for all your work on this; all these commits over the last half a year look like they were a serious time investment, and are much appreciated. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, 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 Tue Apr 17 6:54:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id DAA2F37B422; Tue, 17 Apr 2001 06:54:39 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14pVwD-0005fD-00; Tue, 17 Apr 2001 15:54:37 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id PAA13105; Tue, 17 Apr 2001 15:54:35 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 12771; Tue Apr 17 15:53:47 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14pVvP-00081E-00; Tue, 17 Apr 2001 15:53:47 +0200 To: Robert Watson Cc: Ruslan Ermilov , current@freebsd.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported In-reply-to: Your message of "Tue, 17 Apr 2001 09:36:55 -0400." Date: Tue, 17 Apr 2001 15:53:47 +0200 Message-ID: <30827.987515627@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001 09:36:55 -0400, Robert Watson wrote: > This is great news -- especially the argument limit removal :-). Indeed! If for nothing else, Ruslan's work will be much appreciated for the fact that we no longer have to jump through .Xo / .Xc hoops to get around the old argument limits. > all these commits over the last half a year look like they were a > serious time investment, and are much appreciated. As someone who cut his teeth on the crusty old mdoc that we had before, I resonate muchly with this sentiment. Even more exciting than what Ruslan has done to sort out the bugbears of the past, however, is the broadening of the horizons he has made feasible for the future. Ruslan, you da man! I'm pretty sure Mike Pritchard would agree that you're the new Mr mdoc. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 7: 4:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id E03F237B43F for ; Tue, 17 Apr 2001 07:04:45 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3HE4Js53358; Tue, 17 Apr 2001 17:04:19 +0300 (EEST) (envelope-from ru) Date: Tue, 17 Apr 2001 17:04:19 +0300 From: Ruslan Ermilov To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010417170419.C47398@sunbay.com> Mail-Followup-To: "Andrey A. Chernov" , current@FreeBSD.ORG References: <20010417163318.A47398@sunbay.com> <20010417173754.A19540@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010417173754.A19540@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Apr 17, 2001 at 05:37:54PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 17, 2001 at 05:37:54PM +0400, Andrey A. Chernov wrote: > On Tue, Apr 17, 2001 at 16:33:18 +0300, Ruslan Ermilov wrote: > > > FreeBSD-specific -mdoc configuration file is called mdoc.local. This > > version also provides a simple way to localize -mdoc. For now, only > > KOI8-R support is implemented. See gnu/usr.bin/groff/tmac/koi8-r for > > details. > > Is this message means that import is finished? :-) > Yes. > ISO-8859-1 support was implemented too, at least in old version. > Why do you think it is gone? I have asked for a repo-copy of all relevant files: contrib/groff/src/preproc/eqn/eqn/neqn.sh,v contrib/groff/src/roff/groff/groff/groff.man,v contrib/groff/src/devices/grotty/grotty/grotty.man,v contrib/groff/src/libs/libgroff/libgroff/cmap.cc,v contrib/groff/src/libs/libgroff/libgroff/cset.cc,v contrib/groff/src/libs/libgroff/libgroff/illegal.cc,v contrib/groff/src/roff/nroff/nroff/nroff.man,v contrib/groff/src/roff/nroff/nroff/nroff.sh,v > BTW, where Russian hyphentation now gone? > It was repo-copied to gnu/usr.bin/groff/tmac/hyphen.us-ru. In short: 1. All FreeBSD-specific contrib/ files were moved to gnu/ with repo-copy. 2. All FreeBSD modifications have either been incorporated by the vendor, or merged with the new release. Nothing got lost! Note: the KOI8-R locale support for -mdoc (gnu/usr.bin/groff/tmac/koi8-r) is still loaded and actived on -Tkoi8-r option to troff(1), but due to the difference in implementation (the current implementation simply redefines some -mdoc string variables), if you run ``nroff -mdoc'' for English manpage, and your LANG environment variable is set to ru_RU.KOI8-R, you will get the corrupted output. Setting -mdoc locale based on the type of the output device is bogus. I am about to introduce another way to set the -mdoc locale in the near future. For now, make sure you pass the correct groff(1) device to nroff(1) script, similar to how this is done in man(1). Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 7:13: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 5529037B43E; Tue, 17 Apr 2001 07:12:55 -0700 (PDT) (envelope-from nsayer@mailhost.kfu.com) Received: from morpheus.kfu.com (morpheus.kfu.com [205.178.90.226]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f3HECth10252; Tue, 17 Apr 2001 07:12:55 -0700 (PDT) (envelope-from nsayer@mailhost.kfu.com) From: Nick Sayer Received: (from nsayer@localhost) by morpheus.kfu.com (8.11.3/8.11.3) id f3HECs066784; Tue, 17 Apr 2001 07:12:54 -0700 (PDT) (envelope-from nsayer) Date: Tue, 17 Apr 2001 07:12:54 -0700 (PDT) Message-Id: <200104171412.f3HECs066784@morpheus.kfu.com> To: freebsd-stable@freebsd.org Subject: hid_report_size() prototype wrong in both -stable and -current Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The definition of hid_report_size() differs between -stable and -current (as to its prototype), yet /usr/src/sys/dev/usb.h shows no difference between -stable and -current, and is wrong in either case. This is causing some heartburn for -current builders of the xmame port. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 7:39:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6035537B422 for ; Tue, 17 Apr 2001 07:39:39 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3HEdbJ20755 for current@FreeBSD.ORG; Tue, 17 Apr 2001 18:39:37 +0400 (MSD) (envelope-from ache) Date: Tue, 17 Apr 2001 18:39:34 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010417183933.C20680@nagual.pp.ru> References: <20010417163318.A47398@sunbay.com> <20010417173754.A19540@nagual.pp.ru> <20010417170419.C47398@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010417170419.C47398@sunbay.com>; from ru@FreeBSD.ORG on Tue, Apr 17, 2001 at 05:04:19PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 17, 2001 at 17:04:19 +0300, Ruslan Ermilov wrote: > > > Why do you think it is gone? I base yourself on commit logs and miss repo copy. > difference in implementation (the current implementation simply redefines > some -mdoc string variables), if you run ``nroff -mdoc'' for English manpage, > and your LANG environment variable is set to ru_RU.KOI8-R, you will get the > corrupted output. This is unacceptable and must be fixed soon (LANG supposed to be always set for Russians, and requiring extra argument for nroff is very contr-intuitive in the light of the fact that old version works without it). -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 8:48:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 287A737B423; Tue, 17 Apr 2001 08:48:20 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3HFlgd64382; Tue, 17 Apr 2001 18:47:42 +0300 (EEST) (envelope-from ru) Date: Tue, 17 Apr 2001 18:47:42 +0300 From: Ruslan Ermilov To: "Andrey A. Chernov" Cc: i18n@FreeBSD.ORG, ru-cvs-all@FreeBSD.org.ua Subject: -mdoc localization support (was: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported) Message-ID: <20010417184742.A61775@sunbay.com> References: <20010417163318.A47398@sunbay.com> <20010417173754.A19540@nagual.pp.ru> <20010417170419.C47398@sunbay.com> <20010417183933.C20680@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010417183933.C20680@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Apr 17, 2001 at 06:39:34PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Redirected to -i18n] On Tue, Apr 17, 2001 at 06:39:34PM +0400, Andrey A. Chernov wrote: > On Tue, Apr 17, 2001 at 17:04:19 +0300, Ruslan Ermilov wrote: [...] > > > difference in implementation (the current implementation simply redefines > > some -mdoc string variables), if you run ``nroff -mdoc'' for English manpage, > > and your LANG environment variable is set to ru_RU.KOI8-R, you will get the > > corrupted output. > > This is unacceptable and must be fixed soon (LANG supposed to be always > set for Russians, and requiring extra argument for nroff is very > contr-intuitive in the light of the fact that old version works without > it). > Sure, just wanted to discuss the change first. :-) Here is the solution I can come up with right now. Every localized manpage should include one prologue line (similar to how this is done in calendar(1) files) that will set locale language to be used. For example, Russian manual pages would look like this: Index: apropos.1 =================================================================== RCS file: /home/rucvs/frdp/doc/ru_RU.KOI8-R/man/man1/apropos.1,v retrieving revision 1.2 diff -u -p -r1.2 apropos.1 --- apropos.1 2001/02/09 13:47:42 1.2 +++ apropos.1 2001/04/17 15:23:14 @@ -16,6 +16,7 @@ .\" $FreeBSDru: frdp/doc/ru_RU.KOI8-R/man/man1/apropos.1,v 1.2 2001/02/09 13:47:42 ru Exp $ .\" Original revision: 1.5.2.2 .\" +.ds lang ru_RU.KOI8-R .Dd 15 ÑÎ×ÁÒÑ 1991 .Dt APROPOS 1 .Os Then, mdoc.local script would load locale-specific file depending on the value of that variable: Index: mdoc.local =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/groff/tmac/mdoc.local,v retrieving revision 1.1 diff -u -p -r1.1 mdoc.local --- mdoc.local 2001/04/17 12:37:18 1.1 +++ mdoc.local 2001/04/17 15:35:37 @@ -58,5 +58,7 @@ .ds doc-operating-system FreeBSD\~5.0 . . -.\" KOI8-R locale support -.if "\*[.T]"koi8-r" .mso mdoc/koi8-r +.\" Locale support +.if d doc-lang \{\ +. if "\*[doc-lang]"ru_RU.KOI8-R" .mso mdoc/koi8-r +.\} Note that the "doc-" prefix is stripped when mdoc-local is installed. Does this looks acceptable to you? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 9:16: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with SMTP id A074B37B422 for ; Tue, 17 Apr 2001 09:16:07 -0700 (PDT) (envelope-from tomdean@speakeasy.org) Received: (qmail 94146 invoked from network); 17 Apr 2001 16:16:07 -0000 Received: from unknown (HELO celebris.tddhome) ([64.81.20.229]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 17 Apr 2001 16:16:07 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.3/8.11.1) id f3HGG6J33776; Tue, 17 Apr 2001 09:16:06 -0700 (PDT) (envelope-from tomdean@speakeasy.org) Date: Tue, 17 Apr 2001 09:16:06 -0700 (PDT) Message-Id: <200104171616.f3HGG6J33776@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: freebsd-current@freebsd.org Subject: etc/* in pending release Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am planning to shift a machine from -current to the pending release. I have tracked -current (SMP) on this machine for > 4 years. But, now, I need to depend on it - it is old, making a net server. What date were the etc/* files frozen for the pending release? I plan to do a new install, just preserve the configuration files. tomdean # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Thu Apr 12 19:30:44 PDT 2001 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 10:17:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id D9B7237B422; Tue, 17 Apr 2001 10:17:04 -0700 (PDT) (envelope-from n_hibma@FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.11.3/8.11.3) with ESMTP id f3HHGtr85291; Tue, 17 Apr 2001 18:16:55 +0100 (BST) (envelope-from n_hibma@FreeBSD.ORG) Date: Tue, 17 Apr 2001 18:16:55 +0100 (BST) From: X-X-Sender: To: Nick Sayer Cc: , Subject: Re: hid_report_size() prototype wrong in both -stable and -current In-Reply-To: <200104171412.f3HECs066784@morpheus.kfu.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 usb.h != libusb.h NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. The prototypes are correct as is. The changes to libusb made in CURRENT have not been backported to STABLE (yet). Nick On Tue, 17 Apr 2001, Nick Sayer wrote: > > The definition of hid_report_size() differs between -stable and -current (as > to its prototype), yet /usr/src/sys/dev/usb.h shows no difference between > -stable and -current, and is wrong in either case. > > This is causing some heartburn for -current builders of the xmame port. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- The USB for FreeBSD project. n_hibma@FreeBSD.ORG http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 10:23: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B199837B43E for ; Tue, 17 Apr 2001 10:22:57 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HHMpt94518; Tue, 17 Apr 2001 10:22:51 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 10:22:51 -0700 (PDT) From: Matt Dillon Message-Id: <200104171722.f3HHMpt94518@earth.backplane.com> To: Alfred Perlstein Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :* Matt Dillon [010415 23:16] wrote: :> :> For example, all this work on a preemptive :> kernel is just insane. Our entire kernel is built on the concept of :> not being preemptable except by interrupts. We virtually guarentee :> years of instability and bugs leaking out of the woodwork by trying to :> make it preemptable, and the performance gain we get for that pain :> is going to be zilch. Nada. Nothing. : :Pre-emption is mearly a side effect of a mutex'd kernel. : :The actual gains are in terms of parallel execution internally. :Meaning if we happen to copyin() a 4 meg buffer we can allow more :than one process to be completing some sort of work inside the :kernel other than spinning on the giant lock. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Switching-away while obtaining giant lock isn't a big deal, and not really 'preemption'. Switching a task out in the middle of some random piece of code is preemption and our system isn't designed to handle it. By trying to implement it, you are virtually guarenteed to introduce hundreds of bugs that will take years to find and fix. My understanding of the original BSDI code was that an interrupt could preempt the current process, but on completion (or if the interrupt blocked) the current process would resume on the same cpu... that is, the BSDI system only preempted for interrupts, which our codebase can accomodate just fine. I can see us doing some fancy process switching to avoid spinning on the giant lock. But I can't see us reliably preempting a process sitting in some random piece of kernel code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 10:25: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A19B937B424 for ; Tue, 17 Apr 2001 10:24:56 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HHOqh94775; Tue, 17 Apr 2001 10:24:52 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 10:24:52 -0700 (PDT) From: Matt Dillon Message-Id: <200104171724.f3HHOqh94775@earth.backplane.com> To: Doug Barton Cc: "Justin T. Gibbs" , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matt Dillon wrote: : :> It is not implying that at all. There is no black and white here. :> This is a case where spending a huge amount of time and complexity :> to get the efficiency down to the Nth degree is nothing but a waste :> of time. What matters is what the user sees, what performance :> the application gets, and how many bugs you introduce when optimizing :> something that might not need optimizing. : : Sooo..... sounds like making "on" the default in -current is a worthy :experiment? : :Doug :-- Testing it 'on' in stable on production systems and observing the relative change in performance is a worthy experiment. Testing it 'on' in current is just an experiment. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:16:13 2001 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 75CD137B422; Tue, 17 Apr 2001 11:16:07 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id CFB9F5D60; Tue, 17 Apr 2001 20:16:38 +0200 (CEST) Date: Tue, 17 Apr 2001 20:16:38 +0200 From: Jesper Skriver To: John Baldwin Cc: current@FreeBSD.org Subject: Re: kernel panic in -current, ithread or newcard related ? Message-ID: <20010417201638.A23027@skriver.dk> References: <20010415172142.A27168@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Apr 16, 2001 at 08:10:37PM -0700 X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 08:10:37PM -0700, John Baldwin wrote: > > On 15-Apr-01 Jesper Skriver wrote: > > About every other time I boot my IBM ThinkPad 600E I get this panic > > (hand typed, as I don't have a second machine here to be able to use a > > serial console). > > > > Fatal trap 12: page fault while in kernel mode > > Fault virtual address = 0x28 > > It's a null pointer dereference. If you've compiled a debug kernel then do > 'gdb -k /usr/obj/usr/src/sys/TAM2/kernel.debug' and then do > 'l *csa_readio+0x17' to find the offending line. It's usually pretty easy to > figure out then. I's not obvious to me, newbee in kernel debugging, how is the below (from the trace) related ? /Jesper (kgdb) l *csa_readio+0x17 0xc0159cd3 is in csa_readio (machine/bus_at386.h:205). 200 } 201 202 static __inline u_int32_t 203 bus_space_read_4(bus_space_tag_t tag, bus_space_handle_t handle, 204 bus_size_t offset) 205 { 206 #if defined(_I386_BUS_PIO_H_) 207 #if defined(_I386_BUS_MEMIO_H_) 208 if (tag == I386_BUS_SPACE_IO) 209 #endif (kgdb) l *csa_intr+0x14 0xc015a5ec is in csa_intr (/usr/src/sys/dev/sound/pci/csapcm.c:685). 680 csa_intr (void *p) 681 { 682 struct csa_info *csa = p; 683 684 if ((csa->binfo->hisr & HISR_VC0) != 0) 685 chn_intr(csa->pch.channel); 686 if ((csa->binfo->hisr & HISR_VC1) != 0) 687 chn_intr(csa->rch.channel); 688 } 689 (kgdb) l *ithread_loop+0x23f 0xc018e077 is in ithread_loop (/usr/src/sys/kern/kern_intr.c:518). 513 free(ih, M_ITHREAD); 514 mtx_unlock(&Giant); 515 goto restart; 516 } 517 ih->ih_handler(ih->ih_argument); 518 if ((ih->ih_flags & IH_MPSAFE) == 0) 519 mtx_unlock(&Giant); 520 } 521 } 522 (kgdb) l *fork_exit+0x59 0xc018d221 is in fork_exit (/usr/src/sys/kern/kern_fork.c:737). 732 733 /* 734 * Check if a kernel thread misbehaved and returned from its main 735 * function. 736 */ 737 PROC_LOCK(p); 738 if (p->p_flag & P_KTHREAD) { 739 PROC_UNLOCK(p); 740 mtx_lock(&Giant); 741 printf("Kernel thread \"%s\" (pid %d) exited prematurely.\n", (kgdb) l *fork_trampoline+0x8 No source file for address 0xc0299f6c. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:18:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 4C60437B622 for ; Tue, 17 Apr 2001 11:18:05 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA13546; Tue, 17 Apr 2001 14:17:38 -0400 (EDT) (envelope-from wollman) Date: Tue, 17 Apr 2001 14:17:38 -0400 (EDT) From: Garrett Wollman Message-Id: <200104171817.OAA13546@khavrinen.lcs.mit.edu> To: "John W. De Boskey" Cc: Current List Subject: Re: FIO* doc added to tty.4 (review) In-Reply-To: <20010417033805.A40658@bsdwins.com> References: <20010415222637.A507@FreeBSD.org> <200104170209.WAA02683@khavrinen.lcs.mit.edu> <20010417033805.A40658@bsdwins.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > ie: FIONREAD will succeed from a backgrounded process, but the > data read itself with hang (tty driver). You are describing a general property of the terminal subsystem, which any process dealing with terminals needs to be aware of. (AFAIK, ioctl(tty, FIONREAD, &n) should set n to zero if the process is in the background; if it does not that's probably a bug.) The new POSIX revision group discussed this briefly in the mailing-list, but the group did not want to innovate in this area. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:25:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C741237B42C; Tue, 17 Apr 2001 11:25:30 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3HIPNG12925; Tue, 17 Apr 2001 11:25:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010417201638.A23027@skriver.dk> Date: Tue, 17 Apr 2001 11:24:46 -0700 (PDT) From: John Baldwin To: Jesper Skriver Subject: Re: kernel panic in -current, ithread or newcard related ? Cc: current@FreeBSD.org, cg@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Apr-01 Jesper Skriver wrote: > On Mon, Apr 16, 2001 at 08:10:37PM -0700, John Baldwin wrote: >> >> On 15-Apr-01 Jesper Skriver wrote: >> > About every other time I boot my IBM ThinkPad 600E I get this panic >> > (hand typed, as I don't have a second machine here to be able to use a >> > serial console). >> > >> > Fatal trap 12: page fault while in kernel mode >> > Fault virtual address = 0x28 >> >> It's a null pointer dereference. If you've compiled a debug kernel then do >> 'gdb -k /usr/obj/usr/src/sys/TAM2/kernel.debug' and then do >> 'l *csa_readio+0x17' to find the offending line. It's usually pretty easy >> to >> figure out then. > > I's not obvious to me, newbee in kernel debugging, how is the below > (from the trace) related ? > > /Jesper > > (kgdb) l *csa_readio+0x17 > 0xc0159cd3 is in csa_readio (machine/bus_at386.h:205). > 200 } > 201 > 202 static __inline u_int32_t > 203 bus_space_read_4(bus_space_tag_t tag, bus_space_handle_t handle, > 204 bus_size_t offset) > 205 { > 206 #if defined(_I386_BUS_PIO_H_) > 207 #if defined(_I386_BUS_MEMIO_H_) > 208 if (tag == I386_BUS_SPACE_IO) > 209 #endif Hmm, well, looking in dev/sound/pci/csa.c at the csa_readio() function, bus_space_read_4() is called once: if (offset < BA0_AC97_RESET) return bus_space_read_4(rman_get_bustag(resp->io), rman_get_bush andle(resp->io), offset) & 0xffffffff; else { if (csa_readcodec(resp, offset, &ul)) ul = 0; return (ul); } My guess is that resp is NULL here. At this point, you may want to poke Cameron Grant with a bug report as he is Mr. Sound and he probably knows what has gone wrong at this point. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Apr 17 11:30:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from reuben.meganet.net (reuben.meganet.net [209.213.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 42CB237B423 for ; Tue, 17 Apr 2001 11:30:31 -0700 (PDT) (envelope-from estair@computer-exchange.com) Received: from proxy (dial-tnt01-p2-086.bos.ma.meganet.net [209.213.73.86]) by reuben.meganet.net (8.9.3/8.9.1-BW0200.01SP) with SMTP id OAA21059 for ; Tue, 17 Apr 2001 14:30:35 -0400 From: estair@computer-exchange.com Message-ID: <002a01c0c76c$a4fe52a0$4900a8c0@mshome.net> To: Subject: mount_smbfs missing, SAMBA package installed, where is it? Date: Tue, 17 Apr 2001 14:31:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 5.0-Current-4.12.2001, X-Kern-Developer with all binaries, have just installed the samba package (pkg_add -r samba) but the smb client services, specifically mount_smbfs, aren't installed. I cannot find reference anywhere to which package the mount_smbfs binary belongs to. Can anyone point me in the right direction? Thanks, Eli Stair To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:39:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 6AD9537B423; Tue, 17 Apr 2001 11:39:41 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f3HIdfh35307; Tue, 17 Apr 2001 11:39:41 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) From: Nick Sayer Received: from kfu.com (localhost [127.0.0.1]) by medusa.kfu.com (8.11.3/8.11.3) with SMTP id f3HIdeY18450; Tue, 17 Apr 2001 11:39:40 -0700 (PDT) (envelope-from nsayer@kfu.com) Received: from 207.5.33.65 (SquirrelMail authenticated user nsayer) by medusa.kfu.com with HTTP; Tue, 17 Apr 2001 11:39:40 -0700 (PDT) Message-ID: <1087.207.5.33.65.987532780.squirrel@medusa.kfu.com> Date: Tue, 17 Apr 2001 11:39:40 -0700 (PDT) Subject: Re: hid_report_size() prototype wrong in both -stable and -current To: n_hibma@FreeBSD.ORG In-Reply-To: References: Cc: nsayer@quack.kfu.com, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: SquirrelMail (version 1.0.4) 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 > > usb.h != libusb.h > > NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. Ok. That's as may be, but then why are there prototypes for libusb calls in dev/usb.h? > > The prototypes are correct as is. They may be in libusb.h, but the prototype for that function in sys/dev/usb.h is mysterious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:42:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 9A01237B43F; Tue, 17 Apr 2001 11:42:11 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f3HIgBh35329; Tue, 17 Apr 2001 11:42:11 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) From: Nick Sayer Received: from kfu.com (localhost [127.0.0.1]) by medusa.kfu.com (8.11.3/8.11.3) with SMTP id f3HIgAY18546; Tue, 17 Apr 2001 11:42:11 -0700 (PDT) (envelope-from nsayer@kfu.com) Received: from 207.5.33.65 (SquirrelMail authenticated user nsayer) by medusa.kfu.com with HTTP; Tue, 17 Apr 2001 11:42:11 -0700 (PDT) Message-ID: <1093.207.5.33.65.987532931.squirrel@medusa.kfu.com> Date: Tue, 17 Apr 2001 11:42:11 -0700 (PDT) Subject: Re: hid_report_size() prototype wrong in both -stable and -current To: nsayer@quack.kfu.com In-Reply-To: <1087.207.5.33.65.987532780.squirrel@medusa.kfu.com> References: <1087.207.5.33.65.987532780.squirrel@medusa.kfu.com> Cc: n_hibma@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: SquirrelMail (version 1.0.4) 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 >> >> usb.h != libusb.h >> >> NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. > > Ok. That's as may be, but then why are there prototypes for libusb > calls in dev/usb.h? Sorry, meant to say /usr/include/dev/usb/hid.h > >> >> The prototypes are correct as is. > > They may be in libusb.h, but the prototype for that function in >sys/dev/usb.h is mysterious. /usr/include/dev/usb/hid.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 11:43: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id 86D6F37B43F for ; Tue, 17 Apr 2001 11:42:58 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 05AD066B38; Tue, 17 Apr 2001 11:42:57 -0700 (PDT) Date: Tue, 17 Apr 2001 11:42:57 -0700 From: Kris Kennaway To: estair@computer-exchange.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: mount_smbfs missing, SAMBA package installed, where is it? Message-ID: <20010417114257.A3630@xor.obsecurity.org> References: <002a01c0c76c$a4fe52a0$4900a8c0@mshome.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002a01c0c76c$a4fe52a0$4900a8c0@mshome.net>; from estair@computer-exchange.com on Tue, Apr 17, 2001 at 02:31:38PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 17, 2001 at 02:31:38PM -0400, estair@computer-exchange.com wrot= e: > I'm running 5.0-Current-4.12.2001, X-Kern-Developer with all binaries, > have just installed the samba package (pkg_add -r samba) but the smb > client services, specifically mount_smbfs, aren't installed. =20 >=20 > I cannot find reference anywhere to which package the mount_smbfs binary > belongs to. Can anyone point me in the right direction? The smbfs package? Part of smbfs was just imported into -current, but I don't think the mount utility was yet. Kris P.S. This question belongs on -questions or -ports, it's nothing to do with 5.0-CURRENT. --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE63I6xWry0BWjoQKURAnWqAKC9hqtVUADc62LWjAv7ouegcklJ7QCgph4r 86gRyJGF6x/KqjNf614BUO0= =mM/K -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 12:35:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0CD3D37B424 for ; Tue, 17 Apr 2001 12:35:22 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3HJZGG15692 for ; Tue, 17 Apr 2001 12:35:16 -0700 (PDT) (envelope-from john@baldwin.cx) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 17 Apr 2001 12:34:39 -0700 (PDT) From: John Baldwin To: current@FreeBSD.org Subject: FW: Snapshot Log - current broke Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----FW: <200104171550.f3HFoZH70998@deimos.osd.bsdi.com>----- Date: Tue, 17 Apr 2001 08:50:35 -0700 (PDT) From: Deimos Root To: jhb@osd.bsdi.com Subject: Snapshot Log rm -f vt220l.816 uudecode /usr/src/usr.sbin/pcvt/fonts/vt220l.814.uu uudecode /usr/src/usr.sbin/pcvt/fonts/vt220l.810.uu uudecode /usr/src/usr.sbin/pcvt/fonts/vt220l.816.uu ===> usr.sbin/pcvt/kcon cc -O -pipe -I/usr/src/usr.sbin/pcvt/kcon/../keycap -DKEYB_DEVICE=\"/dev/ttyv0\" -I/usr/obj/usr/src/i386/usr/include -c /usr /src/usr.sbin/pcvt/kcon/kcon.c gzip -cn /usr/src/usr.sbin/pcvt/kcon/kcon.1 > kcon.1.gz cc -O -pipe -I/usr/src/usr.sbin/pcvt/kcon/../keycap -DKEYB_DEVICE=\"/dev/ttyv0\" -I/usr/obj/usr/src/i386/usr/include -o kco n kcon.o /usr/obj/usr/src/usr.sbin/pcvt/kcon/../keycap/libkeycap.a ===> usr.sbin/pcvt/loadfont cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pcvt/loadfont/loadfont.c gzip -cn /usr/src/usr.sbin/pcvt/loadfont/loadfont.1 > loadfont.1.gz cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o loadfont loadfont.o ===> usr.sbin/pcvt/scon cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pcvt/scon/scon.c gzip -cn /usr/src/usr.sbin/pcvt/scon/scon.1 > scon.1.gz cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o scon scon.o ===> usr.sbin/pcvt/userkeys cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pcvt/userkeys/vt220keys.c gzip -cn /usr/src/usr.sbin/pcvt/userkeys/vt220keys.1 > vt220keys.1.gz cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o vt220keys vt220keys.o ===> usr.sbin/pcvt/vttest cc -O -pipe -traditional -DUSEMYSTTY -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pcvt/vttest/main.c cc -O -pipe -traditional -DUSEMYSTTY -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pcvt/vttest/esc.c gzip -cn /usr/src/usr.sbin/pcvt/vttest/vttest.1 > vttest.1.gz In file included from /usr/src/usr.sbin/pcvt/vttest/header.h:26, from /usr/src/usr.sbin/pcvt/vttest/esc.c:1: /usr/obj/usr/src/i386/usr/include/stdio.h:302: syntax error before `char' In file included from /usr/src/usr.sbin/pcvt/vttest/header.h:26, from /usr/src/usr.sbin/pcvt/vttest/main.c:20: /usr/obj/usr/src/i386/usr/include/stdio.h:302: syntax error before `char' *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Stop in /usr/src/release. ---------------------------------------- release started at 06:00:00 on 04/17/01 release died at 08:50:35 on 04/17/01 ---------------------------------------- --------------End of forwarded message------------------------- -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Apr 17 13: 2:27 2001 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 A658837B43E for ; Tue, 17 Apr 2001 13:02:13 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HK2A222352; Tue, 17 Apr 2001 13:02:10 -0700 (PDT) Date: Tue, 17 Apr 2001 13:02:10 -0700 From: Alfred Perlstein To: Matt Dillon Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417130210.K976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104171722.f3HHMpt94518@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 10:22:51AM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010417 10:22] wrote: > > :* Matt Dillon [010415 23:16] wrote: > :> > :> For example, all this work on a preemptive > :> kernel is just insane. Our entire kernel is built on the concept of > :> not being preemptable except by interrupts. We virtually guarentee > :> years of instability and bugs leaking out of the woodwork by trying to > :> make it preemptable, and the performance gain we get for that pain > :> is going to be zilch. Nada. Nothing. > : > :Pre-emption is mearly a side effect of a mutex'd kernel. > : > :The actual gains are in terms of parallel execution internally. > :Meaning if we happen to copyin() a 4 meg buffer we can allow more > :than one process to be completing some sort of work inside the > :kernel other than spinning on the giant lock. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > Switching-away while obtaining giant lock isn't a big deal, and > not really 'preemption'. Switching a task out in the middle of > some random piece of code is preemption and our system isn't designed > to handle it. By trying to implement it, you are virtually guarenteed > to introduce hundreds of bugs that will take years to find and fix. > > My understanding of the original BSDI code was that an interrupt could > preempt the current process, but on completion (or if the interrupt > blocked) the current process would resume on the same cpu... that > is, the BSDI system only preempted for interrupts, which our > codebase can accomodate just fine. > > I can see us doing some fancy process switching to avoid spinning on > the giant lock. But I can't see us reliably preempting a process sitting > in some random piece of kernel code. There's actually very little code that non-premptable once we get the kernel mutexed. The least complex way to accomplish this is to only preempt kernel processes that hold no mutex (low level) locks. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:16:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 64D0537B423; Tue, 17 Apr 2001 13:16:52 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id NAA08915; Tue, 17 Apr 2001 13:16:47 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp05.primenet.com, id smtpdAAAaJaGyr; Tue Apr 17 13:16:42 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id NAA27566; Tue, 17 Apr 2001 13:17:02 -0700 (MST) From: Terry Lambert Message-Id: <200104172017.NAA27566@usr09.primenet.com> Subject: Very Bad Bug: current, 4.2, 4.3 To: current@freebsd.org Date: Tue, 17 Apr 2001 20:16:57 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I mentioned a very bad bug on the -arch list a while back, which occurred when To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:30:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 51E1537B43C; Tue, 17 Apr 2001 13:30:09 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3HKU1A86600; Tue, 17 Apr 2001 13:30:01 -0700 (PDT) Date: Tue, 17 Apr 2001 13:30:01 -0700 (PDT) From: David Wolfskill Message-Id: <200104172030.f3HKU1A86600@bunrab.catwhisker.org> To: current@FreeBSD.ORG, john@baldwin.cx Subject: Re: FW: Snapshot Log - current broke Cc: kris@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 17 Apr 2001 12:34:39 -0700 (PDT) >From: John Baldwin >.... >===> usr.sbin/pcvt/vttest >cc -O -pipe -traditional -DUSEMYSTTY -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/usr.sbin/pcvt/vttest/main.c >cc -O -pipe -traditional -DUSEMYSTTY -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/usr.sbin/pcvt/vttest/esc.c >gzip -cn /usr/src/usr.sbin/pcvt/vttest/vttest.1 > vttest.1.gz >In file included from /usr/src/usr.sbin/pcvt/vttest/header.h:26, > from /usr/src/usr.sbin/pcvt/vttest/esc.c:1: >/usr/obj/usr/src/i386/usr/include/stdio.h:302: syntax error before `char' >In file included from /usr/src/usr.sbin/pcvt/vttest/header.h:26, > from /usr/src/usr.sbin/pcvt/vttest/main.c:20: >/usr/obj/usr/src/i386/usr/include/stdio.h:302: syntax error before `char' >*** Error code 1 >*** Error code 1 >2 errors >... Whacking src/include/stdio.h thus: Index: include/stdio.h =================================================================== RCS file: /cvs/freebsd/src/include/stdio.h,v retrieving revision 1.32 diff -u -u -r1.32 stdio.h --- include/stdio.h 2001/04/17 07:59:52 1.32 +++ include/stdio.h 2001/04/17 17:54:57 @@ -299,7 +299,7 @@ __BEGIN_DECLS int asprintf __P((char **, const char *, ...)) __printflike(2, 3); char *ctermid_r __P((char *)); -const char *fmtcheck __P((const char *, const char *)) +__const char *fmtcheck __P((const char *, const char *)) __attribute__((__format_arg__(2))); char *fgetLn __P((FILE *, size_t *)); int fpurge __P((FILE *)); has allowed the "make buildworld" to succeed for me. Building the kernel as I type; above was hand-transcribed (machine is not networked at the moment). Use at your own risk; void where prohibited, etc.... Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:37:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 682CB37B43F; Tue, 17 Apr 2001 13:37:32 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id NAA17079; Tue, 17 Apr 2001 13:35:57 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpdAAAZraadH; Tue Apr 17 13:35:39 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id NAA27919; Tue, 17 Apr 2001 13:37:32 -0700 (MST) From: Terry Lambert Message-Id: <200104172037.NAA27919@usr09.primenet.com> Subject: BAD BUG: Second try To: current@freeBSD.org Date: Tue, 17 Apr 2001 20:37:32 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] 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 Oops. NOTE: I don't follow this lists for weeks at a time, so please include me directly in any responses. Thanks. Matt Dillon was looking at this, but I haven't heard from him for a while on it. Here is a patch to make it panic, instead of really, really trashing memory (ignore the version, I'm using a vendor import locally); the patch is to "crfree() and should be obvious: =================================================================== diff -c -r1.2 kern_prot.c *** kern/kern_prot.c 2001/03/21 02:33:03 1.2 --- kern/kern_prot.c 2001/04/17 02:22:48 *************** *** 1001,1006 **** --- 1001,1009 ---- int s; s = splhigh(); + if ( cr->cr_ref == 0) { + panic("Freeing already free credential!\n"); + } if (--cr->cr_ref == 0) { /* * Some callers of crget(), such as nfs_statfs(), =================================================================== Unfortunately, There's also a nameidata structure (it's the only data structure that's exactly 72 bytes long, which I was able to determine by printing sizeof() information for all kernel structures, and gre'ping for "72") getting freed and then either continued to be used, or being used as a result of an unchecked allocation failure (I'm still looking for that one). Basically, the second causes invariants to whine about data modified on the freelist to my console, while the first one results in an eventual panic dues to spammed memory (for the obvious reason that you can't free the same thing twice). The problems only become obvious when you open and then close around 30,000 TCP connections; sometimes it takes a couple of tries before it panics your machine. I have some programs that demonstrate the bug, if anyone is interested in repeating it on their machines locally (you will need appropriate open file limits and bump up to 40,000 or so net.inet.ip.portrange.last, e.g.: sysctl -w net.inet.ip.portrange.last=45000 Which means your box will need about a gig of memory. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:42: 3 2001 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 DE75737B42C for ; Tue, 17 Apr 2001 13:41:59 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA32605; Wed, 18 Apr 2001 06:41:33 +1000 Date: Wed, 18 Apr 2001 06:40:38 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Garrett Wollman Cc: "John W. De Boskey" , Current List Subject: Re: FIO* doc added to tty.4 (review) In-Reply-To: <200104171817.OAA13546@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Garrett Wollman wrote: > < said: > > > ie: FIONREAD will succeed from a backgrounded process, but the > > data read itself with hang (tty driver). > > You are describing a general property of the terminal subsystem, which > any process dealing with terminals needs to be aware of. > > (AFAIK, ioctl(tty, FIONREAD, &n) should set n to zero if the process > is in the background; if it does not that's probably a bug.) It doesn't. However, applications should be prepared to deal with there being no readable data. Success of FIONREAD doesn't guarantee non-blocking of a blocking read in general -- the data may have been read by another process, or there may not be enough data to satisfy the programmed MIN/TIME requirements. > The new POSIX revision group discussed this briefly in the > mailing-list, but the group did not want to innovate in this area. select() and poll() would give the same false positive as FIONREAD, and probably doesn't handle MIN/TIME right. Does POSIX now specify select() and/or poll() precisely enough to show that the current behaviour is wrong? Related bug: ttioctl() doesn't understand all driver ioctls well enough to know which ones should wait until the progress is in the foreground; drivers know even less about background processes. So background processes an do some ioctls that change the device state underneath forground processes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:51:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 19DEE37B440 for ; Tue, 17 Apr 2001 13:51:15 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HKpAF06881; Tue, 17 Apr 2001 13:51:10 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 13:51:10 -0700 (PDT) From: Matt Dillon Message-Id: <200104172051.f3HKpAF06881@earth.backplane.com> To: Alfred Perlstein Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :There's actually very little code that non-premptable once we get the :kernel mutexed. The least complex way to accomplish this is to only :preempt kernel processes that hold no mutex (low level) locks. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] I wish it were that simple. Remember when we went to shared file descriptor arrays for processes? Half a dozen serious bugs were introduced into the kernel from that change which weren't fixed for over a year and half. And that was *WITH* a Giant lock left intact. A change to a single subsystem introduced 6+ serious bugs. Now you guys are introducing preemptive kernel scheduling and expect it will be a walk in the park? I expect it will introduce so many bugs that the system will be destabilized for over a year, because that sort of thing effects every single subsystem rather then just one or two. It is not going to be as simple as throwing mutexes around every little piece of code that might access shared state somewhere. How many mutex calls are we going to wind up making to implement the simplest system call now? How much overhead are we going to introduce to support a feature that isn't going to add one iota of performance to the system? An incredible number of very cool optimizations can be made when you have the ability to assume that the cpu you are running under will not get ripped out from under you. Things like per-cpu caching - not only of mbufs or memory, but of other things as well. Simple access to per-cpu globals now must suddenly be done with compare-exchange or otherwise be required to use atomic instructions. None of the current per-cpu variable handling code assumes that. It's just not a good idea. Do you want people to adopt -current when it becomes 5.0? It isn't going to happen if preemptive kernel scheduling is in there. I am going to wind up having to support 4.x for the next two years before 5.x becomes reliable enough to use in a production environment. Or, worse, -current is going to move down a path of no-return (becoming so unreliable that it will not be adopted by anyone) and we are going to wind up having to scrap the whole damn thing! I was somewhat skeptical about BSDI's interrupt-as-thread methodology, but at least they didn't bite of more then they could chew when they implemented it. Trying to extend that model to the Nth degree is creating a huge mess -- and for what? Just to support interrupts as threads? It isn't worth it. I would much rather see us changing the interrupt model to be less invasive, thus allowing interrupts to run unhindered as interrupts rather then threads, rather then see this preemptive kernel scheduling stuff go in. I love SMP, but I love stability more. BSDI focused on the things that actually effected performance. -current is not focused at all and is going off the deep end.. trying to do things that would be interesting work for 5.2 or 5.3 but just plain should not be in 5.0. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:53:42 2001 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 ECFF337B424 for ; Tue, 17 Apr 2001 13:53:38 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HKraX24197; Tue, 17 Apr 2001 13:53:36 -0700 (PDT) Date: Tue, 17 Apr 2001 13:53:36 -0700 From: Alfred Perlstein To: Matt Dillon Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417135336.Q976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104172051.f3HKpAF06881@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 01:51:10PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need to settle dude, pre-emption isn't a goal, it's mearly a _possible_ side effect. We're not aiming for pre-emption, we're aiming for more concurrancy. * Matt Dillon [010417 13:51] wrote: > : > :There's actually very little code that non-premptable once we get the > :kernel mutexed. The least complex way to accomplish this is to only > :preempt kernel processes that hold no mutex (low level) locks. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > I wish it were that simple. Remember when we went to shared file > descriptor arrays for processes? Half a dozen serious bugs were > introduced into the kernel from that change which weren't fixed for > over a year and half. And that was *WITH* a Giant lock left intact. > A change to a single subsystem introduced 6+ serious bugs. > > Now you guys are introducing preemptive kernel scheduling and expect > it will be a walk in the park? I expect it will introduce so many bugs > that the system will be destabilized for over a year, because that sort > of thing effects every single subsystem rather then just one or two. > > It is not going to be as simple as throwing mutexes around every little > piece of code that might access shared state somewhere. How many > mutex calls are we going to wind up making to implement the simplest > system call now? How much overhead are we going to introduce to support > a feature that isn't going to add one iota of performance to the system? > > An incredible number of very cool optimizations can be made when you > have the ability to assume that the cpu you are running under will not > get ripped out from under you. Things like per-cpu caching - not only > of mbufs or memory, but of other things as well. Simple access to > per-cpu globals now must suddenly be done with compare-exchange or > otherwise be required to use atomic instructions. None of the current > per-cpu variable handling code assumes that. > > It's just not a good idea. Do you want people to adopt -current when it > becomes 5.0? It isn't going to happen if preemptive kernel scheduling > is in there. I am going to wind up having to support 4.x for the next > two years before 5.x becomes reliable enough to use in a production > environment. Or, worse, -current is going to move down a path of > no-return (becoming so unreliable that it will not be adopted by anyone) > and we are going to wind up having to scrap the whole damn thing! > > I was somewhat skeptical about BSDI's interrupt-as-thread methodology, > but at least they didn't bite of more then they could chew when they > implemented it. Trying to extend that model to the Nth degree is > creating a huge mess -- and for what? Just to support interrupts as > threads? It isn't worth it. > > I would much rather see us changing the interrupt model to be less > invasive, thus allowing interrupts to run unhindered as interrupts > rather then threads, rather then see this preemptive kernel scheduling > stuff go in. I love SMP, but I love stability more. BSDI focused on > the things that actually effected performance. -current is not focused > at all and is going off the deep end.. trying to do things that would > be interesting work for 5.2 or 5.3 but just plain should not be in 5.0. > > -Matt -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 13:54:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id A50D737B42C; Tue, 17 Apr 2001 13:54:28 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E855C66B38; Tue, 17 Apr 2001 13:54:27 -0700 (PDT) Date: Tue, 17 Apr 2001 13:54:27 -0700 From: Kris Kennaway To: David Wolfskill Cc: current@FreeBSD.ORG, john@baldwin.cx, kris@FreeBSD.ORG Subject: Re: FW: Snapshot Log - current broke Message-ID: <20010417135427.A12600@xor.obsecurity.org> References: <200104172030.f3HKU1A86600@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104172030.f3HKU1A86600@bunrab.catwhisker.org>; from david@catwhisker.org on Tue, Apr 17, 2001 at 01:30:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I committed this earlier..thanks. Kris --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE63K2DWry0BWjoQKURArkVAJwM6aL42cwLUBl2mJb8tjYVXxkXwACgz3QW WDwO+yOsVYiG2pROykmKW8U= =Ue+p -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 14: 7:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 64F6637B423 for ; Tue, 17 Apr 2001 14:07:46 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HL7ei07632; Tue, 17 Apr 2001 14:07:40 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 14:07:40 -0700 (PDT) From: Matt Dillon Message-Id: <200104172107.f3HL7ei07632@earth.backplane.com> To: Alfred Perlstein Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> <20010417135336.Q976@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :You need to settle dude, pre-emption isn't a goal, it's mearly a :_possible_ side effect. : :We're not aiming for pre-emption, we're aiming for more concurrancy. A goal of having more concurrency is laudable, but I think you are ignoring the costs of doing task switches verses the likely spin time for a mutex. The whole point of using fine-grained Mutexes is to not have significant performance-effecting collisions in the first place, so why bother to try to task switch if you wind up spining in one? The goal for Giant is to get rid of it, so why bother to implement preemption for Giant? The goal of taking an interrupt is to be able to take several interrupts in parallel on different cpu's, and they can't block anyway, so why try to turn interrupts into real threads? It just doesn't make sense, Alfred. You guys are trying to optimize things that don't need optimizing and my fear is that you will introduce so many bugs into the kernel that it will take us years to get it back to 4.x's level of reliability. The goals I see bandied about in the lists are at cross-purposes with each other. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 14:12:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0C55737B422 for ; Tue, 17 Apr 2001 14:12:50 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA15784; Tue, 17 Apr 2001 17:12:36 -0400 (EDT) (envelope-from wollman) Date: Tue, 17 Apr 2001 17:12:36 -0400 (EDT) From: Garrett Wollman Message-Id: <200104172112.RAA15784@khavrinen.lcs.mit.edu> To: Bruce Evans Cc: Current List , freebsd-standards@bostonradio.org Subject: Re: FIO* doc added to tty.4 (review) In-Reply-To: References: <200104171817.OAA13546@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Does POSIX now specify select() and/or poll() precisely enough to > show that the current behaviour is wrong? In addition to more explicit requirements for sockets, draft 6 has the following to say about select() and pselect(): A descriptor shall be considered ready for reading when a call to an input function with O_NONBLOCK clear would not block, whether or not the function would transfer data successfully. (The function might return data, an end-of-file indication, or an error other than one indicating that it is blocked, and in each of these cases the descriptor shall be considered ready for reading.) The socket semantic requirements come from 1003.1g-2000; this paragraph looks to have come from XSH4.2 (SUSv1). -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 14:42:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id ABB8437B43E for ; Tue, 17 Apr 2001 14:42:10 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-114.cwb-adsl.brasiltelecom.net.br [200.193.160.114]) by netbank.com.br (Postfix) with ESMTP id 49C394681A; Tue, 17 Apr 2001 18:42:51 -0300 (BRST) Received: from localhost (svxqxb@localhost [127.0.0.1]) by surriel.ddts.net (8.11.2/8.11.2) with ESMTP id f3HLf0f27197; Tue, 17 Apr 2001 18:41:10 -0300 Date: Tue, 17 Apr 2001 18:41:00 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Matt Dillon Cc: Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <200104172107.f3HL7ei07632@earth.backplane.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Matt Dillon wrote: > :You need to settle dude, pre-emption isn't a goal, it's mearly a > :_possible_ side effect. > : > :We're not aiming for pre-emption, we're aiming for more concurrancy. > > A goal of having more concurrency is laudable, but I think you are > ignoring the costs of doing task switches verses the likely spin time > for a mutex. The whole point of using fine-grained Mutexes is to not > have significant performance-effecting collisions in the first place, > so why bother to try to task switch if you wind up spining in one? Exactly. It makes absolutely no sense to optimise mutexes for the case of having contention. If you have contention, you need to fix the contention, not introduce all kinds of singing-dancing cool things you can do when contention happens. Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 14:52:12 2001 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 1F12837B43C for ; Tue, 17 Apr 2001 14:52:09 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HLq6i26249; Tue, 17 Apr 2001 14:52:06 -0700 (PDT) Date: Tue, 17 Apr 2001 14:52:06 -0700 From: Alfred Perlstein To: Matt Dillon Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417145206.T976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> <20010417135336.Q976@fw.wintelcom.net> <200104172107.f3HL7ei07632@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104172107.f3HL7ei07632@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 02:07:40PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010417 14:07] wrote: > > : > :You need to settle dude, pre-emption isn't a goal, it's mearly a > :_possible_ side effect. > : > :We're not aiming for pre-emption, we're aiming for more concurrancy. > > A goal of having more concurrency is laudable, but I think you are > ignoring the costs of doing task switches verses the likely spin time > for a mutex. The whole point of using fine-grained Mutexes is to not > have significant performance-effecting collisions in the first place, > so why bother to try to task switch if you wind up spining in one? > The goal for Giant is to get rid of it, so why bother to implement > preemption for Giant? The goal of taking an interrupt is to be able to > take several interrupts in parallel on different cpu's, and they can't > block anyway, so why try to turn interrupts into real threads? It just > doesn't make sense, Alfred. You guys are trying to optimize things that > don't need optimizing and my fear is that you will introduce so many > bugs into the kernel that it will take us years to get it back to 4.x's > level of reliability. The goals I see bandied about in the lists are > at cross-purposes with each other. You seem to be more concerned with the implementation rather than the goal. The goal is to have a kernel that's able to have more concurrancy, things like pre-emption and task switching on mutex collisions can be examined and possibly changed later. Once the mutexes are in place the underlying implementation can change pretty easily from task switching always to only task switching when the mutex is owned by the same CPU that I'm running on. (to avoid spinlock deadlock) I agree that task switching _might_ be a performance hit, however that can be fixed by only task switching when in interrupt context. A lot of things remain to be seen, but only if people like you sit down and start working with the SMP team to achieve the main goal, which is making the kernel MP safe for concurrant execution by locking down the appropriate structures and code paths. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 14:53:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id EBBA137B42C for ; Tue, 17 Apr 2001 14:53:11 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HLr9s09698; Tue, 17 Apr 2001 14:53:09 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 14:53:09 -0700 (PDT) From: Matt Dillon Message-Id: <200104172153.f3HLr9s09698@earth.backplane.com> To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: BAD BUG: Second try References: <200104172037.NAA27919@usr09.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Oops. : :NOTE: I don't follow this lists for weeks at a time, so please :include me directly in any responses. Thanks. : :Matt Dillon was looking at this, but I haven't heard from him :for a while on it. : :Here is a patch to make it panic, instead of really, really :trashing memory (ignore the version, I'm using a vendor import :locally); the patch is to "crfree() and should be obvious: Sorry, ran out of time on the weekend. It's still on my TODO list. -Matt :=================================================================== :diff -c -r1.2 kern_prot.c :*** kern/kern_prot.c 2001/03/21 02:33:03 1.2 :--- kern/kern_prot.c 2001/04/17 02:22:48 :*************** :*** 1001,1006 **** :--- 1001,1009 ---- : int s; : : s = splhigh(); :+ if ( cr->cr_ref == 0) { :+ panic("Freeing already free credential!\n"); :+ } : if (--cr->cr_ref == 0) { : /* : * Some callers of crget(), such as nfs_statfs(), :=================================================================== : : :Unfortunately, There's also a nameidata structure (it's the :only data structure that's exactly 72 bytes long, which I was :able to determine by printing sizeof() information for all :kernel structures, and gre'ping for "72") getting freed and :then either continued to be used, or being used as a result :of an unchecked allocation failure (I'm still looking for :that one). : :Basically, the second causes invariants to whine about data :modified on the freelist to my console, while the first one :results in an eventual panic dues to spammed memory (for the :obvious reason that you can't free the same thing twice). : :The problems only become obvious when you open and then close :around 30,000 TCP connections; sometimes it takes a couple of :tries before it panics your machine. : :I have some programs that demonstrate the bug, if anyone is :interested in repeating it on their machines locally (you will :need appropriate open file limits and bump up to 40,000 or so :net.inet.ip.portrange.last, e.g.: : : sysctl -w net.inet.ip.portrange.last=45000 : :Which means your box will need about a gig of memory. : : : Terry Lambert : terry@lambert.org :--- :Any opinions in this posting are my own and not those of my present :or previous employers. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15: 0:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 021C037B424 for ; Tue, 17 Apr 2001 15:00:38 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HM0TI09802; Tue, 17 Apr 2001 15:00:29 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 15:00:29 -0700 (PDT) From: Matt Dillon Message-Id: <200104172200.f3HM0TI09802@earth.backplane.com> To: Alfred Perlstein Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> <20010417135336.Q976@fw.wintelcom.net> <200104172107.f3HL7ei07632@earth.backplane.com> <20010417145206.T976@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Once the mutexes are in place the underlying implementation can :change pretty easily from task switching always to only task :switching when the mutex is owned by the same CPU that I'm running :on. (to avoid spinlock deadlock) That makes *NO* *SENSE* Alfred! So the first step is to introduce every single possible feature under the sun, requiring massive reworking of the code, even if it means the system becomes massively unstable, inefficient, and starts crashing and burning, and then only *later* we remove the features that don't pan out? That is the development model you are using for -current? :I agree that task switching _might_ be a performance hit, however :that can be fixed by only task switching when in interrupt context. WILL be a performance hit. WILL introduce major bugs. IS unnecessary, DOESN'T make any sense whatsoever, is at CROSS PURPOSES with goals already stated (not having any serious contention in the first place), REQUIRES massive changes to the code with not a chance in hell of producing an equivalent performance improvement for the trouble. There is no 'remains to be seen' here Alfred. This is setting up -current for a fall, one that could be entirely avoided *now* if you people would sit down and start thinking about what you are doing. Remember when Dyson introduced ten thousand cool things all at once and didn't debug them? Remember how long it took DG to the system back into some semblence of shape after that? Remember that, even after all that hard work, there were still literally hundreds of hard to find bugs that DG couldn't find that it took Alan, DG, and I a year's worth of work beyond all the work DG had already done to cleanup? Is that what you want to happen to current? Because that is where current is headed right now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:12:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.state.me.us (mailhub.state.me.us [141.114.122.227]) by hub.freebsd.org (Postfix) with ESMTP id 26B1137B43C for ; Tue, 17 Apr 2001 15:12:17 -0700 (PDT) (envelope-from darren@katahdin.bmv.state.me.us) Received: from katahdin.bmv.state.me.us by mailhub.state.me.us with ESMTP; Tue, 17 Apr 2001 18:09:55 -0400 Received: from localhost (darren@localhost) by katahdin.bmv.state.me.us (AIX4.2/UCB 8.7/8.7) with ESMTP id SAA32512; Tue, 17 Apr 2001 18:11:40 -0400 (EDT) Date: Tue, 17 Apr 2001 18:11:40 -0400 (EDT) From: Darren Henderson To: Andrew Gallatin Cc: current@FreeBSD.ORG, jlemon@flugsvamp.com Subject: Re: miibus/fxp intel etherexpress broken In-Reply-To: <15063.18227.260693.786852@grasshopper.cs.duke.edu> Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, the patch appears to work fine. Sorry for the delay in testing it, long weekend here. -Darren On Fri, 13 Apr 2001, Andrew Gallatin wrote: > > Darren Henderson writes: > > > > I had a functional install of -current which was created back on Jan 11th of > > this year. > > > > I cvsup'd yesterday (4/12. I had also tried this on 4/4) fixxed what I > > needed too from UPDATING and RELNOTES, built and installed world and a new > > kernel. > > > > fxp now fails. > > > > ata1: at 0x170 irq 15 on atapci0 > <...> > > fxp0: port 0x5400-0x541f mem 0x60000000-0x600fffff,0x60100000-0x60100fff irq 15 at device 11.0 on pci0 > > fxp0: could not map interrupt > > device_probe_and_attach: fxp0 attach returned 6 > > isa0: unexpected small tag 14 > > > This has nothing to do with fxp. The problem is that irq15 is shared > between ata1 and fxp0 & the ata driver doesn't want to share > interrupts because some older boards will somehow barf when > sharing irqs between ata and other devices. > > Try this patch (I haven't tested it myself) > > Index: dev/ata/ata-pci.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-pci.c,v > retrieving revision 1.3 > diff -u -r1.3 ata-pci.c > --- dev/ata/ata-pci.c 2001/03/19 13:31:58 1.3 > +++ dev/ata/ata-pci.c 2001/04/13 18:32:21 > @@ -508,7 +508,7 @@ > > return BUS_ALLOC_RESOURCE(device_get_parent(dev), child, > SYS_RES_IRQ, rid, > - irq, irq, 1, flags & ~RF_SHAREABLE); > + irq, irq, 1, flags); > #endif > } > else { > > > Drew > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > ________________________________________________________________________ Darren Henderson darren@bmv.state.me.us darren.henderson@state.me.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:19:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id E5B6837B423 for ; Tue, 17 Apr 2001 15:18:58 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3HMIZ312233; Tue, 17 Apr 2001 22:18:35 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Tue, 17 Apr 2001 22:18:34 +0000 (GMT) From: "E.B. Dreger" To: Alfred Perlstein Cc: Matt Dillon , "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <20010417145206.T976@fw.wintelcom.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 > Date: Tue, 17 Apr 2001 14:52:06 -0700 > From: Alfred Perlstein Disclaimer: I am not a kernel hacker. > The goal is to have a kernel that's able to have more concurrancy, Right... > things like pre-emption and task switching on mutex collisions can > be examined and possibly changed later. I think that Matt is saying, why bother? Task switches are expensive. With a heavily loaded system, the amount of time spent arbitrating mutexes would exceed spin time. With a lightly loaded system, do we really care that much about spinning? > Once the mutexes are in place the underlying implementation can > change pretty easily from task switching always to only task > switching when the mutex is owned by the same CPU that I'm running I'm not sure that I follow... if the task switch is on the same CPU, then why do we need any new structures? Without a global memory cache*, I think that keeping processes on the same CPU is the first goal, anyway, and increased concurrency second. * Does Intel have any sort of cache coherency mechanism, where a processor can tell other CPUs, "hey, this line is dirty" and the others retrieve the new info as needed? The Alpha? > on. (to avoid spinlock deadlock) > > I agree that task switching _might_ be a performance hit, however > that can be fixed by only task switching when in interrupt context. Ughh. AFAIK, traditional wisdom holds that interrupt loops should be as short as possible. Assuming that one performs quick operations, DMA transfers, etc., preemptive task switching *would* be expensive. > A lot of things remain to be seen, but only if people like you sit > down and start working with the SMP team to achieve the main goal, > which is making the kernel MP safe for concurrant execution by > locking down the appropriate structures and code paths. Let's look at userland code. I don't use async I/O because I don't want to screw with interrupts and callbacks. Polling of large structures? Ughh. Kernel queues are the solution, and what totally sold me on FreeBSD. How about basing things on *cooperative* multitasking? All else being equal, cooperative is faster because of lower overhead. What makes co-op break down is greedy programs that monopolize the CPU... but there should not be any code like that in the kernel. My instinct (whatever it's worth; remember my disclaimer) is that co-op switching using something like tsleep() and wakeup_one() or similar would be more efficient than trying to screw with mutexes. However, perhaps that could be improved upon: Use something a la kqueue for portions of the kernel to say "I'm waiting for condition XYZ". When we wakeup_one(), we specify "for condition XYZ". We could then avoid waking processes that would only go back to sleep again. I hope that I'm not too far out of my league, here... :-) Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:20:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 9934C37B423 for ; Tue, 17 Apr 2001 15:20:27 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3HMKMM12269; Tue, 17 Apr 2001 22:20:22 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Tue, 17 Apr 2001 22:20:21 +0000 (GMT) From: "E.B. Dreger" To: Matt Dillon Cc: Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <200104172200.f3HM0TI09802@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 17 Apr 2001 15:00:29 -0700 (PDT) > From: Matt Dillon > > WILL be a performance hit. WILL introduce major bugs. IS unnecessary, > DOESN'T make any sense whatsoever, is at CROSS PURPOSES with goals > already stated (not having any serious contention in the first place), > REQUIRES massive changes to the code with not a chance in hell of > producing an equivalent performance improvement for the trouble. What was the name of that network stack... There was a net stack that spent significant amounts of effort creating something asynchronous, with fancy preemption. In the end, they trashed the whole thing, because run-to-completion was faster. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:36:49 2001 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 1304037B424 for ; Tue, 17 Apr 2001 15:36:46 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HMaCA27743; Tue, 17 Apr 2001 15:36:12 -0700 (PDT) Date: Tue, 17 Apr 2001 15:36:12 -0700 From: Alfred Perlstein To: Matt Dillon Cc: "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417153612.W976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> <20010417135336.Q976@fw.wintelcom.net> <200104172107.f3HL7ei07632@earth.backplane.com> <20010417145206.T976@fw.wintelcom.net> <200104172200.f3HM0TI09802@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104172200.f3HM0TI09802@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 03:00:29PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010417 15:00] wrote: > > :Once the mutexes are in place the underlying implementation can > :change pretty easily from task switching always to only task > :switching when the mutex is owned by the same CPU that I'm running > :on. (to avoid spinlock deadlock) > > That makes *NO* *SENSE* Alfred! So the first step is to introduce > every single possible feature under the sun, requiring massive reworking > of the code, even if it means the system becomes massively unstable, > inefficient, and starts crashing and burning, and then only *later* we > remove the features that don't pan out? That is the development model > you are using for -current? No I am not, what I'm trying to do is _use_ the APIs given to me to make the kernel more concurrent. I see no reason to abandon the external API, they are perfectly fine. You may disagree with the underlying implementation of the API and I think you may be right. (although afaik we're basing it on both Solaris and BSD/os's implementation so... well I'm not going to bother defending it.) I just wish you'd sit down and try to work adapting the VM to these APIs You're not going to get an arguement out of me about the underlying implementation of the mutexes as I really don't care right now. What I am going to argue is that argueing about the underlying implementation is a waste of time that could be better spent using the API to gain more concurrancy. > :I agree that task switching _might_ be a performance hit, however > :that can be fixed by only task switching when in interrupt context. > > WILL be a performance hit. WILL introduce major bugs. IS unnecessary, > DOESN'T make any sense whatsoever, is at CROSS PURPOSES with goals > already stated (not having any serious contention in the first place), > REQUIRES massive changes to the code with not a chance in hell of > producing an equivalent performance improvement for the trouble. > > There is no 'remains to be seen' here Alfred. This is setting up > -current for a fall, one that could be entirely avoided *now* > if you people would sit down and start thinking about what you are > doing. No, sitting down and spending many months hashing out the underlying mechnisms of what should be a pretty opaque API is a waste of time and will stagnate developement at much too great a cost. In fact, we sorta spent about 3 years doing it already haven't we? :) > > Remember when Dyson introduced ten thousand cool things all at once > and didn't debug them? Remember how long it took DG to the system > back into some semblence of shape after that? Remember that, even after > all that hard work, there were still literally hundreds of hard to find > bugs that DG couldn't find that it took Alan, DG, and I a year's worth > of work beyond all the work DG had already done to cleanup? Is that > what you want to happen to current? Because that is where current is > headed right now. Actually back then I wasn't that much of a kernel hacker, don't you remeber me standing there at SF BAFUG while you, Julian and Terry were discussing cache-coherency issues? I sort of had to take a break from listening to the lot of you because my brain went into overload, I was 19 or 20 at the time. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:45: 9 2001 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 2D92137B424; Tue, 17 Apr 2001 15:45:05 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA08917; Wed, 18 Apr 2001 08:44:53 +1000 Date: Wed, 18 Apr 2001 08:43:53 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: David Wolfskill Cc: current@FreeBSD.ORG, john@baldwin.cx, kris@FreeBSD.ORG Subject: Re: FW: Snapshot Log - current broke In-Reply-To: <200104172030.f3HKU1A86600@bunrab.catwhisker.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 Tue, 17 Apr 2001, David Wolfskill wrote: > >Date: Tue, 17 Apr 2001 12:34:39 -0700 (PDT) > >From: John Baldwin > >... > >In file included from /usr/src/usr.sbin/pcvt/vttest/header.h:26, > > from /usr/src/usr.sbin/pcvt/vttest/main.c:20: > >/usr/obj/usr/src/i386/usr/include/stdio.h:302: syntax error before `char' > >*** Error code 1 > >*** Error code 1 > >2 errors > >... > > Whacking src/include/stdio.h thus: > > Index: include/stdio.h > =================================================================== > RCS file: /cvs/freebsd/src/include/stdio.h,v > retrieving revision 1.32 > diff -u -u -r1.32 stdio.h > --- include/stdio.h 2001/04/17 07:59:52 1.32 > +++ include/stdio.h 2001/04/17 17:54:57 > @@ -299,7 +299,7 @@ > __BEGIN_DECLS > int asprintf __P((char **, const char *, ...)) __printflike(2, 3); > char *ctermid_r __P((char *)); > -const char *fmtcheck __P((const char *, const char *)) > +__const char *fmtcheck __P((const char *, const char *)) > __attribute__((__format_arg__(2))); > char *fgetLn __P((FILE *, size_t *)); > int fpurge __P((FILE *)); > > has allowed the "make buildworld" to succeed for me. Building the > kernel as I type; above was hand-transcribed (machine is not networked > at the moment). Use at your own risk; void where prohibited, etc.... This is because vttest is compiled with a K&Rish compiler (gcc -traditional) for some reason, and the hard `const' doesn't work for K&R compilers. The `const's inside __P(()) don't cause problems because they are soft -- __P(()) defines them away as part of defining everything inside the inner parentheses away, although this is bogus since prototypes work for `gcc -traditional'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 15:51:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id D9CEE37B423 for ; Tue, 17 Apr 2001 15:51:11 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3HMp6E12691; Tue, 17 Apr 2001 22:51:06 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Tue, 17 Apr 2001 22:51:06 +0000 (GMT) From: "E.B. Dreger" To: "'current@freebsd.org'" Cc: Alfred Perlstein , Matt Dillon , "Justin T. Gibbs" , Doug Barton Subject: Re: FW: Filesystem gets a huge performance boost 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 > Date: Tue, 17 Apr 2001 22:18:34 +0000 (GMT) > From: E.B. Dreger > > My instinct (whatever it's worth; remember my disclaimer) is that co-op > switching using something like tsleep() and wakeup_one() or similar would > be more efficient than trying to screw with mutexes. Oops. I meant asleep(). Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 16: 2:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by hub.freebsd.org (Postfix) with ESMTP id 5C91337B43C for ; Tue, 17 Apr 2001 16:02:44 -0700 (PDT) (envelope-from ancient@outloud.org) Received: from surferboy.outloud.org (Goal@House.Of.Pain.Com [24.14.88.149]) by mail.webjockey.net (8.11.3/8.11.3) with ESMTP id f3HN2Y500359 for ; Tue, 17 Apr 2001 19:02:36 -0400 (EDT) (envelope-from ancient@outloud.org) Message-Id: <5.1.0.12.2.20010417173118.00af0a90@208.141.46.12> X-Sender: ancient@208.141.46.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1.0.12 (Beta) Date: Tue, 17 Apr 2001 17:32:48 -0500 To: current@freebsd.org From: Storms of Perfection Subject: Swap partition panic on -current 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 Does anyone know of a possible bug/panic with the swap partition? I tried to view a file with vi/pico on -current (10+M file) and it crashed the machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 16: 4:34 2001 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 CBEB837B440 for ; Tue, 17 Apr 2001 16:04:31 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3HN4JL28591; Tue, 17 Apr 2001 16:04:19 -0700 (PDT) Date: Tue, 17 Apr 2001 16:04:18 -0700 From: Alfred Perlstein To: "E.B. Dreger" Cc: "'current@freebsd.org'" , Matt Dillon , "Justin T. Gibbs" , Doug Barton Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417160418.X976@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Tue, Apr 17, 2001 at 10:51:06PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * E.B. Dreger [010417 15:51] wrote: > > Date: Tue, 17 Apr 2001 22:18:34 +0000 (GMT) > > From: E.B. Dreger > > > > My instinct (whatever it's worth; remember my disclaimer) is that co-op > > switching using something like tsleep() and wakeup_one() or similar would > > be more efficient than trying to screw with mutexes. > > Oops. I meant asleep(). I don't really like asleep(). asleep()/await() seem to require the schedlock to be aquired and released twice EVERY TIME they are called rather a mutex which only needs to enter the scheduler when it fails to aquire. seriously, it would be _trivial_ to: 1) make interrupts the only thing that could switch, or 2) turn interrupt related locks into spinlocks that do the equivelant of splhigh on that cpu. any further discussion of the underlying implementation is a waste of time and I refuse to do it any further. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 16:27:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from enia.bastun.net (enia.bastun.net [212.95.178.212]) by hub.freebsd.org (Postfix) with ESMTP id AF1FE37B422 for ; Tue, 17 Apr 2001 16:27:24 -0700 (PDT) (envelope-from maav@enia.bastun.net) Received: (from maav@localhost) by enia.bastun.net (8.11.3/8.11.3) id f3HNSbm01254 for freebsd-current@freebsd.org; Wed, 18 Apr 2001 02:28:37 +0300 (EEST) (envelope-from maav) Date: Wed, 18 Apr 2001 02:28:37 +0300 From: User & To: freebsd-current@freebsd.org Subject: mounting netware fs Message-ID: <20010418022836.A494@enia.bastun.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, first of all sorry if this is not the proper list for writing this. This is my first posting and I'm new to FreeBSD, so please forgive me if I am sending crap in this message. I needed to install Netware filesystem support and noticed that if I want to mount the nwfs via /etc/fstab, I have to change the /etc/rc file so that the system won't try to mount the nwfs before there is networking support started. So that's why I had to change /etc/rc on line 258 from: # Mount everything except nfs filesystems. mount -a -t nonfs to # Mount everything except nfs filesystems. mount -a -t nonfs,nwfs In the first case at boot time the machine stops and wants me to enter in shell and fix the problem. I don't know whether I'm right, but I think that my modification can help. Boris Georgiev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 16:28:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 38F2337B42C for ; Tue, 17 Apr 2001 16:28:36 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id QAA07795 for ; Tue, 17 Apr 2001 16:28:35 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpdAAAseaqmp; Tue Apr 17 16:28:25 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA01367 for current@freebsd.org; Tue, 17 Apr 2001 16:28:46 -0700 (MST) From: Terry Lambert Message-Id: <200104172328.QAA01367@usr09.primenet.com> Subject: More on Bad Bug To: current@freebsd.org Date: Tue, 17 Apr 2001 23:28:46 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] 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 NB: To keep me in the loop, keep me in the Cc: list, since I rarely follow -current these days). I've further localized the bug to the freeing of credentials associated with socket buffers, and being unrelated to the crhold()/crfree() calls in socreate() and sodealloc(). Specifically, the bug exhibits as INVARIANTS complaining about a 72 byte malloc -- it seems that in avoiding system call structures, I neglected struct rusage -- which is exactly 72 bytes in size, as well. There seems to be some bad code in soo_close(), which looks like: int soo_close(fp, p) struct file *fp; struct proc *p; { int error = 0; fp->f_ops = &badfileops; if (fp->f_data) error = soclose((struct socket *)fp->f_data); fp->f_data = 0; return (error); } It seems to me this should be? int soo_close(fp, p) struct file *fp; struct proc *p; { int error = 0; if (fp->f_data) error = soclose((struct socket *)fp->f_data); if (!error) { fp->f_data = 0; fp->f_ops = &badfileops; } return (error); } But it's not clear that this is correct for the socket code. The INVARIANTS code is actually part of the problem here, since the reference count on the credential is one of the fields stomped by the WIERD_ADDR "to be safer". This doesn't evidence as a problem with a double free in the case that INVARIANTS aren't used, in that the decremented count in the crfree() (which decrements prior to examining the value to see if it is exactly zero), would continue to be non-zero, and not decrement back to zero (resulting in the double free). Credentials are actually used _AMAZINGLY_ much; it seems that they are a good candidate for some optimization to throw away references that aren't really necessary (for example, it seems to me that a socket can not exist without an fdp referencing it, and the fdp has a reference count on the cred which the socket inherits from the fdp, so the fdp's reference protects the sockets reference, and so the socket's reference doesn't really need to be reference counted). In any case, I'm leaving in the panic patch I sent earlier, and am now rebuilding with my ucred reference count moved past the area stomped by INVARIANTS. This should permit the INVARIANTS to catch double frees (which they can't, otherwise, because of the refcnt decrement making it look like the block was used after being freed, and tricking INVARIANTS in free() in kern_malloc.c. I guess no one else is interested in this bug hunt, or no one else is using 30,000 sockets on any of their machines? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 16:59: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B32C537B422 for ; Tue, 17 Apr 2001 16:58:58 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3HNwua11870; Tue, 17 Apr 2001 16:58:56 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 16:58:56 -0700 (PDT) From: Matt Dillon Message-Id: <200104172358.f3HNwua11870@earth.backplane.com> To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: More on Bad Bug References: <200104172328.QAA01367@usr09.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :There seems to be some bad code in soo_close(), which looks like: : : int : soo_close(fp, p) : struct file *fp; : struct proc *p; : { : int error = 0; : : fp->f_ops = &badfileops; : if (fp->f_data) : error = soclose((struct socket *)fp->f_data); : fp->f_data = 0; : return (error); : } : :It seems to me this should be? : : int : soo_close(fp, p) : struct file *fp; : struct proc *p; : { : int error = 0; : : if (fp->f_data) : error = soclose((struct socket *)fp->f_data); : if (!error) { : fp->f_data = 0; : fp->f_ops = &badfileops; : } : return (error); : } :... :But it's not clear that this is correct for the socket code. I think this is ok. soclose() is passed a socket structure which has no concept of the original struct file that held it. :Credentials are actually used _AMAZINGLY_ much; it seems that they :are a good candidate for some optimization to throw away references :that aren't really necessary (for example, it seems to me that a :socket can not exist without an fdp referencing it, and the fdp has :a reference count on the cred which the socket inherits from the fdp, :so the fdp's reference protects the sockets reference, and so the :socket's reference doesn't really need to be reference counted). There should be a reference count for each reference. The credential is stored in the socket structure so it is the responsibility of the socket code to gain another reference to it when it makes the assignment. I wouldn't worry about trying to optimize ref count cases... you are talking about nanoseconds there. :In any case, I'm leaving in the panic patch I sent earlier, and am :now rebuilding with my ucred reference count moved past the area I think the panic patch is an excellent idea and should be comitted and (after we unfreeze) MFC'd. Moving the ref count to catch double-frees is a good idea as well. :I guess no one else is interested in this bug hunt, or no one else :is using 30,000 sockets on any of their machines? : : Terry Lambert : terry@lambert.org I'm still interested! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 17: 2:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 88B4637B424 for ; Tue, 17 Apr 2001 17:02:14 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9D08F6ACB8; Wed, 18 Apr 2001 09:32:12 +0930 (CST) Date: Wed, 18 Apr 2001 09:32:12 +0930 From: Greg Lehey To: Alfred Perlstein Cc: Matt Dillon , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010418093212.A80877@wantadilla.lemis.com> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010417011957.W976@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Apr 17, 2001 at 01:19:57AM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 17 April 2001 at 1:19:57 -0700, Alfred Perlstein wrote: > * Matt Dillon [010415 23:16] wrote: >> >> For example, all this work on a preemptive >> kernel is just insane. Our entire kernel is built on the concept of >> not being preemptable except by interrupts. We virtually guarentee >> years of instability and bugs leaking out of the woodwork by trying to >> make it preemptable, and the performance gain we get for that pain >> is going to be zilch. Nada. Nothing. > > Pre-emption is mearly a side effect of a mutex'd kernel. > > The actual gains are in terms of parallel execution internally. > Meaning if we happen to copyin() a 4 meg buffer we can allow more > than one process to be completing some sort of work inside the > kernel other than spinning on the giant lock. *sigh* Couldn't you have changed the subject line when discussing something of this importance? 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 Tue Apr 17 17:21:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 3281637B42C; Tue, 17 Apr 2001 17:21:41 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I0Las13653; Wed, 18 Apr 2001 00:21:36 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 00:21:36 +0000 (GMT) From: "E.B. Dreger" To: current@FreeBSD.ORG, smp@FreeBSD.ORG Cc: Alfred Perlstein , Matt Dillon , "Justin T. Gibbs" , Doug Barton Subject: SMP architecture (Re: FW: Filesystem gets a huge performance boost) In-Reply-To: <20010417160418.X976@fw.wintelcom.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 (cross-posting to SMP and renaming in an effort to move the thread) > Date: Tue, 17 Apr 2001 16:04:18 -0700 > From: Alfred Perlstein (Repeat disclaimer: I am not a kernel hacker.) > seriously, it would be _trivial_ to: > > 1) make interrupts the only thing that could switch, or > 2) turn interrupt related locks into spinlocks that do the equivelant > of splhigh on that cpu. I just don't like the idea of preempting interrupts. > any further discussion of the underlying implementation is a waste of > time and I refuse to do it any further. No, it's not. We all want greater meaningful concurrency. (i.e., having one CPU do something productive while seven spin or fight over a mutex is pointless.) The underlying implementation is of utmost importance, because we don't want to have a 500% increase in overhead for a 5% increase in concurrency. Sort of like trying to have a 486-based router compressing T3 traffic... [ snip bit about dislike of asleep()/await() ] Okay. Let me rephrase. I meant in a manner similar to asleep()/await(), not necessarily those specific calls. I was thinking about passing a token. Imagine this for a central CPU loop: do { if (cpu_with_token == this_cpu) { whatever_needs_big_lock(); pass_token_to_next_cpu(); } standard_scheduler(); } Cooperatively share a token, as opposed to spinning/sleeping for a mutex. Interrupt handlers are inherently unsafe, because we may or may not have the token. Fine, most handlers are for I/O anyhow; pull/push data to/from a buffer, then go back to the main loop. The portion of the "interrupt handler" that requires the big lock can wait until the proper CPU has the token... it's better than spinning or blocking other CPUs, right? Am I missing something? ("What am I missing?", maybe?) Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 17:47:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A623637B423 for ; Tue, 17 Apr 2001 17:47:31 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3I0lN615938; Tue, 17 Apr 2001 17:47:23 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 17:47:23 -0700 (PDT) From: Matt Dillon Message-Id: <200104180047.f3I0lN615938@earth.backplane.com> To: Greg Lehey Cc: Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :*sigh* Couldn't you have changed the subject line when discussing :something of this importance? : :Greg Sorry. Now I am so much in a huff I'm thinking about how all this could be implemented from scratch with the 4.x base. I know, I know, good luck Matt... For example, this business about interrupts as threads. BSDI had an interesting solution, but what I liked most about it was that if an interrupt could be completed right then and there it was just like a normal interrupt. It's the bit about switching stacks, detecting a mutex interlock, and blocking as a thread which was the complex part. But I think I just now came up with a better one (and to be fair, I just came up with this now). Interrupts by definition know precisely what they are going to do, so by definition they know precisely which mutexes (if any) they may need to get. This means that, in fact, it is possible to implement a check to determine if any of the mutexes an interrupt might want to get are already being held by the SAME cpu or not, and if they are to do the equivalent of what our delayed-interrupt stuff does in the stable's spl/splx code, but instead do the check when a mutex is released. The result is: No need for an idle process to support interrupt contexts, no need to implement interrupts as threads, and no need to implement fancy scheduling tricks or Giant handling. 4.x: mainline kernel { s = splblah(); . masked interrupt occurs, sets bit and immediately irets . . splx(s); (bit found to be set and delayed interrupt is issued here) } Proposed: mainline kernel { get_spin_mutex(&somemutex); . . masked interrupt occurs, interrupt structure contains array of mutexes the interrupt will need. Check said mutexes, one found to be held by current cpu. Set interrupt-pending bit in mutex and iret immediately. . . release_spin_mutex(&somemutex) (bit found to be set in mutex, triggers interrupt reissuing code) } And there you have it. The mutex/array test is takes very little time being a read-only test that requires no bus locking, and the collision case is cheap also because the current cpu already owns the mutex, allowing us to set the interrupt-pending bit in that mutex without any bus locking. The check during the release of the mutex is two instructions, no bus locking required. The whole thing can be implemented without any additional bus locking and virtually no contention. The case could be further optimized by requiring that interrupts only use a single mutex, period. This would allow the mainline interrupt routine to obtain the mutex on entry to the interrupt and allow the reissuing code to reissue the interrupt without freeing the mutex that caused the reissue, so the mutex is held throughout and then freed by the interrupt itself. Holy shit. I think that's it! I don't think it can get much better then that. It solves all of BDE's issues, solves the interrupt-as-thread issue (by not using threads for interrupts at all), and removes a huge amount of unnecessary complexity from the system. We could even get rid of the idle processes if we wanted to. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18: 2: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from technokratis.com (modemcable092.3-201-24.mtl.mc.videotron.ca [24.201.3.92]) by hub.freebsd.org (Postfix) with ESMTP id CA57637B422 for ; Tue, 17 Apr 2001 18:01:58 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f3I12e514918; Tue, 17 Apr 2001 21:02:40 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 17 Apr 2001 21:02:40 -0400 From: Bosko Milekic To: "E.B. Dreger" Cc: Alfred Perlstein , Matt Dillon , "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010417210240.A14803@technokratis.com> References: <20010417145206.T976@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Tue, Apr 17, 2001 at 10:18:34PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 17, 2001 at 10:18:34PM +0000, E.B. Dreger wrote: > > Once the mutexes are in place the underlying implementation can > > change pretty easily from task switching always to only task > > switching when the mutex is owned by the same CPU that I'm running > > I'm not sure that I follow... if the task switch is on the same CPU, then > why do we need any new structures? Without a global memory cache*, I > think that keeping processes on the same CPU is the first goal, anyway, > and increased concurrency second. > > * Does Intel have any sort of cache coherency mechanism, where a processor > can tell other CPUs, "hey, this line is dirty" and the others retrieve the > new info as needed? The Alpha? There is a mechanism, yes. Whether or not it can be compared to the Alpha's, I have no idea. :-) Intel provides documentation on-line detailing somewhat how cache invalidating happens. Unfortunately, I lost the exact URL in recent CURRENT crashes (ahhh, the irony of it all :-)), so you'll have to dig a little. > > on. (to avoid spinlock deadlock) > > > > I agree that task switching _might_ be a performance hit, however > > that can be fixed by only task switching when in interrupt context. > > Ughh. AFAIK, traditional wisdom holds that interrupt loops should be as > short as possible. Assuming that one performs quick operations, DMA > transfers, etc., preemptive task switching *would* be expensive. Probably true, but then you really only need to task switch if all the CPUs are busy. So, as you say somewhere earlier in this message, "on a lightly loaded system," this actually won't be the case. > > A lot of things remain to be seen, but only if people like you sit > > down and start working with the SMP team to achieve the main goal, > > which is making the kernel MP safe for concurrant execution by > > locking down the appropriate structures and code paths. > > Let's look at userland code. I don't use async I/O because I don't want > to screw with interrupts and callbacks. Polling of large structures? > Ughh. Kernel queues are the solution, and what totally sold me on > FreeBSD. > > How about basing things on *cooperative* multitasking? All else being > equal, cooperative is faster because of lower overhead. What makes co-op > break down is greedy programs that monopolize the CPU... but there should > not be any code like that in the kernel. > > My instinct (whatever it's worth; remember my disclaimer) is that co-op > switching using something like tsleep() and wakeup_one() or similar would > be more efficient than trying to screw with mutexes. > > However, perhaps that could be improved upon: Use something a la kqueue > for portions of the kernel to say "I'm waiting for condition XYZ". When > we wakeup_one(), we specify "for condition XYZ". We could then avoid > waking processes that would only go back to sleep again. See condition variables, as those are the closest I can think of regarding what you described. They are implemented in -CURRENT. > I hope that I'm not too far out of my league, here... :-) > > > Eddy > > --------------------------------------------------------------------------- > > Brotsman & Dreger, Inc. > EverQuick Internet / EternalCommerce Division > > Phone: (316) 794-8922 > > --------------------------------------------------------------------------- Later, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18: 6:38 2001 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 1BBD437B423 for ; Tue, 17 Apr 2001 18:06:36 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3I16Ji02507; Tue, 17 Apr 2001 18:06:19 -0700 (PDT) Date: Tue, 17 Apr 2001 18:06:18 -0700 From: Alfred Perlstein To: Greg Lehey Cc: Matt Dillon , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010417180618.Z976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010418093212.A80877@wantadilla.lemis.com>; from grog@lemis.com on Wed, Apr 18, 2001 at 09:32:12AM +0930 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey [010417 17:02] wrote: > On Tuesday, 17 April 2001 at 1:19:57 -0700, Alfred Perlstein wrote: > > * Matt Dillon [010415 23:16] wrote: > >> > >> For example, all this work on a preemptive > >> kernel is just insane. Our entire kernel is built on the concept of > >> not being preemptable except by interrupts. We virtually guarentee > >> years of instability and bugs leaking out of the woodwork by trying to > >> make it preemptable, and the performance gain we get for that pain > >> is going to be zilch. Nada. Nothing. > > > > Pre-emption is mearly a side effect of a mutex'd kernel. > > > > The actual gains are in terms of parallel execution internally. > > Meaning if we happen to copyin() a 4 meg buffer we can allow more > > than one process to be completing some sort of work inside the > > kernel other than spinning on the giant lock. > > *sigh* Couldn't you have changed the subject line when discussing > something of this importance? I wasn't discussing, I was explaining. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:19:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from technokratis.com (modemcable092.3-201-24.mtl.mc.videotron.ca [24.201.3.92]) by hub.freebsd.org (Postfix) with ESMTP id BC1A437B446 for ; Tue, 17 Apr 2001 18:19:39 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f3I1Kk214991; Tue, 17 Apr 2001 21:20:46 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 17 Apr 2001 21:20:45 -0400 From: Bosko Milekic To: Matt Dillon Cc: Greg Lehey , Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010417212045.B14803@technokratis.com> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> <200104180047.f3I0lN615938@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104180047.f3I0lN615938@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 05:47:23PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 17, 2001 at 05:47:23PM -0700, Matt Dillon wrote: > Proposed: > > mainline kernel { > get_spin_mutex(&somemutex); > . > . > masked interrupt occurs, interrupt structure contains array > of mutexes the interrupt will need. Check said mutexes, one > found to be held by current cpu. Set interrupt-pending bit > in mutex and iret immediately. You cannot be pre-empted by an interrupt if you are holding a spin mutex, AFAIK, even under present implementation. > . > . > release_spin_mutex(&somemutex) > (bit found to be set in mutex, triggers interrupt reissuing code) > } > > And there you have it. The mutex/array test is takes very little time > being a read-only test that requires no bus locking, and the collision > case is cheap also because the current cpu already owns the mutex, allowing > us to set the interrupt-pending bit in that mutex without any bus > locking. The check during the release of the mutex is two instructions, > no bus locking required. The whole thing can be implemented without any > additional bus locking and virtually no contention. > > The case could be further optimized by requiring that interrupts only > use a single mutex, period. This would allow the mainline interrupt > routine to obtain the mutex on entry to the interrupt and allow the > reissuing code to reissue the interrupt without freeing the mutex that > caused the reissue, so the mutex is held throughout and then freed by > the interrupt itself. > > Holy shit. I think that's it! I don't think it can get much better then > that. It solves all of BDE's issues, solves the interrupt-as-thread > issue (by not using threads for interrupts at all), and removes a huge > amount of unnecessary complexity from the system. We could even get rid > of the idle processes if we wanted to. What happens if we get an interrupt, we're thinking about servicing it, about to check whether we're already holding a mutex that may potentially be used inside the mainline int routine, and another CPU becomes idle? In this particular case, let's say that we decide that we have to set ipending and iret immediately, because we're already holding a potential lock when we got interrupted. Isn't the result that we have a second CPU idling while we just set ipending? (I could be missing something, really). Also, some mainline interrupt code may need to acquire a really large number of locks, but only in some cases. Let's say we have to first check if we have a free cached buffer sitting somewhere, and if not, malloc() a new one. Well, the malloc() will eventually trigger a chain of mutex lock operations, but only in the case where we lack the cached buffer to allocate it. There is no practical way of telling up front whether or not we'll have to malloc(), so I'm wondering how efficiently we would be able to predict in cases such as these? > -Matt Cheers, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:28:53 2001 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 70DF837B43E for ; Tue, 17 Apr 2001 18:28:49 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3I1SeW03154; Tue, 17 Apr 2001 18:28:40 -0700 (PDT) Date: Tue, 17 Apr 2001 18:28:40 -0700 From: Alfred Perlstein To: Matt Dillon Cc: Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010417182840.A976@fw.wintelcom.net> References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> <200104180047.f3I0lN615938@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104180047.f3I0lN615938@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 05:47:23PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010417 17:47] wrote: ... > > Interrupts by definition know precisely what they are going to do, so by > definition they know precisely which mutexes (if any) they may need > to get. This means that, in fact, it is possible to implement a check > to determine if any of the mutexes an interrupt might want to get are > already being held by the SAME cpu or not, and if they are to do the > equivalent of what our delayed-interrupt stuff does in the stable's > spl/splx code, but instead do the check when a mutex is released. > > The result is: No need for an idle process to support interrupt > contexts, no need to implement interrupts as threads, and no need > to implement fancy scheduling tricks or Giant handling. > ... > And there you have it. The mutex/array test is takes very little time > being a read-only test that requires no bus locking, and the collision > case is cheap also because the current cpu already owns the mutex, allowing > us to set the interrupt-pending bit in that mutex without any bus > locking. The check during the release of the mutex is two instructions, > no bus locking required. The whole thing can be implemented without any > additional bus locking and virtually no contention. > > The case could be further optimized by requiring that interrupts only > use a single mutex, period. This would allow the mainline interrupt > routine to obtain the mutex on entry to the interrupt and allow the > reissuing code to reissue the interrupt without freeing the mutex that > caused the reissue, so the mutex is held throughout and then freed by > the interrupt itself. > > Holy shit. I think that's it! I don't think it can get much better then > that. It solves all of BDE's issues, solves the interrupt-as-thread > issue (by not using threads for interrupts at all), and removes a huge > amount of unnecessary complexity from the system. We could even get rid > of the idle processes if we wanted to. We can switch to this mechism at a later date. There's issues here though: Mutex creation can be expensive as it seems like each interrupt needs to register what sort of mutex it's interested in, when a mutex is created the list must be scanned and each interrupt updated. Interrupts do not know "exactly" which mutexes they will need, they know about a subset of the mutexes they may need, this scheme causes several problems: 1) interrupts are again fan-in, meaning if you block an interrupt class on one cpu you block them on all cpus 2) when we may have things like per-socket mutexes we are blocking interrupts that may not need twiddling by the interrupt handler, yet we need to block the interrupt anyway because it _may_ want the same mutex that we have. Windriver has a full time developer working on the existing implementation, as far as I know we can only count on you for weekends and spare time. I'm starting to feel that I'm wasting time trying to get you to see the bigger picture; the fact that niether system means diddly unless we get to work on locking the rest of the kernel. With that said, I'd really like to see the better of the two schemes implemented when the dust settles. The problem is that right now neither scheme is buying us much other than overhead without signifigant parts of the kernel being converted over to a mutexed system. Your proposal is valueable and might be something that we switch to, however for the time being it's far more important to work on locking down subsystems than working on the locking subsystem. In fact if you proposed a new macro wrapper for mtx_* that would make it easier at a later date to implement _your_ version of the locking subsystem I would back it just to get you interested in participating in locking down the other subsystems. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:33:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id CCEE837B424 for ; Tue, 17 Apr 2001 18:33:43 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3I1XKv16604; Tue, 17 Apr 2001 18:33:20 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 18:33:20 -0700 (PDT) From: Matt Dillon Message-Id: <200104180133.f3I1XKv16604@earth.backplane.com> To: Bosko Milekic Cc: Greg Lehey , Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> <200104180047.f3I0lN615938@earth.backplane.com> <20010417212045.B14803@technokratis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : You cannot be pre-empted by an interrupt if you are holding a spin : mutex, AFAIK, even under present implementation. Since spin mutexes are going to be held all over the place, this type of restriction would seem to be detrimental. If you can do all the checking up-front it is also unnecessary. : What happens if we get an interrupt, we're thinking about servicing :it, about to check whether we're already holding a mutex that may potentially :be used inside the mainline int routine, and another CPU becomes idle? :In this particular case, let's say that we decide that we have to set :ipending and iret immediately, because we're already holding a potential You could, but you are talking about a very small window of opportunity assuming that we are running similar code to what we have now in regards to assigning the interrupts to a cpu. In 4.x we assign interrupts to whichever cpu is holding Giant. With mutexes we would want to assign interrupts to whichever cpu is idle and if no cpu is idle we round-robin the interrupt assignments (e.g. cpu takes interrupt, assigns all interrupts to the next cpu if no cpus are idle). With that in place, the best course is almost certainly going to be to do nothing ... that is, take the interrupt even though it might not be optimal. If once every X thousand interrupts we happen to hit a case where a cpu remains idle when it doesn't have to be, who gives a flying f**k if that one interrupt is non-optimal? I'm not kidding... that sort of case is not a problem that needs to be solved. : Also, some mainline interrupt code may need to acquire a really :large number of locks, but only in some cases. Let's say we have to first :check if we have a free cached buffer sitting somewhere, and if not, malloc() None of our current interrupt code needs to aquire a huge number of locks, and if some piece of interrupt code is so complex that it does, it should be relegated to a software interrupt (e.g. like the TCP stack). Lets not create problems where they don't exist. If one of our subsystems happened to be require more complexity - for example, the I/O completion handling (biodone() code), it's a solveable problem. Simplification is what is needed here. Creating a complex solution to a complex problem only results in a mess. Simplifying the problem so that it covers most of your codebase and then focusing on the one or two cases it doesn't cover would seem to be a better way of dealing with the issue. :lock operations, but only in the case where we lack the cached buffer to :allocate it. There is no practical way of telling up front whether or not :we'll have to malloc(), so I'm wondering how efficiently we would be able :to predict in cases such as these? : :Cheers, :-- : Bosko Milekic It could very well be that for an interrupt we might need to list two mutexes --- one for the memory subsystem and one for the interrupt's subsystem. It would be nice if we could get away with one, but having to list two or even three mutexes would not be much of a burden on the interrupt code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:37:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 87D4837B443 for ; Tue, 17 Apr 2001 18:37:27 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I1Zjg14354; Wed, 18 Apr 2001 01:35:45 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 01:35:44 +0000 (GMT) From: "E.B. Dreger" To: Bosko Milekic Cc: Matt Dillon , Greg Lehey , Alfred Perlstein , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: <20010417212045.B14803@technokratis.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 > Date: Tue, 17 Apr 2001 21:20:45 -0400 > From: Bosko Milekic > > What happens if we get an interrupt, we're thinking about servicing > it, about to check whether we're already holding a mutex that may > potentially be used inside the mainline int routine, and another CPU > becomes idle? In this particular case, let's say that we decide that we > have to set ipending and iret immediately, because we're already holding > a potential lock when we got interrupted. Isn't the result that we have > a second CPU idling while we just set ipending? (I could be missing > something, really). (Thinking hard... this is fun stuff...) > Also, some mainline interrupt code may need to acquire a really large > number of locks, but only in some cases. Let's say we have to first > check if we have a free cached buffer sitting somewhere, and if not, > malloc() a new one. Well, the malloc() will eventually trigger a chain > of mutex lock operations, but only in the case where we lack the cached > buffer to allocate it. There is no practical way of telling up front > whether or not we'll have to malloc(), so I'm wondering how efficiently > we would be able to predict in cases such as these? In this case, why not have a memory allocator similar to Hoard? Let's say that I have a four-way system with 256 MB. First CPU gets first 64 MB, second gets the next 64 MB, and so on. Now we needn't lock before malloc(), because each CPU knows ahead of time what is "off limits". When one reaches a high water mark, it steals half the available space from the CPU with the least memory utilization. This _would_ require a lock, but should only happen in rare instances. I know that memory could become fragmented over time, but as long as we don't screw up caching (which shouldn't be a problem considering that pages are much larger than cache lines), who cares? Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:45:56 2001 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 34CE337B443 for ; Tue, 17 Apr 2001 18:45:54 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3I1jpH03686; Tue, 17 Apr 2001 18:45:51 -0700 (PDT) Date: Tue, 17 Apr 2001 18:45:51 -0700 From: Alfred Perlstein To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: More on Bad Bug Message-ID: <20010417184551.B976@fw.wintelcom.net> References: <200104172328.QAA01367@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104172328.QAA01367@usr09.primenet.com>; from tlambert@primenet.com on Tue, Apr 17, 2001 at 11:28:46PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [010417 16:28] wrote: > > I guess no one else is interested in this bug hunt, or no one else > is using 30,000 sockets on any of their machines? I've committed a variation of your invariants check to -current, -stable is frozen and I'd prefer to leave it as is until after the release date. As far as tracking down the problem I don't have the resources in terms of hardware, code and time for that right now, however it looks like you've found a possible bug. Please keep us in the loop on this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:48:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 24DAA37B43F for ; Tue, 17 Apr 2001 18:48:33 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I1m7B14438; Wed, 18 Apr 2001 01:48:07 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 01:48:06 +0000 (GMT) From: "E.B. Dreger" To: Alfred Perlstein Cc: Matt Dillon , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: <20010417182840.A976@fw.wintelcom.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 > Date: Tue, 17 Apr 2001 18:28:40 -0700 > From: Alfred Perlstein > > 1) interrupts are again fan-in, meaning if you block an interrupt > class on one cpu you block them on all cpus When would this be a bad case? i.e., if an interrupt [class] must be blocked, would we not it blocked across the board? Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:52: 6 2001 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 32A2737B43E for ; Tue, 17 Apr 2001 18:52:04 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3I1pmW03912; Tue, 17 Apr 2001 18:51:48 -0700 (PDT) Date: Tue, 17 Apr 2001 18:51:48 -0700 From: Alfred Perlstein To: "E.B. Dreger" Cc: Bosko Milekic , Matt Dillon , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010417185148.D976@fw.wintelcom.net> References: <20010417212045.B14803@technokratis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Wed, Apr 18, 2001 at 01:35:44AM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * E.B. Dreger [010417 18:36] wrote: > > In this case, why not have a memory allocator similar to Hoard? It doesn't work, but it's close: http://people.freebsd.org/~alfred/memcache/ -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 18:53:11 2001 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 00E2C37B422 for ; Tue, 17 Apr 2001 18:53:09 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3I1qsm03948; Tue, 17 Apr 2001 18:52:54 -0700 (PDT) Date: Tue, 17 Apr 2001 18:52:54 -0700 From: Alfred Perlstein To: "E.B. Dreger" Cc: Matt Dillon , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) Message-ID: <20010417185254.E976@fw.wintelcom.net> References: <20010417182840.A976@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Wed, Apr 18, 2001 at 01:48:06AM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * E.B. Dreger [010417 18:48] wrote: > > Date: Tue, 17 Apr 2001 18:28:40 -0700 > > From: Alfred Perlstein > > > > 1) interrupts are again fan-in, meaning if you block an interrupt > > class on one cpu you block them on all cpus > > When would this be a bad case? i.e., if an interrupt [class] must be > blocked, would we not it blocked across the board? It'd be nice if you had something like 16 nic cards working independantly of each other to not be in the same collision domain if they don't have to. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19: 6:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id EEF0637B440 for ; Tue, 17 Apr 2001 19:06:13 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3I268716829; Tue, 17 Apr 2001 19:06:08 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 19:06:08 -0700 (PDT) From: Matt Dillon Message-Id: <200104180206.f3I268716829@earth.backplane.com> To: Alfred Perlstein Cc: Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) References: <200104160259.f3G2xqs06321@aslan.scsiguy.com> <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <20010418093212.A80877@wantadilla.lemis.com> <200104180047.f3I0lN615938@earth.backplane.com> <20010417182840.A976@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Mutex creation can be expensive as it seems like each interrupt : needs to register what sort of mutex it's interested in, when a : mutex is created the list must be scanned and each interrupt : updated. The list is based in the interrupt structure. The cost is, what, four or five instructions in a loop for which the vast majority will only have to iterate once. All the operations are read-only unless you get a hit. Very cheap. It would be nice if the list could be fixed to one or two items... same number of instructions, but no loop, fewer memory accesses, and cheaper to execute. The only interrupts we care about in regards to the efficiency of this design are: network interrupts and I/O interrupts, yes? Network interrupts can get away with one or two mutexes (memory and queue, or perhaps even just memory). I/O interrupts are a stickier issue but up until softupdates the only thing biodone() did was release a lock already held, so it wouldn't be an issue. I think softupdates relegates nearly all of its work to a software interrupt or process so softupdates would not represent a problem either. I'd have to review it. I made one change to the VM system in 4.x which was to free swap indirectly from biodone which I would have to rip out, but that would pretty much be it. : Interrupts do not know "exactly" which mutexes they will need, they : know about a subset of the mutexes they may need, this scheme causes : several problems: : 1) interrupts are again fan-in, meaning if you block an interrupt : class on one cpu you block them on all cpus They don't have to be. If you have four NICs each one can be its own interrupt, each with its own mutex. Thus all four can be taken in parallel. I was under the impression that BSDI had achieved that in their scheme. If you have one NIC then obviously you can't take multiple interrupts for that one NIC on different cpu's. No great loss, you generally don't want to do that anyway. : 2) when we may have things like per-socket mutexes we are blocking : interrupts that may not need twiddling by the interrupt handler, : yet we need to block the interrupt anyway because it _may_ want : the same mutex that we have. Network interrupts do not mess around with sockets. The packets are passed to a software interrupt level which is certainly a more heavyweight entity. I can be argued very easily that the TCP stack should operate as a thread -- actually, one thread for each cpu, so if you have a lot of TCP activity you can activate several threads and process TCP operations in parallel. (IRIX did this to good effect). Nobody should ever do complex processing in an interrupt, period. If you need to do complex processing, you do it in a software interrupt (in -stable), or a thread in the new design. : Windriver has a full time developer working on the existing : implementation, as far as I know we can only count on you for : weekends and spare time. Doesn't effect the discussion, really. It's nice that people are dedicated to the project. I wish someone were in charge of it, like Linus is in charge of Linux. When my time frees up (A year from now? Less? More? I don't know).. when my time frees up I am going to start working from whatever platform is the most stable. If 5.x isn't stable by that time it's probably hopeless and I'll have to start work from the 4.x base. If 5.x is stable then I'll be able to start from 5.x. I know that sounds harsh, but it's a realistic view. I truely do not believe that SMPifying things needs to be this difficult, if only people would focus on the things that matter and stop trying to throw the kitchen sink into -current (especially without adequate testing). That's my beef with current. I find it ironic that I was shot down for not following the BSDI mutex model in the name of compatibility when I did that first push, but when other people started messing with the system compatibility went flying right out the window. Very ironic. :neither scheme is buying us much other than overhead without :signifigant parts of the kernel being converted over to a mutexed :system. : :Your proposal is valueable and might be something that we switch :to, however for the time being it's far more important to work on :locking down subsystems than working on the locking subsystem. : :In fact if you proposed a new macro wrapper for mtx_* that would :make it easier at a later date to implement _your_ version of the :locking subsystem I would back it just to get you interested in :participating in locking down the other subsystems. : :-Alfred I wasn't really proposing a new macro wrapper, it was just pseudo code. If I were doing mutexes from scratch I would scrap all the fancy features and just have spin mutexes, period. One argument (pointer to the mutex), simplified operation, optional debugging, done. Complexity breeds bugs. Bugs prevent adoption, lack of adoption results in death. Death not good. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19:21:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id A8B3D37B43E for ; Tue, 17 Apr 2001 19:21:40 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I2L5714802; Wed, 18 Apr 2001 02:21:05 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 02:21:04 +0000 (GMT) From: "E.B. Dreger" To: Matt Dillon Cc: Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: <200104180206.f3I268716829@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 17 Apr 2001 19:06:08 -0700 (PDT) > From: Matt Dillon > > They don't have to be. If you have four NICs each one can be its own > interrupt, each with its own mutex. Thus all four can be taken in > parallel. I was under the impression that BSDI had achieved that > in their scheme. IIRC, didn't the NT driver for some NIC (Intel?) switch to polling, anyway, under heavy load? The reasoning being that you _know_ that you're going to get something... why bother an IRQ hit? That said, IRQ distribution sounds like a good thing for the general case. > If you have one NIC then obviously you can't take multiple interrupts > for that one NIC on different cpu's. No great loss, you generally don't > want to do that anyway. Actually, I should think that one would _want_ to serialize traffic for a given NIC. (I'm ignoring when one trunks NICs... speaking of which, anyone have info on 802.3ad? ;-) Otherwise, one ends up with a race that [potentially] screws up packet sequence. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19:35: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id D080537B43C for ; Tue, 17 Apr 2001 19:34:58 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3I2Yuq17047; Tue, 17 Apr 2001 19:34:56 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 19:34:56 -0700 (PDT) From: Matt Dillon Message-Id: <200104180234.f3I2Yuq17047@earth.backplane.com> To: "E.B. Dreger" Cc: Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :IIRC, didn't the NT driver for some NIC (Intel?) switch to polling, :anyway, under heavy load? The reasoning being that you _know_ that you're :going to get something... why bother an IRQ hit? : :That said, IRQ distribution sounds like a good thing for the general case. Under a full load polling would work just as well as an interrupt. With NT for the network tests they hardwired each NIC to a particular CPU. I don't know if they did any polling or not. :> If you have one NIC then obviously you can't take multiple interrupts :> for that one NIC on different cpu's. No great loss, you generally don't :> want to do that anyway. : :Actually, I should think that one would _want_ to serialize traffic for a :given NIC. (I'm ignoring when one trunks NICs... speaking of which, :anyone have info on 802.3ad? ;-) Otherwise, one ends up with a race that :[potentially] screws up packet sequence. : :Eddy Yes. Also NICs usually have circular buffers for packets so, really, only one cpu can be processing a particular NIC's packets at any given moment. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19:40: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 385C437B424 for ; Tue, 17 Apr 2001 19:39:58 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I2deW15016; Wed, 18 Apr 2001 02:39:40 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 02:39:39 +0000 (GMT) From: "E.B. Dreger" To: Matt Dillon Cc: Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: <200104180234.f3I2Yuq17047@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 17 Apr 2001 19:34:56 -0700 (PDT) > From: Matt Dillon > > Yes. Also NICs usually have circular buffers for packets so, really, > only one cpu can be processing a particular NIC's packets at any given > moment. We could always have a mutex for each NIC's ring buffer... *ducking and running* Sorry... couldn't resist. :-) Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19:41:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id A644337B496 for ; Tue, 17 Apr 2001 19:41:27 -0700 (PDT) (envelope-from janb@cs.utep.edu) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.11.3/8.11.3) with ESMTP id f3I2eaf17153; Tue, 17 Apr 2001 20:40:37 -0600 (MDT) Date: Tue, 17 Apr 2001 20:40:38 -0600 (MDT) From: X-Sender: To: "E.B. Dreger" Cc: Matt Dillon , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) 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 > IIRC, didn't the NT driver for some NIC (Intel?) switch to polling, > anyway, under heavy load? The reasoning being that you _know_ that you're > going to get something... why bother an IRQ hit? THis is very interesting. How does this affect performance? JAn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 19:47:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 6408337B42C for ; Tue, 17 Apr 2001 19:47:16 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id TAA27875 for ; Tue, 17 Apr 2001 19:47:14 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpdAAAeKaOx2; Tue Apr 17 19:47:03 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id TAA06343 for current@freebsd.org; Tue, 17 Apr 2001 19:47:24 -0700 (MST) From: Terry Lambert Message-Id: <200104180247.TAA06343@usr09.primenet.com> Subject: Bad Bug update To: current@freebsd.org Date: Wed, 18 Apr 2001 02:47:13 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] 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 Just an update... ] In any case, I'm leaving in the panic patch I sent earlier, and am ] now rebuilding with my ucred reference count moved past the area Moving the reference count of of the range of the stop clears up the invariant corruption complaint. It is now abundantly clear that a credential is being freed while there is still a reference to it. So either somone is not doing a crhold(), or crfree() is being called one too many times, when you have a boatload of fd's that are sockets. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 20: 5:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 9C75337B42C for ; Tue, 17 Apr 2001 20:05:16 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-114.cwb-adsl.brasiltelecom.net.br [200.193.160.114]) by netbank.com.br (Postfix) with ESMTP id 18F824680A; Wed, 18 Apr 2001 00:05:58 -0300 (BRST) Received: from localhost (vatcnq@localhost [127.0.0.1]) by surriel.ddts.net (8.11.2/8.11.2) with ESMTP id f3I34Cf00384; Wed, 18 Apr 2001 00:04:22 -0300 Date: Wed, 18 Apr 2001 00:04:12 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Matt Dillon Cc: "E.B. Dreger" , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: <200104180234.f3I2Yuq17047@earth.backplane.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Matt Dillon wrote: > Under a full load polling would work just as well as an interrupt. > With NT for the network tests they hardwired each NIC to a particular > CPU. I don't know if they did any polling or not. Not true. Interrupts work worse than polling because the interrupt top halves can keep the CPU busy, whereas with polling you only peek at the card when you have time. This means pure interrupts can possibly DoS a CPU (think about a gigabit ping flood) while polling leaves the box alive and still allows it to process as much as it can (while not wasting CPU on taking in packets it cannot process higher up the stack). regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 20:12:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 935A137B423 for ; Tue, 17 Apr 2001 20:12:41 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I3Bwh15485; Wed, 18 Apr 2001 03:11:58 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 03:11:57 +0000 (GMT) From: "E.B. Dreger" To: Rik van Riel Cc: Matt Dillon , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) 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 > Date: Wed, 18 Apr 2001 00:04:12 -0300 (BRST) > From: Rik van Riel > > Not true. Interrupts work worse than polling because the interrupt > top halves can keep the CPU busy, whereas with polling you only Top halves and _task switching_. Again, in a well-written handler with a tight loop, task switching becomes expensive. > peek at the card when you have time. Think aio_xxxx versus kernel queues. :-) > This means pure interrupts can possibly DoS a CPU (think about a > gigabit ping flood) while polling leaves the box alive and still > allows it to process as much as it can (while not wasting CPU on > taking in packets it cannot process higher up the stack). I should hope that the card would be smart enough to combine consecutive packets into a single DMA transfer, but I know what you mean. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 20:23:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 8B92C37B423 for ; Tue, 17 Apr 2001 20:23:54 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I3NZD15585; Wed, 18 Apr 2001 03:23:35 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 03:23:34 +0000 (GMT) From: "E.B. Dreger" To: Rik van Riel Cc: Matt Dillon , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) 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 Going back to basic principles: For minimal CPU utilization, it would be nice skip task switching, period. Run something to completion, then go on to the next task. Poll without ever using an interrupt. The problem is that latency becomes totally unacceptable. So now let's go to the other extreme: Create a Transputer-like array with hundreds of 65xx-complexity CPUs. Each atomic task runs on its own private CPU. The problem is that the electronics become a pain, and are often idle. When too many tasks are launched, we run out of CPU power. The compromise is to switch tasks on whatever CPU power is available... balancing switching overhead with latency. *Let the latency be as high as is acceptable to reduce overhead as low as is practical.* Hence, my philosophy is that task switching and preemption are necessary evils because hardware does not perfectly accomodate software. If we must, we must... otherwise, use co-op switching as the next best thing to straight run-to-completion. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 21: 4:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 2948037B43E for ; Tue, 17 Apr 2001 21:04:09 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 95BED28769; Wed, 18 Apr 2001 11:04:01 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 7D7B7286FD; Wed, 18 Apr 2001 11:04:01 +0700 (ALMST) Date: Wed, 18 Apr 2001 11:04:01 +0700 (ALMST) From: Boris Popov To: User & Cc: freebsd-current@freebsd.org Subject: Re: mounting netware fs In-Reply-To: <20010418022836.A494@enia.bastun.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 Wed, 18 Apr 2001, User & wrote: > mount -a -t nonfs > > to > > # Mount everything except nfs filesystems. > mount -a -t nonfs,nwfs > > In the first case at boot time the machine stops and wants me to enter > in shell and fix the problem. I don't know whether I'm right, but I > think that my modification can help. Well, nwfs and smbfs can be added to the list along with nfs. However I would recommend to use 'noauto' modifier and the shell script like one in the /usr/share/examples/nwclient -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 21: 5:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 7CC5437B423 for ; Tue, 17 Apr 2001 21:05:35 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 7D80F287FD; Wed, 18 Apr 2001 11:05:28 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 74BE1287E3; Wed, 18 Apr 2001 11:05:28 +0700 (ALMST) Date: Wed, 18 Apr 2001 11:05:28 +0700 (ALMST) From: Boris Popov To: estair@computer-exchange.com Cc: freebsd-current@freebsd.org Subject: Re: mount_smbfs missing, SAMBA package installed, where is it? In-Reply-To: <002a01c0c76c$a4fe52a0$4900a8c0@mshome.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001 estair@computer-exchange.com wrote: > I'm running 5.0-Current-4.12.2001, X-Kern-Developer with all binaries, > have just installed the samba package (pkg_add -r samba) but the smb > client services, specifically mount_smbfs, aren't installed. mount_smbfs doesn't belong to the Samba package. Take a look at ports/net/smbfs. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 17 21:39:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 3E72437B422 for ; Tue, 17 Apr 2001 21:39:22 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-114.cwb-adsl.brasiltelecom.net.br [200.193.160.114]) by netbank.com.br (Postfix) with ESMTP id CB64946805; Wed, 18 Apr 2001 01:40:06 -0300 (BRST) Received: from localhost (tmogbd@localhost [127.0.0.1]) by surriel.ddts.net (8.11.2/8.11.2) with ESMTP id f3I4cEf01755; Wed, 18 Apr 2001 01:38:25 -0300 Date: Wed, 18 Apr 2001 01:38:14 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: "E.B. Dreger" Cc: Matt Dillon , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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, 18 Apr 2001, E.B. Dreger wrote: > For minimal CPU utilization, it would be nice skip task switching, > period. Run something to completion, then go on to the next task. > Poll without ever using an interrupt. [snip] > Hence, my philosophy is that task switching and preemption are > necessary evils because hardware does not perfectly accomodate > software. If we must, we must... otherwise, use co-op switching as > the next best thing to straight run-to-completion. Except that for the [extremely performance critical] interrupt handlers the "software" is under control of the folks who write the OS. You need preemption for userspace because it's possibly "hostile" software, but things like the interrupt handlers and the kernel code are under your control ... this means you can code it to be as efficient as possible without impacting latency too much. regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 1:34:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 1A91E37B423 for ; Wed, 18 Apr 2001 01:34:12 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f3I8Y3798290; Wed, 18 Apr 2001 10:34:04 +0200 (CEST) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f3I8XXo53611; Wed, 18 Apr 2001 10:33:33 +0200 (CEST) (envelope-from asmodai) Date: Wed, 18 Apr 2001 10:33:32 +0200 From: Jeroen Ruigrok/Asmodai To: Matt Dillon Cc: Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan Langille Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010418103332.B45919@daemon.ninth-circle.org> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <200104171724.f3HHOqh94775@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200104171724.f3HHOqh94775@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 10:24:52AM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010417 20:47], Matt Dillon (dillon@earth.backplane.com) wrote: > Testing it 'on' in stable on production systems and observing the > relative change in performance is a worthy experiment. Testing it > 'on' in current is just an experiment. I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last week or so. Still no problems. Been doing massive cvsups and all that. This is not in combination with softupdates. That's next on the agenda. I think Dan Langille enabled it on a cvsupd server he has set up after I mentioned this sysctl to him. Dan? -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 We decide who's crazy or not... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 1:48:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 4082937B422 for ; Wed, 18 Apr 2001 01:48:26 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f3I8mMv43026; Wed, 18 Apr 2001 10:48:22 +0200 (CEST) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f3I8mJb53795; Wed, 18 Apr 2001 10:48:19 +0200 (CEST) (envelope-from asmodai) Date: Wed, 18 Apr 2001 10:48:18 +0200 From: Jeroen Ruigrok/Asmodai To: Alfred Perlstein Cc: Matt Dillon , "Justin T. Gibbs" , Doug Barton , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010418104818.C45919@daemon.ninth-circle.org> References: <200104160616.f3G6GI973782@earth.backplane.com> <20010417011957.W976@fw.wintelcom.net> <200104171722.f3HHMpt94518@earth.backplane.com> <20010417130210.K976@fw.wintelcom.net> <200104172051.f3HKpAF06881@earth.backplane.com> <20010417135336.Q976@fw.wintelcom.net> <200104172107.f3HL7ei07632@earth.backplane.com> <20010417145206.T976@fw.wintelcom.net> <200104172200.f3HM0TI09802@earth.backplane.com> <20010417153612.W976@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010417153612.W976@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Apr 17, 2001 at 03:36:12PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010418 01:00], Alfred Perlstein (bright@wintelcom.net) wrote: > (although afaik we're basing it on both Solaris and BSD/os's > implementation so... well I'm not going to bother defending it.) You just scared the shit out of me by mentioning Solaris. I've found Solaris to be a PITA with all new subsequent releases. Surely we're not aiming towards their goals where we can only run on state of the art hardware? -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Expansion of happiness is the purpose of life... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 2:25:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id BEF1737B619; Wed, 18 Apr 2001 02:25:16 -0700 (PDT) (envelope-from n_hibma@FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.11.3/8.11.3) with ESMTP id f3I9PCr92566; Wed, 18 Apr 2001 10:25:12 +0100 (BST) (envelope-from n_hibma@FreeBSD.ORG) Date: Wed, 18 Apr 2001 10:25:12 +0100 (BST) From: X-X-Sender: To: Nick Sayer Cc: , Subject: Re: hid_report_size() prototype wrong in both -stable and -current In-Reply-To: <1087.207.5.33.65.987532780.squirrel@medusa.kfu.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 Concidental. The code that is in libusb is also present in the kernel. Nick On Tue, 17 Apr 2001, Nick Sayer wrote: > > > > usb.h != libusb.h > > > > NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. > > Ok. That's as may be, but then why are there prototypes for libusb calls in > dev/usb.h? > > > > > The prototypes are correct as is. > > They may be in libusb.h, but the prototype for that function in > sys/dev/usb.h is mysterious. > > -- The USB for FreeBSD project. n_hibma@FreeBSD.ORG http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 5:17:18 2001 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 53F3237B423 for ; Wed, 18 Apr 2001 05:17:13 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA08487; Wed, 18 Apr 2001 22:16:58 +1000 Date: Wed, 18 Apr 2001 22:16:02 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jeroen Ruigrok/Asmodai Cc: Matt Dillon , Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan Langille Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <20010418103332.B45919@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 Wed, 18 Apr 2001, Jeroen Ruigrok/Asmodai wrote: > -On [20010417 20:47], Matt Dillon (dillon@earth.backplane.com) wrote: > > Testing it 'on' in stable on production systems and observing the > > relative change in performance is a worthy experiment. Testing it > > 'on' in current is just an experiment. > > I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last > week or so. Still no problems. Been doing massive cvsups and all > that. > This is not in combination with softupdates. That's next on the agenda. So, how much slower was it? ;-) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 5:57:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id A60F037B42C for ; Wed, 18 Apr 2001 05:57:29 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f3ICvMP26767; Wed, 18 Apr 2001 14:57:22 +0200 (CEST) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f3ICtIf55642; Wed, 18 Apr 2001 14:55:18 +0200 (CEST) (envelope-from asmodai) Date: Wed, 18 Apr 2001 14:55:17 +0200 From: Jeroen Ruigrok/Asmodai To: Bruce Evans Cc: Matt Dillon , Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan Langille Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010418145517.J45919@daemon.ninth-circle.org> References: <20010418103332.B45919@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bde@zeta.org.au on Wed, Apr 18, 2001 at 10:16:02PM +1000 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010418 14:38], Bruce Evans (bde@zeta.org.au) wrote: [vfs.vmiodirenable] >So, how much slower was it? ;-) Not noticeable for me at least. -- Jeroen Ruigrok van der Werven/Asmodai --=-- asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best http://www.freebsd.org/doc/en_US.ISO_8859-1/books/developers-handbook/ Cogito, ergo sum... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 6:10: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id B90A137B42C for ; Wed, 18 Apr 2001 06:09:56 -0700 (PDT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3ID9Th19647; Wed, 18 Apr 2001 13:09:29 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Wed, 18 Apr 2001 13:09:29 +0000 (GMT) From: "E.B. Dreger" To: Rik van Riel Cc: Matt Dillon , Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) 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 > Date: Wed, 18 Apr 2001 01:38:14 -0300 (BRST) > From: Rik van Riel > > > Hence, my philosophy is that task switching and preemption are > > necessary evils because hardware does not perfectly accomodate > > software. If we must, we must... otherwise, use co-op switching as > > the next best thing to straight run-to-completion. > > Except that for the [extremely performance critical] interrupt > handlers the "software" is under control of the folks who write > the OS. > > You need preemption for userspace because it's possibly "hostile" > software, but things like the interrupt handlers and the kernel > code are under your control ... this means you can code it to be > as efficient as possible without impacting latency too much. Right. This is why I think that messing with pre-emption inside interrupt handlers is a bad thing. If kernel code doesn't cooperatively time-share, then we likely have bigger problems than task switching. :-) Hence I'm curious about replacing Giant with a token-passing mechanism. If the token equals your CPU number, you have "Giant"... do what's needed. Then set the token to the next CPU, and do what doesn't require "Giant". Matt pointed out (to me off-list IIRC) that the mutex usually shouldn't have to spin. However, passing a token would involve changing the value of some known memory location... that should be even faster and simpler than a mutex. No bus locking, no spinning... AFAIK, there isn't any "good" support specifically for token passing. But memory reads and writes that don't even require the lock prefix... how much faster and simpler can you get? Want finer-grained control than "Giant"? Any time you have "Giant"/token, you can poll (and claim, if available) any more-specific mutex. Nobody else has G/tk, so there would be no races. By using fine-grained co-op mutexes, there is very little that must be done when we have G/tk, thus minimizing wait for G/tk. Note, too, that we run our standard scheduler when we don't yet have G/tk, so we're not even blocking unless the CPU is totally idle... and then, the degenerate case is spinning. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 6:32:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id E6CED37B422 for ; Wed, 18 Apr 2001 06:32:29 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3IDWCm65855; Thu, 19 Apr 2001 01:32:13 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104181332.f3IDWCm65855@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: Jeroen Ruigrok/Asmodai Date: Wed, 18 Apr 2001 09:32:08 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FW: Filesystem gets a huge performance boost Reply-To: dan@langille.org Cc: Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan Langille In-reply-to: <20010418103332.B45919@daemon.ninth-circle.org> References: <200104171724.f3HHOqh94775@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Apr 17, 2001 at 10:24:52AM -0700 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Apr 2001, at 10:33, Jeroen Ruigrok/Asmodai wrote: > -On [20010417 20:47], Matt Dillon (dillon@earth.backplane.com) wrote: > > Testing it 'on' in stable on production systems and observing the > > relative change in performance is a worthy experiment. Testing it > > 'on' in current is just an experiment. > > I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last > week or so. Still no problems. Been doing massive cvsups and all that. > This is not in combination with softupdates. That's next on the agenda. > > I think Dan Langille enabled it on a cvsupd server he has set up after I > mentioned this sysctl to him. Dan? I've seen no problems at all. This is cvsup.nz.freebsd.org: [dan@cvsup:/usr/home/dan] $ sysctl vfs.vmiodirenable vfs.vmiodirenable: 1 $ uptime 1:29AM up 27 days, 14:06, 1 user, load averages: 0.00, 0.02, 0.05 As for how highly stressed this box is: $ zgrep -c "\+" cvsupd.log* cvsupd.log:5 cvsupd.log.0.gz:27 cvsupd.log.1.gz:134 cvsupd.log.2.gz:49 cvsupd.log.3.gz:22 cvsupd.log.4.gz:26 cvsupd.log.5.gz:18 cvsupd.log.6.gz:39 cvsupd.log.7.gz:24 It's a P120 with 64MB of RAM... I can't comment on the performance boost. Merely that it's been stable. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 6:35:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 0A1ED37B424 for ; Wed, 18 Apr 2001 06:35:36 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3IDZDm65892; Thu, 19 Apr 2001 01:35:14 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104181335.f3IDZDm65892@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: Bruce Evans Date: Wed, 18 Apr 2001 09:35:08 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FW: Filesystem gets a huge performance boost Reply-To: dan@langille.org Cc: Matt Dillon , Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan.Langi@ns1.unixathome.org References: <20010418103332.B45919@daemon.ninth-circle.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Apr 2001, at 22:16, Bruce Evans wrote: > On Wed, 18 Apr 2001, Jeroen Ruigrok/Asmodai wrote: > > > -On [20010417 20:47], Matt Dillon (dillon@earth.backplane.com) wrote: > > > Testing it 'on' in stable on production systems and observing the > > > relative change in performance is a worthy experiment. Testing it > > > 'on' in current is just an experiment. > > > > I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last > > week or so. Still no problems. Been doing massive cvsups and all that. > > This is not in combination with softupdates. That's next on the agenda. > > So, how much slower was it? ;-) $ uname -a FreeBSD cvsup.nz.freebsd.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Mar 8 01:24:24 NZDT 2001 root@xeon.int.nz.freebsd.org:/usr/src/sys/compile/ZEKE i386 The box I mentioned in my previous message is running softupdates. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 9: 9:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E3B737B424; Wed, 18 Apr 2001 09:09:20 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: from shalmaneser.enst.fr (shalmaneser.enst.fr [137.194.160.128]) by infres.enst.fr (Postfix) with ESMTP id 00C3E1892; Wed, 18 Apr 2001 18:09:18 +0200 (MET DST) Received: by shalmaneser.enst.fr (Postfix, from userid 11117) id 4FAE6112B4; Wed, 18 Apr 2001 18:09:18 +0200 (CEST) Date: Wed, 18 Apr 2001 18:09:18 +0200 From: Thomas Quinot To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010418180917.A6832@shalmaneser.enst.fr> Reply-To: Thomas Quinot References: <20010417163318.A47398@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010417163318.A47398@sunbay.com>; from ru@FreeBSD.org on Tue, Apr 17, 2001 at 04:33:18PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-04-17, Ruslan Ermilov écrivait : > It is my great pleasure to announce the availability of just released > Groff 1.17. Please refer to the src/contrib/groff/NEWS for details on > what's new in this release. Hum. I have just made world, and can't format man pages anymore. All I get is the following on stdout: Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) Should this have been `.Em ...'? User Abort. Done. Sources are from cvsup a few hours ago from now. Thomas. -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 9:14:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 3232037B422 for ; Wed, 18 Apr 2001 09:14:47 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f3IGIPI99727 for freebsd-current@freebsd.org; Wed, 18 Apr 2001 09:18:25 -0700 (PDT) (envelope-from sgk) Date: Wed, 18 Apr 2001 09:18:25 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: groff breaks "make -j N buildworld" Message-ID: <20010418091825.A75054@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> src/utils/tfmtodit install -C -c -s -o root -g wheel -m 555 tfmtodit /usr/obj/usr/src/i386/usr/bin ===> tmac cd /usr/src/gnu/usr.bin/groff/tmac/../../../../contrib/groff/tmac; install -C -c -o root -g wheel -m 444 mandoc.tmac andoc.tmac an-old.tmac me.tmac mdoc.tmac pic.tmac a4.tmac safer.tmac trace.tmac ps.tmac psold.tmac pspic.tmac psatk.tmac dvi.tmac tty.tmac tty-char.tmac latin1.tmac X.tmac Xps.tmac lj4.tmac html.tmac mwww.tmac www.tmac eqnrc troffrc troffrc-end hyphen.us /usr/obj/usr/src/i386/usr/share/tmac cd /usr/src/gnu/usr.bin/groff/tmac; install -C -c -o root -g wheel -m 444 hyphen.us-ru /usr/obj/usr/src/i386/usr/share/tmac install -C -c -o root -g wheel -m 444 e.tmac-s /usr/obj/usr/src/i386/usr/share/tmac/e.tmac install: e.tmac-s: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error A standard "make buildworld" appears to work. troutmask:kargl[351] grep FreeBSD /usr/src/Makefile.inc1 # $FreeBSD: src/Makefile.inc1,v 1.197 2001/04/18 12:20:28 ru Exp $ -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 9:20: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 4251937B423 for ; Wed, 18 Apr 2001 09:20:03 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3IGJl838259; Thu, 19 Apr 2001 01:19:48 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.ORG In-Reply-To: <20010418180917.A6832@shalmaneser.enst.fr> References: <20010417163318.A47398@sunbay.com> <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 7 From: Makoto MATSUSHITA To: Thomas Quinot Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Date: Thu, 19 Apr 2001 01:19:30 +0900 Message-Id: <20010419011930Q.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG quinot> Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) quinot> Should this have been `.Em ...'? quinot> User Abort. Same here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 9:23:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 0EF1237B423 for ; Wed, 18 Apr 2001 09:23:46 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3IGNa838352; Thu, 19 Apr 2001 01:23:36 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010419011930Q.matusita@jp.FreeBSD.org> References: <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010419011930Q.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 22 From: Makoto MATSUSHITA To: quinot@inf.enst.fr, current@FreeBSD.ORG Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Date: Thu, 19 Apr 2001 01:23:22 +0900 Message-Id: <20010419012322O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops... my fingers behave badly. quinot> Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) quinot> Should this have been `.Em ...'? quinot> User Abort. Same here. % zcat /usr/share/man/man1/ls.1.gz | nroff -mandoc |& head -2 mdoc error: end-macro (.em) respecification is not allowed. (#41) Should this have been `.Em ...'? % I've extracted whole 5-current distribution as of today, and do chroot(1)... man(1) works quite fine. Maybe it depend of 'old system upgrade to the latest 5-current' problem, but sorry I have no answer to fix. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 9:34:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id DEBF537B422 for ; Wed, 18 Apr 2001 09:34:22 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3IGWX416285; Wed, 18 Apr 2001 19:32:33 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Apr 2001 19:32:33 +0300 From: Ruslan Ermilov To: Thomas Quinot , Makoto MATSUSHITA Cc: current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010418193233.A11193@sunbay.com> Mail-Followup-To: Thomas Quinot , Makoto MATSUSHITA , current@FreeBSD.org References: <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010419011930Q.matusita@jp.FreeBSD.org> <20010419012322O.matusita@jp.FreeBSD.org> <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010418180917.A6832@shalmaneser.enst.fr>; from quinot@inf.enst.fr on Wed, Apr 18, 2001 at 06:09:18PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Unfortunately, I can't reproduce this. I even installed new Groff over the old one, but with no luck to reproduce this. It would be great if you could give me an SSH account on one of the problematic box. On Wed, Apr 18, 2001 at 06:09:18PM +0200, Thomas Quinot wrote: > Le 2001-04-17, Ruslan Ermilov ecrivait : > > > It is my great pleasure to announce the availability of just released > > Groff 1.17. Please refer to the src/contrib/groff/NEWS for details on > > what's new in this release. > > Hum. > > I have just made world, and can't format man pages anymore. All I get > is the following on stdout: > > Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) > Should this have been `.Em ...'? > User Abort. > Done. > > Sources are from cvsup a few hours ago from now. > > Thomas. > > -- > Thomas Quinot ** Departement Informatique & Reseaux ** quinot@inf.enst.fr > ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 On Thu, Apr 19, 2001 at 01:23:22AM +0900, Makoto MATSUSHITA wrote: > > Oops... my fingers behave badly. > > quinot> Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) > quinot> Should this have been `.Em ...'? > quinot> User Abort. > > Same here. > > % zcat /usr/share/man/man1/ls.1.gz | nroff -mandoc |& head -2 > mdoc error: end-macro (.em) respecification is not allowed. (#41) > Should this have been `.Em ...'? > % > > I've extracted whole 5-current distribution as of today, and do > chroot(1)... man(1) works quite fine. > > Maybe it depend of 'old system upgrade to the latest 5-current' > problem, but sorry I have no answer to fix. > > -- - > Makoto `MAR' MATSUSHITA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 10:28:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6484137B423 for ; Wed, 18 Apr 2001 10:28:30 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3IHS3q21008; Wed, 18 Apr 2001 20:28:03 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Apr 2001 20:28:03 +0300 From: Ruslan Ermilov To: Thomas Quinot , Makoto MATSUSHITA , current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010418202803.A18781@sunbay.com> Mail-Followup-To: Thomas Quinot , Makoto MATSUSHITA , current@FreeBSD.org References: <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010419011930Q.matusita@jp.FreeBSD.org> <20010419012322O.matusita@jp.FreeBSD.org> <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010418193233.A11193@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010418193233.A11193@sunbay.com>; from ru@FreeBSD.org on Wed, Apr 18, 2001 at 07:32:33PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 18, 2001 at 07:32:33PM +0300, Ruslan Ermilov wrote: > Hi! > > Unfortunately, I can't reproduce this. I even installed new Groff over > the old one, but with no luck to reproduce this. It would be great if > you could give me an SSH account on one of the problematic box. > OK, got it -- the usual stale /usr/obj problem. This particular one was caused by obsolete doc-* files in /usr/obj/usr/src/gnu/usr.bin/groff/tmac. They should not be there. Previous version created ${.OBJDIR}/doc-common by stripping the contrib/groff/tmac/doc-common file. This worked only because all source files to be stripped were in the same directory. Now, some source files are in the contrib/groff/tmac directory, and some (one actually, koi8-r) is in the ${.CURDIR}, so I had to replace the dependancy line $f: ${DIST_DIR}/$f with $f-s: $f and then install *-s files. What happened here is that make(1) built ${.OBJDIR}/doc-common-s from ${.OBJDIR}/doc-common, but the correct source file is ${DIST_DIR}/doc-common, i.e. /usr/src/contrib/groff/tmac/doc-common. The solution is simple: cd /usr/src/gnu/usr.bin/groff/tmac && make cleandir obj && make all install > On Wed, Apr 18, 2001 at 06:09:18PM +0200, Thomas Quinot wrote: > > Le 2001-04-17, Ruslan Ermilov ecrivait : > > > > > It is my great pleasure to announce the availability of just released > > > Groff 1.17. Please refer to the src/contrib/groff/NEWS for details on > > > what's new in this release. > > > > Hum. > > > > I have just made world, and can't format man pages anymore. All I get > > is the following on stdout: > > > > Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) > > Should this have been `.Em ...'? > > User Abort. > > Done. > > > > Sources are from cvsup a few hours ago from now. > > > > Thomas. > > > > -- > > Thomas Quinot ** Departement Informatique & Reseaux ** quinot@inf.enst.fr > > ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 > > On Thu, Apr 19, 2001 at 01:23:22AM +0900, Makoto MATSUSHITA wrote: > > > > Oops... my fingers behave badly. > > > > quinot> Formatting page, please wait...mdoc error: end-macro (.em) respecification is not allowed. (#41) > > quinot> Should this have been `.Em ...'? > > quinot> User Abort. > > > > Same here. > > > > % zcat /usr/share/man/man1/ls.1.gz | nroff -mandoc |& head -2 > > mdoc error: end-macro (.em) respecification is not allowed. (#41) > > Should this have been `.Em ...'? > > % > > > > I've extracted whole 5-current distribution as of today, and do > > chroot(1)... man(1) works quite fine. > > > > Maybe it depend of 'old system upgrade to the latest 5-current' > > problem, but sorry I have no answer to fix. > > > > -- - > > Makoto `MAR' MATSUSHITA -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 10:33:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by hub.freebsd.org (Postfix) with ESMTP id 0504537B50C for ; Wed, 18 Apr 2001 10:33:23 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: from shalmaneser.enst.fr (shalmaneser.enst.fr [137.194.160.128]) by infres.enst.fr (Postfix) with ESMTP id 504491891; Wed, 18 Apr 2001 19:33:22 +0200 (MET DST) Received: by shalmaneser.enst.fr (Postfix, from userid 11117) id 79967112B4; Wed, 18 Apr 2001 19:33:21 +0200 (CEST) Date: Wed, 18 Apr 2001 19:33:21 +0200 From: Thomas Quinot To: Thomas Quinot , Makoto MATSUSHITA , current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010418193321.B7442@shalmaneser.enst.fr> Reply-To: Thomas Quinot References: <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010419011930Q.matusita@jp.FreeBSD.org> <20010419012322O.matusita@jp.FreeBSD.org> <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010418193233.A11193@sunbay.com> <20010418202803.A18781@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010418202803.A18781@sunbay.com>; from ru@FreeBSD.org on Wed, Apr 18, 2001 at 08:28:03PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-04-18, Ruslan Ermilov écrivait : > cd /usr/src/gnu/usr.bin/groff/tmac && make cleandir obj && make all install It works here, thanks! -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 10:39:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6A21237B42C for ; Wed, 18 Apr 2001 10:39:41 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3IHdLh22124; Wed, 18 Apr 2001 20:39:21 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Apr 2001 20:39:21 +0300 From: Ruslan Ermilov To: Thomas Quinot Cc: Makoto MATSUSHITA , current@FreeBSD.ORG Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Message-ID: <20010418203921.C18781@sunbay.com> Mail-Followup-To: Thomas Quinot , Makoto MATSUSHITA , current@FreeBSD.ORG References: <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010419011930Q.matusita@jp.FreeBSD.org> <20010419012322O.matusita@jp.FreeBSD.org> <20010417163318.A47398@sunbay.com> <20010418180917.A6832@shalmaneser.enst.fr> <20010418193233.A11193@sunbay.com> <20010418202803.A18781@sunbay.com> <20010418193321.B7442@shalmaneser.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010418193321.B7442@shalmaneser.enst.fr>; from quinot@inf.enst.fr on Wed, Apr 18, 2001 at 07:33:21PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 18, 2001 at 07:33:21PM +0200, Thomas Quinot wrote: > Le 2001-04-18, Ruslan Ermilov ecrivait : > > > cd /usr/src/gnu/usr.bin/groff/tmac && make cleandir obj && make all install > > It works here, thanks! > Make sure you delete empty files from /usr/share/man/[en.ISO_8859-1/]cat?/. I will try to fix man(1) tomorrow so that it will not create empty files if groff(1) returns with non-zero exit status. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 10:47:25 2001 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 7F0ED37B422 for ; Wed, 18 Apr 2001 10:47:22 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 4652A5D60; Wed, 18 Apr 2001 19:47:57 +0200 (CEST) Date: Wed, 18 Apr 2001 19:47:57 +0200 From: Jesper Skriver To: Jeroen Ruigrok/Asmodai Cc: Matt Dillon , Doug Barton , "Justin T. Gibbs" , "'current@freebsd.org'" , Dan Langille Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010418194757.B41847@skriver.dk> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <200104171724.f3HHOqh94775@earth.backplane.com> <20010418103332.B45919@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010418103332.B45919@daemon.ninth-circle.org>; from asmodai@wxs.nl on Wed, Apr 18, 2001 at 10:33:32AM +0200 X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 18, 2001 at 10:33:32AM +0200, Jeroen Ruigrok/Asmodai wrote: > -On [20010417 20:47], Matt Dillon (dillon@earth.backplane.com) wrote: > > Testing it 'on' in stable on production systems and observing the > > relative change in performance is a worthy experiment. Testing it > > 'on' in current is just an experiment. > > I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last > week or so. Still no problems. Been doing massive cvsups and all > that. > This is not in combination with softupdates. That's next on the agenda. > > I think Dan Langille enabled it on a cvsupd server he has set up after I > mentioned this sysctl to him. Dan? I've had it running on cvsup.dk.FreeBSD.org + several quite busy RELENG_4 machines here for about 6 to 8 weeks, no problems at all. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) 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 Wed Apr 18 11:35:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from www.mdres.com (www.mdres.com [209.180.205.201]) by hub.freebsd.org (Postfix) with ESMTP id 734FF37B424; Wed, 18 Apr 2001 11:35:25 -0700 (PDT) (envelope-from list-owner@mdres.com) Received: (from petidomo@localhost) by www.mdres.com (8.9.3/8.9.3) id JAA12674; Wed, 18 Apr 2001 09:15:44 -0700 X-Authentication-Warning: www.mdres.com: petidomo set sender to list-owner@mdres.com using -f Received: from mktg ([209.180.205.202]) by www.mdres.com (8.9.3/8.9.3) with SMTP id JAA12670 for ; Wed, 18 Apr 2001 09:15:44 -0700 From: "Hamilton Global Management" To: Subject: New CD-ROM Atlas of Russia - all oblasts, krays, and republics Date: Wed, 18 Apr 2001 10:16:12 -0700 Message-ID: Reply-To: mktg@mdres.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Colleague, Subject: New CD-ROM Atlas of Russia - all oblasts, krays, and republics We have recently acquired a new, unique CD-ROM atlas of the Russian Federation. The atlas displays highly detailed maps of all oblasts, krays, and republics. Visible details include cities, towns, and villages; roads and highways; pipelines; power lines; railroads; canals; forests; bodies of water; mountains; much more. Population figures are also shown for most populated places. Additional details are available for many map objects - e.g., road coverings, route names, as well as specifics about bodies of water and forest cover. Map scales range from 1:200000 to 1:1000000. All the maps show longitude and latitude for any location or object. The atlas uses vector maps based on WGS-84 and Krasovsky systems. We invite you to see sample maps and to get additional information at our web site: http://www.mdres.com/AtlasCatalog/ The CD-ROM atlas is in stock and available for immediate shipment from the USA. It is priced at $165.00 US + $6.00 shipping and handling. Please feel free to send us an e-mail or call if you have any questions. Our customers have previously included major libraries, map centers, universities, international and national agencies, and individuals from around the world. Sincerely, David C. Andresen Vice-President P.S. This e-mail is being sent to you as a person interested in atlases and maps. If you do not wish to receive future e-mails about our map products from Russia, please let us know by return e-mail, and we will remove your e-mail address from our database. Please place the word "Remove" in the message subject box and indicate in the message body the precise e-mail address or addresses you wish us to remove. We do not share our databases with other organi- zations of any type. -------------------------------------- Hamilton Global Management, Ltd. 8103 104th St., S.W. Lakewood, WA 98498 Tel. (253) 588-4149 Fax: (253) 588-4366 E-mail: mktg@mdres.com Web: http://www.mdres.com/AtlasCatalog/ -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 12:54:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 6AF2E37B423 for ; Wed, 18 Apr 2001 12:54:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f3IJsXQ82504; Wed, 18 Apr 2001 12:54:33 -0700 (PDT) Date: Wed, 18 Apr 2001 12:54:33 -0700 (PDT) From: Doug White To: Doug Barton Cc: Alfred Perlstein , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <3ADC0221.32127C39@DougBarton.net> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Doug Barton wrote: > OK... this brings up the question of what other cool optimizations are > there that may have been disabled in the past for reasons that are no > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > with commented out examples of configurations for various systems. For > example, > > # For more modern systems that have a reasonable amount of RAM > #vfs.vmiodirenable=1 > # Low memory systems > # Systems that need lots of randomness > # Low resource systems that need less randomness > # Super high performance TCP options for various situations I smell a book. I was going to write it but I just don't have the time or knowledge. :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Apr 18 15: 7:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id BAF9737B422; Wed, 18 Apr 2001 15:07:26 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id PAA21754; Wed, 18 Apr 2001 15:00:12 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAA9WaqvQ; Wed Apr 18 15:00:01 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA11716; Wed, 18 Apr 2001 15:07:35 -0700 (MST) From: Terry Lambert Message-Id: <200104182207.PAA11716@usr08.primenet.com> Subject: Found BAD BUG: squashed To: arch@freebsd.org Date: Wed, 18 Apr 2001 22:07:25 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have identified the bug. It turns out that the bug causes memory corruption by freeing but continuing to use a credential, and it only occurs in big resource usage cases, and then seemingly at random. It is the fact that there are two credentials per socket, one for the socket, and one for the descriptor itself. The cr_ref is an unsigned short, and ... There is no test for overflow. Thus if I open 65537 files, and close 2, my cred structure is freed. If invariants are on, "0xdeadc0de" is spammed over top of the reference count, and then each time the cread is released, it is decremented: "0xdeadc0dd", "0xdeadc0dc", "0xdeadc0db", ... ...until another "0xc0de" (49374) closes, at which point it frees the already freed credential _again_. The way FreeBSD code is currently structured, this means that the quick-and-ugly fix is simply to change this from u_short to u_long. Further, I moved the cr_ref below the cr_groups declartion -- well out of stomping range of the INVARIANTS code. I have successfully opened 60,000 socket connections (240,000 credential references between the client and server processes combined, and 120,000 each) with this change. -- The real fix is to do as I suggested on -arch earlier today (and then some), and change: crhold(curproc->p_ucred); sigio->sio_ucred = curproc->p_ucred; style things into: sigio->sio_ucred = crhold(curproc->p_ucred); style things. But that is only part of it. Additionally, it needs to be further changed to something like: sigio->sio_ucred = crhold(&curproc->p_ucred); -- passing the address of the credential pointer -- and then (pseudocode), the credential code in crhold() needs to check for an imminent overflow, and when it sees it: struct ucred * crhold(struct ucred **cpp) { struct ucred *ret; if( about_to_overflow) { ret = *cpp; *cpp = crdup(save); } else { ret = *cpp; ret ->cr_ref++; } return ret; } The point of doing this would be to give the FD the overflowing cred, so that new files opened by the process can start counting at 1 again. NOTE: I also suggest chagning free() in kern/kern_malloc.c in free() in the INVARIANTS case, from: --- #ifdef INVARIANTS /* * Check for multiple frees. Use a quick check to see if * it looks free before laboriously searching the freelist. */ if (freep->spare0 == WEIRD_ADDR) { fp = (struct freelist *)kbp->kb_next; while (fp) { if (fp->spare0 != WEIRD_ADDR) panic("free: free item %p modified", fp); else if (addr == (caddr_t)fp) panic("free: multiple freed item %p", addr); fp = (struct freelist *)fp->next; } } --- #ifdef INVARIANTS /* * Check for multiple frees. We can't use a quick check, since * that will give us a false negative for something like a * stomped reference counter or mutex, if it is the first item. */ fp = (struct freelist *)kbp->kb_next; while (fp) { if (fp->spare0 != WEIRD_ADDR) panic("free: free item %p modified", fp); else if (addr == (caddr_t)fp) panic("free: multiple freed item %p", addr); fp = (struct freelist *)fp->next; } --- Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 16:54:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 3D81637B53A for ; Wed, 18 Apr 2001 16:54:21 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3INsJ855653 for ; Thu, 19 Apr 2001 08:54:19 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010418193321.B7442@shalmaneser.enst.fr> References: <20010418193233.A11193@sunbay.com> <20010418202803.A18781@sunbay.com> <20010418193321.B7442@shalmaneser.enst.fr> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 9 From: Makoto MATSUSHITA To: current@FreeBSD.org Subject: Re: ** HEADS UP ** Groff 1.17 (including -mdocNG) imported Date: Thu, 19 Apr 2001 08:54:01 +0900 Message-Id: <20010419085401B.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ru> cd /usr/src/gnu/usr.bin/groff/tmac && make cleandir obj && make all install quinot> It works here, thanks! It works also here. Thanks! -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 20:22:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 9C37637B424 for ; Wed, 18 Apr 2001 20:22:10 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.3/8.11.3) id f3J3M8w56668; Thu, 19 Apr 2001 10:22:08 +0700 (NOVST) (envelope-from nnd) Date: Thu, 19 Apr 2001 10:22:08 +0700 (NOVST) Message-Id: <200104190322.f3J3M8w56668@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: groff breaks "make -j N buildworld" In-Reply-To: <20010418091825.A75054@troutmask.apl.washington.edu> User-Agent: tin/1.5.9-20010328 ("Blue Water") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20010418091825.A75054@troutmask.apl.washington.edu> Steve Kargl wrote: ........ > install -C -c -s -o root -g wheel -m 555 tfmtodit /usr/obj/usr/src/i386/usr/bin > ===> tmac > install -C -c -o root -g wheel -m 444 e.tmac-s /usr/obj/usr/src/i386/usr/share/tmac/e.tmac > install: e.tmac-s: No such file or directory > *** Error code 71 > 1 error > > A standard "make buildworld" appears to work. > > troutmask:kargl[351] grep FreeBSD /usr/src/Makefile.inc1 > # $FreeBSD: src/Makefile.inc1,v 1.197 2001/04/18 12:20:28 ru Exp $ The next patch allows me to 'make -j32 all install' in 'src/gnu/usr.bin/groff/tmac'. N.Dudorov Index: Makefile =================================================================== RCS file: /scratch/CVS/src/gnu/usr.bin/groff/tmac/Makefile,v retrieving revision 1.27 diff -b -u -r1.27 Makefile --- Makefile 2001/04/17 12:37:18 1.27 +++ Makefile 2001/04/19 03:14:14 @@ -37,7 +37,7 @@ STRIPFILES= e.tmac doc.tmac mdoc.local MDOCFILES= doc-common doc-ditroff doc-nroff doc-syms koi8-r -all: ${MDOCFILES:S/$/-s/} ${STRIPFILES:S/$/-s/} ${SPECIALFILES:S/$/-s/} +all: ${MDOCFILES:S/$/-s/} ${STRIPFILES:S/$/-s/} ${SPECIALFILES:S/$/-s/} ${MAN} .for f in ${MDOCFILES} ${STRIPFILES} $f-s: $f @@ -51,6 +51,8 @@ ${.ALLSRC} > ${.TARGET} .endfor +.ORDER: all beforeinstall + beforeinstall: cd ${DIST_DIR}; \ ${INSTALL} -c -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ @@ -59,14 +61,17 @@ ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ hyphen.us-ru ${DESTDIR}${TMACDIR} .for f in ${STRIPFILES} ${SPECIALFILES} + cd ${.OBJDIR}; \ ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ $f-s ${DESTDIR}${TMACDIR}/$f .endfor .for f in ${MDOCFILES} + cd ${.OBJDIR}; \ ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ $f-s ${DESTDIR}${MDOCDIR}/$f .endfor .if !exists(${DESTDIR}${TMACDIR}/man.local) + cd ${.OBJDIR}; \ ${INSTALL} -c -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ ${DIST_DIR}/man.local ${DESTDIR}${TMACDIR} .endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 18 22:36:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from uhura.concentric.net (uhura.concentric.net [206.173.118.93]) by hub.freebsd.org (Postfix) with ESMTP id 964B537B423 for ; Wed, 18 Apr 2001 22:36:08 -0700 (PDT) (envelope-from BenefitsAll@gmx.net) Received: from cliff.concentric.net (cliff.concentric.net [206.173.118.90]) by uhura.concentric.net (8.9.1a/(98/12/15 5.12)) id BAA11074; Thu, 19 Apr 2001 01:36:07 -0400 (EDT) [1-800-745-2747 The Concentric Network] From: Received: from gmx.net ([208.36.180.115]) by cliff.concentric.net (8.9.1a) id BAA27958; Thu, 19 Apr 2001 01:36:06 -0400 (EDT) Date: Thu, 19 Apr 2001 01:36:06 -0400 (EDT) Message-Id: <200104190536.BAA27958@cliff.concentric.net> Reply-To: BenefitsAll@gmx.net To: current@freebsd.org Subject: Donation to your organization 041801 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Friend April 2001 Newsletter Here is another way for your organization to raise money in a painless way Cash rebates of up to 30% from BenefitsAll become welcome donations to your organization when your members shop online with Lands End, Disney, Dell, Gap, Esprit and 300 plus retailers through our web site. Widely endorsed, socially responsible site offers no obligation, free rebate program for members. See how easy it is for your charity to earn substantial cash back for every online, shopping purchase made. To find out more information from BenefitsAll click on reply and we will contact you shortly. Please put "MORE INFO" in the subject box. If you prefer call us toll free at 866 961 2468. Ask for customer service extension 1 To remove you from this list type " REMOVE" in the subject box and click reply. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 1: 4:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 307C337B423 for ; Thu, 19 Apr 2001 01:04:39 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3J845483388; Thu, 19 Apr 2001 11:04:05 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 11:04:05 +0300 From: Ruslan Ermilov To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" Message-ID: <20010419110405.B75677@sunbay.com> Mail-Followup-To: nnd@mail.nsk.ru, current@FreeBSD.ORG References: <20010418091825.A75054@troutmask.apl.washington.edu> <200104190322.f3J3M8w56668@wint.itfs.nsk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104190322.f3J3M8w56668@wint.itfs.nsk.su>; from nnd@mail.nsk.ru on Thu, Apr 19, 2001 at 10:22:08AM +0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I always thought that ``obj'', ``all'' and ``install'' should be executed in sequence, not together. Hey, this even does not work for bin/cat: $ uname -a FreeBSD dev.lan.Awfulhak.org 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Wed Apr 18 14:07:56 BST 2001 brian@dev.lan.Awfulhak.org:/usr/obj/usr/src/sys/DEV i386 $ make obj /usr/obj/net/gate/home/ru/cat created for /net/gate/home/ru/cat $ make -j32 all install -DNOMAN DESTDIR=/tmp/1 BINDIR=/bin BINOWN=ru cc -O -pipe -I/tmp/1/usr/include -c /net/gate/home/ru/cat/cat.c install -c -s -o ru -g wheel -m 555 cat /tmp/1/bin install: cat: No such file or directory *** Error code 71 1 error $ make -j32 all install -DNOMAN DESTDIR=/tmp/1 BINDIR=/bin BINOWN=ru install -c -s -o ru -g wheel -m 555 cat /tmp/1/bin install: cat: No such file or directory *** Error code 71 cc -O -pipe -I/tmp/1/usr/include -o cat cat.o 1 error $ make -j32 all install -DNOMAN DESTDIR=/tmp/1 BINDIR=/bin BINOWN=ru install -c -s -o ru -g wheel -m 555 cat /tmp/1/bin $ OTOH, this seems like a bug in make(1), as the following patch makes -j32 bootstrap-tools happy in gnu/usr.bin/groff/tmac: Index: Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/groff/tmac/Makefile,v retrieving revision 1.27 diff -u -r1.27 Makefile --- Makefile 2001/04/17 12:37:18 1.27 +++ Makefile 2001/04/19 08:01:52 @@ -58,6 +58,7 @@ cd ${.CURDIR}; \ ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ hyphen.us-ru ${DESTDIR}${TMACDIR} + cd ${.OBJDIR} .for f in ${STRIPFILES} ${SPECIALFILES} ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ $f-s ${DESTDIR}${TMACDIR}/$f On Thu, Apr 19, 2001 at 10:22:08AM +0700, nnd@mail.nsk.ru wrote: > In <20010418091825.A75054@troutmask.apl.washington.edu> Steve Kargl wrote: > ........ > > install -C -c -s -o root -g wheel -m 555 tfmtodit /usr/obj/usr/src/i386/usr/bin > > ===> tmac > > install -C -c -o root -g wheel -m 444 e.tmac-s /usr/obj/usr/src/i386/usr/share/tmac/e.tmac > > install: e.tmac-s: No such file or directory > > *** Error code 71 > > 1 error > > > > A standard "make buildworld" appears to work. > > > > troutmask:kargl[351] grep FreeBSD /usr/src/Makefile.inc1 > > # $FreeBSD: src/Makefile.inc1,v 1.197 2001/04/18 12:20:28 ru Exp $ > > The next patch allows me to 'make -j32 all install' in > 'src/gnu/usr.bin/groff/tmac'. > > N.Dudorov > > Index: Makefile > =================================================================== > RCS file: /scratch/CVS/src/gnu/usr.bin/groff/tmac/Makefile,v > retrieving revision 1.27 > diff -b -u -r1.27 Makefile > --- Makefile 2001/04/17 12:37:18 1.27 > +++ Makefile 2001/04/19 03:14:14 > @@ -37,7 +37,7 @@ > STRIPFILES= e.tmac doc.tmac mdoc.local > MDOCFILES= doc-common doc-ditroff doc-nroff doc-syms koi8-r > > -all: ${MDOCFILES:S/$/-s/} ${STRIPFILES:S/$/-s/} ${SPECIALFILES:S/$/-s/} > +all: ${MDOCFILES:S/$/-s/} ${STRIPFILES:S/$/-s/} ${SPECIALFILES:S/$/-s/} ${MAN} > > .for f in ${MDOCFILES} ${STRIPFILES} > $f-s: $f > @@ -51,6 +51,8 @@ > ${.ALLSRC} > ${.TARGET} > .endfor > > +.ORDER: all beforeinstall > + > beforeinstall: > cd ${DIST_DIR}; \ > ${INSTALL} -c -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ > @@ -59,14 +61,17 @@ > ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ > hyphen.us-ru ${DESTDIR}${TMACDIR} > .for f in ${STRIPFILES} ${SPECIALFILES} > + cd ${.OBJDIR}; \ > ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ > $f-s ${DESTDIR}${TMACDIR}/$f > .endfor > .for f in ${MDOCFILES} > + cd ${.OBJDIR}; \ > ${INSTALL} ${COPY} -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ > $f-s ${DESTDIR}${MDOCDIR}/$f > .endfor > .if !exists(${DESTDIR}${TMACDIR}/man.local) > + cd ${.OBJDIR}; \ > ${INSTALL} -c -o ${TMACOWN} -g ${TMACGRP} -m ${TMACMODE} \ > ${DIST_DIR}/man.local ${DESTDIR}${TMACDIR} > .endif > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 1:18:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 66D9A37B423 for ; Thu, 19 Apr 2001 01:18:56 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3J8Iq868180 for ; Thu, 19 Apr 2001 17:18:53 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010419110405.B75677@sunbay.com> References: <200104190322.f3J3M8w56668@wint.itfs.nsk.su> <200104190322.f3J3M8w56668@wint.itfs.nsk.su> <20010419110405.B75677@sunbay.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 10 From: Makoto MATSUSHITA To: current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" Date: Thu, 19 Apr 2001 17:18:41 +0900 Message-Id: <20010419171841Z.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ru> I always thought that ``obj'', ``all'' and ``install'' should be ru> executed in sequence, not together. Hey, this even does not work ru> for bin/cat: IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. I've heard why, but I've forgotten :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 1:44:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5ABFB37B423 for ; Thu, 19 Apr 2001 01:44:20 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 16F996ACBA; Thu, 19 Apr 2001 18:14:19 +0930 (CST) Date: Thu, 19 Apr 2001 18:14:19 +0930 From: Greg Lehey To: FreeBSD current users Subject: Breakage in today's -CURRENT Message-ID: <20010419181419.G72816@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just built a couple of worlds from -CURRENT cvsupped at 2030 UTC on the 18th, and at 0600 UTC on the 19th. In each case, I have massive problems, apparently with the synchronization. Here's some log file output: Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforrwwarardd__hsatradtcclloocckk:: ch ecchkesctkasttea te 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: ffrwaordr_whaarrdd_cstocakt:c lock: checkstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwoarrwd_rds_hatacrldckckl:o cckheckstate : c0h Apr 19 18:11:34 zaphod /boot/kernel/kernel: eckstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwarodr_whaarrdd_cstoactk:lo ccheckstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: k: checkstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: forfwarod_rhaarrdcd_sltoactkc:l occk: checkstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 These blocks repeat exactly every 30 seconds. Also, the display is dead: the keyboard responds to NumLock and ScrollLock, but the last line on the bottom of the display consists of random data in bright. I can't enter ddb, or if I do, I can't tell that I've made it. I can rlogin with no problems. zaphod is an Abit BP6 with 2 Celerons. 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 Thu Apr 19 1:49:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B0F2137B422; Thu, 19 Apr 2001 01:49:17 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3J8mrT87624; Thu, 19 Apr 2001 11:48:53 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 11:48:53 +0300 From: Ruslan Ermilov To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG, Will Andrews Subject: make -jN bug (was: Re: groff breaks "make -j N buildworld") Message-ID: <20010419114853.B84456@sunbay.com> Mail-Followup-To: Makoto MATSUSHITA , current@FreeBSD.ORG, Will Andrews References: <200104190322.f3J3M8w56668@wint.itfs.nsk.su> <200104190322.f3J3M8w56668@wint.itfs.nsk.su> <20010419110405.B75677@sunbay.com> <20010419171841Z.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010419171841Z.matusita@jp.FreeBSD.org>; from matusita@jp.FreeBSD.org on Thu, Apr 19, 2001 at 05:18:41PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 19, 2001 at 05:18:41PM +0900, Makoto MATSUSHITA wrote: > > ru> I always thought that ``obj'', ``all'' and ``install'' should be > ru> executed in sequence, not together. Hey, this even does not work > ru> for bin/cat: > > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > I've heard why, but I've forgotten :-) > Attached is the Makefile that demonstrates the problem. Run it like this: make obj; make all Then try: make install And then try: make -j2 install Note the difference. This fixes the problem: --- Makefile Thu Apr 19 11:33:04 2001 +++ Makefile Thu Apr 19 11:36:20 2001 @@ -8,6 +8,7 @@ beforeinstall: .SILENT cd ${.CURDIR}; \ ${INSTALL} ${COPY} -m ${NOBINMODE} Makefile ${DESTDIR}/tmp + cd ${.OBJDIR} pwd ${INSTALL} ${COPY} -m ${NOBINMODE} foo ${DESTDIR}/tmp I'm not sure if this a make(1) bug or a feature, as both NetBSD and OpenBSD behave the same. But I'm pretty sure this is a bug. Will? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=Makefile NOMAN= YES all: foo foo: touch ${.TARGET} beforeinstall: .SILENT cd ${.CURDIR}; \ ${INSTALL} ${COPY} -m ${NOBINMODE} Makefile ${DESTDIR}/tmp pwd ${INSTALL} ${COPY} -m ${NOBINMODE} foo ${DESTDIR}/tmp .include --FL5UXtIhxfXey3p5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 4:48:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 4D03137B648 for ; Thu, 19 Apr 2001 04:48:33 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JBmVo52367 for current@freebsd.org; Thu, 19 Apr 2001 15:48:32 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 15:48:28 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Syscons mouse char range redefine proposal Message-ID: <20010419154827.A52282@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict with several languages code tables. I plan to redefine it by default to 0x03-0x07 leaving possibility to redefine it to any range as currently present. This way minimizes arcane information needed for user to setup its language correctly. Any objections? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 4:55:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 1C42B37B422 for ; Thu, 19 Apr 2001 04:55:09 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f3JBsqV10841; Thu, 19 Apr 2001 13:54:52 +0200 (CEST) (envelope-from sos) From: Sĝren Schmidt Message-Id: <200104191154.f3JBsqV10841@freebsd.dk> Subject: Re: Syscons mouse char range redefine proposal In-Reply-To: <20010419154827.A52282@nagual.pp.ru> "from Andrey A. Chernov at Apr 19, 2001 03:48:28 pm" To: "Andrey A. Chernov" Date: Thu, 19 Apr 2001 13:54:52 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Andrey A. Chernov wrote: > Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict > with several languages code tables. I plan to redefine it by default to > 0x03-0x07 leaving possibility to redefine it to any range as currently > present. This way minimizes arcane information needed for user to setup > its language correctly. > > Any objections? Wont work, it needs to be in the (IIRC) 0xd0 - 0xe0 range for the HW to DTRT with the ninth bit on VGA HW. The has been beaten to death several times before, check the archives... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5: 4:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 109EE37B422 for ; Thu, 19 Apr 2001 05:04:32 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JC34f52534; Thu, 19 Apr 2001 16:03:04 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 16:03:01 +0400 From: "Andrey A. Chernov" To: =?koi8-r?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010419160300.A52373@nagual.pp.ru> References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200104191154.f3JBsqV10841@freebsd.dk>; from sos@freebsd.dk on Thu, Apr 19, 2001 at 01:54:52PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 13:54:52 +0200, Sĝren Schmidt wrote: > It seems Andrey A. Chernov wrote: > > Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict > > with several languages code tables. I plan to redefine it by default to > > 0x03-0x07 leaving possibility to redefine it to any range as currently > > present. This way minimizes arcane information needed for user to setup > > its language correctly. > > > > Any objections? > > Wont work, it needs to be in the (IIRC) 0xd0 - 0xe0 range for the > HW to DTRT with the ninth bit on VGA HW. It works for years, just making small vertical black line sometimes appearse in the cursor. > The has been beaten to death several times before, check the archives... We just add yet one conflicting language - Ukrainian. How many you want to change this decision? Breaking letters is more important than black line in the cursor. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:16:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 4E74437B423 for ; Thu, 19 Apr 2001 05:16:50 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f3JCFIi209380; Thu, 19 Apr 2001 21:15:18 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f3JCFI755826; Thu, 19 Apr 2001 21:15:18 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:COINPy0xbcHnPN1NipiFQn0s81VwFRTN@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id VAA16007; Thu, 19 Apr 2001 21:23:58 +0900 (JST) Message-Id: <200104191223.VAA16007@zodiac.mech.utsunomiya-u.ac.jp> To: "Andrey A. Chernov" Cc: sos@freebsd.dk, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Syscons mouse char range redefine proposal In-reply-to: Your message of "Thu, 19 Apr 2001 16:03:01 +0400." <20010419160300.A52373@nagual.pp.ru> References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> <20010419160300.A52373@nagual.pp.ru> Date: Thu, 19 Apr 2001 21:23:57 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, Apr 19, 2001 at 13:54:52 +0200, S ren Schmidt wrote: >> It seems Andrey A. Chernov wrote: >> > Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict >> > with several languages code tables. I plan to redefine it by default to >> > 0x03-0x07 leaving possibility to redefine it to any range as currently >> > present. This way minimizes arcane information needed for user to setup >> > its language correctly. >> > >> > Any objections? >> >> Wont work, it needs to be in the (IIRC) 0xd0 - 0xe0 range for the >> HW to DTRT with the ninth bit on VGA HW. > >It works for years, just making small vertical black line sometimes >appearse in the cursor. > >> The has been beaten to death several times before, check the archives... > >We just add yet one conflicting language - Ukrainian. How many you want >to change this decision? Breaking letters is more important than black >line in the cursor. This has been discussed so many times in the past. We can configure the the base mouse char ether 1) by the kernel option SC_MOUSE_CHAR or 2) by `vidcontrol -M'. Maybe we should automatically add `-M 3' to flags for vidcontrol in rc.conf for those languages... Kazu > >-- >Andrey A. Chernov >http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:20:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6751437B423 for ; Thu, 19 Apr 2001 05:20:53 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JCKj752694; Thu, 19 Apr 2001 16:20:46 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 16:20:43 +0400 From: "Andrey A. Chernov" To: =?koi8-r?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010419162042.A52565@nagual.pp.ru> References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> <20010419160300.A52373@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010419160300.A52373@nagual.pp.ru>; from ache@nagual.pp.ru on Thu, Apr 19, 2001 at 04:03:01PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 16:03:01 +0400, Andrey A. Chernov wrote: > > > The has been beaten to death several times before, check the archives... > > We just add yet one conflicting language - Ukrainian. How many you want > to change this decision? Breaking letters is more important than black > line in the cursor. In any case it must be sysctl-controlled variable and not kernel option only. Rebuilding whole kernel to just change console language is superfluous! rc.syscon/rc.conf hooks must be added too. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:47:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id DDCBF37B43F for ; Thu, 19 Apr 2001 05:47:26 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup7-10.iptelecom.net.ua [212.9.227.138]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id PAA10517; Thu, 19 Apr 2001 15:47:18 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3JCkkT50488; Thu, 19 Apr 2001 15:46:46 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3ADEDE2F.573C20A1@FreeBSD.org> Date: Thu, 19 Apr 2001 15:46:39 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Doug Barton Cc: Alfred Perlstein , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> Content-Type: multipart/mixed; boundary="------------DC63A2FA63FD00D605314E3D" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------DC63A2FA63FD00D605314E3D Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Doug Barton wrote: > Alfred Perlstein wrote: > > > I'm figuring the only time when it may be a problem is on machines > > with a small amount of memory. Since memory is cheap, I plan on > > turning it on within the next couple of days unless a stability > > issue comes up. > > > > I'll leave it to those people with low memory to remember to turn > > it off. > > OK... this brings up the question of what other cool optimizations are > there that may have been disabled in the past for reasons that are no > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > with commented out examples of configurations for various systems. For > example, > > # For more modern systems that have a reasonable amount of RAM > #vfs.vmiodirenable=1 > > # Low memory systems > > # Systems that need lots of randomness > > # Low resource systems that need less randomness > > # Super high performance TCP options for various situations > > .... etc. I'm sure y'all can come up with more. > > It might also be desirable to put these in etc/defautls/rc.conf, but I > think something of this nature might be better suited in a freer format. What do you think about attached patch? -Maxim --------------DC63A2FA63FD00D605314E3D Content-Type: text/plain; charset=koi8-r; name="sysctl.conf.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sysctl.conf.diff" Index: Makefile =================================================================== RCS file: /home/ncvs/src/etc/Makefile,v retrieving revision 1.248 diff -d -u -r1.248 Makefile --- Makefile 2001/03/29 14:02:59 1.248 +++ Makefile 2001/04/19 12:44:09 @@ -15,8 +15,8 @@ printcap profile protocols \ rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.firewall6 \ rc.isdn rc.network rc.network6 rc.pccard rc.serial rc.shutdown \ - rc.syscons rc.sysctl remote rpc security services shells syslog.conf \ - usbd.conf \ + rc.syscons rc.sysctl remote rpc security services shells sysctl.conf \ + syslog.conf usbd.conf \ etc.${MACHINE_ARCH}/disktab \ etc.${MACHINE_ARCH}/rc.${MACHINE_ARCH} \ etc.${MACHINE_ARCH}/ttys \ Index: sysctl.conf =================================================================== RCS file: /home/ncvs/src/etc/sysctl.conf,v retrieving revision 1.1 diff -d -u -r1.1 sysctl.conf --- sysctl.conf 2000/07/27 22:53:42 1.1 +++ sysctl.conf 2001/04/19 12:44:09 @@ -3,3 +3,6 @@ # This file is read when going to multi-user and its contents piped thru # ``sysctl -w'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # + +vfs.vmiodirenable=0 # Set to 1 to enable a new directory allocation policy + # (codenamed "dirpref") --------------DC63A2FA63FD00D605314E3D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:51:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 864F237B424 for ; Thu, 19 Apr 2001 05:51:17 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JCp3x53199; Thu, 19 Apr 2001 16:51:04 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 16:51:00 +0400 From: "Andrey A. Chernov" To: Kazutaka YOKOTA Cc: sos@freebsd.dk, current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010419165059.A53153@nagual.pp.ru> References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> <20010419160300.A52373@nagual.pp.ru> <200104191223.VAA16007@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104191223.VAA16007@zodiac.mech.utsunomiya-u.ac.jp>; from yokota@zodiac.mech.utsunomiya-u.ac.jp on Thu, Apr 19, 2001 at 09:23:57PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 21:23:57 +0900, Kazutaka YOKOTA wrote: > > Maybe we should automatically add `-M 3' to flags for vidcontrol > in rc.conf for those languages... > Please review this patch: --- defaults/rc.conf.old Tue Apr 10 05:34:17 2001 +++ defaults/rc.conf Thu Apr 19 16:46:40 2001 @@ -292,6 +292,8 @@ moused_type="auto" # See man page for rc.conf(5) for available settings. moused_port="/dev/psm0" # Set to your mouse port. moused_flags="" # Any additional flags to moused. +mousechar_start="NO" # if 0xd0-0xd4 default range occuped in the font code + # table, specify alternative range start like 3 allscreens_flags="" # Set this vidcontrol mode for all virtual screens --- rc.syscons.old Mon Jan 22 09:04:56 2001 +++ rc.syscons Thu Apr 19 16:45:12 2001 @@ -160,6 +160,13 @@ [Yy][Ee][Ss]) echo -n ' moused' moused ${moused_flags} -p ${moused_port} -t ${moused_type} + case ${mousechar_start} in + [Nn][Oo] | '') + ;; + *) + echo -n ' mousechar_start'; vidcontrol < ${viddev} -M ${mousechar_start} + ;; + esac vidcontrol < ${viddev} -m on ;; esac -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:55: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id EFC8437B423 for ; Thu, 19 Apr 2001 05:54:55 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.11.3/8.11.3) with ESMTP id f3JCsTr03942; Thu, 19 Apr 2001 13:54:30 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Thu, 19 Apr 2001 13:54:29 +0100 (BST) From: Nick Hibma X-X-Sender: To: "Andrey A. Chernov" Cc: Kazutaka YOKOTA , , Subject: Re: Syscons mouse char range redefine proposal In-Reply-To: <20010419165059.A53153@nagual.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 You might want to specify in the comment what the arguments should look like, like an example. Nick On Thu, 19 Apr 2001, Andrey A. Chernov wrote: > On Thu, Apr 19, 2001 at 21:23:57 +0900, Kazutaka YOKOTA wrote: > > > > Maybe we should automatically add `-M 3' to flags for vidcontrol > > in rc.conf for those languages... > > > > Please review this patch: > > --- defaults/rc.conf.old Tue Apr 10 05:34:17 2001 > +++ defaults/rc.conf Thu Apr 19 16:46:40 2001 > @@ -292,6 +292,8 @@ > moused_type="auto" # See man page for rc.conf(5) for available settings. > moused_port="/dev/psm0" # Set to your mouse port. > moused_flags="" # Any additional flags to moused. > +mousechar_start="NO" # if 0xd0-0xd4 default range occuped in the font code > + # table, specify alternative range start like 3 > allscreens_flags="" # Set this vidcontrol mode for all virtual screens > > > --- rc.syscons.old Mon Jan 22 09:04:56 2001 > +++ rc.syscons Thu Apr 19 16:45:12 2001 > @@ -160,6 +160,13 @@ > [Yy][Ee][Ss]) > echo -n ' moused' > moused ${moused_flags} -p ${moused_port} -t ${moused_type} > + case ${mousechar_start} in > + [Nn][Oo] | '') > + ;; > + *) > + echo -n ' mousechar_start'; vidcontrol < ${viddev} -M ${mousechar_start} > + ;; > + esac > vidcontrol < ${viddev} -m on > ;; > esac > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@FreeBSD.ORG http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 5:55:29 2001 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 E970037B422; Thu, 19 Apr 2001 05:55:23 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3JCtNx02574; Thu, 19 Apr 2001 05:55:23 -0700 (PDT) Date: Thu, 19 Apr 2001 05:55:23 -0700 From: Alfred Perlstein To: Maxim Sobolev Cc: Doug Barton , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010419055523.G976@fw.wintelcom.net> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADEDE2F.573C20A1@FreeBSD.org>; from sobomax@FreeBSD.org on Thu, Apr 19, 2001 at 03:46:39PM +0300 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Maxim Sobolev [010419 05:48] wrote: > Doug Barton wrote: > > > Alfred Perlstein wrote: > > > > > I'm figuring the only time when it may be a problem is on machines > > > with a small amount of memory. Since memory is cheap, I plan on > > > turning it on within the next couple of days unless a stability > > > issue comes up. > > > > > > I'll leave it to those people with low memory to remember to turn > > > it off. > > > > OK... this brings up the question of what other cool optimizations are > > there that may have been disabled in the past for reasons that are no > > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > > with commented out examples of configurations for various systems. For > > example, > > > > # For more modern systems that have a reasonable amount of RAM > > #vfs.vmiodirenable=1 > > > > # Low memory systems > > > > # Systems that need lots of randomness > > > > # Low resource systems that need less randomness > > > > # Super high performance TCP options for various situations > > > > .... etc. I'm sure y'all can come up with more. > > > > It might also be desirable to put these in etc/defautls/rc.conf, but I > > think something of this nature might be better suited in a freer format. > > What do you think about attached patch? I think it's a step in the right direction, however vmiodirenable != dirpref vmiodirenable = Enable the use of the vm subsystem to back UFS directory memory requirements, because of the amount of wasted memory this causes it's not advised for machines with less than 64MB of ram, but on machines with more than 64MB it can provide a substantial benifit related to directory caching. dirpref = A new allocation policy that can substantially speed up metadata operations, it's enabled by default once the modifications are put into -stable, so there probably won't be a sysctl for it. :) The real fix would be to automagically enable it on machines with > 64megs of ram. > > -Maxim > > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/etc/Makefile,v > retrieving revision 1.248 > diff -d -u -r1.248 Makefile > --- Makefile 2001/03/29 14:02:59 1.248 > +++ Makefile 2001/04/19 12:44:09 > @@ -15,8 +15,8 @@ > printcap profile protocols \ > rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.firewall6 \ > rc.isdn rc.network rc.network6 rc.pccard rc.serial rc.shutdown \ > - rc.syscons rc.sysctl remote rpc security services shells syslog.conf \ > - usbd.conf \ > + rc.syscons rc.sysctl remote rpc security services shells sysctl.conf \ > + syslog.conf usbd.conf \ > etc.${MACHINE_ARCH}/disktab \ > etc.${MACHINE_ARCH}/rc.${MACHINE_ARCH} \ > etc.${MACHINE_ARCH}/ttys \ > Index: sysctl.conf > =================================================================== > RCS file: /home/ncvs/src/etc/sysctl.conf,v > retrieving revision 1.1 > diff -d -u -r1.1 sysctl.conf > --- sysctl.conf 2000/07/27 22:53:42 1.1 > +++ sysctl.conf 2001/04/19 12:44:09 > @@ -3,3 +3,6 @@ > # This file is read when going to multi-user and its contents piped thru > # ``sysctl -w'' to adjust kernel values. ``man 5 sysctl.conf'' for details. > # > + > +vfs.vmiodirenable=0 # Set to 1 to enable a new directory allocation policy > + # (codenamed "dirpref") -- -Alfred Perlstein - [alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6: 2:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 78AA637B423 for ; Thu, 19 Apr 2001 06:02:19 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JD20P53438; Thu, 19 Apr 2001 17:02:02 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 17:01:56 +0400 From: "Andrey A. Chernov" To: Nick Hibma Cc: Kazutaka YOKOTA , sos@freebsd.dk, current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010419170154.B53153@nagual.pp.ru> References: <20010419165059.A53153@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from n_hibma@qubesoft.com on Thu, Apr 19, 2001 at 01:54:29PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 13:54:29 +0100, Nick Hibma wrote: > > You might want to specify in the comment what the arguments should look > like, like an example. > > +mousechar_start="NO" # if 0xd0-0xd4 default range occuped in the font code > > + # table, specify alternative range start like 3 What about + # table, specify alternative range start like + # mousechar_start=3 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:13:44 2001 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 7F50C37B42C for ; Thu, 19 Apr 2001 06:13:40 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA03448; Thu, 19 Apr 2001 23:13:25 +1000 Date: Thu, 19 Apr 2001 23:12:24 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" In-Reply-To: <20010419171841Z.matusita@jp.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, 19 Apr 2001, Makoto MATSUSHITA wrote: > ru> I always thought that ``obj'', ``all'' and ``install'' should be > ru> executed in sequence, not together. Hey, this even does not work > ru> for bin/cat: `obj' must normally be built before everything else. Otherwise, make(1) will start by chdir'ing to the wrong object directory... Some cases work accidentally. E.g., `make obj all' works in directories with only subdirs, since all the object subdirectories will have been created by the time make(1) recurses into them for the `all' target. `make all install' might work. However ... > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > I've heard why, but I've forgotten :-) Right. One case where it doesn't work is installing /bin/sh with the default install flags. /bin/sh gets clobbered, so anything that attempts to use it concurrently doesn't work. In particular, a concurrent sub-make may fail. This problem is avoided for some very important install targets like ld.so by adding -C to INSTALLFLAGS to give an atomic installation. Atomic installation (but not -C) should be the default. Since make -jX install doesn't work, `make world' in /usr/src/Makefile uses `${MAKE} -B installworld' to turn off any previous setting of -j. If you make installworld directly, then then -B is not enforced, so you must use it in the command line if you have a setting of -j in the environment. ... back to `make all install'. If this works at all, then you can only use it without -j, since the `install' part of it doesn't work with -j. Separate steps are required to pass different flags to make(1). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:19:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 8B6DC37B440 for ; Thu, 19 Apr 2001 06:19:09 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup7-6.iptelecom.net.ua [212.9.227.134]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id QAA15204; Thu, 19 Apr 2001 16:18:52 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3JDILT50766; Thu, 19 Apr 2001 16:18:21 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3ADEE594.A49F8FD2@FreeBSD.org> Date: Thu, 19 Apr 2001 16:18:13 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alfred Perlstein Cc: Doug Barton , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <20010419055523.G976@fw.wintelcom.net> Content-Type: multipart/mixed; boundary="------------745D9EFD10E6355E398485E7" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------745D9EFD10E6355E398485E7 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Alfred Perlstein wrote: > * Maxim Sobolev [010419 05:48] wrote: > > Doug Barton wrote: > > > > > Alfred Perlstein wrote: > > > > > > > I'm figuring the only time when it may be a problem is on machines > > > > with a small amount of memory. Since memory is cheap, I plan on > > > > turning it on within the next couple of days unless a stability > > > > issue comes up. > > > > > > > > I'll leave it to those people with low memory to remember to turn > > > > it off. > > > > > > OK... this brings up the question of what other cool optimizations are > > > there that may have been disabled in the past for reasons that are no > > > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > > > with commented out examples of configurations for various systems. For > > > example, > > > > > > # For more modern systems that have a reasonable amount of RAM > > > #vfs.vmiodirenable=1 > > > > > > # Low memory systems > > > > > > # Systems that need lots of randomness > > > > > > # Low resource systems that need less randomness > > > > > > # Super high performance TCP options for various situations > > > > > > .... etc. I'm sure y'all can come up with more. > > > > > > It might also be desirable to put these in etc/defautls/rc.conf, but I > > > think something of this nature might be better suited in a freer format. > > > > What do you think about attached patch? > > I think it's a step in the right direction, however OOPS, I see. See updated patch. -Maxim --------------745D9EFD10E6355E398485E7 Content-Type: text/plain; charset=koi8-r; name="sysctl.conf.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sysctl.conf.diff" Index: Makefile =================================================================== RCS file: /home/ncvs/src/etc/Makefile,v retrieving revision 1.248 diff -d -u -r1.248 Makefile --- Makefile 2001/03/29 14:02:59 1.248 +++ Makefile 2001/04/19 13:18:01 @@ -15,8 +15,8 @@ printcap profile protocols \ rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.firewall6 \ rc.isdn rc.network rc.network6 rc.pccard rc.serial rc.shutdown \ - rc.syscons rc.sysctl remote rpc security services shells syslog.conf \ - usbd.conf \ + rc.syscons rc.sysctl remote rpc security services shells sysctl.conf \ + syslog.conf usbd.conf \ etc.${MACHINE_ARCH}/disktab \ etc.${MACHINE_ARCH}/rc.${MACHINE_ARCH} \ etc.${MACHINE_ARCH}/ttys \ Index: sysctl.conf =================================================================== RCS file: /home/ncvs/src/etc/sysctl.conf,v retrieving revision 1.1 diff -d -u -r1.1 sysctl.conf --- sysctl.conf 2000/07/27 22:53:42 1.1 +++ sysctl.conf 2001/04/19 13:18:01 @@ -3,3 +3,10 @@ # This file is read when going to multi-user and its contents piped thru # ``sysctl -w'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # + +vfs.vmiodirenable=0 # Set to 1 to enable the use of the VM subsystem to + # back UFS directory memory requirements. Because of + # the amount of wasted memory this causes it's not + # advised for machines with less than 64MB of RAM, but + # on machines with more than 64MB it can provide a + # substantial benefit related to directory caching --------------745D9EFD10E6355E398485E7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:26: 8 2001 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 09DC937B424; Thu, 19 Apr 2001 06:26:04 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3JDQ3m03376; Thu, 19 Apr 2001 06:26:03 -0700 (PDT) Date: Thu, 19 Apr 2001 06:26:03 -0700 From: Alfred Perlstein To: Maxim Sobolev Cc: Doug Barton , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010419062603.J976@fw.wintelcom.net> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <20010419055523.G976@fw.wintelcom.net> <3ADEE594.A49F8FD2@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADEE594.A49F8FD2@FreeBSD.org>; from sobomax@FreeBSD.org on Thu, Apr 19, 2001 at 04:18:13PM +0300 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Maxim Sobolev [010419 06:20] wrote: > > OOPS, I see. See updated patch. Looks ok. > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/etc/Makefile,v > retrieving revision 1.248 > diff -d -u -r1.248 Makefile > --- Makefile 2001/03/29 14:02:59 1.248 > +++ Makefile 2001/04/19 13:18:01 > @@ -15,8 +15,8 @@ > printcap profile protocols \ > rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.firewall6 \ > rc.isdn rc.network rc.network6 rc.pccard rc.serial rc.shutdown \ > - rc.syscons rc.sysctl remote rpc security services shells syslog.conf \ > - usbd.conf \ > + rc.syscons rc.sysctl remote rpc security services shells sysctl.conf \ > + syslog.conf usbd.conf \ > etc.${MACHINE_ARCH}/disktab \ > etc.${MACHINE_ARCH}/rc.${MACHINE_ARCH} \ > etc.${MACHINE_ARCH}/ttys \ > Index: sysctl.conf > =================================================================== > RCS file: /home/ncvs/src/etc/sysctl.conf,v > retrieving revision 1.1 > diff -d -u -r1.1 sysctl.conf > --- sysctl.conf 2000/07/27 22:53:42 1.1 > +++ sysctl.conf 2001/04/19 13:18:01 > @@ -3,3 +3,10 @@ > # This file is read when going to multi-user and its contents piped thru > # ``sysctl -w'' to adjust kernel values. ``man 5 sysctl.conf'' for details. > # > + > +vfs.vmiodirenable=0 # Set to 1 to enable the use of the VM subsystem to > + # back UFS directory memory requirements. Because of > + # the amount of wasted memory this causes it's not > + # advised for machines with less than 64MB of RAM, but > + # on machines with more than 64MB it can provide a > + # substantial benefit related to directory caching -- -Alfred Perlstein - [alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:29:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from filk.iinet.net.au (syncopation-dns.iinet.net.au [203.59.24.29]) by hub.freebsd.org (Postfix) with SMTP id D47CA37B424 for ; Thu, 19 Apr 2001 06:29:23 -0700 (PDT) (envelope-from julian@elischer.org) Received: (qmail 10229 invoked by uid 666); 19 Apr 2001 13:32:11 -0000 Received: from i181-078.nv.iinet.net.au (HELO elischer.org) (203.59.181.78) by mail.m.iinet.net.au with SMTP; 19 Apr 2001 13:32:11 -0000 Message-ID: <3ADEE806.43216916@elischer.org> Date: Thu, 19 Apr 2001 06:28:38 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: =?iso-8859-1?Q?S=F8ren?= Schmidt , current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> <20010419160300.A52373@nagual.pp.ru> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > On Thu, Apr 19, 2001 at 13:54:52 +0200, Sĝren Schmidt wrote: > > It seems Andrey A. Chernov wrote: > > > Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict > > > with several languages code tables. I plan to redefine it by default to > > > 0x03-0x07 leaving possibility to redefine it to any range as currently > > > present. This way minimizes arcane information needed for user to setup > > > its language correctly. > > > > > > Any objections? > > > > Wont work, it needs to be in the (IIRC) 0xd0 - 0xe0 range for the > > HW to DTRT with the ninth bit on VGA HW. > > It works for years, just making small vertical black line sometimes > appearse in the cursor. > > > The has been beaten to death several times before, check the archives... > > We just add yet one conflicting language - Ukrainian. How many you want > to change this decision? Breaking letters is more important than black > line in the cursor. also breaks Hungarian (for some capital letters) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:39:56 2001 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 0EFB537B424; Thu, 19 Apr 2001 06:39:53 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA05156; Thu, 19 Apr 2001 23:39:50 +1000 Date: Thu, 19 Apr 2001 23:38:49 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: Makoto MATSUSHITA , current@FreeBSD.ORG, Will Andrews Subject: Re: make -jN bug (was: Re: groff breaks "make -j N buildworld") In-Reply-To: <20010419114853.B84456@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Apr 2001, Ruslan Ermilov wrote: > Attached is the Makefile that demonstrates the problem. Run it like this: > > make obj; make all > > Then try: > > make install > > And then try: > > make -j2 install > > Note the difference. This fixes the problem: > > --- Makefile Thu Apr 19 11:33:04 2001 > +++ Makefile Thu Apr 19 11:36:20 2001 > @@ -8,6 +8,7 @@ > beforeinstall: .SILENT > cd ${.CURDIR}; \ > ${INSTALL} ${COPY} -m ${NOBINMODE} Makefile ${DESTDIR}/tmp > + cd ${.OBJDIR} > pwd > ${INSTALL} ${COPY} -m ${NOBINMODE} foo ${DESTDIR}/tmp > > I'm not sure if this a make(1) bug or a feature, as both NetBSD and > OpenBSD behave the same. But I'm pretty sure this is a bug. Will? This is a feature of parallel make. Parallel make combines all of the commands for each target into a single shell command (if possible?). Thus `cd's in one command affect subsequent commands. This feature can be controlled using the undocumented .SINGLESHELL directive. Unfortunately, the implementation of .SINGLESHELL is too primitive for .SINGELSHELL to be worth using. Using it is equivalent to using -B to turn off -j. This has caused problems before. See the log message for rev.1.177 of src/Makefile for a more complicated example. (The problem for `cd's is obvious compared with the one for `&&'s. In the example in log message, the point of the `cd's is to maximise the damage caused by combining non- -j-aware commands. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 6:48:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from rbn-gw.bgtu.debryansk.ru (rbn-gw.bgtu.debryansk.ru [62.76.89.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BE8C37B423; Thu, 19 Apr 2001 06:48:11 -0700 (PDT) (envelope-from kapr@acm.org) Received: from server.bitmcnit.bryansk.su (root@bitmcnit.bryansk.su [192.168.121.2]) by rbn-gw.bgtu.debryansk.ru (8.11.2/8.11.2) with ESMTP id f3JDkhC08043; Thu, 19 Apr 2001 17:46:43 +0400 Received: (from uucp@localhost) by server.bitmcnit.bryansk.su (8.9.3/8.9.3) with UUCP id RAA12184; Thu, 19 Apr 2001 17:41:20 +0400 Received: (from alex@localhost) by kapran.bitmcnit.bryansk.su (8.11.3/8.11.3) id f3JDSBA00841; Thu, 19 Apr 2001 17:28:11 +0400 (MSD) (envelope-from kapr@acm.org) X-Authentication-Warning: kapran.bitmcnit.bryansk.su: alex set sender to kapr@acm.org using -f Date: Thu, 19 Apr 2001 17:28:09 +0400 From: Alex Kapranoff To: Maxim Sobolev Cc: "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010419172808.A726@kapran.bitmcnit.bryansk.su> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADEDE2F.573C20A1@FreeBSD.org>; from sobomax@FreeBSD.ORG on Thu, Apr 19, 2001 at 03:46:39PM +0300 X-Operating-System: FreeBSD 5.0-CURRENT i386 Organization: Internal Mongolia Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 03:46:39PM +0300, Maxim Sobolev wrote: > > What do you think about attached patch? > > -Maxim > > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/etc/Makefile,v > retrieving revision 1.248 > diff -d -u -r1.248 Makefile > --- Makefile 2001/03/29 14:02:59 1.248 > +++ Makefile 2001/04/19 12:44:09 > @@ -15,8 +15,8 @@ > printcap profile protocols \ > rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.firewall6 \ > rc.isdn rc.network rc.network6 rc.pccard rc.serial rc.shutdown \ > - rc.syscons rc.sysctl remote rpc security services shells syslog.conf \ > - usbd.conf \ > + rc.syscons rc.sysctl remote rpc security services shells sysctl.conf \ > + syslog.conf usbd.conf \ > etc.${MACHINE_ARCH}/disktab \ > etc.${MACHINE_ARCH}/rc.${MACHINE_ARCH} \ > etc.${MACHINE_ARCH}/ttys \ > Index: sysctl.conf > =================================================================== > RCS file: /home/ncvs/src/etc/sysctl.conf,v > retrieving revision 1.1 > diff -d -u -r1.1 sysctl.conf > --- sysctl.conf 2000/07/27 22:53:42 1.1 > +++ sysctl.conf 2001/04/19 12:44:09 > @@ -3,3 +3,6 @@ > # This file is read when going to multi-user and its contents piped thru > # ``sysctl -w'' to adjust kernel values. ``man 5 sysctl.conf'' for details. > # > + > +vfs.vmiodirenable=0 # Set to 1 to enable a new directory allocation policy > + # (codenamed "dirpref") Oops, the comment is wrong. Dirpref is totally another thing which has nothing to do with that sysctl. -- Alex Kapranoff, Voice: +7(0832)791845 We've lived 2608 hours in the brand new millenium... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 7:55:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6FE1A37B422 for ; Thu, 19 Apr 2001 07:55:43 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3JErr921062; Thu, 19 Apr 2001 17:53:53 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 17:53:53 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: Makoto MATSUSHITA , current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" Message-ID: <20010419175353.A13567@sunbay.com> Mail-Followup-To: Bruce Evans , Makoto MATSUSHITA , current@FreeBSD.ORG References: <20010419171841Z.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Thu, Apr 19, 2001 at 11:12:24PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: [...] > > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > > I've heard why, but I've forgotten :-) > > Right. One case where it doesn't work is installing /bin/sh with the > default install flags. /bin/sh gets clobbered, so anything that attempts > to use it concurrently doesn't work. In particular, a concurrent > sub-make may fail. This problem is avoided for some very important > install targets like ld.so by adding -C to INSTALLFLAGS to give an > atomic installation. Atomic installation (but not -C) should be the > default. > This one seems like an easy task, and this is suspicious... How about the attached patch? I have tested it lightly, and haven't found any problems. Will the `make -j32 installworld' of -CURRENT be enough test to commit this and remove -B from Makefile.inc1? > Since make -jX install doesn't work, `make world' in /usr/src/Makefile > uses `${MAKE} -B installworld' to turn off any previous setting of -j. > If you make installworld directly, then then -B is not enforced, so > you must use it in the command line if you have a setting of -j in the > environment. > > ... back to `make all install'. If this works at all, then you can > only use it without -j, since the `install' part of it doesn't work > with -j. Separate steps are required to pass different flags to > make(1). > Is the atomic install the only known issue for not functional `make -jN install'? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 8: 1:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 7DD5237B42C; Thu, 19 Apr 2001 08:01:31 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3JF19s21802; Thu, 19 Apr 2001 18:01:09 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 18:01:09 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: Makoto MATSUSHITA , current@FreeBSD.ORG, Will Andrews Subject: Re: make -jN bug (was: Re: groff breaks "make -j N buildworld") Message-ID: <20010419180109.B13567@sunbay.com> Mail-Followup-To: Bruce Evans , Makoto MATSUSHITA , current@FreeBSD.ORG, Will Andrews References: <20010419114853.B84456@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Thu, Apr 19, 2001 at 11:38:49PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 11:38:49PM +1000, Bruce Evans wrote: > On Thu, 19 Apr 2001, Ruslan Ermilov wrote: > > > Attached is the Makefile that demonstrates the problem. Run it like this: > > > > make obj; make all > > > > Then try: > > > > make install > > > > And then try: > > > > make -j2 install > > > > Note the difference. This fixes the problem: > > > > --- Makefile Thu Apr 19 11:33:04 2001 > > +++ Makefile Thu Apr 19 11:36:20 2001 > > @@ -8,6 +8,7 @@ > > beforeinstall: .SILENT > > cd ${.CURDIR}; \ > > ${INSTALL} ${COPY} -m ${NOBINMODE} Makefile ${DESTDIR}/tmp > > + cd ${.OBJDIR} > > pwd > > ${INSTALL} ${COPY} -m ${NOBINMODE} foo ${DESTDIR}/tmp > > > > I'm not sure if this a make(1) bug or a feature, as both NetBSD and > > OpenBSD behave the same. But I'm pretty sure this is a bug. Will? > > This is a feature of parallel make. Parallel make combines all of > the commands for each target into a single shell command (if possible?). > Thus `cd's in one command affect subsequent commands. This feature > can be controlled using the undocumented .SINGLESHELL directive. > Unfortunately, the implementation of .SINGLESHELL is too primitive > for .SINGELSHELL to be worth using. Using it is equivalent to using > -B to turn off -j. > I stand corrected. The simple demo of this feature would be: foo: .SILENT VARIABLE=value echo $${VARIABLE} BTW, I have found the relevant info in the section 2.2 of the /usr/share/doc/psd/12.make/ paper: : Because all the commands are given to a single shell to execute, : such things as setting shell variables, changing directories, etc., ^^^^^^^^^^^^^^^^^^^^ : last beyond the command in which they are found. This also allows : shell compound commands (like ``for'' loops) to be entered in a : natural manner. Since this could cause problems for some makefiles : that depend on each command being executed by a single shell, PMake : has a -B flag (it stands for backwards-compatible) that forces each : command to be given to a separate shell. It also does several other : things, all of which I discourage since they are now old-fashioned. Thanks, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 8: 4:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 158CA37B505 for ; Thu, 19 Apr 2001 08:04:48 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3JF3qA22297; Thu, 19 Apr 2001 18:03:52 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 18:03:52 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Atomic install(1) by default (was: Re: groff breaks "make -j N buildworld") Message-ID: <20010419180352.C13567@sunbay.com> Mail-Followup-To: Bruce Evans , current@FreeBSD.ORG References: <20010419171841Z.matusita@jp.FreeBSD.org> <20010419175353.A13567@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010419175353.A13567@sunbay.com>; from ru@FreeBSD.org on Thu, Apr 19, 2001 at 05:53:53PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 19, 2001 at 05:53:53PM +0300, Ruslan Ermilov wrote: > On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: > [...] > > > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > > > I've heard why, but I've forgotten :-) > > > > Right. One case where it doesn't work is installing /bin/sh with the > > default install flags. /bin/sh gets clobbered, so anything that attempts > > to use it concurrently doesn't work. In particular, a concurrent > > sub-make may fail. This problem is avoided for some very important > > install targets like ld.so by adding -C to INSTALLFLAGS to give an > > atomic installation. Atomic installation (but not -C) should be the > > default. > > > This one seems like an easy task, and this is suspicious... How about > the attached patch? I have tested it lightly, and haven't found any > problems. Will the `make -j32 installworld' of -CURRENT be enough > test to commit this and remove -B from Makefile.inc1? > Damn, forgot to attach the patch. Here it goes... -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: xinstall.c =================================================================== RCS file: /home/ncvs/src/usr.bin/xinstall/xinstall.c,v retrieving revision 1.40 diff -u -p -r1.40 xinstall.c --- xinstall.c 2000/10/08 09:17:56 1.40 +++ xinstall.c 2001/04/19 14:38:41 @@ -53,11 +53,6 @@ static const char rcsid[] = * attribute changes and don't clear the dump flag. (I think inode * ctimes are not updated for null attribute changes, but this is a * bug.) - * o independent of -C, if a copy must be made, then copy to a tmpfile, - * set all attributes except the immutable flags, then rename, then - * set the immutable flags. It's annoying that the immutable flags - * defeat the atomicicity of rename - it seems that there must be - * a window where the target is not immutable. */ #include @@ -347,7 +342,7 @@ install(from_name, to_name, fset, flags) devnull = 1; } - if (docompare) { + if (docopy) { old_to_name = to_name; /* * Make a new temporary file in the same file system @@ -409,7 +404,7 @@ install(from_name, to_name, fset, flags) * It may be possible to better optimize the !dostrip case, however. * For further study. */ - if (docompare) { + if (docopy) { struct stat old_sb, new_sb, timestamp_sb; int old_fd; struct utimbuf utb; @@ -423,7 +418,7 @@ install(from_name, to_name, fset, flags) if (old_sb.st_flags & NOCHANGEBITS) (void)fchflags(old_fd, old_sb.st_flags & ~NOCHANGEBITS); fstat(to_fd, &new_sb); - if (compare(old_fd, old_to_name, to_fd, to_name, &old_sb, + if (!docompare || compare(old_fd, old_to_name, to_fd, to_name, &old_sb, &new_sb)) { different: if (debug != 0) --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 8:17:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 8851537B424; Thu, 19 Apr 2001 08:17:15 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id IAA30578; Thu, 19 Apr 2001 08:17:14 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3ADF0179.999BA451@DougBarton.net> Date: Thu, 19 Apr 2001 08:17:13 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Alfred Perlstein , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <20010419055523.G976@fw.wintelcom.net> <3ADEE594.A49F8FD2@FreeBSD.org> 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: > > > What do you think about attached patch? Definitely the right idea, however I'm waiting on input from a couple people on some additional suggestions, so if you'd hold off I'd appreciate it. -- "One thing they don't tell you about doing experimental physics is that sometimes you must work under adverse conditions ... like a state of sheer terror." -- W. K. Hartmann Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 9: 1:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 3C8B437B423; Thu, 19 Apr 2001 09:01:08 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup7-1.iptelecom.net.ua [212.9.227.129]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id TAA37532; Thu, 19 Apr 2001 19:01:02 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3JG0UT51887; Thu, 19 Apr 2001 19:00:30 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3ADF0B95.42E19625@FreeBSD.org> Date: Thu, 19 Apr 2001 19:00:21 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: markm@FreeBSD.org Cc: current@FreeBSD.org Subject: core(5) implementation using perl(1) Content-Type: multipart/mixed; boundary="------------0C1B441EC7CD1958B55D2237" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------0C1B441EC7CD1958B55D2237 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hi, Attached script forces perl(1) to dump core, which isn't a good behaviour IMO (tested on 5-CURRENT and 4.3-RC). -Maxim --------------0C1B441EC7CD1958B55D2237 Content-Type: text/plain; charset=koi8-r; name="killperl" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="killperl" #!/bin/sh perl -pi -e "s|make|\$\{MAKE\}|g ; s|^INCPATH=.*|INCPATH=-I/usr/local/include -I/usr/local/include/SDL11 -D_REENTRANT| ; s|^LIBS=.*|LIBS=-L/usr/local/lib -Wl,-rpath,/usr/local/lib -lSDL-1.1 -lc_r -lm -L/usr/local/lib -lesd -laudiofile -lm -L/usr/X11R6/lib -lX11 -lXext -lXxf86vm -lXxf86dga -lXv -lvga -lvgl -laa|" foobar --------------0C1B441EC7CD1958B55D2237-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 9: 6:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 24FA937B422 for ; Thu, 19 Apr 2001 09:06:42 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup7-33.iptelecom.net.ua [212.9.227.161]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id TAA38194; Thu, 19 Apr 2001 19:06:37 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3JG5QT51902; Thu, 19 Apr 2001 19:05:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3ADF0CBC.A38606EA@FreeBSD.org> Date: Thu, 19 Apr 2001 19:05:17 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Doug Barton Cc: Alfred Perlstein , Matt Dillon , "'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <20010419055523.G976@fw.wintelcom.net> <3ADEE594.A49F8FD2@FreeBSD.org> <3ADF0179.999BA451@DougBarton.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > Maxim Sobolev wrote: > > > > > What do you think about attached patch? > > Definitely the right idea, however I'm waiting on input from a couple > people on some additional suggestions, so if you'd hold off I'd appreciate > it. Unfortunately I've already cvs ci it. :( Hovewer, it is a cvs, so it should not be big deal, really. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 9:32:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id C6AB937B422; Thu, 19 Apr 2001 09:32:36 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3JGWVG54689; Thu, 19 Apr 2001 09:32:31 -0700 (PDT) (envelope-from dillon) Date: Thu, 19 Apr 2001 09:32:31 -0700 (PDT) From: Matt Dillon Message-Id: <200104191632.f3JGWVG54689@earth.backplane.com> To: Maxim Sobolev Cc: Doug Barton , "Alfred Perlstein \"'current@freebsd.org'\"" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :What do you think about attached patch? : :-Maxim mmm.. I think it would just confuse the issue and prevent us from being able to change the kernel default trivially. 99.5% of the FreeBSD boxes out there are just going to want it to be on by default. We could provide a commented-out rc.conf variable and support in rc to allow the sysadmin to set it, but we should not provide a default in the rc system or try to create yet another configuration file. The issue doesn't require that level of sophistication. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:25: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 0EB0637B423 for ; Thu, 19 Apr 2001 10:25:04 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup15-34.iptelecom.net.ua [212.9.229.162]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id UAA47685; Thu, 19 Apr 2001 20:24:57 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3JHOQT52196; Thu, 19 Apr 2001 20:24:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3ADF1F36.44A3AA54@FreeBSD.org> Date: Thu, 19 Apr 2001 20:24:06 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Matt Dillon Cc: Doug Barton , "Alfred Perlstein \"'current@freebsd.org'\"" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > : > :What do you think about attached patch? > : > :-Maxim > > mmm.. I think it would just confuse the issue and prevent us from > being able to change the kernel default trivially. 99.5% of the > FreeBSD boxes out there are just going to want it to be on by default. Point taken and issues fixed, thank you! > We could provide a commented-out rc.conf variable and support in rc > to allow the sysadmin to set it, but we should not provide a default > in the rc system or try to create yet another configuration file. The > issue doesn't require that level of sophistication. But we already have sysctl.conf and appropriate rc.sysctl, haven't we? What's wrong with putting some useful payload into it? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:26:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id 04DE037B42C; Thu, 19 Apr 2001 10:26:23 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id D74AA1BD72; Thu, 19 Apr 2001 12:23:54 -0500 (EST) Date: Thu, 19 Apr 2001 12:23:54 -0500 From: Will Andrews To: Jens Schweikhardt Cc: FreeBSD Current Subject: Re: LINT and NOTES Message-ID: <20010419122354.Z5017@casimir.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Jens Schweikhardt , FreeBSD Current References: <20010419102302.A70870@schweikhardt.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="htVlOAOs/VIaEhiC" Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010419102302.A70870@schweikhardt.net>; from schweikh@schweikhardt.net on Thu, Apr 19, 2001 at 10:23:02AM -0700 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --htVlOAOs/VIaEhiC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 19, 2001 at 10:23:02AM -0700, Jens Schweikhardt wrote: > I just wanted to close http://www.freebsd.org/cgi/query-pr.cgi?pr=3D25030 > by frobbing NOTES. While 4.2-R LINT has option USER_LDT, NOTES doesn't > have it anymore. Can anybody clue me in why it disappeared? Can I simply > resurrect it? Because peter eliminated it by making the relevant code mandatory about 2 months ago. Check out the cvs logs for NOTES. > BTW, is this the right list to ask such a question? Nope. current@ would be. --=20 wca --htVlOAOs/VIaEhiC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE63x8qF47idPgWcsURAqn5AJ4/6v6PVFlFQVKhhKlzupFTBxaOYwCeORFW OcGQdrDQ85H7Tdog1zPYgbI= =eXI1 -----END PGP SIGNATURE----- --htVlOAOs/VIaEhiC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:31: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id D802737B42C for ; Thu, 19 Apr 2001 10:31:00 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JHUtQ69117; Thu, 19 Apr 2001 21:30:56 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 21:30:55 +0400 From: "Andrey A. Chernov" To: =?koi8-r?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010419213055.A69048@nagual.pp.ru> References: <20010419154827.A52282@nagual.pp.ru> <200104191154.f3JBsqV10841@freebsd.dk> <20010419160300.A52373@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010419160300.A52373@nagual.pp.ru>; from ache@nagual.pp.ru on Thu, Apr 19, 2001 at 04:03:01PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 16:03:01 +0400, Andrey A. Chernov wrote: > > Wont work, it needs to be in the (IIRC) 0xd0 - 0xe0 range for the > > HW to DTRT with the ninth bit on VGA HW. > > It works for years, just making small vertical black line sometimes > appearse in the cursor. BTW, default variant cause 9th pixel appearse in the characters near the cursor, so it is not obvious what is worse, black line in the cursor or extra pixels in the nearby chars. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:33:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 63BF437B423 for ; Thu, 19 Apr 2001 10:33:09 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 5352 invoked by uid 1000); 19 Apr 2001 17:31:33 -0000 Date: Thu, 19 Apr 2001 20:31:33 +0300 From: Peter Pentchev To: Will Andrews , Jens Schweikhardt , FreeBSD Current Subject: Re: LINT and NOTES Message-ID: <20010419203133.F1527@ringworld.oblivion.bg> Mail-Followup-To: Peter Pentchev , Will Andrews , Jens Schweikhardt , FreeBSD Current References: <20010419102302.A70870@schweikhardt.net> <20010419122354.Z5017@casimir.physics.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010419122354.Z5017@casimir.physics.purdue.edu>; from will@physics.purdue.edu on Thu, Apr 19, 2001 at 12:23:54PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 12:23:54PM -0500, Will Andrews wrote: > On Thu, Apr 19, 2001 at 10:23:02AM -0700, Jens Schweikhardt wrote: > > I just wanted to close http://www.freebsd.org/cgi/query-pr.cgi?pr=25030 > > by frobbing NOTES. While 4.2-R LINT has option USER_LDT, NOTES doesn't > > have it anymore. Can anybody clue me in why it disappeared? Can I simply > > resurrect it? > > Because peter eliminated it by making the relevant code mandatory about > 2 months ago. Check out the cvs logs for NOTES. > > > BTW, is this the right list to ask such a question? > > Nope. current@ would be. Here's Peter Wemm's commit, for reference purposes. G'luck, Peter -- When you are not looking at it, this sentence is in Spanish. Message-Id: <200102230125.f1N1P2g47761@freefall.freebsd.org> From: Peter Wemm Date: Thu, 22 Feb 2001 17:25:02 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/conf options.i386 options.pc98 src/sys/i386/conf NOTES src/sys/i386/i386 genassym.c machdep.c mp_machdep.c pmap.c swtch.s sys_machdep.c vm_machdep.c src/sys/i386/include globaldata.h pcb.h pcb_ext.h ... X-FreeBSD-CVS-Branch: HEAD Precedence: bulk peter 2001/02/22 17:25:02 PST Modified files: sys/conf options.i386 options.pc98 sys/i386/conf NOTES sys/i386/i386 genassym.c machdep.c mp_machdep.c pmap.c swtch.s sys_machdep.c vm_machdep.c sys/i386/include globaldata.h pcb.h pcb_ext.h sys/i386/svr4 svr4_machdep.c sys/pc98/i386 machdep.c Log: Activate USER_LDT by default. The new thread libraries are going to depend on this. The linux ABI emulator tries to use it for some linux binaries too. VM86 had a bigger cost than this and it was made default a while ago. Reviewed by: jhb, imp Revision Changes Path 1.146 +1 -2 src/sys/conf/options.i386 1.117 +1 -2 src/sys/conf/options.pc98 1.891 +1 -8 src/sys/i386/conf/NOTES 1.107 +1 -9 src/sys/i386/i386/genassym.c 1.442 +3 -8 src/sys/i386/i386/machdep.c 1.147 +1 -4 src/sys/i386/i386/mp_machdep.c 1.273 +1 -2 src/sys/i386/i386/pmap.c 1.111 +1 -4 src/sys/i386/i386/swtch.s 1.53 +2 -10 src/sys/i386/i386/sys_machdep.c 1.153 +3 -9 src/sys/i386/i386/vm_machdep.c 1.24 +2 -2 src/sys/i386/include/globaldata.h 1.36 +1 -5 src/sys/i386/include/pcb.h 1.5 +1 -3 src/sys/i386/include/pcb_ext.h 1.17 +4 -3 src/sys/i386/svr4/svr4_machdep.c 1.207 +3 -8 src/sys/pc98/i386/machdep.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:38:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 33C3D37B424; Thu, 19 Apr 2001 10:38:13 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3JHcCa55868; Thu, 19 Apr 2001 10:38:12 -0700 (PDT) (envelope-from dillon) Date: Thu, 19 Apr 2001 10:38:12 -0700 (PDT) From: Matt Dillon Message-Id: <200104191738.f3JHcCa55868@earth.backplane.com> To: Maxim Sobolev Cc: Doug Barton , "Alfred Perlstein \"'current@freebsd.org'\"" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> <3ADF1F36.44A3AA54@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :But we already have sysctl.conf and appropriate rc.sysctl, haven't we? What's :wrong with putting some useful payload into it? : :-Maxim If it's commented out, it's fine. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:40: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 5DAB937B423; Thu, 19 Apr 2001 10:39:58 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3JHdw255890; Thu, 19 Apr 2001 10:39:58 -0700 (PDT) (envelope-from dillon) Date: Thu, 19 Apr 2001 10:39:58 -0700 (PDT) From: Matt Dillon Message-Id: <200104191739.f3JHdw255890@earth.backplane.com> To: Maxim Sobolev Cc: Doug Barton , "Alfred Perlstein \"'current@freebsd.org'\"" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> <3ADF1F36.44A3AA54@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :But we already have sysctl.conf and appropriate rc.sysctl, haven't we? What's :wrong with putting some useful payload into it? : :-Maxim Let me explain a little more. If it's commented out, it's fine. But if you are actually setting a value in there you will override whatever is set in the kernel. When people install new systems they do not usually override their /etc/ files, so an uncommented value will set that default in stone and prevent us from being able to change it with a new kernel rev. This being a *kernel* specific feature, we need to have control over the default in the kernel itself. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:42:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id D6D6D37B42C; Thu, 19 Apr 2001 10:42:38 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JHgVi69277; Thu, 19 Apr 2001 21:42:31 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 21:42:30 +0400 From: "Andrey A. Chernov" To: Matt Dillon Cc: Maxim Sobolev , Doug Barton , "Alfred Perlstein 'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010419214230.A69239@nagual.pp.ru> References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> <3ADF1F36.44A3AA54@FreeBSD.org> <200104191739.f3JHdw255890@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104191739.f3JHdw255890@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Apr 19, 2001 at 10:39:58AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 10:39:58 -0700, Matt Dillon wrote: > :But we already have sysctl.conf and appropriate rc.sysctl, haven't we? What's > :wrong with putting some useful payload into it? > : > :-Maxim > > Let me explain a little more. If it's commented out, it's fine. But > if you are actually setting a value in there you will override whatever > is set in the kernel. When people install new systems they do not > usually override their /etc/ files, so an uncommented value will > set that default in stone and prevent us from being able to change > it with a new kernel rev. This being a *kernel* specific feature, > we need to have control over the default in the kernel itself. What about simple check in the kernel: if total memory is above 64Mb, then enable this mode by default, else disable it. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:47:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B3BDF37B424; Thu, 19 Apr 2001 10:47:25 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3JHlK156009; Thu, 19 Apr 2001 10:47:20 -0700 (PDT) (envelope-from dillon) Date: Thu, 19 Apr 2001 10:47:20 -0700 (PDT) From: Matt Dillon Message-Id: <200104191747.f3JHlK156009@earth.backplane.com> To: "Andrey A. Chernov" Cc: Maxim Sobolev , Doug Barton , "Alfred Perlstein 'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost References: <200104161634.f3GGYZs11356@aslan.scsiguy.com> <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> <3ADF1F36.44A3AA54@FreeBSD.org> <200104191739.f3JHdw255890@earth.backplane.com> <20010419214230.A69239@nagual.pp.ru> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> set that default in stone and prevent us from being able to change :> it with a new kernel rev. This being a *kernel* specific feature, :> we need to have control over the default in the kernel itself. : :What about simple check in the kernel: if total memory is above 64Mb, then :enable this mode by default, else disable it. : :-- :Andrey A. Chernov You are assuming that turning on vmiodirenable is detrimental on a low-memory machine. I don't think it is, because on a low memory machine you aren't going to be able to cache very much anyway. But if anyone thinks it is please be my guest and test it on a low-memory machine on verses off. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 10:50:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id F243837B42C; Thu, 19 Apr 2001 10:50:25 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f3JHoLC69424; Thu, 19 Apr 2001 21:50:21 +0400 (MSD) (envelope-from ache) Date: Thu, 19 Apr 2001 21:50:20 +0400 From: "Andrey A. Chernov" To: Matt Dillon Cc: Maxim Sobolev , Doug Barton , "Alfred Perlstein 'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost Message-ID: <20010419215020.A69376@nagual.pp.ru> References: <200104162146.f3GLkGT82369@earth.backplane.com> <3ADBF9FA.9D1C4DB4@DougBarton.net> <20010417011335.V976@fw.wintelcom.net> <3ADC0221.32127C39@DougBarton.net> <3ADEDE2F.573C20A1@FreeBSD.org> <200104191632.f3JGWVG54689@earth.backplane.com> <3ADF1F36.44A3AA54@FreeBSD.org> <200104191739.f3JHdw255890@earth.backplane.com> <20010419214230.A69239@nagual.pp.ru> <200104191747.f3JHlK156009@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104191747.f3JHlK156009@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Apr 19, 2001 at 10:47:20AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 10:47:20 -0700, Matt Dillon wrote: > :> set that default in stone and prevent us from being able to change > :> it with a new kernel rev. This being a *kernel* specific feature, > :> we need to have control over the default in the kernel itself. > : > :What about simple check in the kernel: if total memory is above 64Mb, then > :enable this mode by default, else disable it. > : > :-- > :Andrey A. Chernov > > You are assuming that turning on vmiodirenable is detrimental on a > low-memory machine. I don't think it is, because on a low memory > machine you aren't going to be able to cache very much anyway. But if > anyone thinks it is please be my guest and test it on a low-memory > machine on verses off. Personally I not test this thing, just assume that current etc/sysctl.conf comment about 64Mb limit is correct, i.e. assume that sysctl.conf commiter already test it. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 11: 0:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C044337B43E for ; Thu, 19 Apr 2001 11:00:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3JHxvG91279; Thu, 19 Apr 2001 10:59:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010419181419.G72816@wantadilla.lemis.com> Date: Thu, 19 Apr 2001 10:59:18 -0700 (PDT) From: John Baldwin To: Greg Lehey Subject: RE: Breakage in today's -CURRENT Cc: FreeBSD current users Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Apr-01 Greg Lehey wrote: > I've just built a couple of worlds from -CURRENT cvsupped at 2030 UTC > on the 18th, and at 0600 UTC on the 19th. In each case, I have > massive problems, apparently with the synchronization. Here's some > log file output: > > Apr 19 18:11:34 zaphod /boot/kernel/kernel: > fforrwwarardd__hsatradtcclloocckk:: ch ecchkesctkasttea te 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: ffrwaordr_whaarrdd_cstocakt:c > lock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwoarrwd_rds_hatacrldckckl:o > cckheckstate : c0h > Apr 19 18:11:34 zaphod /boot/kernel/kernel: eckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwarodr_whaarrdd_cstoactk:lo > ccheckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: k: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forfwarod_rhaarrdcd_sltoactkc:l > occk: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > > These blocks repeat exactly every 30 seconds. Also, the display is > dead: the keyboard responds to NumLock and ScrollLock, but the last > line on the bottom of the display consists of random data in bright. > I can't enter ddb, or if I do, I can't tell that I've made it. I can > rlogin with no problems. zaphod is an Abit BP6 with 2 Celerons. > > Greg Try bumping the timeouts in forward_hardclock() and forward_statclock() in mp_machdep.c. I'm currently overhauling the clock stuff so that we don't need these timeouts. The problem is that these timeouts are CPU speed sensitive, so while they might be fine for a PPro 200, they are far too short for a P3 600. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 12:39:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 0DF3B37B424 for ; Thu, 19 Apr 2001 12:39:15 -0700 (PDT) (envelope-from jwd@bsdwins.com) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.1/8.11.0) id f3JJdEm75017 for freebsd-current@freebsd.org; Thu, 19 Apr 2001 15:39:14 -0400 (EDT) (envelope-from jwd) Date: Thu, 19 Apr 2001 15:39:14 -0400 From: "John W. De Boskey" To: Current List Subject: cp -d dir patch for review Message-ID: <20010419153913.A74863@bsdwins.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have added a -d dir option to cp. This allows the target directory to be specified at the head of the command line instead of the tail. This makes cp work much more nicely with tools like xargs... (allowing for major performance improvements over inline shell loops). The patch is at: http://www.freebsd.org/~jwd/cp-d.patch which allows: cp -d target_directory source1 source2 ... sourceN and/or cat big_file_list | xargs cp -d target_directory The changes required to do this turned out to be simple. Please let me know if you have any comments. Note: I do not have a man page update yet. Working with man pages on current appears to be broken. nroff/groff are also producing bad output on freefall.. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 12:42:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdhome.dyndns.org (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 1850937B423 for ; Thu, 19 Apr 2001 12:42:53 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by bsdhome.dyndns.org (8.11.3/8.11.3) with ESMTP id f3JJgpJ36498; Thu, 19 Apr 2001 15:42:51 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: (from bsd@localhost) by vger.bsdhome.com (8.11.3/8.11.1) id f3JJgoB28058; Thu, 19 Apr 2001 15:42:50 -0400 (EDT) (envelope-from bsd) Date: Thu, 19 Apr 2001 15:42:49 -0400 From: Brian Dean To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: Failed using CD-ROM as root filesystem Message-ID: <20010419154249.A26622@vger.bsdhome.com> References: <20010416132724H.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010416132724H.matusita@jp.FreeBSD.org>; from matusita@jp.FreeBSD.org on Mon, Apr 16, 2001 at 01:27:24PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 01:27:24PM +0900, Makoto MATSUSHITA wrote: > I've tried to use (bootable) CD-ROM as root filesystem (I want have > this because it's good alternative of fixit.flp), but it seems that > GENERIC kernel doesn't understand where is root filesystem. > > What I did are: > [ procedure deleted ] > > It seems that something goes wrong in setrootbyname(). Any clues? > > P.S.: I've also tried with 4-stable kernel, and it goes pretty well. I've been doing something similar with the latest code in -stable and have got it working very well. My purposes are varied, but I'm mainly experimenting with setting up a cd-rom based firewall device using a more traditional layout as opposed to the picobsd methods. -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 13:40:42 2001 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 1A79237B424; Thu, 19 Apr 2001 13:40:35 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA27546; Fri, 20 Apr 2001 06:40:32 +1000 Date: Fri, 20 Apr 2001 06:39:30 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: Atomic install(1) by default (was: Re: groff breaks "make -j N buildworld") In-Reply-To: <20010419180352.C13567@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Apr 2001, Ruslan Ermilov wrote: > On Thu, Apr 19, 2001 at 05:53:53PM +0300, Ruslan Ermilov wrote: > > On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: > > > atomic installation. Atomic installation (but not -C) should be the > > > default. > > > > > This one seems like an easy task, and this is suspicious... How about > > the attached patch? I have tested it lightly, and haven't found any > > problems. Will the `make -j32 installworld' of -CURRENT be enough > > test to commit this and remove -B from Makefile.inc1? > > > Damn, forgot to attach the patch. Here it goes... This seems to be simple enough. A bit too simple :-). The old behaviour of deleting the target first is still needed at least optionally to handle cases where there is no space for a copy. Cleaning up the temporary files after a signal is more necessary if -C is the default. Index: xinstall.c =================================================================== RCS file: /home/ncvs/src/usr.bin/xinstall/xinstall.c,v retrieving revision 1.40 diff -u -p -r1.40 xinstall.c --- xinstall.c 2000/10/08 09:17:56 1.40 +++ xinstall.c 2001/04/19 14:38:41 @@ -53,11 +53,6 @@ static const char rcsid[] = * attribute changes and don't clear the dump flag. (I think inode * ctimes are not updated for null attribute changes, but this is a * bug.) - * o independent of -C, if a copy must be made, then copy to a tmpfile, - * set all attributes except the immutable flags, then rename, then - * set the immutable flags. It's annoying that the immutable flags - * defeat the atomicicity of rename - it seems that there must be - * a window where the target is not immutable. */ The comment still applies to the -C case. We now always make a copy, but for -C this is just a waste of time if the comparison succeeds. ... @@ -409,7 +404,7 @@ install(from_name, to_name, fset, flags) * It may be possible to better optimize the !dostrip case, however. * For further study. */ - if (docompare) { + if (docopy) { struct stat old_sb, new_sb, timestamp_sb; int old_fd; struct utimbuf utb; @@ -423,7 +418,7 @@ install(from_name, to_name, fset, flags) if (old_sb.st_flags & NOCHANGEBITS) (void)fchflags(old_fd, old_sb.st_flags & ~NOCHANGEBITS); fstat(to_fd, &new_sb); - if (compare(old_fd, old_to_name, to_fd, to_name, &old_sb, + if (!docompare || compare(old_fd, old_to_name, to_fd, to_name, &old_sb, &new_sb)) { Line too long. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 13:45:52 2001 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 470B537B43E; Thu, 19 Apr 2001 13:45:47 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA27843; Fri, 20 Apr 2001 06:45:43 +1000 Date: Fri, 20 Apr 2001 06:44:42 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: Makoto MATSUSHITA , current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" In-Reply-To: <20010419175353.A13567@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Apr 2001, Ruslan Ermilov wrote: > On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: > [...] > > > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > > > I've heard why, but I've forgotten :-) > > > > Right. One case where it doesn't work is installing /bin/sh with the > > default install flags. /bin/sh gets clobbered, so anything that attempts > > to use it concurrently doesn't work. In particular, a concurrent > > sub-make may fail. This problem is avoided for some very important > > install targets like ld.so by adding -C to INSTALLFLAGS to give an > > atomic installation. Atomic installation (but not -C) should be the > > default. > > > This one seems like an easy task, and this is suspicious... How about > the attached patch? I have tested it lightly, and haven't found any > problems. Will the `make -j32 installworld' of -CURRENT be enough > test to commit this and remove -B from Makefile.inc1? Testing several times with different -j values is a good idea, since the order of commands can vary with the -j value and the timing. > Is the atomic install the only known issue for not functional > `make -jN install'? It's the only one that I can think of now. There are probably more in the perl install :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 15:26:24 2001 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 2F7F337B43E; Thu, 19 Apr 2001 15:26:21 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA02608; Fri, 20 Apr 2001 08:26:01 +1000 Date: Fri, 20 Apr 2001 08:23:20 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: Matt Dillon , Maxim Sobolev , Doug Barton , "Alfred Perlstein 'current@freebsd.org'" Subject: Re: FW: Filesystem gets a huge performance boost In-Reply-To: <20010419214230.A69239@nagual.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 Thu, 19 Apr 2001, Andrey A. Chernov wrote: > On Thu, Apr 19, 2001 at 10:39:58 -0700, Matt Dillon wrote: > > Let me explain a little more. If it's commented out, it's fine. But > > if you are actually setting a value in there you will override whatever > > is set in the kernel. When people install new systems they do not > > usually override their /etc/ files, so an uncommented value will > > set that default in stone and prevent us from being able to change > > it with a new kernel rev. This being a *kernel* specific feature, > > we need to have control over the default in the kernel itself. > > What about simple check in the kernel: if total memory is above 64Mb, then > enable this mode by default, else disable it. I believe it should be enabled at more like 640MB than 64MB. It slows down makeworld (immediately after rebooting to get a consistent enviroment) a little here with 256MB. Whether it is good depends more on the application mix than the memory size. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 16: 4:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from zorch.sf-bay.org (zorch.dial.idiom.com [216.240.37.73]) by hub.freebsd.org (Postfix) with ESMTP id 52D6237B423 for ; Thu, 19 Apr 2001 16:04:08 -0700 (PDT) (envelope-from scott@zorch.sf-bay.org) Received: (from uucp@localhost) by zorch.sf-bay.org (8.11.1/8.8.2) with UUCP id f3JN45q93085 for freebsd-current@freebsd.org; Thu, 19 Apr 2001 16:04:05 -0700 (PDT) Received: (from scott@localhost) by zorba.sf-bay.org (8.11.3/8.8.8) id f3JN2Ik56603 for freebsd-current@freebsd.org; Thu, 19 Apr 2001 16:02:18 -0700 (PDT) (envelope-from scott) Date: Thu, 19 Apr 2001 16:02:18 -0700 (PDT) From: Scott Hazen Mueller Message-Id: <200104192302.f3JN2Ik56603@zorba.sf-bay.org> To: freebsd-current@freebsd.org Subject: sound driver breakage/megapatch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like the recent sound driver megapatch broke (at least) the Neomagic 256AV driver. With a cvsup from yesterday, trying to do play mp3 files got trash that was vaguely recognizable as a seriously distorted version of the original piece. I did some trolling of the cvsweb and decided to roll back to a fixed date (2001.03.24.00.00.00) before the megapatch. I've rebuilt the .ko files and unloaded/reloaded them; I now have working sound. The failing sound also generated this error Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead The probe message "before" (removing megapatch) - Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 The probe message "after" (removing megapatch) - Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 And, somewhere in here, "hwintr went backwards" went away. Hope this helps. \scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 18:26:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from enia.bastun.net (enia.bastun.net [212.95.178.212]) by hub.freebsd.org (Postfix) with ESMTP id 77FC337B424 for ; Thu, 19 Apr 2001 18:26:03 -0700 (PDT) (envelope-from maav@enia.bastun.net) Received: (from maav@localhost) by enia.bastun.net (8.11.3/8.11.3) id f3K1P6791066; Fri, 20 Apr 2001 04:25:06 +0300 (EEST) (envelope-from maav) Date: Fri, 20 Apr 2001 04:25:06 +0300 From: User & To: Scott Hazen Mueller Cc: freebsd-current@freebsd.org Subject: Re: sound driver breakage/megapatch Message-ID: <20010420042505.A90945@enia.bastun.net> References: <200104192302.f3JN2Ik56603@zorba.sf-bay.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104192302.f3JN2Ik56603@zorba.sf-bay.org>; from scott@zorch.sf-bay.org on Thu, Apr 19, 2001 at 04:02:18PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 04:02:18PM -0700, Scott Hazen Mueller wrote: > It looks like the recent sound driver megapatch broke (at least) the Neomagic > 256AV driver. With a cvsup from yesterday, trying to do play mp3 files got > trash that was vaguely recognizable as a seriously distorted version of the > original piece. I did some trolling of the cvsweb and decided to roll back to > a fixed date (2001.03.24.00.00.00) before the megapatch. I've rebuilt the > .ko files and unloaded/reloaded them; I now have working sound. > > The failing sound also generated this error > > Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead > Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead > > The probe message "before" (removing megapatch) - > > Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 > > The probe message "after" (removing megapatch) - > > Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 > > And, somewhere in here, "hwintr went backwards" went away. > > Hope this helps. Same thing here with Creative AWE64 PnP ISA sound card. pcm1: play interrupt timeout, channel dead pcm1: play interrupt timeout, channel dead sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm1: on sbc0 FreeBSD enia.bastun.net 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Apr 19 19:40:03 EEST 2001 root@enia.bastun.net:/usr/src/sys/compile/ENIA i386 Boris Georgiev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 20:13:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from ambar.ofermundo.com.ar (h066060007247.isol.net.ar [66.60.7.247]) by hub.freebsd.org (Postfix) with ESMTP id D6DBE37B424 for ; Thu, 19 Apr 2001 20:13:37 -0700 (PDT) (envelope-from freebsd@grunblatt.com.ar) Received: from laptop.infonegocio.com.ar ([24.232.143.74]) by ambar.ofermundo.com.ar (8.9.3/8.8.7) with ESMTP id XAA09036; Thu, 19 Apr 2001 23:46:17 -0300 Date: Fri, 20 Apr 2001 02:49:07 -0300 (ART) From: Daniel X-X-Sender: To: Scott Hazen Mueller Cc: Subject: Re: sound driver breakage/megapatch In-Reply-To: <200104192302.f3JN2Ik56603@zorba.sf-bay.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 I have the same problem on a Sony VAIO PCG-XG38 running -current pcm0: mem 0xfedf0000-0xfedf7fff irq 9 at device 9.0 on pci0 daniel.- On Thu, 19 Apr 2001, Scott Hazen Mueller wrote: > Date: Thu, 19 Apr 2001 16:02:18 -0700 (PDT) > From: Scott Hazen Mueller > To: freebsd-current@FreeBSD.ORG > Subject: sound driver breakage/megapatch > > It looks like the recent sound driver megapatch broke (at least) the Neomagic > 256AV driver. With a cvsup from yesterday, trying to do play mp3 files got > trash that was vaguely recognizable as a seriously distorted version of the > original piece. I did some trolling of the cvsweb and decided to roll back to > a fixed date (2001.03.24.00.00.00) before the megapatch. I've rebuilt the > .ko files and unloaded/reloaded them; I now have working sound. > > The failing sound also generated this error > > Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead > Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead > > The probe message "before" (removing megapatch) - > > Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 > > The probe message "after" (removing megapatch) - > > Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 > > And, somewhere in here, "hwintr went backwards" went away. > > Hope this helps. > > \scott > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 20:31: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id EDC5037B422 for ; Thu, 19 Apr 2001 20:30:59 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA42925; Thu, 19 Apr 2001 20:30:58 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3ADFAD72.ED8A09DD@DougBarton.net> Date: Thu, 19 Apr 2001 20:30:58 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas D. Dean" Cc: freebsd-current@FreeBSD.ORG Subject: Re: etc/* in pending release References: <200104171616.f3HGG6J33776@celebris.tddhome> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas D. Dean" wrote: > > I am planning to shift a machine from -current to the pending release. > > I have tracked -current (SMP) on this machine for > 4 years. But, > now, I need to depend on it - it is old, making a net server. > > What date were the etc/* files frozen for the pending release? Err... the upcoming release is in releng_4. It has nothing to do with -current. -- "One thing they don't tell you about doing experimental physics is that sometimes you must work under adverse conditions ... like a state of sheer terror." -- W. K. Hartmann Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 21:57:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 399DC37B423 for ; Thu, 19 Apr 2001 21:57:33 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f3K4vWt46032; Fri, 20 Apr 2001 00:57:32 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010419153913.A74863@bsdwins.com> References: <20010419153913.A74863@bsdwins.com> Date: Fri, 20 Apr 2001 00:57:29 -0400 To: "John W. De Boskey" , Current List From: Garance A Drosihn Subject: Re: cp -d dir patch for review (or 'xargs'?) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:39 PM -0400 4/19/01, John W. De Boskey wrote: > I have added a -d dir option to cp. This allows the target >directory to be specified at the head of the command line >instead of the tail. This makes cp work much more nicely with >tools like xargs... (allowing for major performance improvements >over inline shell loops). > >The patch is at: > http://www.freebsd.org/~jwd/cp-d.patch > >which allows: > cp -d target_directory source1 source2 ... sourceN > >and/or > cat big_file_list | xargs cp -d target_directory While I can see how this is useful for 'cp', it only fixes that how xargs works wrt that one command. It doesn't do anything for 'mv', for instance. It seems to me that the problem here is due to xargs, not cp. What other tools are there like xargs, where this new option would really be useful? What I'm wondering is if it would be better to add a new option to 'xargs' itself. Something like: cat big_file_list | xargs -last target_directory cp Or maybe something to indicate where the list of arguments should go in a command. Hrm. Let's say '-Y replstr' or '-y[replstr]' (no blank after -y). If no [replstr] is given on -y, it defaults to the two characters '[]'. Then one might do: cat big_file_list | xargs -y cp [] target_directory This is similar to the '-I' and '-i' parameters on the xargs command that I see in solaris, except that '-I' (stands for "insert mode") forces xarg to build a separate command for each line it is being fed, and for -I/-i the replstr can be specified multiple times in the command xargs will be executing. I picked -Y and -y for no other reason than they didn't seem to be used... Any other letter would be fine by me. I think both -I/-i and -Y/-y would be useful additions to xargs, and would be a more general solution to the problem you're trying to address. On the other hand, the man page for 'xargs' on FreeBSD says: The xargs utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compliant. so I don't know how we go about adding options to it. On the other hand, that same issue is faced by adding options to 'cp', as there is a similar claim made in cp's man page. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 22: 8:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 6B5B037B422 for ; Thu, 19 Apr 2001 22:08:43 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id E8EA93E2F; Thu, 19 Apr 2001 22:08:42 -0700 (PDT) To: Garance A Drosihn Cc: "John W. De Boskey" , Current List Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: ; from drosih@rpi.edu on "Fri, 20 Apr 2001 00:57:29 -0400" Date: Thu, 19 Apr 2001 22:08:42 -0700 From: Dima Dorfman Message-Id: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > Or maybe something to indicate where the list of arguments > should go in a command. Hrm. Let's say '-Y replstr' or > '-y[replstr]' (no blank after -y). If no [replstr] is > given on -y, it defaults to the two characters '[]'. > Then one might do: > cat big_file_list | xargs -y cp [] target_directory This is a great idea! I'm willing to implement it if nobody else wants to. > you're trying to address. On the other hand, the man page > for 'xargs' on FreeBSD says: > > The xargs utility is expected to be IEEE Std 1003.2 > (``POSIX.2'') compliant. > > so I don't know how we go about adding options to it. On > the other hand, that same issue is faced by adding options > to 'cp', as there is a similar claim made in cp's man page. I don't think it's a problem. We're adding new options here, not changing--sometimes known as breaking--what already exists. I'm pretty sure that the standards don't say anything to the effect of, "You must support this and nothing else." That'd be rather silly. Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 19 22:57:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 22E2437B42C for ; Thu, 19 Apr 2001 22:57:07 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f3K5v4t74646; Fri, 20 Apr 2001 01:57:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> References: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Date: Fri, 20 Apr 2001 01:57:01 -0400 To: Dima Dorfman From: Garance A Drosihn Subject: Re: cp -d dir patch for review (or 'xargs'?) Cc: "John W. De Boskey" , Current List , wollman@khavrinen.lcs.mit.edu Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:08 PM -0700 4/19/01, Dima Dorfman wrote: >Garance A Drosihn writes: > > Or maybe something to indicate where the list of arguments >> should go in a command. Hrm. Let's say '-Y replstr' or >> '-y[replstr]' (no blank after -y). If no [replstr] is >> given on -y, it defaults to the two characters '[]'. >> Then one might do: >> cat big_file_list | xargs -y cp [] target_directory > >This is a great idea! I'm willing to implement it if nobody >else wants to. Woo-hoo! Someone to do the work! Yes! > > you're trying to address. On the other hand, the man page >> for 'xargs' on FreeBSD says: >> >> The xargs utility is expected to be IEEE Std 1003.2 >> (``POSIX.2'') compliant. >> >> so I don't know how we go about adding options to it. On >> the other hand, that same issue is faced by adding options >> to 'cp', as there is a similar claim made in cp's man page. > >I don't think it's a problem. We're adding new options here, not >changing--sometimes known as breaking--what already exists. I'm >pretty sure that the standards don't say anything to the effect of, >"You must support this and nothing else." That'd be rather silly. Actually, it's not as silly as it sounds. If you're writing scripts, and you use those extra parameters, then you'll get into trouble when running the script on some other POSIX-based OS which does not have these new options. I really do like the idea of both the -I/-i options from solaris, and the -Y/-y options that I just dreamed up, but I'm not sure what the right procedure is to introduce them (and eventually have them standard everywhere... :-). Maybe we could initially have a 'yargs' command, which is just like 'xargs' except that it adds those four options. Maybe I'm just overly pedantic. Hmm. Checking my copy of "Single Unix Specification, v2", the -I/-i parameters are defined in THAT standard, but it doesn't have anything matching my -Y/-y suggestion. Hmm, I wonder if I should be copying this "meta-question" to the mailing list for standardizing things... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 0: 4:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id ECFD937B42C for ; Fri, 20 Apr 2001 00:04:31 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.3/8.11.3) with ESMTP id f3K74Jt81742 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 20 Apr 2001 09:04:20 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.2/8.11.2) id f3K74Jh38969; Fri, 20 Apr 2001 09:04:19 +0200 (CEST) Date: Fri, 20 Apr 2001 09:04:19 +0200 From: Cejka Rudolf To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: Syscons mouse char range redefine proposal Message-ID: <20010420090419.A38573@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ache@nagual.pp.ru on Thu, Apr 19, 2001 at 04:20:43PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrey A. Chernov wrote (2001/04/19): > In any case it must be sysctl-controlled variable and not kernel > option only. Rebuilding whole kernel to just change console language is > superfluous! rc.syscon/rc.conf hooks must be added too. I agree that there should be some rc.* variable. It is not kernel option only. However, it is not sysctl variable (as Kazu was against it and I understand it). It is ioctl() and you can use "vidcontrol -M n" to call this one, but it does not work as it should: Please, could anybody commit very simple patches in PR kern/24437? It was assigned to Kazu by Johan, but it seems that Kazu is really out of time. Or are there any objections? Thanks. -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 1:27:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 05DA637B424 for ; Fri, 20 Apr 2001 01:27:49 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3K8RXn94982; Fri, 20 Apr 2001 11:27:33 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Apr 2001 11:27:33 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Atomic install(1) by default (was: Re: groff breaks "make -j N buildworld") Message-ID: <20010420112733.C87435@sunbay.com> Mail-Followup-To: Bruce Evans , current@FreeBSD.ORG References: <20010419180352.C13567@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Fri, Apr 20, 2001 at 06:39:30AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 06:39:30AM +1000, Bruce Evans wrote: > On Thu, 19 Apr 2001, Ruslan Ermilov wrote: > > > On Thu, Apr 19, 2001 at 05:53:53PM +0300, Ruslan Ermilov wrote: > > > On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: > > > > atomic installation. Atomic installation (but not -C) should be the > > > > default. > > > > > > > This one seems like an easy task, and this is suspicious... How about > > > the attached patch? I have tested it lightly, and haven't found any > > > problems. Will the `make -j32 installworld' of -CURRENT be enough > > > test to commit this and remove -B from Makefile.inc1? > > > > > Damn, forgot to attach the patch. Here it goes... > > This seems to be simple enough. A bit too simple :-). The old > behaviour of deleting the target first is still needed at least > optionally to handle cases where there is no space for a copy. > But then all atomicy goes awry. Should I introduce -r instead (borrowed from NetBSD)? : -r Install to a temporary file and then rename the file to its final : destination name. This can be used for precious files, to avoid : truncation of the original when error conditions (filesystem full : etc.) occur. > Cleaning up the temporary files after a signal is more necessary if -C > is the default. > I didn't mean to volunteer to fix all of the BUGS section :-) > Index: xinstall.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/xinstall/xinstall.c,v > retrieving revision 1.40 > diff -u -p -r1.40 xinstall.c > --- xinstall.c 2000/10/08 09:17:56 1.40 > +++ xinstall.c 2001/04/19 14:38:41 > @@ -53,11 +53,6 @@ static const char rcsid[] = > * attribute changes and don't clear the dump flag. (I think inode > * ctimes are not updated for null attribute changes, but this is a > * bug.) > - * o independent of -C, if a copy must be made, then copy to a tmpfile, > - * set all attributes except the immutable flags, then rename, then > - * set the immutable flags. It's annoying that the immutable flags > - * defeat the atomicicity of rename - it seems that there must be > - * a window where the target is not immutable. > */ > > The comment still applies to the -C case. We now always make a copy, but > for -C this is just a waste of time if the comparison succeeds. > I fail to understand how this still applies. Could you please exaplain it in a bit more details? Also, for -C case, copy is not exactly the waste of time, and this is you who added the comment below in revision 1.4: /* * Unfortunately, because we strip the installed file and not the * original one, it is impossible to do the comparison without * first laboriously copying things over and then comparing. * It may be possible to better optimize the !dostrip case, however. * For further study. */ OTOH, I agree that it is probably makes sense to disable -C and -s combo: /*- * Todo: * o for -C, compare original files except in -s case. And have always compare with original files. What do you think? > ... > @@ -409,7 +404,7 @@ install(from_name, to_name, fset, flags) > * It may be possible to better optimize the !dostrip case, however. > * For further study. > */ > - if (docompare) { > + if (docopy) { > struct stat old_sb, new_sb, timestamp_sb; > int old_fd; > struct utimbuf utb; > @@ -423,7 +418,7 @@ install(from_name, to_name, fset, flags) > if (old_sb.st_flags & NOCHANGEBITS) > (void)fchflags(old_fd, old_sb.st_flags & ~NOCHANGEBITS); > fstat(to_fd, &new_sb); > - if (compare(old_fd, old_to_name, to_fd, to_name, &old_sb, > + if (!docompare || compare(old_fd, old_to_name, to_fd, to_name, &old_sb, > &new_sb)) { > > Line too long. > Argh, I recently added allscreens_flags="VGA_90x25" to /etc/rc.conf :-) Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 1:36:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 3B2F037B424 for ; Fri, 20 Apr 2001 01:36:17 -0700 (PDT) (envelope-from jwd@bsdwins.com) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.1/8.11.0) id f3K8ZwE82145; Fri, 20 Apr 2001 04:35:59 -0400 (EDT) (envelope-from jwd) Date: Fri, 20 Apr 2001 04:35:58 -0400 From: "John W. De Boskey" To: Garance A Drosihn Cc: Dima Dorfman , Current List , wollman@khavrinen.lcs.mit.edu Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010420043558.A81959@bsdwins.com> References: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Fri, Apr 20, 2001 at 01:57:01AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you just want an xargs that supports --replstr/-i simply install: ftp://ftp.gnu.org/gnu/findutils or even more easily: /usr/ports/misc/findutils two comments: I don't want to enter a protracted discussion over the benefits/drawbacks of the current xargs vs an updated xargs, nor try to do a write-from-scratch. The cp -d option has runtime execution of O(1). Xargs addes O(n) due to it's manipulation of the arguement vector in -i mode. The process I'm dealing with already takes many hours to run. I want to reduce time, not increase it. Comments welcome. -john ----- Garance A Drosihn's Original Message ----- > At 10:08 PM -0700 4/19/01, Dima Dorfman wrote: > >Garance A Drosihn writes: > > > Or maybe something to indicate where the list of arguments > >> should go in a command. Hrm. Let's say '-Y replstr' or > >> '-y[replstr]' (no blank after -y). If no [replstr] is > >> given on -y, it defaults to the two characters '[]'. > >> Then one might do: > >> cat big_file_list | xargs -y cp [] target_directory > > > >This is a great idea! I'm willing to implement it if nobody > >else wants to. > > Woo-hoo! Someone to do the work! Yes! > > > > you're trying to address. On the other hand, the man page > >> for 'xargs' on FreeBSD says: > >> > >> The xargs utility is expected to be IEEE Std 1003.2 > >> (``POSIX.2'') compliant. > >> > >> so I don't know how we go about adding options to it. On > >> the other hand, that same issue is faced by adding options > >> to 'cp', as there is a similar claim made in cp's man page. > > > >I don't think it's a problem. We're adding new options here, not > >changing--sometimes known as breaking--what already exists. I'm > >pretty sure that the standards don't say anything to the effect of, > >"You must support this and nothing else." That'd be rather silly. > > Actually, it's not as silly as it sounds. If you're writing > scripts, and you use those extra parameters, then you'll get > into trouble when running the script on some other POSIX-based > OS which does not have these new options. > > I really do like the idea of both the -I/-i options from solaris, > and the -Y/-y options that I just dreamed up, but I'm not sure > what the right procedure is to introduce them (and eventually > have them standard everywhere... :-). Maybe we could initially > have a 'yargs' command, which is just like 'xargs' except that > it adds those four options. Maybe I'm just overly pedantic. > > Hmm. Checking my copy of "Single Unix Specification, v2", the > -I/-i parameters are defined in THAT standard, but it doesn't > have anything matching my -Y/-y suggestion. Hmm, I wonder if > I should be copying this "meta-question" to the mailing list > for standardizing things... > > -- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 3:29:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 424E137B440 for ; Fri, 20 Apr 2001 03:29:19 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3KAU8b69613; Fri, 20 Apr 2001 11:30:10 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3KATF533872; Fri, 20 Apr 2001 11:29:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104201029.f3KATF533872@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Dima Dorfman Cc: Garance A Drosihn , "John W. De Boskey" , Current List , brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Dima Dorfman of "Thu, 19 Apr 2001 22:08:42 PDT." <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 11:29:15 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Garance A Drosihn writes: > > Or maybe something to indicate where the list of arguments > > should go in a command. Hrm. Let's say '-Y replstr' or > > '-y[replstr]' (no blank after -y). If no [replstr] is > > given on -y, it defaults to the two characters '[]'. > > Then one might do: > > cat big_file_list | xargs -y cp [] target_directory > > This is a great idea! I'm willing to implement it if nobody else > wants to. If you add this (which I think is a good idea), please make it option free with {} as the default arglist and -i to override that string in line with sysv's xargs: find something | xargs cp {} target_directory or find something | xargs -i '[]' cp '[]' target_directory Although it's possible to break something that uses a literal {} as an argument, I think this is better than introducing semantics that'll confuse people. > Dima Dorfman > dima@unixfreak.org Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 4:15:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 1AFDF37B423 for ; Fri, 20 Apr 2001 04:15:09 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup7-47.iptelecom.net.ua [212.9.227.175]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id OAA58282; Fri, 20 Apr 2001 14:14:57 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3KBDk202794; Fri, 20 Apr 2001 14:13:46 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3AE019B7.6C76556A@FreeBSD.org> Date: Fri, 20 Apr 2001 14:12:55 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Dima Dorfman Cc: Garance A Drosihn , "John W. De Boskey" , Current List Subject: Re: cp -d dir patch for review (or 'xargs'?) References: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dima Dorfman wrote: > Garance A Drosihn writes: > > Or maybe something to indicate where the list of arguments > > should go in a command. Hrm. Let's say '-Y replstr' or > > '-y[replstr]' (no blank after -y). If no [replstr] is > > given on -y, it defaults to the two characters '[]'. > > Then one might do: > > cat big_file_list | xargs -y cp [] target_directory > > This is a great idea! I'm willing to implement it if nobody else > wants to. > > > you're trying to address. On the other hand, the man page > > for 'xargs' on FreeBSD says: > > > > The xargs utility is expected to be IEEE Std 1003.2 > > (``POSIX.2'') compliant. > > > > so I don't know how we go about adding options to it. On > > the other hand, that same issue is faced by adding options > > to 'cp', as there is a similar claim made in cp's man page. > > I don't think it's a problem. We're adding new options here, not > changing--sometimes known as breaking--what already exists. I'm > pretty sure that the standards don't say anything to the effect of, > "You must support this and nothing else." That'd be rather silly. I don't think that introducing a new option in the tool that expected to be compatible among several systems is a good thing. Once new option is introduced and documented, people would start using it, in many cases even without a notion that this option is FreeBSD specific, which will obviously lead to users' confusion and scripts incompatabilities. The right way to go, IMO, is to introduce a simple wrapper for xargs (say yargs), that it will be clearly documented as a FreeBSD scecific thing. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 6:59:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 579A937B423 for ; Fri, 20 Apr 2001 06:59:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f3KDwg812830; Fri, 20 Apr 2001 07:58:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200104201358.f3KDwg812830@harmony.village.org> To: David Wolfskill Subject: Re: world (still) having trouble (after gdb.291/gdb/defs.h) Cc: bp@butya.kz, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Apr 2001 17:07:19 PDT." <200104120007.f3C07JN67377@bunrab.catwhisker.org> References: <200104120007.f3C07JN67377@bunrab.catwhisker.org> Date: Fri, 20 Apr 2001 07:58:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200104120007.f3C07JN67377@bunrab.catwhisker.org> David Wolfskill writes: : That said, while I was trying to figure out what had gone wrong, I ended : up chasing something that was "merely" a warning, but loks to me as if : it has some unpleasant potential: the dual (conflicting) definitions of : MDF_ACTIVE, thus: : : sys/pccard/cardinfo.h:81:#define MDF_ACTIVE 0x40 /* Context active (read-only) */ : : and : : sys/sys/memrange.h:18:#define MDF_ACTIVE (1<<27) /* currently active */ : : : The notion of the same program (kdump, in this case) actually using both : include files would seem to be a cause for some concern. Don't worry about it. The person who imported the memcontrol stuff didn't check the system closely enough for conflicts. The pccard define has been around since 1996 while the memcontrol one was added in 1999 and still hasn't been fixed :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:11:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 8B54C37B423 for ; Fri, 20 Apr 2001 07:11:43 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3KEBO139285; Fri, 20 Apr 2001 17:11:24 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Apr 2001 17:11:24 +0300 From: Ruslan Ermilov To: Bruce Evans , current@FreeBSD.ORG Subject: Re: Atomic install(1) by default (was: Re: groff breaks "make -j N buildworld") Message-ID: <20010420171124.A38925@sunbay.com> Mail-Followup-To: Bruce Evans , current@FreeBSD.ORG References: <20010419180352.C13567@sunbay.com> <20010420112733.C87435@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010420112733.C87435@sunbay.com>; from ru@FreeBSD.ORG on Fri, Apr 20, 2001 at 11:27:33AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bruce! Forget all of this. I started incorporating OpenBSD fixes to install(1). They seem to cover all the cases you have mentioned. I will send a CFR when I finish. They used your revision 1.4 as the base, and implemented all of the todos, and even more. Thanks, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:30: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mistral.imasy.or.jp (mistral.imasy.or.jp [202.227.24.84]) by hub.freebsd.org (Postfix) with ESMTP id 7E95C37B423 for ; Fri, 20 Apr 2001 07:29:53 -0700 (PDT) (envelope-from mistral@imasy.or.jp) Received: (from yohta@localhost) by mistral.imasy.or.jp (8.11.3/3.7Wpl2-010215) id f3KETm601670; Fri, 20 Apr 2001 23:29:48 +0900 (JST) From: mistral@imasy.or.jp (Yoshihiko SARUMARU) To: freebsd-current@FreeBSD.org Cc: dyama@bres.tsukuba.ac.jp, ush@netlab.is.tsukuba.ac.jp Subject: restore doesn't restore ownership of symbolic link Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.22PL5] 2001-02/07(Wed) Date: Fri, 20 Apr 2001 23:29:46 +0900 Message-ID: <010420232946.M0200857@mistral.imasy.or.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I will report to all that restore command doesn't restore the property of symbolic link at all, that is owner, group, permissions and utime. Yamazaki-san first reported this issue on USENET at fj.os.bsd.freebsd. So I'm Cc'ing he and thread participater. I will propose below quick patch. How do you feel ? My environment is FreeBSD 4.3RC (today). Sorry I don't have current environment. Thanks ! before dump: mistral# ls -l /mnt4 total 1 -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo lrwxr-xr-x 1 yohta wheel 3 3/19 13:17 foos -> foo restore with 4.3-RC restore: mistral# dump 0f - /mnt4 | ( cd /tmp/tmp ; restore rf - ) ... mistral# ls -l /tmp/tmp total 53 -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo lrwx------ 1 root wheel 3 4/20 23:17 foos -> foo -rw------- 1 root wheel 52580 4/20 23:17 restoresymtable restore with patch'ed restore: mistral# dump 0f - /mnt4 | ( cd /tmp/tmp ; /home/yohta/restore/restore rf - ) ... mistral# ls -l total 53 -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo lrwxr-xr-x 1 yohta wheel 3 3/19 13:17 foos -> foo -rw------- 1 root wheel 52580 4/20 23:18 restoresymtable Here is sample patch: --- tape.c.orig Fri Apr 20 22:25:10 2001 +++ tape.c Fri Apr 20 23:12:07 2001 @@ -559,6 +559,14 @@ return (genliteraldir(name, curfile.ino)); case IFLNK: + { + uid_t uid; + gid_t gid; + int ret; + + uid = curfile.dip->di_uid; + gid = curfile.dip->di_gid; + lnkbuf[0] = '\0'; pathlen = 0; getfile(xtrlnkfile, xtrlnkskip); @@ -567,7 +575,13 @@ "%s: zero length symbolic link (ignored)\n", name); return (GOOD); } - return (linkit(lnkbuf, name, SYMLINK)); + ret = linkit(lnkbuf, name, SYMLINK); + (void) lchown(name, uid, gid); + (void) lchmod(name, mode); + lutimes(name, timep); + /* symbolic link doesn't have any flags */ + return (ret); + } case IFIFO: vprintf(stdout, "extract fifo %s\n", name); -- Yoshihiko SARUMARU mail: mistral@imasy.or.jp web: http://www.imasy.or.jp/~mistral/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:34: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 82E9E37B424; Fri, 20 Apr 2001 07:33:51 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 484B5546D; Fri, 20 Apr 2001 16:33:48 +0200 (CEST) Date: Fri, 20 Apr 2001 16:33:48 +0200 From: Anton Berezin To: Maxim Sobolev Cc: markm@FreeBSD.org, current@FreeBSD.org Subject: Re: core(5) implementation using perl(1) Message-ID: <20010420163348.B62303@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Maxim Sobolev , markm@FreeBSD.org, current@FreeBSD.org References: <3ADF0B95.42E19625@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ADF0B95.42E19625@FreeBSD.org>; from sobomax@FreeBSD.org on Thu, Apr 19, 2001 at 07:00:21PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 07:00:21PM +0300, Maxim Sobolev wrote: > Attached script forces perl(1) to dump core, which isn't a good > behaviour IMO (tested on 5-CURRENT and 4.3-RC). Why it is definitely not a good behavior for perl(1), the script is not correct anyway. You need to change " to ' to achieve the result you want. I'll try to make a shorter testcase and submit it to perl developers. Cheers, +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:42:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id AE5A137B424; Fri, 20 Apr 2001 07:42:34 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 91D50546B; Fri, 20 Apr 2001 16:42:31 +0200 (CEST) Date: Fri, 20 Apr 2001 16:42:31 +0200 From: Anton Berezin To: Maxim Sobolev Cc: markm@FreeBSD.org, current@FreeBSD.org Subject: Re: core(5) implementation using perl(1) Message-ID: <20010420164231.C62303@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Maxim Sobolev , markm@FreeBSD.org, current@FreeBSD.org References: <3ADF0B95.42E19625@FreeBSD.org> <20010420163348.B62303@heechee.tobez.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010420163348.B62303@heechee.tobez.org>; from tobez@tobez.org on Fri, Apr 20, 2001 at 04:33:48PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 04:33:48PM +0200, Anton Berezin wrote: > On Thu, Apr 19, 2001 at 07:00:21PM +0300, Maxim Sobolev wrote: > > > Attached script forces perl(1) to dump core, which isn't a good > > behaviour IMO (tested on 5-CURRENT and 4.3-RC). > > Why it is definitely not a good behavior for perl(1), the script is > not correct anyway. You need to change " to ' to achieve the result > you want. > > I'll try to make a shorter testcase and submit it to perl developers. FYI. Here's the minimal coredump case: $ perl -n -e 's||${}|g; s|||' Have not tried with 5.6.1 yet. Cheers, =Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:44:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from adakro.osowa.gda.osk.pl (adakro.osowa.gda.osk.pl [212.244.103.57]) by hub.freebsd.org (Postfix) with ESMTP id 9232237B424 for ; Fri, 20 Apr 2001 07:43:49 -0700 (PDT) (envelope-from kontakt@poznajkraj.pl) Received: from localhost.localdomain (IDENT:root@localhost.localdomain [127.0.0.1]) by adakro.osowa.gda.osk.pl (8.9.3/8.9.3) with SMTP id QAA07254 for ; Fri, 20 Apr 2001 16:44:30 -0400 Message-Id: <200104202044.QAA07254@adakro.osowa.gda.osk.pl> Subject: Ogolnopolski Wortal Turystyczny Content-transfer-encoding: 8bit Content-type: text/plain; charset="iso-8859-2" Mime-version: 1.0 To: freebsd-current@FreeBSD.ORG From: "www.poznajkraj.pl" Date: Fri, 20 Apr 2001 16:44 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OGÓLNOPOLSKI WORTAL KRAJOZNAWCZY HTTP://POZNAJKRAJ.PL TWÓJ PRZEWODNIK PO POLSCE Poznajkraj.pl najdynamiczniej rozwijajħcy siê w Polsce profesjonalny wortal, prezentujħcy kompleksowħ bazê informacji o wypoczynku, rozrywce i kulturze w naszym kraju. Poznajkraj.pl u³atwi Pañstwu planowanie podróży po Polsce, przedstawiajħc szerokħ gamê informacji o regionach, w które chcieliby siê Pañstwo wybraĉ. Poznajkraj.pl pomoże Pañstwu w wyborze, gdzie znaleĵĉ odpowiedniħ kwaterê, gdzie najlepiej zjeĥĉ, gdzie najprzyjemniej spêdziĉ wolny czas. Poznajkraj.pl - piszħ dla nas najznakomitsi autorzy przewodników. Poznajkraj.pl - już ponad 400 artyku³ów z zakresu geografii, historii, etnografii, architektury, przyrodoznawstwa i wielu innych dziedzin; tworzħ one swoisty multimedialny przewodnik po Polsce, który pozwoli na lepsze poznanie naszego kraju. Poznajkraj.pl - prognoza pogody, również w systemie WAP. Poznajkraj.pl - czat, galeria sztuki, ksiêgarnia Już wkrótce wortal bêdzie posiada³ angielskħ, niemieckħ i rosyjskħ wersje jêzykowħ. ZAPRASZAMY! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 7:47:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 0803037B423; Fri, 20 Apr 2001 07:47:41 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup14-27.iptelecom.net.ua [212.9.229.91]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id RAA88297; Fri, 20 Apr 2001 17:47:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3KEkf228441; Fri, 20 Apr 2001 17:46:41 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3AE04BC7.8F20F414@FreeBSD.org> Date: Fri, 20 Apr 2001 17:46:31 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Anton Berezin Cc: markm@FreeBSD.org, current@FreeBSD.org Subject: Re: core(5) implementation using perl(1) References: <3ADF0B95.42E19625@FreeBSD.org> <20010420163348.B62303@heechee.tobez.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anton Berezin wrote: > On Thu, Apr 19, 2001 at 07:00:21PM +0300, Maxim Sobolev wrote: > > > Attached script forces perl(1) to dump core, which isn't a good > > behaviour IMO (tested on 5-CURRENT and 4.3-RC). > > Why it is definitely not a good behavior for perl(1), the script is > not correct anyway. You need to change " to ' to achieve the result > you want. I know that there is an error. But coredumping is not a best error handling out there ;). > I'll try to make a shorter testcase and submit it to perl developers. Ok, thank you! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 8:19:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 46D2E37B42C for ; Fri, 20 Apr 2001 08:19:13 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA49875; Fri, 20 Apr 2001 11:19:09 -0400 (EDT) (envelope-from wollman) Date: Fri, 20 Apr 2001 11:19:09 -0400 (EDT) From: Garrett Wollman Message-Id: <200104201519.LAA49875@khavrinen.lcs.mit.edu> To: Garance A Drosihn Cc: "John W. De Boskey" , Current List Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: References: <20010419153913.A74863@bsdwins.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > '-y[replstr]' (no blank after -y). Prohibited by POSIX. The `xargs' utility ``shall'' follow the Utility Syntax Guidelines. > so I don't know how we go about adding options to it. POSIX is clear on this issue: the implementation may add any options it wishes, provided that those options are documented. Of course, if a POSIX working group happens to choose ``your'' option letter next time they add an option to that utility, you lose. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 8:57: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3757A37B424 for ; Fri, 20 Apr 2001 08:56:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA15003; Fri, 20 Apr 2001 08:56:38 -0700 Date: Fri, 20 Apr 2001 08:56:37 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoshihiko SARUMARU Cc: freebsd-current@FreeBSD.ORG, dyama@bres.tsukuba.ac.jp, ush@netlab.is.tsukuba.ac.jp Subject: Re: restore doesn't restore ownership of symbolic link In-Reply-To: <010420232946.M0200857@mistral.imasy.or.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 It seems good, but shouldn't it be: ret = linkit(lnkbuf, name, SYMLINK); if (ret == 0) { if (lchown(name, uid, gid)) perror(name); if (lchmod(name, mode)) perror(name); lutimes(name, timep); } /* symbolic link doesn't have any flags */ return (ret); On Fri, 20 Apr 2001, Yoshihiko SARUMARU wrote: > Hello all, > > I will report to all that restore command doesn't restore the > property of symbolic link at all, that is owner, group, > permissions and utime. > > Yamazaki-san first reported this issue on USENET at > fj.os.bsd.freebsd. So I'm Cc'ing he and thread participater. > > I will propose below quick patch. How do you feel ? > > My environment is FreeBSD 4.3RC (today). Sorry I don't have > current environment. > > Thanks ! > > > before dump: > mistral# ls -l /mnt4 > total 1 > -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo > lrwxr-xr-x 1 yohta wheel 3 3/19 13:17 foos -> foo > > restore with 4.3-RC restore: > mistral# dump 0f - /mnt4 | ( cd /tmp/tmp ; restore rf - ) > ... > mistral# ls -l /tmp/tmp > total 53 > -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo > lrwx------ 1 root wheel 3 4/20 23:17 foos -> foo > -rw------- 1 root wheel 52580 4/20 23:17 restoresymtable > > restore with patch'ed restore: > mistral# dump 0f - /mnt4 | ( cd /tmp/tmp ; /home/yohta/restore/restore rf - ) > ... > mistral# ls -l > total 53 > -rw-r--r-- 1 root wheel 5 1/ 3 17:33 foo > lrwxr-xr-x 1 yohta wheel 3 3/19 13:17 foos -> foo > -rw------- 1 root wheel 52580 4/20 23:18 restoresymtable > > > Here is sample patch: > --- tape.c.orig Fri Apr 20 22:25:10 2001 > +++ tape.c Fri Apr 20 23:12:07 2001 > @@ -559,6 +559,14 @@ > return (genliteraldir(name, curfile.ino)); > > case IFLNK: > + { > + uid_t uid; > + gid_t gid; > + int ret; > + > + uid = curfile.dip->di_uid; > + gid = curfile.dip->di_gid; > + > lnkbuf[0] = '\0'; > pathlen = 0; > getfile(xtrlnkfile, xtrlnkskip); > @@ -567,7 +575,13 @@ > "%s: zero length symbolic link (ignored)\n", name); > return (GOOD); > } > - return (linkit(lnkbuf, name, SYMLINK)); > + ret = linkit(lnkbuf, name, SYMLINK); > + (void) lchown(name, uid, gid); > + (void) lchmod(name, mode); > + lutimes(name, timep); > + /* symbolic link doesn't have any flags */ > + return (ret); > + } > > case IFIFO: > vprintf(stdout, "extract fifo %s\n", name); > > -- > Yoshihiko SARUMARU > mail: mistral@imasy.or.jp web: http://www.imasy.or.jp/~mistral/ > > 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 Apr 20 9: 6:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id AFB4937B422 for ; Fri, 20 Apr 2001 09:06:05 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id 8D967D9B8; Fri, 20 Apr 2001 17:06:03 +0100 (BST) Message-ID: <003301c0c9b3$ed614e00$0504020a@haveblue> From: "Cameron Grant" To: "Scott Hazen Mueller" , References: <200104192302.f3JN2Ik56603@zorba.sf-bay.org> Subject: Re: sound driver breakage/megapatch Date: Fri, 20 Apr 2001 17:06:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead > Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead can anyone suffering from this problem confirm that the hardware is generating interrupts? use 'systat -vm 1' to watch while you try to play sound. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 9:11:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id BC8F437B422; Fri, 20 Apr 2001 09:10:11 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3KGA8F52731; Fri, 20 Apr 2001 19:10:08 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Apr 2001 19:10:08 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: current@FreeBSD.org, hackers@FreeBSD.org Subject: [CFR] OpenBSD install(1) fixes: atomic install, etc. Message-ID: <20010420191008.A51313@sunbay.com> Mail-Followup-To: Bruce Evans , current@FreeBSD.org, hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! The attached patch incorporates most of OpenBSD fixes to install(1). It does not include manpage update. Most significant changes are: o All TODOs are acted upon. o New flags: -b and -B : -b Backup any existing files before overwriting them by : renaming them to file.old. See -B for specifying a : different backup suffix. : : -B suffix : Use suffix as the backup suffix if -b is given. o New flag: -S (atomic install) : -S Safe copy. Normally, install unlinks an existing target before : installing the new file. With the -S flag a temporary file is : used and then renamed to be the target. The reason this is safer : is that if the copy or rename fails, the existing target is left : untouched. o The -c flag is now the default, and only provided for backwards compatibility. We now never remove the original file. o Flags -v and -D were withdrawn. o strip(1) failure is not considered fatal. Please review. Thanks, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: xinstall.c =================================================================== RCS file: /home/ncvs/src/usr.bin/xinstall/xinstall.c,v retrieving revision 1.40 diff -u -p -r1.40 xinstall.c --- xinstall.c 2000/10/08 09:17:56 1.40 +++ xinstall.c 2001/04/20 15:42:20 @@ -45,21 +45,6 @@ static const char rcsid[] = "$FreeBSD: src/usr.bin/xinstall/xinstall.c,v 1.40 2000/10/08 09:17:56 bde Exp $"; #endif /* not lint */ -/*- - * Todo: - * o for -C, compare original files except in -s case. - * o for -C, don't change anything if nothing needs be changed. In - * particular, don't toggle the immutable flags just to allow null - * attribute changes and don't clear the dump flag. (I think inode - * ctimes are not updated for null attribute changes, but this is a - * bug.) - * o independent of -C, if a copy must be made, then copy to a tmpfile, - * set all attributes except the immutable flags, then rename, then - * set the immutable flags. It's annoying that the immutable flags - * defeat the atomicicity of rename - it seems that there must be - * a window where the target is not immutable. - */ - #include #include #include @@ -82,45 +67,29 @@ static const char rcsid[] = #include "pathnames.h" -/* Bootstrap aid - this doesn't exist in most older releases */ -#ifndef MAP_FAILED -#define MAP_FAILED ((void *)-1) /* from */ -#endif - -int debug, docompare, docopy, dodir, dopreserve, dostrip, nommap, verbose; -int mode = S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH; -char *group, *owner, pathbuf[MAXPATHLEN]; -char pathbuf2[MAXPATHLEN]; - #define DIRECTORY 0x01 /* Tell install it's a directory. */ #define SETFLAGS 0x02 /* Tell install to set flags. */ #define NOCHANGEBITS (UF_IMMUTABLE | UF_APPEND | SF_IMMUTABLE | SF_APPEND) +#define BACKUP_SUFFIX ".old" +struct passwd *pp; +struct group *gp; +int dobackup, docompare, dodir, dopreserve, dostrip, nommap, safecopy; +int mode = S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH; +char pathbuf[MAXPATHLEN], tempfile[MAXPATHLEN]; +char *suffix = BACKUP_SUFFIX; +uid_t uid; +gid_t gid; + void copy __P((int, char *, int, char *, off_t)); -int compare __P((int, const char *, int, const char *, - const struct stat *, const struct stat *)); +int compare __P((int, const char *, size_t, int, const char *, size_t)); +int create_newfile __P((char *, struct stat *)); +int create_tempfile __P((char *, char *, size_t)); void install __P((char *, char *, u_long, u_int)); void install_dir __P((char *)); void strip __P((char *)); -void usage __P((void)); int trymmap __P((int)); - -#define ALLOW_NUMERIC_IDS 1 -#ifdef ALLOW_NUMERIC_IDS - -uid_t uid = -1; -gid_t gid = -1; - -uid_t resolve_uid __P((char *)); -gid_t resolve_gid __P((char *)); -u_long numeric_id __P((char *, char *)); - -#else - -struct passwd *pp; -struct group *gp; - -#endif /* ALLOW_NUMERIC_IDS */ +void usage __P((void)); int main(argc, argv) @@ -132,20 +101,23 @@ main(argc, argv) u_long fset; u_int iflags; int ch, no_target; - char *flags, *to_name; + char *flags, *to_name, *group = NULL, *owner = NULL; iflags = 0; - while ((ch = getopt(argc, argv, "CcdDf:g:m:Mo:psv")) != -1) + while ((ch = getopt(argc, argv, "BbCcdf:g:Mm:o:pSs")) != -1) switch((char)ch) { + case 'B': + suffix = optarg; + /* FALLTHROUGH */ + case 'b': + dobackup = 1; + break; case 'C': - docompare = docopy = 1; + docompare = 1; break; case 'c': - docopy = 1; + /* For backwards compatibility. */ break; - case 'D': - debug++; - break; case 'd': dodir = 1; break; @@ -158,6 +130,9 @@ main(argc, argv) case 'g': group = optarg; break; + case 'M': + nommap = 1; + break; case 'm': if (!(set = setmode(optarg))) errx(EX_USAGE, "invalid file mode: %s", @@ -165,21 +140,18 @@ main(argc, argv) mode = getmode(set, 0); free(set); break; - case 'M': - nommap = 1; - break; case 'o': owner = optarg; break; case 'p': - docompare = docopy = dopreserve = 1; + docompare = dopreserve = 1; + break; + case 'S': + safecopy = 1; break; case 's': dostrip = 1; break; - case 'v': - verbose = 1; - break; case '?': default: usage(); @@ -188,29 +160,24 @@ main(argc, argv) argv += optind; /* some options make no sense when creating directories */ - if (dostrip && dodir) + if ((safecopy || docompare || dostrip) && dodir) usage(); /* must have at least two arguments, except when creating directories */ if (argc < 2 && !dodir) usage(); - -#ifdef ALLOW_NUMERIC_IDS - if (owner) - uid = resolve_uid(owner); - if (group) - gid = resolve_gid(group); + /* need to make a temp copy so we can compare stripped version */ + if (docompare && dostrip) + safecopy = 1; -#else - /* get group and owner id's */ - if (owner && !(pp = getpwnam(owner))) - errx(EX_NOUSER, "unknown user %s", owner); - if (group && !(gp = getgrnam(group))) + if (group && !(gp = getgrnam(group)) && !isdigit(*group)) errx(EX_NOUSER, "unknown group %s", group); - -#endif /* ALLOW_NUMERIC_IDS */ + gid = (group) ? ((gp) ? gp->gr_gid : (gid_t)strtoul(group, NULL, 10)) : (gid_t)-1; + if (owner && !(pp = getpwnam(owner)) && !isdigit(*owner)) + errx(EX_NOUSER, "unknown user %s", owner); + uid = (owner) ? ((pp) ? pp->pw_uid : (uid_t)strtoul(owner, NULL, 10)) : (uid_t)-1; if (dodir) { for (; *argv != NULL; ++argv) @@ -220,7 +187,7 @@ main(argc, argv) } no_target = stat(to_name = argv[argc - 1], &to_sb); - if (!no_target && (to_sb.st_mode & S_IFMT) == S_IFDIR) { + if (!no_target && S_ISDIR(to_sb.st_mode)) { for (; *argv != to_name; ++argv) install(*argv, to_name, fset, iflags | DIRECTORY); exit(EX_OK); @@ -242,72 +209,12 @@ main(argc, argv) to_sb.st_ino == from_sb.st_ino) errx(EX_USAGE, "%s and %s are the same file", *argv, to_name); -/* - * XXX - It's not at all clear why this code was here, since it completely - * duplicates code install(). The version in install() handles the -C flag - * correctly, so we'll just disable this for now. - */ -#if 0 - /* - * Unlink now... avoid ETXTBSY errors later. Try and turn - * off the append/immutable bits -- if we fail, go ahead, - * it might work. - */ - if (to_sb.st_flags & NOCHANGEBITS) - (void)chflags(to_name, - to_sb.st_flags & ~(NOCHANGEBITS)); - (void)unlink(to_name); -#endif } install(*argv, to_name, fset, iflags); exit(EX_OK); /* NOTREACHED */ } -#ifdef ALLOW_NUMERIC_IDS - -uid_t -resolve_uid(s) - char *s; -{ - struct passwd *pw; - - return ((pw = getpwnam(s)) == NULL) ? - (uid_t) numeric_id(s, "user") : pw->pw_uid; -} - -gid_t -resolve_gid(s) - char *s; -{ - struct group *gr; - - return ((gr = getgrnam(s)) == NULL) ? - (gid_t) numeric_id(s, "group") : gr->gr_gid; -} - -u_long -numeric_id(name, type) - char *name, *type; -{ - u_long val; - char *ep; - - /* - * XXX - * We know that uid_t's and gid_t's are unsigned longs. - */ - errno = 0; - val = strtoul(name, &ep, 10); - if (errno) - err(EX_NOUSER, "%s", name); - if (*ep != '\0') - errx(EX_NOUSER, "unknown %s %s", type, name); - return (val); -} - -#endif /* ALLOW_NUMERIC_IDS */ - /* * install -- * build a path name and install the file @@ -319,12 +226,15 @@ install(from_name, to_name, fset, flags) u_int flags; { struct stat from_sb, to_sb; - int devnull, from_fd, to_fd, serrno; - char *p, *old_to_name = 0; + struct utimbuf utb; + int devnull, from_fd, to_fd, serrno, files_match = 0; + char *p; - if (debug >= 2 && !docompare) - fprintf(stderr, "install: invoked without -C for %s to %s\n", - from_name, to_name); +#ifdef __GNUC__ /* XXX: to shut up gcc warnings */ + (void)&from_fd; +#endif + + (void)memset((void *)&from_sb, 0, sizeof(from_sb)); /* If try to install NULL file to a directory, fails. */ if (flags & DIRECTORY || strcmp(from_name, _PATH_DEVNULL)) { @@ -343,143 +253,155 @@ install(from_name, to_name, fset, flags) } devnull = 0; } else { - from_sb.st_flags = 0; /* XXX */ devnull = 1; } - if (docompare) { - old_to_name = to_name; - /* - * Make a new temporary file in the same file system - * (actually, in in the same directory) as the target so - * that the temporary file can be renamed to the target. - */ - snprintf(pathbuf2, sizeof pathbuf2, "%s", to_name); - p = strrchr(pathbuf2, '/'); - p = (p == NULL ? pathbuf2 : p + 1); - snprintf(p, &pathbuf2[sizeof pathbuf2] - p, "INS@XXXX"); - to_fd = mkstemp(pathbuf2); + if (stat(to_name, &to_sb) == 0) { + /* Only compare against regular files. */ + if (docompare && !S_ISREG(to_sb.st_mode)) { + docompare = 0; + errno = EFTYPE; + warn("%s", to_name); + } + } else if (docompare) { + /* File does not exist so silently ignore compare flag. */ + docompare = 0; + } + + if (safecopy) { + to_fd = create_tempfile(to_name, tempfile, sizeof(tempfile)); if (to_fd < 0) - /* XXX should fall back to not comparing. */ - err(EX_OSERR, "mkstemp: %s for %s", pathbuf2, to_name); - to_name = pathbuf2; + err(EX_OSERR, "%s", tempfile); + } else if (docompare && !dostrip) { + if ((to_fd = open(to_name, O_RDONLY, 0)) < 0) + err(EX_OSERR, "%s", to_name); } else { - /* - * Unlink now... avoid errors later. Try to turn off the - * append/immutable bits -- if we fail, go ahead, it might - * work. - */ - if (stat(to_name, &to_sb) == 0 && to_sb.st_flags & NOCHANGEBITS) - (void)chflags(to_name, to_sb.st_flags & ~NOCHANGEBITS); - unlink(to_name); - - /* Create target. */ - to_fd = open(to_name, - O_CREAT | O_RDWR | O_TRUNC, S_IRUSR | S_IWUSR); - if (to_fd < 0) + if ((to_fd = create_newfile(to_name, &to_sb)) < 0) err(EX_OSERR, "%s", to_name); } if (!devnull) { if ((from_fd = open(from_name, O_RDONLY, 0)) < 0) { serrno = errno; - (void)unlink(to_name); + (void)unlink(safecopy ? tempfile : to_name); errno = serrno; err(EX_OSERR, "%s", from_name); } - copy(from_fd, from_name, to_fd, to_name, from_sb.st_size); - (void)close(from_fd); + + if (docompare && !safecopy) { + files_match = !(compare(from_fd, from_name, + (size_t)from_sb.st_size, to_fd, + to_name, (size_t)to_sb.st_size)); + + /* Truncate "to" file for copy unless we match */ + if (!files_match) { + (void)close(to_fd); + if ((to_fd = create_newfile(to_name, &to_sb)) < 0) + err(EX_OSERR, "%s", to_name); + } + } + if (!files_match) + copy(from_fd, from_name, to_fd, + safecopy ? tempfile : to_name, from_sb.st_size); } if (dostrip) { - (void)close(to_fd); + strip(safecopy ? tempfile : to_name); - strip(to_name); - - /* Reopen target. */ - to_fd = open(to_name, O_RDWR, 0); + /* + * Re-open our fd on the target, in case we used a strip + * that does not work in-place -- like GNU binutils strip. + */ + close(to_fd); + to_fd = open(safecopy ? tempfile : to_name, O_RDONLY, 0); if (to_fd < 0) - err(EX_OSERR, "%s", to_name); + err(EX_OSERR, "stripping %s", to_name); } /* - * Unfortunately, because we strip the installed file and not the - * original one, it is impossible to do the comparison without - * first laboriously copying things over and then comparing. - * It may be possible to better optimize the !dostrip case, however. - * For further study. + * Compare the (possibly stripped) temp file to the target. */ - if (docompare) { - struct stat old_sb, new_sb, timestamp_sb; - int old_fd; - struct utimbuf utb; - - old_fd = open(old_to_name, O_RDONLY, 0); - if (old_fd < 0 && errno == ENOENT) - goto different; - if (old_fd < 0) - err(EX_OSERR, "%s", old_to_name); - fstat(old_fd, &old_sb); - if (old_sb.st_flags & NOCHANGEBITS) - (void)fchflags(old_fd, old_sb.st_flags & ~NOCHANGEBITS); - fstat(to_fd, &new_sb); - if (compare(old_fd, old_to_name, to_fd, to_name, &old_sb, - &new_sb)) { -different: - if (debug != 0) - fprintf(stderr, - "install: renaming for %s: %s to %s\n", - from_name, to_name, old_to_name); - if (verbose != 0) - printf("install: %s -> %s\n", - from_name, old_to_name); - if (dopreserve && stat(from_name, ×tamp_sb) == 0) { - utb.actime = timestamp_sb.st_atime; - utb.modtime = timestamp_sb.st_mtime; - (void)utime(to_name, &utb); + if (safecopy && docompare) { + int temp_fd = to_fd; + struct stat temp_sb; + + /* Re-open to_fd using the real target name. */ + if ((to_fd = open(to_name, O_RDONLY, 0)) < 0) + err(EX_OSERR, "%s", to_name); + + if (fstat(temp_fd, &temp_sb)) { + serrno = errno; + (void)unlink(tempfile); + errno = serrno; + err(EX_OSERR, "%s", tempfile); + } + + if (compare(temp_fd, tempfile, (size_t)temp_sb.st_size, to_fd, + to_name, (size_t)to_sb.st_size) == 0) { + /* + * If target has more than one link we need to + * replace it in order to snap the extra links. + * Need to preserve target file times, though. + */ + if (to_sb.st_nlink != 1) { + utb.actime = to_sb.st_atime; + utb.modtime = to_sb.st_mtime; + (void)utime(tempfile, &utb); + } else { + files_match = 1; + (void)unlink(tempfile); } -moveit: - if (rename(to_name, old_to_name) < 0) { + (void) close(temp_fd); + } + } + + /* + * Move the new file into place if doing a safe copy + * and the files are different (or just not compared). + */ + if (safecopy && !files_match) { + /* Try to turn off the immutable bits. */ + if (to_sb.st_flags & (NOCHANGEBITS)) + (void)chflags(to_name, to_sb.st_flags & ~(NOCHANGEBITS)); + if (dobackup) { + char backup[MAXPATHLEN]; + (void)snprintf(backup, MAXPATHLEN, "%s%s", to_name, + suffix); + if (rename(to_name, backup) < 0) { serrno = errno; - unlink(to_name); - unlink(old_to_name); - errno = serrno; - err(EX_OSERR, "rename: %s to %s", to_name, - old_to_name); - } - close(old_fd); - } else { - if (old_sb.st_nlink != 1) { - /* - * Replace the target, although it hasn't - * changed, to snap the extra links. But - * preserve the target file times. - */ - if (fstat(old_fd, ×tamp_sb) == 0) { - utb.actime = timestamp_sb.st_atime; - utb.modtime = timestamp_sb.st_mtime; - (void)utime(to_name, &utb); - } - goto moveit; + unlink(tempfile); + errx(EX_OSERR, "rename: %s to %s: %s", to_name, + backup, strerror(serrno)); } - if (unlink(to_name) < 0) - err(EX_OSERR, "unlink: %s", to_name); - close(to_fd); - to_fd = old_fd; + } + if (rename(tempfile, to_name) < 0) { + serrno = errno; + unlink(tempfile); + errno = serrno; + err(EX_OSERR, "rename: %s to %s", + tempfile, to_name); } - to_name = old_to_name; + + /* Re-open to_fd so we aren't hosed by the rename(2). */ + (void) close(to_fd); + if ((to_fd = open(to_name, O_RDONLY, 0)) < 0) + err(EX_OSERR, "%s", to_name); } /* + * Preserve the timestamp of the source file if necesary. + */ + if (dopreserve && !files_match) { + utb.actime = from_sb.st_atime; + utb.modtime = from_sb.st_mtime; + (void)utime(to_name, &utb); + } + + /* * Set owner, group, mode for target; do the chown first, * chown may lose the setuid bits. */ - if ((group || owner) && -#ifdef ALLOW_NUMERIC_IDS - fchown(to_fd, owner ? uid : -1, group ? gid : -1)) { -#else - fchown(to_fd, owner ? pp->pw_uid : -1, group ? gp->gr_gid : -1)) { -#endif + if ((gid != (gid_t)-1 || uid != (uid_t)-1) && fchown(to_fd, uid, gid)) { serrno = errno; (void)unlink(to_name); errno = serrno; @@ -514,8 +436,8 @@ moveit: } (void)close(to_fd); - if (!docopy && !devnull && unlink(from_name)) - err(EX_OSERR, "%s", from_name); + if (!devnull) + (void)close(from_fd); } /* @@ -523,35 +445,32 @@ moveit: * compare two files; non-zero means files differ */ int -compare(int from_fd, const char *from_name, int to_fd, const char *to_name, - const struct stat *from_sb, const struct stat *to_sb) +compare(int from_fd, const char *from_name, size_t from_len, + int to_fd, const char *to_name, size_t to_len) { char *p, *q; int rv; - size_t tsize; int done_compare; rv = 0; - if (from_sb->st_size != to_sb->st_size) + if (from_len != to_len) return 1; - - tsize = (size_t)from_sb->st_size; - if (tsize <= 8 * 1024 * 1024) { + if (from_len <= 8 * 1024 * 1024) { done_compare = 0; if (trymmap(from_fd) && trymmap(to_fd)) { - p = mmap(NULL, tsize, PROT_READ, MAP_SHARED, from_fd, (off_t)0); + p = mmap(NULL, from_len, PROT_READ, MAP_SHARED, from_fd, (off_t)0); if (p == (char *)MAP_FAILED) goto out; - q = mmap(NULL, tsize, PROT_READ, MAP_SHARED, to_fd, (off_t)0); + q = mmap(NULL, from_len, PROT_READ, MAP_SHARED, to_fd, (off_t)0); if (q == (char *)MAP_FAILED) { - munmap(p, tsize); + munmap(p, from_len); goto out; } - rv = memcmp(p, q, tsize); - munmap(p, tsize); - munmap(q, tsize); + rv = memcmp(p, q, from_len); + munmap(p, from_len); + munmap(q, from_len); done_compare = 1; } out: @@ -586,6 +505,59 @@ compare(int from_fd, const char *from_na } /* + * create_tempfile -- + * create a temporary file based on path and open it + */ +int +create_tempfile(path, temp, tsize) + char *path; + char *temp; + size_t tsize; +{ + char *p; + + (void)strncpy(temp, path, tsize); + temp[tsize - 1] = '\0'; + if ((p = strrchr(temp, '/')) != NULL) + p++; + else + p = temp; + (void)strncpy(p, "INS@XXXXXX", &temp[tsize - 1] - p); + temp[tsize - 1] = '\0'; + + return (mkstemp(temp)); +} + +/* + * create_newfile -- + * create a new file, overwriting an existing one if necessary + */ +int +create_newfile(path, sbp) + char *path; + struct stat *sbp; +{ + char backup[MAXPATHLEN]; + + /* + * Unlink now... avoid ETXTBSY errors later. Try to turn + * off the append/immutable bits -- if we fail, go ahead, + * it might work. + */ + if (sbp->st_flags & NOCHANGEBITS) + (void)chflags(path, sbp->st_flags & ~NOCHANGEBITS); + + if (dobackup) { + (void)snprintf(backup, MAXPATHLEN, "%s%s", path, suffix); + if (rename(path, backup) < 0) + err(EX_OSERR, "rename: %s to %s", path, backup); + } else + (void)unlink(path); + + return(open(path, O_CREAT | O_RDWR | O_TRUNC, S_IRUSR | S_IWUSR)); +} + +/* * copy -- * copy from one file to another */ @@ -600,16 +572,21 @@ copy(from_fd, from_name, to_fd, to_name, char *p, buf[MAXBSIZE]; int done_copy; + /* Rewind file descriptors. */ + if (lseek(from_fd, (off_t)0, SEEK_SET) == (off_t)-1) + err(EX_OSERR, "lseek: %s", from_name); + if (lseek(to_fd, (off_t)0, SEEK_SET) == (off_t)-1) + err(EX_OSERR, "lseek: %s", to_name); + /* * Mmap and write if less than 8M (the limit is so we don't totally * trash memory on big files. This is really a minor hack, but it * wins some CPU back. */ done_copy = 0; - if (size <= 8 * 1048576 && trymmap(from_fd)) { - if ((p = mmap(NULL, (size_t)size, PROT_READ, - MAP_SHARED, from_fd, (off_t)0)) == (char *)MAP_FAILED) - goto out; + if (size <= 8 * 1048576 && trymmap(from_fd) && + (p = mmap(NULL, (size_t)size, PROT_READ, MAP_SHARED, + from_fd, (off_t)0)) != (char *)MAP_FAILED) { if ((nw = write(to_fd, p, size)) != size) { serrno = errno; (void)unlink(to_name); @@ -617,7 +594,6 @@ copy(from_fd, from_name, to_fd, to_name, err(EX_OSERR, "%s", to_name); } done_copy = 1; - out: } if (!done_copy) { while ((nr = read(from_fd, buf, sizeof(buf))) > 0) @@ -656,7 +632,7 @@ strip(to_name) execlp("strip", "strip", to_name, NULL); err(EX_OSERR, "exec(strip)"); default: - if (wait(&status) == -1 || status) { + if (wait(&status) == -1 || !WIFEXITED(status)) { (void)unlink(to_name); exit(EX_SOFTWARE); /* NOTREACHED */ @@ -704,11 +680,12 @@ install_dir(path) void usage() { - (void)fprintf(stderr,"\ -usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2\n\ - install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ...\n\ - fileN directory\n\ - install -d [-v] [-g group] [-m mode] [-o owner] directory ...\n"); + (void)fprintf(stderr, "\ +usage: install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner]\n\ + file1 file2\n\ + install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner]\n\ + file1 ... fileN directory\n\ + install -d [-g group] [-m mode] [-o owner] directory ...\n"); exit(EX_USAGE); /* NOTREACHED */ } --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 9:14:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 61D1637B423 for ; Fri, 20 Apr 2001 09:14:21 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id SAA19086; Fri, 20 Apr 2001 18:14:14 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14qdXx-0008BN-00 for ; Fri, 20 Apr 2001 18:14:13 +0200 Date: Fri, 20 Apr 2001 18:14:13 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: Re: sound driver breakage/megapatch Message-ID: <20010420181413.B18460@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org References: <200104192302.f3JN2Ik56603@zorba.sf-bay.org> <003301c0c9b3$ed614e00$0504020a@haveblue> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003301c0c9b3$ed614e00$0504020a@haveblue>; from gandalf@vilnya.demon.co.uk on Fri, Apr 20, 2001 at 05:06:58PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, When was this megapatch? I have a kernel & world from evening of 18th CEST, and my SB 64 AWE rocks as usual. I even figured out, how to play Shoutcast streams with mpg123 which enabled me to listen to my favourite radio on the console:-) Doing it right now:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 9:23: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 80E7337B424; Fri, 20 Apr 2001 09:22:59 -0700 (PDT) (envelope-from konstantin.chuguev@dante.org.uk) Received: from theta.dante.org.uk ([193.63.211.7] helo=dante.org.uk) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 14qdgP-0004Fj-00; Fri, 20 Apr 2001 17:22:57 +0100 Message-ID: <3AE06267.BE44852F@dante.org.uk> Date: Fri, 20 Apr 2001 17:23:03 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Network Technology to Europe Ltd. X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: ru, en MIME-Version: 1.0 To: Ruslan Ermilov Cc: Bruce Evans , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [CFR] OpenBSD install(1) fixes: atomic install, etc. References: <20010420191008.A51313@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Ruslan Ermilov wrote: > The attached patch incorporates most of OpenBSD fixes to install(1). > It does not include manpage update. Most significant changes are: > > o New flag: -S (atomic install) > > : -S Safe copy. Normally, install unlinks an existing target before > : installing the new file. With the -S flag a temporary file is > : used and then renamed to be the target. The reason this is safer > : is that if the copy or rename fails, the existing target is left > : untouched. > Just curious: why not make this way of doing install default (i.e. always use it)? Regards, Konstantin. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 9:43:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 4DDFC37B423; Fri, 20 Apr 2001 09:43:32 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (dialup15-8.iptelecom.net.ua [212.9.229.136]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id TAA02813; Fri, 20 Apr 2001 19:43:22 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.3/8.11.2) with ESMTP id f3KGg9229112; Fri, 20 Apr 2001 19:42:09 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3AE066C0.6B375985@FreeBSD.org> Date: Fri, 20 Apr 2001 19:41:36 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Konstantin Chuguev Cc: Ruslan Ermilov , Bruce Evans , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [CFR] OpenBSD install(1) fixes: atomic install, etc. References: <20010420191008.A51313@sunbay.com> <3AE06267.BE44852F@dante.org.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Konstantin Chuguev wrote: > Hi, > > Ruslan Ermilov wrote: > > > The attached patch incorporates most of OpenBSD fixes to install(1). > > It does not include manpage update. Most significant changes are: > > > > o New flag: -S (atomic install) > > > > : -S Safe copy. Normally, install unlinks an existing target before > > : installing the new file. With the -S flag a temporary file is > > : used and then renamed to be the target. The reason this is safer > > : is that if the copy or rename fails, the existing target is left > > : untouched. > > > > Just curious: why not make this way of doing install default (i.e. always use > it)? It may effectively doubles disk space requirements during copy (when destination file is not on a sofdep-enabled partition and is not open at the moment when install(8) unlinks it). For small files it doesn't matter, but for a big ones it could lead to a problem. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 10: 3:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 2263137B42C; Fri, 20 Apr 2001 10:03:36 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3KH3KO57392; Fri, 20 Apr 2001 20:03:20 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Apr 2001 20:03:20 +0300 From: Ruslan Ermilov To: Maxim Sobolev Cc: Konstantin Chuguev , Bruce Evans , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [CFR] OpenBSD install(1) fixes: atomic install, etc. Message-ID: <20010420200320.A54192@sunbay.com> Mail-Followup-To: Maxim Sobolev , Konstantin Chuguev , Bruce Evans , current@FreeBSD.org, hackers@FreeBSD.org References: <20010420191008.A51313@sunbay.com> <3AE06267.BE44852F@dante.org.uk> <3AE066C0.6B375985@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AE066C0.6B375985@FreeBSD.org>; from sobomax@FreeBSD.org on Fri, Apr 20, 2001 at 07:41:36PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 07:41:36PM +0300, Maxim Sobolev wrote: > Konstantin Chuguev wrote: > > > Hi, > > > > Ruslan Ermilov wrote: > > > > > The attached patch incorporates most of OpenBSD fixes to install(1). > > > It does not include manpage update. Most significant changes are: > > > > > > o New flag: -S (atomic install) > > > > > > : -S Safe copy. Normally, install unlinks an existing target before > > > : installing the new file. With the -S flag a temporary file is > > > : used and then renamed to be the target. The reason this is safer > > > : is that if the copy or rename fails, the existing target is left > > > : untouched. > > > > > > > Just curious: why not make this way of doing install default (i.e. always use > > it)? > > It may effectively doubles disk space requirements during copy (when destination > file is not on a sofdep-enabled partition and is not open at the moment when > install(8) unlinks it). For small files it doesn't matter, but for a big ones it > could lead to a problem. > I think -S should be made the default for `installworld' (this was the main reason that triggered this work). But I don't think this should be turned `on' by default in install(1). BTW, this binary just completed the `installworld' test on -STABLE. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 10:39:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from ambar.ofermundo.com.ar (h066060007247.isol.net.ar [66.60.7.247]) by hub.freebsd.org (Postfix) with ESMTP id C272E37B43C for ; Fri, 20 Apr 2001 10:39:29 -0700 (PDT) (envelope-from freebsd@grunblatt.com.ar) Received: from dialup212.icatel.net (dialup212.icatel.net [200.47.39.212]) by ambar.ofermundo.com.ar (8.9.3/8.8.7) with ESMTP id OAA12306; Fri, 20 Apr 2001 14:37:50 -0300 Date: Fri, 20 Apr 2001 17:40:45 -0300 (ART) From: Daniel X-X-Sender: To: Cameron Grant Cc: Scott Hazen Mueller , Subject: Re: sound driver breakage/megapatch In-Reply-To: <003301c0c9b3$ed614e00$0504020a@haveblue> 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 No, it's not generating interrupts. On Fri, 20 Apr 2001, Cameron Grant wrote: > Date: Fri, 20 Apr 2001 17:06:58 +0100 > From: Cameron Grant > To: Scott Hazen Mueller , freebsd-current@FreeBSD.ORG > Subject: Re: sound driver breakage/megapatch > > > Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, > channel dead > > Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, > channel dead > > can anyone suffering from this problem confirm that the hardware is > generating interrupts? > > use 'systat -vm 1' to watch while you try to play sound. > > -cg > > > > 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 Apr 20 10:41:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 4089037B43E; Fri, 20 Apr 2001 10:41:23 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3KHfGo60549; Fri, 20 Apr 2001 20:41:16 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Apr 2001 20:41:16 +0300 From: Ruslan Ermilov To: current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [CFR] OpenBSD install(1) fixes: atomic install, etc. Message-ID: <20010420204116.A60253@sunbay.com> Mail-Followup-To: current@FreeBSD.org, hackers@FreeBSD.org References: <20010420191008.A51313@sunbay.com> <3AE06267.BE44852F@dante.org.uk> <3AE066C0.6B375985@FreeBSD.org> <20010420200320.A54192@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010420200320.A54192@sunbay.com>; from ru@FreeBSD.org on Fri, Apr 20, 2001 at 08:03:20PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 08:03:20PM +0300, Ruslan Ermilov wrote: > On Fri, Apr 20, 2001 at 07:41:36PM +0300, Maxim Sobolev wrote: > > Konstantin Chuguev wrote: > > > > > Hi, > > > > > > Ruslan Ermilov wrote: > > > > > > > The attached patch incorporates most of OpenBSD fixes to install(1). > > > > It does not include manpage update. Most significant changes are: > > > > > > > > o New flag: -S (atomic install) > > > > > > > > : -S Safe copy. Normally, install unlinks an existing target before > > > > : installing the new file. With the -S flag a temporary file is > > > > : used and then renamed to be the target. The reason this is safer > > > > : is that if the copy or rename fails, the existing target is left > > > > : untouched. > > > > > > > > > > Just curious: why not make this way of doing install default (i.e. always use > > > it)? > > > > It may effectively doubles disk space requirements during copy (when destination > > file is not on a sofdep-enabled partition and is not open at the moment when > > install(8) unlinks it). For small files it doesn't matter, but for a big ones it > > could lead to a problem. > > > I think -S should be made the default for `installworld' (this was the main > reason that triggered this work). But I don't think this should be turned > `on' by default in install(1). > > BTW, this binary just completed the `installworld' test on -STABLE. > Just tried -j32 installworld with modified install(1) binary for which -S is the default, and it still choked on lib/libncurses. The problem is in bsd.man.mk: we should separate installing of manpages and their MLINKS, otherwise links could be attempted before their originals are installed. Continuing with -DNOMAN now... Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 10:46:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from zork.sf-bay.org (zork.sf-bay.org [192.150.103.29]) by hub.freebsd.org (Postfix) with ESMTP id 50DCF37B42C for ; Fri, 20 Apr 2001 10:46:22 -0700 (PDT) (envelope-from scott@zorch.sf-bay.org) Received: (from uucp@localhost) by zork.sf-bay.org (8.11.1/8.9.3) with UUCP id f3KHjMA70066; Fri, 20 Apr 2001 10:45:22 -0700 (PDT) (envelope-from scott@zorch.sf-bay.org) Received: (from scott@localhost) by zorba.sf-bay.org (8.11.3/8.8.8) id f3KHha102887 for gandalf@vilnya.demon.co.uk; Fri, 20 Apr 2001 10:43:36 -0700 (PDT) (envelope-from scott) Date: Fri, 20 Apr 2001 10:43:36 -0700 (PDT) From: Scott Hazen Mueller Message-Id: <200104201743.f3KHha102887@zorba.sf-bay.org> Subject: Re: sound driver breakage/megapatch To: gandalf@vilnya.demon.co.uk, freebsd-current@freebsd.org X-Envelope-To: gandalf@vilnya.demon.co.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, >channel dead >> Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, >channel dead >can anyone suffering from this problem confirm that the hardware is >generating interrupts? >use 'systat -vm 1' to watch while you try to play sound. Oh, sorry - yes, I can... I watched the pcm interrupt (irq 9 on my box) increment using vmstat -i. I had seen something in the archives about that not happening. \scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 11: 6:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id 3720537B43C for ; Fri, 20 Apr 2001 11:06:46 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id 58A03D9B8; Fri, 20 Apr 2001 19:06:44 +0100 (BST) Message-ID: <007801c0c9c4$c8986f20$0504020a@haveblue> From: "Cameron Grant" To: "Scott Hazen Mueller" , References: <200104201743.f3KHha102887@zorba.sf-bay.org> Subject: Re: sound driver breakage/megapatch Date: Fri, 20 Apr 2001 19:07:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh, sorry - yes, I can... I watched the pcm interrupt (irq 9 on my box) > increment using vmstat -i. I had seen something in the archives about that > not happening. is there any other device using irq 9? -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 11:15:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from zork.sf-bay.org (zork.sf-bay.org [192.150.103.29]) by hub.freebsd.org (Postfix) with ESMTP id 7236137B423 for ; Fri, 20 Apr 2001 11:15:25 -0700 (PDT) (envelope-from scott@zorch.sf-bay.org) Received: (from uucp@localhost) by zork.sf-bay.org (8.11.1/8.9.3) with UUCP id f3KIFIk71330; Fri, 20 Apr 2001 11:15:18 -0700 (PDT) (envelope-from scott@zorch.sf-bay.org) Received: (from scott@localhost) by zorba.sf-bay.org (8.11.3/8.8.8) id f3KIDhv05777 for gandalf@vilnya.demon.co.uk; Fri, 20 Apr 2001 11:13:43 -0700 (PDT) (envelope-from scott) Date: Fri, 20 Apr 2001 11:13:43 -0700 (PDT) From: Scott Hazen Mueller Message-Id: <200104201813.f3KIDhv05777@zorba.sf-bay.org> Subject: Re: sound driver breakage/megapatch To: gandalf@vilnya.demon.co.uk, freebsd-current@freebsd.org X-Envelope-To: gandalf@vilnya.demon.co.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Oh, sorry - yes, I can... I watched the pcm interrupt (irq 9 on my box) >> increment using vmstat -i. I had seen something in the archives about >that >> not happening. >is there any other device using irq 9? vmstat -i interrupt total rate stray irq0 1 0 stray irq6 1 0 stray irq7 1 0 stray irq15 1 0 ata0 irq14 21279 7 ata1 irq15 4 0 atkbd0 irq1 7569 2 psm0 irq12 27669 10 fdc0 irq6 1 0 clk irq0 272328 100 ep0 irq5 122422 44 Total 451276 165 [Sound driver is currently not loaded. Putting the .ko files into loader.conf.local hangs the system during boot? Dunno if this is a clue or no.] grep "irq.*9" /var/log/messages Apr 16 09:46:07 zorba /boot/kernel/kernel: pci0: at 8.0 irq 9 Apr 16 09:46:07 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 17 10:01:53 zorba /boot/kernel/kernel: pci0: at 8.0 irq 9 Apr 17 10:01:53 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 18 10:10:45 zorba /boot/kernel/kernel: pci0: at 8.0 irq 9 Apr 18 10:10:45 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 19 14:44:30 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 Apr 19 18:47:21 zorba /boot/kernel/kernel: pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 I'm pretty sure not. \scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 11:37: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from ambar.ofermundo.com.ar (h066060007247.isol.net.ar [66.60.7.247]) by hub.freebsd.org (Postfix) with ESMTP id D93BE37B422 for ; Fri, 20 Apr 2001 11:36:57 -0700 (PDT) (envelope-from freebsd@grunblatt.com.ar) Received: from dialup212.icatel.net (dialup212.icatel.net [200.47.39.212]) by ambar.ofermundo.com.ar (8.9.3/8.8.7) with ESMTP id PAA12598; Fri, 20 Apr 2001 15:35:45 -0300 Date: Fri, 20 Apr 2001 18:38:39 -0300 (ART) From: Daniel X-X-Sender: To: Cameron Grant Cc: Scott Hazen Mueller , Subject: Re: sound driver breakage/megapatch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry, I was wrong, I have the same problem that Scott: # vmstat -i interrupt total rate stray irq0 1 0 stray irq6 1 0 stray irq7 1 0 ata0 irq14 337983 15 ata1 irq15 20 0 fdc0 irq6 1 0 atkbd0 irq1 46247 2 psm0 irq12 22998 1 clk irq0 2185682 99 rtc irq8 2797782 128 sio1 irq3 251802 11 ed1 irq11 31724 1 Total 5674242 259 # dmesg |grep "irq 9" pcm0: mem 0xfedf0000-0xfedf7fff irq 9 at device 9.0 on pci0 daniel.- On Fri, 20 Apr 2001, Daniel wrote: > Date: Fri, 20 Apr 2001 17:40:45 -0300 (ART) > From: Daniel > To: Cameron Grant > Cc: Scott Hazen Mueller , freebsd-current@FreeBSD.ORG > Subject: Re: sound driver breakage/megapatch > > No, it's not generating interrupts. > > On Fri, 20 Apr 2001, Cameron Grant wrote: > > > Date: Fri, 20 Apr 2001 17:06:58 +0100 > > From: Cameron Grant > > To: Scott Hazen Mueller , freebsd-current@FreeBSD.ORG > > Subject: Re: sound driver breakage/megapatch > > > > > Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, > > channel dead > > > Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, > > channel dead > > > > can anyone suffering from this problem confirm that the hardware is > > generating interrupts? > > > > use 'systat -vm 1' to watch while you try to play sound. > > > > -cg > > > > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 12: 8: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from student.wesleyan.edu (student.wesleyan.edu [129.133.1.63]) by hub.freebsd.org (Postfix) with ESMTP id B0F0537B423 for ; Fri, 20 Apr 2001 12:08:04 -0700 (PDT) (envelope-from vsavichev@wesleyan.edu) Received: (from nobody@localhost) by student.wesleyan.edu (8.9.3/8.9.3) id PAA11832 for freebsd-current@freebsd.org; Fri, 20 Apr 2001 15:08:03 -0400 (EDT) X-Authentication-Warning: student.wesleyan.edu: nobody set sender to vsavichev@wesleyan.edu using -f To: Subject: missing man's files Message-ID: <987793682.3ae08912f26a1@mail.wesleyan.edu> Date: Fri, 20 Apr 2001 15:08:02 -0400 From: MIME-Version: 1.0 Content-Type: text/plain; Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.0-pre13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD ariel.phys.wesleyan.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Fri Apr 20 11:39:31 EDT 2001 root@ariel.phys.wesleyan.edu:/usr/obj/usr/src/sys/ARIEL i386 after last build many man's files are missing, they're there but empty. Was it just my badluck ? -Vlad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 12:12:53 2001 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 513D237B423 for ; Fri, 20 Apr 2001 12:12:51 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3KJCmp19796; Fri, 20 Apr 2001 12:12:48 -0700 (PDT) Date: Fri, 20 Apr 2001 12:12:48 -0700 From: Alfred Perlstein To: vsavichev@wesleyan.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: missing man's files Message-ID: <20010420121248.D1790@fw.wintelcom.net> References: <987793682.3ae08912f26a1@mail.wesleyan.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <987793682.3ae08912f26a1@mail.wesleyan.edu>; from vsavichev@wesleyan.edu on Fri, Apr 20, 2001 at 03:08:02PM -0400 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * vsavichev@wesleyan.edu [010420 12:08] wrote: > FreeBSD ariel.phys.wesleyan.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Fri Apr 20 > 11:39:31 EDT 2001 root@ariel.phys.wesleyan.edu:/usr/obj/usr/src/sys/ARIEL > i386 > after last build many man's files are missing, they're there but empty. > Was it just my badluck ? I think there was groff breakage. > -Vlad > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- -Alfred Perlstein - [alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 14:19:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from nova.sparklist.com (nova.sparklist.com [207.250.144.28]) by hub.freebsd.org (Postfix) with SMTP id 50ED837B440 for ; Fri, 20 Apr 2001 14:18:55 -0700 (PDT) (envelope-from bounce-fwd-newswire-2059525@nova.sparklist.com) X-Mailer: Lyris Web Interface Date: Fri, 20 Apr 2001 15:21:53 -0500 Subject: FirewireDirect Gets A New Spark Mime-Version: 1.0 To: "FirewireDirect.com" From: "FirewireDirect NewsWire" Content-Type: multipart/alternative; boundary="============newsletter============" List-Unsubscribe: Reply-To: "FirewireDirect.com" X-Hosted-By: http://SparkLIST.com/ - The Business Email List Experts Message-Id: <20010420211855.50ED837B440@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --============newsletter============ Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable FirewireDirect is happy to announce the debut and immediate availability of the newest in our series of FireWire storage solutions, the 2.5" Spark II FireWire & USB Portable Hard Drive. The new design means we've retired the number of the original Spark, the popular mobile hard drive that launched our line of FireWire solutions. We've replaced it with an even smaller chassis, and added USB for extra flexability. Come by our web site to see the new package, and order this weekend to receive FREE SHIPPING. Spark II 10GB HDD - $259 Spark II 20GB HDD - $329 Spark II Firewire Enclosure Kit - $119 This offer ends Tuesday, April 24, 200. This is a special offer to subscribers to this list. Please see our web site for info about these offers. --- You are currently subscribed to fwd-newswire as: freebsd-current@freebsd.org To unsubscribe send a blank email to leave-fwd-newswire-2059525T@nova.sparklist.com or visit our subscription page at http://firewiredirect.com/company/newswire/subscribe.shtml --============newsletter============ Content-Type: text/html; charset="iso-8859-1" ; Content-Transfer-Encoding: 8bit
FirewireDirect Newswire April 20, 2001
If you have trouble seeing this email, please click here for help.
FirewireDirect is happy to announce the debut and immediate availability of the newest in our series of FireWire storage solutions, the 2.5" Spark II FireWire & USB Portable Hard Drive.

The new design means we've retired the number of the original Spark, the popular mobile hard drive that launched our line of FireWire solutions. We've replaced it with an even smaller chassis, and added USB for extra flexability.

Come by our web site to see the new package, and order this weekend to receive FREE SHIPPING.

Spark II 10GB HDD - $259

Spark II 20GB HDD - $329

Spark II Firewire Enclosure Kit - $119

This offer ends Tuesday, April 24, 200. This is a special offer to subscribers to this list. Please see our web site for info about these offers.

You received this message because you subscribed to the FirewireDirect Newswire.

You are currently subscribed to fwd-newswire as:
freebsd-current@freebsd.org
To unsubscribe send a blank email to
leave-fwd-newswire-2059525T@nova.sparklist.com
Or visit our subscription page at
http://firewiredirect.com/company/newswire/subscribe.shtml


To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 15: 0:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 27F3A37B43E for ; Fri, 20 Apr 2001 15:00:36 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 70D8617D2E; Sat, 21 Apr 2001 00:00:29 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.1/8.11.1) id f3KLsJU02275 for freebsd-current@freebsd.org; Fri, 20 Apr 2001 23:54:20 +0200 (CEST) (envelope-from schweikh) Date: Fri, 20 Apr 2001 23:54:19 +0200 From: Jens Schweikhardt To: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010420235419.B1276@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, although there was much rejoicing, I think there's no need for a new option to cp. Just use the toolbox, it's not too hard: (cat bigfilelist; echo destdir) | xargs cp Or even echo destdir >>bigfilelist xargs cp < bigfilelist should do the trick. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 15: 7:59 2001 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 D830437B423 for ; Fri, 20 Apr 2001 15:07:55 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([fec0::2e0:7dff:fe81:749d] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.22 #1) id 14qj4E-000BxT-00; Fri, 20 Apr 2001 23:07:54 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.3/8.11.3) id f3KM7rs29964; Fri, 20 Apr 2001 23:07:53 +0100 (BST) (envelope-from ben) Date: Fri, 20 Apr 2001 23:07:53 +0100 From: Ben Smithurst To: Jens Schweikhardt Cc: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010420230753.C44121@scientia.demon.co.uk> References: <20010420235419.B1276@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010420235419.B1276@schweikhardt.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jens Schweikhardt wrote: > although there was much rejoicing, I think there's no need for a > new option to cp. Just use the toolbox, it's not too hard: > > (cat bigfilelist; echo destdir) | xargs cp > > Or even > > echo destdir >>bigfilelist > xargs cp < bigfilelist > > should do the trick. Err, neither of those will work if there are too many filenames for a single invokation of "cp" since none but the last will get the "destdir" argument. -- Ben Smithurst / ben@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 Apr 20 15:11:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 4584D37B43F for ; Fri, 20 Apr 2001 15:11:42 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KMEAf06331; Fri, 20 Apr 2001 15:14:16 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104202214.f3KMEAf06331@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jens Schweikhardt Cc: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-reply-to: Your message of "Fri, 20 Apr 2001 23:54:19 +0200." <20010420235419.B1276@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 15:14:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Folks, > > although there was much rejoicing, I think there's no need for a > new option to cp. Just use the toolbox, it's not too hard: > > (cat bigfilelist; echo destdir) | xargs cp > > Or even > > echo destdir >>bigfilelist > xargs cp < bigfilelist > > should do the trick. No, it won't. Consider a list of files a, b, c, d. You create input to xargs 'a b c d destdir', which it then splits into 'a b c' and 'd destdir'. The first time cp is run, it will probably fail; the second time only 'd' ends up where you expect it. The best solution to this is actually to fix xargs to accept a "command format string", eg. echo list | xargs "cp %s destdir" Probably a better way to do it would be to have the insertion marker an option to xargs: echo list | xargs -s LIST_HERE cp LIST_HERE destdir -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 15:50:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id DA4C237B42C; Fri, 20 Apr 2001 15:49:59 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 9763E3E09; Fri, 20 Apr 2001 15:49:58 -0700 (PDT) To: Brian Somers Cc: Garrett Wollman , "John W. De Boskey" , freebsd-standards@bostonradio.org, Mike Smith , current@freebsd.org, Jens Schweikhardt Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104201911.f3KJB7540090@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on "Fri, 20 Apr 2001 20:11:07 +0100" Date: Fri, 20 Apr 2001 15:49:58 -0700 From: Dima Dorfman Message-Id: <20010420224958.9763E3E09@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ attempting to consolidate two identical threads into one ] Brian Somers writes: > I agree - the script idea doesn't seem right. > > If {} isn't allowed to implicitly mean ``all the arguments that'll > fit'', then I'd vote for using -i (a version that does full grouping) > although I would not vote for the semantics whereby -i must either be > followed directly with the replacement string (with no intervening > spaces) or else have an implicit {} replacement string, ie we should > have these meaning the same thing: > > xargs -i '<<<>>>' command blah '<<<>>>' blah > xargs -i'<<<>>>' command blah '<<<>>>' blah I honestly don't understand the differnece between this and the -y option gad described. Nevertheless, it seems that pretty much everyone agrees that something like this is a good idea. Attached is a patch that adds a -Y option to xargs which does, well, pretty much what I imagine the above would do. Here are a couple of examples: dima@spike% cat test # test input this is just a test; it has no real purpose in life dima@spike% ./xargs -Y {} echo CMD LINE ARGS < test CMD LINE ARGS this is just a test; it has no real purpose in life dima@spike% ./xargs -Y {} echo {} CMD LINE ARGS < test this is just a test; it has no real purpose in life CMD LINE ARGS dima@spike% ./xargs -Y {} echo CMD {} LINE ARGS < test CMD this is just a test; it has no real purpose in life LINE ARGS dima@spike% ./xargs -Y {} echo CMD LINE {} ARGS < test CMD LINE this is just a test; it has no real purpose in life ARGS dima@spike% ./xargs -Y {} echo CMD LINE ARGS {} < test CMD LINE ARGS this is just a test; it has no real purpose in life dima@spike% ./xargs -n 2 -Y {} echo CMD LINE {} ARGS < test CMD LINE this is ARGS CMD LINE just a ARGS CMD LINE test; it ARGS CMD LINE has no ARGS CMD LINE real purpose ARGS CMD LINE in life ARGS I'm not sure the patch is entirely correct. xargs seems to be overly complicated in the way it does some of its processing, but it works and I believe I managed to maintain most of the assumptions it makes. Comments? Suggestions? Thanks, Dima Dorfman dima@unixfreak.org Index: xargs.c =================================================================== RCS file: /st/src/FreeBSD/src/usr.bin/xargs/xargs.c,v retrieving revision 1.9 diff -u -r1.9 xargs.c --- xargs.c 1999/08/28 01:07:50 1.9 +++ xargs.c 2001/04/20 22:37:15 @@ -73,6 +73,8 @@ int cnt, indouble, insingle, nargs, nflag, nline, xflag, wasquoted; char **av, *argp, **ep = env; long arg_max; + int apargs = 0; + char **avv, *replstr = NULL; /* * POSIX.2 limits the exec line length to ARG_MAX - 2K. Running that @@ -96,7 +98,7 @@ nline -= strlen(*ep++) + 1 + sizeof(*ep); } nflag = xflag = wasquoted = 0; - while ((ch = getopt(argc, argv, "0n:s:tx")) != -1) + while ((ch = getopt(argc, argv, "0n:s:txY:")) != -1) switch(ch) { case 'n': nflag = 1; @@ -115,6 +117,9 @@ case '0': zflag = 1; break; + case 'Y': + replstr = optarg; + break; case '?': default: usage(); @@ -144,6 +149,13 @@ else { cnt = 0; do { + if (replstr && strcmp(*argv, replstr) == 0) { + apargs = 1; + *argv++; + for (avv = argv; *avv; *avv++) + cnt += strlen(*avv) + 1; + break; + } cnt += strlen(*bxp++ = *argv) + 1; } while (*++argv); } @@ -211,6 +223,8 @@ if (xp == exp || p > ebp || ch == EOF) { if (xflag && xp != exp && p > ebp) errx(1, "insufficient space for arguments"); + for (avv = argv; apargs && *avv; *avv++) + strlen(*xp++ = *avv) + 1; *xp = NULL; run(av); if (ch == EOF) @@ -253,6 +267,8 @@ if (xflag) errx(1, "insufficient space for arguments"); + for (avv = argv; apargs && *avv; *avv++) + strlen(*xp++ = *avv) + 1; *xp = NULL; run(av); xp = bxp; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 16: 2:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from nova.sparklist.com (nova.sparklist.com [207.250.144.28]) by hub.freebsd.org (Postfix) with SMTP id 46AF537B423 for ; Fri, 20 Apr 2001 16:02:43 -0700 (PDT) (envelope-from sparklist-admin@nova.sparklist.com) Message-Id: X-sparklist-type: unsubscribed From: "SparkLIST.com" Reply-To: "SparkLIST.com" To: freebsd-current@freebsd.org Subject: Re: your unsubscribe request Date: Fri, 20 Apr 2001 18:04:42 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you requested, you have been unsubscribed from 'fwd-newswire'. --- Return-Path: Received: from mailhost.sparknet.net ([207.67.22.123]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Fri, 20 Apr 2001 18:04:41 -0500 Received: from don-oakes.sparklist.com (dhcp-client-26.sparklist.com [207.250.191.151]) by mailhost.sparknet.net (8.10.1/8.10.1) with ESMTP id f3KN6oI12670 for ; Fri, 20 Apr 2001 18:06:50 -0500 Message-Id: <4.3.1.2.20010420175859.00d1ae90@207.67.22.123> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 20 Apr 2001 17:59:06 -0500 To: fwd-newswire-request From: "SparkLIST.com Abuse" Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed # Mail sent to leave-fwd-newswire-2059525t was converted to these commands: unsubscribe fwd-newswire freebsd-current@freebsd.org confirm end # This is the text of the message that triggered the action: Return-Path: Received: from mailhost.sparknet.net ([207.67.22.123]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Fri, 20 Apr 2001 18:04:41 -0500 Received: from don-oakes.sparklist.com (dhcp-client-26.sparklist.com [207.250.191.151]) by mailhost.sparknet.net (8.10.1/8.10.1) with ESMTP id f3KN6oI12670 for ; Fri, 20 Apr 2001 18:06:50 -0500 Message-Id: <4.3.1.2.20010420175859.00d1ae90@207.67.22.123> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 20 Apr 2001 17:59:06 -0500 To: leave-fwd-newswire-2059525T@nova.sparklist.com From: "SparkLIST.com Abuse" Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 18:46: 2 2001 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 52BD537B43F; Fri, 20 Apr 2001 18:45:59 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id LAA25415; Sat, 21 Apr 2001 11:45:57 +1000 Date: Sat, 21 Apr 2001 11:43:16 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: Atomic install(1) by default (was: Re: groff breaks "make -j N buildworld") In-Reply-To: <20010420171124.A38925@sunbay.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 > Forget all of this. I started incorporating OpenBSD fixes to install(1). > They seem to cover all the cases you have mentioned. I will send a CFR > when I finish. They used your revision 1.4 as the base, and implemented > all of the todos, and even more. Ah, good. Rev.1.4 sure was a long time ago. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 18:52: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id BBDCE37B43C for ; Fri, 20 Apr 2001 18:52:06 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id D2B1010F400 for ; Fri, 20 Apr 2001 20:52:11 -0500 (CDT) Message-ID: <001701c0ca05$ae43cca0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: kernel core Date: Fri, 20 Apr 2001 20:52:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm gettind kernel core dumps in the weirdest places with a -current from early today. One place it coredumps is when I run "chsh", another is during a certain part of make install on XFree86-4, the same place every time. I can get some more details if this is an unknown bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 19: 9:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3580F37B440 for ; Fri, 20 Apr 2001 19:09:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3L28wG43624; Fri, 20 Apr 2001 19:08:58 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001701c0ca05$ae43cca0$931576d8@inethouston.net> Date: Fri, 20 Apr 2001 19:08:22 -0700 (PDT) From: John Baldwin To: "David W. Chapman Jr." Subject: RE: kernel core Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-01 David W. Chapman Jr. wrote: > I'm gettind kernel core dumps in the weirdest places with a -current from > early today. One place it coredumps is when I run "chsh", another is during > a certain part of make install on XFree86-4, the same place every time. I > can get some more details if this is an unknown bug. Is it always a sig 11? Can you cvsup or cvs update to specific dates to track down which commit started causing these as well? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Apr 20 19:26:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9064437B424 for ; Fri, 20 Apr 2001 19:26:23 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id TAA68957; Fri, 20 Apr 2001 19:26:18 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104210226.TAA68957@gndrsh.dnsmgr.net> Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010420235419.B1276@schweikhardt.net> from Jens Schweikhardt at "Apr 20, 2001 11:54:19 pm" To: schweikh@schweikhardt.net (Jens Schweikhardt) Date: Fri, 20 Apr 2001 19:26:18 -0700 (PDT) Cc: 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 > > Folks, > > although there was much rejoicing, I think there's no need for a > new option to cp. Just use the toolbox, it's not too hard: > > (cat bigfilelist; echo destdir) | xargs cp I like this version of the patch!! It's much much cleaner than hacking up cp or xargs, it even follows the unix principle of using simple tools and glueing them togeather to do bigger jobs, is unix implementation independent, and is very clear in what it does. [You even taugh this old dog a new trick he totally blanked out on!!] > > Or even > > echo destdir >>bigfilelist > xargs cp < bigfilelist > > should do the trick. I don't like this one, bigfilelist gets modified and may need to be used again for something else. Please don't commit this version of the patch :-) > Regards, > > Jens > -- > Jens Schweikhardt http://www.schweikhardt.net/ > SIGSIG -- signature too long (core dumped) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 19:38:32 2001 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 965C537B42C for ; Fri, 20 Apr 2001 19:38:28 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA28372; Sat, 21 Apr 2001 12:38:03 +1000 Date: Sat, 21 Apr 2001 12:35:22 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: David Wolfskill , bp@butya.kz, current@FreeBSD.ORG Subject: Re: world (still) having trouble (after gdb.291/gdb/defs.h) In-Reply-To: <200104201358.f3KDwg812830@harmony.village.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, 20 Apr 2001, Warner Losh wrote: > In message <200104120007.f3C07JN67377@bunrab.catwhisker.org> David Wolfskill writes: > : The notion of the same program (kdump, in this case) actually using both > : include files would seem to be a cause for some concern. > > Don't worry about it. The person who imported the memcontrol stuff > didn't check the system closely enough for conflicts. The pccard > define has been around since 1996 while the memcontrol one was added > in 1999 and still hasn't been fixed :-) Building with "mkioctls -s" also shows many conflicting numeric ioctl values (probably many more than in 1996). This is mostly another non- problem, since the conflicting values mostly go to different drivers, but it prevents utilities like kdump from interpreting ioctl numbers unambiguously. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 19:39:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdhome.dyndns.org (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 822F037B424 for ; Fri, 20 Apr 2001 19:39:46 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by bsdhome.dyndns.org (8.11.3/8.11.3) with ESMTP id f3L2dhJ41506; Fri, 20 Apr 2001 22:39:44 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: (from bsd@localhost) by vger.bsdhome.com (8.11.3/8.11.1) id f3L2dhe59175; Fri, 20 Apr 2001 22:39:43 -0400 (EDT) (envelope-from bsd) Date: Fri, 20 Apr 2001 22:39:43 -0400 From: Brian Dean To: "Rodney W. Grimes" Cc: Jens Schweikhardt , freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010420223943.A59039@vger.bsdhome.com> References: <20010420235419.B1276@schweikhardt.net> <200104210226.TAA68957@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104210226.TAA68957@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Fri, Apr 20, 2001 at 07:26:18PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote: > > (cat bigfilelist; echo destdir) | xargs cp > > I like this version of the patch!! It's much much cleaner than > hacking up cp or xargs, it even follows the unix principle of > using simple tools and glueing them togeather to do bigger > jobs, is unix implementation independent, and is very clear > in what it does. It's clean, simple, and unfortunately, totally bogus. Try: echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo Now consider what would happen with the above suggested construct with a very long file list. I don't see a problem with adding an option to cp to treat the first argument as the target instead of the last argument. It's a simple solution, the code change is simple, and it produces the exact desired result. What's the problem? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 19:45:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 4CAB337B422; Fri, 20 Apr 2001 19:45:33 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id BDFFD10F400; Fri, 20 Apr 2001 21:45:38 -0500 (CDT) Message-ID: <000501c0ca0d$253834c0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "John Baldwin" Cc: References: Subject: Re: kernel core Date: Fri, 20 Apr 2001 21:45:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's an exact error message because I'm sure I wrongly diagnosed it. Fatal trap 12: pagefault while in kernel mode fault code = supervisor read, page not present kernel: type 12 trap, code = 0 stopped at ffs_valloc+0x8ei cmpb $0,0(%edi,%eax,1) I can still try to play around with cvs dates if needed, just give me a clue on how far back I should start. Its been over a month since I've cvsuped -current besides this morning. ----- Original Message ----- From: "John Baldwin" To: "David W. Chapman Jr." Cc: Sent: Friday, April 20, 2001 9:08 PM Subject: RE: kernel core > > On 21-Apr-01 David W. Chapman Jr. wrote: > > I'm gettind kernel core dumps in the weirdest places with a -current from > > early today. One place it coredumps is when I run "chsh", another is during > > a certain part of make install on XFree86-4, the same place every time. I > > can get some more details if this is an unknown bug. > > Is it always a sig 11? Can you cvsup or cvs update to specific dates to track > down which commit started causing these as well? > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 20: 6:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 836D837B422 for ; Fri, 20 Apr 2001 20:06:41 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from localhost (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.1/8.11.1) with ESMTP id f3L36UM59719; Fri, 20 Apr 2001 21:06:31 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200104210306.f3L36UM59719@hunkular.glarp.com> To: Brian Dean Cc: "Rodney W. Grimes" , Jens Schweikhardt , freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Your message of "Fri, 20 Apr 2001 22:39:43 EDT." <20010420223943.A59039@vger.bsdhome.com> Date: Fri, 20 Apr 2001 21:06:30 -0600 From: Brad Huntting Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Try: > > echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo > > Now consider what would happen with the above suggested construct with > a very long file list. > > I don't see a problem with adding an option to cp to treat the first > argument as the target instead of the last argument. It's a simple > solution, the code change is simple, and it produces the exact desired > result. What's the problem? Unfortunatly, cp is not alone in needing this feature. I think a more sensable approach would be to add an "append args" flag to xargs. For example "--", which could be used like so: xargs cp -- destdir <; Fri, 20 Apr 2001 21:01:07 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA69212; Fri, 20 Apr 2001 21:00:56 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104210400.VAA69212@gndrsh.dnsmgr.net> Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010420223943.A59039@vger.bsdhome.com> from Brian Dean at "Apr 20, 2001 10:39:43 pm" To: bsd@bsdhome.com (Brian Dean) Date: Fri, 20 Apr 2001 21:00:56 -0700 (PDT) Cc: schweikh@schweikhardt.net (Jens Schweikhardt), 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 > On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote: > > > > (cat bigfilelist; echo destdir) | xargs cp > > > > I like this version of the patch!! It's much much cleaner than > > hacking up cp or xargs, it even follows the unix principle of > > using simple tools and glueing them togeather to do bigger > > jobs, is unix implementation independent, and is very clear > > in what it does. > > It's clean, simple, and unfortunately, totally bogus. > > Try: > > echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo > > Now consider what would happen with the above suggested construct with > a very long file list. bleck... try this for your sample: $ (echo 1 2 3 4 5 6 7 8 9 | xargs -n 4) | while read x; do > echo -n $x; echo " dst" > done 1 2 3 4 dst 5 6 7 8 dst 9 dst $ > > I don't see a problem with adding an option to cp to treat the first > argument as the target instead of the last argument. It's a simple > solution, the code change is simple, and it produces the exact desired > result. What's the problem? It's yet another non-portable option. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 21:43:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 2583337B42C; Fri, 20 Apr 2001 21:43:09 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id DF98210F400; Fri, 20 Apr 2001 23:43:14 -0500 (CDT) Message-ID: <000901c0ca1d$9341cfc0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "John Baldwin" Cc: References: <000501c0ca0d$253834c0$931576d8@inethouston.net> Subject: Re: kernel core Date: Fri, 20 Apr 2001 23:43:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried to do an installkernel on a new kernel I built and I got the same error except the last line changed to stopped at ffs_dirpref+0x210 movzbl 0(%ECX,%EAX,1),%EAX Do I have any hope at recovering from this or should I start again with 4 and upgrade to -current. I'm assuming is a problem with the kernel and without being able to update the kernel and install a new one, I don't think I can fix it. ----- Original Message ----- From: "David W. Chapman Jr." To: "John Baldwin" Cc: Sent: Friday, April 20, 2001 9:45 PM Subject: Re: kernel core > Here's an exact error message because I'm sure I wrongly diagnosed it. > > Fatal trap 12: pagefault while in kernel mode > fault code = supervisor read, page not present > kernel: type 12 trap, code = 0 > stopped at ffs_valloc+0x8ei cmpb $0,0(%edi,%eax,1) > > > I can still try to play around with cvs dates if needed, just give me a clue > on how far back I should start. Its been over a month since I've > cvsuped -current besides this morning. > > ----- Original Message ----- > From: "John Baldwin" > To: "David W. Chapman Jr." > Cc: > Sent: Friday, April 20, 2001 9:08 PM > Subject: RE: kernel core > > > > > > On 21-Apr-01 David W. Chapman Jr. wrote: > > > I'm gettind kernel core dumps in the weirdest places with a -current > from > > > early today. One place it coredumps is when I run "chsh", another is > during > > > a certain part of make install on XFree86-4, the same place every time. > I > > > can get some more details if this is an unknown bug. > > > > Is it always a sig 11? Can you cvsup or cvs update to specific dates to > track > > down which commit started causing these as well? > > > > -- > > > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 20 23:43:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id 3928737B424 for ; Fri, 20 Apr 2001 23:43:56 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-1.enteract.com (shell-1.enteract.com [207.229.143.40]) by smtp-2.enteract.com (Postfix) with ESMTP id 64C7E6669 for ; Sat, 21 Apr 2001 01:43:45 -0500 (CDT) Date: Sat, 21 Apr 2001 01:43:45 -0500 (CDT) From: David Scheidt X-Sender: dscheidt@shell-1.enteract.com To: freebsd-current@FreeBSD.ORG Subject: Boot hang with pcm 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 Current as of yesterday afternoon hangs trying to boot on my box with an OPTi931 soundcard installed. It prints the probe, and then hangs. With boot -v, the messages are pcm0: at port 0x5 34-0x537,0x380-0x38b,0x220-0x22f,0xe0c-0xe0f irq 5 drq 0,1 on isa0 mss_init: opti_offset=2 Yanking the card, or removing the driver from the kernel config allows the machine to boot fine. Unfortunatly, I just upgraded from a September 2000 vintage -current, so I don't know when this broke. David -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 5:13:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.dada.it (mail3.dada.it [195.110.96.70]) by hub.freebsd.org (Postfix) with SMTP id 07C9E37B423 for ; Sat, 21 Apr 2001 05:13:32 -0700 (PDT) (envelope-from riccardo@torrini.org) Received: (qmail 8332 invoked from network); 21 Apr 2001 12:13:21 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 21 Apr 2001 12:13:21 -0000 Received: (from riccardo@localhost) by torrini.org (8.11.3/8.11.3) id f3LCCxq23137 for freebsd-current@FreeBSD.ORG; Sat, 21 Apr 2001 14:12:59 +0200 (CEST) (envelope-from riccardo) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 21 Apr 2001 14:12:59 +0200 (CEST) From: Riccardo Torrini To: freebsd-current@FreeBSD.ORG Subject: nroff stopped working Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using -current from 3.0 w/out big problems over last years. But after last 3 make world man breaks: trying _ANY_ man give me an empty page but under .../man/man*/*.gz sources are good. Only formatted-compressed pages are wrong. Even the command: # gzip -cd /usr/share/man/man1/man.1.gz | nroff -man give me an empty page. Happens only to me? Can I send a PR? Something related to recent changes to nroff? Ciao++ Riccardo. PS: Any news about burncd? My PR are stalled? Last month I was unable only to close cd, now I am unable even to ask msinfo :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 5:26:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 6ABFF37B422; Sat, 21 Apr 2001 05:26:33 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id C965517D25; Sat, 21 Apr 2001 14:26:17 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.1/8.11.1) id f3LBIvm06780; Sat, 21 Apr 2001 13:18:57 +0200 (CEST) (envelope-from schweikh) Date: Sat, 21 Apr 2001 13:18:57 +0200 From: Jens Schweikhardt To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010421131857.B4574@schweikhardt.net> References: <20010420235419.B1276@schweikhardt.net> <200104202214.f3KMEAf06331@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104202214.f3KMEAf06331@mass.dis.org>; from msmith@freebsd.org on Fri, Apr 20, 2001 at 03:14:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 20, 2001 at 03:14:10PM -0700, Mike Smith wrote: # > # > Folks, # > # > although there was much rejoicing, I think there's no need for a # > new option to cp. Just use the toolbox, it's not too hard: # > # > (cat bigfilelist; echo destdir) | xargs cp # > # > Or even # > # > echo destdir >>bigfilelist # > xargs cp < bigfilelist # > # > should do the trick. # # No, it won't. Consider a list of files a, b, c, d. You create input to # xargs 'a b c d destdir', which it then splits into 'a b c' and 'd # destdir'. The first time cp is run, it will probably fail; the second # time only 'd' ends up where you expect it. You mean if bigfilelist list exceeds the -n limit of xargs (default 5000)? Yes, you'll be surprised then. It was a bit of POLA violation for me when I found xargs would by default use 5000 arg chunks and not all in one go. I'd rather get rid of kern.argmax and the limitations of the exec familiy. Yes, I'm dreaming :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 5:29:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 1860137B422 for ; Sat, 21 Apr 2001 05:29:55 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3LCTsB00582; Sat, 21 Apr 2001 05:29:54 -0700 (PDT) Date: Sat, 21 Apr 2001 05:29:54 -0700 (PDT) From: David Wolfskill Message-Id: <200104211229.f3LCTsB00582@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG, riccardo@torrini.org Subject: Re: nroff stopped working In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sat, 21 Apr 2001 14:12:59 +0200 (CEST) >From: Riccardo Torrini >I'm using -current from 3.0 w/out big problems over last years. >But after last 3 make world man breaks: trying _ANY_ man give >me an empty page but under .../man/man*/*.gz sources are good. >Only formatted-compressed pages are wrong. I ended up removing all of the pre-formatted man pages, and things worked after that. >PS: Any news about burncd? My PR are stalled? Last month I was >unable only to close cd, now I am unable even to ask msinfo :-( I've been using burncd (though under -STABLE; haven't tried it under -CURRENT (yet)) successfully.... Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 6: 6:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 5F6C437B422 for ; Sat, 21 Apr 2001 06:06:49 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LD7Cb78440; Sat, 21 Apr 2001 14:07:12 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LD64543456; Sat, 21 Apr 2001 14:06:04 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104211306.f3LD64543456@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Rodney W. Grimes" Cc: bsd@bsdhome.com (Brian Dean), schweikh@schweikhardt.net (Jens Schweikhardt), freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from "Rodney W. Grimes" of "Fri, 20 Apr 2001 21:00:56 PDT." <200104210400.VAA69212@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 14:06:04 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote: > > > > > > (cat bigfilelist; echo destdir) | xargs cp > > > > > > I like this version of the patch!! It's much much cleaner than > > > hacking up cp or xargs, it even follows the unix principle of > > > using simple tools and glueing them togeather to do bigger > > > jobs, is unix implementation independent, and is very clear > > > in what it does. > > > > It's clean, simple, and unfortunately, totally bogus. > > > > Try: > > > > echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo > > > > Now consider what would happen with the above suggested construct with > > a very long file list. > > bleck... try this for your sample: > $ (echo 1 2 3 4 5 6 7 8 9 | xargs -n 4) | while read x; do > > echo -n $x; echo " dst" > > done > 1 2 3 4 dst > 5 6 7 8 dst > 9 dst > $ > > > > > I don't see a problem with adding an option to cp to treat the first > > argument as the target instead of the last argument. It's a simple > > solution, the code change is simple, and it produces the exact desired > > result. What's the problem? > > It's yet another non-portable option. I hate to appear rude, but has anybody in this discussion actually used xargs for what it's meant to be used ? How do you do this in a script: cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. Before anyone starts writing scripts, consider that {} will be replaced by xargs with (roughly) ARG_MAX - 10 characters worth of the stuff coming off the pipe. If your combined arguments plus environment exceeds ARG_MAX execve(2) will give you E2BIG. > -- > Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 6:35:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from nova.sparklist.com (nova.sparklist.com [207.250.144.28]) by hub.freebsd.org (Postfix) with SMTP id 8D59537B423 for ; Sat, 21 Apr 2001 06:35:19 -0700 (PDT) (envelope-from sparklist-admin@nova.sparklist.com) Message-Id: X-sparklist-type: unsubscribed From: "SparkLIST.com" Reply-To: "SparkLIST.com" To: freebsd-current@freebsd.org Subject: Re: your unsubscribe request Date: Sat, 21 Apr 2001 08:37:21 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you requested, you have been unsubscribed from 'fwd-newswire'. --- Return-Path: Received: from nova.sparklist.com ([207.250.144.28]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 08:37:20 -0500 From: freebsd-current@freebsd.org () To: fwd-newswire-request Subject: # Mail sent to leave-fwd-newswire was converted to these commands: unsubscribe end # This is the text of the message that triggered the action: Return-Path: Received: from nova.sparklist.com ([207.250.144.28]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 08:37:20 -0500 From: freebsd-current@freebsd.org () To: leave-fwd-newswire@nova.sparklist.com Subject: your subscription request IP:203.55.242.168 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 7:24:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 4DEC337B43E for ; Sat, 21 Apr 2001 07:24:21 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14qyIy-0002vX-00; Sat, 21 Apr 2001 16:24:08 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA07655; Sat, 21 Apr 2001 16:23:01 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 7567; Sat Apr 21 16:22:48 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14qyHf-000OOy-00; Sat, 21 Apr 2001 16:22:47 +0200 To: Brian Somers Cc: "Rodney W. Grimes" , bsd@bsdhome.com (Brian Dean), schweikh@schweikhardt.net (Jens Schweikhardt), freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-reply-to: Your message of "Sat, 21 Apr 2001 14:06:04 +0100." <200104211306.f3LD64543456@hak.lan.Awfulhak.org> Date: Sat, 21 Apr 2001 16:22:44 +0200 Message-ID: <93802.987862964@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > How do you do this in a script: > > cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. for i in `find /path/to/source -type f`; do cp $i /path/to/dest/ done What's all the fuss about? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 7:33:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id AFD1C37B422 for ; Sat, 21 Apr 2001 07:33:30 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id QAA04049; Sat, 21 Apr 2001 16:33:29 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 16:33:29 +0200 (CEST) Message-Id: <200104211433.QAA04049@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010421131857.B4574@schweikhardt.net> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Jens Schweikhardt wrote: > You mean if bigfilelist list exceeds the -n limit of xargs (default 5000)? > Yes, you'll be surprised then. It was a bit of POLA violation for me when I > found xargs would by default use 5000 arg chunks and not all in one go. > I'd rather get rid of kern.argmax and the limitations of the exec familiy. > Yes, I'm dreaming :-) Certainly, it would cause a whole lot of other problems, the smallest of which would be that people would be starting to write non-portable scripts that rely on the feature that there is no ARG_MAX limit. By the way, the -i and -I options of xargs are specified in the SUSv2 standard, and I think it would certainly be a good thing to comply with that. At least it would be a whole lot better than hacking a non-standard option into cp which would solve the problem for one particular case only, while fixing xargs would solve the whole class of problems. Putting that option into cp seems rather GNUish to me, but not very UNIXish. :-) Just my 2 Euro cents. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 7:50:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 2551637B446 for ; Sat, 21 Apr 2001 07:50:17 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14qyiE-00033h-00 for freebsd-current@freebsd.org; Sat, 21 Apr 2001 16:50:14 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA10805 for ; Sat, 21 Apr 2001 16:50:13 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 10694; Sat Apr 21 16:49:25 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14qyhQ-000P1T-00 for freebsd-current@freebsd.org; Sat, 21 Apr 2001 16:49:24 +0200 To: freebsd-current@freebsd.org Subject: Post-FILE size change upgrade Date: Sat, 21 Apr 2001 16:49:24 +0200 Message-ID: <96190.987864564@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, After downgrading to RELENG_4 for a while to prove to my team mates that 3 months of pain were the result of hardware instability and not features of HEAD, I'm ready to get back on the wagon. I didn't follow the FILE size change debarcle, because I assumed that the problem would be resolved by the time I was ready for -CURRENT again. However, the entry for 20010211 in UPDATING suggests that I was wrong: 20010211: The size of FILE was changed. This breaks upgrading. If you must upgrade, be prepared for pain. It also breaks almost all binaries that you've compiled on -current. You are warned Is this still true? Please note that I'm not taking a dig at anyone. I've always seen source upgrades to HEAD as a luxury and firmly believe that binary upgrades are the "correct answer for technical support". Please don't use this innocent question to start a flame war. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 7:51:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id E6F3A37B43C for ; Sat, 21 Apr 2001 07:51:24 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id QAA04891; Sat, 21 Apr 2001 16:51:24 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 16:51:24 +0200 (CEST) Message-Id: <200104211451.QAA04891@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <93802.987862964@axl.fw.uunet.co.za> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Sheldon Hearn wrote: > On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > > How do you do this in a script: > > > > cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. > > for i in `find /path/to/source -type f`; do > cp $i /path/to/dest/ > done That can overflow your shell's command line limit (at the "for" command). True, our /bin/sh doesn't has such a limit, AFAIK, but there _are_ shells that do). Apart from that it is extremely inefficient, because it runs a "cp" for every single file. These are exactly the problems that xargs is supposed to solve. Actually I don't see any problem with Brian's approach (provided that the -i option exists, of course). xargs _does_ take the size of the environment into account, as well as the size of all arguments, and it still leaves much room (it only uses up to ARG_MAX - 2048 by default). Oh by the way, in this particular example it is probably a good idea to use cpio. This will even work with our xargs (which doesn't support -i yet): cd /topdir; find . -type f | cpio -dup /otherdir should do exactly that job. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 7:52:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx7.port.ru (mx7.port.ru [194.67.23.44]) by hub.freebsd.org (Postfix) with ESMTP id B616637B423 for ; Sat, 21 Apr 2001 07:52:43 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-40-154.bostma.adsl.bellatlantic.net ([141.154.40.154] helo=kan.dnsalias.net) by mx7.port.ru with esmtp (Exim 3.14 #17) id 14qykX-0004iB-00; Sat, 21 Apr 2001 18:52:37 +0400 Received: (from kan@localhost) by kan.dnsalias.net (8.11.3/8.11.3) id f3LEq6V00907; Sat, 21 Apr 2001 10:52:06 -0400 (EDT) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <93802.987862964@axl.fw.uunet.co.za> Date: Sat, 21 Apr 2001 10:52:05 -0400 (EDT) From: Alexander Kabaev To: Sheldon Hearn Subject: Re: cp -d dir patch for review (or 'xargs'?) Cc: freebsd-current@FreeBSD.ORG, (Jens Schweikhardt) , (Brian Dean) , "Rodney W. Grimes" , Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-2001 Sheldon Hearn wrote: > > > On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > >> How do you do this in a script: >> >> cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. > > for i in `find /path/to/source -type f`; do > cp $i /path/to/dest/ > done > > What's all the fuss about? > It looks like above construct will fail horribly if any of the files in /topdir have names with spaces in them. Think MP3 collections :) > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Alexander Kabaev Date: 21-Apr-2001 Time: 10:49:59 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8: 2:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 2C02E37B422 for ; Sat, 21 Apr 2001 08:02:54 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14qyuO-00038m-00 for freebsd-current@freebsd.org; Sat, 21 Apr 2001 17:02:48 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA12268 for ; Sat, 21 Apr 2001 17:02:47 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 12164; Sat Apr 21 17:02:03 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14qyte-0005Th-00 for freebsd-current@FreeBSD.ORG; Sat, 21 Apr 2001 17:02:02 +0200 To: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-reply-to: Your message of "Sat, 21 Apr 2001 16:51:24 +0200." <200104211451.QAA04891@lurza.secnetix.de> Date: Sat, 21 Apr 2001 17:02:02 +0200 Message-ID: <21060.987865322@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Apr 2001 16:51:24 +0200, Oliver Fromme wrote: > That can overflow your shell's command line limit (at the > "for" command). True, our /bin/sh doesn't has such a > limit, AFAIK, but there _are_ shells that do). That's actually my point. What's being proposed is a non-standard extension to work around a problem on a system that already doesn't have the problem. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8: 3:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 3FCCE37B423 for ; Sat, 21 Apr 2001 08:03:07 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14qyrK-00037C-00; Sat, 21 Apr 2001 16:59:38 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA11897; Sat, 21 Apr 2001 16:59:37 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 11796; Sat Apr 21 16:58:48 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14qyqW-00037j-00; Sat, 21 Apr 2001 16:58:48 +0200 To: Alexander Kabaev Cc: freebsd-current@freebsd.org, schweikh@schweikhardt.net (Jens Schweikhardt), bsd@bsdhome.com (Brian Dean), "Rodney W. Grimes" , Brian Somers Subject: Re: cp -d dir patch for review (or 'xargs'?) In-reply-to: Your message of "Sat, 21 Apr 2001 10:52:05 -0400." Date: Sat, 21 Apr 2001 16:58:48 +0200 Message-ID: <12006.987865128@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Apr 2001 10:52:05 -0400, Alexander Kabaev wrote: > > for i in `find /path/to/source -type f`; do > > cp $i /path/to/dest/ > > done > > > > What's all the fuss about? > > It looks like above construct will fail horribly if any of the files in /topdir > have names with spaces in them. Think MP3 collections :) Your comments have nothing to do with the issue at hand. Just wrap the first argument to cp in double-quotes, i.e. cp "$i" The point is, why bastardize tools to cope with areas beyond their focus and well within the focus of other tools? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8: 9: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id DE36837B422 for ; Sat, 21 Apr 2001 08:09:06 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3LF96d00884; Sat, 21 Apr 2001 08:09:06 -0700 (PDT) Date: Sat, 21 Apr 2001 08:09:06 -0700 (PDT) From: David Wolfskill Message-Id: <200104211509.f3LF96d00884@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG, sheldonh@uunet.co.za Subject: Re: Post-FILE size change upgrade In-Reply-To: <96190.987864564@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sat, 21 Apr 2001 16:49:24 +0200 >From: Sheldon Hearn >After downgrading to RELENG_4 for a while to prove to my team mates >that 3 months of pain were the result of hardware instability and not >features of HEAD, I'm ready to get back on the wagon. >I didn't follow the FILE size change debarcle, because I assumed that >the problem would be resolved by the time I was ready for -CURRENT >again. However, the entry for 20010211 in UPDATING suggests that I was >wrong: >20010211: > The size of FILE was changed. This breaks upgrading. If > you must upgrade, be prepared for pain. It also breaks almost > all binaries that you've compiled on -current. You are warned >Is this still true? Well, I acquired my laptop in early March, got 4.2 running on it, then cloned the / & /usr from that to another slice, and upgraded the clone to -CURRENT. I've been tracking both -STABLE & -CURRENT (daily) since. I do not recall encountering any problems attributable to the above. Indeed, the only undesirable side-effect of the procedure has been that there was some cruft left over from 4.x -- the old kernel & modules. Oh yeah; when I'm running -STABLE, I see that there is a populated /dev over on the -CURRENT side (that is hidden by the devfs mounted on /dev when I'm running -CURRENT). I suppose I could try wiping the cruft out; hasn't been enough of an issue to bother with, though. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8:11:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp5.port.ru (mx5.port.ru [194.67.23.40]) by hub.freebsd.org (Postfix) with ESMTP id 5450C37B423 for ; Sat, 21 Apr 2001 08:11:47 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-40-154.bostma.adsl.bellatlantic.net ([141.154.40.154] helo=kan.dnsalias.net) by smtp5.port.ru with esmtp (Exim 3.14 #3) id 14qz33-00077i-00; Sat, 21 Apr 2001 19:11:45 +0400 Received: (from kan@localhost) by kan.dnsalias.net (8.11.3/8.11.3) id f3LFBgH01066; Sat, 21 Apr 2001 11:11:42 -0400 (EDT) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <12006.987865128@axl.fw.uunet.co.za> Date: Sat, 21 Apr 2001 11:11:42 -0400 (EDT) From: Alexander Kabaev To: Sheldon Hearn Subject: Re: cp -d dir patch for review (or 'xargs'?) Cc: Brian Somers , "Rodney W. Grimes" , (Brian Dean) , (Jens Schweikhardt) , freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Your comments have nothing to do with the issue at hand. Just wrap the > first argument to cp in double-quotes, i.e. > > cp "$i" > > The point is, why bastardize tools to cope with areas beyond their > focus and well within the focus of other tools? > > Ciao, > Sheldon. Sorry for butting in. Adding new non-portable functionality to solve the problem which could be adequitely taken care of using existing and well known techniquies is not appropriate, I completely agree with you on that. ---------------------------------- E-Mail: Alexander Kabaev Date: 21-Apr-2001 Time: 11:08:13 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8:27: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 519DD37B423 for ; Sat, 21 Apr 2001 08:27:05 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id RAA06452; Sat, 21 Apr 2001 17:27:04 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 17:27:04 +0200 (CEST) Message-Id: <200104211527.RAA06452@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <21060.987865322@axl.fw.uunet.co.za> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Sheldon Hearn wrote: > On Sat, 21 Apr 2001 16:51:24 +0200, Oliver Fromme wrote: > > That can overflow your shell's command line limit (at the > > "for" command). True, our /bin/sh doesn't has such a > > limit, AFAIK, but there _are_ shells that do). > > That's actually my point. What's being proposed is a non-standard > extension to work around a problem on a system that already doesn't have > the problem. Maybe I didn't make myself clear enough. We _do_ have a problem. Not all users use /bin/sh. Scripts needn't be written in /bin/sh, and xargs can be used interactively, too (I use it a lot). Just because _our_ xargs works fine with _our_ /bin/sh doesn't mean there is no problem. And then there's the gross efficiency problem. Try these alternatives and compare how long they take: for i in `find /usr/ports -type f`; do cat $i >/dev/null done find /usr/ports -type f | xargs cat >/dev/null The latter is a hell of a lot faster. (The example uses "cat" just because it works with xargs.) By the way, the first (inefficient) approach could be rewritten like this: find /usr/ports -type f | while read i; do cat $i >/dev/null done This avoid the potential line limit problem, but of course it's just as inefficient. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8:35:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id B553537B42C for ; Sat, 21 Apr 2001 08:35:29 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14qzPz-0003KN-00 for freebsd-current@freebsd.org; Sat, 21 Apr 2001 17:35:27 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA16157 for ; Sat, 21 Apr 2001 17:35:25 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 16057; Sat Apr 21 17:34:31 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14qzP5-000Hcc-00 for freebsd-current@FreeBSD.ORG; Sat, 21 Apr 2001 17:34:31 +0200 To: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-reply-to: Your message of "Sat, 21 Apr 2001 17:27:04 +0200." <200104211527.RAA06452@lurza.secnetix.de> Date: Sat, 21 Apr 2001 17:34:31 +0200 Message-ID: <67741.987867271@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Apr 2001 17:27:04 +0200, Oliver Fromme wrote: > Not all users use /bin/sh. Scripts needn't be written > in /bin/sh, and xargs can be used interactively, too (I > use it a lot). Just because _our_ xargs works fine with > _our_ /bin/sh doesn't mean there is no problem. So we have two problems: 1) Calling cp(1) repetitively is inefficient. 2) The argument list is too big for cp(1). Extending cp(1) will not solve (2). Extending xargs(1) will solve both. So why is an extension to cp(1) being proposed? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 8:59:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from nova.sparklist.com (nova.sparklist.com [207.250.144.28]) by hub.freebsd.org (Postfix) with SMTP id D852C37B42C for ; Sat, 21 Apr 2001 08:59:38 -0700 (PDT) (envelope-from sparklist-admin@nova.sparklist.com) Message-Id: X-sparklist-type: unsubscribed From: "SparkLIST.com" Reply-To: "SparkLIST.com" To: freebsd-current@freebsd.org Subject: Re: your unsubscribe request Date: Sat, 21 Apr 2001 11:01:41 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you requested, you have been unsubscribed from 'fwd-newswire'. --- Return-Path: Received: from mailhost.sparknet.net ([207.67.22.123]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 11:01:40 -0500 Received: from don-oakes.sparklist.com (dhcp-client-26.sparklist.com [207.250.191.151]) by mailhost.sparknet.net (8.10.1/8.10.1) with ESMTP id f3LG3pI03813 for ; Sat, 21 Apr 2001 11:03:51 -0500 Message-Id: <4.3.1.2.20010421105600.02635c40@207.67.22.123> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 21 Apr 2001 10:56:03 -0500 To: fwd-newswire-request From: admin Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed # Mail sent to leave-fwd-newswire-2059525t was converted to these commands: unsubscribe fwd-newswire freebsd-current@freebsd.org confirm end # This is the text of the message that triggered the action: Return-Path: Received: from mailhost.sparknet.net ([207.67.22.123]) by nova.sparklist.com with SMTP (SparkLIST.com WIN32 version 4.1); Sat, 21 Apr 2001 11:01:40 -0500 Received: from don-oakes.sparklist.com (dhcp-client-26.sparklist.com [207.250.191.151]) by mailhost.sparknet.net (8.10.1/8.10.1) with ESMTP id f3LG3pI03813 for ; Sat, 21 Apr 2001 11:03:51 -0500 Message-Id: <4.3.1.2.20010421105600.02635c40@207.67.22.123> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 21 Apr 2001 10:56:03 -0500 To: leave-fwd-newswire-2059525T@nova.sparklist.com From: admin Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 10:21:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id C836E37B423 for ; Sat, 21 Apr 2001 10:21:29 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id TAA11754; Sat, 21 Apr 2001 19:21:28 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 19:21:28 +0200 (CEST) Message-Id: <200104211721.TAA11754@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: /bin/df set-gid operator X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Hi, This is probably the wrong list, but I have no idea where else to ask, and -current is also affected, so ... I'm wondering why /bin/df is set-gid to the operator group by default. I have tried to remove the s bit, and it is still working fine. Looking at the source code didn't give me a clue either. -1- Am I missing something? What? -2- If I'm not missing anything, then shouldn't the BINMODE line be removed from src/bin/df/Makefile? -3- Shall I send-pr a patch? :-) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 10:28:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0D6DC37B43C; Sat, 21 Apr 2001 10:28:49 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f3LHSlK63013; Sat, 21 Apr 2001 10:28:47 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f3LHQj264230; Sat, 21 Apr 2001 10:26:45 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000901c0ca1d$9341cfc0$931576d8@inethouston.net> Date: Sat, 21 Apr 2001 10:26:45 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: "David W. Chapman Jr." , imp@FreeBSD.org Subject: Re: kernel core Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-01 David W. Chapman Jr. wrote: > I just tried to do an installkernel on a new kernel I built and I got the > same error except the last line changed to > > stopped at ffs_dirpref+0x210 movzbl 0(%ECX,%EAX,1),%EAX > > Do I have any hope at recovering from this or should I start again with 4 > and upgrade to -current. I'm assuming is a problem with the kernel and > without being able to update the kernel and install a new one, I don't think > I can fix it. You need to rebuild fsck and install it and fsck your filesystems. This is the dirpref changes biting you. Warner, we probably need an entry in UPDATING for the dirpref changes that warn people to build and install a new fsck before booting a dirpref kernel. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 10:38:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id E5F8637B424 for ; Sat, 21 Apr 2001 10:38:15 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-194-8-209-248.netcologne.de [194.8.209.248]) by mr200.netcologne.de (Mirapoint) with ESMTP id AEC57482; Sat, 21 Apr 2001 19:38:14 +0200 (CEST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.3) with ESMTP id f3LHc5m70538 for ; Sat, 21 Apr 2001 19:38:05 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Sat, 21 Apr 2001 19:38:05 +0200 (CEST) From: Paul Herman To: Subject: Re: /bin/df set-gid operator In-Reply-To: <200104211721.TAA11754@lurza.secnetix.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 Sat, 21 Apr 2001, Oliver Fromme wrote: > I'm wondering why /bin/df is set-gid to the operator group > by default. It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or whatever) as user nobody with chmod 555 /bin/df. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 10:45:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 79ACF37B422 for ; Sat, 21 Apr 2001 10:45:14 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id TAA13326; Sat, 21 Apr 2001 19:45:13 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 19:45:13 +0200 (CEST) Message-Id: <200104211745.TAA13326@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: /bin/df set-gid operator In-Reply-To: X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Paul Herman wrote: > On Sat, 21 Apr 2001, Oliver Fromme wrote: > > I'm wondering why /bin/df is set-gid to the operator group > > by default. > > It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or > whatever) as user nobody with chmod 555 /bin/df. Ah, thanks for clueing me. :-) I didn't know that unprivileged users are supposed to be allowed to use df on non-mounted filesystems. I think I'll keep it at mode 555 on my machines. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 11: 4:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 8147737B423 for ; Sat, 21 Apr 2001 11:04:53 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-73-41.netcologne.de [213.168.73.41]) by mr200.netcologne.de (Mirapoint) with ESMTP id AEC59575; Sat, 21 Apr 2001 20:04:50 +0200 (CEST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.3) with ESMTP id f3LI4hg83135 for ; Sat, 21 Apr 2001 20:04:43 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Sat, 21 Apr 2001 20:04:43 +0200 (CEST) From: Paul Herman To: Subject: Re: /bin/df set-gid operator In-Reply-To: <200104211745.TAA13326@lurza.secnetix.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 Sat, 21 Apr 2001, Oliver Fromme wrote: > Paul Herman wrote: > > On Sat, 21 Apr 2001, Oliver Fromme wrote: > > > I'm wondering why /bin/df is set-gid to the operator group > > > by default. > > > > It's to df filesystems that aren't mounted. Try "df /dev/ad0s1a" (or > > whatever) as user nobody with chmod 555 /bin/df. > > Ah, thanks for clueing me. :-) > I didn't know that unprivileged users are supposed to be > allowed to use df on non-mounted filesystems. > > I think I'll keep it at mode 555 on my machines. This brings up a slightly related question: Now that "cooked" block devices have been abolished, wouldn't it be a good idea to get rid of the quick mount(2)/umount(2) of /tmp/df.XXXXXX to stat the file system? Something like the following patch. Not that it should ever get called anyway... -Paul. Index: df.c =================================================================== RCS file: /home/ncvs/src/bin/df/df.c,v retrieving revision 1.23.2.1 diff -u -r1.23.2.1 df.c --- df.c 2000/06/13 03:19:40 1.23.2.1 +++ df.c 2001/04/21 18:02:18 @@ -208,40 +208,6 @@ } else if ((stbuf.st_mode & S_IFMT) == S_IFCHR) { rv = ufs_df(*argv, maxwidth) || rv; continue; - } else if ((stbuf.st_mode & S_IFMT) == S_IFBLK) { - if ((mntpt = getmntpt(*argv)) == 0) { - mdev.fspec = *argv; - mntpath = strdup("/tmp/df.XXXXXX"); - if (mntpath == NULL) { - warn("strdup failed"); - rv = 1; - continue; - } - mntpt = mkdtemp(mntpath); - if (mntpt == NULL) { - warn("mkdtemp(\"%s\") failed", mntpath); - rv = 1; - free(mntpath); - continue; - } - if (mount("ufs", mntpt, MNT_RDONLY, - &mdev) != 0) { - rv = ufs_df(*argv, maxwidth) || rv; - (void)rmdir(mntpt); - free(mntpath); - continue; - } else if (statfs(mntpt, &statfsbuf) == 0) { - statfsbuf.f_mntonname[0] = '\0'; - prtstat(&statfsbuf, maxwidth); - } else { - warn("%s", *argv); - rv = 1; - } - (void)unmount(mntpt, 0); - (void)rmdir(mntpt); - free(mntpath); - continue; - } } else mntpt = *argv; /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 11: 7: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 5CEDD37B422 for ; Sat, 21 Apr 2001 11:07:03 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3LI6oM60236; Sat, 21 Apr 2001 11:06:50 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: freebsd-current@FreeBSD.ORG, olli@secnetix.de Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104211527.RAA06452@lurza.secnetix.de> References: <21060.987865322@axl.fw.uunet.co.za> <200104211527.RAA06452@lurza.secnetix.de> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010421110650E.jkh@osd.bsdi.com> Date: Sat, 21 Apr 2001 11:06:50 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Oliver Fromme Subject: Re: cp -d dir patch for review (or 'xargs'?) Date: Sat, 21 Apr 2001 17:27:04 +0200 (CEST) > Not all users use /bin/sh. Scripts needn't be written > in /bin/sh ... Actually, just to jump in and correct this, scripts *should* be written in /bin/sh. That's a defacto Unix standard when it comes to writing shell scripts, just for uniformities sake, and even if you use tcsh or zsh as your personal shell one is always encouraged to write in straight POSIX-conformant /bin/sh for portable scripts. If one also needs to walk entirely outside the painted lines there then that's a good indication that maybe it should be written in perl. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 11:28:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id A174337B422 for ; Sat, 21 Apr 2001 11:28:22 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-88-15.netcologne.de [213.168.88.15]) by mr200.netcologne.de (Mirapoint) with ESMTP id AEC61181; Sat, 21 Apr 2001 20:27:57 +0200 (CEST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.3) with ESMTP id f3LIRpj97450 for ; Sat, 21 Apr 2001 20:27:51 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Sat, 21 Apr 2001 20:27:51 +0200 (CEST) From: Paul Herman To: Subject: Re: /bin/df set-gid operator 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 Sorry to follow up on my own mail... On Sat, 21 Apr 2001, Paul Herman wrote: > This brings up a slightly related question: Now that block > devices have been abolished, wouldn't it be a good idea to get rid > of the quick mount(2)/umount(2) of /tmp/df.XXXXXX to stat the file > system? I see now that block type devices still pop up everywhere in the VFS system, so I'll just forget this and leave it up to the team that may someday totaly remove block device support from the kernel -- if that ever will happen. :-) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 11:35:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6737B43C; Sat, 21 Apr 2001 11:35:17 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.2) with ESMTP id f3LIdGC01045; Sat, 21 Apr 2001 11:39:18 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104211839.f3LIdGC01045@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: "David W. Chapman Jr." , imp@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: kernel core In-reply-to: Your message of "Sat, 21 Apr 2001 10:26:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 11:39:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You need to rebuild fsck and install it and fsck your filesystems. This is the > dirpref changes biting you. Warner, we probably need an entry in UPDATING for > the dirpref changes that warn people to build and install a new fsck before > booting a dirpref kernel. Er. This really isn't very good; I can see all sorts of opportunities here for disk migration between -stable and -current systems causing massive headaches. I assume there's a better fix in the works, so that a "dirpref-touched" disk can be moved back to a pre-dirpref system? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 12: 0: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 2056F37B43C for ; Sat, 21 Apr 2001 11:59:52 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LIvrb79728; Sat, 21 Apr 2001 19:57:53 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LIug547373; Sat, 21 Apr 2001 19:56:42 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104211856.f3LIug547373@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Sheldon Hearn Cc: Brian Somers , "Rodney W. Grimes" , bsd@bsdhome.com (Brian Dean), schweikh@schweikhardt.net (Jens Schweikhardt), freebsd-current@freebsd.org, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Sheldon Hearn of "Sat, 21 Apr 2001 16:22:44 +0200." <93802.987862964@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 19:56:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > > > How do you do this in a script: > > > > cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. > > for i in `find /path/to/source -type f`; do > cp $i /path/to/dest/ > done > > What's all the fuss about? Have you tried that for values of /path/to/source with lots of files ? Something like find blah | while read i; do cp $i /dest/.; done is better, but it runs cp too many times. > Ciao, > Sheldon. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 12: 6:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id B058F37B424 for ; Sat, 21 Apr 2001 12:06:36 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LJ5hb79757; Sat, 21 Apr 2001 20:05:43 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LJ4V547486; Sat, 21 Apr 2001 20:04:32 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104211904.f3LJ4V547486@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alexander Kabaev Cc: Sheldon Hearn , Brian Somers , "Rodney W. Grimes" , bsd@bsdhome.com (Brian Dean), schweikh@schweikhardt.net (Jens Schweikhardt), freebsd-current@freebsd.org, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Alexander Kabaev of "Sat, 21 Apr 2001 11:11:42 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 20:04:31 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry for butting in. Adding new non-portable functionality to solve the problem > which could be adequitely taken care of using existing and well known > techniquies is not appropriate, I completely agree with you on that. And I'm still waiting to see those well known techniques. > ---------------------------------- > E-Mail: Alexander Kabaev > Date: 21-Apr-2001 > Time: 11:08:13 > ---------------------------------- -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 12: 7:29 2001 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 8E73937B422 for ; Sat, 21 Apr 2001 12:07:23 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id FAA05064; Sun, 22 Apr 2001 05:07:14 +1000 Date: Sun, 22 Apr 2001 05:06:16 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Paul Herman Cc: freebsd-current@FreeBSD.ORG Subject: Re: /bin/df set-gid operator 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, 21 Apr 2001, Paul Herman wrote: > This brings up a slightly related question: Now that "cooked" block > devices have been abolished, wouldn't it be a good idea to get rid of > the quick mount(2)/umount(2) of /tmp/df.XXXXXX to stat the file > system? Something like the following patch. No. This code is just unreachable because it still hasn't be changed to mount "raw" block devices. Note that in 4.4BSD, the mount(2)/unmount(2) code works without df being setgid operator provided group operator can read the devices, since mount(2) doesn't require superuser privilege in 4.4BSD. In FreeBSD, mount privilege is controlled by the vfs.usermount sysctl (default: off), so df must still be setgid operator to work on devices. The mount() method is better because can work on work on all types of filesystems that the kernel understands, while ufs_df() only works for ufs. Untested fixes: Index: df.c =================================================================== RCS file: /home/ncvs/src/bin/df/df.c,v retrieving revision 1.24 diff -c -2 -r1.24 df.c *** df.c 2000/06/03 20:17:39 1.24 --- df.c 2001/04/21 18:52:52 *************** *** 108,112 **** void usage __P((void)); ! int aflag = 0, hflag, iflag, nflag; struct ufs_args mdev; --- 108,112 ---- void usage __P((void)); ! int aflag, hflag, iflag, nflag; struct ufs_args mdev; *************** *** 120,125 **** long mntsize; int ch, err, i, maxwidth, rv, width; ! char *mntpt, *mntpath, **vfslist; vfslist = NULL; while ((ch = getopt(argc, argv, "abgHhikmnPt:")) != -1) --- 120,126 ---- long mntsize; int ch, err, i, maxwidth, rv, width; ! char *fstype, *mntpath, *mntpt, **vfslist; + fstype = "ufs"; vfslist = NULL; while ((ch = getopt(argc, argv, "abgHhikmnPt:")) != -1) *************** *** 163,166 **** --- 164,168 ---- if (vfslist != NULL) errx(1, "only one -t option may be specified."); + fstype = optarg; vfslist = makevfslist(optarg); break; *************** *** 206,213 **** continue; } ! } else if ((stbuf.st_mode & S_IFMT) == S_IFCHR) { ! rv = ufs_df(*argv, maxwidth) || rv; ! continue; ! } else if ((stbuf.st_mode & S_IFMT) == S_IFBLK) { if ((mntpt = getmntpt(*argv)) == 0) { mdev.fspec = *argv; --- 208,212 ---- continue; } ! } else if (S_ISBLK(stbuf.st_mode) || S_ISCHR(stbuf.st_mode)) { if ((mntpt = getmntpt(*argv)) == 0) { mdev.fspec = *argv; *************** *** 225,229 **** continue; } ! if (mount("ufs", mntpt, MNT_RDONLY, &mdev) != 0) { rv = ufs_df(*argv, maxwidth) || rv; --- 224,228 ---- continue; } ! if (mount(fstype, mntpt, MNT_RDONLY, &mdev) != 0) { rv = ufs_df(*argv, maxwidth) || rv; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 13: 0: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 1059837B43C for ; Sat, 21 Apr 2001 12:59:58 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id VAA19256; Sat, 21 Apr 2001 21:59:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 21:59:57 +0200 (CEST) Message-Id: <200104211959.VAA19256@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010421110650E.jkh@osd.bsdi.com> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Jordan Hubbard wrote: > From: Oliver Fromme > > Not all users use /bin/sh. Scripts needn't be written > > in /bin/sh ... > > Actually, just to jump in and correct this, scripts *should* be > written in /bin/sh. It depends. I often happen to write zsh scripts, but only if I'm sure that they don't really have to be portable, and that I am the only one who will ever use them. When I was young, I also wrote a few tcsh scripts (*ouch*), but I discontinued doing that long ago. :-) I agree with you 100% that portable scripts should use /bin/sh and nothing else. And to come back on topic: Portable scripts also should _not_ assume that there are no limits on the length of shell commands. On the other hand, portable scripts can legitimately assume that xargs supports -i and -I, which ours doesn't. Regards Oliver PS: FWIW, I also write a lot of awk scripts, which is my favourite scripting language, but this is really getting off-topic ... -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 13: 7:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 767AC37B424 for ; Sat, 21 Apr 2001 13:07:36 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3LK7JM60695; Sat, 21 Apr 2001 13:07:19 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: freebsd-current@FreeBSD.ORG, olli@secnetix.de Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104211959.VAA19256@lurza.secnetix.de> References: <20010421110650E.jkh@osd.bsdi.com> <200104211959.VAA19256@lurza.secnetix.de> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010421130719H.jkh@osd.bsdi.com> Date: Sat, 21 Apr 2001 13:07:19 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And to come back on topic: Portable scripts also should > _not_ assume that there are no limits on the length of > shell commands. On the other hand, portable scripts can > legitimately assume that xargs supports -i and -I, which > ours doesn't. Agreed on both counts. I guess we should fix that. > PS: FWIW, I also write a lot of awk scripts, which is my > favourite scripting language, but this is really getting > off-topic ... So do I, and you're right. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 13:18:47 2001 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 805E937B424 for ; Sat, 21 Apr 2001 13:18:44 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA06924; Sun, 22 Apr 2001 06:16:10 +1000 Date: Sun, 22 Apr 2001 06:15:07 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Brian Somers Cc: Sheldon Hearn , "Rodney W. Grimes" , Brian Dean , Jens Schweikhardt , freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104211856.f3LIug547373@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Apr 2001, Brian Somers wrote: > > On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > > > > > How do you do this in a script: > > > > > > cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. > > > > for i in `find /path/to/source -type f`; do > > cp $i /path/to/dest/ > > done > > > > What's all the fuss about? > > Have you tried that for values of /path/to/source with lots of files ? > Something like > > find blah | while read i; do cp $i /dest/.; done > > is better, but it runs cp too many times. cp is a bad example, since it usually does physical i/o which is much slower than execve() of a program that is probably cached, especially when the program is small and not dynamically linked. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 13:20: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 5F54637B423 for ; Sat, 21 Apr 2001 13:19:58 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id D12FD3E09; Sat, 21 Apr 2001 13:19:57 -0700 (PDT) To: Jordan Hubbard Cc: freebsd-current@FreeBSD.ORG, olli@secnetix.de Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010421130719H.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on "Sat, 21 Apr 2001 13:07:19 -0700" Date: Sat, 21 Apr 2001 13:19:57 -0700 From: Dima Dorfman Message-Id: <20010421201957.D12FD3E09@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard writes: > > And to come back on topic: Portable scripts also should > > _not_ assume that there are no limits on the length of > > shell commands. On the other hand, portable scripts can > > legitimately assume that xargs supports -i and -I, which > > ours doesn't. > > Agreed on both counts. I guess we should fix that. I don't have a copy of SuSv2 or anything else that defines -I and -i, but from what I can gather, -i is the same as "-I {}" and -I allows things like this: dima@spike% ./xargs -I [] echo CMD LINE [] ARGS < test CMD LINE this is the contents of the test file ARGS dima@spike% ./xargs -I [] echo CMD [] LINE ARGS < test CMD this is the contents of the test file LINE ARGS dima@spike% ./xargs -I [] echo [] CMD LINE ARGS < test this is the contents of the test file CMD LINE ARGS Does that mean everyone is blind and missed my arrogant cross-post of the amazingly short patch to do this, or are we just interested in discussing it and not testing the implementation? ;-) FWIW, I'm not sure the patch is entirely correct; xargs' processing of this stuff looks like black magic. It works, but I'm not sure if I failed to cater to some other weird assumptions it makes. This is why it'd help if someone would at least look at it. Thanks, Dima Dorfman dima@unixfreak.org Index: xargs.c =================================================================== RCS file: /st/src/FreeBSD/src/usr.bin/xargs/xargs.c,v retrieving revision 1.9 diff -u -r1.9 xargs.c --- xargs.c 1999/08/28 01:07:50 1.9 +++ xargs.c 2001/04/21 20:15:27 @@ -73,6 +73,8 @@ int cnt, indouble, insingle, nargs, nflag, nline, xflag, wasquoted; char **av, *argp, **ep = env; long arg_max; + int apargs = 0; + char **avv, *replstr = NULL; /* * POSIX.2 limits the exec line length to ARG_MAX - 2K. Running that @@ -96,8 +98,14 @@ nline -= strlen(*ep++) + 1 + sizeof(*ep); } nflag = xflag = wasquoted = 0; - while ((ch = getopt(argc, argv, "0n:s:tx")) != -1) + while ((ch = getopt(argc, argv, "0I:in:s:tx")) != -1) switch(ch) { + case 'I': + replstr = optarg; + break; + case 'i': + replstr = "{}"; + break; case 'n': nflag = 1; if ((nargs = atoi(optarg)) <= 0) @@ -144,6 +152,13 @@ else { cnt = 0; do { + if (replstr && strcmp(*argv, replstr) == 0) { + apargs = 1; + *argv++; + for (avv = argv; *avv; *avv++) + cnt += strlen(*avv) + 1; + break; + } cnt += strlen(*bxp++ = *argv) + 1; } while (*++argv); } @@ -211,6 +226,8 @@ if (xp == exp || p > ebp || ch == EOF) { if (xflag && xp != exp && p > ebp) errx(1, "insufficient space for arguments"); + for (avv = argv; apargs && *avv; *avv++) + strlen(*xp++ = *avv) + 1; *xp = NULL; run(av); if (ch == EOF) @@ -253,6 +270,8 @@ if (xflag) errx(1, "insufficient space for arguments"); + for (avv = argv; apargs && *avv; *avv++) + strlen(*xp++ = *avv) + 1; *xp = NULL; run(av); xp = bxp; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 13:24:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdhome.dyndns.org (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id A0CE637B422 for ; Sat, 21 Apr 2001 13:24:38 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by bsdhome.dyndns.org (8.11.3/8.11.3) with ESMTP id f3LKObJ46262; Sat, 21 Apr 2001 16:24:37 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: (from bsd@localhost) by vger.bsdhome.com (8.11.3/8.11.1) id f3LKOas57031; Sat, 21 Apr 2001 16:24:36 -0400 (EDT) (envelope-from bsd) Date: Sat, 21 Apr 2001 16:24:36 -0400 From: Brian Dean To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010421162436.A56976@vger.bsdhome.com> References: <200104211527.RAA06452@lurza.secnetix.de> <67741.987867271@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <67741.987867271@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Sat, Apr 21, 2001 at 05:34:31PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 21, 2001 at 05:34:31PM +0200, Sheldon Hearn wrote: > So we have two problems: > > 1) Calling cp(1) repetitively is inefficient. > > 2) The argument list is too big for cp(1). > > Extending cp(1) will not solve (2). Extending xargs(1) will solve both. > So why is an extension to cp(1) being proposed? But extending cp does solve the problem. The proposal was to make % cp -d target src1 src2 ... srcN Be equivalent to; % cp src1 src2 ... srcN target This makes cp work with xargs; % cat ReallyBigListOfFiles | xargs cp -d target -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14: 1:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 2D83637B424 for ; Sat, 21 Apr 2001 14:01:19 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id XAA22211; Sat, 21 Apr 2001 23:01:18 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 23:01:18 +0200 (CEST) Message-Id: <200104212101.XAA22211@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010421162436.A56976@vger.bsdhome.com> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Brian Dean wrote: > But extending cp does solve the problem. Only for cp. It wouldn't solve the problem for mv, ln and a bunch of other tools. Fixing it at _one_ place in xargs would solve all of that without touching a dozen tools. > [...] > This makes cp work with xargs; > > % cat ReallyBigListOfFiles | xargs cp -d target That's actually a bad example anyway, because you would use cpio in that case, not xargs|cp. It's also a bad example for using cat, but that's a different story. :-) cpio -dup target < ReallyBigListOfFiles Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14: 9:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 7D93137B42C for ; Sat, 21 Apr 2001 14:09:29 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLAkb80222; Sat, 21 Apr 2001 22:10:46 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LL9X549119; Sat, 21 Apr 2001 22:09:33 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104212109.f3LL9X549119@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Sheldon Hearn of "Sat, 21 Apr 2001 17:34:31 +0200." <67741.987867271@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 22:09:33 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So we have two problems: > > 1) Calling cp(1) repetitively is inefficient. > > 2) The argument list is too big for cp(1). > > Extending cp(1) will not solve (2). Extending xargs(1) will solve both. > So why is an extension to cp(1) being proposed? I wasn't proposing that cp should be changed - I don't think it should. I'm just guilty of using a stale subject line :-/ > Ciao, > Sheldon. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14:12:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 8966237B42C for ; Sat, 21 Apr 2001 14:12:21 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id XAA22737; Sat, 21 Apr 2001 23:12:20 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 21 Apr 2001 23:12:20 +0200 (CEST) Message-Id: <200104212112.XAA22737@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <20010421201957.D12FD3E09@bazooka.unixfreak.org> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) 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 Dima Dorfman wrote: > I don't have a copy of SuSv2 or anything else that defines -I and -i, http://www.secnetix.de/~olli/susv2/xcu/xargs.html > but from what I can gather, -i is the same as "-I {}" and -I allows > things like this: Not exactly. The difference is that the option-argument to -i is optional and -- if present -- has to follow without whitespace after the -i. This is a violation of the common utility syntax guidelines, but has been adopted by SUSv2 because it was widely implemented. So ``-i'' is the same as ``-I {}'', and ``-i[]'' (no space!) is the same as ``-I []''. Unfortunately, when you use -i or -I, then each line from stdin is used as a signle argument, and the utility is invoked once for every line, unless I misunderstand what SUSv2 is saying. :-( $ cat test foo bar baz bla $ xargs -i echo XXX '{}' YYY < test XXX foo bar YYY XXX baz bla YYY $ > Does that mean everyone is blind and missed my arrogant cross-post of > the amazingly short patch to do this, or are we just interested in > discussing it and not testing the implementation? ;-) I must have missed it, and I think it's at least a good start. :-) The patch looks good. At leat it would solve the problem which this thread is about, although I think it doesn't comply with SUSv2. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14:17:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 6B87037B422 for ; Sat, 21 Apr 2001 14:17:20 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLHUb80253; Sat, 21 Apr 2001 22:17:31 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLGI549254; Sat, 21 Apr 2001 22:16:18 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104212116.f3LLGI549254@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Dima Dorfman Cc: Jordan Hubbard , freebsd-current@FreeBSD.ORG, olli@secnetix.de, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Dima Dorfman of "Sat, 21 Apr 2001 13:19:57 PDT." <20010421201957.D12FD3E09@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 22:16:18 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I looked at your patches and immediately thought ``these patches can't be right'' as I was expecting it to deal with things such as xargs -I [] echo args are [], duplicated are [] I'm also dubious about the patches working for large volumes on standard input. At this point I scrapped the email I was composing 'cos I didn't have time to look into it further :-/ I think it's important to test any patches with a large number of large path names as input - so that ARG_MAX is reached before the 5000 argument limit and we can see that we don't end up getting E2BIG because of an accidental overflow/miscalculation. Sorry I don't have more time to spend on it :-/ > I don't have a copy of SuSv2 or anything else that defines -I and -i, > but from what I can gather, -i is the same as "-I {}" and -I allows > things like this: > > dima@spike% ./xargs -I [] echo CMD LINE [] ARGS < test > CMD LINE this is the contents of the test file ARGS > > dima@spike% ./xargs -I [] echo CMD [] LINE ARGS < test > CMD this is the contents of the test file LINE ARGS > > dima@spike% ./xargs -I [] echo [] CMD LINE ARGS < test > this is the contents of the test file CMD LINE ARGS > > Does that mean everyone is blind and missed my arrogant cross-post of > the amazingly short patch to do this, or are we just interested in > discussing it and not testing the implementation? ;-) > > FWIW, I'm not sure the patch is entirely correct; xargs' processing of > this stuff looks like black magic. It works, but I'm not sure if I > failed to cater to some other weird assumptions it makes. This is why > it'd help if someone would at least look at it. > > Thanks, > > Dima Dorfman > dima@unixfreak.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14:18:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 0E9B137B422 for ; Sat, 21 Apr 2001 14:18:27 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLJkb80257 for ; Sat, 21 Apr 2001 22:19:46 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLIY549287; Sat, 21 Apr 2001 22:18:34 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104212118.f3LLIY549287@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-current@FreeBSD.ORG Cc: brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Oliver Fromme of "Sat, 21 Apr 2001 16:33:29 +0200." <200104211433.QAA04049@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 21 Apr 2001 22:18:34 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Putting that option into cp seems rather GNUish to me, but > not very UNIXish. :-) Yes. I think most people agree that changing cp is not good. > Just my 2 Euro cents. > = > Regards > Oliver > = > -- = > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 M=FCnchen > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > = > "All that we see or seem is just a dream within a dream" (E. A. Poe) -- = Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 14:32:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id D033237B424 for ; Sat, 21 Apr 2001 14:32:28 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLXeb80310 for ; Sat, 21 Apr 2001 22:33:40 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LLWS549499; Sat, 21 Apr 2001 22:32:28 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104212132.f3LLWS549499@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-current@FreeBSD.ORG Cc: brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Oliver Fromme of "Sat, 21 Apr 2001 23:12:20 +0200." <200104212112.XAA22737@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 21 Apr 2001 22:32:28 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dima Dorfman wrote: > > I don't have a copy of SuSv2 or anything else that defines -I and -i= , > = > http://www.secnetix.de/~olli/susv2/xcu/xargs.html > = > > but from what I can gather, -i is the same as "-I {}" and -I allows > > things like this: > = > Not exactly. The difference is that the option-argument to > -i is optional and -- if present -- has to follow without > whitespace after the -i. This is a violation of the common > utility syntax guidelines, but has been adopted by SUSv2 > because it was widely implemented. > = > So ``-i'' is the same as ``-I {}'', and ``-i[]'' (no space!) > is the same as ``-I []''. I don't think we should adopt these semantics. I'm coming around to = Dima's -Y option - which must have an argument. > Unfortunately, when you use -i or -I, then each line from > stdin is used as a signle argument, and the utility is > invoked once for every line, unless I misunderstand what > SUSv2 is saying. :-( I guess that settles it then. This is a dumb restriction and doesn't = seem to fit in very well with how xargs works. Again, Dima's idea is = IMHO superior. But as I said in my other follow-up, I'm not convinced that the patch = deals with ARG_MAX overflows properly (I may be wrong though). -- = Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 15: 1:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 49E0337B424; Sat, 21 Apr 2001 15:01:27 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f3LM1BK66851; Sat, 21 Apr 2001 15:01:11 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f3LLx9Y67583; Sat, 21 Apr 2001 14:59:09 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200104211839.f3LIdGC01045@mass.dis.org> Date: Sat, 21 Apr 2001 14:59:08 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Mike Smith Subject: Re: kernel core Cc: freebsd-current@FreeBSD.org, imp@FreeBSD.org, "David W. Chapman Jr." Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-01 Mike Smith wrote: >> >> You need to rebuild fsck and install it and fsck your filesystems. This is >> the >> dirpref changes biting you. Warner, we probably need an entry in UPDATING >> for >> the dirpref changes that warn people to build and install a new fsck before >> booting a dirpref kernel. > > Er. This really isn't very good; I can see all sorts of opportunities > here for disk migration between -stable and -current systems causing > massive headaches. I agree. > I assume there's a better fix in the works, so that a "dirpref-touched" > disk can be moved back to a pre-dirpref system? I hope so. I'm not sure if it is feasible, but it would be nice if the kernel would do a sanity check on the dirpref values in the superblock and fall back to defaults if they aren't sane. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 15:11: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id D947C37B423 for ; Sat, 21 Apr 2001 15:11:04 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 65A033E09; Sat, 21 Apr 2001 15:11:04 -0700 (PDT) To: Brian Somers Cc: Jordan Hubbard , freebsd-current@FreeBSD.ORG, olli@secnetix.de Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104212116.f3LLGI549254@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on "Sat, 21 Apr 2001 22:16:18 +0100" Date: Sat, 21 Apr 2001 15:11:04 -0700 From: Dima Dorfman Message-Id: <20010421221104.65A033E09@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > I looked at your patches and immediately thought ``these patches > can't be right'' as I was expecting it to deal with things such as > > xargs -I [] echo args are [], duplicated are [] It deals with it. It conveniently ignores the second '[]' :-). Seriosly though, what do you expect it to do in this case? It can either read some more from stdin, or use the same input it used for the first case of '[]'. I also can't think of a case when either one of these would be useful. I guess the only reason we would want this is if SUSv2 defines it, but even that may not matter since we probably won't support the silly '-i[nospace]' semantic (other than being silly, I can't think of how to implement it without writing a custom getopt() facility). > I'm also dubious about the patches working for large volumes on > standard input. At this point I scrapped the email I was composing > 'cos I didn't have time to look into it further :-/ > > I think it's important to test any patches with a large number of > large path names as input - so that ARG_MAX is reached before the > 5000 argument limit and we can see that we don't end up getting E2BIG > because of an accidental overflow/miscalculation. Any advice on testing this (you did write rev. 1.9 of xargs.1, after all)? I created a file with 4500 words like this: /this/is/a/very/long/path/name/because/I/am/testing/some/posix/limit/10 which ended up being 330 kB. It ran the `utility' multiple times like I expected it to. That said, I don't know what kind of failure mode to expect. I.e., if the patch is wrong, should it have failed with something like, "xargs: exec: argument list too long", or would it just produce incorrect output (which I didn't really check for)? Thanks, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 15:15:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id 5FEA237B424 for ; Sat, 21 Apr 2001 15:15:27 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E8F3966B1C; Sat, 21 Apr 2001 15:15:26 -0700 (PDT) Date: Sat, 21 Apr 2001 15:15:26 -0700 From: Kris Kennaway To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: Post-FILE size change upgrade Message-ID: <20010421151526.C21322@xor.obsecurity.org> References: <96190.987864564@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <96190.987864564@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Sat, Apr 21, 2001 at 04:49:24PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Apr 21, 2001 at 04:49:24PM +0200, Sheldon Hearn wrote: > Is this still true? I don't believe so; I updated from 4.3-RC to 5.0-CURRENT on this machine and didn't have to do anything special (except set NOMAN, because I was being studly and updating using 'make all' instead of 'make world', and the bsd.*.mk changes to use MAN hadn't been backported yet -- this shouldn't affect you if you're making world). Kris --JWEK1jqKZ6MHAcjA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE64gZ+Wry0BWjoQKURAqLkAJ9GxynDvBmWF1gt/gZVxZWQaYmlmgCgmrjj 3InwPUYwePNQlls8c0Lt24U= =nrLB -----END PGP SIGNATURE----- --JWEK1jqKZ6MHAcjA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 15:45:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 7A43D37B423 for ; Sat, 21 Apr 2001 15:45:33 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LMkMb80566; Sat, 21 Apr 2001 23:46:22 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f3LMj9550349; Sat, 21 Apr 2001 23:45:09 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200104212245.f3LMj9550349@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Dima Dorfman Cc: Brian Somers , Jordan Hubbard , freebsd-current@FreeBSD.ORG, olli@secnetix.de, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: Message from Dima Dorfman of "Sat, 21 Apr 2001 15:11:04 PDT." <20010421221104.65A033E09@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 23:45:09 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers writes: > > I looked at your patches and immediately thought ``these patches > > can't be right'' as I was expecting it to deal with things such as > > > > xargs -I [] echo args are [], duplicated are [] > > It deals with it. It conveniently ignores the second '[]' :-). > Seriosly though, what do you expect it to do in this case? It can > either read some more from stdin, or use the same input it used for > the first case of '[]'. I also can't think of a case when either one > of these would be useful. I can't think of a case either :*] > I guess the only reason we would want this is if SUSv2 defines it, but > even that may not matter since we probably won't support the silly > '-i[nospace]' semantic (other than being silly, I can't think of how > to implement it without writing a custom getopt() facility). Absolutely - we wanna avoid that sort of mucking about. > > I'm also dubious about the patches working for large volumes on > > standard input. At this point I scrapped the email I was composing > > 'cos I didn't have time to look into it further :-/ > > > > I think it's important to test any patches with a large number of > > large path names as input - so that ARG_MAX is reached before the > > 5000 argument limit and we can see that we don't end up getting E2BIG > > because of an accidental overflow/miscalculation. > > Any advice on testing this (you did write rev. 1.9 of xargs.1, after > all)? I created a file with 4500 words like this: > > /this/is/a/very/long/path/name/because/I/am/testing/some/posix/limit/10 > > which ended up being 330 kB. It ran the `utility' multiple times like > I expected it to. That said, I don't know what kind of failure mode > to expect. I.e., if the patch is wrong, should it have failed with > something like, "xargs: exec: argument list too long", or would it > just produce incorrect output (which I didn't really check for)? Yes, I was expecting it to fail with E2BIG. Sorry for doubting your patches - they work as advertised from the looks of it ! Nice one. > Thanks, Thank you ! > Dima Dorfman > dima@unixfreak.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 21 16:52:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 8E65F37B422 for ; Sat, 21 Apr 2001 16:52:17 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-88-8.netcologne.de [213.168.88.8]) by mr200.netcologne.de (Mirapoint) with ESMTP id AEC78927; Sun, 22 Apr 2001 01:52:14 +0200 (CEST) Date: Sun, 22 Apr 2001 01:51:32 +0200 (CEST) From: Paul Herman To: Bruce Evans Cc: Subject: Changing "df [device]" behaviour (Re: /bin/df set-gid operator) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Apr 2001, Bruce Evans wrote: > In FreeBSD, mount privilege is controlled by the vfs.usermount > sysctl (default: off), so df must still be setgid operator to work > on devices. > > The mount() method is better because can work on work on all types > of filesystems that the kernel understands, while ufs_df() only > works for ufs. > > [patch] Although I like the idea of being able to df unmounted, non-ufs filesystems, I think the tradeoff might be too harsh. Non-root users aren't allowed to mount(2) at all if vfs.usermount=0, operator or no operator -- that is, in this case, df would fail for non-root users. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message