From owner-freebsd-current Sun Sep 30 1:11:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from ms3.hinet.net (ms3.hinet.net [168.95.4.30]) by hub.freebsd.org (Postfix) with ESMTP id 76BDC37B415; Sun, 30 Sep 2001 01:11:01 -0700 (PDT) Received: from localhost (61-216-109-39.HINET-IP.hinet.net [61.216.109.39]) by ms3.hinet.net (8.8.8/8.8.8) with SMTP id QAA15725; Sun, 30 Sep 2001 16:08:48 +0800 (CST) Date: Sun, 30 Sep 2001 16:08:48 +0800 (CST) From: vadwgrhunb@ms12.hinet.net Message-Id: <200109300808.QAA15725@ms3.hinet.net> To: able@freebsd.org Subject: uvcx 立即幫您網路開店營業!! lxlu MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Novasoft_Sagittarius_Professional_" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Novasoft Sagittarius Professional 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 is a multi-part message in MIME format. ------=_Novasoft_Sagittarius_Professional_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 7bit dnjymxjjocxnu 立即幫您網路開店營業做生意!!
 


立即幫您網路開店營業做生意!!

2小時快速網頁製作及修改!!

        網頁製作超低價只要NT800元. 免費網址!!

網站內容可分:
公司簡介. 產品介紹. 產品相片. 客戶留言板. 定購表單. 彩色動畫等等
有意者歡迎洽談!!

         本處提供商家實例作品展示: 請來mail索取!!  完成網頁製作. 立即知會您的免費網址. 如 http://98.to/您的命名(中英及數字皆可)

　網頁製作或修改留言

聯絡姓名

聯絡電話
公司名稱

電子信箱

預估網頁數量 5頁以下 5頁-10頁 10頁以上 不知道

目前網址
無  有

感謝您的留言!!我們會儘快與您聯絡!!

kyehnbecoxqnc ------=_Novasoft_Sagittarius_Professional_ Content-Type: text/html; Content-Transfer-Encoding: quoted-printable ------=_Novasoft_Sagittarius_Professional_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 1:57:32 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 6D6DF37B40C for ; Sun, 30 Sep 2001 01:57:29 -0700 (PDT) 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 f8U8vSu62774; Sun, 30 Sep 2001 02:57:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f8U8vR794609; Sun, 30 Sep 2001 02:57:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109300857.f8U8vR794609@harmony.village.org> To: "Georg-W. Koltermann" Subject: Re: cardbus nonfunctional in -current as of 9/24 Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 28 Sep 2001 10:28:11 +0200." References: Date: Sun, 30 Sep 2001 02:57:27 -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 Try disabling acpi and let me know what's what. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 5:54:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 4D92037B411; Sun, 30 Sep 2001 05:54:25 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f8UCsPY27670; Sun, 30 Sep 2001 14:54:25 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f8UCsOc27666; Sun, 30 Sep 2001 14:54:24 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id OAA23809; Sun, 30 Sep 2001 14:54:23 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f8UCsXc20784; Sun, 30 Sep 2001 14:54:33 +0200 (CEST) (envelope-from alex) Date: Sun, 30 Sep 2001 14:54:31 +0200 From: Alexander Langer To: current@FreeBSD.org Cc: ume@FreeBSD.org, gad@FreeBSD.org Subject: lpd: Host name for your address (fe80:....%xl0) unknown Message-ID: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , current@FreeBSD.org, ume@FreeBSD.org, gad@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: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I don't think that I like this behaviour: alex@oink ~ $ ps ax | grep lpd 15328 ?? Ss 0:00.01 lpd -4 15329 ?? S 0:00.02 lpd -4 alex@oink ~ $ lpq lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown alex@oink ~ $ ifconfig -a rl0: flags=8843 mtu 1500 inet 192.168.0.19 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::250:baff:fed4:a512%rl0 prefixlen 64 scopeid 0x1 ether 00:50:ba:d4:a5:12 media: Ethernet autoselect (100baseTX) status: active lp0: flags=8810 mtu 1500 faith0: flags=8000 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 I don't know why lpd.c's chkhost() gets an INET6 socket, since it only listens on tcp4: alex@oink ~dir $ netstat -a | grep print tcp4 0 0 *.printer *.* LISTEN ccbdd3c0 stream 0 0 ccab3200 0 0 0 /var/run/printer Odd. Is a link-local address supposed to have a host name anyways? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 7:45: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id EBF9937B40D; Sun, 30 Sep 2001 07:45:04 -0700 (PDT) Received: (from root@localhost) by cheer.mahoroba.org (8.12.0/8.12.0) id f8UEiX4U068705; Sun, 30 Sep 2001 23:44:33 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:O51b8FUK921YXS2QK9/1jx4Z+KUmL/UukRANZvXDMwszySajVeglQWFS94EvcvqP@peace.mahoroba.org [IPv6:3ffe:505:2:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.0/8.12.0/av) with ESMTP/inet6 id f8UEiTPp056008; Sun, 30 Sep 2001 23:44:31 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 30 Sep 2001 23:44:28 +0900 (JST) Message-Id: <20010930.234428.102494221.ume@mahoroba.org> To: alex@big.endian.de Cc: current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown From: Hajimu UMEMOTO In-Reply-To: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> 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 X-Mailer: xcite1.38> Mew version 2.0.54 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 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 Sun, 30 Sep 2001 14:54:31 +0200 >>>>> Alexander Langer said: alex> I don't think that I like this behaviour: alex> alex@oink ~ $ ps ax | grep lpd alex> 15328 ?? Ss 0:00.01 lpd -4 alex> 15329 ?? S 0:00.02 lpd -4 alex> alex@oink ~ $ lpq alex> lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown Sorry, but I cannot see this message, here. Could you please tell me how did you do? alex> Odd. Is a link-local address supposed to have a host name anyways? No. The resolver doesn't do reverse lookup at all. So, I believe you cannot play with lpr by specifying link-local address. -- 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 Sun Sep 30 13:21:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 08B9A37B412 for ; Sun, 30 Sep 2001 13:21:48 -0700 (PDT) Received: from DougBarton.net (f1-snv-covad-rtr.corp.yahoo.com [216.145.49.18]) by mail-relay1.yahoo.com (Postfix) with ESMTP id DC6F08B5AE for ; Sun, 30 Sep 2001 13:21:45 -0700 (PDT) Message-ID: <3BB77EE4.4F7CAD2D@DougBarton.net> Date: Sun, 30 Sep 2001 13:21:56 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 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 With -current as of last night around 7pm PDT: IdlePTD 4390912 initial pcb at 320920 panicstr: bremfree: bp 0xc68bf184 not locked panic messages: --- panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 syncing disks... panic: bremfree: bp 0xc68bf184 not locked Uptime: 9h46m14s #0 dumpsys () at /usr/local/src/sys/kern/kern_shutdown.c:488 #1 0xc01cf098 in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:331 #2 0xc01cf4d5 in panic (fmt=0xc02b3fcf "bremfree: bp %p not locked") at /usr/local/src/sys/kern/kern_shutdown.c:628 #3 0xc01fd7a1 in bremfree (bp=0xc68bf184) at /usr/local/src/sys/kern/vfs_bio.c:535 #4 0xc01fedd1 in vfs_bio_awrite (bp=0xc68bf184) at /usr/local/src/sys/kern/vfs_bio.c:1528 #5 0xc01b2190 in spec_fsync (ap=0xcd9a0994) at /usr/local/src/sys/fs/specfs/spec_vnops.c:404 #6 0xc01b1d49 in spec_vnoperate (ap=0xcd9a0994) at /usr/local/src/sys/fs/specfs/spec_vnops.c:119 #7 0xc023b6f5 in ffs_sync (mp=0xc1703200, waitfor=2, cred=0xc0e3ed00, td=0xc0359f44) at vnode_if.h:441 #8 0xc0209f76 in sync (td=0xc0359f44, uap=0x0) at /usr/local/src/sys/kern/vfs_syscalls.c:626 #9 0xc01ced35 in boot (howto=256) at /usr/local/src/sys/kern/kern_shutdown.c:240 #10 0xc01cf4d5 in panic (fmt=0xc02b0f20 "blockable sleep lock (%s) %s @ %s:%d") at /usr/local/src/sys/kern/kern_shutdown.c:628 #11 0xc01e6054 in witness_lock (lock=0xc035a9a0, flags=0, file=0xc02ad8e0 "/usr/local/src/sys/kern/kern_proc.c", line=212) at /usr/local/src/sys/kern/subr_witness.c:493 #12 0xc01d3625 in _sx_slock (sx=0xc035a9a0, file=0xc02ad8e0 "/usr/local/src/sys/kern/kern_proc.c", line=212) at /usr/local/src/sys/kern/kern_sx.c:115 #13 0xc01ca5e4 in pfind (pid=353) at /usr/local/src/sys/kern/kern_proc.c:212 #14 0xc01e98a2 in selwakeup (sip=0xc179b804) at /usr/local/src/sys/kern/sys_generic.c:1292 #15 0xc01f33a3 in ptcwakeup (tp=0xc179b828, flag=1) at /usr/local/src/sys/kern/tty_pty.c:321 #16 0xc01f337a in ptsstart (tp=0xc179b828) at /usr/local/src/sys/kern/tty_pty.c:310 #17 0xc01f0958 in ttstart (tp=0xc179b828) at /usr/local/src/sys/kern/tty.c:1409 #18 0xc01f1da9 in tputchar (c=99, tp=0xc179b828) at /usr/local/src/sys/kern/tty.c:2469 #19 0xc01e291f in putchar (c=99, arg=0xcd9a0be8) at /usr/local/src/sys/kern/subr_prf.c:306 #20 0xc01e2b9e in kvprintf ( fmt=0xc02add01 "alcru: negative time of %ld usec for pid %d (%s)\n", func=0xc01e28d0 , arg=0xcd9a0be8, radix=10, ap=0xcd9a0c00 "�/��\002\020") at /usr/local/src/sys/kern/subr_prf.c:489 #21 0xc01e284c in printf ( fmt=0xc02add00 "calcru: negative time of %ld usec for pid %d (%s)\n") at /usr/local/src/sys/kern/subr_prf.c:262 #22 0xc01cdeab in calcru (p=0xcd0e7300, up=0xc189ae00, sp=0xc189ae08, ip=0x0) at /usr/local/src/sys/kern/kern_resource.c:669 #23 0xc01c041c in exit1 (td=0xcd0e7404, rv=256) at /usr/local/src/sys/kern/kern_exit.c:318 #24 0xc01bfdde in sys_exit (td=0xcd0e7404, uap=0xcd9a0d20) at /usr/local/src/sys/kern/kern_exit.c:110 #25 0xc027543f in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = -1, tf_ebp = -1077937600, tf_isp = -845542028, tf_ebx = 672297256, tf_edx = 512, tf_ecx = 672374048, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 671896240, tf_cs = 31, tf_eflags = 643, tf_esp = -1077937644, tf_ss = 47}) at /usr/local/src/sys/i386/i386/trap.c:1122 #26 0xc026953d in syscall_with_err_pushed () -- "We will not tire, we will not falter, and we will not fail." - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 16:33: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 6066137B401; Sun, 30 Sep 2001 16:33:01 -0700 (PDT) Received: by heechee.tobez.org (Postfix, from userid 1001) id B2D605411; Mon, 1 Oct 2001 01:32:54 +0200 (CEST) Date: Mon, 1 Oct 2001 01:32:54 +0200 From: Anton Berezin To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/isa psm.c atkbdc_isa.c Message-ID: <20011001013254.A698@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Kazutaka YOKOTA , current@freebsd.org References: <200109251659.f8PGxTN66726@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109251659.f8PGxTN66726@freefall.freebsd.org>; from yokota@FreeBSD.org on Tue, Sep 25, 2001 at 09:59:28AM -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 Tue, Sep 25, 2001 at 09:59:28AM -0700, Kazutaka YOKOTA wrote: > yokota 2001/09/25 09:59:28 PDT > > Modified files: > sys/isa psm.c atkbdc_isa.c > Log: > Yet another turn of workaround for psm/ACPI/PnP BIOS > problems currently experienced in -CURRENT. > > This should fix the problem that the PS/2 mouse is detected > twice if the acpi module is not loaded on some systems. > > Revision Changes Path > 1.24 +2 -2 src/sys/isa/atkbdc_isa.c > 1.40 +84 -39 src/sys/isa/psm.c Can it be that this fix is responsible for PS/2 mouse being detected zero times? :-) :-( Dmesg output is in a separate message. +Anton. -- | Anton Berezin | FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | tobez@catpipe.net (_(_|| | tobez@FreeBSD.org | | +45 7021 0050 | Private: tobez@tobez.org | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 19:20:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id F119137B409; Sun, 30 Sep 2001 19:20:39 -0700 (PDT) Received: from DougBarton.net (f1-snv-covad-rtr.corp.yahoo.com [216.145.49.18]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 096A28B5B2; Sun, 30 Sep 2001 19:20:38 -0700 (PDT) Message-ID: <3BB7D300.5DA6F311@DougBarton.net> Date: Sun, 30 Sep 2001 19:20:48 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: John Indra , freebsd-current@FreeBSD.ORG, jdp@polstra.com Subject: 4.x apps can't resolve hostnames References: <20010928152726.A765@office.naver.co.id> <20010928113859.H30062@sunbay.com> 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 Ruslan Ermilov wrote: > If this Yahoo! Messenger is the 4.x application, make sure to add > COMPAT4X=TRUE to /etc/make.conf. This will remove old libc.so.4 > from /usr/lib and install proper one into /usr/lib/compat. While this does install the appropriate libs, network apps from 4.x still can't resolve hostnames. This applies to ymessenger as mentioned above, and cvsup so far. You can get ymessenger at http://messenger.yahoo.com/messenger/download/unix.html Doug -- "We will not tire, we will not falter, and we will not fail." - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 20:28:48 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 3EA7A37B408 for ; Sun, 30 Sep 2001 20:24:44 -0700 (PDT) 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 NAA03428; Mon, 1 Oct 2001 13:24:36 +1000 Date: Mon, 1 Oct 2001 13:24:00 +1000 (EST) From: Bruce Evans X-X-Sender: To: Doug Barton Cc: Subject: Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 In-Reply-To: <3BB77EE4.4F7CAD2D@DougBarton.net> Message-ID: <20011001131719.B76679-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE 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, 30 Sep 2001, Doug Barton wrote: > =09With -current as of last night around 7pm PDT: > > > IdlePTD 4390912 > initial pcb at 320920 > panicstr: bremfree: bp 0xc68bf184 not locked > panic messages: > --- > panic: blockable sleep lock (sx) allproc @ > /usr/local/src/sys/kern/kern_proc.c:212 > > syncing disks... panic: bremfree: bp 0xc68bf184 not locked > Uptime: 9h46m14s > > ... > #10 0xc01cf4d5 in panic (fmt=3D0xc02b0f20 "blockable sleep lock (%s) %s @ > %s:%d") > at /usr/local/src/sys/kern/kern_shutdown.c:628 > #11 0xc01e6054 in witness_lock (lock=3D0xc035a9a0, flags=3D0, > file=3D0xc02ad8e0 "/usr/local/src/sys/kern/kern_proc.c", line=3D212) > at /usr/local/src/sys/kern/subr_witness.c:493 > #12 0xc01d3625 in _sx_slock (sx=3D0xc035a9a0, > file=3D0xc02ad8e0 "/usr/local/src/sys/kern/kern_proc.c", line=3D212) > at /usr/local/src/sys/kern/kern_sx.c:115 > #13 0xc01ca5e4 in pfind (pid=3D353) at > /usr/local/src/sys/kern/kern_proc.c:212 > #14 0xc01e98a2 in selwakeup (sip=3D0xc179b804) at > /usr/local/src/sys/kern/sys_generic.c:1292 > #15 0xc01f33a3 in ptcwakeup (tp=3D0xc179b828, flag=3D1) > at /usr/local/src/sys/kern/tty_pty.c:321 > #16 0xc01f337a in ptsstart (tp=3D0xc179b828) at > /usr/local/src/sys/kern/tty_pty.c:310 > #17 0xc01f0958 in ttstart (tp=3D0xc179b828) at > /usr/local/src/sys/kern/tty.c:1409 > #18 0xc01f1da9 in tputchar (c=3D99, tp=3D0xc179b828) at > /usr/local/src/sys/kern/tty.c:2469 > #19 0xc01e291f in putchar (c=3D99, arg=3D0xcd9a0be8) at > /usr/local/src/sys/kern/subr_prf.c:306 > #20 0xc01e2b9e in kvprintf ( > fmt=3D0xc02add01 "alcru: negative time of %ld usec for pid %d (%s)\n"= , > func=3D0xc01e28d0 , arg=3D0xcd9a0be8, radix=3D10, ap=3D0xcd9= a0c00 > "=DE/=CC=FF\002\020") > at /usr/local/src/sys/kern/subr_prf.c:489 > #21 0xc01e284c in printf ( > fmt=3D0xc02add00 "calcru: negative time of %ld usec for pid %d (%s)\n= ") > at /usr/local/src/sys/kern/subr_prf.c:262 > #22 0xc01cdeab in calcru (p=3D0xcd0e7300, up=3D0xc189ae00, sp=3D0xc189ae0= 8, > ip=3D0x0) > at /usr/local/src/sys/kern/kern_resource.c:669 > #23 0xc01c041c in exit1 (td=3D0xcd0e7404, rv=3D256) at > /usr/local/src/sys/kern/kern_exit.c:318 > #24 0xc01bfdde in sys_exit (td=3D0xcd0e7404, uap=3D0xcd9a0d20) > at /usr/local/src/sys/kern/kern_exit.c:110 > #25 0xc027543f in syscall (frame=3D{tf_fs =3D 47, tf_es =3D 47, tf_ds =3D= 47, > tf_edi =3D 0, > tf_esi =3D -1, tf_ebp =3D -1077937600, tf_isp =3D -845542028, tf_eb= x =3D > 672297256, > tf_edx =3D 512, tf_ecx =3D 672374048, tf_eax =3D 1, tf_trapno =3D 1= 2, tf_err > =3D 2, > tf_eip =3D 671896240, tf_cs =3D 31, tf_eflags =3D 643, tf_esp =3D > -1077937644, tf_ss =3D 47}) > at /usr/local/src/sys/i386/i386/trap.c:1122 > #26 0xc026953d in syscall_with_err_pushed () This is a well-know bug in printf(9). The TIOCCONS ioctl always gave non-deterministic crashes. Now it gives determinstic panics when pintf() is called while sched_lock is held. Work-around: don't use anything that uses TIOCCONS (xconsole?). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 21:35:37 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 09D6137B40C for ; Sun, 30 Sep 2001 21:35:30 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f914ZSH95996 for ; Sun, 30 Sep 2001 21:35:28 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 30 Sep 2001 21:35:27 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: current@freebsd.org Subject: reappearance of an old bug again? (microtime went backwards) 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 -current as of the last day or so- anyone else seen? Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041 microuptime() went backwards (939.4410978 -> 938.949317) microuptime() went backwards (1382.4391199 -> 1382.075447) microuptime() went backwards (1382.4391190 -> 1382.252820) microuptime() went backwards (1442.4313917 -> 1441.807840) microuptime() went backwards (1712.4246230 -> 1712.400756) microuptime() went backwards (1811.4370757 -> 1811.261143) microuptime() went backwards (1811.4370751 -> 1811.671929) microuptime() went backwards (1934.4016347 -> 1933.851724) microuptime() went backwards (1937.3816473 -> 1936.242822) microuptime() went backwards (1937.3816479 -> 1936.687978) microuptime() went backwards (1937.3816473 -> 1936.792461) microuptime() went backwards (1937.3816473 -> 1937.011415) microuptime() went backwards (1960.4337552 -> 1959.992393) microuptime() went backwards (1960.4337567 -> 1960.965830) microuptime() went backwards (1985.3978684 -> 1984.781996) microuptime() went backwards (1985.3978684 -> 1984.857352) microuptime() went backwards (2241.3910344 -> 2241.274206) microuptime() went backwards (2458.3750237 -> 2457.673501) microuptime() went backwards (2548.4364374 -> 2548.592190) microuptime() went backwards (2548.4364374 -> 2548.670159) microuptime() went backwards (2560.4124905 -> 2559.917046) microuptime() went backwards (2560.4124905 -> 2560.722790) microuptime() went backwards (2753.3773692 -> 2752.322675) microuptime() went backwards (2796.154103 -> 2796.153535) microuptime() went backwards (3005.4345219 -> 3005.116923) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 21:40:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C83AF37B410 for ; Sun, 30 Sep 2001 21:40:49 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f914oOn05597; Sun, 30 Sep 2001 21:50:25 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110010450.f914oOn05597@mass.dis.org> To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: reappearance of an old bug again? (microtime went backwards) In-Reply-To: Message from Matthew Jacob of "Sun, 30 Sep 2001 21:35:27 PDT." Date: Sun, 30 Sep 2001 21:50:24 -0700 From: Mike Smith 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 > > -current as of the last day or so- anyone else seen? > > Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041 > microuptime() went backwards (939.4410978 -> 938.949317) Try turning off the ACPI timer: debug.acpi.disable="timer" in loader.conf and see if it goes away. I'm still looking for better testing techniques, since it looks like the ACPI timer can't be trusted. 8( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 21:43:35 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 DA26037B40F; Sun, 30 Sep 2001 21:43:31 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f914hVH96086; Sun, 30 Sep 2001 21:43:31 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 30 Sep 2001 21:43:30 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Mike Smith Cc: current@freebsd.org Subject: Re: reappearance of an old bug again? (microtime went backwards) In-Reply-To: <200110010450.f914oOn05597@mass.dis.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 Cool. Yes. Will do. It also turns out that even with this being an SMP system with IOAPIC that ACPI still shares an irq with isp0. How odd. On Sun, 30 Sep 2001, Mike Smith wrote: > > > > -current as of the last day or so- anyone else seen? > > > > Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041 > > microuptime() went backwards (939.4410978 -> 938.949317) > > Try turning off the ACPI timer: > > debug.acpi.disable="timer" > > in loader.conf and see if it goes away. I'm still looking for better > testing techniques, since it looks like the ACPI timer can't be trusted. 8( > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 22:41: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 7128B37B409 for ; Sun, 30 Sep 2001 22:41:15 -0700 (PDT) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f915eh5484023; Mon, 1 Oct 2001 14:40:43 +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 f915ehO326005; Mon, 1 Oct 2001 14:40:43 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:9piUckXWf2pvbP6SvcZxskL33AENdNdN@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 OAA01361; Mon, 1 Oct 2001 14:50:19 +0900 (JST) Message-Id: <200110010550.OAA01361@zodiac.mech.utsunomiya-u.ac.jp> To: Anton Berezin Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: cvs commit: src/sys/isa psm.c atkbdc_isa.c In-reply-to: Your message of "Mon, 01 Oct 2001 01:32:54 +0200." <20011001013254.A698@heechee.tobez.org> References: <200109251659.f8PGxTN66726@freefall.freebsd.org> <20011001013254.A698@heechee.tobez.org> Date: Mon, 01 Oct 2001 14:50:18 +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 >> Modified files: >> sys/isa psm.c atkbdc_isa.c >> Log: >> Yet another turn of workaround for psm/ACPI/PnP BIOS >> problems currently experienced in -CURRENT. >> >> This should fix the problem that the PS/2 mouse is detected >> twice if the acpi module is not loaded on some systems. >> >> Revision Changes Path >> 1.24 +2 -2 src/sys/isa/atkbdc_isa.c >> 1.40 +84 -39 src/sys/isa/psm.c > >Can it be that this fix is responsible for PS/2 mouse being detected >zero times? :-) :-( > >Dmesg output is in a separate message. This is most likely to be an ACPI problem. Please try disabling the acpi module ("unset load_acpi" at the loader prompt) and "boot -v", then send me dmesg's output. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 23:13: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 01E0537B40C for ; Sun, 30 Sep 2001 23:12:59 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f916MYn06393; Sun, 30 Sep 2001 23:22:34 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110010622.f916MYn06393@mass.dis.org> To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: reappearance of an old bug again? (microtime went backwards) In-Reply-To: Message from Matthew Jacob of "Sun, 30 Sep 2001 21:43:30 PDT." Date: Sun, 30 Sep 2001 23:22:34 -0700 From: Mike Smith 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 > > Cool. Yes. Will do. It also turns out that even with this being an SMP system > with IOAPIC that ACPI still shares an irq with isp0. How odd. This is probably an artifact of the PCI interrupt swizzle; the ACPI irq is typically an interrupt line out of the southbridge (where the "power management controller" typically lives). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 30 23:40:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-227.dsl.lsan03.pacbell.net [64.165.226.227]) by hub.freebsd.org (Postfix) with ESMTP id 81D9037B40B for ; Sun, 30 Sep 2001 23:40:31 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BFE4566BD5; Sun, 30 Sep 2001 23:40:30 -0700 (PDT) Date: Sun, 30 Sep 2001 23:40:30 -0700 From: Kris Kennaway To: current@FreeBSD.org Subject: HEADS UP: UUCP migration to ports Message-ID: <20010930234030.A67748@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" 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 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, As discussed on -arch, I've removed the UUCP utilities from the base system, and they now live in the net/freebsd-uucp port. I have left the cu utility behind, because it reportedly has capabilities not supported by tip at this time. Ideally, it would be great if we can get any missing capabilities added to tip so we can complete the removal of cu, but that's a project for another time and possibly another person (I've noticed OpenBSD have done some work in this direction already). I've verified that cu continues to build, but since I don't use it I can't test whether it still works. Please let me know of any problems with this, or the UUCP port and I'll be happy to fix them. Kris P.S. I'm running a post-commit buildworld now to verify that I haven't broken the build. --3V7upXqbjpZ4EhLz 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 iD8DBQE7uA/eWry0BWjoQKURAkL7AJ4guxjsBgU5mH6YbGB014VEu8GWmwCgvTlR 8naijtMKOxmE/RAJ1aDe9wM= =eDNT -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 0:33:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 4538937B413; Mon, 1 Oct 2001 00:33:07 -0700 (PDT) Received: from vega.vega.com (h137.228.dialup.iptcom.net [212.9.228.137]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id KAA40245; Mon, 1 Oct 2001 10:32:57 +0300 (EEST) (envelope-from max@vega.com) Received: (from max@localhost) by vega.vega.com (8.11.6/8.11.3) id f917WPY68887; Mon, 1 Oct 2001 10:32:25 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200110010732.f917WPY68887@vega.vega.com> Subject: Some CDIO ioctl's are broken To: sos@FreeBSD.org Date: Mon, 1 Oct 2001 10:32:24 +0300 (EEST) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.5 PL5] 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 Hi Soren, It seems that after a commit to reduce stack usage in ata driver some CDIO ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an 'Invalid argument'. This could be verified by executing `cdcontrol stat'. Please fix. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 0:40: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 4D5E937B40A; Mon, 1 Oct 2001 00:40:02 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id f917e1u64130; Mon, 1 Oct 2001 09:40:01 +0200 (CEST) (envelope-from sos) From: S鷨en Schmidt Message-Id: <200110010740.f917e1u64130@freebsd.dk> Subject: Re: Some CDIO ioctl's are broken In-Reply-To: <200110010732.f917WPY68887@vega.vega.com> "from Maxim Sobolev at Oct 1, 2001 10:32:24 am" To: Maxim Sobolev Date: Mon, 1 Oct 2001 09:40:01 +0200 (CEST) Cc: sos@FreeBSD.org, current@FreeBSD.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > Hi Soren, > > It seems that after a commit to reduce stack usage in ata driver some CDIO > ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an > 'Invalid argument'. This could be verified by executing `cdcontrol stat'. Uhm: sos> cdcontrol -f acd0 stat No current status info available No media catalog info available Left volume = 255, right volume = 255 That looks pretty OK to me ... -S鷨en To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 0:52:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id C09F137B40F; Mon, 1 Oct 2001 00:52:06 -0700 (PDT) Received: from vega.vega.com (h50.229.dialup.iptcom.net [212.9.229.50]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id KAA46218; Mon, 1 Oct 2001 10:52:02 +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.6/8.11.3) with ESMTP id f917onA68965; Mon, 1 Oct 2001 10:50:49 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BB820C3.FB36C84@FreeBSD.org> Date: Mon, 01 Oct 2001 10:52:36 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: sos@freebsd.dk Cc: sos@FreeBSD.org, current@FreeBSD.org Subject: Re: Some CDIO ioctl's are broken References: <200110010740.f917e1u64130@freebsd.dk> Content-Type: text/plain; charset=x-user-defined 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 "S鈜en Schmidt" wrote: > It seems Maxim Sobolev wrote: > > Hi Soren, > > > > It seems that after a commit to reduce stack usage in ata driver some CDIO > > ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an > > 'Invalid argument'. This could be verified by executing `cdcontrol stat'. > > Uhm: > > sos> cdcontrol -f acd0 stat > No current status info available > No media catalog info available > Left volume = 255, right volume = 255 > > That looks pretty OK to me ... No it isn't normal. Try to truss(1) it and see the problem which leads to the first string to be "No current status info available". Alternatively, try to boot 11 days old kernel and see the difference. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 0:54:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A3BA37B407; Mon, 1 Oct 2001 00:54:02 -0700 (PDT) Received: from vega.vega.com (h50.229.dialup.iptcom.net [212.9.229.50]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id KAA46939; Mon, 1 Oct 2001 10:53:58 +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.6/8.11.3) with ESMTP id f917rQA68994; Mon, 1 Oct 2001 10:53:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BB82160.8910B33A@FreeBSD.org> Date: Mon, 01 Oct 2001 10:55:12 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: "Andrey A. Chernov" , msmith@FreeBSD.org, current@FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation References: <200109171327.f8HDRKm12450@vega.vega.com> <20010918001654.A2442@nagual.pp.ru> <3BA710D9.75544A23@FreeBSD.org> <3BA99FEA.7270C90A@FreeBSD.org> 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: > Maxim Sobolev wrote: > > > "Andrey A. Chernov" wrote: > > > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote: > > > > Hi, > > > > > > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found > > > > that I'm having problem with resource allocation for floppy disk controller. > > > > I'm sure somebody already reported this some time ago, but the problems seems > > > > still here, so I would like to see it resolved. > > > > > > > fdc0: cannot reserve I/O port range (1 ports) > > > > > > It seems that here is conflict with your device.hints, try to remove fdc > > > from the hints. > > > > > > As I already write, it is very bad thing that ACPI is in conflicts with > > > default hints file correctly describing devices used. ACPI must ignore > > > duplicate devices from the hints. > > > > > > The problem with floppy is harder, because floppy controller present in > > > ACPI but the floppy itself not present (on my motherboard at least), so > > > in current situation fdc0 must not be in hints, but fd0 must be, it makes > > > whole thing even more cryptic. > > > > Doesn't work, exactly the same problem - see attached device.hints. > > Knock, knock... Is anybody home? Hmm, it is very sad to see that acpi code is totally unsupported, especially in the spite of recent "how to attract people to test -current" thread. The problem is still here, as of today's kernel. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 0:57:11 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 17C5C37B409 for ; Mon, 1 Oct 2001 00:57:09 -0700 (PDT) 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 f917v7u67025; Mon, 1 Oct 2001 01:57:07 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f917v6703030; Mon, 1 Oct 2001 01:57:07 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110010757.f917v6703030@harmony.village.org> To: mjacob@feral.com Subject: Re: reappearance of an old bug again? (microtime went backwards) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 30 Sep 2001 21:35:27 PDT." References: Date: Mon, 01 Oct 2001 01:57:06 -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 Matthew Jacob writes: : -current as of the last day or so- anyone else seen? Do these happen with acpi disabled? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 1:43: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id 7F37637B401 for ; Mon, 1 Oct 2001 01:42:57 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f918grL31041; Mon, 1 Oct 2001 01:42:53 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA1504780; Mon, 1 Oct 2001 10:42:38 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA06722; Mon, 1 Oct 2001 10:42:10 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA64875; Mon, 1 Oct 2001 10:42:07 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.5/8.11.5) with ESMTP id f918fXC01053; Mon, 1 Oct 2001 10:41:34 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Mon, 01 Oct 2001 10:41:33 +0200 Message-ID: From: "Georg-W. Koltermann" To: Warner Losh Cc: "Georg-W. Koltermann" , current@freebsd.org Subject: Re: cardbus nonfunctional in -current as of 9/24 In-Reply-To: <200109300857.f8U8vR794609@harmony.village.org> References: <200109300857.f8U8vR794609@harmony.village.org> User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk 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 At Sun, 30 Sep 2001 02:57:27 -0600, Warner Losh wrote: > > Try disabling acpi and let me know what's what. > > Warner Still the same without acpi. Last night, undocked: Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: at device 4.0 on pci0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 10000000 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus0: on pccbb0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccard0: <16-bit PCCard bus> on pccbb0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: at device 4.1 on pci0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus1: on pccbb1 Sep 30 20:23:00 hunter /boot/kernel/kernel: pccard1: <16-bit PCCard bus> on pccbb1 Sep 30 20:23:00 hunter /boot/kernel/kernel: isab0: at device 7.0 on pci0 Sep 30 20:23:00 hunter /boot/kernel/kernel: isa0: on isab0 [...] Sep 30 20:23:00 hunter /boot/kernel/kernel: acd0: DVD-ROM at ata1-master PIO4 Sep 30 20:23:00 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x00000000, state=00000000 Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: card inserted: event=0x00000000, state=00000000 Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected Sep 30 20:23:00 hunter /boot/kernel/kernel: linprocfs registered Today, docked: Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb0: at device 4.0 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 10000000 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: cardbus0: on pccbb0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccard0: <16-bit PCCard bus> on pccbb0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb1: at device 4.1 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: cardbus1: on pccbb1 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccard1: <16-bit PCCard bus> on pccbb1 Oct 1 09:01:16 hunter /boot/kernel/kernel: isab0: at device 7.0 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: isa0: on isab0 [...] Oct 1 09:01:17 hunter /boot/kernel/kernel: acd0: DVD-ROM at ata1-master PIO4 Oct 1 09:01:17 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x00000000, state=00000000 Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb1: card inserted: event=0x00000000, state=00000000 Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected Oct 1 09:01:17 hunter /boot/kernel/kernel: linprocfs registered [...] Oct 1 09:06:03 hunter su: gwk to root on /dev/ttyp2 Oct 1 09:09:58 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Oct 1 09:10:33 hunter last message repeated 35 times Oct 1 09:12:34 hunter last message repeated 349 times Oct 1 09:21:11 hunter last message repeated 3687 times Oct 1 09:21:11 hunter su: gwk to root on /dev/ttyp4 Oct 1 09:21:11 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Oct 1 09:21:18 hunter last message repeated 66 times Oct 1 09:21:19 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 Oct 1 09:21:19 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:21:20 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 Oct 1 09:21:20 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:21:22 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 Oct 1 09:21:22 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:21:24 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 ...and on and on. Note that these insertion messages appeared spontaneously. I didn't even touch the cards. An OLDCARD kernel works fine on the same machine, even with ACPI. I have one 16 bit card and one 32 bit card. BTW, I was surprised to see that ACPI was even able to suspend and resume my machine, with some quirks. Sound is dead after resume, PCMCIA is dead after a couple of resumes (maybe intermittent?), suspend/resume in X11 will fade the LCD to rainbow colors. But the basic functionality is there, so it's an improvement to APM which wasn't able to resume my machine since a couple of months now. -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 1:51:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id E320637B40B for ; Mon, 1 Oct 2001 01:51:21 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f918pKL31741 for <@rj.corp.sgi.com:current@freebsd.org>; Mon, 1 Oct 2001 01:51:21 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA1508541 for <@eugate.sgi.com:current@freebsd.org>; Mon, 1 Oct 2001 10:51:18 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA07158; Mon, 1 Oct 2001 10:50:50 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA65106; Mon, 1 Oct 2001 10:50:36 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.5/8.11.5) with ESMTP id f918oHC01120; Mon, 1 Oct 2001 10:50:18 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Mon, 01 Oct 2001 10:50:17 +0200 Message-ID: From: "Georg-W. Koltermann" To: current@freebsd.org Subject: ACPI and APM interoperability? User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk 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 Hi, I'm wondering how I should handle APM now that ACPI has basically taken over power management responsibility. It seems I still need to configure APM so that /dev/apm is there and battery monitoring utilities like the GNOME battery_applet can work. I also was able to suspend and resume my machine (DELL Inspiron 7500) with APM being configured (and ACPI being active by default). Sound is dead after a resume, PCMCIA is dead after a couple of resumes, I have to switch to text mode before suspend or else the LCD will turn pale, but still, the basic functionality is there. APM used to lockup on resume, so this is a definite improvement. Oh, and I'm wondering why a close of the lid only does a "mild" suspend where the laptop still hums (disk? fan?). I need to do a "acpiconf -s3" in order to get it to really suspend. Is this configurable someplace? -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 2: 3:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-227.dsl.lsan03.pacbell.net [64.165.226.227]) by hub.freebsd.org (Postfix) with ESMTP id A0CDF37B413 for ; Mon, 1 Oct 2001 02:02:47 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2B6C266BD5; Mon, 1 Oct 2001 02:02:47 -0700 (PDT) Date: Mon, 1 Oct 2001 02:02:46 -0700 From: Kris Kennaway To: current@FreeBSD.org Subject: uucp user shell and home directory Message-ID: <20011001020246.A77511@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" 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 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Can anyone tell me why the uucp user needs to have a default shell and home directory set? uucp:*:66:66:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico Both of those no longer exist by default in FreeBSD, with my changes. Is there any reason why this can't be changed to: uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin ? Kris --gKMricLos+KVdGMg 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 iD8DBQE7uDE2Wry0BWjoQKURAiO4AJ9ixu9rAu2YGK6JTaeP7jKMKWSslgCgyODG 7B1cpND2vtLZYObngtMg2Mc= =ZkII -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 3:53:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from ms4.kntech.com.tw (ms4.kntech.com.tw [210.200.114.14]) by hub.freebsd.org (Postfix) with ESMTP id 24AB437B40D for ; Mon, 1 Oct 2001 03:53:31 -0700 (PDT) Received: from Y3E1N1 (121-93.kntech.com.tw [210.201.121.93]) by ms4.kntech.com.tw (8.9.3/8.9.3) with ESMTP id SAA25924 for ; Mon, 1 Oct 2001 18:56:01 +0800 Message-Id: <200110011056.SAA25924@ms4.kntech.com.tw> From: jingdian@ms4.kntech.com.tw Subject: =?Big5?B?t/rCSbPQt04=?= To: current@freebsd.org Content-Type: text/plain ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; Date: Mon, 1 Oct 2001 19:2:12 +0800 X-Priority: 2 X-Library: Indy 8.009B 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 睛點創意以自由和多元的時間空間創造出最多的成績，以開發創意和構思企劃為主，並提供其執行能力。 睛點創意的工作成員都以擁有相當的工作能力和經驗為最大的資產，並且相互激勵開發創意，注意時下市場商機，以推廣創意理念。 各個成員辦事效率和配合度高，能以最短的時間完成最精緻的作品，不論在資料蒐集，還是在採訪攝影、編輯設計上作最極至的發揮 。 ----------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- 服務項目：平面設計、廣告設計、DM、海報、公司形象CI、雜誌廣告、報紙廣告、型錄、說明書、名片設計...... ●書籍期刊 單冊期刊封面 每件\設計5000\完稿1500 書籍內頁 每頁\設計650\完稿350 ●雜誌廣告 跨頁、拉長頁 每件\設計4000 內頁 每件\設計3000 ●報紙廣告 全20批 每件\設計5000 全10批、半20批 每件\設計3000 ●傳單、DM A3 單面\設計2500 雙面\設計4500 A4 單面\設計1000 雙面\設計1500 ●海報設計 全開 每件\設計8000 菊全、對開 每件\設計4000 菊對 每件\設計3000 ●戶外廣告 廣告招牌 每件\設計5500 車箱廣告 面板\設計4500 帆布廣告 每件\設計3500 旗幟設計 一式兩款\設計2500 ●採訪攝影 每圖\300\給予電子檔 ----------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- 睛點廣告創意坊 地址：台中市北屯區文心路四段182號15樓之7 電話：04-2291-2347 企劃執行 邱啟豪 先生 0922-789-018 創意網站 http://jingdian.2u.com.tw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 4: 1:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 26C5E37B401 for ; Mon, 1 Oct 2001 04:01:39 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15o0pY-0006hf-00; Mon, 01 Oct 2001 13:01:48 +0200 From: Sheldon Hearn To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: uucp user shell and home directory In-reply-to: Your message of "Mon, 01 Oct 2001 02:02:46 MST." <20011001020246.A77511@xor.obsecurity.org> Date: Mon, 01 Oct 2001 13:01:48 +0200 Message-ID: <25770.1001934108@axl.seasidesoftware.co.za> 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, 01 Oct 2001 02:02:46 MST, Kris Kennaway wrote: > uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin Please use /nonexistent while it's the prevailing convention, or change the prevailing convention. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 5:19:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 1C79937B406; Mon, 1 Oct 2001 05:19:11 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f91CJAY29451; Mon, 1 Oct 2001 14:19:10 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f91CJAc29444; Mon, 1 Oct 2001 14:19:10 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id OAA28299; Mon, 1 Oct 2001 14:19:08 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f91CJJq24344; Mon, 1 Oct 2001 14:19:19 +0200 (CEST) (envelope-from alex) Date: Mon, 1 Oct 2001 14:19:16 +0200 From: Alexander Langer To: Hajimu UMEMOTO Cc: current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown Message-ID: <20011001141916.A24281@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , Hajimu UMEMOTO , current@freebsd.org, gad@freebsd.org References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> <20010930.234428.102494221.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010930.234428.102494221.ume@mahoroba.org>; from ume@mahoroba.org on Sun, Sep 30, 2001 at 11:44:28PM +0900 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Hajimu UMEMOTO (ume@mahoroba.org): > alex> 15329 ?? S 0:00.02 lpd -4 > alex> alex@oink ~ $ lpq > alex> lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown > Sorry, but I cannot see this message, here. > Could you please tell me how did you do? I started lpd on this machine: (with the -4 flag, see above). alex@oink ~ $ uname -a ; ifconfig -a FreeBSD oink.cichlids.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Sep 1 15:25:41 CEST 2001 root@oink.cichlids.com:/usr/obj/usr/src/sys/GENERIC i386 rl0: flags=8843 mtu 1500 inet 192.168.0.19 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::250:baff:fed4:a512%rl0 prefixlen 64 scopeid 0x1 ether 00:50:ba:d4:a5:12 media: Ethernet autoselect (100baseTX) status: active lp0: flags=8810 mtu 1500 faith0: flags=8000 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 This is the printcap from this machine: lp|local line printer:\ :sh:\ :rm=neutron:\ :sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: Note that "neutron" has: alex@oink ~ $ ping6 neutron PING6(56=40+8+8 bytes) fe80::250:baff:fed4:a512%rl0 --> fe80:1::250:4ff:fe0f:5a27 16 bytes from fe80::250:4ff:fe0f:5a27%rl0, icmp_seq=0 hlim=64 time=2.492 ms ^X^C (telnet6 works!) Then I just start lpd (or lpd -4, same effect), and this happens. when I do rm=192.168.0.1 in the printcap, I get: root@oink ~ $ lpq oink.cichlids.com: Warning: no daemon present Rank Owner Job Files Total Size 1st alex 0 (standard input) 419326 bytes lpd: Host name for your address (192.168.0.19) unknown So, this MIGHT be the reason: The IPv4 address is nonexistent, but it displays the IPv6 address as error address. However, it's still bad that he uses and IPv6 stuff when I specify -4 BTW, it works if I add a PTR for 192.168.0.19. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 5:21:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 04D8F37B409; Mon, 1 Oct 2001 05:21:18 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f91CLIY29924; Mon, 1 Oct 2001 14:21:18 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f91CLIc29920; Mon, 1 Oct 2001 14:21:18 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id OAA28440; Mon, 1 Oct 2001 14:21:16 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f91CLTI24356; Mon, 1 Oct 2001 14:21:29 +0200 (CEST) (envelope-from alex) Date: Mon, 1 Oct 2001 14:21:28 +0200 From: Alexander Langer To: Hajimu UMEMOTO Cc: current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown Message-ID: <20011001142128.B24281@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , Hajimu UMEMOTO , current@freebsd.org, gad@freebsd.org References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> <20010930.234428.102494221.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010930.234428.102494221.ume@mahoroba.org>; from ume@mahoroba.org on Sun, Sep 30, 2001 at 11:44:28PM +0900 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG BTW, the lpd server (neutron) is a FreeBSD neutron.cichlids.com 4.3-STABLE FreeBSD 4.3-STABLE #0: Tue Jun 5 01:38:27 CEST 2001 root@neutron.cichlids.com:/storage/obj/storage/src/sys/NEUTRON i386 I think the problem is on the server-side. (since the error messages contains a "xl0" string, which is the server's NIC). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 6:31:45 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 86D3337B40E; Mon, 1 Oct 2001 06:20:49 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA35786; Mon, 1 Oct 2001 15:20: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: Alexander Langer Cc: current@FreeBSD.ORG, ume@FreeBSD.ORG, gad@FreeBSD.ORG Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> From: Dag-Erling Smorgrav Date: 01 Oct 2001 15:20:45 +0200 In-Reply-To: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> Message-ID: Lines: 11 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 Alexander Langer writes: > alex@oink ~ $ lpq > lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown The server is reporting that it can't figure out who you are, and therefore won't let you access the printer. See hosts.lpd(5). The client is merely repeating the error message it got from the server. 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 Mon Oct 1 6:38:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id C780637B405; Mon, 1 Oct 2001 06:29:34 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f91DTZY14398; Mon, 1 Oct 2001 15:29:35 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f91DTYc14394; Mon, 1 Oct 2001 15:29:34 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id PAA31326; Mon, 1 Oct 2001 15:29:32 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f91DTiW25004; Mon, 1 Oct 2001 15:29:45 +0200 (CEST) (envelope-from alex) Date: Mon, 1 Oct 2001 15:29:43 +0200 From: Alexander Langer To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG, ume@FreeBSD.ORG, gad@FreeBSD.ORG Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown Message-ID: <20011001152943.A24910@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , Dag-Erling Smorgrav , current@FreeBSD.ORG, ume@FreeBSD.ORG, gad@FreeBSD.ORG References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, Oct 01, 2001 at 03:20:45PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Dag-Erling Smorgrav (des@ofug.org): > > alex@oink ~ $ lpq > > lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown > The server is reporting that it can't figure out who you are, and > therefore won't let you access the printer. See hosts.lpd(5). The > client is merely repeating the error message it got from the server. It's still using IPv6 though I told it to do IPv4. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 6:48: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id 9FB0C37B40D; Mon, 1 Oct 2001 06:43:47 -0700 (PDT) Received: (from root@localhost) by cheer.mahoroba.org (8.12.0/8.12.0) id f91Dha9D089755; Mon, 1 Oct 2001 22:43:36 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:YYgrM01d7AbefP3fuQPcf64CMpjxpU77Ku6YM4sMspeSp8deXRVDAzeqGWxQAnvG@peace.mahoroba.org [IPv6:2001:200:301:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.0/8.12.0/av) with ESMTP/inet6 id f91DhZPp097550; Mon, 1 Oct 2001 22:43:35 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 01 Oct 2001 22:43:34 +0900 (JST) Message-Id: <20011001.224334.74504729.ume@mahoroba.org> To: alex@big.endian.de Cc: des@ofug.org, current@FreeBSD.ORG, gad@FreeBSD.ORG Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown From: Hajimu UMEMOTO In-Reply-To: <20011001152943.A24910@fump.kawo2.rwth-aachen.de> References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> <20011001152943.A24910@fump.kawo2.rwth-aachen.de> 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 X-Mailer: xcite1.38> Mew version 2.0.54 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 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, 1 Oct 2001 15:29:43 +0200 >>>>> Alexander Langer said: alex> Thus spake Dag-Erling Smorgrav (des@ofug.org): > > alex@oink ~ $ lpq > > lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown > The server is reporting that it can't figure out who you are, and > therefore won't let you access the printer. See hosts.lpd(5). The > client is merely repeating the error message it got from the server. alex> It's still using IPv6 though I told it to do IPv4. Still, I cannot understand why it occures, and I cannot reproduce it, here. -- 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 Oct 1 6:53:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id 39C5137B40D; Mon, 1 Oct 2001 06:50:51 -0700 (PDT) Received: (from root@localhost) by cheer.mahoroba.org (8.12.0/8.12.0) id f91DolnH003220; Mon, 1 Oct 2001 22:50:47 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:nIGcEGttmZk1/Gq6xbVdJMlJ/gbX9qsqUK+hlB6m9zIPV/3lTyjEWmrPTDMdaCpR@peace.mahoroba.org [IPv6:2001:200:301:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.0/8.12.0/av) with ESMTP/inet6 id f91DojPp097753; Mon, 1 Oct 2001 22:50:45 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 01 Oct 2001 22:50:44 +0900 (JST) Message-Id: <20011001.225044.115965392.ume@mahoroba.org> To: alex@big.endian.de Cc: current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown From: Hajimu UMEMOTO In-Reply-To: <20011001142128.B24281@fump.kawo2.rwth-aachen.de> References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> <20010930.234428.102494221.ume@mahoroba.org> <20011001142128.B24281@fump.kawo2.rwth-aachen.de> 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 X-Mailer: xcite1.38> Mew version 2.0.54 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 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, 1 Oct 2001 14:21:28 +0200 >>>>> Alexander Langer said: alex> BTW, the lpd server (neutron) is a alex> FreeBSD neutron.cichlids.com 4.3-STABLE FreeBSD 4.3-STABLE #0: Tue Jun 5 01:38:27 CEST 2001 root@neutron.cichlids.com:/storage/obj/storage/src/sys/NEUTRON i386 alex> I think the problem is on the server-side. (since the error messages alex> contains a "xl0" string, which is the server's NIC). Yes, lpd has this message, while lpq hasn't. I'm trying to reproduce it on my 4.4-RELEASE box. -- 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 Oct 1 7:25: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from lamovida.it (www.lamovida.it [212.110.162.163]) by hub.freebsd.org (Postfix) with ESMTP id 5F1E437B413 for ; Mon, 1 Oct 2001 07:24:13 -0700 (PDT) Received: by lamovida.it (Postfix, from userid 1000) id 6C9D916D; Mon, 1 Oct 2001 16:24:12 +0200 (CEST) Date: Mon, 1 Oct 2001 16:24:12 +0200 From: Andrea Campi To: current@freebsd.org Subject: sys/compat/linux/linux_util.h needs KSE patch Message-ID: <20011001162412.A96470@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike 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 Subject says all; I think this patch should be applied. It's for clarity only, no functional change at all. Sorry for the broken whitespaces in the patch but I have to send mail from a remote ssh box etc.. long story, anyway if anybody is willing to commit I can prepare a better patch. Bye, Andrea --- linux_util.h.bak Mon Oct 1 16:20:31 2001 +++ linux_util.h Mon Oct 1 16:21:25 2001 @@ -79,18 +79,18 @@ int linux_emul_find __P((struct thread *, caddr_t *, const char *, char *, char **, int)); -#define CHECKALT(p, sgp, path, i) \ +#define CHECKALT(td, sgp, path, i) \ do { \ int _error; \ \ - _error = linux_emul_find(p, sgp, linux_emul_path, path, \ + _error = linux_emul_find(td, sgp, linux_emul_path, path,\ &path, i); \ if (_error == EFAULT) \ return (_error); \ } while (0) -#define CHECKALTEXIST(p, sgp, path) CHECKALT(p, sgp, path, 0) -#define CHECKALTCREAT(p, sgp, path) CHECKALT(p, sgp, path, 1) +#define CHECKALTEXIST(td, sgp, path) CHECKALT(td, sgp, path, 0) +#define CHECKALTCREAT(td, sgp, path) CHECKALT(td, sgp, path, 1) #define DUMMY(s) \ int \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 7:30: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.cicely.de (ppp110.uni-duisburg.de [134.91.19.110]) by hub.freebsd.org (Postfix) with ESMTP id A9BE337B414 for ; Mon, 1 Oct 2001 07:29:01 -0700 (PDT) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f91ET8d23541 for freebsd-current@freebsd.org; Mon, 1 Oct 2001 16:29:08 +0200 (CEST) Date: Mon, 1 Oct 2001 16:29:08 +0200 From: Bernd Walter To: freebsd-current@freebsd.org Subject: world broken in src/lib/libedit Message-ID: <20011001162907.A23284@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc 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 [...] cd /var/d10/FreeBSD-2001-10-01/src/lib/libc; make beforeinstall cd /var/d10/FreeBSD-2001-10-01/src/lib/libcalendar; make beforeinstall cd /var/d10/FreeBSD-2001-10-01/src/lib/libcalendar && sh /var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444 calendar.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include cd /var/d10/FreeBSD-2001-10-01/src/lib/libcam; make beforeinstall cd /var/d10/FreeBSD-2001-10-01/src/lib/libcam && sh /var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444 camlib.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include cd /var/d10/FreeBSD-2001-10-01/src/lib/libdisk; make beforeinstall cd /var/d10/FreeBSD-2001-10-01/src/lib/libdisk && sh /var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444 libdisk.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit; make beforeinstall cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit && sh /var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444 histedit.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include install: histedit.h: No such file or directory *** Error code 71 Stop in /var/d10/FreeBSD-2001-10-01/src/lib/libedit. *** Error code 1 Stop in /var/d10/FreeBSD-2001-10-01/src. *** Error code 1 Stop in /var/d10/FreeBSD-2001-10-01/src. *** Error code 1 Stop in /var/d10/FreeBSD-2001-10-01/src. 1345.645u 386.311s 44:38.58 64.6% 1315+1849k 6670+1085io 2417pf+0w Exit 1 ticso@cicely5# -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 7:35:10 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 A37B337B40F; Mon, 1 Oct 2001 07:31:38 -0700 (PDT) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id f91F6Ks09189; Mon, 1 Oct 2001 08:06:20 -0700 (PDT) (envelope-from david) Date: Mon, 1 Oct 2001 08:06:20 -0700 (PDT) From: David Wolfskill Message-Id: <200110011506.f91F6Ks09189@bunrab.catwhisker.org> To: current@freebsd.org, obrien@freebsd.org Subject: Today's -CURRENT buildworld breaks: libedit/Makefile wants histedit.h 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 Today's -CURRENT build breaks: >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- ... cd /usr/src/lib/libcam; make beforeinstall cd /usr/src/lib/libcam && sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 camlib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libdisk; make beforeinstall cd /usr/src/lib/libdisk && sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libdisk.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libedit; make beforeinstall cd /usr/src/lib/libedit && sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 histedit.h /usr/obj/usr/src/i386/usr/include install: histedit.h: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 Looks as if histedit.h has been in src/include (vs. src/lib/libedit) for a while, now.... (Ref. src/lib/libedit/Makefile 1.22, line 33.) Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 7:36:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 895F237B414 for ; Mon, 1 Oct 2001 07:34:23 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f91EXh661785; Mon, 1 Oct 2001 17:33:43 +0300 (EEST) (envelope-from ru) Date: Mon, 1 Oct 2001 17:33:43 +0300 From: Ruslan Ermilov To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011001173343.D57416@sunbay.com> References: <20011001020246.A77511@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011001020246.A77511@xor.obsecurity.org>; from kris@obsecurity.org on Mon, Oct 01, 2001 at 02:02:46AM -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, Oct 01, 2001 at 02:02:46AM -0700, Kris Kennaway wrote: > Can anyone tell me why the uucp user needs to have a default shell and > home directory set? > > uucp:*:66:66:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico > > Both of those no longer exist by default in FreeBSD, with my changes. > Is there any reason why this can't be changed to: > > uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin > As already was told on "that channel", this comes from the times when ``uucp'' user didn't have password and the account was used for UUCP communication over serial lines. Any dialup UUCP user should have a passwd(5) entry built like the ``uucp''. It doesn't really matter what the home directory is set to (IIRC), but the shell must be uucico(8). It doesn't make any sense though to enable the ``uucp'' account. Moreover, doing so may have a bad impact on system's security, as many UUCP related files are owner by the user ``uucp''. Having said that, I'm with Sheldon on how this change should be done, i.e., change home directory to /nonexistent and shell to /sbin/nologin. 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 Mon Oct 1 7:55:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 0DB8E37B40B for ; Mon, 1 Oct 2001 07:53:57 -0700 (PDT) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA00918; Mon, 1 Oct 2001 07:53:56 -0700 (PDT) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA01156; Mon, 1 Oct 2001 07:40:25 -0700 (PDT) Received: from hollin.btc.adaptec.com (hollin [162.62.149.56]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id IAA05026; Mon, 1 Oct 2001 08:53:53 -0600 (MDT) Received: (from scottl@localhost) by hollin.btc.adaptec.com (8.11.6/8.11.4) id f91EnAM08551; Mon, 1 Oct 2001 08:49:10 -0600 (MDT) (envelope-from scottl) Date: Mon, 1 Oct 2001 08:49:10 -0600 From: Scott Long To: "Georg-W. Koltermann" Cc: current@freebsd.org Subject: Re: ACPI and APM interoperability? Message-ID: <20011001084910.A1952@hollin.btc.adaptec.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: > Hi, > > I'm wondering how I should handle APM now that ACPI has basically > taken over power management responsibility. APM and ACPI are mutually exclusive from what I understand. You should remove the apm device from your kernel config. > It seems I still need to configure APM so that /dev/apm is there and > battery monitoring utilities like the GNOME battery_applet can work. Battery, temp, etc, can be monitored via the hw.acpi sysctl tree. Someone will have to do the required conversion to the various APM utilities is GNOME and whatever else. > I also was able to suspend and resume my machine (DELL Inspiron 7500) > with APM being configured (and ACPI being active by default). Sound > is dead after a resume, What sound card? > PCMCIA is dead after a couple of resumes, Resource leak? Warner? Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 8: 3:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from lamovida.it (www.lamovida.it [212.110.162.163]) by hub.freebsd.org (Postfix) with ESMTP id C034437B40A for ; Mon, 1 Oct 2001 07:59:33 -0700 (PDT) Received: by lamovida.it (Postfix, from userid 1000) id 0205652; Mon, 1 Oct 2001 16:59:31 +0200 (CEST) Date: Mon, 1 Oct 2001 16:59:31 +0200 From: Andrea Campi To: current@freebsd.org Subject: RFC: /compat/linux altpath behavior under admin control Message-ID: <20011001165931.A96486@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike 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 current@, as you no doubt know, when you run a Linux binary every file access undergoes an intermediate step where the kernel looks for a file with the same name under /compat/linux. This interferes with basically anything which needs to traverse the whole tree, and in particular backup software (Tivoli Storage Manager, in my case). You can reproduce this by just doing: $ /compat/linux/bin/bash $ ls -laR / | less And you see a nice mix of Linux and FreeBSD dirs / files. After playing tricks for sometime (I currently remount filesystems via nullfs on /backup and backup that tree), I am now looking at a different solution. I am preparing a patch which should only touch linux_emul_find() in src/sys/compat/linux/linux_util.c, to check if the process name (td->td_proc->p_args) matches one of a list given with a sysctl, and if so, just return with no mapping. I will produce a patch, but I will need assistance wrt any locking I might need, making sure sysctl works properly, etc. Is there anybody interested enough to volunteer to mentor me on this mini-project? ;-) TIA, bye, Andrea To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 8: 5:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 4F48D37B414 for ; Mon, 1 Oct 2001 08:01:28 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id f91F1Rr83025 for current@freebsd.org; Mon, 1 Oct 2001 17:01:27 +0200 (CEST) (envelope-from sos) From: S鷨en Schmidt Message-Id: <200110011501.f91F1Rr83025@freebsd.dk> Subject: HEADS UP kernel & burncd change.. To: current@freebsd.org Date: Mon, 1 Oct 2001 17:01:26 +0200 (CEST) Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kernel and burncd must be in sync again, a make kernel followed by a make world should do it. -S鷨en To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 8: 7:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id DB79C37B403 for ; Mon, 1 Oct 2001 08:03:57 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id f91F3DJ83369; Mon, 1 Oct 2001 17:03:13 +0200 (CEST) (envelope-from sos) From: S鷨en Schmidt Message-Id: <200110011503.f91F3DJ83369@freebsd.dk> Subject: Re: ACPI and APM interoperability? In-Reply-To: <20011001084910.A1952@hollin.btc.adaptec.com> To: Scott Long Date: Mon, 1 Oct 2001 17:03:13 +0200 (CEST) Cc: "Georg-W. Koltermann" , current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Scott Long wrote: > On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: > > I also was able to suspend and resume my machine (DELL Inspiron 7500) > > with APM being configured (and ACPI being active by default). Sound > > is dead after a resume, > > What sound card? > > > PCMCIA is dead after a couple of resumes, > > Resource leak? Warner? It has been like that on -current for about a month or so on my Latitude as well, try to use slot1 instead of slot0, that makes it work better here... -S鷨en To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 8:47:37 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 6411E37B416 for ; Mon, 1 Oct 2001 08:47:35 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f91FlRH07141; Mon, 1 Oct 2001 08:47:28 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 1 Oct 2001 08:47:27 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Warner Losh Cc: current@freebsd.org Subject: microtime 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 yes, with acpi timer disabled this seems to have gone away To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 9: 0:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 7E3D937B40B; Mon, 1 Oct 2001 08:53:54 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id f91Frfm92134; Tue, 2 Oct 2001 00:53:41 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 02 Oct 2001 00:53:40 +0900 (JST) Message-Id: <20011002.005340.74695085.iwasaki@jp.FreeBSD.org> To: sobomax@FreeBSD.org Cc: ache@nagual.pp.ru, msmith@FreeBSD.org, current@FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation From: Mitsuru IWASAKI In-Reply-To: <3BB82160.8910B33A@FreeBSD.org> References: <3BA710D9.75544A23@FreeBSD.org> <3BA99FEA.7270C90A@FreeBSD.org> <3BB82160.8910B33A@FreeBSD.org> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) 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 Hi, > Maxim Sobolev wrote: > > > Maxim Sobolev wrote: > > > > > "Andrey A. Chernov" wrote: > > > > > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote: > > > > > Hi, > > > > > > > > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found > > > > > that I'm having problem with resource allocation for floppy disk controller. > > > > > I'm sure somebody already reported this some time ago, but the problems seems > > > > > still here, so I would like to see it resolved. > > > > > > > > > fdc0: cannot reserve I/O port range (1 ports) > > > > > > > > It seems that here is conflict with your device.hints, try to remove fdc > > > > from the hints. > > > > > > > > As I already write, it is very bad thing that ACPI is in conflicts with > > > > default hints file correctly describing devices used. ACPI must ignore > > > > duplicate devices from the hints. > > > > > > > > The problem with floppy is harder, because floppy controller present in > > > > ACPI but the floppy itself not present (on my motherboard at least), so > > > > in current situation fdc0 must not be in hints, but fd0 must be, it makes > > > > whole thing even more cryptic. > > > > > > Doesn't work, exactly the same problem - see attached device.hints. > > > > Knock, knock... Is anybody home? > > Hmm, it is very sad to see that acpi code is totally unsupported, especially in the > spite of recent "how to attract people to test -current" thread. The problem is still > here, as of today's kernel. I'm not sure exactly what's the problem you are having, but it's too little information to track it down... Could you send acpi-jp@jp.freebsd.org ; - acpidump output; like # acpidump -o your_machine_name.dsdt > your_machine_name.dsdt.asl I'll add them to http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp - dmesg output of kernel boot -v Mike, anything add to this? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 9:54:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 8AA4137B409; Mon, 1 Oct 2001 09:52:42 -0700 (PDT) Received: from vega.vega.com (h226.228.dialup.iptcom.net [212.9.228.226]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id TAA70193; Mon, 1 Oct 2001 19:52:37 +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.6/8.11.3) with ESMTP id f91Gq6A70994; Mon, 1 Oct 2001 19:52:06 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BB89FA1.DD75D31C@FreeBSD.org> Date: Mon, 01 Oct 2001 19:53:53 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Mitsuru IWASAKI Cc: ache@nagual.pp.ru, msmith@FreeBSD.org, current@FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation References: <3BA710D9.75544A23@FreeBSD.org> <3BA99FEA.7270C90A@FreeBSD.org> <3BB82160.8910B33A@FreeBSD.org> <20011002.005340.74695085.iwasaki@jp.FreeBSD.org> 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 Mitsuru IWASAKI wrote: > Hi, > > > Maxim Sobolev wrote: > > > > > Maxim Sobolev wrote: > > > > > > > "Andrey A. Chernov" wrote: > > > > > > > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote: > > > > > > Hi, > > > > > > > > > > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found > > > > > > that I'm having problem with resource allocation for floppy disk controller. > > > > > > I'm sure somebody already reported this some time ago, but the problems seems > > > > > > still here, so I would like to see it resolved. > > > > > > > > > > > fdc0: cannot reserve I/O port range (1 ports) > > > > > > > > > > It seems that here is conflict with your device.hints, try to remove fdc > > > > > from the hints. > > > > > > > > > > As I already write, it is very bad thing that ACPI is in conflicts with > > > > > default hints file correctly describing devices used. ACPI must ignore > > > > > duplicate devices from the hints. > > > > > > > > > > The problem with floppy is harder, because floppy controller present in > > > > > ACPI but the floppy itself not present (on my motherboard at least), so > > > > > in current situation fdc0 must not be in hints, but fd0 must be, it makes > > > > > whole thing even more cryptic. > > > > > > > > Doesn't work, exactly the same problem - see attached device.hints. > > > > > > Knock, knock... Is anybody home? > > > > Hmm, it is very sad to see that acpi code is totally unsupported, especially in the > > spite of recent "how to attract people to test -current" thread. The problem is still > > here, as of today's kernel. > > I'm not sure exactly what's the problem you are having, but it's too > little information to track it down... > Could you send acpi-jp@jp.freebsd.org ; > - acpidump output; like > # acpidump -o your_machine_name.dsdt > your_machine_name.dsdt.asl > I'll add them to > http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp > - dmesg output of kernel boot -v Just sent it to you privately. After hiting sed button I've realised that machine_name that you have requested != host_name. Since it isn't a brandname model you can identify it after the mainboard name - Tyan-S1590. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 10: 5:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 1D8AC37B408 for ; Mon, 1 Oct 2001 10:05:28 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id f91H4Ym04765; Tue, 2 Oct 2001 02:04:35 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 02 Oct 2001 02:04:31 +0900 (JST) Message-Id: <20011002.020431.25420279.iwasaki@jp.FreeBSD.org> To: scott_long@btc.adaptec.com Cc: gwk@sgi.com, current@freebsd.org Subject: Re: ACPI and APM interoperability? From: Mitsuru IWASAKI In-Reply-To: <20011001084910.A1952@hollin.btc.adaptec.com> References: <20011001084910.A1952@hollin.btc.adaptec.com> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) 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 Hi, > On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: > > Hi, > > > > I'm wondering how I should handle APM now that ACPI has basically > > taken over power management responsibility. > > APM and ACPI are mutually exclusive from what I understand. You should > remove the apm device from your kernel config. Yes, some older machines w/ ACPI can support both of them at the same time, but most modern machines don't. > > It seems I still need to configure APM so that /dev/apm is there and > > battery monitoring utilities like the GNOME battery_applet can work. > > Battery, temp, etc, can be monitored via the hw.acpi sysctl tree. > Someone will have to do the required conversion to the various APM > utilities is GNOME and whatever else. Yes, you can get battery info. in C code like; sysctlbyname("hw.acpi.battery.time", &percent, &len, NULL, 0); Note that these MIBs maybe change in future... Generalized power-management interface API to have compatibility with APM and ACPI also is suggested long time ago; http://www.freebsd.org/cgi/getmsg.cgi?fetch=403390+406841+/usr/local/www/db/text/2001/freebsd-current/20010114.freebsd-current Device node for ACPI is discussed bofore too; having only one /dev/acpi or having generalized nodes for each device types such as /dev/battery0 but we couldn't reach the conclusion, now discussion stops... Any suggestions on it? Once we get the conclusion, we can start developing API and convert userland tools. > > I also was able to suspend and resume my machine (DELL Inspiron 7500) > > with APM being configured (and ACPI being active by default). Sound > > is dead after a resume, > > What sound card? > > > PCMCIA is dead after a couple of resumes, > > Resource leak? Warner? Is yours similar to any data at there (Dell_I7500*) ? http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp I guess CardBus controllers are _SB_.PCI0.CB1_ and _SB_.PCI0.CB2_ but I didn't see any sleep/wakeup hack for them... Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 10:41:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 84DEE37B416 for ; Mon, 1 Oct 2001 10:38:25 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f91Hc3i94899; Mon, 1 Oct 2001 10:38:03 -0700 (PDT) (envelope-from obrien) Date: Mon, 1 Oct 2001 10:38:03 -0700 From: "David O'Brien" To: David Wolfskill Cc: current@freebsd.org Subject: Re: Today's -CURRENT buildworld breaks: libedit/Makefile wants histedit.h Message-ID: <20011001103803.A94881@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200110011506.f91F6Ks09189@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110011506.f91F6Ks09189@bunrab.catwhisker.org>; from david@catwhisker.org on Mon, Oct 01, 2001 at 08:06:20AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 01, 2001 at 08:06:20AM -0700, David Wolfskill wrote: > Today's -CURRENT build breaks: Thanks for the note. I'm looking now what is different from my test box and what everyone else has. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 10:41:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81]) by hub.freebsd.org (Postfix) with ESMTP id E581137B413 for ; Mon, 1 Oct 2001 10:37:55 -0700 (PDT) Received: from fwd02.sul.t-online.de by mailout03.sul.t-online.de with smtp id 15o70q-0002qW-00; Mon, 01 Oct 2001 19:37:52 +0200 Received: from server.rock.net (340029380333-0001@[217.224.24.82]) by fmrl02.sul.t-online.com with esmtp id 15o70j-1y4L4qC; Mon, 1 Oct 2001 19:37:45 +0200 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.6/8.11.6/Rock) with ESMTP id f91HbeK62213 for ; Mon, 1 Oct 2001 19:37:40 +0200 (MEST) Message-ID: <3BB8A9E3.7058FBEA@t-online.de> Date: Mon, 01 Oct 2001 19:37:39 +0200 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: panic in ipfw code Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net 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 wondered nobody noticed this bug so far. The kernel panics if you feed him with unnumbered firewall rules (like "ipfw add allow all from any to any") Fix is simple. In the code the wrong loop variable was used: Index: ip_fw.c =================================================================== RCS file: /data/cvs/src/sys/netinet/ip_fw.c,v retrieving revision 1.170 diff -u -r1.170 ip_fw.c --- ip_fw.c 27 Sep 2001 23:44:26 -0000 1.170 +++ ip_fw.c 1 Oct 2001 17:20:39 -0000 @@ -1654,9 +1654,9 @@ /* If entry number is 0, find highest numbered rule and add 100 */ if (ftmp->fw_number == 0) { - LIST_FOREACH(ftmp, head, next) { - if (ftmp->fw_number != IPFW_DEFAULT_RULE) - nbr = ftmp->fw_number; + LIST_FOREACH(fcp, head, next) { + if (fcp->fw_number != IPFW_DEFAULT_RULE) + nbr = fcp->fw_number; else break; } -- Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 10:41:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 17C3B37B409; Mon, 1 Oct 2001 10:32:10 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare/smtpfeed 1.14) with ESMTP/inet id f91HW2m08523; Tue, 2 Oct 2001 02:32:03 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 02 Oct 2001 02:31:58 +0900 (JST) Message-Id: <20011002.023158.71143343.iwasaki@jp.FreeBSD.org> To: sobomax@FreeBSD.org Cc: ache@nagual.pp.ru, msmith@FreeBSD.org, current@FreeBSD.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation From: Mitsuru IWASAKI In-Reply-To: <3BB89FA1.DD75D31C@FreeBSD.org> <3BB89DB9.54C35891@FreeBSD.org> References: <3BB82160.8910B33A@FreeBSD.org> <20011002.005340.74695085.iwasaki@jp.FreeBSD.org> <3BB89FA1.DD75D31C@FreeBSD.org> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) 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 Hi, > > I'm not sure exactly what's the problem you are having, but it's too > > little information to track it down... > > Could you send acpi-jp@jp.freebsd.org ; > > - acpidump output; like > > # acpidump -o your_machine_name.dsdt > your_machine_name.dsdt.asl > > I'll add them to > > http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp > > - dmesg output of kernel boot -v > > Just sent it to you privately. After hiting sed button I've realised that machine_name that > you have requested != host_name. Since it isn't a brandname model you can identify it after > the mainboard name - Tyan-S1590. Thanks, I've just add them to http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/Tyan-S1590.asl?cvsroot=freebsd-jp The problem is here, right? > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some problems (not sure in BIOS or ACPICA yet). I could reproduce the problem which you reported. Trace attached in this mail. I'll try to make a workaround tomorrow or next, sorry. # Here in Japan, it's midnight... Thanks % acpicadb Tyan-S1590.dsdt Parsing Methods:....................................................... 55 Control Methods found and parsed (259 nodes total) ACPI Namespace successfully loaded at root 0x8087414 - f FDC0 \_SB_.PCI0.ISA_.FDC0 (0x8098da8) - Device - debug _SB_.PCI0.ISA_.FDC0._CRS Executing \_SB_.PCI0.ISA_.FDC0._CRS 00000 #0008 [00] Name BUF0 (Path \) [00] ( 00005 #0011 [01] ....Buffer [01] ....( 00007 #000A [02] ........(UINT8) 0x18, 00009 #0033 [02] ........ByteList (Length 0x00000018) [02] ....} [01] } % ArgObj: 0x80acfa8 Integer 0000000000000018 00021 #008C [00] CreateByteField [00] ( 00022 #002D [01] ....BUF0, (Path 00026 #000A [01] ....(UINT8) 0x02, 00028 #002D [01] ....IOLO (Path [01] } % ArgObj: 0x80acf28 Name BUF0 Type-Buffer ArgObj: 0x80af1a8 Integer 0000000000000002 ArgObj: 0x80af0a8 Name IOLO Type-BuffField 0002C #008C [00] CreateByteField [00] ( 0002D #002D [01] ....BUF0, (Path 00031 #000A [01] ....(UINT8) 0x03, 00033 #002D [01] ....IOHI (Path [01] } % ArgObj: 0x80acf28 Name BUF0 Type-Buffer ArgObj: 0x80af328 Integer 0000000000000003 ArgObj: 0x80af228 Name IOHI Type-BuffField 00037 #008C [00] CreateByteField [00] ( 00038 #002D [01] ....BUF0, (Path 0003C #000A [01] ....(UINT8) 0x04, 0003E #002D [01] ....IORL (Path [01] } % ArgObj: 0x80acf28 Name BUF0 Type-Buffer ArgObj: 0x80af4a8 Integer 0000000000000004 ArgObj: 0x80af3a8 Name IORL Type-BuffField 00042 #008C [00] CreateByteField [00] ( 00043 #002D [01] ....BUF0, (Path 00047 #000A [01] ....(UINT8) 0x05, 00049 #002D [01] ....IORH (Path [01] } % ArgObj: 0x80acf28 Name BUF0 Type-Buffer ArgObj: 0x80af628 Integer 0000000000000005 ArgObj: 0x80af528 Name IORH Type-BuffField 0004D #008C [00] CreateByteField [00] ( 0004E #002D [01] ....BUF0, (Path 00052 #000A [01] ....(UINT8) 0x19, 00054 #002D [01] ....IRQL (Path [01] } % ArgObj: 0x80acf28 Name BUF0 Type-Buffer ArgObj: 0x80af7a8 Integer 0000000000000019 ArgObj: 0x80af6a8 Name IRQL Type-BuffField dsopcode-0677 [09] DsEvalBufferFieldOpera: Field size 208 exceeds Buffer size 192 (bits) PsExecute: method failed - \_SB_.PCI0.ISA_.FDC0._CRS (0x8098fa8) Execution of \_SB_.PCI0.ISA_.FDC0._CRS failed with status AE_AML_BUFFER_LIMIT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 10:55:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id 863AD37B405; Mon, 1 Oct 2001 10:51:34 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f91HpW8f014902; Mon, 1 Oct 2001 11:51:32 -0600 (MDT) Message-Id: <200110011751.f91HpW8f014902@atg.aciworldwide.com> Organization: ACI Worldwide - Advanced Technology Group X-URL: http://www.aciworldwide.com/ To: Ruslan Ermilov Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: Message from Ruslan Ermilov of "Mon, 01 Oct 2001 17:33:43 +0300." <20011001173343.D57416@sunbay.com> Date: Mon, 01 Oct 2001 11:51:32 -0600 From: Lyndon Nerenberg 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" == Ruslan Ermilov writes: Ruslan> It doesn't really matter what the home directory is set to Ruslan> (IIRC), but the shell must be uucico(8). No, this is wrong on both counts. By convention, the home directory of the uucp login has corresponded to the UUCP PUBDIR. Traditionally this was /usr/spool/uucppublic, and maps to /var/spool/uucppublic these days. Thus, if I wanted to copy a file to the public file area on machine b I would incant uucp file b!~ and the uucico on the remote end would expand the '~' to /usr/spool/uucppublic. This usage predates (and probably inspired) the common behavior of current shells handling of '~' expansion. While no modern UUCP I'm aware of uses the value of pw->pw_dir to derive PUBDIR, POLA would imply that the interpretation of '~uucp' should be the same for both the uucp(1) command and for shells that do ~ expansion. Therefore I would recommend keeping the UUCP home directory as /var/spool/uucppublic. If you want to be paranoid you make this directory owned by root.wheel and mode 0555 without breaking anything. As for the `uucp' account's shell, this should be set to /sbin/nologin. The purpose of the uucp entry in /etc/passwd is to provide a unique runtime uid for the setuid UUCP components. Note that there are some periodic maintenance scripts that should be run if you actively use UUCP. These traditionally run under the `uucp' identity, so you need to make sure that they will continue to function with /sbin/nologin. (Which they should, otherwise they would have barfed with uucico as the shell.) The shell for the uucp account should most certainly NOT be uucico! And you should *never* allow remote site UUCP logins (those that run uucico) under the `uucp' login, for obvious security reasons. Instead, create seperate unique logins for each remote site, just as you would for each of your shell accounts, but set the login shell to uucico. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 11: 5: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B164237B403 for ; Mon, 1 Oct 2001 11:01:00 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f91I0u053253; Mon, 1 Oct 2001 14:00:56 -0400 (EDT) (envelope-from wollman) Date: Mon, 1 Oct 2001 14:00:56 -0400 (EDT) From: Garrett Wollman Message-Id: <200110011800.f91I0u053253@khavrinen.lcs.mit.edu> To: Lyndon Nerenberg Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: <200110011751.f91HpW8f014902@atg.aciworldwide.com> References: <20011001173343.D57416@sunbay.com> <200110011751.f91HpW8f014902@atg.aciworldwide.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 < said: > And you should *never* allow remote site UUCP logins (those that run > uucico) under the `uucp' login, for obvious security reasons. I remember, back in the mists of ancient time, it was common practice to provide ``anonymous UUCP'' service along the lines of anonymous FTP in (what was at that time) ARPANET. I find it hard to imagine anyone doing so today, but OTOH I find it hard to imagine anyone using UUCP at all today, so it is obviously my imagination which has failed rather than reality. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 11:26:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id 696A337B403 for ; Mon, 1 Oct 2001 11:26:47 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f91IQk8f015078; Mon, 1 Oct 2001 12:26:46 -0600 (MDT) Message-Id: <200110011826.f91IQk8f015078@atg.aciworldwide.com> Organization: ACI Worldwide - Advanced Technology Group X-URL: http://www.aciworldwide.com/ To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: Message from Garrett Wollman of "Mon, 01 Oct 2001 14:00:56 EDT." <200110011800.f91I0u053253@khavrinen.lcs.mit.edu> Date: Mon, 01 Oct 2001 12:26:46 -0600 From: Lyndon Nerenberg 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 >>>>> "Garrett" == Garrett Wollman writes: Garrett> I remember, back in the mists of ancient time, it was Garrett> common practice to provide ``anonymous UUCP'' service Garrett> along the lines of anonymous FTP in (what was at that Garrett> time) ARPANET. Yup, I used to run one of those (ncc). osu-cis was probably the grandaddy of the anonymous UUCP sites. The convention seemed to be to use the login 'nuucp' for anonymous passwordless access. (And I wouldn't call it common -- there were only a handful sites that provided this type of service.) Garrett> I find it hard to imagine anyone doing so Garrett> today, but OTOH I find it hard to imagine anyone using Garrett> UUCP at all today, so it is obviously my imagination Garrett> which has failed rather than reality. UUCP still gets used. It's one of the few sane ways to handle email in a laptop environment when you're always connecting through different dialups/ISPs. It has mostly fallen out of favour due to ignorance and FUD. Which is a shame, as it can still be a useful tool in certain situations. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 11:52:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id A2E2537B40D for ; Mon, 1 Oct 2001 11:52:52 -0700 (PDT) Received: (qmail 39075 invoked by uid 1001); 1 Oct 2001 18:53:18 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15288.48029.798593.908820@zircon.zircon.seattle.wa.us> Date: Mon, 1 Oct 2001 11:53:17 -0700 To: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: <200110011826.f91IQk8f015078@atg.aciworldwide.com> References: <200110011800.f91I0u053253@khavrinen.lcs.mit.edu> <200110011826.f91IQk8f015078@atg.aciworldwide.com> X-Mailer: VM 6.92 under Emacs 20.7.1 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 Lyndon Nerenberg writes: > >>>>> "Garrett" == Garrett Wollman writes: > > Garrett> I remember, back in the mists of ancient time, it was > Garrett> common practice to provide ``anonymous UUCP'' service > Garrett> along the lines of anonymous FTP in (what was at that > Garrett> time) ARPANET. > > Yup, I used to run one of those (ncc). osu-cis was probably the > grandaddy of the anonymous UUCP sites. The convention seemed to be to > use the login 'nuucp' for anonymous passwordless access. (And I > wouldn't call it common -- there were only a handful sites that > provided this type of service.) The convention was to use ``uucp'' as the default anonymous login service. Some people had the mistaken impression that there was some sort of "hole" in the uucp system which was caused by using uucp as a default login for uucp service. No such hole existed in modern uucico processes, although there were bugs in early uucico (7th Edition vintage) which may be the reason that these rumors started. Of course, it didn't hurt the spread of these rumors that most BSD sites were stuck in the 7th Edition heritage and never actually caught up to the modern HoneyDanBer uucp. With the HoneyDanBer uucp, there were no security holes in uucico and it was completely safe to use uucp as an anonymous login service. However, most university sites mistakenly perpetuated the nuucp service, mostly for administrative reasons. That said, for max security it is always useful to have each site have its own login, up to a point. Some large uucp sites used to use common logins simply because there was so little security risk (especially with HoneyDanBer variety). Certainly, anonymous uucp is more secure than anonymous ftp. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 12:16:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 70F7737B40C for ; Mon, 1 Oct 2001 12:16:08 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f91JFtC96289; Mon, 1 Oct 2001 12:15:55 -0700 (PDT) (envelope-from obrien) Date: Mon, 1 Oct 2001 12:15:55 -0700 From: "David O'Brien" To: Bernd Walter Cc: freebsd-current@freebsd.org Subject: Re: world broken in src/lib/libedit Message-ID: <20011001121555.B96248@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20011001162907.A23284@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011001162907.A23284@cicely20.cicely.de>; from ticso@mail.cicely.de on Mon, Oct 01, 2001 at 04:29:08PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 01, 2001 at 04:29:08PM +0200, Bernd Walter wrote: > cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit && sh /var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444 histedit.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include > install: histedit.h: No such file or directory > *** Error code 71 Known problem -- working on it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 12:25:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id 80EC337B401 for ; Mon, 1 Oct 2001 12:25:13 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f91JPC8f015412; Mon, 1 Oct 2001 13:25:12 -0600 (MDT) Message-Id: <200110011925.f91JPC8f015412@atg.aciworldwide.com> Organization: ACI Worldwide - Advanced Technology Group X-URL: http://www.aciworldwide.com/ To: Joe Kelsey Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: Message from Joe Kelsey of "Mon, 01 Oct 2001 11:53:17 PDT." <15288.48029.798593.908820@zircon.zircon.seattle.wa.us> Date: Mon, 01 Oct 2001 13:25:12 -0600 From: Lyndon Nerenberg 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 convention was to use ``uucp'' as the default anonymous login > service. I think we're talking about two different things. Yes, many UNIX distributions shipped with a passwordless 'uucp' account with uucico as the shell. My comments about the 'nuucp' convention were referring to the publically visible anonymous UUCP sites. > Some people had the mistaken impression that there was some > sort of "hole" in the uucp system which was caused by using uucp as a > default login for uucp service. No such hole existed in modern uucico > processes, although there were bugs in early uucico (7th Edition > vintage) which may be the reason that these rumors started. I think much of this was related to the System V (R0 and R1) getty/login environment, where you could pass in arbitrary environment variables along with the login id. If your machine was poorly configured this could be used to bypass restricted shell environments. I can see where uucico shells could get lumped in with the rsh (the shell, not the network utility) environment bugs. Early uucico's were definately buggy, however I don't recall these bugs ever being exploited to compromise security. (Well, you could do DOS attacks by getting the remote uucico to drop core, leaving a LCK..site file lying around. SCO's uucico could be made to do this just by making faces at it.) > With the HoneyDanBer uucp, there were no > security holes in uucico and it was completely safe to use uucp as an > anonymous login service. I wouldn't be that absolute. No security holes were ever demonstrated, which isn't the same as saying they weren't there. (Did anyone ever breach ihnp4?) > That said, for max security it is always useful to have each site have > its own login, up to a point. Some large uucp sites used to use common > logins simply because there was so little security risk (especially with > HoneyDanBer variety). Unique logins provided fine-grained policy control. If site foo started doing bad things (deliberately or by accident) you want to be able to knock it down without taking out other functioning sites. HDB's ability to require a particular UUCP node to connect only with a specific login id was a very nice feature. (Or was it Taylor that introduced that? My memory is getting a wee bit fuzzy.) > Certainly, anonymous uucp is more secure than > anonymous ftp. For the server. The client side of the copy could definately use some work. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 12:28:10 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 5137D37B40E for ; Mon, 1 Oct 2001 12:28:07 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f91JRxH84440; Mon, 1 Oct 2001 12:27:59 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 1 Oct 2001 12:27:59 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Warner Losh Cc: current@freebsd.org Subject: whups, I lied 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, 1 Oct 2001, Matthew Jacob wrote: > > yes, with acpi timer disabled this seems to have gone away > > > Nope, even with the change Mike mentioned, I still get: microuptime() went backwards (50013.3990440 -> 50012.321555) microuptime() went backwards (50013.3990440 -> 50012.406351) microuptime() went backwards (50539.962847 -> 50539.962817) microuptime() went backwards (50675.4610692 -> 50674.977188) microuptime() went backwards (50675.4610731 -> 50675.058088) microuptime() went backwards (50820.887817 -> 50820.887763) microuptime() went backwards (51030.226497 -> 51030.226467) microuptime() went backwards (51428.4154992 -> 51427.500856) microuptime() went backwards (51497.498015 -> 51497.497964) microuptime() went backwards (51639.4064605 -> 51638.444693) microuptime() went backwards (51720.569467 -> 51720.569430) microuptime() went backwards (51794.189059 -> 51794.189005) microuptime() went backwards (52789.4037060 -> 52788.371861) microuptime() went backwards (52789.4037060 -> 52788.451444) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 12:30:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id 77FFA37B40D for ; Mon, 1 Oct 2001 12:30:22 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f91FTmL32351; Mon, 1 Oct 2001 08:29:48 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id RAA1528461; Mon, 1 Oct 2001 17:29:18 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id RAA25652; Mon, 1 Oct 2001 17:28:47 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id RAA59131; Mon, 1 Oct 2001 17:28:26 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.5/8.11.5) with ESMTP id f91FSEu04388; Mon, 1 Oct 2001 17:28:14 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Mon, 01 Oct 2001 17:28:13 +0200 Message-ID: From: "Georg-W. Koltermann" To: Scott Long Cc: current@freebsd.org Subject: Re: ACPI and APM interoperability? In-Reply-To: <20011001084910.A1952@hollin.btc.adaptec.com> References: <20011001084910.A1952@hollin.btc.adaptec.com> User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk 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 At Mon, 1 Oct 2001 08:49:10 -0600, Scott Long wrote: > > On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: > [...] > > I also was able to suspend and resume my machine (DELL Inspiron 7500) > > with APM being configured (and ACPI being active by default). Sound > > is dead after a resume, > > What sound card? Sep 28 23:38:22 hunter /boot/kernel/kernel: pcm0: port 0x1400-0x14ff irq 5 at device 8.0 on pci0 -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 12:49:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from enigma.x-telecom.net (enigma.x-telecom.net [80.70.64.51]) by hub.freebsd.org (Postfix) with ESMTP id 75B2237B40D for ; Mon, 1 Oct 2001 12:49:32 -0700 (PDT) Received: (from pal@localhost) by enigma.x-telecom.net (8.11.6/8.11.5) id f91JnGG32148 for freebsd-current@freebsd.org; Mon, 1 Oct 2001 22:49:16 +0300 (EEST) (envelope-from pal@x-telecom.net) X-Authentication-Warning: enigma.x-telecom.net: pal set sender to pal@x-telecom.net using -f Date: Mon, 1 Oct 2001 22:49:16 +0300 From: Gene Raytsin To: freebsd-current@freebsd.org Subject: broken current Message-ID: <20011001224916.F558@x-telecom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.3.22.1i 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, 44 camlib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libdisk; make beforeinstall cd /usr/src/lib/libdisk && sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libdisk.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libedit; make beforeinstall cd /usr/src/lib/libedit && sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 histedit.h /usr/obj/usr/src/i386/usr/include install: histedit.h: No such file or directory Getting this like 3d time as of today. Any ideas? Yevgeniy Raytsin | ITSP "Extreme Telecom" | phone: +380-44-2391429 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 13:27:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from shell.ataris.co.za (shell.ataris.co.za [196.15.138.40]) by hub.freebsd.org (Postfix) with ESMTP id 6679937B40A for ; Mon, 1 Oct 2001 13:27:34 -0700 (PDT) Received: from jacques by shell.ataris.co.za with local (Exim 3.33 #1) id 15o9es-0001vn-00; Mon, 01 Oct 2001 22:27:22 +0200 Date: Mon, 1 Oct 2001 22:27:22 +0200 From: Jacques To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011001222722.A2598@serenity.org.za> References: <20011001173343.D57416@sunbay.com> <200110011751.f91HpW8f014902@atg.aciworldwide.com> <200110011800.f91I0u053253@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110011800.f91I0u053253@khavrinen.lcs.mit.edu>; from Garrett Wollman on Mon, Oct 01, 2001 at 02:00:56PM -0400 X-Operating-System: FreeBSD shell.ataris.co.za 4.3-STABLE FreeBSD 4.3-STABLE 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 Oct 1 14:00:56 2001 Garrett Wollman wrote: > < said: > > > And you should *never* allow remote site UUCP logins (those that run > > uucico) under the `uucp' login, for obvious security reasons. > > I remember, back in the mists of ancient time, it was common practice > to provide ``anonymous UUCP'' service along the lines of anonymous FTP > in (what was at that time) ARPANET. I find it hard to imagine anyone > doing so today, but OTOH I find it hard to imagine anyone using UUCP > at all today, so it is obviously my imagination which has failed > rather than reality. > > -GAWollman > There are many schools in South Africa who use UUCP for their mail, since they have dial-up connections. Organisations like the Western Cape Schools' Network, and various others provide these UUCP feeds. There is a software package called Thurn (for MS-DOS) and Taxis (for Win32) which incluses the UUCP/extended software. For more informaton about taxis look @ http://www.wcape.school.za/taxis/ The UUCP solution works well in the educational environment as well as in corporate environments. YMMV. Regards --jm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 13:54:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id 459E637B403 for ; Mon, 1 Oct 2001 13:54:35 -0700 (PDT) Received: (qmail 39541 invoked by uid 1001); 1 Oct 2001 20:54:55 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15288.55327.157368.562263@zircon.zircon.seattle.wa.us> Date: Mon, 1 Oct 2001 13:54:55 -0700 To: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: <200110011925.f91JPC8f015412@atg.aciworldwide.com> References: <15288.48029.798593.908820@zircon.zircon.seattle.wa.us> <200110011925.f91JPC8f015412@atg.aciworldwide.com> X-Mailer: VM 6.92 under Emacs 20.7.1 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 Lyndon Nerenberg writes: > > The convention was to use ``uucp'' as the default anonymous login > > service. > > I think we're talking about two different things. Yes, many > UNIX distributions shipped with a passwordless 'uucp' account > with uucico as the shell. My comments about the 'nuucp' > convention were referring to the publically visible anonymous > UUCP sites. I was merely pointing out that the convention was really that both logins were in use in the public uucp community. Some sites used uucp as a login name and some sites used nuucp as a login name. It really depended on the heritage of the site and the version of uucp in use there. (I personally used both for different purposes.) > Early uucico's were definately buggy, however I don't recall these > bugs ever being exploited to compromise security. (Well, you could > do DOS attacks by getting the remote uucico to drop core, leaving > a LCK..site file lying around. SCO's uucico could be made to do > this just by making faces at it.) SCO was so far behind the state of software in so many ways. They definitely were the source of many bugs due to the fact that they had that strange mix of 7th Edition (inheirited from the Microsoft 286-unix) and bad implementations of other software. Almost as bad as HP... > > With the HoneyDanBer uucp, there were no > > security holes in uucico and it was completely safe to use uucp as an > > anonymous login service. > > I wouldn't be that absolute. No security holes were ever demonstrated, > which isn't the same as saying they weren't there. (Did anyone ever > breach ihnp4?) As far as I know, HDB was never broken at ihnp4. > HDB's ability to require a particular UUCP node to connect only with > a specific login id was a very nice feature. (Or was it Taylor that > introduced that? My memory is getting a wee bit fuzzy.) HDB introduced the PERMISSIONS file. Taylor was based on HDB specs because ATT would not release HDB to the community, in spite of pleas from all of H, D, and B. Of course, now it is all a moot point, and all of this is merely of historical (hysterical?) interest. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 14: 5:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EFED537B40D for ; Mon, 1 Oct 2001 14:05:18 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f91L4pB88026; Mon, 1 Oct 2001 17:04:52 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 1 Oct 2001 17:04:51 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jesper Skriver Cc: current@FreeBSD.org Subject: Re: Review: change NGROUPS_MAX from 16 to 64 In-Reply-To: <20010929200940.A10366@skriver.dk> 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 Note this will break binary compatibility for xucred. Note also that this may have fascinating effects in NFS environments. Note also that you'll probably want to update KI_NGROUPS also. No idea if it will affect NIS. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sat, 29 Sep 2001, Jesper Skriver wrote: > Hi, > > I'm involved in a project, where we need the ability for users to > be in more than 16 groups, on those boxes we're using the below > patch, any objections to committing it ? > > Index: sys/sys/syslimits.h > =================================================================== > RCS file: /home/ncvs/src/sys/sys/syslimits.h,v > retrieving revision 1.10 > diff -u -r1.10 syslimits.h > --- sys/sys/syslimits.h 2001/06/18 20:24:54 1.10 > +++ sys/sys/syslimits.h 2001/09/29 18:07:00 > @@ -45,7 +45,7 @@ > #define MAX_CANON 255 /* max bytes in term canon input line */ > #define MAX_INPUT 255 /* max bytes in terminal input */ > #define NAME_MAX 255 /* max bytes in a file name */ > -#define NGROUPS_MAX 16 /* max supplemental group id's */ > +#define NGROUPS_MAX 64 /* max supplemental group id's */ > #ifndef OPEN_MAX > #define OPEN_MAX 64 /* max open files per process */ > #endif > > /Jesper > > -- > Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 > Work: Network manager @ AS3292 (Tele Danmark DataNetworks) > Private: FreeBSD committer @ AS2109 (A much smaller network ;-) > > One Unix to rule them all, One Resolver to find them, > One IP to bring them all and in the zone to bind them. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 14:37:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 7D70E37B408 for ; Mon, 1 Oct 2001 14:37:29 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f91LbEZ98005; Mon, 1 Oct 2001 14:37:14 -0700 (PDT) (envelope-from obrien) Date: Mon, 1 Oct 2001 14:37:14 -0700 From: "David O'Brien" To: Gene Raytsin Cc: freebsd-current@freebsd.org Subject: Re: broken current Message-ID: <20011001143714.A97970@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20011001224916.F558@x-telecom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011001224916.F558@x-telecom.net>; from pal@x-telecom.net on Mon, Oct 01, 2001 at 10:49:16PM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote: > hi, Hi. > /usr/obj/usr/src/i386/usr/include > install: histedit.h: No such file or directory > > Getting this like 3d time as of today. > Any ideas? Yeah, do what ever you do to retrieve this mailing list; then read any new messages before sending out a "current is broken" email. If you had done that you would have known I was working on this issue. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 14:44: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from enigma.x-telecom.net (enigma.x-telecom.net [80.70.64.51]) by hub.freebsd.org (Postfix) with ESMTP id A23E737B40C; Mon, 1 Oct 2001 14:43:53 -0700 (PDT) Received: (from pal@localhost) by enigma.x-telecom.net (8.11.6/8.11.5) id f91LhpE60165; Tue, 2 Oct 2001 00:43:52 +0300 (EEST) (envelope-from pal@x-telecom.net) X-Authentication-Warning: enigma.x-telecom.net: pal set sender to pal@x-telecom.net using -f Date: Tue, 2 Oct 2001 00:43:50 +0300 From: Gene Raytsin To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: oops [was: Re: broken current] Message-ID: <20011002004349.E32284@x-telecom.net> References: <20011001224916.F558@x-telecom.net> <20011001143714.A97970@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20011001143714.A97970@dragon.nuxi.com> User-Agent: Mutt/1.3.22.1i 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, 01 Oct 2001 at 14:37:14 -0700, David O'Brien wrote: > On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote: > > hi, > > Hi. > > > /usr/obj/usr/src/i386/usr/include > > install: histedit.h: No such file or directory > > > > Getting this like 3d time as of today. > > Any ideas? > > Yeah, do what ever you do to retrieve this mailing list; then read any > new messages before sending out a "current is broken" email. > If you had done that you would have known I was working on this issue. > sorry man, my falt :( didn't mean to piss you off. and I am sorry for offtopic, ofcourse regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 14:50:47 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 ADF0637B401; Mon, 1 Oct 2001 14:50:43 -0700 (PDT) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id B21D25DAB; Mon, 1 Oct 2001 23:50:42 +0200 (CEST) Date: Mon, 1 Oct 2001 23:50:42 +0200 From: Jesper Skriver To: Robert Watson Cc: current@FreeBSD.org Subject: Re: Review: change NGROUPS_MAX from 16 to 64 Message-ID: <20011001235042.E64694@skriver.dk> References: <20010929200940.A10366@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.org on Mon, Oct 01, 2001 at 05:04:51PM -0400 X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > Note this will break binary compatibility for xucred. Note also that this > may have fascinating effects in NFS environments. Note also that you'll > probably want to update KI_NGROUPS also. No idea if it will affect NIS. As John Baldwin pointed out, it's probably not worth it, so we'll just keep it as a local diff. Thanks for your time. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 16:12:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id EAE0A37B408 for ; Mon, 1 Oct 2001 16:12:30 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f91NCRl99388; Mon, 1 Oct 2001 16:12:27 -0700 (PDT) (envelope-from obrien) Date: Mon, 1 Oct 2001 16:12:27 -0700 From: "David O'Brien" To: Gene Raytsin Cc: freebsd-current@FreeBSD.ORG Subject: Re: oops [was: Re: broken current] Message-ID: <20011001161227.A99365@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20011001224916.F558@x-telecom.net> <20011001143714.A97970@dragon.nuxi.com> <20011002004349.E32284@x-telecom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011002004349.E32284@x-telecom.net>; from pal@x-telecom.net on Tue, Oct 02, 2001 at 12:43:50AM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 02, 2001 at 12:43:50AM +0300, Gene Raytsin wrote: > and I am sorry for offtopic, ofcourse It wasn't off topic. Users of -current just have responsibilities (such as reading the freebsd-current list) before posting about a problem. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 16:52:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id C1AA937B406 for ; Mon, 1 Oct 2001 16:52:08 -0700 (PDT) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id f91NrMr26302; Mon, 1 Oct 2001 19:53:22 -0400 (EDT) (envelope-from mike) Date: Mon, 1 Oct 2001 19:53:22 -0400 From: Mike Barcroft To: Daniel Rock Cc: current@FreeBSD.ORG Subject: Re: panic in ipfw code Message-ID: <20011001195322.D22367@coffee.q9media.com> References: <3BB8A9E3.7058FBEA@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BB8A9E3.7058FBEA@t-online.de>; from D.Rock@t-online.de on Mon, Oct 01, 2001 at 07:37:39PM +0200 Organization: The FreeBSD Project 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 Daniel Rock writes: > I wondered nobody noticed this bug so far. > The kernel panics if you feed him with unnumbered firewall rules > (like "ipfw add allow all from any to any") This was reported by DES, and fixed moments before you sent out your e-mail (with a delta identical to your patch). Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 18: 8:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id BE59337B416 for ; Mon, 1 Oct 2001 18:05:31 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA10036; Tue, 2 Oct 2001 10:35:14 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.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: <200110011826.f91IQk8f015078@atg.aciworldwide.com> Date: Tue, 02 Oct 2001 10:35:14 +0930 (CST) From: "Daniel O'Connor" To: Lyndon Nerenberg Subject: Re: uucp user shell and home directory Cc: current@FreeBSD.ORG, Garrett Wollman 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-Oct-2001 Lyndon Nerenberg wrote: > UUCP still gets used. It's one of the few sane ways to handle email in > a laptop environment when you're always connecting through different > dialups/ISPs. It has mostly fallen out of favour due to ignorance and > FUD. Which is a shame, as it can still be a useful tool in certain > situations. I think a more 'modern' solution is POP or IMAP over SSH, you can also feed SMTP over an SSH tunnel too (This is what I use). --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 18:20: 4 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 DC59C37B411 for ; Mon, 1 Oct 2001 18:19:57 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA88743; Mon, 1 Oct 2001 19:12:39 -0700 (PDT) Date: Mon, 1 Oct 2001 19:12:37 -0700 (PDT) From: Julian Elischer To: "Daniel O'Connor" Cc: Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory 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 NO, POP and IMAP (I think) will lose all the envelope information, UUCP keeps that.. SMTP is a PUSH operation.. so for a PULL operation that can handle envelope information (e.g. BCC) you need UUCP On Tue, 2 Oct 2001, Daniel O'Connor wrote: > > On 01-Oct-2001 Lyndon Nerenberg wrote: > > UUCP still gets used. It's one of the few sane ways to handle email in > > a laptop environment when you're always connecting through different > > dialups/ISPs. It has mostly fallen out of favour due to ignorance and > > FUD. Which is a shame, as it can still be a useful tool in certain > > situations. > > I think a more 'modern' solution is POP or IMAP over SSH, you can also feed > SMTP over an SSH tunnel too (This is what I use). > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 18:34: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 184C737B401 for ; Mon, 1 Oct 2001 18:34:03 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA10423; Tue, 2 Oct 2001 11:03:42 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.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: Tue, 02 Oct 2001 11:03:42 +0930 (CST) From: "Daniel O'Connor" To: Julian Elischer Subject: Re: uucp user shell and home directory Cc: Garrett Wollman , current@FreeBSD.ORG, Lyndon Nerenberg 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-Oct-2001 Julian Elischer wrote: > POP and IMAP (I think) will lose all the envelope information, > > UUCP keeps that.. What use is it? I don't know what I'm missing... > SMTP is a PUSH operation.. I meant that I tunnel SMTP back to my work to send email from a foreign location. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 18:36:46 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 2796137B413 for ; Mon, 1 Oct 2001 18:36:39 -0700 (PDT) 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 f921abu71131; Mon, 1 Oct 2001 19:36:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f921ab709436; Mon, 1 Oct 2001 19:36:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110020136.f921ab709436@harmony.village.org> To: Scott Long Subject: Re: ACPI and APM interoperability? Cc: "Georg-W. Koltermann" , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 01 Oct 2001 08:49:10 MDT." <20011001084910.A1952@hollin.btc.adaptec.com> References: <20011001084910.A1952@hollin.btc.adaptec.com> Date: Mon, 01 Oct 2001 19:36:37 -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 <20011001084910.A1952@hollin.btc.adaptec.com> Scott Long writes: : On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: : > Hi, : > : > I'm wondering how I should handle APM now that ACPI has basically : > taken over power management responsibility. : : APM and ACPI are mutually exclusive from what I understand. You should : remove the apm device from your kernel config. I've been able to run both with my VAIO. However, my VAIO hangs randomly with ACPI enabled (even when i have apm disable). : > It seems I still need to configure APM so that /dev/apm is there and : > battery monitoring utilities like the GNOME battery_applet can work. : : Battery, temp, etc, can be monitored via the hw.acpi sysctl tree. : Someone will have to do the required conversion to the various APM : utilities is GNOME and whatever else. Hmmm. That's good to know. I didn't know that until now. I'll have to reboot my vaio to see how good/bad this information is. : > I also was able to suspend and resume my machine (DELL Inspiron 7500) : > with APM being configured (and ACPI being active by default). Sound : > is dead after a resume, : : What sound card? : : > PCMCIA is dead after a couple of resumes, : : Resource leak? Warner? I don't see this with my Inspiron 8000, so I don't care :-). Seriously, I'm still running stable on my i8000. I'll be cutting over in a little bit (I can dual boot it now), so that will be less of an issue going forward. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 18:42:22 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 70C5337B411 for ; Mon, 1 Oct 2001 18:42:18 -0700 (PDT) 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 f921gHu71159; Mon, 1 Oct 2001 19:42:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f921gE709493; Mon, 1 Oct 2001 19:42:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110020142.f921gE709493@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: ACPI and APM interoperability? Cc: scott_long@btc.adaptec.com, gwk@sgi.com, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 02 Oct 2001 02:04:31 +0900." <20011002.020431.25420279.iwasaki@jp.FreeBSD.org> References: <20011002.020431.25420279.iwasaki@jp.FreeBSD.org> <20011001084910.A1952@hollin.btc.adaptec.com> Date: Mon, 01 Oct 2001 19:42:14 -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 <20011002.020431.25420279.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: : Generalized power-management interface API to have compatibility with : APM and ACPI also is suggested long time ago; : http://www.freebsd.org/cgi/getmsg.cgi?fetch=403390+406841+/usr/local/www/db/text/2001/freebsd-current/20010114.freebsd-current I still have this message in my inbox :-). I liked the API presented in it. : Device node for ACPI is discussed bofore too; having only one /dev/acpi : or having generalized nodes for each device types such as /dev/battery0 : but we couldn't reach the conclusion, now discussion stops... I like what we do with the sound system. There's only /dev/dsp0 for people that want blast sound. Under the covers the sound system hooks up the drivers to that device. I think that doing /dev/battery would be a good idea. Doing device plumbing like this isn't too bad with newbus. Just make the battery device attach at either the acpi or apm devices. I'm doing something similar right now with a FM USB Radio driver I'm writing. I'm bringing Video 4 Linux API into the tree (assuming I don't get shot first) because there are so many cool progrms that work with that which don't work with FreeBSD. : Any suggestions on it? Once we get the conclusion, we can start developing : API and convert userland tools. What other APIs are available? Do they fit our needs? What does Linux or NetBSD do here? Anything interesting? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 19:10:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E85C437B40D; Mon, 1 Oct 2001 19:10:48 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare/smtpfeed 1.14) with ESMTP/inet id f922Akm80194; Tue, 2 Oct 2001 11:10:46 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 02 Oct 2001 11:10:45 +0900 (JST) Message-Id: <20011002.111045.78762705.iwasaki@jp.FreeBSD.org> To: sobomax@FreeBSD.org Cc: ache@nagual.pp.ru, msmith@FreeBSD.org, current@FreeBSD.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation From: Mitsuru IWASAKI In-Reply-To: <20011002.023158.71143343.iwasaki@jp.FreeBSD.org> References: <20011002.005340.74695085.iwasaki@jp.FreeBSD.org> <3BB89FA1.DD75D31C@FreeBSD.org> <20011002.023158.71143343.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) 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 Hi, I've just made a workaround for this. Intel folks, could you review it as always? > The problem is here, right? > > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT > > I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some > problems (not sure in BIOS or ACPICA yet). I could reproduce the problem > which you reported. Trace attached in this mail. [snip] > dsopcode-0677 [09] DsEvalBufferFieldOpera: Field size 208 exceeds Buffer size 192 (bits) > PsExecute: method failed - \_SB_.PCI0.ISA_.FDC0._CRS (0x8098fa8) > Execution of \_SB_.PCI0.ISA_.FDC0._CRS failed with status AE_AML_BUFFER_LIMIT This method is like this; Method(_CRS) { Name(BUF0, Buffer(0x18) {0x47, 0x1, 0xf2, 0x3, 0xf2, 0x3, 0x0, 0x4, 0x47, 0x1, 0xf7, 0x3, 0xf7, 0x3, 0x0, 0x1, 0x22, 0x40, 0x0, 0x2a, 0x4, 0x0, 0x79, 0x0 }) CreateByteField(BUF0, 0x2, IOLO) CreateByteField(BUF0, 0x3, IOHI) CreateByteField(BUF0, 0x4, IORL) CreateByteField(BUF0, 0x5, IORH) CreateByteField(BUF0, 0x19, IRQL) CreateByteField(BUF0, 0x1c, DMAV) Return(BUF0) } The problem is that this AML is trying to create a field at exceeded position (0x19) of the Buffer (size is 0x18). I couldn't find how AML interprepter treat this in ACPI Spec. so I'm not sure wether AWRDACPI violates the Spec. or ACPICA can have a workaround for this. Anyway, I made a patch to reallocate a large enough buffer for the requested operation. Thanks Index: dsopcode.c =================================================================== RCS file: /home/ncvs/src/sys/contrib/dev/acpica/dsopcode.c,v retrieving revision 1.1.1.10 diff -u -r1.1.1.10 dsopcode.c --- dsopcode.c 7 Sep 2001 01:22:24 -0000 1.1.1.10 +++ dsopcode.c 1 Oct 2001 18:58:41 -0000 @@ -615,11 +615,24 @@ if ((BitOffset + BitCount) > (8 * (UINT32) SrcDesc->Buffer.Length)) { + UINT32 Length; + UINT8 *Pointer; + ACPI_DEBUG_PRINT ((ACPI_DB_ERROR, "Field size %d exceeds Buffer size %d (bits)\n", BitOffset + BitCount, 8 * (UINT32) SrcDesc->Buffer.Length)); - Status = AE_AML_BUFFER_LIMIT; - goto Cleanup; + Length = ((BitOffset + BitCount) / 8) + + (((BitOffset + BitCount) % 8) ? 1 : 0); + Pointer = ACPI_MEM_CALLOCATE (Length); + if (!Pointer) + { + Status = AE_NO_MEMORY; + goto Cleanup; + } + MEMCPY (Pointer, SrcDesc->Buffer.Pointer, SrcDesc->Buffer.Length); + ACPI_MEM_FREE (SrcDesc->Buffer.Pointer); + SrcDesc->Buffer.Pointer = Pointer; + SrcDesc->Buffer.Length = Length; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 20:25:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 1B2C437B40C for ; Mon, 1 Oct 2001 20:25:39 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f923Yv306335; Mon, 1 Oct 2001 20:34:57 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110020334.f923Yv306335@mass.dis.org> To: Warner Losh Cc: Scott Long , "Georg-W. Koltermann" , current@FreeBSD.ORG Subject: Re: ACPI and APM interoperability? In-Reply-To: Message from Warner Losh of "Mon, 01 Oct 2001 19:36:37 MDT." <200110020136.f921ab709436@harmony.village.org> Date: Mon, 01 Oct 2001 20:34:57 -0700 From: Mike Smith 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 > : APM and ACPI are mutually exclusive from what I understand. You should > : remove the apm device from your kernel config. > > I've been able to run both with my VAIO. However, my VAIO hangs > randomly with ACPI enabled (even when i have apm disable). You shouldn't be able to do this. 8) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 1 20:27: 8 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 C475437B40C; Mon, 1 Oct 2001 20:27:05 -0700 (PDT) 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 f923R4u71471; Mon, 1 Oct 2001 21:27:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f923R3710058; Mon, 1 Oct 2001 21:27:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110020327.f923R3710058@harmony.village.org> To: Mike Smith Subject: Re: ACPI and APM interoperability? Cc: Scott Long , "Georg-W. Koltermann" , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 01 Oct 2001 20:34:57 PDT." <200110020334.f923Yv306335@mass.dis.org> References: <200110020334.f923Yv306335@mass.dis.org> Date: Mon, 01 Oct 2001 21:27:03 -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 <200110020334.f923Yv306335@mass.dis.org> Mike Smith writes: : > : APM and ACPI are mutually exclusive from what I understand. You should : > : remove the apm device from your kernel config. : > : > I've been able to run both with my VAIO. However, my VAIO hangs : > randomly with ACPI enabled (even when i have apm disable). : : You shouldn't be able to do this. 8) Like I said, it worked great, apart from the hangs. Maybe I have an evil, mutant BIOS. I'll have to upgrade to slam my fingers in the door more effectively :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 1: 2:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 8B4FA37B40A for ; Tue, 2 Oct 2001 01:02:22 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f9281kc82645; Tue, 2 Oct 2001 11:01:46 +0300 (EEST) (envelope-from ru) Date: Tue, 2 Oct 2001 11:01:46 +0300 From: Ruslan Ermilov To: Lyndon Nerenberg Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011002110145.F74839@sunbay.com> References: <200110011751.f91HpW8f014902@atg.aciworldwide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110011751.f91HpW8f014902@atg.aciworldwide.com>; from lyndon@atg.aciworldwide.com on Mon, Oct 01, 2001 at 11:51:32AM -0600 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, Oct 01, 2001 at 11:51:32AM -0600, Lyndon Nerenberg wrote: > >>>>> "Ruslan" == Ruslan Ermilov writes: > > Ruslan> It doesn't really matter what the home directory is set to > Ruslan> (IIRC), but the shell must be uucico(8). > > No, this is wrong on both counts. > > By convention, the home directory of the uucp login has corresponded > to the UUCP PUBDIR. Traditionally this was /usr/spool/uucppublic, and > maps to /var/spool/uucppublic these days. Thus, if I wanted to > copy a file to the public file area on machine b I would incant > > uucp file b!~ > > and the uucico on the remote end would expand the '~' to > /usr/spool/uucppublic. > Of course I know what the /var/spool/uucppublic is for, but it's not controlled by "uucp" account in FreeBSD. It's controlled by the "pubdir" UUCP config option, that's why "it doesn't really matter". > This usage predates (and probably inspired) the common behavior of > current shells handling of '~' expansion. While no modern UUCP I'm > aware of uses the value of pw->pw_dir to derive PUBDIR, POLA would > imply that the interpretation of '~uucp' should be the same for > both the uucp(1) command and for shells that do ~ expansion. Therefore > I would recommend keeping the UUCP home directory as /var/spool/uucppublic. > If you want to be paranoid you make this directory owned by root.wheel > and mode 0555 without breaking anything. > The problem is that "uucp" account should stay, but the creation of this directory should be moved to ports. And we don't want "uucp" account with non-existing homedir. > As for the `uucp' account's shell, this should be set to > /sbin/nologin. The purpose of the uucp entry in /etc/passwd is to > provide a unique runtime uid for the setuid UUCP components. Note that > there are some periodic maintenance scripts that should be run if you > actively use UUCP. These traditionally run under the `uucp' identity, > so you need to make sure that they will continue to function with > /sbin/nologin. (Which they should, otherwise they would have barfed > with uucico as the shell.) The shell for the uucp account should most > certainly NOT be uucico! And you should *never* allow remote site UUCP > logins (those that run uucico) under the `uucp' login, for obvious > security reasons. Instead, create seperate unique logins for each > remote site, just as you would for each of your shell accounts, but > set the login shell to uucico. > Oh, you obviously replied too quickly. This is exactly what I wrote in my email. I just tried to explain "historical behavior" at the start of my message, and you were confused by not reading my mail entirely. 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 Oct 2 1:15:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 6D12937B408; Tue, 2 Oct 2001 01:15:46 -0700 (PDT) Received: from vega.vega.com (h178.229.dialup.iptcom.net [212.9.229.178]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA77243; Tue, 2 Oct 2001 11:14:49 +0300 (EEST) (envelope-from max@vega.com) Received: (from max@localhost) by vega.vega.com (8.11.6/8.11.3) id f928EHV73680; Tue, 2 Oct 2001 11:14:17 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200110020814.f928EHV73680@vega.vega.com> Subject: Re: ACPI: problem with fdc resource allocation To: iwasaki@jp.FreeBSD.org (Mitsuru IWASAKI) Date: Tue, 2 Oct 2001 11:13:37 +0300 (EEST) Cc: sobomax@FreeBSD.ORG, ache@nagual.pp.ru, msmith@FreeBSD.ORG, current@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org In-Reply-To: from "Mitsuru IWASAKI" at Oct 02, 2001 11:10:45 AM X-Mailer: ELM [version 2.5 PL5] 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 > > Hi, I've just made a workaround for this. Intel folks, could you review > it as always? > > > The problem is here, right? > > > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT > > > > I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some > > problems (not sure in BIOS or ACPICA yet). I could reproduce the problem > > which you reported. Trace attached in this mail. > [snip] > > dsopcode-0677 [09] DsEvalBufferFieldOpera: Field size 208 exceeds Buffer size 192 (bits) > > PsExecute: method failed - \_SB_.PCI0.ISA_.FDC0._CRS (0x8098fa8) > > Execution of \_SB_.PCI0.ISA_.FDC0._CRS failed with status AE_AML_BUFFER_LIMIT > > This method is like this; > Method(_CRS) { > Name(BUF0, Buffer(0x18) {0x47, 0x1, 0xf2, 0x3, 0xf2, 0x3, > 0x0, 0x4, 0x47, 0x1, 0xf7, 0x3, 0xf7, 0x3, 0x0, > 0x1, 0x22, 0x40, 0x0, 0x2a, 0x4, 0x0, 0x79, 0x0 }) > CreateByteField(BUF0, 0x2, IOLO) > CreateByteField(BUF0, 0x3, IOHI) > CreateByteField(BUF0, 0x4, IORL) > CreateByteField(BUF0, 0x5, IORH) > CreateByteField(BUF0, 0x19, IRQL) > CreateByteField(BUF0, 0x1c, DMAV) > Return(BUF0) > } > > The problem is that this AML is trying to create a field at exceeded > position (0x19) of the Buffer (size is 0x18). > I couldn't find how AML interprepter treat this in ACPI Spec. so I'm > not sure wether AWRDACPI violates the Spec. or ACPICA can have a workaround > for this. > Anyway, I made a patch to reallocate a large enough buffer for the > requested operation. Yes, that patch fixed the problem, thank you! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 1:21:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id 9DDAA37B405 for ; Tue, 2 Oct 2001 01:21:55 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f928LsL08305 for <@rj.corp.sgi.com:current@freebsd.org>; Tue, 2 Oct 2001 01:21:54 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA1598147 for <@eugate.sgi.com:current@freebsd.org>; Tue, 2 Oct 2001 10:21:26 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA10991; Tue, 2 Oct 2001 10:21:23 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA66441; Tue, 2 Oct 2001 10:21:08 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.6/8.11.6) with ESMTP id f928KmS01419; Tue, 2 Oct 2001 10:20:49 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Tue, 02 Oct 2001 10:20:48 +0200 Message-ID: From: "Georg-W. Koltermann" To: current@freebsd.org Subject: VMWare2 permission problems on -current as of Sep 26 User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk 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 Hi, I have applied the KSE patches to vmware2 that were posted on http://www.ripe.net/home/mark/files/vmware2_kse.patch.tgz. I can now build vmware2, but run into a number of permission problems running it: 1. Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: :0 Can be worked around by "chmod 644 ~/.Xauthority". 2. Cannot open /dev/tty0: permission denied (in a GUI message box). Linux /dev/tty0 seems to refer to FreeBSD /dev/ttyv0, using a chain of two symlinks. "chown $USER /dev/ttyv0" doesn't seem to be effective, but "chmod 666 /dev/ttyv0" makes the message go away. 3. Active virtual terminal (/dev/tty9) is not valid. Permission denied. (in a GUI message box). Seems to be like the above, Linux tty9 is really FreeBSD ttyv8, and a chown is ineffective but a chmod 666 solves it. 4. Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed on stderr. Don't know if this is a problem or just a warning. 5. Permission error creating lockfiles (vmware-lock.whoever) The directory is owned by me. In summary, it seems as though the vmware binary (which is SUID root) is unable to access any files that are only accessible to the invoking user (like .Xauthority), and also unable to access any files accessible by root (like the /dev nodes). Is there a kind of changed permission policy in the new linuxulator that could cause this? By any chance, would I need to recompile the linux_base port? Is anyone using VMWare2 successfully on a recent -current? -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 1:52: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 2767237B40D; Tue, 2 Oct 2001 01:52:11 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f928q7V89863; Tue, 2 Oct 2001 11:52:07 +0300 (EEST) (envelope-from ru) Date: Tue, 2 Oct 2001 11:52:06 +0300 From: Ruslan Ermilov To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Review: change NGROUPS_MAX from 16 to 64 Message-ID: <20011002115206.M74839@sunbay.com> References: <20010929200940.A10366@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Mon, Oct 01, 2001 at 05:04:51PM -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 What's the reason why KI_NGROUPS should be different from NGROUPS_MAX? On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > Note this will break binary compatibility for xucred. Note also that this > may have fascinating effects in NFS environments. Note also that you'll > probably want to update KI_NGROUPS also. No idea if it will affect NIS. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services -- 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 Oct 2 2: 8:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.cicely.de (ppp105.uni-duisburg.de [134.91.19.105]) by hub.freebsd.org (Postfix) with ESMTP id 4E08937B40C for ; Tue, 2 Oct 2001 02:08:08 -0700 (PDT) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f9297oB26606; Tue, 2 Oct 2001 11:07:50 +0200 (CEST) Date: Tue, 2 Oct 2001 11:07:50 +0200 From: Bernd Walter To: Julian Elischer Cc: "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory Message-ID: <20011002110750.B24680@cicely20.cicely.de> 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 julian@elischer.org on Mon, Oct 01, 2001 at 07:12:37PM -0700 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc 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, Oct 01, 2001 at 07:12:37PM -0700, Julian Elischer wrote: > NO, > > POP and IMAP (I think) will lose all the envelope information, There are ugly methods of puting these into extended header. I don't like it. > UUCP keeps that.. > > SMTP is a PUSH operation.. Not neccesarily - there are poll type operations, which are beleaved to be dangerous, because you never know who you realy sending the mails. But with todays SMTP AUTH and SSL Authentication it may be trustfull again. > so for a PULL operation that can handle envelope information (e.g. BCC) > you need UUCP That's the reason why I'm currently using UUCP. > On Tue, 2 Oct 2001, Daniel O'Connor wrote: > > > > > On 01-Oct-2001 Lyndon Nerenberg wrote: > > > UUCP still gets used. It's one of the few sane ways to handle email in > > > a laptop environment when you're always connecting through different > > > dialups/ISPs. It has mostly fallen out of favour due to ignorance and > > > FUD. Which is a shame, as it can still be a useful tool in certain > > > situations. > > > > I think a more 'modern' solution is POP or IMAP over SSH, you can also feed > > SMTP over an SSH tunnel too (This is what I use). Over SSH is possible. But UUCP is also independend from an IP connection and can run on nearly every bidirectional communication channel - even loosy. And UUCP restarts a dropped transmission exactly where it stopped and doesn't try to retransmit the complete message. There are still uses for UUCP. E.g. I'm doing printing over UUCP from my notebook. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 2:23:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E3C2637B407 for ; Tue, 2 Oct 2001 02:23:44 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA15658; Tue, 2 Oct 2001 18:53:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.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: <20011002110750.B24680@cicely20.cicely.de> Date: Tue, 02 Oct 2001 18:53:27 +0930 (CST) From: "Daniel O'Connor" To: Bernd Walter Subject: Re: uucp user shell and home directory Cc: Garrett Wollman , current@FreeBSD.ORG, Lyndon Nerenberg , Julian Elischer 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-Oct-2001 Bernd Walter wrote: > But UUCP is also independend from an IP connection and can run on > nearly every bidirectional communication channel - even loosy. > And UUCP restarts a dropped transmission exactly where it stopped > and doesn't try to retransmit the complete message. > > There are still uses for UUCP. > E.g. I'm doing printing over UUCP from my notebook. I'm not saying there aren't, just curious as to what it gets used for :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 4:45:32 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 EC6B337B401; Tue, 2 Oct 2001 04:45:22 -0700 (PDT) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f92BjD5518593; Tue, 2 Oct 2001 20:45:13 +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 f92BjDQ401490; Tue, 2 Oct 2001 20:45:13 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:NGN9Zf6rq3Jf2DK4lXd370xbzXfSDjp9@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 UAA10794; Tue, 2 Oct 2001 20:55:08 +0900 (JST) Message-Id: <200110021155.UAA10794@zodiac.mech.utsunomiya-u.ac.jp> To: phk@freebsd.org, current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: log(9) bug? or feature? Date: Tue, 02 Oct 2001 20:55:07 +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 In /sys/kern/subr_prf.c rev 1.66 and earlier, log(9) printed the message to the log buffer if the log buffer is being read by a process (syslogd). If no process is reading the log buffer, the message went to BOTH the log buffer and the console, as documented in the comment just above log(9). /* * Log writes to the log buffer, and guarantees not to sleep (so can be * called by interrupt routines). If there is no process reading the * log yet, it writes to the console also. */ void log(int level, const char *fmt, ...) { [...] In rev 1.67 and later, the message goes to the log buffer only if a process is reading the log buffer. If no process is reading, the message goes to the console ONLY, and it is not put into the log buffer. This behavior is inconsistent with the above comment. Is this a bug introduced in rev 1.67, or is it the intended new behavior and the comment is out of date? The following patch will print the message to BOTH the log buffer and the console if no process is reading the log buffer. Kazu Index: subr_prf.c =================================================================== RCS file: /src/CVS/src/sys/kern/subr_prf.c,v retrieving revision 1.72 diff -u -r1.72 subr_prf.c --- subr_prf.c 12 Sep 2001 08:37:45 -0000 1.72 +++ subr_prf.c 2 Oct 2001 11:37:31 -0000 @@ -194,7 +196,7 @@ pca.tty = NULL; pca.pri = level; - pca.flags = log_open ? TOLOG : TOCONS; + pca.flags = log_open ? TOLOG : (TOLOG | TOCONS); va_start(ap, fmt); retval = kvprintf(fmt, putchar, &pca, 10, ap); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 5:13: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 630B037B409; Tue, 2 Oct 2001 05:13:00 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f92CCjB97521; Tue, 2 Oct 2001 08:12:45 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 2 Oct 2001 08:12:45 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: Review: change NGROUPS_MAX from 16 to 64 In-Reply-To: <20011002115206.M74839@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, 2 Oct 2001, Ruslan Ermilov wrote: > What's the reason why KI_NGROUPS should be different from NGROUPS_MAX? None -- ideally, they would be the same. I was reminding him that if he updated one, he should be sure to update the other. > On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > > > Note this will break binary compatibility for xucred. Note also that this > > may have fascinating effects in NFS environments. Note also that you'll > > probably want to update KI_NGROUPS also. No idea if it will affect NIS. > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > > robert@fledge.watson.org NAI Labs, Safeport Network Services > > -- > 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 Oct 2 5:15:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from day.anthologeek.net (day.anthologeek.net [212.43.217.20]) by hub.freebsd.org (Postfix) with ESMTP id 2710037B40A for ; Tue, 2 Oct 2001 05:15:31 -0700 (PDT) Received: by day.anthologeek.net (Postfix, from userid 1000) id A5B51171E9; Tue, 2 Oct 2001 14:14:41 +0200 (CEST) Date: Tue, 2 Oct 2001 14:14:41 +0200 From: Sameh Ghane To: freebsd-current@freebsd.org Subject: XFree 4 DRM/DRI under -CURRENT Message-ID: <20011002141441.A93483@anthologeek.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Keys: 0x1289F00D: 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, Did anyone find a way to compile the x11-servers/XFree86-4-Server port ? According to the Makefile it is not possible to build it since FreeBSD 500013. Will a package built under < 500013 work under > 500013 ? Another way to have DRI/M rendering with mga/G400 and XFree under -current ? Cheers, -- Sameh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 5:19:22 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 9783537B408; Tue, 2 Oct 2001 05:19:11 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f92CH7f21500; Tue, 2 Oct 2001 15:17:07 +0300 (EEST) (envelope-from ru) Date: Tue, 2 Oct 2001 15:17:07 +0300 From: Ruslan Ermilov To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Review: change NGROUPS_MAX from 16 to 64 Message-ID: <20011002151707.D18632@sunbay.com> References: <20011002115206.M74839@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 rwatson@FreeBSD.ORG on Tue, Oct 02, 2001 at 08:12:45AM -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 Probably, the reason is to still have a working KINFO_PROC_SIZE even if the user modifies NGROUPS_MAX? On Tue, Oct 02, 2001 at 08:12:45AM -0400, Robert Watson wrote: > > On Tue, 2 Oct 2001, Ruslan Ermilov wrote: > > > What's the reason why KI_NGROUPS should be different from NGROUPS_MAX? > > None -- ideally, they would be the same. I was reminding him that if he > updated one, he should be sure to update the other. > > > On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > > > > > Note this will break binary compatibility for xucred. Note also that this > > > may have fascinating effects in NFS environments. Note also that you'll > > > probably want to update KI_NGROUPS also. No idea if it will affect NIS. -- 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 Oct 2 5:20:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from theinternet.com.au (co3040619-a.kelvn1.qld.optushome.com.au [203.164.207.8]) by hub.freebsd.org (Postfix) with ESMTP id 84C1837B407 for ; Tue, 2 Oct 2001 05:20:41 -0700 (PDT) Received: (from akm@localhost) by theinternet.com.au (8.11.6/8.11.4) id f92CKRW09655; Tue, 2 Oct 2001 22:20:27 +1000 (EST) (envelope-from akm) Date: Tue, 2 Oct 2001 22:20:27 +1000 From: Andrew Kenneth Milton To: Sameh Ghane Cc: freebsd-current@FreeBSD.ORG Subject: Re: XFree 4 DRM/DRI under -CURRENT Message-ID: <20011002222027.B751@zeus.theinternet.com.au> References: <20011002141441.A93483@anthologeek.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20011002141441.A93483@anthologeek.net>; from Sameh Ghane on Tue, Oct 02, 2001 at 02:14:41PM +0200 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 +-------[ Sameh Ghane ]---------------------- | Hi, | | Did anyone find a way to compile the x11-servers/XFree86-4-Server port ? | | According to the Makefile it is not possible to build it since FreeBSD 500013. | Will a package built under < 500013 work under > 500013 ? It's busted since the KSE changes went in, the changes are fairly easy to do, but, it involves a crapload of #ifdefing to do it properly... The pre 500013 kernel modules will not work for you, they will panic your system as soon as you try to access them d;) They're on my list of things to do someday if someone hasn't done them, by the time I get around to it. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 8:34:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id D097737B40B for ; Tue, 2 Oct 2001 08:34:34 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA09859; Tue, 2 Oct 2001 09:34:19 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA21065; Tue, 2 Oct 2001 09:34:18 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15289.56953.709463.415400@nomad.yogotech.com> Date: Tue, 2 Oct 2001 09:34:17 -0600 To: Julian Elischer Cc: "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: References: X-Mailer: VM 6.95 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > POP and IMAP (I think) will lose all the envelope information, You've been listening to Terry too long. It's certainly not the case, although I've decided to quit arguing with Terry, since it's an excercise in futility. No matter what you say, he'll either change the subject or simply overwhelm you with useless/unrelated material until you simply abandon any hope of trying to give out useful information. > SMTP is a PUSH operation.. > > so for a PULL operation that can handle envelope information (e.g. BCC) > you need UUCP See above. fetchmail + pop works fine. I've been get all of my envelope information, and there is no worries. For 'fetching' email, fetchmail is a very good solution. However, there is also another fairly trivial solution that works well, *IF* you have a static IP address. ETRN also is a good 'fetch' mechanism, if your ISP sets up MX records for you. When you come up, you simply telnet into your ISP's mail server, then type 'ETRN foobar.com', and it'll dump all your email to the IP address of your static configuration. However, this won't work for roving users. Nate > > On Tue, 2 Oct 2001, Daniel O'Connor wrote: > > > > > On 01-Oct-2001 Lyndon Nerenberg wrote: > > > UUCP still gets used. It's one of the few sane ways to handle email in > > > a laptop environment when you're always connecting through different > > > dialups/ISPs. It has mostly fallen out of favour due to ignorance and > > > FUD. Which is a shame, as it can still be a useful tool in certain > > > situations. > > > > I think a more 'modern' solution is POP or IMAP over SSH, you can also feed > > SMTP over an SSH tunnel too (This is what I use). > > > > --- > > Daniel O'Connor software and network engineer > > for Genesis Software - http://www.gsoft.com.au > > "The nice thing about standards is that there > > are so many of them to choose from." > > -- Andrew Tanenbaum > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > 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 Oct 2 8:36:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 907B737B406; Tue, 2 Oct 2001 08:36:37 -0700 (PDT) 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 BAA09193; Wed, 3 Oct 2001 01:36:29 +1000 Date: Wed, 3 Oct 2001 01:35:51 +1000 (EST) From: Bruce Evans X-X-Sender: To: Ruslan Ermilov Cc: Robert Watson , Subject: Re: Review: change NGROUPS_MAX from 16 to 64 In-Reply-To: <20011002115206.M74839@sunbay.com> Message-ID: <20011003012734.P89444-100000@delplex.bde.org> 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, 2 Oct 2001, Ruslan Ermilov wrote: > What's the reason why KI_NGROUPS should be different from NGROUPS_MAX? > > On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > > > Note this will break binary compatibility for xucred. Note also that this > > may have fascinating effects in NFS environments. Note also that you'll > > probably want to update KI_NGROUPS also. No idea if it will affect NIS. Because some constants are more constants than others :-). The layout of the user struct is constant, so changing NGROUPS_MAX must not affect it. My version of makes these constants more obviously constant: Index: user.h =================================================================== RCS file: /home/ncvs/src/sys/sys/user.h,v retrieving revision 1.44 diff -u -2 -r1.44 user.h --- user.h 13 Sep 2001 22:52:41 -0000 1.44 +++ user.h 27 Sep 2001 18:52:42 -0000 @@ -36,10 +36,10 @@ #ifndef _SYS_USER_H_ -#define _SYS_USER_H_ +#define _SYS_USER_H_ -#include #ifndef _KERNEL /* stuff that *used* to be included by user.h, or is now needed */ #include +#include #include #include @@ -49,4 +49,7 @@ #include #include + +#include + #include /* XXX */ #include /* XXX */ @@ -54,4 +57,5 @@ #include /* XXX */ #endif /* !_KERNEL */ + #ifndef _SYS_RESOURCEVAR_H_ #include @@ -74,29 +78,28 @@ * fill_kinfo_proc and in lib/libkvm/kvm_proc.c in the function kvm_proclist. */ -#ifdef __alpha__ -#define KINFO_PROC_SIZE 912 /* the correct size for kinfo_proc */ +#ifdef __alpha__ +#define KINFO_PROC_SIZE 912 #endif -#ifdef __ia64__ -#define KINFO_PROC_SIZE 888 +#ifdef __ia64__ +#define KINFO_PROC_SIZE 888 #endif -#ifdef __i386__ -#define KINFO_PROC_SIZE 648 /* the correct size for kinfo_proc */ +#ifdef __i386__ +#define KINFO_PROC_SIZE 648 #endif -#ifdef __powerpc__ +#ifdef __powerpc__ #define KINFO_PROC_SIZE 656 #endif -#ifdef __sparc64__ +#ifdef __sparc64__ #define KINFO_PROC_SIZE 888 #endif -#ifndef KINFO_PROC_SIZE +#ifndef KINFO_PROC_SIZE #error "Unknown architecture" #endif -#define WMESGLEN 8 /* size of returned wchan message */ -#define MTXNAMELEN 8 /* size of returned mutex name */ -#define OCOMMLEN 16 /* size of returned ki_ocomm name */ -#define COMMLEN 19 /* size of returned ki_comm name */ -#define KI_NGROUPS 16 /* number of groups in ki_groups */ -#define LOGNAMELEN 17 /* size of returned ki_login */ +/* + * Note: the magic numbers for the array sizes are mostly the numbers that + * were exactly the right size when this binary interface was designed. + * E.g., 16 in the declaration of ki_ocomm[] is the old value of MAXCOMLEN. + */ struct kinfo_proc { int ki_structsize; /* size of this structure */ @@ -128,5 +131,5 @@ gid_t ki_svgid; /* Saved effective group id */ short ki_ngroups; /* number of groups */ - gid_t ki_groups[KI_NGROUPS]; /* groups */ + gid_t ki_groups[16]; /* groups */ vm_size_t ki_size; /* virtual size */ segsz_t ki_rssize; /* current resident set size in pages */ @@ -153,9 +156,9 @@ u_char ki_oncpu; /* Which cpu we are on */ u_char ki_lastcpu; /* Last cpu we were on */ - char ki_ocomm[OCOMMLEN+1]; /* command name */ - char ki_wmesg[WMESGLEN+1]; /* wchan message */ - char ki_login[LOGNAMELEN+1]; /* setlogin name */ - char ki_mtxname[MTXNAMELEN+1]; /* mutex name */ - char ki_comm[COMMLEN+1]; /* command name */ + char ki_ocomm[16 + 1]; /* command name */ + char ki_wmesg[8 + 1]; /* wchan message */ + char ki_login[17 + 1]; /* setlogin name */ + char ki_mtxname[8 + 1]; /* mutex name */ + char ki_comm[19 + 1]; /* command name */ char ki_sparestrings[85]; /* spare string space */ struct rusage ki_rusage; /* process rusage statistics */ @@ -167,4 +170,5 @@ long ki_spare[22]; /* spare constants */ }; + void fill_kinfo_proc __P((struct proc *, struct kinfo_proc *)); @@ -180,16 +184,14 @@ * in all processes. */ - struct user { - struct sigacts u_sigacts; /* *p_sigacts */ - struct pstats u_stats; /* *p_stats */ + struct sigacts u_sigacts; /* p_sigacts points here (use it!) */ + struct pstats u_stats; /* p_stats points here (use it!) */ /* - * Remaining fields only for - * core dump and/or ptrace-- + * Remaining fields only for core dump and/or ptrace-- * not valid at other times! + * XXX also valid for data returned by certain sysctls... */ - struct kinfo_proc u_kproc; /* eproc */ - struct md_coredump u_md; /* glop */ + struct kinfo_proc u_kproc; }; -#endif +#endif /* !_SYS_USER_H_ */ Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 9:18:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.cicely.de (ppp108.uni-duisburg.de [134.91.19.108]) by hub.freebsd.org (Postfix) with ESMTP id AD19637B406 for ; Tue, 2 Oct 2001 09:18:50 -0700 (PDT) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f92GITS27373; Tue, 2 Oct 2001 18:18:29 +0200 (CEST) Date: Tue, 2 Oct 2001 18:18:29 +0200 From: Bernd Walter To: Nate Williams Cc: Julian Elischer , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory Message-ID: <20011002181829.A27231@cicely20.cicely.de> References: <15289.56953.709463.415400@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15289.56953.709463.415400@nomad.yogotech.com>; from nate@yogotech.com on Tue, Oct 02, 2001 at 09:34:17AM -0600 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc 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, Oct 02, 2001 at 09:34:17AM -0600, Nate Williams wrote: > > POP and IMAP (I think) will lose all the envelope information, > > You've been listening to Terry too long. It's certainly not the case, > although I've decided to quit arguing with Terry, since it's an > excercise in futility. No matter what you say, he'll either change the > subject or simply overwhelm you with useless/unrelated material until > you simply abandon any hope of trying to give out useful information. > > > SMTP is a PUSH operation.. > > > > so for a PULL operation that can handle envelope information (e.g. BCC) > > you need UUCP > > See above. fetchmail + pop works fine. I've been get all of my envelope > information, and there is no worries. As long as the informations are put into the mails. I asume your don't forget to strip these after fetching the mails? If you do not you distribute those even if not wished by the sender - e.g. in an bcc case. pop/fetchmail is an ugly hack in my eyes because it tries to do something with an protocoll it isn't designed for and it has many pitfalls. > For 'fetching' email, fetchmail is a very good solution. However, there > is also another fairly trivial solution that works well, *IF* you have a > static IP address. > > ETRN also is a good 'fetch' mechanism, if your ISP sets up MX records > for you. When you come up, you simply telnet into your ISP's mail > server, then type 'ETRN foobar.com', and it'll dump all your email to > the IP address of your static configuration. That's unpolite to all mailservers trying to reach yours first. If you know your mailserver is unreachable don't put it in the MX set. Ask your provider to set up a mailertable entry to your server instead. If your provider uses an expansive tagged mailer he can even spare the first try if it's required - this is nice for call-back lines. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 9:31: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 210EB37B409; Tue, 2 Oct 2001 09:30:59 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f92GUbk167254; Tue, 2 Oct 2001 12:30:38 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20011001141916.A24281@fump.kawo2.rwth-aachen.de> References: <20010930145431.A20483@fump.kawo2.rwth-aachen.de> <20010930.234428.102494221.ume@mahoroba.org> <20011001141916.A24281@fump.kawo2.rwth-aachen.de> Date: Tue, 2 Oct 2001 12:30:33 -0400 To: Alexander Langer , Hajimu UMEMOTO From: Garance A Drosihn Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown Cc: current@freebsd.org, gad@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 2:19 PM +0200 10/1/01, Alexander Langer wrote: > >> alex> 15329 ?? S 0:00.02 lpd -4 >> alex> alex@oink ~ $ lpq > > alex> lpd: Host name for your address >(fe80::250:baff:fed4:a512%xl0) unknown > >I started lpd on this machine: (with the -4 flag, see above). >alex@oink ~ $ uname -a ; ifconfig -a >FreeBSD oink.cichlids.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat >Sep 1 15:25:41 CEST 2001 >root@oink.cichlids.com:/usr/obj/usr/src/sys/GENERIC i386 >rl0: flags=8843 mtu 1500 > inet 192.168.0.19 netmask 0xffffff00 broadcast 192.168.0.255 > inet6 fe80::250:baff:fed4:a512%rl0 prefixlen 64 scopeid 0x1 >This is the printcap from this machine: > >lp|local line printer:\ > :sh:\ > :rm=neutron:\ > :sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: > >Note that "neutron" has: >alex@oink ~ $ ping6 neutron >PING6(56=40+8+8 bytes) fe80::250:baff:fed4:a512%rl0 > --> fe80:1::250:4ff:fe0f:5a27 > >Then I just start lpd (or lpd -4, same effect), and this happens. >when I do rm=192.168.0.1 in the printcap, I get: >root@oink ~ $ lpq >oink.cichlids.com: Warning: no daemon present >Rank Owner Job Files Total Size >1st alex 0 (standard input) 419326 bytes > >lpd: Host name for your address (192.168.0.19) unknown > >So, this MIGHT be the reason: The IPv4 address is nonexistent, >but it displays the IPv6 address as error address. However, it's >still bad that he uses and IPv6 stuff when I specify -4 > >BTW, it works if I add a PTR for 192.168.0.19. I am currently battling some kind of cold or flu, so my thinking may be a bit confused. Still, after reading all your messages a few times, I think I understand what is happening. You have a machine which is a "client", as far as printing is concerned. That machine is oink.cichlids.com. In the printcap file for that machine, you reference a printer on a different machine. That print-server machine is named neutron. On the print *client* machine, you start lpd with '-4', meaning that it (the client) should only accept jobs from IPv4-style connections. Note that this flag only effects what lpd will accept, this flag has no effect on what lpr/lpq/lprm will do when they need to connect to a remote queue. The print queue for 'lp' on oink refers to a remote machine that is named neutron. That hostname maps to an IPv6 address. Thus, lpq/lpr/lprm have no choice on how to connect to that remote host. They use the IPv6 address. (note, for instance, that your 'ping6' knows about neutron via IPv6, not IPv4). So, the print client connects to the print server via IPv6. When the print client connects to the print server, the print server looks up the IPv6 address of the *client*, because the client made an IPv6 connection to the server. Again, this has nothing to do with 'lpd -4' on the client. The print server apparently can not find a hostname to match the IPv6 address of the client, so it returns the first error message, listing the IPv6 address of the client. You change printcap to use an IPv4 address, and the client now connects to the server using IPv4. However, the print-server also can not find a hostname to match that IPv4 address, so it returns the second error message. Assuming that all of the above is correct, then I *think* everything is working the way it is supposed to. However, I do not know the finer points of how IPv6 is supposed to work. Can a single hostname have both an IPv4 address and an IPv6 address? (as far as DNS is concerned, I mean). This I do not know. In any case, the parameters to 'lpd' are not going to effect how 'lpq' handles the printcap file. It may be that lpr/lpq/lprm need some change here, but I'm not sure what it would be. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 9:52:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id 4795837B406; Tue, 2 Oct 2001 09:52:28 -0700 (PDT) Received: (from root@localhost) by cheer.mahoroba.org (8.12.1/8.12.1) id f92Gq94h049093; Wed, 3 Oct 2001 01:52:09 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:UvZ7gfn9pSzYgS1RZKbl26aXkRlMkdErzjZYkNkoDTMFWyEo9qRU7p41mOKTn0Lf@peace.mahoroba.org [IPv6:2001:200:301:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.1/8.12.1/av) with ESMTP/inet6 id f92Gq57Q079564; Wed, 3 Oct 2001 01:52:07 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 03 Oct 2001 01:52:04 +0900 (JST) Message-Id: <20011003.015204.133265112.ume@mahoroba.org> To: drosih@rpi.edu Cc: alex@big.endian.de, current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown From: Hajimu UMEMOTO In-Reply-To: References: <20010930.234428.102494221.ume@mahoroba.org> <20011001141916.A24281@fump.kawo2.rwth-aachen.de> 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 X-Mailer: xcite1.38> Mew version 2.0.54 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 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, 2 Oct 2001 12:30:33 -0400 >>>>> Garance A Drosihn said: drosih> On the print *client* machine, you start lpd with '-4', meaning that drosih> it (the client) should only accept jobs from IPv4-style connections. drosih> Note that this flag only effects what lpd will accept, this flag has drosih> no effect on what lpr/lpq/lprm will do when they need to connect to drosih> a remote queue. Yes, it's right. drosih> The print queue for 'lp' on oink refers to a remote machine that drosih> is named neutron. That hostname maps to an IPv6 address. Thus, drosih> lpq/lpr/lprm have no choice on how to connect to that remote host. drosih> They use the IPv6 address. (note, for instance, that your 'ping6' drosih> knows about neutron via IPv6, not IPv4). So, the print client drosih> connects to the print server via IPv6. When the print client drosih> connects to the print server, the print server looks up the IPv6 drosih> address of the *client*, because the client made an IPv6 connection drosih> to the server. Again, this has nothing to do with 'lpd -4' on the drosih> client. The print server apparently can not find a hostname to drosih> match the IPv6 address of the client, so it returns the first error drosih> message, listing the IPv6 address of the client. No, a client does query AAAA RR for IPv6 and A RR for IPv4. If AAAA RR is found, a client tries to connect using IPv6, 1st. However, lpd accepts only IPv4 connection, in this case. Then, if A RR is found, a client falls down and tries to connect using IPv4. So, a client never connects using IPv6 to an IPv4 only listening server. drosih> Assuming that all of the above is correct, then I *think* everything drosih> is working the way it is supposed to. However, I do not know the drosih> finer points of how IPv6 is supposed to work. Can a single hostname drosih> have both an IPv4 address and an IPv6 address? (as far as DNS is drosih> concerned, I mean). This I do not know. In any case, the parameters drosih> to 'lpd' are not going to effect how 'lpq' handles the printcap file. It is usual way that a dual stack host has both AAAA RR and A RR. -- 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 Tue Oct 2 10:42:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 9DC3D37B405 for ; Tue, 2 Oct 2001 10:42:18 -0700 (PDT) Received: by heechee.tobez.org (Postfix, from userid 1001) id 736C95411; Tue, 2 Oct 2001 19:42:14 +0200 (CEST) Date: Tue, 2 Oct 2001 19:42:14 +0200 From: Anton Berezin To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/isa psm.c atkbdc_isa.c Message-ID: <20011002194214.A95652@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Kazutaka YOKOTA , current@freebsd.org References: <200109251659.f8PGxTN66726@freefall.freebsd.org> <20011001013254.A698@heechee.tobez.org> <200110010550.OAA01361@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110010550.OAA01361@zodiac.mech.utsunomiya-u.ac.jp>; from yokota@zodiac.mech.utsunomiya-u.ac.jp on Mon, Oct 01, 2001 at 02:50:18PM +0900 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, Oct 01, 2001 at 02:50:18PM +0900, Kazutaka YOKOTA wrote: > >> Yet another turn of workaround for psm/ACPI/PnP BIOS problems > >> currently experienced in -CURRENT. > >> > >> This should fix the problem that the PS/2 mouse is detected twice > >> if the acpi module is not loaded on some systems. > >Can it be that this fix is responsible for PS/2 mouse being detected > >zero times? :-) :-( > > > >Dmesg output is in a separate message. > > This is most likely to be an ACPI problem. Please try disabling the > acpi module ("unset load_acpi" at the loader prompt) and "boot -v", > then send me dmesg's output. Yes, it turned out to be ACPI problem - the mouse's working fine now. Sorry for bugging you. I presume you don't need a new dmesg output now? \Anton. -- | Anton Berezin | FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | tobez@catpipe.net (_(_|| | tobez@FreeBSD.org | | +45 7021 0050 | Private: tobez@tobez.org | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 10:48:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail153.nifty.com (mail153.nifty.com [202.248.37.146]) by hub.freebsd.org (Postfix) with ESMTP id 4903337B407 for ; Tue, 2 Oct 2001 10:48:43 -0700 (PDT) Received: from chrysanthe.oikumene.gcd.org by mail153.nifty.com (8.11.4+3.4W/3.7W-10/13/99) with SMTP id f92Hmf315316 for ; Wed, 3 Oct 2001 02:48:41 +0900 Received: (qmail 76907 invoked from network); 2 Oct 2001 17:48:41 -0000 Received: from chrysanthe.oikumene.gcd.org (HELO localhost) (@192.168.0.12) by chrysanthe.oikumene.gcd.org with SMTP; 2 Oct 2001 17:48:41 -0000 To: freebsd-current@FreeBSD.ORG Subject: Re: current.freebsd.org is broken? From: Hiroo ONO (=?iso-2022-jp?B?GyRCPi5MbjQyQDgbKEI=?=) In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20011003024840R.hiroo@oikumene.gcd.org> Date: Wed, 03 Oct 2001 02:48:40 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 16 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 did not look at current.FreeBSD.ORG, but at current.jp.FreeBSD.ORG, the build on the 1st and 2nd October seem to have succeeded. I tried to install 5.0-CURRENT-20011002-JPSNAP from current.jp.FreeBSD.ORG, then sysinstall says mknod of /dev/rad0s1b returned failure status! and stops at the time of "Commit". housel@acm.org (Peter S. Housel) wrote: > At Wed, 26 Sep 2001 16:54:52 -0400 (EDT), Robert Watson wrote: > > current.jp.freebsd.org apparently carries snapshots, although I haven't > > tried it recently. > It's been unable to build a release for the past two weeks since the > release kernel overflows its floppy. The last successful build was > on September 11. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 11: 8:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3574037B406 for ; Tue, 2 Oct 2001 11:08:30 -0700 (PDT) Received: from blossom.cjclark.org (dialup-209.245.143.22.Dial1.SanJose1.Level3.net [209.245.143.22]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA07937; Tue, 2 Oct 2001 11:08:10 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f92I7w100948; Tue, 2 Oct 2001 11:07:58 -0700 (PDT) (envelope-from cjc) Date: Tue, 2 Oct 2001 11:07:58 -0700 From: "Crist J. Clark" To: Bernd Walter Cc: Nate Williams , Julian Elischer , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory Message-ID: <20011002110758.A310@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <15289.56953.709463.415400@nomad.yogotech.com> <20011002181829.A27231@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011002181829.A27231@cicely20.cicely.de>; from ticso@mail.cicely.de on Tue, Oct 02, 2001 at 06:18:29PM +0200 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, Oct 02, 2001 at 06:18:29PM +0200, Bernd Walter wrote: > On Tue, Oct 02, 2001 at 09:34:17AM -0600, Nate Williams wrote: [snip] > > See above. fetchmail + pop works fine. I've been get all of my envelope > > information, and there is no worries. > > As long as the informations are put into the mails. > I asume your don't forget to strip these after fetching the mails? Strip what? > If you do not you distribute those even if not wished by the sender - > e.g. in an bcc case. Any special processing of 'BCC' takes place at the sender's end. There is nothing special a receiver needs to (or could ever be trusted to) do. > pop/fetchmail is an ugly hack in my eyes because it tries to do > something with an protocoll it isn't designed for and it has many > pitfalls. Uhh, grabbing email from a remote mailspool _is_ exactly what POP3/fetchmail is meant to do. Or is there something else here that someone is trying to do? But how does any of this relate to -CURRENT? uucp is still there for anyone who wants it in the ports. If your ISP does not support uucp and you want to use it to grab email, complain to your ISP, not -current. -- 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 Tue Oct 2 11:27:13 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 F085E37B401 for ; Tue, 2 Oct 2001 11:27:07 -0700 (PDT) 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 f92IR7H93929 for ; Tue, 2 Oct 2001 11:27:07 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 2 Oct 2001 11:26:24 -0700 (PDT) From: Matthew Jacob Reply-To: To: Subject: that was wierd... Message-ID: <20011002112521.A97562-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 rebooted a kernel (2xSMP -current, last day or so) and it went to the debugger in hardclock.....so I said 'c' to continue and it rebooted fine. Wierd. boot() called on cpu#1 Stopped at hardclock+0x1ac: testl %esi,%esi db> t hardclock(d98a3cc4) at hardclock+0x1ac clkintr(0) at clkintr+0xe7 Xfastintr0(d9893500,d98a3d34,c01a3bcb,0,d98a3d48) at Xfastintr0+0x2f idle_proc(0,d98a3d48) at idle_proc+0x16 fork_exit(c01a3db4,0,d98a3d48) at fork_exit+0x77 fork_trampoline() at fork_trampoline+0x8 db> c Waiting (max 60 seconds) for system process `bufdaemon' to stop...isp1: Name Server Database Changed isp1: Name Server Database Changed isp1: Port Logout for Initiator 137 RX_ID 0x0 isp1: Port Database Changed isp1: Name Server Database Changed Connection attempt to UDP 10.0.0.252:111 from 10.0.0.199:990 isp1: Firmware State Ready> isp1: Target 126 (Loop 0x7e) Port ID 0xfffffe (role (none)) Arrived Port WWN 0x200500c0dd007179 Node WWN 0x100000c0dd007179 isp1: Loop ID 0, AL_PA 0xef, Port ID 0x1005ef, Loop State 0x2, Topology 'FL Port' isp1: Target 0 (Loop 0x0) Port ID 0x1005ef (role Target/Initiator) Arrived Port WWN 0x210000e08b022d48 Node WWN 0x200000e08b022d48 stopped Waiting (max 60 seconds) for system process `syncer' to stop...isp1: NL_Port @ 0x1006e1, Node 0x2000002037304800 Port 2200002037304800 isp1: NL_Port @ 0x1006e2, Node 0x200000203730484b Port 220000203730484b isp1: NL_Port @ 0x1006e4, Node 0x2000002037304daf Port 2200002037304daf isp1: sNL_Potrt @ o0x1006pe8, Node 0x2000002037304875 Port 2200002037304875 ped syncing disks... 18 18 isp1: NL_Port @ 0x1006ef, Node 0x2000002037304e8b Port 2200002037304e8b isp1: N_14 Port @ 0x100000, Node 0x200000a080002265 Port 200100a080002265 14 isp1: NL_Port @ 0x100126, Node 0x200000e08b0012c5 Port 210000e08b0012c5 6 6 isp1: NL_Port @ 0x1002ef, Node 0x200000e08b022648 Port 210000e08b0221 648 1 isp1: NL_Port @ 0x1005ef, Node 0x200000e08b022d48 Port 210000e08b022d48 (Por Retaining Loop ID 0x7e for Target 126 t 0xffdone fffe) isp1: Target 134 (Loop 0x81) Port ID 0x100729 (role Target/Initiator) Departed Port WWN 0x210000e08b00391f Node WWN 0x200000e08b00391f isp1: Retained login of Target 129 (Loop ID 0x82) Port 0x1006e1 isp1: Retained login of Target 130 (Loop ID 0x83) Port 0x1006e2 isp1: Retained login of Target 131 (Loop ID 0x84) Port 0x1006e4 isp1: Retained login of Target 132 (Loop ID 0x85) Port 0x1006e8 isp1: Retained login of Target 133 (Loop ID 0x86) Port 0x1006ef isp1: Retained login of Target 135 (Loop ID 0x87) Port 0x100000 Uptime: 1d13h40m53s Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 12:19:37 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 AA1C637B407 for ; Tue, 2 Oct 2001 12:19:28 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA92654; Tue, 2 Oct 2001 13:04:59 -0700 (PDT) Date: Tue, 2 Oct 2001 13:04:58 -0700 (PDT) From: Julian Elischer To: Nate Williams Cc: "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: <15289.56953.709463.415400@nomad.yogotech.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, 2 Oct 2001, Nate Williams wrote: > > POP and IMAP (I think) will lose all the envelope information, > > You've been listening to Terry too long. It's certainly not the case, > although I've decided to quit arguing with Terry, since it's an > excercise in futility. No matter what you say, he'll either change the > subject or simply overwhelm you with useless/unrelated material until > you simply abandon any hope of trying to give out useful information. > > > SMTP is a PUSH operation.. > > > > so for a PULL operation that can handle envelope information (e.g. BCC) > > you need UUCP > > See above. fetchmail + pop works fine. I've been get all of my envelope > information, and there is no worries. This has noty been the case where I have seen.. This requires that you have a mailbox set up on the server which can 'encode' all of the envelope information (e.g. other delivery addresses) and that fetchmail can extract this information in such a way that it can reconstruct the original mail address information without getting it confused with the header infiormation within the mail headers, which of course should be completely ignored when it comes to delivery. Unfortunatly I have not see this done completely successfully. UUCP can do this with very little work and does it very well. (as if keeps the 'command' information separate from the "data" information). I"m not saying that this is not possible, just that it's very complicated to get right compared to a basic "out of the box" uucp connection that can do it completely correctly with almost no work... > > For 'fetching' email, fetchmail is a very good solution. However, there > is also another fairly trivial solution that works well, *IF* you have a > static IP address. (see above) > > ETRN also is a good 'fetch' mechanism, if your ISP sets up MX records > for you. When you come up, you simply telnet into your ISP's mail > server, then type 'ETRN foobar.com', and it'll dump all your email to > the IP address of your static configuration. > > However, this won't work for roving users. It doesn't even work well for static users in large configurations.. as it requires a full queue scan. (some mail servers do this better than others). > > > > Nate > > > > On Tue, 2 Oct 2001, Daniel O'Connor wrote: > > > > > > > > On 01-Oct-2001 Lyndon Nerenberg wrote: > > > > UUCP still gets used. It's one of the few sane ways to handle email in > > > > a laptop environment when you're always connecting through different > > > > dialups/ISPs. It has mostly fallen out of favour due to ignorance and > > > > FUD. Which is a shame, as it can still be a useful tool in certain > > > > situations. > > > > > > I think a more 'modern' solution is POP or IMAP over SSH, you can also feed > > > SMTP over an SSH tunnel too (This is what I use). > > > > > > --- > > > Daniel O'Connor software and network engineer > > > for Genesis Software - http://www.gsoft.com.au > > > "The nice thing about standards is that there > > > are so many of them to choose from." > > > -- Andrew Tanenbaum > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > 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 Oct 2 12:19:48 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 D4FF437B406 for ; Tue, 2 Oct 2001 12:19:43 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA92666; Tue, 2 Oct 2001 13:09:43 -0700 (PDT) Date: Tue, 2 Oct 2001 13:09:43 -0700 (PDT) From: Julian Elischer To: cjclark@alum.mit.edu Cc: Bernd Walter , Nate Williams , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: <20011002110758.A310@blossom.cjclark.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, 2 Oct 2001, Crist J. Clark wrote: > On Tue, Oct 02, 2001 at 06:18:29PM +0200, Bernd Walter wrote: > > On Tue, Oct 02, 2001 at 09:34:17AM -0600, Nate Williams wrote: > > [snip] > > > > See above. fetchmail + pop works fine. I've been get all of my envelope > > > information, and there is no worries. > > > > As long as the informations are put into the mails. > > I asume your don't forget to strip these after fetching the mails? > > Strip what? The embedded information that shuold not be passed on. I.E. the delivery addresses. (these are not the same as the To: lines) > > > If you do not you distribute those even if not wished by the sender - > > e.g. in an bcc case. > > Any special processing of 'BCC' takes place at the sender's end. There > is nothing special a receiver needs to (or could ever be trusted to) > do. this is not true at all. BCC requires that all intemediate stages have separate handling of the header, and the address list. > > > pop/fetchmail is an ugly hack in my eyes because it tries to do > > something with an protocoll it isn't designed for and it has many > > pitfalls. > > Uhh, grabbing email from a remote mailspool _is_ exactly what > POP3/fetchmail is meant to do. Or is there something else here that > someone is trying to do? No, Pop is for grabbing mail from a MAILBOX. Mailboxes strip off and delete delivery address information. > > But how does any of this relate to -CURRENT? uucp is still there for > anyone who wants it in the ports. If your ISP does not support uucp > and you want to use it to grab email, complain to your ISP, not > -current. The question was "Is there something that people want uucp for?" > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 12:24:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.dada.it (mail3.dada.it [195.110.96.70]) by hub.freebsd.org (Postfix) with SMTP id DEE2337B408 for ; Tue, 2 Oct 2001 12:24:20 -0700 (PDT) Received: (qmail 20431 invoked from network); 2 Oct 2001 19:24:12 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 2 Oct 2001 19:24:12 -0000 Received: (from riccardo@localhost) by torrini.org (8.11.3/8.11.3) id f92JNpA22791 for freebsd-current@FreeBSD.ORG; Tue, 2 Oct 2001 21:23:51 +0200 (CEST) (envelope-from riccardo) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 02 Oct 2001 21:23:50 +0200 (CEST) From: Riccardo Torrini To: freebsd-current@FreeBSD.ORG Subject: Different host behaviour 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 Different behaviour from 4.4 to 5.0 of host command. Why? Yes, I got finally delegation for reverse (with RFC 2317). Yes, my -CURRENT is really old, but I'm reading this list... ;) And sorry for long lines with custom formatting. Using nslookup from either 4.4 and 5.0 give me same results (tryed with an external dns, to minimize my config problems): # nslookup 217.58.169.99 151.1.1.1 Server: dns.it.net Address: 151.1.1.1 Name: gw-fi.esaote.com Address: 217.58.169.99 Aliases: 99.169.58.217.in-addr.arpa -----8<-----[ 4.4-STABLE ]-----8<----- # uname -a FreeBSD silos.home.torrini.org 4.4-STABLE FreeBSD 4.4-STABLE #5: Sun Sep 16 05:34:02 CEST 2001 root@silos.home.torrini.org:/usr/obj/usr/src/sys/SILOS i386 # host 217.58.169.99 99.169.58.217.IN-ADDR.ARPA is a nickname for 99.96-28.169.58.217.IN-ADDR.ARPA 99.96-28.169.58.217.IN-ADDR.ARPA domain name pointer gw-fi.esaote.com -----8<-----[ 5.0-CURRENT ]-----8<----- # uname -a FreeBSD trudy.home.torrini.org 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Sat Apr 28 03:30:53 CEST 2001 root@trudy.home.torrini.org:/usr/obj/usr/src/sys/TRUDY i386 # host 217.58.169.99 99.169.58.217.IN-ADDR.ARPA is a nickname for 99.96-28.169.58.217.IN-ADDR.ARPA Riccardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 12:25:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id EBBA737B401 for ; Tue, 2 Oct 2001 12:25:17 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA19222; Tue, 2 Oct 2001 13:25:01 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA22941; Tue, 2 Oct 2001 13:25:01 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15290.5260.610951.681033@nomad.yogotech.com> Date: Tue, 2 Oct 2001 13:25:00 -0600 To: Julian Elischer Cc: Nate Williams , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: References: <15289.56953.709463.415400@nomad.yogotech.com> X-Mailer: VM 6.95 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > > > POP and IMAP (I think) will lose all the envelope information, > > > > You've been listening to Terry too long. It's certainly not the case, > > although I've decided to quit arguing with Terry, since it's an > > excercise in futility. No matter what you say, he'll either change the > > subject or simply overwhelm you with useless/unrelated material until > > you simply abandon any hope of trying to give out useful information. > > > > > SMTP is a PUSH operation.. > > > > > > so for a PULL operation that can handle envelope information (e.g. BCC) > > > you need UUCP > > > > See above. fetchmail + pop works fine. I've been get all of my envelope > > information, and there is no worries. > > This has noty been the case where I have seen.. Again, as has been pointed out, it's the responsibility of the *sender* to make sure all of the envelope information is properly respected. POP3 is a mail retriever, designed to retrieve mail for a single user. It preserves all of the necessary information that a 'receiver' needs. Now, if you're doing something that POP3 was never intended to do (ie; handle multiple users with a single mailbox), then we're talking something completely different. This isn't something POP3 was designed to do. The problem isn't a fetchmail/POP3 problem. It's trying to stuff multiple users into a single account. UUCP doesn't 'solve' this problem anymore, since you still need the ability to have multiple 'user' accounts at the ISP, even with UUDP. Nate > > ETRN also is a good 'fetch' mechanism, if your ISP sets up MX records > > for you. When you come up, you simply telnet into your ISP's mail > > server, then type 'ETRN foobar.com', and it'll dump all your email to > > the IP address of your static configuration. > > > > However, this won't work for roving users. > > It doesn't even work well for static users in large configurations.. > as it requires a full queue scan. (some mail servers do this better than > others). Right, David and I just had a long offline talk about this. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 12:49:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id E1A5137B401 for ; Tue, 2 Oct 2001 12:49:13 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f92JnC8f023243; Tue, 2 Oct 2001 13:49:12 -0600 (MDT) Message-Id: <200110021949.f92JnC8f023243@atg.aciworldwide.com> Organization: ACI Worldwide - Advanced Technology Group X-URL: http://www.aciworldwide.com/ To: nate@yogotech.com (Nate Williams) Cc: current@freebsd.org Subject: Re: uucp user shell and home directory In-Reply-To: Message from Nate Williams of "Tue, 02 Oct 2001 13:25:00 MDT." <15290.5260.610951.681033@nomad.yogotech.com> Date: Tue, 02 Oct 2001 13:49:12 -0600 From: Lyndon Nerenberg 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 Okay, here's why I use UUCP rather than POP (or in my case, IMAP). I make use of detail addressing to filter my mail. For example: RCPT TO Delivery location ------- ----------------- lyndon /var/mail/lyndon lyndon+imap ${HOME}/Mail/imap/... (MH) lyndon+sysalert /var/mail/lyndon + an X11 on-screen alert lists+freebsd-current LMTP to the lists/freebsd/current folder on the local IMAP server Not all of the filtering I require can be done based on the MAIL FROM. I have to have access to the RCPT TO address that triggered the delivery in order to do some of this filtering. While you can usually determine the MAIL FROM by examining the Return-Path: header in the message, you cannot determine the RCPT TO address by looking inside of the RFC2822 message headers. This eliminates POP and IMAP for "delivery" of this mail. Also, I *do* have delivery to multiple user accounts on my laptop. Polling for these multiple "users" from another mail server would be inefficient and wasteful of resources. For the times that I'm directly connected to my regular LAN at my regular IP address, mail flows in via SMTP directly to the laptop. I don't go polling any IMAP or POP servers to collect my mail. When I'm not connected to the usual network, I don't want to (nor should I have to) change how I retrieve my mail. And I don't have to. When I'm on the road (and direct SMTP delivery fails because I'm not reachable at the usual IP address), my mail is delivered to the MX backup host. The MTA there queues my mail up for UUCP delivery. When I get the chance to get connected, be it via IP or direct dialup to the backup MX server, I fire up a UUCP session which pulls down incoming mail for the laptop (and also sends any queued outbound mail), all the while preserving the sender and recipient *envelope* addresses, which are critical to my filtering needs. All without requiring *any* changes in how I handle my email. IMAP and POP are not message transport protocols. If you're using them as such you need to take a close look at your email environment. --lyndon >What about all the people who hoarded tonnes of spam in their bunkers? I hoard spam on my hard drive. When I heard about the coming Y2K worries, I downloaded a lifetime supply from the net. -- Charlie Gibbs in alt.folklore.computers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 12:55:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by hub.freebsd.org (Postfix) with SMTP id 2930E37B401 for ; Tue, 2 Oct 2001 12:55:29 -0700 (PDT) Received: from mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 2 Oct 2001 19:55:28 -0000 X-Apparently-From: Message-ID: <3BBA1BAF.7020502@yahoo.com> Date: Tue, 02 Oct 2001 14:55:27 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: burncd issue Content-Type: text/plain; charset=us-ascii; format=flowed 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 This is from -current as of about 1am or so CDT today. 2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data StarOffice52.iso fixate burncd: ioctl(CDIOCSTART): Device busy I was under the impression that if the kernel and world were in sync that this would work based on a message I read yesterday. acd0: CD-RW at ata1-master PIO4 jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 13:19: 6 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 825A737B401 for ; Tue, 2 Oct 2001 13:19:02 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA92942; Tue, 2 Oct 2001 14:17:35 -0700 (PDT) Date: Tue, 2 Oct 2001 14:17:33 -0700 (PDT) From: Julian Elischer To: Nate Williams Cc: "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: <15290.5260.610951.681033@nomad.yogotech.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, 2 Oct 2001, Nate Williams wrote: > > > > POP and IMAP (I think) will lose all the envelope information, > > > > > > You've been listening to Terry too long. It's certainly not the case, > > > although I've decided to quit arguing with Terry, since it's an > > > excercise in futility. No matter what you say, he'll either change the > > > subject or simply overwhelm you with useless/unrelated material until > > > you simply abandon any hope of trying to give out useful information. > > > > > > > SMTP is a PUSH operation.. > > > > > > > > so for a PULL operation that can handle envelope information (e.g. BCC) > > > > you need UUCP > > > > > > See above. fetchmail + pop works fine. I've been get all of my envelope > > > information, and there is no worries. > > > > This has noty been the case where I have seen.. > > Again, as has been pointed out, it's the responsibility of the *sender* > to make sure all of the envelope information is properly respected. > > POP3 is a mail retriever, designed to retrieve mail for a single user. > It preserves all of the necessary information that a 'receiver' needs. > > Now, if you're doing something that POP3 was never intended to do (ie; > handle multiple users with a single mailbox), then we're talking > something completely different. This isn't something POP3 was designed > to do. exactly my point.. fetchmail/pop does not do what uucp does... (pull mail between hops on the mail delivery path). > > The problem isn't a fetchmail/POP3 problem. It's trying to stuff > multiple users into a single account. UUCP doesn't 'solve' this problem > anymore, since you still need the ability to have multiple 'user' > accounts at the ISP, even with UUDP. No, uucp dosn't require this.. it will just pass on the envelope information withuot trying to interpret it.. i.e. it does this correctly (assuming you set it up correctly) > > > > Nate > > > ETRN also is a good 'fetch' mechanism, if your ISP sets up MX records > > > for you. When you come up, you simply telnet into your ISP's mail > > > server, then type 'ETRN foobar.com', and it'll dump all your email to > > > the IP address of your static configuration. > > > > > > However, this won't work for roving users. > > > > It doesn't even work well for static users in large configurations.. > > as it requires a full queue scan. (some mail servers do this better than > > others). > > Right, David and I just had a long offline talk about this. > > > > Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 13:22:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 08CE837B401 for ; Tue, 2 Oct 2001 13:22:40 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id OAA21481; Tue, 2 Oct 2001 14:22:31 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id OAA23192; Tue, 2 Oct 2001 14:22:31 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15290.8711.449917.768672@nomad.yogotech.com> Date: Tue, 2 Oct 2001 14:22:31 -0600 To: Julian Elischer Cc: Nate Williams , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory In-Reply-To: References: <15290.5260.610951.681033@nomad.yogotech.com> X-Mailer: VM 6.95 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > > POP3 is a mail retriever, designed to retrieve mail for a single user. > > It preserves all of the necessary information that a 'receiver' needs. > > > > Now, if you're doing something that POP3 was never intended to do (ie; > > handle multiple users with a single mailbox), then we're talking > > something completely different. This isn't something POP3 was designed > > to do. > > exactly my point.. > fetchmail/pop does not do what uucp does... (pull mail between hops on > the mail delivery path). POP3 pulls mail fine, as long as the mail is for a single user. > > The problem isn't a fetchmail/POP3 problem. It's trying to stuff > > multiple users into a single account. UUCP doesn't 'solve' this problem > > anymore, since you still need the ability to have multiple 'user' > > accounts at the ISP, even with UUCP. > > No, uucp dosn't require this.. it will just pass on the envelope > information withuot trying to interpret it.. > i.e. it does this correctly (assuming you set it up correctly) It requires that you setup a new domain, which POP3 does not. A new domain is only 'useful' if you have multiple user accounts, otherwise it's un-necessary. (Although, some people like to have their own domain, this can be done using POP3 fine if the domain has only one user account). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 13:30:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id E8A4137B401 for ; Tue, 2 Oct 2001 13:30:39 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f92KUd8f024047; Tue, 2 Oct 2001 14:30:39 -0600 (MDT) Message-Id: <200110022030.f92KUd8f024047@atg.aciworldwide.com> Organization: ACI Worldwide - Advanced Technology Group X-URL: http://www.aciworldwide.com/ To: nate@yogotech.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: uucp user shell and home directory In-Reply-To: Message from Nate Williams of "Tue, 02 Oct 2001 14:22:31 MDT." <15290.8711.449917.768672@nomad.yogotech.com> Date: Tue, 02 Oct 2001 14:30:39 -0600 From: Lyndon Nerenberg 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 requires that you setup a new domain No it doesn't. All that's needed is an MX record and an MTA routing table entry on the MX host. --lyndon Never look at the trombones. You'll only encourage them. -- Robert Strauss, on conducting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 2 14: 6:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id B8E0F37B408 for ; Tue, 2 Oct 2001 14:06:41 -0700 (PDT) Received: from blossom.cjclark.org (dialup-209.245.143.22.Dial1.SanJose1.Level3.net [209.245.143.22]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA12311; Tue, 2 Oct 2001 14:06:32 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f92L6Uh01710; Tue, 2 Oct 2001 14:06:30 -0700 (PDT) (envelope-from cjc) Date: Tue, 2 Oct 2001 14:06:30 -0700 From: "Crist J. Clark" To: Julian Elischer Cc: Bernd Walter , Nate Williams , "Daniel O'Connor" , Lyndon Nerenberg , current@FreeBSD.ORG, Garrett Wollman Subject: Re: uucp user shell and home directory Message-ID: <20011002140630.B310@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20011002110758.A310@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: ; from julian@elischer.org on Tue, Oct 02, 2001 at 01:09:43PM -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 Tue, Oct 02, 2001 at 01:09:43PM -0700, Julian Elischer wrote: [snip] > > Any special processing of 'BCC' takes place at the sender's end. There > > is nothing special a receiver needs to (or could ever be trusted to) > > do. > > this is not true at all. > BCC requires that all intemediate stages have separate > handling of the header, and the address list. Ah. I understand what that was supposed to mean now. The way I think of SMTP working I think of the BCC recipient being the just MAIL TO and not in the mailed file, the DATA. Obviously, you are correct, the MAIL TO is stored temporarily in a spool file. I've spent too much time talking to SMTP servers with telnet. -- 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 Tue Oct 2 14: 7:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id B707E37B41F for ; Tue, 2 Oct 2001 14:06:48 -0700 (PDT) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.6/8.11.4) id f92L6lI82471 for freebsd-current@freebsd.org; Tue, 2 Oct 2001 17:06:47 -0400 (EDT) (envelope-from ak03) Date: Tue, 2 Oct 2001 17:06:46 -0400 From: "Alexander N. Kabaev" To: freebsd-current@freebsd.org Subject: Weird PCI BIOS - long Message-ID: <20011002170646.A81966@kanpc.gte.com> Reply-To: kabaev@bellatlantic.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i 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 am trying to install -CURRENT on ThinkPad 770ED with a limited success so far. I noticed that when the kernel boots on this notebook, it complains about PCI BIOS entry call point not being available. The following is a boot -v output from my kernel file(see below for further comments): 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 #3: Tue Oct 2 14:42:07 EDT 2001 root@kanpc.gte.com:/usr/src/sys/i386/compile/MONTY Calibrating clock(s) ... TSC clock: 265248670 Hz, i8254 clock: 1193117 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 265266729 Hz CPU: Pentium II/Pentium II Xeon/Celeron (265.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 134021120 (130880K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00336000 - 0x07fc7fff, 130621440 bytes (31890 pages) avail memory = 127336448 (124352K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd880+0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f0000:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: Preloaded elf kernel "/boot/kernel/kernel" at 0xc030f000. null: random: mem: Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x000038c8 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) pcibios: No call entry point npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base 00000000, size 28, enabled found-> vendor=0x8086, dev=0x7192, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 map[10]: type 1, range 32, base 20822000, size 12, enabled found-> vendor=0x104c, dev=0xac16, revid=0x02 bus=0, slot=2, 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 20821000, size 12, enabled found-> vendor=0x104c, dev=0xac16, revid=0x02 bus=0, slot=2, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 intpin=b, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 20400000, size 22, enabled map[14]: type 1, range 32, base 20800000, size 17, enabled map[18]: type 1, range 32, base 20000000, size 22, enabled found-> vendor=0x1023, dev=0x9397, revid=0xf3 bus=0, slot=3, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11 map[10]: type 1, range 32, base 20820000, size 10, enabled found-> vendor=0x1014, dev=0x007d, revid=0x00 bus=0, slot=5, func=0 class=04-80-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11 found-> vendor=0x8086, dev=0x7110, revid=0x01 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base 0000fcf0, 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 00008400, 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=11 map[90]: type 4, range 32, base 0000efa0, size 4, enabled found-> vendor=0x8086, dev=0x7113, revid=0x01 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 pci0: on pcib0 pcibios: No call entry point pci_cfgintr: BIOS 0.00 doesn't support interrupt routing pcic0: mem 0x20822000-0x20822fff at device 2.0 on pci0 pcibios: No call entry point pci_cfgintr: BIOS 0.00 doesn't support interrupt routing pcic0: No PCI interrupt routed, trying ISA. pcic0: Polling mode pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC parallel isa irq] pcic0: PCI Configuration space: 0x00: 0xac16104c 0x04: 0x02100007 0x08: 0x06070002 0x0c: 0x0082a808 0x10: 0x20822000 0x14: 0x020000a0 0x18: 0xb0030100 0x1c: 0x00000000 0x20: 0x00000000 0x24: 0x00000000 0x28: 0x00000000 0x2c: 0x00000000 0x30: 0x00000000 0x34: 0x00000000 0x38: 0x00000000 0x3c: 0x07e001ff 0x40: 0x00921014 0x44: 0x00000001 0x48: 0x00000000 0x4c: 0x00000000 0x50: 0x00000000 0x54: 0x00000000 0x58: 0x00000000 0x5c: 0x00000000 0x60: 0x00000000 0x64: 0x00000000 0x68: 0x00000000 0x6c: 0x00000000 0x70: 0x00000000 0x74: 0x00000000 0x78: 0x00000000 0x7c: 0x00000000 0x80: 0x00449060 0x84: 0x00000000 0x88: 0x09818148 0x8c: 0xfba97543 0x90: 0x606283c0 0x94: 0x00000000 0x98: 0x00000000 0x9c: 0x00000000 0xa0: 0x7e210001 0xa4: 0x00800000 0xa8: 0x00000000 0xac: 0x00000000 0xb0: 0x00000000 0xb4: 0x00000000 0xb8: 0x00000000 0xbc: 0x00000000 0xc0: 0x00000000 0xc4: 0x00000000 0xc8: 0x00000000 0xcc: 0x00000000 0xd0: 0x00000000 0xd4: 0x00000000 0xd8: 0x00000000 0xdc: 0x00000000 0xe0: 0x00000000 0xe4: 0x00000000 0xe8: 0x00000000 0xec: 0x00000000 0xf0: 0x00000000 0xf4: 0x00000000 0xf8: 0x00000000 0xfc: 0x00000000 pccard0: on pcic0 pcibios: No call entry point pci_cfgintr: BIOS 0.00 doesn't support interrupt routing pcic1: mem 0x20821000-0x20821fff at device 2.1 on pci0 pcibios: No call entry point pci_cfgintr: BIOS 0.00 doesn't support interrupt routing pcic1: No PCI interrupt routed, trying ISA. pcic1: Polling mode pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC parallel isa irq] pcic1: PCI Configuration space: 0x00: 0xac16104c 0x04: 0x02100007 0x08: 0x06070002 0x0c: 0x0082a808 0x10: 0x20821000 0x14: 0x020000a0 0x18: 0xb0060400 0x1c: 0x00000000 0x20: 0x00000000 0x24: 0x00000000 0x28: 0x00000000 0x2c: 0x00000000 0x30: 0x00000000 0x34: 0x00000000 0x38: 0x00000000 0x3c: 0x07e002ff 0x40: 0x00921014 0x44: 0x00000001 0x48: 0x00000000 0x4c: 0x00000000 0x50: 0x00000000 0x54: 0x00000000 0x58: 0x00000000 0x5c: 0x00000000 0x60: 0x00000000 0x64: 0x00000000 0x68: 0x00000000 0x6c: 0x00000000 0x70: 0x00000000 0x74: 0x00000000 0x78: 0x00000000 0x7c: 0x00000000 0x80: 0x00449060 0x84: 0x00000000 0x88: 0x09818148 0x8c: 0xfba97543 0x90: 0x606282c0 0x94: 0x00000000 0x98: 0x00000000 0x9c: 0x00000000 0xa0: 0x7e210001 0xa4: 0x00800000 0xa8: 0x00000000 0xac: 0x00000000 0xb0: 0x00000000 0xb4: 0x00000000 0xb8: 0x00000000 0xbc: 0x00000000 0xc0: 0x00000000 0xc4: 0x00000000 0xc8: 0x00000000 0xcc: 0x00000000 0xd0: 0x00000000 0xd4: 0x00000000 0xd8: 0x00000000 0xdc: 0x00000000 0xe0: 0x00000000 0xe4: 0x00000000 0xe8: 0x00000000 0xec: 0x00000000 0xf0: 0x00000000 0xf4: 0x00000000 0xf8: 0x00000000 0xfc: 0x00000000 pccard1: on pcic1 pci0: at device 3.0 (no driver attached) pci0: at device 5.0 (no driver attached) 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 0xfcf0-0xfcff at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe 00 00 ata0-slave: 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=0xfcf8 ata1: mask=03 ostat0=50 ostat2=01 ata1-master: ATAPI probe 14 eb ata1-slave: ATAPI probe 00 00 ata1: mask=03 stat0=00 stat1=01 ata1-slave: ATA probe 04 00 ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (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 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: 23 devices, largest 980 bytes PNP0000: adding fixed io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding fixed io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 0x4 pnpbios: handle 0 device ID PNP0000 (0000d041) PNP0200: adding fixed io range 0-0xf, size=0x10, align=0x1 PNP0200: adding fixed io range 0x80-0x8f, size=0x10, align=0x1 PNP0200: adding fixed io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding fixed io range 0x40-0x43, size=0x4, align=0x1 pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding fixed io range 0x70-0x73, size=0x4, align=0x1 pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0800: adding fixed io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 4 device ID PNP0800 (0008d041) PNP0303: adding irq mask 0x2 PNP0303: adding fixed io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding fixed io range 0x64-0x64, size=0x1, align=0x1 pnpbios: handle 5 device ID PNP0303 (0303d041) IBM3780: adding irq mask 0x1000 pnpbios: handle 6 device ID IBM3780 (80374d24) PNP0c04: adding fixed io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0700: adding irq mask 0x40 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x80 PNP0700: adding dma mask 0x4 pnpbios: handle 8 device ID PNP0700 (0007d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x22-0x22, size=0x1, align=0 PNP0c02: adding io range 0x2e-0x2f, size=0x2, align=0 PNP0c02: adding io range 0x92-0x92, size=0x1, align=0 PNP0c02: adding io range 0xb2-0xb3, size=0x2, align=0 PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0c02: adding io range 0x15e0-0x15ef, size=0x10, align=0 PNP0c02: adding io range 0xef00-0xefaf, size=0xb0, align=0 PNP0c02: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c02: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c02: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c02: adding fixed memory32 range 0xffff0000-0xffffffff, size=0x10000 pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x3bc-0x3bf, size=0x4, align=0 pnpbios: handle 11 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 pnpbios: handle 13 device ID PNP0501 (0105d041) CSC0000: adding io range 0x530-0x537, size=0x8, align=0 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0 CSC0000: adding io range 0x220-0x233, size=0x14, align=0x20 CSC0000: adding irq mask 0x20 CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x1 pnpbios: handle 14 device ID CSC0000 (0000630e) CSC0010: adding io range 0x538-0x53f, size=0x8, align=0 pnpbios: handle 15 device ID CSC0010 (1000630e) CSC0001: adding io range 0x200-0x207, size=0x8, align=0 pnpbios: handle 16 device ID CSC0001 (0100630e) pnpbios: handle 17 device ID CSC0003 (0300630e) pnpbios: handle 18 device ID IBM3760 (60374d24) pnpbios: handle 19 device ID IBM0071 (71004d24) PNP0e03: adding io range 0-0x1, size=0x2, align=0 pnpbios: handle 20 device ID PNP0e03 (030ed041) PNP0680: adding irq mask 0x4000 PNP0680: adding io range 0x1f0-0x1f7, size=0x8, align=0 PNP0680: adding io range 0x3f6-0x3f7, size=0x2, align=0 PNP0680: adding io range 0xfcf0-0xfcf7, size=0x8, align=0 pnpbios: handle 23 device ID PNP0680 (8006d041) PNP0680: adding irq mask 0x8000 PNP0680: adding io range 0x170-0x177, size=0x8, align=0 PNP0680: adding io range 0x376-0x376, size=0x1, align=0 PNP0680: adding io range 0xfcf8-0xfcff, size=0x8, align=0 pnpbios: handle 25 device ID PNP0680 (8006d041) PNP0c02: adding io range 0x2100-0x217f, size=0x80, align=0 PNP0c02: adding io range 0x2180-0x21ff, size=0x80, align=0 PNP0c02: adding fixed memory32 range 0xca000-0xcbfff, size=0x2000 pnpbios: handle 27 device ID PNP0c02 (020cd041) 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: