From owner-freebsd-hackers Sun Sep 9 0:54:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 310C937B401; Sun, 9 Sep 2001 00:54:20 -0700 (PDT) Received: from sm.socccd.cc.ca.us (pool0056.cvx15-bradley.dialup.earthlink.net [209.179.44.56]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f897sIa17803; Sun, 9 Sep 2001 00:54:18 -0700 (PDT) Message-ID: <3B9B20D8.5393D4E@sm.socccd.cc.ca.us> Date: Sun, 09 Sep 2001 00:57:12 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Hackers@FreeBSD.ORG Cc: sos@FreeBSD.ORG Subject: Failure to fixate cd in burncd Content-Type: multipart/mixed; boundary="------------2C67590429291780833B3BCB" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------2C67590429291780833B3BCB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, Sometimes when I burn data CD's from ISO's at 12x speed like so: # burncd -f /dev/acd1c -s 12 data file.iso fixate The fixate fails, and I believe it is because the CD-R has not yet spun down from the burn phase. The problem doesn't occur when the burn is done at a lower speed. The fixate works perfectly if, immediately after the 12x speed burn, I then do "burncd -f /dev/acd1c -s 12 fixate," because then the CD-R has stopped doing the burning phase. I don't know that much about ATA or anything, but I have attached a patch for burncd (against -STABLE) which will perhaps fix the problem (it does for me at least). It just retries the CDRIOCCLOSEDISK ioctl (which is the ioctl that fails) a few times, with pauses in between. Any thoughts? BTW, don't EVER try mounting a CD that has an .iso image burned to it but hasn't been fixated. There is a fatal kernel trap, and then somewhere in the code that handles kernel traps, there is another fatal trap, so there is a continuous barrage of kernel trap messages and information; these go on indefinitely until you press a key. -- farooq --------------2C67590429291780833B3BCB Content-Type: text/plain; charset=us-ascii; name="burncd.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="burncd.txt" --- /usr/src/usr.sbin/burncd/burncd.c Sat Mar 3 23:59:34 2001 +++ burncd.c Sun Sep 9 00:47:25 2001 @@ -118,9 +118,16 @@ for (arg = 0; arg < argc; arg++) { if (!strcmp(argv[arg], "fixate")) { + int retries; + if (!quiet) fprintf(stderr, "fixating CD, please wait..\n"); - if (ioctl(fd, CDRIOCCLOSEDISK, &multi) < 0) + for (retries = 5; retries; retries--) { + if (ioctl(fd, CDRIOCCLOSEDISK, &multi) == 0) + break; + usleep(100000); + } + if (retries == 0) err(EX_IOERR, "ioctl(CDRIOCCLOSEDISK)"); break; } --------------2C67590429291780833B3BCB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 0:58:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.sovintel.ru (ns.sovintel.ru [212.44.130.6]) by hub.freebsd.org (Postfix) with ESMTP id 4EEC137B406 for ; Sun, 9 Sep 2001 00:58:43 -0700 (PDT) Received: from ppp70-spb-213-221-48.sovintel.ru (ppp70-spb-213-221-48.sovintel.ru [213.221.48.70] (may be forged)) by ns.sovintel.ru (8.11.5/8.11.5) with SMTP id f897vGo66080 for ; Sun, 9 Sep 2001 11:57:26 +0400 (MSD) (envelope-from helprita@list.ru) Message-ID: <00de01c138d8$84c3cb40$1230ddd5@users.mns.ru> From: "alya radzik" To: freebsd-hackers@FreeBSD.org Subject: =?koi8-r?B?0M/Nz8fJ1MUg09DB09TJIM3BzMXO2MvVwCDExdfP3svV?= Date: Sun, 9 Sep 2001 06:38:32 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00DB_01C138FA.0B785720" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2417.2000 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01C138FA.0B785720 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit Моей дочери Рите 7 лет. 1 января 2001 года у нее начались спазмы почки, а на следующий день вылился почти литр крови. Маргарите поставили страшный диагноз - опухоль Вилмса правой почки с метастазами в правое легкое, 4-я стадия. С этого момента девочка перенесла курс интенсивной лучевой и химиотерапии, тяжелейшую операцию по удалению правой почки и опухолевого тромба длиной 8.5 см., заражение крови через катетер, химический ожог кишечника, гемаррагический синдром и падение зрения. Состояние и мучения девочки не передать никакими словами. Несмотря на полгода интенсивных процедур лечение Маргариты далеко от успешного завершения. А ведь Рита всего лишь семилетняя девочка, которая очень любит танцевать и много трудилась до болезни, чтобы стать балериной. Наши опытные врачи дают нам благоприятный прогноз, но чтобы вылечиться, нам необходимы лекарства для защиты и поддержания органов, время от времени нужна кровь для вливания. Лекарства очень дорогие, одна ампула нейпогена стоит 180 долларов, а ампул нужно много, перед каждым блоком химии. 50 мг. дифлюкана в растворе стоят 550 рублей - это нам на день, 7 капсул дифлюкана по 50 мг. - около 900 рублей, а в день нужно принимать 2 капсулы. Мы должны пить эссенциале, покупать противорвотные латран, зофрам, для защиты сердца от токсического воздействия химии и общей поддержки нужны кардиоксан, инозия-ф, коэнзим Q10 и т.д. Рита очень нежная девочка и плохо переносит жесткий протокол лечения по 4 стадии. Она была на грани гибели после лечения химиопрепаратом карбоплатина. Поэтому ее перевели на менее жесткий протокол лечения по 3 стадии, но остающийся метастаз в легком вероятно вынудит врачей снова провести курс карбоплатины, о чем нас заранее предупредили, и тогда нам будет нужен амбизом - самый эффективный на сегодняшний день противогрибковый препарат. Нам понадобится около 10 ампул амбизома, а цена одной ампулы около 220 долларов. Его более дешевые аналоги для нас непригодны из-за токсичности. Мы с Ритой, ее бабушкой и моей сестрой живем в одной комнате (14.2 м2) в коммуналке на первом этаже, под нами в подвале постоянно стоит вода. Квартира темная и сырая. Даже когда ход лечения позволяет нам возвращаться домой, мы с дочкой часто предпочитаем оставаться в больнице, где условия проживания гораздо лучше. Я не могу работать, так как постоянно нахожусь на отделении вместе с Маргаритой. Моя мама получает пенсию 780 рублей, сестра зарабатывает около 1500 рублей. Прошу помощи, очень трудно! Заранее спасибо всем, кто откликнется. С уважением, Алевтина Раздик тел: (812)272-92-18 helprita@list.ru http://helprita.boom.ru ------=_NextPart_000_00DB_01C138FA.0B785720 Content-Type: image/jpeg; name="homerita.jpg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="homerita.jpg" /9j/4AAQSkZJRgABAgEASwBLAAD//gAmRmlsZSB3cml0dGVuIGJ5IEFkb2JlIFBob3Rvc2hvcKgg NS4w/+4AIUFkb2JlAGSAAAAAAQMAEAMCAwYAAAAAAAAAAAAAAAD/2wCEAAwICAgJCAwJCQwRCwoL ERUPDAwPFRgTExUTExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4N EA4OEBQODg4UFA4ODg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM DP/CABEIAGQAWgMBIgACEQEDEQH/xADLAAACAgMBAQAAAAAAAAAAAAAFBgMEAAcIAgEBAAIDAQAA AAAAAAAAAAAAAAIDAAQFARAAAgICAgEDAwMFAAAAAAAAAgMBBAAFERIGExQWICIVECEyMDEkBxcR AAIBAwEFBQMGCA8AAAAAAAECAwAREgQhMUEiE1EyQlIzciMUcbFigpKiEGHSU2NzNAUgMIGRodGy wuJDk8PjVDUSAAIBAwEFBQcFAAAAAAAAAAABETECEiEQQWFCEyBRcSIy8IGRobFSYoIDI1MU/9oA DAMBAQIRAxEAAAAcdUpMwmT2uScM+k2JHtZfghaa7aLHrS+NfYMCE3NCeJjyhxZjaEcoBAkxOiHm iSvxsDAuulUpSV+BCjNdVHLjQgUGCyy5IzEbJKFpor8mriVurXbbr1i2ETYmv2uteonuCNtG00ze TWJhFaK8dHgUJJ950BVvzZ82YLmWKcjalojpEx2lIjoLN+hN0R1F6PjEFUKUaaq+xRN8PRsjXxQ2 Bq1wpG9NYbBNJkTkU2dEavOeciRS0zmYXSBnlbNIeqs5Vwp1VnKuSdVZyrknVWcq5J//2gAIAQIA AQUAJSywlhMJUoSlHUuk8+nPHQeFLkiBa4yRjh0yI+4LgZKZV9sDMzBZZnhfeOoyMlEc5EzhRzHM SP8AkdhI3BTlkRE8yU/tyUZ1H1VJ65W4yI4zrHOdY5T/AHD+P0f/2gAIAQMAAQUAFpDkNnkRa0rC GpiYHjkOec5yTZEy9zBmOQ6jgliw7SQjGCQzgDzPSeRHnE4Y/tASElH3cIyJBZQYHBp+305iCkYn tPUmwWRyOTZLrJlP6s/l9P8A/9oACAEBAAEFANVsU1RR5RrRv3F+JbANd8c1y27vS6mhHkmyfbqe b3Eg7zixYVoPJqGqqV9/Qsq/OURj5TrsAGTMIvdVULtiT1ezWTKFrYtPx5ZHapQGuTZNpaW2rYVb Ba+Ned0vR9hGR40EiXjFuM+L3iHZ+PWwoAQamrdfcsuTetDYrqbT29DrWylo421hPiFxQfjNlkTz nM4fPHkHkJPdagvTlZNWWqZCS1fvagdhDxlNYrjNzTSHyFWespcPv1VzsPKKQVNTVtXV1tE1mR4f wIePWAyvpIrjv6xK2tQ1qr7qrUvo+O0csxYOHn1jbX2MLQFwGuBfUBGckB6lCO3l9IGN1IrsYjQr i76uWNTTdG+WmmgyWk/FEkNSu6lEqzpJRZUayv21LB+vKrl/QWhrfHdnkFzH+wFvrW68TaOprnPp fHdgTtQh80Hh5Im3VZccrd7NSb292iTqxvXVK/5irh2whWyTSvhvPHatJWjaoQu20RlUlkkwQZtg BDygjsb0qtloavYt1uy+cOw4cmke090CNnZhWjam4mNn6L0Xqq5sW1tYMtIb3jjatibCjzVvRqXe 8qZFol5Z1tCkes9ge1vQiqz2yrk1qVscmtMApXWOMVXrpnY6HWbJX/N62bOwNjHN2A5qNUTLWuoT Vojr6QEK+v12/Yezb8k9TTfifdf0f//aAAgBAgIGPwDK6JMZTtmhFqTuZrbBDfhBvOYiiWswUl94 4OJGbp3EE73s1Y25xS1aOl/ou6cZTHmy/ryLdyZuIgpBBjy5ermxElW3eY3vLF1PEagWjRl0/NGP UknW1Oto/wCOPyeydkwXeK9Qqe7s/wD/2gAIAQMCBj8AhNktVpCFbanLF1FGVDL4yU+eySU2o7hW /uN3K3W2RplR7KFB8aGfRWeUV5fuxGhktwVTQzLXKIifKaveNLSVREWy49vSWttrhdUbmZPXxwga xVzSqZZKXy2kfVEPaq/o7X//2gAIAQEBBj8AKyzTadggETqtyhvzt9LKo5Z9RPqIYwVJ6Vrk28r0 Ypv3trVheQyNE98Lk+HKPJcam08H7z1LpKCosiFlW3mwp5NFLqddqMBHH18QntOi9JOWgNRqmIBu FJ5N98V8lRxMFlixJ6rXy2fSqTSMuEc4Kl1UsTfZ2+WunrG5Cw9+l9g7q9SLvUJ9O5kiYlQQQBkO 93qu0gH4iy/11x324UcmIvuAFzs/u1ksbG/4t9ASpgRwJCV3DHGwuxBJOI8VR6aEHA5MwF74pUMT e6ji5mFiC39FLDpO/ECBnxBOVSQ3tNHdlI4Yml65w1KWs/A25sXqbJV00+nZmWSMOQxYKfTHI3NU aRR6d81F5cTG4uB4WeTmr/zYvR/OLv8Azu+jdYwbWUgC/wBakZNSqMl9yA/PWL6xbE5G0Sg39qtT qH1zySJA/JiLMArcn1q08/VL6uWEq8SixUnbi1B3lOQIsMiLL9WpIJJCyNsiLG6g/VOVM+oGOVyj C5Uljy1LGRZhNioO61+T7r1JGNQISFV+m3EHvL9qiTwUBABfYK3N6GHHf5a2fgNjapY4nxgiGC23 Mx8bezRdrtKF3ntJotuLAknibGutGpZSbbPlrpup60Numx4G1TFl9+JVyHYQwXl+zQ1MwvgjR7eN zfm9nGun1Stjytvt8teovZ/jqxYWoozAsNoUG9SFQ2RRgDs2bPlqReCG+R43rpyi6NYX7LGioIA4 bKWGNAEYjqtwuBytTAhWJWxvvv8AyUMUEaaghrdjLjnTtJIVBkBJ7BfmqGXTzpEyyBM1bYQ/sV+1 zbrd7727u00gZ+Xbv4eGlYSPcXMuR33pdMhxWVrADiPM3loRxD3YNjxJ9qtoFxWyjR2bbbajlQW6 JZieIvYVLGSmCg26gBB4feo6l36caOGRFC2BHnby14N+PfXu+agGBBtY22bKugGZZwLncoNua9Nq p1B3soubn2dtJLqAV6m2w27CaVBIEcjYrcpP2qt2UduyiwOy/wA9PFKmTMdhIvtqSf8AypkDAbrB ifCKhkjndpZZArCVjgqtl5e4qV6qbsPU4f8AY/U1s40kgGUUgYp2E27tGZx1B33v2LzKn0aQaeUw nHbiATt8uVO8v711DxLtjgkW4DbO89mXH2KvIecXFD4SODVLdrpNI62GzFss/wDbq2qgEEw3hWDo QPEj/l1NC7hWhnUpluKjBnWpAlimClLdjWf7uVL8LGsstgJkk5gUJ8KpXrj07em+/wDMd2thuwPh oQ6nGVg2cd96ipNbooTGCMZEFitjys6ighO2ukGGbdu6gUIIPZVrDMb+2rDh2Vq0iOWLNc9pDfk1 AGNhioIvwxWvidNEspQdEo635Se/HjzZ1/50Pq5f8v6ypnHK0RdhsFiL5f2a1McoTOUWgdmsN3d5 F8zU+nnkWQRozRglSthhnj4mxyrqJLjynau8OPDR00ukeZmBYPmtnt5cvFSxTaCdG2HGwcC/stSP pFcTIQJEZGXlP0mGH3qGW/srVa+aOZQGL2CEg3OXqJlHUzQWaMRjFHGRDEczNj3Fjp5dbAZInjLd Wys3iX3fkzev2eT1M949P8qg7IXlmtlBJsIVjz8jeFa14nUhHXPT47lBUIycv6RfG9QNJ7kalhE8 YGIUSgqzr5EyoRmIRIB6lrXP0seWrRlXZDssQbXoAgC1ua+2go2kWN+N6u21jvP4GMUaRltrFVAv 9mmSeFQzj1EGLfzjvfWr9tbfb007nlpdTp7LIimKQ7GLb+5ieZUenhn1SOsitiLWANkLe3IuNKdL pS2sQgmaQkociyzKmzuJ9Ol000jam17mU5mxPp5N3lTwUXjhVGbeVFvmrYT/AA0+Fy+Kybo4Wt3m y7vL08/r1F8b0Ph8X6VrY48nUy6Xvf8AUqfoY/GX95a1rfoP0X8V/9k= ------=_NextPart_000_00DB_01C138FA.0B785720-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 2:47:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id 8C3C237B403 for ; Sun, 9 Sep 2001 02:47:21 -0700 (PDT) Received: by seven.Alameda.net (Postfix, from userid 1000) id 56F593A212; Sun, 9 Sep 2001 02:47:21 -0700 (PDT) Date: Sun, 9 Sep 2001 02:47:21 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.org Subject: Question about what programs to use in /etc/rc* Message-ID: <20010909024721.B1500@seven.alameda.net> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.3-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello everyone. I am looking at some PRs and I am trying to come up with a solution to submit a patch. I know how to use expr to test as tring in sh inside of a /etc/rc* script, but what method would people recommend to remove part of the string after expr confirmed that something is part of it ? These are some examples strings: "dhcp" "dhcp media 10baseTX" "media 10baseTX dhcp mediaopt half-duplex" The following code will get me inside a if condition: if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then .... fi What I would like to do inside the if .. fi is to remove "[Dd][Hh][Cc][Pp]" from the string so that the rest of the options can be used to call ifconfig. Otherwise the if .. fi will test if the string is then empty or just white spaces and if so it will not do anything but set ${dhcp_interfaces}. If its not empty it will call ifconfig with the extra options to set the interface. Awk/sed comes to mind but those are in /usr/bin and I am trying to avoid that. Any suggestions from the more experienced hackers ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 3:27:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id A7D4737B406 for ; Sun, 9 Sep 2001 03:27:40 -0700 (PDT) Received: (from root@localhost) by bugz.infotecs.ru (8.11.6/8.11.4) id f89AREX05365; Sun, 9 Sep 2001 14:27:14 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200109091027.f89AREX05365@bugz.infotecs.ru> Subject: Re: Kernel-loadable Root Kits To: charon@labs.gr (Giorgos Keramidas) Date: Sun, 9 Sep 2001 14:27:14 +0400 (MSD) Cc: freebsd-hackers@freebsd.org In-Reply-To: <20010909001951.A6949@hades.hell.gr> from "Giorgos Keramidas" at Sep 09, 2001 12:19:51 AM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > 1) scan the sysent table and check syscalls pointers (generally, rootkits > > intercepts syscalls) > > This can get really "hairy". To scan the syscall table, even if you > are 'root' and directly access /dev/mem you will have to use some > system calls to open(), read() and seek() into the /dev/mem device. > But those syscalls might be the intercepted ones: ouch! Of course this is not to be done from userland program. You should write your own KLD module which will compare sysent[] values against standart system calls and list the differences. I don't really see how "root kit" can prevent such scan. Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 3:32:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.teledis.be (mail.teledis.be [217.117.32.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F25237B405 for ; Sun, 9 Sep 2001 03:32:32 -0700 (PDT) Received: from natalie ([217.117.38.8]) by mail.teledis.be (Netscape Messaging Server 4.15) with SMTP id GJE5A801.H7T; Sun, 9 Sep 2001 12:32:32 +0200 Message-ID: <003601c1391b$50f7c580$0201a8c0@teledisnet.be> From: "Sansonetti Laurent" To: "Giorgos Keramidas" Cc: References: <002f01c13871$8dc2d360$0201a8c0@teledisnet.be> <20010909001951.A6949@hades.hell.gr> Subject: Re: Kernel-loadable Root Kits Date: Sun, 9 Sep 2001 12:36:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, > > 1) scan the sysent table and check syscalls pointers (generally, rootkits > > intercepts syscalls) > > This can get really "hairy". To scan the syscall table, even if you > are 'root' and directly access /dev/mem you will have to use some > system calls to open(), read() and seek() into the /dev/mem device. > But those syscalls might be the intercepted ones: ouch! I don't think so, you can easily make a KLD which simply scans the table and checks the pointers. This is not really good but it'll work. > Instead of worrying after the module has been loaded it's much safer > to run the kernel in securelevel>=1 when modules cannot be loaded > without a reboot to single-user mode. You might see this: http://www.s0ftpj.org/tools/securelvl.tgz (I didn't tested it yet). > -giorgos > -- Sansonetti Laurent - http://lrz.linuxbe.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 9:44:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by hub.freebsd.org (Postfix) with ESMTP id 9CA1C37B401 for ; Sun, 9 Sep 2001 09:44:32 -0700 (PDT) Received: from Bsdguru@aol.com by imo-r06.mx.aol.com (mail_out_v31_r1.4.) id 6.146.14cf6de (4242); Sun, 9 Sep 2001 12:44:20 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <146.14cf6de.28ccf663@aol.com> Date: Sun, 9 Sep 2001 12:44:19 EDT Subject: Re: PCI probe reordering? To: imp@harmony.village.org Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 9/9/01 2:52:52 AM Eastern Daylight Time, imp@harmony.village.org writes: > : I've encountered a MB that seems to probe devices in a less than desirable > : order. There is an onboard fxp controller, but it scans the slots first, > so > : that the onboard controller is fxp1 if there is another intel card in the > : box, for example. > : > : I want to make the onboard controller fxp0 (since most MBs probe that way > and > : it makes sense). Where would I have to hack to get Freebsd to probe slots > in > : reverse order? > > I truly believe that it would be easier to hack the pci bus code to > support wired hints than it would be to hack the probe order and still > have things work afterwards. > > The outline of the hack: > hints.fxp.0.at="pci1:10:0" > would be how you'd tell the system about it. Then, in the device > probe/attachment routine, check to see if the "at" hint, if it exists, > matches the bus:device:function you are about to probe. If so, go > ahead with the probe/attach. Otherwise bump the child number and go > to the "Then" part of this paragraph. > > This may be a little difficult, because I think that the probing the > children is actually pushed down into the bus code... > > Warner Its a bit hard to understand this without knowing what code you are referring to. Also, which routing specifically implements the probe calls to drivers? Another option is to probe the wired device first explicitly, and then skip it in the normal probe scan. In linux there is a clearly defined routine that does this, but i havent found it in freebsd yet. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 9:51:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r05.mx.aol.com (imo-r05.mx.aol.com [152.163.225.101]) by hub.freebsd.org (Postfix) with ESMTP id 47EFE37B408 for ; Sun, 9 Sep 2001 09:51:42 -0700 (PDT) Received: from Bsdguru@aol.com by imo-r05.mx.aol.com (mail_out_v31_r1.4.) id n.17.1b4a418c (4242) for ; Sun, 9 Sep 2001 12:51:39 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <17.1b4a418c.28ccf81a@aol.com> Date: Sun, 9 Sep 2001 12:51:38 EDT Subject: Re: PCI probe reordering? To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 9/9/01 12:45:06 PM Eastern Daylight Time, Bsdguru@aol.com writes: > Also, which routing specifically implements the probe calls to drivers? > Another option is to probe the wired device first explicitly, and then skip > > it in the normal probe scan. In linux there is a clearly defined routine > that does this, but i havent found it in freebsd yet. > > Bryan I meant "which routine" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 10:15:10 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 E87F337B408 for ; Sun, 9 Sep 2001 10:15:06 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f89HEsB21590; Sun, 9 Sep 2001 13:14:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 9 Sep 2001 13:14:53 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bsdguru@aol.com Cc: hackers@freebsd.org Subject: Re: PCI probe reordering? In-Reply-To: <146.146a821.28cc24bc@aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've actually noticed that the probe order in FreeBSD appears to have changed between RELENG_4 and -CURRENT. I likewise experienced it with on-board and external fxp chipsets, only in my case, the probe order for (fxp0, fxp1) switched with (fxp2, fxp3), as there were two on-MB and two on a card. Interestingly, our -CURRENT probe order is the same as that on OpenBSD. It's not clear what the "right" probe order is, but changing probe orders certainly is annoying during an upgrade :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sat, 8 Sep 2001 Bsdguru@aol.com wrote: > > I've encountered a MB that seems to probe devices in a less than desirable > order. There is an onboard fxp controller, but it scans the slots first, so > that the onboard controller is fxp1 if there is another intel card in the > box, for example. > > I want to make the onboard controller fxp0 (since most MBs probe that way and > it makes sense). Where would I have to hack to get Freebsd to probe slots in > reverse order? > > Thanks, > > bryan > > 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 Sun Sep 9 11:12: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2A81A37B401 for ; Sun, 9 Sep 2001 11:11:58 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id B2C2E81D05; Sun, 9 Sep 2001 13:11:52 -0500 (CDT) Date: Sun, 9 Sep 2001 13:11:52 -0500 From: Alfred Perlstein To: Ulf Zimmermann Cc: hackers@FreeBSD.org Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010909131152.L2965@elvis.mu.org> References: <20010909024721.B1500@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010909024721.B1500@seven.alameda.net>; from ulf@Alameda.net on Sun, Sep 09, 2001 at 02:47:21AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Ulf Zimmermann [010909 04:47] wrote: > Hello everyone. > > I am looking at some PRs and I am trying to come up with a solution to > submit a patch. I know how to use expr to test as tring in sh inside > of a /etc/rc* script, but what method would people recommend to remove > part of the string after expr confirmed that something is part of it ? > > These are some examples strings: > > "dhcp" > "dhcp media 10baseTX" > "media 10baseTX dhcp mediaopt half-duplex" > > The following code will get me inside a if condition: > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > .... > > fi > > What I would like to do inside the if .. fi is to remove "[Dd][Hh][Cc][Pp]" > from the string so that the rest of the options can be used to call ifconfig. > Otherwise the if .. fi will test if the string is then empty or just white > spaces and if so it will not do anything but set ${dhcp_interfaces}. If its > not empty it will call ifconfig with the extra options to set the interface. > > Awk/sed comes to mind but those are in /usr/bin and I am trying to avoid > that. > > Any suggestions from the more experienced hackers ? sed? :) sed 's/[Dd][Hh][Cc][Pp]//g' -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 13:38: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id 67F7337B409 for ; Sun, 9 Sep 2001 13:38:04 -0700 (PDT) Received: by seven.Alameda.net (Postfix, from userid 1000) id 41B923A23E; Sun, 9 Sep 2001 13:38:00 -0700 (PDT) Date: Sun, 9 Sep 2001 13:38:00 -0700 From: Ulf Zimmermann To: Alfred Perlstein Cc: Ulf Zimmermann , hackers@FreeBSD.org Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010909133800.C1500@seven.alameda.net> Reply-To: ulf@Alameda.net References: <20010909024721.B1500@seven.alameda.net> <20010909131152.L2965@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010909131152.L2965@elvis.mu.org>; from bright@mu.org on Sun, Sep 09, 2001 at 01:11:52PM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.3-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 09, 2001 at 01:11:52PM -0500, Alfred Perlstein wrote: > * Ulf Zimmermann [010909 04:47] wrote: > > Hello everyone. > > > > I am looking at some PRs and I am trying to come up with a solution to > > submit a patch. I know how to use expr to test as tring in sh inside > > of a /etc/rc* script, but what method would people recommend to remove > > part of the string after expr confirmed that something is part of it ? > > > > These are some examples strings: > > > > "dhcp" > > "dhcp media 10baseTX" > > "media 10baseTX dhcp mediaopt half-duplex" > > > > The following code will get me inside a if condition: > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > .... > > > > fi > > > > What I would like to do inside the if .. fi is to remove "[Dd][Hh][Cc][Pp]" > > from the string so that the rest of the options can be used to call ifconfig. > > Otherwise the if .. fi will test if the string is then empty or just white > > spaces and if so it will not do anything but set ${dhcp_interfaces}. If its > > not empty it will call ifconfig with the extra options to set the interface. > > > > Awk/sed comes to mind but those are in /usr/bin and I am trying to avoid > > that. > > > > Any suggestions from the more experienced hackers ? > > sed? :) > > sed 's/[Dd][Hh][Cc][Pp]//g' > > -Alfred sed is in /usr/bin and so its not a too good idea to use it in a /etc/rc script. There is sed also in /stand, can that be used ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 13:52:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from infinitive.futureperfectcorporation.com (curie.sunesi.com [196.25.112.244]) by hub.freebsd.org (Postfix) with SMTP id B263337B406 for ; Sun, 9 Sep 2001 13:52:41 -0700 (PDT) Received: (qmail 6618 invoked by uid 0); 9 Sep 2001 20:52:39 -0000 Received: from choke.sunesi.net (HELO gerund.futureperfectcorporation.com) (196.25.112.242) by infinitive.futureperfectcorporation.com with SMTP; 9 Sep 2001 20:52:39 -0000 Received: (qmail 76438 invoked by uid 1001); 9 Sep 2001 20:53:16 -0000 Date: Sun, 9 Sep 2001 22:53:16 +0200 From: Neil Blakey-Milner To: Ulf Zimmermann Cc: Alfred Perlstein , hackers@FreeBSD.org Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010909225316.A76366@mithrandr.moria.org> References: <20010909024721.B1500@seven.alameda.net> <20010909131152.L2965@elvis.mu.org> <20010909133800.C1500@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010909133800.C1500@seven.alameda.net>; from ulf@Alameda.net on Sun, Sep 09, 2001 at 01:38:00PM -0700 Organization: iTouch Labs X-Operating-System: FreeBSD 4.3-RELEASE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun 2001-09-09 (13:38), Ulf Zimmermann wrote: > On Sun, Sep 09, 2001 at 01:11:52PM -0500, Alfred Perlstein wrote: > > * Ulf Zimmermann [010909 04:47] wrote: > > > Hello everyone. > > > > > > I am looking at some PRs and I am trying to come up with a solution to > > > submit a patch. I know how to use expr to test as tring in sh inside > > > of a /etc/rc* script, but what method would people recommend to remove > > > part of the string after expr confirmed that something is part of it ? > > > > > > These are some examples strings: > > > > > > "dhcp" > > > "dhcp media 10baseTX" > > > "media 10baseTX dhcp mediaopt half-duplex" > > > > > > The following code will get me inside a if condition: > > > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > > > .... > > > > > > fi > > > > > > What I would like to do inside the if .. fi is to remove "[Dd][Hh][Cc][Pp]" > > > from the string so that the rest of the options can be used to call ifconfig. > > > Otherwise the if .. fi will test if the string is then empty or just white > > > spaces and if so it will not do anything but set ${dhcp_interfaces}. If its > > > not empty it will call ifconfig with the extra options to set the interface. > > > > > > Awk/sed comes to mind but those are in /usr/bin and I am trying to avoid > > > that. > > > > > > Any suggestions from the more experienced hackers ? > > > > sed? :) > > > > sed 's/[Dd][Hh][Cc][Pp]//g' > > > > -Alfred > > sed is in /usr/bin and so its not a too good idea to use it in a /etc/rc > script. There is sed also in /stand, can that be used ? Nope, you can't. However, you might be able to do it all within sh, by using case and "Parameter Expansion" (see the section in the sh man page). Try this: case ${ifconfig_args} in *[Dd][Hh][Cc][Pp]*) # do stuff with whatever $ifconfig_args=${ifconfig_args%dhcp} ;; esac This probably won't work, since I've not tested it. Casedness is irritating too - dd.sh would advocate converting it all to lowercase with ``dd conv=lcase''. ;) 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 Sun Sep 9 13:53: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3.psconsult.nl (ps226.psconsult.nl [193.67.147.226]) by hub.freebsd.org (Postfix) with ESMTP id 1591337B40B for ; Sun, 9 Sep 2001 13:52:46 -0700 (PDT) Received: (from paul@localhost) by pop3.psconsult.nl (8.9.2/8.9.2) id WAA15367; Sun, 9 Sep 2001 22:52:22 +0200 (CEST) (envelope-from paul) Date: Sun, 9 Sep 2001 22:52:22 +0200 From: Paul Schenkeveld To: Ulf Zimmermann Cc: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010909225221.A15301@psconsult.nl> References: <20010909024721.B1500@seven.alameda.net> <20010909131152.L2965@elvis.mu.org> <20010909133800.C1500@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010909133800.C1500@seven.alameda.net>; from ulf@Alameda.net on Sun, Sep 09, 2001 at 01:38:00PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 09, 2001 at 01:38:00PM -0700, Ulf Zimmermann wrote: > On Sun, Sep 09, 2001 at 01:11:52PM -0500, Alfred Perlstein wrote: > > * Ulf Zimmermann [010909 04:47] wrote: > > > Hello everyone. > > > > > > I am looking at some PRs and I am trying to come up with a solution to > > > submit a patch. I know how to use expr to test as tring in sh inside > > > of a /etc/rc* script, but what method would people recommend to remove > > > part of the string after expr confirmed that something is part of it ? > > > > > > These are some examples strings: > > > > > > "dhcp" > > > "dhcp media 10baseTX" > > > "media 10baseTX dhcp mediaopt half-duplex" > > > > > > The following code will get me inside a if condition: > > > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > > > .... > > > > > > fi > > > > > > What I would like to do inside the if .. fi is to remove "[Dd][Hh][Cc][Pp]" > > > from the string so that the rest of the options can be used to call ifconfig. > > > Otherwise the if .. fi will test if the string is then empty or just white > > > spaces and if so it will not do anything but set ${dhcp_interfaces}. If its > > > not empty it will call ifconfig with the extra options to set the interface. > > > > > > Awk/sed comes to mind but those are in /usr/bin and I am trying to avoid > > > that. > > > > > > Any suggestions from the more experienced hackers ? > > > > sed? :) > > > > sed 's/[Dd][Hh][Cc][Pp]//g' > > > > -Alfred > > sed is in /usr/bin and so its not a too good idea to use it in a /etc/rc > script. There is sed also in /stand, can that be used ? Expr could do the trick: before=`expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp]\(.*\)'` behind=`expr "${ifconfig_args}" : '\(.*\)[Dd][Hh][Cc][Pp].*'` other_ifconfig_args="${before}${behind}" And expr is in /bin. My EUR 0.024 (~$0.02 :-) > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Paul Schenkeveld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 14:21:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id A5B3137B407 for ; Sun, 9 Sep 2001 14:21:34 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f89LSQh01403; Sun, 9 Sep 2001 14:28:26 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109092128.f89LSQh01403@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bsdguru@aol.com Cc: imp@harmony.village.org, hackers@freebsd.org Subject: Re: PCI probe reordering? In-reply-to: Your message of "Sun, 09 Sep 2001 12:44:19 EDT." <146.14cf6de.28ccf663@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Sep 2001 14:28:26 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Also, which routing specifically implements the probe calls to drivers? device_probe_and_attach > Another option is to probe the wired device first explicitly, and then skip > it in the normal probe scan. In linux there is a clearly defined routine > that does this, but i havent found it in freebsd yet. The entire PCI probe/attach process is going to have to change, however I don't see it changing all that much. It is hard to detect devices that are "onboard" as opposed to being in physical slots, and there is no consistent mechanism that one can take to always get them "first". In short, what you're asking for is difficult to achieve consistently, and not really worth the effort. Your onboard ethernet is fxp1. Deal with it. -- ... 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 Sun Sep 9 15: 6:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.65.55]) by hub.freebsd.org (Postfix) with ESMTP id 608B637B403 for ; Sun, 9 Sep 2001 15:06:05 -0700 (PDT) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.11.6/8.11.6) with ESMTP id f89M61k36100; Sun, 9 Sep 2001 18:06:01 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Sun, 9 Sep 2001 18:06:01 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Ulf Zimmermann Cc: Subject: Re: Question about what programs to use in /etc/rc* In-Reply-To: <20010909024721.B1500@seven.alameda.net> Message-ID: <20010909180325.T36056-100000@lorax.ubergeeks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 9 Sep 2001, Ulf Zimmermann wrote: > These are some examples strings: > > "dhcp" > "dhcp media 10baseTX" > "media 10baseTX dhcp mediaopt half-duplex" > > The following code will get me inside a if condition: > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > .... > > fi You do everything you need within sh. Someone else pointed out that case/esac is your friend here. It was not quite complete. Here's more complete example that will let you pair up the options and their arguments if they take them. ifconfig_args="media 10baseTX dhcp mediaopt half-duplex" set -- ${ifconfig_args} while [ $# -gt 0 ]; do op=$1 case ${op} in [Mm][Ee][Dd][Ii][Aa]) op_arg=$2 shift echo "op=media op_arg=${op_arg}" ;; [Mm][Ee][Dd][Ii][Aa][Oo][Pp][Tt]) op_arg=$2 shift echo "op=mediaopt op_arg=${op_arg}" ;; [Dd][Hh][Cc][Pp]) echo "do something dhcp specific..." ;; *) echo "unknown op: ${op}" ;; esac shift done cheers, Adrian -- [ adrian@ubergeeks.com ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 15:49:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id 231A037B406 for ; Sun, 9 Sep 2001 15:49:30 -0700 (PDT) Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16]) by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with ESMTP id f89MnRv06223 for ; Mon, 10 Sep 2001 00:49:28 +0200 (MEST) Received: from news.du.uab.ericsson.se (news [134.138.176.24]) by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id f89MnQ106694 for ; Mon, 10 Sep 2001 00:49:26 +0200 (MET DST) Received: (from news@localhost) by news.du.uab.ericsson.se (8.9.1b+Sun/8.9.1/news-1.1) id AAA14933 for freebsd-hackers@freebsd.org; Mon, 10 Sep 2001 00:49:26 +0200 (MET DST) Received: from GATEWAY by news with netnews for freebsd-hackers@freebsd.org (freebsd-hackers@freebsd.org) To: freebsd-hackers@freebsd.org Date: 10 Sep 2001 00:49:25 +0200 From: Kent Boortz Message-ID: Organization: Ericsson Utvecklings AB, Stockholm, Sweden Content-Type: text/plain; charset=us-ascii Subject: How to force small TCP packets? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I want to run an application with the OS set to send small TCP packets to spot programming errors like assuming that a write of 100 bytes on a socket can be read in a single read operation. It may work most of the time but break at some point. So if I could configure FreeBSD to use small packets I can spot these programming errors faster. How can I do this? I can't just set the MTU on the interface right? Can I use sysctl "net.inet.tcp.sendspace" or some other configuration? Can I set it as low as sending one byte of data in each packet? Will this still not help, i.e. if we are not reading fast enough we will get all 100 bytes we wrote in a single read even if the packets were small? Is there another way to force the behaviour that read() on a socket just return a few bytes at the time? Sorry if this is a stupid question, I haven't gone deep enough in Stevens "TCP/IP Illustrated" to understand things like this yet, kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 16:27:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5163237B403 for ; Sun, 9 Sep 2001 16:27:45 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 3A81D81D01; Sun, 9 Sep 2001 18:27:45 -0500 (CDT) Date: Sun, 9 Sep 2001 18:27:45 -0500 From: Alfred Perlstein To: Kent Boortz Cc: freebsd-hackers@freebsd.org Subject: Re: How to force small TCP packets? Message-ID: <20010909182745.O2965@elvis.mu.org> 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 kent@erix.ericsson.se on Mon, Sep 10, 2001 at 12:49:25AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kent Boortz [010909 17:49] wrote: > > I want to run an application with the OS set to send small TCP packets > to spot programming errors like assuming that a write of 100 bytes on > a socket can be read in a single read operation. It may work most of > the time but break at some point. So if I could configure FreeBSD to > use small packets I can spot these programming errors faster. > > How can I do this? I can't just set the MTU on the interface right? > Can I use sysctl "net.inet.tcp.sendspace" or some other configuration? > Can I set it as low as sending one byte of data in each packet? Will > this still not help, i.e. if we are not reading fast enough we will > get all 100 bytes we wrote in a single read even if the packets were > small? Is there another way to force the behaviour that read() on a > socket just return a few bytes at the time? > > Sorry if this is a stupid question, I haven't gone deep enough in > Stevens "TCP/IP Illustrated" to understand things like this yet, there's a setsockopt for this called TCP_NODELAY in netinet/tcp.h. you should read further into stevens before posting such questions. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 16:56:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36]) by hub.freebsd.org (Postfix) with ESMTP id D986B37B428; Sun, 9 Sep 2001 16:56:43 -0700 (PDT) Received: from Bsdguru@aol.com by imo-d04.mx.aol.com (mail_out_v31_r1.4.) id n.6f.1a7105ea (3972); Sun, 9 Sep 2001 19:56:39 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <6f.1a7105ea.28cd5bb7@aol.com> Date: Sun, 9 Sep 2001 19:56:39 EDT Subject: Re: PCI probe reordering? To: msmith@freebsd.org Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 9/9/01 5:21:51 PM Eastern Daylight Time, msmith@freebsd.org writes: > The entire PCI probe/attach process is going to have to change, however I > don't see it changing all that much. It is hard to detect devices that > are "onboard" as opposed to being in physical slots, and there is no > consistent mechanism that one can take to always get them "first". > > In short, what you're asking for is difficult to achieve consistently, > and not really worth the effort. Your onboard ethernet is fxp1. Deal > with it. > "Worth it" depends on what you care about, I suppose. But a commercial vendor, using freebsd as a platform, will "care" if one motherboard scans one way and another scans differently, as you cant tell customers "well, if you have this product the ports are this way, and if you have that product the ports are another way". While there may not be a generic way to always do it the way one expects, it doesnt seem unreasonable to have a mechanism to override the default probe that isnt a nightmare to implement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 19:10:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 2DC1837B407; Sun, 9 Sep 2001 19:10:17 -0700 (PDT) Received: from soekris.com (1.4.soekris.com [192.168.1.4] (may be forged)) by server.soekris.com (8.9.2/8.9.2) with ESMTP id TAA13231; Sun, 9 Sep 2001 19:10:20 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3B9C2102.4AC887E1@soekris.com> Date: Sun, 09 Sep 2001 19:10:10 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bsdguru@aol.com Cc: msmith@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: PCI probe reordering? References: <6f.1a7105ea.28cd5bb7@aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Aren't operating systems supposed to use the PCI BIOS calls for finding devices ? So the scanning order would then be controlled by the BIOS, and then always follow the intent of the hardware manufacturer ? Or is there problems with their intent ? Regards, Soren Bsdguru@aol.com wrote: > > In a message dated 9/9/01 5:21:51 PM Eastern Daylight Time, > msmith@freebsd.org writes: > > > The entire PCI probe/attach process is going to have to change, however I > > don't see it changing all that much. It is hard to detect devices that > > are "onboard" as opposed to being in physical slots, and there is no > > consistent mechanism that one can take to always get them "first". > > > > In short, what you're asking for is difficult to achieve consistently, > > and not really worth the effort. Your onboard ethernet is fxp1. Deal > > with it. > > > > "Worth it" depends on what you care about, I suppose. But a commercial > vendor, using freebsd as a platform, will "care" if one motherboard scans one > way and another scans differently, as you cant tell customers "well, if you > have this product the ports are this way, and if you have that product the > ports are another way". While there may not be a generic way to always do it > the way one expects, it doesnt seem unreasonable to have a mechanism to > override the default probe that isnt a nightmare to implement. > > 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 Sun Sep 9 21: 5:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (spoon.beta.com [199.165.180.1]) by hub.freebsd.org (Postfix) with ESMTP id CF79637B403; Sun, 9 Sep 2001 21:05:11 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.11.3/8.11.3) with ESMTP id f8A45Bs00710; Mon, 10 Sep 2001 00:05:11 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200109100405.f8A45Bs00710@spoon.beta.com> To: freebsd-qa@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Anyone interested in working on a test harness? Date: Mon, 10 Sep 2001 00:05:11 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have just freed up my last 'committed' project, and I've got some spare cycles to burn. I've been thinking about how much goes untested in a release, and have been thinking about how to put together a test harness to check as many things as possible. Thats got me thinking (again) about a test harness, and a test plan. I'm thinking that the harness can be fairly simple, basically a configuration engine to run external binaries, and basically keep a running tally of passed, failed, skipped, and 'warning' tests. The test themselves would perform some little bit of work, and spew back an exit code that would put the test in to one of the four above bins. I'm thinking code for things like filesystems (reading/writing), mmap, basic networking (tcp/udp, IPv4 + 6), etc. would base a good base set. If there was a good tool for thrashing disks, for instance, it could be used in multiple ways... regular UFS, soft updates, vinum volumes, etc. The test plan could then basically describe how to set up a 'test system', and run the various tests on it. People lacking hardware could run a subset of the tests that were appropriate. Anyhow, I'm looking for anyone who would be willing to do some work in this area. Obviously, as I'm starting, its pretty open right now to suggestions/help. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 21:23:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jordan.llnl.gov (jordan.llnl.gov [128.115.36.14]) by hub.freebsd.org (Postfix) with ESMTP id 957AF37B401 for ; Sun, 9 Sep 2001 21:23:37 -0700 (PDT) Received: (from wea@localhost) by jordan.llnl.gov (8.11.4/8.11.4) id f8A4MKC04388; Sun, 9 Sep 2001 21:22:20 -0700 (PDT) Date: Sun, 9 Sep 2001 21:22:20 -0700 (PDT) From: Ed Alley Message-Id: <200109100422.f8A4MKC04388@jordan.llnl.gov> To: fmela0@sm.socccd.cc.ca.us Subject: Re: Failure to fixate cd in burncd Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ---On Sun, 09 Sep 2001 Farooq Mela >Subject: Failure to fixate cd in burncd > ... Any thoughts? Not knowing what CDR you are using makes your problem difficult to analyze. Each IDE CDR behaves differently. Check out Soren Schmidt's page: http://freebsd.dk/ata He gives a list of ATAPI CDR/RW drives that work so far. Also, I know that he is constantly working on the ATAPI driver as new drivers come on the market. Also, it is known that the CD makers play with the protocol a little; thus, he must sometimes relax the driver a bit to accomodate new hardware. If you have any detailed fixes like the patch you included, then you should either discusses it with him or submit a problem report. Look at the man page send-pr(1). Ed wea@llnl.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 22:14:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) by hub.freebsd.org (Postfix) with ESMTP id 09AAE37B405 for ; Sun, 9 Sep 2001 22:14:37 -0700 (PDT) Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16]) by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id f8A5EYK11881 for ; Mon, 10 Sep 2001 07:14:35 +0200 (MEST) Received: from news.du.uab.ericsson.se (news [134.138.176.24]) by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id f8A5EY110869 for ; Mon, 10 Sep 2001 07:14:34 +0200 (MET DST) Received: (from news@localhost) by news.du.uab.ericsson.se (8.9.1b+Sun/8.9.1/news-1.1) id HAA21795 for freebsd-hackers@freebsd.org; Mon, 10 Sep 2001 07:14:33 +0200 (MET DST) Received: from GATEWAY by news with netnews for freebsd-hackers@freebsd.org (freebsd-hackers@freebsd.org) To: freebsd-hackers@freebsd.org Date: 10 Sep 2001 07:14:33 +0200 From: Kent Boortz Message-ID: Organization: Ericsson Utvecklings AB, Stockholm, Sweden Content-Type: text/plain; charset=us-ascii References: , <20010909182745.O2965@elvis.mu.org> Subject: Re: How to force small TCP packets? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bright@mu.org (Alfred Perlstein) writes: > there's a setsockopt for this called TCP_NODELAY in netinet/tcp.h. > > you should read further into stevens before posting such questions. I seem to have expressed myself really bad :-( I want to debug an application. We have had code that broke only occasionally on a specific Linux version under heavy load. I want to detect bad code like that and had hoped that some FreeBSD hackers had some tricks how to use kernel configuration to do that. If application A do a write like write(socket, buf, 100); and application B read this like read(socket, buf, 100); without checking the result from the read operation, then this code will probably work 99.9999% of the time. But if I could force the kernel to pass data from a socket on to the application say one byte at the time then this code will break 100% of the time. This makes finding these problems more easy. This is highly simplified example, else I could just grep the sources for all calls to read() and manually inspect the code. The data is passed on to other parts of the system using message queues. But using the kernel to debug user applications like this was probably a stupid idea. I'm sorry for posting a question to this group without the proper knowledge wasting your time, kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 9 22:31:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 90C2A37B405; Sun, 9 Sep 2001 22:31:54 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8A5Vq604442; Sun, 9 Sep 2001 23:31:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8A5Vqt13429; Sun, 9 Sep 2001 23:31:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109100531.f8A5Vqt13429@harmony.village.org> To: Soren Kristensen Subject: Re: PCI probe reordering? Cc: Bsdguru@aol.com, msmith@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 09 Sep 2001 19:10:10 PDT." <3B9C2102.4AC887E1@soekris.com> References: <3B9C2102.4AC887E1@soekris.com> <6f.1a7105ea.28cd5bb7@aol.com> Date: Sun, 09 Sep 2001 23:31:52 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B9C2102.4AC887E1@soekris.com> Soren Kristensen writes: : Aren't operating systems supposed to use the PCI BIOS calls for finding : devices ? So the scanning order would then be controlled by the BIOS, : and then always follow the intent of the hardware manufacturer ? Or is : there problems with their intent ? Too bad the PCI BIOS sucks *WAY* too bad to use it for these things. The recent fiasco in the MFC of the PCI BIOS stuff shows this *WAY* to clearly. Otherwise, it is another of those great theories that are shot to hell with the facts. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 1: 6:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id 2FBBD37B408 for ; Mon, 10 Sep 2001 01:06:03 -0700 (PDT) Received: (qmail 2946 invoked by uid 1000); 10 Sep 2001 08:05:37 -0000 Date: Mon, 10 Sep 2001 11:05:37 +0300 From: Peter Pentchev To: Adrian Filipi-Martin Cc: Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010910110537.A2053@ringworld.oblivion.bg> Mail-Followup-To: Adrian Filipi-Martin , Ulf Zimmermann , hackers@FreeBSD.ORG References: <20010909024721.B1500@seven.alameda.net> <20010909180325.T36056-100000@lorax.ubergeeks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010909180325.T36056-100000@lorax.ubergeeks.com>; from adrian@ubergeeks.com on Sun, Sep 09, 2001 at 06:06:01PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 09, 2001 at 06:06:01PM -0400, Adrian Filipi-Martin wrote: > On Sun, 9 Sep 2001, Ulf Zimmermann wrote: > > > These are some examples strings: > > > > "dhcp" > > "dhcp media 10baseTX" > > "media 10baseTX dhcp mediaopt half-duplex" > > > > The following code will get me inside a if condition: > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > .... > > > > fi > > You do everything you need within sh. Someone else pointed out > that case/esac is your friend here. It was not quite complete. Here's > more complete example that will let you pair up the options and their > arguments if they take them. > > ifconfig_args="media 10baseTX dhcp mediaopt half-duplex" > set -- ${ifconfig_args} > while [ $# -gt 0 ]; do > op=$1 > case ${op} in > [Mm][Ee][Dd][Ii][Aa]) > op_arg=$2 > shift > echo "op=media op_arg=${op_arg}" > ;; I don't like this. This second-guessing of ifconfig(8)'s arguments is prone to error - consider the case of a new keyword added to ifconfig(8).. And blindly discarding unrecognized keyword would not really work either - a new keyword might take an argument, the shell script has no way of knowing that, so it would skip the keyword and try to look at its argument as another keyword; what if a keyword takes a string argument of, oh, say, 'dhcp'? :) A ${args#dhcp} might work better, but there is a problem with it - the # match is case-sensitive, and I *know* that there are people using 'dhcp' and people using 'DHCP' :) G'luck, Peter -- This would easier understand fewer had omitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 6:17:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id AD7EB37B405 for ; Mon, 10 Sep 2001 06:17:28 -0700 (PDT) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA34818; Mon, 10 Sep 2001 15:17:24 +0200 (CEST) (envelope-from assar) To: Kent Boortz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to force small TCP packets? References: <20010909182745.O2965@elvis.mu.org> From: Assar Westerlund Date: 10 Sep 2001 15:17:23 +0200 In-Reply-To: Kent Boortz's message of "10 Sep 2001 07:14:33 +0200" Message-ID: <5lelpfmbh8.fsf@assaris.sics.se> Lines: 23 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Boortz writes: > If application A do a write like > > write(socket, buf, 100); > > and application B read this like > > read(socket, buf, 100); > > without checking the result from the read operation, then this code > will probably work 99.9999% of the time. But if I could force the > kernel to pass data from a socket on to the application say one byte > at the time then this code will break 100% of the time. This makes > finding these problems more easy. Cannot you implement a shared library that you give to the applications that you want to test with your own version of read() that calls the real system call with different values of nbytes depending on your testing policy? You might want to hook socket too so that you know which fd:s are sockets (or you can probably call getsockname/getpeername on them). /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 8: 4: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.65.55]) by hub.freebsd.org (Postfix) with ESMTP id 5CFE637B40D for ; Mon, 10 Sep 2001 08:04:04 -0700 (PDT) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.11.6/8.11.6) with ESMTP id f8AF3fv37899; Mon, 10 Sep 2001 11:03:44 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Mon, 10 Sep 2001 11:03:41 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Peter Pentchev Cc: Ulf Zimmermann , Subject: Re: Question about what programs to use in /etc/rc* In-Reply-To: <20010910110537.A2053@ringworld.oblivion.bg> Message-ID: <20010910102943.N36056-100000@lorax.ubergeeks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Sep 2001, Peter Pentchev wrote: > On Sun, Sep 09, 2001 at 06:06:01PM -0400, Adrian Filipi-Martin wrote: > > On Sun, 9 Sep 2001, Ulf Zimmermann wrote: > > > > > These are some examples strings: > > > > > > "dhcp" > > > "dhcp media 10baseTX" > > > "media 10baseTX dhcp mediaopt half-duplex" > > > > > > The following code will get me inside a if condition: > > > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > > > .... > > > > > > fi > > > > You do everything you need within sh. Someone else pointed out > > that case/esac is your friend here. It was not quite complete. Here's > > more complete example that will let you pair up the options and their > > arguments if they take them. > > > > ifconfig_args="media 10baseTX dhcp mediaopt half-duplex" > > set -- ${ifconfig_args} > > while [ $# -gt 0 ]; do > > op=$1 > > case ${op} in > > [Mm][Ee][Dd][Ii][Aa]) > > op_arg=$2 > > shift > > echo "op=media op_arg=${op_arg}" > > ;; > > I don't like this. This second-guessing of ifconfig(8)'s arguments > is prone to error - consider the case of a new keyword added to > ifconfig(8).. And blindly discarding unrecognized keyword would > not really work either - a new keyword might take an argument, > the shell script has no way of knowing that, so it would skip > the keyword and try to look at its argument as another keyword; > what if a keyword takes a string argument of, oh, say, 'dhcp'? :) Sorry, but my example was meant to be more featureful than necessary and let you strip it down, sinice you needs wern't completely clear. If you just want to test for a substring, try this instead: case "${ifconfig_args}" in *[Dd][Hh][Cc][Pp]*) echo "we are using dhcp..." ;; esac > > A ${args#dhcp} might work better, but there is a problem with it - The pattern after the # is a regular glob pattern. You can use ${args#[Dd][Hh][Cc][Pp]} to deal with case. You probably really meant to say '${args##*[Dd][Hh][Cc][Pp]*}' which will collapse to a null string if 'dhcp' is in the string, or the string is empty to begin with. With only a single # and no *'s, you will not modify the string unless it is exactly "dhcp". Sill I don't recommend this approach, since you need to test the string twice, once before and once after the expansion. The case/esac idiom is pretty common as well. Adrian -- [ adrian@ubergeeks.com ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 8:20:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id A9E2337B401 for ; Mon, 10 Sep 2001 08:20:22 -0700 (PDT) Received: (qmail 3281 invoked by uid 1000); 10 Sep 2001 15:19:54 -0000 Date: Mon, 10 Sep 2001 18:19:54 +0300 From: Peter Pentchev To: Adrian Filipi-Martin Cc: Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010910181954.G1983@ringworld.oblivion.bg> Mail-Followup-To: Adrian Filipi-Martin , Ulf Zimmermann , hackers@FreeBSD.ORG References: <20010910110537.A2053@ringworld.oblivion.bg> <20010910102943.N36056-100000@lorax.ubergeeks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010910102943.N36056-100000@lorax.ubergeeks.com>; from adrian@ubergeeks.com on Mon, Sep 10, 2001 at 11:03:41AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 10, 2001 at 11:03:41AM -0400, Adrian Filipi-Martin wrote: > On Mon, 10 Sep 2001, Peter Pentchev wrote: > > > On Sun, Sep 09, 2001 at 06:06:01PM -0400, Adrian Filipi-Martin wrote: > > > On Sun, 9 Sep 2001, Ulf Zimmermann wrote: > > > > > > > These are some examples strings: > > > > > > > > "dhcp" > > > > "dhcp media 10baseTX" > > > > "media 10baseTX dhcp mediaopt half-duplex" > > > > > > > > The following code will get me inside a if condition: > > > > > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > > > > > .... > > > > > > > > fi > > > > > > You do everything you need within sh. Someone else pointed out > > > that case/esac is your friend here. It was not quite complete. Here's > > > more complete example that will let you pair up the options and their > > > arguments if they take them. > > > > > > ifconfig_args="media 10baseTX dhcp mediaopt half-duplex" > > > set -- ${ifconfig_args} > > > while [ $# -gt 0 ]; do > > > op=$1 > > > case ${op} in > > > [Mm][Ee][Dd][Ii][Aa]) > > > op_arg=$2 > > > shift > > > echo "op=media op_arg=${op_arg}" > > > ;; > > > > I don't like this. This second-guessing of ifconfig(8)'s arguments > > is prone to error - consider the case of a new keyword added to > > ifconfig(8).. And blindly discarding unrecognized keyword would > > not really work either - a new keyword might take an argument, > > the shell script has no way of knowing that, so it would skip > > the keyword and try to look at its argument as another keyword; > > what if a keyword takes a string argument of, oh, say, 'dhcp'? :) > > Sorry, but my example was meant to be more featureful than > necessary and let you strip it down, sinice you needs wern't completely > clear. If you just want to test for a substring, try this instead: > > case "${ifconfig_args}" in > *[Dd][Hh][Cc][Pp]*) > echo "we are using dhcp..." > ;; > esac > > > > > > A ${args#dhcp} might work better, but there is a problem with it - > > The pattern after the # is a regular glob pattern. You can use > ${args#[Dd][Hh][Cc][Pp]} to deal with case. > > You probably really meant to say '${args##*[Dd][Hh][Cc][Pp]*}' > which will collapse to a null string if 'dhcp' is in the string, or the > string is empty to begin with. With only a single # and no *'s, you will > not modify the string unless it is exactly "dhcp". > > Sill I don't recommend this approach, since you need to test the > string twice, once before and once after the expansion. The case/esac > idiom is pretty common as well. I think that the original poster is interested in first testing for 'dhcp' in the string, and then removing it - the original post mentioned a PR sweep, and I really think he means PR 30441. To correctly process an ifconfig_rl0="dhcp media 10baseT/UTP", you'd first have to match it against [Dd][Hh][Cc][Pp], and then remove the 'dhcp' part to get the real arguments to add to the ifconfig line. Come to think of it, it might be as easy as: [**UNTESTED**] case ${ifconfig_args}; in [Dd][Hh][Cc][Pp]*) set $ifconfig_args shift ifconfig_add_args="$*" ...... ..provided there is a requirement that the ifconfig_args should *start* with 'dhcp' (which would be easy enough to meet - right now, the args have to *be* 'dhcp', so any additional arguments would be stapled on at the end). G'luck, Peter -- If wishes were fishes, the antecedent of this conditional would be true. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 9:35:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id 67FDC37B408 for ; Mon, 10 Sep 2001 09:35:24 -0700 (PDT) Received: by seven.Alameda.net (Postfix, from userid 1000) id 3801C3A212; Mon, 10 Sep 2001 09:35:24 -0700 (PDT) Date: Mon, 10 Sep 2001 09:35:24 -0700 From: Ulf Zimmermann To: Adrian Filipi-Martin , Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010910093524.D1500@seven.alameda.net> Reply-To: ulf@Alameda.net References: <20010910110537.A2053@ringworld.oblivion.bg> <20010910102943.N36056-100000@lorax.ubergeeks.com> <20010910181954.G1983@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010910181954.G1983@ringworld.oblivion.bg>; from roam@ringlet.net on Mon, Sep 10, 2001 at 06:19:54PM +0300 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.3-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 10, 2001 at 06:19:54PM +0300, Peter Pentchev wrote: > On Mon, Sep 10, 2001 at 11:03:41AM -0400, Adrian Filipi-Martin wrote: > > On Mon, 10 Sep 2001, Peter Pentchev wrote: > > > > > On Sun, Sep 09, 2001 at 06:06:01PM -0400, Adrian Filipi-Martin wrote: > > > > On Sun, 9 Sep 2001, Ulf Zimmermann wrote: > > > > > > > > > These are some examples strings: > > > > > > > > > > "dhcp" > > > > > "dhcp media 10baseTX" > > > > > "media 10baseTX dhcp mediaopt half-duplex" > > > > > > > > > > The following code will get me inside a if condition: > > > > > > > > > > if [ `expr "${ifconfig_args}" : '.*[Dd][Hh][Cc][Pp].*'` -ne 0 ]; then > > > > > > > > > > .... > > > > > > > > > > fi > > > > > > > > You do everything you need within sh. Someone else pointed out > > > > that case/esac is your friend here. It was not quite complete. Here's > > > > more complete example that will let you pair up the options and their > > > > arguments if they take them. > > > > > > > > ifconfig_args="media 10baseTX dhcp mediaopt half-duplex" > > > > set -- ${ifconfig_args} > > > > while [ $# -gt 0 ]; do > > > > op=$1 > > > > case ${op} in > > > > [Mm][Ee][Dd][Ii][Aa]) > > > > op_arg=$2 > > > > shift > > > > echo "op=media op_arg=${op_arg}" > > > > ;; > > > > > > I don't like this. This second-guessing of ifconfig(8)'s arguments > > > is prone to error - consider the case of a new keyword added to > > > ifconfig(8).. And blindly discarding unrecognized keyword would > > > not really work either - a new keyword might take an argument, > > > the shell script has no way of knowing that, so it would skip > > > the keyword and try to look at its argument as another keyword; > > > what if a keyword takes a string argument of, oh, say, 'dhcp'? :) > > > > Sorry, but my example was meant to be more featureful than > > necessary and let you strip it down, sinice you needs wern't completely > > clear. If you just want to test for a substring, try this instead: > > > > case "${ifconfig_args}" in > > *[Dd][Hh][Cc][Pp]*) > > echo "we are using dhcp..." > > ;; > > esac > > > > > > > > > > A ${args#dhcp} might work better, but there is a problem with it - > > > > The pattern after the # is a regular glob pattern. You can use > > ${args#[Dd][Hh][Cc][Pp]} to deal with case. > > > > You probably really meant to say '${args##*[Dd][Hh][Cc][Pp]*}' > > which will collapse to a null string if 'dhcp' is in the string, or the > > string is empty to begin with. With only a single # and no *'s, you will > > not modify the string unless it is exactly "dhcp". > > > > Sill I don't recommend this approach, since you need to test the > > string twice, once before and once after the expansion. The case/esac > > idiom is pretty common as well. > > I think that the original poster is interested in first testing for > 'dhcp' in the string, and then removing it - the original post mentioned > a PR sweep, and I really think he means PR 30441. To correctly process > an ifconfig_rl0="dhcp media 10baseT/UTP", you'd first have to match > it against [Dd][Hh][Cc][Pp], and then remove the 'dhcp' part to get > the real arguments to add to the ifconfig line. > > Come to think of it, it might be as easy as: [**UNTESTED**] > > case ${ifconfig_args}; in > [Dd][Hh][Cc][Pp]*) > set $ifconfig_args > shift > ifconfig_add_args="$*" > ...... > > ..provided there is a requirement that the ifconfig_args should *start* > with 'dhcp' (which would be easy enough to meet - right now, the args > have to *be* 'dhcp', so any additional arguments would be stapled on at > the end). This sounds as the best solution. This would allow to set an interface to be DHCP (variable dhcp_interfaces get set) and take the rest of the arguments (like media/mediaopt) and apply them to the interface before the dhclient gets started. > > G'luck, > Peter > > -- > If wishes were fishes, the antecedent of this conditional would be true. > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 10: 0:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id 69FD737B405 for ; Mon, 10 Sep 2001 09:56:34 -0700 (PDT) Received: (qmail 4981 invoked by uid 1000); 10 Sep 2001 16:51:52 -0000 Date: Mon, 10 Sep 2001 19:51:52 +0300 From: Peter Pentchev To: Ulf Zimmermann Cc: Adrian Filipi-Martin , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010910195152.H1983@ringworld.oblivion.bg> Mail-Followup-To: Ulf Zimmermann , Adrian Filipi-Martin , hackers@FreeBSD.ORG References: <20010910110537.A2053@ringworld.oblivion.bg> <20010910102943.N36056-100000@lorax.ubergeeks.com> <20010910181954.G1983@ringworld.oblivion.bg> <20010910093524.D1500@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010910093524.D1500@seven.alameda.net>; from ulf@Alameda.net on Mon, Sep 10, 2001 at 09:35:24AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 10, 2001 at 09:35:24AM -0700, Ulf Zimmermann wrote: > On Mon, Sep 10, 2001 at 06:19:54PM +0300, Peter Pentchev wrote: > > Come to think of it, it might be as easy as: [**UNTESTED**] > > > > case ${ifconfig_args}; in > > [Dd][Hh][Cc][Pp]*) > > set $ifconfig_args > > shift > > ifconfig_add_args="$*" > > ...... > > > > ..provided there is a requirement that the ifconfig_args should *start* > > with 'dhcp' (which would be easy enough to meet - right now, the args > > have to *be* 'dhcp', so any additional arguments would be stapled on at > > the end). > > This sounds as the best solution. This would allow to set an interface > to be DHCP (variable dhcp_interfaces get set) and take the rest of the > arguments (like media/mediaopt) and apply them to the interface before > the dhclient gets started. If you decide to do it this way, make sure you do not make the same mistake I did - "set $ifconfig_args" is *very* much unsafe; better try "set -- $ifconfig_args", as in Adrian's message to which I repled :) G'luck, Peter -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 10:11:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gigi.excite.com (gigi.excite.com [199.172.152.110]) by hub.freebsd.org (Postfix) with ESMTP id 6A61237B409; Mon, 10 Sep 2001 10:11:35 -0700 (PDT) Received: from roary.excite.com ([199.172.148.162]) by gigi.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010910171135.JJIW11972.gigi.excite.com@roary.excite.com>; Mon, 10 Sep 2001 10:11:35 -0700 Message-ID: <8846549.1000141895110.JavaMail.imail@roary.excite.com> Date: Mon, 10 Sep 2001 10:11:28 -0700 (PDT) From: john_wilson100@excite.com To: freebsd-hackers@freebsd.org Subject: HPT370 RAID or Vinum? Cc: sos@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, I am trying to install FreeBSD on a (pseudo-) hardware ATA RAID volume which consists of two striped ATA disks connected to a Highpoint HPT370 controller. "Pseudo-" because FreeBSD detects the individual disks (ad4/ad6) as well as the striped volume (ar0). Besides the fact that ar0 isn't documented anywhere (except in /dev/MAKEDEV) and "man 4 ar" gives something completely irrelevant, which one is better to use: Highpoint built-in RAID (ar0), or ad4/ad6 striped with Vinum? I reckon if the RAID functions are implemented in HPT BIOS (in software), I'll be better off with Vinum. What do you guys think? 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 Mon Sep 10 10:13: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 031E937B40A for ; Mon, 10 Sep 2001 10:12:59 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8AHCdl04449; Mon, 10 Sep 2001 10:12:39 -0700 Date: Mon, 10 Sep 2001 10:12:39 -0700 From: Brooks Davis To: Ulf Zimmermann Cc: Adrian Filipi-Martin , hackers@FreeBSD.ORG Subject: Re: Question about what programs to use in /etc/rc* Message-ID: <20010910101239.A28442@Odin.AC.HMC.Edu> References: <20010910110537.A2053@ringworld.oblivion.bg> <20010910102943.N36056-100000@lorax.ubergeeks.com> <20010910181954.G1983@ringworld.oblivion.bg> <20010910093524.D1500@seven.alameda.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010910093524.D1500@seven.alameda.net>; from ulf@Alameda.net on Mon, Sep 10, 2001 at 09:35:24AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 10, 2001 at 09:35:24AM -0700, Ulf Zimmermann wrote: > > Come to think of it, it might be as easy as: [**UNTESTED**] > >=20 > > case ${ifconfig_args}; in > > [Dd][Hh][Cc][Pp]*) > > set $ifconfig_args > > shift > > ifconfig_add_args=3D"$*" > > ...... > >=20 > > ..provided there is a requirement that the ifconfig_args should *start* > > with 'dhcp' (which would be easy enough to meet - right now, the args > > have to *be* 'dhcp', so any additional arguments would be stapled on at > > the end). >=20 > This sounds as the best solution. This would allow to set an interface > to be DHCP (variable dhcp_interfaces get set) and take the rest of the > arguments (like media/mediaopt) and apply them to the interface before > the dhclient gets started. If you want to go this route, make dhcp be the last argument not the first one. If ifconfig understood dhcp (on my todo list) it would have to be the last argument if you wanted it to work reliably because args are processed in order and if your interface requires that you set the media before it works, it's not going to work very well to run dhcp and then fix the media. At least making dhcp be last insures that it will continue to work once ifconfig grows dhcp support[*]. -- Brooks [*] No ifconfig will not contain any DHCP code, it will simply call a script which calls your choice of dhcp clients. It's just lame that we have variables that are supposidly ifconfig commands, but which won't actually work. --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7nPSHXY6L6fI4GtQRAsqaAKDM51Tb5uwypJXtYwQ3E/eLURY9CgCgq7mw rxlYBzw+ssuSkLV3ixw0VUo= =BAjt -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 11: 4:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 24EF737B403; Mon, 10 Sep 2001 11:04:53 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f8AI5GU53003; Mon, 10 Sep 2001 20:05:16 +0200 (CEST) (envelope-from sos) From: SЬren Schmidt Message-Id: <200109101805.f8AI5GU53003@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <8846549.1000141895110.JavaMail.imail@roary.excite.com> "from john_wilson100@excite.com at Sep 10, 2001 10:11:28 am" To: john_wilson100@excite.com Date: Mon, 10 Sep 2001 20:05:05 +0200 (CEST) Cc: freebsd-hackers@freebsd.org, sos@freebsd.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems john_wilson100@excite.com wrote: > Hi there, > > I am trying to install FreeBSD on a (pseudo-) hardware ATA RAID volume which > consists of two striped ATA disks connected to a Highpoint HPT370 > controller. "Pseudo-" because FreeBSD detects the individual disks > (ad4/ad6) as well as the striped volume (ar0). Uhm, if a RAID array is foundm you cannot access the individual disks, the driver does not allow for that. > > Highpoint built-in RAID (ar0), or ad4/ad6 striped with Vinum? > > I reckon if the RAID functions are implemented in HPT BIOS (in software), > I'll be better off with Vinum. The RAID code is implemented in the ATA driver (ata-raid.c) and tbat takes over from the BIOS as soon as we are airborne (the BIOS is only needed and used for booting). However, there is no way to rebuild the ATA RAID from FreeBSD (that may soon change though) you have to use the BIOS for that... -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 11: 5:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.redstar.spb.ru (relay.redstar.spb.ru [195.131.87.225]) by hub.freebsd.org (Postfix) with ESMTP id DC75137B403 for ; Mon, 10 Sep 2001 11:05:55 -0700 (PDT) Received: from dmitry (dimon.redstar.spb.ru [192.168.120.5]) by relay.redstar.spb.ru (8.11.6/8.11.1) with ESMTP id f8AI9Pw32060 for ; Mon, 10 Sep 2001 22:09:26 +0400 (MSD) (envelope-from dss2001@redstar.spb.ru) Date: Mon, 10 Sep 2001 22:07:24 +0400 From: Dmitry Shubin X-Mailer: The Bat! (v1.44) Educational Reply-To: Dmitry Shubin Organization: RedStar Software X-Priority: 3 (Normal) Message-ID: <4115944917.20010910220724@redstar.spb.ru> To: freebsd-hackers@FreeBSD.ORG Subject: Some problems with CVSup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello freebsd-hackers, I have some troubles with CVSup. I want to get FreeBSD 4.3-STABLE. So I use such cvsupfile: *default host=cvsup.fi.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix src-all ports-all doc-all After that I used /usr/local/bin/cvsup -g -L 2 -z /etc/cvsupfile than make world, mergemaster, recompiling kernel and so on as usual. And after rebooting I saw, that system became not STABLE, but 4.4-RC!!! Can't you tell me, what's wrong? I think that there are mistake in cvsupfile, but where? -- With Best regards, Dmitry Shubin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 11:17:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8E49F37B401 for ; Mon, 10 Sep 2001 11:17:21 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8AIH7t11927; Mon, 10 Sep 2001 13:17:07 -0500 (CDT) (envelope-from jlemon) Date: Mon, 10 Sep 2001 13:17:07 -0500 (CDT) From: Jonathan Lemon Message-Id: <200109101817.f8AIH7t11927@prism.flugsvamp.com> To: kent@erix.ericsson.se, hackers@freebsd.org Subject: Re: How to force small TCP packets? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: , Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: > >bright@mu.org (Alfred Perlstein) writes: >> there's a setsockopt for this called TCP_NODELAY in netinet/tcp.h. >> >> you should read further into stevens before posting such questions. > >I seem to have expressed myself really bad :-( I want to debug an >application. We have had code that broke only occasionally on a >specific Linux version under heavy load. I want to detect bad code >like that and had hoped that some FreeBSD hackers had some tricks how >to use kernel configuration to do that. > >If application A do a write like > > write(socket, buf, 100); > >and application B read this like > > read(socket, buf, 100); > >without checking the result from the read operation, then this code >will probably work 99.9999% of the time. But if I could force the >kernel to pass data from a socket on to the application say one byte >at the time then this code will break 100% of the time. This makes >finding these problems more easy. > >This is highly simplified example, else I could just grep the sources >for all calls to read() and manually inspect the code. The data is >passed on to other parts of the system using message queues. > >But using the kernel to debug user applications like this was probably >a stupid idea. I'm sorry for posting a question to this group without >the proper knowledge wasting your time, One thing you might want to try doing is to write your own read() function and link against that. Your modified version could then replace the nbytes value with something smaller, for debugging purposes. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 11:25:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5CABD37B406 for ; Mon, 10 Sep 2001 11:25:18 -0700 (PDT) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15gVkB-00042v-00; Mon, 10 Sep 2001 19:25:15 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.6/8.11.4) id f8AIPM795187; Mon, 10 Sep 2001 19:25:22 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Mon, 10 Sep 2001 19:25:22 +0100 From: Ben Smithurst To: Dmitry Shubin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Some problems with CVSup Message-ID: <20010910192522.A80531@strontium.shef.vinosystems.com> References: <4115944917.20010910220724@redstar.spb.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4115944917.20010910220724@redstar.spb.ru> X-PGP-Key: http://www.smithurst.org/ben/pgp-key.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dmitry Shubin wrote: > And after rebooting I saw, that system became not STABLE, but > 4.4-RC!!! http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RELEASE-CAN= DIDATE --=20 Ben Smithurst / ben@FreeBSD.org FreeBSD: The Power To Serve http://www.FreeBSD.org/ --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7nQWRbPzJ+yzvRCwRAppTAJ0fetH7sZKOFE+80kGFiaCdmznYLACghtbk dCSoRtwlZcv+QPNDLeeIIxM= =Dd27 -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 11:28:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 0A6C037B407 for ; Mon, 10 Sep 2001 11:28:25 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA18026; Mon, 10 Sep 2001 11:27:45 -0700 (PDT) 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: <20010910101239.A28442@Odin.AC.HMC.Edu> Date: Mon, 10 Sep 2001 11:27:37 -0700 (PDT) From: John Baldwin To: Brooks Davis Subject: Re: Question about what programs to use in /etc/rc* Cc: hackers@FreeBSD.org, Adrian Filipi-Martin , Ulf Zimmermann Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10-Sep-01 Brooks Davis wrote: > On Mon, Sep 10, 2001 at 09:35:24AM -0700, Ulf Zimmermann wrote: >> > Come to think of it, it might be as easy as: [**UNTESTED**] >> > >> > case ${ifconfig_args}; in >> > [Dd][Hh][Cc][Pp]*) >> > set $ifconfig_args >> > shift >> > ifconfig_add_args="$*" >> > ...... >> > >> > ..provided there is a requirement that the ifconfig_args should *start* >> > with 'dhcp' (which would be easy enough to meet - right now, the args >> > have to *be* 'dhcp', so any additional arguments would be stapled on at >> > the end). >> >> This sounds as the best solution. This would allow to set an interface >> to be DHCP (variable dhcp_interfaces get set) and take the rest of the >> arguments (like media/mediaopt) and apply them to the interface before >> the dhclient gets started. > > If you want to go this route, make dhcp be the last argument not the > first one. If ifconfig understood dhcp (on my todo list) it would have > to be the last argument if you wanted it to work reliably because args > are processed in order and if your interface requires that you set the > media before it works, it's not going to work very well to run dhcp and > then fix the media. At least making dhcp be last insures that it will > continue to work once ifconfig grows dhcp support[*]. ifconfig won't grok dhcp b/c no one wants it to. I did that about a year ago in http://people.freebsd.org/~jhb/patches/ifconfig.dhcp.patch.that.no.one.wants (It might be a bit stale.) You are better off fixing the ifconfig args to allow multiple ifconfig statements much like we do with inet6 and ipx right now. I have this done, but again, the patch is stale. It also centralized a lot of duplicated cruft in /etc/pccard_ether. This patch file is way stale, but here it is: http://people.freebsd.org/~jhb/patches/dhcp.patch It allows you to have any arbitrary number of ifconfig commands if you really want. It also adds dhcp_foo0 variables to control dhcp, and supports the 'dhcp' ifconfig case as backwards compatibility. -- 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 Mon Sep 10 11:44: 8 2001 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 33F2937B401; Mon, 10 Sep 2001 11:43:56 -0700 (PDT) Received: from roary.excite.com ([199.172.148.162]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010910184355.KWOS29991.kuku.excite.com@roary.excite.com>; Mon, 10 Sep 2001 11:43:55 -0700 Message-ID: <29968233.1000147435488.JavaMail.imail@roary.excite.com> Date: Mon, 10 Sep 2001 11:43:52 -0700 (PDT) From: john_wilson100@excite.com To: sos@freebsd.org Subject: Re: HPT370 RAID or Vinum? Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, I'm not lying, honest :) Sysinstall gives me a dialog that has three checkboxes: ad4, ad6 and ar0. = =20 This got me confused, because I had never heard of ar0, and because the manual page for ar describes some other driver (Digi/Arnet). ad4 says 7476 cyls/255 heads/63 sectors (58643 MB), Offset Size End Name PType Desc Subtype Flags 0 63 62 - 6 unused 0 63 120103137 120103199 ad4s1 1 NTFS/HPFS/QNX 7 =3D ad6 complains about bad geometry (119150/16/63) and then shows this: ad6: 7476 cyls/255 heads/63 sectors (58643 MB), Offset Size End Name PType Desc Subtype Flags 0 120103200 120103199 - 6 unused 0 ar0 shows 14952 cyls/255 heads/63 sectors =3D 240203880 sectors (117287 MB) Offset Size End Name PType Desc Subtype Flags 0 63 62 - 6 unused 0 63 240187752 240187814 ar0s1 1 NTFS/HPFS/QNX 7=20 240187815 18503 240206317 - 6 unused 0 Maybe I should mention that the controller is actually called "Iwill SIDE-RAID 100" but it does have an HPT370 chip in it. And yes, it has NT on it (hence NTFS). I don't know what to make out of it, but I hope you can. Thanks John It seems john_wilson100@excite.com wrote: > Hi there, >=20 > I am trying to install FreeBSD on a (pseudo-) hardware ATA RAID volume which > consists of two striped ATA disks connected to a Highpoint HPT370 > controller. "Pseudo-" because FreeBSD detects the individual disks > (ad4/ad6) as well as the striped volume (ar0). Uhm, if a RAID array is foundm you cannot access the individual disks, the driver does not allow for that. > > Highpoint built-in RAID (ar0), or ad4/ad6 striped with Vinum? >=20 > I reckon if the RAID functions are implemented in HPT BIOS (in software), > I'll be better off with Vinum. The RAID code is implemented in the ATA driver (ata-raid.c) and tbat=20 takes over from the BIOS as soon as we are airborne (the BIOS is only needed and used for booting). However, there is no way to rebuild the ATA RAID from FreeBSD (that may soon change though) you have to use the BIOS for that... -S=F8ren _______________________________________________________ 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 Mon Sep 10 12:22:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 0FBC637B40D for ; Mon, 10 Sep 2001 12:22:43 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA49573; Mon, 10 Sep 2001 12:43:16 -0700 (PDT) Date: Mon, 10 Sep 2001 12:43:15 -0700 (PDT) From: Julian Elischer To: Jonathan Lemon Cc: kent@erix.ericsson.se, hackers@freebsd.org Subject: Re: How to force small TCP packets? In-Reply-To: <200109101817.f8AIH7t11927@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG just set the MTU on the sender to something really small (120 byres) On Mon, 10 Sep 2001, Jonathan Lemon wrote: > In article you write: > > > >bright@mu.org (Alfred Perlstein) writes: > >> there's a setsockopt for this called TCP_NODELAY in netinet/tcp.h. > >> > >> you should read further into stevens before posting such questions. > > > >I seem to have expressed myself really bad :-( I want to debug an > >application. We have had code that broke only occasionally on a > >specific Linux version under heavy load. I want to detect bad code > >like that and had hoped that some FreeBSD hackers had some tricks how > >to use kernel configuration to do that. > > > >If application A do a write like > > > > write(socket, buf, 100); > > > >and application B read this like > > > > read(socket, buf, 100); > > > >without checking the result from the read operation, then this code > >will probably work 99.9999% of the time. But if I could force the > >kernel to pass data from a socket on to the application say one byte > >at the time then this code will break 100% of the time. This makes > >finding these problems more easy. > > > >This is highly simplified example, else I could just grep the sources > >for all calls to read() and manually inspect the code. The data is > >passed on to other parts of the system using message queues. > > > >But using the kernel to debug user applications like this was probably > >a stupid idea. I'm sorry for posting a question to this group without > >the proper knowledge wasting your time, > > One thing you might want to try doing is to write your own read() > function and link against that. Your modified version could then > replace the nbytes value with something smaller, for debugging purposes. > -- > Jonathan > > 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 Mon Sep 10 12:31:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 79EBC37B401; Mon, 10 Sep 2001 12:31:10 -0700 (PDT) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id f8AJUud36423; Mon, 10 Sep 2001 09:30:57 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 10 Sep 2001 09:30:56 -1000 (HST) From: Vincent Poy To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: "[?X-UNKNOWN?]" , Subject: Re: cvs commit: src/usr.sbin/burncd burncd.8 burncd.c In-Reply-To: <200109101917.f8AJHea69437@freebsd.dk> Message-ID: <20010910092946.E34905-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Sep 2001, SЬren Schmidt wrote: > It seems Vincent Poy wrote: > > >root@pele [9:09am][/usr/src/usr.sbin/burncd] >> make > >cc -O -pipe -c /usr/src/usr.sbin/burncd/burncd.c > >/usr/src/usr.sbin/burncd/burncd.c:65: warning: `struct cdr_cue_entry' > >declared inside parameter list > >/usr/src/usr.sbin/burncd/burncd.c:65: warning: its scope is only this > >definition or declaration, which is probably not what you want. > >/usr/src/usr.sbin/burncd/burncd.c: In function `main': > >/usr/src/usr.sbin/burncd/burncd.c:244: `CDRIOCINITWRITER' undeclared > >(first use in this function) > >/usr/src/usr.sbin/burncd/burncd.c:244: (Each undeclared identifier is > >reported only once > .... > > You need to make world first as /sys/sys/cdrio.h has been updated, > and will only be copied to /usr/include/sys on a make world... I just finished a make world and not much changed but a make clean depend all install in /usr/src/include seems to do the same thing. It's working now. Thanks! Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 12:35:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 723F837B405 for ; Mon, 10 Sep 2001 12:35:33 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8AJYmP14585; Mon, 10 Sep 2001 14:34:48 -0500 (CDT) (envelope-from jlemon) Date: Mon, 10 Sep 2001 14:34:48 -0500 From: Jonathan Lemon To: Julian Elischer Cc: Jonathan Lemon , kent@erix.ericsson.se, hackers@freebsd.org Subject: Re: How to force small TCP packets? Message-ID: <20010910143448.C9056@prism.flugsvamp.com> References: <200109101817.f8AIH7t11927@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 10, 2001 at 12:43:15PM -0700, Julian Elischer wrote: > just set the MTU on the sender to something really small (120 byres) No. The data gets coalesced in the socket receive buffer on the other end, remember? So depending on how fast things are running, there may or may not be enough data present to satisfy the "100 byte" read, which is proably the edge case he is attempting to debug. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 12:41:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id 4F2C837B406 for ; Mon, 10 Sep 2001 12:41:37 -0700 (PDT) Received: (qmail 84761 invoked from network); 10 Sep 2001 19:41:34 -0000 Received: from gattaca.local.yadt.co.uk (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by xfiles.yadt.co.uk with SMTP; 10 Sep 2001 19:41:34 -0000 Received: (qmail 65543 invoked by uid 1000); 10 Sep 2001 19:41:34 -0000 Date: Mon, 10 Sep 2001 20:41:34 +0100 From: David Taylor To: Jonathan Lemon Cc: kent@erix.ericsson.se, hackers@freebsd.org Subject: Re: How to force small TCP packets? Message-ID: <20010910204134.A65177@gattaca.yadt.co.uk> Mail-Followup-To: Jonathan Lemon , kent@erix.ericsson.se, hackers@freebsd.org References: , <200109101817.f8AIH7t11927@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109101817.f8AIH7t11927@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Mon, Sep 10, 2001 at 13:17:07 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Sep 2001, Jonathan Lemon wrote: > One thing you might want to try doing is to write your own read() > function and link against that. Your modified version could then > replace the nbytes value with something smaller, for debugging purposes. Infact, when I saw this thread I whipped up a simple .so to override the syscalls to test a network program of my own, and it helpfully found a obscure bug where I wasn't correctly using the return value from read().. The main problem with the below code is that it unconditionally reads X bytes at a time. You might want to override socket/close (and maybe dup too, if the code does things like that) so you're only restricting syscalls on sockets. Or make a is_socket() function that does some runtime test I can't think of to figure out what to do... (compile using something like: gcc -fPIC -shared -O2 -g test.c -o test.so; use with something like: LD_PRELOAD=/path/to/test.so /your/program/bin/blah) #define NBYTES 1 ssize_t read(int d, void *buf, size_t nbytes) { return syscall(SYS_read, d, buf, ((nbytes; Mon, 10 Sep 2001 13:32:08 -0700 (PDT) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Sep 2001 14:31:59 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828F421@bdr-xcln.corp.matchlogic.com> From: Charles Randall To: 'Jonathan Lemon' , Julian Elischer Cc: kent@erix.ericsson.se, hackers@freebsd.org Subject: RE: How to force small TCP packets? Date: Mon, 10 Sep 2001 14:31:57 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Out of curiosity, can ipfw+dummynet do something like this? -----Original Message----- From: Jonathan Lemon [mailto:jlemon@flugsvamp.com] Sent: Monday, September 10, 2001 1:35 PM To: Julian Elischer Cc: Jonathan Lemon; kent@erix.ericsson.se; hackers@freebsd.org Subject: Re: How to force small TCP packets? On Mon, Sep 10, 2001 at 12:43:15PM -0700, Julian Elischer wrote: > just set the MTU on the sender to something really small (120 byres) No. The data gets coalesced in the socket receive buffer on the other end, remember? So depending on how fast things are running, there may or may not be enough data present to satisfy the "100 byte" read, which is proably the edge case he is attempting to debug. -- Jonathan 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 Mon Sep 10 13:35:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id BDC3B37B401 for ; Mon, 10 Sep 2001 13:35:50 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 908C381D06; Mon, 10 Sep 2001 15:35:45 -0500 (CDT) Date: Mon, 10 Sep 2001 15:35:45 -0500 From: Alfred Perlstein To: Charles Randall Cc: 'Jonathan Lemon' , Julian Elischer , kent@erix.ericsson.se, hackers@freebsd.org Subject: Re: How to force small TCP packets? Message-ID: <20010910153545.T2965@elvis.mu.org> References: <5FE9B713CCCDD311A03400508B8B30130828F421@bdr-xcln.corp.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828F421@bdr-xcln.corp.matchlogic.com>; from crandall@matchlogic.com on Mon, Sep 10, 2001 at 02:31:57PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (re: testing a client to see if it deals with short messages over a socket) * Charles Randall [010910 15:32] wrote: > Out of curiosity, can ipfw+dummynet do something like this? I've already responded to the poster in private about it because my initial suggestion was wrong (i hadn't read his email thouroughly enough). One way that should work without having to do anything tricky is using setsockopt with SO_RCVBUF to lower the buffer space, this should force the remote side to buffer and reduce the amount of data to be read. I'm still unsure if this is appropriate because the kernel may silently (or loudly) complain about a SO_RCVBUF that appears to be too small. You may be able to also do this by setting the sysctl kern.ipc.maxsockbuf to something small. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 18:13:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from canberra.worldwide.lemis.com (sydney3.au.ibm.com [202.135.142.201]) by hub.freebsd.org (Postfix) with ESMTP id 5703F37B403; Mon, 10 Sep 2001 18:13:22 -0700 (PDT) Received: (from grog@localhost) by canberra.worldwide.lemis.com (8.11.4/8.11.1) id f8AN5I301766; Tue, 11 Sep 2001 09:05:18 +1000 (EST) (envelope-from grog) Date: Tue, 11 Sep 2001 09:05:18 +1000 From: Greg Lehey To: john_wilson100@excite.com Cc: freebsd-hackers@FreeBSD.org, sos@FreeBSD.org Subject: Re: HPT370 RAID or Vinum? Message-ID: <20010911090518.G733@canberra.worldwide.lemis.com> References: <8846549.1000141895110.JavaMail.imail@roary.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <8846549.1000141895110.JavaMail.imail@roary.excite.com>; from john_wilson100@excite.com on Mon, Sep 10, 2001 at 10:11:28AM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 10 September 2001 at 10:11:28 -0700, john_wilson100@excite.com wrote: > Hi there, > > I am trying to install FreeBSD on a (pseudo-) hardware ATA RAID volume which > consists of two striped ATA disks connected to a Highpoint HPT370 > controller. "Pseudo-" because FreeBSD detects the individual disks > (ad4/ad6) as well as the striped volume (ar0). > > Besides the fact that ar0 isn't documented anywhere (except in /dev/MAKEDEV) > and "man 4 ar" gives something completely irrelevant, which one is better to > use: > > Highpoint built-in RAID (ar0), or ad4/ad6 striped with Vinum? > > I reckon if the RAID functions are implemented in HPT BIOS (in software), > I'll be better off with Vinum. Ultimately, all RAID is software RAID. The issue is just how it's implemented. I'd guess that the HPT will give you far worse performance than Vinum, though I'd be very interested to see confirmation or denial of this guess. If you feel like benchmarking, contact me first. 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 Mon Sep 10 20:34:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-6.dsl.lsan03.pacbell.net [63.207.60.6]) by hub.freebsd.org (Postfix) with ESMTP id 2245637B403 for ; Mon, 10 Sep 2001 20:34:38 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 557D766D0B; Mon, 10 Sep 2001 20:34:37 -0700 (PDT) Date: Mon, 10 Sep 2001 20:34:37 -0700 From: Kris Kennaway To: "Mark D. Anderson" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: local changes to CVS tree Message-ID: <20010910203437.A8986@xor.obsecurity.org> References: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke>; from mda@discerning.com on Sat, Sep 08, 2001 at 09:28:27PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 08, 2001 at 09:28:27PM -0700, Mark D. Anderson wrote: > "Terry Lambert " wrote: > > Any chance of getting CVSup to transfer from a remote repository > > to a local vendor branch, instead of from a remote repository to > > a local repository? > >=20 > > This would be incredibly useful for building a combined local > > source tree from multiple project's CVS repositories. It could > > be used by FreeBSD for a number of "contrib" things, as well... >=20 > this has probably been discussed before, but has the freebsd project cons= idered > using perforce for the central repository? Yes; see the archives. The main barrier is replication of the p4 depot to local developer machines for offline work. You can extract to cvs, but that's not really good enough. A number of committers are using perforce for out-of-main-tree development work on some of the major projects in -current (SMPng, etc). Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7nYZMWry0BWjoQKURAvGbAKC2exN8KDHOsLAY7xChjVtRxGel9gCcD+95 swe5YjlBI4+4kI518Z857lM= =zyVN -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 20:57:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kashmir.thend.org (thend.org [63.175.88.16]) by hub.freebsd.org (Postfix) with ESMTP id 8DEC137B407 for ; Mon, 10 Sep 2001 20:57:12 -0700 (PDT) Received: (from judge@localhost) by kashmir.thend.org (8.9.3/8.9.3) id WAA07010; Mon, 10 Sep 2001 22:02:21 -0600 (MDT) (envelope-from judge) Date: Mon, 10 Sep 2001 22:02:21 -0600 (MDT) From: Jeremy Pavleck Message-Id: <200109110402.WAA07010@kashmir.thend.org> To: perlbug@perl.com Subject: .. Cc: hackers@FreeBSD.org Reply-To: root@"kashmo".FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a bug report for perl from root@kashmo, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] jeowiejwoeijweoiwjeoiwjewoiejwoiejweoiwjeoiwjeowiejwoiejwoiejwoie [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at Sun Mar 5 13:39:27 SAST 2000. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='FreeBSD freefall.FreeBSD.org 4.0-current FreeBSD 4.0-current #0: $Date$' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=2.95.2 19991024 (release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E -lperl -lm ' libpth=/usr/lib libs=-lm -lc -lcrypt libc=, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/lib' cccdlflags='-DPIC -fpic', lddlflags='-Wl,-E -shared -lperl -lm ' Locally applied patches: --- @INC for perl 5.00503: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/judge LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/judge/bin:/usr/local/bin PERL_BADLANG (unset) SHELL=/usr/local/bin/bash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 20:57:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from onion.perl.org (onion.valueclick.com [209.85.157.220]) by hub.freebsd.org (Postfix) with SMTP id BF3B037B403 for ; Mon, 10 Sep 2001 20:57:25 -0700 (PDT) Received: (qmail 49314 invoked by uid 1007); 11 Sep 2001 03:57:25 -0000 Date: 11 Sep 2001 03:57:25 -0000 X-Perlbug-Url-Bug: http://bugs.perl.org/index.html?req=bug_id&bug_id=20010910.019 To: Jeremy Pavleck X-Original-Message-Id: <200109110402.WAA07010@kashmir.thend.org> Cc: hackers@freebsd.org X-Original-To: perlbug@perl.com X-Original-CC: hackers@FreeBSD.org Subject: Ack: [ID 20010910.019] .. X-Errors-To: perlbug@rfi.net From: perlbugtron@bugs.perl.org X-Perlbug: Perlbug(tron) v2.78 X-Perlbug-Admin-Url-Bug: http://bugs.perl.org/index.html?req=bug_id&bug_id=20010910.019 X-Original-Subject: .. X-Original-Perlbug: X-Original-From: Jeremy Pavleck Reply-To: perlbug@rfi.net Message-Id: <49291_237553787.005611@bugs.perl.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Your e-mail has been received by the Perl Bug Squashing Team. Original subject: .. A Bug ID (20010910.019) has been assigned and is shown in the subject of this email. Please include this bug ID in the subject line of any followup messages. This is an automatic confirmation message. If you do not wish to receive this confirmation, in the future, put 'ack=no' somewhere in the body of your mail. -- Perl Bug Squashing Team Message from the Perlbug squashing team at 'perlbug@perl.org' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 22:41: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id DAA3C37B405; Mon, 10 Sep 2001 22:40:56 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f8B5fAC10992; Tue, 11 Sep 2001 07:41:10 +0200 (CEST) (envelope-from sos) From: SЬren Schmidt Message-Id: <200109110541.f8B5fAC10992@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <20010911090518.G733@canberra.worldwide.lemis.com> "from Greg Lehey at Sep 11, 2001 09:05:18 am" To: Greg Lehey Date: Tue, 11 Sep 2001 07:41:06 +0200 (CEST) Cc: john_wilson100@excite.com, freebsd-hackers@FreeBSD.org, sos@FreeBSD.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > > I reckon if the RAID functions are implemented in HPT BIOS (in software), > > I'll be better off with Vinum. > > Ultimately, all RAID is software RAID. The issue is just how it's > implemented. Exactly. > I'd guess that the HPT will give you far worse performance than Vinum, > though I'd be very interested to see confirmation or denial of this > guess. If you feel like benchmarking, contact me first. And why is that ? for RAID's with the same parameters, I'd expect them to perform equal, maybe with a sligtht advantage to the ATA driver since it saves a few cycles by being tighter integrated. -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 10 22:58:31 2001 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 0293D37B401 for ; Mon, 10 Sep 2001 22:58:24 -0700 (PDT) Received: from redemma ([64.230.186.246]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20010911055823.KLSZ24586.tomts7-srv.bellnexxia.net@redemma> for ; Tue, 11 Sep 2001 01:58:23 -0400 Reply-To: From: "Institute For Social Ecology" To: Subject: httpd in free(): warning: recursive call. Date: Tue, 11 Sep 2001 02:00:18 -0400 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal In-Reply-To: <20010911054659.4D05A37B40A@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am very new to Apache administration, and am looking for some feedback on an apache/freeBSD issue. I have been frequently dealing with httpd maxing out at well over 150 threads, and running, bringing my system to a near standstill. My error log confirms that apache is being maxed out, but also turns up some weird stuff. Actually, when httpd does max out, the error log pumps out several hundred pages of this: httpd in free(): warning: recursive call. and httpd in malloc(): warning: recursive call. I have looked around to find an explanation for this warning, and have come up empty handed. Any ideas? Any thoughts is greatly appreciated. Regards, Michael FYI: I am running FreeBSD 4.1.1-STABLE Apache Version Apache/1.3.17 Apache Release 10317100 Apache API Version 19990320 User/Group nobody(65534)/65534 Max Requests Per Child: 30 Keep Alive: on Max Per Connection: 100 Timeouts Connection: 300 Keep-Alive: 15 Server Root /usr/local/apache Loaded Modules mod_perl, mod_php4, mod_setenvif, mod_auth, mod_access, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_status, mod_negotiation, mod_mime, mod_log_config, mod_env, http_core To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 0: 2:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f30.pav1.hotmail.com [64.4.31.30]) by hub.freebsd.org (Postfix) with ESMTP id BDCC437B406 for ; Tue, 11 Sep 2001 00:02:20 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 11 Sep 2001 00:02:20 -0700 Received: from 32.97.136.233 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 11 Sep 2001 07:02:20 GMT X-Originating-IP: [32.97.136.233] From: "Jayesh Krishna" To: freebsd-hackers@FreeBSD.ORG Subject: Packet Shapers Date: Tue, 11 Sep 2001 12:32:20 +0530 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Sep 2001 07:02:20.0515 (UTC) FILETIME=[B3403B30:01C13A8F] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! Does any one of u guys/gals have a hands on experience with Packet Shapers. I am in the process of verification of a proposal for a Packet Shaper. I would like to know the practical views regarding the Packet Shaper( Is it really useful ???). Any contributions will be really helpful. regds Jayesh _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 5:33:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diogenis.ceid.upatras.gr (diogenis.ceid.upatras.gr [150.140.141.181]) by hub.freebsd.org (Postfix) with SMTP id 5A72D37B405 for ; Tue, 11 Sep 2001 05:33:24 -0700 (PDT) Received: (qmail 8385 invoked by uid 1604); 11 Sep 2001 12:32:22 -0000 Date: Tue, 11 Sep 2001 15:32:22 +0300 (EET DST) From: Balis George To: Institute For Social Ecology Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: httpd in free(): warning: recursive call. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I assume that by the term "threads" you mean processes so i disregard it. There is always the matter of the limit of file descriptors you can have open at any time. You don't mention what other purposes (e.g services) your box runs or what are it's "stats". George On Tue, 11 Sep 2001, Institute For Social Ecology wrote: > Date: Tue, 11 Sep 2001 02:00:18 -0400 > From: Institute For Social Ecology > To: freebsd-hackers@FreeBSD.ORG > Subject: httpd in free(): warning: recursive call. > > Hello, > > I am very new to Apache administration, and am looking for some > feedback on an apache/freeBSD issue. I have been frequently dealing > with httpd maxing out at well over 150 threads, and running, bringing > my system to a near standstill. My error log confirms that apache is > being maxed out, but also turns up some weird stuff. Actually, when > httpd does max out, the error log pumps out several hundred pages of > this: > > httpd in free(): warning: recursive call. > > and > > httpd in malloc(): warning: recursive call. > > I have looked around to find an explanation for this warning, and have > come up empty handed. Any ideas? > > Any thoughts is greatly appreciated. > > Regards, > > Michael > > > FYI: I am running > > FreeBSD 4.1.1-STABLE > Apache Version Apache/1.3.17 > Apache Release 10317100 > Apache API Version 19990320 > User/Group nobody(65534)/65534 > Max Requests Per Child: 30 > Keep Alive: on > Max Per Connection: 100 > Timeouts Connection: 300 > Keep-Alive: 15 > Server Root /usr/local/apache > Loaded Modules mod_perl, mod_php4, mod_setenvif, mod_auth, mod_access, > mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, > mod_dir, mod_autoindex, mod_include, mod_status, mod_negotiation, > mod_mime, mod_log_config, mod_env, http_core > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Black holes are the result when God devides by zero.. mailto: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 5:50:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.iae.nl [212.61.26.37]) by hub.freebsd.org (Postfix) with ESMTP id A830237B410 for ; Tue, 11 Sep 2001 05:50:08 -0700 (PDT) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id OAA04262 for freebsd-hackers@freebsd.org; Tue, 11 Sep 2001 14:50:07 +0200 (MET DST) Received: by drawbridge.oasis.IAEhv.nl (Postfix, from userid 226) id 3B82B3E02; Tue, 11 Sep 2001 14:46:47 +0200 (CEST) Subject: kernel memory size To: freebsd-hackers@freebsd.org Date: Tue, 11 Sep 2001 14:46:47 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010911124647.3B82B3E02@drawbridge.oasis.IAEhv.nl> From: volf@oasis.IAEhv.nl (Frank Volf) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a way to increase the memory size that is allocated by the kernel to a certain kernel memory pool (is that the correct word?): I mean, I have options VM_KMEM_SIZE="(64*1024*1024)" in my kernel config file, and it appears that I'm only allowed to use half of that memory for a certain pool: # vmstat -m | grep Filter 16 uc_devlist, p1003.1b, IP Filter, igmp, routetbl, ether_multi, vnodes, 256 file desc, FFS node, newblk, IP Filter, routetbl, ifaddr, vnodes, 512 uc_devlist, UFS mount, IP Filter, mount, BIO buffer, ptys, msg, 32K VM pgdata, UFS ihash, inodedep, IP Filter, devbuf IP Filter 276 158K 23307K 32768K 47735 0 0 16,256,512,32K Howerver, this box is a dedicated traffic filtering box, and I want to increase the available kernel memory for this kmalloc category. I grepped in the source, but apart from the assignment type->ks_limit = vm_kmem_size / 2; in kern_malloc.c, I could not find a place were this limit is increased. Is it possible to circumvent this? Frank BTW: I'm running FreeBSD 4.3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 8:22:20 2001 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 0EB5C37B401 for ; Tue, 11 Sep 2001 08:22:18 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f8BFMGn11515 for ; Tue, 11 Sep 2001 11:22:16 -0400 (EDT) Date: Tue, 11 Sep 2001 11:22:14 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: why use vfs_clean_pages()? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The routine vfs_clean_pages() is only called by bdwrite() to tell the VM that the buffer pages are "clean" so that VFS will write them when it sees fit. However, pages belonging to buffers are wired down, which means they are not on any paging queues. So even without vfs_clean_pages(), the pageout daemon will not write those pages. There is therefore no need for the call to vfs_clean_pages(). Please correct me if I am wrong. I am really confused here. Thanks, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 10:55:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 8F68D37B403; Tue, 11 Sep 2001 10:55:34 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8BHtdi26424; Tue, 11 Sep 2001 19:55:39 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <00a601c13aeb$04d380a0$0245a8c0@chojin> From: "Chojin" To: , Subject: Problem with snmpd Date: Tue, 11 Sep 2001 19:56:00 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I have a problem with snmpd. In fact, one day, for unknown reason ( I didn't modify any setting ), snmpd didn't work anymore: When I do a snmpwalk or snmpget to public@localhost it doesn't respond. I checked snmpd, recreated snmpd.conf and launched again snmpd with -c and -l to be sure it uses the correct files. But even if snmpd is in background process, public@localhost doesn't work. I don't have any firewall rule that block it. #snmpwalk localhost public Timeout: No Response from localhost #snmpget localhost public SysName Timeout: No Response from localhost. After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't change anything for snmpd. If someone has got any idea... Best regards, Chojin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 11:45:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smile.idiom.com (inreach-gw1.idiom.com [209.209.13.26]) by hub.freebsd.org (Postfix) with ESMTP id D9FD837B405 for ; Tue, 11 Sep 2001 11:45:28 -0700 (PDT) Received: from mdaxke (adsl-64-171-254-205.dsl.snfc21.pacbell.net [64.171.254.205]) by smile.idiom.com (8.9.1/8.8.5) with SMTP id LAA57894 for ; Tue, 11 Sep 2001 11:45:28 -0700 (PDT) Message-ID: <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke> From: "Mark D. Anderson" To: References: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> <01090920122401.00426@antiproton.ChrisBowman.com> Subject: Re: local changes to CVS tree Date: Tue, 11 Sep 2001 11:44:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I use perforce at work, and I think it is a really great tool. That said it > does have a few drawbacks. For one my experience is that perforce is really > only suitable for use in a situation where you are well connected to the > server. You can check out a set of files and work with them, but if you want > to do things like diff two repo versions you have to be connected to the > server at the time. In contrast you can keep a local copy of the cvs repo > and do just about everything locally, I haven't found this capability with > perforce. Also you can very efficiently fetch the entire cvs repo with cvsup > which is really a marvelous tool. I am not aware of a method to do this with > perforce. Finally just about my favorite cvs feature is cvs annotate which I > have not yet found a way to do under perforce. Do you know of a way to do > this? in any scenario, compatibility with existing cvs practices would have to be largely preserved. i was imagining a perforce repository for committers, and a readonly cvs server kept up to date by triggers, to support existing (readonly) practices. this would allow for advanced branching/merging against that perforce repository, without the limitations of cvs. an alternative would be to reverse the relationship, keeping cvs as the master, and constructing perforce slave snapshots. according to kris kennaway, that is already being done for some longer freebsd projects. i don't see how that directly solves the stable vs. current problem, however. "cvs annotate" can either be done against a slave cvs, or a similar report could be constructed against perforce. it is really just a report, after all. as for the other areas you mention, perforce does not directly support repository-to-repository replication, nor disconnected operations. if replicas are required, rsync (which is not atomic at the database level), or journal playback could be used, though both would require work. i do not know if perforce supports branching against a "remote depot"; i suspect something like that would accomplish the same goal. but maybe not. the whole question of distributed repositories is kind of a hot button in the CM world, because historically that feature, which clearcase has, was pushed as a solution in circumstances where it was not appropriate, and the simple client-server model works fine (for example, two corporate offices of the same company, both in the U.S.). > Finally, what about other version systems does any body have any comments or > experience with Ageis, bitkeeper or subversion? and what about that thing > the Evind was writing? i don't know anything about Evind; here is a brief summary of some of the other alternatives. all IMHO of course. Aegis (GPL, http://www.canb.auug.org.au/~millerp/aegis/aegis.html ) the pro and the con of aegis is that it enforces a whole change lifecycle, ensuring that submitted changes still compile and pass tests. it seems unlikely that all freebsd committers would care for this approach. If stripped of those abilities, leaving just a source control system, i doubt it is worth it, though i'm sure aegis advocates would disagree. Aegis does have excellent support for name operations (rename/delete/mkdir), one of many things cvs is horrible at. bitkeeper (bitkeeper license, http://www.bitkeeper.com ) bitkeeper was apparently inspired in part by a desire by larry mcvoy to supply linus and linux with a better solution than their current one, although to date there is no sign of it being adopted; judging from the email archive this seems mostly due to it having a free-only-for-free-projects license, though i wonder too if linus ever thought he needed an alternative to begin with. it takes the approach that every workspace is a repository; there is no distinction between a workspace sync and a repository sync; they are the same thing. furthermore, repositories can be placed in a hierarchy. this capability (insofar as i understand it) is used not only for disconnected operations and distributed repositories, but also for what other systems would consider "branches" or "lines of development". if you really feel you need such a distributed model (i.e. distributed repos, not just distributed clients), it is probably worth a look. bitkeeper has its own bitkeeper license. for non open source projects, it allegedly has close-to-clearcase level pricing. subversion (apache/bsd, http://subversion.tigris.org/ ) probably the most active effort for an open source replacement for CVS. as of a week ago it just hits its "milestone 3", of being self-hosting (it was previously using CVS to keep its own sources). it is still being actively worked on; now is probably not a good time to adopt it. while it intends to supplant CVS, it is inclear to me whether it will support a CVSup equivalent. PRCS (GPL, http://prcs.sourceforge.net/ ) Josh MacDonald's labor of love. because of his background, has a very strong backend storage mechanism (xdelta). appears not to have distributed repositories. as with aegis, good about name operations. If anyone has a more detailed review of these alternatives, discussing the specifics of branching support, namespace changes, repository replication, view definition, and so on, i'd be interested to see it. But usually discussions of CM tools are about as informative as discussions of text editors.... -mda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 12: 5:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f4.law3.hotmail.com [209.185.241.4]) by hub.freebsd.org (Postfix) with ESMTP id 1946B37B406 for ; Tue, 11 Sep 2001 12:05:12 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 11 Sep 2001 12:05:12 -0700 Received: from 205.158.104.176 by lw3fd.law3.hotmail.msn.com with HTTP; Tue, 11 Sep 2001 19:05:11 GMT X-Originating-IP: [205.158.104.176] From: "Srinivas Dharmasanam" To: freebsd-hackers@freebsd.org Subject: Re: inw and outw calls Date: Tue, 11 Sep 2001 12:05:11 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Sep 2001 19:05:12.0078 (UTC) FILETIME=[AEB78AE0:01C13AF4] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a question regarding the inb/outb() or inw/outw() calls in FreeBSD 4.2. I have a dual fxp Fast Ethernet NIC that shows up as following with dmesg : fxp1: port 0xcc00-0xcc3f mem 0xef900000-0xef9fffff,0xefa ff000-0xefafffff irq 18 at device 12.0 on pci2 fxp1: Ethernet address 00:30:64:03:03:2a fxp2: port 0xc800-0xc83f mem 0xef700000-0xef7fffff,0xefa fe000-0xefafefff irq 19 at device 13.0 on pci2 fxp2: Ethernet address 00:30:64:03:03:2b Now, I need to write the Watchdog timer ctrl registers (offset 65 and 66) on this card. For this I'm using outb(port, val) fn call. Can someone please tell me how to calculate the port no to pass to this outb() function. I tried writing to all possible port nos starting from 0xc800 to 0xc83f and 0xcc00-0xcc3f but it has no apparent effect on the system. Please let me know how to translate this port range to the actual outb() fn call arguments. Thanks a lot in advance. Regards, -Srinivas _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 12:21:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcbain.stg.com (mcbain.stg.com [65.162.207.13]) by hub.freebsd.org (Postfix) with ESMTP id A87A137B40B for ; Tue, 11 Sep 2001 12:21:51 -0700 (PDT) Received: from stg.com (willie.stg.com [65.162.207.103]) by mcbain.stg.com (Netscape Messaging Server 4.15) with ESMTP id GJIJ4D00.B1P; Tue, 11 Sep 2001 14:21:49 -0500 Message-ID: <3B9E644A.AA666A68@stg.com> Date: Tue, 11 Sep 2001 14:21:46 -0500 From: "Andy Schweig" Organization: Software Technologies Group X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Cc: SBS Project Staff Subject: Major number request Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Software Technologies Group (http://www.stg.com) is currently developing a FreeBSD driver for SBS Technologies (http://www.sbs.com) for their WANic 520 series of WAN interface cards. The design of the driver requires the creation of a device node. Would it be possible to get a major number reserved for this driver? Thanks for your help... Andy Schweig Software Technologies Group 708.547.0110 x224 aes@stg.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 12:26:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hamster.franken.de (hamster.franken.de [193.141.110.13]) by hub.freebsd.org (Postfix) with ESMTP id DEFE737B401 for ; Tue, 11 Sep 2001 12:26:14 -0700 (PDT) Received: from karnickel.franken.de (karnickel.franken.de [193.141.110.11]) by hamster.franken.de (8.11.5/8.11.5) with ESMTP id f8BJQAX72519; Tue, 11 Sep 2001 21:26:10 +0200 (CEST) (envelope-from tanis@gaspode.franken.de) Received: from gaspode.franken.de (lengfeld.core.main.franken.de [193.141.110.4]) by karnickel.franken.de (8.11.3/8.11.3) with ESMTP id f8BJQAJ64370; Tue, 11 Sep 2001 21:26:10 +0200 (CEST) (envelope-from tanis@gaspode.franken.de) Received: (from tanis@localhost) by gaspode.franken.de (8.11.6/8.11.1) id f8BJQA702856; Tue, 11 Sep 2001 21:26:10 +0200 (CEST) (envelope-from tanis) Date: Tue, 11 Sep 2001 21:26:10 +0200 From: German Tischler To: Srinivas Dharmasanam Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: inw and outw calls Message-ID: <20010911212610.A2817@gaspode.franken.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.2.5-current-20010403i In-Reply-To: ; from the_srinivas@hotmail.com on Tue, Sep 11, 2001 at 12:05:11PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 11, 2001 at 12:05:11PM -0700, Srinivas Dharmasanam wrote: > Hi, > I have a question regarding the inb/outb() or inw/outw() calls in FreeBSD= =20 > 4.2. >=20 > I have a dual fxp Fast Ethernet NIC that shows up as following with dmesg= : >=20 > fxp1: port 0xcc00-0xcc3f mem=20 > 0xef900000-0xef9fffff,0xefa > ff000-0xefafffff irq 18 at device 12.0 on pci2 > fxp1: Ethernet address 00:30:64:03:03:2a > fxp2: port 0xc800-0xc83f mem=20 > 0xef700000-0xef7fffff,0xefa > fe000-0xefafefff irq 19 at device 13.0 on pci2 > fxp2: Ethernet address 00:30:64:03:03:2b >=20 > Now, I need to write the Watchdog timer ctrl registers (offset 65 and 66)= on=20 > this card. >=20 > For this I'm using outb(port, val) fn call. Can someone please tell me ho= w=20 > to calculate the port no to pass to this outb() function. >=20 > I tried writing to all possible port nos starting from 0xc800 to 0xc83f > and 0xcc00-0xcc3f but it has no apparent effect on the system. >=20 > Please let me know how to translate this port range to the actual outb() = fn=20 > call arguments. >=20 > Thanks a lot in advance. You should probably extend the kernel fxp driver and use=20 bus_space_read and bus_space_write instead of trying to do this in userspace. The driver already has a watchdog routine, perhaps you can add what you need there. --gt --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iQEVAwUBO55lUb7hO6NLB/FvAQHDpgf/YjL+0G/E8aMVq/5FH6J51TzTW/H6XNrS iPEHMLOVa5j1LvjdutmSSglBssNW6ZbyJMcwvBR6bDbQ8M7fjF2QpsH2LOnRw1Zb y+aZqYheGGbChZ1j57uIeWP7kqZGI1RpWOQaBpzSbnco2qBvuo97VYPDJvAZ/tX9 BGVM06hmaLoUpzV+zzEUFR5ZYtJJNJM33E+It3aZUUIc9d3jhsQVVKVMvONs43T6 S0dciOQ20F4odpZMuN61YMQ8q4hzMYqUeBmCU5XwGKbYYL7XsIGbDcxHKnqE86qc MFdleIMgETCLiybxvdM8zcjY0P1Yfq6TQLoOi1pxUuyX2CDLPx6kyg== =m0fL -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 12:44:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4DB5837B40B for ; Tue, 11 Sep 2001 12:44:19 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8BJhdv24844; Tue, 11 Sep 2001 21:43:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Andy Schweig" Cc: hackers@FreeBSD.ORG, SBS Project Staff Subject: Re: Major number request In-Reply-To: Your message of "Tue, 11 Sep 2001 14:21:46 CDT." <3B9E644A.AA666A68@stg.com> Date: Tue, 11 Sep 2001 21:43:39 +0200 Message-ID: <24842.1000237419@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B9E644A.AA666A68@stg.com>, "Andy Schweig" writes: >Hello, > >Software Technologies Group (http://www.stg.com) is currently developing a >FreeBSD driver for SBS Technologies (http://www.sbs.com) for their WANic 520 >series of WAN interface cards. The design of the driver requires the creation of >a device node. Would it be possible to get a major number reserved for this >driver? Thanks for your help... Hi Andy, I'm pretty sure that you should not make this a "classical device" but rather a NetGraph node. Contact julian@freebsd.org for details on NetGraph if you cannot find any docs on it. You may also want to look at the "musycc" and "if_mn" drivers which support similar cards. -- 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 From owner-freebsd-hackers Tue Sep 11 12:50:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-94-248-46.mmcable.com [24.94.248.46]) by hub.freebsd.org (Postfix) with SMTP id DD12937B40A for ; Tue, 11 Sep 2001 12:50:56 -0700 (PDT) Received: (qmail 82475 invoked by uid 100); 11 Sep 2001 19:50:55 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15262.27423.830000.167832@guru.mired.org> Date: Tue, 11 Sep 2001 14:50:55 -0500 To: "Mark D. Anderson" Cc: Subject: Re: local changes to CVS tree In-Reply-To: <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke> References: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> <01090920122401.00426@antiproton.ChrisBowman.com> <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark D. Anderson types: > as for the other areas you mention, perforce does not directly support repository-to-repository > replication, nor disconnected operations. > i do not know if perforce supports branching against a "remote depot"; i suspect something > like that would accomplish the same goal. > but maybe not. Perforce permits branching from a remote depot, but not to a remote depot - they are read-only. If the goal is to replicate the remote depot, this won't do it. If the goal is to keep local changes to remote depot, it works very well. It will require you to be online to do source udpates, though. While perforce doesn't let you work with it while disconnected, there is a simple procedure to integrate changes made locally while disconnected back to the depot. Personally, I'd love to have access to FreeBSD source via a perforce remote host. On the other hand, I'm biased. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 13:46:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcbain.stg.com (mcbain.stg.com [65.162.207.13]) by hub.freebsd.org (Postfix) with ESMTP id 5E55237B40F for ; Tue, 11 Sep 2001 13:46:32 -0700 (PDT) Received: from stg.com (willie.stg.com [65.162.207.103]) by mcbain.stg.com (Netscape Messaging Server 4.15) with ESMTP id GJIN1J00.N1N; Tue, 11 Sep 2001 15:46:31 -0500 Message-ID: <3B9E7827.39529B62@stg.com> Date: Tue, 11 Sep 2001 15:46:31 -0500 From: "Andy Schweig" Organization: Software Technologies Group X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG, SBS Project Staff Subject: Re: Major number request References: <24842.1000237419@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually, it will be a Netgraph node. The idea is to use the character device interface for configuration. Each of these cards has a 6-byte MAC address programmed into it which can be used as a unique ID for the card. We would like to be able to program the driver with an association between MAC address and card number (0, 1, 2, etc.). This card number would determine the name of the Netgraph node (e.g., "wan520c0"). It would seem that this configuration would have to happen before the creation of any Netgraph nodes, which means that some method other than Netgraph would need to be used to give the driver this mapping information (e.g., an ioctl using the character device interface). Another strategy occurred to me while writing this mail, namely that a default association could be made between Netgraph node names and physical devices which could be changed by issuing a control message to the Netgraph node. Perhaps this is a better alternative. I would welcome any suggestions you might have for handling this situation. Thanks again for your help... Andy Poul-Henning Kamp wrote: > > In message <3B9E644A.AA666A68@stg.com>, "Andy Schweig" writes: > >Hello, > > > >Software Technologies Group (http://www.stg.com) is currently developing a > >FreeBSD driver for SBS Technologies (http://www.sbs.com) for their WANic 520 > >series of WAN interface cards. The design of the driver requires the creation of > >a device node. Would it be possible to get a major number reserved for this > >driver? Thanks for your help... > > Hi Andy, > > I'm pretty sure that you should not make this a "classical device" but > rather a NetGraph node. > > Contact julian@freebsd.org for details on NetGraph if you cannot find > any docs on it. > > You may also want to look at the "musycc" and "if_mn" drivers which > support similar cards. > > -- > 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 From owner-freebsd-hackers Tue Sep 11 13:53:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B7B5837B407 for ; Tue, 11 Sep 2001 13:53:36 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8BKrRv26684; Tue, 11 Sep 2001 22:53:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Andy Schweig" Cc: hackers@FreeBSD.ORG, SBS Project Staff Subject: Re: Major number request In-Reply-To: Your message of "Tue, 11 Sep 2001 15:46:31 CDT." <3B9E7827.39529B62@stg.com> Date: Tue, 11 Sep 2001 22:53:27 +0200 Message-ID: <26682.1000241607@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fort the musycc and if_mn drivers I ended up giving the nodes names from the physical location on the pci bus, so they are called things like: sync-0-10-0 sync-0-9-0 etc. I wouldn't mind if we could standardize the interface in general btw, it would make it a lot easier for FreeBSD users if they can just plug in a supported card and see things work the same, nomatter which card. I'm not saying that the way I designed the interface for the musycc or if_mn are ideal, but at least they work in production... Poul-Henning In message <3B9E7827.39529B62@stg.com>, "Andy Schweig" writes: >Actually, it will be a Netgraph node. The idea is to use the character device >interface for configuration. Each of these cards has a 6-byte MAC address >programmed into it which can be used as a unique ID for the card. We would like >to be able to program the driver with an association between MAC address and >card number (0, 1, 2, etc.). This card number would determine the name of the >Netgraph node (e.g., "wan520c0"). It would seem that this configuration would >have to happen before the creation of any Netgraph nodes, which means that some >method other than Netgraph would need to be used to give the driver this mapping >information (e.g., an ioctl using the character device interface). > >Another strategy occurred to me while writing this mail, namely that a default >association could be made between Netgraph node names and physical devices which >could be changed by issuing a control message to the Netgraph node. Perhaps this >is a better alternative. I would welcome any suggestions you might have for >handling this situation. Thanks again for your help... > >Andy > >Poul-Henning Kamp wrote: >> >> In message <3B9E644A.AA666A68@stg.com>, "Andy Schweig" writes: >> >Hello, >> > >> >Software Technologies Group (http://www.stg.com) is currently developing a >> >FreeBSD driver for SBS Technologies (http://www.sbs.com) for their WANic 520 >> >series of WAN interface cards. The design of the driver requires the creation of >> >a device node. Would it be possible to get a major number reserved for this >> >driver? Thanks for your help... >> >> Hi Andy, >> >> I'm pretty sure that you should not make this a "classical device" but >> rather a NetGraph node. >> >> Contact julian@freebsd.org for details on NetGraph if you cannot find >> any docs on it. >> >> You may also want to look at the "musycc" and "if_mn" drivers which >> support similar cards. >> >> -- >> 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. > -- 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 From owner-freebsd-hackers Tue Sep 11 15:41:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id E7B0837B406 for ; Tue, 11 Sep 2001 15:41:44 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA55370; Tue, 11 Sep 2001 16:08:51 -0700 (PDT) Date: Tue, 11 Sep 2001 16:08:49 -0700 (PDT) From: Julian Elischer To: Andy Schweig Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG, SBS Project Staff Subject: Re: Major number request In-Reply-To: <3B9E7827.39529B62@stg.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 11 Sep 2001, Andy Schweig wrote: > Actually, it will be a Netgraph node. The idea is to use the character > device interface for configuration. > Each of these cards has a 6-byte MAC address programmed into it which > can be used as a unique ID for the card.s > We would like to be able to program the driver with an association > between MAC address and card number (0, 1, 2, etc.). This card number > would determine the name of the Netgraph node (e.g., "wan520c0"). Not quite sure I follow (4.x or -current by the way?) I think you mean that you would just use the MAC address as a fixed identifier, rather than a unit number (as is used by, say, if_sr,c). > It would seem that this configuration would have to happen before the > creation of any Netgraph nodes, which means that some method other > than Netgraph would need to be used to give the driver this mapping > information (e.g., an ioctl using the character device interface). > I don't understand.. On detecting the hardware, the driver would read the MAC and set up the name... What configuration do you mean? And anyway, a name is optional in netgraph. teh node can be addressed before it gets a name by using it's unique ID. > Another strategy occurred to me while writing this mail, namely that a > default association could be made between Netgraph node names and > physical devices which could be changed by issuing a control message > to the Netgraph node. Perhaps this is a better alternative. I would > welcome any suggestions you might have for handling this situation. > Thanks again for your help... > I think that is a better tack.. The default name that it sets up can be the MAC address, and you can redefine it to be "Sydney1" or "London3" if you want. (Actually you can't yet in 4.x because you can't REname a node, but I'm going to remove that restriction, because it's silly.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 16:40:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 4CFC337B407 for ; Tue, 11 Sep 2001 16:40:52 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA55567 for ; Tue, 11 Sep 2001 17:19:12 -0700 (PDT) Date: Tue, 11 Sep 2001 17:19:11 -0700 (PDT) From: Julian Elischer To: hackers@freebsd.org Subject: cvsup14 (cvsup.above.net) not up to date Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems to be not updating.. maybe they didn't get the new version of cvsup (or installed the wrong one like I did to start with) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 18: 3: 8 2001 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 DEED037B401 for ; Tue, 11 Sep 2001 18:03:05 -0700 (PDT) Received: from tuttle ([64.228.142.217]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20010912010305.YFKI22880.tomts8-srv.bellnexxia.net@tuttle> for ; Tue, 11 Sep 2001 21:03:05 -0400 Message-ID: <000501c13b26$eb042d00$d98ee440@tuttle> From: "Adam Tuttle" To: References: Subject: Date: Tue, 11 Sep 2001 21:04:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 19:11:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id 7B26637B403 for ; Tue, 11 Sep 2001 19:11:16 -0700 (PDT) Received: from localhost.softweyr.com ([127.0.0.1] helo=softweyr.com) by softweyr.com with esmtp (Exim 3.33 #1) id 15gzfR-00009d-00; Tue, 11 Sep 2001 20:22:22 -0600 Message-ID: <3B9EC6DD.5C68629D@softweyr.com> Date: Tue, 11 Sep 2001 20:22:21 -0600 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 Kozubik Cc: hackers@freebsd.org Subject: Re: OT: firewire slugs available ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Kozubik wrote: > > In the near future I will be doing some research and development with IEEE > 1394. Such that I will be requiring a _large_ number of firewire > devices. It is not within my budget to purchase 63 x 4 cameras. Firewire CD-Rs or DVDs would be less expensive than cameras, wouldn't they? > So I was trying to think of the cheapest possible IEEE 1394 device - if > worst comes to worse I could just buy 252 of those ... again, not very > practicle. > > IEEE 1394 chipsets, however, are about $8.00 each. > > Has anyone seen IEEE 1394 "slugs" - devices that perform basic > functionality (in terms of participating on the bus) but not much else > ? (presumably, if these devices exist, they were developed for just this > type of development) Does anyone make a firewire mouse? ;^) You might want to look at one of the embedded firewire SDKs; using some of the sample code you should be able to produce 300 boneheaded firewire devices for very low cost after the purchase price of the SDK. -- "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 Sep 11 23:21:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 36FA237B407 for ; Tue, 11 Sep 2001 23:21:50 -0700 (PDT) Received: from NDNM ([195.161.98.250]) by ns.morning.ru (8.11.5/8.11.5) with ESMTP id f8C6Lld52965 for ; Wed, 12 Sep 2001 14:21:48 +0800 (KRAST) Date: Wed, 12 Sep 2001 14:22:06 +0800 From: Igor Podlesny X-Mailer: The Bat! (v1.53d) UNREG / CD5BF9353B3B7091 Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <11964730767.20010912142206@morning.ru> To: hackers@FreeBSD.ORG Subject: libcap question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! I suspect that it's impossible to check out with libcap (BPF) whether a captured packet is incoming or outgoing, but may be it is not? -- Best regards, Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 11 23:59:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id AF76237B405 for ; Tue, 11 Sep 2001 23:59:41 -0700 (PDT) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.6/8.11.4) id f8C6xDv31401; Wed, 12 Sep 2001 08:59:13 +0200 (CEST) (envelope-from stijn) Date: Wed, 12 Sep 2001 08:59:13 +0200 From: Stijn Hoop To: "Mark D. Anderson" Cc: freebsd-hackers@freebsd.org Subject: Re: local changes to CVS tree Message-ID: <20010912085913.B31205@pcwin002.win.tue.nl> References: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> <01090920122401.00426@antiproton.ChrisBowman.com> <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke>; from mda@discerning.com on Tue, Sep 11, 2001 at 11:44:26AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Sep 11, 2001 at 11:44:26AM -0700, Mark D. Anderson wrote: > subversion (apache/bsd, http://subversion.tigris.org/ ) > probably the most active effort for an open source replacement for CVS. > as of a week ago it just hits its "milestone 3", of being self-hosting > (it was previously using CVS to keep its own sources). > it is still being actively worked on; now is probably not a good time to > adopt it. while it intends to supplant CVS, it is inclear to me whether > it will support a CVSup equivalent. You're right, this is not the time to adopt it, but I'm keeping an eye on this one - it's actively trying to be easy for CVS users to use, plus it tries to correct CVS's deficiencies, plus they are working on CVS -> subversion repository conversion tools. Not to mention the license. Thanks for the pointer! --Stijn -- "I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 0:23:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 590DB37B408; Wed, 12 Sep 2001 00:23:12 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8C7NFi13587; Wed, 12 Sep 2001 09:23:15 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <002e01c13b5b$d3dea0d0$0245a8c0@chojin> From: "Chojin" To: "Jean-Francois Dive" Cc: , References: Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 09:22:31 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG snmpd.log is empty... I did #netstat -an | grep 161 udp4 0 0 *.161 *.* port 161 exists then it should work... ----- Original Message ----- From: "Jean-Francois Dive" To: "Chojin" Cc: ; Sent: Wednesday, September 12, 2001 3:21 AM Subject: Re: Problem with snmpd > Hi, > > So you have any traces in a log file or something similar ? > > JeF > > On Tue, 11 Sep 2001, Chojin wrote: > > > Hello, > > > > I have a problem with snmpd. > > > > In fact, one day, for unknown reason ( I didn't modify any setting ), snmpd > > didn't work anymore: > > When I do a snmpwalk or snmpget to public@localhost it doesn't respond. > > I checked snmpd, recreated snmpd.conf and launched again snmpd with -c > > and -l to be sure it uses the correct files. > > But even if snmpd is in background process, public@localhost doesn't work. > > I don't have any firewall rule that block it. > > > > #snmpwalk localhost public > > Timeout: No Response from localhost > > #snmpget localhost public SysName > > Timeout: No Response from localhost. > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't change > > anything for snmpd. > > > > If someone has got any idea... > > > > Best regards, > > > > Chojin > > > > > > 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 Wed Sep 12 0:39:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 7F3B137B407 for ; Wed, 12 Sep 2001 00:39:27 -0700 (PDT) Received: from NDNM ([195.161.98.250]) by ns.morning.ru (8.11.5/8.11.5) with ESMTP id f8C7cpd55946; Wed, 12 Sep 2001 15:39:23 +0800 (KRAST) Date: Wed, 12 Sep 2001 15:39:12 +0800 From: Igor Podlesny X-Mailer: The Bat! (v1.53d) UNREG / CD5BF9353B3B7091 Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <17069356238.20010912153912@morning.ru> To: Jean-Francois Dive Cc: hackers@FreeBSD.ORG Subject: Re[2]: libcap question In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > From what i know, it is not. Bpf does copy the frame to make it accessible > to the pcap code and does loose this information. I however guess it is > possible to compute it from the local host information... alas, not always and not easy... > JeF > On Wed, 12 Sep 2001, Igor Podlesny wrote: >> >> Hello! >> >> I suspect that it's impossible to check out with libcap (BPF) whether >> a captured packet is incoming or outgoing, but may be it is not? >> >> -- >> Best regards, >> Igor mailto:poige@morning.ru >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> -- Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 1:34:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brinstar.nerim.net (brinstar.nerim.net [62.4.16.71]) by hub.freebsd.org (Postfix) with ESMTP id 3B48137B408; Wed, 12 Sep 2001 01:34:21 -0700 (PDT) Received: from chojin (chojin.adsl.nerim.net [62.4.22.98]) by brinstar.nerim.net (8.11.2/Raphit-20001115) with SMTP id f8C8YJx90997; Wed, 12 Sep 2001 10:34:20 +0200 (CEST) (envelope-from chojin@nerim.net) Message-ID: <002d01c13b65$c6a74070$0245a8c0@chojin> From: "Chojin" To: , Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 10:34:44 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I launched in debug mode #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l /var/log/snmpd.log You can see my snmpd.log at http://www.tarakan-network.com/snmpd.log (as it is too big for ML) There are so many informations I can't detect the problem :pp ----- Original Message ----- From: "Jean-Francois Dive" To: "Chojin" Cc: ; Sent: Wednesday, September 12, 2001 9:53 AM Subject: Re: Problem with snmpd > i think it is possible to start the snmpd and not send it to backgroud, > and see if it does printout some error messages..Otherwise use the truss > command to follow the syscalls made by the daemon while processing your > request, this could point you to a problem.. > > JeF > > On Wed, 12 Sep 2001, Chojin wrote: > > > snmpd.log is empty... > > > > I did #netstat -an | grep 161 > > udp4 0 0 *.161 *.* > > > > port 161 exists then it should work... > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" > > To: "Chojin" > > Cc: ; > > Sent: Wednesday, September 12, 2001 3:21 AM > > Subject: Re: Problem with snmpd > > > > > > > Hi, > > > > > > So you have any traces in a log file or something similar ? > > > > > > JeF > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > Hello, > > > > > > > > I have a problem with snmpd. > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any setting ), > > snmpd > > > > didn't work anymore: > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't respond. > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd with -c > > > > and -l to be sure it uses the correct files. > > > > But even if snmpd is in background process, public@localhost doesn't > > work. > > > > I don't have any firewall rule that block it. > > > > > > > > #snmpwalk localhost public > > > > Timeout: No Response from localhost > > > > #snmpget localhost public SysName > > > > Timeout: No Response from localhost. > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't change > > > > anything for snmpd. > > > > > > > > If someone has got any idea... > > > > > > > > Best regards, > > > > > > > > Chojin > > > > > > > > > > > > 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 Wed Sep 12 1:35:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id B6F6C37B40C; Wed, 12 Sep 2001 01:34:59 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8C8Z6i21164; Wed, 12 Sep 2001 10:35:06 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <003701c13b65$dd8e7100$0245a8c0@chojin> From: "Chojin" To: , Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 10:35:23 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I launched in debug mode #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l /var/log/snmpd.log You can see my snmpd.log at http://www.tarakan-network.com/snmpd.log (as it is too big for ML) There are so many informations I can't detect the problem :pp ----- Original Message ----- From: "Jean-Francois Dive" To: "Chojin" Cc: ; Sent: Wednesday, September 12, 2001 9:53 AM Subject: Re: Problem with snmpd > i think it is possible to start the snmpd and not send it to backgroud, > and see if it does printout some error messages..Otherwise use the truss > command to follow the syscalls made by the daemon while processing your > request, this could point you to a problem.. > > JeF > > On Wed, 12 Sep 2001, Chojin wrote: > > > snmpd.log is empty... > > > > I did #netstat -an | grep 161 > > udp4 0 0 *.161 *.* > > > > port 161 exists then it should work... > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" > > To: "Chojin" > > Cc: ; > > Sent: Wednesday, September 12, 2001 3:21 AM > > Subject: Re: Problem with snmpd > > > > > > > Hi, > > > > > > So you have any traces in a log file or something similar ? > > > > > > JeF > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > Hello, > > > > > > > > I have a problem with snmpd. > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any setting ), > > snmpd > > > > didn't work anymore: > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't respond. > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd with -c > > > > and -l to be sure it uses the correct files. > > > > But even if snmpd is in background process, public@localhost doesn't > > work. > > > > I don't have any firewall rule that block it. > > > > > > > > #snmpwalk localhost public > > > > Timeout: No Response from localhost > > > > #snmpget localhost public SysName > > > > Timeout: No Response from localhost. > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't change > > > > anything for snmpd. > > > > > > > > If someone has got any idea... > > > > > > > > Best regards, > > > > > > > > Chojin > > > > > > > > > > > > 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 Wed Sep 12 2:49: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta06.onebox.com (mta06.onebox.com [64.68.77.179]) by hub.freebsd.org (Postfix) with ESMTP id B3F6E37B401 for ; Wed, 12 Sep 2001 02:48:58 -0700 (PDT) Received: from onebox.com ([10.1.111.10]) by mta06.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20010912094858.WBPX12015.mta06.onebox.com@onebox.com> for ; Wed, 12 Sep 2001 02:48:58 -0700 Received: from [165.121.194.208] by onebox.com with HTTP; Wed, 12 Sep 2001 02:48:58 -0700 Date: Wed, 12 Sep 2001 02:48:58 -0700 Subject: FreeBSD-Current Install / Mouse Problem From: "glenn gombert" To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20010912094858.WBPX12015.mta06.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I have just upgraded to FreeBSD-Current, from FreeBSD-4.3 Release and have a problem getting my mouse working again. I did the buildworld, installworld, buildkernel, installkernel, etc and everything seems fine, except for my mouse daemon not working anymore.... Could someone tell me how to reinstall my mouse device (maybe in the /dev directory) and what I need to do to get my PS2 mouse working with X-Windows again?? Thanks in advance, Glenn Gombert Dayton, Ohio ___________________________________________________________________ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 3:17:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 3AA2537B406 for ; Wed, 12 Sep 2001 03:17:09 -0700 (PDT) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f8CAFN538532; Wed, 12 Sep 2001 19:15:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f8CAFNu519173; Wed, 12 Sep 2001 19:15:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:XEwuUXITw0IMgyNgDzetxGBK/HCeGdOn@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id TAA22063; Wed, 12 Sep 2001 19:25:00 +0900 (JST) Message-Id: <200109121025.TAA22063@zodiac.mech.utsunomiya-u.ac.jp> To: "glenn gombert" Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FreeBSD-Current Install / Mouse Problem In-reply-to: Your message of "Wed, 12 Sep 2001 02:48:58 MST." <20010912094858.WBPX12015.mta06.onebox.com@onebox.com> References: <20010912094858.WBPX12015.mta06.onebox.com@onebox.com> Date: Wed, 12 Sep 2001 19:24:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I have just upgraded to FreeBSD-Current, from FreeBSD-4.3 Release and >have a problem getting my mouse working again. I did the buildworld, >installworld, buildkernel, installkernel, etc and everything seems fine, >except for my mouse daemon not working anymore.... > > Could someone tell me how to reinstall my mouse device (maybe in the >/dev directory) and what I need to do to get my PS2 mouse working with >X-Windows again?? > >Thanks in advance, >Glenn Gombert >Dayton, Ohio Please do the following and send me two copies of dmesg output. Step 1. Start your system by typing "boot -v" at the loader prompt. I expect the PS/2 mouse is not recognized this time. Step 2. After the system is up, run dmesg. Step 3. Reboot the system. This time type unset acpi_load boot -v at the loader prompt. The PS/2 mouse MAY be recognized. Step 4. After the system is up, run dmesg. Send dmesg output obtained in the step 2 and 4. If your PS/2 mouse is recognized in step 3, put the following line in /boot/device.hints until ACPI issues are resolved. hint.acpi.0.disable=1 Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 7:59:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id DA24D37B40D; Wed, 12 Sep 2001 07:59:06 -0700 (PDT) Received: from fwd02.sul.t-online.de by mailout06.sul.t-online.de with smtp id 15hBTj-0000ne-0D; Wed, 12 Sep 2001 16:59:03 +0200 Received: from goofy.disney.gb (320066129553-0001@[217.81.129.140]) by fwd02.sul.t-online.com with esmtp id 15hBTb-1tCxTUC; Wed, 12 Sep 2001 16:58:55 +0200 Received: from guenter (helo=localhost) by goofy.disney.gb with local-esmtp (Exim 3.31 #1 (Debian)) id 15hBTa-0006KP-00; Wed, 12 Sep 2001 16:58:54 +0200 Date: Wed, 12 Sep 2001 16:58:54 +0200 (CEST) From: bartscgr@t-online.de (Guenter Bartsch) X-X-Sender: Reply-To: To: Heiko Schaefer Cc: , Robert Edmonds , xine-user , Subject: Re: [xine-user] xine on freebsd? In-Reply-To: <20010912154515.X1528-100000@daneel.foundation.hs> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320066129553-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On Wed, 12 Sep 2001, Heiko Schaefer wrote: > > has anyone got xine to play DVDs on freebsd? videolan can play DVDs on > > freebsd.. but the playback sucks even on a 500 mhz machine. > > by now, xine runs pretty nicely on freebsd. however, unfortunately not > quite as well as on linux > i am currently trying to find reasons for this lack of performance on > freebsd compared to linux and am mostly stuck with the theory that agp > support is not really the same as on linux. maybe someone who knows more > about xfree, agp and freebsd will eventually comment on this or propose a > solution. any input on this would be welcome... even when using XvShm to display the video data xfree86 uses significantly more cpu power on freebsd than on linux (~15% on freebsd compared to ~1-3% on linux) which further indicates there's something wrong here. Comments, hints, ideas very welcome, Guenter -- time is a funny concept To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 8:19:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id 8616537B407; Wed, 12 Sep 2001 08:19:25 -0700 (PDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id f8CFJ6g14468; Wed, 12 Sep 2001 11:19:07 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8CFJ5f08471; Wed, 12 Sep 2001 11:19:05 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 7696702; Wed, 12 Sep 2001 11:19:04 -0400 Message-ID: <3B9F7CE8.E96D1B0@mitre.org> Date: Wed, 12 Sep 2001 11:19:04 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: bartscgr@studbox.uni-stuttgart.de Cc: Heiko Schaefer , multimedia@freebsd.org, Robert Edmonds , xine-user , freebsd-hackers@freebsd.org Subject: Re: [xine-user] xine on freebsd? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Guenter Bartsch wrote: > > Hi, > > On Wed, 12 Sep 2001, Heiko Schaefer wrote: > > > > has anyone got xine to play DVDs on freebsd? videolan can play DVDs on > > > freebsd.. but the playback sucks even on a 500 mhz machine. > > > > by now, xine runs pretty nicely on freebsd. however, unfortunately not > > quite as well as on linux > > > i am currently trying to find reasons for this lack of performance on > > freebsd compared to linux and am mostly stuck with the theory that agp > > support is not really the same as on linux. maybe someone who knows more > > about xfree, agp and freebsd will eventually comment on this or propose a > > solution. any input on this would be welcome... > > even when using XvShm to display the video data xfree86 uses significantly > more cpu power on freebsd than on linux (~15% on freebsd compared to ~1-3% > on linux) which further indicates there's something wrong here. > > Comments, hints, ideas very welcome, Are you using XFree 4.x? What video cards are in both boxes? Are they the same box just dual booting? I've found that XFree 3.x is a processor pig on my system, but XFree 4.x is nice and light, particularly with Xv. I'm using a Matrox G200 with the slightly older Matrox HAL. Sometimes I wonder if Linux puts more of a buffer on DVDs than FreeBSD does, given the way that most of the linux DVD programs are written (read, decode, display, continue) they tend to IO starve themselves under FreeBSD. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 8:48:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 9550937B406; Wed, 12 Sep 2001 08:48:45 -0700 (PDT) Received: from mindspring.com (dialup-209.247.142.20.Dial1.SanJose1.Level3.net [209.247.142.20]) by pintail.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id IAA05511; Wed, 12 Sep 2001 08:48:24 -0700 (PDT) Message-ID: <3B9F83F4.70585613@mindspring.com> Date: Wed, 12 Sep 2001 08:49:08 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jason Andresen Cc: bartscgr@studbox.uni-stuttgart.de, Heiko Schaefer , multimedia@freebsd.org, Robert Edmonds , xine-user , freebsd-hackers@freebsd.org Subject: Re: [xine-user] xine on freebsd? References: <3B9F7CE8.E96D1B0@mitre.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Andresen wrote: > Are you using XFree 4.x? What video cards are in both boxes? > Are they the same box just dual booting? I've found that XFree > 3.x is a processor pig on my system, but XFree 4.x is nice and > light, particularly with Xv. I'll echo the 3.x vs. 4.x observation. > Sometimes I wonder if Linux puts more of a buffer on DVDs than > FreeBSD does, given the way that most of the linux DVD programs > are written (read, decode, display, continue) they tend to IO > starve themselves under FreeBSD. Double buffering the I/O is a definite win. This is really an application space issue, since you want to buffer at least two key frames and the associated deltas... Linux tends to do this automatically. I've also noticed that Linux tends to precache the index data (just like the MACH paper that cached the entire FAT for an MSDOSFS and turned off UFS cacheing as "unfair", in order to "prove" that MSDOSFS was "faster" than UFS), which may be a good idea, or at least a useful mount option. Also, look at the optimization options chosen by configure in Linux vs. FreeBSD for compiling the player. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 9:22: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout00.sul.t-online.de (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 3A63437B40B; Wed, 12 Sep 2001 09:21:56 -0700 (PDT) Received: from fwd02.sul.t-online.de by mailout00.sul.t-online.de with smtp id 15hCaH-0000w9-0C; Wed, 12 Sep 2001 18:09:53 +0200 Received: from goofy.disney.gb (320066129553-0001@[217.81.129.140]) by fwd02.sul.t-online.com with esmtp id 15hCZg-02IRKiC; Wed, 12 Sep 2001 18:09:16 +0200 Received: from guenter (helo=localhost) by goofy.disney.gb with local-esmtp (Exim 3.31 #1 (Debian)) id 15hCZf-0006Ov-00; Wed, 12 Sep 2001 18:09:15 +0200 Date: Wed, 12 Sep 2001 18:09:15 +0200 (CEST) From: bartscgr@t-online.de (Guenter Bartsch) X-X-Sender: Reply-To: To: Jason Andresen Cc: , Heiko Schaefer , , xine-user , Subject: Re: [xine-user] xine on freebsd? In-Reply-To: <3B9F7CE8.E96D1B0@mitre.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320066129553-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Jason, On Wed, 12 Sep 2001, Jason Andresen wrote: > > even when using XvShm to display the video data xfree86 uses significantly > > more cpu power on freebsd than on linux (~15% on freebsd compared to ~1-3% > > on linux) which further indicates there's something wrong here. > > > > Comments, hints, ideas very welcome, > > Are you using XFree 4.x? yep, xfree 4.1 exactly > What video cards are in both boxes? in my box it's a riva TNT (so I don't have Xv on FreeBSD), but in Heiko's box (where we do most of the performance testing) we've seen these results both with a GeForce 2MX and a Matrox G400 on a GNU/Linux / FreeBSD dual boot machine (first there we used the GeForce card and later replaced it by the G400 one but the results were roughly the same). > Sometimes I wonder if Linux puts more of a buffer on DVDs than FreeBSD > does yep, on linux there's hardly any difference between reading single block or larger chunks of data from the device, even when using raw devices. FreeBSD seems to have trouble reading single blocks here, but with xine's new dvd read_cache that heiko mentioned xine reads data in 16kb chunks and the device read performance is roughly the same as on linux now. The only thing that is still significantly slower on freebsd is the actual frame display on X11. For full-PAL (720x576) images xine easily decodes all frames on heiko's box but throws away 30% of them because X11 is too slow to display them in time - this indicates to me that there's something wrong with X11 shared memory support on FreeBSD here. Somehow I get the feeling that there are extra memcpys involved here - maybe the MTRR isn't set up correctly so the CPU caches the display data or, more likely, the CPU is used to copy to images into the framebuffer instead of letting the graphic's card do the work via dma/agp. Any ideas? Cheers, Guenter -- time is a funny concept To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 10:58:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 9F13937B40B for ; Wed, 12 Sep 2001 10:57:57 -0700 (PDT) Received: from hades.hell.gr (patr530-a172.otenet.gr [212.205.215.172]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8CHvsx29978 for ; Wed, 12 Sep 2001 20:57:54 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8CHvhU65013 for hackers@freebsd.org; Wed, 12 Sep 2001 20:57:43 +0300 (EEST) (envelope-from charon@labs.gr) Date: Wed, 12 Sep 2001 20:57:43 +0300 From: Giorgos Keramidas To: hackers@freebsd.org Subject: Checking changes to listening ports in /etc/security Message-ID: <20010912205743.A64992@hades.hell.gr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've been adding an extra check in my local version of /etc/security for quite some time now. All it does is use 'netstat' to grab a list of the listening tcp and udp ports of my machine and save it to /var/log/netstat.today (and /var/log/netstat.yesterday). This way, when some service starts and listens on a new port the next run of /etc/security will log the fact in the usual stuff sent to root by mail. I tested this running /etc/periodic/daily/450.security twice, and running a local IRC daemon between the two runs. The output that is added to the message root receives looks like the following: hades.hell.gr changes in listening ports: 4a5,6 > tcp4 0 0 *.6667 *.* LISTEN > tcp4 0 0 *.7325 *.* LISTEN 7a10 > udp4 0 0 *.* *.* 10a14 > udp4 0 0 *.7007 *.* Does the attached patch below seem interesting to anyone else, too? Should I send-pr it, or just keep merging it with my own security checks, and leave things as they are? -giorgos --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=lala Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.55 diff -u -r1.55 security --- security 4 Jul 2001 12:49:17 -0000 1.55 +++ security 12 Sep 2001 17:25:53 -0000 @@ -128,6 +128,26 @@ tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 +# Show changes in listening tcp and udp ports: +# +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat +if ( netstat -natl | grep LISTEN | sort ; echo "--"; netstat -na | grep '^udp' | sort ) | $cmd > $TMP; then + if [ ! -f $LOG/netstat.today ]; then + [ $rc -lt 1 ] && rc=1 + separator + echo "No $LOG/netstat.today" + cp $TMP $LOG/netstat.today || rc=3 + fi + if ! cmp $LOG/netstat.today $TMP >/dev/null 2>&1; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b $LOG/netstat.today $TMP + mv $LOG/netstat.today $LOG/netstat.yesterday || rc=3 + mv $TMP $LOG/netstat.today || rc=3 + fi +fi + # Show denied packets # if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then --Kj7319i9nmIyA2yE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 11:20: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id D101537B405; Wed, 12 Sep 2001 11:19:29 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8CIJPr61504; Wed, 12 Sep 2001 20:19:26 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <00af01c13bb7$83665420$0245a8c0@chojin> From: "Chojin" To: "Jean-Francois Dive" , , References: Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 20:19:50 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I used TMRTGCHO as community name before, but since I've got this problem I use now public. Request from localhost or any other interface doesn't work. I cleaned snmpd.log, restarted snmpd: #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l /var/log/snmpd.log and a new one is located at http://www.tarakan-network.com/snmpd.log (I did a snmpwalk and snmpget for public@localhost but no success) ----- Original Message ----- From: "Jean-Francois Dive" To: "Chojin" Sent: Wednesday, September 12, 2001 10:38 AM Subject: Re: Problem with snmpd > Hi (salut) > > In fact, i see some successfull request with the community: > TMRTGCHO and no attemps with the localhost one... seems pretty odd. did > you only got those requests from localhost not working ? > > Otherwise, purge the log file, be *sure* that no requests are comming from > somewhere else and resart to see some failures... > > JeF > > On Wed, 12 Sep 2001, Chojin wrote: > > > I launched in debug mode > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > /var/log/snmpd.log > > I attached snmpd.log > > There are so many informations I can't detect the problem :pp > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" > > To: "Chojin" > > Cc: ; > > Sent: Wednesday, September 12, 2001 9:53 AM > > Subject: Re: Problem with snmpd > > > > > > > i think it is possible to start the snmpd and not send it to backgroud, > > > and see if it does printout some error messages..Otherwise use the truss > > > command to follow the syscalls made by the daemon while processing your > > > request, this could point you to a problem.. > > > > > > JeF > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > snmpd.log is empty... > > > > > > > > I did #netstat -an | grep 161 > > > > udp4 0 0 *.161 *.* > > > > > > > > port 161 exists then it should work... > > > > > > > > ----- Original Message ----- > > > > From: "Jean-Francois Dive" > > > > To: "Chojin" > > > > Cc: ; > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > Hi, > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > JeF > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > setting ), > > > > snmpd > > > > > > didn't work anymore: > > > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't > > respond. > > > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd > > with -c > > > > > > and -l to be sure it uses the correct files. > > > > > > But even if snmpd is in background process, public@localhost > > doesn't > > > > work. > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > #snmpwalk localhost public > > > > > > Timeout: No Response from localhost > > > > > > #snmpget localhost public SysName > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't > > change > > > > > > anything for snmpd. > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > 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 Wed Sep 12 11:23:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 1017C37B401 for ; Wed, 12 Sep 2001 11:23:26 -0700 (PDT) Received: (qmail 24146 invoked by uid 1001); 12 Sep 2001 18:23:24 -0000 Date: 12 Sep 2001 11:23:24 -0700 Date: Wed, 12 Sep 2001 11:23:24 -0700 From: Bill Swingle To: Giorgos Keramidas Cc: hackers@freebsd.org Subject: Re: Checking changes to listening ports in /etc/security Message-ID: <20010912112324.A24009@dub.net> References: <20010912205743.A64992@hades.hell.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010912205743.A64992@hades.hell.gr>; from charon@labs.gr on Wed, Sep 12, 2001 at 08:57:43PM +0300 X-Operating-System: FreeBSD toxic.magnesium.net 4.3-STABLE FreeBSD 4.3-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Why not use sockstat instead of netstat? -Bill On Wed, Sep 12, 2001 at 08:57:43PM +0300, Giorgos Keramidas wrote: >=20 > I've been adding an extra check in my local version of /etc/security for = quite > some time now. All it does is use 'netstat' to grab a list of the listen= ing > tcp and udp ports of my machine and save it to /var/log/netstat.today > (and /var/log/netstat.yesterday). This way, when some service starts > and listens on a new port the next run of /etc/security will log the > fact in the usual stuff sent to root by mail. I tested this running > /etc/periodic/daily/450.security twice, and running a local IRC daemon be= tween > the two runs. The output that is added to the message root receives looks > like the following: >=20 > hades.hell.gr changes in listening ports: > 4a5,6 > > tcp4 0 0 *.6667 *.* = LISTEN > > tcp4 0 0 *.7325 *.* = LISTEN > 7a10 > > udp4 0 0 *.* *.* = =20 > 10a14 > > udp4 0 0 *.7007 *.* = =20 >=20 > Does the attached patch below seem interesting to anyone else, too? > Should I send-pr it, or just keep merging it with my own security checks, > and leave things as they are? >=20 > -giorgos > Index: security > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/etc/security,v > retrieving revision 1.55 > diff -u -r1.55 security > --- security 4 Jul 2001 12:49:17 -0000 1.55 > +++ security 12 Sep 2001 17:25:53 -0000 > @@ -128,6 +128,26 @@ > tee /dev/stderr | wc -l) > [ $n -gt 0 -a $rc -lt 1 ] && rc=3D1 > =20 > +# Show changes in listening tcp and udp ports: > +# > +[ -n "$ignore" ] && cmd=3D"egrep -v ${ignore#|}" || cmd=3Dcat > +if ( netstat -natl | grep LISTEN | sort ; echo "--"; netstat -na | grep = '^udp' | sort ) | $cmd > $TMP; then > + if [ ! -f $LOG/netstat.today ]; then > + [ $rc -lt 1 ] && rc=3D1 > + separator > + echo "No $LOG/netstat.today" > + cp $TMP $LOG/netstat.today || rc=3D3 > + fi > + if ! cmp $LOG/netstat.today $TMP >/dev/null 2>&1; then > + [ $rc -lt 1 ] && rc=3D1 > + separator > + echo "$host changes in listening ports:" > + diff -b $LOG/netstat.today $TMP > + mv $LOG/netstat.today $LOG/netstat.yesterday || rc=3D3 > + mv $TMP $LOG/netstat.today || rc=3D3 > + fi > +fi > + > # Show denied packets > # > if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then --=20 -=3D| Bill Swingle - -=3D| Every message PGP signed -=3D| Fingerprint: C1E3 49D1 EFC9 3EE0 EA6E 6414 5200 1C95 8E09 0223 -=3D| Different all twisty a of in maze are you, passages little --SUOF0GtieIMvvwua Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7n6gcUgAclY4JAiMRAlf9AKDBFY4pmdNx82xTRla3ZOMBcGjNFACdHDEQ dhIGKjE9v04YfZEGne4MqhM= =cQxp -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 11:34:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 5752337B405; Wed, 12 Sep 2001 11:34:17 -0700 (PDT) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8CIX9571056; Wed, 12 Sep 2001 14:33:09 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8CIYm044706; Wed, 12 Sep 2001 14:34:48 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Wed, 12 Sep 2001 14:34:48 -0400 (EDT) From: Joe Clarke To: Chojin Cc: Jean-Francois Dive , , Subject: Re: Problem with snmpd In-Reply-To: <00af01c13bb7$83665420$0245a8c0@chojin> Message-ID: <20010912143244.B43876-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can you send your snmp.conf file? These are the relevant bits of mine: com2sec local localhost public com2sec localrw localhost private com2sec mynetwork 172.18.0.0/24 public com2sec mynetworkrw 172.18.0.0/24 private #### # Second, map the security names into group names: # sec.model sec.name group LocalRWGroup v1 localrw group LocalRWGroup v2c localrw group LocalRWGroup usm localrw group LocalROGroup v1 local group LocalROGroup v2c local group LocalROGroup usm local group NetROGroup v1 mynetwork group NetROGroup v2c mynetwork group NetROGroup usm mynetwork group NetRWGroup v1 mynetworkrw group NetRWGroup v2c mynetworkrw group NetRWGroup usm mynetworkrw #### # Third, create a view for us to let the groups have rights to: # incl/excl subtree mask view all included .1 80 #### # Finally, grant the 2 groups access to the 1 view with different # write permissions: # context sec.model sec.level match read write notif access LocalROGroup "" any noauth exact all none none access LocalRWGroup "" any noauth exact all all none access NetROGroup "" any noauth exact all none none access NetRWGroup "" any noauth exact all all none public@localhost does work on my machine. Joe On Wed, 12 Sep 2001, Chojin wrote: > I used TMRTGCHO as community name before, but since I've got this problem I > use now public. > Request from localhost or any other interface doesn't work. > I cleaned snmpd.log, restarted snmpd: > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > /var/log/snmpd.log > > and a new one is located at http://www.tarakan-network.com/snmpd.log (I did > a snmpwalk and snmpget for public@localhost but no success) > > ----- Original Message ----- > From: "Jean-Francois Dive" > To: "Chojin" > Sent: Wednesday, September 12, 2001 10:38 AM > Subject: Re: Problem with snmpd > > > > Hi (salut) > > > > In fact, i see some successfull request with the community: > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. did > > you only got those requests from localhost not working ? > > > > Otherwise, purge the log file, be *sure* that no requests are comming from > > somewhere else and resart to see some failures... > > > > JeF > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > I launched in debug mode > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > /var/log/snmpd.log > > > I attached snmpd.log > > > There are so many informations I can't detect the problem :pp > > > > > > ----- Original Message ----- > > > From: "Jean-Francois Dive" > > > To: "Chojin" > > > Cc: ; > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > Subject: Re: Problem with snmpd > > > > > > > > > > i think it is possible to start the snmpd and not send it to > backgroud, > > > > and see if it does printout some error messages..Otherwise use the > truss > > > > command to follow the syscalls made by the daemon while processing > your > > > > request, this could point you to a problem.. > > > > > > > > JeF > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > snmpd.log is empty... > > > > > > > > > > I did #netstat -an | grep 161 > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > ----- Original Message ----- > > > > > From: "Jean-Francois Dive" > > > > > To: "Chojin" > > > > > Cc: ; > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > JeF > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > setting ), > > > > > snmpd > > > > > > > didn't work anymore: > > > > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't > > > respond. > > > > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd > > > with -c > > > > > > > and -l to be sure it uses the correct files. > > > > > > > But even if snmpd is in background process, public@localhost > > > doesn't > > > > > work. > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > Timeout: No Response from localhost > > > > > > > #snmpget localhost public SysName > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't > > > change > > > > > > > anything for snmpd. > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > 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-questions" 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 Wed Sep 12 12:12:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sploot.vicor-nb.com (sploot.vicor-nb.com [208.206.78.81]) by hub.freebsd.org (Postfix) with ESMTP id 48E9637B401; Wed, 12 Sep 2001 12:12:30 -0700 (PDT) Received: from vicor-nb.com (localhost [127.0.0.1]) by sploot.vicor-nb.com (8.11.1/8.9.3) with ESMTP id f8CJ8wc29726; Wed, 12 Sep 2001 12:08:58 -0700 (PDT) (envelope-from kmarx@vicor-nb.com) Message-ID: <3B9FB2C9.C87A4@vicor-nb.com> Date: Wed, 12 Sep 2001 12:08:58 -0700 From: Ken Marx X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" , freebsd-hackers@FreeBSD.ORG Cc: kmarx@vicor-nb.com Subject: palm: pose Abort trap Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has anyone successfully run pose for palm on Release4.2? I'm just beginning at trying to understand the world of palm. I downloaded roms and skins and can't get anything but Abort trap, when trying to set the configuration from the pulldown menu. (Actually, if I run as root, and specify the rom at the command line, I can get it to load a skin. But I still get no response to kb/mouse activity, and changing config results in the same abort.) So, all it seems to emulate with any success is core dumps. This is pose version 3.0a6. I tried downloading/building 3.3 from the palm site (http://www.palmos.com/dev/tech/tools/emulator/): After an hour of fixing config and X11R6/include/Fl include files, gave up when the build hit this: --------------- ./../SrcShared/MetaMemory.cpp: In function `static enum Errors::EAccessType MetaMemory::AllowForBugs(long unsigned int, long int, int, Errors::EAccessType)': ./../SrcShared/MetaMemory.cpp:428: Internal compiler error. ./../SrcShared/MetaMemory.cpp:428: Please submit a full bug report. ./../SrcShared/MetaMemory.cpp:428: See for instructions. ----------- (You know, I'm still waiting for a response on the 'full bug report' I 'submit'ed them 3 years ago.) Anyway the above error happens where it's trying to figure out something to do with "::InPrvFindMemoryLeaks ()", which truly is mentioned nowhere else in that pose source. Any help/ideas greatly appreciated (including what other mail lists I could address this to. I couldn't figure that out either.) k. -- Ken Marx, kmarx@vicor-nb.com This group must improve our denominator as well as our numerator - with an emphasis on the denominator - and keep the faith regarding the industry's convergence. - http://cgi.bigshed.com/~kmarx/cgi-bin/speak.cgi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 12:17:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 6BF1D37B407; Wed, 12 Sep 2001 12:16:49 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8CJGar66870; Wed, 12 Sep 2001 21:16:36 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <015f01c13bbf$808e5b50$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010912143244.B43876-100000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 21:17:01 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My snmpd.conf: syslocation France syscontact root@tarakan-network.com rocommunity public localhost ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Wednesday, September 12, 2001 8:34 PM Subject: Re: Problem with snmpd > Can you send your snmp.conf file? These are the relevant bits of mine: > > com2sec local localhost public > com2sec localrw localhost private > com2sec mynetwork 172.18.0.0/24 public > com2sec mynetworkrw 172.18.0.0/24 private > > #### > # Second, map the security names into group names: > > # sec.model sec.name > group LocalRWGroup v1 localrw > group LocalRWGroup v2c localrw > group LocalRWGroup usm localrw > group LocalROGroup v1 local > group LocalROGroup v2c local > group LocalROGroup usm local > group NetROGroup v1 mynetwork > group NetROGroup v2c mynetwork > group NetROGroup usm mynetwork > group NetRWGroup v1 mynetworkrw > group NetRWGroup v2c mynetworkrw > group NetRWGroup usm mynetworkrw > > #### > # Third, create a view for us to let the groups have rights to: > > # incl/excl subtree mask > view all included .1 80 > > #### > # Finally, grant the 2 groups access to the 1 view with different > # write permissions: > > # context sec.model sec.level match read write notif > access LocalROGroup "" any noauth exact all none none > access LocalRWGroup "" any noauth exact all all none > access NetROGroup "" any noauth exact all none none > access NetRWGroup "" any noauth exact all all none > > > public@localhost does work on my machine. > > Joe > > On Wed, 12 Sep 2001, Chojin wrote: > > > I used TMRTGCHO as community name before, but since I've got this problem I > > use now public. > > Request from localhost or any other interface doesn't work. > > I cleaned snmpd.log, restarted snmpd: > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > /var/log/snmpd.log > > > > and a new one is located at http://www.tarakan-network.com/snmpd.log (I did > > a snmpwalk and snmpget for public@localhost but no success) > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" > > To: "Chojin" > > Sent: Wednesday, September 12, 2001 10:38 AM > > Subject: Re: Problem with snmpd > > > > > > > Hi (salut) > > > > > > In fact, i see some successfull request with the community: > > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. did > > > you only got those requests from localhost not working ? > > > > > > Otherwise, purge the log file, be *sure* that no requests are comming from > > > somewhere else and resart to see some failures... > > > > > > JeF > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > I launched in debug mode > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > /var/log/snmpd.log > > > > I attached snmpd.log > > > > There are so many informations I can't detect the problem :pp > > > > > > > > ----- Original Message ----- > > > > From: "Jean-Francois Dive" > > > > To: "Chojin" > > > > Cc: ; > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > backgroud, > > > > > and see if it does printout some error messages..Otherwise use the > > truss > > > > > command to follow the syscalls made by the daemon while processing > > your > > > > > request, this could point you to a problem.. > > > > > > > > > > JeF > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jean-Francois Dive" > > > > > > To: "Chojin" > > > > > > Cc: ; > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > > setting ), > > > > > > snmpd > > > > > > > > didn't work anymore: > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't > > > > respond. > > > > > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd > > > > with -c > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > But even if snmpd is in background process, public@localhost > > > > doesn't > > > > > > work. > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > Timeout: No Response from localhost > > > > > > > > #snmpget localhost public SysName > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't > > > > change > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" 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 Wed Sep 12 12:30:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id D6F5937B401; Wed, 12 Sep 2001 12:30:00 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8CJTrr68083; Wed, 12 Sep 2001 21:29:53 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <017801c13bc1$5bc3a580$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010912143244.B43876-100000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Wed, 12 Sep 2001 21:30:03 +0200 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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I tried your snmpd.conf but with no success :'( ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Wednesday, September 12, 2001 8:34 PM Subject: Re: Problem with snmpd > Can you send your snmp.conf file? These are the relevant bits of mine: > > com2sec local localhost public > com2sec localrw localhost private > com2sec mynetwork 172.18.0.0/24 public > com2sec mynetworkrw 172.18.0.0/24 private > > #### > # Second, map the security names into group names: > > # sec.model sec.name > group LocalRWGroup v1 localrw > group LocalRWGroup v2c localrw > group LocalRWGroup usm localrw > group LocalROGroup v1 local > group LocalROGroup v2c local > group LocalROGroup usm local > group NetROGroup v1 mynetwork > group NetROGroup v2c mynetwork > group NetROGroup usm mynetwork > group NetRWGroup v1 mynetworkrw > group NetRWGroup v2c mynetworkrw > group NetRWGroup usm mynetworkrw > > #### > # Third, create a view for us to let the groups have rights to: > > # incl/excl subtree mask > view all included .1 80 > > #### > # Finally, grant the 2 groups access to the 1 view with different > # write permissions: > > # context sec.model sec.level match read write notif > access LocalROGroup "" any noauth exact all none none > access LocalRWGroup "" any noauth exact all all none > access NetROGroup "" any noauth exact all none none > access NetRWGroup "" any noauth exact all all none > > > public@localhost does work on my machine. > > Joe > > On Wed, 12 Sep 2001, Chojin wrote: > > > I used TMRTGCHO as community name before, but since I've got this problem I > > use now public. > > Request from localhost or any other interface doesn't work. > > I cleaned snmpd.log, restarted snmpd: > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > /var/log/snmpd.log > > > > and a new one is located at http://www.tarakan-network.com/snmpd.log (I did > > a snmpwalk and snmpget for public@localhost but no success) > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" > > To: "Chojin" > > Sent: Wednesday, September 12, 2001 10:38 AM > > Subject: Re: Problem with snmpd > > > > > > > Hi (salut) > > > > > > In fact, i see some successfull request with the community: > > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. did > > > you only got those requests from localhost not working ? > > > > > > Otherwise, purge the log file, be *sure* that no requests are comming from > > > somewhere else and resart to see some failures... > > > > > > JeF > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > I launched in debug mode > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > /var/log/snmpd.log > > > > I attached snmpd.log > > > > There are so many informations I can't detect the problem :pp > > > > > > > > ----- Original Message ----- > > > > From: "Jean-Francois Dive" > > > > To: "Chojin" > > > > Cc: ; > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > backgroud, > > > > > and see if it does printout some error messages..Otherwise use the > > truss > > > > > command to follow the syscalls made by the daemon while processing > > your > > > > > request, this could point you to a problem.. > > > > > > > > > > JeF > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jean-Francois Dive" > > > > > > To: "Chojin" > > > > > > Cc: ; > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > > setting ), > > > > > > snmpd > > > > > > > > didn't work anymore: > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't > > > > respond. > > > > > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd > > > > with -c > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > But even if snmpd is in background process, public@localhost > > > > doesn't > > > > > > work. > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > Timeout: No Response from localhost > > > > > > > > #snmpget localhost public SysName > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't > > > > change > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Wed Sep 12 15:15:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 078FD37B403 for ; Wed, 12 Sep 2001 15:15:20 -0700 (PDT) Received: from hades.hell.gr (patr530-b016.otenet.gr [195.167.121.144]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8CMFGx12359; Thu, 13 Sep 2001 01:15:16 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8CMEbC02003; Thu, 13 Sep 2001 01:14:37 +0300 (EEST) (envelope-from charon@labs.gr) Date: Thu, 13 Sep 2001 01:14:37 +0300 From: Giorgos Keramidas To: Bill Swingle Cc: hackers@freebsd.org Subject: Re: Checking changes to listening ports in /etc/security Message-ID: <20010913011436.A1792@hades.hell.gr> References: <20010912205743.A64992@hades.hell.gr> <20010912112324.A24009@dub.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="BQPnanjtCNWHyqYD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010912112324.A24009@dub.net>; from unfurl@dub.net on Wed, Sep 12, 2001 at 11:23:24AM -0700 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --BQPnanjtCNWHyqYD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable From: Bill Swingle Subject: Re: Checking changes to listening ports in /etc/security Date: Wed, Sep 12, 2001 at 11:23:24AM -0700 > Why not use sockstat instead of netstat? >=20 > -Bill Simple. Because I had forgotten of sockstat. Probably because I've been using netstat on linuxen, solaris, and everywhere else. Now that I tried sockstat, I changed my /etc/security to remove netstat and include a sockstat using part. I tested the attached patch, and now I have only one little fine point to refine. When the sockstat test runs, Sendmail will open connections to comsat (if that's enabled in the local sendmail.cf). If I keep the included 'grep -v comsat' it will not print extra lines for comsat connections. However, if someone else opens a udp listening socket = on comsat port, it will not be detected by diff. On the other hand, leaving t= he grep -v out, might cause false alarms to be brought up in security output. I tend to prefer the one that includes comsat in the output[2]. The second attachment shows what the output of /etc/security looks like (wi= th the comsat output lines included). I rather like the idea about sockstat. Thank you, Bill. We now might just have a version that is good enough for a PR. Any comments on the sockstat-using diffs, Bill (or anyone else)? -giorgos --BQPnanjtCNWHyqYD Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-ab Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.55 diff -u -r1.55 security --- security 4 Jul 2001 12:49:17 -0000 1.55 +++ security 12 Sep 2001 22:00:50 -0000 @@ -128,6 +128,28 @@ tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 +# Show changes in listening tcp and udp ports: +# +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat +if ( sockstat -l46 | head -1 ;\ + sockstat -l46 | grep -v comsat | grep -v '^$' |\ + grep -v '^USER' | sort +5 ) | $cmd > $TMP ;then + if [ ! -f $LOG/sockstat.today ]; then + [ $rc -lt 1 ] && rc=1 + separator + echo "No $LOG/sockstat.today" + cp $TMP $LOG/sockstat.today || rc=3 + fi + if ! cmp $LOG/sockstat.today $TMP >/dev/null 2>&1; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b $LOG/sockstat.today $TMP + mv $LOG/sockstat.today $LOG/sockstat.yesterday || rc=3 + mv $TMP $LOG/sockstat.today || rc=3 + fi +fi + # Show denied packets # if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then --BQPnanjtCNWHyqYD Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=lala hades.hell.gr changes in listening ports: 7a8,10 > tty comsat 1504 0 udp4 *:512 *:* > tty comsat 1504 1 udp4 *:512 *:* > tty comsat 1504 2 udp4 *:512 *:* --BQPnanjtCNWHyqYD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 12 18:44:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C3CFF37B410; Wed, 12 Sep 2001 18:44:10 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA21526; Thu, 13 Sep 2001 11:14:00 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 13 Sep 2001 11:13:59 +0930 (CST) From: "Daniel O'Connor" To: bartscgr@studbox.uni-stuttgart.de Subject: Re: [xine-user] xine on freebsd? Cc: freebsd-hackers@freebsd.org, Robert Edmonds , multimedia@freebsd.org, Heiko Schaefer , xine-user Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12-Sep-2001 Guenter Bartsch wrote: > even when using XvShm to display thevideo data xfree86 uses significantly > more cpu power on freebsd than on linux (~15% on freebsd compared to ~1-3% > on linux) which further indicates there's something wrong here. > > Comments, hints, ideas very welcome, My personal recommendation is to use mplayer. (ports/graphics/mplayer). It _rocks_ :) The SDL video renderer supports the Xv extension and can go fullscreen and the press of a key. I haven't had this program crash once yet even after feeding it some pretty nasty movie files. [xine-users@ ignore this paragraph please ;) ] As to your actual question.. How to you know the Linux and FreeBSD top's are measuring the same thing? top is a very poor way to measure CPU usage, a much better idea would be to play the movie and then exit, and measure the total CPU time used for that activity. This would be moderatly difficult for Xfree86, but maybe do something like.. 1) Edit .xinitrc to run xine with the movie as it's only activity. 2) Run /usr/bin/time startx Compare the numbers between the two systems :) Also, are you sure that you have enough shared memory on the freebsd box? By default the amount of shm you can use is fairly small, and if you use GNOME it will easily eat it all. --- 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 Wed Sep 12 20:41:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 7BAE437B401; Wed, 12 Sep 2001 20:41:05 -0700 (PDT) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id UAA07532; Wed, 12 Sep 2001 20:40:16 -0700 (PDT) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id UAA17676; Wed, 12 Sep 2001 20:27:14 -0700 (PDT) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id VAA29435; Wed, 12 Sep 2001 21:40:11 -0600 (MDT) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id ; Wed, 12 Sep 2001 21:40:13 -0600 Message-ID: <50486691668CD511BB660000D11ABE92147246@btcexc01.btc.adaptec.com> From: "Long, Scott" To: "'Daniel O'Connor'" , bartscgr@studbox.uni-stuttgart.de Cc: freebsd-hackers@freebsd.org, Robert Edmonds , multimedia@freebsd.org, Heiko Schaefer , xine-user Subject: RE: [xine-user] xine on freebsd? Date: Wed, 12 Sep 2001 21:40:12 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Also, are you sure that you have enough shared memory on the freebsd box? By > default the amount of shm you can use is fairly small, and if you use GNOME it > will easily eat it all. I can't agree with this statement more. Gnome/GTK is a pig on SHM, and the FreeBSD default make relatively low amounts of memory and segments available. There are various kernel options and tunables that can be set to ajust this. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 4:39:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.redstar.spb.ru (relay.redstar.spb.ru [195.131.87.225]) by hub.freebsd.org (Postfix) with ESMTP id D511C37B407 for ; Thu, 13 Sep 2001 04:39:20 -0700 (PDT) Received: from dmitry (dimon.redstar.spb.ru [192.168.120.5]) by relay.redstar.spb.ru (8.11.6/8.11.1) with ESMTP id f8DBgLw02464 for ; Thu, 13 Sep 2001 15:42:23 +0400 (MSD) (envelope-from BSD@redstar.spb.ru) Date: Thu, 13 Sep 2001 15:40:45 +0400 From: Dmitry Shubin X-Mailer: The Bat! (v1.44) Educational Reply-To: Dmitry Shubin X-Priority: 3 (Normal) Message-ID: <3614699146.20010913154045@redstar.spb.ru> To: freebsd-hackers@FreeBSD.org Subject: Problems with RSA and OpenSSH Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello freebsd-hackers, I've CVSupped RELENG_4_3. I've installed last port of OpenSSH 2.9_3. And when I tried to start sshd, I've got a message: Could not load host key: /usr/local/etc/ssh_host_rsa_key There are no such file in /usr/local/etc. I thought, that there some problems with RSA and OpenSSL. I've looked at /usr/src/crypto/openssl in my system and at ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/crypto/openssl/ And I saw that I have no rsaref folder in my openssl. Who knows, what's the problem? -- Best regards, Dmitry mailto:BSD@redstar.spb.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 8:37: 1 2001 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 38AC337B412 for ; Thu, 13 Sep 2001 08:36:56 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f8DFaqK01715 for ; Thu, 13 Sep 2001 11:36:52 -0400 (EDT) Date: Thu, 13 Sep 2001 11:36:51 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: Kernel module debug help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am debugging a KLD and I have got the following panic inside an interrupt context: fault virutal address = 0x1080050 ... interrupt mask = bio kernel trap: type 12, code = 0 Stopped at vwakeup+0x14: decl 0x44(%eax) Where eax is 0x108000c and vwakeup() is called from biodone(). Since this panic occurs in an interrupt environment, I have no idea how to trace it. Is there a way to find the bug by tracing or what is the prime suspect in this case. Thanks! -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 9:43:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from goose.mail.pas.earthlink.net (goose.mail.pas.earthlink.net [207.217.120.18]) by hub.freebsd.org (Postfix) with ESMTP id 941EF37B40C for ; Thu, 13 Sep 2001 09:43:29 -0700 (PDT) Received: from mindspring.com (dialup-209.247.137.158.Dial1.SanJose1.Level3.net [209.247.137.158]) by goose.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA26198; Thu, 13 Sep 2001 09:43:22 -0700 (PDT) Message-ID: <3BA0E256.10B8F05B@mindspring.com> Date: Thu, 13 Sep 2001 09:44:06 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel module debug help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ah. Interesting bug; perhaps related to a similar experience of my own... so let's stare at it! Zhihui Zhang wrote: > > I am debugging a KLD and I have got the following panic inside an > interrupt context: > > fault virutal address = 0x1080050 > ... > interrupt mask = bio > kernel trap: type 12, code = 0 > Stopped at vwakeup+0x14: decl 0x44(%eax) > > Where eax is 0x108000c and vwakeup() is called from biodone(). > > Since this panic occurs in an interrupt environment, I have no idea how to > trace it. Is there a way to find the bug by tracing or what is the prime > suspect in this case. Thanks! The best advice would be to repeat this failure in the context of linking the module in statically instead of dynamically. If it won't repeat for you then, the problem has to be in the form of memory allocation you are using as part of the module. If you want to brute-force the issue, find out what is being dereferenced at vwakeup+0x14 ...it looks to be: vp->v_numoutput--; though mine is at: 0x40189c9c : decl 0x44(%eax) which implies you have bad/older/newer vwakeup code. Maybe you are just missing the "if" test that verifies it's non-NULL vnode pointer being dereferenced??? That would match the number of bytes your "decl" instruction is off from mine: 614 void 615 vwakeup(bp) 616 register struct buf *bp; 617 { 618 register struct vnode *vp; 619 620 bp->b_flags &= ~B_WRITEINPROG; 621 if ((vp = bp->b_vp)) { 622 vp->v_numoutput--; 623 if (vp->v_numoutput < 0) 624 panic("vwakeup: neg numoutput"); 625 if ((vp->v_numoutput == 0) && (vp->v_flag & VBWAIT)) { 626 vp->v_flag &= ~VBWAIT; 627 wakeup((caddr_t) &vp->v_numoutput); 628 } 629 } 630 } I'll also note that 0x44 is 68, which implies 17 long words before v_numoutput is declared in struct vnode; this didn't match my quick count. I rather expect that it's in a swappable memory region that's currently not mapped, or NULL (we see it's not NULL), so this implies that it's an unitialized vnode from the zone -- a thing you can't initialize at interrupt. This can happen as the result of a kevent() completion being noted (e.g. readable) at interrupt context, since you can get swappable objects (it also looks like you may be on your way out of splbio, which implies networking -- my guess is therefore that you are working on network file system code, and have a "shadow" vnode that you are using as a context for the calls that should have been allocated out of an interrupt zone instead of out of the main memory allocator, which is not interrupt safe for new allocations... 8-)). For example, I use LRP, which drastically increases my connections per second out of the TCP stack and eliminates receiver livelock and a number of other problems for heavily loaded servers, but it means that sockets need to be able of accept'ing to completion (creating a new socket) at interrupt context. But when this happens, I don't have a proc structure handy to deal with the issue (since I'm at interrupt context). The sneaky way around this is to use the proc from the already existing socket on which the listen for which the accept is being completed was initially posted -- which gets me the proc struct, which gets me the ucred, so I have the proc pointer and the ucred pointer necessary to run the connection to completion. I rather expect that if you are depending on the existance of something similar at interrupt context, that you will have to either queue it and run to completion at a software interrupt level (e.g. NETISR -- not recommended, even for networking!), or just "lose" the wakeup (which is what the vwakeup code I have does, with it's "if" test). Still, your best bet is to compile the thing in static, repeat the problem, and then look at where things went wrong in the kernel debugger. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 9:53:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by hub.freebsd.org (Postfix) with ESMTP id 59A4E37B405 for ; Thu, 13 Sep 2001 09:53:18 -0700 (PDT) Received: from Bsdguru@aol.com by imo-d06.mx.aol.com (mail_out_v31_r1.4.) id n.97.1b274302 (16787) for ; Thu, 13 Sep 2001 12:53:07 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <97.1b274302.28d23e73@aol.com> Date: Thu, 13 Sep 2001 12:53:07 EDT Subject: Freebsd Multicast question To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are PIM-DM and PIM-SM supported in Freebsd? I cant find any reference in the code. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 10: 6: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 4B8C837B403 for ; Thu, 13 Sep 2001 10:06:00 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 8F5BA64; Thu, 13 Sep 2001 18:05:57 +0100 (BST) Date: Thu, 13 Sep 2001 18:05:57 +0100 From: Josef Karthauser To: Bsdguru@aol.com Cc: hackers@freebsd.org Subject: Re: Freebsd Multicast question Message-ID: <20010913180557.D17489@tao.org.uk> References: <97.1b274302.28d23e73@aol.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4zI0WCX1RcnW9Hbu" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <97.1b274302.28d23e73@aol.com>; from Bsdguru@aol.com on Thu, Sep 13, 2001 at 12:53:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4zI0WCX1RcnW9Hbu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2001 at 12:53:07PM -0400, Bsdguru@aol.com wrote: > Are PIM-DM and PIM-SM supported in Freebsd? I cant find any reference in = the=20 > code. >=20 > Bryan Look in the ports collection: Port: pim6dd-20010602a_1 Path: /usr/ports/net/pim6dd Info: PIM for IPv6 dense mode daemon Maint: ume@FreeBSD.org Index: net ipv6 B-deps:=20 R-deps:=20 Port: pim6sd-20010602a_1 Path: /usr/ports/net/pim6sd Info: PIM for IPv6 sparse mode daemon Maint: ume@FreeBSD.org Index: net ipv6 B-deps:=20 R-deps:=20 Joe --4zI0WCX1RcnW9Hbu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjug53UACgkQXVIcjOaxUBZm2QCg1yLoC2z9KoWoguYRwmW+zvaZ jugAoOsogEBNKbDqm0bxAZ5cr0gXMstv =PM8T -----END PGP SIGNATURE----- --4zI0WCX1RcnW9Hbu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 10:42:46 2001 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 B290137B415 for ; Thu, 13 Sep 2001 10:42:43 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f8DHgdg22429; Thu, 13 Sep 2001 10:42:39 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id f8DHgdK66692; Thu, 13 Sep 2001 10:42:39 -0700 (PDT) (envelope-from jdp) Date: Thu, 13 Sep 2001 10:42:39 -0700 (PDT) Message-Id: <200109131742.f8DHgdK66692@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: julian@elischer.org Subject: Re: cvsup14 (cvsup.above.net) not up to date In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Julian Elischer wrote: > > It seems to be not updating.. maybe they didn't get the new version > of cvsup (or installed the wrong one like I did to start with) telnet cvsup14.freebsd.org 5999 shows that they are running the corrected version of CVSup. If they are still out of date, could you please drop a note to the maintainer? All maintainers are listed in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS In the case of cvsup14, the address is . Thanks, 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 Sep 13 12:23:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id A070037B403 for ; Thu, 13 Sep 2001 12:23:54 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f8DJNrN24260 for hackers@freebsd.org; Thu, 13 Sep 2001 23:23:53 +0400 (MSD) (envelope-from yar) Date: Thu, 13 Sep 2001 23:23:52 +0400 From: Yar Tikhiy To: hackers@freebsd.org Subject: Driver structures & alignment Message-ID: <20010913232352.A23874@snark.rinet.ru> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, Is there a single blessed way to define packed structures for use in drivers? I suspect that using "#pragma pack(1)" will lead to alignment errors in non-Intel architectures. Should char arrays be used for all multi-byte elements to avoid alignment problems? And is it OK to rely on specially crafted structures, like "struct fs" in /sys/ufs/ffs/fs.h where multi-byte elements are pre-aligned by the structure's design, being contiguous? -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 13:38:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F56937B401 for ; Thu, 13 Sep 2001 13:38:07 -0700 (PDT) Received: from brother.ludd.luth.se (brother.ludd.luth.se [130.240.16.78]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id WAA07657 for ; Thu, 13 Sep 2001 22:38:05 +0200 (MEST) From: Peter B Received: (from pb@localhost) by brother.ludd.luth.se (8.9.3+Sun/8.9.3) id WAA02709 for freebsd-hackers@freebsd.org; Thu, 13 Sep 2001 22:38:03 +0200 (MEST) Message-Id: <200109132038.WAA02709@brother.ludd.luth.se> Subject: All ok? To: freebsd-hackers@freebsd.org Date: Thu, 13 Sep 2001 22:38:03 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I just wonder if all freebsd developers are ok, due the wtc attack? /P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 13:39: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id C44D237B440 for ; Thu, 13 Sep 2001 13:38:57 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 5523178; Thu, 13 Sep 2001 21:38:55 +0100 (BST) Date: Thu, 13 Sep 2001 21:38:55 +0100 From: Josef Karthauser To: Peter B Cc: freebsd-hackers@freebsd.org Subject: Re: All ok? Message-ID: <20010913213855.F17489@tao.org.uk> Mail-Followup-To: Josef Karthauser , Peter B , freebsd-hackers@freebsd.org References: <200109132038.WAA02709@brother.ludd.luth.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="rWhLK7VZz0iBluhq" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109132038.WAA02709@brother.ludd.luth.se>; from pb@ludd.luth.se on Thu, Sep 13, 2001 at 10:38:03PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --rWhLK7VZz0iBluhq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2001 at 10:38:03PM +0200, Peter B wrote: >=20 > Hi! >=20 > I just wonder if all freebsd developers are ok, due the wtc attack? > /P We believe so. Joe --rWhLK7VZz0iBluhq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuhGV4ACgkQXVIcjOaxUBak9QCgjFYLWyK8gHb7Bcp+WWeq+8wq f/0AoO2yBXGHduq983qM7l9PH4eJO3ry =rhHb -----END PGP SIGNATURE----- --rWhLK7VZz0iBluhq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 14:25:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 205AA37B403 for ; Thu, 13 Sep 2001 14:25:10 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8DLP6i22023; Thu, 13 Sep 2001 22:25:07 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8DLP2d97096; Thu, 13 Sep 2001 22:25:02 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200109132125.f8DLP2d97096@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Giorgos Keramidas Cc: hackers@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: Checking changes to listening ports in /etc/security In-Reply-To: Message from Giorgos Keramidas of "Wed, 12 Sep 2001 20:57:43 +0300." <20010912205743.A64992@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Sep 2001 22:25:02 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I've been adding an extra check in my local version of /etc/security for quite > some time now. All it does is use 'netstat' to grab a list of the listening > tcp and udp ports of my machine and save it to /var/log/netstat.today > (and /var/log/netstat.yesterday). This way, when some service starts > and listens on a new port the next run of /etc/security will log the > fact in the usual stuff sent to root by mail. I tested this running > /etc/periodic/daily/450.security twice, and running a local IRC daemon between > the two runs. The output that is added to the message root receives looks > like the following: [.....] I like this idea. I think It would be worth making it diff against /dev/null when netstat.today doesn't exist, so that the first time this is run on a given machine, you get to see all the ports that are open. [.....] +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat [.....] I think this like is bogus. In fact, it looks like the $daily_status_security_noamd periodic.conf tunable is broken. Oops ! I'll fix it after your changes go in. -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 14:30:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 7877A37B405; Thu, 13 Sep 2001 14:30:52 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8DLUoi22040; Thu, 13 Sep 2001 22:30:50 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8DLUkd97146; Thu, 13 Sep 2001 22:30:46 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200109132130.f8DLUkd97146@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Yar Tikhiy Cc: hackers@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: Driver structures & alignment In-Reply-To: Message from Yar Tikhiy of "Thu, 13 Sep 2001 23:23:52 +0400." <20010913232352.A23874@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Sep 2001 22:30:46 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi there, > > Is there a single blessed way to define packed structures > for use in drivers? I suspect that using "#pragma pack(1)" > will lead to alignment errors in non-Intel architectures. gcc deals with it, certainly on alpha anyway. However, I don't think anyone would ever bless using packed structures as it hurts memory transfers. I prefer the fix-it-up-when-I-need-it-packed approach :*) > -- > Yar -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 15:45:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m06.mx.aol.com (imo-m06.mx.aol.com [64.12.136.161]) by hub.freebsd.org (Postfix) with ESMTP id EB0FA37B406 for ; Thu, 13 Sep 2001 15:45:11 -0700 (PDT) Received: from Bsdguru@aol.com by imo-m06.mx.aol.com (mail_out_v31_r1.7.) id 6.10e.50cd483 (4331); Thu, 13 Sep 2001 18:45:04 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <10e.50cd483.28d290ef@aol.com> Date: Thu, 13 Sep 2001 18:45:03 EDT Subject: All Ok? To: pb@ludd.luth.se Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The developers are largely a "west-coast" crowd, i think :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 15:51:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 511FE37B413 for ; Thu, 13 Sep 2001 15:51:52 -0700 (PDT) Received: from hades.hell.gr (patr530-b081.otenet.gr [195.167.121.209]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8DMpkp27216; Fri, 14 Sep 2001 01:51:46 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8DMq3A43377; Fri, 14 Sep 2001 01:52:03 +0300 (EEST) (envelope-from charon@labs.gr) Date: Fri, 14 Sep 2001 01:52:03 +0300 From: Giorgos Keramidas To: Brian Somers Cc: hackers@FreeBSD.ORG Subject: Re: Checking changes to listening ports in /etc/security Message-ID: <20010914015203.A43352@hades.hell.gr> References: <200109132125.f8DLP2d97096@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109132125.f8DLP2d97096@hak.lan.Awfulhak.org>; from brian@freebsd-services.com on Thu, Sep 13, 2001 at 10:25:02PM +0100 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline From: Brian Somers Subject: Re: Checking changes to listening ports in /etc/security Date: Thu, Sep 13, 2001 at 10:25:02PM +0100 > I like this idea. I think It would be worth making it diff against > /dev/null when netstat.today doesn't exist, so that the first time > this is run on a given machine, you get to see all the ports that are > open. Done. I duplicated the code of the second if[] since I could not easily come up with a version that does not use some kind of shell variable weirdness and still work the same way. I prefer to keep this clean and easy to understand. The attached patch makes /dev/null the first argument of diff when sockstat.today does not exist. > [.....] > +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat > [.....] > > I think this like is bogus. In fact, it looks like the > $daily_status_security_noamd periodic.conf tunable is broken. > > Oops ! I'll fix it after your changes go in. So far, two people like the change. Since I can't help in making the change go in, I trust that after checking I did not break anything that I missed in my tests, you'll either give me a 'go ahead' to send-pr or just commit this yourself? -giorgos --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-security Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.55 diff -u -r1.55 security --- security 4 Jul 2001 12:49:17 -0000 1.55 +++ security 13 Sep 2001 22:46:08 -0000 @@ -128,6 +128,29 @@ tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 +# Show changes in listening tcp and udp ports: +# +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat +if ( sockstat -l46 | head -1 ;\ + sockstat -l46 | grep -v comsat | grep -v '^$' |\ + grep -v '^USER' | sort +5 ) | $cmd > $TMP ;then + if [ ! -f $LOG/sockstat.today ]; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b /dev/null $TMP + touch $LOG/sockstat.yesterday || rc=3 + mv $TMP $LOG/sockstat.today || rc=3 + elif ! cmp $LOG/sockstat.today $TMP >/dev/null 2>&1; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b $LOG/sockstat.today $TMP + mv $LOG/sockstat.today $LOG/sockstat.yesterday || rc=3 + mv $TMP $LOG/sockstat.today || rc=3 + fi +fi + # Show denied packets # if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then --n8g4imXOkfNTN/H1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 16: 0:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 2C59837B40A for ; Thu, 13 Sep 2001 16:00:40 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 7B1474C5; Fri, 14 Sep 2001 00:00:37 +0100 (BST) Date: Fri, 14 Sep 2001 00:00:37 +0100 From: Josef Karthauser To: Bsdguru@aol.com Cc: pb@ludd.luth.se, hackers@freebsd.org Subject: Re: All Ok? Message-ID: <20010914000037.A26498@tao.org.uk> References: <10e.50cd483.28d290ef@aol.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <10e.50cd483.28d290ef@aol.com>; from Bsdguru@aol.com on Thu, Sep 13, 2001 at 06:45:03PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 13, 2001 at 06:45:03PM -0400, Bsdguru@aol.com wrote: > The developers are largely a "west-coast" crowd, i think :-) And the rest of the world. Joe --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuhOpQACgkQXVIcjOaxUBZocACbBObw8r3JygDuXYUiAEG9mlfC Jq8AoIohAwd3AIjgqrTXbFF2XfkoloDt =U9Ak -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 16: 2:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id DFE2037B408; Thu, 13 Sep 2001 16:02:29 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8DN9vX03967; Thu, 13 Sep 2001 16:09:58 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109132309.f8DN9vX03967@mass.dis.org> To: Yar Tikhiy Cc: hackers@freebsd.org, msmith@mass.dis.org Subject: Re: Driver structures & alignment In-Reply-To: Message from Yar Tikhiy of "Thu, 13 Sep 2001 23:23:52 +0400." <20010913232352.A23874@snark.rinet.ru> Date: Thu, 13 Sep 2001 16:09:57 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi there, > > Is there a single blessed way to define packed structures > for use in drivers? I suspect that using "#pragma pack(1)" > will lead to alignment errors in non-Intel architectures. Any form of packing is going to cause problems for items that are located in illegal fashions. Having said that, I recommend using __attribute__ ((packed)) to explicitly request that a structure be packed. > Should char arrays be used for all multi-byte elements to > avoid alignment problems? No. > And is it OK to rely on specially crafted structures, like > "struct fs" in /sys/ufs/ffs/fs.h where multi-byte elements > are pre-aligned by the structure's design, being contiguous? "rely" in what fashion? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 18:28:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id F3DB537B408; Thu, 13 Sep 2001 18:28:09 -0700 (PDT) Received: from doby.excite.com ([199.172.152.182]) by ewey.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010914012809.NTDX7149.ewey.excite.com@doby.excite.com>; Thu, 13 Sep 2001 18:28:09 -0700 Message-ID: <20775668.1000430889008.JavaMail.imail@doby.excite.com> Date: Thu, 13 Sep 2001 18:28:02 -0700 (PDT) From: john_wilson100@excite.com To: Greg Lehey Subject: Vinum Panic (was Re: HPT370 RAID or Vinum?) Cc: freebsd-hackers@freebsd.org, sos@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, I have to say that Vinum feels a lot faster than HPT RAID... I will quantify this statement when someone tells me how to turn off ATA write caching, because sysctl -w hw.ata.wc=0 doesn't work, says "sysctl: oid 'hw.ata.wc' is read only" Unfortunately, Vinum reproducibly panics my machine while doing "newfs -v /dev/vinum/home", where /dev/vinum/home is a 70+ Gb striped volume: # newfs -v /dev/vinum/home ...superblocks here... 154206240, 154271776, 154337312, 154402848, 154468384, 154533920, Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc2bb8571 stack pointer = 0x10:0xdb1e2d1c frame pointer = 0x10:0xdb1e2d28 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 = 2195 (newfs) interrupt mask = none trap number = 12 panic: page fault syncing disks... 1 done Uptime: 1d0h23m8s dumping to dev #ad/0x20021, offset 3145760 dump ata2: resetting devices .. done 511 510 509 ... ... 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:473 (kgdb) add-symbol-file /modules/vinum.ko 0xc2baebf0 (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:473 #1 0xc013d1df in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:313 #2 0xc013d5ac in poweroff_wait (junk=0xc025898c, howto=-1071283025) at /usr/src/sys/kern/kern_shutdown.c:581 #3 0xc0228e4e in trap_fatal (frame=0xdb1e2cdc, eva=28) at /usr/src/sys/i386/i386/trap.c:956 #4 0xc0228b21 in trap_pfault (frame=0xdb1e2cdc, usermode=0, eva=28) at /usr/src/sys/i386/i386/trap.c:849 #5 0xc022870b in trap (frame={tf_fs = 16, tf_es = -618790896, tf_ds = -1027932144, tf_edi = 396, tf_esi = -1021550528, tf_ebp = -618779352, tf_isp = -618779384, tf_ebx = 0, tf_edx = 6662, tf_ecx = -1069469696, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1027897999, tf_cs = 8, tf_eflags = 66118, tf_esp = 1116, tf_ss = -1026983728}) at /usr/src/sys/i386/i386/trap.c:448 #6 0xc2bb8571 in allocrqg (rq=0xc31c6040, elements=1) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:1054 #7 0xc2bb7b1e in bre (rq=0xc31c6040, plexno=1, diskaddr=0xdb1e2d90, diskend=154600128) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:571 #8 0xc2bb7f1f in build_write_request (rq=0xc31c6040) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:774 #9 0xc2bb74fe in vinumstart (bp=0xcd1b3a0c, reviveok=0) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:272 #10 0xc2bb73d2 in vinumstrategy (bp=0xcd1b3a0c) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:164 #11 0xc0139bdf in physio (dev=0xc307ed00, uio=0xdb1e2ed8, ioflag=1048577) at /usr/src/sys/kern/kern_physio.c:111 #12 0xc0175041 in spec_write (ap=0xdb1e2e68) at /usr/src/sys/miscfs/specfs/spec_vnops.c:283 #13 0xc01e6f94 in ufsspec_write (ap=0xdb1e2e68) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1872 #14 0xc01e7551 in ufs_vnoperatespec (ap0xdb1e2e68) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2400 #15 0xc0171352 in vn_write (fp=0xc35bda00, uio=0xdb1e2ed8, cred=0xc307ee80, flags=0, p=0xd6a508a0) at vnode_if.h:363 #16 0xc014baed in dofilewrite (p=0xd6a508a0, fp=0x0xc35bda00, fd=3, buf=0x806c860, nbyte=131072, offset=-1, flags=0) at /usr/src/sys/sys/file.h:162 #17 0xc014b9a6 in write (p=0xd6a508a0, uap=0xdb1e2f80) at /usr/src/sys/kern/sys_generic.c:329 #18 0xc02290f9 in syscall2 (frame={tf_fs = 47, tf_es = 65583, tf_ds = -1078001617, tf_edi = 8192, tf_esi = 122880, tf_ebp = -1077940256, tf_isp = -618778668, tf_ebx = 18, tf_edx = 18, tf_ecx = 0, tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 134620572, tf_cs = 31, tf_eflags = 663, tf_esp = -1077940284, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1155 #19 0xc021b1c5 in Xint0x80_syscall () #20 0x804c8ed in ?? () #21 0x804b785 in ?? () #22 0x804b1b5 in ?? () #23 0x80491ab in ?? () #24 0x8048135 in ?? () Here's my Vinum config: $ more /root/vinum.conf drive data1 device /dev/ad4s1g drive data2 device /dev/ad6s1e drive home1 device /dev/ad4s1h drive home2 device /dev/ad6s1f volume data plex org striped 279k sd length 0 drive data1 sd length 0 drive data2 volume home plex org striped 279k sd length 0 drive home1 sd length 0 drive home2 The disk labels: disklabel ad4s1 # /dev/ad4s1c: type: ESDI disk: ad4s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7475 sectors/unit: 120101877 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 524288 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 32*) b: 4194304 524288 swap # (Cyl. 32*- 293*) c: 120101877 0 unused 0 0 # (Cyl. 0 - 7475*) e: 4194304 4718592 4.2BSD 1024 8192 16 # (Cyl. 293*- 554*) f: 10485760 8912896 4.2BSD 1024 8192 16 # (Cyl. 554*- 1207*) g: 20971520 19398656 vinum # (Cyl. 1207*- 2512*) h: 79731701 40370176 vinum # (Cyl. 2512*- 7475*) disklabel ad6s1 # /dev/ad6s1c: type: ESDI disk: ad6s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7475 sectors/unit: 120101877 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 4194304 0 swap # (Cyl. 0 - 261*) c: 120101877 0 unused 0 0 # (Cyl. 0 - 7475*) e: 20971520 4194304 vinum # (Cyl. 261*- 1566*) f: 77278156 25165824 vinum # (Cyl. 1566*- 6376*) g: 17657897 102443980 4.2BSD 1024 8192 16 # (Cyl. 6376*- 7475*) BTW, this is on latest -stable (supped two days ago). Let me know if you need more info. John On Tue, 11 Sep 2001 09:05:18 +1000, Greg Lehey wrote: > On Monday, 10 September 2001 at 10:11:28 -0700, john_wilson100@excite.com wrote: > > Hi there, > > > > I am trying to install FreeBSD on a (pseudo-) hardware ATA RAID volume which > > consists of two striped ATA disks connected to a Highpoint HPT370 > > controller. "Pseudo-" because FreeBSD detects the individual disks > > (ad4/ad6) as well as the striped volume (ar0). > > > > Besides the fact that ar0 isn't documented anywhere (except in /dev/MAKEDEV) > > and "man 4 ar" gives something completely irrelevant, which one is better to > > use: > > > > Highpoint built-in RAID (ar0), or ad4/ad6 striped with Vinum? > > > > I reckon if the RAID functions are implemented in HPT BIOS (in software), > > I'll be better off with Vinum. > > Ultimately, all RAID is software RAID. The issue is just how it's > implemented. > > I'd guess that the HPT will give you far worse performance than Vinum, > though I'd be very interested to see confirmation or denial of this > guess. If you feel like benchmarking, contact me first. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers _______________________________________________________ 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 Thu Sep 13 20:11: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 4BFB137B403 for ; Thu, 13 Sep 2001 20:11:02 -0700 (PDT) Received: from NDNM ([195.161.98.250]) by ns.morning.ru (8.11.5/8.11.5) with ESMTP id f8E3ANd45055; Fri, 14 Sep 2001 11:10:24 +0800 (KRAST) Date: Fri, 14 Sep 2001 11:11:10 +0800 From: Igor Podlesny X-Mailer: The Bat! (v1.53d) UNREG / CD5BF9353B3B7091 Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <22226074908.20010914111110@morning.ru> To: Giorgos Keramidas Cc: Brian Somers , hackers@FreeBSD.ORG Subject: Re[2]: Checking changes to listening ports in /etc/security In-Reply-To: <20010914015203.A43352@hades.hell.gr> References: <200109132125.f8DLP2d97096@hak.lan.Awfulhak.org> <20010914015203.A43352@hades.hell.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! I've done similar thing by myself also, cause I have been working with some Linux distros, where it is an usual thing (I mean detection of any listeners changes) and I consider this is useful. But, the idea is slightly different -- my code is being called every minute (cron). It then compares the previous situation and in case of any changes reports about it via e-mail to the root. Actually, the code is quite raw/poor in meaning of its abilities.. for e.g., report with syslog also could have place. Another thing to change is using sort(1)|comm(1) instead of diff(1) cause sometimes the only thing changed is the location of strings in sockstat(1) 's output... Up till now I haven't rewritten it (it works :-) and a lack of time, alas) -- here it is: ====================================================================== #!/bin/sh prevsf=/var/spool/prevsockstat nowsf=/var/spool/nowsockstat if ! [ -e $prevsf ]; then nowsf=$prevsf fi sockstat -f inet -an|grep LISTEN > $nowsf if ! diff $nowsf $prevsf 2>/dev/null 1>&2 ; then hostname=`hostname` mail -s "$hostname listeners changed!" root <<__TEXT__ Date: `date` the difference: ----------------------X-8---------------------------------- `diff $prevsf $nowsf 2>&1 ` ----------------------X-8---------------------------------- the sockstat output: `sockstat -4` __TEXT__ mv -f $nowsf $prevsf fi ====================================================================== As you can see there are lots of places where it could be improved. :) MYBR! > From: Brian Somers > Subject: Re: Checking changes to listening ports in /etc/security > Date: Thu, Sep 13, 2001 at 10:25:02PM +0100 >> I like this idea. I think It would be worth making it diff against >> /dev/null when netstat.today doesn't exist, so that the first time >> this is run on a given machine, you get to see all the ports that are >> open. > Done. I duplicated the code of the second if[] since I could not easily come > up with a version that does not use some kind of shell variable weirdness > and still work the same way. I prefer to keep this clean and easy to > understand. The attached patch makes /dev/null the first argument of diff > when sockstat.today does not exist. >> [.....] >> +[ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat >> [.....] >> >> I think this like is bogus. In fact, it looks like the >> $daily_status_security_noamd periodic.conf tunable is broken. >> >> Oops ! I'll fix it after your changes go in. > So far, two people like the change. Since I can't help in making the change > go in, I trust that after checking I did not break anything that I missed in > my tests, you'll either give me a 'go ahead' to send-pr or just commit this > yourself? > -giorgos -- Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 13 20:22:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 7217437B415; Thu, 13 Sep 2001 20:22:50 -0700 (PDT) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id LAA31288; Fri, 14 Sep 2001 11:27:00 +0800 Message-ID: <005401c13ccc$1c9cfd50$ef01a8c0@davidwnt> From: "David Xu" To: , "Greg Lehey" Cc: , References: <20775668.1000430889008.JavaMail.imail@doby.excite.com> Subject: Re: Vinum Panic (was Re: HPT370 RAID or Vinum?) Date: Fri, 14 Sep 2001 11:19:48 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message -----=20 From: To: "Greg Lehey" Cc: ; Sent: Friday, September 14, 2001 9:28 AM Subject: Vinum Panic (was Re: HPT370 RAID or Vinum?) > Well, I have to say that Vinum feels a lot faster than HPT RAID... I = will > quantify this statement when someone tells me how to turn off ATA = write > caching, because >=20 > sysctl -w hw.ata.wc=3D0 >=20 > doesn't work, says "sysctl: oid 'hw.ata.wc' is read only" >=20 hw.ata.wc=3D0 put it into /boot/loader.conf, then reboot. -- David Xu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 1:26:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id 8EF4237B409; Fri, 14 Sep 2001 01:26:20 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f8E8Nib38763; Fri, 14 Sep 2001 12:23:44 +0400 (MSD) (envelope-from yar) Date: Fri, 14 Sep 2001 12:23:44 +0400 From: Yar Tikhiy To: Mike Smith Cc: hackers@freebsd.org, msmith@mass.dis.org Subject: Re: Driver structures & alignment Message-ID: <20010914122344.A38530@snark.rinet.ru> References: <200109132309.f8DN9vX03967@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109132309.f8DN9vX03967@mass.dis.org>; from msmith@freebsd.org on Thu, Sep 13, 2001 at 04:09:57PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote: > > > > Is there a single blessed way to define packed structures > > for use in drivers? I suspect that using "#pragma pack(1)" > > will lead to alignment errors in non-Intel architectures. > > Any form of packing is going to cause problems for items that are > located in illegal fashions. > > Having said that, I recommend using __attribute__ ((packed)) > to explicitly request that a structure be packed. Should the __attribute__ be supplied to each structure's member? Or can it be the whole structure's attribute? > > And is it OK to rely on specially crafted structures, like > > "struct fs" in /sys/ufs/ffs/fs.h where multi-byte elements > > are pre-aligned by the structure's design, being contiguous? > > "rely" in what fashion? E.g., will the following structure: struct foo { int16_t a; int16_t b; int32_t c; /* 4-byte boundary */ int64_t d; /* 8-byte boundary */ int8_t e[4]; int32_t f; /* 4-byte boundary */ }; contain alignment holes in any architecture/compiler? -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 1:39:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id E7EBC37B412 for ; Fri, 14 Sep 2001 01:39:22 -0700 (PDT) Received: from mindspring.com (dialup-209.245.133.204.Dial1.SanJose1.Level3.net [209.245.133.204]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f8E8dEf10464; Fri, 14 Sep 2001 01:39:15 -0700 (PDT) Message-ID: <3BA1C25E.23D95C4D@mindspring.com> Date: Fri, 14 Sep 2001 01:39:58 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: Peter B , freebsd-hackers@freebsd.org Subject: Re: All ok? References: <200109132038.WAA02709@brother.ludd.luth.se> <20010913213855.F17489@tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Josef Karthauser wrote: > > Hi! > > > > I just wonder if all freebsd developers are ok, due the wtc attack? > > We believe so. Has anyone talked to Loqui Chen since the the event? Loqui was a financial person in New York at one time, and made significant contributions in the VM system, the Soft Updates code, and SMP code. People would post a bug no one could find, and the first you'd hear from him (and usually the last) was a bug fix for some insanely deep problem in code that was opaque to most people on these lists. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 2: 3:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 76C2837B40B; Fri, 14 Sep 2001 02:03:40 -0700 (PDT) Received: from mindspring.com (dialup-209.245.133.204.Dial1.SanJose1.Level3.net [209.245.133.204]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA01716; Fri, 14 Sep 2001 02:03:38 -0700 (PDT) Message-ID: <3BA1C819.65D72D4B@mindspring.com> Date: Fri, 14 Sep 2001 02:04:25 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Yar Tikhiy , hackers@freebsd.org, msmith@mass.dis.org Subject: Re: Driver structures & alignment References: <200109132309.f8DN9vX03967@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > Having said that, I recommend using __attribute__ ((packed)) > to explicitly request that a structure be packed. Is there a problem with "#pragma pack(1)"? I see it in a lot of header files... do they need changing? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 4:21:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 26E4137B409 for ; Fri, 14 Sep 2001 04:21:23 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8EBLKi25525; Fri, 14 Sep 2001 12:21:20 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8EBIhd29603; Fri, 14 Sep 2001 12:18:43 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200109141118.f8EBIhd29603@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Giorgos Keramidas Cc: Brian Somers , hackers@FreeBSD.ORG Subject: Re: Checking changes to listening ports in /etc/security In-Reply-To: Message from Giorgos Keramidas of "Fri, 14 Sep 2001 01:52:03 +0300." <20010914015203.A43352@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Sep 2001 12:18:43 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Brian Somers > Subject: Re: Checking changes to listening ports in /etc/security > Date: Thu, Sep 13, 2001 at 10:25:02PM +0100 > > > I like this idea. I think It would be worth making it diff against > > /dev/null when netstat.today doesn't exist, so that the first time > > this is run on a given machine, you get to see all the ports that are > > open. > > Done. I duplicated the code of the second if[] since I could not easily come > up with a version that does not use some kind of shell variable weirdness > and still work the same way. I prefer to keep this clean and easy to > understand. The attached patch makes /dev/null the first argument of diff > when sockstat.today does not exist. [.....] Hi, I think the attached patch makes things slightly better. We only run sockstat once, and remove the trailing whitespace that sockstat emits (making the diff lines look better when viewed on an 80 column screen). Could you look these over ? If you're happy with this I can commit it. Cheers. -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.55 diff -u -r1.55 security --- security 4 Jul 2001 12:49:17 -0000 1.55 +++ security 14 Sep 2001 11:12:09 -0000 @@ -128,6 +128,30 @@ tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 +# Show changes in listening tcp and udp ports: +# +sockstat -l46 | { + read line + echo "$line" + sed -e /^USER/d -e /comsat/d -e '/^[ ]*$/d' | sort +5 +} | sed 's/[ ][ ]*$//' >${TMP} + +if [ ! -f $LOG/sockstat.today ]; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b /dev/null $TMP + touch $LOG/sockstat.yesterday || rc=3 + mv $TMP $LOG/sockstat.today || rc=3 +elif ! cmp $LOG/sockstat.today $TMP >/dev/null 2>&1; then + [ $rc -lt 1 ] && rc=1 + separator + echo "$host changes in listening ports:" + diff -b $LOG/sockstat.today $TMP + mv $LOG/sockstat.today $LOG/sockstat.yesterday || rc=3 + mv $TMP $LOG/sockstat.today || rc=3 +fi + # Show denied packets # if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 4:27: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 7C99837B407 for ; Fri, 14 Sep 2001 04:26:55 -0700 (PDT) Received: (qmail 35740 invoked by uid 1001); 14 Sep 2001 11:37:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Sep 2001 11:37:58 -0000 Date: Fri, 14 Sep 2001 04:37:58 -0700 (PDT) From: Dan To: Subject: ide striping Message-ID: <20010914043602.P31777-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does it make sense at all to stripe primary slave, secondary master and slave together? I would imagine it is a waste of time , just looking for thoughts on this vs just a single primary master IDE. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 5: 3:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 8D1D537B405; Fri, 14 Sep 2001 05:03:20 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8EC3KM78670; Fri, 14 Sep 2001 05:03:20 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 25BB5380A; Fri, 14 Sep 2001 05:03:20 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: tlambert2@mindspring.com Cc: Mike Smith , Yar Tikhiy , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Driver structures & alignment In-Reply-To: <3BA1C819.65D72D4B@mindspring.com> Date: Fri, 14 Sep 2001 05:03:20 -0700 From: Peter Wemm Message-Id: <20010914120320.25BB5380A@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Mike Smith wrote: > > Having said that, I recommend using __attribute__ ((packed)) > > to explicitly request that a structure be packed. > > Is there a problem with "#pragma pack(1)"? I see it in a > lot of header files... do they need changing? Yes, but it should be: #define __packed __attribute__((packed)) in sys/cdefs.h. This allows us to provide an alternative __packed implementation for some other mythical compiler some day. The same goes for __format_arg(n) in stdio.h. And so on. We've been pretty clean about it so far, but a few have slipped through. 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 Fri Sep 14 6:59:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by hub.freebsd.org (Postfix) with ESMTP id 4377637B405 for ; Fri, 14 Sep 2001 06:59:19 -0700 (PDT) Received: from rasputin by shaft.techsupport.co.uk with local (Exim 3.22 #1) id 15htXf-0007zp-00 for hackers@freebsd.org; Fri, 14 Sep 2001 15:02:03 +0100 Date: Fri, 14 Sep 2001 15:02:03 +0100 From: Rasputin To: hackers@freebsd.org Subject: 802.11 with best Apple compatibility? Message-ID: <20010914150203.A30720@shaft.techsupport.co.uk> Reply-To: Rasputin 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG iJust a quickie - sorry if it's OT, but I know a few people on this list use Orinoco wireless NICs. I'm finally implementing my wireless gateway BSD box. Is there any difference between Gold and Silver cards from a compatibility standpoint (with the usual Apple Airport cards)? Thanks! -- One of the lessons of history is that nothing is often a good thing to do and always a clever thing to say. -- Will Durant Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 7: 5: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 8535737B40A for ; Fri, 14 Sep 2001 07:05:01 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8EEUbC06374 for hackers@FreeBSD.ORG; Fri, 14 Sep 2001 10:30:37 -0400 (EDT) (envelope-from bicknell) Date: Fri, 14 Sep 2001 10:30:37 -0400 From: Leo Bicknell To: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914103037.A5619@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , hackers@FreeBSD.ORG References: <20010914150203.A30720@shaft.techsupport.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914150203.A30720@shaft.techsupport.co.uk>; from rara.rasputin@virgin.net on Fri, Sep 14, 2001 at 03:02:03PM +0100 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote: > Is there any difference between Gold and Silver cards from > a compatibility standpoint (with the usual Apple Airport cards)? With WEP encryption turned off they both work together fine. I've seen many used in mixed enviornments. With WEP turned on, they are completely incomptable. The silver cards do a 40 bit encryption, and the gold cards do a 128 bit encryption, and it seems the gold cards can't be stepped back to 40 bit. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 7:53:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C82FA37B416; Fri, 14 Sep 2001 07:53:23 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA14780; Fri, 14 Sep 2001 10:53:07 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f8EEqen14227; Fri, 14 Sep 2001 10:52:40 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15266.6584.799463.704352@grasshopper.cs.duke.edu> Date: Fri, 14 Sep 2001 10:52:40 -0400 (EDT) To: Peter Wemm Cc: tlambert2@mindspring.com, Mike Smith , Yar Tikhiy , hackers@FreeBSD.ORG Subject: Re: Driver structures & alignment In-Reply-To: <20010914120320.25BB5380A@overcee.netplex.com.au> References: <3BA1C819.65D72D4B@mindspring.com> <20010914120320.25BB5380A@overcee.netplex.com.au> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm writes: > The same goes for __format_arg(n) in stdio.h. And so on. We've been pretty > clean about it so far, but a few have slipped through. > That __format_arg, btw, breaks the Compaq CCC compiler & causes us to have to override stdio.h because of just that one line. Does your comment mean this has a chance of getting fixed? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 8: 7: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id CE98A37B401 for ; Fri, 14 Sep 2001 08:06:55 -0700 (PDT) Received: (qmail 952 invoked by uid 1000); 14 Sep 2001 15:06:22 -0000 Date: Fri, 14 Sep 2001 18:06:22 +0300 From: Peter Pentchev To: rnordier@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org Subject: Does boot1 still have a > 1023 cyl limit? Message-ID: <20010914180622.A512@ringworld.oblivion.bg> Mail-Followup-To: rnordier@FreeBSD.org, 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, A quote from the end of the boot_i386.8 manual page.. IMPORTANT NOTE: Because of limitations imposed by the conventional disk interface provided by the BIOS, all boot-related files and structures (including the kernel) that need to be accessed during the boot phase must reside on the disk at or below cylinder 1023 (as the BIOS under- stands the geometry). When a ``Disk error 0x1'' is reported by the sec- ond-stage bootstrap, it generally means that this requirement has not been adhered to. Just today I had a friend ask me if this is still true; I checked CVS history and found out that this comment was added by rnordier more than two years ago. Is this still true? G'luck, Peter -- If you think this sentence is confusing, then change one pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 8:47: 7 2001 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 B09DC37B407 for ; Fri, 14 Sep 2001 08:46:59 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f8EFkwZ24443; Fri, 14 Sep 2001 11:46:58 -0400 (EDT) Date: Fri, 14 Sep 2001 11:46:55 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel module debug help In-Reply-To: <3BA0E256.10B8F05B@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks! It turns out the bug is caused by the following reason: I use bp=malloc() to allocate a buffer structure and issue an I/O with BUF_STRATEGY(). Then I use free() to free bp even before the I/O is completed. Really stupid. Memory trespass seems to be the most common source of panics I have met. -Zhihui On Thu, 13 Sep 2001, Terry Lambert wrote: > Ah. Interesting bug; perhaps related to a similar experience > of my own... so let's stare at it! > > > Zhihui Zhang wrote: > > > > I am debugging a KLD and I have got the following panic inside an > > interrupt context: > > > > fault virutal address = 0x1080050 > > ... > > interrupt mask = bio > > kernel trap: type 12, code = 0 > > Stopped at vwakeup+0x14: decl 0x44(%eax) > > > > Where eax is 0x108000c and vwakeup() is called from biodone(). > > > > Since this panic occurs in an interrupt environment, I have no idea how to > > trace it. Is there a way to find the bug by tracing or what is the prime > > suspect in this case. Thanks! > > The best advice would be to repeat this failure in the > context of linking the module in statically instead of > dynamically. > > If it won't repeat for you then, the problem has to be in > the form of memory allocation you are using as part of the > module. > > If you want to brute-force the issue, find out what is being > dereferenced at vwakeup+0x14 ...it looks to be: > > vp->v_numoutput--; > > though mine is at: > > 0x40189c9c : decl 0x44(%eax) > > which implies you have bad/older/newer vwakeup code. Maybe > you are just missing the "if" test that verifies it's non-NULL > vnode pointer being dereferenced??? That would match the number > of bytes your "decl" instruction is off from mine: > > 614 void > 615 vwakeup(bp) > 616 register struct buf *bp; > 617 { > 618 register struct vnode *vp; > 619 > 620 bp->b_flags &= ~B_WRITEINPROG; > 621 if ((vp = bp->b_vp)) { > 622 vp->v_numoutput--; > 623 if (vp->v_numoutput < 0) > 624 panic("vwakeup: neg numoutput"); > 625 if ((vp->v_numoutput == 0) && (vp->v_flag & VBWAIT)) { > 626 vp->v_flag &= ~VBWAIT; > 627 wakeup((caddr_t) &vp->v_numoutput); > 628 } > 629 } > 630 } > > > I'll also note that 0x44 is 68, which implies 17 long words > before v_numoutput is declared in struct vnode; this didn't > match my quick count. > > > I rather expect that it's in a swappable memory region that's > currently not mapped, or NULL (we see it's not NULL), so this > implies that it's an unitialized vnode from the zone -- a thing > you can't initialize at interrupt. > > This can happen as the result of a kevent() completion being > noted (e.g. readable) at interrupt context, since you can get > swappable objects (it also looks like you may be on your way > out of splbio, which implies networking -- my guess is therefore > that you are working on network file system code, and have a > "shadow" vnode that you are using as a context for the calls > that should have been allocated out of an interrupt zone instead > of out of the main memory allocator, which is not interrupt safe > for new allocations... 8-)). > > For example, I use LRP, which drastically increases my connections > per second out of the TCP stack and eliminates receiver livelock > and a number of other problems for heavily loaded servers, but it > means that sockets need to be able of accept'ing to completion > (creating a new socket) at interrupt context. > > But when this happens, I don't have a proc structure handy to > deal with the issue (since I'm at interrupt context). The > sneaky way around this is to use the proc from the already > existing socket on which the listen for which the accept is > being completed was initially posted -- which gets me the proc > struct, which gets me the ucred, so I have the proc pointer > and the ucred pointer necessary to run the connection to > completion. > > I rather expect that if you are depending on the existance of > something similar at interrupt context, that you will have to > either queue it and run to completion at a software interrupt > level (e.g. NETISR -- not recommended, even for networking!), > or just "lose" the wakeup (which is what the vwakeup code I > have does, with it's "if" test). > > Still, your best bet is to compile the thing in static, repeat > the problem, and then look at where things went wrong in the > kernel debugger. > > -- Terry > > 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 Sep 14 8:49:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id DCFE937B40E for ; Fri, 14 Sep 2001 08:49:16 -0700 (PDT) Received: from d1o913.telia.com (d1o913.telia.com [195.252.44.241]) by maile.telia.com (8.11.2/8.11.0) with ESMTP id f8EFnBT22054 for ; Fri, 14 Sep 2001 17:49:15 +0200 (CEST) Received: from ertr1013.student.uu.se (h185n2fls20o913.telia.com [212.181.163.185]) by d1o913.telia.com (8.8.8/8.8.8) with SMTP id RAA11196 for ; Fri, 14 Sep 2001 17:49:03 +0200 (CEST) Received: (qmail 53524 invoked by uid 1001); 14 Sep 2001 15:48:59 -0000 Date: Fri, 14 Sep 2001 17:48:59 +0200 From: Erik Trulsson To: Peter Pentchev Cc: freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? Message-ID: <20010914174859.A53427@student.uu.se> Mail-Followup-To: Peter Pentchev , freebsd-hackers@FreeBSD.org References: <20010914180622.A512@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010914180622.A512@ringworld.oblivion.bg> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 06:06:22PM +0300, Peter Pentchev wrote: > Hi, > > A quote from the end of the boot_i386.8 manual page.. > > IMPORTANT NOTE: Because of limitations imposed by the conventional disk > interface provided by the BIOS, all boot-related files and structures > (including the kernel) that need to be accessed during the boot phase > must reside on the disk at or below cylinder 1023 (as the BIOS under- > stands the geometry). When a ``Disk error 0x1'' is reported by the sec- > ond-stage bootstrap, it generally means that this requirement has not > been adhered to. > > Just today I had a friend ask me if this is still true; I checked CVS > history and found out that this comment was added by rnordier more than > two years ago. Is this still true? I think it depends on the BIOS. The first stages of the bootstrap sequence use the BIOS to read from the disk. The original BIOS calls for reading/writing the disk does not support cylinder numbers larger than 1023. On later BIOSes extensions have been added to allow access to cylinders above 1023. Nowadays the FreeBSD bootstrap is able to use these BIOS extensions. This capability was added about a year ago. (From reading the CVS logs it seems 4.1 was the first release to support this.) But to use this requires that the BIOS support these extensions. All modern machines do AFAIK but many older machines don't. To sum it up: If you have a modern BIOS you can boot from anywhere on the disk (assuming a recent version of FreeBSD) but older BIOSes do not support this. Anybody who knows when BIOSes in general were extended to support >1024 cylinders? My *guess* would be 1997 or thereabout. -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 9:39: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D3D0C37B40B; Fri, 14 Sep 2001 09:39:01 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8EGkb501038; Fri, 14 Sep 2001 09:46:37 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109141646.f8EGkb501038@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Yar Tikhiy Cc: Mike Smith , hackers@freebsd.org Subject: Re: Driver structures & alignment In-reply-to: Your message of "Fri, 14 Sep 2001 12:23:44 +0400." <20010914122344.A38530@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Sep 2001 09:46:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote: > > > > > > Is there a single blessed way to define packed structures > > > for use in drivers? I suspect that using "#pragma pack(1)" > > > will lead to alignment errors in non-Intel architectures. > > > > Any form of packing is going to cause problems for items that are > > located in illegal fashions. > > > > Having said that, I recommend using __attribute__ ((packed)) > > to explicitly request that a structure be packed. > > Should the __attribute__ be supplied to each structure's member? > Or can it be the whole structure's attribute? You could just search for examples in /sys/dev, perhaps. 8) But for the record, the attribute applies to the structure as a whole. -- ... 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 Sep 14 9:42:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D2AC837B411; Fri, 14 Sep 2001 09:42:52 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8EGoN501078; Fri, 14 Sep 2001 09:50:24 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109141650.f8EGoN501078@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Pentchev Cc: rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? In-reply-to: Your message of "Fri, 14 Sep 2001 18:06:22 +0300." <20010914180622.A512@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Sep 2001 09:50:23 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > A quote from the end of the boot_i386.8 manual page.. > > IMPORTANT NOTE: Because of limitations imposed by the conventional disk > interface provided by the BIOS, all boot-related files and structures > (including the kernel) that need to be accessed during the boot phase > must reside on the disk at or below cylinder 1023 (as the BIOS under- > stands the geometry). When a ``Disk error 0x1'' is reported by the sec- > ond-stage bootstrap, it generally means that this requirement has not > been adhered to. > > Just today I had a friend ask me if this is still true; I checked CVS > history and found out that this comment was added by rnordier more than > two years ago. Is this still true? No; it's quite possible now to boot from beyond the 1024 cylinder mark, however boot0 does not install in 'packet' mode by default, which means that you need to manually install/configure it before rebooting after system installation. So we don't cleanly install for > 1024 cylinders, but it works with a little tweaking. -- ... 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 Sep 14 9:47:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 261B437B401 for ; Fri, 14 Sep 2001 09:47:53 -0700 (PDT) Received: from hades.hell.gr (patr530-a184.otenet.gr [212.205.215.184]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8EGlmd02421; Fri, 14 Sep 2001 19:47:48 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8EEvId01192; Fri, 14 Sep 2001 17:57:18 +0300 (EEST) (envelope-from charon@labs.gr) Date: Fri, 14 Sep 2001 17:57:18 +0300 From: Giorgos Keramidas To: Brian Somers Cc: hackers@FreeBSD.ORG Subject: Re: Checking changes to listening ports in /etc/security Message-ID: <20010914175718.A1118@hades.hell.gr> References: <200109141118.f8EBIhd29603@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109141118.f8EBIhd29603@hak.lan.Awfulhak.org>; from brian@freebsd-services.com on Fri, Sep 14, 2001 at 12:18:43PM +0100 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Brian Somers Subject: Re: Checking changes to listening ports in /etc/security Date: Fri, Sep 14, 2001 at 12:18:43PM +0100 > I think the attached patch makes things slightly better. We only run > sockstat once, and remove the trailing whitespace that sockstat emits > (making the diff lines look better when viewed on an 80 column > screen). Ahem, that's what happens when one works in 132 column modes. Yes, trailing spaces are better removed. > Could you look these over ? If you're happy with this I can commit > it. Looks great to me. I tested it with the usual four runs of periodic/daily/450.status-security that I used for my versions. It works great :) -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 9:54:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id CD24137B414 for ; Fri, 14 Sep 2001 09:54:18 -0700 (PDT) Received: (qmail 798 invoked by uid 1000); 14 Sep 2001 16:46:30 -0000 Date: Fri, 14 Sep 2001 19:46:30 +0300 From: Peter Pentchev To: Mike Smith Cc: rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? Message-ID: <20010914194630.A781@ringworld.oblivion.bg> Mail-Followup-To: Mike Smith , rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org References: <20010914180622.A512@ringworld.oblivion.bg> <200109141650.f8EGoN501078@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109141650.f8EGoN501078@mass.dis.org>; from msmith@freebsd.org on Fri, Sep 14, 2001 at 09:50:23AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 09:50:23AM -0700, Mike Smith wrote: > > A quote from the end of the boot_i386.8 manual page.. > > > > IMPORTANT NOTE: Because of limitations imposed by the conventional disk > > interface provided by the BIOS, all boot-related files and structures > > (including the kernel) that need to be accessed during the boot phase > > must reside on the disk at or below cylinder 1023 (as the BIOS under- > > stands the geometry). When a ``Disk error 0x1'' is reported by the sec- > > ond-stage bootstrap, it generally means that this requirement has not > > been adhered to. > > > > Just today I had a friend ask me if this is still true; I checked CVS > > history and found out that this comment was added by rnordier more than > > two years ago. Is this still true? > > No; it's quite possible now to boot from beyond the 1024 cylinder mark, > however boot0 does not install in 'packet' mode by default, which means > that you need to manually install/configure it before rebooting after > system installation. > > So we don't cleanly install for > 1024 cylinders, but it works with a > little tweaking. So.. if I read you right, booting correctly for > 1024 cylinders works if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd slice? Does this mean that boot1 and boot2 should work just fine if they are loaded by another kind of MBR loader (say, Grub), and they find out that they are placed beyond the 1023th cylinder? G'luck, Peter -- Nostalgia ain't what it used to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 9:56:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id DD48437B40F; Fri, 14 Sep 2001 09:56:27 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8EH41501267; Fri, 14 Sep 2001 10:04:01 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109141704.f8EH41501267@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Pentchev Cc: rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? In-reply-to: Your message of "Fri, 14 Sep 2001 19:46:30 +0300." <20010914194630.A781@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Sep 2001 10:04:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > So.. if I read you right, booting correctly for > 1024 cylinders works > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > slice? Does this mean that boot1 and boot2 should work just fine if they > are loaded by another kind of MBR loader (say, Grub), and they find out > that they are placed beyond the 1023th cylinder? This should work, yes. -- ... 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 Sep 14 10:15:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 1449F37B40D for ; Fri, 14 Sep 2001 10:15:52 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8EHFma26076; Fri, 14 Sep 2001 10:15:48 -0700 Date: Fri, 14 Sep 2001 10:15:48 -0700 From: Brooks Davis To: Leo Bicknell Cc: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914101548.B7169@Odin.AC.HMC.Edu> References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914103037.A5619@ussenterprise.ufp.org>; from bicknell@ufp.org on Fri, Sep 14, 2001 at 10:30:37AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 14, 2001 at 10:30:37AM -0400, Leo Bicknell wrote: > On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote: > > Is there any difference between Gold and Silver cards from > > a compatibility standpoint (with the usual Apple Airport cards)? >=20 > With WEP encryption turned off they both work together fine. I've > seen many used in mixed enviornments. With WEP turned on, they > are completely incomptable. The silver cards do a 40 bit encryption, > and the gold cards do a 128 bit encryption, and it seems the gold > cards can't be stepped back to 40 bit. Unless Apple is mangling the firmware or someone screwed up the driver, this is false. Gold Lucent cards are capable of 40-bit crypto. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --lEGEL1/lMxI0MVQ2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ojtDXY6L6fI4GtQRAhPAAKCUxpATwfHzUfEremCPh6awX4/3BQCgq/IA T0b47d2Xa87aLIu4CNv1gmw= =B8gu -----END PGP SIGNATURE----- --lEGEL1/lMxI0MVQ2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 10:34:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id A185737B412 for ; Fri, 14 Sep 2001 10:34:09 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8EHX8c06830; Fri, 14 Sep 2001 13:33:08 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8EHX5f19548; Fri, 14 Sep 2001 13:33:05 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 7727758; Fri, 14 Sep 2001 13:32:42 -0400 Message-ID: <3BA23F2E.23F68B29@mitre.org> Date: Fri, 14 Sep 2001 13:32:30 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis Cc: Leo Bicknell , hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brooks Davis wrote: > > On Fri, Sep 14, 2001 at 10:30:37AM -0400, Leo Bicknell wrote: > > On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote: > > > Is there any difference between Gold and Silver cards from > > > a compatibility standpoint (with the usual Apple Airport cards)? > > > > With WEP encryption turned off they both work together fine. I've > > seen many used in mixed enviornments. With WEP turned on, they > > are completely incomptable. The silver cards do a 40 bit encryption, > > and the gold cards do a 128 bit encryption, and it seems the gold > > cards can't be stepped back to 40 bit. > > Unless Apple is mangling the firmware or someone screwed up the driver, > this is false. Gold Lucent cards are capable of 40-bit crypto. Aren't the airport cards just plain old Silver Lucent cards? If so, then either the Gold or the Silver should work fine. In fact I know the silver works fine because I have an Airport at home that I talk to with a Silver card. There's a FreeBSD port that lets you configure the box from your machine. In Windowsland there's a program called FreeBase, and of course the Airport comes with Mac tools bundled. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 10:50:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.iae.nl [212.61.26.37]) by hub.freebsd.org (Postfix) with ESMTP id 766BF37B412 for ; Fri, 14 Sep 2001 10:50:08 -0700 (PDT) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id TAA16617 for freebsd-hackers@freebsd.org; Fri, 14 Sep 2001 19:50:07 +0200 (MET DST) Received: by drawbridge.oasis.IAEhv.nl (Postfix, from userid 226) id A834E3E02; Fri, 14 Sep 2001 19:48:53 +0200 (CEST) Subject: kernel memory size To: freebsd-hackers@freebsd.org Date: Tue, 11 Sep 2001 14:46:47 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010914174853.A834E3E02@drawbridge.oasis.IAEhv.nl> From: volf@oasis.IAEhv.nl (Frank Volf) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a way to increase the memory size that is allocated by the kernel to a certain kernel memory pool (is that the correct word?): I mean, I have options VM_KMEM_SIZE="(64*1024*1024)" in my kernel config file, and it appears that I'm only allowed to use half of that memory for a certain pool: # vmstat -m | grep Filter 16 uc_devlist, p1003.1b, IP Filter, igmp, routetbl, ether_multi, vnodes, 256 file desc, FFS node, newblk, IP Filter, routetbl, ifaddr, vnodes, 512 uc_devlist, UFS mount, IP Filter, mount, BIO buffer, ptys, msg, 32K VM pgdata, UFS ihash, inodedep, IP Filter, devbuf IP Filter 276 158K 23307K 32768K 47735 0 0 16,256,512,32K Howerver, this box is a dedicated traffic filtering box, and I want to increase the available kernel memory for this kmalloc category. I grepped in the source, but apart from the assignment type->ks_limit = vm_kmem_size / 2; in kern_malloc.c, I could not find a place were this limit is increased. Is it possible to circumvent this? Frank BTW: I'm running FreeBSD 4.3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11: 3: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 143FF37B409 for ; Fri, 14 Sep 2001 11:03:03 -0700 (PDT) Received: (qmail 22052 invoked from network); 14 Sep 2001 18:03:02 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 18:03:02 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010914180622.A512@ringworld.oblivion.bg> Date: Fri, 14 Sep 2001 11:02:53 -0700 (PDT) From: John Baldwin To: Peter Pentchev Subject: RE: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@FreeBSD.org, rnordier@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-01 Peter Pentchev wrote: > Hi, > > A quote from the end of the boot_i386.8 manual page.. > > IMPORTANT NOTE: Because of limitations imposed by the conventional disk > interface provided by the BIOS, all boot-related files and structures > (including the kernel) that need to be accessed during the boot phase > must reside on the disk at or below cylinder 1023 (as the BIOS under- > stands the geometry). When a ``Disk error 0x1'' is reported by the sec- > ond-stage bootstrap, it generally means that this requirement has not > been adhered to. > > Just today I had a friend ask me if this is still true; I checked CVS > history and found out that this comment was added by rnordier more than > two years ago. Is this still true? Not in boot1, boot2, and the loader. boot0 has to have the workaround manually enabled, but sysinstall does that during installation. -- 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 Sep 14 11: 3: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id CD94337B40F for ; Fri, 14 Sep 2001 11:03:03 -0700 (PDT) Received: (qmail 38199 invoked from network); 14 Sep 2001 18:03:03 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 18:03:03 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200109141650.f8EGoN501078@mass.dis.org> Date: Fri, 14 Sep 2001 11:02:57 -0700 (PDT) From: John Baldwin To: Mike Smith Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@FreeBSD.org, rnordier@FreeBSD.org, Peter Pentchev Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-01 Mike Smith wrote: >> A quote from the end of the boot_i386.8 manual page.. >> >> IMPORTANT NOTE: Because of limitations imposed by the conventional disk >> interface provided by the BIOS, all boot-related files and structures >> (including the kernel) that need to be accessed during the boot phase >> must reside on the disk at or below cylinder 1023 (as the BIOS under- >> stands the geometry). When a ``Disk error 0x1'' is reported by the sec- >> ond-stage bootstrap, it generally means that this requirement has not >> been adhered to. >> >> Just today I had a friend ask me if this is still true; I checked CVS >> history and found out that this comment was added by rnordier more than >> two years ago. Is this still true? > > No; it's quite possible now to boot from beyond the 1024 cylinder mark, > however boot0 does not install in 'packet' mode by default, which means > that you need to manually install/configure it before rebooting after > system installation. > > So we don't cleanly install for > 1024 cylinders, but it works with a > little tweaking. Actually, sysinstall has a hack to turn on EDD (aka packet mode) support if the drive has > 1024 cylinders. -- 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 Sep 14 11: 8:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 97F7837B408; Fri, 14 Sep 2001 11:08:28 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id A79A25021A; Fri, 14 Sep 2001 11:08:26 -0700 Message-ID: <3BA2479A.4582C4BC@urx.com> Date: Fri, 14 Sep 2001 11:08:26 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Peter Pentchev , rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: <200109141704.f8EH41501267@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > slice? Does this mean that boot1 and boot2 should work just fine if they > > are loaded by another kind of MBR loader (say, Grub), and they find out > > that they are placed beyond the 1023th cylinder? > > This should work, yes. I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I had to go back to the boot1 from 4.3 before I could boot. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11:24:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A98A337B40D; Fri, 14 Sep 2001 11:24:55 -0700 (PDT) Received: (from rnordier@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8EIOtU40806; Fri, 14 Sep 2001 11:24:55 -0700 (PDT) (envelope-from rnordier) From: Message-Id: <200109141824.f8EIOtU40806@freefall.freebsd.org> Subject: Re: Does boot1 still have a > 1023 cyl limit? In-Reply-To: <20010914180622.A512@ringworld.oblivion.bg> from Peter Pentchev at "Sep 14, 2001 6: 6:22 pm" To: roam@ringlet.net (Peter Pentchev) Date: Fri, 14 Sep 2001 11:24:54 -0700 (PDT) Cc: rnordier@FreeBSD.org, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > A quote from the end of the boot_i386.8 manual page.. > > IMPORTANT NOTE: Because of limitations imposed by the conventional disk > interface provided by the BIOS, all boot-related files and structures > (including the kernel) that need to be accessed during the boot phase > must reside on the disk at or below cylinder 1023 (as the BIOS under- > stands the geometry). When a ``Disk error 0x1'' is reported by the sec- > ond-stage bootstrap, it generally means that this requirement has not > been adhered to. > > Just today I had a friend ask me if this is still true; I checked CVS > history and found out that this comment was added by rnordier more than > two years ago. Is this still true? As others have already indicated, the info is out of date. There is at least one PR already open for this man page (PR 26692), so I'll try to tidy up this and any other factual inaccuracies when attending to that. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11:33:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C07D837B406; Fri, 14 Sep 2001 11:33:27 -0700 (PDT) Received: (from rnordier@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8EIXRf42001; Fri, 14 Sep 2001 11:33:27 -0700 (PDT) (envelope-from rnordier) From: Message-Id: <200109141833.f8EIXRf42001@freefall.freebsd.org> Subject: Re: Does boot1 still have a > 1023 cyl limit? In-Reply-To: <3BA2479A.4582C4BC@urx.com> from Kent Stewart at "Sep 14, 2001 11: 8:26 am" To: kstewart@urx.com Date: Fri, 14 Sep 2001 11:33:27 -0700 (PDT) Cc: msmith@freebsd.org, roam@ringlet.net, rnordier@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Stewart wrote: > Mike Smith wrote: > > > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > > slice? Does this mean that boot1 and boot2 should work just fine if they > > > are loaded by another kind of MBR loader (say, Grub), and they find out > > > that they are placed beyond the 1023th cylinder? > > > > This should work, yes. > > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > had to go back to the boot1 from 4.3 before I could boot. That could be serious. Can you post a brief description of your hardware, together with the BTX register dump if possible? boot1 was changed to address some problems with certain hardware, so it is important to know if other incompatibilities have been introduced. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11:40:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 768D337B403 for ; Fri, 14 Sep 2001 11:40:29 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8EJAmd19771 for hackers@FreeBSD.ORG; Fri, 14 Sep 2001 15:10:48 -0400 (EDT) (envelope-from bicknell) Date: Fri, 14 Sep 2001 15:10:48 -0400 From: Leo Bicknell To: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914151048.A19601@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , hackers@FreeBSD.ORG References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914101548.B7169@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Fri, Sep 14, 2001 at 10:15:48AM -0700 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 10:15:48AM -0700, Brooks Davis wrote: > Unless Apple is mangling the firmware or someone screwed up the driver, > this is false. Gold Lucent cards are capable of 40-bit crypto. How do you set this? I have been unable to set a 40 bit key, or set a card into '40 bit mode' with the Orinoco Windows 98 drivers, the FreeBSD drivers, or the Apple airport software. If this works it could solve a lot of problems for me. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 8E6EF37B409 for ; Fri, 14 Sep 2001 11:46:11 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.32 #1) id 15hxyb-0004Mb-00; Fri, 14 Sep 2001 21:46:09 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 15hxya-0005Rb-00; Fri, 14 Sep 2001 21:46:08 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: hackers@FreeBSD.ORG Cc: Brooks Davis Subject: Re: 802.11 with best Apple compatibility? In-reply-to: Your message of Fri, 14 Sep 2001 10:15:48 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Sep 2001 21:46:08 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG any success in using an Airport AP with non airport cards? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 11:48:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 28A7A37B401 for ; Fri, 14 Sep 2001 11:48:47 -0700 (PDT) Received: from hades.hell.gr (patr530-b093.otenet.gr [195.167.121.221]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8EImfd15420; Fri, 14 Sep 2001 21:48:42 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8EIPQv31661; Fri, 14 Sep 2001 21:25:26 +0300 (EEST) (envelope-from charon@labs.gr) Date: Fri, 14 Sep 2001 21:25:25 +0300 From: Giorgos Keramidas To: Igor Podlesny Cc: hackers@FreeBSD.ORG Subject: Re: Checking changes to listening ports in /etc/security Message-ID: <20010914212525.B21489@hades.hell.gr> References: <200109132125.f8DLP2d97096@hak.lan.Awfulhak.org> <20010914015203.A43352@hades.hell.gr> <22226074908.20010914111110@morning.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <22226074908.20010914111110@morning.ru>; from poige@morning.ru on Fri, Sep 14, 2001 at 11:11:10AM +0800 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Igor Podlesny Subject: Re[2]: Checking changes to listening ports in /etc/security Date: Fri, Sep 14, 2001 at 11:11:10AM +0800 > > Hello! > > I've done similar thing by myself also, cause I have been working with > some Linux distros, where it is an usual thing (I mean detection of > any listeners changes) and I consider this is useful. > > But, the idea is slightly different -- my code is being called every > minute (cron). Yes I thought of something like that too, and many of the /etc/security checks would be nice to run more often. But having all of the /etc/security checks run every minute is an overkill :( It would practically bring my box to its knees. I think I'll stick to a diff of sockstat.today and sockstat.yesterday in my daily security checks. -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 12: 4:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 9378137B403 for ; Fri, 14 Sep 2001 12:04:48 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8EJZRH21283; Fri, 14 Sep 2001 15:35:27 -0400 (EDT) (envelope-from bicknell) Date: Fri, 14 Sep 2001 15:35:27 -0400 From: Leo Bicknell To: Danny Braniss Cc: hackers@FreeBSD.ORG, Brooks Davis Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914153527.A21049@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , Danny Braniss , hackers@FreeBSD.ORG, Brooks Davis 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 danny@cs.huji.ac.il on Fri, Sep 14, 2001 at 09:46:08PM +0300 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 09:46:08PM +0300, Danny Braniss wrote: > any success in using an Airport AP with non airport cards? It works with Lucent gold cards at least. If you open it the card inside is a standard lucent silver card, not even relabeled. The guts are also a 'karlbridge', and the karlnet software can configure airports (at least older ones). Their web page is http://www.gbnet.net/karlnet/products/system/wireless_KBridge.html. It lists "Compatible with Lucent WaveLAN, C-SPEC, OverLAN, ASK, Pinnacle, WaveWireless, SpeedLAN and all other Lucent WaveLAN wireless LAN products sold worldwide." Apple may not have included full support, though. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 12: 7:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from net.tamu.edu (net.tamu.edu [128.194.177.50]) by hub.freebsd.org (Postfix) with ESMTP id 01D8B37B40F for ; Fri, 14 Sep 2001 12:07:15 -0700 (PDT) Received: by net.tamu.edu (Postfix, from userid 157) id E9E2915891; Fri, 14 Sep 2001 14:07:13 -0500 (CDT) Date: Fri, 14 Sep 2001 14:07:13 -0500 From: Dave Duchscher To: Danny Braniss Cc: hackers@FreeBSD.ORG, Brooks Davis Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914140713.A21667@net.tamu.edu> Mail-Followup-To: Danny Braniss , hackers@FreeBSD.ORG, Brooks Davis 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 danny@cs.huji.ac.il on Fri, Sep 14, 2001 at 09:46:08PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 09:46:08PM +0300, Danny Braniss wrote: > > any success in using an Airport AP with non airport cards? We have not had any problems using many different manufactures with the Airport AP. The only gotcha is if you using WEP. Different drivers using different methods of entering the key. Some take it as a hex number, others convert a text string into the full key. We decided not to use WEP so I haven't played with enough to give detailed instructions. There seems to be lots of gotchas on getting WEP to work between manufactures. DaveD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 12:22:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 61D7D37B410 for ; Fri, 14 Sep 2001 12:22:34 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8EJMTl17668; Fri, 14 Sep 2001 12:22:29 -0700 Date: Fri, 14 Sep 2001 12:22:29 -0700 From: Brooks Davis To: Leo Bicknell Cc: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010914122229.A7636@Odin.AC.HMC.Edu> References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <20010914151048.A19601@ussenterprise.ufp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914151048.A19601@ussenterprise.ufp.org>; from bicknell@ufp.org on Fri, Sep 14, 2001 at 03:10:48PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 14, 2001 at 03:10:48PM -0400, Leo Bicknell wrote: > On Fri, Sep 14, 2001 at 10:15:48AM -0700, Brooks Davis wrote: > > Unless Apple is mangling the firmware or someone screwed up the driver, > > this is false. Gold Lucent cards are capable of 40-bit crypto. >=20 > How do you set this? I have been unable to set a 40 bit key, or > set a card into '40 bit mode' with the Orinoco Windows 98 drivers, > the FreeBSD drivers, or the Apple airport software. If this works > it could solve a lot of problems for me. In FreeBSD all you do is: ifconfig wi0 wepkey <40-bit key> The same should work in windows though I haven't used the windows driver in months so I don't remember what the dialog looks like. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7olj0XY6L6fI4GtQRAsHtAJ4zxp41XeVY1f1ANIzva3CfNTYeDwCfTwiz NPa05sOXTBSB18qAnauZ02M= =WW/Y -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 13:16:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id C2F1F37B406; Fri, 14 Sep 2001 13:16:15 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id A58FA801D0; Fri, 14 Sep 2001 13:16:15 -0700 Message-ID: <3BA2658E.C962BCC4@urx.com> Date: Fri, 14 Sep 2001 13:16:14 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: rnordier@FreeBSD.org Cc: msmith@freebsd.org, roam@ringlet.net, freebsd-hackers@freebsd.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: <200109141833.f8EIXRf42001@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG rnordier@FreeBSD.org wrote: > > Kent Stewart wrote: > > > Mike Smith wrote: > > > > > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > > > slice? Does this mean that boot1 and boot2 should work just fine if they > > > > are loaded by another kind of MBR loader (say, Grub), and they find out > > > > that they are placed beyond the 1023th cylinder? > > > > > > This should work, yes. > > > > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > > had to go back to the boot1 from 4.3 before I could boot. > > That could be serious. Can you post a brief description of your > hardware, together with the BTX register dump if possible? boot1 was > changed to address some problems with certain hardware, so it is > important to know if other incompatibilities have been introduced. The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are identical models. All are rated at ATA-100. The loader has been Win XP Pro since beta2 and runs FreeBSD about half of the time. BTX - Register dump int=00000006 err=00000000 efl=00030216 eip=00000de7 eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 BTX halted Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 13:39:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id AC53937B401; Fri, 14 Sep 2001 13:39:33 -0700 (PDT) Received: (from ambrisko@localhost) by ambrisko.com (8.11.3/8.11.3) id f8EKdNT75021; Fri, 14 Sep 2001 13:39:23 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200109142039.f8EKdNT75021@ambrisko.com> Subject: Re: Does boot1 still have a > 1023 cyl limit? In-Reply-To: <200109141833.f8EIXRf42001@freefall.freebsd.org> To: rnordier@FreeBSD.ORG Date: Fri, 14 Sep 2001 13:39:23 -0700 (PDT) Cc: kstewart@urx.com, msmith@FreeBSD.ORG, roam@ringlet.net, freebsd-hackers@FreeBSD.ORG, jhb@FreeBSD.ORG, mark@whistle.com, dhw@whistle.com X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG rnordier@FreeBSD.ORG writes: | Kent Stewart wrote: | | > Mike Smith wrote: | > > | > > > So.. if I read you right, booting correctly for > 1024 cylinders works | > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd | > > > slice? Does this mean that boot1 and boot2 should work just fine if they | > > > are loaded by another kind of MBR loader (say, Grub), and they find out | > > > that they are placed beyond the 1023th cylinder? | > > | > > This should work, yes. | > | > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I | > had to go back to the boot1 from 4.3 before I could boot. | | That could be serious. Can you post a brief description of your | hardware, together with the BTX register dump if possible? boot1 was | changed to address some problems with certain hardware, so it is | important to know if other incompatibilities have been introduced. ... in 4.3: warp% nm boot1.o | grep flags 00000199 t flags warp% in -current a21p% !nm nm boot1.o | grep flags 000001ba t flags a21p% Is someone writing into boot1 "flags"? Then there is a problem since this has moved. We did some work to avoid this "linking type" problem for xread in boot2.c to prevent this type of error. Do we have to do it for "flags"? I see in libdisk: static void Cfg_Boot_Mgr(u_char *mbr, int edd) { if (mbr[0x1b0] == 0x66 && mbr[0x1b1] == 0xbb) { if (edd) mbr[0x1bb] |= 0x80; /* Packet mode on */ else mbr[0x1bb] &= 0x7f; /* Packet mode off */ } } The mbr code it is modifying is in boot0 or mbr since I see in boot0 that: a21p% nm boot0.o | grep flags 000001bb t flags a21p% but I'm not seeing how it gets over to boot1 for this test? read.7: testb $FL_PACKET,%cs:MEM_REL+flags-start # LBA support e Doug A. PS. dhw ... could you try to set packet mode on some machines there and test it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 13:53:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 98F1E37B40D for ; Fri, 14 Sep 2001 13:53:04 -0700 (PDT) Received: (qmail 88428 invoked from network); 14 Sep 2001 20:53:03 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 20:53:03 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BA2658E.C962BCC4@urx.com> Date: Fri, 14 Sep 2001 13:52:56 -0700 (PDT) From: John Baldwin To: Kent Stewart Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@freebsd.org, roam@ringlet.net, msmith@freebsd.org, rnordier@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-01 Kent Stewart wrote: > > > rnordier@FreeBSD.org wrote: >> >> Kent Stewart wrote: >> >> > Mike Smith wrote: >> > > >> > > > So.. if I read you right, booting correctly for > 1024 cylinders works >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the >> > > > fbsd >> > > > slice? Does this mean that boot1 and boot2 should work just fine if >> > > > they >> > > > are loaded by another kind of MBR loader (say, Grub), and they find >> > > > out >> > > > that they are placed beyond the 1023th cylinder? >> > > >> > > This should work, yes. >> > >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I >> > had to go back to the boot1 from 4.3 before I could boot. >> >> That could be serious. Can you post a brief description of your >> hardware, together with the BTX register dump if possible? boot1 was >> changed to address some problems with certain hardware, so it is >> important to know if other incompatibilities have been introduced. > > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are > identical models. All are rated at ATA-100. The loader has been Win XP > Pro since beta2 and runs FreeBSD about half of the time. > > BTX - Register dump > > int=00000006 err=00000000 efl=00030216 eip=00000de7 > eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce > esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 > cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 > BTX halted 00000000 0F0000 sldt [bx+si] 00000003 007000 add [bx+si+0x0],dh 00000006 0000 add [bx+si],al 00000008 0000 add [bx+si],al 0000000A 00681E add [bx+si+0x1e],ch 0000000D 0000 add [bx+si],al That doesn't look to be very sane. Are you sure you haven't mixed an old version of boot2 with a new boot1 or vice versa? -- 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 Sep 14 13:53:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 496E337B403 for ; Fri, 14 Sep 2001 13:53:10 -0700 (PDT) Received: (qmail 46345 invoked from network); 14 Sep 2001 20:53:09 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 20:53:09 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200109142039.f8EKdNT75021@ambrisko.com> Date: Fri, 14 Sep 2001 13:53:01 -0700 (PDT) From: John Baldwin To: Doug Ambrisko Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: dhw@whistle.com, mark@whistle.com, freebsd-hackers@FreeBSD.ORG, roam@ringlet.net, msmith@FreeBSD.ORG, kstewart@urx.com, rnordier@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-01 Doug Ambrisko wrote: > rnordier@FreeBSD.ORG writes: >| Kent Stewart wrote: >| >| > Mike Smith wrote: >| > > >| > > > So.. if I read you right, booting correctly for > 1024 cylinders works >| > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the >| > > > fbsd >| > > > slice? Does this mean that boot1 and boot2 should work just fine if >| > > > they >| > > > are loaded by another kind of MBR loader (say, Grub), and they find >| > > > out >| > > > that they are placed beyond the 1023th cylinder? >| > > >| > > This should work, yes. >| > >| > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I >| > had to go back to the boot1 from 4.3 before I could boot. >| >| That could be serious. Can you post a brief description of your >| hardware, together with the BTX register dump if possible? boot1 was >| changed to address some problems with certain hardware, so it is >| important to know if other incompatibilities have been introduced. > > ... in 4.3: > warp% nm boot1.o | grep flags > 00000199 t flags > warp% > > in -current > a21p% !nm > nm boot1.o | grep flags > 000001ba t flags > a21p% > > Is someone writing into boot1 "flags"? Then there is a problem since this > has moved. We did some work to avoid this "linking type" problem for xread > in boot2.c to prevent this type of error. Do we have to do it for "flags"? > > I see in libdisk: > static void > Cfg_Boot_Mgr(u_char *mbr, int edd) > { > if (mbr[0x1b0] == 0x66 && mbr[0x1b1] == 0xbb) { > if (edd) > mbr[0x1bb] |= 0x80; /* Packet mode on */ > else > mbr[0x1bb] &= 0x7f; /* Packet mode off */ > } > } This is for boot0. Nothing should be touching boot1 flags. My guess is that someone has somehow mixed an old boot2 with the new boot1 which is jumping to the wrong place to call xread. The "code" at cs:eip looks a lot like the BPB in boot1 now. -- 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 Sep 14 13:58:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id 1CE3337B40D; Fri, 14 Sep 2001 13:58:31 -0700 (PDT) Received: (from ambrisko@localhost) by ambrisko.com (8.11.3/8.11.3) id f8EKwQI75128; Fri, 14 Sep 2001 13:58:26 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200109142058.f8EKwQI75128@ambrisko.com> Subject: Re: Does boot1 still have a > 1023 cyl limit? In-Reply-To: To: John Baldwin Date: Fri, 14 Sep 2001 13:58:26 -0700 (PDT) Cc: Doug Ambrisko , dhw@whistle.com, mark@whistle.com, freebsd-hackers@FreeBSD.org, roam@ringlet.net, msmith@FreeBSD.org, kstewart@urx.com, rnordier@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: | This is for boot0. Nothing should be touching boot1 flags. | My guess is that someone has somehow mixed an old boot2 with the new boot1 | which is jumping to the wrong place to call xread. The "code" at cs:eip looks | a lot like the BPB in boot1 now. Okay that basically how I read the code. Just wanted to make sure I wasn't missing something. Your theory sounds quite possible. Thanks, Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 14: 0:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 158E637B405; Fri, 14 Sep 2001 14:00:31 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id AFECCA01F4; Fri, 14 Sep 2001 14:00:28 -0700 Message-ID: <3BA26FEB.D701D7EE@urx.com> Date: Fri, 14 Sep 2001 14:00:27 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: freebsd-hackers@freebsd.org, roam@ringlet.net, msmith@freebsd.org, rnordier@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 14-Sep-01 Kent Stewart wrote: > > > > > > rnordier@FreeBSD.org wrote: > >> > >> Kent Stewart wrote: > >> > >> > Mike Smith wrote: > >> > > > >> > > > So.. if I read you right, booting correctly for > 1024 cylinders works > >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the > >> > > > fbsd > >> > > > slice? Does this mean that boot1 and boot2 should work just fine if > >> > > > they > >> > > > are loaded by another kind of MBR loader (say, Grub), and they find > >> > > > out > >> > > > that they are placed beyond the 1023th cylinder? > >> > > > >> > > This should work, yes. > >> > > >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > >> > had to go back to the boot1 from 4.3 before I could boot. > >> > >> That could be serious. Can you post a brief description of your > >> hardware, together with the BTX register dump if possible? boot1 was > >> changed to address some problems with certain hardware, so it is > >> important to know if other incompatibilities have been introduced. > > > > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 > > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller > > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are > > identical models. All are rated at ATA-100. The loader has been Win XP > > Pro since beta2 and runs FreeBSD about half of the time. > > > > BTX - Register dump > > > > int=00000006 err=00000000 efl=00030216 eip=00000de7 > > eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce > > esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 > > cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 > > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 > > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 > > BTX halted > > 00000000 0F0000 sldt [bx+si] > 00000003 007000 add [bx+si+0x0],dh > 00000006 0000 add [bx+si],al > 00000008 0000 add [bx+si],al > 0000000A 00681E add [bx+si+0x1e],ch > 0000000D 0000 add [bx+si],al > > That doesn't look to be very sane. > > Are you sure you haven't mixed an old version of boot2 with a new boot1 or vice > versa? Yes, coral# mount_msdos /dev/ad0s1 /mnt coral# cmp /mnt/boot1 /boot/boot1 coral# They test identical. Boot1 was copied to bootsect.bsd, which is referenced in boot.ini. Kent > > -- > > 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/ -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 14: 4: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id B033637B418 for ; Fri, 14 Sep 2001 14:03:56 -0700 (PDT) Received: (qmail 7198 invoked from network); 14 Sep 2001 21:03:53 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 21:03:53 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BA26FEB.D701D7EE@urx.com> Date: Fri, 14 Sep 2001 14:03:46 -0700 (PDT) From: John Baldwin To: Kent Stewart Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: rnordier@FreeBSD.org, msmith@freebsd.org, roam@ringlet.net, freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-01 Kent Stewart wrote: > > > John Baldwin wrote: >> >> On 14-Sep-01 Kent Stewart wrote: >> > >> > >> > rnordier@FreeBSD.org wrote: >> >> >> >> Kent Stewart wrote: >> >> >> >> > Mike Smith wrote: >> >> > > >> >> > > > So.. if I read you right, booting correctly for > 1024 cylinders >> >> > > > works >> >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in >> >> > > > the >> >> > > > fbsd >> >> > > > slice? Does this mean that boot1 and boot2 should work just fine >> >> > > > if >> >> > > > they >> >> > > > are loaded by another kind of MBR loader (say, Grub), and they find >> >> > > > out >> >> > > > that they are placed beyond the 1023th cylinder? >> >> > > >> >> > > This should work, yes. >> >> > >> >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I >> >> > had to go back to the boot1 from 4.3 before I could boot. >> >> >> >> That could be serious. Can you post a brief description of your >> >> hardware, together with the BTX register dump if possible? boot1 was >> >> changed to address some problems with certain hardware, so it is >> >> important to know if other incompatibilities have been introduced. >> > >> > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 >> > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller >> > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are >> > identical models. All are rated at ATA-100. The loader has been Win XP >> > Pro since beta2 and runs FreeBSD about half of the time. >> > >> > BTX - Register dump >> > >> > int=00000006 err=00000000 efl=00030216 eip=00000de7 >> > eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce >> > esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 >> > cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 >> > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 >> > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 >> > BTX halted >> >> 00000000 0F0000 sldt [bx+si] >> 00000003 007000 add [bx+si+0x0],dh >> 00000006 0000 add [bx+si],al >> 00000008 0000 add [bx+si],al >> 0000000A 00681E add [bx+si+0x1e],ch >> 0000000D 0000 add [bx+si],al >> >> That doesn't look to be very sane. >> >> Are you sure you haven't mixed an old version of boot2 with a new boot1 or >> vice >> versa? > > Yes, > > coral# mount_msdos /dev/ad0s1 /mnt > coral# cmp /mnt/boot1 /boot/boot1 > coral# > > They test identical. Boot1 was copied to bootsect.bsd, which is > referenced in boot.ini. Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk (the boot blocks do _not_ live in the /boot files, they are part of the disklabel) when you updated the boot1 in bootsect.bsd? -- 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 Sep 14 14: 4: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id DF18837B40B; Fri, 14 Sep 2001 14:04:02 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8EL2k622665; Fri, 14 Sep 2001 15:02:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8EL2jt24452; Fri, 14 Sep 2001 15:02:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109142102.f8EL2jt24452@harmony.village.org> To: Mike Smith Subject: Re: Driver structures & alignment Cc: Yar Tikhiy , hackers@FreeBSD.ORG, msmith@mass.dis.org In-reply-to: Your message of "Thu, 13 Sep 2001 16:09:57 PDT." <200109132309.f8DN9vX03967@mass.dis.org> References: <200109132309.f8DN9vX03967@mass.dis.org> Date: Fri, 14 Sep 2001 15:02:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200109132309.f8DN9vX03967@mass.dis.org> Mike Smith writes: : Any form of packing is going to cause problems for items that are : located in illegal fashions. It is almost more appropriate to use bus_space_{read,write} than using memory mapped structures. The bus macros will work for otherwise unaligned thigns, while direct access won't. Also, the compiler/system may optimize things in strange ways that cause problems. Do yourself a big favor and don't go down this path. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 14:40:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 8D06237B417; Fri, 14 Sep 2001 14:40:07 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id A9361BA0098; Fri, 14 Sep 2001 14:40:06 -0700 Message-ID: <3BA27936.E3D2FF13@urx.com> Date: Fri, 14 Sep 2001 14:40:06 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: rnordier@FreeBSD.org, msmith@freebsd.org, roam@ringlet.net, freebsd-hackers@freebsd.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 14-Sep-01 Kent Stewart wrote: > > > > > > John Baldwin wrote: > >> > >> On 14-Sep-01 Kent Stewart wrote: > >> > > >> > > >> > rnordier@FreeBSD.org wrote: > >> >> > >> >> Kent Stewart wrote: > >> >> > >> >> > Mike Smith wrote: > >> >> > > > >> >> > > > So.. if I read you right, booting correctly for > 1024 cylinders > >> >> > > > works > >> >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in > >> >> > > > the > >> >> > > > fbsd > >> >> > > > slice? Does this mean that boot1 and boot2 should work just fine > >> >> > > > if > >> >> > > > they > >> >> > > > are loaded by another kind of MBR loader (say, Grub), and they find > >> >> > > > out > >> >> > > > that they are placed beyond the 1023th cylinder? > >> >> > > > >> >> > > This should work, yes. > >> >> > > >> >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > >> >> > had to go back to the boot1 from 4.3 before I could boot. > >> >> > >> >> That could be serious. Can you post a brief description of your > >> >> hardware, together with the BTX register dump if possible? boot1 was > >> >> changed to address some problems with certain hardware, so it is > >> >> important to know if other incompatibilities have been introduced. > >> > > >> > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 > >> > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller > >> > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are > >> > identical models. All are rated at ATA-100. The loader has been Win XP > >> > Pro since beta2 and runs FreeBSD about half of the time. > >> > > >> > BTX - Register dump > >> > > >> > int=00000006 err=00000000 efl=00030216 eip=00000de7 > >> > eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce > >> > esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 > >> > cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 > >> > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 > >> > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 > >> > BTX halted > >> > >> 00000000 0F0000 sldt [bx+si] > >> 00000003 007000 add [bx+si+0x0],dh > >> 00000006 0000 add [bx+si],al > >> 00000008 0000 add [bx+si],al > >> 0000000A 00681E add [bx+si+0x1e],ch > >> 0000000D 0000 add [bx+si],al > >> > >> That doesn't look to be very sane. > >> > >> Are you sure you haven't mixed an old version of boot2 with a new boot1 or > >> vice > >> versa? > > > > Yes, > > > > coral# mount_msdos /dev/ad0s1 /mnt > > coral# cmp /mnt/boot1 /boot/boot1 > > coral# > > > > They test identical. Boot1 was copied to bootsect.bsd, which is > > referenced in boot.ini. > > Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk (the > boot blocks do _not_ live in the /boot files, they are part of the disklabel) > when you updated the boot1 in bootsect.bsd? That I didn't do. What do I need to do? I'm reading the man page and this is foreign country. This system was created at 4.2 and they were created for me at that point. I don't want to have to reset the ntldr butI could find the floppies to do a console recovery if I have to. Kent > > -- > > 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 -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 15: 5:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 20DC337B408 for ; Fri, 14 Sep 2001 15:05:10 -0700 (PDT) Received: (qmail 30802 invoked from network); 14 Sep 2001 22:05:09 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 22:05:09 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BA27936.E3D2FF13@urx.com> Date: Fri, 14 Sep 2001 15:05:01 -0700 (PDT) From: John Baldwin To: Kent Stewart Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@freebsd.org, roam@ringlet.net, msmith@freebsd.org, rnordier@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk >> (the >> boot blocks do _not_ live in the /boot files, they are part of the >> disklabel) >> when you updated the boot1 in bootsect.bsd? > > That I didn't do. What do I need to do? I'm reading the man page and > this is foreign country. This system was created at 4.2 and they were > created for me at that point. I don't want to have to reset the ntldr > butI could find the floppies to do a console recovery if I have to. > > Kent 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD and that the root filesystem is on. The files in /boot are sort of like the 'reference' version of the boot blocks. At the beginning of a FreeBSD slice is a 16-sector disklabel that describes the 'a', 'e', 'f' partitions, etc. The first sector of that is boot1. The second sector is the disklabel table itself, and the remaining 14 sectors hold boot2. Hope that makes sense. Until you use disklabel to update those boot blocks at the start of the slice, you are still using the old boot1 and boot2. However, you are using the ntldr which gets boot1 from somewhere else (not from the slice on the disk). When you updated that file, you ended up with mismatch since the new boot1 is still loading the boot2 off of the front of the slice, thus you end up with a new boot1 and an old boot2. -- 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 Sep 14 15: 9:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 3DAC937B408; Fri, 14 Sep 2001 15:09:33 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8EMH4504153; Fri, 14 Sep 2001 15:17:04 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109142217.f8EMH4504153@mass.dis.org> To: Warner Losh Cc: Mike Smith , Yar Tikhiy , hackers@FreeBSD.ORG, msmith@mass.dis.org, msmith@mass.dis.org Subject: Re: Driver structures & alignment In-Reply-To: Message from Warner Losh of "Fri, 14 Sep 2001 15:02:45 MDT." <200109142102.f8EL2jt24452@harmony.village.org> Date: Fri, 14 Sep 2001 15:17:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message <200109132309.f8DN9vX03967@mass.dis.org> Mike Smith writes: > : Any form of packing is going to cause problems for items that are > : located in illegal fashions. > > It is almost more appropriate to use bus_space_{read,write} than using > memory mapped structures. The bus macros will work for otherwise > unaligned thigns, while direct access won't. Also, the > compiler/system may optimize things in strange ways that cause > problems. Do yourself a big favor and don't go down this path. The most common use for alignment-sensitive data structures nowadays is in control structures exchanged with devices via busmaster DMA. Needless to say, the bus_space functions aren't very useful for this, and controlled alignment is necessary. Even then, I really want a mechanical way of generating a stub function to correct endianness in a structure based on the structure definition; we have a lot of drivers that are explicitly little-endian due to all this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 15:21:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74]) by hub.freebsd.org (Postfix) with ESMTP id D3D7D37B401 for ; Fri, 14 Sep 2001 15:21:45 -0700 (PDT) Received: from revolt.poohsticks.org (localhost [127.0.0.1]) by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id f8EMLhs84165; Fri, 14 Sep 2001 16:21:43 -0600 (MDT) (envelope-from drew@revolt.poohsticks.org) Message-Id: <200109142221.f8EMLhs84165@revolt.poohsticks.org> To: Dan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ide striping In-reply-to: Your message of "Fri, 14 Sep 2001 04:37:58 PDT." <20010914043602.P31777-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <84162.1000506103.1@revolt.poohsticks.org> Date: Fri, 14 Sep 2001 16:21:43 -0600 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010914043602.P31777-100000@gandalf.bravenet.com>, dphoenix@braven et.com writes: > >Does it make sense at all to stripe primary slave, >secondary master and slave together? >I would imagine it is a waste of time , just looking for thoughts >on this vs just a single primary master IDE. On a normal system, random access time will have a much bigger effect on performance than raw throughput. Although you can transfer 800K sequentially to or from the outer cylinders on a modern drive in 20ms, it's going to take just as long to transfer a single 4K block from an arbitrary disk location because of seek time and rotational latency. So, you'd be better off running a file system on each spindle and spreading your data out accross those file systems than striping for one big file system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 17: 9:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta04.onebox.com (mta04.onebox.com [64.68.77.147]) by hub.freebsd.org (Postfix) with ESMTP id B7D4A37B401 for ; Fri, 14 Sep 2001 17:09:47 -0700 (PDT) Received: from onebox.com ([10.1.101.8]) by mta04.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20010915000947.BYTU7831.mta04.onebox.com@onebox.com> for ; Fri, 14 Sep 2001 17:09:47 -0700 Received: from [165.121.193.212] by onebox.com with HTTP; Fri, 14 Sep 2001 17:09:47 -0700 Date: Fri, 14 Sep 2001 17:09:47 -0700 Subject: FreeBSD CW-Writer Problem From: "glenn gombert" To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20010915000947.BYTU7831.mta04.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am running FreeBSD Current and having a problem with my Memorx CRW-1662 CD-Writer and trying to use it with 'burncd'. I tried to write a small test 'iso' Image that I made using mkisofa and got the following error message "MODE_SELECT_BIG - Illegal Request'...when trying to write to the CRW-1662.... As another test I used 'burncd' to erase a CR-R/W with the 'burncd erase' command and it seemed to work just fine.... Can anyone tell me what the above error is about and how I might get the Memorex CRW-1662 with my FreeBSD Current System?? Thanks in Advance, Glenn Gombert Dayton, Ohio ___________________________________________________________________ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 19: 6: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 1DBA437B408 for ; Fri, 14 Sep 2001 19:06:05 -0700 (PDT) Received: (qmail 70627 invoked by uid 1001); 15 Sep 2001 02:17:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Sep 2001 02:17:08 -0000 Date: Fri, 14 Sep 2001 19:17:08 -0700 (PDT) From: Dan To: Subject: PIO mode Message-ID: <20010914191522.X61225-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 sn 2) retrying ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 sn 2) retrying ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 sn 2) retrying ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 sn 2) falling back to PIO mode we currently do replication on disks for mirrors of webservers. I am wondering what this PIO mode is and if this message should be any concern to me at all. we use dd to replicate complete disks....but i have been noticing fdisk bitching about wrong geometry. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 14 20: 7:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id CDC7537B408; Fri, 14 Sep 2001 20:07:43 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA26726; Sat, 15 Sep 2001 12:37:30 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010914194630.A781@ringworld.oblivion.bg> Date: Sat, 15 Sep 2001 12:37:23 +0930 (CST) From: "Daniel O'Connor" To: Peter Pentchev Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@FreeBSD.org, rnordier@FreeBSD.org, Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Sep-2001 Peter Pentchev wrote: > So.. if I read you right, booting correctly for > 1024 cylinders works > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > slice? Does this mean that boot1 and boot2 should work just fine if they > are loaded by another kind of MBR loader (say, Grub), and they find out > that they are placed beyond the 1023th cylinder? FYI the way you actually DO this is run boot0cfg :) eg.. boot0cfg -v -o packet /dev/mydiskdevice --- 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 Sep 14 22:25:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server1.lordlegacy.org (lordlegacy.org [209.61.182.147]) by hub.freebsd.org (Postfix) with ESMTP id B52CF37B410 for ; Fri, 14 Sep 2001 22:25:34 -0700 (PDT) Received: from sharon ([216.13.207.127]) by server1.lordlegacy.org (8.9.3/8.9.3) with SMTP id TAA06655; Fri, 14 Sep 2001 19:36:55 -0500 From: "Stephen Hurd" To: "Dan" , Subject: RE: PIO mode Date: Fri, 14 Sep 2001 23:33:50 -0600 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) In-reply-to: <20010914191522.X61225-100000@gandalf.bravenet.com> X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 > sn 2) retrying > ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 > sn 2) retrying > ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 > sn 2) retrying > ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3 > sn 2) falling back to PIO mode > > we currently do replication on disks for mirrors of webservers. > I am wondering what this PIO mode is and if this message should be any > concern to me at all. Basically, the ata driver is having a problem reading (WHICH MAY BE NORMAL... read on) and is falling back to Programmed Input Output mode... which is how ALL IDE devices were accessed before DMA mode came along... basically it's slower, uses more CPU, and is generally not as good. However, some Hard Drives/Controller combinations just plain won't run in DMA mode. This MAY not be a serious problem... basically if all was fine, but this suddenly started happening, something is failing... Actually, the ICRC error IS a bit frigtening... I always got read timeouts when it was a bad HD/controller combo... I'd like to revise my opinion to say "Get your data off now while you still can!" But maybe dig through the ata source... there's probobly helpful comments in that bit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 2:25:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id A710E37B406 for ; Sat, 15 Sep 2001 02:25:03 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f8F9PFR88190; Sat, 15 Sep 2001 11:25:15 +0200 (CEST) (envelope-from sos) From: SЬren Schmidt Message-Id: <200109150925.f8F9PFR88190@freebsd.dk> Subject: Re: FreeBSD CW-Writer Problem In-Reply-To: <20010915000947.BYTU7831.mta04.onebox.com@onebox.com> "from glenn gombert at Sep 14, 2001 05:09:47 pm" To: glenn gombert Date: Sat, 15 Sep 2001 11:25:14 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems glenn gombert wrote: > Hello, > > I am running FreeBSD Current and having a problem with my Memorx CRW-1662 > CD-Writer and trying to use it with 'burncd'. I tried to write a small > test 'iso' Image that I made using mkisofa and got the following error > message "MODE_SELECT_BIG - Illegal Request'...when trying to write to > the CRW-1662.... > > As another test I used 'burncd' to erase a CR-R/W with the 'burncd > erase' command and it seemed to work just fine.... > > Can anyone tell me what the above error is about and how I might get > the Memorex CRW-1662 with my FreeBSD Current System?? This is probably due to the new DAO mode code, try the below patch and see if that helps in normal burning mode, if your burner has problems with DAO mode (-d option) that will most likely still fail. Index: sys/dev/ata/atapi-cd.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/atapi-cd.c,v retrieving revision 1.100 diff -u -r1.100 atapi-cd.c --- sys/dev/ata/atapi-cd.c 10 Sep 2001 11:43:20 -0000 1.100 +++ sys/dev/ata/atapi-cd.c 15 Sep 2001 08:25:55 -0000 @@ -1407,9 +1407,7 @@ static int acd_init_writer(struct acd_softc *cdp, int test_write) { - struct write_param param; int8_t ccb[16]; - int error; bzero(ccb, sizeof(ccb)); ccb[0] = ATAPI_REZERO; @@ -1417,23 +1415,7 @@ ccb[0] = ATAPI_SEND_OPC_INFO; ccb[1] = 0x01; atapi_queue_cmd(cdp->atp, ccb, NULL, 0, ATPR_F_QUIET, 30, NULL, NULL); - - if ((error = acd_mode_sense(cdp, ATAPI_CDROM_WRITE_PARAMETERS_PAGE, - (caddr_t)¶m, sizeof(param)))) - return error; - param.data_length = 0; - param.page_code = ATAPI_CDROM_WRITE_PARAMETERS_PAGE; - param.page_length = 0x32; - param.test_write = test_write ? 1 : 0; - param.write_type = CDR_WTYPE_SESSION; - param.session_type = CDR_SESS_NONE; - param.fp = 0; - param.packet_size = 0; - param.track_mode = CDR_TMODE_AUDIO; - param.datablock_type = CDR_DB_RAW; - param.session_format = CDR_SESS_CDROM; - - return acd_mode_select(cdp, (caddr_t)¶m, param.page_length + 10); + return 0; } static int @@ -1613,6 +1595,7 @@ static int acd_send_cue(struct acd_softc *cdp, struct cdr_cuesheet *cuesheet) { + struct write_param param; int8_t ccb[16] = { ATAPI_SEND_CUE_SHEET, 0, 0, 0, 0, 0, cuesheet->len>>16, cuesheet->len>>8, cuesheet->len, 0, 0, 0, 0, 0, 0, 0 }; @@ -1621,6 +1604,24 @@ #ifdef ACD_DEBUG int i; #endif + + if ((error = acd_mode_sense(cdp, ATAPI_CDROM_WRITE_PARAMETERS_PAGE, + (caddr_t)¶m, sizeof(param)))) + return error; + param.data_length = 0; + param.page_code = ATAPI_CDROM_WRITE_PARAMETERS_PAGE; + param.page_length = 0x32; + param.test_write = cuesheet->test_write ? 1 : 0; + param.write_type = CDR_WTYPE_SESSION; + param.session_type = CDR_SESS_NONE; + param.fp = 0; + param.packet_size = 0; + param.track_mode = CDR_TMODE_AUDIO; + param.datablock_type = CDR_DB_RAW; + param.session_format = CDR_SESS_CDROM; + if ((error = acd_mode_select(cdp, (caddr_t)¶m, param.page_length + 10))) + return error; + buffer = malloc(cuesheet->len, M_ACD, M_NOWAIT); if (!buffer) return ENOMEM; Index: sys/sys/cdrio.h =================================================================== RCS file: /home/ncvs/src/sys/sys/cdrio.h,v retrieving revision 1.4 diff -u -r1.4 cdrio.h --- sys/sys/cdrio.h 10 Sep 2001 11:42:27 -0000 1.4 +++ sys/sys/cdrio.h 15 Sep 2001 08:19:38 -0000 @@ -71,6 +71,7 @@ struct cdr_cuesheet { int32_t len; struct cdr_cue_entry *entries; + int test_write; }; #define CDRIOCBLANK _IOW('c', 100, int) Index: usr.sbin/burncd/burncd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/burncd/burncd.c,v retrieving revision 1.16 diff -u -r1.16 burncd.c --- usr.sbin/burncd/burncd.c 11 Sep 2001 12:14:20 -0000 1.16 +++ usr.sbin/burncd/burncd.c 15 Sep 2001 08:19:07 -0000 @@ -58,7 +58,7 @@ static int fd, quiet, verbose, saved_block_size, notracks; void add_track(char *, int, int); -void do_DAO(void); +void do_DAO(int); void do_TAO(int, int); int write_file(struct track_info *); int roundup_blocks(struct track_info *); @@ -245,7 +245,7 @@ cdopen = 1; } if (dao) - do_DAO(); + do_DAO(test_write); else do_TAO(test_write, preemp); } @@ -308,7 +308,7 @@ } void -do_DAO(void) +do_DAO(int test_write) { struct cdr_cuesheet sheet; struct cdr_cue_entry cue[100]; @@ -390,6 +390,7 @@ sheet.len = j * 8; sheet.entries = cue; + sheet.test_write = test_write; if (verbose) { u_int8_t *ptr = (u_int8_t *)sheet.entries; @@ -404,9 +405,10 @@ if (ioctl(fd, CDRIOCSENDCUE, &sheet) < 0) err(EX_IOERR, "ioctl(CDRIOCSENDCUE)"); - +#if 0 if (ioctl(fd, CDRIOCNEXTWRITEABLEADDR, &addr) < 0) err(EX_IOERR, "ioctl(CDRIOCNEXTWRITEABLEADDR)"); +#endif for (i = 0; i < notracks; i++) { if (write_file(&tracks[i])) err(EX_IOERR, "write_file"); -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 4: 3:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id E7D9C37B409 for ; Sat, 15 Sep 2001 04:03:16 -0700 (PDT) Received: from ibook (ibook.Radio-do.de [193.101.164.23]) by gatekeeper.radio-do.de (Postfix) with ESMTP id E225A16F96; Sat, 15 Sep 2001 13:03:00 +0200 (CEST) Date: Sat, 15 Sep 2001 13:03:00 +0200 From: Frank Nobis Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: PIO mode Cc: "Dan" , To: "Stephen Hurd" X-Mailer: Apple Mail (2.388) In-Reply-To: Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit Message-Id: <20010915110300.E225A16F96@gatekeeper.radio-do.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am Samstag, 15. September 2001 um 07:33 schrieb Stephen Hurd: >> ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn >> 3 >> sn 2) retrying > > Actually, the ICRC error IS a bit frigtening... I always got read timeouts > when it was a bad HD/controller combo... I'd like to revise my opinion to > say > "Get your data off now while you still can!" But maybe dig through the ata > source... there's probobly helpful comments in that bit. > I had those problems once with a HPT370 controller. The problem was at last bad cable. After trying three different 80 wire types I had success. I had no more ICRC errors since then. Frank -- Frank Nobis Landgrafenstr. 130 44139 Dortmund To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 5:25:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.teledis.be (mail.teledis.be [217.117.32.52]) by hub.freebsd.org (Postfix) with ESMTP id 504BD37B40B for ; Sat, 15 Sep 2001 05:25:52 -0700 (PDT) Received: from natalie ([217.117.38.8]) by mail.teledis.be (Netscape Messaging Server 4.15) with SMTP id GJPEJ301.DEN for ; Sat, 15 Sep 2001 14:25:51 +0200 Message-ID: <000b01c13de2$31b78ae0$0201a8c0@teledisnet.be> From: "Sansonetti Laurent" To: Subject: error in man page kvm_nlist(3) ? Date: Sat, 15 Sep 2001 14:30:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I think there's an error in man page for kvm_nlist(3): a reference to kldsym(2) which doesn't exist in the manual... pinux@arrakis ~> man kvm_nlist | grep kldsym kldsym(2) is used to locate the symbol. This is a less than perfect emu- kldsym(2), kvm(3), kvm_close(3), kvm_getargv(3), kvm_getenvv(3), pinux@arrakis ~> man 2 kldsym No entry for kldsym in section 2 of the manual I'm running 4.2-RELEASE. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 5:33:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.teledis.be (mail.teledis.be [217.117.32.52]) by hub.freebsd.org (Postfix) with ESMTP id 8166537B413 for ; Sat, 15 Sep 2001 05:33:35 -0700 (PDT) Received: from natalie ([217.117.38.8]) by mail.teledis.be (Netscape Messaging Server 4.15) with SMTP id GJPEVY01.KGX for ; Sat, 15 Sep 2001 14:33:34 +0200 Message-ID: <001501c13de3$45dd8320$0201a8c0@teledisnet.be> From: "Sansonetti Laurent" To: Subject: storing routine code in kernel memory using kvm interface Date: Sat, 15 Sep 2001 14:38:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there a way to store a function in kernel memory using KVM interface ? I have written a tty spy'er, which simply hijack discipline line entries for a tty, and as you know probably, those routines must be situated in kernel land. I know that I should use KLD for that, but i'm still curious.. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 5:45: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id CCBDC37B407 for ; Sat, 15 Sep 2001 05:45:02 -0700 (PDT) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 7D8A63E28; Sat, 15 Sep 2001 05:45:02 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 708DC3C12E; Sat, 15 Sep 2001 05:45:02 -0700 (PDT) To: "Sansonetti Laurent" Cc: freebsd-hackers@freebsd.org Subject: Re: error in man page kvm_nlist(3) ? In-Reply-To: <000b01c13de2$31b78ae0$0201a8c0@teledisnet.be>; from lorenzo@linuxbe.org on "Sat, 15 Sep 2001 14:30:24 +0200" Date: Sat, 15 Sep 2001 05:44:57 -0700 From: Dima Dorfman Message-Id: <20010915124502.7D8A63E28@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Sansonetti Laurent" wrote: > Hi, > > I think there's an error in man page for kvm_nlist(3): a reference to > kldsym(2) which doesn't exist in the manual... > > pinux@arrakis ~> man kvm_nlist | grep kldsym > kldsym(2) is used to locate the symbol. This is a less than perfect > emu- > kldsym(2), kvm(3), kvm_close(3), kvm_getargv(3), kvm_getenvv(3), > pinux@arrakis ~> man 2 kldsym > No entry for kldsym in section 2 of the manual > > I'm running 4.2-RELEASE. This last part is the problem. The kldsym(2) manual page exists in more recent releases. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 5:50:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 01F4D37B40C for ; Sat, 15 Sep 2001 05:50:14 -0700 (PDT) Received: from mindspring.com (dialup-209.247.139.129.Dial1.SanJose1.Level3.net [209.247.139.129]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id FAA04825; Sat, 15 Sep 2001 05:50:04 -0700 (PDT) Message-ID: <3BA34EAA.38878044@mindspring.com> Date: Sat, 15 Sep 2001 05:50:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sansonetti Laurent Cc: freebsd-hackers@freebsd.org Subject: Re: storing routine code in kernel memory using kvm interface References: <001501c13de3$45dd8320$0201a8c0@teledisnet.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sansonetti Laurent wrote: > > Hi, > > Is there a way to store a function in kernel memory using KVM interface ? > > I have written a tty spy'er, which simply hijack discipline line entries for > a tty, and as you know probably, those routines must be situated in kernel > land. > > I know that I should use KLD for that, but i'm still curious.. No. You can not allocate memory safely to prevent the kernel reusing it and stomping your code, and you can not guarantee your hook installation will be done atomically without getting context switched or interrupted via a hardware interrupt, thus panic'ing the kernel. Not to mention that you would have to know a huge amount about the VM system to establish mappings, and those mappings wouldn't be atomic, either, and without them, your kernel would panic with a "page not present". Use a KLD instead, unless this is a cracking tool, in which case go ahead and use /dev/kmem, if it's writeable, since repeated crashes with tracebacks pointing to a program using your uid and having /dev/kmem open will get your admin to you-proof his box. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 10:38:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id E801437B408 for ; Sat, 15 Sep 2001 10:38:29 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA06756; Sat, 15 Sep 2001 11:13:38 -0700 (PDT) Message-ID: <3BA38F7D.C0167616@elischer.org> Date: Sat, 15 Sep 2001 10:27:25 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Sansonetti Laurent Cc: freebsd-hackers@freebsd.org Subject: Re: storing routine code in kernel memory using kvm interface References: <001501c13de3$45dd8320$0201a8c0@teledisnet.be> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sansonetti Laurent wrote: > > Hi, > > Is there a way to store a function in kernel memory using KVM interface ? > > I have written a tty spy'er, which simply hijack discipline line entries for > a tty, and as you know probably, those routines must be situated in kernel > land. > > I know that I should use KLD for that, but i'm still curious.. why not use thw snoop interface? > > -- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 10:58: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id E7E5D37B401; Sat, 15 Sep 2001 10:57:58 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8FHvva53648; Sat, 15 Sep 2001 10:57:57 -0700 (PDT) (envelope-from obrien) Date: Sat, 15 Sep 2001 10:57:57 -0700 From: "David O'Brien" To: John Baldwin Cc: Kent Stewart , freebsd-hackers@FreeBSD.org, roam@ringlet.net, msmith@FreeBSD.org, rnordier@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? Message-ID: <20010915105757.A53569@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.org References: <3BA27936.E3D2FF13@urx.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 jhb@FreeBSD.org on Fri, Sep 14, 2001 at 03:05:01PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: > 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD Isn't `disklable -B ad0sX' more proper? (especially if the disk has multiple FreeBSD slices) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 11: 3:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 0AAD237B403; Sat, 15 Sep 2001 11:03:53 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8FI3bL53737; Sat, 15 Sep 2001 11:03:37 -0700 (PDT) (envelope-from obrien) Date: Sat, 15 Sep 2001 11:03:37 -0700 From: "David O'Brien" To: Yar Tikhiy Cc: Mike Smith , hackers@freebsd.org, msmith@mass.dis.org Subject: Re: Driver structures & alignment Message-ID: <20010915110337.B53569@dragon.nuxi.com> Reply-To: hackers@freebsd.org References: <200109132309.f8DN9vX03967@mass.dis.org> <20010914122344.A38530@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914122344.A38530@snark.rinet.ru>; from yar@freebsd.org on Fri, Sep 14, 2001 at 12:23:44PM +0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 14, 2001 at 12:23:44PM +0400, Yar Tikhiy wrote: > E.g., will the following structure: > struct foo { > }; > contain alignment holes in any architecture/compiler? It is best to order this from largest to smallest size if you are worried about alignment holes, etc. int64_t d; /* 8-byte boundary */ int32_t c; /* 4-byte boundary */ int32_t f; /* 4-byte boundary */ int16_t a; int16_t b; int8_t e[4]; -- -- David (obrien@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 Sep 15 11:15:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 95D1437B407; Sat, 15 Sep 2001 11:15:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8FIDxn00891; Sat, 15 Sep 2001 12:13:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8FIDwW02011; Sat, 15 Sep 2001 12:13:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109151813.f8FIDwW02011@harmony.village.org> To: hackers@FreeBSD.ORG Subject: Re: Driver structures & alignment Cc: Yar Tikhiy , Mike Smith , msmith@mass.dis.org In-reply-to: Your message of "Sat, 15 Sep 2001 11:03:37 PDT." <20010915110337.B53569@dragon.nuxi.com> References: <20010915110337.B53569@dragon.nuxi.com> <200109132309.f8DN9vX03967@mass.dis.org> <20010914122344.A38530@snark.rinet.ru> Date: Sat, 15 Sep 2001 12:13:58 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010915110337.B53569@dragon.nuxi.com> "David O'Brien" writes: : It is best to order this from largest to smallest size if you are worried : about alignment holes, etc. : : int64_t d; /* 8-byte boundary */ : int32_t c; /* 4-byte boundary */ : int32_t f; /* 4-byte boundary */ : int16_t a; : int16_t b; : int8_t e[4]; unfortunately, there are many device structures that are passed around via DMA and hte like that don't let you do this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 11:17:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from durga.arc.nasa.gov (durga.arc.nasa.gov [128.102.141.14]) by hub.freebsd.org (Postfix) with ESMTP id 1E2DF37B40F for ; Sat, 15 Sep 2001 11:17:24 -0700 (PDT) Received: from localhost (sullivan@localhost) by durga.arc.nasa.gov (8.11.6/8.11.6) with ESMTP id f8FIHMQ01221; Sat, 15 Sep 2001 11:17:22 -0700 (PDT) X-Authentication-Warning: durga.arc.nasa.gov: sullivan owned process doing -bs Date: Sat, 15 Sep 2001 11:17:22 -0700 (PDT) From: Don Sullivan X-X-Sender: sullivan@durga.arc.nasa.gov To: freebsd-hackers@FreeBSD.ORG Subject: Large disk (>1 TB) support in FBD4.3 ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I probably SHOULD know this, but how can I get a 1.3 TB RAID 5 array recognized by FBD 4.3 (Or, 4.4 RC5) ? Thanks for reading this, Don ----------------------------------------------- Don Sullivan NASA Ames Research Center MS 242-4 Moffett Field, CA 94035-1000 Office: +1.650.604.0526 Lab: +1.650.604.0595 (best bet) Fax: +1.650.604.4680 email: dsullivan@gaia.arc.nasa.gov ----------------------------------------------- Never argue with an idiot; They drag you down to their level, and then beat you with experience. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 11:29:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 3D32037B40B for ; Sat, 15 Sep 2001 11:29:44 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f8FITfI09292; Sat, 15 Sep 2001 11:29:41 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 15 Sep 2001 11:29:41 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Don Sullivan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Large disk (>1 TB) support in FBD4.3 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don- too bad- I'm over in NAS in building N-258 and just took down the h/w where we could test this (Alpha 4100 with 8 Qlogic cards && 8 150GB MegaDrive RAID arrays)- We're excessing this equipment because the mass storage group's work was terminated due to budgetary goop. Typically there's no problem in *recognizing* raw SCSI disk, or RAID units that look like a SCSI disks- Mike or others will have to speak about how well specifical supported RAID cards for FreeBSD will handle something that large. A more problematic issue is whether FFS can reliably handle > 1TB. We did some tests with NetBSD at 1TB a couple of years ago- you have to use larger block and frag sizes (we were using 32k/8k)- but I've never myelf gotten FreeBSD up above 500GB. I was going to do so when the rather flakey h/w I was on above was set to be excessed. If I'd known you needed the work done- I could have kept it going a couple more weeks and we could worked on sorting it out. -matt On Sat, 15 Sep 2001, Don Sullivan wrote: > > I probably SHOULD know this, but how can I get a 1.3 TB > RAID 5 array recognized by FBD 4.3 (Or, 4.4 RC5) ? > > Thanks for reading this, > Don > ----------------------------------------------- > Don Sullivan > NASA Ames Research Center > MS 242-4 > Moffett Field, CA 94035-1000 > Office: +1.650.604.0526 > Lab: +1.650.604.0595 (best bet) > Fax: +1.650.604.4680 > email: dsullivan@gaia.arc.nasa.gov > ----------------------------------------------- > > Never argue with an idiot; > They drag you down to their level, > and then beat you with experience. > > > 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 Sep 15 11:56:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 75F1837B407 for ; Sat, 15 Sep 2001 11:56:25 -0700 (PDT) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f8FIuI609623; Sat, 15 Sep 2001 20:56:19 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f8FIukN18148; Sat, 15 Sep 2001 20:56:46 +0200 (CEST) Date: Sat, 15 Sep 2001 20:56:45 +0200 From: Bernd Walter To: Matthew Jacob Cc: Don Sullivan , freebsd-hackers@FreeBSD.ORG Subject: Re: Large disk (>1 TB) support in FBD4.3 ? Message-ID: <20010915205645.C17960@cicely20.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Sat, Sep 15, 2001 at 11:29:41AM -0700 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 15, 2001 at 11:29:41AM -0700, Matthew Jacob wrote: > > Don- too bad- I'm over in NAS in building N-258 and just took down the h/w > where we could test this (Alpha 4100 with 8 Qlogic cards && 8 150GB MegaDrive > RAID arrays)- We're excessing this equipment because the mass storage group's > work was terminated due to budgetary goop. > > Typically there's no problem in *recognizing* raw SCSI disk, or RAID units > that look like a SCSI disks- Mike or others will have to speak about how well > specifical supported RAID cards for FreeBSD will handle something that large. I'm not shure about recent SCSI definitions, but as long as a physical sector is sized at 512 Bytes and SCSI uses 32Bit unsigned numbers a (virtual) SCSI disk is limited to 2T. Maybe recent SCSI specs already defined a new set of read/write... > A more problematic issue is whether FFS can reliably handle > 1TB. We did some > tests with NetBSD at 1TB a couple of years ago- you have to use larger block > and frag sizes (we were using 32k/8k)- but I've never myelf gotten FreeBSD up > above 500GB. I was going to do so when the rather flakey h/w I was on above > was set to be excessed. If I'd known you needed the work done- I could have > kept it going a couple more weeks and we could worked on sorting it out. FFS in it's design can go up to 2G * fragsize - that means 2T with default fragsize of 1k. The Problem is that FreeBSD internaly uses 32bit signed Blocknumbers for 512Bytes/Block independend of it's physical size. This limits to 1T. I successfully build 600G partitions with vinum and I've heared of users running partitions near the 1T limit. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 12:17:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id E0A1637B40E; Sat, 15 Sep 2001 12:17:21 -0700 (PDT) Received: by sharmas.dhs.org (Postfix, from userid 500) id C2AF55E448; Sat, 15 Sep 2001 12:21:06 -0700 (PDT) Date: Sat, 15 Sep 2001 12:21:06 -0700 From: Arun Sharma To: hackers@freebsd.org Cc: java@freebsd.org Subject: NGPT port upgraded to 1.0.1 Message-ID: <20010915122106.A26894@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Added spinlock support, so that libc functions are reentrant. This is based on the Aug 3 release from the NGPT project. http://www.freebsd.org/cgi/query-pr.cgi?pr=30599 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 12:26:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gigi.excite.com (gigi.excite.com [199.172.152.110]) by hub.freebsd.org (Postfix) with ESMTP id 27ED537B401; Sat, 15 Sep 2001 12:26:21 -0700 (PDT) Received: from doby.excite.com ([199.172.152.182]) by gigi.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010915192616.KRZG24199.gigi.excite.com@doby.excite.com>; Sat, 15 Sep 2001 12:26:16 -0700 Message-ID: <20024143.1000581976859.JavaMail.imail@doby.excite.com> Date: Sat, 15 Sep 2001 12:26:10 -0700 (PDT) From: john_wilson100@excite.com To: freebsd-hackers@freebsd.org Subject: VINUM PANIC ON -STABLE Cc: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I posted a message to -hackers several days ago, complete with a kernel backtrace. The panic is 100% reproducible on my machine running the latest -stable. Does anyone care? My message to Greg Lehey was rejected by his mail server, but I am pretty sure he reads both -hackers and -stable. 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 Sep 15 12:26:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 62C5337B408; Sat, 15 Sep 2001 12:26:23 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8FJQFH72306; Sat, 15 Sep 2001 12:26:15 -0700 (PDT) (envelope-from obrien) Date: Sat, 15 Sep 2001 12:26:15 -0700 From: "David O'Brien" To: Warner Losh Cc: hackers@FreeBSD.ORG, Yar Tikhiy , Mike Smith , msmith@mass.dis.org Subject: Re: Driver structures & alignment Message-ID: <20010915122615.A72222@dragon.nuxi.com> Reply-To: hackers@FreeBSD.ORG References: <20010915110337.B53569@dragon.nuxi.com> <200109132309.f8DN9vX03967@mass.dis.org> <20010914122344.A38530@snark.rinet.ru> <20010915110337.B53569@dragon.nuxi.com> <200109151813.f8FIDwW02011@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109151813.f8FIDwW02011@harmony.village.org>; from imp@harmony.village.org on Sat, Sep 15, 2001 at 12:13:58PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote: > In message <20010915110337.B53569@dragon.nuxi.com> "David O'Brien" writes: > : It is best to order this from largest to smallest size if you are worried > : about alignment holes, etc. > : > : int64_t d; /* 8-byte boundary */ > : int32_t c; /* 4-byte boundary */ > : int32_t f; /* 4-byte boundary */ > : int16_t a; > : int16_t b; > : int8_t e[4]; > > unfortunately, there are many device structures that are passed around > via DMA and hte like that don't let you do this... How come? The struct represents some [semi-]physical organization? -- -- David (obrien@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 Sep 15 12:29:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f42.law8.hotmail.com [216.33.241.42]) by hub.freebsd.org (Postfix) with ESMTP id 8C64537B40C for ; Sat, 15 Sep 2001 12:29:38 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 15 Sep 2001 12:29:38 -0700 Received: from 209.52.193.59 by lw8fd.law8.hotmail.msn.com with HTTP; Sat, 15 Sep 2001 19:29:38 GMT X-Originating-IP: [209.52.193.59] From: "Craig R" To: freebsd-hackers@freebsd.org Subject: ATAPI CD-R/RW Suggestion Date: Sat, 15 Sep 2001 12:29:38 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Sep 2001 19:29:38.0476 (UTC) FILETIME=[C2691EC0:01C13E1C] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think that burncd is a good program, and I appreciate the development of it, but I feel that there may be a better solution for owners of atapi burners. cdrecord is basically an industry standard, and should be able to be used by owers of atapi burners under FreeBSD. Linux has a driver called "ide-scsi" which emulates an ATAPI cd writer as a scsi device. This allows the use of such mainstream programs as cdrecord. I would more than greatly appreciate the writing of a similar driver for FreeBSD so that I can master CDs as good (or better?) than I can in Linux. Also, an addition to atapicd(4) that closes the cdrom tray, waits for the cd to spool up, then mounts the cd would be nice. This saves people from getting the error stating that the device is busy (spinning up) and having to try to mount again. Another cool feature would be the driver detecting that the "eject" button on the drive (if even possible) has been pushed and then attempting to unmount it would be really handy. Once again, I would like to emphasize that my first suggestion is in no way intended to make the creators of burncd feel like they wasted their time. I am only suggesting an alternative, not a replacement. Craig _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 12:48:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74]) by hub.freebsd.org (Postfix) with ESMTP id 9075437B405 for ; Sat, 15 Sep 2001 12:48:19 -0700 (PDT) Received: from revolt.poohsticks.org (localhost [127.0.0.1]) by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id f8FJmIs88068 for ; Sat, 15 Sep 2001 13:48:18 -0600 (MDT) (envelope-from drew@revolt.poohsticks.org) Message-Id: <200109151948.f8FJmIs88068@revolt.poohsticks.org> To: hackers@FreeBSD.ORG Subject: Re: Driver structures & alignment In-reply-to: Your message of "Sat, 15 Sep 2001 12:26:15 PDT." <20010915122615.A72222@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <88065.1000583297.1@revolt.poohsticks.org> Date: Sat, 15 Sep 2001 13:48:18 -0600 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010915122615.A72222@dragon.nuxi.com>, dev-null@NUXI.com writes: >On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote: >> unfortunately, there are many device structures that are passed around >> via DMA and hte like that don't let you do this... > >How come? The struct represents some [semi-]physical organization? Other hardware uses the data directly (say scatter/gathre lists for a SCSI host adapter or ethernet board) and you can't (or don't want to) change the firmware on the device. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 12:51:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 08CEE37B406; Sat, 15 Sep 2001 12:51:46 -0700 (PDT) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f8FJpf610007; Sat, 15 Sep 2001 21:51:42 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f8FJq7l18311; Sat, 15 Sep 2001 21:52:07 +0200 (CEST) Date: Sat, 15 Sep 2001 21:52:06 +0200 From: Bernd Walter To: john_wilson100@excite.com Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010915215206.E17960@cicely20.cicely.de> References: <20024143.1000581976859.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20024143.1000581976859.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sat, Sep 15, 2001 at 12:26:10PM -0700 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 15, 2001 at 12:26:10PM -0700, john_wilson100@excite.com wrote: > I posted a message to -hackers several days ago, complete with a kernel > backtrace. The panic is 100% reproducible on my machine running the > latest -stable. I saw two unsualy points in your config. 1. why use more than one vinum partition per physical drive? vinum itself handles it very well - it's a volume manager. 2. I don't think that a stripe size not matching n * page size is a good choice. Both points shouldn't crash your box but it's at least not very common. > Does anyone care? My message to Greg Lehey was rejected by his mail server, > but I am pretty sure he reads both -hackers and -stable. There must be a reson to reject. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 13:33: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id B264037B410 for ; Sat, 15 Sep 2001 13:33:00 -0700 (PDT) Received: (qmail 89364 invoked from network); 15 Sep 2001 20:33:00 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Sep 2001 20:33:00 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010915105757.A53569@dragon.nuxi.com> Date: Sat, 15 Sep 2001 13:32:54 -0700 (PDT) From: John Baldwin To: "David O'Brien" Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: rnordier@FreeBSD.org, msmith@FreeBSD.org, roam@ringlet.net, freebsd-hackers@FreeBSD.org, Kent Stewart Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Sep-01 David O'Brien wrote: > On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: >> 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD > > Isn't `disklable -B ad0sX' more proper? (especially if the disk has > multiple FreeBSD slices) On x86, yes. I think disklabel -B ad0 will still work though. (It finds the first FreeBSD slice and does it I think). -- 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 Sat Sep 15 13:35:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 94F5437B403 for ; Sat, 15 Sep 2001 13:35:50 -0700 (PDT) Received: (qmail 48211 invoked by uid 1001); 15 Sep 2001 20:35:48 +0000 (GMT) To: ticso@mail.cicely.de Cc: john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: VINUM PANIC ON -STABLE From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 15 Sep 2001 21:52:06 +0200" References: <20010915215206.E17960@cicely20.cicely.de> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 15 Sep 2001 22:35:48 +0200 Message-ID: <48209.1000586148@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I saw two unsualy points in your config. > 1. why use more than one vinum partition per physical drive? > vinum itself handles it very well - it's a volume manager. > 2. I don't think that a stripe size not matching n * page size is a > good choice. There are excellent reasons why you want a stripe size which is *not* a multiple of the page size: To distribute the inodes across all disks. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 13:36:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2030837B407; Sat, 15 Sep 2001 13:35:55 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA26700; Sun, 16 Sep 2001 06:35:52 +1000 Date: Sun, 16 Sep 2001 06:35:27 +1000 (EST) From: Bruce Evans X-X-Sender: To: Cc: , Subject: Re: cvs commit: src/lib/libatm atm_addr.c cache_key.c ioctl_subr.c ip_addr.c ip_checksum.c timer.c In-Reply-To: <200109151939.f8FJdKF28278@earth.backplane.com> Message-ID: <20010916062557.V30137-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 15 Sep 2001, Matt Dillon wrote: > I'm redirecting this to freebsd-hackers. > > Ok, I've comitted a new set of changes to libatm. Please check them out. > When we get a format that enough people are happy with we can start > converting the other libraries. I'm not particularly interested in > fixing old old problems, I just want to get the __FBSDID() stuff in shape. I prefer the following (for one of the changed files). Especially the empty line after the copyright message: %%% Index: atm_addr.c =================================================================== RCS file: /home/ncvs/src/lib/libatm/atm_addr.c,v retrieving revision 1.6 diff -u -2 -r1.6 atm_addr.c --- atm_addr.c 2001/09/15 19:36:55 1.6 +++ atm_addr.c 2001/09/15 20:25:39 @@ -24,10 +24,12 @@ * notice must be reproduced on all copies. */ -#include + +#ifdef VENDOR_ID #ifndef lint -#if 0 /* original (broken) import id */ static char *RCSid = "@(#) $Id: atm_addr.c,v 1.1 1998/07/09 21:45:18 johnc Exp $"; #endif #endif + +#include __FBSDID("$FreeBSD: src/lib/libatm/atm_addr.c,v 1.6 2001/09/15 19:36:55 dillon Exp $"); %%% (VENDOR_ID is intended to be left undefined.) This still changes the vendor id excessively relative to rev.1.1. The vendor put it after the comment after the copyright comment, and restoring it in rev.1.5 moved it to a different place. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 13:45:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 80BAD37B40C; Sat, 15 Sep 2001 13:45:28 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8FKiBn01221; Sat, 15 Sep 2001 14:44:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8FKiBW02752; Sat, 15 Sep 2001 14:44:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109152044.f8FKiBW02752@harmony.village.org> To: hackers@FreeBSD.ORG Subject: Re: Driver structures & alignment Cc: Yar Tikhiy , Mike Smith , msmith@mass.dis.org In-reply-to: Your message of "Sat, 15 Sep 2001 12:26:15 PDT." <20010915122615.A72222@dragon.nuxi.com> References: <20010915122615.A72222@dragon.nuxi.com> <20010915110337.B53569@dragon.nuxi.com> <200109132309.f8DN9vX03967@mass.dis.org> <20010914122344.A38530@snark.rinet.ru> <20010915110337.B53569@dragon.nuxi.com> <200109151813.f8FIDwW02011@harmony.village.org> Date: Sat, 15 Sep 2001 14:44:11 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010915122615.A72222@dragon.nuxi.com> "David O'Brien" writes: : On Sat, Sep 15, 2001 at 12:13:58PM -0600, Warner Losh wrote: : > In message <20010915110337.B53569@dragon.nuxi.com> "David O'Brien" writes: : > : It is best to order this from largest to smallest size if you are worried : > : about alignment holes, etc. : > : : > : int64_t d; /* 8-byte boundary */ : > : int32_t c; /* 4-byte boundary */ : > : int32_t f; /* 4-byte boundary */ : > : int16_t a; : > : int16_t b; : > : int8_t e[4]; : > : > unfortunately, there are many device structures that are passed around : > via DMA and hte like that don't let you do this... : : How come? The struct represents some [semi-]physical organization? Because the hardware designer may have done silly things. These are hardware data structures. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 13:51:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id F35BA37B403; Sat, 15 Sep 2001 13:51:28 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id AF482E30156; Sat, 15 Sep 2001 13:51:20 -0700 Message-ID: <3BA3BF48.7B9E853E@urx.com> Date: Sat, 15 Sep 2001 13:51:20 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Cc: John Baldwin , roam@ringlet.net, msmith@FreeBSD.org, rnordier@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: <3BA27936.E3D2FF13@urx.com> <20010915105757.A53569@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: > > 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD > > Isn't `disklable -B ad0sX' more proper? (especially if the disk has > multiple FreeBSD slices) I tried ad0s3 and the system was just reinstalled using a binary install. It wouldn't boot past the "-" symbol. Kent > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 14:30:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 0482637B40A; Sat, 15 Sep 2001 14:30:04 -0700 (PDT) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f8FLTv610504; Sat, 15 Sep 2001 23:29:58 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f8FLUQR18548; Sat, 15 Sep 2001 23:30:26 +0200 (CEST) Date: Sat, 15 Sep 2001 23:30:25 +0200 From: Bernd Walter To: sthaug@nethelp.no Cc: ticso@mail.cicely.de, john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010915233025.F17960@cicely20.cicely.de> References: <20010915215206.E17960@cicely20.cicely.de> <48209.1000586148@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <48209.1000586148@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Sep 15, 2001 at 10:35:48PM +0200 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 15, 2001 at 10:35:48PM +0200, sthaug@nethelp.no wrote: > > I saw two unsualy points in your config. > > 1. why use more than one vinum partition per physical drive? > > vinum itself handles it very well - it's a volume manager. > > 2. I don't think that a stripe size not matching n * page size is a > > good choice. > > There are excellent reasons why you want a stripe size which is *not* a > multiple of the page size: To distribute the inodes across all disks. It's unusual to have less than 4(8)k inode area per cylinder group. An inode is 128 bytes that means 4k gives you only 32 inodes. At best you don't use the pagesize but the cluster size, which is 64k on FFS. Breaking a single access into 2 or even more phycally access is additional load and more wait time, as you need wait for 2 disks to inform the filesystem a write back, which gives you bigger delays and you also need to wait for both disks on a read. What you usually realy want is to break cylinder groups so that their management area gets distributed over the physicaly disks. FFS itself does a good job to distribute data over the cylinder groups. Here a random example: ticso@cicely6# newfs -N /dev/da0b Warning: 1408 sector(s) in last cylinder unallocated /dev/da0b: 400000 sectors in 98 cylinders of 1 tracks, 4096 sectors 195.3MB in 5 cyl groups (22 c/g, 44.00MB/g, 9728 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480 We have 9728 inodes/group, which means 1216k for each group. That is much more than 4k. If you have two disks and use 256k stripe size it even breaks the inode area. But we have 44M cg size, which is what we want to break. With 2 disks 192k is a sensefull stripe size: 44 * 1024 / 2 / 192 = 117.33333333333333333333 -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 16:34:42 2001 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 4C73B37B407 for ; Sat, 15 Sep 2001 16:34:38 -0700 (PDT) Received: from doby.excite.com ([199.172.152.182]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010915233438.LUJB22472.kuku.excite.com@doby.excite.com>; Sat, 15 Sep 2001 16:34:38 -0700 Message-ID: <33343543.1000596877983.JavaMail.imail@doby.excite.com> Date: Sat, 15 Sep 2001 16:34:32 -0700 (PDT) From: john_wilson100@excite.com To: Bernd Walter Subject: Re: VINUM PANIC ON -STABLE Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 15 Sep 2001 21:52:06 +0200, Bernd Walter wrote: > On Sat, Sep 15, 2001 at 12:26:10PM -0700, john_wilson100@excite.com wrote: > > I posted a message to -hackers several days ago, complete with a kernel > > backtrace. The panic is 100% reproducible on my machine running the > > latest -stable. > > I saw two unsualy points in your config. > 1. why use more than one vinum partition per physical drive? > vinum itself handles it very well - it's a volume manager. If one gets corrupted (for whatever reason), the other one will keep going (assuming that one volume will not touch another's partitions) > 2. I don't think that a stripe size not matching n * page size is a > good choice. > Both points shouldn't crash your box but it's at least not very common. A stripe size that is a power of 2 will put all superblocks on the same subdisk. > > Does anyone care? My message to Greg Lehey was rejected by his mail server, > > but I am pretty sure he reads both -hackers and -stable. > > There must be a reson to reject. Let's hear it. John > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > _______________________________________________________ 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 Sep 15 17: 8:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 4171637B410 for ; Sat, 15 Sep 2001 17:08:24 -0700 (PDT) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f8G086612807; Sun, 16 Sep 2001 02:08:10 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f8G08Tx18817; Sun, 16 Sep 2001 02:08:29 +0200 (CEST) Date: Sun, 16 Sep 2001 02:08:28 +0200 From: Bernd Walter To: john_wilson100@excite.com Cc: Bernd Walter , freebsd-hackers@freebsd.org Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010916020828.I17960@cicely20.cicely.de> References: <33343543.1000596877983.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <33343543.1000596877983.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sat, Sep 15, 2001 at 04:34:32PM -0700 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 15, 2001 at 04:34:32PM -0700, john_wilson100@excite.com wrote: > > On Sat, 15 Sep 2001 21:52:06 +0200, Bernd Walter wrote: > > > On Sat, Sep 15, 2001 at 12:26:10PM -0700, john_wilson100@excite.com > wrote: > > > I posted a message to -hackers several days ago, complete with a kernel > > > backtrace. The panic is 100% reproducible on my machine running the > > > latest -stable. > > > > I saw two unsualy points in your config. > > 1. why use more than one vinum partition per physical drive? > > vinum itself handles it very well - it's a volume manager. > > If one gets corrupted (for whatever reason), the other one will keep going > (assuming that one volume will not touch another's partitions) If you don't trust in vinum not to mix subdisk range... But I don't think vinum has problems here. The difference is that you have 2 instances of the vinum configuration per disk. > > 2. I don't think that a stripe size not matching n * page size is a > > good choice. > > Both points shouldn't crash your box but it's at least not very common. > > A stripe size that is a power of 2 will put all superblocks on the same > subdisk. The Superblocks are all in the same offset in a cylindergroup. That means: 1. It's sufficient to enshure that the cylindergroups start at with alternating disks. Well with 279 you don't have to think if it meets the requirement. 2. If you loose one disk with 279k stripe size you are not interested in reading this superblocks anymore. This is a difference with concatenating where you have a good chance you recover some of the data and there you don't have to wory about this anyway. > > > Does anyone care? My message to Greg Lehey was rejected by his mail > server, > > > but I am pretty sure he reads both -hackers and -stable. > > > > There must be a reson to reject. > > Let's hear it. I know that he had an URL explaining what he rejects. But I'm almost shure that it's described in the error message you got back. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 17: 8:35 2001 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 4346537B409; Sat, 15 Sep 2001 17:08:22 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 505236AD6A; Sun, 16 Sep 2001 09:38:20 +0930 (CST) Date: Sun, 16 Sep 2001 09:38:20 +0930 From: Greg Lehey To: john_wilson100@excite.com Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, Bernd Walter Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010916093820.I26893@wantadilla.lemis.com> References: <33343543.1000596877983.JavaMail.imail@doby.excite.com> <20024143.1000581976859.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20024143.1000581976859.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sat, Sep 15, 2001 at 12:26:10PM -0700 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Saturday, 15 September 2001 at 12:26:10 -0700, john_wilson100@excite.com wrote: > I posted a message to -hackers several days ago, complete with a > kernel backtrace. Well, not quite 42 hours. That's not "several days" in my book. You also omitted a lot of other information I asked for. > The panic is 100% reproducible on my machine running the latest > -stable. > > Does anyone care? Yes, I care. > My message to Greg Lehey was rejected by his mail server, Well, there's something that you can fix in the meantime :-) > but I am pretty sure he reads both -hackers and -stable. Correct. I also have other things to do. When you sent the backtrace, I was away from home doing some training, and I didn't have access to my machines. I'll look at it, but it would be *really* nice if you'd give me the info I ask for. On Saturday, 15 September 2001 at 16:34:32 -0700, john_wilson100@excite.com wrote: > On Sat, 15 Sep 2001 21:52:06 +0200, Bernd Walter wrote: >> On Sat, Sep 15, 2001 at 12:26:10PM -0700, john_wilson100@excite.com wrote: >>> I posted a message to -hackers several days ago, complete with a kernel >>> backtrace. The panic is 100% reproducible on my machine running the >>> latest -stable. >> >> I saw two unsualy points in your config. >> 1. why use more than one vinum partition per physical drive? >> vinum itself handles it very well - it's a volume manager. > > If one gets corrupted (for whatever reason), the other one will keep going > (assuming that one volume will not touch another's partitions) The only time the driver can get "corrupted" is when writing the configuration information. By creating two drives per spindle, you are doubling this likelihood. > >> 2. I don't think that a stripe size not matching n * page size is a >> good choice. >> Both points shouldn't crash your box but it's at least not very common. > > A stripe size that is a power of 2 will put all superblocks on the same > subdisk. Correct. There's nothing wrong with your stripe size. I suspect you took it from one of the valid examples in the man page. >>> Does anyone care? My message to Greg Lehey was rejected by his >>> mail server, but I am pretty sure he reads both -hackers and >>> -stable. >> >> There must be a reson to reject. > > Let's hear it. You did. It was in the reject message. You apparently chose to ignore it. You've made me go and look in the logs: Sep 14 10:58:46 wantadilla postfix/smtpd[17429]: reject: RCPT from ewey-rwcmta.excite.com[198.3.99.191]: 550 : Sender address rejected: " Mail rejected. See http://www.lemis.com/dontspam.html"; from= to= Do you understand now? Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html 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 Sat Sep 15 17: 8:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1A7C837B410; Sat, 15 Sep 2001 17:08:38 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8G08VG84286; Sat, 15 Sep 2001 17:08:31 -0700 (PDT) (envelope-from obrien) Date: Sat, 15 Sep 2001 17:08:31 -0700 From: "David O'Brien" To: Bruce Evans Cc: freebsd-hackers@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libatm atm_addr.c cache_key.c ioctl_subr.c ip_addr.c ip_checksum.c timer.c Message-ID: <20010915170831.A84246@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200109151939.f8FJdKF28278@earth.backplane.com> <20010916062557.V30137-100000@delplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010916062557.V30137-100000@delplex.bde.org>; from bde@zeta.org.au on Sun, Sep 16, 2001 at 06:35:27AM +1000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 16, 2001 at 06:35:27AM +1000, Bruce Evans wrote: > Especially the empty line after the copyright message: Agreed. > __FBSDID("$FreeBSD: src/lib/libatm/atm_addr.c,v 1.6 2001/09/15 19:36:55 dillon Exp $"); What about changing this to __FBSD(), which is what I was using in a prototype to reduce the number of characters in the macro name (and thus reduce the wrap around). -- -- David (obrien@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 Sep 15 17:16:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id CB93C37B405; Sat, 15 Sep 2001 17:16:34 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8G0GY429697; Sat, 15 Sep 2001 17:16:34 -0700 (PDT) (envelope-from dillon) Date: Sat, 15 Sep 2001 17:16:34 -0700 (PDT) From: Matt Dillon Message-Id: <200109160016.f8G0GY429697@earth.backplane.com> To: "David O'Brien" Cc: Bruce Evans , freebsd-hackers@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libatm atm_addr.c cache_key.c ioctl_subr.c ip_addr.c ip_checksum.c timer.c References: <200109151939.f8FJdKF28278@earth.backplane.com> <20010916062557.V30137-100000@delplex.bde.org> <20010915170831.A84246@dragon.nuxi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :What about changing this to __FBSD(), which is what I was using in a :prototype to reduce the number of characters in the macro name (and thus :reduce the wrap around). : :-- :-- David (obrien@FreeBSD.org) __FBSD() is too generic for a #define name in what is essentially a global header file. These are rcs id's, so it should be something like __FBSDID() or __FBSD_ID() or something like that, not just __FBSD(). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 17:49:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from math.missouri.edu (math.missouri.edu [128.206.49.180]) by hub.freebsd.org (Postfix) with ESMTP id 785F637B408 for ; Sat, 15 Sep 2001 17:49:18 -0700 (PDT) Received: from math.missouri.edu (cauchy.math.missouri.edu [128.206.49.166]) by math.missouri.edu (8.11.3/8.11.3) with ESMTP id f8G0nIK91940 for ; Sat, 15 Sep 2001 19:49:18 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <3BA3F70D.27C2136@math.missouri.edu> Date: Sat, 15 Sep 2001 19:49:17 -0500 From: Stephen Montgomery-Smith Organization: University of Missouri X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Could not bind Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have written a server program that listens on port 3000. The program works very well except for one feature. I am asking if that is normal, or whether I forgot something. If I run the program it does fine. If I then kill the program (after it has accepted connections), and then run the program again, the bind function fails to work, and I get a message like "Could not bind" (see program below). If I wait a while, like a minute or two, then the program will work again. Is this normal behavior, or did I miss something? I got the programming style from Richard Steven's book on network programming. The structure of the program is something like this: typedef struct { int connfd; struct in_addr addr; u_short port; } arg_pass_type; void *process_client(void *arg) { int connfd = ((arg_pass_type*)arg)->connfd; struct in_addr addr = ((arg_pass_type*)arg)->addr; u_short port = ((arg_pass_type*)arg)->port; free(arg); pthread_detach(pthread_self()); do_lots_of_stuff(); } int main () { int listenfd; struct sockaddr_in servaddr; socklen_t slen; pthread_t tid; arg_pass_type *arg; listenfd=socket(AF_INET,SOCK_STREAM,0); bzero(&servaddr,sizeof(servaddr)); servaddr.sin_family=AF_INET; servaddr.sin_addr.s_addr=htonl(INADDR_ANY); servaddr.sin_port=htons(3000); if (bind(listenfd,(struct sockaddr*)&servaddr,sizeof(servaddr)) < 0) { fprintf(stderr,"Could not bind\n"); exit(1); } listen(listenfd,6); while (1) { slen=sizeof(servaddr); arg = malloc(sizeof(arg_pass_type)); arg->connfd = accept(listenfd,(struct sockaddr*)&servaddr,&slen); arg->addr = servaddr.sin_addr; arg->port = servaddr.sin_port; pthread_create(&tid,NULL,process_client,(void*) arg); } exit(0); } -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 17:53:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 8610D37B405 for ; Sat, 15 Sep 2001 17:53:47 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f8G0riI11246; Sat, 15 Sep 2001 17:53:45 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 15 Sep 2001 17:53:44 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Stephen Montgomery-Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Could not bind In-Reply-To: <3BA3F70D.27C2136@math.missouri.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You should always use perror or strerror if a system call fails so you know *why* it fails. Then you can cross-references with the man(2) and man(3) pages to figure out what's up. On Sat, 15 Sep 2001, Stephen Montgomery-Smith wrote: > I have written a server program that listens on port 3000. The program > works very well except for one feature. I am asking if that is normal, > or whether I forgot something. > > If I run the program it does fine. If I then kill the program (after it > has accepted connections), and then run the program again, the bind > function fails to work, and I get a message like "Could not bind" (see > program below). If I wait a while, like a minute or two, then the > program will work again. Is this normal behavior, or did I miss > something? > > I got the programming style from Richard Steven's book on network > programming. The structure of the program is something like this: > > > typedef struct { > int connfd; > struct in_addr addr; > u_short port; > } > arg_pass_type; > > void *process_client(void *arg) { > int connfd = ((arg_pass_type*)arg)->connfd; > struct in_addr addr = ((arg_pass_type*)arg)->addr; > u_short port = ((arg_pass_type*)arg)->port; > > free(arg); > pthread_detach(pthread_self()); > do_lots_of_stuff(); > > } > > int main () { > int listenfd; > struct sockaddr_in servaddr; > socklen_t slen; > pthread_t tid; > arg_pass_type *arg; > > listenfd=socket(AF_INET,SOCK_STREAM,0); > bzero(&servaddr,sizeof(servaddr)); > servaddr.sin_family=AF_INET; > servaddr.sin_addr.s_addr=htonl(INADDR_ANY); > servaddr.sin_port=htons(3000); > if (bind(listenfd,(struct sockaddr*)&servaddr,sizeof(servaddr)) < 0) > { > fprintf(stderr,"Could not bind\n"); > exit(1); > } > listen(listenfd,6); > > while (1) > { > slen=sizeof(servaddr); > arg = malloc(sizeof(arg_pass_type)); > arg->connfd = accept(listenfd,(struct sockaddr*)&servaddr,&slen); > arg->addr = servaddr.sin_addr; > arg->port = servaddr.sin_port; > pthread_create(&tid,NULL,process_client,(void*) arg); > } > exit(0); > } > > -- > Stephen Montgomery-Smith > stephen@math.missouri.edu > http://www.math.missouri.edu/~stephen > > 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 Sep 15 17:58:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.bu.edu (CS.BU.EDU [128.197.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 3665637B406 for ; Sat, 15 Sep 2001 17:58:07 -0700 (PDT) Received: from csa.bu.edu (evms@csa [128.197.12.3]) by cs.bu.edu (8.10.1/8.10.1) with ESMTP id f8G0w5A22233 for ; Sat, 15 Sep 2001 20:58:05 -0400 (EDT) Received: (from evms@localhost) by csa.bu.edu (8.10.1/8.10.1) id f8G0w0503596; Sat, 15 Sep 2001 20:58:00 -0400 (EDT) Date: Sat, 15 Sep 2001 20:58:00 -0400 (EDT) Message-Id: <200109160058.f8G0w0503596@csa.bu.edu> From: Evan Sarmiento To: freebsd-hackers@freebsd.org Subject: interesting -current project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Since the relaes for 5.0 was extended another year, an interesting feature I'd like to see go in to the kernel is hooks. So users can add extra security checks.. etc. There's a project in its beginnings right now, www.freesoftware.fsf.org/jailuser/ Think anyone could join the prfw mailing list and help development? Thanks, Evan :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 18: 2:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id ABE7F37B403 for ; Sat, 15 Sep 2001 18:02:34 -0700 (PDT) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15iQKO-0005nk-00; Sun, 16 Sep 2001 02:02:32 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.6/8.11.4) id f8G12WI12959; Sun, 16 Sep 2001 02:02:32 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Sun, 16 Sep 2001 02:02:32 +0100 From: Ben Smithurst To: Stephen Montgomery-Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Could not bind Message-ID: <20010916020232.J43502@strontium.shef.vinosystems.com> References: <3BA3F70D.27C2136@math.missouri.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="oplxJGu+Ee5xywIT" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA3F70D.27C2136@math.missouri.edu> X-PGP-Key: http://www.smithurst.org/ben/pgp-key.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --oplxJGu+Ee5xywIT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Stephen Montgomery-Smith wrote: > listenfd=3Dsocket(AF_INET,SOCK_STREAM,0); > bzero(&servaddr,sizeof(servaddr)); > servaddr.sin_family=3DAF_INET; > servaddr.sin_addr.s_addr=3Dhtonl(INADDR_ANY); > servaddr.sin_port=3Dhtons(3000); > if (bind(listenfd,(struct sockaddr*)&servaddr,sizeof(servaddr)) < 0) You probably need to set the SO_REUSEADDR socket option; Stevens talks about this eventually, maybe you haven't read that far. Basically you need something like int foo =3D 1; and then call setsockopt(listenfd, SOL_SOCKET, SO_REUSEADDR, &foo, sizeof foo); between the socket() and listen() calls. Check setsockopt(2) and Stevens for more information (and to make sure I got the arguments and stuff right!) --=20 Ben Smithurst / ben@FreeBSD.org FreeBSD: The Power To Serve http://www.FreeBSD.org/ --oplxJGu+Ee5xywIT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7o/onbPzJ+yzvRCwRAi7IAJ9f+mOpZeSsxEfwrYezntV2h4VrhgCfbmJS iuJigiDKd1wqw6HStTjCzdI= =/rIA -----END PGP SIGNATURE----- --oplxJGu+Ee5xywIT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 15 18:40: 1 2001 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 000D937B40B; Sat, 15 Sep 2001 18:39:24 -0700 (PDT) Received: from slippery ([199.172.153.106]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010916013924.MKDN22472.kuku.excite.com@slippery>; Sat, 15 Sep 2001 18:39:24 -0700 Message-ID: <18954083.1000604364686.JavaMail.imail@slippery> Date: Sat, 15 Sep 2001 18:39:20 -0700 (PDT) From: john_wilson100@excite.com To: Greg Lehey Subject: Re: VINUM PANIC ON -STABLE Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Greg, I apologise in advance if this message is too long. On Sun, 16 Sep 2001 09:38:20 +0930, Greg Lehey wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Saturday, 15 September 2001 at 12:26:10 -0700, john_wilson100@excite.com wrote: > > > I posted a message to -hackers several days ago, complete > > with a kernel backtrace. > > Well, not quite 42 hours. That's not "several days" in my > book. You also omitted a lot of other information I asked > for. You are right, but I need to make this machine a file server as soon as possible, and I don't know how long I can keep the current broken setup. > > > The panic is 100% reproducible on my machine running the > > latest -stable. > > > > Does anyone care? > > Yes, I care. Good, I'll be happy to help you fix it. > > My message to Greg Lehey was rejected by his mail server, > > Well, there's something that you can fix in the meantime :-) > > > but I am pretty sure he reads both -hackers and -stable. > > Correct. I also have other things to do. When you sent the > backtrace, I was away from home doing some training, and I > didn't have access to my machines. I'll look at it, but it > would be *really* nice if you'd give me the info I ask for. No problem. I didn't realise that you asked for some specific information, but now that you've told me, here goes: 1) What problems are you having? Vinum panics. 2) Which version of FreeBSD are you running? FreeBSD 4.4-RC, built 12 Sep 2001 (supped around the same time) 3) Have you made any changes to the system sources, including Vinum? No. 4) Supply the output of the vinum list command. 4 drives: D data1 State: up Device /dev/ad4s1g Avail: 0/10240 MB (0%) D home1 State: up Device /dev/ad4s1h Avail: 0/38931 MB (0%) D data2 State: up Device /dev/ad6s1e Avail: 0/10240 MB (0%) D home2 State: up Device /dev/ad6s1f Avail: 0/37733 MB (0%) 2 volumes: V data State: up Plexes: 1 Size: 19 GB V home State: up Plexes: 1 Size: 74 GB 2 plexes: P data.p0 S State: up Subdisks: 2 Size: 19 GB P home.p0 S State: up Subdisks: 2 Size: 74 GB 4 subdisks: S data.p0.s0 State: up PO: 0 B Size: 9 GB S data.p0.s1 State: up PO: 279 kB Size: 9 GB S home.p0.s0 State: up PO: 0 B Size: 38 GB S home.p0.s1 State: up PO: 279 kB Size: 36 GB 5) Supply an extract of the Vinum history file. 13 Sep 2001 01:58:14.762508 *** vinum started *** 13 Sep 2001 01:58:14.763601 *** Created devices *** 13 Sep 2001 01:58:14.977566 create -v vinum.conf # The drives drive data1 device /dev/ad4s1g drive data2 device /dev/ad6s1e drive home1 device /dev/ad4s1h drive home2 device /dev/ad6s1f # One striped volume volume data plex org striped 279k sd length 0 drive data1 sd length 0 drive data2 volume home plex org striped 279k sd length 0 drive home1 sd length 0 drive home2 13 Sep 2001 01:58:15.030494 *** Created devices *** 13 Sep 2001 02:01:01.096464 *** vinum started *** 13 Sep 2001 02:01:01.097047 create -v vinum.conf # The drives drive data1 device /dev/ad4s1g drive data2 device /dev/ad6s1e drive home1 device /dev/ad4s1h drive home2 device /dev/ad6s1f # One striped volume volume data plex org striped 279k sd length 0 drive data1 sd length 0 drive data2 volume home plex org striped 279k sd length 0 drive home1 sd length 0 drive home2 13 Sep 2001 02:01:01.099272 *** Created devices *** 13 Sep 2001 02:02:21.094275 *** vinum started *** 13 Sep 2001 01:58:14.763601 *** Created devices *** 13 Sep 2001 02:02:24.464758 stop 13 Sep 2001 02:02:33.130188 *** vinum started *** 13 Sep 2001 02:02:33.130954 create -v vinum.conf # The drives drive data1 device /dev/ad4s1g drive data2 device /dev/ad6s1e drive home1 device /dev/ad4s1h drive home2 device /dev/ad6s1f # One striped volume volume data plex org striped 279k sd length 0 drive data1 sd length 0 drive data2 volume home plex org striped 279k sd length 0 drive home1 sd length 0 drive home2 13 Sep 2001 02:02:33.158054 *** Created devices *** 13 Sep 2001 02:13:47.686198 *** vinum started *** 13 Sep 2001 02:14:59.824765 *** vinum started *** 13 Sep 2001 02:14:59.825620 read ad4 ad6 13 Sep 2001 02:15:10.914699 *** vinum started *** 13 Sep 2001 02:15:10.915271 read ad4s1 ad6s1 13 Sep 2001 02:15:20.100632 *** vinum started *** 13 Sep 2001 02:15:20.101207 read /dev/ad4s1 /dev/ad6s1 13 Sep 2001 02:15:20.196171 *** Created devices *** 13 Sep 2001 02:29:58.399989 *** vinum started *** 13 Sep 2001 02:29:58.415789 info 13 Sep 2001 02:30:01.983586 *** vinum started *** 13 Sep 2001 02:30:01.984155 info 13 Sep 2001 02:30:13.001453 *** vinum started *** 13 Sep 2001 02:30:13.001991 dumpconfig 13 Sep 2001 02:31:24.133859 *** vinum started *** 13 Sep 2001 02:32:11.335262 *** vinum started *** 13 Sep 2001 02:32:11.335860 start 13 Sep 2001 02:32:11.413807 *** Created devices *** 13 Sep 2001 02:52:51.646474 *** vinum started *** 13 Sep 2001 02:52:51.662275 start 13 Sep 2001 02:52:51.754875 *** Created devices *** 13 Sep 2001 03:13:23.407808 *** vinum started *** 13 Sep 2001 03:13:23.424895 stop 13 Sep 2001 03:13:27.716186 *** vinum started *** 13 Sep 2001 03:13:27.716929 start 13 Sep 2001 03:13:27.835339 *** Created devices *** 16 Sep 2001 04:08:53.103875 *** vinum started *** 16 Sep 2001 04:08:53.112648 list 16 Sep 2001 04:09:08.872212 *** vinum started *** 16 Sep 2001 04:09:08.872769 list 6) Supply an extract of the file /var/log/messages. Sep 12 14:06:10 depot login: ROOT LOGIN (root) ON ttyv0 Sep 12 14:07:29 depot login: ROOT LOGIN (root) ON ttyv1 Sep 13 01:58:14 depot /kernel: vinum: loaded Sep 13 01:58:15 depot /kernel: vinum: drive data1 is up Sep 13 01:58:15 depot /kernel: vinum: drive home1 is up Sep 13 01:58:15 depot /kernel: vinum: drive home2 is up Sep 13 01:58:15 depot /kernel: vinum: removing 499 blocks of partial stripe at the end of data.p0 Sep 13 01:58:15 depot /kernel: vinum: data.p0 must have equal sized subdisks Sep 13 01:58:15 depot /kernel: Correcting length of data.p0: was 20970756, is 20970757 Sep 13 01:58:15 depot /kernel: vinum: data.p0.s0 is up Sep 13 01:58:15 depot /kernel: vinum: data.p0.s1 is up Sep 13 01:58:15 depot /kernel: vinum: data.p0 is up Sep 13 01:58:15 depot /kernel: vinum: data is up Sep 13 01:58:15 depot /kernel: vinum: removing 403 blocks of partial stripe at the end of home.p0 Sep 13 01:58:15 depot /kernel: vinum: home.p0 must have equal sized subdisks Sep 13 01:58:15 depot /kernel: Correcting length of home.p0: was 157008924, is 157008925 Sep 13 01:58:15 depot /kernel: vinum: home.p0.s0 is up Sep 13 01:58:15 depot /kernel: vinum: home.p0.s1 is up Sep 13 01:58:15 depot /kernel: vinum: home.p0 is up Sep 13 01:58:15 depot /kernel: vinum: home is up Sep 13 02:01:01 depot /kernel: vinum: removing 1 blocks of partial stripe at the end of data.p0 Sep 13 02:01:01 depot /kernel: vinum: data.p0 must have equal sized subdisks Sep 13 02:01:01 depot /kernel: Correcting length of data.p0: was 20970756, is 20970757 Sep 13 02:01:01 depot /kernel: vinum: removing 1 blocks of partial stripe at the end of home.p0 Sep 13 02:01:01 depot /kernel: vinum: home.p0 must have equal sized subdisks Sep 13 02:01:01 depot /kernel: Correcting length of home.p0: was 157008924, is 157008925 Sep 13 02:01:01 depot /kernel: vinum: removing 1 blocks of partial stripe at the end of data.p0 Sep 13 02:01:01 depot /kernel: vinum: data.p0 must have equal sized subdisks Sep 13 02:01:01 depot /kernel: Correcting length of data.p0: was 20970756, is 20970757 Sep 13 02:01:01 depot /kernel: vinum: removing 1 blocks of partial stripe at the end of home.p0 Sep 13 02:01:01 depot /kernel: vinum: home.p0 must have equal sized subdisks Sep 13 02:01:01 depot /kernel: Correcting length of home.p0: was 157008924, is 157008925 Sep 13 02:01:01 depot /kernel: vinum: removing 249 blocks of partial stripe at the end of data.p1 Sep 13 02:01:01 depot /kernel: vinum: data.p1 must have equal sized subdisks Sep 13 02:01:01 depot /kernel: Correcting length of data.p1: was 0, is 1 Sep 13 02:01:01 depot /kernel: vinum: data.p1 is faulty Sep 13 02:01:01 depot /kernel: vinum: removing 402 blocks of partial stripe at the end of home.p1 Sep 13 02:01:01 depot /kernel: vinum: home.p1 is faulty Sep 13 02:02:25 depot /kernel: vinum: unloaded Sep 13 02:02:33 depot /kernel: vinum: loaded Sep 13 02:02:33 depot /kernel: vinum: drive data1 is up Sep 13 02:02:33 depot /kernel: vinum: drive data2 is up Sep 13 02:02:33 depot /kernel: vinum: drive home1 is up Sep 13 02:02:33 depot /kernel: vinum: drive home2 is up Sep 13 02:02:33 depot /kernel: vinum: removing 998 blocks of partial stripe at the end of data.p0 Sep 13 02:02:33 depot /kernel: vinum: data.p0.s0 is up Sep 13 02:02:33 depot /kernel: vinum: data.p0.s1 is up Sep 13 02:02:33 depot /kernel: vinum: data.p0 is up Sep 13 02:02:33 depot /kernel: vinum: data is up Sep 13 02:02:33 depot /kernel: vinum: removing 403 blocks of partial stripe at the end of home.p0 Sep 13 02:02:33 depot /kernel: vinum: home.p0 must have equal sized subdisks Sep 13 02:02:33 depot /kernel: Correcting length of home.p0: was 157008924, is 157008925 Sep 13 02:02:33 depot /kernel: vinum: home.p0.s0 is up Sep 13 02:02:33 depot /kernel: vinum: home.p0.s1 is up Sep 13 02:02:33 depot /kernel: vinum: home.p0 is up Sep 13 02:02:33 depot /kernel: vinum: home is up Sep 13 02:13:19 depot /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Sep 13 02:13:19 depot /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Sep 13 02:13:19 depot /kernel: The Regents of the University of California. All rights reserved. Sep 13 02:13:19 depot /kernel: FreeBSD 4.4-RC #0: Wed Sep 12 12:46:00 IDT 2001 Sep 13 02:13:19 depot /kernel: Timecounter "i8254" frequency 1193182 Hz Sep 13 02:13:19 depot /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (602.19-MHz 686-class CPU) Sep 13 02:13:19 depot /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Sep 13 02:13:19 depot /kernel: Features=0x383f9ff Sep 13 02:13:19 depot /kernel: real memory = 536854528 (524272K bytes) Sep 13 02:13:19 depot /kernel: avail memory = 518512640 (506360K bytes) Sep 13 02:13:19 depot /kernel: Preloaded elf kernel "kernel" at 0xc02e5000. Sep 13 02:13:19 depot /kernel: Pentium Pro MTRR support enabled Sep 13 02:13:19 depot /kernel: md0: Malloc disk Sep 13 02:13:19 depot /kernel: Using $PIR table, 8 entries at 0xc00f0e60 Sep 13 02:13:19 depot /kernel: npx0: on motherboard Sep 13 02:13:19 depot /kernel: npx0: INT 16 interface Sep 13 02:13:19 depot /kernel: pcib0: on motherboard Sep 13 02:13:19 depot /kernel: pci0: on pcib0 Sep 13 02:13:19 depot /kernel: pcib2: at device 1.0 on pci0 Sep 13 02:13:19 depot /kernel: pci1: on pcib2 Sep 13 02:13:19 depot /kernel: isab0: at device 4.0 on pci0 Sep 13 02:13:19 depot /kernel: isa0: on isab0 Sep 13 02:13:19 depot /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Sep 13 02:13:19 depot /kernel: ata0: at 0x1f0 irq 14 on atapci0 Sep 13 02:13:19 depot /kernel: pci0: at 4.2 irq 10 Sep 13 02:13:19 depot /kernel: fxp0: port 0xd000-0xd03f mem 0xe2800000-0xe28fffff,0xe3000000-0xe3000fff irq 10 at device 9.0 on pci0 Sep 13 02:13:19 depot /kernel: fxp0: Ethernet address 00:d0:b7:af:14:da Sep 13 02:13:19 depot /kernel: inphy0: on miibus0 Sep 13 02:13:19 depot /kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Sep 13 02:13:19 depot /kernel: atapci1: port 0xa400-0xa4ff,0xa800-0xa803,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 irq 11 at device 11.0 on pci0 Sep 13 02:13:19 depot /kernel: ata2: at 0xb800 on atapci1 Sep 13 02:13:19 depot /kernel: ata3: at 0xb000 on atapci1 Sep 13 02:13:19 depot /kernel: pcib1: on motherboard Sep 13 02:13:19 depot /kernel: pci2: on pcib1 Sep 13 02:13:19 depot /kernel: orm0: