From owner-freebsd-current Sun Jul 1 0:13:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.plug.cx (unix-gw.gihs.sa.edu.au [203.63.40.115]) by hub.freebsd.org (Postfix) with ESMTP id 9365E37B408 for ; Sun, 1 Jul 2001 00:13:42 -0700 (PDT) (envelope-from andrew.reid@plug.cx) Received: from popadl-06-041.picknowl.com.au (firewall.gihs.sa.edu.au [192.168.1.1]) by mail.plug.cx (Postfix) with ESMTP id F14D82B7EB; Sun, 1 Jul 2001 17:03:09 +0000 (GMT) Subject: Re: wierd build error with -current From: Andrew Reid To: mjacob@feral.com Cc: current@freebsd.org In-Reply-To: <20010630215849.S19736-100000@wonky.feral.com> References: <20010630215849.S19736-100000@wonky.feral.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 01 Jul 2001 16:34:27 +0930 Message-Id: <993971070.1729.0.camel@percible.alfred.cx> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 30 Jun 2001 21:59:19 -0700, Matthew Jacob wrote: > I'm sure you're right. I guess I need to go fix the breakage. > > It's supposed to work. Things get built in /usr/obj, not /usr/src. Hrm, OK. That's something I didn't know. I'm assuming that you've tried mounting /usr/src as read-write and tried compiling again? - andrew -- void signature () { cout << "Andrew Reid -- andrew.reid@plug.cx" << endl ; cout << "Cell: +61 401 946 813" << endl; cout << "Quidquid latine dictum sit, altum viditur" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 5:21:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id A37BD37B401 for ; Sun, 1 Jul 2001 05:21:21 -0700 (PDT) (envelope-from ncbp@bank-pedersen.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 7D8C35D6A; Sun, 1 Jul 2001 14:21:20 +0200 (CEST) Date: Sun, 1 Jul 2001 14:21:20 +0200 From: "Niels Chr. Bank-Pedersen" To: current@freebsd.org Subject: ipfilter+ipv6 - what am I missing? Message-ID: <20010701142120.C770@bank-pedersen.dk> Mail-Followup-To: "Niels Chr. Bank-Pedersen" , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 18D0 73F3 767F 3A40 CEBA C595 4783 D7F5 5DD1 FB8C X-PGP-Public-Key: http://freesbee.wheel.dk/~ncbp/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On yesterdays -current I'm having some problems making ipfilter DTRT with ipv6 packets: bm# ipfstat -6io block out quick on xl0 from any to any block out quick on vx0 from any to any block in quick on xl0 from any to any block in quick on vx0 from any to any (passing ipv6 traffic) bm# ipfstat -6 IPv6 packets: in 0 out 0 Even with the above ruleset installed, ipfilter doesn't block any traffic at all, and counters for ipv6 packets remains at zero while successfully running various ipv6 sessions through the firewall, so what am I missing here? Feel free to flame me if I am missing the obvious :-) /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 6:28:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from femail18.sdc1.sfba.home.com (femail18.sdc1.sfba.home.com [24.0.95.145]) by hub.freebsd.org (Postfix) with ESMTP id 8C74237B401 for ; Sun, 1 Jul 2001 06:28:40 -0700 (PDT) (envelope-from mdharnois@home.com) Received: from c1030098-a.wtrlo1.ia.home.com ([24.6.200.230]) by femail18.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010701132840.QFKC22639.femail18.sdc1.sfba.home.com@c1030098-a.wtrlo1.ia.home.com> for ; Sun, 1 Jul 2001 06:28:40 -0700 Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 5BE1914A02; Sun, 1 Jul 2001 08:29:23 -0500 (CDT) To: freebsd-current@freebsd.org Subject: can't build kernel: config doesn't work From: Michael Harnois Date: Sun, 01 Jul 2001 08:29:22 -0500 Message-ID: <86pubklqvh.fsf@mharnois.workgroup.net> Lines: 9 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (anise) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Truly bizarre. Running config does nothing, although it generates the usual messages. I tried deleting my kernel object directory after an odd failure; ran config again, it didn't even recreate the directory. -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa "Everyone thinks of changing the world, but no one thinks of changing himself." -- Leo Nikolaevich Tolstoy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 6:42:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (Postfix) with ESMTP id 0581937B401 for ; Sun, 1 Jul 2001 06:42:24 -0700 (PDT) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (natto.tydfam.machida.tokyo.jp [210.161.209.131]) by tydfam.machida.tokyo.jp (8.11.3/8.11.3) with ESMTP id f61DgGa76437 for ; Sun, 1 Jul 2001 22:42:16 +0900 (JST) (envelope-from ken@tydfam.machida.tokyo.jp) To: freebsd-current@FreeBSD.ORG Subject: Re: can't build kernel: config doesn't work X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Cuyahoga Valley) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010701224216A.ken@tydfam.machida.tokyo.jp> Date: Sun, 01 Jul 2001 22:42:16 +0900 From: Takeshi Ken Yamada X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The same here, but 'config -d /sys/compile/GENERIC GENERIC' did what it is supposed to do. Is this a new specification of 'config', or bug? From: Michael Harnois Subject: can't build kernel: config doesn't work mdharnois> Truly bizarre. Running config does nothing, although it generates the mdharnois> usual messages. I tried deleting my kernel object directory after an mdharnois> odd failure; ran config again, it didn't even recreate the directory. mdharnois> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 6:58:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A2B2737B403 for ; Sun, 1 Jul 2001 06:58:17 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA16033; Sun, 1 Jul 2001 15:58:16 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: blockable sleep lock panic (and dumps still don't work) From: Dag-Erling Smorgrav Date: 01 Jul 2001 15:58:15 +0200 Message-ID: Lines: 87 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "microuptime() went backwards" warning caused a "blockable sleep lock" panic on a June 25 kernel: panic: blockable sleep lock (sx) allproc @ ../../kern/kern_proc.c:146 Debugger("panic") Stopped at Debugger+0x44: pushl %ebx db> trace Debugger(c02c7cfb) at Debugger+0x44 panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 tputchar(6d,c2ad1620) at tputchar+0x35 putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- db> x/s 0xx02c7700 Bad character in number db> x/s 0xc02c7700 pgrpdump_cmd+0x358: microuptime() went backwards (%ld.%06ld -> %ld.%06ld)\012 db> panic panic: from debugger Uptime: 4d23h47m42s dumping to dev ad1b, offset 7340064 dump ata1: resetting devices .. ad1: invalidating queued requests panic: mutex sched lock recursed at ../../kern/kern_synch.c:826 Uptime: 4d23h47m42s kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc01c7933 stack pointer = 0x10:0xdc3ae904 frame pointer = 0x10:0xdc3ae910 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 68314 (cvsup) kernel: type 12 trap, code=0 Stopped at Debugger+0x44: pushl %ebx db> trace Debugger(c02c7cfb) at Debugger+0x44 panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 tputchar(6d,c2ad1620) at tputchar+0x35 putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- db> reboot No such command db> call boot syncing disks... 34 34 panic: runq_add: proc 0xdc3abc80 (cvsup) not SRUN Uptime: 4d23h49m41s panic: lockmgr: locking against myself Uptime: 4d23h49m41s panic: lockmgr: locking against myself Uptime: 4d23h49m41s panic: lockmgr: locking against myself [ad nauseam] DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 7: 7:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from iatl0x01.coxmail.com (iatl1x01.coxmail.com [206.157.231.23]) by hub.freebsd.org (Postfix) with ESMTP id A161C37B403 for ; Sun, 1 Jul 2001 07:07:05 -0700 (PDT) (envelope-from mheffner@novacoxmail.com) Received: from enterprise.muriel.penguinpowered.com ([208.138.198.178]) by iatl0x01.coxmail.com (InterMail vK.4.03.02.00 201-232-124 license 85f4f10023be2bd3bce00b3a38363ea2) with ESMTP id <20010701140659.OWZS1034.iatl0x01@enterprise.muriel.penguinpowered.com>; Sun, 1 Jul 2001 10:06:59 -0400 Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.5.0.FreeBSD:20010701100554:359=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <20010701224216A.ken@tydfam.machida.tokyo.jp> Date: Sun, 01 Jul 2001 10:05:54 -0400 (EDT) Reply-To: Mike Heffner From: Mike Heffner To: Takeshi Ken Yamada Subject: Re: can't build kernel: config doesn't work Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.5.0.FreeBSD:20010701100554:359=_ Content-Type: text/plain; charset=us-ascii It works for me ;) Remember that the new default is: /sys/${MACHINEARCH}/compile/${KERNCONF} On 01-Jul-2001 Takeshi Ken Yamada wrote: | | The same here, but 'config -d /sys/compile/GENERIC GENERIC' | did what it is supposed to do. | | Is this a new specification of 'config', or bug? | | From: Michael Harnois | Subject: can't build kernel: config doesn't work | mdharnois> Truly bizarre. Running config does nothing, although it generates | the | mdharnois> usual messages. I tried deleting my kernel object directory after | an | mdharnois> odd failure; ran config again, it didn't even recreate the | directory. | mdharnois> | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-current" in the body of the message Mike -- Mike Heffner Fredericksburg, VA --_=XFMail.1.5.0.FreeBSD:20010701100554:359=_ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7Py5CFokZQs3sv5kRAk4RAJ4k3R4On69IqL2PZMzcIGozUyz62wCZAena yu12qKPV4QQpk3vlAy5CIcQ= =h2Wn -----END PGP SIGNATURE----- --_=XFMail.1.5.0.FreeBSD:20010701100554:359=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 8:11:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id E440E37B407 for ; Sun, 1 Jul 2001 08:11:17 -0700 (PDT) (envelope-from mark@whistle.com) Received: from [207.76.207.129] ([10.1.10.118]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA45041; Sun, 1 Jul 2001 08:09:15 -0700 (PDT) Mime-Version: 1.0 X-Sender: mark@207.76.206.1 Message-Id: In-Reply-To: References: Date: Sun, 1 Jul 2001 08:09:14 -0700 To: Mike Heffner , Takeshi Ken Yamada From: Mark Peek Subject: Re: can't build kernel: config doesn't work Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:05 AM -0400 7/1/01, Mike Heffner wrote: >It works for me ;) Remember that the new default is: > > /sys/${MACHINEARCH}/compile/${KERNCONF} > > >On 01-Jul-2001 Takeshi Ken Yamada wrote: >| >| The same here, but 'config -d /sys/compile/GENERIC GENERIC' >| did what it is supposed to do. >| >| Is this a new specification of 'config', or bug? >| >| From: Michael Harnois >| Subject: can't build kernel: config doesn't work >| mdharnois> Truly bizarre. Running config does nothing, although it generates >| the >| mdharnois> usual messages. I tried deleting my kernel object directory after >| an >| mdharnois> odd failure; ran config again, it didn't even recreate the >| directory. >| mdharnois> Right, there is a new compile directory. Perhaps this needs to be added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs tree? Or just do mkdir on the new path mentioned above. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 8:27:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by hub.freebsd.org (Postfix) with ESMTP id 3F3F537B403 for ; Sun, 1 Jul 2001 08:27:33 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.mybox.zip ([207.214.149.224]) by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GFS00IPMW9U5N@mta7.pltn13.pbi.net> for current@freebsd.org; Sun, 01 Jul 2001 08:27:32 -0700 (PDT) Received: by zippy.mybox.zip (Postfix, from userid 1000) id 04AAB180A; Sun, 01 Jul 2001 08:27:25 -0700 (PDT) Date: Sun, 01 Jul 2001 08:27:25 -0700 From: Alex Zepeda Subject: Re: can't build kernel: config doesn't work In-reply-to: <"from mark"@whistle.com> To: Mark Peek Cc: current@freebsd.org Message-id: <20010701082725.A798@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote: > Right, there is a new compile directory. Perhaps this needs to be > added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs > tree? Or just do mkdir on the new path mentioned above. It *IS* in UPDATING: Updating Information for FreeBSD current users This file is maintained and copyrighted by M. Warner Losh . Please send new entries directly to him. See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. 20010628: The kernel compile module has moved from src/sys/compile/FOO to src/sys/${MACHINE}/compile/FOO. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 8:39:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from femail18.sdc1.sfba.home.com (femail18.sdc1.sfba.home.com [24.0.95.145]) by hub.freebsd.org (Postfix) with ESMTP id 8106237B401 for ; Sun, 1 Jul 2001 08:39:42 -0700 (PDT) (envelope-from mdharnois@home.com) Received: from c1030098-a.wtrlo1.ia.home.com ([24.6.200.230]) by femail18.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010701153942.UFCN22639.femail18.sdc1.sfba.home.com@c1030098-a.wtrlo1.ia.home.com> for ; Sun, 1 Jul 2001 08:39:42 -0700 Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 7EF9414A14; Sun, 1 Jul 2001 10:40:25 -0500 (CDT) To: freebsd-current@freebsd.org Subject: Re: can't build kernel: config doesn't work References: <20010701082725.A798@zippy.mybox.zip> From: Michael Harnois In-Reply-To: <20010701082725.A798@zippy.mybox.zip> (Alex Zepeda's message of "Sun, 01 Jul 2001 08:27:25 -0700") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (anise) Date: Sun, 01 Jul 2001 10:40:25 -0500 Message-ID: <86ofr4k68m.fsf@mharnois.workgroup.net> Lines: 8 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, so it is my fault. Did I miss a HEADS UP on this? It certainly deserved one. -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa "He who will not reason is a bigot; he who cannot is a fool; and he who dares not, is a slave." -- William Drummond To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 9: 6:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 75B5C37B403 for ; Sun, 1 Jul 2001 09:06:09 -0700 (PDT) (envelope-from mark@whistle.com) Received: from [207.76.207.129] ([10.1.10.118]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA45929; Sun, 1 Jul 2001 08:59:06 -0700 (PDT) Mime-Version: 1.0 X-Sender: mark@207.76.206.1 Message-Id: In-Reply-To: <20010701082725.A798@zippy.mybox.zip> References: <20010701082725.A798@zippy.mybox.zip> Date: Sun, 1 Jul 2001 08:59:08 -0700 To: Alex Zepeda , Mark Peek From: Mark Peek Subject: Re: can't build kernel: config doesn't work Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:27 AM -0700 7/1/01, Alex Zepeda wrote: >On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote: > >> Right, there is a new compile directory. Perhaps this needs to be >> added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs >> tree? Or just do mkdir on the new path mentioned above. > >It *IS* in UPDATING: > >Updating Information for FreeBSD current users > >This file is maintained and copyrighted by M. Warner Losh >. Please send new entries directly to him. See end >of file for further details. For commonly done items, please see the >COMMON ITEMS: section later in the file. > >20010628: > The kernel compile module has moved from src/sys/compile/FOO > to src/sys/${MACHINE}/compile/FOO. Silly me, of course Warner would make sure UPDATING is correct! :-) I must have glossed over the cvs commit message for that change. I stand corrected. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 9:34:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from iatl0x01.coxmail.com (iatl1x01.coxmail.com [206.157.231.23]) by hub.freebsd.org (Postfix) with ESMTP id 6EB6937B403 for ; Sun, 1 Jul 2001 09:34:14 -0700 (PDT) (envelope-from mheffner@novacoxmail.com) Received: from enterprise.muriel.penguinpowered.com ([208.138.198.178]) by iatl0x01.coxmail.com (InterMail vK.4.03.02.00 201-232-124 license 85f4f10023be2bd3bce00b3a38363ea2) with ESMTP id <20010701163413.OYTJ1034.iatl0x01@enterprise.muriel.penguinpowered.com>; Sun, 1 Jul 2001 12:34:13 -0400 Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.5.0.FreeBSD:20010701123257:356=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Sun, 01 Jul 2001 12:32:57 -0400 (EDT) Reply-To: Mike Heffner From: Mike Heffner To: Mark Peek Subject: Re: can't build kernel: config doesn't work Cc: freebsd-current@FreeBSD.ORG, Cc: freebsd-current@FreeBSD.ORG, Takeshi Ken Yamada , Mike Heffner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.5.0.FreeBSD:20010701123257:356=_ Content-Type: text/plain; charset=us-ascii On 01-Jul-2001 Mark Peek wrote: | At 10:05 AM -0400 7/1/01, Mike Heffner wrote: |>It works for me ;) Remember that the new default is: |> |> /sys/${MACHINEARCH}/compile/${KERNCONF} | | | Right, there is a new compile directory. Perhaps this needs to be | added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs | tree? Or just do mkdir on the new path mentioned above. I just did a cvsup and ran config with no arguments, and it created the right directory for me. Mike -- Mike Heffner Fredericksburg, VA --_=XFMail.1.5.0.FreeBSD:20010701123257:356=_ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7P1C4FokZQs3sv5kRAu5CAJ9XDh407qdmMbtdbbtiMYs6DhihmACeIKzg as506HZOwi5TYD3bB1IPyy0= =AHZm -----END PGP SIGNATURE----- --_=XFMail.1.5.0.FreeBSD:20010701123257:356=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 10:47:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2623E37B403 for ; Sun, 1 Jul 2001 10:47:28 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA29958; Mon, 2 Jul 2001 03:47:17 +1000 Date: Mon, 2 Jul 2001 03:45:19 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: blockable sleep lock panic (and dumps still don't work) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 1 Jul 2001, Dag-Erling Smorgrav wrote: > "microuptime() went backwards" warning caused a "blockable sleep lock" > panic on a June 25 kernel: > > panic: blockable sleep lock (sx) allproc @ ../../kern/kern_proc.c:146 > Debugger("panic") > Stopped at Debugger+0x44: pushl %ebx > db> trace > ... > tputchar(6d,c2ad1620) at tputchar+0x35 > putchar(6d,dc3aeeb4) at putchar+0x4f > kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e > printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 > Debugger(c02c7cfb) at Debugger+0x44 > panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 > witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e > _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 > pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c > selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 > ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 > ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 > ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 > tputchar(6d,c2ad1620) at tputchar+0x35 This has something to do with the TIOCCONS ioctl. tputchar() is the output function for the TOTTY case, and the TOTTY flag is only set for kernel printfs if TIOCCONS has set constty to non-NULL. I'm not sure what uses TIOCCONS (I think it is intended for use with X, but it doesn't seem to be used on my systems). TIOCCONS is almost unimplementable (printing to a terminal is not reentrant enough to work in all contexts, and is supposed to be protected by spltty(), but kernel printfs must work in all contexts), so the correct fix may be to remove it. TIOCCONS is broken in all versions of FreeBSD. The brokenness is just more obvious now that there are more locks to trip over. The output function for the TOLOG case (i.e., msglogchar()) also seems to be broken in all versions of FreeBSD. It operates on the circular message buffer, but doesn't have any locking. The output function for the TOCONS case (i.e., cnputc()) is also problematic. Only the serial console output routine even attempts to be reentrant, and (per-cpu) reentrancy is not enough under SMP. Syscons' output routine was easy to panic by mixing kernel printfs with user-mode output the last time I checked. > putchar(6d,dc3aeeb4) at putchar+0x4f > kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e > printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 > calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b > getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 > syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 > syscall_with_err_pushed() at syscall_with_err_pushed+0x1b > --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- > ... > dumping to dev ad1b, offset 7340064 > dump ata1: resetting devices .. ad1: invalidating queued requests > panic: mutex sched lock recursed at ../../kern/kern_synch.c:826 Apparently addump() depends on too much infrastructure. A panic may occur at any time, so dump routines face much the same locking problems as console output routines. They can't go near normal locks like sched_lock, since they need to work when such locks are in any state. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 11: 0:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 8059137B401 for ; Sun, 1 Jul 2001 11:00:52 -0700 (PDT) (envelope-from matt-l@pacbell.net) Received: from fire (1Cust191.tnt1.pasadena.ca.da.uu.net [63.28.226.191]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id LAA10882; Sun, 1 Jul 2001 11:00:42 -0700 (PDT) Message-ID: <005701c10256$d5361960$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: "Niels Chr. Bank-Pedersen" , References: <20010701142120.C770@bank-pedersen.dk> Subject: Re: ipfilter+ipv6 - what am I missing? Date: Sun, 1 Jul 2001 10:54:01 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't think ipf is complete in its ipv6 support yet.You can use ipfw instead. ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== ----- Original Message ----- From: Niels Chr. Bank-Pedersen To: Sent: Sunday, July 01, 2001 5:21 AM Subject: ipfilter+ipv6 - what am I missing? > Hi, > > On yesterdays -current I'm having some problems making ipfilter > DTRT with ipv6 packets: > > bm# ipfstat -6io > block out quick on xl0 from any to any > block out quick on vx0 from any to any > block in quick on xl0 from any to any > block in quick on vx0 from any to any > > (passing ipv6 traffic) > > bm# ipfstat -6 > IPv6 packets: in 0 out 0 > > Even with the above ruleset installed, ipfilter doesn't block > any traffic at all, and counters for ipv6 packets remains at > zero while successfully running various ipv6 sessions through > the firewall, so what am I missing here? > > Feel free to flame me if I am missing the obvious :-) > > > /Niels Chr. > > -- > Niels Christian Bank-Pedersen, NCB1-RIPE. > Network Manager, TDC, IP-section. > > "Hey, are any of you guys out there actually *using* RFC 2549?" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 11:31:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id DEB5537B403 for ; Sun, 1 Jul 2001 11:31:50 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id VME45023; Sun, 1 Jul 2001 21:31:40 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.4/8.11.4) id f61GZL203417; Sun, 1 Jul 2001 19:35:21 +0300 (EEST) (envelope-from netch) Date: Sun, 1 Jul 2001 19:35:21 +0300 From: Valentin Nechayev To: cjclark@alum.mit.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: fd0c mount(8) Race Message-ID: <20010701193521.A2949@iv.nn.kiev.ua> References: <20010630001653.D348@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010630001653.D348@blossom.cjclark.org>; from cristjc@earthlink.net on Sat, Jun 30, 2001 at 12:16:53AM -0700 X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sat, Jun 30, 2001 at 00:16:53, cristjc (Crist J. Clark) wrote about "fd0c mount(8) Race": > mount: /dev/fd0c: No such file or directory > That is, even though once I drop into single-user mode we see the > symlink for /dev/fd0c, it does not seem like it was there when 'mount > -a -t nonfs' is run in /etc/rc. I don't see it too. It appears if is created explicitly. Log follows (showing quite strange behavior): root@iv:~##ls -l /dev/fd0* crw-r----- 1 root operator 9, 0 Jul 1 15:01 /dev/fd0 root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 mknod: /dev/fd0c: File exists root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c -> fd0 root@iv:~##rm /dev/fd0c root@iv:~##rm /dev/fd0c rm: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c -> fd0 I'm surprised mainly that first mknod reported bogus failure. > reproduce the problem? Or is it well known (I can't find it in the > mail archive)? I think you can't - current devfs is too young. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 12:22:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 391C737B401 for ; Sun, 1 Jul 2001 12:22:38 -0700 (PDT) (envelope-from patrick@137.org) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id A337850D; Sun, 1 Jul 2001 14:22:37 -0500 (CDT) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id E712419F81; Sun, 1 Jul 2001 14:22:36 -0500 (CDT) To: Alfred Perlstein Cc: freebsd-current@freebsd.org Subject: Re: Vinum + DEVFS ? In-reply-to: "Sat, 30 Jun 2001 22:30:14 CDT." <20010630223014.F84523@sneakerz.org> Date: Sun, 01 Jul 2001 14:22:36 -0500 From: Patrick Hartling Message-Id: <20010701192236.E712419F81@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: } * Patrick Hartling [010630 14:04] wrote: } > I just got two new hard drives, and I am preparing to set them up to do } > RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } > became the default in -current), I saw a message saying that Vinum was } > not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, and why is it invalid? Is there some caveat I have missed? -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 12:59:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from sydney.worldwide.lemis.com (ip-208.54.117.169.mobilestar.net [208.54.117.169]) by hub.freebsd.org (Postfix) with ESMTP id D474337B401 for ; Sun, 1 Jul 2001 12:59:26 -0700 (PDT) (envelope-from grog@sydney.worldwide.lemis.com) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.3/8.9.3) id f61JxMx00513; Sun, 1 Jul 2001 15:59:22 -0400 (EDT) (envelope-from grog) Date: Sun, 1 Jul 2001 15:59:22 -0400 From: Greg Lehey To: Patrick Hartling Cc: Alfred Perlstein , freebsd-current@freebsd.org Subject: Re: Vinum + DEVFS ? Message-ID: <20010701155921.C454@sydney.worldwide.lemis.com> References: <20010630223014.F84523@sneakerz.org> <20010701192236.E712419F81@tomservo.vrac.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010701192236.E712419F81@tomservo.vrac.iastate.edu>; from patrick@137.org on Sun, Jul 01, 2001 at 02:22:36PM -0500 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: > Alfred Perlstein wrote: > >> * Patrick Hartling [010630 14:04] wrote: >>> I just got two new hard drives, and I am preparing to set them up to do >>> RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS >>> became the default in -current), I saw a message saying that Vinum was >>> not yet ready for use with DEVFS. Is that still the case? >> >> I fixed that. :) Let me and Grog know if you have problems. > > Everything seems to be okay with the vinum device node creation, but I > am having problems with my vinum configuration. I basically copied this > from an example in the online documentation (which is also in the > vinum(8) manpage); > > drive da3e device /dev/da3s1e > drive da4e device /dev/da4s1e > volume mirror > plex org concat > sd length 12g drive da3e > plex org concat > sd length 12g drive da4e > > When I do 'vinum create', I get the following: > > 1: drive da3e device /dev/da3s1e > ** 1 : Invalid argument > 2: drive da4e device /dev/da4s1e > ** 2 : Invalid argument > 3: volume mirror > 4: plex org concat > 5: sd length 12g drive da3e > 6: plex org concat > 7: sd length 12g drive da4e > > Which one is the invalid argument, The name of the partition. > and why is it invalid? I can't say for sure, since you don't supply the info asked for in the man page and the web page. But I'd be prepared to bet that your da3s1e and da4s1e partitions are not of type Vinum. Look for 'disklabel' in the man page. BTW, it's bad practice to name your drives after the partition on which they are currently resident. You can take those two drives and swap their SCSI IDs. Vinum will still find them and operate correctly, but your da3s1e partition will be drive da4e, and da4s1e will be drive da3e, which is completely confusing. Greg -- 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 Sun Jul 1 13:15:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 446AC37B401; Sun, 1 Jul 2001 13:15:45 -0700 (PDT) (envelope-from patrick@137.org) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 079E550D; Sun, 1 Jul 2001 15:15:44 -0500 (CDT) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 900A319F81; Sun, 1 Jul 2001 15:15:43 -0500 (CDT) To: Greg Lehey Cc: Alfred Perlstein , freebsd-current@freebsd.org Subject: Re: Vinum + DEVFS ? In-reply-to: "Sun, 01 Jul 2001 15:59:22 EDT." <20010701155921.C454@sydney.worldwide.lemis.com> Date: Sun, 01 Jul 2001 15:15:43 -0500 From: Patrick Hartling Message-Id: <20010701201543.900A319F81@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: } On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: } > Alfred Perlstein wrote: } > } >> * Patrick Hartling [010630 14:04] wrote: } >>> I just got two new hard drives, and I am preparing to set them up to do } >>> RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } >>> became the default in -current), I saw a message saying that Vinum was } >>> not yet ready for use with DEVFS. Is that still the case? } >> } >> I fixed that. :) Let me and Grog know if you have problems. } > } > Everything seems to be okay with the vinum device node creation, but I } > am having problems with my vinum configuration. I basically copied this } > from an example in the online documentation (which is also in the } > vinum(8) manpage); } > } > drive da3e device /dev/da3s1e } > drive da4e device /dev/da4s1e } > volume mirror } > plex org concat } > sd length 12g drive da3e } > plex org concat } > sd length 12g drive da4e } > } > When I do 'vinum create', I get the following: } > } > 1: drive da3e device /dev/da3s1e } > ** 1 : Invalid argument } > 2: drive da4e device /dev/da4s1e } > ** 2 : Invalid argument } > 3: volume mirror } > 4: plex org concat } > 5: sd length 12g drive da3e } > 6: plex org concat } > 7: sd length 12g drive da4e } > } > Which one is the invalid argument, } } The name of the partition. } } > and why is it invalid? } } I can't say for sure, since you don't supply the info asked for in the } man page and the web page. Sorry, I'll be sure to include everything next time. } But I'd be prepared to bet that your } da3s1e and da4s1e partitions are not of type Vinum. Look for } 'disklabel' in the man page. That was it, thanks. I must have missed that point in reading the web pages yesterday (which are very helpful and readable, btw). } BTW, it's bad practice to name your drives after the partition on } which they are currently resident. You can take those two drives and } swap their SCSI IDs. Vinum will still find them and operate } correctly, but your da3s1e partition will be drive da4e, and da4s1e } will be drive da3e, which is completely confusing. Thanks for the tip. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 18:21:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id DCEE437B401 for ; Sun, 1 Jul 2001 18:21:42 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f621L4d424992; Mon, 2 Jul 2001 10:21:04 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f621L4D373144; Mon, 2 Jul 2001 10:21:04 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:EADZdvevhiEjVpbmVsd9Ti7XOAif69XN@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id KAA23158; Mon, 2 Jul 2001 10:30:37 +0900 (JST) Message-Id: <200107020130.KAA23158@zodiac.mech.utsunomiya-u.ac.jp> To: Bruce Evans Cc: Dag-Erling Smorgrav , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: blockable sleep lock panic (and dumps still don't work) In-reply-to: Your message of "Mon, 02 Jul 2001 03:45:19 +1000." References: Date: Mon, 02 Jul 2001 10:30:36 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >This has something to do with the TIOCCONS ioctl. tputchar() is the >output function for the TOTTY case, and the TOTTY flag is only set for >kernel printfs if TIOCCONS has set constty to non-NULL. I'm not sure >what uses TIOCCONS (I think it is intended for use with X, but it >doesn't seem to be used on my systems). IIRC, xconsole uses this to capture console output. >TIOCCONS is almost unimplementable >(printing to a terminal is not reentrant enough to work in all contexts, >and is supposed to be protected by spltty(), but kernel printfs must >work in all contexts), so the correct fix may be to remove it. TIOCCONS >is broken in all versions of FreeBSD. The brokenness is just more >obvious now that there are more locks to trip over. > >The output function for the TOLOG case (i.e., msglogchar()) also seems to >be broken in all versions of FreeBSD. It operates on the circular message >buffer, but doesn't have any locking. I discussed this with jhb. We even had a test patch. Jhb told me that someone else was working on providing proper locking in kernel printf(). >The output function for the TOCONS case (i.e., cnputc()) is also >problematic. Only the serial console output routine even attempts to >be reentrant, and (per-cpu) reentrancy is not enough under SMP. >Syscons' output routine was easy to panic by mixing kernel printfs with >user-mode output the last time I checked. Syscons' sccnputc() is not reentrant. I was trying to improbe this, but decided that I would wait until I see further development in tty locking and kernel printf() area by jhb. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 18:35:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from degler.net (crusoe.degler.net [160.79.55.71]) by hub.freebsd.org (Postfix) with ESMTP id 68DE937B401 for ; Sun, 1 Jul 2001 18:35:26 -0700 (PDT) (envelope-from sdegler@degler.net) Received: (from sdegler@localhost) by degler.net (8.11.3/8.11.0) id f621ZJ309558 for freebsd-current@freebsd.org; Sun, 1 Jul 2001 21:35:19 -0400 (EDT) Date: Sun, 1 Jul 2001 21:35:19 -0400 From: Stephen Degler To: freebsd-current@freebsd.org Subject: IPV6 panic ? Message-ID: <20010701213519.A9492@crusoe.degler.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have had two of these since 6/30, which is when I last cvsup'ed and rebuilt everything. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xc02c3b10 stack pointer = 0x10:0xcbb4ff28 frame pointer = 0x10:0xcbb4ff3c 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 = 12 (swi6: tty:sio+) kernel: type 12 trap, code=0 Stopped at nd6_timer+_0x38: movl 0(%ebx),%eax db> trace nd6_timer(0) at nd6_timer+0x38 softclock(0) at softclock_0x30e ithread_loop(c1207d00,cbb4ffa8) at ithread_loop+0x263 fork_exit(c0224b14,c1207d00,cbb4ffa8) at fork_exit+0xa0 fork_trampoline() at fork trampoline+0x8 db> The kernel config is just GENERIC + IPSEC. IPV6 is configured and running. Thanks, skd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 19:16:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id AA5D137B403 for ; Sun, 1 Jul 2001 19:16:08 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 22111 invoked by uid 0); 2 Jul 2001 02:16:01 -0000 Received: from pd9508863.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.99) by mail.gmx.net (mail09) with SMTP; 2 Jul 2001 02:16:01 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA12092 for current@freebsd.org; Sun, 1 Jul 2001 21:33:27 +0200 Date: Sun, 1 Jul 2001 21:33:27 +0200 From: Gerhard Sittig To: current@freebsd.org Subject: Re: ipfilter+ipv6 - what am I missing? Message-ID: <20010701213327.O17514@speedy.gsinet> Mail-Followup-To: current@freebsd.org References: <20010701142120.C770@bank-pedersen.dk> <005701c10256$d5361960$6503c23f@XGforce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <005701c10256$d5361960$6503c23f@XGforce.com>; from matt-l@pacbell.net on Sun, Jul 01, 2001 at 10:54:01AM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 01, 2001 at 10:54 -0700, matt wrote: > > I don't think ipf is complete in its ipv6 support yet.You can > use ipfw instead. Ipf has been supporting IPv6 for quite some time. It's just that one has to enable this support in the Makefile. $ grep INET6 contrib/ipfilter/Makefile #INET6=-DUSE_INET6 MFLAGS1='CFLAGS=$(CFLAGS) $(ARCHINC) $(SOLARIS2) $(INET6)' \ [ ... ] And ISTR that one has to add "-6" to the ipf(8) invocation options (like, in /etc/rc.conf). When I extended ipf to invoke a preprocessor (PR bin/21989) I added some magic to not propose switches for unsupported features in the synopsis. Maybe this concern should be reraised? virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 20:41:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.novagate.net (mailgate.novagate.net [205.138.138.22]) by hub.freebsd.org (Postfix) with ESMTP id E68F837B401 for ; Sun, 1 Jul 2001 20:41:43 -0700 (PDT) (envelope-from djhill@novagate.net) Received: from rain.hill.hom (081bc122.chartermi.net [24.247.81.122]) by mailgate.novagate.net (8.11.3/8.11.3) with SMTP id f623fbq56443 for ; Sun, 1 Jul 2001 23:41:38 -0400 (EDT) (envelope-from djhill@novagate.net) Date: Sun, 1 Jul 2001 23:41:25 -0400 From: David Hill To: freebsd-current@freebsd.org Subject: syslogd and -a Message-Id: <20010701234125.7a7d3e3a.djhill@novagate.net> X-Mailer: Sylpheed version 0.5.0pre2 (GTK+ 1.2.10; i386-unknown-freebsd4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello - It seems the -a option for syslogd does not work 100%. I need to log from hosts from 192.168.1.1-.6 doing "/usr/sbin/syslogd -a 192.168.1.1/29" does not work (nothing gets logged) but, if i do /usr/sbin/syslogd -a 192.168.1.1/32 -a 192.168.1.2/32, etc... that works can anyone try this out? Thanks - David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 20:48:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A18CD37B403 for ; Sun, 1 Jul 2001 20:48:37 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f623mZU30944; Sun, 1 Jul 2001 21:48:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107020348.f623mZU30944@harmony.village.org> To: Michael Harnois Subject: Re: can't build kernel: config doesn't work Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Jul 2001 10:40:25 CDT." <86ofr4k68m.fsf@mharnois.workgroup.net> References: <86ofr4k68m.fsf@mharnois.workgroup.net> <20010701082725.A798@zippy.mybox.zip> Date: Sun, 01 Jul 2001 21:48:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <86ofr4k68m.fsf@mharnois.workgroup.net> Michael Harnois writes: : OK, so it is my fault. Did I miss a HEADS UP on this? It certainly : deserved one. I didn't send one. Maybe I should have. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 21:20:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 6AB0837B401 for ; Sun, 1 Jul 2001 21:20:49 -0700 (PDT) (envelope-from cjc@earthlink.net) Received: from blossom.cjclark.org (dialup-209.245.135.39.Dial1.SanJose1.Level3.net [209.245.135.39]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA20071; Sun, 1 Jul 2001 21:20:47 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.4/8.11.3) id f624Kje12171; Sun, 1 Jul 2001 21:20:45 -0700 (PDT) (envelope-from cjc) Date: Sun, 1 Jul 2001 21:20:44 -0700 From: "Crist J. Clark" To: David Hill Cc: freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Message-ID: <20010701212044.Q296@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20010701234125.7a7d3e3a.djhill@novagate.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010701234125.7a7d3e3a.djhill@novagate.net>; from djhill@novagate.net on Sun, Jul 01, 2001 at 11:41:25PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 01, 2001 at 11:41:25PM -0400, David Hill wrote: > Hello - > > It seems the -a option for syslogd does not work 100%. > I need to log from hosts from 192.168.1.1-.6 > > doing "/usr/sbin/syslogd -a 192.168.1.1/29" does not work (nothing gets logged) > > but, if i do > > /usr/sbin/syslogd -a 192.168.1.1/32 -a 192.168.1.2/32, etc... that works > > can anyone try this out? Hmmm... Looks like, # syslogd -a 192.168.1.0/29 Will work and, # syslogd -a 192.168.1.1/29 Won't. I'll have a look. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 1 22:36:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.dada.it (mail4.dada.it [195.110.96.56]) by hub.freebsd.org (Postfix) with SMTP id CC49737B403 for ; Sun, 1 Jul 2001 22:36:21 -0700 (PDT) (envelope-from riccardo@torrini.org) Received: (qmail 13752 invoked from network); 2 Jul 2001 05:36:19 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 2 Jul 2001 05:36:19 -0000 Received: (from riccardo@localhost) by torrini.org (8.11.3/8.11.3) id f625aIC00664 for freebsd-current@FreeBSD.ORG; Mon, 2 Jul 2001 07:36:18 +0200 (CEST) (envelope-from riccardo) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010701212044.Q296@blossom.cjclark.org> Date: Mon, 02 Jul 2001 07:36:18 +0200 (CEST) From: Riccardo Torrini To: freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Jul-01 (04:20:44/GMT) Crist J. Clark wrote: >> It seems the -a option for syslogd does not work 100%. > Hmmm... Looks like, > # syslogd -a 192.168.1.0/29 > Will work and, > # syslogd -a 192.168.1.1/29 > Won't. Under 4.3-STABLE is the same. To capure log from router I added (in rc.conf) -a 192.168.22.254/32:* because with all log enabled I notice that with ..22.0/24 syslod refused to accept requests from network :-( Ciao, Riccardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 1:12:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id DF3C737B401; Mon, 2 Jul 2001 01:12:44 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with ESMTP id f628CfK44241 ; Mon, 2 Jul 2001 17:12:42 +0900 (JST) Message-Id: <200107020812.f628CfK44241@rina.r.dl.itc.u-tokyo.ac.jp> Date: Mon, 02 Jul 2001 17:12:41 +0900 From: Seigo Tanimura To: obrien@FreeBSD.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, jhb@FreeBSD.org, current@FreeBSD.org Subject: Re: Lock of struct filedesc, file, pgrp, session and sigio In-Reply-To: In your message of "Mon, 18 Jun 2001 19:04:31 +0900" <200106181004.f5IA4VD63112@rina.r.dl.itc.u-tokyo.ac.jp> References: <20010531124007.B57907@dragon.nuxi.com> <20010531130155.A58258@dragon.nuxi.com> <200106011228.f51CSvD46848@rina.r.dl.itc.u-tokyo.ac.jp> <20010602125223.J31257@dragon.nuxi.com> <200106040748.f547mUD53783@rina.r.dl.itc.u-tokyo.ac.jp> <200106181004.f5IA4VD63112@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 18 Jun 2001 19:04:31 +0900, Seigo Tanimura said: Seigo> The results of build test with the latest patch are now at: Seigo> http://people.FreeBSD.org/~tanimura/pg_fd/ Seigo> As it is likely to take quite a while to fix alpha, I am going to Seigo> update the patch every few days. The latest test on alpha shows successful build of a kernel. Is alpha fixed and working now? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 1:38:46 2001 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 299C737B401 for ; Mon, 2 Jul 2001 01:38:44 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Jul 2001 09:38:43 +0100 (BST) Date: Mon, 2 Jul 2001 09:38:42 +0100 From: David Malone To: cjclark@alum.mit.edu Cc: David Hill , freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Message-ID: <20010702093842.A13480@walton.maths.tcd.ie> References: <20010701234125.7a7d3e3a.djhill@novagate.net> <20010701212044.Q296@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010701212044.Q296@blossom.cjclark.org>; from cristjc@earthlink.net on Sun, Jul 01, 2001 at 09:20:44PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 01, 2001 at 09:20:44PM -0700, Crist J. Clark wrote: > Hmmm... Looks like, > > # syslogd -a 192.168.1.0/29 > > Will work and, > > # syslogd -a 192.168.1.1/29 > > Won't. That's the standard behaviour of a netmask, isn't it? The usual way to check if host h is in network/netmask n/m is to check if: (h & m == n) this means that the bits of the network which are not in the mask must be zero. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 4:16:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id CCB9D37B401 for ; Mon, 2 Jul 2001 04:16:48 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (patr530-b101.otenet.gr [195.167.121.229]) by mailsrv.otenet.gr (8.11.1/8.11.1) with ESMTP id f62BGjK03249 for ; Mon, 2 Jul 2001 14:16:45 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.4/8.11.3) id f628YRq07312; Mon, 2 Jul 2001 11:34:27 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 2 Jul 2001 11:34:25 +0300 From: Giorgos Keramidas To: current@freebsd.org Subject: funny strlen defines in sys/alpha/alpha/alpha-gdbstub.c Message-ID: <20010702113423.B7023@hades.hell.gr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Close to the top of sys/alpha/alpha/alpha-gdbstub.c i found out this, as i was randomly browsing the kernel sources today: 1 /* $FreeBSD: src/sys/alpha/alpha/alpha-gdbstub.c,v 1.11 2001/03/28 01:54:05 jhb Exp $ */ ... 130 #define strlen gdb_strlen 131 #define strcpy gdb_strcpy ... 133 static int 134 strlen (const char *s) 135 { ... 143 static char * 144 strcpy (char *dst, const char *src) 145 { ... wondering what happens when this file is fed to the preprocessor, it seems that all occurences of strlen() and strcpy() are replaced with gdb_strlen() and gdb_strcpy() in this file. Is it really necessary to do this funny thing with the #defines? I mean, why not replace the calls with gdb_XXX() ourselves and be done with it? After all it only occurs in a handful of places, and the functions are static. % fgrep strlen alpha-gdbstub.c | wc -l 8 % fgrep strcpy alpha-gdbstub.c | wc -l 11 As I dont have an Alpha around, I can't actually test the attached patch, but I'm looking forward to your comments. -giorgos --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="alpha-gdbstub.diff" Index: alpha/alpha/alpha-gdbstub.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/alpha-gdbstub.c,v retrieving revision 1.11 diff -c -u -r1.11 alpha-gdbstub.c --- alpha/alpha/alpha-gdbstub.c 2001/03/28 01:54:05 1.11 +++ alpha/alpha/alpha-gdbstub.c 2001/07/02 08:25:34 @@ -119,19 +119,8 @@ /* at least NUMREGBYTES*2 are needed for register packets */ #define BUFMAX 1500 -/* Create private copies of common functions used by the stub. This prevents - nasty interactions between app code and the stub (for instance if user steps - into strlen, etc..) */ -/* XXX this is fairly bogus. strlen() and strcpy() should be reentrant, - and are reentrant under FreeBSD. In any case, our versions should not - be named the same as the standard versions, so that the address `strlen' - is unambiguous... */ - -#define strlen gdb_strlen -#define strcpy gdb_strcpy - static int -strlen (const char *s) +gdb_strlen (const char *s) { const char *s1 = s; @@ -141,7 +130,7 @@ } static char * -strcpy (char *dst, const char *src) +gdb_strcpy (char *dst, const char *src) { char *retval = dst; @@ -230,7 +219,7 @@ /* remove sequence chars from buffer */ - count = strlen (buffer); + count = gdb_strlen (buffer); for (i=3; i <= count; i++) buffer[i-3] = buffer[i]; } @@ -239,7 +228,7 @@ } while (checksum != xmitcsum); - if (strlen(buffer) >= BUFMAX) + if (gdb_strlen(buffer) >= BUFMAX) panic("kgdb: buffer overflow"); } @@ -252,7 +241,7 @@ int count; unsigned char ch; - if (strlen(buffer) >= BUFMAX) + if (gdb_strlen(buffer) >= BUFMAX) panic("kgdb: buffer overflow"); /* $#. */ @@ -655,7 +644,7 @@ case 'G': /* set the value of the CPU registers - return OK */ hex2mem (&remcomInBuffer[1], (vm_offset_t)®isters, NUMREGBYTES); - strcpy (remcomOutBuffer, "OK"); + gdb_strcpy (remcomOutBuffer, "OK"); break; case 'P': /* Set the value of one register */ @@ -669,10 +658,10 @@ && regno < NUM_REGS) { hex2mem (ptr, (vm_offset_t)®isters + regno * 8, 8); - strcpy(remcomOutBuffer,"OK"); + gdb_strcpy(remcomOutBuffer,"OK"); } else - strcpy (remcomOutBuffer, "P01"); + gdb_strcpy (remcomOutBuffer, "P01"); break; } case 'm': /* mAA..AA,LLLL Read LLLL bytes at address AA..AA */ @@ -685,11 +674,11 @@ && hexToInt (&ptr, &length)) { if (mem2hex((vm_offset_t) addr, remcomOutBuffer, length) == NULL) - strcpy (remcomOutBuffer, "E03"); + gdb_strcpy (remcomOutBuffer, "E03"); break; } else - strcpy (remcomOutBuffer, "E01"); + gdb_strcpy (remcomOutBuffer, "E01"); break; case 'M': /* MAA..AA,LLLL: Write LLLL bytes at address AA.AA return OK */ @@ -704,12 +693,12 @@ && *(ptr++) == ':') { if (hex2mem(ptr, (vm_offset_t) addr, length) == NULL) - strcpy (remcomOutBuffer, "E03"); + gdb_strcpy (remcomOutBuffer, "E03"); else - strcpy (remcomOutBuffer, "OK"); + gdb_strcpy (remcomOutBuffer, "OK"); } else - strcpy (remcomOutBuffer, "E02"); + gdb_strcpy (remcomOutBuffer, "E02"); break; /* cAA..AA Continue at address AA..AA(optional) */ --17pEHd4RhPHOinZp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 8:26:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 6F47C37B401 for ; Mon, 2 Jul 2001 08:26:13 -0700 (PDT) (envelope-from cjc@earthlink.net) Received: from blossom.cjclark.org (dialup-209.245.142.69.Dial1.SanJose1.Level3.net [209.245.142.69]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id IAA24420; Mon, 2 Jul 2001 08:26:01 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.4/8.11.3) id f62FPck00691; Mon, 2 Jul 2001 08:25:38 -0700 (PDT) (envelope-from cjc) Date: Mon, 2 Jul 2001 08:25:38 -0700 From: "Crist J. Clark" To: David Malone Cc: David Hill , freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Message-ID: <20010702082538.B448@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20010701234125.7a7d3e3a.djhill@novagate.net> <20010701212044.Q296@blossom.cjclark.org> <20010702093842.A13480@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010702093842.A13480@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Mon, Jul 02, 2001 at 09:38:42AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 02, 2001 at 09:38:42AM +0100, David Malone wrote: > On Sun, Jul 01, 2001 at 09:20:44PM -0700, Crist J. Clark wrote: > > Hmmm... Looks like, > > > > # syslogd -a 192.168.1.0/29 > > > > Will work and, > > > > # syslogd -a 192.168.1.1/29 > > > > Won't. > > That's the standard behaviour of a netmask, isn't it? The usual > way to check if host h is in network/netmask n/m is to check if: > > (h & m == n) > > this means that the bits of the network which are not in the mask > must be zero. That's exactly what happens in the syslogd(8) code. However, I think that should be, n &= m . . . ((h & m) == n) That is, why allow the user to enter a network number that is not /really/ the network number? Either flag an error or do the calculation for the user. I think doing the calculation is the more sensible choice. Commiting it to CURRENT now. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 8:33:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.novagate.net (mailgate.novagate.net [205.138.138.22]) by hub.freebsd.org (Postfix) with ESMTP id B3C5137B401 for ; Mon, 2 Jul 2001 08:33:46 -0700 (PDT) (envelope-from djhill@novagate.net) Received: from rain.hill.hom (081bc122.chartermi.net [24.247.81.122]) by mailgate.novagate.net (8.11.3/8.11.3) with SMTP id f62FXgq68077; Mon, 2 Jul 2001 11:33:42 -0400 (EDT) (envelope-from djhill@novagate.net) Date: Mon, 2 Jul 2001 11:33:23 -0400 From: David Hill To: David Malone Cc: freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Message-Id: <20010702113323.5f43e3e5.djhill@novagate.net> In-Reply-To: <20010702093842.A13480@walton.maths.tcd.ie> References: <20010701234125.7a7d3e3a.djhill@novagate.net> <20010701212044.Q296@blossom.cjclark.org> <20010702093842.A13480@walton.maths.tcd.ie> X-Mailer: Sylpheed version 0.5.0pre2 (GTK+ 1.2.10; i386-unknown-freebsd4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001 09:38:42 +0100 David Malone wrote: > On Sun, Jul 01, 2001 at 09:20:44PM -0700, Crist J. Clark wrote: > > Hmmm... Looks like, > > > > # syslogd -a 192.168.1.0/29 > > > > Will work and, > > > > # syslogd -a 192.168.1.1/29 > > > > Won't. > > That's the standard behaviour of a netmask, isn't it? The usual > way to check if host h is in network/netmask n/m is to check if: > > (h & m == n) > > this means that the bits of the network which are not in the mask > must be zero. > > David. > Ok, changing the .1 to .0 worked for me. The last octect must be the network number. Thanks - David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 8:51:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 4318E37B403 for ; Mon, 2 Jul 2001 08:51:17 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f62Fom722048 for current@FreeBSD.org; Mon, 2 Jul 2001 18:50:48 +0300 (EEST) (envelope-from ru) Date: Mon, 2 Jul 2001 18:50:48 +0300 From: Ruslan Ermilov To: current@FreeBSD.org Subject: TIOCSCTTY Message-ID: <20010702185048.A21809@sunbay.com> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! Could someone please explain why the following code snippet does not work anymore with the "/dev/console" argument? # ./tiocsctty /dev/console tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted Thanks, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="tiocsctty.c" #include #include #include #include #include int main(int argc, char *argv[]) { int fd; if (argc != 2) errx(1, "missing argument"); if ((fd = open(argv[1], O_RDWR)) == -1) err(1, "open %s", argv[1]); if (daemon(1, 1) == -1) err(1, "daemon"); if (ioctl(fd, TIOCSCTTY) == -1) err(1, "ioctl(%s, TIOCSCTTY)", argv[1]); exit(0); } --bg08WKrSYDhXBjb5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 9:19: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 7849037B403; Mon, 2 Jul 2001 09:19:04 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 297F55D010; Mon, 2 Jul 2001 11:19:04 -0500 (CDT) Date: Mon, 2 Jul 2001 11:19:04 -0500 From: Alfred Perlstein To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: TIOCSCTTY Message-ID: <20010702111904.O84523@sneakerz.org> References: <20010702185048.A21809@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010702185048.A21809@sunbay.com>; from ru@FreeBSD.org on Mon, Jul 02, 2001 at 06:50:48PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Ruslan Ermilov [010702 10:51] wrote: > Hi! > > Could someone please explain why the following code snippet > does not work anymore with the "/dev/console" argument? > > # ./tiocsctty /dev/console > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted I think LINT has an option to allow this. The reason, I think, is that you don't want non-root users to be able to grab the console output as it may allow them to obscure evil behavior. :) -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 9:37:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.mn.rr.com (msp-65-25-196-169.mn.rr.com [65.25.196.169]) by hub.freebsd.org (Postfix) with ESMTP id 9CDA037B401 for ; Mon, 2 Jul 2001 09:37:28 -0700 (PDT) (envelope-from visigoth@mn.rr.com) Received: by morpheus.mn.rr.com (Postfix, from userid 1001) id 098AB3451C; Mon, 2 Jul 2001 11:36:26 -0500 (CDT) Date: Mon, 2 Jul 2001 11:36:26 -0500 From: Damieon Stark To: current@freebsd.org Subject: Re: unified pwutil library - thoughts? Message-ID: <20010702113626.A21098@morpheus.mn.rr.com> References: <20010624210541.A12494@morpheus.mn.rr.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010624210541.A12494@morpheus.mn.rr.com>; from visigoth@mn.rr.com on Sun, Jun 24, 2001 at 09:05:41PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey all... So, by the fact that I got _no_ replies I must surmise that either my message didn't get posted (confirmed posting with archive), or people didn't read it, or _nobody_ thinks it is a good idea ;) but if nobody thinks it is a good idea, I _think_ I would have gotten some flames/feedbac= k. Here goes again... Below is the message I sent about a unified libpwutil, = and possibly integrating it into FreeBSD. _ANY_ feedback, positive or negitive would be appreciated as it will help to validate my existance ;) On Sun, Jun 24, 2001 at 09:05:41PM -0500, Damieon Stark wrote: > Hey all, >=20 > Ok, so my thinking goes a little like this: having chpass, vipw,=20 > passwd, rpc.yppasswdd et. al. using the same functions (pw_copy, pw_temp, > pw_init...) and then, in order to update the database calling a > function which does nothing more than execl(pwd_mkdb) and exit > seems kinda silly.=20 > For a couple of my projects, having a "BSD approved" way > of modifying the master.passwd/spwd.db would have been _very_ nice, so I > have created libpwutil. This new lib could be used to (staticly) link > all the afore mentioned command line utils, and create a more central way > to manage password changes, as well as creating a reasonably nice C inter= face > to changing passwords. > If I am way off my rocker, please let me know. I've > also created a _new_ pw_mkdb function which does NOT use execl or system.= If > this sounds like something that people are interested in, I would be happ= y to > work up some doccumentation, and submit it for inclusion/port-dom as well= as > patches to chpass and crew if people think it is a good idea. > Just _looking_ at the Makefiles for things like chpass brought on > the urge to make a change... ;) Also, future support for things like NIS+= /LDAP > could (possibly) be more easily developed. >=20 > visigoth >=20 > P.S. the lib will be BSD licenced, NOT GPL'd ;) Visigoth --=20 Damieon Stark, CCSE Unix/Network Security Engineer currently seeking employment ___________________________________________________________________________= ___ Damieon Stark | Microsoft: Where do you want to go today? e: visigoth@mn.rr.com | Linux: Where do you want to go tommorow? p: 612.382.6945 | FreeBSD: Are you guys comming or what? pgp: 0xBE5D0C57 |=20 pgp.mit.edu | http://www.freebsd.org - The power to serve! ---------------------------------------------------------------------------= --- --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQEVAwUBO0CUtIA1oSe+XQxXAQFBHwgAwjpy6f1lmLLx2eWO5bmQ+bpffGLD/pFq fqOBcB8GOq63y/lLkmVmrX45Q5LVGNkZnPmFlEdxG235PUgFlXelEejZ7TQEnLGH SydLVr99lSyZRnQs5qkYfWYCSxf3WDzE3uozZV1jYLqXzMh64IP4vPEUSSDGIxs+ +SROpyUQYUpatvroMDZePkLD4Jf8oKtCFuVV+qQTkXfSrKzCssnct+LSF05g5VkZ +nwh7C4KAXmPG0TKHdKX8kMnZXfm+2o77c2jaxjh1GeI+39I5Xwo/+kGw8Gb6Rq0 1jsRgJ0pCkCmWu15Ey57D9nX3dR56agB95NfUI2HoNWw9s3qM0RXaw== =Cb7b -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 9:49:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id AF46F37B405; Mon, 2 Jul 2001 09:49:50 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.3/8.11.1) with ESMTP id f62GoxC28949; Mon, 2 Jul 2001 19:51:00 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (das0-l96.uic-in.net [212.35.189.223]) by mail.uic-in.net (8.11.3/8.11.3) with ESMTP id f62GmPm44484; Mon, 2 Jul 2001 19:48:29 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f62Glsq23853; Mon, 2 Jul 2001 19:47:54 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B40A5BD.42726F09@FreeBSD.org> Date: Mon, 02 Jul 2001 19:47:57 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Mark Murray , Maxim Sobolev , current@FreeBSD.org Subject: Re: PAM causes segfault in login(1) References: <200106130707.f5D77Rx05230@vega.vega.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > > > > I've noticed that new PAM segfaults when I'm typing non-existing login > > > at console login prompt. Please fix. > > > > This current, right? > > Did I complain? > > > I'll sort it out. Thanks for the debug-sleuthing! > > Yes, please do it. Any progress (the problem is still here)? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 11:18: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id D13B337B406 for ; Mon, 2 Jul 2001 11:18:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f62II4S91481 for ; Mon, 2 Jul 2001 11:18:04 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 2 Jul 2001 11:18:04 -0700 (PDT) From: Matthew Jacob Reply-To: To: Subject: kernel configs completely broken Message-ID: <20010702111357.Y23320-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The latest config(8) changes have broken kernel configs for me such that it apparently will not rewrite the ../compile//Makefile anymore and important things like subr_trap, etc.. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 11:20:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id C7E6837B407 for ; Mon, 2 Jul 2001 11:20:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f62IKnS91525 for ; Mon, 2 Jul 2001 11:20:49 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 2 Jul 2001 11:20:49 -0700 (PDT) From: Matthew Jacob Reply-To: To: Subject: Jesus, never mind....Re: kernel configs completely broken In-Reply-To: <20010702111357.Y23320-100000@wonky.feral.com> Message-ID: <20010702112030.J23320-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I somehow missed the change to sys/ARCH/compile. On Mon, 2 Jul 2001, Matthew Jacob wrote: > > > The latest config(8) changes have broken kernel configs for me such that > it apparently will not rewrite the ../compile//Makefile anymore > and important things like subr_trap, etc.. > > -matt > > > > 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 Jul 2 11:22:23 2001 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 EED1437B406 for ; Mon, 2 Jul 2001 11:22:17 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:RU5p615rpOkp35ATvEgZ7g6RjfchwzTq7mgos+PdxbTMDILX5l6EXvjuteS9NtYX@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.4/8.11.4/peace) with ESMTP/inet6 id f62ILH928511; Tue, 3 Jul 2001 03:21:17 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 03 Jul 2001 03:21:14 +0900 (JST) Message-Id: <20010703.032114.36997379.ume@mahoroba.org> To: cjclark@alum.mit.edu, cristjc@earthlink.net Cc: dwmalone@maths.tcd.ie, djhill@novagate.net, freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a From: Hajimu UMEMOTO In-Reply-To: <20010702082538.B448@blossom.cjclark.org> References: <20010701212044.Q296@blossom.cjclark.org> <20010702093842.A13480@walton.maths.tcd.ie> <20010702082538.B448@blossom.cjclark.org> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / 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-Operating-System: 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Mon, 2 Jul 2001 08:25:38 -0700 >>>>> "Crist J. Clark" said: cristjc> That's exactly what happens in the syslogd(8) code. However, I think cristjc> that should be, cristjc> n &= m cristjc> . cristjc> . cristjc> . cristjc> ((h & m) == n) I think it should be: ((h & m) == (n & m)) cristjc> That is, why allow the user to enter a network number that is not cristjc> /really/ the network number? Either flag an error or do the cristjc> calculation for the user. I think doing the calculation is the more cristjc> sensible choice. Commiting it to CURRENT now. When I committed IPv6 support to syslogd, I didn't mask address to keep compatibility with IPv4. So, I'll commit to IPv6 side, later. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}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 Mon Jul 2 12:15:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4B57D37B405 for ; Mon, 2 Jul 2001 12:15:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f62JFsU36427 for ; Mon, 2 Jul 2001 13:15:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107021915.f62JFsU36427@harmony.village.org> To: current@freebsd.org Subject: ** HEADS UP **: kernel compile directory change Date: Mon, 02 Jul 2001 13:15:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you use the buildkernel/installkernel method in current to build your kernels, nothing has changed and can ignore the rest of this message. If you use the classic/developers method to build your kernels, read on. You need a new config after july 1, 2001[*]. The compile directory has moved from src/sys/compile/FOO to src/sys/$MACHINE/compile/FOO. This allows us to compile multiple architectures' GENERIC/LINT files in one tree. As we get more architectures in the tree, this becomes critical to more of our developers. If you wish to keep the old config directory location, I suggest: config -d `pwd`/../../config/FOO FOO Also, if you wanted to move the compile directory directly (eg mv src/sys/compile/FOO src/sys/alpha/compile/FOO), you must remove the machine link and reconfig. However, if you go this route, you are on your own if things go wrong. Alternatively, you can also put a symbolic link from src/sys/compile to src/sys/MACHINE/compile if you have only one MACHINE. However, this may cause problems with cvs and/or cvsup (eg, the author hasn't tested it). Warner [*] Actually, the directory was moved on June 29, but there were a number of fixes that dribbled in over the next two days to knock the rough edges off of things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 12:25:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-161.dsl.lsan03.pacbell.net [64.169.104.161]) by hub.freebsd.org (Postfix) with ESMTP id 0E47637B401 for ; Mon, 2 Jul 2001 12:25:44 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E6E3967B08; Mon, 2 Jul 2001 12:25:42 -0700 (PDT) Date: Mon, 2 Jul 2001 12:25:42 -0700 From: Kris Kennaway To: David Malone Cc: cjclark@alum.mit.edu, David Hill , freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a Message-ID: <20010702122542.C64285@xor.obsecurity.org> References: <20010701234125.7a7d3e3a.djhill@novagate.net> <20010701212044.Q296@blossom.cjclark.org> <20010702093842.A13480@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NU0Ex4SbNnrxsi6C" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010702093842.A13480@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Mon, Jul 02, 2001 at 09:38:42AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --NU0Ex4SbNnrxsi6C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 02, 2001 at 09:38:42AM +0100, David Malone wrote: > On Sun, Jul 01, 2001 at 09:20:44PM -0700, Crist J. Clark wrote: > > Hmmm... Looks like, > >=20 > > # syslogd -a 192.168.1.0/29 > >=20 > > Will work and, > >=20 > > # syslogd -a 192.168.1.1/29 > >=20 > > Won't. >=20 > That's the standard behaviour of a netmask, isn't it? The usual > way to check if host h is in network/netmask n/m is to check if: >=20 > (h & m =3D=3D n) >=20 > this means that the bits of the network which are not in the mask > must be zero. This doesn't seem to work with IPv6. Isn't there a libc function which can be used to do this? Kris --NU0Ex4SbNnrxsi6C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7QMq1Wry0BWjoQKURAnO+AJ0dEnAhJYWEW4C1Evm1IVIjem6xWQCgo+7O msbbBVsje8EKETHnqNAouyU= =jlTG -----END PGP SIGNATURE----- --NU0Ex4SbNnrxsi6C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 12:38:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id CCCC037B405 for ; Mon, 2 Jul 2001 12:38:35 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA13582 for ; Mon, 2 Jul 2001 14:16:18 -0700 (PDT) Date: Mon, 2 Jul 2001 14:16:16 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: RFC: Kernel thread system nomenclature. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The time has come (now that we have a design) to assign names to the various entities that will be created when we implement the (current name) KSE code. I have already done initial work on this and have a system running with the proc structure split into 4 parts. The names of these parts need to be fully decided and agreed upon now while the changes are limited to 2 files :-) The next change requires editing almost every file in the kernel. The KSE names were a temporary measure to identify these while their functions were being decided. Here are the entities, a decription of what they do, and some suggested names: 1) This structure 'owns' all the resources that are relavent to the process. It owns the credentials, the VM space, the file desriptors, (possibly the signal state), the parent process, the child processes etc. etc. Suggested names: proc, task (others?) 2) The second structure owns the scheduling parameters. All scheduling decisions are made according to information held in this structure. The is by default one of these per each of the above (#1) structure. However the threads library may make more should it wish to shedule some threads at a different priority. Each of these competes with the weight of a process in the system scope. In the case where there are not per-cpu run queues, THIS would be put on the run queues. There may be between 1 and M of these where M is the remaining rlimit on processes. (they count as processes against the rlimits) Suggested names: schedblock (SB), Kernel Schedulabale Entity Group (KSEG), KSE (confusing but acurate), SchedEntry, (SE?), Process Schduling control block (pscb) 3) The third structure is a container for running code contexts. The concurrency of a MP machine can be exploited by having multiple of these entities, each of which most be run on a different processor. With per-CPU run queues, these would be on the queues, but the controling parameters are inherrited from the 2nd structure. There may be between 1 and N (where N is the number of processors) of these entities per each of the 2nd structure type. Eligible contexts are run in either kernel or user mode when this is scheduled. Each of these has a separate upcall context stored for communication with the Userland scheduler. Suggested names: Kernel Schedulable Entity(KSE), thread container(TC), Scheduler Virtual processor(SVP), Scheduler Slot(schedslot, ss?) Thread processor (tp?) 4) The last entity is the 'kernel context' structure. This contains the kernel stack for whatever thread of execution is being run and is what is saved onto the sleep queues when a tread of execution blocks. All the context needed to restart a thread is saved in this. In the current system this information is stored in a combination of the proc struct, the U area and the kernel stack. There can be an almost unlimited (resource limited) number of these which would indicate a large number of blocked syscalls. They are allocated to the #2 structure and may run under more than one of the #3 entities during the course of a syscall if there are context switches. they would have some affinity to the last #3 they ran on for cache reasons, but conld be switched to another #3 that is connected to the same #2 if it were idle. Suggested names: Thread Context Block (TCB) Kernel Schedulabel Entity Context (KSEC) Thread Context (TCTX) Any more suggestions are most welcome! (but seeing as how I'm doing the code I will select as I see fit at the end of the discussion. Almost all of the current 'proc' pointers being passed around the system in syscalls will be changed to the #4 item. In addition, most accesses to curproc would point to a curthread (curr-#4) or a curr#3, so the names selected will be used a lot. The exctent of these edits almost makes it worthwhile to call the #4 item 'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). (everyhting to do with sleeping, blocking, and waking up would avoid changes, and everywhere a syscall passes down "struct proc *p" would avoid changes. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 12:43:47 2001 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 1A96637B401 for ; Mon, 2 Jul 2001 12:43:41 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:lyxLqOVph8iTFzQSaAagAKb9JV0ZEA2vC8FBSUgLXU14dmZjgEa0VHz6QTRA3UzA@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.4/8.11.4/peace) with ESMTP/inet6 id f62Jh5906609; Tue, 3 Jul 2001 04:43:05 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 03 Jul 2001 04:43:01 +0900 (JST) Message-Id: <20010703.044302.78781077.ume@mahoroba.org> To: kris@obsecurity.org Cc: dwmalone@maths.tcd.ie, cjclark@alum.mit.edu, djhill@novagate.net, freebsd-current@FreeBSD.ORG Subject: Re: syslogd and -a From: Hajimu UMEMOTO In-Reply-To: <20010702122542.C64285@xor.obsecurity.org> References: <20010701212044.Q296@blossom.cjclark.org> <20010702093842.A13480@walton.maths.tcd.ie> <20010702122542.C64285@xor.obsecurity.org> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / 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-Operating-System: 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Mon, 2 Jul 2001 12:25:42 -0700 >>>>> Kris Kennaway said: kris> This doesn't seem to work with IPv6. Isn't there a libc function kris> which can be used to do this? Yup, there is no api for masking address ether libc nor standard. I'll commit the following patch for IPv6: Index: usr.sbin/syslogd/syslogd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/syslogd/syslogd.c,v retrieving revision 1.79 diff -u -r1.79 syslogd.c --- usr.sbin/syslogd/syslogd.c 2001/07/02 15:26:47 1.79 +++ usr.sbin/syslogd/syslogd.c 2001/07/02 19:39:32 @@ -2033,7 +2033,7 @@ reject = 0; for (j = 0; j < 16; j += 4) { if ((*(u_int32_t *)&sin6->sin6_addr.s6_addr[i] & *(u_int32_t *)&m6p->sin6_addr.s6_addr[i]) - != *(u_int32_t *)&a6p->sin6_addr.s6_addr[i]) { + != (*(u_int32_t *)&a6p->sin6_addr.s6_addr[i] & *(u_int32_t *)&m6p->sin6_addr.s6_addr[i])) { ++reject; break; } -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}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 Mon Jul 2 12:54:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id E515337B401 for ; Mon, 2 Jul 2001 12:54:24 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 4A5E85D01F; Mon, 2 Jul 2001 14:54:14 -0500 (CDT) Date: Mon, 2 Jul 2001 14:54:14 -0500 From: Alfred Perlstein To: Julian Elischer Cc: current@freebsd.org Subject: Re: RFC: Kernel thread system nomenclature. Message-ID: <20010702145414.R84523@sneakerz.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from julian@elischer.org on Mon, Jul 02, 2001 at 02:16:16PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oh what a bikeshed you've begun. :) * Julian Elischer [010702 14:39] wrote: > > The time has come (now that we have a design) to assign names to the > various entities that will be created when we implement the > (current name) KSE code. > > I have already done initial work on this and have a system running with > the proc structure split into 4 parts. > > The names of these parts need to be fully decided and agreed upon now > while the changes are limited to 2 files :-) The next change requires > editing almost every file in the kernel. The KSE names were a temporary > measure to identify these while their functions were being decided. > > > Here are the entities, a decription of what they do, and some suggested > names: > > 1) This structure 'owns' all the resources that are relavent to the > process. It owns the credentials, the VM space, the file desriptors, > (possibly the signal state), the parent process, the child processes > etc. etc. > > Suggested names: proc, task (others?) Proc, this keeps the unix convention, a task is confusing, at least to me because afaik in Linux a task is actually a thread. Keeping it as proc will also require fewer changes to the code. :) > > 2) The second structure owns the scheduling parameters. All scheduling > decisions are made according to information held in this structure. The is > by default one of these per each of the above (#1) structure. However the > threads library may make more should it wish to shedule some threads at a > different priority. Each of these competes with the weight of a process in > the system scope. In the case where there are not per-cpu run queues, THIS > would be put on the run queues. There may be between 1 and M of these > where M is the remaining rlimit on processes. (they count as processes > against the rlimits) > > Suggested names: schedblock (SB), > Kernel Schedulabale Entity Group (KSEG), > KSE (confusing but acurate), > SchedEntry, (SE?), > Process Schduling control block (pscb) Scheduling control block. Remove 'Process' because as far as I understand it, it's not really a process, it's a group of threads. > 3) The third structure is a container for running code contexts. The > concurrency of a MP machine can be exploited by having multiple of these > entities, each of which most be run on a different processor. With per-CPU > run queues, these would be on the queues, but the controling parameters > are inherrited from the 2nd structure. There may be between 1 and N (where > N is the number of processors) of these entities per each of the 2nd > structure type. Eligible contexts are run in either kernel or user mode > when this is scheduled. Each of these has a separate upcall context stored > for communication with the Userland scheduler. > > Suggested names: Kernel Schedulable Entity(KSE), > thread container(TC), > Scheduler Virtual processor(SVP), > Scheduler Slot(schedslot, ss?) > Thread processor (tp?) I think thread container makes the most sense. > 4) The last entity is the 'kernel context' structure. > This contains the kernel stack for whatever thread of execution is being > run and is what is saved onto the sleep queues when a tread of execution > blocks. All the context needed to restart a thread is saved in this. > In the current system this information is stored in a combination of the > proc struct, the U area and the kernel stack. There can be an almost > unlimited (resource limited) number of these which would indicate > a large number of blocked syscalls. They are allocated to the #2 > structure and may run under more than one of the #3 entities during the > course of a syscall if there are context switches. they would have some > affinity to the last #3 they ran on for cache reasons, but conld be > switched to another #3 that is connected to the same #2 if it were idle. > > Suggested names: Thread Context Block (TCB) > Kernel Schedulabel Entity Context (KSEC) > Thread Context (TCTX) thread/curthread, if you think about it, this is what it boils down to at the most basic level and therefore keeps the terminology simple. > Any more suggestions are most welcome! (but seeing as how I'm doing the > code I will select as I see fit at the end of the discussion. > > Almost all of the current 'proc' pointers being passed around the system > in syscalls will be changed to the #4 item. In addition, most accesses to > curproc would point to a curthread (curr-#4) or a curr#3, so the names > selected will be used a lot. > The exctent of these edits almost makes it worthwhile to call the #4 item > 'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). > (everyhting to do with sleeping, blocking, and waking up would > avoid changes, and everywhere a syscall passes down "struct proc *p" > would avoid changes. I agree, but keeping the old terminology to describe things isn't proper and can lead to code mistakes and confusion as a thread is not really a process. It gets sort of confusing, as I'm not really sure where the thread actually is, #3 or #4, it's actually 4, however you can only run 'amount of #3' threads at the same time. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 13:18:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id BF88837B403 for ; Mon, 2 Jul 2001 13:18:43 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA13710; Mon, 2 Jul 2001 14:43:13 -0700 (PDT) Date: Mon, 2 Jul 2001 14:43:12 -0700 (PDT) From: Julian Elischer To: Alfred Perlstein Cc: current@freebsd.org Subject: Re: RFC: Kernel thread system nomenclature. In-Reply-To: <20010702145414.R84523@sneakerz.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001, Alfred Perlstein wrote: > Oh what a bikeshed you've begun. :) > > Proc, this keeps the unix convention, a task is confusing, at least > to me because afaik in Linux a task is actually a thread. Keeping it > as proc will also require fewer changes to the code. :) Actually this would REDUCE teh size of the change.. MOST of the proc pointers will be changeing to #4 whatever that becomes. calling THAT proc would be the easiest :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 13:23:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id AC02D37B403 for ; Mon, 2 Jul 2001 13:23:53 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA14076; Mon, 2 Jul 2001 16:23:06 -0400 (EDT) Date: Mon, 2 Jul 2001 16:23:06 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: RFC: Kernel thread system nomenclature. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001, Julian Elischer wrote: > > The time has come (now that we have a design) to assign names to the > various entities that will be created when we implement the > (current name) KSE code. > > I have already done initial work on this and have a system running with > the proc structure split into 4 parts. > > The names of these parts need to be fully decided and agreed upon now > while the changes are limited to 2 files :-) The next change requires > editing almost every file in the kernel. The KSE names were a temporary > measure to identify these while their functions were being decided. > > Here are the entities, a decription of what they do, and some suggested > names: > > 1) This structure 'owns' all the resources that are relavent to the > process. It owns the credentials, the VM space, the file desriptors, > (possibly the signal state), the parent process, the child processes > etc. etc. > > Suggested names: proc, task (others?) > > 2) The second structure owns the scheduling parameters. All scheduling > decisions are made according to information held in this structure. The is > by default one of these per each of the above (#1) structure. However the > threads library may make more should it wish to shedule some threads at a > different priority. Each of these competes with the weight of a process in > the system scope. In the case where there are not per-cpu run queues, THIS > would be put on the run queues. There may be between 1 and M of these > where M is the remaining rlimit on processes. (they count as processes > against the rlimits) > > Suggested names: schedblock (SB), > Kernel Schedulabale Entity Group (KSEG), > KSE (confusing but acurate), > SchedEntry, (SE?), > Process Schduling control block (pscb) I think Mike's point about not naming this kseg was good (to avoid confusion with kernel segment). scheduling param, schedparam? scheduling resource, schedres? > 3) The third structure is a container for running code contexts. The > concurrency of a MP machine can be exploited by having multiple of these > entities, each of which most be run on a different processor. With per-CPU > run queues, these would be on the queues, but the controling parameters > are inherrited from the 2nd structure. There may be between 1 and N (where > N is the number of processors) of these entities per each of the 2nd > structure type. Eligible contexts are run in either kernel or user mode > when this is scheduled. Each of these has a separate upcall context stored > for communication with the Userland scheduler. > > Suggested names: Kernel Schedulable Entity(KSE), > thread container(TC), > Scheduler Virtual processor(SVP), > Scheduler Slot(schedslot, ss?) > Thread processor (tp?) > > 4) The last entity is the 'kernel context' structure. > This contains the kernel stack for whatever thread of execution is being > run and is what is saved onto the sleep queues when a tread of execution > blocks. All the context needed to restart a thread is saved in this. > In the current system this information is stored in a combination of the > proc struct, the U area and the kernel stack. There can be an almost > unlimited (resource limited) number of these which would indicate > a large number of blocked syscalls. They are allocated to the #2 > structure and may run under more than one of the #3 entities during the > course of a syscall if there are context switches. they would have some > affinity to the last #3 they ran on for cache reasons, but conld be > switched to another #3 that is connected to the same #2 if it were idle. > > Suggested names: Thread Context Block (TCB) > Kernel Schedulabel Entity Context (KSEC) > Thread Context (TCTX) Other than renaming kseg to something else, the names we were using previously seemed OK. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 13:28:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id AF03637B403 for ; Mon, 2 Jul 2001 13:28:26 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA14677; Mon, 2 Jul 2001 16:27:35 -0400 (EDT) Date: Mon, 2 Jul 2001 16:27:34 -0400 (EDT) From: Daniel Eischen To: Alfred Perlstein Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: RFC: Kernel thread system nomenclature. In-Reply-To: <20010702145414.R84523@sneakerz.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001, Alfred Perlstein wrote: > Scheduling control block. Remove 'Process' because as far as I > understand it, it's not really a process, it's a group of threads. SCB is SCSI Command Block. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 13:34: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id 166D137B406 for ; Mon, 2 Jul 2001 13:34:07 -0700 (PDT) (envelope-from gh@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 1012) id 97ED162D0A; Mon, 2 Jul 2001 15:34:01 -0500 (CDT) Date: Mon, 2 Jul 2001 15:34:01 -0500 From: GH To: Damieon Stark Cc: current@freebsd.org Subject: Re: unified pwutil library - thoughts? Message-ID: <20010702153401.A55131@over-yonder.net> References: <20010624210541.A12494@morpheus.mn.rr.com> <20010702113626.A21098@morpheus.mn.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010702113626.A21098@morpheus.mn.rr.com>; from visigoth@covertdata.com on Mon, Jul 02, 2001 at 11:36:26AM -0500 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 02, 2001 at 11:36:26AM -0500, some SMTP stream spewed forth: > > Hey all... > > So, by the fact that I got _no_ replies I must surmise that either my > message didn't get posted (confirmed posting with archive), or people > didn't read it, or _nobody_ thinks it is a good idea ;) but if nobody > thinks it is a good idea, I _think_ I would have gotten some flames/feedback. > Here goes again... Below is the message I sent about a unified libpwutil, and > possibly integrating it into FreeBSD. _ANY_ feedback, positive or negitive > would be appreciated as it will help to validate my existance ;) > It sounds like a good idea to me. It would be more efficient, cleaner, and easier to maintain and use. It would be rather non-standard, though. gh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 13:54:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1BAFF37B401 for ; Mon, 2 Jul 2001 13:54:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f62JHQU36462; Mon, 2 Jul 2001 13:17:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107021917.f62JHQU36462@harmony.village.org> To: mjacob@feral.com Subject: Re: Jesus, never mind....Re: kernel configs completely broken Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Jul 2001 11:20:49 PDT." <20010702112030.J23320-100000@wonky.feral.com> References: <20010702112030.J23320-100000@wonky.feral.com> Date: Mon, 02 Jul 2001 13:17:26 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010702112030.J23320-100000@wonky.feral.com> Matthew Jacob writes: : I somehow missed the change to sys/ARCH/compile. I'm sorry that I didn't send a heads up to current. I've corrected that now. Sorry for difficulties that you've had. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 14:21: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from ajax.cnchost.com (ajax.cnchost.com [207.155.248.31]) by hub.freebsd.org (Postfix) with ESMTP id E583737B403 for ; Mon, 2 Jul 2001 14:20:58 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by ajax.cnchost.com id RAA06256; Mon, 2 Jul 2001 17:20:53 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200107022120.RAA06256@ajax.cnchost.com> To: Julian Elischer Cc: current@freebsd.org Subject: Re: RFC: Kernel thread system nomenclature. In-reply-to: Your message of "Mon, 02 Jul 2001 14:16:16 PDT." Date: Mon, 02 Jul 2001 14:20:52 -0700 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there is an online description of what you guys decided at Usenix? An xfig picture would be very helpful! > 1) This structure 'owns' all the resources that are relavent to the > process. It owns the credentials, the VM space, the file desriptors, > (possibly the signal state), the parent process, the child processes > etc. etc. > > Suggested names: proc, task (others?) proc or process? Actually "domain" is more appropriate once you can have multiple threads sharing the same VM. > 2) The second structure owns the scheduling parameters. All scheduling > decisions are made according to information held in this structure. The is > by default one of these per each of the above (#1) structure. However the > threads library may make more should it wish to shedule some threads at a > different priority. Each of these competes with the weight of a process in > the system scope. In the case where there are not per-cpu run queues, THIS > would be put on the run queues. There may be between 1 and M of these > where M is the remaining rlimit on processes. (they count as processes > against the rlimits) > > Suggested names: schedblock (SB), > Kernel Schedulabale Entity Group (KSEG), > KSE (confusing but acurate), > SchedEntry, (SE?), > Process Schduling control block (pscb) How about just schedule or schedule set? It is a perfectly good noun! "control block" is just noise at this point :-) Seems like the old (Thoth) team concept. Can a thread context belong to more than one of these? > 3) The third structure is a container for running code contexts. The > concurrency of a MP machine can be exploited by having multiple of these > entities, each of which most be run on a different processor. With per-CPU > run queues, these would be on the queues, but the controling parameters > are inherrited from the 2nd structure. There may be between 1 and N (where > N is the number of processors) of these entities per each of the 2nd > structure type. Eligible contexts are run in either kernel or user mode > when this is scheduled. Each of these has a separate upcall context stored > for communication with the Userland scheduler. > > Suggested names: Kernel Schedulable Entity(KSE), > thread container(TC), > Scheduler Virtual processor(SVP), > Scheduler Slot(schedslot, ss?) > Thread processor (tp?) > > 4) The last entity is the 'kernel context' structure. > This contains the kernel stack for whatever thread of execution is being > run and is what is saved onto the sleep queues when a tread of execution > blocks. All the context needed to restart a thread is saved in this. > In the current system this information is stored in a combination of the > proc struct, the U area and the kernel stack. There can be an almost > unlimited (resource limited) number of these which would indicate > a large number of blocked syscalls. They are allocated to the #2 > structure and may run under more than one of the #3 entities during the > course of a syscall if there are context switches. they would have some > affinity to the last #3 they ran on for cache reasons, but conld be > switched to another #3 that is connected to the same #2 if it were idle. > > Suggested names: Thread Context Block (TCB) > Kernel Schedulabel Entity Context (KSEC) > Thread Context (TCTX) I am confused about #3 and #4. Sounds to me like #3 is a runnable thread context and #4 is a sleeping/waiting thread context. A runnable thread is bound to a processor. For example, Given processes A, B & C processors X & Y, Threads A1, A2, B1 are runnable; A3, B2, C1, C2 are waiting, A1,A3 in one and A2 in another schedule set, A1 and A2 are actually running, B1 is waiting for a processor we have 3 #1 entities (A, B, C) 4 #2 entities ({A1,A3}, {A2}, {B1, B2}, {C1, C2}) 3 #3 entities (A1, A2, B1) 4 #4 entities (A3, B2, C1, C2) Correct? I am not sure how actually running threads are distinguished from a runnable thread. > The exctent of these edits almost makes it worthwhile to call the #4 item > 'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). > (everyhting to do with sleeping, blocking, and waking up would > avoid changes, and everywhere a syscall passes down "struct proc *p" > would avoid changes. But this would confuse future hackers. Appropriate names really help even if it means moe editing now. I have found that the process of coming up with the right names frequently simplifies things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 15:34:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from Stalker.alfacom.net (Stalker2.Alfacom.net [212.26.133.81]) by hub.freebsd.org (Postfix) with ESMTP id 46D5D37B401; Mon, 2 Jul 2001 15:34:28 -0700 (PDT) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (dup-124-82.Alfacom.net [193.108.124.82]) by Stalker.alfacom.net (8.9.3/8.9.3) with ESMTP id BAA27305; Tue, 3 Jul 2001 01:34:15 +0300 (EEST) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.11.4/8.11.4) with ESMTP id f62MXxd00997; Tue, 3 Jul 2001 01:34:03 +0300 (EEST) (envelope-from vkushnir@Alfacom.net) X-Authentication-Warning: kushnir1.kiev.ua: volodya owned process doing -bs Date: Tue, 3 Jul 2001 01:33:58 +0300 (EEST) From: Vladimir Kushnir X-X-Sender: To: Mike Smith Cc: Subject: Re: HEADS UP: ACPI update - thermal management In-Reply-To: <200106280635.f5S6Z7w07241@mass.dis.org> Message-ID: <20010703012419.C408-100000@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Here's some experience with ACPI. It does work (which is good :-) but for some reason it turns off computer (always from under X) at rather low temperatures with emergency shutdown. How could I debug ACPI to provide more details? Regards, Vladimir -- Vladimir Kushnir - vkushnir@Alfacom.net On Wed, 27 Jun 2001, Mike Smith wrote: > > This is just a heads-up to let folks know that I've committed some early > code to handle thermal management under ACPI. This should DTRT with > active cooling (fans, etc.). It won't help with passive cooling yet (we > need to sort out the processor device control first), and it may well > have problems (there are places where the specification is vague about > what should be in the namespace and my ability to test these options is > limited). > > Testing and feedback would be welcome. I'll try to get the new ACPI CA > stuff merged tomorrow, unless there are too many people bugging me at > Usenix. 8) > > Regards, > Mike > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 16: 6:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 59E9C37B406 for ; Mon, 2 Jul 2001 16:06:15 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA24721; Tue, 3 Jul 2001 09:04:28 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01K5HLV8RREOVFAEWZ@cim.alcatel.com.au>; Tue, 3 Jul 2001 09:04:05 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f62N4N221578; Tue, 03 Jul 2001 09:04:23 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 03 Jul 2001 09:04:23 +1000 From: Peter Jeremy Subject: Re: funny strlen defines in sys/alpha/alpha/alpha-gdbstub.c In-reply-to: <20010702113423.B7023@hades.hell.gr>; from keramida@ceid.upatras.gr on Mon, Jul 02, 2001 at 11:34:25AM +0300 To: Giorgos Keramidas Cc: current@FreeBSD.ORG Mail-Followup-To: Giorgos Keramidas , current@FreeBSD.ORG Message-id: <20010703090423.V506@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010702113423.B7023@hades.hell.gr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001-Jul-02 11:34:25 +0300, Giorgos Keramidas wrote: > 130 #define strlen gdb_strlen > 131 #define strcpy gdb_strcpy > >Is it really necessary to do this funny thing with the #defines? I >mean, why not replace the calls with gdb_XXX() ourselves and be done >with it? Alternatively, given the XXX comment, why not delete the local copies of str{cpy,len}() and just usr the library versions? The original reason appears to be to avoid the possibility that str{cpy,len}() are not re-entrant. The FreeBSD ones _are_ re-entrant and it doesn't seem likely that we will re-write them not to be re-entrant. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 16:36:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 7D21137B403 for ; Mon, 2 Jul 2001 16:36:51 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (patr530-b047.otenet.gr [195.167.121.175]) by mailsrv.otenet.gr (8.11.1/8.11.1) with ESMTP id f62NamK03175; Tue, 3 Jul 2001 02:36:48 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.4/8.11.3) id f62Nalp69550; Tue, 3 Jul 2001 02:36:47 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 3 Jul 2001 02:36:46 +0300 From: Giorgos Keramidas To: Peter Jeremy Cc: current@freebsd.org Subject: Re: funny strlen defines in sys/alpha/alpha/alpha-gdbstub.c Message-ID: <20010703023646.A65147@hades.hell.gr> References: <20010702113423.B7023@hades.hell.gr> <20010703090423.V506@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010703090423.V506@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Tue, Jul 03, 2001 at 09:04:23AM +1000 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 09:04:23AM +1000, Peter Jeremy wrote: > Alternatively, given the XXX comment, why not delete the local copies > of str{cpy,len}() and just usr the library versions? The original > reason appears to be to avoid the possibility that str{cpy,len}() are > not re-entrant. The FreeBSD ones _are_ re-entrant and it doesn't seem > likely that we will re-write them not to be re-entrant. I don't have an alpha around to test any of these changes. If someone can test a kernel with these functions removed, and/or replaced by gdb_xxx equivalents, and says that it works for them, its ok with me. What you suggest about reentrancy seems OK though :-) -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 17:58:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 057C837B403 for ; Mon, 2 Jul 2001 17:58:35 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA14891; Mon, 2 Jul 2001 19:40:06 -0700 (PDT) Date: Mon, 2 Jul 2001 19:40:01 -0700 (PDT) From: Julian Elischer To: Bakul Shah Cc: current@freebsd.org Subject: Re: RFC: Kernel thread system nomenclature. In-Reply-To: <200107022120.RAA06256@ajax.cnchost.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001, Bakul Shah wrote: > Is there is an online description of what you guys decided at Usenix? > An xfig picture would be very helpful! [...] I'm working on one. > > proc or process? Actually "domain" is more appropriate once > you can have multiple threads sharing the same VM. > [...] > > How about just schedule or schedule set? It is a > perfectly good noun! "control block" is just noise at this > point :-) > > Seems like the old (Thoth) team concept. Can a thread > context belong to more than one of these? > The thread 'carrier/slot/container' (KSE) cannot, but a user thread may be reassigned from one to another by the Userland thread scheduler. In the kernel a thread must return on the same one as it went in on, but while in userland it could be switched. > > I am confused about #3 and #4. #3 is a virtual processor onto which the userland can schedule threads to run. When a syscall blocks, the virtual processor returns via an upcall and asks for another thread. So even with only one processor you get many parallel syscalls.... #4 is the context in the kernel of such a thread while doing a syscall, and possibly blocked. > Sounds to me like #3 is a > runnable thread context and #4 is a sleeping/waiting thread > context. A runnable thread is bound to a processor. For > example, Given > processes A, B & C > processors X & Y, > Threads A1, A2, B1 are runnable; A3, B2, C1, C2 are waiting, > A1,A3 in one and A2 in another schedule set, > A1 and A2 are actually running, B1 is waiting for a processor > we have > 3 #1 entities (A, B, C) > 4 #2 entities ({A1,A3}, {A2}, {B1, B2}, {C1, C2}) > 3 #3 entities (A1, A2, B1) > 4 #4 entities (A3, B2, C1, C2) > Correct? I am not sure how actually running threads are > distinguished from a runnable thread. No.. we have: 3 #1 entities (A, B, C) 4 #2 entities ({A1,A3}, {A2}, {B1, B2}, {C1, C2}) 7 #3 entities (A1, A2, A3, B1, B2, C1, C2) 4 #4 entities on sleep queues (A3, B2, C1, C2) 3 #4 entities actially running (A1,A2) 1 #4 entity hanging off the 'B' #2 entitiy, which is on the run queue. These are all teh threads that are presently IN THE KERNEL. (well, A1 and A2 might be in user space) Since A3, B2, C1, C2 are waiting obviously there are no more userland threads to be run in A*, B or C, or they would be running them. (A* is process A but at a different priority) this example is actually bad because: 1/ it doesn't show any user threads. 2/ no process has more threads than there are processors in a scheduling group. #4 items that are blocked are divorced from their #3 items, allowing the #3 items to return to userspace to get more work. #3 items are always in one of 3 states: 1/ active in userspace, awaiting a trap or fault. 2/ active in kernel space, running code from a syscall. 3/ suspended, awaiting a blocked context to be made runnable by an interrupt or by a user signal. There may be many more #4 than there are #3 but only #4 that are ACTUALLY RUNNING are assigned to an #3. a #3 has a cpu resource and a #4 has the context needed to run on it. > > But this would confuse future hackers. Appropriate names > really help even if it means moe editing now. I have found > that the process of coming up with the right names frequently > simplifies things. That's why I'm asking :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 18:15:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 56B0C37B403 for ; Mon, 2 Jul 2001 18:15:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f631FhS96205 for ; Mon, 2 Jul 2001 18:15:43 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 2 Jul 2001 18:15:43 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: current@freebsd.org Subject: FWIW, r/o source worked again Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ===> etc ===> etc/sendmail rm -f freebsd.cf (cd /usr/src/etc/sendmail && m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 20:51:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from ras.wa (usswa.ozemail.com.au [203.108.45.207]) by hub.freebsd.org (Postfix) with ESMTP id 4E0DE37B401 for ; Mon, 2 Jul 2001 20:51:52 -0700 (PDT) (envelope-from nelsont@switch.aust.com) Received: from exchange.wa.switch.aust.com (exchange [10.0.1.4]) by ras.wa (8.11.3/8.11.3) with ESMTP id f6342DY22576; Tue, 3 Jul 2001 12:02:14 +0800 Received: from switch.aust.com (10.0.2.56 [10.0.2.56]) by exchange.wa.switch.aust.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id MY63403Q; Tue, 3 Jul 2001 11:53:27 +0800 Received: by switch.aust.com (sSMTP sendmail emulation); Tue, 3 Jul 2001 11:57:29 +0800 Date: Tue, 3 Jul 2001 11:57:29 +0800 From: nelsont@switch.aust.com To: Bakul Shah Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: RFC: Kernel thread system nomenclature. Message-ID: <20010703115729.H475@freebsd06.udt> References: <200107022120.RAA06256@ajax.cnchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107022120.RAA06256@ajax.cnchost.com>; from bakul@bitblocks.com on Mon, Jul 02, 2001 at 02:20:52PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 02, 2001 at 02:20:52PM -0700, Bakul Shah wrote: > > The exctent of these edits almost makes it worthwhile to call the #4 item > > 'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). > > (everyhting to do with sleeping, blocking, and waking up would > > avoid changes, and everywhere a syscall passes down "struct proc *p" > > would avoid changes. I agree with you and Alfred here, Julian. > But this would confuse future hackers. Appropriate names > really help even if it means moe editing now. I have found > that the process of coming up with the right names frequently > simplifies things. I see no reason to change the name of struct proc just because its implementation is being modified. The new architecture being proposed is just a natural progression of FreeBSD's kernel; I fail to see how that warrants dropping previous UNIX kernel naming conventions. I don't think the argument that future kernel hackers would be confused is very substantial at all. -- Trent Nelson - Software Engineer - nelsont@switch.aust.com "A man with unlimited enthusiasm can achieve almost anything." --unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 21:18:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from ras.wa (usswa.ozemail.com.au [203.108.45.207]) by hub.freebsd.org (Postfix) with ESMTP id C488A37B405 for ; Mon, 2 Jul 2001 21:18:22 -0700 (PDT) (envelope-from nelsont@switch.aust.com) Received: from exchange.wa.switch.aust.com (exchange [10.0.1.4]) by ras.wa (8.11.3/8.11.3) with ESMTP id f634SlY22762; Tue, 3 Jul 2001 12:28:47 +0800 Received: from switch.aust.com (10.0.2.56 [10.0.2.56]) by exchange.wa.switch.aust.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id MY6340PA; Tue, 3 Jul 2001 12:20:01 +0800 Received: by switch.aust.com (sSMTP sendmail emulation); Tue, 3 Jul 2001 12:24:09 +0800 Date: Tue, 3 Jul 2001 12:24:09 +0800 From: nelsont@switch.aust.com To: Daniel Eischen Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: RFC: Kernel thread system nomenclature. Message-ID: <20010703122409.I475@freebsd06.udt> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eischen@vigrid.com on Mon, Jul 02, 2001 at 04:23:06PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 02, 2001 at 04:23:06PM -0400, Daniel Eischen wrote: > > > > 2) The second structure owns the scheduling parameters. ^^^^^^^^^^ ^^^^^^^^^^ > I think Mike's point about not naming this kseg was good (to avoid > confusion with kernel segment). > > scheduling param, schedparam? ``schedparam'' gets my vote. > Other than renaming kseg to something else, the names we were using > previously seemed OK. Agreed. The whole notion of SAs and KSEs were derived from research papers based on these naming schemes. I fail to see the justificat- ion in obfuscating the details of our new implementation by sporting a naming scheme completely unrelated to its original heritage. I don't think there's enough merit in deducing a new naming scheme when there's nothing really wrong with the naming scheme originally devised by the researchers. If it conceptually already exists in the kernel, but is just having its implementation reworked (i.e. struct proc), keep the name to be consistent with UNIX kernel convention. If it's new to the kernel (KSEs, SAs, KSEGs etc), I say keep the naming scheme as close to its theoretical/conceptual heritage as possible. > Dan Eischen Regards, Trent. -- Trent Nelson - Software Engineer - nelsont@switch.aust.com "A man with unlimited enthusiasm can achieve almost anything." --unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 2 23:11:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id CF59737B401 for ; Mon, 2 Jul 2001 23:11:38 -0700 (PDT) (envelope-from matt-l@pacbell.net) Received: from fire (1Cust142.tnt1.pasadena.ca.da.uu.net [63.28.226.142]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id XAA29536; Mon, 2 Jul 2001 23:11:35 -0700 (PDT) Message-ID: <004e01c10386$1b0e2f60$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: , References: <20010702111357.Y23320-100000@wonky.feral.com> Subject: Re: kernel configs completely broken Date: Mon, 2 Jul 2001 23:05:01 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The Makefile is actually copied over to the compile dir, is it? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== ----- Original Message ----- From: Matthew Jacob To: Sent: Monday, July 02, 2001 11:18 AM Subject: kernel configs completely broken > > > The latest config(8) changes have broken kernel configs for me such that > it apparently will not rewrite the ../compile//Makefile anymore > and important things like subr_trap, etc.. > > -matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 0:31:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D3D9037B405 for ; Tue, 3 Jul 2001 00:30:58 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f637Lkk05830; Tue, 3 Jul 2001 10:21:46 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Jul 2001 10:21:46 +0300 From: Ruslan Ermilov To: Alfred Perlstein Cc: current@FreeBSD.org Subject: Re: TIOCSCTTY Message-ID: <20010703102146.D99875@sunbay.com> Mail-Followup-To: Alfred Perlstein , current@FreeBSD.org References: <20010702185048.A21809@sunbay.com> <20010702111904.O84523@sneakerz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010702111904.O84523@sneakerz.org>; from bright@sneakerz.org on Mon, Jul 02, 2001 at 11:19:04AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 02, 2001 at 11:19:04AM -0500, Alfred Perlstein wrote: > * Ruslan Ermilov [010702 10:51] wrote: > > Hi! > > > > Could someone please explain why the following code snippet > > does not work anymore with the "/dev/console" argument? > > > > # ./tiocsctty /dev/console > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted > > I think LINT has an option to allow this. The reason, I think, is > that you don't want non-root users to be able to grab the console > output as it may allow them to obscure evil behavior. :) > If you mean UCONSOLE, I doubt this is the case: 1) I do have it compiled in. 2) I run this program under root. 3) I do not have any session that has /dev/console as its controlling tty. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 1:59: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id F307737B405 for ; Tue, 3 Jul 2001 01:58:58 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA24613; Tue, 3 Jul 2001 10:58:46 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Kazutaka YOKOTA Cc: Bruce Evans , current@freebsd.org Subject: Re: blockable sleep lock panic (and dumps still don't work) References: <200107020130.KAA23158@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 03 Jul 2001 10:58:45 +0200 In-Reply-To: <200107020130.KAA23158@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > I discussed this with jhb. We even had a test patch. Jhb told me > that someone else was working on providing proper locking in > kernel printf(). Poul-Henning, I think - I remember discussing it with him on IRC. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 2:34:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D4FE137B401 for ; Tue, 3 Jul 2001 02:34:35 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA23847; Tue, 3 Jul 2001 19:31:07 +1000 Date: Tue, 3 Jul 2001 19:29:07 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Jeremy Cc: Giorgos Keramidas , current@FreeBSD.ORG Subject: Re: funny strlen defines in sys/alpha/alpha/alpha-gdbstub.c In-Reply-To: <20010703090423.V506@gsmx07.alcatel.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 3 Jul 2001, Peter Jeremy wrote: > On 2001-Jul-02 11:34:25 +0300, Giorgos Keramidas wrote: > > 130 #define strlen gdb_strlen > > 131 #define strcpy gdb_strcpy > > > >Is it really necessary to do this funny thing with the #defines? I > >mean, why not replace the calls with gdb_XXX() ourselves and be done > >with it? Sort of. ${MACHINE_ARCH}-gdbstub.c is sort of contrib'ed code, so we should wait for the vendor to fix this. > Alternatively, given the XXX comment, why not delete the local copies > of str{cpy,len}() and just usr the library versions? The original > reason appears to be to avoid the possibility that str{cpy,len}() are > not re-entrant. The FreeBSD ones _are_ re-entrant and it doesn't seem > likely that we will re-write them not to be re-entrant. The XXX comment applies to the code without the defines. It was removed in the i386 version when these defines were added in rev.1.12. See the comment for some of the other reasons why naming the private versions the same as the extern versions is bad. Yet another reason: strlen() and strcpy() are now normally gcc builtins, so the extern versions are rarely actually used, but you have know too much about how the gcc builtins are implemented to be sure that they are safe to use here. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 2:55:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1C92537B401; Tue, 3 Jul 2001 02:55:20 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA25730; Tue, 3 Jul 2001 19:55:07 +1000 Date: Tue, 3 Jul 2001 19:53:08 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alfred Perlstein Cc: Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: TIOCSCTTY In-Reply-To: <20010702111904.O84523@sneakerz.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2 Jul 2001, Alfred Perlstein wrote: > * Ruslan Ermilov [010702 10:51] wrote: > > Hi! > > > > Could someone please explain why the following code snippet > > does not work anymore with the "/dev/console" argument? > > > > # ./tiocsctty /dev/console > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted This still works here. Perhaps another process has aquired /dev/console as its controlling terminal. > I think LINT has an option to allow this. The reason, I think, is > that you don't want non-root users to be able to grab the console > output as it may allow them to obscure evil behavior. :) You must be thinking of UCONSOLE. This has nothing to do with TIOCSTTY. It controls TIOCCONS. TIOCCONS is evil (it currently implements panic(3) (see another thread)), but TIOCSCTTY is very important for setting up job control. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 5:26:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B558237B401 for ; Tue, 3 Jul 2001 05:26:19 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f63CPOU44707; Tue, 3 Jul 2001 15:25:24 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Jul 2001 15:25:24 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: TIOCSCTTY Message-ID: <20010703152523.C39090@sunbay.com> Mail-Followup-To: Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG References: <20010702111904.O84523@sneakerz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Tue, Jul 03, 2001 at 07:53:08PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 07:53:08PM +1000, Bruce Evans wrote: > On Mon, 2 Jul 2001, Alfred Perlstein wrote: > > > * Ruslan Ermilov [010702 10:51] wrote: > > > Hi! > > > > > > Could someone please explain why the following code snippet > > > does not work anymore with the "/dev/console" argument? > > > > > > # ./tiocsctty /dev/console > > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted > > This still works here. Perhaps another process has aquired /dev/console > as its controlling terminal. > Weird. I figured out what causes this, it's moused(8). I have inserted some debug code into it to see what's going on: This is the "ps axjww" and "pstat -t" output before moused(8) calls daemon(3): USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 0 0 0 241c60 0 DLs ?? 0:00.00 (swapper) root 1 0 1 b14840 0 SLs ?? 0:00.00 /sbin/init -- root 2 0 0 241c60 0 DL ?? 0:00.00 (pagedaemon) root 3 0 0 241c60 0 DL ?? 0:00.00 (vmdaemon) root 4 0 0 241c60 0 DL ?? 0:00.00 (bufdaemon) root 5 0 0 241c60 0 DL ?? 0:00.00 (syncer) root 26 1 26 b75fc0 0 Ss ?? 0:00.00 adjkerntz -i root 128 1 128 b75340 0 Ss ?? 0:00.00 /sbin/natd -n rl0 root 149 1 149 b753c0 0 Ss ?? 0:00.03 syslogd -s daemon 156 1 156 b801c0 0 Ss ?? 0:00.00 /usr/sbin/portmap root 162 1 162 b92940 0 Ss ?? 0:00.01 amd -p -a /.amd_mnt -l syslog /host /etc/amd.map root 179 1 179 b92200 0 Ss ?? 0:00.01 /usr/sbin/cron root 182 1 182 bf8ec0 0 Ss ?? 0:00.96 /usr/sbin/sshd root 6 1 6 b14700 0 Ss+ con 0:00.13 sh /etc/rc autoboot root 214 6 6 b14700 0 S+ con 0:00.01 moused -3 -p /dev/cuaa1 -t auto root 218 214 6 b14700 0 S+ con 0:00.00 sh -c (ps axjww; pstat -t) >>/1 root 219 218 6 b14700 0 S+ con 0:00.00 sh -c (ps axjww; pstat -t) >>/1 root 220 219 6 b14700 0 R+ con 0:00.00 ps axjww LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term consolectl 0 0 0 512 448 1296 256 98 OCc c0b14700 6 term 0 0 0 0 0 0 0 0 0 - 0 0 term ttyp0 0 0 0 0 0 0 0 0 - 0 0 term ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term As you can see, process 6 (sh /etc/rc autoboot) is the session leader with /dev/console as the controlling terminal, and the same session is referenced from the `tty' structure for the consolectl device. Next, this is after moused(8) calls daemon(3): USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 0 0 0 241c60 0 DLs ?? 0:00.00 (swapper) root 1 0 1 b14840 0 SLs ?? 0:00.00 /sbin/init -- root 2 0 0 241c60 0 DL ?? 0:00.00 (pagedaemon) root 3 0 0 241c60 0 DL ?? 0:00.00 (vmdaemon) root 4 0 0 241c60 0 DL ?? 0:00.00 (bufdaemon) root 5 0 0 241c60 0 DL ?? 0:00.00 (syncer) root 26 1 26 b75fc0 0 Ss ?? 0:00.00 adjkerntz -i root 128 1 128 b75340 0 Ss ?? 0:00.00 /sbin/natd -n rl0 root 149 1 149 b753c0 0 Ss ?? 0:00.03 syslogd -s daemon 156 1 156 b801c0 0 Ss ?? 0:00.00 /usr/sbin/portmap root 162 1 162 b92940 0 Ss ?? 0:00.01 amd -p -a /.amd_mnt -l syslog /host /etc/amd.map root 179 1 179 b92200 0 Ss ?? 0:00.01 /usr/sbin/cron root 182 1 182 bf8ec0 0 Ss ?? 0:00.96 /usr/sbin/sshd root 221 1 221 bf8280 0 Ss ?? 0:00.00 moused -3 -p /dev/cuaa1 -t auto root 223 221 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 root 225 223 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 root 227 225 221 bf8280 0 R ?? 0:00.00 ps axjww root 6 1 6 b14700 0 Ss+ con 0:00.14 sh /etc/rc autoboot root 228 6 6 b14700 0 R+ con 0:00.00 sh /etc/rc autoboot LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term consolectl 0 0 0 512 448 1296 256 109 OCc c0b14700 6 term 0 0 0 0 0 0 0 0 0 - 0 0 term ttyp0 0 0 0 0 0 0 0 0 - 0 0 term ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term Nothing has changed re: consolectl. It still has session c0b14700 (with the session leader PID = 6) bound to it. moused(8) becomes a session leader for a new session with address c0bf8280 (note that MSB of the session address is not shown in the ps(1) output). Next, this is the output after the system has booted into multi-user: USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 0 0 0 241c60 0 DLs ?? 0:00.00 (swapper) root 1 0 1 b14840 0 ILs ?? 0:00.01 /sbin/init -- root 2 0 0 241c60 0 DL ?? 0:00.00 (pagedaemon) root 3 0 0 241c60 0 DL ?? 0:00.00 (vmdaemon) root 4 0 0 241c60 0 DL ?? 0:00.00 (bufdaemon) root 5 0 0 241c60 0 DL ?? 0:00.01 (syncer) root 26 1 26 b75fc0 0 Is ?? 0:00.00 adjkerntz -i root 128 1 128 b75340 0 Ss ?? 0:00.00 /sbin/natd -n rl0 root 149 1 149 b753c0 0 Ss ?? 0:00.03 syslogd -s daemon 156 1 156 b801c0 0 Is ?? 0:00.00 /usr/sbin/portmap root 162 1 162 b92940 0 Ss ?? 0:00.01 amd -p -a /.amd_mnt -l syslog /host /etc/amd.map root 179 1 179 b92200 0 Is ?? 0:00.01 /usr/sbin/cron root 182 1 182 bf8ec0 0 Is ?? 0:00.96 /usr/sbin/sshd root 221 1 221 bf8280 0 Ss ?? 0:00.08 moused -3 -p /dev/cuaa1 -t auto root 253 1 253 c02bc0 0 Is+ v0 0:00.01 /usr/libexec/getty Pc ttyv0 root 254 1 254 c02b00 0 Is v1 0:00.06 -csh (csh) root 265 254 265 c02b00 1 S v1 0:00.07 deco root 276 265 276 c02b00 1 S+ v1 0:00.00 sh -c ps axjww >> 11 root 277 276 276 c02b00 1 R+ v1 0:00.00 ps axjww root 255 1 255 c02a40 0 Is+ v2 0:00.01 /usr/libexec/getty Pc ttyv2 root 256 1 256 c02980 0 Is+ v3 0:00.01 /usr/libexec/getty Pc ttyv3 root 257 1 257 c02940 0 Is+ v4 0:00.01 /usr/libexec/getty Pc ttyv4 root 258 1 258 c02900 0 Is+ v5 0:00.01 /usr/libexec/getty Pc ttyv5 root 259 1 259 c028c0 0 Is+ v6 0:00.01 /usr/libexec/getty Pc ttyv6 root 260 1 260 c02800 0 Is+ v7 0:00.01 /usr/libexec/getty Pc ttyv7 root 261 1 261 c02e00 0 Is+ v8 0:00.01 /usr/libexec/getty Pc ttyv8 root 262 1 262 c02d40 0 Is+ v9 0:00.01 /usr/libexec/getty Pc ttyv9 root 263 1 263 c02c80 0 Is+ va 0:00.01 /usr/libexec/getty Pc ttyva The session c0b14700 has disappeared from the ps(1) output, but it is still referenced from the `tty' structure: LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC ttyvb 0 0 0 512 448 1296 256 0 - 0 0 term ttyva 0 0 0 512 448 2052 256 7 OCc c0c02c80 263 term ttyv9 0 0 0 512 448 2052 256 7 OCc c0c02d40 262 term ttyv8 0 0 0 512 448 2052 256 7 OCc c0c02e00 261 term ttyv7 0 0 0 512 448 2052 256 7 OCc c0c02800 260 term ttyv6 0 0 0 512 448 2052 256 7 OCc c0c028c0 259 term ttyv5 0 0 0 512 448 2052 256 7 OCc c0c02900 258 term ttyv4 0 0 0 512 448 2052 256 7 OCc c0c02940 257 term ttyv3 0 0 0 512 448 2052 256 7 OCc c0c02980 256 term ttyv2 0 0 0 512 448 2052 256 7 OCc c0c02a40 255 term ttyv1 0 0 0 512 448 2052 256 0 OCc c0c02b00 279 term cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term consolectl 0 0 0 512 448 1296 256 0 OCc c0b14700 0 term 0 0 0 0 0 0 0 0 0 - 0 0 term ttyp0 0 0 0 0 0 0 0 0 - 0 0 term ttyv0 0 0 0 512 448 2052 256 7 OCc c0c02bc0 253 term If I then kill moused(8), tty's t_session pointer is reset, and the next TIOCSCTTY call to /dev/console succeeds. The problem could also be demonstrated by running the following small program from /etc/rc.local. It emulates actions performed by moused(8), except moused(8) opens /dev/consolectl before a call to daemon(3), and this one opens /dev/consolectl only in a new session. What I can't understand is how opening a /dev/consolectl in a new session doesn't allow the t_session tty pointer to be reset that points to another (not existing) session. (This is probably somehow relates to the fact that the device's close() routine is called only on a last reference drop, but I'm not sure.) Run this from /etc/rc.local: #include #include #include #include #include int main(void) { int fd; if (daemon(0, 0) == -1) err(1, "daemon"); if ((fd = open("/dev/consolectl", O_RDWR)) == -1) err(1, "open /dev/consolectl"); for (;;) sleep(1000); exit(0); } Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 5:51:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 029E137B408; Tue, 3 Jul 2001 05:51:08 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.4/8.11.4) id f63Cp3v25948; Tue, 3 Jul 2001 16:51:03 +0400 (MSD) (envelope-from ache) Date: Tue, 3 Jul 2001 16:50:59 +0400 From: "Andrey A. Chernov" To: Ruslan Ermilov Cc: Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG Subject: Re: TIOCSCTTY Message-ID: <20010703165058.A25874@nagual.pp.ru> References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010703152523.C39090@sunbay.com> User-Agent: Mutt/1.3.19i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 15:25:24 +0300, Ruslan Ermilov wrote: > On Tue, Jul 03, 2001 at 07:53:08PM +1000, Bruce Evans wrote: > > On Mon, 2 Jul 2001, Alfred Perlstein wrote: > > > > > * Ruslan Ermilov [010702 10:51] wrote: > > > > Hi! > > > > > > > > Could someone please explain why the following code snippet > > > > does not work anymore with the "/dev/console" argument? > > > > > > > > # ./tiocsctty /dev/console > > > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted > > > > This still works here. Perhaps another process has aquired /dev/console > > as its controlling terminal. > > > Weird. I figured out what causes this, it's moused(8). I have inserted > some debug code into it to see what's going on: It sounds like moused needs to be fixed to drop its control terminal. -- 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 Jul 3 6:16:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 0E17E37B401; Tue, 3 Jul 2001 06:16:19 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f63DG1B09811; Tue, 3 Jul 2001 22:16:01 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f63DG2I09223; Tue, 3 Jul 2001 22:16:02 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:2sULpGRNH9utnrFXmkAQ2HZn9uO35iLo@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id WAA03263; Tue, 3 Jul 2001 22:25:36 +0900 (JST) Message-Id: <200107031325.WAA03263@zodiac.mech.utsunomiya-u.ac.jp> To: "Andrey A. Chernov" Cc: Ruslan Ermilov , Bruce Evans , Alfred Perlstein , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: TIOCSCTTY In-reply-to: Your message of "Tue, 03 Jul 2001 16:50:59 +0400." <20010703165058.A25874@nagual.pp.ru> References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> <20010703165058.A25874@nagual.pp.ru> Date: Tue, 03 Jul 2001 22:25:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> > This still works here. Perhaps another process has aquired /dev/console >> > as its controlling terminal. >> > >> Weird. I figured out what causes this, it's moused(8). I have inserted >> some debug code into it to see what's going on: > >It sounds like moused needs to be fixed to drop its control terminal. Isn't that what daemon(3) is supposed to do? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 6:19:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D1EEC37B405 for ; Tue, 3 Jul 2001 06:19:45 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f63DIVH52094; Tue, 3 Jul 2001 16:18:31 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Jul 2001 16:18:31 +0300 From: Ruslan Ermilov To: "Andrey A. Chernov" Cc: Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG Subject: Re: TIOCSCTTY Message-ID: <20010703161831.D39090@sunbay.com> Mail-Followup-To: "Andrey A. Chernov" , Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> <20010703165058.A25874@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010703165058.A25874@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Jul 03, 2001 at 04:50:59PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 04:50:59PM +0400, Andrey A. Chernov wrote: > On Tue, Jul 03, 2001 at 15:25:24 +0300, Ruslan Ermilov wrote: > > On Tue, Jul 03, 2001 at 07:53:08PM +1000, Bruce Evans wrote: > > > On Mon, 2 Jul 2001, Alfred Perlstein wrote: > > > > > > > * Ruslan Ermilov [010702 10:51] wrote: > > > > > Hi! > > > > > > > > > > Could someone please explain why the following code snippet > > > > > does not work anymore with the "/dev/console" argument? > > > > > > > > > > # ./tiocsctty /dev/console > > > > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted > > > > > > This still works here. Perhaps another process has aquired /dev/console > > > as its controlling terminal. > > > > > Weird. I figured out what causes this, it's moused(8). I have inserted > > some debug code into it to see what's going on: > > It sounds like moused needs to be fixed to drop its control terminal. > But the daemon(3) performs this function, and forked moused(8) runs without the controlling tty. Further investigation shows, that after running and killing this small program (from /etc/rc.local), I can't get a functional moused(8). It runs OK, and when with -f and -d shows mouse events, but does not show mouse cursor, etc. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 6:32:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 4B08137B401; Tue, 3 Jul 2001 06:32:26 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f63DWOB10139; Tue, 3 Jul 2001 22:32:24 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f63DWPI09791; Tue, 3 Jul 2001 22:32:25 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wvE5QSZea41E1j08WjmNCDrXx3XiI7jA@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id WAA03355; Tue, 3 Jul 2001 22:42:01 +0900 (JST) Message-Id: <200107031342.WAA03355@zodiac.mech.utsunomiya-u.ac.jp> To: Ruslan Ermilov Cc: "Andrey A. Chernov" , Bruce Evans , Alfred Perlstein , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: TIOCSCTTY In-reply-to: Your message of "Tue, 03 Jul 2001 16:18:31 +0300." <20010703161831.D39090@sunbay.com> References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> <20010703165058.A25874@nagual.pp.ru> <20010703161831.D39090@sunbay.com> Date: Tue, 03 Jul 2001 22:42:00 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> It sounds like moused needs to be fixed to drop its control terminal. >> >But the daemon(3) performs this function, and forked moused(8) runs >without the controlling tty. > >Further investigation shows, that after running and killing this small >program (from /etc/rc.local), I can't get a functional moused(8). >It runs OK, and when with -f and -d shows mouse events, but does not >show mouse cursor, etc. No error message logged by moused(8)? Very weired, indeed. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 6:33:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id E75A937B401 for ; Tue, 3 Jul 2001 06:32:46 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f63DVMG53812; Tue, 3 Jul 2001 16:31:22 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Jul 2001 16:31:22 +0300 From: Ruslan Ermilov To: "Andrey A. Chernov" , Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG Subject: Re: TIOCSCTTY Message-ID: <20010703163122.F39090@sunbay.com> Mail-Followup-To: "Andrey A. Chernov" , Bruce Evans , Alfred Perlstein , current@FreeBSD.ORG References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> <20010703165058.A25874@nagual.pp.ru> <20010703161831.D39090@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010703161831.D39090@sunbay.com>; from ru@FreeBSD.ORG on Tue, Jul 03, 2001 at 04:18:31PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 04:18:31PM +0300, Ruslan Ermilov wrote: > On Tue, Jul 03, 2001 at 04:50:59PM +0400, Andrey A. Chernov wrote: > > On Tue, Jul 03, 2001 at 15:25:24 +0300, Ruslan Ermilov wrote: > > > On Tue, Jul 03, 2001 at 07:53:08PM +1000, Bruce Evans wrote: > > > > On Mon, 2 Jul 2001, Alfred Perlstein wrote: > > > > > > > > > * Ruslan Ermilov [010702 10:51] wrote: > > > > > > Hi! > > > > > > > > > > > > Could someone please explain why the following code snippet > > > > > > does not work anymore with the "/dev/console" argument? > > > > > > > > > > > > # ./tiocsctty /dev/console > > > > > > tiocsctty: ioctl(/dev/console, TIOCSCTTY): Operation not permitted > > > > > > > > This still works here. Perhaps another process has aquired /dev/console > > > > as its controlling terminal. > > > > > > > Weird. I figured out what causes this, it's moused(8). I have inserted > > > some debug code into it to see what's going on: > > > > It sounds like moused needs to be fixed to drop its control terminal. > > > But the daemon(3) performs this function, and forked moused(8) runs > without the controlling tty. > > Further investigation shows, that after running and killing this small > program (from /etc/rc.local), I can't get a functional moused(8). > It runs OK, and when with -f and -d shows mouse events, but does not > show mouse cursor, etc. > See also PR 28468 for the origin of this thread. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 8: 7: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id ADDB537B407; Tue, 3 Jul 2001 08:06:56 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA25967; Tue, 3 Jul 2001 17:06:55 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: Still weird psm behaviour in -CURRENT From: Dag-Erling Smorgrav Date: 03 Jul 2001 17:06:54 +0200 Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I hit the famed "psm probed twice" problem on my laptop last week (trackpoint didn't work at all), and tried to remove the psm and atkbd hints as advised. This resulted in a laptop with no trackpoint and no keyboard ("dumb, dumb fun" sez Juliana Hatfield), but interestingly, when I then rebooted with the previous kernel, the trackpoint worked. Both kernels were identical except for the hints, which I compile statically. No fiddling with the BIOS or anything. I'm now using the exact same kernel that didn't work before, with the exact same hints, on the exact same hardware, and I get the exact same PnP "can't assign resources" messages as before, but the trackpoint works. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 8:17:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 103B337B405; Tue, 3 Jul 2001 08:17:25 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA15455; Wed, 4 Jul 2001 01:17:18 +1000 Date: Wed, 4 Jul 2001 01:15:17 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: TIOCSCTTY In-Reply-To: <20010703152523.C39090@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 3 Jul 2001, Ruslan Ermilov wrote: > Weird. I figured out what causes this, it's moused(8). I have inserted > some debug code into it to see what's going on: > ... > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > consolectl 0 0 0 512 448 1296 256 98 OCc c0b14700 6 term > 0 0 0 0 0 0 0 0 0 - 0 0 term > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term > > As you can see, process 6 (sh /etc/rc autoboot) is the session leader with > /dev/console as the controlling terminal, and the same session is referenced > from the `tty' structure for the consolectl device. The bug seems to be caused by a combination of sloppy code in moused, dubious aliasing in syscons and a known bug in cnclose(): 1. moused opens /dev/consolectl before becoming a daemon. This shouldn't be a problem, since /dev/consolectl should be a completely different device from the controlling terminal (which is /dev/console, although you can't really see that from the ps output since "consolectl" is a poorly chosen name which is indistinguishable from "console" after ps truncates it to 3 characters). However: 2. syscons.c makes /dev/consolectl a sort of alias for /dev/consolectl: dev = make_dev(&sc_cdevsw, SC_CONSOLECTL, UID_ROOT, GID_WHEEL, 0600, "consolectl"); dev->si_tty = sc_console_tty = ttymalloc(sc_console_tty); This obviously breaks the pstat output and complicates debugging (pstat should display "console" instead of "consolectl"). It apparently also breaks last-close stuff when /dev/console is closed. 3. cnclose() already has broken handling of controlling terminals when /dev/console is last-closed while the physical device underlying the console is open and /dev/console is a controlling terminal. /dev/consolectl is different from the physical device underlying /dev/console (even if the latter is /dev/ttyv0), and is not understood by cnclose(), but I think the same problem and fix apply. > Next, this is after moused(8) calls daemon(3): > > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > ... > root 221 1 221 bf8280 0 Ss ?? 0:00.00 moused -3 -p /dev/cuaa1 -t auto > root 223 221 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 > root 225 223 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 > root 227 225 221 bf8280 0 R ?? 0:00.00 ps axjww > root 6 1 6 b14700 0 Ss+ con 0:00.14 sh /etc/rc autoboot > root 228 6 6 b14700 0 R+ con 0:00.00 sh /etc/rc autoboot No problem here. > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > consolectl 0 0 0 512 448 1296 256 109 OCc c0b14700 6 term > 0 0 0 0 0 0 0 0 0 - 0 0 term > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term > > Nothing has changed re: consolectl. It still has session c0b14700 (with > the session leader PID = 6) bound to it. Nothing should have changed, since moused only closed a dup'ed descriptor for /dev/console. The last-close bugs will bite later when ancestors of moused all close all their descriptors for /dev/console. Here we can still see the consolectl vs console confusion. > Next, this is the output after the system has booted into multi-user: > ... > The session c0b14700 has disappeared from the ps(1) output, but it is still > referenced from the `tty' structure: > > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > ttyvb 0 0 0 512 448 1296 256 0 - 0 0 term > ttyva 0 0 0 512 448 2052 256 7 OCc c0c02c80 263 term > ttyv9 0 0 0 512 448 2052 256 7 OCc c0c02d40 262 term > ttyv8 0 0 0 512 448 2052 256 7 OCc c0c02e00 261 term > ttyv7 0 0 0 512 448 2052 256 7 OCc c0c02800 260 term > ttyv6 0 0 0 512 448 2052 256 7 OCc c0c028c0 259 term > ttyv5 0 0 0 512 448 2052 256 7 OCc c0c02900 258 term > ttyv4 0 0 0 512 448 2052 256 7 OCc c0c02940 257 term > ttyv3 0 0 0 512 448 2052 256 7 OCc c0c02980 256 term > ttyv2 0 0 0 512 448 2052 256 7 OCc c0c02a40 255 term > ttyv1 0 0 0 512 448 2052 256 0 OCc c0c02b00 279 term > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > consolectl 0 0 0 512 448 1296 256 0 OCc c0b14700 0 term > 0 0 0 0 0 0 0 0 0 - 0 0 term > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > ttyv0 0 0 0 512 448 2052 256 7 OCc c0c02bc0 253 term Hmm. ttyv0 apparently doesn't share a tty struct with consolectl/console. I'm familiar with this feature from old versions of syscons but thought that it was lost. This used to prevent bug (3) for syscons (it always affected sio and maybe pcvt), but we now have it via the consolectl alias. I wonder if the bogus line of zeros is related to miscounting the single tty struct for console/consolectl as two structs. > What I can't understand is how opening a /dev/consolectl in a new session > doesn't allow the t_session tty pointer to be reset that points to another > (not existing) session. > > (This is probably somehow relates to the fact that the device's close() > routine is called only on a last reference drop, but I'm not sure.) I think I understand the details now: - on i386's, sccnprobe() sets the physical device for /dev/console to /dev/consolectl. Thus /dev/consolectl is more than "sort of" an alias for /dev/console, and bug (3) bites. I don't understand the minor detail that pstat prefers the "consolectl" alias. - on alphas, sccnattach() sets the physical device for /dev/console to /dev/ttyv0. Thus the bugs are gratuitously different. I use the following fix for (3). This is not suitable for committing, due to probable races clearing the state. E.g., p_session can apparently change before d_close() returns, so my closing_ctty flag may become invalid, but since there is no explicit locking it's not clear that other fatal changes can't happen. Hopefully everything is protected by Giant until d_close() blocks, but the code after d_close() blocks isn't very careful about the state. It needs to be, because d_open() can be called successfully while d_close() is blocked! Note that d_close() can block for arbitrarily long waiting for output to drain, and it is useful for d_open() to succeed while d_close() is busy, if only to unblock the close by changing the drain wait time. --- Index: fs/specfs/spec_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/specfs/spec_vnops.c,v retrieving revision 1.159 diff -u -2 -r1.159 spec_vnops.c --- fs/specfs/spec_vnops.c 2001/05/23 22:20:29 1.159 +++ fs/specfs/spec_vnops.c 2001/05/24 11:22:57 @@ -570,4 +570,5 @@ struct proc *p = ap->a_p; dev_t dev = vp->v_rdev; + int closing_ctty, error; /* @@ -579,9 +580,12 @@ * if the reference count is 2 (this last descriptor * plus the session), release the reference from the session. + * But don't clear s_ttyvp yet, since at least cnclose() + * needs it. */ + closing_ctty = 0; if (vcount(vp) == 2 && p && (vp->v_flag & VXLOCK) == 0 && vp == p->p_session->s_ttyvp) { vrele(vp); - p->p_session->s_ttyvp = NULL; + closing_ctty = 1; } /* @@ -601,5 +605,8 @@ return (0); } - return (devsw(dev)->d_close(dev, ap->a_fflag, S_IFCHR, p)); + error = devsw(dev)->d_close(dev, ap->a_fflag, S_IFCHR, p); + if (closing_ctty) + p->p_session->s_ttyvp = NULL; + return (error); } Index: kern/tty_cons.c =================================================================== RCS file: /home/ncvs/src/sys/kern/tty_cons.c,v retrieving revision 1.91 diff -u -2 -r1.91 tty_cons.c --- kern/tty_cons.c 2001/06/13 10:58:36 1.91 +++ kern/tty_cons.c 2001/06/14 04:05:36 @@ -50,4 +50,5 @@ #include #include +#include #include @@ -297,5 +298,19 @@ return (0); cndev = cn_tab->cn_dev; + + /* + * Close the controlling tty aspects of the tty if the tty is a + * controlling tty and it belongs to the device being closed. + * This is normally done in ttyclose(), but we won't reach there + * if both devices are open. + */ cn_tp = cndev->si_tty; + if (cn_tp != NULL && cn_tp->t_session != NULL && + cn_tp->t_session->s_ttyvp != NULL && + cn_tp->t_session->s_ttyvp->v_rdev == dev) { + cn_tp->t_pgrp = NULL; + cn_tp->t_session = NULL; + } + /* * act appropriatly depending on whether it's /dev/console @@ -307,13 +322,6 @@ /* the physical device is about to be closed */ cn_phys_is_open = 0; - if (cn_is_open) { - if (cn_tp) { - /* perform a ttyhalfclose() */ - /* reset session and proc group */ - cn_tp->t_pgrp = NULL; - cn_tp->t_session = NULL; - } + if (cn_is_open) return (0); - } } else if (major(dev) != major(cndev)) { /* the logical console is about to be closed */ --- Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 8:45:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 9610A37B403 for ; Tue, 3 Jul 2001 08:45:02 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f63FiHN71929; Tue, 3 Jul 2001 18:44:17 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Jul 2001 18:44:17 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: TIOCSCTTY Message-ID: <20010703184417.A69095@sunbay.com> Mail-Followup-To: Bruce Evans , current@FreeBSD.ORG References: <20010703152523.C39090@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Wed, Jul 04, 2001 at 01:15:17AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 04, 2001 at 01:15:17AM +1000, Bruce Evans wrote: > On Tue, 3 Jul 2001, Ruslan Ermilov wrote: > > > Weird. I figured out what causes this, it's moused(8). I have inserted > > some debug code into it to see what's going on: > > ... > > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > > consolectl 0 0 0 512 448 1296 256 98 OCc c0b14700 6 term > > 0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term > > > > As you can see, process 6 (sh /etc/rc autoboot) is the session leader with > > /dev/console as the controlling terminal, and the same session is referenced > > from the `tty' structure for the consolectl device. > > The bug seems to be caused by a combination of sloppy code in moused, > dubious aliasing in syscons and a known bug in cnclose(): > 1. moused opens /dev/consolectl before becoming a daemon. This shouldn't > be a problem, since /dev/consolectl should be a completely different device > from the controlling terminal (which is /dev/console, although you can't > really see that from the ps output since "consolectl" is a poorly chosen > name which is indistinguishable from "console" after ps truncates it to > 3 characters). However: > But my "emulation" program opens /dev/consolectl _after_ becoming a daemon. And yes, I can distinguish "console" from "consolectl" with ``-O tty''. > 2. syscons.c makes /dev/consolectl a sort of alias for /dev/consolectl: > > dev = make_dev(&sc_cdevsw, SC_CONSOLECTL, > UID_ROOT, GID_WHEEL, 0600, "consolectl"); > dev->si_tty = sc_console_tty = ttymalloc(sc_console_tty); > > This obviously breaks the pstat output and complicates debugging (pstat > should display "console" instead of "consolectl"). It apparently also > breaks last-close stuff when /dev/console is closed. > 3. cnclose() already has broken handling of controlling terminals when > /dev/console is last-closed while the physical device underlying the > console is open and /dev/console is a controlling terminal. > /dev/consolectl is different from the physical device underlying > /dev/console (even if the latter is /dev/ttyv0), and is not understood > by cnclose(), but I think the same problem and fix apply. > > > Next, this is after moused(8) calls daemon(3): > > > > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > > ... > > root 221 1 221 bf8280 0 Ss ?? 0:00.00 moused -3 -p /dev/cuaa1 -t auto > > root 223 221 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 > > root 225 223 221 bf8280 0 S ?? 0:00.00 sh -c (ps axjww; pstat -t) >>/1 > > root 227 225 221 bf8280 0 R ?? 0:00.00 ps axjww > > root 6 1 6 b14700 0 Ss+ con 0:00.14 sh /etc/rc autoboot > > root 228 6 6 b14700 0 R+ con 0:00.00 sh /etc/rc autoboot > > No problem here. > I did not mean there is. :-) > > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > > consolectl 0 0 0 512 448 1296 256 109 OCc c0b14700 6 term > > 0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyv0 0 0 0 512 448 1296 256 0 - 0 0 term > > > > Nothing has changed re: consolectl. It still has session c0b14700 (with > > the session leader PID = 6) bound to it. > > Nothing should have changed, since moused only closed a dup'ed descriptor > for /dev/console. > Sure, this is normal. > The last-close bugs will bite later when ancestors of > moused all close all their descriptors for /dev/console. > Here we can still see the consolectl vs console confusion. > How this applies to my "emulation" program, which opens /dev/consolectl only when in a new session? > > Next, this is the output after the system has booted into multi-user: > > ... > > The session c0b14700 has disappeared from the ps(1) output, but it is still > > referenced from the `tty' structure: > > > > LINE RAW CAN OUT IHIWT ILOWT OHWT LWT COL STATE SESS PGID DISC > > ttyvb 0 0 0 512 448 1296 256 0 - 0 0 term > > ttyva 0 0 0 512 448 2052 256 7 OCc c0c02c80 263 term > > ttyv9 0 0 0 512 448 2052 256 7 OCc c0c02d40 262 term > > ttyv8 0 0 0 512 448 2052 256 7 OCc c0c02e00 261 term > > ttyv7 0 0 0 512 448 2052 256 7 OCc c0c02800 260 term > > ttyv6 0 0 0 512 448 2052 256 7 OCc c0c028c0 259 term > > ttyv5 0 0 0 512 448 2052 256 7 OCc c0c02900 258 term > > ttyv4 0 0 0 512 448 2052 256 7 OCc c0c02940 257 term > > ttyv3 0 0 0 512 448 2052 256 7 OCc c0c02980 256 term > > ttyv2 0 0 0 512 448 2052 256 7 OCc c0c02a40 255 term > > ttyv1 0 0 0 512 448 2052 256 0 OCc c0c02b00 279 term > > cuaa1 0 0 0 512 448 216 60 0 OCcl 0 0 term > > consolectl 0 0 0 512 448 1296 256 0 OCc c0b14700 0 term > > 0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyp0 0 0 0 0 0 0 0 0 - 0 0 term > > ttyv0 0 0 0 512 448 2052 256 7 OCc c0c02bc0 253 term > > Hmm. ttyv0 apparently doesn't share a tty struct with consolectl/console. > I'm familiar with this feature from old versions of syscons but thought that > it was lost. This used to prevent bug (3) for syscons (it always affected > sio and maybe pcvt), but we now have it via the consolectl alias. > > I wonder if the bogus line of zeros is related to miscounting the single > tty struct for console/consolectl as two structs. > > > What I can't understand is how opening a /dev/consolectl in a new session > > doesn't allow the t_session tty pointer to be reset that points to another > > (not existing) session. > > > > (This is probably somehow relates to the fact that the device's close() > > routine is called only on a last reference drop, but I'm not sure.) > > I think I understand the details now: > - on i386's, sccnprobe() sets the physical device for /dev/console to > /dev/consolectl. Thus /dev/consolectl is more than "sort of" an > alias for /dev/console, and bug (3) bites. I don't understand the > minor detail that pstat prefers the "consolectl" alias. > - on alphas, sccnattach() sets the physical device for /dev/console to > /dev/ttyv0. Thus the bugs are gratuitously different. > > I use the following fix for (3). This is not suitable for committing, > due to probable races clearing the state. E.g., p_session can apparently > change before d_close() returns, so my closing_ctty flag may become > invalid, but since there is no explicit locking it's not clear that > other fatal changes can't happen. Hopefully everything is protected > by Giant until d_close() blocks, but the code after d_close() blocks > isn't very careful about the state. It needs to be, because d_open() > can be called successfully while d_close() is blocked! Note that > d_close() can block for arbitrarily long waiting for output to drain, > and it is useful for d_open() to succeed while d_close() is busy, > if only to unblock the close by changing the drain wait time. > I will try this patch tomorrow and see if it works. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 11:29:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 2369937B406; Tue, 3 Jul 2001 11:29:18 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.4/8.11.4) id f63IT3p28839; Tue, 3 Jul 2001 22:29:03 +0400 (MSD) (envelope-from ache) Date: Tue, 3 Jul 2001 22:29:02 +0400 From: "Andrey A. Chernov" To: Kazutaka YOKOTA Cc: Ruslan Ermilov , Bruce Evans , Alfred Perlstein , current@freebsd.org Subject: Re: TIOCSCTTY Message-ID: <20010703222902.A28775@nagual.pp.ru> References: <20010702111904.O84523@sneakerz.org> <20010703152523.C39090@sunbay.com> <20010703165058.A25874@nagual.pp.ru> <200107031325.WAA03263@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107031325.WAA03263@zodiac.mech.utsunomiya-u.ac.jp> User-Agent: Mutt/1.3.19i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 03, 2001 at 22:25:35 +0900, Kazutaka YOKOTA wrote: > > >> > This still works here. Perhaps another process has aquired /dev/console > >> > as its controlling terminal. > >> > > >> Weird. I figured out what causes this, it's moused(8). I have inserted > >> some debug code into it to see what's going on: > > > >It sounds like moused needs to be fixed to drop its control terminal. > > Isn't that what daemon(3) is supposed to do? Yes. If it not works this way, something fishing is in console driver itself. -- 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 Jul 3 11:37: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 73C7337B403; Tue, 3 Jul 2001 11:36:59 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA24565; Wed, 4 Jul 2001 04:36:57 +1000 Date: Wed, 4 Jul 2001 04:34:55 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: TIOCSCTTY In-Reply-To: <20010703184417.A69095@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 3 Jul 2001, Ruslan Ermilov wrote: > On Wed, Jul 04, 2001 at 01:15:17AM +1000, Bruce Evans wrote: > > On Tue, 3 Jul 2001, Ruslan Ermilov wrote: > > > ... > > > Nothing has changed re: consolectl. It still has session c0b14700 (with > > > the session leader PID = 6) bound to it. > > > > Nothing should have changed, since moused only closed a dup'ed descriptor > > for /dev/console. > > > Sure, this is normal. > > > The last-close bugs will bite later when ancestors of > > moused all close all their descriptors for /dev/console. > > Here we can still see the consolectl vs console confusion. > > > How this applies to my "emulation" program, which opens > /dev/consolectl only when in a new session? I'm not sure, since I didn't keep it :-). "This" was just more background information. The point is that holding /dev/consolectl open breaks job control stuff on /dev/console. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 11:44: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from alchemistry.net (alchemistry.net [160.79.102.254]) by hub.freebsd.org (Postfix) with ESMTP id C22CB37B406 for ; Tue, 3 Jul 2001 11:44:02 -0700 (PDT) (envelope-from mail@krel.org) Received: from [192.168.0.1] (helo=ilya) by alchemistry.net with smtp (TLSv1:RC4-MD5:128) (Exim 3.22 #1) id 15HV9W-000Dqg-00 for freebsd-current@FreeBSD.ORG; Tue, 03 Jul 2001 14:44:02 -0400 Message-ID: <017301c103f0$46c2a400$0100a8c0@ilya> From: "Ilya" To: Subject: error building kernel Date: Tue, 3 Jul 2001 14:45:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just cvsuped sources for current, was able to build world succesfully but kernel build failes at this point: linux_sysent.c:21: sizeof applied to an incomplete type linux_sysent.c:21: warning: built-in function 'exit' used without declaration linux_sysent.c:21: warning: cast discards qualifiers from pointer target type Error code 1 etc ive tried to add LINUX_COMPAT to my kernel, but got same error. there is no linux mentioning in my kernel config. can some one tell me whats wrong? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 14:33:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 5758D37B401 for ; Tue, 3 Jul 2001 14:33:42 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id f63LWxI21463 for ; Tue, 3 Jul 2001 14:32:59 -0700 (PDT) Received: from [172.30.50.86] by pain.corp.disney.com with ESMTP for freebsd-current@freebsd.org; Tue, 3 Jul 2001 14:31:26 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id OAA17356 for ; Tue, 3 Jul 2001 14:30:32 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com for freebsd-current@freebsd.org; Tue, 3 Jul 2001 14:30:32 -0700 Content-Type: text/plain; charset="us-ascii" From: Jim Pirzyk Organization: Walt Disney Feature Animation To: freebsd-current@freebsd.org Subject: chgrp broken on alpha systems Date: Tue, 3 Jul 2001 14:30:32 -0700 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01070314303203.18554@snoopy> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The current version go chkgrp does not compile under alpha systems grep FreeBSD chkgrp.c "$FreeBSD: src/usr.sbin/chkgrp/chkgrp.c,v 1.5 2001/06/24 12:38:28 des Exp $"; ===> usr.sbin/chkgrp cc -nostdinc -O -pipe -mcpu=ev4 -mcpu=ev4 -I/usr/obj/usr/src/alpha/usr/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c /usr/src/usr.sbin/chkgrp/chkgrp.c cc1: warnings being treated as errors /usr/src/usr.sbin/chkgrp/chkgrp.c: In function `main': /usr/src/usr.sbin/chkgrp/chkgrp.c:76: warning: passing arg 2 of `fgetln' from incompatible pointer type *** Error code 1 - JimP -- --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------- pirzyk@freebsd.org _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 14:43: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 1AA1637B409 for ; Tue, 3 Jul 2001 14:42:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f63LfaS06872; Tue, 3 Jul 2001 14:41:36 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 3 Jul 2001 14:41:33 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jim Pirzyk Cc: Subject: Re: chgrp broken on alpha systems In-Reply-To: <01070314303203.18554@snoopy> Message-ID: <20010703143647.G29024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hmm. Somebody must have cranked some C compilation up enough to turn warnings into errors. If I check out chkgrp into /tmp now on a system that's currently trying to update itself, I get: yorp.feral.com > make Warning: Object directory not changed from original /tmp/src/usr.sbin/chkgrp cc -O -pipe -mcpu=ev4 -c chkgrp.c chkgrp.c: In function `main': chkgrp.c:76: warning: passing arg 2 of `fgetln' from incompatible pointer type cc -O -pipe -mcpu=ev4 -o chkgrp chkgrp.o gzip -cn chkgrp.8 > chkgrp.8.gz Gee, I wonder who's turned this on for userland? The only thing these are on for is the kernel- and even that isn't -Werror. On Tue, 3 Jul 2001, Jim Pirzyk wrote: > The current version go chkgrp does not compile under alpha systems > > grep FreeBSD chkgrp.c > "$FreeBSD: src/usr.sbin/chkgrp/chkgrp.c,v 1.5 2001/06/24 12:38:28 des Exp > $"; > > ===> usr.sbin/chkgrp > cc -nostdinc -O -pipe -mcpu=ev4 -mcpu=ev4 > -I/usr/obj/usr/src/alpha/usr/include -W -Wall -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type > -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c > /usr/src/usr.sbin/chkgrp/chkgrp.c > cc1: warnings being treated as errors > /usr/src/usr.sbin/chkgrp/chkgrp.c: In function `main': > /usr/src/usr.sbin/chkgrp/chkgrp.c:76: warning: passing arg 2 of `fgetln' from > incompatible pointer type > *** Error code 1 > > - JimP > > -- > --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ > __o Jim.Pirzyk@disney.com ------------- pirzyk@freebsd.org > _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation > (*)/ (*) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 15: 8:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 3F0EA37B407 for ; Tue, 3 Jul 2001 15:08:19 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA12761; Wed, 4 Jul 2001 08:07:36 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01K5IY72Z2EOVFB1LE@cim.alcatel.com.au>; Wed, 4 Jul 2001 08:07:14 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f63M7Yf65336; Wed, 04 Jul 2001 08:07:34 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 04 Jul 2001 08:07:33 +1000 From: Peter Jeremy Subject: Re: RFC: Kernel thread system nomenclature. In-reply-to: ; from julian@elischer.org on Mon, Jul 02, 2001 at 02:16:16PM -0700 To: Julian Elischer Cc: current@FreeBSD.ORG Mail-Followup-To: Julian Elischer , current@FreeBSD.ORG Message-id: <20010704080733.C506@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001-Jul-02 14:16:16 -0700, Julian Elischer wrote: >The time has come (now that we have a design) to assign names to the >various entities that will be created when we implement the >(current name) KSE code. I'm reasonably sure that there's prior art here. What do other OS's call these entities? Our naming convention should at least be not inconsistent, and preferably consistent with other implementations. This is especially true for related implementations (BSDi and *BSD - if any of them have gone this path). This affects code portability between the *BSDs, developers who use multiple Unix variants as well as 3rd party vendors. >The exctent of these edits almost makes it worthwhile to call the #4 item >'struct proc' as the size of the diff would be MASSIVLY reduced.. :-). IMHO, what we call #4 has the biggest impact (extending to what we can reasonable call #1). As I see it, the tradeoffs are: Keeping the same name: + Everyone is familiar with it - The entity it references is no longer a `process' and hence the name is no longer descriptive. Changing the name: + The chosen name would be descriptive of its contents. - Massive diffs required (I count ~5200 references in 648 files in /sys and there are more references in userland). Personally, I'd prefer to see struct proc renamed to reflect its new role as a thread context. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 18:35:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id A2ECB37B405; Tue, 3 Jul 2001 18:35:10 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f641YxB21803; Wed, 4 Jul 2001 10:34:59 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f641YwI28237; Wed, 4 Jul 2001 10:34:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:5u41PQjeJpWxYkDW3PanOKiIWacZW30k@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id KAA05714; Wed, 4 Jul 2001 10:44:30 +0900 (JST) Message-Id: <200107040144.KAA05714@zodiac.mech.utsunomiya-u.ac.jp> To: Bruce Evans Cc: Ruslan Ermilov , Alfred Perlstein , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: TIOCSCTTY In-reply-to: Your message of "Wed, 04 Jul 2001 01:15:17 +1000." References: Date: Wed, 04 Jul 2001 10:44:29 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >The bug seems to be caused by a combination of sloppy code in moused, >dubious aliasing in syscons and a known bug in cnclose(): >1. moused opens /dev/consolectl before becoming a daemon. This shouldn't > be a problem, since /dev/consolectl should be a completely different device > from the controlling terminal (which is /dev/console, although you can't > really see that from the ps output since "consolectl" is a poorly chosen > name which is indistinguishable from "console" after ps truncates it to > 3 characters). However: >2. syscons.c makes /dev/consolectl a sort of alias for /dev/consolectl: > > dev = make_dev(&sc_cdevsw, SC_CONSOLECTL, > UID_ROOT, GID_WHEEL, 0600, "consolectl"); > dev->si_tty = sc_console_tty = ttymalloc(sc_console_tty); > > This obviously breaks the pstat output and complicates debugging (pstat > should display "console" instead of "consolectl"). It apparently also > breaks last-close stuff when /dev/console is closed. >3. cnclose() already has broken handling of controlling terminals when > /dev/console is last-closed while the physical device underlying the > console is open and /dev/console is a controlling terminal. > /dev/consolectl is different from the physical device underlying > /dev/console (even if the latter is /dev/ttyv0), and is not understood > by cnclose(), but I think the same problem and fix apply. [...] >I think I understand the details now: >- on i386's, sccnprobe() sets the physical device for /dev/console to > /dev/consolectl. Thus /dev/consolectl is more than "sort of" an > alias for /dev/console, and bug (3) bites. I don't understand the > minor detail that pstat prefers the "consolectl" alias. Yes, the dev_t (and its tty struct) for /dev/console and /dev/consolectl is one and the same. This has been so for a long time by now. Their key input and screen output take place in the same screen as ttyv0, though. >- on alphas, sccnattach() sets the physical device for /dev/console to > /dev/ttyv0. Thus the bugs are gratuitously different. When syscons was ported to alpha, it was done this way... I don't remember why. ;-( We may provide two separate copies of dev_t (and tty struct) for /dev/console and /dev/consolectl. (/dev/console's I/O will still be done in the same screen as ttyv0.) But, that won't entirely solve the bug (3), will it? /dev/console still can be accessed via /dev/console (major:0, minor:0) and via the underlaying dev_t (major:XX, minor:YY). (As a kludge, we can make /dev/console's underlaying dev_t invisible from the userland, so that it will never be open()ed directly. Ha, ha.) Kazu >I use the following fix for (3). This is not suitable for committing, >due to probable races clearing the state. E.g., p_session can apparently >change before d_close() returns, so my closing_ctty flag may become >invalid, but since there is no explicit locking it's not clear that >other fatal changes can't happen. Hopefully everything is protected >by Giant until d_close() blocks, but the code after d_close() blocks >isn't very careful about the state. It needs to be, because d_open() >can be called successfully while d_close() is blocked! Note that >d_close() can block for arbitrarily long waiting for output to drain, >and it is useful for d_open() to succeed while d_close() is busy, >if only to unblock the close by changing the drain wait time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 21:11:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-161.dsl.lsan03.pacbell.net [64.169.104.161]) by hub.freebsd.org (Postfix) with ESMTP id 2186437B401 for ; Tue, 3 Jul 2001 21:11:29 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AFC9C678A6; Tue, 3 Jul 2001 21:11:27 -0700 (PDT) Date: Tue, 3 Jul 2001 21:11:27 -0700 From: Kris Kennaway To: Matthew Jacob Cc: Jim Pirzyk , freebsd-current@FreeBSD.ORG Subject: Re: chgrp broken on alpha systems Message-ID: <20010703211126.C46524@xor.obsecurity.org> References: <01070314303203.18554@snoopy> <20010703143647.G29024-100000@wonky.feral.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Y5rl02BVI9TCfPar" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010703143647.G29024-100000@wonky.feral.com>; from mjacob@feral.com on Tue, Jul 03, 2001 at 02:41:33PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Y5rl02BVI9TCfPar Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 03, 2001 at 02:41:33PM -0700, Matthew Jacob wrote: >=20 > Hmm. Somebody must have cranked some C compilation up enough to turn > warnings into errors. >=20 > If I check out chkgrp into /tmp now on a system that's currently trying > to update itself, I get: >=20 > yorp.feral.com > make > Warning: Object directory not changed from original > /tmp/src/usr.sbin/chkgrp > cc -O -pipe -mcpu=3Dev4 -c chkgrp.c > chkgrp.c: In function `main': > chkgrp.c:76: warning: passing arg 2 of `fgetln' from incompatible > pointer type > cc -O -pipe -mcpu=3Dev4 -o chkgrp chkgrp.o > gzip -cn chkgrp.8 > chkgrp.8.gz >=20 >=20 > Gee, I wonder who's turned this on for userland? The only thing these > are on for is the kernel- and even that isn't -Werror. You're about two months out of date; we started locking down userland code around that timeframe. This one probably wasn't tested thoroughly enough on alpha. Kris --Y5rl02BVI9TCfPar Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7QpduWry0BWjoQKURAkwlAKDAsKbkxGJ5OWi6lFc06x1clZfCWgCdH75V raa6cfdWciIX554oaRy+FNI= =llkn -----END PGP SIGNATURE----- --Y5rl02BVI9TCfPar-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 21:32:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 890C937B406 for ; Tue, 3 Jul 2001 21:32:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f644WUS08446; Tue, 3 Jul 2001 21:32:30 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 3 Jul 2001 21:32:30 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Kris Kennaway Cc: Jim Pirzyk , freebsd-current@FreeBSD.ORG Subject: Re: chgrp broken on alpha systems In-Reply-To: <20010703211126.C46524@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 3 Jul 2001, Kris Kennaway wrote: > On Tue, Jul 03, 2001 at 02:41:33PM -0700, Matthew Jacob wrote: > > > > Hmm. Somebody must have cranked some C compilation up enough to turn > > warnings into errors. > > > > If I check out chkgrp into /tmp now on a system that's currently trying > > to update itself, I get: > > > > yorp.feral.com > make > > Warning: Object directory not changed from original > > /tmp/src/usr.sbin/chkgrp > > cc -O -pipe -mcpu=ev4 -c chkgrp.c > > chkgrp.c: In function `main': > > chkgrp.c:76: warning: passing arg 2 of `fgetln' from incompatible > > pointer type > > cc -O -pipe -mcpu=ev4 -o chkgrp chkgrp.o > > gzip -cn chkgrp.8 > chkgrp.8.gz > > > > > > Gee, I wonder who's turned this on for userland? The only thing these > > are on for is the kernel- and even that isn't -Werror. > > You're about two months out of date; we started locking down userland > code around that timeframe. This one probably wasn't tested > thoroughly enough on alpha. Too much frickin' ergot in yer wheaties, bucko. There is no -Wall or -Werror in normal /usr/src builds. Try again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 21:34:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 0B7E337B405; Tue, 3 Jul 2001 21:34:13 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f644YAS08501; Tue, 3 Jul 2001 21:34:10 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 3 Jul 2001 21:34:10 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Kris Kennaway , des@freebsd.org Cc: Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG S> > > are on for is the kernel- and even that isn't -Werror. > > > > You're about two months out of date; we started locking down userland > > > code around that timeframe. This one probably wasn't tested > > thoroughly enough on alpha. > > Too much frickin' ergot in yer wheaties, bucko. > > There is no -Wall or -Werror in normal /usr/src builds. Try again. Sorry- let me modify that. Not normal, except by dimwits who add WARNS?= 2 w/o checking. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 22:47:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.novagate.net (mailgate.novagate.net [205.138.138.22]) by hub.freebsd.org (Postfix) with ESMTP id 67F9337B403 for ; Tue, 3 Jul 2001 22:47:45 -0700 (PDT) (envelope-from djhill@novagate.net) Received: from rain.hill.hom (081bc122.chartermi.net [24.247.81.122]) by mailgate.novagate.net (8.11.3/8.11.3) with SMTP id f645ldq56390 for ; Wed, 4 Jul 2001 01:47:39 -0400 (EDT) (envelope-from djhill@novagate.net) Date: Wed, 4 Jul 2001 01:47:03 -0400 From: David Hill To: freebsd-current@freebsd.org Subject: system and (v)fork Message-Id: <20010704014703.4ec62b5f.djhill@novagate.net> X-Mailer: Sylpheed version 0.5.0pre2 (GTK+ 1.2.10; i386-unknown-freebsd4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello - Reading Advanced Programming in the UNIX Environment by Richard W. Stevens, I see that he says that vfork() should be used instead of fork() when you just need to use one of the exec() functions, since it doesn't need to fully copy the address space. Later in the book, he has an example system() which uses fork() to run /bin/sh -c via the execl() function. Why wouldn't he use vfork() instead of fork()? I ran FreeBSD's version of system() both by the default (using fork()) and by using vfork() I ran a loop 1000 times that called system("echo"); Here are my results: time ./app fork() vfork() 1. 4.528 3.056 0.050 0.058 2.078 1.492 2. 3.652 2.865 0.060 0.060 2.036 1.484 3. 3.735 3.022 0.068 0.041 2.031 1.506 As you can see, vfork() performed better. But, I am sure there is good reasoning for using fork() over vfork() in the system() call, and I am just curious why. Can anyone explain this? Thanks - David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 22:50:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 5CF2237B403 for ; Tue, 3 Jul 2001 22:50:20 -0700 (PDT) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (gshapiro@localhost [127.0.0.1]) by horsey.gshapiro.net (8.12.0.Beta13/8.12.0.Beta13) with ESMTP id f645oJTh010927 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Jul 2001 22:50:19 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.0.Beta13/8.12.0.Beta13) id f645oJPW010924; Tue, 3 Jul 2001 22:50:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15170.44698.988817.714880@horsey.gshapiro.net> Date: Tue, 3 Jul 2001 22:50:18 -0700 From: Gregory Neil Shapiro To: David Hill Cc: freebsd-current@FreeBSD.ORG Subject: Re: system and (v)fork In-Reply-To: <20010704014703.4ec62b5f.djhill@novagate.net> References: <20010704014703.4ec62b5f.djhill@novagate.net> X-Mailer: VM 6.92 under 21.5 (beta1) "anise" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG djhill> Reading Advanced Programming in the UNIX Environment by Richard djhill> W. Stevens, I see that he says that vfork() should be used instead djhill> of fork() when you just need to use one of the exec() functions, djhill> since it doesn't need to fully copy the address space. djhill> Later in the book, he has an example system() which uses fork() to djhill> run /bin/sh -c via the execl() function. djhill> Why wouldn't he use vfork() instead of fork()? If there is anything that modifies memory or file descripts between the fork() and exec*() call, you can't use vfork(). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 22:54:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.novagate.net (mailgate.novagate.net [205.138.138.22]) by hub.freebsd.org (Postfix) with ESMTP id 4AD2B37B403; Tue, 3 Jul 2001 22:54:49 -0700 (PDT) (envelope-from djhill@novagate.net) Received: from rain.hill.hom (081bc122.chartermi.net [24.247.81.122]) by mailgate.novagate.net (8.11.3/8.11.3) with SMTP id f645smq57373; Wed, 4 Jul 2001 01:54:48 -0400 (EDT) (envelope-from djhill@novagate.net) Date: Wed, 4 Jul 2001 01:54:18 -0400 From: David Hill To: Gregory Neil Shapiro Cc: freebsd-current@FreeBSD.ORG Subject: Re: system and (v)fork Message-Id: <20010704015418.769fa3eb.djhill@novagate.net> In-Reply-To: <15170.44698.988817.714880@horsey.gshapiro.net> References: <20010704014703.4ec62b5f.djhill@novagate.net> <15170.44698.988817.714880@horsey.gshapiro.net> X-Mailer: Sylpheed version 0.5.0pre2 (GTK+ 1.2.10; i386-unknown-freebsd4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 3 Jul 2001 22:50:18 -0700 Gregory Neil Shapiro wrote: > djhill> Reading Advanced Programming in the UNIX Environment by Richard > djhill> W. Stevens, I see that he says that vfork() should be used instead > djhill> of fork() when you just need to use one of the exec() functions, > djhill> since it doesn't need to fully copy the address space. > > djhill> Later in the book, he has an example system() which uses fork() to > djhill> run /bin/sh -c via the execl() function. > > djhill> Why wouldn't he use vfork() instead of fork()? > > If there is anything that modifies memory or file descripts between the > fork() and exec*() call, you can't use vfork(). > Ahh, understood. Thanks for the quick response - David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 23:18:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id E89DC37B405; Tue, 3 Jul 2001 23:18:41 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f646IXB28515; Wed, 4 Jul 2001 15:18:33 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f646IXI44715; Wed, 4 Jul 2001 15:18:33 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:HpMVma2xk+6FV6y+Mut8DEGg1HbYIeOh@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id PAA07548; Wed, 4 Jul 2001 15:28:04 +0900 (JST) Message-Id: <200107040628.PAA07548@zodiac.mech.utsunomiya-u.ac.jp> To: Ruslan Ermilov , Bruce Evans , Alfred Perlstein , current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: tangled dev_t, struct tty and screen in syscons (was: Re: TIOCSCTTY) Date: Wed, 04 Jul 2001 15:28:03 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JFYI, In i386, /dev/console is the same as /dev/consolectl, and all I/O operations for /dev/console, /dev/concolectl and /dev/ttyv0 take place in the screen #0, as shown below. In alpha /dev/console is /dev/ttyv0. Access to /dev/console is routed to /dev/consolectl's dev_t by cdevsw functions in kern/tty_cons.c. When syscons is not acting as the system/kernel console, /dev/console is not connected to /dev/console or /dev/ttyv0. But /dev/consolectl still exists. /dev/console /dev/consolectl /dev/ttyv0 /dev/ttyvN | | | | V | | | dev_t | | | | V V V +--------------->dev_t dev_t dev_t | | | V V V struct tty struct tty struct tty | | | +--------------->| | | | V V screen #0 screen #N As /dev/consolectl doesn't need to get input from or put output to the screen, it can exist without an associated screen. In that sense, it perhaps doesn't even need a struct tty. Maybe we also should give /dev/console a separate a screen than ttyv0. See the figure below. But, even in this configuration, we still have two copies of dev_t for /dev/console: the native dev_t (*1) and the underlaying dev_t (*2). As make_dev(9) requires us to supply the name to create a dev_t, dev_t (*2) will appear under /dev and will be accessible from the user land, thus, we still have "the last close()" problem, I guess. /dev/console /dev/consolectl /dev/ttyv0 /dev/ttyvN | | | | V | | | dev_t | | | | *1 | | | +-------+ | | | | | | | V V V V dev_t dev_t dev_t dev_t | *2 | | | V V V V struct tty (struct tty) struct tty struct tty | | | +-------????--------------->| | | | | ??? | | | | | V V V screen #X screen #0 screen #N Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 23:54:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D5F9837B401 for ; Tue, 3 Jul 2001 23:54:07 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id IAA29363; Wed, 4 Jul 2001 08:53:59 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: mjacob@feral.com Cc: Kris Kennaway , Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems References: From: Dag-Erling Smorgrav Date: 04 Jul 2001 08:53:59 +0200 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob writes: > > Too much frickin' ergot in yer wheaties, bucko. > > > > There is no -Wall or -Werror in normal /usr/src builds. Try again. > > Sorry- let me modify that. > > Not normal, except by dimwits who add WARNS?= 2 w/o checking. Now, would it really have been so hard to just send (or even commit) a patch that declares len as a size_t rather than an unsigned int, instead of calling people names? I don't have a frickin' Alpha, you dimwit, and beast is so out of date it's useless. Send me a working Alpha with at least 64 MB RAM and 4 GB disk, then we'll talk. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 3 23:56:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id CACD837B407 for ; Tue, 3 Jul 2001 23:56:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f646uES09201; Tue, 3 Jul 2001 23:56:14 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 3 Jul 2001 23:56:14 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: Kris Kennaway , Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 4 Jul 2001, Dag-Erling Smorgrav wrote: > Matthew Jacob writes: > > > Too much frickin' ergot in yer wheaties, bucko. > > > > > > There is no -Wall or -Werror in normal /usr/src builds. Try again. > > > > Sorry- let me modify that. > > > > Not normal, except by dimwits who add WARNS?= 2 w/o checking. > > Now, would it really have been so hard to just send (or even commit) a > patch that declares len as a size_t rather than an unsigned int, I made the change. > instead of calling people names? There is, in my mailbox, a grotesque and unforgiveable insult from you from some months back. You deserve no respect whatsoever. > I don't have a frickin' Alpha, you > dimwit, and beast is so out of date it's useless. Send me a working > Alpha with at least 64 MB RAM and 4 GB disk, then we'll talk. Talk? Not if I can help it. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0: 0:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 50C0E37B407 for ; Wed, 4 Jul 2001 00:00:05 -0700 (PDT) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f64705m08269 for freebsd-current@freebsd.org; Wed, 4 Jul 2001 00:00:05 -0700 (PDT) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200107040700.f64705m08269@troutmask.apl.washington.edu> Subject: diskcheckd goes nuts on /dev/cd0 To: freebsd-current@freebsd.org Date: Wed, 4 Jul 2001 00:00:05 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm sure this is pilot error, but ... I updated a pre june 13th current to a july 3 current. Ran mergemaster and installed /etc/diskcheckd.conf without modification. Upon reboot I saw 1000s of the following message streaming up the console: dscheck(cd0): bio_bcount 512 is not on a sector boundary (ssize 2048) Checking /var/log/messages I find (note date and machine name removed): diskcheckd[213]: /dev/cd0 has 2048 byte sectors, may cause minor problems /boot/kernel/kernel: dscheck(cd0): bio_bcount 512 is not on a sector boun dary (ssize 2048) last message repeated 3 times diskcheckd[213]: error reading 512 bytes from sector 0 on /dev/cd0 Variations on the above 5 line fill that last 700 lines of /var/log/messages. I checked src/UPDATING for a diskcheckd HEADS_UP. Nada. Read the diskcheckd and the diskcheckd.conf man pages. So, I'll "fix" the problem. However, it seems that default settings in diskcheckd.conf that tell diskcheckd to check all kern.disks in system and setting diskcheckd_enable="YES" in /etc/defaults/rc.conf without a HEAD-UPS is somewhat alarming. As a side question, why is diskcheckd even looking at at /dev/cd0? From reading the man pages, one would infer that diskcheckd is intended to check for read errors on /dev/daYADA and /dev/adYADA and maybe /dev/fd0. -- Steve http://troutmask.apl.washington.edu/~kargl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0: 0:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 07A2237B41B for ; Wed, 4 Jul 2001 00:00:19 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA29412; Wed, 4 Jul 2001 09:00:15 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: mjacob@feral.com Cc: Kris Kennaway , Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems References: From: Dag-Erling Smorgrav Date: 04 Jul 2001 09:00:15 +0200 In-Reply-To: Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob writes: > There is, in my mailbox, a grotesque and unforgiveable insult from you > from some months back. You deserve no respect whatsoever. Heh. You're so cute. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0: 0:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 2CF3537B401 for ; Wed, 4 Jul 2001 00:00:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6470fS09238; Wed, 4 Jul 2001 00:00:41 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Wed, 4 Jul 2001 00:00:41 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: Kris Kennaway , Jim Pirzyk , freebsd-current@FreeBSD.ORG Subject: Re: chgrp broken on alpha systems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oh- btw- let's change the tenor of this slightly: I apologize to Dag-Erling for calling him a dimwit. On Tue, 3 Jul 2001, Matthew Jacob wrote: > > > On 4 Jul 2001, Dag-Erling Smorgrav wrote: > > > Matthew Jacob writes: > > > > Too much frickin' ergot in yer wheaties, bucko. > > > > > > > > There is no -Wall or -Werror in normal /usr/src builds. Try again. > > > > > > Sorry- let me modify that. > > > > > > Not normal, except by dimwits who add WARNS?= 2 w/o checking. > > > > Now, would it really have been so hard to just send (or even commit) a > > patch that declares len as a size_t rather than an unsigned int, > > I made the change. > > > instead of calling people names? > > There is, in my mailbox, a grotesque and unforgiveable insult from you > from some months back. You deserve no respect whatsoever. > > > I don't have a frickin' Alpha, you > > dimwit, and beast is so out of date it's useless. Send me a working > > Alpha with at least 64 MB RAM and 4 GB disk, then we'll talk. > > Talk? Not if I can help it. > > -matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0: 1:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 5621E37B403 for ; Wed, 4 Jul 2001 00:01:14 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f64717S09261; Wed, 4 Jul 2001 00:01:07 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Wed, 4 Jul 2001 00:01:07 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: Kris Kennaway , Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 4 Jul 2001, Dag-Erling Smorgrav wrote: > Matthew Jacob writes: > > There is, in my mailbox, a grotesque and unforgiveable insult from you > > from some months back. You deserve no respect whatsoever. > > Heh. You're so cute. *smooch* to you too, sweetie! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0:12:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-161.dsl.lsan03.pacbell.net [64.169.104.161]) by hub.freebsd.org (Postfix) with ESMTP id 8194537B405; Wed, 4 Jul 2001 00:12:25 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 15987678A6; Wed, 4 Jul 2001 00:12:23 -0700 (PDT) Date: Wed, 4 Jul 2001 00:12:22 -0700 From: Kris Kennaway To: Matthew Jacob Cc: Kris Kennaway , des@freebsd.org, Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems Message-ID: <20010704001222.B49299@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+pHx0qQiF2pBVqBT" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Tue, Jul 03, 2001 at 09:34:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+pHx0qQiF2pBVqBT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 03, 2001 at 09:34:10PM -0700, Matthew Jacob wrote: >=20 > S> > > are on for is the kernel- and even that isn't -Werror. > > >=20 > > > You're about two months out of date; we started locking down userland > >=20 > > > code around that timeframe. This one probably wasn't tested > > > thoroughly enough on alpha. > >=20 > > Too much frickin' ergot in yer wheaties, bucko. > >=20 > > There is no -Wall or -Werror in normal /usr/src builds. Try again. >=20 > Sorry- let me modify that. >=20 > Not normal, except by dimwits who add WARNS?=3D 2 w/o checking. This kind of language isn't called for. People make mistakes, and insulting them for it serves no useful purpose. Kris --+pHx0qQiF2pBVqBT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7QsHVWry0BWjoQKURAr1bAKD3MuYwoRCYm1/y47R07rDNCcAiFgCcDdLa wqfeG77WWW5s70KuA7ytvII= =fS5c -----END PGP SIGNATURE----- --+pHx0qQiF2pBVqBT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0:14:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 847D237B403; Wed, 4 Jul 2001 00:14:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f647EpS09361; Wed, 4 Jul 2001 00:14:51 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Wed, 4 Jul 2001 00:14:51 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Kris Kennaway Cc: des@freebsd.org, Jim Pirzyk , freebsd-current@freebsd.org Subject: Re: chgrp broken on alpha systems In-Reply-To: <20010704001222.B49299@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > There is no -Wall or -Werror in normal /usr/src builds. Try again. > > > > Sorry- let me modify that. > > > > Not normal, except by dimwits who add WARNS?= 2 w/o checking. > > This kind of language isn't called for. People make mistakes, and > insulting them for it serves no useful purpose. yah, yah, yah, yah, yah..... it's just the same old same old refrain of "beast is broken" or "oh well", etc. etc. etc.... but yer right, insulting does no good. I beg too much hard cider at dinner. It makes the veins in the forehead swell and makes one impatient. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0:54: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.xs4all.nl (smtp6.xs4all.nl [194.109.6.48]) by hub.freebsd.org (Postfix) with ESMTP id 706C337B406 for ; Wed, 4 Jul 2001 00:54:04 -0700 (PDT) (envelope-from wkb@xs4all.nl) Received: from webmail4.xs4all.nl (webmail4.xs4all.nl [194.109.127.38]) by smtp6.xs4all.nl (8.9.3/8.9.3) with ESMTP id JAA10820; Wed, 4 Jul 2001 09:53:56 +0200 (CEST) Received: (from nobody@localhost) by webmail4.xs4all.nl (8.11.1/8.11.1) id f647soW23134; Wed, 4 Jul 2001 09:54:50 +0200 (CEST) (envelope-from wkb@xs4all.nl) X-Authentication-Warning: webmail4.xs4all.nl: nobody set sender to wkb@xs4all.nl using -f Received: from 161.114.88.71 (SquirrelMail authenticated user wkb) by webmail.xs4all.nl with HTTP; Wed, 4 Jul 2001 09:54:50 +0200 (CEST) Message-ID: <9215.161.114.88.71.994233290.squirrel@webmail.xs4all.nl> Date: Wed, 4 Jul 2001 09:54:50 +0200 (CEST) Subject: Re: chgrp broken on alpha systems From: "Wilko Bulte" To: In-Reply-To: References: Cc: , , , X-Mailer: SquirrelMail (version 1.1.3 [cvs]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gentlemen, Please? I will happily supply you with ample quantities of quality Dutch mud to sling at one another. But please do so in private? tnx Wilko > Matthew Jacob writes: >> There is, in my mailbox, a grotesque and unforgiveable insult from you >> from some months back. You deserve no respect whatsoever. > > Heh. You're so cute. > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 0:56:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id 45E4137B403 for ; Wed, 4 Jul 2001 00:56:22 -0700 (PDT) (envelope-from gh@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 1012) id D05D762D0A; Wed, 4 Jul 2001 02:56:21 -0500 (CDT) Date: Wed, 4 Jul 2001 02:56:21 -0500 From: GH To: Wilko Bulte Cc: des@ofug.org, mjacob@feral.com, freebsd-current@FreeBSD.ORG Subject: Re: chgrp broken on alpha systems Message-ID: <20010704025621.F69839@over-yonder.net> References: <9215.161.114.88.71.994233290.squirrel@webmail.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <9215.161.114.88.71.994233290.squirrel@webmail.xs4all.nl>; from wkb@freebie.xs4all.nl on Wed, Jul 04, 2001 at 09:54:50AM +0200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 04, 2001 at 09:54:50AM +0200, some SMTP stream spewed forth: > Gentlemen, > > Please? I will happily supply you with ample quantities of quality > Dutch mud to sling at one another. But please do so in private? But think of the money we'll save on wrestling tickets. gh > > tnx > Wilko > > > Matthew Jacob writes: > >> There is, in my mailbox, a grotesque and unforgiveable insult from you > >> from some months back. You deserve no respect whatsoever. > > > > Heh. You're so cute. > > > > DES > > -- > > Dag-Erling Smorgrav - des@ofug.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > -- > | / o / / _ Arnhem, The Netherlands email: > wilko@FreeBSD.org > |/|/ / / /( (_) Bulte > http://www.FreeBSD.org > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 1:17:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id 3B84537B405 for ; Wed, 4 Jul 2001 01:17:42 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f648J3A73072; Wed, 4 Jul 2001 09:19:03 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.4/8.11.4) id f648IBE51086; Wed, 4 Jul 2001 09:18:11 +0100 (BST) (envelope-from mark) Date: Wed, 4 Jul 2001 09:18:11 +0100 (BST) From: Mark Valentine Message-Id: <200107040818.f648IBE51086@dotar-sojat.thuvia.org> In-Reply-To: "Steven G. Kargl"'s message of Jul 4, 7:11am X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: kargl@troutmask.apl.washington.edu ("Steven G. Kargl"), freebsd-current@freebsd.org Subject: Re: diskcheckd goes nuts on /dev/cd0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: kargl@troutmask.apl.washington.edu ("Steven G. Kargl") > Date: Wed 4 Jul, 2001 > Subject: diskcheckd goes nuts on /dev/cd0 > However, it seems that default > settings in diskcheckd.conf that tell diskcheckd to check > all kern.disks in system and setting diskcheckd_enable="YES" > in /etc/defaults/rc.conf without a HEAD-UPS is somewhat > alarming. Yes, I thought this too. Isn't this likely to do damage to some types of media, for example Jaz disks which like to spin down most of the time (and which aren't cheap)? Also, it's pointless checking md devices... What about stuff like flash RAM appearing as IDE disks? > As a side question, why is diskcheckd even looking at > at /dev/cd0? From reading the man pages, one would infer > that diskcheckd is intended to check for read errors on > /dev/daYADA and /dev/adYADA and maybe /dev/fd0. Just using kern.disks by default seems unwise. Is there a way to determine which devices are fixed magnetic disks? (For SCSI? IDE? Other?) I'd suggest that until this is resolved that the default diskcheckd.conf not check anything; even just defaulting to ad0 probably isn't safe. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 9:11: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.elbayu.com (mail.elbayu.com [12.16.41.112]) by hub.freebsd.org (Postfix) with ESMTP id BAF0737B403 for ; Wed, 4 Jul 2001 09:11:06 -0700 (PDT) (envelope-from eleanor_19@hotmail.com) Received: from oemcomputer [12.21.14.148] by mail.elbayu.com (SMTPD32-6.06) id A10A12330136; Wed, 04 Jul 2001 12:06:50 -0300 Message-Id: Date: Wed, 4 Jul 2001 03:10:18 -0300 X-Priority: 3 From: "Eleanor Davis" Reply-To: eleanor_19@hotmail.com X-Mailer: Email Collector & Sender by SBZ systems To: A-L.Heim@t-online.de MIME-Version: 1.0 Subject: my pic that i told you =) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8Bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG the finest girls and models over the net http://www.erawtic.org/ FOR FREE!!! give them a look.. what can lose? i dont have much to say.. its not needed.. you will like them, beliveme att. Eleanor http://www.erawtic.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 9:48:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with SMTP id 53F8337B406 for ; Wed, 4 Jul 2001 09:48:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 72916 invoked from network); 4 Jul 2001 16:48:05 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Jul 2001 16:48:05 -0000 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: <993971070.1729.0.camel@percible.alfred.cx> Date: Wed, 04 Jul 2001 09:48:02 -0700 (PDT) From: John Baldwin To: Andrew Reid Subject: Re: wierd build error with -current Cc: current@FreeBSD.ORG, mjacob@feral.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 01-Jul-01 Andrew Reid wrote: > On 30 Jun 2001 21:59:19 -0700, Matthew Jacob wrote: > >> I'm sure you're right. I guess I need to go fix the breakage. >> >> It's supposed to work. Things get built in /usr/obj, not /usr/src. > > Hrm, OK. That's something I didn't know. I'm assuming that you've tried > mounting /usr/src as read-write and tried compiling again? > > - andrew That's just hacking around the bug. It's a _problem_ for buildworld to write to /usr/src. It's not supposed to do that, period. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 9:48:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with SMTP id 3F41237B407 for ; Wed, 4 Jul 2001 09:48:07 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 25771 invoked from network); 4 Jul 2001 16:48:06 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Jul 2001 16:48:06 -0000 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: Wed, 04 Jul 2001 09:48:04 -0700 (PDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: blockable sleep lock panic (and dumps still don't work) Cc: current@FreeBSD.ORG, Bruce Evans , Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Jul-01 Dag-Erling Smorgrav wrote: > Kazutaka YOKOTA writes: >> I discussed this with jhb. We even had a test patch. Jhb told me >> that someone else was working on providing proper locking in >> kernel printf(). > > Poul-Henning, I think - I remember discussing it with him on IRC. No, Chuck Paterson has it done, provided I can wrangle the patch from him. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 9:48:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with SMTP id AC9A837B409 for ; Wed, 4 Jul 2001 09:48:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 25785 invoked from network); 4 Jul 2001 16:48:08 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Jul 2001 16:48:08 -0000 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: Wed, 04 Jul 2001 09:48:05 -0700 (PDT) From: John Baldwin To: Julian Elischer Subject: RE: RFC: Kernel thread system nomenclature. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Jul-01 Julian Elischer wrote: > > The time has come (now that we have a design) to assign names to the > various entities that will be created when we implement the > (current name) KSE code. I'm not sure the current names are all that bad. Hopefully one is going to be doing some reading before diving and modifying this stuff. Here are some suggestions anyways. > Suggested names: proc, task (others?) This should stay 'proc' as it is still the actual process (it holds the pid, etc.) Every reference I've seen to kernels with threads still calls this a process. > Suggested names: schedblock (SB), > Kernel Schedulabale Entity Group (KSEG), > KSE (confusing but acurate), > SchedEntry, (SE?), > Process Schduling control block (pscb) threadgroup (threadgrp), we already have process groups for a set of related processes. > Suggested names: Kernel Schedulable Entity(KSE), > thread container(TC), > Scheduler Virtual processor(SVP), > Scheduler Slot(schedslot, ss?) > Thread processor (tp?) virtcpu > Suggested names: Thread Context Block (TCB) > Kernel Schedulabel Entity Context (KSEC) > Thread Context (TCTX) thread This makes the most sense, and allows curproc to become curthread. This should most definitely _not_ be proc. Get it conceptually right rather than minimize diffs. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 10: 1:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 66D1B37B403 for ; Wed, 4 Jul 2001 10:01:38 -0700 (PDT) (envelope-from ben@FreeBSD.org) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15HnlT-0000bX-00; Wed, 04 Jul 2001 15:36:27 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.4/8.11.4) id f64EaQr07012; Wed, 4 Jul 2001 15:36:26 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Wed, 4 Jul 2001 15:36:25 +0100 From: Ben Smithurst To: "Steven G. Kargl" Cc: freebsd-current@freebsd.org Subject: Re: diskcheckd goes nuts on /dev/cd0 Message-ID: <20010704153625.A97328@strontium.shef.vinosystems.com> References: <200107040700.f64705m08269@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107040700.f64705m08269@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Steven G. Kargl wrote: > I updated a pre june 13th current to a july 3 current. > Ran mergemaster and installed /etc/diskcheckd.conf > without modification. Upon reboot I saw 1000s of the > following message streaming up the console: > > dscheck(cd0): bio_bcount 512 is not on a sector boundary (ssize 2048) > > Checking /var/log/messages I find (note date and machine name removed): > > diskcheckd[213]: /dev/cd0 has 2048 byte sectors, may cause minor problems > /boot/kernel/kernel: dscheck(cd0): bio_bcount 512 is not on a sector boun > dary (ssize 2048) > last message repeated 3 times > diskcheckd[213]: error reading 512 bytes from sector 0 on /dev/cd0 I was gonna commit a fix for this, but after reporting the problem DES never tested the patch I supplied. :-( I'll commit it later hopefully; se@ did test it and it worked for him... > As a side question, why is diskcheckd even looking at at /dev/cd0? Because my only current system when I was writing diskcheckd didn't have a CD drive so I didn't think to tell it not to check them. Sorry... I'll commit a patch soon that allows you to specify drives to exclude, and the default config file will exclude cd*, acd*, and md*. Also, you shouldn't get these errors soon even if diskcheckd did try to check the CD drive, because it will no longer read in 512 byte blocks. -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 10:46:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 64A3A37B401; Wed, 4 Jul 2001 10:46:34 -0700 (PDT) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f64HkYk14178; Wed, 4 Jul 2001 10:46:34 -0700 (PDT) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200107041746.f64HkYk14178@troutmask.apl.washington.edu> Subject: Re: diskcheckd goes nuts on /dev/cd0 In-Reply-To: <20010704153625.A97328@strontium.shef.vinosystems.com> "from Ben Smithurst at Jul 4, 2001 03:36:25 pm" To: Ben Smithurst Date: Wed, 4 Jul 2001 10:46:34 -0700 (PDT) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ben Smithurst said: > Steven G. Kargl wrote: > > > last message repeated 3 times > > diskcheckd[213]: error reading 512 bytes from sector 0 on /dev/cd0 > > I was gonna commit a fix for this, but after reporting the problem DES > never tested the patch I supplied. :-( > > I'll commit it later hopefully; se@ did test it and it worked for him... Ah, okay. I checked GNATS and freebsd-current mailing list archive, but I could not locate any relevant PR's or posts. > > > As a side question, why is diskcheckd even looking at at /dev/cd0? > > Because my only current system when I was writing diskcheckd didn't have > a CD drive so I didn't think to tell it not to check them. Sorry... > > I'll commit a patch soon that allows you to specify drives to exclude, > and the default config file will exclude cd*, acd*, and md*. > Do you need to special case tape drives, floppies, zip, etc? If so, you might want to exclude all devices except those that start with da and ad. -- Steve http://troutmask.apl.washington.edu/~kargl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11: 1:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by hub.freebsd.org (Postfix) with ESMTP id EEF1337B401; Wed, 4 Jul 2001 11:01:50 -0700 (PDT) (envelope-from Antoine.Beaupre@ericsson.ca) Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id f64I1np17273; Wed, 4 Jul 2001 13:01:49 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id f64I1mL29581; Wed, 4 Jul 2001 13:01:48 -0500 (CDT) Received: from lmc35.lmc.ericsson.se (lmc35.lmc.ericsson.se [142.133.16.175]) by noah.lmc.ericsson.se (8.11.2/8.9.2) with ESMTP id f64I1gG07971; Wed, 4 Jul 2001 14:01:47 -0400 (EDT) Received: by lmc35.lmc.ericsson.se with Internet Mail Service (5.5.2653.19) id <32AT248N>; Wed, 4 Jul 2001 14:01:41 -0400 Received: from lmc.ericsson.se (lmcpc100455.pc.lmc.ericsson.se [142.133.23.150]) by LMC37.lmc.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 32AX8YD0; Wed, 4 Jul 2001 14:01:35 -0400 From: "Antoine Beaupre (LMC)" To: "Steven G. Kargl" Cc: Ben Smithurst , freebsd-current@FreeBSD.ORG Message-ID: <3B4359FC.8050803@lmc.ericsson.se> Date: Wed, 04 Jul 2001 14:01:32 -0400 Organization: LMC, Ericsson Research Canada User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en,fr-CA,fr MIME-Version: 1.0 Subject: Re: diskcheckd goes nuts on /dev/cd0 References: <200107041746.f64HkYk14178@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Steven G. Kargl wrote: > Ben Smithurst said: > >>Steven G. Kargl wrote: >>>As a side question, why is diskcheckd even looking at at /dev/cd0? >>> >>Because my only current system when I was writing diskcheckd didn't have >>a CD drive so I didn't think to tell it not to check them. Sorry... >> >>I'll commit a patch soon that allows you to specify drives to exclude, >>and the default config file will exclude cd*, acd*, and md*. > > Do you need to special case tape drives, floppies, zip, etc? If so, > you might want to exclude all devices except those that start with > da and ad. Actually, I think that it should exclude all devices except those specified in the config file... As in "check only requested disks"... My 2 cents. A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:antoine.beaupre@ericsson.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11:12:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 057D937B401 for ; Wed, 4 Jul 2001 11:12:13 -0700 (PDT) (envelope-from ben@FreeBSD.org) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15Hr8A-000D3e-00; Wed, 04 Jul 2001 19:12:06 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.4/8.11.4) id f64IC5X64860; Wed, 4 Jul 2001 19:12:05 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Wed, 4 Jul 2001 19:12:05 +0100 From: Ben Smithurst To: "Steven G. Kargl" Cc: freebsd-current@FreeBSD.org Subject: Re: diskcheckd goes nuts on /dev/cd0 Message-ID: <20010704191205.B97328@strontium.shef.vinosystems.com> References: <20010704153625.A97328@strontium.shef.vinosystems.com> <200107041746.f64HkYk14178@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107041746.f64HkYk14178@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Steven G. Kargl wrote: > Do you need to special case tape drives, floppies, zip, etc? If so, > you might want to exclude all devices except those that start with > da and ad. floppies, no: ben@ref5:~$ grep fd0 /var/run/dmesg.boot fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ben@ref5:~$ sysctl kern.disks kern.disks: ad0 i.e. floppies aren't included in kern.disks. Not sure about zip disks, and if tapes are included in kern.disks there's something very broken going on. ;-) -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11:17:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id DF38037B403 for ; Wed, 4 Jul 2001 11:17:42 -0700 (PDT) (envelope-from ben@FreeBSD.org) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15HrDZ-000Flu-00; Wed, 04 Jul 2001 19:17:41 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.4/8.11.4) id f64IHfe72131; Wed, 4 Jul 2001 19:17:41 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Wed, 4 Jul 2001 19:17:40 +0100 From: Ben Smithurst To: "Antoine Beaupre (LMC)" Cc: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: diskcheckd goes nuts on /dev/cd0 Message-ID: <20010704191740.C97328@strontium.shef.vinosystems.com> References: <200107041746.f64HkYk14178@troutmask.apl.washington.edu> <3B4359FC.8050803@lmc.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4359FC.8050803@lmc.ericsson.se> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Antoine Beaupre (LMC) wrote: > Actually, I think that it should exclude all devices except those > > specified in the config file... As in "check only requested disks"... It's perfectly possible to do just that... phk wanted it to check all disks by default when I was writing it though, but this seems to be causing problems for people. :-( I think excluding CDs and MDs should solve most of the problems that have been reported, I'm not sure what the situation with zip/jaz type things is though. Are they included in kern.disks? Anyone? -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11:47:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by hub.freebsd.org (Postfix) with ESMTP id 0BD4137B407; Wed, 4 Jul 2001 11:47:14 -0700 (PDT) (envelope-from Antoine.Beaupre@ericsson.ca) Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id f64IlDp02964; Wed, 4 Jul 2001 13:47:13 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr5.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id f64IlCT24720; Wed, 4 Jul 2001 13:47:12 -0500 (CDT) Received: from lmc35.lmc.ericsson.se (lmc35.lmc.ericsson.se [142.133.16.175]) by noah.lmc.ericsson.se (8.11.2/8.9.2) with ESMTP id f64IlBG10103; Wed, 4 Jul 2001 14:47:11 -0400 (EDT) Received: by lmc35.lmc.ericsson.se with Internet Mail Service (5.5.2653.19) id <32AT2VH0>; Wed, 4 Jul 2001 14:47:10 -0400 Received: from lmc.ericsson.se (lmcpc100455.pc.lmc.ericsson.se [142.133.23.150]) by LMC37.lmc.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 32AX8YZ5; Wed, 4 Jul 2001 14:47:06 -0400 From: "Antoine Beaupre (LMC)" To: Ben Smithurst Cc: "Antoine Beaupre (LMC)" , "Steven G. Kargl" , freebsd-current@FreeBSD.org Message-ID: <3B4364A6.8070609@lmc.ericsson.se> Date: Wed, 04 Jul 2001 14:47:02 -0400 Organization: LMC, Ericsson Research Canada User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en,fr-CA,fr MIME-Version: 1.0 Subject: Re: diskcheckd goes nuts on /dev/cd0 References: <200107041746.f64HkYk14178@troutmask.apl.washington.edu> <3B4359FC.8050803@lmc.ericsson.se> <20010704191740.C97328@strontium.shef.vinosystems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ben Smithurst wrote: > Antoine Beaupre (LMC) wrote: > > >>Actually, I think that it should exclude all devices except those >>specified in the config file... As in "check only requested disks"... > > It's perfectly possible to do just that... good to hear that. > phk wanted it to check all > disks by default when I was writing it though, but this seems to be > causing problems for people. :-( Well, not only for people but mostly for hardware. ;) > I think excluding CDs and MDs should solve most of the problems that > have been reported, I think someone already raised the point about memory chips that "look like" IDE disks. These chips have limited r/w lifespan, and should be spared from diskcheck... So that's another problem. > I'm not sure what the situation with zip/jaz type > things is though. Are they included in kern.disks? Anyone? No idea. I could take a look at home when I buy my next power supply. ;) A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:antoine.beaupre@ericsson.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11:54:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id 4949137B405 for ; Wed, 4 Jul 2001 11:54:15 -0700 (PDT) (envelope-from Tomi.Vainio@Sun.COM) Received: from helsinki.Finland.Sun.COM ([129.159.101.19]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA18512 for ; Wed, 4 Jul 2001 12:54:12 -0600 (MDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by helsinki.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v2.1p1) with ESMTP id VAA05164 for ; Wed, 4 Jul 2001 21:54:11 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.10.2+Sun/8.10.2) id f64IsAu05512; Wed, 4 Jul 2001 21:54:10 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15171.26193.676993.450713@gargle.gargle.HOWL> Date: Wed, 4 Jul 2001 21:54:09 +0300 To: freebsd-current@freebsd.org Subject: Nokia C110 WLAN X-Mailer: VM 6.92 under 21.4 (patch 3) "Academic Rigor" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, This card should be a prism2 clone and it works with Linux prism2 driver. I have tried to get this work with current but no luck yet. Jul 4 21:48:35 phb pccardd[174]: Card "Nokia"("C110/C111 Wireless LAN Card") [(null)] [(null)] matched "Nokia" ("C110/C111 Wireless LAN Card") [(null)] [(null)] Jul 4 21:48:40 phb /boot/kernel/kernel: wi0: No I/O space?! Jul 4 21:48:40 phb pccardd[174]: driver allocation failed for Nokia(C110/C111 Wireless LAN Card): Device not configured card "Nokia" "C110/C111 Wireless LAN Card" config 0x1 "wi" ? 0x10000 insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I already tried auto and without 0x10000 Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x1c (Other conditions for common memory), length = 4 000: 02 00 00 ff (3V card) Tuple #3, code = 0x15 (Version 1 info), length = 37 000: 07 00 4e 6f 6b 69 61 00 43 31 31 30 2f 43 31 31 010: 31 20 57 69 72 65 6c 65 73 73 20 4c 41 4e 20 43 020: 61 72 64 00 ff Version = 7.0, Manuf = [Nokia], card vers = [C110/C111 Wireless LAN Card] Tuple #4, code = 0x20 (Manufacturer ID), length = 4 000: 24 01 10 11 PCMCIA ID = 0x124, OEM ID = 0x1110 Tuple #5, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #6, code = 0x22 (Functional EXT), length = 2 000: 01 07 Network technology: Wireless Tuple #7, code = 0x22 (Functional EXT), length = 5 000: 02 c0 d8 a7 00 Network speed: 11 Mb/sec Tuple #8, code = 0x22 (Functional EXT), length = 2 000: 03 07 Network media: 2.4 GHz Tuple #9, code = 0x1a (Configuration map), length = 4 000: 00 02 f4 01 Reg len = 1, config register addr = 0xf4, last config = 0x2 Registers: X------- Tuple #10, code = 0x1b (Configuration entry), length = 19 000: c1 01 1d 79 55 a6 1e a6 1e b6 14 24 e5 13 5f 64 010: 30 ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2 x 100mA, ext = 0x1e Max current average over 1 second: 2 x 100mA, ext = 0x1e Max current average over 10 ms: 3 x 100mA, ext = 0x14 Power down supply current: 2 x 1mA Wait scale Speed = 1.2 x 1 us, scaled by 10 RDY/BSY scale Speed = 5.0 x 10 ms, scaled by 10 Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #11, code = 0x1b (Configuration entry), length = 10 000: 02 01 79 b5 1e 36 36 b6 46 24 Config index = 0x2 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Continuous supply current: 3 x 100mA Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 3 x 100mA, ext = 0x46 Power down supply current: 2 x 1mA Tuple #12, code = 0x14 (No link), length = 0 Tuple #13, code = 0xff (Terminator), length = 0 -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 11:57:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 7A92A37B403 for ; Wed, 4 Jul 2001 11:57:10 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (goose.mail.pas.earthlink.net [207.217.120.18]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA06370; Wed, 4 Jul 2001 11:57:06 -0700 (PDT) Message-ID: <3B436725.748C71DD@mindspring.com> Date: Wed, 04 Jul 2001 11:57:41 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: Still weird psm behaviour in -CURRENT References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > but interestingly, > when I then rebooted with the previous kernel, the trackpoint worked. > Both kernels were identical except for the hints, which I compile > statically. No fiddling with the BIOS or anything. I'm now using the > exact same kernel that didn't work before, with the exact same hints, > on the exact same hardware, and I get the exact same PnP "can't assign > resources" messages as before, but the trackpoint works. Cold boot or warm boot? FreeBSD's keyboard probes are really obnoxious; on PC-class hardware, it should leave the damn things where the BIOS puts them. FreeBSD has problems with a number of Belkin switches, and while the newer firmware (1.9) works on the smaller switches when FreeBSD is not actively selected, the bigger ones still puke FreeBSD out and make it lose the keyboard and mouse, and the remote ones really don't work at all. No problem with NT, Linux, Windows, etc. (of course). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 13:57:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id 27A7F37B403; Wed, 4 Jul 2001 13:57:11 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f64KwBE02507; Wed, 4 Jul 2001 21:58:11 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.4/8.11.4) id f64Kvc379721; Wed, 4 Jul 2001 21:57:38 +0100 (BST) (envelope-from mark) Date: Wed, 4 Jul 2001 21:57:38 +0100 (BST) From: Mark Valentine Message-Id: <200107042057.f64Kvc379721@dotar-sojat.thuvia.org> In-Reply-To: Ben Smithurst's message of Jul 4, 6:20pm X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: ben@freebsd.org (Ben Smithurst), "Antoine Beaupre (LMC)" Subject: Re: diskcheckd goes nuts on /dev/cd0 Cc: "Steven G. Kargl" , freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: ben@freebsd.org (Ben Smithurst) > Date: Wed 4 Jul, 2001 > Subject: Re: diskcheckd goes nuts on /dev/cd0 > I think excluding CDs and MDs should solve most of the problems that > have been reported, I'm not sure what the situation with zip/jaz type > things is though. Are they included in kern.disks? Anyone? kern.disks: md0 da2 da1 da0 cd1 cd0 ad0 ad0: 73308MB [148945/16/63] at ata0-master UDMA33 da0: Fixed Direct Access SCSI-3 device da1: Fixed Direct Access SCSI-3 device cd1: Removable CD-ROM SCSI-2 device cd0: Removable CD-ROM SCSI-2 device da2: Removable Direct Access SCSI-2 device da2 should not be checked. ad0 is okay, it's not a flash device... It's still unsafe to clean ad* or da* in the default disckcheckd.conf. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 4 15: 9:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id D08CE37B401 for ; Wed, 4 Jul 2001 15:08:49 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.4/8.11.4) id f64M8mp14089 for current@freebsd.org; Wed, 4 Jul 2001 15:08:48 -0700 (PDT) Date: Wed, 4 Jul 2001 15:08:48 -0700 (PDT) From: David Wolfskill Message-Id: <200107042208.f64M8mp14089@bunrab.catwhisker.org> To: current@freebsd.org Subject: Interruptable hang starting init in today's -CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, maybe it's not in starting init per se; I see the usual log messages (I'll quote what gets logged from a "boot-v" below) up to: start_init: trying /sbin/init DEPENDENCY NOTE: portmap will be enabled to support NFS Entropy harvesting: interrupts ethernet point_to_point Leaving the system alone, it will apparently sit there (staying fairly busy, based on the speed of the fan -- this is my laptop) indefinitely. Ctl+Alt+Esc drops into debugger, where I see (hand-copied): Debugger("manual escape to debugger") Stopped at Debugger+0x44 pushl %ebx db> trace Debugger(c0391069) at Debugger+0x44 scgetc(c042e240,2,c169fdc0,c04271e0,4) at scgetc+0x41e sckbdevent(c04271e0,0,c042e240,c169fdc0,c169ee00) at sckbdevent+0x1c5 atkbd_intr(c04271e0,0,ccdd1f7c,c01d3563,c04271e0) at atkbd_intr+0x22 atkbd_isa_intr(c04271e0) at atkbd_isa_intr+0x18 ithread_loop(c169ee00,ccdd1fa8) at ithread_loop+0x2bf fork_exit(c01d32a4,c169ee00,ccdd1fa8) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 db> show locks exclusive (sleep mutex) Giant (0xc043ef40) locked @ /usr/src/sys/kern/kern_intr.c:519 I do have some experimental code, but that's been unchanged for the past week or so, and affects the an (Aironet) driver mostly; I was able to recreate the symptoms when I power-cycled the machine with neither the CD-ROM nor the Aironet card connected in any way. And interrupting the boot sequence to unload the kernel & load yesterday's -CURRENT kernel (/boot/kernel.old/kernel) worked like a charm -- no hangs. Here's my recent CVSup history: CVSup begin from cvsup14.freebsd.org at Sun Jul 1 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sun Jul 1 03:52:23 PDT 2001 CVSup begin from cvsup14.freebsd.org at Mon Jul 2 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Mon Jul 2 03:52:46 PDT 2001 CVSup begin from cvsup14.freebsd.org at Tue Jul 3 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Tue Jul 3 03:52:47 PDT 2001 CVSup begin from cvsup14.freebsd.org at Wed Jul 4 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Wed Jul 4 03:53:33 PDT 2001 I have a local CVS repository, so I have some flexibility here. (I also run & track -STABLE on the same machine. I got today's -STABLE built & running before attacking -CURRENT, as usual. The "trackinig" is for both -STABLE & -CURRENT, and is daily.) Here's what got logged to /var/run/dmesg.boot from that most recent boot (which was verbose, and I interrupted it with the debugger stuff shown above): Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #59: Wed Jul 4 13:02:32 PDT 2001 root@dhcp-140.catwhisker.org:/common/C/obj/usr/src/sys/LAPTOP_30W Calibrating clock(s) ... TSC clock: 746316090 Hz, i8254 clock: 1193151 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Pentium III Xeon/Celeron (746.34-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 268369920 (262080K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x004e7000 - 0x0ffe7fff, 263196672 bytes (64257 pages) avail memory = 256208896 (250204K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7210 bios32: Entry = 0xfd890 (c00fd890) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd890+0x11e pnpbios: Found PnP BIOS data at 0xc00f7240 pnpbios: Entry = f0000:a600 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc04c1000. null: random: mem: Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base e0000000, size 26, enabled found-> vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 found-> vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 map[10]: type 1, range 32, base 44000000, size 12, enabled found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=0, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 44001000, size 12, enabled found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=0, slot=4, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base 00001050, size 4, enabled found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 map[20]: type 4, range 32, base 00001060, size 5, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=7 map[90]: type 4, range 32, base 00001040, size 4, enabled found-> vendor=0x8086, dev=0x7113, revid=0x03 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 map[10]: type 4, range 32, base 00001400, size 8, enabled found-> vendor=0x125d, dev=0x1978, revid=0x10 bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 intpin=a, irq=7 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base f4000000, size 8, enabled map[14]: type 4, range 32, base 00001080, size 3, enabled map[18]: type 4, range 32, base 00001800, size 8, enabled found-> vendor=0x11c1, dev=0x0450, revid=0x00 bus=0, slot=16, func=0 class=07-80-00, hdrtype=0x00, mfdev=0 intpin=a, irq=7 powerspec 2 supports D0 D3 current D0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x2000-0x2fff pcib1: memory decode 0xf4100000-0xf41fffff pcib1: prefetched decode 0xf8000000-0xfbffffff pci1: physical bus=1 map[10]: type 3, range 32, base f8000000, size 26, enabled map[14]: type 4, range 32, base 00002000, size 8, enabled map[18]: type 1, range 32, base f4100000, size 14, enabled found-> vendor=0x1002, dev=0x4c46, revid=0x02 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: on pcib1 pci1: at 0.0 (no driver attached) pci_cfgintr_unique: hard-routed to irq 11 pci_cfgintr: 0:4 INTA routed to irq 11 pcic0: mem 0x44000000-0x44000fff irq 11 at device 4.0 on pci0 pcic0: Memory mapped device, will work. pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][pci only] pccard0: on pcic0 stat is 0 pci_cfgintr_unique: hard-routed to irq 11 pci_cfgintr: 0:4 INTA routed to irq 11 pcic1: mem 0x44001000-0x44001fff irq 11 at device 4.1 on pci0 pcic1: Memory mapped device, will work. pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][pci only] pccard1: on pcic1 stat is 6d PCI-ISA bridge with incorrect subclass 0x80 PCI-ISA bridge with incorrect subclass 0x80 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1050-0x105f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1050 ata0: mask=03 ostat0=50 ostat2=00 ata0-slave: ATAPI probe 00 00 ata0-master: ATAPI probe 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA probe 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1058 ata1: mask=02 ostat0=a5 ostat2=00 ata1-master: ATAPI probe 7f 7f ata1-slave: ATAPI probe 14 eb ata1: mask=02 stat0=00 stat1=00 ata1: devices=08 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1060-0x107f irq 7 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) pcm0: port 0x1400-0x14ff irq 7 at device 8.0 on pci0 setmap (56a000, 4000), nseg=1, error=0 pcm0: Maestro DMA base: 0x56a000 pcm0: ac97 codec id 0x83847609 (SigmaTel STAC9721/9723) pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: ac97 primary codec extended features AMAP setmap (572000, 4000), nseg=1, error=0 pcm0: pch[0].offset = 0x8000 setmap (581000, 4000), nseg=1, error=0 pcm0: pch[1].offset = 0x17000 setmap (589000, 4000), nseg=1, error=0 pcm0: pch[2].offset = 0x1f000 setmap (591000, 4000), nseg=1, error=0 pcm0: pch[3].offset = 0x27000 pci0: at 16.0 (no driver attached) ata-: ata0 already exists, using ata2 instead ata-: ata1 already exists, using ata3 instead pcic-: pcic0 already exists, using pcic2 instead pcic-: pcic1 already exists, using pcic3 instead pcm-: pcm0 already exists, using pcm1 instead 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 pnpbios: 16 devices, largest 170 bytes PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 PNP0c02: adding fixed memory32 range 0xfff80000-0xffffffff, size=0x80000 PNP0c02: end config pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xe4000-0xfffff, size=0x1c000 PNP0c01: adding fixed memory32 range 0x100000-0xfffffff, size=0xff00000 PNP0c01: end config pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: end config pnpbios: handle 2 device ID PNP0200 (0002d041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 0x4 PNP0000: end config pnpbios: handle 3 device ID PNP0000 (0000d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 0x1 PNP0100: end config pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 PNP0b00: end config pnpbios: handle 5 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 0x2 PNP0303: end config pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 PNP0c04: end config pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 8 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: end config pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0x1000-0x103f, size=0x40, align=0x1 PNP0c02: adding io range 0x1040-0x104f, size=0x10, align=0x1 PNP0c02: adding io range 0x10-0x18, size=0x9, align=0x1 PNP0c02: adding io range 0x1f-0x1f, size=0x1, align=0x1 PNP0c02: adding io range 0x24-0x25, size=0x2, align=0x1 PNP0c02: adding io range 0x28-0x29, size=0x2, align=0x1 PNP0c02: adding io range 0x2c-0x2d, size=0x2, align=0x1 PNP0c02: adding io range 0x30-0x31, size=0x2, align=0x1 PNP0c02: adding io range 0x34-0x35, size=0x2, align=0x1 PNP0c02: adding io range 0x38-0x39, size=0x2, align=0x1 PNP0c02: adding io range 0x3c-0x3d, size=0x2, align=0x1 PNP0c02: adding io range 0x50-0x52, size=0x3, align=0x1 PNP0c02: adding io range 0x72-0x77, size=0x6, align=0x1 PNP0c02: adding io range 0x90-0x9f, size=0x10, align=0x1 PNP0c02: adding io range 0xa4-0xa5, size=0x2, align=0x1 PNP0c02: adding io range 0xa8-0xa9, size=0x2, align=0x1 PNP0c02: adding io range 0xac-0xad, size=0x2, align=0x1 PNP0c02: adding io range 0xb0-0xbd, size=0xe, align=0x1 PNP0c02: end config pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0c02: skipping empty range PNP0c02: end config pnpbios: handle 12 device ID PNP0c02 (020cd041) PNP0c02: adding fixed memory32 range 0xcf000-0xcffff, size=0x1000 PNP0c02: end config pnpbios: handle 13 device ID PNP0c02 (020cd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x1 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 15 device ID PNP0501 (0105d041) PNP0f13: end config pnpbios: handle 17 device ID PNP0f13 (130fd041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x1 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 20 device ID PNP0700 (0007d041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0:
Hi
 
when upgrading a machine from FreeBSD = 4.1 to=20 -current I encountered some problems and I could only solve the first=20 one:
 
1. defines HALT, PDWN, PASTE were = missing in kbio.h=20 (defined them)
 
2. when linking miniperl in stage 3 the = function=20 'setproctitle' was missing
 
3. eelf_i386.o: undefined reference to = 'basename'=20 in /usr/src/gnu/usr.bin/binutils/ld
 
How can I overcome the problems? (cvsup = ran just=20 before and updated all to the current stage, /usr/obj was = cleaned)
 
Any advice are welcome.
 
Eckhard
------=_NextPart_000_000E_01C10783.5E5985C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 7 23:21:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4157E37B406; Sat, 7 Jul 2001 23:21:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f686LXg11910; Sun, 8 Jul 2001 00:21:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f686LXJ76403; Sun, 8 Jul 2001 00:21:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107080621.f686LXJ76403@harmony.village.org> To: Mike Smith Subject: Re: Problems with ata probing twice. Cc: Makoto MATSUSHITA , sos@freebsd.dk, current@FreeBSD.ORG In-reply-to: Your message of "Sat, 07 Jul 2001 14:41:13 PDT." <200107072141.f67LfD702155@mass.dis.org> References: <200107072141.f67LfD702155@mass.dis.org> Date: Sun, 08 Jul 2001 00:21:33 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200107072141.f67LfD702155@mass.dis.org> Mike Smith writes: : > Actually, there is a reason. Ata is special like pcic is special. : > Both of them can have multiple interrupt routing methods. When ata is : > connected directly to the south bridge, it can route ISA interrupts, : > even though it is a pci device. In this case, it is unsafe to share : > interrupts between the ata device and anything else. Even though it : > looks like a pci device, the interrupt routing is ISA. : : This just reinforces what I said; shareability has nothing to do with the : driver, and everything to do with where the interrupts come *from*. Right. : > Cardbus bridges in laptops have the same problems. And it is looking : > like we can't just use the pcibios to route the interrupts on some : > older machines so we have to have some way to say "use isa interrupts : > for this device." That's a big pain for cardbus bridges because many : > of them would really like to be pci devices so you can relocate memory : > out of the ISA hole, etc. : : There's no reason they can't be PCI devices, but using interrupts from : ISA. No reason except that the current pci code always will try to route pci interrupts and never acts as a simple pass through. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message