From owner-freebsd-hackers Sun Jul 12 01:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22178 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 01:15:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22172 for ; Sun, 12 Jul 1998 01:15:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-35.camalott.com [208.229.74.35]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id DAA32319; Sun, 12 Jul 1998 03:15:45 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id DAA01115; Sun, 12 Jul 1998 03:14:35 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 03:14:35 -0500 (CDT) Message-Id: <199807120814.DAA01115@detlev.UUCP> To: winter@jurai.net CC: cyouse@artemis.syncom.net, bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: (winter@jurai.net) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Obviously this guy is on crack. "Adding a warning to stderr is gonna >> break things! Why can't we just leave it alone instead of effecting >> massive change?!?" > You -will- break things if you alter the default behavior. Show me where. I have already offered to buy a beer for somebody who can show me where I -will- break things; see message-id <199807111926.OAA14413@detlev.UUCP>. > As you are not able to prove for -all- cases that this change will > not break things it should be only enabled by a new switch. (-w as > someone suggested) Neither were we able to prove that there wasn't some assembly code that references errno when we changed it to *__errno(). Neither were we able to prove that nobody's scripts used hexdump and examined an executable file to find information about an a.out image, but we still are going to elf. Neither were we able to prove that adding a #warning to sys/dir.h wasn't going to break things. For nearly any change you make, there will *potentially* be some code, somewhere, that relies on the old state. But nevertheless, if it is unlikely enough to break things, then we make the change and move on. If you want to ensure that anything you might possibly be running will still work after you upgrade, I suggest that your next upgrade from, say, 2.2.6-RELEASE be to... you guessed it... 2.2.6-RELEASE. > Besides, creating a link to a non existent directory is not cause for an > error condition; you get the error when you attempt to reference the link. I'm not talking about an error condition. I am talking about a diagnostic. We're going through a different transition, not dumping to a trap state. > This is the correct unix behavior, to assume that you know what you're > talking about. If you want to have unix perform sanity checks, there are > flags for that as well. Add this as a new flag please. Sorry, I didn't realize that Unix was supposed to never mention if a user is doing something odd. Regrettably, we have a number of programs which violate this important design principle. I'll have to submit a few pr's: pwd_mkdb: Issues a warning if the root's shell is not yet listed in /etc/shells. If, for instance, a user wants the root shell to be only availible as a login shell to root, then it would not be listed in /etc/shells. However, this means that many userlist maintainance programs will issue a diagnostic that is unnecessary and poor design. swapon: Warns if a device is already being swapped on. This is superfluous output in scripts which are executing swapon to assert that all devices that should be swapped on, are being swapped on. This superfluous output should be removed. Users who want to tell if a device is being swapped on when they execute the command should simply add a shell script to their path that executes swapinfo and grep, and gives the appropriate diagnostic. cp: Warns if: 1) a directory is referenced without -R, or 2) a source file is linked to its destination. Obviously, if you had a directory you want to copy, you would have included -R. Also, if a large static file in a compile directory was linked into a build directory, the cp that takes place during the build process would issue an unnecessary diagnostic that disrupts the appearance of the build process. ftp: Warns if an unknown keyword is encountered in .netrc for the target machine. Since comments are not allowed in .netrc, then a user might use an invalid field as a comment. If a script is examining the ftp output, then the extraneous output would confuse it. od: Generates an extra warning about being depreciated if an illegal flag is used. A utility to generate a summary of flags for all programs may intentionally use illegal flags to get summaries from various programs, and the extra line may confuse its parser. lex: -w (suppress warnings) is not the default. This causes warnings in several possible non-error situations. This extraneous output is irrelevant and shouldn't be displayed unless requested. login: Displays a notice if a password is about to expire. This may break autologin scripts which depend on a particular sequence of events. If a user wants to know about password expiration, that information should be displayed by the user's .profile (or equivilent). Most Kerberos-enabled programs: Warn if they cannot connect to a Kerberos domain. make: Warns if it cannot chdir to MAKEOBJDIR (or its equivilent). Clearly, if a user decided to set this to a path the user did not normally have access to, it was intended to only be used if the user were su'd. This superfluous warning should be removed. rsh: When Kerberos-enabled, and connecting to a non-Kerberos host, rsh issues a warning. This warning may break automated login scripts written for pre-Kerberos rsh. units: In the case of a control file which redefines a prefix, will issue a diagnostic. This is undesirable, as such a control file may exist for interoperability with a units-like system with more advanced prefix handling that allows the redefinition of units. Furthermore, this could break scripts which depend on the output of units, and is not useful to the interactive user (who already knows this information). This diagnostic should be removed. write: Issues a warning if a user is logged in more than once and no tty is specified. A script written for a different write may examine stderr and assume that the user is not logged in if anything is sent. This diagnostic should be removed. cdcontrol: Issues a warning when using the default CD device. This warning goes against correct Unix behavior (as described by Dodd, et al) and should be eliminated. ed: Prints a '?' warning if a user makes a typo. An experienced user will know that a typo has been made and will not require a diagnostic. This extra verbosity is unnecessary and clutters up the screen. moused: Issues a warning if the mouse connected has a different protocol than specified. rcp: Warns if setting the TOS for the socket failed. However, since this is not a fatal situation, this diagnostic is superfluous and should be avoided. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 01:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23020 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 01:28:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23015 for ; Sun, 12 Jul 1998 01:28:10 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-35.camalott.com [208.229.74.35]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id DAA32424; Sun, 12 Jul 1998 03:22:27 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id DAA01163; Sun, 12 Jul 1998 03:21:40 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 03:21:40 -0500 (CDT) Message-Id: <199807120821.DAA01163@detlev.UUCP> To: tlambert@primenet.com CC: bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <199807120123.SAA17458@usr08.primenet.com> (message from Terry Lambert on Sun, 12 Jul 1998 01:23:19 +0000 (GMT)) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807120123.SAA17458@usr08.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> How on earth will issuing a diagnostic make it harder to write >>> scripts? >> Because now you have to filter out (additional) noise. > Consider the "improvement" to the dump(8) command about a year ago... Regrettably, I don't remember this. Could you please refresh my memory? > Especially if it is a deviation in order to protect the kind of people > who type "DIR" in DOS after "DELETE FILE.DAT" to reassure themselves > that the system, indeed, did what they told it to do, and deleted the > file. > Protecting people who don't believe a file is really gone until they > get a directory listing without the file in it is pretty low on the > ladder of UNIX priorities. I trust Unix to do what I tell it to. But I don't mind it reminding me if I may have had one too many as it's doing what I told it to. > I wouldn't object too strongly to a "-w", as has been suggested elsewhere, > so long as the alias was not there by default. I would still object a > little, on the principle that a future version of POSIX might define > a "-w" argument, causing a namespace collision with the FreeBSD version > of the command (and thus breaking scripts, .login's, .cshrc's, etc.). I generally prefer a 'no-warnings' option over a 'enable-warnings' option if the warnings don't change the effects of the command. That is because a user at the keyboard is lazy, and will not, generally, type the extra options. Yes, we can make aliases, and so on, and so forth. On the other hand, those who are scared of breaking something can do the same with the -q (quiet) option I proposed. It comes back to my earlier question: Are there going to be more lossages if we add the warnings, or if we don't? I know for a fact that I've done the same thing that rminnich described in his original post. I also know that I've never written a script that this change would break. How many of us have done each? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 03:12:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08531 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 03:12:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA08291 for ; Sun, 12 Jul 1998 03:12:18 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id DAA11521; Sun, 12 Jul 1998 03:11:55 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd011501; Sun Jul 12 03:11:45 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id DAA12276; Sun, 12 Jul 1998 03:11:38 -0700 (MST) From: Terry Lambert Message-Id: <199807121011.DAA12276@usr04.primenet.com> Subject: Re: Improvemnet of ln(1). To: joelh@gnu.org Date: Sun, 12 Jul 1998 10:11:38 +0000 (GMT) Cc: tlambert@primenet.com, bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-Reply-To: <199807120821.DAA01163@detlev.UUCP> from "Joel Ray Holveck" at Jul 12, 98 03:21:40 am X-Mailer: ELM [version 2.4 PL25] 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 > >>> How on earth will issuing a diagnostic make it harder to write > >>> scripts? > >> Because now you have to filter out (additional) noise. > > Consider the "improvement" to the dump(8) command about a year ago... > > Regrettably, I don't remember this. Could you please refresh my memory? Someone "fixed" dump to be more consistent in the way it logged events, resulting in scripts that called dump, and even some programs, no longer working. Consider the effect on xgdb of "fixing" gdb's output. > It comes back to my earlier question: Are there going to be more > lossages if we add the warnings, or if we don't? I know for a fact > that I've done the same thing that rminnich described in his original > post. I also know that I've never written a script that this change > would break. > > How many of us have done each? Well, delaying the warning until such time as you try to use the link is not a bad idea -- and it's existing practice. Putting this warning in is in the same class as warning about anything else that implements late-binding of information. If you are going to pre-warn about something which may be perfectly valid, ie: ln -s /b/stuff/newsrc /newsrc cd /b/stuff mkdir newsrc cd !$ cvs co src Then you might as well warn about mismatched braces in C source code when you exit "vi" after editing something which is obviosly C source code because it matches the regular expression .*\.c. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 03:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09502 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 03:22:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09442 for ; Sun, 12 Jul 1998 03:21:52 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id MAA22825 for freebsd-hackers@FreeBSD.ORG; Sun, 12 Jul 1998 12:17:28 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA03600; Sun, 12 Jul 1998 11:46:36 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807120946.LAA03600@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG cc: seggers@semyam.dinoco.de Subject: Page size flexibility in FreeBSD VM? Date: Sun, 12 Jul 1998 11:46:35 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! While reading the VM source I was wondering about how flexible it shall be with regard to the page sizes used. Is the goal just to support 4k pages and if that works it is good enough or shall it be more flexible if one wishes to use smaller or larger pages? The actual mapping in pmap.c of course has to cope with hardware restrictions. My questions is just concerned with the machine independent part. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 03:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09510 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 03:22:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09448 for ; Sun, 12 Jul 1998 03:21:59 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id MAA22812 for freebsd-hackers@FreeBSD.ORG; Sun, 12 Jul 1998 12:17:26 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA02700; Sun, 12 Jul 1998 11:15:31 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807120915.LAA02700@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shadow object collapse In-reply-to: Your message of "Sat, 11 Jul 1998 11:23:06 EDT." Cc: seggers@semyam.dinoco.de Date: Sun, 12 Jul 1998 11:15:30 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to the Mach paper "Machine-Independent Virtual Memory Management > for Paged Uniprocessor and Multiprocessor Architectures", a shadow object For the record so someone looking for documentation on VM can find it w/o much effort: ftp://mach.cs.cmu.edu/project/mach/doc/published/MIvmm.ps The URL I found on one Web page I found on this was unfortunately mis- leading. :-( Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 04:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18911 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 04:32:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tapti.hss.hns.com (tapti.hss.hns.com [139.85.242.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18904; Sun, 12 Jul 1998 04:32:10 -0700 (PDT) (envelope-from kchowksey@hss.hns.com) Received: from tarang.hss.hns.com (tarang.hss.hns.com [139.85.242.33]) by tapti.hss.hns.com (8.8.8/8.8.8) with ESMTP id RAA26428; Sun, 12 Jul 1998 17:19:52 +0530 (IST) Received: (from kchowksey@localhost) by tarang.hss.hns.com (8.8.2/8.7.3) id RAA06121; Sun, 12 Jul 1998 17:07:56 +0530 (IST) Date: Sun, 12 Jul 1998 17:07:56 +0530 (IST) Message-Id: <199807121137.RAA06121@tarang.hss.hns.com> From: Kapil Chowksey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@FreeBSD.ORG CC: freebsd-sparc@FreeBSD.ORG Subject: console question X-Mailer: VM 6.34 under Emacs 19.34.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I wonder if it is possible to have multiple devices as consoles with FreeBSD/i386 ? eg. a Serial port as well as the monitor. By reading i386/i386/cons.c, it appears to be not. If it is not, then I would want to put away with the layer provided by i386/i386/cons.c while porting to sparc beacause the OpenBoot PROM already provides a console abstraction. Meanwhile, I have a functional locore.S and a PROM library with I/O routines and device tree browsing routines. I want to work on adding more debug infrastructure now with symbol table lookups and a panic routine which brings you to the PROM where you can do a `ctrace'. Also, integrating things with the BSD `configure'. -- Kapil Chowksey Viva GNU ! kchowksey@hss.hns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 05:50:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22547 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 05:50:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22540 for ; Sun, 12 Jul 1998 05:50:53 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA25645 for ; Sun, 12 Jul 1998 05:50:34 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA18692; Sun, 12 Jul 1998 08:50:42 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id JAA25423; Sun, 12 Jul 1998 09:27:11 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA14564; Sun, 12 Jul 1998 08:53:59 -0400 (EDT) Date: Sun, 12 Jul 1998 08:53:59 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807121253.IAA14564@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com, joelh@gnu.org Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807111525.KAA13574@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Whereas in order to get the existing non-"-f" behaviour, I'd have to > > modify existing code. > > A warning message wouldn't break your existing code. Again, we're not > proposing a prompt here, just a diagnostic that you can ignore if > you're intentionally linking to a non-existant file. Umm... just a subtle point here. Adding a message that didn't previously exist with working scripts will almost always break some code. If this ln were placed in a shell script that produced the string "OK" when it worked correctly - then the sudden appearance of new text would likely break users of that shell script. Also, sending the message to stderr instead of stdout will break fewer programs; but you have no assurances. My point being - a change in behaviour without a change in interface will break programs... almost by definition. I'm a believer in the more conservative "add a new option to produce these warnings" approach. Note that the opposite, add a new option to suppress the warnings isn't as palatable because one would need to visit every script that uses 'ln' and determine if the option should be added. And, furthermore, that script would suddenly become FreeBSD-specific... - 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 Jul 12 05:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22826 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 05:54:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22821 for ; Sun, 12 Jul 1998 05:54:26 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA19085; Sun, 12 Jul 1998 08:54:02 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id JAA25541; Sun, 12 Jul 1998 09:31:27 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA14584; Sun, 12 Jul 1998 08:58:15 -0400 (EDT) Date: Sun, 12 Jul 1998 08:58:15 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807121258.IAA14584@lakes.dignus.com> To: bakul@torrentnet.com, cyouse@artemis.syncom.net Subject: Re: Improvemnet of ln(1). Cc: dchapes@ddm.on.ca, hackers@FreeBSD.ORG, joelh@gnu.org, rminnich@Sarnoff.COM In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Sat, 11 Jul 1998, Bakul Shah wrote: > > > For interactive use, alias ln to `ln -w' to warn you. If you > > change the default behavior of ln, you *will* break scripts. > > Unlike editors, ln is more likely to be used in scripts than > > interactively (well, it is so for most people). > > I fail to see how. An extra line output to stderr is going to break > scripts? Can you provide an example? > > > > Bottom line: backward compatibility is a good program design. > > Well, not always. Compare Windows/DOS. > > > Chuck > Sure... Consider the following files, 'foo' and 'bar': foo: ... do some stuff - with stderr copied to stdout (i.e. 2>&1) one of the 'stuff' commands is "ln" echo "done" bar: if test "`foo`" != "done" then something happened... fi The script was working just fine creating the symlink; with the change 'bar' now reports that something is amis. It is an example of a change in behaviour - which (depending on what 'something happened...' does; could be anywhere from annoying to devastating... Particularly, since the users/authors of this didn't expect the change (i.e. they didn't change 'foo') - 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 Jul 12 06:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23505 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 06:06:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23464 for ; Sun, 12 Jul 1998 06:06:03 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA25961 for ; Sun, 12 Jul 1998 06:05:45 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id JAA20046; Sun, 12 Jul 1998 09:05:54 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id JAA25836; Sun, 12 Jul 1998 09:43:20 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id JAA14646; Sun, 12 Jul 1998 09:10:08 -0400 (EDT) Date: Sun, 12 Jul 1998 09:10:08 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807121310.JAA14646@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com, joelh@gnu.org, sastdr@unx.sas.com Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807111926.OAA14413@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I will personally buy a beer (so long as it's not an American beer) > for the first five people who can show me current existance of such a > script. (In other words, a script written during or after this > discussion doesn't count.) That said, I sincerely doubt I'll have to > buy a single beer. > I don't know if this counts - but the source/build management system at SAS would break... technically, it's a program that scans the output. The code doesn't employ reasonable return-codes for some ungodly reasons, and thus, there are 'scraping scripts' that read through several gigs worth out shell/compiler/utility output and "decide" if the build was successful. Changing the behaviour of ln, as you suggest, would likely break all of that 'log scraping' code. [Who knows how many questionable 'ln' commands are embedded within this spaghetti.] Believe me; as I'm the manager of the compiler group; and I am expressly prohibited from changing even the smallest typo in a compiler message; much less adding a new one - for fear of such a calamity. The argument is that a broken 'script scraper' costs several thousands of developers a couple of days while it's repaired... we're talking man-years here of wasted time... I don't buy it myself - but that's the rule I live under. - 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 Jul 12 06:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24942 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 06:28:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24900; Sun, 12 Jul 1998 06:27:41 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807121327.GAA24900@hub.freebsd.org> Subject: Re: list closed to non subscribers In-Reply-To: <199807111729.KAA06795@rah.star-gate.com> from Amancio Hasty at "Jul 11, 98 10:29:02 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 12 Jul 1998 06:27:41 -0700 (PDT) Cc: rhh@ct.picker.com, roger@cs.strath.ac.uk, mjh@east.isi.edu, tinguely@plains.nodak.edu, grog@lemis.com, jmb@FreeBSD.ORG, sue@welearn.com.au, eivind@FreeBSD.ORG, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > Hi Jonathan, > > Care to open the list again? > sure...i have no problem opening the list. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 06:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25508 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 06:36:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25499 for ; Sun, 12 Jul 1998 06:36:07 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id GAA07869; Sun, 12 Jul 1998 06:36:29 -0700 (PDT) Message-Id: <199807121336.GAA07869@implode.root.com> To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-reply-to: Your message of "Sun, 12 Jul 1998 11:46:35 +0200." <199807120946.LAA03600@semyam.dinoco.de> From: David Greenman Reply-To: dg@root.com Date: Sun, 12 Jul 1998 06:36:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >While reading the VM source I was wondering about how flexible it >shall be with regard to the page sizes used. Is the goal just to >support 4k pages and if that works it is good enough or shall it be >more flexible if one wishes to use smaller or larger pages? > >The actual mapping in pmap.c of course has to cope with hardware >restrictions. My questions is just concerned with the machine >independent part. The goal is to be flexible enough to support our supported hardware platforms. Right now, that would be Intel x86 (4K) and Alpha (8K) in the future. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 08:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02860 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:06:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02855 for ; Sun, 12 Jul 1998 08:06:08 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id QAA26378; Sun, 12 Jul 1998 16:08:14 +0100 (BST) Date: Sun, 12 Jul 1998 16:08:14 +0100 (BST) From: Doug Rabson To: David Greenman cc: Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-Reply-To: <199807121336.GAA07869@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 Sun, 12 Jul 1998, David Greenman wrote: > >While reading the VM source I was wondering about how flexible it > >shall be with regard to the page sizes used. Is the goal just to > >support 4k pages and if that works it is good enough or shall it be > >more flexible if one wishes to use smaller or larger pages? > > > >The actual mapping in pmap.c of course has to cope with hardware > >restrictions. My questions is just concerned with the machine > >independent part. > > The goal is to be flexible enough to support our supported hardware > platforms. Right now, that would be Intel x86 (4K) and Alpha (8K) in the > future. To add to that, I only found one minor bug in the machine-independant parts of the kernel that was caused by the different page size of the alpha platform. I would not expect to see any problems with page sizes other than 4k/8k, within reason. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 08:17:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03419 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:17:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bytor.rush.net (lynch@bytor.rush.net [209.45.245.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03414 for ; Sun, 12 Jul 1998 08:17:07 -0700 (PDT) (envelope-from lynch@rush.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.1/8.8.8) with SMTP id LAA11166 for ; Sun, 12 Jul 1998 11:17:03 -0400 (EDT) (envelope-from lynch@rush.net) Date: Sun, 12 Jul 1998 11:17:01 -0400 (EDT) From: Pat Lynch To: freebsd-hackers@FreeBSD.ORG Subject: NYC FreeBSD Users Group 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 already posted this somewhat to -chat I am starting a NYC FreeBSD Users Group, anyone interested please contact me. -thanks, Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net Systems Administrator Rush Networking ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 08:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03641 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:18:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03389 for ; Sun, 12 Jul 1998 08:16:45 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id RAA21523; Sun, 12 Jul 1998 17:10:31 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id QAA13277; Sun, 12 Jul 1998 16:54:02 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807121454.QAA13277@semyam.dinoco.de> Cc: zhihuizhang , seggers@semyam.dinoco.de Subject: Re: Question about shadow object collapse In-reply-to: Your message of "Sat, 11 Jul 1998 11:23:06 EDT." To: freebsd-hackers@FreeBSD.ORG Date: Sun, 12 Jul 1998 16:54:01 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the following comments found in the routine vm_object_collapse() (see > source file vm/vm_object.c): > > (1) Pages that have been paged out will be overwirteen by any of the > parent's pages that shadow them. (why so and how to know if a page has > been paged out?) (The following is just based on what I know by now and a little bit of thinking about how to answer the questions based on the article and the FreeBSD code. It might be wrong of course. As always with soft- ware it is w/o guarantees of any kind. ;->) First terminology as I understand it: The parent here is the object belonging to a process which shares some memory with another process. It's named shadow object in the paper. The backing object is the one containing the original pages before COW operations. The shadow objects point to this object. The while loop loops over backing objects's memq which only has the resident pages on it. Non-resident pages get handled by the call to swap_pager_copy shortly after the while loop for both objects being swap objects as it is the case for shared memory. For other object types the copying of the object->un_pager should take care of it. To the former I think the answer is that the backing objects page is discarded if we have our own copy. That's what the codes does as I understand it. We might get this situation due to COW. There are three cases handled by the two if/else near the comment: 1) The backing object's page falls outside the range we contain the pages for. For example a shared memory region where we removed our own mappings for part of it. We don't care about the backing objects's pages outside our territory and just drop them. 2) We either have a page resident in memory or somewhere in swap for a page in the backing object. Then we have our own copy of this page for some reason. No need to copy, then. 3) None of the above. We rely on the backing object's page and have to move it to ourself. Non-resident pages of the backing object swap_object_copy takes care of. I must admit the comments in the code are not that useful. Maybe we could replace them by something easier to understand. If you think what I wrote is OK it might be the basis for improved comments in that area of code. It took a longer time to get these answers and I don't think everybody should get penalized that way for trying to understand the VM subsystem without need. > (2) If the page falls outside the parent, dispose of it. (why so?) See above. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 08:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04486 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:24:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04460 for ; Sun, 12 Jul 1998 08:24:46 -0700 (PDT) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id BAA14607; Sun, 12 Jul 1998 01:38:50 -0400 (EDT) (envelope-from adrian@lorax.ubergeeks.com) Date: Sun, 12 Jul 1998 01:38:50 -0400 (EDT) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Terry Lambert cc: joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807110848.BAA16020@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Jul 1998, Terry Lambert wrote: > > > I've many times used ln(1) to create what you call 'questionable links' > > > on purpose and I'd _hate_ warnings. > > > > You frequently link to files that don't exist? I generally consider > > that to be putting the cart before the cat(1), er, horse. But it's > > your system. > > I don't do it frequently, but yes, I do this occasionally. > > In a number of cases, I do this in makefiles, and I do this to > create links into a non-existant object tree. Don't you also do this to set operational flags for phkmalloc? Questionable links have their purpose in life, even if somewhat esoteric at times. 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 Sun Jul 12 08:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05327 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:30:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from penmax.com (cc595093-a.mdltwn1.nj.home.com [24.3.192.38]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA05312 for ; Sun, 12 Jul 1998 08:30:48 -0700 (PDT) (envelope-from vincef@penmax.com) Received: from penmax.com by penmax.com (SMI-8.6/SMI-SVR4) id LAA01010; Sun, 12 Jul 1998 11:52:59 -0400 Message-ID: <35A8D7E9.1CE486B@penmax.com> Date: Sun, 12 Jul 1998 11:36:09 -0400 From: Vincent Fleming Reply-To: vincef@penmax.com Organization: Penmax Grafix, Inc. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 08:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05569 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 08:33:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05564 for ; Sun, 12 Jul 1998 08:33:26 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id XAA25766 for ; Sun, 12 Jul 1998 23:32:24 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id XAA01460; Sun, 12 Jul 1998 23:32:50 +0800 Message-Id: <199807121532.XAA01460@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Motif & Lesstif - where can I buy the real thing? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Jul 1998 23:32:50 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been happily hacking away with lesstif for a while, but have tripped over a uil bug, wherein it happily loads the uid file, but dies in the rear when attempting to pick up any of the widgets in question. So who sells real Motif (apart from Xig)? Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 09:45:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15591 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 09:45:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15586 for ; Sun, 12 Jul 1998 09:45:22 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA29497 for ; Sun, 12 Jul 1998 09:44:54 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id SAA08675 for freebsd-hackers@freefall.cdrom.com; Sun, 12 Jul 1998 18:45:15 +0200 (MEST) (envelope-from kuku) Date: Sun, 12 Jul 1998 18:45:15 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807121645.SAA08675@gilberto.physik.RWTH-Aachen.DE> To: freebsd-hackers@freefall.cdrom.com Subject: 2.2.6 src tree broken? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried a mount /dist cd /dist/src sh install.sh lib (after getting the same when doing sh install.sh all) # sh install.sh lib Extracting source component: lib gzip: stdout: Broken pipe tar: child returned status 1 Is the CD (2.2.6R) damaged/broken? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 09:57:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAB17445 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 09:57:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17440 for ; Sun, 12 Jul 1998 09:57:41 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id JAA20283; Sun, 12 Jul 1998 09:42:25 -0700 (PDT) Message-Id: <199807121642.JAA20283@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Doug Rabson Cc: David Greenman , Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 12 Jul 1998 09:42:24 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Jul 1998 16:08:14 +0100 (BST) Doug Rabson wrote: > To add to that, I only found one minor bug in the machine-independant > parts of the kernel that was caused by the different page size of the > alpha platform. I would not expect to see any problems with page sizes > other than 4k/8k, within reason. You guys want to run on the UltraSparc, right? The MMU found on that puppy doesn't really have the notion of "page size" ... (well, sort of; the TLB is much like the R10000's, in that the reach of a given TLB entry is configurable per-entry...) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 10:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24095 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 10:46:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24082 for ; Sun, 12 Jul 1998 10:46:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA26356; Sun, 12 Jul 1998 10:45:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Jason Thorpe cc: Doug Rabson , David Greenman , Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-reply-to: Your message of "Sun, 12 Jul 1998 09:42:24 PDT." <199807121642.JAA20283@lestat.nas.nasa.gov> Date: Sun, 12 Jul 1998 10:45:48 -0700 Message-ID: <26353.900265548@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You guys want to run on the UltraSparc, right? The MMU found on that puppy Actually, and just FYI, when SME merged back with the rest of Sun that project was killed. SunSoft didn't want any internal competition. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 13:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10035 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 13:32:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10024 for ; Sun, 12 Jul 1998 13:32:28 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA15071; Sun, 12 Jul 1998 22:27:39 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA29400; Sun, 12 Jul 1998 21:37:15 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807121937.VAA29400@semyam.dinoco.de> Cc: dg@root.com, Stefan Eggers To: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-reply-to: Your message of "Sun, 12 Jul 1998 06:36:29 PDT." <199807121336.GAA07869@implode.root.com> Date: Sun, 12 Jul 1998 21:37:15 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The goal is to be flexible enough to support our supported hardware > platforms. Right now, that would be Intel x86 (4K) and Alpha (8K) in the > future. But if there is an obvious problem it won't be bad to remove it before someone tries other page sizes? Low priority of course. Or should I leave it alone till someone has a need for other page sizes to spare resources? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 13:32:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10069 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 13:32:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10064 for ; Sun, 12 Jul 1998 13:32:51 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA14882; Sun, 12 Jul 1998 22:27:33 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA29373; Sun, 12 Jul 1998 21:33:57 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807121933.VAA29373@semyam.dinoco.de> Cc: Jason Thorpe , seggers@semyam.dinoco.de To: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-reply-to: Your message of "Sun, 12 Jul 1998 09:42:24 PDT." <199807121642.JAA20283@lestat.nas.nasa.gov> Date: Sun, 12 Jul 1998 21:33:56 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > alpha platform. I would not expect to see any problems with page sizes > > other than 4k/8k, within reason. > > You guys want to run on the UltraSparc, right? The MMU found on that puppy > doesn't really have the notion of "page size" ... (well, sort of; the TLB > is much like the R10000's, in that the reach of a given TLB entry is > configurable per-entry...) So where's the problem. A page is 4k by definition then. ;-) As long as there is something which can act like a MMU with pages of uniform size it's good enough. If we make page sizes other than 4k/8k we will hit some small bugs (one at least - the one I found being the reason I asked) but I don't think there will be many such problems. The VM systems is pretty independent of the actual page sizes used. And the underlaying physical pages don't have to be that size anyway as far as I see. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 14:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12823 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 14:04:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (jaresh-112.mdm.mke.execpc.com [169.207.81.240]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA12805 for ; Sun, 12 Jul 1998 14:04:41 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199807122104.OAA12805@hub.freebsd.org> Received: (qmail 21306 invoked from network); 12 Jul 1998 15:40:08 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 12 Jul 1998 15:40:08 -0500 To: joelh@gnu.org cc: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Your message of "Sun, 12 Jul 1998 03:21:40 CDT." <199807120821.DAA01163@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Jul 1998 15:40:08 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807120821.DAA01163@detlev.UUCP>, Joel Ray Holveck wrote: [ ... ] } I trust Unix to do what I tell it to. But I don't mind it reminding } me if I may have had one too many as it's doing what I told it to. Ok, but your sample size of one isn't much of a consensus. } > I wouldn't object too strongly to a "-w", as has been suggested elsewhere, } > so long as the alias was not there by default. I would still object a } > little, on the principle that a future version of POSIX might define } > a "-w" argument, causing a namespace collision with the FreeBSD version } > of the command (and thus breaking scripts, .login's, .cshrc's, etc.). } } I generally prefer a 'no-warnings' option over a 'enable-warnings' } option if the warnings don't change the effects of the command. That } is because a user at the keyboard is lazy, and will not, generally, } type the extra options. Yes, we can make aliases, and so on, and so } forth. On the other hand, those who are scared of breaking something } can do the same with the -q (quiet) option I proposed. This is clearly a religious argument, and your religion seems to operate from the premise that people should be protected from themselves. While that's not what you're explicitly proposing in this case, I think that *is* the kind of philosophy that underpins your suggestion, and I suspect that's what some people are objecting to - once we do this, what's the next "little step" we undertake to protect J. Random Luser? } It comes back to my earlier question: Are there going to be more } lossages if we add the warnings, or if we don't? I know for a fact } that I've done the same thing that rminnich described in his original } post. I also know that I've never written a script that this change } would break. Well, from a slightly different perspective, you're arguing for a change. If things are left as they currently stand, there is no POLA factor to consider. You can get what you want without forcing a change upon everyone else, so the bar your argument has to clear in order to make the change goes up by that much more. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:11:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18164 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:11:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18158 for ; Sun, 12 Jul 1998 15:11:03 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id SAA18866; Sun, 12 Jul 1998 18:09:10 -0400 (EDT) From: "Allen Smith" Message-Id: <9807121809.ZM18864@beatrice.rutgers.edu> Date: Sun, 12 Jul 1998 18:09:09 -0400 In-Reply-To: Joel Ray Holveck "Re: Improvemnet of ln(1)." (Jul 12, 3:21am) References: <199807120123.SAA17458@usr08.primenet.com> <199807120821.DAA01163@detlev.UUCP> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: joelh@gnu.org, tlambert@primenet.com Subject: Re: Improvemnet of ln(1). Cc: bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am somewhat reluctant to suggest this... but why not: A. use isatty on the stderr file descriptor to decide the default behavior B. use -w to activate warnings for a non-tty and C. use -q to deactivate warnings for a tty The reason I'm somewhat reluctant to suggest this is that I generally dislike things that change based upon isatty... but this appears to be an exception, just as is color ls' --color=tty option. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19642 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:24:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hoser (root@in221.inetnebr.com [199.184.119.221]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA19637 for ; Sun, 12 Jul 1998 15:24:42 -0700 (PDT) (envelope-from cradek@in221.inetnebr.com) Message-Id: X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: Accton EtherPocket driver: beta testers wanted? Date: Sun, 12 Jul 1998 17:24:38 -0500 From: Chris Radek Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you have one of these parallel port ethernet devices and are running 3.0, please contact me. Or is it best to just post a patch? (I'm new at this...) Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:28:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20347 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:28:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20342 for ; Sun, 12 Jul 1998 15:28:28 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.2]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA330; Mon, 13 Jul 1998 00:26:53 +0200 Message-ID: <35A9387E.478BECBF@pipeline.ch> Date: Mon, 13 Jul 1998 00:28:14 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? References: <26353.900265548@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc trimmed] Jordan K. Hubbard wrote: > > > You guys want to run on the UltraSparc, right? The MMU found on that puppy > > Actually, and just FYI, when SME merged back with the rest of Sun that > project was killed. SunSoft didn't want any internal competition. :) But it looks like Kapil Chowksey is still working on it: Kapil Chowksey (kchowksey@hss.hns.com) wrote [earlier today]: -snip- > If it is not, then I would want to put away with the layer provided by > i386/i386/cons.c while porting to sparc beacause the OpenBoot PROM ^^^^^^^^^^^^^^^^^^^^^^ > already provides a console abstraction. > > Meanwhile, I have a functional locore.S and a PROM library with I/O > routines and device tree browsing routines. -snip- Hmm... who's wrong? BTW: Why joined Sun Linux International? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20513 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:29:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20492 for ; Sun, 12 Jul 1998 15:29:11 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-71.camalott.com [208.229.74.71]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA27750; Sun, 12 Jul 1998 17:29:12 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA02805; Sun, 12 Jul 1998 17:28:22 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 17:28:22 -0500 (CDT) Message-Id: <199807122228.RAA02805@detlev.UUCP> To: easmith@beatrice.rutgers.edu CC: tlambert@primenet.com, bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <9807121809.ZM18864@beatrice.rutgers.edu> (easmith@beatrice.rutgers.edu) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807120123.SAA17458@usr08.primenet.com> <199807120821.DAA01163@detlev.UUCP> <9807121809.ZM18864@beatrice.rutgers.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am somewhat reluctant to suggest this... but why not: > A. use isatty on the stderr file descriptor to decide the > default behavior > B. use -w to activate warnings for a non-tty > and C. use -q to deactivate warnings for a tty > The reason I'm somewhat reluctant to suggest this is that I generally > dislike things that change based upon isatty... but this appears to be > an exception, just as is color ls' --color=tty option. I considered this, but I am fairly opposed to basing the behavior of non-interactive programs on isatty, probably for the same reasons as you. I've made my case, quite clearly, and seem to be in the minority. However, there doesn't seem to be anyone who objects to adding -w. (Even Terry stated that he may consider objecting, but doesn't actually object at this time.) So, I'll write the patch to add a -w switch. Thanks for everyone's input! Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23923 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:46:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23867 for ; Sun, 12 Jul 1998 15:46:01 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-71.camalott.com [208.229.74.71]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA28594; Sun, 12 Jul 1998 17:46:38 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA02880; Sun, 12 Jul 1998 17:45:53 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 17:45:53 -0500 (CDT) Message-Id: <199807122245.RAA02880@detlev.UUCP> To: hamilton@pobox.com CC: hackers@FreeBSD.ORG In-reply-to: <199807122104.OAA12805@hub.freebsd.org> (message from Jon Hamilton on Sun, 12 Jul 1998 15:40:08 -0500) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807122104.OAA12805@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I trust Unix to do what I tell it to. But I don't mind it reminding >> me if I may have had one too many as it's doing what I told it to. > Ok, but your sample size of one isn't much of a consensus. I didn't come up with the idea. I've got a sample size of at least twice what you thought, so there! :-) If I was sure that this was the Right Thing, I wouldn't have put it to the mailing lists. I'd have just submitted a patch. Instead, I thought I'd see just what the sample size is. (And so far, although there's a lot of people scared that something will break, I have yet to buy any beers... but I've got a message in my inbox that may make me eat my words.) > This is clearly a religious argument, And boy, do I wish I had known that when I started. > and your religion seems to operate from the premise that people > should be protected from themselves. While that's not what you're > explicitly proposing in this case, I think that *is* the kind of > philosophy that underpins your suggestion, and I suspect that's what > some people are objecting to - once we do this, what's the next > "little step" we undertake to protect J. Random Luser? No, my religion includes reminding users of common mistakes that result in valid commands-- in this case, forgetting that ln and ln -s have a different syntax. I had thought that this was a common error. However, it seems that there are remarkably few of us. I object to preventing a user from doing anything at all, from making a symbolic link to a non-existant file, to more catastrophic possibilities like unlinking directories and newfs'ing a mounted fs. >> It comes back to my earlier question: Are there going to be more >> lossages if we add the warnings, or if we don't? I know for a fact >> that I've done the same thing that rminnich described in his original >> post. I also know that I've never written a script that this change >> would break. > Well, from a slightly different perspective, you're arguing for a > change. As I said before, if you don't want any changes... this seems to be a tricky bit for a lot of people here... *you can't upgrade your OS!* > If things are left as they currently stand, there is no POLA factor to > consider. Not for existing Unix users. I would consider having -s change the syntax of ln to be a POLA violation, but it's embedded enough that I wouldn't dare change that. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 15:57:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25835 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 15:57:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25794 for ; Sun, 12 Jul 1998 15:57:15 -0700 (PDT) (envelope-from tim@localhost.my.domain) Received: from localhost.my.domain (ppp6425.on.bellglobal.com [206.172.208.17]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id SAA02870; Sun, 12 Jul 1998 18:54:59 -0400 (EDT) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id LAA01049; Sun, 12 Jul 1998 11:26:39 -0400 (EDT) (envelope-from tim) Message-ID: <19980712112639.A1008@zappo> Date: Sun, 12 Jul 1998 11:26:39 -0400 From: Tim Vanderhoek To: Terry Lambert , joelh@gnu.org Cc: bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). References: <199807120821.DAA01163@detlev.UUCP> <199807121011.DAA12276@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807121011.DAA12276@usr04.primenet.com>; from Terry Lambert on Sun, Jul 12, 1998 at 10:11:38AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 12, 1998 at 10:11:38AM +0000, Terry Lambert wrote: > > Well, delaying the warning until such time as you try to use the > link is not a bad idea -- and it's existing practice. > > Putting this warning in is in the same class as warning about anything > else that implements late-binding of information. I really think the above is the issue, not backwards-compatibility. I simply don't think this is something we should issue a warning for. A few of the cases you [joelh] cited are also examples for which a warning should not be issued (even though one is). A warning is issued on ``ln nonexist y''. Think of '-s' as the "supress warning" flag. ('s', as in 'supress'). Perhaps that will sooth your (misguided) sensibilities and we can return to our regular -hackers fare. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 16:00:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26768 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 16:00:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26685 for ; Sun, 12 Jul 1998 16:00:05 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id PAA08462 for ; Sun, 12 Jul 1998 15:59:42 -0700 (PDT) Received: from detlev.UUCP (tex-71.camalott.com [208.229.74.71]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA29338; Sun, 12 Jul 1998 18:00:36 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA02889; Sun, 12 Jul 1998 17:59:51 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 17:59:51 -0500 (CDT) Message-Id: <199807122259.RAA02889@detlev.UUCP> To: rivers@dignus.com CC: freebsd-hackers@freefall.cdrom.com, sastdr@unx.sas.com In-reply-to: <199807121310.JAA14646@lakes.dignus.com> (message from Thomas David Rivers on Sun, 12 Jul 1998 09:10:08 -0400 (EDT)) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807121310.JAA14646@lakes.dignus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I will personally buy a beer (so long as it's not an American beer) >> for the first five people who can show me current existance of such a >> script. (In other words, a script written during or after this >> discussion doesn't count.) That said, I sincerely doubt I'll have to >> buy a single beer. > I don't know if this counts - If it's existing code that runs on BSD, whether public or private, it counts. I don't want to break anything. Let me make sure I've got all the details. > but the source/build management system at SAS would > break... technically, it's a program that scans the output. The > code doesn't employ reasonable return-codes for some ungodly > reasons, and thus, there are 'scraping scripts' that read through > several gigs worth out shell/compiler/utility output and "decide" if > the build was successful. Ugh. > Changing the behaviour of ln, as you suggest, would likely break all > of that 'log scraping' code. [Who knows how many questionable 'ln' > commands are embedded within this spaghetti.] By questionable ln commands, you mean ln -s's that link to files that don't exist at the time of the command is issued? > Believe me; as I'm the manager of the compiler group; and I am > expressly prohibited from changing even the smallest typo in a > compiler message; much less adding a new one - for fear of such a > calamity. The argument is that a broken 'script scraper' costs > several thousands of developers a couple of days while it's > repaired... we're talking man-years here of wasted time... I don't > buy it myself - but that's the rule I live under. Okay. If it is your own belief that adding a new message would break things, then I'll accept that. (I just want it to be your own belief, not something handed down on high that you believe is a product of FUD.) If this code does these things, that is: (1) Creates a symbolic link to a file that doesn't exist at the time, and (2) analyzes the output of ln's stderr, and (3) would likely break on the addition of a new line in the input of [2], then please email me with the name of your favorite beer, and the address of the liquor store where you want to pick it up. (Alternatively, if you live in Texas, I may be in your area soon, and would be happy to buy you the beer in person.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 16:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28141 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 16:08:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28069 for ; Sun, 12 Jul 1998 16:08:23 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA17325; Sun, 12 Jul 1998 16:08:37 -0700 (PDT) Message-Id: <199807122308.QAA17325@implode.root.com> To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-reply-to: Your message of "Sun, 12 Jul 1998 21:37:15 +0200." <199807121937.VAA29400@semyam.dinoco.de> From: David Greenman Reply-To: dg@root.com Date: Sun, 12 Jul 1998 16:08:36 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The goal is to be flexible enough to support our supported hardware >> platforms. Right now, that would be Intel x86 (4K) and Alpha (8K) in the >> future. > >But if there is an obvious problem it won't be bad to remove it before >someone tries other page sizes? Low priority of course. Or should I >leave it alone till someone has a need for other page sizes to spare >resources? You should leave it alone. We have plenty of real VM bugs to work on. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 17:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08796 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 17:08:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (jaresh-112.mdm.mke.execpc.com [169.207.81.240]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA08782 for ; Sun, 12 Jul 1998 17:08:47 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199807130008.RAA08782@hub.freebsd.org> Received: (qmail 22974 invoked from network); 12 Jul 1998 19:10:54 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 12 Jul 1998 19:10:54 -0500 To: "Allen Smith" Cc: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Your message of "Sun, 12 Jul 1998 18:09:09 EDT." <9807121809.ZM18864@beatrice.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Jul 1998 19:10:53 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Cc: list trimmed, I assume everyone involved will read it on the list ] In message <9807121809.ZM18864@beatrice.rutgers.edu>, "Allen Smith" wrote: } I am somewhat reluctant to suggest this... but why not: } A. use isatty on the stderr file descriptor to decide the } default behavior } B. use -w to activate warnings for a non-tty } and C. use -q to deactivate warnings for a tty You forgot: D. Answer the resulting never-ending deluge of questions from people asking why it behaves differently in different circumstances, and why it differs from the behavior they're used to seeing in . I'm sure others will complain of bloat if another flag is added to turn on such warnings - and I'm not convinced that it's a bad argument, but it's nowhere near as objectionable as changing the default behavior. I still think a wrapper is a much better option, for those who want this. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 17:11:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09130 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 17:11:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09103 for ; Sun, 12 Jul 1998 17:11:25 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-69.camalott.com [208.229.74.69]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA32453; Sun, 12 Jul 1998 19:11:37 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id TAA03473; Sun, 12 Jul 1998 19:10:51 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Jul 1998 19:10:51 -0500 (CDT) Message-Id: <199807130010.TAA03473@detlev.UUCP> To: ac199@hwcn.org CC: tlambert@primenet.com, bakul@torrentnet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <19980712112639.A1008@zappo> (message from Tim Vanderhoek on Sun, 12 Jul 1998 11:26:39 -0400) Subject: Re: Improvemnet of ln(1). (THE END OF IT!) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807120821.DAA01163@detlev.UUCP> <199807121011.DAA12276@usr04.primenet.com> <19980712112639.A1008@zappo> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wherein is enclosed a general notice to all who are considering continuing this thread: > A warning is issued on ``ln nonexist y''. Think of '-s' as the > "supress warning" flag. ('s', as in 'supress'). Perhaps that will > sooth your (misguided) sensibilities You *must* be kidding me. I applaud your efforts to restore our tranquility, but have no intention of thinking of '-s' as "suppress warning". > and we can return to our regular -hackers fare. In the enlightened interests of: 1. Better improving the operating system as a whole, and ln in particular, 2. Ending the hostility which has regrettably come into being in this thread (quite a bit of it my own fault, my apologies to the populace and MTAs at large) 3. Allowing myself and others to return to a pressing hack I have elsewhere instead of keeping up with this discussion, and 4. Keeping me from making the same blasted silly mistake that brought me into this mess to begin with, I have submitted, as pr bin/7265, a patch to implement a -w flag which will effect these warnings. I have no intention of dealing with this matter further unless somebody can show good cause (ie bugs or actual breakage caused by this patch) as to why my patch is a Bad Thing. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 17:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09274 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 17:12:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usc.usc.unal.edu.co ([200.21.26.65]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA09249 for ; Sun, 12 Jul 1998 17:12:20 -0700 (PDT) (envelope-from giffunip@asme.org) Received: from unalmodem18.usc.unal.edu.co by usc.usc.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA11140; Sun, 12 Jul 1998 19:52:28 -0400 Message-Id: <35A95091.B9537D31@asme.org> Date: Sun, 12 Jul 1998 19:10:58 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) Mime-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Porting FreeBSD to TenDRA 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 not sure it's a good idea, but JIC someone has been giving it a serious thought, there is some documentation in the OpenGroup about this: http://www.gr.opengroup.org/andf/tendra.htm http://www.gr.opengroup.org/andf/linux_re.htm and there's also some documentation on the relationships between TenDRA and Java: http://www.gr.opengroup.org/andf/javandf.htm cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 17:43:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13229 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 17:43:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13224 for ; Sun, 12 Jul 1998 17:43:47 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id RAA13247 for ; Sun, 12 Jul 1998 17:43:23 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id UAA23407; Sun, 12 Jul 1998 20:43:26 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id VAA28183; Sun, 12 Jul 1998 21:21:08 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id UAA15906; Sun, 12 Jul 1998 20:47:40 -0400 (EDT) Date: Sun, 12 Jul 1998 20:47:40 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807130047.UAA15906@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com, joelh@gnu.org Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807122259.RAA02889@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >> I will personally buy a beer (so long as it's not an American beer) > >> for the first five people who can show me current existance of such a > >> script. (In other words, a script written during or after this > >> discussion doesn't count.) That said, I sincerely doubt I'll have to > >> buy a single beer. > > I don't know if this counts - > > If it's existing code that runs on BSD, whether public or private, it > counts. I don't want to break anything. > > Let me make sure I've got all the details. > > > but the source/build management system at SAS would > > break... technically, it's a program that scans the output. The > > code doesn't employ reasonable return-codes for some ungodly > > reasons, and thus, there are 'scraping scripts' that read through > > several gigs worth out shell/compiler/utility output and "decide" if > > the build was successful. > > Ugh. Believe me - that's being polite! The entire setup suffers from what I call the "bailing" problem. That is, "we're too busy bailing water to steer the ship off of the reef into a dock for repairs." > > > Changing the behaviour of ln, as you suggest, would likely break all > > of that 'log scraping' code. [Who knows how many questionable 'ln' > > commands are embedded within this spaghetti.] > > By questionable ln commands, you mean ln -s's that link to files that > don't exist at the time of the command is issued? Most assuredly... the intent is for the files to (hopefully) exist at a future time... Part of it is builds; part of it build-area management, etc... > > > Believe me; as I'm the manager of the compiler group; and I am > > expressly prohibited from changing even the smallest typo in a > > compiler message; much less adding a new one - for fear of such a > > calamity. The argument is that a broken 'script scraper' costs > > several thousands of developers a couple of days while it's > > repaired... we're talking man-years here of wasted time... I don't > > buy it myself - but that's the rule I live under. > > Okay. If it is your own belief that adding a new message would break > things, then I'll accept that. (I just want it to be your own belief, > not something handed down on high that you believe is a product of > FUD.) Actually, it's a combination of both. My own experience has caused "thundering hurds" of people to call me up; whereby we beat a hasty retreat to a previous revision of a compiler. [The appellation there was someone elses, not my own :-) ] However, I'm convinced a good percentage of the concern was simply FUD. As far as "break" something - it would inconvenience a large group of developers (which costs money.) > > If this code does these things, that is: (1) Creates a symbolic link > to a file that doesn't exist at the time, and (2) analyzes the output > of ln's stderr, and (3) would likely break on the addition of a new > line in the input of [2], then please email me with the name of your > favorite beer, and the address of the liquor store where you want to > pick it up. (Alternatively, if you live in Texas, I may be in your > area soon, and would be happy to buy you the beer in person.) However; you bring up another point. The code I'm thinking of doesn't actually run on FreeBSD, it's on HP/UX at the moment. Only a portion of the builds currently run on FreeBSD.... so, the entire discussion is moot :-) [sorry to drag it out... I didn't realize that at the start.] And, unfortunately; I'm in Raleigh NC... and can no longer drink beer... But; if you're ever in the area - look me up! - 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 Jul 12 18:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15898 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 18:09:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15892 for ; Sun, 12 Jul 1998 18:09:08 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id VAA11325; Sun, 12 Jul 1998 21:16:30 -0400 (EDT) Date: Sun, 12 Jul 1998 21:16:30 -0400 (EDT) From: Charles Youse To: "Jordan K. Hubbard" cc: Jason Thorpe , Doug Rabson , David Greenman , Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-Reply-To: <26353.900265548@time.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 Well, the port to sun4m (sparc32) is soon underway, with ultrasparc following (soon as I get my hands on a board ;). Chuck On Sun, 12 Jul 1998, Jordan K. Hubbard wrote: > > You guys want to run on the UltraSparc, right? The MMU found on that puppy > > Actually, and just FYI, when SME merged back with the rest of Sun that > project was killed. SunSoft didn't want any internal competition. :) > > - Jordan > > 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 Jul 12 19:46:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25273 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 19:46:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25268 for ; Sun, 12 Jul 1998 19:46:54 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id WAA24866 for freebsd-hackers@FreeBSD.ORG; Sun, 12 Jul 1998 22:45:30 -0400 (EDT) From: "Allen Smith" Message-Id: <9807122245.ZM24864@beatrice.rutgers.edu> Date: Sun, 12 Jul 1998 22:45:30 -0400 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: freebsd-hackers@FreeBSD.ORG Subject: Best means of telling if a proc is still around? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. What's the best fast means of telling if a reference to a proc structure is still valid? I'm needing this for the work on privileges that I'm doing. (Specifically, there are circumstances where an action initiated by a process that then exits may be a privileged one, and may not get to the point of checking the privileges before the exit takes place.) Thanks, -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 19:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25660 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 19:50:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@hobbes.saturn-tech.com [207.229.19.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25655 for ; Sun, 12 Jul 1998 19:50:28 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id UAA29906; Sun, 12 Jul 1998 20:51:11 -0600 (MDT) Date: Sun, 12 Jul 1998 20:51:11 -0600 (MDT) From: Doug Russell To: Joel Ray Holveck cc: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807120814.DAA01115@detlev.UUCP> 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, 12 Jul 1998, Joel Ray Holveck wrote: > For nearly any change you make, there will *potentially* be some code, > somewhere, that relies on the old state. But nevertheless, if it is > unlikely enough to break things, then we make the change and move on. Exactly..... We could argue all day about every little change to every little program. There are going to be times when changing something breaks something else, even when repairing something that is obviously wrong to begin with. If we nit-picked over every change as insignificant as this one, nothing would EVER get done. Personally I think it's a good idea to warn when the user does something "stupid". Not prompt and prompt and prompt a la MS-xyz, but warn. If this breaks something somewhere, they will just have to fix it. (It would NOT be a major fix.) There are FAR FAR FAR "worse problems" introduced every day to the tree. Bottom line? I can't think of many changes that impact things LESS. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 19:53:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25927 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 19:53:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25922 for ; Sun, 12 Jul 1998 19:53:25 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA00702; Sun, 12 Jul 1998 19:53:20 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807130253.TAA00702@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Pedro F. Giffuni" cc: hackers@FreeBSD.ORG Subject: Re: Porting FreeBSD to TenDRA In-reply-to: Your message of "Sun, 12 Jul 1998 19:10:58 CDT." <35A95091.B9537D31@asme.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Jul 1998 19:53:20 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe we can get the US Department of Defense to start funding again BSD 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 20:09:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28088 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 20:09:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@hobbes.saturn-tech.com [207.229.19.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28076 for ; Sun, 12 Jul 1998 20:09:40 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id VAA29957; Sun, 12 Jul 1998 21:10:25 -0600 (MDT) Date: Sun, 12 Jul 1998 21:10:24 -0600 (MDT) From: Doug Russell To: Jon Hamilton cc: joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807122104.OAA12805@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 On Sun, 12 Jul 1998, Jon Hamilton wrote: > Well, from a slightly different perspective, you're arguing for a change. > If things are left as they currently stand, there is no POLA factor to > consider. You can get what you want without forcing a change upon everyone > else, so the bar your argument has to clear in order to make the change > goes up by that much more. What we really need is a new concept of "user levels". Or warning levels, or some such thing. Those of us who know what we want to do could run at the same level as our scripts, which would be an advanced user level with no help whatsoever, and there could be x number of other levels below, right down to extra warnings and prompts on all sorts of commands for the newbies. This doesn't even have to be implemented in the binaries a good portion of the time. A start might be some quick scripts, aliases, etc... even installable as a package. I could see this being valuable, especially when teaching UNIX to new users. Things could even be configurable, so one user could have ln warn for silly links, and another could have it off by default. As you can see, I haven't really given the implementation much thought, but I think the general IDEA is worth some thought. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 20:23:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29618 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 20:23:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29613 for ; Sun, 12 Jul 1998 20:23:46 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id UAA26460; Sun, 12 Jul 1998 20:08:51 -0700 (PDT) Message-Id: <199807130308.UAA26460@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Stefan Eggers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 12 Jul 1998 20:08:50 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Jul 1998 21:33:56 +0200 Stefan Eggers wrote: > So where's the problem. A page is 4k by definition then. ;-) The base page size (e.g. minimum) certainly would be, but you'd want to be able to communicate to the pmap a hint that says "merge into large pages if possible". Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 20:58:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03481 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 20:58:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03420 for ; Sun, 12 Jul 1998 20:58:34 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id UAA06218; Sun, 12 Jul 1998 20:57:54 -0700 (PDT) (envelope-from dhw) Date: Sun, 12 Jul 1998 20:57:54 -0700 (PDT) From: David Wolfskill Message-Id: <199807130357.UAA06218@pau-amma.whistle.com> To: hackers@FreeBSD.ORG, joe@via.net Subject: Re: Changes to login.conf In-Reply-To: <199807120612.XAA20809@monk.via.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sat, 11 Jul 1998 23:12:34 -0700 >From: Joe McGuckin >After shooting myself in the foot a couple of times, I'd like to propose >that the login.conf values cannot be set below values that would render the >machine inoperable. I understand the pain that might engender such a perspective, but might it be appropriate to (instead) have some sort of (external) checking facility -- implemented as a Perl script or (C) program or something? david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 21:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04099 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 21:04:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA04067 for ; Sun, 12 Jul 1998 21:03:58 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id VAA18751; Sun, 12 Jul 1998 21:02:41 -0700 Date: Sun, 12 Jul 1998 21:02:41 -0700 From: Joe McGuckin Message-Id: <199807130402.VAA18751@monk.via.net> To: dhw@whistle.com Subject: Re: Changes to login.conf Cc: hackers@FreeBSD.ORG X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not have the kernel set some reasonable 'min' value that it would silently enforced? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 21:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05807 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 21:19:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05802 for ; Sun, 12 Jul 1998 21:19:17 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id VAA06381; Sun, 12 Jul 1998 21:18:38 -0700 (PDT) (envelope-from dhw) Date: Sun, 12 Jul 1998 21:18:38 -0700 (PDT) From: David Wolfskill Message-Id: <199807130418.VAA06381@pau-amma.whistle.com> To: dhw@whistle.com, joe@via.net Subject: Re: Changes to login.conf Cc: hackers@FreeBSD.ORG In-Reply-To: <199807130402.VAA18751@monk.via.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 12 Jul 1998 21:02:41 -0700 >From: Joe McGuckin >Why not have the kernel set some reasonable 'min' value that >it would silently enforced? That's certainly a possible approach. I'm merely pointing out another alternative way of accomplishing what I interpreted as the base objective (avoiding self-inflicted injury). I confess that I haven't had the time to actually read the kernel source, but based on my experience in various systems, I'd expect that there could well be lots of variables that could be set to values too low (or too high, or too out-of-sync with some other variables) to make sense. Maybe 2 or 3 could make sense to check in the kernel... but it seems to me that the approach is likely to get very complex very quickly. On the other hand, the use of an external tool wouldn't involve any change to the kernel itself, and could start out simple, with new tests being added comparatively modularly (and thus, one hopes, easily). david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 21:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08518 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 21:45:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08502 for ; Sun, 12 Jul 1998 21:45:27 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA03825; Sun, 12 Jul 1998 21:45:19 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd003759; Sun Jul 12 21:45:09 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA25307; Sun, 12 Jul 1998 21:45:01 -0700 (MST) From: Terry Lambert Message-Id: <199807130445.VAA25307@usr07.primenet.com> Subject: Re: Page size flexibility in FreeBSD VM? To: cyouse@artemis.syncom.net (Charles Youse) Date: Mon, 13 Jul 1998 04:45:01 +0000 (GMT) Cc: jkh@time.cdrom.com, thorpej@nas.nasa.gov, dfr@nlsystems.com, dg@root.com, seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Charles Youse" at Jul 12, 98 09:16:30 pm X-Mailer: ELM [version 2.4 PL25] 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 > Well, the port to sun4m (sparc32) is soon underway, with ultrasparc > following (soon as I get my hands on a board ;). Let me know where you stand. I recently bought a SPARC box for porting work, but have as yet not unpacked it because I promised myself I would get some other code done before I started sucking up my free time on something like that... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 21:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08703 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 21:47:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08698 for ; Sun, 12 Jul 1998 21:47:05 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id VAA06356; Sun, 12 Jul 1998 21:46:53 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd006295; Sun Jul 12 21:46:43 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA25353; Sun, 12 Jul 1998 21:46:40 -0700 (MST) From: Terry Lambert Message-Id: <199807130446.VAA25353@usr07.primenet.com> Subject: Re: Changes to login.conf To: dhw@whistle.com (David Wolfskill) Date: Mon, 13 Jul 1998 04:46:40 +0000 (GMT) Cc: hackers@FreeBSD.ORG, joe@via.net In-Reply-To: <199807130357.UAA06218@pau-amma.whistle.com> from "David Wolfskill" at Jul 12, 98 08:57:54 pm X-Mailer: ELM [version 2.4 PL25] 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 > >After shooting myself in the foot a couple of times, I'd like to propose > >that the login.conf values cannot be set below values that would render the > >machine inoperable. > > I understand the pain that might engender such a perspective, but might > it be appropriate to (instead) have some sort of (external) checking > facility -- implemented as a Perl script or (C) program or something? vilc (as in vipw) anyone? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 22:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10798 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 22:02:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10791 for ; Sun, 12 Jul 1998 22:02:45 -0700 (PDT) (envelope-from sysadmin@mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id AAA14921 for ; Mon, 13 Jul 1998 00:03:09 -0500 (CDT) (envelope-from sysadmin@mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDAE1B.73B84C90@noc.mfn.org>; Mon, 13 Jul 1998 05:02:36 +0100 Message-ID: <01BDAE1B.73B84C90@noc.mfn.org> From: NOC-GFX To: "'freebsd-hackers@freebsd.org'" Subject: rwhod / syslogd anomaly Date: Mon, 13 Jul 1998 05:02:35 +0100 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 Greetings, First, let me apologize if this is the wrong forum, I wasn't sure: I've gone around and around with this on -questions but with no resolution... First off, the base problem started out as rwhod dying with no messages or log entries to LOG_DAEMON, for reasons I still haven't figured out. It dies after about three minutes of up time (the magic number according to the source), and doesn't peep a thing. And the *really* strange part is that if you try to bring up back up, it won't start, *nor* leave a message/log entry as to why not! I have not coded in c since 1985, so to say that my skills are rusty is an understatement: this has left me in the position of trying to track this thing down using really dirty hacks like fprintf's to mark where I am in the code. So far I have put a message out to std-err before every single exit() call in the source, and have not seen a single one show up. On top of that, I made sure that the facility for logging rwhod was up and set correctly by forcing errors while it was up for its initial (IPL) 3 minute run. Before it dies, it logs correctly, after it dies, it neither runs nor logs. So, here's where I'm at now: (1) A thorough search of the archives has turned up nothing for either rwhod/syslogd. (2) I need to establish (a) what can stop a program dead like this, and (b) what can prevent it from either logging or putting messages out to stderr, all without generating *any* messages itself. (I have gone over the other logs dozens of times with a fine tooth comb, even the "Daemon" log, which is just massive). Does anybody have any thoughts on this? J.A. Terranson sysadmin@mfn.org (PS: Please cc me directly, as I am not a -hackers recipient. Thanks!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 22:03:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10928 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 22:03:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10920 for ; Sun, 12 Jul 1998 22:03:47 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id WAA06547 for hackers@freebsd.org; Sun, 12 Jul 1998 22:03:09 -0700 (PDT) (envelope-from dhw) Date: Sun, 12 Jul 1998 22:03:09 -0700 (PDT) From: David Wolfskill Message-Id: <199807130503.WAA06547@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: Changes to login.conf In-Reply-To: <199807130446.VAA25353@usr07.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Terry Lambert >Date: Mon, 13 Jul 1998 04:46:40 +0000 (GMT) >> >After shooting myself in the foot a couple of times, I'd like to propose >> >that the login.conf values cannot be set below values that would render the >> >machine inoperable. >> I understand the pain that might engender such a perspective, but might >> it be appropriate to (instead) have some sort of (external) checking >> facility -- implemented as a Perl script or (C) program or something? >vilc (as in vipw) anyone? Seems that the name probably ought to be closer to "virc" -- but then, I'm pretty bad at naming things.... :-} But yes; that's certainly one approach that might well be workable. Implementing it might be "interesting".... I'd be content, though, with a separately-run executable that would run around & do various consistency checks. (vipw is of somewhat more limited scope, I would expect....) david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 12 23:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18521 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 23:33:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18516 for ; Sun, 12 Jul 1998 23:33:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA12305; Sun, 12 Jul 1998 23:33:32 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Joe McGuckin cc: dhw@whistle.com, hackers@FreeBSD.ORG Subject: Re: Changes to login.conf In-reply-to: Your message of "Sun, 12 Jul 1998 21:02:41 PDT." <199807130402.VAA18751@monk.via.net> Date: Sun, 12 Jul 1998 23:33:31 -0700 Message-ID: <12301.900311611@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It wouldn't be the Unix philosophy, for one thing. As one person put it, "Unix doesn't stop you from doing stupid things since that would also stop you from doing clever things." More importantly, doing "silent enforcement" is something which is only bound to bite you on the ass. Needless to say, I think that prevailing opinion is so much against a change like this that it's probably not constructive to debate it any further - it just ain't gonna happen. login.conf is only one of many many ways in which you can completely screw yourself if you commit various errors, and once down this road we'd next get asked why we didn't do the same for sysctl(2), kernel configuration files, rm(1), etc etc. It's a slippery slope that anyone seriously versed in the whys and whats of Unix knows to avoid. - Jordan > > Why not have the kernel set some reasonable 'min' value that > it would silently enforced? > > 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 Jul 12 23:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19210 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 23:39:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19205 for ; Sun, 12 Jul 1998 23:39:56 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA05674; Sun, 12 Jul 1998 23:39:52 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd005608; Sun Jul 12 23:39:42 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA00272; Sun, 12 Jul 1998 23:39:41 -0700 (MST) From: Terry Lambert Message-Id: <199807130639.XAA00272@usr07.primenet.com> Subject: Re: Changes to login.conf To: dhw@whistle.com (David Wolfskill) Date: Mon, 13 Jul 1998 06:39:40 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199807130503.WAA06547@pau-amma.whistle.com> from "David Wolfskill" at Jul 12, 98 10:03:09 pm X-Mailer: ELM [version 2.4 PL25] 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 > >vilc (as in vipw) anyone? > > Seems that the name probably ought to be closer to "virc" -- but then, > I'm pretty bad at naming things.... :-} > > But yes; that's certainly one approach that might well be workable. > Implementing it might be "interesting".... > > I'd be content, though, with a separately-run executable that would run > around & do various consistency checks. (vipw is of somewhat more > limited scope, I would expect....) Well, this is more along the lines of a schema based system, where you say "here is the proposed changes, are they consistent?". It's more useful that they be globally consistent than that they be merely internally consistent. Consider the network interface whose IP address, netmask, and broadcast address are consistent, but which are in conflict with another network interface. This moves into the real of LDAP and subschema enforcement, I think. It's amazing to me that sendmail used to have a .cf checking mechanism, in support of "frozen" configurations, but that this was discarded at the same time configurations were discarded. You could also consider the case of a modification to the bind configuration information that would result in both upper and lower case versions of the same host name. There should be a method for proposing a group of changes as an atomic unit, and having them vetted (or rejected) as a unit. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 00:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22487 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 00:13:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unionion.uion.edu.gr ([195.130.124.68]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA22480; Mon, 13 Jul 1998 00:13:00 -0700 (PDT) (envelope-from gvlachos@kerkyra.ionio.gr) Received: from localhost by unionion.uion.edu.gr; (5.65/1.1.8.2/05Mar96-0202PM) id AA28262; Mon, 13 Jul 1998 10:11:25 +0300 Date: Mon, 13 Jul 1998 10:11:24 +0300 (EET DST) From: Giannis Vlachos To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Script for dialup users 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 to anyone on the lists of FreeBSD. I have build my dialup server on Freebsd 2.2.2 version. The users who they are connected using Win95 need a script for automatically login (Not the old fashion type with the black window verifacation login : and Password: ) I try one . It takes the login name correctlly but at the password the script halted and i have to continue manually and to type the password by hand. Does anyone have any solution for this case? I want to say thanks in advance. Giannis Vlachos Corfu Isladn - Greece To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 00:55:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26510 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 00:55:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26505 for ; Mon, 13 Jul 1998 00:55:47 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA20589 ; Mon, 13 Jul 1998 09:54:11 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA22063; Mon, 13 Jul 1998 09:54:10 +0200 To: Doug Russell Cc: Dag-Erling Coidan Smørgrav , sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: 3c509 NICs suck (was: Re: NIC drivers) References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 13 Jul 1998 09:54:09 +0200 In-Reply-To: Doug Russell's message of Fri, 10 Jul 1998 11:32:50 -0600 (MDT) Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Russell writes: > They are definitely funky. I have one (thank goodness it was given to me, > I didn't buy it. :) ) It usually sits on the shelf, but when I have tried > to use it, it will do all kinds of strange things. In some machines, the Tell me about it... I have an old 3c509 Combo card that once in a while (usually after you've taken it out of the machine and put it back in) will decide to switch over from 10Base2 to 10BaseT, and it doesn't even *have* a UTP connector... Did I ever rip out my hair over *this* one (well, I would have, if my hair was long enough to get a good grip) DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 01:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29511 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 01:37:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hermes.hrz.uni-bielefeld.de (hermes.hrz.uni-bielefeld.de [129.70.4.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29487; Mon, 13 Jul 1998 01:37:06 -0700 (PDT) (envelope-from lkoeller@post.uni-bielefeld.de) Received: from mitch.hrz.uni-bielefeld.de (mitch.hrz.uni-bielefeld.de [129.70.4.17]) by hermes.hrz.uni-bielefeld.de (8.8.8/8.8.8) with ESMTP id KAA23420; Mon, 13 Jul 1998 10:37:10 +0200 (MESZ) Received: from localhost by mitch.hrz.uni-bielefeld.de with SMTP (8.8.6/16.2) id IAA02918; Mon, 13 Jul 1998 08:36:58 GMT Message-Id: <199807130836.IAA02918@mitch.hrz.uni-bielefeld.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Lars =?iso-8859-1?Q?K=F6ller?= To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG cc: lkoeller@post.uni-bielefeld.de Subject: fastvid, Tyan 1668 and new BIOS V5.01! X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09860 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 03:18:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09855 for ; Mon, 13 Jul 1998 03:18:41 -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.8.7/8.8.7) with ESMTP id KAA08973; Mon, 13 Jul 1998 10:18:21 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA27248; Mon, 13 Jul 1998 12:18:19 +0200 (MET DST) Message-ID: <19980713121819.08980@follo.net> Date: Mon, 13 Jul 1998 12:18:19 +0200 From: Eivind Eklund To: "Larry S. Lile" , hackers@FreeBSD.ORG Subject: Re: Still having problems with my driver :( References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Larry S. Lile on Sat, Jul 11, 1998 at 03:47:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I limited this to -hackers only, as it isn't really a tokenring problem. On Sat, Jul 11, 1998 at 03:47:07PM -0400, Larry S. Lile wrote: > > I still cannot get the upper network layers to respond to incoming > packets. I even hacked tcpdump to make sure that I was no wrecking > the packets as I took them off the wire. > > 15:29:58.698564 arp who-has anatok tell blastok (0:0:83:2d:9f:35) > hardware #6 > 15:29:59.588735 cyntok > anatok: icmp: echo request > 15:30:00.590438 cyntok > anatok: icmp: echo request > tcpdump: WARNING: compensating for unaligned libpcap packets > (^- anybody know how to fix this?) > 15:30:03.499586 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) > win 16384 > 15:30:09.271262 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) > win 16384 > 15:30:09.702343 arp who-has anatok tell blastok (0:0:83:2d:9f:35) > hardware #6 > > The only messages I got indicating anything at all is wrong were > these when I ifconfig the card up for the first time after a > reboot. > > Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway > Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, > 10.0.0.255.520): No buffer space available > Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 > --> 10.0.0.1: File exists > > Any ideas what might be wrong, or could someone please look at my > code and help me figure this out. If ping -f gives the same "no buffer space available", it probably originate here (around line 333 in netinet/ip_output.c): /* * Verify that we have any chance at all of being able to queue * the packet or packet fragments */ if ((ifp->if_snd.ifq_len + ip->ip_len / ifp->if_mtu + 1) >= ifp->if_snd.ifq_maxlen) { error = ENOBUFS; goto bad; } If this is the case, it is due to your driver not pulling packets off the output queue (or not doing it fast enough). What to do about it depend on the internals of your driver. The 'file exists' comes from an already existing route being overwritten - that part of it shouldn't be a problem, I think. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 03:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10219 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 03:21:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10214 for ; Mon, 13 Jul 1998 03:21:28 -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.8.7/8.8.7) with ESMTP id KAA09251; Mon, 13 Jul 1998 10:21:24 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA27268; Mon, 13 Jul 1998 12:21:24 +0200 (MET DST) Message-ID: <19980713122124.39089@follo.net> Date: Mon, 13 Jul 1998 12:21:24 +0200 From: Eivind Eklund To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: Still having problems with my driver :( References: <199807120558.WAA28581@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199807120558.WAA28581@usr07.primenet.com>; from Terry Lambert on Sun, Jul 12, 1998 at 05:58:22AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Limited to -hackers only. On Sun, Jul 12, 1998 at 05:58:22AM +0000, Terry Lambert wrote: > > The only messages I got indicating anything at all is wrong were > > these when I ifconfig the card up for the first time after a > > reboot. > > > > Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway > > Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, > > 10.0.0.255.520): No buffer space available > > Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 > > --> 10.0.0.1: File exists > > > > Any ideas what might be wrong, or could someone please look at my > > code and help me figure this out. > > This happens to me on my ppp link if I start pinging, but turn my > modem off (yes, I do bizarre things to see what would happen on > border cases) so the link can't come up. > > Typically, it means that outbound packets haven't been sent, and the > output queue has filled up. In the PPP case, it probably means it has done a blocking operation somehow, one the original author thought "wouldn't take time". iij-ppp relied heavily on non-blocking mode last time I looked ;-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 04:00:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14707 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 04:00:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from amor.wcs.uq.edu.au (amor.wcs.uq.edu.au [130.102.222.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14697 for ; Mon, 13 Jul 1998 04:00:06 -0700 (PDT) (envelope-from gdr@amor.wcs.uq.edu.au) Received: (from gdr@localhost) by amor.wcs.uq.edu.au (8.8.8/8.8.8) id UAA10245 for freebsd-hackers@FreeBSD.ORG; Mon, 13 Jul 1998 20:58:34 +1000 (EST) (envelope-from gdr) From: Gary Roberts Message-Id: <199807131058.UAA10245@amor.wcs.uq.edu.au> Subject: 3Com 3C589 Ethernet PC Card To: freebsd-hackers@FreeBSD.ORG Date: Mon, 13 Jul 1998 20:58:34 +1000 (EST) Organisation: Well Control Australia Phone: +617 3844 0400 Fax: +617 3844 0444 Reply-To: gdr@wcs.uq.edu.au (Gary Roberts) X-Mailer: ELM [version 2.4ME+ PL38 (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'm having occasional lockups when doing large NFS file transfers to/from a 2.2.6-R Toshiba notebook using the above card and the zp driver. I've followed the various discussions about how 3C509 NICs suck :-) and I'm wondering if the 3C589 might be tarred with the same brush. I'd like to get a PC Card ethernet that doesn't lockup and I have the opportunity to get rid of the 3C589 to another machine running Win95 so I'm looking for informed opinions about what is regarded as the best type of PC Card ethernet for FreeBSD. I understand there are ethernet/modem combo cards around. Anyone have any experience with any of those under FreeBSD. Thanks for any advice. Cheers, -- Gary Roberts (gdr@wcs.uq.edu.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 06:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26762 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 06:17:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26753 for ; Mon, 13 Jul 1998 06:17:45 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id PAA04993 ; Mon, 13 Jul 1998 15:16:10 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id PAA25743; Mon, 13 Jul 1998 15:16:09 +0200 To: "Jordan K. Hubbard" Cc: Joe McGuckin , dhw@whistle.com, hackers@FreeBSD.ORG Subject: Re: Changes to login.conf References: <12301.900311611@time.cdrom.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 13 Jul 1998 15:16:07 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of Sun, 12 Jul 1998 23:33:31 -0700 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > It wouldn't be the Unix philosophy, for one thing. As one person put > it, "Unix doesn't stop you from doing stupid things since that would > also stop you from doing clever things." More importantly, doing > "silent enforcement" is something which is only bound to bite you on > the ass. > [...] Hear, hear. But there's no reason not to write a Perl script or C program which goes through login.conf and checks that the values are reasonably sane. DES (who wrote /usr/bin/chkgrp after the last such discussion...) -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 06:19:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27216 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 06:19:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27211 for ; Mon, 13 Jul 1998 06:19:27 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA25761 for ; Mon, 13 Jul 1998 06:18:56 -0700 (PDT) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id PAA05125 ; Mon, 13 Jul 1998 15:18:29 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id PAA25773; Mon, 13 Jul 1998 15:18:27 +0200 To: Christoph Kukulies Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.6 src tree broken? References: <199807121645.SAA08675@gilberto.physik.RWTH-Aachen.DE> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 13 Jul 1998 15:18:27 +0200 In-Reply-To: Christoph Kukulies's message of Sun, 12 Jul 1998 18:45:15 +0200 (MEST) Message-ID: Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies writes: > mount /dist > cd /dist/src > sh install.sh lib (after getting the same when doing sh install.sh all) > # sh install.sh lib > Extracting source component: lib > > gzip: stdout: Broken pipe > tar: child returned status 1 Try again, but with 'sh -x' instead of 'sh'. This should give you some clue to where the problem originates. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 06:21:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27412 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 06:21:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27382; Mon, 13 Jul 1998 06:21:08 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id PAA05191 ; Mon, 13 Jul 1998 15:20:29 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id PAA25797; Mon, 13 Jul 1998 15:20:27 +0200 To: Giannis Vlachos Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Script for dialup users References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 13 Jul 1998 15:20:27 +0200 In-Reply-To: Giannis Vlachos's message of Mon, 13 Jul 1998 10:11:24 +0300 (EET DST) Message-ID: Lines: 10 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Giannis Vlachos writes: > The users who they are connected using Win95 need a script > for automatically login (Not the old fashion type with the > black window verifacation login : and Password: ) PAP/CHAP support on the server side. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 06:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00272 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 06:42:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00267 for ; Mon, 13 Jul 1998 06:42:09 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id JAA13121; Mon, 13 Jul 1998 09:49:33 -0400 (EDT) Date: Mon, 13 Jul 1998 09:49:33 -0400 (EDT) From: Charles Youse To: Terry Lambert cc: jkh@time.cdrom.com, thorpej@nas.nasa.gov, dfr@nlsystems.com, dg@root.com, seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Subject: Re: Page size flexibility in FreeBSD VM? In-Reply-To: <199807130445.VAA25307@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently working on the secondary boot loader. I'm reworking and restructuring the boot code from NetBSD. Just a word of warning, though: I don't have an Ultra yet, so consequently this code runs on hardware that is a couple of generations old. Chuck Youse On Mon, 13 Jul 1998, Terry Lambert wrote: > > Well, the port to sun4m (sparc32) is soon underway, with ultrasparc > > following (soon as I get my hands on a board ;). > > Let me know where you stand. I recently bought a SPARC box for > porting work, but have as yet not unpacked it because I promised > myself I would get some other code done before I started sucking > up my free time on something like that... > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 06:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00906 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 06:49:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00901 for ; Mon, 13 Jul 1998 06:49:49 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA26792 for ; Mon, 13 Jul 1998 06:49:10 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id PAA12564; Mon, 13 Jul 1998 15:49:13 +0200 (MEST) (envelope-from kuku) Message-ID: <19980713154913.A12529@gil.physik.rwth-aachen.de> Date: Mon, 13 Jul 1998 15:49:13 +0200 From: Christoph Kukulies To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , Christoph Kukulies Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.6 src tree broken? References: <199807121645.SAA08675@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91 In-Reply-To: =?iso-8859-1?Q?=3Crx4sok57uu4=2Efsf=40oslo=2Egeco-prakla=2Eslb=2Ecom=3E?= =?iso-8859-1?Q?=3B_from_Dag-Erling_Coidan_Sm=F8rgrav_on_Mon=2C_Jul_13=2C?= =?iso-8859-1?Q?_1998_at_03:18:27PM_+0200?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 03:18:27PM +0200, Dag-Erling Coidan Smørgrav wrote: > Christoph Kukulies writes: > > mount /dist > > cd /dist/src > > sh install.sh lib (after getting the same when doing sh install.sh all) > > # sh install.sh lib > > Extracting source component: lib > > > > gzip: stdout: Broken pipe > > tar: child returned status 1 > > Try again, but with 'sh -x' instead of 'sh'. This should give you some > clue to where the problem originates. Really strange. Unreproducable. Space was 400 MB free. I checked all MD5 sums and all were OK. CD Media? ATAPI CDR driver? > > DES > -- > Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 07:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02873 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 07:01:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.sminter.com.ar (ns1.sminter.com.ar [200.10.100.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02866 for ; Mon, 13 Jul 1998 07:01:23 -0700 (PDT) (envelope-from fpscha@ns1.sminter.com.ar) Received: (from fpscha@localhost) by ns1.sminter.com.ar (8.8.5/8.8.4) id KAA06424 for hackers@freebsd.org; Mon, 13 Jul 1998 10:58:30 -0300 (GMT) From: Fernando Schapachnik Message-Id: <199807131358.KAA06424@ns1.sminter.com.ar> Subject: ARP not on local network To: hackers@FreeBSD.ORG Date: Mon, 13 Jul 1998 10:58:30 -0300 (GMT) X-Mailer: ELM [version 2.4 PL25] 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 Hello: Some weeks ago I posted a question regarding some extrange messgaes I found in my syslog related to ARP. My system was reporting he wasn't able to resolv via ARP an address that by no means could be on my network. Now I think I know what's all about. Bay Networks 5399 Access Servers implement RFC 1868 ("unarp"), a proposed extension to ARP to announce that a host is leaving the network. More information on http://sunsite.auc.dk/RFC/rfc/rfc1868.html. Maybe this is confusing FreeBSD? Regards! Fernando P. Schapachnik Administracion de la red S&M Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 07:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06309 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 07:22:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06302 for ; Mon, 13 Jul 1998 07:22:41 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA00975; Mon, 13 Jul 1998 16:19:22 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id KAA04341; Mon, 13 Jul 1998 10:07:32 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807130807.KAA04341@semyam.dinoco.de> To: "Allen Smith" Subject: Re: Best means of telling if a proc is still around? In-reply-to: Your message of "Sun, 12 Jul 1998 22:45:30 EDT." <9807122245.ZM24864@beatrice.rutgers.edu> Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Mon, 13 Jul 1998 10:07:31 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. What's the best fast means of telling if a reference to a proc > structure is still valid? I'm needing this for the work on privileges > that I'm doing. (Specifically, there are circumstances where an action > initiated by a process that then exits may be a privileged one, and > may not get to the point of checking the privileges before the exit > takes place.) Use at_exit(9) to know when it exits. If it is important to you an at_exec(9) might be needed, too. The latter does not exist, yet. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 07:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09932 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 07:42:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09926 for ; Mon, 13 Jul 1998 07:42:47 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id HAA08166 for hackers@freebsd.org; Mon, 13 Jul 1998 07:42:07 -0700 (PDT) (envelope-from dhw) Date: Mon, 13 Jul 1998 07:42:07 -0700 (PDT) From: David Wolfskill Message-Id: <199807131442.HAA08166@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: Changes to login.conf In-Reply-To: <199807130639.XAA00272@usr07.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Terry Lambert >Date: Mon, 13 Jul 1998 06:39:40 +0000 (GMT) >Well, this is more along the lines of a schema based system, where you >say "here is the proposed changes, are they consistent?". >It's more useful that they be globally consistent than that they be >merely internally consistent. Quite. >This moves into the real of LDAP and subschema enforcement, I think. That's a possible implementation, sure. In case it isn't Real Obvious(!) yet, I try to avoid jumping to implementation concerns too quickly.... :-} >You could also consider the case of a modification to the bind >configuration information that would result in both upper and lower >case versions of the same host name. Yes, though I'd class the nameserver "reality checking" as rather distinct from /etc/rc*-checking (though the rc-checking probably ought to do a reality check with the nameservers the host in question uses). >There should be a method for proposing a group of changes as an atomic >unit, and having them vetted (or rejected) as a unit. Yes -- something that is capable of eating the global config stuff without getting too much indigestion. :-} It could start fairly limited, and if it were well-designed, could expand -- direction of expansion being toward areas where more analgesics are required (typically, from self-inflicted injuries).... And if it weren't well-designed, well, then, it would either stagnate (& be forgotten), or change: if for the better, great; if not, it could die. And since it need not be an integral part of anything, its fate would have minimal impact on anyone or -thing else.... unless, of course, it became so useful for enough folks that they kept working on it.... :-} david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 08:38:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16303 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 08:38:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA16298 for ; Mon, 13 Jul 1998 08:38:44 -0700 (PDT) (envelope-from shigio@wafu.netgate.net) Message-Id: <199807131538.IAA16298@hub.freebsd.org> Received: (qmail 15523 invoked from network); 13 Jul 1998 07:38:31 -0000 Received: from ins173.tama-ap3.dti.ne.jp (HELO choota.signet.or.jp) (203.181.69.227) by wafu.netgate.net with SMTP; 13 Jul 1998 07:38:31 -0000 Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.7/) with ESMTP id AAA03049; Tue, 14 Jul 1998 00:40:17 +0900 (JST) To: hackers@FreeBSD.ORG Cc: shigio@wafu.netgate.net Subject: Improvement of ln(1). [Second RFC] Date: Tue, 14 Jul 1998 00:40:17 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, About improved ln(1), I have written short examples and alpha version's manual. Current implementation is here. http://wafu.netgate.net/tama/unix/pathconvert.tar.gz Comments appreciated. Thank you in advance. ------------------------------------------------------------------------------ Short examples: Ex1: You can make right and relative (or absolute) symbolic link without thinking where you are and where symbolic link will be made. % cd /usr/src/sys % ls -l kern/tty.c -rw-r--r-- 1 root wheel 56525 Jul 3 09:27 kern/tty.c % ln -sf kern/tty.c ~/tmp % ls -l ~/tmp/tty.c lrwxrwxrwx 1 shigio users 10 Jul 13 18:08 /home/shigio/tmp/tty.c -> kern/tty.c ~~~~~~~~~~ (wrong symbolic link) % ln -sfr kern/tty.c ~/tmp % ls -l ~/tmp/tty.c lrwxrwxrwx 1 shigio users 31 Jul 13 13:28 /home/shigio/tmp/tty.c -> ../../../usr/src/sys/kern/tty.c ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (right and relative symbolic link) % ln -sfa kern/tty.c ~/tmp % ls -l ~/tmp/tty.c lrwxrwxrwx 1 shigio users 31 Jul 13 13:28 /home/shigio/tmp/tty.c -> /usr/src/sys/kern/tty.c ~~~~~~~~~~~~~~~~~~~~~~~ (right and absolute symbolic link) Ex2: You can make symbolic link even if the target isn't exist. (This is a spec of symbolic link. ln(1) doens't print warning message.) % cd /usr/src/sys % ls -l kern/noexist.c ls: kern/noexist.c: No such file or directory % ln -sr kern/noexist.c ~/tmp % ls -l ~/tmp/noexist.c lrwxrwxrwx 1 shigio users 36 Jul 13 17:53 /home/shigio/tmp/noexist.c -> ../../../usr/src/sys/kern/noexist.c ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (not exist but right symbolic link) Ex3: You can make shadow tree with relative symbolic link like this. % cd /usr/src/sys % set obj=/usr/obj`pwd` % mkdir -p $obj % find * -type d -exec mkdir $obj/'{}' ';' % find * -type f -exec ln -sr '{}' $obj/'{}' ';' ------------------------------------------------------------------------------ LN(1) FreeBSD General Commands Manual LN(1) NAME ln - make links SYNOPSIS ln [-afrs] source_file [target_file] ln [-afrs] source_file ... [target_dir] DESCRIPTION The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining multiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy. There are two types of links; hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard or symbolic link. The options are as follows: -a If the -s option is specified, make absolute symbolic link. -f Unlink any already existing file, permitting the link to occur. -r If the -s option is specified, make relative symbolic link. -s Create a symbolic link. If neither -a nor -r option are speci- fied, all done is copy the exact 'source_file' name into the link as- is. The -a and -r options override each other; the last one specified deter- mines the method used. By default ln makes hard links. A hard link to a file is indistinguish- able from the original directory entry; any changes to a file are effec- tive independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file systems. A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The read- link(2) call may be used to read the contents of a symbolic link. Sym- bolic links may span file systems and may refer to directories. Given one or two arguments, ln creates a link to an existing file 'source_file'. If 'target_file' is given, the link has that name; 'target_file' may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the link will be made to the last component of 'source_file'. Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the files being linked to. SEE ALSO link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7) HISTORY A ln command appeared in Version 1 AT&T UNIX. 4th Berkeley Distribution December 30, 1993 1 ------------------------------------------------------------------------------ Following functions are used in improved ln(1). ------------------------------------------------------------------------------ ABS2REL(3) FreeBSD Library Functions Manual ABS2REL(3) NAME abs2rel - make a relative path name from an absolute path SYNOPSIS char * abs2rel(const char *path, const char *base, char *result, size_t size) DESCRIPTION The abs2rel() function makes a relative path name from an absolute path name 'path' based on a directory 'base' and copies the resulting path name into the memory referenced by 'result'. The 'result' argument must refer to a buffer capable of storing at least 'size' characters. The resulting path name may include symbolic links. The abs2rel() func- tion doesn't check whether or not any path exists. RETURN VALUES The abs2rel() function returns relative path name on success. If an er- ror occurs, it returns NULL. ERRORS The abs2rel() function may fail and set the external variable errno to indicate the error. [EINVAL] The 'base' directory isn't an absolute path name or the 'size' argument is zero. [ERANGE] The 'size' argument is greater than zero but smaller than the length of the pathname plus 1. EXAMPLE char result[MAXPATHLEN]; char *path = abs2rel("/usr/src/sys", "/usr/local/lib", result, MAX- PATHLEN); yields: path == "../../src/sys" Similarly, path1 = abs2rel("/usr/src/sys", "/usr", result, MAXPATHLEN); path2 = abs2rel("/usr/src/sys", "/usr/src/sys", result, MAXPATHLEN); yields: path1 == "src/sys" path2 == "." BUGS If the base directory includes symbolic links, the abs2rel() function produces the wrong path. For example, if '/sys' is a symbolic link to '/usr/src/sys', char *path = abs2rel("/usr/local/lib", "/sys", result, MAXPATHLEN); yields: path == "../usr/local/lib" /* It's wrong!! */ You should convert the base directory into a real path in advance. path = abs2rel("/sys/kern", realpath("/sys", resolvedname), result, MAXPATHLEN); yields: path == "../../../sys/kern" /* It's correct but ... */ That is correct, but a little redundant. If you wish get the simple an- swer 'kern', do the following. path = abs2rel(realpath("/sys/kern", r1), realpath("/sys", r2), result, MAXPATHLEN); The realpath() function assures correct result, but don't forget that realpath() requires that all but the last component of the path exist. SEE ALSO rel2abs(3) BSD Dec 15, 1997" 2 ------------------------------------------------------------------------------ REL2ABS(3) FreeBSD Library Functions Manual REL2ABS(3) NAME rel2abs - make an absolute path name from a relative path SYNOPSIS char * rel2abs(const char *path, const char *base, char *result, size_t size) DESCRIPTION The rel2abs() function makes an absolute path name from a relative path name 'path' based on a directory 'base' and copies the resulting path name into the memory referenced by 'result'. The 'result' argument must refer to a buffer capable of storing at least 'size' character The resulting path name may include symbolic links. abs2rel() doesn't check whether or not any path exists. RETURN VALUES The rel2abs() function returns absolute path name on success. If an er- ror occurs, it returns NULL. ERRORS The rel2abs() function may fail and set the external variable errno to indicate the error. [EINVAL] The 'base' directory isn't an absolute path name or the 'size' argument is zero. [ERANGE] The 'size' argument is greater than zero but smaller than the length of the pathname plus 1 EXAMPLE char result[MAXPATHLEN]; char *path = rel2abs("../../src/sys", "/usr/local/lib", result, MAX- PATHLEN); yields: path == "/usr/src/sys" Similarly, path1 = rel2abs("src/sys", "/usr", result, MAXPATHLEN); path2 = rel2abs(".", "/usr/src/sys", result, MAXPATHLEN); yields: path1 == "/usr/src/sys" path2 == "/usr/src/sys" SEE ALSO abs2rel(3) BSD Dec 3, 1997" 1 ------------------------------------------------------------------------------ -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 08:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17303 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 08:46:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2 (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA17297 for ; Mon, 13 Jul 1998 08:46:11 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2 (SMI-8.6/8.6.9) with SMTP id LAA26420; Mon, 13 Jul 1998 11:45:58 -0400 Date: Mon, 13 Jul 1998 11:45:57 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: Nathan Ahlstrom cc: hackers Subject: Re: Question about shadow object collapse 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 Try this one: http://www.cs.cmu.edu/afs/cs/project/mach/public/www/doc/tutorials.html If fail, search for "Mach" with a web searcher. Good Luck! -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- On Mon, 13 Jul 1998, Nathan Ahlstrom wrote: > Hello, > > Could you provide a URL for the mentioned paper? > > Thank You. > > Nathan > > > According to the Mach paper "Machine-Independent Virtual Memory Management > > for Paged Uniprocessor and Multiprocessor Architectures", a shadow object > > > > > Nathan Ahlstrom > nrahlstr@winternet.com > Run FreeBSD: 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 Jul 13 13:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00491 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 13:38:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA00474; Mon, 13 Jul 1998 13:38:15 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id PAA23160; Mon, 13 Jul 1998 15:35:42 -0500 Received: from stlabcexg004.anheuser-busch.com(unknown 151.145.101.160) by gatewaya via smap (V2.1) id xma023109; Mon, 13 Jul 98 15:35:30 -0500 Received: by stlabcexg004.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3QYWQRAT>; Mon, 13 Jul 1998 21:38:39 +0100 Message-ID: <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011> From: "Alton, Matthew" To: "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Software RAID Date: Mon, 13 Jul 1998 21:38:37 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody working on software RAID? Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 13:42:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01359 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 13:42:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01348 for ; Mon, 13 Jul 1998 13:42:38 -0700 (PDT) (envelope-from julian@FreeBSD.org) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id NAA13011 for hackers; Mon, 13 Jul 1998 13:42:04 -0700 (PDT) Date: Mon, 13 Jul 1998 13:42:04 -0700 (PDT) Message-Id: <199807132042.NAA13011@freefall.freebsd.org> To: hackers@FreeBSD.ORG Subject: test Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wertwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 13:43:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01518 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 13:43:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from julian@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01510 for hackers; Mon, 13 Jul 1998 13:43:24 -0700 (PDT) (envelope-from julian) Date: Mon, 13 Jul 1998 13:43:24 -0700 (PDT) From: Julian Elischer Message-Id: <199807132043.NAA01510@hub.freebsd.org> To: hackers Subject: tracking down hackers fubar Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sdfsdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 13:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04355 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 13:55:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hq.freegate.com (freegate.com [208.226.86.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA04344 for ; Mon, 13 Jul 1998 13:55:10 -0700 (PDT) (envelope-from ravi@freegate.com) Received: (qmail+freegate 24520 invoked by alias); 13 Jul 1998 20:55:01 -0000 Received: from ws3-n0.hq.freegate.com (HELO ravi.hq.freegate.com) (208.226.86.131) by hq.freegate.com with SMTP; 13 Jul 1998 20:55:01 -0000 Reply-To: From: "Ravi Duvvuri" To: Subject: Compacting FFS filesystem Date: Mon, 13 Jul 1998 13:48:20 -0700 Message-ID: <000501bdae9f$93eda4e0$8356e2d0@ravi.hq.freegate.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to reduce the size of an existing FFS filesystem partition without losing data. I want to reparation the existing drive so that the new partition size is equal (or close) to the actual number of used blocks in the partition. I need to do this without dumping the filesystem to tape or some other backup media. Ravi Duvvuri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 14:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15367 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 14:47:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15351; Mon, 13 Jul 1998 14:47:46 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id PAA06102; Mon, 13 Jul 1998 15:46:35 -0600 (MDT) Message-Id: <199807132146.PAA06102@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Alton, Matthew" cc: "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Re: Software RAID In-reply-to: Your message of "Mon, 13 Jul 1998 21:38:37 BST." <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 15:41:23 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is anybody working on software RAID? There is supposedly some work being done in the NetBSD environment to pull RaidFrame into their kernel. You may want to get involved with that effort. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 15:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21114 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 15:17:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21102; Mon, 13 Jul 1998 15:17:28 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA412; Tue, 14 Jul 1998 00:15:39 +0200 Message-ID: <35AA872E.3D07CE1D@pipeline.ch> Date: Tue, 14 Jul 1998 00:16:14 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Re: Software RAID References: <199807132146.PAA06102@pluto.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin T. Gibbs wrote: > > >Is anybody working on software RAID? > > There is supposedly some work being done in the NetBSD environment to > pull RaidFrame into their kernel. You may want to get involved with > that effort. Terry did that already for FreeBSD: http://www.freebsd.org/~terry -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 15:19:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21711 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 15:19:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21686; Mon, 13 Jul 1998 15:19:35 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id QAA07976; Mon, 13 Jul 1998 16:19:26 -0600 (MDT) Message-Id: <199807132219.QAA07976@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "IBS / Andre Oppermann" cc: "Justin T. Gibbs" , "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Re: Software RAID In-reply-to: Your message of "Tue, 14 Jul 1998 00:16:14 +0200." <35AA872E.3D07CE1D@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 16:14:14 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> There is supposedly some work being done in the NetBSD environment to >> pull RaidFrame into their kernel. You may want to get involved with >> that effort. > >Terry did that already for FreeBSD: http://www.freebsd.org/~terry Last I heard, Terry had ported the userland implementation to FreeBSD, not the kernel one. The kernel stuff would actually give reasonable performance since the userland code doesn't have "real threads" to rely on. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 15:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26352 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 15:46:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26330; Mon, 13 Jul 1998 15:46:26 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id WAA12655; Mon, 13 Jul 1998 22:43:41 GMT Date: Tue, 14 Jul 1998 07:43:40 +0900 (JST) From: Michael Hancock To: "Alton, Matthew" cc: "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Re: Software RAID In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011> 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://www.lemis.com/vinum.html On Mon, 13 Jul 1998, Alton, Matthew wrote: > Is anybody working on software RAID? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 16:07:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29619 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 16:07:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bb.cc.wa.us (chris@bb.cc.wa.us [134.39.181.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29602; Mon, 13 Jul 1998 16:07:24 -0700 (PDT) (envelope-from chris@bb.cc.wa.us) Received: from localhost (chris@localhost) by bb.cc.wa.us (8.8.8/8.6.9) with SMTP id XAA02434; Mon, 13 Jul 1998 23:02:08 GMT Date: Mon, 13 Jul 1998 16:02:08 -0700 (PDT) From: Chris Coleman To: "Alton, Matthew" cc: "'Hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Subject: Re: Software RAID In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011> 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 Isn't vinum that Greg Lehey working on supposed to do RAID. At least RAID0 now and RAID5 soon. Christopher J. Coleman (whyareyou@lookingforme.com) Computer Support Analyst I (509)-762-6341 FreeBSD Book Project: http://www.vmunix.com/fbsd-book/ On Mon, 13 Jul 1998, Alton, Matthew wrote: > Is anybody working on software RAID? > > Matthew Alton > Computer Services - UNIX Systems Administration > (314)632-6644 matthew.alton@anheuser-busch.com > alton@plantnet.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 16:31:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04176 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 16:31:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04171; Mon, 13 Jul 1998 16:31:34 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA05632; Mon, 13 Jul 1998 16:31:28 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd005560; Mon Jul 13 16:31:22 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA15175; Mon, 13 Jul 1998 16:31:08 -0700 (MST) From: Terry Lambert Message-Id: <199807132331.QAA15175@usr08.primenet.com> Subject: Re: Software RAID To: gibbs@plutotech.com (Justin T. Gibbs) Date: Mon, 13 Jul 1998 23:31:08 +0000 (GMT) Cc: andre@pipeline.ch, gibbs@plutotech.com, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG, FreeBSD-fs@FreeBSD.ORG In-Reply-To: <199807132219.QAA07976@pluto.plutotech.com> from "Justin T. Gibbs" at Jul 13, 98 04:14:14 pm X-Mailer: ELM [version 2.4 PL25] 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 > >> There is supposedly some work being done in the NetBSD environment to > >> pull RaidFrame into their kernel. You may want to get involved with > >> that effort. > > > >Terry did that already for FreeBSD: http://www.freebsd.org/~terry > > Last I heard, Terry had ported the userland implementation to FreeBSD, > not the kernel one. This is correct. I did the userspace port, and I sent the patches back to the maintainer; in theory it should work "out of the box". Which begs the question: "who is going through all the ports and sending those patches back to the maintainers so FreeBSD is supported out of the box?". > The kernel stuff would actually give reasonable > performance since the userland code doesn't have "real threads" to rely > on. I think the value of quote-unquote "real threads" has been greatly exaggerated; kernel threads result in SMP scalability and higher context switch overhead and more interleaved I/O, and that's presuming something has been done about scheduler and processor affinity (I have yet to see John Dyson's patches for this committed, however, even though Elvind and other have copies). The biggest overhead in a software RAID 5 is the software instead of hardware checksum calculation, and that's going to be a much higher penalty than non-interleaved I/O (IMO; writes are typically interleaved, and where you care about reads, you will be set to trigger read-ahead). Software RAID is a data integrity issue, not a performance one, and I think making the performance argument for whatever reason (protection domain crossing, interleaved I/O, SMP scalability, etc.) is a strawman at best. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 16:34:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04882 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 16:34:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04845 for ; Mon, 13 Jul 1998 16:33:58 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA29390; Mon, 13 Jul 1998 16:33:53 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd029371; Mon Jul 13 16:33:51 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA15497; Mon, 13 Jul 1998 16:33:49 -0700 (MST) From: Terry Lambert Message-Id: <199807132333.QAA15497@usr08.primenet.com> Subject: Re: Compacting FFS filesystem To: ravi@freegate.com Date: Mon, 13 Jul 1998 23:33:49 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <000501bdae9f$93eda4e0$8356e2d0@ravi.hq.freegate.com> from "Ravi Duvvuri" at Jul 13, 98 01:48:20 pm X-Mailer: ELM [version 2.4 PL25] 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 > Is there any way to reduce the size of an existing FFS filesystem partition > without losing data. I want to reparation the existing drive so that > the new partition size is equal (or close) to the actual number of used > blocks in the partition. I need to do this without dumping the filesystem > to tape or some other backup media. Yes. Theo DeRaddt wrote some code to do this. Check the -current list archives on ww.freebsd.org, where it was discussed at length in a thread on logical volume management. I posted the URL, but I don't have it in the bookmarks of my current desktop. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 16:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08024 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 16:50:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08010 for ; Mon, 13 Jul 1998 16:50:18 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id TAA09981; Mon, 13 Jul 1998 19:48:44 -0400 (EDT) From: "Allen Smith" Message-Id: <9807131948.ZM9979@beatrice.rutgers.edu> Date: Mon, 13 Jul 1998 19:48:44 -0400 In-Reply-To: Stefan Eggers "Re: Best means of telling if a proc is still around?" (Jul 13, 10:07am) References: <199807130807.KAA04341@semyam.dinoco.de> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Stefan Eggers Subject: Re: Best means of telling if a proc is still around? Cc: freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 13, 10:07am, Stefan Eggers (possibly) wrote: > > Hi. What's the best fast means of telling if a reference to a proc > > structure is still valid? I'm needing this for the work on privileges > > that I'm doing. (Specifically, there are circumstances where an action > > initiated by a process that then exits may be a privileged one, and > > may not get to the point of checking the privileges before the exit > > takes place.) > > Use at_exit(9) to know when it exits. If it is important to you an > at_exec(9) might be needed, too. The latter does not exist, yet. Sorry; I wasn't clear enough. The situation I'm worried about is the following: A. process does system call or other action requiring a privilege check (for something other than uid 0, which is already checked for in, for example, socreate). The system call returns to avoid blocking, say, a rt process. B. process exits C. system call or other action gets to the point of the privilege check D. privilege check attempts to access privilege flags, associated with the process, that aren't there E. all hell breaks loose because it's accessing a now-nonsense memory location I don't want to do the checking at A, since a lot of times that would mean doing a full-scale interpretation of what the system call is doing at the time of the call, which is likely to be a duplication of the stuff happening later. I suppose I could do an at_exit call at each such system call, but that's going to result in a definite slowdown. Yeah, I know, I'm being a perfectionist - this combination isn't _that_ likely to happen (indeed, I'm not sure if there are any circumstances in which it _can_ happen currently) - but I'd prefer to fix the potential problem now before it bites somebody trying to add capabilities to the system who won't be as familiar with the workings of this as I will be (since I'm writing it). -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 17:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10133 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 17:01:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10116 for ; Mon, 13 Jul 1998 17:01:06 -0700 (PDT) (envelope-from wadlow@tw.com) Received: from tw.com (millennium.tw.com [140.174.99.21]) by mail-oak-1.pilot.net with ESMTP id RAA17946 for ; Mon, 13 Jul 1998 17:00:56 -0700 (PDT) Received: from hotspur.tw.com ([140.174.99.210]) by tw.com with SMTP id RAA10498 for ; Mon, 13 Jul 1998 17:04:20 -0700 (PDT) Received: from localhost (wadlow@localhost) by hotspur.tw.com (8.6.10/8.6.10) with SMTP id QAA08135 for ; Mon, 13 Jul 1998 16:58:20 -0700 X-Authentication-Warning: hotspur.tw.com: wadlow owned process doing -bs Date: Mon, 13 Jul 1998 16:58:19 -0700 (PDT) From: Tom Wadlow To: hackers@FreeBSD.ORG Subject: Problem with swap under 3.0-980524-SNAP 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've got an odd problem with swap space on my machine, namely, it doesn't seem to be using any. Machine: HP Kayak (Pentium II) Memory: 128M Disk: 4.3 GB SCSI /etc/fstab (with allocations shown in parens): /dev/sd0s1b none swap sw 0 0 (500MB) /dev/sd0s1a / ufs rw 1 1 (100MB) /dev/sd0s1g /export/home ufs rw 2 2 (2.1GB) /dev/sd0s1f /usr ufs rw 2 2 (1.4GB) /dev/sd0s1e /var ufs rw 2 2 (200MB) proc /proc procfs rw 0 0 Unusual things about this workstation: Two-headed display (two Matrox Millenium II's) XIG Multiheaded X11R6 instead of XFree86 (which doesn't support multihead) Kernel config: GENERIC with the mods described below FAQ: Yes, I looked, but I couldn't find anything helpful for this. Description: I'm just in the process of finalizing the setup of this system for my primary use (moving off Sun boxes for the first time in more than a decade, for whatever that's worth). Got most things working, but then ran into a problem where I ran out of pseudo-ttys. Looking through the FAQ, I figured out how to up them to the (documented) max of 64 in the kernel. Did so. Made more pseudo-ttys in /dev via MAKEDEV. Rebooted. Everything seemed to work. Ran a little script to start creating rxvts one per second to see how much stress I could put on the system. I expected this to get up into the 50s or low 60s with the kernel mods. Instead, it went up from 16 (the previous limit) to about 24, then started getting "Cannot fork" errors. I stopped the script, and everything else I tried could not fork either. Killed a few windows, enough to see that it looked like a swap problem, as in, "I am out of swap". This surprised me. So I did a "pstat -T" 136/1320 files 0M/499M swap space Hmmmm, not touching the swap space.... So I ran the test again, this time with "top" running. Turns out that the system starts hanging when mem usage gets up near the 128M border, which is the amount of RAM I have in the system. The pstat output never lifts off 0, which says to me that the system isn't using any of the 500MB of swap that I built into it. "pstat -s" says this: Device 1K-blocks Used Avail Capacity Type /dev/sd0s1b 512000 0 511872 0% Interleaved which seems to imply that the system knows about my swap space at some level as that is the correct swap volume. It is just not choosing to use that space as swap space. Any thoughts? --Tom P.S. Is the max ptys still 64 (as it says in the FAQ)? The MAKEDEV seems to imply 240 are trivially possible, with more requiring a little edit of MAKEDEV. I may try it in the kernel just to see what happens, but while I'm addressing this august body, I might as well do a little pre-emptive lobbying for more if need be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 17:55:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19496 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 17:55:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mage.dt.wdc.com (fission.dt.wdc.com [129.253.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19487 for ; Mon, 13 Jul 1998 17:55:47 -0700 (PDT) (envelope-from kehlet@dt.wdc.com) Received: from cygnus.dt.wdc.com (root@[172.31.1.2]) by mage.dt.wdc.com (8.8.8/8.8.8) with ESMTP id RAA01164; Mon, 13 Jul 1998 17:55:36 -0700 (PDT) Received: from hydra-X4 (kehlet@hydra-X4 [172.31.1.11]) by cygnus.dt.wdc.com (8.8.8/8.8.8) with SMTP id RAA08592; Mon, 13 Jul 1998 17:50:38 -0700 (PDT) Date: Mon, 13 Jul 1998 17:55:06 -0700 (PDT) From: Steven Kehlet X-Sender: kehlet@hydra-X4 Reply-To: Steven Kehlet To: Jonny cc: hackers@FreeBSD.ORG Subject: Re: Assembly.. 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 Hey, after searching through the source for as I think there must be a bug or something. The as that comes with FreeBSD is "a pre-alpha version of the GNU assembler, version 1.92.3". The latest is 2.8.1. Sounds suspect. It looks like it should accept two args to lcall if the first is an immediate 16 bit value and the second an "absolute" value (preceeded by a '*'--this is new to me). But even trying to give the second value as an absolute, i.e. "lcall $0x7,*0x0", it still won't compile. I'll try downloading binutils and compiling the newest gas for FreeBSD sometime... I did however find a way around this... just use .byte and generate the machine language yourself: .byte 0x9a # opcode for lcall .long 0x0 # this will yield "lcall 0x7,0x0" .word 0x7 # A gdb disassemble will show: (gdb) disass main Dump of assembler code for function main: 0x15b0
: pushl $0x0 0x15b2 : leal 0x1,%eax 0x15b8 : pushl 0x1234 0x15be : lcall 0x7,0x0 End of assembler dump. (gdb) ... just like it should. Oh yeah, though, there's one more weird thing. Note that "pushl 0x1234" I stuck in there. I found you need to push this garbage value onto the stack before doing the lcall. It looks like the normal flow (which everyone keeps saying to do) is to call _exit, which then lcalls the system call. So there's a return value there on the stack from the call to _exit, which the kernel must skip when looking for the exit value you provide. If you don't do this, you'll get garbage for an exit value. Go figure. So here's the final product: .text .globl _main _main: pushl $0x0 # exit value leal 0x1,%eax # 1 is system call code for exit pushl 0x1234 # push a junk word onto stack # because syscall expects value .byte 0x9a # opcode for lcall .long 0x0 # this will yield "lcall 0x7,0x0" .word 0x7 # END: # so gdb stops disassembly here Woohoo! Nothing like spending a day figuring this out on company time ;-). Steve On Mon, 13 Jul 1998, Jonny wrote: > Date: Mon, 13 Jul 1998 19:20:52 -0400 (EDT) > From: Jonny > To: Steven Kehlet > Subject: Re: Assembly.. > > sure man, i have been at this for a couple of weeks now > and have gotten little or no information, everyone is like > just use call syscallName, which is fine but i want to know > how it works through and through, gcc -S shows it as > lcall 0x7,0x0 why will it now assemble when you write > the src yourself. also your correct in the different > in linux and freebsd.. the pushing onto the stack in fbsd > those i get np. thank you though for your input.. i will > be sure to email you anything i get on the matter. > > On Mon, 13 Jul 1998, Steven Kehlet wrote: > > > Same here. I've been trying to get this to work myself for about a > > week. Even the gcc info pages confirm the form "lcall 0x7,0x0", which > > doesn't compile: > > > > * Immediate form long jumps and calls are `lcall/ljmp $SECTION, > > $OFFSET' in AT&T syntax; the Intel syntax is `call/jmp far > > SECTION:OFFSET'. Also, the far return instruction is `lret > > $STACK-ADJUST' in AT&T syntax; Intel syntax is `ret far > > STACK-ADJUST'. > > > > > > ??? If someone mails you the answer, mind forwarding it to me? > > Thanks... also one thing.. FreeBSD pushes its arguments to the system > > calls on the stack, as opposed to Linux which puts them in registers. > > The system call code is put in %eax. > > > > So the asm for exit is (I think ;-)): > > > > pushl $0 # exit status > > leal 0x1,%eax # 0x1 is call code for exit > > lcall 0x7,0x0 > > > > > > Steve > > > > > > > > On Sat, 11 Jul 1998, Jonny wrote: > > > > > Date: Sat, 11 Jul 1998 15:08:34 -0400 (EDT) > > > From: Jonny > > > To: Luoqi Chen > > > Cc: hackers@freebsd.org > > > Subject: Re: Assembly.. > > > > > > > > call 0x7,0x0 > > > > > > > > It should be a `far' call: lcall 0x7,0x0. > > > > > > > > -lq > > > > > > right, my bust. even so i continue to get operands dont match any known > > > 386 instruction. > > > > > > -> going out of my head =) > > > > > > > > > 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 Jul 13 18:09:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21322 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 18:09:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21311; Mon, 13 Jul 1998 18:09:23 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807140109.SAA21311@hub.freebsd.org> Subject: Re: test In-Reply-To: <199807132042.NAA13011@freefall.freebsd.org> from Julian Elischer at "Jul 13, 98 01:42:04 pm" To: julian@FreeBSD.ORG (Julian Elischer) Date: Mon, 13 Jul 1998 18:09:23 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > wertwe > julian, please, never send test messages to any list but freebsd-test@freebsd.org. you will want to subscribe to the list first. i know that you know better than this ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 18:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23685 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 18:29:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23662; Mon, 13 Jul 1998 18:29:51 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id KAA13777; Tue, 14 Jul 1998 10:59:44 +0930 (CST) Message-ID: <19980714105944.C754@freebie.lemis.com> Date: Tue, 14 Jul 1998 10:59:44 +0930 From: Greg Lehey To: Matthew Alton , Hackers@FreeBSD.ORG, FreeBSD-fs@FreeBSD.ORG Subject: Re: Software RAID References: <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF90177660A@STLABCEXG011>; from Alton, Matthew on Mon, Jul 13, 1998 at 09:38:37PM +0100 WWW-Home-Page: http://www.lemis.com/~grog 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, 13 July 1998 at 21:38:37 +0100, Alton, Matthew wrote: > Is anybody working on software RAID? Yes, I am. I see you've already followed up the URL (http://www.lemis.com/vinum.html; thanks, Chris). Greg -- See complete headers for address 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 Jul 13 19:38:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02777 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 19:38:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02772; Mon, 13 Jul 1998 19:38:20 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id KAA16747; Tue, 14 Jul 1998 10:37:20 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA10232; Tue, 14 Jul 1998 10:37:46 +0800 Message-Id: <199807140237.KAA10232@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: How do you tell (within the kernel) if we started setuid? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 10:37:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're executing a program that was started setuid root but has subsequently given up its privileges, is there anyway to tell if it was originally set uid? Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 20:01:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05888 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 20:01:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05878 for ; Mon, 13 Jul 1998 20:01:36 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id MAA13966; Tue, 14 Jul 1998 12:29:52 +0930 (CST) Message-ID: <19980714122952.L754@freebie.lemis.com> Date: Tue, 14 Jul 1998 12:29:52 +0930 From: Greg Lehey To: Terry Lambert , "Justin T. Gibbs" Cc: andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG Subject: Re: Software RAID-5 performance References: <199807132219.QAA07976@pluto.plutotech.com> <199807132331.QAA15175@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807132331.QAA15175@usr08.primenet.com>; from Terry Lambert on Mon, Jul 13, 1998 at 11:31:08PM +0000 WWW-Home-Page: http://www.lemis.com/~grog 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 (trimming -fs) On Monday, 13 July 1998 at 23:31:08 +0000, Terry Lambert wrote: >>>> There is supposedly some work being done in the NetBSD environment to >>>> pull RaidFrame into their kernel. You may want to get involved with >>>> that effort. >>> >>> Terry did that already for FreeBSD: http://www.freebsd.org/~terry >> >> Last I heard, Terry had ported the userland implementation to FreeBSD, >> not the kernel one. > > This is correct. > > I did the userspace port, and I sent the patches back to the maintainer; > in theory it should work "out of the box". > >> The kernel stuff would actually give reasonable >> performance since the userland code doesn't have "real threads" to rely >> on. > > The biggest overhead in a software RAID 5 is the software instead > of hardware checksum calculation, and that's going to be a much > higher penalty than non-interleaved I/O (IMO; writes are typically > interleaved, and where you care about reads, you will be set to > trigger read-ahead). Don't overestimate the penalty of checksum calculations. Sure, they're an issue, but recall that it takes maybe one instruction per byte written to perform the checksum. Before you write, you must read, so you're not going to checksum more than, say, 5 MB/s per controller. That doesn't take up much CPU on a modern processor. I'm currently running some tests on vinum running on a degraded array. The CPU is a 486/66, the controller a 2940UW, and the disks are CDC 94181s, admittedly pretty slow. The CPU is running at 97% idle, interrupt time (where the checksums are done) is running at 1.9%. With a set of fast disks, this might go up to 20% to 25%, but that's still not bad for a 486/66. Non-interleaved I/O, on the other hand, can be a big penalty (if we're talking about the same thing). If I have an array with 5 drives, each capable of a realistic 5 MB/s, and a stripe width of 64 kB, and I write 256 kB to it, I need to do: 1. *Don't* read in the old blocks. If you're completely replacing the stripe, you have all the information you need to calculate the parity block. 2. Calculate parity. On the 486/66, this looks like being about 8 ms. 3. Write the blocks. If you can do this in parallel, it'll take about 13 ms. Serially, it'll take about 50 ms. Of course, this comparison isn't the real issue. If I can transfer at 20 MB/s to the RAID controller, the penalty disappears. But the potential is there, and I'm comparing worst case: fast disks, fast controller, slow processor. > Software RAID is a data integrity issue, not a performance one, > and I think making the performance argument for whatever reason > (protection domain crossing, interleaved I/O, SMP scalability, > etc.) is a strawman at best. I'm not sure that I understand what you're saying here. Obviously offloading the checksum calculation (or anything else, for that matter) to an external box will offload the CPU. And I can't see any particular difference in data integrity between the two approaches. Greg -- See complete headers for address 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 Jul 13 21:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13978 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 21:20:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13973 for ; Mon, 13 Jul 1998 21:20:51 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id XAA03325; Mon, 13 Jul 1998 23:20:29 -0500 (CDT) (envelope-from dan) Message-ID: <19980713232028.A3128@emsphone.com> Date: Mon, 13 Jul 1998 23:20:28 -0500 From: Dan Nelson To: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: How do you tell (within the kernel) if we started setuid? References: <199807140237.KAA10232@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807140237.KAA10232@ariadne.tensor.pgs.com>; from "Stephen Hocking-Senior Programmer PGS Tensor Perth" on Tue Jul 14 10:37:46 GMT 1998 X-OS: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [dropped -current list] In the last episode (Jul 14), Stephen Hocking-Senior Programmer PGS Tensor Perth said: > > If you're executing a program that was started setuid root but has > subsequently given up its privileges, is there anyway to tell if it > was originally set uid? >From a quick look at the kernel source, it looks like checking for (p->p_flag & P_SUGID) will do what you want (check to see if the process is 'tainted'). See the issetugid(2) man page for more info, or grep the kernel source for P_SUGID :) -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 Mon Jul 13 22:08:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18330 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 22:08:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18325 for ; Mon, 13 Jul 1998 22:08:27 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-137.camalott.com [208.229.74.137]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id AAA17627; Tue, 14 Jul 1998 00:08:57 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA00726; Tue, 14 Jul 1998 00:08:11 -0500 (CDT) (envelope-from joelh) Date: Tue, 14 Jul 1998 00:08:11 -0500 (CDT) Message-Id: <199807140508.AAA00726@detlev.UUCP> To: kehlet@dt.wdc.com CC: jvz@ns.nternet.net, hackers@FreeBSD.ORG In-reply-to: (message from Steven Kehlet on Mon, 13 Jul 1998 17:55:06 -0700 (PDT)) Subject: Re: Assembly.. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > is 2.8.1. Sounds suspect. It looks like it should accept two args > to lcall if the first is an immediate 16 bit value and the second > an "absolute" value (preceeded by a '*'--this is new to me). But > even trying to give the second value as an absolute, i.e. "lcall > $0x7,*0x0", it still won't compile. I'll try downloading binutils > and compiling the newest gas for FreeBSD sometime... I really can't look at the rest of it, but a '*' is used to mark an absolute jump or call (as opposed to an IP relative jump/call). Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 13 23:01:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24393 for freebsd-hackers-outgoing; Mon, 13 Jul 1998 23:01:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24388 for ; Mon, 13 Jul 1998 23:01:31 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA19209; Mon, 13 Jul 1998 23:01:24 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd019171; Mon Jul 13 23:01:20 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA00726; Mon, 13 Jul 1998 23:01:13 -0700 (MST) From: Terry Lambert Message-Id: <199807140601.XAA00726@usr06.primenet.com> Subject: Re: Software RAID-5 performance To: grog@lemis.com (Greg Lehey) Date: Tue, 14 Jul 1998 06:01:13 +0000 (GMT) Cc: tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG In-Reply-To: <19980714122952.L754@freebie.lemis.com> from "Greg Lehey" at Jul 14, 98 12:29:52 pm X-Mailer: ELM [version 2.4 PL25] 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 > Non-interleaved I/O, on the other hand, can be a big penalty (if we're > talking about the same thing). If I have an array with 5 drives, each > capable of a realistic 5 MB/s, and a stripe width of 64 kB, and I > write 256 kB to it, I need to do: We are talking about read(2) calls occuring serially, and write(2) calls occurring non-serially, presuming write(2) is implemented correctly for the non-blocking I/O case. This means that reads will trigger a fetch, but return an EWOULDBLOCK, and writes copy to a buffer (presuming, as you did, that you will be writing a stripe, which puts it on a page boundry with a page increment). > 2. Calculate parity. On the 486/66, this looks like being about 8 > ms. This is the overhead I was referring to. > 3. Write the blocks. If you can do this in parallel, it'll take > about 13 ms. Serially, it'll take about 50 ms. Writes occur in parallel if they are queued when the write is requested, and success is indicated by permission to write and available buffer space. Hard errors are a seperate issue. due to the nature of an async fd, I think it's safe to say that writes, at least in page increments on page boundries, complete immediately if there is buffer space, and therefore multiple user space threads writes are interleaved. For this case, it takes it from 13ms to 21 ms, or to be generous, one and a half times slower. > > Software RAID is a data integrity issue, not a performance one, > > and I think making the performance argument for whatever reason > > (protection domain crossing, interleaved I/O, SMP scalability, > > etc.) is a strawman at best. > > I'm not sure that I understand what you're saying here. Obviously > offloading the checksum calculation (or anything else, for that > matter) to an external box will offload the CPU. And I can't see any > particular difference in data integrity between the two approaches. If you have a specific need for RAID-5 assurances, then performance is a secondardy consideration. The next consideration after assumed fault tolerance requirements is the performance/money trade-off for hardware RAID 5 vs. software. I think performance will be secondary, so a performance argument is really secondary; you can throw money at the RAID-5 performance issues to make them go away. So even if there is a significant performance penalty (1.538 times slower is a significant penalty, IMO), if your application requires RAID-5, then it requires it at any cost. And if performance isn't an issue at that point, then pointing at user space threads as a bottleneck is the wrong thing to do (and it isn't even the bottleneck it is blamed as being; the overhead from non-interleaved reads (which are effectively interleaved read-ahead requests, followed by serial copy-from-cache, which means "about as fast as you can get, since you have to copy anyway") is negligible compared to the overhead you are already willing to eat to get the fault tolerance. There's a tiny increment, true, but it's much less than the additional overhead you'd get from kernel thread context switching on a UP kernel, or even on an SMP kernel, if you didn't have thread-CPU affinity. So the fact that FreeBSD currently has user space threads is pretty much a red herring. The performance penalty for user space threads, and the performance benefit for kernel space threads won't affect this particular (I/O bound) application anyway, unlees your box is (1) SMP and (2) has CPU affinity code; if it does, you can cut the time from 16ms for two operations to 8ms for two operations (still 128% of the time it would take with hardware RAID-5). The losses from user space threading in RAIDFrame are negligible. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 03:13:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14569 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 03:13:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14564 for ; Tue, 14 Jul 1998 03:13:05 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id MAA17920 for hackers@FreeBSD.ORG; Tue, 14 Jul 1998 12:12:58 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id MAA05366 for hackers@FreeBSD.ORG; Tue, 14 Jul 1998 12:06:05 +0200 (CEST) (envelope-from roberto) Message-ID: <19980714120605.A5227@keltia.freenix.fr> Date: Tue, 14 Jul 1998 12:06:05 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: How do you tell (within the kernel) if we started setuid? Mail-Followup-To: hackers@FreeBSD.ORG References: <199807140237.KAA10232@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807140237.KAA10232@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Tue, Jul 14, 1998 at 10:37:46AM +0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Stephen Hocking-Senior Programmer PGS Tensor Perth: > If you're executing a program that was started setuid root but has > subsequently given up its privileges, is there anyway to tell if it was > originally set uid? There is a system call about this. It looks for a special flag in the process entry. NAME issetugid - is current process tainted by uid or gid changes int issetugid(p, uap) register struct proc *p; struct issetugid_args *uap; { /* * Note: OpenBSD sets a P_SUGIDEXEC flag set at execve() time, * we use P_SUGID because we consider changing the owners as * "tainting" as well. * This is significant for procs that start as root and "become" * a user without an exec - programs cannot know *everything* * that libc *might* have put in their data segment. */ if (p->p_flag & P_SUGID) return (1); return (0); } -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 04:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23822 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 04:29:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.225.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23806 for ; Tue, 14 Jul 1998 04:29:40 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from freenet.bishkek.su (freenet.bishkek.su [193.125.230.1]) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id RAA06577 for ;Tue, 14 Jul 1998 17:15:32 +0600 (KGST) Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id RAA29927 for ; Tue, 14 Jul 1998 17:18:46 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id RAA25983 for ; Tue, 14 Jul 1998 17:20:29 +0300 Date: Tue, 14 Jul 1998 17:20:29 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: freebsd-hackers@FreeBSD.ORG Subject: Kernel dies. 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 people, I have recompiled kernel (2.2.1) and added Firewalls options to it, and since that, it started rebooting nearly every 15 minutes. Here's the message it displayed before going down: --------------- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1. processor eflags = interrupt enabled, resume, IOPL = 0 current process = 62 (routed) interrupt mask = kernel: type 12 trap, code = 0 ----------------- Any ideas what could be wrong? I suppose there might be some problem with routed daemon and firewalling options. But anyone knows what exactly goes wrong here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 06:36:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03199 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 06:36:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA03193 for ; Tue, 14 Jul 1998 06:36:12 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw2.att.com; Tue Jul 14 08:16 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id IAA07738 for ; Tue, 14 Jul 1998 08:35:58 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <37TTYYKZ>; Tue, 14 Jul 1998 09:35:44 -0400 Message-ID: To: shigio@wafu.netgate.net Cc: hackers@FreeBSD.ORG Subject: RE: Improvemnet of ln(1). Date: Tue, 14 Jul 1998 09:35:40 -0400 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 > From: Shigio Yamaguchi [SMTP:shigio@wafu.netgate.net] > > > > [Problem] > > > > > > Ln(1) with -s option makes illegal symbolic link in some case. > > > For example, > > > > > > (Both '/usr/src/sys' and '/tmp' are real directories.) > > > > > > % cd /usr > > > % ln -s src/sys /tmp > > > % ls -l /tmp/sys > > > lrwxrwxrwx 1 shigio wheel 7 Jul 11 02:03 /tmp/sys -> src/sys > > > % cd /tmp/sys > > > /tmp/sys: No such file or directory. > > > > > > Symbolic link '/tmp/sys' has illegal value, so we cannot move > there. > > > Above behavior is not desireble in almost case, I think. > > > > > > [Solution] > > > > > ln -s `pwd`/src/sys /tmp > > > > Isn't it simpler ? > > But it forces user to use absolute symbolic link. > Do the relative symbolic links make any sense outside of subdirectory hierarchy ? Of course, you can do it as ../usr/src/sys and it may be useful in some cases but would it make any sense here? -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 06:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04026 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 06:40:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bytor.rush.net (lynch@bytor.rush.net [209.45.245.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04007; Tue, 14 Jul 1998 06:40:40 -0700 (PDT) (envelope-from lynch@rush.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.1/8.8.8) with SMTP id JAA23316; Tue, 14 Jul 1998 09:40:24 -0400 (EDT) (envelope-from lynch@rush.net) Date: Tue, 14 Jul 1998 09:40:22 -0400 (EDT) From: Pat Lynch To: Gary Roberts cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: 3Com 3C589 Ethernet PC Card In-Reply-To: <199807131058.UAA10245@amor.wcs.uq.edu.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 having problems with a 3c589? thats weird, I have two of them and they work great. I'm actually using the ep0 driver (the one for the 3c509) with the PAO package. also, this might have been a better question for -questions instead of -hackers ___________________________________________________________________________ Pat Lynch lynch@rush.net Systems Administrator Rush Networking ___________________________________________________________________________ On Mon, 13 Jul 1998, Gary Roberts wrote: > I'm having occasional lockups when doing large NFS file transfers to/from > a 2.2.6-R Toshiba notebook using the above card and the zp driver. I've > followed the various discussions about how 3C509 NICs suck :-) and I'm > wondering if the 3C589 might be tarred with the same brush. > > I'd like to get a PC Card ethernet that doesn't lockup and I have the > opportunity to get rid of the 3C589 to another machine running Win95 so > I'm looking for informed opinions about what is regarded as the best > type of PC Card ethernet for FreeBSD. > > I understand there are ethernet/modem combo cards around. Anyone have any > experience with any of those under FreeBSD. Thanks for any advice. > > Cheers, > -- > Gary Roberts (gdr@wcs.uq.edu.au) > > 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 Jul 14 07:18:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08460 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 07:18:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08454 for ; Tue, 14 Jul 1998 07:18:35 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA07289; Tue, 14 Jul 1998 10:18:46 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 10:18:46 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Tom Wadlow cc: hackers@FreeBSD.ORG Subject: Re: Problem with swap under 3.0-980524-SNAP 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 please look at /etc/login.conf you are hitting limits on your login class. -Alfred On Mon, 13 Jul 1998, Tom Wadlow wrote: > I'm just in the process of finalizing the setup of this system for my > primary use (moving off Sun boxes for the first time in more than a > decade, for whatever that's worth). Got most things working, but then > ran into a problem where I ran out of pseudo-ttys. Looking through the > FAQ, I figured out how to up them to the (documented) max of 64 in the > kernel. Did so. Made more pseudo-ttys in /dev via MAKEDEV. Rebooted. > Everything seemed to work. > > Ran a little script to start creating rxvts one per second to see how much > stress I could put on the system. I expected this to get up into the 50s > or low 60s with the kernel mods. Instead, it went up from 16 (the > previous limit) to about 24, then started getting "Cannot fork" errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 07:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09398 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 07:27:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09391 for ; Tue, 14 Jul 1998 07:27:06 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA07334; Tue, 14 Jul 1998 10:27:08 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 10:27:08 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: hackers@FreeBSD.ORG Subject: Re: How do you tell (within the kernel) if we started setuid? In-Reply-To: <199807140237.KAA10232@ariadne.tensor.pgs.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 don't crosspost please. NAME issetugid - is current process tainted by uid or gid changes DESCRIPTION The issetugid() function returns 1 if the process environment or memory address space is considered ``tainted'', and returns 0 otherwise. A process is tainted if it was created as a result of an execve(2) system call which had either of the setuid or setgid bits set (and extra privi- leges were given as a result) or if it has changed any of it's real, ef- fective or saved user or group ID's since it began execution. -alfred On Tue, 14 Jul 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > If you're executing a program that was started setuid root but has > subsequently given up its privileges, is there anyway to tell if it was > originally set uid? > > > Stephen > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 07:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11374 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 07:41:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11366 for ; Tue, 14 Jul 1998 07:41:03 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA07348; Tue, 14 Jul 1998 10:35:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 10:35:14 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: CyberPsychotic cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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's REALLY time you upgraded. 2.2.1 has accumilated a long list of holes, you are vulnerable to several TCP/IP DoS attacks as well as vulnerabilities in the userland tools get a copy of 2.2.6 (maybe 2.2.7, it' out i heard) you should be fine -Alfred On Tue, 14 Jul 1998, CyberPsychotic wrote: > Hello people, > I have recompiled kernel (2.2.1) and added Firewalls options to it, and > since that, it started rebooting nearly every 15 minutes. Here's the > message it displayed before going down: > > --------------- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1. > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 62 (routed) > interrupt mask = > kernel: type 12 trap, code = 0 > ----------------- > > Any ideas what could be wrong? I suppose there might be some problem with > routed daemon and firewalling options. But anyone knows what exactly goes > wrong here? > > > 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 Jul 14 08:12:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16650 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 08:12:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from stennis.ca.sandia.gov (bmah@stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16629 for ; Tue, 14 Jul 1998 08:12:53 -0700 (PDT) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.1/8.9.1) id IAA26885; Tue, 14 Jul 1998 08:12:44 -0700 (PDT) Message-Id: <199807141512.IAA26885@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Cc: bmah@CA.Sandia.GOV Subject: Package version checker From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-368376312P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 14 Jul 1998 08:12:44 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-368376312P Content-Type: text/plain; charset=us-ascii Hello -hackers... I've written a Perl 5 script that checks the installed version of ports/packages against an index file (a la /usr/ports/INDEX, or the on-line equivalent) to see which ones might be out of date. I'm not real proud of this quick hack, but if it'd be useful to anyone, I've put it at: http://www.ca.sandia.gov/~bmah/pub/pkg_version/ If something like this already exists, and I just didn't RTFM closely enough, well, at least I learned a little more about Perl... Cheers, Bruce. --==_Exmh_-368376312P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNat1a6jOOi0j7CY9AQFN+AP7BQhd45+BkBy2QMNYFVgYMRWCfbrdS+zi 4GdicgxbIJcIUe6Y8GdHeDmKe6RlGq95fBYMkTCh5/s1nw+60jNZNUUrpgs39mQR 13crwtXEmUPe46rHylcdqClDmViMBDeNn+2j4FpYE9mQsmcb1jzry4Fq5Mh1wH7s IR/k1bAHwRU= =K+wH -----END PGP MESSAGE----- --==_Exmh_-368376312P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 08:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18565 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 08:28:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA18558 for ; Tue, 14 Jul 1998 08:28:08 -0700 (PDT) (envelope-from shigio@wafu.netgate.net) Message-Id: <199807141528.IAA18558@hub.freebsd.org> Received: (qmail 18812 invoked from network); 14 Jul 1998 07:27:52 -0000 Received: from ins46.tama-ap3.dti.ne.jp (HELO choota.signet.or.jp) (203.181.67.46) by wafu.netgate.net with SMTP; 14 Jul 1998 07:27:52 -0000 Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.7/) with ESMTP id AAA01259; Wed, 15 Jul 1998 00:29:33 +0900 (JST) To: sbabkin@dcn.att.com cc: shigio@wafu.netgate.net, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Message from sbabkin@dcn.att.com of "Tue, 14 Jul 1998 09:35:40 -0400." Date: Wed, 15 Jul 1998 00:29:33 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: sbabkin@dcn.att.com > > > ln -s `pwd`/src/sys /tmp > > > > > > Isn't it simpler ? > > > > But it forces user to use absolute symbolic link. > > > Do the relative symbolic links make any sense outside of subdirectory > hierarchy ? > Of course, you can do it as ../usr/src/sys and it may be useful in some > cases but > would it make any sense here? Do you mean a symbolic link including root directory is useless? You are right. My example was bad. How about this example? % ln -sr /usr/src/sys/kern/tty.c /usr/obj/usr/src/sys/kern/tty.c % ls -l !$ lrwxrwxrwx 1 shigio bin 33 Jul 14 23:56 /usr/obj/usr/src/sys/kern/tty.c -> ../../../../../src/sys/kern/tty.c This symbolic link is solved in the '/usr' subdirectory. So, you can mount /usr file system at any point. -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 08:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18786 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 08:29:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18780 for ; Tue, 14 Jul 1998 08:29:21 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id LAA23671 for ; Tue, 14 Jul 1998 11:29:36 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 11:29:36 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: freebsd-hackers@FreeBSD.ORG Subject: ATAPI reset? 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 has anyone looked into setting up a real way to reset the atapi bus? it's kinda bad when i manually control my cdrom drive and it locks up all programs that attempt to use it. for referance: -current of about 2-3 days ago dmesg wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wcd0: 2412/5512Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked i get this on my consol: wcd0: cannot read audio disc wcd0: cannot read audio disc atapi1.0: invalid command phase, ireason=0xd0, status=d0, error=d0 atapi1.0: invalid command phase, ireason=0xd8, status=d8, error=d8 atapi1.0: controller not ready for cmd atapi1.0: controller not ready for cmd atapi1.0: controller not ready for cmd thanks, Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 08:36:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19933 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 08:36:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19928 for ; Tue, 14 Jul 1998 08:36:27 -0700 (PDT) (envelope-from shmit@natasya.kublai.com) Received: from natasya.kublai.com (natasya.kublai.com [207.172.25.236]) by coleridge.kublai.com (8.8.8/8.8.8) with ESMTP id LAA07589; Tue, 14 Jul 1998 11:36:20 -0400 (EDT) (envelope-from shmit@natasya.kublai.com) Received: (from shmit@localhost) by natasya.kublai.com (8.8.8/8.8.8) id LAA23207; Tue, 14 Jul 1998 11:36:18 -0400 (EDT) Message-ID: <19980714113618.23544@kublai.com> Date: Tue, 14 Jul 1998 11:36:18 -0400 From: Brian Cully To: Steven Kehlet , Jonny Cc: hackers@FreeBSD.ORG Subject: Re: Assembly.. Reply-To: shmit@kublai.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Steven Kehlet on Mon, Jul 13, 1998 at 05:55:06PM -0700 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 05:55:06PM -0700, Steven Kehlet wrote: > (gdb) disass main > Dump of assembler code for function main: > 0x15b0
: pushl $0x0 > 0x15b2 : leal 0x1,%eax > 0x15b8 : pushl 0x1234 > 0x15be : lcall 0x7,0x0 > End of assembler dump. > (gdb) > > ... just like it should. Oh yeah, though, there's one more weird thing. > Note that "pushl 0x1234" I stuck in there. I found you need to > push this garbage value onto the stack before doing the lcall. I noticed the same thing when I was doing it with int $0x80, and not lcall. What is the purpose of that value? From looking in /sys/i386/i386/trap.c it appears to be ignored: params = (caddr_t)frame.tf_esp + sizeof(int); Did it used to be used to hold an RTA or something? -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 08:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20917 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 08:46:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20908 for ; Tue, 14 Jul 1998 08:46:26 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) for freebsd-hackers@freebsd.org id 0yw7HQ-0007iY-00; Tue, 14 Jul 1998 17:46:12 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id PAA02610 for ; Tue, 14 Jul 1998 15:42:16 +0200 (SAT) Date: Tue, 14 Jul 1998 15:42:15 +0200 (SAT) From: Peter van Heusden Reply-To: Peter van Heusden To: freebsd-hackers@FreeBSD.ORG Subject: Detecting the presence of threads (for a port) 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've been merging Terry Lambert's patches to ldap-3.3 (which include the Critical Angle patches as well as some of Terry's own) with the existing ldap port, and managed to get a working build (which needs an hour or two of cleaning up). The port, however, requires pthreads, which requires libc_r. I was wondering how to deal with this. Two questions: 1) How to detect the existence of pthreads? I assume a pre-configure test for libc_r should do? 2) Should pthreads be required in the default port? Since they are not available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case I'd have to break the pthread patches out into a seperate set of files, and only apply them if a particular make variable is set. Does this make sense? P.S. Who else (if anyone) is working on ldap at present? Thanks, Peter -- Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 09:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27085 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 09:28:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beelzebubba.sysabend.org (grail@beelzebubba.sysabend.org [209.48.124.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27074 for ; Tue, 14 Jul 1998 09:28:33 -0700 (PDT) (envelope-from grail@beelzebubba.sysabend.org) Received: (from grail@localhost) by beelzebubba.sysabend.org (8.8.5/8.8.5) id MAA25951; Tue, 14 Jul 1998 12:28:31 -0400 (EDT) Message-ID: <19980714122831.A25859@beelzebubba.sysabend.org> Date: Tue, 14 Jul 1998 12:28:31 -0400 From: Giao Nguyen To: Peter van Heusden , freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting the presence of threads (for a port) Mail-Followup-To: Peter van Heusden , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Peter van Heusden on Tue, Jul 14, 1998 at 03:42:15PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter van Heusden said: > > P.S. Who else (if anyone) is working on ldap at present? Me. I'm reading up on the ldap docs and source and eventually adopting the port once I've caught up on everything. Giao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 09:44:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00578 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 09:44:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hq.freegate.com (freegate.com [208.226.86.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA00570 for ; Tue, 14 Jul 1998 09:44:13 -0700 (PDT) (envelope-from ravi@freegate.com) Received: (qmail+freegate 14747 invoked by alias); 14 Jul 1998 16:44:04 -0000 Received: from ws3-n0.hq.freegate.com (HELO ravi.hq.freegate.com) (208.226.86.131) by hq.freegate.com with SMTP; 14 Jul 1998 16:44:04 -0000 Reply-To: From: "Ravi Duvvuri" To: "'Terry Lambert'" , Cc: Subject: RE: Compacting FFS filesystem Date: Tue, 14 Jul 1998 09:37:19 -0700 Message-ID: <001d01bdaf45$ab9c66c0$8356e2d0@ravi.hq.freegate.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199807132333.QAA15497@usr08.primenet.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I searched under http://www.freebsd.org/search.html#mailinglists but could not find any thing. Can you post the URL? or give me anyother pointers to this. Thankx -Ravi -----Original Message----- From: Terry Lambert [mailto:tlambert@primenet.com] Sent: Monday, July 13, 1998 4:34 PM To: ravi@freegate.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Compacting FFS filesystem > Is there any way to reduce the size of an existing FFS filesystem partition > without losing data. I want to reparation the existing drive so that > the new partition size is equal (or close) to the actual number of used > blocks in the partition. I need to do this without dumping the filesystem > to tape or some other backup media. Yes. Theo DeRaddt wrote some code to do this. Check the -current list archives on ww.freebsd.org, where it was discussed at length in a thread on logical volume management. I posted the URL, but I don't have it in the bookmarks of my current desktop. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 09:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02382 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 09:53:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02377 for ; Tue, 14 Jul 1998 09:53:11 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA388; Tue, 14 Jul 1998 18:51:16 +0200 Message-ID: <35AB8CAB.4FF133B@pipeline.ch> Date: Tue, 14 Jul 1998 18:51:55 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Peter van Heusden CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting the presence of threads (for a port) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter van Heusden wrote: > > I've been merging Terry Lambert's patches to ldap-3.3 (which include the > Critical Angle patches as well as some of Terry's own) with the existing > ldap port, and managed to get a working build (which needs an hour or two > of cleaning up). The port, however, requires pthreads, which requires > libc_r. I was wondering how to deal with this. Two questions: > > 1) How to detect the existence of pthreads? I assume a pre-configure test > for libc_r should do? Simply check for libc_r. > 2) Should pthreads be required in the default port? Since they are not > available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case > I'd have to break the pthread patches out into a seperate set of files, > and only apply them if a particular make variable is set. Does this make > sense? You need it. Otherwise it won't work in any useful manner. > P.S. Who else (if anyone) is working on ldap at present? We are not working on it, but working with it. Theres one really big bug in Terry's patches (or in libc_r) that prevents ldif2ldap & co. from working (you'll get empty ddb files). I reported that to Terry but I don't know if he has fixed it yet. Lemme suggest another small thing: Please inlcude the Berkeley DB 2.x stuff into the LDAP-3.3 port (LDAP isn't really useful without it). And yet another thing: Netscape released their LDAP client lib stuff to the public on www.mozilla.org, it needs also an port but I'm far too busy at the moment to do it. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 10:55:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10184 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 10:55:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10178 for ; Tue, 14 Jul 1998 10:55:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA04019; Tue, 14 Jul 1998 10:54:21 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Peter van Heusden cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting the presence of threads (for a port) In-reply-to: Your message of "Sat, 14 Jul 1998 15:42:15 +0200." Date: Tue, 14 Jul 1998 10:54:21 -0700 Message-ID: <4015.900438861@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2) Should pthreads be required in the default port? Since they are not > available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case > I'd have to break the pthread patches out into a seperate set of files, > and only apply them if a particular make variable is set. Does this make > sense? You could always wimp out on this one and simply stop if you don't find a libc_r in the obvious place, telling the user to go compile that bit and come back. 2.2.7, due in just 7 days now (eek!), will have it by default and, of course, 3.0 does as well so relying on it just being installed is not as bad as it sounds. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 11:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12809 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 11:08:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12758 for ; Tue, 14 Jul 1998 11:07:57 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id UAA17407; Tue, 14 Jul 1998 20:00:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id TAA02916; Tue, 14 Jul 1998 19:01:49 +0200 (CEST) (envelope-from andreas) Message-ID: <19980714190149.A1062@klemm.gtn.com> Date: Tue, 14 Jul 1998 19:01:49 +0200 From: Andreas Klemm To: Alfred Perlstein , CyberPsychotic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alfred Perlstein on Tue, Jul 14, 1998 at 10:35:14AM -0500 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 10:35:14AM -0500, Alfred Perlstein wrote: > it's REALLY time you upgraded. 2.2.1 has accumilated a long list of holes, > you are vulnerable to several TCP/IP DoS attacks as well as > vulnerabilities in the userland tools > > get a copy of 2.2.6 (maybe 2.2.7, it' out i heard) you should be fine update /usr/src using cvsup cd /usr/src make buildworld make installworld That's the advantage of FreeBSD over xxx ... ;-) Fine tune /etc/rc scripts on demand with things in /usr/src/etc manually ... New is the main config file rc.conf instead of system.conf (if I remember right) ... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 11:22:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15756 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 11:22:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15751 for ; Tue, 14 Jul 1998 11:22:38 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0yw9ig-0005mE-00; Tue, 14 Jul 1998 11:22:30 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA04384; Tue, 14 Jul 1998 11:22:14 -0700 Date: Tue, 14 Jul 1998 11:22:13 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Detecting the presence of threads (for a port) To: Peter van Heusden cc: freebsd-hackers@FreeBSD.ORG 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 Peter van Heusden wrote (in a slightly different order): > P.S. Who else (if anyone) is working on ldap at present? I've been working on setting up some LDAP-based facilities for my virtual domain customers. I haven't really dug into the ldap sources much though. > I've been merging Terry Lambert's patches to ldap-3.3 (which include the > Critical Angle patches as well as some of Terry's own) with the existing > ldap port, and managed to get a working build (which needs an hour or two > of cleaning up). The port, however, requires pthreads, which requires > libc_r. I was wondering how to deal with this. Two questions: > > 1) How to detect the existence of pthreads? I assume a pre-configure test > for libc_r should do? > > 2) Should pthreads be required in the default port? Since they are not > available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case > I'd have to break the pthread patches out into a seperate set of files, > and only apply them if a particular make variable is set. Does this make > sense? Hmmm. If pthreads were a port; I'd say just make it a dependancy and let the build auto-install it. On the whole, I'm inclined to go ahead and require it. Add a test to the top-level Makefile that emits a message and aborts if it can't find libc_r or pthread.h. The message should briefly indicate how to install pthreads; or at least where to find that info. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 11:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19847 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 11:43:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19842 for ; Tue, 14 Jul 1998 11:43:29 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0ywA2u-0005xW-00; Tue, 14 Jul 1998 11:43:24 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA04396; Tue, 14 Jul 1998 11:43:20 -0700 Date: Tue, 14 Jul 1998 11:43:20 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Detecting the presence of threads (for a port) To: IBS / Andre Oppermann cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG In-Reply-To: <35AB8CAB.4FF133B@pipeline.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 > We are not working on it, but working with it. Theres one really big > bug in Terry's patches (or in libc_r) that prevents ldif2ldap & co. > from working (you'll get empty ddb files). I reported that to Terry > but I don't know if he has fixed it yet. It looks like the original code makes some silly assumptions about uninitialized variables being set to zero. The following patches seemed to make it work for me. But I wouldn't be surprised if there are more uninitialized variable bugs... *** ldif2id2children.c.old Mon Jan 19 18:21:59 1998 --- ldif2id2children.c Wed Jun 24 22:30:39 1998 *************** *** 63,69 **** int dbnum; ID id; struct dbcache *db, *db2; ! Backend *be; struct berval bv; struct berval *vals[2]; Avlnode *avltypes = NULL; --- 63,69 ---- int dbnum; ID id; struct dbcache *db, *db2; ! Backend *be = NULL; struct berval bv; struct berval *vals[2]; Avlnode *avltypes = NULL; *** ldif2index.c.old Mon Jan 19 18:21:59 1998 --- ldif2index.c Wed Jun 24 22:04:58 1998 *************** *** 53,59 **** int lmax, lcur, indexmask, syntaxmask; int dbnum; unsigned long id; ! Backend *be; struct berval bv; struct berval *vals[2]; extern char *optarg; --- 53,59 ---- int lmax, lcur, indexmask, syntaxmask; int dbnum; unsigned long id; ! Backend *be = NULL; struct berval bv; struct berval *vals[2]; extern char *optarg; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 11:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20507 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 11:47:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20502 for ; Tue, 14 Jul 1998 11:47:01 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0ywA6K-0005zP-00; Tue, 14 Jul 1998 11:46:56 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA04399; Tue, 14 Jul 1998 11:46:52 -0700 Date: Tue, 14 Jul 1998 11:46:52 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Detecting the presence of threads (for a port) To: "Jordan K. Hubbard" cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG In-Reply-To: <4015.900438861@time.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 > > 2) Should pthreads be required in the default port? Since they are not > > available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case > > I'd have to break the pthread patches out into a seperate set of files, > > and only apply them if a particular make variable is set. Does this make > > sense? > > You could always wimp out on this one and simply stop if you don't > find a libc_r in the obvious place, telling the user to go compile > that bit and come back. ...... Errr, shouldn't that be "compile or install from the binary distribution"? It's easy to forget that many folks won't even install the system sources. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 12:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00431 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 12:32:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.kacst.edu.sa (ns1.kacst.edu.sa [198.77.88.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00385 for ; Tue, 14 Jul 1998 12:32:02 -0700 (PDT) (envelope-from onur@kfupm.edu.sa) Received: from ns1.kfupm.edu.sa ([198.77.102.26]) by relay.kacst.edu.sa (8.7.5/8.7.3) with ESMTP id WAA18367 for ; Tue, 14 Jul 1998 22:22:54 -0300 (GMT) Received: from dpc107.dpc.kfupm.edu.sa (dpc107.dpc.kfupm.edu.sa [196.15.33.198]) by ns1.kfupm.edu.sa (8.7.5/8.7.3) with ESMTP id WAA206084 for ; Tue, 14 Jul 1998 22:19:01 +0300 Received: from kfupm.edu.sa ([196.1.65.80]) by dpc107.dpc.kfupm.edu.sa (8.7.5/8.7.3) with ESMTP id WAA90237 for ; Tue, 14 Jul 1998 22:27:54 +0300 Message-ID: <35AC05B1.869474CA@kfupm.edu.sa> Date: Tue, 14 Jul 1998 22:28:17 -0300 From: Onur Toker Organization: KFUPM, CCSE X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FREEBSD Subject: YPSERV crashes with SOLARIS-2.6 References: <35AA83F5.36AD2548@netrover.com> <19980714143753.B1993@dcs.qmw.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, When I use the FreeBSD ypserv in unsecure mode and configure one Solaris-2.6 client and another FreeBSD client, ypserv crashes and gives the following error message Jul 13 17:30:53 pc-ftp-syslab /kernel: pid 88 (ypserv), uid 0: exited on signal 11 (core dumped) The FreeBSD client is able to change the passwords with no problem Jul 13 17:37:19 pc-ftp-syslab rpc.yppasswdd[92]: update completed for user onur (uid 1001): Jul 13 17:37:19 pc-ftp-syslab rpc.yppasswdd[92]: password changed But the Solaris box is rejected Jul 12 18:36:45 pc-ftp-syslab rpc.yppasswdd[92]: Access to master.passwd.byname denied -- client 196.1.65.80:32947 not privileged Jul 12 18:36:45 pc-ftp-syslab rpc.yppasswdd[92]: rejected update request from unauthorized host Is the port number 32947 causing the problem and ypserv to crash ? Well, my securenets file is # allow connections from local host -- mandatory 127.0.0.1 255.255.255.255 # allow connections from any host # on the 196.1.65.0 network 196.1.65.0 255.255.255.0 and both the FreeBSD client and the Solaris-2.6 is authorized. Why this crash occurs ? Why password change from Solaris-2.6 is rejected. PS: FreeBSD version = 2.2.1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 12:50:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02638 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 12:50:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA02629 for ; Tue, 14 Jul 1998 12:50:44 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA00215 (5.67b/IDA-1.5); Tue, 14 Jul 1998 21:40:36 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA03774; Tue, 14 Jul 1998 20:05:16 +0200 (CEST) From: Wilko Bulte Message-Id: <199807141805.UAA03774@yedi.iaf.nl> Subject: Re: Software RAID-5 performance In-Reply-To: <19980714122952.L754@freebie.lemis.com> from Greg Lehey at "Jul 14, 98 12:29:52 pm" To: grog@lemis.com (Greg Lehey) Date: Tue, 14 Jul 1998 20:05:16 +0200 (CEST) Cc: tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, 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+ PL38 (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 Greg Lehey wrote... > (trimming -fs) > > Software RAID is a data integrity issue, not a performance one, > > and I think making the performance argument for whatever reason > > (protection domain crossing, interleaved I/O, SMP scalability, > > etc.) is a strawman at best. > > I'm not sure that I understand what you're saying here. Obviously > offloading the checksum calculation (or anything else, for that > matter) to an external box will offload the CPU. And I can't see any > particular difference in data integrity between the two approaches. Software raid without stable (battery backed) storage is flawed: assume a write that had 2 disks actually write the data onto the platter and (e.g.) the parity data did not make it out on it's platter because your system crashed. Or the power went bang. Or... You now have an inconsistent raid5 set. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 12:52:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02872 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 12:52:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from trauco.colomsat.net.co ([200.13.195.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02829; Tue, 14 Jul 1998 12:52:17 -0700 (PDT) (envelope-from y-carden@uniandes.edu.co) Received: from [206.156.157.194] ([206.156.157.194]) by trauco.colomsat.net.co (8.8.8/8.8.8) with SMTP id OAA12119; Tue, 14 Jul 1998 14:52:58 +0500 (GMT) Message-ID: <35ABB85B.DFA180D3@uniandes.edu.co> Received: from YONNY by [206.156.157.194] via smtpd (for trauco.colomsat.net.co [200.13.195.2]) with SMTP; 14 Jul 1997 19:52:19 UT Date: Tue, 14 Jul 1998 14:58:19 -0500 From: Yonny Cardenas Baron Organization: Panamco Indega S.A X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: jseger@FreeBSD.ORG, hackers Subject: DHCP Server with 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, I have a problem with my ISC DHCP server in FreeBSD. The request of clients from other subnets not pass for a router Cisco 7500. Thanks for your help. ------------------------------------ YONNY CARDENAS B. e-mail: y-carden@uniandes.edu.co To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 13:34:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09968 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 13:34:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2 (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA09963 for ; Tue, 14 Jul 1998 13:34:31 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2 (SMI-8.6/8.6.9) with SMTP id QAA24139 for ; Tue, 14 Jul 1998 16:34:17 -0400 Date: Tue, 14 Jul 1998 16:34:17 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Wrong comment in pmap_bootstrap() about virtual_avail? 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 file i386/pmap.c, routine pmap_bootstrap(), I find the following comment: "XXX The calculation of virtual_avail is wrong. It's NKPT*PAGE_SIZE too large. It should be instead be correctly calculated in locore.s and not based on 'first'(which is a physical address, not a virtual address, for the start of unused physical memory)..." I read this comment a long while ago and still do not understand it. I believe that the calculation of virutal_avail which immediately follows is correct and 'firstaddr' has to be a physical address (PA + KERNBASE == VA). Why it is wrong? How come it is NKPT*PAGE_SIZE large? Anyway, this piece of code appears in freebsd-stable. If the code IS wrong, how can this bug not be removed? So maybe the comment is wrong. BTW, what does "XXX' mean which appear many times elsewhere? Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 13:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10033 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 13:34:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA10024 for ; Tue, 14 Jul 1998 13:34:42 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Tue Jul 14 15:34 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id PAA05700 for ; Tue, 14 Jul 1998 15:34:30 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <37TTY5N5>; Tue, 14 Jul 1998 16:34:15 -0400 Message-ID: To: shigio@wafu.netgate.net Cc: hackers@FreeBSD.ORG Subject: RE: Improvement of ln(1). Date: Tue, 14 Jul 1998 16:34:13 -0400 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 > From: shigio@wafu.netgate.net [SMTP:shigio@wafu.netgate.net] > > Do you mean a symbolic link including root directory is useless? > You are right. My example was bad. > > How about this example? > > % ln -sr /usr/src/sys/kern/tty.c /usr/obj/usr/src/sys/kern/tty.c > % ls -l !$ > lrwxrwxrwx 1 shigio bin 33 Jul 14 23:56 > /usr/obj/usr/src/sys/kern/tty.c -> > ../../../../../src/sys/kern/tty.c > > This symbolic link is solved in the '/usr' subdirectory. So, you can > mount > /usr file system at any point. > This example is a lot better. But is it really often needed (I mean, the automatic calculation of ../.. sequence) ? -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 13:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11081 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 13:39:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11076 for ; Tue, 14 Jul 1998 13:39:01 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA06931; Tue, 14 Jul 1998 22:34:38 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA07274; Tue, 14 Jul 1998 11:19:33 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807140919.LAA07274@semyam.dinoco.de> To: "Allen Smith" cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Best means of telling if a proc is still around? In-reply-to: Your message of "Mon, 13 Jul 1998 19:48:44 EDT." <9807131948.ZM9979@beatrice.rutgers.edu> Date: Tue, 14 Jul 1998 11:19:32 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Use at_exit(9) to know when it exits. If it is important to you an > > at_exec(9) might be needed, too. The latter does not exist, yet. > mean doing a full-scale interpretation of what the system call is > doing at the time of the call, which is likely to be a duplication of > the stuff happening later. I suppose I could do an at_exit call at > each such system call, but that's going to result in a definite slowdown. No, you call it the first time you get called. Then you are on the list of things wanting to know about process exits and get a callback every time a process exits. At least that's what the -stable man page says. ;-) If that's too much overhead I think you can introduce a new type of service a la at_exit(9) w/o too much work but this time you don't hang it on a global list but add a local list to the process structure. Then you only get callbacks for the processes where you explicitly requested it and the only overhead for exiting non-affected processes is a test for this list to be empty if done the way I think it should work and a few (four on x86 I suppose) bytes. > Yeah, I know, I'm being a perfectionist - this combination isn't > _that_ likely to happen (indeed, I'm not sure if there are any > circumstances in which it _can_ happen currently) - but I'd prefer to Sure. That's probably the reason why you are willing to implement such a process local at_proc_exit(9). ;-) If you want very low overhead I think that's the only reasonable way to do it. With storing the PID you might get confused with a later existing process with the same PID and searching the process won't make the overhead lower. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 14:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17636 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 14:32:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.alcatel.com.au (gatekeeper.alcatel.com.au [203.17.66.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17630 for ; Tue, 14 Jul 1998 14:32:28 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from mfg1.cim.alcatel.com.au ("port 2087"@[139.188.23.1]) by gatekeeper.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IZF6RCLHS0000JLD@gatekeeper.alcatel.com.au> for hackers@FreeBSD.ORG; Wed, 15 Jul 1998 07:31:45 +1000 Received: from gsms01.alcatel.com.au by cim.alcatel.com.au (PMDF V5.1-10 #23324) with ESMTP id <01IZF6RB7YW0JIYLIV@cim.alcatel.com.au> for hackers@FreeBSD.ORG; Wed, 15 Jul 1998 07:31:43 +1000 Received: (from jeremyp@localhost) by gsms01.alcatel.com.au (8.8.8/8.7.3) id HAA28406 for hackers@FreeBSD.ORG; Wed, 15 Jul 1998 07:31:41 +1000 (EST) Date: Wed, 15 Jul 1998 07:31:41 +1000 (EST) From: Peter Jeremy Subject: Re: Assembly.. To: hackers@FreeBSD.ORG Message-id: <199807142131.HAA28406@gsms01.alcatel.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On: Mon, 13 Jul 1998 17:55:06 -0700 (PDT), Steven Kehlet wrote: > The latest [version of GAS] is 2.8.1. Actually, its 2.9.1 last time I checked. According to the GAS info file (in the section on AT&T Syntax versus Intel Syntax), the correct syntax for lcall is "lcall $SEG,$OFFSET" (ie "lcall $7,$0" for a FreeBSD syscall). This does work in gas 2.9.1, but isn't accepted by the gas 1.92.3 in FreeBSD. The opcode map in gas 1.92.3 suggests "lcall $7,0" might work, but this just generates a core file :-(. >I did however find a way around this... just use .byte and generate >the machine language yourself: > >.byte 0x9a # opcode for lcall >.long 0x0 # this will yield "lcall 0x7,0x0" >.word 0x7 # A check through the system sources will show that this is how it's handled inside the kernel and libraries: #define LCALL(x,y) .byte 0x9a; .long y; .word x #define KERNCALL LCALL(7,0) Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 15:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23344 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 15:15:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23338; Tue, 14 Jul 1998 15:15:19 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA22184; Tue, 14 Jul 1998 17:14:53 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35ABB85B.DFA180D3@uniandes.edu.co> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Jul 1998 17:13:57 -0500 To: Yonny Cardenas Baron From: Richard Wackerbarth Subject: Re: DHCP Server with FreeBSD Cc: jseger@FreeBSD.ORG, hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:58 PM -0500 7/14/98, Yonny Cardenas Baron wrote: >Hi, > >I have a problem with my ISC DHCP server in FreeBSD. > >The request of clients from other subnets not pass for a router Cisco >7500. The "problem" is neither FreeBSD nor DHCP. For a server to service any network to which it is not directly attached, the routers on that network must be set up to relay the dhcp requests. In Cisco terminology, I think that is a "dhcp-helper" that must be configured in the Cisco. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 16:01:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28001 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 16:01:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27995 for ; Tue, 14 Jul 1998 16:01:00 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id SAA28732; Tue, 14 Jul 1998 18:59:52 -0400 (EDT) (envelope-from luoqi) Date: Tue, 14 Jul 1998 18:59:52 -0400 (EDT) From: Luoqi Chen Message-Id: <199807142259.SAA28732@lor.watermarkgroup.com> To: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In file i386/pmap.c, routine pmap_bootstrap(), I find the following > comment: > > "XXX The calculation of virtual_avail is wrong. It's NKPT*PAGE_SIZE too > large. It should be instead be correctly calculated in locore.s and not > based on 'first'(which is a physical address, not a virtual address, for > the start of unused physical memory)..." > > I read this comment a long while ago and still do not understand it. I > believe that the calculation of virutal_avail which immediately follows is > correct and 'firstaddr' has to be a physical address (PA + KERNBASE == > VA). Why it is wrong? How come it is NKPT*PAGE_SIZE large? The kernel physical page table KPTphys is not mapped into the virtual address space. So from physical address 0 to firstaddr, only firstaddr-NKPT*PAGE_SIZE are mapped into the virtual space. The first available virtual address should be KERNBASE+firstaddr-NKPT*PAGE_SIZE. -lq > > Anyway, this piece of code appears in freebsd-stable. If the code IS > wrong, how can this bug not be removed? So maybe the comment is wrong. > > BTW, what does "XXX' mean which appear many times elsewhere? > > Any help is appreciated. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 16:05:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28537 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 16:05:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from holwegner.com (qmailr@holwegner.com [205.158.165.183]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA28532 for ; Tue, 14 Jul 1998 16:05:43 -0700 (PDT) (envelope-from shawn@holwegner.com) Received: (qmail 3416 invoked by uid 500); 13 Jul 1998 23:04:44 -0000 Message-ID: <19980713160444.B3383@holwegner.com> Date: Mon, 13 Jul 1998 16:04:44 -0700 From: Shawn Holwegner To: freebsd-hackers@FreeBSD.ORG Subject: Tyan Tomcat DMA and IRQ woes. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.14i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Seemed that this may be the place for more of a technical discussion, as opposed to many of the other groups where one can expect 'Whats a DMA?'. I have recently aquired a Tyan Tomcat II Dual Pent. MB. Looks nice, wish I could say it works the same: I am having no end to troubles with it in regards to DMA and IRQ timeouts. I have set the Award BIOS to 'manually controlled resources' as opposed to PnP (evil, wish I knew about this before). The odd part is: everyting bloody well works fine until the kernel attempts to probe the IRQs/DMAs. It will read absolutely everything, even report ATAPI status on the CDROM and single IDE drive within (IBM DHEA EIDE), but a simple disklabel has it locking up (an attempt to boot from 3.0-SNAP, May 24, 1998 will cause it to panic, init dies and jordy's graphic laden fiend of an install program resets the box. If any Tomcat users could shed a little light what they had to do to make it work, it'd be greatly apprecated. Right now Im limping by from a small partition on my 2940 emergency backup, which seems to lose devices every reboot with this @_(#$@#$@# board. Shawn (Called Tyan - 'Have you disabled the Video Bios yet?') Holwegner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 16:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29881 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 16:15:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29873; Tue, 14 Jul 1998 16:15:00 -0700 (PDT) (envelope-from jer@jorsm.com) Received: from localhost (jer@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id SAA02653; Tue, 14 Jul 1998 18:14:50 -0500 (CDT) Date: Tue, 14 Jul 1998 18:14:49 -0500 (CDT) From: Jeremy Shaffner To: Giannis Vlachos cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Script for dialup users 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, 13 Jul 1998, Giannis Vlachos wrote: > Hello to anyone on the lists of FreeBSD. > > I have build my dialup server on Freebsd 2.2.2 version. > > The users who they are connected using Win95 need a script > for automatically login (Not the old fashion type with the > black window verifacation login : and Password: ) > > I try one . It takes the login name correctlly but at the password > the script halted and i have to continue manually and to type the password > by hand. > > Does anyone have any solution for this case? > > I want to say thanks in advance. I think everyone thinks you're having problems with a fbsd chat script. Is it the Windows Dial-Up Scripting you're having problems with? If so, this is not the place to get help on it. There are gobs of sites on the web that tell you how to get a DUN Script to work. There are also sample scripts included (ppp.scp and slip.scp). Modify them as necessary. Or, like some people said, use PAP/CHAP on the server. For those who wondered..the "black window" is a post-dial terminal window allowing for UNIX style login after a connection is made. -===================================================================- Jeremy Shaffner JORSM Internet Senior Technical Support Northwest Indiana's Premium jer@jorsm.com Internet Service Provider support@jorsm.com http://www.jorsm.com -===================================================================- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 16:33:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01874 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 16:33:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01862 for ; Tue, 14 Jul 1998 16:33:56 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA04377; Tue, 14 Jul 1998 16:33:19 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004371; Tue Jul 14 16:33:12 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA10092; Tue, 14 Jul 1998 16:33:12 -0700 (PDT) From: Archie Cobbs Message-Id: <199807142333.QAA10092@bubba.whistle.com> Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? In-Reply-To: from zhihuizhang at "Jul 14, 98 04:34:17 pm" To: bf20761@binghamton.edu (zhihuizhang) Date: Tue, 14 Jul 1998 16:33:12 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 zhihuizhang writes: > BTW, what does "XXX' mean which appear many times elsewhere? This just means "here is something that still needs to be looked at"... the dream being that someday a fairy godmother/programmer will do a vi `find /sys -type f -print | xargs grep -l XXX` and resolve all those issues... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 17:08:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07322 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 17:08:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA07316 for ; Tue, 14 Jul 1998 17:08:26 -0700 (PDT) (envelope-from shigio@wafu.netgate.net) Message-Id: <199807150008.RAA07316@hub.freebsd.org> Received: (qmail 12358 invoked from network); 14 Jul 1998 16:08:15 -0000 Received: from ins4.tama-ap3.dti.ne.jp (HELO choota.signet.or.jp) (203.181.67.4) by wafu.netgate.net with SMTP; 14 Jul 1998 16:08:15 -0000 Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.7/) with ESMTP id JAA00397; Wed, 15 Jul 1998 09:09:30 +0900 (JST) To: sbabkin@dcn.att.com cc: shigio@wafu.netgate.net, hackers@FreeBSD.ORG Subject: Re: Improvement of ln(1). In-reply-to: Message from sbabkin@dcn.att.com of "Tue, 14 Jul 1998 16:34:13 -0400." Date: Wed, 15 Jul 1998 09:09:30 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: sbabkin@dcn.att.com > > > % ln -sr /usr/src/sys/kern/tty.c /usr/obj/usr/src/sys/kern/tty.c > > % ls -l !$ > > lrwxrwxrwx 1 shigio bin 33 Jul 14 23:56 > > /usr/obj/usr/src/sys/kern/tty.c -> > > ../../../../../src/sys/kern/tty.c > > > > This symbolic link is solved in the '/usr' subdirectory. So, you can > > mount > > /usr file system at any point. > > > This example is a lot better. But is it really often needed (I mean, the > automatic calculation of ../.. sequence) ? Yes, it is, at least for me. I need it especially to publish WWW site on the Internet and to make developpment environment on the LAN. I think the calculation of conversion between absolute and relative path should be done automatically not manually. -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 17:12:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07923 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 17:12:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07915 for ; Tue, 14 Jul 1998 17:12:00 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA24922; Tue, 14 Jul 1998 17:11:42 -0700 (PDT) Message-Id: <199807150011.RAA24922@implode.root.com> To: Luoqi Chen cc: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? In-reply-to: Your message of "Tue, 14 Jul 1998 18:59:52 EDT." <199807142259.SAA28732@lor.watermarkgroup.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 14 Jul 1998 17:11:42 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In file i386/pmap.c, routine pmap_bootstrap(), I find the following >> comment: >> >> "XXX The calculation of virtual_avail is wrong. It's NKPT*PAGE_SIZE too >> large. It should be instead be correctly calculated in locore.s and not >> based on 'first'(which is a physical address, not a virtual address, for >> the start of unused physical memory)..." I wrote the comment. The word "wrong" above doesn't mean that it is wrong in the sense that there is a bug in the code. It means only that, from an architectural perspective, it should represent the actual start of the kernel VM (after the kernel text/data/bss), and instead means something slightly different. I can't help but wonder why you are looking at this code fragment...it is highly esoteric for most anyone who intends to do development in the FreeBSD kernel. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 17:19:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08658 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 17:19:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08653 for ; Tue, 14 Jul 1998 17:19:30 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id JAA16563; Wed, 15 Jul 1998 09:47:57 +0930 (CST) Message-ID: <19980715094757.P15083@freebie.lemis.com> Date: Wed, 15 Jul 1998 09:47:57 +0930 From: Greg Lehey To: Wilko Bulte Cc: tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG Subject: Re: Software RAID-5 performance References: <19980714122952.L754@freebie.lemis.com> <199807141805.UAA03774@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141805.UAA03774@yedi.iaf.nl>; from Wilko Bulte on Tue, Jul 14, 1998 at 08:05:16PM +0200 WWW-Home-Page: http://www.lemis.com/~grog 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, 14 July 1998 at 20:05:16 +0200, Wilko Bulte wrote: > As Greg Lehey wrote... >> (trimming -fs) > >>> Software RAID is a data integrity issue, not a performance one, >>> and I think making the performance argument for whatever reason >>> (protection domain crossing, interleaved I/O, SMP scalability, >>> etc.) is a strawman at best. >> >> I'm not sure that I understand what you're saying here. Obviously >> offloading the checksum calculation (or anything else, for that >> matter) to an external box will offload the CPU. And I can't see any >> particular difference in data integrity between the two approaches. > > Software raid without stable (battery backed) storage is flawed: > > assume a write that had 2 disks actually write the data onto the platter > and (e.g.) the parity data did not make it out on it's platter because your > system crashed. Or the power went bang. Or... > > You now have an inconsistent raid5 set. Correct. Similar things happen if a disk loses power while writing, but the window is larger for RAID-5, and it's much more difficult to detect. There are a number of "solutions", of course: 1. Intent logging. Save some copy of the data elsewhere first. Slow. 2. Battery backup. Doesn't guard against panics and non-disk hardware failure. 3. As long as the disks didn't physically fail, rebuild the RAID-5 set after rebooting. None of these is nice. Greg -- See complete headers for address 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 Jul 14 17:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10736 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 17:30:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA10722 for ; Tue, 14 Jul 1998 17:30:49 -0700 (PDT) (envelope-from jasone@canonware.com) Received: (qmail 15410 invoked by uid 1001); 15 Jul 1998 00:31:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Jul 1998 00:31:30 -0000 Date: Tue, 14 Jul 1998 17:31:30 -0700 (PDT) From: Jason Evans To: Shawn Holwegner cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Tyan Tomcat DMA and IRQ woes. In-Reply-To: <19980713160444.B3383@holwegner.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, 13 Jul 1998, Shawn Holwegner wrote: > I have recently aquired a Tyan Tomcat II Dual Pent. MB. Looks nice, > wish I could say it works the same: I am having no end to troubles with it > in regards to DMA and IRQ timeouts. I have set the Award BIOS to 'manually > controlled resources' as opposed to PnP (evil, wish I knew about this before). > > The odd part is: everyting bloody well works fine until the kernel > attempts to probe the IRQs/DMAs. It will read absolutely everything, even > report ATAPI status on the CDROM and single IDE drive within (IBM DHEA EIDE), > but a simple disklabel has it locking up (an attempt to boot from 3.0-SNAP, > May 24, 1998 will cause it to panic, init dies and jordy's graphic laden > fiend of an install program resets the box. Well, I've installed the same snapshot on the same board with 2 166MHz CPUs on it, 64 MB RAM, a couple of EIDE drives, and assorted junk parts. It works fine for me. I did nothing special to the BIOS to make it work. Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 17:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10861 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 17:31:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10854 for ; Tue, 14 Jul 1998 17:31:30 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-152.camalott.com [208.229.74.152]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA06090; Tue, 14 Jul 1998 19:32:01 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id TAA04219; Tue, 14 Jul 1998 19:31:13 -0500 (CDT) (envelope-from joelh) Date: Tue, 14 Jul 1998 19:31:13 -0500 (CDT) Message-Id: <199807150031.TAA04219@detlev.UUCP> To: archie@whistle.com CC: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: <199807142333.QAA10092@bubba.whistle.com> (message from Archie Cobbs on Tue, 14 Jul 1998 16:33:12 -0700 (PDT)) Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807142333.QAA10092@bubba.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> BTW, what does "XXX' mean which appear many times elsewhere? > This just means "here is something that still needs to be looked at"... > the dream being that someday a fairy godmother/programmer will do a > vi `find /sys -type f -print | xargs grep -l XXX` > and resolve all those issues... More realistically, you often write this comment in the hopes that when you (or somebody else) is groveling over that bit of code to find why it breaks when used in an odd manner, that comment will stand out and give you a likely candidate. In reality, of course, bugs are not marked, since the use of "XXX" means that the programmer in question was thinking clearly enough to 1. write something that works even though it's not the right thing, and 2. notice it. "... and X never, never marks the spot." -- Indiana Jones, "Indiana Jones and the Last Crusade" See also the Jargon File (http://www.ccil.org/jargon) entries for XXX and FIXME. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 19:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29534 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 19:40:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29510 for ; Tue, 14 Jul 1998 19:40:22 -0700 (PDT) (envelope-from sysadmin@mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id VAA00394 for ; Tue, 14 Jul 1998 21:40:13 -0500 (CDT) (envelope-from sysadmin@mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDAF99.E3BEEEC0@noc.mfn.org>; Wed, 15 Jul 1998 02:40:12 +0100 Message-ID: <01BDAF99.E3BEEEC0@noc.mfn.org> From: "sysadmin@mfn.org" To: "'freebsd-hackers@freebsd.org'" Subject: rwhod problem: more info, bigger problem... Date: Wed, 15 Jul 1998 02:40:10 +0100 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 Greetings, I found out what causes my rwho daemon to die, but I can't figure out how to throw gdb on it: It's the act of logging in which makes it die. How would one gdb a task without logging in? I am assuming that this is a low-ram problem, as the machine in question is dedicated to a specific purpose, and has only 8mb of ram. Since rwho runs until a login takes place, my working theory is it dies when trying to swap: top reports 1.6mb of swap in use after login, which means the machine has almost to the byte what it needs to run moment to moment... Any thoughts on how to attack this cockroach? TIA J.A. Terranson sysadmin@mfn.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 21:27:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12201 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 21:27:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12192 for ; Tue, 14 Jul 1998 21:27:30 -0700 (PDT) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id VAA15987; Tue, 14 Jul 1998 21:21:40 -0700 (PDT) Message-ID: <19980714212139.48766@dog.farm.org> Date: Tue, 14 Jul 1998 21:21:39 -0700 From: Dmitry Kohmanyuk =?KOI8-R?B?5M3J1NLJyiDrz8jNwc7Ayw==?= To: Subject: netscape communicator 4.5 preview 1 is released ~50 minutes ago Reply-To: dk+@ua.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e X-Class: Fast X-OS-Used: FreeBSD 2.2-960501-SNAP X-NIC-Handle: DK379 X-Pager-Email: dk@interpage.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there is no binary for freebsd, but this one works: ftp://ftp.netscape.com/pub/communicator/4.5/4.5_PR1/english/unix/linux20/communicator-v45b1-export.x86-unknown-linux2.0.tar.gz (there are 3 linux packages...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25907 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:15:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25901 for ; Tue, 14 Jul 1998 23:15:35 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA16497; Tue, 14 Jul 1998 23:15:27 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd016476; Tue Jul 14 23:15:24 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA06392; Tue, 14 Jul 1998 23:15:21 -0700 (MST) From: Terry Lambert Message-Id: <199807150615.XAA06392@usr06.primenet.com> Subject: Re: Improvemnet of ln(1). To: shigio@wafu.netgate.net (Shigio Yamaguchi) Date: Wed, 15 Jul 1998 06:15:21 +0000 (GMT) Cc: sbabkin@dcn.att.com, shigio@wafu.netgate.net, hackers@FreeBSD.ORG In-Reply-To: <199807141528.IAA18558@hub.freebsd.org> from "Shigio Yamaguchi" at Jul 15, 98 00:29:33 am X-Mailer: ELM [version 2.4 PL25] 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 > Do you mean a symbolic link including root directory is useless? > You are right. My example was bad. > > How about this example? > > % ln -sr /usr/src/sys/kern/tty.c /usr/obj/usr/src/sys/kern/tty.c > % ls -l !$ > lrwxrwxrwx 1 shigio bin 33 Jul 14 23:56 /usr/obj/usr/src/sys/kern/tty.c -> > ../../../../../src/sys/kern/tty.c > > This symbolic link is solved in the '/usr' subdirectory. So, you can mount > /usr file system at any point. #!/bin/sh # # A script that needs to make non-existant absolute symlinks # TARGET=$1 if test "x$1" = "x" then echo "usage: mkbuild " >&2 exit 1 fi cd / # copy in the kernel so ps will work... cp kernel ${TARGET} # copy in the rest of the stuff to make the environment minimally functional cp -R bin ${TARGET} cp -R dev ${TARGET} cp -R etc ${TARGET} cp -R usr ${TARGET} cd b cp -R newsrc ${TARGET}/usr cd .. ln -s /usr/lib ${TARGET}/lib # make a non-existant link to the newsrc kernel sources.. ln -s /usr/newsrc/sys /sys # now enter into the isolated developement environment... chroot ${TARGET} /bin/sh exit 0 Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27944 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:29:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27937 for ; Tue, 14 Jul 1998 23:29:27 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA07281; Tue, 14 Jul 1998 23:29:20 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd007271; Tue Jul 14 23:29:14 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA06869; Tue, 14 Jul 1998 23:29:07 -0700 (MST) From: Terry Lambert Message-Id: <199807150629.XAA06869@usr06.primenet.com> Subject: Re: Detecting the presence of threads (for a port) To: andre@pipeline.ch (IBS / Andre Oppermann) Date: Wed, 15 Jul 1998 06:29:06 +0000 (GMT) Cc: pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: <35AB8CAB.4FF133B@pipeline.ch> from "IBS / Andre Oppermann" at Jul 14, 98 06:51:55 pm X-Mailer: ELM [version 2.4 PL25] 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 > > P.S. Who else (if anyone) is working on ldap at present? > > We are not working on it, but working with it. Theres one really big > bug in Terry's patches (or in libc_r) that prevents ldif2ldap & co. > from working (you'll get empty ddb files). I reported that to Terry > but I don't know if he has fixed it yet. For what it's worth, the code with all the agregate patches I did, plus all of my own patches I did on top of that, appears to run fine on RedHat Linux. The bug is a result of linking the dbm stuff against libc_r, and is a libc_r bug, not a bug in the patches. You can work around it by building the thing once without patches, which is enough to get the ldif tools working, and then once with the patches to get all of the servers working. I haven't had much time outside of work to hack on the code; when I get the chance, I'll probably buckle down and bring the code up to the LDAP 3 standard, with the Netscape draft extensions for transaction tracking. It will be a while before I can do this, but I'm very interested in getting the code to work. > Lemme suggest another small thing: Please inlcude the Berkeley DB 2.x > stuff into the LDAP-3.3 port (LDAP isn't really useful without it). Hmm. I am very distressed at the sleepycat license. It is GPL without the poison pill, and so it is very dangerous to BSD style free software (as far as GPL is concerned, software that wants to be commrecialy utilizable really should view it as yet another proprietary effort, just like Microsoft or Sun). I have considering poisinging my code with an additional clause that states derivative works can ask but not require that source be made available, with the intent that the code remain capable of being incorporated into a commercial product without additional license. I think the code is really very useful, so long as you do not rely on the ndbm features, which BSD's dbm pretends to implement by making stub functions so it will link, but not run. 8-(. > And yet another thing: Netscape released their LDAP client lib stuff > to the public on www.mozilla.org, it needs also an port but I'm far > too busy at the moment to do it. Not to mention the LDAP client code from the JAVASoft site; LDAP is a flly funtional JNDI citizen. There is also a Perl mod for talking to LDAP servers, and there is a draft standard for serializing JAVA objects into an LDAP database. If one of your record attributes was "validate" and it contained a serialized JAVA object, it's not that big a step to consider using HTML templates that assemble validation functions dynamically, and run the same validation in the browser as on the server the browser is POSTing to... finally realizing the ability to allow UI programmers to export arbitrary views on the database, which may have absolutely nothing to do with "third normal form" or engineering requirements vs. cognitive psychology requirements for making humans comfortable with the interfaces. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00280 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:40:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00273 for ; Tue, 14 Jul 1998 23:40:27 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA09922; Tue, 14 Jul 1998 23:40:20 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd009863; Tue Jul 14 23:40:13 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA07367; Tue, 14 Jul 1998 23:40:09 -0700 (MST) From: Terry Lambert Message-Id: <199807150640.XAA07367@usr06.primenet.com> Subject: Re: Detecting the presence of threads (for a port) To: patl@phoenix.volant.org Date: Wed, 15 Jul 1998 06:40:09 +0000 (GMT) Cc: andre@pipeline.ch, pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "patl@phoenix.volant.org" at Jul 14, 98 11:43:20 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We are not working on it, but working with it. Theres one really big > > bug in Terry's patches (or in libc_r) that prevents ldif2ldap & co. > > from working (you'll get empty ddb files). I reported that to Terry > > but I don't know if he has fixed it yet. > > It looks like the original code makes some silly assumptions about > uninitialized variables being set to zero. The following patches > seemed to make it work for me. But I wouldn't be surprised if there > are more uninitialized variable bugs... Whoah. I will give this a try; if it works, can I post this to the LDAP list? I'll also be happy to re-roll the patches to include this. I happen to know at least one currently shipping commercial platform that needs my Draft 4 pthreads patches, and SGI apparently need my FD_SETSIZE patches, or it eats CPU like the previous FreeBSD port. I have some code that replaces getpwent and family (basically, the draft "Uning LDAP for NIS data" standard) to let you use LDAP to validate users. It's rather nifty to be able to point your Netscape communicator at your FreeBSD box, and see your companies account database show up in the "address book" as addresses you can automatically mail to. 8-). I also have some code that can identify v2 vs. v3, and knows the root of the server. This means you can write a client that can talk to an LDAP server it didn't previously know about, and not trigger referrals. This is a must for using the code as a parameter store (for FreeBSD configuration data, for example). Critical-Angle sells an LDAP server, so they apparently aren't too interested in maintaining the code in, for example, a publically available CVS tree. Maybe it's time to start a public LDAP project, with the aim of supporting version 3, and the ability to run Netscape's calendaring software? I have full netscape.oc.conf/netscape.at.conf files, but I think without v3 subschema entry support, it can't be used for calendaring. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01245 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:46:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01238 for ; Tue, 14 Jul 1998 23:46:56 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA23200; Tue, 14 Jul 1998 23:46:48 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd023180; Tue Jul 14 23:46:44 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA07711; Tue, 14 Jul 1998 23:46:37 -0700 (MST) From: Terry Lambert Message-Id: <199807150646.XAA07711@usr06.primenet.com> Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? To: dg@root.com Date: Wed, 15 Jul 1998 06:46:36 +0000 (GMT) Cc: luoqi@watermarkgroup.com, bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199807150011.RAA24922@implode.root.com> from "David Greenman" at Jul 14, 98 05:11:42 pm X-Mailer: ELM [version 2.4 PL25] 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 can't help but wonder why you are looking at this code fragment...it > is highly esoteric for most anyone who intends to do development in the > FreeBSD kernel. Maybe he's proting FreeBSD to the relatively high powered, yet very inexpensive MIPS chip based systems that are out there. 8-) 8-). Wishful thinking, I know... Still, are you aware that the "Cobalt" thin server platform, running MIPS Linux, has hardware about 1/3 as expensive as comparable Intel hardware? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01431 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:48:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01426 for ; Tue, 14 Jul 1998 23:48:05 -0700 (PDT) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id PAA19672; Wed, 15 Jul 1998 15:47:34 +0900 (JST) Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.26.2]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id PAA03621; Wed, 15 Jul 1998 15:47:33 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id PAA25283; Wed, 15 Jul 1998 15:47:29 +0900 (JST) Date: Wed, 15 Jul 1998 15:47:29 +0900 (JST) Message-Id: <199807150647.PAA25283@stone.astec.co.jp> From: HAMADA Naoki References: To: smoergrd@oslo.geco-prakla.slb.com CC: sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: Dag-Erling Coidan Sm,Ax(Brgrav's message of "09 Jul 1998 16:31:39 +0200" Subject: Re: NIC drivers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG smoergrd@oslo.geco-prakla.slb.com writes: >Believe me, it still sucks. Search the archives (both the mailing list >archives and the PR database) for "no buffer space", and/or "ep0". >Basically, the driver is fine for telnet and mail, but wedges under >sustained load. I can get it to hang without ever going above 20 kBps >(160 kbps). Gimme an Intel EtherExpress. I carefully looked through the source code to find a bug which results mbuf leaks. Could you try this patch? -nao --- sys/i386/isa/if_ep.c- Wed Jul 15 15:40:09 1998 +++ sys/i386/isa/if_ep.c Wed Jul 15 15:41:04 1998 @@ -1128,8 +1128,7 @@ /* we see if by now, the packet has completly arrived */ goto read_again; } - outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | RX_NEXT_EARLY_THRESH); - return; + goto out; } outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); ++ifp->if_ipackets; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 14 23:56:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03260 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 23:56:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03255 for ; Tue, 14 Jul 1998 23:56:41 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA12818; Tue, 14 Jul 1998 23:56:27 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd012794; Tue Jul 14 23:56:22 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA08080; Tue, 14 Jul 1998 23:56:10 -0700 (MST) From: Terry Lambert Message-Id: <199807150656.XAA08080@usr06.primenet.com> Subject: Re: Software RAID-5 performance To: grog@lemis.com (Greg Lehey) Date: Wed, 15 Jul 1998 06:56:10 +0000 (GMT) Cc: wilko@yedi.iaf.nl, tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG In-Reply-To: <19980715094757.P15083@freebie.lemis.com> from "Greg Lehey" at Jul 15, 98 09:47:57 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You now have an inconsistent raid5 set. > > Correct. Similar things happen if a disk loses power while writing, > but the window is larger for RAID-5, and it's much more difficult to > detect. There are a number of "solutions", of course: > > 1. Intent logging. Save some copy of the data elsewhere first. > Slow. You can actually "containerize" this. You end up with something that looks a lot like IBM's JFS. The basic idea is that you create a "container" that points to the old object; then you update the new object to a new location, rewrite the container, and free up the old object. This is currently how you can implement multi-record transactions in databases that don't support exporting a transaction mechanis,. This approach is useful, for example, if you want to have implied state between a data file and an index file, but your system does not guarantee metadata updates to be ordered (either soft updates, delayed ordered writes, or synchronus writes). For example, on EXT2FS. The recent Informix port to Linux had me seriously wondering how they would address this issue. I suspect that they do a system-wide "sync(2)" when they do directory entry manipulation, and fsync(2) before committing the container data. A little slower than it has to be, if run under FreeBSD under Linux emulation, but computationally sound. > 2. Battery backup. Doesn't guard against panics and non-disk > hardware failure. No, but it's a hell of a lot faster as an intention log, and it resolves most of your issues. If written correctly, it supports transaction rolll-forward (ie: you do the RAM update, mark it valid, and commit it in the background, removing it only after the commit is verified -- exactly how PrestoServe(tm) does it...). > 3. As long as the disks didn't physically fail, rebuild the RAID-5 > set after rebooting. > > None of these is nice. Unfortuantely, if you relied on this last approach, you wouldn't be able to tell a soft failutre from a hard failure. VXFS (Veritas) on UnixWare used to have this problem; it assumed that all soft failures would be resolved transparently (an incorrect assumption). On slow IDE disks, the orginal 1.0 release had a habit of eating "/usr" and marking it bad. Unfortunately, you could undo this without a low level format. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 00:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04010 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 00:02:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04005 for ; Wed, 15 Jul 1998 00:02:18 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA12911; Wed, 15 Jul 1998 00:02:11 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd012890; Wed Jul 15 00:02:05 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA08476; Wed, 15 Jul 1998 00:02:01 -0700 (MST) From: Terry Lambert Message-Id: <199807150702.AAA08476@usr06.primenet.com> Subject: Re: Detecting the presence of threads (for a port) To: tlambert@primenet.com (Terry Lambert) Date: Wed, 15 Jul 1998 07:02:00 +0000 (GMT) Cc: andre@pipeline.ch, pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199807150629.XAA06869@usr06.primenet.com> from "Terry Lambert" at Jul 15, 98 06:29:06 am X-Mailer: ELM [version 2.4 PL25] 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 > For what it's worth, the code with all the agregate patches I did, > plus all of my own patches I did on top of that, appears to run fine > on RedHat Linux. > > The bug is a result of linking the dbm stuff against libc_r, and is > a libc_r bug, not a bug in the patches. Oops. I may have spoke too soon. If the patches posted here by another able engineer actually work, this is tantamount to the common Linux assumption of bzero'ed stack pages for sockaddr_in structs... in other words, a real coding error, not a threads bug on BSD. If this holds true, my theory is that the user space nature of the threads triggered the bug by scribbling on the stack before it was used (something that should not have caused a problem, but did because of the coding error). This is totally cool. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 00:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06427 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 00:28:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06368 for ; Wed, 15 Jul 1998 00:27:59 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0ywLyj-0004Yf-00; Wed, 15 Jul 1998 00:27:53 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id AAA04711; Wed, 15 Jul 1998 00:27:49 -0700 Date: Wed, 15 Jul 1998 00:27:49 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Detecting the presence of threads (for a port) To: Terry Lambert cc: andre@pipeline.ch, pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199807150640.XAA07367@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > We are not working on it, but working with it. Theres one really big > > > bug in Terry's patches (or in libc_r) that prevents ldif2ldap & co. > > > from working (you'll get empty ddb files). I reported that to Terry > > > but I don't know if he has fixed it yet. > > > > It looks like the original code makes some silly assumptions about > > uninitialized variables being set to zero. The following patches > > seemed to make it work for me. But I wouldn't be surprised if there > > are more uninitialized variable bugs... > > Whoah. > > I will give this a try; if it works, can I post this to the LDAP > list? I'll also be happy to re-roll the patches to include this. Be my guest. I should probably also try to break out my patch to make slapd give up root permission once it has the privileged port bound. I haven't done it before because it really needs a bit more work to be a good general solution - I just hacked out something with a hard-coded check for a user named 'ldap'. It really should be both compile-time and config-file configurable. > ...... > > I have some code that replaces getpwent and family (basically, > the draft "Uning LDAP for NIS data" standard) to let you use > LDAP to validate users. It's rather nifty to be able to point > your Netscape communicator at your FreeBSD box, and see your > companies account database show up in the "address book" as > addresses you can automatically mail to. 8-). Hmm. I've had to put my LDAP work on the back burner for a couple of months; but this looks like something I'd find helpful when I get back to it. I seem to have missed that draft, could you send me an URL and/or RFC number? > I also have some code that can identify v2 vs. v3, and knows the > root of the server. This means you can write a client that can > talk to an LDAP server it didn't previously know about, and not > trigger referrals. This is a must for using the code as a parameter > store (for FreeBSD configuration data, for example). This sounds interesting as well. > Critical-Angle sells an LDAP server, so they apparently aren't too > interested in maintaining the code in, for example, a publically > available CVS tree. > > Maybe it's time to start a public LDAP project, with the aim of > supporting version 3, and the ability to run Netscape's calendaring > software? I have full netscape.oc.conf/netscape.at.conf files, but > I think without v3 subschema entry support, it can't be used for > calendaring. 8-(. I'd love to see a freely available v3 LDAP server. The schema retrieval and subschema support would be particularly nice for a couple of clients I have on my to-do list. (I occasionally have this fantasy about a completely generic client that queries the server for all the schema info then dynamically builds the schema-specific GUI elements to edit the database. Then I wake up back here in the real world.) I'd also like to be able to say "Count me in, I'll help build it." But in all honesty, I have no idea whether I'd be able to free up the cycles to do anything useful; unless I could find someone who would be willing to pay me to do it. (I already have way too many non-billable projects fighting for my time.) -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 01:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11277 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 01:05:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11254 for ; Wed, 15 Jul 1998 01:05:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 3974 invoked by uid 1001); 15 Jul 1998 08:05:31 +0000 (GMT) To: tlambert@primenet.com Cc: Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? In-Reply-To: Your message of "Wed, 15 Jul 1998 06:46:36 +0000 (GMT)" References: <199807150646.XAA07711@usr06.primenet.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, 15 Jul 1998 10:05:31 +0200 Message-ID: <3972.900489931@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe he's proting FreeBSD to the relatively high powered, yet > very inexpensive MIPS chip based systems that are out there. ... > Still, are you aware that the "Cobalt" thin server platform, running > MIPS Linux, has hardware about 1/3 as expensive as comparable Intel > hardware? Just how inexpensive are we talking here? Where can we buy the stuff? 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 Jul 15 02:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20285 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 02:32:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gateway.blueberry.co.uk (gateway.blueberry.co.uk [195.153.48.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20268; Wed, 15 Jul 1998 02:32:27 -0700 (PDT) (envelope-from keith@blueberry.co.uk) Received: from intranet.blueberry.co.uk (intranet.internal.blueberry.co.uk [10.0.0.2]) by gateway.blueberry.co.uk (8.8.8/8.8.8) with ESMTP id KAA28043; Wed, 15 Jul 1998 10:32:17 +0100 (BST) (envelope-from keith@blueberry.co.uk) Received: (from keith@localhost) by intranet.blueberry.co.uk (8.8.8/8.8.8) id KAA03356; Wed, 15 Jul 1998 10:35:38 +0100 (BST) (envelope-from keith) Message-ID: <19980715103538.41845@blueberry.co.uk> Date: Wed, 15 Jul 1998 10:35:38 +0100 From: Keith Jones To: Subject: kernel panic performing large number of writes to vnode FS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Organization: Blueberry New Media Ltd. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this message to -questions a short while ago, with no joy:- I've recently begun experimenting with using a vnode as a filesystem, and have discovered what appears to be a bug: when copying large numbers of files to a mounted 'vnode filesystem' the kernel panics and the system hangs. This problem appears to be similar to that reported by Mark Taylor on 13 April, 1997 (posted to -bugs and -hackers) though I may be mistaken. This is what I did: # dd if=/dev/zero of=/usr/diskimage bs=1024 count=409600 # vnconfig -c -s labels /dev/vn0 /usr/diskimage # disklabel -w /dev/vn0 400M # newfs /dev/vn0a # newfs /dev/vn0e # newfs /dev/vn0f # mount /dev/vn0a /mnt # cd /mnt # mkdir usr # mkdir var # mount /dev/vn0e /mnt/var # mount /dev/vn0f /mnt/usr The /etc/disktab entry for 400M is as follows: 400M|400M Disk:\ :ty=mfs:se#512:nt#16:ns#32:nc#1600: \ :pa#65536:oa#0:ta=4.2BSD:ba#4096:fa#512:\ :pb#65536:ob#65536:tb=swap: \ :pc#819200:oc#0: \ :pe#61440:oe#131072:te=4.2BSD:be#4096:fe#512: \ :pf#626688:of#192512:tf=4.2BSD:bf#4096:ff#512: Everything works fine up to here, but if I then type (for instance): # cat /usr/local/ftp/pub/FreeBSD/2.2.6-RELEASE/bin/bin.?? | tar --unlink -xpzf - -C /mnt around 150 files or so are extracted, then the following kernel messages appear: Fatal double fault: eip=0xf01a0aba esp=0xefbfcfe0 ebp=0xefbfd058 panic: double fault Syncing disks... at which point the system hangs entirely, unable to sync its disks and thus unable to reboot. The only way out appears to be by resetting the machine. This problem is mitigated somewhat by sync'ing repeatedly while writing to /dev/vn0 - though sometimes the system will crash even in this scenario. intranet# while 1 while? sync while? end dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Tue Jun 30 13:08:32 BST 1998 root@dummy.blueberry.co.uk:/usr/src/sys/compile/DUMMY CPU: Pentium II (233.86-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff real memory = 67108864 (65536K bytes) avail memory = 63537152 (62048K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 3 on pci0:1:0 chip2 rev 1 on pci0:4:0 chip3 rev 1 on pci0:4:1 chip4 rev 1 int d irq 15 on pci0:4:2 chip5 rev 1 on pci0:4:3 de0 rev 33 int a irq 9 on pci0:10:0 de0: SMC 21041 [10Mb/s] pass 2.1 de0: address 00:e0:29:0c:9e:7e vga0 rev 20 int a irq 10 on pci0:11:0 ncr0 rev 3 int a irq 11 on pci0:12:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): "FUJITSU M2952Q-512 0155" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) 2291MB (4693462 512 byte sectors) (ncr0:1:0): "FUJITSU M2954Q-512 0153" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) 4149MB (8498506 512 byte sectors) (ncr0:4:0): "HP HP35480A T503" type 1 removable SCSI 2 st0(ncr0:4:0): Sequential-Access st0(ncr0:4:0): 5.0 MB/s (200 ns, offset 8) density code 0x13, variable blocks, write-enabled Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3: configured irq 12 not in bitmap of probed irqs 0 sio3 at 0x2e8-0x2ef irq 12 on isa sio3: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface de0: enabling 10baseT port WARNING: / was not properly dismounted. de0: abnormal interrupt: receive process stopped Can anyone shed any light on this? Kind regards Keith -- v Keith Jones Systems Manager, Blueberry New Media Ltd. v | Postal Mail: 2/10 Harbour Yard, Chelsea Harbour, LONDON, UK. SW10 0XD | | Telephone: +44 (0)171 351 3313 Fax: +44 (0)171 351 2476 | ^ Email: Keith.Jones@blueberry.co.uk WWW: http://www.blueberry.co.uk/ ^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 04:37:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05693 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 04:37:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05688 for ; Wed, 15 Jul 1998 04:37:24 -0700 (PDT) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id GAA14753; Wed, 15 Jul 1998 06:37:04 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma014742; Wed, 15 Jul 98 06:36:51 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id GAA25464; Wed, 15 Jul 1998 06:36:47 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Wed, 15 Jul 1998 06:36:47 -0500 (CDT) From: Kyle Mestery To: Jason Evans cc: Shawn Holwegner , freebsd-hackers@FreeBSD.ORG Subject: Re: Tyan Tomcat DMA and IRQ woes. 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, 14 Jul 1998, Jason Evans wrote: > Well, I've installed the same snapshot on the same board with 2 166MHz > CPUs on it, 64 MB RAM, a couple of EIDE drives, and assorted junk parts. > It works fine for me. I did nothing special to the BIOS to make it work. > > Jason > I also have this board installed with EIDE drives and SCSI drives, and various other parts. It has been running solidly for over a year. It is currently running current from mid-May I believe, and might be time to update it.:) -- Kyle Mestery StorageTek's Network Systems Group "I'll take what you're willing to give, and I'll teach myself to live, with a walk-on part of a background shot from a movie I'm not in." - Blink 182, "Apple Shampoo" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 05:13:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09289 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 05:13:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.alcatel.com.au (gatekeeper.alcatel.com.au [203.17.66.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09281 for ; Wed, 15 Jul 1998 05:13:12 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from mfg1.cim.alcatel.com.au ("port 4593"@[139.188.23.1]) by gatekeeper.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IZG1I9CL6O000MUU@gatekeeper.alcatel.com.au> for hackers@freebsd.org; Wed, 15 Jul 1998 22:12:26 +1000 Received: from gsms01.alcatel.com.au by cim.alcatel.com.au (PMDF V5.1-10 #23324) with ESMTP id <01IZG1I5NNBKJIYPVP@cim.alcatel.com.au> for hackers@freebsd.org; Wed, 15 Jul 1998 22:12:21 +1000 Received: (from jeremyp@localhost) by gsms01.alcatel.com.au (8.8.8/8.7.3) id WAA23486 for hackers@freebsd.org; Wed, 15 Jul 1998 22:12:20 +1000 (EST) Date: Wed, 15 Jul 1998 22:12:20 +1000 (EST) From: Peter Jeremy Subject: Losing clock interrupts To: hackers@FreeBSD.ORG Message-id: <199807151212.WAA23486@gsms01.alcatel.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running parallel IP between a 486 DX2-50 and a 386SX-25. Both systems have IDE disks. I find that network-intensive activities are causing clock interrupts to be lost. Dropping the MTU helps, but has adverse effects on the throughput (admittedly the system's own calculated throughput looks very good when the clock is basically stopped). I've added some code to the IRQ0 handler to capture timestamps on the 486 system and have come up with the following: - With no system load, the latency (to the beginning of hardclock()) averages ~12usec (~50usec worst case). - The IDE disk handler has minimal impact (the worst case went up to ~75usec latency with ~2.5MB/sec disk I/O and multi-block-16) - LPIP is a real killer. With an MTU of 512, I'm getting latencies >8.5msec sending data and >9.8 msec receiving data. In all cases, the hardware interrupt is received quite quickly - the latencies seem to be ~6usec up to the point where DS is reloaded. The delay is caused by SPL inhibition (most of the LPIP code runs above splclock()). My initial understanding was that when an interrupt was masked, it re-entered at Xresume{n} when it was unmasked. This would mean that I could add some code between Xintr0 and Xresume0 that would count the number of hardware interrupts and modify hardclock() to handle being called less than once per tick. Unfortunately, my timing results show that the soft interrupt entry is also via Xintr{n} which renders this approach useless. (It also explains the vec0 code in i386/isa/icu.s). I accept that a slow 386 on the other end of the link doesn't help, but I can't readily replace that machine. (And it's an ancient laptop with no other `fast' IP-capable interfaces - I don't count 16450 UARTs as fast). Can anyone offer any suggestions on how to either: 1) allow clock interrupts to be handled (and hardclock() run) whilst sending/receiving an LPIP packet. 2) Count real clock interrupts (so hardclock() could compensate when it finally gets a look in) 3) Soup up LPIP so it doesn't hog as much CPU. On the latter point, has anyone looked at making LPIP transmit bytes instead of nybbles? This should roughly halve the time to send/receive a packet. The biggest problem would seem to be negotiating who would transmit at any point in time. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 06:06:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15126 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 06:06:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tc.nsc.ru (ns.tc.nsc.ru [194.226.168.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14945 for ; Wed, 15 Jul 1998 06:05:09 -0700 (PDT) (envelope-from vitaly@tc.nsc.ru) Received: from localhost (vitaly@localhost) by tc.nsc.ru (8.8.8/8.8.8) with SMTP id UAA10885 for ; Wed, 15 Jul 1998 20:04:12 +0700 (NSS) (envelope-from vitaly@tc.nsc.ru) Date: Wed, 15 Jul 1998 20:04:12 +0700 (NSS) From: "Vitaly V. Belekhov" To: freebsd-hackers@FreeBSD.ORG Subject: IPX over IP tunneling. 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! Can anyone say me how IPX over IP tunneling can be implementing? I need connect two IPX networks over IP network. Still find nothing about it... I have FreeBSD-STABLE on my routers. Btw, I now working on right (tm) version of drivers for AirLAN radioethernet cards. I have 4 airlan in my routers, now I test it. ------------------------------------------------------------- Best wishes, Vitaly Belekhov PGP public key - finger://vitaly@tc.nsc.ru http://www.tc.nsc.ru/~vitaly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 07:02:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21089 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 07:02:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20954 for ; Wed, 15 Jul 1998 07:01:49 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id QAA16549 for ; Wed, 15 Jul 1998 16:07:56 +0200 (SAT) Received: by citadel via recvmail id 16547; Wed Jul 15 16:07:50 1998 From: Graham Wheeler Message-Id: <199807151406.QAA04416@cdsec.com> Subject: isnetworktty is really isnettty To: hackers@FreeBSD.ORG Date: Wed, 15 Jul 1998 16:06:52 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] 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 all I don't know who would be responsible for repairing this but anyway... I notice that the /usr/include/ttyent.h file and the manual pages refer to isnetworktty(char *name). However, in the libc/gen/getttyent.c file, the routine is actually called getnettty. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 07:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26032 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 07:44:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26026 for ; Wed, 15 Jul 1998 07:44:05 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA00917; Wed, 15 Jul 1998 00:56:18 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807150756.AAA00917@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci brooktree848.c In-reply-to: Your message of "Wed, 15 Jul 1998 08:36:43 +0200." <8279.900484603@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 00:56:18 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In response to: sos@FreeBSD.ORG said: > sos 1998/07/14 14:20:00 PDT > Modified files: > sys/pci brooktree848.c > Log: > Add support for the AVer Media range of cards. > Revision Changes Path > 1.45 +13 -9 src/sys/pci/brooktree848.c > In message <199807150359.UAA02946@rah.star-gate.com>, Amancio Hasty writes: > >Cute, I will review the patch later on the week after my work crunch. > > > >If the patch is not good it will be wipe out on my next rev level. > > WARNING: > > Do not wipe out other peoples patches, unless you provide > the same level of functionality in "your next rev level". Background, we in the multimedia list are in the process of improving the tuner detection code due mostly to the ever increasing proliferation of bt848/tuners . So far we have identified a popular bt848 vendor Hauppauge who stores its configuration information in an eeprom over the couple of weeks we engaged in decoding the eeprom and so far we have been successful. This was an important step for detecting the known good configurations helps reduce the search space for bt848/tuners. Prior to that I send out a general query to attempt to identify the basic characteristics of the cards and I am compiling a small database of bt848 / tuner cards -- in the mean time any code dealing with tuner detection addition/deletion has been frozen by me till I get a better handle on the proper identification of the bt848/tuner cards. I have a basic question, can any committer or so called "core" tramp over any code in the tree specially if they are not the author/mantainer of the code? PHK's e-mail seems to imply that is the case. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 07:52:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26874 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 07:52:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26861; Wed, 15 Jul 1998 07:52:41 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id HAA01599; Wed, 15 Jul 1998 07:52:33 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807151452.HAA01599@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci brooktree848.c In-reply-to: Your message of "Wed, 15 Jul 1998 10:11:15 +0200." <199807150811.KAA04070@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 15 Jul 1998 07:52:33 -0700 From: Amancio Hasty Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA26867 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I have thought about it and yes I do know how to handle the situation. Amancio > In reply to Amancio Hasty who wrote: > > Cute, I will review the patch later on the week after my work crunch. > > Do that, you have had month to do it now :) > > > If the patch is not good it will be wipe out on my next rev level. > > Think more than once about that ;) > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 08:32:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03585 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 08:32:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03483 for ; Wed, 15 Jul 1998 08:31:56 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id RAA27803 ; Wed, 15 Jul 1998 17:31:13 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id RAA02478; Wed, 15 Jul 1998 17:31:12 +0200 To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: Losing clock interrupts References: <199807151212.WAA23486@gsms01.alcatel.com.au> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 15 Jul 1998 17:31:11 +0200 In-Reply-To: Peter Jeremy's message of Wed, 15 Jul 1998 22:12:20 +1000 (EST) Message-ID: Lines: 39 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > I'm running parallel IP between a 486 DX2-50 and a 386SX-25. Both > systems have IDE disks. I find that network-intensive activities are > causing clock interrupts to be lost. Dropping the MTU helps, but has > adverse effects on the throughput (admittedly the system's own > calculated throughput looks very good when the clock is basically > stopped). We know. You will find links to previous PRs about this problem, as well as patches which almost (but not quite, according to Bruce Evans) fix the bug at The audit trail for one of the PRs listed there includes an article by Bruce explaining what's wrong with the current patches. If you think you can fix them, go ahead; I'm not familiar enough with the kernel's interrupt handling mechanisms to do it myself. BTW, Dropping the MTU doesn't really help, because although you get inter-packet breaks more often, which allows you to catch up on interrupts a little, you're transmitting more data, which leads to higher CPU usage. > 3) Soup up LPIP so it doesn't hog as much CPU. Unfortunately, that's not possible unless you can live with having the parallell port issuing two interrupts for every byte transferred over the link. As I understand it, the current implementation generates one interrupt per packet, then polls the parallell port to actually read the data. The busy-looping in the polling code is what hogs the CPU. > On the latter point, has anyone looked at making LPIP transmit bytes > instead of nybbles? This would require a collision detection mechanism, or a slave/master scheme in which one of the hosts never talks unless asked by the other. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 11:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27197 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 11:21:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [209.137.74.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27188 for ; Wed, 15 Jul 1998 11:21:54 -0700 (PDT) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id OAA10952 for ; Wed, 15 Jul 1998 14:26:30 -0400 Date: Wed, 15 Jul 1998 14:26:30 -0400 (EDT) From: Scott Smyth To: freebsd-hackers Subject: RAID support in freebsd kernel 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 anyone trying to put RAID support into the freebsd kernel (similar or not to the Linux RAID support)? Thanks -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 11:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28918 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 11:37:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28913 for ; Wed, 15 Jul 1998 11:37:11 -0700 (PDT) (envelope-from vanmaren@fast.cs.utah.edu) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by wrath.cs.utah.edu (8.8.8/8.8.8) with SMTP id MAA16891 for ; Wed, 15 Jul 1998 12:37:03 -0600 (MDT) Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id MAA09249; Wed, 15 Jul 1998 12:37:02 -0600 Date: Wed, 15 Jul 1998 12:37:02 -0600 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199807151837.MAA09249@fast.cs.utah.edu> To: hackers@FreeBSD.ORG Subject: ibcs2 emulation problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not currently on this list, but I'm hoping someone has an answer for me: I tried to run the Seagate BackupExec client for SCO on FreeBSD 2.2.6-Release. It seems to get stuck in an infinite loop when it tries to determine the disk usage: in this case I had the server try to backup the /mis directory, and it is looping on /mis/. Does anyone know if maybe the lstat call (#91) is not entirly compatable? Any other ideas? There are no symbols in the COFF file, which makes debugging more challenging. Here is an excerpt from ktrace: 6292 agent.be CALL close(0x9) 6292 agent.be RET close 0 6292 agent.be CALL #91(0xefbfd7bc,0xefbfda18) 6292 agent.be NAMI "/compat/ibcs2/mis/." 6292 agent.be NAMI "/mis/." 6292 agent.be RET #91 0 6292 agent.be CALL open(0x40a910,0,0x40a900) 6292 agent.be NAMI "/compat/ibcs2/mis" 6292 agent.be NAMI "/mis" 6292 agent.be RET open 9 6292 agent.be CALL sendmsg(0x9,0xefbfd9c8) 6292 agent.be RET sendmsg 0 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 0 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 0 6292 agent.be CALL getpgrp(0x9,0x4212e4,0x418) 6292 agent.be RET getpgrp 518/0x206 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 512/0x200 6292 agent.be CALL close(0x9) 6292 agent.be RET close 0 6292 agent.be CALL #91(0xefbfd7bc,0xefbfda18) 6292 agent.be NAMI "/compat/ibcs2/mis/." 6292 agent.be NAMI "/mis/." 6292 agent.be RET #91 0 6292 agent.be CALL open(0x40a910,0,0x40a900) 6292 agent.be NAMI "/compat/ibcs2/mis" 6292 agent.be NAMI "/mis" 6292 agent.be RET open 9 6292 agent.be CALL sendmsg(0x9,0xefbfd9c8) 6292 agent.be RET sendmsg 0 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 0 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 0 6292 agent.be CALL getpgrp(0x9,0x4212e4,0x418) 6292 agent.be RET getpgrp 518/0x206 6292 agent.be CALL old.lseek(0x9,0,0x1) 6292 agent.be RET old.lseek 512/0x200 6292 agent.be CALL close(0x9) 6292 agent.be RET close 0 6292 agent.be CALL #91(0xefbfd7bc,0xefbfda18) 6292 agent.be NAMI "/compat/ibcs2/mis/." 6292 agent.be NAMI "/mis/." 6292 agent.be RET #91 0 6292 agent.be CALL open(0x40a910,0,0x40a900) 6292 agent.be NAMI "/compat/ibcs2/mis" 6292 agent.be NAMI "/mis" 6292 agent.be RET open 9 The other agents I can choose from (x86) are the Solaris/x86 and Unixware(1,2), and another SCO (isc) binary, that dies on /dev/tcp. Thanks, Kevin Van Maren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 12:27:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06213 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 12:27:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from firebat.wolfepub.com (firebat.wolfepub.com [206.250.193.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06205 for ; Wed, 15 Jul 1998 12:27:14 -0700 (PDT) (envelope-from matthew@wolfepub.com) Received: from ricecake.fastnet0.net (niu-ppp134.triton.net [209.172.4.134]) by firebat.wolfepub.com (8.9.0/8.9.0) with SMTP id PAA15043 for ; Wed, 15 Jul 1998 15:25:08 -0400 (EDT) Message-Id: <3.0.3.32.19980715153323.00733ab8@wolfepub.com> X-Sender: matthew@wolfepub.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 15 Jul 1998 15:33:23 -0400 To: hackers@FreeBSD.ORG From: Matthew Hagerty Subject: Protecting data in memory Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Is there any way to protect a programs memory space from all users, even root? I am developing an encryption program that has to run as a daemon. Upon start-up the program would prompt for the key, then slip into daemon land. If the server is compromised (root access is gained) can I prevent the cracker from reading the program's memory and gaining access to the key data? As long as I can keep the key secure, the data should be safe (I'm using IDEA in chain-block mode). I'm currently writing the program in C. If this is not possible (protecting the key), then can someone shed some light on how I can protect sensitive data on an on-line machine? I know, I know, but this data "has" to be on-line for processing that happens all day long. Thanks, Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 13:32:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12282 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 13:32:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA12275 for ; Wed, 15 Jul 1998 13:32:49 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ywYDk-0000j7-01; Wed, 15 Jul 1998 14:32:12 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA00173; Wed, 15 Jul 1998 10:40:23 -0600 (MDT) Message-Id: <199807151640.KAA00173@harmony.village.org> To: sthaug@nethelp.no Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Jul 1998 10:05:31 +0200." <3972.900489931@verdi.nethelp.no> References: <3972.900489931@verdi.nethelp.no> <199807150646.XAA07711@usr06.primenet.com> Date: Wed, 15 Jul 1998 10:40:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3972.900489931@verdi.nethelp.no> sthaug@nethelp.no writes: : Just how inexpensive are we talking here? Where can we buy the stuff? I do know that at least two palm top and one hand held PC running Windows CE use the Vr4111 chip. These range in price from $300 to $400 depending on RAM, ROM and features (eg modem or no modem). I'd love to port FreeBSD to one of these boxes. I've been workign on getting OpenBSD to grok the 411x differences from the rest of the MIPS ISA III 4xxx chips: different cache sizing, ability to grok and execute MIPS-16 code and the vast array of cool devices that are on chip. However, the project is currently hampered by two things. One is lack of hardware, and the second is no known way to bootstrap into the flash of these boxes... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 13:32:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12297 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 13:32:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA12281 for ; Wed, 15 Jul 1998 13:32:51 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ywYDk-0000j7-00; Wed, 15 Jul 1998 14:32:12 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA00108; Wed, 15 Jul 1998 10:32:08 -0600 (MDT) Message-Id: <199807151632.KAA00108@harmony.village.org> To: bmah@CA.Sandia.GOV Subject: Re: Package version checker Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Jul 1998 08:12:44 PDT." <199807141512.IAA26885@stennis.ca.sandia.gov> References: <199807141512.IAA26885@stennis.ca.sandia.gov> Date: Wed, 15 Jul 1998 10:32:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807141512.IAA26885@stennis.ca.sandia.gov> Bruce A. Mah writes: : I've written a Perl 5 script that checks the installed version of : ports/packages against an index file (a la /usr/ports/INDEX, or the on-line : equivalent) to see which ones might be out of date. I'm not real proud of : this quick hack, but if it'd be useful to anyone, I've put it at: Cool. This is one of the cool things that my brother was recently telling me about in one of the Linux distributions that he was using. Namely you could type a single command, and it would go out, grab source and install stuff that has been updated (eg the ports system plus some database to allow one to update at will). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 13:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13586 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 13:44:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA13577 for ; Wed, 15 Jul 1998 13:44:47 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA11744 (5.67b/IDA-1.5); Wed, 15 Jul 1998 22:12:49 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA03283; Wed, 15 Jul 1998 22:03:32 +0200 (CEST) From: Wilko Bulte Message-Id: <199807152003.WAA03283@yedi.iaf.nl> Subject: Re: Software RAID-5 performance In-Reply-To: <19980715094757.P15083@freebie.lemis.com> from Greg Lehey at "Jul 15, 98 09:47:57 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 15 Jul 1998 22:03:32 +0200 (CEST) Cc: tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, 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+ PL38 (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 Greg Lehey wrote... > On Tuesday, 14 July 1998 at 20:05:16 +0200, Wilko Bulte wrote: > > As Greg Lehey wrote... > >> (trimming -fs) > > > >>> Software RAID is a data integrity issue, not a performance one, > >>> and I think making the performance argument for whatever reason > >>> (protection domain crossing, interleaved I/O, SMP scalability, > >>> etc.) is a strawman at best. > >> > >> I'm not sure that I understand what you're saying here. Obviously > >> offloading the checksum calculation (or anything else, for that > >> matter) to an external box will offload the CPU. And I can't see any > >> particular difference in data integrity between the two approaches. > > > > Software raid without stable (battery backed) storage is flawed: > > > > assume a write that had 2 disks actually write the data onto the platter > > and (e.g.) the parity data did not make it out on it's platter because your > > system crashed. Or the power went bang. Or... > > > > You now have an inconsistent raid5 set. > Correct. Similar things happen if a disk loses power while writing, > but the window is larger for RAID-5, and it's much more difficult to > detect. There are a number of "solutions", of course: > 1. Intent logging. Save some copy of the data elsewhere first. > Slow. > > 2. Battery backup. Doesn't guard against panics and non-disk > hardware failure. That is why standalone RAID boxes these days use dual RAID controllers and mirrored write back caches. Obviously this is expensive. Nothing really guards against panics. > 3. As long as the disks didn't physically fail, rebuild the RAID-5 > set after rebooting. I don't think this solves it, as you don't know which block is up to date and which block is not. Or do I miss your point? W/ _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 13:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14482 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 13:48:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14467 for ; Wed, 15 Jul 1998 13:48:16 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-112.camalott.com [208.229.74.112]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA29347; Wed, 15 Jul 1998 15:48:36 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA15101; Wed, 15 Jul 1998 15:47:46 -0500 (CDT) (envelope-from joelh) Date: Wed, 15 Jul 1998 15:47:46 -0500 (CDT) Message-Id: <199807152047.PAA15101@detlev.UUCP> To: matthew@wolfepub.com CC: hackers@FreeBSD.ORG In-reply-to: <3.0.3.32.19980715153323.00733ab8@wolfepub.com> (message from Matthew Hagerty on Wed, 15 Jul 1998 15:33:23 -0400) Subject: Re: Protecting data in memory From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <3.0.3.32.19980715153323.00733ab8@wolfepub.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any way to protect a programs memory space from all users, even > root? No. root always has access to all memory space. Consider: If it were otherwise, root could just patch the kernel and gain whatever access was needed. > I am developing an encryption program that has to run as a daemon. > Upon start-up the program would prompt for the key, Right there, you have a place where an intruder, if they have sufficient time and access, can gain access to your key. An intruder who gains root access can put a shell around your program and have the key delivered by email on a silver platter come next boot. Your design, if it is supposed to be secure against root compromise, is flawed. There aren't many designs that can withstand that. By using a hardware device with its own keypad to enter the key, and have it do the processing, then you can secure against key compromise. But then what about the plaintext as it's being sent to the daemon and the device? That could still be intercepted. (However, a plaintext compromise scenario often isn't as bad as a private key compromise scenario.) > If this is not possible (protecting the key), then can someone shed > some light on how I can protect sensitive data on an on-line > machine? I know, I know, but this data "has" to be on-line for > processing that happens all day long. Sorry. The best you can do is make it difficult for an intruder to compromise your machine. Normally, putting a firewall and other normal security measures between the secured network (your LAN or part of it) and the insecure access points (the Internet or the rest of your LAN or whatever) would be called for. You mentioned that your program is doing encryption, but you never said anything about decryption. If you're only doing encryption, look at public key. (Did you say you're using IDEA? There you have it.) This will still leave you vulnerable to trojan horse attacks (which means that plaintexts going to the daemon are vulnerable), but will mean that a compromised key alone would not give the intruder the ability to restore plaintexts from previously intercepted ciphertexts. (It would, however, give forging capabilities to the recipient.) Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 14:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16472 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 14:09:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16464 for ; Wed, 15 Jul 1998 14:09:52 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id RAA16485; Wed, 15 Jul 1998 17:09:29 -0400 (EDT) Date: Wed, 15 Jul 1998 17:09:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Matthew Hagerty cc: hackers@FreeBSD.ORG Subject: Re: Protecting data in memory In-Reply-To: <3.0.3.32.19980715153323.00733ab8@wolfepub.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, 15 Jul 1998, Matthew Hagerty wrote: > Is there any way to protect a programs memory space from all users, even > root? I am developing an encryption program that has to run as a daemon. > Upon start-up the program would prompt for the key, then slip into daemon > land. If the server is compromised (root access is gained) can I prevent > the cracker from reading the program's memory and gaining access to the key > data? As long as I can keep the key secure, the data should be safe (I'm > using IDEA in chain-block mode). I'm currently writing the program in C. > > If this is not possible (protecting the key), then can someone shed some > light on how I can protect sensitive data on an on-line machine? I know, I > know, but this data "has" to be on-line for processing that happens all day > long. There was discussion on freebsd-security recently about using the immutable flag to prevent debuggers/etc from attaching to processes exec'd from the file. I think this is mis-use of the immutable flag, and instead recommended a flag specifically implying process protection when running -- this would have several effects, including: 1. Preventing core dumps to disk for the process 2. Preventing debuggers from attaching to the process 3. Making /proc access to its memoryspace/etc disabled (sort of 2) 4. Preventing ktrace/truss from attaching to the process 5. Limiting signal delivery to the process (to prevent premature exit, etc). 6. Other things here? This might be good for audit daemons, key/token managers, etc. I was thinking of implementing this some time in the next few weeks -- if there are any items missing from the list above, please let me know... Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 14:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17230 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 14:12:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17221 for ; Wed, 15 Jul 1998 14:12:34 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id RAA16504; Wed, 15 Jul 1998 17:12:15 -0400 (EDT) Date: Wed, 15 Jul 1998 17:12:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Joel Ray Holveck cc: matthew@wolfepub.com, hackers@FreeBSD.ORG Subject: Re: Protecting data in memory In-Reply-To: <199807152047.PAA15101@detlev.UUCP> 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, 15 Jul 1998, Joel Ray Holveck wrote: > > Is there any way to protect a programs memory space from all users, even > > root? > > No. root always has access to all memory space. Consider: If it were > otherwise, root could just patch the kernel and gain whatever access > was needed. On the contrary. This is the purpose of securelevels and read-only files/file-systems. UID != supervisor mode access to the machine, and should not be equal to. Currently, indeed, there are many loopholes in the securelevel mechanism, but it is a worthwhile goal. I'd rather not have to completely scrap machines when they are compromised -- rather, know I have a trusted kernel and root file system, and just reinstall application-land. Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 14:33:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19766 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 14:33:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19754 for ; Wed, 15 Jul 1998 14:33:01 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA29039; Wed, 15 Jul 1998 14:32:46 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd029011; Wed Jul 15 14:32:41 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA20814; Wed, 15 Jul 1998 14:32:37 -0700 (MST) From: Terry Lambert Message-Id: <199807152132.OAA20814@usr08.primenet.com> Subject: Re: Wrong comment in pmap_bootstrap() about virtual_avail? To: sthaug@nethelp.no Date: Wed, 15 Jul 1998 21:32:37 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <3972.900489931@verdi.nethelp.no> from "sthaug@nethelp.no" at Jul 15, 98 10:05:31 am X-Mailer: ELM [version 2.4 PL25] 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 > > Maybe he's proting FreeBSD to the relatively high powered, yet > > very inexpensive MIPS chip based systems that are out there. > ... > > Still, are you aware that the "Cobalt" thin server platform, running > > MIPS Linux, has hardware about 1/3 as expensive as comparable Intel > > hardware? > > Just how inexpensive are we talking here? Where can we buy the stuff? You can by MIPS chips and smaple PC boards from MIPS, Inc.. As far as price, Nintendo machines run MIPS chips, and are under $200. Cobalt is a just a company using their own MIPS-based proprietary hardware and a Linux OS to sell, effectively, Linux PC's in blue cubic boxes. If you are interested in blue cubic boxes, they don't sell them seperately; you would be better of finding an old "Cubix" box with an 386 or 486, painting it blue, and running FreeBSD on it. 8-). Or you could always ort to the '030/'040 and paint an old "NeXT cube" blue... 8-) 8-). For an embedded system, non-Intel hardware is almost invariably cheaper. You could get "Cobalt" class SPARC hardware directly from Sun for resale for under $1000 for quantity, for example, and that's ssuming expensive Sun cases and paying for their board design instead of your own, and giving them margin on everything including the hard disk, instead of just on the processor and necessary support chips. You could probably do a JAVA-chip based system even cheaper (JAVA rings go for $50), but of course it would suck because it wouldn't be capable of running BSD. 8^p. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 14:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22712 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 14:56:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22693 for ; Wed, 15 Jul 1998 14:56:32 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA07159; Wed, 15 Jul 1998 17:55:54 -0400 (EDT) (envelope-from luoqi) Date: Wed, 15 Jul 1998 17:55:54 -0400 (EDT) From: Luoqi Chen Message-Id: <199807152155.RAA07159@lor.watermarkgroup.com> To: joelh@gnu.org, matthew@wolfepub.com Subject: Re: Protecting data in memory Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there any way to protect a programs memory space from all users, even > > root? > > No. root always has access to all memory space. Consider: If it were > otherwise, root could just patch the kernel and gain whatever access > was needed. Actually, if you raise the securelevel to 1 or above, not even root can access kernel memory space (see init(8)). It is still possible to access user process memory space through procfs -- procfs doesn't yet check securelevel before granting access to mem file. To disable procfs, remove PROCFS option from your kernel config file (you may also want to compile file systems like NFS into the kernel instead of lkms), make a new kernel. Remove /proc entry from /etc/fstab, raise securelevel at the very beginning of your /etc/rc file. Boot from the new kernel, and you should be all set. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 15:31:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27359 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 15:31:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27349 for ; Wed, 15 Jul 1998 15:31:33 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id PAA01224 for hackers@freebsd.org; Wed, 15 Jul 1998 15:30:55 -0700 (PDT) (envelope-from dhw) Date: Wed, 15 Jul 1998 15:30:55 -0700 (PDT) From: David Wolfskill Message-Id: <199807152230.PAA01224@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: Embedded systems In-Reply-To: <199807152132.OAA20814@usr08.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I changed the subject, since this thread hasn't had a whole lot to do with that comment in a long time.... dhw] >From: Terry Lambert >Date: Wed, 15 Jul 1998 21:32:37 +0000 (GMT) >For an embedded system, non-Intel hardware is almost invariably >cheaper.... When I was working for a (very) small company that provided fairly inexpensive ports (& a years' worth of support) of gcc (& friends), primarily for embedded systems developers, the most common configuration requested was for generating 68k code while running on PC-DOS. There was a smattering of other targets MIPS 4k; i860; a few others. But 68k target on PC-DOS was easily 10x the quantity of the next-most- requested flavor. Many of the requestors were folks building things in their garages; costs were non-trivial concerns. That was, however, about 4 years ago.... david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 16:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01903 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 16:06:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01898 for ; Wed, 15 Jul 1998 16:06:41 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-112.camalott.com [208.229.74.112]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA05444; Wed, 15 Jul 1998 18:06:49 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA15377; Wed, 15 Jul 1998 18:05:58 -0500 (CDT) (envelope-from joelh) Date: Wed, 15 Jul 1998 18:05:58 -0500 (CDT) Message-Id: <199807152305.SAA15377@detlev.UUCP> To: robert+freebsd@cyrus.watson.org CC: matthew@wolfepub.com, hackers@FreeBSD.ORG In-reply-to: (message from Robert Watson on Wed, 15 Jul 1998 17:12:15 -0400 (EDT)) Subject: Re: Protecting data in memory From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Is there any way to protect a programs memory space from all users, even >>> root? >> No. root always has access to all memory space. Consider: If it were >> otherwise, root could just patch the kernel and gain whatever access >> was needed. > On the contrary. This is the purpose of securelevels and read-only > files/file-systems. I realize this. I was actually giving a simplistic example. Yes, you can prevent the kernel from being patched. You would also have to prevent trojan horse attacks elsewhere (ie, r/o /usr and /), not to mention avoid root managing to patch the in-core kernel, etc, etc. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 16:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02175 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 16:08:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02162 for ; Wed, 15 Jul 1998 16:08:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-112.camalott.com [208.229.74.112]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA05526; Wed, 15 Jul 1998 18:08:35 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA15384; Wed, 15 Jul 1998 18:07:48 -0500 (CDT) (envelope-from joelh) Date: Wed, 15 Jul 1998 18:07:48 -0500 (CDT) Message-Id: <199807152307.SAA15384@detlev.UUCP> To: luoqi@watermarkgroup.com CC: matthew@wolfepub.com, hackers@FreeBSD.ORG In-reply-to: <199807152155.RAA07159@lor.watermarkgroup.com> (message from Luoqi Chen on Wed, 15 Jul 1998 17:55:54 -0400 (EDT)) Subject: Re: Protecting data in memory From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807152155.RAA07159@lor.watermarkgroup.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Is there any way to protect a programs memory space from all users, even >>> root? >> No. root always has access to all memory space. Consider: If it were >> otherwise, root could just patch the kernel and gain whatever access >> was needed. > Actually, if you raise the securelevel to 1 or above, not even root can > access kernel memory space (see init(8)). Er, according to init(8), then root cannot *write* to kernel memory. I am basically familiar with securelevel. I oversimplified my example. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 16:55:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07656 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 16:55:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07650; Wed, 15 Jul 1998 16:55:52 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id TAA17006; Wed, 15 Jul 1998 19:55:44 -0400 (EDT) Date: Wed, 15 Jul 1998 19:55:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-security@FreeBSD.ORG cc: freebsd-hackers@FreeBSD.ORG Subject: Announcement: 0.2 Release: Experimental Authentication and Authorization Token Management Extensions in the FreeBSD Kernel 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 This is the release announcement for ktokens-0.2, now available for download from http://www.watson.org/fbsd-hardening/tokens/ Announcements of future versions will be made only to the FreeBSD Security mailing list (freebsd-security@freebsd.org) and not freebsd-hackers. If there is sufficient interest from parties not subscribed to freebsd-security, I will set up an announcement mailing list for ktokens. New Features since 0.1 ---------------------- - Mod unload garbage collection now works - Bug fixes - Rudimentary TOKEND behavior implemented - KerberosIV patches to use Tokens/PAGs - Setuidtoken implemented as sample syscall access control behavior - More extensive user test utilities - Makefiles improved -- make install added (What follows is the same as the 0.1 announcement) Experimental Authentication and Authorization Token Management Extensions in the FreeBSD Kernel Robert Watson Abstract FreeBSD, a derivative of the 4.4BSDlite research operating system developed at the University of California at Berkeley, is used in a variety of networked and stand-alone computing environments. FreeBSD makes use of a simple yet flexible user-based authorization model following the UNIX example. However, this model is not scalable across large computing infrastructures with multiple administrative domains, and the model does not interact well with the differing paradigms supported by a variety of network operating systems. This document proposes a set of extensions to the FreeBSD kernel providing both authentication and authorization "tokens", allowing greater flexibility in supporting a variety of authentication and authorization models. Tokens are the kernel's representation of a fragment of data relating to the capabilities and keying material associated with a set of processes, or Process Authentication Group (PAG). A sample implementation of a subset of the described token behavior via a loadable kernel module available for download, along with a set of utilities for experimenting with the token behavior. Expansion on the implementation to provide additional features and sample uses will be forthcoming. URL: http://www.watson.org/fbsd-hardening/tokens/ Email: robert+sec.ktokens@cyrus.watson.org The freebsd-security@freebsd.org mailing list is also an appropriate place to discuss the issues involved. Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 17:14:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11523 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 17:14:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts03-117.dublin.indigo.ie [194.125.148.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11455 for ; Wed, 15 Jul 1998 17:14:02 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id BAA02112; Thu, 16 Jul 1998 01:08:33 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807160008.BAA02112@indigo.ie> Date: Thu, 16 Jul 1998 01:08:33 +0000 In-Reply-To: <199807152155.RAA07159@lor.watermarkgroup.com>; Luoqi Chen Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Luoqi Chen , joelh@gnu.org, matthew@wolfepub.com Subject: Re: Protecting data in memory Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 15, 5:55pm, Luoqi Chen wrote: } Subject: Re: Protecting data in memory > > Actually, if you raise the securelevel to 1 or above, not even root can > access kernel memory space (see init(8)). It is still possible to access > user process memory space through procfs -- procfs doesn't yet check And ptrace(2). Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: 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 Wed Jul 15 17:34:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13661 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 17:34:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13654 for ; Wed, 15 Jul 1998 17:34:10 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA08157; Wed, 15 Jul 1998 20:33:32 -0400 (EDT) (envelope-from luoqi) Date: Wed, 15 Jul 1998 20:33:32 -0400 (EDT) From: Luoqi Chen Message-Id: <199807160033.UAA08157@lor.watermarkgroup.com> To: joelh@gnu.org, luoqi@watermarkgroup.com Subject: Re: Protecting data in memory Cc: hackers@FreeBSD.ORG, matthew@wolfepub.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> Is there any way to protect a programs memory space from all users, even > >>> root? > >> No. root always has access to all memory space. Consider: If it were > >> otherwise, root could just patch the kernel and gain whatever access > >> was needed. > > Actually, if you raise the securelevel to 1 or above, not even root can > > access kernel memory space (see init(8)). > > Er, according to init(8), then root cannot *write* to kernel memory. > Sorry, I was wrong. Root is still able to read kernel memory. My solution won't work. :( -lq > I am basically familiar with securelevel. I oversimplified my > example. > > Best, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 18:04:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17612 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 18:04:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from doughnut.cc.uq.edu.au (tony@doughnut.cc.uq.edu.au [130.102.128.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17466; Wed, 15 Jul 1998 18:04:02 -0700 (PDT) (envelope-from T.Jago@prentice.uq.edu.au) Received: (from tony@localhost) by doughnut.cc.uq.edu.au (8.8.6/8.8.6) id LAA25200; Thu, 16 Jul 1998 11:00:24 +1000 (EST) X-Authentication-Warning: doughnut.cc.uq.edu.au: tony set sender to T.Jago@prentice.uq.edu.au using -f Date: Thu, 16 Jul 1998 11:00:14 +1000 (EST) To: Brian McGovern cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG, Poul-Henning Kamp , Kazutaka Yokota , hardware@FreeBSD.ORG Subject: PSM problem... [ intel motherboard and silo problems ] Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From: Tony Jago Organization: University of Queensland X-Key-Fingerprint: 48 3F 5D FB 37 51 01 C5 A1 82 B1 6B 76 2C 75 9D X-PGP-Key-URL: http://doughnut.cc.uq.edu.au/pub/pgp-keys/T.Jago@prentice.uq.edu.au X-Direct-Email: tony@scar.uq.edu.au Comments: This mail has been PGP signed. (http://www.pgp.com/) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Brian, In found your e-mail about problems getting your PS/2 port on an intel AL440LX motherboard to work. I own an AL440LX as well and had exactly the same problem: > psm0: current command byte:0047 > kbdio: TEST_AUX_PORT status:00fa > kbdio: DIAGNOSE status:0055 > kbdio: TEST_KBD_PORT status:00fa > psm: keyboard port failed. > psm0: the aux port is not functioning (250). > psm0 not found at 0x60 My mouse worked fine under windows 95 as yours did. Under Win95 the mouse port was reported to be on int 12 which was what freebsd expected it to be. The mouse had worked when I installed FreeBSD originally so I suspected it was something I had changed. The only thing I could think of was a BIOS upgrade so I rolled back the BIOS to P08 and everything started working! Then I rolled it forward to the current version P09 and it still worked! The BIOS changes caused the CMOS memory to get cleared and caused the system to re-run the Plug and Play doobie so perhaps this is what fixed it. I also had another problem with the machine. I was constantly getting silo over flows when using my modem. The best transfer rate I could get was about 3K a second. At this point a silo overflow would occurr and a packet would get dropped and the TCP stack would drop back its transfer rate. I had to set my modem port to 38400 and even then I would have the occasional over flow under heavy load. This BIOS down-up-grade fixed this problem as well! I can now run the 56K modem at 115200 bps with not a single overflow. Transfering some text files using the modem compression ran the comm port up to the 115200 limit with no problems. Under windows 95 the modem would work with the default settings but if you moved the buffer size sliders up to maximum then a similar problem would happen just the windows just silently dropped the packets and no error was reported. Thanks again for posting to the mailing list. Without your e-mail I am sure I would have never worked out what the problem was. - --- Tony Jago, Systems Programmer, E-Mail: T.Jago@prentice.uq.edu.au Facilities Management Services, Phone: +61 7 3365 4078 Prentice Centre, The University of Fax: +61 7 3365 4477 Queensland. Brisbane, Australia. 4072. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBNa1QpphPSpCDJcQFAQG0UQP/RCs1pGPCwMThVodaK0HuXfgURCniY6d+ yptWFobwAyctZR+p3BT23re5PhstXMQsCgF5TB7ULCNUuS0veNCTTin6fwMH/849 g4mBgeRB6Bk4tl+BR5A16prKERQ8CS2aiRdQlxXrhPwvJYrPmIHz1JFGxHgQW08C IgPO4wkAA+0= =QdDN -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 19:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28078 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 19:27:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28073 for ; Wed, 15 Jul 1998 19:27:21 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id TAA05432 for ; Wed, 15 Jul 1998 19:26:27 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id WAA14153 for ; Wed, 15 Jul 1998 22:27:08 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id WAA00522 for ; Wed, 15 Jul 1998 22:58:31 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id WAA00296 for freebsd-hackers@freefall.cdrom.com; Wed, 15 Jul 1998 22:31:16 -0400 (EDT) Date: Wed, 15 Jul 1998 22:31:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807160231.WAA00296@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com Subject: Mysterious reboots w/2.2.6-RELEASE. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may recall that I reported a few crashes with the 2.2.6-RELEASE and sent in tracebacks... but the kernel was not config'd -g so there was little info in the tracebacks. I promised to build a DEBUG kernel and report my findings. Well - after a week or two, I have little to report. It seems that the machine is still mysteriously crashing, but now I don't get anything in /var/crash. I just had the opportunity to see first-hand this happen; I was working and suddenly - "poof" away things went. On the reboot - savecore issued the message "savecore: no core dump". That is; the machine apparently just rebooted - no panic or nothing... Has anyone else experienced mysterious, non-panic reboots? This is while in X, and didn't seem to happen with the 2.2.5-RELEASE. Perhaps there's something in the X code (Matrox Millenium II card) that's causing this spontaneous reboot... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 19:38:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29138 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 19:38:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29093 for ; Wed, 15 Jul 1998 19:37:57 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from sunix (eculp@sunix.mexcom.net [206.103.64.3]) by dns.webwizard.net.mx (8.8.8/8.8.7) with SMTP id VAA23907; Wed, 15 Jul 1998 21:36:31 -0500 (CDT) Message-ID: <35AD5A92.78123D1B@webwizard.org.mx> Date: Wed, 15 Jul 1998 20:42:42 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: dk+@ua.net CC: freebsd-hackers@FreeBSD.ORG Subject: Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago References: <19980714212139.48766@dog.farm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Kohmanyuk =?KOI8-R?B?5M3J1NLJyiDrz8jNwc7Ayw==?= wrote: > > there is no binary for freebsd, but this one works: > > There is now :-) Hot out of the oven ftp://ftp.netscape.com/pub/communicator/4.5/4.5_PR1/english/unix/freebsd2/communicator-v45b1-export.x86-unknown-freebsd.tar.gz If the url isn't right it's close :-) ed > > (there are 3 linux packages...) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Ahora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 22:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17354 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 22:44:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elcat-gtw1.bishkek.su (elcat-gw.Nursat.net [194.226.137.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17250 for ; Wed, 15 Jul 1998 22:44:26 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.229.1]) by elcat-gtw1.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id LAA16962 ;Thu, 16 Jul 1998 11:30:30 +0600 (KGST) Received: from freenet.bishkek.su (freenet.bishkek.su [193.125.230.1]) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id KAA03272 ;Thu, 16 Jul 1998 10:27:32 +0600 (KGST) Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id KAA14212; Thu, 16 Jul 1998 10:31:18 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id KAA31658; Thu, 16 Jul 1998 10:32:13 +0300 Date: Thu, 16 Jul 1998 10:32:13 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: Alfred Perlstein cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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's REALLY time you upgraded. 2.2.1 has accumilated a long list of holes, > you are vulnerable to several TCP/IP DoS attacks as well as > vulnerabilities in the userland tools > > get a copy of 2.2.6 (maybe 2.2.7, it' out i heard) you should be fine > Well, I have CD of 2.2.5 around, but is it possible to upgrade the kernel without touching/recompiling the rest of binaries. I came to BSD from the linux world, and there it wasn't problem at all, but in BSD things are much different.. so.. anyway, thanks for your help,... Fyodor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 22:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17715 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 22:46:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elcat-gtw1.bishkek.su (elcat-gw.Nursat.net [194.226.137.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17685 for ; Wed, 15 Jul 1998 22:46:40 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.229.1]) by elcat-gtw1.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id LAA17234 ;Thu, 16 Jul 1998 11:33:03 +0600 (KGST) Received: from freenet.bishkek.su (freenet.bishkek.su [193.125.230.1]) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id KAA03758 ;Thu, 16 Jul 1998 10:35:01 +0600 (KGST) Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id KAA14402; Thu, 16 Jul 1998 10:38:50 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id KAA00515; Thu, 16 Jul 1998 10:39:44 +0300 Date: Thu, 16 Jul 1998 10:39:44 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: Andreas Klemm cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. In-Reply-To: <19980714190149.A1062@klemm.gtn.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 > > update /usr/src using cvsup > cd /usr/src > make buildworld > make installworld > > That's the advantage of FreeBSD over xxx ... ;-) :) seems BSD has some advantages which i haven't explored yet.(comparing to Linux). Hmm.. So far by this moment I was considering updating binaries/kernel as rather more compicated procedure. Hmm.. I still don't exactly understand the purpose of CVS things.. but hmm.. :) we are here to learn. Thanks for your hints. > Fine tune /etc/rc scripts on demand with things in /usr/src/etc > manually ... New is the main config file rc.conf instead of > system.conf (if I remember right) ... All rightie. I will play with it. Hmm.. By the way, can anyone share why in BSD it was decided to avoid inittab things (while init's still present), so far I see in systems havin' inittab it makes configuration much more flexible... maybe my opinion is just biased by Linux expirience tho.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 23:12:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20242 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 23:12:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20223 for ; Wed, 15 Jul 1998 23:12:18 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id CAA12953; Thu, 16 Jul 1998 02:01:05 -0400 (EDT) Date: Thu, 16 Jul 1998 02:01:03 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: CyberPsychotic cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 16 Jul 1998, CyberPsychotic wrote: > Well, I have CD of 2.2.5 around, but is it possible to upgrade the > kernel without touching/recompiling the rest of binaries. I came to BSD > from the linux world, and there it wasn't problem at all, but in BSD > things are much different.. so.. > > anyway, thanks for your help,... The supported procedure is to make world (userland) and then build your new kernel, if you're upgrading to newer source. However, if config(8) hasn't changed, you might be able to get away with building the kernel only. Why would you want to, though? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 15 23:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21404 for freebsd-hackers-outgoing; Wed, 15 Jul 1998 23:23:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elcat-gtw1.bishkek.su (elcat-gw.Nursat.net [194.226.137.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21393 for ; Wed, 15 Jul 1998 23:23:22 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.229.1]) by elcat-gtw1.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id MAA18040 ;Thu, 16 Jul 1998 12:21:52 +0600 (KGST) Received: from freenet.bishkek.su (freenet.bishkek.su [193.125.230.1]) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id MAA05544 ;Thu, 16 Jul 1998 12:21:02 +0600 (KGST) Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id MAA18812; Thu, 16 Jul 1998 12:25:01 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id MAA23716; Thu, 16 Jul 1998 12:25:53 +0300 Date: Thu, 16 Jul 1998 12:25:52 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: ben@rosengart.com cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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 > > from the linux world, and there it wasn't problem at all, but in BSD > > things are much different.. so.. > > > > anyway, thanks for your help,... > > The supported procedure is to make world (userland) could you please clarify abit, what's meant as "world" in BSD? the set of binaries? Some other environment? > and then build your > new kernel, if you're upgrading to newer source. However, if config(8) > hasn't changed, you might be able to get away with building the kernel hmm.. The things with kernel stuff (i.g. in what packages it's distributed, what actions are supposed to be taken. What are directories/files/binaries dependences etc) is still cloudy to me abit, is there manual covering such things? I looked thro handbook and some manuals with no much related info there. > only. Why would you want to, though? well, the primary problem is : I have kernel 2.2.1 on some machine installed, and when I recompiled kernel there to support firewalling, machine started crashing every 15 mins blaming routed daemon in it. For one of the solutions I was suggested to upgrade kernel there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 00:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26455 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 00:01:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26449 for ; Thu, 16 Jul 1998 00:01:34 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id CAA12305; Thu, 16 Jul 1998 02:56:31 -0400 (EDT) Date: Thu, 16 Jul 1998 02:56:29 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: CyberPsychotic cc: ben@rosengart.com, Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 16 Jul 1998, CyberPsychotic wrote: > > The supported procedure is to make world (userland) > > could you please clarify abit, what's meant as "world" in BSD? the set of > binaries? Some other environment? World in this case refers to the whole system (/bin and /usr/bin but not /usr/local/bin, for example). > > and then build your > > new kernel, if you're upgrading to newer source. However, if config(8) > > hasn't changed, you might be able to get away with building the kernel > > hmm.. The things with kernel stuff (i.g. in what packages it's > distributed, what actions are supposed to be taken. What are > directories/files/binaries dependences etc) is still cloudy to me abit, is > there manual covering such things? I looked thro handbook and some manuals > with no much related info there. The kernel is distributed with the rest of the system. Look at the section in the handbook about keeping current with ctm or cvsup. > > only. Why would you want to, though? > > well, the primary problem is : I have kernel 2.2.1 on some machine > installed, and when I recompiled kernel there to support firewalling, > machine started crashing every 15 mins blaming routed daemon in it. For > one of the solutions I was suggested to upgrade kernel there. If I were you, I would install cvsup from ports or packages, cvsup to the latest 2.2.6-stable source, "make world", and rebuild and install my kernel. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 00:35:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29685 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 00:35:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29680 for ; Thu, 16 Jul 1998 00:35:42 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA20531 ; Thu, 16 Jul 1998 09:29:43 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA14667; Thu, 16 Jul 1998 09:29:42 +0200 To: ben@rosengart.com Cc: CyberPsychotic , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 16 Jul 1998 09:29:42 +0200 In-Reply-To: Snob Art Genre's message of Thu, 16 Jul 1998 02:56:29 -0400 (EDT) Message-ID: Lines: 12 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre writes: > If I were you, I would install cvsup from ports or packages, cvsup to > the latest 2.2.6-stable source, "make world", and rebuild and install my > kernel. There isn't much choice, really. He'll at the very least have to rebuild mount(8) if he goes for -stable or 2.2.7, due to the slice name change. Just building a kernel won't do much good. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.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 16 01:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09025 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 01:34:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09012; Thu, 16 Jul 1998 01:34:07 -0700 (PDT) (envelope-from Majordomo-Owner@FreeBSD.ORG) Date: Thu, 16 Jul 1998 01:34:07 -0700 (PDT) Message-Id: <199807160834.BAA09012@hub.freebsd.org> To: freebsd-hackers@FreeBSD.ORG From: Majordomo@FreeBSD.ORG Subject: Confirmation for subscribe freebsd-hackers Reply-To: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Please be sure to read the charters before subscribing or sending mail to any FreeBSD mailing list for an explanation of which topics are relevant for a given list and what types of postings are and are not allowed. They may be found at: http://www.freebsd.org/handbook/eresources:charters.html Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "freebsd-hackers@FreeBSD.ORG". If you really want this action to be taken, please send the following commands (exactly as shown) back to "Majordomo@FreeBSD.ORG": auth e659031c subscribe freebsd-hackers freebsd-hackers@freebsd.org If you do not want this action to be taken, simply ignore this message and the request will be disregarded. If your mailer will not allow you to send the entire command as a single line, you may split it using backslashes, like so: auth e659031c subscribe freebsd-hackers \ freebsd-hackers@freebsd.org If you have any questions about the policy of the list owner, please contact "freebsd-hackers-approval@FreeBSD.ORG". Thanks! Majordomo@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 16 05:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29354 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 05:01:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29348 for ; Thu, 16 Jul 1998 05:01:25 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA24845 for ; Thu, 16 Jul 1998 05:00:29 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA11874 for ; Thu, 16 Jul 1998 08:01:05 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id IAA01536 for ; Thu, 16 Jul 1998 08:32:41 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA01215 for freebsd-hackers@freefall.cdrom.com; Thu, 16 Jul 1998 08:05:13 -0400 (EDT) Date: Thu, 16 Jul 1998 08:05:13 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807161205.IAA01215@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com Subject: ipfw rules for exposing an internal machine's port externally? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent the following to freebsd-questions; but nothing has come of it, so I thought, perhaps, freebsd-hackers might be a better forum... - Thanks - - Dave Rivers - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I thought I should be able to do this; but it doesn't seem to work well. Perhaps someone knows what I've got wrong here. What I have is a machine "X" which is on the external network and through which I divert all internal traffic on the 10.0.0.x network via ipfw/natd, as in: ipfw add 100 divert 32000 ip from any to any via sl0 However, I have an internal machine (10.0.0.10) that's set up to do telnet connections on a different port (e.g. port #PPPP in the following example.) I would like to make those connections available externally. So - I've got added: ipfw add 50 pass log tcp from any PPPP to 10.0.0.10 PPPP ipfw add 50 pass log udp from any PPPP to 10.0.0.10 PPPP But, if I telnet to the gateway machine at port PPPP as in: telnet gateway PPPP all I get is: Trying x.x.x.x... telnet: Unable to connect to remote host: Connection refused If I, however, telnet on the internal network to 10.0.0.10 PPPP I get connected just fine. Has anyone done this before? That is, map a particular port number on one machine to a different one? And, use that with divert to make a service on an internal machine externally visible? If so, how? - Thanks - - 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 16 05:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01542 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 05:21:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from karon.siemens.se (karon.siemens.se [192.121.70.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA01537 for ; Thu, 16 Jul 1998 05:21:00 -0700 (PDT) (envelope-from dpn@profetia.se) Received: by karon.siemens.se; (5.65v3.2/1.3/10May95) id AA02445; Thu, 16 Jul 1998 14:20:50 +0200 Received: from pccon2.sni.se by mailworks; (5.65v3.2/1.1.8.2/04Sep95-1134AM/sal) id AA00403; Thu, 16 Jul 1998 14:20:45 +0200 From: "Dennis Pettersson" To: Subject: subscribe Date: Thu, 16 Jul 1998 14:20:06 +0200 Message-Id: <000001bdb0b4$12405610$8253d495@procon2.sni.se> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------------------------------------------------------- o-o Dennis Pettersson Phone +46 8 584 113 06 |\\ Frihetsvägen 46 Fax +46 8 584 113 06 |(_) SE-177 33 JÄRFÄLLA Mobile +46 708 78 78 66 ||" Sweden || E-mail dpn@profetia.se || HTML http://www.profetia.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 05:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01926 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 05:23:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01901 for ; Thu, 16 Jul 1998 05:23:19 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA25320 for ; Thu, 16 Jul 1998 05:22:12 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id PAA22794; Thu, 16 Jul 1998 15:22:45 +0300 (EEST) (envelope-from ru) Message-ID: <19980716152244.A22669@ucb.crimea.ua> Date: Thu, 16 Jul 1998 15:22:44 +0300 From: Ruslan Ermilov To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: ipfw rules for exposing an internal machine's port externally? Mail-Followup-To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com References: <199807161205.IAA01215@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807161205.IAA01215@lakes.dignus.com>; from Thomas David Rivers on Thu, Jul 16, 1998 at 08:05:13AM -0400 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 16, 1998 at 08:05:13AM -0400, Thomas David Rivers wrote: > > I thought I should be able to do this; but it doesn't > seem to work well. Perhaps someone knows what I've got wrong here. > > What I have is a machine "X" which is on the external network > and through which I divert all internal traffic on the 10.0.0.x > network via ipfw/natd, as in: > > ipfw add 100 divert 32000 ip from any to any via sl0 > > > However, I have an internal machine (10.0.0.10) that's set up > to do telnet connections on a different port (e.g. port #PPPP in > the following example.) > > I would like to make those connections available externally. > > So - I've got added: > > ipfw add 50 pass log tcp from any PPPP to 10.0.0.10 PPPP > ipfw add 50 pass log udp from any PPPP to 10.0.0.10 PPPP > > But, if I telnet to the gateway machine at port PPPP as in: > telnet gateway PPPP > all I get is: > Trying x.x.x.x... > telnet: Unable to connect to remote host: Connection refused > > > If I, however, telnet on the internal network to 10.0.0.10 PPPP > I get connected just fine. > > > > Has anyone done this before? That is, map a particular port number > on one machine to a different one? And, use that with divert to > make a service on an internal machine externally visible? If so, how? > You're missing redirect natd rule, it seems to me. Add the following line in natd config file on "X": redirect_port tcp 10.0.0.10:PPPP PPPP This will tell natd to redirect X:PPPP connection to 10.0.0.10:PPPP. HTH and regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +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 Thu Jul 16 05:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04378 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 05:46:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04373 for ; Thu, 16 Jul 1998 05:46:16 -0700 (PDT) (envelope-from lada@pc8811.gud.siemens.at) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA25871 for ; Thu, 16 Jul 1998 05:44:14 -0700 (PDT) Received: from scesie04.sie.siemens.at (root@[10.1.140.1]) by zwei.siemens.at with ESMTP id OAA09624; Thu, 16 Jul 1998 14:43:02 +0200 (MET DST) Received: from scegud01.gud.siemens.at (scegud01.gud.siemens.at [195.3.240.30]) by scesie04.sie.siemens.at () with ESMTP id OAA28885; Thu, 16 Jul 1998 14:43:04 +0200 (METDST) Received: from pc8811.gud.siemens.at (pc8811.gud.siemens.at [195.3.22.159]) by scegud01.gud.siemens.at (8.8.8/8.8.5) with ESMTP id OAA19949; Thu, 16 Jul 1998 14:43:03 +0200 (METDST) Message-ID: X-Mailer: XFMail 1.2 [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: <199807161205.IAA01215@lakes.dignus.com> Date: Thu, 16 Jul 1998 14:43:05 +0200 (CEST) Organization: Siemens Austria AG From: Marino Ladavac To: Thomas David Rivers Subject: RE: ipfw rules for exposing an internal machine's port externall Cc: freebsd-hackers@freefall.cdrom.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jul-98 Thomas David Rivers wrote: > > > However, I have an internal machine (10.0.0.10) that's set up > to do telnet connections on a different port (e.g. port #PPPP in > the following example.) > > I would like to make those connections available externally. > > So - I've got added: > > ipfw add 50 pass log tcp from any PPPP to 10.0.0.10 PPPP > ipfw add 50 pass log udp from any PPPP to 10.0.0.10 PPPP > > But, if I telnet to the gateway machine at port PPPP as in: > telnet gateway PPPP > all I get is: > Trying x.x.x.x... > telnet: Unable to connect to remote host: Connection refused Hardly any wonder. There is nothing that listens on port PPPP on the gateway machine--ergo, connection refused. > > > If I, however, telnet on the internal network to 10.0.0.10 PPPP > I get connected just fine. Sure, because there is someone listening on port PPPP on 10.0.0.10 > > > > Has anyone done this before? That is, map a particular port number > on one machine to a different one? And, use that with divert to > make a service on an internal machine externally visible? If so, how? First, you don't need divert for that (nor do you want it). What you need is a listener on gateway at port PPPP which then opens a connection to 10.0.0.10 PPPP and forwards all bytes from one end to the other. Take a look at SAMBA, they used to have such a utility (it was used for SMB protocol reverse engineering). /Marino > > - Thanks - > - Dave Rivers - > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------- Marino Ladavac Date: 16-Jul-98 Time: 14:38:05 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 06:14:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07600 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 06:14:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elcat-gtw1.bishkek.su (elcat-gw.Nursat.net [194.226.137.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07503 for ; Thu, 16 Jul 1998 06:14:01 -0700 (PDT) (envelope-from root@elcat2.bishkek.su) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.229.1]) by elcat-gtw1.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id TAA23543 for ;Thu, 16 Jul 1998 19:12:50 +0600 (KGST) Received: from elcat2.bishkek.su (uucp@localhost) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with UUCP id TAA26809 for freebsd-hackers@freebsd.org;Thu, 16 Jul 1998 19:12:33 +0600 (KGST) Received: by elcat2.bishkek.su id TAA06393; (8.7.3/vak/1.8r) Thu, 16 Jul 1998 19:08:04 +0600 (BSD) To: freebsd-hackers@FreeBSD.ORG Message-ID: Organization: Cronyx Ltd. From: "Micro.Softs &" Date: Thu, 16 Jul 98 19:08:03 +0600 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: Please, help me ...... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello . I had a problem with kernel. Version FreeBSD 2.1.7 It gives out the following messages after compilation. ----------------- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1. processor eflags = interrupt enabled, resume, IOPL = 0 current process = 62 (routed) interrupt mask = kernel: type 12 trap, code = 0 ------------------- What you to me will advise? Is beforehand grateful. Rinat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 06:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10751 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 06:39:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from voland.freenet.bishkek.su (voland.freenet.bishkek.su [193.125.230.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09945 for ; Thu, 16 Jul 1998 06:29:31 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from freenet.bishkek.su (mail@freenet.bishkek.su [193.125.230.1]) by voland.freenet.bishkek.su (8.8.8/8.8.8) with ESMTP id TAA31333; Thu, 16 Jul 1998 19:21:15 +0600 Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id TAA01228; Thu, 16 Jul 1998 19:10:46 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id TAA09628; Thu, 16 Jul 1998 19:11:31 +0300 Date: Thu, 16 Jul 1998 19:11:31 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: ben@rosengart.com cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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 > > binaries? Some other environment? > > World in this case refers to the whole system (/bin and /usr/bin but not > /usr/local/bin, for example). so binaries, right? > The kernel is distributed with the rest of the system. Look at the > section in the handbook about keeping current with ctm or cvsup. Ok. Thanks. > > machine started crashing every 15 mins blaming routed daemon in it. For > > one of the solutions I was suggested to upgrade kernel there. > > If I were you, I would install cvsup from ports or packages, cvsup to > the latest 2.2.6-stable source, "make world", and rebuild and install my > kernel. so I will need to get whole three at ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/* and then put it into my /usr/src instead of current stuff? And then I am ready to recompile all the biaries world here, right? By the way can I find all the kernel stuff precompressed somewhere? because I use proxy, and whenever it fetches things, the compression on the fly hardly work. Thanks Fyodor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 06:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11523 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 06:43:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11505 for ; Thu, 16 Jul 1998 06:43:04 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id IAA18138 for ; Thu, 16 Jul 1998 08:40:49 -0400 (EDT) Date: Thu, 16 Jul 1998 08:40:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-Hackers@FreeBSD.ORG Subject: ppp and routing 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 having problems in moving the server I dial into from being an old-ish BSDi system to a FreeBSD system. Both systems _seem_ to operate the same way, but I can't get routing correct on the FreeBSD system. Understand, I'm not talking about my local system, it's the one I dial into that's giving me troubles, so all comments from here on are about either the BSDi server or the FreeBSD server, not my own host (also FreeBSD). The ppp for the old BSDi system is kernel mode, and for the FreeBSD system, it's usermode. Both the servers are on the same local ethernet, and communicate to the same single outgoing gateway. The ppp address for my host (which is static, not dynamic ip) is advertised to the gateway via arp proxying. Both systems seem to stick up the same kind of arp info, and the route (netstat -rn) stuff seems alike, but packets being routed to my host from the gateway are intercepted on the FreeBSD server as if they are destined for that server, and not being passed on to the ppp line. For example, an incoming telnet request gets me a banner from the server (it doesn't make it to my home system). I really want to move to the FreeBSD server, because the old BSDi system has a major bug that's killing throughput. If it would be a help, I could post netstat's and arp listings from the working (but slow) BSDi system and the nonworking (but fast!) FreeBSD system. I can communicate directly the server without any problem. Oh yeah, one last thing, I used sysctl to set net.inet.ip.forwarding to 1, so it would forward packets. I tried setting it to 0 (in case I had the logic backwards) but that didn't help any. Thanks for any hints. Both my home system and the FreeBSD server are running FreeBSD-current. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 06:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13198 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 06:56:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sun-test.hightek.com ([194.74.141.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13182; Thu, 16 Jul 1998 06:56:52 -0700 (PDT) (envelope-from andreas@klemm2.hightek.com) Received: from klemm2.hightek.com ([195.90.203.76]) by sun-test.hightek.com (Netscape Mail Server v1.1) with ESMTP id AAA5030; Thu, 16 Jul 1998 15:56:38 +0200 Received: (from andreas@localhost) by klemm2.hightek.com (8.8.8/8.8.8) id PAA24314; Thu, 16 Jul 1998 15:56:38 +0200 (CEST) (envelope-from andreas) Message-ID: <19980716155638.50690@hightek.com> Date: Thu, 16 Jul 1998 15:56:38 +0200 From: Andreas Klemm To: Majordomo@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Confirmation for subscribe freebsd-hackers References: <199807160834.BAA09012@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199807160834.BAA09012@hub.freebsd.org>; from Majordomo@freebsd.org on Thu, Jul 16, 1998 at 01:34:07AM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 16, 1998 at 01:34:07AM -0700, Majordomo@freebsd.org wrote: > [...] > If you really want this action to be taken, please send the following > commands (exactly as shown) back to "Majordomo@FreeBSD.ORG": > > auth e659031c subscribe freebsd-hackers freebsd-hackers@freebsd.org > [...] Obfuscated majordomo subscriber contest 1998 ? -- B&K Gruppe - Wuppertal phone +49 202 7399 - 170 fax +49 202 7399 - 100 http://www.FreeBSD.ORG/~andreas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 06:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13672 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 06:59:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13655 for ; Thu, 16 Jul 1998 06:59:23 -0700 (PDT) (envelope-from richard@jezebel.demon.co.uk) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id GAA27590 for ; Thu, 16 Jul 1998 06:58:24 -0700 (PDT) Received: from (work.jezebel.demon.co.uk) [158.152.38.143] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0ywoYq-0003N3-00; Thu, 16 Jul 1998 13:59:04 +0000 Received: from [127.0.0.1] by work.jezebel.demon.co.uk with SMTP id 00614360; Thu, 16 Jul 1998 13:58:41 +0000 Message-ID: <35AE0711.D86870C9@jezebel.demon.co.uk> Date: Thu, 16 Jul 1998 14:58:41 +0100 From: Richard Smith Organization: http://www.trltech.co.uk X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: Thomas David Rivers CC: freebsd-hackers@freefall.cdrom.com Subject: Re: ipfw rules for exposing an internal machine's port externally? References: <199807161205.IAA01215@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > I sent the following to freebsd-questions; but nothing has come of it, > so I thought, perhaps, freebsd-hackers might be a better forum... > > - Thanks - > - Dave Rivers - > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > I thought I should be able to do this; but it doesn't > seem to work well. Perhaps someone knows what I've got wrong here. > > What I have is a machine "X" which is on the external network > and through which I divert all internal traffic on the 10.0.0.x > network via ipfw/natd, as in: > > ipfw add 100 divert 32000 ip from any to any via sl0 > > However, I have an internal machine (10.0.0.10) that's set up > to do telnet connections on a different port (e.g. port #PPPP in > the following example.) > > I would like to make those connections available externally. > > So - I've got added: > > ipfw add 50 pass log tcp from any PPPP to 10.0.0.10 PPPP > ipfw add 50 pass log udp from any PPPP to 10.0.0.10 PPPP > > But, if I telnet to the gateway machine at port PPPP as in: > telnet gateway PPPP > all I get is: > Trying x.x.x.x... > telnet: Unable to connect to remote host: Connection refused > > If I, however, telnet on the internal network to 10.0.0.10 PPPP > I get connected just fine. > > Has anyone done this before? That is, map a particular port number > on one machine to a different one? And, use that with divert to > make a service on an internal machine externally visible? If so, how? > > - Thanks - > - Dave Rivers - > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Dave, You need to add a static mapping from the #PPPP port on your firewall to the #PPPP port on 10.0.0.10. Add '-redirect_port tcp 10.0.0.10:PPPP PPPP' to the 'natd' command line, and open up your firewall with something like: $fwcmd add pass tcp from any to ${oip} PPPP setup $fwcmd add pass tcp from any to 10.0.0.10 PPPP setup Bye, -- Richard Smith Assistant Chief Engineer TRL Technology Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 07:31:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17551 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 07:31:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17542 for ; Thu, 16 Jul 1998 07:31:02 -0700 (PDT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.8.8/8.8.8) with ESMTP id QAA27635 for ; Thu, 16 Jul 1998 16:31:58 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <199807161431.QAA27635@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: Special memory board on ISA bus Date: Thu, 16 Jul 1998 16:31:58 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have a special memory board on the ISA bus that responds to addresses from BOARD_BASE up to BOARD_BASE+BOARD_MASK. Now I need to make sure that the memory manager in FreeBSD does not use this part of the memory address space. Is there an "easy" way to do this or do I have to rewrite init386 in /usr/src/sys/i386/i386/machdep.c to ensure that it will not use the board. I also need to make sure that the cache is not used when I read/write to my board. To do this one can use the MTRR:s (Memory Type Range Registers). These registers only exists in a P6 cpu. (see http://www.intel.com/design/pro/manuals/ "Intel Architecture Software Developer's Manual, Volume 3: System Programming Guide" Chapter 9) I have noticed that FBSD detects the existens of MTRR:s but it does not seem to use it anywhere. Is there any support in FBSD to set these registers? Any suggestions on how I should handle uncachable memory in FreeBSD? BTW I've been using FBSD-stable for 2 years but I have never needed to change anything in the kernel before. Please keep that in mind when replying. Any help appreciated. /K - -- Johan Karlsson mailto:k@numeri.campus.luth.se SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 07:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18551 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 07:35:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bb.cc.wa.us (chris@bb.cc.wa.us [134.39.181.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18541 for ; Thu, 16 Jul 1998 07:35:48 -0700 (PDT) (envelope-from chris@bb.cc.wa.us) Received: from localhost (chris@localhost) by bb.cc.wa.us (8.8.8/8.6.9) with SMTP id OAA05797; Thu, 16 Jul 1998 14:26:59 GMT Date: Thu, 16 Jul 1998 07:26:59 -0700 (PDT) From: Chris Coleman Reply-To: Chris Coleman To: CyberPsychotic cc: chrisc@vmunix.com, hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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 cd /usr/ports/net/cvsup-bin make install rehash cp /usr/share/examples/cvsup/stable-supfile /usr/src/ cd /usr/src/ cvsup stable-supfile make buildworld && make installworld cd /sys/i386/conf/ cp GENERIC mykernel vi mykernel config mykernel cd ../../compile/mykernel make depend && make && make install reboot Christopher J. Coleman (whyareyou@lookingforme.com) Computer Support Analyst I (509)-762-6341 FreeBSD Book Project: http://www.vmunix.com/fbsd-book/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 07:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20618 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 07:52:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20609 for ; Thu, 16 Jul 1998 07:52:21 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA00902 for ; Thu, 16 Jul 1998 07:51:23 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id KAA13190 for ; Thu, 16 Jul 1998 10:52:02 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id LAA00274; Thu, 16 Jul 1998 11:23:25 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id KAA01628; Thu, 16 Jul 1998 10:56:09 -0400 (EDT) Date: Thu, 16 Jul 1998 10:56:09 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807161456.KAA01628@lakes.dignus.com> To: rivers@dignus.com Subject: Tantalizingly close (was: ipfw rules for exposing an internal machine's port externally?) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <35AE0711.D86870C9@jezebel.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all the wonderful suggestions I've gotten from fellow hackers - I'm tantalizingly close to being able to expose an internal machine to the external network. But, things are quite working yet [By the way, in case I haven't mentioned - this is with 2.2.6.] Here's what I currently have: [10.0.0.1]$ ipfw list 00100 divert 32000 ip from any to any via sl0 00200 allow tcp from any to 166.82.177.48 7490 00201 allow tcp from any to 10.0.0.10 7490 01000 allow ip from any to any via lo0 01010 deny ip from 127.0.0.0/8 to 127.0.0.0/8 65000 allow ip from any to any 65535 deny ip from any to any [10.0.0.1]$ ifconfig sl0 (external interface) sl0: flags=9011 mtu 552 inet 166.82.177.48 --> 166.82.100.202 netmask 0xffffff00 [10.0.0.1]$ ifconfig ed0 (internal interface) ed0: flags=8843 mtu 1500 inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 ether 66:66:77:00:0b:31 And, natd was run with: /usr/sbin/natd -l -port 32000 -interface sl0 -m -u -dynamic \ -redirect_port tcp 10.0.0.10:7490 7490 When I try to connect to 166.82.177.48 with: telnet 166.82.177.48 7490 (from the 'external world') I no longer get the immediate 'connection refused' [which implies things are getting somewhat routed...] But - I also don't get connected. It eventually times out. [Internal connections from the gateway machine to 10.0.0.10 7490 work just fine.] To me, this implies some route isn't right yet... i.e. the internal machine can't get back to the external network... I have the feeling I'm just missing one little item... which I hope is obvious to the more ipfw/natd-experienced people on the list :-) - Thanks - - 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 16 07:53:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20905 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 07:53:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20691 for ; Thu, 16 Jul 1998 07:52:40 -0700 (PDT) (envelope-from wosch@cs.tu-berlin.de) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id QAA03241; Thu, 16 Jul 1998 16:45:36 +0200 (MET DST) From: Wolfram Schneider Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.9.1/8.9.0) id QAA07255; Thu, 16 Jul 1998 16:45:34 +0200 (MET DST) Date: Thu, 16 Jul 1998 16:45:34 +0200 (MET DST) Message-Id: <199807161445.QAA07255@caramba.cs.tu-berlin.de> To: hackers@FreeBSD.ORG Subject: OpenBSD CVSup service 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 The CVSup server cvsup.de.freebsd.org support now the OpenBSD CVS tree The collections are openbsd-cvs-all full OpenBSD CVS tree (src + www + ports + CVSROOT) openbsd-ports-all Only OpenBSD ports openbsd-src-all Only OpenBSD sources -- Wolfram Schneider http://freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 08:32:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26515 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 08:32:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26510 for ; Thu, 16 Jul 1998 08:32:27 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id RAA18804; Thu, 16 Jul 1998 17:32:13 +0200 (MET DST) Date: Thu, 16 Jul 1998 17:32:12 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Andreas Klemm cc: FreeBSD hackers mailing list Subject: Re: Confirmation for subscribe freebsd-hackers In-Reply-To: <19980716155638.50690@hightek.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 > > [...] > > Obfuscated majordomo subscriber contest 1998 ? FreeBSD Hackers 98: New version! More bugs and strange behaviour to be exposed! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 09:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02967 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 09:17:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA02962 for ; Thu, 16 Jul 1998 09:17:37 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Thu Jul 16 11:17 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id LAA01257 for ; Thu, 16 Jul 1998 11:17:16 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <37TTZAM1>; Thu, 16 Jul 1998 12:17:12 -0400 Message-ID: To: k@numeri.campus.luth.se, freebsd-hackers@FreeBSD.ORG Subject: RE: Special memory board on ISA bus Date: Thu, 16 Jul 1998 12:17:11 -0400 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: Johan Karlsson [SMTP:k@numeri.campus.luth.se] > > I have a special memory board on the ISA bus that responds to > addresses from > BOARD_BASE up to BOARD_BASE+BOARD_MASK. > Is it mapped in ISA hole under 1M or over it ? > Now I need to make sure that the memory manager in FreeBSD does not > use this > part of the memory address space. Is there an "easy" way to do this or > do I > have to rewrite init386 in /usr/src/sys/i386/i386/machdep.c to ensure > that it > will not use the board. > There exists such a thing as 1M address hole at 15M address, configured in BIOS (some BIOSes also have ability to configure 2M hole at 14M). The problem is that FreeBSD does not support it if you have over 16M of memory. You can add it to machdep.c, to the memory size probe routine and add one more entry to the array describing the physical memory. But there is a catch: the kernel is loaded over 1M, into the second contiguous piece of memory that is normally the biggest. But if you have 15M hole and 32M of memory, the third piece would be the biggest, and the VM initialization code is thinking that the kernel is in the biggest piece, not the second. That would be wrong and need to be fixed. > I also need to make sure that the cache is not used when I read/write > to my > board. To do this one can use the MTRR:s (Memory Type Range > Registers). > I guess, if you configure the memory hole in BIOS, it does all the necessary setups during bootstrapping and then you just use it in FreeBSD (and for range 640K-1M it's already preconfigured). -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 10:07:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11233 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 10:07:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nexus.astro.psu.edu (nexus.astro.psu.edu [128.118.147.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA11225 for ; Thu, 16 Jul 1998 10:07:52 -0700 (PDT) (envelope-from mph@astro.psu.edu) Received: from mstar.astro.psu.edu by nexus.astro.psu.edu (4.1/Nexus-1.3) id AA23581; Thu, 16 Jul 98 13:07:41 EDT Received: by mstar.astro.psu.edu (SMI-8.6/Client-1.3) id NAA10216; Thu, 16 Jul 1998 13:07:36 -0400 Message-Id: <19980716130736.B10063@mstar.astro.psu.edu> Date: Thu, 16 Jul 1998 13:07:36 -0400 From: Matthew Hunt To: CyberPsychotic , ben@rosengart.com Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. Mail-Followup-To: CyberPsychotic , ben@rosengart.com, Alfred Perlstein , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from CyberPsychotic on Thu, Jul 16, 1998 at 07:11:31PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 16, 1998 at 07:11:31PM +0300, CyberPsychotic wrote: > > World in this case refers to the whole system (/bin and /usr/bin but not > > /usr/local/bin, for example). > > so binaries, right? Not just the binaries. Also the manpages, everything in /usr/share, the libraries in /usr/lib, and various other things. One notable exception is that /etc is not touched at all. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 10:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12270 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 10:19:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12264 for ; Thu, 16 Jul 1998 10:19:03 -0700 (PDT) (envelope-from malte@webmore.com) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id KAA05873 for ; Thu, 16 Jul 1998 10:18:01 -0700 (PDT) Received: from neuron.webmore.com (unverified [194.95.214.161]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Thu, 16 Jul 1998 19:19:53 +0200 Received: (from malte@webmore.com) by neuron.webmore.com (8.8.8/8.8.8) id TAA00436; Thu, 16 Jul 1998 19:17:44 +0200 (CEST) Message-ID: X-Mailer: XFMail 1.2 [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: <199807160231.WAA00296@lakes.dignus.com> Date: Thu, 16 Jul 1998 19:17:38 +0200 (CEST) Reply-To: malte@webmore.com From: Malte Lance To: Thomas David Rivers Subject: RE: Mysterious reboots w/2.2.6-RELEASE. Cc: freebsd-hackers@freefall.cdrom.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jul-98 Thomas David Rivers wrote: > > You may recall that I reported a few crashes with the 2.2.6-RELEASE > and sent in tracebacks... but the kernel was not config'd -g so > there was little info in the tracebacks. ... > It seems that the machine is still mysteriously crashing, but now > I don't get anything in /var/crash. > > I just had the opportunity to see first-hand this happen; I was > working and suddenly - "poof" away things went. > > On the reboot - savecore issued the message "savecore: no core dump". > > That is; the machine apparently just rebooted - no panic or nothing... > > > Has anyone else experienced mysterious, non-panic reboots? Yes !!! > This is while in X, and didn't seem to happen with the 2.2.5-RELEASE. > Perhaps there's something in the X code (Matrox Millenium II card) > that's causing this spontaneous reboot... Yes exactly. Always in X and very often related to netscape. After playing around with the scsi-subsystem (termination, order of devices...) the crashes happend not as frequent but they still happend. Then i changed the PCI-SLOT-IRQ assignment for my graphics-card in BIOS from "Auto" to "NA". No crash so far (2 weeks). Malte. > > - Dave Rivers - > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------- E-Mail: Malte Lance Date: 16-Jul-98 Time: 16:23:27 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 10:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17913 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 10:58:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17908 for ; Thu, 16 Jul 1998 10:58:23 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA24154; Thu, 16 Jul 1998 13:54:07 -0400 (EDT) Date: Thu, 16 Jul 1998 13:54:03 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: CyberPsychotic cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 16 Jul 1998, CyberPsychotic wrote: > > > binaries? Some other environment? > > > > World in this case refers to the whole system (/bin and /usr/bin but not > > /usr/local/bin, for example). > > so binaries, right? And documentation, yes. Changed to /etc are made in /usr/src/etc and have to be brought over by hand. > so I will need to get whole three at > ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/* and then put it into my > /usr/src instead of current stuff? And then I am ready to recompile all > the biaries world here, right? By the way can I find all the > kernel stuff precompressed somewhere? because I use proxy, and whenever it > fetches things, the compression on the fly hardly work. Cvsup will be much faster than ftp, since it only transfers diffs, not the whole files involved, and files that haven't changed won't be transferred. I usually install it by doing cd /usr/ports/net/cvsup make install clean Then you run cvsup with one of the files in /usr/share/examples/cvsup/, for you it would be stable-supfile. You might want to copy it and tweak it first. Cvsup knows how to work with proxies; I've never had to do it, but take a look at the man page for the appropriate arguments. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 11:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20675 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 11:17:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20664 for ; Thu, 16 Jul 1998 11:17:55 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA29416; Thu, 16 Jul 1998 11:03:27 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029406; Thu Jul 16 18:03:19 1998 Message-ID: <35AE4062.ABD322C@whistle.com> Date: Thu, 16 Jul 1998 11:03:14 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: "Micro.Softs &" CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Please, help me ...... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Micro.Softs & wrote: > > Hello . > I had a problem with kernel. > Version FreeBSD 2.1.7 It gives out the following messages after compilation. > ----------------- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1. > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 62 (routed) > interrupt mask = > kernel: type 12 trap, code = 0 > ------------------- > > What you to me will advise? > Is beforehand grateful. > > Rinat > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message I vaguely remember this bug.. it was due to routed using the wrong data on the default route and the kernel actualyy trusting it.. both bugs were fixed in later versions.. I would suggest that an upgrade to 2.2.6 (or 2.2.7 when it comes out) might be a good investment. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 13:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08159 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 13:22:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08153 for ; Thu, 16 Jul 1998 13:22:06 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA03930; Thu, 16 Jul 1998 13:21:14 -0700 (PDT) Message-Id: <199807162021.NAA03930@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: HAMADA Naoki cc: smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "Wed, 15 Jul 1998 15:47:29 +0900." <199807150647.PAA25283@stone.astec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Jul 1998 13:21:14 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If anyone has the chance to test this under -stable in the next few days, please do so, as it'd be nice to have it in 2.2.7. > smoergrd@oslo.geco-prakla.slb.com writes: > >Believe me, it still sucks. Search the archives (both the mailing list > >archives and the PR database) for "no buffer space", and/or "ep0". > >Basically, the driver is fine for telnet and mail, but wedges under > >sustained load. I can get it to hang without ever going above 20 kBps > >(160 kbps). Gimme an Intel EtherExpress. > > I carefully looked through the source code to find a bug which results > mbuf leaks. Could you try this patch? > > -nao > > --- sys/i386/isa/if_ep.c- Wed Jul 15 15:40:09 1998 > +++ sys/i386/isa/if_ep.c Wed Jul 15 15:41:04 1998 > @@ -1128,8 +1128,7 @@ > /* we see if by now, the packet has completly arrived */ > goto read_again; > } > - outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | RX_NEXT_EARLY_THRESH); > - return; > + goto out; > } > outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); > ++ifp->if_ipackets; > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 16 14:13:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16143 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 14:13:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ilium.troy.msen.com (ilium.troy.msen.com [148.59.4.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA16133 for ; Thu, 16 Jul 1998 14:13:35 -0700 (PDT) (envelope-from wayne@ilium.troy.msen.com) Received: by ilium.troy.msen.com (Smail3.1.28.1 #1) id m0ywvKM-0003cUC; Thu, 16 Jul 98 17:12 EDT Message-Id: To: Shawn Holwegner , freebsd-hackers@FreeBSD.ORG Subject: Re: Tyan Tomcat DMA and IRQ woes. In-reply-to: Your message of Tue, 14 Jul 98 17:31:30 PDT. From: "Michael R. Wayne" Date: Thu, 16 Jul 98 17:12:33 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +----------> + On Mon, 13 Jul 1998, Shawn Holwegner wrote: + > I have recently aquired a Tyan Tomcat II Dual Pent. MB. Looks nice, + > wish I could say it works the same: I am having no end to troubles with +----------> We have learned from bitter experience that Tyan Pentium boards do not function properly if you have more than 128MB of RAM in them. Tyan refuses to address the problem so we switched to Supermicro. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 19:09:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05413 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 19:09:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05408 for ; Thu, 16 Jul 1998 19:09:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id TAA26414 for ; Thu, 16 Jul 1998 19:08:50 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 16 Jul 1998 19:08:49 -0700 (PDT) From: Doug White To: hackers@FreeBSD.ORG Subject: NetBSD now has USB .. 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 FreeBSD next? Someone want to take on a porting project? (and don't say me, I don't have time or the technical expertice.) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 19:10:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05803 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 19:10:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.lrb.lapan.go.id (root@mail.lrb.lapan.go.id [202.46.11.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05796 for ; Thu, 16 Jul 1998 19:10:34 -0700 (PDT) (envelope-from 95150166@alice.mhs.bl.ac.id) Received: from radio.bl.ac.id (radio.bl.ac.id [141.103.129.5]) by mail.lrb.lapan.go.id (8.8.4/8.8.4) with SMTP id IAA03128 for ; Fri, 17 Jul 1998 08:06:16 GMT Received: from java.miti.bl.ac.id by radio.bl.ac.id (JNOS1.10a) with SMTP id AA8545 ; Fri, 17 Jul 98 09:14:01 UTC Received: from alice.mhs.bl.ac.id (alice.mhs.bl.ac.id [141.118.100.11]) by java.miti.bl.ac.id (8.6.12/8.6.9) with ESMTP id JAA03289 for ; Fri, 17 Jul 1998 09:04:46 +0700 Received: from MHS/SpoolDir by alice.mhs.bl.ac.id (Mercury 1.21); 17 Jul 98 09:08:25 +0700 Received: from SpoolDir by MHS (Mercury 1.21); 17 Jul 98 09:08:18 +0700 From: "Blueprints" <95150166@alice.mhs.bl.ac.id> Organization: Lab. MI/TI STMIK Budi Luhur To: hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 09:08:12 GMT +0700 Subject: I want to become a netters Reply-to: 95150166%alice.mhs.bl.ac.id@mail.lrb.lapan.go.id X-mailer: Pegasus Mail v3.22 Message-ID: <1779AB43191@alice.mhs.bl.ac.id> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 19:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08012 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 19:39:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08006 for ; Thu, 16 Jul 1998 19:39:43 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id WAA01174; Thu, 16 Jul 1998 22:39:45 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Thu, 16 Jul 1998 22:39:45 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG are you tracking -current? chip3: rev 0x01 int d irq 11 on pci0.7.2 :) (unless you mean actuall devices supported or something) -Alfred On Thu, 16 Jul 1998, Doug White wrote: > ... Is FreeBSD next? > > Someone want to take on a porting project? (and don't say me, I don't > have time or the technical expertice.) > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > 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 16 19:48:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08927 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 19:48:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08922 for ; Thu, 16 Jul 1998 19:48:43 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id WAA08091; Thu, 16 Jul 1998 22:48:15 -0400 (EDT) Date: Thu, 16 Jul 1998 22:48:15 -0400 (EDT) From: The Hermit Hacker To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. 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, 16 Jul 1998, Doug White wrote: > ... Is FreeBSD next? > > Someone want to take on a porting project? (and don't say me, I don't > have time or the technical expertice.) Hate to ask, but what is USB, and where can I learn more about it, and the NetBSD aspect of it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 20:32:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12411 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 20:32:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12405 for ; Thu, 16 Jul 1998 20:32:28 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id UAA19422; Thu, 16 Jul 1998 20:16:50 -0700 (PDT) Message-Id: <199807170316.UAA19422@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Alfred Perlstein Cc: Doug White , hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 16 Jul 1998 20:16:49 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 22:39:45 -0500 (EST) Alfred Perlstein wrote: > are you tracking -current? > > chip3: rev 0x01 int d irq 11 on > pci0.7.2 > > :) > > (unless you mean actuall devices supported or something) Yes, NetBSD actually supports devices, like USB mice, keyboards, printers, hubs, etc. USB audio support is in progress. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 20:38:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12848 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 20:38:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12843 for ; Thu, 16 Jul 1998 20:38:22 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id UAA19443; Thu, 16 Jul 1998 20:23:03 -0700 (PDT) Message-Id: <199807170323.UAA19443@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: The Hermit Hacker Cc: Doug White , hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 16 Jul 1998 20:23:02 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 22:48:15 -0400 (EDT) The Hermit Hacker wrote: > Hate to ask, but what is USB, and where can I learn more about it, and the > NetBSD aspect of it? Universal Serial Bus. "Those funny connectors on new PC motherboards." USB will eventually replace all of that PS/2 gunk, and will be a standard way of connecting (and chaining) input and output devices. USB spec: http://www.teleport.com/cgi-bin/mailmerge.cgi/~usb/cgiform.tpl There exist already USB mice, keyboards, printers, speakers, RS-232 interfaces, cameras, etc. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 16 21:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18855 for freebsd-hackers-outgoing; Thu, 16 Jul 1998 21:59:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.lrb.lapan.go.id (root@mail.lrb.lapan.go.id [202.46.11.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18847 for ; Thu, 16 Jul 1998 21:59:17 -0700 (PDT) (envelope-from 95150166@alice.mhs.bl.ac.id) Received: from radio.bl.ac.id (radio.bl.ac.id [141.103.129.5]) by mail.lrb.lapan.go.id (8.8.4/8.8.4) with SMTP id KAA05038 for ; Fri, 17 Jul 1998 10:43:19 GMT Received: from java.miti.bl.ac.id by radio.bl.ac.id (JNOS1.10a) with SMTP id AA8635 ; Fri, 17 Jul 98 11:12:13 UTC Received: from alice.mhs.bl.ac.id (alice.mhs.bl.ac.id [141.118.100.11]) by java.miti.bl.ac.id (8.6.12/8.6.9) with ESMTP id LAA03526 for ; Fri, 17 Jul 1998 11:01:57 +0700 Received: from MHS/SpoolDir by alice.mhs.bl.ac.id (Mercury 1.21); 17 Jul 98 11:05:37 +0700 Received: from SpoolDir by MHS (Mercury 1.21); 17 Jul 98 11:05:27 +0700 From: "Blueprints" <95150166@alice.mhs.bl.ac.id> Organization: Lab. MI/TI STMIK Budi Luhur To: freebsd-hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 11:05:19 GMT +0700 Subject: Reply-to: 95150166%alice.mhs.bl.ac.id@mail.lrb.lapan.g X-mailer: Pegasus Mail v3.22 Message-ID: <1798EA011EA@alice.mhs.bl.ac.id> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 00:43:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01236 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 00:43:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01231 for ; Fri, 17 Jul 1998 00:43:49 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA12754; Fri, 17 Jul 1998 09:43:32 +0200 (MET DST) Date: Fri, 17 Jul 1998 09:43:30 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. 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 > ... Is FreeBSD next? > > Someone want to take on a porting project? (and don't say me, I don't > have time or the technical expertice.) Little update on that one: Support for USB is being developed for Linux, NetBSD and FreeBSD. There is a separate effort, done by several companies, and lead by DEC to create a Universal Interface to it, a so-called USBDI. Lennart Augustsson is doing the work for NetBSD and I was supposed to the implementation for FreeBSD. I have a stack that does something, but couldn't yet be bothered to have a look at the USBDI. Lennart is much further in that he is able to run a number of different devices off it, with control, interrupt, bulk AND isochroneous transfers. He is at the moment rewriting his code, because he did not like the looks of it. Linux is a separate effort due to licensing (GNU) and done by Inaky Perez Gonzalez. At the moment, my implementation has stopped completely due to lack of time. It is however intended to either port Lennart's source or build my own stack (of which the lower parts, UHCI/HC virtual hub, have already been implemented) within the next few weeks. I'm supposed to be the point of contact for the FreBSD implementation, so if you want do anything or want more information, just let me know. Links to information on USB: http://www.usb.org http://www.etla.net/~n_hibma/usb/usb.pl Ciao, Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 01:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02939 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 01:06:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02934 for ; Fri, 17 Jul 1998 01:06:29 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA04592 ; Fri, 17 Jul 1998 10:01:10 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA19766; Fri, 17 Jul 1998 10:01:09 +0200 To: Mike Smith Cc: HAMADA Naoki , sbabkin@dcn.att.com, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: <199807162021.NAA03930@antipodes.cdrom.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 17 Jul 1998 10:01:09 +0200 In-Reply-To: Mike Smith's message of Thu, 16 Jul 1998 13:21:14 -0700 Message-ID: Lines: 31 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > If anyone has the chance to test this under -stable in the next few > days, please do so, as it'd be nice to have it in 2.2.7. Well, I don't have a -stable box right now, but from preliminary testing on my -current boxes, I'd recommend against it. I haven't had much time to track down the problem, but it would seem that a certain percentage of incoming packets go down a black hole. > > I carefully looked through the source code to find a bug which results > > mbuf leaks. Could you try this patch? > > > > -nao > > > > --- sys/i386/isa/if_ep.c- Wed Jul 15 15:40:09 1998 > > +++ sys/i386/isa/if_ep.c Wed Jul 15 15:41:04 1998 > > @@ -1128,8 +1128,7 @@ > > /* we see if by now, the packet has completly arrived */ > > goto read_again; > > } > > - outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | RX_NEXT_EARLY_THRESH); > > - return; > > + goto out; > > } > > outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); > > ++ifp->if_ipackets; > > DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.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 17 01:36:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05764 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 01:36:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05756; Fri, 17 Jul 1998 01:36:25 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA06058 ; Fri, 17 Jul 1998 10:35:42 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA19776; Fri, 17 Jul 1998 10:35:41 +0200 To: Andreas Klemm Cc: Majordomo@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Confirmation for subscribe freebsd-hackers References: <199807160834.BAA09012@hub.freebsd.org> <19980716155638.50690@hightek.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 17 Jul 1998 10:35:41 +0200 In-Reply-To: Andreas Klemm's message of Thu, 16 Jul 1998 15:56:38 +0200 Message-ID: Lines: 28 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm writes: > On Thu, Jul 16, 1998 at 01:34:07AM -0700, Majordomo@freebsd.org wrote: > > [...] > > If you really want this action to be taken, please send the following > > commands (exactly as shown) back to "Majordomo@FreeBSD.ORG": > > > > auth e659031c subscribe freebsd-hackers freebsd-hackers@freebsd.org > > [...] > > Obfuscated majordomo subscriber contest 1998 ? No, it's simply what happens if someone believes they can list several list names in a single subscribe command, e.g.: subscribe freebsd-hackers freebsd-chat Majordomo understands this as "Please subscribe freebsd-chat to freebsd-hackers" and sends an authentication request to freebsd-chat. In Ye Good Olde Days, before X-Loop and authentication, it would just obey with no questions asked, and everything on -hackers would be echoed to -chat. The really fun thing to do is to subscribe a list to itself, and watch the mail server climb the wall. Doesn't work anymore though, because Majordomo will reject mail with "X-Loop: FreeBSD.ORG" in the headers. Kinda takes the spice out of life, doesn't it? DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.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 17 01:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06228 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 01:38:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cullinan.bistbn.com (cullinan.bistbn.com [209.88.174.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06223 for ; Fri, 17 Jul 1998 01:38:52 -0700 (PDT) (envelope-from yury@bistbn.com) Received: from yuryk (yuryk.bistbn.com [209.88.174.51]) by cullinan.bistbn.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id PBQTF47S; Fri, 17 Jul 1998 11:38:48 +0300 From: "Yuri Krichevsky" To: Subject: RE: cvs commit: src/sys/pci if_tl.c if_tlreg.h Date: Fri, 17 Jul 1998 11:38:38 +0300 Message-ID: <000401bdb15e$4b3ca630$33ae58d1@yuryk.bistbn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199807131815.LAA08937@freefall.freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG BTW, Will we see this driver in 2.2.7-RELEASE ? It will be very appriciated... > wpaul 1998/07/13 11:15:49 PDT > > Modified files: > sys/pci if_tl.c if_tlreg.h > Log: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 01:42:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06741 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 01:42:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06736 for ; Fri, 17 Jul 1998 01:42:25 -0700 (PDT) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id RAA01554; Fri, 17 Jul 1998 17:41:46 +0900 (JST) Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.26.2]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id RAA23648; Fri, 17 Jul 1998 17:41:46 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id RAA01128; Fri, 17 Jul 1998 17:41:44 +0900 (JST) Date: Fri, 17 Jul 1998 17:41:44 +0900 (JST) Message-Id: <199807170841.RAA01128@stone.astec.co.jp> From: HAMADA Naoki References: <199807162021.NAA03930@antipodes.cdrom.com> To: smoergrd@oslo.geco-prakla.slb.com CC: mike@smith.net.au, hamada@astec.co.jp, sbabkin@dcn.att.com, hackers@FreeBSD.ORG In-reply-to: Dag-Erling Coidan Sm,Ax(Brgrav's message of "17 Jul 1998 10:01:09 +0200" Subject: Re: NIC drivers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Sm,Ax(Brgrav writes: >Well, I don't have a -stable box right now, but from preliminary >testing on my -current boxes, I'd recommend against it. I haven't had >much time to track down the problem, but it would seem that a certain >percentage of incoming packets go down a black hole. Are the purged packets sane? If that is the case, the top packet should not be discarded when an ERR_RX_INCOMPLETE is reported. In my environment, an ERR_RX_INCOMPLETE is so rare that I cannot make sure... - nao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 03:29:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14527 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 03:29:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14521 for ; Fri, 17 Jul 1998 03:29:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA15119; Fri, 17 Jul 1998 03:28:22 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Yuri Krichevsky" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci if_tl.c if_tlreg.h In-reply-to: Your message of "Fri, 17 Jul 1998 11:38:38 +0300." <000401bdb15e$4b3ca630$33ae58d1@yuryk.bistbn.com> Date: Fri, 17 Jul 1998 03:28:22 -0700 Message-ID: <15115.900671302@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure - it's nothing I personally can test. Anyone? - Jordan > > BTW, Will we see this driver in 2.2.7-RELEASE ? > It will be very appriciated... > > > > wpaul 1998/07/13 11:15:49 PDT > > > > Modified files: > > sys/pci if_tl.c if_tlreg.h > > Log: > > > 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 17 05:51:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26312 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 05:51:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA26281 for ; Fri, 17 Jul 1998 05:51:12 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id IAA06263 for hackers@freebsd.org; Fri, 17 Jul 1998 08:54:16 -0400 From: Bill Paul Message-Id: <199807171254.IAA06263@skynet.ctr.columbia.edu> Subject: Obtaining 3Com programming documentation To: hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 08:54:14 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody know the right place/person from which to obtain programming documentation for 3Com ethernet chips? We recently received two Dell GX1 systems as donations from Intel as part of a testbed system that some people in the EE department will be using in cooperation with a researcher from Intel. The systems actually have the Dell markings replaced with big 'Donated by Intel' signs but you can still tell they're Dells. Anyway, the machines have integrated 3Com 3c905B 'Cyclone' chips in them which, of course, don't work right in FreeBSD. My experiments so far indicate that the problem is that the first time a packet is received, the chip generates an interrupt flood. After the interrupt routine is invoked, there's a function that's supposed to remove the received frame from the chip: this function is supposed to read a status register from the window 1 register set so that it can learn the size of the packet, but the value read is always 0. This means the packet is never taken off the chip and the chip keeps interrupting forever, which wedges the system pretty tightly. I have the source for a Linux driver which claims to support this chip, but an actual programming manual would be better. Of course, 3Com doesn't seem to have any such info on their web servers. Any other driver programmers know the right trees to shake at 3Com? I really need to get this stupid thing working to make the Intel guy happy (to say nothing of certain Columbia EE faculty). -Bill PS: These systems also came with Adaptec 2940 U/UW controllers with the 7895 chip. This forced me to download the CAM snapshot in order to even get the machines running. The CAM stuff seems to work fine so far, though at the moment we only have the one SCSI disk attached. Please tell me there will be driver support for these bastiches in FreeBSD 3.0-RELEASE. PPS: Amusingly, whoever assembled the systems at Dell used the wrong pre-loaded LoseNT 4.0 disk image which did not have the correct driver loaded to support this controller: the machines blue-screened immediately after we first turned the systems on, with the Intel researcher looking on. I got a good laugh. Well, for a little while. Then I had to re-load LoseNT. PPPS: This is the second time I've had to do FreeBSD development work as part of my job. (The first time was writing the ThunderLAN driver.) Maybe the world isn't so screwed up after all. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 06:51:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23395 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 06:51:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elcat-gtw1.bishkek.su (elcat-gw.Nursat.net [194.226.137.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23062 for ; Fri, 17 Jul 1998 06:50:58 -0700 (PDT) (envelope-from fygrave@krsu.edu.kg) Received: from nsv.bishkek.su (nsv.bishkek.su [193.125.229.1]) by elcat-gtw1.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id TAA06883 ;Fri, 17 Jul 1998 19:49:54 +0600 (KGST) Received: from freenet.bishkek.su (freenet.bishkek.su [193.125.230.1]) by nsv.bishkek.su (8.7.5.R.S/Relcom-2A) with ESMTP id TAA25501 ;Fri, 17 Jul 1998 19:49:38 +0600 (KGST) Received: from unslaved.freenet.bishkek.su (IDENT:fygrave@unslaved.freenet.bishkek.su [192.168.5.3]) by freenet.bishkek.su (8.9.0/8.9.0) with ESMTP id TAA20254; Fri, 17 Jul 1998 19:53:52 -0500 Received: from localhost (fygrave@localhost) by unslaved.freenet.bishkek.su (8.8.8/8.8.8) with SMTP id TAA12561; Fri, 17 Jul 1998 19:54:10 +0300 Date: Fri, 17 Jul 1998 19:54:10 +0300 (EET DST) From: CyberPsychotic X-Sender: fygrave@unslaved.freenet.bishkek.su To: ben@rosengart.com cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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 > > so binaries, right? > > And documentation, yes. Changed to /etc are made in /usr/src/etc and > have to be brought over by hand. Ah, I see. So things are more wide than in linux. in linux the most thing i do is upgrade kernel, and binaries, if i feel they produce bugs working with new kernel (but usually they don't) under BSD things are more dependent uppon each other. hmm.,.. thanks anyway, I guess now i see the whole picture. > > Cvsup will be much faster than ftp, since it only transfers diffs, not > the whole files involved, and files that haven't changed won't be > transferred. I usually install it by doing > cd /usr/ports/net/cvsup > make install clean yep.:) I just found out that i lack this binary, so I have to download by hand cvsup archives (together with modula libs.,. hmm, why would it want modula anyway?) > Then you run cvsup with one of the files in /usr/share/examples/cvsup/, > for you it would be stable-supfile. and this file tells cvsup what to download, right? > You might want to copy it and tweak > it first. > > Cvsup knows how to work with proxies; I've never had to do it, but take > a look at the man page for the appropriate arguments. > yeah. I guess I won't have problems tuning it here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 07:19:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27965 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 07:19:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27898 for ; Fri, 17 Jul 1998 07:19:45 -0700 (PDT) (envelope-from ziggy@wopr.inetu.net) Received: from localhost (ziggy@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id KAA20006; Fri, 17 Jul 1998 10:16:42 -0400 (EDT) Date: Fri, 17 Jul 1998 10:16:42 -0400 (EDT) From: Ryan Ziegler To: CyberPsychotic cc: ben@rosengart.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 17 Jul 1998, CyberPsychotic wrote: > > > > Cvsup will be much faster than ftp, since it only transfers diffs, not > > the whole files involved, and files that haven't changed won't be > > transferred. I usually install it by doing > > > cd /usr/ports/net/cvsup > > make install clean > > yep.:) I just found out that i lack this binary, so I have to download by > hand cvsup archives (together with modula libs.,. hmm, why would it want > modula anyway?) You probably want to use the cvsup package, which a precompiled version of the cvsup port. ftp.freebsd.org:/pub/FreeBSD/packages/net/cvsup-bin-15.2.tgz I have found the port impossible to compile properly. Question for the galley: Why isn't cvsup installed by default? -Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 07:56:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13420 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 07:56:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13297 for ; Fri, 17 Jul 1998 07:56:47 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA19801 ; Fri, 17 Jul 1998 16:54:53 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA19972; Fri, 17 Jul 1998 16:54:53 +0200 To: CyberPsychotic Cc: ben@rosengart.com, Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 17 Jul 1998 16:54:53 +0200 In-Reply-To: CyberPsychotic's message of Fri, 17 Jul 1998 19:54:10 +0300 (EET DST) Message-ID: Lines: 63 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CyberPsychotic writes: > > > so binaries, right? > > And documentation, yes. Changed to /etc are made in /usr/src/etc and > > have to be brought over by hand. > Ah, I see. So things are more wide than in linux. in linux the most thing > i do is upgrade kernel, and binaries, if i feel they produce bugs working > with new kernel (but usually they don't) under BSD things are more > dependent uppon each other. hmm.,.. thanks anyway, I guess now i see the > whole picture. I don't think things are "more dependent upon eachother"in FreeBSD than in Linux. If you feel like, you can rebuild exactly the binaries you want manually, e.g. for ls(1): # cd /usr/src/bin/ls # make ; make install But since FreeBSD, unlike Linux, is one large, integrated, centrally controlled project, we have a consistent source tree and tools to rebuild the entire tree in just a few commands. If you are jumping a large gap (e.g. 2.2.1 to 2.2.7) you should at the very least rebuild most of man section 8 (init(8), fsck(8), mount(8) etc), anything that access kernel structures, such as ps(1) and top(1) (which is now part of the base system rather than a port), config(8), and the LKMs. Don't expect everything to work just peachy unless you rebuild everything, though. > yep.:) I just found out that i lack this binary, so I have to download by > hand cvsup archives (together with modula libs.,. hmm, why would it want > modula anyway?) You don't. Just look for a package named "cvsup-bin" and install that. > > Then you run cvsup with one of the files in /usr/share/examples/cvsup/, > > for you it would be stable-supfile. > and this file tells cvsup what to download, right? Yes. It's not very difficult to read, once you understand that everything that is on a "*default" line can also be put on a collection line. For instance, instead of: *default tag=RELENG_2_2 src-all ports-all tag=. you can drop the *default line and just use src-all tag=RELENG_2_2 ports-all tag=. > > You might want to copy it and tweak > > it first. > > Cvsup knows how to work with proxies; I've never had to do it, but take > > a look at the man page for the appropriate arguments. > yeah. I guess I won't have problems tuning it here. John Polstra (IIRC) has written an excellent CVSup FAQ, though the URL escapes me at the moment. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.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 17 08:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19843 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 08:03:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from altos.rnd.runnet.ru (root@altos.rnd.runnet.ru [195.208.248.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19779 for ; Fri, 17 Jul 1998 08:03:48 -0700 (PDT) (envelope-from max@rsu.ru) Received: from localhost (max@localhost [127.0.0.1]) by altos.rnd.runnet.ru (8.8.8/8.8.8) with SMTP id TAA04831; Fri, 17 Jul 1998 19:05:48 +0400 (MSD) Date: Fri, 17 Jul 1998 19:05:48 +0400 (MSD) From: Maxim Bolotin X-Sender: max@altos.rnd.runnet.ru To: Mike Smith cc: hackers@FreeBSD.ORG Subject: cs89x0 driver in 2.2.7 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! What do you think about cs driver in 2.2.7 RELEASE, I can send you version with PNP tomorrow (18 june). But I think that this vesion is stable enough for RELEASE. I'm using it more than one year. Max. - Rostov State University Computer Center Rostov-on-Don, +7 (8632) 285794 or 357476 Russia, RUNNet, MAB1-RIPE max@rsu.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 08:11:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26425 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 08:11:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26413 for ; Fri, 17 Jul 1998 08:11:04 -0700 (PDT) (envelope-from tom@tomqnx.com) Received: from tomqnx.com by TomQNX.tomqnx.com with esmtp (Smail3.2 #1) id m0yxC9s-000826C; Fri, 17 Jul 1998 11:10:52 -0400 (EDT) Message-ID: <35AF697B.203ED7E4@tomqnx.com> Date: Fri, 17 Jul 1998 11:10:51 -0400 From: Tom Torrance at home X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: IB Linux Download page Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone succeeded in getting the InterBase SQL server to work under emulation? http://www.interbase.com/download/linux/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 08:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18809 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 08:37:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spiv.fnal.gov (spiv.fnal.gov [131.225.124.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18752 for ; Fri, 17 Jul 1998 08:37:38 -0700 (PDT) (envelope-from neswold@spiv.fnal.gov) Received: (from neswold@localhost) by spiv.fnal.gov (8.8.8/8.8.7) id KAA08916; Fri, 17 Jul 1998 10:38:23 -0500 (CDT) (envelope-from neswold) Message-ID: <19980717103823.53900@spiv.fnal.gov> Date: Fri, 17 Jul 1998 10:38:23 -0500 From: Rich Neswold To: Tom Torrance at home , hackers@FreeBSD.ORG Subject: Re: IB Linux Download page Reply-To: neswold@fnal.gov Mail-Followup-To: Tom Torrance at home , hackers@FreeBSD.ORG References: <35AF697B.203ED7E4@tomqnx.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=VS++wcV0S1rZb1Fb X-Mailer: Mutt 0.89i In-Reply-To: <35AF697B.203ED7E4@tomqnx.com>; from Tom Torrance at home on Fri, Jul 17, 1998 at 11:10:51AM -0400 X-Spambot-Food: abuse@localhost postmaster@localhost abuse@fbi.gov Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii On Fri, Jul 17, 1998 at 11:10:51AM -0400, Tom Torrance at home wrote: > Has anyone succeeded in getting the InterBase SQL server to work under > emulation? > > http://www.interbase.com/download/linux/index.html Nope. I didn't try because it's against the licensing agreement: You may install and use the Software or the foregoing components provided that (1) the Software is used only with the Red Hat Linux 4.2 operating system, ... -- Rich ------------------------------------------------------------------------ Richard Neswold, Accelerator Div./Controls Dept | neswold@fnal.gov Fermilab, PO Box 500, MS 347, Batavia, IL 60510 | voice (630) 840-3454 'finger neswold@aduxb.fnal.gov' for PGP key | fax (630) 840-3093 --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNa9v7tyo48HBVqoBAQGZXgP/b8ikkee0SgvugFaq4ZRWguY34Ul5Rlni N2B8V3rIFGXSUHReZOfs9js4mRo9QpTdR7jcY8g+RyJklAKteClTWoz1uxDp6DrR +XjtCm47PFnFVU/BlwZGq7Jc9Se6DeWUyStLHg9mE0xJodcRqdhdfZ/a0wg1Hyss nnzJF2SAL1U= =3yC2 -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 08:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20149 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 08:39:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20095 for ; Fri, 17 Jul 1998 08:39:05 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA08276; Fri, 17 Jul 1998 08:38:23 -0700 (PDT) Message-Id: <199807171538.IAA08276@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Maxim Bolotin cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: cs89x0 driver in 2.2.7 In-reply-to: Your message of "Fri, 17 Jul 1998 19:05:48 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Jul 1998 08:38:22 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > What do you think about cs driver in 2.2.7 RELEASE, I can send you > version with PNP tomorrow (18 june). But I think that this vesion is > stable enough for RELEASE. I'm using it more than one year. I'm thinking it would be an excellent idea. I was going to do just that, but if you have PnP ready, that's even better. Thanks! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 17 09:35:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09726 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 09:35:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from altos.rnd.runnet.ru (root@altos.rnd.runnet.ru [195.208.248.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09711 for ; Fri, 17 Jul 1998 09:35:22 -0700 (PDT) (envelope-from max@rsu.ru) Received: from localhost (max@localhost [127.0.0.1]) by altos.rnd.runnet.ru (8.8.8/8.8.8) with SMTP id UAA05665; Fri, 17 Jul 1998 20:38:04 +0400 (MSD) Date: Fri, 17 Jul 1998 20:38:04 +0400 (MSD) From: Maxim Bolotin X-Sender: max@altos.rnd.runnet.ru To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: cs89x0 driver in 2.2.7 In-Reply-To: <199807171538.IAA08276@antipodes.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 On Fri, 17 Jul 1998, Mike Smith wrote: > > Hi! > > > > What do you think about cs driver in 2.2.7 RELEASE, I can send you > > version with PNP tomorrow (18 june). But I think that this vesion is > > stable enough for RELEASE. I'm using it more than one year. > > I'm thinking it would be an excellent idea. I was going to do just > that, but if you have PnP ready, that's even better. > Not now, tomorrow, I have to incorpotate in current version of the driver. Now Here's 20:30, and I havn't access to my computer with cs8920 card. I'll do it tomorrow and send you ASAP. Regards, Max. > Thanks! > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > - Rostov State University Computer Center Rostov-on-Don, +7 (8632) 285794 or 357476 Russia, RUNNet, MAB1-RIPE max@rsu.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 10:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14175 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 10:05:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14170 for ; Fri, 17 Jul 1998 10:05:30 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id TAA22475; Fri, 17 Jul 1998 19:04:54 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 17 Jul 1998 19:04:53 +0200 (MET DST) Mime-Version: 1.0 To: HAMADA Naoki Cc: smoergrd@oslo.geco-prakla.slb.com, mike@smith.net.au, sbabkin@dcn.att.com, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: <199807162021.NAA03930@antipodes.cdrom.com> <199807170841.RAA01128@stone.astec.co.jp> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 17 Jul 1998 19:04:52 +0200 In-Reply-To: HAMADA Naoki's message of "Fri, 17 Jul 1998 17:41:44 +0900 (JST)" Message-ID: Lines: 52 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HAMADA Naoki writes: > Dag-Erling Sm,Ax(Brgrav writes: > > Well, I don't have a -stable box right now, but from preliminary > > testing on my -current boxes, I'd recommend against it. I haven't had > > much time to track down the problem, but it would seem that a certain > > percentage of incoming packets go down a black hole. > Are the purged packets sane? If that is the case, the top packet > should not be discarded when an ERR_RX_INCOMPLETE is reported. In my > environment, an ERR_RX_INCOMPLETE is so rare that I cannot make > sure... Scratch that, I think the packet loss is caused by something else. I'm only getting it on one of my computers, and it works no better without the patch. My setup is as follows: helen --- LPIP --- niobe --- Ether --- luna | PPP | Internet Needless to say, Niobe is set up as a gateway. Both Niobe and Luna have 3Com 3c509 NICs. Ssh from Helen or Niobe to Luna doesn't work reliably; 'ssh -v luna' stops with "Waiting for server public key"; once in a while, it gets all the way to "requesting shell" and hangs there. If I reboot Luna, it will work for some time after the reboot (5-10 minutes) then gradually stop working. Ssh between Luna and Niobe works just fine, 'ping -f luna' from Helen shows no packet loss. Luna is headless, so I can't experiment much with ssh from Luna to Niobe or Helen, but yesterday, when I had a monitor plugged in on Luna, I noticed NFS and NIS were very flaky; not entirely gone, but flaky. All three computers run -current, and all three had their world remade yesterday. The problem manifested itself with the first kernel I compiled with your patch, but since I cvsupped right before I applied that patch, it may have been caused by something else. I have had absolutely no network problems between Luna and Niobe (except for forgetting to ifconfig lo0 on Luna) since I installed Luna on saturday - in fact, I did a minimal installation from the February snapshot CD-ROM, then cvsupped the entire tree from Niobe and made world. Niobe and Luna have IP addresses 10.0.1.1 and 10.0.1.2 respectively; on the LPIP link, Niobe and Helen have IP addresses 10.0.2.1 and 10.0.2.3 respectively. Niobe also has an (unused) Accton 2107 with IP address 10.0.3.1. Netmask is 0xffffff00 on all interfaces. Niobe is NFS, NIS, CVSup, FTP and HTTP server, and HTTP proxy. Luna is NFS and NIS client. Helen, being a laptop, does not use NIS, but mounts the repository over NFS from Niobe (not that I ever use it on Helen). DES -- One two, one two, one two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 10:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14584 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 10:08:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14528 for ; Fri, 17 Jul 1998 10:08:01 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id JAA27844; Fri, 17 Jul 1998 09:35:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 17 Jul 1998 09:35:48 -0700 (PDT) From: Doug White To: Nick Hibma cc: hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. 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, 17 Jul 1998, Nick Hibma wrote: > > ... Is FreeBSD next? > > > > Someone want to take on a porting project? (and don't say me, I don't > > have time or the technical expertice.) > > Little update on that one: > > Support for USB is being developed for Linux, NetBSD and FreeBSD. There > is a separate effort, done by several companies, and lead by DEC to > create a Universal Interface to it, a so-called USBDI. I thought I was on it's mailing list; what's the address? I think they moved it and I missed the announcement. > At the moment, my implementation has stopped completely due to lack of > time. It is however intended to either port Lennart's source or build my > own stack (of which the lower parts, UHCI/HC virtual hub, have already > been implemented) within the next few weeks. Do you have this anywhere? I'm pretty bored in my lab of several FreeBSD machines and have wanted to do some driver programming. > I'm supposed to be the point of contact for the FreBSD implementation, > so if you want do anything or want more information, just let me know. Will do, thanks! Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 10:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19605 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 10:40:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19599 for ; Fri, 17 Jul 1998 10:40:25 -0700 (PDT) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id NAA02335; Fri, 17 Jul 1998 13:34:22 -0400 (EDT) Date: Fri, 17 Jul 1998 13:34:22 -0400 (EDT) From: Tim Vanderhoek To: Ryan Ziegler cc: CyberPsychotic , ben@rosengart.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 17 Jul 1998, Ryan Ziegler wrote: > You probably want to use the cvsup package, which a precompiled version of > the cvsup port. [...] > Question for the galley: Why isn't cvsup installed by default? For the same reason you can't compile it on a normal computer. It (well, modula-3), is big. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 11:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29102 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 11:48:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (vYQyeTciWrmrNz6bBKkeQQWx3n4J0GHH@heron.doc.ic.ac.uk [146.169.16.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29097 for ; Fri, 17 Jul 1998 11:48:11 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak67.doc.ic.ac.uk [146.169.33.67] ([fohDdN6IaPPKFUXSCEaQ6CiE5w/RJh/2]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0yxFXZ-0006LN-00; Fri, 17 Jul 1998 19:47:33 +0100 Received: from njs3 by oak67.doc.ic.ac.uk with local (Exim 1.62 #3) id 0yxFXY-0006IC-00; Fri, 17 Jul 1998 19:47:32 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 17 Jul 1998 19:47:32 +0100 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hackers@FreeBSD.ORG Subject: tags for snapshots? Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Currently there are no tags for snapshots, so it is impossible to cvsup to a snapshot (to the best of my knowledge), would it be possible to introduce this? I know I could probably get something similar using date= but I'd rather get all the files exactly as they were per the snapshot. Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 12:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05091 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 12:38:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05086 for ; Fri, 17 Jul 1998 12:38:48 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA02501 for freebsd-hackers@FreeBSD.ORG; Fri, 17 Jul 1998 21:37:42 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id JAA07048; Fri, 17 Jul 1998 09:48:36 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807170748.JAA07048@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG cc: seggers@semyam.dinoco.de Subject: Should IP over SLIP/PLIP work w/o loop device? Date: Fri, 17 Jul 1998 09:48:35 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I just tried to compile a small -current kernel (source is from early July) for my 386/33 (where I intend to test swapoff). While doing so I commented out the pseudo device loop by accident but kept sl and discovered it won't finish the kernel generation. sl is - besides lp - the only network interface I left in it. The problem is that it needs sys/net/if_loop.c - specifically simloop in there but that config didn't include in the generated Makefile. Should it - despite being a strange configuration - in theory compile? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 12:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08179 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 12:52:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2 (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08173 for ; Fri, 17 Jul 1998 12:52:45 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2 (SMI-8.6/8.6.9) with SMTP id PAA21986 for ; Fri, 17 Jul 1998 15:52:29 -0400 Date: Fri, 17 Jul 1998 15:52:29 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: copy-on-write flags 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 (1) Can anybody tell me the different usages of those copy-on-write flags: MAP_COPY_NEEDED (MAP_ENTRY_COPY_NEEDED), MAP_COPY_ON_WRITE (MAP_ENTRY_COW), and MAP_NOFAULT (MAN_ENTRY_NOFAULT)? (2) I guess the field is_main_map is never used (just like shared map). Is that correct? Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 12:53:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08312 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 12:53:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08297 for ; Fri, 17 Jul 1998 12:53:26 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id OAA17133; Fri, 17 Jul 1998 14:51:39 -0500 (CDT) Message-Id: <199807171951.OAA17133@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: Tyan Tomcat DMA and IRQ woes. To: "Michael R. Wayne" cc: Shawn Holwegner , freebsd-hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 14:51:38 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Data point only: I've run three Tyan Pentium Pro machines with 256 MB RAM for the past year. Although we are now using SuperMicro for new Pentium II machines, so I can't comment on Tyan Pentium II boards. Jacques Vidrine On 16 July 1998 at 17:12, "Michael R. Wayne" wrote: > > +----------> > + On Mon, 13 Jul 1998, Shawn Holwegner wrote: > + > I have recently aquired a Tyan Tomcat II Dual Pent. MB. Looks nice, > + > wish I could say it works the same: I am having no end to troubles with > +----------> > > We have learned from bitter experience that Tyan Pentium boards do not > function properly if you have more than 128MB of RAM in them. Tyan > refuses to address the problem so we switched to Supermicro. > > /\/\ \/\/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNa+rSjeRhT8JRySpAQHJXwP+NFthwZuXhJRXYOSOfKfb0/nWCNCt5NkF BcL5Oepegyf9StmdP2hdc28yvn23ZwpGmwteXnd41u6gehs7Z9ShKfUa0F5WH7xH eI/y12KPxo95Vnqx56+NM/RM6XC6iw0xFjO5uh3m+mHBjUFcOElx8g0hUQJsUCz9 uEpdJ+3IO08= =LGbH -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 13:02:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10443 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:02:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nexus.astro.psu.edu (nexus.astro.psu.edu [128.118.147.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA10426 for ; Fri, 17 Jul 1998 13:02:22 -0700 (PDT) (envelope-from mph@astro.psu.edu) Received: from mstar.astro.psu.edu by nexus.astro.psu.edu (4.1/Nexus-1.3) id AA01222; Fri, 17 Jul 98 16:02:14 EDT Received: by mstar.astro.psu.edu (SMI-8.6/Client-1.3) id QAA27643; Fri, 17 Jul 1998 16:02:10 -0400 Message-Id: <19980717160210.B27578@astro.psu.edu> Date: Fri, 17 Jul 1998 16:02:10 -0400 From: Matthew Hunt To: Niall Smart , freebsd-hackers@FreeBSD.ORG Subject: Re: tags for snapshots? Mail-Followup-To: Niall Smart , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Niall Smart on Fri, Jul 17, 1998 at 07:47:32PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 17, 1998 at 07:47:32PM +0100, Niall Smart wrote: > Currently there are no tags for snapshots, so it is impossible to cvsup > to a snapshot (to the best of my knowledge), would it be possible to > introduce this? I know I could probably get something similar using > date= but I'd rather get all the files exactly as they were per > the snapshot. I find the prospect of that much disk I/O that often to be fairly unpleasant... -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 13:02:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10522 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:02:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10509 for ; Fri, 17 Jul 1998 13:02:48 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA15427; Fri, 17 Jul 1998 13:02:00 -0700 (PDT) Message-Id: <199807172002.NAA15427@implode.root.com> To: "Jordan K. Hubbard" cc: "Yuri Krichevsky" , freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci if_tl.c if_tlreg.h In-reply-to: Your message of "Fri, 17 Jul 1998 03:28:22 PDT." <15115.900671302@time.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 17 Jul 1998 13:02:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm not sure - it's nothing I personally can test. Anyone? ... >> > sys/pci if_tl.c if_tlreg.h It will have to be ported to -stable first. There is no time to do this before the release. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 13:07:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11389 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:07:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11314 for ; Fri, 17 Jul 1998 13:07:12 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id QAA23917; Fri, 17 Jul 1998 16:05:11 -0400 (EDT) Date: Fri, 17 Jul 1998 16:05:11 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Edwin Culp cc: dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago In-Reply-To: <35AD5A92.78123D1B@webwizard.org.mx> 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 We've found that 4.5pr1 has a nasty tendancy to leak information about page visits to the Netscape servers -- that is, the "Smart Browsing" feature. If you so much as click the button up there to pull down the menu, the URL for the page you are currently visiting is sent to the Netscape web servers. At TIS, we're concerned as this could easily leak data about our internal server structure to Netscape. It also gives them a very large marketing advantage, etc. We are advising our users to turn it off, and are working on making our firewall block such requests. It seems like a neat feature for the un-privacy-concerned end user, but really has no place in our environment. The configuration menus seem a lot nice now, though. I'd like to see Netscape put a link to the FreeBSD version on their web page, not just a file on their ftp server. Linux, etc, are up on the web server, and I suspect that their being there raises there legitimacy in the eyes of the viewer -- the signficant lack of FreeBSD there is concerning. On Wed, 15 Jul 1998, Edwin Culp wrote: > Dmitry Kohmanyuk =?KOI8-R?B?5M3J1NLJyiDrz8jNwc7Ayw==?= wrote: > > > > there is no binary for freebsd, but this one works: > > > > > There is now :-) Hot out of the oven > > ftp://ftp.netscape.com/pub/communicator/4.5/4.5_PR1/english/unix/freebsd2/communicator-v45b1-export.x86-unknown-freebsd.tar.gz > If the url isn't right it's close :-) > ed > > > > (there are 3 linux packages...) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > Ahora > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 13:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14040 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:26:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from friends.socialnet.com (friends.socialnet.com [209.185.12.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14035 for ; Fri, 17 Jul 1998 13:26:45 -0700 (PDT) (envelope-from markc@socialnet.com) Received: from stimpy (host-237.relationships.com [207.82.50.237]) by friends.socialnet.com (8.8.8/8.8.7) with SMTP id NAA01849 for ; Fri, 17 Jul 1998 13:25:23 -0700 (PDT) (envelope-from markc@socialnet.com) Message-ID: <00b101bdb1c1$1d352ab0$ed3252cf@stimpy.intranet.relationships.com> From: "Mark Castillo" To: Subject: writing software for serial port based devices Date: Fri, 17 Jul 1998 13:26:00 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been interested in writing software that will dowload images from a serial port based digital camera. In particular the Epson PhotoPC. I'm a decent C programmer, but don't no where to start with on FreeBSD as far as programming serial port devices. Can someone please direct me to where the best resources for this is (source code that uses the serial port, etc.) ------------------------------------------------- Mark Castillo Systems Integration Engineer SocialNet, Inc. 650.691.0609 x229 ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 13:32:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15148 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:32:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15103 for ; Fri, 17 Jul 1998 13:32:08 -0700 (PDT) (envelope-from john@jfive.com) Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by snake.supranet.net (8.8.8/8.8.8) with SMTP id PAA19320 for ; Fri, 17 Jul 1998 15:31:43 -0500 (CDT) (envelope-from john@jfive.com) Date: Fri, 17 Jul 1998 15:31:43 -0500 (CDT) From: John Heyer X-Sender: john@snake.supranet.net To: freebsd-hackers@FreeBSD.ORG Subject: FS Questsion - UFS vs. ext2 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 a SyQuest drive with cartridges I intend to share between a Linux and FreeBSD box. My question is if I should "format" the cartridges with FreeBSD's UFS file system or Linux's Ext2, or more specifically what the performance difference is. I know that UFS is roughly 2x faster over MSDOS FAT, but am not sure about ext2. Linux supposedly supports UFS r/o, but I've had problems before (I believe the actually error messages was "I/O Error: Fu**ing Sun Blows Me") and I'd prefer ext2. I know FreeBSD has supported ext2 r/w for a while, but will I lose performance? Also, can I change permissions on the ext2 drive while it's mounted under FreeBSD? -- "Calling the Lilith Fair 'A Celebration of Women in Music' is like calling Burger King 'A Celebration of Food'." -- Deborah Wolfinsohn John "The Fisherman" Heyer - http://john.jfive.com The Bastard Boat - http://primus.jfive.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 17 13:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15847 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 13:35:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from slarti.muc.de (slarti.muc.de [193.174.4.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA15832 for ; Fri, 17 Jul 1998 13:34:58 -0700 (PDT) (envelope-from eilts@tor.muc.de) Received: (qmail 7600 invoked by uid 66); 17 Jul 1998 20:34:09 -0000 Received: (from eilts@localhost) by tor.muc.de (8.8.7/8.6.6) id WAA27538; Fri, 17 Jul 1998 22:40:36 +0200 (CEST) Date: Fri, 17 Jul 1998 22:40:36 +0200 (CEST) From: Hinrich Eilts Message-Id: <199807172040.WAA27538@tor.muc.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: IPX over IP tunneling X-Newsreader: NN version 6.5.0 CURRENT #11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyone say me how IPX over IP tunneling can be implementing? > I need connect two IPX networks over IP network. > Still find nothing about it... You may try "IPXtund", located at sunsite.unc.edu /pub/Linux/system/network/daemons/ipxtund-1.2.0.tgz Bye Hinrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 14:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25020 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 14:21:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25009 for ; Fri, 17 Jul 1998 14:21:18 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id QAA16499 for ; Fri, 17 Jul 1998 16:20:36 -0500 (CDT) Message-Id: <199807172120.QAA16499@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: DigiBoard PC IMAC To: freebsd-hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 16:20:36 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi, Cleaning my closet, I came across a DigiBoard PC IMAC card. This is an ISA ISDN adapter, and is the predecessor to the DataFire. I think the difference was merely that the DataFire has a built-in NT1. The PC IMAC has been discontinued, but Digi (name changed) still sells the DataFire. I suppose this board might be useful for driver development. Does anybody care? Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNa/AIzeRhT8JRySpAQF8JQQArOWYryOohwHY5q8Yl+gNzGo88CBH1NnB 3EUslFpg3H1s5ZTpvFlh0CBIvLk79RhBO1jJZL5o4H5cPXiMOCiOeJvmUBp/OZ/s lsMskqfRvJwcLzxLjZ/Hq3/gIRFx3oani5AyGTbwkkgEBNEbINnoUJNg/6Kxt7/K a5WX8LeDADY= =+fL0 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 14:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28528 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 14:37:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from chen.ml.org (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28517 for ; Fri, 17 Jul 1998 14:37:40 -0700 (PDT) (envelope-from luoqi@chen.ml.org) Received: (from luoqi@localhost) by chen.ml.org (8.8.8/8.8.8) id RAA14378 for hackers@freebsd.org; Fri, 17 Jul 1998 17:37:28 -0400 (EDT) (envelope-from luoqi) Date: Fri, 17 Jul 1998 17:37:28 -0400 (EDT) From: Luoqi Chen Message-Id: <199807172137.RAA14378@chen.ml.org> To: hackers@FreeBSD.ORG Subject: Chinese locale data Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have submitted a set of patches for zh_CN.EUC locale via send-pr (misc/7310). Would some kind sole out there please helping me commit them? After that, we can proudly announce that FreeBSD now supports Chinese:) Thanks -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 14:39:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28970 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 14:39:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28961 for ; Fri, 17 Jul 1998 14:39:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA20409; Fri, 17 Jul 1998 14:38:06 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020393; Fri Jul 17 21:37:52 1998 Message-ID: <35AFC428.ABD322C@whistle.com> Date: Fri, 17 Jul 1998 14:37:44 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Stefan Eggers CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Should IP over SLIP/PLIP work w/o loop device? References: <199807170748.JAA07048@semyam.dinoco.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While theoretically the loop device is independent, it is in practice a needed component in an IP capabel kernel. The function simloop, in fact really should be removed from if_loop.c and placed in if.c. It's where it is for historical reasons. julian Stefan Eggers wrote: > > Hi! > > I just tried to compile a small -current kernel (source is from early > July) for my 386/33 (where I intend to test swapoff). While doing so > I commented out the pseudo device loop by accident but kept sl and > discovered it won't finish the kernel generation. sl is - besides lp > - the only network interface I left in it. > > The problem is that it needs sys/net/if_loop.c - specifically simloop > in there but that config didn't include in the generated Makefile. > Should it - despite being a strange configuration - in theory compile? > > Stefan. > -- > Stefan Eggers Lu4 yao2 zhi1 ma3 li4, > Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. > 51109 Koeln > Federal Republic of Germany > > 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 17 14:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00654 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 14:49:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00647 for ; Fri, 17 Jul 1998 14:49:14 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id RAA16177; Fri, 17 Jul 1998 17:47:36 -0400 (EDT) From: "Allen Smith" Message-Id: <9807171747.ZM16175@beatrice.rutgers.edu> Date: Fri, 17 Jul 1998 17:47:35 -0400 In-Reply-To: Robert Watson "Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago" (Jul 17, 4:05pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Robert Watson Subject: Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago Cc: freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 17, 4:05pm, Robert Watson (possibly) wrote: > > We've found that 4.5pr1 has a nasty tendancy to leak information about > page visits to the Netscape servers -- that is, the "Smart Browsing" > feature. If you so much as click the button up there to pull down the > menu, the URL for the page you are currently visiting is sent to the > Netscape web servers. At TIS, we're concerned as this could easily leak > data about our internal server structure to Netscape. It also gives them > a very large marketing advantage, etc. We are advising our users to turn > it off, and are working on making our firewall block such requests. > > It seems like a neat feature for the un-privacy-concerned end user, but > really has no place in our environment. Agreed. What HTTP header does it use? Thanks, -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 14:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02230 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 14:56:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02220 for ; Fri, 17 Jul 1998 14:56:39 -0700 (PDT) (envelope-from ziggy@wopr.inetu.net) Received: from localhost (ziggy@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id RAA24668; Fri, 17 Jul 1998 17:53:03 -0400 (EDT) Date: Fri, 17 Jul 1998 17:53:03 -0400 (EDT) From: Ryan Ziegler To: Tim Vanderhoek cc: CyberPsychotic , ben@rosengart.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. 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, 17 Jul 1998, Tim Vanderhoek wrote: > On Fri, 17 Jul 1998, Ryan Ziegler wrote: > > > You probably want to use the cvsup package, which a precompiled version of > > the cvsup port. > [...] > > Question for the galley: Why isn't cvsup installed by default? > > For the same reason you can't compile it on a normal computer. > It (well, modula-3), is big. cvsup-bin-15.2.tgz is a little over a meg. I'm not quite sure what modula-3 is used for in the port, but it's not included in the package. A line in /etc/crontab such as "uncomment to upgrade your ports once a week" would be nice. -Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 15:04:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03964 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 15:04:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (P8Z276+fhU9gWjElYITbwe+mdtu5VGk4@heron.doc.ic.ac.uk [146.169.16.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA03948 for ; Fri, 17 Jul 1998 15:04:29 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak67.doc.ic.ac.uk [146.169.33.67] ([p/kWAEKwUJ0HLkrid0RrDzs5qMhmBZcg]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0yxIbt-0006dP-00; Fri, 17 Jul 1998 23:04:13 +0100 Received: from njs3 by oak67.doc.ic.ac.uk with local (Exim 1.62 #3) id 0yxIbs-0006LN-00; Fri, 17 Jul 1998 23:04:12 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 17 Jul 1998 23:04:12 +0100 In-Reply-To: Matthew Hunt "Re: tags for snapshots?" (Jul 17, 4:02pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Matthew Hunt , Niall Smart , freebsd-hackers@FreeBSD.ORG Subject: Re: tags for snapshots? Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 17, 4:02pm, Matthew Hunt wrote: } Subject: Re: tags for snapshots? > > I find the prospect of that much disk I/O that often to be fairly > unpleasant... Eh? Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 15:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04302 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 15:05:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04273 for ; Fri, 17 Jul 1998 15:05:32 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id SAA16777; Fri, 17 Jul 1998 18:04:05 -0400 (EDT) From: "Allen Smith" Message-Id: <9807171804.ZM16775@beatrice.rutgers.edu> Date: Fri, 17 Jul 1998 18:04:04 -0400 In-Reply-To: Robert Watson "Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago" (Jul 17, 4:05pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Robert Watson Subject: Re: netscape communicator 4.5 preview 1 is released ~50 minutes ago Cc: freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops... sorry, I misinterpreted how it works. What _URLs_ is it requesting from Netscape? Thanks, -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 15:56:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09465 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 15:56:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09443 for ; Fri, 17 Jul 1998 15:56:27 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA00333; Fri, 17 Jul 1998 18:55:56 -0400 (EDT) Date: Fri, 17 Jul 1998 18:55:56 -0400 (EDT) From: "Matthew N. Dodd" To: David Greenman cc: "Jordan K. Hubbard" , Yuri Krichevsky , freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci if_tl.c if_tlreg.h In-Reply-To: <199807172002.NAA15427@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 Fri, 17 Jul 1998, David Greenman wrote: > >I'm not sure - it's nothing I personally can test. Anyone? > ... > >> > sys/pci if_tl.c if_tlreg.h > > It will have to be ported to -stable first. There is no time to do this > before the release. IIRC it was 'ported' to -current after being developed on -stable. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 17:01:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19983 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 17:01:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19974; Fri, 17 Jul 1998 17:01:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Date: Fri, 17 Jul 1998 17:01:29 -0700 (PDT) Message-Id: <199807180001.RAA19974@hub.freebsd.org> To: freebsd-hackers@FreeBSD.ORG From: Majordomo@FreeBSD.ORG Subject: Welcome to freebsd-hackers Reply-To: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Welcome to the freebsd-hackers mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to with the following command in the body of your email message: unsubscribe freebsd-hackers or from another account, besides freebsd-hackers@freebsd.org: unsubscribe freebsd-hackers freebsd-hackers@freebsd.org If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: FREEBSD-HACKERS Technical discussions This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 17:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20357 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 17:02:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20316 for ; Fri, 17 Jul 1998 17:02:31 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id SAA01382; Fri, 17 Jul 1998 18:59:13 -0500 (CDT) Message-Id: <199807172359.SAA01382@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: Kernel dies. To: Ryan Ziegler cc: Tim Vanderhoek , CyberPsychotic , ben@rosengart.com, freebsd-hackers@FreeBSD.ORG Date: Fri, 17 Jul 1998 18:59:13 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- It might be, except that there's no good way to upgrade a port. make deinstall && make install for each port leaves something to be desired. Hmm, do the ports get automatically built & installed on some FreeBSD.ORG machine periodically? How is that done? Or maybe it is part of make release? Jacques Vidrine On 17 July 1998 at 17:53, Ryan Ziegler wrote: [snip] > A line in /etc/crontab such as "uncomment to upgrade your ports once a > week" would be nice. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNa/lUTeRhT8JRySpAQHuLAQAtOoDiHsuNrp8w5wVaWpWjwrj9TY2oy0U cwnCW6jwHrS5jaaRcDlzHz1gN0pwnQFTMkvMRP2O39ZSidBwUzeQm8wUv7vZ6i6B eWm5zsu9lk3n/FVhld5/sNoLQBeKCb/dZCSkuZJJrkE97UjPMNsgmg7PwtAikA6b 2fckOCdcsuY= =zx7F -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 18:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28590 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 18:05:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28577 for ; Fri, 17 Jul 1998 18:04:59 -0700 (PDT) (envelope-from tim@localhost.my.domain) Received: from localhost.my.domain (ppp1583.on.bellglobal.com [206.172.249.47]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id VAA05969; Fri, 17 Jul 1998 21:00:17 -0400 (EDT) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id TAA29595; Fri, 17 Jul 1998 19:00:31 -0400 (EDT) (envelope-from tim) Message-ID: <19980717190030.A29560@zappo> Date: Fri, 17 Jul 1998 19:00:30 -0400 From: Tim Vanderhoek To: Ryan Ziegler Cc: CyberPsychotic , ben@rosengart.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Ryan Ziegler on Fri, Jul 17, 1998 at 05:53:03PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 17, 1998 at 05:53:03PM -0400, Ryan Ziegler wrote: > > cvsup-bin-15.2.tgz is a little over a meg. I'm not quite sure what > modula-3 is used for in the port, but it's not included in the package. > > A line in /etc/crontab such as "uncomment to upgrade your ports once a > week" would be nice. Wow! Only a meg (compressed). Let's add it! Heck, it's _way_ more useful than perl (compareable size), and everyone wanted that added! There's no reason such a comment can't be in /etc/crontab regardless. /etc/inetd.conf includes "uncomment me" examples for stuff in the ports system. PR your submission. :) -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 19:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07643 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 19:46:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA07637 for ; Fri, 17 Jul 1998 19:46:05 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id WAA07322; Fri, 17 Jul 1998 22:48:42 -0400 From: Bill Paul Message-Id: <199807180248.WAA07322@skynet.ctr.columbia.edu> Subject: Re: cvs commit: src/sys/pci if_tl.c if_tlreg.h To: winter@jurai.net (Matthew N. Dodd) Date: Fri, 17 Jul 1998 22:48:40 -0400 (EDT) Cc: dg@root.com, jkh@time.cdrom.com, yury@bistbn.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Matthew N. Dodd" at Jul 17, 98 06:55:56 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew N. Dodd had to walk into mine and say: > On Fri, 17 Jul 1998, David Greenman wrote: > > >I'm not sure - it's nothing I personally can test. Anyone? > > ... > > >> > sys/pci if_tl.c if_tlreg.h > > > > It will have to be ported to -stable first. There is no time to do this > > before the release. > > IIRC it was 'ported' to -current after being developed on -stable. I already have a 2.2.x version of the driver in /home/wpaul/tl/2.2 on freefall (grr... okay, for you web browsing types, I also put a copy at http://freebsd.org/~wpaul/thunderlan/2.2). The code is the same as the -current version except for 2.2/3.0 differences (i.e. PCI initialization and multicast handling). I've been keeping a 2.2 version synced with the changes I've been making in -current, but I've resisted putting the driver into the 2.2.x tree due a lack of feedback about the driver's stability. I know that it works for me on my original development machine, but I was hoping to get some more user reports before putting it in the 2.2 branch. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 21:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14612 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 21:26:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nexus.astro.psu.edu (nexus.astro.psu.edu [128.118.147.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA14560 for ; Fri, 17 Jul 1998 21:25:59 -0700 (PDT) (envelope-from mph@astro.psu.edu) Received: from mstar.astro.psu.edu by nexus.astro.psu.edu (4.1/Nexus-1.3) id AA02845; Sat, 18 Jul 98 00:25:50 EDT Received: by mstar.astro.psu.edu (SMI-8.6/Client-1.3) id AAA02190; Sat, 18 Jul 1998 00:25:46 -0400 Message-Id: <19980718002545.A2174@astro.psu.edu> Date: Sat, 18 Jul 1998 00:25:45 -0400 From: Matthew Hunt To: Niall Smart , freebsd-hackers@FreeBSD.ORG Subject: Re: tags for snapshots? Mail-Followup-To: Niall Smart , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Niall Smart on Fri, Jul 17, 1998 at 11:04:12PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 17, 1998 at 11:04:12PM +0100, Niall Smart wrote: > > I find the prospect of that much disk I/O that often to be fairly > > unpleasant... > > Eh? Putting down a tag requires that CVS modify (approximately) all of the files in the repository. Frequent tagging will cause a great deal of disk I/O on freefall, and likewise for everyone who maintains a copy of the repository. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 22:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19893 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 22:33:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from priscilla.mu.org (paul@priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19887 for ; Fri, 17 Jul 1998 22:33:27 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id AAA26554; Sat, 18 Jul 1998 00:32:59 -0500 (CDT) (envelope-from paul) Message-ID: <19980718003259.A26528@mu.org> Date: Sat, 18 Jul 1998 00:32:59 -0500 From: Paul Saab To: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Obtaining 3Com programming documentation References: <199807171254.IAA06263@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807171254.IAA06263@skynet.ctr.columbia.edu>; from Bill Paul on Fri, Jul 17, 1998 at 08:54:14AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there is a driver being written but we never hear anything about it. From what I understand about the 905 and the 905B is that the 905 has a programmed IO interface and the 905B had it removed. Paul Bill Paul (wpaul@skynet.ctr.columbia.edu) wrote: > Anybody know the right place/person from which to obtain programming > documentation for 3Com ethernet chips? We recently received two Dell > GX1 systems as donations from Intel as part of a testbed system that > some people in the EE department will be using in cooperation with a > researcher from Intel. The systems actually have the Dell markings > replaced with big 'Donated by Intel' signs but you can still tell they're > Dells. > > Anyway, the machines have integrated 3Com 3c905B 'Cyclone' chips in > them which, of course, don't work right in FreeBSD. My experiments so > far indicate that the problem is that the first time a packet is received, > the chip generates an interrupt flood. After the interrupt routine is > invoked, there's a function that's supposed to remove the received frame > from the chip: this function is supposed to read a status register from > the window 1 register set so that it can learn the size of the packet, > but the value read is always 0. This means the packet is never taken > off the chip and the chip keeps interrupting forever, which wedges the > system pretty tightly. > > I have the source for a Linux driver which claims to support this chip, > but an actual programming manual would be better. Of course, 3Com doesn't > seem to have any such info on their web servers. Any other driver > programmers know the right trees to shake at 3Com? I really need to get > this stupid thing working to make the Intel guy happy (to say nothing > of certain Columbia EE faculty). > > -Bill > > PS: These systems also came with Adaptec 2940 U/UW controllers with > the 7895 chip. This forced me to download the CAM snapshot in order > to even get the machines running. The CAM stuff seems to work fine > so far, though at the moment we only have the one SCSI disk attached. > Please tell me there will be driver support for these bastiches in > FreeBSD 3.0-RELEASE. > > PPS: Amusingly, whoever assembled the systems at Dell used the wrong > pre-loaded LoseNT 4.0 disk image which did not have the correct driver > loaded to support this controller: the machines blue-screened immediately > after we first turned the systems on, with the Intel researcher looking > on. I got a good laugh. Well, for a little while. Then I had to re-load > LoseNT. > > PPPS: This is the second time I've had to do FreeBSD development work as > part of my job. (The first time was writing the ThunderLAN driver.) Maybe > the world isn't so screwed up after all. > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================= > > 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 17 22:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21957 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 22:59:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21939; Fri, 17 Jul 1998 22:59:42 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id WAA07183; Fri, 17 Jul 1998 22:59:04 -0700 (PDT) Newsgroups: comp.unix.bsd.freebsd.misc Date: Fri, 17 Jul 1998 22:59:01 -0700 (PDT) From: Ian Kallen Reply-To: Ian Kallen To: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: rc can't fsck 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 migrated a machine that includes a big ass seagate drive from 2.2.5 to 2.2.6 and it won't fsck it at boot time! I can fsck it fine manually but check out rc croaking on fsck'ing it: (ahc0:5:0): "SEAGATE ST423451W 0013" type 0 fixed SCSI 2 sd2(ahc0:5:0): Direct-Access 22130MB (45322644 512 byte sectors) ... cannot alloc 5314561 bytes for typemap /dev/rsd2s1: CAN'T CHECK FILE SYSTEM. /dev/rsd2s1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Automatic file system check failed... help! Enter full pathname of shell or RETURN for /bin/sh: I can fsck it then (or control-d out of single-user) w/o any complaint. I modified login.conf like this to give rc the same limits as root: # Settings used by /etc/rc # daemon:\ :coredumpsize=infinity:\ :datasize=infinity:\ :maxproc=infinity:\ :memoryuse=infinity:\ :memorylocked=infinity:\ :openfiles=infinity:\ :stacksize=infinity:\ :tc=default: but no joy. I can hack up rc to skip fsck'ing it just to make it rebootable but, damn, I really don't want to do that. So um, what to do next? -Ian -- I play the harmonica. the only way I can play is if I get my car going really fast, and stick it out the window. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 17 23:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26011 for freebsd-hackers-outgoing; Fri, 17 Jul 1998 23:43:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26006 for ; Fri, 17 Jul 1998 23:43:40 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id CAA28530; Sat, 18 Jul 1998 02:43:22 -0400 (EDT) Date: Sat, 18 Jul 1998 02:43:22 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Ian Kallen cc: freebsd-hackers@FreeBSD.ORG Subject: Re: rc can't fsck 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 an older -stable machine I ran into the same problem with a 9G drive. Setting the "default" limits in login.conf fixed it. Why? I don't know... Charles Charles Sprickman spork@super-g.com ---- On Fri, 17 Jul 1998, Ian Kallen wrote: > > I migrated a machine that includes a big ass seagate drive from 2.2.5 to > 2.2.6 and it won't fsck it at boot time! I can fsck it fine manually but > check out rc croaking on fsck'ing it: > > (ahc0:5:0): "SEAGATE ST423451W 0013" type 0 fixed SCSI 2 > sd2(ahc0:5:0): Direct-Access 22130MB (45322644 512 byte sectors) > ... > cannot alloc 5314561 bytes for typemap > /dev/rsd2s1: CAN'T CHECK FILE SYSTEM. > /dev/rsd2s1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > Automatic file system check failed... help! > Enter full pathname of shell or RETURN for /bin/sh: > > I can fsck it then (or control-d out of single-user) w/o any complaint. I > modified login.conf like this to give rc the same limits as root: > > # Settings used by /etc/rc > # > daemon:\ > :coredumpsize=infinity:\ > :datasize=infinity:\ > :maxproc=infinity:\ > :memoryuse=infinity:\ > :memorylocked=infinity:\ > :openfiles=infinity:\ > :stacksize=infinity:\ > :tc=default: > > but no joy. I can hack up rc to skip fsck'ing it just to make it > rebootable but, damn, I really don't want to do that. So um, what to do > next? > -Ian > > -- > I play the harmonica. the only way I can play is if I get my car going > really fast, and stick it out the window. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" 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 18 00:30:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28970 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 00:30:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bleep.ishiboo.com (user20570@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA28962 for ; Sat, 18 Jul 1998 00:30:38 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 28737 invoked by uid 1000); 18 Jul 1998 07:30:23 -0000 Message-ID: <19980718033022.58777@bleep.ishiboo.com> Date: Sat, 18 Jul 1998 03:30:22 -0400 From: Danny Dulai To: Mark Castillo Cc: hackers@FreeBSD.ORG Subject: Re: writing software for serial port based devices References: <00b101bdb1c1$1d352ab0$ed3252cf@stimpy.intranet.relationships.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <00b101bdb1c1$1d352ab0$ed3252cf@stimpy.intranet.relationships.com>; from Mark Castillo on Fri, Jul 17, 1998 at 01:26:00PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Mark Castillo (markc@socialnet.com): > > I've been interested in writing software that will dowload images > from a serial port based digital camera. In particular the Epson PhotoPC. > I'm a decent C programmer, but don't no where to start with on FreeBSD > as far as programming serial port devices. Can someone please direct me > to where the best resources for this is (source code that uses the serial > port, etc.) http://dns.easysw.com/~mike/serial/ Thats an excellent tutorial on serial programming for POSIX compliant OSs. -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.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 18 02:44:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05851 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 02:44:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05844 for ; Sat, 18 Jul 1998 02:44:01 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA01142; Sat, 18 Jul 1998 02:43:34 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd001139; Sat Jul 18 02:43:34 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id CAA05959; Sat, 18 Jul 1998 02:43:31 -0700 (MST) From: Terry Lambert Message-Id: <199807180943.CAA05959@usr07.primenet.com> Subject: Re: tags for snapshots? To: mph@pobox.com (Matthew Hunt) Date: Sat, 18 Jul 1998 09:43:31 +0000 (GMT) Cc: njs3@doc.ic.ac.uk, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980718002545.A2174@astro.psu.edu> from "Matthew Hunt" at Jul 18, 98 00:25:45 am X-Mailer: ELM [version 2.4 PL25] 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 find the prospect of that much disk I/O that often to be fairly > > > unpleasant... > > > > Eh? > > Putting down a tag requires that CVS modify (approximately) all of > the files in the repository. Frequent tagging will cause a great > deal of disk I/O on freefall, and likewise for everyone who > maintains a copy of the repository. Seems to me that tags should be expresed in terms of dates; this presumes a write lock for the apllication of the tag... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 18 02:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06080 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 02:46:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06075 for ; Sat, 18 Jul 1998 02:46:13 -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.8.7/8.8.7) with ESMTP id JAA20403; Sat, 18 Jul 1998 09:45:56 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA10907; Sat, 18 Jul 1998 11:45:55 +0200 (MET DST) Message-ID: <19980718114554.40115@follo.net> Date: Sat, 18 Jul 1998 11:45:54 +0200 From: Eivind Eklund To: John Heyer , freebsd-hackers@FreeBSD.ORG Subject: Re: FS Questsion - UFS vs. ext2 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from John Heyer on Fri, Jul 17, 1998 at 03:31:43PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 17, 1998 at 03:31:43PM -0500, John Heyer wrote: > > I have a SyQuest drive with cartridges I intend to share between a Linux > and FreeBSD box. My question is if I should "format" the cartridges with > FreeBSD's UFS file system or Linux's Ext2, or more specifically what the > performance difference is. I know that UFS is roughly 2x faster over > MSDOS FAT, but am not sure about ext2. Linux supposedly supports UFS r/o, > but I've had problems before (I believe the actually error messages was > "I/O Error: Fu**ing Sun Blows Me") and I'd prefer ext2. I know FreeBSD has > supported ext2 r/w for a while, but will I lose performance? Also, can I > change permissions on the ext2 drive while it's mounted under FreeBSD? The ext2 support in FreeBSD won't use soft updates, so you'll loose that performance boost. Apart from that, I've heard ext2 looses more performance as the FS ages (which I can see some theoretical reasons for, too, but not enough that I'll claim it as truth until I've done measurements). The FFS and ext2 should be about the same speed initially, as long as you use the same block sizes. Due to (if I've understood correctly) missing fragment support in ext2, ext2 will probably be quite a bit less space-efficient than FFS. Also, I'm not certain of the stability of the -current ext2 support - I don't know if anybody use it. If you have problems with it, I believe it likely that they will be fixed, but I wouldn't bet too much on it being correct up front (I know I have fixed issues of it not compiling in a somewhat random fashion - I don't have an ext2fs to test on, so I've just fixed it by applying the suitable patches from FFS, in the convicition that it is better to have LINT compile than not, and it is 99% certain they are correct given that it is derived from the same codebase). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 18 06:41:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20802 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 06:41:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20797 for ; Sat, 18 Jul 1998 06:41:36 -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.8.7/8.8.7) with ESMTP id NAA29879 for ; Sat, 18 Jul 1998 13:41:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA11341; Sat, 18 Jul 1998 15:41:22 +0200 (MET DST) Message-ID: <19980718154122.53467@follo.net> Date: Sat, 18 Jul 1998 15:41:22 +0200 From: Eivind Eklund To: hackers@FreeBSD.ORG Subject: Weird bug strikes in _NPX_ when adding PnP support to i4b Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm slightly stuck here. I have done "draft code" (not nicely enough integrated, but should be correct) to add PnP support to i4b. This work fine for one card, but when I use two PnP cards, npx (of all weird things) crash here: * 16 works. */ printf("EE: npxprobe1 checks for exception 16\n"); control &= ~(1 << 2); /* enable divide by 0 trap */ fldcw(&control); npx_traps_while_probing = npx_intrs_while_probing = 0; printf("EE: npxprobe1 checks for divide by 0\n"); fp_divide_by_0(); if (npx_traps_while_probing != 0) { /* * Good, exception 16 works. */ printf("EE: exception 16 OK\n"); npx_ex16 = 1; The first two printfs get through, before the third the machine spontaneously reboot (and it sporadically reboot long before NPX, but I assume this is related to the same root cause). I don't have much of an i386-specific clue; I'd appreciate it if anybody have ideas of what could cause it. I'll probably track it down eventually, but would like to get it out of the world as fast as possible... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 18 13:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25989 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 13:44:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25974 for ; Sat, 18 Jul 1998 13:44:52 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA22651 for ; Sat, 18 Jul 1998 22:44:30 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sat, 18 Jul 1998 22:44:29 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Dump device with DEVFS? Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Jul 1998 22:44:28 +0200 Message-ID: Lines: 257 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to be impossible to enable a dump device with DEVFS. The following code in setdumpdev() in sys/i386/i386/autoconf.c is the culprit: if (dkpart(dev) != SWAP_PART) return (ENODEV); dkpart(dev) is #defined to (minor(dev) & 7) in disklabel.h, and SWAP_PART is #defined to 1 in the same file. Now MAKEDEV will assign minor numbers with the lower nybble 0x1 to swap partitions ([fosw]d?b or something like that) so it will work fine, but Helen's swap partition (/dev/wd0s1b) has minor number 11 (lower nybble 0x3), and Niobe's swap partition (/dev/sd0b) has minor number 20 (lower nybble 0x4), neither of which is acceptable to setdumpdev(). The only partition I have which is eligible as a dump device (due to its minor number being 25) is /dev/sd0h, aka. /usr/src. Am I missing something here? Is this a bug or a feature? How do I set a dump device on a DEVFS system? And anyway, shouldn't setdumpdev() just trust the user to know what he's doing even if the selected partition doesn't seem to be a swap partition? BTW, I just had a panic trying to umount an msdosfs floppy - probably thanks to soft updates, all my file systems except /var came up clean although I was cvsupping at the time of the panic. For completeness' sake, here is my dmesg, kernel config and a listing of /dev/sd*: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #9: Fri Jul 17 18:26:15 CEST 1998 finrod@niobe.ewox.org:/usr/src/sys/compile/niobe Timecounter "i8254" frequency 1193182 Hz cost 2278 ns Timecounter "TSC" frequency 166193751 Hz cost 137 ns CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) FreeBSD Kernel Configuration Utility - Version 1.1 Type "help" for help or "visual" to go to the visual configuration interface (requires MGA/VGA display or serial terminal capable of displaying ANSI graphics). config> quit avail memory = 127885312 (124888K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 de0: rev 0x22 int a irq 15 on pci0.9.0 de0: ACCTON EN1207 21140A [10-100Mb/s] pass 2.2 de0: address 00:00:e8:4a:83:63 de0: enabling 100baseTX port vga0: rev 0x70 int a irq 9 on pci0.10.0 ahc0: rev 0x00 int a irq 12 on pci0.11.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs scbus0 at ahc0 bus 0 sd0 at scbus0 target 2 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4341MB (8890760 512 byte sectors) sd0: with 5899 cyls, 10 heads, and an average 150 sectors/track ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers sd1 at scbus0 target 4 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 6180MB (12657717 512 byte sectors) sd1: with 7068 cyls, 8 heads, and an average 223 sectors/track ahc1: rev 0x00 int a irq 11 on pci0.12.0 ahc1: aic7870 Single Channel, SCSI Id=7, 16 SCBs scbus1 at ahc1 bus 0 st0 at scbus1 target 3 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x0, drive empty sd2 at scbus1 target 4 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 1030MB (2110812 512 byte sectors) sd2: with 3658 cyls, 6 heads, and an average 96 sectors/track cd0 at scbus1 target 5 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [258777 x 2048 byte records] od0 at scbus1 target 6 lun 0 od0: type 7 removable SCSI 2 od0: Optical 217MB (446325 512 byte sectors) od0: with approximate 217 cyls, 64 heads, and 32 sectors/track Probing for PnP devices: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> psm0 not found at 0x60 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:61:df:38 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround DEVFS: ready to run IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 256 packets/entry sd0: probing for MBR.. rejected.. Slice includes MBR sd0: probing for disklabel.. part a, start=0, size=131072 part b, start=131072, size=1048576 part d, start=3932160, size=4958600 part e, start=1179648, size=131072 part f, start=1310720, size=524288 part g, start=1835008, size=1048576 part h, start=2883584, size=1048576 sd1: probing for MBR.. rejected.. Slice includes MBR sd1: probing for disklabel.. part e, start=0, size=524288 part f, start=524288, size=1572864 part g, start=2097152, size=10560565 sd2: probing for MBR.. part 1, start=63, size=2104452 sd2s1: attaching disklabel.. part e, start=0, size=524288 part f, start=524288, size=1580164 fd0: probing for MBR.. WOULD SELECT /sd0a And it exists WARNING: / was not properly dismounted. fd0: Operation timeout fd0: hard error, block 0 (No status) ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated # # Kernel configuration for niobe.ewox.org # machine "i386" cpu "I586_CPU" ident niobe maxusers 64 # # Networking options INET options IPFIREWALL options IPFIREWALL_VERBOSE options "IPFIREWALL_VERBOSE_LIMIT=256" options "NMBCLUSTERS=4096" # # File system options DEVFS options FFS options FFS_ROOT # Boot from FFS options NFS options PROCFS options SLICE # Use devfs for devices options SOFTUPDATES # # XFree86 support options SYSVMSG options SYSVSEM options SYSVSHM options UCONSOLE # # Misc. kernel options options "AUTO_EOI_1" options "AUTO_EOI_2" options "COMPAT_43" options "MD5" options BOUNCE_BUFFERS options INCLUDE_CONFIG_FILE options USERCONFIG options USERCONFIG_BOOT options USER_LDT options VISUAL_USERCONFIG # config kernel root on sd0 # # Buses controller isa0 controller pci0 controller pnp0 # # Numeric processor extensions device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Floppy controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # # SCSI controllers controller ahc0 controller scbus0 device sd0 device od0 device st0 device cd0 pseudo-device su pseudo-device ssc options "SCSI_DELAY=1" options SCSI_REPORT_GEOMETRY # # System console and mouse device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options "MAXCONS=12" options "SC_HISTORY_SIZE=4096" options "MSGBUF_SIZE=32768" device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # # I/O ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr # # Network adapters device de0 device ep0 at isa? port 0x300 net irq 10 vector epintr # # Networking pseudo-devices pseudo-device loop pseudo-device ether pseudo-device tun 4 pseudo-device bpfilter 4 # # Other pseudo-devices pseudo-device gzip pseudo-device pty 64 pseudo-device vn 4 # # Sound hardware (Luigi Rizzo) device pcm0 at isa? port? tty irq 5 drq 1 flags 0x15 vector pcmintr # root@niobe # ll /dev/sd* brw------- 1 root operator 14, 8 Jul 18 21:56 /dev/sd0 brw------- 1 root operator 14, 19 Jul 18 21:56 /dev/sd0a brw------- 1 root operator 14, 20 Jul 18 21:56 /dev/sd0b brw------- 1 root operator 14, 21 Jul 18 21:56 /dev/sd0d brw------- 1 root operator 14, 22 Jul 18 21:56 /dev/sd0e brw------- 1 root operator 14, 23 Jul 18 21:56 /dev/sd0f brw------- 1 root operator 14, 24 Jul 18 21:56 /dev/sd0g brw------- 1 root operator 14, 25 Jul 18 21:56 /dev/sd0h brw------- 1 root operator 14, 9 Jul 18 21:56 /dev/sd1 brw------- 1 root operator 14, 26 Jul 18 21:56 /dev/sd1e brw------- 1 root operator 14, 27 Jul 18 21:56 /dev/sd1f brw------- 1 root operator 14, 28 Jul 18 21:56 /dev/sd1g brw------- 1 root operator 14, 10 Jul 18 21:56 /dev/sd2 brw------- 1 root operator 14, 29 Jul 18 21:56 /dev/sd2s1 brw------- 1 root operator 14, 30 Jul 18 21:56 /dev/sd2s1e brw------- 1 root operator 14, 31 Jul 18 21:56 /dev/sd2s1f DES -- One two, one two, one two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 18 14:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29517 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 14:22:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29507 for ; Sat, 18 Jul 1998 14:22:24 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.8.5/8.8.5) id HAA18260; Sun, 19 Jul 1998 07:22:05 +1000 (EST) Message-ID: <19980719072159.16036@welearn.com.au> Date: Sun, 19 Jul 1998 07:21:59 +1000 From: Sue Blake To: freebsd-hackers@FreeBSD.ORG Subject: Installation Packages [was: 2.2.6 CD-ROM : Package dependencies up the creek ?] References: <19980622074850.57163@welearn.com.au> <18668.898473053@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <18668.898473053@time.cdrom.com>; from Jordan K. Hubbard on Sun, Jun 21, 1998 at 04:50:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may recall we were talking about making it easy for new installers to select a set of appropriate packages, and the idea came up of having a single meta-package that could be offered during installation rather than pondering over a list of hundreds of packages. This would be particularly suited to people who are new to both FreeBSD and Unix. I felt that some additional documentation should be part of it too. On Sun, Jun 21, 1998 at 04:50:53PM -0700, Jordan K. Hubbard wrote: > > Since at this stage I'm rather vague about shell scripts let alone > > packages, and I've seen several others come up with related ideas, this > > will proceed on the basis of "if nobody else does something similar > > before I learn how to do it". > > I strongly urge you to do this even if someone else does do something > like it. This is a category of packages which could stand to have a > lot more than one entry in it and knowing how to create packages of > this nature is a valuable skill. Read the man page for pkg_create (it > will probably take several readings - the material is dense :) and > start off with small single-purpose packages which exercise each > specific feature of packages (install scripts, special PLIST > directives, etc) you're unclear on until you can put it all together. Done. Sort of. I've sussed out everything that's in the documentation, and a few things that are not, and just about got this together. In its present state the package seems to work well for me but could do with prettying up a bit. It installs other packages as provided on the 2.2.6 CD, since that's what I've had around to test it with. Easily fixed. The useful packages have been identified and basic documentation added. At this stage it is probably far too late to have it integrated with sysinstall for 2.2.7 as we had discussed, offered as an alternative to selecting from the list of packages. Obviously that would require someone with skills I don't have to spend some time in the next few days, which is unrealistic. It might even be too late to lump it in with the other packages in the hope that newbies will find it there, depending on how much is wrong with it. I'm letting you guys know where I'm up to anyway, since I did say I would try. It just took too long to get this far from square one. http://www.welearn.com.au/freebsd/newkit/ warts and all. If there is no reason to rush it into the upcoming release, I'll put it aside for now and write more documentation and config files until October. I can't see any way to make it work as a package unless it's either on the CD with the other packages or installed with assistance, and it's aimed at people who haven't got ppp or basic unix skills yet so downloading and fiddling is out of the question. I've learned what I wanted to learn and have other work to get on with. If I can get this far, maybe one of you can do better. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 18 14:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00375 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 14:28:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00370 for ; Sat, 18 Jul 1998 14:28:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA17287; Sat, 18 Jul 1998 14:25:03 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017277; Sat Jul 18 21:24:52 1998 Date: Sat, 18 Jul 1998 14:24:46 -0700 (PDT) From: Julian Elischer To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: hackers@FreeBSD.ORG Subject: Re: Dump device with DEVFS? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id OAA00371 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the test should be commented out for SLICE bde broke it because he thought it needed to test for a swap partition.. it actually needs to be re-examined.. check the history of that file for bruce's backout. your anaylsys is correct. On 18 Jul 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > It seems to be impossible to enable a dump device with DEVFS. The > following code in setdumpdev() in sys/i386/i386/autoconf.c is the > culprit: > > if (dkpart(dev) != SWAP_PART) > return (ENODEV); > > dkpart(dev) is #defined to (minor(dev) & 7) in disklabel.h, and > SWAP_PART is #defined to 1 in the same file. > > Now MAKEDEV will assign minor numbers with the lower nybble 0x1 to > swap partitions ([fosw]d?b or something like that) so it will work > fine, but Helen's swap partition (/dev/wd0s1b) has minor number 11 > (lower nybble 0x3), and Niobe's swap partition (/dev/sd0b) has minor > number 20 (lower nybble 0x4), neither of which is acceptable to > setdumpdev(). The only partition I have which is eligible as a dump > device (due to its minor number being 25) is /dev/sd0h, aka. /usr/src. > > Am I missing something here? Is this a bug or a feature? How do I set > a dump device on a DEVFS system? And anyway, shouldn't setdumpdev() > just trust the user to know what he's doing even if the selected > partition doesn't seem to be a swap partition? > > BTW, I just had a panic trying to umount an msdosfs floppy - probably > thanks to soft updates, all my file systems except /var came up clean > although I was cvsupping at the time of the panic. great.. > > For completeness' sake, here is my dmesg, kernel config and a listing > of /dev/sd*: > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #9: Fri Jul 17 18:26:15 CEST 1998 > finrod@niobe.ewox.org:/usr/src/sys/compile/niobe > Timecounter "i8254" frequency 1193182 Hz cost 2278 ns > Timecounter "TSC" frequency 166193751 Hz cost 137 ns > CPU: Pentium/P54C (166.19-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf > real memory = 134217728 (131072K bytes) > > FreeBSD Kernel Configuration Utility - Version 1.1 > Type "help" for help or "visual" to go to the visual > configuration interface (requires MGA/VGA display or > serial terminal capable of displaying ANSI graphics). > config> quit > avail memory = 127885312 (124888K bytes) > DEVFS: ready for devices > Probing for devices on PCI bus 0: > chip0: rev 0x03 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > de0: rev 0x22 int a irq 15 on pci0.9.0 > de0: ACCTON EN1207 21140A [10-100Mb/s] pass 2.2 > de0: address 00:00:e8:4a:83:63 > de0: enabling 100baseTX port > vga0: rev 0x70 int a irq 9 on pci0.10.0 > ahc0: rev 0x00 int a irq 12 on pci0.11.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > scbus0 at ahc0 bus 0 > sd0 at scbus0 target 2 lun 0 > sd0: type 0 fixed SCSI 2 > sd0: Direct-Access 4341MB (8890760 512 byte sectors) > sd0: with 5899 cyls, 10 heads, and an average 150 sectors/track > ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers > sd1 at scbus0 target 4 lun 0 > sd1: type 0 fixed SCSI 2 > sd1: Direct-Access 6180MB (12657717 512 byte sectors) > sd1: with 7068 cyls, 8 heads, and an average 223 sectors/track > ahc1: rev 0x00 int a irq 11 on pci0.12.0 > ahc1: aic7870 Single Channel, SCSI Id=7, 16 SCBs > scbus1 at ahc1 bus 0 > st0 at scbus1 target 3 lun 0 > st0: type 1 removable SCSI 2 > st0: Sequential-Access density code 0x0, drive empty > sd2 at scbus1 target 4 lun 0 > sd2: type 0 fixed SCSI 2 > sd2: Direct-Access 1030MB (2110812 512 byte sectors) > sd2: with 3658 cyls, 6 heads, and an average 96 sectors/track > cd0 at scbus1 target 5 lun 0 > cd0: type 5 removable SCSI 2 > cd0: CD-ROM cd present [258777 x 2048 byte records] > od0 at scbus1 target 6 lun 0 > od0: type 7 removable SCSI 2 > od0: Optical 217MB (446325 512 byte sectors) > od0: with approximate 217 cyls, 64 heads, and 32 sectors/track > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <12 virtual consoles, flags=0x0> > psm0 not found at 0x60 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > pcm0 not found > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > 1 3C5x9 board(s) on ISA found at 0x300 > ep0 at 0x300-0x30f irq 10 on isa > ep0: aui/bnc[*BNC*] address 00:60:8c:61:df:38 > npx0 on motherboard > npx0: INT 16 interface > Intel Pentium F00F detected, installing workaround > DEVFS: ready to run > IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 256 packets/entry > sd0: probing for MBR.. rejected.. Slice includes MBR sd0: probing for disklabel.. part a, start=0, size=131072 > part b, start=131072, size=1048576 > part d, start=3932160, size=4958600 > part e, start=1179648, size=131072 > part f, start=1310720, size=524288 > part g, start=1835008, size=1048576 > part h, start=2883584, size=1048576 > sd1: probing for MBR.. rejected.. Slice includes MBR sd1: probing for disklabel.. part e, start=0, size=524288 > part f, start=524288, size=1572864 > part g, start=2097152, size=10560565 > sd2: probing for MBR.. part 1, start=63, size=2104452 > sd2s1: attaching disklabel.. > part e, start=0, size=524288 > part f, start=524288, size=1580164 > fd0: probing for MBR.. WOULD SELECT /sd0a And it exists > WARNING: / was not properly dismounted. > fd0: Operation timeout > fd0: hard error, block 0 (No status) > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > > # > # Kernel configuration for niobe.ewox.org > # > machine "i386" > cpu "I586_CPU" > ident niobe > maxusers 64 > # > # Networking > options INET > options IPFIREWALL > options IPFIREWALL_VERBOSE > options "IPFIREWALL_VERBOSE_LIMIT=256" > options "NMBCLUSTERS=4096" > # > # File system > options DEVFS > options FFS > options FFS_ROOT # Boot from FFS > options NFS > options PROCFS > options SLICE # Use devfs for devices > options SOFTUPDATES > # > # XFree86 support > options SYSVMSG > options SYSVSEM > options SYSVSHM > options UCONSOLE > # > # Misc. kernel options > options "AUTO_EOI_1" > options "AUTO_EOI_2" > options "COMPAT_43" > options "MD5" > options BOUNCE_BUFFERS > options INCLUDE_CONFIG_FILE > options USERCONFIG > options USERCONFIG_BOOT > options USER_LDT > options VISUAL_USERCONFIG > # > config kernel root on sd0 > # > # Buses > controller isa0 > controller pci0 > controller pnp0 > # > # Numeric processor extensions > device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > # > # Floppy controller > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > # > # SCSI controllers > controller ahc0 > controller scbus0 > device sd0 > device od0 > device st0 > device cd0 > pseudo-device su > pseudo-device ssc > options "SCSI_DELAY=1" > options SCSI_REPORT_GEOMETRY > # > # System console and mouse > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > options "MAXCONS=12" > options "SC_HISTORY_SIZE=4096" > options "MSGBUF_SIZE=32768" > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > # > # I/O ports > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > device lpt0 at isa? port? tty irq 7 vector lptintr > # > # Network adapters > device de0 > device ep0 at isa? port 0x300 net irq 10 vector epintr > # > # Networking pseudo-devices > pseudo-device loop > pseudo-device ether > pseudo-device tun 4 > pseudo-device bpfilter 4 > # > # Other pseudo-devices > pseudo-device gzip > pseudo-device pty 64 > pseudo-device vn 4 > # > # Sound hardware (Luigi Rizzo) > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x15 vector pcmintr > # > > root@niobe # ll /dev/sd* > brw------- 1 root operator 14, 8 Jul 18 21:56 /dev/sd0 > brw------- 1 root operator 14, 19 Jul 18 21:56 /dev/sd0a > brw------- 1 root operator 14, 20 Jul 18 21:56 /dev/sd0b > brw------- 1 root operator 14, 21 Jul 18 21:56 /dev/sd0d > brw------- 1 root operator 14, 22 Jul 18 21:56 /dev/sd0e > brw------- 1 root operator 14, 23 Jul 18 21:56 /dev/sd0f > brw------- 1 root operator 14, 24 Jul 18 21:56 /dev/sd0g > brw------- 1 root operator 14, 25 Jul 18 21:56 /dev/sd0h > brw------- 1 root operator 14, 9 Jul 18 21:56 /dev/sd1 > brw------- 1 root operator 14, 26 Jul 18 21:56 /dev/sd1e > brw------- 1 root operator 14, 27 Jul 18 21:56 /dev/sd1f > brw------- 1 root operator 14, 28 Jul 18 21:56 /dev/sd1g > brw------- 1 root operator 14, 10 Jul 18 21:56 /dev/sd2 > brw------- 1 root operator 14, 29 Jul 18 21:56 /dev/sd2s1 > brw------- 1 root operator 14, 30 Jul 18 21:56 /dev/sd2s1e > brw------- 1 root operator 14, 31 Jul 18 21:56 /dev/sd2s1f > > DES > -- > One two, one two, one two. > > 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