From owner-freebsd-current Sun Jun 4 1: 9:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 8E29F37B5D2 for ; Sun, 4 Jun 2000 01:09:27 -0700 (PDT) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-16-20.nv.iinet.net.au [203.59.76.20]) by urban.iinet.net.au (8.8.7/8.8.7) with SMTP id QAA25122; Sun, 4 Jun 2000 16:08:49 +0800 Message-ID: <393A0E8F.41C67EA6@elischer.org> Date: Sun, 04 Jun 2000 01:08:47 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Boris Popov Cc: Jeroen Ruigrok van der Werven , current@FreeBSD.ORG Subject: Re: vmware1/linux broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Popov wrote: > > On Sat, 3 Jun 2000, Julian Elischer wrote: > > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec > > format error > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec > > format error > > vmware.sh: cannot create /dev/vmnet1: no such device or address > > jules# dmesg > > [...] > > link_elf: symbol linux_ioctl_register_handler undefined > > link_elf: symbol linux_ioctl_register_handler undefined > > jules# > > Could you check if vmmon and vmnet sources contains the following > lines: > > MODULE_DEPEND(vmmon, linux, 1, 1, 1); , and > MODULE_DEPEND(vmnet, linux, 1, 1, 1); respectively ? > > If not, add one line to the each module and recompile them. I'm > unsure if vmware1 port was updated to reflect recent changes in the > kernel. (vmware2 runs fine for me, the only grief is that license will > expire soon :) that fixed it .. I added the lines to: usr/ports/emulators/vmware/work/vmware-distrib/vmmon-only/freebsd/linux_emu.c and /usr/ports/emulators/vmware/work/vmware-distrib/vmnet-only/freebsd/vmnet_linux.c I'll try figure out how to fix the port. > > > the symbols are present and the linux module is loaded. > > link-elf is just incapable of seeing symbols in the module, > > only in the actual kernel. > > The symbols looked up in the module name space only if dependency > tag is present. This effectively allows us to have multiple versions of > kernel interfaces to be loaded simultaneously. > > -- > 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 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 8:59:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from tempest.waterspout.com (tempest.waterspout.com [208.13.56.2]) by hub.freebsd.org (Postfix) with ESMTP id D092037B561; Sun, 4 Jun 2000 08:59:41 -0700 (PDT) (envelope-from ajk@iu.edu) Received: from localhost (ajk@localhost) by tempest.waterspout.com (8.9.3/8.9.3) with ESMTP id KAA19214; Sun, 4 Jun 2000 10:59:38 -0500 (EST) (envelope-from ajk@iu.edu) Date: Sun, 4 Jun 2000 10:59:31 -0500 (EST) From: "Andrew J. Korty" X-Sender: ajk@tempest.waterspout.com To: Kris Kennaway Cc: Hajimu UMEMOTO , Alexander@Leidinger.net, current@FreeBSD.org Subject: Re: PAM & OpenSSH 2.1 & X11 -> signal 11 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: > > > Thank you. It's working fine with wdm here. > > Good to know. > > > BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. > > Does someone working on it? > > Perhaps the author could tell us (CCed) :-) I'm on it. -- Andrew J. Korty, Lead Security Engineer Office of the Vice President for Information Technology Indiana University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 9:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 495E737B905 for ; Sun, 4 Jun 2000 09:58:29 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id MAA16436 for freebsd-current@freebsd.org; Sun, 4 Jun 2000 12:58:28 -0400 (EDT) (envelope-from dervish) Date: Sun, 4 Jun 2000 12:58:28 -0400 From: bush doctor To: freebsd-current@freebsd.org Subject: Starange behaviour ... Message-ID: <20000604125828.A16397@ikhala.tcimet.net> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need some hints in finding the answer to the following. When compiling xscreensaver-3.24 from the ports on my home box I get the following diagnostics (P200 128Mb ram) ikhala.tcimet.net:dervish> uname -a FreeBSD ikhala.tcimet.net 5.0-CURRENT FreeBSD 5.0-CURRENT #28: Sat Jun 3 07:10:29 EDT 2000 root@ikhala.tcimet.net:/usr/src/sys/compile/GANJA i386 cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format -Wp,-lang-c89 -L/usr/X11R6/lib -o cage cage.o screenhack-gl.o xlock-gl.o ../xlockm ore.o ../../utils/resources.o ../../utils/visual.o ../../utils/visual-gl.o ../../utils/usleep.o ../../utils/yarandom.o ../../utils/hsv.o ../../utils/colors.o -L/usr/X11R6/lib -lMesaGL -lMesaGLU -lXmu -lSM -lICE -lXmu -lXt -lXt -lX11 -lXext -lm /usr/lib/libc_r.so.4: WARNING! setkey(3) not present in the system! /usr/lib/libc_r.so.4: warning: this program uses gets(), which is unsafe. /usr/lib/libc_r.so.4: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc_r.so.4: WARNING! des_setkey(3) not present in the system! /usr/lib/libc_r.so.4: WARNING! encrypt(3) not present in the system! /usr/lib/libc_r.so.4: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc_r.so.4: warning: this program uses f_prealloc(), which is stupid. /usr/lib/libc_r.so.4: WARNING! des_cipher(3) not present in the system! /usr/lib/libc_r.so.4: warning: tempnam() possibly used unsafely; consider using mkstemp() cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format -Wp,-lang-c89 -c -I. -I./../../utils -I./.. -I../.. -I/usr/X11R6/include -DSTANDA LONE -DUSE_GL -DHAVE_CONFIG_H -O -pipe -I/usr/X11R6/include gears.c Alone this would indicate that the port needs to be linked with the -pthreads option. However on my box at work (PIII 550 128Mb ram) goku.cl.msu.edu:dervish> uname -a FreeBSD goku.cl.msu.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #40: Thu May 25 21:56:27 EDT 2000 root@goku.cl.msu.edu:/usr/src/sys/compile/GOKU i386 the same port reports none of the warnings :(. Any clues? #;^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! 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 Sun Jun 4 10: 2:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by hub.freebsd.org (Postfix) with ESMTP id BC63E37BC4B for ; Sun, 4 Jun 2000 10:02:44 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from almanac.yi.org (pm001-025.dialup.bignet.net [64.79.80.25]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id NAA17512; Sun, 4 Jun 2000 13:02:38 -0400 Received: by almanac.yi.org (Postfix, from userid 1000) id 4C0A71946; Sun, 4 Jun 2000 13:01:46 -0400 (EDT) Date: Sun, 4 Jun 2000 13:01:46 -0400 From: Will Andrews To: bush doctor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Starange behaviour ... Message-ID: <20000604130146.B546@argon.gryphonsoft.com> References: <20000604125828.A16397@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000604125828.A16397@ikhala.tcimet.net>; from dervish@ikhala.tcimet.net on Sun, Jun 04, 2000 at 12:58:28PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 04, 2000 at 12:58:28PM -0400, bush doctor wrote: > the same port reports none of the warnings :(. Any clues? Different libc linking in one of the libs. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 10:30:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from verbal.uits.iupui.edu (ajk-5.waterspout.com [208.13.56.5]) by hub.freebsd.org (Postfix) with ESMTP id 4A1D037B5E4; Sun, 4 Jun 2000 10:30:45 -0700 (PDT) (envelope-from ajk@iu.edu) Received: from localhost (ajk@localhost) by verbal.uits.iupui.edu (8.9.3/8.9.3) with ESMTP id MAA07916; Sun, 4 Jun 2000 12:30:42 -0500 (EST) (envelope-from ajk@iu.edu) X-Authentication-Warning: verbal.uits.iupui.edu: ajk owned process doing -bs Date: Sun, 4 Jun 2000 12:30:42 -0500 (EST) From: "Andrew J. Korty" X-Sender: ajk@verbal.uits.iupui.edu To: Kris Kennaway Cc: Hajimu UMEMOTO , Alexander@Leidinger.net, current@FreeBSD.org Subject: Re: PAM & OpenSSH 2.1 & X11 -> signal 11 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: > > > BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. > > Does someone working on it? Oops ... it looks like ssh-agent doesn't support DSA keys yet. Am I missing something? I suppose I could just add DSA support for the PAM authentication phase ... -- Andrew J. Korty, Lead Security Engineer Office of the Vice President for Information Technology Indiana University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 11:45:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 0928537B89F; Sun, 4 Jun 2000 11:45:31 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:qCXkYf86/gDTZC7EYVj9dP/SOnFHf0OzxzSdUSRfYD8XXbn+49MO7AY/nLFYtZ/m@localhost [::1]) (authenticated) by peace.mahoroba.org (8.10.1/3.7W-peace) with ESMTP id e54IjEU43342; Mon, 5 Jun 2000 03:45:14 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 05 Jun 2000 03:45:10 +0900 (JST) Message-Id: <20000605.034510.95025277.ume@mahoroba.org> To: ajk@iu.edu Cc: kris@FreeBSD.org, Alexander@Leidinger.net, current@FreeBSD.org Subject: Re: PAM & OpenSSH 2.1 & X11 -> signal 11 From: Hajimu UMEMOTO (=?iso-2022-jp?B?GyRCR19LXBsoQiAbJEJIJRsoQg==?=) In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Sun, 4 Jun 2000 12:30:42 -0500 (EST) >>>>> "Andrew J. Korty" said: > On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: > > > BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. > > Does someone working on it? ajk> Oops ... it looks like ssh-agent doesn't support DSA keys yet. Am ajk> I missing something? I suppose I could just add DSA support for the ajk> PAM authentication phase ... Oh, I see. You are right. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 15:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 7E2AB37B64E for ; Sun, 4 Jun 2000 15:19:30 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id SAA49140; Sun, 4 Jun 2000 18:19:25 -0400 (EDT) (envelope-from dervish) Date: Sun, 4 Jun 2000 18:19:25 -0400 From: bush doctor To: Will Andrews Cc: freebsd-current@FreeBSD.ORG Subject: Re: Starange behaviour ... Message-ID: <20000604181925.A16745@ikhala.tcimet.net> Mail-Followup-To: Will Andrews , freebsd-current@FreeBSD.ORG References: <20000604125828.A16397@ikhala.tcimet.net> <20000604130146.B546@argon.gryphonsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000604130146.B546@argon.gryphonsoft.com>; from andrews@technologist.com on Sun, Jun 04, 2000 at 01:01:46PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Will Andrews aka (andrews@technologist.com) said: > On Sun, Jun 04, 2000 at 12:58:28PM -0400, bush doctor wrote: > > the same port reports none of the warnings :(. Any clues? > > Different libc linking in one of the libs. Thanxs, I found the culprit. I needed to rebuild libgii. Looks like I hadn't rebuilt since the -pthread option was implemented. > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? #;-) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! 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 Sun Jun 4 17:57:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id AF17337B6C3; Sun, 4 Jun 2000 17:57:51 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id e550wB616228; Mon, 5 Jun 2000 10:28:11 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Mon, 5 Jun 2000 10:28:33 +0930 Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id KAA09858; Mon, 5 Jun 2000 10:24:18 +0930 (CST) Received: from fuzz.dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id KAA04932; Mon, 5 Jun 2000 10:24:18 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.3/8.9.3) with ESMTP id KAA07209; Mon, 5 Jun 2000 10:24:26 +0930 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <393AFA40.6DECACC1@dsto.defence.gov.au> Date: Mon, 05 Jun 2000 10:24:24 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@freebsd.org Cc: current@freebsd.org, Matthew Thyer Subject: Re: Oddities with the new binutils References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone tried the specific instructions I gave to reproduce the problem ? i.e.: - make world - making and installing a new kernel - mergemaster - reboot - deletion of ALL installed ports - recompile of every essential port (inc XFree 3.3.6) Then: Build xaos from ports (/usr/ports/graphics/xaos) Run xaos and press 'a' David O'Brien wrote: > > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > Three issues: > > - floating point math doesn't seem to work properly: > > - backward compatibility: > > - stability: > > Are others seeing these issues? > > > These issues make me think that the new binutils is not yet ready > > for -STABLE. > > It could also be poorly written ASM code in the things you were running. > The old Binutils let people write inconsistent and illegal ASM. > > -- > -- David (obrien@FreeBSD.org) -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 21:20:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from web115.yahoomail.com (web115.yahoomail.com [205.180.60.88]) by hub.freebsd.org (Postfix) with SMTP id A685837B52E for ; Sun, 4 Jun 2000 21:19:56 -0700 (PDT) (envelope-from eaglez69@yahoo.com) Received: (qmail 1844 invoked by uid 60001); 5 Jun 2000 04:19:51 -0000 Message-ID: <20000605041951.1843.qmail@web115.yahoomail.com> Received: from [136.152.194.139] by web115.yahoomail.com; Sun, 04 Jun 2000 21:19:51 PDT Date: Sun, 4 Jun 2000 21:19:51 -0700 (PDT) From: Eaglez Subject: Re: Unknown Devices To: John Hengstler , freebsd-current@freebsd.org Cc: hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, i'm not sure about 5.0's new funky support (i mean, if it supports the SB Live, who knows), but in the past, PCI modems have never been supported, because they all tend to be win modems (only MS windows drivers available). I'd advise possibly an external modem. (Hey, they're probably still cheaper than USB modems, although i'd go with that if it IS somehow cheaper.) -Jesse --- John Hengstler wrote: > Greetings, > > I just subscribed to -current list to get > suggestions on the following so if > I have missed comments on this already I am sorry > for the redundancy. > > I have just upgraded to 5.0-current in order to get > the driver for my ether > card, which has corrected that problem (xe device). > > But I still can't access my pci modem, because it is > listed as an unknown > device. There are many other unknown devices as > well. The following is > dmesg output: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > FreeBSD 5.0-CURRENT #0: Thu Jun 1 22:20:39 PDT 2000 > root@laptop.atbd.com:/usr/src/sys/compile/ATBD > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (473.17-MHz 586-class > CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > Features=0x8021bf > AMD Features=0x80000800 > real memory = 29294592 (28608K bytes) > avail memory = 25411584 (24816K bytes) > Preloaded elf kernel "kernel" at 0xc033e000. > K6-family MTRR support enabled (2 registers) > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib1: > at device 1.0 on pci0 > pci1: on pcib1 > pci1: device> at 0.0 irq 9 > isab0: at device 7.0 on > pci0 > isa0: on isab0 > atapci0: port > 0x1820-0x182f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 7.2 irq 11 > isab1: > at device 7.4 on pci0 > chip1: port > 0x1830-0x1833,0x1834-0x1837,0x1000-0x10ff irq 11 at > device 7.5 on pci0 > > ***built in card here ? also appeared in prior sys > releases *** > pci0: (vendor=0x11c1, dev=0x0441) at > 9.0 irq 9 > > pcic-pci0: at > device 10.0 on pci0 > pcic-pci0: TI12XX PCI Config Reg: [ring > enable][speaker enable][pwr > save][CSC serial isa irq] > fdc0: at port > 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port > 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > pcic0: at port 0x3e0-0x3e1 on isa0 > pcic0: Polling mode > pccard0: on pcic0 > pccard1: on pcic0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > ppc0: This ppc chipset does not support the extended > I/O port range...no > problem > ppc0: at port 0x378-0x37b irq 7 on > isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE > mode > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > unknown0: at port > 0x80,0x62,0x66,0x72-0x75,0x92,0xa8-0xa9,0x38a-0x38b,0x8040-0x807f,0x9050-0x9 > 051 iomem 0xfffe0000-0xffffffff on isa0 > unknown1: at iomem > 0-0x9ffff,0xec000-0xfffff,0x100000-0x1bfffff on > isa0 > unknown2: at port > 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 > unknown: can't assign resources > unknown3: at port 0x40-0x43 irq 0 on isa0 > unknown4: at port 0x70-0x71 irq 8 on isa0 > unknown: can't assign resources > npxisa0: at port > 0xf0-0xff irq 13 on isa0 > unknown5: at port 0x61 on isa0 > unknown6: at port 0xcf8-0xcff on isa0 > unknown7: at port > 0x4d0-0x4d1,0x8000-0x803f,0x8080-0x808f on isa0 > unknown8: at port 0x3400-0x347f on isa0 > unknown9: at iomem 0xdc000-0xdffff on isa0 > unknown10: on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > IP packet filtering initialized, divert disabled, > rule-based forwarding > enabled, default to deny, logging limited to 10 > packets/entry by default > ad0: 5729MB [12416/15/63] at > ata0-master using UDMA66 > acd0: CDROM at ata1-master > using UDMA33 > Mounting root from ufs:/dev/ad0s3a > pccard: card inserted, slot 0 > > Everything else on the system works for now, except > for the modem. This > same results were in 4.0-release, and stable as > well.. > > Any suggestions are appreciated. > > John Hengstler > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of > the message __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 22:54:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1419337B615 for ; Sun, 4 Jun 2000 22:54:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@[209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA62560; Sun, 4 Jun 2000 22:54:11 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA34108; Sun, 4 Jun 2000 22:54:28 -0700 (PDT) (envelope-from obrien) Date: Sun, 4 Jun 2000 22:54:28 -0700 From: "David O'Brien" To: Matthew Thyer Cc: current@freebsd.org, Matthew Thyer Subject: Re: Oddities with the new binutils Message-ID: <20000604225428.F29113@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> <393AFA40.6DECACC1@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393AFA40.6DECACC1@dsto.defence.gov.au>; from Matthew.Thyer@dsto.defence.gov.au on Mon, Jun 05, 2000 at 10:24:24AM +0930 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 05, 2000 at 10:24:24AM +0930, Matthew Thyer wrote: > Has anyone tried the specific instructions I gave to reproduce > the problem ? These instructions do things at too high a level. > i.e.: > > - make world > - making and installing a new kernel > - mergemaster > - reboot All fine. > - deletion of ALL installed ports > - recompile of every essential port (inc XFree 3.3.6) This doesn't give me anything to debug. I need to know a specific source file. Sending this bug report plus instructions to reproduce to the Binutils maintainers will get no where. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 4 23:42:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id 2B2B237B7B2; Sun, 4 Jun 2000 23:42:27 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id e556gj609251; Mon, 5 Jun 2000 16:12:45 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Mon, 5 Jun 2000 16:13:22 +0930 Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id QAA22007; Mon, 5 Jun 2000 16:06:55 +0930 (CST) Received: from fuzz.dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id QAA07431; Mon, 5 Jun 2000 16:06:55 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.3/8.9.3) with ESMTP id QAA00423; Mon, 5 Jun 2000 16:06:54 +0930 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <393B4A86.2D8CF3D7@dsto.defence.gov.au> Date: Mon, 05 Jun 2000 16:06:54 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@freebsd.org Cc: current@freebsd.org, Matthew Thyer Subject: Re: Oddities with the new binutils References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> <393AFA40.6DECACC1@dsto.defence.gov.au> <20000604225428.F29113@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, I emailed my details on what I have done on two machines that are exhibiting this problem. Because these machines are different in their hardware and have not expressed the problem in the past, I dont think its a hardware issue. Before the new binutils both machines did not have this problem. I dont know if it is the binutils change that has caused this problem as I do not have the time to exhaustively test. My email was to try to get others to reproduce the problem hence I gave details on what I did. So, has anyone done the procedure I have and seen or not seen the problem where xaos version 3.0 draws garbage when renderring. (run xaos and press the 'a' key). I haven't given kernel config files or hardware details because I dont think its relevant until someone can say "I have done the steps you have outlined and I dont see you problem". I do not have time to debug this myself (I would also need to learn a few things) however, I have been running -CURRENT for more than 5 years and know that I have upgraded my software correctly and am fairly convinced that hardware is not an issue so I am reporting this problem to see if others can reproduce it as a service to the FreeBSD community (I wont even charge for it!). I also do not intend to report this to the binutils maintainers because it may be a FreeBSD issue, not a binutils issue. David O'Brien wrote: > > On Mon, Jun 05, 2000 at 10:24:24AM +0930, Matthew Thyer wrote: > > Has anyone tried the specific instructions I gave to reproduce > > the problem ? > > These instructions do things at too high a level. > > > i.e.: > > > > - make world > > - making and installing a new kernel > > - mergemaster > > - reboot > > All fine. > > > - deletion of ALL installed ports > > - recompile of every essential port (inc XFree 3.3.6) > > This doesn't give me anything to debug. I need to know a specific source > file. Sending this bug report plus instructions to reproduce to the > Binutils maintainers will get no where. > > -- > -- David (obrien@FreeBSD.org) -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 5 3: 2:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from eden.dei.uc.pt (eden.dei.uc.pt [193.137.203.230]) by hub.freebsd.org (Postfix) with ESMTP id CBF0337BC6E for ; Mon, 5 Jun 2000 03:02:00 -0700 (PDT) (envelope-from nunov@dei.uc.pt) Received: from dei.uc.pt (marx.dei.uc.pt [193.136.212.95]) by eden.dei.uc.pt (8.10.1/8.10.1) with ESMTP id e55A1td16064 for ; Mon, 5 Jun 2000 11:01:55 +0100 (WET DST) Message-ID: <393B7A90.FDA1FEBD@dei.uc.pt> Date: Mon, 05 Jun 2000 11:01:52 +0100 From: Nuno Veiga X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: FreeBSD 2.2 -> 4.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have the code of an ATM driver for FreeBSD 2.2 I would like to port it to FreeBSD 4.0 What cautions should I have? When I tried to compile the code, I got a warning: "Don't #include ioctl.h in the kernel. Include xxxio.h instead." So I did it. Then an error: ... ################: MAKING DRIVER ################ #####: [1]> [install] driver (host) #####: [2]> [install] driver/FREEBSD (host) #####: [3]> [install] driver/FREEBSD/i386 (host) #####: [5]> [install] driver/FREEBSD/i386/host (host) gmake[6]: *** No rule to make target `/usr/include/machine/spl.h', needed by `_lebuscom.ldep'. Stop. gmake[5]: *** [host] Error 2 gmake[4]: *** [install] Error 2 gmake[3]: *** [install] Error 2 gmake[2]: *** [install] Error 2 gmake[1]: *** [driver] Error 2 gmake: *** [all] Error 2 Could you help me? Thank you Nuno Veiga To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 5 8:21: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 0A9B837BC3D; Mon, 5 Jun 2000 08:21:01 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA17373; Mon, 5 Jun 2000 08:23:53 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006051523.IAA17373@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Eaglez Cc: John Hengstler , freebsd-current@freebsd.org, hardware@freebsd.org Subject: Re: Unknown Devices In-reply-to: Your message of "Sun, 04 Jun 2000 21:19:51 PDT." <20000605041951.1843.qmail@web115.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jun 2000 08:23:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, i'm not sure about 5.0's new funky support (i > mean, if it supports the SB Live, who knows), but in > the past, PCI modems have never been supported, > because they all tend to be win modems (only MS > windows drivers available). I'd advise possibly an > external modem. (Hey, they're probably still cheaper > than USB modems, although i'd go with that if it IS > somehow cheaper.) Watch out - some USB modems are also WinModems. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 5 8:43: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from c014.sfo.cp.net (c014-h022.c014.sfo.cp.net [209.228.12.86]) by hub.freebsd.org (Postfix) with SMTP id A8A4C37BDB0 for ; Mon, 5 Jun 2000 08:42:50 -0700 (PDT) (envelope-from john@hei.net) Received: (cpmta 28213 invoked from network); 5 Jun 2000 08:31:49 -0700 Received: from unknown (HELO trout) (209.222.163.131) by smtp.transport.com with SMTP; 5 Jun 2000 08:31:49 -0700 X-Sent: 5 Jun 2000 15:31:49 GMT Message-ID: <001501bfcf00$5b905b00$83a3ded1@hei.net> From: "John Hengstler" To: "Mike Smith" Cc: , References: <200006051523.IAA17373@mass.cdrom.com> Subject: Re: Unknown Devices Date: Mon, 5 Jun 2000 08:11:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know that what the actual modem is inside. The system is a Compaq Presario 1200. I am waiting for the compaq restore CD to reinstall the windows side to figure out what really on here. (Needs a compaq driver?) John ----- Original Message ----- From: "Mike Smith" To: "Eaglez" Cc: "John Hengstler" ; ; Sent: Monday, June 05, 2000 8:23 AM Subject: Re: Unknown Devices > > Well, i'm not sure about 5.0's new funky support (i > > mean, if it supports the SB Live, who knows), but in > > the past, PCI modems have never been supported, > > because they all tend to be win modems (only MS > > windows drivers available). I'd advise possibly an > > external modem. (Hey, they're probably still cheaper > > than USB modems, although i'd go with that if it IS > > somehow cheaper.) > > Watch out - some USB modems are also WinModems. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 5 10:23:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 2F8F137C3D0 for ; Mon, 5 Jun 2000 10:23:44 -0700 (PDT) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lapbsd.nat.Awfulhak.org [172.31.0.22]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id SAA99043 for ; Mon, 5 Jun 2000 18:23:41 +0100 (BST) (envelope-from markk@knigma.org) Message-ID: Date: Mon, 5 Jun 2000 18:23:19 +0100 To: freebsd-current@freebsd.org From: Mark Knight Subject: Re: Panic during boot under current References: <200005251717.SAA03422@hak.lan.Awfulhak.org> <200005302211.PAA39853@bubba.whistle.com> In-Reply-To: <200005302211.PAA39853@bubba.whistle.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200005302211.PAA39853@bubba.whistle.com>, Archie Cobbs writes >Brian Somers writes: >> Also (Mark sits beside me at work), is there anyone else out there >> that actually runs FreeBSD-current under VMWare (irrespective of the >> host OS) ? This problem has now been traced down to a bug in the lnc driver, where multiple instances are installed. This surfaced as a result of changes made on 16th May. -- Mark Knight PGP Public Key: finger mkn@knigma.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 5 13: 0:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 9427137BDB3; Mon, 5 Jun 2000 13:00:35 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA42897; Mon, 5 Jun 2000 20:56:49 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA00878; Mon, 5 Jun 2000 20:18:19 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006051918.UAA00878@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Knight , paul@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG, wollman@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re: Panic during boot under current In-Reply-To: Message from Mark Knight of "Mon, 05 Jun 2000 18:23:19 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jun 2000 20:18:19 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <200005302211.PAA39853@bubba.whistle.com>, Archie Cobbs > writes > >Brian Somers writes: > >> Also (Mark sits beside me at work), is there anyone else out there > >> that actually runs FreeBSD-current under VMWare (irrespective of the > >> host OS) ? > > This problem has now been traced down to a bug in the lnc driver, where > multiple instances are installed. > > This surfaced as a result of changes made on 16th May. Specifically, the lnc driver declares NLNC softcs. Mark has an isa style ``device lnc0'' in his config and then uses vmware with two configured devices. config produces lnc.h which contains ``#define NLNC 1'' and if_lnc_pci.c dives in and starts writing to the second softc. I'll look at fixing this at some point if you don't have time Paul :-I This may have broken because Paul changed the softc decl from static to just global (so that the other if_lnc*.c modules can get at it).... either that or Mark has been ``just lucky'' so far and the lnc driver has never worked properly with more than one device. This would neatly explain why he's seen funny errors in the past - one of them was a message to you Garrett saying that your npx.c modification to do no more than output a boot-time diagnostic seemed to screw up his kernel !!! > -- > Mark Knight PGP Public Key: finger mkn@knigma.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 Mon Jun 5 19:57:21 2000 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 E054337B7DB; Mon, 5 Jun 2000 19:57:10 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id MAA57603; Tue, 6 Jun 2000 12:27:08 +0930 (CST) (envelope-from grog) Date: Tue, 6 Jun 2000 12:27:08 +0930 From: Greg Lehey To: FreeBSD current users , FreeBSD Stable Users Subject: HEADS UP: Another Vinum RAID-5 data integrity problem (*sigh*) Message-ID: <20000606122708.D57232@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i 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 only just fixed one problem in RAID-5 revive, and another one has surfaced. For the moment: if you have a RAID-5 plex with a dead subdisk, leave it that way. It's safer than restarting it. I think I should have it fixed relatively quickly. Watch this space. 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 Jun 6 0:21:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from evil.2y.net (ztown2-2-9.adsl.one.net [216.23.15.9]) by hub.freebsd.org (Postfix) with ESMTP id 3F4D037BF58; Tue, 6 Jun 2000 00:21:05 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id DAA02325; Tue, 6 Jun 2000 03:27:43 -0400 (EDT) (envelope-from cokane) Date: Tue, 6 Jun 2000 03:27:43 -0400 From: Coleman Kane To: stable@freebsd.org, current@freebsd.org Subject: 3dfx device driver Message-ID: <20000606032743.A2315@cokane.yi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi, I am just updating about the driver. I mad a few significant changes th= at are up at http://pohl.ececs.uc.edu/~cokane now. --=20 Coleman Kane President,=20 UC Free O.S. Users Group - http://pohl.ececs.uc.edu --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5PKfvERViMObJ880RAZprAJ40187EBD1/028JJXYmv0PYhzJt/ACgkKu6 qBIwCWarkp4vAN8SiaK7DPM= =vSUV -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 1:15: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id 5750A37BF96 for ; Tue, 6 Jun 2000 01:14:54 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id MAA05837 for current@freebsd.org; Tue, 6 Jun 2000 12:14:50 +0400 (MSD) (envelope-from ache) Date: Tue, 6 Jun 2000 12:14:46 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: What happens with SECURELVL? (init complains) Message-ID: <20000606121446.A5822@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now init always complains: init: cannot get kernel security level: No such file or directory It is because KERN_SECURELVL define still present in /sys/sysctl.h but gone from kern_mib.c Moreover, even define is gone from kern_mib.c, sysctl_kern_securelvl() function is still there! Please clean up the mess. -- 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 Jun 6 3:41: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 3E7A237B717; Tue, 6 Jun 2000 03:41:00 -0700 (PDT) (envelope-from kuriyama@FreeBSD.org) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e56AejY45097; Tue, 6 Jun 2000 19:40:46 +0900 (JST) Date: Tue, 06 Jun 2000 19:40:45 +0900 Message-ID: <863dmr5byq.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: john@hei.net Cc: freebsd-current@FreeBSD.org, hardware@FreeBSD.org Subject: Re: Unknown Devices In-Reply-To: In your message of "2 Jun 2000 21:09:16 GMT" <001201bfccd2$1643be00$83a3ded1@hei.net> References: <001201bfccd2$1643be00$83a3ded1@hei.net> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2 Jun 2000 21:09:16 GMT, John Hengstler wrote: > pci0: (vendor=0x11c1, dev=0x0441) at 9.0 irq 9 http://www.yourvote.com/pci/pciread.asp?venid=0x11c1 says that chip is AT&T Microelectronics' WinModem. This is not yet supported by FreeBSD. -- Jun Kuriyama // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 3:53: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id DAC4837C007; Tue, 6 Jun 2000 03:52:57 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id LAA96948; Tue, 6 Jun 2000 11:59:20 +0100 (IST) (envelope-from steve) 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: <001501bfcf00$5b905b00$83a3ded1@hei.net> Date: Tue, 06 Jun 2000 11:59:19 +0100 (IST) From: "Steve O'Hara-Smith" To: John Hengstler Subject: Re: Unknown Devices Cc: current@freebsd.org, hardware@freebsd.org, Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jun-00 John Hengstler wrote: > I don't know that what the actual modem is inside. The system is a Compaq > Presario 1200. I rather think that means Lucent windows only modem. It does in my 1690. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 5:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id D16D437B665 for ; Tue, 6 Jun 2000 05:53:12 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id PAA29510; Tue, 6 Jun 2000 15:51:56 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id PAA54626; Tue, 6 Jun 2000 15:32:32 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <393CEF53.EAC2041C@FreeBSD.org> Date: Tue, 06 Jun 2000 15:32:19 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alexander Sanda Cc: current@FreeBSD.org Subject: Re: Shared memory changes in current? References: <4.3.2.7.2.20000604012146.02c204a8@mail.kabsi.at> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Sanda wrote: > Anyone aware of them? > > After building a complete kernel + world with a very recent -current > (Saturday morning, european time) I now get lots of shared memory errors > in gnome (most coming from gdk and imlib, some from Xfree 4 aswell). I > recompiled parts of gnome (gtk+, imlib, glib) and the situation has > slightly changed, but gdk still throws a lot of shmget() failed: errors. It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 6:25:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id F376A37B665 for ; Tue, 6 Jun 2000 06:25:41 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id RAA00459 for current@freebsd.org; Tue, 6 Jun 2000 17:25:39 +0400 (MSD) (envelope-from ache) Date: Tue, 6 Jun 2000 17:25:34 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: ls Message-ID: <20000606172534.A448@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: It seems that color support in 'ls' is clean now. I have no ideas or bug reports to fix it more. -- 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 Jun 6 7: 7:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id C3E9837B96C for ; Tue, 6 Jun 2000 07:07:53 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id RAA03330; Tue, 6 Jun 2000 17:06:41 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id RAA57463; Tue, 6 Jun 2000 17:08:13 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <393D05BF.3A373254@FreeBSD.org> Date: Tue, 06 Jun 2000 17:07:59 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: current@FreeBSD.org Subject: Re: ls References: <20000606172534.A448@nagual.pp.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > FYI: It seems that color support in 'ls' is clean now. I have no ideas or > bug reports to fix it more. There is colorls-related PR 18616 (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18616). Please take a look at it and close if it is mandatory or merge if not. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 7:15:54 2000 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 2BC1B37BBD9; Tue, 6 Jun 2000 07:15:48 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id SAA40645; Tue, 6 Jun 2000 18:15:46 +0400 (MSD) (envelope-from ache) Date: Tue, 6 Jun 2000 18:15:43 +0400 From: "Andrey A. Chernov" To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: ls Message-ID: <20000606181541.A40578@nagual.pp.ru> References: <20000606172534.A448@nagual.pp.ru> <393D05BF.3A373254@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393D05BF.3A373254@FreeBSD.org>; from sobomax@FreeBSD.org on Tue, Jun 06, 2000 at 05:07:59PM +0300 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 06, 2000 at 05:07:59PM +0300, Maxim Sobolev wrote: > There is colorls-related PR 18616 > (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18616). Please take a look at it > and close if it is mandatory or merge if not. Our system color-'ls' already don't have this bug. Know nothing about colors from ports. -- 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 Jun 6 7:20: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id BD59E37BBA4 for ; Tue, 6 Jun 2000 07:19:58 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id RAA04012; Tue, 6 Jun 2000 17:18:44 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id RAA57601; Tue, 6 Jun 2000 17:20:00 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <393D0881.7BE47D6A@FreeBSD.org> Date: Tue, 06 Jun 2000 17:19:46 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: current@FreeBSD.org Subject: Re: ls References: <20000606172534.A448@nagual.pp.ru> <393D05BF.3A373254@FreeBSD.org> <20000606181541.A40578@nagual.pp.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > On Tue, Jun 06, 2000 at 05:07:59PM +0300, Maxim Sobolev wrote: > > There is colorls-related PR 18616 > > (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18616). Please take a look at it > > and close if it is mandatory or merge if not. > > Our system color-'ls' already don't have this bug. > Know nothing about colors from ports. Probably it would be nice if colorls from the ports will be synchronized with one in /usr/src, so users of 4.0 and downward could benefit from your efforts as well. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 7:41: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 4964F37B7C1 for ; Tue, 6 Jun 2000 07:41:02 -0700 (PDT) (envelope-from regnauld@eu.org) Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged)) by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id QAA12718; Tue, 6 Jun 2000 16:42:18 +0200 (CEST) X-Authentication-Warning: mail.ftf.dk: Host fw2.ftf.dk [192.168.1.2] (may be forged) claimed to be ns.int.ftf.net Received: (from uucp@localhost) by ns.int.ftf.net (8.9.2/8.9.3) with UUCP id QAA41276; Tue, 6 Jun 2000 16:40:32 +0200 (CEST) Received: (from regnauld@localhost) by flow.eu.org (8.9.3/8.9.1/stimpy-1.0) id KAA02307; Tue, 6 Jun 2000 10:34:59 +0200 (CEST) (envelope-from regnauld) Message-ID: <20000606103459.40497@flow.eu.org> Date: Tue, 6 Jun 2000 10:34:59 +0200 From: Phil Regnauld To: Terry Lambert Cc: FreeBSD-Current@FreeBSD.ORG Subject: Re: FrontPage Extensions References: <00ea01be374a$b11fa020$1acb2e9c@westbend.net> <199901190354.UAA04699@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199901190354.UAA04699@usr04.primenet.com>; from Terry Lambert on Tue, Jan 19, 1999 at 03:54:33AM +0000 X-Operating-System: FreeBSD 5.0-CURRENT i386 Organization: FTFnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [reply to an old mail found in archives] Terry Lambert writes: > For what it's worth, the FP security issues are very well documented > by ReadyToRun Software's site (these are the folks who do the UNIX > ports for Microsoft). > > They also keep both BSDI 2.1 and 3.0 binaries available, and they > know about FreeBSD (it's mentioned in the FAQ as an unsupported > platform; apparently someone was having problems with the MD5 > password hashing. Someone who cares should send them mail on how > to update their FAQ to be more correct, and to raise FreeBSD's > visibility as a platform -- e.g. what versions to us4e for > what, install instructions for FreeBSD, etc.). FWIW, they now have a native FreeBSD version (FP extensions SR1, the port needs to be updated BTW) -- works like a charm with minor changes to one of the port patches. The binaries are 3.3, linked dynamically -- compat3x will get this working. Caveat: if you misconfigure your VirtualHost in some way, any call to the FP-patched Apache to that subweb's /_vti_bin/ will make it (apache) segfault. Will debug this if I find time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 10: 6:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D315737BA3A; Tue, 6 Jun 2000 10:06:25 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb43.imasy.or.jp [202.227.24.171]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e56H6GP29636; Wed, 7 Jun 2000 02:06:16 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: SMP + APM = panic -> fixed! X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000607020615U.iwasaki@jp.FreeBSD.org> Date: Wed, 07 Jun 2000 02:06:15 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 27 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We're having this problem for long time (from the old 4.0-CURRENT days), but Mr. SUMITANI discovered a bug and fixed it. The problem was that we got worng gdt pointer for the current cpu, then panic... The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Please test this and I'll commit & MFC this if we have no problem with this fix. I love to have APM enabled SMP system with 4.1-RELEASE. Index: bios.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/bios.c,v retrieving revision 1.32 diff -u -r1.32 bios.c --- bios.c 2000/05/17 19:44:16 1.32 +++ bios.c 2000/06/06 16:47:46 @@ -262,7 +262,7 @@ union descriptor *p_gdt; #ifdef SMP - p_gdt = &gdt[cpuid]; + p_gdt = &gdt[cpuid * NGDT]; #else p_gdt = gdt; #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 10:14:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 1FF2C37B69B; Tue, 6 Jun 2000 10:13:59 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id MAA05724; Tue, 6 Jun 2000 12:18:43 -0500 (CDT) (envelope-from jlemon) Date: Tue, 6 Jun 2000 12:18:43 -0500 From: Jonathan Lemon To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! Message-ID: <20000606121843.A4129@prism.flugsvamp.com> References: <20000607020615U.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000607020615U.iwasaki@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 07, 2000 at 02:06:15AM +0900, Mitsuru IWASAKI wrote: > > We're having this problem for long time (from the old 4.0-CURRENT > days), but Mr. SUMITANI discovered a bug and fixed it. > The problem was that we got worng gdt pointer for the current cpu, > then panic... > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! > Please test this and I'll commit & MFC this if we have no problem with > this fix. I don't have an SMP + APM system around at the moment, but the fix does look correct to me, go ahead and commit it. Thanks for tracking this down! -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 10:41:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 7165337B567; Tue, 6 Jun 2000 10:41:45 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb43.imasy.or.jp [202.227.24.171]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e56HfgP40167; Wed, 7 Jun 2000 02:41:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: jlemon@flugsvamp.com Cc: iwasaki@jp.FreeBSD.org, freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: <20000606121843.A4129@prism.flugsvamp.com> References: <20000607020615U.iwasaki@jp.FreeBSD.org> <20000606121843.A4129@prism.flugsvamp.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000607024141K.iwasaki@jp.FreeBSD.org> Date: Wed, 07 Jun 2000 02:41:41 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Please test this and I'll commit & MFC this if we have no problem with > > this fix. > > I don't have an SMP + APM system around at the moment, but the > fix does look correct to me, go ahead and commit it. Thanks for > tracking this down! Thank you for reviewing this. I'm going to comit tomorrow night (JST), then MFC on early next week if no problems are reported. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 12:27:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id ABE4537B911 for ; Tue, 6 Jun 2000 12:27:20 -0700 (PDT) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.10.1/2000040900) with ESMTP id VAA02104 for ; Tue, 6 Jun 2000 21:27:18 +0200 (CEST) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.10.1/2000040900) with ESMTP id VAA09354 for ; Tue, 6 Jun 2000 21:27:16 +0200 (CEST) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id VAA12002 for freebsd-current@freebsd.org; Tue, 6 Jun 2000 21:27:16 +0200 (MET DST) From: Thomas Schuerger Message-Id: <200006061927.VAA12002@wjpserver.cs.uni-sb.de> Subject: Check for ports updates To: freebsd-current@freebsd.org Date: Tue, 6 Jun 2000 21:27:16 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Is there already a tool that checks the installed ports for available updates in /usr/ports? I've written such a tool, which seems to work fine already. Anyone interested? Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 12:35:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by hub.freebsd.org (Postfix) with ESMTP id F151837B911 for ; Tue, 6 Jun 2000 12:35:32 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from almanac.yi.org (pm001-036.dialup.bignet.net [64.79.80.36]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id PAA16280; Tue, 6 Jun 2000 15:35:16 -0400 Received: by almanac.yi.org (Postfix, from userid 1000) id C63F0195D; Tue, 6 Jun 2000 15:33:51 -0400 (EDT) Date: Tue, 6 Jun 2000 15:33:51 -0400 From: Will Andrews To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: Check for ports updates Message-ID: <20000606153351.E7792@argon.gryphonsoft.com> References: <200006061927.VAA12002@wjpserver.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200006061927.VAA12002@wjpserver.cs.uni-sb.de>; from schuerge@wjpserver.CS.Uni-SB.DE on Tue, Jun 06, 2000 at 09:27:16PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 06, 2000 at 09:27:16PM +0200, Thomas Schuerger wrote: > Is there already a tool that checks the installed ports for available > updates in /usr/ports? > > I've written such a tool, which seems to work fine already. Anyone > interested? pkg_version(1) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 13:25:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 1D3C837B98D for ; Tue, 6 Jun 2000 13:25:09 -0700 (PDT) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.10.1/2000040900) with ESMTP id WAA02318; Tue, 6 Jun 2000 22:25:04 +0200 (CEST) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.10.1/2000040900) with ESMTP id WAA09840; Tue, 6 Jun 2000 22:25:02 +0200 (CEST) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id WAA12391; Tue, 6 Jun 2000 22:25:02 +0200 (MET DST) From: Thomas Schuerger Message-Id: <200006062025.WAA12391@wjpserver.cs.uni-sb.de> Subject: Re: Check for ports updates In-Reply-To: <20000606153351.E7792@argon.gryphonsoft.com> from Will Andrews at "Jun 6, 2000 03:33:51 pm" To: Will Andrews Date: Tue, 6 Jun 2000 22:25:02 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there already a tool that checks the installed ports for available > > updates in /usr/ports? > > > > I've written such a tool, which seems to work fine already. Anyone > > interested? > > pkg_version(1) Ah, haven't seen that before. The output of pkg_version is very canonical, but not very readable for humans. And it's slower than my version... ;-) Here is my version called "ports_updates": --------- #!/usr/bin/perl ################################################################################ # $Id: ports_updates,v 1.1 2000/06/01 20:24:06 schuerge Exp $ # # 20000601 schuerge first checkin # # TODO: Make version check more sophisticated. Currently the version strings are # compared lexicographically, which may sometimes not be what is expected. ################################################################################ # # ports_updates - fast check for available updates of installed ports # # (C) 2000 by Thomas Schürger Mail: thomas@schuerger.com # # invocation: # ports_updates # # description: # Checks for each installed port if a newer version is available # in /usr/ports. Ports are output in a sorted manner. # # Uses efficient merge-sort like algorithm for detecting updated # port versions. The file /usr/ports/INDEX is inspected for # detecting updates, which is not updated daily in the ports # collection. Therefore the results are just almost exact. # ################################################################################ $installedports = `\\ls -1 /var/db/pkg | sort -t "-" +0 -1`; @installedports = split(/\n/, $installedports); $c = 0; foreach $i ( @installedports ) { next if($i =~ /^\./); # super-user ls also lists dot-files $i =~ /(.*)-([^\-].*)/; $installedname[$c] = $1; $installedversion[$c] = $2; $c++; } $ports = ` cut -f "1-2" -d "|" /usr/ports/INDEX | sort -t "-" +0 -1`; @ports = split(/\n/, $ports); $c = 0; foreach $i ( @ports ) { $i =~ /^(.*)-([^\-\|].*)\|(.*)/; $name[$c] = $1; $version[$c] = $2; $location[$c] = $3; # $location[$c] =~ s/^\/usr\/ports\///; $c++; } @a = stat("/usr/ports/INDEX"); $time = localtime($a[9]); $age = -M "/usr/ports/INDEX"; if($age >= 30) { printf("Ports available: %4d (last port index update: %s)\n",($#ports+1),$time); } else { printf("Ports available: %4d (last port index update %d day%s ago)\n",($#ports+1),$age,$age == 1 ? "" : "s"); } printf("Ports installed: %4d\n",($#installedname+1)); $c = 0; # counter for @ports $d = 0; # counter for @installedports while($c <= $#name && $d <= $#installedname) { $a = $name[$c] cmp $installedname[$d]; # printf("%4d %-30s %-10s %4d %-30s %-10s $a\n",$c,$name[$c],$version[$c],$d,$installedname[$d],$installedversion[$d]); if($a == 0) { $ver = $version[$c]; $instver = $installedversion[$d]; if($ver gt $instver) # newer version available? { if(!$header) # has the table header not been printed yet? { print "\nThe following installed ports should be updated:\n\n"; print "Port name /usr/ports Installed Port location\n"; print "--------------------------------------------------------------------------\n"; $header = 1; } printf("%-20s %-12s %-10s %s\n",$name[$c],$ver,$instver,$location[$c]); } } $c++ if($a <= 0); if($a > 0) { push(@obsolete,$installedname[$d]."-".$installedversion[$d]); } $d++ if($a >= 0); } if(!$header) { print "\nCongratulations, all installed ports are up-to-date!\n"; } if($#obsolete >= 0) { print "\nThe following ports are installed but are no longer available in /usr/ports\n"; print "(or now have a different name) and should be considered for deletion:\n\n"; foreach $i (@obsolete) { print "$i\n", } } ------ Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 13:29:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.mdanderson.org (mail.mdacc.tmc.edu [143.111.87.47]) by hub.freebsd.org (Postfix) with ESMTP id 9DB8637B722 for ; Tue, 6 Jun 2000 13:28:52 -0700 (PDT) (envelope-from fosburgh@flash.net) Received: from jefnt (jef-nt.mdacc.tmc.edu [143.111.64.202]) by mail.mdanderson.org (8.9.1b+Sun/8.9.1) with SMTP id PAA26017; Tue, 6 Jun 2000 15:24:52 -0500 (CDT) Message-ID: <02e001bfcff5$b920b990$ca406f8f@mdacc.tmc.edu> From: "Jonathan Fosburgh" To: "Thomas Schuerger" Cc: References: <200006062025.WAA12391@wjpserver.cs.uni-sb.de> Subject: Re: Check for ports updates Date: Tue, 6 Jun 2000 15:28:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Thomas Schuerger" To: "Will Andrews" Cc: Sent: Tuesday, June 06, 2000 3:25 PM Subject: Re: Check for ports updates > > > Is there already a tool that checks the installed ports for available > > > updates in /usr/ports? > > > > > > I've written such a tool, which seems to work fine already. Anyone > > > interested? > > > > pkg_version(1) > > Ah, haven't seen that before. The output of pkg_version is very > canonical, but not very readable for humans. And it's slower than my > version... ;-) > > Here is my version called "ports_updates": > > > --------- > > #!/usr/bin/perl > > ############################################################################ #### > # $Id: ports_updates,v 1.1 2000/06/01 20:24:06 schuerge Exp $ > # > # 20000601 schuerge first checkin > # > # TODO: Make version check more sophisticated. Currently the version strings are > # compared lexicographically, which may sometimes not be what is expected. > ############################################################################ #### > # > # ports_updates - fast check for available updates of installed ports > # > # (C) 2000 by Thomas Schürger Mail: thomas@schuerger.com > # > # invocation: > # ports_updates > # > # description: > # Checks for each installed port if a newer version is available > # in /usr/ports. Ports are output in a sorted manner. > # > # Uses efficient merge-sort like algorithm for detecting updated > # port versions. The file /usr/ports/INDEX is inspected for > # detecting updates, which is not updated daily in the ports > # collection. Therefore the results are just almost exact. > # > ############################################################################ #### > > $installedports = `\\ls -1 /var/db/pkg | sort -t "-" +0 -1`; > @installedports = split(/\n/, $installedports); > > $c = 0; > foreach $i ( @installedports ) > { > next if($i =~ /^\./); # super-user ls also lists dot-files > $i =~ /(.*)-([^\-].*)/; > $installedname[$c] = $1; > $installedversion[$c] = $2; > $c++; > } > > $ports = ` cut -f "1-2" -d "|" /usr/ports/INDEX | sort -t "-" +0 -1`; > @ports = split(/\n/, $ports); > > $c = 0; > foreach $i ( @ports ) > { > $i =~ /^(.*)-([^\-\|].*)\|(.*)/; > $name[$c] = $1; > $version[$c] = $2; > $location[$c] = $3; > # $location[$c] =~ s/^\/usr\/ports\///; > $c++; > } > > @a = stat("/usr/ports/INDEX"); > $time = localtime($a[9]); > $age = -M "/usr/ports/INDEX"; > > if($age >= 30) > { > printf("Ports available: %4d (last port index update: %s)\n",($#ports+1),$time); > } > else > { > printf("Ports available: %4d (last port index update %d day%s ago)\n",($#ports+1),$age,$age == 1 ? "" : "s"); > } > > printf("Ports installed: %4d\n",($#installedname+1)); > > $c = 0; # counter for @ports > $d = 0; # counter for @installedports > > while($c <= $#name && $d <= $#installedname) > { > $a = $name[$c] cmp $installedname[$d]; > > # printf("%4d %-30s %-10s %4d %-30s %-10s $a\n",$c,$name[$c],$version[$c],$d,$installedname[$d],$installedversion[$d]) ; > > if($a == 0) > { > $ver = $version[$c]; > $instver = $installedversion[$d]; > > if($ver gt $instver) # newer version available? > { > if(!$header) # has the table header not been printed yet? > { > print "\nThe following installed ports should be updated:\n\n"; > print "Port name /usr/ports Installed Port location\n"; > print "--------------------------------------------------------------------------\ n"; > $header = 1; > } > > printf("%-20s %-12s %-10s %s\n",$name[$c],$ver,$instver,$location[$c]); > } > } > > $c++ if($a <= 0); > > if($a > 0) > { > push(@obsolete,$installedname[$d]."-".$installedversion[$d]); > } > > $d++ if($a >= 0); > } > > if(!$header) > { > print "\nCongratulations, all installed ports are up-to-date!\n"; > } > > if($#obsolete >= 0) > { > print "\nThe following ports are installed but are no longer available in /usr/ports\n"; > print "(or now have a different name) and should be considered for deletion:\n\n"; > > foreach $i (@obsolete) > { > print "$i\n", > } > } > > ------ > > > Ciao, > Thomas Schürger. http://www.menden.org > > Maybe you can submit this as a port :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 14:12:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C31D37BC10 for ; Tue, 6 Jun 2000 14:12:41 -0700 (PDT) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.10.1/2000040900) with ESMTP id XAA02619 for ; Tue, 6 Jun 2000 23:12:37 +0200 (CEST) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.10.1/2000040900) with ESMTP id XAA10407 for ; Tue, 6 Jun 2000 23:12:36 +0200 (CEST) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id XAA12640 for freebsd-current@freebsd.org; Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) From: Thomas Schuerger Message-Id: <200006062112.XAA12640@wjpserver.cs.uni-sb.de> Subject: Mesa segfaults To: freebsd-current@freebsd.org Date: Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm having problems with Mesa 3.2. Some OpenGL programs don't work at all (they quit with a segmentation fault on initialization), some other programs work a short time and then crash the same way. I installed 4.0-Release some days ago (I had 4.0-Current before that), but that didn't solve the problem, neither did remaking the Mesa port. Is anyone else experiencing this? Any ideas of what to do? Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 14:47: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7FF1737B568 for ; Tue, 6 Jun 2000 14:47:01 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id XAA95190; Tue, 6 Jun 2000 23:46:41 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200006062146.XAA95190@info.iet.unipi.it> Subject: problem creating new kernels with 20000604 snap To: current@freebsd.org Date: Tue, 6 Jun 2000 23:46:41 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i am a bit in trouble with a june 4th snap of -current. I have successfully installed it, and even compiled and installed a kernel using the GENERIC config. However when i try to remove devices from there, with high probability i end up in a panic while booting, generally in loader_preload() which tries to dereference a null pointer. I cannot really track down what is going on -- the loader shows something like module miibus module usb module splash and if i remove any usb device, or something ethernet using the mii bus, or (it seems) even some scsi device, it panics. Is this a bug or a feature ? Should i just keep all the pieces in GENERIC and add my options there ? help appreciated. thanks luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 14:58:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by hub.freebsd.org (Postfix) with ESMTP id 2DBFB37B5F1 for ; Tue, 6 Jun 2000 14:58:29 -0700 (PDT) (envelope-from bmah@cisco.com) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.10.1/8.10.1) id e56LwLT23308; Tue, 6 Jun 2000 14:58:21 -0700 (PDT) (envelope-from bmah) Message-Id: <200006062158.e56LwLT23308@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.1.1+ 05/08/2000 To: Thomas Schuerger Cc: Will Andrews , freebsd-current@FreeBSD.ORG Subject: Re: Check for ports updates In-reply-to: <200006062025.WAA12391@wjpserver.cs.uni-sb.de> References: <200006062025.WAA12391@wjpserver.cs.uni-sb.de> Comments: In-reply-to Thomas Schuerger message dated "Tue, 06 Jun 2000 22:25:02 +0200." From: bmah@cisco.com (Bruce A. Mah) Reply-To: bmah@cisco.com 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&+ Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Tue, 06 Jun 2000 14:58:21 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If memory serves me right, Thomas Schuerger wrote: > > > Is there already a tool that checks the installed ports for available > > > updates in /usr/ports? > > > > > > I've written such a tool, which seems to work fine already. Anyone > > > interested? > > > > pkg_version(1) > > Ah, haven't seen that before. The output of pkg_version is very > canonical, but not very readable for humans. And it's slower than my > version... ;-) Without having looked at ports_updates yet, let me just mention that: 1. If you want human-readable output, try "pkg_version -v". Maybe that should have been a default; certainly I always run it that way. But in the case that a program was going to postprocess the output, I didn't want it to have to wade through a bunch of pretty-printing stuff to get the results it needed. 2. When I was writing pkg_version, speed wasn't exactly a big priority to me, since pretty much *anything* was faster than what I was doing. Bruce. PS. I've been really bad about ignoring suggestions for pkg_version, mostly because it does everything I need/want it to do right now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 15:12:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id B3AD037B568 for ; Tue, 6 Jun 2000 15:12:39 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000606221219.LKCA17505.relay02@chello.nl>; Wed, 7 Jun 2000 00:12:19 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id AAA10489; Wed, 7 Jun 2000 00:12:32 +0200 (CEST) (envelope-from wkb) Date: Wed, 7 Jun 2000 00:12:32 +0200 From: Wilko Bulte To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: problem creating new kernels with 20000604 snap Message-ID: <20000607001232.F10255@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <200006062146.XAA95190@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006062146.XAA95190@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Tue, Jun 06, 2000 at 11:46:41PM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 06, 2000 at 11:46:41PM +0200, Luigi Rizzo wrote: > hi, > i am a bit in trouble with a june 4th snap of -current. > > I have successfully installed it, and even compiled and > installed a kernel using the GENERIC config. > However when i try to remove devices from there, > with high probability i end up in a panic while booting, > generally in loader_preload() which tries to dereference > a null pointer. > > I cannot really track down what is going on -- the loader shows > something like > > module miibus > module usb > module splash > > and if i remove any usb device, or something ethernet using the mii > bus, or (it seems) even some scsi device, it panics. I've seen something similar on Alpha when I removed the dc driver (leaving xl and miibus in). Removing dc and config / make depend / make /make install / reboot left me with a crashing alpha box. It only got as far as the loader printing a few lines on loading modules. And then a 'kernel stack not valid, HALT' line. Doing config -r on the same kernel config file worked OK. > Is this a bug or a feature ? Should i just keep all the pieces > in GENERIC and add my options there ? I don't pretend to understand this.. -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 17:10:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BE69237BB94 for ; Tue, 6 Jun 2000 17:10:07 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:5b9bcO5HGIpO+nT1F2k4gD4HRW2R5+YZ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA04497; Wed, 7 Jun 2000 09:10:02 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wZVumBTa3LzipLjPdD5rc0gL0w5nKd/D@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id JAA27095; Wed, 7 Jun 2000 09:16:44 +0900 (JST) Message-Id: <200006070016.JAA27095@zodiac.mech.utsunomiya-u.ac.jp> To: Michael Harnois Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: not making a splash In-reply-to: Your message of "29 May 2000 20:47:49 EST." <86og5oizay.fsf@mharnois.workgroup.net> References: <86og5oizay.fsf@mharnois.workgroup.net> Date: Wed, 07 Jun 2000 09:16:43 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've tried to get a splash screen with two different 320x200x256 >bitmaps now, and all I get is a blank screen. Is there something else >I'm missing? Would you type 'boot -v' at the boot loader prompt and send me /var/run/dmesg.boot? I also like to see the output from 'vidcontrol -i mode' and 'vidcontrol -i adapter'. Are you sure the bitmap file is in BMP format and is not larger than 320x200? Is it possible for me to have a look at the file? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 17:32:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8D48437B964 for ; Tue, 6 Jun 2000 17:32:23 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA36369 for ; Tue, 6 Jun 2000 20:32:16 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 6 Jun 2000 20:32:16 -0400 (EDT) From: Chuck Robey To: FreeBSD-current Subject: vmware 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 fianlly have vmware2 working on my current box, but I have noticed a couple things in my log, and I wanted to ask about them. Here's a little bit at the end: sio1: 3 more silo overflows (total 1268) /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 359971, unlocked dirty pages: 217740 I guess I can understand the large number of silo overflows. I noticed that I can't seem to get any mails when I have vmware working, and I wish that wasn't so. The part that really worries me, tho, is the virtual memory warning. I was doing a lot of Windows software installation (which dragged on *really* slowly), but is there anything to be worried about in that warning above? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 20:15:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id AC23237BAB8; Tue, 6 Jun 2000 20:15:31 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id WAA26787; Tue, 6 Jun 2000 22:15:21 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <001d01bfd02e$9db01960$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Terry Lambert" , "Phil Regnauld" Cc: "FreeBSD-Ports" , References: <00ea01be374a$b11fa020$1acb2e9c@westbend.net> <199901190354.UAA04699@usr04.primenet.com> <20000606103459.40497@flow.eu.org> Subject: Re: FrontPage Extensions Date: Tue, 6 Jun 2000 22:15:21 -0500 Organization: West Bend Internet 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.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Phil Regnauld" > Terry Lambert writes: > > For what it's worth, the FP security issues are very well documented > > by ReadyToRun Software's site (these are the folks who do the UNIX > > ports for Microsoft). > > > > They also keep both BSDI 2.1 and 3.0 binaries available, and they > > know about FreeBSD (it's mentioned in the FAQ as an unsupported > > platform; apparently someone was having problems with the MD5 > > password hashing. Someone who cares should send them mail on how > > to update their FAQ to be more correct, and to raise FreeBSD's > > visibility as a platform -- e.g. what versions to us4e for > > what, install instructions for FreeBSD, etc.). > > FWIW, they now have a native FreeBSD version (FP extensions > SR1, the port needs to be updated BTW) -- works like a charm with minor > changes to one of the port patches. > Yes, there is only a minor change that is needed to the port to get it working with FP 2K SR1. See PR 18581, PR 18788 I did find a problem with fpsrvadm.exe. If you have libcrypt linked to libscrypt, then fpsrvadm.exe creates an invalid MD5 password (I believe the buffer RTR used to hold the password returned from the crypt function is too small for the MD5 passwords). I have informed RTR and they said a fix would be available in the next release. For the time being the port (apache13-fp, or upcomming mod_frontpage) will still need to use the BSDI extentions, and statically compile the apache server with libdescrypt.a on systems where libcrypt is linked to libscrypt. > Caveat: if you misconfigure your VirtualHost in some way, any call > to the FP-patched Apache to that subweb's /_vti_bin/ will make it > (apache) segfault. > > Will debug this if I find time. > I haven't come across this problem. But I do know that it will segfault if you are not using a patched suexec, as the unpatched suexec will not allow fpexe to run. Scot PS. This is off topic for current, so please remove current when replying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 6 20:22:53 2000 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 9D29B37BBA1; Tue, 6 Jun 2000 20:22:43 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12zWPu-000Hru-00; Wed, 07 Jun 2000 10:22:06 +0700 Date: Wed, 7 Jun 2000 10:22:06 +0700 (ALMST) From: Boris Popov To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: <20000607020615U.iwasaki@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 Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > We're having this problem for long time (from the old 4.0-CURRENT > days), but Mr. SUMITANI discovered a bug and fixed it. > The problem was that we got worng gdt pointer for the current cpu, > then panic... > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' command works too, but machine never come back from the suspend mode (looks like interrupt controller programmed incorrectly or something like this). -- 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 Jun 6 22:31:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id 55F5D37B746 for ; Tue, 6 Jun 2000 22:31:26 -0700 (PDT) (envelope-from rjoseph@manatee.mammalia.org) Received: (from rjoseph@localhost) by manatee.mammalia.org (8.9.3/8.9.3) id WAA04551 for freebsd-current@FreeBSD.org; Tue, 6 Jun 2000 22:31:21 -0700 (PDT) (envelope-from rjoseph) Date: Tue, 6 Jun 2000 22:31:21 -0700 From: R Joseph Wright To: freebsd-current@FreeBSD.org Subject: odd error in bioscall.s Message-ID: <20000606223120.A4519@manatee.mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have this problem while building a kernel from sources cvsup'ed today: cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s {standard input}: Assembler messages: {standard input}:774: Error: operands given don't match any known 386 instruction {standard input}:839: Error: operands given don't match any known 386 instruction *** Error code 1 Stop in /usr/src/sys/compile/MANATEE. The file bioscall.s has only 163 lines. Where is it getting 774 and 839? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 1:34:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E6B1537B5BB; Wed, 7 Jun 2000 01:34:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA52809; Wed, 7 Jun 2000 01:34:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 01:34:56 -0700 (PDT) From: Kris Kennaway To: R Joseph Wright Cc: freebsd-current@FreeBSD.org Subject: Re: odd error in bioscall.s In-Reply-To: <20000606223120.A4519@manatee.mammalia.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, 6 Jun 2000, R Joseph Wright wrote: > I have this problem while building a kernel from sources cvsup'ed > today: > > cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s > {standard input}: Assembler messages: > {standard input}:774: Error: operands given don't match any known 386 instruction > {standard input}:839: Error: operands given don't match any known 386 instruction > *** Error code 1 > > Stop in /usr/src/sys/compile/MANATEE. > > The file bioscall.s has only 163 lines. Where is it getting 774 and > 839? Preprocessor. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 4:26:28 2000 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 63B1A37B834; Wed, 7 Jun 2000 04:26: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.8.7/8.8.7) with ESMTP id VAA22951; Wed, 7 Jun 2000 21:26:18 +1000 Date: Wed, 7 Jun 2000 21:26:14 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: R Joseph Wright , freebsd-current@FreeBSD.ORG Subject: Re: odd error in bioscall.s In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Kris Kennaway wrote: > On Tue, 6 Jun 2000, R Joseph Wright wrote: > > > I have this problem while building a kernel from sources cvsup'ed > > today: > > > > cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s > > {standard input}: Assembler messages: > > {standard input}:774: Error: operands given don't match any known 386 instruction > > {standard input}:839: Error: operands given don't match any known 386 instruction > > *** Error code 1 > > > > Stop in /usr/src/sys/compile/MANATEE. > > > > The file bioscall.s has only 163 lines. Where is it getting 774 and > > 839? > > Preprocessor. Preprocessor + broken assembler. Error messages about files in pipelines are even less useful than error messages about temporary files. The preprocessor puts line numbers in its output, but gas apparently doesn't understand them. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 6: 2:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 58F3837B93C; Wed, 7 Jun 2000 06:02:49 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id PAA28207; Wed, 7 Jun 2000 15:02:46 +0200 (CEST) Date: Wed, 7 Jun 2000 15:02:45 +0200 From: Martin Cracauer To: "David O'Brien" Cc: Matthew Thyer , current@FreeBSD.ORG, Matthew Thyer Subject: Re: Oddities with the new binutils Message-ID: <20000607150244.A23666@cons.org> References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000603232557.C67024@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sat, Jun 03, 2000 at 11:25:57PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000603232557.C67024@dragon.nuxi.com>, David O'Brien wrote: > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > Three issues: > > - floating point math doesn't seem to work properly: I don't have a -current machine I want to delete all ports from, but I have a -current from yesterday, I compiled xaos on it and libpng, which is the only dependency of xaos. That leave XFree as the only non-recompiled thing in the chain. Works fine. > It could also be poorly written ASM code in the things you were running. > The old Binutils let people write inconsistent and illegal ASM. xoas and png themself do not have assembler files. Xfree servers have some, but not in floating point related things. Where is the information that this is a floating-point problem from? Matthew, do you possibly use a custom gcc from /usr/local/bin and the native assembler or vice versa? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 6:15:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109]) by hub.freebsd.org (Postfix) with ESMTP id 77C6037BC85 for ; Wed, 7 Jun 2000 06:15:22 -0700 (PDT) (envelope-from vova@express.ru) Received: from vova (helo=localhost) by lanturn.express.ru with local-esmtp (Exim 3.11 #1) id 12zfgp-000J1T-00 for current@freebsd.org; Wed, 07 Jun 2000 17:16:11 +0400 Date: Wed, 7 Jun 2000 17:16:06 +0400 (MSD) From: vova@express.ru X-Sender: vova@lanturn.kmost.express.ru To: current@freebsd.org Subject: 'make world' broken 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 while making usr.sbin/kdump or usr.bin/truss: ------------------------------------------------- In file included from ioctl.c:80: /usr/obj/ext/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/ext/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition ioctl.c: In function `ioctlname': ioctl.c:363: sizeof applied to an incomplete type *** Error code 1 Stop in /ext/src/usr.bin/truss. *** Error code 1 ------------------------------------------------- Any ideas ? -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 8:37:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 53EC537B78B; Wed, 7 Jun 2000 08:37:39 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id RAA03037; Wed, 7 Jun 2000 17:37:36 +0200 (CEST) Date: Wed, 7 Jun 2000 17:37:35 +0200 From: Martin Cracauer To: "David O'Brien" Cc: Matthew Thyer , current@FreeBSD.ORG, Matthew Thyer Subject: Re: Oddities with the new binutils Message-ID: <20000607173734.A3002@cons.org> References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> <20000607150244.A23666@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000607150244.A23666@cons.org>; from cracauer@cons.org on Wed, Jun 07, 2000 at 03:02:45PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000607150244.A23666@cons.org>, Martin Cracauer wrote: > In <20000603232557.C67024@dragon.nuxi.com>, David O'Brien wrote: > > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > > Three issues: > > > - floating point math doesn't seem to work properly: > > I don't have a -current machine I want to delete all ports from, but I > have a -current from yesterday, I compiled xaos on it and libpng, > which is the only dependency of xaos. That leave XFree as the only > non-recompiled thing in the chain. > > Works fine. OK, now I am pissed. I also recompiled and restarted X11 to trace this down, only to find that some stupid error in Xwrapper breaks xinit and I had to roll my own xinit. Anyway, now I am running everything in the pipe compiled within the last 24 hours on a fresh -current and xaos work just fine. > > It could also be poorly written ASM code in the things you were running. > > The old Binutils let people write inconsistent and illegal ASM. > > xoas and png themself do not have assembler files. Xfree servers have > some, but not in floating point related things. > > Where is the information that this is a floating-point problem from? > > Matthew, do you possibly use a custom gcc from /usr/local/bin and the > native assembler or vice versa? Also, what level of optimization do you use? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 9:53:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id DC4CB37BB75; Wed, 7 Jun 2000 09:53:27 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn49.imasy.or.jp [202.227.24.241]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e57GrMP05053; Thu, 8 Jun 2000 01:53:22 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: bp@butya.kz Cc: iwasaki@jp.FreeBSD.org, freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: References: <20000607020615U.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000608015319J.iwasaki@jp.FreeBSD.org> Date: Thu, 08 Jun 2000 01:53:19 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > > > We're having this problem for long time (from the old 4.0-CURRENT > > days), but Mr. SUMITANI discovered a bug and fixed it. > > The problem was that we got worng gdt pointer for the current cpu, > > then panic... > > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! > > Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' OK, I think many people will be happy with poweroff on SMP system, so I'd like to commit this first. Then I'll track it down and try to fix later in order to support suspend/resume SMP system. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 10:48: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 61FB037BA1F for ; Wed, 7 Jun 2000 10:47:57 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id NAA05282; Wed, 7 Jun 2000 13:16:27 +0100 (BST) (envelope-from nik) Date: Wed, 7 Jun 2000 13:16:27 +0100 From: Nik Clayton To: Thomas Schuerger Cc: Will Andrews , freebsd-current@FreeBSD.ORG Subject: Re: Check for ports updates Message-ID: <20000607131626.A4884@catkin.nothing-going-on.org> References: <20000606153351.E7792@argon.gryphonsoft.com> <200006062025.WAA12391@wjpserver.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200006062025.WAA12391@wjpserver.cs.uni-sb.de>; from schuerge@wjpserver.CS.Uni-SB.DE on Tue, Jun 06, 2000 at 10:25:02PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 06, 2000 at 10:25:02PM +0200, Thomas Schuerger wrote: > > > Is there already a tool that checks the installed ports for available > > > updates in /usr/ports? > > > > > > I've written such a tool, which seems to work fine already. Anyone > > > interested? > > > > pkg_version(1) > > Ah, haven't seen that before. The output of pkg_version is very > canonical, but not very readable for humans. pkg_version -v pkg_version -c N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 10:50:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f53.law8.hotmail.com [216.33.241.53]) by hub.freebsd.org (Postfix) with SMTP id E675837BE1C for ; Wed, 7 Jun 2000 10:50:34 -0700 (PDT) (envelope-from the_hermit665@hotmail.com) Received: (qmail 6460 invoked by uid 0); 7 Jun 2000 17:50:33 -0000 Message-ID: <20000607175033.6459.qmail@hotmail.com> Received: from 207.246.128.137 by www.hotmail.com with HTTP; Wed, 07 Jun 2000 10:50:33 PDT X-Originating-IP: [207.246.128.137] Reply-To: the_hermit665@hotmail.com From: "Cosmic 665" To: schuerge@wjpserver.CS.Uni-SB.DE, freebsd-current@freebsd.org Subject: Re: Mesa segfaults Date: Wed, 07 Jun 2000 10:50:33 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would be nice if you let us know what programs your trying to run and what kind of video card you have :) -cosmic-665 >From: Thomas Schuerger >To: freebsd-current@freebsd.org >Subject: Mesa segfaults >Date: Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) >MIME-Version: 1.0 >Received: from [204.216.27.18] by hotmail.com (3.2) with ESMTP id >MHotMailBB06B47000B1D820F3DACCD81B1255920; Tue Jun 06 14:13:23 2000 >Received: by hub.freebsd.org (Postfix, from userid 538)id 85C9A37BAAD; Tue, > 6 Jun 2000 14:12:44 -0700 (PDT) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid 719342E8168; Tue, 6 Jun 2000 14:12:44 -0700 >(PDT)(envelope-from owner-freebsd-current) >Received: by hub.freebsd.org (bulk_mailer v1.12); Tue, 6 Jun 2000 14:12:44 >-0700 >Received: from uni-sb.de (uni-sb.de [134.96.252.33])by hub.freebsd.org >(Postfix) with ESMTP id 5C31D37BC10for ; Tue, >6 Jun 2000 14:12:41 -0700 (PDT)(envelope-from >schuerge@wjpserver.CS.Uni-SB.DE) >Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])by uni-sb.de >(8.10.1/2000040900) with ESMTP id XAA02619for >; Tue, 6 Jun 2000 23:12:37 +0200 (CEST) >Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de >[134.96.247.42])by cs.uni-sb.de (8.10.1/2000040900) with ESMTP id >XAA10407for ; Tue, 6 Jun 2000 23:12:36 +0200 >(CEST) >Received: (from schuerge@localhost)by wjpserver.cs.uni-sb.de >(8.9.3/8.9.3/wjp-SVR4/1999052600) id XAA12640for >freebsd-current@freebsd.org; Tue, 6 Jun 2000 23:12:36 +0200 (MET DST) >From owner-freebsd-current@FreeBSD.ORG Tue Jun 06 14:17:00 2000 >Delivered-To: freebsd-current@freebsd.org >Message-Id: <200006062112.XAA12640@wjpserver.cs.uni-sb.de> >X-Mailer: ELM [version 2.4ME+ PL57 (25)] >Sender: owner-freebsd-current@FreeBSD.ORG >X-Loop: FreeBSD.ORG >Precedence: bulk > >Hi! > >I'm having problems with Mesa 3.2. Some OpenGL programs don't work at >all (they quit with a segmentation fault on initialization), some >other programs work a short time and then crash the same way. I >installed 4.0-Release some days ago (I had 4.0-Current before that), >but that didn't solve the problem, neither did remaking the Mesa port. >Is anyone else experiencing this? Any ideas of what to do? > > >Ciao, >Thomas Schürger. http://www.menden.org > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 12:20:17 2000 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 3AA3B37BF4B for ; Wed, 7 Jun 2000 12:20:12 -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.9.3/8.9.3) with SMTP id PAA27835; Wed, 7 Jun 2000 15:19:47 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Jun 2000 15:19:47 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: What happens with SECURELVL? (init complains) In-Reply-To: <20000606121446.A5822@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 At bde's request, I moved kern.suser_permitted to kern_prot.c and accidentally also trimmed kern.securelevel. I just committed it back into kern_mib.c. Please let me know if there are further problems. That said, I'm a little puzzled as to where securelevel is being defined -- a bunch of stuff depends on the variable and yet my test build succeeded without it in there. And you go that far also -- far enough to boot rather than have the linking fail. Robert On Tue, 6 Jun 2000, Andrey A. Chernov wrote: > Now init always complains: > > init: cannot get kernel security level: No such file or directory > > It is because KERN_SECURELVL define still present in /sys/sysctl.h but > gone from kern_mib.c > Moreover, even define is gone from kern_mib.c, sysctl_kern_securelvl() > function is still there! > > Please clean up the mess. > > -- > 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 > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 12:27: 6 2000 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 BD47D37BA64 for ; Wed, 7 Jun 2000 12:27:02 -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.9.3/8.9.3) with SMTP id PAA27930; Wed, 7 Jun 2000 15:26:56 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Jun 2000 15:26:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: What happens with SECURELVL? (init complains) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Robert Watson wrote: > That said, I'm a little puzzled as to where securelevel is being defined > -- a bunch of stuff depends on the variable and yet my test build > succeeded without it in there. And you go that far also -- far enough to > boot rather than have the linking fail. Nevermind -- I just trimmed the SYSCTL, not the variable declaration. Sorry for inconvenience to all. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 13:25:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 9EE0D37BE8D for ; Wed, 7 Jun 2000 13:25:24 -0700 (PDT) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.10.1/2000040900) with ESMTP id WAA11228; Wed, 7 Jun 2000 22:25:16 +0200 (CEST) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.10.1/2000040900) with ESMTP id WAA00615; Wed, 7 Jun 2000 22:25:14 +0200 (CEST) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id WAA29208; Wed, 7 Jun 2000 22:25:14 +0200 (MET DST) From: Thomas Schuerger Message-Id: <200006072025.WAA29208@wjpserver.cs.uni-sb.de> Subject: Re: Mesa segfaults In-Reply-To: <20000607175033.6459.qmail@hotmail.com> from Cosmic 665 at "Jun 7, 2000 10:50:33 am" To: the_hermit665@hotmail.com Date: Wed, 7 Jun 2000 22:25:14 +0200 (MET DST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would be nice if you let us know what programs your trying to run and > what kind of video card you have :) Oops, sorry. I have a Matrox G200 (8 Meg SGRAM) and a Voodoo 2 card (12 Meg) running on a dual P II/400 (512 Megs) with 4.0-Release and XFree86 3.3.6 (XF86_SVGA) installed... Before Mesa 3.2, everything worked fine). Ciao, Thomas Schürger. http://www.menden.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 15:26:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EA86437B5A8 for ; Wed, 7 Jun 2000 15:26:11 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@[209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA78549 for ; Wed, 7 Jun 2000 15:26:10 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA17045 for current@freebsd.org; Wed, 7 Jun 2000 15:26:31 -0700 (PDT) (envelope-from obrien) Date: Wed, 7 Jun 2000 15:26:30 -0700 From: "David O'Brien" To: current@freebsd.org Subject: make release broken on Alpha Message-ID: <20000607152630.A17008@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make release is breaking in the crunch gen'ing: gzip -cn /usr/src/release/sysinstall/sysinstall.8 > sysinstall.8.gz install -c -s -o root -g wheel -m 555 sysinstall /stand install -c -o root -g wheel -m 444 sysinstall.8.gz /usr/share/man/man8 rm -rf /R/stage/crunch mkdir -p /R/stage/crunch export RELEASE_BUILD_FIXIT=noway ; for j in boot fixit ; do sed -e "s:MACHINE: alpha:" /usr/src/release/${j}_crunch.conf > /usr/obj/usr/src/release/${j}_crun ch.conf && rm -rf ${j}_crunch && mkdir ${j}_crunch && ( cd ${j}_crunch && cr unchgen /usr/obj/usr/src/release/${j}_crunch.conf && make -DRELEASE_CRUNCH -f $ {j}_crunch.mk subclean all NOCRYPT=yes "CFLAGS=-O -pipe -DCRUNCHED_BINARY") & & mv ${j}_crunch/${j}_crunch /R/stage/crunch/${j} && true || { rm -rf ${j}_cru nch ; false ; } ; done [reading /usr/obj/usr/src/release/boot_crunch.conf] ^Mcrunchgen: /usr/obj/usr/s rc/release/boot_crunch.conf:4: `/usr/src/sbin/alpha' is not a directory, skippin g it [filling in parms for sh] ^M [filling in parms for fin d] ^M [filling in parms for sed] ^M [filling in parms for test] ^M [filling in p arms for rm] ^M [filling in parms for pwd] ^M [filling in parms for ppp] ^M [fi lling in parms for sysinstall] ^M [filling in parms for newfs] ^M [filling i n parms for minigzip] ^M [filling in parms for cpio] ^M [filling in parms for fsck] ^M [filling in parms for ifconfig] ^M [filling in parms for route] ^M [ filling in parms for slattach] ^M [filling in parms for mount_nfs] ^M [filling i n parms for dhclient] ^M [filling in parms for arp] ^M [filling in parms for hostname] ^M [filling in parms for pccardc] ^M [filling in parms for pccardd] [filling in parms for usbd] ^M [filling in parms for usbdevs] ^M [generating boot_crunch.cache] ^M [generating boot_crunch.c] ^M [generating boot_crunch.m k] ^M [] ^MRun "make -f boot_crunch.mk objs exe" to buil d crunched binary. *** Error code 1 Stop in /usr/src/release. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 18:11: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C5A6B37B5AE for ; Wed, 7 Jun 2000 18:11:04 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA15265 for ; Wed, 7 Jun 2000 18:11:04 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 18:11:04 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Subject: mktemp() patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch was developed by Peter Jeremy and myself and increases the number of possible temporary filenames which can be generated by the mktemp() family, by more densely encoding the PID and using a larger set of characters to randomly pad with. Instead of using only alphabetic characters, the patch uses the following character set: 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ which is not believed to cause any problems with shells. The PID is also base-64 encoded into 3 characters (instead of the usual 5 for a base-10 representation) with an extra bit of randomness added in to fill the space. All up, for the usual case of a program calling mktemp() with 6 X's in the argument, this patch gives 74^3*2=810448 possibilities instead of 52 (assuming the PID is known), and the number increases exponentially thereafter with additional X's. It's not a solution to mktemp() since there's still a race condition, and for applications which only use 6 X's there's still only a relatively small number of possible filenames, but it does incrementally improve the situation by making it less likely for an attacker to guess the correct name (i.e. harder to win the race). Unless anyone has comments, I'd like to commit this to -current. Peter, I hope I've got the right version of the patch - any remaining bugs are likely to be my fault (although I've been running this here for a long time without problems). Kris Index: mktemp.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdio/mktemp.c,v retrieving revision 1.19 diff -u -r1.19 mktemp.c --- mktemp.c 2000/01/27 23:06:46 1.19 +++ mktemp.c 2000/06/08 00:57:17 @@ -52,6 +52,11 @@ static int _gettemp __P((char *, int *, int, int)); +static unsigned char base64[] = + ".#0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"; +static unsigned char padchar[] = +"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~"; + int mkstemps(path, slen) char *path; @@ -103,8 +108,10 @@ int slen; { register char *start, *trv, *suffp; + char *pad; struct stat sbuf; - int pid, rval; + int rval, n; + uint32_t pid; if (doopen && domkdir) { errno = EINVAL; @@ -120,20 +127,22 @@ errno = EINVAL; return (0); } - pid = getpid(); - while (*trv == 'X' && pid != 0) { - *trv-- = (pid % 10) + '0'; - pid /= 10; + + /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */ + pid = getpid() | (arc4random() & 0x00020000); + for (n = 0; *trv == 'X' && n < 3; n++) { + *trv-- = base64[pid & 0x3f]; + pid >>= 6; } - while (*trv == 'X') { - char c; + if (n < 3) { /* Not enough characters to encode PID */ + errno = EINVAL; + return(0); + } - pid = (arc4random() & 0xffff) % (26+26); - if (pid < 26) - c = pid + 'A'; - else - c = (pid - 26) + 'a'; - *trv-- = c; + /* Fill remaining space with random characters */ + while (*trv == 'X') { + pid = arc4random() % (sizeof(padchar) - 1); + *trv-- = padchar[pid]; } start = trv + 1; @@ -179,15 +188,11 @@ for (trv = start;;) { if (*trv == '\0' || trv == suffp) return(0); - if (*trv == 'Z') - *trv++ = 'a'; + pad = strchr(padchar, *trv); + if (pad == NULL || !*++pad) + *trv++ = padchar[0]; else { - if (isdigit((unsigned char)*trv)) - *trv = 'a'; - else if (*trv == 'z') /* inc from z to A */ - *trv = 'A'; - else - ++*trv; + *trv++ = *pad; break; } } -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 20:22:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id C891737B822 for ; Wed, 7 Jun 2000 20:22:04 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e583M1b08552 for ; Thu, 8 Jun 2000 13:22:01 +1000 (EST) Received: (from ggm@localhost) by asuncion.dstc.edu.au (8.9.3+Sun/8.8.8) id NAA09771 for current@FreeBSD.ORG; Thu, 8 Jun 2000 13:22:01 +1000 (EST) Date: Thu, 8 Jun 2000 13:22:01 +1000 (EST) From: George Michaelson Message-Id: <200006080322.NAA09771@asuncion.dstc.edu.au> To: current@FreeBSD.ORG Subject: heimdal/kerberosV pam module? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there doesn't appear to be recent mail in the searchable archives discussing the status of Heimdal, Kerberos V or pam. can somebody clueful give me some pointers please? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 21: 9:26 2000 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 4A5D437BF17; Wed, 7 Jun 2000 21:09:19 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12ztd5-000KMY-00; Thu, 08 Jun 2000 11:09:15 +0700 Date: Thu, 8 Jun 2000 11:09:15 +0700 (ALMST) From: Boris Popov To: Kris Kennaway Cc: current@freebsd.org Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Kris Kennaway wrote: > This patch was developed by Peter Jeremy and myself and increases the > number of possible temporary filenames which can be generated by the > mktemp() family, by more densely encoding the PID and using a larger set > of characters to randomly pad with. > > Instead of using only alphabetic characters, the patch uses the following > character set: > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ Symbols '=' and '+' are prohibited in some other filesystems. It is possible to avoid using them ? -- 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 Wed Jun 7 21:28: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 41CBB37B9DD; Wed, 7 Jun 2000 21:28:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA40106; Wed, 7 Jun 2000 21:28:02 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 21:28:02 -0700 (PDT) From: Kris Kennaway To: Boris Popov Cc: current@freebsd.org Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Boris Popov wrote: > > Instead of using only alphabetic characters, the patch uses the following > > character set: > > > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > > Symbols '=' and '+' are prohibited in some other filesystems. It > is possible to avoid using them ? Yes, but at the expense of weakening the number of possible random filenames :-( Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 21:36: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C5F8437B764; Wed, 7 Jun 2000 21:36:02 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id EAA25500; Thu, 8 Jun 2000 04:35:45 GMT (envelope-from doconnor@gsoft.com.au) 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: Date: Thu, 08 Jun 2000 14:05:45 +0930 (CST) From: "Daniel O'Connor" To: Kris Kennaway Subject: Re: mktemp() patch Cc: current@freebsd.org, Boris Popov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Jun-00 Kris Kennaway wrote: > On Thu, 8 Jun 2000, Boris Popov wrote: > > > > Instead of using only alphabetic characters, the patch uses the following > > > character set: > > > > > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > > > > Symbols '=' and '+' are prohibited in some other filesystems. It > > is possible to avoid using them ? > > Yes, but at the expense of weakening the number of possible random > filenames :-( IMHO the loss of 2 characters doesn't greatly reduce the number of possibilities, but it DOES greatly reduce the chance of an obscure error message appearing when you try and make a temp file on a brain dead FS. BTW.. For 5 character long temp names with + and = the number of possibile names is 2073071593, without it is 1804229351. (13% less) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 22:38:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id 3664D37B60C; Wed, 7 Jun 2000 22:38:05 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id e585cL621602; Thu, 8 Jun 2000 15:08:21 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 8 Jun 2000 15:08:59 +0930 Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id PAA26880; Thu, 8 Jun 2000 15:03:07 +0930 (CST) Received: from fuzz.dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id PAA17867; Thu, 8 Jun 2000 15:03:07 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.3/8.9.3) with ESMTP id PAA02216; Thu, 8 Jun 2000 15:03:08 +0930 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <393F3014.448D2A8C@dsto.defence.gov.au> Date: Thu, 08 Jun 2000 15:03:08 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: "David O'Brien" , current@freebsd.org, Matthew Thyer Subject: Re: Oddities with the new binutils References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> <20000607150244.A23666@cons.org> <20000607173734.A3002@cons.org> Content-Type: multipart/mixed; boundary="------------52C9B151EBB798F2EDC3A995" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------52C9B151EBB798F2EDC3A995 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "-O -pipe" is all I use for kernel and world builds. The kernel config file from my work box is attached. I have never built gcc from ports. I always use "config -r" when building kernels. I dont use modules as I have everything I need in my kernel including COMPAT_LINUX. And as I said before I removed all ports so that my testing is with XFree86, xaos and any supporting libraries all compiled after my world and kernel build. Did you do something similar ? I am using XFree86 3.3.6 on both machines. If it comes down to particular video cards, My work machine has: VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c09da (c00009da) VESA: S3 Incorporated. Trio64V+ My home machine has a "3dfx Velocity 100 AGP with 8MB SGRAM" which is detected as a Voodoo 3 by the VESA code. Martin Cracauer wrote: > > In <20000607150244.A23666@cons.org>, Martin Cracauer wrote: > > In <20000603232557.C67024@dragon.nuxi.com>, David O'Brien wrote: > > > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > > > Three issues: > > > > - floating point math doesn't seem to work properly: > > > > I don't have a -current machine I want to delete all ports from, but I > > have a -current from yesterday, I compiled xaos on it and libpng, > > which is the only dependency of xaos. That leave XFree as the only > > non-recompiled thing in the chain. > > > > Works fine. > > OK, now I am pissed. I also recompiled and restarted X11 to trace > this down, only to find that some stupid error in Xwrapper breaks > xinit and I had to roll my own xinit. > > Anyway, now I am running everything in the pipe compiled within the > last 24 hours on a fresh -current and xaos work just fine. > > > > It could also be poorly written ASM code in the things you were running. > > > The old Binutils let people write inconsistent and illegal ASM. > > > > xoas and png themself do not have assembler files. Xfree servers have > > some, but not in floating point related things. > > > > Where is the information that this is a floating-point problem from? > > > > Matthew, do you possibly use a custom gcc from /usr/local/bin and the > > native assembler or vice versa? > > Also, what level of optimization do you use? > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer/ > BSD User Group Hamburg, Germany http://www.bsdhh.org/ -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 --------------52C9B151EBB798F2EDC3A995 Content-Type: text/plain; charset=us-ascii; name="FUZZ" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="FUZZ" # $FreeBSD: FUZZ,v 5.5 2000/05/30 10:59:00 +09:30 thyerm Exp $ # based on $FreeBSD: src/sys/i386/conf/LINT,v 1.775 2000/05/22 15:00:40 dan Exp $ machine i386 ident "FUZZ" maxusers 64 options INCLUDE_CONFIG_FILE # Include this file in kernel cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options SHM_PHYS_BACKED options SHMALL=16384 options SHMMAXPGS=4096 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMSEG=50 options SHMMNI=64 options SEMMNI=32 options SEMMNS=128 # DEBUGGING OPTIONS #options DDB # Enable the kernel debugger options KTRACE # kernel tracing (SVR4 emul needs this) options UCONSOLE # Allow users to grab the console options USERCONFIG # boot -c editor options VISUAL_USERCONFIG # visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device #pseudo-device tun # Tunnel driver (user ppp requirement) # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT # FFS usable as root device options NFS # Network Filesystem options MFS # Memory Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process Filesystem options MSDOSFS # MSDOS Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # Allow FFS to use Softupdates tech options NCP # NetWare Core protocol options NWFS # NetWare filesystem options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options VFS_AIO # Real aio_* system calls # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty # Pseudo ttys pseudo-device vn # Vnode (turns a file into a device) pseudo-device bpf # Berkeley packet filter options MSGBUF_SIZE=40960 # Size of the kernel message buffer. Should be N * pagesize. options COMPAT_LINUX # Linux image activator in kernel (instead of module) # HARDWARE DEVICE CONFIGURATION device isa options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? device sc0 at isa? options MAXCONS=12 # Number of virtual consoles options SC_HISTORY_SIZE=400 # Number of history buffer lines options SC_DISABLE_REBOOT # Disable Ctrl-Alt-Del reboot options SC_NORM_ATTR="(FG_GREEN|BG_BLACK)" options SC_NORM_REV_ATTR="(FG_YELLOW|BG_GREEN)" options SC_KERNEL_CONS_ATTR="(FG_RED|BG_BLACK)" options SC_KERNEL_CONS_REV_ATTR="(FG_BLACK|BG_RED)" options VESA pseudo-device splash device npx0 at nexus? port IO_NPX flags 0x0 irq 13 options ATA_ENABLE_ATAPI_DMA device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device miibus device aha0 at isa? port 0x234 device ahc0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device pcm device sbc device pci device xl device apm0 at nexus? device smbus # SMBus system device intpm # PIIX4 interface device smb # User access to the SMBus device ppc0 at isa? irq 7 device ppbus device lpt options BOOTP options BOOTP_COMPAT # SCSI DEVICE CONFIGURATION options SCSI_DELAY=300 # Only wait 0.3 seconds for SCSI device scbus0 at aha0 device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus0 target 3 device da4 at scbus0 target 4 device da5 at scbus0 target 5 device da6 at scbus0 target 6 device scbus1 at ahc0 device da10 at scbus1 target 0 device da11 at scbus1 target 1 device da12 at scbus1 target 2 device da13 at scbus1 target 3 device da14 at scbus1 target 4 device da15 at scbus1 target 5 device da16 at scbus1 target 6 device da18 at scbus1 target 8 device da19 at scbus1 target 9 device da20 at scbus1 target 10 device da21 at scbus1 target 11 device da22 at scbus1 target 12 device da23 at scbus1 target 13 device da24 at scbus1 target 14 device da25 at scbus1 target 15 --------------52C9B151EBB798F2EDC3A995-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 22:52:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 13BB437B60C; Wed, 7 Jun 2000 22:52:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA68971; Wed, 7 Jun 2000 22:52:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 22:52:29 -0700 (PDT) From: Kris Kennaway To: George Michaelson Cc: current@FreeBSD.ORG Subject: Re: heimdal/kerberosV pam module? In-Reply-To: <200006080322.NAA09771@asuncion.dstc.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, George Michaelson wrote: > there doesn't appear to be recent mail in the searchable archives > discussing the status of Heimdal, Kerberos V or pam. > > can somebody clueful give me some pointers please? Pointers on? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23: 7:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EC89137B764; Wed, 7 Jun 2000 23:07:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA03778; Wed, 7 Jun 2000 23:06:55 -0700 (PDT) (envelope-from dillon) Date: Wed, 7 Jun 2000 23:06:55 -0700 (PDT) From: Matthew Dillon Message-Id: <200006080606.XAA03778@apollo.backplane.com> To: Boris Popov Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> Instead of using only alphabetic characters, the patch uses the following :> character set: :> :> 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ : : Symbols '=' and '+' are prohibited in some other filesystems. It :is possible to avoid using them ? : :-- :Boris Popov :http://www.butya.kz/~bp/ It would be a good idea to avoid any punctuation. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23: 7:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B19D37BAA0; Wed, 7 Jun 2000 23:07:34 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e5867Ub19406; Thu, 8 Jun 2000 16:07:30 +1000 (EST) X-Mailer: exmh version 2.1.0 09/18/1999 To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: heimdal/kerberosV pam module? In-Reply-To: Message from Kris Kennaway of "Wed, 07 Jun 2000 22:52:29 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jun 2000 16:07:29 +1000 Message-ID: <10076.960444449@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, George Michaelson wrote: > there doesn't appear to be recent mail in the searchable archives > discussing the status of Heimdal, Kerberos V or pam. > > can somebody clueful give me some pointers please? Pointers on? Pointers on the status of Heimdal, Kerberos V and pam. What I infer is: Heimdal is still 'experimental' Kerberos V is mostly back-links to the imported heimdal pam is stuck at Kerberos_IV for the time being /etc/services is 'almost' ok for Kerberos V the port in /usr/ports/security/heimdal is pretty well ok but runs from /usr/local, and doesn't use exactly the same formats for data: you can do some things off the /usr/src/ installed code but some others don't work. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:13:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by hub.freebsd.org (Postfix) with ESMTP id E8B1337C05D for ; Wed, 7 Jun 2000 23:13:31 -0700 (PDT) (envelope-from bc-freebsd@vicious.dropbear.id.au) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id QAA04218; Thu, 8 Jun 2000 16:12:41 +1000 (EST) Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1) id xma004211; Thu, 8 Jun 00 16:12:25 +1000 Received: from julubu.staff.apnic.net (julubu.staff.apnic.net [192.168.1.37]) by hadrian.staff.apnic.net (8.9.3/8.9.3) with ESMTP id PAA22000; Thu, 8 Jun 2000 15:49:01 +1000 (EST) Date: Thu, 8 Jun 2000 16:12:23 +1000 (EST) From: Bruce Campbell X-Sender: bc@julubu.staff.apnic.net To: "Daniel O'Connor" Cc: current@freebsd.org Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Daniel O'Connor wrote: doconn> On 08-Jun-00 Kris Kennaway wrote: doconn> > On Thu, 8 Jun 2000, Boris Popov wrote: doconn> > doconn> > > > Instead of using only alphabetic characters, the patch uses the following doconn> > > > character set: doconn> > > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ doconn> > > Symbols '=' and '+' are prohibited in some other filesystems. It doconn> > > is possible to avoid using them ? doconn> > Yes, but at the expense of weakening the number of possible random doconn> > filenames :-( doconn> doconn> IMHO the loss of 2 characters doesn't greatly reduce the number of doconn> possibilities, but it DOES greatly reduce the chance of an obscure error doconn> message appearing when you try and make a temp file on a brain dead FS. mkstemp() actually creates the file if possible. If the creation of the file fails (and not due to race condition), retry the algorithm without 'suspect' characters. That way, you don't lose out on the extra 13% of possibilities when running on a 'real' filesystem ;) Since mktemp() only returns the suggested filename, you lose, unless mktemp() starts examining the mounted filesystems for known character no-nos. Its a pity that one cannot pass the allowable list of characters to mktemp() and related functions. --==-- Bruce. Common Sense, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:24:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 3261B37C02E; Wed, 7 Jun 2000 23:24:50 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca41-94.ix.netcom.com [209.111.208.94]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id CAA02722; Thu, 8 Jun 2000 02:24:18 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id XAA23012; Wed, 7 Jun 2000 23:23:47 -0700 (PDT) To: Maxim Sobolev Cc: "Andrey A. Chernov" , current@FreeBSD.org Subject: Re: ls References: <20000606172534.A448@nagual.pp.ru> <393D05BF.3A373254@FreeBSD.org> <20000606181541.A40578@nagual.pp.ru> <393D0881.7BE47D6A@FreeBSD.org> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 07 Jun 2000 23:23:39 -0700 In-Reply-To: Maxim Sobolev's message of "Tue, 06 Jun 2000 17:19:46 +0300" Message-ID: Lines: 9 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Maxim Sobolev * Probably it would be nice if colorls from the ports will be * synchronized with one in /usr/src, so users of 4.0 and downward * could benefit from your efforts as well. I was going to do exactly that. (I was waiting for Andrey to finish.) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:29:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 0E42D37B835; Wed, 7 Jun 2000 23:29:01 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA04362; Thu, 8 Jun 2000 08:29:07 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006080629.IAA04362@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch References: In-Reply-To: ; from Kris Kennaway "Wed, 07 Jun 2000 18:11:04 MST." Date: Thu, 08 Jun 2000 08:29:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > + /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */ > + pid = getpid() | (arc4random() & 0x00020000); What is the purpose of this? It looks hugely wasteful to me. If you really need a single random bit, it is not good to waste a block of hard-gained gryptographic randomness; can you not use a pseudo-random bit-generator? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:35:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 96EFA37C0A6 for ; Wed, 7 Jun 2000 23:35:10 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA04413; Thu, 8 Jun 2000 08:35:02 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006080635.IAA04413@grimreaper.grondar.za> To: George Michaelson Cc: current@FreeBSD.ORG Subject: Re: heimdal/kerberosV pam module? References: <10076.960444449@dstc.edu.au> In-Reply-To: <10076.960444449@dstc.edu.au> ; from George Michaelson "Thu, 08 Jun 2000 16:07:29 +1000." Date: Thu, 08 Jun 2000 08:35:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Kerberos is my baby. > What I infer is: > > Heimdal is still 'experimental' Correct. > Kerberos V is mostly back-links to the imported heimdal > pam is stuck at Kerberos_IV for the time being Correct. Correct. Care to write a K5/Heimdal PAM? > /etc/services is 'almost' ok for Kerberos V Patches? > the port in /usr/ports/security/heimdal is pretty well ok but > runs from /usr/local, and doesn't use exactly the same formats > for data: you can do some things off the /usr/src/ installed code > but some others don't work. I intend to update the mainstream stuff to the latest Heimdal soonish. As for differences; patches or pointers, please? :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:35:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr1003333-a.crdva1.bc.home.com (cr1003333-a.crdva1.bc.wave.home.com [24.113.51.240]) by hub.freebsd.org (Postfix) with ESMTP id B091C37C0F8 for ; Wed, 7 Jun 2000 23:35:20 -0700 (PDT) (envelope-from pangolin@home.com) Received: from cr1003333-a.crdva1.bc.wave.home.com. (localhost [127.0.0.1]) by cr1003333-a.crdva1.bc.home.com (8.9.3/8.9.3) with ESMTP id XAA06907 for ; Wed, 7 Jun 2000 23:35:01 -0700 (PDT) (envelope-from pangolin@home.com) Message-Id: <200006080635.XAA06907@cr1003333-a.crdva1.bc.home.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 07 Jun 2000 23:35:01 -0700 (PDT) Reply-To: Jonathan Hanna Organization: Pangolin Systems From: Jonathan Hanna To: freebsd-current@freebsd.org Subject: Strange rpc.statd and mount_nfs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running a fairly recent current and noticed my swap seemed a little overused. bash-2.02$ uname -a FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun May 14 11:50:20 PDT 2000 jh@roller.pangolin-sy stems.com:/home/src/sys/compile/ROLLER i386 bash-2.02$ uptime 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 ps shows: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.40 (swapper) 0 1 0 0 10 0 524 72 wait ILs ?? 0:00.06 /sbin/init -- 0 2 0 0 -18 0 0 0 psleep DL ?? 0:50.94 (pagedaemon) 0 3 0 3 18 0 0 0 psleep DL ?? 0:00.47 (vmdaemon) 0 4 0 0 -18 0 0 0 psleep DL ?? 0:05.69 (bufdaemon) 0 5 0 0 18 0 0 0 syncer DL ?? 0:56.96 (syncer) 0 32 1 34 18 0 208 0 pause IWs ?? 0:00.00 adjkerntz -i 0 191 1 0 2 0 888 236 select Ss ?? 0:01.77 syslogd -s 0 194 1 0 2 -12 1224 328 select S To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 7 23:44: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B0A3E37BAE2; Wed, 7 Jun 2000 23:44:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA86883; Wed, 7 Jun 2000 23:44:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 23:44:02 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: <200006080629.IAA04362@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Mark Murray wrote: > Hi > > > + /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */ > > + pid = getpid() | (arc4random() & 0x00020000); > > What is the purpose of this? It looks hugely wasteful to me. If you > really need a single random bit, it is not good to waste a block of > hard-gained gryptographic randomness; can you not use a pseudo-random > bit-generator? arc4random() does not consume entropy except the first time it is called and when explicitly reseeded through arc4random_stir(). Apart from that it's a deterministic function (the arc4 stream cipher), but it's still a reasonably good cryptographic PRNG because arc4 is a cryptographically strong algorithm. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 0:28: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id EE48E37BEC6; Thu, 8 Jun 2000 00:27:41 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id e587Rw628103; Thu, 8 Jun 2000 16:57:58 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 8 Jun 2000 16:58:44 +0930 Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id QAA26010; Thu, 8 Jun 2000 16:54:36 +0930 (CST) Received: from fuzz.dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id QAA09325; Thu, 8 Jun 2000 16:54:36 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.3/8.9.3) with ESMTP id QAA02370; Thu, 8 Jun 2000 16:54:38 +0930 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <393F4A36.2C4D580B@dsto.defence.gov.au> Date: Thu, 08 Jun 2000 16:54:38 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: "David O'Brien" , current@freebsd.org, Matthew Thyer Subject: Re: Oddities with the new binutils References: <39375E5D.A967720F@dsto.defence.gov.au> <20000603232557.C67024@dragon.nuxi.com> <20000607150244.A23666@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It may not be FP itself. In fact I have seen some other strange graphic corruption at home when running xplanet in the background and xanim. When the planet turns, the top 20 or so rows of the root window get corrupted with some of the image of the currently playing animation in xanim. I haven't mentioned this yet because I've only been running xplanet since post-binutils so I cant compare it with previous behaviour. It would appear to be an Xserver problem. The fact remains that I am seeing the xaos problem on two machines that are both using the SVGA server from XFree86 3.3.6 but with different video cards (one's a PII-266 with an S3 Trio64V+, the other a Celeron 300a with a 3dfx Velocity 100 AGP). I need to do more testing.... I have another -CURRENT machine with a recent XFree86 from before the new binutils so I will try displaying xaos on that Xserver. Sorry for the limited time I can spend on debugging this... I dont get any chance at work and the wife and kids limit my access to the home machine that has my source until after the kids go to bed. Martin Cracauer wrote: > > In <20000603232557.C67024@dragon.nuxi.com>, David O'Brien wrote: > > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > > Three issues: > > > - floating point math doesn't seem to work properly: > > I don't have a -current machine I want to delete all ports from, but I > have a -current from yesterday, I compiled xaos on it and libpng, > which is the only dependency of xaos. That leave XFree as the only > non-recompiled thing in the chain. > > Works fine. > > > It could also be poorly written ASM code in the things you were running. > > The old Binutils let people write inconsistent and illegal ASM. > > xoas and png themself do not have assembler files. Xfree servers have > some, but not in floating point related things. > > Where is the information that this is a floating-point problem from? > > Matthew, do you possibly use a custom gcc from /usr/local/bin and the > native assembler or vice versa? > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer/ > BSD User Group Hamburg, Germany http://www.bsdhh.org/ -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 1:24: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from ux1.schottle.net (ux1.schottle.net [199.88.145.11]) by hub.freebsd.org (Postfix) with ESMTP id 4573537BFBF for ; Thu, 8 Jun 2000 01:23:56 -0700 (PDT) (envelope-from tom@schottle.net) Received: from schottle.net (ntw1.internetct.com [199.88.145.110]) by ux1.schottle.net (8.9.3/8.9.3) with ESMTP id EAA15873; Thu, 8 Jun 2000 04:23:52 -0400 (EDT) (envelope-from tom@schottle.net) Message-ID: <393F5818.B54D31F2@schottle.net> Date: Thu, 08 Jun 2000 04:23:52 -0400 From: Tom Schottle X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Hanna Cc: freebsd-current@FreeBSD.ORG Subject: Re: Strange rpc.statd and mount_nfs References: <200006080635.XAA06907@cr1003333-a.crdva1.bc.home.com> 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 the same problem with 4.0-STABLE, cvsup'ed June 2. I just turned rpc.statd off in /etc/rc.conf. Tom Schottle tom@schottle.net Jonathan Hanna wrote: > > I am running a fairly recent current and noticed my swap seemed > a little overused. > > bash-2.02$ uname -a > FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun May 14 11:50:20 PDT 2000 jh@roller.pangolin-sy > stems.com:/home/src/sys/compile/ROLLER i386 > bash-2.02$ uptime > 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 > > ps shows: > > 0 212 1 29 2 0 263036 0 select IWs ?? 0:00.00 rpc.statd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 1:57:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by hub.freebsd.org (Postfix) with ESMTP id 0A32B37BB0D; Thu, 8 Jun 2000 01:57:24 -0700 (PDT) (envelope-from johan@ockle.dev.nanoteq.co.za) Received: (from johan@localhost) by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id LAA67293; Thu, 8 Jun 2000 11:04:01 +0200 (SAST) (envelope-from johan) 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: Thu, 08 Jun 2000 11:04:01 +0200 (SAST) Organization: Nanoteq From: Johan Kruger To: freebsd-hackers@freebsd.org, FreeBSD Current Subject: syslog do not want to remote log Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 2 machine's : A = Amnesiac B = ockle I want to remote log to ockle from Amnesiac Amnesiac : /etc/syslog.conf *.emerg * *.crit /var/log/crit *.err /var/log/errors *.info /var/log/all *.notice;kern.debug;lpr.info;mail.crit;news.err @ockle I started syslogd on Amnesiac with : syslogd -d and i get Logging to CONSOLE /dev/console 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 X FILE: /var/log/crit 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/log/errors 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 X FILE: /var/log/all 7 5 2 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X UNUSED: logmsg: pri 56, flags 4, from Amnesiac, msg syslogd: restart Logging to FILE /var/log/all syslogd: restarted readfds = 0x38 NOTICE THE UNUSED ???? Amnesiac do not want to use ockle - i tried specifying the i.p. of ockle but to no avail. ockle is in the hosts file on Amnesiac, a dns is present and specified in /etc/resolve.conf and it works. On ockle i started syslogd with -a and the i.p. of Amnesiac. But the problem is not here ( on ockle ), i first have to get syslogd on Amnesiac not to report UNUSED in debug mode ?? Any suggestions ?? ---------------------------------- E-Mail: Johan Kruger Date: 08-Jun-00 Time: 10:56:22 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 3:37:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 5155637BB3B for ; Thu, 8 Jun 2000 03:37:08 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from neutron.cichlids.com (p3E9C116C.dip0.t-ipconnect.de [62.156.17.108]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id MAA30052 for ; Thu, 8 Jun 2000 12:37:06 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 2CEC5AC30 for ; Thu, 8 Jun 2000 12:37:01 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 2D16814A6E; Thu, 8 Jun 2000 12:37:00 +0200 (CEST) Date: Thu, 8 Jun 2000 12:37:00 +0200 From: Alexander Langer To: current@freebsd.org Subject: inetd with -R -1 patch? Message-ID: <20000608123700.A22155@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! What about that patch to let one use unlimited numbers of connections? The standard is still 256, but if one really wants that... Index: inetd.c =================================================================== RCS file: /usr/home/ncvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.81 diff -u -r1.81 inetd.c --- inetd.c 2000/04/02 16:11:14 1.81 +++ inetd.c 2000/06/08 10:33:42 @@ -191,7 +191,9 @@ < 0 = no limit */ #endif +#ifndef TOOMANY #define TOOMANY 256 /* don't start more than TOOMANY */ +#endif #define CNT_INTVL 60 /* servers in CNT_INTVL sec. */ #define RETRYTIME (60*10) /* retry after bind or server fail */ #define MAX_MAXCHLD 32767 /* max allowable max children */ @@ -590,7 +592,7 @@ if (dofork) { if (sep->se_count++ == 0) (void)gettimeofday(&sep->se_time, (struct timezone *)NULL); - else if (sep->se_count >= toomany) { + else if (toomany >= 0 && sep->se_count >= toomany) { struct timeval now; (void)gettimeofday(&now, (struct timezone *)NULL); Alex -- This is a FreeBSD advocacy ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 3:46:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id CB37D37BBA8; Thu, 8 Jun 2000 03:46:07 -0700 (PDT) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id MAA84635; Thu, 8 Jun 2000 12:46:05 +0200 (CEST) (envelope-from asmodai) Date: Thu, 8 Jun 2000 12:46:05 +0200 From: Jeroen Ruigrok van der Werven To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000608124605.G82993@lucifer.bart.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@FreeBSD.ORG on Wed, Jun 07, 2000 at 06:11:04PM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000608 03:12], Kris Kennaway (kris@FreeBSD.ORG) wrote: >Instead of using only alphabetic characters, the patch uses the following >character set: > >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > >which is not believed to cause any problems with shells. The PID is also Some shells parse # as a deletion character if memory serves me right. I think I noticed this behaviour when I started using zsh a few weeks ago after ksh. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl ...fools rush in where Angels fear to tread. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 3:52:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 384C737B867; Thu, 8 Jun 2000 03:52:01 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from trillian.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id F237B190A1; Thu, 8 Jun 2000 12:51:56 +0200 (CEST) Received: by trillian.enst.fr (Postfix, from userid 1000) id D681A259; Thu, 8 Jun 2000 12:51:54 +0200 (CEST) Date: Thu, 8 Jun 2000 12:51:53 +0200 To: Jeroen Ruigrok van der Werven Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000608124605.G82993@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000608124605.G82993@lucifer.bart.nl>; from jruigrok@via-net-works.nl on Thu, Jun 08, 2000 at 12:46:05PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8/06, Jeroen Ruigrok van der Werven wrote: | -On [20000608 03:12], Kris Kennaway (kris@FreeBSD.ORG) wrote: | >Instead of using only alphabetic characters, the patch uses the following | >character set: | > | >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ | > | >which is not believed to cause any problems with shells. The PID is also | | Some shells parse # as a deletion character if memory serves me right. | I think I noticed this behaviour when I started using zsh a few weeks | ago after ksh. Also ^ is used for substitutions in many shells (as in ^faulty^ok). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 4:51: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8266937B97D for ; Thu, 8 Jun 2000 04:50:55 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 5199 invoked from network); 8 Jun 2000 11:50:51 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 8 Jun 2000 11:50:51 -0000 Date: Thu, 8 Jun 2000 21:50:48 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Kris Kennaway wrote: > Instead of using only alphabetic characters, the patch uses the following > character set: > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > > which is not believed to cause any problems with shells. The PID is also I think it should use only letters and digits. For 6 X's, this gives a namespace of size 52^6 provided the namespace is not gratuitously (?) reduced using the pid. > Index: mktemp.c > =================================================================== > RCS file: /home/ncvs/src/lib/libc/stdio/mktemp.c,v > retrieving revision 1.19 > diff -u -r1.19 mktemp.c > --- mktemp.c 2000/01/27 23:06:46 1.19 > +++ mktemp.c 2000/06/08 00:57:17 > ... > @@ -120,20 +127,22 @@ > errno = EINVAL; > return (0); > } > - pid = getpid(); > - while (*trv == 'X' && pid != 0) { > - *trv-- = (pid % 10) + '0'; > - pid /= 10; > + > + /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */ > + pid = getpid() | (arc4random() & 0x00020000); > + for (n = 0; *trv == 'X' && n < 3; n++) { > + *trv-- = base64[pid & 0x3f]; > + pid >>= 6; > } Why are we still using the pid? It is highly non-random. It was originally used to ensure a separate starting point for separate processes, and because there was no truly random RNG. Now, arc4random() is hopefully random enough to give a good starting point by itself. It is a feature (a consequence of true randomness) that it may give identical starting points for separate processes. > @@ -179,15 +188,11 @@ > for (trv = start;;) { > if (*trv == '\0' || trv == suffp) ^^^^^^^ normal style > return(0); > - if (*trv == 'Z') > - *trv++ = 'a'; > + pad = strchr(padchar, *trv); > + if (pad == NULL || !*++pad) ^ style bug > + *trv++ = padchar[0]; > else { > - if (isdigit((unsigned char)*trv)) > - *trv = 'a'; > - else if (*trv == 'z') /* inc from z to A */ > - *trv = 'A'; > - else > - ++*trv; > + *trv++ = *pad; > break; > } > } This finishes bogotifying the comment before the for loop: /* tricky little algorithm for backward compatibility */ Don't forget to remove it :-). The algorithm is now a simple increment in base strlen(padchar). Perhaps it should use a random increment initially if there aren't enough X's to provide enough randomness in the starting point, or always. All cases do slow filesystem syscalls, so it might be cheap enough to randomize the whole path every time. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 6:48:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id DD71937BFC6; Thu, 8 Jun 2000 06:48:42 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id PAA03955; Thu, 8 Jun 2000 15:48:17 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200006081348.PAA03955@info.iet.unipi.it> Subject: HEADS UP- WF2Q and RED now available in -current To: net@freebsd.org Date: Thu, 8 Jun 2000 15:48:17 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL61 (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 [Bcc to -current and -isp as relevant for them as well] Hi, as the subject says, i have just committed some new code to dummynet (and related hooks and documentation for ipfw) to implement RED (thanks to Gianluca Iannaccone) and a variant of Weighted Fair Queueing called WF2Q+ I have tested it locally and would like to have this code in -STABLE and hopefully -RELENG_3 before 3.5 if time permits. Read the manpage for more details. An updated PicoBSD image should appear soon at http://www.iet.unipi.it/~luigi/ip_dummynet/ In order to test WFQ you can try the following: ipfw add 100 queue 10 icmp from any to any out ipfw add 200 queue 11 ip from any to any out ipfw queue 10 config weight 1 pipe 2 ipfw queue 11 config weight 10 pipe 2 mask all ipfw pipe 2 config bw 200Kbit/s and then see how a ping -f to the outside will not disturb other IP traffic, while still being able to use the full bandwidth configured for the pipe. Please email me if you make use of this feature, or you find bugs, etc. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 8:18:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (p3E9B8F1A.dip.t-dialin.net [62.155.143.26]) by hub.freebsd.org (Postfix) with ESMTP id 174FD37B7C0 for ; Thu, 8 Jun 2000 08:18:11 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id RAA00635; Thu, 8 Jun 2000 17:09:55 +0200 (CEST) Message-Id: <200006081509.RAA00635@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Schottle Cc: Jonathan Hanna , freebsd-current@FreeBSD.ORG Subject: Re: Strange rpc.statd and mount_nfs Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 08 Jun 2000 04:23:52 EDT." <393F5818.B54D31F2@schottle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jun 2000 17:09:55 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Schottle writes: >I have the same problem with 4.0-STABLE, cvsup'ed June 2. I just >turned rpc.statd off in /etc/rc.conf. > >Tom Schottle >tom@schottle.net > > >Jonathan Hanna wrote: >> >> I am running a fairly recent current and noticed my swap seemed >> a little overused. >> >> bash-2.02$ uname -a >> FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun > May 14 11:50:20 PDT 2000 jh@roller.pangolin-sy >> stems.com:/home/src/sys/compile/ROLLER i386 >> bash-2.02$ uptime >> 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 >> >> ps shows: >> >> 0 212 1 29 2 0 263036 0 select IWs ?? 0:00.00 rpc.stat >d > > This question has been correctly answered in the past. Look in the mail archives. --- Gary Jennejohn / garyj@muc.de gj@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 Jun 8 8:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 173CF37C048; Thu, 8 Jun 2000 08:35:32 -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 e58FZGO21212; Thu, 8 Jun 2000 08:35:16 -0700 (PDT) Date: Thu, 8 Jun 2000 08:35:16 -0700 (PDT) From: Doug White To: Johan Kruger Cc: freebsd-hackers@FreeBSD.ORG, FreeBSD Current Subject: Re: syslog do not want to remote log In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Johan Kruger wrote: > I started syslogd on Amnesiac with : syslogd -d and i get > > Logging to CONSOLE /dev/console > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: > 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 X FILE: /var/log/crit > 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/log/errors > 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 X FILE: /var/log/all > 7 5 2 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X UNUSED: > logmsg: pri 56, flags 4, from Amnesiac, msg syslogd: restart > Logging to FILE /var/log/all > syslogd: restarted > readfds = 0x38 > > NOTICE THE UNUSED ???? > Amnesiac do not want to use ockle - i tried specifying the i.p. of ockle > but to no avail. ockle is in the hosts file on Amnesiac, a dns is present > and specified in /etc/resolve.conf and it works. Try setting the hostname of the machine first -- syslog might be having trouble figuring out which interface touse. 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 Thu Jun 8 9:48:49 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 9C62737C096; Thu, 8 Jun 2000 09:48:46 -0700 (PDT) Date: Thu, 8 Jun 2000 09:48:46 -0700 From: "Andrey A. Chernov" To: Bruce Evans Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000608094846.A53442@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from bde@zeta.org.au on Thu, Jun 08, 2000 at 09:50:48PM +1000 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 08, 2000 at 09:50:48PM +1000, Bruce Evans wrote: > I think it should use only letters and digits. For 6 X's, this gives a > namespace of size 52^6 provided the namespace is not gratuitously (?) > reduced using the pid. Best variant will be to keep the name MSDOS FS 8.3 name safe. > Why are we still using the pid? It is highly non-random. It was originally I agree. We must not use getpid() since we have arc4random(). -- 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 Jun 8 10:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id E192A37B893; Thu, 8 Jun 2000 10:24:03 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id TAA00705; Thu, 8 Jun 2000 19:24:11 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006081724.TAA00705@grimreaper.grondar.za> To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch References: In-Reply-To: ; from Kris Kennaway "Wed, 07 Jun 2000 23:44:02 MST." Date: Thu, 08 Jun 2000 19:24:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is the purpose of this? It looks hugely wasteful to me. If you > > really need a single random bit, it is not good to waste a block of > > hard-gained gryptographic randomness; can you not use a pseudo-random > > bit-generator? > > arc4random() does not consume entropy except the first time it is called > and when explicitly reseeded through arc4random_stir(). Apart from that > it's a deterministic function (the arc4 stream cipher), but it's still a > reasonably good cryptographic PRNG because arc4 is a cryptographically > strong algorithm. But I repeat myself; are you still intending to use cryptographic security for one bit? What does that buy you? An attacker will laugh at the waste of resources that went into a coin-flip :-). Much better is to use something cheaper like time-of-day XOR 1 << whatever. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 11:13: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id E9FED37BC4D; Thu, 8 Jun 2000 11:12:50 -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.9.3/8.9.3) with ESMTP id OAA562572; Thu, 8 Jun 2000 14:11:23 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> References: <20000608124605.G82993@lucifer.bart.nl> <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> Date: Thu, 8 Jun 2000 14:11:48 -0400 To: Samuel Tardieu , Jeroen Ruigrok van der Werven From: Garance A Drosihn Subject: Re: mktemp() patch Cc: Kris Kennaway , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:51 PM +0200 6/8/00, Samuel Tardieu wrote: >On 8/06, Jeroen Ruigrok van der Werven wrote: >| -On [20000608 03:12], Kris Kennaway (kris@FreeBSD.ORG) wrote: >| >Instead of using only alphabetic characters, the patch uses the following >| >character set: >| > >| >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ >| > >| > which is not believed to cause any problems with shells. >| >| Some shells parse # as a deletion character if memory serves me right. >| I think I noticed this behaviour when I started using zsh a few weeks >| ago after ksh. > >Also ^ is used for substitutions in many shells (as in ^faulty^ok). I believe bash requires some kind of whitespace character (blank, tab, newline) in front of the '#' before it will treat it as the comment character. I am not sure about other shells (people who use other shells might want to check). Similarly, I believe '^' is used for substitutions ONLY if it is the first character in the line. Ie, 'echo hello^to^you' does not do any substitution on the previous line. Since we know these characters are only being used in a filename, and NOT as the first character of a filename, then we should not have trouble using them. I must admit I am not as comfortable using '+=,', and I think one of '@' or ':' should go, just in case the file is used in some context that reads blah@blah:blah as userid@hostname:fname I would probably drop the '@', but if there is some other reason to drop ':' then the '@' could probably stay. At the same time, I do like to see the set expanded as much as possible, without causing any problems. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 11:33:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02-svc.server.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 9DF3E37C0B0; Thu, 8 Jun 2000 11:33:36 -0700 (PDT) (envelope-from topper.harley@ntlworld.com) Received: from conax ([62.253.84.15]) by mta02-svc.server.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20000608193311.WXWW10065.mta02-svc.server.ntlworld.com@conax>; Thu, 8 Jun 2000 19:33:11 +0000 From: "Steve" To: "Listar@Isc. Org" , "Freebsd-Net" , "Freebsd-Net" , "FreeBSD-ISP" , "Freebsd-ISP" , "Freebsd-Hackers" , "Freebsd-Current" , "Cvs-All" , "Current" , "Comp-Protocols-Dns-Bind" , "Bind-Users-Bounce" , "Bind-Users" Subject: Stupid Bonzi program Date: Thu, 8 Jun 2000 19:32:53 +0100 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.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please accept my sincere apologies for sending this mail, I at least thought that the program would give a conformation of the addresses sent to. Apologies Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 11:33:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02-svc.server.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 9DF3E37C0B0; Thu, 8 Jun 2000 11:33:36 -0700 (PDT) (envelope-from topper.harley@ntlworld.com) Received: from conax ([62.253.84.15]) by mta02-svc.server.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20000608193311.WXWW10065.mta02-svc.server.ntlworld.com@conax>; Thu, 8 Jun 2000 19:33:11 +0000 From: "Steve" To: "Listar@Isc. Org" , "Freebsd-Net" , "Freebsd-Net" , "FreeBSD-ISP" , "Freebsd-ISP" , "Freebsd-Hackers" , "Freebsd-Current" , "Cvs-All" , "Current" , "Comp-Protocols-Dns-Bind" , "Bind-Users-Bounce" , "Bind-Users" Subject: Stupid Bonzi program Date: Thu, 8 Jun 2000 19:32:53 +0100 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.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please accept my sincere apologies for sending this mail, I at least thought that the program would give a conformation of the addresses sent to. Apologies Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 12:23: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 9584F37C121 for ; Thu, 8 Jun 2000 12:22:59 -0700 (PDT) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id E949EDDB8A for ; Thu, 8 Jun 2000 15:21:17 -0400 (EDT) Message-ID: <393FF36A.8B62FB66@infolibria.com> Date: Thu, 08 Jun 2000 15:26:34 -0400 From: John LoVerso Organization: InfoLibria X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000608124605.G82993@lucifer.bart.nl> <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | >which is not believed to cause any problems with shells. The PID is also > | Some shells parse # as a deletion character if memory serves me right. > Also ^ is used for substitutions in many shells (as in ^faulty^ok). Why would you care if some shell used the a character in some special way? In general, you are not going to be typing the filename generated by mktemp() et al. And when you do, use the shell's strong quote (ala ') to escape such characters. (before someone mentions, almost none of these restrictions apply to scripts) > Symbols '=' and '+' are prohibited in some other filesystems. Specific examples of filesystems supported by FreeBSD and likely used by programs invoking mktemp(), please! (I'm not sure that the NetWare filesystem counts!) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 12:48:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 681F337B955 for ; Thu, 8 Jun 2000 12:48:26 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id OAA26753; Thu, 8 Jun 2000 14:48:15 -0500 (CDT) (envelope-from dan) Date: Thu, 8 Jun 2000 14:48:15 -0500 From: Dan Nelson To: John LoVerso Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000608144815.A26076@dan.emsphone.com> References: <20000608124605.G82993@lucifer.bart.nl> <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> <393FF36A.8B62FB66@infolibria.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393FF36A.8B62FB66@infolibria.com>; from "John LoVerso" on Thu Jun 8 15:26:34 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 08), John LoVerso said: > > Symbols '=' and '+' are prohibited in some other filesystems. > > Specific examples of filesystems supported by FreeBSD and likely used > by programs invoking mktemp(), please! (I'm not sure that the > NetWare filesystem counts!) But why wouldn't it count? If I mount a Netware volume and decide to edit a file with an editor that creates a temporary filename for some reason, I'd like it to work. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 13:45:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from brs.com.br (brs.com.br [192.41.24.32]) by hub.freebsd.org (Postfix) with ESMTP id 455A337C02F for ; Thu, 8 Jun 2000 13:45:27 -0700 (PDT) (envelope-from email@carlos.eti.br) Received: from fraga.carlos.eti.br ([200.241.0.6]) by brs.com.br (8.8.5) id SAA12716; Thu, 8 Jun 2000 18:45:21 -0200 (GMT+2) X-Authentication-Warning: brs.com.br: Host [200.241.0.6] claimed to be fraga.carlos.eti.br Message-Id: <4.3.2.7.2.20000608174626.00b305f0@carlos.eti.br> X-Sender: email@carlos.eti.br X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 08 Jun 2000 17:46:36 -0300 To: freebsd-current@FreeBSD.ORG From: Carlos Fraga Subject: Re: It's worth ! 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 A site that pays you to receive some e-mails. No more than that. Nothing to buy, just to receive the e-mail and click on the link to visit the site. Don't you believe it exists ? Yes, it exists. And I have already received a US$ 50,00 check. Will you say that you don't want some money ? It's up to you to subscribe and start receiving e-mails and money ! Follow the link: http://www.sendmoreinfo.com/id/871883 See you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 17:11:53 2000 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 EBE3737C150 for ; Thu, 8 Jun 2000 17:11:46 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 130COh-000MUJ-00; Fri, 09 Jun 2000 07:11:39 +0700 Date: Fri, 9 Jun 2000 07:11:39 +0700 (ALMST) From: Boris Popov To: John LoVerso Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: <393FF36A.8B62FB66@infolibria.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, 8 Jun 2000, John LoVerso wrote: > > Symbols '=' and '+' are prohibited in some other filesystems. > > Specific examples of filesystems supported by FreeBSD and likely used by > programs invoking mktemp(), please! (I'm not sure that the NetWare filesystem > counts!) Count both, nwfs and smbfs, because any program can attempt to create temporary file on these filesystems. File with an invalid file name will be rejected, and this will cost an additional lookup operation(s). -- 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 Thu Jun 8 18:35: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id F085437C0E5; Thu, 8 Jun 2000 18:34:54 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:7XidcUajliibfpqSo8DW5jjQiZMstYEf@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id KAA14770; Fri, 9 Jun 2000 10:34:52 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:qhCi9UzPvqUZ+lC6KjHMWiZgml6DzriB@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id KAA27612; Fri, 9 Jun 2000 10:41:40 +0900 (JST) Message-Id: <200006090141.KAA27612@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.org, stable@FreeBSD.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: [PATCH] psmintr out of sync.. Date: Fri, 09 Jun 2000 10:41:39 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, folks. This is a test patch for the psm driver. I would like you to do some test for me. This is NOT the fix for the infamous "psmintr out of sync" message, but is a test patch to see how things are on your machines. The patch is for both CURRENT and STABLE. Please apply the patch to /sys/isa/psm.c (make backup copy first!), and rebuild the kernel. I would like you to carry out two tests: Test #1. Make sure you remove the flags 0x100 from the psm driver and see how your PS/2 mouse works. You may still see "psmintr out of sync", but I would like to know if the mouse pointer goes berserk when this message appears, or it seems to operate properly despite the message. Test #2. Add the flags 0x100 (NOCHECKSYNC) to the psm driver and see what happens. Please report your results together with your motherboard model, mouse model, FreeBSD version, mouse settings in /etc/rc.conf and XF86Config, and /var/run/dmesg.boot (after you reboot the kernel by typing "boot -v" at the boot loader prompt). Thank you for your cooperation. Kazu Index: psm.c =================================================================== RCS file: /src/CVS/src/sys/isa/psm.c,v retrieving revision 1.26 diff -u -r1.26 psm.c --- psm.c 2000/04/19 14:57:50 1.26 +++ psm.c 2000/06/09 01:19:59 @@ -1830,10 +1830,11 @@ unit = (int)arg; sc = devclass_get_softc(psm_devclass, unit); - if (sc->watchdog) { + if (sc->watchdog && kbdc_lock(sc->kbdc, TRUE)) { if (verbose >= 4) log(LOG_DEBUG, "psm%d: lost interrupt?\n", unit); psmintr(sc); + kbdc_lock(sc->kbdc, FALSE); } sc->watchdog = TRUE; sc->callout = timeout(psmtimeout, (void *)unit, hz); @@ -1880,18 +1881,6 @@ if ((sc->state & PSM_OPEN) == 0) continue; - /* - * Check sync bits. We check for overflow bits and the bit 3 - * for most mice. True, the code doesn't work if overflow - * condition occurs. But we expect it rarely happens... - */ - if ((sc->inputbytes == 0) - && ((c & sc->mode.syncmask[0]) != sc->mode.syncmask[1])) { - log(LOG_DEBUG, "psmintr: out of sync (%04x != %04x).\n", - c & sc->mode.syncmask[0], sc->mode.syncmask[1]); - continue; - } - sc->ipacket[sc->inputbytes++] = c; if (sc->inputbytes < sc->mode.packetsize) continue; @@ -1904,6 +1893,13 @@ c = sc->ipacket[0]; + if ((c & sc->mode.syncmask[0]) != sc->mode.syncmask[1]) { + log(LOG_DEBUG, "psmintr: out of sync (%04x != %04x).\n", + c & sc->mode.syncmask[0], sc->mode.syncmask[1]); + sc->inputbytes = 0; + continue; + } + /* * A kludge for Kensington device! * The MSB of the horizontal count appears to be stored in To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 20:47:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 083CC37BCC5; Thu, 8 Jun 2000 20:47:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA68437; Thu, 8 Jun 2000 20:47:37 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 8 Jun 2000 20:47:36 -0700 (PDT) From: Kris Kennaway To: Boris Popov Cc: John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Jun 2000, Boris Popov wrote: > Count both, nwfs and smbfs, because any program can attempt to > create temporary file on these filesystems. File with an invalid file name > will be rejected, and this will cost an additional lookup operation(s). I'm not sure that weird filesystems are a valid argument against mktemp() naming - there are LOTS of UNIX code which assumes UNIX namespace conventions, and it's not just mktemp() which is going to break on weird filesystems. For example, should we limit all FreeBSD file names to 8.3 single-case in case someone wants to run from an old-style MSDOS partition? Basically, I think the answer is not to use a nwfs or smbfs filesystem as your TMPDIR :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 21:56: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C35EB37B5EA; Thu, 8 Jun 2000 21:55:58 -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.9.3/8.9.3) with ESMTP id AAA245936; Fri, 9 Jun 2000 00:55:57 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 9 Jun 2000 00:56:22 -0400 To: Kris Kennaway , Boris Popov From: Garance A Drosihn Subject: Re: mktemp() patch Cc: John LoVerso , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:47 PM -0700 6/8/00, Kris Kennaway wrote: >On Fri, 9 Jun 2000, Boris Popov wrote: > > > Count both, nwfs and smbfs, because any program can > > attempt to create temporary file on these filesystems. Files > > with an invalid file name will be rejected, and this will > > cost an additional lookup operation(s). > >I'm not sure that weird filesystems are a valid argument against >mktemp() naming - there are LOTS of UNIX code which assumes UNIX >namespace conventions, and it's not just mktemp() which is going >to break on weird filesystems. For example, should we limit all >FreeBSD file names to 8.3 single-case in case someone wants to >run from an old-style MSDOS partition? > >Basically, I think the answer is not to use a nwfs or smbfs >filesystem as your TMPDIR :-) Certainly the new version should not worry about any problems (such as 8.3) which are just as much of a "problem" with the current implementation. A thought occurs to me, and it's vile enough that I would not feel insulted if everyone unanimously shouts it down. However, thoughts occur to me so rarely that I feel compelled to share them if there is any chance they might be useful. Should the new mktemp check some kind of environment variable, and use a different list (or maybe even a totally different algorithm) depending on the value? Perhaps have a few specific choices, where even the "least random" option would at least add a few characters to the current list. Maybe have the "most random" option completely drop more of the the UID part, and use that space for more randomly-generated bits? Honest, I won't feel bad if everyone hates this idea or laughs at the absurdity of it... :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 22: 7:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id D4CDD37B5EA; Thu, 8 Jun 2000 22:07:14 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id AAA18276; Fri, 9 Jun 2000 00:07:07 -0500 (CDT) (envelope-from dan) Date: Fri, 9 Jun 2000 00:07:07 -0500 From: Dan Nelson To: Kris Kennaway Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609000707.A16619@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from "Kris Kennaway" on Thu Jun 8 20:47:36 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 08), Kris Kennaway said: > On Fri, 9 Jun 2000, Boris Popov wrote: > > Count both, nwfs and smbfs, because any program can attempt to > > create temporary file on these filesystems. File with an invalid > > file name will be rejected, and this will cost an additional lookup > > operation(s). > > I'm not sure that weird filesystems are a valid argument against > mktemp() naming - there are LOTS of UNIX code which assumes UNIX > namespace conventions, and it's not just mktemp() which is going to > break on weird filesystems. For example, should we limit all FreeBSD > file names to 8.3 single-case in case someone wants to run from an > old-style MSDOS partition? I still suggest not using symbols at all, since I'd like to be able to quickly remove tempfiles by hand without worrying if I have to escape # or ^, etc. Considering the great jump in randomness between the orginal and the proposed (65536 -> 916132832 just using [A-Za-z0-9] ), I'd rather stick with easy-to-read and type tempnames. > Basically, I think the answer is not to use a nwfs or smbfs > filesystem as your TMPDIR :-) mktemp() doesn't use TMPDIR; the user gets to pass a template of his choosing, which could reasonably be just "bobXXXXX.tmp". -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 22:33:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 4347937B669 for ; Thu, 8 Jun 2000 22:33:23 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA99225 for ; Fri, 9 Jun 2000 01:33:21 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 9 Jun 2000 01:33:21 -0400 (EDT) From: Adam To: current@freebsd.org Subject: freezing and rebooting with vidcontrol -m on Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't really know where to go with this issue on my own anymore so im tossing it to the list for suggestions. I had a celeron running in a Abit BX6-2 system running -current approx a month or 1.5 old. Today I moved the disks to a Abit BP6 Motherboard and recompiled the kernel for smp and the other hardware changes I intended to make. Well, when I boot it up it would get down to approx "starting i386 whatever" and the boot would stop, the keyboard wouldnt type (although numlock would work for x amount of time) and you couldnt drop into ddb. Sometimes it would stick in this braindead mode, sometimes if you tried typing things to get it unstuck it would just reboot after a brief total keyboard lockup. No panic, just a reboot. I booted singleuser and cleaned up my rc.conf, disabling some noncritical things, and got the system booting fine. I have a usb logitech mouse by the way. Later I noticed no mouse cursor on my consoles even though I had moused running, so I ran vidcontrol -m on. WHAM. I had found the culprit. Okay so I know what caused it and what not to run ;0 I took the opportunity to cvsup and upgrade the whole system to -current as of today, and to my dismay it still does the same thing. I really wish I could drop into ddb when it happens but it wont let me. If serial might be a better option I could probably dig out a null modem cable... Suggestions Please! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 8 23:32:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 5524337C1EB; Thu, 8 Jun 2000 23:32:43 -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.9.3/8.9.3) with ESMTP id CAA270442; Fri, 9 Jun 2000 02:32:39 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000609000707.A16619@dan.emsphone.com> References: <20000609000707.A16619@dan.emsphone.com> Date: Fri, 9 Jun 2000 02:33:02 -0400 To: Dan Nelson , Kris Kennaway From: Garance A Drosihn Subject: Re: mktemp() patch Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:07 AM -0500 6/9/00, Dan Nelson wrote: >I still suggest not using symbols at all, since I'd like to >be able to quickly remove tempfiles by hand without worrying >if I have to escape # or ^, etc. Uh, if I understand the update, the '#' is ALREADY used for this, in the current implementation. If you haven't been having any trouble with it for the past few years, it seems odd to worry about it with the new implementation. Also, you do not have to worry about '^' in the middle of a filename. That is only significant when it's the first character of the line. Yes, someone might worry about it the first time they go to delete a file with one of those characters in it's name, but it won't take too long before they learn either to just 'rm blah*' or they'll learn that they do not have to worry about it. Just MO. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 2:14: 5 2000 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 1323137C327; Fri, 9 Jun 2000 02:13:53 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 130KrK-000NUR-00; Fri, 09 Jun 2000 16:13:46 +0700 Date: Fri, 9 Jun 2000 16:13:46 +0700 (ALMST) From: Boris Popov To: Kris Kennaway Cc: John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jun 2000, Kris Kennaway wrote: > > Count both, nwfs and smbfs, because any program can attempt to > > create temporary file on these filesystems. File with an invalid file name > > will be rejected, and this will cost an additional lookup operation(s). > > I'm not sure that weird filesystems are a valid argument against mktemp() > naming - there are LOTS of UNIX code which assumes UNIX namespace > conventions, and it's not just mktemp() which is going to break on weird > filesystems. For example, should we limit all FreeBSD file names to 8.3 > single-case in case someone wants to run from an old-style MSDOS > partition? Well, nwfs and smbfs filesystems usually used when one need to integrate FreeBSD machine in the already existing environment. So, the question is simple - do we need to help interoperability or not ? 8.3 format filenames are probably obsolete, and there is no reason to support them because nearly all server platforms support long file names. > Basically, I think the answer is not to use a nwfs or smbfs filesystem as > your TMPDIR :-) With mktemp() function you can create tempoary files anywhere, not just in TMPDIR. -- 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 Fri Jun 9 2:53:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.net [213.172.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 6323137B5BF for ; Fri, 9 Jun 2000 02:53:39 -0700 (PDT) (envelope-from kong@comset.net) Received: from localhost (kong@localhost) by crucian.comset.net (8.9.3/8.8.7) with ESMTP id NAA33519 for ; Fri, 9 Jun 2000 13:53:36 +0400 (MSD) Date: Fri, 9 Jun 2000 13:53:35 +0400 (MSD) From: Hostas Red To: freebsd-current@freebsd.org Subject: Can't make installworld :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I can't make installworld for some time with following message: vm/vm_object.h -> vm/vm_object.ph vm/vm_page.h -> vm/vm_page.ph vm/vm_pageout.h -> vm/vm_pageout.ph vm/vm_pager.h -> vm/vm_pager.ph vm/vm_param.h -> vm/vm_param.ph vm/vm_prot.h -> vm/vm_prot.ph vm/vm_zone.h -> vm/vm_zone.ph vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Some manipulations with manual installation of perl didn't help. :( Any ideas? Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 5:28:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 59A0D37B544 for ; Fri, 9 Jun 2000 05:28:35 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 28276 invoked from network); 9 Jun 2000 12:28:34 -0000 Received: from lc210.cvzoom.net (HELO cvzoom.net) (208.226.154.210) by ns.cvzoom.net with SMTP; 9 Jun 2000 12:28:34 -0000 Message-ID: <3940E2F2.FE989935@cvzoom.net> Date: Fri, 09 Jun 2000 08:28:34 -0400 From: Donn Miller X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Latest pcm commits and ESS 1868... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the latest pcm commits, there's a lot of pops and clicks during the playing of MP3's. This is with the ESS 1868 sound card. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 7:28:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id B77B237B52F for ; Fri, 9 Jun 2000 07:28:35 -0700 (PDT) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id 31493DDB96; Fri, 9 Jun 2000 10:26:12 -0400 (EDT) Message-ID: <3940FFBD.E6C7D6E9@infolibria.com> Date: Fri, 09 Jun 2000 10:31:25 -0400 From: John LoVerso Organization: InfoLibria X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000609000707.A16619@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I still suggest not using symbols at all, since I'd like to be able to > quickly remove tempfiles by hand without worrying if I have to escape # > or ^, etc. Then disable globbing first. (csh et al) "set noglob" or (sh et al) "set -f noglob". John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 8:27:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 3413E37C400; Fri, 9 Jun 2000 08:27:38 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e59FRYb10540; Fri, 9 Jun 2000 11:27:34 -0400 (EDT) Date: Fri, 9 Jun 2000 11:27:34 -0400 (EDT) From: Luoqi Chen Message-Id: <200006091527.e59FRYb10540@lor.watermarkgroup.com> To: current@freebsd.org, emulation@freebsd.org Subject: VMware detection code in boot loader Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would anyone object if I add a ficl word to detect whether we're booting from a vmware virtual machine? I find it extremely useful when I'm running FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a single kernel to boot both directly or inside the virtual machine. With this new word, I can determine which kernel to use in the loader script, saving me the trouble to unload and reload a new kernel each time I reboot. Here's the patch to the boot loader, Index: boot/ficl/ficl.h =================================================================== RCS file: /home/ncvs/src/sys/boot/ficl/ficl.h,v retrieving revision 1.14 diff -u -r1.14 ficl.h --- boot/ficl/ficl.h 2000/06/01 18:10:43 1.14 +++ boot/ficl/ficl.h 2000/06/07 18:18:38 @@ -860,6 +860,7 @@ #if defined(__i386__) && !defined(TESTMAIN) extern void ficlOutb(FICL_VM *pVM); extern void ficlInb(FICL_VM *pVM); +extern void vmware(FICL_VM *pVM); #endif #ifdef __cplusplus Index: boot/ficl/words.c =================================================================== RCS file: /home/ncvs/src/sys/boot/ficl/words.c,v retrieving revision 1.27 diff -u -r1.27 words.c --- boot/ficl/words.c 2000/06/01 18:10:43 1.27 +++ boot/ficl/words.c 2000/06/07 18:19:13 @@ -4800,6 +4800,7 @@ #ifdef __i386__ dictAppendWord(dp, "outb", ficlOutb, FW_DEFAULT); dictAppendWord(dp, "inb", ficlInb, FW_DEFAULT); + dictAppendWord(dp, "vmware", vmware, FW_DEFAULT); #endif #endif Index: boot/ficl/i386/sysdep.c =================================================================== RCS file: /home/ncvs/src/sys/boot/ficl/i386/sysdep.c,v retrieving revision 1.7 diff -u -r1.7 sysdep.c --- boot/ficl/i386/sysdep.c 1999/09/29 04:43:07 1.7 +++ boot/ficl/i386/sysdep.c 2000/06/07 18:18:13 @@ -111,6 +111,26 @@ c=inb(port); stackPushINT(pVM->pStack,c); } + +/* + * vmware ( -- version ) + * Get vmware version. + */ +void +vmware(FICL_VM *pVM) +{ + int version, magic = 0; + +#define VMWARE_MAGIC 0x564d5868 +#define VMWARE_PORT 0x5658 + + __asm __volatile("inl %%dx, %%eax" + : "=a" (version), "=b" (magic) + : "0" (VMWARE_MAGIC), "d" (VMWARE_PORT), "c" (0xa)); + if (magic != VMWARE_MAGIC) + version = -1; + stackPushINT(pVM->pStack, version); +} #endif #endif To use this feature, you first create a file /boot/vmware.4th: : vmware-conf vmware dup 0> if ." VMware version " . cr ." Loading /boot/vmware.conf..." cr s" /boot/vmware.conf" read-conf else drop then ; then create /boot/vmware.conf which sets the kernel to use: kernel="/kernel.VMWARE" finally, change your /boot/loader.rc to include /boot/loader.4th include /boot/vmware.4th initialize drop vmware-conf boot-conf check-password -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 8:35:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 4267937C3F8; Fri, 9 Jun 2000 08:35:06 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA03598; Fri, 9 Jun 2000 08:38:55 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006091538.IAA03598@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Luoqi Chen Cc: current@freebsd.org, emulation@freebsd.org Subject: Re: VMware detection code in boot loader In-reply-to: Your message of "Fri, 09 Jun 2000 11:27:34 EDT." <200006091527.e59FRYb10540@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Jun 2000 08:38:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would anyone object if I add a ficl word to detect whether we're booting > from a vmware virtual machine? Sounds good to me! -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 10: 9:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id D0FD037C720; Fri, 9 Jun 2000 10:09:24 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id AD05951; Fri, 9 Jun 2000 13:09:23 -0400 (AST) Message-ID: <394124C3.221E61BC@vangelderen.org> Date: Fri, 09 Jun 2000 13:09:23 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <200006081724.TAA00705@grimreaper.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > > What is the purpose of this? It looks hugely wasteful to me. If you > > > really need a single random bit, it is not good to waste a block of > > > hard-gained gryptographic randomness; can you not use a pseudo-random > > > bit-generator? > > > > arc4random() does not consume entropy except the first time it is called > > and when explicitly reseeded through arc4random_stir(). Apart from that > > it's a deterministic function (the arc4 stream cipher), but it's still a > > reasonably good cryptographic PRNG because arc4 is a cryptographically > > strong algorithm. > > But I repeat myself; are you still intending to use cryptographic security > for one bit? What does that buy you? An attacker will laugh at the waste > of resources that went into a coin-flip :-). Much better is to use something > cheaper like time-of-day XOR 1 << whatever. Pseudo random numbers are so cheap (or they should be) that you just don't want to try and 'optimize' here. It is much better to be conservative and use a good PRNG until it *proves* to be very problematic. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 10:14:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 6509337B60E; Fri, 9 Jun 2000 10:14:36 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 6CB0451; Fri, 9 Jun 2000 13:14:35 -0400 (AST) Message-ID: <394125FB.964917F7@vangelderen.org> Date: Fri, 09 Jun 2000 13:14:35 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Luoqi Chen Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <200006091527.e59FRYb10540@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > Would anyone object if I add a ficl word to detect whether we're booting > from a vmware virtual machine? I find it extremely useful when I'm running > FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a > single kernel to boot both directly or inside the virtual machine. With this > new word, I can determine which kernel to use in the loader script, saving > me the trouble to unload and reload a new kernel each time I reboot. > > Here's the patch to the boot loader, > > Index: boot/ficl/ficl.h > =================================================================== > RCS file: /home/ncvs/src/sys/boot/ficl/ficl.h,v > retrieving revision 1.14 > diff -u -r1.14 ficl.h > --- boot/ficl/ficl.h 2000/06/01 18:10:43 1.14 > +++ boot/ficl/ficl.h 2000/06/07 18:18:38 > @@ -860,6 +860,7 @@ > #if defined(__i386__) && !defined(TESTMAIN) > extern void ficlOutb(FICL_VM *pVM); > extern void ficlInb(FICL_VM *pVM); > +extern void vmware(FICL_VM *pVM); I'm not sure it is a good idea to name this variable VMWare as that is implementation specific. It may be better to have a var named 'emulation' set to 'none' or 'vmware' or 'bochs' or ... Just my EC 0.02, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 10:50: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 8B12D37BC74 for ; Fri, 9 Jun 2000 10:50:00 -0700 (PDT) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id CEB272CE6D; Fri, 9 Jun 2000 19:46:12 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.3+Sun/8.9.3) id TAA10597; Fri, 9 Jun 2000 19:57:27 +0200 (EET) Date: Fri, 9 Jun 2000 19:57:22 +0200 From: Vallo Kallaste To: Hostas Red Cc: freebsd-current@FreeBSD.ORG Subject: Re: Can't make installworld :( Message-ID: <20000609195722.B10454@myhakas.matti.ee> Reply-To: vallo@matti.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kong@comset.net on Fri, Jun 09, 2000 at 01:53:35PM +0400 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 01:53:35PM +0400, Hostas Red wrote: > I can't make installworld for some time with following message: > > vm/vm_object.h -> vm/vm_object.ph > vm/vm_page.h -> vm/vm_page.ph > vm/vm_pageout.h -> vm/vm_pageout.ph > vm/vm_pager.h -> vm/vm_pager.ph > vm/vm_param.h -> vm/vm_param.ph > vm/vm_prot.h -> vm/vm_prot.ph > vm/vm_zone.h -> vm/vm_zone.ph > vm/vnode_pager.h -> vm/vnode_pager.ph > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl. > *** Error code 1 > > Some manipulations with manual installation of perl didn't help. :( Any > ideas? I had same problem in the past. Some person, can't recall his name, said that it's known problem and discussed in the lists. His advice was to search in list archives. I've never found the exact answer but probably my search was wrong. Perhaps you'll have better luck. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 11:59:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 2AFDF37B74D; Fri, 9 Jun 2000 11:59:46 -0700 (PDT) Date: Fri, 9 Jun 2000 11:59:46 -0700 From: "Andrey A. Chernov" To: Kris Kennaway Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609115946.A55638@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kris@FreeBSD.org on Thu, Jun 08, 2000 at 08:47:36PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 08, 2000 at 08:47:36PM -0700, Kris Kennaway wrote: > filesystems. For example, should we limit all FreeBSD file names to 8.3 > single-case in case someone wants to run from an old-style MSDOS > partition? Bad example. Not _all_ filenames but temp. ones only which allows to run FreeBSD binary in MSDOS FS with MSDOS files. > Basically, I think the answer is not to use a nwfs or smbfs filesystem as > your TMPDIR :-) mktemp() makes temp files in any directory including current one. -- 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 Fri Jun 9 12: 2:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C016C37C4D6 for ; Fri, 9 Jun 2000 12:02:08 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Jun 2000 20:02:05 +0100 (BST) To: Hostas Red Cc: freebsd-current@freebsd.org, Vallo Kallaste Subject: Re: Can't make installworld :( In-reply-to: Your message of "Fri, 09 Jun 2000 13:53:35 +0400." Date: Fri, 09 Jun 2000 20:02:05 +0100 From: Ian Dowse Message-ID: <200006092002.aa59259@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Hosta s Red writes: >I can't make installworld for some time with following message: > >vm/vm_object.h -> vm/vm_object.ph >vm/vm_page.h -> vm/vm_page.ph >vm/vm_pageout.h -> vm/vm_pageout.ph >vm/vm_pager.h -> vm/vm_pager.ph >vm/vm_param.h -> vm/vm_param.ph >vm/vm_prot.h -> vm/vm_prot.ph >vm/vm_zone.h -> vm/vm_zone.ph >vm/vnode_pager.h -> vm/vnode_pager.ph >*** Error code 1 I've seen this before. h2ph will return a non-zero exit status if it failed to open _any_ of the files listed on the command line. This will typically happen if you have a dangling symbolic link somewhere in /usr/include. The error message indicating exactly which files h2ph couldn't open will be somewhere among all the 'XX.h -> XX.ph' messages. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 12:58:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id ED5E537CBA9; Fri, 9 Jun 2000 12:58:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA65944; Fri, 9 Jun 2000 12:58:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 9 Jun 2000 12:58:27 -0700 (PDT) From: Kris Kennaway To: "Andrey A. Chernov" Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: <20000609115946.A55638@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 Fri, 9 Jun 2000, Andrey A. Chernov wrote: > On Thu, Jun 08, 2000 at 08:47:36PM -0700, Kris Kennaway wrote: > > filesystems. For example, should we limit all FreeBSD file names to 8.3 > > single-case in case someone wants to run from an old-style MSDOS > > partition? > > Bad example. Not _all_ filenames but temp. ones only which allows to run > FreeBSD binary in MSDOS FS with MSDOS files. The point is the same. Files created by FreeBSD binaries during the course of operation don't conform to an 8.3 monocase naming scheme (think of dotfiles for example). I don't believe there's such a thing as a lowest common denominator of file system naming conventions - either a filesystem can support UFS names (perhaps through a translation later) or it's not suitable for running FreeBSD from. > > Basically, I think the answer is not to use a nwfs or smbfs filesystem as > > your TMPDIR :-) > > mktemp() makes temp files in any directory including current one. Yes, but in practice it's not used that way since you can't write to most directories on the system except ~ and /tmp and relatives. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 13: 2: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BC68537B543; Fri, 9 Jun 2000 13:02:01 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA66376; Fri, 9 Jun 2000 13:02:01 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 9 Jun 2000 13:02:01 -0700 (PDT) From: Kris Kennaway To: "Andrey A. Chernov" Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Jun 2000, Kris Kennaway wrote: > The point is the same. Files created by FreeBSD binaries during the course > of operation don't conform to an 8.3 monocase naming scheme (think of > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not layer > suitable for running FreeBSD from. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 13: 2:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id BC60E37C59C; Fri, 9 Jun 2000 13:02:36 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id WAA00773; Fri, 9 Jun 2000 22:02:44 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006092002.WAA00773@grimreaper.grondar.za> To: "Jeroen C. van Gelderen" Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <394124C3.221E61BC@vangelderen.org> In-Reply-To: <394124C3.221E61BC@vangelderen.org> ; from "Jeroen C. van Gelderen" "Fri, 09 Jun 2000 13:09:23 -0400." Date: Fri, 09 Jun 2000 22:02:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But I repeat myself; are you still intending to use cryptographic security > > for one bit? What does that buy you? An attacker will laugh at the waste > > of resources that went into a coin-flip :-). Much better is to use something > > cheaper like time-of-day XOR 1 << whatever. > > Pseudo random numbers are so cheap (or they should be) that you > just don't want to try and 'optimize' here. It is much better to > be conservative and use a good PRNG until it *proves* to be very > problematic. Why not just XOR the whole lot into the current ${randomnumber}? That way, at least the effort of the whole calculation is not wasted as much. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 13:46:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from c014.sfo.cp.net (c014-h001.c014.sfo.cp.net [209.228.12.65]) by hub.freebsd.org (Postfix) with SMTP id BC3B137C49B for ; Fri, 9 Jun 2000 13:46:04 -0700 (PDT) (envelope-from john@hei.net) Received: (cpmta 15560 invoked from network); 9 Jun 2000 13:46:03 -0700 Received: from unknown (HELO trout) (209.222.163.131) by smtp.transport.com (209.228.12.65) with SMTP; 9 Jun 2000 13:46:03 -0700 X-Sent: 9 Jun 2000 20:46:03 GMT Message-ID: <003f01bfd251$0c6fca20$83a3ded1@hei.net> From: "John Hengstler" To: Subject: Boot Manager Date: Fri, 9 Jun 2000 13:26:48 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, What is the quick way to restore the boot manager (dual os). Lost it when I reloaded Win98. Have 4.0 CD, machine running 5.0-current. John Hengstler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 14:29:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 19F4837B659; Fri, 9 Jun 2000 14:29:41 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA26768; Fri, 9 Jun 2000 17:29:18 -0400 (EDT) Message-ID: <20000609172917.A26459@netmonger.net> Date: Fri, 9 Jun 2000 17:29:18 -0400 From: Christopher Masto To: "Jeroen C. van Gelderen" , Luoqi Chen Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <200006091527.e59FRYb10540@lor.watermarkgroup.com> <394125FB.964917F7@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <394125FB.964917F7@vangelderen.org>; from Jeroen C. van Gelderen on Fri, Jun 09, 2000 at 01:14:35PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote: > I'm not sure it is a good idea to name this variable VMWare as > that is implementation specific. It may be better to have a var > named 'emulation' set to 'none' or 'vmware' or 'bochs' or ... Mmm.. or, giving forth the ability to do in/out instructions, so the non-generic code would be entirely in the add-on forth piece. I'm not sure if there are any security implications there.. at boot time the machine is essentially as single-user as it's ever going to be. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 14:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 217F837B52A; Fri, 9 Jun 2000 14:31:22 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA27155; Fri, 9 Jun 2000 17:31:18 -0400 (EDT) Message-ID: <20000609173118.B26459@netmonger.net> Date: Fri, 9 Jun 2000 17:31:18 -0400 From: Christopher Masto To: "Jeroen C. van Gelderen" , Luoqi Chen Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <200006091527.e59FRYb10540@lor.watermarkgroup.com> <394125FB.964917F7@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <394125FB.964917F7@vangelderen.org>; from Jeroen C. van Gelderen on Fri, Jun 09, 2000 at 01:14:35PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > extern void ficlOutb(FICL_VM *pVM); > > extern void ficlInb(FICL_VM *pVM); I'm an idiot. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 14:44:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-2.sjc.telocity.net (mail-2.sjc.telocity.net [216.227.56.42]) by hub.freebsd.org (Postfix) with ESMTP id D41B137B75C for ; Fri, 9 Jun 2000 14:44:12 -0700 (PDT) (envelope-from otterr@telocity.com) Received: from telocity.com (dsl-216-227-91-85.telocity.com [216.227.91.85]) by mail-2.sjc.telocity.net (8.9.3/8.9.3) with ESMTP id OAA00316; Fri, 9 Jun 2000 14:42:03 -0700 (PDT) Message-ID: <394165B6.F27D4B74@telocity.com> Date: Fri, 09 Jun 2000 17:46:30 -0400 From: Otter X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Latest pcm commits and ESS 1868... References: <3940E2F2.FE989935@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > With the latest pcm commits, there's a lot of pops and clicks during > the playing of MP3's. This is with the ESS 1868 sound card. > > - Donn > I hate to send "me too" emails, but i think it's the driver. My SB Live has worked great until last night, when i caught my source up to date. I was running on source from 6/4 which worked fine. I'm going to check it out again in a bit to see if it's been updated. I recommend you do the same. -Otter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 14:56:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.corp.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 78BEC37B756; Fri, 9 Jun 2000 14:56:42 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B13911CE1; Fri, 9 Jun 2000 14:56:41 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Christopher Masto Cc: "Jeroen C. van Gelderen" , Luoqi Chen , current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader In-Reply-To: Message from Christopher Masto of "Fri, 09 Jun 2000 17:29:18 EDT." <20000609172917.A26459@netmonger.net> Date: Fri, 09 Jun 2000 14:56:41 -0700 From: Peter Wemm Message-Id: <20000609215641.B13911CE1@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote: > > I'm not sure it is a good idea to name this variable VMWare as > > that is implementation specific. It may be better to have a var > > named 'emulation' set to 'none' or 'vmware' or 'bochs' or ... > > Mmm.. or, giving forth the ability to do in/out instructions, so the > non-generic code would be entirely in the add-on forth piece. I'm > not sure if there are any security implications there.. at boot time > the machine is essentially as single-user as it's ever going to be. I prefer 'emulation' being set to 'native', 'vmware' etc. Consider that there is IA64, Alpha, sparc, ppc etc to deal with. Teaching the ficl scripts to do inb/outb would be bad. It would be much better to have a generic mechanism for informing the loader about possible emulation environments, eg you are using the IA64 emulator under an x86 box, or an x86 emulator on an Alpha, or an Alpha SIMOS emulation under x86, or whatever. 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 Fri Jun 9 15:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 85E3D37B5A6; Fri, 9 Jun 2000 15:49:30 -0700 (PDT) Date: Fri, 9 Jun 2000 15:49:30 -0700 From: "Andrey A. Chernov" To: Kris Kennaway Cc: Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609154930.A33329@freebsd.org> References: <20000609115946.A55638@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kris@FreeBSD.org on Fri, Jun 09, 2000 at 12:58:27PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 12:58:27PM -0700, Kris Kennaway wrote: > > Bad example. Not _all_ filenames but temp. ones only which allows to run > > FreeBSD binary in MSDOS FS with MSDOS files. > > The point is the same. Files created by FreeBSD binaries during the course > of operation don't conform to an 8.3 monocase naming scheme (think of > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not > suitable for running FreeBSD from. Dotfiles usually created in user's home directory which is in UFS. What I mean is simple processing using temp files, consider running zip or unzip binaries. Proper way will be to sense FS name/abilitites and tune available charset in accordance with them. > > mktemp() makes temp files in any directory including current one. > > Yes, but in practice it's not used that way since you can't write to most > directories on the system except ~ and /tmp and relatives. I don't care about /tmp which is in UFS, I care about current directory. Probably /tmp-prefix sensing code helps to solve this. -- 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 Fri Jun 9 15:53:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id D446137BD55; Fri, 9 Jun 2000 15:53:42 -0700 (PDT) Date: Fri, 9 Jun 2000 15:53:42 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: "Jeroen C. van Gelderen" , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609155342.B33329@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200006092002.WAA00773@grimreaper.grondar.za>; from mark@grondar.za on Fri, Jun 09, 2000 at 10:02:44PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 10:02:44PM +0200, Mark Murray wrote: > > > But I repeat myself; are you still intending to use cryptographic security > > > for one bit? What does that buy you? An attacker will laugh at the waste > > > of resources that went into a coin-flip :-). Much better is to use something > > > cheaper like time-of-day XOR 1 << whatever. > > > > Pseudo random numbers are so cheap (or they should be) that you > > just don't want to try and 'optimize' here. It is much better to > > be conservative and use a good PRNG until it *proves* to be very > > problematic. > > Why not just XOR the whole lot into the current ${randomnumber}? > That way, at least the effort of the whole calculation is not wasted > as much. Why to XOR true random bits from arc4random() with non-random bits from getpid()? It only weakens. Better way is just remove any getpid() code and left arc4random() only. -- 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 Fri Jun 9 16:37:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id E02D037C1F2; Fri, 9 Jun 2000 16:37:10 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 693F94C; Fri, 9 Jun 2000 19:37:09 -0400 (AST) Message-ID: <39417FA5.F260EAA8@vangelderen.org> Date: Fri, 09 Jun 2000 19:37:09 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@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 "Andrey A. Chernov" wrote: > > On Fri, Jun 09, 2000 at 10:02:44PM +0200, Mark Murray wrote: > > > > But I repeat myself; are you still intending to use cryptographic security > > > > for one bit? What does that buy you? An attacker will laugh at the waste > > > > of resources that went into a coin-flip :-). Much better is to use something > > > > cheaper like time-of-day XOR 1 << whatever. > > > > > > Pseudo random numbers are so cheap (or they should be) that you > > > just don't want to try and 'optimize' here. It is much better to > > > be conservative and use a good PRNG until it *proves* to be very > > > problematic. > > > > Why not just XOR the whole lot into the current ${randomnumber}? > > That way, at least the effort of the whole calculation is not wasted > > as much. Good point, there is no need to throw them away indeed. > Why to XOR true random bits from arc4random() with non-random bits from > getpid()? It only weakens. Better way is just remove any getpid() code and > left arc4random() only. Then you will get collisions which you will have to deal with. I am not familiar with the code but if we can handle collisions nicely then that would be the way to go: 64^6 = 2^36 possibilities which is nice... Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 16:56:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id BEA6F37C256; Fri, 9 Jun 2000 16:56:29 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 0CAB34F; Fri, 9 Jun 2000 19:56:29 -0400 (AST) Message-ID: <3941842C.DE59BF21@vangelderen.org> Date: Fri, 09 Jun 2000 19:56:28 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: "Andrey A. Chernov" , Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Fri, 9 Jun 2000, Andrey A. Chernov wrote: > > > On Thu, Jun 08, 2000 at 08:47:36PM -0700, Kris Kennaway wrote: > > > filesystems. For example, should we limit all FreeBSD file names to 8.3 > > > single-case in case someone wants to run from an old-style MSDOS > > > partition? > > > > Bad example. Not _all_ filenames but temp. ones only which allows to run > > FreeBSD binary in MSDOS FS with MSDOS files. > > The point is the same. Files created by FreeBSD binaries during the course > of operation don't conform to an 8.3 monocase naming scheme (think of > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not > suitable for running FreeBSD from. There really is no reason to use 72 characters instead of -say- 64. The increase in security is marginal and if the side-effect of using 64 is that it works with more filesystems than that is a Good Thing (TM). We are not alone in this world as -say- Microsoft tends to think. It's probably better to just get rid of the PID and use randomness troughout the name than to use 72 characters. 64^6 vs. 2*(72^3) . Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 16:59:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 87DEC37C256; Fri, 9 Jun 2000 16:59:13 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id D34384F; Fri, 9 Jun 2000 19:59:12 -0400 (AST) Message-ID: <394184D0.3B7479F2@vangelderen.org> Date: Fri, 09 Jun 2000 19:59:12 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Christopher Masto , Luoqi Chen , current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <20000609215641.B13911CE1@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Christopher Masto wrote: > > On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote: > > > I'm not sure it is a good idea to name this variable VMWare as > > > that is implementation specific. It may be better to have a var > > > named 'emulation' set to 'none' or 'vmware' or 'bochs' or ... > > > > Mmm.. or, giving forth the ability to do in/out instructions, so the > > non-generic code would be entirely in the add-on forth piece. I'm > > not sure if there are any security implications there.. at boot time > > the machine is essentially as single-user as it's ever going to be. > > I prefer 'emulation' being set to 'native', 'vmware' etc. Consider that > there is IA64, Alpha, sparc, ppc etc to deal with. Teaching the ficl > scripts to do inb/outb would be bad. It would be much better to have a > generic mechanism for informing the loader about possible emulation > environments, eg you are using the IA64 emulator under an x86 box, or an > x86 emulator on an Alpha, or an Alpha SIMOS emulation under x86, or > whatever. Rethinking, emulation may not be the best suggestion. People might confuse it with Linux emulation. How about 'hardware' ? or 'platform' or ? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 17:29: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5192F37B61B; Fri, 9 Jun 2000 17:28:24 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Fri, 9 Jun 2000 20:28:06 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: "Jacob A. Hart" Cc: Doug Barton , Sheldon Hearn , FreeBSD-CURRENT Subject: Re: Scheduler changes? In-Reply-To: <20000528135331.A241@carcass.au.hartware.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, 28 May 2000, Jacob A. Hart wrote: > I remember the scheduler bug you're talking about. My system feels much > the same as it did during 4.0-CURRENT when that bug was active. I had a > collection of wrapper scripts for CPU intensive programs that suspended > rc5des, ran the program, then reenabled it again. Should have held on to > them, I guess. Check out http://people.FreeBSD.org/~green/mean.c. > > If this change > > fixes things for you, please report it asap, since my understanding is > > that this problem is rather elusive and annoying. > > No, it didn't work, unfortunately. To test it, I renice'd rc5des to a > couple of different values while encoding an MP3. It's an issue. Nice values count for less than before due to fixes that Luoqi Chen made (and I committed). The behavior now isn't optimal, but it is better than the system locking up. NICE_WEIGHT might be okay to keep at 2. Try the attached diff; I'm pretty sure it won't blow things up :) The diff should make a process at -20 which uses all available CPU schedule just slightly the ahead of a process at +20 which uses no CPU. A process which uses full CPU at 0 niceness would have a priority of 128, whereas a process using no CPU at 0 niceness would have a priority of 90. All processes will always have a priority less than or equal to 128, which is the priority at which a process with a niceness of +20 always runs at. A +20 process won't get better priority than anything else, period. Try it out, see how it works for you:) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' --- /usr/src/sys/sys/proc.h Fri May 26 20:15:46 2000 +++ /home/green/tmp/proc.h Fri Jun 9 20:13:30 2000 @@ -405,10 +405,10 @@ * the range 100-256 Hz (approximately). */ #define INVERSE_ESTCPU_WEIGHT 8 /* 1 / (priorities per estcpu level) */ -#define NICE_WEIGHT 1 /* priorities per nice level */ +#define NICE_WEIGHT 2 /* priorities per nice level */ #define PPQ (128 / NQS) /* priorities per queue */ #define ESTCPULIM(e) \ - min((e), INVERSE_ESTCPU_WEIGHT * (NICE_WEIGHT * PRIO_TOTAL - PPQ) + \ + min((e), INVERSE_ESTCPU_WEIGHT * (NICE_WEIGHT * PRIO_TOTAL / 2 - PPQ) + \ INVERSE_ESTCPU_WEIGHT - 1) extern u_long ps_arg_cache_limit; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 20:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 69EBE37B582 for ; Fri, 9 Jun 2000 20:57:15 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA09927; Fri, 9 Jun 2000 23:56:51 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 9 Jun 2000 23:56:51 -0400 (EDT) From: Adam To: Matthew Thyer Cc: current@freebsd.org Subject: Re: freezing and rebooting with vidcontrol -m on In-Reply-To: <3941AD54.EE18AC13@camtech.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Jun 2000, Matthew Thyer wrote: >Are you using power management (presumably so you can poweroff your >ATX system) ? > >You must not use APM with an SMP kernel currently. > >Remove the lines in your /etc/rc.conf that read: > >apm_enable="YES" >apmd_enable="YES" > >(Or change them to ="NO"). > >Or you can update your sources because this problem has just been fixed >(but there are suspend/resume problems with SMP still). Been there, did that, suspend even works. Waiting on lusers to logout so I can reboot and try a new kernel, I think i might have been using some console options it didnt like. > >Adam wrote: >> >> Hi, I don't really know where to go with this issue on my own anymore so >> im tossing it to the list for suggestions. >> >> I had a celeron running in a Abit BX6-2 system running -current approx a >> month or 1.5 old. Today I moved the disks to a Abit BP6 Motherboard and >> recompiled the kernel for smp and the other hardware changes I intended to >> make. Well, when I boot it up it would get down to approx "starting i386 >> whatever" and the boot would stop, the keyboard wouldnt type (although >> numlock would work for x amount of time) and you couldnt drop into >> ddb. Sometimes it would stick in this braindead mode, sometimes if you >> tried typing things to get it unstuck it would just reboot after a brief >> total keyboard lockup. No panic, just a reboot. I booted singleuser and >> cleaned up my rc.conf, disabling some noncritical things, and got the >> system booting fine. I have a usb logitech mouse by the way. Later I >> noticed no mouse cursor on my consoles even though I had moused running, >> so I ran vidcontrol -m on. WHAM. I had found the culprit. Okay so I >> know what caused it and what not to run ;0 I took the opportunity to cvsup >> and upgrade the whole system to -current as of today, and to my dismay it >> still does the same thing. I really wish I could drop into ddb when it >> happens but it wont let me. If serial might be a better option I could >> probably dig out a null modem cable... Suggestions Please! >> >> 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 Jun 9 21:11:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.194.18]) by hub.freebsd.org (Postfix) with ESMTP id 279EF37B67F for ; Fri, 9 Jun 2000 21:11:13 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id AAA00340 for freebsd-current@freebsd.org; Sat, 10 Jun 2000 00:11:12 -0400 (EDT) (envelope-from ray) Date: Sat, 10 Jun 2000 00:11:12 -0400 From: Ray Kohler To: freebsd-current@freebsd.org Subject: ps2 mouse troubles Message-ID: <20000610001112.A317@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just one more report to add to the ps2 mouse discussion: Today I moved from 4.0 to -CURRENT. Now my mouse jumps around like other people are reporting. It worked fine before. I tried using a different mouse. I tried using NOCHECKSYNC (even though I'm not getting the messages). I tried this both with and without moused, in X and in syscons. Nothing fixed it. This machine is a desktop with no APM support running. I'm not using a KVM. The two kinds of mice were a Logitech TrackMan Marble+ (detected as Intellimouse) and a standard Microsoft Mouse. Does this info help anyone out? I'll include my dmesg (with -v enabled): Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Fri Jun 9 23:34:10 EDT 2000 ray@rjk191.rh.psu.edu:/usr/src/sys/compile/RJK191 Calibrating clock(s) ... TSC clock: 167095319 Hz, i8254 clock: 1193539 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 167046023 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 83820544 (81856K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d8000 - 0x04fe7fff, 80805888 bytes (19728 pages) avail memory = 78757888 (76912K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fdb70 bios32: Entry = 0xfdb80 (c00fdb80) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xdba1 pnpbios: Found PnP BIOS data at 0xc00f6d50 pnpbios: Entry = f0000:6906 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02bf000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175254118 bytes/sec bzero() bandwidth = 88425148 bytes/sec pcib0: on motherboard found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[20]: type 4, range 32, base 0000ef80, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 4, range 32, base 0000ff40, size 4, enabled found-> vendor=0x1002, dev=0x4755, revid=0x9a class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base fe000000, size 24, enabled map[14]: type 4, range 32, base 0000ec00, size 8, enabled map[18]: type 1, range 32, base ffeff000, size 12, enabled found-> vendor=0x1274, dev=0x5000, revid=0x00 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 4, range 32, base 0000ee80, size 6, enabled found-> vendor=0x109e, dev=0x0350, revid=0x12 class=04-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 3, range 32, base fddff000, size 12, enabled found-> vendor=0x10b7, dev=0x9000, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 0000ef00, size 6, enabled pci0: on pcib0 pci0: (vendor=0x8086, dev=0x7100) at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=01 status0=50 status1=ff ata1: mask=01 status0=00 status1=ff ata1: devices = 0x4 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x7112) at 7.2 irq 10 pci0: (vendor=0x8086, dev=0x7113) at 7.3 pci0: (vendor=0x1002, dev=0x4755) at 10.0 irq 11 pcm0: port 0xee80-0xeebf irq 10 at device 11.0 on pci0 pcm: setmap 4e48000, 1000; 0xc0854000 -> 4e48000 pcm: setmap 4e49000, 1000; 0xc0855000 -> 4e49000 pci0: (vendor=0x109e, dev=0x0350) at 18.0 irq 10 xl0: <3Com 3c900-TPO Etherlink XL> port 0xef00-0xef3f irq 11 at device 19.0 on pci0 xl0: Ethernet address: 00:60:97:6d:9c:d8 xl0: media options word: e108 xl0: found 10baseT xl0: found AUI xl0: selecting 10baseT transceiver, half duplex pnpbios: 16 devices, largest 385 bytes PNP0c01: adding fixed memory32 range 0-0x9fbff, size=0x9fc00 PNP0c01: adding fixed memory32 range 0x9fc00-0x9ffff, size=0x400 PNP0c01: adding fixed memory32 range 0xe0000-0xfffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0x4feffff, size=0x4ef0000 PNP0c01: adding fixed memory32 range 0x4ff0000-0x4ff7fff, size=0x8000 PNP0c01: adding fixed memory32 range 0x4ff8000-0x4ffffff, size=0x8000 PNP0c01: adding fixed memory32 range 0xfffc0000-0xffffffff, size=0x40000 PNP0c01: end config pnpbios: handle 0 device ID PNP0c01 (010cd041) PNP0000: adding fixed io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding fixed io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0000: adding irq mask 00x4 PNP0000: end config pnpbios: handle 1 device ID PNP0000 (0000d041) PNP0200: adding dma mask 0x10 PNP0200: adding fixed io range 0-0xf, size=0x10, align=0x1 PNP0200: adding fixed io range 0x80-0x90, size=0x11, align=0x1 PNP0200: adding fixed io range 0x94-0x9f, size=0xc, align=0x1 PNP0200: adding fixed io range 0xc0-0xde, size=0x1f, align=0x1 PNP0200: end config pnpbios: handle 2 device ID PNP0200 (0002d041) PNP0100: adding irq mask 00x1 PNP0100: adding fixed io range 0x40-0x43, size=0x4, align=0x1 PNP0100: end config pnpbios: handle 3 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding fixed io range 0x70-0x73, size=0x4, align=0x1 PNP0b00: end config pnpbios: handle 4 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 00x2 PNP0303: adding fixed io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding fixed io range 0x64-0x64, size=0x1, align=0x1 PNP0303: end config pnpbios: handle 5 device ID PNP0303 (0303d041) PNP0800: adding fixed io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 6 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding fixed io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: end config pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0c02: adding io range 0xb0-0xb5, size=0x6, align=0x1 PNP0c02: adding io range 0xb8-0xb9, size=0x2, align=0x1 PNP0c02: adding io range 0xbc-0xbd, size=0x2, align=0x1 PNP0c02: adding io range 0xea-0xeb, size=0x2, align=0x1 PNP0c02: adding io range 0xef-0xef, size=0x1, align=0x1 PNP0c02: adding io range 0x3f0-0x3f1, size=0x2, align=0x1 PNP0c02: end config pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0c02: adding io range 0xff00-0xff3f, size=0x40, align=0x1 PNP0c02: adding io range 0xff40-0xff4f, size=0x10, align=0x1 PNP0c02: end config pnpbios: handle 9 device ID PNP0c02 (020cd041) PNP0f13: end config pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: end config pnpbios: handle 11 device ID PNP0a03 (030ad041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0c02: end config pnpbios: handle 13 device ID PNP0c02 (020cd041) PNP0400: adding io range 0x378-0x37b, size=0x4, align=0x8 PNP0400: adding irq mask 0x80 PNP0400: end config pnpbios: handle 14 device ID PNP0400 (0004d041) PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 15 device ID PNP0700 (0007d041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pcm-: pcm0 exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 39 03 c8 psm: status 39 03 c8 psm: status 39 03 c8 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) ppc0: parallel port found at 0x378 ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: EPP SPP ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP/NIBBLE_ID/ECP_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: SCP,VLINK lpt0: on ppbus0 lpt0: Interrupt-driven port mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) isa_probe_children: probing PnP devices unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x100000-0x4feffff,0x4ff0000-0x4ff7fff,0x4ff8000-0x4ffffff,0xfffc0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x73 irq 8 on isa0 unknown: can't assign resources unknown4: at port 0x61 on isa0 npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown5: at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: on isa0 unknown7: at port 0xcf8-0xcff on isa0 unknown8: at port 0x3f8-0x3ff irq 4 on isa0 unknown9: on isa0 unknown: can't assign resources unknown: can't assign resources BIOS Geometries: 0:0314fe3f 0..788=789 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO3 mode on generic chip acd0: CDROM drive at ata1 as master acd0: read 2755KB/s (2755KB/s), 256KB buffer, PIO3 acd0: Reads: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 6329609, size 6329547 : OK ad0s2: type 0xa5, start 6329610, end = 12691349, size 6361740 : OK start_init: trying /sbin/init lpt0: switched to polled standard mode -- Ray Kohler FreeBSD -- The Power to Serve HOW YOU CAN TELL THAT IT'S GOING TO BE A ROTTEN DAY: #32: You call your answering service and they've never heard of you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 21:26:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3DC7F37B995; Fri, 9 Jun 2000 21:26:03 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.135]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id NAA13281; Sat, 10 Jun 2000 13:25:57 +0900 (JST) Message-ID: <3941C395.621849D9@newsguy.com> Date: Sat, 10 Jun 2000 13:27:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <200006091527.e59FRYb10540@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > Would anyone object if I add a ficl word to detect whether we're booting > from a vmware virtual machine? I find it extremely useful when I'm running > FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a > single kernel to boot both directly or inside the virtual machine. With this > new word, I can determine which kernel to use in the loader script, saving > me the trouble to unload and reload a new kernel each time I reboot. > > Here's the patch to the boot loader, > > --- boot/ficl/ficl.h 2000/06/01 18:10:43 1.14 > +++ boot/ficl/ficl.h 2000/06/07 18:18:38 > @@ -860,6 +860,7 @@ > #if defined(__i386__) && !defined(TESTMAIN) > extern void ficlOutb(FICL_VM *pVM); ^^^^^^^^ > extern void ficlInb(FICL_VM *pVM); ^^^^^^^ > +extern void vmware(FICL_VM *pVM); We have inb and outb. Can't vmware be written in Forth? If inl cannot be replaced with inb, I'd rather add inl than vmware. > To use this feature, you first create a file /boot/vmware.4th: > > : vmware-conf > vmware dup 0> if > ." VMware version " . cr > ." Loading /boot/vmware.conf..." cr > s" /boot/vmware.conf" read-conf > else > drop > then > ; > > then create /boot/vmware.conf which sets the kernel to use: > > kernel="/kernel.VMWARE" > > finally, change your /boot/loader.rc to > > include /boot/loader.4th > include /boot/vmware.4th > initialize drop > vmware-conf > boot-conf > check-password IMHO, it would be better to add exec="include /boot/vmware.4th" to the end of your /boot/loader.conf, and either execute vmware-conf from there or script the whole thing: s" arch-i386" environment? [if] \ Get vmware version, magic 0x564d868 ( VMware magic ) = [if] .( VMware version ) . cr .( Loading /boot/vmware.conf...) cr s" /boot/vmware.conf" read-conf [else] drop [then] [then] Either way, no changes to /boot/loader.rc would be required. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@yet.another.bsdconspiracy.org Hmmm - I have to go check this. My reality assumptions are shattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 22:43:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from panda.showcase2000.net (00-50-04-ac-fc-bd.bconnected.net [209.53.15.75]) by hub.freebsd.org (Postfix) with SMTP id 979D437BCB4 for ; Fri, 9 Jun 2000 22:43:42 -0700 (PDT) (envelope-from kellyzg@hotmail.com) From: "Kelly G." To: freebsd-current@FreeBSD.ORG Cc: freebsd-questions@FreeBSD.ORG Subject: IPFW, sound, and modules Date: Thu, 08 Jun 2000 16:42:41 PDT Message-Id: <20000610054342.979D437BCB4@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Please excuse me, this is my first time posting a question. I know you people are only answering out of courtesy, and I appreciate any replies I may get. I was using FreeBSD 4.0 successfully with IPFW and Sound enabled. Recently I upgraded to 5.0 snapshot 2000/05/20 and my kernel now uses /modules/*.ko as much as possible. 1) So I took FIREWALL out of kernel configuration, and instead uses ipfw.ko. But now "ipfw add 15000 fwd 192.168.1.1 from any to 192.168.1.2" no longer works. I read from mailing lists that I need "options IPFIREWALL_FORWARD" in kernel configuration file. So I added that and recompile everything. Still doesn't work. My question is how do I enable forwarding in ipfw.ko? 2) Before upgrading to 5.0, my sound card worked well, and all I needed is to place "device pcm" in kernel configuration. But now, "mixer"... still works (I can use "cam" to adjust volume) and "line-in" still works (I can watch TV using "fxtv") but "wave" no longer work (Machine hangs when I run "mpg123"). Was there any changes to "pcm" driver recently? Thanks again. - Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 23: 5:18 2000 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 0AB3337C2D3; Fri, 9 Jun 2000 23:05: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.8.7/8.8.7) with ESMTP id QAA08614; Sat, 10 Jun 2000 16:05:06 +1000 Date: Sat, 10 Jun 2000 16:05:02 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: "Andrey A. Chernov" , Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Jun 2000, Kris Kennaway wrote: > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not > suitable for running FreeBSD from. There is the POSIX.1 portable filename character set: [A-Za-z._-] (from which the hyphen shall not be used as the first character of a portable filename). There are the POSIX NAME_MAX and pathconf(path, _SC_NAME_MAX) test features. NAME_MAX may be as low as 14 on POSIX systems. It is a small step from 14 to 11 or 8 to support non-POSIX 8.3 filenames. Very few programs actually support systems with variable or short filenames. patch(1) is one. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 23:21:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 3D76D37B5A3 for ; Fri, 9 Jun 2000 23:21:29 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id CAA11195 for ; Sat, 10 Jun 2000 02:21:30 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sat, 10 Jun 2000 02:21:29 -0400 (EDT) From: Adam To: current@freebsd.org Subject: Re: freezing and rebooting with vidcontrol -m on In-Reply-To: <3941AD54.EE18AC13@camtech.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, answering my own question for the sake of the archive, I believe it was an on combination of some of the options SC_something that vidcontrol -m on and my mouse and kernel didnt like. I was using some to save on kernel size and memory used but then decided to start using the computer on the console again so I just commented all those SC feature disabling out and all seems well. > >Adam wrote: >> >> Hi, I don't really know where to go with this issue on my own anymore so >> im tossing it to the list for suggestions. >> >> I had a celeron running in a Abit BX6-2 system running -current approx a >> month or 1.5 old. Today I moved the disks to a Abit BP6 Motherboard and >> recompiled the kernel for smp and the other hardware changes I intended to >> make. Well, when I boot it up it would get down to approx "starting i386 >> whatever" and the boot would stop, the keyboard wouldnt type (although >> numlock would work for x amount of time) and you couldnt drop into >> ddb. Sometimes it would stick in this braindead mode, sometimes if you >> tried typing things to get it unstuck it would just reboot after a brief >> total keyboard lockup. No panic, just a reboot. I booted singleuser and >> cleaned up my rc.conf, disabling some noncritical things, and got the >> system booting fine. I have a usb logitech mouse by the way. Later I >> noticed no mouse cursor on my consoles even though I had moused running, >> so I ran vidcontrol -m on. WHAM. I had found the culprit. Okay so I >> know what caused it and what not to run ;0 I took the opportunity to cvsup >> and upgrade the whole system to -current as of today, and to my dismay it >> still does the same thing. I really wish I could drop into ddb when it >> happens but it wont let me. If serial might be a better option I could >> probably dig out a null modem cable... Suggestions Please! >> >> 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 Jun 9 23:24: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 5FED637B6AB; Fri, 9 Jun 2000 23:23:58 -0700 (PDT) Date: Fri, 9 Jun 2000 23:23:58 -0700 From: "Andrey A. Chernov" To: "Jeroen C. van Gelderen" Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609232358.A38967@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <39417FA5.F260EAA8@vangelderen.org>; from jeroen@vangelderen.org on Fri, Jun 09, 2000 at 07:37:09PM -0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 07:37:09PM -0400, Jeroen C. van Gelderen wrote: > > Why to XOR true random bits from arc4random() with non-random bits from > > getpid()? It only weakens. Better way is just remove any getpid() code and > > left arc4random() only. > > Then you will get collisions which you will have to deal with. I am not > familiar with the code but if we can handle collisions nicely then that > would be the way to go: 64^6 = 2^36 possibilities which is nice... 1) Just totally opposite: mixing random with non-random sources you'll get into collision much faster then with random source only. 2) Yet, of course, the code handles collisions. -- 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 Fri Jun 9 23:31:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4897A37B66E for ; Fri, 9 Jun 2000 23:31:46 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:LE+NK8XGxJH3soQkv1jd66X5M7DFhyET@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id PAA22031; Sat, 10 Jun 2000 15:31:40 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:REGrnPVUSK1Xu1/Olop/CS0dZM7K1oPZ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id PAA10703; Sat, 10 Jun 2000 15:38:28 +0900 (JST) Message-Id: <200006100638.PAA10703@zodiac.mech.utsunomiya-u.ac.jp> To: Adam Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: freezing and rebooting with vidcontrol -m on In-reply-to: Your message of "Sat, 10 Jun 2000 02:21:29 -0400." References: Date: Sat, 10 Jun 2000 15:38:27 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Okay, answering my own question for the sake of the archive, I believe it >was an on combination of some of the options SC_something that >vidcontrol -m on and my mouse and kernel didnt like. I was using some to >save on kernel size and memory used but then decided to start using the >computer on the console again so I just commented all those SC feature >disabling out and all seems well. Thank you for reporting. Would you tell me which SC_XXX options you used to have in your kernel configuration file? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 23:33:15 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 4E93A37B66E; Fri, 9 Jun 2000 23:33:13 -0700 (PDT) Date: Fri, 9 Jun 2000 23:33:13 -0700 From: "Andrey A. Chernov" To: "Jeroen C. van Gelderen" Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609233313.A46973@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> <20000609232358.A38967@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000609232358.A38967@freebsd.org>; from ache@freebsd.org on Fri, Jun 09, 2000 at 11:23:58PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 11:23:58PM -0700, Andrey A. Chernov wrote: > On Fri, Jun 09, 2000 at 07:37:09PM -0400, Jeroen C. van Gelderen wrote: > > > Why to XOR true random bits from arc4random() with non-random bits from > > > getpid()? It only weakens. Better way is just remove any getpid() code and > > > left arc4random() only. > > > > Then you will get collisions which you will have to deal with. I am not > > familiar with the code but if we can handle collisions nicely then that > > would be the way to go: 64^6 = 2^36 possibilities which is nice... > > 1) Just totally opposite: mixing random with non-random sources you'll get > into collision much faster then with random source only. To clarify this: I mean getpid() ^ arc4random() suggestion only. Current variant is more complex because part of name is getpid() to avoid collision and part is random. But avoiding collision in this way is less secure because it is more predictable for attacker. -- 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 Fri Jun 9 23:38:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C124637B66E for ; Fri, 9 Jun 2000 23:38:09 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id CAA11379; Sat, 10 Jun 2000 02:38:03 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sat, 10 Jun 2000 02:38:03 -0400 (EDT) From: Adam To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: freezing and rebooting with vidcontrol -m on In-Reply-To: <200006100638.PAA10703@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont recall exactly :( SC_NO_FONT_LOADING was one of them, I may have commented one of the others in the old conf trying to fix it. I have a spare comp with a freebsd install I could play around with it on and see if I can recreate it instead of goofing around with my server that had the problem, fsck'ing 78 gigs is not pretty ;} (Yes I eventually stopped mounting the big drives while testing but I still dont like torturing / and /usr hehe) On Sat, 10 Jun 2000, Kazutaka YOKOTA wrote: > >>Okay, answering my own question for the sake of the archive, I believe it >>was an on combination of some of the options SC_something that >>vidcontrol -m on and my mouse and kernel didnt like. I was using some to >>save on kernel size and memory used but then decided to start using the >>computer on the console again so I just commented all those SC feature >>disabling out and all seems well. > >Thank you for reporting. Would you tell me which SC_XXX options >you used to have in your kernel configuration file? > >Kazu > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 9 23:46:38 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 8F3EE37B66E; Fri, 9 Jun 2000 23:46:34 -0700 (PDT) Date: Fri, 9 Jun 2000 23:46:34 -0700 From: "Andrey A. Chernov" To: "Jeroen C. van Gelderen" Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000609234634.A50676@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> <20000609232358.A38967@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000609232358.A38967@freebsd.org>; from ache@freebsd.org on Fri, Jun 09, 2000 at 11:23:58PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 11:23:58PM -0700, Andrey A. Chernov wrote: > > would be the way to go: 64^6 = 2^36 possibilities which is nice... > > 1) Just totally opposite: mixing random with non-random sources you'll get > into collision much faster then with random source only. 2) Yet, of course, > the code handles collisions. Part 2) need to be clarified too. The code _attempt_ to handle collision, but collision race can occurse between two processes checking for collision, so getpid() insertion prevents this. I am not against of removing getpid() code totally, just against of "randomization" of it, suggested in the patch, which increase collision chance. -- 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 Fri Jun 9 23:53:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A392537B66E; Fri, 9 Jun 2000 23:53:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17619; Fri, 9 Jun 2000 23:53:34 -0700 (PDT) (envelope-from dillon) Date: Fri, 9 Jun 2000 23:53:34 -0700 (PDT) From: Matthew Dillon Message-Id: <200006100653.XAA17619@apollo.backplane.com> To: "Andrey A. Chernov" Cc: "Jeroen C. van Gelderen" , Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> <20000609232358.A38967@freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :1) Just totally opposite: mixing random with non-random sources you'll get :into collision much faster then with random source only. 2) Yet, of course, :the code handles collisions. : :-- :Andrey A. Chernov : Think about it. If you mix a random number with a non-random number, using xor, what you get is.... a random number. It's neither stronger nor weaker. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 0:13:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id E957037B66E; Sat, 10 Jun 2000 00:13:18 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA04771; Sat, 10 Jun 2000 09:13:30 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006100713.JAA04771@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: Mark Murray , "Jeroen C. van Gelderen" , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000609155342.B33329@freebsd.org> In-Reply-To: <20000609155342.B33329@freebsd.org> ; from "Andrey A. Chernov" "Fri, 09 Jun 2000 15:53:42 MST." Date: Sat, 10 Jun 2000 09:13:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why not just XOR the whole lot into the current ${randomnumber}? > > That way, at least the effort of the whole calculation is not wasted > > as much. > > Why to XOR true random bits from arc4random() with non-random bits from > getpid()? It only weakens. Better way is just remove any getpid() code and > left arc4random() only. Rubbish. A XOR B is random if at least one of A or B is random. That is a pretty fundamental theorem of Cryptography. My suggestion _strengthens_ the random number. All you lose is one bit if it turns out that BOTH A and B are random, because they get combined into one. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 0:31:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id A1D1E37C69E; Sat, 10 Jun 2000 00:31:38 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA04819; Sat, 10 Jun 2000 09:31:49 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006100731.JAA04819@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: "Jeroen C. van Gelderen" , Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch References: <20000609232358.A38967@freebsd.org> In-Reply-To: <20000609232358.A38967@freebsd.org> ; from "Andrey A. Chernov" "Fri, 09 Jun 2000 23:23:58 MST." Date: Sat, 10 Jun 2000 09:31:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Then you will get collisions which you will have to deal with. I am not > > familiar with the code but if we can handle collisions nicely then that > > would be the way to go: 64^6 = 2^36 possibilities which is nice... > > 1) Just totally opposite: mixing random with non-random sources you'll get > into collision much faster then with random source only. 2) Yet, of course, > the code handles collisions. Incorrect. See my other mail; ${RANDOM} xor ${PREDICTABLE} is random. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 0:57:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from limbo.dn.ua (kapa.aist.net [193.124.70.67]) by hub.freebsd.org (Postfix) with ESMTP id 24F7237B613; Sat, 10 Jun 2000 00:56:46 -0700 (PDT) (envelope-from arcade@limbo.dn.ua) Received: (from arcade@localhost) by limbo.dn.ua (8.9.3/8.9.3) id KAA56072; Sat, 10 Jun 2000 10:56:00 +0300 (EEST) (envelope-from arcade) Date: Sat, 10 Jun 2000 10:56:00 +0300 From: Volodymyr Kostyrko To: Brian Fundakowski Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: Scheduler changes? Message-ID: <20000610105600.A55725@limbo.dn.ua> Reply-To: arcade@aist.net References: <20000528135331.A241@carcass.au.hartware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from green@FreeBSD.ORG on Fri, Jun 09, 2000 at 08:28:06PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 08:28:06PM -0400, Brian Fundakowski Feldman wrote: > It's an issue. Nice values count for less than before due to fixes > that Luoqi Chen made (and I committed). The behavior now isn't optimal, > but it is better than the system locking up. NICE_WEIGHT might be okay > to keep at 2. Try the attached diff; I'm pretty sure it won't blow > things up :) > The diff should make a process at -20 which uses all available CPU > schedule just slightly the ahead of a process at +20 which uses no CPU. > A process which uses full CPU at 0 niceness would have a priority of > 128, whereas a process using no CPU at 0 niceness would have a priority > of 90. All processes will always have a priority less than or equal to > 128, which is the priority at which a process with a niceness of +20 > always runs at. A +20 process won't get better priority than anything > else, period. Try it out, see how it works for you:) I think this is not the clear solution for descibed problem 'couse the dnetc client still gets a priority and still have the share of time while other programs might run. For me idprio works great. Just change last string in the starting shell scipt. idprio 31 su nobody -c "$dir/dnetc -quiet" 2>/dev/null >/dev/null & -- [WBR], Arcade Zardos. [AIST] [SAT Astronomy//Think to survive!] [mp3.aist.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 3: 7:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 6463A37BCB7 for ; Sat, 10 Jun 2000 03:07:49 -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.9.3/8.9.3) with ESMTP id GAA107118 for ; Sat, 10 Jun 2000 06:07:46 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3941842C.DE59BF21@vangelderen.org> References: <3941842C.DE59BF21@vangelderen.org> Date: Sat, 10 Jun 2000 06:08:08 -0400 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: mktemp() patch Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It's probably better to just get rid of the PID and use randomness >throughout the name than to use 72 characters. 64^6 vs. 2*(72^3) . I seem to be in the minority on this, but in general I *like* the idea that the tempfiles include the pid. It's bad because it makes it easier for an evil-person to guess what the next tempfile will be, but it's nice in after-the-fact situations, where there are a bunch of tempfiles left over, and you're wondering which ones are related (in the sense of having come from the same process, and you can then check if the process is still running). Not a big issue for me, as I doubt I have taken advantage of this more often than about once every two years, but I thought I would at least mention it. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 6:31:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 9749F37B71B; Sat, 10 Jun 2000 06:31:41 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e5ADVe205943; Sat, 10 Jun 2000 09:31:40 -0400 (EDT) Date: Sat, 10 Jun 2000 09:31:40 -0400 (EDT) From: Luoqi Chen Message-Id: <200006101331.e5ADVe205943@lor.watermarkgroup.com> To: dcs@newsguy.com Subject: Re: VMware detection code in boot loader Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have inb and outb. Can't vmware be written in Forth? If inl cannot be > replaced with inb, I'd rather add inl than vmware. > But we can't set registers to specific values before inb/outb, which also means our inb/outb are quite useless in making BIOS calls. > IMHO, it would be better to add > > exec="include /boot/vmware.4th" > > to the end of your /boot/loader.conf, and either execute vmware-conf > from there or script the whole thing: > > s" arch-i386" environment? [if] > \ Get vmware version, magic > 0x564d868 ( VMware magic ) = [if] > .( VMware version ) . cr > .( Loading /boot/vmware.conf...) cr > s" /boot/vmware.conf" read-conf > [else] > drop > [then] > [then] > > Either way, no changes to /boot/loader.rc would be required. > This looks much better, I didn't know we could tell the loader to execute a script in loader.conf. > -- > Daniel C. Sobral (8-DCS) > > dcs@newsguy.com > dcs@freebsd.org > capo@yet.another.bsdconspiracy.org > > Hmmm - I have to go check this. My reality assumptions are shattered. > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 7:46:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0D1F637B60B; Sat, 10 Jun 2000 07:46:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p54-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.119]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id XAA12425; Sat, 10 Jun 2000 23:46:30 +0900 (JST) Message-ID: <39425506.AE599417@newsguy.com> Date: Sat, 10 Jun 2000 23:47:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader References: <200006101331.e5ADVe205943@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > > We have inb and outb. Can't vmware be written in Forth? If inl cannot be > > replaced with inb, I'd rather add inl than vmware. > But we can't set registers to specific values before inb/outb, which also > means our inb/outb are quite useless in making BIOS calls. BIOS calls? Y'know, I once argued for a vm86intr() (or whatever it is called) on FICL, in case applications needed it. As for setting registers ti specific values... huh? Why does this matter? Can you explain exactly what your code does and how? I'd much prefer this could be done from a .4th file, as this is something ports and third-parties might like to do. > > Either way, no changes to /boot/loader.rc would be required. > > > This looks much better, I didn't know we could tell the loader to execute a > script in loader.conf. I try to keep it a secret. :-) While the exec="" stuff allows for arbitrary code execution (as do _after, _before and _error), this sort of thing is best avoided if possible on a configuration file. This particular case, though, is precisely the kind of exception to the rule I had in mind. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@yet.another.bsdconspiracy.org Hmmm - I have to go check this. My reality assumptions are shattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 9:15: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 37E6D37BBF9; Sat, 10 Jun 2000 09:15:02 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sat, 10 Jun 2000 12:14:59 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: arcade@aist.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Scheduler changes? In-Reply-To: <20000610105600.A55725@limbo.dn.ua> 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, 10 Jun 2000, Volodymyr Kostyrko wrote: > On Fri, Jun 09, 2000 at 08:28:06PM -0400, Brian Fundakowski Feldman wrote: > > It's an issue. Nice values count for less than before due to fixes > > that Luoqi Chen made (and I committed). The behavior now isn't optimal, > > but it is better than the system locking up. NICE_WEIGHT might be okay > > to keep at 2. Try the attached diff; I'm pretty sure it won't blow > > things up :) > > The diff should make a process at -20 which uses all available CPU > > schedule just slightly the ahead of a process at +20 which uses no CPU. > > A process which uses full CPU at 0 niceness would have a priority of > > 128, whereas a process using no CPU at 0 niceness would have a priority > > of 90. All processes will always have a priority less than or equal to > > 128, which is the priority at which a process with a niceness of +20 > > always runs at. A +20 process won't get better priority than anything > > else, period. Try it out, see how it works for you:) > > I think this is not the clear solution for descibed problem 'couse the dnetc client still gets a priority and still have the share of time while other programs might run. For me idprio works great. Just change last string in the starting shell scipt. There is no clear solution at all... try it out. Of _course_ it still gets a share of the time. If it didn't, then it could deadlock the system (like idprio and rtprio both can). > idprio 31 su nobody -c "$dir/dnetc -quiet" 2>/dev/null >/dev/null & > > -- > [WBR], Arcade Zardos. [AIST] [SAT Astronomy//Think to survive!] [mp3.aist.net] -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 9:29: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from fepa.mail.ozemail.net (fepa.mail.ozemail.net [203.2.192.101]) by hub.freebsd.org (Postfix) with ESMTP id 4ABAF37BBF9; Sat, 10 Jun 2000 09:28:55 -0700 (PDT) (envelope-from obituary@ozemail.com.au) Received: from carcass.au.hartware.com (slnew54p31.ozemail.com.au [203.108.151.47]) by fepa.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id CAA24400; Sun, 11 Jun 2000 02:28:50 +1000 (EST) Received: (from obituary@localhost) by carcass.au.hartware.com (8.9.3/8.9.3) id CAA10150; Sun, 11 Jun 2000 02:26:29 +1000 (EST) (envelope-from obituary) Date: Sun, 11 Jun 2000 02:26:29 +1000 From: "Jacob A. Hart" To: arcade@aist.net Cc: Brian Fundakowski Feldman , freebsd-current@FreeBSD.ORG Subject: Re: Scheduler changes? Message-ID: <20000611022629.E9700@carcass.au.hartware.com> References: <20000528135331.A241@carcass.au.hartware.com> <20000610105600.A55725@limbo.dn.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000610105600.A55725@limbo.dn.ua>; from arcade@limbo.dn.ua on Sat, Jun 10, 2000 at 10:56:00AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 10:56:00AM +0300, Volodymyr Kostyrko wrote: > > I think this is not the clear solution for descibed problem 'couse the > dnetc client still gets a priority and still have the share of time while > other programs might run. For me idprio works great. Just change last > string in the starting shell scipt. > > idprio 31 su nobody -c "$dir/dnetc -quiet" 2>/dev/null >/dev/null & I had no idea this wonderful little utility existed. It's a godsend! Thanks. -jake -- Jacob A. Hart Powered by: FreeBSD 5.0-CURRENT #17: Fri Jun 9 21:58:34 EST 2000 "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 9:39:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EC66E37B54B; Sat, 10 Jun 2000 09:39:50 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p61-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.62]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA08135; Sun, 11 Jun 2000 01:39:46 +0900 (JST) Message-ID: <39426699.472F35D7@newsguy.com> Date: Sun, 11 Jun 2000 01:02:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: "Andrey A. Chernov" , Boris Popov , John LoVerso , current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > > Bad example. Not _all_ filenames but temp. ones only which allows to run > > FreeBSD binary in MSDOS FS with MSDOS files. > > The point is the same. Files created by FreeBSD binaries during the course > of operation don't conform to an 8.3 monocase naming scheme (think of > dotfiles for example). I don't believe there's such a thing as a lowest > common denominator of file system naming conventions - either a filesystem > can support UFS names (perhaps through a translation later) or it's not > suitable for running FreeBSD from. With this line of reasoning, why don't you go all the way and add control characters and stuff? They are allowed by ufs, and shell even grok them. In fact, commands such as ls even have flags to deal with them. Kris, IT IS THE APPLICATION THAT DICTATE YOUR NEEDS. The reasoning above would more likely get FreeBSD to be discarded than the FS. If the OS won't bend to the users' need, it will get dumped, period. As we position FreeBSD as a server system, the need to support foreign filesystems WELL increases. FIOFO (with all due respect :). > > mktemp() makes temp files in any directory including current one. > > Yes, but in practice it's not used that way since you can't write to most > directories on the system except ~ and /tmp and relatives. Tell that to vim. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@yet.another.bsdconspiracy.org Hmmm - I have to go check this. My reality assumptions are shattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 9:39:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 47EBD37BBF9; Sat, 10 Jun 2000 09:39:53 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p61-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.62]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA08158; Sun, 11 Jun 2000 01:39:50 +0900 (JST) Message-ID: <394267EB.F56153D5@newsguy.com> Date: Sun, 11 Jun 2000 01:08:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Instead of using only alphabetic characters, the patch uses the following > character set: > > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > > which is not believed to cause any problems with shells. The PID is also Huh? # does not cause problems? : does not cause problems? Mind you, shells don't have problems with any character at all in a filename if they are properly written, but if you are expecting the filenames generated by mktemp() to be handled by shell, they ought to pass the IFS=':'; for file in $filelist test. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@yet.another.bsdconspiracy.org Hmmm - I have to go check this. My reality assumptions are shattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 11:33:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr1003333-a.crdva1.bc.home.com (cr1003333-a.crdva1.bc.wave.home.com [24.113.51.240]) by hub.freebsd.org (Postfix) with ESMTP id E9D0437BEFE for ; Sat, 10 Jun 2000 11:33:24 -0700 (PDT) (envelope-from pangolin@home.com) Received: from cr1003333-a.crdva1.bc.wave.home.com. (localhost [127.0.0.1]) by cr1003333-a.crdva1.bc.home.com (8.9.3/8.9.3) with ESMTP id LAA04816 for ; Sat, 10 Jun 2000 11:33:16 -0700 (PDT) (envelope-from pangolin@home.com) Message-Id: <200006101833.LAA04816@cr1003333-a.crdva1.bc.home.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200006080635.XAA06907@cr1003333-a.crdva1.bc.home.com> Date: Sat, 10 Jun 2000 11:33:16 -0700 (PDT) Reply-To: Jonathan Hanna Organization: Pangolin Systems From: Jonathan Hanna To: freebsd-current@FreeBSD.ORG Subject: RE: Strange rpc.statd and mount_nfs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As was pointed out, rcp.statd is supposed to have a large VSZ, but mount_nfs should not and my swap was getting used up. mount_nfs will do an RPC clntudp_create for every attempt, but only a clnt_destroy after a success. Here is a rather suspicious fix, I have not looked at rpc call use in detail: --- mount_nfs.c.orig Sat Jun 10 11:08:19 2000 +++ mount_nfs.c Sat Jun 10 11:09:06 2000 @@ -784,10 +784,11 @@ warnx("%s", clnt_sperror(clp, "bad MNT RPC")); } else { - auth_destroy(clp->cl_auth); - clnt_destroy(clp); retrycnt = 0; } + auth_destroy(clp->cl_auth); + clnt_destroy(clp); + so = RPC_ANYSOCK; } } if (--retrycnt > 0) { On 08-Jun-00 Jonathan Hanna wrote: > > I am running a fairly recent current and noticed my swap seemed > a little overused. > > bash-2.02$ uname -a > FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun May 14 11:50:20 PDT 2000 jh@roller.pangolin- sy > stems.com:/home/src/sys/compile/ROLLER i386 > bash-2.02$ uptime > 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 > > ps shows: ... > 0 212 1 29 2 0 263036 0 select IWs ?? 0:00.00 rpc.stat This is expected. > This looks big. > 0 1382 1 0 2 0 3716 352 select I ?? 0:01.02 xterm -geometry 80x25 -fg springgree ... > 1000 1504 1 0 10 0 86368 408 nanslp Is ?? 0:07.93 nfs -o bg -o noauto ghost-p1:/home/j > > This seems rather large as well. Not expected. ... > I do remember an nfs mount failing and perhaps being backgrounded. This was it, in normal circumstances the problem would not show up. I guess I shouldn't be leaving failing mounts around! Jonathan Hanna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 12:20:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from hrothgar.gw.com (hrothgar.gw.com [204.80.150.3]) by hub.freebsd.org (Postfix) with ESMTP id C50AE37BDB8; Sat, 10 Jun 2000 12:20:41 -0700 (PDT) (envelope-from kim@tac.nyc.ny.us) Received: from hrothgar.gw.com (kim@localhost [127.0.0.1]) by hrothgar.gw.com (8.9.3/8.8.6.Beta0/2.1.kim) with ESMTP id PAA17675; Sat, 10 Jun 2000 15:20:25 -0400 (EDT) Message-Id: <200006101920.PAA17675@hrothgar.gw.com> To: "Andrey A. Chernov" Cc: tcsh-bugs@mx.gw.com, obrien@FreeBSD.org, current@FreeBSD.org Subject: Re: tcsh history and month bugfix: tc.prompt.c v3.38 In-Reply-To: <20000421083612.A35344@nagual.pp.ru> from "Andrey A. Chernov" on Fri, 21 Apr 2000 08:36:12 +0400 References: <20000421083612.A35344@nagual.pp.ru> X-Face: dJ`"\|-Z6bKup3nm*Th75RV`!T)~xXMZKQt6|%BR~9'A7WzN"rsq4Cv+T~Hg9YRb^oEmVxz I0s1&A|(:ISoQJus6s<%pssRki3x*Kf;3BL;Gyq3'>06R>R`Om_ILkJAizKL{AC::|UE/N)u}*Ix}s nn{eh=0Um[!yF@gn-JN.6AB+xy5$Biy5I?)T~i#-C^m>vy(!(S*'m}M[>5uvbWcm X-Attribution: Kim MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17671.960664825.1@hrothgar.gw.com> Date: Sat, 10 Jun 2000 15:20:25 -0400 From: Kimmo Suominen Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been applied. + Kim | From: "Andrey A. Chernov" | Date: Fri, 21 Apr 2000 08:36:12 +0400 | | --- tc.prompt.c.bak Thu Apr 20 11:47:23 2000 | +++ tc.prompt.c Fri Apr 21 08:31:17 2000 | @@ -222,7 +222,7 @@ | fmthist('R', info, (char *) (cz = cbuff), sizeof(cbuff)); | else | cz = (unsigned char *) str; | - if (str != NULL) | + if (cz != NULL) | for (; *cz; *p++ = attributes | *cz++) | if (p >= ep) break; | break; | @@ -477,7 +477,7 @@ | case 'w': | if (p >= ep - 5) break; | for (cz = (unsigned char *) month_list[t->tm_mon]; *cz; | - *p++ = attributes | *cz++); | + *p++ = attributes | *cz++) | if (p >= ep) break; | break; | case 'W': | -- | Andrey A. Chernov | | http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 13: 8:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 8ABDE37B586 for ; Sat, 10 Jun 2000 13:08:43 -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 e5AK8Tc05880; Sat, 10 Jun 2000 13:08:29 -0700 (PDT) Date: Sat, 10 Jun 2000 13:08:29 -0700 (PDT) From: Doug White To: John Hengstler Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot Manager In-Reply-To: <003f01bfd251$0c6fca20$83a3ded1@hei.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 Fri, 9 Jun 2000, John Hengstler wrote: > Greetings, > > What is the quick way to restore the boot manager (dual os). Lost it when I > reloaded Win98. man boot0cfg 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 Sat Jun 10 14:29:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from node1457.a2000.nl (node1457.a2000.nl [62.108.20.87]) by hub.freebsd.org (Postfix) with ESMTP id 1695F37BCE9 for ; Sat, 10 Jun 2000 14:29:28 -0700 (PDT) (envelope-from freebsd@node1457.a2000.nl) Received: from localhost (freebsd@localhost) by node1457.a2000.nl (8.9.3/8.9.3) with SMTP id XAA20648 for ; Sat, 10 Jun 2000 23:29:35 +0200 Date: Sat, 10 Jun 2000 23:29:35 +0200 (MET DST) From: Bart Thate To: freebsd-current@freebsd.org Subject: Jail panics on 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 Hi .. if i try to run /etc/rc of my jail with the following: /usr/sbin/jail /extra/panic panic 192.168.10.7 /bin/sh /etc/rc i get an panic on: FreeBSD du.1st.dudi.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jun 9 19:02:27 CEST 2000 bart@du.1st.dudi.org:/usr/src2/sys/compile/1st.dummynet i386 snap of gdb -k : (23:24:16):root:1st.debug# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.3 (kgdb) core-file /var/crash/vmcore.3 IdlePTD 3153920 initial pcb at 284fc0 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01705b5 stack pointer = 0x10:0xca35dee8 frame pointer = 0x10:0xca35def4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 33996 (inetd) interrupt mask = none panic: from debugger panic: from debugger Uptime: 14m45s dumping to dev #ad/0x20011, offset 262144 dump ata1: resetting devices .. done 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 #1 0xc01522c9 in panic (fmt=0xc0236bd4 "from debugger") at ../../kern/kern_shutdown.c:553 #2 0xc0128f7d in db_panic (addr=-1072233035, have_addr=0, count=-1, modif=0xca35dd54 "") at ../../ddb/db_command.c:433 #3 0xc0128f1b in db_command (last_cmdp=0xc0266b5c, cmd_table=0xc02669bc, aux_cmd_tablep=0xc0280f48) at ../../ddb/db_command.c:333 #4 0xc0128fe2 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc012b247 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xc020e0da in kdb_trap (type=12, code=0, regs=0xca35dea8) at ../../i386/i386/db_interface.c:158 #7 0xc021a634 in trap_fatal (frame=0xca35dea8, eva=4) at ../../i386/i386/trap.c:922 #8 0xc021a2fd in trap_pfault (frame=0xca35dea8, usermode=0, eva=4) at ../../i386/i386/trap.c:820 #9 0xc0219eaf in trap (frame={tf_fs = -1072431088, tf_es = 16, tf_ds = -912982000, tf_edi = 2, tf_esi = 0, tf_ebp = -902439180, tf_isp = -902439212, tf_ebx = 0, tf_edx = -902439128, tf_ecx = 0, tf_eax = -912942112, tf_trapno = 12, tf_err = 0, tf_eip = -1072233035, tf_cs = 8, tf_eflags = 66050, tf_esp = 0, tf_ss = -902439040}) at ../../i386/i386/trap.c:426 #10 0xc01705b5 in socreate (dom=28, aso=0xca35df20, type=2, proto=0, p=0xc9959be0) at ../../kern/uipc_socket.c:138 ---Type to continue, or q to quit--- #11 0xc0173c79 in socket (p=0xc9959be0, uap=0xca35df80) at ../../kern/uipc_syscalls.c:119 #12 0xc021a931 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077939036, tf_esi = -1077938908, tf_ebp = -1077939004, tf_isp = -902438956, tf_ebx = 269511812, tf_edx = -1077938908, tf_ecx = 269503024, tf_eax = 97, tf_trapno = 12, tf_err = 2, tf_eip = 269225128, tf_cs = 31, tf_eflags = 663, tf_esp = -1077939080, tf_ss = 47}) at ../../i386/i386/trap.c:1126 #13 0xc020ea15 in Xint0x80_syscall () #14 0x100b0f1a in ?? () #15 0x8049cab in ?? () #16 0x8049aa1 in ?? () (kgdb) Hope this helps .. if i can be of any assistance let me know. Grtx, Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 14:31:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BF09A37C814; Sat, 10 Jun 2000 14:31:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA58437; Sat, 10 Jun 2000 14:31:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 10 Jun 2000 14:31:23 -0700 (PDT) From: Kris Kennaway To: "Andrey A. Chernov" Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: <20000609234634.A50676@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 Fri, 9 Jun 2000, Andrey A. Chernov wrote: > On Fri, Jun 09, 2000 at 11:23:58PM -0700, Andrey A. Chernov wrote: > > > would be the way to go: 64^6 = 2^36 possibilities which is nice... > > > > 1) Just totally opposite: mixing random with non-random sources you'll get > > into collision much faster then with random source only. 2) Yet, of course, > > the code handles collisions. > > Part 2) need to be clarified too. The code _attempt_ to handle collision, > but collision race can occurse between two processes checking for collision, > so getpid() insertion prevents this. I am not against of removing > getpid() code totally, just against of "randomization" of it, suggested in > the patch, which increase collision chance. The patch doesn't do this -at present it only XORs getpid() with a single random bit which is untouched by getpid() (since PIDs will only be less than 99999). Obviously, overwriting bits which are actually returned from getpid() would be stupid since it turns them totally random and thereby invalidates their use for collision protection. Given the other replies in this thread I think I'll just remove the PID stuff altogether and make the temp filename only constructed from alphanumeric character. The price is that there's a chance of collision between two programs who mktemp() and come up with the same random filename, which is a theoretical security risk (at present only something with the same PID can come up with a colliding tempfile name) but the probability is altogether pretty small. I'll do some calculations to estimate the exact level of risk here. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 15: 0:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 44B8B37C780; Sat, 10 Jun 2000 15:00:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA62152; Sat, 10 Jun 2000 15:00:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 10 Jun 2000 15:00:43 -0700 (PDT) From: Kris Kennaway To: "Andrey A. Chernov" Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch 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, 10 Jun 2000, Kris Kennaway wrote: > Given the other replies in this thread I think I'll just remove the PID > stuff altogether and make the temp filename only constructed from > alphanumeric character. The price is that there's a chance of collision > between two programs who mktemp() and come up with the same random > filename, which is a theoretical security risk (at present only something > with the same PID can come up with a colliding tempfile name) but the > probability is altogether pretty small. I'll do some calculations to > estimate the exact level of risk here. Actually, it's not of course a security risk in the new algorithm (this is mktemp() after all), but it's a potential failure mode which can cause applications to fail in ways they otherwise wouldn't (with some very low probability) on a normal system. But, I don't think it's a big enough problem to worry about (numbers still coming :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 15:13:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id D7A1A37BD83; Sat, 10 Jun 2000 15:13:28 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 3436749; Sat, 10 Jun 2000 18:13:20 -0400 (AST) Message-ID: <3942BD80.F7354092@vangelderen.org> Date: Sat, 10 Jun 2000 18:13:20 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: "Andrey A. Chernov" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 10 Jun 2000, Kris Kennaway wrote: > > > Given the other replies in this thread I think I'll just remove the PID > > stuff altogether and make the temp filename only constructed from > > alphanumeric character. The price is that there's a chance of collision > > between two programs who mktemp() and come up with the same random > > filename, which is a theoretical security risk (at present only something > > with the same PID can come up with a colliding tempfile name) but the > > probability is altogether pretty small. I'll do some calculations to > > estimate the exact level of risk here. > > Actually, it's not of course a security risk in the new algorithm (this is > mktemp() after all), but it's a potential failure mode which can cause > applications to fail in ways they otherwise wouldn't (with some very low > probability) on a normal system. But, I don't think it's a big enough > problem to worry about (numbers still coming :-) It's not a new situation, any application that can write to /tmp can create files that collide with other program's use of mktemp(). Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 15:22:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 58F0237BDA4; Sat, 10 Jun 2000 15:22:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA68055; Sat, 10 Jun 2000 15:22:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 10 Jun 2000 15:22:25 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: "Andrey A. Chernov" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch In-Reply-To: <3942BD80.F7354092@vangelderen.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, 10 Jun 2000, Jeroen C. van Gelderen wrote: > > Actually, it's not of course a security risk in the new algorithm (this is > > mktemp() after all), but it's a potential failure mode which can cause > > applications to fail in ways they otherwise wouldn't (with some very low > > probability) on a normal system. But, I don't think it's a big enough > > problem to worry about (numbers still coming :-) > > It's not a new situation, any application that can write to /tmp can > create files that collide with other program's use of mktemp(). Not under the current mktemp() since the PID is unique (except for wraparounds) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 15:27:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id B9DF437BDB1; Sat, 10 Jun 2000 15:27:38 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id A5DFB4D; Sat, 10 Jun 2000 18:27:15 -0400 (AST) Message-ID: <3942C0C3.D06003DB@vangelderen.org> Date: Sat, 10 Jun 2000 18:27:15 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: "Andrey A. Chernov" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 10 Jun 2000, Jeroen C. van Gelderen wrote: > > > > Actually, it's not of course a security risk in the new algorithm (this is > > > mktemp() after all), but it's a potential failure mode which can cause > > > applications to fail in ways they otherwise wouldn't (with some very low > > > probability) on a normal system. But, I don't think it's a big enough > > > problem to worry about (numbers still coming :-) > > > > It's not a new situation, any application that can write to /tmp can > > create files that collide with other program's use of mktemp(). > > Not under the current mktemp() since the PID is unique (except for > wraparounds) mktemp() is not the only function that creates files in /tmp. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 16:41:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 65D2D37BA59 for ; Sat, 10 Jun 2000 16:41:39 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA03051 for ; Sat, 10 Jun 2000 16:41:39 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 10 Jun 2000 16:41:38 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Subject: 4.x buildworlds broken on -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 Recent compiler changes seem to have broken the ability to do 4.x buildworlds under -current - I've tested this on beast.freebsd.org and my own machines and got the same result. The build dies during the compiler phase with lots of stuff like: /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o): In function `finish_function': c-decl.o(.text+0x8360): multiple definition of `finish_function' decl.o(.text+0x10880): first defined here /usr/libexec/elf/ld: Warning: size of symbol `finish_function' changed from 3003 to 565 in c-decl.o /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o): In function `implicitly_declare': c-decl.o(.text+0x2a81): undefined reference to `maybe_objc_check_decl' /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o): In function `finish_decl': c-decl.o(.text+0x4b1c): undefined reference to `maybe_objc_check_decl' c-decl.o(.text+0x4b51): undefined reference to `maybe_objc_check_decl' c-decl.o(.text+0x4bce): undefined reference to `maybe_objc_check_decl' /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o): In function `grokfield': c-decl.o(.text+0x6a92): undefined reference to `maybe_objc_check_decl' /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o)(.text+0x7077): more undefined references to `maybe_objc_check_decl' follow *** Error code 1 1 error On a related note, are there any freebsd.org machines which are still 4.x which can be used for buildworld testing? I used to use beast, but it's now 5.0 as well. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 17:40:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7100337B84F; Sat, 10 Jun 2000 17:40:13 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e5B0eB514121; Sat, 10 Jun 2000 20:40:12 -0400 (EDT) Date: Sat, 10 Jun 2000 20:40:12 -0400 (EDT) From: Luoqi Chen Message-Id: <200006110040.e5B0eB514121@lor.watermarkgroup.com> To: dcs@newsguy.com Subject: Re: VMware detection code in boot loader Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As for setting registers ti specific values... huh? Why does this > matter? Can you explain exactly what your code does and how? > VMware intercepts the inb/outb instruction to port 0x5658 when the eax register is set to a magic value, otherwise it would be handled as any other ports. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 18: 1:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 1538D37B960; Sat, 10 Jun 2000 18:01:29 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA11913; Sat, 10 Jun 2000 18:05:25 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006110105.SAA11913@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Luoqi Chen Cc: dcs@newsguy.com, current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader In-reply-to: Your message of "Sat, 10 Jun 2000 20:40:12 EDT." <200006110040.e5B0eB514121@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Jun 2000 18:05:25 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As for setting registers ti specific values... huh? Why does this > > matter? Can you explain exactly what your code does and how? > > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax > register is set to a magic value, otherwise it would be handled as any > other ports. I think, again, that adding an i386-specific word that detects the presence of VMware is a perfectly sensible idea, and it should simply be done. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 18:24:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.194.18]) by hub.freebsd.org (Postfix) with ESMTP id 856F137B68C for ; Sat, 10 Jun 2000 18:24:29 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id VAA01541 for freebsd-current@freebsd.org; Sat, 10 Jun 2000 21:24:28 -0400 (EDT) (envelope-from ray) Date: Sat, 10 Jun 2000 21:24:28 -0400 From: Ray Kohler To: freebsd-current@freebsd.org Subject: strange messages at bootup Message-ID: <20000610212428.A1523@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just came over from 4.0 yesterday, and now I get some odd messages that weren't there before. unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x100000-0x4feffff,0x4ff0000-0x4ff7fff,0x4ff8000-0x4ffffff,0xfffc0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x73 irq 8 on isa0 unknown: can't assign resources unknown4: at port 0x61 on isa0 npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown5: at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: on isa0 unknown7: at port 0xcf8-0xcff on isa0 unknown8: at port 0x3f8-0x3ff irq 4 on isa0 unknown9: on isa0 unknown: can't assign resources unknown: can't assign resources What are these? Are they possibly related to my mouse no longer working (it's not the "out of sync" problem)? How can I get rid of them? I think they are from the ppbus driver checking for attached devices, I'll put the entire dmesg here for context. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #4: Sat Jun 10 16:09:51 EDT 2000 ray@rjk191.rh.psu.edu:/usr/src/sys/compile/RJK191 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046041 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 83820544 (81856K bytes) avail memory = 78753792 (76908K bytes) Preloaded elf kernel "kernel" at 0xc02c0000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 10 pci0: at 7.3 pci0: at 10.0 irq 11 pcm0: port 0xee80-0xeebf irq 10 at device 11.0 on pci0 pci0: (vendor=0x109e, dev=0x0350) at 18.0 irq 10 xl0: <3Com 3c900-TPO Etherlink XL> port 0xef00-0xef3f irq 11 at device 19.0 on pci0 xl0: Ethernet address: 00:60:97:6d:9c:d8 xl0: selecting 10baseT transceiver, half duplex fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: SCP,VLINK lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x100000-0x4feffff,0x4ff0000-0x4ff7fff,0x4ff8000-0x4ffffff,0xfffc0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x73 irq 8 on isa0 unknown: can't assign resources unknown4: at port 0x61 on isa0 npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown5: at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: on isa0 unknown7: at port 0xcf8-0xcff on isa0 unknown8: at port 0x3f8-0x3ff irq 4 on isa0 unknown9: on isa0 unknown: can't assign resources unknown: can't assign resources ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s2a lpt0: switched to polled standard mode -- Ray Kohler FreeBSD -- The Power to Serve The lion and the calf shall lie down together but the calf won't get much sleep. -- Woody Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 19:23: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id AED6437BE9C; Sat, 10 Jun 2000 19:22:59 -0700 (PDT) Date: Sat, 10 Jun 2000 19:22:59 -0700 From: "Andrey A. Chernov" To: Kris Kennaway Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610192259.A99504@freebsd.org> References: <20000609234634.A50676@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kris@FreeBSD.org on Sat, Jun 10, 2000 at 02:31:23PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 02:31:23PM -0700, Kris Kennaway wrote: > between two programs who mktemp() and come up with the same random > filename, which is a theoretical security risk (at present only something > with the same PID can come up with a colliding tempfile name) but the > probability is altogether pretty small. I'll do some calculations to > estimate the exact level of risk here. Please note that you turn never probavility into small one, and it is degradation. "never" is not completely never, of course, but if temp file stays until pids wrapped. -- 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 Sat Jun 10 19:36:12 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 4DF9B37BE79; Sat, 10 Jun 2000 19:36:10 -0700 (PDT) Date: Sat, 10 Jun 2000 19:36:10 -0700 From: "Andrey A. Chernov" To: Matthew Dillon Cc: "Jeroen C. van Gelderen" , Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610193610.B99504@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> <20000609232358.A38967@freebsd.org> <200006100653.XAA17619@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200006100653.XAA17619@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Jun 09, 2000 at 11:53:34PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 09, 2000 at 11:53:34PM -0700, Matthew Dillon wrote: > :1) Just totally opposite: mixing random with non-random sources you'll get > :into collision much faster then with random source only. 2) Yet, of course, > :the code handles collisions. > : > :-- > :Andrey A. Chernov > : > > Think about it. If you mix a random number with a non-random number, > using xor, what you get is.... a random number. It's neither stronger > nor weaker. No, you'll get weaker random number, it badly affects random distribution. OR or AND will affect more. What you say is true only if second XOR part is 0 or -1 or changed between them or simple constant. I.e. if not _all_ bits XORed in the same way, it affects. -- 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 Sat Jun 10 19:43: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 465B937BE8C; Sat, 10 Jun 2000 19:43:06 -0700 (PDT) Date: Sat, 10 Jun 2000 19:43:06 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: "Jeroen C. van Gelderen" , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610194306.C99504@freebsd.org> References: <20000609232358.A38967@freebsd.org> <200006100731.JAA04819@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200006100731.JAA04819@grimreaper.grondar.za>; from mark@grondar.za on Sat, Jun 10, 2000 at 09:31:49AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 09:31:49AM +0200, Mark Murray wrote: > Incorrect. See my other mail; ${RANDOM} xor ${PREDICTABLE} is random. Only if predictable have the same bits number as random. If not all bits of random XOR-ed (i.e. half of random), it becomes weaker. BTW, if they have the same bits number, there is no reason to XOR random with predictable, random is not become more random. -- 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 Sat Jun 10 19:51: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 1EC1837BEAB; Sat, 10 Jun 2000 19:51:03 -0700 (PDT) Date: Sat, 10 Jun 2000 19:51:03 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: "Jeroen C. van Gelderen" , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610195102.D99504@freebsd.org> References: <20000609155342.B33329@freebsd.org> <200006100713.JAA04771@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200006100713.JAA04771@grimreaper.grondar.za>; from mark@grondar.za on Sat, Jun 10, 2000 at 09:13:30AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 09:13:30AM +0200, Mark Murray wrote: Well, I tend to agree that it is not weakens random, but I not see any improvement too. > That is a pretty fundamental theorem of Cryptography. My suggestion > _strengthens_ the random number. All you lose is one bit if it If it not weakers I can't see why it strenghthens. I.e. you can constantly strenghthens generator with passing it through XOR -1? If not, why any other value is better than -1? -- 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 Sat Jun 10 19:52:15 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 07D2237BE79; Sat, 10 Jun 2000 19:52:14 -0700 (PDT) Date: Sat, 10 Jun 2000 19:52:14 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: "Jeroen C. van Gelderen" , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610195213.E99504@freebsd.org> References: <20000609232358.A38967@freebsd.org> <200006100731.JAA04819@grimreaper.grondar.za> <20000610194306.C99504@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000610194306.C99504@freebsd.org>; from ache@freebsd.org on Sat, Jun 10, 2000 at 07:43:06PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 07:43:06PM -0700, Andrey A. Chernov wrote: > On Sat, Jun 10, 2000 at 09:31:49AM +0200, Mark Murray wrote: > > Incorrect. See my other mail; ${RANDOM} xor ${PREDICTABLE} is random. > > Only if predictable have the same bits number as random. If not all bits of > random XOR-ed (i.e. half of random), it becomes weaker. Forget this, I change my mind here. > BTW, if they have the same bits number, > there is no reason to XOR random with predictable, random is not become > more random. But still confirm this. -- 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 Sat Jun 10 19:54:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id D62FB37BE79; Sat, 10 Jun 2000 19:54:31 -0700 (PDT) Date: Sat, 10 Jun 2000 19:54:31 -0700 From: "Andrey A. Chernov" To: Matthew Dillon Cc: "Jeroen C. van Gelderen" , Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: mktemp() patch Message-ID: <20000610195431.F99504@freebsd.org> References: <394124C3.221E61BC@vangelderen.org> <200006092002.WAA00773@grimreaper.grondar.za> <20000609155342.B33329@freebsd.org> <39417FA5.F260EAA8@vangelderen.org> <20000609232358.A38967@freebsd.org> <200006100653.XAA17619@apollo.backplane.com> <20000610193610.B99504@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000610193610.B99504@freebsd.org>; from ache@freebsd.org on Sat, Jun 10, 2000 at 07:36:10PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 07:36:10PM -0700, Andrey A. Chernov wrote: > On Fri, Jun 09, 2000 at 11:53:34PM -0700, Matthew Dillon wrote: > > :1) Just totally opposite: mixing random with non-random sources you'll get > > :into collision much faster then with random source only. 2) Yet, of course, > > :the code handles collisions. > > : > > :-- > > :Andrey A. Chernov > > : > > > > Think about it. If you mix a random number with a non-random number, > > using xor, what you get is.... a random number. It's neither stronger > > nor weaker. > > No, you'll get weaker random number, it badly affects random distribution. Forget this, I change my mind. It is not weaker, but not strengtenth 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 Sat Jun 10 20:19: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 1D3BA37B7F2 for ; Sat, 10 Jun 2000 20:19:03 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 5052 invoked by uid 1001); 11 Jun 2000 03:19:01 -0000 Date: Sat, 10 Jun 2000 23:19:01 -0400 From: Brian Reichert To: rjk191@psu.edu Cc: freebsd-current@freebsd.org Subject: Re: strange messages at bootup Message-ID: <20000610231901.A5028@numachi.com> References: <20000610212428.A1523@rjk191.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000610212428.A1523@rjk191.rh.psu.edu>; from ray@rjk191.rh.psu.edu on Sat, Jun 10, 2000 at 09:24:28PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 09:24:28PM -0400, Ray Kohler wrote: > I just came over from 4.0 yesterday, and now I get some odd messages > that weren't there before. > > unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x100000-0x4feffff,0x4ff0000-0x4ff7fff,0x4ff8000-0x4ffffff,0xfffc0000-0xffffffff on isa0 I would hazard the guess that you now have the PNPBIOS directive in your kernel config file... > -- > Ray Kohler > FreeBSD -- The Power to Serve > The lion and the calf shall lie down together but the calf won't get > much sleep. > -- Woody Allen > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 21:30:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.194.18]) by hub.freebsd.org (Postfix) with ESMTP id 71C2437B6FF for ; Sat, 10 Jun 2000 21:30:46 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id AAA00403 for freebsd-current@freebsd.org; Sun, 11 Jun 2000 00:30:45 -0400 (EDT) (envelope-from ray) Date: Sun, 11 Jun 2000 00:30:45 -0400 From: Ray Kohler To: freebsd-current@freebsd.org Subject: Re: strange messages at bootup Message-ID: <20000611003045.A386@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu References: <20000610212428.A1523@rjk191.rh.psu.edu> <20000610231901.A5028@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000610231901.A5028@numachi.com>; from reichert@numachi.com on Sat, Jun 10, 2000 at 11:19:01PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 11:19:01PM -0400, Brian Reichert wrote: > On Sat, Jun 10, 2000 at 09:24:28PM -0400, Ray Kohler wrote: > > I just came over from 4.0 yesterday, and now I get some odd messages > > that weren't there before. > > > > unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x100000-0x4feffff,0x4ff0000-0x4ff7fff,0x4ff8000-0x4ffffff,0xfffc0000-0xffffffff on isa0 > > I would hazard the guess that you now have the PNPBIOS directive > in your kernel config file... Actually, I don't have PnP in my config file. That's why I think this is so weird... -- Ray Kohler FreeBSD -- The Power to Serve Speak softly and carry a +6 two-handed sword. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 21:33:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id A9E6D37B7DB for ; Sat, 10 Jun 2000 21:33:52 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 1343D10D; Sat, 10 Jun 2000 21:33:52 -0700 (PDT) Date: Sat, 10 Jun 2000 21:33:51 -0700 From: Chris Piazza To: Ray Kohler Cc: freebsd-current@freebsd.org Subject: Re: strange messages at bootup Message-ID: <20000610213351.A362@norn.ca.eu.org> References: <20000610212428.A1523@rjk191.rh.psu.edu> <20000610231901.A5028@numachi.com> <20000611003045.A386@rjk191.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mutt 1.0.1i-jp0 In-Reply-To: <20000611003045.A386@rjk191.rh.psu.edu>; from ray@rjk191.rh.psu.edu on Sun, Jun 11, 2000 at 12:30:45AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 11, 2000 at 12:30:45AM -0400, Ray Kohler wrote: > On Sat, Jun 10, 2000 at 11:19:01PM -0400, Brian Reichert wrote: > > I would hazard the guess that you now have the PNPBIOS directive > > in your kernel config file... > > Actually, I don't have PnP in my config file. That's why I think > this is so weird... It's on by default now. -Chris -- cpiazza@jaxon.net | yawn..... cpiazza@FreeBSD.org | Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 21:38: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.194.18]) by hub.freebsd.org (Postfix) with ESMTP id 8936137B7DB for ; Sat, 10 Jun 2000 21:37:57 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id AAA00435 for freebsd-current@freebsd.org; Sun, 11 Jun 2000 00:37:57 -0400 (EDT) (envelope-from ray) Date: Sun, 11 Jun 2000 00:37:57 -0400 From: Ray Kohler To: freebsd-current@freebsd.org Subject: Re: strange messages at bootup Message-ID: <20000611003757.C386@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu References: <20000610212428.A1523@rjk191.rh.psu.edu> <20000610231901.A5028@numachi.com> <20000611003045.A386@rjk191.rh.psu.edu> <20000610213351.A362@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000610213351.A362@norn.ca.eu.org>; from cpiazza@jaxon.net on Sat, Jun 10, 2000 at 09:33:51PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 09:33:51PM -0700, Chris Piazza wrote: > On Sun, Jun 11, 2000 at 12:30:45AM -0400, Ray Kohler wrote: > > On Sat, Jun 10, 2000 at 11:19:01PM -0400, Brian Reichert wrote: > > > I would hazard the guess that you now have the PNPBIOS directive > > > in your kernel config file... > > > > Actually, I don't have PnP in my config file. That's why I think > > this is so weird... > > It's on by default now. Can I turn it off somehow? Or otherwise fix it? -- Ray Kohler FreeBSD -- The Power to Serve Pure drivel tends to drive ordinary drivel off the TV screen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 22:11:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AB3CE37BECE for ; Sat, 10 Jun 2000 22:11:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA24596; Sat, 10 Jun 2000 22:11:32 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Jun 2000 22:11:32 -0700 (PDT) From: Matthew Dillon Message-Id: <200006110511.WAA24596@apollo.backplane.com> To: Jonathan Hanna Cc: freebsd-current@FreeBSD.ORG Subject: Re: RE: Strange rpc.statd and mount_nfs References: <200006101833.LAA04816@cr1003333-a.crdva1.bc.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Here is a rather suspicious fix, I have not looked at rpc call :use in detail: : :--- mount_nfs.c.orig Sat Jun 10 11:08:19 2000 :+++ mount_nfs.c Sat Jun 10 11:09:06 2000 :@@ -784,10 +784,11 @@ : warnx("%s", clnt_sperror(clp, : "bad MNT RPC")); : } else { :- auth_destroy(clp->cl_auth); :- clnt_destroy(clp); : retrycnt = 0; : } :+ auth_destroy(clp->cl_auth); :+ clnt_destroy(clp); :+ so = RPC_ANYSOCK; Good catch! This patch looks good to me, I am going to go ahead and commit it. Resetting 'so' is good code form, but I went through the rpc code and it wasn't an operational bug ... the rpc code can overwrite so in the case of a failure but only with '-1', which is RPC_ANYSOCK anyway. Still, it's good not to make assumptions. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 10 23:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id E328237BF0D for ; Sat, 10 Jun 2000 23:43:48 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 24990 invoked from network); 11 Jun 2000 06:43:45 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 11 Jun 2000 06:43:45 -0000 Date: Sun, 11 Jun 2000 16:43:41 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: 4.x buildworlds broken on -current 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, 10 Jun 2000, Kris Kennaway wrote: > Recent compiler changes seem to have broken the ability to do 4.x > buildworlds under -current - I've tested this on beast.freebsd.org and my > own machines and got the same result. The build dies during the compiler > phase with lots of stuff like: > > /morden/usr3/tmp/obj//morden/usr3/tmp/src/i386/morden/usr3/tmp/src/gnu/usr.bin/cc/cc1plus/../cc_int/libcc_int.a(c-decl.o): In > function `finish_function': > c-decl.o(.text+0x8360): multiple definition of `finish_function' > decl.o(.text+0x10880): first defined here > /usr/libexec/elf/ld: Warning: size of symbol `finish_function' changed > from 3003 to 565 in c-decl.o > ... This is a bug in the cc Makefiles in 4.x. It was fixed in -current in: # RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_int/Makefile,v # Working file: Makefile # head: 1.26 # ... # ---------------------------- # revision 1.26 # date: 2000/05/24 20:02:21; author: obrien; state: Exp; lines: +2 -2 # Move c-decl.c out of the common libcc_int.a into the binary Makefiles # where it is used. c-decl has symbols that conflict with several of the # cc1plus sources. # # GNU `ld' was changed in Dec 1999 to be more be compatable with the way that # other linkers work (specifically in the Solaris linker). The 2.9.1 `ld', # did the Wrong Thing in that if a library contained a common symbol that # matched a definition of that symbol in another (already linked in object) # it would also be linked in, even if there was no other reason to do so. # This is wrong. The library should only be linked in if it contains # non-common, non-weak symbols which are needed by previously linked in # objects. # ---------------------------- etc. This could be fixed by MFC to RELENG_4, but bootstrapping from 4.0, 3.x and 2.x is much harder to fix. Building old kernels under -current is becoming difficult. I build kernels for RELENG_3 and RELENG_4. This causes a lot of new warnings about invalid assembler, but still works, at least a week ago. I left genassym(1) in /usr/bin to avoid breaking the build of RELENG_4 kernels until the genassym changes are MFC'ed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message