From owner-freebsd-hackers Sun Oct 22 4:42:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [203.2.75.105]) by hub.freebsd.org (Postfix) with ESMTP id 0F31E37B479 for ; Sun, 22 Oct 2000 04:42:41 -0700 (PDT) Received: from echidna.stu.cowan.edu.au (perax6-207.dialup.optusnet.com.au [198.142.92.207]) by mail02.syd.optusnet.com.au (8.9.3/8.9.3) with ESMTP id WAA04129 for ; Sun, 22 Oct 2000 22:41:34 +1100 Message-ID: <39F2D320.74A760FF@echidna.stu.cowan.edu.au> Date: Sun, 22 Oct 2000 19:44:32 +0800 From: Trent Nelson X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: Conflicting C/H/S values Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone explain to me why the following HDD BIOS Geometries don't represent the values proposed by the drives. What am I missing? (snippets from boot -v) BIOS Geometries: 0:030c7f3f 0..780=781 cylinders, 0..127=128 heads, 1..63=63 sectors 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 3:026dfe3f 0..621=622 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for These don't correlate to the C/H/S values proposed by the drives: ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad1: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad2: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad3: 4892MB (10018890 sectors), 10602 cyls, 15 heads, 63 S/T, 512 B/S I'm running 5.0 as of mid-September, but I don't think that's the issue as Windows tends to exhibit the same behaviour. Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 10:11:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 17E2437B683 for ; Sun, 22 Oct 2000 10:11:16 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id e9MHBDM09221; Sun, 22 Oct 2000 19:11:13 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id e9MGv0Z01239; Sun, 22 Oct 2000 18:57:01 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <006801c03c49$264e03a0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: , References: Subject: Re: can't build custom kernel Date: Sun, 22 Oct 2000 18:56:53 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First thing: read /usr/src/UPDATING. The proper procedure to > build a kernel is in there. To save you some time: > > cd /usr/src > make buildkernel KERNEL= > make installkernel KERNEL= > > If the build still fails, then yes, you have a legitimate problem. > At least when the normal (faster) config MYKERNEL;; cd ../../compile/MYKERNEL;make depend && make && make install fails. I also couldn't build a kernel the normal way, but the buildkernel cleaned something, so my preferred method worked again. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 11:14:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 9539737B4E5 for ; Sun, 22 Oct 2000 11:14:39 -0700 (PDT) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by kweetal.tue.nl (8.11.0/8.11.0) with ESMTP id e9MIEbt07511 for ; Sun, 22 Oct 2000 20:14:37 +0200 (MDT) Received: from deathstar (n140.dial.tue.nl [131.155.209.139]) by hermes.tue.nl (Postfix) with ESMTP id 6A1B22E802 for ; Sun, 22 Oct 2000 20:14:35 +0200 (CEST) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Sun, 22 Oct 2000 20:17:15 +0100 Subject: Free Pascal compiler version 1.0.2 beta for FreeBSD is officially out ! X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20001022181435.6A1B22E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, It is with great pleasure that the Free Pascal Development Team announces that Version 1.0.2 beta for FreeBSD 4.x + of the Free Pascal compiler has been officially released. This is a first beta version, commandline only, and not all packages are checked for FreeBSD compability. If you have FreeBSD available, try to test to compile your sources with FreeBSD, so we can lift this beta status soon. The Free Pascal Compiler/FreeBSD features: - A Turbo Pascal and Delphi compatible compiler for the Intel processor family, with some extensions to the Pascal and Object Pascal dialects, such as operator overloading. - An OS independent Run-Time Library, equivalent to the Turbo Pascal and Delphi Run-Time Libraries, not dependent on external libraries. - An API allowing for OS-Independent screen, keyboard and mouse management. (we need a lot of fixes and help here!) - Many units, interfacing to various API's: gtk, xforms, zlib, ncurses, sockets, X, mysql, postgresql, Interbase, paszlib, opengl, libgdb. - A Free Component Library, containing many base classes from the Delphi VCL. - More than 800 pages of documentation in Adobe PDF format, featuring + User's guide + Programmer's guide + Reference guide + reference guide for all units in the Run-Time Library + More than 440 complete example programs. (Other formats include plain text, HTML and PostScript) - Full sources to compiler, RTL, docs, packages. The distribution is available from ftp://ftp.freepascal.org in directory /pub/fpc/dist/freebsd-1.0.2 and below and from FTP mirrors. Marco, speaking for the whole Free Pascal Development Team Marco van de Voort (MarcoV@Stack.nl or marco@freepascal.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 12:14:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r29.bfm.org [216.127.220.125]) by hub.freebsd.org (Postfix) with ESMTP id C7C3437B479 for ; Sun, 22 Oct 2000 12:14:30 -0700 (PDT) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id OAA00279 for hackers@FreeBSD.org; Sun, 22 Oct 2000 14:13:22 -0500 (CDT) (envelope-from adam) Date: Sun, 22 Oct 2000 14:12:41 -0500 From: "G. Adam Stanislav" To: hackers@FreeBSD.org Subject: Dynamic memory allocation from non-C code Message-ID: <20001022141241.A263@whizkidtech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is probably a stupid question, but I have not been able to figure it out on my own: How do I dynamically allocate/free memory from programs that do not use the C library (e.g., assembly language programs)? I looked through syscalls.master but could not find anything resembling malloc in it. Is there a system call for this? Or do I have to just create a huge .data section and hope I made it large enough for all possible cases? Any help will be appreciated. Thanks, Adam -- A billion dollars in the bank, without the experience of carefreeness and charity, is a state of poverty. -- Deepak Chopra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 12:17:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8395737B4C5 for ; Sun, 22 Oct 2000 12:17:33 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9MJO8U07801; Sun, 22 Oct 2000 21:24:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "G. Adam Stanislav" Cc: hackers@FreeBSD.ORG Subject: Re: Dynamic memory allocation from non-C code In-Reply-To: Your message of "Sun, 22 Oct 2000 14:12:41 CDT." <20001022141241.A263@whizkidtech.net> Date: Sun, 22 Oct 2000 21:24:08 +0200 Message-ID: <7799.972242648@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001022141241.A263@whizkidtech.net>, "G. Adam Stanislav" writes: >This is probably a stupid question, but I have not been able to figure it >out on my own: > >How do I dynamically allocate/free memory from programs that do not use >the C library (e.g., assembly language programs)? If you don't link with the C library, you will need to use the sbrk(2)/brk(2) interface to extend your heap. -- 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 Sun Oct 22 12:50: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (rh22.bfm.org [216.127.220.215]) by hub.freebsd.org (Postfix) with ESMTP id B2E6537B479 for ; Sun, 22 Oct 2000 12:49:59 -0700 (PDT) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id OAA00257; Sun, 22 Oct 2000 14:46:03 -0500 (CDT) (envelope-from adam) Date: Sun, 22 Oct 2000 14:45:31 -0500 From: "G. Adam Stanislav" To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG Subject: Re: Dynamic memory allocation from non-C code Message-ID: <20001022144531.A240@whizkidtech.net> References: <20001022141241.A263@whizkidtech.net> <7799.972242648@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <7799.972242648@critter>; from phk@critter.freebsd.dk on Sun, Oct 22, 2000 at 09:24:08PM +0200 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 09:24:08PM +0200, Poul-Henning Kamp wrote: >>How do I dynamically allocate/free memory from programs that do not use >>the C library (e.g., assembly language programs)? > >If you don't link with the C library, you will need to use the >sbrk(2)/brk(2) interface to extend your heap. Thanks! Adam -- "Let's eat, drink, and be merry, for tomorrow we may diet" -- Seen on a dining room wall... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 14: 4:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 105ED37B479 for ; Sun, 22 Oct 2000 14:04:09 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA36321; Sun, 22 Oct 2000 23:04:04 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: James Housley Cc: FengYue , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux References: <39F238E5.309444B1@thehousleys.net> From: Dag-Erling Smorgrav Date: 22 Oct 2000 23:04:03 +0200 In-Reply-To: James Housley's message of "Sat, 21 Oct 2000 20:46:29 -0400" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Housley writes: > I believe a correct and true statement is "FreeBSD is a direct decendant > of Unix(TM). Based on the BSD sources" I don't think there's all that much left of the original BSD sources... at least not in the kernel. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 14:48:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 97CB437B4CF for ; Sun, 22 Oct 2000 14:48:26 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-143.nnj.dialup.bellatlantic.net [151.198.117.143]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA08628; Sun, 22 Oct 2000 17:48:14 -0400 (EDT) Message-ID: <39F3609E.83C02B3E@bellatlantic.net> Date: Sun, 22 Oct 2000 17:48:14 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Frederik Meerwaldt Cc: "phpStop.com" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frederik Meerwaldt wrote: > > Hi! > > > > > > > > We need this information in order to determine which of these two OS to > > > > choose from to drive our website. > > > > > > Choose FreeBSD. It's faster. > > > > Also if some things don't work or work strangely or are poorly > > documented, finding sources for them is MUCH easier in FreeBSD. Linux > > Huh?! What's strange in FreeBSD? Bugs do happen. Also things are sometimes changed faster than being documented. Some things are just too timey or obvious for being documented but matter when you are trying to find out why your seemingly right script does not work as intended. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 17:38:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 580BE37B479 for ; Sun, 22 Oct 2000 17:38:53 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-143.nnj.dialup.bellatlantic.net [151.198.117.143]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA10220; Sun, 22 Oct 2000 20:38:44 -0400 (EDT) Message-ID: <39F38893.6A8204A@bellatlantic.net> Date: Sun, 22 Oct 2000 20:38:43 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Frederik Meerwaldt , "phpStop.com" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux References: <39F3609E.83C02B3E@bellatlantic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: > > Frederik Meerwaldt wrote: > > > > Hi! > > > > > > > > > > > We need this information in order to determine which of these two OS to > > > > > choose from to drive our website. > > > > > > > > Choose FreeBSD. It's faster. > > > > > > Also if some things don't work or work strangely or are poorly > > > documented, finding sources for them is MUCH easier in FreeBSD. Linux > > > > Huh?! What's strange in FreeBSD? > > Bugs do happen. Also things are sometimes changed faster than > being documented. Some things are just too timey or obvious for > being documented but matter when you are trying to find out why > your seemingly right script does not work as intended. By the way, speaking of that, things in FreeBSD tend to be more synchronous with docs than in Linux. Also FreeBSD has much better backwards compatibility (though alas still not as good as commercial systems). In Linux the applications tend to break and require recompilation when the kernel is upgraded to the next second-digit version. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 18:12:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 1064937B479 for ; Sun, 22 Oct 2000 18:12:20 -0700 (PDT) Received: from phpStop.com (ras13-18.hfa.netvision.net.il [62.0.124.20]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id DAA15571; Mon, 23 Oct 2000 03:12:05 +0200 (IST) Message-ID: <39F3902A.6846BB49@phpStop.com> Date: Mon, 23 Oct 2000 03:11:06 +0200 From: "stop here. start everywhere." Organization: phpStop.com X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sergey Babkin Cc: Frederik Meerwaldt , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all again, Speaking of this subject again, I have read in the archives that FreeBSD has a method of building the whole source tree using the "make world" command. Although this is a nice feature, but isn't too much risky to upgrade the whole system in one shot? What if something breaks down after you've recompiled? Your system would be dead. In Linux, on the contrary, there's no such feature and you'll need to take the server anyways to upgrade it, which seems as a good way of doing things. In the meantime, another backup server can take its position. I guess in this fashion, Linux is better than FreeBSD... or did I miss something here? /John Sergey Babkin wrote: > > By the way, speaking of that, things in FreeBSD tend to be more > synchronous with docs than in Linux. Also FreeBSD has much better > backwards compatibility (though alas still not as good as commercial > systems). In Linux the applications tend to break and require > recompilation when the kernel is upgraded to the next > second-digit version. > > -SB -- Regards, phpStop.com http://www.phpstop.com/ stop here. start everywhere. mailto:info@phpstop.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 19:47:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 3501037B479 for ; Sun, 22 Oct 2000 19:47:08 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9N2kUA84359; Sun, 22 Oct 2000 19:46:30 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: "stop here. start everywhere." Cc: Sergey Babkin , Frederik Meerwaldt , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux In-Reply-To: Message from "stop here. start everywhere." of "Mon, 23 Oct 2000 03:11:06 +0200." <39F3902A.6846BB49@phpStop.com> Date: Sun, 22 Oct 2000 19:46:29 -0700 Message-ID: <84356.972269189@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of this subject again, I have read in the archives that FreeBSD > has a method of building the whole source tree using the "make world" > command. Although this is a nice feature, but isn't too much risky to > upgrade the whole system in one shot? Not anywhere near as "risky" as upgrading one component which n things depend on (without necessarily knowing this) and then having those n things start failing in mysterious and not-immediately-obvious ways. The make world target, on the other hand, knows the correct order to build things in so that interface or implementation changes are done in the correct order. > be dead. In Linux, on the contrary, there's no such feature and you'll Which is why things frequently break in not-immediately-obvious ways over there when people upgrade things piece-meal and in the incorrect order. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 19:56:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 1273A37B4FE for ; Sun, 22 Oct 2000 19:56:18 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.9.3/8.9.3) id TAA54218; Sun, 22 Oct 2000 19:57:30 -0700 (PDT) Date: Sun, 22 Oct 2000 19:57:30 -0700 From: Kris Kennaway To: "stop here. start everywhere." Cc: Sergey Babkin , Frederik Meerwaldt , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux Message-ID: <20001022195730.A54207@citusc17.usc.edu> References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> <39F3902A.6846BB49@phpStop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F3902A.6846BB49@phpStop.com>; from feedback@phpStop.com on Mon, Oct 23, 2000 at 03:11:06AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 23, 2000 at 03:11:06AM +0200, stop here. start everywhere. wrote: > Speaking of this subject again, I have read in the archives that FreeBSD > has a method of building the whole source tree using the "make world" > command. Although this is a nice feature, but isn't too much risky to > upgrade the whole system in one shot? Theres always an element of risk when upgrading systems, but having it done in a automatic, managed fashion which takes care of doing everything in the correct order, makes sure no steps are missed etc, is a lot safer than trying to do it manually, piecemeal, by hand and hoping you get it right and all of the resultant bits work together. > What if something breaks down after you've recompiled? Your system would > be dead. In Linux, on the contrary, there's no such feature and you'll > need to take the server anyways to upgrade it, which seems as a good way > of doing things. In the meantime, another backup server can take its > position. I guess in this fashion, Linux is better than FreeBSD... or > did I miss something here? You can do the backup server thing on FreeBSD too if you like - nothing to stop you. In fact it's always sensible to have a contingency plan when doing upgrades of critical production systems because despite our best efforts, things may sometimes (rarely, if you do it right) not go according to plan. My experience of upgrading Linux vs FreeBSD systems is that make world beats it hands down, at least compared to an RPM-based linux system. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 20:15:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 732E937B479 for ; Sun, 22 Oct 2000 20:15:50 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id e9N3Fju02357; Mon, 23 Oct 2000 05:15:45 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id e9N2d3Z03511; Mon, 23 Oct 2000 04:39:04 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <02af01c03c9a$75f08120$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "stop here. start everywhere." Cc: References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> <39F3902A.6846BB49@phpStop.com> Subject: Re: FreeBSD vs. Linux Date: Mon, 23 Oct 2000 04:36:31 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all again, > > Speaking of this subject again, I have read in the archives that FreeBSD > has a method of building the whole source tree using the "make world" > command. Although this is a nice feature, but isn't too much risky to > upgrade the whole system in one shot? > > What if something breaks down after you've recompiled? Your system would > be dead. In Linux, on the contrary, there's no such feature and you'll > need to take the server anyways to upgrade it, which seems as a good way > of doing things. In the meantime, another backup server can take its > position. I guess in this fashion, Linux is better than FreeBSD... or > did I miss something here? > The make world is done in two steps: first is everything compiled to /var/obj, then everything is installed. Per definition production servers run freebsd-stable, which by definition are never broken :-). By definition freebsd-current are not for production and are allowed to be broken. You could compile on a testserver; when you are satisfied it works, you can install other servers from that via nfs. I have updated servers while they were online without problems. An OS shouldn't limit you from taking the risc of shooting yourself in the foot if you feel you have a legitimate reason to do so. Leif > /John > > > Sergey Babkin wrote: > > > > By the way, speaking of that, things in FreeBSD tend to be more > > synchronous with docs than in Linux. Also FreeBSD has much better > > backwards compatibility (though alas still not as good as commercial > > systems). In Linux the applications tend to break and require > > recompilation when the kernel is upgraded to the next > > second-digit version. > > > > -SB > > -- > Regards, > > phpStop.com http://www.phpstop.com/ > stop here. start everywhere. mailto:info@phpstop.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 20:32:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id 8808537B479 for ; Sun, 22 Oct 2000 20:32:13 -0700 (PDT) Received: from beastie.localdomain ([24.19.158.41]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001023033158.EXXY28404.femail1.sdc1.sfba.home.com@beastie.localdomain>; Sun, 22 Oct 2000 20:31:58 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id UAA44965; Sun, 22 Oct 2000 20:34:31 -0700 (PDT) (envelope-from brian) Date: Sun, 22 Oct 2000 20:34:31 -0700 From: "Brian O'Shea" To: "stop here. start everywhere." Cc: Sergey Babkin , Frederik Meerwaldt , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux Message-ID: <20001022203431.T622@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: "stop here. start everywhere." , Sergey Babkin , Frederik Meerwaldt , freebsd-hackers@FreeBSD.ORG References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> <39F3902A.6846BB49@phpStop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <39F3902A.6846BB49@phpStop.com>; from stop here. start everywhere. on Mon, Oct 23, 2000 at 03:11:06AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 23, 2000 at 03:11:06AM +0200, stop here. start everywhere. wrote: > Hi all again, > > Speaking of this subject again, I have read in the archives that FreeBSD > has a method of building the whole source tree using the "make world" > command. Although this is a nice feature, but isn't too much risky to > upgrade the whole system in one shot? Actually, FreeBSD has broken it down into four steps now: make buildworld make buildkernel make installkernel make installworld It is crucial that you know what you are doing before you attempt this! It generally isn't necessary to build the world when you are running a release version of FreeBSD, and if you are just configuring a custom kernel (i.e. not upgrading it), then you should use the normal method of compiling a kernel (see the handbook section on this topic at http://www.freebsd.org/handbook/kernelconfig.html). The buildworld/ buildkernel/installkernel/installworld procedures are really for upgrading your system from sources, and if you are going to attempt to do this, you *must* read the UPDATING file in your source directory (typically in /usr/src) for special instructions that might be needed for the particular version transition that you will be making. You should also be subscribed to the mailing list that discusses the version to which you will be upgrading for a good week before you attempt the upgrade. > > What if something breaks down after you've recompiled? Your system would > be dead. In Linux, on the contrary, there's no such feature and you'll > need to take the server anyways to upgrade it, which seems as a good way > of doing things. In the meantime, another backup server can take its > position. I guess in this fashion, Linux is better than FreeBSD... or > did I miss something here? As with any upgrade (on Linux as well), you run the risk of running into any bugs that may exist in the new version. If the problem is with the kernel, you can back out by booting the old kernel. It's a good idea to keep around a copy of a known good kernel just for this reason. There are three branches of FreeBSD, the release branch, the stable branch, and the current branch. There are different reasons for running each, and as I mentioned before, there is a mailing list for stable and current, and you should be subscribed to it if you are going to be running anything other than release. Cheers, -brian > > /John > > > Sergey Babkin wrote: > > > > By the way, speaking of that, things in FreeBSD tend to be more > > synchronous with docs than in Linux. Also FreeBSD has much better > > backwards compatibility (though alas still not as good as commercial > > systems). In Linux the applications tend to break and require > > recompilation when the kernel is upgraded to the next > > second-digit version. > > > > -SB > > -- > Regards, > > phpStop.com http://www.phpstop.com/ > stop here. start everywhere. mailto:info@phpstop.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 21:11:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DB85837B479 for ; Sun, 22 Oct 2000 21:11:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9N4BAn79580; Sun, 22 Oct 2000 22:11:10 -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.9.3/8.8.3) with ESMTP id WAA04416; Sun, 22 Oct 2000 22:11:09 -0600 (MDT) Message-Id: <200010230411.WAA04416@harmony.village.org> To: David Miller Subject: Re: Boot off USB SanDisk? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 20 Oct 2000 13:14:14 EDT." References: Date: Sun, 22 Oct 2000 22:11:09 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message David Miller writes: : SanDisk makes a IDE-like flash card one could plug into a $30 USB : flashcard reader. : : Would FreeBSD have any idea how to boot off such a beast? Alternatively, : anyone know of an ISA/PCI adapter with enough bios on it to boot off a : similar flash? You can use a IDE <-> CF adapter to boot off this device. You can't boot it off via the USB device however. I've been booting FreeBSD off this beast since about 3.2R. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 21:13: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E345437B479 for ; Sun, 22 Oct 2000 21:13:02 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9N4D1n79588; Sun, 22 Oct 2000 22:13:01 -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.9.3/8.8.3) with ESMTP id WAA04436; Sun, 22 Oct 2000 22:13:01 -0600 (MDT) Message-Id: <200010230413.WAA04436@harmony.village.org> To: Ronald G Minnich Subject: Re: Boot off USB SanDisk? Cc: David Miller , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 20 Oct 2000 11:27:28 MDT." References: Date: Sun, 22 Oct 2000 22:13:01 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ronald G Minnich writes: : On Fri, 20 Oct 2000, Ronald G Minnich wrote: : : > I'm booting to single-user in 3 seconds using these things. The IDE delays : > are high, even for Flash IDE, so going for the socket is a good thing. : should have said: single user Linux. FreeBSD did not work, I think because With the right boot blocks, it works great. I've also used 3.4R with DOC2k disk on chips with the fla driver. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 21:15:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E778137B479 for ; Sun, 22 Oct 2000 21:15:47 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9N4Fkn79599; Sun, 22 Oct 2000 22:15: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.9.3/8.8.3) with ESMTP id WAA04462; Sun, 22 Oct 2000 22:15:46 -0600 (MDT) Message-Id: <200010230415.WAA04462@harmony.village.org> To: Len Conrad Subject: Re: can't build custom kernel Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Oct 2000 00:08:46 +0200." <5.0.0.25.0.20001022000602.00b072d0@mail.Go2France.com> References: <5.0.0.25.0.20001022000602.00b072d0@mail.Go2France.com> <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.com> Date: Sun, 22 Oct 2000 22:15:46 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.0.20001022000602.00b072d0@mail.Go2France.com> Len Conrad writes: : > First thing: read /usr/src/UPDATING. : : but I'm not UPDATING, I've installed to virgin disk from 4.1.1 iso-image. The problem is that you need to add the ISA compat shims: options COMPAT_OLDISA # compatability shims for lnc, le Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 21:22:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 56A5E37B479; Sun, 22 Oct 2000 21:22:32 -0700 (PDT) Received: from beastie.localdomain ([24.19.158.41]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001023042221.HMNL15466.femail2.sdc1.sfba.home.com@beastie.localdomain>; Sun, 22 Oct 2000 21:22:21 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id VAA45066; Sun, 22 Oct 2000 21:24:50 -0700 (PDT) (envelope-from brian) Date: Sun, 22 Oct 2000 21:24:50 -0700 From: "Brian O'Shea" To: Marko Ruban Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Routing issue with cable modem Message-ID: <20001022212450.U622@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Marko Ruban , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <39F0C896.30C53A1D@dppl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <39F0C896.30C53A1D@dppl.com>; from Marko Ruban on Fri, Oct 20, 2000 at 06:35:02PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 20, 2000 at 06:35:02PM -0400, Marko Ruban wrote: > Joel said HTML was badly formatted, so I'm resubmitting in plain text. > Thanks :) While the HTML in that message was particularly difficult for humans to parse, in genersl sending mail formatted in HTML is frowned upon since many of us (perhaps most of us) don't use mailers that can render HTML. Such messages are often ignored. Thanks for re-sending it as plain text. :) -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 22 21:25:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uranium.dashmail.net (uranium.dashmail.net [216.36.26.29]) by hub.freebsd.org (Postfix) with ESMTP id 7F10437B479 for ; Sun, 22 Oct 2000 21:25:55 -0700 (PDT) Received: from no1spec (rc1s7p8.dashmail.net [216.36.33.80]) by uranium.dashmail.net (8.10.1/8.10.1) with SMTP id e9N4ZrW36801 for ; Mon, 23 Oct 2000 04:35:53 GMT From: "Chris Ptacek" To: Subject: DMA in drivers? Date: Sun, 22 Oct 2000 21:26:11 -0700 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am in the process of writing a PCI driver for an encryption card. The specifications state that the DMA Destination Address, DMA Dest. Length, DMA Source Addr, and DMA Source Length should be loaded into registers in the card. Part of the info states: "This register is used to establish the PCI address for data moving from the the Host Computer Memory to the card. It consists of a 30 bit counter with the low-order 2 bits hardwired as zeros. The address stored may be any nonzero byte length that is a multiple of 8, since 8 bytes are required to make up a DES encryption block. The Source Address Register is continually updated during the transfer process and will always be pointing to the next unwritten location." What do I need to do to get a memory address for the source and destination data for the DMA transfers? It sounds as if these memory addresses must have the last three bits zeros, will this happen automatically? Right now I am stuck on how this DMA stuff is working and any help would be appreciated. Oh yeah, I am targeting this driver for a FreeBSD 3.x system. Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 3:35: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (unknown [212.85.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E3F637B479 for ; Mon, 23 Oct 2000 03:35:03 -0700 (PDT) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13neEh-0000YG-00; Mon, 23 Oct 2000 09:49:43 +0000 Date: Mon, 23 Oct 2000 09:49:43 +0000 From: Tony Finch To: Dag-Erling Smorgrav Cc: James Housley , FengYue , freebsd-hackers@FreeBSD.ORG, Tony Finch Subject: Re: FreeBSD vs. Linux Message-ID: <20001023094943.B375@hand.dotat.at> References: <39F238E5.309444B1@thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: >James Housley writes: >> I believe a correct and true statement is "FreeBSD is a direct decendant >> of Unix(TM). Based on the BSD sources" > >I don't think there's all that much left of the original BSD >sources... at least not in the kernel. Large bits of errno.h haven't changed since 1982 :-) Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 4:49: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EF07837B4C5 for ; Mon, 23 Oct 2000 04:49:04 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA09187; Mon, 23 Oct 2000 13:46:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010231146.NAA09187@freebsd.dk> Subject: Re: burncd utility for atapi burners In-Reply-To: <200010201635.JAA07149@usr06.primenet.com> from Terry Lambert at "Oct 20, 2000 04:35:35 pm" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 23 Oct 2000 13:46:44 +0200 (CEST) Cc: tomas@sdxnet.com (Tomas Hruz), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Terry Lambert wrote: > > I would like to communicate the proposed changes to the author but I did not > > find his address. Could somebody provide his email to me? > > [ ... ] > > This is going to be a problem in getting your changes accepted: > > > +/*- > > + * t.h. changes copyright (c) 2000 Tomas Hruz > > + * All rights reserved. > > + */ > > Since that includes the right to integrate and distribute. Yups, I'll look at it though, since burncd is my baby :) -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 Oct 23 5:35: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id DF13D37B4C5 for ; Mon, 23 Oct 2000 05:35:03 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id qsljaaaa for ; Mon, 23 Oct 2000 05:32:50 -0700 From: "Christopher Harrer" To: "Freebsd-Hackers" Subject: Cache Questions Date: Mon, 23 Oct 2000 08:33:04 -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.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, We're working on a driver for a PCI card, we're currently running into a problem that's symptomatic of a cache coherency problem. We have a area of memory that we manipulate and pass a physical address to our card. In other OS's (Linux, NT), before we manipulate this memory area, we mark the area as non-cachable. Are there similar operations/system calls we can use in FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory usage/attributes? Thanks very much! Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 6:24:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id CF60D37B4C5 for ; Mon, 23 Oct 2000 06:24:16 -0700 (PDT) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id PAA07547; Mon, 23 Oct 2000 15:26:22 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200010231326.PAA07547@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Christopher Harrer" Cc: "Freebsd-Hackers" Subject: Re: Cache Questions In-Reply-To: Your message of "Mon, 23 Oct 2000 08:33:04 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Oct 2000 15:26:22 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 23 Oct 2000 08:33:04 EDT, "Christopher Harrer" wrote: > Hello All, > > We're working on a driver for a PCI card, we're currently running into a > problem that's symptomatic of a cache coherency problem. We have a area of > memory that we manipulate and pass a physical address to our card. In other > OS's (Linux, NT), before we manipulate this memory area, we mark the area as > non-cachable. Are there similar operations/system calls we can use in > FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory > usage/attributes? See (in 4-Stabel and current) /usr/include/sys/memrange.h which has functions for setting memory regions uncachable. /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 9: 4:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winconx.com (ns1.winconx.net [63.114.199.2]) by hub.freebsd.org (Postfix) with SMTP id 397FE37B479 for ; Mon, 23 Oct 2000 09:04:28 -0700 (PDT) Received: (qmail 3050 invoked from network); 23 Oct 2000 16:04:22 -0000 Received: from home-isdn-pc6.winconx.net (HELO travis) (63.114.200.151) by ns1.winconx.net with SMTP; 23 Oct 2000 16:04:22 -0000 Message-ID: <002101c03d0a$abe14b50$97c8723f@winconx.com> From: "Travis Leuthauser" To: "stop here. start everywhere." Cc: References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> <39F3902A.6846BB49@phpStop.com> Subject: Re: FreeBSD vs. Linux Date: Mon, 23 Oct 2000 11:02:40 -0500 Organization: WinConX Online, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't used Linux for quite a while, I am however an avid supporter of FreeBSD. It is true that you can update your sources and rebuild everything in one shot. That may seem kinda risky, but I run several FreeBSD servers and have never had a problem remotely rebuilding/installing world without even dropping to single user mode. The upgrade process was very well planned, and in my experience, the chance of something major going wrong is no greater than trying to update one piece at a time. At least going all at once, you can be fairly certain that anything maintained on the FreeBSD cvs repository will work with the rest of your system. Travis Leuthauser Network Administrator WinConX Online, Inc. ----- Original Message ----- From: "stop here. start everywhere." To: "Sergey Babkin" Cc: "Frederik Meerwaldt" ; Sent: Sunday, October 22, 2000 8:11 PM Subject: Re: FreeBSD vs. Linux > Hi all again, > > Speaking of this subject again, I have read in the archives that FreeBSD > has a method of building the whole source tree using the "make world" > command. Although this is a nice feature, but isn't too much risky to > upgrade the whole system in one shot? > > What if something breaks down after you've recompiled? Your system would > be dead. In Linux, on the contrary, there's no such feature and you'll > need to take the server anyways to upgrade it, which seems as a good way > of doing things. In the meantime, another backup server can take its > position. I guess in this fashion, Linux is better than FreeBSD... or > did I miss something here? > > /John > > > Sergey Babkin wrote: > > > > By the way, speaking of that, things in FreeBSD tend to be more > > synchronous with docs than in Linux. Also FreeBSD has much better > > backwards compatibility (though alas still not as good as commercial > > systems). In Linux the applications tend to break and require > > recompilation when the kernel is upgraded to the next > > second-digit version. > > > > -SB > > -- > Regards, > > phpStop.com http://www.phpstop.com/ > stop here. start everywhere. mailto:info@phpstop.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 9:27:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 1587937B4C5; Mon, 23 Oct 2000 09:27:20 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Mon, 23 Oct 2000 12:27:19 -0400 Message-ID: <39F46748.8E433F14@tellurian.com> Date: Mon, 23 Oct 2000 12:28:56 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: FreeBSD questions Cc: FreeBSD hackers Subject: Re: Routing issue with cable modem References: <39F0C896.30C53A1D@dppl.com> <20001023062704.A23746@firedrake.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Oct 20, 2000 at 06:35:02PM -0400, Marko Ruban wrote: > > Joel said HTML was badly formatted, so I'm resubmitting in plain text. > > Thanks :) > > That's progress ... but if you would wrap your lines around 70-74 > columns, it would be even better. Thank you. I wish I'd get as much help, as I got "improper message formatting" responses :) P.S. No column counter in Netscape email composer :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 9:52:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 1286337B479; Mon, 23 Oct 2000 09:52:32 -0700 (PDT) Received: from owp.csus.edu (qbqjyl@[130.86.77.19]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id JAA19061; Mon, 23 Oct 2000 09:50:38 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <39F46B08.808132D2@owp.csus.edu> Date: Mon, 23 Oct 2000 09:44:56 -0700 From: Joseph Scott X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Boris Popov Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When is this going to be brought into -current? Boris Popov wrote: > > Hello, > > At first, I'm want to say 'thank you' for everybody who provided > me with feedback on my work. So, here is a records from the HISTORY file > for last two releases: > > 20.10.2000 1.3.0 > - Network IO engine significantly reworked. Now it uses kernel threads > to implement 'smbiod' process which handles network traffic for each VC. > Previous model were incapable to serve large number of mount points and > didn't work well with intensive IO operations performed on a different > files on the same mount point. Special care was taken on better > usage of MP systems. > Unfortunately, kernel threads aren't supported by FreeBSD 3.X and for > now it is excluded from the list of supported systems. > - Reduce overhead caused by using single hash table for each mount point. > > 26.09.2000 1.2.8 (never released) > - More SMP related bugs are fixed. > - Make smbfs compatible with the Linux emulator. > - smbfs now known to work with IBM LanManager (special thanks to > Eugen Averin) > - Fix problem with files bigger than 2GB (reported by Lee McKenna) > - Please note that smbfs may not work properly with FreeBSD 3.X. > > New version can be downloaded from: > ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz > > -- > Boris Popov > http://www.butya.kz/~bp/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Joseph Scott joseph.scott@owp.csus.edu The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 10: 6:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 558C337B479 for ; Mon, 23 Oct 2000 10:06:17 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id NAA06399; Mon, 23 Oct 2000 13:01:30 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001023130049.02985eb0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 23 Oct 2000 13:06:16 -0400 To: Sergey Babkin , Frederik Meerwaldt From: Dennis Subject: Re: FreeBSD vs. Linux Cc: "phpStop.com" , freebsd-hackers@FreeBSD.ORG In-Reply-To: <39F209DF.88368125@bellatlantic.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:25 PM 10/21/2000, Sergey Babkin wrote: >Frederik Meerwaldt wrote: > > > > > We need this information in order to determine which of these two OS to > > > choose from to drive our website. > > > > Choose FreeBSD. It's faster. > >Also if some things don't work or work strangely or are poorly >documented, finding sources for them is MUCH easier in FreeBSD. Linux >is a patchwork of independent packages, and tracking down what came >from where and was patched by what is usually not easy. Also commercial >distributions of Linux sometimes tend to "lose" parts of sources, >so that you will not always be able to re-compile the stuff at all. >There's been a short period when I worked on building a Linux >distribution and that was a quite special experience. What he's trying to say is that the linux kernel is an abortion. They keep redesigning it and its continuously unstable. Many of the kernel "features" are experimental and large chunks of it simply dont work. Then, IF you can get everything you need working, virtually all of the ethernet drivers lock up under load. There is no static buffer pool so the memory system will fail under heavy network load. So-called "local" panics can disable the network sub-system without a reboot making it unusable in unattended environments.... Need I go on? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 10:15:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id A210437B479 for ; Mon, 23 Oct 2000 10:15:35 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13nlC9-000GZX-00; Mon, 23 Oct 2000 17:15:34 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e9NHIKf01016; Mon, 23 Oct 2000 19:18:20 +0200 (CEST) (envelope-from wkb) Date: Mon, 23 Oct 2000 19:18:20 +0200 From: Wilko Bulte To: Warner Losh Cc: David Miller , freebsd-hackers@freebsd.org Subject: Re: Boot off USB SanDisk? Message-ID: <20001023191820.B394@freebie.demon.nl> References: <200010230411.WAA04416@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010230411.WAA04416@harmony.village.org>; from imp@village.org on Sun, Oct 22, 2000 at 10:11:09PM -0600 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 10:11:09PM -0600, Warner Losh wrote: > In message David Miller writes: > : SanDisk makes a IDE-like flash card one could plug into a $30 USB > : flashcard reader. > : > : Would FreeBSD have any idea how to boot off such a beast? Alternatively, > : anyone know of an ISA/PCI adapter with enough bios on it to boot off a > : similar flash? > > You can use a IDE <-> CF adapter to boot off this device. You can't > boot it off via the USB device however. As a matter of curiosity: what does such an adapter cost (roughly) ? -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 10:15:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id EF36737B479 for ; Mon, 23 Oct 2000 10:15:47 -0700 (PDT) Received: (qmail 30439 invoked by uid 0); 23 Oct 2000 17:15:44 -0000 Received: from unknown (HELO blade) (212.118.36.37) by mail.gmx.net with SMTP; 23 Oct 2000 17:15:44 -0000 From: "d_f0rce" To: Subject: Understanding what happens on open() within the kernel Date: Mon, 23 Oct 2000 19:18:15 +0200 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i'm currently working on understanding the FreeBSD kernel. Therefore I read the book "The design and implementation of the 4.4BSD OS". As I know that most of the things described in this book are probably no longer up to date, I think that the basics should be the same. As I would like to experiment a bit with the serial port I have a question conerning the open() call. Perhabs you could tell me if I understood the open-procedure correctly: On opening i.e. /dev/cuaa0 the kernel sees that this is a tty device. It then calls ttyopen(). Ttyopen() knows which driver is responsible by analyzing the minor device number. It calls the real open() function from the driver responsible for that device and then fills in the tty structure. Now you can change settings by using ioctl() or the termios functions. What would I have to do to get the filled in tty_structure directly, without using ioctl to get the settings of a tty? Or is there perhabs an ioctl() call to get the tty_structure? Greetings, Alex PS: Please answer directly to me as I'm not on the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 10:32:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by hub.freebsd.org (Postfix) with ESMTP id B72D137B479 for ; Mon, 23 Oct 2000 10:32:47 -0700 (PDT) Received: from fondue.ICSI.Berkeley.EDU (fondue.ICSI.Berkeley.EDU [192.150.186.19]) by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id KAA09775; Mon, 23 Oct 2000 10:32:44 -0700 (PDT) Received: from localhost (rizzo@localhost) by fondue.ICSI.Berkeley.EDU (8.8.2/1.8) with ESMTP id KAA07639; Mon, 23 Oct 2000 10:32:44 -0700 (PDT) X-Authentication-Warning: fondue.ICSI.Berkeley.EDU: rizzo owned process doing -bs Date: Mon, 23 Oct 2000 10:32:43 -0700 (PDT) From: Luigi Rizzo To: Wilko Bulte Cc: Warner Losh , David Miller , freebsd-hackers@FreeBSD.ORG Subject: Re: Boot off USB SanDisk? In-Reply-To: <20001023191820.B394@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You can use a IDE <-> CF adapter to boot off this device. You can't > > boot it off via the USB device however. > > As a matter of curiosity: what does such an adapter cost (roughly) ? i bought one from TAPR (www.tapr.org i think) for some 59US$ but it is really just a connector and a PCB so i suppose it is just a matter of volumes to get a better price cheers luigi > -- > Wilko Bulte Arnhem, the Netherlands > wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl > > > > 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 Oct 23 11: 3:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7EFC337B4CF for ; Mon, 23 Oct 2000 11:03:19 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9NI3En82517; Mon, 23 Oct 2000 12:03:14 -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.9.3/8.8.3) with ESMTP id MAA09059; Mon, 23 Oct 2000 12:03:13 -0600 (MDT) Message-Id: <200010231803.MAA09059@harmony.village.org> To: Luigi Rizzo Subject: Re: Boot off USB SanDisk? Cc: Wilko Bulte , David Miller , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 23 Oct 2000 10:32:43 PDT." References: Date: Mon, 23 Oct 2000 12:03:13 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Luigi Rizzo writes: : > > You can use a IDE <-> CF adapter to boot off this device. You can't : > > boot it off via the USB device however. : > : > As a matter of curiosity: what does such an adapter cost (roughly) ? : : i bought one from TAPR (www.tapr.org i think) for some 59US$ : but it is really just a connector and a PCB so i suppose it is : just a matter of volumes to get a better price I've seen them in the $20-$50 range myself. If you are making 100s of these things, they cost in the ballpark of $20 each to make if you have the right infrastructure. The $20 ones are from one of the embedded PC houses. The ones we make for our own internal use have special mounting requirements that the commercially available ones did not fullfil. The board is dead simple. Two connectors, a pc board, some traces and a bypass cap (optional: M/S jumper and a led activity light). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 13: 5: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 991F337B4CF for ; Mon, 23 Oct 2000 13:05:00 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9NK7Ih04538; Mon, 23 Oct 2000 13:07:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010232007.e9NK7Ih04538@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Christopher Harrer" Cc: "Freebsd-Hackers" Subject: Re: Cache Questions In-reply-to: Your message of "Mon, 23 Oct 2000 08:33:04 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Oct 2000 13:07:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello All, > > We're working on a driver for a PCI card, we're currently running into a > problem that's symptomatic of a cache coherency problem. We have a area of > memory that we manipulate and pass a physical address to our card. In other > OS's (Linux, NT), before we manipulate this memory area, we mark the area as > non-cachable. Are there similar operations/system calls we can use in > FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory > usage/attributes? Take a look at , and particularly mem_range_attr_set(). *However*, since the PC architecture is strongly cache coherent, you probably have a problem with the design or implementation of your driver:adapter protocol. Marking an entire region of memory as uncacheable is *very* inefficient; there are much better ways of maintaining synchronisation without doing this. -- ... 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 Mon Oct 23 13:28:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 54D3A37B479; Mon, 23 Oct 2000 13:28:33 -0700 (PDT) Received: from dppl.com (unverified [216.182.27.75]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Mon, 23 Oct 2000 16:28:34 -0400 Message-ID: <39F49ECC.AF8CDFD2@dppl.com> Date: Mon, 23 Oct 2000 16:25:48 -0400 From: Marko Ruban X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: gateway on different subnet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Summary of the problem: Can't assign cable modem gateway (10.17.56.12) to interface ed0 with assigned IP (208.59.162.242) - "network unreachable". I called RCN (my cable provider) and asked them to give me a gateway on the same subnet; they said they "don't do that". Part of solution: I set an alias for ed0 to 10.17.0.1 and it accepted the cable modem gateway as is. BUT, the packets are sent out with source address (10.17.0.1) responses to which, I suspect, gateway doesn't know how to route. Question: how can I have an alias of 10.17.0.1 and send out all packets with source address set to 208.59.162.242 (the IP that is actually assigned to the interface - not alias). Thanks for any help you can give. Marko P.S. Alternately, how can I force the system to allow a gateway that is on a different subnet (like windows allows that). Who can I turn to for help ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 13:31:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 4F13737B4CF; Mon, 23 Oct 2000 13:31:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9NKZ1h04685; Mon, 23 Oct 2000 13:35:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010232035.e9NKZ1h04685@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Marko Ruban Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: gateway on different subnet In-reply-to: Your message of "Mon, 23 Oct 2000 16:25:48 EDT." <39F49ECC.AF8CDFD2@dppl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Oct 2000 13:35:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Summary of the problem: > > Can't assign cable modem gateway (10.17.56.12) to interface > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > I called RCN (my cable provider) and asked them to give me > a gateway on the same subnet; they said they "don't do that". Your gateway *must* be on a reachable subnet. That's all there is to 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 Mon Oct 23 14: 9:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hookie.cs.ndsu.NoDak.edu (hookie.cs.ndsu.NoDak.edu [134.129.125.253]) by hub.freebsd.org (Postfix) with ESMTP id 8B22C37B479 for ; Mon, 23 Oct 2000 14:09:10 -0700 (PDT) Received: (from tinguely@localhost) by hookie.cs.ndsu.NoDak.edu (8.9.3/8.9.3) id MAA50727; Mon, 23 Oct 2000 12:19:48 -0500 (CDT) (envelope-from tinguely) Date: Mon, 23 Oct 2000 12:19:48 -0500 (CDT) From: mark tinguely Message-Id: <200010231719.MAA50727@hookie.cs.ndsu.NoDak.edu> To: freebsd-hackers@FreeBSD.ORG, ptacek@technologist.com Subject: Re: DMA in drivers? In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "This register is used to establish the PCI address for data moving from the > the Host Computer Memory to the card. It consists of a 30 bit counter with > the low-order 2 bits hardwired as zeros. The address stored may be any > nonzero byte length that is a multiple of 8, since 8 bytes are required to > make up a DES encryption block. The Source Address Register is continually > updated during the transfer process and will always be pointing to the next > unwritten location." > > What do I need to do to get a memory address for the source and destination > data for the DMA transfers? It sounds as if these memory addresses must have > the last three bits zeros, will this happen automatically? Right now I am > stuck on how this DMA stuff is working and any help would be appreciated. > Oh yeah, I am targeting this driver for a FreeBSD 3.x system. sounds to be that it wants the buffers to be long-word aligned (multiple of 4 bytes) and not greater than 1 GB (address & 0x3ffffffc). the source data must be null padded so that the length is a multiple of 8 bytes. other gotchas, the addresses you specified must be the PHYSICAL address, not the kernel virtual address. use the vtophys(mtr->bigbuf) routine to get the physical address. The physical page should be wired down, so it does not get paged out to swap between the time you set up the DMA and the DMA finish. be sure the data does not cross into another physical page unless the two pages are contiguous. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 14:11:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id E8BA937B4E5; Mon, 23 Oct 2000 14:11:36 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Mon, 23 Oct 2000 15:11:36 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma011364; Mon, 23 Oct 00 15:11:08 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id PAA18526; Mon, 23 Oct 2000 15:11:05 -0600 (MDT) Date: Mon, 23 Oct 2000 15:27:18 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Marko Ruban Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <39F49ECC.AF8CDFD2@dppl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm -- how about using proxy-arp style routing? If their router has has proxy-arp support turned on, then you can set yourself (ie your own IP) as the default and will arp for _all_ addreeses of _all_ remote boxes you try to connect to. Then their router sends a response to the arp-request and your box gets an apr table entry of the router (within the local ethernet-broacast realm) and will send stuff for whatever remote IP address you have. It's not the cleanest solution, but I've used it under windows, linux and hpux to get around the foolishness of a network architecture I couldn't change... I used this at an old job where I had non-contiguous IP networks in the same ethernet-broacast domain so that all the machines would find each other on the local network, and the router handled all the off-segment connections via proxy-arp. I have NOT tried this under FreeBSD as I thankfully dont work there any more (was converted to the FreeBSD religion after I left...). Alternatively, you could use an exceptionally permissive netmask so that the local box _thought_ the other IP was in the same 'network' as yours. Pretty much both achieve the same effect of putting the remote router on the 'same network' as you. Good luck. Fred > > Can't assign cable modem gateway (10.17.56.12) to interface > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > I called RCN (my cable provider) and asked them to give me > a gateway on the same subnet; they said they "don't do that". ... > P.S. Alternately, how can I force the system to allow a gateway > that is on a different subnet (like windows allows that). Who > can I turn to for help ? -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 14:15:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id ACFD437B4C5; Mon, 23 Oct 2000 14:15:38 -0700 (PDT) Received: from dppl.com (unverified [216.182.27.75]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Mon, 23 Oct 2000 17:12:44 -0400 Message-ID: <39F4A923.BA5FD933@dppl.com> Date: Mon, 23 Oct 2000 17:09:55 -0400 From: Marko Ruban X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: gateway on different subnet References: <200010232035.e9NKZ1h04685@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Summary of the problem: > > > > Can't assign cable modem gateway (10.17.56.12) to interface > > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > > > I called RCN (my cable provider) and asked them to give me > > a gateway on the same subnet; they said they "don't do that". > > Your gateway *must* be on a reachable subnet. That's all there is to it. > If so, why doesn't windows have any problem with gateway being on a different subnet ? How do I make it reachable ? > -- > ... 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-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 Mon Oct 23 15:15:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.safety.net (ns3.safety.net [216.200.162.38]) by hub.freebsd.org (Postfix) with ESMTP id CE30337B4C5; Mon, 23 Oct 2000 15:14:57 -0700 (PDT) Received: (from les@localhost) by ns3.safety.net (8.9.3/8.9.3) id PAA14556; Mon, 23 Oct 2000 15:14:54 -0700 (MST) (envelope-from les) From: Les Biffle Message-Id: <200010232214.PAA14556@ns3.safety.net> Subject: Re: gateway on different subnet In-Reply-To: from Fred Clift at "Oct 23, 2000 03:27:18 pm" To: fclift@verio.net (Fred Clift) Date: Mon, 23 Oct 2000 15:14:54 -0700 (MST) Cc: marko@dppl.com (Marko Ruban), freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: les@safety.net 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 X-Loop: FreeBSD.ORG > Hm -- how about using proxy-arp style routing? Here's what I've done in the past: 1. Have a friend out in the net ping your address 208.59.162.242 2. Run tcpdump and look for someone ARPing for you. That someone will very likely be your default gateway as seen from your site. If that router is in your subnet, set your default to it and you're done. If not, continue at the next step. 3. Pick an IP Address in your cable subnet that feels like a really good router address to you. Make something up. 208.59.162.1 perhaps? 4. Use "arp -s 208.59.162.1 xx:xx:xx:xx:xx:xx" to install an arp entry in your route table for this made-up address. That will keep you from ARPing for 208.59.162.1 and discovering the device that really owns that address. 5. Set your default gateway to 208.59.162.1. Good luck, -Les -- Les Biffle Community Service... Just Say NO! (480) 778-0177 les@safety.net http://www.networksafety.com/ Network Safety, 7802 E Gray Rd Ste 500, Scottsdale, AZ 85260 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 16: 3:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 6B33337B4C5 for ; Mon, 23 Oct 2000 16:03:27 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9NN73h05149; Mon, 23 Oct 2000 16:07:09 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010232307.e9NN73h05149@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Chris Ptacek" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DMA in drivers? In-reply-to: Your message of "Sun, 22 Oct 2000 21:26:11 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Oct 2000 16:07:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am in the process of writing a PCI driver for an encryption card. The > specifications state that the DMA Destination Address, DMA Dest. Length, DMA > Source Addr, and DMA Source Length should be loaded into registers in the > card. Part of the info states: > > "This register is used to establish the PCI address for data moving from the > the Host Computer Memory to the card. It consists of a 30 bit counter with > the low-order 2 bits hardwired as zeros. The address stored may be any > nonzero byte length that is a multiple of 8, since 8 bytes are required to > make up a DES encryption block. The Source Address Register is continually > updated during the transfer process and will always be pointing to the next > unwritten location." > > What do I need to do to get a memory address for the source and destination > data for the DMA transfers? It sounds as if these memory addresses must have > the last three bits zeros, will this happen automatically? Right now I am > stuck on how this DMA stuff is working and any help would be appreciated. > Oh yeah, I am targeting this driver for a FreeBSD 3.x system. 3.x is obsolete, and should typically not be considered for new drivers unless you're doing something specifically to spec. Having said that, the busdma infrastructure in 3.x probably works well enough to do what you want. The actual process to follow is going to depend largely on how your exported interface to the driver works. The card sounds like it's pretty stupid (eg. no scatter/gather DMA, no descriptor ring, etc). so you really have two options: - manual scatter/gather - copy to/from a conforming DMA-able buffer. The choice between these two depends on the nature of the data; if your chunks of contiguous data are relatively large, then manual scatter/ gather will be more efficient. OTOH, if the chunks are small, then it will be more efficient to gather the stream into a single buffer and pass that to the adapter instead. In either case, you will want to look to the busdma code. At the very least, you will need to construct a DMA tag which decsribes the card's DMA capabilities and a DMA map for the transaction in progress. For manual scatter/gather, you then pass the input segment to bus_dmamap_load and use the helper function to build a list of physical segment addresses and lengths. Then you feed each of these segments to the adapter, and call bus_dmamap_unload when you're done. To allocate a conforming DMA-able buffer, use bus_dmamem_alloc and then pass it to bus_dmamap_load in order to obtain the base address of the buffer (note that if you've set the tag up properly, the buffer will be physically contiguous). -- ... 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 Mon Oct 23 16: 9: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 4EBBF37B479 for ; Mon, 23 Oct 2000 16:09:05 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9NNCbh05191; Mon, 23 Oct 2000 16:12:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010232312.e9NNCbh05191@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ronald G Minnich Cc: David Miller , freebsd-hackers@FreeBSD.ORG Subject: Re: Boot off USB SanDisk? In-reply-to: Your message of "Fri, 20 Oct 2000 11:27:28 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Oct 2000 16:12:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm booting to single-user in 3 seconds using these things. The IDE delays > > are high, even for Flash IDE, so going for the socket is a good thing. > > should have said: single user Linux. FreeBSD did not work, I think because > the bootup stuff in the kernel wants to as the BIOS "a few questions", and > there's not bios there. If anyone wants to work on a non-bios-querying > boot-time parameter interface for freebsd (like the one linux has) let me > know. I would really like to boot freebsd out of flash. Most of the infrastructure is already there. The kernel expects to be able to use the SMAP interface to obtain a map of physical memory segments; you will need to rewrite i386/i386/machdep.c:getmemsize() to use whatever interface your firmware provides for locating usable physical memory. Likewise, you'll need to turn off the probing that goes on in i386/i386/bios.c. -- ... 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 Mon Oct 23 16:24:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 899DC37B479; Mon, 23 Oct 2000 16:24:22 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id RAA09295; Mon, 23 Oct 2000 17:23:28 -0600 (MDT) Date: Mon, 23 Oct 2000 17:23:28 -0600 (MDT) From: Nick Rogness To: les@safety.net Cc: Fred Clift , Marko Ruban , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <200010232214.PAA14556@ns3.safety.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Les Biffle wrote: > > Hm -- how about using proxy-arp style routing? > > Here's what I've done in the past: > > 1. Have a friend out in the net ping your address 208.59.162.242 > > 2. Run tcpdump and look for someone ARPing for you. That someone > will very likely be your default gateway as seen from your site. > If that router is in your subnet, set your default to it and you're > done. If not, continue at the next step. > > 3. Pick an IP Address in your cable subnet that feels like a really > good router address to you. Make something up. 208.59.162.1 perhaps? > > 4. Use "arp -s 208.59.162.1 xx:xx:xx:xx:xx:xx" to install an arp > entry in your route table for this made-up address. That will keep > you from ARPing for 208.59.162.1 and discovering the device that > really owns that address. > > 5. Set your default gateway to 208.59.162.1. If that doesn't work (it should), you could also look into the ipfw fwd option. I would like to know when you get it to work... Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 17:34:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tahiti.cc.odu.edu (tahiti.server1.odu.edu [128.82.224.6]) by hub.freebsd.org (Postfix) with ESMTP id 4D0D337B479; Mon, 23 Oct 2000 17:34:41 -0700 (PDT) Received: from [10.3.2.31] (sd11-174.sd.odu.edu [128.82.11.174]) by tahiti.cc.odu.edu (8.9.3/8.9.3) with ESMTP id UAA21693; Mon, 23 Oct 2000 20:34:38 -0400 (EDT) Date: Mon, 23 Oct 2000 20:42:17 +0000 (GMT) From: Kherry Zamore X-Sender: dknj@jubilee.sd.odu.edu To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: gateway on different subnet In-Reply-To: <200010232035.e9NKZ1h04685@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Mike Smith wrote: > > Summary of the problem: > > > > Can't assign cable modem gateway (10.17.56.12) to interface > > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > > > I called RCN (my cable provider) and asked them to give me > > a gateway on the same subnet; they said they "don't do that". > > Your gateway *must* be on a reachable subnet. That's all there is to it. > RCN has recently pulled a crack smoking move and made the gateways 10.x ip addresses on their cable modems. It caught me by surprise since I had just put up a new box and it refused to get on the internet. Anywho, the easiest way to fix it is to alias 10.254.254.1 (or some other bogus ip) to your public interface with a netmask of 0xff000000 and then set your default gateway as normal. % ifconfig ed0 ed0: flags=8843 mtu 1500 inet 216.164.35.237 netmask 0xffffff00 broadcast 216.164.35.255 inet 10.254.254.1 netmask 0xff000000 broadcast 10.255.255.255 ether 00:50:4e:00:cc:ff When I get home I'm probably going to switch to DSL, my sanity is worth more than low cost bandwidth. -= Kherry Zamore -=- (757) 683-7386 =- -= Resident Computer and Network geek/god =- -= Rogers Hall Main Room 324 -=- www.dknj.org =- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 17:36:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 88FE037B4C5 for ; Mon, 23 Oct 2000 17:36:39 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id BAA06658 for hackers@freebsd.org; Tue, 24 Oct 2000 01:36:34 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id BAA45816 for ; Tue, 24 Oct 2000 01:21:38 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Oct 2000 01:21:36 +0100 To: hackers@freebsd.org From: Bob Bishop Subject: How to install BootEasy? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Apologies for this, I'm sure I've seen the answer recently but I'm *&^%ed if I can find it in the archives[1]. I have an installed FreeBSD hard disk that I want to use as the second drive on a machine with other stuff on the first drive. How do I install BootEasy on the first drive? TIA [1] Sort by date on the archive search would be a worthwhile improvement. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 23 19: 5:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lambdatel.com (lambda.lambdatel.com [192.83.199.1]) by hub.freebsd.org (Postfix) with ESMTP id CFC9237B479 for ; Mon, 23 Oct 2000 19:05:54 -0700 (PDT) Received: from jim (helo=localhost) by lambdatel.com with local-smtp (Exim 2.11 #1) id 13ntUX-0004Z3-00 for hackers@freebsd.org; Mon, 23 Oct 2000 19:07:05 -0700 Date: Mon, 23 Oct 2000 19:07:04 -0700 (PDT) From: Jim Dixon To: hackers@freebsd.org Subject: Device Number Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As it says in the 'majors.i386' file, I guess Im supposed to send a request to this email address asking for the assignment of a Device number. Okay, I'm requesting the assignment of a character device number. Please take a look at the preliminary project documentation at: http://www.bsdtelephony.com.mx/prelim.html This will be for the 'tor' driver (the "Tormenta" telephony card). Also, if interested, please check out the current project status at: http://www.bsdtelephony.com.mx/status.html Also, how do I go about submitting this stuff (once fully complete, tested and stuff) to be included in releases??? Jim Dixon Duuuude jim@lambdatel.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 0:21:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.mobilix.dk (unknown [194.234.53.85]) by hub.freebsd.org (Postfix) with ESMTP id 75C2A37B479 for ; Tue, 24 Oct 2000 00:21:34 -0700 (PDT) Received: from lflat.vas.mobilix.dk (gw-vas.mobilix.net [212.97.206.4]) by mail.mobilix.dk (8.8.7/8.8.7) with ESMTP id KAA20674 for ; Tue, 24 Oct 2000 10:00:07 +0200 Received: by lflat.vas.mobilix.dk (Postfix, from userid 72044) id F35E0A89D; Tue, 24 Oct 2000 09:21:01 +0200 (CEST) Date: Tue, 24 Oct 2000 09:21:01 +0200 From: Vadim Belman To: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS/VM deadlock report and help request Message-ID: <20001024092101.A88854@lflat.vas.mobilix.dk> Mail-Followup-To: Vadim Belman , freebsd-hackers@FreeBSD.ORG References: <20001020145043.B73760@lflat.vas.mobilix.dk> <20001020171810.A28345@walton.maths.tcd.ie> <200010201624.e9KGO3B08039@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010201624.e9KGO3B08039@earth.backplane.com>; from dillon@earth.backplane.com on Fri, Oct 20, 2000 at 09:24:03AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 20, 2000 at 09:24:03AM -0700, Matt Dillon wrote: > :> The kernel config I supply as an attachment. Kernel-mode stack > :> trace for the thttpd process looks like this: > : > :I think we've seen a similar problem and have a work around for it. > :You could try the following patch, though it might take more fiddling > :to get it right. > : > :(The patch is by Ian Dowse, Matt Dillon had a quick look at it and said > :it looked OK, we've been testing it for a bit here). > : > : David. > > Ah yes, that problem... if Ian's patch solves the problem for Vadim, I > think you should go ahead and commit it. After a day of testing I confirm that the patch does work. -- /Voland Vadim Belman E-mail: voland@lflat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 0:28:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c3-dbn-83.dial-up.net (c3-dbn-83.dial-up.net [196.33.200.83]) by hub.freebsd.org (Postfix) with ESMTP id 5BBF337B4C5 for ; Tue, 24 Oct 2000 00:28:11 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id JAA14543; Tue, 24 Oct 2000 09:26:08 +0200 (SAST) From: Robert Nordier Message-Id: <200010240726.JAA14543@siri.nordier.com> Subject: Re: How to install BootEasy? To: rb@gid.co.uk (Bob Bishop) Date: Tue, 24 Oct 2000 09:26:08 +0200 (SAST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Bob Bishop" at Oct 24, 2000 01:21:36 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Bishop wrote: > Apologies for this, I'm sure I've seen the answer recently but I'm *&^%ed > if I can find it in the archives[1]. I have an installed FreeBSD hard disk > that I want to use as the second drive on a machine with other stuff on the > first drive. How do I install BootEasy on the first drive? TIA We don't use BootEasy any longer, but something called boot0 ... which is probably why you couldn't find anything in the archives. Something like boot0cfg -Bv $DRIVE should work, though see the man page. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 0:39:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 4232F37B479 for ; Tue, 24 Oct 2000 00:39:42 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id AAA06195; Tue, 24 Oct 2000 00:37:58 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpdAAAoda45l; Tue Oct 24 00:37:54 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id AAA11051; Tue, 24 Oct 2000 00:39:20 -0700 (MST) From: Terry Lambert Message-Id: <200010240739.AAA11051@usr01.primenet.com> Subject: Re: FreeBSD vs. Linux To: fengyue@bluerose.windmoon.nu (FengYue) Date: Tue, 24 Oct 2000 07:39:20 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "FengYue" at Oct 21, 2000 05:31:50 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 21 Oct 2000, Frederik Meerwaldt wrote: > > ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I > > Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really > doesn't matter IMHO) > > Don't forget UNIX is a trademark of Open Group. Actually, it's a trademark of USL, licensed to The Open Group. People with paid up USL licenses are grandfathered to be able to call it UNIX, since it's derived from USL sources. I believe there was actually a full POSIX certification of a version of Linux at one time, but it's certainly dated, and the trademark usage rules have since changed. I believe that the The Open Group license is exclusive, so I don't know what impact Caldera's recent purchase has on their ability to call Caldera Linux "UNIX". Last time I checked, they wanted an unholy amount of money to permit you to use the trademark, or they wanted a similar amount for an SVR4 source license, so there was practically no difference in the money they got out of the deal (so I guess the value is in the name, not the code). On a similar note, Novell was licensing NetWare for UNIX for $150,000, the Netware for UNIX Client for $100,000, or you could get UNIX sources and both NetWare products for $250,000, which also makes a statement about the value of the SVR4 source code... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 0:54:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id EB3A037B479 for ; Tue, 24 Oct 2000 00:54:29 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id AAA23504; Tue, 24 Oct 2000 00:54:52 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAAOIaG4T; Tue Oct 24 00:54:47 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id AAA11489; Tue, 24 Oct 2000 00:54:18 -0700 (MST) From: Terry Lambert Message-Id: <200010240754.AAA11489@usr01.primenet.com> Subject: Re: Cache Questions To: charrer@alacritech.com (Christopher Harrer) Date: Tue, 24 Oct 2000 07:54:18 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG (Freebsd-Hackers) In-Reply-To: from "Christopher Harrer" at Oct 23, 2000 08:33:04 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We're working on a driver for a PCI card, we're currently running into a > problem that's symptomatic of a cache coherency problem. We have a area of > memory that we manipulate and pass a physical address to our card. In other > OS's (Linux, NT), before we manipulate this memory area, we mark the area as > non-cachable. Are there similar operations/system calls we can use in > FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory > usage/attributes? FreeBSD has a unified VM and buffer cache, so you should not really be having cache coherency issues. This sounds like the DMA from the card is getting bad data transferred into the card memory from the host memory, since the data is in the chip cache, and hasn't been written to main memory yet? I think this is the only possible failure mode. This indicates to me that your cache is not properly configured for write-through, or that you are using an older chipset, with more than two PCI devices. You could always mark it non-cacheable, of course: there are primitives to support this (see other postings in this thread), but I would really be surprised about you needing to do this. Another alternative might be that your card is eating the high bits (i.e. it can only see a region of low memory), or that you are doing unaligned transfers (many cards hate them), so there might be other avenues you should explore (I know that there are a number of video boards, for example, which can only access low memory correctly). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 1: 8:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C037B479; Tue, 24 Oct 2000 01:08:10 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id BAA25961; Tue, 24 Oct 2000 01:08:37 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAA7taWRY; Tue Oct 24 01:08:30 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id BAA11953; Tue, 24 Oct 2000 01:08:00 -0700 (MST) From: Terry Lambert Message-Id: <200010240808.BAA11953@usr01.primenet.com> Subject: Re: Cache Questions To: msmith@FreeBSD.ORG (Mike Smith) Date: Tue, 24 Oct 2000 08:08:00 +0000 (GMT) Cc: charrer@alacritech.com (Christopher Harrer), freebsd-hackers@FreeBSD.ORG (Freebsd-Hackers) In-Reply-To: <200010232007.e9NK7Ih04538@mass.osd.bsdi.com> from "Mike Smith" at Oct 23, 2000 01:07:18 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We're working on a driver for a PCI card, we're currently running into a > > problem that's symptomatic of a cache coherency problem. We have a area of > > memory that we manipulate and pass a physical address to our card. In other > > OS's (Linux, NT), before we manipulate this memory area, we mark the area as > > non-cachable. Are there similar operations/system calls we can use in > > FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory > > usage/attributes? > > Take a look at , and particularly mem_range_attr_set(). > > *However*, since the PC architecture is strongly cache coherent, you > probably have a problem with the design or implementation of your > driver:adapter protocol. Marking an entire region of memory as > uncacheable is *very* inefficient; there are much better ways of > maintaining synchronisation without doing this. Mark had a good point about wiring the pages so they don't get swapped, if they are in a swappable region in another thread discussion DMA. He also pointed out that if he was talking about physical pages, that he needs to make sure that they are either contiguous, or that the DMA region doesn't span a page boundary. If the original poster follows -hackers, look for a subject with "DMA in drivers", since the topic appears to be over similar general issues. For that matter, your scatter/gather comments in that thread were also potentially relevent. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 1:56:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 1DB2E37B479 for ; Tue, 24 Oct 2000 01:56:49 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id zdnjaaaa for ; Tue, 24 Oct 2000 01:54:31 -0700 From: "Christopher Harrer" To: "Terry Lambert" Cc: "Freebsd-Hackers" Subject: RE: Cache Questions Date: Tue, 24 Oct 2000 04:54:48 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: <200010240754.AAA11489@usr01.primenet.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry, Thanks for the information, you're right in that we are not experiencing cache problems. It's a timing issue we haven't tracked down yet, but I'm sure we will. Thanks for the DMA pointers. Chris -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Terry Lambert Sent: Tuesday, October 24, 2000 3:54 AM To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Cache Questions > We're working on a driver for a PCI card, we're currently running into a > problem that's symptomatic of a cache coherency problem. We have a area of > memory that we manipulate and pass a physical address to our card. In other > OS's (Linux, NT), before we manipulate this memory area, we mark the area as > non-cachable. Are there similar operations/system calls we can use in > FreeBSD? Are there any FAQ's, Docs or man-pages that explain memory > usage/attributes? FreeBSD has a unified VM and buffer cache, so you should not really be having cache coherency issues. This sounds like the DMA from the card is getting bad data transferred into the card memory from the host memory, since the data is in the chip cache, and hasn't been written to main memory yet? I think this is the only possible failure mode. This indicates to me that your cache is not properly configured for write-through, or that you are using an older chipset, with more than two PCI devices. You could always mark it non-cacheable, of course: there are primitives to support this (see other postings in this thread), but I would really be surprised about you needing to do this. Another alternative might be that your card is eating the high bits (i.e. it can only see a region of low memory), or that you are doing unaligned transfers (many cards hate them), so there might be other avenues you should explore (I know that there are a number of video boards, for example, which can only access low memory correctly). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 3:15:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 57AE637B4CF for ; Tue, 24 Oct 2000 03:15:49 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Oct 2000 11:15:47 +0100 (BST) Date: Tue, 24 Oct 2000 11:15:47 +0100 From: David Malone To: Vadim Belman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS/VM deadlock report and help request Message-ID: <20001024111547.A58909@walton.maths.tcd.ie> References: <20001020145043.B73760@lflat.vas.mobilix.dk> <20001020171810.A28345@walton.maths.tcd.ie> <200010201624.e9KGO3B08039@earth.backplane.com> <20001024092101.A88854@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001024092101.A88854@lflat.vas.mobilix.dk>; from voland@lflat.org on Tue, Oct 24, 2000 at 09:21:01AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 24, 2000 at 09:21:01AM +0200, Vadim Belman wrote: > After a day of testing I confirm that the patch does work. I've just committed the patch to -current, I'll MFC it in a few days. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 3:22:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c3-dbn-41.dial-up.net (c3-dbn-41.dial-up.net [196.33.200.41]) by hub.freebsd.org (Postfix) with ESMTP id 6C03A37B479 for ; Tue, 24 Oct 2000 03:22:17 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id MAA16016; Tue, 24 Oct 2000 12:20:53 +0200 (SAST) From: Robert Nordier Message-Id: <200010241020.MAA16016@siri.nordier.com> Subject: Re: Conflicting C/H/S values To: tpnelson@echidna.stu.cowan.edu.au (Trent Nelson) Date: Tue, 24 Oct 2000 12:20:53 +0200 (SAST) Cc: hackers@FreeBSD.ORG In-Reply-To: <39F2D320.74A760FF@echidna.stu.cowan.edu.au> from "Trent Nelson" at Oct 22, 2000 07:44:32 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trent Nelson wrote: > Could someone explain to me why the following HDD BIOS Geometries don't > represent the values proposed by the drives. What am I missing? > > (snippets from boot -v) > > BIOS Geometries: > 0:030c7f3f 0..780=781 cylinders, 0..127=128 heads, 1..63=63 sectors > 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 3:026dfe3f 0..621=622 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > > These don't correlate to the C/H/S values proposed by the drives: > > ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S > ad2: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S > ad3: 4892MB (10018890 sectors), 10602 cyls, 15 heads, 63 S/T, 512 B/S > > I'm running 5.0 as of mid-September, but I don't think that's the issue > as Windows tends to exhibit the same behaviour. The way the PC BIOS CHS disk interface was designed, too few cylinders (1024) and too many heads (256) are supported, compared with the geometry disk drives pretend to have nowadays. So most modern BIOSes do translation by default, representing 6256 cyls x 16 heads as (6256/8 x 16*8 =) 782 cyls x 128 heads. The off-by-one difference (782 vs. 781 given as BIOS geometry for drive 0) is due to reserving the last cylinder for diagnostics, etc., another BIOS quirk. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 4:39:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 0710B37B479 for ; Tue, 24 Oct 2000 04:39:12 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id sgnjaaaa for ; Tue, 24 Oct 2000 04:36:55 -0700 From: "Christopher Harrer" To: "Freebsd-Hackers" Subject: Determining CPU on SMP box Date: Tue, 24 Oct 2000 07:37:12 -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.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Is there a way to determine which CPU I'm currently executing on in a SMP box? I've found references to proc->p_oncpu, but I'm not sure if this is the best way to determine where I'm executing. I'd like to be able to "trace" various actions within my driver and one of the fields I want to keep track of is what CPU I'm executing on. Thanks! Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 5:12:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 3147937B4C5; Tue, 24 Oct 2000 05:12:17 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.11.0) id e9OCCGo95458; Tue, 24 Oct 2000 14:12:16 +0200 (CEST) (envelope-from asmodai) Date: Tue, 24 Oct 2000 14:12:16 +0200 From: Jeroen Ruigrok van der Werven To: David Malone Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, hackers@FreeBSD.org Subject: Re: cvs commit: src/sys/nfs nfs.h nfs_subs.c nfsm_subs.h Message-ID: <20001024141216.H93799@lucifer.bart.nl> Reply-To: hackers@FreeBSD.org References: <200010241013.DAA74467@freefall.freebsd.org> <20001024130316.C93799@lucifer.bart.nl> <20001024125141.A35631@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001024125141.A35631@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Oct 24, 2000 at 12:51:41PM +0100 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Redirecting to -hackers after this one] -On [20001024 13:55], David Malone (dwmalone@maths.tcd.ie) wrote: >On Tue, Oct 24, 2000 at 01:03:16PM +0200, Jeroen Ruigrok van der Werven wrote: > >> Does this solve the problem reported by me in MSG-ID: >> >> 20000618132353.B95177@lucifer.bart.nl >> >> on -stable back in June/July? > >Possibly, but probably not. We do know about another bug which >causes this sort of problem, but haven't quite figured out how to >fix it yet. See Ian's message to -hackers: > > 200010201733.aa97121@salmon.maths.tcd.ie Just read through the thread, the situation looks like the one we had. At least for the vmopar problems. We run a bunch of webservers who get the data off of a read-only NFS mount from a NetApp. Of course when an user updates the files the Apache webserver might reference that file and you get the same problem as Vadim described. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl But touch my Tears, with your lips, touch my World, with your fingertips, and we can have forever... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 6:11:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 0895D37B479; Tue, 24 Oct 2000 06:11:28 -0700 (PDT) Received: by puck.firepipe.net (Postfix, from userid 1000) id 156C61908; Tue, 24 Oct 2000 08:11:36 -0500 (EST) Date: Tue, 24 Oct 2000 08:11:36 -0500 From: Will Andrews To: Jordan Hubbard Cc: "Scott D. Yelich" , Jeremy Lea , freebsd-hackers@FreeBSD.org Subject: Re: Who broke "ls" in FreeBSD? and why? Message-ID: <20001024081136.K1604@puck.firepipe.net> Reply-To: Will Andrews References: <12367.972372237@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <12367.972372237@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Oct 24, 2000 at 12:23:57AM -0700 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ redirected to -hackers ] On Tue, Oct 24, 2000 at 12:23:57AM -0700, Jordan Hubbard wrote: > What's wrong with -a? And what the heck does this have to do with > mobile computing? -a doesn't disable -A, it adds to it (also shows . and ..). I think this guy's looking for an option to disable this flag.. no idea why. One could simply invoke `ls' as a normal user (say, `nobody') if they so desired. -- Will Andrews - Physics Computer Network wench To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 10:57:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E650B37B4C5; Tue, 24 Oct 2000 10:57:41 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9OHvPn87615; Tue, 24 Oct 2000 11:57:25 -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.9.3/8.8.3) with ESMTP id LAA17136; Tue, 24 Oct 2000 11:57:24 -0600 (MDT) Message-Id: <200010241757.LAA17136@harmony.village.org> To: Will Andrews Subject: Re: Who broke "ls" in FreeBSD? and why? Cc: Jordan Hubbard , "Scott D. Yelich" , Jeremy Lea , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 24 Oct 2000 08:11:36 CDT." <20001024081136.K1604@puck.firepipe.net> References: <20001024081136.K1604@puck.firepipe.net> <12367.972372237@winston.osd.bsdi.com> Date: Tue, 24 Oct 2000 11:57:24 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001024081136.K1604@puck.firepipe.net> Will Andrews writes: : [ redirected to -hackers ] : : On Tue, Oct 24, 2000 at 12:23:57AM -0700, Jordan Hubbard wrote: : > What's wrong with -a? And what the heck does this have to do with : > mobile computing? : : -a doesn't disable -A, it adds to it (also shows . and ..). I think : this guy's looking for an option to disable this flag.. no idea why. : One could simply invoke `ls' as a normal user (say, `nobody') if they so : desired. Yes. Last night I misunderstood what he was saying. For normal users, ls -a lists all files, not counting . and .., but for root it does list all files. ls -A lists all files for normal users, but omits . and .. for root. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 11:12:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A28D37B4CF; Tue, 24 Oct 2000 11:12:06 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Tue, 24 Oct 2000 14:12:15 -0400 Message-ID: <39F5D14E.806B7BA9@tellurian.com> Date: Tue, 24 Oct 2000 14:13:35 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: Nick Rogness Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IT WORKED ! the arp way is the true way hehehe I edited /sbin/dhclient-script to automate the process: - removed the code that was supposed to add the default gateway - added following lines in its place: arp -s 208.59.162.1 00:20:cd:02:f1:59 # MAC address of cable modem gateway route add default 208.59.162.1 Later I'll have to figure out a way to take the $new_ip_address variable and modify it into my dummy gateway, so that the script would handle any IP my provider throws at it. And to make it work with any modem, I'd need an automatic way to get the MAC based on gateway IP (10.17.56.12). Any standard way to do this ? Thanks to everyone who has replied with suggestions, especially to Nick whose suggestion was the answer I needed :) Nick Rogness wrote: > On Mon, 23 Oct 2000, Les Biffle wrote: > > > > Hm -- how about using proxy-arp style routing? > > > > Here's what I've done in the past: > > > > 1. Have a friend out in the net ping your address 208.59.162.242 > > > > 2. Run tcpdump and look for someone ARPing for you. That someone > > will very likely be your default gateway as seen from your site. > > If that router is in your subnet, set your default to it and you're > > done. If not, continue at the next step. > > > > 3. Pick an IP Address in your cable subnet that feels like a really > > good router address to you. Make something up. 208.59.162.1 perhaps? > > > > 4. Use "arp -s 208.59.162.1 xx:xx:xx:xx:xx:xx" to install an arp > > entry in your route table for this made-up address. That will keep > > you from ARPing for 208.59.162.1 and discovering the device that > > really owns that address. > > > > 5. Set your default gateway to 208.59.162.1. > > If that doesn't work (it should), you could also look into the > ipfw fwd option. > > I would like to know when you get it to work... > > Nick Rogness > - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 11:23:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 42E5137B4C5; Tue, 24 Oct 2000 11:23:44 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id MAA74429; Tue, 24 Oct 2000 12:23:42 -0600 (MDT) Date: Tue, 24 Oct 2000 12:23:42 -0600 (MDT) From: Nick Rogness To: Marko Ruban Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <39F5D14E.806B7BA9@tellurian.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Oct 2000, Marko Ruban wrote: > IT WORKED ! > the arp way is the true way hehehe > > > Thanks to everyone who has replied with suggestions, especially to Nick > whose suggestion was the answer I needed :) Actually it was Mr. Biffle (Les Biffle ). I will make sure to document it though. Thanks for the reply. Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 11:27:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D137E37B4C5; Tue, 24 Oct 2000 11:27:08 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9OIR8313379; Tue, 24 Oct 2000 11:27:08 -0700 (PDT) Date: Tue, 24 Oct 2000 11:27:08 -0700 From: Alfred Perlstein To: dillon@freebsd.org Cc: ps@freebsd.org, hackers@freebsd.org Subject: vm_pageout_scan badness Message-ID: <20001024112708.E28123@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, I'm not sure if Paul mailed you yet so I thought I'd take the initiative of bugging you about some reported problems (lockups) when dealing with machines that have substantial MAP_NOSYNC'd data along with a page shortage. What seems to happen is that vm_pageout_scan (src/sys/vm/vm_pageout.c line 618) keeps rescanning the inactive queue. My guess is that it just doesn't expect someone to have hosed themselves by having so many pages that need laundering (maxlaunder/launder_loop) along with the fact that the comment and code here are doing the wrong thing for the situation: /* * Figure out what to do with dirty pages when they are encountered. * Assume that 1/3 of the pages on the inactive list are clean. If * we think we can reach our target, disable laundering (do not * clean any dirty pages). If we miss the target we will loop back * up and do a laundering run. */ if (cnt.v_inactive_count / 3 > page_shortage) { maxlaunder = 0; launder_loop = 0; } else { maxlaunder = (cnt.v_inactive_target > max_page_launder) ? max_page_launder : cnt.v_inactive_target; launder_loop = 1; } The problem is that there's a chance that nearly all the pages on the inactive queue need laundering and the loop that starts with the lable 'rescan0:' is never able to clean enough pages before stumbling across a block that has moved to another queue. This forces a jump back to the 'rescan0' lable with effectively nothing accomplished. Here's a patch that may help, it's untested, but shows what I'm hoping to achieve which is force a maximum on the amount of times rescan0 will be jumped to while not laundering. Index: vm_pageout.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_pageout.c,v retrieving revision 1.151.2.4 diff -u -u -r1.151.2.4 vm_pageout.c --- vm_pageout.c 2000/08/04 22:31:11 1.151.2.4 +++ vm_pageout.c 2000/10/24 07:31:39 @@ -618,7 +618,7 @@ vm_pageout_scan() { vm_page_t m, next; - int page_shortage, maxscan, pcount; + int page_shortage, maxscan, maxtotscan, pcount; int addl_page_shortage, addl_page_shortage_init; int maxlaunder; int launder_loop = 0; @@ -672,13 +672,23 @@ * we have scanned the entire inactive queue. */ +rescantot: + /* make sure we don't hit rescan0 too many times */ + maxtotscan = cnt.v_inactive_count; rescan0: addl_page_shortage = addl_page_shortage_init; maxscan = cnt.v_inactive_count; + if (maxtotscan < 1) { + maxlaunder = + (cnt.v_inactive_target > max_page_launder) ? + max_page_launder : cnt.v_inactive_target; + } for (m = TAILQ_FIRST(&vm_page_queues[PQ_INACTIVE].pl); m != NULL && maxscan-- > 0 && page_shortage > 0; m = next) { + --maxtotscan; + cnt.v_pdpages++; if (m->queue != PQ_INACTIVE) { @@ -930,7 +940,7 @@ maxlaunder = (cnt.v_inactive_target > max_page_launder) ? max_page_launder : cnt.v_inactive_target; - goto rescan0; + goto rescantot; } /* (still talking about vm_pageout_scan()): I'm pretty sure that there's yet another problem here, when paging out a vnode's pages the output routine attempts to cluster them, this could easily make 'next' point to a page that is cleaned and put on the FREE queue, when the loop then tests it for 'm->queue != PQ_INACTIVE' it forces 'rescan0' to happen. I think one could fix this by keeping a pointer to the previous page then the 'goto rescan0;' test might become something like this: /* * We keep a back reference just in case the vm_pageout_clean() * happens to clean the page after the one we just cleaned * via clustering, this would make next point to something not * one the INACTIVE queue, as a stop-gap we keep a pointer * to the previous page and attempt to use it as a fallback * starting point before actually starting at the head of the * INACTIVE queue again */ if (m->queue != PQ_INACTIVE) { if (prev != NULL && prev->queue == PQ_INACTIVE) { m = TAILQ_NEXT(prev, pageq); if (m == NULL || m->queue != PQ_INACTIVE) goto rescan0; } else { goto rescan0; } } Of course we need to set 'prev' properly, but I need to get back to my database stuff right now. :) Also... I wish there was a good hueristic to make max_page_launder a bit more adaptive, you've done some wonders with bufdaemon so I'm wondering if you had some ideas about that. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 11:37:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id A0B4A37B479 for ; Tue, 24 Oct 2000 11:37:30 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13o8wu-0002Gi-00; Tue, 24 Oct 2000 19:37:24 +0100 Date: Tue, 24 Oct 2000 19:37:24 +0100 To: hackers@freebsd.org Subject: Solaris 8's split cache Message-ID: <20001024193724.A8443@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://sunsolve.Sun.COM/pub-cgi/show.pl?target=content/content8#cyclical BSD doesn't do anything like this (distinguishing between instructions and data in the VM cache), does it? Should it? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 11:44:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D688E37B479 for ; Tue, 24 Oct 2000 11:44:25 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9OIiNB14059; Tue, 24 Oct 2000 11:44:23 -0700 (PDT) Date: Tue, 24 Oct 2000 11:44:23 -0700 From: Alfred Perlstein To: void Cc: hackers@FreeBSD.ORG Subject: Re: Solaris 8's split cache Message-ID: <20001024114423.I28123@fw.wintelcom.net> References: <20001024193724.A8443@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001024193724.A8443@firedrake.org>; from float@firedrake.org on Tue, Oct 24, 2000 at 07:37:24PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * void [001024 11:37] wrote: > http://sunsolve.Sun.COM/pub-cgi/show.pl?target=content/content8#cyclical > > BSD doesn't do anything like this (distinguishing between instructions > and data in the VM cache), does it? Should it? It's an interesting idea, the only weirdness is that one could pretty easily tie down a lot of memory with underused instruction data and force the filesystem cache to use a much smaller subset of memory than it should degrading performance, it could also work against you in the opposite direction. If solaris is able to put these pages on a "general inactive+free queue" after some time so that pages can migrate between the two caches it would help out some. Interestingly enough we're trying to address a problem related to this in FreeBSD right now, but I'm not sure the Solaris solution is the right way to go. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 13:10:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CEF9337B479; Tue, 24 Oct 2000 13:10:40 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9OKAJK19739; Tue, 24 Oct 2000 13:10:19 -0700 (PDT) (envelope-from dillon) Date: Tue, 24 Oct 2000 13:10:19 -0700 (PDT) From: Matt Dillon Message-Id: <200010242010.e9OKAJK19739@earth.backplane.com> To: Alfred Perlstein Cc: ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness References: <20001024112708.E28123@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ouch. The original VM code assumed that pages would not often be ripped out from under the pageadaemon, so it felt free to restart whenever. I think you are absolutely correct in regards to the clustering code causing nearby-page ripouts. I don't have much time available, but let me take a crack at the problem tonight. I don't think we want to add another workaround to code that already has too many of them. The solution may be to create a dummy placemarker vm_page_t and to insert it into the pagelist just after the current page after we've locked it and decided we have to do something significant to it. We would then be able to pick the scan up where we left off using the placemarker. This would allow us to get rid of the restart code entirely, or at least devolve it back into its original design (i.e. something that would not happen very often). Since we already have cache locality of reference for the list node, the placemarker idea ought to be quite fast. I'll take a crack at implementing the openbsd (or was it netbsd?) partial fsync() code as well, to prevent the update daemon from locking up large files that have lots of dirty pages for long periods of time. -Matt : :Matt, I'm not sure if Paul mailed you yet so I thought I'd take the :initiative of bugging you about some reported problems (lockups) :when dealing with machines that have substantial MAP_NOSYNC'd :data along with a page shortage. : :What seems to happen is that vm_pageout_scan (src/sys/vm/vm_pageout.c :line 618) keeps rescanning the inactive queue. : :My guess is that it just doesn't expect someone to have hosed themselves :by having so many pages that need laundering (maxlaunder/launder_loop) :along with the fact that the comment and code here are doing the wrong :thing for the situation: : : /* : * Figure out what to do with dirty pages when they are encountered. : * Assume that 1/3 of the pages on the inactive list are clean. If : * we think we can reach our target, disable laundering (do not : * clean any dirty pages). If we miss the target we will loop back : * up and do a laundering run. : */ : : if (cnt.v_inactive_count / 3 > page_shortage) { : maxlaunder = 0; : launder_loop = 0; : } else { : maxlaunder = : (cnt.v_inactive_target > max_page_launder) ? : max_page_launder : cnt.v_inactive_target; : launder_loop = 1; : } : :The problem is that there's a chance that nearly all the pages on :the inactive queue need laundering and the loop that starts with :the lable 'rescan0:' is never able to clean enough pages before :stumbling across a block that has moved to another queue. This :forces a jump back to the 'rescan0' lable with effectively nothing :accomplished. : :Here's a patch that may help, it's untested, but shows what I'm :hoping to achieve which is force a maximum on the amount of times :rescan0 will be jumped to while not laundering. :... : :I'm pretty sure that there's yet another problem here, when paging :out a vnode's pages the output routine attempts to cluster them, :this could easily make 'next' point to a page that is cleaned and :put on the FREE queue, when the loop then tests it for :'m->queue != PQ_INACTIVE' it forces 'rescan0' to happen. : :I think one could fix this by keeping a pointer to the previous :page then the 'goto rescan0;' test might become something like :this: :... : :Of course we need to set 'prev' properly, but I need to get back :to my database stuff right now. :) : :Also... I wish there was a good hueristic to make max_page_launder :a bit more adaptive, you've done some wonders with bufdaemon so :I'm wondering if you had some ideas about that. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] :"I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 13:44: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by hub.freebsd.org (Postfix) with SMTP id 8107E37B479 for ; Tue, 24 Oct 2000 13:44:05 -0700 (PDT) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA03532; Tue, 24 Oct 00 15:40:40 EDT Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id PAA00991 for ; Tue, 24 Oct 2000 15:40:55 -0400 (EDT) Received: from contents-vnder-pressvre.mit.edu (CONTENTS-VNDER-PRESSVRE.MIT.EDU [18.184.0.40]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id PAA05062 for ; Tue, 24 Oct 2000 15:40:54 -0400 (EDT) Received: (from daveg@localhost) by contents-vnder-pressvre.mit.edu (8.9.3) id PAA07983; Tue, 24 Oct 2000 15:40:46 -0400 (EDT) To: freebsd-hackers@freebsd.org Subject: PCI Device Remapping From: David D Golombek Date: 24 Oct 2000 15:40:46 -0400 Message-Id: Lines: 28 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.3 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've written a device driver for a proprietary PCI card, and have run into what seems to be a show-stopping bug. The device I'm writing the driver for is responsible for running DMA transfers to other PCI devices, and all of our initial work was going well. I locked down a contiguous range of host memory and was able to do DMA fine. I'm now trying to get the card to do DMA to other PCI cards, and have found a bug in our chip. Basically, the high bit of the address on PCI transfers gets dropped. This means that the chip can't address PCI memory physical addresses over 0x7FFFFFFF. Big problem, since the BIOS on our computers maps PCI device memory from 0xFFFF0000 downward. So my question is, under FreeBSD (any version -- we're currently running 3.4, but I can upgrade to -current if it will help), is there any support for overriding the BIOS-assigned PCI address maps? I've read through the 3.4 pci.c code and didn't see anything, and am not thrilled about writing code to remap all the devices on the PCI bus. I'm talking to our BIOS vendor about getting them to do the rework for us, but as in all dealing with BIOS vendors, I am not hopeful :-( Thanks for any and all suggestions! DaveG o_, o, o_ o_ o' Programmer )-' /|' ),` ) ' (\ ^o Gymnast Dancer >\ / > >\ >^' >\ >>' Hiker daveg@mit.edu www.mit.edu/~daveg/ (617)216-4705 dave.golombek@conexant.com www.conexant.com (508)621-0658 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 13:44:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 57C7537B479 for ; Tue, 24 Oct 2000 13:44:32 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9OKmPh02075; Tue, 24 Oct 2000 13:48:25 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010242048.e9OKmPh02075@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Christopher Harrer" Cc: "Freebsd-Hackers" Subject: Re: Determining CPU on SMP box In-reply-to: Your message of "Tue, 24 Oct 2000 07:37:12 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Oct 2000 13:48:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a way to determine which CPU I'm currently executing on in a SMP > box? I've found references to proc->p_oncpu, but I'm not sure if this is > the best way to determine where I'm executing. I'd like to be able to > "trace" various actions within my driver and one of the fields I want to > keep track of is what CPU I'm executing on. There's a per-CPU variable 'cpuid' (at least, there used to be) that you could use for this. However, it's kinda pointless working out what CPU you're on, since you're liable to be rescheduled onto another CPU if an interrupt occurs... -- ... 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 Tue Oct 24 13:45: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 6C7C137B4C5 for ; Tue, 24 Oct 2000 13:44:58 -0700 (PDT) Received: (qmail 21560 invoked from network); 24 Oct 2000 20:51:33 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 24 Oct 2000 20:51:33 -0000 Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id e9OGjXX18205; Tue, 24 Oct 2000 16:47:21 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200010241647.e9OGjXX18205@jhs.muc.de> To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Tue, 24 Oct 2000 07:39:20 -0000." <200010240739.AAA11051@usr01.primenet.com> Date: Tue, 24 Oct 2000 18:45:33 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Terry Lambert wrote: > > On Sat, 21 Oct 2000, Frederik Meerwaldt wrote: > > ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I > > Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really > > doesn't matter IMHO) > > Don't forget UNIX is a trademark of Open Group. > > Actually, it's a trademark of USL, licensed to The Open Group. `Actually' ;-) ... Well I'm not sure, ... the TM ownership has ceased to be of real relevance to me, but AFAIR Unix the TM was bought by SCO a few years back, (SCO=Santa Cruz Org, server div. of which is busy being bought by Caldera, a Linux distrib.) > I believe that the The Open Group license is exclusive, so I Exclusion not possible regarding current licensed usage of the name, only regarding granting of future licences to use the name. > don't know what impact Caldera's recent purchase has on their > ability to call Caldera Linux "UNIX". Unix the TM has moved a lot: AT&T Bell Labs NJ, then also licensed by Unix Europe in Putney London (a European subsidiary of AT&T) used to flog licences in the 80s, I guess just about every major computer co. can dig up a licence that they too are allowed to flog some ancient version of Unix, & use the name Unix in marketing etc (probably with a `this is not the original, but is based on' clause). Who this season holds the right to sell licenses to use the Unix TM I'm not sure, but as the Bavarian (Germany) division of SCO holds its quarterly business briefing this thursday (supported by Caldera, backed by Compaq), I'll ask them if they know who's the current owner of the trademark. Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3900 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 13:45:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 7C3EF37B4F9 for ; Tue, 24 Oct 2000 13:45:01 -0700 (PDT) Received: (qmail 21572 invoked from network); 24 Oct 2000 20:51:34 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 24 Oct 2000 20:51:34 -0000 Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id e9OGFuX18041; Tue, 24 Oct 2000 16:17:44 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200010241617.e9OGFuX18041@jhs.muc.de> To: Christian Weisgerber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anybody want to review vi patch? From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Sat, 21 Oct 2000 13:28:00 +0200." <20001021132800.A67078@kemoauc.mips.inka.de> Date: Tue, 24 Oct 2000 18:15:56 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did some additions to vi long ago: http://bim.bsn.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/contrib/nvi/ I seem to recall sending them to Keith Bostik maybe (the/an author I recall), my patches ars still outstanding AFAIK. (my patches signal link vi to chimera ghostscript & xfig to do a WYSIWYG linkage between an xterm editing a source, & a graphical output viewer ). Reference: > From: Christian Weisgerber > Date: Sat, 21 Oct 2000 13:28:00 +0200 > Message-id: <20001021132800.A67078@kemoauc.mips.inka.de> Hi, Christian Weisgerber wrote: > > --UugvWAfsgieZRqgk > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > There's a bug in nvi 1.79. The options "noprint", "print", and > "octal" don't work properly. When these options are changed, the > routine that evaluates them is called before the option has been > set. > > Do we have any people who know their way around the guts of nvi? > I've appended a patch, partly based on a change in nvi 1.81 where > this is fixed incompletely, and I'd like somebody to review this. Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3900 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 14: 5:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id D566337B479 for ; Tue, 24 Oct 2000 14:05:14 -0700 (PDT) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id PAA204162; Tue, 24 Oct 2000 15:05:14 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id PAA26403; Tue, 24 Oct 2000 15:05:14 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Tue, 24 Oct 2000 15:05:14 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: daveg@mit.edu Cc: hackers@freebsd.org Subject: pci maps Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if your cards are on pci bus 0, not behind a bridge, you can set the base addresses to pretty much any value you want even after the OS is up -- you just have to make sure the drivers are all informed. But it's no big deal, you can do it from user mode if you have access to ports cf8/cfc. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 14:14:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-145.dsl.snfc21.pacbell.net [63.202.176.145]) by hub.freebsd.org (Postfix) with ESMTP id 2DA1C37B479 for ; Tue, 24 Oct 2000 14:14:53 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9OLIXh02243; Tue, 24 Oct 2000 14:18:38 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010242118.e9OLIXh02243@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David D Golombek Cc: freebsd-hackers@freebsd.org Subject: Re: PCI Device Remapping In-reply-to: Your message of "24 Oct 2000 15:40:46 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Oct 2000 14:18:33 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've written a device driver for a proprietary PCI card, and have run > into what seems to be a show-stopping bug. The device I'm writing the > driver for is responsible for running DMA transfers to other PCI > devices, and all of our initial work was going well. I locked down a > contiguous range of host memory and was able to do DMA fine. I'm now > trying to get the card to do DMA to other PCI cards, and have found a > bug in our chip. Basically, the high bit of the address on PCI > transfers gets dropped. This means that the chip can't address PCI > memory physical addresses over 0x7FFFFFFF. Big problem, since the > BIOS on our computers maps PCI device memory from 0xFFFF0000 downward. Whoops. > So my question is, under FreeBSD (any version -- we're currently > running 3.4, but I can upgrade to -current if it will help), is there > any support for overriding the BIOS-assigned PCI address maps? I've > read through the 3.4 pci.c code and didn't see anything, and am not > thrilled about writing code to remap all the devices on the PCI bus. There is no support, no. You really have one serious option - fix your chip. > I'm talking to our BIOS vendor about getting them to do the rework for > us, but as in all dealing with BIOS vendors, I am not hopeful :-( If you're working on a single, fixed platform, this should be pretty simple; they just lop the top bit off the base address they use for PCI address allocation. Here's an evil trick you can pull though, if you're *really* desperate and if you're *certain* that you're in control of your platform, and *certain* that you'll never have more than ~1.9GB of physical memory. In sys/pci/pci.c:pci_readmaps(), fix the loop that reads maps to knock the high bit off memory ranges and write them back: for (i = 0; i < maxmaps; i++) { int reg = PCIR_MAPS + i*4; u_int32_t base; u_int32_t ln2range; base = pci_cfgread(cfg, reg, 4); ln2range = pci_maprange(base); if (base == 0 || ln2range == 0 || base == 0xffffffff) continue; /* skip invalid entry */ else { /* remap below 2GB */ if (pci_maptype(base) == PCI_MAPMEM) { base &= ~0x80000000; pci_cfgwrite(cfg, reg, base, 4); ln2range = pci_maprange(base); } j++; if (ln2range > 32) { i++; j++; } } } This is, of course, only a solution if you have total control over the system as well; if you plan to ship the product for inclusion in general FreeBSD systems, you're prettymuch hosed. I hope this helps though. -- ... 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 Tue Oct 24 15:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by hub.freebsd.org (Postfix) with SMTP id A5FA737B479; Tue, 24 Oct 2000 15:11:17 -0700 (PDT) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA11896; Tue, 24 Oct 00 18:11:00 EDT Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id SAA20476; Tue, 24 Oct 2000 18:08:46 -0400 (EDT) Received: from contents-vnder-pressvre.mit.edu (CONTENTS-VNDER-PRESSVRE.MIT.EDU [18.184.0.40]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id SAA29217; Tue, 24 Oct 2000 18:08:45 -0400 (EDT) Received: (from daveg@localhost) by contents-vnder-pressvre.mit.edu (8.9.3) id SAA13482; Tue, 24 Oct 2000 18:08:45 -0400 (EDT) To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: PCI Device Remapping References: <200010242118.e9OLIXh02243@mass.osd.bsdi.com> From: David D Golombek Date: 24 Oct 2000 18:08:45 -0400 In-Reply-To: Mike Smith's message of "Tue, 24 Oct 2000 14:18:33 -0700" Message-Id: Lines: 63 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.3 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > If you're working on a single, fixed platform, this should be pretty > simple; they just lop the top bit off the base address they use for PCI > address allocation. > > Here's an evil trick you can pull though, if you're *really* desperate > and if you're *certain* that you're in control of your platform, and > *certain* that you'll never have more than ~1.9GB of physical memory. > > In sys/pci/pci.c:pci_readmaps(), fix the loop that reads maps to knock the > high bit off memory ranges and write them back: > > for (i = 0; i < maxmaps; i++) { > int reg = PCIR_MAPS + i*4; > u_int32_t base; > u_int32_t ln2range; > > base = pci_cfgread(cfg, reg, 4); > ln2range = pci_maprange(base); > > if (base == 0 || ln2range == 0 || base == 0xffffffff) > continue; /* skip invalid entry */ > else { > /* remap below 2GB */ > if (pci_maptype(base) == PCI_MAPMEM) { > base &= ~0x80000000; > pci_cfgwrite(cfg, reg, base, 4); > ln2range = pci_maprange(base); > } > j++; > if (ln2range > 32) { > i++; > j++; > } > } > } > > This is, of course, only a solution if you have total control over the > system as well; if you plan to ship the product for inclusion in general > FreeBSD systems, you're prettymuch hosed. This is actually only needed for an internal use project, and this hack is exactly what I was looking for! It works wonderfully, although I had to change the code slightly: if ((pci_maptype(base) & PCI_MAPMEM) == PCI_MAPMEM) { base &= ~0x80000000; printf("0x%x)\n", base); pci_cfgwrite(cfg, reg, base, 4); ln2range = pci_maprange(base); } to handle prefetchable memory as well. Thank you very much for the suggestion -- I'd read through that code, but didn't think about the simple fix you've suggested! DaveG o_, o, o_ o_ o' Programmer )-' /|' ),` ) ' (\ ^o Gymnast Dancer >\ / > >\ >^' >\ >>' Hiker daveg@mit.edu www.mit.edu/~daveg/ (617)216-4705 dave.golombek@conexant.com www.conexant.com (508)621-0658 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 15:14:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 557B537B479; Tue, 24 Oct 2000 15:14:15 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9OMEEV20728; Tue, 24 Oct 2000 15:14:14 -0700 (PDT) Date: Tue, 24 Oct 2000 15:14:14 -0700 From: Alfred Perlstein To: Matt Dillon Cc: ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness Message-ID: <20001024151414.P28123@fw.wintelcom.net> References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010242010.e9OKAJK19739@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Oct 24, 2000 at 01:10:19PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [001024 13:11] wrote: > Ouch. The original VM code assumed that pages would not often be > ripped out from under the pageadaemon, so it felt free to restart > whenever. I think you are absolutely correct in regards to the > clustering code causing nearby-page ripouts. Yes, it would make sense to me that if you did a sequential write to a file after some time it would be likely that those pages would be put in order on the inactive queue and when cluster written 'next' would be on a different queue as it was written along with the preceeding page. > I don't have much time available, but let me take a crack at the > problem tonight. I don't think we want to add another workaround to > code that already has too many of them. The solution may be > to create a dummy placemarker vm_page_t and to insert it into the pagelist > just after the current page after we've locked it and decided we have > to do something significant to it. We would then be able to pick the > scan up where we left off using the placemarker. > > This would allow us to get rid of the restart code entirely, or at least > devolve it back into its original design (i.e. something that would not > happen very often). Since we already have cache locality of reference for > the list node, the placemarker idea ought to be quite fast. > > I'll take a crack at implementing the openbsd (or was it netbsd?) partial > fsync() code as well, to prevent the update daemon from locking up large > files that have lots of dirty pages for long periods of time. Making the partial fsync would help some people but probably not these folks. The people getting hit by this are Yahoo! boxes, they have giant areas of NOSYNC mmap'd data, the issue is that for them the first scan through the loop always sees dirty data that needs to be written out. I think they also need a _lot_ more than 32 pages cleaned per pass because all of thier pages need laundering. Perhaps if you detected how often the routine was being called you could slowly raise max_page_launder to compensate and lower it after some time without a shortage. Perhaps adding a quarter of 'should_have_laundered' to maxlaunder for a short interval. It might be wise to switch to a 'launder mode' if this sort of usage pattern is detected and figure some better figure to use than 32, I was hoping you'd have some suggestions for a heuristic to detect this along the lines of what you have implemented in bufdaemon. What you could also do is count the amount of pages that could/should have been laundered during the first pass and if it exceeds a certain threshold passing the amount of pages that were free'd via: if (m->object->ref_count == 0) { and: if (m->valid == 0) { and: } else if (m->dirty == 0) { basically if maxlaunder is equal to zero and we miss all those tests you might want to bump up a counter and if it exceeds a threshold immediately start rescanning and double(?) maxlaunder. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 15:32:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CF54A37B4C5; Tue, 24 Oct 2000 15:32:15 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9OMW1X21204; Tue, 24 Oct 2000 15:32:01 -0700 (PDT) (envelope-from dillon) Date: Tue, 24 Oct 2000 15:32:01 -0700 (PDT) From: Matt Dillon Message-Id: <200010242232.e9OMW1X21204@earth.backplane.com> To: Alfred Perlstein Cc: ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> <20001024151414.P28123@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The people getting hit by this are Yahoo! boxes, they have giant areas :of NOSYNC mmap'd data, the issue is that for them the first scan through :the loop always sees dirty data that needs to be written out. I think :they also need a _lot_ more than 32 pages cleaned per pass because all :of thier pages need laundering. : :Perhaps if you detected how often the routine was being called you :could slowly raise max_page_launder to compensate and lower it :after some time without a shortage. Perhaps adding a quarter of :'should_have_laundered' to maxlaunder for a short interval. :.... :It might be wise to switch to a 'launder mode' if this sort of :usage pattern is detected and figure some better figure to use than :32, I was hoping you'd have some suggestions for a heuristic to :detect this along the lines of what you have implemented in bufdaemon. We definitely don't want to increase max_page_launder too much... the problem is that there is a relationship between it and the number of simultanious async writes that can be queued in one go, and that can interfere with normal I/O. But perhaps we should decouple it from the I/O count and have it count clusters instead of pages. i.e. this line: written = vm_pageout_clean(m); if (vp) vput(vp) maxlaunder -= written; Can turn into: if (vm_pageout_clean(m)) --maxlaunder; if (vp) vput(vp); In regards to speeding up paging, perhaps we can implement a heuristic similar to what buf_daemon() does. We could wake the pageout daemon up more often. I'll experiment with it a bit. We certainly have enough statistical information to come up with something good. -Matt :-Alfred : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 15:45: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BA2F837B479; Tue, 24 Oct 2000 15:45:00 -0700 (PDT) Received: from localhost (wwj37n@localhost [127.0.0.1]) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e9OMiv503269; Tue, 24 Oct 2000 18:44:58 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200010242244.e9OMiv503269@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: hackers@FreeBSD.org Cc: n_hibma@FreeBSD.org Subject: Anyone have uhid working and stable? From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 24 Oct 2000 18:44:56 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After just buying a device and attempting to use uhid for a while, I got = a = nice little crash. I can't figure out what's going on, because the clist= = queue seems to be corrupted. Is it valid for a clist to have a non-zero = c_cc and NULL c_cf? I wonder if this is just me, because it seems to hav= e = been provoked with little effort. Maybe I'm missing something as to where exactly the crash occurs -- the l= ine = of code is wrong, and I don't exactly see where the bcopy is coming from = (other than probably q_to_b or uiomove, but I don't know how they can't s= how = up on the stack trace). (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:461 #1 0xc016873f in boot (howto=3D0x100) at ../../kern/kern_shutdown.c:302 #2 0xc0168ae1 in panic (fmt=3D0xc029198f "page fault") at ../../kern/ker= n_shutdown.c:550 #3 0xc024ef2a in trap_fatal (frame=3D0xd02f6cac, eva=3D0x0) at ../../i38= 6/i386/trap.c:951 #4 0xc024ebdd in trap_pfault (frame=3D0xd02f6cac, usermode=3D0x0, eva=3D= 0x0) at ../../i386/i386/trap.c:844 #5 0xc024e77f in trap (frame=3D{tf_fs =3D 0x10, tf_es =3D 0x10, tf_ds =3D= 0x10, tf_edi =3D 0xd02f6d3c, tf_esi =3D 0x0, = tf_ebp =3D 0xd02f6d1c, tf_isp =3D 0xd02f6cd8, tf_ebx =3D 0x4, tf_ed= x =3D 0x80, tf_ecx =3D 0x1, tf_eax =3D 0xd02f6d3c, = tf_trapno =3D 0xc, tf_err =3D 0x0, tf_eip =3D 0xc024d34a, tf_cs =3D= 0x8, tf_eflags =3D 0x10212, tf_esp =3D 0x0, = tf_ss =3D 0xc14f6bb4}) at ../../i386/i386/trap.c:443 #6 0xc024d34a in generic_bcopy () #7 0xc18695e9 in uhid_do_read (sc=3D0xc14f6b80, uio=3D0xd02f6edc, flag=3D= 0x7f0010) at /usr/src/sys/modules/uhid/../../dev/usb/uhid.c:504 #8 0xc1869649 in uhidread () at /usr/src/sys/modules/uhid/../../dev/usb/= uhid.c:513 #9 0xc01a5e29 in spec_read (ap=3D0xd02f6e6c) at ../../miscfs/specfs/spec= _vnops.c:261 #10 0xc02144f8 in ufsspec_read (ap=3D0xd02f6e6c) at ../../ufs/ufs/ufs_vno= ps.c:1802 #11 0xc02149f9 in ufs_vnoperatespec (ap=3D0xd02f6e6c) at ../../ufs/ufs/uf= s_vnops.c:2281 #12 0xc01a2ef4 in vn_read (fp=3D0xc105d080, uio=3D0xd02f6edc, cred=3D0xc1= 1e1280, flags=3D0x0, p=3D0xc7e65380) at vnode_if.h:334 #13 0xc017a1f4 in dofileread (p=3D0xc7e65380, fp=3D0xc105d080, fd=3D0x6, = buf=3D0x8baf180, nbyte=3D0x4, = offset=3D0xffffffffffffffff, flags=3D0x0) at ../../sys/file.h:141 #14 0xc017a0db in read (p=3D0xc7e65380, uap=3D0xd02f6f80) at ../../kern/s= ys_generic.c:110 #15 0xc024f1dd in syscall2 (frame=3D{tf_fs =3D 0x2f, tf_es =3D 0x2f, tf_d= s =3D 0x2f, tf_edi =3D 0x0, tf_esi =3D 0x8bac6e4, = tf_ebp =3D 0x0, tf_isp =3D 0xd02f6fd4, tf_ebx =3D 0x8bac6ec, tf_edx= =3D 0x140, tf_ecx =3D 0x8, tf_eax =3D 0x3, = tf_trapno =3D 0x16, tf_err =3D 0x2, tf_eip =3D 0x28846858, tf_cs =3D= 0x1f, tf_eflags =3D 0x256, tf_esp =3D 0xbfbff6a4, = tf_ss =3D 0x2f}) at ../../i386/i386/trap.c:1150 (kgdb) p ((struct uhid_softc *)$foo->softc)->sc_q = $18 =3D { c_cc =3D 0x1c, = c_cbcount =3D 0x0, = c_cbmax =3D 0xb, = c_cbreserved =3D 0xb, = c_cf =3D 0x0, = c_cl =3D 0xc1178fb0 "=E5=DAD6\t=C4=E6\037zk\036=F3=C4I=E4!\nX=C2\022\21= 2K=A7\233\207=F2S\217\203" } -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 15:50:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4581D37B479; Tue, 24 Oct 2000 15:50:36 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9OMoZY22187; Tue, 24 Oct 2000 15:50:35 -0700 (PDT) Date: Tue, 24 Oct 2000 15:50:35 -0700 From: Alfred Perlstein To: Matt Dillon Cc: ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness Message-ID: <20001024155035.Q28123@fw.wintelcom.net> References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> <20001024151414.P28123@fw.wintelcom.net> <200010242232.e9OMW1X21204@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010242232.e9OMW1X21204@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Oct 24, 2000 at 03:32:01PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [001024 15:32] wrote: > > :The people getting hit by this are Yahoo! boxes, they have giant areas > :of NOSYNC mmap'd data, the issue is that for them the first scan through > :the loop always sees dirty data that needs to be written out. I think > :they also need a _lot_ more than 32 pages cleaned per pass because all > :of thier pages need laundering. > : > :Perhaps if you detected how often the routine was being called you > :could slowly raise max_page_launder to compensate and lower it > :after some time without a shortage. Perhaps adding a quarter of > :'should_have_laundered' to maxlaunder for a short interval. > :.... > :It might be wise to switch to a 'launder mode' if this sort of > :usage pattern is detected and figure some better figure to use than > :32, I was hoping you'd have some suggestions for a heuristic to > :detect this along the lines of what you have implemented in bufdaemon. > > We definitely don't want to increase max_page_launder too much... the > problem is that there is a relationship between it and the number of > simultanious async writes that can be queued in one go, and that can > interfere with normal I/O. But perhaps we should decouple it from the > I/O count and have it count clusters instead of pages. i.e. this line: Ok, now I feel pretty lost, how is there a relationship between max_page_launder and async writes? If increasing max_page_launder increases the amount of async writes, isn't that a good thing? > > written = vm_pageout_clean(m); > if (vp) > vput(vp) > maxlaunder -= written; > > Can turn into: > > if (vm_pageout_clean(m)) > --maxlaunder; > if (vp) > vput(vp); > > In regards to speeding up paging, perhaps we can implement a heuristic > similar to what buf_daemon() does. We could wake the pageout daemon up > more often. I'll experiment with it a bit. We certainly have enough > statistical information to come up with something good. That looks like it would help by ignoring the clustered data which probably got written out pretty quickly and reducing the negative cost/gain to a single page. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 16:16:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id C414937B479 for ; Tue, 24 Oct 2000 16:16:28 -0700 (PDT) Received: from bellatlantic.net (client-151-198-135-33.nnj.dialup.bellatlantic.net [151.198.135.33]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA13558; Tue, 24 Oct 2000 19:16:12 -0400 (EDT) Message-ID: <39F6183B.D78D3D90@bellatlantic.net> Date: Tue, 24 Oct 2000 19:16:11 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Terry Lambert Cc: FengYue , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux References: <200010240739.AAA11051@usr01.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > On Sat, 21 Oct 2000, Frederik Meerwaldt wrote: > > > > ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I > > > > Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really > > doesn't matter IMHO) > > > > Don't forget UNIX is a trademark of Open Group. > > Actually, it's a trademark of USL, licensed to The Open Group. USL is no more, for quite a few years now. I believe that SCO gave the ownership of UNIX trademark to Open Group. > I believe that the The Open Group license is exclusive, so I > don't know what impact Caldera's recent purchase has on their > ability to call Caldera Linux "UNIX". Well, actually Caldera has opposite problem: how to call UnixWare with Linux emulator "Linux". -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 16:39:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 1E97C37B479; Tue, 24 Oct 2000 16:39:16 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9ONd1B21981; Tue, 24 Oct 2000 16:39:01 -0700 (PDT) (envelope-from dillon) Date: Tue, 24 Oct 2000 16:39:01 -0700 (PDT) From: Matt Dillon Message-Id: <200010242339.e9ONd1B21981@earth.backplane.com> To: Alfred Perlstein Cc: ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> <20001024151414.P28123@fw.wintelcom.net> <200010242232.e9OMW1X21204@earth.backplane.com> <20001024155035.Q28123@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Ok, now I feel pretty lost, how is there a relationship between :max_page_launder and async writes? If increasing max_page_launder :increases the amount of async writes, isn't that a good thing? The async writes are competing against the rest of the system for disk resources. While it is ok for an async write to stall, the fact that it will cause other processes read() or page-in (which is nominally synchronous) requests to stall can result in seriously degraded operation for those processes. Piling on the number of async writes running in parallel is not going to improve the performance of page-out daemon, but it will degrade the performance of I/O issued by other processes in the system. The only two reasons the pageout daemon is not doing synchronous writes are: (1) because it can't afford to stall on a slow device (or NFS, etc.) and (2) so it can parallelize I/O across different devices. But since the pageout daemon isn't really all that smart and doesn't track what it does, the whole algorithm devolves into issueing a certain number of asynchronous I/O's all at once.... governed by max_page_launder. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 16:51:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id D684737B479; Tue, 24 Oct 2000 16:51:39 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (lxpxed.lx.ehu.es [158.227.99.207]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id BAA10378; Wed, 25 Oct 2000 01:51:36 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.11.0/8.11.0) with ESMTP id e9ONoL018826; Wed, 25 Oct 2000 01:50:21 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <39F6203D.123CCE95@we.lc.ehu.es> Date: Wed, 25 Oct 2000 01:50:21 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Warner Losh Cc: Will Andrews , Jordan Hubbard , Jeremy Lea , freebsd-hackers@FreeBSD.ORG Subject: Re: Who broke "ls" in FreeBSD? and why? References: <20001024081136.K1604@puck.firepipe.net> <12367.972372237@winston.osd.bsdi.com> <200010241757.LAA17136@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of ls(1)... $ mkdir Arghh $ touch Arghh/{one,two,three} $ ls Arghh one three two $ chmod a-x Arghh $ ls Arghh && echo SUCCESS SUCCESS $ ls -l Arghh && echo SUCCESS SUCCESS ARGGGGHHHHH!!!! :-) This is not the expected behavior. If a directory does not have search permission, but it has read permission, a plain "ls" (or "ls -i") should list its contents, while "ls -l" should fail. And still worse, when ls fails to list the non-searchable directory contents, it does _not_ return an error code. I tried to find the cause of this behavior in the ls source code, but it uses the fts(3) functions, which I am not used to. Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 17:46:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.disney.com (mail11.disney.com [208.246.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 972E437B479 for ; Tue, 24 Oct 2000 17:46:26 -0700 (PDT) Received: from pain.corp.disney.com (pain.corp.disney.com [153.7.231.100]) by mail11.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e9P0xbS14307 for ; Tue, 24 Oct 2000 17:59:37 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for freebsd-hackers@freebsd.org; Tue, 24 Oct 2000 17:47:00 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id RAA15869 for ; Tue, 24 Oct 2000 17:46:24 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com for freebsd-hackers@freebsd.org; Tue, 24 Oct 2000 17:46:23 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation To: freebsd-hackers@freebsd.org Subject: AutoFS on FreeBSD Date: Tue, 24 Oct 2000 17:24:06 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00102417462400.00469@snoopy.fan.fa.disney.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if there is anyone working on AutoFS for FreeBSD. We currently have 4 studios with around 1000 unix systems of all kinds. Currently there are only 2 OSes that do not have autofs, FreeBSD and one that is known for its number crunching capabilties (and those are being phased out of production). Amd will not meet our needs because of the use of sym links. This is why AutoFS was written in the first place. I quote the 1993 USENIX paper on AutoFS (check http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt for the full paper). Symbolic links A single automount daemon can service many mountpoints. At each mountpoint the daemon associates a map, and emulates either a symbolic link (direct map) or a directory of symbolic links (indirect map). The symbolic links point to a directory where the automounter performs NFS mounts - /tmp_mnt or /a. The automounter unmounts what it considers to be "idle" mounts - those that have not been active - or that can be unmounted (not busy). As long as all references to these mounts are made through the daemon mountpoint, the dae- mon can replace the mounts as necessary. However, if a process invokes the getwd() function to obtain the path of the current directory while in an automounted filesystem, it will obtain a "/tmp_mnt/..." path. If this "back door" path is cached and used sometime later, there is no guarantee that the filesystem will still be mounted there. The automounter cannot detect references to empty mount- points unless they are made through the automounter's mountpoint. A common victim of this behavior is the at com- mand. It uses the pwd command to record the current directory so that it can be cd'ed to for subsequent invocation of the script. The symbolic links also confuse users because "/tmp_mnt" frequently appears as a prefix to the current directory. Various workarounds have been proposed for this problem. The most common was for the getwd() function to strip prepended "/tmp_mnt/" from paths. This workaround didn't take into account the effect of the automounter's -M flag that allowed users to specify a directory other than "/tmp_mnt/". It is also questionable whether the semantics of getwd() should be changed this way. The symbolic links present a problem for relative references between separate automounter mounts. For instance given the two directories /home/bob and /home/carol it seems reasonable that Bob should be able to "cd ../carol" but this will fail if Carol's directory isn't already mounted. If no one is using it, how is it looked apon if AutoFS was ported from Linux (with the GPL and that stuff) or would a complete rewrite be better? - JimP -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 17:50: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zilla.emergent.com.au (www.emergent.com.au [203.27.68.30]) by hub.freebsd.org (Postfix) with ESMTP id 741BE37B479 for ; Tue, 24 Oct 2000 17:50:01 -0700 (PDT) Received: from apache2 (tide87.microsoft.com [131.107.3.87]) by zilla.emergent.com.au (8.9.3/8.9.3) with SMTP id LAA03887 for ; Wed, 25 Oct 2000 11:49:59 +1100 (EST) (envelope-from cmoran@emergent.com.au) Message-ID: <016301c03e1d$7a9d8090$4ba63c9d@southpacific.corp.microsoft.com> Reply-To: "Christopher F. Moran" From: "Christopher F. Moran" To: Subject: named changes between 4.0 and 4.1 releases Date: Wed, 25 Oct 2000 11:49:15 +1100 Organization: Emergent Technology MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How can I find what changes occurred to named as shipped on the 4.1 CDs? on 4.0-RELEASE we could do zone transfers with a Windows 2000 DNS, but putting the same config onto a 4.1-RELEASE machine we can't. I'm guessing something changed, and I need to try and figure out what. Cheers, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 17:52:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 3D8D437B65E for ; Tue, 24 Oct 2000 17:52:18 -0700 (PDT) Received: by peitho.fxp.org (Postfix, from userid 1501) id ABE211360E; Tue, 24 Oct 2000 20:52:22 -0400 (EDT) Date: Tue, 24 Oct 2000 20:52:22 -0400 From: Chris Faulhaber To: Jim Pirzyk Cc: freebsd-hackers@freebsd.org Subject: Re: AutoFS on FreeBSD Message-ID: <20001024205222.A99340@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Jim Pirzyk , freebsd-hackers@freebsd.org References: <00102417462400.00469@snoopy.fan.fa.disney.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00102417462400.00469@snoopy.fan.fa.disney.com>; from Jim.Pirzyk@disney.com on Tue, Oct 24, 2000 at 05:24:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 24, 2000 at 05:24:06PM -0700, Jim Pirzyk wrote: > I was wondering if there is anyone working on AutoFS for FreeBSD. We > currently have 4 studios with around 1000 unix systems of all kinds. > Currently there are only 2 OSes that do not have autofs, FreeBSD and one > that is known for its number crunching capabilties (and those are being > phased out of production). Amd will not meet our needs because of the > use of sym links. This is why AutoFS was written in the first place. > I quote the 1993 USENIX paper on AutoFS (check > http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt > for the full paper). > Do you mean amd(8)? AMD(8) FreeBSD System Manager's Manual AMD(8) NAME amd - automatically mount file systems ... DESCRIPTION Amd is a daemon that automatically mounts filesystems whenever a file or directory within that filesystem is accessed. Filesystems are automati- cally unmounted when they appear to be quiescent. ... HISTORY The amd utility first appeared in 4.4BSD. BSD April 19, 1994 3 -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 17:53: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id E69B137B479 for ; Tue, 24 Oct 2000 17:53:02 -0700 (PDT) Received: by peitho.fxp.org (Postfix, from userid 1501) id 074441360E; Tue, 24 Oct 2000 20:53:07 -0400 (EDT) Date: Tue, 24 Oct 2000 20:53:07 -0400 From: Chris Faulhaber To: "Christopher F. Moran" Cc: freebsd-hackers@freebsd.org Subject: Re: named changes between 4.0 and 4.1 releases Message-ID: <20001024205307.B99340@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , "Christopher F. Moran" , freebsd-hackers@freebsd.org References: <016301c03e1d$7a9d8090$4ba63c9d@southpacific.corp.microsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <016301c03e1d$7a9d8090$4ba63c9d@southpacific.corp.microsoft.com>; from cmoran@emergent.com.au on Wed, Oct 25, 2000 at 11:49:15AM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 25, 2000 at 11:49:15AM +1100, Christopher F. Moran wrote: > Hi, > > How can I find what changes occurred to named as shipped on the 4.1 CDs? on > 4.0-RELEASE we could do zone transfers with a Windows 2000 DNS, but putting > the same config onto a 4.1-RELEASE machine we can't. > > I'm guessing something changed, and I need to try and figure out what. > In general, RELNOTES.TXT; although the source is the definitive answer. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 17:55: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 3F93037B4C5 for ; Tue, 24 Oct 2000 17:55:07 -0700 (PDT) Received: (qmail 12218 invoked by uid 1000); 25 Oct 2000 00:55:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Oct 2000 00:55:06 -0000 Date: Tue, 24 Oct 2000 19:55:06 -0500 (CDT) From: Mike Silbersack To: "Christopher F. Moran" Cc: freebsd-hackers@freebsd.org Subject: Re: named changes between 4.0 and 4.1 releases In-Reply-To: <016301c03e1d$7a9d8090$4ba63c9d@southpacific.corp.microsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Oct 2000, Christopher F. Moran wrote: > Hi, > > How can I find what changes occurred to named as shipped on the 4.1 CDs? on > 4.0-RELEASE we could do zone transfers with a Windows 2000 DNS, but putting > the same config onto a 4.1-RELEASE machine we can't. > > I'm guessing something changed, and I need to try and figure out what. 4.0 had 8.2.2-P5, 4.1 has 8.2.3-T5B. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 18:12:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ipperformance.com (unknown [206.225.36.162]) by hub.freebsd.org (Postfix) with ESMTP id 6927C37B479 for ; Tue, 24 Oct 2000 18:12:20 -0700 (PDT) Received: from rbg.ipperf.com (rbg.ipperformance.com [10.1.0.66]) by ipperformance.com (8.9.3/8.9.3) with ESMTP id UAA12999; Tue, 24 Oct 2000 20:11:30 -0500 (CDT) (envelope-from rbg@ipperformance.com) Received: from localhost (localhost [127.0.0.1]) by rbg.ipperf.com (8.9.3/8.9.3) with ESMTP id UAA13780; Tue, 24 Oct 2000 20:12:03 -0500 (CDT) (envelope-from rbg@ipperformance.com) From: rbg@ipperformance.com Date: Tue, 24 Oct 2000 20:12:03 -0500 (CDT) Message-Id: <20001024.201203.23008724.rbg@ipperformance.com> To: jedgar@fxp.org Cc: Jim.Pirzyk@disney.com, freebsd-hackers@FreeBSD.ORG Subject: Re: AutoFS on FreeBSD In-Reply-To: <20001024205222.A99340@peitho.fxp.org> References: <00102417462400.00469@snoopy.fan.fa.disney.com> <20001024205222.A99340@peitho.fxp.org> X-Mailer: Mew version 1.95b43 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, I think he means the kernel VFS layer based AutoFS... ala SUN which was ported to AIX and I'm sure a bunch more platforms.. > On Tue, 24 Oct 2000 20:52:22 -0400 you said: > On Tue, Oct 24, 2000 at 05:24:06PM -0700, Jim Pirzyk wrote: > > I was wondering if there is anyone working on AutoFS for FreeBSD. We > > currently have 4 studios with around 1000 unix systems of all kinds. > > Currently there are only 2 OSes that do not have autofs, FreeBSD and one > > that is known for its number crunching capabilties (and those are being > > phased out of production). Amd will not meet our needs because of the > > use of sym links. This is why AutoFS was written in the first place. > > I quote the 1993 USENIX paper on AutoFS (check > > http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt > > for the full paper). > > > > Do you mean amd(8)? > > AMD(8) FreeBSD System Manager's Manual AMD(8) > > NAME > amd - automatically mount file systems > > ... > > DESCRIPTION > Amd is a daemon that automatically mounts filesystems whenever a file or > directory within that filesystem is accessed. Filesystems are automati- > cally unmounted when they appear to be quiescent. > > ... > > HISTORY > The amd utility first appeared in 4.4BSD. > > BSD April 19, 1994 3 > > > -- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > -------------------------------------------------------- > FreeBSD: 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 _____________________________________________________________ Robert Gordon rbg@ipperf.com IP Performance, Inc Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 18:18:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zilla.emergent.com.au (www.emergent.com.au [203.27.68.30]) by hub.freebsd.org (Postfix) with ESMTP id 2488737B479 for ; Tue, 24 Oct 2000 18:18:08 -0700 (PDT) Received: from apache2 (tide87.microsoft.com [131.107.3.87]) by zilla.emergent.com.au (8.9.3/8.9.3) with SMTP id MAA04004 for ; Wed, 25 Oct 2000 12:18:12 +1100 (EST) (envelope-from cmoran@emergent.com.au) Message-ID: <01b901c03e21$6b446060$4ba63c9d@southpacific.corp.microsoft.com> Reply-To: "Christopher F. Moran" From: "Christopher F. Moran" To: References: Subject: Re: named changes between 4.0 and 4.1 releases Date: Wed, 25 Oct 2000 12:17:27 +1100 Organization: Emergent Technology MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, And for what it's worth there were notes on ISC about a "problem" with IXFR in T5B. T6B fixed it. ----- Original Message ----- From: "Mike Silbersack" To: "Christopher F. Moran" Cc: Sent: Wednesday, October 25, 2000 11:55 AM Subject: Re: named changes between 4.0 and 4.1 releases > > On Wed, 25 Oct 2000, Christopher F. Moran wrote: > > > Hi, > > > > How can I find what changes occurred to named as shipped on the 4.1 CDs? on > > 4.0-RELEASE we could do zone transfers with a Windows 2000 DNS, but putting > > the same config onto a 4.1-RELEASE machine we can't. > > > > I'm guessing something changed, and I need to try and figure out what. > > 4.0 had 8.2.2-P5, 4.1 has 8.2.3-T5B. > > Mike "Silby" Silbersack > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 20:10:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 87A7237B479 for ; Tue, 24 Oct 2000 20:10:38 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id UAA27160; Tue, 24 Oct 2000 20:08:51 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdAAA1kaO50; Tue Oct 24 20:08:45 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id UAA12091; Tue, 24 Oct 2000 20:10:14 -0700 (MST) From: Terry Lambert Message-Id: <200010250310.UAA12091@usr02.primenet.com> Subject: Re: FreeBSD vs. Linux To: babkin@bellatlantic.net (Sergey Babkin) Date: Wed, 25 Oct 2000 03:10:14 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), fengyue@bluerose.windmoon.nu (FengYue), freebsd-hackers@FreeBSD.ORG In-Reply-To: <39F6183B.D78D3D90@bellatlantic.net> from "Sergey Babkin" at Oct 24, 2000 07:16:11 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Don't forget UNIX is a trademark of Open Group. > > > > Actually, it's a trademark of USL, licensed to The Open Group. > > USL is no more, for quite a few years now. I believe that SCO > gave the ownership of UNIX trademark to Open Group. The WIPO database shows a GB registration fro X/Open Company Limited. Application numbers are 000227991 and 000431569. This is from the Community Trade Mark Consulatation Service (CTM-Online search engine): http://oami.eu.int/search/trademark/la/en_tm_search.cfm The US-PTO search engine, Trademark Electronic Search System (TESS), appears to be dead right now; it's normally at: The last time I searched there, it was still owned by USL and exclusively licensed. The Canadian online database is still up at: And a search there yields: REGISTRANT: AMERICAN TELEPHONE AND TELEGRAPH COMPANY, 550 MADISON AVENUE, NEW YORK, NEW YORK 10022, UNITED STATES OF AMERICA CURRENT OWNER: X/Open Company Limited Apex Plaza, Forbury Road, Reading, Berkshire, RG1 1AX, UNITED KINGDOM REPRESENTATIVE FOR SERVICE: SHAPIRO, COHEN P.O. BOX 3440, STATION D 112 KENT STREET, SUITE 2001 OTTAWA ONTARIO K1P 6P1 INTERESTED PARTIES OLD OWNER NOVELL INC., A DELAWARE CORPORATION, 1555 NORTH TECHNOLOGY WAY, OREM UTAH 84057, UNITED STATES OF AMERICA In the U.S., I'm still not sure; the applicable U.S. law implies that there are problems with transfer of ownership, just like transfer of ownership of patents and copyrights (in the U.S., a patent or copyright can not be transferred, only assigned, since there are time limits who clock would otherwise reset, especially for Copyright). In any case, it looks like use of the UNIX trademark is still subject to testing and certification, per: http://www.opengroup.org/testing/checklist/ It's interesting that they require CDE certification, if you want to use the UNIX trademark in association with a workstation, and that you must support their Internet Server Product Registration checklist to use it in association with a server. As an intersting aside, here are registered products by company (note that Caldera isn't lists -- yet, anyway): http://www.opengroup.org/regproducts/company.htm Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 20:59:13 2000 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 6170C37B479 for ; Tue, 24 Oct 2000 20:59:10 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e9P3x3X87744; Wed, 25 Oct 2000 13:29:03 +0930 (CST) (envelope-from grog) Date: Wed, 25 Oct 2000 13:29:03 +0930 From: Greg Lehey To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Determining CPU on SMP box Message-ID: <20001025132903.B87564@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from charrer@alacritech.com on Tue, Oct 24, 2000 at 07:37:12AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 24 October 2000 at 7:37:12 -0400, Christopher Harrer wrote: > Hello All, > > Is there a way to determine which CPU I'm currently executing on in a SMP > box? I've found references to proc->p_oncpu, but I'm not sure if this is > the best way to determine where I'm executing. I'd like to be able to > "trace" various actions within my driver and one of the fields I want to > keep track of is what CPU I'm executing on. Which version of FreeBSD? 5-CURRENT has the ktr functions, which you could use for your tracing. They include CPU information. Unfortunately we don't have a man page yet. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 24 21:42: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tdl.com (pm4-39.tdl.com [206.180.234.39]) by hub.freebsd.org (Postfix) with ESMTP id 3351537B479 for ; Tue, 24 Oct 2000 21:41:59 -0700 (PDT) Received: from localhost (wdr@localhost) by tdl.com (8.11.0/8.11.0) with ESMTP id e9P4hWA02852 for ; Tue, 24 Oct 2000 21:43:32 -0700 (PDT) (envelope-from wdr@saffron.wraltd) Date: Tue, 24 Oct 2000 21:43:32 -0700 (PDT) From: William Richard To: hackers@freebsd.org Subject: Interval Timer Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Hackers. This is my first post to -hackers, so forgive me if I'm asking in the wrong list. I've been writing a little program to wait for a specified length of time, then beep on the terminal and exit. I originally made the process wait the specified number of seconds with a call to sleep(3). Once invoked, the program would sit there, not give any indication that it was running, until the interval had passed and it beeped. So I wrote a cheap little twirling baton routine and stuck it into my program. Obviously, the baton won't twirl if the process is sleep(3)ing, so I delved into the manual and came across the setitimer(2) system call. Setitimer takes three arguments: a #define from time.h specifying whether the timer should run in real time, process virtual time, or on the profiling timer; a pointer to a struct itimerval (which contains two struct timevals) which indicates how long the timer should run for and what to do when it runs out; and a pointer to a struct itimerval to store the old value of the timer before setitimer resets it. When the interval timer expires, it sends the process a SIGALRM, the default action for which is to terminate the process. I rewrote my timer program to use setitimer, defining a signal handler for SIGALRM with signal(3), and it worked as I expected. In this version, the process called setitimer, then pause(3)ed until the process received a signal and invoked the signal handler (which beeped the terminal and exited). I then rewrote the program again to include the twirling baton, and this is where things went awry. The baton is a for loop, which putchars an element of the baton, flushes the stdout, write a backspace, and tests to see if we're at the end of the array which stores the -\|/ of the baton and if so, reset the for loop iterator. After adding the for loop, the interval timer I established with setitimer stopped working. I removed the fflush and the backspace, and couldn't get it to work. I can kill -ALRM the process and make it invoke the signal handler, but the setitimer interval timer isn't sending a SIGALRM. I rewrote the program again to use alarm(3) instead of setitimer, and the program works as expected. I am confused as to why setitimer didn't work in this case, but alarm did. The question is: I would like to know the reason why doesn't setitimer work when I invoke this for loop? If someone knows, or at least can give me a pointer to where I can start looking for the answer, that would be great. Maybe I can add something to the setitimer man page to document this gotcha. I can provide source code, either in the list or on a Web page, if it would help anyone so kind as to answer my question. Cheers, William Richard wdr@tdl.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 0: 9:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5]) by hub.freebsd.org (Postfix) with ESMTP id D11E537B479 for ; Wed, 25 Oct 2000 00:09:30 -0700 (PDT) Received: from [206.246.249.217] (helo=daydream) by wilma.widomaker.com with esmtp (Exim 3.16 #2) id 13oKge-0003qK-00; Wed, 25 Oct 2000 03:09:25 -0400 Received: from shannon by daydream with local (Exim 3.12 #1 (Debian)) id 13nxne-0000XG-00; Tue, 24 Oct 2000 02:43:06 -0400 Date: Tue, 24 Oct 2000 02:43:06 -0400 From: Shannon Hendrix To: Sergey Babkin Cc: Frederik Meerwaldt , "phpStop.com" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux Message-ID: <20001024024305.A1466@widomaker.com> Mail-Followup-To: Sergey Babkin , Frederik Meerwaldt , "phpStop.com" , freebsd-hackers@freebsd.org References: <39F3609E.83C02B3E@bellatlantic.net> <39F38893.6A8204A@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F38893.6A8204A@bellatlantic.net>; from babkin@bellatlantic.net on Sun, Oct 22, 2000 at 08:38:43PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 08:38:43PM -0400, Sergey Babkin wrote: > By the way, speaking of that, things in FreeBSD tend to be more > synchronous with docs than in Linux. Also FreeBSD has much better > backwards compatibility (though alas still not as good as commercial > systems). In Linux the applications tend to break and require > recompilation when the kernel is upgraded to the next > second-digit version. Mostly, that is only for system utilities. Few applications care about the kernel, and I run plenty of old applications with just a compatbility library installed, just like I do on FreeBSD. I dislike the package systems like rpm and debian when they keep me from running different versions of a library unless I force it. Some dependencies just don't make any sense. The FreeBSD situation is better, but no UNIX is exactly library heaven once you get away from the basics (C, kernel, POSIX). Graphics and sound are still alphabet soup. Hopefully that will settle down in time. -- "Those who trade liberty for security will have neither -- (??)" shannon @ w i d o m a k e r . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 0: 9:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5]) by hub.freebsd.org (Postfix) with ESMTP id 4543F37B479 for ; Wed, 25 Oct 2000 00:09:38 -0700 (PDT) Received: from [206.246.249.217] (helo=daydream) by wilma.widomaker.com with esmtp (Exim 3.16 #2) id 13oKga-0003pl-00; Wed, 25 Oct 2000 03:09:21 -0400 Received: from shannon by daydream with local (Exim 3.12 #1 (Debian)) id 13nyBw-0000ha-00; Tue, 24 Oct 2000 03:08:12 -0400 Date: Tue, 24 Oct 2000 03:08:12 -0400 From: Shannon Hendrix To: FengYue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux Message-ID: <20001024030811.B1466@widomaker.com> Mail-Followup-To: FengYue , freebsd-hackers@FreeBSD.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 fengyue@bluerose.windmoon.nu on Sat, Oct 21, 2000 at 05:31:50PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 21, 2000 at 05:31:50PM -0700, FengYue wrote: > > On Sat, 21 Oct 2000, Frederik Meerwaldt wrote: > > ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I > > Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really > doesn't matter IMHO) > > Don't forget UNIX is a trademark of Open Group. Don? :) Serously, BSD is UNIX. Wether or not TOG likes that is irrelevant. The legal distinction is not the important one. -- "The grieving lords take ship. With these our very souls pass | | | overseas." -- Exile | | | ________________________________________________________________ / | \ s h a n n o n @ w i d o m a k e r . c o m _/ | \_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 1:38:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 1CF6437B479 for ; Wed, 25 Oct 2000 01:38:10 -0700 (PDT) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 13oM3a-0002Sp-00; Wed, 25 Oct 2000 09:37:10 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 13oM3Z-0002NZ-00; Wed, 25 Oct 2000 09:37:09 +0100 Message-ID: <39F69BB5.7861C480@dante.org.uk> Date: Wed, 25 Oct 2000 09:37:09 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: rbg@ipperformance.com Cc: jedgar@fxp.org, Jim.Pirzyk@disney.com, freebsd-hackers@FreeBSD.ORG Subject: Re: AutoFS on FreeBSD References: <00102417462400.00469@snoopy.fan.fa.disney.com> <20001024205222.A99340@peitho.fxp.org> <20001024.201203.23008724.rbg@ipperformance.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rbg@ipperformance.com wrote: > No, I think he means the kernel VFS layer based AutoFS... ala SUN > which was ported to AIX and I'm sure a bunch more platforms.. > Besides of shell's uglish look of paths resolved from symbolic links created by AMD (like /.a/net/my_server/home/joy as my home directory in bash on my workstation), what is the advantage of doing this in kernel? -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 2:10:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 0631237B4C5 for ; Wed, 25 Oct 2000 02:10:16 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id CAA22410; Wed, 25 Oct 2000 02:10:43 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp05.primenet.com, id smtpdAAAmNaGVR; Wed Oct 25 02:10:35 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id CAA18466; Wed, 25 Oct 2000 02:10:05 -0700 (MST) From: Terry Lambert Message-Id: <200010250910.CAA18466@usr02.primenet.com> Subject: Re: PCI Device Remapping To: daveg@MIT.EDU (David D Golombek) Date: Wed, 25 Oct 2000 09:10:05 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "David D Golombek" at Oct 24, 2000 03:40:46 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm now > trying to get the card to do DMA to other PCI cards, and have found a > bug in our chip. Basically, the high bit of the address on PCI > transfers gets dropped. This means that the chip can't address PCI > memory physical addresses over 0x7FFFFFFF. Big problem, since the > BIOS on our computers maps PCI device memory from 0xFFFF0000 downward. A gross hack that Eagle used on NE1000 cards was to require that an even number of bytes be transferred. You can do this hack yourself by swapping the pinouts on the chip, if it's simply impossible to go back to fab on it. You will need to rearrange the input to the mapping register at the same time. Pretty much ECN time, though. Alternately, if you have a flashable BIOS, you can hack the BIOS to start mapping at 0x7fffffff instead. This should be pretty trivial, if you have something like a copy of Sourcer lying around, since it can take your BIOS as input and output a program (fully commented!) that, when assembled, will result in the same BIOS being generated. Flip the start bit and... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 2:48: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 06F9237B479 for ; Wed, 25 Oct 2000 02:47:59 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id CAA27930; Wed, 25 Oct 2000 02:48:25 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp05.primenet.com, id smtpdAAAiya4H2; Wed Oct 25 02:48:19 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id CAA18929; Wed, 25 Oct 2000 02:47:50 -0700 (MST) From: Terry Lambert Message-Id: <200010250947.CAA18929@usr02.primenet.com> Subject: Re: AutoFS on FreeBSD To: Jim.Pirzyk@disney.com (Jim Pirzyk) Date: Wed, 25 Oct 2000 09:47:50 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <00102417462400.00469@snoopy.fan.fa.disney.com> from "Jim Pirzyk" at Oct 24, 2000 05:24:06 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was wondering if there is anyone working on AutoFS for FreeBSD. We > currently have 4 studios with around 1000 unix systems of all kinds. > Currently there are only 2 OSes that do not have autofs, FreeBSD and one > that is known for its number crunching capabilties (and those are being > phased out of production). Amd will not meet our needs because of the > use of sym links. This is why AutoFS was written in the first place. > I quote the 1993 USENIX paper on AutoFS (check > http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt > for the full paper). [ ... AutoFS Introduction ... ] [ ... NFS automounter "problems" ... ] > However, if a process invokes the getwd() function to obtain the path > of the current directory while in an automounted filesystem, it will > obtain a "/tmp_mnt/..." path. If this "back door" path is cached and > used sometime later, there is no guarantee that the filesystem will > still be mounted there. I think that the attempt to change to the directory should be delayed until the event. This will cause the use of the forward path, which, if there is a timeout, will reinvoke the automounter, correctly. > A common victim of this behavior is the at command. It uses the pwd > command to record the current directory so that it can be cd'ed to > for subsequent invocation of the script. I think this is a bug in the "at" command. If you want, I can provide patches which implement the behaviour using "open(2)" and "fchdir(2)", instead of recording the "cwd path". Alternately, I can provide patches to make it use the command line path instead, using evaluation of the path not involving "readlink(2)". I would personally prefer the "fchdir(2)" method, since the "open(2)" will keep the mount active, so it isn't allowed to time out. > The symbolic links also confuse users [...] This argument is an attempt to pile on; not a very good one. As long as the software does what it's supposed to do, user's don't have to be able to understand it to make it work. Look how many people drive cars, but don't understand how they operate or program C, with no understanding of the assembly language the compiler will produce as a result. > If no one is using it, how is it looked apon if AutoFS was ported from > Linux (with the GPL and that stuff) or would a complete rewrite be > better? A complete rewrite would be required for the AutoFS to be included in the system by default, if it were found to be generally desired. I think your problem can probably be solved a lot of ways; if the Linux AutoFS is a module, you are aware that you can use Linux FS modules under FreeBSD, right? If the problem is the "at" problem, I'd suggest that a simple change to the problem software would also fix the problem. At worst, I'd suggest use of static maps, distributed via NIS, to resolve the problem. I think that, given the way BSD covers mount points, the other issues that were raised as problems are really no longer problems, on modern systems. The threading is not an issue, and neither is the map change. The performance issues for the link traversal are really trivial (particularly when you consider that the "get current directory" argument means that the symlinks were never getting traversed, other than the very first reference). I think the "in place mapping" failure that they reported in their implementation would never be an issue under BSD. Is this a requirement that you be able to support "standard" AutoFS mount maps, or is there an issue with the automounter where you are actually experiencing a problem which would be resolved by AutoFS and only AutoFS? In any case, you *could* use the Linux AutoFS module with FreeBSD; there is a port which supports Linux FS modules loaded into user space, but without a clarification of why you want/need an AutoFS, I don't think anyone can tell you whether or not that would be an appropriate technology... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 2:50:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id CF4B037B479 for ; Wed, 25 Oct 2000 02:50:35 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA12408; Wed, 25 Oct 2000 11:49:48 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.11.0/8.11.0) with ESMTP id e9P9n1019174; Wed, 25 Oct 2000 11:49:01 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <39F6AC8D.542149FC@we.lc.ehu.es> Date: Wed, 25 Oct 2000 11:49:01 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Sean Lutner , hackers@FreeBSD.org Subject: Re: Who broke "ls" in FreeBSD? and why? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Lutner wrote: > > I may just be being naive here, which is why I took this off the list. I > don't understand how a directory that is a-x will not let you run ls -l on > it. > > (48) sean@h0050dab9d058: ~ $ ls test > one three two > (49) sean@h0050dab9d058: ~ $ ls -l test/ > total 0 > -rw-r--r-- 1 sean sean 0 Oct 24 19:59 one > -rw-r--r-- 1 sean sean 0 Oct 24 19:59 three > -rw-r--r-- 1 sean sean 0 Oct 24 19:59 two > (50) sean@h0050dab9d058: ~ $ chmod a-x test/ > (51) sean@h0050dab9d058: ~ $ ls test/ > one three two > (52) sean@h0050dab9d058: ~ $ ls -l test/ > (53) sean@h0050dab9d058: ~ $ > > As you can see, after changing the permissions, you cannot run ls -l as > you could before. Perhaps I don't have the broken version, or there is > something I am missing. At any rate, a better understanding would be nice. > If a directory does not have search permission, the i-node contents of each of its entries cannot be examined. Under these circumstances, the directory listing "per se" does not fail, but the information requested cannot be shown. For example, in Solaris (and in SunOS 4.x): $ ls -ld Test/ drw-r----- 2 jose lsi 512 oct 25 11:13 Test/ $ ls Test 1 2 3 $ ls -i Test 288799 1 288800 2 288801 3 $ ls -l Test Test/1: Permission denied Test/2: Permission denied Test/3: Permission denied total 0 $ Anyway, I found something interesting: the bash shell is involved in some way: Using bash: $ mkdir Test $ touch Test/{1,2,3} $ chmod a-x Test $ ls Test && echo SUCCESS SUCCESS <------ WRONG!! $ /bin/ls Test && echo SUCCESS 1 2 3 <------ This works as expected (?!?!??) SUCCESS $ type ls ls is hashed (/bin/ls) Using [t]csh: $ csh %ls -ld Test drw------- 2 jose lsi 512 25 oct 10:49 Test %ls Test 1 2 3 <------ This works as expected %ls -i Test <------ WRONG!! %which ls /bin/ls % Using both bash and csh, 'ls -i' and 'ls -l' give nothing and don't return any error when the directory does not have search permission. "ls -i" should work, since getdirentries(2) only requires that the directory must be opened for reading. The behavior of "ls -l" may be a subject for discussion. Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 3: 6: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 8A5E337B479 for ; Wed, 25 Oct 2000 03:06:03 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id DAA13038; Wed, 25 Oct 2000 03:02:51 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpdAAAdYaioz; Wed Oct 25 03:02:49 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id DAA19164; Wed, 25 Oct 2000 03:05:43 -0700 (MST) From: Terry Lambert Message-Id: <200010251005.DAA19164@usr02.primenet.com> Subject: More UNIX trademark trivia To: tlambert@primenet.com (Terry Lambert) Date: Wed, 25 Oct 2000 10:05:43 +0000 (GMT) Cc: babkin@bellatlantic.net (Sergey Babkin), tlambert@primenet.com (Terry Lambert), fengyue@bluerose.windmoon.nu (FengYue), freebsd-hackers@FreeBSD.ORG In-Reply-To: <200010250310.UAA12091@usr02.primenet.com> from "Terry Lambert" at Oct 25, 2000 03:10:14 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The US-PTO search engine, Trademark Electronic Search System (TESS), > appears to be dead right now; it's normally at: > > > > The last time I searched there, it was still owned by USL and > exclusively licensed. It's back. It shows the following: sn 74433402 rn 1845474 UNIXWARE; owner: registered USL; assigned SCO sn 73544900 rn 1392203 UNIX; owner: registered AT&T; assigned USL sn 73537419 rn 1390593 UNIX; owner: registered AT&T; assigned USL This doesn't include licensing, which, as I said before, is to X/Open (per X/Open). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 3:13: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id D9F1837B479; Wed, 25 Oct 2000 03:13:02 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id DAA16635; Wed, 25 Oct 2000 03:09:54 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpdAAANUaqxG; Wed Oct 25 03:09:47 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id DAA19288; Wed, 25 Oct 2000 03:12:53 -0700 (MST) From: Terry Lambert Message-Id: <200010251012.DAA19288@usr02.primenet.com> Subject: Re: vm_pageout_scan badness To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 25 Oct 2000 10:12:53 +0000 (GMT) Cc: dillon@earth.backplane.com (Matt Dillon), ps@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <20001024151414.P28123@fw.wintelcom.net> from "Alfred Perlstein" at Oct 24, 2000 03:14:14 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'll take a crack at implementing the openbsd (or was it netbsd?) partial > > fsync() code as well, to prevent the update daemon from locking up large > > files that have lots of dirty pages for long periods of time. > > Making the partial fsync would help some people but probably not > these folks. I think this would be better handled as a per file working set quota, which could not be exceeded, unless changed by root. Consider that a file with a huge number of pages outstanding should probably be stealing pages from its own LRU list, and not the system, to satisfy new requests. This is particularly true of files that are demanding resources on a resource-bound system. > The people getting hit by this are Yahoo! boxes, they have giant areas > of NOSYNC mmap'd data, the issue is that for them the first scan through > the loop always sees dirty data that needs to be written out. I think > they also need a _lot_ more than 32 pages cleaned per pass because all > of thier pages need laundering. First principles? What are they doing, such that this situation arises in the first place? Having a clue to the problem they are trying to resolve, which causes this problem as a side effect, would both help to clarify if there were a better soloution for them, as well as what FreeBSD should potentially act like they were asking for instead, when/if the situation arose. > It might be wise to switch to a 'launder mode' if this sort of > usage pattern is detected and figure some better figure to use than > 32, I was hoping you'd have some suggestions for a heuristic to > detect this along the lines of what you have implemented in bufdaemon. This is kind of evil. You could do low and high watermarking, as you suggest, but without any idea of the queue retention time to expect, and how bursty the situation is, there's no way to pick an appropriate algorithm. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 3:22:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 82B9637B479 for ; Wed, 25 Oct 2000 03:22:34 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id DAA04604; Wed, 25 Oct 2000 03:23:01 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp05.primenet.com, id smtpdAAAHEaa_i; Wed Oct 25 03:22:52 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id DAA19445; Wed, 25 Oct 2000 03:22:23 -0700 (MST) From: Terry Lambert Message-Id: <200010251022.DAA19445@usr02.primenet.com> Subject: Re: Solaris 8's split cache To: float@firedrake.org (void) Date: Wed, 25 Oct 2000 10:22:23 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <20001024193724.A8443@firedrake.org> from "void" at Oct 24, 2000 07:37:24 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > http://sunsolve.Sun.COM/pub-cgi/show.pl?target=content/content8#cyclical > > BSD doesn't do anything like this (distinguishing between instructions > and data in the VM cache), does it? Should it? I keep thinking I'm going insane... Is this true? Have they invented the split VM and buffer cache? Or did they invent a "working set quota for all file system data"? Guess you couldn't patent it, if you called it that... 8-p Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 3:32: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heechee.tobez.org (238.adsl0.ryv.worldonline.dk [213.237.10.238]) by hub.freebsd.org (Postfix) with ESMTP id ED17637B479; Wed, 25 Oct 2000 03:32:00 -0700 (PDT) Received: by heechee.tobez.org (Postfix, from userid 1001) id 5D3EC54CC; Wed, 25 Oct 2000 12:31:54 +0200 (CEST) Date: Wed, 25 Oct 2000 12:31:54 +0200 From: Anton Berezin To: Matt Dillon Cc: Alfred Perlstein , ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness Message-ID: <20001025123154.A56298@heechee.tobez.org> References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010242010.e9OKAJK19739@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Oct 24, 2000 at 01:10:19PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 24, 2000 at 01:10:19PM -0700, Matt Dillon wrote: > Ouch. The original VM code assumed that pages would not often be > ripped out from under the pageadaemon, so it felt free to restart > whenever. I think you are absolutely correct in regards to the > clustering code causing nearby-page ripouts. > > I don't have much time available, but let me take a crack at the > problem tonight. While you are at it, would you care and have a look at PR19672. It seems to be at least remotely relevant. ;-) > I don't think we want to add another workaround to code that > already has too many of them. The solution may be to create a > dummy placemarker vm_page_t and to insert it into the pagelist > just after the current page after we've locked it and decided we > have to do something significant to it. We would then be able to > pick the scan up where we left off using the placemarker. > > This would allow us to get rid of the restart code entirely, or at > least devolve it back into its original design (i.e. something > that would not happen very often). Since we already have cache > locality of reference for the list node, the placemarker idea > ought to be quite fast. > > I'll take a crack at implementing the openbsd (or was it netbsd?) > partial fsync() code as well, to prevent the update daemon from > locking up large files that have lots of dirty pages for long > periods of time. Cheers, %Anton. -- and would be a nice addition to HTML specification. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 5:49: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 7C4F737B479; Wed, 25 Oct 2000 05:49:00 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id ezojaaaa for ; Wed, 25 Oct 2000 05:46:44 -0700 From: "Christopher Harrer" To: "Mike Smith" Cc: "Freebsd-Hackers" Subject: RE: Determining CPU on SMP box Date: Wed, 25 Oct 2000 08:47:00 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: <200010242048.e9OKmPh02075@mass.osd.bsdi.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, Thanks for the response. As I said, the reason for this is diagnostic information. Especially wanting to know if I got reshceduled on another CPU. I'll look for this cpuid. Chris -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Mike Smith Sent: Tuesday, October 24, 2000 4:48 PM To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Determining CPU on SMP box > Is there a way to determine which CPU I'm currently executing on in a SMP > box? I've found references to proc->p_oncpu, but I'm not sure if this is > the best way to determine where I'm executing. I'd like to be able to > "trace" various actions within my driver and one of the fields I want to > keep track of is what CPU I'm executing on. There's a per-CPU variable 'cpuid' (at least, there used to be) that you could use for this. However, it's kinda pointless working out what CPU you're on, since you're liable to be rescheduled onto another CPU if an interrupt occurs... -- ... 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 5:55: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id AD43737B4C5 for ; Wed, 25 Oct 2000 05:55:02 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id kzojaaaa for ; Wed, 25 Oct 2000 05:52:46 -0700 From: "Christopher Harrer" To: "Greg Lehey" Cc: "Freebsd-Hackers" Subject: RE: Determining CPU on SMP box Date: Wed, 25 Oct 2000 08:53:03 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: <20001025132903.B87564@wantadilla.lemis.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using version 4.1. Thanks, Chris -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Greg Lehey Sent: Tuesday, October 24, 2000 11:59 PM To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Determining CPU on SMP box On Tuesday, 24 October 2000 at 7:37:12 -0400, Christopher Harrer wrote: > Hello All, > > Is there a way to determine which CPU I'm currently executing on in a SMP > box? I've found references to proc->p_oncpu, but I'm not sure if this is > the best way to determine where I'm executing. I'd like to be able to > "trace" various actions within my driver and one of the fields I want to > keep track of is what CPU I'm executing on. Which version of FreeBSD? 5-CURRENT has the ktr functions, which you could use for your tracing. They include CPU information. Unfortunately we don't have a man page yet. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 6:26:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id C803237B4C5 for ; Wed, 25 Oct 2000 06:26:36 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id UAA43944; Wed, 25 Oct 2000 20:22:55 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 25 Oct 2000 20:22:55 +0700 (NSS) From: Max Khon To: Terry Lambert Cc: Jim Pirzyk , freebsd-hackers@FreeBSD.ORG Subject: Re: AutoFS on FreeBSD In-Reply-To: <200010250947.CAA18929@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 25 Oct 2000, Terry Lambert wrote: > In any case, you *could* use the Linux AutoFS module with FreeBSD; > there is a port which supports Linux FS modules loaded into user > space which one? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 7:42:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 11BEE37B479; Wed, 25 Oct 2000 07:42:33 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 8CC1D193DF; Wed, 25 Oct 2000 09:42:31 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id e9PEgV415639; Wed, 25 Oct 2000 09:42:31 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Wed, 25 Oct 2000 09:42:31 -0500 From: "Jacques A. Vidrine" To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: call for testers: nsswitch + dynamic linking Message-ID: <20001025094231.A15563@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , freebsd-current@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 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Please follow-up to only one list] Hello, I need more testers for the following! nsswitch extends the C library so that arbitrary sources may be consulted by database routines such as getpwent, gethostbyname, and so on. This implementation was based on NetBSD's implementation. I have enhanced it to make the interfaces thread safe, and to provide support for dynamically loaded nsswitch modules. Patches for 4-STABLE and 5-CURRENT are at: http://www.nectar.com/freebsd/nsswitch. Also available there are patches for PADL.COM's nss_ldap so that it may be used with FreeBSD. Incidentally this also adds reentrant versions of common routines such as getpwnam_r. Note that routines that eventually call the resolver are only as thread safe as the resolver -- i.e. not really. Please contact me with any comments/bugs/patches. Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 7:54: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id 262A637B479; Wed, 25 Oct 2000 07:54:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.0/8.11.1) with ESMTP id e9PEsY420595; Wed, 25 Oct 2000 10:54:34 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Wed, 25 Oct 2000 10:54:34 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Marko Ruban Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <39F49ECC.AF8CDFD2@dppl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Marko Ruban wrote: > Summary of the problem: > > Can't assign cable modem gateway (10.17.56.12) to interface > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > I called RCN (my cable provider) and asked them to give me > a gateway on the same subnet; they said they "don't do that". man dhcp.conf(5). From what I saw there, "option routers" and "option routes" are what you need to stick into your dhclient.conf. Can you add routes by hand and make it work? If not, then even the above won't help you. > Part of solution: > > I set an alias for ed0 to 10.17.0.1 and it accepted the cable > modem gateway as is. BUT, the packets are sent out with source > address (10.17.0.1) responses to which, I suspect, gateway doesn't > know how to route. I would imagine you're right. > Question: how can I have an alias of 10.17.0.1 and send out all > packets with source address set to 208.59.162.242 (the IP > that is actually assigned to the interface - not alias). natd? > P.S. Alternately, how can I force the system to allow a gateway > that is on a different subnet (like windows allows that). Who > can I turn to for help ? I'm not a routing guru, but the guy in the next office is. I'll ask him. (tromp, tromp, tromp) The answer is this: run routed in verbose or debug mode, or listen with rip, or some other network sniffer (you could even ping the network and see who answers). You should have a local router within 30 seconds. Failing that, there have been a lot of other good suggestions, among which probably the best is to switch to DSL. :-/ -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 8: 7:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 23D6F37B479 for ; Wed, 25 Oct 2000 08:07:42 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 5BBFD193DF for ; Wed, 25 Oct 2000 10:07:41 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id e9PF7fB15739 for freebsd-hackers@freebsd.org; Wed, 25 Oct 2000 10:07:41 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Wed, 25 Oct 2000 10:07:41 -0500 From: "Jacques A. Vidrine" To: freebsd-hackers@freebsd.org Subject: symbols seek home Message-ID: <20001025100741.A15732@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In what header file could GETGR_R_SIZE_MAX and GETPW_R_SIZE_MAX live? These are defines that can be used to specify the sizes of the buffers needed for getpw*_r/getgr*_r. I'd like to put them in unistd.h, and add _SC_GETGR_R_SIZE_MAX/ _SC_GETPW_R_SIZE_MAX as well (for use with sysconf), but I thought I'd ask around first. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 8:43:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id BB41A37B4D7 for ; Wed, 25 Oct 2000 08:43:07 -0700 (PDT) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e9PFgqR26011 for ; Wed, 25 Oct 2000 08:42:52 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for freebsd-hackers@FreeBSD.ORG; Wed, 25 Oct 2000 08:42:37 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id IAA08331 for ; Wed, 25 Oct 2000 08:42:00 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com; Wed, 25 Oct 2000 08:41:59 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation To: rbg@ipperformance.com, jedgar@fxp.org Subject: Re: AutoFS on FreeBSD Date: Wed, 25 Oct 2000 08:41:31 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: Jim.Pirzyk@disney.com, freebsd-hackers@FreeBSD.ORG References: <00102417462400.00469@snoopy.fan.fa.disney.com> <20001024205222.A99340@peitho.fxp.org> <20001024.201203.23008724.rbg@ipperformance.com> In-Reply-To: <20001024.201203.23008724.rbg@ipperformance.com> MIME-Version: 1.0 Message-Id: <00102508420101.01988@snoopy.fan.fa.disney.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Oct 2000, rbg@ipperformance.com wrote: > No, I think he means the kernel VFS layer based AutoFS... ala SUN > which was ported to AIX and I'm sure a bunch more platforms.. SGI and Linux too. - JimP > > > On Tue, 24 Oct 2000 20:52:22 -0400 you said: > > On Tue, Oct 24, 2000 at 05:24:06PM -0700, Jim Pirzyk wrote: > > > I was wondering if there is anyone working on AutoFS for FreeBSD. We > > > currently have 4 studios with around 1000 unix systems of all kinds. > > > Currently there are only 2 OSes that do not have autofs, FreeBSD and one > > > that is known for its number crunching capabilties (and those are being > > > phased out of production). Amd will not meet our needs because of the > > > use of sym links. This is why AutoFS was written in the first place. > > > I quote the 1993 USENIX paper on AutoFS (check > > > http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt > > > for the full paper). > > > > > > > Do you mean amd(8)? > > > > AMD(8) FreeBSD System Manager's Manual AMD(8) > > > > NAME > > amd - automatically mount file systems > > > > ... > > > > DESCRIPTION > > Amd is a daemon that automatically mounts filesystems whenever a file or > > directory within that filesystem is accessed. Filesystems are automati- > > cally unmounted when they appear to be quiescent. > > > > ... > > > > HISTORY > > The amd utility first appeared in 4.4BSD. > > > > BSD April 19, 1994 3 > > > > > > -- > > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > > -------------------------------------------------------- > > FreeBSD: 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 > _____________________________________________________________ > Robert Gordon rbg@ipperf.com > IP Performance, Inc > Austin, Texas. -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 8:57:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id DB49037B479 for ; Wed, 25 Oct 2000 08:57:42 -0700 (PDT) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e9PFvfR06905 for ; Wed, 25 Oct 2000 08:57:41 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for freebsd-hackers@FreeBSD.ORG; Wed, 25 Oct 2000 08:58:16 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id IAA10201 for ; Wed, 25 Oct 2000 08:57:39 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com; Wed, 25 Oct 2000 08:57:38 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation To: Konstantin Chuguev , rbg@ipperformance.com Subject: Re: AutoFS on FreeBSD Date: Wed, 25 Oct 2000 08:53:21 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: jedgar@fxp.org, Jim.Pirzyk@disney.com, freebsd-hackers@FreeBSD.ORG References: <00102417462400.00469@snoopy.fan.fa.disney.com> <20001024.201203.23008724.rbg@ipperformance.com> <39F69BB5.7861C480@dante.org.uk> In-Reply-To: <39F69BB5.7861C480@dante.org.uk> MIME-Version: 1.0 Message-Id: <00102508574004.01988@snoopy.fan.fa.disney.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Oct 2000, Konstantin Chuguev wrote: > rbg@ipperformance.com wrote: > > > No, I think he means the kernel VFS layer based AutoFS... ala SUN > > which was ported to AIX and I'm sure a bunch more platforms.. > > > > Besides of shell's uglish look of paths resolved from symbolic links created by AMD (like > /.a/net/my_server/home/joy as my home directory in bash on my workstation), what is the > advantage of doing this in kernel? No context switching from kernel space to user space. Lighter weight threads (a thread in the kernel vs a fork for amd) and with in place mounts, there is less likely for a deadlock situation to happen. - JimP > > > -- > * * Konstantin Chuguev - Application Engineer > * * Francis House, 112 Hills Road > * Cambridge CB2 1PQ, United Kingdom > D A N T E WWW: http://www.dante.net -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 9:43:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id AD07437B479; Wed, 25 Oct 2000 09:43:08 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9PGguj26737; Wed, 25 Oct 2000 09:42:56 -0700 (PDT) (envelope-from dillon) Date: Wed, 25 Oct 2000 09:42:56 -0700 (PDT) From: Matt Dillon Message-Id: <200010251642.e9PGguj26737@earth.backplane.com> To: Terry Lambert Cc: bright@wintelcom.net (Alfred Perlstein), ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness References: <200010251012.DAA19288@usr02.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Consider that a file with a huge number of pages outstanding :should probably be stealing pages from its own LRU list, and :not the system, to satisfy new requests. This is particularly :true of files that are demanding resources on a resource-bound :system. :... : Terry Lambert : terry@lambert.org This isn't exactly what I was talking about. The issue in regards to the filesystem syncer is that it fsync()'s an entire file. If you have a big file (e.g. a USENET news history file) the filesystem syncer can come along and exclusively lock it for *seconds* while it is fsync()ing it, stalling all activity on the file every 30 seconds. The current VM system already does a good job in allowing files to stealing pages from themselves. The sequential I/O detection heuristic depresses the priority of pages as they are read making it more likely for them to be reused. Since sequential I/O tends to be the biggest abuser of file cache, the current FreeBSD algorithms work well in real-life situations. We also have a few other optimizations to reuse pages in there that I had added a year or so ago (or fixed up, in the case of the sequential detection heuristic). One of the reasons why Yahoo uses MAP_NOSYNC so much (causing the problem that Alfred has been talking about) is because the filesystem syncer is 'broken' in regards to generating unnecessarily long stalls. Personally speaking, I would much rather use MAP_NOSYNC anyway, even with a fixed filesystem syncer. MAP_NOSYNC pages are not restricted by the size of the filesystem buffer cache, so you can have a whole lot more dirty pages in the system then you would normally be able to have. This 'feature' has had the unfortunate side effect of screwing up the pageout daemon's algorithms, but that's fixable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 9:44:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 929EC37B479 for ; Wed, 25 Oct 2000 09:44:30 -0700 (PDT) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e9PGiUR14347 for ; Wed, 25 Oct 2000 09:44:30 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP; Wed, 25 Oct 2000 09:45:00 -0700 Received: from plio.fan.fa.disney.com (plio.fan.fa.disney.com [153.7.118.2]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id JAA20980; Wed, 25 Oct 2000 09:44:24 -0700 (PDT) (envelope-from pirzyk@fa.disney.com) Received: from snoopy.fan.fa.disney.com (snoopy.fan.fa.disney.com [172.30.228.110]) by plio.fan.fa.disney.com (8.9.2/8.9.2) with ESMTP id JAA04412; Wed, 25 Oct 2000 09:44:23 -0700 (PDT) (envelope-from pirzyk@fa.disney.com) From: Jim Pirzyk Received: (from pirzyk@localhost) by snoopy.fan.fa.disney.com (8.9.3/8.9.3) id JAA04278; Wed, 25 Oct 2000 09:44:25 -0700 (PDT) (envelope-from pirzyk@fa.disney.com) Date: Wed, 25 Oct 2000 09:44:25 -0700 (PDT) Message-Id: <200010251644.JAA04278@snoopy.fan.fa.disney.com> To: tlambert@primenet.com Subject: Re: AutoFS on FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Oct 2000, Terry Lambert wrote: > > I was wondering if there is anyone working on AutoFS for FreeBSD. We > > currently have 4 studios with around 1000 unix systems of all kinds. > > Currently there are only 2 OSes that do not have autofs, FreeBSD and one > > that is known for its number crunching capabilties (and those are being > > phased out of production). Amd will not meet our needs because of the > > use of sym links. This is why AutoFS was written in the first place. > > I quote the 1993 USENIX paper on AutoFS (check > > http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt > > for the full paper). > > [ ... AutoFS Introduction ... ] > [ ... NFS automounter "problems" ... ] > > > > However, if a process invokes the getwd() function to obtain the path > > of the current directory while in an automounted filesystem, it will > > obtain a "/tmp_mnt/..." path. If this "back door" path is cached and > > used sometime later, there is no guarantee that the filesystem will > > still be mounted there. > > I think that the attempt to change to the directory should be delayed > until the event. This will cause the use of the forward path, which, > if there is a timeout, will reinvoke the automounter, correctly. Yes the attempt to mount the dir should be delayed until it is needed. But if the user cached the dir name with the results of a pwd/cwd, the it still would have the back door name of /tmp_mnt/... > > A common victim of this behavior is the at command. It uses the pwd > > command to record the current directory so that it can be cd'ed to > > for subsequent invocation of the script. > > I think this is a bug in the "at" command. If you want, I can > provide patches which implement the behaviour using "open(2)" and > "fchdir(2)", instead of recording the "cwd path". Alternately, > I can provide patches to make it use the command line path instead, > using evaluation of the path not involving "readlink(2)". I would > personally prefer the "fchdir(2)" method, since the "open(2)" will > keep the mount active, so it isn't allowed to time out. But fchdir needs a int fd argument (a open file handle) that was used by open(2), so if you close the fd, then the fchdir will fail and not work correctly. There is no way that I can see to use fchdir with out open(2). And we want the mount to expire. Modifiy at is just an ugly workaround for the problem in the first place. In addition to fixing 'at' you would have to fix 'csh' & 'tcsh'(ksh does not have the problem). > > The symbolic links also confuse users [...] > > This argument is an attempt to pile on; not a very good one. As long > as the software does what it's supposed to do, user's don't have to > be able to understand it to make it work. Look how many people drive > cars, but don't understand how they operate or program C, with no > understanding of the assembly language the compiler will produce as > a result. But since the users see the sym link name, it is not the same. The user cd's to /home/$LOGIN and when they do a pwd (in csh), they see /tmp_mnt/home/$LOGIN and say, "hey that is now where I cd'ed to, what is going on here". We move data around every week or so, and so we use symbolic names for our paths, like /data/ada18, but this week pwd returns /tmp_mnt/aj/export/bay_l1g1, but next week it could return /tmp_mnt/oilspot/january_b1g1 and we do NOT want our users to use those names at all. (We move data around so often because of defragging XFS file sysems or now we are in the process of upgrading XFS v1 to XFS v2 file systems. With around 10T of space, we do about 200 - 400GB over a weekend. Ther is a design bug in XFS v1 that if you have a long file name with most of the first characters the same, and then mount that filesystem over NFS, you will not see the second file. This is because of collisions in the hash table in the XFS directory. Yuck). > > If no one is using it, how is it looked apon if AutoFS was ported from > > Linux (with the GPL and that stuff) or would a complete rewrite be > > better? > > A complete rewrite would be required for the AutoFS to be included > in the system by default, if it were found to be generally desired. > > I think your problem can probably be solved a lot of ways; if the > Linux AutoFS is a module, you are aware that you can use Linux FS > modules under FreeBSD, right? No, I did not. This is very interesting. Have any pointers to where I would start looking. > If the problem is the "at" problem, I'd suggest that a simple > change to the problem software would also fix the problem. Nope, more than just at, it is the use of sym links in the mounts. Now I do see that amd had some sort of autofs mount type instead of nfs. That may work, but I do not know anything about it. > At worst, I'd suggest use of static maps, distributed via NIS, > to resolve the problem. Huhhh? We do use NIS to distribute our maps but that does not solve our problem. At one studio, we have to parallel maps, one for automount (auto.home and etc) and one for amd (amd.home) and the amd maps are auto generated from the automount maps. This works ok but does limit what options we can use in the automount maps (since in automounter you can define variables with -DIF=-atm on the command line). I have not been able to find out how to define my own variables in amd to use in my maps without recompiling. > I think that, given the way BSD covers mount points, the other > issues that were raised as problems are really no longer problems, > on modern systems. The threading is not an issue, and neither is > the map change. The performance issues for the link traversal > are really trivial (particularly when you consider that the "get > current directory" argument means that the symlinks were never > getting traversed, other than the very first reference). But the need to fix the caching the path information is in every program. Seems better to fix it in one place than in X where X is very large. One may not even be able to fix it everywhere, like in third party apps. (unless one fixes getwd()). > Is this a requirement that you be able to support "standard" AutoFS > mount maps, or is there an issue with the automounter where you > are actually experiencing a problem which would be resolved by > AutoFS and only AutoFS? The support of "standard" automount maps would be a big plus but the sym link issue is the major problem. It could be such a potental problem for us that it could jepordize the use of FreeBSD as a viable platform. > In any case, you *could* use the Linux AutoFS module with FreeBSD; > there is a port which supports Linux FS modules loaded into user > space, but without a clarification of why you want/need an AutoFS, > I don't think anyone can tell you whether or not that would be an > appropriate technology... I hope I have cleared up what I am after ( a better user experience ). Thanks - JimP -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 10:22:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from MLNOVPS0142.nacio.com (ns1.m-l.net [167.160.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 48B7137B4C5 for ; Wed, 25 Oct 2000 10:22:53 -0700 (PDT) Received: from polyserve.com ([167.160.187.80]) by MLNOVPS0142.nacio.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Wed, 25 Oct 2000 10:20:26 -0700 Message-ID: <39F71657.8855C56D@polyserve.com> Date: Wed, 25 Oct 2000 10:20:23 -0700 From: "Michelle R. Sanchez, CNE" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: question for the freebsd community Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, i work for a software company in berkeley that makes high availability server clustering software. we have a distribution for freebsd. our software is distributed and runs as a daemon on one's existing servers which are to be clustered together. in addition to making servers highly available, we also have the ability to monitor services such as http, smtp, and generic tcp apps by utilizing their ports and trying to make a tcp connection to them or sending an http head request if http is the one being monitored. if our software doesn't receive the anticipated reply - it will failover to the backup machine even though the primary machine is still physically running. we have had a lot of requests from customers wishing to make their firewalls highly available by clustering them together and putting a service monitor on the firewall port in case the firewall daemon should hang. this is probably not very likely but they would like to be able to do so in any case. my questions are these: 1] is it a good idea to try to put a service monitor on IPFW? If so, does this compromise the firewall in any way? i am not a firewall expert by any means but i think that you would not want to take this approach. our service monitor tries to connect to the application once per second or by some user-definable interval. 2] someone once suggested to monitor the port that the 'console' uses to talk to the firewall if you are trying to configure it remotely. would this be recommended? does it mean leaving the 'console' up all the time? 3] is there a configuration that could be made where the firewall would allow a tcp connection to be made by a specific IP address only - without any compromise? if so, how can this be done. the books i have purchased on firewalls and IPFW documentation unfortunately do not provide enough information for us to make a sound decision on this issue. i have researched this to the best of my ability and now i realize that i must ask the freebsd community for assistance. if anyone has any insight to provide on this issue - we would be most appreciative. kindest regards, michelle r. sanchez, cne/rhce polyserve technical support msanchez@polyserve.com 1 510 649 3554 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 10:38:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E2DEE37B4CF for ; Wed, 25 Oct 2000 10:38:19 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id NAA15590 for ; Wed, 25 Oct 2000 13:34:22 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001025133755.0270d1b0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 25 Oct 2000 13:39:14 -0400 To: hackers@freebsd.org From: Dennis Subject: trafshow question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a reason why trafshow wont run on an interface that doesnt have an IP address assigned? Bridged interfaces have traffic also. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 10:54:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by hub.freebsd.org (Postfix) with ESMTP id 23C5437B479 for ; Wed, 25 Oct 2000 10:54:18 -0700 (PDT) Received: from fondue.ICSI.Berkeley.EDU (fondue.ICSI.Berkeley.EDU [192.150.186.19]) by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id KAA12026; Wed, 25 Oct 2000 10:54:16 -0700 (PDT) Received: from localhost (rizzo@localhost) by fondue.ICSI.Berkeley.EDU (8.8.2/1.8) with ESMTP id KAA20803; Wed, 25 Oct 2000 10:54:15 -0700 (PDT) X-Authentication-Warning: fondue.ICSI.Berkeley.EDU: rizzo owned process doing -bs Date: Wed, 25 Oct 2000 10:54:15 -0700 (PDT) From: Luigi Rizzo To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: trafshow question In-Reply-To: <5.0.0.25.0.20001025133755.0270d1b0@mail.etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a reason why trafshow wont run on an interface that doesnt have an > IP address assigned? Bridged interfaces have traffic also. as far as i remember bpf complains for the lack of an IP address (though i do not remember if it is just a warning or a fatal error, i think i have run tcpdump on a bridged interface without an address assigned). If trafshow uses bpf that could be the cause of the problem, likely. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (501) 666 2947 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 11: 8:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0841137B479 for ; Wed, 25 Oct 2000 11:08:37 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id OAA15753; Wed, 25 Oct 2000 14:04:43 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001025140856.01e32cb0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 25 Oct 2000 14:09:35 -0400 To: Luigi Rizzo From: Dennis Subject: Re: trafshow question Cc: hackers@FreeBSD.ORG In-Reply-To: References: <5.0.0.25.0.20001025133755.0270d1b0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:54 PM 10/25/2000, Luigi Rizzo wrote: > > Is there a reason why trafshow wont run on an interface that doesnt > have an > > IP address assigned? Bridged interfaces have traffic also. > >as far as i remember bpf complains for the lack of an IP address >(though i do not remember if it is just a warning or a fatal error, >i think i have run tcpdump on a bridged interface without an >address assigned). If trafshow uses bpf that could be the cause >of the problem, likely. Yes, tcpdump complains but works, but trafshow refuses to start. Sounds like a bug. Dennis > cheers > luigi >----------------------------------+----------------------------------------- > Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) > http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 > Phone: (501) 666 2947 >----------------------------------+----------------------------------------- > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message Emerging Technologies, Inc. ------------------------------------------------------------------------------------- http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 11:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdhome.dyndns.org (unknown [24.25.2.13]) by hub.freebsd.org (Postfix) with ESMTP id 9EFCC37B479 for ; Wed, 25 Oct 2000 11:37:48 -0700 (PDT) Received: from vger.bsdhome.com (vger [192.168.220.2]) by bsdhome.dyndns.org (8.11.1/8.11.1) with ESMTP id e9PIbff10671; Wed, 25 Oct 2000 14:37:41 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: (from bsd@localhost) by vger.bsdhome.com (8.11.1/8.11.1) id e9PIbfY55165; Wed, 25 Oct 2000 14:37:41 -0400 (EDT) (envelope-from bsd) Date: Wed, 25 Oct 2000 14:37:41 -0400 From: Brian Dean To: Warner Losh Cc: Luigi Rizzo , Wilko Bulte , David Miller , freebsd-hackers@FreeBSD.ORG Subject: Re: Boot off USB SanDisk? Message-ID: <20001025143741.A55061@vger.bsdhome.com> References: <200010231803.MAA09059@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: <200010231803.MAA09059@harmony.village.org>; from imp@village.org on Mon, Oct 23, 2000 at 12:03:13PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > > You can use a IDE <-> CF adapter to boot off this device. You can't > : > > boot it off via the USB device however. So does FreeBSD recognize this as 'ad[0123]'? Even if we can boot from them, I suppose that it would be asking too much to expect any kind of hot pluggability? -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 11:55:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id ABFFC37B4CF for ; Wed, 25 Oct 2000 11:55:32 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9PIsva21963; Wed, 25 Oct 2000 11:54:57 -0700 (PDT) Date: Wed, 25 Oct 2000 11:54:57 -0700 From: Alfred Perlstein To: Dan Kegel Cc: Jonathan Lemon , hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results Message-ID: <20001025115457.X28123@fw.wintelcom.net> References: <20001024225637.A54554@prism.flugsvamp.com> <39F6655A.353FD236@alumni.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39F6655A.353FD236@alumni.caltech.edu>; from dank@alumni.caltech.edu on Tue, Oct 24, 2000 at 09:45:14PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG moved to hackers, dropped linux-kernel and -chat. * Dan Kegel [001024 21:38] wrote: > Johnathan, > Thanks for running that test for me! I've added your results > (plus a cautionary note about microbenchmarks and a link to > your site) to http://www.kegel.com/dkftpbench/Poller_bench.html > > If you haven't already, you might peek at the discussion on > linux-kernel. Linus seems to be on the verge of adding > something like kqueue() to Linux, but appears opposed to > supporting level-triggering; he likes the simplicity of > edge triggering (from the kernel's point of view!). See > http://boudicca.tux.org/hypermail/linux-kernel/2000week44/index.html#9 Jonathan, wouldn't this be a good time to try to push our interface on Linux? After all, we have several instances of it working and having the Open Source community force a new design feature into mainstream UNIX to address scalability would be very cool. Basically, if Linux implements exactly the same thing but just a bit different it would suck pretty badly for both camps. Also Linus doesn't seem to realize the utility of the transparent void * that kevent has: http://boudicca.tux.org/hypermail/linux-kernel/2000week44/0310.html Since you wrote kqueue, maybe you want to clue him in about the wonders of our interface before they find themselves with a deficient API that's not like anything else out there? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 13:21:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3CAD737B4CF for ; Wed, 25 Oct 2000 13:21:00 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9PKKhn93795; Wed, 25 Oct 2000 14:20:44 -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.9.3/8.8.3) with ESMTP id OAA35395; Wed, 25 Oct 2000 14:20:43 -0600 (MDT) Message-Id: <200010252020.OAA35395@harmony.village.org> To: Brian Dean Subject: Re: Boot off USB SanDisk? Cc: Luigi Rizzo , Wilko Bulte , David Miller , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 25 Oct 2000 14:37:41 EDT." <20001025143741.A55061@vger.bsdhome.com> References: <20001025143741.A55061@vger.bsdhome.com> <200010231803.MAA09059@harmony.village.org> Date: Wed, 25 Oct 2000 14:20:43 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001025143741.A55061@vger.bsdhome.com> Brian Dean writes: : > : > > You can use a IDE <-> CF adapter to boot off this device. You can't : > : > > boot it off via the USB device however. : : So does FreeBSD recognize this as 'ad[0123]'? Even if we can boot : from them, I suppose that it would be asking too much to expect any : kind of hot pluggability? It recognizes it ad0, et al. *DO*NOT*HOTPLUG* You will be sorry and replacing hardware. I've blown out 1 IDE controller before I twigged to this fact. :-( At least we could RMA the board. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 13:53: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5F6BB37B479 for ; Wed, 25 Oct 2000 13:53:02 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id D72071C72; Wed, 25 Oct 2000 16:53:01 -0400 (EDT) Date: Wed, 25 Oct 2000 16:53:01 -0400 From: Bill Fumerola To: "Michelle R. Sanchez, CNE" Cc: freebsd-hackers@freebsd.org Subject: Re: question for the freebsd community Message-ID: <20001025165301.O37870@jade.chc-chimes.com> References: <39F71657.8855C56D@polyserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39F71657.8855C56D@polyserve.com>; from msanchez@polyserve.com on Wed, Oct 25, 2000 at 10:20:23AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 25, 2000 at 10:20:23AM -0700, Michelle R. Sanchez, CNE wrote: > 1] is it a good idea to try to put a service monitor on IPFW? If so, > does this compromise the firewall in any way? Yes, it could be beneficial, if its done right it isn't a compromise. > i am not a firewall expert by any means but i think that you would not > want to take this approach. our service monitor tries to connect to the > application once per second or by some user-definable interval. If you wanted to get tricky, you could use icmp response codes to do what you want. Make a rule like: ipfw add unreach host-unknown tcp from somemonitoringmachine to yourfirewall someunusedport# (you can use an unused icmp unreach code for this as well.) open a connection to that machine (on that port) and you should get that icmp message back. you can do this with icmp as well: [hawk-root] /sys/netinet # ipfw sh 00100 0 0 unreach host-prohib icmp from any to 172.16.81.69 icmptype 8 65510 173 14654 allow ip from any to any 65535 0 0 deny ip from any to any [elk-billf] /home/billf > ping hawk PING hawk.internal.chc-chimes.com (172.16.81.69): 56 data bytes 36 bytes from hawk.internal.chc-chimes.com (172.16.81.69): Dest Unreachable, Bad Code: 10 Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 6800 55d4 0 0000 ff 01 ec9f 172.16.81.77 172.16.81.69 36 bytes from hawk.internal.chc-chimes.com (172.16.81.69): Dest Unreachable, Bad Code: 10 Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 6800 58d4 0 0000 ff 01 ec9c 172.16.81.77 172.16.81.69 Tada. If your firewall is "down" then the response wouldn't be a unreach with code 10. This may be considered hackish, but it also may be considered pretty damn slick. > 2] someone once suggested to monitor the port that the 'console' uses to > talk to the firewall if you are trying to configure it remotely. would > this be recommended? does it mean leaving the 'console' up all the time? The console is either your VGA/keyboard or a serial console depending on how you configure it. It is wise to either be really good at firewall rules or have some sort of out of band access to the firewall. > 3] is there a configuration that could be made where the firewall would > allow a tcp connection to be made by a specific IP address only - > without any compromise? if so, how can this be done. If you want _just_ those rules do this: ipfw add allow tcp from goodhost to mymachine portnumber setup ipfw add allow tcp from any to any established ipfw add deny tcp from any to mymachine portnumber If you already have rules, those 3 lines will go in different sections of your firewall. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 14:32:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 5074B37B479 for ; Wed, 25 Oct 2000 14:32:07 -0700 (PDT) Received: (from bob@localhost) by luke.immure.com (8.11.1/8.11.1) id e9PLW3t22547 for freebsd-hackers@freebsd.org; Wed, 25 Oct 2000 16:32:03 -0500 (CDT) (envelope-from bob) Date: Wed, 25 Oct 2000 16:32:03 -0500 From: Bob Willcox To: hackers list Subject: STAILQ_LAST -- what should it return? Message-ID: <20001025163203.A22361@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using a SINGLY-LINKED TAIL QUEUE in a device driver I'm developing and have encountered what looks like a problem with the STAILQ_LAST macro (this is FreeBSD 4.1.1-stable). This macro as defined: #define STAILQ_LAST(head) (*(head)->stqh_last) in /usr/src/sys/sys/queue.h appears to be returning the value of the first word of the last entry, which in my case (since the link pointer is the first word in each of my chained structures) is _always_ zero! What am I missing here? Is this possibly a bug or have I missinterpreted what this macro is supposed to do? Thanks, Bob -- Bob Willcox hatred, n: bob@VIEO.com A sentiment appropriate to the occasion of Austin, TX another's superiority. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 14:41:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 5B65B37B479 for ; Wed, 25 Oct 2000 14:41:44 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id OAA21677; Wed, 25 Oct 2000 14:42:10 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAAAhaG4C; Wed Oct 25 14:30:35 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA04864; Wed, 25 Oct 2000 14:30:03 -0700 (MST) From: Terry Lambert Message-Id: <200010252130.OAA04864@usr01.primenet.com> Subject: Re: AutoFS on FreeBSD To: Jim.Pirzyk@disney.com (Jim Pirzyk) Date: Wed, 25 Oct 2000 21:30:03 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com In-Reply-To: <200010251644.JAA04278@snoopy.fan.fa.disney.com> from "Jim Pirzyk" at Oct 25, 2000 09:44:25 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think that the attempt to change to the directory should be delayed > > until the event. This will cause the use of the forward path, which, > > if there is a timeout, will reinvoke the automounter, correctly. > > Yes the attempt to mount the dir should be delayed until it is needed. > But if the user cached the dir name with the results of a pwd/cwd, > the it still would have the back door name of /tmp_mnt/... [ ... symlink expansion ... ] The easiest fix is to fix symlinks to actually use reference inodes to refer to the real inodes, and not expand inline unless referenced explicitly through "readlink". The same approach would establish explicit parents for hardlinks. The pain here is that following a symlink loses your parent path, when it shouldn't. I still think users who are surprised at this shouldn't be looking behind the curtain, if they are not sure they will like what they find there, but am sympathetic to administrator worries. The problem boils down to knowing the parent pointer of a directory being pointed to; on a mount, that's explicit, since there is a 1:1 relationship, but on a symlink, there is no 1:1 enforcement. In the speed argument case, the argument against symlinks is destroyed if they are replaced by mounts, in any case, since comparisons against the device/inode number of all mounted FSs is vastly more expensive, overall, than simply expanding a symlink. I think if the cwd approach is used, you'll see that the mount will stay busy, so long as there are users sitting on a current directory, since a current directory reference is identical to an open file handle. The only exception is cd-cache-go_away- come-back, which is still a problem. The way my ISP handled this is to mount user's home directories onto /user/t (for /usr/t/terry, etc.), and let that be the explicit automount point, so that the directory never changes out from under the user. The actual FS mounted is never really exposed to the user's view, unless they do a "df" or a "mount" (the latter is restricted, while the former refuses to show NFS volumes); in any case, it would not naturally show the server in a getcwd result. Another option is to mount several FS instances using the automounter as one instance per FS. This would result in the mount point also appearing to be static, and can be done with creative amd maps (David Wolfskill did this for the engineering department a Whistle/IBM). Then there's always doing the dirty deed. On the plus side, you can use the direct approach that deadlocked them, since in BSD, the directories being covered don't need to exist as real things. The BSD VFS interface also allows you to cause a VFS layer to "eat" path components, so you could hide your symlink issue, and still use symlinks, if you wanted to do it that way. > > I think your problem can probably be solved a lot of ways; if the > > Linux AutoFS is a module, you are aware that you can use Linux FS > > modules under FreeBSD, right? > > No, I did not. This is very interesting. Have any pointers to where I > would start looking. You need to look in the -announce or -fs list archives; I believe the author of the note was Erez, Marius, or Karsten. Basically, another Eastern block maniac, of the type that brought us VGA displays built on ASCII art so that we can watch mpeg videos on Televideo 925s or MDA cards, has hacked up code that mmap's Linux FS modules into a user space process, and then satisfies their dependencies, allowing them to run via an NFS loopback. I remember it because it was so insane an idea, but it apparently worked well enough to announce; I believe that it was released around the same time as 3.4-STABLE. Unfortunately, the list archives are a bit spotty. I think the Erez is the primary investigator on FiST (it's his PhD thesis, if I remember correctly), and it may already implement AutoFS support. FiST runs under both FreeBSD and Linux, so it is an alternative, common ABI. > I hope I have cleared up what I am after ( a better user experience ). Understood; just looking for alternatives that don't have you doing a lot of coding yourself or trying to get someone else to do a lot of coding. You best bet, if you pursue this further, is to contact the freebsd-fs list instead of the freebsd-hackers list, since the people who hack FS code are all there, and not all here (as opposed to the people on hackers, who are "not all there" 8-)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 15: 2:47 2000 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 A60A737B4CF for ; Wed, 25 Oct 2000 15:02:44 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id e9PM1HC88732; Wed, 25 Oct 2000 17:01:17 -0500 (CDT) (envelope-from jlemon) Date: Wed, 25 Oct 2000 17:01:17 -0500 From: Jonathan Lemon To: Alfred Perlstein Cc: Dan Kegel , Jonathan Lemon , hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results Message-ID: <20001025170117.C87091@prism.flugsvamp.com> References: <20001024225637.A54554@prism.flugsvamp.com> <39F6655A.353FD236@alumni.caltech.edu> <20001025115457.X28123@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20001025115457.X28123@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 25, 2000 at 11:54:57AM -0700, Alfred Perlstein wrote: > moved to hackers, dropped linux-kernel and -chat. > > * Dan Kegel [001024 21:38] wrote: > > Johnathan, > > Thanks for running that test for me! I've added your results > > (plus a cautionary note about microbenchmarks and a link to > > your site) to http://www.kegel.com/dkftpbench/Poller_bench.html > > > > If you haven't already, you might peek at the discussion on > > linux-kernel. Linus seems to be on the verge of adding > > something like kqueue() to Linux, but appears opposed to > > supporting level-triggering; he likes the simplicity of > > edge triggering (from the kernel's point of view!). See > > http://boudicca.tux.org/hypermail/linux-kernel/2000week44/index.html#9 > > Jonathan, wouldn't this be a good time to try to push our interface > on Linux? After all, we have several instances of it working and > having the Open Source community force a new design feature into > mainstream UNIX to address scalability would be very cool. I'd love to do that, but am not quite sure how I'd go about it. If you read the l-k mailing list, you'll see Linus calling kqueue "overengineered", and what he is proposing is something that is definitely not well thought out. Other than whacking him on the head with a stick, any ideas on how to get him to turn away from the "NIH" syndrome? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 15:19:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id B1CF537B479; Wed, 25 Oct 2000 15:19:48 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id OAA01187; Wed, 25 Oct 2000 14:57:58 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpdAAA1taOK2; Wed Oct 25 14:51:44 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA05765; Wed, 25 Oct 2000 14:54:42 -0700 (MST) From: Terry Lambert Message-Id: <200010252154.OAA05765@usr01.primenet.com> Subject: Re: vm_pageout_scan badness To: dillon@earth.backplane.com (Matt Dillon) Date: Wed, 25 Oct 2000 21:54:42 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), bright@wintelcom.net (Alfred Perlstein), ps@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <200010251642.e9PGguj26737@earth.backplane.com> from "Matt Dillon" at Oct 25, 2000 09:42:56 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Consider that a file with a huge number of pages outstanding > :should probably be stealing pages from its own LRU list, and > :not the system, to satisfy new requests. This is particularly > :true of files that are demanding resources on a resource-bound > :system. > > This isn't exactly what I was talking about. The issue in regards to > the filesystem syncer is that it fsync()'s an entire file. If > you have a big file (e.g. a USENET news history file) the > filesystem syncer can come along and exclusively lock it for > *seconds* while it is fsync()ing it, stalling all activity on > the file every 30 seconds. This seems like a broken (non)use of _SYNC parameters, but I definitely remember now about the FreeBSD breakage in the dirty page sync case not knowing what pages should be sync'ed or not, in the mmap region sync case of msync() degrading to fsync(). I guess O_WRITESYNC or msync() fixing is not an option? > The current VM system already does a good job in allowing files > to stealing pages from themselves. The sequential I/O detection > heuristic depresses the priority of pages as they are read making > it more likely for them to be reused. Since sequential I/O tends > to be the biggest abuser of file cache, the current FreeBSD > algorithms work well in real-life situations. We also have a few > other optimizations to reuse pages in there that I had added a year > or so ago (or fixed up, in the case of the sequential detection > heuristic). The biggest abuser that I have seen of this is actually not sequential. It is a linker that mmap()'s the object files, and then seeks all over creation to do the link, forcing all other pages out of core. I think the assumption that this is a sequential access problem, instead of a more general problem, is a bad one (FWIW, building per vnode working set quotas fixed the problem with the linker being antagonisitic). > One of the reasons why Yahoo uses MAP_NOSYNC so much (causing > the problem that Alfred has been talking about) is because the > filesystem syncer is 'broken' in regards to generating > unnecessarily long stalls. It doesn't stall when it should? 8-) 8-). I think this is a case of needing to eventually pay the piper for the music being played. If the pages are truly anonymous, then they don't need sync'ed; if they aren't, then they do need sync'ed. It sounds to me that if they are seeing long stalls, it's the msync() bug with not being able to tell what's dirty and what's clean... > Personally speaking, I would much rather use MAP_NOSYNC anyway, > even with a fixed filesystem syncer. MAP_NOSYNC pages are not > restricted by the size of the filesystem buffer cache, I see this as a bug in the non-MAP_NOSYNC case in FreeBSD's use vnodes as synonyms for vm_object_t's. I really doubt, though, that they are exceeding the maximum file size with a mapping; if not, then the issue is tuning. The limits on the size of the FS buffer cache are arbitrary; it should be possible to relax them. Again, I think the biggest problem here is historical, and it derives from the ability to dissociate a vnode with pages still hung off it from the backing inode (a cache bust). I suspect that if they increased the size of the ihash cache, they would see much better characteristics. My personal preference would be to not dissociate valid but clean pages from the reference object, until absolutely necessary. An easy fix for this would be to allow the FS to own the vnodes, not have a fixed size pool, and have a struct like: struct ufs_vnode { struct vnode; struct ufs_in_core_inode; }; And pass that around as if it were just a vnode, giving it back the the VFS that owned it, instead of using a system reclaim method, in order to reclaim it. Then if an ihash reclaim was wanted, it would have to free up the vnode resources to get it. Using high and low watermarks, instead of a fixed pool would complete the picture (the use of a fixed per-FS ihash pool in combination with a high/low watermarked per-system vnode pool is part of what causes the problem in the first place; an analytical mechanic or electronics buff would call this a classic case of "impedence mismatch"). > so you can have a whole lot more dirty pages in the system > then you would normally be able to have. E.g. they are working around an arbitrary, and wrong-for-them, administrative limit, instead of changing it. Bletch. > This 'feature' has had the unfortunate side effect of screwing > up the pageout daemon's algorithms, but that's fixable. I think the idea of a fixed limit on the FS buffer cache is probably wrong in the first place; certainly, there must be high and low reserves, but: |----------------------------------------------| all of memory |---------------------------------| FS allowed use |-------------------------------------| non-FS allowed use |------------| non-FSreserve |--------| FS reserve ...in other words, a reserve-based system, rather than a limit based system. It would result in the same effect, without damaging natural limits for any given loading chracteristics, arrived at through hysteresis effects, right? NB: The reserve sizes in the diagram are vastly exagerated to keep them from being just vertical bars. It has always amazed me that the system limits natural load as if all systems were to be used as general purpose systems by interactive users; you could achieve that effect by making larger reserves for interactive use, but you can't achieve the opposite effect by diddling administrative limits that aren't already predicated on a reserve model. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 16: 9:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BD5CF37B4C5 for ; Wed, 25 Oct 2000 16:09:47 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9PN9ip00617; Wed, 25 Oct 2000 16:09:44 -0700 (PDT) Date: Wed, 25 Oct 2000 16:09:44 -0700 From: Alfred Perlstein To: Jonathan Lemon Cc: Dan Kegel , hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results Message-ID: <20001025160944.C28123@fw.wintelcom.net> References: <20001024225637.A54554@prism.flugsvamp.com> <39F6655A.353FD236@alumni.caltech.edu> <20001025115457.X28123@fw.wintelcom.net> <20001025170117.C87091@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001025170117.C87091@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Wed, Oct 25, 2000 at 05:01:17PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jonathan Lemon [001025 15:02] wrote: > On Wed, Oct 25, 2000 at 11:54:57AM -0700, Alfred Perlstein wrote: > > moved to hackers, dropped linux-kernel and -chat. > > > > * Dan Kegel [001024 21:38] wrote: > > > Johnathan, > > > Thanks for running that test for me! I've added your results > > > (plus a cautionary note about microbenchmarks and a link to > > > your site) to http://www.kegel.com/dkftpbench/Poller_bench.html > > > > > > If you haven't already, you might peek at the discussion on > > > linux-kernel. Linus seems to be on the verge of adding > > > something like kqueue() to Linux, but appears opposed to > > > supporting level-triggering; he likes the simplicity of > > > edge triggering (from the kernel's point of view!). See > > > http://boudicca.tux.org/hypermail/linux-kernel/2000week44/index.html#9 > > > > Jonathan, wouldn't this be a good time to try to push our interface > > on Linux? After all, we have several instances of it working and > > having the Open Source community force a new design feature into > > mainstream UNIX to address scalability would be very cool. > > I'd love to do that, but am not quite sure how I'd go about it. > If you read the l-k mailing list, you'll see Linus calling kqueue > "overengineered", and what he is proposing is something that is > definitely not well thought out. I think that's a good summary and probably what you ought to tell him. > Other than whacking him on the head with a stick, any ideas on > how to get him to turn away from the "NIH" syndrome? Try apealing to his sense of making Linux compatible with other OS's... er... Actually I'm at a loss here. :) If you do mail the linux kernel list, which you _should_ otherwise you'll find yourself implementing thier substandard hack over kqueue for freebsd 5 and a really annoying thing to emulate in the linuxulator. CC me on the mail, I'll back you up. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 16:13: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id 5497437B479 for ; Wed, 25 Oct 2000 16:12:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.0/8.11.1) with ESMTP id e9PNDe422236 for ; Wed, 25 Oct 2000 19:13:40 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Wed, 25 Oct 2000 19:13:40 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: freebsd-hackers@freebsd.org Subject: Re: question for the freebsd community In-Reply-To: <39F71657.8855C56D@polyserve.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Oct 2000, Michelle R. Sanchez, CNE wrote: > [...company makes high availability clustering software, and > supports FreeBSD...] > > we have had a lot of requests from customers wishing to make their > firewalls highly available by clustering them together and putting a > service monitor on the firewall port in case the firewall daemon should > hang. this is probably not very likely but they would like to be able to > do so in any case. > > my questions are these: > > 1] is it a good idea to try to put a service monitor on IPFW? If so, > does this compromise the firewall in any way? ipfw is not a daemon, and does not have a designated port to monitor--it's a kernel option to do packet filtering. If a kernel is built with the IPFIREWALL option, and the machine is running, then the firewall is also running, period. That should make the monitor as simple as asking the machine "Are you alive?". :-) I'd suggest "man ipfw" and also look at /sys/i386/conf/LINT for more details. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 18:26:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pimout3-int.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by hub.freebsd.org (Postfix) with ESMTP id 666DE37B479 for ; Wed, 25 Oct 2000 18:26:17 -0700 (PDT) Received: from ppp-207-193-3-44.kscymo.swbell.net (ppp-207-193-3-44.kscymo.swbell.net [207.193.3.44]) by pimout3-int.prodigy.net (8.10.1/8.10.1) with ESMTP id e9Q1QAj120246 for ; Wed, 25 Oct 2000 21:26:12 -0400 Received: (from jbryant@localhost) by ppp-207-193-3-44.kscymo.swbell.net (8.9.3/8.9.3) id UAA94395 for freebsd-hackers@freebsd.org; Wed, 25 Oct 2000 20:26:15 -0500 (CDT) (envelope-from jbryant) From: Jim Bryant Message-Id: <200010260126.UAA94395@ppp-207-193-3-44.kscymo.swbell.net> Subject: Rijndael status in FreeBSD?? To: freebsd-hackers@freebsd.org Date: Wed, 25 Oct 100 20:24:24 -0500 (CDT) Reply-To: kc5vdj@prodigy.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-RELEASE X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What are the plans for incorporating Rijndael, the finalist algorithm for the Advanced Encryption Standard, into FreeBSD? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ kc5vdj@prodigy.net KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81A KPC3+ & PK-232MBX Grid: EM28px ------------------------------------------------------------------------------ ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 19: 2:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id D7BC437B479 for ; Wed, 25 Oct 2000 19:02:12 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9Q26Eh00591; Wed, 25 Oct 2000 19:06:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010260206.e9Q26Eh00591@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Michelle R. Sanchez, CNE" Cc: freebsd-hackers@freebsd.org Subject: Re: question for the freebsd community In-reply-to: Your message of "Wed, 25 Oct 2000 10:20:23 PDT." <39F71657.8855C56D@polyserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Oct 2000 19:06:14 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > we have had a lot of requests from customers wishing to make their > firewalls highly available by clustering them together and putting a > service monitor on the firewall port in case the firewall daemon should > hang. this is probably not very likely but they would like to be able to > do so in any case. Just so that it's clear; in the FreeBSD context there's no "firewall daemon" so there's nothing to hang. If you're talking about the NAT daemon, then yes, adding monitoring to it would be a good idea. -- ... 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 Wed Oct 25 20:57:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 19C1937B479 for ; Wed, 25 Oct 2000 20:57:31 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id e9Q3xsS08119; Wed, 25 Oct 2000 20:59:54 -0700 (PDT) (envelope-from kris) Date: Wed, 25 Oct 2000 20:59:53 -0700 From: Kris Kennaway To: kc5vdj@prodigy.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Rijndael status in FreeBSD?? Message-ID: <20001025205953.A8103@citusc17.usc.edu> References: <200010260126.UAA94395@ppp-207-193-3-44.kscymo.swbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010260126.UAA94395@ppp-207-193-3-44.kscymo.swbell.net>; from jbryant@ppp-207-193-3-44.kscymo.swbell.net on Wed, Oct 25, 2000 at 08:24:24PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 25, 2000 at 08:24:24PM -0500, Jim Bryant wrote: > What are the plans for incorporating Rijndael, the finalist algorithm > for the Advanced Encryption Standard, into FreeBSD? Going into the kernel as soon as I get some free time..I have patches from KAME to add AES IPSEC support, OpenSSH support will also come in at a later date once they release a new version containing it. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 22:53:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 1D4EB37B479; Wed, 25 Oct 2000 22:53:23 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9Q5qnf32627; Wed, 25 Oct 2000 22:52:49 -0700 (PDT) (envelope-from dillon) Date: Wed, 25 Oct 2000 22:52:49 -0700 (PDT) From: Matt Dillon Message-Id: <200010260552.e9Q5qnf32627@earth.backplane.com> To: Alfred Perlstein , ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: VM pager patch (was Re: vm_pageout_scan badness) References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> <20001025123154.A56298@heechee.tobez.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a test patch, inclusive of some debugging sysctls: vm.always_launder set to 1 to give up on trying to avoid pageouts. vm.vm_pageout_stats_rescans Number of times the main inactive scan in the pageout loop had to restart vm.vm_pageout_stats_xtralaunder Number of times a second pass had to be taken (in normal mode, with always_launder set to 0). This patch: * implements a placemarker to try to avoid restarts. * does not penalize the pageout daemon for being able to cluster writes. * adds an additional vnode check that should be there One last note: I wrote a quick and dirty program to mmap() a bunch of big files MAP_NOSYNC and then dirty them in a loop. I noticed that the filesystem update daemon 'froze up' the system for about a second every 30 seconds due to the huge number of dirty MAP_NOSYNC pages (about 1GB worth) sitting around (it has to scan the vm_page_t's even if it doesn't do anything with them). This is a separate issue. If Alfred, and others running heavily loaded systems are able to test this patch sufficiently, we can include it (minus the debugging sysctls) in the release. If not, I will wait until after the release is rolled before I commit it or whatever the final patch winds up looking like. -Matt Index: vm_page.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.c,v retrieving revision 1.147.2.3 diff -u -r1.147.2.3 vm_page.c --- vm_page.c 2000/08/04 22:31:11 1.147.2.3 +++ vm_page.c 2000/10/26 04:43:22 @@ -1783,6 +1783,12 @@ ("contigmalloc1: page %p is not PQ_INACTIVE", m)); next = TAILQ_NEXT(m, pageq); + /* + * ignore markers + */ + if (m->flags & PG_MARKER) + continue; + if (vm_page_sleep_busy(m, TRUE, "vpctw0")) goto again1; vm_page_test_dirty(m); Index: vm_page.h =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.h,v retrieving revision 1.75.2.3 diff -u -r1.75.2.3 vm_page.h --- vm_page.h 2000/09/16 01:08:03 1.75.2.3 +++ vm_page.h 2000/10/26 04:17:28 @@ -251,6 +251,7 @@ #define PG_SWAPINPROG 0x0200 /* swap I/O in progress on page */ #define PG_NOSYNC 0x0400 /* do not collect for syncer */ #define PG_UNMANAGED 0x0800 /* No PV management for page */ +#define PG_MARKER 0x1000 /* special queue marker page */ /* * Misc constants. Index: vm_pageout.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_pageout.c,v retrieving revision 1.151.2.4 diff -u -r1.151.2.4 vm_pageout.c --- vm_pageout.c 2000/08/04 22:31:11 1.151.2.4 +++ vm_pageout.c 2000/10/26 05:07:45 @@ -143,6 +143,9 @@ static int disable_swap_pageouts=0; static int max_page_launder=100; +static int always_launder=0; +static int vm_pageout_stats_rescans=0; +static int vm_pageout_stats_xtralaunder=0; #if defined(NO_SWAPPING) static int vm_swap_enabled=0; static int vm_swap_idle_enabled=0; @@ -186,6 +189,12 @@ SYSCTL_INT(_vm, OID_AUTO, max_page_launder, CTLFLAG_RW, &max_page_launder, 0, "Maximum number of pages to clean per pass"); +SYSCTL_INT(_vm, OID_AUTO, always_launder, + CTLFLAG_RW, &always_launder, 0, "Always launder on the first pass"); +SYSCTL_INT(_vm, OID_AUTO, vm_pageout_stats_rescans, + CTLFLAG_RD, &vm_pageout_stats_rescans, 0, ""); +SYSCTL_INT(_vm, OID_AUTO, vm_pageout_stats_xtralaunder, + CTLFLAG_RD, &vm_pageout_stats_xtralaunder, 0, ""); #define VM_PAGEOUT_PAGE_COUNT 16 @@ -613,11 +622,16 @@ /* * vm_pageout_scan does the dirty work for the pageout daemon. + * + * This code is responsible for calculating the page shortage + * and then attempting to clean or free enough pages to hit that + * mark. */ static int vm_pageout_scan() { vm_page_t m, next; + struct vm_page marker; int page_shortage, maxscan, pcount; int addl_page_shortage, addl_page_shortage_init; int maxlaunder; @@ -651,27 +665,41 @@ /* * Figure out what to do with dirty pages when they are encountered. * Assume that 1/3 of the pages on the inactive list are clean. If - * we think we can reach our target, disable laundering (do not - * clean any dirty pages). If we miss the target we will loop back - * up and do a laundering run. + * we think we can reach our target, reduce the amount of launder we + * try to do in the first pass significantly. If we miss the target + * we will loop back up and do a full laundering run. + * + * If always_launder is set, we do a full laundering run on the + * first pass. */ - if (cnt.v_inactive_count / 3 > page_shortage) { + if (always_launder == 0 && cnt.v_inactive_count / 3 > page_shortage) { +#if 0 /* THIS MAY BE BETTER */ + maxlaunder = cnt.v_inactive_target / 10 + 1; +#endif maxlaunder = 0; launder_loop = 0; } else { - maxlaunder = - (cnt.v_inactive_target > max_page_launder) ? - max_page_launder : cnt.v_inactive_target; + maxlaunder = cnt.v_inactive_target; launder_loop = 1; } + if (maxlaunder > max_page_launder) + maxlaunder = max_page_launder; /* + * Initialize our marker + */ + bzero(&marker, sizeof(marker)); + marker.flags = PG_BUSY | PG_FICTITIOUS | PG_MARKER; + marker.valid = 0; + marker.queue = PQ_INACTIVE; + marker.wire_count = 1; + + /* * Start scanning the inactive queue for pages we can move to the * cache or free. The scan will stop when the target is reached or * we have scanned the entire inactive queue. */ - rescan0: addl_page_shortage = addl_page_shortage_init; maxscan = cnt.v_inactive_count; @@ -682,11 +710,18 @@ cnt.v_pdpages++; if (m->queue != PQ_INACTIVE) { + ++vm_pageout_stats_rescans; goto rescan0; } next = TAILQ_NEXT(m, pageq); + /* + * Skip marker pages + */ + if (m->flags & PG_MARKER) + continue; + if (m->hold_count) { s = splvm(); TAILQ_REMOVE(&vm_page_queues[PQ_INACTIVE].pl, m, pageq); @@ -763,7 +798,8 @@ --page_shortage; /* - * Clean pages can be placed onto the cache queue. + * Clean pages can be placed onto the cache queue, which + * is almost the same as freeing them. */ } else if (m->dirty == 0) { vm_page_cache(m); @@ -774,7 +810,6 @@ * only a limited number of pages per pagedaemon pass. */ } else if (maxlaunder > 0) { - int written; int swap_pageouts_ok; struct vnode *vp = NULL; @@ -871,10 +906,16 @@ } /* - * The page might have been moved to another queue - * during potential blocking in vget() above. + * The page might have been moved to another + * queue during potential blocking in vget() + * above. The page might have been freed and + * reused for another vnode. The object might + * have been reused for another vnode. */ - if (m->queue != PQ_INACTIVE) { + if (m->queue != PQ_INACTIVE || + m->object != object || + object->handle != vp + ) { if (object->flags & OBJ_MIGHTBEDIRTY) vnodes_skipped++; vput(vp); @@ -882,9 +923,10 @@ } /* - * The page may have been busied during the blocking in - * vput(); We don't move the page back onto the end of - * the queue so that statistics are more correct if we don't. + * The page may have been busied during the + * blocking in vput(); We don't move the + * page back onto the end of the queue so that + * statistics are more correct if we don't. */ if (m->busy || (m->flags & PG_BUSY)) { vput(vp); @@ -910,13 +952,27 @@ * If a page is dirty, then it is either being washed * (but not yet cleaned) or it is still in the * laundry. If it is still in the laundry, then we - * start the cleaning operation. + * start the cleaning operation. maxlaunder nominally + * counts I/O cost, essentially seeks, so we drop it + * by one no matter how large a cluster + * vm_pageout_clean() is able to put together. + * + * This operation may cluster-out, causing the 'next' + * page to move to another queue. To avoid loosing our + * place we insert a placemarker, then recalculate + * next after vm_pageout_clean() returns. */ - written = vm_pageout_clean(m); - if (vp) + s = splvm(); + TAILQ_INSERT_AFTER(&vm_page_queues[PQ_INACTIVE].pl, m, &marker, pageq); + splx(s); + if (vm_pageout_clean(m) != 0) + --maxlaunder; + s = splvm(); + next = TAILQ_NEXT(&marker, pageq); + TAILQ_REMOVE(&vm_page_queues[PQ_INACTIVE].pl, &marker, pageq); + splx(s); + if (vp != NULL) vput(vp); - - maxlaunder -= written; } } @@ -930,6 +986,7 @@ maxlaunder = (cnt.v_inactive_target > max_page_launder) ? max_page_launder : cnt.v_inactive_target; + ++vm_pageout_stats_xtralaunder; goto rescan0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 25 23:18:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flashmail.com (unknown [202.166.255.140]) by hub.freebsd.org (Postfix) with SMTP id 657F637B479 for ; Wed, 25 Oct 2000 23:18:49 -0700 (PDT) Message-Id: X-Sender: fast_ride2001@flashmail.com X-Mailer: Mozilla 4.71 [en] (Win98; I) Date: Wed, 25 Oct 2000 23:18:14 -0700 To: carlist From: fast_ride2001 Subject: FREE! Get A Great Price On A New Car! (3e8445a9) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Get A Great Price On A New Car! Absolutely Free! Want to save time and money? Want to have quick access to car quotes? Want to have all makes and models available to you? If you answered yes to any of these, then take advantage of this free, no-hassle service. Simply click on the link below to get low prices on all makes and models of new and used cars, without having to negotiate with a dealer. It’s painless and stress-free! CLICK-HERE--> http://3627528622/ <--CLICK-HERE ************************************************** If you wish to unsubscribe from this list, simply go to http://3627528622/remove.html and follow the instructions. You will be removed immediately. PLEASE NOTE: replying to this message will not remove you, you MUST follow the link above. Thank you. ************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 0:11:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E04E537B479; Thu, 26 Oct 2000 00:11:16 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9Q7B6q32884; Thu, 26 Oct 2000 00:11:06 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Oct 2000 00:11:06 -0700 (PDT) From: Matt Dillon Message-Id: <200010260711.e9Q7B6q32884@earth.backplane.com> To: Anton Berezin Cc: Alfred Perlstein , ps@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_pageout_scan badness References: <20001024112708.E28123@fw.wintelcom.net> <200010242010.e9OKAJK19739@earth.backplane.com> <20001025123154.A56298@heechee.tobez.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, Oct 24, 2000 at 01:10:19PM -0700, Matt Dillon wrote: :> Ouch. The original VM code assumed that pages would not often be :> ripped out from under the pageadaemon, so it felt free to restart :> whenever. I think you are absolutely correct in regards to the :> clustering code causing nearby-page ripouts. :> :> I don't have much time available, but let me take a crack at the :> problem tonight. : :While you are at it, would you care and have a look at PR19672. It :seems to be at least remotely relevant. ;-) Hmmm. Blech. contigmalloc is aweful. I'm not even sure if what it is doing is legal! If it can't find contiguous space it tries to flush the entire inactive and active queues. Every single page! not to mention the insane restarting. The algorithm is O(N^2) on an idle machine, and even worse on machines that might be doing something. There is no easy fix. contigmalloc would have to be completely rewritten. We could use the placemarker idea to make the loop 'retry' the page that blocked rather then restart at the beginning, but the fact that contigmalloc tries to flush the entire page queue means that it could very trivially get stuck on dead devices (e.g. like a dead NFS mount). Also, if we don't restart, there is less of a chance that contigmalloc can find sufficient free space. When it frees pages it does so half-hazzardly, and when it flushes pages out it makes no attempt to free them so an active process may reuse the page instantly. Bleh. I'm afraid I don't have the time to rewrite contigmalloc myself, but my brain is available to answer questions if someone else wants to have a go at it. -Matt :Cheers, :%Anton. :-- : and would be a nice addition :to HTML specification. : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 1:47:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 762E937B4C5; Thu, 26 Oct 2000 01:47:29 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JVSGN1N80K000T66@research.kpn.com>; Thu, 26 Oct 2000 10:47:27 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Thu, 26 Oct 2000 10:47:27 +0100 Content-return: allowed Date: Thu, 26 Oct 2000 10:47:26 +0100 From: "Koster, K.J." Subject: KPN ADSL Mxstream howto To: 'FreeBSD Questions mailing list' , 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7960@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, It's interesting to hear the reactions when you ask for FreeBSD support at helpdesks. (and not just KPN's) They used to say: "I'm sorry, you cannot use anything but Windows", nowadays they apologize for not knowing enough about UNIX to help. :-) We're getting there. For all you Dutchies out there: here's how I set up my Mxstream connection under FreeBSD. http://web.inter.nl.net/users/kjkoster/content/adsl.html Kees Jan Disclaimer: Yes, I work for KPN, but that is a coincidence. This e-mail is from me personally, and KPN may or may not agree with me. ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 2:52:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 1FC3E37B479; Thu, 26 Oct 2000 02:52:52 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 1651628788; Thu, 26 Oct 2000 16:52:46 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 0B68028761; Thu, 26 Oct 2000 16:52:46 +0700 (ALMST) Date: Thu, 26 Oct 2000 16:52:45 +0700 (ALMST) From: Boris Popov To: Joseph Scott Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <39F46B08.808132D2@owp.csus.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Joseph Scott wrote: > When is this going to be brought into -current? This was planned to be done in early September, but got some troubles with import of iconv library. I can't import smbfs without i18n support because many people use it. In any way, future smbfs releases will support 4.x and recent -current. p.s. Sorry for delay but I'm overloaded with my primary work and a little bit behind my mail :( -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 5:23:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lambdatel.com (lambda.lambdatel.com [192.83.199.1]) by hub.freebsd.org (Postfix) with ESMTP id 8946B37B4CF for ; Thu, 26 Oct 2000 05:23:16 -0700 (PDT) Received: from jim (helo=localhost) by lambdatel.com with local-smtp (Exim 2.11 #1) id 13om5D-000252-00 for hackers@freebsd.org; Thu, 26 Oct 2000 05:24:35 -0700 Date: Thu, 26 Oct 2000 05:24:35 -0700 (PDT) From: Jim Dixon To: hackers@freebsd.org Subject: Status?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple of days ago, I made a request for the assignment of a major device number and have not as of yet received any response directly regarding this request. Like what's going on with this?? Thanks.... Jim Dixon Duuuude jim@lambdatel.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 5:27: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 67BCC37B479 for ; Thu, 26 Oct 2000 05:27:08 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9QCQx449342; Thu, 26 Oct 2000 05:26:59 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Jim Dixon Cc: hackers@FreeBSD.ORG Subject: Re: Status?? In-Reply-To: Message from Jim Dixon of "Thu, 26 Oct 2000 05:24:35 PDT." Date: Thu, 26 Oct 2000 05:26:59 -0700 Message-ID: <49338.972563219@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A couple of days ago, I made a request for the assignment of a major > device number and have not as of yet received any response directly > regarding this request. > > Like what's going on with this?? Sorry, that rule has changed a little since those guidelines were formed. Now the policy is to simply use the special major which is reserved for this (20) until such time as you actually want to bring the driver into FreeBSD. At that point, you're assigned whatever major is free at the time of the import. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 6:10:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by hub.freebsd.org (Postfix) with ESMTP id 2ED8C37B4E5 for ; Thu, 26 Oct 2000 06:10:25 -0700 (PDT) Received: from student.tue.nl (dhcp0.stack.nl [::ffff:131.155.141.120]) by mailhost.stack.nl (Postfix) with ESMTP id 5E19914E04 for ; Thu, 26 Oct 2000 15:10:23 +0200 (CEST) Message-ID: <39F82D3C.2532AEB7@student.tue.nl> Date: Thu, 26 Oct 2000 15:10:20 +0200 From: David van Deijk Organization: tue X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: dir-listing bug in linux-emulation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear hackers. When I was running an linux program (soffice) i needed something of my dos-partition. Then i stumbled onto something I would call a "major" bug. I went to /dos/c (my first partition ) but saw only 6 files and 1 dir. So i went for some exploring and this are my results: (davidd@93% batterij)/dos/c$ls 4dos FCONNECT VIDEOROM.BIN ASD.LOG IO.SYS WINDOWS ATI LOGITEMP WinRAR AUTOEXEC.BAT MOUSE XIRCOM AUTOEXEC.DOS MSDOS.--- bbdemo AUTOEXEC.JPS MSDOS.SYS command.PIF BAS MagicCube4D dosd BDIENST MagicCube4D.log fbsdboot.exe BIN MikTeX fbsdboot.zip BOOMPJE.COM NUKEM2.BAT freebsd BOOTLOG.PRV PDOXUSRS.NET geems BOOTLOG.TXT Program Files logo.sys BOOTSECT.F16 RECYCLED mukzooi.m3u BRAND.EXE Rescued Document.txt my documents COMMAND.COM SCANDISK.LOG netwerk CONFIG.DOS SETUP.EXE opennap CONFIG.SYS SETUPLOG.TXT rip DETLOG.OLD SETUPXLG.TXT t3vvn4hn DETLOG.TXT SUHDLOG.DAT temp DUKE2 SYSTEM.1ST truman DUKE3D SchoonWoagen.exe wav DUKE3D.BAT Tntetris www Exceed.lnk Tuecis (davidd@93% batterij)/dos/c$ (davidd@93% batterij)/dos/c$/usr/compat/linux/bin/bash (davidd@93% batterij)/dos/c$ls BOOTSECT.F16 IO.SYS SCANDISK.LOG WINDOWS COMMAND.COM MSDOS.SYS SUHDLOG.DAT (davidd@93% batterij)/dos/c$ when i checked these 7 files were the first 7 directorie entrys in de root dir BTW. cd - ing to not listed dirs was no problem... (davidd@93% batterij)/dos/c$cd dosd (davidd@93% batterij)/dos/c/dosd$ls RECYCLED RealPlayer blabla zut math mpeg tentamina tweakvga wolf (davidd@93% batterij)/dos/c/dosd$ but again only 8 files are listed (this time including long file names) I would like to have a solution for this (so i can browse my dos with linux binaries). TIA. David van Deijk. PS. any other persons confirming (or not) this problem would be welcome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 8: 5:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id A0AF237B479; Thu, 26 Oct 2000 08:05:07 -0700 (PDT) Received: from localhost (scottj@localhost) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id IAA44613; Thu, 26 Oct 2000 08:04:57 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Date: Thu, 26 Oct 2000 08:04:57 -0700 (PDT) From: Joseph Scott X-Sender: scottj@pebkac.owp.csus.edu To: Boris Popov Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Oct 2000, Boris Popov wrote: > On Mon, 23 Oct 2000, Joseph Scott wrote: > > > When is this going to be brought into -current? > > This was planned to be done in early September, but got some > troubles with import of iconv library. I can't import smbfs without i18n > support because many people use it. > > In any way, future smbfs releases will support 4.x and recent > -current. I've only got -stable boxes around here, I was asking simply because the sooner it makes it into -current the sooner it gets into -stable :-) Thanks again for your work on this, I look forward to seeing this in the base system. --- Joseph Scott joseph.scott@owp.csus.edu The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 10:12:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id C4BC637B479 for ; Thu, 26 Oct 2000 10:12:44 -0700 (PDT) Received: (from bob@localhost) by luke.immure.com (8.11.1/8.11.1) id e9QHChP39131 for freebsd-hackers@FreeBSD.ORG; Thu, 26 Oct 2000 12:12:43 -0500 (CDT) (envelope-from bob) Date: Thu, 26 Oct 2000 12:12:43 -0500 From: Bob Willcox To: hackers list Subject: Re: STAILQ_LAST -- what should it return? Message-ID: <20001026121243.A38987@luke.immure.com> Reply-To: Bob Willcox References: <20001025163203.A22361@luke.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001025163203.A22361@luke.immure.com>; from bob@immure.com on Wed, Oct 25, 2000 at 04:32:03PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To follow-up my own question, it appears that the STAILQ_LAST macro has been changed (fixed) in -current to return the address of the last entry (or NULL if the list is empty). Bob On Wed, Oct 25, 2000 at 04:32:03PM -0500, Bob Willcox wrote: > I am using a SINGLY-LINKED TAIL QUEUE in a device driver I'm developing > and have encountered what looks like a problem with the STAILQ_LAST > macro (this is FreeBSD 4.1.1-stable). This macro as defined: > > #define STAILQ_LAST(head) (*(head)->stqh_last) > > in /usr/src/sys/sys/queue.h appears to be returning the value of > the first word of the last entry, which in my case (since the link > pointer is the first word in each of my chained structures) is _always_ > zero! What am I missing here? Is this possibly a bug or have I > missinterpreted what this macro is supposed to do? > > Thanks, > Bob > > -- > Bob Willcox hatred, n: > bob@VIEO.com A sentiment appropriate to the occasion of > Austin, TX another's superiority. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Bob Willcox hatred, n: bob@VIEO.com A sentiment appropriate to the occasion of Austin, TX another's superiority. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 10:15:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id B729237B4CF for ; Thu, 26 Oct 2000 10:15:05 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9QHF1N00900; Thu, 26 Oct 2000 19:15:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bob Willcox Cc: hackers list Subject: Re: STAILQ_LAST -- what should it return? In-Reply-To: Your message of "Thu, 26 Oct 2000 12:12:43 CDT." <20001026121243.A38987@luke.immure.com> Date: Thu, 26 Oct 2000 19:15:01 +0200 Message-ID: <898.972580501@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001026121243.A38987@luke.immure.com>, Bob Willcox writes: >To follow-up my own question, it appears that the STAILQ_LAST macro has >been changed (fixed) in -current to return the address of the last entry >(or NULL if the list is empty). Please don't MFS sys/queue.h from -current. It bogusly #includes . I have a patch which is in the finishing stages of brucification right now. >> #define STAILQ_LAST(head) (*(head)->stqh_last) >> -- 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 Thu Oct 26 20:24:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [203.2.75.115]) by hub.freebsd.org (Postfix) with ESMTP id 6A2C737B4C5 for ; Thu, 26 Oct 2000 20:24:08 -0700 (PDT) Received: from echidna.stu.cowan.edu.au (perax5-120.dialup.optusnet.com.au [198.142.91.120]) by mail05.syd.optusnet.com.au (8.9.3/8.9.3) with ESMTP id OAA26556; Fri, 27 Oct 2000 14:20:49 +1100 Message-ID: <39F8F53C.A500A16B@echidna.stu.cowan.edu.au> Date: Fri, 27 Oct 2000 11:23:40 +0800 From: Trent Nelson X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David van Deijk Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dir-listing bug in linux-emulation References: <39F82D3C.2532AEB7@student.tue.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David van Deijk wrote: > > Dear hackers. > > When I was running an linux program (soffice) i needed something of my > dos-partition. > Then i stumbled onto something I would call a "major" bug. > > I went to /dos/c (my first partition ) but saw only 6 files and 1 dir. > So i went for some exploring and this are my results: > PS. any other persons confirming (or not) this problem would be > welcome. Yup, I had the exact same problem running Star Office 5.2 in 5.0-current. Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 26 23:35:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f37.law4.hotmail.com [216.33.149.37]) by hub.freebsd.org (Postfix) with ESMTP id 869C337B479 for ; Thu, 26 Oct 2000 23:35:20 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 26 Oct 2000 23:35:20 -0700 Received: from 24.22.119.121 by lw4fd.law4.hotmail.msn.com with HTTP; Fri, 27 Oct 2000 06:35:20 GMT X-Originating-IP: [24.22.119.121] From: "Adam Klinkel" To: hackers@freebsd.org Subject: rlzdbase port 635 Date: Fri, 27 Oct 2000 06:35:20 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Oct 2000 06:35:20.0392 (UTC) FILETIME=[13CED480:01C03FE0] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scanning for open ports I found that port 635 rlzdbase port open. I've searched the web, and mailing lists but I could find any info on any deamon or program that ran on this port. So my question is, what is it used for. Thanks, Adam _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 0:46:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 9336937B479; Fri, 27 Oct 2000 00:46:08 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9R7k5k00392; Fri, 27 Oct 2000 00:46:05 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 00:46:05 -0700 (PDT) From: Matt Dillon Message-Id: <200010270746.e9R7k5k00392@earth.backplane.com> To: "freebsd-stable@FreeBSD.ORG" Cc: hackers@FreeBSD.ORG Subject: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is really weird. I have two valinux rackmount boxes, duel cpu's. I was testing the PXE stuff and booting one of the boxes regularly. All of a sudden every time I reboot I get: ... BIOS drive A: is disk0 int=00000000 err=00000000 efl=00030246 eip=00001d29 eax=00000000 ebs=00000390 ecx=00000000 edx=00000000 esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7 cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 BTX halted *All* the time. That is, everything was working fine, then nothing was working. Powering down doesn't help... now every boot comes up with the above error. I didn't change the boot image ... in fact, when I stuck the 4.1 CD in the now non-working machine, *IT's* bootloader also crashed every time too (and it worked previously). I messed around trying to track down where the loader was dying. I found it was dying in v86int(), called from bd_int13probe() in libi386/biosdisk.c. It seems to be dying in the BIOS itself. When I put a 'printf("X\n");' just before the v86int() call, the boot loader stopped crashing at that point and was able to load the kernel, but when it tried to run the kernel either it or the kernel crashed with the same BTX halted message. This is too weird. I put the second machine on my desk and started playing with it. After about the 30th reboot (where everything was working up until the 30th reboot), *IT* started doing the same thing! And it did the same thing when I stuck the 3.2 CD or the 4.1 CD in the box... both CD's crunched with the same BTX error. Anyone have any clue? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 1:13: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id B8C0837B479; Fri, 27 Oct 2000 01:12:54 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9R8Cpd02393; Fri, 27 Oct 2000 01:12:51 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 01:12:51 -0700 (PDT) From: Matt Dillon Message-Id: <200010270812.e9R8Cpd02393@earth.backplane.com> To: Paul Saab Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware References: <200010270746.e9R7k5k00392@earth.backplane.com> <20001027005935.A96133@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm just curious. How many disks are in this box? We saw something :similar here at work and it turned out that there were multiple disklabels :on the other disks and for somereason it was confusing the loader. :We dd'd the bad sections off and everything worked. : :paul I've got one IDE CDRom and two SCSI disks. I did play with the labels on those machines. I will try blowing them away. If I put a 'printf("XXX\n");' in front of every single v86int() call in libi386/biosdisk.c it doesn't crash on me. ... ( time passes ) ... ok... I cleared the disk labels using dd. Hoa! That seems to have fixed it allright! Very weird. I was sure I zero'd the labels before I populated the disk, but maybe not. Thanks much! I was tearing my hair out on this one... -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 1:22:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-14.dsl.snfc21.pacbell.net [63.202.178.14]) by hub.freebsd.org (Postfix) with ESMTP id 053D237B479; Fri, 27 Oct 2000 01:22:18 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id e9R8QWF01184; Fri, 27 Oct 2000 01:26:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010270826.e9R8QWF01184@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matt Dillon Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-reply-to: Your message of "Fri, 27 Oct 2000 01:12:51 PDT." <200010270812.e9R8Cpd02393@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 01:26:32 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :I'm just curious. How many disks are in this box? We saw something > :similar here at work and it turned out that there were multiple disklabels > :on the other disks and for somereason it was confusing the loader. > :We dd'd the bad sections off and everything worked. Are you sure it's confusing the loader? Matt's fault address puts it in the BIOS at 0xc800, which is probably the SCSI adapter's BIOS...> -- ... 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 Oct 27 1:25:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 05E7837B479; Fri, 27 Oct 2000 01:25:28 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 7D3D72B206; Fri, 27 Oct 2000 03:25:22 -0500 (CDT) Date: Fri, 27 Oct 2000 01:25:22 -0700 From: Paul Saab To: Mike Smith Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware Message-ID: <20001027012522.A96576@elvis.mu.org> References: <200010270812.e9R8Cpd02393@earth.backplane.com> <200010270826.e9R8QWF01184@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010270826.e9R8QWF01184@mass.osd.bsdi.com>; from msmith@mass.osd.bsdi.com on Fri, Oct 27, 2000 at 01:26:32AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith (msmith@mass.osd.bsdi.com) wrote: > > > > :I'm just curious. How many disks are in this box? We saw something > > :similar here at work and it turned out that there were multiple disklabels > > :on the other disks and for somereason it was confusing the loader. > > :We dd'd the bad sections off and everything worked. > > Are you sure it's confusing the loader? Matt's fault address puts it in > the BIOS at 0xc800, which is probably the SCSI adapter's BIOS...> I wasn't 100% involved with the problem. Peter looked into and notice the disks had bogus labels (sometimes up to 3 labels on 1 disk) and when he removed them, the machines were happy again. We never looked into further because we just didn't have the time. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 2: 8:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 5C65F37B4CF for ; Fri, 27 Oct 2000 02:08:42 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id CAA14881; Fri, 27 Oct 2000 02:09:09 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp05.primenet.com, id smtpdAAAriaWcD; Fri Oct 27 02:09:05 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA26473; Fri, 27 Oct 2000 02:08:36 -0700 (MST) From: Terry Lambert Message-Id: <200010270908.CAA26473@usr09.primenet.com> Subject: Re: rlzdbase port 635 To: hotsmak@hotmail.com (Adam Klinkel) Date: Fri, 27 Oct 2000 09:08:33 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Adam Klinkel" at Oct 27, 2000 06:35:20 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Scanning for open ports I found that port 635 rlzdbase port open. I've > searched the web, and mailing lists but I could find any info on any deamon > or program that ran on this port. So my question is, what is it used for. Contact: Michael Ginn NB: http://www.isi.edu/in-notes/iana/assignments/port-numbers is your friend. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 2:12:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 7435337B661; Fri, 27 Oct 2000 02:12:18 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id CAA01298; Fri, 27 Oct 2000 02:09:08 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpdAAAZXaaDc; Fri Oct 27 02:09:04 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA26546; Fri, 27 Oct 2000 02:12:10 -0700 (MST) From: Terry Lambert Message-Id: <200010270912.CAA26546@usr09.primenet.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware To: dillon@earth.backplane.com (Matt Dillon) Date: Fri, 27 Oct 2000 09:12:10 +0000 (GMT) Cc: freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG In-Reply-To: <200010270746.e9R7k5k00392@earth.backplane.com> from "Matt Dillon" at Oct 27, 2000 12:46:05 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was testing the PXE stuff and booting one of the boxes regularly. > All of a sudden every time I reboot I get: > > ... > BIOS drive A: is disk0 > > int=00000000 err=00000000 efl=00030246 eip=00001d29 > eax=00000000 ebs=00000390 ecx=00000000 edx=00000000 > esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c > cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7 > cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 > BTX halted > > *All* the time. That is, everything was working fine, then nothing was > working. Powering down doesn't help... now every boot comes up with the > above error. I didn't change the boot image ... in fact, when I stuck > the 4.1 CD in the now non-working machine, *IT's* bootloader also > crashed every time too (and it worked previously). Too bad you killed your test case, or it might have gotton fixed; you made an image backup before you blew away the labels, or not? I think you might want to consider putting a DELAY after the BIOS call itself; perhaps some device that was poked by the BIOS is latching the bus, and you are doing an INB or OUTB too soon after the fact (but that's just my gut reaction to a crash following a BIOS call... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 2:15: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 9882037B479; Fri, 27 Oct 2000 02:14:51 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9R9E5Y03182; Fri, 27 Oct 2000 02:14:05 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 02:14:05 -0700 (PDT) From: Matt Dillon Message-Id: <200010270914.e9R9E5Y03182@earth.backplane.com> To: Mike Smith Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware References: <200010270826.e9R8QWF01184@mass.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> :I'm just curious. How many disks are in this box? We saw something :> :similar here at work and it turned out that there were multiple disklabels :> :on the other disks and for somereason it was confusing the loader. :> :We dd'd the bad sections off and everything worked. : :Are you sure it's confusing the loader? Matt's fault address puts it in :the BIOS at 0xc800, which is probably the SCSI adapter's BIOS...> I'm confusing something. If I clear the disk by dd'ing it, the machine boots (diskless) fine. If I do this: dd if=/dev/zero of=/dev/da0 bs=32k count=4 dd if=/dev/zero of=/dev/da1 bs=32k count=4 disklabel -w -r da0 auto disklabel -w -r da1 auto reboot The machine will boot diskless just fine. fdisk reports: Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 731/ sector 63/ head 254 ***************************************************** If I install boot blocks it seems to whack the partition info, and if I reboot after this point the machine is fracked -- the boot loader blows up in the BIOS (i.e. the BIOS blows up) trying to scan the disks. disklabel -B da0 disklabel -B da1 fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 reboot... BEWM!!!!!!! ***************************************************** HEEELP! Why is the simple installation of boot blocks by disklabel screwing up the partition table? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 2:30:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E06B837B479; Fri, 27 Oct 2000 02:30:02 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9R9U1X03815; Fri, 27 Oct 2000 02:30:01 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 02:30:01 -0700 (PDT) From: Matt Dillon Message-Id: <200010270930.e9R9U1X03815@earth.backplane.com> To: Terry Lambert Cc: freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware References: <200010270912.CAA26546@usr09.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto' 000000f0 66 8b 46 08 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 |f.F.Rf...f1.f...| 00000100 eb 88 d5 43 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 |...C0.f....Zf=..| 00000110 00 00 fb 77 44 86 c4 c0 c8 02 08 e8 40 91 88 fe |...wD.......@...| 00000120 28 e0 8a 66 02 38 e0 72 02 88 e0 bf 05 00 c4 5e |(..f.8.r.......^| 00000130 04 50 b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 |.P....[s.Ot.0...| 00000140 93 eb eb 0f b6 c3 01 46 08 73 03 ff 46 0a d0 e3 |.......F.s..F...| 00000150 00 5e 05 28 46 02 77 88 c3 2e f6 06 99 08 80 0f |.^.(F.w.........| 00000160 84 79 ff bb aa 55 52 b4 41 cd 13 5a 0f 82 6f ff |.y...UR.A..Z..o.| 00000170 81 fb 55 aa 0f 85 64 ff f6 c1 01 0f 84 5d ff 89 |..U...d......]..| 00000180 ee b4 42 cd 13 c3 52 65 61 64 00 42 6f 6f 74 00 |..B...Read.Boot.| 00000190 20 65 72 72 6f 72 0d 0a 00 80 90 90 90 90 90 90 | error..........| 000001a0 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 |................| 000001b0 90 90 90 90 90 90 90 90 90 90 90 90 90 90 00 00 |................| 000001c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 00 |................| 000001f0 01 00 a5 ff ff ff 00 00 00 00 50 c3 00 00 55 aa |..........P...U.| fdisk da0 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Raw data on disk after 'fdisk -I da0' 000000f0 65 6d 00 4d 69 73 73 69 6e 67 20 6f 70 65 72 61 |em.Missing opera| 00000100 74 69 6e 67 20 73 79 73 74 65 6d 00 00 00 00 00 |ting system.....| 00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01 |................| 000001c0 01 00 a5 fe bf db 3f 00 00 00 9d 8f 8b 08 00 00 |......?.........| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| fdisk da0 The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 731/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 2:44:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heechee.tobez.org (238.adsl0.ryv.worldonline.dk [213.237.10.238]) by hub.freebsd.org (Postfix) with ESMTP id 03AD037B479; Fri, 27 Oct 2000 02:44:47 -0700 (PDT) Received: by heechee.tobez.org (Postfix, from userid 1001) id 4CEF354D2; Fri, 27 Oct 2000 11:44:29 +0200 (CEST) Date: Fri, 27 Oct 2000 11:44:29 +0200 From: Anton Berezin To: Matt Dillon Cc: "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware Message-ID: <20001027114429.B69762@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Matt Dillon , "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.ORG References: <200010270746.e9R7k5k00392@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010270746.e9R7k5k00392@earth.backplane.com>; from dillon@earth.backplane.com on Fri, Oct 27, 2000 at 12:46:05AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 27, 2000 at 12:46:05AM -0700, Matt Dillon wrote: > This is really weird. I have two valinux rackmount boxes, duel cpu's. > > I was testing the PXE stuff and booting one of the boxes regularly. > All of a sudden every time I reboot I get: > > ... > BIOS drive A: is disk0 > > int=00000000 err=00000000 efl=00030246 eip=00001d29 > eax=00000000 ebs=00000390 ecx=00000000 edx=00000000 > esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c > cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7 > cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 > BTX halted > > *All* the time. That is, everything was working fine, then nothing was > working. Powering down doesn't help... now every boot comes up with the > above error. I didn't change the boot image ... in fact, when I stuck > the 4.1 CD in the now non-working machine, *IT's* bootloader also > crashed every time too (and it worked previously). > > I messed around trying to track down where the loader was dying. I > found it was dying in v86int(), called from bd_int13probe() in > libi386/biosdisk.c. It seems to be dying in the BIOS itself. It looks pretty similar to famous BIOS virus protection thingy. Can this be the case? Cheers, %Anton. -- and would be a nice addition to HTML specification. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 3: 3:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from siri.nordier.com (c3-dbn-109.dial-up.net [196.33.200.109]) by hub.freebsd.org (Postfix) with ESMTP id 03B2737B479; Fri, 27 Oct 2000 03:03:31 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id MAA24624; Fri, 27 Oct 2000 12:03:06 +0200 (SAST) From: Robert Nordier Message-Id: <200010271003.MAA24624@siri.nordier.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware To: dillon@earth.backplane.com (Matt Dillon) Date: Fri, 27 Oct 2000 12:03:06 +0200 (SAST) Cc: tlambert@primenet.com (Terry Lambert), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG In-Reply-To: <200010270930.e9R9U1X03815@earth.backplane.com> from "Matt Dillon" at Oct 27, 2000 02:30:01 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto' If you added "auto" after the "disklabel -B", that may be your problem. -- Robert Nordier rnordier@nordier.com rnordier@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 Oct 27 3:18:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw3.netvision.net.il (mailgw3.netvision.net.il [194.90.1.11]) by hub.freebsd.org (Postfix) with ESMTP id CF23937B479; Fri, 27 Oct 2000 03:18:33 -0700 (PDT) Received: from phpStop.com (ras3-p153.hfa.netvision.net.il [62.0.147.153]) by mailgw3.netvision.net.il (8.9.3/8.9.3) with ESMTP id MAA18293; Fri, 27 Oct 2000 12:17:27 +0200 (IST) Message-ID: <39F955F2.49FA8BE0@phpStop.com> Date: Fri, 27 Oct 2000 12:16:18 +0200 From: "Stop here. Start everywhere." Organization: phpStop.com X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: ipfw security. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I thought I would spread this to the mailing list just in case no one knew about it, and ask whether ipfw does implement all of the mentioned requirements: ftp://ftp.isi.edu/in-notes/rfc2979.txt Well, does ipfw support all of it, and if not, what doesn't it support? Thanks in advance. /John -- Regards, phpStop.com http://www.phpstop.com/ Stop here. Start everywhere. mailto:info@phpstop.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 3:34:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 4F2F037B479; Fri, 27 Oct 2000 03:34:25 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RAY9J04147; Fri, 27 Oct 2000 03:34:09 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 03:34:09 -0700 (PDT) From: Matt Dillon Message-Id: <200010271034.e9RAY9J04147@earth.backplane.com> To: Robert Nordier Cc: tlambert@primenet.com (Terry Lambert), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware References: <200010271003.MAA24624@siri.nordier.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto' : :If you added "auto" after the "disklabel -B", that may be your problem. : :-- :Robert Nordier type-o. No auto for the -B still blows up the dos partition table. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 4:11:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from siri.nordier.com (c2-dbn-81.dial-up.net [196.34.155.209]) by hub.freebsd.org (Postfix) with ESMTP id A78B037B479; Fri, 27 Oct 2000 04:11:16 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id NAA26088; Fri, 27 Oct 2000 13:10:56 +0200 (SAST) From: Robert Nordier Message-Id: <200010271110.NAA26088@siri.nordier.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware To: dillon@earth.backplane.com (Matt Dillon) Date: Fri, 27 Oct 2000 13:10:56 +0200 (SAST) Cc: tlambert@primenet.com (Terry Lambert), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG In-Reply-To: <200010271034.e9RAY9J04147@earth.backplane.com> from "Matt Dillon" at Oct 27, 2000 03:34:09 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > : > :> Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto' > : > :If you added "auto" after the "disklabel -B", that may be your problem. > : > :-- > :Robert Nordier > > type-o. No auto for the -B still blows up the dos partition > table. Just doing the disklabel -w -r followed by the disklabel -B is creating a dangerously dedicated disk, which your BIOS apparently doesn't like. (See the first hex dump you did, where boot1 has ended up in the MBR.) That's why installing boot blocks is messing with the partition table, to answer the question you asked elsewhere. You need to dd and fdisk before the disklabel commands, which will give you a standard partition table (at the cost of 63 sectors of disk space). -- Robert Nordier rnordier@nordier.com rnordier@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 Oct 27 5: 4:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4FDE637B479; Fri, 27 Oct 2000 05:04:23 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Oct 2000 12:42:30 +0100 (BST) Date: Fri, 27 Oct 2000 12:42:29 +0100 From: David Malone To: "Stop here. Start everywhere." Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ipfw security. Message-ID: <20001027124229.A52457@walton.maths.tcd.ie> References: <39F955F2.49FA8BE0@phpStop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F955F2.49FA8BE0@phpStop.com>; from feedback@phpStop.com on Fri, Oct 27, 2000 at 12:16:18PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 27, 2000 at 12:16:18PM +0200, Stop here. Start everywhere. wrote: > I thought I would spread this to the mailing list just in case no one > knew about it, and ask whether ipfw does implement all of the mentioned > requirements: > > ftp://ftp.isi.edu/in-notes/rfc2979.txt > > Well, does ipfw support all of it, and if not, what doesn't it support? Ipfw allows you to specify what action to take on the recept of certain packets. As such it compliance with that RFC depends on your intended security policy and the set of rules you define using ipfw. It is certainly possibly to create complient and noncomplient rule-sets. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 5:40:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id ECD3637B479 for ; Fri, 27 Oct 2000 05:40:50 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 27 Oct 2000 12:40:50 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D2611@erlangen01.atrada.de> From: Alexander Maret To: "'freebsd-hackers@freebsd.org'" Subject: Accessing the tty structure of an opened device Date: Fri, 27 Oct 2000 14:40:38 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is it possible to access the tty structure of an opened device directly? Background: I'm trying to sense the DCD state of a serial port for getting the pulses and spaces of a simple IR device. I could use ioctl commands to get the current state but then I would have to check the state continously which uses too much cpu time. What I want to do is something like that: - open the serial port - get the tty structure of the opened device - define something like that: #define TSA_CARR_OFF(tp) (!((void *)&(tp)->t_rawq)) and then wait for TSA_CARR_OFF and TSA_CARR_ON for example: - get current DCD state if DCD is up error = tsleep(TSA_CARR_OFF(tp), .....) to get a wakeup on DCD down. Is this possible and if yes where do I get access to the tty structure of my opened serial port? Unfortunately I'm no kernel hacker so be patient with me. I tried to find examples within the source code and in "The design and implementation of the 4.4 BSD OS" but couldn't find a good solution. An example code how to access the tty structure would be great. Perhaps you can point me to the right files within the kernel sources. Thanks in advance, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 5:46:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id CE88C37B479 for ; Fri, 27 Oct 2000 05:46:27 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9RCkPN10393; Fri, 27 Oct 2000 14:46:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device In-Reply-To: Your message of "Fri, 27 Oct 2000 14:40:38 +0200." <58A002A02C5ED311812E0050044517F00D2611@erlangen01.atrada.de> Date: Fri, 27 Oct 2000 14:46:25 +0200 Message-ID: <10391.972650785@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <58A002A02C5ED311812E0050044517F00D2611@erlangen01.atrada.de>, Alexa nder Maret writes: >Hi, > >is it possible to access the tty structure of an opened >device directly? > >Background: >I'm trying to sense the DCD state of a serial port for >getting the pulses and spaces of a simple IR device. We have some ioctls which allow you to do that, some of them work. Look in , I belive I have used TIOCMODG() at one point in time. -- 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 Fri Oct 27 5:59:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id B93FC37B479 for ; Fri, 27 Oct 2000 05:59:44 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 27 Oct 2000 12:59:44 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D2612@erlangen01.atrada.de> From: Alexander Maret To: 'Poul-Henning Kamp' Cc: "'freebsd-hackers@freebsd.org'" Subject: AW: Accessing the tty structure of an opened device Date: Fri, 27 Oct 2000 14:59:41 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > Subject: Re: Accessing the tty structure of an opened device > > > >is it possible to access the tty structure of an opened > >device directly? > > > >Background: > >I'm trying to sense the DCD state of a serial port for > >getting the pulses and spaces of a simple IR device. > > We have some ioctls which allow you to do that, some of them work. > > Look in , I belive I have used TIOCMODG() at one > point in time. Thanks for your answer but unfortunately you misunderstood my intention (probably because of my bad english). I already saw that I can get the state of the DCD line via ioctl(). But to really get all pulses and spaces of the IR device I would have to check DCD continously. What I need is something to get a signal/intr/wakeup as soon as dcd changes. My hope was that I could define a TSA_CARR_OFF and then do a tsleep to get a wakeup as soon as DCD goes down. On DCD down do a tsleep untill it gets up again. Unfortunately to go tsleep and wait for TSA_CARR_OFF/ON I have to get access to the tty structure of my serial port. Thanks for your help, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 6: 2:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 87F4637B479 for ; Fri, 27 Oct 2000 06:02:13 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9RD2AN10500; Fri, 27 Oct 2000 15:02:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: AW: Accessing the tty structure of an opened device In-Reply-To: Your message of "Fri, 27 Oct 2000 14:59:41 +0200." <58A002A02C5ED311812E0050044517F00D2612@erlangen01.atrada.de> Date: Fri, 27 Oct 2000 15:02:10 +0200 Message-ID: <10498.972651730@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <58A002A02C5ED311812E0050044517F00D2612@erlangen01.atrada.de>, Alexa nder Maret writes: >> From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] >> Subject: Re: Accessing the tty structure of an opened device >> >> >> >is it possible to access the tty structure of an opened >> >device directly? >> > >> >Background: >> >I'm trying to sense the DCD state of a serial port for >> >getting the pulses and spaces of a simple IR device. >> >> We have some ioctls which allow you to do that, some of them work. >> >> Look in , I belive I have used TIOCMODG() at one >> point in time. > >Thanks for your answer but unfortunately you misunderstood my >intention (probably because of my bad english). >I already saw that I can get the state of the DCD line via >ioctl(). But to really get all pulses and spaces of the IR >device I would have to check DCD continously. What I need >is something to get a signal/intr/wakeup as soon as dcd changes. How fast do these pulses arrive ? Consider using the PPS-API for that: -- 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 Fri Oct 27 6: 5:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id BC3CF37B4C5 for ; Fri, 27 Oct 2000 06:05:33 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 27 Oct 2000 13:05:33 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D2613@erlangen01.atrada.de> From: Alexander Maret To: 'Poul-Henning Kamp' Cc: "'freebsd-hackers@freebsd.org'" Subject: AW: AW: Accessing the tty structure of an opened device Date: Fri, 27 Oct 2000 15:05:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > Subject: Re: AW: Accessing the tty structure of an opened device > > > How fast do these pulses arrive ? Consider using the > PPS-API for that: > the time between a pulse and a space often only takes a few milliseconds. I have to meassure that with gettimeofday(). Greetings, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 6:10:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 39A2837B6C6 for ; Fri, 27 Oct 2000 06:08:36 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9RD8YN10555; Fri, 27 Oct 2000 15:08:34 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: AW: AW: Accessing the tty structure of an opened device In-Reply-To: Your message of "Fri, 27 Oct 2000 15:05:29 +0200." <58A002A02C5ED311812E0050044517F00D2613@erlangen01.atrada.de> Date: Fri, 27 Oct 2000 15:08:34 +0200 Message-ID: <10553.972652114@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <58A002A02C5ED311812E0050044517F00D2613@erlangen01.atrada.de>, Alexa nder Maret writes: >> From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] >> Subject: Re: AW: Accessing the tty structure of an opened device >> >> >> How fast do these pulses arrive ? Consider using the >> PPS-API for that: >> > >the time between a pulse and a space often only takes >a few milliseconds. I have to meassure that with >gettimeofday(). You will need to do this in a device driver, there is no way you can reliably measure that from userland. Trust me on this: I've tried. -- 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 Fri Oct 27 6:15: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-14.dsl.snfc21.pacbell.net [63.202.178.14]) by hub.freebsd.org (Postfix) with ESMTP id 5C0A837B479 for ; Fri, 27 Oct 2000 06:15:04 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id e9RD6hF00416; Fri, 27 Oct 2000 06:06:44 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010271306.e9RD6hF00416@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Maret Cc: "'Poul-Henning Kamp'" , "'freebsd-hackers@freebsd.org'" Subject: Re: AW: Accessing the tty structure of an opened device In-reply-to: Your message of "Fri, 27 Oct 2000 14:59:41 +0200." <58A002A02C5ED311812E0050044517F00D2612@erlangen01.atrada.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 06:06:43 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for your answer but unfortunately you misunderstood my > intention (probably because of my bad english). > I already saw that I can get the state of the DCD line via > ioctl(). But to really get all pulses and spaces of the IR > device I would have to check DCD continously. What I need > is something to get a signal/intr/wakeup as soon as dcd changes. > > My hope was that I could define a TSA_CARR_OFF and then do > a tsleep to get a wakeup as soon as DCD goes down. On DCD down > do a tsleep untill it gets up again. > > Unfortunately to go tsleep and wait for TSA_CARR_OFF/ON I have to > get access to the tty structure of my serial port. Stop trying to do this; you cannot poll the serial line at anything like a useful speed to perform IR decoding. The entire approach you're trying to take is unworkable. -- ... 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 Oct 27 6:29:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id 7D1AD37B479 for ; Fri, 27 Oct 2000 06:29:54 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 27 Oct 2000 13:29:54 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de> From: Alexander Maret To: 'Poul-Henning Kamp' Cc: "'msmith@mass.osd.bsdi.com'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device Date: Fri, 27 Oct 2000 15:29:50 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Ursprungliche Nachricht----- > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > Subject: Re: Accessing the tty structure of an opened device > > You will need to do this in a device driver, there is no way you > can reliably measure that from userland. > > Trust me on this: I've tried. That's what I wanted to do. I wanted to write a character device which on read() passes the last IR-code. Well as Mike Smith told me: "you cannot poll the serial line at anything like a useful speed to perform IR decoding" my hopes are all gone to get a simple solution. Do I have to write my own serial driver to get what I want or is it possible to use functions of the "build in" serial device driver? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 6:34:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 79C0837B4D7 for ; Fri, 27 Oct 2000 06:34:26 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9RDXaN10773; Fri, 27 Oct 2000 15:33:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Maret Cc: "'msmith@mass.osd.bsdi.com'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device In-Reply-To: Your message of "Fri, 27 Oct 2000 15:29:50 +0200." <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de> Date: Fri, 27 Oct 2000 15:33:36 +0200 Message-ID: <10771.972653616@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de>, Alexa nder Maret writes: >Do I have to write my own serial driver to get what I want or >is it possible to use functions of the "build in" serial >device driver? You may be able to do it as a "line discipline. I'm not quite sure if it is possible. If not, a (hardware-) device driver is your only hope. -- 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 Fri Oct 27 6:53:55 2000 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 B122E37B479; Fri, 27 Oct 2000 06:53:51 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13p9x6-0000om-00; Fri, 27 Oct 2000 15:53:48 +0200 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 13p9x5-0002oM-00; Fri, 27 Oct 2000 15:53:47 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Matt Dillon Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-reply-to: Your message of Fri, 27 Oct 2000 00:46:05 -0700 (PDT) . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 15:53:47 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010270746.e9R7k5k00392@earth.backplane.com>you write: } This is really weird. I have two valinux rackmount boxes, duel cpu's. } } I was testing the PXE stuff and booting one of the boxes regularly. } All of a sudden every time I reboot I get: } i've seen the same, i just reboot it, and it works. sometimes, while the kernel is doing it's init stuff it panics. i haven't seen it fail more than once in a row, so i was thinking maybe some network error that was not dealt properly. btw, the boxes are DELL. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 7: 2:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 592EF37B479; Fri, 27 Oct 2000 07:02:35 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 08C6B2B21D; Fri, 27 Oct 2000 09:02:29 -0500 (CDT) Date: Fri, 27 Oct 2000 07:02:29 -0700 From: Paul Saab To: Danny Braniss Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware Message-ID: <20001027070229.A3341@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Fri, Oct 27, 2000 at 03:53:47PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > In message <200010270746.e9R7k5k00392@earth.backplane.com>you write: > } This is really weird. I have two valinux rackmount boxes, duel cpu's. > } > } I was testing the PXE stuff and booting one of the boxes regularly. > } All of a sudden every time I reboot I get: > } > > i've seen the same, i just reboot it, and it works. sometimes, while > the kernel is doing it's init stuff it panics. i haven't seen it fail > more than once in a row, so i was thinking maybe some network error > that was not dealt properly. btw, the boxes are DELL. He was not seeing a PXE bug, it was a loader issue with the BIOS. The PXE bug you are seeing is with anything build 078 or earlier. Intel has a bug in their rom which they fixed back in March of this year. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 7:12:17 2000 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 58C2037B4C5; Fri, 27 Oct 2000 07:12:13 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13pAEq-00010a-00; Fri, 27 Oct 2000 16:12:08 +0200 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 13pAEp-0002pS-00; Fri, 27 Oct 2000 16:12:07 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: freebsd-stable@freebsd.org, hackers@freebsd.org Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-reply-to: Your message of Fri, 27 Oct 2000 07:02:29 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 16:12:07 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001027070229.A3341@elvis.mu.org>you write: }Danny Braniss (danny@cs.huji.ac.il) wrote: } }He was not seeing a PXE bug, it was a loader issue with the BIOS. }The PXE bug you are seeing is with anything build 078 or earlier. }Intel has a bug in their rom which they fixed back in March of this year. } i am not 100% sure, but i think it also happend with 3com. i'll do some more testing next week. thanks for the tip, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 7:30:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 389FC37B479 for ; Fri, 27 Oct 2000 07:30:48 -0700 (PDT) Received: from mbabane-15.budapest.interware.hu ([195.70.60.143] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13pAWf-0004EH-00; Fri, 27 Oct 2000 16:30:34 +0200 Message-ID: <39F99180.AE1F99E4@elischer.org> Date: Fri, 27 Oct 2000 07:30:24 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Maret Cc: 'Poul-Henning Kamp' , "'msmith@mass.osd.bsdi.com'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device References: <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Maret wrote: > > > -----Ursprungliche Nachricht----- > > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > > Subject: Re: Accessing the tty structure of an opened device > > > > You will need to do this in a device driver, there is no way you > > can reliably measure that from userland. > > > > Trust me on this: I've tried. > > That's what I wanted to do. I wanted to write a character device > which on read() passes the last IR-code. > > Well as Mike Smith told me: "you cannot poll the serial line at > anything like a useful speed to perform IR decoding" my hopes are > all gone to get a simple solution. > > Do I have to write my own serial driver to get what I want or > is it possible to use functions of the "build in" serial > device driver? look at the pcaudio driver it uses a 16KHz clock to poll out audio.. You can use a similar method to poll in data with little system load.... As for the 'build in' serial driver, it depends on wht your data will look like.... Julian > > Alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 7:32:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-14.dsl.snfc21.pacbell.net [63.202.178.14]) by hub.freebsd.org (Postfix) with ESMTP id 9767B37B4CF for ; Fri, 27 Oct 2000 07:32:35 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id e9REZHF00426; Fri, 27 Oct 2000 07:35:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010271435.e9REZHF00426@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Maret Cc: "'Poul-Henning Kamp'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device In-reply-to: Your message of "Fri, 27 Oct 2000 15:29:50 +0200." <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 07:35:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That's what I wanted to do. I wanted to write a character device > which on read() passes the last IR-code. > > Well as Mike Smith told me: "you cannot poll the serial line at > anything like a useful speed to perform IR decoding" my hopes are > all gone to get a simple solution. > > Do I have to write my own serial driver to get what I want or > is it possible to use functions of the "build in" serial > device driver? You will need to write your own. Even then, polling an inbound signal is not going to be reliable. Use a UART or some other appropriate hardware decoder. -- ... 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 Oct 27 8:15:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.lpa.com (mail.lpa.com [12.3.233.134]) by hub.freebsd.org (Postfix) with ESMTP id E2E7437B479; Fri, 27 Oct 2000 08:15:42 -0700 (PDT) Received: from xelus.com ([10.4.5.232]) by zeus.lpa.com (Netscape Messaging Server 4.15) with ESMTP id G33H1700.9FA; Fri, 27 Oct 2000 11:15:07 -0400 Date: Fri, 27 Oct 2000 11:15:39 -0400 From: Shawn Halpenny Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released Message-ID: <20001027111539.A391@nightrain.xelus.com> References: <39F46B08.808132D2@owp.csus.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F46B08.808132D2@owp.csus.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of smbfs, has anyone else run into an odd bug using it in 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the directories (e.g. using 'ls') for an smbfs mount after a period of time during which there were no accesses across that mount point (e.g. mount, don't touch it for an hour, then try 'df'), my machine will reboot after a few seconds. No panic message or anything--it's just like I pressed the reset button. Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' to display 'broken pipe' and I could remount that share and things would be fine. 'df' would still work without any noticeable difference. Don't have any idea about starting to troubleshoot this one. -- Shawn Halpenny | Maniacal@I Ache, Ohm | "Universal Danger!" +- - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - \ | vi:G3kfM~lxfAPXh~l~2x2FirllpfcxlrifaprmfOX~Xp2hr.lrcelyl2p - - - - - - - -| fU~X~refsPprnlxppri2lxlpr,pFrpprrfaPlpfiprgllxp~3Xlpfndw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 8:23:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id EBCCF37B479 for ; Fri, 27 Oct 2000 08:23:52 -0700 (PDT) Received: (qmail 17572 invoked by uid 1000); 27 Oct 2000 15:23:48 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2000 15:23:48 -0000 Date: Fri, 27 Oct 2000 10:23:48 -0500 (CDT) From: Mike Silbersack To: Mike Smith Cc: Alexander Maret , 'Poul-Henning Kamp' , "'freebsd-hackers@freebsd.org'" Subject: Re: AW: Accessing the tty structure of an opened device In-Reply-To: <200010271306.e9RD6hF00416@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Mike Smith wrote: > Stop trying to do this; you cannot poll the serial line at anything like > a useful speed to perform IR decoding. The entire approach you're trying > to take is unworkable. Hm, it seems like every motherboard made in the last few years has some hookup for an IR port that will act as com 2. Are the parts for those available? (Or would alexander be able to adapt his IR device to that interface somehow?) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 10: 2: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 5110737B479; Fri, 27 Oct 2000 10:02:02 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA16720; Fri, 27 Oct 2000 12:01:49 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 27 Oct 2000 12:01:48 -0500 (CDT) From: Chris Dillon To: Shawn Halpenny Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <20001027111539.A391@nightrain.xelus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Shawn Halpenny wrote: > Speaking of smbfs, has anyone else run into an odd bug using it in > 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the > directories (e.g. using 'ls') for an smbfs mount after a period > of time during which there were no accesses across that mount > point (e.g. mount, don't touch it for an hour, then try 'df'), my > machine will reboot after a few seconds. No panic message or > anything--it's just like I pressed the reset button. I've not had it panic on me under those situations, but it does do weird things. I think I'd either get an empty directory listing, or it would say "path too long" or something like that and any relative path stuff like "cd .." wouldn't work. I'd have to give a full path to get where I wanted to go, even if it was the _same_ directory. I've also had cases where I was drilling down through the directories in the Save File dialog in Navigator and I would get incomplete directory listings. Also, it seems, if I try to save a file that way, the file ends up corrupted. If I save it to a local filesystem and then move it over manually, its fine. Other than those small annoyances, it seems to work great. Oh yeah, I've noticed one more thing. When you're at the root of a mount, you can cd into a directory using any case, but if you get the case wrong, you don't get a listing. Here's an example: root@tech43 [/smb/rsisfs1/d]# ls ADMINNOTIFY/ REB98/ SECURITY/ SHARES/ tmpacls.bat* CPQIS1/ RECYCLER/ SETACLS.BAT* TEMP/ root@tech43 [/smb/rsisfs1/d]# cd reb98 root@tech43 [/smb/rsisfs1/d/reb98]# ls root@tech43 [/smb/rsisfs1/d/reb98]# cd ../REB98 root@tech43 [/smb/rsisfs1/d/REB98]# ls ARCHIVE/ PACKAGES/ AUTOEXEC.BAT* PCRDIST/ BATCH/ REBMIR.LOG* ... and so on ... root@tech43 [/smb/rsisfs1/d/REB98]# cd packages packages: No such file or directory. root@tech43 [/smb/rsisfs1/d/REB98]# cd PACKAGES root@tech43 [/smb/rsisfs1/d/REB98/PACKAGES]# So... the case-insensitivity only happens at the root of the mount. Should it happen everywhere? It'd be nice if it did. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. 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 Oct 27 10:37:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 011DA37B4C5; Fri, 27 Oct 2000 10:37:10 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RHaXf83496; Fri, 27 Oct 2000 10:36:33 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010270746.e9R7k5k00392@earth.backplane.com> Date: Fri, 27 Oct 2000 10:37:23 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: RE: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org Cc: hackers@FreeBSD.org, "freebsd-stable@FreeBSD.ORG" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Matt Dillon wrote: > This is really weird. I have two valinux rackmount boxes, duel cpu's. > > I was testing the PXE stuff and booting one of the boxes regularly. > All of a sudden every time I reboot I get: > > ... > BIOS drive A: is disk0 > > int=00000000 err=00000000 efl=00030246 eip=00001d29 > eax=00000000 ebs=00000390 ecx=00000000 edx=00000000 > esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c > cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7 > cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 > BTX halted Int 00 is a divide by zero fault. Note that %eax is zero. Do you have dangerously dedicated mode on by chance? Some SCSI BIOS's _will_ crash with this if you use dangerously dedicated mode. -- 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 Oct 27 11: 4:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 019BE37B479; Fri, 27 Oct 2000 11:04:26 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RI3wK05949; Fri, 27 Oct 2000 11:03:58 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 11:03:58 -0700 (PDT) From: Matt Dillon Message-Id: <200010271803.e9RI3wK05949@earth.backplane.com> To: Paul Saab Cc: Danny Braniss , freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware References: <20001027070229.A3341@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Danny Braniss (danny@cs.huji.ac.il) wrote: :> In message <200010270746.e9R7k5k00392@earth.backplane.com>you write: :> } This is really weird. I have two valinux rackmount boxes, duel cpu's. :> } :> } I was testing the PXE stuff and booting one of the boxes regularly. :> } All of a sudden every time I reboot I get: :> } :> :> i've seen the same, i just reboot it, and it works. sometimes, while :> the kernel is doing it's init stuff it panics. i haven't seen it fail :> more than once in a row, so i was thinking maybe some network error :> that was not dealt properly. btw, the boxes are DELL. : :He was not seeing a PXE bug, it was a loader issue with the BIOS. :The PXE bug you are seeing is with anything build 078 or earlier. :Intel has a bug in their rom which they fixed back in March of this year. : :-- :Paul Saab :Technical Yahoo Right. It isn't PXE. PXE works fine. I'm starting to figure out what is going on. If I create a 'dangerously dedicated' parittion, the BIOS drops dead when the loader tries to scan it. If I create a normal fdisk partition, the BIOS works, but disklabel will not let me label the fdisk partition and I have no clue as to why not! fdisk -I da0 (init a real freebsd-dedicated DOS partition) reboot (reboot just to be sure) (BIOS does NOT crash with a real dos partition table) fdisk da0 (see output below) The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 731/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: 10:/root# disklabel -w -r da0s1 auto (label it) 10:/root# disklabel -w -r da0s1 auto Oct 27 11:00:35 10 /kernel: da0: cannot find label (no disk label) Oct 27 11:00:35 10 /kernel: da0s1: cannot find label (no disk label) Oct 27 11:00:35 10 /kernel: da0: cannot find label (no disk label) Oct 27 11:00:35 10 /kernel: da0s1: cannot find label (no disk label) disklabel: ioctl DIOCGDINFO: Invalid argument disklabel: auto: unknown disk type I don't understand why it won't let me label the fdisk partition. If only I could label the real partition 'fdisk -I' created, I think the system will work. The question is, why is disklabel failing above? It shouldn't be failing..it should let me label da0s1. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 11:14:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 73A2137B4CF; Fri, 27 Oct 2000 11:14:01 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RIDOf84634; Fri, 27 Oct 2000 11:13:24 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010271803.e9RI3wK05949@earth.backplane.com> Date: Fri, 27 Oct 2000 11:14:14 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, Danny Braniss , Paul Saab Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Matt Dillon wrote: >:Danny Braniss (danny@cs.huji.ac.il) wrote: >:> In message <200010270746.e9R7k5k00392@earth.backplane.com>you write: >:> } This is really weird. I have two valinux rackmount boxes, duel cpu's. >:> } >:> } I was testing the PXE stuff and booting one of the boxes regularly. >:> } All of a sudden every time I reboot I get: >:> } >:> >:> i've seen the same, i just reboot it, and it works. sometimes, while >:> the kernel is doing it's init stuff it panics. i haven't seen it fail >:> more than once in a row, so i was thinking maybe some network error >:> that was not dealt properly. btw, the boxes are DELL. >: >:He was not seeing a PXE bug, it was a loader issue with the BIOS. >:The PXE bug you are seeing is with anything build 078 or earlier. >:Intel has a bug in their rom which they fixed back in March of this year. >: >:-- >:Paul Saab >:Technical Yahoo > > Right. It isn't PXE. PXE works fine. > > I'm starting to figure out what is going on. If I create a > 'dangerously dedicated' parittion, the BIOS drops dead when the > loader tries to scan it. > > If I create a normal fdisk partition, the BIOS works, but disklabel > will not let me label the fdisk partition and I have no clue as to why > not! > > fdisk -I da0 (init a real freebsd-dedicated DOS partition) > reboot (reboot just to be sure) > (BIOS does NOT crash with a real dos partition > table) > fdisk da0 (see output below) > > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 143363997 (70001 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 731/ sector 63/ head 254 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > 10:/root# > > disklabel -w -r da0s1 auto (label it) Disklabel can not label slices. For a project I had to work on receently I hacked up a slicelabel tool that used libdisk (which can handle slices) to initialize the disklabels in slices. The code for the slicelabel command is quite short: #include #include #include #include #include static void usage(void); static void label_disk(const char *name); static void usage(void) { fprintf(stderr, "Usage: slicelabel disk [disk ...]\n"); exit(1); } static void label_disk(const char *name) { struct disk *disk; if ((disk = Open_Disk(name)) == NULL) fprintf(stderr, "Unable to open disk %s.\n", name); else Write_Disk(disk); } int main(int argc, char *argv[]) { int index; if (argc == 1) usage(); for(index = 1; index < argc; index++) label_disk(argv[index]); return(0); } -- 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 Oct 27 11:24:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 6F92B37B479; Fri, 27 Oct 2000 11:24:21 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RIOLw06173; Fri, 27 Oct 2000 11:24:21 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 11:24:21 -0700 (PDT) From: Matt Dillon Message-Id: <200010271824.e9RIOLw06173@earth.backplane.com> To: John Baldwin Cc: hackers@FreeBSD.org, "freebsd-stable@FreeBSD.ORG" Subject: Re: RE: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I was testing the PXE stuff and booting one of the boxes regularly. :> All of a sudden every time I reboot I get: :> :> ... :> BIOS drive A: is disk0 :> :> int=00000000 err=00000000 efl=00030246 eip=00001d29 :> eax=00000000 ebs=00000390 ecx=00000000 edx=00000000 :> esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c :> cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7 :> cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff :> ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 :> BTX halted : :Int 00 is a divide by zero fault. Note that %eax is zero. :Do you have dangerously dedicated mode on by chance? Some :SCSI BIOS's _will_ crash with this if you use dangerously :dedicated mode. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ Yup. The real question is: Ok, so if I can't use dangerously dedicated mode, then how do I create a disklabel on a normal partition? Everything I try using fdisk and disklabel fails. fdisk will create a normal freebsd-dedicated dos partition, but disklabel refuses to label it. Beyond that, our 'dangerously dedicated' disk label should at least contain reasonable values -- be correct enough to pass BIOS muster. I don't know enough about the partition format to know where the BIOS calculation is failing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 11:29:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id F297037B479; Fri, 27 Oct 2000 11:29:52 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RITGf85246; Fri, 27 Oct 2000 11:29:16 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010271824.e9RIOLw06173@earth.backplane.com> Date: Fri, 27 Oct 2000 11:30:06 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: RE: Really odd "BTX halted" problem booting FreeBSD on VALin Cc: "freebsd-stable@FreeBSD.ORG" Cc: "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Matt Dillon wrote: > The real question is: Ok, so if I can't use dangerously dedicated > mode, then how do I create a disklabel on a normal partition? Everything > I try using fdisk and disklabel fails. fdisk will create a normal > freebsd-dedicated dos partition, but disklabel refuses to label it. See my previous e-mail about my slicelabel utility^Whack. If you use sysinstall you can label the disk as well. :) > Beyond that, our 'dangerously dedicated' disk label should at least > contain reasonable values -- be correct enough to pass BIOS muster. > I don't know enough about the partition format to know where the > BIOS calculation is failing. Errr, the dangerously dedicated label can't contain reasonable values because it violates assumptions made by other pieces of the PC architecture. > -Matt -- 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 Oct 27 11:33: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 613EC37B4C5; Fri, 27 Oct 2000 11:32:54 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RIWsk06307; Fri, 27 Oct 2000 11:32:54 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 11:32:54 -0700 (PDT) From: Matt Dillon Message-Id: <200010271832.e9RIWsk06307@earth.backplane.com> To: John Baldwin Cc: hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Danny Braniss , Paul Saab Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> disklabel -w -r da0s1 auto (label it) : :Disklabel can not label slices. For a project I had to work on receently :I hacked up a slicelabel tool that used libdisk (which can handle slices) :to initialize the disklabels in slices. The code for the slicelabel :command is quite short: :.. :John Baldwin -- http://www.FreeBSD.org/~jhb/ Thanks for the program. I think, however, that the proper solution is to make disklabel work with slices. We shouldn't need three programs to label a disk... if fdisk and disklabel can't do the job then our distribution is broken. I am going to spend some time researching the problem to see if I can come up with a 'disklabel' solution for labeling slices. It would also be nice if someone could figure out why our 'dangerously dedicated' partition fails with some BIOSes ... it should be possible to fix it if someone could track down what exactly is causing the divide-by-0 ! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 12:30:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 7AC0D37B479; Fri, 27 Oct 2000 12:30:40 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RJUad07211; Fri, 27 Oct 2000 12:30:36 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 12:30:36 -0700 (PDT) From: Matt Dillon Message-Id: <200010271930.e9RJUad07211@earth.backplane.com> To: John Baldwin Cc: hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Danny Braniss , Paul Saab Subject: Proposed patch to fix disklabel for slices. (was re: BTX halted...) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is my proposal and a patch. The patch adds a new iodctl, called DIOCGDVIRGIN. This ioctl returns a 'virgin disklabel' for a disk or slice. The other part of the patch is to modify the 'disklabel' program to use the new ioctl (and to fallback to what it was doing before: DIOCGINFO if the new ioctl fails). With this patch you can now use 'fdisk -I da0' to create a real dos partition, and then use 'disklabel -w -r da0s1 auto' to label it. Without the patch it is not possible to disklabel a slice without writing a separate program to do it (as mentioned by others in this thread). I am testing it now, but I believe it to be very close to correct if not completely correct. I would appreciate comment and testing by others and some input from Jordan in regards to possibly getting it into the release. -Matt Index: sbin/disklabel/disklabel.c =================================================================== RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v retrieving revision 1.28.2.3 diff -u -r1.28.2.3 disklabel.c --- sbin/disklabel/disklabel.c 2000/07/01 06:47:46 1.28.2.3 +++ sbin/disklabel/disklabel.c 2000/10/27 19:24:00 @@ -1347,10 +1347,17 @@ warn("cannot open %s", namebuf); return (NULL); } - if (ioctl(f, DIOCGDINFO, &lab) < 0) { - warn("ioctl DIOCGDINFO"); - close(f); - return (NULL); + + /* + * Try to use the new get-virgin-label ioctl. If it fails, + * fallback to the old get-disdk-info ioctl. + */ + if (ioctl(f, DIOCGDVIRGIN, &lab) < 0) { + if (ioctl(f, DIOCGDINFO, &lab) < 0) { + warn("ioctl DIOCGDINFO"); + close(f); + return (NULL); + } } close(f); lab.d_boot0 = NULL; Index: sys/kern/kern_descrip.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_descrip.c,v retrieving revision 1.81.2.4 diff -u -r1.81.2.4 kern_descrip.c --- sys/kern/kern_descrip.c 2000/10/24 19:28:26 1.81.2.4 +++ sys/kern/kern_descrip.c 2000/10/26 04:04:25 @@ -125,6 +125,9 @@ /* * Duplicate a file descriptor to a particular value. + * + * note: keep in mind that a potential race condition exists when closing + * descriptors from a shared descriptor table (via rfork). */ #ifndef _SYS_SYSPROTO_H_ struct dup2_args { @@ -145,8 +148,9 @@ if (old >= fdp->fd_nfiles || fdp->fd_ofiles[old] == NULL || new >= p->p_rlimit[RLIMIT_NOFILE].rlim_cur || - new >= maxfilesperproc) + new >= maxfilesperproc) { return (EBADF); + } if (old == new) { p->p_retval[0] = new; return (0); @@ -157,12 +161,15 @@ if (new != i) panic("dup2: fdalloc"); } else if (fdp->fd_ofiles[new]) { + struct file *fp = fdp->fd_ofiles[new]; + if (fdp->fd_ofileflags[new] & UF_MAPPED) (void) munmapfd(p, new); /* * dup2() must succeed even if the close has an error. */ - (void) closef(fdp->fd_ofiles[new], p); + fdp->fd_ofiles[new] = NULL; + (void) closef(fp, p); } return (finishdup(fdp, (int)old, (int)new, p->p_retval)); } Index: sys/kern/subr_diskslice.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_diskslice.c,v retrieving revision 1.82 diff -u -r1.82 subr_diskslice.c --- sys/kern/subr_diskslice.c 2000/01/28 11:51:08 1.82 +++ sys/kern/subr_diskslice.c 2000/10/27 19:23:28 @@ -366,12 +366,46 @@ int slice; struct diskslice *sp; struct diskslices *ssp; + struct partition *pp; slice = dkslice(dev); ssp = *sspp; sp = &ssp->dss_slices[slice]; lp = sp->ds_label; switch (cmd) { + + case DIOCGDVIRGIN: + lp = (struct disklabel *)data; + if (ssp->dss_slices[WHOLE_DISK_SLICE].ds_label) { + *lp = *ssp->dss_slices[WHOLE_DISK_SLICE].ds_label; + } else { + bzero(lp, sizeof(struct disklabel)); + } + + lp->d_magic = DISKMAGIC; + lp->d_magic2 = DISKMAGIC; + pp = &lp->d_partitions[RAW_PART]; + pp->p_offset = 0; + pp->p_size = sp->ds_size; + + lp->d_npartitions = MAXPARTITIONS; + if (lp->d_interleave == 0) + lp->d_interleave = 1; + if (lp->d_rpm == 0) + lp->d_rpm = 3600; + if (lp->d_nsectors == 0) + lp->d_nsectors = 32; + if (lp->d_ntracks == 0) + lp->d_ntracks = 64; + + lp->d_bbsize = BBSIZE; + lp->d_sbsize = SBSIZE; + lp->d_secpercyl = lp->d_nsectors * lp->d_ntracks; + lp->d_ncylinders = sp->ds_size / lp->d_secpercyl; + lp->d_secperunit = sp->ds_size; + lp->d_checksum = 0; + lp->d_checksum = dkcksum(lp); + return (0); case DIOCGDINFO: if (lp == NULL) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13: 4:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id DC3C137B479; Fri, 27 Oct 2000 13:04:27 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 14:04:26 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma027833; Fri, 27 Oct 00 14:03:58 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA81690; Fri, 27 Oct 2000 14:03:57 -0600 (MDT) Date: Fri, 27 Oct 2000 14:20:30 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Matt Dillon Cc: hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h In-Reply-To: <200010271832.e9RIWsk06307@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So let me see if I get this -- the recommended way to install is to have fdisk slices, and inside (one of) those slices have FreeBSD lables. However, right now, other than using the program posted in this thread, getting creative with dd is the only way to set up lables like that in an automated way. The only other choice it would seem is to use sysinstall interactively? disklabel -e claims it supports 'leaving the fdisk partition alone' while labling -- would that work? This is interactive too, however. The 'fake' fdisk table that gets put on for dangerously dedicated mode (ie the one inside boot0) has a fake 25 meg partition in it. Wouldn't the problem be solved if we jut put valid info in this 'fake' partition table making this a both 'dedicated' and non-bios confusing 'normal' install at the same time? I have a bunch boxes based on the L440GX+ intel motherboard that get confused by 'dangerously dedicated' labels. If you want real fun, dd boo0 from 3.4 onto the first block of any hard disk in your system and you will be unable to boot _any_ device in your system as the bios gets a wedgie somewhere before the bootloader gets invoked. PXE or other network boot still works and from there you can 'fix' the disk, or you can just yank it from the box too. At any rate, I've found a workaround in that if I put in valid partition info into the boot0 bootblock, the wedgie problem goes away. Am I confused about something? Perhaps I'm mistaken about how things work -- if so, enlighten me, please. -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13:24:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 34C4837B479; Fri, 27 Oct 2000 13:24:18 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9RKOHL07526; Fri, 27 Oct 2000 13:24:17 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 13:24:17 -0700 (PDT) From: Matt Dillon Message-Id: <200010272024.e9RKOHL07526@earth.backplane.com> To: Fred Clift Cc: hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a bunch boxes based on the L440GX+ intel motherboard that get :confused by 'dangerously dedicated' labels. If you want real fun, dd :boo0 from 3.4 onto the first block of any hard disk in your system and :you will be unable to boot _any_ device in your system as the bios gets a :wedgie somewhere before the bootloader gets invoked. PXE or other network :boot still works and from there you can 'fix' the disk, or you can just :yank it from the box too. : :At any rate, I've found a workaround in that if I put in valid partition :info into the boot0 bootblock, the wedgie problem goes away. : :Am I confused about something? Perhaps I'm mistaken about how things work :-- if so, enlighten me, please. :-- :Fred Clift - fclift@verio.net -- Remember: If brute I think that the days of the 'dangerously dedicated partition' are numbered. It has obviously caused much more havoc then people have realized. We don't have time to fix it for the current release, but I took a good hard look at the code and as far as I can tell the only reason we *have* a dangerously dedicated partition at all is because the disklabel code is too cheap to create a real one - it is just copying the skeleton fdisk data from boot0 verbatim and leaving it. Disklabel could very easily create a real partition - in fact, I think with my proposed patch for labeling slices all it needs to do is exec 'fdisk -I disk' to do it, and then generate a virgin label for the slice. An interim solution would be to get my proposed patch (DIOCGVIRGIN and giving disklabel the ability to label a slice) in for this release, assuming it passes muster. We definitely need something for this release, or everyone running VALinux hardware is going to be real confused if they ever disklabel a disk manually. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13:25:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D5AA37B4F9; Fri, 27 Oct 2000 13:25:05 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 14:25:04 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma002775; Fri, 27 Oct 00 14:24:32 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA84224; Fri, 27 Oct 2000 14:24:31 -0600 (MDT) Date: Fri, 27 Oct 2000 14:41:06 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Matt Dillon Cc: Mike Smith , freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-Reply-To: <200010270914.e9R9E5Y03182@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you do a hexdump on boot0 and the first sector of your disk, you'll see that boot0 has been copied onto your disk, broken partition table and all. If you then run fdisk on the disk and put in the 'right' number of sectors and let it automatically recalculate everything else, you'll get a decent fdisk table back. disklabel -B, in my opinion should either A) leave the partition table alone (even though it's part of the first sector too) or B) look at the freebsd label and automagically calculate what the values should be and put them in (as does fdisk -u when you 'Supply a decimal value for "size"' and dont explicitly calculate anything else, letting it calculate it for you. > > disklabel -B da0 > disklabel -B da1 > > fdisk da0 ... > The data for partition 4 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 50000 (24 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 0; > end: cyl 1023/ sector 63/ head 255 Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13:28:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E83537B479; Fri, 27 Oct 2000 13:28:53 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 14:28:46 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma003668; Fri, 27 Oct 00 14:28:36 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA84731; Fri, 27 Oct 2000 14:28:36 -0600 (MDT) Date: Fri, 27 Oct 2000 14:45:10 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Robert Nordier Cc: Matt Dillon , Terry Lambert , "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-Reply-To: <200010271110.NAA26088@siri.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Robert Nordier wrote: > > Just doing the disklabel -w -r followed by the disklabel -B is creating > a dangerously dedicated disk, which your BIOS apparently doesn't like. > (See the first hex dump you did, where boot1 has ended up in the MBR.) > > That's why installing boot blocks is messing with the partition table, > to answer the question you asked elsewhere. > > You need to dd and fdisk before the disklabel commands, which will give > you a standard partition table (at the cost of 63 sectors of disk > space). > So why not just put a valid partition table inside the boot1 that gets put on sector zero? When boot1 gets dropped onto sector zero, it does hose the partition table, but there is no reason why a valid one couln't be put there insead of this broken one: Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Why not edit the partition table after boot1 gets installed? Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13:30:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 0FC1037B479; Fri, 27 Oct 2000 13:30:28 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 14:30:27 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma003956; Fri, 27 Oct 00 14:30:08 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA84950; Fri, 27 Oct 2000 14:30:08 -0600 (MDT) Date: Fri, 27 Oct 2000 14:46:42 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Fred Clift Cc: Matt Dillon , Mike Smith , freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Fred Clift wrote: > > If you do a hexdump on boot0 and the first sector of your disk, you'll see > that boot0 has been copied onto your disk, broken partition table and a typo/thinko -- replace boot0 here with boot1 -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 13:45: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C3D9237B479; Fri, 27 Oct 2000 13:44:55 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RKiIf90204; Fri, 27 Oct 2000 13:44:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010272024.e9RKOHL07526@earth.backplane.com> Date: Fri, 27 Oct 2000 13:45:08 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: freebsd-stable@FreeBSD.org, hackers@FreeBSD.org, Fred Clift Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Matt Dillon wrote: >:I have a bunch boxes based on the L440GX+ intel motherboard that get >:confused by 'dangerously dedicated' labels. If you want real fun, dd >:boo0 from 3.4 onto the first block of any hard disk in your system and >:you will be unable to boot _any_ device in your system as the bios gets a >:wedgie somewhere before the bootloader gets invoked. PXE or other network >:boot still works and from there you can 'fix' the disk, or you can just >:yank it from the box too. >: >:At any rate, I've found a workaround in that if I put in valid partition >:info into the boot0 bootblock, the wedgie problem goes away. >: >:Am I confused about something? Perhaps I'm mistaken about how things work >:-- if so, enlighten me, please. >:-- >:Fred Clift - fclift@verio.net -- Remember: If brute > > I think that the days of the 'dangerously dedicated partition' are > numbered. It has obviously caused much more havoc then people have > realized. We don't have time to fix it for the current release, but I > took a good hard look at the code and as far as I can tell the only > reason we *have* a dangerously dedicated partition at all is because > the disklabel code is too cheap to create a real one - it is just copying > the skeleton fdisk data from boot0 verbatim and leaving it. Disklabel > could very easily create a real partition - in fact, I think with my > proposed patch for labeling slices all it needs to do is exec > 'fdisk -I disk' to do it, and then generate a virgin label for the slice. No, unfortunately we can't quite kill dedicated mode yet. There are still potential cases where the geometry the BIOS uses and the geometry that sysinstall uses are different, resulting in sysinstall writing a MBR that the BIOS won't handle properly (it won't find boot1 on the FreeBSD slice in the right place). DD mode works around this by sticking boot1 as the second sector on the disk whose geometry can't be screwed up. If you remove DD mode then the workaround in this case is for the user to enter the BIOS setup, write down the geometry the BIOS thinks the disk has, and then use the set geometry command in sysinstall's fdisk editor to set the geometry to the one the BIOS is using so that sysinstall writes out a MBR that the BIOS can properly use. As you can see, the issues involved with PC booting are revolting at best. -- 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 Oct 27 13:54:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 05F4F37B479; Fri, 27 Oct 2000 13:54:24 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RKrpf90497; Fri, 27 Oct 2000 13:53:51 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 27 Oct 2000 13:54:41 -0700 (PDT) From: John Baldwin To: Fred Clift Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org Cc: hackers@FreeBSD.org, "freebsd-stable@FreeBSD.ORG" , Terry Lambert , Matt Dillon , Robert Nordier Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Fred Clift wrote: > On Fri, 27 Oct 2000, Robert Nordier wrote: > >> >> Just doing the disklabel -w -r followed by the disklabel -B is creating >> a dangerously dedicated disk, which your BIOS apparently doesn't like. >> (See the first hex dump you did, where boot1 has ended up in the MBR.) >> >> That's why installing boot blocks is messing with the partition table, >> to answer the question you asked elsewhere. >> >> You need to dd and fdisk before the disklabel commands, which will give >> you a standard partition table (at the cost of 63 sectors of disk >> space). >> > > > So why not just put a valid partition table inside the boot1 that gets put > on sector zero? When boot1 gets dropped onto sector zero, it does hose > the partition table, but there is no reason why a valid one couln't be put > there insead of this broken one: Well, for one thing, 99% of the PC architecture assumes that the first track is reserved for the MBR so to speak, so putting boot1 in the MBR is already bogus. The reason it is bogus is to work around disk geometry pain as I mentioned in my previous e-mail to Matt. The only thing you can change is the size of the last slice, but my guess is that that won't fix the problem that the SCSI BIOS's have, but that instead the hack that we use boot1 as an MBR for (having the slice start at 0/0/1) is what is causing the BIOS to choke. -- 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 Oct 27 14:12:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from siri.nordier.com (c2-dbn-94.dial-up.net [196.34.155.222]) by hub.freebsd.org (Postfix) with ESMTP id 607C637B479; Fri, 27 Oct 2000 14:12:23 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id XAA32064; Fri, 27 Oct 2000 23:11:26 +0200 (SAST) From: Robert Nordier Message-Id: <200010272111.XAA32064@siri.nordier.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux To: fclift@verio.net (Fred Clift) Date: Fri, 27 Oct 2000 23:11:26 +0200 (SAST) Cc: dillon@earth.backplane.com (Matt Dillon), tlambert@primenet.com (Terry Lambert), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG In-Reply-To: from "Fred Clift" at Oct 27, 2000 02:45:10 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fred Clift wrote: > On Fri, 27 Oct 2000, Robert Nordier wrote: > > > > > Just doing the disklabel -w -r followed by the disklabel -B is creating > > a dangerously dedicated disk, which your BIOS apparently doesn't like. > > (See the first hex dump you did, where boot1 has ended up in the MBR.) > > > > That's why installing boot blocks is messing with the partition table, > > to answer the question you asked elsewhere. > > > > You need to dd and fdisk before the disklabel commands, which will give > > you a standard partition table (at the cost of 63 sectors of disk > > space). > > > So why not just put a valid partition table inside the boot1 that gets put > on sector zero? When boot1 gets dropped onto sector zero, it does hose > the partition table, but there is no reason why a valid one couln't be put > there insead of this broken one: There seems to be a lot of muddy thinking going around, so let's go over some basics: o Dangerously dedicated mode was created so that boot1 could sit on sector zero, as it does on non-PC implementations of UNIX. (It also saved space, since PC partitions are usually head- aligned and up to 62 sectors could be wasted, though that's hardly an issue now.) o A dangerously dedicated disk can _never_ be a valid PC partition. By even a loose definition, a PC partition always _excludes_ the MBR. By definition, a dangerously dedicated disk explicitly _includes_ the MBR sector. o Given that a dangerously dedicated disk is an invalid PC partition and can't be otherwise, the PC partition table entry is invalid and can't be otherwise. It is therefore better to "limit the damage" and always use the same invalid entry 0x80, 0x00, 0x01, 0x00 0xa5, 0xff, 0xff, 0xff 0x00, 0x00, 0x00, 0x00 0x50, 0xc3, 0x00, 0x00 rather than change it to better fit the disk. > > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 50000 (24 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 0; > end: cyl 1023/ sector 63/ head 255 > > Why not edit the partition table after boot1 gets installed? Because you can never make it valid. By keeping it the same set of illegal values, at least the system can recognise it. A final point: o Don't use dangerously dedicated mode. -- Robert Nordier rnordier@nordier.com rnordier@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 Oct 27 14:27:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 0A6FC37B479; Fri, 27 Oct 2000 14:27:40 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 15:27:39 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma017396; Fri, 27 Oct 00 15:27:26 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id PAA90936; Fri, 27 Oct 2000 15:27:26 -0600 (MDT) Date: Fri, 27 Oct 2000 15:44:01 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Robert Nordier Cc: Fred Clift , Matt Dillon , Terry Lambert , "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux In-Reply-To: <200010272111.XAA32064@siri.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Why not edit the partition table after boot1 gets installed? > > Because you can never make it valid. By keeping it the same set of > illegal values, at least the system can recognise it. What do you mean it can't be made valid? fdisk -u and a few keystrokes later and I have a valid partition table... Whats wrong with it? Really, if I'm being dense, sorry -- perhaps I just dont under stand yet -- please be patient with me :) > > A final point: > > o Don't use dangerously dedicated mode. I'd love to but the tools for automated installs in non-dedicated mode dont really exist in a supported way. One of the things that was pointed out in the thread is that disklabel doesn't work inside an fdisk slice. I could use expect to manipulate sysinstall? So, for now, I use dangerously dedicated installs with a hacked fake partition table to work around the broken bioses I use. I just might start using program posted in this thread that lets you do labels right in lieu of anything else, or perhaps I'll fix disklabel to work right as was suggeseted elsewhere. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 14:40:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from siri.nordier.com (c3-dbn-77.dial-up.net [196.33.200.77]) by hub.freebsd.org (Postfix) with ESMTP id 736EE37B479; Fri, 27 Oct 2000 14:40:10 -0700 (PDT) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id XAA32861; Fri, 27 Oct 2000 23:39:55 +0200 (SAST) From: Robert Nordier Message-Id: <200010272139.XAA32861@siri.nordier.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux To: fclift@verio.net (Fred Clift) Date: Fri, 27 Oct 2000 23:39:54 +0200 (SAST) Cc: fclift@verio.net (Fred Clift), dillon@earth.backplane.com (Matt Dillon), tlambert@primenet.com (Terry Lambert), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG In-Reply-To: from "Fred Clift" at Oct 27, 2000 03:44:01 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fred Clift wrote: > > > > > > Why not edit the partition table after boot1 gets installed? > > > > Because you can never make it valid. By keeping it the same set of > > illegal values, at least the system can recognise it. > > > What do you mean it can't be made valid? fdisk -u and a few keystrokes > later and I have a valid partition table... Whats wrong with it? Really, > if I'm being dense, sorry -- perhaps I just dont under stand yet -- please > be patient with me :) If the PC partition (slice) includes boot1, it is invalid. A slice should can't include its own MBR. If the BSD partition excludes boot1, it is invalid. A partition can't exclude its own boot blocks. Just because fdisk is happy, doesn't mean it's valid. Just because it works (for you), doesn't mean it's valid, either. :) > > > > A final point: > > > > o Don't use dangerously dedicated mode. > > I'd love to but the tools for automated installs in non-dedicated mode > dont really exist in a supported way. One of the things that was pointed > out in the thread is that disklabel doesn't work inside an fdisk slice. Disklabel really needs to be rewritten. > I could use expect to manipulate sysinstall? So, for now, I use > dangerously dedicated installs with a hacked fake partition table to work > around the broken bioses I use. I just might start using program posted > in this thread that lets you do labels right in lieu of anything else, or > perhaps I'll fix disklabel to work right as was suggeseted elsewhere. Don't sysinstall work in a script mode? I've never used it, but I thought it did. -- Robert Nordier rnordier@nordier.com rnordier@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 Oct 27 14:52: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (Postfix) with ESMTP id 3B5C937B4C5 for ; Fri, 27 Oct 2000 14:52:01 -0700 (PDT) Received: from localhost (ccsanady@localhost) by isua3.iastate.edu (8.8.8/8.8.5) with SMTP id QAA14985 for ; Fri, 27 Oct 2000 16:51:55 -0500 (CDT) Message-Id: <200010272151.QAA14985@isua3.iastate.edu> To: freebsd-hackers@freebsd.org Subject: IDE Questions Date: Fri, 27 Oct 2000 16:51:55 CDT From: Chris Csanady Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anyone successfully using an IBM 75GXP with an Abit KT7-Raid motherboard? I am using stable from a couple days ago, and am having some problems getting it to work. If the disk is attached to the onboard IDE, the kernel spews a bunch of these ad2: UDMA ICRC WRITE ERROR blk# 1457759 retrying and then falls back to PIO mode, which is unacceptable. (ie. it transforms my Athlon 900 into a turd. For any moderate amount of disk activity, I get 100% CPU utilization, and it is very much non-interactive.) I have the proper cables, and have observed this on two seperate KT7 motherboards. Is the KT7 onboard IDE just busted? (I wouldn't be at all surprised, considering how horribly broken the BIOS boot ordering is, not to mention the soft power issues, etc. For a board that comes so highly recommended, I'm not terribly impressed.) When I attach the disk to the Highpoint 370 controller, the machine wedges after a short while. Is the support for this chipset in stable up to date? Also, are there any plans to merge the support for tagged queueing? Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 15:19:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pegasus.kazrak.com (adsl-209-233-16-235.dsl.snfc21.pacbell.net [209.233.16.235]) by hub.freebsd.org (Postfix) with ESMTP id 07B0B37B479 for ; Fri, 27 Oct 2000 15:19:21 -0700 (PDT) Received: by pegasus.kazrak.com (Postfix, from userid 1001) id 9B3913181; Fri, 27 Oct 2000 15:19:20 -0700 (PDT) Date: Fri, 27 Oct 2000 15:19:20 -0700 From: Brad Jones To: Chris Csanady Cc: freebsd-hackers@freebsd.org Subject: Re: IDE Questions Message-ID: <20001027151920.A85611@pegasus.kazrak.com> References: <200010272151.QAA14985@isua3.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010272151.QAA14985@isua3.iastate.edu>; from ccsanady@iastate.edu on Fri, Oct 27, 2000 at 04:51:55PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 27, 2000 at 04:51:55PM -0500, Chris Csanady wrote: > Is there anyone successfully using an IBM 75GXP with an Abit KT7-Raid > motherboard? I am using stable from a couple days ago, and am having > some problems getting it to work. > > [snip] > > When I attach the disk to the Highpoint 370 controller, the > machine wedges after a short while. Is the support for this > chipset in stable up to date? Also, are there any plans to > merge the support for tagged queueing? There appear to be some problems with the IBM disks and some drive controllers. (The HPT366 is one, so I wouldn't be surprised if the 370 has problems as well.) The latest BIOS for the 366 is supposed to fix this problem, but it only partially fixed it for me. (The BIOS detects the disk properly, but any attempt to access causes the machine to hang.) My workaround for my BP6 motherboard was to connect it to one of the standard BX IDE controllers, but this is less than ideal. In short, this is much less likely to be FreeBSD's problem than Highpoint's, IMO. BJ -- Brad Jones -- brad@kazrak.com "Until you can face up to reality, I'm not sure you can be my imaginary friend anymore." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 15:46:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 02DCD37B479; Fri, 27 Oct 2000 15:46:19 -0700 (PDT) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id VT2X0H2L; Fri, 27 Oct 2000 18:46:23 -0400 Reply-To: Randell Jesup To: Robert Nordier Cc: dillon@earth.backplane.com (Matt Dillon), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG), hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux References: <200010272139.XAA32861@siri.nordier.com> From: Randell Jesup Date: 27 Oct 2000 18:49:37 -0400 In-Reply-To: Robert Nordier's message of "Fri, 27 Oct 2000 23:39:54 +0200 (SAST)" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier writes: >> > o Don't use dangerously dedicated mode. >> >> I'd love to but the tools for automated installs in non-dedicated mode >> dont really exist in a supported way. One of the things that was pointed >> out in the thread is that disklabel doesn't work inside an fdisk slice. > >Disklabel really needs to be rewritten. Few truer statements have ever been made... >> I could use expect to manipulate sysinstall? So, for now, I use >> dangerously dedicated installs with a hacked fake partition table to work >> around the broken bioses I use. I just might start using program posted >> in this thread that lets you do labels right in lieu of anything else, or >> perhaps I'll fix disklabel to work right as was suggeseted elsewhere. > >Don't sysinstall work in a script mode? I've never used it, but I >thought it did. It does work in a scripted mode, however the documentation on it is close to non-existant; arguments are case-sensitive, etc. I was working to migrate data to disks/partitions of different sizes, and had to read lots of the sysinstall/disklabel source, and on top of that had to hack sysinstall in order to get it to work at all for my purpose. Ugh. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 16:34:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 99D4037B479 for ; Fri, 27 Oct 2000 16:34:45 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id QAA26751; Fri, 27 Oct 2000 16:31:04 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpdAAAYGayk0; Fri Oct 27 16:30:55 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA01336; Fri, 27 Oct 2000 16:34:22 -0700 (MST) From: Terry Lambert Message-Id: <200010272334.QAA01336@usr01.primenet.com> Subject: Re: Accessing the tty structure of an opened device To: maret@atrada.net (Alexander Maret) Date: Fri, 27 Oct 2000 23:34:21 +0000 (GMT) Cc: phk@critter.freebsd.dk ('Poul-Henning Kamp'), msmith@mass.osd.bsdi.com ('msmith@mass.osd.bsdi.com'), freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org') In-Reply-To: <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de> from "Alexander Maret" at Oct 27, 2000 03:29:50 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You will need to do this in a device driver, there is no way you > > can reliably measure that from userland. > > > > Trust me on this: I've tried. > > That's what I wanted to do. I wanted to write a character device > which on read() passes the last IR-code. > > Well as Mike Smith told me: "you cannot poll the serial line at > anything like a useful speed to perform IR decoding" my hopes are > all gone to get a simple solution. > > Do I have to write my own serial driver to get what I want or > is it possible to use functions of the "build in" serial > device driver? You will have to modify the serial driver somewhat to be able to externalize the interruptable events. Some of these events are handled internally. My personaly suggestion, since you created this dongle on your own, would be to drop uses of DCD, and use CTS/RTS as the signalling method instead. To do this right, you will need to set your FIFO depth on the UART to nothing, so it doesn't delay delivery of interrupts (some FIFO implementations delay signalling of events intentionally to reduce processing overhead, and only deliver when they would deliver data). You will also effectively be using every character as a wakeup character, to avoid queueuing at the tty pseudo device boundary (or would, last time I looked). I would specifically suggest you implement this as a line discipline, since most of what you would need to do is there. If you are not adamant about clock speed on input, this should work in a non-noisy environment. For a noisy environment, you will want to poke the UART at some multiple of your expected frequency to get it to reinterrupt, and then debounce it in software, based on your expected event boundary crossing frequency vs. the (higher) poking frequency. If you plan to implement this as a line discipline, you should look at the SLIP, PPP, and mouse line disciplines; the first two will tell you about the wakeup code, and the second will tell you about FIFO depth. Looking back over all this, it would be useful to have the ability to generalize all serial port data using a line discipline and externalization of all possible interrupt signals... BUT... it would probably be easier for you, in the short run, to just take the serial and IR driver code, and write a custom driver that takes over the serial port, and disable the standard serial driver from grabbing it using kernel configuration options. If I were doing it, I'd probably want to open up the ports for people to hack on every possible little thing they could hack on, but then I don't have a deadline, and I wouldn't really care how much work it would take, and I don't have a specific hack in mind, like you do. Sort of the current parallel port code, applied to serial ports... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 16:57:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 77F3B37B479; Fri, 27 Oct 2000 16:57:29 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id QAA07200; Fri, 27 Oct 2000 16:55:41 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpdAAA2CayNl; Fri Oct 27 16:53:22 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA02252; Fri, 27 Oct 2000 16:55:01 -0700 (MST) From: Terry Lambert Message-Id: <200010272355.QAA02252@usr01.primenet.com> Subject: Re: smbfs-1.3.0 released To: cdillon@wolves.k12.mo.us (Chris Dillon) Date: Fri, 27 Oct 2000 23:55:01 +0000 (GMT) Cc: malachai@iname.com (Shawn Halpenny), bp@butya.kz (Boris Popov), freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Chris Dillon" at Oct 27, 2000 12:01:48 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh yeah, I've noticed one more thing. When you're at the root of a > mount, you can cd into a directory using any case, but if you get the > case wrong, you don't get a listing. Here's an example: [ ... ] > So... the case-insensitivity only happens at the root of the mount. > Should it happen everywhere? It'd be nice if it did. :-) Ha! The full path is sent over the wire. The attempt to be "case sensitive on storage, case insensitive on lookup" is inhernetly flawed. The way this works on OSs which support it is that the globbing occurs in the kernel. This lets the case folding occur before the data is returned. The difference is that if you are iterating and comparing in user space, you will get a failure, but if you are doing an explicit VOP_LOOKUP in kernel space, the case folding will work. The problem is that you don't really get a directory handle object, like you get an inode in NFS, since in a DOS FS, and thus in the wire externalization of a DOS FS, which is what SMB gives you, the directory entry itself _is_ the inode, not a pointer to an independent object which dereferences to the inode. I suspect that this is at the heart of your lookup problems, given the way that UNIX programs tend to put in what they were given out. I think that if you disable the attempted case folding in the SMBFS VOP_LOOKUP code, your problem will go away. Note: things which reference explicit names use VOP_LOOKUP, while things which iterate directories use VOP_READDIR. I suspect that you will see similar problems on attempts to rename things, because of this. NB: Another approach would be to fold everything to lower case in both VOP_LOOKUP and VOP_READDIR; this could be accomplished using a mount option. If you wanted to be more Windows-like, you could make the first letter upper case, and subsequent letters lower case. NNB: The behaviour will also depend on the server you are using; some servers can return both the short (8.3) and long names over SMB, and others can only return the short names. NNNB: If you are using a Samba server as the server, and short names, you are probably screwed, since short names on a Samba server are synthetic, and indeterminately so. On a Windows box, if I rename (short:long) "PROGRA~1":"Program Files" to "PROGRA~7", I get "PROGRA~7":"PROGRA~7"; if I then rename "PROGRA~7" to "Program Files", I get "PROGRA~7":"Program Files". Since the Samba short namespace is synthetic even if the UNIX FS underneath supports both name spaces (since the UNIX name API is handicapped, compared to the Macintosh or Windows API), you will get a short name based on the inode number. --- As to the df/du problem, I'd suggest hacking VFS_STAT to return fake data, and then figure out why it's failing so catastrophically, since the problem is there. I suspect the problem is that it is an old VFS_STAT call that is being called, and that a new VFS_STAT struct is being copied out in all cases, instead of making sure it is old vs. new, and doing the right thing, and the resulting buffer overrun stomps on something important. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 16:58:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id BA05B37B479; Fri, 27 Oct 2000 16:58:37 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id QAA00894; Fri, 27 Oct 2000 16:58:58 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAAGxa4Kb; Fri Oct 27 16:58:49 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA02448; Fri, 27 Oct 2000 16:58:13 -0700 (MST) From: Terry Lambert Message-Id: <200010272358.QAA02448@usr01.primenet.com> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h To: dillon@earth.backplane.com (Matt Dillon) Date: Fri, 27 Oct 2000 23:58:13 +0000 (GMT) Cc: jhb@FreeBSD.ORG (John Baldwin), hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, danny@cs.huji.ac.il (Danny Braniss), paul@mu.org (Paul Saab) In-Reply-To: <200010271832.e9RIWsk06307@earth.backplane.com> from "Matt Dillon" at Oct 27, 2000 11:32:54 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the program. > > I think, however, that the proper solution is to make disklabel work > with slices. We shouldn't need three programs to label a disk... > if fdisk and disklabel can't do the job then our distribution is broken. > > I am going to spend some time researching the problem to see if I can > come up with a 'disklabel' solution for labeling slices. It would > also be nice if someone could figure out why our 'dangerously dedicated' > partition fails with some BIOSes ... it should be possible to fix it if > someone could track down what exactly is causing the divide-by-0 ! I think you are specifying the wrong arguments to disklabel; I seem to rememebr a -w/-W distinction... In any case, I'm running with a disklabel inside a DOS partition on all but one box of mine, and always have been. I installed 4.1 on my laptop that way. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 17:12:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D3DB037B479; Fri, 27 Oct 2000 17:12:37 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9S0BPf97048; Fri, 27 Oct 2000 17:11:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010272358.QAA02448@usr01.primenet.com> Date: Fri, 27 Oct 2000 17:12:14 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: (Paul Saab) , (Danny Braniss) , freebsd-stable@FreeBSD.org, hackers@FreeBSD.org, (Matt Dillon) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Terry Lambert wrote: >> Thanks for the program. >> >> I think, however, that the proper solution is to make disklabel work >> with slices. We shouldn't need three programs to label a disk... >> if fdisk and disklabel can't do the job then our distribution is broken. >> >> I am going to spend some time researching the problem to see if I can >> come up with a 'disklabel' solution for labeling slices. It would >> also be nice if someone could figure out why our 'dangerously dedicated' >> partition fails with some BIOSes ... it should be possible to fix it if >> someone could track down what exactly is causing the divide-by-0 ! > > I think you are specifying the wrong arguments to disklabel; I > seem to rememebr a -w/-W distinction... Nope. > In any case, I'm running with a disklabel inside a DOS partition > on all but one box of mine, and always have been. I installed > 4.1 on my laptop that way. Sysinstall can create a disklabel inside of a MBR slice fine. The problem is that the disklabel(8) _program_ itself doesn't know how to create a virgin disklabel for a MBR slice. -- 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 Oct 27 17:31:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E0DC837B479; Fri, 27 Oct 2000 17:31:13 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9S0VCl55795; Fri, 27 Oct 2000 17:31:12 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 17:31:12 -0700 (PDT) From: Matt Dillon Message-Id: <200010280031.e9S0VCl55795@earth.backplane.com> To: John Baldwin Cc: Terry Lambert , (Paul Saab) , (Danny Braniss) , freebsd-stable@FreeBSD.org, hackers@FreeBSD.org, (Matt Dillon) Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I think you are specifying the wrong arguments to disklabel; I :> seem to rememebr a -w/-W distinction... : :Nope. : :> In any case, I'm running with a disklabel inside a DOS partition :> on all but one box of mine, and always have been. I installed :> 4.1 on my laptop that way. : :Sysinstall can create a disklabel inside of a MBR slice fine. The :problem is that the disklabel(8) _program_ itself doesn't know how :to create a virgin disklabel for a MBR slice. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ The patchset I put on the lists earlier today will allow disklabel to install a virgin label on a slice. Did it not get out? As matters currently stand, disklabel can only edit a preexisting label on a slice. I'll post it again... included below (this time without the file descriptor cruft that snuck into my previous posting of the patch). With the patch you can do this: # optional dd if you are paranoid # dd if=/dev/zero of=/dev/da0 bs=32k count=4 fdisk -I da0 disklabel -w -r da0s1 auto That's much preferable to having to use sysinstall if all you want to do is initialize a label on a slice. -Matt Index: sbin/disklabel/disklabel.c =================================================================== RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v retrieving revision 1.28.2.3 diff -u -r1.28.2.3 disklabel.c --- sbin/disklabel/disklabel.c 2000/07/01 06:47:46 1.28.2.3 +++ sbin/disklabel/disklabel.c 2000/10/27 19:24:00 @@ -1347,10 +1347,17 @@ warn("cannot open %s", namebuf); return (NULL); } - if (ioctl(f, DIOCGDINFO, &lab) < 0) { - warn("ioctl DIOCGDINFO"); - close(f); - return (NULL); + + /* + * Try to use the new get-virgin-label ioctl. If it fails, + * fallback to the old get-disdk-info ioctl. + */ + if (ioctl(f, DIOCGDVIRGIN, &lab) < 0) { + if (ioctl(f, DIOCGDINFO, &lab) < 0) { + warn("ioctl DIOCGDINFO"); + close(f); + return (NULL); + } } close(f); lab.d_boot0 = NULL; Index: sys/kern/subr_diskslice.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_diskslice.c,v retrieving revision 1.82 diff -u -r1.82 subr_diskslice.c --- sys/kern/subr_diskslice.c 2000/01/28 11:51:08 1.82 +++ sys/kern/subr_diskslice.c 2000/10/27 19:23:28 @@ -366,12 +366,46 @@ int slice; struct diskslice *sp; struct diskslices *ssp; + struct partition *pp; slice = dkslice(dev); ssp = *sspp; sp = &ssp->dss_slices[slice]; lp = sp->ds_label; switch (cmd) { + + case DIOCGDVIRGIN: + lp = (struct disklabel *)data; + if (ssp->dss_slices[WHOLE_DISK_SLICE].ds_label) { + *lp = *ssp->dss_slices[WHOLE_DISK_SLICE].ds_label; + } else { + bzero(lp, sizeof(struct disklabel)); + } + + lp->d_magic = DISKMAGIC; + lp->d_magic2 = DISKMAGIC; + pp = &lp->d_partitions[RAW_PART]; + pp->p_offset = 0; + pp->p_size = sp->ds_size; + + lp->d_npartitions = MAXPARTITIONS; + if (lp->d_interleave == 0) + lp->d_interleave = 1; + if (lp->d_rpm == 0) + lp->d_rpm = 3600; + if (lp->d_nsectors == 0) + lp->d_nsectors = 32; + if (lp->d_ntracks == 0) + lp->d_ntracks = 64; + + lp->d_bbsize = BBSIZE; + lp->d_sbsize = SBSIZE; + lp->d_secpercyl = lp->d_nsectors * lp->d_ntracks; + lp->d_ncylinders = sp->ds_size / lp->d_secpercyl; + lp->d_secperunit = sp->ds_size; + lp->d_checksum = 0; + lp->d_checksum = dkcksum(lp); + return (0); case DIOCGDINFO: if (lp == NULL) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 18: 8:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B9FB437B479; Fri, 27 Oct 2000 18:08:50 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9S18Cf98419; Fri, 27 Oct 2000 18:08:12 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010280031.e9S0VCl55795@earth.backplane.com> Date: Fri, 27 Oct 2000 18:09:01 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, (Danny Braniss) , (Paul Saab) , Terry Lambert Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-00 Matt Dillon wrote: >:> I think you are specifying the wrong arguments to disklabel; I >:> seem to rememebr a -w/-W distinction... >: >:Nope. >: >:> In any case, I'm running with a disklabel inside a DOS partition >:> on all but one box of mine, and always have been. I installed >:> 4.1 on my laptop that way. >: >:Sysinstall can create a disklabel inside of a MBR slice fine. The >:problem is that the disklabel(8) _program_ itself doesn't know how >:to create a virgin disklabel for a MBR slice. >: >:-- >: >:John Baldwin -- http://www.FreeBSD.org/~jhb/ > > The patchset I put on the lists earlier today will allow disklabel > to install a virgin label on a slice. Did it not get out? As matters > currently stand, disklabel can only edit a preexisting label on a slice. If your patch works it looks great to me. I was just referring to our currently checked in code in disklabel(8). :) > I'll post it again... included below (this time without the file > descriptor cruft that snuck into my previous posting of the patch). With > the patch you can do this: I did wonder about the file descriptor patch the first go-round... :) > # optional dd if you are paranoid > # dd if=/dev/zero of=/dev/da0 bs=32k count=4 > fdisk -I da0 > disklabel -w -r da0s1 auto > > That's much preferable to having to use sysinstall if all you want to > do is initialize a label on a slice. Yes, this is definitely the desired behavior. -- 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 Oct 27 18:36:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E56FB37B479; Fri, 27 Oct 2000 18:36:07 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9S1a7H56416; Fri, 27 Oct 2000 18:36:07 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Oct 2000 18:36:07 -0700 (PDT) From: Matt Dillon Message-Id: <200010280136.e9S1a7H56416@earth.backplane.com> To: John Baldwin Cc: hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, (Danny Braniss) , (Paul Saab) , Terry Lambert Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> # optional dd if you are paranoid :> # dd if=/dev/zero of=/dev/da0 bs=32k count=4 :> fdisk -I da0 :> disklabel -w -r da0s1 auto :> :> That's much preferable to having to use sysinstall if all you want to :> do is initialize a label on a slice. : :Yes, this is definitely the desired behavior. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ John, can you explain how the MBR bootstraps a slice? Should I make disklabel zero-out the fdisk partition table area in the slice rather then installing the dummy fdisk partition table? That is, for the case where -B is used on a slice (da0s1) verses on the whole-disk (da0)? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 18:55:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id ED0ED37B479; Fri, 27 Oct 2000 18:55:36 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 27A0628DA0; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 175EE28D7E; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Date: Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) From: Boris Popov To: Shawn Halpenny Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <20001027111539.A391@nightrain.xelus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Shawn Halpenny wrote: > Speaking of smbfs, has anyone else run into an odd bug using it in > 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the > directories (e.g. using 'ls') for an smbfs mount after a period of > time during which there were no accesses across that mount point (e.g. > mount, don't touch it for an hour, then try 'df'), my machine will > reboot after a few seconds. No panic message or anything--it's just > like I pressed the reset button. I think that I've found possible cause of this problem and 1.3.1 will be released at this weekend. > Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' > to display 'broken pipe' and I could remount that share and things Yes, 'broken pipe' was a bug and now it should work properly. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 19: 2:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 608B537B479; Fri, 27 Oct 2000 19:02:26 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9S21Df00681; Fri, 27 Oct 2000 19:01:13 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010280136.e9S1a7H56416@earth.backplane.com> Date: Fri, 27 Oct 2000 19:02:03 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: Terry Lambert , (Paul Saab) , (Danny Braniss) , freebsd-stable@FreeBSD.org, hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-00 Matt Dillon wrote: >:> # optional dd if you are paranoid >:> # dd if=/dev/zero of=/dev/da0 bs=32k count=4 >:> fdisk -I da0 >:> disklabel -w -r da0s1 auto >:> >:> That's much preferable to having to use sysinstall if all you want to >:> do is initialize a label on a slice. >: >:Yes, this is definitely the desired behavior. >: >:-- >: >:John Baldwin -- http://www.FreeBSD.org/~jhb/ > > John, can you explain how the MBR bootstraps a slice? Should I make > disklabel zero-out the fdisk partition table area in the slice rather > then installing the dummy fdisk partition table? That is, for the > case where -B is used on a slice (da0s1) verses on the whole-disk (da0)? Just ignore the slice table within a slice. It is only used when boot1 is splatted over top of the MBR for the dangerously dedicated mode. It is unused and ignored otherwise. > -Matt -- 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 Oct 27 19:14:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 2356137B479; Fri, 27 Oct 2000 19:14:13 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id AFE3628DA0; Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id A41D228D7E; Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) Date: Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) From: Boris Popov To: Terry Lambert Cc: Chris Dillon , Shawn Halpenny , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <200010272355.QAA02252@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Terry Lambert wrote: > > So... the case-insensitivity only happens at the root of the mount. > > Should it happen everywhere? It'd be nice if it did. :-) > > Ha! > > The full path is sent over the wire. > > The attempt to be "case sensitive on storage, case insensitive on > lookup" is inhernetly flawed. Actually, smbfs doesn't try to be case insensitive. At this moment it merely passes file names with possible charset translation. If long names is not used (WfWg for example), then file names converted to upper case. nwfs have more complex case management features (see mount_nwfs(4) for '-c' option). > The difference is that if you are iterating and comparing in > user space, you will get a failure, but if you are doing an > explicit VOP_LOOKUP in kernel space, the case folding will work. Hmm, why ? > The problem is that you don't really get a directory handle > object, like you get an inode in NFS, since in a DOS FS, and > thus in the wire externalization of a DOS FS, which is what SMB > gives you, the directory entry itself _is_ the inode, not a > pointer to an independent object which dereferences to the inode. > I think that if you disable the attempted case folding in the > SMBFS VOP_LOOKUP code, your problem will go away. Not exactly so - case sensitivity depends on server, for most servers ls /A and ls /a are the same, but NT have strange behavior for root directory and not all directories are case insensitive. > NB: Another approach would be to fold everything to lower case > in both VOP_LOOKUP and VOP_READDIR; this could be accomplished > using a mount option. If you wanted to be more Windows-like, > you could make the first letter upper case, and subsequent > letters lower case. I'm unsure if this correct, because long file names used on windows platform may have more than one upper case letter (Program Files for example). > NNNB: If you are using a Samba server as the server, and short > names, you are probably screwed, since short names on a Samba > server are synthetic, and indeterminately so. On a Windows > box, if I rename (short:long) "PROGRA~1":"Program Files" to > "PROGRA~7", I get "PROGRA~7":"PROGRA~7"; if I then rename > "PROGRA~7" to "Program Files", I get "PROGRA~7":"Program Files". > Since the Samba short namespace is synthetic even if the UNIX > FS underneath supports both name spaces (since the UNIX name > API is handicapped, compared to the Macintosh or Windows API), > you will get a short name based on the inode number. Correct and it is not recommended to use 8.3 name space with Samba. > As to the df/du problem, I'd suggest hacking VFS_STAT to return > fake data, and then figure out why it's failing so catastrophically, > since the problem is there. I suspect the problem is that it is > an old VFS_STAT call that is being called, and that a new VFS_STAT > struct is being copied out in all cases, instead of making sure it > is old vs. new, and doing the right thing, and the resulting > buffer overrun stomps on something important. No, this is not related. The same things will happen on all SMB requests if server dropped the connection and it seems to be fixed in the upcoming smbfs-1.3.1. On a side note I'm unsure why NT server drops the connection if client doesn't send any request in XX minutes (for example Samba uses NetBIOS keepalive packets). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 19:22:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id E5D1E37B4C5 for ; Fri, 27 Oct 2000 19:22:28 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id B22DC9B25; Sat, 28 Oct 2000 03:20:33 +0100 (BST) Date: Sat, 28 Oct 2000 03:20:33 +0100 From: Josef Karthauser To: kc5vdj@prodigy.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Rijndael status in FreeBSD?? Message-ID: <20001028032033.B54956@pavilion.net> Mail-Followup-To: Josef Karthauser , kc5vdj@prodigy.net, freebsd-hackers@FreeBSD.ORG References: <200010260126.UAA94395@ppp-207-193-3-44.kscymo.swbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010260126.UAA94395@ppp-207-193-3-44.kscymo.swbell.net>; from jbryant@ppp-207-193-3-44.kscymo.swbell.net on Wed, Oct 25, 2000 at 08:24:24PM -0500 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 25, 2000 at 08:24:24PM -0500, Jim Bryant wrote: > What are the plans for incorporating Rijndael, the finalist algorithm > for the Advanced Encryption Standard, into FreeBSD? > > jim I believe that there are people working on this. Expect it in current shortly. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 27 21:24:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id E541D37B479 for ; Fri, 27 Oct 2000 21:24:09 -0700 (PDT) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13pNeu-00007z-00; Fri, 27 Oct 2000 22:31:56 -0600 Message-ID: <39FA56BC.814B1E63@softweyr.com> Date: Fri, 27 Oct 2000 22:31:56 -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: Poul-Henning Kamp Cc: Alexander Maret , "'msmith@mass.osd.bsdi.com'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Accessing the tty structure of an opened device References: <10771.972653616@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <58A002A02C5ED311812E0050044517F00D2614@erlangen01.atrada.de>, Alexa > nder Maret writes: > > >Do I have to write my own serial driver to get what I want or > >is it possible to use functions of the "build in" serial > >device driver? > > You may be able to do it as a "line discipline. I'm not quite sure > if it is possible. If not, a (hardware-) device driver is your only hope. Uh oh. Is it time for 'ttygraph'? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 1:23:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D6C8037B4C5 for ; Sat, 28 Oct 2000 01:23:16 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA69120; Sat, 28 Oct 2000 10:21:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010280821.KAA69120@freebsd.dk> Subject: Re: IDE Questions In-Reply-To: <200010272151.QAA14985@isua3.iastate.edu> from Chris Csanady at "Oct 27, 2000 04:51:55 pm" To: ccsanady@iastate.edu (Chris Csanady) Date: Sat, 28 Oct 2000 10:21:45 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Chris Csanady wrote: > Is there anyone successfully using an IBM 75GXP with an Abit KT7-Raid > motherboard? I am using stable from a couple days ago, and am having > some problems getting it to work. I use 4 on a Abit KA7-100 with RAID0 with no problems... > When I attach the disk to the Highpoint 370 controller, the > machine wedges after a short while. Is the support for this > chipset in stable up to date? Also, are there any plans to > merge the support for tagged queueing? I have just committed all -current functionality to -stable a couble of days ago... -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 Oct 28 5: 7:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from altos.rsu.ru (altos.rsu.ru [195.208.252.79]) by hub.freebsd.org (Postfix) with ESMTP id BE30537B479 for ; Sat, 28 Oct 2000 05:05:51 -0700 (PDT) Received: from localhost (os@localhost [127.0.0.1]) by altos.rsu.ru (8.11.0/8.9.3) with ESMTP id e9SC5b563100 for ; Sat, 28 Oct 2000 16:05:41 +0400 (MSD) Date: Sat, 28 Oct 2000 16:05:37 +0400 (MSD) From: Oleg Sharoiko To: freebsd-hackers@freebsd.org Subject: Problem with 2 video cards: /src/sys/pci.c code question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've just tried to install second video card into Intel L440GX+ based box running FreeBSD and this broke the system: the screen output is messed (even during device probing), some characters are not printed, scrolling doesn't work well and after some short time it dies with only 'reset' key working. I also noticed that kernel.GENERIC from 4.1-RELEASE works fine. I tried to compile different versions of kernel and found that my problem caused by the following change in src/sys/pci/pci.c (between 2000-09-02 and 2000-09-03): < * $FreeBSD: src/sys/pci/pci.c,v 1.141.2.2 2000/07/04 01:35:10 mjacob Exp $ --- > * $FreeBSD: src/sys/pci/pci.c,v 1.141.2.3 2000/09/01 23:29:34 msmith Exp $ 1082,1085c1082,1089 < if (type == SYS_RES_IOPORT && !pci_porten(cfg)) < return 1; < if (type == SYS_RES_MEMORY && !pci_memen(cfg)) < return 1; --- > if (type == SYS_RES_IOPORT && !pci_porten(cfg)) { > cfg->cmdreg |= PCIM_CMD_PORTEN; > pci_cfgwrite(cfg, PCIR_COMMAND, cfg->cmdreg, 2); > } > if (type == SYS_RES_MEMORY && !pci_memen(cfg)) { > cfg->cmdreg |= PCIM_CMD_MEMEN; > pci_cfgwrite(cfg, PCIR_COMMAND, cfg->cmdreg, 2); > } I've looked into the log and found this ---------------------------- revision 1.141.2.3 date: 2000/09/01 23:29:34; author: msmith; state: Exp; lines: +9 -5 MFC: fix up botched PCI configuration by the BIOS in the case where a resource has been allocated but its class is not marked as enabled in the command register. ---------------------------- So I'm wondering is this a bug or I should by some means disable first card. There're no any jumpers or bios options to disable video card. I suppose that kernel turns on the built-in video adapter and it conflicts with the one I've plugged in. I don't have strong skills in PCI programming so I'm asking for your help. Please CC: replies to my e-mail. I would greatly appreciate that and I hope to here your replies soon. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 5:20:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-14.dsl.snfc21.pacbell.net [63.202.178.14]) by hub.freebsd.org (Postfix) with ESMTP id 4309737B479 for ; Sat, 28 Oct 2000 05:20:51 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id e9SCLLF07465; Sat, 28 Oct 2000 05:21:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010281221.e9SCLLF07465@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Oleg Sharoiko Cc: freebsd-hackers@freebsd.org Subject: Re: Problem with 2 video cards: /src/sys/pci.c code question In-reply-to: Your message of "Sat, 28 Oct 2000 16:05:37 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Oct 2000 05:21:21 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just tried to install second video card into Intel L440GX+ based box > running FreeBSD and this broke the system: the screen output is messed (even > during device probing), some characters are not printed, scrolling doesn't > work well and after some short time it dies with only 'reset' key working. Grr. The BIOS shouldn't turn these resources on. However, why are you trying to put a second video card into the system? > I've looked into the log and found this > ---------------------------- > revision 1.141.2.3 > date: 2000/09/01 23:29:34; author: msmith; state: Exp; lines: +9 -5 > MFC: fix up botched PCI configuration by the BIOS in the case where a > resource has been allocated but its class is not marked as enabled > in the command register. > ---------------------------- > > So I'm wondering is this a bug or I should by some means disable first > card. There're no any jumpers or bios options to disable video card. I suppose > that kernel turns on the built-in video adapter and it conflicts with the one > I've plugged in. I don't have strong skills in PCI programming so I'm asking > for your help. We don't (properly) support multiple video adapters at this time. If you're trying to override the onboard video adapter, I do believe that the Intel L440GX+ does provide a jumper on the board to disable the builtin video. The problem here is somewhat complex; in reality we shouldn't care whether the resource kind is actually enabled in the PCI command register, and devices that do care should have it fixed up in the driver or when the resource is allocated. There are a number of other fixes that need to be made to the PCI resource allocation code, and I supposed I (or whoever else makes them) will try to fix all this at the same time. Sorry. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 7:19:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 46DD337B479; Sat, 28 Oct 2000 07:19:16 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA16048; Sat, 28 Oct 2000 07:18:59 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda16046; Sat Oct 28 07:18:58 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.0/8.9.1) id e9SEIw616118; Sat, 28 Oct 2000 07:18:58 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdT16116; Sat Oct 28 07:18:48 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.1/8.9.1) id e9SEImB08772; Sat, 28 Oct 2000 07:18:48 -0700 (PDT) Message-Id: <200010281418.e9SEImB08772@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdoX8762; Sat Oct 28 07:18:20 2000 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.1.1-RELEASE X-Sender: cy To: Matt Dillon Cc: John Baldwin , hackers@FreeBSD.ORG, "freebsd-stable@FreeBSD.ORG" Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h In-reply-to: Your message of "Fri, 27 Oct 2000 11:24:21 PDT." <200010271824.e9RIOLw06173@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Oct 2000 07:18:20 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010271824.e9RIOLw06173@earth.backplane.com>, Matt Dillon writes: > :Do you have dangerously dedicated mode on by chance? Some > :SCSI BIOS's _will_ crash with this if you use dangerously > :dedicated mode. > > Yup. > > The real question is: Ok, so if I can't use dangerously dedicated > mode, then how do I create a disklabel on a normal partition? Everything > I try using fdisk and disklabel fails. fdisk will create a normal > freebsd-dedicated dos partition, but disklabel refuses to label it. After fdisk creating partitions try, dd if=/dev/zero of=/dev/da0s1 count=16 Then disklabel -r -w and disklabel -B Tru64-UNIX has a disklabel -z option which zeros out the disk label. Compaq and Digital before that recommended disklabel -z prior to laying down a new label. Should we consider a -z option for our disklabel? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 7:42:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 376CA37B479; Sat, 28 Oct 2000 07:42:13 -0700 (PDT) Received: from [194.207.93.139] by gate.trident-uk.co.uk for hackers@freebsd.org id OAA08146; Sat Oct 28 14:37:23 2000 Organization: Psi-Domain Ltd. Subject: Re: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware Date: Sat, 28 Oct 2000 15:41:25 +0100 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00102815431606.00181@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: hackers@freebsd.org, freebsd-stable@freebsd.org From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool idea. I will add a -z option to the disklabel code and submit it to the author if thats OK with everyone else? -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== On Sat, 28 Oct 2000, you wrote: > In message <200010271824.e9RIOLw06173@earth.backplane.com>, Matt Dillon > writes: > > :Do you have dangerously dedicated mode on by chance? Some > > :SCSI BIOS's _will_ crash with this if you use dangerously > > :dedicated mode. > > > > Yup. > > > > The real question is: Ok, so if I can't use dangerously dedicated > > mode, then how do I create a disklabel on a normal partition? Everything > > I try using fdisk and disklabel fails. fdisk will create a normal > > freebsd-dedicated dos partition, but disklabel refuses to label it. > > After fdisk creating partitions try, > > dd if=/dev/zero of=/dev/da0s1 count=16 > > Then disklabel -r -w and disklabel -B > > Tru64-UNIX has a disklabel -z option which zeros out the disk label. > Compaq and Digital before that recommended disklabel -z prior to laying > down a new label. Should we consider a -z option for our disklabel? > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca > Open Systems Group, ITSD, ISTA > Province of BC > > > > > > 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 Oct 28 7:58:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 960EC37B479; Sat, 28 Oct 2000 07:58:27 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA16110; Sat, 28 Oct 2000 07:58:20 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda16108; Sat Oct 28 07:58:06 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.0/8.9.1) id e9SEw5n16217; Sat, 28 Oct 2000 07:58:05 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdX16215; Sat Oct 28 07:57:50 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.1/8.9.1) id e9SEvmk09019; Sat, 28 Oct 2000 07:57:48 -0700 (PDT) Message-Id: <200010281457.e9SEvmk09019@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdXB9013; Sat Oct 28 07:57:03 2000 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.1.1-RELEASE X-Sender: cy To: Matt Dillon Cc: Fred Clift , hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h In-reply-to: Your message of "Fri, 27 Oct 2000 13:24:17 PDT." <200010272024.e9RKOHL07526@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Oct 2000 07:57:03 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010272024.e9RKOHL07526@earth.backplane.com>, Matt Dillon writes: > I think that the days of the 'dangerously dedicated partition' are > numbered. It has obviously caused much more havoc then people have > realized. We don't have time to fix it for the current release, but I > took a good hard look at the code and as far as I can tell the only > reason we *have* a dangerously dedicated partition at all is because > the disklabel code is too cheap to create a real one - it is just copying > the skeleton fdisk data from boot0 verbatim and leaving it. Disklabel > could very easily create a real partition - in fact, I think with my > proposed patch for labeling slices all it needs to do is exec > 'fdisk -I disk' to do it, and then generate a virgin label for the slice. The other reason to have dangerously dedicated disks is to support Zip and Jazz disks. For a while under 2.2.x or was it 3.x dangerously dedicated Zip disks did not work, requiring an fdisk label on the disks. During that period, I had to relabel all of my Zip disks with fdisk labels and subsequently remove them because of this. If we do remove dangerously dedicated, which I think is a good idea, special considerations for really dedicated disks, e.g. Zip and Jazz drives need to be taken into account. If that cannot be done, then making the change would have too much impact on Jazz and Zip disk users. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 8:14:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web9608.mail.yahoo.com (web9608.mail.yahoo.com [216.136.129.187]) by hub.freebsd.org (Postfix) with SMTP id 9121337B479 for ; Sat, 28 Oct 2000 08:14:37 -0700 (PDT) Message-ID: <20001028151437.26838.qmail@web9608.mail.yahoo.com> Received: from [155.239.82.78] by web9608.mail.yahoo.com; Sat, 28 Oct 2000 08:14:37 PDT Date: Sat, 28 Oct 2000 08:14:37 -0700 (PDT) From: Yorick Hardy Subject: pipe through ghostscript causes stdin EAGAIN error To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A problem with a program I have written (which pipes information to ghostscript) prompted me to check the following cat | gs -sDEVICE=ppmraw - which gives the result from cat(as soon as a newline is entered) cat: stdin: Resource temporarily unavailable (i.e. the error EAGAIN). I am using 4-STABLE, tcsh as the shell and gs6.01. Is ghostscript at fault? In my program, ensuring that all the standard descriptors(stdin,stdout and stderr) were closed before the exec, solved the problem. Is there some way that ghostscript can influence stdin when it only has access to stderr? I tried search the ghostscript code for an explanation, but I could not find any ioctl or fcntl calls relating to the standard descriptors. Thank you for any suggestions. Yorick Hardy __________________________________________________ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 8:46:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Mail.Openet-Telecom.COM (unknown [193.120.50.79]) by hub.freebsd.org (Postfix) with ESMTP id 825EB37B479 for ; Sat, 28 Oct 2000 08:46:41 -0700 (PDT) Received: from openet-telecom.com (rocklobster.openet-telecom.lan [10.0.0.40]) by Mail.Openet-Telecom.COM (8.9.3/8.9.3) with ESMTP id QAA37229; Sat, 28 Oct 2000 16:47:12 +0100 (IST) (envelope-from peter.edwards@openet-telecom.com) Message-ID: <39FAF500.526FFD69@openet-telecom.com> Date: Sat, 28 Oct 2000 16:47:12 +0100 From: Peter Edwards Organization: Openet Telecom X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Trent Nelson Cc: David van Deijk , freebsd-hackers@FreeBSD.ORG Subject: Re: dir-listing bug in linux-emulation References: <39F82D3C.2532AEB7@student.tue.nl> <39F8F53C.A500A16B@echidna.stu.cowan.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Here's a patch that fixes the problem for me. can someone review and possibly commit it? Here's my understanding: The data returned by VOP_READDIR is not neccessarily the same as that consumed from the directory vnode. linux_getdents fills in a "doff" field in the linux_dirent structure using the offset from the start of the read data rather than the offset in the directory vnode that produced that directory entry. Then, rather than continuing where it left off, the linux "ls" command uses this as an offset to seek to before the next time it calls linux_getdents, (actually seeking back over data it's already read, for some reason). The correct offset is provided via the VOP_READDIR "cookies" when available. For the code-path that I can produce, the following patch makes linux's ls work on my -stable box for ufs, cd9660, and msdos filesystems. diff -c -r1.38.2.2 linux_file.c *** src/sys/i386/linux/linux_file.c 2000/07/19 21:12:39 1.38.2.2 --- src/sys/i386/linux/linux_file.c 2000/10/28 15:21:35 *************** *** 498,504 **** linux_dirent.doff = (linux_off_t) linuxreclen; linux_dirent.dreclen = (u_short) bdp->d_namlen; } else { ! linux_dirent.doff = (linux_off_t)(off + reclen); linux_dirent.dreclen = (u_short) linuxreclen; } strcpy(linux_dirent.dname, bdp->d_name); --- 498,504 ---- linux_dirent.doff = (linux_off_t) linuxreclen; linux_dirent.dreclen = (u_short) bdp->d_namlen; } else { ! linux_dirent.doff = (linux_off_t)(cookiep ? *cookiep : off+reclen); linux_dirent.dreclen = (u_short) linuxreclen; } strcpy(linux_dirent.dname, bdp->d_name); I'm not sure about the "justone" case: I'll have to read the code more carefully, since I can't get this code to execute without an older linux "ls". Trent Nelson wrote: > > David van Deijk wrote: > > > > Dear hackers. > > > > When I was running an linux program (soffice) i needed something of my > > dos-partition. > > Then i stumbled onto something I would call a "major" bug. > > > > I went to /dos/c (my first partition ) but saw only 6 files and 1 dir. > > So i went for some exploring and this are my results: > > > PS. any other persons confirming (or not) this problem would be > > welcome. > > Yup, I had the exact same problem running Star Office 5.2 in > 5.0-current. > > > Trent. > > 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 Oct 28 12:16:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Mail.Openet-Telecom.COM (unknown [193.120.50.79]) by hub.freebsd.org (Postfix) with ESMTP id C0E5437B479 for ; Sat, 28 Oct 2000 12:16:40 -0700 (PDT) Received: from openet-telecom.com (rocklobster.openet-telecom.lan [10.0.0.40]) by Mail.Openet-Telecom.COM (8.9.3/8.9.3) with ESMTP id UAA37641; Sat, 28 Oct 2000 20:17:35 +0100 (IST) (envelope-from peter.edwards@openet-telecom.com) Message-ID: <39FB264F.EEFB5AE1@openet-telecom.com> Date: Sat, 28 Oct 2000 20:17:35 +0100 From: Peter Edwards Organization: Openet Telecom X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Trent Nelson , David van Deijk , freebsd-hackers@FreeBSD.ORG Subject: Re: dir-listing bug in linux-emulation References: <39F82D3C.2532AEB7@student.tue.nl> <39F8F53C.A500A16B@echidna.stu.cowan.edu.au> <39FAF500.526FFD69@openet-telecom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, It appears, on second look, a little more complex. The cookies are used properly in most places, but the fix was introduced in 1.36 breaks it. I understand what's going on now, and I'll try a for a more complete patch... Watch this space! -- Peter. Peter Edwards wrote: > > Hi, > Here's a patch that fixes the problem for me. can someone review and > possibly commit it? > > Here's my understanding: > > The data returned by VOP_READDIR is not neccessarily the same as that > consumed from the directory vnode. > > linux_getdents fills in a "doff" field in the linux_dirent structure > using the offset from the start of the read data rather than the offset > in the directory vnode that produced that directory entry. > > Then, rather than continuing where it left off, the linux "ls" command > uses this as an offset to seek to before the next time it calls > linux_getdents, (actually seeking back over data it's already read, for > some reason). > > The correct offset is provided via the VOP_READDIR "cookies" when > available. For the code-path that I can produce, the following patch > makes linux's ls work on my -stable box for ufs, cd9660, and msdos > filesystems. > > diff -c -r1.38.2.2 linux_file.c > *** src/sys/i386/linux/linux_file.c 2000/07/19 21:12:39 1.38.2.2 > --- src/sys/i386/linux/linux_file.c 2000/10/28 15:21:35 > *************** > *** 498,504 **** > linux_dirent.doff = (linux_off_t) linuxreclen; > linux_dirent.dreclen = (u_short) bdp->d_namlen; > } else { > ! linux_dirent.doff = (linux_off_t)(off + reclen); > linux_dirent.dreclen = (u_short) linuxreclen; > } > strcpy(linux_dirent.dname, bdp->d_name); > --- 498,504 ---- > linux_dirent.doff = (linux_off_t) linuxreclen; > linux_dirent.dreclen = (u_short) bdp->d_namlen; > } else { > ! linux_dirent.doff = (linux_off_t)(cookiep ? *cookiep : > off+reclen); > linux_dirent.dreclen = (u_short) linuxreclen; > } > strcpy(linux_dirent.dname, bdp->d_name); > > I'm not sure about the "justone" case: I'll have to read the code more > carefully, since I can't get this code to execute without an older linux > "ls". > > Trent Nelson wrote: > > > > David van Deijk wrote: > > > > > > Dear hackers. > > > > > > When I was running an linux program (soffice) i needed something of my > > > dos-partition. > > > Then i stumbled onto something I would call a "major" bug. > > > > > > I went to /dos/c (my first partition ) but saw only 6 files and 1 dir. > > > So i went for some exploring and this are my results: > > > > > PS. any other persons confirming (or not) this problem would be > > > welcome. > > > > Yup, I had the exact same problem running Star Office 5.2 in > > 5.0-current. > > > > > > Trent. > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 14: 4:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id EE21C37B4C5; Sat, 28 Oct 2000 14:04:38 -0700 (PDT) Received: by peorth.iteration.net (Postfix, from userid 1001) id 9C1005730B; Sat, 28 Oct 2000 16:04:38 -0500 (CDT) Date: Sat, 28 Oct 2000 16:04:38 -0500 From: "Michael C . Wu" To: i18n@freebsd.org Cc: hackers@freebsd.org Subject: Need dotfiles for various L10N groups Message-ID: <20001028160438.A86353@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [cc'ed to -hackers because I know that not everyone reads -i18n] Hello everyone, I am trying to collect various dotfiles (.cshrc, .profile, .Xresources, .Xdefaults, ~/.*) for various language localization groups. As I discussed with Nik Clayton, I hope to create /usr/share/skel/{chinese, japanese, french, russian, korean, vietnamese *} Then I will add an option to adduser(8) and sysinstall configure to choose whatever language you want the user to have. However, since I don't speak so many languages, I need your help. :) Please email me the dotfiles that you use, and I will clean them up for review. Right now we need the following: (Please tell me if your language group does not appear here) All of the European languages, including but not limited to French, British English, Spanish, Portugese, Danish, German, Russian, Italian, Finnish Do locales exist for Brazilian Portugese or places like South Africa? Asian Languages: Chinese(traditional, simplified, cantonese), Japanese (JIS, EUC, etc.), Korean, Vietnamese (Yes, I am ignoring en_US.ISO8859-1. ;) ) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: d+phPyMCvh1DnxMMa4AhPiboysZ6NyiU iQA/AwUBOfsxVXfOKcWPoS4gEQK8HgCg2WNSxz/cgXyCRQkgt+F/nUlh8vsAmwcC atoVNfygR6h66HHO+qWnymAQ =Vr9P -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 14:58:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8359237B4C5; Sat, 28 Oct 2000 14:58:44 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9SLw8f22894; Sat, 28 Oct 2000 14:58:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010281418.e9SEImB08772@cwsys.cwsent.com> Date: Sat, 28 Oct 2000 14:59:01 -0700 (PDT) From: John Baldwin To: Cy Schubert - ITSD Open Systems Group Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: "freebsd-stable@FreeBSD.ORG" Cc: "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.org, Matt Dillon Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-00 Cy Schubert - ITSD Open Systems Group wrote: > In message <200010271824.e9RIOLw06173@earth.backplane.com>, Matt Dillon > writes: >> :Do you have dangerously dedicated mode on by chance? Some >> :SCSI BIOS's _will_ crash with this if you use dangerously >> :dedicated mode. >> >> Yup. >> >> The real question is: Ok, so if I can't use dangerously dedicated >> mode, then how do I create a disklabel on a normal partition? >> Everything >> I try using fdisk and disklabel fails. fdisk will create a normal >> freebsd-dedicated dos partition, but disklabel refuses to label it. > > After fdisk creating partitions try, > > dd if=/dev/zero of=/dev/da0s1 count=16 > > Then disklabel -r -w and disklabel -B Nope, I tried that. Without Dillon's patch, disklabel cannot create a virgin disklabel on a slice. Period. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 15:28:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CD5F137B479; Sat, 28 Oct 2000 15:28:25 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9SMSFu67012; Sat, 28 Oct 2000 15:28:15 -0700 (PDT) (envelope-from dillon) Date: Sat, 28 Oct 2000 15:28:15 -0700 (PDT) From: Matt Dillon Message-Id: <200010282228.e9SMSFu67012@earth.backplane.com> To: Matthew Jacob , John Baldwin , Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > After fdisk creating partitions try, :> > :> > dd if=/dev/zero of=/dev/da0s1 count=16 : :Hmm. Isn't the only thing that's suppose to really work is : :dd if=/dev/zero of=/dev/da0 count=16 : :(which doesn't always work on Alpha yet) : :I'm missing some context, so forgive me if this is a stupid question? Ah, the joys of fdisk and disklabels. I've learned more in the last two days then I ever really wanted to find out :-) # clear out feldercarp at the base of the # disk and create a real slice for freebsd. Install # the MBR. # dd if=/dev/zero of=/dev/da0 count=16 fdisk -BI da0 # clear out feldercarp in the slice and then disklabel the * slice (using my patch) + the boot blocks # dd if=/dev/zero of=/dev/da0s1 count=16 disklabel -w -r -B da0s1 auto Presumably a '-z' option to disklabel would do the equivalent of what the 'dd' in the above examples are doing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 15:57:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C84A37B479; Sat, 28 Oct 2000 15:57:40 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA27904; Sat, 28 Oct 2000 15:57:39 -0700 Date: Sat, 28 Oct 2000 15:57:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matt Dillon Cc: John Baldwin , Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h In-Reply-To: <200010282228.e9SMSFu67012@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ah, the joys of fdisk and disklabels. I've learned more in the last > two days then I ever really wanted to find out :-) > > # clear out feldercarp at the base of the > # disk and create a real slice for freebsd. Install > # the MBR. > # > dd if=/dev/zero of=/dev/da0 count=16 > fdisk -BI da0 > > # clear out feldercarp in the slice and then disklabel the > * slice (using my patch) + the boot blocks > # > dd if=/dev/zero of=/dev/da0s1 count=16 > disklabel -w -r -B da0s1 auto > > Presumably a '-z' option to disklabel would do the equivalent of what > the 'dd' in the above examples are doing. I guess. There's always some hack to dd me and David O'Brien keep asking about adding- you have to do the DIOCWLABEL. This keeps on getting discussed over and over and over again. Bruce claims to understand all of this- I sure don't. I *do* know that dangerously dedicated disks that are built on i386 aren't readable on alpha (a mistake that linux avoids). I have some mail going back a year saying "this all has to be fixed for 4.0!". Guess what? The story probably is "somebody needs to own the issue" and it hasn't reached a level of pain for me to do that (other things are far more painful). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 16:12:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E4C6B37B479; Sat, 28 Oct 2000 16:12:22 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e9SNCS804076; Sun, 29 Oct 2000 00:12:28 +0100 (BST) (envelope-from nik) Date: Sun, 29 Oct 2000 00:12:28 +0100 From: Nik Clayton To: "Michael C . Wu" Cc: i18n@freebsd.org, hackers@freebsd.org Subject: Re: Need dotfiles for various L10N groups Message-ID: <20001029001228.A4049@canyon.nothing-going-on.org> References: <20001028160438.A86353@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001028160438.A86353@peorth.iteration.net>; from keichii@iteration.net on Sat, Oct 28, 2000 at 04:04:38PM -0500 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 28, 2000 at 04:04:38PM -0500, Michael C . Wu wrote: > I am trying to collect various dotfiles (.cshrc, .profile, .Xresources, > .Xdefaults, ~/.*) for various language localization groups. > As I discussed with Nik Clayton, I hope to create > /usr/share/skel/{chinese, japanese, french, russian, korean, vietnamese *} Shouldn't these be /usr/share/skel/{ja_JP.eucJP, zh_TW.Big5, ...} to cater for the same language/multiple encodings problem? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 16:13:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id D661A37B479; Sat, 28 Oct 2000 16:13:42 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id CAA21032; Sun, 29 Oct 2000 02:13:40 +0300 (MSK) Message-Id: <200010282313.CAA21032@aaz.links.ru> Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h In-Reply-To: from "John Baldwin" at "Oct 28, 0 02:59:01 pm" To: jhb@FreeBSD.ORG (John Baldwin) Date: Sun, 29 Oct 2000 02:13:40 +0300 (MSK) Cc: Cy.Schubert@uumail.gov.bc.ca, freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG, dillon@earth.backplane.com From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > On 28-Oct-00 Cy Schubert - ITSD Open Systems Group wrote: > > In message <200010271824.e9RIOLw06173@earth.backplane.com>, Matt Dillon > > writes: > >> :Do you have dangerously dedicated mode on by chance? Some > >> :SCSI BIOS's _will_ crash with this if you use dangerously > >> :dedicated mode. > >> > >> Yup. > >> > >> The real question is: Ok, so if I can't use dangerously dedicated > >> mode, then how do I create a disklabel on a normal partition? > >> Everything > >> I try using fdisk and disklabel fails. fdisk will create a normal > >> freebsd-dedicated dos partition, but disklabel refuses to label it. > > > > After fdisk creating partitions try, > > > > dd if=/dev/zero of=/dev/da0s1 count=16 > > > > Then disklabel -r -w and disklabel -B > Nope, I tried that. Without Dillon's patch, disklabel cannot create > a virgin disklabel on a slice. Period. I know English bad ... let me see ... what "virgin" mean ... See! disklabel CAN create a virgin disklabel on a slice. Period. just supply the real entry from disktab. For example disklabel -r -w ad0sX fd360 disklabel -e ad0sX works in any case. Yes, it is hack, I understand. And I use about 20 my own entryes in disktab for all slise sizes I ever use. This is not stright, but not annoy. What is real annoyance: it is impossible to read label twice if more then one label are present on a disk in DD mode. It is very bad because of bug in kernel, not userland. > -- > > 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 > -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 16:28:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wolf.istc.kiev.ua (wolf.istc.kiev.ua [193.193.221.1]) by hub.freebsd.org (Postfix) with ESMTP id 63E4137B479; Sat, 28 Oct 2000 16:28:50 -0700 (PDT) Received: from localhost (kunia@localhost) by wolf.istc.kiev.ua ( . . / . . ) with ESMTP id CAA03619; Sun, 29 Oct 2000 02:26:18 +0300 Date: Sun, 29 Oct 2000 02:26:18 +0300 (EEST) From: Olexander Kunytsa To: Nik Clayton Cc: "Michael C . Wu" , i18n@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Need dotfiles for various L10N groups In-Reply-To: <20001029001228.A4049@canyon.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Oct 2000, Nik Clayton wrote: > > I am trying to collect various dotfiles (.cshrc, .profile, .Xresources, > > .Xdefaults, ~/.*) for various language localization groups. > > As I discussed with Nik Clayton, I hope to create > > /usr/share/skel/{chinese, japanese, french, russian, korean, vietnamese *} > > Shouldn't these be /usr/share/skel/{ja_JP.eucJP, zh_TW.Big5, ...} to cater > for the same language/multiple encodings problem? > It would be better to use in such way, I think. I myself can make /usr/share/skel/uk_UA.KOI8-U/* for Ukrainian lang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 18:58:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 440D537B4C5; Sat, 28 Oct 2000 18:58:52 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9T1woA67627; Sat, 28 Oct 2000 18:58:50 -0700 (PDT) (envelope-from dillon) Date: Sat, 28 Oct 2000 18:58:50 -0700 (PDT) From: Matt Dillon Message-Id: <200010290158.e9T1woA67627@earth.backplane.com> To: John Baldwin , Terry Lambert , (Paul Saab) , (Danny Braniss) , freebsd-stable@FreeBSD.org, hackers@FreeBSD.org Subject: Disklabel patch committed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've committed the disklabel patch, plus updated documentation for disklabel.8, into 4.x. Please report any problems directly to me. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 19: 0: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id CA52337B479; Sat, 28 Oct 2000 19:00:01 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9T1xKf27087; Sat, 28 Oct 2000 18:59:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010282228.e9SMSFu67012@earth.backplane.com> Date: Sat, 28 Oct 2000 19:00:14 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, Cy Schubert - ITSD Open Systems Group , Matthew Jacob Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-00 Matt Dillon wrote: >:> > After fdisk creating partitions try, >:> > >:> > dd if=/dev/zero of=/dev/da0s1 count=16 >: >:Hmm. Isn't the only thing that's suppose to really work is >: >:dd if=/dev/zero of=/dev/da0 count=16 >: >:(which doesn't always work on Alpha yet) >: >:I'm missing some context, so forgive me if this is a stupid question? > > Ah, the joys of fdisk and disklabels. I've learned more in the last > two days then I ever really wanted to find out :-) I think there is more there than anyone wants to find out. Can you commit your fixes to make disklabel label virgin slices please? -- 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 Oct 28 20:41:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 11A8A37B479 for ; Sat, 28 Oct 2000 20:41:17 -0700 (PDT) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id VAA86456 for ; Sat, 28 Oct 2000 21:45:07 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sat, 28 Oct 2000 21:45:07 -0600 (CST) From: Ryan Thompson To: freebsd-hackers@freebsd.org Subject: Filesystem holes Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all... One the tasks that I have undertaken lately is to improve the efficiency of a couple of storage facilities we use internally, here. Basically, they are moderate-size tables currently implemented in SQL, which is OK in terms of performance, but the hash function is breaking down and the storage is rather inefficient for our table of about 2,850,000 members (~2.1 GB total storage). There are 64M possible hash values in our current implementation, and our record size is variable, but could be safely fixed at about 1.5KB... So, total storage if all values were used would be about 96GB. (See where I'm going with this?) One of the options I am considering is actually using address calculation, and taking advantage of filesystem holes, to keep storage down to what is actually being used, while providing instant lookups. The single file would be about 96G addressable bytes... But the actual block count would be much lower. I suppose I will have to create a series of these files and divide the problem into < 4GB chunks, but one lookup/store will still be done with one calculation and one disk seek (just more filehandles open). Deletes seem problematic. My question is, does the operating system provide any way to free blocks used in the middle of a file? Must I periodically re-create these files (long and slow process, but not so bad if done infrequently) to reclaim space, or is there a way to free arbitrary blocks in a file in userland (WITHOUT trashing the filesystem? :-) - Ryan -- Ryan Thompson Network Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 21:31:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id BF4DE37B479; Sat, 28 Oct 2000 21:31:39 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9T4VdP68089; Sat, 28 Oct 2000 21:31:39 -0700 (PDT) (envelope-from dillon) Date: Sat, 28 Oct 2000 21:31:39 -0700 (PDT) From: Matt Dillon Message-Id: <200010290431.e9T4VdP68089@earth.backplane.com> To: John Baldwin Cc: hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, Cy Schubert - ITSD Open Systems Group , Matthew Jacob Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think there is more there than anyone wants to find out. Can you commit :your fixes to make disklabel label virgin slices please? : :John Baldwin -- http://www.FreeBSD.org/~jhb/ Yah, it's done. I'll forward merge it from -stable -> -current after the release is rolled. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 21:33:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 0041E37B479; Sat, 28 Oct 2000 21:33:40 -0700 (PDT) Received: by peorth.iteration.net (Postfix, from userid 1001) id 062DE5730B; Sat, 28 Oct 2000 23:33:38 -0500 (CDT) Date: Sat, 28 Oct 2000 23:33:37 -0500 From: "Michael C . Wu" To: Olexander Kunytsa Cc: Nik Clayton , i18n@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Need dotfiles for various L10N groups Message-ID: <20001028233337.A88806@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20001029001228.A4049@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kunia@wolf.istc.kiev.ua on Sun, Oct 29, 2000 at 02:26:18AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 29, 2000 at 02:26:18AM +0300, Olexander Kunytsa scribbled: | On Sun, 29 Oct 2000, Nik Clayton wrote: | > > I am trying to collect various dotfiles (.cshrc, .profile, .Xresources, | > > .Xdefaults, ~/.*) for various language localization groups. | > > As I discussed with Nik Clayton, I hope to create | > > /usr/share/skel/{chinese, japanese, french, russian, korean, vietnamese *} | > | > Shouldn't these be /usr/share/skel/{ja_JP.eucJP, zh_TW.Big5, ...} to cater | > for the same language/multiple encodings problem? | > | It would be better to use in such way, I think. I myself can make | /usr/share/skel/uk_UA.KOI8-U/* for Ukrainian lang Yes, you are right. I failed to remember this and I will do it this way. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 28 22:47:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by hub.freebsd.org (Postfix) with ESMTP id 875F237B479 for ; Sat, 28 Oct 2000 22:47:55 -0700 (PDT) Received: from fondue.ICSI.Berkeley.EDU (fondue.ICSI.Berkeley.EDU [192.150.186.19]) by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id WAA29830; Sat, 28 Oct 2000 22:47:54 -0700 (PDT) Received: from localhost (rizzo@localhost) by fondue.ICSI.Berkeley.EDU (8.8.2/1.8) with ESMTP id WAA10082; Sat, 28 Oct 2000 22:47:54 -0700 (PDT) X-Authentication-Warning: fondue.ICSI.Berkeley.EDU: rizzo owned process doing -bs Date: Sat, 28 Oct 2000 22:47:53 -0700 (PDT) From: Luigi Rizzo To: Ryan Thompson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem holes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, how about using an indirect table of 64M 32-bit pointers into the actual blocks being used ? For insertions you just allocate a new fixed size block from the file. For deletion, either keep a list of freed blocks, or provide a back pointer from each entry into the hash table so when you remove a block (creating a hole) you can move the last allocated one into the hole and update the hash table. Kind of quick. You might have to pay an extra disk access on each access but given enough memory you'd save that one as well. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- On Sat, 28 Oct 2000, Ryan Thompson wrote: > > Hi all... > > One the tasks that I have undertaken lately is to improve the efficiency > of a couple of storage facilities we use internally, here. Basically, > they are moderate-size tables currently implemented in SQL, which is OK in > terms of performance, but the hash function is breaking down and the > storage is rather inefficient for our table of about 2,850,000 members > (~2.1 GB total storage). There are 64M possible hash values in our > current implementation, and our record size is variable, but could be > safely fixed at about 1.5KB... So, total storage if all values were used > would be about 96GB. (See where I'm going with this?) > > One of the options I am considering is actually using address calculation, > and taking advantage of filesystem holes, to keep storage down to what is > actually being used, while providing instant lookups. > > The single file would be about 96G addressable bytes... But the actual > block count would be much lower. I suppose I will have to create a series > of these files and divide the problem into < 4GB chunks, but one > lookup/store will still be done with one calculation and one disk seek > (just more filehandles open). > > Deletes seem problematic. My question is, does the operating system > provide any way to free blocks used in the middle of a file? > > Must I periodically re-create these files (long and slow process, but not > so bad if done infrequently) to reclaim space, or is there a way to free > arbitrary blocks in a file in userland (WITHOUT trashing the filesystem? > :-) > > - Ryan > > -- > Ryan Thompson > Network Administrator, Accounts > Phone: +1 (306) 664-1161 > > SaskNow Technologies http://www.sasknow.com > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message