From owner-freebsd-hackers Sun Jun 27 0:14:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 252D414C93 for ; Sun, 27 Jun 1999 00:14:27 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id JAA14203; Sun, 27 Jun 1999 09:07:07 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id JAA03124; Sun, 27 Jun 1999 09:14:06 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id JAA38622; Sun, 27 Jun 1999 09:14:53 +0200 (CEST) (envelope-from ticso) Date: Sun, 27 Jun 1999 09:14:53 +0200 From: Bernd Walter To: Greg Lehey Cc: Ollivier Robert , freebsd-hackers@FreeBSD.ORG Subject: Re: Volume managers (was: ufs/ffs resize?) Message-ID: <19990627091453.A38541@cicely8.cicely.de> References: <199906252100.OAA31969@sigma.veritas.com> <19990626195554.A37269@cicely8.cicely.de> <19990627003554.A25754@keltia.freenix.fr> <19990627093345.O427@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990627093345.O427@freebie.lemis.com>; from Greg Lehey on Sun, Jun 27, 1999 at 09:33:45AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 27, 1999 at 09:33:45AM +0930, Greg Lehey wrote: > On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote: > > I think one of the difficulty of growing a FS is that you have to > > choose whether you need the FS to be contiguous or not. The latter > > case makes it much more difficult... > > Why shouldn't it be contiguous? That's what the volume manager's > there for. > It should be always possible to add some blocks to an existing volume without a gap between. The problem is shrinking. You usually want to shrink a fs not because you want it smaller but you want to free a harddisk. Murphy says that this disk is at the beginning or the middle of the partition. If Murphy had a good day he says this disk is part of a stripe... What system should handle this case? For FFS it might be better handled by the volume-managaer because it should be difficult to implement GAP-Handling in FFS LFSs daily job is to do such jobs as a kind of garbadge collection so it should be much faster and easier if handled by the fs - but that would mean the fs need to know about the volumes details. There are some other points left with interaction of volumemanagers and Filesystem instead of shrinking and growing. Say you have a concatenated volume with 3 disks. One drive fails without any chance to get it up again. Vinum takes the plex and because it's the only one the volume too. There no kind of emergency mode in which you can say - bring that volume up with a large defektive area in them so I can mount read-only and try to read everthing I can. Instead of CCD vinum knows how big the failed disk was. One other point is that it is not possible with vinum or ccd to add space to a striped/raid5 volume. One way might be to use ccd to concat striped vinum volumes - never tried. But in my opinion that's not the way it should be. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 0:33:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id BF22A14E57 for ; Sun, 27 Jun 1999 00:33:11 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 37241 invoked by uid 1001); 27 Jun 1999 07:33:10 +0000 (GMT) To: k.stevenson@louisville.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ufs/ffs resize? From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 26 Jun 1999 21:12:59 -0400" References: <19990626211259.B15044@homer.louisville.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Sun, 27 Jun 1999 09:33:09 +0200 Message-ID: <37239.930468789@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Another datapoint ot consider, it seems that Linux (at least the derivative > > version maintained by Alan Cox -- the other one :) ) has now grown an LVM > > system (probably à la HP or AIX). That's what I've been told yesterday during > > a small conference about Linux and free software in France (and where I did a > > talk about FreeBSD *grin*). > > Hmmm. It might be from SGI. SGI has donated XFS to Linux and is actively > marketing it on their Intel based systems. > > http://www.news.com/News/Item/0,4,36807,00.html?st.ne.fd.tohhed.ni As far as I know it's way too early for the Linux LVM to based on XFS, since SGI hasn't even released the source code yet (just stated that they intend to do so). Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 0:34: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B1D714E57 for ; Sun, 27 Jun 1999 00:34:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA10635; Sun, 27 Jun 1999 00:33:35 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 00:33:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199906270733.AAA10635@apollo.backplane.com> To: "Daniel J. O'Connor" Cc: Jesus Monroy , Ville-Pertti Keinonen , hackers@FreeBSD.ORG, "Daniel J.OConnor" Subject: Re: [Re: [Re: coarse vs fine-grained locking in SMP systems]] References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the basic problem: The kernel is currently designed for single-threaded operation plus interrupt handling. A piece of code in the kernel can temporarily disable certain interrupts with the spl*() codes to cover situations where a race on some system resource might occur. But with SMP, several cpu's may be running in supervisor mode simultaniously. The spl*() model breaks down because while one can block interrupts, one cannot easily block another cpu that might be running conflicting code. Resource races can now occur between mainline code running on several cpu's simultaniously as well as between mainline code and interrupt code. The traditional BSD kernel code cannot deal with this new type of race. At the moment every entry into supervisor mode is being governed by a "big giant lock" which only allows one cpu to run mainline code in supervisor mode at any given moment. Both cpu's can run usermode code simultaniously just fine, but only one can run supervisor code. In order to make SMP operation work better, pieces of the kernel are slowly being moved outside the "big giant lock". Linux developers, in fact, have already moved their core data copying code and their TCP stack outside the lock. At the moment the FreeBSD-current kernel has not moved anything outside the lock, but John Dyson has shown that it is fairly easy to move certain specific pieces such as the uiomove() code outside the lock, though inefficiencies from side-effects currently make the improvement in performance less then steller. The real question is how to manage concurrency as pieces get moved outside the lock. There are lots of ways to do it. One can use spin locks to protect resources or, as someone pointed out earlier, to protect sections of code. I don't know which is better myself, it probably depends on the situation so a hybrid will probably be the end result. One can also use kernel threads to simplify resource management. The advantage of a kernel thread verses a normal process is in the ability to switch between kernel threads very quickly, allowing the time normally wasted spining in certain types of locks to be used more efficiently. The problem that generally needs to be solved is the problem of stalling on a resource. For example, if you have several threads running simultaniously and they all need access to the same resource, serialization of the threads occurs due to the 'blockage' on access to the resource. (serialization means that only one thread can run at a time within the resource, which means your efficiency drops to the efficiency of only a single cpu). There are lots of other issues (such as cache efficiency), but that is the big one. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 0:54:43 1999 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 80813151E7 for ; Sun, 27 Jun 1999 00:54:38 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA88827; Sun, 27 Jun 1999 01:54:38 -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 BAA09021; Sun, 27 Jun 1999 01:52:44 -0600 (MDT) Message-Id: <199906270752.BAA09021@harmony.village.org> To: Matthew Dillon Subject: Re: [Re: [Re: coarse vs fine-grained locking in SMP systems]] Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Jun 1999 00:33:35 PDT." <199906270733.AAA10635@apollo.backplane.com> References: <199906270733.AAA10635@apollo.backplane.com> Date: Sun, 27 Jun 1999 01:52:44 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906270733.AAA10635@apollo.backplane.com> Matthew Dillon writes: : Here's the basic problem: The kernel is currently designed for : single-threaded operation plus interrupt handling. A piece of code : in the kernel can temporarily disable certain interrupts with the : spl*() codes to cover situations where a race on some system resource : might occur. : : But with SMP, several cpu's may be running in supervisor mode : simultaniously. The spl*() model breaks down because while one : can block interrupts, one cannot easily block another cpu that : might be running conflicting code. Resource races can now occur between : mainline code running on several cpu's simultaniously as well as between : mainline code and interrupt code. Yes. However, the spl* model could also be viewed as a few very basic locks. so splnet would block the net interrupts and take out the net mutex, etc. When splx is executed, the interrupts are restored to their old value and the net mutex could be released. In this case the return value of spl* becomes a cookie that can be used to restore both the prior interrupt context, as well as release the mutex aquired. There are problems with this approach, as I believe early efforts in the FreeBSD/SMP project can attest, but I don't recall the details of them. It was originally thought that this could be made to work, if I recall the few messages about SMP that I saw, since you are effectively emulating the spl mechanism accross CPUS. VMS 5.0 introduced a similar concept as well. To get access to a resource, you'd raise the SPL level of the CPU (to keep the hardware devices from interrupting you) and then take out a spin lock (to keep the other CPUs from doing the same). : In order to make SMP operation work better, pieces of the kernel are : slowly being moved outside the "big giant lock". Linux developers, : in fact, have already moved their core data copying code and their TCP : stack outside the lock. At the moment the FreeBSD-current kernel has : not moved anything outside the lock, but John Dyson has shown that it : is fairly easy to move certain specific pieces such as the uiomove() : code outside the lock, though inefficiencies from side-effects currently : make the improvement in performance less then steller. That is correct. At Solbourne[*], we were honest enough to call the one big lock approach ASMP (any CPU could run in kernel mode, but only one at a time). Linux's (and FreeBSD's) SMP has really been mostly ASMP, with a little bit of fine grain locking in the corners. [*] Solbourne, for those of you that don't know, made sparc servers (and one workstation) several years ago. They were SMP years before Sun managed to ship SMP support in Solrais. Many of my SMP "gut feelings" were developed while working there. : The real question is how to manage concurrency as pieces get moved outside : the lock. There are lots of ways to do it. One can use spin locks to : protect resources or, as someone pointed out earlier, to protect sections : of code. I don't know which is better myself, it probably depends on the : situation so a hybrid will probably be the end result. One can also use : kernel threads to simplify resource management. The advantage of a : kernel thread verses a normal process is in the ability to switch between : kernel threads very quickly, allowing the time normally wasted spining in : certain types of locks to be used more efficiently. Solaris wound up using mutexes, condition variables, and semaphores to accomplish this. I don't know the exact details of what they did on a resource stall, however. The ddk tended to discourage exploration of this. I believe it was simply the thread stalled and another thread were allowed to run. I don't know how the scheduler itself was protected. Given that you have a threading kernel, making it SMP safe is generally fairly easy, modulo locking issues. The biggest area that both Solbourne, VMS and Solaris had in their early versions were making sure that deadlock didn't happen. Locks were always a real SOB to get right, and generally the cause of all kinds of problems. When I was testing Solbourne OS/MP 4.0C, I'd say that 95% of the difficult to reproduce problems turned out to be locking related and 60% of the easily reproducible were locking related. The years may have colored my rememberences of the percentages and the version numbers for OS/MP, but it is the one thing that stands out in my mind accross the 9 years it has been since I was doing that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 1: 5:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 4AD0D14C58 for ; Sun, 27 Jun 1999 01:05:46 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA12447; Sun, 27 Jun 1999 17:35:42 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA14962; Sun, 27 Jun 1999 17:35:40 +0930 (CST) Date: Sun, 27 Jun 1999 17:35:40 +0930 From: Greg Lehey To: sthaug@nethelp.no Cc: k.stevenson@louisville.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: ufs/ffs resize? Message-ID: <19990627173540.J427@freebie.lemis.com> References: <19990626211259.B15044@homer.louisville.edu> <37239.930468789@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <37239.930468789@verdi.nethelp.no>; from sthaug@nethelp.no on Sun, Jun 27, 1999 at 09:33:09AM +0200 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 27 June 1999 at 9:33:09 +0200, sthaug@nethelp.no wrote: >>> Another datapoint ot consider, it seems that Linux (at least the derivative >>> version maintained by Alan Cox -- the other one :) ) has now grown an LVM >>> system (probably à la HP or AIX). That's what I've been told yesterday during >>> a small conference about Linux and free software in France (and where I did a >>> talk about FreeBSD *grin*). >> >> Hmmm. It might be from SGI. SGI has donated XFS to Linux and is actively >> marketing it on their Intel based systems. >> >> http://www.news.com/News/Item/0,4,36807,00.html?st.ne.fd.tohhed.ni > > As far as I know it's way too early for the Linux LVM to based on XFS, > since SGI hasn't even released the source code yet (just stated that > they intend to do so). There's another reason: XFS is a file system, not a volume manager. A volume manager is more like a disk than a file system. In fact, I've seen the Linux LVM before; it's been around for a while, but last time I looked at it I wasn't very interesting. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 2:59:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id EA186151B2 for ; Sun, 27 Jun 1999 02:59:32 -0700 (PDT) (envelope-from fare@tunes.org) Received: (qmail 12590 invoked from network); 27 Jun 1999 09:47:23 -0000 Received: from d153.paris-131.cybercable.fr (HELO ZhengHe) ([212.198.131.153]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 27 Jun 1999 09:47:23 -0000 Received: from fare by ZhengHe with local (Exim 2.11 #1 (Debian)) id 10yBV8-00014B-00; Sun, 27 Jun 1999 11:45:26 +0200 Date: Sun, 27 Jun 1999 11:45:26 +0200 From: Francois-Rene Rideau To: Linux Kernel Cc: FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel Subject: Improving the Unix API Message-ID: <19990627114526.A10755@ZhengHe.augustin.thierry> Reply-To: Francois-Rene Rideau Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Improving the Unix Kernels' API A Kernel Discussion with Hacker Robert Ehrlich Summary: after a discussion with R.E., I submit a suggestion about improving the API of free Unices with useful features such as open(path,O_NULL); Dear Free *n*x Kernel Hackers, I've been discussing today with old-time Unix hacker (since V6 or so) Robert.Ehrlich@inria.fr about possible improvements in the design of Unix APIs in general, and to the Linux kernel in particular. I'd like to share a summary with you, since your are the ones fit to implement them or not. (Comments in parentheses are purely mine). The starting point of the discussion was an unexplained corruption of a Linux ext2 fs partition on a friend's machine. Our common friend (Bernard.Lang@inria.fr) had found that 4 subdirectories in his large persistent web cache were corrupted: their type, size, dates, access rights, attributes, etc, were garbled. Obviously, a directory inode has been filled with random garbage. As I happened to pass by, I helped Bernard kill the processes that had files opened on the mounted drive, so as to fsck it. The corrupted directories were lost. They happily weren't critical data, but still an annoying thing to lose them (who knows, maybe some of the files are now lost pearls of the Internet?). After fsck, Bernard tried to remove the files, but there remained one that garbled meta-data had made into a non-existing block device, that would resist rm -f. On Friday morning (I guess, since Robert wasn't there on Thursday), Bernard asked help from Robert. Robert tried to figure out what went wrong, and soon ended up examining a binary dump of the bad block and reading the kernel source code to understand. He realized that the device had an immutable attribute. He tried to change the attribute with open() and ioctl() (having learnt about the immutable flag and its behavior by reading kernel sources for rm, and grep'ing for the flag in the rest of the kernel; he didn't know about chattr; chattr must do the same, anyway). However, the problem is that to change the attribute, you have to open the file before you can ioctl() on it; but the file didn't exist (a non-existing device!) and thus couldn't be opened successfully. Robert had to hand-remove the immutable flag (I guess, by accessing the relevant block directly). We met afterwards, before lunch (he did all that during that morning at work, including diagnosis and correction of the problem by reading the kernel code; and he didn't know about the existence of lsattr and chattr -- impressive!). Robert told me that in some Unix flavors of old, it was possible to open a file by path with a null access mode (O_NULL ?) granting neither read nor write access, of value -1 (bytewise? or 2-bit-wise?), so that adding 1 to the open mode you get 0 for 0_NULL, 1 for O_RDONLY, 2 for O_RDWR, O_WRONLY=2, and you get a 2-bit capability bitmask for read and write. He argued that it would have been useful to be able to do that in modern Unices. An alternative would be to provide additional system calls to change attributes, as well as for everything that should be done on files without requiring to open them. Indeed, the "open without access rights" is useful not only to modify attributes and do other ioctl's, but also to effect all operations that should be done w/o the ability to open for either read or write (fstat, funlink, ioctl, fchown, fchmod, fsync), and could be used with new syscalls like flink (make a new directory link for file given by descriptor), freadlink (read link from a file descriptor opened with O_NULL), fexec (execute the binary that we checked), etc. open(path,O_NULL) allows you to do all these things _atomically_, without all those nasty race conditions that happen all the time in absence of it, when you have to check a file, then use the data from a which ever same-named file happens to be there between two system calls, without any kernel-enforced way to ensure the file will be the same at that time. Of course, you'll want to be able to fcntl(fd,F_SETFL,O_RDWR) or something equivalent, to upgrade your access mode on a file you opened with O_NULL. It looked like the linux kernel did immutability checking at wrong places: not only you can't modify attributes from a file you cannot open, but you cannot do it for symlinks, either (actually, the situation of symlinks with respect to attributes and fstat, etc, is very peculiar; maybe there should be in open an O_DONTFOLLOWLINK option when you open in mode O_NULL, so that you can do the equivalent of lstat on a filedescriptor; again such thing could be a life-saver when dealing with files atomically in presence of symlinks). I remember having been very disappointed not being able to chattr +i symlinks from /etc to /trans/etc or /proc so as to ensure that given "files" would always point to the zone where I store machine/network-dependent configuration files that I generate automatically from templates when I move from a machine to another, or when I plug my laptop to another network. The discussion thus evolved into issues of lookup tables in kernel space. Robert had a case long ago when he optimized tar on a Unix system of old to use one of those "cheap" tape hardware on which you had little control. The tape had two speeds, something like 25ft/s and 100ft/s (I don't remember for sure what speed he said), but tar didn't work well at 100ft/s. Indeed, at 100ft/s, the tape drive wouldn't stop right away, and had to rewind back to where it stopped (which was done transparently to the user). So you had to keep your buffers full to avoid the slowness and unreliability of rewinding too often. After optimizing tar quite a bit, Robert faced the problem of the performance bottleneck being open(), due to the kernel doing lots of namei lookups (all the more with poor cacheing, at the time), all the more in absence of fchdir() (which used to make open() even more of a problem in cp and mv). As a feature related to open(path,O_NULL) and avoiding race conditions, I remarked about directory backup that another useful kernel feature would be locking on opened directories, so as to do atomic modification/backup/foo of directories with kernel support rather than using conventional advisory lock files. About namei() and large directories, Robert suggested that news servers, and other large databases (terminfo, that web cache, and many more come to my mind), should use special database libraries with a well-defined API (possibly inspired by the filesystem interface), rather than abuse the filesystem API as they do; he didn't think that attempts to adapt filesystem code specifically to every such use would be useful (plus it's doomed to induce the hell of putting more and more complicated filesystem code in the kernel for every single application). Another problem was the ability to change the mount status of a partition from read-write to read-only or to unmounted, which is sometimes done automatically and unnicely in presence of severe corruption, and that should be doable by root in a nice way even in absence of severe fs corruption (small corruption; removable media; service operation; whatever). The first question was: what to do about processes that had open file descriptors on the partition with too much access? Would they get spurious errors? Would they be stopped? Would they be stopped, or blocked, or killed, either immediately or at first file access with obsolete rights on partition? Robert favored the stop at once option. In any case, handling such things at fd use requires marking fds somehow, so that operations will not go awry while the partition is not available, and will resume nicely when it is again available with enough access; while handling things at once requires that the kernel atomically (or otherwise consistently) determines what are processes using the partition so as to kill them, which in current implementation requires linear lookup and search over the whole process table to see if they use a fd on said partition. The latter possibility raised a second question: a linear lookup of the whole process lookup table may be quite long for an atomic operation, so the question is whether it should be allowed to begin with (the original KISS design of the Unix kernel would answer: "no!"), and if so, is the kernel interruptible by "real-time" processes while doing such operations; indeed, in a truly real-time OS, response time is most important and shouldn't be degraded by long system operations. This is an essential question for kernel design. One "solution" proposed in the past has been micro-kernel design (I explain in http://www.tunes.org/papers/Glossary/index.html#microkernel why micro-kernel isn't really the solution to anything). The real solution is to have a mostly-interruptible kernel with as fine-grained locking as needed, which is useful anyway in a multi-processor implementation. (Real-time support also implies adapted scheduling and priority management, but this is an otherwise well-known topic well studied in computer science). Finally, we discussed about saving _and restoring_ the state of a process, another hack that he did once to preserve a long-winded calculation from the service shutdown of a big unix computer. Saving was a "simple" matter of dumping core. The only right way to restore things atomically on computers without user-accessible return-from-interrupt was use sigreturn, simulating the correct argument stack from saved state. Of course, even if you manage such hack, there remains the problem of saving the underlying system state of the process: file descriptors, sharing of resources, etc. There is no way to consistently restore these without system support (so that people who want to do it have to go through specialized infrastructure libraries that keep enough information to (attempt) restore process connections at restart -- some people @lip6.fr have done process migration this way); it would be nice that when the system dumps core, it also saved enough description about filedescriptors so that restoring connections may be attempted by a core handler (maybe the system could even dump cores in the format of binaries dynamically linked to a core-restoring library). We then discussed about saving and restoring more than a single process: saving the whole state of the machine so as to restore it later (which some laptops do in a combination of hardware and firmware). Not only must core memory be saved (as a useful optimization, buffers should be flushed, and may or not be dropped from the core dump), but as a problem similar to the one above, the underlying system state (i.e. I/O device state) must be saved, too, which requires save&restore support from every device driver (by saving a mirror device state in software when it isn't readable from hardware), as well as tracking dependencies between device initializations so as to do things correctly. Of course, as with processes above, the restoring code should do consistency checking to ensure that restored state is coherent with disk state, device state, etc; in case some inconsistency is detected, handlers should be called to resolve it by modifying core state; and in case the inconsistency cannot be resolved, the state restoration should fail. As a side effect to a successful save&restore feature, not only would it be possible to do on every computer in software what is done only on some laptops in hardware (and not always satisfactorily, depending on laptops), it would also be possible to have a "fast start mode", whereby you'd save the machine in a state ready-to-go, so as to achieve the fastest-booting OS in the west. We discussed a lot of topics, but the above is all I remember that is relevant to the unixish kernels. I am sorry to bug you with such a long e-mail. I have not enough time, interest or knowledge to modify the Linux kernel myself for all these features (all the less time, interest or knowledge to modify every existing free unix kernel); actually I'm involved in implementation efforts for another completely different OS already (see Tunes in my .sig). Nevertheless, I see immediate benefit for everyone in the kernel features I proposed. I hope that some hackers reading me see benefit in them, too, and choose to implement some of them in their favorite Unix kernel. Maybe someone could convince Robert to hack Linux or another kernel. By posting on all free unix kernel mailing-list I know, I intend to put free unices in competition as to which will implement these features first. I hope this won't launch a cross-mailing-list flamewar. Please watch what you reply to what recipients. I am not subscribed to any of the unix kernel lists I'm posting to, but I'm interested in discussion that this mail may inspire. I hope that Linux/BSD kernel hackers will implement the suggested improvements. If not, I'm interested to hear about reasons why you kernel hackers think it shouldn't be done, or about the features having already been implemented in such free Unix flavor. NB: This mail is my own initiative. I didn't ask Robert E. for consent. I'm doing my best effort at representing what happened and what resulted from the discussion with Robert Ehrlich. Any mistake, any wrong guess, any misrepresentation, any gross error, any plain stupidity, is purely my own fault. All good ideas are Robert's. Regards, [ "Faré" | VN: Уng-Vû Bân | Join the TUNES project! http://www.tunes.org/ ] [ FR: François-René Rideau | TUNES is a Useful, Nevertheless Expedient System ] [ Reflection&Cybernethics | Project for a Free Reflective Computing System ] Those who do not understand LISP are condemned to reinvent it, poorly. -- Faré, without apologies to Henry Spencer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 5:39:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orchard.arlington.ma.us (orchard.epilogue.com [128.224.138.4]) by hub.freebsd.org (Postfix) with ESMTP id 76F3215121 for ; Sun, 27 Jun 1999 05:39:26 -0700 (PDT) (envelope-from sommerfeld@orchard.arlington.ma.us) Received: from orchard.arlington.ma.us (localhost [[UNIX: localhost]]) by orchard.arlington.ma.us (8.8.8/1.34) with ESMTP id MAA22238; Sun, 27 Jun 1999 12:39:07 GMT Message-Id: <199906271239.MAA22238@orchard.arlington.ma.us> To: Francois-Rene Rideau Cc: Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: Message from Francois-Rene Rideau of "Sun, 27 Jun 1999 11:45:26 +0200." <19990627114526.A10755@ZhengHe.augustin.thierry> Date: Sun, 27 Jun 1999 08:39:06 -0400 From: Bill Sommerfeld Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > .. but there remained one that garbled meta-data had made into a > non-existing block device, that would resist rm -f. He realized > that the device had an immutable attribute. However, the problem is > that to change the attribute, you have to open the file before you > can ioctl() on it; BSD4.4 and its progeny deal with this by providing both chflags() and fchflags() system calls; as you don't need to be able to do an open() call to use chflags(), you can just fix the immutable attribute once you have the system running at an appropriate securelevel. - Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 6:29:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lrcpc22.epfl.ch (lrcpc22.epfl.ch [128.178.156.58]) by hub.freebsd.org (Postfix) with ESMTP id 8F5881529F for ; Sun, 27 Jun 1999 06:29:32 -0700 (PDT) (envelope-from almesber@lrc.di.epfl.ch) Received: (from almesber@localhost) by lrcpc22.epfl.ch (8.8.7/ICA.Lc1) id OAA04427; Sun, 27 Jun 1999 14:46:13 +0200 Date: Sun, 27 Jun 1999 14:46:13 +0200 From: Werner Almesberger To: Francois-Rene Rideau Cc: Linux Kernel , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel Subject: Re: Improving the Unix API Message-ID: <19990627144613.B4004@lrc.di.epfl.ch> References: <19990627114526.A10755@ZhengHe.augustin.thierry> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990627114526.A10755@ZhengHe.augustin.thierry>; from Francois-Rene Rideau on Sun, Jun 27, 1999 at 11:45:26AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Francois-Rene Rideau wrote: > Robert told me that in some Unix flavors of old, > it was possible to open a file by path with a null access mode (O_NULL ?) E.g. Linux. Very undocumented, but has been around for ages ('92 or such). The main purpose is to keep the floppy drive from spinning up to check for a media change when you open it to access parameters and such. E.g. fdformat, setfdprm, and LILO use this. (NB: some versions of strace print the flags argument in this case as "0x4", although it's really 3.) - Werner -- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 7:58: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id BA19814E7E for ; Sun, 27 Jun 1999 07:58:01 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id OAA63487; Sun, 27 Jun 1999 14:56:32 GMT Message-ID: <37763B00.15894ADD@tdx.co.uk> Date: Sun, 27 Jun 1999 15:53:52 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Constantine Shkolny , "hackers@FreeBSD.ORG" Subject: Re: All this and documentation too? (was: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c))) References: <01BEBFCB.F95F6F00.stan@osgroup.com> <19990627093124.N427@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > I've come to understanding that lack of documentation is probably one of > > the factors that keep the system healthy, because it keeps the unskilled > > people away. I don't know whether it's true but I read in books that > > reading code is one of the methods to learn programming. Since FreeBSD > > does ship with source code, docs are not necessary. NT ships with poorly > > written docs instead, and, that is what kills it all the time, despite of > > its perfect design that I really like. People write NT drivers without > > full understanding what is going on, so they destabilize the system. > > I can't agree with this theory. Lack of documentation just moves the > degree of skill needed to, for example, write device drivers. > Document less well and your average device driver writer will write a > worse driver, with or without source code access. Source code access > helps too, of course. Coming from someone who's struggled to write a device driver, and then had to move the driver from 2.X, through to 3.X to 4.X (it's currently languishing somewhere along the line of 3.X) - I would wholely agree with Greg. Documentation is _very important_ even more so in a rapidly moving system... Having access to the source code is one thing, but 'c' was not designed for documentation, it was designed to program in... Looking at the current array of drivers in -current you get the idea everyones done it 'slightly differently', and no one comments their code enough to make it 'self documenting', nor has anyone singled out any of the vast array of drivers and said "this is a good example if your writing ISA drivers", or "this is a good one to go from if your writing PCI". Just my annoyed $0.02's worth! :) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 9:19:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 0770F14D8E for ; Sun, 27 Jun 1999 09:19:20 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id MAA28069; Sun, 27 Jun 1999 12:19:03 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id MAA02595; Sun, 27 Jun 1999 12:19:02 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 12:19:02 -0400 (EDT) From: Alexander Viro To: Bill Sommerfeld Cc: Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906271239.MAA22238@orchard.arlington.ma.us> 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, 27 Jun 1999, Bill Sommerfeld wrote: > > .. but there remained one that garbled meta-data had made into a > > non-existing block device, that would resist rm -f. He realized > > that the device had an immutable attribute. However, the problem is > > that to change the attribute, you have to open the file before you > > can ioctl() on it; > > BSD4.4 and its progeny deal with this by providing both chflags() and > fchflags() system calls; as you don't need to be able to do an open() > call to use chflags(), you can just fix the immutable attribute once > you have the system running at an appropriate securelevel. Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More or less in the same direction, not exactly the same - 4.4 chflags() works fine for UFS and leaves other filesystems to map what they can into the UFS set. Which is bogus - immutable is not a UFS attribute, it's VFS one. I have a patch (still pre-alpha) and I'll post it tomorrow or on Wednesday when I'll be back from CA. As for the opening with no permissions - well, it would make *big* sense if we could narrow down the API and move chown(), chmod(), etc. into libc leaving f-variants in the kernel. Binary compatibility... Extreme variant might include {set,get}sockopt extended to files and doing both *stat and *ch{mod,own,flags} via that. Out of curiosity - did somebody on *BSD side play with that? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 9:29:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orchard.arlington.ma.us (orchard.epilogue.com [128.224.138.4]) by hub.freebsd.org (Postfix) with ESMTP id 7A26214D8E for ; Sun, 27 Jun 1999 09:29:05 -0700 (PDT) (envelope-from sommerfeld@orchard.arlington.ma.us) Received: from orchard.arlington.ma.us (localhost [[UNIX: localhost]]) by orchard.arlington.ma.us (8.8.8/1.34) with ESMTP id QAA22753; Sun, 27 Jun 1999 16:28:59 GMT Message-Id: <199906271628.QAA22753@orchard.arlington.ma.us> To: Alexander Viro Cc: Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: Message from Alexander Viro of "Sun, 27 Jun 1999 12:19:02 EDT." Date: Sun, 27 Jun 1999 12:28:58 -0400 From: Bill Sommerfeld Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More > or less in the same direction, not exactly the same - 4.4 chflags() works > fine for UFS and leaves other filesystems to map what they can into the > UFS set. > Which is bogus - immutable is not a UFS attribute, it's VFS one. Well, I'd argue that Berkeley defined a bunch of VFS attributes, and then implemented them natively in UFS and LFS; other non-native filesystems have to map their concepts of other file attributes (e.g., dates, permissions, etc.,) into the native VFS concepts. - Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 9:59:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [132.206.78.3]) by hub.freebsd.org (Postfix) with ESMTP id 553D214C23 for ; Sun, 27 Jun 1999 09:59:12 -0700 (PDT) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id MAA22092; Sun, 27 Jun 1999 12:58:05 -0400 (EDT) Date: Sun, 27 Jun 1999 12:58:05 -0400 (EDT) From: der Mouse Message-Id: <199906271658.MAA22092@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > He realized that the device had an immutable attribute. > He tried to change the attribute with open() and ioctl() As I think someone already mentioned, BSD has chflags(), which takes a pathname. > Robert had to hand-remove the immutable flag > (I guess, by accessing the relevant block directly). (clri didn't work?) > Indeed, the "open without access rights" > is useful not only to modify attributes and do other ioctl's, > but also to effect all operations that should be done w/o the ability > to open for either read or write > (fstat, funlink, ioctl, fchown, fchmod, fsync), funlink makes no sense, unless the fd it takes is the fd of a directory and you pass in the name of the entry to be removed - which I imagine is not what most people will think when they think of an fd-based variant of unlink. unlink() operates on names, not files, after all. I've often wanted open-with-no-access in conjunction with fchdir(). This is because you need only execute access to set your cwd to a directory, but there's no way to get an fd on a mode-111 directory. > and could be used with new syscalls like > flink (make a new directory link for file given by descriptor), > freadlink (read link from a file descriptor opened with O_NULL), > fexec (execute the binary that we checked), etc. freadlink() implies that open() with O_NULL has the peculiar property that, unlike all other open()s, it doesn't follow terminal symlinks. While I think there are ways symlinks could be improved, I don't think this is one of them. I can't see any use for opening a symlink except use of write() to atomically make the link point somewhere different, and I'd prefer to do that by making symlink() do that when the link already exists and some appropriate condition is met. > Of course, you'll want to be able to fcntl(fd,F_SETFL,O_RDWR) > or something equivalent, to upgrade your access mode > on a file you opened with O_NULL. The security weenie in me is _really_ unsure that the ability to increase the access modes on an open fd is a good idea. > About namei() and large directories, Robert suggested > that news servers, and other large databases > (terminfo, that web cache, and many more come to my mind), > should use special database libraries with a well-defined API > (possibly inspired by the filesystem interface), > rather than abuse the filesystem API as they do; At least one news system does this now, I think - instead of keeping each post in a separate file, it uses one huge file and does its own space allocation out of it. > Another problem was the ability to change the mount status of a partition > from read-write to read-only or to unmounted, See NetBSD (and presumably other BSD) "mount -o update,rdonly" and/or "umount -f". (Last I tried, the latter didn't work as it should, but that's a matter of fixing bugs rather than introducing new features.) > Finally, we discussed about saving _and restoring_ the state of a process, > another hack that he did once to preserve a long-winded calculation > from the service shutdown of a big unix computer. I did this once, long long ago, under (I think) 4.3. I found that I couldn't just dump core, though I forget why. As for the open file descriptor question, I punted - I made the relevant call fail unless the process had no fds open. > By posting on all free unix kernel mailing-list I know, > I intend to put free unices in competition as to which > will implement these features first. Reasonable as this sounds, I think the last thing we need is yet another ground on which one free-unix can be doing the "nana nana boo boo" taunt at another. Once upon a time I would have hoped the people involved were sufficiently mature to avoid doing that, or responding when on the receiving end of it - and many of them *are*, but I've been involved in this scene too long to retain any real hope that *all* of them are. [And replying to another message...] > 4.4 chflags() works fine for UFS and leaves other filesystems to map > what they can into the UFS set. Which is bogus - immutable is not a > UFS attribute, it's VFS one. Perhaps, but it's still something that the underlying filesystem has to support. Just because the API bit definitions happen to match what FFS filesystems save on disk doesn't mean it's inherently an FFS thing. > As for the opening with no permissions - well, it would make *big* > sense if we could narrow down the API and move chown(), chmod(), etc. > into libc leaving f-variants in the kernel. I really don't like that. The reasons why are (1) this means you have to have an fd free to do them; (2) it triples the number of user/kernel crossings involved. > Extreme variant might include {set,get}sockopt extended to files and > doing both *stat and *ch{mod,own,flags} via that. If done, I think the name should be changed. They are ?etSOCKopt, after all. I'm not fond of this, though; it amounts to returning to using ioctl() for the tasks - albeit with a slightly different name. der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10: 2:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id F367D14C23 for ; Sun, 27 Jun 1999 10:02:41 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA28612; Sun, 27 Jun 1999 13:02:39 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA02680; Sun, 27 Jun 1999 13:02:39 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 13:02:39 -0400 (EDT) From: Alexander Viro To: Bill Sommerfeld Cc: Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906271628.QAA22753@orchard.arlington.ma.us> 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, 27 Jun 1999, Bill Sommerfeld wrote: > > Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More > > or less in the same direction, not exactly the same - 4.4 chflags() works > > fine for UFS and leaves other filesystems to map what they can into the > > UFS set. > > > Which is bogus - immutable is not a UFS attribute, it's VFS one. > > Well, I'd argue that Berkeley defined a bunch of VFS attributes, and > then implemented them natively in UFS and LFS; other non-native > filesystems have to map their concepts of other file attributes (e.g., > dates, permissions, etc.,) into the native VFS concepts. Right. Except that UFS has not only generic attibutes. For example, you have UF_NODUMP and SF_ARCHIVED. The *only* place in the /sys you mention the former is sys/stat.h (BTW, you don't even map it on EXT2_NODUMP_FL). The latter is mentioned only in the msdosfs/msdosfs_vnops.c. Hardly a VFS flag, right? Proposed API on the Linux side being int chflags(name, level, oldp, newp); where level is FL_VFS for generic attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw flags - corresponding filesystem is free to interpret the thing as it likes and should set the generic attributes in the right way. If you are trying to talk with the wrong filesystem (i.e. the level is not FL_VFS and not FL_) you are getting an error. If oldp is not NULL *oldp contains the attributes to set. if newp is not NULL *newp will contain the attributes *after* operation. IMO it's cleaner than pushing all attributes into the single bitmap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:15: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0977C14C23 for ; Sun, 27 Jun 1999 10:15:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA28770; Sun, 27 Jun 1999 18:17:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 27 Jun 1999 18:17:34 +0100 (BST) From: Doug Rabson To: Alexander Viro Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API 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 Sun, 27 Jun 1999, Alexander Viro wrote: > > > On Sun, 27 Jun 1999, Bill Sommerfeld wrote: > > > > Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More > > > or less in the same direction, not exactly the same - 4.4 chflags() works > > > fine for UFS and leaves other filesystems to map what they can into the > > > UFS set. > > > > > Which is bogus - immutable is not a UFS attribute, it's VFS one. > > > > Well, I'd argue that Berkeley defined a bunch of VFS attributes, and > > then implemented them natively in UFS and LFS; other non-native > > filesystems have to map their concepts of other file attributes (e.g., > > dates, permissions, etc.,) into the native VFS concepts. > > Right. Except that UFS has not only generic attibutes. For example, > you have UF_NODUMP and SF_ARCHIVED. The *only* place in the /sys you > mention the former is sys/stat.h (BTW, you don't even map it on > EXT2_NODUMP_FL). The latter is mentioned only in the msdosfs/msdosfs_vnops.c. > Hardly a VFS flag, right? > Proposed API on the Linux side being > int chflags(name, level, oldp, newp); where level is FL_VFS for generic > attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw > flags - corresponding filesystem is free to interpret the thing as it > likes and should set the generic attributes in the right way. If you are > trying to talk with the wrong filesystem (i.e. the level is not FL_VFS and > not FL_) you are getting an error. If > oldp is not NULL *oldp contains the attributes to set. if newp is not > NULL *newp will contain the attributes *after* operation. IMO it's cleaner > than pushing all attributes into the single bitmap. This looks viable as long as you don't use small integers to represent FL_UFS etc. Having a single header defining constants for all filesystems just doesn't scale at all. You still want a clearly defined set of FS independant flags so that the application doesn't need to care what filesystem it is sitting on. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:29:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orchard.arlington.ma.us (orchard.epilogue.com [128.224.138.4]) by hub.freebsd.org (Postfix) with ESMTP id D34B414E7F for ; Sun, 27 Jun 1999 10:29:18 -0700 (PDT) (envelope-from sommerfeld@orchard.arlington.ma.us) Received: from orchard.arlington.ma.us (localhost [[UNIX: localhost]]) by orchard.arlington.ma.us (8.8.8/1.34) with ESMTP id RAA23192; Sun, 27 Jun 1999 17:29:13 GMT Message-Id: <199906271729.RAA23192@orchard.arlington.ma.us> To: Alexander Viro Cc: Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: Message from Alexander Viro of "Sun, 27 Jun 1999 13:02:39 EDT." Date: Sun, 27 Jun 1999 13:29:12 -0400 From: Bill Sommerfeld Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right. Except that UFS has not only generic attibutes. For example, > you have UF_NODUMP and SF_ARCHIVED. The *only* place in the /sys you > mention the former is sys/stat.h Well, right, because backup/restore aren't part of the kernel... > (BTW, you don't even map it on EXT2_NODUMP_FL). This was presumably an oversight; I've reported it as a bug. - Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:36:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 393631502E for ; Sun, 27 Jun 1999 10:36:29 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA29133; Sun, 27 Jun 1999 13:36:27 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA02749; Sun, 27 Jun 1999 13:36:26 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 13:36:26 -0400 (EDT) From: Alexander Viro To: Doug Rabson Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API 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 Sun, 27 Jun 1999, Doug Rabson wrote: > This looks viable as long as you don't use small integers to represent > FL_UFS etc. Having a single header defining constants for all filesystems Erm... sizeof(int)==4. I doubt that you will need more. > just doesn't scale at all. Sure. If you don't need fs-specific stuff - and there you go. If you need some particular fs - and > You still want a clearly defined set of FS independant flags so that the > application doesn't need to care what filesystem it is sitting on. And that's exactly the reason for FL_VFS vs. FL_FOOFS separation - some applications should be able to talk with the filesystem in the filesystem's terms *and* be sure that they will not mess with another fs; the rest shouldn't care for fs differences at all (aside of "did the sucker set the bits I wanted?" that you already have for SUID/SGID/sticky). I don't think that porting it to 4.4 will be difficult - all you need is a way to tell VOP_SETATTR what level are you talking to (most likely the same way as on the our side - add a field to the structure and let the methods scratch their heads). I'm going to do the Linux variant and see how it will work. If somebody wants to do it with *BSD - fine, it shouldn't be a problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:41:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92]) by hub.freebsd.org (Postfix) with ESMTP id 5FBA9150C6 for ; Sun, 27 Jun 1999 10:40:35 -0700 (PDT) (envelope-from jsp@pendry.com) Received: from [195.99.51.200] (helo=pendry.com) by carbon.btinternet.com with esmtp (Exim 2.05 #1) id 10yIua-0004Uj-00; Sun, 27 Jun 1999 18:40:13 +0100 Message-ID: <377661C6.89FB7F5@pendry.com> Date: Sun, 27 Jun 1999 18:39:18 +0100 From: Jan-Simon Pendry X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.3.2 i586) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Viro Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Viro wrote: > Proposed API on the Linux side being > int chflags(name, level, oldp, newp); where level is FL_VFS for generic > attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw > flags - corresponding filesystem is free to interpret the thing as it > likes and should set the generic attributes in the right way. if linux introduces a different API (ie not just an extension of the existing bsd API) then please do *not* call it "chflags". it took years just to get over the bsd vs. svr4 gettimeofday() fiasco. btw, what's the proposed API for getting the current attribute set? jan-simon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id A9C6A14BD5 for ; Sun, 27 Jun 1999 10:47:21 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-70-218.atl.bellsouth.net [209.214.70.218]) by mail2.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id NAA15509 for ; Sun, 27 Jun 1999 13:47:14 -0400 (EDT) Received: (from wghicks@localhost) by wghicks.bellsouth.net (8.9.3/8.9.2) id NAA49144 for hackers@freebsd.org; Sun, 27 Jun 1999 13:50:35 -0400 (EDT) (envelope-from wghicks) Date: Sun, 27 Jun 1999 13:50:35 -0400 (EDT) From: W Gerald Hicks Message-Id: <199906271750.NAA49144@bellsouth.net> To: hackers@freebsd.org Reply-To: wghicks@bellsouth.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:50: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 80F2714EA6 for ; Sun, 27 Jun 1999 10:50:07 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA29326; Sun, 27 Jun 1999 13:50:02 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA02781; Sun, 27 Jun 1999 13:50:02 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 13:50:02 -0400 (EDT) From: Alexander Viro To: der Mouse Cc: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906271658.MAA22092@Twig.Rodents.Montreal.QC.CA> 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, 27 Jun 1999, der Mouse wrote: > > Another problem was the ability to change the mount status of a partition > > from read-write to read-only or to unmounted, > > See NetBSD (and presumably other BSD) "mount -o update,rdonly" and/or > "umount -f". (Last I tried, the latter didn't work as it should, but > that's a matter of fixing bugs rather than introducing new features.) mount -o remount,ro on Linux. What was the problem? Indeed you can't do it if you have files opened for write there (or pending removal of files from unlinks), but that limitation is reasonable, IMHO. > > As for the opening with no permissions - well, it would make *big* > > sense if we could narrow down the API and move chown(), chmod(), etc. > > into libc leaving f-variants in the kernel. > > I really don't like that. The reasons why are (1) this means you have > to have an fd free to do them; (2) it triples the number of user/kernel > crossings involved. The former is not too terrible, but the latter... Yup. > > Extreme variant might include {set,get}sockopt extended to files and > > doing both *stat and *ch{mod,own,flags} via that. > > If done, I think the name should be changed. They are ?etSOCKopt, > after all. I'm not fond of this, though; it amounts to returning to > using ioctl() for the tasks - albeit with a slightly different name. The *only* way to make it reasonable would be to have a hierarchical namespace for the options. Otherwise you are just getting the ioctl() mess, and that's the last thing I'ld like to see. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 10:51:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id ACEB015040 for ; Sun, 27 Jun 1999 10:51:50 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA29411; Sun, 27 Jun 1999 13:51:48 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id NAA02792; Sun, 27 Jun 1999 13:51:47 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 13:51:47 -0400 (EDT) From: Alexander Viro To: Jan-Simon Pendry Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API In-Reply-To: <377661C6.89FB7F5@pendry.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 Sun, 27 Jun 1999, Jan-Simon Pendry wrote: > Alexander Viro wrote: > > Proposed API on the Linux side being > > int chflags(name, level, oldp, newp); where level is FL_VFS for generic > > attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw > > flags - corresponding filesystem is free to interpret the thing as it > > likes and should set the generic attributes in the right way. > > if linux introduces a different API (ie not just an extension of > the existing bsd API) then please do *not* call it "chflags". ;-/ Yes, it makes sense. > it took years just to get over the bsd vs. svr4 gettimeofday() > fiasco. btw, what's the proposed API for getting the current > attribute set? oldp == NULL ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 11:10: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 7F12815091 for ; Sun, 27 Jun 1999 11:10:01 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id E98C55AC6; Sun, 27 Jun 1999 20:10:00 +0200 (MET DST) Message-ID: <19990627201000.A29472@gvr.org> Date: Sun, 27 Jun 1999 20:10:00 +0200 From: Guido van Rooij To: FreeBSD-hackers Subject: ipfilter volunteer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to volunteer to maintain ipfilter. I already told several people at the usenix conference, but as I have seen others taking interest as well, it seems right to at least spread it more publicly. I am still waiting for a machine I won at the conference to start on it though so it might take some weeks before seeing some action. Current plans are to import a more recent version of ipfilter followed by having a look at features implemented by ipfw that are currently missing in ipfilter. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 11:37:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id D1F7A14E9B; Sun, 27 Jun 1999 11:37:26 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.207]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3B58; Sun, 27 Jun 1999 20:37:25 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA22906; Sun, 27 Jun 1999 20:04:34 +0200 (CEST) (envelope-from asmodai) Date: Sun, 27 Jun 1999 20:04:34 +0200 From: Jeroen Ruigrok/Asmodai To: Francis Jordan Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: building thread-safe Xlibs Message-ID: <19990627200434.A22859@daemon.ninth-circle.org> References: <19990626003458.26580.qmail@ww185.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990626003458.26580.qmail@ww185.netaddress.usa.net>; from Francis Jordan on Sat, Jun 26, 1999 at 01:34:58AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Francis Jordan (frankrj@netscape.net) [990626 06:03]: > xc/include/Xos_r.h > > which contains definitions of same (basically, pwd.h wrappers) for various > platforms, but not FreeBSD (I guess at the time FreeBSD didn't have threads). > Unfortunately, the wrappers for other platforms are no good, as FreeBSD's pwd > structures are different from everything else. Hmmm, one thing that's still missing from at least the POSIX threads is pthread_cancel. Plus that there's no such thing as a libpthread. Thread support (POSIX) has a long way to come in FreeBSD, but I lack the cloo-by-four to do it. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at it's best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 12: 4: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from idiom.com (idiom.com [209.157.64.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B2F914DAA for ; Sun, 27 Jun 1999 12:03:57 -0700 (PDT) (envelope-from greywolf@starwolf.com) Received: from starwolf.com (root@starwolf.starwolf.com [209.157.73.91]) by idiom.com (8.9.3/8.9.3) with ESMTP id MAA32167; Sun, 27 Jun 1999 12:02:07 -0700 (PDT) Received: from defender.starwolf.com (defender.starwolf.com [10.11.11.2]) by starwolf.com (8.8.8/8.8.8) with ESMTP id LAA29632; Sun, 27 Jun 1999 11:58:53 -0700 (PDT) Received: from localhost (localhost.starwolf.com [127.0.0.1]) by defender.starwolf.com (8.8.8/8.8.8) with SMTP id LAA12726; Sun, 27 Jun 1999 11:51:21 -0700 (PDT) Date: Sun, 27 Jun 1999 11:51:20 -0700 (PDT) From: Gandhi woulda smacked you To: der Mouse Cc: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906271658.MAA22092@Twig.Rodents.Montreal.QC.CA> 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, 27 Jun 1999, der Mouse wrote: # > Robert had to hand-remove the immutable flag # > (I guess, by accessing the relevant block directly). # # (clri didn't work?) Obviously the guy thinks along the lines that you need a file descriptor to do things to files. That, or he didn't want to do an fsck on the partition once he was done. # # > Indeed, the "open without access rights" # > is useful not only to modify attributes and do other ioctl's, # > but also to effect all operations that should be done w/o the ability # > to open for either read or write # > (fstat, funlink, ioctl, fchown, fchmod, fsync), You mean like stat, unlink, chown, chmod? Why in the world are you going to fsync a file with which you haven't done anything? The only one up there that makes sense is ioctl. # # funlink makes no sense, unless the fd it takes is the fd of a directory # and you pass in the name of the entry to be removed - which I imagine # is not what most people will think when they think of an fd-based # variant of unlink. unlink() operates on names, not files, after all. I've wanted an fclri(fd) which would clear the dev/ino attached to the fd, but there's no clean way to do that as the system would then have to search for all instances of that ino on that dev, and that's something the system has no business doing. namei (name-to-inode) is necessary, and also easier than doing the reverse since name-to-inode mapping is unique (because pathnames are unique) while inode-to-name mapping is not (because there are hard links, i.e. multiple names can refer to the same inode). [read that carefully, it looks contradictory but isn't.] # I've often wanted open-with-no-access in conjunction with fchdir(). # This is because you need only execute access to set your cwd to a # directory, but there's no way to get an fd on a mode-111 directory. Playing the Daemon's advocate, here... What use is a descriptor into a directory you can't read? What's the point of fchdir(dd->fd) if you can't figure out where you're going from there? You may as well use chdir(dir). # While I think there are ways symlinks could be improved, I don't think # this is one of them. I can't see any use for opening a symlink except # use of write() to atomically make the link point somewhere different, # and I'd prefer to do that by making symlink() do that when the link # already exists and some appropriate condition is met. That's a dicey proposition. We already have quite a few "appropriate condition" cases, and I think we want to avoid special-casing a whole slough of conditions. # > Of course, you'll want to be able to fcntl(fd,F_SETFL,O_RDWR) # > or something equivalent, to upgrade your access mode # > on a file you opened with O_NULL. # # The security weenie in me is _really_ unsure that the ability to # increase the access modes on an open fd is a good idea. Nah. fd's are inevitably associated with vnodes (which don't get freed until the last close()); if the vnode doesn't map out to the appropriate permissions, the fcntl() would fail. # > About namei() and large directories, Robert suggested # > that news servers, and other large databases # > (terminfo, that web cache, and many more come to my mind), # > should use special database libraries with a well-defined API # > (possibly inspired by the filesystem interface), # > rather than abuse the filesystem API as they do; # # At least one news system does this now, I think - instead of keeping # each post in a separate file, it uses one huge file and does its own # space allocation out of it. Another problem with making filesystems for news was that you had to tune cpg and bpi way down and ipg way up. When fscking the block device was actually possible, it was also faster to fsck the block device on a device full of symlinks (but that's a horse of a different colour, I realise...). Go figure. # > Another problem was the ability to change the mount status of a partition # > from read-write to read-only or to unmounted, # # See NetBSD (and presumably other BSD) "mount -o update,rdonly" and/or # "umount -f". (Last I tried, the latter didn't work as it should, but # that's a matter of fixing bugs rather than introducing new features.) ...really? umount -f always works for me. There's a bug running around, though, at the end of a shutdown which prevents me from umounting /var for some reason (fstat shows nothing). # > Finally, we discussed about saving _and restoring_ the state of a process, # > another hack that he did once to preserve a long-winded calculation # > from the service shutdown of a big unix computer. # # I did this once, long long ago, under (I think) 4.3. I found that I # couldn't just dump core, though I forget why. As for the open file # descriptor question, I punted - I made the relevant call fail unless # the process had no fds open. Yeah, there's just no way to restore fd state from saved state, since that would require locking that particular set of state in core and if you're going to do that, you certainly cannot shut the system down. Your program will need to maintain the state of the fd flags as set by fcntl() and the disposition of the file descriptors (read,write,both) by logging them as you do them; the position information is about the only parameter you will be saving at the time of the suspension. You can't just dump core probably because of all the signal overhead caused by dumping core will be saved in the core file. You need to effectively generate a state file from whence your calculations can resume. Someone wrote an undump utility, though, which seemed to branch around the fault that caused the core dump, so go figure. # > 4.4 chflags() works fine for UFS and leaves other filesystems to map # > what they can into the UFS set. Which is bogus - immutable is not a # > UFS attribute, it's VFS one. Well, no and yes. ("Go not to the elves for council...") Yes, it's a VFSATTR. No, other filesystem do not map into the UFS set. They map into the VFS set which is rather a superset of all possible filesystem attributes. If the underlying filesystem type supports something in the VFS, it gets set. If it doesn't, it gets ignored. Likewise for something for which VFS does not account in the underlying filesystem (in which case it's time to take another look at the VFS structure, but I suspect we have some room left). # > As for the opening with no permissions - well, it would make *big* # > sense if we could narrow down the API and move chown(), chmod(), etc. # > into libc leaving f-variants in the kernel. # # I really don't like that. The reasons why are (1) this means you have # to have an fd free to do them; (2) it triples the number of user/kernel # crossings involved. Ditto that. That is, in principle, the largest part of the mikrokernel gestalt that really bugs me (the message passing and interpreting seems harmless enough except for the overhead in contexts that it generates). Narrowing the API is not a good thing to do for its own sake. The moves really have to make sense. Stuff that does direct operations on system structures is best left in the kernel and, last I looked, a vnode (fh, vp, whatever) is a system structure which, while it can be transported out to userland for perusal (I think...), has no value in being mutated in userland and passed back in to the kernel for approval on the changes. # > Extreme variant might include {set,get}sockopt extended to files and # > doing both *stat and *ch{mod,own,flags} via that. # # If done, I think the name should be changed. They are ?etSOCKopt, # after all. I'm not fond of this, though; it amounts to returning to # using ioctl() for the tasks - albeit with a slightly different name. {set,get}fopt? I don't know. What are you saving besides kernel entry points? It's certainly not nicer to program in (functions in userland add call overhead, and macros don't show up in debuggers, usually). "{,f}chmod(path, mode);" certainly codes easier than "setfopt({path,fd}, SFO_CHMOD|SFO_{PATH,DESC}, mode)". And "getfopt(path, SFO_NOFOLLOW|SFO_PATH, sp);" vs "lstat(sp);"? Or "setfopt(fd, SFO_DESC|SFO_CHDIR, dir)" vs "fchdir(fd);"??? No, thank you. [I hope it's obvious why the SFO_PATH and SFO_DESC would be necessary in the aforementioned cases.] --*greywolf; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 13:19:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server4.reno.powernet.net (server4.reno.powernet.net [208.226.189.15]) by hub.freebsd.org (Postfix) with ESMTP id 0065114D3B for ; Sun, 27 Jun 1999 13:19:25 -0700 (PDT) (envelope-from trzy@powernet.net) Received: from p3-26.reno.powernet.net (p3-26.reno.powernet.net [208.226.189.146]) by server4.reno.powernet.net (8.9.0/8.8.5) with ESMTP id NAA12509 for ; Sun, 27 Jun 1999 13:19:17 -0700 (PDT) Date: Sun, 27 Jun 1999 13:13:22 -0700 (PDT) From: Bart Trzynadlowski X-Sender: trzy@Brzuszek To: freebsd-hackers@freebsd.org Subject: sio2 often fails to initialize Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I set about to reconfigure my kernel and everything works great except for sio2. My COM3 port is unusual, it has the port address 0x3e8 with an IRQ of 10 so I commented out the relevant sio2 line in my configuration file and replaced it with this: device sio2 at isa? port 0x3e8 tty irq 10 vector siointr It works fine the first time I boot FreeBSD. In fact, it also works if I reboot BUT if I use the modem on cuaa2 (for user PPP) during a session and then reboot sio2 is no longer found. Before I used the GENERIC kernel and /boot/loader set the port, irq, and flags for me. But even if I book my new kernel through /boot/loader (I just boot straight to the kernel with my new one regularly) it doesn't help. I suspect this has something to do with the modem not properly hanging up or the COM port not being de-initialized. But why would it work most of the time with the GENERIC kernel? Thanks, Bart Trzynadlowski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 13:24:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 5B81415176; Sun, 27 Jun 1999 13:24:30 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb59.imasy.or.jp [202.227.24.187]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id FAA11076; Mon, 28 Jun 1999 05:24:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199906272024.FAA11076@tasogare.imasy.or.jp> To: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Cc: phk@FreeBSD.org, imp@harmony.village.org, iwasaki@jp.FreeBSD.org Subject: [Call for review] apmd for FreeBSD X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 28 Jun 1999 05:29:02 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm ready to import apmd into freefall CVS repository. Now manpage (first version) and patch for CURRENT kernel were prepared :) Please review them before my commit. Any comments, suggestions, corrections are very appreciated. The latest (and final?) version of apmd package is available at: apmd(8): http://home.jp.freebsd.org/~iwasaki/apm/19990628/apmd-usr.sbin.tar.gz CURRENT kernel patch (as of 19990628): http://home.jp.freebsd.org/~iwasaki/apm/19990628/apmd-sys-CURRENT.diff.gz No changes were made for previous PAO3 and 3.2-RELEASE kernel patch: http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-sys-PAO3.diff.gz http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-sys-R320.diff.gz Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 15:46:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3E53714D31 for ; Sun, 27 Jun 1999 15:46:54 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40332>; Mon, 28 Jun 1999 08:29:46 +1000 Date: Mon, 28 Jun 1999 08:46:44 +1000 From: Peter Jeremy Subject: Re: Microsoft performance (was: All this and documentation too? In-reply-to: To: hackers@FreeBSD.ORG Message-Id: <99Jun28.082946est.40332@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: >> Programmers need documentation too. > >And they are going to scream like mad if there isn't any. But in the end >they start reading the code anyway, even if there is docu, because they >don't trust anything but their own eyes and brain. > >It's all documented in C anyway. Not really. The C code defines what a piece of code is doing and how it does it. It does not explain why it is doing what it is doing, and most importantly, why it is doing it the way that it is. In many cases, the code might be written the way it is because that's the first thing that popped into the author's head. In this case, it might not matter if the code is substantially re-arranged. In some cases, the code is written in a particular way because the `more obvious' ways of writing the code didn't meet the author's requirements. Whilst it possible that the particular requirement was `this code must be unintelligible', it's more likely to be a subtle interaction with some other subsystem. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 16: 6:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id E8A3514CA1 for ; Sun, 27 Jun 1999 16:06:52 -0700 (PDT) (envelope-from fare@tunes.org) Received: (qmail 7451 invoked from network); 27 Jun 1999 23:06:49 -0000 Received: from d153.paris-131.cybercable.fr (HELO ZhengHe) ([212.198.131.153]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 27 Jun 1999 23:06:49 -0000 Received: from fare by ZhengHe with local (Exim 2.11 #1 (Debian)) id 10yNyh-0001Y6-00; Mon, 28 Jun 1999 01:04:47 +0200 Date: Mon, 28 Jun 1999 01:04:47 +0200 From: Francois-Rene Rideau To: der Mouse Cc: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Message-ID: <19990628010446.A5377@ZhengHe.augustin.thierry> Reply-To: Francois-Rene Rideau References: <199906271658.MAA22092@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i In-Reply-To: <199906271658.MAA22092@Twig.Rodents.Montreal.QC.CA>; from der Mouse on Sun, Jun 27, 1999 at 12:58:05PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 27, 1999 at 12:58:05PM -0400, der Mouse wrote: > As I think someone already mentioned, BSD has chflags(), [...] Yup. >> Robert had to hand-remove the immutable flag >> (I guess, by accessing the relevant block directly). > (clri didn't work?) Never heard about clri (was under Linux). And I dunno what Robert did. I will ask him, if it matters. > funlink makes no sense [...] unlink() operates on names, not files [...] Oops. Indeed. The thinko is purely mine. > I've often wanted open-with-no-access in conjunction with fchdir(). > This is because you need only execute access to set your cwd to a > directory, but there's no way to get an fd on a mode-111 directory. Again and again, open-with-no-access definitely seems to have lots of applications. >> flink (make a new directory link for file given by descriptor), flink() combined with the ability to create an unlinked file in a given filesystem would allow for safe temporaries without race conditions, that could be "published" when ready. >> freadlink (read link from a file descriptor opened with O_NULL), >> fexec (execute the binary that we checked), etc. > freadlink() implies that open() with O_NULL has the peculiar property > that, unlike all other open()s, it doesn't follow terminal symlinks. I suggested that there could be a flag O_DONTFOLLOWLINK in such cases; I'm not fully sure the feature, but it would allow to set flags on symlinks, and other goodies. > While I think there are ways symlinks could be improved, I don't think > this is one of them. I can't see any use for opening a symlink except > use of write() to atomically make the link point somewhere different, > and I'd prefer to do that by making symlink() do that when the link > already exists and some appropriate condition is met. Well, I can imagine opening them to lock them, so as to prevent other people from making them point somewhere else, as well as change some filesystem attributes on the right thing, etc. Again, open() allows locking and prevents race conditions. >> Of course, you'll want to be able to fcntl(fd,F_SETFL,O_RDWR) >> or something equivalent, to upgrade your access mode >> on a file you opened with O_NULL. > The security weenie in me is _really_ unsure that the ability to > increase the access modes on an open fd is a good idea. Well, there could be a flag O_NOINCREASEACCESS to prevent further increasing of access modes (by e.g. children), if you that makes you safer. And of course, increasing access mode is subject to usual permission checking. >> Another problem was the ability to change the mount status of a partition >> from read-write to read-only or to unmounted, > See NetBSD (and presumably other BSD) "mount -o update,rdonly" and/or > "umount -f". (Last I tried, the latter didn't work as it should, but > that's a matter of fixing bugs rather than introducing new features.) If you re-read the original message, the problem is what to do about processes with open file descriptors on the partition: stop them at once? stop them at first file access? block them instead? kill them? Will you do it atomically? How will you allow for such large table-walking to be compatible with real-time kernel response? [Hint: either use incremental data-structures, or don't be atomic and be interruptible instead.] >> Finally, we discussed about saving _and restoring_ the state of a process, >> another hack that he did once to preserve a long-winded calculation >> from the service shutdown of a big unix computer. > I did this once, long long ago, under (I think) 4.3. I found that I > couldn't just dump core, though I forget why. As for the open file > descriptor question, I punted - I made the relevant call fail unless > the process had no fds open. Again, the difficult part is precisely about fd handling; and the suggested feature of whole-computer save&restore (where external connections will still be a problem) similarly required that device drivers be able to dump restorable state. >> By posting on all free unix kernel mailing-list I know, >> I intend to put free unices in competition as to which >> will implement these features first. > Reasonable as this sounds, I think the last thing we need is yet > another ground on which one free-unix can be doing the "nana nana boo > boo" taunt at another. Competition is _not_ about taunting each other for pride; it's about striving to be the best we can in an atmosphere of creative diversity whereby people copy each other's good ideas and drop everyone's bad ideas. Diversity and free competition increase the odds of good and bad ideas being recognized as what they are, first by one, then by everyone, which benefits to everyone in the form of positive evolution. But let's reserve such meta-technical discussions to another forum. >> As for the opening with no permissions - well, it would make *big* >> sense if we could narrow down the API and move chown(), chmod(), etc. >> into libc leaving f-variants in the kernel. > I really don't like that. The reasons why are (1) this means you have > to have an fd free to do them; (2) it triples the number of user/kernel > crossings involved. I think that (1) file descriptors are not an expensive resource, and the kernel will basically have to maintain an internal temporary resource that has most of the file descriptor complexity when doing name-based operations, anyway; (2) processes that have critical behavior will prefer a locking open-based interface to do several things at once, whereas those that do only name-based handling are mostly non-critical user-interaction processes where syscalls are not the performance bottleneck; (3) if that's really really a problem, you can still keep old syscalls as a an optimization, although it might be argued that keeping the kernel smaller will help reduce page faults and make more memory available, which will have a beneficial overall effect on performance. [ "Faré" | VN: Уng-Vû Bân | Join the TUNES project! http://www.tunes.org/ ] [ FR: François-René Rideau | TUNES is a Useful, Nevertheless Expedient System ] [ Reflection&Cybernethics | Project for a Free Reflective Computing System ] Imagine algebra in XML: instead of (sin (+ x y)), sin(x+y) or x y + sin, you get . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 16:19:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9664D14ECD for ; Sun, 27 Jun 1999 16:19:20 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id AAA29423; Mon, 28 Jun 1999 00:21:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 28 Jun 1999 00:21:55 +0100 (BST) From: Doug Rabson To: Alexander Viro Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API 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 Sun, 27 Jun 1999, Alexander Viro wrote: > > > On Sun, 27 Jun 1999, Doug Rabson wrote: > > > This looks viable as long as you don't use small integers to represent > > FL_UFS etc. Having a single header defining constants for all filesystems > > Erm... sizeof(int)==4. I doubt that you will need more. > > > just doesn't scale at all. > Sure. If you don't need fs-specific stuff - and there > you go. If you need some particular fs - and I'm talking about the concept of a header file containing something like: #define FL_VFS 0 #define FL_FOOFS 1 #define FD_BARFS 2 ... not being scalable. Do you have a complete list of filesystem types? Are you prepared to act as an Assigned Number authority for that list. For this kind of problem, strings are a damn sight easier to manage in the long term. > > > You still want a clearly defined set of FS independant flags so that the > > application doesn't need to care what filesystem it is sitting on. > > And that's exactly the reason for FL_VFS vs. FL_FOOFS separation - > some applications should be able to talk with the filesystem in the > filesystem's terms *and* be sure that they will not mess with another fs; > the rest shouldn't care for fs differences at all (aside of "did the > sucker set the bits I wanted?" that you already have for SUID/SGID/sticky). > > I don't think that porting it to 4.4 will be difficult - all you > need is a way to tell VOP_SETATTR what level are you talking to (most > likely the same way as on the our side - add a field to the structure and > let the methods scratch their heads). I'm going to do the Linux variant > and see how it will work. If somebody wants to do it with *BSD - fine, it > shouldn't be a problem. I'm sure the api would be easy to port. I wouldn't accept any api for FreeBSD which involved assigning numbers to filesystem types. It was too painful to rid it of the last set of numbers from the old mount(2) call. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 16:34:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [132.206.78.3]) by hub.freebsd.org (Postfix) with ESMTP id 02A0114E84 for ; Sun, 27 Jun 1999 16:34:04 -0700 (PDT) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id TAA23042; Sun, 27 Jun 1999 19:33:32 -0400 (EDT) Date: Sun, 27 Jun 1999 19:33:32 -0400 (EDT) From: der Mouse Message-Id: <199906272333.TAA23042@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> (clri didn't work?) > Never heard about clri (was under Linux). May not have existed, then, which *would* explain it. :-) >>> Another problem was the ability to change the mount status of a >>> partition from read-write to read-only or to unmounted, >> See NetBSD (and presumably other BSD) "mount -o update,rdonly" >> and/or "umount -f". > If you re-read the original message, the problem is what to do about > processes with open file descriptors on the partition: stop them at > once? stop them at first file access? block them instead? kill them? Yes, that's the most difficult part. The NetBSD manpage doesn't say what happens if you "mount -o update,force,rdonly" when there are writeable descriptors open onto the filesystem, and then try to use those fds. I would assume further attempts to write would produce errors (EROFS?), unless of course the filesystem has been re-remounted read/write. The manpage for umount says -f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. I haven't looked at the relevant kernel code to see what *really* happens. > How will you allow for such large table-walking to be compatible with > real-time kernel response? *What* large table-walking? All this means you have to do is have every write check the relevant mount point to see if it's mounted read-only, for downgrading remounts, and mark the filesystem as gone, for forced unmounts. (I suspect this is what deadfs is for.) >>> I intend to put free unices in competition [...] >> Reasonable as this sounds, I think the last thing we need is yet >> another ground on which one free-unix can be doing the "nana nana >> boo boo" taunt at another. > Competition is _not_ about taunting each other for pride; I know this. I even think most of the people involved know it. But there seem to be a few - not many, but very poisonous - who seem to take any competition - indeed, almost any *difference* - as an opportunity for "we're better than you" egoboo. der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 16:35:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id BBFE214E84 for ; Sun, 27 Jun 1999 16:35:21 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id TAA17805 for ; Sun, 27 Jun 1999 19:38:48 -0400 (EDT) Date: Sun, 27 Jun 1999 18:38:47 -0500 (EST) From: Alfred Perlstein To: hackers@freebsd.org Subject: pseudo kernel dma/tee 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 any support or plans for support of "kernel dma", sort of like the aio stuff, however you just give the kernel two file descriptors and perhaps some parameters (such as seeking to a specific point on either or both files and amount of data to be sent) and the kernel will then do all the copying for you? You could avoid a lot of work when doing proxy like connections this way.. This would be like sendfile() however it would be possible to mix socket+socket or fd+fd. Another interesting application would be to implement this with an option of tee'ing the transfer into the process' address space as well. Just something that popped into my head while writing a mini proxy today... It would save a lot of cycles for certain apps. -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Win Telecom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 17: 4:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id E4B79151E3 for ; Sun, 27 Jun 1999 17:03:56 -0700 (PDT) (envelope-from fare@tunes.org) Received: (qmail 10777 invoked from network); 28 Jun 1999 00:03:54 -0000 Received: from d153.paris-131.cybercable.fr (HELO ZhengHe) ([212.198.131.153]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 28 Jun 1999 00:03:54 -0000 Received: from fare by ZhengHe with local (Exim 2.11 #1 (Debian)) id 10yOrw-0001aP-00; Mon, 28 Jun 1999 02:01:52 +0200 Date: Mon, 28 Jun 1999 02:01:51 +0200 From: Francois-Rene Rideau To: der Mouse Cc: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Message-ID: <19990628020151.A6067@ZhengHe.augustin.thierry> Reply-To: Francois-Rene Rideau References: <199906272333.TAA23042@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i In-Reply-To: <199906272333.TAA23042@Twig.Rodents.Montreal.QC.CA>; from der Mouse on Sun, Jun 27, 1999 at 07:33:32PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 27, 1999 at 07:33:32PM -0400, der Mouse wrote: >> If you re-read the original message, the problem is what to do about >> processes with open file descriptors on the partition [...] > Yes, that's the most difficult part. [...] NetBSD manpage: > -f The filesystem is forcibly unmounted. Active special devices > continue to work, but all other files return errors if further > accesses are attempted. I think that returning errors is WRONG, unless specifically requested by fnctl(). It means that processes will get unexpected errors from otherwise validly open filedescriptor. It means that you can't fix the problem with the filesystem and resume operations nicely afterwards; or you will have to manually stop processes from userland before unmounting, which would not be atomic and generate yet another race condition. Robert seemed to favor atomically stopping processes. I am personally in favor of defaulting to a blocking behavior. >> How will you allow for such large table-walking to be compatible with >> real-time kernel response? > *What* large table-walking? All this means you have to do is have > every write check the relevant mount point to see if it's mounted > read-only, for downgrading remounts, and mark the filesystem as gone, > for forced unmounts. (I suspect this is what deadfs is for.) That's typical incremental behavior. Again, it's a matter of tradeoff: do you want a big atomic operation once in a while and simple operations every time, or complex incremental operations every time? It's real-time response vs overall-time duration. See GC for a field of CS where this trade-off has been beaten to death. Also, the worry was most important in the case of atomically stopping processes as recommended by Robert. Hum. It looks like the need to avoid losing file descriptor information and pending I/O requests would make it a good idea that there be a mount mode without either read or write permissions, similarly to opening files without read or write permissions. Looks to me like an interesting alternative to deadfs, anyway... >> Competition is _not_ about taunting each other for pride; > I know this. I even think most of the people involved know it. Cool. > But there seem to be a few - not many, but very poisonous - who seem to > take any competition - indeed, almost any *difference* - as an > opportunity for "we're better than you" egoboo. "Hey, stupid, my underwear is nicer than yours!" Hum. Let's just send those kiddies to /dev/null; uh, I mean, er, whatever. [ "Faré" | VN: Уng-Vû Bân | Join the TUNES project! http://www.tunes.org/ ] [ FR: François-René Rideau | TUNES is a Useful, Nevertheless Expedient System ] [ Reflection&Cybernethics | Project for a Free Reflective Computing System ] My opinions may have changed, but not the fact that I am right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 17:43:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 1424314CAF for ; Sun, 27 Jun 1999 17:43:37 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id UAA05427; Sun, 27 Jun 1999 20:43:29 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id UAA03825; Sun, 27 Jun 1999 20:43:28 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 20:43:28 -0400 (EDT) From: Alexander Viro To: der Mouse Cc: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906272333.TAA23042@Twig.Rodents.Montreal.QC.CA> 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, 27 Jun 1999, der Mouse wrote: > >> (clri didn't work?) > > Never heard about clri (was under Linux). > > May not have existed, then, which *would* explain it. :-) # debugfs -w /dev/sda1 debugfs: clri file debugfs: close It exists, all right ;-) Even documented - man 8 debugfs and there you go. > The NetBSD manpage doesn't say what happens if you "mount -o > update,force,rdonly" when there are writeable descriptors open onto the > filesystem, and then try to use those fds. I would assume further > attempts to write would produce errors (EROFS?), unless of course the > filesystem has been re-remounted read/write. Forced revoke()? But then there is mmap() and IIRC revoke() on *BSD doesn't unmap the stuff. Oh, shit, there is such thing as pending unlink... Does vgone() force it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 17:52: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 474D114D21 for ; Sun, 27 Jun 1999 17:51:54 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id RAA07365; Sun, 27 Jun 1999 17:51:07 -0700 (PDT) Message-Id: <199906280051.RAA07365@lestat.nas.nasa.gov> To: Alexander Viro Cc: der Mouse , Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 27 Jun 1999 17:51:06 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999 20:43:28 -0400 (EDT) Alexander Viro wrote: > Forced revoke()? But then there is mmap() and IIRC revoke() on *BSD > doesn't unmap the stuff. Oh, shit, there is such thing as pending > unlink... Does vgone() force it? It doesn't unmap the region, but it doesn't allow any more page faults from that backing vnode (the pager will get an error from the file system, and thus send a SIGSEGV to the process), and no dirty pages can be cleaned to that vnode. I mean, you wouldn't invalidate any buffers the user read the file into when the file was revoke()'d, would you? :-) Regarding unlink()... those aren't operations on vnodes. Those are operations on the filesystem namespace, and are thus (correctly) unaffected. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18: 0:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 2754214D21 for ; Sun, 27 Jun 1999 18:00:09 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA05702; Sun, 27 Jun 1999 21:00:08 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA03854; Sun, 27 Jun 1999 21:00:07 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 21:00:07 -0400 (EDT) From: Alexander Viro To: Doug Rabson Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API 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 Mon, 28 Jun 1999, Doug Rabson wrote: > I'm talking about the concept of a header file containing something like: > > #define FL_VFS 0 > #define FL_FOOFS 1 > #define FD_BARFS 2 > ... > > not being scalable. > > Do you have a complete list of filesystem types? Are you prepared to act > as an Assigned Number authority for that list. For this kind of problem, > strings are a damn sight easier to manage in the long term. Augh... It's ugly, indeed, but... sysctl() is not much nicer and all systems in question manage to deal with it somehow. OTOH doing it as strings... Hell knows. I'll look at it. Considering that HFS folks had already asked for more than one value here (creator and type?) it may be reasonable. I'm afraid that doing that may open the hell gates ;-/ 'N' in *ANA can be 'namespace' as well as 'number'... [1] BTW, how does NetBSD deal with HFS forks? [1] cue current flamew^Wthreads on l-k regarding files-as-directories hell. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18: 5:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 9BF2014BEC for ; Sun, 27 Jun 1999 18:05:22 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA05776; Sun, 27 Jun 1999 21:05:19 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA03861; Sun, 27 Jun 1999 21:05:18 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 21:05:18 -0400 (EDT) From: Alexander Viro To: Jason Thorpe Cc: der Mouse , Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API In-Reply-To: <199906280051.RAA07365@lestat.nas.nasa.gov> 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, 27 Jun 1999, Jason Thorpe wrote: > Regarding unlink()... those aren't operations on vnodes. Those are > operations on the filesystem namespace, and are thus (correctly) > unaffected. Eh, wait. Those are operations on namespace, but at some moment you need to clean the bit in inode bitmap. You can't do it before the last close() and it definitely alters the filesystem. fsck will pick them up, but that may be *not* a desired result. Dirty filesystem is definitely not desired anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18: 8:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by hub.freebsd.org (Postfix) with ESMTP id CAB4714BEB for ; Sun, 27 Jun 1999 18:08:52 -0700 (PDT) (envelope-from cwood@ichips.intel.com) Received: from ichips-ra.pdx.intel.com (ichips-ra.pdx.intel.com [137.102.192.31]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id SAA11909; Sun, 27 Jun 1999 18:08:33 -0700 (PDT) Received: from pdxcs199.pdx.intel.com (pdxcs199.pdx.intel.com [137.102.196.139]) by ichips-ra.pdx.intel.com (8.9.1a/8.9.1/d: internal.m4,v 1.2 1998/11/09 19:18:37 iwep Exp iwep $) with ESMTP id SAA10014; Sun, 27 Jun 1999 18:08:33 -0700 (PDT) Received: (from cwood@localhost) by pdxcs199.pdx.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id SAA137568; Sun, 27 Jun 1999 18:08:33 -0700 Message-Id: <199906280108.SAA137568@pdxcs199.pdx.intel.com> Subject: Re: Improving the Unix API In-Reply-To: from Alexander Viro at "Jun 27, 99 09:00:07 pm" To: viro@math.psu.edu (Alexander Viro) Date: Sun, 27 Jun 1999 18:08:32 -0700 (PDT) From: Colin Wood Cc: linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Reply-To: ender@macbsd.com X-Mailer: ELM [version 2.4ME+ PL37 (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 Alexander Viro wrote: > [1] > BTW, how does NetBSD deal with HFS forks? > easy, it doesn't :-) we don't currently have HFS support, mainly b/c the only freeware implementations of it (that i'm aware of) are GPL'd, and no one has been able to devote enough time to it to get a BSD-licensed version. although the darwin stuff is now available. i'm not too sure how much of it is useful (i haven't looked at it either, tho). later. colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18:16:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 1418C15283 for ; Sun, 27 Jun 1999 18:16:07 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from ece.cmu.edu (localhost [127.0.0.1]) by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id VAA25177; Sun, 27 Jun 1999 21:12:12 -0400 (EDT) Message-Id: <199906280112.VAA25177@ece.cmu.edu> Date: Sun, 27 Jun 1999 21:12:09 -0400 (EDT) From: allbery@ece.cmu.edu Reply-To: allbery@ece.cmu.edu Subject: Re: Improving the Unix API To: thorpej@nas.nasa.gov Cc: viro@math.psu.edu, mouse@Rodents.Montreal.QC.CA, fare@tunes.org, freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org, linux-kernel@vger.rutgers.edu In-Reply-To: <199906280051.RAA07365@lestat.nas.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Jun, Jason Thorpe wrote: +----- | Alexander Viro wrote: | > doesn't unmap the stuff. Oh, shit, there is such thing as pending | > unlink... Does vgone() force it? | | Regarding unlink()... those aren't operations on vnodes. Those are | operations on the filesystem namespace, and are thus (correctly) | unaffected. +--->8 I believe what he meant is "how is deallocation of a pending-unlink file whose only reference is an open fd which has been revoked dealt with"? (To which my own answer would be: "deallocated on close as usual, no reason to treat this case specially that I know of".) -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH We are Linux. Resistance is an indication that you missed the point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18:16:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6DB06152D8 for ; Sun, 27 Jun 1999 18:16:31 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA88952; Sun, 27 Jun 1999 21:16:06 -0400 (EDT) Date: Sun, 27 Jun 1999 21:16:06 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Alexander Viro Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API y, 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 Sun, 27 Jun 1999, Alexander Viro wrote: > > As for the opening with no permissions - well, it would make *big* sense > if we could narrow down the API and move chown(), chmod(), etc. into libc > leaving f-variants in the kernel. Binary compatibility... Extreme variant > might include {set,get}sockopt extended to files and doing both *stat and > *ch{mod,own,flags} via that. Out of curiosity - did somebody on *BSD side > play with that? > Actually, instead of *big* sense, that makes *no* sense. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sun Jun 27 18:28:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 59C9014F84 for ; Sun, 27 Jun 1999 18:28:17 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from ece.cmu.edu (localhost [127.0.0.1]) by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id VAA25227; Sun, 27 Jun 1999 21:27:47 -0400 (EDT) Message-Id: <199906280127.VAA25227@ece.cmu.edu> Date: Sun, 27 Jun 1999 21:27:45 -0400 (EDT) From: allbery@ece.cmu.edu Reply-To: allbery@ece.cmu.edu Subject: Re: Improving the Unix API To: thorpej@nas.nasa.gov Cc: viro@math.psu.edu, mouse@Rodents.Montreal.QC.CA, fare@tunes.org, freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org, linux-kernel@vger.rutgers.edu In-Reply-To: <199906280112.VAA25177@ece.cmu.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Jun, To: thorpej@nas.nasa.gov wrote: +----- | (To which my own answer would be: "deallocated on close as usual, no | reason to treat this case specially that I know of".) +--->8 Strike that, I was on the wrong page. (Crossed threads re: general revoke() on Linux) -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH We are Linux. Resistance is an indication that you missed the point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 18:31:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 4787C15239 for ; Sun, 27 Jun 1999 18:31:24 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA06141; Sun, 27 Jun 1999 21:31:22 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id VAA03928; Sun, 27 Jun 1999 21:31:21 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Sun, 27 Jun 1999 21:31:21 -0400 (EDT) From: Alexander Viro To: allbery@ece.cmu.edu Cc: thorpej@nas.nasa.gov, mouse@Rodents.Montreal.QC.CA, fare@tunes.org, freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org, linux-kernel@vger.rutgers.edu Subject: Re: Improving the Unix API In-Reply-To: <199906280112.VAA25177@ece.cmu.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 Sun, 27 Jun 1999 allbery@ece.cmu.edu wrote: > On 27 Jun, Jason Thorpe wrote: > +----- > | Alexander Viro wrote: > | > doesn't unmap the stuff. Oh, shit, there is such thing as pending > | > unlink... Does vgone() force it? > | > | Regarding unlink()... those aren't operations on vnodes. Those are > | operations on the filesystem namespace, and are thus (correctly) > | unaffected. > +--->8 > > I believe what he meant is "how is deallocation of a pending-unlink > file whose only reference is an open fd which has been revoked dealt > with"? > > (To which my own answer would be: "deallocated on close as usual, no > reason to treat this case specially that I know of".) When it's already remounted r/o? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 19: 9:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id B827115269 for ; Sun, 27 Jun 1999 19:09:26 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id WAA22733 for ; Sun, 27 Jun 1999 22:09:56 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id WAA18393 for ; Sun, 27 Jun 1999 22:09:22 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id WAA76016 for freebsd-hackers@freebsd.org; Sun, 27 Jun 1999 22:09:22 -0400 (EDT) Date: Sun, 27 Jun 1999 22:09:22 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906280209.WAA76016@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: setiathome crashes 3.2? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall seeing this someone (this may not be the right list.) But - I downloaded the 3.2 Seti@home and starting running it on a left-over 75mhz laptop I have. It seems to crash the laptop (silently lock it up, actually) fairly quickly. Did I recall someone else mentioning that? Would everyone agree that it's not a "good thing" for a user-mode program to be able to lock up the OS? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 19:19: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [132.206.78.3]) by hub.freebsd.org (Postfix) with ESMTP id ABD3314E30 for ; Sun, 27 Jun 1999 19:19:00 -0700 (PDT) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id WAA00668; Sun, 27 Jun 1999 22:18:22 -0400 (EDT) Date: Sun, 27 Jun 1999 22:18:22 -0400 (EDT) From: der Mouse Message-Id: <199906280218.WAA00668@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: Francois-Rene Rideau , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> -f The filesystem is forcibly unmounted. Active special devices >> continue to work, but all other files return errors if further >> accesses are attempted. > I think that returning errors is WRONG, unless [...] > It means that you can't fix the problem with the filesystem and > resume operations nicely afterwards; I think I see part of the problem here. You are thinking "unmount to fix problem, will remount later". "umount -f" is more like "it's going away, dammit, and I'd rather crash a few processes than have to take down the whole system". It might be worthwhile having an option that causes attempted accesses to hang until the filesystem comes back online, somewhat akin to Auspex's filesystem "isolation". der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 19:26:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by hub.freebsd.org (Postfix) with ESMTP id 262E0152B5 for ; Sun, 27 Jun 1999 19:26:48 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-251.s60.as3.hgt.md.dialup.rcn.com [207.172.143.251]) by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id WAA09596; Sun, 27 Jun 1999 22:26:35 -0400 (EDT) Message-Id: <199906280226.WAA09596@smtp3.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906251244.FAA30357@sigma.veritas.com> Date: Sun, 27 Jun 1999 22:26:34 -0400 (EDT) From: John Baldwin To: Aaron Smith Subject: Re: Inetd and wrapping. Cc: Doug , David Malone , freebsd-hackers@FreeBSD.ORG, Sheldon Hearn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jun-99 Aaron Smith wrote: > On Fri, 25 Jun 1999 10:14:48 +0200, Sheldon Hearn writes: >>I think I prefer the suggestion I saw from someone else, which would >>allow >> >>ftp stream tcp nowait/10/10/wrap root ... >> >>This can be done in such a way as to be backward compatible. Looks like >>something for the week-end, if I can convince my wife that it's a good >>idea. :-) > > could you please restate the argument for this? i still haven't heard a > decent reason for this sort of conf format perturbation. every small whack > like this makes freebsd weirder to administrate -- there is a value to > sharing the same inetd.conf format with lots of other platforms. > > if people have their undies in a wad over this, can't they compile inetd > without LIBWRAP? Ahem.. Let's say I have two services, foo and bar, with food and bard. I want to wrap food, but *NOT* bard and they are both in /etc/inetd.conf. How do you propose to solve this with the internal wrapping (which is a good idea, IMO as it eliminates an exec())? > aaron --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/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 Sun Jun 27 19:27:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id 579B11535A for ; Sun, 27 Jun 1999 19:27:38 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-251.s60.as3.hgt.md.dialup.rcn.com [207.172.143.251]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id WAA03294; Sun, 27 Jun 1999 22:27:29 -0400 (EDT) Message-Id: <199906280227.WAA03294@smtp1.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906252058.OAA78683@dune.plutotech.com> Date: Sun, 27 Jun 1999 22:27:28 -0400 (EDT) From: John Baldwin To: Drew Eckhardt Subject: Re: Inetd and wrapping. Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jun-99 Drew Eckhardt wrote: > In article <199906242353.TAA06995@smtp4.erols.com> you write: >> >>Here's one possibility, it adds a a wrap/nowrap field that goes beside the >>wait/nowait field, so you would have: >> >>ftp stream tcp nowait wrap root /usr/libexec/ftpd ftpd >>-l > > Breaking backwards compatability is evil. Do something like this instead - > > ftp stream tcp nowait&wrap root /usr/libexec/ftpd ftpd > -l That's easy to change (just change where it reads the wrap/nowrap whatever in the last half of the patch). It was more of a proof of concept to show that it could be easily done in 10 minutes or so. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/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 Sun Jun 27 19:42: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (unknown [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 8049E152CF for ; Sun, 27 Jun 1999 19:42:02 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id CAA10989; Mon, 28 Jun 1999 02:39:25 GMT Date: Mon, 28 Jun 1999 02:39:25 +0000 (GMT) From: Ben Rosengart To: David Malone Cc: Aaron Smith , Sheldon Hearn , Keith Stevenson , freebsd-hackers@FreeBSD.ORG Subject: Re: Inetd and wrapping. In-Reply-To: <19990625201201.A10893@boole.maths.tcd.ie> 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, 25 Jun 1999, David Malone wrote: > Some people think that doing the hosts.allow lookup is too expensive > for some services but not others. (It requires opening /etc/hosts.allow, > reading it in line by line and possibly doing DNS lookups). I would hope that anyone concerned about speed would be writing tcp-wrappers rules with numbers, not names. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 20:11:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.masirv.com (ns1.masirv.com [207.105.128.2]) by hub.freebsd.org (Postfix) with SMTP id 321BA14F8B for ; Sun, 27 Jun 1999 20:11:35 -0700 (PDT) (envelope-from FloresR@mx3.masirv.com) Received: from ns2.masirv.com (root@ns2 [207.105.129.4]) by ns1.masirv.com (8.6.12/8.6.6) with ESMTP id UAA27903 for ; Sun, 27 Jun 1999 20:11:35 -0700 Received: from newman.masirv.com (mx3 [207.105.129.15]) by masirv.com (8.8.7/8.8.7) with ESMTP id UAA05256 for ; Sun, 27 Jun 1999 20:11:33 -0700 Received: by exchange.masirv.com with Internet Mail Service (5.5.2448.0) id ; Sun, 27 Jun 1999 20:11:33 -0700 Message-ID: From: Richard Flores To: "'freebsd-hackers@FreeBSD.ORG'" Subject: RE: setiathome crashes 3.2? Date: Sun, 27 Jun 1999 20:11:32 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers end > -----Original Message----- > From: Thomas David Rivers [mailto:rivers@dignus.com] > Sent: Sunday, June 27, 1999 7:09 PM > To: freebsd-hackers@FreeBSD.ORG > Subject: setiathome crashes 3.2? > > > > I seem to recall seeing this someone (this may not be the > right list.) > > But - I downloaded the 3.2 Seti@home and starting running it > on a left-over 75mhz laptop I have. > > It seems to crash the laptop (silently lock it up, actually) > fairly quickly. > > Did I recall someone else mentioning that? > > Would everyone agree that it's not a "good thing" for a user-mode > program to be able to lock up the OS? > > - Dave Rivers - > > > > 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 Jun 27 22:21:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5AAAA1532D for ; Sun, 27 Jun 1999 22:21:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA02982; Sun, 27 Jun 1999 22:21:37 -0700 Date: Sun, 27 Jun 1999 22:19:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Thomas David Rivers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: setiathome crashes 3.2? In-Reply-To: <199906280209.WAA76016@lakes.dignus.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 Umm- I've been running it for weeks on 3.2 with no problem. On Sun, 27 Jun 1999, Thomas David Rivers wrote: > > I seem to recall seeing this someone (this may not be the > right list.) > > But - I downloaded the 3.2 Seti@home and starting running it > on a left-over 75mhz laptop I have. > > It seems to crash the laptop (silently lock it up, actually) > fairly quickly. > > Did I recall someone else mentioning that? > > Would everyone agree that it's not a "good thing" for a user-mode > program to be able to lock up the OS? > > - Dave Rivers - > > > > 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 Jun 27 22:25:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 2499A150D9 for ; Sun, 27 Jun 1999 22:25:30 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id WAA16612; Sun, 27 Jun 1999 22:26:08 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (1629 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sun, 27 Jun 1999 22:25:16 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id WAA48626; Sun, 27 Jun 1999 22:25:12 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906280525.WAA48626@sigma.veritas.com> From: Aaron Smith To: John Baldwin Cc: Aaron Smith , Doug , David Malone , freebsd-hackers@FreeBSD.ORG, Sheldon Hearn Subject: Re: Inetd and wrapping. In-reply-to: Your message of "Sun, 27 Jun 1999 22:26:34 EDT." <199906280226.WAA09596@smtp3.erols.com> Date: Sun, 27 Jun 1999 22:25:11 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999 22:26:34 EDT, John Baldwin writes: >Let's say I have two services, foo and bar, with food and bard. I want to >wrap food, but *NOT* bard and they are both in /etc/inetd.conf. How do >you propose to solve this with the internal wrapping (which is a good >idea, IMO as it eliminates an exec())? i wouldn't...i'd have to either pay the (small) cost of wrapping or pay the (less small) tcpd exec and not use internal wrapping. it's "nice" to save the exec, but intensely performance or latency sensitive daemons probably shouldn't be starting out of inetd, they should be standalone and preforked or threaded... aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 23: 3:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0516515366 for ; Sun, 27 Jun 1999 23:03:52 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id HAA15271; Mon, 28 Jun 1999 07:56:33 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id IAA06480; Mon, 28 Jun 1999 08:03:15 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id IAA43913; Mon, 28 Jun 1999 08:04:08 +0200 (CEST) (envelope-from ticso) Date: Mon, 28 Jun 1999 08:04:08 +0200 From: Bernd Walter To: Thomas David Rivers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: setiathome crashes 3.2? Message-ID: <19990628080407.A43878@cicely8.cicely.de> References: <199906280209.WAA76016@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199906280209.WAA76016@lakes.dignus.com>; from Thomas David Rivers on Sun, Jun 27, 1999 at 10:09:22PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jun 27, 1999 at 10:09:22PM -0400, Thomas David Rivers wrote: > > I seem to recall seeing this someone (this may not be the > right list.) > > But - I downloaded the 3.2 Seti@home and starting running it > on a left-over 75mhz laptop I have. > > It seems to crash the laptop (silently lock it up, actually) > fairly quickly. > > Did I recall someone else mentioning that? > > Would everyone agree that it's not a "good thing" for a user-mode > program to be able to lock up the OS? > There are severall resons. One of them is that I got panics with a to high set MAXUSER in kernel options. I don't know if it's a problem with 3.2. The other possible reason might be a CPU overheating. CPUs used under FreeBSD are typicall suspended during idle-time - when running seti or other permanent running programms there is no idle time. I asume there are several more possbilities. But it sounds like there is something broken with your configuration. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 23:11: 8 1999 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 5178415394 for ; Sun, 27 Jun 1999 23:11:05 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA91393 for ; Mon, 28 Jun 1999 00:11:05 -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 AAA13467 for ; Mon, 28 Jun 1999 00:09:22 -0600 (MDT) Message-Id: <199906280609.AAA13467@harmony.village.org> To: hackers@freebsd.org Subject: "restricted" kernel threads implementation from NetBSD via newconfig Date: Mon, 28 Jun 1999 00:09:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to bring a kernel thread implementation, ported from NetBDS by the newconfig project, into the kernel. Who would like to review things before they go into the tree? I can see many benefits for having this in the tree, but very little downside. This should allow people to more easily port raid-frame from NetBSD if they desire. FYI, this is an outshoot of the porting of the newconfig code to new-bus. Each bridge controller has its own even thread to handle cards events in a sane manner. It is basically a stripped down pccardd in the kernel, but one that has a huge hint database. I'm not proposing, at this time, to bring it on. I just want to get the kthread stuff in as a separate issue. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 27 23:34:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5EAE315369 for ; Sun, 27 Jun 1999 23:34:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id XAA04905; Sun, 27 Jun 1999 23:34:25 -0700 (PDT) Date: Sun, 27 Jun 1999 23:34:22 -0700 (PDT) From: Julian Elischer To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via newconfig In-Reply-To: <199906280609.AAA13467@harmony.village.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 please yes.. eventually we'll be using it to fire off a thread for every interrupt source if we go the BSDI way. (as dicussed with various people at USENIX) I was actually thinking about this today... now this is threads within the kernel, and not kernel support for user threads right? julian On Mon, 28 Jun 1999, Warner Losh wrote: > > I'd like to bring a kernel thread implementation, ported from NetBDS > by the newconfig project, into the kernel. Who would like to review > things before they go into the tree? I can see many benefits for > having this in the tree, but very little downside. This should allow > people to more easily port raid-frame from NetBSD if they desire. > > FYI, this is an outshoot of the porting of the newconfig code to > new-bus. Each bridge controller has its own even thread to handle > cards events in a sane manner. It is basically a stripped down > pccardd in the kernel, but one that has a huge hint database. I'm not > proposing, at this time, to bring it on. I just want to get the > kthread stuff in as a separate issue. > > Comments? > > Warner > > > 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 Jun 28 0:19: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C33FE150EF for ; Mon, 28 Jun 1999 00:19:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA18001; Mon, 28 Jun 1999 00:19:01 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 00:19:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280719.AAA18001@apollo.backplane.com> To: Julian Elischer Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via newconfig References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :please yes.. :eventually we'll be using it to fire off a thread for every interrupt :source if we go the BSDI way. (as dicussed with various people at USENIX) : :I was actually thinking about this today... : :now this is threads within the kernel, and not kernel support for user :threads right? : :julian I think we desparately need a kernel threads implementation. *Any* implementation, so we can start messing around with it! Even if it isn't the one we eventually choose. Once we have something we can add interrupt-thread support to it and then move some of the more innocuous interrupt-based device drivers over to it to generate test cases for the various SMP mechanisms people have been discussing. I was thinking, specifically, of moving a few of the ethernet devices, which tend to have relatively simplistic interrupt-level code - a perfect test case for us because it will be fairly easy to port and fairly easy to measure performance under load. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 0:24:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.ms.tlk.com (saturn.ms.tlk.com [194.97.68.6]) by hub.freebsd.org (Postfix) with ESMTP id 9F836153B8 for ; Mon, 28 Jun 1999 00:24:10 -0700 (PDT) (envelope-from br@smilla.rueskamp.com) Received: from mars.ms.tlk.com (mars.ms.tlk.com [194.97.68.1]) by saturn.ms.tlk.com (Postfix) with ESMTP id 1DF304ECF7; Mon, 28 Jun 1999 09:24:10 +0200 (CEST) Received: from smilla.rueskamp.com(really [194.97.69.109]) by mars.ms.tlk.com via sendmail with esmtp id for ; Mon, 28 Jun 1999 09:24:09 +0200 (CEST)) Received: (from br@localhost) by smilla.rueskamp.com (8.9.3/8.9.3) id JAA23765; Mon, 28 Jun 1999 09:23:13 +0200 (CEST) (envelope-from br) From: Bodo Rueskamp Message-Id: <199906280723.JAA23765@smilla.rueskamp.com> Subject: Re: Improving the Unix API In-Reply-To: <19990628010446.A5377@ZhengHe.augustin.thierry> from Francois-Rene Rideau at "Jun 28, 1999 01:04:47 am" To: fare@tunes.org (Francois-Rene Rideau) Date: Mon, 28 Jun 1999 09:23:13 +0200 (CEST) Cc: mouse@Rodents.Montreal.QC.CA (der Mouse), freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers), tech-kern@netbsd.org (NetBSD Kernel), tech@openbsd.org (OpenBSD Kernel), linux-kernel@vger.rutgers.edu (Linux Kernel) 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 > >> flink (make a new directory link for file given by descriptor), > flink() combined with the ability to create an unlinked file > in a given filesystem would allow for safe temporaries > without race conditions, that could be "published" when ready. The System V people (Solaris, Unixware) call this fattach(). ; Bodo -- Bodo Rüskamp, br@rueskamp.com, 51°55' N 7°41' E (1) Elvis is alive. (2) Dinosaurs too. (3) The next millenium starts on January 1st 2000. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1: 6:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from piinbh1.ms.com (piinbh1.ms.com [199.89.64.71]) by hub.freebsd.org (Postfix) with ESMTP id 083DD14E12 for ; Mon, 28 Jun 1999 01:06:14 -0700 (PDT) (envelope-from jsp@ms.com) Received: (from uucp@localhost) by piinbh1.ms.com (8.8.6/fw v1.22) id EAA28883; Mon, 28 Jun 1999 04:05:54 -0400 (EDT) Received: from unknown(138.20.197.23) by piinbh1.ms.com via smap (4.1) id xma028583; Mon, 28 Jun 99 04:05:23 -0400 Received: from ms.com (eqln106.morgan.com [205.228.77.106]) by hasmh1.morgan.com (8.8.5/imap+ldap v2.3) with ESMTP id JAA16989; Mon, 28 Jun 1999 09:05:17 +0100 (BST) Message-ID: <37772C78.ADC003F9@ms.com> Date: Mon, 28 Jun 1999 09:04:08 +0100 From: Jan-Simon Pendry X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.3.2 i586) X-Accept-Language: en MIME-Version: 1.0 To: Bodo Rueskamp Cc: Francois-Rene Rideau , der Mouse , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API References: <199906280723.JAA23765@smilla.rueskamp.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by hasmh1.morgan.com id JAA16989 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bodo Rueskamp wrote: >=20 > > >> flink (make a new directory link for file given by descriptor), > > flink() combined with the ability to create an unlinked file > > in a given filesystem would allow for safe temporaries > > without race conditions, that could be "published" when ready. >=20 > The System V people (Solaris, Unixware) call this fattach(). fattach is used to implement stream mounts. it does not attach an arbitrary file back to the filesystem. fattach is a library function that specifically mounts a stream pipe using the "namefs" filesystem. the effect of fattach does not persist across a reboot. jan-simon. >=20 > ; Bodo >=20 > -- > Bodo R=FCskamp, br@rueskamp.com, 51=B055' N 7=B041' E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:12:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from golgotha.dons.net.au (spare6.gsoft.com.au [203.38.152.108]) by hub.freebsd.org (Postfix) with ESMTP id 83ADB14E12 for ; Mon, 28 Jun 1999 01:12:06 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from golgotha.dons.net.au (localhost [127.0.0.1]) by golgotha.dons.net.au (8.9.3/8.9.3) with ESMTP id RAA04409; Mon, 28 Jun 1999 17:41:33 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <199906280719.AAA18001@apollo.backplane.com> Date: Mon, 28 Jun 1999 17:41:33 +0930 (CST) From: "Daniel J. O'Connor" To: Matthew Dillon Subject: Re: "restricted" kernel threads implementation from NetBSD via n Cc: hackers@FreeBSD.ORG, Warner Losh , Julian Elischer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_ Content-Type: text/plain; charset=us-ascii On 28-Jun-99 Matthew Dillon wrote: > I think we desparately need a kernel threads implementation. *Any* > implementation, so we can start messing around with it! Even if it isn't > the one we eventually choose. I don't suppose someone could post an explanation of how kernel threads work could they? :) I sort of grasp the idea but I'm wondering what passes for context switches and stuff like that.. What does the switching between threads etc? Or am I completely off track? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3ctpWj0TqzKxF7VAQE5uAP/SDvpI6TZJuDt0FfHfe0Eqp90QD2gjk2R nTrDhLsP/vMey3Ogsc/LeFNww8woaqXwTD6x3i+04wzkoDvti7rlczi4+2DUfnAj 79lflMw7DdBgd9tYB/3+QTQ3o2BVpT2JZK8zHVX5cPiPKHcPwQl7DhojQeqBx0QU W7ZKnn2ZYqI= =SXMo -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:17:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id E6BFE14E12 for ; Mon, 28 Jun 1999 01:17:41 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 28 Jun 1999 10:20:40 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796A9@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Matthew Dillon' , Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Implementation of mmap() in FreeBSD Date: Mon, 28 Jun 1999 10:14:50 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > :All these situations seem to me are not handled by FreeBSD mmap() > code. I > :hope I am wrong. I also wonder why we can not add some information to > the > > No machine's mmap() code handles these situations. It is a side > effect > of the way MMU's work and the way mmap() was defined - that is, in > order > for mmap() to be reasonably optimal it has to munge the boundry > conditions. It is an explicitly allowed case. > [ML] It is possible to handle these cases in VM code, by trapping on any access to the partial page, and allowing only those accesses which are withing the originally requested range. Performance would suck without end, though. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:23:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from golgotha.dons.net.au (spare6.gsoft.com.au [203.38.152.108]) by hub.freebsd.org (Postfix) with ESMTP id 0A34E14D01 for ; Mon, 28 Jun 1999 01:23:47 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from golgotha.dons.net.au (localhost [127.0.0.1]) by golgotha.dons.net.au (8.9.3/8.9.3) with ESMTP id RAA06351; Mon, 28 Jun 1999 17:53:09 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990628175309:1295=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <55586E7391ACD211B9730000C11002761796A9@r-lmh-wi-100.corpnet.at> Date: Mon, 28 Jun 1999 17:53:09 +0930 (CST) From: "Daniel J. O'Connor" To: Ladavac Marino Subject: RE: Implementation of mmap() in FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, Zhihui Zhang , Matthew Dillon Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990628175309:1295=_ Content-Type: text/plain; charset=us-ascii On 28-Jun-99 Ladavac Marino wrote: > [ML] It is possible to handle these cases in VM code, by > trapping on any access to the partial page, and allowing only those > accesses which are withing the originally requested range. Performance > would suck without end, though. Well it would only suck for access to that page right, which wouldn't be too bad unless the program in question thrashes out the partial pages. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990628175309:1295=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3cw7Wj0TqzKxF7VAQH2SAQApOZBeJlerLjcmaDTlJBocETis37A/VQv Bh8HnXBxpOB7reyA4YS9W5OFKUPCJu8rJ/tYBlV1AsVQAGclnOMhxAU7V6LqHwAI qvhfydHURpk7Mc4F2FSqBsF9G7Dpv6dzoNAb6uyJbyPBrZsPpPn+1HtjMFT2Fycx 5vsja1r8KRM= =isg3 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990628175309:1295=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:28:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id 5017114D01 for ; Mon, 28 Jun 1999 01:28:13 -0700 (PDT) (envelope-from Hans.Zuidam@nl.origin-it.com) Received: from mail.nl.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id KAA22949 for ; Mon, 28 Jun 1999 10:28:12 +0200 (MEST) (envelope-from Hans.Zuidam@nl.origin-it.com) Received: from mail.nl.origin-it.com(172.16.127.67) by gw-nl1.origin-it.com via mwrap (4.0a) id xma022947; Mon, 28 Jun 99 10:28:12 +0200 Received: from nlehx900.ehvovh.nl.origin-it.com (nlehx900.ehvovh.nl.origin-it.com [172.16.92.111]) by mail.nl.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id KAA22106 for ; Mon, 28 Jun 1999 10:28:02 +0200 (MET DST) Received: by nlehx900.ehvovh.nl.origin-it.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BEC150.E6C1FD50@nlehx900.ehvovh.nl.origin-it.com>; Mon, 28 Jun 1999 10:28:02 +0200 Message-ID: From: "Zuidam, Hans" To: "'hackers@FreeBSD.ORG'" Subject: RE: synch primitives Date: Mon, 28 Jun 1999 10:28:01 +0200 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 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 > -----Original Message----- > From: Wes Peters [mailto:wes@softweyr.com] > Sent: Friday, 25 June, 1999 23:46 > To: Aaron Smith > Cc: Alfred Perlstein; Brian F. Feldman; Karl Denninger; > hackers@FreeBSD.ORG > Subject: Re: synch primitives (was Re: Microsoft performance) > > > Here's a couple of good research points: And of course: "Unix Systems for Modern Architectures: Symmetric Multiprocesssing and Caching for Kernel Programmers", Curt Schimmel, September 1994, Addison-Wesley Pub Co; ISBN: 0201633388 -- Hans Zuidam h.zuidam@computer.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:34: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 758F814D01 for ; Mon, 28 Jun 1999 01:33:57 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA18397; Mon, 28 Jun 1999 01:32:53 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 01:32:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280832.BAA18397@apollo.backplane.com> To: "Daniel J. O'Connor" Cc: hackers@FreeBSD.ORG, Warner Losh , Julian Elischer Subject: Re: "restricted" kernel threads implementation from NetBSD via n References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I don't suppose someone could post an explanation of how kernel threads work :could they? :) : :I sort of grasp the idea but I'm wondering what passes for context switches and :stuff like that.. What does the switching between threads etc? Or am I :completely off track? : :--- :Daniel O'Connor software and network engineer Basically switching between kernel threads is the same as switching between processes except that you do not need to mess with the MMU or other complex scheduling elements, so switching between kernel threads can be made almost as fast as a simple subroutine call. A kernel thread can be thought of as a cheaper process. Threads are often called "tasks". The terminology is the same, but still distinct from "process". This is key to being able to vector an interrupt to a kernel thread. The interrupt code must already save much of the process context, adding a little extra glue to turn it into a kernel thread that we can actually switch-away from should theoretically be very cheap. -Matt Matthew Dillon :for Genesis Software - http://www.gsoft.com.au :"The nice thing about standards is that there :are so many of them to choose from." : -- Andrew Tanenbaum : :--_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_ :Content-Type: application/pgp-signature : :-----BEGIN PGP MESSAGE----- :Version: 2.6.3ia : :iQCVAwUBN3ctpWj0TqzKxF7VAQE5uAP/SDvpI6TZJuDt0FfHfe0Eqp90QD2gjk2R :nTrDhLsP/vMey3Ogsc/LeFNww8woaqXwTD6x3i+04wzkoDvti7rlczi4+2DUfnAj :79lflMw7DdBgd9tYB/3+QTQ3o2BVpT2JZK8zHVX5cPiPKHcPwQl7DhojQeqBx0QU :W7ZKnn2ZYqI= :=SXMo :-----END PGP MESSAGE----- : :--_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_-- :End of MIME 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 Mon Jun 28 1:42:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D233A14CC0 for ; Mon, 28 Jun 1999 01:42:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA18494; Mon, 28 Jun 1999 01:41:58 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 01:41:58 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280841.BAA18494@apollo.backplane.com> To: "Daniel J. O'Connor" Cc: Ladavac Marino , freebsd-hackers@FreeBSD.ORG, Zhihui Zhang Subject: Re: RE: Implementation of mmap() in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> [ML] It is possible to handle these cases in VM code, by :> trapping on any access to the partial page, and allowing only those :> accesses which are withing the originally requested range. Performance :> would suck without end, though. : :Well it would only suck for access to that page right, which wouldn't be too :bad unless the program in question thrashes out the partial pages. : :--- :Daniel O'Connor software and network engineer I don't think this would be workable. It would fail utterly on small files -- every single access would be trapped. The system must be reasonably deterministic. Programmers have a reasonable expectation that accesses to mmap'd areas are, for in-core pages, instantanious. Otherwise they wouldn't bother to use mmap and instead would use read() and write() :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:50: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C62A01511F for ; Mon, 28 Jun 1999 01:49:55 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA78466; Mon, 28 Jun 1999 09:52:43 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 28 Jun 1999 09:52:35 +0100 (BST) From: Doug Rabson To: Alexander Viro Cc: Bill Sommerfeld , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API 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 Sun, 27 Jun 1999, Alexander Viro wrote: > > > On Mon, 28 Jun 1999, Doug Rabson wrote: > > I'm talking about the concept of a header file containing something like: > > > > #define FL_VFS 0 > > #define FL_FOOFS 1 > > #define FD_BARFS 2 > > ... > > > > not being scalable. > > > > Do you have a complete list of filesystem types? Are you prepared to act > > as an Assigned Number authority for that list. For this kind of problem, > > strings are a damn sight easier to manage in the long term. > > Augh... It's ugly, indeed, but... sysctl() is not much nicer and all > systems in question manage to deal with it somehow. OTOH doing it as > strings... Hell knows. I'll look at it. Considering that HFS folks > had already asked for more than one value here (creator and type?) it may > be reasonable. I'm afraid that doing that may open the hell gates ;-/ > 'N' in *ANA can be 'namespace' as well as 'number'... Its a tough one alright. Some of my friends at Microsoft would suggest using UUIDs for this job. They might be clumsy but at least they are never going to collide and they are easy to generate. As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and has a string-based mechanism for exploring the sysctl tree. > > [1] > BTW, how does NetBSD deal with HFS forks? > > > [1] cue current flamew^Wthreads on l-k regarding files-as-directories > hell. :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 1:52:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 1419A14CEE for ; Mon, 28 Jun 1999 01:52:25 -0700 (PDT) (envelope-from a.reilly@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA14981 for ; Mon, 28 Jun 1999 18:52:23 +1000 (EST) X-BPC-Relay-Envelope-From: a.reilly@lake.com.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-48-172.nsw.bigpond.net.au [24.192.48.172]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id SAA02067 for ; Mon, 28 Jun 1999 18:52:22 +1000 (EST) Received: (qmail 13217 invoked by uid 1000); 27 Jun 1999 23:52:25 -0000 From: "Andrew Reilly" Date: Mon, 28 Jun 1999 09:52:25 +1000 To: Mike Smith Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: Beating system usage down Message-ID: <19990628095225.A2389@gurney.reilly.home> References: <19990624121816.A17448@trinsec.com> <199906241934.MAA01020@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906241934.MAA01020@dingo.cdrom.com>; from Mike Smith on Thu, Jun 24, 1999 at 12:34:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 24, 1999 at 12:34:06PM -0700, Mike Smith wrote: > > Just for those that have been following the benchmarking thread, this > is exactly the same symptom set that FreeBSD demonstrates when loaded > by WebBench. The gotcha here is, again, the giant kernel lock. Rather than trying to do the Solaris thing of mutexing everything, why don't we go in the opposite direction, and configure a multi-processor box as a cluster that happens to have really fast communications? Probably not as easy as it sounds, particularly since it would involve writing a "memory network" device driver, and some boot code to partition the main memory, and probably an extra layer of interrupt handling code, to hand device interrupts around. Er, yuck. It's just that it sounds as though it would be simpler to start with a blank sheet and a clean reentrant scheduling scheme, and graft pieces of FreeBSD back on top, than it would be to add that sort of functionality onto an existing traditionally structured Unix. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 2: 4: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E2C6153AE for ; Mon, 28 Jun 1999 02:04:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id CAA18676; Mon, 28 Jun 1999 02:03:41 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 02:03:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280903.CAA18676@apollo.backplane.com> To: "Daniel J. O'Connor" Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: RE: Implementation of mmap() in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Otherwise they wouldn't bother to use mmap and instead would use read() :> and write() :-) : :Hmm.. why (unless you forced mmap to use the address you gave it) would it not :choose the start address to be on a page boundary? : :--- :Daniel O'Connor software and network engineer Because we can't realign the data in the pages without doing a buffer copy. To force mmap() to align the data to the start of the page requires it to allocate memory and copy the in-core disk cache to the new memory. This is extremely wasteful of cpu and memory. The current UNIX mmap implementation is able to simply map the existing in-core disk cache directly to the process - no buffer copying is required at all, and it is extremely memory efficient. Programmers who use mmap() expect it to be as close to optimal as possible. Also, even if we were to realign the data, it would not deal with the end-of-data case. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 2: 6:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 6A77B1541C for ; Mon, 28 Jun 1999 02:06:01 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 67003 invoked by uid 1003); 28 Jun 1999 09:05:41 -0000 Date: Mon, 28 Jun 1999 11:05:41 +0200 From: Neil Blakey-Milner To: John Baldwin Cc: Aaron Smith , freebsd-hackers@FreeBSD.ORG, Sheldon Hearn Subject: Re: Inetd and wrapping. Message-ID: <19990628110541.A65857@rucus.ru.ac.za> References: <199906251244.FAA30357@sigma.veritas.com> <199906280226.WAA09596@smtp3.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199906280226.WAA09596@smtp3.erols.com>; from John Baldwin on Sun, Jun 27, 1999 at 10:26:34PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 1999-06-27 (22:26), John Baldwin wrote: > > if people have their undies in a wad over this, can't they compile > > inetd without LIBWRAP? > > Ahem.. > > Let's say I have two services, foo and bar, with food and > bard. I want to wrap food, but *NOT* bard and they are both in > /etc/inetd.conf. How do you propose to solve this with the internal > wrapping (which is a good idea, IMO as it eliminates an exec())? Run two copies of inetd? Seriously, if wrapping support can be tuned at runtime, and you can set up inetd to run with different configuration files (which you can), if those people who want to run both wrapped and non-wrapped services agree that this is an option, there needn't be a hack to do this sort of thing. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 2:45:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from the-village.bc.nu (lightning.swansea.uk.linux.org [194.168.151.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D87214C96 for ; Mon, 28 Jun 1999 02:44:55 -0700 (PDT) (envelope-from alan@lxorguk.ukuu.org.uk) Received: from alan by the-village.bc.nu with local (Exim 2.12 #1) id 10yXwO-0004oB-00; Mon, 28 Jun 1999 10:43:04 +0100 Subject: Re: Improving the Unix API To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 28 Jun 1999 10:43:03 +0100 (BST) Cc: viro@math.psu.edu, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: from "Doug Rabson" at Jun 28, 99 09:52:35 am Content-Type: text Content-Length: 343 Message-Id: From: Alan Cox Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and > has a string-based mechanism for exploring the sysctl tree. So we are actually both going the same way. Linus with /proc/sys and his official dislike of sysctl (Oh well I think sysctl using number spaces is the right idea - like snmp is), and BSD going to names To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 2:47: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 1176B14C96 for ; Mon, 28 Jun 1999 02:47:05 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 28 Jun 1999 11:50:07 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796AB@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Dan Seguin' , Ladavac Marino Cc: "Brian F. Feldman" , FreeBSD Hackers Subject: RE: Connect and so on.. Date: Mon, 28 Jun 1999 11:44:17 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Essentially, we're trying to mediate system calls. Read, Write, Open, > Socket calls from userland are caught, information about the calling > process (i.e. caller UID) are sent to an external source for > authorization and depending on the reply, the system call will proceed > or > not. This is the reason why the connection should be atomic and (so I > think) in the kernel. Can't have other calls going through in the > interim. [ML] If I understand this correctly, only the syscall which is being authenticated must block during the authentication. This makes the authentication atomic from the viewpoint of the syscall. The other processes/kernel supported threads may proceed. Sounds like RAGF(spelling?) scheme you're doing there. NFS daemon approach may be feasible for you, because this is exactly what it does. You have one central authentication daemon which is blocked in kernel syscall all the time, unless some other process (syscall) requests the authentication. The daemon then returns to user space, performs the neccessary authentication, and goes back into kernel with results. This is the way I would implement it, because it makes adding authentication schemes rather simple. [ML] /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3: 1:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9142C14CD1 for ; Mon, 28 Jun 1999 03:01:29 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA87884; Mon, 28 Jun 1999 11:00:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 28 Jun 1999 11:00:29 +0100 (BST) From: Doug Rabson To: Alan Cox Cc: viro@math.psu.edu, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Improving the Unix API 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 Mon, 28 Jun 1999, Alan Cox wrote: > > As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and > > has a string-based mechanism for exploring the sysctl tree. > > So we are actually both going the same way. Linus with /proc/sys and his > official dislike of sysctl (Oh well I think sysctl using number spaces is the > right idea - like snmp is), and BSD going to names As far as I know, only FreeBSD has a string-based sysctl implementation. Something which always confused me about Linux' procfs - what have all these kernel variables got to do with process state? We used to have a kernfs which was intended for this kind of thing but it rotted after people started extending sysctl for the purpose. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3: 2:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 0133915408 for ; Mon, 28 Jun 1999 03:02:23 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA14520; Mon, 28 Jun 1999 06:02:21 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA04557; Mon, 28 Jun 1999 06:02:20 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Mon, 28 Jun 1999 06:02:20 -0400 (EDT) From: Alexander Viro To: Alan Cox Cc: Doug Rabson , sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Improving the Unix API 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 Mon, 28 Jun 1999, Alan Cox wrote: > > As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and > > has a string-based mechanism for exploring the sysctl tree. > > So we are actually both going the same way. Linus with /proc/sys and his > official dislike of sysctl (Oh well I think sysctl using number spaces is the > right idea - like snmp is), and BSD going to names Yup. kernfs (we'ld also better keep it in a separate fs instead of cluttering procfs, but that's another story). OK, then. I've looked at it and it seems that strings will be easy to do (for new chflags, that is). For the time being I simply #define them to "vfs" and fs names - choosing decent names will wait until the thing will actually work ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:12:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from the-village.bc.nu (lightning.swansea.uk.linux.org [194.168.151.1]) by hub.freebsd.org (Postfix) with ESMTP id 815FC15285 for ; Mon, 28 Jun 1999 03:12:12 -0700 (PDT) (envelope-from alan@lxorguk.ukuu.org.uk) Received: from alan by the-village.bc.nu with local (Exim 2.12 #1) id 10yYMo-0004sP-00; Mon, 28 Jun 1999 11:10:22 +0100 Subject: Re: Improving the Unix API To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 28 Jun 1999 11:10:15 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk, viro@math.psu.edu, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: from "Doug Rabson" at Jun 28, 99 11:00:29 am Content-Type: text Content-Length: 567 Message-Id: From: Alan Cox Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as I know, only FreeBSD has a string-based sysctl implementation. Nod. > Something which always confused me about Linux' procfs - what have all > these kernel variables got to do with process state? We used to have a > kernfs which was intended for this kind of thing but it rotted after > people started extending sysctl for the purpose. About as much as having a /usr/bin for the slower binaries on the 40Mbyte moving head disk has relationship to /usr nowdays. /proc is basically both process and machine state in Linux. It got expaneded on. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:12:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id 14F3F15459 for ; Mon, 28 Jun 1999 03:12:46 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA14710; Mon, 28 Jun 1999 06:12:44 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA04566; Mon, 28 Jun 1999 06:12:44 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Mon, 28 Jun 1999 06:12:44 -0400 (EDT) From: Alexander Viro To: Doug Rabson Cc: Alan Cox , sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Improving the Unix API 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 Mon, 28 Jun 1999, Doug Rabson wrote: > As far as I know, only FreeBSD has a string-based sysctl implementation. > Something which always confused me about Linux' procfs - what have all > these kernel variables got to do with process state? We used to have a Nothing. procfs is a union of 4 filesystems. Historical reasons ;-/ There are: 1) /* - per-process stuff. Procfs proper. 2) sys/ - what kernfs should be. I.e. fs interface for sysctl tree. 3) openpromfs - sparc only (?), AFAICS not actively maintained. 4) the rest - mostly information advertised by drivers + kcore + kmsg, etc. Stuff that is not covered by sysctls (/dev/core is a symlink to /proc/kcore. 'nuff said.) They are different code-wise and ought to be separated. As soon as we'll have working unionfs (or at least non-opaque mount) they *will* be separated. > kernfs which was intended for this kind of thing but it rotted after > people started extending sysctl for the purpose. /proc/sys on Linux. It was stuffed into procfs because at that moment procfs was the only virtual filesystem (and because they shared some code). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:18: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m-net.arbornet.org (m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (Postfix) with ESMTP id F24E614C39 for ; Mon, 28 Jun 1999 03:17:59 -0700 (PDT) (envelope-from amol2@m-net.arbornet.org) Received: from localhost (amol2@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id FAA16670 for ; Mon, 28 Jun 1999 05:54:30 -0400 (EDT) Date: Mon, 28 Jun 1999 05:54:29 -0400 (EDT) From: Amol Mohite To: freebsd-hackers@FreeBSD.ORG Subject: environment strings In-Reply-To: <19990628084759.937F414F6C@hub.freebsd.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 Hi! i hope this is the right list for this qs. I wanted t know where the environment strings i bsd were stored after a program execs another one. Is there any place I ca get hold of the ABIs for freebsd ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:21:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 4737A14E43 for ; Mon, 28 Jun 1999 03:21:31 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA14303; Mon, 28 Jun 1999 06:22:00 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA19154; Mon, 28 Jun 1999 06:21:26 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id GAA76959; Mon, 28 Jun 1999 06:21:26 -0400 (EDT) Date: Mon, 28 Jun 1999 06:21:26 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906281021.GAA76959@lakes.dignus.com> To: rivers@dignus.com, ticso@cicely.de Subject: Re: setiathome crashes 3.2? Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19990628080407.A43878@cicely8.cicely.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Would everyone agree that it's not a "good thing" for a user-mode > > program to be able to lock up the OS? > > > There are severall resons. > One of them is that I got panics with a to high set MAXUSER in kernel options. > I don't know if it's a problem with 3.2. > The other possible reason might be a CPU overheating. CPUs used under FreeBSD > are typicall suspended during idle-time - when running seti or other permanent > running programms there is no idle time. I didn't know that. This laptop does have a fan for the P-75.... But, I don't believe it is that problem. You see, I can run it for about 5 minutes and *poof* - the machine is gone. > I asume there are several more possbilities. > But it sounds like there is something broken with your configuration. I think I'll need to put ddb in the kernel and see what's happening, since I get no panic or anything... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:21:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pizda.davem.net (adsl-216-101-162-242.dsl.snfc21.pacbell.net [216.101.162.242]) by hub.freebsd.org (Postfix) with ESMTP id C672115420 for ; Mon, 28 Jun 1999 03:21:47 -0700 (PDT) (envelope-from davem@redhat.com) Received: (from davem@localhost) by pizda.davem.net (8.9.3/8.9.3) id DAA09420; Mon, 28 Jun 1999 03:25:01 -0700 Date: Mon, 28 Jun 1999 03:25:01 -0700 Message-Id: <199906281025.DAA09420@pizda.davem.net> X-Authentication-Warning: pizda.davem.net: davem set sender to davem@redhat.com using -f From: "David S. Miller" To: viro@math.psu.edu Cc: dfr@nlsystems.com, alan@lxorguk.ukuu.org.uk, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org In-reply-to: (message from Alexander Viro on Mon, 28 Jun 1999 06:12:44 -0400 (EDT)) Subject: Re: Improving the Unix API References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Mon, 28 Jun 1999 06:12:44 -0400 (EDT) From: Alexander Viro 3) openpromfs - sparc only (?), AFAICS not actively maintained. Oh, it's maintained and used every day, believe me. Later, David S. Miller davem@redhat.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 3:29:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by hub.freebsd.org (Postfix) with ESMTP id EDF3F14C39 for ; Mon, 28 Jun 1999 03:29:19 -0700 (PDT) (envelope-from viro@math.psu.edu) Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA14913; Mon, 28 Jun 1999 06:29:17 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id GAA04594; Mon, 28 Jun 1999 06:29:08 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Mon, 28 Jun 1999 06:29:08 -0400 (EDT) From: Alexander Viro To: "David S. Miller" Cc: dfr@nlsystems.com, alan@lxorguk.ukuu.org.uk, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Improving the Unix API In-Reply-To: <199906281025.DAA09420@pizda.davem.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, 28 Jun 1999, David S. Miller wrote: > Date: Mon, 28 Jun 1999 06:12:44 -0400 (EDT) > From: Alexander Viro > > 3) openpromfs - sparc only (?), AFAICS not actively maintained. > > Oh, it's maintained and used every day, believe me. Cool ;-) There is a lot of stuff that is apparently not used in the main tree and vger CVS also gives zero. I'ld like to ask a couple of questions about that code, but let's take it to e-ma^W oh, hell... out of crossposting. And postpone till the evening - I'm going down now... Oh, dear... Integrating all this stuff when the page/buffer cache stuff will settle down is going to be something ;-/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 4:50:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oknodo.bof.de (oknodo.bof.de [195.4.223.10]) by hub.freebsd.org (Postfix) with ESMTP id 5E83B14E21 for ; Mon, 28 Jun 1999 04:50:39 -0700 (PDT) (envelope-from phbof@bof.de) Received: (from phbof@localhost) by oknodo.bof.de (8.8.8/8.8.8) id NAA02869; Mon, 28 Jun 1999 13:50:39 +0200 From: Patrick Schaaf Message-Id: <199906281150.NAA02869@oknodo.bof.de> Subject: Re: Improving the Unix API In-Reply-To: from Alan Cox at "Jun 28, 99 11:10:15 am" To: alan@lxorguk.ukuu.org.uk (Alan Cox) Date: Mon, 28 Jun 1999 13:50:39 +0200 (MEST) Cc: dfr@nlsystems.com, alan@lxorguk.ukuu.org.uk, viro@math.psu.edu, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org X-Mailer: ELM [version 2.4ME+ PL37 (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 > > Something which always confused me about Linux' procfs - what have all > > these kernel variables got to do with process state? We used to have a > > kernfs which was intended for this kind of thing but it rotted after > > people started extending sysctl for the purpose. > > About as much as having a /usr/bin for the slower binaries on the 40Mbyte > moving head disk has relationship to /usr nowdays. /proc is basically > both process and machine state in Linux. It got expaneded on. Maybe nobody noticed yet that 'proc' is an acronym, and has nothing to do with processes per se. Hmm. 'Portable Runtime Operation Control' might be a useful name expansion, alluding to the fact that the interface works across all supported platforms without byte order problems etc. :-) Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 6: 1:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from agamaweb.agama.ru (www.agama.com [195.94.226.130]) by hub.freebsd.org (Postfix) with SMTP id 04B0515064 for ; Mon, 28 Jun 1999 06:01:00 -0700 (PDT) (envelope-from andrey@agama.com) Received: from [195.94.226.144] by agamaweb.agama.com (NTMail 4.01.0008/NU2432.00.3e8112ca) with ESMTP id uiebaaaa for ; Mon, 28 Jun 1999 16:57:12 +0400 Message-ID: <37777289.8BE6C88E@agama.com> Date: Mon, 28 Jun 1999 17:03:05 +0400 From: Andrew Iltchenko Organization: AGAMA X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: Dynamic linking Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anyone know if it is possible to figure out the name of a shared object linked using the dlopen call, having only the address returned by dlopen? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 6:57:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 3353614DA6; Mon, 28 Jun 1999 06:57:26 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 28 Jun 1999 16:00:21 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796AE@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'freebsd-hackers@freebsd.org'" , "'freebsd-qestions@freebsd.org'" Subject: FreeBSD users in Vienna, AT Date: Mon, 28 Jun 1999 15:54:30 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone out there in Vienna area using/hacking on FreeBSD? How about a raid on Wiednerbrau this weekend? /Marino -- Marino Ladavac, Dipl.-Ing. Metropolitan Datenserviceges.m.b.H e-mail: mladavac@metropolitan.at GSM: +43 676 309 79 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 7:22:55 1999 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 21B9614C96 for ; Mon, 28 Jun 1999 07:22:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA92505; Mon, 28 Jun 1999 08:22:50 -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 IAA15190; Mon, 28 Jun 1999 08:21:12 -0600 (MDT) Message-Id: <199906281421.IAA15190@harmony.village.org> To: Julian Elischer Subject: Re: "restricted" kernel threads implementation from NetBSD via newconfig Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Jun 1999 23:34:22 PDT." References: Date: Mon, 28 Jun 1999 08:21:12 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Julian Elischer writes: : now this is threads within the kernel, and not kernel support for user : threads right? Yes. That's right. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 7:27:47 1999 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 1A3E314FC8 for ; Mon, 28 Jun 1999 07:27:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA92520; Mon, 28 Jun 1999 08:27:41 -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 IAA15234; Mon, 28 Jun 1999 08:26:03 -0600 (MDT) Message-Id: <199906281426.IAA15234@harmony.village.org> To: "Daniel J. O'Connor" Subject: Re: "restricted" kernel threads implementation from NetBSD via n Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Jun 1999 17:41:33 +0930." References: Date: Mon, 28 Jun 1999 08:26:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Daniel J. O'Connor" writes: : I don't suppose someone could post an explanation of how kernel threads work : could they? :) Looks like it just does a fork like thing so it can do context switches... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 9:28:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 4886614C01 for ; Mon, 28 Jun 1999 09:28:23 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id JAA20683; Mon, 28 Jun 1999 09:28:12 -0700 (PDT) Date: Mon, 28 Jun 1999 09:28:11 -0700 (PDT) From: Julian Elischer To: Warner Losh Cc: "Daniel J. O'Connor" , hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via n In-Reply-To: <199906281426.IAA15234@harmony.village.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 Mon, 28 Jun 1999, Warner Losh wrote: > In message "Daniel J. O'Connor" writes: > : I don't suppose someone could post an explanation of how kernel threads work > : could they? :) > > Looks like it just does a fork like thing so it can do context > switches... To be more precise, it should be more like a rfork() like thing that doesn't change any resources except the stack, a process structure and processor context. Specifically, processor VMspace is basically left at whatever it is already at, and there is no 'signal' stuff or file descriptor table munging. We might even allow the MMU to be left unchanged too. julian > > Warner > > > > 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 Jun 28 9:39:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id D75BB14E12 for ; Mon, 28 Jun 1999 09:39:41 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 221D483; Tue, 29 Jun 1999 00:39:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: "Daniel J. O'Connor" , hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via n In-reply-to: Your message of "Mon, 28 Jun 1999 08:26:02 CST." <199906281426.IAA15234@harmony.village.org> Date: Tue, 29 Jun 1999 00:39:41 +0800 From: Peter Wemm Message-Id: <19990628163941.221D483@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message "Daniel J. O'Connor" writ es: > : I don't suppose someone could post an explanation of how kernel threads wor k > : could they? :) > > Looks like it just does a fork like thing so it can do context > switches... > > Warner When I looked last time, it was effectively a callable interface to what we do from SYSINIT_KT(), ie: fork proc0, which runs in kernel space with it's own stack etc. kthread_create_deferred() is not really anything to do with those sort of threads. It's just a generic callback registration system that happens to be called after the basic processes have started so that proc0,1,2 etc are not disturbed. It's similar to the config_intrhook() stuff but is run later. You can probably cut/paste our SYSINIT_KT() code into some compatable function interfaces pretty easily to avoid yet another new file. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 10: 9:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norad.inetu.net (norad.inetu.net [206.245.188.72]) by hub.freebsd.org (Postfix) with ESMTP id AD0AF152E3 for ; Mon, 28 Jun 1999 10:09:50 -0700 (PDT) (envelope-from mark@inetu.net) Received: from localhost (maxiter@localhost) by norad.inetu.net (8.9.3/8.9.3) with ESMTP id NAA14382 for ; Mon, 28 Jun 1999 13:10:20 -0400 (EDT) Date: Mon, 28 Jun 1999 13:10:20 -0400 (EDT) From: Mark To: freebsd-hackers@freebsd.org Subject: panic: bwrite: buffer is not busy??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm recieving this error on a FreeBSD 2.2.x installation with an Adaptac 2940UW and a Seagate hard drive. I have a second machine with the exact same hardware and software setup which is also producing this error (with a lesser frequency). There are, unfortunately, several other machines with the same hardware and similar software which are not producing this error. For now, I'm looking for an explanation of what is error is and where it may be coming from. I found one question very similar to this in the archive, but alas, there was no reply. TIA! --------------------------------------------------- Mark Rekai - INetU, Inc.(tm) - http://www.INetU.net Electronic commerce - Web development - Web hosting Mark@INetU.net - Phone: (610) 266-7441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 10:51:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 50D2D14C33 for ; Mon, 28 Jun 1999 10:51:19 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA16543; Mon, 28 Jun 1999 13:54:56 -0400 (EDT) Date: Mon, 28 Jun 1999 12:54:54 -0500 (EST) From: Alfred Perlstein To: Andrew Iltchenko Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Dynamic linking In-Reply-To: <37777289.8BE6C88E@agama.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, 28 Jun 1999, Andrew Iltchenko wrote: > Hi, > > Does anyone know if it is possible to figure out the name of a shared > object linked using the dlopen call, having only the address returned by > dlopen? man dladdr tell me if this helps, thanks. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 10:56: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pinochet.cityline.ru (pinochet.cityline.ru [195.46.160.34]) by hub.freebsd.org (Postfix) with ESMTP id 9D1E015332 for ; Mon, 28 Jun 1999 10:56:01 -0700 (PDT) (envelope-from alfapri@cityline.ru) Received: from cityline.ru (ppp05-2-25.cityline.ru [195.46.162.25]) by pinochet.cityline.ru (8.9.2/t/08-Oct-1998) with ESMTP id VAA06536 for ; Mon, 28 Jun 1999 21:52:38 +0400 (MSD) Message-ID: <3777B74B.A4EA41E9@cityline.ru> Date: Mon, 28 Jun 1999 21:56:27 +0400 From: Alexey Ryndin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: unsubscribe Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 11:39:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id 6C4B414E00 for ; Mon, 28 Jun 1999 11:39:19 -0700 (PDT) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7) with SMTP id LAA01333; Mon, 28 Jun 1999 11:38:49 -0700 (PDT) Date: Mon, 28 Jun 1999 11:38:49 -0700 (PDT) From: Bill Studenmund To: Francois-Rene Rideau Cc: der Mouse , FreeBSD Hackers , NetBSD Kernel , OpenBSD Kernel , Linux Kernel Subject: Re: Improving the Unix API In-Reply-To: <19990628010446.A5377@ZhengHe.augustin.thierry> 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, 28 Jun 1999, Francois-Rene Rideau wrote: > On Sun, Jun 27, 1999 at 12:58:05PM -0400, der Mouse wrote: > > See NetBSD (and presumably other BSD) "mount -o update,rdonly" and/or > > "umount -f". (Last I tried, the latter didn't work as it should, but > > that's a matter of fixing bugs rather than introducing new features.) > If you re-read the original message, the problem is what to do > about processes with open file descriptors on the partition: > stop them at once? stop them at first file access? > block them instead? kill them? Will you do it atomically? > How will you allow for such large table-walking to be compatible > with real-time kernel response? [Hint: either use incremental > data-structures, or don't be atomic and be interruptible instead.] unmount -f is more intended for oh-sh*t situations. So harshness is ok. The way it's done is that all of the vnodes in that fs's vnode list get either vgone'd or vcleaned (in the -f case). This will have the effect of mapping them to deadfs vnodes, so all future access will either fail or do nothing (close works, read returns an error). There aren't any big table walks. :-) Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 11:45:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pinochet.cityline.ru (pinochet.cityline.ru [195.46.160.34]) by hub.freebsd.org (Postfix) with ESMTP id C4CB714E00 for ; Mon, 28 Jun 1999 11:45:44 -0700 (PDT) (envelope-from alfapri@cityline.ru) Received: from cityline.ru (ppp05-2-25.cityline.ru [195.46.162.25]) by pinochet.cityline.ru (8.9.2/t/08-Oct-1998) with ESMTP id WAA14737 for ; Mon, 28 Jun 1999 22:42:57 +0400 (MSD) Message-ID: <3777C31D.41A3957A@cityline.ru> Date: Mon, 28 Jun 1999 22:46:53 +0400 From: Alexey Ryndin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: unsubscribe Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 12:47: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 62BAE14FCB for ; Mon, 28 Jun 1999 12:46:39 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id PAA20468; Mon, 28 Jun 1999 15:34:15 -0400 Date: Mon, 28 Jun 1999 15:34:15 -0400 (EDT) From: Zhihui Zhang Reply-To: Zhihui Zhang To: Matthew Dillon Cc: "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: RE: Implementation of mmap() in FreeBSD In-Reply-To: <199906280903.CAA18676@apollo.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 > > Because we can't realign the data in the pages without doing a buffer > copy. To force mmap() to align the data to the start of the page requires > it to allocate memory and copy the in-core disk cache to the new memory. > > This is extremely wasteful of cpu and memory. The current UNIX mmap > implementation is able to simply map the existing in-core disk cache > directly to the process - no buffer copying is required at all, and > it is extremely memory efficient. I guess you are talking about VMIO buffers where the pages are found and registered into the buffer header during allocbuf(). When we do I/O on VMIO buffers using conventional system call method, we specify UIO_NOCOPY to instruct the uiomove() do not perform data copy. > Programmers who use mmap() expect it to be as close to optimal as > possible. I write a program to test the mmap() today. It turns out that a user can modify the part of the mmapped area that is within the system returned area but not part of the user-specified area. As I understand it, there are two access paths to a file: conventional I/O through read/write systems calls and memory-mapped I/O. Both of them converge at the vnode read and write routine (VOP_READ() and VOP_WRITE()). This should give us the opportunity to guard against illegal memory-mapped I/O writes made by the user. Maybe we can add some fields in the vm_object to record the real or user-specifed area which can be passed to the vnode read and write routine. In the vnode I/O routine, we should be able to limit the write to only the orginal part of the area specified by the user. This practice should not incur any performance loss. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 12:54:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BB19D15028 for ; Mon, 28 Jun 1999 12:54:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA24312; Mon, 28 Jun 1999 12:54:12 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 12:54:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199906281954.MAA24312@apollo.backplane.com> To: Zhihui Zhang Cc: "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: RE: Implementation of mmap() in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> it is extremely memory efficient. : :I guess you are talking about VMIO buffers where the pages are found and :registered into the buffer header during allocbuf(). When we do I/O on :VMIO buffers using conventional system call method, we specify UIO_NOCOPY :to instruct the uiomove() do not perform data copy. UIO_NOCOPY is used to handle a degenerate case in the VFS/BIO vs VM interaction for I/O, it has nothing to do with the read() or write() syscall per say, nor is it related to the mmap code. :> Programmers who use mmap() expect it to be as close to optimal as :> possible. : :I write a program to test the mmap() today. It turns out that a user can :modify the part of the mmapped area that is within the system returned :area but not part of the user-specified area. : :As I understand it, there are two access paths to a file: conventional I/O :through read/write systems calls and memory-mapped I/O. Both of them :converge at the vnode read and write routine (VOP_READ() and VOP_WRITE()). :This should give us the opportunity to guard against illegal memory-mapped :I/O writes made by the user. They converge in the VMIO page cache. :Maybe we can add some fields in the vm_object to record the real or :user-specifed area which can be passed to the vnode read and write :routine. In the vnode I/O routine, we should be able to limit the write to :only the orginal part of the area specified by the user. This practice :should not incur any performance loss. : :-Zhihui mmap bypasses the vnode. What you propose will not work because even if the VM object is process-specific, the pages underlying the VM object are not. If several processes are mmap()ing overlapping portions of the file, they are *sharing* the pages. So even though they are not sharing the VM object, the VM system will not be able to tell which process modified the page, and therefore any byte-ranged limits specified in the VM object will be useless. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 13:14: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id AF8081538C for ; Mon, 28 Jun 1999 13:13:47 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id QAA20625; Mon, 28 Jun 1999 16:01:42 -0400 Date: Mon, 28 Jun 1999 16:01:42 -0400 (EDT) From: Zhihui Zhang To: Matthew Dillon Cc: "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: RE: Implementation of mmap() in FreeBSD In-Reply-To: <199906281954.MAA24312@apollo.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 On Mon, 28 Jun 1999, Matthew Dillon wrote: > :> it is extremely memory efficient. > : > :I guess you are talking about VMIO buffers where the pages are found and > :registered into the buffer header during allocbuf(). When we do I/O on > :VMIO buffers using conventional system call method, we specify UIO_NOCOPY > :to instruct the uiomove() do not perform data copy. > > UIO_NOCOPY is used to handle a degenerate case in the VFS/BIO vs VM > interaction for I/O, it has nothing to do with the read() or write() > syscall per say, nor is it related to the mmap code. > > :> Programmers who use mmap() expect it to be as close to optimal as > :> possible. > : > :I write a program to test the mmap() today. It turns out that a user can > :modify the part of the mmapped area that is within the system returned > :area but not part of the user-specified area. > : > :As I understand it, there are two access paths to a file: conventional I/O > :through read/write systems calls and memory-mapped I/O. Both of them > :converge at the vnode read and write routine (VOP_READ() and VOP_WRITE()). > :This should give us the opportunity to guard against illegal memory-mapped > :I/O writes made by the user. > > They converge in the VMIO page cache. By converge, I mean VOP_GETPAGES() and VOP_PUTPAGES() will call VOP_READ() and VOP_WRITE() just as read() and write() system call. > > :Maybe we can add some fields in the vm_object to record the real or > :user-specifed area which can be passed to the vnode read and write > :routine. In the vnode I/O routine, we should be able to limit the write to > :only the orginal part of the area specified by the user. This practice > :should not incur any performance loss. > : > :-Zhihui > > mmap bypasses the vnode. What you propose will not work because even if > the VM object is process-specific, the pages underlying the VM object are > not. If several processes are mmap()ing overlapping portions of the file, > they are *sharing* the pages. So even though they are not sharing the > VM object, the VM system will not be able to tell which process modified > the page, and therefore any byte-ranged limits specified in the VM object > will be useless. This is a good point! I have never thought of it before. Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 13:21:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3CBE41543C for ; Mon, 28 Jun 1999 13:21:40 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-149.skylink.it [194.185.55.149]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA22521; Mon, 28 Jun 1999 22:20:55 +0200 Received: from brunte.ispra.webweaving.org (brunte.ispra.webweaving.org [10.0.0.12]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id UAA01266; Mon, 28 Jun 1999 20:21:07 GMT X-Passed: MX on Ispra.WebWeaving.org Mon, 28 Jun 1999 20:21:07 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 28 Jun 1999 20:21:07 GMT Date: Mon, 28 Jun 1999 22:28:04 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@brunte.ispra.webweaving.org To: freebsd-hackers@freebsd.org Cc: Dirk-Willem van Gulik Subject: RPLd or rplboot 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 Has anyone ever seen an open implementation of RPL, remote program load ? Or at paper specification of it against which one could write such a beast ? Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 14: 8: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 1929215478 for ; Mon, 28 Jun 1999 14:07:50 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id OAA22292; Mon, 28 Jun 1999 14:07:20 -0700 (PDT) Message-Id: <199906282107.OAA22292@lestat.nas.nasa.gov> To: Matthew Dillon Cc: Zhihui Zhang , "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: Implementation of mmap() in FreeBSD Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 28 Jun 1999 14:07:20 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999 12:54:12 -0700 (PDT) Matthew Dillon wrote: > mmap bypasses the vnode. What you propose will not work because even if > the VM object is process-specific, the pages underlying the VM object are > not. If several processes are mmap()ing overlapping portions of the file, > they are *sharing* the pages. So even though they are not sharing the > VM object, the VM system will not be able to tell which process modified > the page, and therefore any byte-ranged limits specified in the VM object > will be useless. Well, if you make a VM object map-entry-specific (not just "process-specific"; a single process may have multiple mappings of a file!), then the pages *can't* be shared, because pages are owned by the objects. The only reason you can share pages is because multiple map entries may reference the same object (the offset into the object being map-entry-specific). Put another way, it's not possible for this sentence to be true, at all: What you propose will not work because even if the VM object is process-specific, the pages underlying the VM object are not. ...since the presence of map-entry-specific objects would make the pages also map-entry-specific by definition. This, of course, would mean that VM objects themselves serve no purpose, so you could collapse it into "pages are owned by VM map entries", and do away with objects completely. However, that would be stupid. Anyhow, it's possible to have the semantics Zhihui suggested, but you have to give up an awful lot to get them. :-) -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 14:17:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5286C152F6 for ; Mon, 28 Jun 1999 14:17:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA24801; Mon, 28 Jun 1999 14:17:13 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 14:17:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199906282117.OAA24801@apollo.backplane.com> To: Jason Thorpe Cc: Zhihui Zhang , "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: Implementation of mmap() in FreeBSD References: <199906282107.OAA22292@lestat.nas.nasa.gov> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Well, if you make a VM object map-entry-specific (not just "process-specific"; :a single process may have multiple mappings of a file!), then the pages :*can't* be shared, because pages are owned by the objects. The only reason :you can share pages is because multiple map entries may reference the same :object (the offset into the object being map-entry-specific). : :Put another way, it's not possible for this sentence to be true, at all: : : What you propose will not work because even if the VM object is : process-specific, the pages underlying the VM object are not. There's missing information. Remember that VM objects are recursive. That is, they stack in layers. So, in fact, you are sharing the same physical page for both a PRIVATE and SHARED mmap. A copy only occurs if you attempt to modify a page in a PRIVATE mmap. The underlying VM object is, ultimately, the file itself. That's what I meant. You are absolute correct about the high-level mapping occuring in the map-entry. For a shared map it is ultimately the same VM object. :This, of course, would mean that VM objects themselves serve no purpose, so :you could collapse it into "pages are owned by VM map entries", and do away :with objects completely. : :However, that would be stupid. : :Anyhow, it's possible to have the semantics Zhihui suggested, but you have to :give up an awful lot to get them. :-) : : -- Jason R. Thorpe It really isn't possible without creating massive inefficiencies. It would be possible in a MULTICS system, but not in a UNIX system and not with most modern processors ( which do not have byte resolved variable-length page maps ). Not efficiently, anyway. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 14:22:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 866BB1538C for ; Mon, 28 Jun 1999 14:22:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA24829; Mon, 28 Jun 1999 14:22:47 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 14:22:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199906282122.OAA24829@apollo.backplane.com> To: Zhihui Zhang Cc: "Daniel J. O'Connor" , freebsd-hackers@FreeBSD.ORG, Ladavac Marino Subject: Re: RE: Implementation of mmap() in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :By converge, I mean VOP_GETPAGES() and VOP_PUTPAGES() will call VOP_READ() :and VOP_WRITE() just as read() and write() system call. Yes, but what they are doing is mapping the VMIO cache pages into the buffer, so the VOP_READ/VOP_WRITE essentially operates directly on the VMIO cache pages. This is why NOCOPY is set -- because there is no need to copy the data from the buffer to the VMIO cache because the buffer IS the VMIO cache at that point in time. Confusing, eh? A normal read() or write() syscall always copies the data, because the uio buffer in that case is not VMIO cache but instead some location in the processor's memory. Even if this location were associated with an mmap(), it would almost certainly be to a different file so the copy must occur anyway. A lot of the apparent confusion in the code is due to the fact that the code did not originally implemented a unified buffer cache. It is being slowly cleaned up. :-Zhihui -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 17: 0: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2C55D15483 for ; Mon, 28 Jun 1999 17:00:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01851; Mon, 28 Jun 1999 16:56:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906282356.QAA01851@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dirk-Willem van Gulik Cc: freebsd-hackers@freebsd.org Subject: Re: RPLd or rplboot In-reply-to: Your message of "Mon, 28 Jun 1999 22:28:04 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jun 1999 16:56:40 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anyone ever seen an open implementation of RPL, remote > program load ? Or at paper specification of it against > which one could write such a beast ? http://www.freebsd/org/~msmith/documents/RPL BTW, did you get your box? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19: 3:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 9D0E914BD7 for ; Mon, 28 Jun 1999 19:03:32 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id VAA21819 for ; Mon, 28 Jun 1999 21:51:29 -0400 Date: Mon, 28 Jun 1999 21:51:29 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: A way to crash system (3.1 & 3.2) with floppy 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 Suppose you have a *write-protected* DOS floppy and you do: # mount -t msdos /dev/fd0 /floppy <-- this is OK # cp somefile /floppy <-- a lot of error messages # umount /floppy <-- crash Now the system tries to sync the dirty buffers and fails. You have to press a key to reboot. Is there anything wrong here or FreeBSD simply does not handle this in a more elegant way? Thanks for any help. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19: 7:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 616D314D86 for ; Mon, 28 Jun 1999 19:06:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA21307; Tue, 29 Jun 1999 11:36:54 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA16110; Tue, 29 Jun 1999 09:56:59 +0930 (CST) Date: Tue, 29 Jun 1999 09:56:59 +0930 From: Greg Lehey To: Amol Mohite Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990629095659.B86806@freebie.lemis.com> References: <19990628084759.937F414F6C@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Amol Mohite on Mon, Jun 28, 1999 at 05:54:29AM -0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote: > > Hi! > > i hope this is the right list for this qs. > > I wanted t know where the environment strings i bsd were stored after a > program execs another one. At the top of memory. You can access them by the standard (but undocumented) method: int main (int argc, char *argv [], char *envp []) envp is a pointer to the environment strings. This is true for every version of UNIX I know. > Is there any place I ca get hold of the ABIs for freebsd ? Can you be more specific? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19:18:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 624A114C23 for ; Mon, 28 Jun 1999 19:18:07 -0700 (PDT) (envelope-from patrykz@mycenae.ilion.eu.org) Received: from mycenae.ilion.eu.org (patrykz@localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.2/8.9.2) with ESMTP id MAA29451 for ; Tue, 29 Jun 1999 12:18:07 +1000 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <199906290218.MAA29451@mycenae.ilion.eu.org> To: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-reply-to: Your message of "Tue, 29 Jun 1999 09:56:59 +0930." <19990629095659.B86806@freebie.lemis.com> Date: Tue, 29 Jun 1999 12:18:07 +1000 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I wanted t know where the environment strings i bsd were stored after a > > program execs another one. extern char **environ; > At the top of memory. You can access them by the standard (but > undocumented) method: > > int main (int argc, char *argv [], char *envp []) > > envp is a pointer to the environment strings. This is true for every > version of UNIX I know. This is of course correct except for the `undocumented' claim. The `envp' has been documented as the third argument to main() since the Pharaons (well, not quite ;). Apparently AT&T UNIX even has a (documented) five-parameter main(). Besides, the `envp' argument is a recommended extension in ISO/ANSI C, so you can hardly say that it's undocumented. l8r, patryk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19:26:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (Postfix) with ESMTP id 8F33514C23 for ; Mon, 28 Jun 1999 19:26:40 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.9.3/8.9.3) with ESMTP id VAA31113; Mon, 28 Jun 1999 21:30:05 -0400 X-Authentication-Warning: dragon.ham.muohio.edu: howardjp owned process doing -bs Date: Mon, 28 Jun 1999 21:30:05 -0400 (EDT) From: Jamie Howard X-Sender: howardjp@dragon.ham.muohio.edu To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy 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 Mon, 28 Jun 1999, Zhihui Zhang wrote: > Suppose you have a *write-protected* DOS floppy and you do: > > # mount -t msdos /dev/fd0 /floppy <-- this is OK > > # cp somefile /floppy <-- a lot of error messages > > # umount /floppy <-- crash > > Now the system tries to sync the dirty buffers and fails. You have to > press a key to reboot. > > Is there anything wrong here or FreeBSD simply does not handle this in a > more elegant way? > > Thanks for any help. I had this happen to me the other day on my 3.2 system. I thought it was just me because I had mounted the disk several days before and figured I had swapped it out. I also had to reformat the floppy on a Win95 system to make it usable again. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19:43:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 1B34515028 for ; Mon, 28 Jun 1999 19:43:16 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA21520; Tue, 29 Jun 1999 12:13:15 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA85918; Tue, 29 Jun 1999 12:13:13 +0930 (CST) Date: Tue, 29 Jun 1999 12:13:13 +0930 From: Greg Lehey To: Patryk Zadarnowski Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990629121313.B85121@freebie.lemis.com> References: <19990629095659.B86806@freebie.lemis.com> <199906290218.MAA29451@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906290218.MAA29451@mycenae.ilion.eu.org>; from Patryk Zadarnowski on Tue, Jun 29, 1999 at 12:18:07PM +1000 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote: > >>> I wanted t know where the environment strings i bsd were stored after a >>> program execs another one. > > extern char **environ; > >> At the top of memory. You can access them by the standard (but >> undocumented) method: >> >> int main (int argc, char *argv [], char *envp []) >> >> envp is a pointer to the environment strings. This is true for every >> version of UNIX I know. > > This is of course correct except for the `undocumented' claim. The > `envp' has been documented as the third argument to main() since the > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a > (documented) five-parameter main(). This is news to me. Can you point to the documentation? > Besides, the `envp' argument is a recommended extension in ISO/ANSI > C, so you can hardly say that it's undocumented. Hmm. I don't have the Standard here, but I've dug around and found a couple of references to the third parameter, an "optional extension". I think the real problem is that K&R didn't describe it: it was introduced in the Seventh Edition, which came after K&R. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19:55:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 6F48814FBE for ; Mon, 28 Jun 1999 19:55:15 -0700 (PDT) (envelope-from patrykz@mycenae.ilion.eu.org) Received: from mycenae.ilion.eu.org (patrykz@localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.2/8.9.2) with ESMTP id MAA29727; Tue, 29 Jun 1999 12:55:10 +1000 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <199906290255.MAA29727@mycenae.ilion.eu.org> To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-reply-to: Your message of "Tue, 29 Jun 1999 12:13:13 +0930." <19990629121313.B85121@freebie.lemis.com> Date: Tue, 29 Jun 1999 12:55:10 +1000 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is of course correct except for the `undocumented' claim. The > > `envp' has been documented as the third argument to main() since the > > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a > > (documented) five-parameter main(). > > This is news to me. Can you point to the documentation? I'll sniff around and get back to you (read: I'll ask our local guru on PDP-11's and other ancient rituals, who told me about those in the first place.) l8r, patryk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 19:59:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 1112514E39 for ; Mon, 28 Jun 1999 19:59:24 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA86269; Mon, 28 Jun 1999 22:58:26 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Mon, 28 Jun 1999 22:58:26 -0400 (EDT) From: Chuck Robey To: Greg Lehey Cc: Patryk Zadarnowski , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-Reply-To: <19990629121313.B85121@freebie.lemis.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, 29 Jun 1999, Greg Lehey wrote: > > This is of course correct except for the `undocumented' claim. The > > `envp' has been documented as the third argument to main() since the > > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a > > (documented) five-parameter main(). > > This is news to me. Can you point to the documentation? > > > Besides, the `envp' argument is a recommended extension in ISO/ANSI > > C, so you can hardly say that it's undocumented. > > Hmm. I don't have the Standard here, but I've dug around and found a > couple of references to the third parameter, an "optional extension". > I think the real problem is that K&R didn't describe it: it was > introduced in the Seventh Edition, which came after K&R. man 3 exec, I think. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 21:35:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m-net.arbornet.org (m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (Postfix) with ESMTP id D3E1F14D5B for ; Mon, 28 Jun 1999 21:34:58 -0700 (PDT) (envelope-from amol2@m-net.arbornet.org) Received: from localhost (amol2@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id XAA25539; Mon, 28 Jun 1999 23:32:59 -0400 (EDT) Date: Mon, 28 Jun 1999 23:32:59 -0400 (EDT) From: Amol Mohite To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-Reply-To: <19990629095659.B86806@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know about envp. What I want to know is the exact position of these variables on the stack. and if anywhere I can find some data, on the exact compisoition of the stcak, then it will be very helpful. references of books and websites wil be most helpful. amol > On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote: > > > > Hi! > > > > i hope this is the right list for this qs. > > > > I wanted t know where the environment strings i bsd were stored after a > > program execs another one. > > At the top of memory. You can access them by the standard (but > undocumented) method: > > int main (int argc, char *argv [], char *envp []) > > envp is a pointer to the environment strings. This is true for every > version of UNIX I know. > > > Is there any place I ca get hold of the ABIs for freebsd ? > > Can you be more specific? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 21:41: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 7E5C414D67 for ; Mon, 28 Jun 1999 21:41:02 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA22107; Tue, 29 Jun 1999 14:11:00 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA88989; Tue, 29 Jun 1999 14:10:58 +0930 (CST) Date: Tue, 29 Jun 1999 14:10:57 +0930 From: Greg Lehey To: Amol Mohite Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990629141057.I85121@freebie.lemis.com> References: <19990629095659.B86806@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Amol Mohite on Mon, Jun 28, 1999 at 11:32:59PM -0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote: >> On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote: >>> >>> Hi! >>> >>> i hope this is the right list for this qs. >>> >>> I wanted t know where the environment strings i bsd were stored after a >>> program execs another one. >> >> At the top of memory. You can access them by the standard (but >> undocumented) method: >> >> int main (int argc, char *argv [], char *envp []) >> >> envp is a pointer to the environment strings. This is true for every >> version of UNIX I know. >> >>> Is there any place I ca get hold of the ABIs for freebsd ? >> >> Can you be more specific? > > I know about envp. > > What I want to know is the exact position of these variables on the stack. As I said, at the top. > and if anywhere I can find some data, on the exact compisoition of > the stcak, then it will be very helpful. > > references of books and websites wil be most helpful. I think that, for FreeBSD, the source is the only place you'll find it. There's a brief description in "Porting UNIX Software" (http://www.ora.com/catalog/port/noframes.html), but that's not specific to FreeBSD. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 21:45:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 491AD14D67 for ; Mon, 28 Jun 1999 21:45:25 -0700 (PDT) (envelope-from patrykz@mycenae.ilion.eu.org) Received: from mycenae.ilion.eu.org (patrykz@localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.2/8.9.2) with ESMTP id OAA30104; Tue, 29 Jun 1999 14:44:40 +1000 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <199906290444.OAA30104@mycenae.ilion.eu.org> To: Amol Mohite Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-reply-to: Your message of "Mon, 28 Jun 1999 23:32:59 -0400." Date: Tue, 29 Jun 1999 14:44:39 +1000 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I know about envp. > > What I want to know is the exact position of these variables on the stack. > > and if anywhere I can find some data, on the exact compisoition of the > stcak, then it will be very helpful. > > references of books and websites wil be most helpful. Basically, i386 BSD kernels (you're after i386, aren't you?) point ESP to the following "struct" (which means that it will be dumped at the very top of the address space) struct kframe { int argc; /* "argc" to be passed to main() */ char *argv[argc]; /* "argv" to be passed to main() */ char *null; /* a NULL pointer terminating argv[] */ char **envp; /* value to be assigned to "environ" */ }; /usr/src/lib/csu/i386/crt0.c is probably the best reference you can get your hands on ;) Patryk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 21:48:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id CE83314D67 for ; Mon, 28 Jun 1999 21:48:33 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA22136; Tue, 29 Jun 1999 14:18:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA89139; Tue, 29 Jun 1999 14:18:30 +0930 (CST) Date: Tue, 29 Jun 1999 14:18:30 +0930 From: Greg Lehey To: Patryk Zadarnowski Cc: Amol Mohite , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990629141830.J85121@freebie.lemis.com> References: <199906290444.OAA30104@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906290444.OAA30104@mycenae.ilion.eu.org>; from Patryk Zadarnowski on Tue, Jun 29, 1999 at 02:44:39PM +1000 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 29 June 1999 at 14:44:39 +1000, Patryk Zadarnowski wrote: > >> I know about envp. >> >> What I want to know is the exact position of these variables on the stack. >> >> and if anywhere I can find some data, on the exact compisoition of the >> stcak, then it will be very helpful. >> >> references of books and websites wil be most helpful. > > Basically, i386 BSD kernels (you're after i386, aren't you?) point ESP to > the following "struct" (which means that it will be dumped at the very > top of the address space) > > struct kframe { > int argc; /* "argc" to be passed to main() */ > char *argv[argc]; /* "argv" to be passed to main() */ > char *null; /* a NULL pointer terminating argv[] */ > char **envp; /* value to be assigned to "environ" */ > }; In fact, the environment strings are at the very top, followed by the arguments, followed by this structure. But I suppose that's what you meant to say. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 22: 0:33 1999 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 CAEFB14DDC for ; Mon, 28 Jun 1999 22:00:29 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA94846; Mon, 28 Jun 1999 23:00:28 -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 WAA19339; Mon, 28 Jun 1999 22:58:56 -0600 (MDT) Message-Id: <199906290458.WAA19339@harmony.village.org> To: "Daniel J. O'Connor" Subject: Re: "restricted" kernel threads implementation from NetBSD via n Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Jun 1999 17:41:33 +0930." References: Date: Mon, 28 Jun 1999 22:58:56 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Daniel J. O'Connor" writes: : I don't suppose someone could post an explanation of how kernel threads work : could they? :) In a nutshell, it appears to basically do an rfork. It then becomes like any other process that is interrupted in the kernel... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 28 22:19:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B06BE15108 for ; Mon, 28 Jun 1999 22:19:54 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA25692; Mon, 28 Jun 1999 23:19:33 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <37785764.F63593AE@softweyr.com> Date: Mon, 28 Jun 1999 23:19:32 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Patryk Zadarnowski , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings References: <19990629095659.B86806@freebie.lemis.com> <199906290218.MAA29451@mycenae.ilion.eu.org> <19990629121313.B85121@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote: > > > > This is of course correct except for the `undocumented' claim. The > > `envp' has been documented as the third argument to main() since the > > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a > > (documented) five-parameter main(). > > This is news to me. Can you point to the documentation? > > > Besides, the `envp' argument is a recommended extension in ISO/ANSI > > C, so you can hardly say that it's undocumented. > > Hmm. I don't have the Standard here, but I've dug around and found a > couple of references to the third parameter, an "optional extension". > I think the real problem is that K&R didn't describe it: it was > introduced in the Seventh Edition, which came after K&R. Time for a main() man page? Where would it go? Section 2, 3, or 9? Hmm... -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 0:39:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from balsam.methow.com (balsam.methow.com [206.107.156.5]) by hub.freebsd.org (Postfix) with SMTP id 77C5114E94 for ; Tue, 29 Jun 1999 00:39:46 -0700 (PDT) (envelope-from tcole@balsam.methow.com) Received: (qmail 28686 invoked by uid 535); 29 Jun 1999 07:39:45 -0000 Message-ID: <19990629003945.A28540@wcug.wwu.edu> Date: Tue, 29 Jun 1999 00:39:45 -0700 From: Travis Cole To: Jamie Howard , Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Jamie Howard on Mon, Jun 28, 1999 at 09:30:05PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 28, 1999 at 09:30:05PM -0400, Jamie Howard wrote: > On Mon, 28 Jun 1999, Zhihui Zhang wrote: > > > Suppose you have a *write-protected* DOS floppy and you do: > > > > # mount -t msdos /dev/fd0 /floppy <-- this is OK > > > > # cp somefile /floppy <-- a lot of error messages > > > > # umount /floppy <-- crash > > > > Now the system tries to sync the dirty buffers and fails. You have to > > press a key to reboot. > > > > Is there anything wrong here or FreeBSD simply does not handle this in a > > more elegant way? > > > > Thanks for any help. > > I had this happen to me the other day on my 3.2 system. I thought it was > just me because I had mounted the disk several days before and figured I > had swapped it out. I also had to reformat the floppy on a Win95 system > to make it usable again. > > Jamie I just reproduced this on a system running 4.0-CURRENT from about Sun Jun 27 01:12:42 PDT I got a ton of these errors in dmesg and /var/log/messages: Jun 29 00:17:53 marx /kernel: fd0c: hard error writing fsbn 19 (ST0 40 ST1 2 ST2 0 cyl 0 hd 1 sec 2) And it let me try several umount commands and even a umount -f. None of them actualy umounted the floppy drive and it completly reboot my computer after about 2 or 3 mins. No panic or anything. Once second I'm looking at X, next second I'm looking at my BIOS bootup screen. -- --Travis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 0:46:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id A639814E94 for ; Tue, 29 Jun 1999 00:46:48 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA04091; Tue, 29 Jun 1999 17:16:46 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA26843; Tue, 29 Jun 1999 17:16:45 +0930 Date: Tue, 29 Jun 1999 17:16:45 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Mark Cc: freebsd-hackers@freebsd.org Subject: Re: panic: bwrite: buffer is not busy??? 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 Mon, 28 Jun 1999, Mark wrote: > For now, I'm looking for an explanation of what is error is and where it > may be coming from. I found one question very similar to this in the > archive, but alas, there was no reply. You didn't post any information which might help a developer track down your problem - heck, you didn't even specify the version you're running (there's no version called '2.2.x' :-). See the handbook. Kris ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 2:51: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 284CF14D69 for ; Tue, 29 Jun 1999 02:50:59 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id FAA20217; Tue, 29 Jun 1999 05:49:05 -0400 (EDT) Date: Tue, 29 Jun 1999 05:49:04 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Greg Lehey Cc: Amol Mohite , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-Reply-To: <19990629141057.I85121@freebie.lemis.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, 29 Jun 1999, Greg Lehey wrote: > On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote: > > What I want to know is the exact position of these variables on the stack. > > As I said, at the top. > > > and if anywhere I can find some data, on the exact compisoition of > > the stcak, then it will be very helpful. > > > > references of books and websites wil be most helpful. > > I think that, for FreeBSD, the source is the only place you'll find > it. There's a brief description in "Porting UNIX Software" > (http://www.ora.com/catalog/port/noframes.html), but that's not > specific to FreeBSD. That's not true, Greg. I'm sure you of all people know that it (the composition of address space) is described in "The Design and Implementation of the 4.4BSD Operating System," even if things are slightly different in FreeBSD of today (especially addresses.) > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Jun 29 2:53:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BD3C114BE7 for ; Tue, 29 Jun 1999 02:53:50 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA22911; Tue, 29 Jun 1999 19:23:47 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA71637; Tue, 29 Jun 1999 19:23:47 +0930 (CST) Date: Tue, 29 Jun 1999 19:23:47 +0930 From: Greg Lehey To: "Brian F. Feldman" Cc: Amol Mohite , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990629192347.O85121@freebie.lemis.com> References: <19990629141057.I85121@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Tue, Jun 29, 1999 at 05:49:04AM -0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 29 June 1999 at 5:49:04 -0400, Brian F. Feldman wrote: > On Tue, 29 Jun 1999, Greg Lehey wrote: > >> On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote: >>> What I want to know is the exact position of these variables on the stack. >> >> As I said, at the top. >> >>> and if anywhere I can find some data, on the exact compisoition of >>> the stcak, then it will be very helpful. >>> >>> references of books and websites wil be most helpful. >> >> I think that, for FreeBSD, the source is the only place you'll find >> it. There's a brief description in "Porting UNIX Software" >> (http://www.ora.com/catalog/port/noframes.html), but that's not >> specific to FreeBSD. > > That's not true, Greg. I'm sure you of all people know that it (the > composition of address space) is described in "The Design and > Implementation of the 4.4BSD Operating System," even if things > are slightly different in FreeBSD of today (especially addresses.) Well, no, it's true. I wrote "I think that...". Yes, you're correct, it's described on page 62 of "The Design and Implementation of the 4.4BSD Operating System,", but that has little bearing on what I thought at the time (though, of course, it has significant bearing on what I think now :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 2:56:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7E99714BF9 for ; Tue, 29 Jun 1999 02:56:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id FAA20364; Tue, 29 Jun 1999 05:56:37 -0400 (EDT) Date: Tue, 29 Jun 1999 05:56:37 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Greg Lehey Cc: Amol Mohite , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Brian F. Feldman wrote: > > That's not true, Greg. I'm sure you of all people know that it (the > composition of address space) is described in "The Design and > Implementation of the 4.4BSD Operating System," even if things > are slightly different in FreeBSD of today (especially addresses.) Should we expect to see something similar in the next revision of your book? Describing this would be nice, because lots of people get curious about this :) Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Jun 29 3:39:28 1999 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 B86CF14C39 for ; Tue, 29 Jun 1999 03:37:07 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA01519 for ; Tue, 29 Jun 1999 17:36:38 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 29 Jun 1999 17:36:38 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: dlopen returns non NULL 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! in the following code `dlopen' returns NULL on the first iteration (because g() is not defined) -- it's ok but on the second iteration `dlopen' returns "valid" dlh I need the code like this to load some functions dynamically. The code below shows that it's unable to ensure that all the symbols in .so to be loaded can be properly resolved AND try again (with recompiled module) if dlopen fails first time. Any suggestions? --- cut here (Makefile) --- CFLAGS = -g all: dl.so main4 dl.so: dl.c gcc -o dl.so $(CFLAGS) -shared -fpic -fPIC dl.c main4: main4.o gcc -o main4 -export-dynamic main4.o clean: rm -f dl.so main4.o --- cut here --- --- cut here (dl.c) --- #include void f() { printf("Hello, world!\n"); g(); } --- cut here --- --- cut here (main4.c) --- #include #include #include main() { void *dlh = NULL; void (*f)(void); for (;;) { getchar(); if (dlh != NULL) { dlclose(dlh); dlh = NULL; } dlh = dlopen("./dl.so", RTLD_NOW); if (dlh == NULL) { fprintf(stderr, "dlopen: %s\n", dlerror()); continue; } f = dlsym(dlh, "f"); if (f == NULL) { fprintf(stderr, "dlsym: %s\n", dlerror()); dlh = NULL; continue; } f(); } dlclose(dlh); return 0; } --- cut here --- /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 5:58:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bigbird.telly.org (bigbird.telly.org [198.53.146.159]) by hub.freebsd.org (Postfix) with ESMTP id B780514EAB for ; Tue, 29 Jun 1999 05:58:50 -0700 (PDT) (envelope-from evan@telly.org) Received: from bigbird.telly.org ([204.187.86.5]) by bigbird.telly.org with esmtp (Exim 2.02 #2) id 10yxTC-0001Ak-00 for hackers@freebsd.org; Tue, 29 Jun 1999 08:58:38 -0400 Date: Tue, 29 Jun 1999 08:58:38 -0400 (EDT) From: Evan Leibovitch To: hackers@freebsd.org Subject: A portable version of 'sar' 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 In an attempt to improve the abiility of free-software operating systems' ability to report on their performance, I (and some other people at my company, Starnix) have started a project to create an open version of the System V program "sar". Furthermore, we've been able to convince SCO -- current owner of the "official" Unix code -- to open up the actual code to 'sar': http://www.sco.com/press/releases/1999/6868.html It's our intention to keep "osar" as portable as possible, and we can certainly use some help with people who are familiar with the ability to extract performance information from the BSD kernel. Please have a look at the website for this project at http://www.starnix.com/osar/ , and join the associated mailing list if interested. Thanks! - Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 6:48:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id A1DB614DB9 for ; Tue, 29 Jun 1999 06:48:10 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id JAA53461 for ; Tue, 29 Jun 1999 09:48:09 -0400 (EDT) Message-Id: <199906291348.JAA53461@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: bug in latests NFS patches for -stable Date: Tue, 29 Jun 1999 09:48:08 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a small by critical error in the latest patches which causes the server to never transmit a response packet back to the client in certain conditions on a nfs create RPC. Below is the updated NFS3 patch. If jullian could take this for review and place it at the "official" unoffical URL it would be muchly appreciated :) It is a one line patch. http://www.cs.rpi.edu/~crossd/FreeBSD/nfspatch3a.diff -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 6:50:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from canolog.ninthwonder.com (canolog.ninthwonder.com [151.199.66.142]) by hub.freebsd.org (Postfix) with SMTP id 1476114DB9 for ; Tue, 29 Jun 1999 06:50:40 -0700 (PDT) (envelope-from briggs@canolog.ninthwonder.com) Received: (qmail 23104 invoked by uid 69); 29 Jun 1999 13:50:38 -0000 Date: Tue, 29 Jun 1999 09:50:38 -0400 From: Allen Briggs To: Alexander Viro Cc: Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Subject: Re: Improving the Unix API Message-ID: <19990629095038.K1063@canolog.ninthwonder.com> Mail-Followup-To: Alexander Viro , Francois-Rene Rideau , Linux Kernel , FreeBSD Hackers , NetBSD Kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, I'd argue that Berkeley defined a bunch of VFS attributes, and > > then implemented them natively in UFS and LFS; other non-native > > filesystems have to map their concepts of other file attributes (e.g., > > dates, permissions, etc.,) into the native VFS concepts. > > Right. Except that UFS has not only generic attibutes. For example, > you have UF_NODUMP and SF_ARCHIVED. The *only* place in the /sys you > mention the former is sys/stat.h (BTW, you don't even map it on > EXT2_NODUMP_FL). The latter is mentioned only in the msdosfs/msdosfs_vnops.c. > Hardly a VFS flag, right? It sounds like the implementation is what you are complaining about here, not the design or the interface. If I understand you correctly, the level argument in the proposed API is used to extend the namespace for the attributes. Do you see a real need right now to extend your namespace this way? It seems to provide more room for error on the programmer's side by increasing the complexity (albeit not much) of the function/system call. Additionally, using the same name as the BSD entry point but changing the calling conventions could confuse programmers who use both systems and even if it doesn't confuse them, it's an additional thing that they have to keep in mind when writing portable software. I think we should be working in the other direction--reducing the differences between the systems and making it easier to write portable software. Maybe that's just me, though... ;-) -allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 9:18:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 1B5F515267 for ; Tue, 29 Jun 1999 09:18:30 -0700 (PDT) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 8CFE8248; Tue, 29 Jun 1999 12:18:29 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id 7C4DF244 for ; Tue, 29 Jun 1999 12:18:29 -0400 (EDT) Date: Tue, 29 Jun 1999 12:18:29 -0400 (EDT) From: David Miller Reply-To: David Miller To: freebsd-hackers@freebsd.org Subject: DVD-ram 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 Apologies if this should be on -scsi.... Has anyone done any work with dvd-ram drives under FreeBSD? I will soon need to duplicate dvd-ram media and would very much like to do it under unix. All I need to start with is the ability to read/write the raw device. Currently the drive is recognized as cd0 (FreeBSD 3.2) and I can read a 2.x GB side but not, of course, write it. I'm looking at cdrecord for clues but would like not to reinvent someone elses work. Thanks in advance, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 11:52:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.pingnet.ch (luna.pingnet.ch [194.148.8.14]) by hub.freebsd.org (Postfix) with ESMTP id DE03B14F95 for ; Tue, 29 Jun 1999 11:52:38 -0700 (PDT) (envelope-from mgilly@bonsai-studio.com) Received: from [192.168.1.2] (pop-ls-10-1-dialup-109.freesurf.ch [194.230.20.109]) by luna.pingnet.ch (8.9.3/8.9.3) with ESMTP id SAA21433 for ; Tue, 29 Jun 1999 18:55:39 GMT Message-Id: <199906291855.SAA21433@luna.pingnet.ch> X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Date: Tue, 29 Jun 1999 20:51:33 +0000 Subject: Redundant Remote Webserver clustering From: "Miguel Gilly" To: hackers@freebsd.org Mime-version: 1.0 X-Priority: 3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bonsai Studio: Web Design and More http://www.bonsai-studio.com Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Dear Sirs, I would find it extremely helpful if FreeBSD could offer redundant clustering capabilities for ISP applications. Nowadays I feel that it is a far better choice to choose a x86 Unix cluster over the expensive Sun/SGI SMP servers. I found some affordable tools for Linux, but almost nothing for FreeBSD. I feel such an ability would raise the value a lot of FreeBSD. Kind regards Miguel Gilly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 11:53: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 7497C15403 for ; Tue, 29 Jun 1999 11:53:00 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 61110 invoked from network); 29 Jun 1999 18:53:00 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 29 Jun 1999 18:53:00 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id NAA01639; Tue, 29 Jun 1999 13:52:56 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Tue, 29 Jun 1999 13:52:56 -0500 (CDT) From: David Scheidt To: Travis Cole Cc: Jamie Howard , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy In-Reply-To: <19990629003945.A28540@wcug.wwu.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 Tue, 29 Jun 1999, Travis Cole wrote: > On Mon, Jun 28, 1999 at 09:30:05PM -0400, Jamie Howard wrote: > > On Mon, 28 Jun 1999, Zhihui Zhang wrote: > > > > I just reproduced this on a system running 4.0-CURRENT from about > Sun Jun 27 01:12:42 PDT > > I got a ton of these errors in dmesg and /var/log/messages: > Jun 29 00:17:53 marx /kernel: fd0c: hard error writing fsbn 19 (ST0 40 ST1 2 ST2 0 cyl 0 hd 1 sec 2) > > And it let me try several umount commands and even a umount -f. None > of them actualy umounted the floppy drive and it completly reboot my computer > after about 2 or 3 mins. No panic or anything. Once second I'm looking at X, I can do this from -CURRENT from whenever CTM broke. I have a panic, and a dump which i havne't had time to look at. The panic string is panic: vinvalbuf: dirty bufs David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 12:49:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id 38E4D14A0B for ; Tue, 29 Jun 1999 12:49:37 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id PAA25969; Tue, 29 Jun 1999 15:49:21 -0400 (EDT) To: "Miguel Gilly" Cc: hackers@FreeBSD.ORG Subject: Re: Redundant Remote Webserver clustering References: <199906291855.SAA21433@luna.pingnet.ch> User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.3 (i386-pc-solaris2.7) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII From: Chris Shenton Date: 29 Jun 1999 15:49:21 -0400 In-Reply-To: "Miguel Gilly"'s message of "Tue, 29 Jun 1999 20:51:33 +0000" Message-ID: Lines: 36 X-Mailer: Gnus v5.6.45/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999 20:51:33 +0000, "Miguel Gilly" said: Miguel> I would find it extremely helpful if FreeBSD could offer Miguel> redundant clustering capabilities for ISP applications. Miguel> Nowadays I feel that it is a far better choice to choose a x86 Miguel> Unix cluster over the expensive Sun/SGI SMP servers. Miguel> I found some affordable tools for Linux, but almost nothing Miguel> for FreeBSD. I feel such an ability would raise the value a Miguel> lot of FreeBSD. If you're talking true close-coupled clustering, my reply's not gonna help :-( If you're talking about web-type servers, read on... Have you checked www.EddieWare.org? It's a (web) load balancer and dynamic DNS, performing somewhat similar functions to commercial products from RND Networks, F5 Labs, Foundry, IPivot, Alteon, etc. Runs on Solaris, FreeBSD, Linux, and recently NT . I'm just getting into it now, as the F5 folks want an absurd $27K for a single dynamic DNS (two required), and I think their $15K each balancers are a bit high, since it's SW running on BSDI boxes (previously FreeBSD!) running on commodity hardware. I'm not saying the boxes aren't worth it -- what I've seen works great, has a command line interface, seems secure, and even the GUI's good. But I think the Eddie project on FreeBSD would give you 90% of that -- open source. My big thing these days is fault tolerance: at the server level, at the (web) farm level, and at the colo/datacenter level. If I can get that then I can sleep easy while the back-hoes do their work... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 13:42: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cserv.oksys.bg (ipp-8-056-sofia.ttm.bg [195.230.8.56]) by hub.freebsd.org (Postfix) with ESMTP id 7054514EB5 for ; Tue, 29 Jun 1999 13:41:45 -0700 (PDT) (envelope-from ian@bulinfo.net) Received: from bulinfo.net (ian@localhost [127.0.0.1]) by cserv.oksys.bg (8.9.3/8.9.3) with ESMTP id XAA94422; Tue, 29 Jun 1999 23:41:07 +0300 (EEST) (envelope-from ian@bulinfo.net) Message-ID: <37792F62.7CF2AB94@bulinfo.net> Date: Tue, 29 Jun 1999 23:41:06 +0300 From: Iani Brankov Organization: ok systems X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Scheidt , hackers@freebsd.org Subject: Re: A way to crash system (3.1 & 3.2) with floppy References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: [snip] > I can do this from -CURRENT from whenever CTM broke. I have a panic, and a > dump which i havne't had time to look at. The panic string is > panic: vinvalbuf: dirty bufs I know that's not the right mail list, but i feel (not sure) the fdc driver has probems sometimes. I tried using fdformat on a 1200k floppy and the kernel filled my screen with error messages. After that I formatted this diskette in the same drive, the same computer, but under windoze. -iani To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 15:11:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 3A18115242 for ; Tue, 29 Jun 1999 15:11:31 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 43446 invoked from network); 29 Jun 1999 22:11:27 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 29 Jun 1999 22:11:27 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id RAA33900; Tue, 29 Jun 1999 17:11:26 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Tue, 29 Jun 1999 17:11:26 -0500 (CDT) From: David Scheidt To: Travis Cole Cc: Jamie Howard , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, David Scheidt wrote: > I can do this from -CURRENT from whenever CTM broke. I have a panic, and a > dump which i havne't had time to look at. The panic string is > panic: vinvalbuf: dirty bufs > > David > And the dump shows....nothing: rally3# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.8 (kgdb) core-file /var/crash/vmcore.8 IdlePTD 2875392 initial pcb at 250320 panicstr: vinvalbuf: dirty bufs panic messages: --- panic: vinvalbuf: dirty bufs syncing disks... 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 giving up dumping to dev (0,131073), offset 256385 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 #1 0xc0130d40 in boot (howto=0) at ../../kern/kern_shutdown.c:290 Anything else Ishould look for? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 15:50: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (Postfix) with ESMTP id ABD69152CE; Tue, 29 Jun 1999 15:49:59 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id SAA06740; Tue, 29 Jun 1999 18:54:06 -0400 (EDT) (envelope-from billf@jade.chc-chimes.com) Date: Tue, 29 Jun 1999 18:54:06 -0400 (EDT) From: Bill Fumerola To: hackers@FreeBSD.org Subject: tcpdump(1) additions. 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 [bcc to committers, replys to hackers] Unless there is strong feelings against it, I'd like to commit the smb patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). Comments? - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Tue Jun 29 15:55:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 8E5FB152B9 for ; Tue, 29 Jun 1999 15:55:24 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id SAA20188; Tue, 29 Jun 1999 18:55:16 -0400 (EDT) Date: Tue, 29 Jun 1999 18:55:15 -0400 (EDT) From: "Matthew N. Dodd" To: Bill Fumerola Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Bill Fumerola wrote: > [bcc to committers, replys to hackers] > > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). I'm very much for this as it doesn't make a great deal of sense to have 3 different tcpdump binaries floating around with small differences in their feature sets. We already have local modifications to the in-tree tcpdump (tokenring) and as its imported with vendor tags it shouldn't be all that difficult to reconcile local changes with whatever the next release brings us. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 16:43: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fasterix.frmug.org (d066.paris-81.cybercable.fr [212.198.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 49D92151AD for ; Tue, 29 Jun 1999 16:42:53 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id BAA19746; Wed, 30 Jun 1999 01:42:34 +0200 (CEST) Message-ID: <19990630014234.A18559@fasterix.frmug.fr.net> Date: Wed, 30 Jun 1999 01:42:34 +0200 From: Pierre Beyssac To: Bill Fumerola , hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: ; from Bill Fumerola on Tue, Jun 29, 1999 at 06:54:06PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 29, 1999 at 06:54:06PM -0400, Bill Fumerola wrote: > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) Could you elaborate some more about the SMB patches? I've been to www.samba.org but it's not obvious to me what's in there for FreeBSD (except for samba itself). > and ipsec/ike patches (recently mailed > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). > > Comments? The IPSEC/IKE stuff for tcpdump seems like a great thing to have! -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 16:45: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 1F7A0151AD for ; Tue, 29 Jun 1999 16:45:05 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA11401; Wed, 30 Jun 1999 09:15:03 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA29153; Wed, 30 Jun 1999 09:15:02 +0930 Date: Wed, 30 Jun 1999 09:15:02 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Pierre Beyssac Cc: Bill Fumerola , hackers@freebsd.org Subject: Re: tcpdump(1) additions. In-Reply-To: <19990630014234.A18559@fasterix.frmug.fr.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 Wed, 30 Jun 1999, Pierre Beyssac wrote: > Could you elaborate some more about the SMB patches? I've been to > www.samba.org but it's not obvious to me what's in there for FreeBSD > (except for samba itself). It makes tcpdump understand SMB packets (header structure, etc). See the tcpdump-smb port. Kris, also in favour of merging. ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 16:56:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (Postfix) with ESMTP id 57E58151AD for ; Tue, 29 Jun 1999 16:56:50 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id UAA01326; Tue, 29 Jun 1999 20:00:34 -0400 (EDT) (envelope-from billf@jade.chc-chimes.com) Date: Tue, 29 Jun 1999 20:00:34 -0400 (EDT) From: Bill Fumerola Reply-To: Bill Fumerola To: Pierre Beyssac Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. In-Reply-To: <19990630014234.A18559@fasterix.frmug.fr.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 Wed, 30 Jun 1999, Pierre Beyssac wrote: > On Tue, Jun 29, 1999 at 06:54:06PM -0400, Bill Fumerola wrote: > > Unless there is strong feelings against it, I'd like to commit the smb > > patches (as seen on www.samba.org) > > Could you elaborate some more about the SMB patches? I've been to > www.samba.org but it's not obvious to me what's in there for FreeBSD > (except for samba itself). They decode the SMB (windows share) protocol. They are GPLd, but there is always the possibility of convincing the author to re-release them. > > > and ipsec/ike patches (recently mailed > > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). > > > > Comments? > > The IPSEC/IKE stuff for tcpdump seems like a great thing to have! Agreed. They have the BSD license as well. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Tue Jun 29 17:13:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5C6F1153E6 for ; Tue, 29 Jun 1999 17:13:41 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id RAA14536; Tue, 29 Jun 1999 17:13:05 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA03536; Tue, 29 Jun 1999 17:13:05 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17516; Tue, 29 Jun 99 17:13:04 PDT Message-Id: <3779610F.AD0A55A0@softweyr.com> Date: Tue, 29 Jun 1999 18:13:03 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Miguel Gilly Cc: hackers@FreeBSD.ORG Subject: Re: Redundant Remote Webserver clustering References: <199906291855.SAA21433@luna.pingnet.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Miguel Gilly wrote: > > Bonsai Studio: Web Design and More > http://www.bonsai-studio.com > Content-type: text/plain; charset="US-ASCII" > Content-transfer-encoding: 7bit > > Dear Sirs, > > I would find it extremely helpful if FreeBSD could offer redundant > clustering capabilities for ISP applications. > > Nowadays I feel that it is a far better choice to choose a x86 Unix cluster > over the expensive Sun/SGI SMP servers. > > I found some affordable tools for Linux, but almost nothing for FreeBSD. I > feel such an ability would raise the value a lot of FreeBSD. Define clustering. If you mean a bunch of boxes that serve up HTTP requests and the lot of them continue working in the face of a failure on one, you CAN do this with FreeBSD, and the "Beowulf" software you're probably thinking of for Linux WILL NOT do this. You do this on FreeBSD (or Linux or Solaris) by creating a "layer 4 router" or HTTP switch that directs traffic evenly among your several web servers, and stops sending traffic to servers that have failed. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 17:37:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 289CD1517C for ; Tue, 29 Jun 1999 17:37:23 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA65916; Tue, 29 Jun 1999 20:37:05 -0400 (EDT) Message-Id: <199906300037.UAA65916@cs.rpi.edu> To: Wes Peters Cc: Miguel Gilly , hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Redundant Remote Webserver clustering In-Reply-To: Message from Wes Peters of "Tue, 29 Jun 1999 18:13:03 MDT." <3779610F.AD0A55A0@softweyr.com> Date: Tue, 29 Jun 1999 20:37:04 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Miguel Gilly wrote: > > > > Bonsai Studio: Web Design and More > > http://www.bonsai-studio.com > > Content-type: text/plain; charset="US-ASCII" > > Content-transfer-encoding: 7bit > > > > Dear Sirs, > > > > I would find it extremely helpful if FreeBSD could offer redundant > > clustering capabilities for ISP applications. > > > > Nowadays I feel that it is a far better choice to choose a x86 Unix cluster > > over the expensive Sun/SGI SMP servers. > > > > I found some affordable tools for Linux, but almost nothing for FreeBSD. I > > feel such an ability would raise the value a lot of FreeBSD. > > Define clustering. If you mean a bunch of boxes that serve up HTTP > requests and the lot of them continue working in the face of a > failure on one, you CAN do this with FreeBSD, and the "Beowulf" > software you're probably thinking of for Linux WILL NOT do this. I have looked into the "Beowulf" system alot recently. It is nothing but a glorified COW design. And it uses "off the shelf" software components that run under FreeBSD as well of better than linux often. I used to thing it was a big deal. Not any more :I This is a tangent though :) > You do this on FreeBSD (or Linux or Solaris) by creating a "layer 4 > router" or HTTP switch that directs traffic evenly among your several > web servers, and stops sending traffic to servers that have failed. Where could someone find information on setting this up, and what software to use? I have someone who would be very interested in this. Isn't the "layer 4 router" a SPoF though? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 18: 8:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id 0B88214F73 for ; Tue, 29 Jun 1999 18:08:40 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-144-27.s27.as4.hgt.md.dialup.rcn.com [207.172.144.27]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id VAA27445; Tue, 29 Jun 1999 21:08:18 -0400 (EDT) Message-Id: <199906300108.VAA27445@smtp1.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <48541.930372953@axl.noc.iafrica.com> Date: Tue, 29 Jun 1999 21:08:16 -0400 (EDT) From: John Baldwin To: Sheldon Hearn Subject: Re: Inetd and wrapping. Cc: freebsd-hackers@FreeBSD.ORG, Keith Stevenson , David Malone , Aaron Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-Jun-99 Sheldon Hearn wrote: > On Fri, 25 Jun 1999 13:02:00 MST, Aaron Smith wrote: >> with it. i didn't realize there was an extension already in place -- i >> should have checked the man page over when i saw sheldon's first message >> about "wait/10/10/nowrap". > > There isn't. It's a proposed extension that might happen soon. :-) > >> in order to make this compatible won't one have to specify the not-so-pretty >> "wait/0/0/nowrap"? i guess "wait/nowrap" could be made to work. that's less >> ugly. > > Actually, any of the following ought to work: > > wait/nowrap wait/10/nowrap wait/10/10/nowrap > wait/nowrap/10 wait/10/nowrap/10 > > As well as the previous permutations available. We're lucky because > "nowrap" isn't a number, so it can't be confused with a request to set > max_child nor max_cpm. > >> i am less bothered by this change given the maxchild precedent, if there >> are definitely people who will *use* this. if people don't actually use it, >> it will just become a chunk of legacy extra-complexity. > > I think you may have as many as two people using it. :-\ As I said earlier, if no else wants this and if everyone hates this (which appears to be the case), then you don't have to add it.. majority rule wins. Some viable solutions (such as running two inetd's and sucking up the rather small performance hit and running regular tcpd) have been offered so that the rare functionality I mentioned is still available. I didn't realize adding another tunable know was such an evil hack (I did realize that my original idea of using a seperate flag was an evil hack and has made the original suggestion in a previous post of the wait/(wrao|nowrap) thingamajig). Guess "show me the code" doesn't always work.. :) >> all: sorry if i came off too strident. i have a sore spot for feeping >> creaturism. :) > > Don't be sorry. It's about time people started articulating my rebuttal. > ;-) > > I don't think the core team would care enough about something this silly > to bother making a decision, so I'm just watching what people have to > say. I'm leaning toward leaving the "nowrap" feature out. If it hurts, then by all means. If not, then why design out extra configurability? However, it's no big deal and I'll be content with whatever decision you come to. Note that this would solve the -w(e|i) solution that Doug(?) requested in a more orthogonal way... > Ciao, > Sheldon. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 18:29:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 9177A1534C for ; Tue, 29 Jun 1999 18:29:26 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10z9B4-000Auq-00; Wed, 30 Jun 1999 08:28:42 +0700 Date: Wed, 30 Jun 1999 08:28:42 +0700 (ALMST) From: Boris Popov To: Bill Fumerola Cc: Pierre Beyssac , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Bill Fumerola wrote: I'm also will be happy to see NCP protocol dumps, but probably, it isn't a high priority task. > > Could you elaborate some more about the SMB patches? I've been to > > www.samba.org but it's not obvious to me what's in there for FreeBSD > > (except for samba itself). > > They decode the SMB (windows share) protocol. They are GPLd, but there is > always the possibility of convincing the author to re-release them. Hope it will be possible. The samba team is very restrictive about BSD-style license. As result I can say that smbfs for FreeBSD doesn't contain any GPLd code from Linux's smbfs. BTW, does anybody have objections about name of this file system in FreeBSD ? -- 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 Tue Jun 29 19: 3:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psf.Pinyon.ORG (unknown [205.253.70.237]) by hub.freebsd.org (Postfix) with ESMTP id 8003214E07; Tue, 29 Jun 1999 19:03:05 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id TAA43626; Tue, 29 Jun 1999 19:00:50 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199906300200.TAA43626@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Redundant Remote Webserver clustering In-reply-to: Your message of "Tue, 29 Jun 1999 20:37:04 -0400." <199906300037.UAA65916@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jun 1999 19:00:50 -0700 From: "Russell L. Carter" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %> Define clustering. If you mean a bunch of boxes that serve up HTTP %> requests and the lot of them continue working in the face of a %> failure on one, you CAN do this with FreeBSD, and the "Beowulf" %> software you're probably thinking of for Linux WILL NOT do this. %I have looked into the "Beowulf" system alot recently. It is nothing but %a glorified COW design. And it uses "off the shelf" software components %that run under FreeBSD as well of better than linux often. I used to %thing it was a big deal. Not any more :I This is a tangent though :) That's exactly right, and has been true for about 4 years now. %> You do this on FreeBSD (or Linux or Solaris) by creating a "layer 4 %> router" or HTTP switch that directs traffic evenly among your several %> web servers, and stops sending traffic to servers that have failed. %Where could someone find information on setting this up, and what software %to use? I have someone who would be very interested in this. Isn't the %"layer 4 router" a SPoF though? I haven't actually installed one but my understanding, based on evaluating it as a competitor to some work that I am doing, is you just buy these off the shelf now. I don't have the vendor list handy at home. These things apparently are pretty good at looking inside of packets and making (fast) routing decisions based on the packet protocol and a set of site configured policies. The jargon thrown around my neck of the woods is "smart networks". They understand HTTP pretty darn well. Luckily, not IIOP, yet, which is when my interest faded. Oh yes, about that SPoF, they happily run redundantly, too, with the obvious performance optimizations for redundant channels, degrading as needed. Apparently, these things don't need proprietary extensions for their functionality so use of FreeBSD for the backend OS is unimpaired. I suspect Yahoo has a few... Anyway, maybe followup this to freebsd-isp? Not much -hackers stuff here. And if my assessment is inaccurate, I can find out quicker :-). Russell % %-- %David Cross | email: crossd@cs.rpi.edu %Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd %Rensselaer Polytechnic Institute, | Ph: 518.276.2860 %Department of Computer Science | Fax: 518.276.4033 %I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 19: 7:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id F21F11527C for ; Tue, 29 Jun 1999 19:07:29 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.C832C910@mailer.syr.edu>; Tue, 29 Jun 1999 22:07:30 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id WAA20052; Tue, 29 Jun 1999 22:07:28 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Tue, 29 Jun 1999 22:07:28 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Miguel Gilly Cc: hackers@FreeBSD.ORG Subject: Re: Redundant Remote Webserver clustering In-Reply-To: <199906291855.SAA21433@luna.pingnet.ch> 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, 29 Jun 1999, Miguel Gilly wrote: > Bonsai Studio: Web Design and More > http://www.bonsai-studio.com > Content-type: text/plain; charset="US-ASCII" > Content-transfer-encoding: 7bit > > Dear Sirs, > > I would find it extremely helpful if FreeBSD could offer redundant > clustering capabilities for ISP applications. > > Nowadays I feel that it is a far better choice to choose a x86 Unix cluster > over the expensive Sun/SGI SMP servers. > > I found some affordable tools for Linux, but almost nothing for FreeBSD. I > feel such an ability would raise the value a lot of FreeBSD. > I wrote a simple one--take a look at http://tfeed.maxwell.syr.edu/cluster.txt and http://tfeed.maxwell.syr.edu/fbsd-cluster-0.1.tgz It isn't terribly advanced, but it does work and could be easily modified or extended. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 19:17:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 58F2015184 for ; Tue, 29 Jun 1999 19:17:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id TAA06328; Tue, 29 Jun 1999 19:17:07 -0700 (PDT) Date: Tue, 29 Jun 1999 19:17:06 -0700 (PDT) From: Julian Elischer To: Bill Fumerola Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. 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 yes! they've been submitted to the tcpdump folks many times. On Tue, 29 Jun 1999, Bill Fumerola wrote: > [bcc to committers, replys to hackers] > > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). > > Comments? > > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Tue Jun 29 20:32:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8C4A3152DD for ; Tue, 29 Jun 1999 20:32:36 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40438>; Wed, 30 Jun 1999 13:15:16 +1000 Date: Wed, 30 Jun 1999 13:32:28 +1000 From: Peter Jeremy Subject: Re: environment strings To: hackers@FreeBSD.ORG Message-Id: <99Jun30.131516est.40438@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: >Time for a main() man page? Where would it go? Section 2, 3, or 9? >Hmm... I'd support that. I believe the page needs to be tied to exec (ala setjmp/longjmp), which means it either ties to execve(2) or exec*(3). Note that execve(2) already includes a reference to the calling procedure for main(). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 20:43:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 0750714D0A for ; Tue, 29 Jun 1999 20:43:09 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40486>; Wed, 30 Jun 1999 13:25:50 +1000 Date: Wed, 30 Jun 1999 13:38:41 +1000 From: Peter Jeremy Subject: Re: tcpdump(1) additions. To: hackers@FreeBSD.ORG Message-Id: <99Jun30.132550est.40486@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: >Unless there is strong feelings against it, I'd like to commit the smb >patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed >to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). I also think it's a good idea. Judging from what has happened previously, you'll probably get no-one objecting until you commit the changes, at which time a group from core will erupt from the wood-work with a large collection of reasons for not doing it :-(. Whilst we're at it, how about extending `-x' to print out the packet in ASCII and hex (ala hd(1)). I know the code includes the statement * (BTW, please don't send us patches to print the packet out in ascii) but I find this feature very useful. (I'll send you patches if you are interested). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 20:47:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A83FE14CA0; Tue, 29 Jun 1999 20:47:50 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id UAA08859; Tue, 29 Jun 1999 20:47:49 -0700 (PDT) Date: Tue, 29 Jun 1999 20:47:47 -0700 (PDT) From: Julian Elischer To: "David E. Cross" Cc: dillon@freebsd.org, hackers@freebsd.org Subject: Re: bug in latests NFS patches for -stable In-Reply-To: <199906291348.JAA53461@cs.rpi.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 Matt, If you agree with this patch to your patch I'll commit the NFS fixes to 3.x (I'll also add this change to the 4.0 version.) *** hold/nfs_serv.c Tue Jun 22 13:37:17 1999 --- nfs_serv.c Tue Jun 29 20:42:44 1999 *************** *** 1580,1585 **** --- 1580,1586 ---- if (error) { nfsm_reply(NFSX_WCCDATA(v3)); nfsm_srvwcc_data(dirfor_ret, &dirfor, diraft_ret, &diraft); + error=0; goto nfsmout; } On Tue, 29 Jun 1999, David E. Cross wrote: > There is a small by critical error in the latest patches which causes the > server to never transmit a response packet back to the client in certain > conditions on a nfs create RPC. Below is the updated NFS3 patch. If > jullian could take this for review and place it at the "official" unoffical > URL it would be muchly appreciated :) It is a one line patch. > > http://www.cs.rpi.edu/~crossd/FreeBSD/nfspatch3a.diff see above for diff > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > 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 Jun 29 20:57:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id E95BD14E4A for ; Tue, 29 Jun 1999 20:57:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id UAA09112; Tue, 29 Jun 1999 20:57:30 -0700 (PDT) Date: Tue, 29 Jun 1999 20:57:29 -0700 (PDT) From: Julian Elischer To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: fix for bug in latests NFS patches for -stable In-Reply-To: <199906291348.JAA53461@cs.rpi.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 New full 3.x relative patch at: ftp://ftp.whistle.com/pub/julian/nfs-3.diffs On Tue, 29 Jun 1999, David E. Cross wrote: > There is a small by critical error in the latest patches which causes the > server to never transmit a response packet back to the client in certain > conditions on a nfs create RPC. Below is the updated NFS3 patch. If > jullian could take this for review and place it at the "official" unoffical > URL it would be muchly appreciated :) It is a one line patch. > > http://www.cs.rpi.edu/~crossd/FreeBSD/nfspatch3a.diff > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > 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 Jun 29 21:22:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 20ACF150FF for ; Tue, 29 Jun 1999 21:22:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA33965; Tue, 29 Jun 1999 21:22:49 -0700 (PDT) (envelope-from dillon) Date: Tue, 29 Jun 1999 21:22:49 -0700 (PDT) From: Matthew Dillon Message-Id: <199906300422.VAA33965@apollo.backplane.com> To: Julian Elischer Cc: "David E. Cross" , hackers@FreeBSD.ORG Subject: Re: bug in latests NFS patches for -stable References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys. Sorry, I've been busy messing with Kirk's locking code. Yes, David found a critical bug all right! When I changed the return(0); that had previously been in this section of code to a 'goto nfsmout', I forgot to set error = 0. -Matt Matthew Dillon :Matt, :If you agree with this patch to your patch :I'll commit the NFS fixes to 3.x :(I'll also add this change to the 4.0 version.) : :*** hold/nfs_serv.c Tue Jun 22 13:37:17 1999 :--- nfs_serv.c Tue Jun 29 20:42:44 1999 :*************** :*** 1580,1585 **** :--- 1580,1586 ---- : if (error) { : nfsm_reply(NFSX_WCCDATA(v3)); : nfsm_srvwcc_data(dirfor_ret, &dirfor, diraft_ret, &diraft); :+ error=0; : goto nfsmout; : } : :> :> http://www.cs.rpi.edu/~crossd/FreeBSD/nfspatch3a.diff : :see above for diff : ... Julian : :> David Cross | email: crossd@cs.rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 22: 9: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E8D83154BF for ; Tue, 29 Jun 1999 22:08:47 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA27161; Wed, 30 Jun 1999 14:38:41 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA74422; Wed, 30 Jun 1999 14:38:35 +0930 (CST) Date: Wed, 30 Jun 1999 14:38:35 +0930 From: Greg Lehey To: "Brian F. Feldman" Cc: Amol Mohite , freebsd-hackers@FreeBSD.ORG Subject: Re: environment strings Message-ID: <19990630143835.Y85121@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Tue, Jun 29, 1999 at 05:56:37AM -0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 29 June 1999 at 5:56:37 -0400, Brian F. Feldman wrote: > On Tue, 29 Jun 1999, Brian F. Feldman wrote: > >> >> That's not true, Greg. I'm sure you of all people know that it (the >> composition of address space) is described in "The Design and >> Implementation of the 4.4BSD Operating System," even if things >> are slightly different in FreeBSD of today (especially addresses.) > > Should we expect to see something similar in the next revision of > your book? Assuming you're talking about "The Complete FreeBSD", I don't think so. As I mentioned, it's already in "Porting UNIX Software". > Describing this would be nice, because lots of people get curious > about this :) You may be overstating the case. CFBSD is about FreeBSD, not UNIX in general, and every UNIX flavour since the 7th Edition has this arrangement. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 23:51:16 1999 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 ECC2214C4B for ; Tue, 29 Jun 1999 23:51:12 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id HAA91149; Wed, 30 Jun 1999 07:51:12 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 30 Jun 1999 07:45:48 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <99Jun30.132550est.40486@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Jun 1999 07:45:46 +0000 To: Peter Jeremy From: Bob Bishop Subject: Re: tcpdump(1) additions. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 1:38 pm +1000 30/6/99, Peter Jeremy wrote: >[...] >Whilst we're at it, how about extending `-x' to print out the packet >in ASCII and hex (ala hd(1)). I know the code includes the statement > > * (BTW, please don't send us patches to print the packet out in ascii) > >but I find this feature very useful. (I'll send you patches if you >are interested). Hear hear. I have just three tiny personal patches that I apply to the FreeBSD code base, and (my version of) that's one of them. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 29 23:51:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 323A015501 for ; Tue, 29 Jun 1999 23:51:19 -0700 (PDT) (envelope-from klein@KryptoKom.DE) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id KAA16633 for ; Wed, 30 Jun 1999 10:50:25 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa16631; Wed Jun 30 10:50:12 1999 Received: from borg.kryptokom.de (borg.Kryptokom.DE [192.168.6.132]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id IAA05190 for ; Wed, 30 Jun 1999 08:55:56 +0200 Received: from kryptokom.de (localhost [127.0.0.1]) by borg.kryptokom.de (8.8.8/8.8.8) with ESMTP id JAA11471 for ; Wed, 30 Jun 1999 09:16:36 +0200 (CEST) (envelope-from klein@kryptokom.de) Message-ID: <3779C453.41FDF036@kryptokom.de> Date: Wed, 30 Jun 1999 09:16:35 +0200 From: Thomas Klein X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-19980804-SNAP i386) X-Accept-Language: de, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: questing: delay of a context - switch Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dose anyone know how long a the kernel is buisy with context switching (beetween two processes) ? Has anyone testet this yet? I have made estimate of 7 usec duration for that, (on a Pentium 400) but I think that's to long. Regards Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 0:22:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B6A7914E0D for ; Wed, 30 Jun 1999 00:22:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id AAA13550; Wed, 30 Jun 1999 00:22:10 -0700 (PDT) Date: Wed, 30 Jun 1999 00:22:08 -0700 (PDT) From: Julian Elischer To: Bob Bishop Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. 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 It would make sense except that the last time someone tried, some people complained that it made it too easy to sniff passwords etc. On Wed, 30 Jun 1999, Bob Bishop wrote: > Hi, > > At 1:38 pm +1000 30/6/99, Peter Jeremy wrote: > >[...] > >Whilst we're at it, how about extending `-x' to print out the packet > >in ASCII and hex (ala hd(1)). I know the code includes the statement > > > > * (BTW, please don't send us patches to print the packet out in ascii) > > > >but I find this feature very useful. (I'll send you patches if you > >are interested). > > Hear hear. I have just three tiny personal patches that I apply to the > FreeBSD code base, and (my version of) that's one of them. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > > 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 Jun 30 0:36:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 1936C1573F for ; Wed, 30 Jun 1999 00:36:15 -0700 (PDT) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1] (may be forged)) by orthanc.ab.ca (8.9.3/8.9.3) with ESMTP id BAA13149; Wed, 30 Jun 1999 01:35:50 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <199906300735.BAA13149@orthanc.ab.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: Bob Bishop , Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. In-reply-to: Your message of "Wed, 30 Jun 1999 00:22:08 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jun 1999 01:35:50 -0600 From: lyndon@orthanc.ab.ca Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would make sense except that the last time someone tried, some people > complained that it made it too easy to sniff passwords etc. And thus was born tcpshow. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 0:36:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id B1B5D156E3 for ; Wed, 30 Jun 1999 00:36:09 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 30 Jun 1999 08:35:54 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id NHL6LZJV; Wed, 30 Jun 1999 08:26:54 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10zEuU-000J20-00; Wed, 30 Jun 1999 08:35:58 +0100 Date: Wed, 30 Jun 1999 08:35:58 +0100 To: Julian Elischer Cc: Bob Bishop , Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. Message-Id: <19990630083557.A69889@palmerharvey.co.uk> References: MIME-Version: 1.0 X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Julian Elischer on Wed, Jun 30, 1999 at 12:22:08AM -0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 12:22:08AM -0700, Julian Elischer wrote: > It would make sense except that the last time someone tried, some people > complained that it made it too easy to sniff passwords etc. Ok, so how about making it a compile time option, turned off by default? That way, you have to recompile it from source. I suppose it's a little bit of "security through obscurity", though. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "How Unix vendors can ship ancient shells with no job control and no cursor editing by default and still wonder why people buy NT is beyond me." - Alan Cox -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 0:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0488D14BCD for ; Wed, 30 Jun 1999 00:44:16 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id DAA05331; Wed, 30 Jun 1999 03:44:06 -0400 (EDT) Date: Wed, 30 Jun 1999 03:44:05 -0400 (EDT) From: "Matthew N. Dodd" To: Julian Elischer Cc: Bob Bishop , Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. 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 Wed, 30 Jun 1999, Julian Elischer wrote: > It would make sense except that the last time someone tried, some people > complained that it made it too easy to sniff passwords etc. Thats such a bogus issue. IIRC there are ports that do the same thing (automatic snarfing of cleartext passwords from tcp streams.) And if it isn't a port yet I'm sure someone will come out of the woodwork and make it one. Regardless, -x solves 90% of the issues that cause me to have to use tcpdump | tcpshow right now. > On Wed, 30 Jun 1999, Bob Bishop wrote: > > > Hi, > > > > At 1:38 pm +1000 30/6/99, Peter Jeremy wrote: > > >[...] > > >Whilst we're at it, how about extending `-x' to print out the packet > > >in ASCII and hex (ala hd(1)). I know the code includes the statement > > > > > > * (BTW, please don't send us patches to print the packet out in ascii) > > > > > >but I find this feature very useful. (I'll send you patches if you > > >are interested). > > > > Hear hear. I have just three tiny personal patches that I apply to the > > FreeBSD code base, and (my version of) that's one of them. > > > > > > -- > > Bob Bishop (0118) 977 4017 international code +44 118 > > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > > > > > > > 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 > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 0:47:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tinny.eis.net.au (tinny.eis.net.au [203.12.171.1]) by hub.freebsd.org (Postfix) with ESMTP id 9E37D14BCD for ; Wed, 30 Jun 1999 00:47:46 -0700 (PDT) (envelope-from ernie@tinny.eis.net.au) Received: (from ernie@localhost) by tinny.eis.net.au (8.8.8/8.8.3) id RAA22457 for freebsd-hackers@freebsd.org; Wed, 30 Jun 1999 17:47:45 +1000 (EST) From: Ernie Elu Message-Id: <199906300747.RAA22457@tinny.eis.net.au> Subject: Device Drivers on 3.2-RELEASE To: freebsd-hackers@freebsd.org Date: Wed, 30 Jun 1999 17:47:45 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking for a guide to portin a device driver for a wireless networking ISA card that was written for 2.2.5-RELEASE. across to 3.2-RELEASE. From reading various mail lists I understand that from the 3.0 kernel onwards the drive interface to the kernel changed a lot, not doubt this is why I can't get th driver to compile. Can someone point me to a reference on the changes, or is there some kind of documentation on driver writing for FreeBSD that I can study? - Ernie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 0:54:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from golgotha.dons.net.au (spare6.gsoft.com.au [203.38.152.108]) by hub.freebsd.org (Postfix) with ESMTP id 6D1AE14CB7 for ; Wed, 30 Jun 1999 00:54:43 -0700 (PDT) (envelope-from doconnor@golgotha.dons.net.au) Received: (from doconnor@localhost) by golgotha.dons.net.au (8.9.3/8.9.3) id RAA07825; Wed, 30 Jun 1999 17:23:38 +0930 (CST) (envelope-from doconnor) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990630172337:633=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <199906300747.RAA22457@tinny.eis.net.au> Date: Wed, 30 Jun 1999 17:23:37 +0930 (CST) From: "Daniel J. O'Connor" To: Ernie Elu Subject: RE: Device Drivers on 3.2-RELEASE Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990630172337:633=_ Content-Type: text/plain; charset=us-ascii On 30-Jun-99 Ernie Elu wrote: > From reading various mail lists I understand that from the 3.0 kernel > onwards the drive interface to the kernel changed a lot, not doubt this is > why I can't get th driver to compile. > > Can someone point me to a reference on the changes, or is there some kind of > documentation on driver writing for FreeBSD that I can study? "Use the source luke" I don't know what changed network wise, but for an IO device its a fairly simple change.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990630172337:633=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3nNAWj0TqzKxF7VAQFh4gP8Cwaea4MyHmS/+YiYOgWGvQ9N2/QA4FfG jHrnDYxGtSt7zirVCI6+1ArDMVe/VWRU6fiZYuLh2qOpbojmdXi3meMoIq0nS3tF PRkHqKLnozJ/0Rl0h600CHBzagiUw4yRCtGG80PBCL5QsTeObC6fgtut0OpAS8+l APTzbOqZRuo= =mBYI -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990630172337:633=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 1:15:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 151E114FC5 for ; Wed, 30 Jun 1999 01:15:37 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-1-24.ucdavis.edu [169.237.16.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA36920; Wed, 30 Jun 1999 01:15:35 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA98763; Wed, 30 Jun 1999 08:15:33 GMT (envelope-from obrien) Date: Wed, 30 Jun 1999 01:15:32 -0700 From: "David O'Brien" To: Bill Fumerola Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. Message-ID: <19990630011532.A97926@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Bill Fumerola on Tue, Jun 29, 1999 at 06:54:06PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 29, 1999 at 06:54:06PM -0400, Bill Fumerola wrote: > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) Cool! I've been meaning to do this for quite some time. HOWEVER, please reference this PGP signed email (I'll send you the full copy) in the commit message: Sender: tridge@samba.anu.edu.au From: Andrew Tridgell To: obrien@NUXI.com In-reply-to: <19990106131559.A18935@dragon.nuxi.com> (obrien@NUXI.com) Subject: Re: tcpdump patches copyright References: <19990106131559.A18935@dragon.nuxi.com> Message-Id: <19990106234704Z12605236-3608+4250@samba.anu.edu.au> Date: Thu, 7 Jan 1999 10:47:03 +1100 yes, you are welcome to use those files under the tcpdump copyright. ..snip.. Note that the Tcpdump patches from www.samba.org are under the GPL. Andrew Tridgell also warned: I should warn you though that there are some security issues with my tcpdump-smb patches. It is possible for a malicious user to put packets on the wire that will cause a buffer overflow in the SMB parser in that code. That could lead to a root exploit. I just haven't got around to fixing it yet. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 1:24:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 41D48150F2 for ; Wed, 30 Jun 1999 01:24:19 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 738 invoked by uid 1001); 30 Jun 1999 08:24:18 +0000 (GMT) To: julian@whistle.com Cc: rb@gid.co.uk, jeremyp@gsmx07.alcatel.com.au, hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 30 Jun 1999 00:22:08 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 30 Jun 1999 10:24:18 +0200 Message-ID: <736.930731058@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would make sense except that the last time someone tried, some people > complained that it made it too easy to sniff passwords etc. There are plenty of patches to do this available, and plenty of other packet sniffers that do this. AFAIK even the attitude of the tcpdump maintainers is changing - precisely because this facility is so widely available. Let us by all means have an ACII dump facility. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 2:33:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kodos.tinet.ie (kodos.tinet.ie [159.134.237.29]) by hub.freebsd.org (Postfix) with ESMTP id 10F35150BC for ; Wed, 30 Jun 1999 02:33:09 -0700 (PDT) (envelope-from crypt0genic@tinet.ie) Received: from p210.as2.cork1.tinet.ie ([159.134.229.210] helo=tweak.home) by kodos.tinet.ie with esmtp (Exim 2.05 #23) id 10zGjq-0000Kv-00; Wed, 30 Jun 1999 10:33:07 +0100 Received: (from crypt0genic@localhost) by tweak.home (8.9.3/8.9.3) id KAA00320; Wed, 30 Jun 1999 10:31:35 GMT Date: Wed, 30 Jun 1999 10:31:35 +0000 From: crypt0genic To: David Miller Cc: freebsd-hackers@freebsd.org Subject: Re: DVD-ram Message-ID: <19990630103135.A315@ecad.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from David Miller on Tue, Jun 29, 1999 at 12:18:29PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Lacie DVD-RAM drive, it work great under windows, here is the DMESG i g et from it, I hope this is of some help. acd0: drive speed 1033KB/sec, 256KB cache acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked AFAIK I need to format the disks im using, but im unsure what format to use, If anyone has some suggestions or would like me to try different things for informa tion purposes I will be glad to help out. Also on another note, what is the support like for a Creative Labs encore DVD dr ive under FreeBSD? -crypt0genic * David Miller (dmiller@search.sparks.net) [990630 09:53]: > Apologies if this should be on -scsi.... > > Has anyone done any work with dvd-ram drives under FreeBSD? > > I will soon need to duplicate dvd-ram media and would very much like to do > it under unix. All I need to start with is the ability to read/write the > raw device. > > Currently the drive is recognized as cd0 (FreeBSD 3.2) and I can read a > 2.x GB side but not, of course, write it. I'm looking at cdrecord for > clues but would like not to reinvent someone elses work. > > Thanks in advance, > > --- David > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. Public PGP key: http://www.ecad.org/crypt0genic_pgp_key Website: http://www.ecad.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 4:33: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 28B0D15259 for ; Wed, 30 Jun 1999 04:32:57 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id VAA16803; Wed, 30 Jun 1999 21:02:38 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA32353; Wed, 30 Jun 1999 21:02:36 +0930 Date: Wed, 30 Jun 1999 21:02:36 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "Matthew N. Dodd" Cc: Julian Elischer , Bob Bishop , Peter Jeremy , hackers@freebsd.org Subject: Re: tcpdump(1) additions. 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 Wed, 30 Jun 1999, Matthew N. Dodd wrote: > > It would make sense except that the last time someone tried, some people > > complained that it made it too easy to sniff passwords etc. > > Thats such a bogus issue. The argument (to me) is not one of capability, but expediency. If you're running a tcpdump which includes telnet traffic and someone logs in, their password goes floating past in front of your eyes (and anyone else who is watching). Most of us can't read hex-encoded ascii strings, so the passswords aren't apparent to the (witting or unwitting) casual observer. But on the other hand it would certainly have its uses, so including this with the default being the current hex dump seems fine to me. Kris ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 4:42:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 7E63D14E0D; Wed, 30 Jun 1999 04:42:07 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn30.imasy.or.jp [202.227.24.222]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id UAA20504; Wed, 30 Jun 1999 20:42:05 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199906301142.UAA20504@tasogare.imasy.or.jp> To: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Cc: iwasaki@jp.freebsd.org Subject: Re: [Call for review] apmd for FreeBSD In-Reply-To: Your message of "Mon, 28 Jun 1999 05:29:02 +0900" <199906272024.FAA11076@tasogare.imasy.or.jp> References: <199906272024.FAA11076@tasogare.imasy.or.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 30 Jun 1999 20:46:33 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Documentation of apmd was updated by cooperation with Nick Hilliard . # Thanks Nick! Updated README and apmd.8 are available at: http://home.jp.freebsd.org/~iwasaki/apm/19990630/apmd-doc.tar.gz http://home.jp.freebsd.org/~iwasaki/apm/19990630/apmd-doc.diff.gz Also, I'm going to import them on this (or next) weekend if nothing happened. # I'm not sure when because I'm in the hospital... :-( Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 6:15:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 70CEA14E82 for ; Wed, 30 Jun 1999 06:15:31 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id PAA23195 for ; Wed, 30 Jun 1999 15:15:30 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma023193; Wed, 30 Jun 99 15:15:30 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id PAA10011 for ; Wed, 30 Jun 1999 15:15:29 +0200 (MET DST) Received: (qmail 56265 invoked by uid 666); 30 Jun 1999 13:15:51 -0000 Date: Wed, 30 Jun 1999 15:15:51 +0200 From: Jos Backus To: freebsd-hackers@freebsd.org Subject: [tobi@caida.org: Re: [MRTG-DEV] CDEF's with LT and IF in .42] Message-ID: <19990630151551.C51182@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Saw this on the MRTG-DEV list. NaN handling is perceived to be problematic, it seems. ----- Forwarded message from Tobi Oetiker ----- Date: Wed, 30 Jun 1999 02:16:55 +0200 (MET DST) From: Tobi Oetiker To: Jesper Skriver cc: mrtg-developers@list.ee.ethz.ch Subject: Re: [MRTG-DEV] CDEF's with LT and IF in .42 Today you sent me mail regarding Re: [MRTG-DEV] CDEF's with LT and IF in .42: *> On Tue, Jun 29, 1999 at 09:01:29PM +0200, Tobi Oetiker wrote: *> *> > aha ... thats in a perl context .. sorry I didn't realize ... could you send *> > me an example rrd and a short programm which demonstrates the problem ? *> *> Yes, this does the trick, it's very ugly code ... *> *> http://e.t.dk/test.pl test program, set $this_breaks to have it core dump *> http://e.t.dk/test.rrd FreeBSD 3.2-STABLE rrd *> http://e.t.dk/test.xml The above dump'ed into xml OK found your problem .... it is that old FreeBSD does no proper IEEE math ... for some comparison operations it raises an sigfpe if an NaN is involved ... the next release of rrdtool will come with a proper test to find the problem and a proper fix in the software to ignore sigfpe cheers tobi *> /Jesper *> *> -- ______ __ _ /_ __/_ / / (_) Oetiker, hacking RRDTOOL&MRTG @ Caida for the Summer / // _ \/ _ \/ / +1 619 822 0882 / tobi@caida.org / www.caida.org/~tobi /_/ \.__/_.__/_/ _______________________________________________________ -- * To unsubscribe from the mrtg-developers mailing list, send a message with the subject: unsubscribe to mrtg-developers-request@list.ee.ethz.ch * Mailing list archives are at http://www.ee.ethz.ch/~slist/mrtg-developers ----- End forwarded message ----- -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 6:58:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 20B73152A0 for ; Wed, 30 Jun 1999 06:58:55 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA122525904; Wed, 30 Jun 1999 05:45:04 -0400 Date: Wed, 30 Jun 1999 05:45:03 -0400 (EDT) From: Bill Fumerola To: Julian Elischer Cc: Bob Bishop , Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. 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 Wed, 30 Jun 1999, Julian Elischer wrote: > It would make sense except that the last time someone tried, some people > complained that it made it too easy to sniff passwords etc. I would bet there are a million other programs on rootshell or other such sites that do just that. If someone has compromised root on one machine, evidently security already isn't a concern for them. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Jun 30 7: 6:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id CEB14152A0; Wed, 30 Jun 1999 07:06:50 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA126036421; Wed, 30 Jun 1999 05:53:41 -0400 Date: Wed, 30 Jun 1999 05:53:41 -0400 (EDT) From: Bill Fumerola To: David O'Brien Cc: Bill Fumerola , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. In-Reply-To: <19990630011532.A97926@dragon.nuxi.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, 30 Jun 1999, David O'Brien wrote: > On Tue, Jun 29, 1999 at 06:54:06PM -0400, Bill Fumerola wrote: > > Unless there is strong feelings against it, I'd like to commit the smb > > patches (as seen on www.samba.org) > > Cool! I've been meaning to do this for quite some time. HOWEVER, please > reference this PGP signed email (I'll send you the full copy) in the > commit message: Excellent. > Note that the Tcpdump patches from www.samba.org are under the GPL. > Andrew Tridgell also warned: > > I should warn you though that there are some security issues with my > tcpdump-smb patches. It is possible for a malicious user to put > packets on the wire that will cause a buffer overflow in the SMB > parser in that code. That could lead to a root exploit. > > I just haven't got around to fixing it yet. Hmmm.. but a non-superuser never sees any of those malicious packets, and the program is not installed suid, so how would that happen? - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Jun 30 7:21:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id B575F15482; Wed, 30 Jun 1999 07:21:27 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 30 Jun 1999 16:24:04 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796C5@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Bill Fumerola' , David O'Brien Cc: Bill Fumerola , hackers@FreeBSD.ORG Subject: RE: tcpdump(1) additions. Date: Wed, 30 Jun 1999 16:18:10 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Bill Fumerola [SMTP:billf@chc-chimes.com] > Sent: Wednesday, June 30, 1999 11:54 AM > To: David O'Brien > Cc: Bill Fumerola; hackers@FreeBSD.ORG > Subject: Re: tcpdump(1) additions. > > On Wed, 30 Jun 1999, David O'Brien wrote: > > > Hmmm.. but a non-superuser never sees any of those malicious packets, > and > the program is not installed suid, so how would that happen? [ML] Simple. One of these bad packets makes the currently executing copy of tcpdump (invoked by superuser) install a backdoor on the system. Probably with root privileges, too. An actual exploit thereof is probably not that simple, but possible nevertheless. /Marino > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons > corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - > billf@FreeBSD.org - > > > > > > 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 Jun 30 7:34:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id E02DC14D0E for ; Wed, 30 Jun 1999 07:34:28 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id PAA41139; Wed, 30 Jun 1999 15:29:16 +0100 (BST) (envelope-from joe) Date: Wed, 30 Jun 1999 15:29:16 +0100 From: Josef Karthauser To: Niall Smart Cc: hackers@FreeBSD.ORG Subject: Re: [DISKLABEL FRAGGED] Clues requested... ;) Message-ID: <19990630152916.I53349@pavilion.net> References: <19990621083803.M95198@pavilion.net> <376E42BD.117B32DA@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <376E42BD.117B32DA@pobox.com>; from Niall Smart on Mon, Jun 21, 1999 at 01:48:45PM +0000 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, 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 Mon, Jun 21, 1999 at 01:48:45PM +0000, Niall Smart wrote: > Josef Karthauser wrote: > > > > Guess what... I've got a disk where the partition table and the disklabel has > > mysteriously disappeared! Oops. > > > > I've reconstructed the partition table, and now need to partition the disklabel. > > Wow, you're probably the first person ever to do that, unlucky you. Out > of sympathy I've written you this findsb program which of course I've > never had to use myself. Its not the most efficiently written program > ever > and since FreeBSD swap partitions don't have magic numbers it may be > slow, > but it seems to work, however I draw your attention to the disclaimer > in the C file. ;) > BTW with a little tweaking this worked fine. Thanks very much. 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 Wed Jun 30 8:39:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 60DBB153A9 for ; Wed, 30 Jun 1999 08:39:13 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id KAA51909; Wed, 30 Jun 1999 10:39:11 -0500 (CDT) (envelope-from dan) Date: Wed, 30 Jun 1999 10:39:10 -0500 From: Dan Nelson To: Jos Backus Cc: freebsd-hackers@FreeBSD.ORG, Tobi Oetiker Subject: Re: [tobi@caida.org: Re: [MRTG-DEV] CDEF's with LT and IF in .42] Message-ID: <19990630103910.B50144@dan.emsphone.com> References: <19990630151551.C51182@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990630151551.C51182@hal.mpn.cp.philips.com>; from "Jos Backus" on Wed Jun 30 15:15:51 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 30), Jos Backus said: > ----- Forwarded message from Tobi Oetiker ----- > > OK found your problem .... it is that old FreeBSD does no proper > > IEEE math ... > > > > for some comparison operations it raises an sigfpe if an NaN is > > involved ... > > > > the next release of rrdtool will come with a proper test to find > > the problem and a proper fix in the software to ignore sigfpe > > Saw this on the MRTG-DEV list. > NaN handling is perceived to be problematic, it seems. The last time this came up (and it comes up every 6 months or so), the consensus was that we would rather trap FP errors than blindly pass them on to the user application. If a program wants to ignore NaN, divide-by-zero, underflow, and overflow conditions, let it wrap the offending line of code with two fpsetmask() calls; one to mask the condition, and one to restore the previous mask. If you want to completely ignore floating point errors, call fpsetmask(0) at the top of main(). I scanned the mailinglists and the thread that covers this issue most completely is http://www.freebsd.org/cgi/mid.cgi?id=199710101907.OAA09470@millenia.srrc.usda.gov -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 9:24:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 272E0155E4; Wed, 30 Jun 1999 09:24:04 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id JAA51776; Wed, 30 Jun 1999 09:23:58 -0700 (PDT) (envelope-from mph) Date: Wed, 30 Jun 1999 09:23:58 -0700 From: Matthew Hunt To: Bill Fumerola Cc: "David O'Brien" , Bill Fumerola , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. Message-ID: <19990630092358.A51584@wopr.caltech.edu> References: <19990630011532.A97926@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Bill Fumerola on Wed, Jun 30, 1999 at 05:53:41AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 05:53:41AM -0400, Bill Fumerola wrote: > > I should warn you though that there are some security issues with my > > tcpdump-smb patches. It is possible for a malicious user to put > > packets on the wire that will cause a buffer overflow in the SMB > > parser in that code. That could lead to a root exploit. > > > > I just haven't got around to fixing it yet. > > Hmmm.. but a non-superuser never sees any of those malicious packets, and > the program is not installed suid, so how would that happen? I think the point is that when root is running tcpdump on host A, a bad guy on host B can create a packet which makes tcpdump on A execute his code (as root, since that's who's running it). This is not desirable. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 11:17:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id AA545155CB for ; Wed, 30 Jun 1999 11:17:28 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA05051; Wed, 30 Jun 1999 11:17:24 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA07050; Wed, 30 Jun 1999 11:17:22 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 30 Jun 1999 11:17:22 -0700 (PDT) Message-Id: <199906301817.LAA07050@vashon.polstra.com> To: fjoe@iclub.nsu.ru Subject: Re: dlopen returns non NULL In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > > in the following code `dlopen' returns NULL > on the first iteration (because g() is not defined) -- it's ok > but on the second iteration `dlopen' returns "valid" dlh ELF or a.out? Which version of FreeBSD? For a.out, it's a known bug and there is already an open PR on it. I wouldn't be surprised if the bug existed in ELF too. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 11:26:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 010AB15635 for ; Wed, 30 Jun 1999 11:26:19 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA05119; Wed, 30 Jun 1999 11:26:17 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA07099; Wed, 30 Jun 1999 11:26:17 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 30 Jun 1999 11:26:17 -0700 (PDT) Message-Id: <199906301826.LAA07099@vashon.polstra.com> To: mph@astro.caltech.edu Subject: Re: tcpdump(1) additions. In-Reply-To: <19990630092358.A51584@wopr.caltech.edu> References: <19990630011532.A97926@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990630092358.A51584@wopr.caltech.edu>, Matthew Hunt wrote: > > I think the point is that when root is running tcpdump on host A, a bad > guy on host B can create a packet which makes tcpdump on A execute his > code (as root, since that's who's running it). This is not desirable. I would say it is not _acceptable_. The code shouldn't go into our source tree until the known buffer overflow problems have been fixed. It's just stupid to add buffer overflow problems to a program that is always run as root. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 11:34:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 2206F15628 for ; Wed, 30 Jun 1999 11:34:02 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id OAA10563 for ; Wed, 30 Jun 1999 14:40:04 -0400 (EDT) Date: Wed, 30 Jun 1999 14:40:04 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: freebsd-hackers@freebsd.org Subject: GRE encapsulation under FreeBSD 3.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD (although I might be blind)...anyone working on support it or is there already an implementation? If I had to write it, I'd presume DIVERT(4) sockets would be the way to go? Thanks. -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 11:34:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 172FD15614 for ; Wed, 30 Jun 1999 11:34:32 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 9838 invoked by uid 1001); 30 Jun 1999 18:34:31 +0000 (GMT) To: jdp@polstra.com Cc: mph@astro.caltech.edu, hackers@freebsd.org Subject: Re: tcpdump(1) additions. From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 30 Jun 1999 11:26:17 -0700 (PDT)" References: <199906301826.LAA07099@vashon.polstra.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 30 Jun 1999 20:34:31 +0200 Message-ID: <9836.930767671@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would say it is not _acceptable_. The code shouldn't go into our > source tree until the known buffer overflow problems have been fixed. > It's just stupid to add buffer overflow problems to a program that is > always run as root. Minor correction: tcpdump will run happily as non-root as long as it can read packets from /dev/bpf. I use this all the time on my own systems, having chmod'ed /dev/bpf to readable for group wheel. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 12: 7: 6 1999 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 C965714FE3 for ; Wed, 30 Jun 1999 12:07:03 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id VAA56297; Wed, 30 Jun 1999 21:06:53 +0200 (CEST) (envelope-from des) To: Bill Fumerola Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. References: From: Dag-Erling Smorgrav Date: 30 Jun 1999 21:06:53 +0200 In-Reply-To: Bill Fumerola's message of "Tue, 29 Jun 1999 18:54:06 -0400 (EDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola writes: > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). Will they be included in a future official release of tcpdump? Can we afford to wait until then, and simply merge in the next release when it comes? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 12: 9:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (Postfix) with ESMTP id 8F75A14FE3 for ; Wed, 30 Jun 1999 12:09:02 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id PAA09545; Wed, 30 Jun 1999 15:13:17 -0400 (EDT) (envelope-from billf@jade.chc-chimes.com) Date: Wed, 30 Jun 1999 15:13:17 -0400 (EDT) From: Bill Fumerola To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.org Subject: Re: tcpdump(1) additions. 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 30 Jun 1999, Dag-Erling Smorgrav wrote: > Bill Fumerola writes: > > Unless there is strong feelings against it, I'd like to commit the smb > > patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed > > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). > > Will they be included in a future official release of tcpdump? Can we > afford to wait until then, and simply merge in the next release when > it comes? I thought of that, and I believe Julian said that patches sent to the tcpdump mailing list seem to never get into the distribution or something to that effect. Correct me if I'm wrong. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Jun 30 12:22:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 947BA1503C for ; Wed, 30 Jun 1999 12:22:33 -0700 (PDT) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 3B0BD24B; Wed, 30 Jun 1999 15:22:29 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id 3375320E; Wed, 30 Jun 1999 15:22:29 -0400 (EDT) Date: Wed, 30 Jun 1999 15:22:29 -0400 (EDT) From: David Miller To: crypt0genic Cc: freebsd-hackers@freebsd.org Subject: Re: DVD-ram In-Reply-To: <19990630103135.A315@ecad.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 Wed, 30 Jun 1999, crypt0genic wrote: > I have a Lacie DVD-RAM drive, it work great under windows, here is the DMESG i g > et from it, I hope this is of some help. > > acd0: drive speed 1033KB/sec, 256KB cache > acd0: supported read types: > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked IDE interface I take it? This is the normal message for a CD. > > AFAIK I need to format the disks im using, but im unsure what format to use, If > anyone has some suggestions or would like me to try different things for informa > tion purposes I will be glad to help out. I didn't realize it until we used it under 95/98, but the DVD-ram appears to act like an MO drive. IE, one can add, remove, change files at will. I may hack the od driver in the next couple of days to see if it will work at all. > > Also on another note, what is the support like for a Creative Labs encore DVD dr > ive under FreeBSD? I have no idea what this drive is. --- david To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 12:34:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 7E0311558E for ; Wed, 30 Jun 1999 12:34:29 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA14590; Wed, 30 Jun 1999 14:34:29 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id OAA08168; Wed, 30 Jun 1999 14:34:28 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id OAA14468; Wed, 30 Jun 1999 14:34:27 -0500 (CDT) Date: Wed, 30 Jun 1999 14:34:27 -0500 (CDT) From: Jonathan Lemon Message-Id: <199906301934.OAA14468@free.pcs> To: marc@netstor.com, hackers@freebsd.org Subject: Re: GRE encapsulation under FreeBSD 3.2 X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD >(although I might be blind)...anyone working on support it or is there >already an implementation? Yes, I've grabbed the GRE support from NetBSD, and have it working here (as far as I can tell). I'll commit it in a day or two. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 12:47:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id D637F154D7 for ; Wed, 30 Jun 1999 12:47:42 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id PAA11129; Wed, 30 Jun 1999 15:53:46 -0400 (EDT) Date: Wed, 30 Jun 1999 15:53:46 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Jonathan Lemon Cc: hackers@freebsd.org Subject: Re: GRE encapsulation under FreeBSD 3.2 In-Reply-To: <199906301934.OAA14468@free.pcs> 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 Jonathan: You're the man :-) I think we're both going in similar directions here... Thanks. -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Wed, 30 Jun 1999, Jonathan Lemon wrote: > In article you write: > >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD > >(although I might be blind)...anyone working on support it or is there > >already an implementation? > > Yes, I've grabbed the GRE support from NetBSD, and have it working > here (as far as I can tell). I'll commit it in a day or two. > -- > Jonathan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 12:55:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id AC70C154D7 for ; Wed, 30 Jun 1999 12:55:13 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA07522; Wed, 30 Jun 1999 19:22:59 +0200 From: Luigi Rizzo Message-Id: <199906301722.TAA07522@labinfo.iet.unipi.it> Subject: Re: GRE encapsulation under FreeBSD 3.2 To: marc@netstor.com (Marc Nicholas) Date: Wed, 30 Jun 1999 19:22:59 +0200 (MET DST) Cc: jlemon@americantv.com, hackers@FreeBSD.ORG In-Reply-To: from "Marc Nicholas" at Jun 30, 99 03:53:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 501 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD > > >(although I might be blind)...anyone working on support it or is there > > >already an implementation? > > > > Yes, I've grabbed the GRE support from NetBSD, and have it working > > here (as far as I can tell). I'll commit it in a day or two. in addition i seem to remember that there is a (userland ?) daemon providing this, only thing is i cant' recall the name and it wasn't something obvious cheers luigi > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 13:18:31 1999 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 A0B8F14C07 for ; Wed, 30 Jun 1999 13:18:14 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id DAA88997; Thu, 1 Jul 1999 03:17:04 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 1 Jul 1999 03:17:03 +0700 (NSS) From: Max Khon To: John Polstra Cc: hackers@freebsd.org Subject: Re: dlopen returns non NULL In-Reply-To: <199906301817.LAA07050@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 30 Jun 1999, John Polstra wrote: > > in the following code `dlopen' returns NULL > > on the first iteration (because g() is not defined) -- it's ok > > but on the second iteration `dlopen' returns "valid" dlh > > ELF or a.out? Which version of FreeBSD? > > For a.out, it's a known bug and there is already an open PR on it. > I wouldn't be surprised if the bug existed in ELF too. 3.2-STABLE built on 10 Jun, ELF /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 13:28:13 1999 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 E2D9015646 for ; Wed, 30 Jun 1999 13:27:56 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id VAA74140; Wed, 30 Jun 1999 21:01:04 +0100 (BST) (envelope-from nik) Date: Wed, 30 Jun 1999 21:01:03 +0100 From: Nik Clayton To: Constantine Shkolny Cc: "hackers@FreeBSD.ORG" Subject: Re: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)) Message-ID: <19990630210102.A72675@catkin.nothing-going-on.org> References: <01BEBFCB.F95F6F00.stan@osgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <01BEBFCB.F95F6F00.stan@osgroup.com>; from Constantine Shkolny on Sat, Jun 26, 1999 at 12:03:59PM -0500 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry it's taken me a while to reply to this; ironically, most of my time has been spent on freebsd-doc recently. On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote: > I've come to understanding that lack of documentation is probably one of > the factors that keep the system healthy, I've just spent five minutes trying to phrase a reply to this that manages to convey my complete disagreement without resorting to profanity. You're talking bollocks. Sorry, I failed. I'm the lesser man for it, I know, and I can only pledge to widen my reading (or buy a set of Shakesperean Insult Fridge Magnets) so that it doesn't happen again. > because it keeps the unskilled people away. And it keeps the skilled people away. You have two systems, one documented, one not. You're looking for something to work on, but don't have a great deal of free time to spend. Which one do you work on? Matthew Dillon, a FreeBSD contributor who has been improving FreeBSD's virtual memory subsystem, NFS implementation, and various other bits and pieces, recently said (in <199906262123.OAA04029@apollo.backplane.com> on the committers@freebsd.org mailing list) [...] I guessed I freaked some people out when I declared that I wanted to work on the VM system, discussions in the first few months went with half of core talking to me like I didn't know jack when I do know at least jack, but had to come up to speed on FreeBSDisms in the code and the utter lack of documentation. [...] That quote is from part of a message on another topic (and one which is off-topic for -hackers). Matt's a very talented coder. But he still has to come up to speed on how things have been done on the FreeBSD project, and how we've diverged from published documentation (such as "The Design and Implementation") before he can do useful work. In this respect, Matt's one of the good guys. Not only has he done some sterling coding, but he's also taken the time to contribute documentation explaining not only what he's done, but also what other code in FreeBSD does, and more importantly, *why it does it that way*. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 13:38:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 74C8715660 for ; Wed, 30 Jun 1999 13:38:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id NAA05736; Wed, 30 Jun 1999 13:38:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA07449; Wed, 30 Jun 1999 13:38:08 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 30 Jun 1999 13:38:08 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Max Khon Subject: Re: dlopen returns non NULL Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Max Khon wrote: >> For a.out, it's a known bug and there is already an open PR on it. >> I wouldn't be surprised if the bug existed in ELF too. > > 3.2-STABLE built on 10 Jun, ELF Thanks for the info. Could you please do a send-pr on this bug, and tell me the PR number? Then I'll assign myself as the resposible person. Please be sure to state that it's the ELF dynamic linker. If you're in a big hurry and would like to work on it yourself, the relevant code is in "src/libexec/rtld-elf/rtld.c" in the function dlopen() near the comment that says "XXX - Clean up properly after an error." :-) The fix may be as simple as calling unref_object_dag() from the failure cases there, but it will need careful checking. Some additional changes may be needed in load_needed_objects() near the comment that says "XXX - cleanup." :-) Thanks, John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 14:12:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from playground.machaon.ru (MACHAON.rusmedia.net [195.230.80.14]) by hub.freebsd.org (Postfix) with ESMTP id A931014DFB for ; Wed, 30 Jun 1999 14:12:11 -0700 (PDT) (envelope-from dima@bog.msu.su) Received: from zippy.machaon.ru (ws-134.machaon.ru [195.230.75.134] (may be forged)) by playground.machaon.ru (8.9.2/8.9.2) with ESMTP id BAA69800; Thu, 1 Jul 1999 01:11:54 +0400 (MSD) (envelope-from dima@bog.msu.su) Date: Thu, 1 Jul 1999 01:11:50 +0400 (MSD) From: Dmitry Khrustalev X-Sender: dima@zippy.machaon.ru To: Jonathan Lemon Cc: hackers@FreeBSD.ORG Subject: Re: GRE encapsulation under FreeBSD 3.2 In-Reply-To: <199906301934.OAA14468@free.pcs> 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, 30 Jun 1999, Jonathan Lemon wrote: > In article you write: > >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD > >(although I might be blind)...anyone working on support it or is there > >already an implementation? > Beware, there is nasty crash when no less specific route is present. As a result, system cannot boot with existing rc.network machinery when gre0 is enabled in rc.conf. You can get my workaround at http://www.machaon.ru/~dima/gre.tar.gz -Dima > Yes, I've grabbed the GRE support from NetBSD, and have it working > here (as far as I can tell). I'll commit it in a day or two. > -- > Jonathan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 14:15:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 710) id 1631815719; Wed, 30 Jun 1999 14:15:11 -0700 (PDT) Date: Wed, 30 Jun 1999 14:15:10 -0700 From: Tim Vanderhoek To: Nik Clayton Cc: Constantine Shkolny , "hackers@FreeBSD.ORG" Subject: Re: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)) Message-ID: <19990630141510.A75094@hub.freebsd.org> References: <01BEBFCB.F95F6F00.stan@osgroup.com> <19990630210102.A72675@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990630210102.A72675@catkin.nothing-going-on.org>; from Nik Clayton on Wed, Jun 30, 1999 at 09:01:03PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 09:01:03PM +0100, Nik Clayton wrote: > On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote: > > I've come to understanding that lack of documentation is probably one of > > the factors that keep the system healthy, > > I've just spent five minutes trying to phrase a reply to this that manages > to convey my complete disagreement without resorting to profanity. I just want to publically state for the record that if we ever re-instate the position of FreeBSD president, I'm voting for Nik. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 14:45:44 1999 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 D209014DCC for ; Wed, 30 Jun 1999 14:45:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA00952; Wed, 30 Jun 1999 15:45: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 PAA32988; Wed, 30 Jun 1999 15:44:03 -0600 (MDT) Message-Id: <199906302144.PAA32988@harmony.village.org> To: John Polstra Subject: Re: tcpdump(1) additions. Cc: mph@astro.caltech.edu, hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 30 Jun 1999 11:26:17 PDT." <199906301826.LAA07099@vashon.polstra.com> References: <199906301826.LAA07099@vashon.polstra.com> <19990630011532.A97926@dragon.nuxi.com> Date: Wed, 30 Jun 1999 15:44:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906301826.LAA07099@vashon.polstra.com> John Polstra writes: : I would say it is not _acceptable_. The code shouldn't go into our : source tree until the known buffer overflow problems have been fixed. : It's just stupid to add buffer overflow problems to a program that is : always run as root. With my security officer hat on, I would *VETO* inclusion of any buffer overflows that have been pointed out and that the author has been too stuborn to fix. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 14:52:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 322A014DCC for ; Wed, 30 Jun 1999 14:52:26 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA84055 for ; Wed, 30 Jun 1999 17:52:25 -0400 (EDT) Message-Id: <199906302152.RAA84055@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 3.2-19990630-STABLE: ATAPI 1.1: unknown phase Date: Wed, 30 Jun 1999 17:52:25 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The error message in the subject (atapi 1.1: unknown phase) has plagued me for some time... everything still works, it just displays that error on the first access to the disk... untill today. Today I am trying to install FreeBSD 3.2 (19990630) from CDROM. It hangs on probing devices (likely acd0), however if I boot to the system already there (this is an upgrade, the system was originally installed via NFS) I can access the CDROM with only the aforementioned "warning". Any ideas? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 14:55:38 1999 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 A2A81156C5 for ; Wed, 30 Jun 1999 14:55:24 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA01512 for ; Wed, 30 Jun 1999 17:50:24 -0400 (EDT) Message-Id: <199906302150.RAA01512@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 30 Jun 1999 16:47:41 -0400 To: hackers@freebsd.org From: Dennis Subject: mbufs question/problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a customer who has been experiencing "slow downs" with a freebsd router....they have substantially increased performance by reducing MINCLSIZE. I havent tracked the source, but im trying to hypothesize what it might be. On the surface I cant see any relationship since very few routines seem dependent on that value (m_devget() in particular, but I dont believe they are using any driver that use it). Is it possible that they are running out of small mbufs (they have NMBCLUSTERS set to a very high value)? Any ideas would be helpful. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 15: 4:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mcclure.tinet.ie (mcclure.tinet.ie [159.134.237.31]) by hub.freebsd.org (Postfix) with ESMTP id 1B5FB14DB1 for ; Wed, 30 Jun 1999 15:04:11 -0700 (PDT) (envelope-from crypt0genic@tinet.ie) Received: from p33.as2.cork1.tinet.ie ([159.134.229.33] helo=tweak.home) by mcclure.tinet.ie with esmtp (Exim 2.05 #23) id 10zSSg-0007cQ-00; Wed, 30 Jun 1999 23:04:10 +0100 Received: (from crypt0genic@localhost) by tweak.home (8.9.3/8.9.3) id XAA52859; Wed, 30 Jun 1999 23:02:45 GMT Date: Wed, 30 Jun 1999 23:01:51 +0000 From: crypt0genic To: David Miller Cc: freebsd-hackers@freebsd.org Subject: Re: DVD-ram Message-ID: <19990630230151.B52815@ecad.org> References: <19990630103135.A315@ecad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from David Miller on Wed, Jun 30, 1999 at 03:22:29PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Miller (dmiller@search.sparks.net) [990630 22:58]: > On Wed, 30 Jun 1999, crypt0genic wrote: > > IDE interface I take it? This is the normal message for a CD. No, its SCSI, im using a adaptec adapter. Keep in mind that i am unfamiliar with SCSI devices so I might allready be doing/have done something stupid ; ) -crypt0genic > > > I didn't realize it until we used it under 95/98, but the DVD-ram appears > to act like an MO drive. IE, one can add, remove, change files at will. > I may hack the od driver in the next couple of days to see if it will work > at all. > -- Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. Public PGP key: http://www.ecad.org/crypt0genic_pgp_key Website: http://www.ecad.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 15: 8:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 9ABFB15765 for ; Wed, 30 Jun 1999 15:08:28 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA27043; Wed, 30 Jun 1999 15:07:21 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA03148; Wed, 30 Jun 1999 15:07:22 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17007; Wed, 30 Jun 99 15:07:17 PDT Message-Id: <377A9515.86415512@softweyr.com> Date: Wed, 30 Jun 1999 16:07:17 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "David E. Cross" Cc: Miguel Gilly , hackers@FreeBSD.ORG Subject: Re: Redundant Remote Webserver clustering References: <199906300037.UAA65916@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > Wes Peters wrote: > > > You do this on FreeBSD (or Linux or Solaris) by creating a "layer 4 > > router" or HTTP switch that directs traffic evenly among your several > > web servers, and stops sending traffic to servers that have failed. > > Where could someone find information on setting this up, and what software > to use? Eddieware: http://www.eddieware.org/ > I have someone who would be very interested in this. Isn't the > "layer 4 router" a SPoF though? What does "layer 4 router" have to do with the Association of Swedish Patent Attorneys (www.spof.com)? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 15:25: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A29631584E for ; Wed, 30 Jun 1999 15:24:59 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA27274; Wed, 30 Jun 1999 15:22:53 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA03683; Wed, 30 Jun 1999 15:22:53 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17735; Wed, 30 Jun 99 15:22:49 PDT Message-Id: <377A98B9.7559B731@softweyr.com> Date: Wed, 30 Jun 1999 16:22:49 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Boris Popov Cc: Bill Fumerola , Pierre Beyssac , hackers@FreeBSD.ORG Subject: Re: tcpdump(1) additions. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Popov wrote: > > Hope it will be possible. The samba team is very restrictive about > BSD-style license. As result I can say that smbfs for FreeBSD doesn't > contain any GPLd code from Linux's smbfs. > > BTW, does anybody have objections about name of this file system > in FreeBSD ? Should we consider changing it to cifs, to follow the Microsnot name du jour? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 15:35:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [207.113.133.228]) by hub.freebsd.org (Postfix) with ESMTP id 51C1614D3F for ; Wed, 30 Jun 1999 15:35:44 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: from lunatic.oneinsane.net (insane@lunatic.oneinsane.net [207.113.133.231]) by the.oneinsane.net (8.9.3/8.9.3) with ESMTP id PAA14348 for ; Wed, 30 Jun 1999 15:35:43 -0700 (PDT) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.3/8.9.3) id PAA32069 for freebsd-hackers@freebsd.org; Wed, 30 Jun 1999 15:35:42 -0700 (PDT) (envelope-from insane) Date: Wed, 30 Jun 1999 15:35:42 -0700 From: "Ron 'The InSaNe One' Rosson" To: freebsd-hackers@freebsd.org Subject: Re: GRE encapsulation under FreeBSD 3.2 Message-ID: <19990630153542.A31833@lunatic.oneinsane.net> Reply-To: Ron Rosson References: <199906301934.OAA14468@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906301934.OAA14468@free.pcs>; from Jonathan Lemon on Wed, Jun 30, 1999 at 02:34:27PM -0500 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.2-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 3:33PM up 22:42, 2 users, load averages: 0.07, 0.10, 0.08 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999, Jonathan Lemon was heard blurting out: > In article you write: > >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD > >(although I might be blind)...anyone working on support it or is there > >already an implementation? > > Yes, I've grabbed the GRE support from NetBSD, and have it working > here (as far as I can tell). I'll commit it in a day or two. > -- > Jonathan > Does this mean NATD/VPN will work for the clients that are using M$ VPN? If so, the sooner the better for me. TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- If Windows 95 is the answer, it must've been an incredibly stupid question. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 15:40:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 521F81582C for ; Wed, 30 Jun 1999 15:40:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA36819; Wed, 30 Jun 1999 16:40:11 -0600 (MDT) (envelope-from ken) Message-Id: <199906302240.QAA36819@panzer.kdm.org> Subject: Re: DVD-ram In-Reply-To: <19990630230151.B52815@ecad.org> from crypt0genic at "Jun 30, 1999 11:01:51 pm" To: crypt0genic@ecad.org (crypt0genic) Date: Wed, 30 Jun 1999 16:40:11 -0600 (MDT) Cc: dmiller@search.sparks.net (David Miller), freebsd-hackers@FreeBSD.ORG From: "Kenneth D. Merry" 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 crypt0genic wrote... > * David Miller (dmiller@search.sparks.net) [990630 22:58]: > > On Wed, 30 Jun 1999, crypt0genic wrote: > > > > IDE interface I take it? This is the normal message for a CD. > > No, its SCSI, im using a adaptec adapter. Keep in mind that i am unfamiliar with SCSI devices so I might allready be doing/have done something stupid ; ) > > -crypt0genic > > > > > > I didn't realize it until we used it under 95/98, but the DVD-ram appears > > to act like an MO drive. IE, one can add, remove, change files at will. > > I may hack the od driver in the next couple of days to see if it will work > > at all. > > It's not SCSI. The acd driver is the ATAPI CD driver. If you had a SCSI DVD drive, it would show up as 'cd0'. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 17:43:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4055014E01 for ; Wed, 30 Jun 1999 17:43:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA41893; Wed, 30 Jun 1999 17:40:39 -0700 (PDT) (envelope-from dillon) Date: Wed, 30 Jun 1999 17:40:39 -0700 (PDT) From: Matthew Dillon Message-Id: <199907010040.RAA41893@apollo.backplane.com> To: Nik Clayton Cc: Constantine Shkolny , "hackers@FreeBSD.ORG" Subject: Re: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)) References: <01BEBFCB.F95F6F00.stan@osgroup.com> <19990630210102.A72675@catkin.nothing-going-on.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : [...] : : I guessed I freaked some people out when I declared that I wanted to : work on the VM system, discussions in the first few months went with : half of core talking to me like I didn't know jack when I do know at : least jack, but had to come up to speed on FreeBSDisms in the code : and the utter lack of documentation. : : [...] : :That quote is from part of a message on another topic (and one which is :off-topic for -hackers). : :Matt's a very talented coder. But he still has to come up to speed on how :things have been done on the FreeBSD project, and how we've diverged from :published documentation (such as "The Design and Implementation") before :he can do useful work. I like to call it "algorithmic rot". In otherwords, after a decade or two the kernel just isn't the squeeky clean implementation it could be. I get screamed at a lot when I try to clean the rot up, because half the time it involves not only documenting code but also rewriting routines that don't actually contain bugs in order to prevent future rot. Kinda like wood sealer. The KASSERT()s work that way too. You put them in to force out the bugs and to prevent new ones from entering. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 17:45:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasquatch.dannyland.org (sasquatch.dannyland.org [207.229.158.70]) by hub.freebsd.org (Postfix) with SMTP id A7B6B14F2F for ; Wed, 30 Jun 1999 17:45:23 -0700 (PDT) (envelope-from dannyman@sasquatch.dannyland.org) Received: (qmail 11754 invoked by uid 1000); 1 Jul 1999 00:45:21 -0000 Date: Wed, 30 Jun 1999 19:45:21 -0500 From: dannyman To: Ron 'The InSaNe One' Rosson Cc: freebsd-hackers@freebsd.org Subject: Re: GRE encapsulation under FreeBSD 3.2 Message-ID: <19990630194519.B24511@dannyland.org> References: <199906301934.OAA14468@free.pcs> <19990630153542.A31833@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990630153542.A31833@lunatic.oneinsane.net>; from Ron 'The InSaNe One' Rosson on Wed, Jun 30, 1999 at 03:35:42PM -0700 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 03:35:42PM -0700, Ron 'The InSaNe One' Rosson wrote: > Does this mean NATD/VPN will work for the clients > that are using M$ VPN? If so, the sooner the better for me. I second that but I'm in no particular hurry there. Supporting CHAP could be a pain? -d -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 18:13: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osgroup.com (unknown [38.229.41.6]) by hub.freebsd.org (Postfix) with ESMTP id 6537F156D4 for ; Wed, 30 Jun 1999 18:13:00 -0700 (PDT) (envelope-from stan@laurent.osgroup.com) Received: from localhost (stan@localhost) by osgroup.com (8.7.6/8.6.12) with SMTP id UAA10458 for ; Wed, 30 Jun 1999 20:02:06 -0500 Date: Wed, 30 Jun 1999 20:02:06 -0500 (CDT) From: Stan Shkolnyy To: hackers@FreeBSD.ORG Subject: Re: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)) In-Reply-To: <19990630210102.A72675@catkin.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 Wed, 30 Jun 1999, Nik Clayton wrote: > Sorry it's taken me a while to reply to this; ironically, most of my time > has been spent on freebsd-doc recently. > > On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote: > > I've come to understanding that lack of documentation is probably one of > > the factors that keep the system healthy, > > I've just spent five minutes trying to phrase a reply to this that manages > to convey my complete disagreement without resorting to profanity. But why did you do that? My posting was more stupid than clever and I'm sorry I posted it. I spent five minutes thinking about why people don't document their work. Those thoughts overloaded my weak brain and I decided that there must be some good in not documenting it and I came up with my idea. It sounded so wonderful at that time, that I hurried to share it with others :-) Kind people simply pressed 'D' in their pines but some cruel souls still want to punish me :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 20:14:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C8C7B14E60; Wed, 30 Jun 1999 20:14:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA02604; Thu, 1 Jul 1999 12:44:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA82696; Thu, 1 Jul 1999 12:44:31 +0930 (CST) Date: Thu, 1 Jul 1999 12:44:31 +0930 From: Greg Lehey To: Hui Huang Cc: FreeBSD Hackers Subject: Re: Could I do floating point calculation in the kernel program? Message-ID: <19990701124431.N79211@freebie.lemis.com> References: <377B21AB.D11FE5C3@ntc.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <377B21AB.D11FE5C3@ntc.nokia.com>; from Hui Huang on Thu, Jul 01, 1999 at 11:07:08AM +0300 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -hackers] On Thursday, 1 July 1999 at 11:07:08 +0300, Hui Huang wrote: > I want to add some floating point calculation functions in FreeBSD > kernel program. > I compiled the new kernel and installed it in a machine. However, the > new kernel could not be booted up with the error information "Fatal trap > > 22: FPU device not available while in kernel mode". > Does anybody know how to enable the FPU device in the kernel mode or > other methods to support floating point calculation in the kernel mode? This is probably more appropriate in -hackers than in -questions, so I've moved it there. Basically, you can't do this. In order to support FP in the kernel, the system would need to save FP state for every context switch, which would be a serious performance hit. Why do you need FP? Do you really need FP? Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 20:33:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id A9DF314CBE; Wed, 30 Jun 1999 20:33:34 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id XAA00848; Wed, 30 Jun 1999 23:32:42 -0400 (EDT) (envelope-from sjr) Message-Id: <199907010332.XAA00848@istari.home.net> Date: Wed, 30 Jun 1999 23:32:42 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: tcpdump(1) additions. To: billf@jade.chc-chimes.com Cc: hackers@freebsd.org, fenner@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Jun, Bill Fumerola wrote: > Unless there is strong feelings against it, I'd like to commit the smb > patches (as seen on www.samba.org) and ipsec/ike patches (recently mailed > to the tcpdump mailing list and bugs@FreeBSD.org) to tcpdump(1). > > Comments? If you do this, please work with Bill Fenner to close out bin/7877. Thanks, Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 22:56:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (Postfix) with ESMTP id DD9CB14D46 for ; Wed, 30 Jun 1999 22:56:45 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id WAA20860; Wed, 30 Jun 1999 22:56:43 -0700 (PDT) Date: Wed, 30 Jun 1999 22:56:43 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199907010556.WAA20860@math.berkeley.edu> To: freebsd-hackers@freebsd.org Subject: pccard problems Cc: dan@math.berkeley.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to configure a couple of pccards on a DELL Inspiron 3500 running FreeBSD 3.2-RELEASE. Neither card works: 1) The first card is some sort of DVD/MPEG-2 decoder card. It seems to be called a "DELL Margi". Whenever the card is inserted and pccardd is running, the entire system hangs so hard that console I/O no longer works. Even ctl-alt-del is ignored. The power button is ignored. I have to turn the machine off by poking a special hidden recessed button on the side with a paper clip. I don't expect to find a FreeBSD driver for this card, but I would prefer that having it physically installed didn't hang the system. 2) The second card is a "DELL 10/100 LAN+56K Modem CardBus by 3Com". A label on the back of the card says "Model 3CCFEM656". The command "pccardc dumpcis" reports: Configuration data for card in slot 1 Tuple #1, code = 0xff (Terminator), length = 0 I assume that pccardd cannot recognize and configure cards without configuration data. Is this card broken in some sense? Can anyone recommend a driver? Thanks, Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 30 23:52: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 7BF4A14C83; Wed, 30 Jun 1999 23:51:53 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA03325; Thu, 1 Jul 1999 16:21:51 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA87140; Thu, 1 Jul 1999 16:21:50 +0930 (CST) Date: Thu, 1 Jul 1999 16:21:50 +0930 From: Greg Lehey To: Dan Strick Cc: freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems Message-ID: <19990701162150.G82831@freebie.lemis.com> References: <199907010556.WAA20860@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907010556.WAA20860@math.berkeley.edu>; from Dan Strick on Wed, Jun 30, 1999 at 10:56:43PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 30 June 1999 at 22:56:43 -0700, Dan Strick wrote: > I am attempting to configure a couple of pccards on a DELL Inspiron 3500 > running FreeBSD 3.2-RELEASE. Neither card works: > > 1) The first card is some sort of DVD/MPEG-2 decoder card. It seems > to be called a "DELL Margi". Whenever the card is inserted and > pccardd is running, the entire system hangs so hard that console > I/O no longer works. Even ctl-alt-del is ignored. The power > button is ignored. I have to turn the machine off by poking a > special hidden recessed button on the side with a paper clip. > > I don't expect to find a FreeBSD driver for this card, but I would > prefer that having it physically installed didn't hang the system. Indeed. Is it possibly interrupting on a line which something else is using? I've found a problem on my Latitude where it appears that the machine only has two interrupts free (3 and 9). If I put a modem on 3 and an Ethernet board on 9, it works, but only by putting pccardd on irq 5, which doesn't really work. If I pull the Ethernet card, the whole machine hangs up when I try to access the net, presumably because pccardd hasn't found out about it. > 2) The second card is a "DELL 10/100 LAN+56K Modem CardBus by 3Com". > A label on the back of the card says "Model 3CCFEM656". > > The command "pccardc dumpcis" reports: > > Configuration data for card in slot 1 > Tuple #1, code = 0xff (Terminator), length = 0 > > I assume that pccardd cannot recognize and configure cards without > configuration data. Is this card broken in some sense? Can anyone > recommend a driver? I've seen this kind of problem on my Latitude laptop after running Microsoft. It seems that Microsoft sets the board state in such a way that a simple reboot doesn't reset it, and this is the result. If I power down the machine and then boot it with FreeBSD, I don't have any problems. Have you tried that? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 1:36:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kang.tinet.ie (kang.tinet.ie [159.134.237.28]) by hub.freebsd.org (Postfix) with ESMTP id 3679A14CB4 for ; Thu, 1 Jul 1999 01:36:44 -0700 (PDT) (envelope-from crypt0genic@tinet.ie) Received: from p82.as2.cork1.tinet.ie ([159.134.229.82] helo=tweak.home) by kang.tinet.ie with esmtp (Exim 2.05 #23) id 10zcKo-0008B1-00; Thu, 1 Jul 1999 09:36:42 +0100 Received: (from crypt0genic@localhost) by tweak.home (8.9.3/8.9.3) id JAA00245; Thu, 1 Jul 1999 09:35:02 GMT Date: Thu, 1 Jul 1999 09:34:08 +0000 From: crypt0genic To: "Kenneth D. Merry" Cc: David Miller , freebsd-hackers@FreeBSD.ORG Subject: Re: DVD-ram Message-ID: <19990701093408.A238@ecad.org> References: <19990630230151.B52815@ecad.org> <199906302240.QAA36819@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906302240.QAA36819@panzer.kdm.org>; from Kenneth D. Merry on Wed, Jun 30, 1999 at 04:40:11PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kenneth D. Merry (ken@plutotech.com) [990701 07:56]: > No, its SCSI, im using a adaptec adapter. Keep in mind that i am unfamiliar with SCSI devices so I might allready be doing/have done something stupid ; ) > > > > It's not SCSI. The acd driver is the ATAPI CD driver. If you had a SCSI > DVD drive, it would show up as 'cd0'. Sorry, the actual dmesg for the device is cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [1218960 x 2048 byte records] I apologise for the confusion. -crypt0genic -- Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. Public PGP key: http://www.ecad.org/crypt0genic_pgp_key Website: http://www.ecad.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 2:20: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id 546C414BB8 for ; Thu, 1 Jul 1999 02:19:57 -0700 (PDT) (envelope-from clc@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id RAA13997 for ; Thu, 1 Jul 1999 17:19:55 +0800 (HKT) Received: (from clc@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id RAA04587 for freebsd-hackers@freebsd.org; Thu, 1 Jul 1999 17:19:53 +0800 (HKT) Date: Thu, 1 Jul 1999 17:19:53 +0800 (HKT) From: Clarence Chu Message-Id: <199907010919.RAA04587@b1.hkstar.com> To: freebsd-hackers@freebsd.org Subject: Annoucing: FreeBSD-3.2-Express, a multi-filesystem capable FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all, It is to announce the availability of FreeBSD-3.2-Express on ftp://ftp.freebsd.org/pub/FreeBSD/development/3.2-express. FreeBSD-3.2-Express is now capable of being hosted on local/remote disk drives of FAT/NTFS/UFS/EXT2FS/NFS and ISO-9660 to take the benefits of harddisk and/or network performance. One don't even need any CD-writer nor CD-ROM to play with FreeBSD. Compared to FreeBSD-3.1-Express, most user configurable files are now placed on the MFS, memory file system, and are user customisable. Tools for backup , 'snap' and 'resume' are shell scripts to ease re-configurations. Also, 'express.sh' under /misc may be used to install the contents of 3.2-Express onto installed 3.2-RELEASE. Numerous packages had been added, such as CORBA 2 compliant ILU, OODBMS PostgreSQL-6.5, File manager XFM, gimp-1.1.5, lyx-1.0.2, abs-0.6a, apache-1.3.6, webmin-0.72, xwpe, ddd-3.1.5, jdk1.1.8-elf, lesstif-0.88.1, samba-2.0.4b, mars_nwse, netatalk-asun, fwtk-2.1, Xvnc-3.3.2, mapedit, acroread, mpsql-2.1, python-1.5.2, ssh. Also, the kernel had been upgraded to include ipfw capability featuring DUMMYNET bandwidth management and BRIDGE. bpf, ccd-capable, vinum, svr4, nwfs as loadable modules. lesstif's mwm, mlvwm(mac lookalike) and qvwm(windows lookalike) are window-manager switchable on the fly, Xwindow configurations being a one-click distance under xfm, editor of vi, ee, vim, nedit of choices. shells of sh, csh, ksh, bash, tcsh for to be choose among. cxterm been configured for both big5 and gb encoding and xcin installed. Xservers are now true-type-font capable. If you're to view the contents of packages on FreeBSD-3.2-Express, please read the MANIFEST.TXT on the CD. Enclosed is the README.TXT found on the url above. Enjoy, -- Best wishes, / ___/ / ___/ Clarence Chu / / / clc@hkstar.com ____/ ____/ ____/ http://www.hkstar.com/~clc Encl. FreeBSD-3.2-EXPRESS ======================================== (C) Copyright 1999 Data Expert Limited. All rights reserved. Running the CD -------------- If you do not have access to a bootable CD-ROM drive for running, you will have to generate two 1.44MB bootable floppies under \INSTALL\kern.flp and \INSTALL\mfsroot.flp by using \INSTALL\fdimage.exe under DOS, consult \INSTALL\README.TXT. vn(4), vinum(8), ccd(4), mount_ntfs(8), mount_ext2fs(8), mount_nwfs(8), mount_cd9660(8), smbclient(8), mount_msdos(8) as well as mount_nfs(8) are working on the CD. To use X-window System with only the CD, optinally configure the network details and choose "eXpress". A default XF86Config file had been placed under /etc, for resolution of 1024x768-8bpp of SVGA compatible card. you may run "x11 [gui]", "startx", "xinit", "xlogin [hostname]" or "Xwrapper " to start the X-window System. If the XF86Config does not match your hardware, reconfigure it by "xf86config" or "XF86Setup". Xdm had been started for network connections, users may login from their X-server and may execute the X-clients. Lpd, httpd, sendmail and webmin for administration had been started, too. Xvnc had been installed, try http://:5800+DISPLAY_NO/ after running 'vncserver' script. About 200 packages of all types had been installed onto the CD as executable binaries, please consult /MANIFEST.TXT on the CD by www browsers. Quick installation of XF86Config for 1152x900, 1024x768, 800x600 and 640x480 with depth 8/16/24/32 is provided. Issue "1152 3" for 1152x900 with 24bpp, "1024i 2" for 1024x768 with 16bpp for interlaced display, etc. Release Notes ------------- a) Visit http://www.freebsd.org for general information. b) SVR4 emulation do work on the CD, /cdrom/misc/svr4.txt c) Linux emulation works, consult /cdrom/misc/staroffice.txt d) Netware clients had been added, see /cdrom/misc/ipx.html e) Ntfs (smbclient on CD) added, mount_ntfs(8) and smbclient(8) f) For professional support, visit http://www.dexpert.com. FreeBSD-3.2-Express How to run it most efficiently ======================================= FreeBSD-3.2-Express is capable of running even without a local CD-ROM drive. Just prepare the ISO-9660 image (by your favorite cdrecording software or dd(1) of any *nix), and place it onto your FAT/NTFS/UFS/EXT2FS/NFS drive space. Then use the /INSTALL/*.flp floppies or the 3.2-Express CD to boot up the box. By using the HoloShell of the 3.2-express main menu, mount the iso-image onto the /dist directory of the HoloShell and exit the shell. FreeBSD-3.2-Express will fire up upon request to enter the 'Express mode'. There is even two life examples on entering the shell. In so doing, the media in use will either be local harddisk or NFS which is several ten-folds of drive access performance. And when you see the Express-Menu, the floppies may be used on other machines. It is in the rarest case, e.g. in demo room of computer stores, to use FreeBSD-3.2-Express on CD basis. i.e. if you have the 650MB drive space, use it! In additions, if you have one FreeBSD-3.2-Express running on a local disk, you may use the /dist directory contents on all your local network: because, the /dist filesystem had been exported as an NFS share. I would like to illustrate the scenerio with an example: That there is few networked machines with, say, Windoz-98 going to run FreeBSD-3.2-Express. The first thing to look for is a single machine with more than 650MB spare disk space, with supported LAN card and more than 64MB RAM. 1) Prepare the ISO-9660 image of FreeBSD-3.2-Express and load it onto the machine, say, on C:\32exprs.img. 2) Boot the machine with either the floppies under INSTALL/ or the FreeBSD-3.2-Express CD 3) When the 3.2-Express Menu appears, configure the Network 4) Enter the Shell 5) follow the examples to mount the C:\32exprs.img onto /dist e.g. # mount_msdos /dev/wd0a /mnt # vnconfig -e /dev/vn0 /mnt/32exprs.img # mount_cd9660 /dev/vn0 /dist 6) exit the shell and fireup Express-mode 7) you may even forget about XF86Setup if you're not to use X there. 8) Go to other machine and boot them with 3.2-express media 9) And go to the shell after network configurations. 10) use 'mount_nfs :/dist /dist' and exit the shell 11) Upon entering Express-mode, another FreeBSD station will be up. The description is rather verbose, but imagine the convenience it had brought forth. Without patitioning of the local disk and scrifice of disk performance by using CD-ROM to be secondary storage, the overall performance of FreeBSD-3.2-Express should be comparable to the installed counterpart. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 2:51:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailserver.display-umea.se (mailserver.display-umea.se [194.165.230.48]) by hub.freebsd.org (Postfix) with ESMTP id 37F3E14F33 for ; Thu, 1 Jul 1999 02:51:38 -0700 (PDT) (envelope-from meyer@display-umea.se) Received: from localhost (meyer@localhost) by mailserver.display-umea.se (8.8.8/8.8.8) with ESMTP id MAA22388 for ; Thu, 1 Jul 1999 12:00:28 +0200 (CEST) (envelope-from meyer@display-umea.se) Date: Thu, 1 Jul 1999 12:00:27 +0200 (CEST) From: Erik Meyer To: freebsd-hackers@freebsd.org Subject: Webcams? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm planning of setting up a webcam under freebsd (4.0-CURRENT) What webcams work good with FreeBSD? thnx in advance /* Erik Meyer erik-m@display-umea.se */ /* work(+46(0)90177963) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 3:46:26 1999 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 9634E15345 for ; Thu, 1 Jul 1999 03:46:21 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA78073; Thu, 1 Jul 1999 12:46:12 +0200 (CEST) (envelope-from des) To: crypt0genic Cc: David Miller , freebsd-hackers@FreeBSD.ORG Subject: Re: DVD-ram References: <19990630103135.A315@ecad.org> From: Dag-Erling Smorgrav Date: 01 Jul 1999 12:46:11 +0200 In-Reply-To: crypt0genic's message of "Wed, 30 Jun 1999 10:31:35 +0000" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG crypt0genic writes: > I have a Lacie DVD-RAM drive, it work great under windows, here is the DMESG i g > et from it, I hope this is of some help. LaCie don't make drives, they just package them in ugly boxes with noisy fans. One of my cow-orkers (with whom I share an office) had an external LaCie disk hooked up to his Mac until I threatened to pour Coca Cola into the PSU (this was after I'd hinted several times that the handles on his G3 would serve very well for chucking it out the window) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 4: 6:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mcclure.tinet.ie (mcclure.tinet.ie [159.134.237.31]) by hub.freebsd.org (Postfix) with ESMTP id A000A14EE3 for ; Thu, 1 Jul 1999 04:06:43 -0700 (PDT) (envelope-from crypt0genic@tinet.ie) Received: from p82.as2.cork1.tinet.ie ([159.134.229.82] helo=tweak.home) by mcclure.tinet.ie with esmtp (Exim 2.05 #23) id 10zefx-0003Zb-00; Thu, 1 Jul 1999 12:06:42 +0100 Received: (from crypt0genic@localhost) by tweak.home (8.9.3/8.9.3) id MAA01763; Thu, 1 Jul 1999 12:05:11 GMT Date: Thu, 1 Jul 1999 12:05:10 +0000 From: crypt0genic To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DVD-ram Message-ID: <19990701120510.A1530@ecad.org> References: <19990630103135.A315@ecad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Dag-Erling Smorgrav on Thu, Jul 01, 1999 at 12:46:11PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav (des@flood.ping.uio.no) [990701 11:47]: > > LaCie don't make drives, they just package them in ugly boxes with > noisy fans. Im not sure what model you are refering too, but the drive I have is in a stylish external box with a fan that doesnt make a whisper on noise, It also doesnt make any sound when reading/writeing. The unit is so sturdy I rekon I could through it at a brick wall without damaging it! Overall Im very pleased with this piece of hardware and when it is supported under freebsd it will be one of my most prised devices. : ) -crypt0genic -- Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. Public PGP key: http://www.ecad.org/crypt0genic_pgp_key Website: http://www.ecad.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 4:55: 5 1999 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 5AFDC156E9 for ; Thu, 1 Jul 1999 04:55:00 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id NAA79583; Thu, 1 Jul 1999 13:54:54 +0200 (CEST) (envelope-from des) To: crypt0genic Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: DVD-ram References: <19990630103135.A315@ecad.org> <19990701120510.A1530@ecad.org> From: Dag-Erling Smorgrav Date: 01 Jul 1999 13:54:53 +0200 In-Reply-To: crypt0genic's message of "Thu, 1 Jul 1999 12:05:10 +0000" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG crypt0genic writes: > * Dag-Erling Smorgrav (des@flood.ping.uio.no) [990701 11:47]: > > LaCie don't make drives, they just package them in ugly boxes with > > noisy fans. > Im not sure what model you are refering too, but the drive I have is > in a stylish external box with a fan that doesnt make a whisper on > noise, It also doesnt make any sound when reading/writeing. The unit > is so sturdy I rekon I could through it at a brick wall without > damaging it! Overall Im very pleased with this piece of hardware and > when it is supported under freebsd it will be one of my most prised > devices. : ) The box may look solid, but the drive inside is a standard OEM component (Matshita, IIRC) which would certainly not survive the impact, no matter how sturdy an enclosure it's in - unless the enclosure has internal shock mounts, which would frankly surprise the hell out of me given LaCie's generally low prices. You get what you pay for. And the fan may be nice and silent now, but how do you know that'll last? My cow-orker's unit was two months old when the fan started screaming like a butchered pig. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 5:28: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 18F5A14DA5 for ; Thu, 1 Jul 1999 05:27:48 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Thu, 01 Jul 1999 13:27:32 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id N96YDLJ7; Thu, 1 Jul 1999 13:18:32 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10zfwI-000Asj-00 for hackers@freebsd.org; Thu, 1 Jul 1999 13:27:38 +0100 Date: Thu, 1 Jul 1999 13:27:38 +0100 To: hackers@freebsd.org Subject: Postfix license update. Message-Id: <19990701132738.A41789@palmerharvey.co.uk> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to let you all know, it appears that the termination clause has been dropped, but it appears to have gained a gpl-like "must make source available" clause. http://msgs.securepoint.com/cgi-bin/get/postfix9906/103.html (and where I found it) http://www.lwn.net/1999/0701/a/postfix.html -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 5:30:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id 0C81215736 for ; Thu, 1 Jul 1999 05:30:52 -0700 (PDT) (envelope-from jesper@freesbee.t.dk) Received: (qmail 29436 invoked by uid 1001); 1 Jul 1999 12:30:51 -0000 Date: Thu, 1 Jul 1999 14:30:50 +0200 From: Jesper Skriver To: Dominic Mitchell Cc: hackers@freebsd.org Subject: Re: Postfix license update. Message-ID: <19990701143050.J25338@skriver.dk> References: <19990701132738.A41789@palmerharvey.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <19990701132738.A41789@palmerharvey.co.uk>; from Dominic Mitchell on Thu, Jul 01, 1999 at 01:27:38PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 01:27:38PM +0100, Dominic Mitchell wrote: > Just to let you all know, it appears that the termination clause has > been dropped, but it appears to have gained a gpl-like "must make source > available" clause. > > http://msgs.securepoint.com/cgi-bin/get/postfix9906/103.html > > (and where I found it) > > http://www.lwn.net/1999/0701/a/postfix.html This has been discussed at the postfix-users@postfix.org mailing list, just download the newest version, and you will see it .. /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 7:44:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id EB0C0157A4; Thu, 1 Jul 1999 07:44:32 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA28235; Thu, 1 Jul 1999 16:44:31 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA94189; Thu, 1 Jul 1999 16:44:30 +0200 (MET DST) Date: Thu, 1 Jul 1999 16:44:30 +0200 From: Eivind Eklund To: Dag-Erling Smorgrav Cc: Ruslan Ermilov , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Message-ID: <19990701164430.O92508@bitbox.follo.net> References: <199907011133.EAA64244@freefall.freebsd.org> <19990701135124.I92508@bitbox.follo.net> <19990701154210.A12020@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Dag-Erling Smorgrav on Thu, Jul 01, 1999 at 03:03:12PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 03:03:12PM +0200, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > On Thu, Jul 01, 1999 at 01:51:24PM +0200, Eivind Eklund wrote: > > > On Thu, Jul 01, 1999 at 04:33:37AM -0700, Ruslan Ermilov wrote: > > > > - separate the pftp and FTP_PASSIVE_MODE tests so gate mode works again > > > > PR: bin/12070 > > > > > > > > - specifically check that FTP_PASSIVE_MODE is set to YES, rather than > > > > just checking if it is defined > > > > > > We elected to change our defaults to having passive mode enabled - it > > > sounds to me like it should explicitly check for FTP_PASSIVE_MODE=NO, > > > not vice versa. > > [for some reason, Eivind's mail hasn't reached me yet] This is because my mail was a private mail to Ruslan, because I didn't feel that the issue was worth filling the committers list with (or really, interesting for anybody but me and the author of the code, which I thought was Ruslan). As it seems Ruslan feels differently, I'm keeping a public Cc:, but moving to -hackers. > Eivind: what Ruslan just did was MFC some patches I committed a week > or two ago but hadn't come around to MFCing yet (these were the > patches I mentioned yesterday). If you had any objections, you should > have raised them back then... Sorry; didn't notice back then. > * 'unset FTP_PASSIVE_MODE' (or hack login.conf), which always worked > > * set FTP_PASSIVE_MODE=NO, which didn't work before the patch, > because ftp(1) would just notice that FTP_PASSIVE_MODE was defined > and assume it meant it should use passive mode. > > Some may find the second solution more obvious than the first; hence > the PR and my patches. > > Changing ftp(1) to check for FTP_PASSIVE_MODE=NO rather than the > reverse would gratuitously change ftp's reaction to its environment. Not at the first point this was done; it would avoid gratiously changing the reaction. Ie: Index: main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/ftp/main.c,v retrieving revision 1.18 diff -u -r1.18 main.c --- main.c 1999/06/25 14:11:15 1.18 +++ main.c 1999/07/01 14:41:35 @@ -135,7 +135,7 @@ cp = strrchr(argv[0], '/'); cp = (cp == NULL) ? argv[0] : cp + 1; if ((s = getenv("FTP_PASSIVE_MODE")) != NULL - && strcasecmp(s, "yes") == 0) + && strcasecmp(s, "no") != 0) passivemode = 1; if (strcmp(cp, "pftp") == 0) passivemode = 1; ... compared to the sources as of today. This gives minimal semantic difference from the way it worked before the change (which was that if FTP_PASSIVE_MODE existed, ftp used passive mode). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 7:50:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 41AD71578A for ; Thu, 1 Jul 1999 07:50:54 -0700 (PDT) (envelope-from steve@ns1.cioe.com) Received: (from steve@localhost) by ns1.cioe.com (8.9.3/8.9.3) id JAA10175 for freebsd-hackers@freebsd.org; Thu, 1 Jul 1999 09:50:52 -0500 (EST) (envelope-from steve) Date: Thu, 1 Jul 1999 09:50:52 -0500 (EST) From: Steve Ames Message-Id: <199907011450.JAA10175@ns1.cioe.com> To: freebsd-hackers@freebsd.org Subject: Lizard... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Everyone should take a peak at http://www.troll.no/announce/lizard.html if you haven't already. Definately take a look at the screenshots. Lizard is a fully graphical Linux installation for Caldera Systems Open Linux. IMO, having an easy, reliable and attractive installer is an excellent selling point. Just something to ponder... -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 8:51: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id B6E4114A13 for ; Thu, 1 Jul 1999 08:50:51 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA18160; Thu, 1 Jul 1999 10:50:49 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id KAA14123; Thu, 1 Jul 1999 10:50:48 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id KAA15509; Thu, 1 Jul 1999 10:50:47 -0500 (CDT) Date: Thu, 1 Jul 1999 10:50:47 -0500 (CDT) From: Jonathan Lemon Message-Id: <199907011550.KAA15509@free.pcs> To: insane@lunatic.oneinsane.net, hackers@freebsd.org Subject: Re: GRE encapsulation under FreeBSD 3.2 X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >On Wed, 30 Jun 1999, Jonathan Lemon was heard blurting out: > >> In article > you write: >> >I don't seem to see support for GRE (IP-in-IP encaspulation) in FreeBSD >> >(although I might be blind)...anyone working on support it or is there >> >already an implementation? >> >> Yes, I've grabbed the GRE support from NetBSD, and have it working >> here (as far as I can tell). I'll commit it in a day or two. >> -- >> Jonathan > >Does this mean NATD/VPN will work for the clients >that are using M$ VPN? If so, the sooner the better for me. Hmm, I don't know what that is, nor what relation it has to GRE. Do you hve an URL that would enlighten me? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 10:59:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D2FBC14EF0 for ; Thu, 1 Jul 1999 10:59:34 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA25913 for ; Thu, 1 Jul 1999 13:59:32 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA60430; Thu, 1 Jul 1999 13:59:32 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Jul 1999 13:59:32 -0400 (EDT) To: hackers@freebsd.org Subject: npx0 to set maxmem broken in -current? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14203.43667.496647.806250@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a user with a need to run a machine in varying memory configurations. The machine has 512MB & she needs to artificially constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB, 96MB, 128MB ...) I was planning on having her edit /kernel.config & change the value of iosize npx0 and have the bootloader do a load -t userconfig_script /kernel.config at boottime. However, this feature appears to be broken in current. The resource_int_value() call which grabs msize is returning ENOENT & we're seeing the full 512MB of ram. Is there any way around this, short of building her 16 different kernels? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 11:15:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id C248B14CBE for ; Thu, 1 Jul 1999 11:15:00 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 846AA8A; Fri, 2 Jul 1999 02:14:49 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Thu, 01 Jul 1999 13:59:32 -0400." <14203.43667.496647.806250@grasshopper.cs.duke.edu> Date: Fri, 02 Jul 1999 02:14:49 +0800 From: Peter Wemm Message-Id: <19990701181449.846AA8A@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > > I have a user with a need to run a machine in varying memory > configurations. The machine has 512MB & she needs to artificially > constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB, > 96MB, 128MB ...) > > I was planning on having her edit /kernel.config & change the value of > iosize npx0 and have the bootloader do a > > load -t userconfig_script /kernel.config > > at boottime. > > However, this feature appears to be broken in current. The > resource_int_value() call which grabs msize is returning ENOENT & > we're seeing the full 512MB of ram. > > Is there any way around this, short of building her 16 different > kernels? The npx0 tuneing hack has been broken for ages and never worked well anyway. Originally, it depended on dset working, because by the time userconfig ran, memory had already been sized and set up and it was way too late. However, dset would modify the kernel binary so that next time it ran the changes would be available early enough. Now it's even worse since the resource_* routines use the config(8) generated tables (see config.c) until malloc is up and running and then it switches over to using malloc for backing. Personally, I think we should use a kernel environment variable passed in from loader, since kern_envp is available *real early*, from the very beginning of init386(), which is called form locore just after going virtual. It needs a couple of tweaks to get this to work, and in particular, the environment variable will have to override the VM86 calls. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 11:20:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E71215614 for ; Thu, 1 Jul 1999 11:20:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA17764; Thu, 1 Jul 1999 11:20:48 -0700 Date: Thu, 1 Jul 1999 11:20:02 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <199907011450.JAA10175@ns1.cioe.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 Reminds me of SCO. I personally don't much like it- it makes it harder than hell to figure out what's gone wrong when it doesn't work. On Thu, 1 Jul 1999, Steve Ames wrote: > > Everyone should take a peak at http://www.troll.no/announce/lizard.html > if you haven't already. Definately take a look at the screenshots. > > Lizard is a fully graphical Linux installation for Caldera Systems > Open Linux. IMO, having an easy, reliable and attractive installer > is an excellent selling point. > > Just something to ponder... > > -Steve > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 11:34:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id EF2C71529C for ; Thu, 1 Jul 1999 11:34:44 -0700 (PDT) (envelope-from steve@ns1.cioe.com) Received: (from steve@localhost) by ns1.cioe.com (8.9.3/8.9.3) id NAA57517; Thu, 1 Jul 1999 13:34:32 -0500 (EST) (envelope-from steve) Date: Thu, 1 Jul 1999 13:34:32 -0500 (EST) From: Steve Ames Message-Id: <199907011834.NAA57517@ns1.cioe.com> To: mjacob@feral.com Subject: Re: Lizard... Cc: freebsd-hackers@freebsd.org In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG True... But such a configuration doesn't preclude the use of a more detailed listing on vty1 the way we do it now. With our current installation setup its similar to this already. Its text based and some of the menus are not exactly intuitive (No... I don't have a better suggestion just yet). If something goes wrong you don't really know what unless you look at the second vty (ALT-F2) and then (maybe) there is some good info there. I've had a lot of installs go awry with little information to explain to me what went wrong. Like you, I'd prefer a very primitive interface if it gave me lots more diagnostics. Joe Average, on the other hand, likes a spiffy, clean interface. We try to accomodate both types by having a simplistic install and then some detail output on a seperate VTY. This could still be done with an even spiffier graphical installation on the first VTY. Wonder if it utilizes the VGALIB? (Lizard that is) > Reminds me of SCO. I personally don't much like it- it makes it harder > than hell to figure out what's gone wrong when it doesn't work. > > On Thu, 1 Jul 1999, Steve Ames wrote: > > > > > Everyone should take a peak at http://www.troll.no/announce/lizard.html > > if you haven't already. Definately take a look at the screenshots. > > > > Lizard is a fully graphical Linux installation for Caldera Systems > > Open Linux. IMO, having an easy, reliable and attractive installer > > is an excellent selling point. > > > > Just something to ponder... > > > > -Steve > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 11:40:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BEED14FFA for ; Thu, 1 Jul 1999 11:40:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA17864; Thu, 1 Jul 1999 11:40:59 -0700 Date: Thu, 1 Jul 1999 11:40:13 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Steve Ames Cc: freebsd-hackers@freebsd.org Subject: Re: Lizard... In-Reply-To: <199907011834.NAA57517@ns1.cioe.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 it gave me lots more diagnostics. Joe Average, on the other hand, > likes a spiffy, clean interface. We try to accomodate both types by > having a simplistic install and then some detail output on a seperate > VTY. This could still be done with an even spiffier graphical installation > on the first VTY. Possibly. It's not clear what or who "Joe Average" is here. I suspect that 99% of all computer users (by volume) get their s/w preinstalled. The amount of sophistication of the remaining 1% who actually struggle through so-called "spiffy" installs is growing exponentially. Keeping a simple interface rather than trying to play human engineering with no real human interfaces lab and a 500K$ testing budget might be better. Just my 2 cents... I'll shut up now... (I mean, why should *I* beef so much? I'm not writing or maintaining sysinst...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 11:50: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 6639614D26 for ; Thu, 1 Jul 1999 11:50:04 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA19145; Thu, 1 Jul 1999 13:50:02 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id NAA11835; Thu, 1 Jul 1999 13:50:01 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id NAA15793; Thu, 1 Jul 1999 13:50:01 -0500 (CDT) Date: Thu, 1 Jul 1999 13:50:01 -0500 (CDT) From: Jonathan Lemon Message-Id: <199907011850.NAA15793@free.pcs> To: peter@netplex.com.au, hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Personally, I think we should use a kernel environment variable passed in >from loader, since kern_envp is available *real early*, from the very >beginning of init386(), which is called form locore just after going >virtual. It needs a couple of tweaks to get this to work, and in >particular, the environment variable will have to override the VM86 >calls. You'd still have to perform the VM86 calls, since one of the things they do is generate a map of where the useable memory segments are. The environment variable would be used later (at the same point where the npx0 hack is) in order to cap Maxmem. I like the idea of being able to say: set console=comconsole set maxmem=.... boot -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 12: 7:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 71DAC14A14 for ; Thu, 1 Jul 1999 12:07:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA68743; Thu, 1 Jul 1999 12:05:56 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-reply-to: Your message of "Thu, 01 Jul 1999 11:40:13 PDT." Date: Thu, 01 Jul 1999 12:05:55 -0700 Message-ID: <68739.930855955@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > through so-called "spiffy" installs is growing exponentially. Keeping a > simple interface rather than trying to play human engineering with no > real human interfaces lab and a 500K$ testing budget might be better. > Just my 2 cents... I'll shut up now... (I mean, why should *I* beef so > much? I'm not writing or maintaining sysinst...) OK, I'll add a few comments to this. I've looked at the screen shots to lizard and have to say that for a certain type of user, it looks pretty approachable. That type of user is specifically the Windows user, someone who'll have certain assumptions about how dialogs look, what kinds of questions they're asked and so on. It's clear from looking at the screenshots that Lizard tries to be extremely Windows-like and that's probably going to make a reasonable number of people happy; if it's what they're used to, there's really no arguing the point. However, we're also not going for the desktop market quite as aggressively head-on as Caldera is and we have an ISP installed base which would also get very persnickety if our installer started shedding usability in the generic cases in favor of a flashy, focused-on-the-desktop installation. What I mean specifically by that is that we still need to be able to install over a serial line with no keyboard or VGA card plugged into the machine, we still need to support scripted installs (even better than we currently support them) and we need to add support for a number of other features like master/slave installations (one master, n clones), adequate OS and component upgrades, high-level repair/recovery, etc. All the sorts of things that network server users seem to expect and a really whiz-bang graphical install can get in the way of if you aren't extremely careful not to code toward that single goal and have a very flexible approach to the UI. Of course, things can also go too much the other way and sysinstall is a good example of an installer which is significantly constrained just by its UI. The hateful libdialog library has a maximum number of 2 buttons on its standard proceed/cancel dialogs, for example, and there's no easy way to add a "Back" to many of the installation dialogs which could really benefit from one. There are also no tab boxes or panners or any other UI elements for putting more than one screen-full's worth of data up in a useful fashion, that is to say which is easily selectable by the user and with an event model that supports arbitrary call-outs. For the last 3 years or so at least, I've also been stuck in the unenviable position of knowing everything that needs to be done to fix the installer and underlying package tools (e.g. rewrite them from scratch) but having a progressively decreasing amount of time to even think about doing it. About a year ago, I even got a paid contractor working on doing some code and he managed to generate some very promising looking stuff, then my time even for interacting with him became so spotty that he finally got annoyed with me and downed tools on the project until he could get some real and effective feedback from us. My bad, as the current generation says, and it's a major item on my TODO list to spend about 2 days pouring through his code and generating a comprehensive set of comments about where to go from there. Unfortunately, this code is also in the very early stages and represents about 34,000 lines of uncommented C++ and TCL code which requires egcs, turbovision 0.7 and (optionally) Qt 1.42 to build so the learning/testing curve is a bit steep. Every person I've handed a copy to so far has never reported back with anything to pass on to the contractor in question.. :) So anyway, that's why (in a nutshell) that sysinstall and pkg_install continue to get patched and ammended even though we all know how limited and hacked-together they are as tools. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 12:19:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A19215232 for ; Thu, 1 Jul 1999 12:19:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA18049; Thu, 1 Jul 1999 12:20:14 -0700 Date: Thu, 1 Jul 1999 12:19:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <68739.930855955@zippy.cdrom.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 >OK, I'll add a few comments to this. And I'll respond... The actual pros and cons of the current installer and what a new one would look like is not the real question to answer here,... I have to say that what we have isn't that bad- it fails only in some areas where it violates the principle of least surprise. It's quite similar to the Slackware install in that it's simple but does have some fastpath items that work for a large number of cases and it tries to sanity check as it goes. That's really all that's needed for almost all the cases (I assert). I'm really not sure that the Windows-like look is a smart move. I mean, KDE looks like a VGA version of win95 and this was all a clever joke with fvwm95 but it's wearing thin. What actual marketing information do we actually have that says that in order to go after the desktops we aren't currently installed on we have to add a lot of engineering effort to the installer? Would it be better to try and work some deals with Compaq or Dell (so that they hedge their bets on Linux) and be a preinstalled choice for those systems instead of trying go after the (exceedingly rare and getting rarer) desktop user who actually installs an entire OS from CD? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 12:34:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DA50014C14 for ; Thu, 1 Jul 1999 12:34:39 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA68844; Thu, 1 Jul 1999 12:33:36 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-reply-to: Your message of "Thu, 01 Jul 1999 12:19:27 PDT." Date: Thu, 01 Jul 1999 12:33:36 -0700 Message-ID: <68840.930857616@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What actual marketing information do we actually have that says that in > order to go after the desktops we aren't currently installed on we have to > add a lot of engineering effort to the installer? Would it be better to Well, just to clear up what looks like a misunderstanding in the making, let me say that the engineering effort we're contemplating here has nothing to do with going after the desktop, it has to do with better security, better componentization(?) of the OS and 3rd party apps, better upgrades, better underlying technology basically. :) - JOrdan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 12:42:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7208114BFD for ; Thu, 1 Jul 1999 12:42:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA18160; Thu, 1 Jul 1999 12:42:52 -0700 Date: Thu, 1 Jul 1999 12:42:04 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <68840.930857616@zippy.cdrom.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 > > What actual marketing information do we actually have that says that in > > order to go after the desktops we aren't currently installed on we have to > > add a lot of engineering effort to the installer? Would it be better to > > Well, just to clear up what looks like a misunderstanding in the > making, let me say that the engineering effort we're contemplating > here has nothing to do with going after the desktop, it has to do with > better security, better componentization(?) of the OS and 3rd party > apps, better upgrades, better underlying technology basically. :) > Whuf! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 12:49:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 5B903151B3 for ; Thu, 1 Jul 1999 12:49:47 -0700 (PDT) (envelope-from nrahlstr@mail.winternet.com) Received: from tundra.winternet.com (nrahlstr@tundra.winternet.com [198.174.169.11]) by icicle.winternet.com (8.9.3/8.9.3) with ESMTP id OAA08882; Thu, 1 Jul 1999 14:49:37 -0500 (CDT) SMTP "HELO" (ESMTP) greeting from tundra.winternet.com But _really_ from :: nrahlstr@tundra.winternet.com [198.174.169.11] SMTP "MAIL From" = nrahlstr@mail.winternet.com (Nathan Ahlstrom) SMTP "RCPT To" = Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id OAA07127; Thu, 1 Jul 1999 14:49:35 -0500 (CDT) Message-ID: <19990701144933.A6772@winternet.com> Date: Thu, 1 Jul 1999 14:49:33 -0500 From: Nathan Ahlstrom To: "Jordan K. Hubbard" , mjacob@feral.com Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... Mail-Followup-To: "Jordan K. Hubbard" , mjacob@feral.com, Steve Ames , freebsd-hackers@FreeBSD.ORG References: <68739.930855955@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <68739.930855955@zippy.cdrom.com>; from Jordan K. Hubbard on Thu, Jul 01, 1999 at 12:05:55PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My bad, as the current generation says, and it's a major item on my > TODO list to spend about 2 days pouring through his code and > generating a comprehensive set of comments about where to go from > there. Unfortunately, this code is also in the very early stages and > represents about 34,000 lines of uncommented C++ and TCL code which > requires egcs, turbovision 0.7 and (optionally) Qt 1.42 to build so > the learning/testing curve is a bit steep. Every person I've handed a > copy to so far has never reported back with anything to pass on to the > contractor in question.. :) Would it be possible to have this code put up for www/ftp or something, so that anyone who is interested could have a look? I, for one, would like to have a look at it. Nathan, not ready to commit to working on something like this. :( -- Nathan Ahlstrom FreeBSD: http://www.FreeBSD.org/ nrahlstr@winternet.com PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 13:10:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 5353A14DC8; Thu, 1 Jul 1999 13:10:38 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA13650; Thu, 1 Jul 1999 13:10:38 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 1 Jul 1999 13:10:38 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-hackers@freebsd.org Cc: peter@freebsd.org Subject: Thank you Peter!! (Was: Heavily loaded amd/nfs... ) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am very happy to report that with the recent commits to -current I can now run my script that reads some 16000 small files in over NFS links at full speed and to completion without locking the box. *BSEG* Many, many thanks for this, it was a huge area of concern for my boss that even though the box performed well under real world load it was falling down on this step (building configuration files). Chalk one up for the good guys. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 13:13:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 152E014D5A; Thu, 1 Jul 1999 13:13:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA00894; Thu, 1 Jul 1999 13:08:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907012008.NAA00894@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems In-reply-to: Your message of "Thu, 01 Jul 1999 16:21:50 +0930." <19990701162150.G82831@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 13:08:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Indeed. Is it possibly interrupting on a line which something else is > using? I've found a problem on my Latitude where it appears that the > machine only has two interrupts free (3 and 9). If I put a modem on 3 > and an Ethernet board on 9, it works, but only by putting pccardd on > irq 5, which doesn't really work. If I pull the Ethernet card, the > whole machine hangs up when I try to access the net, presumably > because pccardd hasn't found out about it. Have you tried setting the PCIC IRQ to 0, so that the driver polls instead? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 14:35:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 0EC53150D5 for ; Thu, 1 Jul 1999 14:35:32 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id XAA60513 for ; Thu, 1 Jul 1999 23:35:16 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <024801bec409$b56075a0$0e00a8c0@neland.dk> From: "Leif Neland" To: "FreeBSD Hackers" Subject: Xfree86 v 3.3.4 Date: Thu, 1 Jul 1999 23:35:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have any inside information on subj? The website still claims: "We are planning to release 3.3.4 some time in June 1999" I'm longing to get support for my S3 Trio3D. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 14:58:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 8788415887 for ; Thu, 1 Jul 1999 14:58:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01384; Thu, 1 Jul 1999 14:54:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907012154.OAA01384@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Ames Cc: freebsd-hackers@freebsd.org Subject: Re: Lizard... In-reply-to: Your message of "Thu, 01 Jul 1999 09:50:52 CDT." <199907011450.JAA10175@ns1.cioe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 14:54:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Everyone should take a peak at http://www.troll.no/announce/lizard.html > if you haven't already. Definately take a look at the screenshots. > > Lizard is a fully graphical Linux installation for Caldera Systems > Open Linux. IMO, having an easy, reliable and attractive installer > is an excellent selling point. > > Just something to ponder... Show us how to a) script it, and b) make it run on a serial terminal, and you'll get a lot more of peoples' attention. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15: 6:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 6EFDA156B0 for ; Thu, 1 Jul 1999 15:06:20 -0700 (PDT) (envelope-from steve@ns1.cioe.com) Received: (from steve@localhost) by ns1.cioe.com (8.9.3/8.9.3) id RAA94424; Thu, 1 Jul 1999 17:06:17 -0500 (EST) (envelope-from steve) Date: Thu, 1 Jul 1999 17:06:17 -0500 (EST) From: Steve Ames Message-Id: <199907012206.RAA94424@ns1.cioe.com> To: mike@smith.net.au, steve@cioe.com Subject: Re: Lizard... Cc: freebsd-hackers@freebsd.org In-Reply-To: <199907012154.OAA01384@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Everyone should take a peak at http://www.troll.no/announce/lizard.html > > if you haven't already. Definately take a look at the screenshots. > > > > Lizard is a fully graphical Linux installation for Caldera Systems > > Open Linux. IMO, having an easy, reliable and attractive installer > > is an excellent selling point. > > > > Just something to ponder... > > Show us how to a) script it, and b) make it run on a serial terminal, > and you'll get a lot more of peoples' attention. 8) *grin* Always the trick isn't it? I think Jordan pointed out all of the good stuff on this topic. Its pretty obvious that one install isn't going to meet everyone's need. FreeBSD does not focus on the desktop and so doesn't need a desktop oriented install. It has also been pointed out that most people don't install their own OS anway unless they have some semblence of technical knowledge or daring. These people don't need a hold-your-hand type install. That being said... I've heard some of my ex-coworkers (who were all FreeBSD people when they worked here) come up to me in this impressed tone: "You wouldn't believe how much easier it is to install RedHat!'. *sigh* I'm not bitching... just being loyal :) -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:14:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ED947156B3 for ; Thu, 1 Jul 1999 15:14:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA18857; Thu, 1 Jul 1999 15:13:58 -0700 Date: Thu, 1 Jul 1999 15:13:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Steve Ames Cc: mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <199907012206.RAA94424@ns1.cioe.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 > That being said... I've heard some of my ex-coworkers (who were all > FreeBSD people when they worked here) come up to me in this impressed > tone: "You wouldn't believe how much easier it is to install RedHat!'. > *sigh* I'm not bitching... just being loyal :) That's ridiculous. I've used both, and RedHat is not that much better, if at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:18: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [207.113.133.228]) by hub.freebsd.org (Postfix) with ESMTP id DEB9514D4A for ; Thu, 1 Jul 1999 15:18:02 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: from lunatic.oneinsane.net (insane@lunatic.oneinsane.net [207.113.133.231]) by the.oneinsane.net (8.9.3/8.9.3) with ESMTP id PAA14867 for ; Thu, 1 Jul 1999 15:18:01 -0700 (PDT) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.3/8.9.3) id PAA19660 for freebsd-hackers@freebsd.org; Thu, 1 Jul 1999 15:18:00 -0700 (PDT) (envelope-from insane) Date: Thu, 1 Jul 1999 15:18:00 -0700 From: "Ron 'The InSaNe One' Rosson" To: freebsd-hackers@freebsd.org Subject: Re: Lizard... Message-ID: <19990701151800.A19504@lunatic.oneinsane.net> Reply-To: Ron Rosson References: <199907012206.RAA94424@ns1.cioe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Matthew Jacob on Thu, Jul 01, 1999 at 03:13:09PM -0700 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.2-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 3:16PM up 15:13, 3 users, load averages: 0.02, 0.04, 0.00 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out: > > > That being said... I've heard some of my ex-coworkers (who were all > > FreeBSD people when they worked here) come up to me in this impressed > > tone: "You wouldn't believe how much easier it is to install RedHat!'. > > *sigh* I'm not bitching... just being loyal :) > > That's ridiculous. I've used both, and RedHat is not that much better, if > at all. > Just tried Redhat last month for the first time. Damn install is more confusing that FreeBSD.. Or maybe I just got accustomed to the freebsd install ;-) -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- Double your drive space: Delete Windows! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:19: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6BC5314A09 for ; Thu, 1 Jul 1999 15:19:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01520; Thu, 1 Jul 1999 15:14:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907012214.PAA01520@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Andrew Gallatin , hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Fri, 02 Jul 1999 02:14:49 +0800." <19990701181449.846AA8A@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 15:14:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Personally, I think we should use a kernel environment variable passed in > from loader, since kern_envp is available *real early*, from the very > beginning of init386(), which is called form locore just after going > virtual. It needs a couple of tweaks to get this to work, and in > particular, the environment variable will have to override the VM86 > calls. It shouldn't "override it", rather it should simply lower the current 4GB cap to whatever it's set to. This allows the BIOS sensing code to correctly walk around holes, etc. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:20:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 485C714D1F for ; Thu, 1 Jul 1999 15:20:32 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id SAA10245; Thu, 1 Jul 1999 18:20:49 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id SAA27894; Thu, 1 Jul 1999 18:20:28 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id SAA45006; Thu, 1 Jul 1999 18:20:28 -0400 (EDT) Date: Thu, 1 Jul 1999 18:20:28 -0400 (EDT) From: Thomas David Rivers Message-Id: <199907012220.SAA45006@lakes.dignus.com> To: freebsd-hackers@freebsd.org, mjacob@feral.com Subject: Re: Lizard... In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > That being said... I've heard some of my ex-coworkers (who were all > > FreeBSD people when they worked here) come up to me in this impressed > > tone: "You wouldn't believe how much easier it is to install RedHat!'. > > *sigh* I'm not bitching... just being loyal :) > > That's ridiculous. I've used both, and RedHat is not that much better, if > at all. > I'd have to concur. I've done both - actually - the RedHat really isn't that different from FreeBSD (that was RedHat 5.2.) - a few of nice boxes you fill in - pop the CD in the drive... *poof* - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:34:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 3576314DE8 for ; Thu, 1 Jul 1999 15:34:53 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 77039 invoked from network); 1 Jul 1999 22:34:53 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 1 Jul 1999 22:34:53 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id RAA82083; Thu, 1 Jul 1999 17:34:52 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Thu, 1 Jul 1999 17:34:52 -0500 (CDT) From: David Scheidt To: Leif Neland Cc: FreeBSD Hackers Subject: Re: Xfree86 v 3.3.4 In-Reply-To: <024801bec409$b56075a0$0e00a8c0@neland.dk> 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, 1 Jul 1999, Leif Neland wrote: > Does anyone have any inside information on subj? > The website still claims: "We are planning to release 3.3.4 some time in > June 1999" > > I'm longing to get support for my S3 Trio3D. Heh. It now says early july. I have a Voodoo Banshee I want to use. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:36:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 1254814DE8 for ; Thu, 1 Jul 1999 15:36:33 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id QAA03769 for ; Thu, 1 Jul 1999 16:36:33 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id QAA20396 for freebsd-hackers@freebsd.org; Thu, 1 Jul 1999 16:36:32 -0600 (MDT) Date: Thu, 1 Jul 1999 16:36:31 -0600 From: Greg Skafte To: freebsd-hackers@freebsd.org Subject: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990701163631.A20163@gras-varg.worldgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been messing around for awhile, and I'm confused (go figure). I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no problems. If I use the adaptec on board utilities it finds my UMAX scanner no probs. when I try to boot the machine hangs just after the waiting for scsi to settle message. So I've turned on cam debugging and get .... lots of iterations of (probe0:aha0:0:0:0) ahaaction (probe1:aha0:0:1:0) ahaaction (probe2:aha0:0:2:0) ahaaction (probe3:aha0:0:3:0) ahaaction (probe4:aha0:0:4:0) ahaaction (probe5:aha0:0:5:0) ahaaction (probe6:aha0:0:6:0) ahaaction and for a given probe (probe0:aha0:0:0:0) camisr(probe0:aha0:0:0:0 ) ahaaction (probe0:aha0:0:0:0) xpt_action (probe0:aha0:0:0:0) INQUIRY. CDB 12 0 0 0 24 0 (probe0:aha0:0:0:0) xtp_setupccb (probe0:aha0:0:0:0) xtp_action (probe0:aha0:0:0:0) CCB 0xc5692508 - timeout (probe0:aha0:0:0:0) CCB 0xc5692508 - timeout (probe0:aha0:0:0:0) ahaaction (probe0:aha0:0:0:0) camisr(probe0:aha0:0:0:0 ) probedone (probe0:aha0:0:0:0) xpt_compile_path (probe0:aha0:0:0:0) xpt_release_path (probe0:aha0:0:0:0) xpt_done aha0: No Longer in timeout I've gabbed these as best as I can since the machine doesn't finish booting so I can't grab a dmesg and I don't have a serial console..... the kernel contains controller aha0 at isa? port ? cam irq ? controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device pass0 #CAM passthrough driver Any thoughts .... comments ..... clues for the clueless ..... TIA Greg -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:40:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2829614DE8 for ; Thu, 1 Jul 1999 15:40:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B9D8679; Fri, 2 Jul 1999 06:40:28 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Andrew Gallatin , hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Thu, 01 Jul 1999 15:14:39 MST." <199907012214.PAA01520@dingo.cdrom.com> Date: Fri, 02 Jul 1999 06:40:28 +0800 From: Peter Wemm Message-Id: <19990701224028.B9D8679@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Personally, I think we should use a kernel environment variable passed in > > from loader, since kern_envp is available *real early*, from the very > > beginning of init386(), which is called form locore just after going > > virtual. It needs a couple of tweaks to get this to work, and in > > particular, the environment variable will have to override the VM86 > > calls. > > It shouldn't "override it", rather it should simply lower the current > 4GB cap to whatever it's set to. This allows the BIOS sensing code to > correctly walk around holes, etc. Also, bear in mind the fun we had with BIOS reporting 15MB of ram and the like.. Capping is fine, so long as there's some way of forcing it to a given value if needed. Never assume BIOS writers are *always* competent. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 15:43:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id AFC0914DE8 for ; Thu, 1 Jul 1999 15:43:08 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id SAA20338; Thu, 1 Jul 1999 18:43:50 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 01 Jul 1999 18:41:39 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: David Scheidt Subject: Re: Xfree86 v 3.3.4 Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a Linux X server for the Voodoo Banshee, over at: http://developer.soundblaster.com/linux/ You might have some luck running it under the Linux emulator. I've never tried it, as I don't have a Banshee. -Mark Taylor NetMAX Developer mtaylor@cybernet.com http://www.netmax.com/ On 01-Jul-99 David Scheidt wrote: > On Thu, 1 Jul 1999, Leif Neland wrote: > >> Does anyone have any inside information on subj? >> The website still claims: "We are planning to release 3.3.4 some time in >> June 1999" >> >> I'm longing to get support for my S3 Trio3D. > > Heh. It now says early july. I have a Voodoo Banshee I want to use. > > David > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:19: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 183C41504B for ; Thu, 1 Jul 1999 16:18:58 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id TAA03762 for ; Thu, 1 Jul 1999 19:06:54 -0400 Date: Thu, 1 Jul 1999 19:06:54 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: reason for slow user-user memory copy 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 graduate student here implements a mmap() interface to a TCP/IP network card. He notices that it takes much longer time to copy from mmapp()'ed area to another user area than it takes to copy the same amount of data from kernel space to user space. The students here have no idea why this could be possible. I hope someone on this list can give us a hint. Below is a part of his original email. He uses rdtsc instruction to do the timing. ------------------------------------------------------------------------ Well I have implemented a memory mapped interface for the user in Linux using the DEC 21140 Tulip ethernet card. Thus the user has access to the buffers, but when I did a memcpy from the RX buffer to the user variable, it took an extraordinary amount of time, approx 70 microsec for 1460 btyes... where as the original scheme takes 25 microsec for the same data when it does a memcpy_to_iovec in tcp_recvmsg(). I am confused by this unexpected timings. More than 80% of the time is spent doing the memcpy. ----------------------------------------------------------------------- Thanks for your help. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:24: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D821C14D90 for ; Thu, 1 Jul 1999 16:24:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA95339; Thu, 1 Jul 1999 16:24:03 -0700 (PDT) Date: Thu, 1 Jul 1999 16:24:02 -0700 (PDT) From: Julian Elischer To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reason for slow user-user memory copy 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 hmm Unfortunatly Linux is nt relevent to FreeBSD so we can't comment directly.. it is possible that the mmapped region is marked non-cachable, which migh tmake a difference. I have no idea where "memcpy_to_iovec" in Linux is copying to so it's hard to comment. julian On Thu, 1 Jul 1999, Zhihui Zhang wrote: > > A graduate student here implements a mmap() interface to a TCP/IP network > card. He notices that it takes much longer time to copy from mmapp()'ed > area to another user area than it takes to copy the same amount of data > from kernel space to user space. The students here have no idea why this > could be possible. I hope someone on this list can give us a hint. Below > is a part of his original email. He uses rdtsc instruction to do the > timing. > > ------------------------------------------------------------------------ > Well I have implemented a memory mapped interface for the user in Linux > using the DEC 21140 Tulip ethernet card. Thus the user has access to the > buffers, but when I did a memcpy from the RX buffer to the user variable, > it took an extraordinary amount of time, approx 70 microsec for 1460 > btyes... where as the original scheme takes 25 microsec for the same data > when it does a memcpy_to_iovec in tcp_recvmsg(). > > I am confused by this unexpected timings. More than 80% of the time is > spent doing the memcpy. > ----------------------------------------------------------------------- > > Thanks for your help. > > -------------------------------------------------- > Zhihui Zhang. Please visit http://www.freebsd.org > -------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:37:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 098DB1586A for ; Thu, 1 Jul 1999 16:37:15 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA07652; Thu, 1 Jul 1999 16:37:11 -0700 (PDT) Message-Id: <199907012337.QAA07652@implode.root.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reason for slow user-user memory copy In-reply-to: Your message of "Thu, 01 Jul 1999 19:06:54 EDT." From: David Greenman Reply-To: dg@root.com Date: Thu, 01 Jul 1999 16:37:11 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >A graduate student here implements a mmap() interface to a TCP/IP network >card. He notices that it takes much longer time to copy from mmapp()'ed >area to another user area than it takes to copy the same amount of data >from kernel space to user space. The students here have no idea why this >could be possible. I hope someone on this list can give us a hint. Below >is a part of his original email. He uses rdtsc instruction to do the >timing. > >------------------------------------------------------------------------ >Well I have implemented a memory mapped interface for the user in Linux >using the DEC 21140 Tulip ethernet card. Thus the user has access to the >buffers, but when I did a memcpy from the RX buffer to the user variable, >it took an extraordinary amount of time, approx 70 microsec for 1460 >btyes... where as the original scheme takes 25 microsec for the same data >when it does a memcpy_to_iovec in tcp_recvmsg(). > >I am confused by this unexpected timings. More than 80% of the time is >spent doing the memcpy. >----------------------------------------------------------------------- If the mapping is being done via a device mapping, then the region will be marked non-cacheable. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:44:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E8A8214F99 for ; Thu, 1 Jul 1999 16:44:05 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA01321; Thu, 1 Jul 1999 19:44:02 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA63201; Thu, 1 Jul 1999 19:44:02 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Jul 1999 19:44:02 -0400 (EDT) To: Peter Wemm Cc: hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-Reply-To: <19990701181449.846AA8A@overcee.netplex.com.au> References: <14203.43667.496647.806250@grasshopper.cs.duke.edu> <19990701181449.846AA8A@overcee.netplex.com.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14203.64207.225157.109702@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: Peter, Thanks for the details. I wasn't sure if it was something that was supposed to work... I assume it still works when built in by config & should be left in place for that reason though, right? (haven't tried it here..) > Personally, I think we should use a kernel environment variable passed in > from loader, since kern_envp is available *real early*, from the very > beginning of init386(), which is called form locore just after going > virtual. It needs a couple of tweaks to get this to work, and in > particular, the environment variable will have to override the VM86 > calls. Great idea! I'd thought about adding a boot flag, but didn't realize the kernel environment variable route was so easy. The following hack seems to work here. At least it should have the same effect as building with MAXMEM. The only bit that concerns me is the movement of the movement of the kern_envp initialzation. I don't know diddly about the early stages of the boot & I don't know if moving it so that environment variables are available in getmemsize() is safe. Can you take a peek at this patch please? Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.342 diff -u -b -B -c -r1.342 machdep.c cvs diff: conflicting specifications of output style *** machdep.c 1999/06/18 14:32:14 1.342 --- machdep.c 1999/07/01 23:28:50 *************** *** 153,158 **** --- 153,164 ---- CTLFLAG_RD, &tlb_flush_count, 0, ""); #endif + int i386_maxmem=0; + + SYSCTL_INT(_machdep, OID_AUTO, maxmem, CTLFLAG_RD, + &i386_maxmem, 0, "override memory auto-size at boottime"); + + #ifdef PC98 static int ispc98 = 1; #else *************** *** 1331,1337 **** /* * If a specific amount of memory is indicated via the MAXMEM ! * option or the npx0 "msize", then don't do the speculative * memory probe. */ #ifdef MAXMEM --- 1337,1344 ---- /* * If a specific amount of memory is indicated via the MAXMEM ! * option or the npx0 "msize", or the machdep.maxmem kernel ! * environment variable, then don't do the speculative * memory probe. */ #ifdef MAXMEM *************** *** 1347,1352 **** --- 1354,1365 ---- } } #endif + if (getenv_int("machdep.maxmem", &i386_maxmem) != 0) { + if(i386_maxmem != 0) { + Maxmem = i386_maxmem / 4; + speculative_mprobe = FALSE; + } + } #ifdef SMP /* look for the MP hardware - needed for apic addresses */ *************** *** 1656,1661 **** --- 1669,1680 ---- dblfault_tss.tss_ldt = GSEL(GLDT_SEL, SEL_KPL); vm86_initialize(); + /* + * XXXX moved here to make machdep.maxmem available in + * getmemsize. Not sure if this is safe + */ + if (bootinfo.bi_envp) + kern_envp = (caddr_t)bootinfo.bi_envp + KERNBASE; getmemsize(first); /* now running on new page tables, configured,and u/iom is accessible */ *************** *** 1700,1707 **** preload_metadata = (caddr_t)bootinfo.bi_modulep + KERNBASE; preload_bootstrap_relocate(KERNBASE); } - if (bootinfo.bi_envp) - kern_envp = (caddr_t)bootinfo.bi_envp + KERNBASE; } #if defined(I586_CPU) && !defined(NO_F00F_HACK) --- 1719,1724 ---- Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:48:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id C928514D94 for ; Thu, 1 Jul 1999 16:48:17 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id TAA03835; Thu, 1 Jul 1999 19:36:11 -0400 Date: Thu, 1 Jul 1999 19:36:10 -0400 (EDT) From: Zhihui Zhang To: David Greenman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reason for slow user-user memory copy In-Reply-To: <199907012337.QAA07652@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Jul 1999, David Greenman wrote: > >A graduate student here implements a mmap() interface to a TCP/IP network > >card. He notices that it takes much longer time to copy from mmapp()'ed > >area to another user area than it takes to copy the same amount of data > >from kernel space to user space. The students here have no idea why this > >could be possible. I hope someone on this list can give us a hint. Below > >is a part of his original email. He uses rdtsc instruction to do the > >timing. > > > >------------------------------------------------------------------------ > >Well I have implemented a memory mapped interface for the user in Linux > >using the DEC 21140 Tulip ethernet card. Thus the user has access to the > >buffers, but when I did a memcpy from the RX buffer to the user variable, > >it took an extraordinary amount of time, approx 70 microsec for 1460 > >btyes... where as the original scheme takes 25 microsec for the same data > >when it does a memcpy_to_iovec in tcp_recvmsg(). > > > >I am confused by this unexpected timings. More than 80% of the time is > >spent doing the memcpy. > >----------------------------------------------------------------------- > > If the mapping is being done via a device mapping, then the region will > be marked non-cacheable. > > -DG I remember that he said he created a character device /dev/tulip to represent the network card. Actually, his work borrowed a lot from the Cornell U-Net project (now the basis of VIA?). Can we change the corresponding page table (directory) entries to be cacheable as needed? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:50:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6F30D14D94 for ; Thu, 1 Jul 1999 16:50:29 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA96888; Thu, 1 Jul 1999 16:50:10 -0700 (PDT) Date: Thu, 1 Jul 1999 16:50:09 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: npx0 to set maxmem broken in -current? In-Reply-To: <14203.64207.225157.109702@grasshopper.cs.duke.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 a bit late.... you should check teh cvs rep for these files.. peter's already checked it in... :-) On Thu, 1 Jul 1999, Andrew Gallatin wrote: > > Peter Wemm writes: > > Peter, > > Thanks for the details. I wasn't sure if it was something that was > supposed to work... I assume it still works when built in by config & > should be left in place for that reason though, right? (haven't tried > it here..) > > > Personally, I think we should use a kernel environment variable passed in > > from loader, since kern_envp is available *real early*, from the very > > beginning of init386(), which is called form locore just after going > > virtual. It needs a couple of tweaks to get this to work, and in > > particular, the environment variable will have to override the VM86 > > calls. > > Great idea! I'd thought about adding a boot flag, but didn't realize > the kernel environment variable route was so easy. > > The following hack seems to work here. At least it should have the > same effect as building with MAXMEM. The only bit that concerns me is > the movement of the movement of the kern_envp initialzation. I don't > know diddly about the early stages of the boot & I don't know if > moving it so that environment variables are available in getmemsize() > is safe. Can you take a peek at this patch please? > > Index: machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v > retrieving revision 1.342 > diff -u -b -B -c -r1.342 machdep.c > cvs diff: conflicting specifications of output style > *** machdep.c 1999/06/18 14:32:14 1.342 > --- machdep.c 1999/07/01 23:28:50 > *************** > *** 153,158 **** > --- 153,164 ---- > CTLFLAG_RD, &tlb_flush_count, 0, ""); > #endif > > + int i386_maxmem=0; > + > + SYSCTL_INT(_machdep, OID_AUTO, maxmem, CTLFLAG_RD, > + &i386_maxmem, 0, "override memory auto-size at boottime"); > + > + > #ifdef PC98 > static int ispc98 = 1; > #else > *************** > *** 1331,1337 **** > > /* > * If a specific amount of memory is indicated via the MAXMEM > ! * option or the npx0 "msize", then don't do the speculative > * memory probe. > */ > #ifdef MAXMEM > --- 1337,1344 ---- > > /* > * If a specific amount of memory is indicated via the MAXMEM > ! * option or the npx0 "msize", or the machdep.maxmem kernel > ! * environment variable, then don't do the speculative > * memory probe. > */ > #ifdef MAXMEM > *************** > *** 1347,1352 **** > --- 1354,1365 ---- > } > } > #endif > + if (getenv_int("machdep.maxmem", &i386_maxmem) != 0) { > + if(i386_maxmem != 0) { > + Maxmem = i386_maxmem / 4; > + speculative_mprobe = FALSE; > + } > + } > > #ifdef SMP > /* look for the MP hardware - needed for apic addresses */ > *************** > *** 1656,1661 **** > --- 1669,1680 ---- > dblfault_tss.tss_ldt = GSEL(GLDT_SEL, SEL_KPL); > > vm86_initialize(); > + /* > + * XXXX moved here to make machdep.maxmem available in > + * getmemsize. Not sure if this is safe > + */ > + if (bootinfo.bi_envp) > + kern_envp = (caddr_t)bootinfo.bi_envp + KERNBASE; > getmemsize(first); > > /* now running on new page tables, configured,and u/iom is accessible */ > *************** > *** 1700,1707 **** > preload_metadata = (caddr_t)bootinfo.bi_modulep + KERNBASE; > preload_bootstrap_relocate(KERNBASE); > } > - if (bootinfo.bi_envp) > - kern_envp = (caddr_t)bootinfo.bi_envp + KERNBASE; > } > > #if defined(I586_CPU) && !defined(NO_F00F_HACK) > --- 1719,1724 ---- > > > > > Thanks, > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:53: 1 1999 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 F038E14DD0 for ; Thu, 1 Jul 1999 16:52:45 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id AAA76586; Fri, 2 Jul 1999 00:09:10 +0100 (BST) (envelope-from nik) Date: Fri, 2 Jul 1999 00:09:09 +0100 From: Nik Clayton To: Stan Shkolnyy Cc: hackers@FreeBSD.ORG Subject: Re: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)) Message-ID: <19990702000909.A75558@catkin.nothing-going-on.org> References: <19990630210102.A72675@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Stan Shkolnyy on Wed, Jun 30, 1999 at 08:02:06PM -0500 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 08:02:06PM -0500, Stan Shkolnyy wrote: > On Wed, 30 Jun 1999, Nik Clayton wrote: > > Sorry it's taken me a while to reply to this; ironically, most of my time > > has been spent on freebsd-doc recently. > > > > On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote: > > > I've come to understanding that lack of documentation is probably one of > > > the factors that keep the system healthy, > > > > I've just spent five minutes trying to phrase a reply to this that manages > > to convey my complete disagreement without resorting to profanity. > > But why did you do that? Basically, I wanted to make sure my disagreement got on record somewhere, so that if anyone trawls the mailing lists at some point in the future and sees your comments, hopefully they'll also see my reply. I know your original comment was intended at least half in jest. But there'll be people who see it and take it the wrong way -- either by assuming that FreeBSD's attitude is too elitist, or that their efforts at documentation won't be welcome, and so on. N PS: Also, there's the considerable thrill of using naughty words. . . -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:54:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 31438151EB for ; Thu, 1 Jul 1999 16:54:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA02072; Thu, 1 Jul 1999 16:50:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907012350.QAA02072@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: Andrew Gallatin , Peter Wemm , hackers@FreeBSD.ORG Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Thu, 01 Jul 1999 16:50:09 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 16:50:44 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > a bit late.... > you should check teh cvs rep for these files.. > peter's already checked it in... :-) Don't count on Peter's changes; I'm going to try to beat them up again. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:58: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A76E814DD0 for ; Thu, 1 Jul 1999 16:58:04 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA01489; Thu, 1 Jul 1999 19:57:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA63231; Thu, 1 Jul 1999 19:57:56 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Jul 1999 19:57:55 -0400 (EDT) To: Julian Elischer Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: npx0 to set maxmem broken in -current? In-Reply-To: References: <14203.64207.225157.109702@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14203.65399.380177.311909@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > a bit late.... > you should check teh cvs rep for these files.. > peter's already checked it in... :-) > Wow, he's fast. ;-) I should have checked my committers folder sooner.. Thanks Peter. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 16:58:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osgroup.com (unknown [38.229.41.6]) by hub.freebsd.org (Postfix) with ESMTP id 49B78156C3 for ; Thu, 1 Jul 1999 16:58:21 -0700 (PDT) (envelope-from stan@laurent.osgroup.com) Received: from localhost (stan@localhost) by osgroup.com (8.7.6/8.6.12) with SMTP id SAA24318 for ; Thu, 1 Jul 1999 18:47:27 -0500 Date: Thu, 1 Jul 1999 18:47:27 -0500 (CDT) From: Stan Shkolnyy To: hackers@FreeBSD.ORG Subject: Usage of 'gdb' command in DDB 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 All, Well, I entered 'gdb', then 'continue' and now I can debug the kernel remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to contact the remote GDB instead of accepting input from me. Thank you, Stan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 17: 1:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 148CA15363 for ; Thu, 1 Jul 1999 17:01:47 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA07819; Thu, 1 Jul 1999 17:01:58 -0700 (PDT) Message-Id: <199907020001.RAA07819@implode.root.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reason for slow user-user memory copy In-reply-to: Your message of "Thu, 01 Jul 1999 19:36:10 EDT." From: David Greenman Reply-To: dg@root.com Date: Thu, 01 Jul 1999 17:01:58 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> If the mapping is being done via a device mapping, then the region will >> be marked non-cacheable. > >I remember that he said he created a character device /dev/tulip to >represent the network card. Actually, his work borrowed a lot from the >Cornell U-Net project (now the basis of VIA?). Can we change the >corresponding page table (directory) entries to be cacheable as needed? You'd have to modify the kernel - specifically pmap_mapdev(). Note that the above behavior is only true for older versions of FreeBSD (pre-2.2). If you're having this problem within a newer version of FreeBSD, then it's probably something else causing it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 18:24: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id D641E14FDD; Thu, 1 Jul 1999 18:23:53 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA07347; Fri, 2 Jul 1999 10:53:52 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA90638; Fri, 2 Jul 1999 10:53:46 +0930 (CST) Date: Fri, 2 Jul 1999 10:53:46 +0930 From: Greg Lehey To: Mike Smith Cc: Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems Message-ID: <19990702105346.H87392@freebie.lemis.com> References: <19990701162150.G82831@freebie.lemis.com> <199907012008.NAA00894@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907012008.NAA00894@dingo.cdrom.com>; from Mike Smith on Thu, Jul 01, 1999 at 01:08:11PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 1 July 1999 at 13:08:11 -0700, Mike Smith wrote: >> >> Indeed. Is it possibly interrupting on a line which something else is >> using? I've found a problem on my Latitude where it appears that the >> machine only has two interrupts free (3 and 9). If I put a modem on 3 >> and an Ethernet board on 9, it works, but only by putting pccardd on >> irq 5, which doesn't really work. If I pull the Ethernet card, the >> whole machine hangs up when I try to access the net, presumably >> because pccardd hasn't found out about it. > > Have you tried setting the PCIC IRQ to 0, so that the driver polls > instead? I have now. It ignored it and grabbed irq 5 anyway. Where is this described? I put it in my config file: # PCCARD (PCMCIA) support controller card0 device pcic0 at card? irq 0 device pcic1 at card? irq 0 Is that what you meant? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 18:33: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2301F14CFC for ; Thu, 1 Jul 1999 18:32:55 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA07390; Fri, 2 Jul 1999 11:02:35 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA90710; Fri, 2 Jul 1999 11:02:33 +0930 (CST) Date: Fri, 2 Jul 1999 11:02:33 +0930 From: Greg Lehey To: Stan Shkolnyy Cc: hackers@FreeBSD.ORG Subject: Re: Usage of 'gdb' command in DDB Message-ID: <19990702110233.J87392@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Stan Shkolnyy on Thu, Jul 01, 1999 at 06:47:27PM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 1 July 1999 at 18:47:27 -0500, Stan Shkolnyy wrote: > Hello All, > > Well, I entered 'gdb', then 'continue' and now I can debug the kernel > remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to > contact the remote GDB instead of accepting input from me. A nuisance, isn't it? There's no documented way. I have this in my .gdbinit: define ddb set boothowto=0x80000000 s end document ddb Switch back to ddb. end That works with -CURRENT. Don't count on it staying that way. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 19:33:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.koganei.wide.ad.jp (ns.koganei.wide.ad.jp [203.178.148.20]) by hub.freebsd.org (Postfix) with ESMTP id 8E0B8150FD for ; Thu, 1 Jul 1999 19:33:15 -0700 (PDT) (envelope-from ikob@koganei.wide.ad.jp) Received: from localhost (eeyore.koganei.wide.ad.jp [203.178.148.70]) by happy.koganei.wide.ad.jp (8.9.3/8.9.3) with ESMTP id LAA08384; Fri, 2 Jul 1999 11:33:51 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) To: hackers@freebsd.org Cc: ikob@koganei.wide.ad.jp Subject: Major device number for firewire X-Mailer: Mew version 1.94b37 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990702113310R.ikob@koganei.wide.ad.jp> Date: Fri, 02 Jul 1999 11:33:10 +0900 From: ikob X-Dispatcher: imput version 990623(IM117) Lines: 14 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I have been developing firewire (IEEE1394) device driver on FreeBSD and the driver is working quite stable. I would like to reserve major device number for firewire. P.S. The driver code can be obtained from following: ftp://ftp.uec.ac.jp/pub/firewire ikob@koganei.wide.ad.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 19:40: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 93AC714F59 for ; Thu, 1 Jul 1999 19:40:04 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 54388 invoked from network); 2 Jul 1999 02:40:03 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 2 Jul 1999 02:40:03 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id VAA90059; Thu, 1 Jul 1999 21:40:03 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Thu, 1 Jul 1999 21:40:03 -0500 (CDT) From: David Scheidt To: "Mark J. Taylor" Cc: hackers@freebsd.org Subject: Re: Xfree86 v 3.3.4 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, 1 Jul 1999, Mark J. Taylor wrote: > > There is a Linux X server for the Voodoo Banshee, over at: > http://developer.soundblaster.com/linux/ > > You might have some luck running it under the Linux emulator. > I've never tried it, as I don't have a Banshee. Thanks! This appears to work pretty well, much better than I would expect a server for a different OS to work. I continue to be very impressed by the Linux emulation! The one problem I have with it is I can't get it to work with sysmouse. For the amount of time I spend using the text console on this box, I can live with killing and started moused manually. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 19:51:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 535DE14CEF for ; Thu, 1 Jul 1999 19:51:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA70339; Thu, 1 Jul 1999 19:49:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: ikob Cc: hackers@FreeBSD.ORG Subject: Re: Major device number for firewire In-reply-to: Your message of "Fri, 02 Jul 1999 11:33:10 +0900." <19990702113310R.ikob@koganei.wide.ad.jp> Date: Thu, 01 Jul 1999 19:49:29 -0700 Message-ID: <70335.930883769@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I assume you mean a major character device number only? You can have 127 (decimal). Any prediction on when you think this driver will be ready to bring into -current? It sounds quite promising! - Jordan > > Folks, > > I have been developing firewire (IEEE1394) device driver on FreeBSD and > the driver is working quite stable. I would like to reserve major > device number for firewire. > > P.S. > > The driver code can be obtained from following: > > ftp://ftp.uec.ac.jp/pub/firewire > > ikob@koganei.wide.ad.jp > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 19:58:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.koganei.wide.ad.jp (ns.koganei.wide.ad.jp [203.178.148.20]) by hub.freebsd.org (Postfix) with ESMTP id 5BB1F14BC9 for ; Thu, 1 Jul 1999 19:58:05 -0700 (PDT) (envelope-from ikob@koganei.wide.ad.jp) Received: from localhost (eeyore.koganei.wide.ad.jp [203.178.148.70]) by happy.koganei.wide.ad.jp (8.9.3/8.9.3) with ESMTP id LAA08491; Fri, 2 Jul 1999 11:57:56 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) To: jkh@zippy.cdrom.com Cc: hackers@FreeBSD.ORG Subject: Re: Major device number for firewire In-Reply-To: <70335.930883769@zippy.cdrom.com> References: <19990702113310R.ikob@koganei.wide.ad.jp> <70335.930883769@zippy.cdrom.com> X-Mailer: Mew version 1.94b37 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990702115715E.ikob@koganei.wide.ad.jp> Date: Fri, 02 Jul 1999 11:57:15 +0900 From: ikob X-Dispatcher: imput version 990623(IM117) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jordan K. Hubbard" Subject: Re: Major device number for firewire Date: Thu, 01 Jul 1999 19:49:29 -0700 Message-ID: <70335.930883769@zippy.cdrom.com> jkh> I assume you mean a major character device number only? You can jkh> have 127 (decimal). jkh> Thanks, I want to get just one character device. jkh> Any prediction on when you think this driver will be ready to bring jkh> into -current? It sounds quite promising! jkh> I am now considering and designing firewire API as I said in FREENIX. When fixing API, I think it is appropriate to import current- . ikob@koganei.wide.ad.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 19:59: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E78BE1570C for ; Thu, 1 Jul 1999 19:58:47 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA70448; Thu, 1 Jul 1999 19:57:14 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nathan Ahlstrom Cc: mjacob@feral.com, Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-reply-to: Your message of "Thu, 01 Jul 1999 14:49:33 CDT." <19990701144933.A6772@winternet.com> Date: Thu, 01 Jul 1999 19:57:13 -0700 Message-ID: <70440.930884233@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would it be possible to have this code put up for www/ftp or > something, so that anyone who is interested could have a look? Feel free, just don't ask me questions about it since I honestly don't have time right now to explain to many hundreds of people how to build this stuff. In a nutshell, use egcs to compile everything from the following list: turbovision 0.7, qt 1.42, libh 0.1 (see below). libh is the code in question and can be obtained from ftp://zippy.cdrom.com/pub/libh.tar.gz. It will work with either gmake or make. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 20:29:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gdead.adm.ispchannel.net (gdead.adm.ispchannel.net [208.138.36.151]) by hub.freebsd.org (Postfix) with ESMTP id 9391214EE4 for ; Thu, 1 Jul 1999 20:29:10 -0700 (PDT) (envelope-from jgrosch@gdead.adm.ispchannel.net) Received: (from jgrosch@localhost) by gdead.adm.ispchannel.net (8.9.3/8.9.2) id UAA22971; Thu, 1 Jul 1999 20:29:19 -0700 (PDT) (envelope-from jgrosch) Date: Thu, 1 Jul 1999 20:29:19 -0700 From: Josef Grosch To: "Ron 'The InSaNe One' Rosson" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... Message-ID: <19990701202919.A22943@gdead.adm.ispchannel.net> Reply-To: jgrosch@ispchannel.com References: <199907012206.RAA94424@ns1.cioe.com> <19990701151800.A19504@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990701151800.A19504@lunatic.oneinsane.net>; from Ron 'The InSaNe One' Rosson on Thu, Jul 01, 1999 at 03:18:00PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 03:18:00PM -0700, Ron 'The InSaNe One' Rosson wrote: > On Thu, 01 Jul 1999, Matthew Jacob was heard blurting out: > > > > > > That being said... I've heard some of my ex-coworkers (who were all > > > FreeBSD people when they worked here) come up to me in this impressed > > > tone: "You wouldn't believe how much easier it is to install RedHat!'. > > > *sigh* I'm not bitching... just being loyal :) > > > > That's ridiculous. I've used both, and RedHat is not that much better, if > > at all. > > > Just tried Redhat last month for the first time. Damn install is more > confusing that FreeBSD.. Or maybe I just got accustomed to the freebsd > install ;-) I have done installs on FreeBSD, Redhat, HP/UX, and Solaris and I have to say that Redhat is very confusing. FreeBSD does have it's warts but it is better than Redhat. HP/UX and Solaris also have their problems, just ask Nicole Harrington how she liked installing Solaris on an X86 box, but they are better than FreeBSD but not by as much as you would think. HP/UX install looks a lot like FreeBSD but not as limited as FreeBSD. The ability to have more than 2 buttons on the screen and too be able to backup is a major blessing. Josef -- Josef Grosch | FreeBSD 3.2 | Bay Area FreeBSD Users Group jgrosch@ispchannel.com | www.freebsd.org | www.bafug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 21:43:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-6.ppp.wenet.net [206.15.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 3761315026 for ; Thu, 1 Jul 1999 21:43:36 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id VAA07294; Thu, 1 Jul 1999 21:43:01 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 1 Jul 1999 21:42:57 -0700 (PDT) From: Alex Zepeda To: jgrosch@ispchannel.com Cc: "Ron 'The InSaNe One' Rosson" , freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <19990701202919.A22943@gdead.adm.ispchannel.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 Thu, 1 Jul 1999, Josef Grosch wrote: > I have done installs on FreeBSD, Redhat, HP/UX, and Solaris and I have to > say that Redhat is very confusing. FreeBSD does have it's warts but it is > better than Redhat. HP/UX and Solaris also have their problems, just ask > Nicole Harrington how she liked installing Solaris on an X86 box, but they > are better than FreeBSD but not by as much as you would think. HP/UX > install looks a lot like FreeBSD but not as limited as FreeBSD. The ability > to have more than 2 buttons on the screen and too be able to backup is a > major blessing. Uh, the Solaris packaging crap *is* a wart. It won't even work on a tarball.. The FreeBSD makefile mess could be extended to be about as "flexible" as the Solaris gunk. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 21:45:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-6.ppp.wenet.net [206.15.85.6]) by hub.freebsd.org (Postfix) with ESMTP id B3D8C14C14 for ; Thu, 1 Jul 1999 21:44:58 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id VAA07301; Thu, 1 Jul 1999 21:43:31 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 1 Jul 1999 21:43:27 -0700 (PDT) From: Alex Zepeda To: "Jordan K. Hubbard" Cc: Nathan Ahlstrom , mjacob@feral.com, Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <70440.930884233@zippy.cdrom.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 > Feel free, just don't ask me questions about it since I honestly don't > have time right now to explain to many hundreds of people how to build > this stuff. In a nutshell, use egcs to compile everything from the > following list: turbovision 0.7, qt 1.42, libh 0.1 (see below). > > libh is the code in question and can be obtained from > ftp://zippy.cdrom.com/pub/libh.tar.gz. It will work with either gmake > or make. FWIW it seems to want GNU make. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 22: 1:27 1999 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 939C614BE5; Thu, 1 Jul 1999 22:00:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA05688; Thu, 1 Jul 1999 23:00:51 -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 WAA41325; Thu, 1 Jul 1999 22:59:56 -0600 (MDT) Message-Id: <199907020459.WAA41325@harmony.village.org> To: Greg Lehey Subject: Re: pccard problems Cc: Mike Smith , Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 10:53:46 +0930." <19990702105346.H87392@freebie.lemis.com> References: <19990702105346.H87392@freebie.lemis.com> <19990701162150.G82831@freebie.lemis.com> <199907012008.NAA00894@dingo.cdrom.com> Date: Thu, 01 Jul 1999 22:59:56 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702105346.H87392@freebie.lemis.com> Greg Lehey writes: : Is that what you meant? No. You need to set machdep.pccard.pcic_irq to be zero in your boot loader. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 22: 6:18 1999 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 CCCC7150C3 for ; Thu, 1 Jul 1999 22:05:51 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA05701; Thu, 1 Jul 1999 23:05:50 -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 XAA41362; Thu, 1 Jul 1999 23:04:54 -0600 (MDT) Message-Id: <199907020504.XAA41362@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 01 Jul 1999 16:36:31 MDT." <19990701163631.A20163@gras-varg.worldgate.com> References: <19990701163631.A20163@gras-varg.worldgate.com> Date: Thu, 01 Jul 1999 23:04:54 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990701163631.A20163@gras-varg.worldgate.com> Greg Skafte writes: : I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no : problems. OK. : If I use the adaptec on board utilities it finds my UMAX scanner no probs. OK. : when I try to boot the machine hangs just after the waiting for scsi to : settle message. Now I'm confused. Is this in -current where you are having the problems? : I've gabbed these as best as I can since the machine doesn't finish booting : so I can't grab a dmesg and I don't have a serial console..... OK. Before going too far, please make sure that termination is currect. I've seen the "timeout timeout ...not in timeout" sequence when that was the case. I would have expected that from identical hardware with a RELENG_3 kernel, however. It is possible that something in the emulation layer in -current isn't working, or that -current's CAM does things a little faster than RELENG_3's CAM did, this exposing another bug in the aha driver. I didn't torture test it with anything except slow disks and a CDROM changer... Any other device will likely work or not work due entirely to chance. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 22:13:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5B00414BE5; Thu, 1 Jul 1999 22:13:41 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA08268; Fri, 2 Jul 1999 14:43:38 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA91932; Fri, 2 Jul 1999 14:43:37 +0930 (CST) Date: Fri, 2 Jul 1999 14:43:36 +0930 From: Greg Lehey To: Warner Losh Cc: Mike Smith , Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems Message-ID: <19990702144336.P87392@freebie.lemis.com> References: <19990702105346.H87392@freebie.lemis.com> <19990701162150.G82831@freebie.lemis.com> <199907012008.NAA00894@dingo.cdrom.com> <19990702105346.H87392@freebie.lemis.com> <199907020459.WAA41325@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907020459.WAA41325@harmony.village.org>; from Warner Losh on Thu, Jul 01, 1999 at 10:59:56PM -0600 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 1 July 1999 at 22:59:56 -0600, Warner Losh wrote: > In message <19990702105346.H87392@freebie.lemis.com> Greg Lehey writes: >> Is that what you meant? > > No. You need to set > machdep.pccard.pcic_irq > to be zero in your boot loader. Yes. Somebody else told me that. I tried it (and confirmed that show displayed it, and that it was spelt right), and it still grabbed irq 5. Just to make sure it wasn't lying, I pulled the Ethernet board. No message, and when I tried a ping, the machine locked up solid. This is 3.2-RELEASE; when I'm finished what I'm doing, I'll look for why it's not reacting correctly. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 1 23:16:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 947EA14DCC for ; Thu, 1 Jul 1999 23:16:20 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA13845; Fri, 2 Jul 1999 08:10:03 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA04205; Fri, 2 Jul 1999 00:16:58 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907012216.AAA04205@yedi.iaf.nl> Subject: Re: Lizard... In-Reply-To: <199907012154.OAA01384@dingo.cdrom.com> from Mike Smith at "Jul 1, 1999 2:54:45 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 2 Jul 1999 00:16:58 +0200 (CEST) Cc: steve@cioe.com, freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mike Smith wrote ... > > > > Everyone should take a peak at http://www.troll.no/announce/lizard.html > > if you haven't already. Definately take a look at the screenshots. > > > > Lizard is a fully graphical Linux installation for Caldera Systems > > Open Linux. IMO, having an easy, reliable and attractive installer > > is an excellent selling point. > > > > Just something to ponder... > > Show us how to a) script it, and b) make it run on a serial terminal, > and you'll get a lot more of peoples' attention. 8) And not to forget the visually impaired users. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Jul 2 0: 2:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id 20CE01502A; Fri, 2 Jul 1999 00:02:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00418; Thu, 1 Jul 1999 23:58:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907020658.XAA00418@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: Mike Smith , Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems In-reply-to: Your message of "Fri, 02 Jul 1999 10:53:46 +0930." <19990702105346.H87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 23:58:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # PCCARD (PCMCIA) support > controller card0 > device pcic0 at card? irq 0 > device pcic1 at card? irq 0 > > Is that what you meant? No, it's a loader tunable. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 0:14:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id A34A614DC3; Fri, 2 Jul 1999 00:14:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00533; Fri, 2 Jul 1999 00:10:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907020710.AAA00533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: Warner Losh , Mike Smith , Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems In-reply-to: Your message of "Fri, 02 Jul 1999 14:43:36 +0930." <19990702144336.P87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jul 1999 00:10:28 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes. Somebody else told me that. I tried it (and confirmed that show > displayed it, and that it was spelt right), and it still grabbed irq > 5. Just to make sure it wasn't lying, I pulled the Ethernet board. > No message, and when I tried a ping, the machine locked up solid. > This is 3.2-RELEASE; when I'm finished what I'm doing, I'll look for > why it's not reacting correctly. You may be loading the pcic KLD as well as having it built into the kernel. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 0:18: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BB3F714DC3; Fri, 2 Jul 1999 00:17:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA08709; Fri, 2 Jul 1999 16:47:57 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA93163; Fri, 2 Jul 1999 16:47:55 +0930 (CST) Date: Fri, 2 Jul 1999 16:47:55 +0930 From: Greg Lehey To: Mike Smith Cc: Warner Losh , Dan Strick , freebsd-hackers@FreeBSD.ORG, FreeBSD-mobile@FreeBSD.ORG Subject: Re: pccard problems Message-ID: <19990702164755.S87392@freebie.lemis.com> References: <19990702144336.P87392@freebie.lemis.com> <199907020710.AAA00533@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907020710.AAA00533@dingo.cdrom.com>; from Mike Smith on Fri, Jul 02, 1999 at 12:10:28AM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 2 July 1999 at 0:10:28 -0700, Mike Smith wrote: >> Yes. Somebody else told me that. I tried it (and confirmed that show >> displayed it, and that it was spelt right), and it still grabbed irq >> 5. Just to make sure it wasn't lying, I pulled the Ethernet board. >> No message, and when I tried a ping, the machine locked up solid. >> This is 3.2-RELEASE; when I'm finished what I'm doing, I'll look for >> why it's not reacting correctly. > > You may be loading the pcic KLD as well as having it built into the > kernel. Nope: === grog@mojave (/dev/ttyp0) ~ 1 -> kldstat Id Refs Address Size Name 1 2 0xc0100000 1ed760 kernel 2 1 0xc0966000 d000 linux.ko === grog@mojave (/dev/ttyp0) ~ 2 -> Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 1: 4:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 516DD15437; Fri, 2 Jul 1999 01:04:25 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA08833; Fri, 2 Jul 1999 17:34:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA94606; Fri, 2 Jul 1999 17:34:22 +0930 (CST) Date: Fri, 2 Jul 1999 17:34:22 +0930 From: Greg Lehey To: FreeBSD Hackers , FreeBSD current users Subject: HEADS UP: Changes in Vinum Message-ID: <19990702173421.T87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been following up on a suggestion Jordan made earlier this week, and I've now introduced some simplified configuration commands for Vinum, in -CURRENT only. I think they cover a fair number of the situations you're likely to need, but they're not intended to be comprehensive. Still, I'd like to make them as good as they can be, and there's a good chance that I'll change them in some detail or another. There's too much to say for this message; RTFM (vinum(8)) and look for the 'concat', 'mirror' and 'stripe' commands and the section SIMPLIFIED CONFIGURATION. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 3:44:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mu.egroups.com (mu.egroups.com [207.138.41.151]) by hub.freebsd.org (Postfix) with SMTP id 3E89614DC3 for ; Fri, 2 Jul 1999 03:44:38 -0700 (PDT) (envelope-from haodongpan@netease.com) Received: from [10.1.2.26] by mu.egroups.com with NNFMP; 01 Jul 1999 16:18:08 -0000 Date: Thu, 01 Jul 1999 08:17:59 -0700 From: haodongpan@netease.com To: freebsd-hackers@freebsd.org Subject: how to start to be a hacker? Message-ID: <7lg0r7$becd@eGroups.com> User-Agent: eGroups-EW/0.73 Content-Length: 85 X-Mailer: www.eGroups.com Message Poster Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know the basic admin knowledge of UNIX,perl,cgi,c how to become a hacker? thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 4:48:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 9BD1B15059 for ; Fri, 2 Jul 1999 04:48:38 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 02 Jul 1999 12:48:22 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id N96YDL6M; Fri, 2 Jul 1999 12:49:15 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 1101nx-000PFO-00; Fri, 2 Jul 1999 12:48:29 +0100 Date: Fri, 2 Jul 1999 12:48:29 +0100 To: haodongpan@netease.com Cc: freebsd-hackers@freebsd.org Subject: Re: how to start to be a hacker? Message-Id: <19990702124829.A97003@palmerharvey.co.uk> References: <7lg0r7$becd@eGroups.com> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <7lg0r7$becd@eGroups.com>; from haodongpan@netease.com on Thu, Jul 01, 1999 at 08:17:59AM -0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > I know the basic admin knowledge of UNIX,perl,cgi,c > how to become a hacker? Not everyone will agree with this, but you may want to look at: http://www.tuxedo.org/~esr/faqs/index.html -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 5:18:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id D2E4F14D2A for ; Fri, 2 Jul 1999 05:18:11 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.9.3/8.9.3) id OAA16854 for ; Fri, 2 Jul 1999 14:18:09 +0200 (SAST) Received: by citadel via recvmail id 16789; Fri Jul 2 14:17:29 1999 Message-ID: <377CAE83.EB1F7EF5@cdsec.com> Date: Fri, 02 Jul 1999 14:20:19 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Porting LILO to FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I currently have Linux installed in a DOS partition for one reason only, and that is that I want to use LILO. I would love to be able to get LILO working under FreeBSD so that I can free up all the space used up by Linux. The reason I want to use LILO is because it allows me to swap my C: and D: drives around when booting DOS. This lets me have Win95 bootable on my real C: drive, but lets me boot a Win95-free DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to C:. I haven't found any other freeware boot loaders that have this ability. Has anyone ever attempted to port LILO to FreeBSD? I imagine that it should be possible, but would require some serious changes in low-level disk access code, to map disk files to physical disk locations, etc. If anyone has any experience with this, or has any advice (including pointing me to other boot loaders that can get the BIOS to switch disks that will work purely from DOS or FreeBSD), please let me know... TIA gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 5:49:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 0808215059 for ; Fri, 2 Jul 1999 05:49:31 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 10202 invoked by uid 1001); 2 Jul 1999 12:49:32 -0000 Date: Fri, 2 Jul 1999 08:49:32 -0400 (EDT) From: Vince Vielhaber To: Graham Wheeler Cc: hackers@freebsd.org Subject: Re: Porting LILO to FreeBSD In-Reply-To: <377CAE83.EB1F7EF5@cdsec.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, 2 Jul 1999, Graham Wheeler wrote: > Hi all > > I currently have Linux installed in a DOS partition for one reason > only, and that is that I want to use LILO. I would love to be able > to get LILO working under FreeBSD so that I can free up all the space > used up by Linux. The reason I want to use LILO is because it allows > me to swap my C: and D: drives around when booting DOS. This lets me > have Win95 bootable on my real C: drive, but lets me boot a Win95-free > DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to > C:. I haven't found any other freeware boot loaders that have this > ability. > > Has anyone ever attempted to port LILO to FreeBSD? I imagine that it > should be possible, but would require some serious changes in low-level > disk access code, to map disk files to physical disk locations, etc. > If anyone has any experience with this, or has any advice (including > pointing me to other boot loaders that can get the BIOS to switch > disks that will work purely from DOS or FreeBSD), please let me know... On CD #1 there's a file called osbsbeta.exe. That version allows you to boot from different physical devices whereas osbs135.exe doesn't. I'm using it on one machine that has 95, dos6, os2 and freebsd on different drives. I should mention that CD #1 I'm referring to is from 2.2.6, I haven't looked at any newer versions. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 6: 9:30 1999 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 4A8EB14F3A; Fri, 2 Jul 1999 06:09:03 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA17662; Fri, 2 Jul 1999 15:09:01 +0200 (CEST) (envelope-from des) To: chat@freebsd.org Cc: ofug-chat@ofug.org Subject: IETF 45 From: Dag-Erling Smorgrav Date: 02 Jul 1999 15:09:01 +0200 Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Bcc: to hackers, Cc: to ofug-chat] As you may be aware of, IETF 45 will be held in Oslo, Norway the week after next. If any of you are going, or know of FreeBSD people who are going, and are interested in getting together with norwegian FreeBSD users and developers in a social context, don't hesitate to contact the Oslo FreeBSD User Group (http://www.ofug.org/). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 6:20:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 6B3C214C18; Fri, 2 Jul 1999 06:15:41 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id QAA59787; Fri, 2 Jul 1999 16:13:52 +0300 (EEST) (envelope-from ru) Date: Fri, 2 Jul 1999 16:13:52 +0300 From: Ruslan Ermilov To: Valentin Nechayev Cc: peter@FreeBSD.org, hackers@FreeBSD.org Subject: Re: rmail Message-ID: <19990702161352.A52135@relay.ucb.crimea.ua> Mail-Followup-To: Valentin Nechayev , peter@FreeBSD.org, hackers@freebsd.org References: <19990702154150.D23322@lucky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990702154150.D23322@lucky.net>; from Valentin Nechayev on Fri, Jul 02, 1999 at 03:41:50PM +0300 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Redirected to -hackers] On Fri, Jul 02, 1999 at 03:41:50PM +0300, Valentin Nechayev wrote: > Why rmail is sitting in /bin, while it is useful only with uuxqt & sendmail? > Historically, I think. NetBSD and OpenBSD install it to /bin as well. > Why it is linked statically? > It is linked dynamically in 3.x and CURRENT as of src/bin/rmail/Makefile,v 1.7 1998/08/04 15:19:16 peter Exp $ # ldd /bin/rmail /bin/rmail: libc.so.3 => /usr/lib/libc.so.3 (0x28063000) > Is it more right to move it to /usr/sbin or /usr/libexec/uucp and link > dynamically? > Personally I think it would make sense. The suggested path (see src/contrib/sendmail/rmail/Makefile.m4) is /usr/sbin. Let's see what Peter thinks. Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 6:25:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 2E3E714D09 for ; Fri, 2 Jul 1999 06:25:02 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.9.3/8.9.3) id PAA21069; Fri, 2 Jul 1999 15:24:29 +0200 (SAST) Received: by citadel via recvmail id 21003; Fri Jul 2 15:24:14 1999 Message-ID: <377CBE28.F3D4E15A@cdsec.com> Date: Fri, 02 Jul 1999 15:27:04 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Vince Vielhaber Cc: Graham Wheeler , hackers@freebsd.org Subject: Re: Porting LILO to FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vince Vielhaber wrote: > > On Fri, 2 Jul 1999, Graham Wheeler wrote: > > > Hi all > > > > I currently have Linux installed in a DOS partition for one reason > > only, and that is that I want to use LILO. I would love to be able > > to get LILO working under FreeBSD so that I can free up all the space > > used up by Linux. The reason I want to use LILO is because it allows > > me to swap my C: and D: drives around when booting DOS. This lets me > > have Win95 bootable on my real C: drive, but lets me boot a Win95-free > > DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to > > C:. I haven't found any other freeware boot loaders that have this > > ability. > > > > Has anyone ever attempted to port LILO to FreeBSD? I imagine that it > > should be possible, but would require some serious changes in low-level > > disk access code, to map disk files to physical disk locations, etc. > > If anyone has any experience with this, or has any advice (including > > pointing me to other boot loaders that can get the BIOS to switch > > disks that will work purely from DOS or FreeBSD), please let me know... > > On CD #1 there's a file called osbsbeta.exe. That version allows you > to boot from different physical devices whereas osbs135.exe doesn't. > I'm using it on one machine that has 95, dos6, os2 and freebsd on > different drives. > > I should mention that CD #1 I'm referring to is from 2.2.6, I haven't > looked at any newer versions. I have a pretty full set up to 3.2 so finding it won't be a problem. Does it actually logically switch the disks, though? There are several that will allow booting from secondary disks; what I like about LILO is that when I boot Win95, then C:\WINDOWS is the main windows directory, and when I boot DoS 6.2 and run Win 3.1, then C:\WINDOWS is *still* the main directory (for 3.1 this time). I.e. under DOS, C: is actually the secondary drive and D: the primary. To do this magic lilo has to load up a special secondary loader program (/boot/any_d.b). I'll check it out, though. I used to use osbs135 before LILO, and like it more than LILO, but it didn't have the critical feature... It would still be interesting to port LILO to FreeBSD... The only reason I even want to do this is that I still have a number of old DOS games that won't work under Win95. And dosemu and Wine just don't cut it either, unfortunately. -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 7:46:28 1999 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 C936B1573F for ; Fri, 2 Jul 1999 07:46:26 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id IAA21408; Fri, 2 Jul 1999 08:46:10 -0600 (MDT) Date: Fri, 2 Jul 1999 08:46:10 -0600 From: "Ronald G. Minnich" To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reason for slow user-user memory copy 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 If you're doing this kind of thing you really should spend $5K for a vmetro PCI analyzer and learn how to use it. It will answer your questions. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 7:56:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from imo25.mx.aol.com (imo25.mx.aol.com [198.81.17.69]) by hub.freebsd.org (Postfix) with ESMTP id E272614C3F for ; Fri, 2 Jul 1999 07:56:49 -0700 (PDT) (envelope-from LupusMcGee@aol.com) Received: from LupusMcGee@aol.com by imo25.mx.aol.com (IMOv20.21) id nXYBa03295 (3984) for ; Fri, 2 Jul 1999 10:56:23 -0400 (EDT) From: LupusMcGee@aol.com Message-ID: <4f8b328b.24ae2d17@aol.com> Date: Fri, 2 Jul 1999 10:56:23 EDT Subject: remove To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Windows 95 sub 13 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: 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 Jul 2 8: 7: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id 0F67B14C42 for ; Fri, 2 Jul 1999 08:07:01 -0700 (PDT) (envelope-from cmcurtin@cis.ohio-state.edu) Received: from gold.cis.ohio-state.edu (cmcurtin@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id LAA07072; Fri, 2 Jul 1999 11:07:00 -0400 (EDT) Received: (from cmcurtin@localhost) by gold.cis.ohio-state.edu (8.9.1/8.9.1) id LAA04243; Fri, 2 Jul 1999 11:06:59 -0400 (EDT) To: haodongpan@netease.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: <7lg0r7$becd@eGroups.com> X-Face: L"IcL.b%SDN]0Kql2b`e.}+i05V9fi\yX#H1+Xl)3!+n/3?5`%-SA-HDgPk9uTk<3dv^J5DCgal)-E{`zN#*o6F|y>r)\< Date: 02 Jul 1999 11:06:59 -0400 In-Reply-To: haodongpan@netease.com's message of "Thu, 01 Jul 1999 08:17:59 -0700" Message-ID: Lines: 18 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Thu, 01 Jul 1999 08:17:59 -0700, haodongpan@netease.com said: haodongpan> I know the basic admin knowledge of UNIX,perl,cgi,c how to haodongpan> become a hacker? How to become a hacker in general: http://www.tuxedo.org/~esr/faqs/hacker-howto.html Of course, not everyone has the personality, intensity, background, and whatever else that it takes to be a hacker. To become a FreeBSD hacker in particular, find yourself a project to help, perhaps one at http://www.freebsd.org/projects/, or start working on one of the tasks-to-do listed online at http://www.freebsd.org/handbook/contrib.html. -- Matt Curtin cmcurtin@interhack.net http://www.interhack.net/people/cmcurtin/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 8:11:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 4AE3414CE1 for ; Fri, 2 Jul 1999 08:11:42 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id LAA24986; Fri, 2 Jul 1999 11:10:30 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Fri, 2 Jul 1999 11:10:30 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Graham Wheeler Cc: hackers@FreeBSD.ORG Subject: Re: Porting LILO to FreeBSD 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, 2 Jul 1999, Vince Vielhaber wrote: > On Fri, 2 Jul 1999, Graham Wheeler wrote: > > > Hi all > > > > I currently have Linux installed in a DOS partition for one reason > > only, and that is that I want to use LILO. I would love to be able > > to get LILO working under FreeBSD so that I can free up all the space > > used up by Linux. The reason I want to use LILO is because it allows > > me to swap my C: and D: drives around when booting DOS. This lets me > > have Win95 bootable on my real C: drive, but lets me boot a Win95-free > > DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to > > C:. I haven't found any other freeware boot loaders that have this > > ability. > > > > Has anyone ever attempted to port LILO to FreeBSD? I imagine that it > > should be possible, but would require some serious changes in low-level > > disk access code, to map disk files to physical disk locations, etc. > > If anyone has any experience with this, or has any advice (including > > pointing me to other boot loaders that can get the BIOS to switch > > disks that will work purely from DOS or FreeBSD), please let me know... > > On CD #1 there's a file called osbsbeta.exe. That version allows you > to boot from different physical devices whereas osbs135.exe doesn't. > I'm using it on one machine that has 95, dos6, os2 and freebsd on > different drives. The standard boot partition selection softwre also works fine booting windoze OS's from other disks. All you need to do is set the "disk id" in the DOS MBR to the correct number, 0x81 for your second disk. That's the only thing that MS doesn't do correctly whe installing the OS on the non-primary disk. I used to do this a long time ago to boot FreeBSD of the "C" drive and the other stuff off of "second C" drive. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 8:20:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id BEEFA14C42 for ; Fri, 2 Jul 1999 08:20:52 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA05071; Fri, 2 Jul 1999 09:20:34 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377CD8C1.2E7E0BFE@softweyr.com> Date: Fri, 02 Jul 1999 09:20:33 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dominic Mitchell Cc: haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: <7lg0r7$becd@eGroups.com> <19990702124829.A97003@palmerharvey.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dominic Mitchell wrote: > > On Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > > I know the basic admin knowledge of UNIX,perl,cgi,c > > how to become a hacker? > > Not everyone will agree with this, but you may want to look at: > > http://www.tuxedo.org/~esr/faqs/index.html Disagree? Eric even managed to mention the existence of freely available BSD! I'm ecstatic! Actually, it's not a bad description of what most of us have actually done. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 8:42:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id AE6E614F25 for ; Fri, 2 Jul 1999 08:42:11 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.9.3/8.9.3) id RAA00845; Fri, 2 Jul 1999 17:41:25 +0200 (SAST) Received: by citadel via recvmail id 842; Fri Jul 2 17:41:00 1999 Message-ID: <377CDE36.19BD1753@cdsec.com> Date: Fri, 02 Jul 1999 17:43:50 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Adrian Filipi-Martin Cc: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Porting LILO to FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Filipi-Martin wrote: > > > The standard boot partition selection softwre also works fine > booting windoze OS's from other disks. All you need to do is set the "disk > id" in the DOS MBR to the correct number, 0x81 for your second disk. That's > the only thing that MS doesn't do correctly whe installing the OS on the > non-primary disk. I used to do this a long time ago to boot FreeBSD of the > "C" drive and the other stuff off of "second C" drive. I'll try that this weekend. Preumably I can just do this under FreeBSD using fdisk? > -- > [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] Kewel company name! -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 9: 4:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r43.bfm.org [208.18.213.139]) by hub.freebsd.org (Postfix) with ESMTP id 52C8514F37 for ; Fri, 2 Jul 1999 09:04:38 -0700 (PDT) (envelope-from adam@whizkidtech.net) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id LAA00241; Fri, 2 Jul 1999 11:04:32 -0500 (CDT) (envelope-from adam) Date: Fri, 2 Jul 1999 11:04:01 -0500 From: "G. Adam Stanislav" To: haodongpan@netease.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? Message-ID: <19990702110401.A225@whizkidtech.net> References: <7lg0r7$becd@eGroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <7lg0r7$becd@eGroups.com>; from haodongpan@netease.com on Thu, Jul 01, 1999 at 08:17:59AM -0700 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ 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 Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > I know the basic admin knowledge of UNIX,perl,cgi,c > how to become a hacker? You either are a hacker, or you are not. It is not something someone else can teach you. Do you have the innate curiosity to take things apart just to learn how they work? Do you have the ability to solve problems? The drive to seek solutions? Are you capable of seeing the overall picture while paying attention to the tiniest of details? Are you not satisfied with a good-enough solution, but, instead, thrive to make it do all it is supposed to do, and to do it in a most efficient way possible? Are you willing to share your experience and knowledge with others for the shear pleasure of sharing it rather than for making a quick buck, amd do so without ever telling them to RTFM? Do you lose all concept of time while working on a problem? Forget to eat lunch and supper, or go to bed on time? Do you like to tinker with low-level solutions? Going down to the level of registers and wires, thinking of C as a high-level language? When you see a problem, do you try to solve it instead of telling others they should? After spending hours, days, weeks, writing code, are you willing to delete it all without winking an eye as soon as a better solution presents itself, and never look back? Do you prefer to keep things simple instead of producing monstrosities that can do everything, but nothing right? Are you willing to accept other people's good solutions instead of reinventing the wheel? If you answered yes to most of these questions, chances are you are a hacker. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 9: 7: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 3A97914F37 for ; Fri, 2 Jul 1999 09:06:55 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA251486413; Fri, 2 Jul 1999 07:53:33 -0400 Date: Fri, 2 Jul 1999 07:53:33 -0400 (EDT) From: Bill Fumerola To: "G. Adam Stanislav" Cc: haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? In-Reply-To: <19990702110401.A225@whizkidtech.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 Fri, 2 Jul 1999, G. Adam Stanislav wrote: > On Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > > I know the basic admin knowledge of UNIX,perl,cgi,c > > how to become a hacker? > > You either are a hacker, or you are not. It is not something someone else > can teach you. This deserves a FAQ entry. What an awesome response. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Fri Jul 2 10: 0:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 941DE14FD7 for ; Fri, 2 Jul 1999 10:00:07 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id MAA25152; Fri, 2 Jul 1999 12:58:04 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Fri, 2 Jul 1999 12:58:04 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Graham Wheeler Cc: hackers@FreeBSD.ORG Subject: Re: Porting LILO to FreeBSD In-Reply-To: <377CDE36.19BD1753@cdsec.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, 2 Jul 1999, Graham Wheeler wrote: > Adrian Filipi-Martin wrote: > > > > > > The standard boot partition selection softwre also works fine > > booting windoze OS's from other disks. All you need to do is set the "disk > > id" in the DOS MBR to the correct number, 0x81 for your second disk. That's > > the only thing that MS doesn't do correctly whe installing the OS on the > > non-primary disk. I used to do this a long time ago to boot FreeBSD of the > > "C" drive and the other stuff off of "second C" drive. > > I'll try that this weekend. Preumably I can just do this under FreeBSD > using fdisk? You cannot do it using fdisk. I tonly manipulates the parition table poriton of the MBR. The "bios device" number is in portion before the partition table. I hesitate to just give an offset and say poke away, so I'd look for a disk editing tool like Norton Disk Editor. That's what I used when I last did this a few years ago. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 10: 3:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id D1BA3152AA for ; Fri, 2 Jul 1999 10:03:44 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id LAA16924; Fri, 2 Jul 1999 11:03:43 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id LAA25062; Fri, 2 Jul 1999 11:03:42 -0600 (MDT) Date: Fri, 2 Jul 1999 11:03:41 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990702110341.A24969@gras-varg.worldgate.com> References: <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907020504.XAA41362@harmony.village.org>; from Warner Losh on Thu, Jul 01, 1999 at 11:04:54PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Thu, Jul 01, 1999 at 11:04:54PM -0600 > In message <19990701163631.A20163@gras-varg.worldgate.com> Greg Skafte writes: > : I've got an adaptec 1542 card using aha driver and RELENG_3 detects it no > : problems. > > OK. > > : If I use the adaptec on board utilities it finds my UMAX scanner no probs. > > OK. > > : when I try to boot the machine hangs just after the waiting for scsi to > : settle message. > > Now I'm confused. Is this in -current where you are having the > problems? nope 3.2-stable cvsuped yesterday > > : I've gabbed these as best as I can since the machine doesn't finish booting > : so I can't grab a dmesg and I don't have a serial console..... > > OK. > > Before going too far, please make sure that termination is currect. > I've seen the "timeout timeout ...not in timeout" sequence when that > was the case. I would have expected that from identical hardware with > a RELENG_3 kernel, however. It is possible that something in the > emulation layer in -current isn't working, or that -current's CAM does > things a little faster than RELENG_3's CAM did, this exposing another > bug in the aha driver. I didn't torture test it with anything except > slow disks and a CDROM changer... Any other device will likely work > or not work due entirely to chance. I verified the terminations, if the termination is wrong the 1542's onboard diagnostics are unable to detect the scanner. I also verified that both devices are narrow. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 11:21:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B288514C93 for ; Fri, 2 Jul 1999 11:21:23 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA04452; Fri, 2 Jul 1999 14:21:22 -0400 (EDT) (envelope-from wollman) Date: Fri, 2 Jul 1999 14:21:22 -0400 (EDT) From: Garrett Wollman Message-Id: <199907021821.OAA04452@khavrinen.lcs.mit.edu> To: "Brian F. Feldman" Cc: hackers@freebsd.org Subject: Re: cvs commit: src/usr.sbin/ac ac.8 ac.c In-Reply-To: References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Remember, the question was, "Do we need to spend the effort making all > of our programs support the use of - to denote std{in,out}?" No, because most of them (for which such an option might be relevant) already do, or else don't need it (because they default to stdin). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 11:30:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 9B90F14CE0; Fri, 2 Jul 1999 11:30:55 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA001865068; Fri, 2 Jul 1999 10:17:48 -0400 Date: Fri, 2 Jul 1999 10:17:48 -0400 (EDT) From: Bill Fumerola To: chat@FreeBSD.org Subject: eBay Listing confirmation - Item 125965474: Jordan K. Hubbard (fwd) 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 http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=125965474 - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Fri Jul 2 12:27:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-11-dbn.dial-up.net [196.34.155.11]) by hub.freebsd.org (Postfix) with ESMTP id 70F2814DE9 for ; Fri, 2 Jul 1999 12:27:25 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA16275; Fri, 2 Jul 1999 21:25:23 +0200 (SAST) From: Robert Nordier Message-Id: <199907021925.VAA16275@ceia.nordier.com> Subject: Re: Porting LILO to FreeBSD In-Reply-To: from Adrian Filipi-Martin at "Jul 2, 1999 12:58:04 pm" To: adrian@ubergeeks.com (Adrian Filipi-Martin), gram@cequrux.com (Graham Wheeler) Date: Fri, 2 Jul 1999 21:25:21 +0200 (SAST) Cc: hackers@freebsd.org 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 > > > The standard boot partition selection softwre also works fine > > > booting windoze OS's from other disks. All you need to do is set the "disk > > > id" in the DOS MBR to the correct number, 0x81 for your second disk. That's > > > the only thing that MS doesn't do correctly whe installing the OS on the > > > non-primary disk. I used to do this a long time ago to boot FreeBSD of the > > > "C" drive and the other stuff off of "second C" drive. > > > > I'll try that this weekend. Preumably I can just do this under FreeBSD > > using fdisk? > > You cannot do it using fdisk. I tonly manipulates the parition > table poriton of the MBR. The "bios device" number is in portion before > the partition table. I hesitate to just give an offset and say poke away, > so I'd look for a disk editing tool like Norton Disk Editor. That's what I > used when I last did this a few years ago. In the standard Microsoft way of doing things, the BIOS drive number is recorded both in the MBR (sector 0 of the disk) and in the DOS boot sector (sector 0 of the "fdisk partition"). A Microsoft-style MBR gets the drive number from the byte at offset 0 of the partition entry (field dp_flag of structure dos_partition in /sys/sys/disklabel.h). This is usually known as the "active flag", and all standard fdisk utilities set this to 0x80 (corresponding to BIOS fixed drive 0) when flagging a partition as active. This can be patched by hand to some other value (eg. 0x81 for BIOS fixed drive 1) but in a standard pre-Win95 OSR2 MBR this causes problems, as the MBR code validates the partition table entries, and will respond to the 0x81 with the message "Invalid partition table" followed by a hang. From Win95 OSR2, the MBR code tolerates value 0x80 through 0xff in the "dp_flag" field. The FreeBSD /sys/boot/i386/mbr code in -current also allows BIOS drive numbers other than 0x80 in this field. You can also just install boot0 on both drives (and, no doubt, many other boot managers as well) and forget about the MBR issues. If you want to boot DOS specifically (and all Windows versions other than NT are essentially DOS at the lowest level), you would need to set the drive number in the DOS boot sector (the equivalent of the FreeBSD boot1 bootstrap). This occurs at at least three different offsets, depending on the FAT filesystem parameters, but it should be possible to deduce the logic required to find it by looking at src/sbin/newfs_msdos/newfs_msdos.c: see the field drv in the structure bsx. The easiest approach, probably adopted by LILO, is to install a wrapper around the BIOS int 0x13 services and just change drive numbers as they go by. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 13: 1:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (Postfix) with SMTP id E09FD14BF2 for ; Fri, 2 Jul 1999 13:01:27 -0700 (PDT) (envelope-from wayne@crb.crb-web.com) Received: (qmail 28152 invoked by uid 1001); 2 Jul 1999 20:12:32 -0000 Date: Fri, 2 Jul 1999 16:12:32 -0400 (EDT) From: Wayne Cuddy Reply-To: wayne@crb-web.com To: FreeBSD Hackers List Subject: poll() vs select() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am struggling through understanding device drivers under freebsd. I have nice book and linux device drivers and some older ones on the UNIX device drivers but nothing seems to match perfectly with freebsd... So stay tuned for more questions.... Correct me if I am wrong... After reading the insanely small device drivers tutorial from the FBSD web page I see that the functionality of the select system call was moved from d_select() in 2.2 kernels to d_poll() in 3.x which now supports the select() and poll() system calls. My question is really one of usage. Why would one us poll() over select()? Is select eventually going to go away for some reason? Thanks, Wayne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 13:27: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hermit.bcs.nostrum.com (hermit.bcs.nostrum.com [206.28.8.2]) by hub.freebsd.org (Postfix) with ESMTP id E3DA815183 for ; Fri, 2 Jul 1999 13:27:01 -0700 (PDT) (envelope-from daved@nostrum.com) Received: (from daved@localhost) by hermit.bcs.nostrum.com (8.9.3/8.9.3) id PAA32348; Fri, 2 Jul 1999 15:25:58 -0500 (CDT) Date: Fri, 2 Jul 1999 15:25:57 -0500 From: Dave Duchscher To: Graham Wheeler Cc: hackers@FreeBSD.ORG Subject: Re: Porting LILO to FreeBSD Message-ID: <19990702152557.A32271@hermit.bcs.nostrum.com> References: <377CAE83.EB1F7EF5@cdsec.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="k+w/mQv8wyuph6w0"; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.5i In-Reply-To: <377CAE83.EB1F7EF5@cdsec.com>; from Graham Wheeler on Fri, Jul 02, 1999 at 02:20:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii > I currently have Linux installed in a DOS partition for one reason > only, and that is that I want to use LILO. I would love to be able > to get LILO working under FreeBSD so that I can free up all the > space used up by Linux. The reason I want to use LILO is because it > allows me to swap my C: and D: drives around when booting DOS. This > lets me have Win95 bootable on my real C: drive, but lets me boot a > Win95-free DOS 6.2 and Windows 3.1 on my D: drive, which gets > logically mapped to C:. I haven't found any other freeware boot > loaders that have this ability. Randish Partition Manager will allow you to do this as well. You can find it at: http://www.users.intercom.com/~ranish/part/ DaveD --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: VMYDWtMRFMHv+7sRftesEZmhORtRLfz+ iQCVAwUBN30SP/sJYFdBGj/VAQGqsQP/Vh179bK682Xx7/OZJbKtLLpjx75IjLai OHZFyqyQy1xbeviH5t2fKMaaEzyd1YYpwKVPw8MfDbIUQyOx5lkzDTrVhZD/piZf Xkplja3jFgnIi82dxMmCCl7nVnQ5KghawXuctgQLE3UeXz/Ki52hmqbt9eRFvBNC /+5lYxeInXw= =WNYz -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 13:53: 7 1999 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 893EE14C45 for ; Fri, 2 Jul 1999 13:53:01 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA08036; Fri, 2 Jul 1999 14:53:00 -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 OAA46204; Fri, 2 Jul 1999 14:52:12 -0600 (MDT) Message-Id: <199907022052.OAA46204@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 11:03:41 MDT." <19990702110341.A24969@gras-varg.worldgate.com> References: <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> Date: Fri, 02 Jul 1999 14:52:12 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702110341.A24969@gras-varg.worldgate.com> Greg Skafte writes: : nope 3.2-stable cvsuped yesterday OK. Are you saying that this used to work, but that it doesn't now? Justin did make some changes to the aha driver in -current which would keep it from losing a race, but I don't know if that was back ported or not. I'll have to investigate. : I verified the terminations, if the termination is wrong the : 1542's onboard diagnostics are unable to detect the scanner. : I also verified that both devices are narrow. Bummer. I had hoped that this was the "usual" problem :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 14:22:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osgroup.com (unknown [38.229.41.6]) by hub.freebsd.org (Postfix) with ESMTP id 283AA14E67 for ; Fri, 2 Jul 1999 14:22:03 -0700 (PDT) (envelope-from stan@laurent.osgroup.com) Received: from localhost (stan@localhost) by osgroup.com (8.7.6/8.6.12) with SMTP id QAA04299; Fri, 2 Jul 1999 16:10:57 -0500 Date: Fri, 2 Jul 1999 16:10:57 -0500 (CDT) From: Stan Shkolnyy To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: mbufs question/problem In-Reply-To: <199906302150.RAA01512@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 On Wed, 30 Jun 1999, Dennis wrote: > > I have a customer who has been experiencing "slow downs" with a freebsd > router....they have substantially increased performance by reducing > MINCLSIZE. I havent tracked the source, but im trying to hypothesize what > it might be. On the surface I cant see any relationship since very few > routines seem dependent on that value (m_devget() in particular, but I dont > believe they are using any driver that use it). Is it possible that they > are running out of small mbufs (they have NMBCLUSTERS set to a very high > value)? > > Any ideas would be helpful. I have not noticed answers so far, so maybe their drivers copy mbufs very often. AFAIK, "small" mbufs are indeed copied but "cluster" ones are not, so when they forced the system to use more "cluster" mbufs, they got substantial savings on copy operations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 15:59:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.gw.tislabs.com (relay.gw.tislabs.com [192.94.214.100]) by hub.freebsd.org (Postfix) with ESMTP id 69E2115091 for ; Fri, 2 Jul 1999 15:59:36 -0700 (PDT) (envelope-from stevek@tislabs.com) Received: by relay.gw.tislabs.com; id TAA07827; Fri, 2 Jul 1999 19:01:20 -0400 (EDT) Received: from clipper.gw.tislabs.com(10.33.1.2) by relay.gw.tislabs.com via smap (4.1) id xma007809; Fri, 2 Jul 99 19:00:47 -0400 Received: from mufasa.va.tislabs.com (mufasa.va.tislabs.com [192.168.10.18]) by clipper.gw.tislabs.com (8.9.1/8.9.1) with ESMTP id SAA02634 for ; Fri, 2 Jul 1999 18:58:24 -0400 (EDT) Received: from localhost (stevek@localhost) by mufasa.va.tislabs.com (8.8.7/8.8.7) with SMTP id SAA00367 for ; Fri, 2 Jul 1999 18:53:23 -0400 (EDT) (envelope-from stevek@mufasa.va.tislabs.com) Date: Fri, 2 Jul 1999 18:53:23 -0400 (EDT) From: Steve Kiernan To: freebsd-hackers@freebsd.org Subject: Re: Usage of 'gdb' command in DDB 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, 2 Jul 1999, Greg Lehey wrote: > On Thursday, 1 July 1999 at 18:47:27 -0500, Stan Shkolnyy wrote: > > Hello All, > > > > Well, I entered 'gdb', then 'continue' and now I can debug the kernel > > remotely. How do I switch DDB back? Ctrl-Alt-Esc now causes DDB to > > contact the remote GDB instead of accepting input from me. > > A nuisance, isn't it? There's no documented way. I have this in my > .gdbinit: > > define ddb > set boothowto=0x80000000 > s > end > document ddb > Switch back to ddb. > end > > That works with -CURRENT. Don't count on it staying that way. You should just be able to 'detach' from gdb. At least, that's what I had been using on 2.2.x, not sure if it works on -CURRENT. -- Stephen Kiernan stevek@tislabs.com NAI Labs, A Division of Network Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 16: 2:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 50D3015091 for ; Fri, 2 Jul 1999 16:02:09 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id RAA05066; Fri, 2 Jul 1999 17:02:08 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id RAA27688; Fri, 2 Jul 1999 17:02:07 -0600 (MDT) Date: Fri, 2 Jul 1999 17:02:07 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@freebsd.org Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990702170206.B25510@gras-varg.worldgate.com> References: <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907022052.OAA46204@harmony.village.org>; from Warner Losh on Fri, Jul 02, 1999 at 02:52:12PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Fri, Jul 02, 1999 at 02:52:12PM -0600 > In message <19990702110341.A24969@gras-varg.worldgate.com> Greg Skafte writes: > : nope 3.2-stable cvsuped yesterday > > OK. Are you saying that this used to work, but that it doesn't now? Nope I'm saying that its not working now, don't know about the previous history. I do know that amancio (sp) has a scsi umax working (freebsd-hacker ~April 19 when jordon was having probs with an HP) .... I haven't spent anytime today (chasing a dma gremlins), but I'm gonna try it on a different machine and cable later this weekend (just in case....) > Justin did make some changes to the aha driver in -current which would > keep it from losing a race, but I don't know if that was back ported > or not. I'll have to investigate. > > : I verified the terminations, if the termination is wrong the > : 1542's onboard diagnostics are unable to detect the scanner. > : I also verified that both devices are narrow. > > Bummer. I had hoped that this was the "usual" problem :-(. I know .... > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 16:23:17 1999 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 8067B14C16 for ; Fri, 2 Jul 1999 16:23:12 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA08326; Fri, 2 Jul 1999 17:23: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 RAA46803; Fri, 2 Jul 1999 17:22:24 -0600 (MDT) Message-Id: <199907022322.RAA46803@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Fri, 02 Jul 1999 17:02:07 MDT." <19990702170206.B25510@gras-varg.worldgate.com> References: <19990702170206.B25510@gras-varg.worldgate.com> <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> Date: Fri, 02 Jul 1999 17:22:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702170206.B25510@gras-varg.worldgate.com> Greg Skafte writes: : Nope I'm saying that its not working now, don't know about the : previous history. I do know that amancio (sp) has a scsi umax : working (freebsd-hacker ~April 19 when jordon was having probs with : an HP) .... : : I haven't spent anytime today (chasing a dma gremlins), but I'm : gonna try it on a different machine and cable later this weekend : (just in case....) Is it possible to grab the 2.2.8R boot disk and see if that works? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:15:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8561D14D37; Fri, 2 Jul 1999 17:15:23 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-94.ucdavis.edu [169.237.16.222]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA83297; Fri, 2 Jul 1999 17:15:22 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA04722; Sat, 3 Jul 1999 00:15:19 GMT (envelope-from obrien) Date: Fri, 2 Jul 1999 17:15:19 -0700 From: "David O'Brien" To: Dag-Erling Smorgrav , Ruslan Ermilov , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Message-ID: <19990702171519.A3643@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <199907011133.EAA64244@freefall.freebsd.org> <19990701135124.I92508@bitbox.follo.net> <19990701154210.A12020@relay.ucb.crimea.ua> <19990701164430.O92508@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990701164430.O92508@bitbox.follo.net>; from Eivind Eklund on Thu, Jul 01, 1999 at 04:44:30PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... compared to the sources as of today. This gives minimal semantic > difference from the way it worked before the change (which was that if > FTP_PASSIVE_MODE existed, ftp used passive mode). I have to agree with Eivind, I know of people in my lab that have FTP_PASSIVE_MODE defined to nosense values since that is all that was required before. Now what are these poor souls to do when they upgrade to 3.3-R and their environment stops working???? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:18:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DFBE151E4 for ; Fri, 2 Jul 1999 17:18:29 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id SAA07878; Fri, 2 Jul 1999 18:18:28 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id SAA27992; Fri, 2 Jul 1999 18:18:27 -0600 (MDT) Date: Fri, 2 Jul 1999 18:18:27 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990702181826.C25510@gras-varg.worldgate.com> References: <19990702170206.B25510@gras-varg.worldgate.com> <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907022322.RAA46803@harmony.village.org>; from Warner Losh on Fri, Jul 02, 1999 at 05:22:23PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup 2.2.8-Release probed it uk device UMAX 2600S V1.1 type 6 fixed scsi2 Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Fri, Jul 02, 1999 at 05:22:23PM -0600 > In message <19990702170206.B25510@gras-varg.worldgate.com> Greg Skafte writes: > : Nope I'm saying that its not working now, don't know about the > : previous history. I do know that amancio (sp) has a scsi umax > : working (freebsd-hacker ~April 19 when jordon was having probs with > : an HP) .... > : > : I haven't spent anytime today (chasing a dma gremlins), but I'm > : gonna try it on a different machine and cable later this weekend > : (just in case....) > > Is it possible to grab the 2.2.8R boot disk and see if that works? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:18:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 180CD15055; Fri, 2 Jul 1999 17:18:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA01965; Fri, 2 Jul 1999 17:15:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907030015.RAA01965@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.org Cc: Dag-Erling Smorgrav , Ruslan Ermilov , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c In-reply-to: Your message of "Fri, 02 Jul 1999 17:15:19 PDT." <19990702171519.A3643@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jul 1999 17:15:14 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ... compared to the sources as of today. This gives minimal semantic > > difference from the way it worked before the change (which was that if > > FTP_PASSIVE_MODE existed, ftp used passive mode). > > I have to agree with Eivind, I know of people in my lab that have > FTP_PASSIVE_MODE defined to nosense values since that is all that was > required before. Now what are these poor souls to do when they upgrade > to 3.3-R and their environment stops working???? Unless they were dumb enough to set it to "no", the "right" fix would have it keep working. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:22:58 1999 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 3A20514D37 for ; Fri, 2 Jul 1999 17:22:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA08465; Fri, 2 Jul 1999 18:22:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA47103; Fri, 2 Jul 1999 18:22:07 -0600 (MDT) Message-Id: <199907030022.SAA47103@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 18:18:27 MDT." <19990702181826.C25510@gras-varg.worldgate.com> References: <19990702181826.C25510@gras-varg.worldgate.com> <19990702170206.B25510@gras-varg.worldgate.com> <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> Date: Fri, 02 Jul 1999 18:22:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702181826.C25510@gras-varg.worldgate.com> Greg Skafte writes: : Yup 2.2.8-Release probed it That tells me that something that I did to the driver busted this. OK. I'll see if I can recreate it later tonight. Are you willing to run experimental code? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:31: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 298AC1515A for ; Fri, 2 Jul 1999 17:31:02 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id SAA08345; Fri, 2 Jul 1999 18:31:02 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id SAA28098; Fri, 2 Jul 1999 18:31:00 -0600 (MDT) Date: Fri, 2 Jul 1999 18:30:58 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990702183058.D25510@gras-varg.worldgate.com> References: <19990702170206.B25510@gras-varg.worldgate.com> <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907030022.SAA47103@harmony.village.org>; from Warner Losh on Fri, Jul 02, 1999 at 06:22:07PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG since this is the only device on the aha card experimental aha drivers are welcome ..... (remember though that the target is RELENG_3 not current) Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Fri, Jul 02, 1999 at 06:22:07PM -0600 > In message <19990702181826.C25510@gras-varg.worldgate.com> Greg Skafte writes: > : Yup 2.2.8-Release probed it > > That tells me that something that I did to the driver busted this. > OK. I'll see if I can recreate it later tonight. Are you willing to > run experimental code? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:35:27 1999 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 968351537B for ; Fri, 2 Jul 1999 17:35:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA08502; Fri, 2 Jul 1999 18:35:16 -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 SAA47172; Fri, 2 Jul 1999 18:34:30 -0600 (MDT) Message-Id: <199907030034.SAA47172@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 18:30:58 MDT." <19990702183058.D25510@gras-varg.worldgate.com> References: <19990702183058.D25510@gras-varg.worldgate.com> <19990702170206.B25510@gras-varg.worldgate.com> <19990702110341.A24969@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> Date: Fri, 02 Jul 1999 18:34:30 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702183058.D25510@gras-varg.worldgate.com> Greg Skafte writes: : since this is the only device on the aha card experimental aha drivers : are welcome ..... (remember though that the target is RELENG_3 not current) OK. I'll make sure that justin's changes are included in the -stable driver and if not send you off a patch to try. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:43:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9A14815385; Fri, 2 Jul 1999 17:43:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-94.ucdavis.edu [169.237.16.222]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA83445; Fri, 2 Jul 1999 17:43:39 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA04952; Sat, 3 Jul 1999 00:43:38 GMT (envelope-from obrien) Date: Fri, 2 Jul 1999 17:43:37 -0700 From: "David O'Brien" To: Cc@FreeBSD.ORG:Dag-Erling Smorgrav , Ruslan Ermilov , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Message-ID: <19990702174337.D3571@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990702171519.A3643@dragon.nuxi.com> <199907030015.RAA01965@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199907030015.RAA01965@dingo.cdrom.com>; from Mike Smith on Fri, Jul 02, 1999 at 05:15:14PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 02, 1999 at 05:15:14PM -0700, Mike Smith wrote: > > I have to agree with Eivind, I know of people in my lab that have > > FTP_PASSIVE_MODE defined to nosense values since that is all that was > > required before. Now what are these poor souls to do when they upgrade > > to 3.3-R and their environment stops working???? > > Unless they were dumb enough to set it to "no", the "right" fix would > have it keep working. So that makes three of us that believe the check should be agaist "no" rather than "yes". -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:46: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 8409D14CF9 for ; Fri, 2 Jul 1999 17:46:01 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id SAA08875; Fri, 2 Jul 1999 18:46:01 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id SAA28171; Fri, 2 Jul 1999 18:46:00 -0600 (MDT) Date: Fri, 2 Jul 1999 18:45:59 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990702184559.E25510@gras-varg.worldgate.com> References: <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> <19990702183058.D25510@gras-varg.worldgate.com> <199907030034.SAA47172@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907030034.SAA47172@harmony.village.org>; from Warner Losh on Fri, Jul 02, 1999 at 06:34:30PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG THANKS man ..... Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Fri, Jul 02, 1999 at 06:34:30PM -0600 > In message <19990702183058.D25510@gras-varg.worldgate.com> Greg Skafte writes: > : since this is the only device on the aha card experimental aha drivers > : are welcome ..... (remember though that the target is RELENG_3 not current) > > OK. I'll make sure that justin's changes are included in the -stable > driver and if not send you off a patch to try. > > Warner -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 17:56:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id E4B1814CF9; Fri, 2 Jul 1999 17:56:16 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id CAA95032; Sat, 3 Jul 1999 02:56:14 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <012801bec4ee$cfb29380$0e00a8c0@neland.dk> From: "Leif Neland" To: , References: <199907011133.EAA64244@freefall.freebsd.org> <19990701135124.I92508@bitbox.follo.net> <19990701154210.A12020@relay.ucb.crimea.ua> <19990701164430.O92508@bitbox.follo.net> <19990702171519.A3643@dragon.nuxi.com> Subject: Sv: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Date: Sat, 3 Jul 1999 02:54:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: David O'Brien To: Dag-Erling Smorgrav ; Ruslan Ermilov ; Sent: Saturday, July 03, 1999 2:15 AM Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c > > ... compared to the sources as of today. This gives minimal semantic > > difference from the way it worked before the change (which was that if > > FTP_PASSIVE_MODE existed, ftp used passive mode). > > I have to agree with Eivind, I know of people in my lab that have > FTP_PASSIVE_MODE defined to nosense values since that is all that was > required before. Now what are these poor souls to do when they upgrade > to 3.3-R and their environment stops working???? > If there was someplace nice to put it: ERROR! ^G^G^G^G^GFTP_PASSIVE_MODE must be either "yes" or "no" Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 18: 4: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.17]) by hub.freebsd.org (Postfix) with ESMTP id 2523515114 for ; Fri, 2 Jul 1999 18:03:54 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id UAA00670; Fri, 2 Jul 1999 20:03:46 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 2 Jul 1999 20:03:44 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: hackers@freebsd.org Subject: Re: Lizard... X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14205.24876.313315.658481@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lizard has a tetris game built in for those long waits... Now THAT is cool. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 19:39:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 691D214CAF for ; Fri, 2 Jul 1999 19:39:48 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA20238; Fri, 2 Jul 1999 22:39:49 -0400 (EDT) Date: Fri, 2 Jul 1999 22:39:49 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Anthony Kimball Cc: hackers@FreeBSD.ORG Subject: Re: Lizard... In-Reply-To: <14205.24876.313315.658481@avalon.east> 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, 2 Jul 1999, Anthony Kimball wrote: > > Lizard has a tetris game built in for those long waits... > Now THAT is cool. > It's a better idea to not have people waiting for a long time. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Fri Jul 2 19:58:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6175C14D74; Fri, 2 Jul 1999 19:58:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA42743; Fri, 2 Jul 1999 19:57:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: "Cc@FreeBSD.ORG": ; Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c In-reply-to: Your message of "Fri, 02 Jul 1999 17:43:37 PDT." <19990702174337.D3571@dragon.nuxi.com> Date: Fri, 02 Jul 1999 19:57:21 -0700 Message-ID: <42739.930970641@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Four. :) > On Fri, Jul 02, 1999 at 05:15:14PM -0700, Mike Smith wrote: > > > I have to agree with Eivind, I know of people in my lab that have > > > FTP_PASSIVE_MODE defined to nosense values since that is all that was > > > required before. Now what are these poor souls to do when they upgrade > > > to 3.3-R and their environment stops working???? > > > > Unless they were dumb enough to set it to "no", the "right" fix would > > have it keep working. > > So that makes three of us that believe the check should be agaist "no" > rather than "yes". > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 21:27:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 1AD6914F26 for ; Fri, 2 Jul 1999 21:27:36 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA25275; Fri, 2 Jul 1999 23:27:36 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id XAA22288; Fri, 2 Jul 1999 23:27:35 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id XAA17423; Fri, 2 Jul 1999 23:27:34 -0500 (CDT) Date: Fri, 2 Jul 1999 23:27:34 -0500 (CDT) From: Jonathan Lemon Message-Id: <199907030427.XAA17423@free.pcs> To: wayne@crb-web.com, hackers@freebsd.org Subject: Re: poll() vs select() X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >now supports the select() and poll() system calls. My question is really one >of usage. Why would one us poll() over select()? Is select eventually going >to go away for some reason? select() as a user-level call will never go away; there is a large base of code that uses it. poll() is faster (it doesn't have to do bit twiddling), and it's interface is cleaner (it can report invalid fd's, something select() can't do). As its functionality is a superset of select()'s, it is used as the internal implementation for select(). As for new code, use whichever you are comfortable with. Personally, I would recommend poll(), since it provides some added functionality over select() that makes for easier programming. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 21:44:47 1999 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 1C88D15257 for ; Fri, 2 Jul 1999 21:44:41 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA09061; Fri, 2 Jul 1999 22:44:39 -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 WAA00317; Fri, 2 Jul 1999 22:42:21 -0600 (MDT) Message-Id: <199907030442.WAA00317@harmony.village.org> To: Greg Skafte Subject: Re: UMAX scsi scanner on adaptec 1542 Card Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 18:45:59 MDT." <19990702184559.E25510@gras-varg.worldgate.com> References: <19990702184559.E25510@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> <19990702183058.D25510@gras-varg.worldgate.com> <199907030034.SAA47172@harmony.village.org> Date: Fri, 02 Jul 1999 22:42:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702184559.E25510@gras-varg.worldgate.com> Greg Skafte writes: : THANKS man ..... A hunch. I just tried to bring up my 1542CF with the bios disabled in -current and it blew chunks like you described. Is your BIOS disabled? If so, can you enable it and see if that works? It should work with the bios disabled, but I know how painful that can be... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 2 22: 2:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 2441414C7F for ; Fri, 2 Jul 1999 22:02:22 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id BAA22495; Sat, 3 Jul 1999 01:01:08 -0400 (EDT) Date: Sat, 3 Jul 1999 01:01:07 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Jonathan Lemon Cc: wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() In-Reply-To: <199907030427.XAA17423@free.pcs> 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, 2 Jul 1999, Jonathan Lemon wrote: > In article you write: > >now supports the select() and poll() system calls. My question is really one > >of usage. Why would one us poll() over select()? Is select eventually going > >to go away for some reason? > > select() as a user-level call will never go away; there is a large base > of code that uses it. > > poll() is faster (it doesn't have to do bit twiddling), and it's interface > is cleaner (it can report invalid fd's, something select() can't do). As > its functionality is a superset of select()'s, it is used as the internal > implementation for select(). Actually, select() doesn't require horrendous amounts of copyin()s, which poll() does. So have you benchmarked the two? I'd expect select to be faster. > > As for new code, use whichever you are comfortable with. Personally, I > would recommend poll(), since it provides some added functionality over > select() that makes for easier programming. poll() is a huge pain to use, which is why I recommend select(). > > -- > Jonathan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Fri Jul 2 23:11:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.tig.com.au (stress.tig.com.au [203.109.250.50]) by hub.freebsd.org (Postfix) with ESMTP id 7DA4215294 for ; Fri, 2 Jul 1999 23:11:20 -0700 (PDT) (envelope-from reman@tig.com.au) Received: from tig.com.au (p3-nas1.syd.ihug.com.au [206.17.111.131]) by smtp1.tig.com.au (8.9.3/8.9.1) with ESMTP id QAA11683; Sat, 3 Jul 1999 16:11:07 +1000 Message-ID: <377DAB5F.459709D0@tig.com.au> Date: Sat, 03 Jul 1999 16:19:11 +1000 From: Chris X-Mailer: Mozilla 4.08 [en] (Win95; I) MIME-Version: 1.0 To: David Scheidt Cc: FreeBSD Hackers Subject: Re: Xfree86 v 3.3.4 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > > On Thu, 1 Jul 1999, Leif Neland wrote: > > > Does anyone have any inside information on subj? > > The website still claims: "We are planning to release 3.3.4 some time in > > June 1999" > > > > I'm longing to get support for my S3 Trio3D. > > Heh. It now says early july. I have a Voodoo Banshee I want to use. You can actually compile native Banshee support into XFree86, get glide.xxedgexx.com/changes.tar.gz (or go to http://glide.xxedgexx.com/3DfxRPMS_vb_glibc.html) then get a copy of the XFree86 sources, patch said XFree86 sources (this may take a little fiddling to get it all in the right places) then recompile and install and voila you have yourself a native Banshee server for X. Any probs you can email me (or the dude who wrote it) and I may be able to help you. regards, chris -- Christopher Day E-Mail reman@tig.com.au Homepage http://www.geocities.com/TimesSquare/Lair/1218 when the rain/when the children reign/keep your conscience in the dark melt the statues in the park - Fall On Me, REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0: 0:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.netlabs.net (www.netlabs.net [216.116.128.3]) by hub.freebsd.org (Postfix) with ESMTP id D5EE21532A for ; Sat, 3 Jul 1999 00:00:24 -0700 (PDT) (envelope-from keerf@www.netlabs.net) Received: (from keerf@localhost) by www.netlabs.net (8.9.2/8.9.0) id DAA24010 for freebsd-hackers@freebsd.org; Sat, 3 Jul 1999 03:00:32 -0400 (EDT) Date: Sat, 3 Jul 1999 03:00:32 -0400 (EDT) From: Terry Warner Message-Id: <199907030700.DAA24010@www.netlabs.net> To: freebsd-hackers@freebsd.org Subject: /usr/libexec/elf/ld Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi ,, I'm running FreeBSD 3.2-STABLE .. umm .. I'm having a little problem compiling some progams .. and this is the error that pops up /usr/libexec/elf/ld: cannot open -ljpeg: No such file or directory .. and I have libjpeg on my system I've tried updated the cache .. but still dosen't work .. I'm confused as all heck ... and need some help .. Thanks Terry Warner keerf@netlabs.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:19:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id EC4AF1507B for ; Sat, 3 Jul 1999 00:19:15 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id BAA06874; Sat, 3 Jul 1999 01:18:54 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377DB95C.448E4227@softweyr.com> Date: Sat, 03 Jul 1999 01:18:52 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: "G. Adam Stanislav" , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > > On Fri, 2 Jul 1999, G. Adam Stanislav wrote: > > > On Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > > > I know the basic admin knowledge of UNIX,perl,cgi,c > > > how to become a hacker? > > > > You either are a hacker, or you are not. It is not something someone else > > can teach you. > > This deserves a FAQ entry. What an awesome response. But it's certainly NOT something that you just are, either. You have to have talent, but you also have to have experience. This is most often done by a mentor. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 3 0:20:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 5046C1533D for ; Sat, 3 Jul 1999 00:19:58 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id BAA06881; Sat, 3 Jul 1999 01:19:42 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377DB98D.B8C15036@softweyr.com> Date: Sat, 03 Jul 1999 01:19:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dominic Mitchell , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: <7lg0r7$becd@eGroups.com> <19990702124829.A97003@palmerharvey.co.uk> <377CD8C1.2E7E0BFE@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Dominic Mitchell wrote: > > > > On Thu, Jul 01, 1999 at 08:17:59AM -0700, haodongpan@netease.com wrote: > > > I know the basic admin knowledge of UNIX,perl,cgi,c > > > how to become a hacker? > > > > Not everyone will agree with this, but you may want to look at: > > > > http://www.tuxedo.org/~esr/faqs/index.html > > Disagree? Eric even managed to mention the existence of freely available > BSD! I'm ecstatic! Actually, it's not a bad description of what most of > us have actually done. ;^) At my request, Eric added a link to www.bsd.org for more information about BSD systems. Now it's perfect. Almost. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 3 0:33:22 1999 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 5358B15290 for ; Sat, 3 Jul 1999 00:33:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09744; Sat, 3 Jul 1999 01:33:03 -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 BAA23514; Sat, 3 Jul 1999 01:30:38 -0600 (MDT) Message-Id: <199907030730.BAA23514@harmony.village.org> To: Graham Wheeler Subject: Re: Porting LILO to FreeBSD Cc: Vince Vielhaber , Graham Wheeler , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 15:27:04 +0200." <377CBE28.F3D4E15A@cdsec.com> References: <377CBE28.F3D4E15A@cdsec.com> Date: Sat, 03 Jul 1999 01:30:38 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <377CBE28.F3D4E15A@cdsec.com> Graham Wheeler writes: : The only reason I even want to do this is that I still have a number : of old DOS games that won't work under Win95. And dosemu and Wine : just don't cut it either, unfortunately. I have a friend that wants to boot FreeBSD on his IDE drive, or Win95 on his SCSI drive. No, it isn't an option to swap them, so the SCSI drive winds up being 'D'. The only way he can boot Win95 is to completely disable the IDE drive from the BIOS' point of view :-(. Would osbs solve this problem, or would he have to take a look at LILO? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:34: 4 1999 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 C1A251533F for ; Sat, 3 Jul 1999 00:34:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09748; Sat, 3 Jul 1999 01:33:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA23530; Sat, 3 Jul 1999 01:31:41 -0600 (MDT) Message-Id: <199907030731.BAA23530@harmony.village.org> To: Adrian Filipi-Martin Subject: Re: Porting LILO to FreeBSD Cc: Graham Wheeler , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 11:10:30 EDT." References: Date: Sat, 03 Jul 1999 01:31:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Adrian Filipi-Martin writes: : The standard boot partition selection softwre also works fine : booting windoze OS's from other disks. All you need to do is set the "disk : id" in the DOS MBR to the correct number, 0x81 for your second disk. That's : the only thing that MS doesn't do correctly whe installing the OS on the : non-primary disk. I used to do this a long time ago to boot FreeBSD of the : "C" drive and the other stuff off of "second C" drive. How does one do that? What tools do you use? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:43:39 1999 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 18B37152F3 for ; Sat, 3 Jul 1999 00:43:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09776; Sat, 3 Jul 1999 01:43:32 -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 BAA23629; Sat, 3 Jul 1999 01:41:15 -0600 (MDT) Message-Id: <199907030741.BAA23629@harmony.village.org> To: obrien@NUXI.com Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 17:43:37 PDT." <19990702174337.D3571@dragon.nuxi.com> References: <19990702174337.D3571@dragon.nuxi.com> <19990702171519.A3643@dragon.nuxi.com> <199907030015.RAA01965@dingo.cdrom.com> Date: Sat, 03 Jul 1999 01:41:15 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990702174337.D3571@dragon.nuxi.com> "David O'Brien" writes: : So that makes three of us that believe the check should be agaist "no" : rather than "yes". (setq check-against-no (+ check-against-no 1)) From my .cshrc: ... setenv FTP_PASSIVE_MODE ... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:44:47 1999 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 34947152F3; Sat, 3 Jul 1999 00:44:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09783; Sat, 3 Jul 1999 01:44:38 -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 BAA23649; Sat, 3 Jul 1999 01:42:21 -0600 (MDT) Message-Id: <199907030742.BAA23649@harmony.village.org> To: "Leif Neland" Subject: Re: Sv: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c Cc: obrien@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Jul 1999 02:54:59 +0200." <012801bec4ee$cfb29380$0e00a8c0@neland.dk> References: <012801bec4ee$cfb29380$0e00a8c0@neland.dk> <199907011133.EAA64244@freefall.freebsd.org> <19990701135124.I92508@bitbox.follo.net> <19990701154210.A12020@relay.ucb.crimea.ua> <19990701164430.O92508@bitbox.follo.net> <19990702171519.A3643@dragon.nuxi.com> Date: Sat, 03 Jul 1999 01:42:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <012801bec4ee$cfb29380$0e00a8c0@neland.dk> "Leif Neland" writes: : If there was someplace nice to put it: : ERROR! ^G^G^G^G^GFTP_PASSIVE_MODE must be either "yes" or "no" I disagree. This breaks the old behavior, while checking explicitly against no preserves all old behavior, except for those crazy people that set it to no expecting to turn it on (rather than off). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:45:44 1999 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 F0E77152F3 for ; Sat, 3 Jul 1999 00:45:41 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09793; Sat, 3 Jul 1999 01:45:40 -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 BAA23669; Sat, 3 Jul 1999 01:43:23 -0600 (MDT) Message-Id: <199907030743.BAA23669@harmony.village.org> To: "Brian F. Feldman" Subject: Re: Lizard... Cc: Anthony Kimball , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 22:39:49 EDT." References: Date: Sat, 03 Jul 1999 01:43:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Brian F. Feldman" writes: : It's a better idea to not have people waiting for a long time. CDROMs and Disks are only so fast... And network downloads are not going to be as snappy as even a 2x cdrom anytime soon... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 0:47:16 1999 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 9A8FB152F3 for ; Sat, 3 Jul 1999 00:47:13 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA09804; Sat, 3 Jul 1999 01:47:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA23702; Sat, 3 Jul 1999 01:44:55 -0600 (MDT) Message-Id: <199907030744.BAA23702@harmony.village.org> Subject: Re: UMAX scsi scanner on adaptec 1542 Card To: Greg Skafte , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 22:42:20 MDT." <199907030442.WAA00317@harmony.village.org> References: <199907030442.WAA00317@harmony.village.org> <19990702184559.E25510@gras-varg.worldgate.com> <19990701163631.A20163@gras-varg.worldgate.com> <199907020504.XAA41362@harmony.village.org> <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> <19990702183058.D25510@gras-varg.worldgate.com> <199907030034.SAA47172@harmony.village.org> Date: Sat, 03 Jul 1999 01:44:55 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199907030442.WAA00317@harmony.village.org> Warner Losh writes: : A hunch. I just tried to bring up my 1542CF with the bios disabled in : -current and it blew chunks like you described. Is your BIOS : disabled? If so, can you enable it and see if that works? It should : work with the bios disabled, but I know how painful that can be... That last bit should read: It should work with the BIOS disabled, because I know how painful having the BIOS enabled can be at boot time. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 2:52:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 9FA4C14D03; Sat, 3 Jul 1999 02:50:41 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id LAA54550; Sat, 3 Jul 1999 11:50:32 +0200 (CEST) (envelope-from des) To: hackers@freebsd.org Subject: bpfilter -> bpf patches [LONG] Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 03 Jul 1999 11:50:32 +0200 Message-ID: Lines: 3294 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Bcc:ed to net, committers; please follow up on hackers] Attached are patches for renaming 'pseudo-device bpfilter' to 'peudo-device bpf', courtesy of glimpse(1) and ed(1). LINT and GENERIC build fine with these patches; I haven't tried to run a kernel built with them, though. Also, although I caught and corrected a few spacing nits caused by chopping off five letters, there may be some I didn't catch. If no-one objects, I'll commit this to -CURRENT in a few days. DES -- Dag-Erling Smorgrav - des@yes.no Index: src/release/picobsd/router/conf/PICOBSD =================================================================== RCS file: /home/ncvs/src/release/picobsd/router/conf/PICOBSD,v retrieving revision 1.14 diff -u -r1.14 PICOBSD --- PICOBSD 1999/05/24 17:27:30 1.14 +++ PICOBSD 1999/07/02 08:10:05 @@ -94,7 +94,7 @@ pseudo-device ether #pseudo-device tun 2 #pseudo-device vn -#pseudo-device bpfilter 4 +#pseudo-device bpf 4 pseudo-device ppp 4 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's Index: src/release/scripts/dokern.sh =================================================================== RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.14 diff -u -r1.14 dokern.sh --- dokern.sh 1999/06/09 09:08:22 1.14 +++ dokern.sh 1999/07/02 08:10:05 @@ -12,7 +12,7 @@ -e 's/GENERIC/BOOTMFS/g' # So dhclient will work (just on boot floppy). -echo "pseudo-device bpfilter 4" +echo "pseudo-device bpf 4" echo "options NFS_NOSERVER" echo "options SCSI_NO_OP_STRINGS" Index: src/share/man/man4/bpf.4 =================================================================== RCS file: /home/ncvs/src/share/man/man4/bpf.4,v retrieving revision 1.16 diff -u -r1.16 bpf.4 --- bpf.4 1999/01/10 04:59:59 1.16 +++ bpf.4 1999/07/02 08:10:05 @@ -29,7 +29,7 @@ .Nm bpf .Nd Berkeley Packet Filter .Sh SYNOPSIS -.Cd pseudo-device bpfilter +.Cd pseudo-device bpf .Sh DESCRIPTION The Berkeley Packet Filter provides a raw interface to data link layers in a protocol Index: src/sys/alpha/tc/am7990.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/tc/am7990.c,v retrieving revision 1.3 diff -u -r1.3 am7990.c --- am7990.c 1999/05/10 15:48:01 1.3 +++ am7990.c 1999/07/02 08:08:50 @@ -78,7 +78,7 @@ */ #include "opt_inet.h" -#if NBPFILTER > 0 +#if NBPF > 0 #include #include #endif @@ -229,7 +229,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&ifp->if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -318,7 +318,7 @@ struct letmd tmd; u_int8_t *myaddr; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_flags & IFF_PROMISC) init.init_mode = LE_MODE_NORMAL | LE_MODE_PROM; else @@ -565,7 +565,7 @@ /* We assume that the header fit entirely in one mbuf. */ eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. * If so, hand off the raw packet to BPF. @@ -923,7 +923,7 @@ if (m == 0) break; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If BPF is listening on this interface, let it see the packet * before we commit it to the wire. Index: src/sys/alpha/tc/if_le_dec.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/tc/if_le_dec.c,v retrieving revision 1.1 diff -u -r1.1 if_le_dec.c --- if_le_dec.c 1998/08/20 08:27:10 1.1 +++ if_le_dec.c 1999/07/02 08:09:11 @@ -41,7 +41,7 @@ * @(#)if_le.c 8.2 (Berkeley) 11/16/93 */ -#include "bpfilter.h" +#include "bpf.h" #include #include #include Index: src/sys/conf/files =================================================================== RCS file: /home/ncvs/src/sys/conf/files,v retrieving revision 1.223 diff -u -r1.223 files --- files 1999/06/24 03:44:10 1.223 +++ files 1999/07/02 08:09:11 @@ -391,7 +391,7 @@ ntfs/ntfs_compr.c optional ntfs ntfs/ntfs_ihash.c optional ntfs net/bpf.c standard -net/bpf_filter.c optional bpfilter +net/bpf_filter.c optional bpf net/bridge.c optional bridge net/bsd_comp.c optional ppp_bsdcomp #net/hostcache.c standard Index: src/sys/contrib/dev/oltr/if_oltr.c =================================================================== RCS file: /home/ncvs/src/sys/contrib/dev/oltr/if_oltr.c,v retrieving revision 1.5 diff -u -r1.5 if_oltr.c --- if_oltr.c 1999/05/09 17:07:24 1.5 +++ if_oltr.c 1999/07/02 08:09:11 @@ -37,7 +37,7 @@ #include "pci.h" #include "oltr.h" #include "opt_inet.h" -#include "bpfilter.h" +#include "bpf.h" #if (NOLTR + NPCI) > 0 @@ -90,7 +90,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -632,7 +632,7 @@ if_attach(ifp); iso88025_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_IEEE802, sizeof(struct iso88025_header)); #endif @@ -949,7 +949,7 @@ goto bad; } -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m0); #endif @@ -1351,7 +1351,7 @@ } ifp->if_ipackets++; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m0); #endif Index: src/sys/dev/en/midway.c =================================================================== RCS file: /home/ncvs/src/sys/dev/en/midway.c,v retrieving revision 1.16 diff -u -r1.16 midway.c --- midway.c 1999/05/08 14:23:00 1.16 +++ midway.c 1999/07/02 08:09:11 @@ -169,8 +169,8 @@ #endif /* __FreeBSD__ */ -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #ifdef __FreeBSD__ #define BPFATTACH(ifp, dlt, hlen) bpfattach((ifp), (dlt), (hlen)) @@ -179,7 +179,7 @@ #define BPFATTACH(ifp, dlt, hlen) bpfattach(&(ifp)->if_bpf, (ifp), (dlt), (hlen)) #define BPF_MTAP(ifp, m) bpf_mtap((ifp)->if_bpf, (m)) #endif -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ /* * params @@ -820,7 +820,7 @@ if_attach(ifp); atm_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 BPFATTACH(ifp, DLT_ATM_RFC1483, sizeof(struct atmllc)); #endif } @@ -2120,7 +2120,7 @@ en_txlaunch(sc, chan, &launch); -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { /* * adjust the top of the mbuf to skip the pseudo atm header @@ -2139,7 +2139,7 @@ launch.t->m_data -= size; launch.t->m_len += size; } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ /* * do some housekeeping and get the next packet */ @@ -2709,7 +2709,7 @@ ifp = &sc->enif; ifp->if_ipackets++; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) BPF_MTAP(ifp, m); #endif Index: src/sys/dev/iicbus/if_ic.c =================================================================== RCS file: /home/ncvs/src/sys/dev/iicbus/if_ic.c,v retrieving revision 1.4 diff -u -r1.4 if_ic.c --- if_ic.c 1999/05/08 21:59:03 1.4 +++ if_ic.c 1999/07/02 08:09:11 @@ -59,9 +59,9 @@ #include #include -#include "bpfilter.h" +#include "bpf.h" -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -151,7 +151,7 @@ if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, ICHDRLEN); #endif @@ -322,7 +322,7 @@ sc->ic_if.if_ipackets ++; sc->ic_if.if_ibytes += len; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->ic_if.if_bpf) bpf_tap(&sc->ic_if, sc->ic_ifbuf, len + ICHDRLEN); #endif @@ -417,7 +417,7 @@ } while ((mm = mm->m_next)); -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { struct mbuf m0, *n = m; Index: src/sys/dev/pccard/if_xe.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pccard/if_xe.c,v retrieving revision 1.5 diff -u -r1.5 if_xe.c --- if_xe.c 1999/06/22 19:21:00 1.5 +++ if_xe.c 1999/07/02 08:09:11 @@ -106,7 +106,7 @@ #include "xe.h" #include "card.h" #include "apm.h" -#include "bpfilter.h" +#include "bpf.h" #if NXE > 0 @@ -131,9 +131,9 @@ #include #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ #include #include @@ -808,7 +808,7 @@ if_attach(scp->ifp); ether_ifattach(scp->ifp); -#if NBPFILTER > 0 +#if NBPF > 0 /* If BPF is in the kernel, call the attach for it */ #if XE_DEBUG > 1 printf("xe%d: BPF listener attached\n", scp->unit); @@ -944,7 +944,7 @@ return; } -#if NBPFILTER > 0 +#if NBPF > 0 /* Tap off here if there is a bpf listener */ if (ifp->if_bpf) { #if XE_DEBUG > 1 @@ -952,7 +952,7 @@ #endif bpf_mtap(ifp, mbp); } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ ifp->if_timer = 5; /* In case we don't hear from the card again */ scp->tx_queued++; @@ -1266,7 +1266,7 @@ else insw(scp->dev->id_iobase+XE_EDP, ehp, len >> 1); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. If so, hand * off the raw packet to bpf. @@ -1289,7 +1289,7 @@ mbp = NULL; } } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ if (mbp != NULL) { mbp->m_pkthdr.len = mbp->m_len = len - ETHER_HDR_LEN; Index: src/sys/dev/pdq/pdq_ifsubr.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pdq/pdq_ifsubr.c,v retrieving revision 1.7 diff -u -r1.7 pdq_ifsubr.c --- pdq_ifsubr.c 1998/02/20 13:11:45 1.7 +++ pdq_ifsubr.c 1999/07/02 08:09:11 @@ -45,8 +45,8 @@ #include #include -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif @@ -186,7 +186,7 @@ struct fddi_header *fh = mtod(m, struct fddi_header *); sc->sc_if.if_ipackets++; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_bpf != NULL) PDQ_BPF_MTAP(sc, m); if ((fh->fddi_fc & (FDDIFC_L|FDDIFC_F)) != FDDIFC_LLC_ASYNC) { @@ -222,7 +222,7 @@ struct mbuf *m) { pdq_softc_t *sc = (pdq_softc_t *) pdq->pdq_os_ctx; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_bpf != NULL) PDQ_BPF_MTAP(sc, m); #endif @@ -384,7 +384,7 @@ if_attach(ifp); fddi_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 PDQ_BPFATTACH(sc, DLT_FDDI, sizeof(struct fddi_header)); #endif } Index: src/sys/dev/ppbus/if_plip.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ppbus/if_plip.c,v retrieving revision 1.12 diff -u -r1.12 if_plip.c --- if_plip.c 1999/02/14 16:19:16 1.12 +++ if_plip.c 1999/07/02 08:09:11 @@ -93,8 +93,8 @@ #include #include -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif @@ -256,7 +256,7 @@ ifp->if_snd.ifq_maxlen = IFQ_MAXLEN; if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, sizeof(u_int32_t)); #endif @@ -446,7 +446,7 @@ return (ctrecvl[cl] | ctrecvh[c]); } -#if NBPFILTER > 0 +#if NBPF > 0 static void lptap(struct ifnet *ifp, struct mbuf *m) { @@ -525,7 +525,7 @@ sc->sc_if.if_ibytes += len; top = m_devget(sc->sc_ifbuf + CLPIPHDRLEN, len, 0, &sc->sc_if, 0); if (top) { -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) lptap(&sc->sc_if, top); #endif @@ -578,7 +578,7 @@ sc->sc_if.if_ibytes += len; top = m_devget(sc->sc_ifbuf + LPIPHDRLEN, len, 0, &sc->sc_if, 0); if (top) { -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) lptap(&sc->sc_if, top); #endif @@ -715,7 +715,7 @@ } else { ifp->if_opackets++; ifp->if_obytes += m->m_pkthdr.len; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) lptap(ifp, m); #endif @@ -762,7 +762,7 @@ } else { ifp->if_opackets++; ifp->if_obytes += m->m_pkthdr.len; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) lptap(ifp, m); #endif Index: src/sys/dev/vx/if_vx.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vx/if_vx.c,v retrieving revision 1.20 diff -u -r1.20 if_vx.c --- if_vx.c 1999/01/27 20:09:20 1.20 +++ if_vx.c 1999/07/02 08:09:11 @@ -62,7 +62,7 @@ #define NVX 4 #endif -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -76,7 +76,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -216,7 +216,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -496,7 +496,7 @@ outw(BASE + VX_COMMAND, SET_TX_START_THRESH | ((len / 4 + sc->tx_start_thresh) >> 2)); -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) { bpf_mtap(&sc->arpcom.ac_if, m0); } @@ -745,7 +745,7 @@ /* We assume the header fit entirely in one mbuf. */ eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. * If so, hand off the raw packet to BPF. Index: src/sys/i386/conf/GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v retrieving revision 1.175 diff -u -r1.175 GENERIC --- GENERIC 1999/06/29 18:55:53 1.175 +++ GENERIC 1999/07/03 09:40:42 @@ -197,9 +197,9 @@ pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. +# The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the legal and administrative consequences of enabling this! -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface Index: src/sys/i386/conf/LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.613 diff -u -r1.613 LINT --- LINT 1999/06/29 21:52:07 1.613 +++ LINT 1999/07/03 09:40:35 @@ -381,7 +381,7 @@ # of synchronous PPP links (like `cx', `ar'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. @@ -394,7 +394,7 @@ # The PPP_BSDCOMP option enables support for compress(1) style entire # packet compression, the PPP_DEFLATE is for zlib/gzip style compression. # PPP_FILTER enables code for filtering the ppp data stream and selecting -# events for resetting the demand dial activity timer - requires bpfilter. +# events for resetting the demand dial activity timer - requires bpf. # See pppd(8) for more details. # pseudo-device ether #Generic Ethernet @@ -402,7 +402,7 @@ pseudo-device fddi #Generic FDDI pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device -pseudo-device bpfilter 4 #Berkeley packet filter +pseudo-device bpf 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (ppp(8), nos-tun(8)) pseudo-device sl 2 #Serial Line IP @@ -410,7 +410,7 @@ pseudo-device streams options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support -options PPP_FILTER #enable bpf filtering (needs bpfilter) +options PPP_FILTER #enable bpf filtering (needs bpf) # # Internet family options: Index: src/sys/i386/conf/PCCARD =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/PCCARD,v retrieving revision 1.11 diff -u -r1.11 PCCARD --- PCCARD 1999/06/17 23:53:20 1.11 +++ PCCARD 1999/07/02 08:09:11 @@ -201,11 +201,11 @@ options SYSVMSG options SYSVSEM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter # USB support #controller uhci0 Index: src/sys/i386/isa/if_ar.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ar.c,v retrieving revision 1.26 diff -u -r1.26 if_ar.c --- if_ar.c 1999/05/06 18:58:04 1.26 +++ if_ar.c 1999/07/02 08:09:11 @@ -49,7 +49,7 @@ */ #include "ar.h" -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -61,7 +61,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -357,7 +357,7 @@ sppp_attach((struct ifnet *)&sc->ifsppp); if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_PPP, PPP_HEADER_LEN); #endif } @@ -537,7 +537,7 @@ txdata += AR_BUF_SIZ; i++; -#if NBPFILTER > 0 +#if NBPF > 0 if(ifp->if_bpf) bpf_mtap(ifp, mtx); #endif @@ -1299,7 +1299,7 @@ } } ar_copy_rxbuf(m, sc, len); -#if NBPFILTER > 0 +#if NBPF > 0 if(sc->ifsppp.pp_if.if_bpf) bpf_mtap(&sc->ifsppp.pp_if, m); #endif Index: src/sys/i386/isa/if_cs.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_cs.c,v retrieving revision 1.10 diff -u -r1.10 if_cs.c --- if_cs.c 1999/04/16 21:22:20 1.10 +++ if_cs.c 1999/07/02 08:09:12 @@ -35,7 +35,7 @@ /* #define CS_DEBUG */ #include "cs.h" -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -52,7 +52,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -620,7 +620,7 @@ printf(CS_NAME"%d: ethernet address %6D\n", ifp->if_unit, sc->arpcom.ac_enaddr, ":"); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof (struct ether_header)); #endif return 1; @@ -777,7 +777,7 @@ eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m); #endif @@ -950,7 +950,7 @@ cs_write_mbufs(sc, m); -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, m); } Index: src/sys/i386/isa/if_cx.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_cx.c,v retrieving revision 1.28 diff -u -r1.28 if_cx.c --- if_cx.c 1999/04/02 13:58:01 1.28 +++ if_cx.c 1999/07/02 08:09:12 @@ -19,7 +19,7 @@ #undef DEBUG #include "cx.h" -#include "bpfilter.h" +#include "bpf.h" #include "opt_devfs.h" #include "sppp.h" @@ -38,7 +38,7 @@ #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -285,7 +285,7 @@ sppp_attach (c->ifp); if_attach (c->ifp); sp = (struct sppp*) c->ifp; -#if NBPFILTER > 0 +#if NBPF > 0 /* If BPF is in the kernel, call the attach for it. */ bpfattach (c->ifp, DLT_PPP, PPP_HEADER_LEN); #endif @@ -481,7 +481,7 @@ return; } m_copydata (m, 0, len, buf); -#if NBPFILTER > 0 +#if NBPF > 0 if (c->ifp->if_bpf) bpf_mtap (c->ifp, m); #endif @@ -805,7 +805,7 @@ printmbuf (m); #endif -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. * If so, hand off the raw packet to bpf. Index: src/sys/i386/isa/if_ed.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ed.c,v retrieving revision 1.152 diff -u -r1.152 if_ed.c --- if_ed.c 1999/05/09 23:24:45 1.152 +++ if_ed.c 1999/07/02 08:09:12 @@ -38,7 +38,7 @@ */ #include "ed.h" -#include "bpfilter.h" +#include "bpf.h" #include "pnp.h" #ifndef EXTRA_ED @@ -65,7 +65,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif #include "opt_bdg.h" @@ -1721,7 +1721,7 @@ /* * If BPF is in the kernel, call the attach for it */ -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif return 1; @@ -2179,7 +2179,7 @@ /* * Tap off here if there is a bpf listener. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, m0); } @@ -2621,7 +2621,7 @@ } } -#if NBPFILTER > 0 +#if NBPF > 0 /* * Promiscuous flag may have changed, so reprogram the RCR. @@ -2752,7 +2752,7 @@ struct ifnet *ifp ; int need_more = 1 ; /* in case not bpf */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) { need_more = 0 ; ed_ring_copy(sc, buf, (char *)eh, len); @@ -2783,7 +2783,7 @@ */ ed_ring_copy(sc, buf, (char *)eh, len); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. If so, hand off Index: src/sys/i386/isa/if_el.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_el.c,v retrieving revision 1.40 diff -u -r1.40 if_el.c --- if_el.c 1999/01/12 01:29:42 1.40 +++ if_el.c 1999/07/02 08:09:12 @@ -20,7 +20,7 @@ * - Does not currently support multicasts */ #include "el.h" -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -48,7 +48,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -213,7 +213,7 @@ sc->arpcom.ac_enaddr, ":"); /* Finally, attach to bpf filter if it is present. */ -#if NBPFILTER > 0 +#if NBPF > 0 dprintf(("Attaching to BPF...\n")); bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -348,7 +348,7 @@ len = max(len,ETHER_MIN_LEN); /* Give the packet to the bpf, if any */ -#if NBPFILTER > 0 +#if NBPF > 0 if(sc->arpcom.ac_if.if_bpf) bpf_tap(&sc->arpcom.ac_if, sc->el_pktbuf, len); #endif @@ -438,7 +438,7 @@ eh = (struct ether_header *)buf; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a bpf filter listening on this interface. * If so, hand off the raw packet to bpf. Index: src/sys/i386/isa/if_ep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ep.c,v retrieving revision 1.79 diff -u -r1.79 if_ep.c --- if_ep.c 1999/01/31 22:41:51 1.79 +++ if_ep.c 1999/07/02 08:09:12 @@ -59,7 +59,7 @@ #include "ep.h" #if NEP > 0 -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -93,7 +93,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -635,7 +635,7 @@ ep_fset(F_RX_FIRST); sc->top = sc->mcur = 0; -#if NBPFILTER > 0 +#if NBPF > 0 if (!attached) { bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); } @@ -871,7 +871,7 @@ while (pad--) outb(BASE + EP_W1_TX_PIO_WR_1, 0); /* Padding */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, top); } @@ -1137,7 +1137,7 @@ top->m_pkthdr.rcvif = &sc->arpcom.ac_if; top->m_pkthdr.len = sc->cur_len; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, top); Index: src/sys/i386/isa/if_ex.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ex.c,v retrieving revision 1.15 diff -u -r1.15 if_ex.c --- if_ex.c 1999/05/02 22:01:24 1.15 +++ if_ex.c 1999/07/02 08:09:12 @@ -37,7 +37,7 @@ #include "ex.h" #if NEX > 0 -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -65,7 +65,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -294,7 +294,7 @@ /* * If BPF is in the kernel, call the attach for it */ -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif DODEBUG(Start_End, printf("ex_attach%d: finish\n", unit);); @@ -520,7 +520,7 @@ sc->tx_last = dest; sc->tx_tail = next; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf != NULL) bpf_mtap(ifp, opkt); #endif @@ -727,7 +727,7 @@ } /* QQQ */ } #endif -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf != NULL) { bpf_mtap(ifp, ipkt); Index: src/sys/i386/isa/if_fe.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_fe.c,v retrieving revision 1.50 diff -u -r1.50 if_fe.c --- if_fe.c 1999/05/04 12:59:59 1.50 +++ if_fe.c 1999/07/02 08:09:12 @@ -70,7 +70,7 @@ */ #include "fe.h" -#include "bpfilter.h" +#include "bpf.h" #include "opt_fe.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -110,7 +110,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -2763,7 +2763,7 @@ sc->sc_unit); } -#if NBPFILTER > 0 +#if NBPF > 0 /* If BPF is in the kernel, call the attach for it. */ bpfattach(&sc->sc_if, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -3132,7 +3132,7 @@ * and only if it is in "receive everything" * mode.) */ -#if NBPFILTER > 0 +#if NBPF > 0 if ( sc->sc_if.if_bpf && !( sc->sc_if.if_flags & IFF_PROMISC ) ) { bpf_mtap( &sc->sc_if, m ); @@ -3764,7 +3764,7 @@ #define ETHER_ADDR_IS_MULTICAST(A) (*(char *)(A) & 1) -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. * If it is, hand off the raw packet to bpf. Index: src/sys/i386/isa/if_ie.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ie.c,v retrieving revision 1.60 diff -u -r1.60 if_ie.c --- if_ie.c 1999/05/13 12:21:41 1.60 +++ if_ie.c 1999/07/02 08:09:12 @@ -125,7 +125,7 @@ #include #include -#include "bpfilter.h" +#include "bpf.h" #ifdef INET #include @@ -153,7 +153,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -842,7 +842,7 @@ if (ie->hard_type == IE_EE16) at_shutdown(ee16_shutdown, ie, SHUTDOWN_POST_SYNC); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -1101,7 +1101,7 @@ * Receiving all multicasts, but no unicasts except those * destined for us. */ -#if NBPFILTER > 0 +#if NBPF > 0 /* BPF gets this packet if anybody cares */ *to_bpf = (ie->arpcom.ac_if.if_bpf != 0); #endif @@ -1117,14 +1117,14 @@ * Receiving all packets. These need to be passed on to * BPF. */ -#if NBPFILTER > 0 +#if NBPF > 0 *to_bpf = (ie->arpcom.ac_if.if_bpf != 0); #endif /* If for us, accept and hand up to BPF */ if (ether_equal(eh->ether_dhost, ie->arpcom.ac_enaddr)) return (1); -#if NBPFILTER > 0 +#if NBPF > 0 if (*to_bpf) *to_bpf = 2; /* we don't need to see it */ #endif @@ -1142,7 +1142,7 @@ for (i = 0; i < ie->mcast_count; i++) { if (ether_equal(eh->ether_dhost, (u_char *)&ie->mcast_addrs[i])) { -#if NBPFILTER > 0 +#if NBPF > 0 if (*to_bpf) *to_bpf = 1; #endif @@ -1156,7 +1156,7 @@ * Acting as a multicast router, and BPF running at the same * time. Whew! (Hope this is a fast machine...) */ -#if NBPFILTER > 0 +#if NBPF > 0 *to_bpf = (ie->arpcom.ac_if.if_bpf != 0); #endif /* We want to see multicasts. */ @@ -1168,7 +1168,7 @@ return (1); /* Anything else goes to BPF but nothing else. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (*to_bpf) *to_bpf = 2; #endif @@ -1183,7 +1183,7 @@ * for the multicast filter), but it will do in this case, * and we want to get out of here as quickly as possible. */ -#if NBPFILTER > 0 +#if NBPF > 0 *to_bpf = (ie->arpcom.ac_if.if_bpf != 0); #endif return (1); @@ -1420,7 +1420,7 @@ struct mbuf *m = 0; struct ether_header eh; -#if NBPFILTER > 0 +#if NBPF > 0 int bpf_gets_it = 0; #endif @@ -1439,7 +1439,7 @@ ie->rfhead = (ie->rfhead + 1) % ie->nframes; if (rfd.ie_fd_status & IE_FD_OK) { -#if NBPFILTER > 0 +#if NBPF > 0 if (ieget(unit, ie, &m, &eh, &bpf_gets_it)) { #else if (ieget(unit, ie, &m, &eh, (int *)0)) { @@ -1466,7 +1466,7 @@ m_freem(last_not_for_us); last_not_for_us = 0; } -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check for a BPF filter; if so, hand it up. Note that we have to * stick an extra mbuf up front, because bpf_mtap expects to have @@ -1494,7 +1494,7 @@ last_not_for_us = m; return; } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ /* * In here there used to be code to check destination addresses upon * receipt of a packet. We have deleted that code, and replaced it @@ -1578,7 +1578,7 @@ m_freem(m0); len = max(len, ETHER_MIN_LEN); -#if NBPFILTER > 0 +#if NBPF > 0 /* * See if bpf is listening on this interface, let it see the * packet before we commit it to the wire. Index: src/sys/i386/isa/if_le.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_le.c,v retrieving revision 1.50 diff -u -r1.50 if_le.c --- if_le.c 1999/05/11 19:54:12 1.50 +++ if_le.c 1999/07/02 08:09:12 @@ -52,7 +52,7 @@ #include #include -#include "bpfilter.h" +#include "bpf.h" #ifdef INET #include @@ -77,7 +77,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -370,7 +370,7 @@ ifp->if_addrlen = 6; ifp->if_hdrlen = 14; -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -412,7 +412,7 @@ } MEMCPY(&eh, seg1, sizeof(eh)); -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->le_if.if_bpf != NULL && seg2 == NULL) { bpf_tap(&sc->le_if, seg1, total_len); /* @@ -469,7 +469,7 @@ MEMCPY(mtod(m, caddr_t), seg1, len1); if (seg2 != NULL) MEMCPY(mtod(m, caddr_t) + len1, seg2, total_len - len1); -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->le_if.if_bpf != NULL && seg2 != NULL) { bpf_mtap(&sc->le_if, m); /* @@ -1142,7 +1142,7 @@ LE_OUTB(sc, LEMAC_REG_TQ, tx_pg); /* tell chip to transmit this packet */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->le_if.if_bpf) bpf_mtap(&sc->le_if, m); #endif Index: src/sys/i386/isa/if_lnc.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_lnc.c,v retrieving revision 1.60 diff -u -r1.60 if_lnc.c --- if_lnc.c 1999/05/09 23:24:47 1.60 +++ if_lnc.c 1999/07/02 08:09:12 @@ -64,7 +64,7 @@ #include "lnc.h" #if NLNC > 0 -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" /* Some defines that should really be in generic locations */ @@ -88,7 +88,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -613,7 +613,7 @@ eh = (struct ether_header *) head->m_data; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) bpf_mtap(&sc->arpcom.ac_if, head); #endif @@ -1295,7 +1295,7 @@ printf("%s", ic_ident[sc->nic.ic]); printf(" address %6D\n", sc->arpcom.ac_enaddr, ":"); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&sc->arpcom.ac_if, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -1809,7 +1809,7 @@ ifp->if_timer = 2; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) bpf_mtap(&sc->arpcom.ac_if, head); #endif Index: src/sys/i386/isa/if_lnc.h =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_lnc.h,v retrieving revision 1.10 diff -u -r1.10 if_lnc.h --- if_lnc.h 1999/01/31 00:56:32 1.10 +++ if_lnc.h 1999/07/02 08:08:52 @@ -39,7 +39,7 @@ * Initialize multicast address hashing registers to accept * all multicasts (only used when in promiscuous mode) */ -#if NBPFILTER > 0 +#if NBPF > 0 #define MULTI_INIT_ADDR 0xff #else #define MULTI_INIT_ADDR 0 Index: src/sys/i386/isa/if_rdp.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_rdp.c,v retrieving revision 1.3 diff -u -r1.3 if_rdp.c --- if_rdp.c 1999/01/12 00:36:31 1.3 +++ if_rdp.c 1999/07/02 08:09:12 @@ -62,7 +62,7 @@ */ #include "rdp.h" -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -89,7 +89,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -629,7 +629,7 @@ /* * If BPF is in the kernel, call the attach for it */ -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif return 1; @@ -814,7 +814,7 @@ /* * Tap off here if there is a bpf listener. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, m); } @@ -862,7 +862,7 @@ } } -#if NBPFILTER > 0 +#if NBPF > 0 /* * Promiscuous flag may have changed, propagage this * to the NIC. @@ -1164,7 +1164,7 @@ outb(sc->baseaddr + lpt_control, Ctrl_SelData); WrNib(sc, CMR1, CMR1_RDPAC); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. If so, hand off Index: src/sys/i386/isa/if_sr.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_sr.c,v retrieving revision 1.23 diff -u -r1.23 if_sr.c --- if_sr.c 1999/05/06 22:14:46 1.23 +++ if_sr.c 1999/07/02 08:09:13 @@ -53,7 +53,7 @@ #else #define NFR 0 #endif -#include "bpfilter.h" +#include "bpf.h" #include "sppp.h" #if NSPPP <= 0 @@ -71,7 +71,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -848,7 +848,7 @@ if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_PPP, PPP_HEADER_LEN); #endif } @@ -1119,7 +1119,7 @@ sc->unit, mtx, len); #endif -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, mtx); #endif @@ -2462,7 +2462,7 @@ */ sr_copy_rxbuf(m, sc, len); /* copy from DPRAM */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m); #endif Index: src/sys/i386/isa/if_wi.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_wi.c,v retrieving revision 1.6 diff -u -r1.6 if_wi.c --- if_wi.c 1999/06/06 16:44:04 1.6 +++ if_wi.c 1999/07/02 08:09:13 @@ -67,7 +67,7 @@ #define WI_HERMES_AUTOINC_WAR /* Work around data write autoinc bug. */ #define WI_HERMES_STATS_WAR /* Work around stats counter bug. */ -#include "bpfilter.h" +#include "bpf.h" #include "card.h" #include "wi.h" @@ -94,7 +94,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -363,7 +363,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -446,7 +446,7 @@ ifp->if_ipackets++; -#if NBPFILTER > 0 +#if NBPF > 0 /* Handle BPF listeners. */ if (ifp->if_bpf) { bpf_mtap(ifp, m); @@ -1222,7 +1222,7 @@ m0->m_pkthdr.len + 2); } -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listner, bounce a copy of * this frame to him. Index: src/sys/i386/isa/if_wl.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_wl.c,v retrieving revision 1.21 diff -u -r1.21 if_wl.c --- if_wl.c 1999/04/27 11:15:02 1.21 +++ if_wl.c 1999/07/02 08:09:13 @@ -190,7 +190,7 @@ #include "wl.h" #include "opt_wavelan.h" -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include @@ -214,7 +214,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -510,7 +510,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -895,7 +895,7 @@ ifp = &(sc->wl_if); IF_DEQUEUE(&ifp->if_snd, m); if (m != (struct mbuf *)0) { -#if NBPFILTER > 0 +#if NBPF > 0 /* let BPF see it before we commit it */ if (ifp->if_bpf) { bpf_mtap(ifp, m); @@ -1080,7 +1080,7 @@ m->m_pkthdr.len = clen; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. If so, hand off * the raw packet to bpf. Index: src/sys/i386/isa/if_ze.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ze.c,v retrieving revision 1.58 diff -u -r1.58 if_ze.c --- if_ze.c 1999/05/06 18:43:58 1.58 +++ if_ze.c 1999/07/02 08:09:13 @@ -64,7 +64,7 @@ #include "ze.h" #if NZE > 0 -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -92,7 +92,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -650,7 +650,7 @@ /* * If BPF is in the kernel, call the attach for it */ -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -871,7 +871,7 @@ for (i = 0; i < ETHER_ADDR_LEN; ++i) outb(sc->nic_addr + ED_P1_PAR0 + i, sc->arpcom.ac_enaddr[i]); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Initialize multicast address hashing registers to accept * all multicasts (only used when in promiscuous mode) @@ -1042,7 +1042,7 @@ /* * If there is BPF support in the configuration, tap off here. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, m0); } @@ -1434,7 +1434,7 @@ ((ifp->if_flags & IFF_RUNNING) == 0)) ze_init(ifp->if_unit); } -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_flags & IFF_PROMISC) { /* * Set promiscuous mode on interface. @@ -1518,7 +1518,7 @@ m = ze_ring_to_mbuf(sc, buf, m, len); if (m == NULL) goto bad; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. * If so, hand off the raw packet to bpf. Index: src/sys/i386/isa/if_zp.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_zp.c,v retrieving revision 1.51 diff -u -r1.51 if_zp.c --- if_zp.c 1999/04/19 06:56:24 1.51 +++ if_zp.c 1999/07/02 08:09:13 @@ -114,7 +114,7 @@ #include "zp.h" -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #include "opt_ipx.h" @@ -145,7 +145,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -568,7 +568,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif #if NAPM > 0 @@ -761,7 +761,7 @@ while (pad--) outb(BASE + EP_W1_TX_PIO_WR_1, 0); /* Padding */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) { bpf_mtap(&sc->arpcom.ac_if, top); } @@ -975,7 +975,7 @@ outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); ++sc->arpcom.ac_if.if_ipackets; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) { bpf_mtap(&sc->arpcom.ac_if, top); Index: src/sys/i4b/driver/i4b_ipr.c =================================================================== RCS file: /home/ncvs/src/sys/i4b/driver/i4b_ipr.c,v retrieving revision 1.4 diff -u -r1.4 i4b_ipr.c --- i4b_ipr.c 1999/05/20 10:08:58 1.4 +++ i4b_ipr.c 1999/07/02 08:09:13 @@ -110,8 +110,8 @@ /* undef to uncompress in the mbuf itself */ #endif /* IPR_VJ */ -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #include #endif @@ -350,7 +350,7 @@ if_attach(&sc->sc_if); -#if NBPFILTER > 0 +#if NBPF > 0 #ifdef __FreeBSD__ bpfattach(&sc->sc_if, DLT_NULL, sizeof(u_int)); #else @@ -994,7 +994,7 @@ sc->sc_inb += m->m_pkthdr.len; #endif -#if NBPFILTER > 0 +#if NBPF > 0 if(sc->sc_if.if_bpf) { /* prepend the address family as a four byte field */ @@ -1010,7 +1010,7 @@ bpf_mtap(sc->sc_if.if_bpf, &mm); #endif } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ if(IF_QFULL(&ipintrq)) { @@ -1062,7 +1062,7 @@ microtime(&sc->sc_if.if_lastchange); -#if NBPFILTER > 0 +#if NBPF > 0 if(sc->sc_if.if_bpf) { /* prepend the address family as a four byte field */ @@ -1079,7 +1079,7 @@ bpf_mtap(sc->sc_if.if_bpf, &mm); #endif } -#endif /* NBPFILTER */ +#endif /* NBPF */ #if I4BIPRACCT sc->sc_outb += m->m_pkthdr.len; /* size before compression */ Index: src/sys/i4b/driver/i4b_isppp.c =================================================================== RCS file: /home/ncvs/src/sys/i4b/driver/i4b_isppp.c,v retrieving revision 1.3 diff -u -r1.3 i4b_isppp.c --- i4b_isppp.c 1999/05/20 10:09:01 1.3 +++ i4b_isppp.c 1999/07/02 08:09:13 @@ -74,8 +74,8 @@ #include #include -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #include #endif @@ -290,7 +290,7 @@ sppp_attach(&sc->sc_if); if_attach(&sc->sc_if); -#if NBPFILTER > 0 +#if NBPF > 0 #ifdef __FreeBSD__ bpfattach(&sc->sc_if, DLT_PPP, PPP_HDRLEN); CALLOUT_INIT(&sc->sc_ch); @@ -361,7 +361,7 @@ while ((m = sppp_dequeue(&sc->sc_if)) != NULL) { -#if NBPFILTER > 0 +#if NBPF > 0 #ifdef __FreeBSD__ if (ifp->if_bpf) bpf_mtap(ifp, m); @@ -371,7 +371,7 @@ if (ifp->if_bpf) bpf_mtap(ifp->if_bpf, m); #endif -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ microtime(&ifp->if_lastchange); @@ -654,7 +654,7 @@ printf("i4bisppp_rx_data_ready: received packet!\n"); #endif -#if NBPFILTER > 0 +#if NBPF > 0 #ifdef __FreeBSD__ if(sc->sc_if.if_bpf) @@ -666,7 +666,7 @@ bpf_mtap(sc->sc_if.if_bpf, m); #endif -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ s = splimp(); Index: src/sys/modules/fxp/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/fxp/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- Makefile 1999/04/18 13:31:23 1.2 +++ Makefile 1999/07/02 08:09:13 @@ -3,15 +3,15 @@ S = ${.CURDIR}/../.. .PATH: $S/pci KMOD = fxp -SRCS = if_fxp.c fxp.h bpfilter.h opt_bdg.h device_if.h bus_if.h pci_if.h -CLEANFILES += fxp.h bpfilter.h opt_bdg.h device_if.h bus_if.h pci_if.h +SRCS = if_fxp.c fxp.h bpf.h opt_bdg.h device_if.h bus_if.h pci_if.h +CLEANFILES += fxp.h bpf.h opt_bdg.h device_if.h bus_if.h pci_if.h CFLAGS += ${DEBUG_FLAGS} fxp.h: echo "#define NFXP 1" > fxp.h -bpfilter.h: - echo "#define NBPFILTER 0" > bpfilter.h +bpf.h: + echo "#define NBPF 0" > bpf.h opt_bdg.h: touch opt_bdg.h Index: src/sys/modules/if_disc/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_disc/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile 1999/04/28 01:17:58 1.7 +++ Makefile 1999/07/02 08:09:13 @@ -2,16 +2,16 @@ .PATH: ${.CURDIR}/../../net KMOD= if_disc -SRCS= if_disc.c bpfilter.h opt_inet.h +SRCS= if_disc.c bpf.h opt_inet.h NOMAN= -NBPFILTER?= 1 +NBPF?= 1 CFLAGS+= ${PROTOS} -CLEANFILES+= bpfilter.h opt_inet.h +CLEANFILES+= bpf.h opt_inet.h -bpfilter.h: - echo "#define NBPFILTER ${NBPFILTER}" > bpfilter.h +bpf.h: + echo "#define NBPF ${NBPF}" > bpf.h opt_inet.h: echo "#define INET 1" > opt_inet.h Index: src/sys/modules/if_ppp/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_ppp/Makefile,v retrieving revision 1.17 diff -u -r1.17 Makefile --- Makefile 1999/04/28 01:18:02 1.17 +++ Makefile 1999/07/02 08:09:13 @@ -3,7 +3,7 @@ .PATH: ${.CURDIR}/../../net KMOD= if_ppp SRCS= if_ppp.c ppp_tty.c slcompress.c \ - bpfilter.h ppp.h opt_inet.h opt_ipx.h opt_ppp.h vnode_if.h + bpf.h ppp.h opt_inet.h opt_ipx.h opt_ppp.h vnode_if.h NOMAN= CLEANFILES+= vnode_if.c vnode_if.h @@ -23,10 +23,10 @@ SRCS+= ppp_deflate.c zlib.c .endif -CLEANFILES+= bpfilter.h opt_inet.h opt_ipx.h opt_ppp.h ppp.h +CLEANFILES+= bpf.h opt_inet.h opt_ipx.h opt_ppp.h ppp.h -bpfilter.h: - echo "#define NBPFILTER ${PPP_FILTER}" > bpfilter.h +bpf.h: + echo "#define NBPF ${PPP_FILTER}" > bpf.h ppp.h: echo "#define NPPP ${NPPP}" > ppp.h Index: src/sys/modules/if_sl/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_sl/Makefile,v retrieving revision 1.8 diff -u -r1.8 Makefile --- Makefile 1999/04/28 01:18:05 1.8 +++ Makefile 1999/07/02 08:09:13 @@ -2,18 +2,18 @@ .PATH: ${.CURDIR}/../../net KMOD= if_sl -SRCS= if_sl.c slcompress.c bpfilter.h opt_inet.h sl.h +SRCS= if_sl.c slcompress.c bpf.h opt_inet.h sl.h NOMAN= -NBPFILTER?= 1 +NBPF?= 1 NSL?= 2 PROTOS?= -DINET CFLAGS+= ${PROTOS} -CLEANFILES+= bpfilter.h opt_inet.h sl.h +CLEANFILES+= bpf.h opt_inet.h sl.h -bpfilter.h: - echo "#define NBPFILTER ${NBPFILTER}" > bpfilter.h +bpf.h: + echo "#define NBPF ${NBPF}" > bpf.h opt_inet.h: echo "#define INET 1" > opt_inet.h Index: src/sys/modules/if_tun/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_tun/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- Makefile 1999/04/28 01:18:08 1.9 +++ Makefile 1999/07/02 08:09:13 @@ -2,18 +2,18 @@ .PATH: ${.CURDIR}/../../net KMOD= if_tun -SRCS= if_tun.c bpfilter.h opt_devfs.h opt_inet.h tun.h vnode_if.h +SRCS= if_tun.c bpf.h opt_devfs.h opt_inet.h tun.h vnode_if.h NOMAN= CLEANFILES+= vnode_if.h vnode_if.c -NBPFILTER?= 1 +NBPF?= 1 NTUN?= 2 CFLAGS+= ${PROTOS} -CLEANFILES+= bpfilter.h opt_devfs.h opt_inet.h tun.h +CLEANFILES+= bpf.h opt_devfs.h opt_inet.h tun.h -bpfilter.h: - echo "#define NBPFILTER ${NBPFILTER}" > bpfilter.h +bpf.h: + echo "#define NBPF ${NBPF}" > bpf.h opt_devfs.h: touch opt_devfs.h Index: src/sys/net/bpf.c =================================================================== RCS file: /home/ncvs/src/sys/net/bpf.c,v retrieving revision 1.51 diff -u -r1.51 bpf.c --- bpf.c 1999/05/31 11:28:08 1.51 +++ bpf.c 1999/07/02 08:09:13 @@ -40,7 +40,7 @@ * $Id: bpf.c,v 1.51 1999/05/31 11:28:08 phk Exp $ */ -#include "bpfilter.h" +#include "bpf.h" #ifndef __GNUC__ #define inline @@ -84,7 +84,7 @@ #include #endif /*DEVFS*/ -#if NBPFILTER > 0 +#if NBPF > 0 /* * Older BSDs don't have kernel malloc. @@ -114,7 +114,7 @@ * bpf_dtab holds the descriptors, indexed by minor device # */ static struct bpf_if *bpf_iflist; -static struct bpf_d bpf_dtab[NBPFILTER]; +static struct bpf_d bpf_dtab[NBPF]; static int bpf_dtab_init; static int bpf_allocbufs __P((struct bpf_d *)); @@ -366,7 +366,7 @@ if (p->p_prison) return (EPERM); - if (minor(dev) >= NBPFILTER) + if (minor(dev) >= NBPF) return (ENXIO); /* * Each minor can be opened by only one process. If the requested @@ -1286,7 +1286,7 @@ * Mark all the descriptors free if this hasn't been done. */ if (!bpf_dtab_init) { - for (i = 0; i < NBPFILTER; ++i) + for (i = 0; i < NBPF; ++i) D_MARKFREE(&bpf_dtab[i]); bpf_dtab_init = 1; } @@ -1296,7 +1296,7 @@ } #ifdef DEVFS -static void *bpf_devfs_token[NBPFILTER]; +static void *bpf_devfs_token[NBPF]; #endif static int bpf_devsw_installed; @@ -1315,7 +1315,7 @@ bpf_devsw_installed = 1; #ifdef DEVFS - for ( i = 0 ; i < NBPFILTER ; i++ ) { + for ( i = 0 ; i < NBPF ; i++ ) { bpf_devfs_token[i] = devfs_add_devswf(&bpf_cdevsw, i, DV_CHR, 0, 0, 0600, "bpf%d", i); @@ -1326,7 +1326,7 @@ SYSINIT(bpfdev,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,bpf_drvinit,NULL) -#else /* !BPFILTER */ +#else /* !BPF */ /* * NOP stubs to allow bpf-using drivers to load and function. * Index: src/sys/net/if_disc.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_disc.c,v retrieving revision 1.21 diff -u -r1.21 if_disc.c --- if_disc.c 1998/12/14 01:59:16 1.21 +++ if_disc.c 1999/07/02 08:09:14 @@ -51,7 +51,7 @@ #include #include -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #ifdef TINY_DSMTU @@ -85,7 +85,7 @@ ifp->if_hdrlen = 0; ifp->if_addrlen = 0; if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, sizeof(u_int)); #endif } @@ -99,7 +99,7 @@ { if ((m->m_flags & M_PKTHDR) == 0) panic("discoutput no HDR"); -#if NBPFILTER > 0 +#if NBPF > 0 /* BPF write needs to be handled specially */ if (dst->sa_family == AF_UNSPEC) { dst->sa_family = *(mtod(m, int *)); Index: src/sys/net/if_fddisubr.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_fddisubr.c,v retrieving revision 1.34 diff -u -r1.34 if_fddisubr.c --- if_fddisubr.c 1999/01/27 22:42:13 1.34 +++ if_fddisubr.c 1999/07/02 08:09:14 @@ -105,7 +105,7 @@ extern struct ifqueue pkintrq; #endif -#include "bpfilter.h" +#include "bpf.h" #define senderr(e) { error = (e); goto bad;} @@ -309,7 +309,7 @@ break; } -#if NBPFILTER > 0 +#if NBPF > 0 case AF_IMPLINK: { fh = mtod(m, struct fddi_header *); Index: src/sys/net/if_iso88025subr.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_iso88025subr.c,v retrieving revision 1.2 diff -u -r1.2 if_iso88025subr.c --- if_iso88025subr.c 1999/03/10 10:11:43 1.2 +++ if_iso88025subr.c 1999/07/02 08:08:54 @@ -68,7 +68,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #include #endif Index: src/sys/net/if_loop.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_loop.c,v retrieving revision 1.38 diff -u -r1.38 if_loop.c --- if_loop.c 1999/02/20 21:03:53 1.38 +++ if_loop.c 1999/07/02 08:09:14 @@ -82,8 +82,8 @@ #include #endif NETATALK -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif @@ -122,7 +122,7 @@ ifp->if_type = IFT_LOOP; ifp->if_snd.ifq_maxlen = ifqmaxlen; if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, sizeof(u_int)); #endif } @@ -186,7 +186,7 @@ if ((m->m_flags & M_PKTHDR) == 0) panic("if_simloop: no HDR"); m->m_pkthdr.rcvif = ifp; -#if NBPFILTER > 0 +#if NBPF > 0 /* BPF write needs to be handled specially */ if (dst->sa_family == AF_UNSPEC) { dst->sa_family = *(mtod(m, int *)); Index: src/sys/net/if_ppp.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_ppp.c,v retrieving revision 1.60 diff -u -r1.60 if_ppp.c --- if_ppp.c 1999/04/27 11:17:00 1.60 +++ if_ppp.c 1999/07/02 08:09:14 @@ -112,12 +112,12 @@ #include #endif -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif -#if defined(PPP_FILTER) && NBPFILTER == 0 +#if defined(PPP_FILTER) && NBPF == 0 #error "PPP_FILTER requires bpf" #endif @@ -221,7 +221,7 @@ sc->sc_fastq.ifq_maxlen = IFQ_MAXLEN; sc->sc_rawq.ifq_maxlen = IFQ_MAXLEN; if_attach(&sc->sc_if); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&sc->sc_if, DLT_PPP, PPP_HDRLEN); #endif } @@ -828,7 +828,7 @@ #endif /* PPP_FILTER */ } -#if NBPFILTER > 0 +#if NBPF > 0 /* * See if bpf wants to look at the packet. */ @@ -1463,7 +1463,7 @@ #endif /* PPP_FILTER */ } -#if NBPFILTER > 0 +#if NBPF > 0 /* See if bpf wants to look at the packet. */ if (sc->sc_if.if_bpf) bpf_mtap(&sc->sc_if, m); Index: src/sys/net/if_sl.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_sl.c,v retrieving revision 1.74 diff -u -r1.74 if_sl.c --- if_sl.c 1999/04/27 11:17:02 1.74 +++ if_sl.c 1999/07/02 08:09:14 @@ -68,7 +68,7 @@ #include "sl.h" #if NSL > 0 -#include "bpfilter.h" +#include "bpf.h" #include "opt_inet.h" #if !defined(ACTUALLY_LKM_NOT_KERNEL) && !defined(KLD_MODULE) #include "opt_slip.h" @@ -105,7 +105,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -150,7 +150,7 @@ * time. So, setting SLIP_HIWAT to ~100 guarantees that we'll lose * at most 1% while maintaining good interactive response. */ -#if NBPFILTER > 0 +#if NBPF > 0 #define BUFOFFSET (128+sizeof(struct ifnet **)+SLIP_HDRLEN) #else #define BUFOFFSET (128+sizeof(struct ifnet **)) @@ -232,7 +232,7 @@ sc->sc_if.if_linkmib = sc; sc->sc_if.if_linkmiblen = sizeof *sc; if_attach(&sc->sc_if); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&sc->sc_if, DLT_SLIP, SLIP_HDRLEN); #endif } @@ -538,7 +538,7 @@ register struct ip *ip; int s; struct mbuf *m2; -#if NBPFILTER > 0 +#if NBPF > 0 u_char bpfbuf[SLTMAX + SLIP_HDRLEN]; register int len = 0; #endif @@ -583,7 +583,7 @@ * queueing, and the connection id compression will get * munged when this happens. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) { /* * We need to save the TCP/IP header before it's @@ -612,7 +612,7 @@ *mtod(m, u_char *) |= sl_compress_tcp(m, ip, &sc->sc_comp, 1); } -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) { /* * Put the SLIP pseudo-"link header" in place. The @@ -775,7 +775,7 @@ register struct mbuf *m; register int len; int s; -#if NBPFILTER > 0 +#if NBPF > 0 u_char chdr[CHDR_LEN]; #endif @@ -844,7 +844,7 @@ /* less than min length packet - ignore */ goto newpack; -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) { /* * Save the compressed header, so we @@ -885,7 +885,7 @@ } else goto error; } -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) { /* * Put the SLIP pseudo-"link header" in place. Index: src/sys/net/if_tun.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_tun.c,v retrieving revision 1.59 diff -u -r1.59 if_tun.c --- if_tun.c 1999/06/19 18:42:28 1.59 +++ if_tun.c 1999/07/02 08:09:14 @@ -54,8 +54,8 @@ #include #endif -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif @@ -144,7 +144,7 @@ ifp->if_flags = IFF_POINTOPOINT | IFF_MULTICAST; ifp->if_snd.ifq_maxlen = ifqmaxlen; if_attach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, sizeof(u_int)); #endif } @@ -340,7 +340,7 @@ return EHOSTDOWN; } -#if NBPFILTER > 0 +#if NBPF > 0 /* BPF write needs to be handled specially */ if (dst->sa_family == AF_UNSPEC) { dst->sa_family = *(mtod(m0, int *)); @@ -366,7 +366,7 @@ bpf_mtap(ifp, &m); } -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ /* prepend sockaddr? this may abort if the mbuf allocation fails */ if (tp->tun_flags & TUN_LMODE) { @@ -628,7 +628,7 @@ top->m_pkthdr.len = tlen; top->m_pkthdr.rcvif = ifp; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { /* * We need to prepend the address family as Index: src/sys/net/if_vlan.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.7 diff -u -r1.7 if_vlan.c --- if_vlan.c 1999/04/07 23:26:43 1.7 +++ if_vlan.c 1999/07/02 08:09:14 @@ -57,7 +57,7 @@ #include "vlan.h" #if NVLAN > 0 #include "opt_inet.h" -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -69,7 +69,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif #include @@ -176,7 +176,7 @@ ifp->if_snd.ifq_maxlen = ifqmaxlen; if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif /* Now undo some of the damage... */ @@ -209,10 +209,10 @@ IF_DEQUEUE(&ifp->if_snd, m); if (m == 0) break; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m); -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ /* * If the LINK0 flag is set, it means the underlying interface @@ -304,7 +304,7 @@ */ m->m_pkthdr.rcvif = &ifv->ifv_if; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifv->ifv_if.if_bpf) { /* * Do the usual BPF fakery. Note that we don't support @@ -356,7 +356,7 @@ m->m_len -= EVL_ENCAPLEN; m->m_pkthdr.len -= EVL_ENCAPLEN; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifv->ifv_if.if_bpf) { /* * Do the usual BPF fakery. Note that we don't support Index: src/sys/pc98/conf/GENERIC98 =================================================================== RCS file: /home/ncvs/src/sys/pc98/conf/GENERIC98,v retrieving revision 1.77 diff -u -r1.77 GENERIC98 --- GENERIC98 1999/06/18 14:48:18 1.77 +++ GENERIC98 1999/07/02 08:09:14 @@ -262,8 +262,8 @@ options SYSVSEM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter Index: src/sys/pc98/pc98/if_ed.c =================================================================== RCS file: /home/ncvs/src/sys/pc98/pc98/if_ed.c,v retrieving revision 1.63 diff -u -r1.63 if_ed.c --- if_ed.c 1999/05/10 09:06:12 1.63 +++ if_ed.c 1999/07/02 08:09:14 @@ -60,7 +60,7 @@ */ #include "ed.h" -#include "bpfilter.h" +#include "bpf.h" #include "pnp.h" #ifndef EXTRA_ED @@ -87,7 +87,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif #include "opt_bdg.h" @@ -2463,7 +2463,7 @@ /* * If BPF is in the kernel, call the attach for it */ -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif return 1; @@ -2929,7 +2929,7 @@ /* * Tap off here if there is a bpf listener. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { bpf_mtap(ifp, m0); } @@ -3371,7 +3371,7 @@ } } -#if NBPFILTER > 0 +#if NBPF > 0 /* * Promiscuous flag may have changed, so reprogram the RCR. @@ -3502,7 +3502,7 @@ struct ifnet *ifp ; int need_more = 1 ; /* in case not bpf */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->arpcom.ac_if.if_bpf) { need_more = 0 ; ed_ring_copy(sc, buf, (char *)eh, len); @@ -3533,7 +3533,7 @@ */ ed_ring_copy(sc, buf, (char *)eh, len); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Check if there's a BPF listener on this interface. If so, hand off Index: src/sys/pc98/pc98/olpt.c =================================================================== RCS file: /home/ncvs/src/sys/pc98/pc98/olpt.c,v retrieving revision 1.1 diff -u -r1.1 olpt.c --- olpt.c 1999/06/18 14:48:26 1.1 +++ olpt.c 1999/07/02 08:09:14 @@ -145,8 +145,8 @@ #include #include #include -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif #endif /* INET */ @@ -958,7 +958,7 @@ if_attach(ifp); printf("lp%d: TCP/IP capable interface\n", unit); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_NULL, LPIPHDRLEN); #endif } @@ -1232,7 +1232,7 @@ IF_DROP(&ipintrq); goto done; } -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->sc_if.if_bpf) { bpf_tap(&sc->sc_if, sc->sc_ifbuf, len); } @@ -1424,7 +1424,7 @@ } else { ifp->if_opackets++; ifp->if_obytes += m->m_pkthdr.len; -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) { /* * We need to prepend the packet type as Index: src/sys/pci/if_al.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_al.c,v retrieving revision 1.4 diff -u -r1.4 if_al.c --- if_al.c 1999/05/26 22:56:22 1.4 +++ if_al.c 1999/07/02 08:09:16 @@ -49,7 +49,7 @@ * has physical address and multicast address registers. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -65,7 +65,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1066,7 +1066,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(al_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1300,7 +1300,7 @@ ifp->if_ipackets++; eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1625,7 +1625,7 @@ /* Pack the data into the descriptor. */ al_encap(sc, cur_tx, m_head); -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_ax.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_ax.c,v retrieving revision 1.9 diff -u -r1.9 if_ax.c --- if_ax.c 1999/05/09 17:06:48 1.9 +++ if_ax.c 1999/07/02 08:09:14 @@ -49,7 +49,7 @@ * the registers. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -65,7 +65,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1308,7 +1308,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(ax_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1542,7 +1542,7 @@ ifp->if_ipackets++; eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1866,7 +1866,7 @@ if (cur_tx != start_tx) AX_TXOWN(cur_tx) = AX_TXSTAT_OWN; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_de.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.106 diff -u -r1.106 if_de.c --- if_de.c 1999/05/10 14:12:26 1.106 +++ if_de.c 1999/07/02 08:09:14 @@ -93,8 +93,8 @@ #include #endif -#include "bpfilter.h" -#if NBPFILTER > 0 +#include "bpf.h" +#if NBPF > 0 #include #endif @@ -3539,7 +3539,7 @@ #endif /* TULIP_BUS_DMA */ eh = *mtod(ms, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->tulip_bpf != NULL) { if (me == ms) TULIP_BPF_TAP(sc, mtod(ms, caddr_t), total_len); @@ -3810,7 +3810,7 @@ TULIP_TXMAP_POSTSYNC(sc, map); sc->tulip_txmaps[sc->tulip_txmaps_free++] = map; #endif /* TULIP_BUS_DMA */ -#if NBPFILTER > 0 +#if NBPF > 0 if (sc->tulip_bpf != NULL) TULIP_BPF_MTAP(sc, m); #endif @@ -5115,7 +5115,7 @@ #endif #endif /* __bsdi__ */ -#if NBPFILTER > 0 +#if NBPF > 0 TULIP_BPF_ATTACH(sc); #endif Index: src/sys/pci/if_devar.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_devar.h,v retrieving revision 1.13 diff -u -r1.13 if_devar.h --- if_devar.h 1999/05/26 23:05:23 1.13 +++ if_devar.h 1999/07/02 08:08:55 @@ -961,7 +961,7 @@ #endif #if BSD >= 199506 #define TULIP_IFP_TO_SOFTC(ifp) ((tulip_softc_t *)((ifp)->if_softc)) -#if NBPFILTER > 0 +#if NBPF > 0 #define TULIP_BPF_MTAP(sc, m) bpf_mtap(&(sc)->tulip_if, m) #define TULIP_BPF_TAP(sc, p, l) bpf_tap(&(sc)->tulip_if, p, l) #define TULIP_BPF_ATTACH(sc) bpfattach(&(sc)->tulip_if, DLT_EN10MB, sizeof(struct ether_header)) @@ -1115,7 +1115,7 @@ * While I think FreeBSD's 2.2 change to the bpf is a nice simplification, * it does add yet more conditional code to this driver. Sigh. */ -#if !defined(TULIP_BPF_MTAP) && NBPFILTER > 0 +#if !defined(TULIP_BPF_MTAP) && NBPF > 0 #define TULIP_BPF_MTAP(sc, m) bpf_mtap((sc)->tulip_bpf, m) #define TULIP_BPF_TAP(sc, p, l) bpf_tap((sc)->tulip_bpf, p, l) #define TULIP_BPF_ATTACH(sc) bpfattach(&(sc)->tulip_bpf, &(sc)->tulip_if, DLT_EN10MB, sizeof(struct ether_header)) Index: src/sys/pci/if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.69 diff -u -r1.69 if_fxp.c --- if_fxp.c 1999/05/09 10:45:54 1.69 +++ if_fxp.c 1999/07/02 08:09:15 @@ -34,7 +34,7 @@ * Intel EtherExpress Pro/100B PCI Fast Ethernet driver */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -52,7 +52,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -419,7 +419,7 @@ */ ifp->if_snd.ifq_maxlen = FXP_NTXCB - 1; ether_ifattach(ifp, enaddr); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&sc->sc_ethercom.ec_if.if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -598,7 +598,7 @@ */ ifp->if_snd.ifq_maxlen = FXP_NTXCB - 1; ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -988,7 +988,7 @@ sc->tx_queued++; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Pass packet to bpf if there is a listener. */ @@ -1097,12 +1097,12 @@ m->m_pkthdr.len = m->m_len = total_len ; eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_tap(FXP_BPFTAP_ARG(ifp), mtod(m, caddr_t), total_len); -#endif /* NBPFILTER > 0 */ +#endif /* NBPF > 0 */ #ifdef BRIDGE if (do_bridge) { struct ifnet *bdg_ifp ; Index: src/sys/pci/if_mx.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_mx.c,v retrieving revision 1.19 diff -u -r1.19 if_mx.c --- if_mx.c 1999/06/16 16:27:30 1.19 +++ if_mx.c 1999/07/02 08:09:15 @@ -56,7 +56,7 @@ * the NWAY support. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -72,7 +72,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1563,7 +1563,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(mx_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1777,7 +1777,7 @@ eh = mtod(m, struct ether_header *); m->m_pkthdr.rcvif = ifp; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -2118,7 +2118,7 @@ if (cur_tx != start_tx) MX_TXOWN(cur_tx) = MX_TXSTAT_OWN; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_pn.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_pn.c,v retrieving revision 1.21 diff -u -r1.21 if_pn.c --- if_pn.c 1999/05/28 18:43:10 1.21 +++ if_pn.c 1999/07/02 08:09:15 @@ -57,7 +57,7 @@ * 100BaseTX PHY. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -73,7 +73,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1211,7 +1211,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(pn_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1569,7 +1569,7 @@ eh = mtod(m, struct ether_header *); m->m_pkthdr.rcvif = ifp; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1900,7 +1900,7 @@ if (cur_tx != start_tx) PN_TXOWN(cur_tx) = PN_TXSTAT_OWN; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_rl.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_rl.c,v retrieving revision 1.17 diff -u -r1.17 if_rl.c --- if_rl.c 1999/06/19 20:17:37 1.17 +++ if_rl.c 1999/07/02 08:09:15 @@ -83,7 +83,7 @@ * to select which interface to use depending on the chip type. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -99,7 +99,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1234,7 +1234,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(rl_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1417,7 +1417,7 @@ eh = mtod(m, struct ether_header *); ifp->if_ipackets++; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1614,7 +1614,7 @@ rl_encap(sc, m_head); -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_ti.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_ti.c,v retrieving revision 1.7 diff -u -r1.7 if_ti.c --- if_ti.c 1999/06/19 00:36:53 1.7 +++ if_ti.c 1999/07/02 08:09:15 @@ -78,7 +78,7 @@ * - Andrew Gallatin for providing FreeBSD/Alpha support. */ -#include "bpfilter.h" +#include "bpf.h" #include "vlan.h" #include @@ -96,7 +96,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1735,7 +1735,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -1830,7 +1830,7 @@ eh = mtod(m, struct ether_header *); m->m_pkthdr.rcvif = ifp; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -2113,7 +2113,7 @@ * If there's a BPF listener, bounce a copy of this frame * to him. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, m_head); #endif Index: src/sys/pci/if_tl.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_tl.c,v retrieving revision 1.32 diff -u -r1.32 if_tl.c --- if_tl.c 1999/05/09 17:07:01 1.32 +++ if_tl.c 1999/07/02 08:09:15 @@ -178,7 +178,7 @@ * itself thereby reducing the load on the host CPU. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -194,7 +194,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1786,7 +1786,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -1966,7 +1966,7 @@ continue; } -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -2434,7 +2434,7 @@ * If there's a BPF listener, bounce a copy of this frame * to him. */ -#if NBPFILTER > 0 +#if NBPF > 0 if (ifp->if_bpf) bpf_mtap(ifp, cur_tx->tl_mbuf); #endif Index: src/sys/pci/if_tx.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_tx.c,v retrieving revision 1.27 diff -u -r1.27 if_tx.c --- if_tx.c 1999/05/10 00:20:46 1.27 +++ if_tx.c 1999/07/02 08:09:15 @@ -67,7 +67,7 @@ } \ } -#include "bpfilter.h" +#include "bpf.h" #include "pci.h" #include "opt_bdg.h" @@ -107,7 +107,7 @@ #include #endif -#if NBPFILTER > 0 +#if NBPF > 0 #include #include #endif @@ -357,7 +357,7 @@ /* Attach os interface and bpf */ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(&sc->sc_if.if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -554,7 +554,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp,DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -850,7 +850,7 @@ /* Set watchdog timer */ ifp->if_timer = 8; -#if NBPFILTER > 0 +#if NBPF > 0 if( ifp->if_bpf ) #if defined(__FreeBSD__) bpf_mtap( ifp, m0 ); @@ -920,15 +920,15 @@ m->m_pkthdr.rcvif = &(sc->sc_if); m->m_pkthdr.len = m->m_len = len; -#if NBPFILTER > 0 - /* Give mbuf to BPFILTER */ +#if NBPF > 0 + /* Give mbuf to BPF */ if( sc->sc_if.if_bpf ) #if defined(__FreeBSD__) bpf_mtap( &sc->sc_if, m ); #else /* __OpenBSD__ */ bpf_mtap( sc->sc_if.if_bpf, m ); #endif /* __FreeBSD__ */ -#endif /* NBPFILTER */ +#endif /* NBPF */ #ifdef BRIDGE if (do_bridge) { @@ -951,7 +951,7 @@ } #endif -#if NBPFILTER > 0 +#if NBPF > 0 #ifdef BRIDGE /* * This deserves explanation @@ -961,7 +961,7 @@ * address of one of the other interfaces. * * But if the bridge is off, then we have to drop - * stuff that came in just via bpfilter. + * stuff that came in just via bpf. */ if (!do_bridge) #endif Index: src/sys/pci/if_vr.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_vr.c,v retrieving revision 1.11 diff -u -r1.11 if_vr.c --- if_vr.c 1999/05/09 17:07:03 1.11 +++ if_vr.c 1999/07/02 08:09:15 @@ -59,7 +59,7 @@ * transmission. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -75,7 +75,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1110,7 +1110,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif @@ -1316,7 +1316,7 @@ eh = mtod(m, struct ether_header *); m->m_pkthdr.rcvif = ifp; m->m_pkthdr.len = m->m_len = total_len; -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1621,7 +1621,7 @@ if (cur_tx != start_tx) VR_TXOWN(cur_tx) = VR_TXSTAT_OWN; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_wb.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_wb.c,v retrieving revision 1.10 diff -u -r1.10 if_wb.c --- if_wb.c 1999/05/13 20:36:00 1.10 +++ if_wb.c 1999/07/02 08:09:15 @@ -83,7 +83,7 @@ * three of my test boards seems fine. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -99,7 +99,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1228,7 +1228,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(wb_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1423,7 +1423,7 @@ ifp->if_ipackets++; eh = mtod(m, struct ether_header *); -#if NBPFILTER > 0 +#if NBPF > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but * don't pass it up to the ether_input() layer unless it's @@ -1772,7 +1772,7 @@ if (cur_tx != start_tx) WB_TXOWN(cur_tx) = WB_TXSTAT_OWN; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. Index: src/sys/pci/if_xl.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_xl.c,v retrieving revision 1.40 diff -u -r1.40 if_xl.c --- if_xl.c 1999/06/01 19:04:23 1.40 +++ if_xl.c 1999/07/02 08:09:15 @@ -89,7 +89,7 @@ * PCI-based NICs. */ -#include "bpfilter.h" +#include "bpf.h" #include #include @@ -105,7 +105,7 @@ #include #include -#if NBPFILTER > 0 +#if NBPF > 0 #include #endif @@ -1791,7 +1791,7 @@ if_attach(ifp); ether_ifattach(ifp); -#if NBPFILTER > 0 +#if NBPF > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif at_shutdown(xl_shutdown, sc, SHUTDOWN_POST_SYNC); @@ -1967,7 +1967,7 @@ m->m_pkthdr.rcvif = ifp; m->m_pkthdr.len = m->m_len = total_len; -#if NBPFILTER > 0 +#if NBPF > 0 /* Handle BPF listeners. Let the BPF user see the packet. */ if (ifp->if_bpf) bpf_mtap(ifp, m); @@ -1987,7 +1987,7 @@ } #endif -#if NBPFILTER > 0 +#if NBPF > 0 /* * Don't pass packet up to the ether_input() layer unless it's * a broadcast packet, multicast packet, matches our ethernet @@ -2381,7 +2381,7 @@ } prev = cur_tx; -#if NBPFILTER > 0 +#if NBPF > 0 /* * If there's a BPF listener, bounce a copy of this frame * to him. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 2:56:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 763A51536F; Sat, 3 Jul 1999 02:56:41 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id LAA54563; Sat, 3 Jul 1999 11:56:30 +0200 (CEST) (envelope-from des) To: hackers@freebsd.org Subject: netstat(1) / sockstat(1) field width adjustments Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 03 Jul 1999 11:56:30 +0200 Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Bcc:ed to net, please follow up on hackers] Attached are patches which widen the local/foreign address fields in netstat(1) (so as not to truncate the port number) and the protocol field in sockstat(1) (to accomodate 'divert'). The netstat patch has the unfortunate side effect of pushing the state field so far to the right that most states (except LISTEN) spill over. I consider that the lesser of two evils. I chopped two characters off the process name field to avoid a similar problem in sockstat. As usual, I welcome comments and suggestions, and will commit the patches to -CURRENT in a few days if no-one objects. The patches are by Ruslan Ermilov, with a few adjustment by yours truly. DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 6:26:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 6D07514F9E for ; Sat, 3 Jul 1999 06:26:11 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id PAA55161; Sat, 3 Jul 1999 15:26:02 +0200 (CEST) (envelope-from des) To: Dag-Erling Smorgrav Cc: hackers@freebsd.org Subject: Re: netstat(1) / sockstat(1) field width adjustments References: Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 03 Jul 1999 15:26:01 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "03 Jul 1999 11:56:30 +0200" Message-ID: Lines: 125 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Attached are patches [...] ...and here are the patches. Noticed by: Peter Wemm DES -- Dag-Erling Smorgrav - des@yes.no Index: src/usr.bin/netstat/inet.c =================================================================== RCS file: /home/ncvs/src/usr.bin/netstat/inet.c,v retrieving revision 1.31 diff -u -r1.31 inet.c --- inet.c 1999/03/10 17:25:42 1.31 +++ inet.c 1999/07/03 09:41:51 @@ -163,9 +163,7 @@ putchar('\n'); if (Aflag) printf("%-8.8s ", "Socket"); - printf(Aflag ? - "%-5.5s %-6.6s %-6.6s %-18.18s %-18.18s %s\n" : - "%-5.5s %-6.6s %-6.6s %-22.22s %-22.22s %s\n", + printf("%-5.5s %-6.6s %-6.6s %-21.21s %-21.21s %s\n", "Proto", "Recv-Q", "Send-Q", "Local Address", "Foreign Address", "(state)"); first = 0; @@ -196,9 +194,9 @@ } if (istcp) { if (tp->t_state < 0 || tp->t_state >= TCP_NSTATES) - printf(" %d", tp->t_state); + printf("%d", tp->t_state); else { - printf(" %s", tcpstates[tp->t_state]); + printf("%s", tcpstates[tp->t_state]); #if defined(TF_NEEDSYN) && defined(TF_NEEDFIN) /* Show T/TCP `hidden state' */ if (tp->t_flags & (TF_NEEDSYN|TF_NEEDFIN)) @@ -555,7 +553,6 @@ { struct servent *sp = 0; char line[80], *cp; - int width; sprintf(line, "%.*s.", (Aflag && !numeric) ? 12 : 16, inetname(in)); cp = index(line, '\0'); @@ -565,8 +562,7 @@ sprintf(cp, "%.15s", sp ? sp->s_name : "*"); else sprintf(cp, "%d", ntohs((u_short)port)); - width = Aflag ? 18 : 22; - printf(" %-*.*s", width, width, line); + printf("%-21.21s ", line); } /* Index: src/usr.bin/sockstat/sockstat.1 =================================================================== RCS file: /home/ncvs/src/usr.bin/sockstat/sockstat.1,v retrieving revision 1.1 diff -u -r1.1 sockstat.1 --- sockstat.1 1999/04/15 13:40:43 1.1 +++ sockstat.1 1999/07/03 09:41:51 @@ -39,7 +39,7 @@ .Nm command lists open Internet sockets. The information listed for each socket is: -.Bl -tag -width FOREIGN_ADDRESS +.Bl -tag -width "FOREIGN ADDRESS" .It Li USER The user who owns the socket. .It Li COMMAND @@ -49,7 +49,7 @@ .It Li FD The file descriptor number of the socket. .It Li PROTO -The transport protocol (udp or tcp) associated with the socket. +The transport protocol associated with the socket. .It Li LOCAL ADDRESS The address the local end of the socket is bound to (see .Xr getsockname 2 ). @@ -59,8 +59,8 @@ .El .Sh SEE ALSO .Xr fstat 1 , -.Xr inet 4 , -.Xr netstat 1 . +.Xr netstat 1 , +.Xr inet 4 . .Sh HISTORY The .Nm Index: src/usr.bin/sockstat/sockstat.pl =================================================================== RCS file: /home/ncvs/src/usr.bin/sockstat/sockstat.pl,v retrieving revision 1.2 diff -u -r1.2 sockstat.pl --- sockstat.pl 1999/05/01 11:31:19 1.2 +++ sockstat.pl 1999/07/03 09:48:24 @@ -33,18 +33,17 @@ my ($user, $cmd, $pid, $fd, $inet, $type, $proto, $sock, $laddr, $faddr); print <>>> @>>> @<< @<<<<<<<<<<<<<<<<<<< @<<<<<<<<<<<<<<<<<<< -$user, $cmd, $pid, $fd, $proto,$laddr, $faddr +@<<<<<<< @<<<<<<< @>>>> @>>> @<<<<< @<<<<<<<<<<<<<<<<<<<< @<<<<<<<<<<<<<<<<<<<< +$user, $cmd, $pid, $fd, $proto,$laddr, $faddr . -open NETSTAT, "netstat -Aan |" or die "'netstat -Aan' failed: $!"; +open NETSTAT, "netstat -Aan -finet | tail +3 |" or die "'netstat' failed: $!"; while () { my ($sock, $proto, $recvq, $sendq, $laddr, $faddr, $state) = split; - next unless ($proto =~ m/tcp|udp/); ($myaddr{$sock}, $hisaddr{$sock}) = ($laddr, $faddr); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 6:39:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 8272114C2D for ; Sat, 3 Jul 1999 06:39:38 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id IAA26329; Sat, 3 Jul 1999 08:39:36 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id IAA12641; Sat, 3 Jul 1999 08:39:35 -0500 Message-ID: <19990703083935.61252@right.PCS> Date: Sat, 3 Jul 1999 08:39:35 -0500 From: Jonathan Lemon To: "Brian F. Feldman" Cc: wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() References: <199907030427.XAA17423@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Brian F. Feldman on Jul 07, 1999 at 01:01:07AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1999 at 01:01:07AM -0400, Brian F. Feldman wrote: > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > poll() is faster (it doesn't have to do bit twiddling), and it's interface > > is cleaner (it can report invalid fd's, something select() can't do). As > > its functionality is a superset of select()'s, it is used as the internal > > implementation for select(). > > Actually, select() doesn't require horrendous amounts of copyin()s, which > poll() does. So have you benchmarked the two? I'd expect select to be faster. Yup, I have. poll() is faster; copying the parameters takes less time than bit twiddling. > > As for new code, use whichever you are comfortable with. Personally, I > > would recommend poll(), since it provides some added functionality over > > select() that makes for easier programming. > > poll() is a huge pain to use, which is why I recommend select(). Whichever you're comfortable with. poll() isn't a pain once you know how to use it, and it does bring additional benefits. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 6:44:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 8F11314C2D for ; Sat, 3 Jul 1999 06:44:10 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id JAA26548 for ; Sat, 3 Jul 1999 09:44:09 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22118; Sat, 3 Jul 1999 09:43:38 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id JAA13822; Sat, 3 Jul 1999 09:43:37 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199907031343.JAA13822@dean.pc.sas.com> Subject: support for i386 hardware debug watch points To: freebsd-hackers@freebsd.org Date: Sat, 3 Jul 1999 09:43:37 -0400 (EDT) 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 Hi, After recently debugging a very elusive memory overwrite problem that I was only able to find by setting up a debugger watch point, and suffering through the slowness that this introduced, I began reading up on the ix86 support for hardware watch points. Using this facility of the chip would require OS support, and specifically, loading the debug registers at context switch time. Also, the 'ptrace' system call could easily be extended to provide an interface for doing this from user code. Is there any interest in supporting something like this in FreeBSD? I'm volunteering to spend some cycles on this, but I don't want to go to the effort if there's little chance that the work would be integrated. Thanks, -Brian -- Brian Dean SAS Institute Inc brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 7: 6:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 37B9614C46 for ; Sat, 3 Jul 1999 07:06:29 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA10879; Sat, 3 Jul 1999 10:06:44 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA04308; Sat, 3 Jul 1999 10:06:24 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id KAA55948; Sat, 3 Jul 1999 10:06:23 -0400 (EDT) Date: Sat, 3 Jul 1999 10:06:23 -0400 (EDT) From: Thomas David Rivers Message-Id: <199907031406.KAA55948@lakes.dignus.com> To: brdean@unx.sas.com, freebsd-hackers@FreeBSD.ORG Subject: Re: support for i386 hardware debug watch points In-Reply-To: <199907031343.JAA13822@dean.pc.sas.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, > > After recently debugging a very elusive memory overwrite problem that > I was only able to find by setting up a debugger watch point, and > suffering through the slowness that this introduced, I began reading > up on the ix86 support for hardware watch points. Using this facility > of the chip would require OS support, and specifically, loading the > debug registers at context switch time. Also, the 'ptrace' system > call could easily be extended to provide an interface for doing this > from user code. > > Is there any interest in supporting something like this in FreeBSD? > I'm volunteering to spend some cycles on this, but I don't want to go > to the effort if there's little chance that the work would be > integrated. > > Thanks, > -Brian > -- > Brian Dean SAS Institute Inc brdean@unx.sas.com > Brian - Scan through the mail archives - I brought this up about this time last year, I think... There were several responses - some people may be willing to assist... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 7:26:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6C7C414D9D for ; Sat, 3 Jul 1999 07:26:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id ED06C64; Sat, 3 Jul 1999 22:26:24 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas David Rivers Cc: brdean@unx.sas.com, freebsd-hackers@FreeBSD.ORG Subject: Re: support for i386 hardware debug watch points In-reply-to: Your message of "Sat, 03 Jul 1999 10:06:23 -0400." <199907031406.KAA55948@lakes.dignus.com> Date: Sat, 03 Jul 1999 22:26:24 +0800 From: Peter Wemm Message-Id: <19990703142624.ED06C64@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > > > Hi, > > > > After recently debugging a very elusive memory overwrite problem that > > I was only able to find by setting up a debugger watch point, and > > suffering through the slowness that this introduced, I began reading > > up on the ix86 support for hardware watch points. Using this facility > > of the chip would require OS support, and specifically, loading the > > debug registers at context switch time. Also, the 'ptrace' system > > call could easily be extended to provide an interface for doing this > > from user code. > > > > Is there any interest in supporting something like this in FreeBSD? > > I'm volunteering to spend some cycles on this, but I don't want to go > > to the effort if there's little chance that the work would be > > integrated. > > > > Thanks, > > -Brian > > -- > > Brian Dean SAS Institute Inc brdean@unx.sas.com > > > > > Brian - > > Scan through the mail archives - I brought this up about this > time last year, I think... > > There were several responses - some people may be willing to > assist... I'll chime in.. I'd be quite willing to bring something like this in, assuming it was done reasonably cleanly. It shouldn't be too hard to do it without imparing portability across cpu/arch types. I think this would be quite useful, especially if gdb could be made aware of it too. > - Dave Rivers - Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 8:28:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B516E14D92 for ; Sat, 3 Jul 1999 08:28:00 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA34426; Sat, 3 Jul 1999 11:27:57 -0400 (EDT) Date: Sat, 3 Jul 1999 11:27:57 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Jonathan Lemon Cc: wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() In-Reply-To: <19990703083935.61252@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Jonathan Lemon wrote: > On Jul 07, 1999 at 01:01:07AM -0400, Brian F. Feldman wrote: > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > As for new code, use whichever you are comfortable with. Personally, I > > > would recommend poll(), since it provides some added functionality over > > > select() that makes for easier programming. > > > > poll() is a huge pain to use, which is why I recommend select(). > > Whichever you're comfortable with. poll() isn't a pain once you know > how to use it, and it does bring additional benefits. I don't see how you can not find poll() a pain when compared to select(). It requires so much set-up, much like (for instance) aio_write() as opposed to write(). I suppose if you're masochistic, you won't mind doing that :) > -- > Jonathan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 8:44:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id DDC3B14CCE for ; Sat, 3 Jul 1999 08:44:16 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA26627; Sat, 3 Jul 1999 10:44:13 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA19656; Sat, 3 Jul 1999 10:44:12 -0500 Message-ID: <19990703104412.48991@right.PCS> Date: Sat, 3 Jul 1999 10:44:12 -0500 From: Jonathan Lemon To: "Brian F. Feldman" Cc: wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() References: <19990703083935.61252@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Brian F. Feldman on Jul 07, 1999 at 11:27:57AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1999 at 11:27:57AM -0400, Brian F. Feldman wrote: > On Sat, 3 Jul 1999, Jonathan Lemon wrote: > > > On Jul 07, 1999 at 01:01:07AM -0400, Brian F. Feldman wrote: > > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > > > As for new code, use whichever you are comfortable with. Personally, I > > > > would recommend poll(), since it provides some added functionality over > > > > select() that makes for easier programming. > > > > > > poll() is a huge pain to use, which is why I recommend select(). > > > > Whichever you're comfortable with. poll() isn't a pain once you know > > how to use it, and it does bring additional benefits. > > I don't see how you can not find poll() a pain when compared to select(). It > requires so much set-up, much like (for instance) aio_write() as opposed to > write(). I suppose if you're masochistic, you won't mind doing that :) Yes, it does require more initial setup. But consider: - you don't have to re-initialize the fd sets every time around the loop, as you do with select(). This administrative overhead is moved into the initial setup, not into the main loop. - it becomes simple to ignore a slot entry; simply set the fd value to -1. - you get notification when the fd is closed. E.g.: you can poll() on a fd, ignoring both read ready and write ready state, and get POLLHUP returned when it closes. for select(), the only way to know that the fd closed is to actually do a read() on the descriptor, and have it return EOF. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 9: 6: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2B5A514C12 for ; Sat, 3 Jul 1999 09:05:58 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA07099; Sat, 3 Jul 1999 12:10:41 -0400 (EDT) Date: Sat, 3 Jul 1999 11:10:39 -0500 (EST) From: Alfred Perlstein To: Jonathan Lemon Cc: "Brian F. Feldman" , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() In-Reply-To: <19990703104412.48991@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Jonathan Lemon wrote: > On Jul 07, 1999 at 11:27:57AM -0400, Brian F. Feldman wrote: > > On Sat, 3 Jul 1999, Jonathan Lemon wrote: > > > > > On Jul 07, 1999 at 01:01:07AM -0400, Brian F. Feldman wrote: > > > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > > > > > As for new code, use whichever you are comfortable with. Personally, I > > > > > would recommend poll(), since it provides some added functionality over > > > > > select() that makes for easier programming. > > > > > > > > poll() is a huge pain to use, which is why I recommend select(). > > > > > > Whichever you're comfortable with. poll() isn't a pain once you know > > > how to use it, and it does bring additional benefits. > > > > I don't see how you can not find poll() a pain when compared to select(). It > > requires so much set-up, much like (for instance) aio_write() as opposed to > > write(). I suppose if you're masochistic, you won't mind doing that :) > > Yes, it does require more initial setup. But consider: > > - you don't have to re-initialize the fd sets every time around the > loop, as you do with select(). This administrative overhead is > moved into the initial setup, not into the main loop. > > - it becomes simple to ignore a slot entry; simply set the fd value to -1. > > - you get notification when the fd is closed. E.g.: you can poll() > on a fd, ignoring both read ready and write ready state, and get > POLLHUP returned when it closes. for select(), the only way to > know that the fd closed is to actually do a read() on the descriptor, > and have it return EOF. I agree. With a proper algorithm you can also track the fds in use and migrate them to lower slots in the pollfd array as well as make an allocator that attempts to grab slots at the beginning. Just something i'm working on right now :) -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Win Telecom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 9:14:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8E0D114EDD for ; Sat, 3 Jul 1999 09:14:19 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id MAA35132; Sat, 3 Jul 1999 12:13:55 -0400 (EDT) Date: Sat, 3 Jul 1999 12:13:55 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: Thomas David Rivers , brdean@unx.sas.com, freebsd-hackers@FreeBSD.ORG Subject: Re: support for i386 hardware debug watch points In-Reply-To: <19990703142624.ED06C64@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Peter Wemm wrote: > Thomas David Rivers wrote: > > > > > > Is there any interest in supporting something like this in FreeBSD? > > > I'm volunteering to spend some cycles on this, but I don't want to go > > > to the effort if there's little chance that the work would be > > > integrated. > > > > > > Thanks, > > > -Brian > > > -- > > > Brian Dean SAS Institute Inc brdean@unx.sas.com > > > > > > > > > Brian - > > > > Scan through the mail archives - I brought this up about this > > time last year, I think... > > > > There were several responses - some people may be willing to > > assist... > > I'll chime in.. I'd be quite willing to bring something like this in, > assuming it was done reasonably cleanly. It shouldn't be too hard to do it > without imparing portability across cpu/arch types. > > I think this would be quite useful, especially if gdb could be made aware > of it too. I think this would be great too, but I have a concern. Not all CPUs (x86) support this; make ABSOLUTELY sure it doesn't do this kind of thing on hardware which doesn't support it, please! > > > - Dave Rivers - > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 9:33: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r2.bfm.org [208.18.213.98]) by hub.freebsd.org (Postfix) with ESMTP id 0C27C14FD5 for ; Sat, 3 Jul 1999 09:32:58 -0700 (PDT) (envelope-from adam@whizkidtech.net) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id LAA00240; Sat, 3 Jul 1999 11:31:41 -0500 (CDT) (envelope-from adam) Date: Sat, 3 Jul 1999 11:31:40 -0500 From: "G. Adam Stanislav" To: Wes Peters Cc: Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? Message-ID: <19990703113140.B220@whizkidtech.net> References: <377DB95C.448E4227@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <377DB95C.448E4227@softweyr.com>; from Wes Peters on Sat, Jul 03, 1999 at 01:18:52AM -0600 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ 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 Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > You either are a hacker, or you are not. It is not something someone else > > > can teach you. > > > > This deserves a FAQ entry. What an awesome response. > > But it's certainly NOT something that you just are, either. You have to > have talent, but you also have to have experience. This is most often > done by a mentor. If you have the innate curiosity mentioned in my message, you will obtain experience whether you have a mentor or not. Experience is best obtained by trying things. It cannot be imparted by anyone else (although, it can be encouraged). Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 10: 4:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.qcislands.net (mail.qcislands.net [209.53.238.6]) by hub.freebsd.org (Postfix) with ESMTP id B091F14D05 for ; Sat, 3 Jul 1999 10:04:27 -0700 (PDT) (envelope-from paz@qcislands.net) Received: from [209.205.50.22] (helo=osa.qcislands.net) by mail.qcislands.net with esmtp (Exim 2.12 #7) id 110TDI-0000Su-00 for freebsd-hackers@freebsd.org; Sat, 3 Jul 1999 10:04:28 -0700 Received: from paz by osa.qcislands.net with local (Exim 3.01 #3) id 110THP-0001ft-00; Sat, 03 Jul 1999 10:08:43 -0700 From: paz@qcislands.net (Jim Pazarena) To: freebsd-hackers@FreeBSD.ORG Subject: BUG boot-time messages X-Mailer: SCO Shell Date: Sat, 3 Jul 1999 10:08:43 -0700 (PDT) Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following messages appear on the display as my FreeBSD machine is booting. The spelling of "failed" is totally incorrect, and it would sure be nice to see the spelling corrected on a future release. To: paz@mail.qcislands.net Subject: BUG boot-time messages From: Charlie Root Date: Sat, 3 Jul 1999 10:01:34 -0700 -- Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x330 Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x334 Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x230 Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x234 Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x130 Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x134 ^^^^^^^ -- Jim Pazarena mailto:paz@qcislands.net http://www.qcislands.net/paz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 10: 6:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 665E514ECE for ; Sat, 3 Jul 1999 10:06:44 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA04359; Sat, 3 Jul 1999 10:06:41 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377E431F.D04C3BE9@gorean.org> Date: Sat, 03 Jul 1999 10:06:40 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: hackers@freebsd.org Subject: Re: bpfilter -> bpf patches [LONG] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > [Bcc:ed to net, committers; please follow up on hackers] > > Attached are patches for renaming 'pseudo-device bpfilter' to > 'peudo-device bpf', courtesy of glimpse(1) and ed(1). LINT and GENERIC > build fine with these patches; I haven't tried to run a kernel built > with them, though. Also, although I caught and corrected a few spacing > nits caused by chopping off five letters, there may be some I didn't > catch. > > If no-one objects, I'll commit this to -CURRENT in a few days. Forgive me if this is a stupid question, but are there any circumstances where naming the kernel include file "bpf.h" would conflict with /usr/include/net/bpf.h? In any case, this is a long overdue, and welcome change. Thank you. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 10:13:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1BB2C14C0E for ; Sat, 3 Jul 1999 10:12:50 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA07738 for freebsd-hackers@FreeBSD.ORG; Sat, 3 Jul 1999 19:12:48 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1D002885F; Sat, 3 Jul 1999 17:45:00 +0200 (CEST) (envelope-from roberto) Date: Sat, 3 Jul 1999 17:44:59 +0200 From: Ollivier Robert To: "FreeBSD Hackers' list" Subject: USB floppy & booting Message-ID: <19990703174459.A57506@keltia.freenix.fr> Mail-Followup-To: FreeBSD Hackers' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5431 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we support booting from USB floppies ? I plan to buy one of the new VAIOs (probably the Z505S with Celeron/333 + 64 MB + 12.1" screen) and it seems to come with an USB floppy (as opposed to the probably-IDE of former models). They've apparently ditched both the PS/2 mouse and the IDE floppy and moved to 2x USB ports... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 10:31:50 1999 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 BAA9F1509D for ; Sat, 3 Jul 1999 10:28:40 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA17426; Sat, 3 Jul 1999 13:24:07 -0400 (EDT) Message-Id: <199907031724.NAA17426@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 03 Jul 1999 12:20:35 -0400 To: Stan Shkolnyy From: Dennis Subject: Re: mbufs question/problem Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199906302150.RAA01512@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:10 PM 7/2/99 -0500, Stan Shkolnyy wrote: >On Wed, 30 Jun 1999, Dennis wrote: > >> >> I have a customer who has been experiencing "slow downs" with a freebsd >> router....they have substantially increased performance by reducing >> MINCLSIZE. I havent tracked the source, but im trying to hypothesize what >> it might be. On the surface I cant see any relationship since very few >> routines seem dependent on that value (m_devget() in particular, but I dont >> believe they are using any driver that use it). Is it possible that they >> are running out of small mbufs (they have NMBCLUSTERS set to a very high >> value)? >> >> Any ideas would be helpful. > >I have not noticed answers so far, so maybe their drivers copy mbufs very >often. AFAIK, "small" mbufs are indeed copied but "cluster" ones are not, so >when they forced the system to use more "cluster" mbufs, they got >substantial savings on copy operations. Well they are using Intel cards and our sync boards (of course our driver is binary so the change wouldnt effect our driver), and I dont see the fxp driver using small buffers. They are running bgp4...but I dont know what kind of buffers are used for routes. Dennis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 10:46:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C9EA15040 for ; Sat, 3 Jul 1999 10:45:59 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA09416; Sat, 3 Jul 1999 11:45:42 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377E4C45.522F3E78@softweyr.com> Date: Sat, 03 Jul 1999 11:45:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "G. Adam Stanislav" Cc: Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: <377DB95C.448E4227@softweyr.com> <19990703113140.B220@whizkidtech.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "G. Adam Stanislav" wrote: > > On Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > > You either are a hacker, or you are not. It is not something someone else > > > > can teach you. > > > > > > This deserves a FAQ entry. What an awesome response. > > > > But it's certainly NOT something that you just are, either. You have to > > have talent, but you also have to have experience. This is most often > > done by a mentor. > > If you have the innate curiosity mentioned in my message, you will obtain > experience whether you have a mentor or not. Experience is best obtained > by trying things. It cannot be imparted by anyone else (although, it can > be encouraged). And, in some cases, disasters averted. I think all of us here have seen a few graphic examples lately of what happens when the mentoring process doesn't work. I think being a hacker is a combination of talent, ethics, and experience. I've known talented and experienced programmers who weren't hackers, either because they didn't have the innate curiousity you mention or because they were ethically challenged and used their skills to steal, cheat, and destroy, which are *not* part of the hacker ethos. Hackers create, crackers steal and destroy. But I'm certain you new that. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 3 10:58: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 4572C15077 for ; Sat, 3 Jul 1999 10:56:41 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA36680; Sat, 3 Jul 1999 13:56:27 -0400 (EDT) Date: Sat, 3 Jul 1999 13:56:27 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Doug Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: bpfilter -> bpf patches [LONG] In-Reply-To: <377E431F.D04C3BE9@gorean.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 Sat, 3 Jul 1999, Doug wrote: > Dag-Erling Smorgrav wrote: > > > > [Bcc:ed to net, committers; please follow up on hackers] > > > > Attached are patches for renaming 'pseudo-device bpfilter' to > > 'peudo-device bpf', courtesy of glimpse(1) and ed(1). LINT and GENERIC > > build fine with these patches; I haven't tried to run a kernel built > > with them, though. Also, although I caught and corrected a few spacing > > nits caused by chopping off five letters, there may be some I didn't > > catch. > > > > If no-one objects, I'll commit this to -CURRENT in a few days. > > Forgive me if this is a stupid question, but are there any circumstances > where naming the kernel include file "bpf.h" would conflict with > /usr/include/net/bpf.h? > > In any case, this is a long overdue, and welcome change. Thank you. :) > > Doug How would that conflict? "bpf.h" is a local include, so it's not the same include path set. Plus, it would only be included as if -I/sys/net. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 10:58: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id A032315096; Sat, 3 Jul 1999 10:57:19 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id UAA01702; Sat, 3 Jul 1999 20:57:16 +0300 (EEST) (envelope-from ru) Date: Sat, 3 Jul 1999 20:57:16 +0300 From: Ruslan Ermilov To: joerg@FreeBSD.org Cc: FreeBSD Hackers Subject: [PATCH] Preprocessor support for ipfw Message-ID: <19990703205716.A98500@relay.ucb.crimea.ua> Mail-Followup-To: joerg@FreeBSD.org, FreeBSD Hackers Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=Kj7319i9nmIyA2yE X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Hi! There is one problem with ``preprocessor support for ipfw''. relay# ls -l 100 ls: 100: No such file or directory relay# ipfw list 100 00100 allow ip from any to any via lo0 relay# touch 100 relay# ipfw list 100 ipfw: error: extraneous filename arguments [...] Please review the attached patch. Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: ipfw.8 =================================================================== RCS file: /usr/FreeBSD-CVS/src/sbin/ipfw/ipfw.8,v retrieving revision 1.54 diff -c -r1.54 ipfw.8 *** ipfw.8 1999/06/19 18:43:18 1.54 --- ipfw.8 1999/07/03 17:35:18 *************** *** 15,21 **** .Op Fl D Ar macro Ns Op Ns =value .Op Fl U Ar macro .Oc ! .Ar file .Nm ipfw .Oo .Fl f --- 15,21 ---- .Op Fl D Ar macro Ns Op Ns =value .Op Fl U Ar macro .Oc ! .Fl F Ar file .Nm ipfw .Oo .Fl f Index: ipfw.c =================================================================== RCS file: /usr/FreeBSD-CVS/src/sbin/ipfw/ipfw.c,v retrieving revision 1.71 diff -c -r1.71 ipfw.c *** ipfw.c 1999/06/19 18:43:15 1.71 --- ipfw.c 1999/07/03 17:35:18 *************** *** 58,65 **** #include #include - int lineno = -1; - int s; /* main RAW socket */ int do_resolv=0; /* Would try to resolve all */ int do_acct=0; /* Show packet/byte count */ --- 58,63 ---- *************** *** 1549,1556 **** #define WHITESP " \t\f\v\n\r" char buf[BUFSIZ]; char *a, *p, *args[MAX_ARGS], *cmd = NULL; ! char linename[10]; ! int i, c, qflag, pflag, status; FILE *f = NULL; pid_t preproc = 0; --- 1547,1556 ---- #define WHITESP " \t\f\v\n\r" char buf[BUFSIZ]; char *a, *p, *args[MAX_ARGS], *cmd = NULL; ! char linename[11]; ! int i = 0, c, qflag = 0, pflag = 0, status; ! int lineno = 0; ! char *file = NULL; FILE *f = NULL; pid_t preproc = 0; *************** *** 1558,1613 **** if ( s < 0 ) err(EX_UNAVAILABLE, "socket"); ! setbuf(stdout,0); ! if (ac > 1 && access(av[ac - 1], R_OK) == 0) { ! qflag = pflag = i = 0; ! lineno = 0; ! ! while ((c = getopt(ac, av, "D:U:p:q")) != -1) ! switch(c) { ! case 'D': ! if (!pflag) ! errx(EX_USAGE, "-D requires -p"); ! if (i > MAX_ARGS - 2) ! errx(EX_USAGE, ! "too many -D or -U options"); ! args[i++] = "-D"; ! args[i++] = optarg; ! break; ! case 'U': ! if (!pflag) ! errx(EX_USAGE, "-U requires -p"); ! if (i > MAX_ARGS - 2) ! errx(EX_USAGE, ! "too many -D or -U options"); ! args[i++] = "-U"; ! args[i++] = optarg; ! break; ! case 'p': ! pflag = 1; ! cmd = optarg; ! args[0] = cmd; ! i = 1; ! break; ! case 'q': ! qflag = 1; ! break; ! default: ! show_usage(NULL); ! } ! av += optind; ! ac -= optind; ! if (ac != 1) show_usage("extraneous filename arguments"); ! if ((f = fopen(av[0], "r")) == NULL) ! err(EX_UNAVAILABLE, "fopen: %s", av[0]); if (pflag) { /* pipe through preprocessor (cpp or m4) */ --- 1558,1614 ---- if ( s < 0 ) err(EX_UNAVAILABLE, "socket"); ! setbuf(stdout, NULL); ! while ((c = getopt(ac, av, "F:D:U:p:q")) != -1) ! switch(c) { ! case 'F': ! if (file) ! errx(EX_USAGE, "only one -F allowed"); ! file = optarg; ! break; ! case 'D': ! if (!pflag) ! errx(EX_USAGE, "-D requires -p"); ! if (i > MAX_ARGS - 2) ! errx(EX_USAGE, ! "too many -D or -U options"); ! args[i++] = "-D"; ! args[i++] = optarg; ! break; ! case 'U': ! if (!pflag) ! errx(EX_USAGE, "-U requires -p"); ! if (i > MAX_ARGS - 2) ! errx(EX_USAGE, ! "too many -D or -U options"); ! args[i++] = "-U"; ! args[i++] = optarg; ! break; ! case 'p': ! pflag = 1; ! cmd = optarg; ! args[0] = cmd; ! i = 1; ! break; ! case 'q': ! qflag = 1; ! break; ! ! default: ! show_usage(NULL); ! } ! if (file) { ! if (ac - optind) show_usage("extraneous filename arguments"); ! if ((f = fopen(file, "r")) == NULL) ! err(EX_UNAVAILABLE, "fopen: %s", file); if (pflag) { /* pipe through preprocessor (cpp or m4) */ *************** *** 1648,1655 **** } while (fgets(buf, BUFSIZ, f)) { ! lineno++; ! sprintf(linename, "Line %d", lineno); args[0] = linename; if (*buf == '#') --- 1649,1655 ---- } while (fgets(buf, BUFSIZ, f)) { ! snprintf(linename, sizeof(linename), "Line %d", ++lineno); args[0] = linename; if (*buf == '#') --Kj7319i9nmIyA2yE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 11: 1:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 2D597150AD for ; Sat, 3 Jul 1999 11:00:29 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA36785; Sat, 3 Jul 1999 14:00:31 -0400 (EDT) Date: Sat, 3 Jul 1999 14:00:31 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Jim Pazarena Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BUG boot-time messages 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 Sat, 3 Jul 1999, Jim Pazarena wrote: > The following messages appear on the display as my FreeBSD machine is > booting. > > The spelling of "failed" is totally incorrect, and it would sure be > nice to see the spelling corrected on a future release. I don't see that in FreeBSD's HEAD, RELENG_2_2, or RELENG_3 branches. > > To: paz@mail.qcislands.net > Subject: BUG boot-time messages > From: Charlie Root > Date: Sat, 3 Jul 1999 10:01:34 -0700 > -- > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x330 > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x334 > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x230 > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x234 > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x130 > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x134 > ^^^^^^^ > > -- > Jim Pazarena mailto:paz@qcislands.net > http://www.qcislands.net/paz > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 11: 4: 7 1999 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 06CA61517B for ; Sat, 3 Jul 1999 11:03:35 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id UAA59043; Sat, 3 Jul 1999 20:03:28 +0200 (CEST) (envelope-from des) To: Doug Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: bpfilter -> bpf patches [LONG] References: <377E431F.D04C3BE9@gorean.org> From: Dag-Erling Smorgrav Date: 03 Jul 1999 20:03:27 +0200 In-Reply-To: Doug's message of "Sat, 03 Jul 1999 10:06:40 -0700" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug writes: > Forgive me if this is a stupid question, but are there any circumstances > where naming the kernel include file "bpf.h" would conflict with > /usr/include/net/bpf.h? I don't think so. The bpf.h created by config(8) resides in the compile directory and is only used there; the "real" bpf.h is in /sys/net/ (or /usr/include/net) and is only referred to as net/bpf.h. Besides, if there were any confusion, I wouldn't (shouldn't) have been able to build LINT and GENERIC with the patches. That said, thanks for asking - while looking into this matter I found another problem :) new patches will be available soon. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 11: 4:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2AD6C15077 for ; Sat, 3 Jul 1999 11:04:28 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id MAA09446; Sat, 3 Jul 1999 12:04:14 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377E509D.75F79D0E@softweyr.com> Date: Sat, 03 Jul 1999 12:04:13 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brian F. Feldman" Cc: Jonathan Lemon , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > > On Sat, 3 Jul 1999, Jonathan Lemon wrote: > > > On Jul 07, 1999 at 01:01:07AM -0400, Brian F. Feldman wrote: > > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > > > As for new code, use whichever you are comfortable with. Personally, I > > > > would recommend poll(), since it provides some added functionality over > > > > select() that makes for easier programming. > > > > > > poll() is a huge pain to use, which is why I recommend select(). > > > > Whichever you're comfortable with. poll() isn't a pain once you know > > how to use it, and it does bring additional benefits. > > I don't see how you can not find poll() a pain when compared to select(). It > requires so much set-up, much like (for instance) aio_write() as opposed to > write(). I suppose if you're masochistic, you won't mind doing that :) He wouldn't be a programmer unless masochistic. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 3 12: 8:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 0EA5C150D9 for ; Sat, 3 Jul 1999 12:07:47 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.114] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id A2BD85033C; Sat, 03 Jul 1999 16:21:33 -0300 Message-ID: <377E34F9.CA198CA5@tdnet.com.br> Date: Sat, 03 Jul 1999 16:06:17 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Login.conf (Whose problem is this) ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i am trying to get a login classes for my users, so i decided to edit /etc/login.conf. Among other, i have yma classes this way: shell:\ :maxproc=5:\ :tc=auth-default: Looking for auth-default, i saw the following: ## Authentication methods ## Note that these are disabled by default, and libutil must ## be rebuilt with LOGIN_CAP_AUTH defined to use them. # #auth-defaults:\ # :auth=krb_skey_or_passwd,passwd,kerberos,skey: # #auth-root-defaults:\ # :auth-login=krb_skey_or_passwd,passwd,kerberos,skey:\ # :auth-rlogin=krb_or_skey,kerberos,skey: # #auth-ftp-defaults:\ # :auth=skey_or_pwd,passwd,skey: # # Ok, so i need LOGIN_CAP_AUTH in libutil, i went to /usr/src/lib/libutil and changed, Makefile: From: # @(#)Makefile 8.1 (Berkeley) 6/4/93 LIB= util SHLIB_MAJOR= 2 SHLIB_MINOR= 2 CFLAGS+=-Wall -DLIBC_SCCS -I${.CURDIR} -I${.CURDIR}/../../sys #CFLAGS+=LOGIN_CAP_AUTH To: # @(#)Makefile 8.1 (Berkeley) 6/4/93 LIB= util SHLIB_MAJOR= 2 SHLIB_MINOR= 2 CFLAGS+=-Wall -DLIBC_SCCS -I${.CURDIR} -I${.CURDIR}/../../sys CFLAGS+=LOGIN_CAP_AUTH Here came the problem: myname# make cc -O -pipe -Wall -DLIBC_SCCS -I/usr/src/lib/libutil -I/usr/src/lib/libutil/../../sys LOGIN_CAP_AUTH -c /usr/src/lib/libutil/login.c -o login.o cc: LOGIN_CAP_AUTH: No such file or directory *** Error code 1 Stop. That's happened cause i turn on LOGIN_CAP_AUTH! My doubt is: Shouldn't it be -DLOGIN_CAP_AUTH? Is it right ? Can i use: # @(#)Makefile 8.1 (Berkeley) 6/4/93 LIB= util SHLIB_MAJOR= 2 SHLIB_MINOR= 2 CFLAGS+=-Wall -DLIBC_SCCS -I${.CURDIR} -I${.CURDIR}/../../sys CFLAGS+=-DLOGIN_CAP_AUTH Is that a FreeBSD error or my one? -- What about something different this year: Crash your FreeBSD box! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 12:16:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id BDDC01512A for ; Sat, 3 Jul 1999 12:16:14 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id VAA10541; Sat, 3 Jul 1999 21:16:04 +0200 (CEST) (envelope-from des) To: Dag-Erling Smorgrav Cc: Doug , Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: bpfilter -> bpf patches [LONG] References: <377E431F.D04C3BE9@gorean.org> Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 03 Jul 1999 21:16:03 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "03 Jul 1999 20:03:27 +0200" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > That said, thanks for asking - while looking into this matter I found > another problem :) new patches will be available soon. Nothing serious; a corrected patch is available on my freefall web page (http://www.freebsd.org/~des/software/) DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 12:16:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles534.castles.com [208.214.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 3ADE214DD2 for ; Sat, 3 Jul 1999 12:16:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01095; Sat, 3 Jul 1999 12:12:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907031912.MAA01095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: Graham Wheeler , Vince Vielhaber , Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Porting LILO to FreeBSD In-reply-to: Your message of "Sat, 03 Jul 1999 01:30:38 MDT." <199907030730.BAA23514@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Jul 1999 12:12:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <377CBE28.F3D4E15A@cdsec.com> Graham Wheeler writes: > : The only reason I even want to do this is that I still have a number > : of old DOS games that won't work under Win95. And dosemu and Wine > : just don't cut it either, unfortunately. > > I have a friend that wants to boot FreeBSD on his IDE drive, or Win95 > on his SCSI drive. No, it isn't an option to swap them, so the SCSI > drive winds up being 'D'. The only way he can boot Win95 is to > completely disable the IDE drive from the BIOS' point of view :-(. > > Would osbs solve this problem, or would he have to take a look at > LILO? Neither; he'll have to tell the BIOS that the drive's not there. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 12:17:45 1999 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 1578014DD2 for ; Sat, 3 Jul 1999 12:17:38 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA12868; Sat, 3 Jul 1999 13:17:33 -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 NAA28969; Sat, 3 Jul 1999 13:15:22 -0600 (MDT) Message-Id: <199907031915.NAA28969@harmony.village.org> To: Mike Smith Subject: Re: Porting LILO to FreeBSD Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Jul 1999 12:12:01 PDT." <199907031912.MAA01095@dingo.cdrom.com> References: <199907031912.MAA01095@dingo.cdrom.com> Date: Sat, 03 Jul 1999 13:15:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199907031912.MAA01095@dingo.cdrom.com> Mike Smith writes: : Neither; he'll have to tell the BIOS that the drive's not there. That's what he's doing right now... He doesn't want to keep doing this since it is such a PITA. However, other posters in the thread gave me enough hints that I think that I can help him make it work. LILO's trick of installing a small translating shim on INT 13 may be just the ticket... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 12:18:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 4F28414DD2 for ; Sat, 3 Jul 1999 12:18:14 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id PAA10651; Sat, 3 Jul 1999 15:18:09 -0400 (EDT) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA17777; Sat, 3 Jul 1999 15:18:08 -0400 (EDT) Received: from localhost by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA17773; Sat, 3 Jul 1999 15:18:08 -0400 (EDT) X-Authentication-Warning: rac9.wam.umd.edu: howardjp owned process doing -bs Date: Sat, 3 Jul 1999 15:18:07 -0400 (EDT) From: Jamie Howard To: freebsd-hackers@freebsd.org, tech-userlevel@netbsd.org, tech@openbsd.org Subject: Repalcement for grep(1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have used FreeBSD for a couple years now. It is the only OS on my desktop. I have learnt many things from its source. I felt it was time to give something back. A few minutes later I decided to offer it to all BSDs. I also will offer it to the DaemonLinux group, Apple, the Darwin group, and Tenon Systems, after public acceptence. If there is anyone else out there using a BSD base and GNU grep, they can have it too. Looking aroud, I thought it would be great to try to replace one of the GNU utilites included in the base with a version which is freely redistributable. I figured a compiler was beyond me, but a a couple of the simpler utilities caught my eye. Grep was first. All of the code is original except for binary.c. It is used with the -a option to prevent searching binary files. binary.c is extricated from less-332's binary checking code. I was just that lazy. I made the version in FreeBSD 4.0 my target except for -A num, -B num, -C, -num, and -Z. These are not required by the Single Unix Specification or POSIX and I felt they would bloat my code too significantly. I added the -o option from 4.4BSD-Lite2's implementation of egrep. I also stole it's man page. One of the primary concerns was simplicity. Looking through the code, you should nobody should have any difficuly understanding the code. Regex does all the heavy work. The object code is about 16% of the size of GNU grep. I also do not use mmap(), I treat the file as a simple stream instead. My code is also a bit slower on larger files, but a bit faster on smaller files. Sometimes I am an order of magnitude slower. I am never that much faster. I think not using mmap is the reason, but I do not know for certain. Now, I am having a problem though. I cannot figure out how to implement -w and -x. For -x, I tried modifying the regular expression (foo) into ^(foo)$ before compiling, but that did not work. I intended to do something similar with -w. Anyway, I am probably missing the obvious, but does anyone have any ideas regarding how I should implement -w and -x? If anyone can help with the -w and -x problems, would like to test, or has any other comments, let me know. I'd also like advice on the speed issue. Also, since I am at it, if you want anything added, lay it on me, either code or ideas. :) The source code can be found at ftp://ftp.wam.umd.edu/pub/howardjp/grep-0.2.tar.gz The source was written and tested on a FreeBSD 3.2 system. I have also compiled under BSDi 3.1. It should work on any BSD and most any Unix. The Makefile is written in the style of the rest of the FreeBSD utilites so that it can be dropped right into /usr/src/usr.bin someday. Only minor modifications should be needed for BSDi, NetBSD, and OpenBSD. I have not built this on either NetBSD or OpenBSD but expect no problems. If anyone does have problems please let me know. Fixes are even better. Thank you everyone, Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 12:30:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r34.bfm.org [208.18.213.130]) by hub.freebsd.org (Postfix) with ESMTP id 8C69A14BF9 for ; Sat, 3 Jul 1999 12:29:39 -0700 (PDT) (envelope-from adam@whizkidtech.net) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id OAA00250; Sat, 3 Jul 1999 14:28:59 -0500 (CDT) (envelope-from adam) Date: Sat, 3 Jul 1999 14:28:28 -0500 From: "G. Adam Stanislav" To: Wes Peters Cc: Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? Message-ID: <19990703142828.A236@whizkidtech.net> References: <377DB95C.448E4227@softweyr.com> <19990703113140.B220@whizkidtech.net> <377E4C45.522F3E78@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <377E4C45.522F3E78@softweyr.com>; from Wes Peters on Sat, Jul 03, 1999 at 11:45:41AM -0600 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ 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 Sat, Jul 03, 1999 at 11:45:41AM -0600, Wes Peters wrote: > And, in some cases, disasters averted. I think all of us here have seen > a few graphic examples lately of what happens when the mentoring process > doesn't work. Sadly, mentoring can occasionaly hurt the mentor, too. I used to work for a company whose only programmer quit. They made testing machines controlled by a computer. All of their software was written in Turbo Pascal under MS DOS, and very poorly at that. I was hired along with a young man who had just graduated from college. The first thing I did was convince the boss to toss Turbo Pascal and switch to a combination of C and assembly language. The second thing I had to do was convince him not to fire the young man. He majored in physics and had a few programming classes which gave him the false impression he could program computers. He was completely lost. The boss wanted to fire him because "we don't run a charity here." I thought the young man was intelligent and could learn. I helped him a lot, taught him many tricks. I think I turned him into a fairly decent programmer (not a hacker, mind you, because programming was a job to him, not a passion). Two years later I was "laid off." The boss figured he no longer needed both of us, and decided to keep the younger one because he did not have to pay him as much as me. The story had a happy ending after all: When the young man saw what the boss did to me, within a few months he got a job with another company and quit. So I think I did teach him well. :-) > I think being a hacker is a combination of talent, ethics, and experience. That's a good way of putting it. > I've known talented and experienced programmers who weren't hackers, > either because they didn't have the innate curiousity you mention or > because they were ethically challenged and used their skills to steal, > cheat, and destroy, which are *not* part of the hacker ethos. Hackers > create, crackers steal and destroy. Agreed. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 13: 2:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 06B8D1514A for ; Sat, 3 Jul 1999 13:02:46 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-158.skylink.it [194.185.55.158]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA32017; Sat, 3 Jul 1999 22:01:54 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA08780; Sat, 3 Jul 1999 21:56:33 +0200 (CEST) Date: Sat, 3 Jul 1999 21:56:33 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Ollivier Robert Cc: "FreeBSD Hackers' list" Subject: Re: USB floppy & booting In-Reply-To: <19990703174459.A57506@keltia.freenix.fr> 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 Booting maybe (through BIOS support), but we do not support USB floppies from Y-E data yet at a later stage. I am working on support for it though. Nick On Sat, 3 Jul 1999, Ollivier Robert wrote: > Do we support booting from USB floppies ? I plan to buy one of the new VAIOs > (probably the Z505S with Celeron/333 + 64 MB + 12.1" screen) and it seems to > come with an USB floppy (as opposed to the probably-IDE of former models). > > They've apparently ditched both the PS/2 mouse and the IDE floppy and moved to > 2x USB ports... > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 13:10: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5FEA514C0C for ; Sat, 3 Jul 1999 13:09:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA66518; Sat, 3 Jul 1999 14:09:22 -0600 (MDT) (envelope-from ken) Message-Id: <199907032009.OAA66518@panzer.kdm.org> Subject: Re: BUG boot-time messages In-Reply-To: from "Brian F. Feldman" at "Jul 3, 1999 02:00:31 pm" To: green@unixhelp.org (Brian F. Feldman) Date: Sat, 3 Jul 1999 14:09:22 -0600 (MDT) Cc: paz@qcislands.net (Jim Pazarena), freebsd-hackers@FreeBSD.ORG From: "Kenneth D. Merry" 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 Brian F. Feldman wrote... > On Sat, 3 Jul 1999, Jim Pazarena wrote: > > > The following messages appear on the display as my FreeBSD machine is > > booting. > > > > The spelling of "failed" is totally incorrect, and it would sure be > > nice to see the spelling corrected on a future release. > > I don't see that in FreeBSD's HEAD, RELENG_2_2, or RELENG_3 branches. > > > > > To: paz@mail.qcislands.net > > Subject: BUG boot-time messages > > From: Charlie Root > > Date: Sat, 3 Jul 1999 10:01:34 -0700 > > -- > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x330 > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x334 > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x230 > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x234 > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x130 > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x134 > > ^^^^^^^ > > It was fixed in -current in April by phk, and merged to -stable by Justin in May. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 13:14:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8927615073 for ; Sat, 3 Jul 1999 13:14:19 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id QAA38844; Sat, 3 Jul 1999 16:14:19 -0400 (EDT) Date: Sat, 3 Jul 1999 16:14:19 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Kenneth D. Merry" Cc: Jim Pazarena , freebsd-hackers@FreeBSD.ORG Subject: Re: BUG boot-time messages In-Reply-To: <199907032009.OAA66518@panzer.kdm.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 Sat, 3 Jul 1999, Kenneth D. Merry wrote: > Brian F. Feldman wrote... > > On Sat, 3 Jul 1999, Jim Pazarena wrote: > > > > > The following messages appear on the display as my FreeBSD machine is > > > booting. > > > > > > The spelling of "failed" is totally incorrect, and it would sure be > > > nice to see the spelling corrected on a future release. > > > > I don't see that in FreeBSD's HEAD, RELENG_2_2, or RELENG_3 branches. > > > > > > > > To: paz@mail.qcislands.net > > > Subject: BUG boot-time messages > > > From: Charlie Root > > > Date: Sat, 3 Jul 1999 10:01:34 -0700 > > > -- > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x330 > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x334 > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x230 > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x234 > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x130 > > > Jul 3 03:53:46 ns2 /kernel: bt_isa_probe: Probe failled for card at 0x134 > > > ^^^^^^^ > > > > > It was fixed in -current in April by phk, and merged to -stable by Justin > in May. > Good reason for me not to see it ;) > Ken > -- > Kenneth Merry > ken@plutotech.com > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 13:25:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pangeatech.com (pangeatech-151.pangeatech.primenet.com [207.218.87.151]) by hub.freebsd.org (Postfix) with ESMTP id AD9C815073 for ; Sat, 3 Jul 1999 13:25:15 -0700 (PDT) (envelope-from jkn33@pangeatech.com) Received: from [207.218.93.158] by mail.pangeatech.com (NTMail 4.30.0010/NU8172.00.ea3d9017) with ESMTP id bjktaaaa for ; Sat, 3 Jul 1999 13:21:15 -0700 Message-ID: <377E71F6.8877ED47@pangeatech.com> Date: Sat, 03 Jul 1999 13:26:30 -0700 From: Janie Dykes Reply-To: jkn33@pangeatech.com X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters Cc: "G. Adam Stanislav" , Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? References: <377DB95C.448E4227@softweyr.com> <19990703113140.B220@whizkidtech.net> <377E4C45.522F3E78@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When scouring through the threads - this one in particular caught my attention. In my experience, which is still very new, I think all of you make excellent points. For the most part, the novice/average person, believes that hackers are malicious, destructive individuals. A huge number of computer users are misled and misinformed about the true definition of the term 'hacker'. This is unfortunate - if those people could spend some time reading the brilliant posts to this list, they might realize that we are not all 16 year olds, hiding behind the glow of the monitor, reading their email and stealing their passwords and credit card information and posting it on IRC. I have a point. :] The first time I experienced that curiosity - I got a little carried away. eh hem I learned that my skills, which included aptness and dexterity, had been misdirected. Upon my awakening, I was blessed with my mentor. He challenged me to use my skills productively. In retrospect, I learned [the hard way] and gained some experience with some help from my mentor [some of you may know Peter Mountain - BRU2000]. All in all, there are many contributing factors to becoming a hacker. I rarely post to this list - so I hope that my lengthy post doesn't offend. So on that note - I will continue observing the minds at work. Thanks for the opportunity to post - Janie Dykes Wes Peters wrote: > > "G. Adam Stanislav" wrote: > > > > On Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > > > You either are a hacker, or you are not. It is not something someone else > > > > > can teach you. > > > > > > > > This deserves a FAQ entry. What an awesome response. > > > > > > But it's certainly NOT something that you just are, either. You have to > > > have talent, but you also have to have experience. This is most often > > > done by a mentor. > > > > If you have the innate curiosity mentioned in my message, you will obtain > > experience whether you have a mentor or not. Experience is best obtained > > by trying things. It cannot be imparted by anyone else (although, it can > > be encouraged). > > And, in some cases, disasters averted. I think all of us here have seen > a few graphic examples lately of what happens when the mentoring process > doesn't work. > > I think being a hacker is a combination of talent, ethics, and experience. > I've known talented and experienced programmers who weren't hackers, > either because they didn't have the innate curiousity you mention or > because they were ethically challenged and used their skills to steal, > cheat, and destroy, which are *not* part of the hacker ethos. Hackers > create, crackers steal and destroy. > > But I'm certain you new that. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://softweyr.com/ wes@softweyr.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 13:26:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 05D7015171 for ; Sat, 3 Jul 1999 13:26:35 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id NAA94092; Sat, 3 Jul 1999 13:26:26 -0700 (PDT) (envelope-from mph) Date: Sat, 3 Jul 1999 13:26:26 -0700 From: Matthew Hunt To: "Brian F. Feldman" Cc: Jim Pazarena , freebsd-hackers@FreeBSD.ORG Subject: Re: BUG boot-time messages Message-ID: <19990703132626.C86487@wopr.caltech.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Sat, Jul 03, 1999 at 02:00:31PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 03, 1999 at 02:00:31PM -0400, Brian F. Feldman wrote: > > The spelling of "failed" is totally incorrect, and it would sure be > > nice to see the spelling corrected on a future release. > > I don't see that in FreeBSD's HEAD, RELENG_2_2, or RELENG_3 branches. revision 1.7 date: 1999/04/06 21:15:18; author: phk; state: Exp; lines: +2 -2 failled spell-check revision 1.5.2.2 date: 1999/05/23 18:59:50; author: gibbs; state: Exp; lines: +2 -2 failled->failed Submitted by: emily@ucdavis.edu -- Matthew Hunt * Inertia is a property http://www.pobox.com/~mph/ * of matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 14: 0:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duh.org (www.duh.org [207.30.95.212]) by hub.freebsd.org (Postfix) with ESMTP id BD2F114CE2 for ; Sat, 3 Jul 1999 14:00:49 -0700 (PDT) (envelope-from tv@pobox.com) Received: from localhost (IDENT:tv@localhost [127.0.0.1]) by duh.org (8.9.3/8.9.3/3.1.1) with ESMTP id RAA21567Sat, 3 Jul 1999 17:00:41 -0400 (EDT) Date: Sat, 3 Jul 1999 17:00:41 -0400 (EDT) From: Todd Vierling X-Sender: tv@server.duh.org To: Jamie Howard Cc: freebsd-hackers@freebsd.org, tech-userlevel@netbsd.org, tech@openbsd.org Subject: Re: Repalcement for grep(1) 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 Sat, 3 Jul 1999, Jamie Howard wrote: : I also do not use mmap(), I treat the file as a simple stream : instead. My code is also a bit slower on larger files, but a bit faster : on smaller files. Sometimes I am an order of magnitude slower. I am : never that much faster. I think not using mmap is the reason, but I do : not know for certain. After the unified buffer cache modifications happen in the NetBSD kernel, the difference will be much less noticeable. : Now, I am having a problem though. I cannot figure out how to implement : -w and -x. For -x, I tried modifying the regular expression (foo) into : ^(foo)$ before compiling, but that did not work. I intended to do : something similar with -w. Anyway, I am probably missing the obvious, but : does anyone have any ideas regarding how I should implement -w and -x? Hm. Adding ^ and $ should work, provided you don't specify either REG_NOTBOL or REG_NOTEOL. (I assume that (foo) above, including the parens, is the RE. With the parens, it depends whether you're using standard REs or extended REs. :) Thatnks for this work ... I'll leave it to another soul to do something with it in NetBSD. -- -- Todd Vierling (tv@pobox.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 14:28:20 1999 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 D83FE151F5 for ; Sat, 3 Jul 1999 14:26:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA13336 for ; Sat, 3 Jul 1999 15:26:51 -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 PAA33313 for ; Sat, 3 Jul 1999 15:24:40 -0600 (MDT) Message-Id: <199907032124.PAA33313@harmony.village.org> To: hackers@freebsd.org Subject: The busspace modernization initiative. Date: Sat, 03 Jul 1999 15:24:40 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to update the bus-space routines to match more closely the NetBSD routines. The new-config project has already done this, so I've been moving their code into a relatively pure -current tree. I'm finding that there are many places that assume that bus_space_handle_t is the same thing as u_int or that bus_space_handles can be compared with !=. Some of this code I even wrote :-(. These strike me as unwise assumptions. Fortunately, it appears that there are only 4 files impacted (at least in my config, I've not tried GENERIC yet): ../../pci/bt_pci.c ../../i386/i386/nexus.c ../../i386/isa/aha_isa.c ../../pci/es1370.c It strikes me as unwise to make these assumptions, even if they should generally prove to be true. Comments? Warner P.S. Here's the diffs which are what I'm trying to do. Please feel free to comment on them. I'm unsure why there is a struct resource * in bus_space_handle_t in this implementation. I'll have to ask on the new-config lists, since if it isn't needed, it would best be removed... --- /home/imp/FreeBSD/src/sys/i386/include/bus.h Sat Jul 3 14:14:08 1999 +++ ./bus.h Mon Apr 26 00:11:18 1999 @@ -107,8 +101,11 @@ /* * Access methods for bus resources and address space. */ -typedef int bus_space_tag_t; -typedef u_int bus_space_handle_t; +typedef u_int bus_space_tag_t; +typedef struct { + u_int addr; + struct resource *resource; +} bus_space_handle_t; /* * Map a region of device bus space into CPU virtual address space. @@ -177,10 +174,10 @@ #if defined (_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) #endif - return (inb(handle + offset)); + return (inb(handle.addr + offset)); #endif #if defined (_I386_BUS_MEMIO_H_) - return (*(volatile u_int8_t *)(handle + offset)); + return (*(volatile u_int8_t *)(handle.addr + offset)); #endif } @@ -192,10 +189,10 @@ #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) #endif - return (inw(handle + offset)); + return (inw(handle.addr + offset)); #endif #if defined(_I386_BUS_MEMIO_H_) - return (*(volatile u_int16_t *)(handle + offset)); + return (*(volatile u_int16_t *)(handle.addr + offset)); #endif } @@ -207,10 +204,10 @@ #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) #endif - return (inl(handle + offset)); + return (inl(handle.addr + offset)); #endif #if defined(_I386_BUS_MEMIO_H_) - return (*(volatile u_int32_t *)(handle + offset)); + return (*(volatile u_int32_t *)(handle.addr + offset)); #endif } @@ -238,9 +235,10 @@ size_t count); static __inline void -bus_space_read_multi_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_multi_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int8_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -266,9 +264,10 @@ } static __inline void -bus_space_read_multi_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_multi_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int16_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -294,9 +293,10 @@ } static __inline void -bus_space_read_multi_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_multi_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int32_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -347,9 +347,10 @@ static __inline void -bus_space_read_region_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_region_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int8_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -384,9 +385,10 @@ } static __inline void -bus_space_read_region_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_region_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int16_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -421,9 +423,10 @@ } static __inline void -bus_space_read_region_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_read_region_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int32_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -479,9 +482,10 @@ bus_size_t offset, u_int32_t value); static __inline void -bus_space_write_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int8_t value) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -497,9 +501,10 @@ } static __inline void -bus_space_write_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int16_t value) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -515,9 +520,10 @@ } static __inline void -bus_space_write_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int32_t value) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -559,9 +565,10 @@ size_t count); static __inline void -bus_space_write_multi_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_multi_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int8_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -587,9 +594,10 @@ } static __inline void -bus_space_write_multi_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_multi_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int16_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -615,9 +623,10 @@ } static __inline void -bus_space_write_multi_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_multi_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int32_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -669,9 +678,10 @@ size_t count); static __inline void -bus_space_write_region_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_region_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int8_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -706,9 +716,10 @@ } static __inline void -bus_space_write_region_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_region_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int16_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -743,9 +754,10 @@ } static __inline void -bus_space_write_region_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_write_region_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, const u_int32_t *addr, size_t count) { + u_int bsh = bsht.addr; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) if (tag == I386_BUS_SPACE_IO) @@ -803,10 +815,10 @@ u_int32_t value, size_t count); static __inline void -bus_space_set_multi_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_multi_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int8_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -825,10 +837,10 @@ } static __inline void -bus_space_set_multi_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_multi_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int16_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -847,10 +859,10 @@ } static __inline void -bus_space_set_multi_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_multi_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int32_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -878,23 +890,23 @@ */ static __inline void bus_space_set_region_1(bus_space_tag_t tag, - bus_space_handle_t bsh, + bus_space_handle_t bsht, bus_size_t offset, u_int8_t value, size_t count); static __inline void bus_space_set_region_2(bus_space_tag_t tag, - bus_space_handle_t bsh, + bus_space_handle_t bsht, bus_size_t offset, u_int16_t value, size_t count); static __inline void bus_space_set_region_4(bus_space_tag_t tag, - bus_space_handle_t bsh, + bus_space_handle_t bsht, bus_size_t offset, u_int32_t value, size_t count); static __inline void -bus_space_set_region_1(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_region_1(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int8_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -913,10 +925,10 @@ } static __inline void -bus_space_set_region_2(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_region_2(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int16_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -935,10 +947,10 @@ } static __inline void -bus_space_set_region_4(bus_space_tag_t tag, bus_space_handle_t bsh, +bus_space_set_region_4(bus_space_tag_t tag, bus_space_handle_t bsht, bus_size_t offset, u_int32_t value, size_t count) { - bus_addr_t addr = bsh + offset; + bus_addr_t addr = bsht.addr + offset; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -966,30 +978,30 @@ */ static __inline void bus_space_copy_region_1(bus_space_tag_t tag, - bus_space_handle_t bsh1, + bus_space_handle_t bsht1, bus_size_t off1, - bus_space_handle_t bsh2, + bus_space_handle_t bsht2, bus_size_t off2, size_t count); static __inline void bus_space_copy_region_2(bus_space_tag_t tag, - bus_space_handle_t bsh1, + bus_space_handle_t bsht1, bus_size_t off1, - bus_space_handle_t bsh2, + bus_space_handle_t bsht2, bus_size_t off2, size_t count); static __inline void bus_space_copy_region_4(bus_space_tag_t tag, - bus_space_handle_t bsh1, + bus_space_handle_t bsht1, bus_size_t off1, - bus_space_handle_t bsh2, + bus_space_handle_t bsht2, bus_size_t off2, size_t count); static __inline void -bus_space_copy_region_1(bus_space_tag_t tag, bus_space_handle_t bsh1, - bus_size_t off1, bus_space_handle_t bsh2, +bus_space_copy_region_1(bus_space_tag_t tag, bus_space_handle_t bsht1, + bus_size_t off1, bus_space_handle_t bsht2, bus_size_t off2, size_t count) { - bus_addr_t addr1 = bsh1 + off1; - bus_addr_t addr2 = bsh2 + off2; + bus_addr_t addr1 = bsht1.addr + off1; + bus_addr_t addr2 = bsht2.addr + off2; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -1030,12 +1042,12 @@ } static __inline void -bus_space_copy_region_2(bus_space_tag_t tag, bus_space_handle_t bsh1, - bus_size_t off1, bus_space_handle_t bsh2, +bus_space_copy_region_2(bus_space_tag_t tag, bus_space_handle_t bsht1, + bus_size_t off1, bus_space_handle_t bsht2, bus_size_t off2, size_t count) { - bus_addr_t addr1 = bsh1 + off1; - bus_addr_t addr2 = bsh2 + off2; + bus_addr_t addr1 = bsht1.addr + off1; + bus_addr_t addr2 = bsht2.addr + off2; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) @@ -1076,12 +1088,12 @@ } static __inline void -bus_space_copy_region_4(bus_space_tag_t tag, bus_space_handle_t bsh1, - bus_size_t off1, bus_space_handle_t bsh2, +bus_space_copy_region_4(bus_space_tag_t tag, bus_space_handle_t bsht1, + bus_size_t off1, bus_space_handle_t bsht2, bus_size_t off2, size_t count) { - bus_addr_t addr1 = bsh1 + off1; - bus_addr_t addr2 = bsh2 + off2; + bus_addr_t addr1 = bsht1.addr + off1; + bus_addr_t addr2 = bsht2.addr + off2; #if defined(_I386_BUS_PIO_H_) #if defined(_I386_BUS_MEMIO_H_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 14:51: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 5493615044 for ; Sat, 3 Jul 1999 14:50:56 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA40489; Sat, 3 Jul 1999 17:50:39 -0400 (EDT) Date: Sat, 3 Jul 1999 17:50:38 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Janie Dykes Cc: Wes Peters , "G. Adam Stanislav" , Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? In-Reply-To: <377E71F6.8877ED47@pangeatech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Janie Dykes wrote: > When scouring through the threads - this one in particular caught my > attention. In my experience, which is still very new, I think all of > you make excellent points. For the most part, the novice/average > person, believes that hackers are malicious, destructive individuals. A > huge number of computer users are misled and misinformed about the true > definition of the term 'hacker'. This is unfortunate - if those people > could spend some time reading the brilliant posts to this list, they > might realize that we are not all 16 year olds, hiding behind the glow *cough* Care to explain that comment? > of the monitor, reading their email and stealing their passwords and > credit card information and posting it on IRC. I have a point. :] The > first time I experienced that curiosity - I got a little carried away. > eh hem I learned that my skills, which included aptness > and dexterity, had been misdirected. Upon my awakening, I was blessed > with my mentor. He challenged me to use my skills productively. In > retrospect, I learned [the hard way] and gained some experience with > some help from my mentor [some of you may know Peter Mountain - > BRU2000]. All in all, there are many contributing factors to becoming a > hacker. I rarely post to this list - so I hope that my lengthy post > doesn't offend. So on that note - I will continue observing the minds > at work. > > Thanks for the opportunity to post - > Janie Dykes > > > > Wes Peters wrote: > > > > "G. Adam Stanislav" wrote: > > > > > > On Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > > > > You either are a hacker, or you are not. It is not something someone else > > > > > > can teach you. > > > > > > > > > > This deserves a FAQ entry. What an awesome response. > > > > > > > > But it's certainly NOT something that you just are, either. You have to > > > > have talent, but you also have to have experience. This is most often > > > > done by a mentor. > > > > > > If you have the innate curiosity mentioned in my message, you will obtain > > > experience whether you have a mentor or not. Experience is best obtained > > > by trying things. It cannot be imparted by anyone else (although, it can > > > be encouraged). > > > > And, in some cases, disasters averted. I think all of us here have seen > > a few graphic examples lately of what happens when the mentoring process > > doesn't work. > > > > I think being a hacker is a combination of talent, ethics, and experience. > > I've known talented and experienced programmers who weren't hackers, > > either because they didn't have the innate curiousity you mention or > > because they were ethically challenged and used their skills to steal, > > cheat, and destroy, which are *not* part of the hacker ethos. Hackers > > create, crackers steal and destroy. > > > > But I'm certain you new that. ;^) > > > > -- > > "Where am I, and what am I doing in this handbasket?" > > > > Wes Peters Softweyr LLC > > http://softweyr.com/ wes@softweyr.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 14:54:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id EA5F715075 for ; Sat, 3 Jul 1999 14:54:32 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id PAA20279; Sat, 3 Jul 1999 15:54:32 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id PAA05219; Sat, 3 Jul 1999 15:54:31 -0600 (MDT) Date: Sat, 3 Jul 1999 15:54:30 -0600 From: Greg Skafte To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UMAX scsi scanner on adaptec 1542 Card Message-ID: <19990703155430.A5082@gras-varg.worldgate.com> References: <19990702110341.A24969@gras-varg.worldgate.com> <199907022052.OAA46204@harmony.village.org> <19990702170206.B25510@gras-varg.worldgate.com> <199907022322.RAA46803@harmony.village.org> <19990702181826.C25510@gras-varg.worldgate.com> <199907030022.SAA47103@harmony.village.org> <19990702183058.D25510@gras-varg.worldgate.com> <199907030034.SAA47172@harmony.village.org> <19990702184559.E25510@gras-varg.worldgate.com> <199907030442.WAA00317@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907030442.WAA00317@harmony.village.org>; from Warner Losh on Fri, Jul 02, 1999 at 10:42:20PM -0600 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tried it both with bios enabled and disabled .... I've even tried reseting to factory defaults, I enabled and disabled sync negotiation, I've also tried cutting the speed from 10 -> 5 -> 1.3 or what ever the slowest transfer rate wa Quoting Warner Losh (imp@harmony.village.org) On Subject: Re: UMAX scsi scanner on adaptec 1542 Card Date: Fri, Jul 02, 1999 at 10:42:20PM -0600 > In message <19990702184559.E25510@gras-varg.worldgate.com> Greg Skafte writes: > : THANKS man ..... > > A hunch. I just tried to bring up my 1542CF with the bios disabled in > -current and it blew chunks like you described. Is your BIOS > disabled? If so, can you enable it and see if that works? It should > work with the bios disabled, but I know how painful that can be... > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 16:24:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id C011D15277 for ; Sat, 3 Jul 1999 16:24:12 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id TAA18732 for ; Sat, 3 Jul 1999 19:29:35 -0400 (EDT) Date: Sat, 3 Jul 1999 18:29:34 -0500 (EST) From: Alfred Perlstein To: hackers@freebsd.org Subject: devices in sysctl MIB? 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 Just a suggestion, perhaps there should be a dev tree in sysctl with nodes for each device type then device. interesting applications for this: reporting on packets dropped/sent and such displaying connection status (duplex/100mb/10mb... etc) enabling/disabling power saving features dev.iface.fxp0.ipkts = 432523 dev.iface.fxp0.opkts = 432523 dev.iface.fxp0.linkspeed = 100 dev.iface.fxp0.linkmode = full-duplex dev.dsk.da0.tags = 32 .... sysctl -w dev.iface.fxp0.linkmode=half-duplex ? -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Win Telecom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 16:49:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id D106214DEA for ; Sat, 3 Jul 1999 16:49:36 -0700 (PDT) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere (ppp18353.on.bellglobal.com [206.172.130.33]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id TAA14717; Sat, 3 Jul 1999 19:52:38 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id TAA44920; Sat, 3 Jul 1999 19:47:00 -0400 (EDT) (envelope-from tim) Date: Sat, 3 Jul 1999 19:47:00 -0400 From: Tim Vanderhoek To: Janie Dykes Cc: Wes Peters , "G. Adam Stanislav" , Bill Fumerola , haodongpan@netease.com, freebsd-hackers@FreeBSD.org Subject: Re: how to start to be a hacker? Message-ID: <19990703194700.A44583@mad> References: <377DB95C.448E4227@softweyr.com> <19990703113140.B220@whizkidtech.net> <377E4C45.522F3E78@softweyr.com> <377E71F6.8877ED47@pangeatech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <377E71F6.8877ED47@pangeatech.com>; from Janie Dykes on Sat, Jul 03, 1999 at 01:26:30PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 03, 1999 at 01:26:30PM -0700, Janie Dykes wrote: > > you make excellent points. For the most part, the novice/average > person, believes that hackers are malicious, destructive individuals. A > huge number of computer users are misled and misinformed about the true > definition of the term 'hacker'. This is unfortunate - if those people I don't know. I'm not sure that's so true anymore as it once was. I've been bugged before by kids (hehe, from my peer group, that is) wanting to know what the best thing I'd ever done was. After giving some answer about some really insiduous batch files I'd written for DOS, I was rather disappointed to find-out they meant "what was the most illegal thing you've ever done". I didn't really give an answer to that, but I think many hackers have broken into a system or done something similar at some time (probably fewer of the younger ones since wide availability of real operating systems helps on this ticket). Not to let this become a passage of right or anything. A hacker, of course, is not going to concern themselves with what a hacker is, but others might. The tone of this thread seems to have been set by esr's little p/r definition of hacker. I'd like to declare at this time that a hacker is someone who sends me money in the mail. Upon these people I will bestow the title hacker. Anyways, like I said: I'm not sure your description of the average person's definition of "hacker" is so true anymore. The average person's definition is probably a little more true than esr's, if not nearly as articulate. PS: don't worry, you aren't expected to send much money these days anymore. PSS: Sending cash in the mail is illegal, don't do it. Canadian or American money orders only, please. > could spend some time reading the brilliant posts to this list, they > might realize that we are not all 16 year olds, hiding behind the glow Heh. Despite the -list name, this whole thread belongs on -chat. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 17:11:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 7A6FC153B7 for ; Sat, 3 Jul 1999 17:11:34 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id SAA10168; Sat, 3 Jul 1999 18:11:10 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <377EA69C.6729DB43@softweyr.com> Date: Sat, 03 Jul 1999 18:11:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brian F. Feldman" Cc: Janie Dykes , freebsd-hackers@freebsd.org Subject: Re: how to start to be a hacker? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > > On Sat, 3 Jul 1999, Janie Dykes wrote: > > > When scouring through the threads - this one in particular caught my > > attention. In my experience, which is still very new, I think all of > > you make excellent points. For the most part, the novice/average > > person, believes that hackers are malicious, destructive individuals. A > > huge number of computer users are misled and misinformed about the true > > definition of the term 'hacker'. This is unfortunate - if those people > > could spend some time reading the brilliant posts to this list, they > > might realize that we are not all 16 year olds, hiding behind the glow > > *cough* Care to explain that comment? Trust me, greenie, those of us who a FAR from 16 wish we weren't. ;^) You're obviously not the wastrel Janie is talking about here. THEY're all over at SlashDot calling me names. ;^) > > The > > first time I experienced that curiosity - I got a little carried away. > > eh hem I learned that my skills, which included aptness > > and dexterity, had been misdirected. Upon my awakening, I was blessed > > with my mentor. He challenged me to use my skills productively. One of the important aspects of being a hacker is discipline, both self-discipline and team discipline when working with others. Both are learned behavior for the typical hacker type; something you have to develop an admiration for before you are even willing to try it yourself. A certain amount of discretion is called for as well, which can ONLY be learned by experience. In the meantime, a good mentor can help by giving advice (and/or an occasional butt-kicking) to avoid doing something REALLY stupid. These two traits are certainly not unique to hacking, that's why mentoring is a concept as old as the children of Adam and Eve. In fact, I've found it to be MUCH more important in other occupations, like motorcycling, sailing, and chemistry. ;^) > > In > > retrospect, I learned [the hard way] and gained some experience with Preferably without losing any body parts? > > some help from my mentor [some of you may know Peter Mountain - > > BRU2000]. All in all, there are many contributing factors to becoming a > > hacker. I rarely post to this list - so I hope that my lengthy post > > doesn't offend. So on that note - I will continue observing the minds > > at work. No problem, you're always welcome. Do try to keep the quoting to a minimum. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 3 17:28:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8ADED14C16; Sat, 3 Jul 1999 17:28:52 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA24976; Sat, 3 Jul 1999 17:28:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA06444; Sat, 3 Jul 1999 17:28:51 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 03 Jul 1999 17:28:51 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: Pictures from USENIX Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I put a handful of pictures from this year's USENIX conference at . John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 18:54:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 276ED14D0C for ; Sat, 3 Jul 1999 18:54:40 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA18884; Sun, 4 Jul 1999 11:24:37 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA06978; Sun, 4 Jul 1999 11:24:27 +0930 (CST) Date: Sun, 4 Jul 1999 11:24:27 +0930 From: Greg Lehey To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: Pictures from USENIX Message-ID: <19990704112426.J709@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from John Polstra on Sat, Jul 03, 1999 at 05:28:51PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 17:28:51 -0700, John Polstra wrote: > I put a handful of pictures from this year's USENIX conference at > . Hey, they're some of the best I've seen of USENIX. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 18:57:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8566D14D0C for ; Sat, 3 Jul 1999 18:57:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA25099; Sat, 3 Jul 1999 18:57:07 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA06552; Sat, 3 Jul 1999 18:57:06 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 3 Jul 1999 18:57:06 -0700 (PDT) Message-Id: <199907040157.SAA06552@vashon.polstra.com> To: kernel@tdnet.com.br Subject: Re: Login.conf (Whose problem is this) ? In-Reply-To: <377E34F9.CA198CA5@tdnet.com.br> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <377E34F9.CA198CA5@tdnet.com.br>, Gustavo V G C Rios wrote: > i am trying to get a login classes for my users, so i decided to edit > /etc/login.conf. > > Among other, i have yma classes this way: > > > shell:\ > :maxproc=5:\ > :tc=auth-default: > > > Looking for auth-default, i saw the following: > > ## Authentication methods > ## Note that these are disabled by default, and libutil must > ## be rebuilt with LOGIN_CAP_AUTH defined to use them. This stuff is old and obsolete. LOGIN_CAP_AUTH isn't supported any more. (It never was fully supported, actually.) Don't use it. > That's happened cause i turn on LOGIN_CAP_AUTH! > My doubt is: Shouldn't it be -DLOGIN_CAP_AUTH? Yes, of course. That's what "with LOGIN_CAP_AUTH defined" means. But it's broken, so don't bother. If you want login classes all you need to do is "vipw" and insert the correct class in the class field. (See passwd(5) for details.) If you want to create a new class, just edit it into your login.conf file and then run cap_mkdb as instructed in the comment at the top of that file. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 19: 4: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 829C614F51 for ; Sat, 3 Jul 1999 19:04:01 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id WAA25635; Sat, 3 Jul 1999 22:09:45 -0400 (EDT) Date: Sat, 3 Jul 1999 22:09:45 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: devices in sysctl MIB? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would certainly welcome such info... The info in the /proc filesystem in Linux is certainly nice. (One of the few things that is!). -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Sat, 3 Jul 1999, Alfred Perlstein wrote: > > Just a suggestion, perhaps there should be a dev tree in > sysctl with nodes for each device type then device. > > interesting applications for this: > > reporting on packets dropped/sent and such > displaying connection status (duplex/100mb/10mb... etc) > enabling/disabling power saving features > > dev.iface.fxp0.ipkts = 432523 > dev.iface.fxp0.opkts = 432523 > dev.iface.fxp0.linkspeed = 100 > dev.iface.fxp0.linkmode = full-duplex > dev.dsk.da0.tags = 32 > .... > > sysctl -w dev.iface.fxp0.linkmode=half-duplex > > ? > > -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] > systems administrator and programmer > Win Telecom - http://www.wintelcom.net/ > > > > 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 Jul 3 19:14:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 811A91520D for ; Sat, 3 Jul 1999 19:14:12 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA04765 for freebsd-hackers@FreeBSD.ORG; Sun, 4 Jul 1999 04:14:09 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 2316A885F; Sun, 4 Jul 1999 00:40:58 +0200 (CEST) (envelope-from roberto) Date: Sun, 4 Jul 1999 00:40:57 +0200 From: Ollivier Robert To: "FreeBSD Hackers' list" Subject: Re: USB floppy & booting Message-ID: <19990704004057.A60235@keltia.freenix.fr> Mail-Followup-To: FreeBSD Hackers' list References: <19990703174459.A57506@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Nick Hibma on Sat, Jul 03, 1999 at 09:56:33PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5431 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nick Hibma: > Booting maybe (through BIOS support), but we do not support USB floppies > from Y-E data yet at a later stage. I don't really care about it afterwards but I'll probably need to at least boot the installation floppy :-) > I am working on support for it though. Thanks ! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 19:57:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 3DC2414ED1 for ; Sat, 3 Jul 1999 19:57:06 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip145.houston3.tx.pub-ip.psi.net [38.12.169.145]) by leap.innerx.net (Postfix) with ESMTP id 64819372A5; Sat, 3 Jul 1999 22:56:54 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA86468; Sat, 3 Jul 1999 21:56:03 -0500 (CDT) (envelope-from chris) Date: Sat, 3 Jul 1999 21:56:02 -0500 From: Chris Costello To: Marc Nicholas Cc: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: devices in sysctl MIB? Message-ID: <19990703215602.C86035@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Marc Nicholas on Sat, Jul 03, 1999 at 10:09:45PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 3, 1999, Marc Nicholas wrote: > I would certainly welcome such info... > > The info in the /proc filesystem in Linux is certainly nice. (One of the > few things that is!). Nice, but misplaced. What does PCI/system version/etc have to do with running processes, exactly? > -marc -- Chris Costello Backups? We doan *NEED* no steenking baX%^~,VbKx NO CARRIER To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 20:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.ingsala.unal.edu.co (ohm.ingsala.unal.edu.co [168.176.15.18]) by hub.freebsd.org (Postfix) with ESMTP id AEC0214D39 for ; Sat, 3 Jul 1999 20:26:46 -0700 (PDT) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co (unalmodem09.usc.unal.edu.co [168.176.3.39]) by ohm.ingsala.unal.edu.co (8.8.5/8.8.5) with ESMTP id WAA25068 for ; Sat, 3 Jul 1999 22:29:39 -0500 (COT) Message-ID: <377EA51C.20DCABA6@bachue.usc.unal.edu.co> Date: Sat, 03 Jul 1999 19:04:44 -0500 From: "Pedro F. Giffuni" Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.1-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: Do we need GNU readline ?? 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 building a library covered by the LGPL when I found this jewel under readline/README: _____________ This is a line-editing library. It can be linked into almost any program to provide command-line editing and recall. It is call-compatible with the FSF readline library, but it is a fraction of the size (and offers fewer features). It does not use standard I/O. It is distributed under a "C News-like" copyright. ... An earlier version was distributed with Byron's rc. Principal changes over that version include: Faster. Is eight-bit clean (thanks to brendan@cs.widener.edu) Written in K&R C, but ANSI compliant (gcc all warnings) Propagates EOF properly; rc trip test now passes Doesn't need or use or provide memmove. More robust Calling sequence changed to be compatible with readline. Test program, new manpage, better configuration More system-independant; includes Unix and OS-9 support. Enjoy, Rich $alz Copyright 1992 Simmule Turner and Rich Salz. All rights reserved. This software is not subject to any license of the American Telephone and Telegraph Company or of the Regents of the University of California. Permission is granted to anyone to use this software for any purpose on any computer system, and to alter it and redistribute it freely, subject to the following restrictions: 1. The authors are not responsible for the consequences of use of this software, no matter how awful, even if they arise from flaws in it. 2. The origin of this software must not be misrepresented, either by explicit claim or by omission. Since few users ever read sources, credits must appear in the documentation. 3. Altered versions must be plainly marked as such, and must not be misrepresented as being the original software. Since few users ever read sources, credits must appear in the documentation. 4. This notice may not be removed or altered. ____________ OTOH, from our "man readline": ... COPYRIGHT Readline is Copyright (C) 1989, 1991, 1993, 1995, 1996 by the Free Software Foundation, Inc. ... BUGS It's too big and too slow. _____________ So the question is: Do we really need the complete, bigger GPL'd version or would it be good if I look for the older, smaller, but free version? cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 20:27:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E1DEF1515D for ; Sat, 3 Jul 1999 20:27:38 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 3FC44F818; Sat, 3 Jul 1999 23:27:33 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 33C129B15; Sat, 3 Jul 1999 23:27:33 -0400 (EDT) Date: Sat, 3 Jul 1999 23:27:33 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Chris Costello Cc: Marc Nicholas , Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: devices in sysctl MIB? In-Reply-To: <19990703215602.C86035@holly.dyndns.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 Sat, 3 Jul 1999, Chris Costello wrote: > On Sat, Jul 3, 1999, Marc Nicholas wrote: > > I would certainly welcome such info... > > > > The info in the /proc filesystem in Linux is certainly nice. (One of the > > few things that is!). > > Nice, but misplaced. What does PCI/system version/etc have to > do with running processes, exactly? > Isn't this what kernfs is for? DESCRIPTION The kernel file system, or kernfs, provides access to information on the currently running kernel... ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 21: 3:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 9E42D14C59 for ; Sat, 3 Jul 1999 21:03:46 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA19268; Sun, 4 Jul 1999 13:33:44 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA10199; Sun, 4 Jul 1999 13:33:38 +0930 (CST) Date: Sun, 4 Jul 1999 13:33:38 +0930 From: Greg Lehey To: "Brian F. Feldman" Cc: Peter Wemm , Thomas David Rivers , brdean@unx.sas.com, freebsd-hackers@FreeBSD.ORG Subject: Re: support for i386 hardware debug watch points Message-ID: <19990704133337.S709@freebie.lemis.com> References: <19990703142624.ED06C64@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Sat, Jul 03, 1999 at 12:13:55PM -0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 12:13:55 -0400, Brian F. Feldman wrote: > On Sat, 3 Jul 1999, Peter Wemm wrote: > >> Thomas David Rivers wrote: >>>> >>>> Is there any interest in supporting something like this in FreeBSD? >>>> I'm volunteering to spend some cycles on this, but I don't want to go >>>> to the effort if there's little chance that the work would be >>>> integrated. >>> >>> Scan through the mail archives - I brought this up about this >>> time last year, I think... >>> >>> There were several responses - some people may be willing to >>> assist... >> >> I'll chime in.. I'd be quite willing to bring something like this in, >> assuming it was done reasonably cleanly. It shouldn't be too hard to do it >> without imparing portability across cpu/arch types. >> >> I think this would be quite useful, especially if gdb could be made aware >> of it too. > > I think this would be great too, but I have a concern. Not all CPUs (x86) > support this; make ABSOLUTELY sure it doesn't do this kind of thing on > hardware which doesn't support it, please! I have code which does this, in a debugger which also offers some features which ddb doesn't have. Unfortunately, I trusted it to DDS tapes, with the result that I can't read the latest version. I've retrieved a version on ftp://ftp.lemis.com/pub/lowbug.tar.gz, but it's out of date in some respects. Still, it might be of use as a basis for new work. I note that the documentation includes a copy of the GPL. I can't recall why; I never placed the debugger under the GPL. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 21: 4:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 073D414E21 for ; Sat, 3 Jul 1999 21:04:38 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 35CD464; Sun, 4 Jul 1999 12:04:35 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Brian F. Feldman" Cc: Jonathan Lemon , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() In-reply-to: Your message of "Sat, 03 Jul 1999 01:01:07 -0400." Date: Sun, 04 Jul 1999 12:04:35 +0800 From: Peter Wemm Message-Id: <19990704040435.35CD464@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > In article you write: > > >now supports the select() and poll() system calls. My question is really one > > >of usage. Why would one us poll() over select()? Is select eventually go ing > > >to go away for some reason? > > > > select() as a user-level call will never go away; there is a large base > > of code that uses it. > > > > poll() is faster (it doesn't have to do bit twiddling), and it's interface > > is cleaner (it can report invalid fd's, something select() can't do). As > > its functionality is a superset of select()'s, it is used as the internal > > implementation for select(). > > Actually, select() doesn't require horrendous amounts of copyin()s, which > poll() does. So have you benchmarked the two? I'd expect select to be faster. Actually.. select() has three copyins and three copyouts per call. poll() has one copyin and one copyout per call. Now what I particular like is the event queue system that David Filo put together for Yahoo. In a nutshell you create a queue (a fd), and then register the descriptors you want to monitor with the queue. You then run an accept()-like loop where the accept returns the fd number that has met the conditions you asked for. For example, if you wanted to know if fd number 4251 becomes readable, then the accept would return 4251. This has potential to work across multiple processes sharing a queue so that events could get round robined or whatever. The other good part is that it maintains the state and lists persistantly and doesn't have to keep copying it to/from the kernel. It handles 50,000 to 100,000 connections without too much trouble. You can still use this with select as the queue fd becomes readable when there is an event waiting for your process. Is there interest in doing something like this in general? Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 21:10:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id B0E1414C59 for ; Sat, 3 Jul 1999 21:10:34 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA28183; Sat, 3 Jul 1999 23:10:31 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA21230; Sat, 3 Jul 1999 23:10:30 -0500 Message-ID: <19990703231029.08379@right.PCS> Date: Sat, 3 Jul 1999 23:10:29 -0500 From: Jonathan Lemon To: Peter Wemm Cc: "Brian F. Feldman" , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() References: <19990704040435.35CD464@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19990704040435.35CD464@overcee.netplex.com.au>; from Peter Wemm on Jul 07, 1999 at 12:04:35PM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1999 at 12:04:35PM +0800, Peter Wemm wrote: > "Brian F. Feldman" wrote: > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > > In article 0000@crb.crb-web.com> you write: > > > >now supports the select() and poll() system calls. My question is really > one > > > >of usage. Why would one us poll() over select()? Is select eventually go > ing > > > >to go away for some reason? > > > > > > select() as a user-level call will never go away; there is a large base > > > of code that uses it. > > > > > > poll() is faster (it doesn't have to do bit twiddling), and it's interface > > > is cleaner (it can report invalid fd's, something select() can't do). As > > > its functionality is a superset of select()'s, it is used as the internal > > > implementation for select(). > > > > Actually, select() doesn't require horrendous amounts of copyin()s, which > > poll() does. So have you benchmarked the two? I'd expect select to be faster. > > Actually.. select() has three copyins and three copyouts per call. poll() > has one copyin and one copyout per call. > > Now what I particular like is the event queue system that David Filo put > together for Yahoo. In a nutshell you create a queue (a fd), and then > register the descriptors you want to monitor with the queue. You then run > an accept()-like loop where the accept returns the fd number that has met > the conditions you asked for. For example, if you wanted to know if fd > number 4251 becomes readable, then the accept would return 4251. This has > potential to work across multiple processes sharing a queue so that events > could get round robined or whatever. The other good part is that it > maintains the state and lists persistantly and doesn't have to keep copying > it to/from the kernel. It handles 50,000 to 100,000 connections without > too much trouble. You can still use this with select as the queue fd > becomes readable when there is an event waiting for your process. > > Is there interest in doing something like this in general? YES! As a matter of fact, I've done something similar to this already, but instead of a queue, it's a variant of poll which passes in and out "change lists"; a list of fd's which have had status changes since the last call. I've been trying to bring it up for discussion on the -arch list, but it's been dead. (I think it was just fixed recently). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 21:21:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 1D68114C96 for ; Sat, 3 Jul 1999 21:21:32 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA19327; Sun, 4 Jul 1999 13:51:30 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA10276; Sun, 4 Jul 1999 13:51:28 +0930 (CST) Date: Sun, 4 Jul 1999 13:51:28 +0930 From: Greg Lehey To: Jonathan Lemon Cc: Peter Wemm , "Brian F. Feldman" , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() Message-ID: <19990704135128.U709@freebie.lemis.com> References: <19990704040435.35CD464@overcee.netplex.com.au> <19990703231029.08379@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990703231029.08379@right.PCS>; from Jonathan Lemon on Sat, Jul 03, 1999 at 11:10:29PM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 23:10:29 -0500, Jonathan Lemon wrote: > On Jul 07, 1999 at 12:04:35PM +0800, Peter Wemm wrote: >> "Brian F. Feldman" wrote: >>> On Fri, 2 Jul 1999, Jonathan Lemon wrote: >>> >>>> In article > 0000@crb.crb-web.com> you write: >>>>> now supports the select() and poll() system calls. My question is really >> one >>>>> of usage. Why would one us poll() over select()? Is select eventually go >> ing >>>>> to go away for some reason? >>>> >>>> select() as a user-level call will never go away; there is a large base >>>> of code that uses it. >>>> >>>> poll() is faster (it doesn't have to do bit twiddling), and it's interface >>>> is cleaner (it can report invalid fd's, something select() can't do). As >>>> its functionality is a superset of select()'s, it is used as the internal >>>> implementation for select(). >>> >>> Actually, select() doesn't require horrendous amounts of copyin()s, which >>> poll() does. So have you benchmarked the two? I'd expect select to be faster. >> >> Actually.. select() has three copyins and three copyouts per call. poll() >> has one copyin and one copyout per call. >> >> Now what I particular like is the event queue system that David Filo put >> together for Yahoo. In a nutshell you create a queue (a fd), and then >> register the descriptors you want to monitor with the queue. You then run >> an accept()-like loop where the accept returns the fd number that has met >> the conditions you asked for. For example, if you wanted to know if fd >> number 4251 becomes readable, then the accept would return 4251. This has >> potential to work across multiple processes sharing a queue so that events >> could get round robined or whatever. The other good part is that it >> maintains the state and lists persistantly and doesn't have to keep copying >> it to/from the kernel. It handles 50,000 to 100,000 connections without >> too much trouble. You can still use this with select as the queue fd >> becomes readable when there is an event waiting for your process. This sounds rather like what Tandem did in its TOS^H^H^HGuardian^H^H^H^H^H^H^H^HNonStop Kernel operating system. At the user level, you had the choice of calling awaitio (-1), which would return the next completion on any fd, or awaitio (4251), which would return information on that specific fd. And of course you have the choice of blocking or not if the conditions aren't met. Of course, the performance implications of waiting on a specific fd are another issue. >> Is there interest in doing something like this in general? > > YES! As a matter of fact, I've done something similar to this already, > but instead of a queue, it's a variant of poll which passes in and out > "change lists"; a list of fd's which have had status changes since the > last call. I've been trying to bring it up for discussion on the -arch > list, but it's been dead. (I think it was just fixed recently). Did you see the presentation "A scalable and explicit event delivery mechanism for UNIX" at USENIX? It sounded quite interesting. Page 253 of the proceedings. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 21:31:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 6706014C59 for ; Sat, 3 Jul 1999 21:31:36 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA28235; Sat, 3 Jul 1999 23:31:21 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA21834; Sat, 3 Jul 1999 23:31:20 -0500 Message-ID: <19990703233119.17254@right.PCS> Date: Sat, 3 Jul 1999 23:31:20 -0500 From: Jonathan Lemon To: Greg Lehey Cc: Peter Wemm , "Brian F. Feldman" , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() References: <19990704040435.35CD464@overcee.netplex.com.au> <19990703231029.08379@right.PCS> <19990704135128.U709@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19990704135128.U709@freebie.lemis.com>; from Greg Lehey on Jul 07, 1999 at 01:51:28PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1999 at 01:51:28PM +0930, Greg Lehey wrote: > On Saturday, 3 July 1999 at 23:10:29 -0500, Jonathan Lemon wrote: > > On Jul 07, 1999 at 12:04:35PM +0800, Peter Wemm wrote: > >> Is there interest in doing something like this in general? > > > > YES! As a matter of fact, I've done something similar to this already, > > but instead of a queue, it's a variant of poll which passes in and out > > "change lists"; a list of fd's which have had status changes since the > > last call. I've been trying to bring it up for discussion on the -arch > > list, but it's been dead. (I think it was just fixed recently). > > Did you see the presentation "A scalable and explicit event delivery > mechanism for UNIX" at USENIX? It sounded quite interesting. Page > 253 of the proceedings. Is this the paper by Mogul, et al? I didn't make it to USENIX, and don't have the proceedings at hand, but my implementation is fairly similar to a series of papers that Jeff Mogul has produced regarding web scalability. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 22: 1: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id DB48C14C30 for ; Sat, 3 Jul 1999 22:00:58 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id AAA28285; Sun, 4 Jul 1999 00:00:43 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id AAA23113; Sun, 4 Jul 1999 00:00:42 -0500 Message-ID: <19990704000042.59954@right.PCS> Date: Sun, 4 Jul 1999 00:00:42 -0500 From: Jonathan Lemon To: hackers@freebsd.org Cc: grog@freebie.lemis.com, peter@netplex.com.au Subject: poll() scalability Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an earlier posting that I attempted to make, perhaps it can provide a starting point for discussion. While this is already implemented, I'm not adverse to tossing it all for something better. -- Jonathan ----- Forwarded message from owner-freebsd-arch@FreeBSD.ORG ----- Date: Mon, 5 Apr 1999 17:42:02 -0500 From: Jonathan Lemon To: freebsd-arch@freebsd.org I'd like to open discussion on adding a new interface to FreeBSD, specifically, a variant of poll(). The problem is that poll() (and select(), as well) do not scale well as the number of open file descriptors increases. When there are a large number of descriptors under consideration, poll() takes an inordinate amount of time. For the purposes of my particular application, "large" translates into roughly 40K descriptors. As having to walk this descriptor list (and pass it between user and kernel space) is unpalatable, I would like to have the interface simply take a "change" list instead. The kernel would keep the state of the descriptors being examined, and would in turn, return a short list of descriptors that actually had any activity. In essence, I want to move the large "struct pollfd" array that I have into the kernel, and then instruct the kernel to add/remove entries from this array, and only return the array subset which has activity. A possible (actually, my current) implementation looks like this: struct fd_change { short fd; short events; }; int new_poll( int nchanges; // entries in new changelist struct fd_change *changelist; // changes to be made int n_events; // max size of output list struct fd_change *event; // returned list of events int timeout; // timeout (same as poll) ) Where the returned value is either an error, or the number of events stored in the returned changelist. Some pseudo-code that would exercise the interface: struct fd_change fc[ MAXCHANGE ]; fc[0].fd = 20; fc[0].events = ADD | READ ; // add, mark read "interest" fc[1].fd = -1; // ignore this one fc[2].fd = 32; fc[2].events = DELETE ; // delete previous fd fc[3].fd = 46; fc[3].events = WRITE ; // ask for writable events n_changes = new_poll(4, fc, MAXCHANGE, fc, -1); Comments? Note that I haven't discussed the implementation details; the implementation is done, and can probably be altered/improved, but I would like to solicit feedback on the feasability of the interface. -- Jonathan ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 22:37:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 55BF714D00 for ; Sat, 3 Jul 1999 22:36:55 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.126] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id A62CC7028A; Sun, 04 Jul 1999 02:50:36 -0300 Message-ID: <377EC869.D742F80@tdnet.com.br> Date: Sun, 04 Jul 1999 02:35:21 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: login problem: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My login.conf classes does not work, i have already looked for into The Complete FBSD, man pages, /usr/src/lib/libutil/* but nothing works the way i wanna. i think that only you hackers can help me. Here goes the classes: shelldef:\ :cputime=10m:\ :filesize=unlimited:\ :datasize=3m:\ :stacksize=2m:\ :coredumpsize=unlimited:\ :memoryuse=3m:\ :memorylocked=1m:\ :openfiles=15:\ :umask=027:\ :idletime=1m:\ :accounted=true:\ :minpasswordlen=10:\ :tc=auth-defaults: shell:\ :maxproc=10:\ :tc=shelldef: I have a user that belong to shell shell login classes, but he is not disconnected after 1 minute of idle time? What is going? I don't really have any ideia about it! Maybe my mistaken is too stupid, but...... Thank you for your time and cooperation. -- What about something different this year: Crash your FreeBSD box! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 22:41:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 98CAB14D00 for ; Sat, 3 Jul 1999 22:41:55 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id BAA47575; Sun, 4 Jul 1999 01:41:47 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 4 Jul 1999 01:41:46 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: "Brian F. Feldman" , Jonathan Lemon , wayne@crb-web.com, hackers@FreeBSD.org Subject: Re: poll() vs select() In-Reply-To: <19990704040435.35CD464@overcee.netplex.com.au> 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, 4 Jul 1999, Peter Wemm wrote: > "Brian F. Feldman" wrote: > > On Fri, 2 Jul 1999, Jonathan Lemon wrote: > > > > > In article 0000@crb.crb-web.com> you write: > > > >now supports the select() and poll() system calls. My question is really > one > > > >of usage. Why would one us poll() over select()? Is select eventually go > ing > > > >to go away for some reason? > > > > > > select() as a user-level call will never go away; there is a large base > > > of code that uses it. > > > > > > poll() is faster (it doesn't have to do bit twiddling), and it's interface > > > is cleaner (it can report invalid fd's, something select() can't do). As > > > its functionality is a superset of select()'s, it is used as the internal > > > implementation for select(). > > > > Actually, select() doesn't require horrendous amounts of copyin()s, which > > poll() does. So have you benchmarked the two? I'd expect select to be faster. > > Actually.. select() has three copyins and three copyouts per call. poll() > has one copyin and one copyout per call. > But poll() copies in HUGE amounts of data compared to the few bytes for thousands of FDs that select does. > Now what I particular like is the event queue system that David Filo put > together for Yahoo. In a nutshell you create a queue (a fd), and then > register the descriptors you want to monitor with the queue. You then run > an accept()-like loop where the accept returns the fd number that has met > the conditions you asked for. For example, if you wanted to know if fd > number 4251 becomes readable, then the accept would return 4251. This has > potential to work across multiple processes sharing a queue so that events > could get round robined or whatever. The other good part is that it > maintains the state and lists persistantly and doesn't have to keep copying > it to/from the kernel. It handles 50,000 to 100,000 connections without > too much trouble. You can still use this with select as the queue fd > becomes readable when there is an event waiting for your process. > > Is there interest in doing something like this in general? Yes! That would not replace select() or poll(), but it would be awesome to have! > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sat Jul 3 22:58:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id D870014C01 for ; Sat, 3 Jul 1999 22:58:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA19584; Sun, 4 Jul 1999 15:28:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA10442; Sun, 4 Jul 1999 15:28:29 +0930 (CST) Date: Sun, 4 Jul 1999 15:28:29 +0930 From: Greg Lehey To: Jonathan Lemon Cc: Peter Wemm , "Brian F. Feldman" , wayne@crb-web.com, hackers@FreeBSD.ORG Subject: Re: poll() vs select() Message-ID: <19990704152829.W709@freebie.lemis.com> References: <19990704040435.35CD464@overcee.netplex.com.au> <19990703231029.08379@right.PCS> <19990704135128.U709@freebie.lemis.com> <19990703233119.17254@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990703233119.17254@right.PCS>; from Jonathan Lemon on Sat, Jul 03, 1999 at 11:31:20PM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 23:31:20 -0500, Jonathan Lemon wrote: > On Jul 07, 1999 at 01:51:28PM +0930, Greg Lehey wrote: >> On Saturday, 3 July 1999 at 23:10:29 -0500, Jonathan Lemon wrote: >>> On Jul 07, 1999 at 12:04:35PM +0800, Peter Wemm wrote: >>>> Is there interest in doing something like this in general? >>> >>> YES! As a matter of fact, I've done something similar to this already, >>> but instead of a queue, it's a variant of poll which passes in and out >>> "change lists"; a list of fd's which have had status changes since the >>> last call. I've been trying to bring it up for discussion on the -arch >>> list, but it's been dead. (I think it was just fixed recently). >> >> Did you see the presentation "A scalable and explicit event delivery >> mechanism for UNIX" at USENIX? It sounded quite interesting. Page >> 253 of the proceedings. > > Is this the paper by Mogul, et al? Yes, this is the one. > I didn't make it to USENIX, and don't have the proceedings at hand, > but my implementation is fairly similar to a series of papers that > Jeff Mogul has produced regarding web scalability. Good. I thought the paper (presented by Gaurav Banga) was quite interesting, but I wasn't convinced it was the only way to do it. Unfortunately, I haven't found time to look at it in more detail. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 23:27:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r31.bfm.org [208.18.213.127]) by hub.freebsd.org (Postfix) with ESMTP id 1FC5B14C59 for ; Sat, 3 Jul 1999 23:27:41 -0700 (PDT) (envelope-from adam@whizkidtech.net) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id BAA00234; Sun, 4 Jul 1999 01:26:28 -0500 (CDT) (envelope-from adam) Date: Sun, 4 Jul 1999 01:25:56 -0500 From: "G. Adam Stanislav" To: Wes Peters Cc: "Brian F. Feldman" , Janie Dykes , freebsd-hackers@FreeBSD.ORG Subject: Re: how to start to be a hacker? Message-ID: <19990704012556.A220@whizkidtech.net> References: <377EA69C.6729DB43@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <377EA69C.6729DB43@softweyr.com>; from Wes Peters on Sat, Jul 03, 1999 at 06:11:08PM -0600 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ 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 Sat, Jul 03, 1999 at 06:11:08PM -0600, Wes Peters wrote: > Trust me, greenie, those of us who a FAR from 16 wish we weren't. ;^) What, and miss the sixties??? Get back to your handbasket! :-) Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 3 23:34:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (unknown [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 1201E14CC3 for ; Sat, 3 Jul 1999 23:34:08 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id GAA11641; Sun, 4 Jul 1999 06:33:45 GMT Date: Sun, 4 Jul 1999 06:33:45 +0000 (GMT) From: Ben Rosengart To: "Chris D. Faulhaber" Cc: hackers@FreeBSD.ORG Subject: Re: devices in sysctl MIB? 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 Sat, 3 Jul 1999, Chris D. Faulhaber wrote: > On Sat, 3 Jul 1999, Chris Costello wrote: > > > On Sat, Jul 3, 1999, Marc Nicholas wrote: > > > I would certainly welcome such info... > > > > > > The info in the /proc filesystem in Linux is certainly nice. (One of the > > > few things that is!). > > > > Nice, but misplaced. What does PCI/system version/etc have to > > do with running processes, exactly? > > > > Isn't this what kernfs is for? Isn't kernfs deprecated in favor of sysctl? -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message