From owner-freebsd-hackers Mon Jan 1 6:21:29 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 06:21:27 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from izhost2.com (ns.izhost2.com [66.33.0.177]) by hub.freebsd.org (Postfix) with SMTP id 506DD37B400 for ; Mon, 1 Jan 2001 06:21:27 -0800 (PST) Received: (qmail 5187 invoked by uid 10352); 1 Jan 2001 13:52:54 -0000 Date: 1 Jan 2001 13:52:54 -0000 Message-ID: <20010101135254.5186.qmail@izhost2.com> To: hackers@FreeBSD.org From: Yonetici Subject: Huge Mp3 Sender: anonymous@izhost2.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Merhabalar.. http://www.hugemp3s.com Sitemizdeki yeniliklerden sizleri haberdar etmek istedik. Oncelikle mutlu yıllar herkese. ** AYSEGUL ALDINC in son Albumu NEFES i kendi serverımıza yukledin tam 12 parca ve hepsi kendi serverımızda. Artık her hafta bir turkce album eklenecektir. ** Yabancı Mp3 arsivi yenilendi Komik Mp3 ler bolumu acildi. Cem Yılmaz Bölümü acildi. Butun bolumler tekrar gozden gecirildi. istek mp3 leriniz icin mail atınız.. http://www.hugemp3s.com ------------------------------------------ Cover all of your mp3 needs. Huge Mp3 ( http://www.hugemp3s.com ) Full Mp3 Albums and Latest hit music mp3s All Mp3 Charts http://www.hugemp3s.com ------------------------------------------------------------------------- HUGE MP3 - http://www.hugemp3s.com Listeden Çıkmak için Aşağıdaki Linke Tıklayınız http://www.hugemp3s.com/mail.cgi??hackers@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 12:40:47 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 12:40:44 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (dyna225-140.nada.kth.se [130.237.225.140]) by hub.freebsd.org (Postfix) with ESMTP id 958C037B402 for ; Mon, 1 Jan 2001 12:40:43 -0800 (PST) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id VAA14886; Mon, 1 Jan 2001 21:40:30 +0100 (CET) (envelope-from assar) Sender: assar@assaris.sics.se To: Will Andrews Cc: hackers@FreeBSD.ORG Subject: Re: make(1) -DREMOTE? References: <20001226040133.N305@argon.firepipe.net> <20001230235109.R305@argon.firepipe.net> From: Assar Westerlund Date: 01 Jan 2001 21:40:30 +0100 In-Reply-To: Will Andrews's message of "Sat, 30 Dec 2000 23:51:10 -0500" Message-ID: <5lhf3jovk1.fsf@assaris.sics.se> Lines: 17 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews writes: > So from general consensus, people who desire this functionality can get > it from ports/devel/pmake and the (non-functional) -DREMOTE code can be > nuked from make(1). I was under the impression that not much development happened on (distributed) pmake, but there seems to be a 2.1.35beta at the ftp-site so it seems I was wrong on that. I do think some coordination feature-wise between FreeBSD make and pmake would be a good thing, but that's probably not much helped by having (I assume) older customs-code in FreeBSD make. So, assuming it's no problem for future syncing with customs pmake, I think ripping out the code is a good idea. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 12:40:48 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 12:40:43 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9040A37B400 for ; Mon, 1 Jan 2001 12:40:42 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id PAA16820; Mon, 1 Jan 2001 15:44:16 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010101152843.033da7f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 01 Jan 2001 15:44:13 -0500 To: "Bosko Milekic" , "Warner Losh" , "Taavi Talvik" From: Dennis Subject: Re: FreeBSD vs Linux, Solaris, and NT Cc: "Bill Fumerola" , "mouss" , "G. Adam Stanislav" , In-Reply-To: <002201c071df$3e97df00$25cbca18@jehovah> References: <5.0.0.25.0.20001229140715.009c2c10@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Core has stated in the past a strong desire for developers not to > > >break kernel interfaces within minor releases. > > > > > > 4.1 broke that "policy" rather badly. Perhaps its time to get rid of the > > mbuf macros, as any change to that structure breaks binary compatibility >in > > the worst way possible. > > > > DB > > The "problem" was not with the macros themselves, but with the fact that > your outdated binary was compiled with old definitions of some structures > which were later changed (mbstat structure). The changes that happened > there were relatively minor. I'm sure you would know all this had you > debugged the problem yourself, but it turns out that all you provided in > terms of "support" was whining and directing blame at the FreeBSD team. The entire point is that "relatively minor" changes will break a binary compiled for 4.1-RELEASE if -STABLE does not adhere to the principles of binary compatibility. If the code has to be recompiled to work safely, then binary compatibility is broken, for those of you who dont know what we are talking about here. A vendor cannot support every possible -STABLE release if binary compatibility is not maintained. Usually, -RELEASE compilations work across -STABLE. We didnt "whine", you whined. You tried to use an unsupported version of the OS and it didnt work. Surprise, surprise. > I disagree with not merging in fixes to -STABLE that help maintain code > in general, for the entire project; In this case, the change helped >userland code > such as netstat(1) deal with mbtypes. This wasn't a "big interface change" >by > any means. Plus, it was discussed on -net and since -net directly concerns >you > and your driver, perhaps you should read it every once in a while. Had we >not > merged this change to -STABLE, I'm sure we would have had just as many, if > not more requests: "MFC MFC, you guys are ignoring -STABLE!" as we > have now with you complaining about the change being made. A wise man > once said something along the lines: "you can never win with tire-kickers," > and now I see how he was right. Thats why there is a FreeBSD core team, so that only people that understand the principles of OS distribution are involved in the process. You can never make everyone happy, so you do whats correct and let the ignorant be unhappy. Its why companies develop policies, so they dont have to cater to every request individually. Not everyone will like every policy, but they are consistent so that order can be maintained. Do you see what happens when you give source code to amateurs? What a headache. His argument "make the change because people need it" is more of the LINUX camp mentality than what has been FreeBSD's policy. Its important to make the distinction. Stability is tantamount. Every time you make a change stabilty is potentially compromised. -STABLE should imply that stability is not at issue. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 14:51:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 14:51:17 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 662B637B400 for ; Mon, 1 Jan 2001 14:51:16 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f01MpBu05801; Mon, 1 Jan 2001 23:51:11 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id f01Mows18827; Mon, 1 Jan 2001 23:50:59 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <04ff01c07445$53563d20$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Dan Nelson" Cc: "FreeBSD hackers" References: <2620.978013915@critter> <20001228170241.D404@ringworld.oblivion.bg> <20001228092057.A15343@dan.emsphone.com> Subject: Re: Boot process robustness Date: Mon, 1 Jan 2001 23:45:03 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > If an fsck fails, ifconfig the interfaces and start an sshd so > > > people can get in remotely and fsck... > > > > What if an fsck on /usr fails? Other than that, I love the idea! > > Force-mount it read-only if necessary, or simply copy a static sshd > into /sbin. Runnning fsck -y is the wrong solution, since if fsck > can't fix an error automatically, something pretty bad has happened > (physical media error, someone dd'ing onto the raw disk, etc).. > Even so, unless the machine contains invaluable data, I guess 99% still does a fsck -y if fsck fails. I'd rather have my remote boxes do that by themselves, and perhaps email me, than I either have to drive there, or give somebody the root password, and remote control that person to just do fsck -y. In almost all cases, when a machine can't fsck itself after a power failure, a fsck -y fixes it. But then, most of the disk is either squid's cache, or unused stuff like termcaps, kernel source, man pages etc. Most stuff is there just because it could be handy one day, and it is not worth the trouble pruning it. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 18: 7: 8 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 18:07:06 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 3353F37B400 for ; Mon, 1 Jan 2001 18:07:06 -0800 (PST) Received: from FreeBSD.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA88829; Mon, 1 Jan 2001 18:06:18 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A513799.75EAB470@FreeBSD.org> Date: Mon, 01 Jan 2001 18:06:17 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: freebsd-hackers@FreeBSD.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > > [ ... reminder after two weeks of silence ... ] Two weeks of silence is generally enough to let you know that no one is interested in this modification. If someone was, they'd generally have said something by now. Speaking only for myself, I don't think your proposed changes are a good idea, which is why I refrained from offering any suggestions on how you can test them. Just so you wouldn't think you were being ignored, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 22: 0:11 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 22:00:05 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ticonet.co.cr (mail.ticonet.co.cr [196.40.4.5]) by hub.freebsd.org (Postfix) with ESMTP id 19CCF37B400; Mon, 1 Jan 2001 21:59:55 -0800 (PST) Received: from Popeye [196.40.53.184] by mail.ticonet.co.cr (SMTPD32-6.05) id AA4327B01DA; Mon, 01 Jan 2001 22:52:51 +0000 To: Happy@FreeBSD.ORG, New@FreeBSD.ORG, !!@Year.FreeBSD.ORG From: Oldies@FreeBSD.ORG, Online@FreeBSD.ORG, Casino@FreeBSD.ORG Subject: 01-01-2001 Date: Mon, 01 Jan 2001 23:59:16 -0600 Message-Id: <36892.999497453704000.238432@localhost> MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oldies Online Casino - Happy New Year!!!

Oldies Online Casino
Would like to welcome you and your family a Happy New Year!

We Would also like to offer ALL NEW & EXISTING Members a
Holiday 25% Bonus
Oldies Online Casino offers Free no download Flash Internet
gambling, games include craps, keno, slots, video poker,
roulette and blackjack in real time. Play for fun or cash!
http://www.oldiesonlinecasino.com

to unsubscribe click here

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 23:27:51 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 23:27:49 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id D24C937B400 for ; Mon, 1 Jan 2001 23:27:48 -0800 (PST) Received: from idem.sympatico.ca ([64.229.234.150]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010102072748.PAZZ18753.tomts8-srv.bellnexxia.net@idem.sympatico.ca> for ; Tue, 2 Jan 2001 02:27:48 -0500 Message-Id: <5.0.2.1.0.20010102022256.009fb870@pop6.sympatico.ca> X-Sender: b1gbfv75@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 02:28:58 -0500 To: hackers@freebsd.org From: =?iso-8859-1?Q?F=E9lix-Antoine?= Paradis Subject: ARP question. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When we do a "dmesg" on a 4.2-STABLE box, we get: arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 and, in ifconfig, it says: ed0: flags=8843 mtu 1500 inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 ether 00:e0:7d:7b:54:8a ed0 is connected to a switch. we want to know what the "arp: " message means. on the linux box, we have: eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:12738748 errors:0 dropped:0 overruns:0 frame:556 TX packets:4014499 errors:0 dropped:0 overruns:0 carrier:0 collisions:172394 txqueuelen:100 Interrupt:10 Base address:0xe800 eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3634104 errors:0 dropped:0 overruns:0 frame:4 TX packets:3842298 errors:0 dropped:0 overruns:0 carrier:0 collisions:197818 txqueuelen:100 Interrupt:12 Base address:0xec00 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 Both eth0 and eth1 are connected to that same switch. Thank's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 23:27:54 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 23:27:50 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id 239C737B402 for ; Mon, 1 Jan 2001 23:27:50 -0800 (PST) Received: from idem.sympatico.ca ([64.229.234.150]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010102072749.PBAE18753.tomts8-srv.bellnexxia.net@idem.sympatico.ca> for ; Tue, 2 Jan 2001 02:27:49 -0500 Message-Id: <5.0.2.1.0.20010102022929.00a10460@pop6.sympatico.ca> X-Sender: b1gbfv75@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 02:29:35 -0500 To: hackers@freebsd.org From: =?iso-8859-1?Q?F=E9lix-Antoine?= Paradis Subject: ARP question. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When we do a "dmesg" on a 4.2-STABLE box, we get: arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 and, in ifconfig, it says: ed0: flags=8843 mtu 1500 inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 ether 00:e0:7d:7b:54:8a ed0 is connected to a switch. we want to know what the "arp: " message means. on the linux box, we have: eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:12738748 errors:0 dropped:0 overruns:0 frame:556 TX packets:4014499 errors:0 dropped:0 overruns:0 carrier:0 collisions:172394 txqueuelen:100 Interrupt:10 Base address:0xe800 eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3634104 errors:0 dropped:0 overruns:0 frame:4 TX packets:3842298 errors:0 dropped:0 overruns:0 carrier:0 collisions:197818 txqueuelen:100 Interrupt:12 Base address:0xec00 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 Both eth0 and eth1 are connected to that same switch. Thank's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 23:28:13 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 23:28:09 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id E674237B400 for ; Mon, 1 Jan 2001 23:28:08 -0800 (PST) Received: from idem.sympatico.ca ([64.229.234.150]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010102072807.FVPZ1081.tomts7-srv.bellnexxia.net@idem.sympatico.ca> for ; Tue, 2 Jan 2001 02:28:07 -0500 Message-Id: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> X-Sender: b1gbfv75@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 02:30:16 -0500 To: hackers@freebsd.org From: =?iso-8859-1?Q?F=E9lix-Antoine?= Paradis Subject: ARP question. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When we do a "dmesg" on a 4.2-STABLE box, we get: arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 and, in ifconfig, it says: ed0: flags=8843 mtu 1500 inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 ether 00:e0:7d:7b:54:8a ed0 is connected to a switch. we want to know what the "arp: " message means. on the linux box, we have: eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:12738748 errors:0 dropped:0 overruns:0 frame:556 TX packets:4014499 errors:0 dropped:0 overruns:0 carrier:0 collisions:172394 txqueuelen:100 Interrupt:10 Base address:0xe800 eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3634104 errors:0 dropped:0 overruns:0 frame:4 TX packets:3842298 errors:0 dropped:0 overruns:0 carrier:0 collisions:197818 txqueuelen:100 Interrupt:12 Base address:0xec00 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 Both eth0 and eth1 are connected to that same switch. Thank's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 1 23:43:28 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 23:43:25 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C520D37B400 for ; Mon, 1 Jan 2001 23:43:25 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f027hOC10084; Mon, 1 Jan 2001 23:43:24 -0800 (PST) Date: Mon, 1 Jan 2001 23:43:24 -0800 From: Alfred Perlstein To: =?iso-8859-1?Q?F=E9lix-Antoine_Paradis?= Cc: hackers@FreeBSD.ORG Subject: Re: ARP question. Message-ID: <20010101234324.Z19572@fw.wintelcom.net> References: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca>; from reel@sympatico.ca on Tue, Jan 02, 2001 at 02:30:16AM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Félix-Antoine Paradis [010101 23:28] wrote: > Hi, > When we do a "dmesg" on a 4.2-STABLE box, we get: > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 > > and, in ifconfig, it says: > > ed0: flags=8843 mtu 1500 > inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 > inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 > ether 00:e0:7d:7b:54:8a > > ed0 is connected to a switch. we want to know what the "arp: " message > means. on the linux box, we have: > > eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 > inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:12738748 errors:0 dropped:0 overruns:0 frame:556 > TX packets:4014499 errors:0 dropped:0 overruns:0 carrier:0 > collisions:172394 txqueuelen:100 > Interrupt:10 Base address:0xe800 > eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3634104 errors:0 dropped:0 overruns:0 frame:4 > TX packets:3842298 errors:0 dropped:0 overruns:0 carrier:0 > collisions:197818 txqueuelen:100 > Interrupt:12 Base address:0xec00 > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > > Both eth0 and eth1 are connected to that same switch. You should check /var/log/messages for the datestamp. Basically it means someone took someone's arp address either by 1) taking the IP from a different machine. 2) telling a machine to change its hardware address. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 2: 0: 9 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 02:00:06 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id A8A8137B400 for ; Tue, 2 Jan 2001 02:00:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id NAA06781; Sat, 30 Dec 2000 13:06:25 GMT (envelope-from n_hibma@calcaphon.com) Date: Sat, 30 Dec 2000 13:06:25 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Jon Simola Cc: hackers@freebsd.org Subject: Re: Broken-by-design USB device? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The panic is definitely bad. It happens straight after failing the attach? If you could recompile the kernel with options DDB makeoptions DEBUG=-g plug the device in again, and after it has panicked (it will drop into the debugger), type trace. That would give me a hint at where it crashes. The controller probably requires some work because a fake report descriptor is needed to make it possible for the uhid driver to talk to it. It does not provide any information on where the information for the buttons and axes is stored in the descriptor returned on the interrupt pipe. Nick > I've got a little USB device that allows Playstation controllers to be > used on a PC. If it's plugged in while booting FreeBSD 4.2-RELEASE (the > shipped GENERIC kernel), I get: > > uhci0: port 0xd400-0xd41f irq 3 at > device 4.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhid0: vendor 0x6666 product 0x0667, rev 1.00/2.88, addr 2, iclass 3/0 > uhid0: no report descriptor > device_probe_and_attach: uhid0 attach returned 6 > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc012663a > stack pointer = 0x10:0xc044a938 > frame pointer = 0x10:0xc044a938 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault > Uptime: 0s > Automatic reboot in 15 seconds - press a key on the console to abort > > > After poking around in the uhid and usb code, I'm beginning to think that > this adapter is just broken by design. Can someone a bit more familiar > with the USB stuff comment on that? Thanks. > > For identifying what this is, there's not a lot of info available. It shows > up in Windows as a "Monster Gamepad" with 4 analog axis and 16 buttons, and > just has a single 20 pin DIPP chip inside with these markings (looks like a > PLA to me): > CY7C63000A-PC > 9946 G 02 518003 > > --- > Jon Simola | "In the near future - corporate networks > Systems Administrator | reach out to the stars, electrons and light > ABC Communications | flow throughout the universe." -- GITS > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 4: 1: 6 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 04:01:04 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 1363837B400 for ; Tue, 2 Jan 2001 04:01:04 -0800 (PST) Received: from way95.eng.tvol.net ([10.32.1.145]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YMS25FZ4; Tue, 2 Jan 2001 07:01:06 -0500 Received: from kway by way95.eng.tvol.net with local (Exim 3.20 #1 (Debian)) id 14DQ7d-0003jS-00; Tue, 02 Jan 2001 07:00:57 -0500 Date: Tue, 2 Jan 2001 07:00:57 -0500 From: Kevin Way To: Renaud Waldura Cc: freebsd-hackers@freebsd.org Subject: Re: Silent FreeBSD Message-ID: <20010102070057.A11829@way95.eng.tvol.net> References: <005801c07037$47ae6ea0$0402010a@biohz.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005801c07037$47ae6ea0$0402010a@biohz.net>; from renaud@waldura.com on Wed, Dec 27, 2000 at 11:00:29AM -0800 Organization: WorldGate Communications [www.wgate.com] Sender: Kevin Way Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable To solve this problem, I invested in one large, fast, fileserver and then= =20 ran the noise-critical machines diskless, with PXE boot. To deal with the= =20 noise of the fileserver, I bought an enclosed rack. My previous solutions which did an admirable job, were to: a) purchase the overly expensive, quiet power supplies (you can find them easily by going to google and searching for 'quiet power supply' or some such similar thing) b) run fans under standard voltage, with an underclocked CPU=20 c) use a small flash IDE device for boot d) use an old laptop Good luck! --=20 kevin way worldgate communications software engineer +1 215 354 5287 --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6UcL4kHXCCwlJQwURAtyCAJ42AYJADvUqngYbOLuNBXv/kTMTaACeIPuw TOrbvvbqQzRkrw5Sp9LsQTI= =CxJJ -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 4: 6:12 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 04:06:10 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 300A837B400 for ; Tue, 2 Jan 2001 04:06:07 -0800 (PST) Received: from cain.gsoft.com.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id WAA00468; Tue, 2 Jan 2001 22:35:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 02 Jan 2001 22:35:54 +1030 (CST) Sender: darius@cain.gsoft.com.au From: "Daniel O'Connor" To: Nick Hibma Subject: Re: Broken-by-design USB device? Cc: hackers@freebsd.org, Jon Simola Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-00 Nick Hibma wrote: > > For identifying what this is, there's not a lot of info available. It shows > > up in Windows as a "Monster Gamepad" with 4 analog axis and 16 buttons, and > > just has a single 20 pin DIPP chip inside with these markings (looks like a > > PLA to me): > > CY7C63000A-PC > > 9946 G 02 518003 FYI that part is made by Cypress... Basically it is an 8051 core with a low speed USB engine attached. The data sheet is at http://www.cypress.com/usb/lowspeed/cy7c63xxxa.html but it's not going to be much help without knowing how the firmware is coded. --- 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-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 6:17:26 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 06:17:23 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 956A937B400 for ; Tue, 2 Jan 2001 06:17:22 -0800 (PST) Received: (qmail 25116 invoked by uid 0); 2 Jan 2001 14:17:20 -0000 Received: from p3ee2162b.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.43) by mail.gmx.net (mail08) with SMTP; 2 Jan 2001 14:17:20 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id MAA12702 for freebsd-hackers@FreeBSD.org; Tue, 2 Jan 2001 12:52:47 +0100 Date: Tue, 2 Jan 2001 12:52:47 +0100 From: Gerhard Sittig To: freebsd-hackers@FreeBSD.org Subject: Re: OT: silence as an answer? (was: how to test out cron.c changes?) Message-ID: <20010102125247.U253@speedy.gsinet> References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A513799.75EAB470@FreeBSD.org>; from DougB@FreeBSD.org on Mon, Jan 01, 2001 at 06:06:17PM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ this message is no personal affront against you, Doug, but an expression of what feeling this kind of behaviour causes for those who want to share and find themselves ignored ] On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote: > Gerhard Sittig wrote: > > > > [ ... reminder after two weeks of silence ... ] > > Two weeks of silence is generally enough to let you know that > no one is interested in this modification. If someone was, > they'd generally have said something by now. Well, I don't come to the same conclusion here as you do and I'm not so sure about it as you are. :) Silence as I see it is just a sign for "nobody answered", without a reason to see why. It could be work load or being offline or getting side tracked or whatever as well as being not interested or disagreeing. And finally I want to take the lack of disagreement (or the absence of its statement) as a sign for "it's not completely wrong what I want to do here". It could even be that the method of searching for contact or the way the proposal was presented has been wrong (in the past I had to learn that Jordan is more of a programmer and obviously is better at reading source than prose, so citing few lines of code had been more clear than one sentence "'cvs diff ... ' moved the test upwards and solved the panic":). At the moment I would like to believe that I just made a mistake in my proposal and that there is some kind of interest or serious rejection. BTW is rejection much more the kind of reaction I had expected in the case you describe (nobody wants it). This would have been at least *some* reaction. Getting ignored is definitely a fine way of discouraging future contributions. Some "we don't like the approach, since ..." or a simple "Nope" or even a serious "PLONK!" would have been great and as much appreciated as an "yes, we like it"! It had saved time and work for _everyone_ involved (me as being the originator as well as those I had to annoy repeatedly when they could have stopped me right in the beginning). The experience will make me think twice next time if I'm in the mood of spending my resources in the will to help and contribute just to find myself sitting there ignored. Would I really feel like having this kind of conversation, I could as well open my fridge and talk to it ... :-| > Speaking only for myself, I don't think your proposed changes > are a good idea, which is why I refrained from offering any > suggestions on how you can test them. Well, this has been the very first and most important the only response. After I offered help in public to solve an "eternal problem" and spent some effort on it ... I'll start one more try (the last on this proposal) in a separate message in the hope that this OT message won't start a new thread or in case it should the thread would die really soon. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 6:17:38 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 06:17:33 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 7AF8337B404 for ; Tue, 2 Jan 2001 06:17:27 -0800 (PST) Received: (qmail 25140 invoked by uid 0); 2 Jan 2001 14:17:21 -0000 Received: from p3ee2162b.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.43) by mail.gmx.net (mail08) with SMTP; 2 Jan 2001 14:17:21 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id NAA12722 for freebsd-hackers@FreeBSD.org; Tue, 2 Jan 2001 13:32:39 +0100 Date: Tue, 2 Jan 2001 13:32:39 +0100 From: Gerhard Sittig To: freebsd-hackers@FreeBSD.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Message-ID: <20010102133239.V253@speedy.gsinet> References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A513799.75EAB470@FreeBSD.org>; from DougB@FreeBSD.org on Mon, Jan 01, 2001 at 06:06:17PM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote: > > Speaking only for myself, I don't think your proposed changes > are a good idea, which is why I refrained from offering any > suggestions on how you can test them. Your refusal(id?) has been the only response so far and it didn't sound very clear / determined / explained (sorry, I lack better words) to me. :) So I guess the wording I used "DST handling in cron" was not done luckily. Let me cite from the doc diff: ----------------------------------------------------------------- --- /usr/src/usr.sbin/cron/cron/cron.8 1999/08/28 01:15:49 1.7 +++ /usr/src/usr.sbin/cron/cron/cron.8 2000/12/03 12:44:53 @@ -68,6 +68,25 @@ .Xr crontab 1 command updates the modtime of the spool directory whenever it changes a crontab. +.Pp +Special considerations exist when the clock is changed by less than 3 +hours; for example, at the beginning and end of Daylight Saving +Time. +If the time has moved forward, those jobs which would have +run in the time that was skipped will be run soon after the change. +Conversely, if the time has moved backward by less than 3 hours, +those jobs that fall into the repeated time will not be run. +.Pp +Only jobs that run at a particular time (not specified as @hourly, nor with +.Ql * +in the hour or minute specifier) +are +affected. +Jobs which are specified with wildcards are run based on the +new time immediately. +.Pp +Clock changes of more than 3 hours are considered to be corrections to +the clock, and the new time is used immediately. .Sh SEE ALSO .Xr crontab 1 , .Xr crontab 5 ----------------------------------------------------------------- This modification (obtained from OpenBSD) handles any situation where system time will jump just a little (assuming you're willing to refer to three hours as "just a little" while talking about computers:). Think of administrators' intervention by means of date(8) or netdate(1) for manual correction. Or maybe DST changes, which are just a special case thereof. And yes, it sounds a little like the anacron method of keeping up with scheduled jobs while the machine hasn't been available continuously. But admittedly DST changes are the cause of permanently upcoming discussions twice a year that cron(8) is broken or crontab(5) needs correction -- with (always the same) result that touching the crontab database cannot solve the problem. And the latest commits to crontab that still didn't satisfy every region FreeBSD users live in were what triggered my wish to stuff the "intelligence" into cron(8) and live in peace for good (at least in this respect). Of course we could wait another few months to have the discussion come up once more (and to know for sure it will again and again). But I'd rather have some feedback whether the problem could be solved before the effect strikes again and whether it's worth to spend any more time on providing fixes people actually don't want to get in the end. Is there anyone out there who feels like rejecting the proposal for a *reason*? Or to accept the idea, but to redirect the effort to a "real solution"? I somehow doubt you'd rather explain again and again that cron(8) isn't broken but that users should shuffle around the daily job's execution time ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 6:31: 6 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 06:31:03 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 2F6FD37B400 for ; Tue, 2 Jan 2001 06:31:00 -0800 (PST) Received: (qmail 69310 invoked by uid 1003); 2 Jan 2001 14:30:55 -0000 Date: Tue, 2 Jan 2001 16:30:55 +0200 From: Neil Blakey-Milner To: Gerhard Sittig Cc: freebsd-hackers@FreeBSD.org Subject: Re: OT: silence as an answer? (was: how to test out cron.c changes?) Message-ID: <20010102163055.A65068@mithrandr.moria.org> References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102125247.U253@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102125247.U253@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Tue, Jan 02, 2001 at 12:52:47PM +0100 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: nbm@rucus.ru.ac.za Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 2001-01-02 (12:52), Gerhard Sittig wrote: > On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote: > > Gerhard Sittig wrote: > > > > > > [ ... reminder after two weeks of silence ... ] > > > > Two weeks of silence is generally enough to let you know that > > no one is interested in this modification. If someone was, > > they'd generally have said something by now. > > Well, I don't come to the same conclusion here as you do and I'm > not so sure about it as you are. :) Silence as I see it is just > a sign for "nobody answered", without a reason to see why. It > could be work load or being offline or getting side tracked or > whatever as well as being not interested or disagreeing. And > finally I want to take the lack of disagreement (or the absence > of its statement) as a sign for "it's not completely wrong what I > want to do here". I tend to agree here - silence could mean many things. In this case, I can't see why people wouldn't want this - it's something that gets brought up time and again. > The experience will make me think twice next time if I'm in the > mood of spending my resources in the will to help and contribute > just to find myself sitting there ignored. Would I really feel > like having this kind of conversation, I could as well open my > fridge and talk to it ... :-| I think we can put this current silence down to holidays and getting sidetracked while trying to think of a reply - the question isn't particularly easy to answer, and people don't generally answer "I don't know". (: I remember reading this, and thinking "gee, what _is_ a good way to test DST changes?", and then promptly forgetting about it, because I never really deal with DST changes. I think the only way is the hard way - changing the date in increments and testing whether extra or no jobs are run. Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 6:34: 2 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 06:34:00 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 0551537B400 for ; Tue, 2 Jan 2001 06:34:00 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 21863322A; Tue, 2 Jan 2001 14:33:57 +0000 (GMT) Date: Tue, 2 Jan 2001 14:33:57 +0000 From: Josef Karthauser To: freebsd-hackers@FreeBSD.ORG Subject: Reprobing the ATAPI bus. Message-ID: <20010102143357.F1391@tao.org.uk> Mail-Followup-To: Josef Karthauser , freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know how to reprobe the ATAPI bus, e.g. for a cd rom drive in a laptop that wasn't present during boot? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 6:50:40 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 06:50:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 36E5237B400 for ; Tue, 2 Jan 2001 06:50:37 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA39669; Tue, 2 Jan 2001 15:50:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101021450.PAA39669@freebsd.dk> Subject: Re: Reprobing the ATAPI bus. In-Reply-To: <20010102143357.F1391@tao.org.uk> from Josef Karthauser at "Jan 2, 2001 02:33:57 pm" To: joe@tao.org.uk (Josef Karthauser) Date: Tue, 2 Jan 2001 15:50:34 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Josef Karthauser wrote: > Does anyone know how to reprobe the ATAPI bus, e.g. for a cd rom drive > in a laptop that wasn't present during boot? Yes :) Most of the code is already in the ATA driver, but the ioctl's and the atacontrol program is still only here in my lab due to lack of time... I hope to be able to devote enough time to this soon, I'm currently looking into having some of my time for this being sponsored... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 7: 3:15 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 07:03:12 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id B36B537B400 for ; Tue, 2 Jan 2001 07:03:10 -0800 (PST) Received: from kampala-08.budapest.interware.hu ([195.70.52.200] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14DSxw-0002Sp-00; Tue, 02 Jan 2001 16:03:09 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A51ED5D.F5724A99@elischer.org> Date: Tue, 02 Jan 2001 07:01:49 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Alfred Perlstein Cc: =?iso-8859-1?Q?F=E9lix=2DAntoine?= Paradis , hackers@FreeBSD.ORG Subject: Re: ARP question. References: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> <20010101234324.Z19572@fw.wintelcom.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Félix-Antoine Paradis [010101 23:28] wrote: > > Hi, > > When we do a "dmesg" on a 4.2-STABLE box, we get: > > > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 > > > > and, in ifconfig, it says: > > > > ed0: flags=8843 mtu 1500 > > inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 > > inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 > > ether 00:e0:7d:7b:54:8a > > > > ed0 is connected to a switch. we want to know what the "arp: " message > > means. on the linux box, we have: > > > > eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 > > inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:12738748 errors:0 dropped:0 overruns:0 frame:556 > > TX packets:4014499 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:172394 txqueuelen:100 > > Interrupt:10 Base address:0xe800 > > eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 > > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:3634104 errors:0 dropped:0 overruns:0 frame:4 > > TX packets:3842298 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:197818 txqueuelen:100 > > Interrupt:12 Base address:0xec00 > > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > > > > Both eth0 and eth1 are connected to that same switch. If they are receiving each other's broadcasts then arp will get upset. (As you noticed) > > You should check /var/log/messages for the datestamp. > > Basically it means someone took someone's arp address either by > 1) taking the IP from a different machine. > 2) telling a machine to change its hardware address. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 7:30: 5 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 07:30:01 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id D981A37B400 for ; Tue, 2 Jan 2001 07:29:57 -0800 (PST) Received: (qmail 8838 invoked from network); 2 Jan 2001 15:29:55 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 2 Jan 2001 15:29:55 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id VAA32213; Tue, 2 Jan 2001 21:29:26 +0600 Date: Tue, 2 Jan 2001 21:29:26 +0600 (NOVT) From: Alexey Dokuchaev To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SecureBSD In-Reply-To: <3A4CD69A.96F81141@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Dec 2000, Wes Peters wrote: > > You may want to look at http://www.trustedbsd.org/ as well. It is provided > under the Berkeley license, and much of what is developed there will be > folded into FreeBSD as time permits. The primary author of TrustedBSD is > Robert Watson, who is now a FreeBSD Core Team member as well. > Actually, TrustedBSD seems to be in very early stages of development. For now, I've decided that the best solution for me would be `spy' KLD (www.freebsd.org -> projects -> SPY). //danfe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 8:15:22 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 08:15:20 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id BCFD437B400 for ; Tue, 2 Jan 2001 08:15:19 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 98306315F; Tue, 2 Jan 2001 16:15:16 +0000 (GMT) Date: Tue, 2 Jan 2001 16:15:16 +0000 From: Josef Karthauser To: Soren Schmidt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reprobing the ATAPI bus. Message-ID: <20010102161516.F592@tao.org.uk> Mail-Followup-To: Josef Karthauser , Soren Schmidt , freebsd-hackers@FreeBSD.ORG References: <20010102143357.F1391@tao.org.uk> <200101021450.PAA39669@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101021450.PAA39669@freebsd.dk>; from sos@freebsd.dk on Tue, Jan 02, 2001 at 03:50:34PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 03:50:34PM +0100, Soren Schmidt wrote: > It seems Josef Karthauser wrote: > > Does anyone know how to reprobe the ATAPI bus, e.g. for a cd rom drive > > in a laptop that wasn't present during boot? > > Yes :) > > Most of the code is already in the ATA driver, but the ioctl's and > the atacontrol program is still only here in my lab due to lack > of time... > > I hope to be able to devote enough time to this soon, I'm currently > looking into having some of my time for this being sponsored... I'll sponser you. How about a penny per line of code :). I'll just reboot then whilst I wait.... ;p Thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 8:22:18 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 08:22:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id B997237B400 for ; Tue, 2 Jan 2001 08:22:11 -0800 (PST) Received: (cpmta 17830 invoked from network); 2 Jan 2001 08:22:02 -0800 Received: from m12hRs4n205.midsouth.rr.com (HELO mike) (24.95.125.205) by smtp.valuedata.net (209.228.12.67) with SMTP; 2 Jan 2001 08:22:02 -0800 X-Sent: 2 Jan 2001 16:22:02 GMT Message-ID: <008a01c074d8$24691bc0$0200000a@mike> From: "Daryl Chance" To: "FreeBSD Hackers" Cc: "Josef Karthauser" , "Soren Schmidt" References: <20010102143357.F1391@tao.org.uk> <200101021450.PAA39669@freebsd.dk> <20010102161516.F592@tao.org.uk> Subject: Re: Reprobing the ATAPI bus. Date: Tue, 2 Jan 2001 10:22:02 -0600 Organization: ValueData, LLC MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That could look/get ugly..... if ( retval == -1 ) { // blah } hehe ;P - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out of? Memphis, TN | - http://www.thinkgeek.com ----- Original Message ----- From: "Josef Karthauser" To: "Soren Schmidt" Cc: Sent: Tuesday, January 02, 2001 10:15 AM Subject: Re: Reprobing the ATAPI bus. > On Tue, Jan 02, 2001 at 03:50:34PM +0100, Soren Schmidt wrote: > > It seems Josef Karthauser wrote: > > > Does anyone know how to reprobe the ATAPI bus, e.g. for a cd rom drive > > > in a laptop that wasn't present during boot? > > > > Yes :) > > > > Most of the code is already in the ATA driver, but the ioctl's and > > the atacontrol program is still only here in my lab due to lack > > of time... > > > > I hope to be able to devote enough time to this soon, I'm currently > > looking into having some of my time for this being sponsored... > > I'll sponser you. How about a penny per line of code :). > > I'll just reboot then whilst I wait.... ;p > > Thanks, > Joe > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 8:35:49 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 08:35:48 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 08DC037B400 for ; Tue, 2 Jan 2001 08:35:48 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id EA02E315F; Tue, 2 Jan 2001 16:35:39 +0000 (GMT) Date: Tue, 2 Jan 2001 16:35:39 +0000 From: Josef Karthauser To: Daryl Chance Cc: FreeBSD Hackers , Soren Schmidt Subject: Re: Reprobing the ATAPI bus. Message-ID: <20010102163538.G592@tao.org.uk> Mail-Followup-To: Josef Karthauser , Daryl Chance , FreeBSD Hackers , Soren Schmidt References: <20010102143357.F1391@tao.org.uk> <200101021450.PAA39669@freebsd.dk> <20010102161516.F592@tao.org.uk> <008a01c074d8$24691bc0$0200000a@mike> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <008a01c074d8$24691bc0$0200000a@mike>; from dchance@valuedata.net on Tue, Jan 02, 2001 at 10:22:02AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 10:22:02AM -0600, Daryl Chance wrote: > That could look/get ugly..... > > if > ( > retval > == > -1 > ) > { > // blah > } > > hehe ;P He only gets paid if it conforms to style(9) Heh :b. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 8:41:10 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 08:41:07 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id B1A7B37B400 for ; Tue, 2 Jan 2001 08:41:06 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14DUaS-00005m-00; Tue, 02 Jan 2001 09:47:00 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A520604.39F63679@softweyr.com> Date: Tue, 02 Jan 2001 09:47:00 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?F=E9lix=2DAntoine?= Paradis Cc: hackers@freebsd.org Subject: Re: ARP question. References: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Félix-Antoine Paradis wrote: > > Hi, > When we do a "dmesg" on a 4.2-STABLE box, we get: > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 This means exactly what is says: IP address 200.42.126.18 was originally associated with ethernet MAC address ...:53:f0, but has moved to ...:ac:05. > > and, in ifconfig, it says: > > ed0: flags=8843 mtu 1500 > inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 > inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 > ether 00:e0:7d:7b:54:8a > > ed0 is connected to a switch. we want to know what the "arp: " message > means. on the linux box, we have: > > eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 > inet addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 Yes, this interface is now showing what ARP reported above. > eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 And this one is not. > Both eth0 and eth1 are connected to that same switch. Did the Linux box reboot when you got the ARP message? If so, the Linux box has reversed the order of the ethernet interfaces. If not, the Linux box is routing packets over the wrong interface, which can happen when you have two networks mingled together like this. What kind of switch is this? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 8:54:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 08:54:40 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CC3A237B400 for ; Tue, 2 Jan 2001 08:54:39 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA69185; Tue, 2 Jan 2001 17:54:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101021654.RAA69185@freebsd.dk> Subject: Re: Reprobing the ATAPI bus. In-Reply-To: <20010102163538.G592@tao.org.uk> from Josef Karthauser at "Jan 2, 2001 04:35:39 pm" To: joe@tao.org.uk (Josef Karthauser) Date: Tue, 2 Jan 2001 17:54:34 +0100 (CET) Cc: dchance@valuedata.net (Daryl Chance), freebsd-hackers@freebsd.org (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Josef Karthauser wrote: > > He only gets paid if it conforms to style(9) Heh :b. Just forget about it then, and be patient :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 9:13:52 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 09:13:50 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.nettoll.com (matrix.nettoll.net [212.155.143.61]) by hub.freebsd.org (Postfix) with ESMTP id 5A3BC37B402 for ; Tue, 2 Jan 2001 09:13:48 -0800 (PST) Received: by smtp.nettoll.com; Tue, 2 Jan 2001 18:11:16 +0100 (MET) Message-Id: <4.3.0.20010102180455.055ed100@pop.free.fr> X-Sender: usebsd@pop.free.fr X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 02 Jan 2001 18:20:08 +0100 To: "Marco van de Voort" , hackers@freebsd.org From: mouss Subject: Re: FreeBSD vs Linux, Solaris, and NT In-Reply-To: <20001229193646.49F822E802@hermes.tue.nl> References: <4.3.0.20001228192610.054d4570@pop.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 20:29 29/12/00 +0100, Marco van de Voort wrote: >Perfect for your purposes. I, as user (and with some machines >running on FreeBSD), want to be able to rebuild the kernel at any >time, and fix myself when needed. I don't want any binary packages >that can cause trouble and delay days. before working for a com company, I'm a BSD user, and my participation to this list is from this point of view. I've never asked for any modifications that would make user's life harder. note that I've not asked for any modifs, I just "started" the question. >You mean some base support in makefiles to make patching easier? >In general: No problem with that. well, I was meaning a patch to config and to some makefiles. why config? I find it annoying that config must be run in $arch/conf, with the exact config filename, and that either one has to be root or he has to copy kernel sources. the config program requires that you run it in ${sys}/$arch/conf and that you give it a "pure" filename. "config /sys/i386/conf/GENERIC" doesn't work! This is because it needs three dirs: the ${sys}/$arch/conf, the ${sys}/conf and the ${sys}/compile. but I still believe this is an old heritage that may be easily "fixed". >In specific cases: No. As a BSD user, I'll never ask for specific stuff, be it for a company I work for:) my discussion was about how to ease 3d party stuff in BSD, not how to make any company or anybody happy by any sacrificial modifs. The problem I was talking about is that if every company modifies the kernel sources or the build procedure in its own way, then the least of the things that happen is that the modifications are not compatible, which is not good. now, let's forget about companies and about any commercial entities. There are things to improve in BSD (though it's perfect:). and among those, the possibility for extensibility, be it by single developpers, by commercial companies, or by anyone on earth. The question is not who does what, the real question is how anything is done. if that is good, it's good and we oughtta take it. if it's bad, we'd better reject it. cheers, mouss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 9:17:41 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 09:17:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.smed.com (unknown [64.46.248.11]) by hub.freebsd.org (Postfix) with ESMTP id E6A5337B400 for ; Tue, 2 Jan 2001 09:17:37 -0800 (PST) Received: from smtpgate.shrmed.com (unknown [64.46.248.2]) by smtp.smed.com (Postfix) with ESMTP id 6C33D16291 for ; Tue, 2 Jan 2001 12:17:37 -0500 (EST) Received: from iesa14.shrmed.com (iesa14.shrmed.com [10.1.99.114]) by smtpgate.shrmed.com (8.9.3/8.9.3) with ESMTP id MAA18256 for ; Tue, 2 Jan 2001 12:17:37 -0500 From: Joe.Warner@smed.com Received: from Deimos.smed.com (unverified) by iesa14.shrmed.com (Content Technologies SMTPRS 2.0.15) with SMTP id for ; Tue, 02 Jan 2001 12:17:32 -0500 Received: by Deimos.smed.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852569C8.005EC79E ; Tue, 2 Jan 2001 12:15:14 -0500 X-Lotus-FromDomain: SMS To: freebsd-hackers@freebsd.org Message-Id: <852569C8.005EC622.00@Deimos.smed.com> Date: Tue, 2 Jan 2001 10:17:58 -0700 Subject: Problems with FreeBSD 4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I installed FreeBSD 4.2 on my home PC last week and everything installed fine except for the desktop managers. When I tried to install KDE, I got the following errors: >Add of package xpm-3.4k aborted, error code 1- >Please check the debug screen for more info >acd0: READ_BIG_MEDIUM ERROR asc=11 >ascq=05 error=00 >Loading of dependant package xpm-3.4k failed >Loading of dependant package kdebase -1.1.2.1 failed In fact, I got these errors when trying to install any of the desktop managers. Could I have received a bad copy (on CD) of FreeBSD 4.2? Would it be possible to use /stand/sysinstall and load KDE from my old 3.4 CD ROM set? Any info would be appreciated. Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 9:33:37 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 09:33:36 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id C7DAC37B400 for ; Tue, 2 Jan 2001 09:33:35 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 6C53D322A; Tue, 2 Jan 2001 17:26:29 +0000 (GMT) Date: Tue, 2 Jan 2001 17:26:29 +0000 From: Josef Karthauser To: Soren Schmidt Cc: Daryl Chance , FreeBSD Hackers Subject: Re: Reprobing the ATAPI bus. Message-ID: <20010102172629.J592@tao.org.uk> Mail-Followup-To: Josef Karthauser , Soren Schmidt , Daryl Chance , FreeBSD Hackers References: <20010102163538.G592@tao.org.uk> <200101021654.RAA69185@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101021654.RAA69185@freebsd.dk>; from sos@freebsd.dk on Tue, Jan 02, 2001 at 05:54:34PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 05:54:34PM +0100, Soren Schmidt wrote: > It seems Josef Karthauser wrote: > > > > He only gets paid if it conforms to style(9) Heh :b. > > > Just forget about it then, and be patient :) Oh go on then :) I'll pay you anyway :). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 9:47: 4 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 09:47:02 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tomts6-srv.bellnexxia.net (smtp.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id B3FEF37B400 for ; Tue, 2 Jan 2001 09:47:01 -0800 (PST) Received: from idem.sympatico.ca ([64.229.234.150]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010102174700.ITKU16490.tomts6-srv.bellnexxia.net@idem.sympatico.ca>; Tue, 2 Jan 2001 12:47:00 -0500 Message-Id: <5.0.2.1.0.20010102124838.009efec0@pop6.sympatico.ca> X-Sender: b1gbfv75@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 12:49:15 -0500 To: Wes Peters From: =?iso-8859-1?Q?F=E9lix-Antoine?= Paradis Subject: Re: ARP question. Cc: hackers@freebsd.org In-Reply-To: <3A520604.39F63679@softweyr.com> References: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:47 01-01-02 -0700, you wrote: >F=E9lix-Antoine Paradis wrote: > > > > Hi, > > When we do a "dmesg" on a 4.2-STABLE box, we get: > > > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on= ed0 > >This means exactly what is says: IP address 200.42.126.18 was originally >associated with ethernet MAC address ...:53:f0, but has moved to ...:ac:05. > > > > and, in ifconfig, it says: > > > > ed0: flags=3D8843 mtu 1500 > > inet 200.42.126.20 netmask 0xffffff00 broadcast 200.42.126.255 > > inet6 fe80::2e0:7dff:fe7b:548a%ed0 prefixlen 64 scopeid 0x1 > > ether 00:e0:7d:7b:54:8a > > > > ed0 is connected to a switch. we want to know what the "arp: " message > > means. on the linux box, we have: > > > > eth0 Link encap:Ethernet HWaddr 00:C0:DF:F4:AC:05 > > inet=20 > addr:200.42.126.18 Bcast:200.42.126.23 Mask:255.255.255.248 > >Yes, this interface is now showing what ARP reported above. > > > eth1 Link encap:Ethernet HWaddr 00:E0:7D:7B:53:F0 > > inet addr:192.168.1.1 Bcast:192.168.1.255 = Mask:255.255.255.0 > >And this one is not. > > > Both eth0 and eth1 are connected to that same switch. > >Did the Linux box reboot when you got the ARP message? If so, the Linux >box has reversed the order of the ethernet interfaces. If not, the Linux >box is routing packets over the wrong interface, which can happen when you >have two networks mingled together like this. What kind of switch is this? It is a Catalyst 2900 XL Series >-- > "Where am I, and what am I doing in this handbasket?" > >Wes=20 >Peters Softweyr LLC >wes@softweyr.com=20 >http://softweyr.com/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 9:55:28 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 09:55:26 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 21A8D37B402 for ; Tue, 2 Jan 2001 09:55:26 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id MAA04182 for ; Tue, 2 Jan 2001 12:55:25 -0500 (EST) Date: Tue, 2 Jan 2001 12:55:24 -0500 (EST) From: Zhiui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: kernel debugging suggestion needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have written a KLD and am debugging it. The program often hangs after runs for a while (I guess it enters into some dead loop). Is there a way to attach to the process and somehow find out which code it is executing (with remote debugging or ddb)? Thanks for your help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 10:17:11 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 10:17:00 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mxbh4.isus.emc.com (mxbh4.isus.emc.com [168.159.208.52]) by hub.freebsd.org (Postfix) with ESMTP id C894237B400 for ; Tue, 2 Jan 2001 10:16:59 -0800 (PST) Received: by mxbh4.isus.emc.com with Internet Mail Service (5.5.2650.21) id ; Tue, 2 Jan 2001 13:16:54 -0500 Message-ID: <0BEC2FAE2A21D411965C00E0291E7C3340BFC2@corpmx17.isus.emc.com> From: Neff_Glen@emc.com To: hackers@freebsd.org Cc: JONESJG@dg-rtp.dg.com, stovall@dg-rtp.dg.com, davenport_ken@emc.com Subject: Problems with sf driver? Date: Tue, 2 Jan 2001 13:17:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I administer a box running v4.2-stable with a pair of the Adaptec ANA-62044 64-bit PCI, Quad port ethernet adapters. Six of the eight ethernet ports are in use. The box routes traffic between five private networks and provides NAT services out the public world on the sixth interface. I encounter an intermittant problem where one of the ports on a private network will quit functioning (usually sf2 or sf3). Nothing on that segment can reach the machine and if I try to ping something on that segment from the box in question I get: ping: sendto: No buffer space available The other five ports in use on the system continue to function normally. If I "ifconfig sfX down/up" the problem goes away. I've seen the problem as often as twice a day and sometimes gone a month without seeing it. The private segments carry very heavy SMB traffic. I have upped NMBCLUSTERS to 8192 with no success. Influenced by what I found digging though the DejaNews archives, I have also increased maxusers from 32 to 128, but do not believe the box has been up long enough to see if this has made a difference or not. Since these settings are global to the OS and I'm only encountering a problem with one port at a time, while the others continue to function normally, I have doubts they are an issue and suspect is must be a problem with the sf driver itself. I have swapped-out the NICs, the PC, and encountered the same problem with v3.x-stable. Thanks for any help you might offer. Below I'll paste some pertinate system configuration info. -G /* Glen R. J. Neff neff_glen@emc.com 919-248-6145 Dirty deeds done for a meager 20% markup. . . */ uname -a output: FreeBSD squeakyfromme.rtp.dg.com 4.2-STABLE FreeBSD 4.2-STABLE #1: Tue Jan 2 11:36:03 EST 2001 root@squeakyfromme.rtp.dg.com:/usr/src/sys/compile/squeakyfromme i386 Kernel config file: machine i386 # cpu I386_CPU # cpu I486_CPU # cpu I586_CPU cpu I686_CPU ident squeakyfromme maxusers 128 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking # options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem # options MD_ROOT #MD is a potential root device options NFS #Network Filesystem # options NFS_ROOT #NFS usable as root device, NFS required # options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem # options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] # options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # Added to to TX buffer problems with so many NICs. options NMBCLUSTERS=8192 # Required for NATd to function options IPFIREWALL options IPDIVERT # Required for port fowarding? # options IPFILTER # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa # device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives # device atapifd # ATAPI floppy drives # device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers # RAID controllers # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 # device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) # device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # device sio2 at isa? disable port IO_COM3 irq 5 # device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer # device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. # device de # DEC/Intel DC21x4x (``Tulip'') # device fxp # Intel EtherExpress PRO/100B (82557, 82558) # device tx # SMC 9432TX (83c170 ``EPIC'') # device vx # 3Com 3c590, 3c595 (``Vortex'') # device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support # device dc # DEC/Intel 21143 and various workalikes # device pcn # AMD Am79C79x PCI 10/100 NICs # device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') # device sis # Silicon Integrated Systems SiS 900/SiS 7016 # device ste # Sundance ST201 (D-Link DFE-550TX) # device tl # Texas Instruments ThunderLAN # device vr # VIA Rhine, Rhine II # device wb # Winbond W89C840F # device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 # device ex # device ep # device fe0 at isa? port 0x300 # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. # device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. # device an # Xircom Ethernet # device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. # device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 # device lnc0 at isa? port 0x280 irq 10 drq 0 # device cs0 at isa? port 0x300 # device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support # pseudo-device sl 1 # Kernel SLIP # pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" # pseudo-device gif 4 # IPv6 and IPv4 tunneling # pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # pseudo-device bpf #Berkeley packet filter rc.conf: sendmail_enable="YES" saver="daemon" blanktime="180" font8x8="swiss-8x8" font8x14="NO" font8x16="swiss-8x16" keyrate="fast" sshd_enable="YES" inetd_enable="YES" network_interfaces="sf0 sf5 sf4 sf3 sf2 sf1 lo0" ifconfig_sf0="inet 128.222.25.114 netmask 255.255.255.0" ifconfig_sf5="inet 10.2.24.3 netmask 255.255.255.0" ifconfig_sf4="inet 10.2.23.4 netmask 255.255.255.0" ifconfig_sf3="inet 10.2.22.4 netmask 255.255.255.0" ifconfig_sf2="inet 10.2.21.4 netmask 255.255.255.0" ifconfig_sf1="inet 10.2.20.4 netmask 255.255.255.0" defaultrouter="128.222.25.253" hostname="squeakyfromme.rtp.dg.com" usbd_enable="NO" gateway_enable="YES" firewall_enable="YES" natd_enable="YES" natd_flags="-s -m" natd_interface="sf0" rc.firewall: /sbin/ipfw -f flush /sbin/ipfw add divert natd all from any to any via sf0 /sbin/ipfw add pass all from any to any To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 10:19:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 10:19:41 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B098D37B400 for ; Tue, 2 Jan 2001 10:19:40 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f02IJbL26250; Tue, 2 Jan 2001 10:19:37 -0800 (PST) Date: Tue, 2 Jan 2001 10:19:37 -0800 From: Alfred Perlstein To: Neff_Glen@emc.com Cc: hackers@FreeBSD.ORG, JONESJG@dg-rtp.dg.com, stovall@dg-rtp.dg.com, davenport_ken@emc.com Subject: Re: Problems with sf driver? Message-ID: <20010102101937.U19572@fw.wintelcom.net> References: <0BEC2FAE2A21D411965C00E0291E7C3340BFC2@corpmx17.isus.emc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0BEC2FAE2A21D411965C00E0291E7C3340BFC2@corpmx17.isus.emc.com>; from Neff_Glen@emc.com on Tue, Jan 02, 2001 at 01:17:10PM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Neff_Glen@emc.com [010102 10:17] wrote: > I administer a box running v4.2-stable with a pair of the Adaptec ANA-62044 > 64-bit PCI, Quad port ethernet adapters. Six of the eight ethernet ports > are in use. The box routes traffic between five private networks and > provides NAT services out the public world on the sixth interface. > > I encounter an intermittant problem where one of the ports on a private > network will quit functioning (usually sf2 or sf3). Nothing on that segment > can reach the machine and if I try to ping something on that segment from > the box in question I get: > > ping: sendto: No buffer space available Can you show us the output of netstat -m after an incident? If your peak == max, then you actually are running out of bufferspace and should further raise maxusers/nmbclusters. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 11:24:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 11:24:39 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from newmail.netbistro.com (newmail.netbistro.com [204.239.167.35]) by hub.freebsd.org (Postfix) with SMTP id 8DAE637B400 for ; Tue, 2 Jan 2001 11:24:39 -0800 (PST) Received: (qmail 20028 invoked by uid 1020); 2 Jan 2001 19:24:38 -0000 Date: Tue, 2 Jan 2001 11:24:38 -0800 (PST) From: Jon Simola X-Sender: jon@newmail.netbistro.com To: Nick Hibma Cc: hackers@freebsd.org Subject: Re: Broken-by-design USB device? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: jon@netbistro.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Dec 2000, Nick Hibma wrote: > The panic is definitely bad. It happens straight after failing the > attach? Yep, but only during the kernel boot. Hot plugging the device after the system is booted spews the same errors to the console but does not cause a panic: uhid0: no report descriptor device_probe_and_attach: uhid0 attach returned 6 > plug the device in again, and after it has panicked (it will drop into > the debugger), type trace. That would give me a hint at where it > crashes. Here you go. If you need anything else, please ask. kernel: type 12 trap, code=0 Stopped at DEVICE_PROBE+0xe: cmpl 0(%edx),%eax db> trace DEVICE_PROBE(c1142d00,c1142d00,c1139100,0,0) at DEVICE_PROBE+0xe device_probe_child(c1139100,c1142d00,c1142e00,0,c1142e30) at device_probe_child+0xc1 device_probe_and_attach(c1142d00) at device_probe_and_attach+0x29 usbd_probe_and_attach(c1139100,c1142e00,2,3,c1142e00) at usbd_probe_and_attach+0xef usbd_new_device(c1139100,c113a000,1,200,2,c11390c0) at usbd_new_device+0x1dd uhub_explore(c1139280,c1139300,c1139e80,0,c0456e64) at uhub_explore+0x1d4 usb_attach(c1139300,c0456e7c,c01afc0b,c1139300,c113a000) at usb_attach+0xf1 DEVICE_ATTACH(c1139300,c113a000,c1139e80,0,c0456ea0) at DEVICE_ATTACH+0x2e device_probe_and_attach(c1139300) at device_probe_and_attach+0x4f uhci_pci_attach(c1139e80,c0456ec4,c01afc0b,c1139e80,c1139e80) at uhci_pci_attach+0x33f DEVICE_ATTACH(c1139e80,c1139e80,c1136400,0,c0456ed4) at DEVICE_ATTACH+0x2e device_probe_and_attach(c1139e80) at device_probe_and_attach+0x4f bus_generic_attach(c1136380,c0456ef8,c01afc0b,c1136380,c1136380) at bus_generic_attach+0x16 DEVICE_ATTACH(c1136380,c1136380,c1136580,0,c0456f08) at DEVICE_ATTACH+0x2e device_probe_and_attach(c1136380) at device_probe_and_attach+0x4f bus_generic_attach(c1136400,c0456f2c,c01afc0b,c1136400,c1136400) at bus_generic_attach+0x16 DEVICE_ATTACH(c1136400,c1136400,c0e25800,0,c0456f3c) at DEVICE_ATTACH+0x2e device_probe_and_attach(c1136400) at device_probe_and_attach+0x4f bus_generic_attach(c1136580,c1136580,c0456f58,c012740e,c1136580) at bus_generic_attach+0x16 nexus_attach(c1136580,c0456f70,c01afc0b,c1136580,c1136580) at nexus_attach+0xd DEVICE_ATTACH(c1136580,c1136580,c039a710,45b000,c0456f80) at DEVICE_ATTACH+0x2e device_probe_and_attach(c1136580) at device_probe_and_attach+0x4f root_bus_configure(c0e25800,c036d38c,0) at root_bus_configure+0x16 configure(0,454c00,45b000,0,c0126df4) at configure+0x33 mi_startup(c0456fb4,b0206,ffe,45b000,c01b42f9) at mi_startup+0x70 begin() at begin+0x4b > The controller probably requires some work because a fake report > descriptor is needed to make it possible for the uhid driver to talk to > it. It does not provide any information on where the information for the > buttons and axes is stored in the descriptor returned on the interrupt > pipe. --- Jon Simola | "In the near future - corporate networks Systems Administrator | reach out to the stars, electrons and light ABC Communications | flow throughout the universe." -- GITS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 11:36:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 11:36:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 426B037B400 for ; Tue, 2 Jan 2001 11:36:15 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f02JZuG01044; Tue, 2 Jan 2001 11:35:56 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010102133239.V253@speedy.gsinet> Date: Tue, 02 Jan 2001 11:36:20 -0800 (PST) From: John Baldwin To: Gerhard Sittig Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc cr Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Jan-01 Gerhard Sittig wrote: > On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote: >> >> Speaking only for myself, I don't think your proposed changes >> are a good idea, which is why I refrained from offering any >> suggestions on how you can test them. > > Your refusal(id?) has been the only response so far and it didn't > sound very clear / determined / explained (sorry, I lack better > words) to me. :) So I guess the wording I used "DST handling in > cron" was not done luckily. Let me cite from the doc diff: I must've missed this the first time through. This looks ok to me, though I'm curious if the 3 hour window is tweakable either by a compile time knob or a run time command line switch? 3 hours for the default would be ok... -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 12:13: 9 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 12:13:07 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id AC93F37B400 for ; Tue, 2 Jan 2001 12:13:05 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id JAA13573; Wed, 3 Jan 2001 09:12:56 +1300 (NZDT) Message-Id: <200101022012.JAA13573@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: Gerhard Sittig Date: Wed, 3 Jan 2001 09:12:55 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: OT: silence as an answer? (was: how to test out cron.c changes?) Reply-To: dan@langille.org Cc: freebsd-hackers@FreeBSD.ORG Priority: normal In-reply-to: <20010102125247.U253@speedy.gsinet> References: <3A513799.75EAB470@FreeBSD.org>; from DougB@FreeBSD.org on Mon, Jan 01, 2001 at 06:06:17PM -0800 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In this message I use the pronoun "you" quite a lot. It does not refer to anyone specifically. It's generic. On 2 Jan 2001, at 12:52, Gerhard Sittig wrote: > Silence as I see it is just > a sign for "nobody answered", without a reason to see why. You are not alone in this regard. Silence is neither consent nor disagreement. But in my experience, people are more vocal if they disagree with you than if they disagree (i.e. if you're made a fundamental mistake or error in your proposal) > Getting ignored is definitely a fine way > of discouraging future contributions. For people new to the project, this is definitely a major disappointment. But more experienced people will realise that repeating a proposal after a couple of week of silence is sometimes necessary. Sometimes, the message is just missed in the traffic and the one or two people which might be crucial to your proposal may have simply not seen your original post. > The experience will make me think twice next time if I'm in the > mood of spending my resources in the will to help and contribute > just to find myself sitting there ignored. Would I really feel > like having this kind of conversation, I could as well open my > fridge and talk to it ... :-| Gerhard: like you said, it's the holidays. Wait a bit. Many people may have unsubscribed or will simply delete the messages waiting for them when they return. In either case, it's worth trying again. Someone out there has an interest in what you're doing. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ FreshPorts - http://freshports.org/ NZ Broadband - http://unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 13:48:50 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 13:48:45 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.94.6.26]) by hub.freebsd.org (Postfix) with ESMTP id 7C05B37B400; Tue, 2 Jan 2001 13:48:44 -0800 (PST) Received: from wmptl.com ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id RAA00941; Tue, 2 Jan 2001 17:04:55 -0500 (EST) (envelope-from webmaster@wmptl.com) Message-ID: <3A524BF2.E2E1F3BF@wmptl.com> Date: Tue, 02 Jan 2001 16:45:22 -0500 From: Nathan Vidican Reply-To: nathan@vidican.com X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: questions@freebsd.org, hackers@freebsd.org Subject: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This machine is an Intel Pentium Pro based system, (not a DEC Alpha), it currently has one 200mhz 512K CPU, 196megs RAM, (4 x 32edo simms, 4 x 16edo simms), and two 4.5Gig SCSI disks in hot-swappable drive carriages configured using RAID 1 (mirrored), attached to a Mylex DAC960P/PD dual-channel controller. I have flashed the firmware of the controller card to 3.52, as reccomended during the dmesg prompts (the card initially had < 3.51). The problem seems to be with booting, I have tried several installs; all seem to partition fine except for 'dangerously dedicated'. After an install using a 4.4Gig root, and an 80meg swap, (leaving 20megs un-partitioned at the end of the drive), the system will not boot. If I boot off of the installation floppies, I can mount/view the files on the drive. This leaves me thinking it's got to have something to do with FreeBSD's MBR. Having problems booting; the system installs to the mylex system drive fine, but when I reboot, I get the FreeBSD boot MGR, and it only beeps when I press F1 for FreeBSD. If I install using a normal boot record, the system reports 'No operating system found'. I'm thinking it may be an issue with the Mylex card, but I don't know for sure if the system's bios could cause this either. I cannot attempt to install the mylex card in another machine; as the drives attached to it are in a hot-swap carriage which is part of the system's chassis. On a hunch, I tried re-partitioning and installing MsDos; maybe the RAID configuration isn't bootable at all I figured; but it partitioned fine, and booted properly. I then tried installing NT, and now Linux. All three had no problems, and all three booted fine. Seeing as how the other O/S's all installed/worked fine; I'm assuming this is just a software issue. Maybe with the bios of the Raid controller, or maybe with the system bios, has anyone else run into similar problems? Am I just missing something blatenly obvious? Does FreeBSD not boot from a mirrored volume (if so... why not)? I've only ever done one other server install with FreeBSD, and a Mylex Raid controller; it booted fine. It was using an AcceleRAID PCI 150 card, with foud 9.1gig SCSIUW's in a RAID 5 configuration. It went fine with no hitches, (cept that it took like 1hr to newfs). However, this is a different controller, and having little to no experience working with RAID controllers I figured I'd ask. Baring no absolute solutions, or better partial ones from this mailing list, I'm going to install Linux on a 200meg partition, and attempt to install FreeBSD on the rest and boot it using Lilo (don't know if it's going to work...but it's worth a try). -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 14: 2: 8 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 14:02:06 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id EC55D37B400 for ; Tue, 2 Jan 2001 14:02:05 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f02M23Q44542; Tue, 2 Jan 2001 14:02:03 -0800 (PST) Date: Tue, 2 Jan 2001 14:02:03 -0800 (PST) From: Doug White To: =?iso-8859-1?Q?F=E9lix-Antoine?= Paradis Cc: hackers@FreeBSD.ORG Subject: Re: ARP question. In-Reply-To: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some more fuel... On Tue, 2 Jan 2001, [iso-8859-1] Félix-Antoine Paradis wrote: > Hi, > When we do a "dmesg" on a 4.2-STABLE box, we get: > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 From personal experience, Linux has this nasty bad habit of broadcasting ARPs on all interfaces. For this reason multihomed Linux boxes should be banned. We got tired of it at my previous job and patched around it on the linux machine. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 14: 3:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 14:03:28 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 44E9E37B400 for ; Tue, 2 Jan 2001 14:03:28 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f02M3Gr44558; Tue, 2 Jan 2001 14:03:16 -0800 (PST) Date: Tue, 2 Jan 2001 14:03:16 -0800 (PST) From: Doug White To: Zhiui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging suggestion needed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001, Zhiui Zhang wrote: > > I have written a KLD and am debugging it. The program often hangs after > runs for a while (I guess it enters into some dead loop). Is there a way > to attach to the process and somehow find out which code it is executing > (with remote debugging or ddb)? kld debugging is a bit tricky. Take a look at the debugging macros and bits that Greg Lehey put together for vinum for a starting point. You have to calculate the appropriate offset to get to the KLD code in gdb. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 14:19:26 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 14:19:23 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 24C1837B400 for ; Tue, 2 Jan 2001 14:19:23 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f02MJ3e68155; Tue, 2 Jan 2001 17:19:03 -0500 (EST) (envelope-from arr@watson.org) Date: Tue, 2 Jan 2001 17:19:03 -0500 (EST) From: "Andrew R. Reiter" To: dwhite@resnet.uoregon.edu, zzhang@cs.binghamton.edu Cc: freebsd-hackers@freebsd.org Subject: Re: kernel debugging suggestion needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Sorry for lack of message in this reply but I accidently rm'd the original emails to reply to :-) ] One thing I've done in the past is if it's convenient in a section of code to hijack a function pointer in the kernel, then hijack it so that it will call your code... Silly, and not always really useful... But, Ive done it before.... *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 15:27:26 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 15:27:25 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.lokigames.com (www.lokigames.com [63.80.144.66]) by hub.freebsd.org (Postfix) with ESMTP id 0870F37B400 for ; Tue, 2 Jan 2001 15:27:25 -0800 (PST) Received: from asgard.lokigames-lan.com (user94.lokigames.com [63.80.144.94]) by mail.lokigames.com (8.9.3/8.9.3) with ESMTP id PAA00739 for ; Tue, 2 Jan 2001 15:24:20 -0800 Received: (from raistlin@localhost) by asgard.lokigames-lan.com (8.9.3/8.9.3) id PAA03199 for hackers@freebsd.org; Tue, 2 Jan 2001 15:27:14 -0800 Date: Tue, 2 Jan 2001 15:27:14 -0800 From: Rafael Barrero To: hackers@freebsd.org Subject: BSD dlopen and such Message-ID: <20010102152714.A3189@lokigames.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: raistlin@mail.lokigames.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Two questions: 0) Are native binaries for OpenBSD different from FreeBSD? 1) Can a native binary dlopen a Linux ELF GL, yes or no? Rafael Barrero raistlin@lokigames.com "You know ... you take the killing for granted. And then it's gone, and you're like, 'I wish I'd appreciated it more.' Stopped and smelled the corpses, you know?" -Spike (BtVS) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 17:41:33 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 17:41:31 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id AA35B37B400 for ; Tue, 2 Jan 2001 17:41:29 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id EFC636A911; Wed, 3 Jan 2001 12:11:15 +1030 (CST) Date: Wed, 3 Jan 2001 12:11:15 +1030 From: Greg Lehey To: Doug White Cc: Zhiui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging suggestion needed Message-ID: <20010103121115.D15003@wantadilla.lemis.com> 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 dwhite@resnet.uoregon.edu on Tue, Jan 02, 2001 at 02:03:16PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 14:03:16 -0800, Doug White wrote: > On Tue, 2 Jan 2001, Zhiui Zhang wrote: > >> >> I have written a KLD and am debugging it. The program often hangs after >> runs for a while (I guess it enters into some dead loop). Is there a way >> to attach to the process and somehow find out which code it is executing >> (with remote debugging or ddb)? > > kld debugging is a bit tricky. Take a look at the debugging macros and > bits that Greg Lehey put together for vinum for a starting point. You have > to calculate the appropriate offset to get to the KLD code in gdb. Doug Rabson has described an alternative to me, but I never got it to work. My hack walks down the list of klds looking for a name starting with 'v'; you can change this to something which identifies your kld, and you'll need to change the name of the kld itself, of course. I also have a number of other macros in files in /usr/src/sys/modules/vinum. Here's the macro: define asf set $file = linker_files.tqh_first set $found = 0 while ($found == 0) if (*$file->filename == 'v') set $found = 1 else set $file = $file->link.tqe_next end end shell /usr/bin/objdump --section-headers sys/modules/vinum/vinum.ko | grep ' .text' | awk '{print "add-symbol-file sys/modules/vinum/vinum.ko \$file->address+0x" $4}' > .asf source .asf end Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 18:30:40 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 18:30:39 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id B18C637B400 for ; Tue, 2 Jan 2001 18:30:38 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14DdhF-0005eB-00; Wed, 3 Jan 2001 03:30:37 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id f031eiw06773 for freebsd-hackers@freebsd.org; Wed, 3 Jan 2001 02:40:44 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: BSD dlopen and such Date: Wed, 3 Jan 2001 01:40:44 +0000 (UTC) Message-ID: <92tvus$6hu$1@kemoauc.mips.inka.de> References: <20010102152714.A3189@lokigames.com> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-hackers@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rafael Barrero wrote: > > 0) Are native binaries for OpenBSD different from FreeBSD? Yes. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 18:54:27 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 18:54:23 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.nji.com (mail.nji.com [216.44.116.2]) by hub.freebsd.org (Postfix) with ESMTP id 4C00C37B400 for ; Tue, 2 Jan 2001 18:54:23 -0800 (PST) Received: from clp (mpb-72.nji.com [216.44.117.72]) by ns1.nji.com (8.9.0/8.9.0) with SMTP id VAA11347 for ; Tue, 2 Jan 2001 21:54:16 -0500 From: clp@nji.com Message-ID: <000a01c07531$f2b26a00$48752cd8@clp> To: Subject: help! Date: Tue, 2 Jan 2001 22:04:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C07508.07DD36A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C07508.07DD36A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. I have a netgear Ethernet card installed in my computer. In order to = reconnect my computer to the internet, I have to reinstall the drivers = and they're missing. So, I opened up my computer to look at the Ethernet = card and I copied down the necessary numbers. However, I do not know how = to download the program. I found this e-mail address on the web and = would greatly appreciate some help. Thank you! -Christina, clp@nji.com=20 ------=_NextPart_000_0007_01C07508.07DD36A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi. I have a netgear Ethernet card = installed in my=20 computer. In order to reconnect my computer to the internet, I have to = reinstall=20 the drivers and they're missing. So, I opened up my computer to look at = the=20 Ethernet card and I copied down the necessary numbers. However, I do not = know=20 how to download the program. I found this e-mail address on the web and = would=20 greatly appreciate some help. Thank you! -Christina, clp@nji.com
------=_NextPart_000_0007_01C07508.07DD36A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 20:23:32 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 20:23:31 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 94A8137B402 for ; Tue, 2 Jan 2001 20:23:30 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id XAA04752; Tue, 2 Jan 2001 23:22:51 -0500 (EST) Date: Tue, 2 Jan 2001 23:22:49 -0500 (EST) From: Zhiui Zhang X-Sender: zzhang@opal To: Doug White Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging suggestion needed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001, Doug White wrote: > On Tue, 2 Jan 2001, Zhiui Zhang wrote: > > > > > I have written a KLD and am debugging it. The program often hangs after > > runs for a while (I guess it enters into some dead loop). Is there a way > > to attach to the process and somehow find out which code it is executing > > (with remote debugging or ddb)? > > kld debugging is a bit tricky. Take a look at the debugging macros and > bits that Greg Lehey put together for vinum for a starting point. You have > to calculate the appropriate offset to get to the KLD code in gdb. I already did this. I hope that I can find a way to know which process is running which part of the KLD code endlessly. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 20:35: 4 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 20:35:02 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 8221E37B400 for ; Tue, 2 Jan 2001 20:35:01 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2694C6A911; Wed, 3 Jan 2001 15:04:52 +1030 (CST) Date: Wed, 3 Jan 2001 15:04:52 +1030 From: Greg Lehey To: Zhiui Zhang Cc: Doug White , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging suggestion needed Message-ID: <20010103150452.F4336@wantadilla.lemis.com> 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 zzhang@cs.binghamton.edu on Tue, Jan 02, 2001 at 11:22:49PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 23:22:49 -0500, Zhiui Zhang wrote: > On Tue, 2 Jan 2001, Doug White wrote: > >> On Tue, 2 Jan 2001, Zhiui Zhang wrote: >> >>> >>> I have written a KLD and am debugging it. The program often hangs after >>> runs for a while (I guess it enters into some dead loop). Is there a way >>> to attach to the process and somehow find out which code it is executing >>> (with remote debugging or ddb)? >> >> kld debugging is a bit tricky. Take a look at the debugging macros and >> bits that Greg Lehey put together for vinum for a starting point. You have >> to calculate the appropriate offset to get to the KLD code in gdb. > > I already did this. I hope that I can find a way to know which process is > running which part of the KLD code endlessly. There are other macros in my .gdbinits which give you backtraces of other processes. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 20:38:37 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 20:38:35 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 4B3C937B400 for ; Tue, 2 Jan 2001 20:38:33 -0800 (PST) Received: (qmail 19916 invoked by uid 1001); 3 Jan 2001 14:38:30 +1000 X-Posted-By: GBA-Post 2.07 04-Dec-2000 X-URL: http://www.gbch.net X-Image-URL: http://www.gbch.net/gjb/img/gjb-auug048.gif X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 X-PGP-Public-Key: http://www.gbch.net/gjb/gjb-pgpkey.asc Message-Id: Date: Wed, 03 Jan 2001 14:38:30 +1000 From: Greg Black To: Gerhard Sittig Cc: freebsd-hackers@FreeBSD.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102133239.V253@speedy.gsinet> In-reply-to: <20010102133239.V253@speedy.gsinet> of Tue, 02 Jan 2001 13:32:39 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > Is there anyone out there who feels like rejecting the proposal > for a *reason*? Or to accept the idea, but to redirect the > effort to a "real solution"? I somehow doubt you'd rather > explain again and again that cron(8) isn't broken but that users > should shuffle around the daily job's execution time ... I'm opposed to the changes. Those people who live in places that use daylight savings time should be aware of its effect on their lives and should understand that scheduling events to fall during the missed or repeated time at the changeover (whether by cron or by any other mechanism) is going to produce anomalous results. Therefore, the /right/ thing to do is to avoid the times where this problem can occur. IMO, the solution is to put a note at the top of the distributed /etc/crontab file suggesting that people who have DST not put jobs in the transition times, together with similar notes in the relevant man pages and in comments at the top of the files that are generated by crontab. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 20:56:35 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 20:56:31 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp5.mail.yahoo.com (smtp5.mail.yahoo.com [128.11.69.102]) by hub.freebsd.org (Postfix) with SMTP id E1A2E37B400 for ; Tue, 2 Jan 2001 20:56:31 -0800 (PST) Received: from tmp1-70fe.rochester.rr.com (HELO halstead007) (24.161.70.254) by smtp.mail.vip.suc.yahoo.com with SMTP; 3 Jan 2001 04:56:31 -0000 X-Apparently-From: Message-ID: <019101c07541$6a573cc0$0601a8c0@halstead007> From: "James Halstead" To: Subject: Re: Boot process robustness Date: Tue, 2 Jan 2001 23:55:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "James Halstead" To: "Poul-Henning Kamp" Sent: Tuesday, January 02, 2001 11:30 PM Subject: Re: Boot process robustness > > ----- Original Message ----- > From: "Poul-Henning Kamp" > To: "Walter W. Hop" > Cc: "FreeBSD hackers" > Sent: Thursday, December 28, 2000 9:31 AM > Subject: Re: Boot process robustness > > > > In message , "Walter > W. Ho > > p" writes: > > >Hi all, > > > > > >I was wondering how to increase the robustness of the booting process, > > >so that a box would be able to keep itself on its feet without > > >intervention of the console. I think this would be of great value to the > > >many people who administer colocated boxes. > > > > > >I'm not much of a coder so all I can do is mailing this (at the risk of > > >wasting your time with total useless crap ofcourse, in which case I > > >apologize.) > > > > > >1. Old kernel recovery > > > When 'make install'ing a new kernel, a flag is raised (say, > > > 'revert_on_fail') which is only cleared after a successful system > > > initialisation. When the new kernel boots, a panic in this state or > > > an unexpected reboot (reset after a system hang) would cause > > > /kernel.old to be loaded on the next boot instead (maybe the same > > > could work for /etc/rc.conf.old) > > > > This is actually more a question of where to store the flag than > > anything else. > > > > Couldn't you just modify the shutdown command to have an option for revert > on fail, which would create > a file on the root filesystem with a timestamp of when the reboot started. > Then at boot time, if that timstamp > is still there, and has been around for too long, boot the kernel.old > instead of kernel. Then the question is > what amount of time is reasonable for the wait period. This may have the > machine boot the new kernel > and panic a few times, but at least you can be assured that it would after x > minutes boot the old kernel > instead. Once a boot was successful the times stamp file could be removed. > > Just a thought. > > ~James > > > Julian made a rather hackish thing for Whistle, but I think we lost > > that with the advent of the new bootblocks. > > > > >2. Automatic file system checks > > > In case of a powercycle or crash, it could be that a filesystem needs > > > fixing. Now I don't know much about fs internals, but I guess that in > > > most cases just answering 'Y' to fsck's questions will fix things. I > > > would appreciate an option where an inconsistency would start up fsck > > > in an "automatic" repair mode, with all actions logged and "undo" > > > data being saved (in case manual review is needed). > > > > Alternatively it might be worth considering adding a "remote-single-user" > > capability: > > > > If an fsck fails, ifconfig the interfaces and start an sshd so people > > can get in remotely and fsck... > > > > -- > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > phk@FreeBSD.ORG | TCP/IP since RFC 956 > > FreeBSD committer | BSD since 4.3-tahoe > > Never attribute to malice what can adequately be explained by > incompetence. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > _________________________________________________________ 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-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 21: 1:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 21:01:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tsunami.waterspout.com (tsunami.waterspout.com [208.13.56.11]) by hub.freebsd.org (Postfix) with ESMTP id 23A5937B400 for ; Tue, 2 Jan 2001 21:01:15 -0800 (PST) Received: from dustdevil.waterspout.com (tsunami.fw.waterspout.com [208.13.60.34]) by tsunami.waterspout.com (8.9.3/8.9.3) with ESMTP id AAA66836 for ; Wed, 3 Jan 2001 00:01:13 -0500 (EST) (envelope-from csg@dustdevil.waterspout.com) Received: (from csg@localhost) by dustdevil.waterspout.com (8.11.1/8.11.1) id f0355Ae16857; Wed, 3 Jan 2001 00:05:10 -0500 (EST) (envelope-from csg) Date: Wed, 3 Jan 2001 00:04:58 -0500 From: "C. Stephen Gunn" To: Doug White Cc: freebsd-hackers@freebsd.org Subject: Re: ARP question. Message-ID: <20010103000458.A16838@waterspout.com> References: <5.0.2.1.0.20010102023010.00a101f0@pop6.sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Tue, Jan 02, 2001 at 02:02:03PM -0800 Sender: csg@dustdevil.waterspout.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 02:02:03PM -0800, Doug White wrote: > > arp: 200.42.126.18 moved from 00:e0:7d:7b:53:f0 to 00:c0:df:f4:ac:05 on ed0 > > From personal experience, Linux has this nasty bad habit of broadcasting > ARPs on all interfaces. For this reason multihomed Linux boxes should be > banned. > > We got tired of it at my previous job and patched around it on the linux > machine. I've seen similar things from Linux. In my experience it was an ARP who-has request with the source IP of the other interface. Linux apparently doesn't learn ARP addresses this way, but FreeBSD takes note, which causes the problem mentioned above. Is the Linux box a firewall/NAT box of some kind? Having two interfaces on the same wire can be a problem. FreeBSD's ARP implementation gets rather upset about seeing the packets twice, since the receive interface is significant. Broadcast protocols aren't guaranteed to be idempotent. Your mileage may vary. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 21: 2:52 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 21:02:50 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id A04EC37B400 for ; Tue, 2 Jan 2001 21:02:49 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id E1829574F0; Tue, 2 Jan 2001 23:03:24 -0600 (CST) Date: Tue, 2 Jan 2001 23:03:24 -0600 From: "Michael C . Wu" To: Greg Black Cc: Gerhard Sittig , freebsd-hackers@FreeBSD.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Message-ID: <20010102230324.B65492@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Greg Black , Gerhard Sittig , freebsd-hackers@FreeBSD.org References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102133239.V253@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb@gbch.net on Wed, Jan 03, 2001 at 02:38:30PM +1000 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 02:38:30PM +1000, Greg Black scribbled: | Gerhard Sittig wrote: | > Is there anyone out there who feels like rejecting the proposal | > for a *reason*? Or to accept the idea, but to redirect the | > effort to a "real solution"? I somehow doubt you'd rather | > explain again and again that cron(8) isn't broken but that users | > should shuffle around the daily job's execution time ... | | I'm opposed to the changes. Those people who live in places | that use daylight savings time should be aware of its effect on You see, "those people" equates to sysadmins living in North/South America, Europe, Australia, and some other places. | their lives and should understand that scheduling events to fall | during the missed or repeated time at the changeover (whether by | cron or by any other mechanism) is going to produce anomalous | results. Therefore, the /right/ thing to do is to avoid the | times where this problem can occur. | | IMO, the solution is to put a note at the top of the distributed | /etc/crontab file suggesting that people who have DST not put | jobs in the transition times, together with similar notes in the | relevant man pages and in comments at the top of the files that | are generated by crontab. Daylight savings time is here to stay. Nobody is going to change this for bunch of unix servers. I do not understand why people resist change in FreeBSD so much. This does not hurt anybody. Mr.Blacks' /etc/crontab comment idea is quite the thing that we try to avoid in the tree. -- Sigh, yet another bikeshed. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 21:48:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 21:48:27 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 3BF8037B402 for ; Tue, 2 Jan 2001 21:48:26 -0800 (PST) Received: (qmail 12612 invoked by uid 0); 3 Jan 2001 05:48:24 -0000 Received: from p3ee21608.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.8) by mail.gmx.net (mail03) with SMTP; 3 Jan 2001 05:48:24 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id WAA13975 for freebsd-hackers@FreeBSD.org; Tue, 2 Jan 2001 22:35:32 +0100 Date: Tue, 2 Jan 2001 22:35:32 +0100 From: Gerhard Sittig To: freebsd-hackers@FreeBSD.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc cr Message-ID: <20010102223532.W253@speedy.gsinet> References: <20010102133239.V253@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Jan 02, 2001 at 11:36:20AM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 11:36 -0800, John Baldwin wrote: > > [ manpage diff for cron.c change reasoning ] > > I must've missed this the first time through. I hoped that silence is not always meant in a negativ way. :> See my first message to freebsd-hackers as of December 5th at http://www.freebsd.org/cgi/getmsg.cgi?fetch=211030+217815+/usr/local/www/db/text/2000/freebsd-hackers/20001210.freebsd-hackers > This looks ok to me, though I'm curious if the 3 hour window is > tweakable either by a compile time knob or a run time command > line switch? 3 hours for the default would be ok... The code is taken verbosely from the FreeBSD -> OpenBSD diff of cron (modulo capability / gcc / other unrelated patches the OpenBSD version has, but both are based on vixie cron). The decision you refer to looks like this: + wakeupKind = -1; + if (timeDiff > -(3*MINUTE_COUNT)) + wakeupKind = 0; + if (timeDiff > 0) + wakeupKind = 1; + if (timeDiff > 5) + wakeupKind = 2; + if (timeDiff > (3*MINUTE_COUNT)) + wakeupKind = 3; + + switch (wakeupKind) { The "three times the minutes one hour has" could easily be made tweakable as soon as there's someone who knows how to propagate a compile time option into a *.c file. :) I'm not clear where to put this thing: /usr/src/usr.sbin/cron/Makefile, some header file, cron.c beginning, ...? Well, the trigger level probably should live in a public variable, get initialized with a #define'd value (tweakable in the Makefile) and overridden at argv[] parse time. This should give all the benefits of leaving it alone, editing source before compile time as well as providing an argument at run time. But let's wait with this until the feature is worth at all to make it into FreeBSD. :) Unless this decision depends on the possibility to tweak the trigger level ... :> I guess I will have to roll the current state (stuck since early December when the silence started:) into a PR to have a base for further discussions and most of all review. There are chances I did something stupid (cut the diff too much / too little) and there's room for improvement (like your turnable knob as well as making the above operate on "more readable" enums and the like). Give me a few days to sort my stuff. Although I didn't want to bother you with (functionally) untested patches, I fail to see any other way of making possible progress in this special feature's case -- discussions would be too much in theory without the patch getting published. Unless somebody could tell me how to test it here locally -- to save other peoples' time by not publishing unfinished code ... BTW: Thank you for CC'ing me. Otherwise there would be turn around times of some five days when I had to follow the thread via the web interface. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 23: 7: 6 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 23:07:04 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 45BBE37B400; Tue, 2 Jan 2001 23:07:04 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 340AE574F0; Wed, 3 Jan 2001 01:07:39 -0600 (CST) Date: Wed, 3 Jan 2001 01:07:39 -0600 From: "Michael C . Wu" To: jlemon@freebsd.org, rwatson@freebsd.org, itojun@netbsd.org Cc: hackers@freebsd.org Subject: TCP Rate-Halving Message-ID: <20010103010739.A68404@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [If need be, please add Cc: to -net] While doing my own research project, I came across this piece of information. It seems like a "nobody-has-it-but-it-is-fast" thing. http://www.psc.edu/networking/ftp/papers/draft-ratehalving.txt It seeks to improve the Reno TCP implementation by the most recommended trick in the book, redesigning the algorithm. From the above url: "Hoe [Hoe95] suggested that during Fast Recovery the TCP data sender space out retransmissions and new data on alternate acknowledgements across the entire recovery RTT. (Note that this eliminates the half RTT lull in sending which occurs in Reno TCP.)" Do we already do this? I know that a re-write of our TCP code is "imminent." This seeks to improve congested server TCP connections. (Oh BTW, Isn't TCP the little thing that servers use ;-)? ) Will someone enlighten me on how deviated we are from the Reno TCP code? I am under the impression that we have the W. Stevens RFC2581 implemented. Is that true? They even implemented this for NetBSD and DECUnix/Tru64: http://www.psc.edu/networking/tcp.html#psc Is this specified in the IPv6 specs? Does KAME do this? If this has already been implemented, can someone e And perhaps we can implement/import this...someday, like what we did with schedular activations. Relevant: http://www.psc.edu/networking/rate-halving/ RFC2581 RFC2481 -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 2 23:25:16 2001 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 2 23:25:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id CBCF937B400; Tue, 2 Jan 2001 23:25:13 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id QAA04708; Wed, 3 Jan 2001 16:25:02 +0900 (JST) To: "Michael C . Wu" Cc: jlemon@freebsd.org, rwatson@freebsd.org, hackers@freebsd.org In-reply-to: keichii's message of Wed, 03 Jan 2001 01:07:39 CST. <20010103010739.A68404@peorth.iteration.net> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: TCP Rate-Halving From: itojun@iijlab.net Date: Wed, 03 Jan 2001 16:25:02 +0900 Message-ID: <4706.978506702@coconut.itojun.org> Sender: itojun@itojun.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is this specified in the IPv6 specs? Does KAME do this? I don't think so. TCP on IPv6 is exactly the same as TCP on IPv4. only differences I know of are in the following portion: (1) pseudo-header checksum documented in in RFC2460 section 8.1 (2) jumbogram support documented in RFC2675 there's no additional requirements whatsoever, I believe. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 4:23:35 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 04:23:30 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id A2B3F37B400 for ; Wed, 3 Jan 2001 04:23:20 -0800 (PST) Received: from way95.eng.tvol.net ([10.32.1.145]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YMS254B2; Wed, 3 Jan 2001 07:23:25 -0500 Received: from kway by way95.eng.tvol.net with local (Exim 3.20 #1 (Debian)) id 14Dmwp-0004r0-00; Wed, 03 Jan 2001 07:23:19 -0500 Date: Wed, 3 Jan 2001 07:23:19 -0500 From: Kevin Way To: Gerhard Sittig Cc: freebsd-hackers@freebsd.org Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Message-ID: <20010103072319.B18615@way95.eng.tvol.net> References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102133239.V253@speedy.gsinet> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102133239.V253@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Tue, Jan 02, 2001 at 01:32:39PM +0100 Organization: WorldGate Communications [www.wgate.com] Sender: Kevin Way Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I like these changes. I'm definitely in favor of code that corrects for the DST handling=20 oddities that sysadmins have to deal with. This would be especially=20 valuable for companies which might have deployments in 25 different=20 time zones globally, which for reasons that are out of scope can't be converted to UTC. The argument that the sysadmin should know the=20 results of putting a cronjob at a certain time become much weaker in=20 that scenario. =20 Additionally, the fact of the matter is that most DST crossovers occur during low-usage periods for typical servers. Given a choice of performing resource-intensive daily chores at a time of low usage, or wasting three hours each night, because twice a year there's a clock jump, I'll take the fully utilized server please. The one thing that has me giving some amount of hesitation, though=20 it's trivial, is the fact that this patch is based solely on clock skew. My initial reaction is that I'd like the patch to check if the skew has been caused by a time zone shift, though honestly, I can't think of another scenario where a properly running server's clock would jump. I'll gladly retract my endorsement of this type of change if somebody can note scenarios where this could have negative effects equal to or greater than the negative effects of the current system. --=20 kevin way worldgate communications software engineer +1 215 354 5287 --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6Uxm3kHXCCwlJQwURAgneAJ4yMSejmX9z4vm4hMJM4wgi5VHxqwCcDs34 n+E9QS5RtneoCc9VM9BPTqA= =MGll -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 5:54:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 05:54:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 9A34E37B402 for ; Wed, 3 Jan 2001 05:54:37 -0800 (PST) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA04380; Wed, 3 Jan 2001 16:01:03 +0100 Message-ID: <3A532F56.60A8DABE@i-clue.de> Date: Wed, 03 Jan 2001 14:55:34 +0100 From: Christoph Sold Reply-To: christoph.sold@server.i-clue.de Organization: i-clue interactive X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: Christoph Sold , hackers@FreeBSD.ORG Subject: Re: Keyboard doesn't work anymore [repost, no answers on -questions] References: <3A410676.207C7E32@i-clue.de> <200012210524.OAA10550@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. It was the race condition. For unknown reasons, the box in questions now needs more than 30 seconds to start its gettys. Now the kdm startup script waits for 120 seconds, and the box works again. Thanks again -Christoph Sold Kazutaka YOKOTA schrieb: > = > >suddenly, the console keyboard does no longer work. kdm is displayed, > >but no keypress works (except num lock and scroll lock, which light th= e > >appropriate LEDs). > = > This means your hardware (keyboard and keyboard controller) and > FreeBSD kernel (keyboard drivver) are working ok. > = > When in X, the keyboard driver passes all keystrokes, untouched and > unmodified, to the X server, and the X server does all necessary > processing to generate key input to X clients. So long as various > lock keys and LEDs work correctly, we can say that the keyboard, the > keyboard driver and the X server are exchanging data all right. > = > It seems to me, somewhat the X server, or one of X clients, is > eating up key strokes and not passing key input to where it should go. > = > Oh, there is another possibility. How do you start the X server and kd= m? > There is a chance that the X server and getty are both trying to read > from the keyboard. Read discussion on xdm in FreeBSD FAQ. There is > a race condition to obtain access to the keyboard, and the X server > and getty may be running in the same vty somewhat. > = > Kazu > = > >The box is still up and running, remote login is > >still possible, the mouse can still be used to select things in kdm. > > > >Ctl-Alt-Fn beeps (except for the console displaying kdm). After reboot= , > >the keyboard is useable for a few minutes. Shortly thereafter, it's de= ad > >again. > > > >System: $ uname -a > >FreeBSD amnesix.i-clue.de 4.1-STABLE FreeBSD 4.1-STABLE #3: Thu Sep 7= > >22:54:08 > >CEST 2000 so@amnesix.i-clue.de:/usr/src/sys/compile/AMNESIX i386 > > > >Any ideas? What to check for? > > > >-Christoph Sold -- = Viele Gr=FC=DFe aus Waiblingen Christoph Sold -- Systemadministrator, i-clue GmbH, Endersbacher Str 57, 71334 Waiblingen Fon: (0 71 51) 9 59 01-12, Fax: (0 71 51) 9 59 01-55, Mail: so@i-clue.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 6:33: 3 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 06:33:01 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 48FCD37B400 for ; Wed, 3 Jan 2001 06:33:00 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14DoyB-0001OV-00; Wed, 03 Jan 2001 15:32:51 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14Doy9-0005mK-00; Wed, 03 Jan 2001 15:32:49 +0100 Date: Wed, 3 Jan 2001 15:32:49 +0100 From: Nicolas Souchu To: "Matthew C. Forman" Cc: freebsd-hackers@freebsd.org Subject: Re: Allocating I/O port space Message-ID: <20010103153249.A21984@wiliam.alcove-int> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: ; from mcf@forman.homeip.net on Fri, Dec 29, 2000 at 12:26:53PM +0000 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 29, 2000 at 12:26:53PM +0000, Matthew C. Forman wrote: > > Hi again all, > > Well, despite the reception I'm still here, desperately trying to allocate > an I/O port range! Still can't get bus_alloc_resource to work, despite > doing everything by the book. I have a question. My kernel prints this: > > amdpm0: at device 7.3 on pci0 > > ...before amdpm_attach complains it can't map any I/O space. Where > does the resource info printed here come from? Does the fact The probe. > that nothing is printed about ports mean that as far as the system is > concerned, it doesn't have any? Is this why bus_alloc_resource > fails? Sorry if the answers seem obvious, but I'm learning, so please be > patient! > > If all this is the case, then how could I allocate the I/O space I need? Try to bus_set_resource() in the probe routine, then alloc them in the attach one. You should get what you want in the detection message. -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 6:40:19 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 06:40:17 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 03A9037B400 for ; Wed, 3 Jan 2001 06:40:15 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14Dp5B-0001Sr-00; Wed, 03 Jan 2001 15:40:05 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14Dp57-0005ms-00; Wed, 03 Jan 2001 15:40:01 +0100 Date: Wed, 3 Jan 2001 15:40:01 +0100 From: Nicolas Souchu To: "Matthew C. Forman" Cc: freebsd-hackers@freebsd.org Subject: Re: AMD PM driver finally there! Message-ID: <20010103154001.B21984@wiliam.alcove-int> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: ; from mcf@forman.homeip.net on Sat, Dec 30, 2000 at 07:54:41PM +0000 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 30, 2000 at 07:54:41PM +0000, Matthew C. Forman wrote: > > OK, I've finally got there with the AMD pm/smbus driver. It's now newbus, > though this was quite a weird experience. In the end, I found that my BIOS > wasn't giving out any I/O resource information for the AMD 756's power > management function, hence bus_alloc_resource failed. A bus_set_resource > fixed this. > > So... I'd like it committed, though I don't really know how this > process works. The diffs are all available at: > > http://www.3d-med.cse.dmu.ac.uk/~mcf/amdpm.tar.gz > > ...if anyone can do the Right Thing with it. If nobody else already looked at it, consider that I will. Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 9:41:48 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 09:41:46 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lh00.opsion.fr (lh00.opsion.fr [212.73.208.226]) by hub.freebsd.org (Postfix) with SMTP id 68C3F37B400 for ; Wed, 3 Jan 2001 09:41:45 -0800 (PST) Received: from 198.168.78.67 [198.168.78.67] by lh00.opsion.fr; Wed, 3 Jan 2001 17:43:20 GMT From: Thierry Reply-To: tjmsdn@ifrance.com To: freebsd-hackers@freebsd.org Subject: gdb question Date: Wed, 3 Jan 2001 12:37:21 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <01010312453500.00430@FreeBSD.eicon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I use the "fork" function to call another function "foo( )" In gdb, I would like to put a breakpoint in this function "foo( )", When I execute, the function "foo( )" is stopped, but gdb doesn't give me the hand. How I can put a breakpoint in a function call by a "fork" system ? Thanks in Advance. Thierry. ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 10:27:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 10:27:25 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rush.telenordia.se (mail.telenordia.se [194.213.64.42]) by hub.freebsd.org (Postfix) with SMTP id 84EF637B402 for ; Wed, 3 Jan 2001 10:27:24 -0800 (PST) Received: (qmail 437 invoked from network); 3 Jan 2001 19:27:23 +0100 Received: from bb-62-5-7-17.bb.tninet.se (HELO web1.tninet.se) (62.5.7.17) by mail.telenordia.se with SMTP; 3 Jan 2001 19:27:23 +0100 From: Mark Rowlands Reply-To: mark.rowlands@minmail.net To: nathan@vidican.com, Nathan Vidican , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason Date: Wed, 3 Jan 2001 19:20:30 +0100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" References: <3A524BF2.E2E1F3BF@wmptl.com> In-Reply-To: <3A524BF2.E2E1F3BF@wmptl.com> MIME-Version: 1.0 Message-Id: <01010319203000.04014@web1.tninet.se> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG do you have bios translation set to 2gb? On Tuesday 02 January 2001 22:45, Nathan Vidican wrote: > This machine is an Intel Pentium Pro based system, (not a DEC Alpha), it > currently has one 200mhz 512K CPU, 196megs RAM, (4 x 32edo simms, 4 x > 16edo simms), and two 4.5Gig SCSI disks in hot-swappable drive carriages > configured using RAID 1 (mirrored), attached to a Mylex DAC960P/PD > dual-channel controller. I have flashed the firmware of the controller > card to 3.52, as reccomended during the dmesg prompts (the card > initially had < 3.51). The problem seems to be with booting, I have > tried several installs; all seem to partition fine except for > 'dangerously dedicated'. After an install using a 4.4Gig root, and an > 80meg swap, (leaving 20megs un-partitioned at the end of the drive), the > system will not boot. If I boot off of the installation floppies, I can > mount/view the files on the drive. This leaves me thinking it's got to > have something to do with FreeBSD's MBR. > Having problems booting; the system installs to the mylex system drive > fine, but when I reboot, I get the FreeBSD boot MGR, and it only beeps > when I press F1 for FreeBSD. If I install using a normal boot record, > the system reports 'No operating system found'. I'm thinking it may be > an issue with the Mylex card, but I don't know for sure if the system's > bios could cause this either. I cannot attempt to install the mylex card > in another machine; as the drives attached to it are in a hot-swap > carriage which is part of the system's chassis. > On a hunch, I tried re-partitioning and installing MsDos; maybe the > RAID configuration isn't bootable at all I figured; but it partitioned > fine, and booted properly. I then tried installing NT, and now Linux. > All three had no problems, and all three booted fine. Seeing as how the > other O/S's all installed/worked fine; I'm assuming this is just a > software issue. Maybe with the bios of the Raid controller, or maybe > with the system bios, has anyone else run into similar problems? Am I > just missing something blatenly obvious? Does FreeBSD not boot from a > mirrored volume (if so... why not)? > I've only ever done one other server install with FreeBSD, and a Mylex > Raid controller; it booted fine. It was using an AcceleRAID PCI 150 > card, with foud 9.1gig SCSIUW's in a RAID 5 configuration. It went fine > with no hitches, (cept that it took like 1hr to newfs). However, this is > a different controller, and having little to no experience working with > RAID controllers I figured I'd ask. > Baring no absolute solutions, or better partial ones from this mailing > list, I'm going to install Linux on a 200meg partition, and attempt to > install FreeBSD on the rest and boot it using Lilo (don't know if it's > going to work...but it's worth a try). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 10:33:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 10:33:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 84B0437B402 for ; Wed, 3 Jan 2001 10:33:15 -0800 (PST) Received: by gvr.gvr.org (Postfix, from userid 657) id E9F495848; Wed, 3 Jan 2001 19:33:13 +0100 (CET) Date: Wed, 3 Jan 2001 19:33:13 +0100 From: Guido van Rooij To: Thierry Cc: freebsd-hackers@freebsd.org Subject: Re: gdb question Message-ID: <20010103193313.A26389@gvr.gvr.org> References: <01010312453500.00430@FreeBSD.eicon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01010312453500.00430@FreeBSD.eicon.com>; from tjmsdn@ifrance.com on Wed, Jan 03, 2001 at 12:37:21PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 12:37:21PM -0500, Thierry wrote: > > Hi, > > I use the "fork" function to call another function "foo( )" > > In gdb, I would like to put a breakpoint in this function "foo( )", When I > execute, the function "foo( )" is stopped, but gdb doesn't give me the hand. > > How I can put a breakpoint in a function call by a "fork" system ? If you exec after the fork you could do it with: gdb --exec=program1 --symbols=program2 if program1 exec program2. if you only fork you can use the set follow_fork_mode setting to follow the child. Hmm no that I check it, it does not seem to work though.... I am using a 4.1 stablish system though. Perhaps it does work on later systems. -Guido -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 12:32:37 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 12:32:33 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 86A5037B402; Wed, 3 Jan 2001 12:32:33 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f03KWN002837; Wed, 3 Jan 2001 12:32:23 -0800 (PST) Date: Wed, 3 Jan 2001 12:32:23 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: jlemon@FreeBSD.ORG, rwatson@FreeBSD.ORG, itojun@netbsd.org, hackers@FreeBSD.ORG Subject: Re: TCP Rate-Halving Message-ID: <20010103123223.I292@fw.wintelcom.net> References: <20010103010739.A68404@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103010739.A68404@peorth.iteration.net>; from keichii@iteration.net on Wed, Jan 03, 2001 at 01:07:39AM -0600 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010102 23:07] wrote: > [If need be, please add Cc: to -net] > > While doing my own research project, I came across this piece > of information. It seems like a "nobody-has-it-but-it-is-fast" thing. > > http://www.psc.edu/networking/ftp/papers/draft-ratehalving.txt > > It seeks to improve the Reno TCP implementation by the most > recommended trick in the book, redesigning the algorithm. > >From the above url: > "Hoe [Hoe95] suggested that during Fast Recovery the TCP > data sender space out retransmissions and new data on > alternate acknowledgements across the entire recovery RTT. > (Note that this eliminates the half RTT lull in sending > which occurs in Reno TCP.)" > > Do we already do this? I know that a re-write of our TCP code is > "imminent." This seeks to improve congested server TCP connections. > (Oh BTW, Isn't TCP the little thing that servers use ;-)? ) There's no re-write in progress, just a couple of us slaving away to make it mpsafe. As far as this feature, I'm pretty sure Jaynath was looking at implementing it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 12:41:14 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 12:41:12 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 7E83937B400 for ; Wed, 3 Jan 2001 12:41:08 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id f03Kexi11900; Thu, 4 Jan 2001 02:40:59 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 4 Jan 2001 02:40:58 +0600 (NS) From: Max Khon To: Thierry Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gdb question In-Reply-To: <01010312453500.00430@FreeBSD.eicon.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 3 Jan 2001, Thierry wrote: > I use the "fork" function to call another function "foo( )" > > In gdb, I would like to put a breakpoint in this function "foo( )", When I > execute, the function "foo( )" is stopped, but gdb doesn't give me the hand. > > How I can put a breakpoint in a function call by a "fork" system ? set follow-fork-mode /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 15:34:41 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 15:34:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from beastie.localdomain (c215563-a.stcla1.sfba.home.com [24.19.158.41]) by hub.freebsd.org (Postfix) with ESMTP id 7E31A37B400 for ; Wed, 3 Jan 2001 15:34:38 -0800 (PST) Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.9.3) id PAA01674; Wed, 3 Jan 2001 15:37:14 -0800 (PST) (envelope-from brian) Date: Wed, 3 Jan 2001 15:37:14 -0800 From: "Brian O'Shea" To: Thierry Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gdb question Message-ID: <20010103153714.B637@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Thierry , freebsd-hackers@FreeBSD.ORG References: <01010312453500.00430@FreeBSD.eicon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01010312453500.00430@FreeBSD.eicon.com>; from tjmsdn@ifrance.com on Wed, Jan 03, 2001 at 12:37:21PM -0500 Sender: brian@beastie.localdomain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 12:37:21PM -0500, Thierry wrote: > > Hi, > > I use the "fork" function to call another function "foo( )" > > In gdb, I would like to put a breakpoint in this function "foo( )", When I > execute, the function "foo( )" is stopped, but gdb doesn't give me the hand. > > How I can put a breakpoint in a function call by a "fork" system ? Since foo() is called in another process (the child process of the one that called fork()), you will have to somehow attach to the child process after the fork() call. I don't know if gdb has support for doing this automatically. I don't think it does, but you might be able to attach to it in another gdb session by having the child process sleep for a while shortly after the fork() call to give you enough time to look up the PID of the child process. > > Thanks in Advance. > Thierry. > -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 17:43:49 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 17:43:45 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 967BF37B402 for ; Wed, 3 Jan 2001 17:43:45 -0800 (PST) Received: (qmail 22047 invoked by uid 1078); 4 Jan 2001 01:43:52 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Jan 2001 01:43:52 -0000 Date: Wed, 3 Jan 2001 17:43:52 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Cc: , Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason In-Reply-To: <3A524BF2.E2E1F3BF@wmptl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can add another data point for this. We are using FreeBSD 4.0 (I'll be upgrading them one of these days) and had this exact same problem. My solution was to make a floppy disk and stuff it in the drive. It did the 3 phase boot loader and in the loader.rc I added set currdev=disk1s1a which did the trick. I'm really interested in getting this working as these are our mailservers that I'd rather not trust to having to boot from floppy disks. -gordon On Tue, 2 Jan 2001, Nathan Vidican wrote: > Subject: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server > will not recognize boot record for some reason > > Having problems booting; the system installs to the mylex system drive > fine, but when I reboot, I get the FreeBSD boot MGR, and it only beeps > when I press F1 for FreeBSD. If I install using a normal boot record, > the system reports 'No operating system found'. I'm thinking it may be > an issue with the Mylex card, but I don't know for sure if the system's > bios could cause this either. I cannot attempt to install the mylex card > in another machine; as the drives attached to it are in a hot-swap > carriage which is part of the system's chassis. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 19:15:51 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 19:15:48 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 9F5F537B400 for ; Wed, 3 Jan 2001 19:15:47 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14E0sU-000Mk9-00 for freebsd-hackers@freebsd.org; Thu, 4 Jan 2001 03:15:46 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f043Fjj47431 for freebsd-hackers@freebsd.org; Thu, 4 Jan 2001 03:15:45 GMT (envelope-from jcm) Date: Thu, 4 Jan 2001 03:15:45 +0000 From: j mckitrick To: freebsd-hackers@freebsd.org Subject: frustration with debug messages Message-ID: <20010104031545.A47353@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NzB8fVQJ5HfG6fxh" X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Hello all, I am new to -hackers, and I have run into a very frustrating problem. I am using standard printf statements for status info while debugging the parallel port zip driver in PS2 mode. For a reason I have yet to discover, my messages are no longer appearing consistently in my dmesg output. As I move through the debug process, I will enable and disable blocks of debug output, but when I run dmesg, what I see is not the same as what I saw while the machine was rebooting. These same messages usually end up in /var/log/messages, but I can't figure out the pattern. I saw that messages.4 was not gzipped like the others. Could i have overflowed syslogd and messed things up? I would be happy to post info besides my syslog.conf, but I didn't want to clog the list. My work has come to a standstill, since I cannot access the debug output. Please help! Hopefully it is only a small issue that I can learn from and fix promptly. jm -- ------------------------------------------------------------------------ Jonathon McKitrick -- jcm@freebsd-uk.eu.org They laugh because I'm different. I laugh because they're all the same. ------------------------------------------------------------------------ --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="syslog.conf" # $FreeBSD: src/etc/syslog.conf,v 1.9.2.1 1999/08/29 14:19:02 peter Exp $ # # Spaces are NOT valid field separators in this file. # Consult the syslog.conf(5) manpage. #*.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages #security.* /var/log/security mail.info /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/log/cron *.err root #*.notice;news.err root *.alert /var/log/messages *.emerg * # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log !ipfw *.* /var/log/ipfw.log --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 3 20:41: 7 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 20:41:00 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7714D37B400; Wed, 3 Jan 2001 20:40:58 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2E2826A911; Thu, 4 Jan 2001 15:10:55 +1030 (CST) Date: Thu, 4 Jan 2001 15:10:55 +1030 From: Greg Lehey To: Jeff Fellin Cc: FreeBSD Hackers Subject: Re: debugging kernel buffer overwrite Message-ID: <20010104151054.N40668@wantadilla.lemis.com> References: <200101021935.OAA12733@zydeco.research.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101021935.OAA12733@zydeco.research.bell-labs.com>; from jkf@research.bell-labs.com on Tue, Jan 02, 2001 at 02:35:39PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -hackers] On Tuesday, 2 January 2001 at 14:35:39 -0500, Jeff Fellin wrote: > > I previous sent this mail on freebsd-current, but realize it > was probably an incorrect list. So, I am reposting on to > freebsd-questions. If this is still the wrong list could > someone tell me the best list to post this question to? FreeBSD-hackers, probably. -questions is for administrative rather than programming issues. > I am having a problem with a device driver that uses physio > to transfer data to a SCSI adapter. Some times the after > passing the buffer to the CAM system, via xpt_action, the > buffer contents are modified. I've traced my driver and cannot > determine how this could be happening. I am running on a single > CPU Pentium II system with all system config defaults. > > What I would like to do is to dynamically set a watch point > on the buffer used by the write system call for the duration > of sending the data to the SCSI adapter. I want to do this > dynamically instead of manually setting a breakpoint in the > code and manually setting the watch point, because the problem > occurs around the 90'th time, and I don't want SCSI bus timeouts > while typing the watch address. > > I've examined the ddb code, and thought that if I emulated the > steps in db_trap() for the command of setting a watchpoint it > would work. However, it doesn't appear to be working. > > What I've done is: > > /* possible on data xfer >= 512 bytes */ > if (condition for problem) { > > db_watchpoint_cmd(bp->bio_addr, bp->bio_addr, > bp->bio_count, &"rw"); Why &"rw"? The parameter is a char *, which is the type of "rw". > db_continue_cmd(0, 0, 0, &"w"): > db_restart_at_pc(FALSE); > } > > When the buffer is done transmitting I do the following: > > db_clear_watchpoints(); > db_deletewatch_cmd(bp->bio_addr, bp->cio_addr, > bp->cio_count, &"rw"); > db_continue_cmd(0, 0, 0, &"w"); > db_restart_at_pc(FALSE); > > My driver trace printf's show the data at bp->bio_addr was > changed from 0x601000a3 to 0x0. That's a strange initial address. I didn't think we had anything mapped at 0x601000a3. > Additional traces show the data from the first 200+ bytes is changed > to zero. In the buffer header, or in the data buffer? > Any guidance on how to use the ddb functions to debug this problem > are appreciated. Also, alternative methods to determine what is > overwriting the buffer. In looking at the data on a SCSI bus > analyzer, the entire buffer has been zero'ed out. Hmm. You don't say what goes wrong, nor whether your breakpoints ever get set. In the past I've used the debug registers for this, which has the advantage that, if you know where it's going to get broken, you can set a memory access breakpoint and catch it in the act. I can drag out the functions if you like. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 1:10:49 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 01:10:46 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id D810A37B400 for ; Thu, 4 Jan 2001 01:10:45 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f049Aim21109 for ; Thu, 4 Jan 2001 10:10:44 +0100 (MET) Received: from agamemnon.informatik.rwth-aachen.de (agamemnon.Informatik.RWTH-Aachen.DE [137.226.194.74]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1/2) with ESMTP id KAA02731 for ; Thu, 4 Jan 2001 10:09:59 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id KAA07718 for freebsd-hackers@freebsd.org; Thu, 4 Jan 2001 10:10:41 +0100 (MET) Date: Thu, 4 Jan 2001 10:10:41 +0100 From: Volker Stolz To: freebsd-hackers@freebsd.org Subject: Questions on i2c Message-ID: <20010104101041.A7651@agamemnon.informatik.rwth-aachen.de> Mail-Followup-To: Volker Stolz , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is someone working actively on new i2c-stuff? I´d be interested in talking to someone who could take a short peek at http://www2.lm-sensors.nu/~lm78/info.html, a Linux-site providing i2c-drivers to various things, and could comment on the feasibility of using their stuff to implement FreeBSD-drivers. Devices include video-devices like TV-Out on the Voodoo3 which could seemingly be enabled using i2c. FreeBSD´s bktr-driver seems too big for me to get me started on trying to attach only a driver which would look for the Voodoo. Is there any further documentation on what I can do with /dev/iic*? Regards, Volker -- \usepackage[latin1]{inputenc}! Volker Stolz * stolz@i2.informatik.rwth-aachen.de * PGP + S/MIME To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 3:30:19 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 03:30:11 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg134-005.ricochet.net [204.179.134.5]) by hub.freebsd.org (Postfix) with ESMTP id D875C37B400; Thu, 4 Jan 2001 03:30:06 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id DAA00395; Thu, 4 Jan 2001 03:29:33 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101041129.DAA00395@spammie.svbug.com> Date: Thu, 4 Jan 2001 03:29:32 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: The Talk: ssh - are you nuts!?! To: tech@openbsd.org Cc: tech-security@netbsd.org, freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: jessem@spammie.svbug.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SSH - are you nuts!?! by Jesus Monroy, Jr. I'm too tired to get this out, but i promised it would be available, so here it is. The Offical Part ---------------- On Jan. 4, 2001, a talk entitled "ssh - are you nuts!?!" will be given at the SVBUG (Silicon Valley BSD User Group) monthly meeting by Club President Jesse Monroy, Jr. Details available at: http://www.svbug.com/events/ My part ------- Today at 7:45pm (local time) this talk will start. People say I'm nuts, sometimes I think they are right. Currently, I've heard hundreds of points of views, read dozens of papers, and comtemplated solutions with vicious circles. Two days before Christmas I related this to my brother-in-law, a Havard/Yale/Cambridge MBA. His response was, "Builds character."; hmm.. Thanks. Other club presidents ask me, "Are you serious about this?" My business partner expressed, just after Christmas, "Is this worth it?" I'll admit, at times, this whole thing has been a bit crazy. So as I've said today at 7:45pm local time, here in Silicon Valley, I will be speaking. The title is "SSH - are you nuts!?!" What do I mean by this? Well to get exactly what I mean you may: 1) Come to the talk. Details are available at: http://www.svbug.com/events/ 2) See my notes after the talk - posted to: http://www.svbug.com/past/ 3) Or see the event with on-line video when it's available later this year. For those you you interested, below are selected points from my talk. ------------------------------------------------------------------- -What I won't be saying -SSH is evil. -SSH is useless. -SSH is a bad idea. -Authentication/Encryption is a hoax or does not work. -Public Key Encryption does not work. (I have no proof.) -I can break Public Key Encryption. (At least, not now.) -I USE SSH. (1 or 2) -I never intend to use SSH. -My systems have never been compromised. -My frame of reference -What I will be saying -Voice my personal complaints -Expose encryption/security myths -Investigate the technical specs/issues -Investigage Technical, Social, Economic, Financial Problems -Investigate attackers and attacks -Tell you where to get SSH -Showing alternatives -Why I'm doing this -My Personal Complaints -What people have to say -SSHv1 vs. SSHv2 -SSHv2 Features -The SSH Specs (the problems within) -Authentication/Encryption - Two methods to argue -can never be broken -can always be broken -SSH(v2) Faults -New Technical problems it creates -Technical Problems outside of SSH control -There are common misconceptions about it's functionality -Social Problems -Economic Problems -Financial Problems -Still Subject to ... -Who wants your data -What is the Man-In-The-Middle -Your Governments Involvement -What SSH programs there are -What alternatives you have -Start with a Strategem -Technical Prevention -Technical Counter Measures -Last words To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 4:38: 5 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 04:38:03 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 2097437B400 for ; Thu, 4 Jan 2001 04:37:59 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id OAA25321 for ; Thu, 4 Jan 2001 14:37:54 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 25178; Thu Jan 4 14:36:44 2001 Sender: gram@citadel.cequrux.com Message-ID: <3A545615.3597BCF3@cequrux.com> Date: Thu, 04 Jan 2001 12:53:09 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Just how standard is APM? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I'm running FreeBSD 4.2-S on a Compaq Presario laptop. This laptop seems to have APM support (at least it does under MS-Windows), but FreeBSD doesn't recognise it as such. I've gone so far as to add additional log messages in the kernel probes for the APM BIOS, and these log that the initial vm86 BIOS call to get the APM BIOS version fail. Is this really exceptional, or are there lots of unsupported APM BIOSes? I believe that APM is a WinTel `standard'; just how standard is it really? -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 6: 3:11 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 06:03:09 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 87CA737B400 for ; Thu, 4 Jan 2001 06:03:09 -0800 (PST) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id FAA24551; Thu, 4 Jan 2001 05:53:47 -0800 (PST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id JAA06947; Thu, 4 Jan 2001 09:02:47 -0500 (EST) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id JAA23917; Thu, 4 Jan 2001 09:02:46 -0500 for Message-Id: <200101041402.JAA23917@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Volker Stolz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions on i2c In-Reply-To: Message from Volker Stolz of "Thu, 04 Jan 2001 10:10:41 +0100." <20010104101041.A7651@agamemnon.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 09:02:47 -0500 From: Robert Withrow Sender: bwithrow@BayNetworks.COM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG stolz@I2.Informatik.RWTH-Aachen.DE said: :- Devices include video-devices like TV-Out on the Voodoo3 which could :- seemingly be enabled using i2c. And, I think, Meade telescopes... -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 7:43:36 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 07:43:33 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 557A837B404 for ; Thu, 4 Jan 2001 07:43:32 -0800 (PST) Received: (qmail 13836 invoked from network); 4 Jan 2001 15:41:27 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 4 Jan 2001 15:41:27 -0000 Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f04CmTp03741; Thu, 4 Jan 2001 12:48:29 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200101041248.f04CmTp03741@jhs.muc.de> To: Warner Losh Cc: hackers@freebsd.org, jhs@jhs.muc.de Subject: Re: Easy way to recover disk In-Reply-To: Message from Warner Losh of "Fri, 29 Dec 2000 18:21:38 MST." <200012300121.SAA00902@harmony.village.org> Date: Thu, 04 Jan 2001 13:48:29 +0100 From: "Julian Stacey Jhs@jhs.muc.de" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > OK. I have a disk drive that is failing in random ways. Today blocks > 123 456 and 293 might be unreadable. Tomorrow, it might be these and > 27 or it might just be 27. It is an IDE drive. I was wondering if anybody > had a program that would read the entire disk and keep a list/bitmap of > the bad blocks and try them again next time the program is run. Operating > on a slice or partition level would be ideal (I have a 20G disk that > is failing, but only about 18G of free space). > > Ideas? > > Warner > > P.S. Basically what I want at the end of the day, disk willing, is > what dd if=/dev/ad8s2a of=/huge/big-honkin-file ... would give me. > I want this so I can then dump it to tape. I can't run dump directly > since it hits those bad blocks and whines. I have 2 C programs you might like to extend/ plunder `for parts' :-) http://bim.bsn.com/~jhs/src/bsd/jhs/bin/public/valid/valid.c & valid.1 Makefile http://bim.bsn.com/~jhs/src/bsd/jhs/bin/public/slice/slice.c & slice.1 Makefile valid: rescues (or writes) arbitrary (or all) sectors of a floppy, but can also be given the name of other devices eg hard disc & normal files. It works best on dos ! as dos returns the buffer even if there's a crc error, If someone hacked the bsd kernel to return the read() buffer even on error, it'd make it equally usefull to rescue sectors on bsd too. slice: rescue data off bad tapes with intermittent drivers, first written to run on BSD4.2 nsc32016, also runs on freebsd of course. More info in the manuals on the web. Julian - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Considering Linux ? Try FreeBSD with its 4200 packages ! Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 8: 0: 3 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 07:59:59 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from theo.forman.homeip.net (pc68-lei2.cable.ntl.com [62.254.20.68]) by hub.freebsd.org (Postfix) with ESMTP id E8E2937B400 for ; Thu, 4 Jan 2001 07:59:58 -0800 (PST) Received: from localhost (mcf@localhost) by theo.forman.homeip.net (8.11.0/8.11.0) with ESMTP id f04Fxvd13769 for ; Thu, 4 Jan 2001 15:59:57 GMT (envelope-from mcf@forman.homeip.net) Date: Thu, 4 Jan 2001 15:59:57 +0000 (GMT) From: "Matthew C. Forman" To: freebsd-hackers@freebsd.org Subject: Allocating an IRQ on PCI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I want to allocate an IRQ for a PCI device driver. Normally this is easy enough, since the BIOS would reserve it for me, then I would just have to bus_alloc_resource and not even care which IRQ line it's using. Thing is, here the BIOS hasn't allocated an IRQ, so I'll need to bus_set_resource in my probe to get one. To complicate matters, the device's interrupt generator is pretty flexible, and can generate an interrupt on (almost) any IRQ line. I have to tell it which IRQ to use when I know which one has been allocated. I can see two possibilities to get this working: 1. Hardwire it, by using bus_set_resource with a specific IRQ. This isn't nice, as it'll fail if someone else's setup is already using the one I pick (or some other device attach will fail later on). 2. Find out what IRQs are free and set and allocate one of those. This is nicer than 1), but then if some poor device attach later on in boot was expecting to use that IRQ, it'll break. Does anyone know of a sensible & portable way around this? Perhaps IRQ sharing could save me in some way... Thanks in advance, Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 8:35:50 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 08:35:48 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id B1B3D37B400 for ; Thu, 4 Jan 2001 08:35:47 -0800 (PST) Received: from fwd02.sul.t-online.com by mailout05.sul.t-online.com with smtp id 14EDMg-000100-02; Thu, 04 Jan 2001 17:35:46 +0100 Received: from venus.mailsurf.com (320051988339-0001@[62.224.117.106]) by fmrl02.sul.t-online.com with esmtp id 14EDMT-1aOCxcC; Thu, 4 Jan 2001 17:35:33 +0100 Received: by venus.mailsurf.com (Postfix, from userid 1001) id ABC681AB29; Thu, 4 Jan 2001 17:35:31 +0100 (CET) Date: Thu, 4 Jan 2001 17:35:30 +0100 From: Sven Huster To: freebsd-hackers@freebsd.org Subject: release with custom kernel Message-ID: <20010104173530.A54132@venus.mailsurf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi there, after asking this in questions for a while, i want to give hackers a try. is there a possibility to make a release with a custom kernel? i know how to create a release but it contains always the GENERIC kernel. thanks sven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 9: 0:28 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 09:00:27 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id B610C37B400 for ; Thu, 4 Jan 2001 09:00:19 -0800 (PST) Received: (qmail 5442 invoked by uid 1000); 4 Jan 2001 16:59:03 -0000 Date: Thu, 4 Jan 2001 18:59:03 +0200 From: Peter Pentchev To: freebsd-hackers@FreeBSD.org Subject: more than 8 colors in console? Message-ID: <20010104185903.C545@ringworld.oblivion.bg> Mail-Followup-To: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm writing a console app, which needs to be quite colorful, and to use customizable colors. Unfortunately, with ncurses, right after start_color(), I get a can_change_color() == FALSE. Besides, COLORS is defined to as many as the Co termcap capability, which is 8. Well, all (well, most ;) PC video adapters can display up to 16 colors, if I decide to drop the bold/blinking capabilities, and define all colors as suits my taste. Is there a way to define more than 8 colors, and.. uh.. is there a way to define *any* colors at all? :) G'luck, Peter -- I am the thought you are now thinking. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 9:34:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 09:34:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 4E89237B400 for ; Thu, 4 Jan 2001 09:34:15 -0800 (PST) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id MAA32452 for ; Thu, 4 Jan 2001 12:27:43 -0500 Date: Thu, 4 Jan 2001 12:27:43 -0500 (EST) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: kernel threads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are threads on FreeBSD 4.x implemented at the kernel level? If so, since when (I remember 2.x used MIT-threads, so I'm guessing at least since 3.x)? How can I see for myself that threads are really implemented at the kernel level? I looked around in /usr/src/sys/kern, but couldn't find anything relating to threads there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 9:48:34 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 09:48:29 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 31B0E37B402 for ; Thu, 4 Jan 2001 09:48:29 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA15041; Thu, 4 Jan 2001 12:48:27 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA00778; Thu, 4 Jan 2001 12:48:27 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA00774; Thu, 4 Jan 2001 12:48:27 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 4 Jan 2001 12:48:27 -0500 (EST) From: Kenneth Wayne Culver To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel threads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are threads on FreeBSD 4.x implemented at the > kernel level? No, as far as I know, those are coming in FreeBSD 5.0 (which won't be out for a while) > > If so, since when (I remember 2.x used MIT-threads, > so I'm guessing at least since 3.x)? > > How can I see for myself that threads are really > implemented at the kernel level? I looked around > in /usr/src/sys/kern, but couldn't find anything > relating to threads there. > They aren't really implemented at the kernel level yet, but something like kernel threads will be in 5.x when it comes out. If you really need kernel threads in FreeBSD take a look at /usr/ports/devel/linuxthreads. Those do kernel threads through a call to rfork I believe. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 9:48:37 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 09:48:28 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smarthost2.mail.easynet.fr (smarthost2.mail.easynet.fr [212.180.1.69]) by hub.freebsd.org (Postfix) with ESMTP id 68E2C37B400 for ; Thu, 4 Jan 2001 09:48:28 -0800 (PST) Received: from smtp1.mail.easynet.fr (slb-1-sippriv.mail.easynet.fr [10.0.1.57]) by smarthost2.mail.easynet.fr (Postfix) with ESMTP id 1FCFEB92D for ; Thu, 4 Jan 2001 18:48:27 +0100 (CET) Received: from foret (adsl-rde-1-179.pops.easynet.fr [212.11.36.179]) by smtp1.mail.easynet.fr (Postfix) with ESMTP id 87545B6B2 for ; Thu, 4 Jan 2001 18:48:26 +0100 (CET) Received: by foret (Postfix, from userid 1001) id EF2BA32165; Thu, 4 Jan 2001 18:48:28 +0100 (CET) Date: Thu, 4 Jan 2001 18:48:28 +0100 From: ecureuil To: hackers@FreeBSD.org Subject: getifaddrs Message-ID: <20010104184828.A12168@foret> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT X-Mailer: =?iso-8859-1?Q?Outlook_Exp^H^H^H^H^H^H^H^H_nan_j'd=E9conne_:=29?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi I'm trying to get interfaces' list and infos with getifaddrs(). The ifa_data struct should contain all needed information, but this is a NULL pointer for IPv4 interfaces. Why ? a sample output for my ethernet card : ed0 ( 6.3.6.0) : UP, AF_INET6 MTU=1500 (struct ifa_data) ed0 ( 10.0.0.1) : UP MTU=1500 (struct ifa_data is a null pointer) BTW, there is always 2 nodes for each interface, even if INET6 is not enabled in the kernel. is it normal ? thanks (see the source attached) -- ecureuil --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="getifinfo.c" /* ecureuil get interface information */ #include #include #include #include #include #include #include #include #include #include int main(int argc, char **argv) { struct ifaddrs *ifap, *ifa; struct sockaddr_in *sa; int fd; struct ifreq ifr; char ifstraddr[16]; sa_family_t fam; if (getifaddrs(&ifap) < 0) { perror("getifaddrs"); return -1; } for (ifa = ifap; ifa; ifa = ifa->ifa_next) { printf("%6s ", ifa->ifa_name); /* get if address */ sa = (struct sockaddr_in *) ifa->ifa_addr; strncpy(ifstraddr, inet_ntoa(sa->sin_addr), 16); printf("(%15s) : ",ifstraddr); if (!(ifa->ifa_flags & IFF_UP)) printf("DOWN"); else printf("UP"); if (ifa->ifa_flags & IFF_PROMISC) printf(", PROMISCUOUS"); if (ifa->ifa_addr->sa_family & AF_INET6) printf(", AF_INET6"); /* get if mtu */ fam = ifa->ifa_addr->sa_family == AF_LINK ? AF_INET : ifa->ifa_addr->sa_family; if ((fd = socket(AF_INET, SOCK_DGRAM, 0)) < 0 ) { perror("[get_if_name] socket(AF_INET, SOCK_DGRAM, 0)"); return -1; } strncpy(ifr.ifr_name,ifa->ifa_name,IFNAMSIZ); if (ioctl(fd, SIOCGIFMTU, &ifr) < 0 ) { perror("ioctl"); return -1; } else { printf(" MTU=%d ",ifr.ifr_mtu); } close(fd); if(ifa->ifa_data) printf("(struct ifa_data)\n"); else printf("(struct ifa_data is a null pointer)\n"); } freeifaddrs(ifap); return 0; } --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 10:20: 4 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 10:20:01 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id AACBB37B400 for ; Thu, 4 Jan 2001 10:20:00 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f04IJuD34137; Thu, 4 Jan 2001 10:19:56 -0800 (PST) Date: Thu, 4 Jan 2001 10:19:56 -0800 (PST) From: Doug White To: Rafael Barrero Cc: hackers@FreeBSD.ORG Subject: Re: BSD dlopen and such In-Reply-To: <20010102152714.A3189@lokigames.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001, Rafael Barrero wrote: > Hi all, > > Two questions: > > 0) Are native binaries for OpenBSD different from FreeBSD? Yes. > 1) Can a native binary dlopen a Linux ELF GL, yes or no? No. The linux compatbility is through the image activator. The syscalls have to be translated, otherwise if you were running as root and loaded a linux lib into a freebsd binary, then that lib called fcntl(), your system would reboot :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 11:17:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 11:17:28 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4026937B69B for ; Thu, 4 Jan 2001 11:17:21 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f04JGVG60003; Thu, 4 Jan 2001 11:16:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 04 Jan 2001 11:17:27 -0800 (PST) From: John Baldwin To: Marc Tardif Subject: RE: kernel threads Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-01 Marc Tardif wrote: > Are threads on FreeBSD 4.x implemented at the > kernel level? No, they probably will not be until 6.0. > If so, since when (I remember 2.x used MIT-threads, > so I'm guessing at least since 3.x)? > > How can I see for myself that threads are really > implemented at the kernel level? I looked around > in /usr/src/sys/kern, but couldn't find anything > relating to threads there. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 14:34:26 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 14:34:25 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1B53237B400 for ; Thu, 4 Jan 2001 14:34:24 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f04MYMl08971; Thu, 4 Jan 2001 15:34:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.8.3) with ESMTP id f04MYM147333; Thu, 4 Jan 2001 15:34:22 -0700 (MST) Message-Id: <200101042234.f04MYM147333@harmony.village.org> To: Graham Wheeler Subject: Re: Just how standard is APM? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Jan 2001 12:53:09 +0200." <3A545615.3597BCF3@cequrux.com> References: <3A545615.3597BCF3@cequrux.com> Date: Thu, 04 Jan 2001 15:34:22 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A545615.3597BCF3@cequrux.com> Graham Wheeler writes: : Hi all : : I'm running FreeBSD 4.2-S on a Compaq Presario laptop. This laptop seems : to have APM support (at least it does under MS-Windows), but FreeBSD : doesn't recognise it as such. I've gone so far as to add additional log : messages in the kernel probes for the APM BIOS, and these log that the : initial vm86 BIOS call to get the APM BIOS version fail. : : Is this really exceptional, or are there lots of unsupported APM BIOSes? : I believe that APM is a WinTel `standard'; just how standard is it : really? APM is standard. Except when it is broken in some brain damaged ways. However, you likely have your apm device disabled in your kernel and all you need to do is enable it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 14:36:19 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 14:36:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1FB2937B404 for ; Thu, 4 Jan 2001 14:36:11 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f04Ma9l08982; Thu, 4 Jan 2001 15:36:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.8.3) with ESMTP id f04Ma5147356; Thu, 4 Jan 2001 15:36:09 -0700 (MST) Message-Id: <200101042236.f04Ma5147356@harmony.village.org> To: "Matthew C. Forman" Subject: Re: Allocating an IRQ on PCI Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Jan 2001 15:59:57 GMT." References: Date: Thu, 04 Jan 2001 15:36:05 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew C. Forman" writes: : Thing is, here the BIOS hasn't allocated an IRQ, so I'll need to : bus_set_resource in my probe to get one. To complicate matters, the : device's interrupt generator is pretty flexible, and can generate an : interrupt on (almost) any IRQ line. I have to tell it which IRQ to use : when I know which one has been allocated. No. You don't want to use bus_set_resource() since it won't do what you want. What version of FreeBSD are you failing with? Newer versions of current just do the right thing. Otherwise you will have to turn plug and play OFF. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 16:26:40 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 16:26:36 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 792E137B400 for ; Thu, 4 Jan 2001 16:26:35 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA16599; Thu, 4 Jan 2001 16:26:31 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f050QU703172; Thu, 4 Jan 2001 16:26:30 -0800 (PST) (envelope-from jdp) Date: Thu, 4 Jan 2001 16:26:30 -0800 (PST) Message-Id: <200101050026.f050QU703172@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: rcarter@pinyon.org Subject: Re: ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/rtld.c:2033 In-Reply-To: <20001230164716.6366F9B@pinyon.org> References: <20001230164716.6366F9B@pinyon.org> Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001230164716.6366F9B@pinyon.org>, Russell L. Carter wrote: > > Bingo! > > Thanks guys! Not so fast there, fella. You're not getting off that easily. ;-) Could you please try the patch below? It is like the patch that Paul sent, except it should handle error conditions better. This patch is against -current, but I think it will apply cleanly to -stable too. Thanks, John Index: rtld.c =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/rtld.c,v retrieving revision 1.50 diff -u -r1.50 rtld.c --- rtld.c 2000/11/07 22:41:53 1.50 +++ rtld.c 2001/01/05 00:13:18 @@ -77,6 +77,8 @@ static Obj_Entry *digest_phdr(const Elf_Phdr *, int, caddr_t, const char *); static Obj_Entry *dlcheck(void *); static bool donelist_check(DoneList *, const Obj_Entry *); +static void errmsg_restore(char *); +static char *errmsg_save(void); static char *find_library(const char *, const Obj_Entry *); static const char *gethints(void); static void init_dag(Obj_Entry *); @@ -457,6 +459,30 @@ va_end(ap); } +/* + * Return a dynamically-allocated copy of the current error message, if any. + */ +static char * +errmsg_save(void) +{ + return error_message == NULL ? NULL : xstrdup(error_message); +} + +/* + * Restore the current error message from a copy which was previously saved + * by errmsg_save(). The copy is freed. + */ +static void +errmsg_restore(char *saved_msg) +{ + if (saved_msg == NULL) + error_message = NULL; + else { + _rtld_error("%s", saved_msg); + free(saved_msg); + } +} + static const char * basename(const char *name) { @@ -696,7 +722,7 @@ if (obj == (Obj_Entry *) handle) break; - if (obj == NULL || obj->dl_refcount == 0) { + if (obj == NULL || obj->refcount == 0 || obj->dl_refcount == 0) { _rtld_error("Invalid shared object handle %p", handle); return NULL; } @@ -1184,13 +1210,20 @@ objlist_call_fini(Objlist *list) { Objlist_Entry *elm; + char *saved_msg; + /* + * Preserve the current error message since a fini function might + * call into the dynamic linker and overwrite it. + */ + saved_msg = errmsg_save(); STAILQ_FOREACH(elm, list, link) { if (elm->obj->refcount == 0) { dbg("calling fini function for %s", elm->obj->path); (*elm->obj->fini)(); } } + errmsg_restore(saved_msg); } /* @@ -1202,11 +1235,18 @@ objlist_call_init(Objlist *list) { Objlist_Entry *elm; + char *saved_msg; + /* + * Preserve the current error message since an init function might + * call into the dynamic linker and overwrite it. + */ + saved_msg = errmsg_save(); STAILQ_FOREACH(elm, list, link) { dbg("calling init function for %s", elm->obj->path); (*elm->obj->init)(); } + errmsg_restore(saved_msg); } static void @@ -2030,7 +2070,8 @@ { const Needed_Entry *needed; - assert(root->refcount != 0); + if (root->refcount == 0) + return; root->refcount--; if (root->refcount == 0) for (needed = root->needed; needed != NULL; needed = needed->next) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 16:51:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 16:51:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from jello.geekspace.com (jello.geekspace.com [63.175.99.14]) by hub.freebsd.org (Postfix) with SMTP id 79EA037B400 for ; Thu, 4 Jan 2001 16:51:15 -0800 (PST) Received: (qmail 39498 invoked from network); 5 Jan 2001 00:53:56 -0000 Received: from footrest.third-rail.net (HELO geekspace.com) (63.175.99.10) by jello.geekspace.com with SMTP; 5 Jan 2001 00:53:56 -0000 Message-ID: <3A551ABD.DBC9BD5C@geekspace.com> Date: Thu, 04 Jan 2001 19:52:13 -0500 From: Chris Williams X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: rozzin@geekspace.com Subject: Strange fwrite() behavior in a+ mode Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I run the following program, I get the following results: --- jello:/usr/home/chris/foo$ cat blah.c #include int main() { FILE *f = fopen("foo", "a+"); char x[50] = " "; char y[50] = " "; fseek(f, 0, SEEK_SET); printf("tell: %d\n", ftell(f)); printf("fread return'd: %d\n", fread(x, (size_t) 1, (size_t)3, f)); printf("read: %s\n", x); printf("tell: %d\n", ftell(f)); fwrite("xxx", (size_t) 1, (size_t) 3, f); printf("tell: %d\n", ftell(f)); printf("fread return'd: %d\n", fread(y, (size_t) 1, (size_t)3, f)); printf("read: %s\n", y); printf("tell: %d\n", ftell(f)); } jello:/usr/home/chris/foo$ cat foo 123456789 jello:/usr/home/chris/foo$ cc blah.c -o bar;./bar tell: 0 fread return'd: 3 read: 123 tell: 3 tell: 13 fread return'd: 0 read: tell: 13 jello:/usr/home/chris/foo$ --- But, if I comment out the read before the write, I get somewhat strange behavior: --- jello:/usr/home/chris/foo$ cat blah.c #include int main() { FILE *f = fopen("foo", "a+"); char x[50] = " "; char y[50] = " "; fseek(f, 0, SEEK_SET); printf("tell: %d\n", ftell(f)); // printf("fread return'd: %d\n", fread(x, (size_t) 1, (size_t)3, f)); // printf("read: %s\n", x); printf("tell: %d\n", ftell(f)); fwrite("xxx", (size_t) 1, (size_t) 3, f); printf("tell: %d\n", ftell(f)); printf("fread return'd: %d\n", fread(y, (size_t) 1, (size_t)3, f)); printf("read: %s\n", y); printf("tell: %d\n", ftell(f)); } jello:/usr/home/chris/foo$ cat foo 123456789 jello:/usr/home/chris/foo$ cc blah.c -o bar;./bar tell: 0 tell: 0 tell: 3 fread return'd: 0 read: tell: 13 jello:/usr/home/chris/foo$ --- It tells me I'm at 3, but my read acts as if I'm at the end of the file, and then after trying to read it tells me I'm at 13 (the end). Is this a bug? Am I doing something illegal, and the behavior is random? Or..? According to Rozzin (CCed, who brought the issue to my attention), under Linux he sees the first behavior (move pointer to end of file, and tell you that) consistantly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 16:52:14 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 16:52:11 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122]) by hub.freebsd.org (Postfix) with ESMTP id 3E23037B400 for ; Thu, 4 Jan 2001 16:52:09 -0800 (PST) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id BAA53610; Fri, 5 Jan 2001 01:52:08 +0100 (CET) (envelope-from assar) Sender: assar@assaris.sics.se To: ecureuil Cc: hackers@FreeBSD.ORG Subject: Re: getifaddrs References: <20010104184828.A12168@foret> From: Assar Westerlund Date: 05 Jan 2001 01:52:07 +0100 In-Reply-To: ecureuil's message of "Thu, 4 Jan 2001 18:48:28 +0100" Message-ID: <5l4rzen7m0.fsf@assaris.sics.se> Lines: 41 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ecureuil writes: > Hi Hello. > I'm trying to get interfaces' list and infos with getifaddrs(). > The ifa_data struct should contain all needed information, but > this is a NULL pointer for IPv4 interfaces. Why ? What you are printing is the link level address and the v4 address for each interface. > a sample output for my ethernet card : > > ed0 ( 6.3.6.0) : UP, AF_INET6 MTU=1500 (struct ifa_data) > ed0 ( 10.0.0.1) : UP MTU=1500 (struct ifa_data is a null pointer) > > > BTW, there is always 2 nodes for each interface, even if INET6 is not > enabled in the kernel. is it normal ? Yes, one link-level and one v4-level. > /* get if address */ > sa = (struct sockaddr_in *) ifa->ifa_addr; > strncpy(ifstraddr, inet_ntoa(sa->sin_addr), 16); Don't do this. You don't know if it's a v4 adress. Look at sa->sa_family to figure out what kind of address it is first. > if (ifa->ifa_addr->sa_family & AF_INET6) printf(", AF_INET6"); Do == AF_INET6 > if(ifa->ifa_data) printf("(struct ifa_data)\n"); > else printf("(struct ifa_data is a null pointer)\n"); Hu? For v4 addresses, ifa_data is NULL, but for link-level addresses, ifa_dat points to `struct if_data'. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 17:15: 9 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 17:15:06 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 166CA37B400 for ; Thu, 4 Jan 2001 17:15:06 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f051F4c15995; Thu, 4 Jan 2001 17:15:04 -0800 (PST) Date: Thu, 4 Jan 2001 17:15:04 -0800 From: Alfred Perlstein To: Chris Williams Cc: freebsd-hackers@FreeBSD.ORG, rozzin@geekspace.com Subject: Re: Strange fwrite() behavior in a+ mode Message-ID: <20010104171504.A15744@fw.wintelcom.net> References: <3A551ABD.DBC9BD5C@geekspace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A551ABD.DBC9BD5C@geekspace.com>; from psion@geekspace.com on Thu, Jan 04, 2001 at 07:52:13PM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Chris Williams [010104 16:51] wrote: > If I run the following program, I get the following results: [snip] I wish you would have summarized that better... > > It tells me I'm at 3, but my read acts as if I'm at the end of the file, and > then after trying to read it tells me I'm at 13 (the end). > > Is this a bug? Am I doing something illegal, and the behavior is random? Or..? > > According to Rozzin (CCed, who brought the issue to my attention), under Linux > he sees the first behavior (move pointer to end of file, and tell you that) > consistantly. from the manpage: ``a+'' Open for reading and writing. The file is created if it does not exist. The stream is positioned at the end of the file. Subse- quent writes to the file will always end up at the then current end of file, irrespective of intervening fseek()s. It doesn't say anything about reads. So in Linux, if you have a "a+" file, you can 1) seek somewhere (mid file) 2) read some data (not until EOF) 3) after the read you are at EOF again? this doesn't sound really intuative. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 19:22:52 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 19:22:48 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from phnxpop2.phnx.uswest.net (phnxpop2.phnx.uswest.net [206.80.192.2]) by hub.freebsd.org (Postfix) with SMTP id E1B5537B400 for ; Thu, 4 Jan 2001 19:22:47 -0800 (PST) Received: (qmail 11995 invoked by uid 0); 5 Jan 2001 03:22:46 -0000 Received: from ndslppp221.phnx.uswest.net (HELO pinyon.org) (63.224.136.221) by phnxpop2.phnx.uswest.net with SMTP; 5 Jan 2001 03:22:46 -0000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 62E3D8F; Thu, 4 Jan 2001 20:22:46 -0700 (MST) Date: Thu, 04 Jan 2001 20:22:46 -0700 Message-Id: <20010105032246.62E3D8F@pinyon.org> From: "Russell L. Carter" To: "John Polstra" Cc: hackers@FreeBSD.ORG X-Mailer: exmh version 2.1.1 10/15/1999 Subject: Re: ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/rtld.c:2033 In-Reply-To: Message from John Polstra of "Thu, 04 Jan 2001 16:26:30 PST." <200101050026.f050QU703172@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %In article <20001230164716.6366F9B@pinyon.org>, %Russell L. Carter wrote: %> %> Bingo! %> %> Thanks guys! % %Not so fast there, fella. You're not getting off that easily. ;-) %Could you please try the patch below? It is like the patch that Paul %sent, except it should handle error conditions better. % %This patch is against -current, but I think it will apply cleanly to %-stable too. My pleasure. This patch applies cleanly against a two day old -stable, and works just as well as the first patch, i.e., my program works as expected. Thanks! Russell %Thanks, %John % %Index: rtld.c %=================================================================== %RCS file: /home/ncvs/src/libexec/rtld-elf/rtld.c,v %retrieving revision 1.50 %diff -u -r1.50 rtld.c %--- rtld.c 2000/11/07 22:41:53 1.50 %+++ rtld.c 2001/01/05 00:13:18 %@@ -77,6 +77,8 @@ % static Obj_Entry *digest_phdr(const Elf_Phdr *, int, caddr_t, const char *); % static Obj_Entry *dlcheck(void *); % static bool donelist_check(DoneList *, const Obj_Entry *); %+static void errmsg_restore(char *); %+static char *errmsg_save(void); % static char *find_library(const char *, const Obj_Entry *); % static const char *gethints(void); % static void init_dag(Obj_Entry *); %@@ -457,6 +459,30 @@ % va_end(ap); % } % %+/* %+ * Return a dynamically-allocated copy of the current error message, if any. %+ */ %+static char * %+errmsg_save(void) %+{ %+ return error_message == NULL ? NULL : xstrdup(error_message); %+} %+ %+/* %+ * Restore the current error message from a copy which was previously saved %+ * by errmsg_save(). The copy is freed. %+ */ %+static void %+errmsg_restore(char *saved_msg) %+{ %+ if (saved_msg == NULL) %+ error_message = NULL; %+ else { %+ _rtld_error("%s", saved_msg); %+ free(saved_msg); %+ } %+} %+ % static const char * % basename(const char *name) % { %@@ -696,7 +722,7 @@ % if (obj == (Obj_Entry *) handle) % break; % %- if (obj == NULL || obj->dl_refcount == 0) { %+ if (obj == NULL || obj->refcount == 0 || obj->dl_refcount == 0) { % _rtld_error("Invalid shared object handle %p", handle); % return NULL; % } %@@ -1184,13 +1210,20 @@ % objlist_call_fini(Objlist *list) % { % Objlist_Entry *elm; %+ char *saved_msg; % %+ /* %+ * Preserve the current error message since a fini function might %+ * call into the dynamic linker and overwrite it. %+ */ %+ saved_msg = errmsg_save(); % STAILQ_FOREACH(elm, list, link) { % if (elm->obj->refcount == 0) { % dbg("calling fini function for %s", elm->obj->path); % (*elm->obj->fini)(); % } % } %+ errmsg_restore(saved_msg); % } % % /* %@@ -1202,11 +1235,18 @@ % objlist_call_init(Objlist *list) % { % Objlist_Entry *elm; %+ char *saved_msg; % %+ /* %+ * Preserve the current error message since an init function might %+ * call into the dynamic linker and overwrite it. %+ */ %+ saved_msg = errmsg_save(); % STAILQ_FOREACH(elm, list, link) { % dbg("calling init function for %s", elm->obj->path); % (*elm->obj->init)(); % } %+ errmsg_restore(saved_msg); % } % % static void %@@ -2030,7 +2070,8 @@ % { % const Needed_Entry *needed; % %- assert(root->refcount != 0); %+ if (root->refcount == 0) %+ return; % root->refcount--; % if (root->refcount == 0) % for (needed = root->needed; needed != NULL; needed = needed->next) % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-hackers" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 20:31:33 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 20:31:32 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B1F9E37B400 for ; Thu, 4 Jan 2001 20:31:31 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA17296; Thu, 4 Jan 2001 20:31:28 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f054VSv03952; Thu, 4 Jan 2001 20:31:28 -0800 (PST) (envelope-from jdp) Date: Thu, 4 Jan 2001 20:31:28 -0800 (PST) Message-Id: <200101050431.f054VSv03952@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: rcarter@pinyon.org Subject: Re: ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/rtld.c:2033 In-Reply-To: <20010105032246.62E3D8F@pinyon.org> References: <20010105032246.62E3D8F@pinyon.org> Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > %Could you please try the patch below? It is like the patch that Paul > %sent, except it should handle error conditions better. > % > %This patch is against -current, but I think it will apply cleanly to > %-stable too. > > My pleasure. This patch applies cleanly against a two day old > -stable, and works just as well as the first patch, i.e., my > program works as expected. Thanks, Russell! I'll commit it to -current and MFC in a few days. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 22:32:44 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 22:32:39 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id A4FA037B400; Thu, 4 Jan 2001 22:32:38 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f056iQt03104; Thu, 4 Jan 2001 22:44:26 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050644.f056iQt03104@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nathan@vidican.com Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason In-reply-to: Your message of "Tue, 02 Jan 2001 16:45:22 EST." <3A524BF2.E2E1F3BF@wmptl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 22:44:26 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This machine is an Intel Pentium Pro based system, (not a DEC Alpha), it > currently has one 200mhz 512K CPU, 196megs RAM, (4 x 32edo simms, 4 x > 16edo simms), and two 4.5Gig SCSI disks in hot-swappable drive carriages > configured using RAID 1 (mirrored), attached to a Mylex DAC960P/PD > dual-channel controller. I have flashed the firmware of the controller > card to 3.52, as reccomended during the dmesg prompts (the card > initially had < 3.51). The problem seems to be with booting, I have > tried several installs; all seem to partition fine except for > 'dangerously dedicated'. After an install using a 4.4Gig root, and an > 80meg swap, (leaving 20megs un-partitioned at the end of the drive), the > system will not boot. If I boot off of the installation floppies, I can > mount/view the files on the drive. This leaves me thinking it's got to > have something to do with FreeBSD's MBR. This is a FAQ; you have a geometry mismatch. Due to a bug in the Mylex driver, you have to set the Mylex "BIOS geometry" to the 2GB mode, then make sure that sysinstall correctly picks up the */128/32 geometry (it may be confused if you have other junk on the drive). I've fixed this in an updated version of the driver, but I haven't had time (or recently, the hardware) to test it properly. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 22:57:47 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 22:57:45 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from badpenguin.linux.it (unknown [213.45.113.111]) by hub.freebsd.org (Postfix) with ESMTP id 2CD4E37B400; Thu, 4 Jan 2001 22:57:43 -0800 (PST) Received: by badpenguin.linux.it (Postfix, from userid 1003) id 406881FCE9; Fri, 5 Jan 2001 05:13:29 +0000 (Local time zone must be set--see zic manual page) Date: Thu, 4 Jan 2001 23:13:29 -0600 From: AGX To: freebsd-hackers@freebsd.org Cc: asami@freebsd.org Subject: RFC: a CUI controlpanel for FreeBSD Message-ID: <20010104231329.A3555@linux.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i X-Disclaimer: Please visit http://www.badpenguin.org/ X-Operating-System: Bad Penguin GNU/Linux 0.9.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >1.3.3. The FreeBSD Development Model >Contributed by Satoshi Asami . >The development of FreeBSD is a very open and flexible process, >FreeBSD being literally built from the >contributions of hundreds of people around the world, as can be >seen from our list of contributors. We >are constantly on the lookout for new developers and ideas, and >those interested in becoming more >closely involved with the project need simply contact us at the >FreeBSD technical discussions mailing >list . Well, i checked out /etc/rc and /etc/rc.conf i would like to port my controlpanel from GNU/Linux to FreeBSD is this possibile? I did developed a lot of script to configure a lot of system settings but in GNU/Linux you have 364376 different distributions that are all different, i tried to develop my own but seems that common system components like GNU libc change each 5 minutes and does not seems more stable. I toughta it would be a nice idea to port my work under FreeBSD because i feel it more stable and reliable then GNU/Linux what do you think about having an "additional" controlpanel to do system configuration (mouse,keyboard,network,X11,postfix,etc.) ??? I firstly developed everything using cdialog but them are very buggy togheter with somebody i did developed "libgringo" that is a generic library that interface both ncurses and Gtk (depending how you compiled it) and allow you to write script that can run both in console both in X-Window. I would like to know if you think that is usefull or not to do this job or if there are more urgents work to do upon the FreeBSD distribution/ installation process. I've wasted 4 years trying to create my personalized GNU/Linux distribution and i'm tired of to remake each time the same job. Thank you in advance, Antonio Gallo -- Ciao, AGX http://www.antoniogallo.it (o_ http://www.badpenguin.org "Bad Penguin" GNU/Linux //\ http://www.linux.it ILS CD V_/_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23: 8: 3 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:07:57 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 96DCD37B69D; Thu, 4 Jan 2001 23:07:53 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f057Jlt03498; Thu, 4 Jan 2001 23:19:47 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050719.f057Jlt03498@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gordon Tetlow Cc: nathan@vidican.com, questions@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason In-reply-to: Your message of "Wed, 03 Jan 2001 17:43:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 23:19:47 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a FAQ; you have a geometry mismatch. Make sure the BIOS on the card is set for 2GB mode, make sure sysinstall detects a */128/32 geometry. 8GB mode doesn't work (my fault, will be fixed once I get my lab set up and some free time). > I can add another data point for this. We are using FreeBSD 4.0 (I'll be > upgrading them one of these days) and had this exact same problem. My > solution was to make a floppy disk and stuff it in the drive. It did the 3 > phase boot loader and in the loader.rc I added set currdev=disk1s1a which > did the trick. I'm really interested in getting this working as these are > our mailservers that I'd rather not trust to having to boot from floppy > disks. > > -gordon > > On Tue, 2 Jan 2001, Nathan Vidican wrote: > > > Subject: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server > > will not recognize boot record for some reason > > > > Having problems booting; the system installs to the mylex system drive > > fine, but when I reboot, I get the FreeBSD boot MGR, and it only beeps > > when I press F1 for FreeBSD. If I install using a normal boot record, > > the system reports 'No operating system found'. I'm thinking it may be > > an issue with the Mylex card, but I don't know for sure if the system's > > bios could cause this either. I cannot attempt to install the mylex card > > in another machine; as the drives attached to it are in a hot-swap > > carriage which is part of the system's chassis. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:21:52 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:21:49 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 9F03137B400 for ; Thu, 4 Jan 2001 23:21:49 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f057YSt03677; Thu, 4 Jan 2001 23:34:29 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050734.f057YSt03677@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew C. Forman" Cc: freebsd-hackers@freebsd.org Subject: Re: Allocating an IRQ on PCI In-reply-to: Your message of "Thu, 04 Jan 2001 15:59:57 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 23:34:28 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I want to allocate an IRQ for a PCI device driver. Normally this is easy > enough, since the BIOS would reserve it for me, then I would just have to > bus_alloc_resource and not even care which IRQ line it's using. This is how it works in -current. > Thing is, here the BIOS hasn't allocated an IRQ, so I'll need to > bus_set_resource in my probe to get one. To complicate matters, the > device's interrupt generator is pretty flexible, and can generate an > interrupt on (almost) any IRQ line. I have to tell it which IRQ to use > when I know which one has been allocated. Er, no, PCI interrupts don't work like that. A PCI device has four interrupt pins (A-D) which are routed in an opaque fashion to up to four different interrupt lines. You can (sometimes) tell the device which pin to generate an interrupt on, but it will normally tell *you*. > 1. Hardwire it, by using bus_set_resource with a specific IRQ. This isn't > nice, as it'll fail if someone else's setup is already using the one I > pick (or some other device attach will fail later on). This is guarateed to fail most of the time. > 2. Find out what IRQs are free and set and allocate one of those. This is > nicer than 1), but then if some poor device attach later on in boot was > expecting to use that IRQ, it'll break. This is also guaranteed to fail most of the time, as it doesn't matter which interrupts are "free" (you may actually be routed to an interrupt that's already in use somewhere else). > Does anyone know of a sensible & portable way around this? Perhaps IRQ > sharing could save me in some way... Look at the PCI interrupt routing code I committed to -current. Backporting it to -stable should be pretty simple (it will get harder as the code diverges more). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:35:15 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:35:12 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 6964237B400 for ; Thu, 4 Jan 2001 23:35:09 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id JAA16308; Fri, 5 Jan 2001 09:33:28 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 16189; Fri Jan 5 09:32:24 2001 Sender: gram@citadel.cequrux.com Message-ID: <3A556040.6B9163BB@cequrux.com> Date: Fri, 05 Jan 2001 07:48:48 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? References: <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > APM is standard. Except when it is broken in some brain damaged ways. > > However, you likely have your apm device disabled in your kernel and > all you need to do is enable it. > Nope - as I said, I added log messages to apm.c to log the BIOS probe and they log a failure (I have "device apm0" in my config file). gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:45:12 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:45:10 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Mail6.sc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 5181E37B404 for ; Thu, 4 Jan 2001 23:45:10 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by Mail6.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 5 Jan 2001 02:44:01 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f057iaV02728; Fri, 5 Jan 2001 02:44:36 -0500 (EST) (envelope-from dmaddox) Date: Fri, 5 Jan 2001 02:44:36 -0500 From: "Donald J . Maddox" To: Graham Wheeler Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? Message-ID: <20010105024436.A2700@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: Graham Wheeler , Warner Losh , hackers@FreeBSD.ORG References: <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> <3A556040.6B9163BB@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A556040.6B9163BB@cequrux.com>; from gram@cequrux.com on Fri, Jan 05, 2001 at 07:48:48AM +0200 Return-Receipt-To: dmaddox@sc.rr.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, I thought that APM was APM, but the apm device does nothing on my desktop with power management hardware... That is, things like 'shutdown -p now' don't work, both 'apm' and 'apmd' just return 'device not configured', etc. Interestingly, at least 'shutdown -p' does work with ACPI anyway :) Of course, maybe I'm just misunder- standing the whole thing anyway... Is power management hardware == APM? On Fri, Jan 05, 2001 at 07:48:48AM +0200, Graham Wheeler wrote: > Warner Losh wrote: > > > > APM is standard. Except when it is broken in some brain damaged ways. > > > > However, you likely have your apm device disabled in your kernel and > > all you need to do is enable it. > > > > Nope - as I said, I added log messages to apm.c to log the BIOS probe > and they log a failure (I have "device apm0" in my config file). > > gram > > -- > Dr Graham Wheeler E-mail: gram@cequrux.com > Director, Research and Development WWW: http://www.cequrux.com > CEQURUX Technologies Phone: +27(21)423-6065 > Firewalls/VPN Specialists Fax: +27(21)424-3656 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:45:48 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:45:46 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 4943937B402 for ; Thu, 4 Jan 2001 23:45:46 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f057vbt03988; Thu, 4 Jan 2001 23:57:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050757.f057vbt03988@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Graham Wheeler Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? In-reply-to: Your message of "Fri, 05 Jan 2001 07:48:48 +0200." <3A556040.6B9163BB@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 23:57:37 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Warner Losh wrote: > > > > APM is standard. Except when it is broken in some brain damaged ways. > > > > However, you likely have your apm device disabled in your kernel and > > all you need to do is enable it. > > > > Nope - as I said, I added log messages to apm.c to log the BIOS probe > and they log a failure (I have "device apm0" in my config file). How new is this laptop? It may be ACPI-only. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:53: 8 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:53:06 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 454FC37B400 for ; Thu, 4 Jan 2001 23:53:04 -0800 (PST) Received: (qmail 10969 invoked by uid 1000); 5 Jan 2001 07:51:43 -0000 Date: Fri, 5 Jan 2001 09:51:42 +0200 From: Peter Pentchev To: Graham Wheeler Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? Message-ID: <20010105095142.A10329@ringworld.oblivion.bg> Mail-Followup-To: Graham Wheeler , Warner Losh , hackers@FreeBSD.ORG References: <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> <3A556040.6B9163BB@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A556040.6B9163BB@cequrux.com>; from gram@cequrux.com on Fri, Jan 05, 2001 at 07:48:48AM +0200 Sender: roam@ringworld.nanolink.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 07:48:48AM +0200, Graham Wheeler wrote: > Warner Losh wrote: > > > > APM is standard. Except when it is broken in some brain damaged ways. > > > > However, you likely have your apm device disabled in your kernel and > > all you need to do is enable it. > > > > Nope - as I said, I added log messages to apm.c to log the BIOS probe > and they log a failure (I have "device apm0" in my config file). I think I've heard rumors of some BIOS's only supporting APM in real mode; and also rumors that this was the reason for Windows sometimes shutting down so slowly - it has to do a switch to real mode to make the APM poweroff calls. Feel free to correct me if I've heard wrong :) I *know* APM in 4.2-stable did not and does not work on my laptop (some kind of Asus). The ACPI from -current worked fine once when I tested it, but I had to go back to -stable for various reasons, and now I've already gotten used to turning it off by hand after the shutdown command. (Note: no bad feelings here, if it's the BIOS's fault, there's nothing the FreeBSD developers can do about it; and no, I would not want anyone to add mode switching code to FreeBSD solely for shutdown purposes :) G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 4 23:55:35 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 4 23:55:33 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 6119E37B400; Thu, 4 Jan 2001 23:55:27 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id JAA19207; Fri, 5 Jan 2001 09:55:20 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 19112; Fri Jan 5 09:55:14 2001 Sender: gram@citadel.cequrux.com Message-ID: <3A55659B.8CDB1EF@cequrux.com> Date: Fri, 05 Jan 2001 08:11:39 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Warner Losh , hackers@freebsd.org Subject: Re: Just how standard is APM? References: <200101050757.f057vbt03988@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > How new is this laptop? It may be ACPI-only. I believe it is quite new ("designed for Windows Me"). I have to admit my ignorance - I've never heard of ACPI. -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 0:10:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 00:10:14 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 1A6A737B69D for ; Fri, 5 Jan 2001 00:10:14 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f058Mrt04256; Fri, 5 Jan 2001 00:22:53 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050822.f058Mrt04256@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Graham Wheeler Cc: hackers@freebsd.org Subject: Re: Just how standard is APM? In-reply-to: Your message of "Fri, 05 Jan 2001 08:11:39 +0200." <3A55659B.8CDB1EF@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jan 2001 00:22:53 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > How new is this laptop? It may be ACPI-only. > > I believe it is quite new ("designed for Windows Me"). It's probably ACPI-only; welcome to FreeBSD-current. 8) > I have to admit my ignorance - I've never heard of ACPI. ACPI is the successor to APM, as well as trying to tie up a lot of loose ends in other parts of the system. We're working on support for it (with a boatload of help from Intel), but it's not quite there yet. Don't ask about backporting. Please. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 0:20:18 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 00:20:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1283F37B402 for ; Fri, 5 Jan 2001 00:20:16 -0800 (PST) Received: from newsguy.com (p44-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.109]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id RAA08754; Fri, 5 Jan 2001 17:19:18 +0900 (JST) Message-ID: <3A5582FE.767A617D@newsguy.com> Date: Fri, 05 Jan 2001 17:17:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: dmaddox@sc.rr.com Cc: Graham Wheeler , Warner Losh , hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? References: <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> <3A556040.6B9163BB@cequrux.com> <20010105024436.A2700@cae88-102-101.sc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Donald J . Maddox" wrote: > > Yeah, I thought that APM was APM, but the apm device does nothing > on my desktop with power management hardware... That is, things like > 'shutdown -p now' don't work, both 'apm' and 'apmd' just return > 'device not configured', etc. Interestingly, at least 'shutdown -p' > does work with ACPI anyway :) Of course, maybe I'm just misunder- > standing the whole thing anyway... Is power management hardware > == APM? If this is still about the Presario laptop, APM works (or did up to november) on the Compaq Presario 1621. Note the apm and acpi can't be used together in the same kernel. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 0:29:40 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 00:29:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 7B62E37B400 for ; Fri, 5 Jan 2001 00:29:35 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id KAA23732; Fri, 5 Jan 2001 10:29:13 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 23600; Fri Jan 5 10:28:02 2001 Sender: gram@citadel.cequrux.com Message-ID: <3A556D4C.44B553C0@cequrux.com> Date: Fri, 05 Jan 2001 08:44:28 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: freebsd-hackers@freebsd.org Subject: Re: Just how standard is APM? References: <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> <3A556040.6B9163BB@cequrux.com> <20010105024436.A2700@cae88-102-101.sc.rr.com> <3A5582FE.767A617D@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > If this is still about the Presario laptop, APM works (or did up to > november) on the Compaq Presario 1621. Note the apm and acpi can't be > used together in the same kernel. It's a 1700; previously I had a 1600 which worked better with everything (the VIA sound was supported, the APM BIOS worked, etc). It had a flaky touchpad, so I exchanged it, and took a 1700 because I wanted the CD-RW drive and lighter weight - but now I have lots of unsupported hardware (Conexant LANtastic Ethernet/modem, ESS1988 Allegro sound, and, it seems, ACPI - which is unsupported in -stable, I gather). Fortunately I have a 3Com PCMCIA EtherNIC, so I have enough working to make it quite usable with FreeBSD anyway. -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 0:48:23 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 00:48:21 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mb2i0.ns.pitt.edu (mb2i0.ns.pitt.edu [136.142.186.36]) by hub.freebsd.org (Postfix) with ESMTP id A02DC37B400 for ; Fri, 5 Jan 2001 00:48:21 -0800 (PST) Received: from pitt.edu ("port 2107"@[136.142.22.237]) by pitt.edu (PMDF V5.2-32 #41462) with ESMTP id <01JYJ8OVTKO2005ZPP@mb2i0.ns.pitt.edu> for freebsd-hackers@FreeBSD.ORG; Fri, 5 Jan 2001 03:48:19 EST Date: Fri, 05 Jan 2001 03:58:25 -0500 From: "Pedro F. Giffuni" Subject: Re: RFC: a CUI controlpanel for FreeBSD To: AGX Cc: freebsd-hackers@FreeBSD.ORG Message-id: <3A558CB1.7797A47A@pitt.edu> Organization: University of Pittsburgh MIME-version: 1.0 X-Mailer: Mozilla 4.76 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en,pdf,es-CO References: <20010104231329.A3555@linux.it> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AGX wrote: Antonio, you are welcome to contribute to FreeBSD. > > I would like to know if you think that is usefull or not to do this > job or if there are more urgents work to do upon the FreeBSD distribution/ > installation process. I've wasted 4 years trying to create my personalized > GNU/Linux distribution and i'm tired of to remake each time the same job. > FWIW, this all reminds me of FreeBSD's own project: http://people.FreeBSD.org/~alex/libh/ ciao, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 0:52:58 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 00:52:56 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 1F2F937B402 for ; Fri, 5 Jan 2001 00:52:53 -0800 (PST) Received: (qmail 60252 invoked by uid 1003); 5 Jan 2001 08:52:47 -0000 Date: Fri, 5 Jan 2001 10:52:47 +0200 From: Neil Blakey-Milner To: AGX Cc: freebsd-hackers@freebsd.org, asami@freebsd.org Subject: Re: RFC: a CUI controlpanel for FreeBSD Message-ID: <20010105105247.A57805@mithrandr.moria.org> References: <20010104231329.A3555@linux.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010104231329.A3555@linux.it>; from agx@linux.it on Thu, Jan 04, 2001 at 11:13:29PM -0600 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: nbm@rucus.ru.ac.za Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2001-01-04 (23:13), AGX wrote: > I firstly developed everything using cdialog but them are very buggy > togheter with somebody i did developed "libgringo" that is a generic > library that interface both ncurses and Gtk (depending how you > compiled it) and allow you to write script that can run both in console > both in X-Window. Where can I look at this stuff? What scripting language do you use when you say 'write scripts'? > I would like to know if you think that is usefull or not to do this > job or if there are more urgents work to do upon the FreeBSD distribution/ > installation process. I've wasted 4 years trying to create my personalized > GNU/Linux distribution and i'm tired of to remake each time the same job. There're lots of things you can do on FreeBSD, but it's generally best to do the stuff you most enjoy and/or are best at. If you like writing documentation, there's the documentation project; if you like general hacking, generally hack, and if you like in-depth kernel stuff, I'm sure the kernel people will be happy for more of themselves. (: Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 6: 4:41 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 06:04:38 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id A24F137B400 for ; Fri, 5 Jan 2001 06:04:37 -0800 (PST) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 14EXTs-000Egu-0Y; Fri, 5 Jan 2001 14:04:32 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.1/8.8.8) with ESMTP id f05E4Gv01086; Fri, 5 Jan 2001 14:04:16 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 5 Jan 2001 14:04:15 +0000 (GMT) From: Doug Rabson To: Doug White Cc: Zhiui Zhang , Subject: Re: kernel debugging suggestion needed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001, Doug White wrote: > On Tue, 2 Jan 2001, Zhiui Zhang wrote: > > > > > I have written a KLD and am debugging it. The program often hangs after > > runs for a while (I guess it enters into some dead loop). Is there a way > > to attach to the process and somehow find out which code it is executing > > (with remote debugging or ddb)? > > kld debugging is a bit tricky. Take a look at the debugging macros and > bits that Greg Lehey put together for vinum for a starting point. You have > to calculate the appropriate offset to get to the KLD code in gdb. Not anymore. You can use GDB's "sharelibrary" command to read the symbols of all loaded KLDs. You only need to ensure that the exact same pathname works for both loading the KLD on the target machine and for loading the symbols on the machine running GDB. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 7:56:56 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 07:56:54 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 4EA7337B400; Fri, 5 Jan 2001 07:56:54 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 9AE343243; Fri, 5 Jan 2001 15:56:51 +0000 (GMT) Date: Fri, 5 Jan 2001 15:56:51 +0000 From: Josef Karthauser To: Mike Smith Cc: Graham Wheeler , Warner Losh , hackers@FreeBSD.ORG Subject: Re: Just how standard is APM? Message-ID: <20010105155651.C1835@tao.org.uk> References: <3A556040.6B9163BB@cequrux.com> <200101050757.f057vbt03988@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101050757.f057vbt03988@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Thu, Jan 04, 2001 at 11:57:37PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 11:57:37PM -0800, Mike Smith wrote: > > Warner Losh wrote: > > > > > > APM is standard. Except when it is broken in some brain damaged ways. > > > > > > However, you likely have your apm device disabled in your kernel and > > > all you need to do is enable it. > > > > > > > Nope - as I said, I added log messages to apm.c to log the BIOS probe > > and they log a failure (I have "device apm0" in my config file). > > How new is this laptop? It may be ACPI-only. Where are we at with ACPI? Does it do power management yet? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:31:15 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:31:12 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from jello.geekspace.com (jello.geekspace.com [63.175.99.14]) by hub.freebsd.org (Postfix) with SMTP id E623337B400 for ; Fri, 5 Jan 2001 09:31:11 -0800 (PST) Received: (qmail 3538 invoked by uid 1002); 5 Jan 2001 17:34:02 -0000 Message-ID: <20010105173402.3537.qmail@jello.geekspace.com> References: <3A551ABD.DBC9BD5C@geekspace.com> <20010104171504.A15744@fw.wintelcom.net> In-Reply-To: <20010104171504.A15744@fw.wintelcom.net> From: "Joshua Rosen" To: Alfred Perlstein Cc: Chris Williams , freebsd-hackers@FreeBSD.ORG, rozzin@geekspace.com Subject: Re: Strange fwrite() behavior in a+ mode Date: Fri, 05 Jan 2001 17:34:02 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: rozzin@jello.geekspace.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > So in Linux, if you have a "a+" file, you can > 1) seek somewhere (mid file) > 2) read some data (not until EOF) > 3) after the read you are at EOF again? > > this doesn't sound really intuative. No, it doesn't sound intuitive; luckily, that isn't what happens;) The issue concerns where the position is after a write (and where ftell reports it as being). Under glibc on Linux, you can: 1) fseek somewhere (non-EOF) 2) fwrite some data 3) after the *write*, you are at EOF again (ftell reports this, and any attempted fread, at this point, will hit EOF. any fseek, after a write, using SEEK_CUR will seek relative to EOF, also) I guess that the idea is, `bytes are read/written starting at the current position in the file', and, in order to do this in a system which always writes after EOF in append-mode, the current position must be changed before writing.... my findings, under FreeBSD 4.2-STABLE, are 1) fseek somewhere (non-EOF, say 4 in a 50-byte-long file) 2) fwrite some data (say 3 bytes) 3) after the fwrite, ftell will report N + the last value pass'd to fseek (using our example numbers: 7), and fseek with SEEK_CUR will seek relative to that point, but fread will immediately hit EOF, and a ftell (or feof) after an attempted read will indicate that the position *is* EOF. Chris' findings (I believe) are that, under FreeBSD 4.2-STABLE, if you use fread before fwrite (say, step `1.1'), it acts just like it does with glibc/Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:31:39 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:31:37 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C6B537B402 for ; Fri, 5 Jan 2001 09:31:36 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id MAA34926; Fri, 5 Jan 2001 12:37:25 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010105123746.02e18810@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 05 Jan 2001 12:38:07 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: if_fxp driver??? Cc: dg@root.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has the issue with the new rev intel parts been resolved yet? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:35:36 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:35:35 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 9671E37B400 for ; Fri, 5 Jan 2001 09:35:34 -0800 (PST) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id RAA19478 for freebsd-hackers@freebsd.org; Fri, 5 Jan 2001 17:35:33 GMT (envelope-from simond) Date: Fri, 5 Jan 2001 17:35:33 +0000 From: simond@irrelevant.org To: freebsd-hackers@freebsd.org Subject: IEEE 1394/Firewire Message-ID: <20010105173533.C6707@irrelevant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: simond@bumper.jellybaby.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know if any work is being done on this? Especially the TCP/IP over firewire (rfc2734), which would make it nice and easy to network up my vaio with my desktop PC :) -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:47:25 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:47:23 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D9D7F37B402 for ; Fri, 5 Jan 2001 09:47:22 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f05HlLS10067; Fri, 5 Jan 2001 09:47:21 -0800 (PST) Date: Fri, 5 Jan 2001 09:47:21 -0800 From: Alfred Perlstein To: Joshua Rosen Cc: Chris Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: Strange fwrite() behavior in a+ mode Message-ID: <20010105094721.B15744@fw.wintelcom.net> References: <3A551ABD.DBC9BD5C@geekspace.com> <20010104171504.A15744@fw.wintelcom.net> <20010105173402.3537.qmail@jello.geekspace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010105173402.3537.qmail@jello.geekspace.com>; from rozzin@geekspace.com on Fri, Jan 05, 2001 at 05:34:02PM +0000 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joshua Rosen [010105 09:31] wrote: > > Alfred Perlstein writes: > > > So in Linux, if you have a "a+" file, you can > > 1) seek somewhere (mid file) > > 2) read some data (not until EOF) > > 3) after the read you are at EOF again? > > > > this doesn't sound really intuative. > > No, it doesn't sound intuitive; luckily, that isn't what happens;) > The issue concerns where the position is after a write (and where ftell > reports it as being). > > Under glibc on Linux, you can: > 1) fseek somewhere (non-EOF) > 2) fwrite some data > 3) after the *write*, you are at EOF again (ftell reports this, and any > attempted fread, at this point, will hit EOF. any fseek, after a write, > using SEEK_CUR will seek relative to EOF, also) > > I guess that the idea is, `bytes are read/written starting at the current > position in the file', and, in order to do this in a system which always > writes after EOF in append-mode, the current position must be changed > before writing.... > > my findings, under FreeBSD 4.2-STABLE, are > 1) fseek somewhere (non-EOF, say 4 in a 50-byte-long file) > 2) fwrite some data (say 3 bytes) > 3) after the fwrite, ftell will report N + the last value pass'd to fseek > (using our example numbers: 7), and fseek with SEEK_CUR will seek relative > to that point, but fread will immediately hit EOF, and a ftell (or feof) > after an attempted read will indicate that the position *is* EOF. > > Chris' findings (I believe) are that, under FreeBSD 4.2-STABLE, if you use > fread before fwrite (say, step `1.1'), it acts just like it does with > glibc/Linux. Can you do a bit more research and let me know if this happens when using open/read/write/lseek as well? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:52:44 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:52:41 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D5A2237B400 for ; Fri, 5 Jan 2001 09:52:40 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f05HqR603142; Fri, 5 Jan 2001 12:52:27 -0500 (EST) (envelope-from arr@watson.org) Date: Fri, 5 Jan 2001 12:52:26 -0500 (EST) From: "Andrew R. Reiter" To: simond@irrelevant.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IEEE 1394/Firewire In-Reply-To: <20010105173533.C6707@irrelevant.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Plz search -hackers On Fri, 5 Jan 2001 simond@irrelevant.org wrote: > Does anyone know if any work is being done on this? Especially the TCP/IP > over firewire (rfc2734), which would make it nice and easy to network up > my vaio with my desktop PC :) > > -- > Simon Dick simond@irrelevant.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:56: 9 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:56:04 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 406B937B402 for ; Fri, 5 Jan 2001 09:56:02 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f05Htpb55318; Fri, 5 Jan 2001 10:55:51 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101051755.f05Htpb55318@harmony.village.org> To: Graham Wheeler Subject: Re: Just how standard is APM? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 05 Jan 2001 07:48:48 +0200." <3A556040.6B9163BB@cequrux.com> References: <3A556040.6B9163BB@cequrux.com> <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> Date: Fri, 05 Jan 2001 10:55:51 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A556040.6B9163BB@cequrux.com> Graham Wheeler writes: : Nope - as I said, I added log messages to apm.c to log the BIOS probe : and they log a failure (I have "device apm0" in my config file). What's the failure mode? Is it enabled in the BIOS (I assume it is, otherwise it wouldn't work in 'Doz). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 9:57:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 09:57:14 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 507C737B402 for ; Fri, 5 Jan 2001 09:57:13 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f05Hv2b55344; Fri, 5 Jan 2001 10:57:02 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101051757.f05Hv2b55344@harmony.village.org> To: dmaddox@sc.rr.com Subject: Re: Just how standard is APM? Cc: Graham Wheeler , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 05 Jan 2001 02:44:36 EST." <20010105024436.A2700@cae88-102-101.sc.rr.com> References: <20010105024436.A2700@cae88-102-101.sc.rr.com> <3A545615.3597BCF3@cequrux.com> <200101042234.f04MYM147333@harmony.village.org> <3A556040.6B9163BB@cequrux.com> Date: Fri, 05 Jan 2001 10:57:02 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010105024436.A2700@cae88-102-101.sc.rr.com> "Donald J . Maddox" writes: : Yeah, I thought that APM was APM, but the apm device does nothing : on my desktop with power management hardware... That is, things like : 'shutdown -p now' don't work, both 'apm' and 'apmd' just return : 'device not configured', etc. Interestingly, at least 'shutdown -p' : does work with ACPI anyway :) Of course, maybe I'm just misunder- : standing the whole thing anyway... Is power management hardware : == APM? No. APM is a BIOS interface. Many BIOSes that have ACPI have legacy APM support. Some work, some don't. Windows (98 and newer) uses ACPI in preference to APM, so the testing that APM mode gets is usually meager at best. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 11: 7: 7 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 11:07:02 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E953C37B402; Fri, 5 Jan 2001 11:06:59 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f05J5gG86990; Fri, 5 Jan 2001 11:05:43 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010105155651.C1835@tao.org.uk> Date: Fri, 05 Jan 2001 11:06:51 -0800 (PST) From: John Baldwin To: Josef Karthauser Subject: Re: Just how standard is APM? Cc: hackers@FreeBSD.org, Warner Losh , Graham Wheeler , Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-01 Josef Karthauser wrote: > On Thu, Jan 04, 2001 at 11:57:37PM -0800, Mike Smith wrote: >> > Warner Losh wrote: >> > > >> > > APM is standard. Except when it is broken in some brain damaged ways. >> > > >> > > However, you likely have your apm device disabled in your kernel and >> > > all you need to do is enable it. >> > > >> > >> > Nope - as I said, I added log messages to apm.c to log the BIOS probe >> > and they log a failure (I have "device apm0" in my config file). >> >> How new is this laptop? It may be ACPI-only. > > Where are we at with ACPI? Does it do power management yet? Yes. For the Inspiron that you have you have to hack around a bit to get it to not hang during boot (and battery status doesn't work as a result I think), but suspend/resume on lid close work, the power button works, shutdown -p, etc. > Joe -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 11:12:10 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 11:12:08 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 49E3037B400 for ; Fri, 5 Jan 2001 11:12:07 -0800 (PST) Received: (qmail 20371 invoked by uid 3001); 5 Jan 2001 19:12:04 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 5 Jan 2001 19:12:04 -0000 Received: (qmail 16301 invoked by uid 1001); 5 Jan 2001 19:12:04 -0000 Date: Fri, 5 Jan 2001 14:12:04 -0500 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: open PR WRT syslogd vs. serial consoles Message-ID: <20010105141204.F14544@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: reichert@natto.numachi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm chasing down a syslogd problem on a 3.4-R box, only to discover that I'm being bit (still!) by a PR I submitted two years ago: I'm responsible for a wad of machines hanging off of a terminal server. - I wanted syslog messages reported to the console, for revealing critical errors. - Due to cabling and the terminal server itself, using Big Digi hardware, I need to have getty running off of cuaa0, not ttyd0. Apparently, in three versions of FreeBSD, this is _still_ a problem. Does anyone have any insight on this? -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 11:42:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 11:42:41 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C240F37B400 for ; Fri, 5 Jan 2001 11:42:40 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA03931; Fri, 5 Jan 2001 11:42:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f05JgcX01569; Fri, 5 Jan 2001 11:42:38 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Jan 2001 11:42:38 -0800 From: "David O'Brien" To: Doug White Cc: Rafael Barrero , hackers@FreeBSD.ORG Subject: Re: BSD dlopen and such Message-ID: <20010105114237.A1548@dragon.nuxi.com> Reply-To: hackers@FreeBSD.ORG References: <20010102152714.A3189@lokigames.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 dwhite@resnet.uoregon.edu on Thu, Jan 04, 2001 at 10:19:56AM -0800 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: obrien@NUXI.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 10:19:56AM -0800, Doug White wrote: > > 1) Can a native binary dlopen a Linux ELF GL, yes or no? > > No. The linux compatbility is through the image activator. The syscalls > have to be translated, otherwise if you were running as root and loaded a > linux lib into a freebsd binary, then that lib called fcntl(), your system > would reboot :) Acutally you should have said "YES", with a limitation that the Linux object cannot make syscalls. On the Alpha we use a Linux library with the Compaq ccc comiler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 13:18:38 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 13:18:33 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 667BD37B698 for ; Fri, 5 Jan 2001 13:18:33 -0800 (PST) Received: (qmail 1686 invoked by uid 1078); 5 Jan 2001 21:18:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Jan 2001 21:18:44 -0000 Date: Fri, 5 Jan 2001 13:18:44 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Mike Smith Cc: , , Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason In-Reply-To: <200101050719.f057Jlt03498@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Mike Smith wrote: > This is a FAQ; you have a geometry mismatch. > > Make sure the BIOS on the card is set for 2GB mode, make sure sysinstall > detects a */128/32 geometry. 8GB mode doesn't work (my fault, will be > fixed once I get my lab set up and some free time). Hmm, I just installed it using 8GB mode (4.2-RELEASE) and it booted no problem. I then tried 4.0-RELEASE and it worked. In my previous experience it hadn't. I'm going to revisit the boxes that don't boot and play with them a bit. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 14:13:57 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 14:13:55 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 3A61A37B402 for ; Fri, 5 Jan 2001 14:13:55 -0800 (PST) Received: from sv.Go2France.com (sv.meiway.com [212.73.210.79]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 157816A91C for ; Fri, 5 Jan 2001 23:13:53 +0100 (CET) Message-Id: <5.0.2.1.0.20010105230853.0477d910@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Fri, 05 Jan 2001 23:11:52 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: encrypt h/w for FreeBSD? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, got no answer in -questions. Just my quarterly check to see whether there's support coming up for hardware assisted IPsec, SSL, whatever? In addition to SSL on web servers, we'd recently have found some need like to run TLS for SMTP and postfix. Thanks, Len http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 14:45:56 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 14:45:53 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 8A45F37B400 for ; Fri, 5 Jan 2001 14:45:52 -0800 (PST) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA14385; Fri, 5 Jan 2001 14:45:36 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A564E90.A49E1BE1@gorean.org> Date: Fri, 05 Jan 2001 14:45:36 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: freebsd-hackers@FreeBSD.org Subject: Re: OT: silence as an answer? (was: how to test out cron.c changes?) References: <200011191816.KAA81473@freefall.freebsd.org> <20001119214008.Z27042@speedy.gsinet> <20001120143658.B4415@netmode.ece.ntua.gr> <20001120193326.C27042@speedy.gsinet> <20001205225656.Z27042@speedy.gsinet> <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102125247.U253@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > > [ this message is no personal affront against you, Doug, but an > expression of what feeling this kind of behaviour causes for > those who want to share and find themselves ignored ] Actually, I wouldn't care if it were, but thanks for the clarification. FYI, you will get a faster response if you cc: the person who wrote you. I'm currently behind on list mail. > On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote: > > Gerhard Sittig wrote: > > > > > > [ ... reminder after two weeks of silence ... ] > > > > Two weeks of silence is generally enough to let you know that > > no one is interested in this modification. If someone was, > > they'd generally have said something by now. > > Well, I don't come to the same conclusion here as you do and I'm > not so sure about it as you are. :) Silence as I see it is just > a sign for "nobody answered", without a reason to see why. Sometimes that's true. I think that my point could have been better stated as, "No one was excited enough about your proposal to take further action on it." This may be because no one wants it, or it may be because no one has had time to deal with it... or lots of other reasons. The fact is however, that things that people really ARE interested in get done. So, silence can be, and usually is rejection, even if that's not really the answer you wanted. > BTW is rejection much more the kind of reaction I had expected in > the case you describe (nobody wants it). This would have been at > least *some* reaction. The problem is that no one person can state conclusively that the project doesn't want something. One person CAN step in and make something happen, so acceptance is easy, whereas rejection is almost always a case of slow death by apathy. > Getting ignored is definitely a fine way > of discouraging future contributions. You may find this hard to believe, but I sympathize with your plight. I was there for years. That's why I tend to make the kinds of replies I did in this case so that at least the person will have some assurance that their suggestion was seen, and considered. > Some "we don't like the > approach, since ..." or a simple "Nope" or even a serious > "PLONK!" would have been great and as much appreciated as an > "yes, we like it"! It had saved time and work for _everyone_ > involved (me as being the originator as well as those I had to > annoy repeatedly when they could have stopped me right in the > beginning). As above, this just doesn't happen very often, unless it's a truly horrible idea. This is the nature of working on this kind of project. You will simply have to develop a thicker skin if you are going to survive in this environment. > > Speaking only for myself, I don't think your proposed changes > > are a good idea, which is why I refrained from offering any > > suggestions on how you can test them. You stated in another post that you wished I had elaborated more. I was in a hurry when I wrote that post, so here are more details. While this is, as you say, "an eternal problem," it is not a problem entirely without remedy. The proper solution is simply to avoid scheduling mission/time critical events during the DST change period for your time zone. Without improperly revealing sources, I can say that I did a lot of research on this topic in a past life, and it is by no means clear that your proposed solution is the best one. Consider the following. We are in the spring and DST is "springing forward" at 2am. We have a job scheduled at 2:15 that takes one hour to run. There is another job scheduled at 3:20 that ABSOLUTELY POSITIVELY cannot run unless the first job finishes. Aside from the fact that this is bad design, how should cron handle this situation? You can (and probably should) respond that this is not cron's responsibility, and come up with all kinds of ways to ameliorate this situation. My response will then be that if you can "fix" this situation without "fixing" cron, then cron doesn't really need to be "fixed." With very little imagination you could easily come up with other situations where your proposed changes will cause more harm than good. On the other hand, the "damage" that cron is doing in these situations can easily be repaired by proper system design. Therefore your changes should not be incorporated. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 15:10:38 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 15:10:36 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 8898B37B400 for ; Fri, 5 Jan 2001 15:10:36 -0800 (PST) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Fri, 5 Jan 2001 16:10:35 -0700 Message-ID: <5FE9B713CCCDD311A03400508B8B3013054E3D07@bdr-xcln.is.matchlogic.com> From: Charles Randall To: freebsd-hackers@freebsd.org Subject: RE: encrypt h/w for FreeBSD? Date: Fri, 5 Jan 2001 16:10:34 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nCipher's nFast card supports FreeBSD 3.3 and 3.4. http://www.ncipher.com/products/nfast_specs.html -Charles -----Original Message----- From: Len Conrad [mailto:LConrad@Go2France.com] Sent: Friday, January 05, 2001 3:12 PM To: freebsd-hackers@freebsd.org Subject: encrypt h/w for FreeBSD? Sorry, got no answer in -questions. Just my quarterly check to see whether there's support coming up for hardware assisted IPsec, SSL, whatever? In addition to SSL on web servers, we'd recently have found some need like to run TLS for SMTP and postfix. Thanks, Len http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 17: 8:24 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 17:08:22 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D7ABE37B400 for ; Fri, 5 Jan 2001 17:08:18 -0800 (PST) Received: from cain.gsoft.com.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id LAA30203; Sat, 6 Jan 2001 11:38:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5FE9B713CCCDD311A03400508B8B3013054E3D07@bdr-xcln.is.matchlogic.com> Date: Sat, 06 Jan 2001 11:38:11 +1030 (CST) Sender: darius@cain.gsoft.com.au From: "Daniel O'Connor" To: Charles Randall Subject: RE: encrypt h/w for FreeBSD? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-01 Charles Randall wrote: > nCipher's nFast card supports FreeBSD 3.3 and 3.4. > > http://www.ncipher.com/products/nfast_specs.html I think Mike Smith is 'sort of' working on support for HW crypto cards.. No idea how far he has got. --- 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-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 5 22: 6:42 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 5 22:06:40 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.kobe-u.ac.jp (mailgate.kobe-u.ac.jp [133.30.228.40]) by hub.freebsd.org (Postfix) with ESMTP id 6BFD137B400 for ; Fri, 5 Jan 2001 22:06:39 -0800 (PST) Received: from [133.30.168.118] ([133.30.168.118]) by mailgate.kobe-u.ac.jp (8.9.3+3.2W/3.7Wpl2/000412) with ESMTP id PAA04466 for ; Sat, 6 Jan 2001 15:06:38 +0900 (JST) Date: Sat, 6 Jan 2001 15:10:30 +0900 (JST) From: Rachmat Hidajat X-Sender: rachmat@okurayama.med.kobe-u.ac.jp To: freebsd-hackers@freebsd.org Subject: Diskless Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I want to try to boot the diskless system, so I compile nb8390.com with NE2000 support. But I got the following error during the process. Did I make a mistake? -------------------------------------------------------------------- # make Warning: Object directory not changed from original /usr/src/sys/i386/boot/netboot cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x90000 -DPCI -DPCI_VENDOR=0x10ec -DPCI_DEV ICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -DASK_BOOT -aout -nostdinc -I/usr/src/sys/ i386/boot/netboot/../../../../include -I/usr/src/sys/i386/boot/netboot/../../.. -I/usr/src/sys/i386/boot/netboot -DROMSIZE=16384 -static -o makerom /usr/src /sys/i386/boot/netboot/makerom.c ld: scrt0.o: No such file or directory *** Error code 1 Stop in /usr/src/sys/i386/boot/netboot. ------------------------------------------------------------------- PS: Please cc your response to my private address whenever possible. Regards, Rachmat Hidajat Kobe, JAPAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 3:31: 8 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 03:31:07 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 2F00037B400 for ; Sat, 6 Jan 2001 03:31:07 -0800 (PST) Received: from sv.Go2France.com (sv.meiway.com [212.73.210.79]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 0C4BB6A90A for ; Sat, 6 Jan 2001 12:31:06 +0100 (CET) Message-Id: <5.0.2.1.0.20010106122540.050d2150@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 06 Jan 2001 12:28:52 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: encrypt h/w for FreeBSD? re-post Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ( sorry to re-post but I didn't get my first post back in the normally extremely short echo times I experience with FreeBSD lists, and no other msgs from hackers since I posted, as if the list was down) Sorry, got no answer in -questions. Just my quarterly check to see whether there's support coming up for hardware assisted IPsec, SSL, whatever? In addition to SSL on web servers, we'd recently have found some need like to run TLS for SMTP and postfix. The mail volumes will benefit from hardware crypto. I really prefer to stay with Free, vs. Open. Thanks, Len http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 4:41:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 04:41:18 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id D029837B402 for ; Sat, 6 Jan 2001 04:41:01 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f06CeLY16173; Sat, 6 Jan 2001 14:40:33 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101061240.f06CeLY16173@gratis.grondar.za> To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: encrypt h/w for FreeBSD? re-post References: <5.0.2.1.0.20010106122540.050d2150@mail.Go2France.com> In-Reply-To: <5.0.2.1.0.20010106122540.050d2150@mail.Go2France.com> ; from Len Conrad "Sat, 06 Jan 2001 12:28:52 +0100." Date: Sat, 06 Jan 2001 14:40:03 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just my quarterly check to see whether there's support coming up for > hardware assisted IPsec, SSL, whatever? I have a card that does this, and I'm slowly working towards making it work. > In addition to SSL on web servers, we'd recently have found some need > like to run TLS for SMTP and postfix. The mail volumes will benefit > from hardware crypto. I really prefer to stay with Free, vs. Open. Quite. :-) Please don't ask anything more than your "quarterly query"; that way I won't have to lie to you. :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 12:28:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 12:28:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id AF5EF37B400 for ; Sat, 6 Jan 2001 12:28:16 -0800 (PST) Received: (qmail 15412 invoked by uid 1078); 6 Jan 2001 20:28:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Jan 2001 20:28:22 -0000 Date: Sat, 6 Jan 2001 12:28:22 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Frederik Meerwaldt Cc: Subject: Re: natd bug In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to get this exact same message, although my natd setup worked just fine. It was just filling up the logs. I then added -log_denied to the arguements for natd and it stopped spewing log messages. Here's what I run: /sbin/natd -unregistered_only -use_sockets -punch_fw 5050:10 -log_denied -n vx0 I don't know if this helps out your problem or not, but at least I don't get really annoying syslog messages every minute. -gordon On Thu, 30 Nov 2000, Frederik Meerwaldt wrote: > I was just looking why my natd doesnt work, when I discovered the > following bug (?): > > I compiled my kernel with IPDIVERT IPFIREWALL and > IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule: > ipfw add divert natd all from any to any via isp0 > Then I started natd (at boot time): > natd -unregistered_only -dynamic -n isp0 > But when a package arrives (doesn't matter from localhost or another > host), natd gives out a kernel message: > > Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission > denied) > > What does that mean? I started natd from my rc.local, so it runs as root > and it should have all permissions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 12:32: 1 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 12:31:58 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 590AA37B400; Sat, 6 Jan 2001 12:31:57 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f06KVo447875; Sat, 6 Jan 2001 21:31:50 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Sat, 6 Jan 2001 21:37:30 +0100 (CET) From: Martin Blapp To: freebsd-hackers@freebsd.org Cc: wpaul@freebsd.org Subject: Re: [PATCH available] TI-RPC and NetBSD's rpc.lockd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm making progress with the code and I have also a new diff available. http://www.attic.ch/patches/rpc.diff_01052001-05.tgz > Issues with the code: > > 1.) NETBSD sets in svc_tcp.c some LOCAL_CREDS which we don't have in our > src/sys/kern/uipc_usrreq.c. They have a FLAG which - if set - > automatically sends the credentials on AF_UNIX sockets connections > if we do a recvmsg(). We have to implement this to have rpcbind properly > working. AF_UNIX socket operations are broken at the moment, but > with compability-mode 'rpcbind -Li' rpcbind works. Not solved yet. Bill, can you help me with the code ? I tried to send first a scm.type of SCM_CREDS with sendmsg(), and to recieve the Creds after with recvmsg() but it does not work as expected. Can you help me to resolve this problem ? I'm I doing something completly wrong ? I'm often on IRC, you know me as 'mbr'. > > 2. Maybe it's related to 1., but unregistring the rpc-services does not > work at the moment. > not solved yet. > 3.) It breaks 'make world', some rpc based programms do not find the > symbol for a extern defined variable from rpcgen generated code. NetBSD > has the same code generated from rpcbind, so it has to be somewhere > defined. Can someone with a netbsd account look if they have the same > problem ? > > cc -O -pipe -I. -o rpc.statd file.o sm_inter_svc.o statd.o procs.o > -lrpcsvc > sm_inter_svc.o: In function `sm_prog_1': > sm_inter_svc.o(.text+0xb): undefined reference to `_rpcsvcdirty' Fixed. This was solved my looking a little bit closer to the NetBSd rpcgen code which was infact a old version and completly messed. We use at the moment the newest rpcgen code available and generate the better code than NetBSD does (Thread-Safe, some fixes for BSD) > > 4.) The threaded version of the libs may not work. As I have seen > it was untested by NetBSD people and I fixed some bugs myself. One thing > I'm not sure about the way I changed pthread_getspecific(key) in several > files. > > Some time ago this function has changed from > > void * pthread_getspecific(pthread_key_t key, void **value_ptr) to > void * pthread_getspecific(pthread_key_t key); > > And I wonder where the **value_ptr now is. Is this the right way to do > this ? > > value_ptr = (int*)pthread_getspecific(key); > Solved, there is a _pthread_getspecific which has old semantics. > 5.) The semantics of authdes_create() are not the same as in TI-RPC > code of Sun. Can someone look a little bit at this changes ? Fixed, I Imported the newest version of auth_des and it should work now. Made the code thread-safe. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 14:12:29 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 14:12:26 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0759937B400; Sat, 6 Jan 2001 14:12:26 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA28183; Sat, 6 Jan 2001 14:12:24 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 06 Jan 2001 14:12:24 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: KVM switch vs. FreeBSD psm driver Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize this is a well-known problem. Although there's much discussion about it in the mailing list archives, I couldn't find an actual solution. I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's much smarter than it really is. When I try to use the mouse through it with FreeBSD (-current from around Christmas, but I also had problems with -stable) it doesn't work right at all. It's got the same symptoms everybody else has reported: the cursor jumps around, and lots of "psmintr: out of sync" messages get logged. I found a posting in -hackers where Kazutaka YOKOTA said: > You can force FreeBSD to use the mouse as the standard PS/2 mouse by > specifying the flags 0x200 to the psm driver. This way, the mouse > should always work. But, you cannot use the wheel. However, setting that flag hasn't helped me at all. Here are the relevant parts of "/var/run/dmesg.boot" from a verbose boot-up: psm0: current command byte:0047 psm0: flags 0x200 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 255-ffffffff, 2 buttons psm0: config:00000200, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 The mouse itself is a no-name 2-button PS/2 mouse. It doesn't have a wheel or anything else "extra". It works fine when connected directly to the computer. I have also tried various combinations of flags 0x100 (NOCHECKSYNC) and 0x400 (NORESET) without any luck. The useless mouse behavior happens with moused and with XFree86 + no moused. It happens whether I specify the protocol as "ps/2" or as "auto". The KVM switch claims to have "Microsoft Intellimouse support and emulation." However, in the troubleshooting section of its manual it says you should make sure your driver is "either for a Standard PS/2 or Microsoft-compatible PS/2" mouse." I don't care about wheels, and I'm even willing to get by with only 2 buttons. I don't mind hacking up the psm driver if necessary. I just want the mouse to work with this switch. Any suggestions? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 14:26:56 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 14:26:54 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id D22AF37B402 for ; Sat, 6 Jan 2001 14:26:51 -0800 (PST) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.1/8.11.1) with ESMTP id f06MQY966928; Sat, 6 Jan 2001 17:26:34 -0500 (EST) (envelope-from jack@germanium.xtalwind.net) Date: Sat, 6 Jan 2001 17:26:34 -0500 (EST) From: jack To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: KVM switch vs. FreeBSD psm driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today John Polstra wrote: > The KVM switch claims to have "Microsoft Intellimouse support and > emulation." However, in the troubleshooting section of its manual it > says you should make sure your driver is "either for a Standard PS/2 > or Microsoft-compatible PS/2" mouse." I have a Brand X KVM which also claims Intellimouse support. I've found that if the switch is set to a machine when that machine boots all is well, if I boot a machine with a different one active on the KVM when I go to the one that was booted the mouse jumps, psm errors, etc. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 14:32:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 14:32:16 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E50B537B402 for ; Sat, 6 Jan 2001 14:32:15 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA28259; Sat, 6 Jan 2001 14:31:57 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f06MVuZ11595; Sat, 6 Jan 2001 14:31:56 -0800 (PST) (envelope-from jdp) Date: Sat, 6 Jan 2001 14:31:56 -0800 (PST) Message-Id: <200101062231.f06MVuZ11595@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Reply-To: hackers@freebsd.org Cc: jack@germanium.xtalwind.net Subject: Re: KVM switch vs. FreeBSD psm driver In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , jack wrote: > > I have a Brand X KVM which also claims Intellimouse support. > I've found that if the switch is set to a machine when that > machine boots all is well, if I boot a machine with a different > one active on the KVM when I go to the one that was booted the > mouse jumps, psm errors, etc. That doesn't seem to help in my case, unfortunately. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 14:58:17 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 14:58:15 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from apocalypse.cdsnet.net (apocalypse.cdsnet.net [63.163.68.5]) by hub.freebsd.org (Postfix) with ESMTP id A5D4F37B400 for ; Sat, 6 Jan 2001 14:58:14 -0800 (PST) Received: (from mrcpu@localhost) by apocalypse.cdsnet.net (8.11.1/8.11.1) id f06N17k17847 for hackers@freebsd.org; Sat, 6 Jan 2001 15:01:07 -0800 (PST) (envelope-from mrcpu) Date: Sat, 6 Jan 2001 15:01:07 -0800 From: Jaye Mathisen To: hackers@freebsd.org Subject: fsck problem on large vinum volume Message-ID: <20010106150106.X32287@apocalypse.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: mrcpu@apocalypse.cdsnet.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD newsfeed-inn2.meganews.com 4.2-STABLE FreeBSD 4.2-STABLE #2: Fri Jan 5 09:42:37 PST 2001 root@newsfeed-inn2.meganews.com:/n/FreeBSD/RELENG_4-2000-12-18/src/sys/compile/NEWSFEED-INN3 i386 I have a 930GB vinum volume newfs -v -i 4194304 /dev/vinum/v-spool went fine. However, I can't fsck it, I have to always use the alternate block. newsfeed-inn2# fsck -b 32 /dev/vinum/v-spool Alternate super block location: 32 ** /dev/vinum/v-spool ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 9 files, 257 used, 975161122 free (18 frags, 121895138 blocks, 0.0% fragmentation) UPDATE STANDARD SUPERBLOCK? [yn] y ***** FILE SYSTEM WAS MODIFIED ***** newsfeed-inn2# fsck /dev/vinum/v-spool ** /dev/vinum/v-spool BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/vinum/v-spool: CANNOT FIGURE OUT FILE SYSTEM PARTITION If I mount it after the fsck -b 32, it seems just fine. smaller vinum volumes mount/umount fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 15: 6:23 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 15:06:21 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from kuku.excite.com (kuku-rwcmta.excite.com [198.3.99.63]) by hub.freebsd.org (Postfix) with ESMTP id 8A46737B404 for ; Sat, 6 Jan 2001 15:06:21 -0800 (PST) Received: from pugsly.excite.com ([199.172.148.160]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010106230621.XYCI11766.kuku.excite.com@pugsly.excite.com> for ; Sat, 6 Jan 2001 15:06:21 -0800 Message-ID: <5546455.978822381106.JavaMail.imail@pugsly.excite.com> Date: Sat, 6 Jan 2001 15:06:20 -0800 (PST) From: John Wilson To: freebsd-hackers@freebsd.org Subject: Converting Perforce to CVS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 192.116.94.254 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I apologize in advance, as this is not strictly a FreeBSD-related question, but I know that a lot of FreeBSD'ers use CVS as well as Perforce, so here goes... What is the easiest way to convert a P4 source repository to CVS, while preserving revisions, history, log messages, etc? Both systems seem to use RCS, but is it as simple as copying the files? Are there any caveats? Thanks, John _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 15:43: 2 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 15:43:00 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wellington.cnchost.com (wellington.concentric.net [207.155.252.14]) by hub.freebsd.org (Postfix) with ESMTP id 7454B37B400 for ; Sat, 6 Jan 2001 15:43:00 -0800 (PST) Received: from buffy (w072.z064003114.lax-ca.dsl.cnc.net [64.3.114.72]) by wellington.cnchost.com id SAA14825; Sat, 6 Jan 2001 18:42:59 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Errors-To: From: "SteveB" To: Subject: RE: KVM switch vs. FreeBSD psm driver Date: Sat, 6 Jan 2001 15:45:24 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <200101062231.f06MVuZ11595@vashon.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same problem with Windows, Linux, and FreeBSD. I am using assorted MS wheel mice. Windows I can get to recover, by switching back and forth a couple times. Linux sometimes the problem goes away if I config X for a generic two-button mouse and no three button emulation. FreeBSD the only thing I can do is use the keyboard command to kill X and startx again and everything is fine. Steve B. > -----Original Message----- > From: jdp@wall.polstra.com [mailto:jdp@wall.polstra.com]On Behalf Of > John Polstra > Sent: Saturday, January 06, 2001 2:32 PM > To: hackers@FreeBSD.ORG > Cc: jack@germanium.xtalwind.net > Subject: Re: KVM switch vs. FreeBSD psm driver > > > In article > , > jack wrote: > > > > I have a Brand X KVM which also claims Intellimouse support. > > I've found that if the switch is set to a machine when that > > machine boots all is well, if I boot a machine with a different > > one active on the KVM when I go to the one that was booted the > > mouse jumps, psm errors, etc. > > That doesn't seem to help in my case, unfortunately. > > John > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 15:59:22 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 15:59:20 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D58E337B400; Sat, 6 Jan 2001 15:59:19 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA28594; Sat, 6 Jan 2001 15:59:19 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f06NxIv11832; Sat, 6 Jan 2001 15:59:18 -0800 (PST) (envelope-from jdp) Date: Sat, 6 Jan 2001 15:59:18 -0800 (PST) Message-Id: <200101062359.f06NxIv11832@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Reply-To: hackers@freebsd.org Subject: Re: KVM switch vs. FreeBSD psm driver (Solved!) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , John Polstra wrote: > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > much smarter than it really is. When I try to use the mouse through > it with FreeBSD (-current from around Christmas, but I also had > problems with -stable) it doesn't work right at all. It's got the > same symptoms everybody else has reported: the cursor jumps around, > and lots of "psmintr: out of sync" messages get logged. I'm happy to report that this problem is solved now. After one fellow wrote to me and reported that his switch of the same model worked OK, I hunted around on the Belkin web site. It turns out that Belkin assembled a few thousand of the units with two EPROMs swapped, and mine was one of them. I moved the chips to their proper sockets, and now everything works fine. You can find the gory details here: http://www.belkin.com/support/downloads/manuals/Omnipro.pdf John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 16:52:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 6 16:52:27 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id DCF1A37B402 for ; Sat, 6 Jan 2001 16:52:24 -0800 (PST) Received: (qmail 69426 invoked by uid 1001); 7 Jan 2001 10:52:21 +1000 X-Posted-By: GJB-Post 2.08 05-Jan-2001 (FreeBSD) X-URL: http://www.gbch.net X-Image-URL: http://www.gbch.net/gjb/img/gjb-auug048.gif X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 X-PGP-Public-Key: http://www.gbch.net/gjb/gjb-pgpkey.asc Message-Id: Date: Sun, 07 Jan 2001 10:52:21 +1000 From: Greg Black To: hackers@freebsd.org Subject: psmintr: out of sync Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an intermittent (and fairly rare) problem with various PS/2 mice on a set of boxes running 4.1-R (but the problem was also evident under 3.{1,2,3,4}-R). The boxes all run X and, on occasion, the mouse will stop working and hundreds of "psmintr: out of sync" messages will be logged. It happens maybe once in 6 weeks on one of seven machines, so is not easy to diagnose. I can fix it by logging in with ssh (or switching to one of the virtual consoles if the box is handy), killing and re-starting moused. This is not a very useful solution for distant clients who are not competent to do stuff like that and tend to resort to the power switch if I'm not available instantly -- and that leads to undesirable collateral damage. I'm keen to hear practical suggestions for a fix, or even better that a bug has been found and fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 18:47:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id DA12237B69C for ; Sat, 6 Jan 2001 18:46:43 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f072lG400803; Sat, 6 Jan 2001 18:47:16 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101070247.f072lG400803@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: John Wilson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Converting Perforce to CVS In-Reply-To: <5546455.978822381106.JavaMail.imail@pugsly.excite.com> Date: Sat, 06 Jan 2001 18:47:16 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Wilson wrote: > I apologize in advance, as this is not strictly a FreeBSD-related question, > but I know that a lot of FreeBSD'ers use CVS as well as Perforce, so here > goes... > > What is the easiest way to convert a P4 source repository to CVS, while > preserving revisions, history, log messages, etc? Both systems seem to use > RCS, but is it as simple as copying the files? Are there any caveats? > > Thanks, > > John perforce only uses the rcs files to store discrete file revisions, the rest of the metadata is in the db.* files (log messages, branches, views, etc). Generally, the "most correct" way to do a conversion is to generate a list of changes and run through them one at a time - checking them out of one repo and into the other, and then tweak the metadata (timestamp, author). Going from cvs to perforce is pretty hard as cvs does not maintain enough information to make a faithful conversion without some guesses and heuristics. Going the other way should be pretty simple as you have a list of discrete changes starting at change 1, then 2, etc. Check them out one at a time and check the changes into cvs. It will take a while but it will work if you get your scripting right. No, I dont know of anybody who has actually wanted to go this way before, so I am not aware of any pre-canned p4->cvs scripts. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 19:12:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B69DB37B6B1 for ; Sat, 6 Jan 2001 19:10:41 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f073Ae722747; Sat, 6 Jan 2001 22:10:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 6 Jan 2001 22:10:40 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@freebsd.org Cc: John Polstra Subject: Re: KVM switch vs. FreeBSD psm driver (Solved!) In-Reply-To: <200101062359.f06NxIv11832@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Jan 2001, John Polstra wrote: > In article , > John Polstra wrote: > > > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > > much smarter than it really is. When I try to use the mouse through > > it with FreeBSD (-current from around Christmas, but I also had > > problems with -stable) it doesn't work right at all. It's got the > > same symptoms everybody else has reported: the cursor jumps around, > > and lots of "psmintr: out of sync" messages get logged. > > I'm happy to report that this problem is solved now. After one fellow > wrote to me and reported that his switch of the same model worked OK, > I hunted around on the Belkin web site. It turns out that Belkin > assembled a few thousand of the units with two EPROMs swapped, and > mine was one of them. I moved the chips to their proper sockets, and > now everything works fine. You can find the gory details here: > > http://www.belkin.com/support/downloads/manuals/Omnipro.pdf Do you know if this fixes the problem the following problem that I started experiencing somewhere in the RELENG_4 line? For some machines, if the KVM is not pointed at the box, the keyboard will not probe properly, and does not respond for that session. As long as I boot with the KVM pointed at the machine during the boot process, it probes fine. This doesn't seem to impact the boot loaders, only after the kernel has loaded and probed. It's really annoying as my crashbox has this problem, so I have to swap to it every time I boot, and given the need to type continue in the serial gdb, I often miss the window. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 19:41:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 5543A37B400 for ; Sat, 6 Jan 2001 19:41:34 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id QAA13937; Sun, 7 Jan 2001 16:41:31 +1300 (NZDT) Message-Id: <200101070341.QAA13937@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: freebsd-hackers@FreeBSD.ORG Date: Sun, 7 Jan 2001 16:41:29 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: KVM switch vs. FreeBSD psm driver (Solved!) Reply-To: dan@langille.org Cc: John Polstra References: <200101062359.f06NxIv11832@vashon.polstra.com> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Jan 2001, at 22:10, Robert Watson wrote: > Do you know if this fixes the problem the following problem that I started > experiencing somewhere in the RELENG_4 line? For some machines, if the > KVM is not pointed at the box, the keyboard will not probe properly, and > does not respond for that session. As long as I boot with the KVM pointed > at the machine during the boot process, it probes fine. This doesn't seem > to impact the boot loaders, only after the kernel has loaded and probed. > It's really annoying as my crashbox has this problem, so I have to swap to > it every time I boot, and given the need to type continue in the serial > gdb, I often miss the window. This is probably not helpful to your situation, but thought I should contribute this as it is KVM related. I just bought a KVM switch (My Hopper, by Rextron Technology). I bought 10M cables to use with it. The FreeBSD box won't boot if I use those cables. It thinks the keyboard isn't there. Note: this appears to be a BIOS problem as if I want long enough, I get the "keyboard not found, press F1 to continue" message. If I don't use the 10M cables, the box boots as expected. Yes, I've thought of enabling no-keyboard booting, but there is no setting in the BIOS. It's on the motherboard I'm told and I've yet to open the box and find it. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ FreshPorts - http://freshports.org/ NZ Broadband - http://unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 21:10:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DE80B37B698; Sat, 6 Jan 2001 21:10:01 -0800 (PST) Received: from localhost (tw3p0y@localhost [127.0.0.1]) by green.dyndns.org (8.11.1/8.11.1) with ESMTP id f0759uw74992; Sun, 7 Jan 2001 00:09:59 -0500 (EST) (envelope-from green@FreeBSD.org) Message-Id: <200101070509.f0759uw74992@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Jeremiah Gowdy" Cc: freebsd-hackers@FreeBSD.org Subject: Re: ONTOPIC - FreeBSD vs Linux, Solaris, and NT - Not a bunch of licence Jihad crap In-Reply-To: Message from "Jeremiah Gowdy" of "Thu, 28 Dec 2000 16:23:48 PST." <001801c0712d$9d46be20$aa240018@vista1.sdca.home.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 00:09:56 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeremiah Gowdy" wrote: > > Uuuuh, I'm gonna have to agree with Murray that there is a complete > > dearth of free software for Windows. Go search shareware.com, or > > Tucows, or any of the other Windows-centric software sites, and just > > TRY to find most of the same tools or applications you take for > > granted on your Unix box. I do all the time, and wished to hell I was > > managing thousands of BSD boxes instead of Windows. The free software > > either doesn't exist, is of very poor quality, or you have to pay for > > it. While "free as in beer" software for Windows is fairly prevalent, > > GOOD free software is quite rare, and open-sourced software for > > Windows is very rare indeed. > > He said, the "amount of free software". He didn't say the amount of free > GOOD software, the amount of useful applications, etc. He said AMOUNT of > FREE software. He didn't say the AMOUNT of OPEN SOURCE software. Saying > that there is more _free software_ for FreeBSD than there is for Windows is > insane. If you're talking about how useful it is, or whether it's open > source, you need to specify those things. But anyone worth their salt would > choke on the general statement, "there is more free software for FreeBSD > than there is for Windows". What's so "free" about software that you don't pay money for? Pretty much nothing compared to software that you are /free/ to modify and /free/ to use any way you want is "free". There is very little of that for Windows compared to for Unix in general. Instead of a lot of free software for Windows, there's quite a lot of no-value software. I don't know why you'd possibly think that software is more /useful/ by costing no money -- and in that it means that it is not an important distinction. Software is more useful if it is truly free (unencumbered by restrictions), therefore that is the important distinction which should define "free" software. We already have a term for software that just costs no money: "freeware". This is _NOT_ free software. Shareware is not free software. GPLed, BSDed, X11ed, public domain, APSLed (ad infinitum) code is free software, the kind that is not often written for Windows. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 21:42:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail3.sdc1.sfba.home.com (femail3.sdc1.sfba.home.com [24.0.95.83]) by hub.freebsd.org (Postfix) with ESMTP id AC52437B400; Sat, 6 Jan 2001 21:42:07 -0800 (PST) Received: from cx443070b ([24.0.36.170]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010107054028.XIFW1118.femail3.sdc1.sfba.home.com@cx443070b>; Sat, 6 Jan 2001 21:40:28 -0800 Message-ID: <001801c0786c$e5d55b60$aa240018@cx443070b> From: "Jeremiah Gowdy" To: "Brian F. Feldman" Cc: , References: <200101070509.f0759uw74992@green.dyndns.org> Subject: Re: ONTOPIC - FreeBSD vs Linux, Solaris, and NT - Not a bunch of licence Jihad crap Date: Sat, 6 Jan 2001 21:44:20 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's so "free" about software that you don't pay money for? Pretty much > nothing compared to software that you are /free/ to modify and /free/ to use > any way you want is "free". There is very little of that for Windows > compared to for Unix in general. Okay, this levels of "free" concept that comes with GPL/BSD licenced software is pretty fuzzy. If I may quote President Clinton, "it depends on what the meaning of the word 'is' is." Claiming that software isn't "free" because it's not valuable is redefining the word "free" to mean something that has no cost, yet has value. free (fr) adj. Costing nothing; gratuitous: The word has absolutely nothing to do with your value judgements. Useful != Free. No cost == Free. > We already have a term for software that just costs no money: "freeware". > This is _NOT_ free software. Shareware is not free software. GPLed, BSDed, > X11ed, public domain, APSLed (ad infinitum) code is free software, the kind > that is not often written for Windows. You're idioticly redefining the term "free" to be software with source code and restrictions, rather than no source code and no restrictions. You can't define the language. Free doesn't have a damned thing to do with your value judgements on what's useful, what's "no-value", whether or not it includes source, and whether or not it travels under the restrictions of your "free" licence. You're saying that the only "free" software is open-source software, and that's a pretty damned closed minded point of view. I've written hundreds of DOS and Windows applications, which are FREE, although I didn't include the source code with them. Your massive generalization that most Windows software is not "free" (by your foolish definition), that most of it is "no-value", and that "freeware" does not equal "free software" (instead "open source" = "free software"), is all terribly insulting to someone who's written free software for DOS and Windows for years. Who the hell are you to say that my software isn't free and isn't useful just because it isn't open source ? Certainly, open source is preferrable, but you can't start redefining words like "free" to push your rabid open source agenda. The people of the past who contributed their software to the scene in the form of public domain, freeware, and shareware were writing code in the same spirit as those of us who write open source code today. So why don't you get off your goddamned high horse and stop belittling the "free" software for other platforms simply because it doesn't comply with your open source jihad bullshit. I'm not anti-open source in the slightest, but I won't have my work, and the work of millions of other DOS and Windows programmers over YEARS, belittled by some asshole who can't look up the word "free" in the dictionary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 22:13: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id AF21237B400 for ; Sat, 6 Jan 2001 22:12:42 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14F9AK-0000Mk-00; Sat, 06 Jan 2001 23:18:52 -0700 Message-ID: <3A580A4C.3756593C@softweyr.com> Date: Sat, 06 Jan 2001 23:18:52 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: hackers@freebsd.org Subject: Re: KVM switch vs. FreeBSD psm driver References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > I realize this is a well-known problem. Although there's much > discussion about it in the mailing list archives, I couldn't find an > actual solution. > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > much smarter than it really is. When I try to use the mouse through > it with FreeBSD (-current from around Christmas, but I also had > problems with -stable) it doesn't work right at all. It's got the > same symptoms everybody else has reported: the cursor jumps around, > and lots of "psmintr: out of sync" messages get logged. I have a Belkin OmniCube 4-Port KVM I use with FreeBSD-notso-current from prior to SMPng and FreeBSD-STABLE, it works fine with my Logitech MouseMan M37. We have a bunch of these OmniCubes at work, and they have fits with some cheap mice, but rarely fail with Logitech or Microsoft (ick!) mice. My brother informs be Belkin KVM switches drive his Linux machines into fits, and to use the other really big brand of KVM switches that isn't coming to mind right now. YMMV. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 22:14:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 7FE4A37B400 for ; Sat, 6 Jan 2001 22:14:28 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14F9C8-0000Mr-00 for hackers@freebsd.org; Sat, 06 Jan 2001 23:20:44 -0700 Message-ID: <3A580ABB.1C35C44C@softweyr.com> Date: Sat, 06 Jan 2001 23:20:43 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: KVM switch vs. FreeBSD psm driver (Solved!) References: <200101062359.f06NxIv11832@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > In article , > John Polstra wrote: > > > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > > much smarter than it really is. When I try to use the mouse through > > it with FreeBSD (-current from around Christmas, but I also had > > problems with -stable) it doesn't work right at all. It's got the > > same symptoms everybody else has reported: the cursor jumps around, > > and lots of "psmintr: out of sync" messages get logged. > > I'm happy to report that this problem is solved now. After one fellow > wrote to me and reported that his switch of the same model worked OK, > I hunted around on the Belkin web site. It turns out that Belkin > assembled a few thousand of the units with two EPROMs swapped, and > mine was one of them. I moved the chips to their proper sockets, and > now everything works fine. You can find the gory details here: Snort. Let's hear it for good web support, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 23: 9:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id DE9E837B6A1 for ; Sat, 6 Jan 2001 22:34:07 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id WAA31144; Sat, 6 Jan 2001 22:35:13 -0800 Date: Sat, 6 Jan 2001 22:35:13 -0800 From: Kris Kennaway To: "Daniel O'Connor" Cc: Charles Randall , freebsd-hackers@FreeBSD.ORG Subject: Re: encrypt h/w for FreeBSD? Message-ID: <20010106223513.C31085@citusc.usc.edu> References: <5FE9B713CCCDD311A03400508B8B3013054E3D07@bdr-xcln.is.matchlogic.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="aT9PWwzfKXlsBJM1" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from doconnor@gsoft.com.au on Sat, Jan 06, 2001 at 11:38:11AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --aT9PWwzfKXlsBJM1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 06, 2001 at 11:38:11AM +1030, Daniel O'Connor wrote: >=20 > On 05-Jan-01 Charles Randall wrote: > > nCipher's nFast card supports FreeBSD 3.3 and 3.4. > > =20 > > http://www.ncipher.com/products/nfast_specs.html >=20 > I think Mike Smith is 'sort of' working on support for HW crypto cards.. = No idea > how far he has got.=20 I think the eval hardware got passed on to Mark Murray at BSDCon..haven't heard anything though. Kris --aT9PWwzfKXlsBJM1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6WA4hWry0BWjoQKURAk3MAKDoZC/HzuHl77AymJFUAazvWgNWpACgmVwI UOBmfXNDMVzI4ItEBoz2nZc= =Ix/Q -----END PGP SIGNATURE----- --aT9PWwzfKXlsBJM1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 6 23:48:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 3A87837B402; Sat, 6 Jan 2001 23:48:06 -0800 (PST) Received: from shell-3.enteract.com (stox@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id BAA16838; Sun, 7 Jan 2001 01:48:04 -0600 (CST) (envelope-from stox@enteract.com) Date: Sun, 7 Jan 2001 01:48:03 -0600 (CST) From: Ken Stox To: Jeremiah Gowdy Cc: "Brian F. Feldman" , freebsd-hackers@FreeBSD.org, lan@irev.net Subject: Re: ONTOPIC - FreeBSD vs Linux, Solaris, and NT - Not a bunch of licence Jihad crap In-Reply-To: <001801c0786c$e5d55b60$aa240018@cx443070b> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found this message to be so off base, that I felt it necessary to reply. I hope the original author wil not mind. On Sat, 6 Jan 2001, Jeremiah Gowdy wrote: > Claiming that software isn't "free" because it's not valuable is redefining > the word "free" to mean something that has no cost, yet has value. > > free (fr) adj. Costing nothing; gratuitous: > > The word has absolutely nothing to do with your value judgements. Useful != > Free. No cost == Free. [ The dict command is your friend ] 1. Exempt from subjection to the will of others; not under restraint, control, or compulsion; able to follow one's own impulses, desires, or inclinations; determining one's own course of action; not dependent; at liberty. 2. Not under an arbitrary or despotic government; subject only to fixed laws regularly and fairly administered, and defended by them from encroachments upon natural or acquired rights; enjoying political liberty. > > > We already have a term for software that just costs no money: "freeware". > > This is _NOT_ free software. Shareware is not free software. GPLed, > BSDed, > > X11ed, public domain, APSLed (ad infinitum) code is free software, the > kind > > that is not often written for Windows. I would agree with this statement fully in the case of BSD and X11. The other cases do not fulfill the definition of "free." GPL is not free, although it approaches it. GPL, APSL, etc. are subject to the will of the authors. > You're idioticly redefining the term "free" to be software with source code > and restrictions, rather than no source code and no restrictions. You can't > define the language. Free doesn't have a damned thing to do with your value > judgements on what's useful, what's "no-value", whether or not it includes > source, and whether or not it travels under the restrictions of your "free" > licence. You're saying that the only "free" software is open-source > software, and that's a pretty damned closed minded point of view. I've I'm afraid you are the victim of a "pretty damned closed minded point of view." "Free" binaries are under the restraint, control, and compulsion of the author. the user is unable to determine the course of action. If I cannot freely change the function of a program, it is not "free". If I must perform other actions as a result of my modifications, it is not "free." I am being compelled to perform. This is not "free." > written hundreds of DOS and Windows applications, which are FREE, although I > didn't include the source code with them. Your massive generalization that > most Windows software is not "free" (by your foolish definition), that most > of it is "no-value", and that "freeware" does not equal "free software" > (instead "open source" = "free software"), is all terribly insulting to > someone who's written free software for DOS and Windows for years. Who the > hell are you to say that my software isn't free and isn't useful just See clues #1 and #2 above. By your definition of "free", No cost == Free. I would contend that there is NO SUCH thing. It costs money to download software, it costs money to install software, and it costs money to maintain software. In fact, in most cases, these costs exceed the cost of purchasing software from commercial companies. > because it isn't open source ? Certainly, open source is preferrable, but > you can't start redefining words like "free" to push your rabid open source > agenda. The people of the past who contributed their software to the scene > in the form of public domain, freeware, and shareware were writing code in > the same spirit as those of us who write open source code today. So why > don't you get off your goddamned high horse and stop belittling the "free" > software for other platforms simply because it doesn't comply with your open > source jihad bullshit. BSD/X11 Open Source is about the only truly "free" software around. Binaries have many hidden costs. Freeware is a great thing, but it is not truly "free." BTW, I should mention that I have written and contributed to a great deal of freeware over the years. But any freeware I have written has been under my control. I have the source. It is not free in the truest form of the word. The ones I did release, the source to the public domain to, are truly free. It has been a wonderful experience to see what they matured into years later. > I'm not anti-open source in the slightest, but I won't have my work, and the > work of millions of other DOS and Windows programmers over YEARS, belittled > by some asshole who can't look up the word "free" in the dictionary. Hmmm, I suggest you look up "free" in the dictionary. And now, back to our originally scheduled program, "The Golden Age of Ballooning." -Ken Stox stox@imagescape.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message