From owner-freebsd-hackers Sun Sep 17 0:26:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4DCCB37B43E; Sun, 17 Sep 2000 00:26:39 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13aY9h-000ByY-00; Sun, 17 Sep 2000 07:42:25 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id HAA11257; Sun, 17 Sep 2000 07:42:25 +0100 (BST) (envelope-from ben) Date: Sun, 17 Sep 2000 07:42:25 +0100 From: Ben Smithurst To: Peter Avalos Cc: freebsd-hackers@freebsd.org, sheldonh@freebsd.org Subject: Re: passwd.1 Message-ID: <20000917074225.K56185@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Avalos wrote: > If I'm composing to the wrong list, please let me know who I should contact > about errors like this. Use send-pr next time (best option), or send the diffs to freebsd-doc@FreeBSD.org (second best option). If Sheldon doesn't do anything with this himself I'll look at it. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 0:33:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spock.org (cm-24-92-52-10.nycap.rr.com [24.92.52.10]) by hub.freebsd.org (Postfix) with ESMTP id EEFFB37B422 for ; Sun, 17 Sep 2000 00:33:23 -0700 (PDT) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F8823e8H7XHY45843F7T for freebsd-hackers@freebsd.org; Sun, 17 Sep 2000 03:33:17 -0400 (EDT) (envelope-from jon) Date: Sun, 17 Sep 2000 03:33:17 -0400 From: Jonathan Chen To: freebsd-hackers@freebsd.org Subject: VM86 interrupt calls from userland Message-ID: <20000917033317.A41735@spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a way to make VM86 interrupt calls from userland? The reason I'm asking is that in order to get my video card (Savage/IX) working in X properly, I need to make a couple of VESA int10 calls (or somehow obtain the programming specs for the card and do this the right way). Anyway, what I have tried is using the syscons ioctl()'s, which doesn't work here. Right now what I've done is modified src/sys/i386/i386/vm86.c to enable the VM86_INTCALL bit (and added a check for uid), and just called i386_vm86 from userland. This seems to work fine, but I want to know 1) Is there already some standard way to do this that I missed? The man page for i386_vm86 mentions sigreturn(), but I'm not sure if that will do what I want, plus I don't know how to use it anyway... 2) There was probably a reason the VM86_INTCALL stuff was #if'ed out... but I looked around the lists and cvs logs to see if one was mentioned and found none. This seems to work and I don't see how anything bad could come from this -- is it possible that this be enabled by default? 3) Or would the whole problem be solved more correctly by extending the ioctl by adding something like FBIO_SETMODE_ONLY where syscons would only switch the mode and not bother setting up the renderer or emulator? Thanks for any pointers... -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 3: 7: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 357E937B422 for ; Sun, 17 Sep 2000 03:06:51 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8HA48v39443; Sun, 17 Sep 2000 11:04:08 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8HA1Mm54441; Sun, 17 Sep 2000 11:01:22 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009171001.e8HA1Mm54441@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: mergemaster RFC (long) In-Reply-To: Message from Doug Barton of "Sat, 16 Sep 2000 21:23:54 PDT." <39C4475A.DBDA6C5@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Sep 2000 11:01:22 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > First, the things I am definitely going to do. Christian "naddy" > Weisgerber has taken on the task of porting mm to openbsd. He has made > some very reasonable requests that will make his life easier and reduce > gratuitous differences between versions. Also, several people have asked > for > the ability to specify DESTDIR, which is an easy fix and definitely an > understandable request. I think it would be nice to aim to keep the two scripts exactly the same, using `uname` when it's really necessary. IMHO this really helps when maintaining code - if there are different versions, the tendency is to update the one you use most, and ``mean to get around to'' updating the other(s) later. Of course the ``later'' tends to stop happening after a while... [.....] > script. I'm going to add variables to the .mergemasterrc file for > mergemaster-start and mergemaster-end scripts (names may change). These > scripts will run after the temproot environment is built, and after mm > is done with it's run. These scripts would be source'd from within mm so > all the variables will be available to them. This should allow people > to add in their own "options" that I don't want to add to the program. I like this idea. Perhaps the man page should have a HOWTO section that describes how to ``not compare files'' by deleting them in the start script etc. > This is cobbled together from various people's suggestions. > We need a list of files somewhere (probably in .mergemasterrc) that > people don't ever want to have to deal with via the "normal" mm process. > If a file on that list has been updated (according to the cvs tag) then > instead of presenting that file to the user, it will be ignored the > first time through. Then, at the end of the script there will be a > printout similar to what happens when the user leaves a file to do by > hand later. Something like: I think having IGNOREFILES="a b c" isn't necessary when it's as easy to have rm a b c in your start script. It seems like overkill to handle ignored files specifically. > Next on the list of things I'm open to suggestions on is a small script > I wrote that compares the variables in /etc/rc.conf[.local] to the ones > in /etc/defaults/rc.conf, and does the same for make.conf. [.....] I don't really think it matters where this happens in mergemaster, but it would be nice to include periodic.conf too. Of course you can't generically include everything in defaults/ as pccard.conf is probably something to avoid. > This also brings up the question of which files in /etc are good to > examine before a world build. [.....] Yes, too much handholding I think. > There was a PR filed in regards to the current situation with the new > sendmail moving the aliases file to /etc/mail, and mergemaster's [.....] Yep, this is definitely an SEP ! > I have an idea related to getting users to actually READ the man page [.....] Yeuch ! :-) > And the last of the ideas I want feedback on is related to the problem > of determining permissions on the files to be installed. To my knowledge [.....] Perhaps the best thing here is to make mtree capable of understanding rwxrwxrwx type modes, and then generate an mtree spec file based on the stuff in temproot and apply it to destdir ? > Doug > -- > "The dead cannot be seduced." > - Kai, "Lexx" > > Do YOU Yahoo!? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 6: 1:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web5103.mail.yahoo.com (web5103.mail.yahoo.com [216.115.106.73]) by hub.freebsd.org (Postfix) with SMTP id 48D9537B423 for ; Sun, 17 Sep 2000 06:01:33 -0700 (PDT) Message-ID: <20000917130132.18895.qmail@web5103.mail.yahoo.com> Received: from [203.101.93.133] by web5103.mail.yahoo.com; Mon, 18 Sep 2000 00:01:32 EST Date: Mon, 18 Sep 2000 00:01:32 +1100 (EST) From: =?iso-8859-1?q?Paul=20Jansen?= Subject: diskless - /sbin/init won't start over NFS mounted root To: hackers@freebsd.org, questions@freebsd.org 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 I'm having troubles getting a diskless system to boot using a FreeBSD 4.1R server and a custom compiled FreeBSD 4.1R kernel. I've made sure the following options were defined in my custom kernel: options NFS_ROOT #NFS usable as root # Kernel BOOTP support options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT # Workaround for broken bootp daemons. I'm using the ISC v2 DHCP server. Here's the /usr/local/etc/dhcpd.conf file: # dhcpd.conf # option definitions common to all supported networks... option domain-name "jansen.org"; option domain-name-servers 202.167.41.130; option subnet-mask 255.255.255.0; default-lease-time 600; max-lease-time 7200; subnet 192.168.0.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.10 192.168.0.20; option routers 192.168.0.8; option broadcast-address 192.168.0.255; filename "/tftpboot/kernel.XWORKSTATION"; option root-path "192.168.0.1:/usr/diskless/rootfs/xworkstation"; option option-128 "192.168.0.1:/usr/diskless/swap"; option option-132 00:00:08:00; option option-176 5; option option-160 "timeout=8:default=193:"; option option-192 "IJ2:::/tftpboot/kernel.ij2:"; option option-193 "XWORKSTATION:::/tftpboot/kernel.XWORKSTATION:"; } The boot process get all the way down to mounting root and swap over NFS. The line: option option-132 00:00:08:00; in the dhcpd.conf file above allows for verbose information to be displayed to the console when booting. The last few lines displayed on the console boot screen are: Mounting root from NFS: NFS ROOT:192.168.0.1:/usr/diskless/rootfs/xworkstation NFS SWAP:192.168.0.1:/usr/diskless/swap start_init: trying /sbin/init So the system has a problem running /sbin/init over the nfs mounted root. I've had a look at what's happening on the wire using ethereal. This is what it turns up: first of all the diskless system sends an NFS request to the server of type 'LOOKUP CALL'. Ethereal> says that proceure LOOKUP is happening in this packet. The next packet goes from the server to the> diskless machine. The procedure is again LOOKUP but this time the packet also has an status entry for NFS. The status says: ERR_NOENT (2) My /etc/exports file has the following line in it: /usr -alldirs -maproot=0:0edessa pico host10 host11 host12 host13 I've checked that the filesystem referenced above is being successfully exported using NFS by mounting it on another machine on the network. I can go into the /sbin directory and execute init. Of course the other machine complains because it already has init running. This just goes to show that the exports directory is mountable and the files are executable. Does anyone have any ideas as to what is wrong here. I am stumped and am quite keen to get diskless operation happening soon. Thanks in advance, Paul _____________________________________________________________________________ http://geocities.yahoo.com.au - Yahoo! Australia & NZ GeoCities - Build your own Web Site - for free! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 9:22: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id EA9F137B422 for ; Sun, 17 Sep 2000 09:22:00 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id e8HGLOR54666; Sun, 17 Sep 2000 11:21:24 -0500 (CDT) (envelope-from jlemon) Date: Sun, 17 Sep 2000 11:21:24 -0500 (CDT) From: Jonathan Lemon Message-Id: <200009171621.e8HGLOR54666@prism.flugsvamp.com> To: jon@spock.org, hackers@freebsd.org Subject: Re: VM86 interrupt calls from userland X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Is there a way to make VM86 interrupt calls from userland? The reason I'm >asking is that in order to get my video card (Savage/IX) working in X >properly, I need to make a couple of VESA int10 calls (or somehow obtain >the programming specs for the card and do this the right way). Anyway, >what I have tried is using the syscons ioctl()'s, which doesn't work here. >Right now what I've done is modified src/sys/i386/i386/vm86.c to enable the >VM86_INTCALL bit (and added a check for uid), and just called i386_vm86 >from userland. This seems to work fine, but I want to know > >1) Is there already some standard way to do this that I missed? The man > page for i386_vm86 mentions sigreturn(), but I'm not sure if that will > do what I want, plus I don't know how to use it anyway... >2) There was probably a reason the VM86_INTCALL stuff was #if'ed out... but > I looked around the lists and cvs logs to see if one was mentioned and > found none. This seems to work and I don't see how anything bad could > come from this -- is it possible that this be enabled by default? >3) Or would the whole problem be solved more correctly by extending the > ioctl by adding something like FBIO_SETMODE_ONLY where syscons would > only switch the mode and not bother setting up the renderer or emulator? I added VM86_INTCALL while developing the vm86 system for this very reason; so I could make vm86 calls from userland. However, it was turned off before it was initially committed, since it could probably open up a security hole or worse. My feeling is that this functionality probably belongs in the kernel (point #3), but as a workaround, adding a root capability check and then enabling the vm86 functionality is probably acceptable. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 10:40:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mazurek.man.lodz.pl (mazurek.man.lodz.pl [212.51.192.15]) by hub.freebsd.org (Postfix) with ESMTP id D09FB37B422 for ; Sun, 17 Sep 2000 10:40:33 -0700 (PDT) Received: from adas (pb136.lodz.ppp.tpnet.pl [212.160.29.136]) by mazurek.man.lodz.pl (8.9.3/8.9.3) with ESMTP id TAA07981 for ; Sun, 17 Sep 2000 19:40:23 +0200 From: "Piotr Sroczynski" To: hackers@FreeBSD.ORG Date: Sun, 17 Sep 2000 19:42:02 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: PnP & 4.1 Release Message-ID: <39C51E8A.13856.5959D@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to stop any PnP operation (checking, seting) during boot? Piotr Sroczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 12:41:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 22DDC37B424 for ; Sun, 17 Sep 2000 12:41:40 -0700 (PDT) Received: from work.mzaki.nom (26.pool9.ipctokyo.att.ne.jp [165.76.205.26]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id EAA18096; Mon, 18 Sep 2000 04:41:38 +0900 (JST) Date: Mon, 18 Sep 2000 04:41:37 +0900 Message-ID: <86em2ihklq.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: hackers@FreeBSD.ORG Subject: PnP resource programming X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Note: Initially pointed out by Hirokazu WATANABE ) PnP resource programming goes in pnp_set_config() in sys/isa/pnp.c: /* program memory resource registers */ for (i = 0; i < config->ic_nmem; i++) { pnp_write(PNP_MEM_...(i), ...); : : } /* zero'ing unused registers */ for (; i < ISA_NMEM; i++) { pnp_write(PNP_MEM_...(i), 0); : : } According to ISA PnP specifications, maximum number of memory resource set is 4 and there is only 4 sets of registers for memory resource programming. But ISA_NMEM is defined to 8 in sys/isa/isavar.h, and this code causes unexpected I/O writing. The same mistakes happen about port resources. There is only 8 sets of registers for port resource programming, but kernel writes into 50 sets of registers during PnP resource programming. I suggest that we should newly define ISA_PNP_NMEM and ISA_PNP_NPORT as 4 and 8 respectively, and use them as a substitute for ISA_NMEM and ISA_NPORT in above case. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 14: 2:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 32A8537B424 for ; Sun, 17 Sep 2000 14:02:36 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA27585; Mon, 18 Sep 2000 01:02:29 +0400 (MSD) Message-Id: <200009172102.BAA27585@aaz.links.ru> Subject: Re: mergemaster RFC (long) In-Reply-To: <39C4475A.DBDA6C5@gorean.org> from "Doug Barton" at "Sep 16, 0 09:23:54 pm" To: DougB@gorean.org (Doug Barton) Date: Mon, 18 Sep 2000 01:02:29 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton writes: .......... > And the last of the ideas I want feedback on is related to the problem > of determining permissions on the files to be installed. To my knowledge > there is no existing C utility that will tell you the octal permissions ports/sysutils/stat, for example 0cicuta~(12)>stat -f'%p' . 0755/drwxr-xr-x But I have stat patched to delete File: \"%s\" clause from printing if no need for it. It is short program and useful in base system 0cicuta~(13)>ls -al `which stat` 6 -r-xr-xr-x 1 root wheel 5720 26 Á×Ç 00:58 /usr/local/bin/stat* > on a file, and preferably also combine them with the umask to spit out > what the permissions should be. My current solution for that is a couple > of one line perl scripts, but I really want to eliminate that as my > contribution to the "don't make anything in the base depend on perl" > campaign. I have written a little tiny program in C to do this which > could be included along with mergemaster, what do people think? It is > possible to do the same thing in sh, but it's very cumbersome, unless > someone can suggest some combination of existing utilities that I > haven't considered yet. The main problem with doing it in sh (which I've > done in the past) is that the umask effectively means "different" things > if it's a binary/directory or if it's a regular file, so even though > getting the permissions is easy (with ls, whatever) combining it with > the umask is hard. Of course, I could always take that whole section > out, and just install the files with the permissions created by > /usr/src/etc/Makefile. I see less need now of custom permissions than I > did ages ago, but what do others think? .............. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 14: 7:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 4293037B422 for ; Sun, 17 Sep 2000 14:07:09 -0700 (PDT) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA58863; Sun, 17 Sep 2000 14:06:53 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39C5326B.F80CF5C2@gorean.org> Date: Sun, 17 Sep 2000 14:06:51 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-091 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Aleksandr A.Babaylov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mergemaster RFC (long) References: <200009172102.BAA27585@aaz.links.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Aleksandr A.Babaylov" wrote: > > Doug Barton writes: > .......... > > And the last of the ideas I want feedback on is related to the problem > > of determining permissions on the files to be installed. To my knowledge > > there is no existing C utility that will tell you the octal permissions > ports/sysutils/stat, for example Thank you for the reference. I should have stated more explicitly that it needs to be part of the base already. You're correct in stating that a program to manipulate the stat(2) function is easy to write, even I can write one. :) Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 14:18:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 25DE837B422; Sun, 17 Sep 2000 14:18:38 -0700 (PDT) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.9.3/8.8.8) with ESMTP id RAA24394; Sun, 17 Sep 2000 17:18:34 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Sun, 17 Sep 2000 17:18:34 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Ben Smithurst Cc: Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <20000914115342.I77593@strontium.scientia.demon.co.uk> 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, 14 Sep 2000, Ben Smithurst wrote: > Poul-Henning Kamp wrote: > > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > > is bogus. It looks like something which happened "because we can" more > > than something which has a legitimate need. > > You think adding a hack to every program to support "-" to mean > stdout/stdin is better? It seems to be that saying "/dev/stdin" when > you mean stdin is better than saying "-" and hoping the application > handles that correctly. Of course many programs will read stdin by > default, and write stdout by default, but that doesn't help when you > want to read more than one file, one of which is stdin. > > > If anything I would propose we ditch it... > > And break loads of scripts at the same time? I recently ran into revelant problem with /dev/stdout, while working on some software under linux that expected /dev/stdout as an argument instead of using stdout. Using the device file breaks, if the process is suid to a non-root user. This is because it cannot open /dev/stdout, which is owned by your UID and not the EUID of the process to which the device was passed. My solution was to add the "-" hack and use the existing open descriptor. Still, I don't think /dev/stdout and friends are such bad things that they should be abandoned. They are present in other OS's and it does help avoid making named pipes and the such when you need the behavior the special devices provide. I think it would simple create minor poratability issues for third party software. 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 Sep 17 19:19:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from astart2.astart.com (astart2.astart.com [64.63.58.122]) by hub.freebsd.org (Postfix) with ESMTP id 1637A37B422 for ; Sun, 17 Sep 2000 19:19:35 -0700 (PDT) Received: from h4.private (papowell@h4.private [10.0.0.4]) by astart2.astart.com (8.9.3/8.9.3) with ESMTP id MAA20778 for ; Sun, 17 Sep 2000 12:18:44 -0700 (PDT) (envelope-from papowell@astart.com) Received: (from papowell@localhost) by h4.private (8.9.3/8.9.3) id TAA12263 for freebsd-hackers@freebsd.org; Sun, 17 Sep 2000 19:20:43 -0700 (PDT) Date: Sun, 17 Sep 2000 19:20:43 -0700 (PDT) From: papowell@astart.com Message-Id: <200009180220.TAA12263@h4.private> To: freebsd-hackers@freebsd.org Subject: Device driver, memory map failing, and it is probably obvious Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am making a driver for a VERY old PCI device. I decided to try using the new 'bus_resource' facilities, and came up with the oddest error. First, here is my 'probe' routine: > static int > digic_probe(device_t dev) > { > static struct digic_type *t; > int vendor = pci_get_vendor(dev); > int did = pci_get_device(dev); > DPRINTF(("myprobe: vendor 0x%x, device 0x%x\n", > vendor, did )); > for( t = digic_devs; t->vid; ++t ){ > if( (t->vid == vendor) && (t->did == did) ){ > DPRINTF(("found '%s'\n", t->name ); > device_set_desc(dev,t->name)); > return(0); > } > } > return( ENXIO ); > } And here is the output it puts out (from dmesg): > Copyright (c) 1992-2000 The FreeBSD Project. > .... > myprobe: vendor 0x1106, device 0x597 > pcib2: at device 1.0 on pci0 > pci1: on pcib2 > myprobe: vendor 0x1002, device 0x4742 Yes it is seeing things... > pci1: at 0.0 irq 11 > isab0: at device 7.0 on pci0 > isa0: on isab0 .... > found 'Digi International PCI Classic 8 Serial Adapter' > my0: \ port 0xdc00-0xdcff,0xd800-0xd87f mem 0xea400000-0xea4000ff,0xea402000-0xea40207f \ irq 12 at device 10.0 on pci0 > digic_attach: unit 0, irq 12, slot 10, progif 0x0, iobase 0xd801, membase 0xea402000, irqline 0x10c > my0: couldn't map memory > device_probe_and_attach: my0 attach returned 6 So it found the card, discovered the vintage hardware id, and printed it out. The we call the attach routine: > static int > digic_attach( device_t dev ) > { > struct digic_softc *digic; > int unit; > int irq, slot, progif, iobase, membase, irqline; > int error = 0; > void *ih = 0; > > /* get the sc structure */ > digic = device_get_softc(dev); > bzero(digic,sizeof(digic[0])); > unit = device_get_unit(dev); > irq = pci_get_irq(dev); > slot = pci_get_slot(dev); > progif = pci_get_progif(dev); > > #define WB_PCI_LOMEM 0x10 > #define WB_PCI_LOIO 0x14 > #define WB_PCI_INTLINE 0x3c > iobase = pci_read_config(dev, WB_PCI_LOIO, 4); > membase = pci_read_config(dev, WB_PCI_LOMEM, 4); > irqline = pci_read_config(dev, WB_PCI_INTLINE, 4); > > DPRINTF(("digic_attach: unit %d, irq %d, slot %d, progif 0x%x, iobase 0x%x, membase 0x%x, irqline 0x%x\n", > unit, irq, slot, progif, iobase, membase, irqline )); > > > switch( pci_get_device(dev) ){ > case PCI_CLASSIC_4: digic->digic_ports = 4; break; > case PCI_CLASSIC_8: digic->digic_ports = 8; break; > default: > device_printf(dev,"digic_attach: bad device id! %d", pci_get_device(dev)); > goto fail; > } > > /* now get the memory resources */ > digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, > &digic->digic_mem_rid, > 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); > if (!digic->digic_mem_res) { > device_printf(dev, "couldn't map memory\n"); > goto fail; > } Now, I am SURE that I must be doing something stupid here - but I snipped this code right out of the code for another driver, and this one works. The only puzzle is: > my0: \ port 0xdc00-0xdcff,0xd800-0xd87f mem 0xea400000-0xea4000ff,0xea402000-0xea40207f \ irq 12 at device 10.0 on pci0 Note that the diagnostic output indicates some VERY strange ranges. Could this be the problem? Patrick Powell Patrick Powell Astart Technologies, papowell@astart.com 9475 Chesapeake Drive, Suite D, Network and System San Diego, CA 92123 Consulting 858-874-6543 FAX 858-279-8424 LPRng - Print Spooler (http://www.astart.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 20: 1:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2DD0937B422 for ; Sun, 17 Sep 2000 20:01:54 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA88523; Sun, 17 Sep 2000 21:01:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA27758; Sun, 17 Sep 2000 21:01:44 -0600 (MDT) Message-Id: <200009180301.VAA27758@harmony.village.org> To: papowell@astart.com Subject: Re: Device driver, memory map failing, and it is probably obvious Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 17 Sep 2000 19:20:43 PDT." <200009180220.TAA12263@h4.private> References: <200009180220.TAA12263@h4.private> Date: Sun, 17 Sep 2000 21:01:44 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009180220.TAA12263@h4.private> papowell@astart.com writes: : I am making a driver for a VERY old PCI device. : > digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, : > &digic->digic_mem_rid, : > 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); : Could this be the problem? Where do you initialize digic_mem_rid? You should set this equal to the BAR offset in the PCI config space that corresponds to this memory. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 22:12: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id CFF4137B424 for ; Sun, 17 Sep 2000 22:11:17 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA05195; Mon, 18 Sep 2000 12:10:46 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 18 Sep 2000 12:10:46 +0700 (NSS) From: Max Khon To: John Polstra Cc: hackers@freebsd.org Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009160037.RAA06418@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 15 Sep 2000, John Polstra wrote: > Here is another possibility: we could call _thread_init() from > crt1.o. The patch (untested) is below. It calls _thread_init() if > and only if that symbol is defined -- i.e., libc_r is linked in. > What do you think about this solution? > > Index: crt1.c > =================================================================== > RCS file: /home/ncvs/src/lib/csu/i386-elf/crt1.c,v > retrieving revision 1.4 > diff -u -r1.4 crt1.c > --- crt1.c 1999/08/27 23:57:57 1.4 > +++ crt1.c 2000/09/16 00:30:51 > @@ -48,6 +48,9 @@ > extern int _DYNAMIC; > #pragma weak _DYNAMIC > > +extern void _thread_init(void); > +#pragma weak _thread_init > + > #ifdef __i386__ > #define get_rtld_cleanup() \ > ({ fptr __value; \ > @@ -91,6 +94,8 @@ > #ifdef GCRT > monstartup(&eprol, &etext); > #endif > + if (&_thread_init != NULL) > + _thread_init(); > _init(); > exit( main(argc, argv, env) ); > } > seems ok to me but can we do this from `do_ctors' or `_init' -- they are located in common/ /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 17 23:22:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 7196137B423; Sun, 17 Sep 2000 23:22:42 -0700 (PDT) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id PAA49090; Mon, 18 Sep 2000 15:22:39 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200009180622.PAA49090@shidahara1.planet.sci.kobe-u.ac.jp> To: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org Subject: PEACE - Portable Executable win32 API Compatible Environment. Date: Mon, 18 Sep 2000 15:22:38 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I ported kernel part of PEACE from NetBSD.(That is in sys/compat/pecoff/*). What is PEACE PEACE is Win32 API Compatible environment for (Originally) NetBSD. It consist of three parts: Kernel part to load PE format executable onto process memory space. Dynamic Linker to link with PE format DLL. Libraries to translate Win32 API call to NetBSD native system call. Yes, this scheme is more like BSD/OS's LAP than FreeBSD Linux ABI module. For more infomation: http://chiharu.hauN.ORG/peace/ Status: FreeBSD Specific: - I ported executable loader moudule to FreeBSD. - FreeBSD native libraries is not yet available,so I wrote a module to add(or replace) system call so that the libraries can be run. - It requires following changes to sys/imgact.h and kern/kern_exec.c to be able to change size of memory area to hold dynamic linker argument from executable image loader. --- sys/imgact.h.orig Mon Sep 18 02:18:46 2000 +++ sys/imgact.h Mon Sep 18 02:19:25 2000 @@ -58,6 +58,7 @@ struct vm_page *firstpage; /* first page that we mapped */ char *fname; /* pointer to filename of executable (user space) */ unsigned long ps_strings; /* PS_STRINGS for BSD/OS binaries */ + size_t auxarg_size; }; #ifdef _KERNEL --- kern/kern_exec.c.orig Fri Jul 14 15:44:45 2000 +++ kern/kern_exec.c Mon Sep 18 02:59:45 2000 @@ -127,6 +127,7 @@ imgp->vp = NULL; imgp->firstpage = NULL; imgp->ps_strings = 0; + imgp->auxarg_size=0; /* * Allocate temporary demand zeroed space for argument and @@ -613,14 +614,21 @@ * If we have a valid auxargs ptr, prepare some room * on the stack. */ - if (imgp->auxargs) + if (imgp->auxargs){ + /* + * 'AT_COUNT*2' is size for the ELF Auxargs data. + * This is for lower compatibility. + */ + imgp->auxarg_size=(imgp->auxarg_size)?imgp->auxarg_size + :(AT_COUNT*2); /* * The '+ 2' is for the null pointers at the end of each of the - * arg and env vector sets, and 'AT_COUNT*2' is room for the - * ELF Auxargs data. + * arg and env vector sets,and imgp->auxarg_size is room for argument + * of Runtime loader. */ vectp = (char **)(destp - (imgp->argc + imgp->envc + 2 + - AT_COUNT*2) * sizeof(char*)); + imgp->auxarg_size) * sizeof(char*)); + } else /* * The '+ 2' is for the null pointers at the end of each of the You can get These modules at http://www.planet.sci.kobe-u.ac.jp/~takawata/peace/peace4fbsd-kmodule.tar.gz General status: - Some command line application like FTP.EXE, CMD.EXE ,EXTRAC32.EXE can be run. - Simplest GUI application can be run,such as whello.exe ,distributed in PEACE website. ToDO priority order. - Merge the patch to precede .(Who should I ask about it?) - Merge pecoff loader module to FreeBSD. - Create native ld.so.dll ,pecoff format of libc.a and libc.dll . - Share library sources with NetBSD version as much as we can. NOTE: I don't subscribe freebsd-emulation. Thanks in advance . Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 0:49:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 5233937B42C for ; Mon, 18 Sep 2000 00:49:36 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13avg4-0003BC-00; Mon, 18 Sep 2000 09:49:24 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA18853; Mon, 18 Sep 2000 09:49:20 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 18536; Mon Sep 18 09:47:54 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13avec-0006Ez-00; Mon, 18 Sep 2000 09:47:54 +0200 From: Sheldon Hearn To: "Peter Avalos" Cc: freebsd-hackers@freebsd.org Subject: Re: passwd.1 In-reply-to: Your message of "Sun, 17 Sep 2000 00:48:27 EST." Date: Mon, 18 Sep 2000 09:47:54 +0200 Message-ID: <23992.969263274@axl.fw.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000 00:48:27 EST, "Peter Avalos" wrote: > I don't know who to contact about this, so I'm hoping some people subscribed > to this list have commit access. I found some spelling errors in passwd(1) > manpage. I have RELENG_4 installed. Here's the output of diff -u: Thanks. Your delta has been committed as rev 1.19 of passwd.1 and has been merged onto the RELENG_4 branch. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 6:26:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 172C937B422; Mon, 18 Sep 2000 06:26:20 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13b0vw-0005Au-00; Mon, 18 Sep 2000 16:26:08 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13b0vv-0002Vr-00; Mon, 18 Sep 2000 16:26:07 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: Paul Saab , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Mon, 11 Sep 2000 09:00:51 +0300 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2000 16:26:07 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG }In message <20000910123829.A50324@elvis.mu.org>you write: }}Danny Braniss (danny@cs.huji.ac.il) wrote: }}> BTW, is someone working in passing all this stuff via dhcp? im trying to co }m }}e}}> up with an almost zero admin diskless ws solution. }} }}Yes, this has been done in current for a while and was back ported to }}-stable yesterday. }} }will tryout asap. } if by -stable you mean whatever i get when i do a 'cvs co -rRELENG_4' src/sys then there are some things missing. i386/i386/autoconf.c does not have the stuff for pxe. if i compile a kernel with the BOOTP_ stuff, then i can mount nfsroot, but [mount_]mfs is broken, i get 'bad address' when trying to mount_mfs ... /conf/etc. if i see (or think i see :-) a bug in the diskless stuff who do i inform? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 6:28: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 0432D37B422; Mon, 18 Sep 2000 06:27:45 -0700 (PDT) Received: from jarrow.dev.nanoteq.co.za (jarrow [196.37.91.33]) by oskar.nanoteq.co.za (8.9.3/8.9.0) with ESMTP id PAA09239; Mon, 18 Sep 2000 15:30:05 +0200 (SAT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 18 Sep 2000 15:26:10 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org, jhb@freebsd.org Subject: libc causes sylogd misbehaviour - fix included Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi .. Sorry for the cross mail but I know there are a few people that suffer from this problem and would like a fix. Quick problem description: When using remote logging, on the server where the logs are written, syslogd tends to stop logging any more info at some stage. This also prevents you to su (if you use a console and it is not plugged in). If you kill syslogd and restart it again .. the first attempt fails when syslogd wants to open the console. Sometimes only a reboot solves the problem. It was possible for me to recreate this problem readily by denying icmp port unreachable packets from the non existing DNS server, causing syslogd to get stuck in cvthname->..->..->poll in libc. If I leave syslogd in this state for a minute or so, and then remove the packet filter, syslogd NEVER recovers and nothing is logged anymore. This condition also seams to occur every now and then (once a day) on a working system without packet filtering. Solution: In libc/net changes were made to res_send.c - specifically in revision 1.32 preventing a deadlock (ever loop) in the name resolution if a SIGALRM was received during that time. This was MFC'ed to 4-stable but not 3-stable (understandably). I made a diff between 1.31 and 1.32 of res_send.c - applied it to my RELENG_3 libc (1.25.2.1) and recompiled libc. When trying to recreate the above error, after the 1 minute deny of icmp's, and removing the rule, syslogd recovers and continues to log without a problem. Conclusion: Is it possible for someone the MFC rev 1.31->1.32 of libc/net/res_send.c to the 3-STABLE ?? And while doing that ... would you be so kind as to also add the "-n" option to disable DNS lookups which is in current at the moment ?? I would really appreciate it ... Thanks Reinier ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 18-Sep-00 Time: 15:09:17 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 6:39:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D8A6337B423; Mon, 18 Sep 2000 06:39:30 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA21762; Tue, 19 Sep 2000 00:39:11 +1100 Date: Tue, 19 Sep 2000 00:39:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Adrian Filipi-Martin Cc: Ben Smithurst , Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote: > I recently ran into revelant problem with /dev/stdout, while > working on some software under linux that expected /dev/stdout as an > argument instead of using stdout. > > Using the device file breaks, if the process is suid to a non-root > user. This is because it cannot open /dev/stdout, which is owned by your > UID and not the EUID of the process to which the device was passed. My > solution was to add the "-" hack and use the existing open descriptor. Um, open on fdesc devices doesn't check either uid. It just checks the access mode. Perhaps the software expected /dev/stdout to for read-write like a tty would be. Then opening /dev/stdout would fail for normal shell output redirection which only opens for writing. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 7:12:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 3FB5C37B423 for ; Mon, 18 Sep 2000 07:12:54 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JUBOX7OPQG000G8W@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Mon, 18 Sep 2000 16:12:45 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Mon, 18 Sep 2000 16:12:43 +0100 Content-return: allowed Date: Mon, 18 Sep 2000 16:12:41 +0100 From: "Koster, K.J." Subject: RE: diskless workstation To: 'Danny Braniss' Cc: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D78C4@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > if by -stable you mean whatever i get when i do a 'cvs co > -rRELENG_4' src/sys > then there are some things missing. > i386/i386/autoconf.c does not have the stuff for pxe. > if i compile a kernel with the BOOTP_ stuff, then i can mount > nfsroot, but > [mount_]mfs is broken, i get 'bad address' when trying to > mount_mfs ... /conf/etc. > > if i see (or think i see :-) a bug in the diskless stuff who > do i inform? > I think the "bad address" messages indicate that your kernel and your "world" are out of sync. Do a make world and install a freshly compiled kernel. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 8: 5: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201]) by hub.freebsd.org (Postfix) with ESMTP id 4E22F37B43C for ; Mon, 18 Sep 2000 08:05:03 -0700 (PDT) Received: from localhost (stein@localhost) by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id LAA16788 for ; Mon, 18 Sep 2000 11:19:17 -0400 (EDT) (envelope-from stein@eecs.harvard.edu) X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs Date: Mon, 18 Sep 2000 11:19:17 -0400 (EDT) From: Christopher Stein To: hackers@freebsd.org Subject: 4.1 make world and cvsup release field Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I don't wish to jump all the way forward to -CURRENT, but would like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0 for kqueue() and fxp PEX support). I would like to do this via cvsup and `make world'. My understanding is that `make world' is just buildworld followed by installworld, each a single monolithic step. Hhmm.. it seems to me that some build stages will not work without some other elements being installed. For example, my current modified 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 vs. 2.10). So how can a `make world' work in a monolithic build then install sequence? How do I specify 4.1 in the release field of my supfile? (The man page isn't too enlightening. Says "The supfile is as described in sup(1)". `man sup` turns up nothing. An additional blurb on the release=releasename keyword talks about traditional sup and recommends using releasename=cvs.) thanks -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 8:56: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id ACFBA37B422; Mon, 18 Sep 2000 08:55:53 -0700 (PDT) Received: from newsguy.com (p03-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.132]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA11656; Tue, 19 Sep 2000 00:55:43 +0900 (JST) Message-ID: <39C63ACD.441658CC@newsguy.com> Date: Tue, 19 Sep 2000 00:54:53 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif wrote: > > What is the FreeBSD naming convention for devices of disk slices and > labels? Considering my system is installed on the first partition of > /dev/wd0 (non-dedicated), these are the block-device interfaces I > have to my disk: > > wd0 wd0c wd0f wd0s1 wd0s1c wd0s1f wd0s2 > wd0a wd0d wd0g wd0s1a wd0s1d wd0s1g wd0s3 > wd0b wd0e wd0h wd0s1b wd0s1e wd0s1h wd0s4 That's for up to 3.x. From 4.x, the device name is ad. > Questions: > 1. What are wd0[a-h] used for? 1) Dangerously Dedicated Disks (no slices). 2) Compatibility mode (an ugly hack) alias for the first FreeBSD slice on that disk. > 2. If wd0s1 is my first slice, why isn't it named wd0s0? Because a slice is what DOS calls a "partition table". They are numbered from 1 on, so we decided to keep the numbering to make things less confusing (which, if you think of it, is pretty silly with the partition/slice confusion). > 3. If I format wd0s2 as any type (Xenix for example), > will /dev now contain wd0s2[a-h]? No. 1. /dev is not a "magical" directory. It contains only what you put in there. 2. If you happened to have devfs, which _is_ "magical", partitions still require that a partition table exists in the slice. > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 > doesn't span to the end of disk: > 4. If I want to use /dev/wd0s2 as a raw slice for reading > and writing, what are the steps to follow? None. You just use it. > 4a. Do I need to format the partition as any type? If so > is there a recommended type (perhaps one which won't > be recognised by the bootloader would be preferable)? No, you don't need to format it, nor do you need to worry about it's type. Just make sure the slice does exist. > 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a > for reading and writing (of course, this is assuming > block i/o of multiples of 512 bytes)? Nope, using raw devices is almost always wrong, and we even got rid of raw device in latter versions of FreeBSD. A "raw" device is an _unbuffered_ device. It has nothing to do with formats or types. Anyway, you should be using /dev/wd0s2. Unless you partition the slice, and want to use the "a" partition. > Lastly, where else could I have found this information other > than asking on the FreeBSD mailing list? Beats me, but it _should_ be in the handbook. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net "I demand that my picture show a handsome face, even if it doesn't look like me." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 8:57:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id E592437B423; Mon, 18 Sep 2000 08:57:13 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id DC55F2B282; Mon, 18 Sep 2000 10:57:07 -0500 (CDT) Date: Mon, 18 Sep 2000 08:57:07 -0700 From: Paul Saab To: Danny Braniss Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000918085707.A9107@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Mon, Sep 18, 2000 at 04:26:07PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > if by -stable you mean whatever i get when i do a 'cvs co -rRELENG_4' src/sys > then there are some things missing. > i386/i386/autoconf.c does not have the stuff for pxe. > if i compile a kernel with the BOOTP_ stuff, then i can mount nfsroot, but > [mount_]mfs is broken, i get 'bad address' when trying to > mount_mfs ... /conf/etc. That means your kernel and userland are out of sync. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 9: 1:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 9793337B423; Mon, 18 Sep 2000 09:01:37 -0700 (PDT) Received: from newsguy.com (p03-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.132]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA13070; Tue, 19 Sep 2000 01:00:52 +0900 (JST) Message-ID: <39C63C03.2C4C26F8@newsguy.com> Date: Tue, 19 Sep 2000 01:00:03 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Marc Tardif Cc: "Aleksandr A.Babaylov" , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif wrote: > > If I understand correctly, wd0[a-h] will be the same as wd0s3[a-h] in a > situation where DOS is on first slice, Linux on second and FreeBSD on > third, right? But what if the fourth slice is also FreeBSD? In such a Right. > case, I'll assume you meant "booted slice" instead of "first slice", where > the slice selected when booting will be referred to by the OS as wd0[a-h] > which would translate to "current slice". Confirmation of my assumption > would be appreciated. Nope, he means "first slice", not "booted slice". I think, at some point, it might have changed to "active partition". But the fact is that the wd0[a-h] hack is very gross. Stay away from it, and always use full device specification. > > > 2. If wd0s1 is my first slice, why isn't it named wd0s0? > > wd0s0 == wd0 > > wd0s0a == wd0a > > > I somehow doubt that. Considering wd0s* goes from 1 to 4 inclusively, I > would tend to believe the first slice is wd0s1. The above is incorrect, he misunderstood your question. > > > 4. If I want to use /dev/wd0s2 as a raw slice for reading > > > and writing, what are the steps to follow? > > You can't write several blocks near /dev/wd0s2 beginning. > > Use /dev/wd0 with proper address > > > That is rather risky. Wouldn't it be safer to have a device name I could > dedicate to some purpose. In such a case, I could chown the device to an > appropriate username and group. Furthermore, I could avoid the unfortunate > mistake of overwriting my current FreeBSD fs in case I get the addresses > wrong. He is incorrect. You can use /dev/wd0s2 any way you want, as long as you have nothing of value there. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net "I demand that my picture show a handsome face, even if it doesn't look like me." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 9: 2:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 9ADB737B50C; Mon, 18 Sep 2000 09:02:09 -0700 (PDT) Received: from server.wes.mee.com (p3EE2AA58.dip.t-dialin.net [62.226.170.88]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id SAA15672; Mon, 18 Sep 2000 18:02:07 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id e8IFuOj06919; Mon, 18 Sep 2000 17:56:24 +0200 (CEST) Date: Mon, 18 Sep 2000 17:56:23 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: freebsd-hackers@freebsd.org Cc: freebsd-bugs@freebsd.org Subject: Bug: NATD Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, CCd to freebsd-bugs (I think it exists, doesn't it?!) In every FreeBSD Snapshot I tested (20000214, 20000521, 20000905) I always got problems regarding Natd. I have a very simple /etc/rc.firewall: /sbin/ipfw -f flush /sbin/ipfw add divert natd all from any to any via isp0 /sbin/ipfw add pass all from any to any And in my Kernel I have enabled IP_DIVERT and IP_FIREWALL_DEFAULT_TO_ACCEPT or however this option is called. Now my Problem: Sometimes, when I activate natd, it won't let me through. But sometimes everything works fine, sometimes it just stopps letting me through at a certain point of time... Very randomized. I think it's a very hard BUG, and it's really taking my last nerv. Are there any similar programs to natd, which I can use instead? I just want to have a working firewall.... MTIA -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 10:22:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 0778837B424 for ; Mon, 18 Sep 2000 10:22:50 -0700 (PDT) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id OAA86837; Mon, 18 Sep 2000 14:24:46 -0300 (ART) From: Fernando Schapachnik Message-Id: <200009181724.OAA86837@ns1.via-net-works.net.ar> Subject: Weird locking issue with makemap, sendmail on a 4.1-R SMP. To: hackers@freebsd.org Date: Mon, 18 Sep 2000 14:24:46 -0300 (ART) Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello: I'm resending this mail here as nobody in -questions seems to have a clue about what is going on. Any ideas? Thanks for your time. ----- Forwarded message from Fernando Schapachnik ----- Subject: Weird locking issue with makemap, sendmail on a 4.1-R SMP. To: questions@freebsd.org Date: Fri, 15 Sep 2000 15:07:11 -0300 (ART) Hello: I'm having a weird problem with my SMP 4.1-RELEASE mail server: CPU: Pentium III/Pentium III Xeon/Celeron (731.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536854528 (524272K bytes) First thing I noticed was that newaliases was getting hung. Further investigation showed the problem was ~majordom/aliases.majordom.db Running makemap hash ~majordom/aliases.majordom < ~majordom/aliases.majordom hunged also. A fstat showed only sendmail has this file open, and for reading only. A ktrace shows: [...] 87185 makemap CALL open(0xbfbff658,0x622,0x1a4) 87185 makemap NAMI "aliases.majordomo.db" [a lot of time... sent kill] 87185 makemap PSIG SIGINT SIG_DFL aliases.majordom.db ends with 0 bytes. Removing the file solves the problem. Sometimes same thing happens with virtusertable and similar aliases-related files. Today the same happened with access.db. Lsof showed sendmail 52975 root 7rR VREG 109,196608 0 35980 /etc/mail/access.db which means sendmail has the whole file locked for reading. Doing a ps -axl shows lockfs state and a sleeping process (waiting for a lock, I guess). Any ideas? Thanks in advance! ----- End of forwarded message from Fernando Schapachnik ----- Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 10:42: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 117C937B422 for ; Mon, 18 Sep 2000 10:41:56 -0700 (PDT) Received: (qmail 531 invoked by uid 501); 18 Sep 2000 17:42:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Sep 2000 17:42:06 -0000 Date: Mon, 18 Sep 2000 10:42:06 -0700 (PDT) From: Peter Avalos To: Christopher Stein Cc: hackers@freebsd.org Subject: Re: 4.1 make world and cvsup release field 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, 18 Sep 2000, Christopher Stein wrote: > > Hello, I don't wish to jump all the way forward to -CURRENT, but would > like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0 > for kqueue() and fxp PEX support). > > How do I specify 4.1 in the release field of my supfile? > If you want 4.1-STABLE you need this: *default release=cvs tag=RELENG_4 On another note, this type of thing would better be suited for freebsd-questions. Peter Avalos TheShell.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:12:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5EE4837B505; Mon, 18 Sep 2000 11:12:11 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA02532; Mon, 18 Sep 2000 11:12:11 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 18 Sep 2000 11:12:11 -0700 (PDT) From: Kris Kennaway To: Christopher Stein Cc: hackers@freebsd.org Subject: Re: 4.1 make world and cvsup release field 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, 18 Sep 2000, Christopher Stein wrote: > I would like to do this via cvsup and `make world'. > My understanding is that `make world' is just buildworld followed > by installworld, each a single monolithic step. Hhmm.. it seems > to me that some build stages will not work without > some other elements being installed. For example, my current modified > 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 > vs. 2.10). So how can a `make world' work in a monolithic build then > install sequence? See the /usr/src/UPDATING file after updating your source and be sure to follow the directions precisely. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:27:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 0F83637B422; Mon, 18 Sep 2000 11:27:05 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13b5cq-000K0n-00; Mon, 18 Sep 2000 20:26:44 +0200 Date: Mon, 18 Sep 2000 20:26:44 +0200 From: Neil Blakey-Milner To: "Daniel C. Sobral" Cc: Marc Tardif , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention Message-ID: <20000918202644.A76911@mithrandr.moria.org> References: <39C63ACD.441658CC@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39C63ACD.441658CC@newsguy.com>; from dcs@newsguy.com on Tue, Sep 19, 2000 at 12:54:53AM +0900 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 2000-09-19 (00:54), Daniel C. Sobral wrote: > > Lastly, where else could I have found this information other > > than asking on the FreeBSD mailing list? > > Beats me, but it _should_ be in the handbook. A basic device naming overview, as well as some simple disk layout information, is available in http://www.FreeBSD.org/handbook/disks.html Of course, noone reads documentation, so I don't know why I bother. (: Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:36:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C87E437B423 for ; Mon, 18 Sep 2000 11:36:30 -0700 (PDT) Received: from jade (jade.cs.binghamton.edu [128.226.140.161]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id OAA22570 for ; Mon, 18 Sep 2000 14:36:27 -0400 (EDT) Date: Mon, 18 Sep 2000 14:36:08 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@jade To: freebsd-hackers@freebsd.org Subject: How to time a system call Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend asks me what will happen if more than one process trying to read the stdin at the same time. There is no way to guarantee that any particular keyboard input will be accepted by a particular process. Since a system call is atomic, this makes me wonder how long it takes to do a system call, like read(), on a 500Mhz PC? How to time it? I later write a program that forks. So that two processes tries to read the stdin at the same time. I use read() to read one character at a time. Each process read 1000 characters and write what they read to a file. I use I/O redirect to let them read from the same file instead of keyboard. I find out that one process always call 1000 read()s before the second has a chance to call read(). I hope someone can give me a clue on how this is happening. Maybe the scheduling quantum (100ms?) is just enough for doing 1000 read() system calls. Is there any easy way to time a system call (perhaps with minor modifications of the kernel)? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:39:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 2E06737B423; Mon, 18 Sep 2000 11:39:17 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id OAA03654; Mon, 18 Sep 2000 14:42:28 -0400 Date: Mon, 18 Sep 2000 14:42:28 -0400 (EDT) From: Marc Tardif To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention In-Reply-To: <39C63ACD.441658CC@newsguy.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 [ snip ] > > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 > > doesn't span to the end of disk: > > 4. If I want to use /dev/wd0s2 as a raw slice for reading > > and writing, what are the steps to follow? > > None. You just use it. > This is what I have in fdisk (from /stand/sysinstall): Offset Size End Name PType Desc Subtype Flags 0 63 62 - 6 unused 0 63 1937565 1937627 wd0s1 3 freebsd 165 C 1937628 191268 2128895 - 6 unused 0 At this point, the second slice does not exist yet so I can't use it. For problems in defining a slice, see next question. > > 4a. Do I need to format the partition as any type? If so > > is there a recommended type (perhaps one which won't > > be recognised by the bootloader would be preferable)? > > No, you don't need to format it, nor do you need to worry about it's > type. Just make sure the slice does exist. > When I define a slice, I need to specify what fdisk (from sysinstall) calls a "partition type". In the case of my FreeBSD slice, I selected "165". In the case of a slice I will use for raw io, is there any reason I should use one partition type rather than another? > > 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a > > for reading and writing (of course, this is assuming > > block i/o of multiples of 512 bytes)? > > Nope, using raw devices is almost always wrong, and we even got rid of > raw device in latter versions of FreeBSD. A "raw" device is an > _unbuffered_ device. It has nothing to do with formats or types. > Got rid of raw devices in later versions of FreeBSD? What if I purposely want unbuffered io? There are instances, such as with databases, where the buffer cache is useless. I understand that in many cases, databases using the raw device practically reinvent the wheel by programming what is effectively another filesystem (which, by the way, is most likely slower than bsd's ffs). Even Oracle, which used to be one of the "you gotta use a raw partition if you want any speed at all" type, has moved into the "use a normal partitoin or regular file unless you do things like sharing a RAID between two hosts" camp. Yet, there are still isolated cases where raw io can be beneficial. What should I do for raw io in later versions of FreeBSD? > Anyway, you should be using /dev/wd0s2. Unless you partition the slice, > and want to use the "a" partition. > If I will be storing a few tables in /dev/wd0s2 of a predefined block aligned size, would it be advisable to use the 165 partition type for /dev/wd0s2 and create labels which will effectively become my tables? If this actually makes sense (fat chance), is there any reason I should be creating mount points? Or, if it would be better to define the labels as swap (assuming I already have a swap label in /dev/wd0s1), could FreeBSD inadvertently use those swap partitions and overwrite my data? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:51: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C93137B423; Mon, 18 Sep 2000 11:50:57 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA91503; Mon, 18 Sep 2000 12:50:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA32922; Mon, 18 Sep 2000 12:50:43 -0600 (MDT) Message-Id: <200009181850.MAA32922@harmony.village.org> To: Takanori Watanabe Subject: Re: PEACE - Portable Executable win32 API Compatible Environment. Cc: freebsd-hackers@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Sep 2000 15:22:38 +0900." <200009180622.PAA49090@shidahara1.planet.sci.kobe-u.ac.jp> References: <200009180622.PAA49090@shidahara1.planet.sci.kobe-u.ac.jp> Date: Mon, 18 Sep 2000 12:50:43 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009180622.PAA49090@shidahara1.planet.sci.kobe-u.ac.jp> Takanori Watanabe writes: : I ported kernel part of PEACE from NetBSD.(That is in sys/compat/pecoff/*). Cool. Way Cool. : - It requires following changes to sys/imgact.h and kern/kern_exec.c to : be able to change size of memory area to hold dynamic linker argument : from executable image loader. Woof. I think this is reasonable, but will let others more qualified talk about it. I think that arch@ should likely review it if there aren't enough people doing so in emulation@. It looks good to me, but my knowledge in this area is limited and I think others with a better understanding might be able to give a better review. : - Merge the patch to precede .(Who should I ask about it?) Once the patch is reviewed, you should be able to commit the change yourself, since you have commit privs. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:56:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by hub.freebsd.org (Postfix) with ESMTP id 8D69937B424; Mon, 18 Sep 2000 11:56:22 -0700 (PDT) Received: from bouvier.eecs.harvard.edu (IDENT:root@bouvier.eecs.harvard.edu [140.247.60.220]) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e8IIkGw02120; Mon, 18 Sep 2000 14:46:16 -0400 (EDT) Received: from localhost (stein@localhost) by bouvier.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id OAA18146; Mon, 18 Sep 2000 14:45:06 -0400 X-Authentication-Warning: bouvier.eecs.harvard.edu: stein owned process doing -bs Date: Mon, 18 Sep 2000 14:45:06 -0400 (EDT) From: Christopher Stein To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: 4.1 make world and cvsup release field 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 Every message I see in the archives on these points is very simple: "See /usr/src/UPDATING" Unfortunately, my system has no /usr/src/UPDATING. I have decided to go with a full net reinstall (rather than use cvsup) to take me from 3.3 to 4.1. I look forward to reading UPDATING when it lands on my system. Should make great bedtime reading. thanks -Chris On Mon, 18 Sep 2000, Kris Kennaway wrote: > On Mon, 18 Sep 2000, Christopher Stein wrote: > > > I would like to do this via cvsup and `make world'. > > My understanding is that `make world' is just buildworld followed > > by installworld, each a single monolithic step. Hhmm.. it seems > > to me that some build stages will not work without > > some other elements being installed. For example, my current modified > > 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 > > vs. 2.10). So how can a `make world' work in a monolithic build then > > install sequence? > > See the /usr/src/UPDATING file after updating your source and be sure to > follow the directions precisely. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 11:59:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ellipse.mcs.drexel.edu (ellipse.mcs.drexel.edu [129.25.7.190]) by hub.freebsd.org (Postfix) with ESMTP id 3E15D37B423 for ; Mon, 18 Sep 2000 11:59:16 -0700 (PDT) Received: from localhost (cosine@localhost) by ellipse.mcs.drexel.edu (8.9.3/8.9.3) with ESMTP id OAA50900 for ; Mon, 18 Sep 2000 14:52:14 -0400 (EDT) (envelope-from cosine@ellipse.mcs.drexel.edu) Date: Mon, 18 Sep 2000 14:52:14 -0400 (EDT) From: Patrick Alken To: freebsd-hackers@freebsd.org Subject: ptrace help Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2049834737-969303134=:50782" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2049834737-969303134=:50782 Content-Type: TEXT/PLAIN; charset=US-ASCII I am experiencing problems with ptrace() under FreeBSD. I made a simple example program to demonstrate. All it does is fork a child process to execl() a simple "hello world" program and ptrace() it with PT_CONTINUE. The first time around, everything is as it should be - the program is executed and traced perfectly. However, when I attempt to repeat the whole process, first by forking a completely new child to execute the helloworld program again, I start getting ptrace() errors such as "Operation not permitted" and "Device busy". Now the weird thing is, after the first trace, the program terminates normally, and I print out the pid of the child process which should no longer be running at this point. ptrace(PT_KILL) verifies this by returning "No such process". However, during the pause between the first and second ptrace, if I do a ps and search for the pid, it shows up in memory as running in the background, although ptrace(PT_KILL) claims it does not exist. Then my sample program attempts to trace the same helloworld program again, and gets "Operation not permitted" - even though an entirely new child is fork()'d with an entirely new pid - so it should have absolutely no connection at all to the first trace. Does anyone know why I can't ptrace() the same helloworld program a second time? I have attached my sample ptrace() program to this message. Thanks in advance for any help Patrick Alken --0-2049834737-969303134=:50782 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="myptrace.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="myptrace.c" LyoNCiAqIFRvIHJ1biB0aGlzLCBtYWtlIGEgcHJvZy5jIHdoaWNoIGNvbnRh aW5zOg0KICogaW50IG1haW4oKSB7IHByaW50ZigiaGVsbG8gd29ybGRcbiIp OyB9DQogKiBhbmQgY29tcGlsZSBpdCBpbnRvIHRoZSBmaWxlICJwcm9nIi4N CiAqDQogKiBUaGVuLCBzaW1wbHk6IGdjYyAtbyBteXB0cmFjZSBteXB0cmFj ZS5jDQogKiBhbmQgLi9teXB0cmFjZQ0KICovDQoNCiNpbmNsdWRlIDxzdGRp by5oPg0KI2luY2x1ZGUgPHN5cy90eXBlcy5oPg0KI2luY2x1ZGUgPHN5cy9w dHJhY2UuaD4NCiNpbmNsdWRlIDxlcnJuby5oPg0KI2luY2x1ZGUgPHN5cy93 YWl0Lmg+DQojaW5jbHVkZSA8bWFjaGluZS9yZWcuaD4NCiNpbmNsdWRlIDx1 bmlzdGQuaD4NCiNpbmNsdWRlIDxzdHJpbmcuaD4NCg0KLyoNCkRvVHJhY2Uo KSAtIGJlZ2luIHRvIHRyYWNlIGEgcHJvY2Vzcw0KKi8NCg0KaW50DQpEb1Ry YWNlKCkNCg0Kew0KICBpbnQgcGlkOyAvKiBjaGlsZCBwaWQgKi8NCiAgaW50 IHdhaXR2YWw7DQoJc3RydWN0IHJlZyByZWdzOw0KDQogIHBpZCA9IGZvcmso KTsNCiAgc3dpdGNoIChwaWQpDQogIHsNCiAgICBjYXNlIC0xOg0KICAgIHsN CiAgICAgIHBlcnJvcigiZm9yayIpOw0KICAgICAgYnJlYWs7DQogICAgfQ0K DQogICAgLyoNCiAgICAgKiBDaGlsZA0KICAgICAqLw0KICAgIGNhc2UgMDoN CiAgICB7DQogICAgICAvKg0KICAgICAgICogQWxsb3cgcGFyZW50IHRvIHRy YWNlIHRoaXMgY2hpbGQgcHJvY2Vzcw0KICAgICAgICovDQogICAgICBwdHJh Y2UoUFRfVFJBQ0VfTUUsIDAsIDAsIDApOw0KICAgICAgDQogICAgICAvKg0K ICAgICAgICogRXhlY3V0ZSBwcm9ncmFtIHRvIGJlIGRlYnVnZ2VkIGFuZCBj YXVzZSBjaGlsZCB0bw0KICAgICAgICogc2VuZCBhIHNpZ25hbCB0byBwYXJl bnQNCiAgICAgICAqLw0KICAgICAgZXhlY2woIi4vcHJvZyIsICJwcm9nIiwg TlVMTCk7DQoNCiAgICAgIGV4aXQoMCk7DQogICAgfQ0KDQogICAgLyoNCiAg ICAgKiBQYXJlbnQNCiAgICAgKi8NCiAgICBkZWZhdWx0Og0KICAgIHsNCiAg ICAgIGludCBwcmV0Ow0KDQogICAgICAvKiANCiAgICAgICAqIFdhaXQgZm9y IGNoaWxkIHRvIHN0b3AgKGV4ZWNsKQ0KICAgICAgICovDQogICAgICB3YWl0 KCZ3YWl0dmFsKTsNCg0KICAgICAgcHJpbnRmKCJ3YWl0dmFsID0gJWRcbiIs IHdhaXR2YWwpOw0KDQogICAgICAvKg0KCQkJICogQ29udGludWUgZXhlY3Rp b24gb2YgcHJvY2Vzcw0KCQkJICovDQoJCQlwcmV0ID0gcHRyYWNlKFBUX0NP TlRJTlVFLCBwaWQsIChjYWRkcl90KSAxLCAwKTsNCgkJCWlmIChwcmV0ICE9 IDApDQoJCQl7DQoJCQkJLyoNCgkJCQkgKiBUaGlzIGlzIHdoZXJlIGl0IGZh aWxzIHRoZSBzZWNvbmQgdGltZSB3aXRoIGFuDQoJCQkJICogZXJybm8gb2Yg MSAoRVBFUk0pLCBldmVuIHRob3VnaCB3ZSBhcmUgdHJhY2luZw0KCQkJCSAq IGEgY29tcGxldGVseSBuZXcgcGlkLg0KCQkJCSAqLw0KCQkJCXBlcnJvcigi cHRyYWNlIik7DQoJCQl9DQoNCiAgICAgIHdhaXQoJndhaXR2YWwpOw0KDQoJ CQlwcmV0ID0gcHRyYWNlKFBUX0tJTEwsIHBpZCwgMCwgMCk7DQoJCQlpZiAo cHJldCA9PSAwKQ0KCQkJew0KCQkJCXByaW50ZigiS2lsbCBzdWNjZXNzZnVs XG4iKTsNCgkJCQl3YWl0KCZ3YWl0dmFsKTsNCgkJCX0NCgkJCWVsc2UNCgkJ CQlwcmludGYoIktpbGwgdW5zdWNjZXNzZnVsLCBlcnJubyA9ICVzXG4iLCBz dHJlcnJvcihlcnJubykpOw0KICAgIH0NCiAgfQ0KDQoJcmV0dXJuIChwaWQp Ow0KfSAvKiBEb1RyYWNlKCkgKi8NCg0KaW50DQptYWluKCkNCg0Kew0KICBp bnQgcGlkOw0KCWNoYXIgYnVmWzUxMl07DQoNCiAgLyoNCgkgKiBUcmFjZSB0 aHJvdWdoIHRoZSBwcm9jZXNzDQoJICovDQoJcGlkID0gRG9UcmFjZSgpOw0K CXByaW50ZigiUGlkMSA9ICVkXG4iLCBwaWQpOw0KDQoJZmdldHMoYnVmLCA1 MTIsIHN0ZGluKTsNCg0KCS8qDQoJICogVHJhY2UgdGhyb3VnaCBhZ2FpbiAo dGhpcyBpcyB3aGVyZSBpdCBmYWlscykNCgkgKi8NCglwaWQgPSBEb1RyYWNl KCk7DQoJcHJpbnRmKCJQaWQyID0gJWRcbiIsIHBpZCk7DQoNCglyZXR1cm4g MDsNCn0NCg== --0-2049834737-969303134=:50782-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 12:10:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id D9C4037B424; Mon, 18 Sep 2000 12:10:27 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13b6Ik-000KAS-00; Mon, 18 Sep 2000 21:10:02 +0200 Date: Mon, 18 Sep 2000 21:10:02 +0200 From: Neil Blakey-Milner To: Marc Tardif Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention Message-ID: <20000918211002.A77486@mithrandr.moria.org> References: <39C63ACD.441658CC@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from intmktg@CAM.ORG on Mon, Sep 18, 2000 at 02:42:28PM -0400 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 2000-09-18 (14:42), Marc Tardif wrote: > > > 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a > > > for reading and writing (of course, this is assuming > > > block i/o of multiples of 512 bytes)? > > > > Nope, using raw devices is almost always wrong, and we even got rid of > > raw device in latter versions of FreeBSD. A "raw" device is an > > _unbuffered_ device. It has nothing to do with formats or types. > > > Got rid of raw devices in later versions of FreeBSD? What if I purposely > want unbuffered io? There are instances, such as with databases, where the > buffer cache is useless. > > I understand that in many cases, databases using the raw device > practically reinvent the wheel by programming what is effectively another > filesystem (which, by the way, is most likely slower than bsd's ffs). Even > Oracle, which used to be one of the "you gotta use a raw partition if you > want any speed at all" type, has moved into the "use a normal partitoin or > regular file unless you do things like sharing a RAID between two hosts" > camp. > > Yet, there are still isolated cases where raw io can be beneficial. What > should I do for raw io in later versions of FreeBSD? We didn't get rid of raw devices. We got rid of block devices, and kept character devices. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 12:23:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8243437B424; Mon, 18 Sep 2000 12:23:13 -0700 (PDT) Received: from newsguy.com (p44-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.109]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id EAA04552; Tue, 19 Sep 2000 04:23:07 +0900 (JST) Message-ID: <39C66B69.96E57728@newsguy.com> Date: Tue, 19 Sep 2000 04:22:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif wrote: > > This is what I have in fdisk (from /stand/sysinstall): > Offset Size End Name PType Desc Subtype Flags > 0 63 62 - 6 unused 0 > 63 1937565 1937627 wd0s1 3 freebsd 165 C > 1937628 191268 2128895 - 6 unused 0 > > At this point, the second slice does not exist yet so I can't use it. For > problems in defining a slice, see next question. Really? I wouldn't expect FreeBSD to worry about the type being "unused". > When I define a slice, I need to specify what fdisk (from sysinstall) > calls a "partition type". In the case of my FreeBSD slice, I selected > "165". In the case of a slice I will use for raw io, is there any reason I > should use one partition type rather than another? A type serves to, well, check the type. :-) If you don't care about the type, nothing else will... in theory. I certainly can't see open("/dev/ad0s2", flags) checking the type for anything. Perhaps, it will, indeed, fail for "unused". But nothing more than that. Other things do worry about type, of course. boot0 will identify slices to be booted by their type. loader will list a slice's type, and try to find the disklabel for FreeBSD slices. > Got rid of raw devices in later versions of FreeBSD? What if I purposely > want unbuffered io? There are instances, such as with databases, where the > buffer cache is useless. Oh, sorry, I got things confused. You should verify the hour at which a message is replied for reliability... ;-) Anyway, raw devices are character devices, unbuffered. Then, there were the "block" devices, which were buffered. We got rid of the _block_ devices, not the raw devices. But, as we no longer have two types, we no longer prefix them with "r". > I understand that in many cases, databases using the raw device > practically reinvent the wheel by programming what is effectively another > filesystem (which, by the way, is most likely slower than bsd's ffs). Even > Oracle, which used to be one of the "you gotta use a raw partition if you > want any speed at all" type, has moved into the "use a normal partitoin or > regular file unless you do things like sharing a RAID between two hosts" > camp. > > Yet, there are still isolated cases where raw io can be beneficial. What > should I do for raw io in later versions of FreeBSD? Actually, there is little benefit in buffered device access. Buffering is better handled elsewhere and by other means. > > Anyway, you should be using /dev/wd0s2. Unless you partition the slice, > > and want to use the "a" partition. > > > If I will be storing a few tables in /dev/wd0s2 of a predefined block > aligned size, would it be advisable to use the 165 partition type for > /dev/wd0s2 and create labels which will effectively become my tables? If > this actually makes sense (fat chance), is there any reason I should be > creating mount points? Or, if it would be better to define the labels as > swap (assuming I already have a swap label in /dev/wd0s1), could FreeBSD > inadvertently use those swap partitions and overwrite my data? Well, you could, indeed, use slice type 165, and partition it. We are limited, though, to 6 partitions. c must always be the whole slice (minus the disklabel :), and d is better left unused for historical reasons. OTOH, using a partition (try to avoid using c -- if you want the whole slice, create a partition with the same data as c) would be cleaner, from the point of view of various utilities, than using a slice. You do lose a few sectors. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net "I demand that my picture show a handsome face, even if it doesn't look like me." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 12:43: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mazurek.man.lodz.pl (mazurek.man.lodz.pl [212.51.192.15]) by hub.freebsd.org (Postfix) with ESMTP id D49F437B423 for ; Mon, 18 Sep 2000 12:43:01 -0700 (PDT) Received: from adas (pb210.lodz.ppp.tpnet.pl [212.160.29.210]) by mazurek.man.lodz.pl (8.9.3/8.9.3) with ESMTP id VAA32637; Mon, 18 Sep 2000 21:42:49 +0200 From: "Piotr Sroczynski" To: Devin Butterfield Date: Mon, 18 Sep 2000 21:44:26 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: PnP & 4.1 Release Cc: hackers@FreeBSD.ORG Message-ID: <39C68CBA.21143.330132@localhost> In-reply-to: <39C53058.E105C2B7@db.wireless.net> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it possible to stop any PnP operation (checking, seting) during > > boot? > > > > Can I ask specifically what problems you're having or what you are > trying to accomplish? I want install 4.1 RELEASE on my old 486's, with ISA bus only and without bios PnP support. First has SMC EliteULTRA 8416 software selectable PnP operation - ethernet Second has Emerging Technology ET-25 (not PnP) - synchronous interface Problems (with 4.1 only, 2.2.7 works perfectly): Ad. 1 - SMC's are "unknown" for 4.1 Setting PnP "on" or "off" has no visible effect. All my card eeprom settings (port,int,mem,etc) are changed after start-up. Ad. 2 - The system hangs on start-up. May be because during PnP scanning, something was written to register. I think that If I could stop PnP scanning and setting, my problems will be solved. Best Regards, Piotr Sroczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 12:58:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (Postfix) with ESMTP id 0559A37B423; Mon, 18 Sep 2000 12:58:23 -0700 (PDT) Received: from death.scl.ameslab.gov ([147.155.137.56] helo=ameslab.gov) by mailhub.scl.ameslab.gov with esmtp (Exim 3.02 #1) id 13b73U-000JL1-00; Mon, 18 Sep 2000 14:58:20 -0500 Message-ID: <39C673DB.135A25FC@ameslab.gov> Date: Mon, 18 Sep 2000 14:58:19 -0500 From: Chris Csanady X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en, ru, ja, ko MIME-Version: 1.0 To: Mike Smith Cc: Danny Braniss , freebsd-hackers@freebsd.org Subject: Re: diskless workstation References: <200009111926.MAA13990@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > ok, once i compiled a kernel with options BOOTP things got better ;-) > > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) > > but after it re-configures the ethernet, the ethernet stops working! > > > > ponters anyone? > > You can't run dhclient (DHCP in any of the ifconfig lines in /etc/ > rc.conf) if you have mounted / via NFS. > > If you're running -current or a very recent -stable, remove the 'BOOTP' > options. The loader now passes all the DHCP information into the kernel. > Then leave the interface configuration alone... Has this actually been merged to -stable yet? I can't find anything that actually reads the boot.nfsroot.* loader variables. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 13: 4:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 843D137B422; Mon, 18 Sep 2000 13:04:45 -0700 (PDT) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.9.3/8.8.8) with ESMTP id QAA26343; Mon, 18 Sep 2000 16:03:14 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Mon, 18 Sep 2000 16:03:14 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Bruce Evans Cc: Ben Smithurst , Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! 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, 19 Sep 2000, Bruce Evans wrote: > On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote: > > > I recently ran into revelant problem with /dev/stdout, while > > working on some software under linux that expected /dev/stdout as an > > argument instead of using stdout. > > > > Using the device file breaks, if the process is suid to a non-root > > user. This is because it cannot open /dev/stdout, which is owned by your > > UID and not the EUID of the process to which the device was passed. My > > solution was to add the "-" hack and use the existing open descriptor. > > Um, open on fdesc devices doesn't check either uid. It just checks > the access mode. > > Perhaps the software expected /dev/stdout to for read-write like a > tty would be. Then opening /dev/stdout would fail for normal shell > output redirection which only opens for writing. No, it wasn't a RW/W issue. I dug a little deeper. It looks like the BSD implmentation of /dev/stdout is smarter than the linux version. Linux's is a symlink into /proc and the device ownership is determined by the UID of the invoking user. I guess I wouldn't have have had a problem under BSD. no suprise here. 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 Mon Sep 18 13: 6:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 78D1537B423; Mon, 18 Sep 2000 13:06:10 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13b7B1-0003lu-00; Mon, 18 Sep 2000 23:06:07 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13b7B0-0002dP-00; Mon, 18 Sep 2000 23:06:06 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Chris Csanady Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Mon, 18 Sep 2000 14:58:19 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2000 23:06:06 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39C673DB.135A25FC@ameslab.gov>you write: }Mike Smith wrote: }> }> > ok, once i compiled a kernel with options BOOTP things got better ;-) }> > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) }> > but after it re-configures the ethernet, the ethernet stops working! }> > }> > ponters anyone? }> }> You can't run dhclient (DHCP in any of the ifconfig lines in /etc/ }> rc.conf) if you have mounted / via NFS. }> }> If you're running -current or a very recent -stable, remove the 'BOOTP' }> options. The loader now passes all the DHCP information into the kernel. }> Then leave the interface configuration alone... } }Has this actually been merged to -stable yet? I can't find anything that }actually reads the boot.nfsroot.* loader variables. } no, last time i checked it's in SNPNG or something, but not stable. i tried some retrofitting (made the changes to autoconfig.c) got past mountroot but got stopped at 'nfs send error 65' :-( danny }Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 13:29: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id ED7D637B43E; Mon, 18 Sep 2000 13:28:57 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id QAA04450; Mon, 18 Sep 2000 16:31:03 -0400 Date: Mon, 18 Sep 2000 16:31:03 -0400 (EDT) From: Marc Tardif To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention In-Reply-To: <39C66B69.96E57728@newsguy.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 > > This is what I have in fdisk (from /stand/sysinstall): > > Offset Size End Name PType Desc Subtype Flags > > 0 63 62 - 6 unused 0 > > 63 1937565 1937627 wd0s1 3 freebsd 165 C > > 1937628 191268 2128895 - 6 unused 0 > > > > At this point, the second slice does not exist yet so I can't use it. For > > problems in defining a slice, see next question. > > Really? I wouldn't expect FreeBSD to worry about the type being > "unused". > If I try the following command as root, nothing is output: # hd /dev/rwd0s2 | head Also, I tried writing a little c program to mmap(2) and, if that fails, read(2) the device. Unfortunately, that didn't work either. It seems I do actually need to define the slice as some type. The reason is maybe to define the limits of the device. Therefore, the actual type is of little importance but knowing where the device starts and stops could be important for some reason. To make the system happy, I then defined the slice as "partition type" 0, but fdisk still displayed "unused". Maybe some obscur type which doesn't appear in the bootloader would be preferable, if I find one... If this kind of information is relevant to the mailing list, I'll post what I find. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 13:35: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9167E37B424; Mon, 18 Sep 2000 13:34:59 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA09131; Mon, 18 Sep 2000 22:34:51 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Takanori Watanabe Cc: freebsd-hackers@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG Subject: Re: PEACE - Portable Executable win32 API Compatible Environment. References: <200009180622.PAA49090@shidahara1.planet.sci.kobe-u.ac.jp> From: Dag-Erling Smorgrav Date: 18 Sep 2000 22:34:50 +0200 In-Reply-To: Takanori Watanabe's message of "Mon, 18 Sep 2000 15:22:38 +0900" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Takanori Watanabe writes: > PEACE is Win32 API Compatible environment for (Originally) NetBSD. > It consist of three parts: > Kernel part to load PE format executable onto process memory space. > Dynamic Linker to link with PE format DLL. > Libraries to translate Win32 API call to NetBSD native system call. What is the difference between PEACE and WINE? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 14: 7:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 23AF137B422 for ; Mon, 18 Sep 2000 14:07:14 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA04182; Mon, 18 Sep 2000 14:04:50 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA15154; Mon, 18 Sep 2000 14:04:49 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 18 Sep 2000 14:04:49 -0700 (PDT) Message-Id: <200009182104.OAA15154@vashon.polstra.com> To: hackers@freebsd.org Cc: fjoe@iclub.nsu.ru Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > hi, there! > > On Fri, 15 Sep 2000, John Polstra wrote: > > > Here is another possibility: we could call _thread_init() from > > crt1.o. The patch (untested) is below. It calls _thread_init() if > > and only if that symbol is defined -- i.e., libc_r is linked in. > > What do you think about this solution? > > seems ok to me but can we do this from `do_ctors' or `_init' -- they are > located in common/ That's a good point. But I would rather not do it from crtbegin since there is a good chance that we'll eventually be using the GCC version of that. However, I have some plans to unify the versions of crt1.c so that it can be moved into "common". The alpha and sparc versions are identical, and they are not very much different from the i386 version. I think a couple of platform-specific #defines or inline functions could handle all of the architecture dependencies. Note, I _don't_ want to do it using "#ifdef __i386__", etc., because that doesn't scale well for a lot of platforms and it makes the code hard to read. Instead I would prefer to #include a small platform-specific header file which defines macros and inline functions appropriately. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 14:18:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 0ECAD37B423; Mon, 18 Sep 2000 14:18:15 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id OAA15595; Mon, 18 Sep 2000 14:23:10 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009182123.OAA15595@troutmask.apl.washington.edu> Subject: Re: PEACE - Portable Executable win32 API Compatible Environment. In-Reply-To: from Dag-Erling Smorgrav at "Sep 18, 2000 10:34:50 pm" To: Dag-Erling Smorgrav Date: Mon, 18 Sep 2000 14:23:10 -0700 (PDT) Cc: Takanori Watanabe , freebsd-hackers@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 Dag-Erling Smorgrav wrote: > Takanori Watanabe writes: > > PEACE is Win32 API Compatible environment for (Originally) NetBSD. > > It consist of three parts: > > Kernel part to load PE format executable onto process memory space. > > Dynamic Linker to link with PE format DLL. > > Libraries to translate Win32 API call to NetBSD native system call. > > What is the difference between PEACE and WINE? > Wine is actually trying to completely replace MS windows (include win3.1, win95, win98, and winnt). SO, wine includes code for the old 16 bit API(s) and it is trying to replace all on the MS dll's with built-in dll. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 14:26:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id C0B7D37B422; Mon, 18 Sep 2000 14:26:50 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA27523; Tue, 19 Sep 2000 01:26:42 +0400 (MSD) Message-Id: <200009182126.BAA27523@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: from "Marc Tardif" at "Sep 18, 0 04:31:03 pm" To: intmktg@CAM.ORG (Marc Tardif) Date: Tue, 19 Sep 2000 01:26:41 +0400 (MSD) Cc: dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif writes: > > > This is what I have in fdisk (from /stand/sysinstall): > > > Offset Size End Name PType Desc Subtype Flags > > > 0 63 62 - 6 unused 0 > > > 63 1937565 1937627 wd0s1 3 freebsd 165 C > > > 1937628 191268 2128895 - 6 unused 0 > > > > > > At this point, the second slice does not exist yet so I can't use it. For > > > problems in defining a slice, see next question. > > > > Really? I wouldn't expect FreeBSD to worry about the type being > > "unused". > > > If I try the following command as root, nothing is output: > # hd /dev/rwd0s2 | head > > Also, I tried writing a little c program to mmap(2) and, if that fails, > read(2) the device. Unfortunately, that didn't work either. It seems I do > actually need to define the slice as some type. The reason is maybe to > define the limits of the device. Therefore, the actual type is of little > importance but knowing where the device starts and stops could be > important for some reason. To make the system happy, I then defined the > slice as "partition type" 0, but fdisk still displayed "unused". Maybe > some obscur type which doesn't appear in the bootloader would be > preferable, if I find one... If this kind of information is relevant to > the mailing list, I'll post what I find. Use fdisk. See at begin and size of slices - nothing else affect until you boot or have another OS on your computer. in sysinstal last string mean that entryes for wd0s2, wd0s3 and wd0s4 are all size 0. So you can read EOF only. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 14:41: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C888137B423; Mon, 18 Sep 2000 14:41:05 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA47631; Mon, 18 Sep 2000 14:41:05 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 18 Sep 2000 14:41:05 -0700 (PDT) From: Kris Kennaway To: Christopher Stein Cc: hackers@FreeBSD.ORG Subject: Re: 4.1 make world and cvsup release field 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, 18 Sep 2000, Christopher Stein wrote: > Every message I see in the archives on these points is very simple: > > "See /usr/src/UPDATING" > > Unfortunately, my system has no /usr/src/UPDATING. Reread what I said: > See the /usr/src/UPDATING file after updating your source and be sure to > follow the directions precisely. ^^^^^^^^^^^^^^^^^^^^^^^^^^ > I have decided to go with a full net reinstall (rather than use cvsup) to > take me from 3.3 to 4.1. Cool. Probably easier all around. > I look forward to reading UPDATING when it lands on my system. Should make > great bedtime reading. :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 15:31:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 369CF37B423 for ; Mon, 18 Sep 2000 15:31:34 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13b9Rl-0002jj-00; Tue, 19 Sep 2000 00:31:33 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e8ILrX856991 for freebsd-hackers@freebsd.org; Mon, 18 Sep 2000 23:53:33 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: mergemaster RFC (long) Date: 18 Sep 2000 23:53:33 +0200 Message-ID: <8q62st$1nkh$1@ganerc.mips.inka.de> References: <200009171001.e8HA1Mm54441@hak.lan.Awfulhak.org> To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > First, the things I am definitely going to do. Christian "naddy" > > Weisgerber has taken on the task of porting mm to openbsd. > > I think it would be nice to aim to keep the two scripts exactly the > same, using `uname` when it's really necessary. If I have interpreted the noises Theo has made correctly, he wants mergemaster in the base tree. I don't think he'll keep a "case `uname` ..." in there. Most of the diff deals with two simple differences: - mergemaster uses "read -p " throughout. That fails for OpenBSD's /bin/sh (pdksh), where "read -p" means something entirely different. - On OpenBSD, "install" is synonymous to "install -c". FreeBSD still has the old behavior where plain "install" deletes the source file. If we can get rid of those, the actual differences become more visible. Oh, and changing every instance of "FreeBSD" into "${OPSYS}" or some such would remove another few diff lines. > I think having > > IGNOREFILES="a b c" > > isn't necessary when it's as easy to have > > rm a b c > > in your start script. It seems like overkill to handle ignored files > specifically. Well, I don't know. Something like "IGNOREFILES=..." was the first thing to come to my mind. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 16: 5:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 74DF337B422 for ; Mon, 18 Sep 2000 16:05:19 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA61686; Mon, 18 Sep 2000 19:04:28 -0400 (EDT) Date: Mon, 18 Sep 2000 19:04:28 -0400 (EDT) From: "Matthew N. Dodd" To: Piotr Sroczynski Cc: Devin Butterfield , hackers@FreeBSD.ORG Subject: Re: PnP & 4.1 Release In-Reply-To: <39C68CBA.21143.330132@localhost> 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, 18 Sep 2000, Piotr Sroczynski wrote: > First has SMC EliteULTRA 8416 software selectable PnP operation > - ethernet The 'ed' driver doesn't support SMC cards in PnP mode. (Or rather it doesn't support SMC cards in non shared memory mode which is what they run in when configured via PnP.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 16:40:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E4BAE37B42C; Mon, 18 Sep 2000 16:40:36 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8INe0i09558; Mon, 18 Sep 2000 16:40:00 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8INbh074640; Mon, 18 Sep 2000 16:37:43 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 18 Sep 2000 16:37:42 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Marc Tardif Subject: Re: device naming convention Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, "Daniel C. Sobral" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Sep-00 Marc Tardif wrote: >> > This is what I have in fdisk (from /stand/sysinstall): >> > Offset Size End Name PType Desc Subtype Flags >> > 0 63 62 - 6 unused 0 >> > 63 1937565 1937627 wd0s1 3 freebsd 165 C >> > 1937628 191268 2128895 - 6 unused 0 >> > >> > At this point, the second slice does not exist yet so I can't use it. For >> > problems in defining a slice, see next question. >> >> Really? I wouldn't expect FreeBSD to worry about the type being >> "unused". >> > If I try the following command as root, nothing is output: ># hd /dev/rwd0s2 | head Look at your output you pasted above. There is no entry with the name 'wd0s2'. There is just an entry with wd0s1. Note that those unused areas are not allocated into any existing slice at the moment, and are thus not the same as a slice with a subtype of '0' indicating that the slice itself is unused. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 17:37:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 3CE9B37B440; Mon, 18 Sep 2000 17:37:23 -0700 (PDT) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id e8J0amu53509; Tue, 19 Sep 2000 10:06:48 +0930 (CST) (envelope-from newton) Date: Tue, 19 Sep 2000 10:06:48 +0930 From: Mark Newton To: Christopher Stein Cc: Kris Kennaway , hackers@FreeBSD.ORG Subject: Re: 4.1 make world and cvsup release field Message-ID: <20000919100648.A53497@internode.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 18, 2000 at 02:45:06PM -0400, Christopher Stein wrote: > On Mon, 18 Sep 2000, Kris Kennaway wrote: > > See the /usr/src/UPDATING file after updating your source and be sure to > > follow the directions precisely. > > Every message I see in the archives on these points is very simple: > "See /usr/src/UPDATING" It's more like, "See /usr/src/UPDATING after updating your source." > Unfortunately, my system has no /usr/src/UPDATING. If you had updated your source, you would have /usr/src/UPDATING. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 18:11:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 3340237B422 for ; Mon, 18 Sep 2000 18:11:54 -0700 (PDT) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id SAA13413 for ; Mon, 18 Sep 2000 18:11:53 -0700 (PDT) Message-ID: <39C6BD59.4C1AFD02@isi.edu> Date: Mon, 18 Sep 2000 18:11:53 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: hackers@freebsd.org Subject: implementing idle-time networking Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms0AF875C3CEAC113E286FF61E" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms0AF875C3CEAC113E286FF61E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, as part of my thesis research, I'm implementing something similar to the POSIX idle-time CPU scheduler for other resource types, one being network I/O. The basic idea is to substitute two-level queues for the standard ones. I'm seeing some unexpected things (explained below), but let me first outline what I'm doing exactly: 1. I extend the ifnet structure to contain a second ifqueue, for idle-time traffic; and also declare a new flag for mbufs, to indicate whether network idle-time processing should be done or not. 2. In sosend(), I check if the sending process is running at a POSIX idle-time priority. If so, I set the idle-time flag in the mbuf. 3. In ether_output_frame(), I check if the idle-time flag is set on an mbuf, and if so, enqueue it in the interface's idle-time queue (default queue otherwise.) 4. In xl_start() (my onboard chip happens to use the xl driver), I first check the default queue for any mbufs ready to send. If there are none, I try the idle-time queue. If an mbuf could be dequeued from either queue, I continue with normal outbound processing (have mbuf be picked up by NIC). Unfortunately, this scheme does not work. Some first experiments have shown that idle-time network performance is practically identical to regular-priority. I measured it going from a slower (10Mb/s) to a faster (100Mb/s) host through a private switch, so the NIC should be the bottleneck (the processors are both 800Mhz PIII). The new code is in fact executed, I have traced it heavily. Closer inspection revealed that both the ifnet ifqueues as well as the driver transmission chain are always empty upon enqueue/dequeue. Thus, even though my fancy queuing code is executed, it has no effect, since there never are any queues. Can someone shed some light on if this is expected behavior? Wouldn't that mean that as packets are being generated by the socket layer, they are handed down through the kernel to the driver one-by-one, incurring at interrupt for each packet? Or am I missing the obvious? Thanks, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms0AF875C3CEAC113E286FF61E Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAwMDkxOTAxMTE1M1owIwYJKoZIhvcNAQkEMRYE FLxb5IyRKZ08HeztzbqAkLd6k5COMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGASrieifrAPe54qFUHcXJctSCzOCxO0qKbc1R4spynHunoxcX+rqmo f8rtmKzXAazErAUZhMxp4HN27m2nBI8WuwQ1GcwpK/I7dJQrXubCyW83cbWoooV1dgp0epfA rXad0QJ0yrIP1gM6o/vA2qatTc0HtzFlaK2jRqo69qSmMRE= --------------ms0AF875C3CEAC113E286FF61E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 18:12: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4875C37B43F; Mon, 18 Sep 2000 18:11:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA92675; Mon, 18 Sep 2000 19:11:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA34705; Mon, 18 Sep 2000 19:11:41 -0600 (MDT) Message-Id: <200009190111.TAA34705@harmony.village.org> To: Christopher Stein Subject: Re: 4.1 make world and cvsup release field Cc: Kris Kennaway , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Sep 2000 14:45:06 EDT." References: Date: Mon, 18 Sep 2000 19:11:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Christopher Stein writes: : Unfortunately, my system has no /usr/src/UPDATING. Then you need to get newer sources. /usr/src here is the conventional code for "the path to where you keep your sources." Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 18:32:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 776AE37B422; Mon, 18 Sep 2000 18:32:19 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id FAA01937; Tue, 19 Sep 2000 05:32:10 +0400 (MSD) Message-Id: <200009190132.FAA01937@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: <39C63C03.2C4C26F8@newsguy.com> from "Daniel C. Sobral" at "Sep 19, 0 01:00:03 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Tue, 19 Sep 2000 05:32:09 +0400 (MSD) Cc: intmktg@CAM.ORG, babolo@links.ru, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral writes: > Marc Tardif wrote: > > > > 4. If I want to use /dev/wd0s2 as a raw slice for reading > > > > and writing, what are the steps to follow? > > > You can't write several blocks near /dev/wd0s2 beginning. > > > Use /dev/wd0 with proper address > > > > > That is rather risky. Wouldn't it be safer to have a device name I could > > dedicate to some purpose. In such a case, I could chown the device to an > > appropriate username and group. Furthermore, I could avoid the unfortunate > > mistake of overwriting my current FreeBSD fs in case I get the addresses > > wrong. > He is incorrect. You can use /dev/wd0s2 any way you want, as long as you > have nothing of value there. It is English that I know bad. Labeling, partitioning so on I know MUCH better. So I take a time and dictionary and because of long letter I begin with conclusion. There is risky use any partition or slice with FreeBSD for arbitrary purposes. May be any file system except ffs can work improperly (msdos, ntfs, hpfs, 9660) Things are worst - ffs does not stable too, but this is far from subject of this letter. OK, lets verify. "cicuta/home/babolo(N)#" is prompt, number before is exit code. Look at test disk: 0cicuta/home/babolo(1)#fdisk wd0 ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=1011 heads=15 sectors/track=44 (660 blks/cyl) parameters to be used for BIOS calculations are: cylinders=1011 heads=15 sectors/track=44 (660 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50160 (24 Meg), flag 0 beg: cyl 0/ sector 1/ head 0; end: cyl 75/ sector 44/ head 14 The data for partition 2 is: sysid 0,(unused) start 50160, size 50160 (24 Meg), flag 0 beg: cyl 76/ sector 1/ head 0; end: cyl 151/ sector 44/ head 14 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 100320, size 50160 (24 Meg), flag 0 beg: cyl 152/ sector 1/ head 0; end: cyl 227/ sector 44/ head 14 The data for partition 4 is: sysid 0,(unused) start 0, size 0 (0 Meg), flag 80 (active) beg: cyl 0/ sector 0/ head 0; end: cyl 0/ sector 0/ head 0 Now read slices: 0cicuta/home/babolo(2)#dd if=/dev/wd0s1 of=/dev/null bs=660b 76+0 records in 76+0 records out 25681920 bytes transferred in 17.175867 secs (1495233 bytes/sec) 0cicuta/home/babolo(3)#dd if=/dev/wd0s2 of=/dev/null bs=660b 1+1 records in 1+1 records out 368640 bytes transferred in 0.258831 secs (1424250 bytes/sec) 0cicuta/home/babolo(4)#dd if=/dev/wd0s3 of=/dev/null bs=660b 76+0 records in 76+0 records out 25681920 bytes transferred in 22.601690 secs (1136283 bytes/sec) 0cicuta/home/babolo(5)#dd if=/dev/wd0s4 of=/dev/null bs=660b 0+0 records in 0+0 records out 0 bytes transferred in 0.000036 secs (0 bytes/sec) 3 equal slices, test if wd0s2 has some error in it: 0cicuta/home/babolo(6)#dd if=/dev/wd0 of=/dev/null bs=660b 1011+0 records in 1011+0 records out 341637120 bytes transferred in 283.316634 secs (1205849 bytes/sec) Whole disk read successfully. What the test system is? 0cicuta/home/babolo(7)#uname -a FreeBSD cicuta.babolo.ru 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Tue Dec 29 04:10:35 MSK 1998 babolo@cicuta.babolo.ru:/usr/src/sys/compile/cicuta i386 0cicuta/home/babolo(8)#dmesg [skip] wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-8 wd0: 325MB (667260 sectors), 1011 cyls, 15 heads, 44 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: 171/1367Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked, lock protected [skip] wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) wd0s2: raw partition size != slice size wd0s2: start 50160, end 100319, size 50160 wd0s2c: start 50160, end 50879, size 720 wd0s3: cannot find label (no disk label) The end of dmesg give the idea, why can't read whole wd0s2 slice. Now about white protected area in slice that is NOT marked 165 (FreeBSD): 0cicuta/home/babolo(9)#dd of=/dev/wd0s2 if=/dev/zero bs=660b dd: /dev/wd0s2: Invalid argument 3+0 records in 2+0 records out 675840 bytes transferred in 0.224398 secs (3011793 bytes/sec) 1cicuta/home/babolo(11)#od -b /dev/wd0s2 0000000 353 020 220 220 121 120 006 123 122 350 300 000 132 133 007 131 0000020 131 313 374 061 311 216 301 216 331 216 321 274 000 174 211 346 0000040 277 000 007 376 305 363 245 276 356 175 200 372 200 162 054 266 0000060 001 350 147 000 271 001 000 276 276 215 266 001 200 174 004 245 0000100 165 007 343 031 366 004 200 165 024 203 306 020 376 306 200 376 0000120 005 162 351 111 343 341 276 114 175 353 122 061 322 211 026 000 [skiped] 0017060 070 066 040 102 117 117 124 012 104 145 146 141 165 154 164 072 0017100 040 045 165 072 045 163 050 045 165 054 045 143 051 045 163 012 0017120 142 157 157 164 072 040 000 116 157 040 045 163 012 000 146 157 0017140 162 155 141 164 000 111 156 166 141 154 151 144 040 045 163 012 0017160 000 171 145 163 000 156 157 000 113 145 171 142 157 141 162 144 0017200 072 040 045 163 012 000 045 163 040 000 116 157 164 040 165 146 0017220 163 012 000 163 154 151 143 145 000 154 141 142 145 154 000 160 0017240 141 162 164 151 164 151 157 156 000 060 061 062 063 064 065 066 0017260 067 070 071 141 142 143 144 145 146 045 143 010 000 104 151 163 0017300 153 040 145 162 162 157 162 040 060 170 045 170 040 050 154 142 0017320 141 075 060 170 045 170 051 012 000 000 000 000 001 000 000 000 0017340 057 174 134 055 000 000 000 000 000 000 000 000 000 000 000 000 0017360 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 * 1320000 Why I use 2.2.7 for test? Because of my lovely 4.1-STABLE is extremly unstable with content of ad0s2 (wd0s2) above and silently reboot after the first dd in the test above. What is slices content? s1 - almost right FreeBSD label s2 - not a right FreeBSD label but similar enough to label. s3 - no label or similar at all. How to do such a content that screw the system? This is my way for this test: - shorten s2 to 3 cilinder. - disklabel -w -r wd0s2 fd360 - restore s2 size. How can you guarantee that occasionally some bits in slice do not fraud FreeBSD if used for arbitrary bits? Do not use slice begin at all. Does 4.1 behave similar? Yes, I know that. But it take some time to select bites in slice begin in such a way that 4.1 not reboot so friquently. You have idea and can test yourself. Remember - 4.1 is HIGHLY unstable during pseudolabel tests. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 20:47: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 8651837B424; Mon, 18 Sep 2000 20:46:57 -0700 (PDT) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id MAA78539; Tue, 19 Sep 2000 12:46:51 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200009190346.MAA78539@shidahara1.planet.sci.kobe-u.ac.jp> To: Steve Kargl , Dag-Erling Smorgrav Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: PEACE - Portable Executable win32 API Compatible Environment. In-reply-to: Your message of "Mon, 18 Sep 2000 14:23:10 MST." <200009182123.OAA15595@troutmask.apl.washington.edu> Date: Tue, 19 Sep 2000 12:46:48 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009182123.OAA15595@troutmask.apl.washington.edu>, Steve Kargl wrote: >Dag-Erling Smorgrav wrote: >> Takanori Watanabe writes: >> > PEACE is Win32 API Compatible environment for (Originally) NetBSD. >> > It consist of three parts: >> > Kernel part to load PE format executable onto process memory space. >> > Dynamic Linker to link with PE format DLL. >> > Libraries to translate Win32 API call to NetBSD native system call. >> >> What is the difference between PEACE and WINE? >> > >Wine is actually trying to completely replace MS windows (include >win3.1, win95, win98, and winnt). SO, wine includes code for the >old 16 bit API(s) and it is trying to replace all on the MS >dll's with built-in dll. Yes ,but more essential difference is the way the executable binaries are treated. In FreeBSD Linux ABI support,executable binariies are treated as a executable text and kernel translate system calls so static Linux binaries can be run. +--------+ |Linux | | binary | |+ Lib | | | +--^-----+ | -----v-------KERNEL---- |Linux Syscall| |Entry | +-------------+ In Wine, Wine behaves as operation system that runs under FreeBSD and from FreeBSD, Windows executable is treated as data file. +----Wine--------+ | +--------+ | | |Windows | | | |App.+lib| | | +^-------+ | | | | +--v-------------| | Internal Lib | +----^-----------+ | --------v------KERNEL------------ (Native system entry) In PEACE,kernel execute PE executable (NE Win16 Binaries and DOS application is not supported) directry and prepare library imprementing win32 API by FreeBSD native system call and replace some win32 library by it. +----------+ |Win32 Exec| |+some native |Lib. +----+ | | | +-----+ | |replaced lib +---^------+ | | ------v----KERNEL----------- (Native sysent) That is my understanding. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 20:55:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web115.yahoomail.com (web115.yahoomail.com [205.180.60.88]) by hub.freebsd.org (Postfix) with SMTP id DC0FE37B422 for ; Mon, 18 Sep 2000 20:55:19 -0700 (PDT) Received: (qmail 24196 invoked by uid 60001); 19 Sep 2000 03:55:19 -0000 Message-ID: <20000919035519.24195.qmail@web115.yahoomail.com> Received: from [164.164.56.2] by web115.yahoomail.com; Mon, 18 Sep 2000 20:55:19 PDT Date: Mon, 18 Sep 2000 20:55:19 -0700 (PDT) From: Mohan Krishna P Subject: semaphores inside kernel??? To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i am implementing a pseudo-devicer, many instaces of this device may be active, all have to share a resource. all instances have to synchronize their access to the resource. trying to implement this, i ended up with a less powerful version of semaphores. since the resultant code became little complex, i want to replace that with the more generic semaphores. i checked the include files, but i couldn't find any semaphore functions(semget,semctl,semop) which are specific or meant for use inside kernel. does it mean they aren't available inside kernel?? if i am wrong, can someone suggest me how to use them?? thank you, mohan __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 20:56:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 6665C37B423; Mon, 18 Sep 2000 20:56:10 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id XAA06712; Mon, 18 Sep 2000 23:59:14 -0400 Date: Mon, 18 Sep 2000 23:59:14 -0400 (EDT) From: Marc Tardif To: "Aleksandr A.Babaylov" Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention In-Reply-To: <200009190132.FAA01937@aaz.links.ru> 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 > 0cicuta/home/babolo(9)#dd of=/dev/wd0s2 if=/dev/zero bs=660b > 1cicuta/home/babolo(11)#od -b /dev/wd0s2 [ snip ] > Why I use 2.2.7 for test? > Because of my lovely 4.1-STABLE is extremly unstable with content of > ad0s2 (wd0s2) above and silently reboot after the first dd in the test above. > Assuming my wd0s2 is still unused and of size 0, 3.5-STABLE also crashes in the test above (no disk activity, ctrl-c doesn't work, alt-f# doesn't work either). Perhaps it eventually reboots, but I wasn't patient enough to wait that long. One solution to this problem is to specify the count blocks after which dd returns properly but still no bytes are copied. > What is slices content? > s1 - almost right FreeBSD label > s2 - not a right FreeBSD label but similar enough to label. > s3 - no label or similar at all. > How to do such a content that screw the system? > This is my way for this test: > - shorten s2 to 3 cilinder. > - disklabel -w -r wd0s2 fd360 > - restore s2 size. > I don't understand this last part, probably because I don't have much experience with labelling and partitioning. Please excuse my questions if they seem basic, but I am fairly new to disks: - how can s2 be "similar enough to label" if it is recognised as "sysid 0,(unused)" by fdisk? - how did you create s2 exactly, in order to make it "similar enough to label" yet remain unused? - how did you create s3 and s4 exactly? - why is s3 not similar at all if it is recognised as a FreeBSD slice by fdisk? - what do you mean by shortening s2 to 3 cylinders? Do you mean s2 should start at the third cylinder? - is there any reason you chose to label wd0s2 as fd360? - how should s2 size be restored? maybe: dd of=/dev/wd0s2 if=/dev/null bs=660b? > How can you guarantee that occasionally some > bits in slice do not fraud FreeBSD > if used for arbitrary bits? > Do not use slice begin at all. > I also didn't quite understand what is wrong with using the slice begin. Your octal dump showed how the first 017343 bytes were not nulls, but why? Is there a fixed number of bytes that should be skipped, or should this number be system dependent and tested manually? To avoid using the slice begin, could the first label be defined at a proper offset to skip the slice begin? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 21:46:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 0291337B422 for ; Mon, 18 Sep 2000 21:46:07 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id VAA69095; Mon, 18 Sep 2000 21:47:49 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id VAA05044; Mon, 18 Sep 2000 21:47:24 -0700 (PDT) (envelope-from john) Message-Id: <200009190447.VAA05044@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000919035519.24195.qmail@web115.yahoomail.com> Date: Mon, 18 Sep 2000 21:47:24 -0700 (PDT) From: John Baldwin To: Mohan Krishna P Subject: RE: semaphores inside kernel??? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Sep-00 Mohan Krishna P wrote: > hi, > > i am implementing a pseudo-devicer, many instaces of > this device may be > active, all have to share a resource. all instances > have to synchronize > their access to the resource. trying to implement > this, i ended up with a > less powerful version of semaphores. since the > resultant code became > little complex, i want to replace that with the more > generic semaphores. > > i checked the include files, but i couldn't find any > semaphore > functions(semget,semctl,semop) which are specific or > meant for use inside > kernel. does it mean they aren't available inside > kernel?? if i am wrong, > can someone suggest me how to use them?? In the most recent -current kernels, there is a new recursive mutex that you can use. See the mutex(9) manpage for details.  > thank you, > mohan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 18 23:28:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id ACE9C37B423 for ; Mon, 18 Sep 2000 23:28:44 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id IAA21747; Tue, 19 Sep 2000 08:29:47 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200009190629.IAA21747@info.iet.unipi.it> Subject: Re: implementing idle-time networking In-Reply-To: <39C6BD59.4C1AFD02@isi.edu> from Lars Eggert at "Sep 18, 2000 06:11:53 pm" To: Lars Eggert Date: Tue, 19 Sep 2000 08:29:47 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i believe there are two things here that you need to consider before you can see any queue build up in ipq: 1. you should generate packets (way) faster than the card is able to handle them; 2. the network card itself might be able to queue multiple packets in the "transmit ring"; to check if #2 is true you should either look at the driver, or trace how fast ipq is drained (e.g. take timestamps) and see if it happens faster than the packet transmission time. re. #1, remember that on a 100Mbit net a full-sized packet goes out in some 100us, which is fast. Maybe you have already done this, but just in case, you should run your tests preferably with reasonably long (that might mean some 50-100 packets if there is queueing in the card) bursts full-sized UDP packets and on a 10Mbit/s link to see queues build up in ipq. cheers luigi > > as part of my thesis research, I'm implementing something similar to the > POSIX idle-time CPU scheduler for other resource types, one being network > I/O. The basic idea is to substitute two-level queues for the standard > ones. I'm seeing some unexpected things (explained below), but let me first > outline what I'm doing exactly: > > 1. I extend the ifnet structure to contain a second ifqueue, for idle-time > traffic; and also declare a new flag for mbufs, to indicate whether network > idle-time processing should be done or not. > > 2. In sosend(), I check if the sending process is running at a POSIX > idle-time priority. If so, I set the idle-time flag in the mbuf. > > 3. In ether_output_frame(), I check if the idle-time flag is set on an > mbuf, and if so, enqueue it in the interface's idle-time queue (default > queue otherwise.) > > 4. In xl_start() (my onboard chip happens to use the xl driver), I first > check the default queue for any mbufs ready to send. If there are none, I > try the idle-time queue. If an mbuf could be dequeued from either queue, I > continue with normal outbound processing (have mbuf be picked up by NIC). > > Unfortunately, this scheme does not work. Some first experiments have shown > that idle-time network performance is practically identical to > regular-priority. I measured it going from a slower (10Mb/s) to a faster > (100Mb/s) host through a private switch, so the NIC should be the > bottleneck (the processors are both 800Mhz PIII). The new code is in fact > executed, I have traced it heavily. > > Closer inspection revealed that both the ifnet ifqueues as well as the > driver transmission chain are always empty upon enqueue/dequeue. Thus, even > though my fancy queuing code is executed, it has no effect, since there > never are any queues. > > Can someone shed some light on if this is expected behavior? Wouldn't that > mean that as packets are being generated by the socket layer, they are > handed down through the kernel to the driver one-by-one, incurring at > interrupt for each packet? Or am I missing the obvious? > > Thanks, > Lars > -- > Lars Eggert Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California Content-Description: S/MIME Cryptographic Signature [Attachment, skipping...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 0:44: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 539E837B422; Tue, 19 Sep 2000 00:44:01 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id EB1B62B211; Tue, 19 Sep 2000 02:44:00 -0500 (CDT) Date: Tue, 19 Sep 2000 00:44:00 -0700 From: Paul Saab To: Chris Csanady Cc: Mike Smith , Danny Braniss , freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000919004400.A25068@elvis.mu.org> References: <200009111926.MAA13990@mass.osd.bsdi.com> <39C673DB.135A25FC@ameslab.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39C673DB.135A25FC@ameslab.gov>; from cc@ameslab.gov on Mon, Sep 18, 2000 at 02:58:19PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Csanady (cc@ameslab.gov) wrote: > Has this actually been merged to -stable yet? I can't find anything that > actually reads the boot.nfsroot.* loader variables. Yes.. it was done more than a week ago. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 2:18:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id EB6AB37B422; Tue, 19 Sep 2000 02:18:10 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 88A042B211; Tue, 19 Sep 2000 04:18:10 -0500 (CDT) Date: Tue, 19 Sep 2000 02:18:10 -0700 From: Paul Saab To: Chris Csanady Cc: Mike Smith , Danny Braniss , freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000919021810.A27284@elvis.mu.org> References: <200009111926.MAA13990@mass.osd.bsdi.com> <39C673DB.135A25FC@ameslab.gov> <20000919004400.A25068@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000919004400.A25068@elvis.mu.org>; from paul@mu.org on Tue, Sep 19, 2000 at 12:44:00AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Saab (paul@mu.org) wrote: > Chris Csanady (cc@ameslab.gov) wrote: > > Has this actually been merged to -stable yet? I can't find anything that > > actually reads the boot.nfsroot.* loader variables. > > Yes.. it was done more than a week ago. Ugh.. I could have sworn I MFC'd this a week ago, but it turns out I did everything but the last part. *sigh*. I just MFC'd it. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 7: 0:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from astart2.astart.com (astart2.astart.com [64.63.58.122]) by hub.freebsd.org (Postfix) with ESMTP id C7E4B37B422 for ; Tue, 19 Sep 2000 07:00:32 -0700 (PDT) Received: from h4.private (papowell@h4.private [10.0.0.4]) by astart2.astart.com (8.9.3/8.9.3) with ESMTP id XAA44396; Mon, 18 Sep 2000 23:59:41 -0700 (PDT) (envelope-from papowell@astart.com) Received: (from papowell@localhost) by h4.private (8.9.3/8.9.3) id HAA16643; Tue, 19 Sep 2000 07:01:33 -0700 (PDT) Date: Tue, 19 Sep 2000 07:01:33 -0700 (PDT) From: papowell@astart.com Message-Id: <200009191401.HAA16643@h4.private> To: imp@village.org, papowell@astart.com Subject: Re: Device driver, memory map failing, and it is probably obvious Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 17 20:03:11 2000 > To: papowell@astart.com > Subject: Re: Device driver, memory map failing, and it is probably obvious > Cc: freebsd-hackers@FreeBSD.ORG > Date: Sun, 17 Sep 2000 21:01:44 -0600 > From: Warner Losh > > In message <200009180220.TAA12263@h4.private> papowell@astart.com writes: > : I am making a driver for a VERY old PCI device. > : > digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, > : > &digic->digic_mem_rid, > : > 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); > > : Could this be the problem? > > Where do you initialize digic_mem_rid? You should set this equal to > the BAR offset in the PCI config space that corresponds to this > memory. > > Warner > BINGO! I added the following: /* now get the memory resources */ digic->digic_mem_rid = DIGI_LOMEM; digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &digic->digic_mem_rid, 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); By the way, from the bus_alloc_resource man page: /* now get the memory resources */ digic->digic_mem_rid = DIGI_LOMEM; digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &digic->digic_mem_rid, 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); > rid points to a bus specific handle that identifies the resource being > allocated. For ISA this is an index into an array of resources that have > been setup for this device by either the PnP mechanism, or via the hints > mechanism. For PCCARD, similar things are used as of writing, but that > may change in the future with newcard. For PCI it just happens to be the > offset into pci config space which has a word that describes the re- > source. The bus methods are free to change the RIDs that they are given > as a parameter. You must not depend on the value you gave it earlier. I might suggest a small rewording: rid points to a value that contains a bus specific handle that identifies the resource being allocated. For ISA this is an index into an array of resources that have been setup for this device by either the PnP mechanism, or via the hints mechanism. A value of 0 will use the first resource. See XXXXX for more details. For PCCARD, similar things are used as of writing, but that may change in the future with newcard. For PCI it is the offset into pci config space which has a word that describes the re- source. The bus methods are may change the values of the RIDs that they are given as a parameter. You must not depend on the value you gave it earlier. You might want to fill in XXXXX. EXAMPLES This is an example for an ISA bus interface. The values of portid and irqid should be saved in the softc of the device after these calls. struct resource *portres, irqres; int portid, irqid, value; #define REG1_OFFSET 0 portid = 0; /* use the first port resource */ irqid = 0; /* use the first interrupt resource */ portres = bus_alloc_resource(dev, SYS_RES_IOPORT, &portid, 0ul, ~0ul, 32, RF_ACTIVE); irqres = bus_alloc_resource(dev, SYS_RES_IRQ, &irqid, 0ul, ~0ul, 1, RF_ACTIVE | RF_SHAREABLE); value = bus_space_read_1( rman_get_bustag(portres), rman_get_bustag(portres), REG1_OFFSET ); This is an example for a PCI bus interface. We assume that for this particular device the device registers are available through PIO instructions or have been mapped into the PCI memory space. We can choose which method we want to use by setting the rid value to the appropriate offset in the PCI configuration that has the IO port or memory information. struct resource *portres; int portid, value; #define REG1_OFFSET 0 #define LOMEM 0x10 #define LOIO 0x14 if( use_io ){ portid = LOIO; } else { portid = LOMEM; } portres = bus_alloc_resource(dev, SYS_RES_IOPORT, &portid, 0ul, ~0ul, 32, RF_ACTIVE); value = bus_space_read_1( rman_get_bustag(portres), rman_get_bustag(portres), REG1_OFFSET ); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 7:30:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id E2C0D37B422; Tue, 19 Sep 2000 07:30:43 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id SAA26861; Tue, 19 Sep 2000 18:30:36 +0400 (MSD) Message-Id: <200009191430.SAA26861@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: from "Marc Tardif" at "Sep 18, 0 11:59:14 pm" To: intmktg@CAM.ORG (Marc Tardif) Date: Tue, 19 Sep 2000 18:30:36 +0400 (MSD) Cc: babolo@links.ru, dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif writes: > > What is slices content? > > s1 - almost right FreeBSD label > > s2 - not a right FreeBSD label but similar enough to label. > > s3 - no label or similar at all. > > How to do such a content that screw the system? > > This is my way for this test: > > - shorten s2 to 3 cilinder. > > - disklabel -w -r wd0s2 fd360 > > - restore s2 size. > I don't understand this last part, probably because I don't have much > experience with labelling and partitioning. Please excuse my questions if > they seem basic, but I am fairly new to disks: > - how can s2 be "similar enough to label" if it is recognised > as "sysid 0,(unused)" by fdisk? sorry, content of s2 ... No, s2 has some bits at the begin that FreeBSD interpretes as label. "sysid 0,(unused)" has no sense - every sysid cant stop slice from been evaluated for label on it. > - how did you create s2 exactly, in order to make it "similar > enough to label" yet remain unused? in case I write about steps were: - fdisk -u wd0 create 3 slices of equal lenght 76 cylinders s1 - suid 165, s2 - suid 0, s3 - suid 165. - reboot - label s1 - I dont remember exact way, nothing special I believe. - fdisk -u wd0 change slice s2 with suid 0 and 3 cylinders (3*660 blocks) in size - disklabel -w -r wd0s2 fd360 - disklabel -e wd0s2 delete b:, mark a: unused and mark c: 4.2BSD - fdisk -u wd0 change size of s2 to 76 tracks. - reboot Now s2 has invalid (broken) label (or some bits that are similar to label) > - how did you create s3 and s4 exactly? s3 above, s4 is suid 0 start 0 size 0 > - why is s3 not similar at all if it is recognised as a > FreeBSD slice by fdisk? s3 has some scrap that is not recognized by FreeBSD as "label" Again - sysid has no sense if not used in boot process or another system, FreeBSD seek every slice for label independantly of sysid. > - what do you mean by shortening s2 to 3 cylinders? Do you > mean s2 should start at the third cylinder? After first fdisk I change s2 size only, not any other s2 parameter > - is there any reason you chose to label wd0s2 as fd360? It is the easyest way to write something to s2 that is similar to label. fd360 is first type in my /etc/disktypes > - how should s2 size be restored? maybe: > dd of=/dev/wd0s2 if=/dev/null bs=660b? No. change size wia fdisk > > How can you guarantee that occasionally some > > bits in slice do not fraud FreeBSD > > if used for arbitrary bits? > > Do not use slice begin at all. > I also didn't quite understand what is wrong with using the slice begin. > Your octal dump showed how the first 017343 bytes were not nulls, but why? > Is there a fixed number of bytes that should be skipped, or should this > number be system dependent and tested manually? If you use slice in such a way that in label area occur something that can be treated by OS as a FreeBSD label, then protection of label and boot area occur. label area IMHO 1K, boot area in any case ends before 32 block (first suberblock copy in ufs) As far as I understand (but I am not hard in this) just keep 4 bytes (addresses 0376, 00377, 00776, 00777) is sufficient > To avoid using the slice begin, could the first label be defined at a > proper offset to skip the slice begin? If NOT use FreeBSD label? How? If use FreeBSD label? just use FreeBSD partitions inside slice (M$ partiton)? May be. But I have example of misbehave such a conctruction in 2.2.X. Not tested in 4.1. Are you interested? 3.X not interesting at all. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 7:31:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id ECD3537B423 for ; Tue, 19 Sep 2000 07:31:34 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id QAA88233 for freebsd-hackers@FreeBSD.ORG; Tue, 19 Sep 2000 16:31:30 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id e8J93vN05018 for ; Tue, 19 Sep 2000 11:04:00 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <00ac01c02218$7f91e080$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: traceroute using tcp to a port? Date: Tue, 19 Sep 2000 11:00:57 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I understand correctly, traceroute works by sending pings with ttl=1, ttl=2,ttl=3 etc and records the names of the routers where the ttl reaches zero. However, an increasing number of sites believes in security by obscurity, and blocks for pings. Would the same technique work for making a telnet to port 80 with ttl=1, ttl=2 etc? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 7:36:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from envy.vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id 3213F37B422 for ; Tue, 19 Sep 2000 07:36:20 -0700 (PDT) Received: (qmail 7122 invoked from network); 19 Sep 2000 14:36:18 -0000 Received: from kesteren.vuurwerk.nl (HELO daemon.vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 19 Sep 2000 14:36:18 -0000 Received: (nullmailer pid 5945 invoked by uid 11109); Tue, 19 Sep 2000 14:36:19 -0000 Date: Tue, 19 Sep 2000 16:36:19 +0200 From: Peter van Dijk To: freebsd-hackers@FreeBSD.ORG Subject: Re: traceroute using tcp to a port? Message-ID: <20000919163619.K5422@vuurwerk.nl> Mail-Followup-To: Peter van Dijk , freebsd-hackers@FreeBSD.ORG References: <00ac01c02218$7f91e080$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00ac01c02218$7f91e080$0e00a8c0@neland.dk>; from leifn@neland.dk on Tue, Sep 19, 2000 at 11:00:57AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 11:00:57AM +0200, Leif Neland wrote: > If I understand correctly, traceroute works by sending pings with ttl=1, > ttl=2,ttl=3 etc and records the names of the routers where the ttl reaches > zero. > > However, an increasing number of sites believes in security by obscurity, > and blocks for pings. traceroute doesn't use pings. mtr does. > Would the same technique work for making a telnet to port 80 with ttl=1, > ttl=2 etc? traceroute currently uses UDP in a similar way, and a SYN ping (like nmap does) should be possible too, yes. The problem is that those sites hinder traceroutes by blocking certain kinds of *outgoing* ICMP traffic, and there's no way we can work around that. Greetz, Peter. -- [ircoper] petervd@vuurwerk.nl - Peter van Dijk / Hardbeat [student] Undernet:#groningen/wallops | IRCnet:/#alliance [developer] EFnet:#qmail _____________ [disbeliever - the world is backwards] (__VuurWerk__(--*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 7:43: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id B0CD837B422 for ; Tue, 19 Sep 2000 07:42:50 -0700 (PDT) Received: from ogoun.hsc.fr (ogoun.hsc.fr [192.70.106.75]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "ogoun.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id C77F410E04 for ; Tue, 19 Sep 2000 16:42:49 +0200 (CEST) Received: by ogoun.hsc.fr (Postfix, from userid 1000) id 472AF9D411; Tue, 19 Sep 2000 16:42:16 +0200 (CEST) Date: Tue, 19 Sep 2000 16:42:16 +0200 From: Yann Berthier To: freebsd-hackers@FreeBSD.ORG Subject: Re: traceroute using tcp to a port? Message-ID: <20000919164216.J65102@hsc.fr> References: <00ac01c02218$7f91e080$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00ac01c02218$7f91e080$0e00a8c0@neland.dk>; from leifn@neland.dk on Tue, Sep 19, 2000 at 11:00:57AM +0200 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, Leif Neland wrote: > If I understand correctly, traceroute works by sending pings with ttl=1, > ttl=2,ttl=3 etc and records the names of the routers where the ttl reaches > zero. > > However, an increasing number of sites believes in security by obscurity, > and blocks for pings. > > Would the same technique work for making a telnet to port 80 with ttl=1, > ttl=2 etc? > > Leif Of course it works, and very well. You should try hping (http://www.kyuzz.org/antirez/hping/) which is a _very cool_ tool developped by Antirez. With it you could do (among many things) traceroute over tcp. regards, -- Yann BERTHIER Yann.Berthier@hsc.fr Network Security Consultant Herve Schauer Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 8:40: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id AE11837B423 for ; Tue, 19 Sep 2000 08:40:00 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA18323 for ; Tue, 19 Sep 2000 11:41:04 -0400 (EDT) Message-Id: <200009191541.LAA18323@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 19 Sep 2000 11:39:50 -0400 To: hackers@freebsd.org From: Dennis Subject: Serial port locks up 4.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: It seems that if you try to access the serial port on a MB with the port disabled, freebsd 4.1 will freeze up solid. Enabling the serial console will cause a lock up on boot, and any access to the port will do it as well. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 8:42:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 22D4137B423; Tue, 19 Sep 2000 08:42:25 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id LAA08606; Tue, 19 Sep 2000 11:45:40 -0400 Date: Tue, 19 Sep 2000 11:45:40 -0400 (EDT) From: Marc Tardif To: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: device timings 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 Considering the following disk configuration: ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=256 heads=132 sectors/track=63 (8316 blks/cyl) parameters to be used for BIOS calculations are: cylinders=256 heads=132 sectors/track=63 (8316 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 1937565 (946 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 232/ sector 63/ head 131 The data for partition 2 is: sysid 0,(unused) start 1937628, size 58212 (28 Meg), flag 0 beg: cyl 233/ sector 1/ head 0; end: cyl 239/ sector 63/ head 131 ... Now considering the following timings done with dd, how come I get such different transfer rates (bytes/sec) for s1 and s2? I understand there should be a difference between the block and character interface, as shown in the first two timings, but why isn't the same difference shown for the last two timings? # dd if=/dev/wd0s1 of=/dev/null bs=8316b count=5 5+0 records in 5+0 records out 21288960 bytes transferred in 8.580486 secs (2481090 bytes/sec) # dd if=/dev/rwd0s1 of=/dev/null bs=8316b count=5 5+0 records in 5+0 records out 21288960 bytes transferred in 4.058639 secs (5245344 bytes/sec) # dd if=/dev/wd0s2 of=/dev/null bs=8316b count=5 5+0 records in 5+0 records out 21288960 bytes transferred in 6.066568 secs (3509226 bytes/sec) # dd if=/dev/rwd0s2 of=/dev/null bs=8316b count=5 5+0 records in 5+0 records out 21288960 bytes transferred in 6.015735 secs (3538879 bytes/sec) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 8:49:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 2119137B423 for ; Tue, 19 Sep 2000 08:49:40 -0700 (PDT) Received: (qmail 7759 invoked by uid 0); 19 Sep 2000 15:49:38 -0000 Received: from m368-mp1-cvx1a.rdg.ntl.com (HELO default) (213.104.149.112) by mail.gmx.net with SMTP; 19 Sep 2000 15:49:38 -0000 Message-ID: <000d01c02251$38316330$709568d5@default> From: "robert smith" To: Subject: Date: Tue, 19 Sep 2000 16:49:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 8:50:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 7056337B422; Tue, 19 Sep 2000 08:50:30 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8JFoQN91118; Tue, 19 Sep 2000 17:50:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Marc Tardif Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: device timings In-Reply-To: Your message of "Tue, 19 Sep 2000 11:45:40 EDT." Date: Tue, 19 Sep 2000 17:50:26 +0200 Message-ID: <91116.969378626@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Marc Tard if writes: >Now considering the following timings done with dd, how come I get such >different transfer rates (bytes/sec) for s1 and s2? I understand there >should be a difference between the block and character interface, as shown >in the first two timings, but why isn't the same difference shown for the >last two timings? Because all modern disks use "zone-layout" where there are typically 50% more sectors in the outher cylinders compared to the inner cylinders. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 8:58:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 8A9AD37B43C; Tue, 19 Sep 2000 08:58:26 -0700 (PDT) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id XAA10960; Tue, 19 Sep 2000 23:58:21 +0800 Received: from jules.elischer.org (reggae-38-16.nv.iinet.net.au [203.59.172.16]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id XAA01515; Tue, 19 Sep 2000 23:58:17 +0800 Message-ID: <39C78D0E.7DE14518@elischer.org> Date: Tue, 19 Sep 2000 08:58:06 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Marc Tardif Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: device timings References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Modern disks pack different ammounts of data on different tracks.. (the outside tracks are longer right?) so at a constant speed (rpm) outside tracks have more data passing below the head per given time than teh inside tracks do... this seems pretty normal to me.. Marc Tardif wrote: > > Considering the following disk configuration: > ******* Working on device /dev/rwd0 ******* > parameters extracted from in-core disklabel are: > cylinders=256 heads=132 sectors/track=63 (8316 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=256 heads=132 sectors/track=63 (8316 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 1937565 (946 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 232/ sector 63/ head 131 > The data for partition 2 is: > sysid 0,(unused) > start 1937628, size 58212 (28 Meg), flag 0 > beg: cyl 233/ sector 1/ head 0; > end: cyl 239/ sector 63/ head 131 > ... > > Now considering the following timings done with dd, how come I get such > different transfer rates (bytes/sec) for s1 and s2? I understand there > should be a difference between the block and character interface, as shown > in the first two timings, but why isn't the same difference shown for the > last two timings? > > # dd if=/dev/wd0s1 of=/dev/null bs=8316b count=5 > 5+0 records in > 5+0 records out > 21288960 bytes transferred in 8.580486 secs (2481090 bytes/sec) > > # dd if=/dev/rwd0s1 of=/dev/null bs=8316b count=5 > 5+0 records in > 5+0 records out > 21288960 bytes transferred in 4.058639 secs (5245344 bytes/sec) > > # dd if=/dev/wd0s2 of=/dev/null bs=8316b count=5 > 5+0 records in > 5+0 records out > 21288960 bytes transferred in 6.066568 secs (3509226 bytes/sec) > > # dd if=/dev/rwd0s2 of=/dev/null bs=8316b count=5 > 5+0 records in > 5+0 records out > 21288960 bytes transferred in 6.015735 secs (3538879 bytes/sec) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 10:23:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.GTS.NET (whambam.gts.net [204.138.66.97]) by hub.freebsd.org (Postfix) with ESMTP id 6CA7937B43C for ; Tue, 19 Sep 2000 10:23:47 -0700 (PDT) Received: from LocalHost by uucp.GTS.NET (Smail-3.2.0.111 2000-Feb-17 #1; 2000-Feb-19) (1349 bytes) via sendmail with /P:stdio/R:inet_hosts/T:smtp id (sender ) for hackers@freebsd.org; Tue, 19 Sep 2000 13:23:36 -0400 (EDT) Message-Id: From: GTS Network admin Subject: pty & tcsetattr To: hackers@freebsd.org Date: Tue, 19 Sep 2000 13:23:35 -0400 (EDT) Cc: jim@reptiles.org, woods@weird.com X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some PPPoE issues so I did a cvsup of FreeBSD 3.4 to help fix them. An unfortunate consequence of this is that pty's seem to be broken now with respect to certain TERMIO operations, which breaks my VPN system completely (thus leaving the client in question with a partly broken WAN). This command line: pty-redir /usr/local/bin/ssh -e none -l toor -t -o 'BatchMode yes' la-gw echo hi returns the pty name string from pty-redir, and an error message from ssh (the /usr/ports/security/ssh version) which says: tcsetattr: Invalid argument This message comes from the enter_raw_mode() function in the clientloop.c module in the ssh-1.2.27 distribution. An attempt to substitute cfmakeraw() in the above function had no visible effect. I am not on your mailing list, so please direct any replies to hostmaster at gts.net - any assistance will be much appreciated. Thanks, Bruce Becker Network Administration Toronto, Ont. Vox: +1 416 699 1868 Email: hostmaster@gts.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 11: 8:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.GTS.NET (whambam.gts.net [204.138.66.97]) by hub.freebsd.org (Postfix) with ESMTP id C8E4937B422 for ; Tue, 19 Sep 2000 11:08:12 -0700 (PDT) Received: from LocalHost by uucp.GTS.NET (Smail-3.2.0.111 2000-Feb-17 #1; 2000-Feb-19) (1276 bytes) via sendmail with /P:stdio/R:inet_hosts/T:smtp id (sender ) for freebsd-hackers@freebsd.org; Tue, 19 Sep 2000 14:08:08 -0400 (EDT) Message-Id: From: GTS Network admin Subject: pty & tcsetattr To: hackers@freebsd.org Date: Tue, 19 Sep 2000 13:23:35 -0400 (EDT) Cc: jim@reptiles.org, woods@weird.com X-Mailer: ELM [version 2.5 PL2] Content-Length: 989 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some PPPoE issues so I did a cvsup of FreeBSD 3.4 to help fix them. An unfortunate consequence of this is that pty's seem to be broken now with respect to certain TERMIO operations, which breaks my VPN system completely (thus leaving the client in question with a partly broken WAN). This command line: pty-redir /usr/local/bin/ssh -e none -l toor -t -o 'BatchMode yes' la-gw echo hi returns the pty name string from pty-redir, and an error message from ssh (the /usr/ports/security/ssh version) which says: tcsetattr: Invalid argument This message comes from the enter_raw_mode() function in the clientloop.c module in the ssh-1.2.27 distribution. An attempt to substitute cfmakeraw() in the above function had no visible effect. I am not on your mailing list, so please direct any replies to hostmaster at gts.net - any assistance will be much appreciated. Thanks, Bruce Becker Network Administration Toronto, Ont. Vox: +1 416 699 1868 Email: hostmaster@gts.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 11:36:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cosrel2.hp.com (cosrel2.hp.com [156.153.255.162]) by hub.freebsd.org (Postfix) with ESMTP id 418F637B423; Tue, 19 Sep 2000 11:36:01 -0700 (PDT) Received: from udlkern.fc.hp.com (udlkern.fc.hp.com [15.1.52.48]) by cosrel2.hp.com (Postfix) with ESMTP id B3B619DF; Tue, 19 Sep 2000 12:34:54 -0600 (MDT) Received: from udlkern.fc.hp.com (erdos.fc.hp.com [15.1.54.169]) by udlkern.fc.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 SMKit7.0) id MAA19602; Tue, 19 Sep 2000 12:35:08 -0600 (MDT) Message-ID: <39C7B1DC.632CC701@udlkern.fc.hp.com> Date: Tue, 19 Sep 2000 12:35:08 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.72 [en] (X11; U; HP-UX B.11.00 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: bus_space_subregion()? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I'm trying to port the TGA/TGA2 driver from NetBSD to FreeBSD, and there is a function used throughout the code (bus_space_subregion()) that has a prototype defined in FreeBSD, but no code associated with it--does anyone know if there is a functional equivalent? Andrew Miklic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 11:59:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id C103137B43C for ; Tue, 19 Sep 2000 11:59:17 -0700 (PDT) Received: (qmail 85518 invoked by uid 1001); 19 Sep 2000 18:58:08 +0000 (GMT) To: Yann.Berthier@hsc.fr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: traceroute using tcp to a port? From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 19 Sep 2000 16:42:16 +0200" References: <20000919164216.J65102@hsc.fr> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 19 Sep 2000 20:58:07 +0200 Message-ID: <85516.969389887@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of course it works, and very well. You should try hping > (http://www.kyuzz.org/antirez/hping/) which is a _very cool_ tool > developped by Antirez. With it you could do (among many things) > traceroute over tcp. Ah, you mean just like FreeBSD's "traceroute -P tcp" does? 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 Tue Sep 19 12:18:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 280C737B424 for ; Tue, 19 Sep 2000 12:18:31 -0700 (PDT) Received: from ogoun.hsc.fr (ogoun.hsc.fr [192.70.106.75]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "ogoun.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id 6034810FCE for ; Tue, 19 Sep 2000 21:18:30 +0200 (CEST) Received: by ogoun.hsc.fr (Postfix, from userid 1000) id D1D929D411; Tue, 19 Sep 2000 21:18:24 +0200 (CEST) Date: Tue, 19 Sep 2000 21:17:15 +0200 From: Yann Berthier To: hackers-freebsd@FreeBSD.ORG Subject: Re: traceroute using tcp to a port? Message-ID: <20000919211715.O65102@hsc.fr> References: <20000919164216.J65102@hsc.fr> <85516.969389887@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85516.969389887@verdi.nethelp.no>; from sthaug@nethelp.no on Tue, Sep 19, 2000 at 08:58:07PM +0200 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, sthaug@nethelp.no wrote: > > Of course it works, and very well. You should try hping > > (http://www.kyuzz.org/antirez/hping/) which is a _very cool_ tool > > developped by Antirez. With it you could do (among many things) > > traceroute over tcp. > > Ah, you mean just like FreeBSD's "traceroute -P tcp" does? No, I mean something like : # ./hping2 -S -p 80 -T -t 1 www.whatever.tld (with -S setting the syn flag, -t the initial ttl, -p the destination port, and -T for traceroute mode). For sure other tools could do the same, I talked about hping 'cause it's my ip swiss knife :) regards, Yann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 13:42:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B260537B422; Tue, 19 Sep 2000 13:42:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA96925; Tue, 19 Sep 2000 14:42:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA41378; Tue, 19 Sep 2000 14:42:30 -0600 (MDT) Message-Id: <200009192042.OAA41378@harmony.village.org> To: "Andrew M. Miklic" Subject: Re: bus_space_subregion()? Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 19 Sep 2000 12:35:08 MDT." <39C7B1DC.632CC701@udlkern.fc.hp.com> References: <39C7B1DC.632CC701@udlkern.fc.hp.com> Date: Tue, 19 Sep 2000 14:42:30 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39C7B1DC.632CC701@udlkern.fc.hp.com> "Andrew M. Miklic" writes: : is a function used throughout the code (bus_space_subregion()) that has : a prototype defined in FreeBSD, but no code associated with it--does : anyone know if there is a functional equivalent? No. I'm fairly sure that there's no equivalent. These interfaces post date the import from NetBSD of the bus_space interface. We should likely add them, as they are useful. They are trivial to implement on i386 and alpha given that bus_space_handle_t is basically an int. On pc98 these will be harder to implement, but shouldn't be too bad. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 14:25:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id DD97F37B424 for ; Tue, 19 Sep 2000 14:25:13 -0700 (PDT) Received: (qmail 11528 invoked by uid 0); 19 Sep 2000 21:25:04 -0000 Received: from m919-mp1-cvx1b.rdg.ntl.com (HELO default) (213.104.155.151) by mail.gmx.net with SMTP; 19 Sep 2000 21:25:04 -0000 Message-ID: <002e01c02280$17555340$979b68d5@default> From: "robert smith" To: Subject: Installation problem Date: Tue, 19 Sep 2000 22:24:47 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01C02288.6AE67A40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0027_01C02288.6AE67A40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hello, allow me to introduce myself. i regard myself to be a well experienced computer user using many = platforms. yet, when i tried to install freebsd, i found that i cannot, since just = past the setupx configuration, the cpu halts. or gets stuck in a cyclic = loop, where i am unable to do anything, and the monitor seems to get = itself into an unreachable mode, this is just after the x-setup, so when = the computer goes back to the installation menus, but i dont get a = chance to see any of them. any assisatnce is welcome. www: www.mp34me.org email: psyfybre@gmx.net icq uin: 21156382 ------=_NextPart_000_0027_01C02288.6AE67A40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hello, allow me to introduce = myself.
 
i regard myself to be a well = experienced computer=20 user using many platforms.
 
yet, when i tried to install freebsd, = i found that=20 i cannot, since just past the setupx configuration, the cpu halts. or = gets stuck=20 in a cyclic loop, where i am unable to do anything, and the monitor = seems=20 to get itself into an unreachable mode, this is just after the x-setup, = so when=20 the computer goes back to the installation menus, but i dont get a = chance to see=20 any of them.
 
any assisatnce is = welcome.
 
www: www.mp34me.org
email: psyfybre@gmx.net
icq uin:=20 21156382
------=_NextPart_000_0027_01C02288.6AE67A40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 14:39:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 2CCEE37B422 for ; Tue, 19 Sep 2000 14:39:16 -0700 (PDT) Received: (qmail 8240 invoked by uid 1001); 19 Sep 2000 21:39:09 -0000 Date: Tue, 19 Sep 2000 17:39:09 -0400 From: Brian Reichert To: robert smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Installation problem Message-ID: <20000919173909.C7694@numachi.com> References: <002e01c02280$17555340$979b68d5@default> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <002e01c02280$17555340$979b68d5@default>; from psyfybre@gmx.net on Tue, Sep 19, 2000 at 10:24:47PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 10:24:47PM +0100, robert smith wrote: > hello, allow me to introduce myself. > > i regard myself to be a well experienced computer user using many platforms. > > yet, when i tried to install freebsd, i found that i cannot, since just past the setupx configuration, the cpu halts. or gets stuck in a cyclic loop, where i am unable to do anything, and the monitor seems to get itself into an unreachable mode, this is just after the x-setup, so when the computer goes back to the installation menus, but i dont get a chance to see any of them. My experience in installing FreeBSD: - Do a minimal install first, and reboot the machine. Make sure you use the 'Options' menu to set debugging to 'yes'. This will assure: - that your installation media is OK. - that you don't have a messed up partition table, or an unbootable partition. - that core hardware (memeory, CPU. hard drive, etc.) works adequately. (memory failures can be a bit magical.) - Even better, do said minimal install via a serial port, from another machine running 'script'. This give a recorded log of your installation process, as well as any messages generated during the reboot. Everything after this point is stuff to be added on, and likely should be done in stages. (Setting a root password, installing packages/distributions/etc.) I've personally never tried to set up X from FreeBSD's installation disks. They just invoke utilities that come with the X distribution. Feel free to use the install disks to install the X distribution, but use the command-line tools to configure X. That way, you can use the man pages for the utilities to see what they are doing, and how they report errors. BTW - I suspect this should have gone to -questions... Good luck... > any assisatnce is welcome. > > www: www.mp34me.org > email: psyfybre@gmx.net > icq uin: 21156382 -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 16:26:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 0B4B937B424 for ; Tue, 19 Sep 2000 16:26:55 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA00942; Mon, 18 Sep 2000 17:23:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009190023.RAA00942@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Csanady Cc: Danny Braniss , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Mon, 18 Sep 2000 14:58:19 CDT." <39C673DB.135A25FC@ameslab.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2000 17:23:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > ok, once i compiled a kernel with options BOOTP things got better ;-) > > > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) > > > but after it re-configures the ethernet, the ethernet stops working! > > > > > > ponters anyone? > > > > You can't run dhclient (DHCP in any of the ifconfig lines in /etc/ > > rc.conf) if you have mounted / via NFS. > > > > If you're running -current or a very recent -stable, remove the 'BOOTP' > > options. The loader now passes all the DHCP information into the kernel. > > Then leave the interface configuration alone... > > Has this actually been merged to -stable yet? I can't find anything that > actually reads the boot.nfsroot.* loader variables. Supposedly; Paul Saab did the merge. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 16:40:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 03FC937B422 for ; Tue, 19 Sep 2000 16:40:31 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA00943; Tue, 19 Sep 2000 16:41:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009192341.QAA00943@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: Serial port locks up 4.1 In-reply-to: Your message of "Tue, 19 Sep 2000 11:39:50 EDT." <200009191541.LAA18323@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 16:41:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FYI: It seems that if you try to access the serial port on a MB with the > port disabled, freebsd 4.1 will freeze up solid. Enabling the serial > console will cause a lock up on boot, and any access to the port will do it > as well. This is probably a feature of the board/super-IO chipset in question. In particular, the port should never have probed successfully if the port was really "disabled", so you should never have been able to access it in the first place. The correct solution, of course, is "don't do that". -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 19:20:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D1C3F37B42C for ; Tue, 19 Sep 2000 19:20:27 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA12887 for ; Tue, 19 Sep 2000 22:20:26 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8K2KQA06910; Tue, 19 Sep 2000 22:20:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Sep 2000 22:20:26 -0400 (EDT) To: freebsd-hackers@freebsd.org Subject: Mounting Solaris/x86 slices? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14792.6464.331697.460715@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are we able to mount Solaris/x86 disk slices? I'm thinking about trying use FreeBSD as an installation crutch to mirror a Solaris/86 installation to 60-odd PCs (I can have FreeBSD netbooted to a diskless workstation configuration by the time solaris is 1/2 way through reading its secondary bootstrap..). I'm just planning to dd an existing disk image onto the local disk. It would be nice to be able to mount the Solaris root partition & touch a few configuration files... If anybody has done something similar and can offer advice, please ping me. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 19:42:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 4F26E37B423 for ; Tue, 19 Sep 2000 19:42:52 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 19 Sep 2000 21:44:41 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8K2gpG83014 for ; Tue, 19 Sep 2000 21:42:51 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1] (may be forged)) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8K2gnG03719 for ; Tue, 19 Sep 2000 21:42:49 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009200242.e8K2gnG03719@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Running natd on more than one interface... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 21:42:49 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a home network that talks to the world-at-large using natd to do the address translation on my gateway machine. However, I've just started tunneling (over an encrypted link) to another place using the tun interface. I'd like to have it translated as well. Has anyone tried running natd on more than one interface? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 20: 5:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 75F3337B423 for ; Tue, 19 Sep 2000 20:05:09 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id XAA12502 for ; Tue, 19 Sep 2000 23:08:22 -0400 Date: Tue, 19 Sep 2000 23:08:22 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: writing(2) to raw devices 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 Design and Implementation of the 4.4BSD Operating System, the write(2) system call must go through vn_write(), ffs_write(), ffs_balloc(), cluster(), bio() and finally dev() which performs the actual disk write. Considering all this block-oriented overhead, how can dd(1) which calls write(2), perform raw io on devices such as /dev/rwd0? Doesn't write(2) confine the process to block io by its very nature? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 21:31:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by hub.freebsd.org (Postfix) with ESMTP id 6DE2D37B422 for ; Tue, 19 Sep 2000 21:31:09 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e8K4USI04081; Wed, 20 Sep 2000 00:30:28 -0400 (EDT) Date: Wed, 20 Sep 2000 00:30:28 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: writing(2) to raw devices 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 That is only if the write is to a file within a partition mounted as an FFS file system. vn_write() contains the VOP_WRITE switch, which will switch to the write implementation based on the vnode type. VOP_WRITE calls through the function hanging off the vnode in the vnode op vector at the offset specified by vop_write_desc (record defined in sys/compile/GENERIC/vnode_if.c -- generated by a perl script from sys/kern/vnode_if.src during kernel build). Finding out which write implementation is actually hanging off the vnode for the raw device is left as an exercise for the reader. -Chris On Tue, 19 Sep 2000, Marc Tardif wrote: > >From The Design and Implementation of the 4.4BSD Operating System, the > write(2) system call must go through vn_write(), ffs_write(), > ffs_balloc(), cluster(), bio() and finally dev() which performs the actual > disk write. Considering all this block-oriented overhead, how can dd(1) > which calls write(2), perform raw io on devices such as /dev/rwd0? Doesn't > write(2) confine the process to block io by its very nature? > > > > 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 Sep 19 22:34:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 893A037B424 for ; Tue, 19 Sep 2000 22:34:45 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA02177; Tue, 19 Sep 2000 22:35:18 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009200535.WAA02177@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Piotr Sroczynski" Cc: hackers@FreeBSD.ORG Subject: Re: PnP & 4.1 Release In-reply-to: Your message of "Sun, 17 Sep 2000 19:42:02 +0200." <39C51E8A.13856.5959D@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 22:35:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it possible to stop any PnP operation (checking, seting) during > boot? No. Could you describe your problem in more detail? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 22:34:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 96C7037B42C for ; Tue, 19 Sep 2000 22:34:52 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA02197; Tue, 19 Sep 2000 22:35:33 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009200535.WAA02197@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: implementing idle-time networking In-reply-to: Your message of "Mon, 18 Sep 2000 18:11:53 PDT." <39C6BD59.4C1AFD02@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 22:35:33 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Closer inspection revealed that both the ifnet ifqueues as well as the > driver transmission chain are always empty upon enqueue/dequeue. Thus, even > though my fancy queuing code is executed, it has no effect, since there > never are any queues. > > Can someone shed some light on if this is expected behavior? Wouldn't that > mean that as packets are being generated by the socket layer, they are > handed down through the kernel to the driver one-by-one, incurring at > interrupt for each packet? Or am I missing the obvious? Packets are pushed down as far as they can go, ie. if the card has resources available to take another packet you'll go all the way into the device driver. It's not until you actually run the card out of resources that the various queues start to fill up. The actual interrupt rate depends on the specific card; many of the better cards have interrupt-reduction features that eg. only signal an interrupt when they have completed a set of transmitted packets, or no more than once every Nms, etc. Otherwise, you're going to take one interrupt per packet anyway. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 22:35: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 46E3937B424 for ; Tue, 19 Sep 2000 22:34:53 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA02187; Tue, 19 Sep 2000 22:35:26 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009200535.WAA02187@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: papowell@astart.com Cc: freebsd-hackers@freebsd.org Subject: Re: Device driver, memory map failing, and it is probably obvious In-reply-to: Your message of "Sun, 17 Sep 2000 19:20:43 PDT." <200009180220.TAA12263@h4.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 22:35:26 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > found 'Digi International PCI Classic 8 Serial Adapter' > > my0: \ > port 0xdc00-0xdcff,0xd800-0xd87f mem 0xea400000-0xea4000ff,0xea402000-0xea40207f \ > irq 12 at device 10.0 on pci0 > > digic_attach: unit 0, irq 12, slot 10, progif 0x0, iobase 0xd801, membase 0xea402000, irqline 0x10c > > my0: couldn't map memory > > device_probe_and_attach: my0 attach returned 6 > > So it found the card, discovered the vintage hardware id, and printed it out. > The we call the attach routine: > > > static int > > digic_attach( device_t dev ) > > { > > struct digic_softc *digic; > > int unit; > > int irq, slot, progif, iobase, membase, irqline; > > int error = 0; > > void *ih = 0; > > > > /* get the sc structure */ > > digic = device_get_softc(dev); > > bzero(digic,sizeof(digic[0])); bzero(digic, sizeof(*digic)) > > unit = device_get_unit(dev); Don't use this; use device_printf(); > > irq = pci_get_irq(dev); > > slot = pci_get_slot(dev); You don't need these. > > progif = pci_get_progif(dev); And you probably don't want that. > > #define WB_PCI_LOMEM 0x10 > > #define WB_PCI_LOIO 0x14 > > #define WB_PCI_INTLINE 0x3c > > iobase = pci_read_config(dev, WB_PCI_LOIO, 4); > > membase = pci_read_config(dev, WB_PCI_LOMEM, 4); > > irqline = pci_read_config(dev, WB_PCI_INTLINE, 4); You don't need these. > > DPRINTF(("digic_attach: unit %d, irq %d, slot %d, progif 0x%x, iobase 0x%x, membase 0x%x, irqline 0x%x\n", > > unit, irq, slot, progif, iobase, membase, irqline )); Use device_printf(). > > > > switch( pci_get_device(dev) ){ > > case PCI_CLASSIC_4: digic->digic_ports = 4; break; > > case PCI_CLASSIC_8: digic->digic_ports = 8; break; > > default: > > device_printf(dev,"digic_attach: bad device id! %d", pci_get_device(dev)); > > goto fail; > > } > > > > /* now get the memory resources */ > > digic->digic_mem_res = bus_alloc_resource(dev, SYS_RES_MEMORY, > > &digic->digic_mem_rid, > > 0, ~0, 256, RF_ACTIVE|RF_SHAREABLE); You have to initialise digic->digic_mem_rid first. Looking at the above, I'd guess it should be initialised to WB_PCI_LOMEM, which should actually be PCIR_MAPS. > > if (!digic->digic_mem_res) { > > device_printf(dev, "couldn't map memory\n"); > > goto fail; > > } > > Now, I am SURE that I must be doing something stupid here - but I snipped this code > right out of the code for another driver, and this one works. > > The only puzzle is: > > my0: \ > port 0xdc00-0xdcff,0xd800-0xd87f mem 0xea400000-0xea4000ff,0xea402000-0xea40207f \ > irq 12 at device 10.0 on pci0 > > Note that the diagnostic output indicates some VERY strange ranges. > Could this be the problem? I wouldn't say that any of these ranges are strange at all. You have a 256-byte and a 128-byte window in each of I/O and memory space. Looks fine to me. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 23: 5:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spock.org (cm-24-92-52-10.nycap.rr.com [24.92.52.10]) by hub.freebsd.org (Postfix) with ESMTP id BF7CA37B424 for ; Tue, 19 Sep 2000 23:05:12 -0700 (PDT) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F8823e8K659702049F7T for freebsd-hackers@freebsd.org; Wed, 20 Sep 2000 02:05:09 -0400 (EDT) (envelope-from jon) Date: Wed, 20 Sep 2000 02:05:09 -0400 From: Jonathan Chen To: freebsd-hackers@freebsd.org Subject: csa sound card not generating interrupt? Message-ID: <20000920020509.B55496@spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an IBM Thinkpad T20 and, after a snificant amount of pain, have been able to get everything working under FreeBSD except for sound. The laptop contains a CS4264 chip with a CS4297A AC97 codec, both of which detects fine as csa0 and pcm0. The memory range and irq in the pci config all appear to be set correctly. The problem is the the sound chip never once generated an interrupt, which results in "pcm0: {play,record} interrupt timeout, channel dead" every time I attempt to play/record. This error does not appear when playing short sound clips, but no sound is heard nonetheless. Upon further poking around, I confirmed that the card did not even attempt to generate an interrupt (interrupt status bit is low, but interrupt enable bit remains high). I've also tried Linux on the same computer (with their alsa sound driver), and sound works under Linux. Comparing the freebsd/alsa driver reveals that the attach routine of the two drivers does the same things! Yet, remarkably, one works and the other doesn't. Does anyone have any suggestions or pointers for this problem before I go crazy pulling all my hair out? Thanks. -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 19 23:41:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop3.gte.net (smtppop3pub.gte.net [206.46.170.22]) by hub.freebsd.org (Postfix) with ESMTP id CEF9E37B423 for ; Tue, 19 Sep 2000 23:41:24 -0700 (PDT) Received: from gte.net ([206.86.227.28]) by smtppop3.gte.net with ESMTP for ; id BAA27012332 Wed, 20 Sep 2000 01:37:27 -0500 (CDT) Message-ID: <39C85C48.E0225A3C@gte.net> Date: Tue, 19 Sep 2000 23:42:16 -0700 From: Soumen Biswas Reply-To: soumen.biswas@gte.net Organization: Netscaler Inc. X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: How to to increase kern malloc pool to 1024 M References: <20000920052453.6098137B423@hub.freebsd.org> 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 am using FreeBSD 2.2.5-RELEASE on a m/c with 2046MB RAM Is it possible to fine tune the kernel to increase the malloc(9) pool to 1024 MB Can it be done by adjusting ( LOAD_ADDRESS, VM_KMEM_SIZE & NKPDE ) ?? If so what is the maximum that i can go. Thanx Soumen BTW I tried the following and could allocate upto 128*3 MB How are the following three params related ??? LOAD_ADDRESS = C010000 NKPDE = 255 VM_KMEM_SIZE = (512 * 1024 * 1024) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 1:57:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mazurek.man.lodz.pl (mazurek.man.lodz.pl [212.51.192.15]) by hub.freebsd.org (Postfix) with ESMTP id D0D3437B422 for ; Wed, 20 Sep 2000 01:57:07 -0700 (PDT) Received: from adas (pb164.lodz.ppp.tpnet.pl [212.160.29.164]) by mazurek.man.lodz.pl (8.9.3/8.9.3) with ESMTP id KAA07373; Wed, 20 Sep 2000 10:56:03 +0200 From: "Piotr Sroczynski" To: "Matthew N. Dodd" Date: Wed, 20 Sep 2000 10:57:43 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: PnP & 4.1 Release Cc: hackers@FreeBSD.ORG Message-ID: <39C89827.31219.15DAE5@localhost> References: <39C68CBA.21143.330132@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > First has SMC EliteULTRA 8416 software selectable PnP operation > > - ethernet > > The 'ed' driver doesn't support SMC cards in PnP mode. (Or rather it > doesn't support SMC cards in non shared memory mode which is what they run > in when configured via PnP.) I know about it but 'ed' in 4.1R doesn't support SMC 8416 in any mode set (PnP /not PnP, PIO/shared mem.), because it aways treat 'ed' as PnP device and reprogram it on his own. With SMC 8216 (no PnP dev.) I haven't any problem. Piotr Sroczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 2: 0: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A7F8637B423 for ; Wed, 20 Sep 2000 01:59:58 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id EAA92059; Wed, 20 Sep 2000 04:59:45 -0400 (EDT) Date: Wed, 20 Sep 2000 04:59:45 -0400 (EDT) From: "Matthew N. Dodd" To: Piotr Sroczynski Cc: hackers@FreeBSD.ORG Subject: Re: PnP & 4.1 Release In-Reply-To: <39C89827.31219.15DAE5@localhost> 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, 20 Sep 2000, Piotr Sroczynski wrote: > I know about it but 'ed' in 4.1R doesn't support SMC 8416 in any mode > set (PnP /not PnP, PIO/shared mem.), because it aways treat 'ed' as > PnP device and reprogram it on his own. With SMC 8216 (no PnP dev.) I > haven't any problem. You're configuring the card using the EZSetup DOS config utility? You need to get the right version of the utility and run it with the flags that tell it to disable PnP on ALL cards in the box. I've had problems disabling PnP with the wrong config utility version and wrong flags. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 2:37:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 36ACD37B422; Wed, 20 Sep 2000 02:37:37 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bgJq-0003Hy-00; Wed, 20 Sep 2000 12:37:34 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bfhE-00015w-00; Wed, 20 Sep 2000 11:57:40 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Tue, 19 Sep 2000 16:41:29 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 11:57:40 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bug report: in lib/libstand/bootp.c: if (IN_CLASSA(myip.s_addr)) nmask = htonl(IN_CLASSA_NET); else if (IN_CLASSB(myip.s_addr)) nmask = htonl(IN_CLASSB_NET); else nmask = htonl(IN_CLASSC_NET); should be: if (IN_CLASSA(ntohl(myip.s_addr))) nmask = htonl(IN_CLASSA_NET); else if (IN_CLASSB(ntohl(myip.s_addr))) nmask = htonl(IN_CLASSB_NET); else nmask = htonl(IN_CLASSC_NET); which explains why gateway was zero, even if it was provided by dhcp. it also explains why it hung trying to mount via nfs. danny In message <20000919164129.A39104@elvis.mu.org>you write: }Danny Braniss (danny@cs.huji.ac.il) wrote: }> In message <20000919024512.A27691@elvis.mu.org>you write: }> }> }set this in your dhcpd.conf, but yes, I will fix it. }> i know it should be in dhcpd.conf but what? :-) btw, i tried router but zilc }h. } }option routers ip; } }> } }> }> 2- if i set different hosts for dhcpd, tftpd, root and swap i get into }> }> all sort of problems. the most anoying one is that the bios-pxe boot w }ill }> }> try and tftpboot from the wrong server. so im using 'option swap-serve }r' }> } }> }I dont follow. }> } }> }> if i set: }> option root-path "132.65.16.6:/vol1/roots/fbsd-4.1S"; }> then the ip gets chunked, and it will try to mount from the tftp server - }> bummer } }Yeah.. I have not wanted to do this. I'll look at this in a little while. } }> if i set }> option next-server myrootserver }> the pxe-bios will use it for the tftpd - bummer } }please read the PXE specs to see how to tell it to grab the tftp loader }from a different server. } }> so, at the moment i use }> option swap-server myrootserver; }> and it works. but it should be less blackmagic. also, what if i want a }> different }> root and swap server? } }I'll fix it if I get time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 5: 5:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 4DCA737B423 for ; Wed, 20 Sep 2000 05:05:55 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8KCKbP48664; Wed, 20 Sep 2000 08:20:37 -0400 (EDT) Date: Wed, 20 Sep 2000 08:20:37 -0400 (EDT) From: Jim Flowers To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: Running natd on more than one interface... In-Reply-To: <200009200242.e8K2gnG03719@bloop.craftncomp.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 Yes. Just use a separate process for each with different ports for the divert. This is useful inbound when you want the source of an external connection to have a local address. Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Tue, 19 Sep 2000, Stephen Hocking wrote: > > I have a home network that talks to the world-at-large using natd to do the > address translation on my gateway machine. However, I've just started > tunneling (over an encrypted link) to another place using the tun interface. > I'd like to have it translated as well. Has anyone tried running natd on more > than one interface? > > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 6:37:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sneety.insync.net (sneety.insync.net [209.113.65.5]) by hub.freebsd.org (Postfix) with ESMTP id A15C037B423 for ; Wed, 20 Sep 2000 06:37:25 -0700 (PDT) Received: from Matt (209-113-91-158.insync.net [209.113.91.158]) by sneety.insync.net (8.9.3/8.9.3) with SMTP id IAA25957 for ; Wed, 20 Sep 2000 08:37:23 -0500 (CDT) Reply-To: From: "Matt Bettinger" To: Subject: sound and gdk errors Date: Wed, 20 Sep 2000 08:35:26 -0500 Message-ID: <71F816A89AA9D3119F4C00D0B7094EFC198F84@FIN_SYN> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0006_01C022DD.FDBB4800" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C022DD.FDBB4800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Posted this to freebsd questions without much of a response so going to give it a shot here in hackers.. getting some errors here have pcm compiled in my kernel and did a make /dev/snd0 as root. still no sound. snd0 does not even come up in dmesg. also, when i shut down X (using enlightenment and the X server that came with the 4.1 cd's) i get the following: Gdk-Warning **: locale not supported by C library Gdk-Warning **: locale not supported by C library Gtk-Warning **: gtk_signal_disconnect_by_data ():could not find handler containing data (0x814A00) as a regular user when I try 'startx' i get Fatal Server Error: xf860open console: Server must be run with root permissions. Should be using Xwrapper. pid 250 (sound properties), uid 0:exited on signal 6 (core dumped) when i reboot and the kernel loads i get the following message: local package initialization xinetd[204] : open (/etc/xinetd.conf) failed:no such file or directory (errno=2) xinetd [204]: {init_services} couldn't get confiduration. Exit xinetd. ----thank you for any insight. sorry if this is not wrapped right, as i am using work email via the web. Matt mail.insync.net Matthew Bettinger Financial Synergies,Inc. 1177 West Loop South, Suite 1400 Houston,Texas 77027-9086 www.fwalling.com 713-623-6600 713-623-6771 FAX ------=_NextPart_000_0006_01C022DD.FDBB4800 Content-Type: text/x-vcard; name="Bettinger, Matt (E-mail).vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Bettinger, Matt (E-mail).vcf" BEGIN:VCARD VERSION:2.1 N:Bettinger;Matt FN:Matt Bettinger (E-mail) ORG:Financial Synergies, Inc. TEL;WORK;VOICE:+1 713-623-6600 TEL;HOME;VOICE:+1 713-436-3220 TEL;WORK;FAX:+1 713-623-6771 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;1177 West Loop = South=3D0D=3D0ASuite 1400;Houston;Texas;77027-9086;United State=3D s of America LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:1177 West Loop = South=3D0D=3D0ASuite 1400=3D0D=3D0AHouston, Texas = 77027-9086=3D0D=3D0AUni=3D ted States of America EMAIL;PREF;INTERNET:mattb@finsyn.com REV:20000616T132045Z END:VCARD ------=_NextPart_000_0006_01C022DD.FDBB4800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 6:46: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sneety.insync.net (sneety.insync.net [209.113.65.5]) by hub.freebsd.org (Postfix) with ESMTP id 613B337B422 for ; Wed, 20 Sep 2000 06:46:00 -0700 (PDT) Received: from Matt (209-113-91-158.insync.net [209.113.91.158]) by sneety.insync.net (8.9.3/8.9.3) with SMTP id IAA27795 for ; Wed, 20 Sep 2000 08:45:59 -0500 (CDT) Reply-To: From: "Matt Bettinger" To: Subject: snd0 gdk/gtk errors Date: Wed, 20 Sep 2000 08:44:03 -0500 Message-ID: <71F816A89AA9D3119F4C00D0B7094EFC198F87@FIN_SYN> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000B_01C022DF.31AAC360" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C022DF.31AAC360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > Posted this to freebsd questions without much of a response so going to give > it a shot here in hackers.. > getting some errors here have pcm compiled in my kernel and did a make > /dev/snd0 as root. > still no sound. snd0 does not even come up in dmesg. > also, when i shut down X (using enlightenment and the X server that came > with the 4.1 > cd's) i get the following: > Gdk-Warning **: locale not supported by C library > Gdk-Warning **: locale not supported by C library > Gtk-Warning **: gtk_signal_disconnect_by_data ():could not find handler > containing data > (0x814A00) > as a regular user when I try 'startx' i get > Fatal Server Error: > xf860open console: Server must be run with root permissions. Should be > using Xwrapper. > pid 250 (sound properties), uid 0:exited on signal 6 (core dumped) > when i reboot and the kernel loads i get the following message: > local package initialization xinetd[204] : open (/etc/xinetd.conf) failed:no > such file or > directory (errno=2) > xinetd [204]: {init_services} couldn't get confiduration. > Exit xinetd. > ----thank you for any insight. sorry if this is not wrapped right, as i am > using work > email via the web. > Matt > mail.insync.net Matthew Bettinger Financial Synergies,Inc. 1177 West Loop South, Suite 1400 Houston,Texas 77027-9086 713-623-6600 713-623-6771 FAX ------=_NextPart_000_000B_01C022DF.31AAC360 Content-Type: text/x-vcard; name="Bettinger, Matt (E-mail).vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Bettinger, Matt (E-mail).vcf" BEGIN:VCARD VERSION:2.1 N:Bettinger;Matt FN:Matt Bettinger (E-mail) ORG:Financial Synergies, Inc. TEL;WORK;VOICE:+1 713-623-6600 TEL;HOME;VOICE:+1 713-436-3220 TEL;WORK;FAX:+1 713-623-6771 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;1177 West Loop = South=3D0D=3D0ASuite 1400;Houston;Texas;77027-9086;United State=3D s of America LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:1177 West Loop = South=3D0D=3D0ASuite 1400=3D0D=3D0AHouston, Texas = 77027-9086=3D0D=3D0AUni=3D ted States of America EMAIL;PREF;INTERNET:mattb@finsyn.com REV:20000616T132045Z END:VCARD ------=_NextPart_000_000B_01C022DF.31AAC360-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 8:19:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 96A3737B422; Wed, 20 Sep 2000 08:19:29 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA09412; Thu, 21 Sep 2000 02:18:52 +1100 Date: Thu, 21 Sep 2000 02:18:48 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Marc Tardif Cc: "Aleksandr A.Babaylov" , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention 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, 18 Sep 2000, Marc Tardif wrote: > > 0cicuta/home/babolo(9)#dd of=/dev/wd0s2 if=/dev/zero bs=660b > > 1cicuta/home/babolo(11)#od -b /dev/wd0s2 > [ snip ] > > Why I use 2.2.7 for test? > > Because of my lovely 4.1-STABLE is extremly unstable with content of > > ad0s2 (wd0s2) above and silently reboot after the first dd in the test above. > > > Assuming my wd0s2 is still unused and of size 0, 3.5-STABLE also crashes in the test above (no disk activity, ctrl-c doesn't work, alt-f# doesn't work either). Perhaps it eventually reboots, but I wasn't patient enough to wait that long. One solution to this problem is to specify the count blocks after which dd returns properly but still no bytes are copied. [Please use lines somewhat shorter than 360 characters.] This is a completely diferent problem. wd0s2 was buffered in 3.5, and buffered devices are very broken in 3.1 and later versions of 3.x (write errors are retried endlessly. Among other bugs, writing beyond EOF hangs the system when it allocates all buffers for writing unwritable data). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 9: 8:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C0DF637B42C; Wed, 20 Sep 2000 09:08:54 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA21433; Wed, 20 Sep 2000 12:10:18 -0400 (EDT) Message-Id: <200009201610.MAA21433@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 20 Sep 2000 12:08:45 -0400 To: Mike Smith From: Dennis Subject: Re: Serial port locks up 4.1 Cc: hackers@freebsd.org In-Reply-To: <200009192341.QAA00943@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:41 PM 09/19/2000 -0700, you wrote: >> >> FYI: It seems that if you try to access the serial port on a MB with the >> port disabled, freebsd 4.1 will freeze up solid. Enabling the serial >> console will cause a lock up on boot, and any access to the port will do it >> as well. > >This is probably a feature of the board/super-IO chipset in question. > >In particular, the port should never have probed successfully if the port >was really "disabled", so you should never have been able to access it in >the first place. Its displays an error, but installs it anyway, so it seems that the driver is at least partially at fault. It happens on several very different MBs (both SBCs and ATX MBs), so its not an isolated issue. > >The correct solution, of course, is "don't do that". Easy to say , but it might be very hard to find if you have a serial console enabled and the machine just wont boot. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 9:30:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id A106237B422; Wed, 20 Sep 2000 09:30:31 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id D6F782B229; Wed, 20 Sep 2000 11:30:25 -0500 (CDT) Date: Wed, 20 Sep 2000 09:30:25 -0700 From: Paul Saab To: Danny Braniss Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000920093025.A53255@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Wed, Sep 20, 2000 at 11:57:40AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm.. I'm using the netboot just fine here for the ports cluster and it is using the code in the tree w/ zero modifications. It boots via nfs and comes up with ip, netmask, and gateway. paul Danny Braniss (danny@cs.huji.ac.il) wrote: > bug report: > in lib/libstand/bootp.c: > > if (IN_CLASSA(myip.s_addr)) > nmask = htonl(IN_CLASSA_NET); > else if (IN_CLASSB(myip.s_addr)) > nmask = htonl(IN_CLASSB_NET); > else > nmask = htonl(IN_CLASSC_NET); > should be: > > if (IN_CLASSA(ntohl(myip.s_addr))) > nmask = htonl(IN_CLASSA_NET); > else if (IN_CLASSB(ntohl(myip.s_addr))) > nmask = htonl(IN_CLASSB_NET); > else > nmask = htonl(IN_CLASSC_NET); > > which explains why gateway was zero, even if it was provided by dhcp. > it also explains why it hung trying to mount via nfs. > > danny > > In message <20000919164129.A39104@elvis.mu.org>you write: > }Danny Braniss (danny@cs.huji.ac.il) wrote: > }> In message <20000919024512.A27691@elvis.mu.org>you write: > }> > }> }set this in your dhcpd.conf, but yes, I will fix it. > }> i know it should be in dhcpd.conf but what? :-) btw, i tried router but zilc > }h. > } > }option routers ip; > } > }> } > }> }> 2- if i set different hosts for dhcpd, tftpd, root and swap i get into > }> }> all sort of problems. the most anoying one is that the bios-pxe boot w > }ill > }> }> try and tftpboot from the wrong server. so im using 'option swap-serve > }r' > }> } > }> }I dont follow. > }> } > }> > }> if i set: > }> option root-path "132.65.16.6:/vol1/roots/fbsd-4.1S"; > }> then the ip gets chunked, and it will try to mount from the tftp server - > }> bummer > } > }Yeah.. I have not wanted to do this. I'll look at this in a little while. > } > }> if i set > }> option next-server myrootserver > }> the pxe-bios will use it for the tftpd - bummer > } > }please read the PXE specs to see how to tell it to grab the tftp loader > }from a different server. > } > }> so, at the moment i use > }> option swap-server myrootserver; > }> and it works. but it should be less blackmagic. also, what if i want a > }> different > }> root and swap server? > } > }I'll fix it if I get time. > > > > -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 9:49:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 5805337B422 for ; Wed, 20 Sep 2000 09:49:39 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JUEMZEWJ68000IBJ@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 20 Sep 2000 18:49:37 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 20 Sep 2000 18:49:36 +0100 Content-return: allowed Date: Wed, 20 Sep 2000 18:49:36 +0100 From: "Koster, K.J." Subject: Executable packages (long, sorry) To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D78DA@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, While we're on the subject of packaging formats, I would like to present an idea that has been running around in the back of my head. Years ago I had the pleasure of playing with a new RiscPC by Acorn. If you create a directory on RiscOS and stick a little BASIC script in with exactly the right name, RiscOS will treat that directory as an executable. You can use the directory to stick in whatever the application needs, and the user never needs to bother. Uninstalling it is as easy as the RiscOS equivalent of "rm -rf". Riding on the wave of the unified BSD packages effort, this might be a good time to rekindle that idea. Say that we agree on some form of uniform package layout. You'd say that man pages go into $PKG_BASE/$PKG_NAME/man, and that libraries go into $PKG_BASE/$PKG_NAME/lib, and that there is probably a script named $PKG_BASE/$PKG_NAME/etc/rc that takes the arguments "start" and "stop" for system startup. A script named $PKG_BASE/$PKG_NAME/bin/run is invoked when a user types $PKG_NAME at the command prompt (triggered by a script in /usr/local/bin, which is symlinked to $PKG_NAME. We are already doing this now, but instead we scatter packages across the filesystem, keeping file lists of where we left the various body parts of the port. So is this a bad idea? I don't think so. Some programs already install themselves in a similar fashion. If you'll allow me to use Tomcat as an example. After you have installed it, only /usr/local/tomcat new on your system. It has its own bin/, conf/ and lib/ directory. Deinstalling is as simple as it is on a RiscPC. There are other places too, where you see this self-containment crop up. The executable JAR files from Java, for example. And someone over at KDE or Gnome (or some desktop kit like that, I can't tell them apart) mentioned that they were going to do a ZIP archive abstraction, much like they did with the file system. You could easily make a zip archive behave like an executable. I do not think that this is the perfect solution to system clobbering. In fact, there are some good examples of stuff that should really not be installed in an executable directory. The GNU tools spring to mind. They were written according to a UNIX utility philosophy, and should be treated as such. Other things, such as a web server, or a word processor are much more self contained. I hope that you will remember this idea when you find yourself staring at traces of an old port, unsure if you should delete it or not. :-) Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 11: 2:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 64E9B37B423; Wed, 20 Sep 2000 11:02:20 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e8KI2Fe45459; Wed, 20 Sep 2000 11:02:15 -0700 (PDT) (envelope-from dillon) Date: Wed, 20 Sep 2000 11:02:15 -0700 (PDT) From: Matt Dillon Message-Id: <200009201802.e8KI2Fe45459@earth.backplane.com> To: Paul Saab Cc: Danny Braniss , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation References: <20000920093025.A53255@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A quick review of the code seems to indicate that this is indeed a bug. As far as I can tell, the IN_CLASS*() macros assume host order. e.g. from /usr/include/netinet/in.h: #define IN_CLASSA(i) (((u_int32_t)(i) & 0x80000000) == 0) Since s_addr is in network byte order, the conversion is necessary. If this fixes Danny's problems, and doesn't break anyone else (Paul?), I'd say it should be committed. -Matt :Umm.. I'm using the netboot just fine here for the ports cluster and :it is using the code in the tree w/ zero modifications. It boots via :nfs and comes up with ip, netmask, and gateway. : :paul : :Danny Braniss (danny@cs.huji.ac.il) wrote: :> bug report: :> in lib/libstand/bootp.c: :> :> if (IN_CLASSA(myip.s_addr)) :> nmask = htonl(IN_CLASSA_NET); :> else if (IN_CLASSB(myip.s_addr)) :> nmask = htonl(IN_CLASSB_NET); :> else :> nmask = htonl(IN_CLASSC_NET); :> should be: :> :> if (IN_CLASSA(ntohl(myip.s_addr))) :> nmask = htonl(IN_CLASSA_NET); :> else if (IN_CLASSB(ntohl(myip.s_addr))) :> nmask = htonl(IN_CLASSB_NET); :> else :> nmask = htonl(IN_CLASSC_NET); :> :> which explains why gateway was zero, even if it was provided by dhcp. :> it also explains why it hung trying to mount via nfs. :> :> danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 11: 7:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 090F037B422; Wed, 20 Sep 2000 11:07:50 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 868B92B230; Wed, 20 Sep 2000 13:07:44 -0500 (CDT) Date: Wed, 20 Sep 2000 11:07:44 -0700 From: Paul Saab To: Matt Dillon Cc: Danny Braniss , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation Message-ID: <20000920110744.A55357@elvis.mu.org> References: <20000920093025.A53255@elvis.mu.org> <200009201802.e8KI2Fe45459@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009201802.e8KI2Fe45459@earth.backplane.com>; from dillon@earth.backplane.com on Wed, Sep 20, 2000 at 11:02:15AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon (dillon@earth.backplane.com) wrote: > A quick review of the code seems to indicate that this is indeed a bug. > As far as I can tell, the IN_CLASS*() macros assume host order. e.g. > from /usr/include/netinet/in.h: > > #define IN_CLASSA(i) (((u_int32_t)(i) & 0x80000000) == 0) > > Since s_addr is in network byte order, the conversion is necessary. If > this fixes Danny's problems, and doesn't break anyone else (Paul?), I'd > say it should be committed. After playing with it somemore, I agree.. It doesn't break for small networks, which is what I was testing on. I'll commit the fix. paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 11:15:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 35BAA37B424; Wed, 20 Sep 2000 11:15:44 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13boP0-0003yP-00; Wed, 20 Sep 2000 21:15:26 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13boOy-0001Sj-00; Wed, 20 Sep 2000 21:15:24 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: Matt Dillon , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation In-reply-to: Your message of Wed, 20 Sep 2000 11:07:44 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 21:15:24 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000920110744.A55357@elvis.mu.org>you write: }Matt Dillon (dillon@earth.backplane.com) wrote: }> A quick review of the code seems to indicate that this is indeed a bug. }> As far as I can tell, the IN_CLASS*() macros assume host order. e.g. }> from /usr/include/netinet/in.h: }> }> #define IN_CLASSA(i) (((u_int32_t)(i) & 0x80000000) == 0) }> }> Since s_addr is in network byte order, the conversion is necessary. If }> this fixes Danny's problems, and doesn't break anyone else (Paul?), I'd }> say it should be committed. } }After playing with it somemore, I agree.. It doesn't break for small }networks, which is what I was testing on. I'll commit the fix. } i still think that this part of code is useless. why overwride the info supplied by dhcp? if it's wrong then the dhcpd.conf should be fixed or some message printed. at the moment, bootp silently ignores some info it conciders wrong - wrongly :-) danny }paul } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 11:32:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 18B1D37B422; Wed, 20 Sep 2000 11:32:34 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id B37162B23C; Wed, 20 Sep 2000 13:32:33 -0500 (CDT) Date: Wed, 20 Sep 2000 11:32:33 -0700 From: Paul Saab To: Danny Braniss Cc: Matt Dillon , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation Message-ID: <20000920113233.B55357@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Wed, Sep 20, 2000 at 09:15:24PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > i still think that this part of code is useless. why overwride the > info supplied by dhcp? if it's wrong then the dhcpd.conf should be > fixed or some message printed. at the moment, bootp silently ignores > some info it conciders wrong - wrongly :-) This is required if no netmask is passed. Atleast that is the way I am reading it. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 12:42:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tdnet.com.br (lince.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 04ACD37B424 for ; Wed, 20 Sep 2000 12:42:26 -0700 (PDT) Received: from tdnet.com.br [200.236.148.135] by tdnet.com.br with ESMTP (SMTPD32-5.05) id A30C1AC400D2; Wed, 20 Sep 2000 16:42:04 -0300 Message-ID: <39C8E94E.2EB59BC3@tdnet.com.br> Date: Wed, 20 Sep 2000 16:43:58 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: cannot install freebsd over a 15 GB IDE Disk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear gentleman, i amgetting crazy since i cannot install my freebsd over a 15GB ide disk! I am sure i have seen messages in the questions mailing list about that, but i could not find than from search web interface. Since, i would be glad if you could help getting this error out off. Thanks a lot for your time and cooperation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 12:47: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.uncanny.net (ns2.uncanny.net [140.174.20.7]) by hub.freebsd.org (Postfix) with ESMTP id 4DE4E37B43C; Wed, 20 Sep 2000 12:46:56 -0700 (PDT) Received: from sandbox.uncanny.net (sandbox.uncanny.net [140.174.20.254]) by ns2.uncanny.net (8.9.2/8.9.2) with ESMTP id MAA45703; Wed, 20 Sep 2000 12:58:27 -0700 (PDT) (envelope-from ee@uncanny.net) Message-Id: <200009201958.MAA45703@ns2.uncanny.net> To: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Frustration with SCSI system Reply-To: Edward Elhauge Date: Wed, 20 Sep 2000 12:58:27 -0700 From: Edward Elhauge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Freebsders, I've been using FreeBSD over the last 6 years (since I switched from NetBSD) to run a small ISP out of my basement. I've had about six disk crashes in as many years and still don't know how to work reliably with them. I have installed UPS boxes on each machine and that seems to have lowered the incidence of failure, but failures still happen; yesterday during our heat wave in the San Francisco area (possible brownouts also) I had another. OK, so you have to expect these things; but I never seem to find an easy way to recover these systems. The only thing that I've seen work has been to mount the disk on another system, back it up, reformat the drive, copy things back over and find out what was trashed. THERE MUST BE A BETTER WAY. It seems like SCSI systems can't use the bad144 program. They are supposed to autorecover on bad sectors, but every system that I've had to recover seems to be in a state where the bad sectors aren't remapping. I've tried buying top of the line hardware, and it does work faster, but no more reliably than the cheap stuff. Once you get in this state it is difficult to mount the partitions so as to recover what is there. I really need some good advice here. Do I need to buy RAID hardware for each and every server in my network? Is there some way to force the SCSI system to remap bad drives? The error I'm getting is: MEDIUM ERROR info:1010f asc:14,1 My configuration is: 1) Pentium-S 100 Mz 2) 128M 3) Adaptec 2940 Ultra/Ultra SCSI with Bios 1.25 4) Seagate ST3437 4GB 5) FreeBSD 3.4 Any advice on how to efficiently bring my server back up or how I can reengineer my system to avoid this in the future, will be greatly appreciated. -- Edward Elhauge -- Uncanny Inc., San Francisco "War is like love; it always finds a way." -- Bertold Brecht To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 12:51:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 875C737B424; Wed, 20 Sep 2000 12:51:30 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8KJpTM12733; Wed, 20 Sep 2000 12:51:29 -0700 (PDT) Date: Wed, 20 Sep 2000 12:51:29 -0700 From: Alfred Perlstein To: Edward Elhauge Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20000920125128.F9141@fw.wintelcom.net> References: <200009201958.MAA45703@ns2.uncanny.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200009201958.MAA45703@ns2.uncanny.net>; from ee@uncanny.net on Wed, Sep 20, 2000 at 12:58:27PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Edward Elhauge [000920 12:48] wrote: > Hello Freebsders, > > I've been using FreeBSD over the last 6 years (since I switched from > NetBSD) to run a small ISP out of my basement. > > I've had about six disk crashes in as many years and still don't know how > to work reliably with them. "man vinum" software mirroring == good. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 12:58:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id C726A37B422; Wed, 20 Sep 2000 12:58:15 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13bq0U-0004nb-00; Wed, 20 Sep 2000 19:58:14 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8KJxZY02880; Wed, 20 Sep 2000 21:59:35 +0200 (CEST) (envelope-from wkb) Date: Wed, 20 Sep 2000 21:59:35 +0200 From: Wilko Bulte To: Edward Elhauge Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Frustration with SCSI system Message-ID: <20000920215935.G2695@freebie.demon.nl> References: <200009201958.MAA45703@ns2.uncanny.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009201958.MAA45703@ns2.uncanny.net>; from ee@uncanny.net on Wed, Sep 20, 2000 at 12:58:27PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 12:58:27PM -0700, Edward Elhauge wrote: > I've been using FreeBSD over the last 6 years (since I switched from > NetBSD) to run a small ISP out of my basement. > > I've had about six disk crashes in as many years and still don't know how > to work reliably with them. > > I have installed UPS boxes on each machine and that seems to have lowered > the incidence of failure, but failures still happen; yesterday during our > heat wave in the San Francisco area (possible brownouts also) I had > another. How hot gets your machine room/basement? > OK, so you have to expect these things; but I never seem to find an easy > way to recover these systems. The only thing that I've seen work has been > to mount the disk on another system, back it up, reformat the drive, copy > things back over and find out what was trashed. THERE MUST BE A BETTER > WAY. Yes. It is called RAID. Either in hardware or in software, using vinum. > It seems like SCSI systems can't use the bad144 program. They are supposed > to autorecover on bad sectors, but every system that I've had to recover > seems to be in a state where the bad sectors aren't remapping. I've tried > buying top of the line hardware, and it does work faster, but no more > reliably than the cheap stuff. Once you get in this state it is difficult > to mount the partitions so as to recover what is there. There are a finite amount of replacement blocks on each SCSI disk. Once they are given out you are toast. > I really need some good advice here. Do I need to buy RAID hardware for > each and every server in my network? Is there some way to force the SCSI > system to remap bad drives? > > The error I'm getting is: > MEDIUM ERROR info:1010f asc:14,1 Is automatic READ/WRITE remapping enabled on those drives? The real disk gurus (Ken, Justin) will want to know which disk types you have. camcontrol devlist or the dmesg.boot will tell them -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13: 6:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id D7F0937B423; Wed, 20 Sep 2000 13:06:20 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id QAA16638; Wed, 20 Sep 2000 16:09:13 -0400 Date: Wed, 20 Sep 2000 16:09:13 -0400 (EDT) From: Marc Tardif To: Alfred Perlstein Cc: Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <20000920125128.F9141@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've been using FreeBSD over the last 6 years (since I switched from > > NetBSD) to run a small ISP out of my basement. > > > > I've had about six disk crashes in as many years and still don't know how > > to work reliably with them. > > "man vinum" > > software mirroring == good. > What would be the incentives to using vinum instead of simply concatenating drives in a RAID-1 array (or whatever) using ccd(4)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:12: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id A207D37B424; Wed, 20 Sep 2000 13:12:05 -0700 (PDT) Received: by heorot.1nova.com (Postfix, from userid 1000) id B2A313288; Tue, 19 Sep 2000 12:35:50 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id 9A4583287; Tue, 19 Sep 2000 12:35:50 +0000 (GMT) Date: Tue, 19 Sep 2000 12:35:50 +0000 (GMT) From: Rick Hamell To: Edward Elhauge Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Frustration with SCSI system In-Reply-To: <200009201958.MAA45703@ns2.uncanny.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have installed UPS boxes on each machine and that seems to have lowered > the incidence of failure, but failures still happen; yesterday during our > heat wave in the San Francisco area (possible brownouts also) I had > another. Lots of fans in the cases... I had a fan go out in one of mine just a couple of days ago. It was about 75 or so, pulled the computer apart and almost burned myself on the drive! It was too hot to touch. Luckily it only ran that way for a day or two... but I'd still suspect it from no on and will be moving it down to a less critical system ASAP. I suspect you're seeing similar problems. Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:12:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.uncanny.net (ns2.uncanny.net [140.174.20.7]) by hub.freebsd.org (Postfix) with ESMTP id 1F40437B43E; Wed, 20 Sep 2000 13:12:49 -0700 (PDT) Received: from sandbox.uncanny.net (sandbox.uncanny.net [140.174.20.254]) by ns2.uncanny.net (8.9.2/8.9.2) with ESMTP id NAA45822; Wed, 20 Sep 2000 13:24:34 -0700 (PDT) (envelope-from ee@uncanny.net) Message-Id: <200009202024.NAA45822@ns2.uncanny.net> To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-reply-to: Your message of "Wed, 20 Sep 2000 12:51:29 PDT." <20000920125128.F9141@fw.wintelcom.net> Date: Wed, 20 Sep 2000 13:24:34 -0700 From: Edward Elhauge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, vinum is good. But my understanding is that you can't use vinum on your root partition. By Murphy's Law it always seems to be root that gets screwed up. And that also causes the biggest problems because then you have to yank the system apart and find another host disk for booting. Well spoken Alfred Perlstein wrote: >* Edward Elhauge [000920 12:48] wrote: >> Hello Freebsders, >> >> I've been using FreeBSD over the last 6 years (since I switched from >> NetBSD) to run a small ISP out of my basement. >> >> I've had about six disk crashes in as many years and still don't know how >> to work reliably with them. > >"man vinum" > >software mirroring == good. > >:) > >-Alfred -- Edward Elhauge -- Uncanny Inc., San Francisco "War is like love; it always finds a way." -- Bertold Brecht To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:17:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id A797C37B423; Wed, 20 Sep 2000 13:17:06 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13bqIj-00058M-00; Wed, 20 Sep 2000 20:17:05 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8KKIQH03106; Wed, 20 Sep 2000 22:18:26 +0200 (CEST) (envelope-from wkb) Date: Wed, 20 Sep 2000 22:18:26 +0200 From: Wilko Bulte To: Marc Tardif Cc: Alfred Perlstein , Edward Elhauge , freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Frustration with SCSI system Message-ID: <20000920221826.A2971@freebie.demon.nl> References: <20000920125128.F9141@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from intmktg@CAM.ORG on Wed, Sep 20, 2000 at 04:09:13PM -0400 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 04:09:13PM -0400, Marc Tardif wrote: > > > I've been using FreeBSD over the last 6 years (since I switched from > > > NetBSD) to run a small ISP out of my basement. > > > > > > I've had about six disk crashes in as many years and still don't know how > > > to work reliably with them. > > > > "man vinum" > > > > software mirroring == good. > > > What would be the incentives to using vinum instead of simply > concatenating drives in a RAID-1 array (or whatever) using ccd(4)? ?? Concatenating != mirroring aka RAID-1 -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:21:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 48F5537B422; Wed, 20 Sep 2000 13:21:07 -0700 (PDT) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA84315; Wed, 20 Sep 2000 15:21:02 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 20 Sep 2000 15:21:02 -0500 (CDT) From: David Scheidt To: Marc Tardif Cc: Alfred Perlstein , Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Marc Tardif wrote: :> > I've been using FreeBSD over the last 6 years (since I switched from :> > NetBSD) to run a small ISP out of my basement. :> > :> > I've had about six disk crashes in as many years and still don't know how :> > to work reliably with them. :> :> "man vinum" :> :> software mirroring == good. :> :What would be the incentives to using vinum instead of simply :concatenating drives in a RAID-1 array (or whatever) using ccd(4)? Concatenating drives is a decidedly different thing than mirroring them is. Mirroring allows you to recover from failed disks without having to restore from tape. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:22: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id D4ABD37B422; Wed, 20 Sep 2000 13:21:54 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Wed, 20 Sep 2000 14:21:54 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma028786; Wed, 20 Sep 00 14:21:34 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA78324; Wed, 20 Sep 2000 14:21:33 -0600 (MDT) Date: Wed, 20 Sep 2000 14:35:11 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Edward Elhauge Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <200009202024.NAA45822@ns2.uncanny.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're willing to go through strange install contortions, you can boot off of an MFS (Or MD, depending on what version you use ) root filesystem (copies stored in separate partition, on both disks you are mirroring) and then have everything else mirrored. Then at least your running system doesn't rely on any unmirrored disks. You can put a minimal root filesystem in memory and then have the rest of the stuff moved out via either symlinks or via just moving things around. Ie if you want to set up a bunch of boxes, it's nice to have most of the rc bootup stuff really reside on the vinum'd user... At any rate, from what I understand, it's the boot loader that doesn't understand vinum disks. put a kernel and minimum stuff somewhere the bootloader can find it and then mirror the rest. If one of the disks goes out, things keep working (root in memory, usr mirrored) and if you have to reboot, just make sure the good disk is the preferred boot device in your scsi bios. On Wed, 20 Sep 2000, Edward Elhauge wrote: > OK, vinum is good. But my understanding is that you can't use vinum on > your root partition. By Murphy's Law it always seems to be root that gets > screwed up. And that also causes the biggest problems because then you > have to yank the system apart and find another host disk for booting. > > Well spoken Alfred Perlstein wrote: > >* Edward Elhauge [000920 12:48] wrote: > >> Hello Freebsders, > >> > >> I've been using FreeBSD over the last 6 years (since I switched from > >> NetBSD) to run a small ISP out of my basement. > >> > >> I've had about six disk crashes in as many years and still don't know how > >> to work reliably with them. > > > >"man vinum" > > > >software mirroring == good. > > > >:) > > > >-Alfred > -- > Edward Elhauge -- Uncanny Inc., San Francisco > "War is like love; it always finds a way." -- Bertold Brecht > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:23:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7867E37B424; Wed, 20 Sep 2000 13:23:51 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8KKNmh13827; Wed, 20 Sep 2000 13:23:48 -0700 (PDT) Date: Wed, 20 Sep 2000 13:23:48 -0700 From: Alfred Perlstein To: Marc Tardif Cc: Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20000920132348.H9141@fw.wintelcom.net> References: <20000920125128.F9141@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from intmktg@CAM.ORG on Wed, Sep 20, 2000 at 04:09:13PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Marc Tardif [000920 13:06] wrote: > > > I've been using FreeBSD over the last 6 years (since I switched from > > > NetBSD) to run a small ISP out of my basement. > > > > > > I've had about six disk crashes in as many years and still don't know how > > > to work reliably with them. > > > > "man vinum" > > > > software mirroring == good. > > > What would be the incentives to using vinum instead of simply > concatenating drives in a RAID-1 array (or whatever) using ccd(4)? vinum can rebuild mirrored disks on the fly if you go with hotswap. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:40:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id B770C37B424 for ; Wed, 20 Sep 2000 13:40:19 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KKajv61760; Wed, 20 Sep 2000 21:36:45 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KKY3s18401; Wed, 20 Sep 2000 21:34:03 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009202034.e8KKY3s18401@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-hackers@FreeBSD.org, brian@Awfulhak.org Subject: Re: mergemaster RFC (long) In-Reply-To: Message from naddy@mips.inka.de (Christian Weisgerber) of "18 Sep 2000 23:53:33 +0200." <8q62st$1nkh$1@ganerc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 21:34:03 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > > First, the things I am definitely going to do. Christian "naddy" > > > Weisgerber has taken on the task of porting mm to openbsd. > > > > I think it would be nice to aim to keep the two scripts exactly the > > same, using `uname` when it's really necessary. > > If I have interpreted the noises Theo has made correctly, he wants > mergemaster in the base tree. I don't think he'll keep a "case > `uname` ..." in there. Of course if we didn't need it... that'd be far better :-) > Most of the diff deals with two simple differences: > - mergemaster uses "read -p " throughout. That fails for > OpenBSD's /bin/sh (pdksh), where "read -p" means something entirely > different. That's not too bad as the read -p can be changed to echo/read. > - On OpenBSD, "install" is synonymous to "install -c". FreeBSD still > has the old behavior where plain "install" deletes the source file. Maybe the best bet here is to have ``INSTALL=install'' at the top of the script (``INSTALL="install -c" for FreeBSD). It's a difference, but managable. > If we can get rid of those, the actual differences become more > visible. > > Oh, and changing every instance of "FreeBSD" into "${OPSYS}" or > some such would remove another few diff lines. Aye. Looks like we're thinking along the same lines. I'll have to talk to Wes at BSDCon about trying to get the NetBSD guys to introduce it there too - maybe some of the NetBSD developers will be there too. > -- > Christian "naddy" Weisgerber naddy@mips.inka.de -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:44: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7A83837B422; Wed, 20 Sep 2000 13:43:55 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8KKhah15539 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 20 Sep 2000 22:43:39 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8KKhlI04687; Wed, 20 Sep 2000 22:43:48 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8KKhhQ74579; Wed, 20 Sep 2000 22:43:43 +0200 (CEST) (envelope-from ticso) Date: Wed, 20 Sep 2000 22:43:42 +0200 From: Bernd Walter To: Edward Elhauge Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20000920224341.A74548@cicely5.cicely.de> References: <20000920125128.F9141@fw.wintelcom.net> <200009202024.NAA45822@ns2.uncanny.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200009202024.NAA45822@ns2.uncanny.net>; from ee@uncanny.net on Wed, Sep 20, 2000 at 01:24:34PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 01:24:34PM -0700, Edward Elhauge wrote: > OK, vinum is good. But my understanding is that you can't use vinum on > your root partition. By Murphy's Law it always seems to be root that gets > screwed up. And that also causes the biggest problems because then you > have to yank the system apart and find another host disk for booting. The root Filesytems doesn't really change. In general if you don't edit something in /etc or add accounts you can even be happy with a readonly /. I can't see any needs for mirrors beside that the host should keep running in case of a disk failure. A simple backup of the small /etc is sufficient. You don't have to find a new / disk if you already created one. A mirror would allocate it anyway. Nevertheless Greg showed me an df output with a mirrored / filesystem but as I usually have stone old drives (90M drives are more than enough ;) for / I never tried it myself because I don't own 2 identic of them. I don't know if it was plain vinum or some magic. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:48:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3DDE837B423; Wed, 20 Sep 2000 13:48:10 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8KKm6j15245; Wed, 20 Sep 2000 13:48:06 -0700 (PDT) Date: Wed, 20 Sep 2000 13:48:06 -0700 From: Alfred Perlstein To: Bernd Walter Cc: Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20000920134806.L9141@fw.wintelcom.net> References: <20000920125128.F9141@fw.wintelcom.net> <200009202024.NAA45822@ns2.uncanny.net> <20000920224341.A74548@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000920224341.A74548@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Wed, Sep 20, 2000 at 10:43:42PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bernd Walter [000920 13:43] wrote: > On Wed, Sep 20, 2000 at 01:24:34PM -0700, Edward Elhauge wrote: > > OK, vinum is good. But my understanding is that you can't use vinum on > > your root partition. By Murphy's Law it always seems to be root that gets > > screwed up. And that also causes the biggest problems because then you > > have to yank the system apart and find another host disk for booting. > > The root Filesytems doesn't really change. > In general if you don't edit something in /etc or add accounts you can > even be happy with a readonly /. > I can't see any needs for mirrors beside that the host should keep running > in case of a disk failure. A simple backup of the small /etc is sufficient. There's a "Zen of backup" somewhere that explains why you want to backup system files. Basically: hotswap spare read-only / and /usr == near 0 downtime, reinstall the OS == 20-120 minutes of downtime. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:49:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 2E82937B422; Wed, 20 Sep 2000 13:49:50 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id OAA37865; Wed, 20 Sep 2000 14:49:18 -0600 (MDT) Date: Wed, 20 Sep 2000 14:49:18 -0600 (MDT) From: Nick Rogness To: Alfred Perlstein Cc: Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <20000920125128.F9141@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Alfred Perlstein wrote: > * Edward Elhauge [000920 12:48] wrote: > > Hello Freebsders, > > > > I've been using FreeBSD over the last 6 years (since I switched from > > NetBSD) to run a small ISP out of my basement. > > > > I've had about six disk crashes in as many years and still don't know how > > to work reliably with them. > > "man vinum" > > software mirroring == good. The question should be, "How much you want to spend?" Depending on how you answer that question, you could choose either software or hardware RAID. I've always had better luck with hardware RAID cards compared to software RAID's. ALthough vinum sounds like a great package, I have little experience with it...only ccd, which is why I went with a hardware solution. If you got money, get a RAID controller (supported by FreeBSD). Then you don't have the root limitation that comes with vinum. If you don't have money, use vinum. Either way, use RAID. Best of luck. Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:57:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1D2AA37B422 for ; Wed, 20 Sep 2000 13:57:48 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA06262; Wed, 20 Sep 2000 13:57:37 -0700 Date: Wed, 20 Sep 2000 13:54:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gustavo Vieira Goncalves Coelho Rios Cc: hackers@FreeBSD.ORG Subject: Re: cannot install freebsd over a 15 GB IDE Disk In-Reply-To: <39C8E94E.2EB59BC3@tdnet.com.br> 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 dunno. I installed 4.0 fine on a 30 GB IDE. > Dear gentleman, > > i amgetting crazy since i cannot install my freebsd over a 15GB ide > disk! > I am sure i have seen messages in the questions mailing list about that, > but i could not find than from search web interface. > > Since, i would be glad if you could help getting this error out off. > > Thanks a lot for your time and cooperation. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 13:59: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A509237B423; Wed, 20 Sep 2000 13:58:59 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA06278; Wed, 20 Sep 2000 13:58:57 -0700 Date: Wed, 20 Sep 2000 13:55:46 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Edward Elhauge Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <200009201958.MAA45703@ns2.uncanny.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keep your disk cool. If you're getting MEDIUM errors, you're disks are getting toasted. I'm also in SF, and I plain mostly have been shut down the last two days. > Hello Freebsders, > > I've been using FreeBSD over the last 6 years (since I switched from > NetBSD) to run a small ISP out of my basement. > > I've had about six disk crashes in as many years and still don't know how > to work reliably with them. > > I have installed UPS boxes on each machine and that seems to have lowered > the incidence of failure, but failures still happen; yesterday during our > heat wave in the San Francisco area (possible brownouts also) I had > another. > > OK, so you have to expect these things; but I never seem to find an easy > way to recover these systems. The only thing that I've seen work has been > to mount the disk on another system, back it up, reformat the drive, copy > things back over and find out what was trashed. THERE MUST BE A BETTER > WAY. > > It seems like SCSI systems can't use the bad144 program. They are supposed > to autorecover on bad sectors, but every system that I've had to recover > seems to be in a state where the bad sectors aren't remapping. I've tried > buying top of the line hardware, and it does work faster, but no more > reliably than the cheap stuff. Once you get in this state it is difficult > to mount the partitions so as to recover what is there. > > I really need some good advice here. Do I need to buy RAID hardware for > each and every server in my network? Is there some way to force the SCSI > system to remap bad drives? > > The error I'm getting is: > MEDIUM ERROR info:1010f asc:14,1 > > My configuration is: > 1) Pentium-S 100 Mz > 2) 128M > 3) Adaptec 2940 Ultra/Ultra SCSI with Bios 1.25 > 4) Seagate ST3437 4GB > 5) FreeBSD 3.4 > > Any advice on how to efficiently bring my server back up or how I can > reengineer my system to avoid this in the future, will be greatly > appreciated. > -- > Edward Elhauge -- Uncanny Inc., San Francisco > "War is like love; it always finds a way." -- Bertold Brecht > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 14: 3:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 031C237B424 for ; Wed, 20 Sep 2000 14:03:22 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA24503; Thu, 21 Sep 2000 01:03:12 +0400 (MSD) Message-Id: <200009202103.BAA24503@aaz.links.ru> Subject: Re: cannot install freebsd over a 15 GB IDE Disk In-Reply-To: <39C8E94E.2EB59BC3@tdnet.com.br> from "Gustavo Vieira Goncalves Coelho Rios" at "Sep 20, 0 04:43:58 pm" To: kernel@tdnet.com.br (Gustavo Vieira Goncalves Coelho Rios) Date: Thu, 21 Sep 2000 01:03:12 +0400 (MSD) Cc: hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo Vieira Goncalves Coelho Rios writes: > i amgetting crazy since i cannot install my freebsd over a 15GB ide > disk! > I am sure i have seen messages in the questions mailing list about that, > but i could not find than from search web interface. > > Since, i would be glad if you could help getting this error out off. > > Thanks a lot for your time and cooperation. I installed FreeBSD on up to 75 Gb IDE disk and many of instalation on 30 Gb. What is a problem exactly? -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 14: 3:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 260A837B424; Wed, 20 Sep 2000 14:03:36 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA40006; Wed, 20 Sep 2000 14:03:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 20 Sep 2000 14:03:35 -0700 (PDT) From: Kris Kennaway To: "Koster, K.J." Cc: "'FreeBSD Hackers mailing list'" Subject: Re: Executable packages (long, sorry) In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D78DA@l04.research.kpn.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, 20 Sep 2000, Koster, K.J. wrote: > Riding on the wave of the unified BSD packages effort, this might be a good > time to rekindle that idea. Say that we agree on some form of uniform > package layout. You'd say that man pages go into $PKG_BASE/$PKG_NAME/man, > and that libraries go into $PKG_BASE/$PKG_NAME/lib, and that there is > probably a script named $PKG_BASE/$PKG_NAME/etc/rc that takes the arguments > "start" and "stop" for system startup. A script named > $PKG_BASE/$PKG_NAME/bin/run is invoked when a user types $PKG_NAME at the > command prompt (triggered by a script in /usr/local/bin, which is symlinked > to $PKG_NAME. It's not possible to determine where a lot of packages install, at run-time - they need compile-time settings. Our packages should mostly (with some notable exceptions where it's just too damn hard) be PREFIX-clean, meaning you can install them wherever you like, but you have to specify that at port compile-time. A similar idea has come up in the past about using something like stow to keep ports in sepoarate directories with symlinks from a master /usr/local/bin, but no-one's done the work to allow it. Hint. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 14:21: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 5E76437B423; Wed, 20 Sep 2000 14:20:57 -0700 (PDT) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8KLKe109103; Wed, 20 Sep 2000 15:20:40 -0600 (MDT) Message-Id: <200009202120.e8KLKe109103@orthanc.ab.ca> To: Edward Elhauge Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: mirroring / (was Re: Frustration with SCSI system) In-reply-to: Your message of "Wed, 20 Sep 2000 13:24:34 PDT." <200009202024.NAA45822@ns2.uncanny.net> Date: Wed, 20 Sep 2000 15:20:40 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Edward" == Edward Elhauge writes: Edward> OK, vinum is good. But my understanding is that you can't Edward> use vinum on your root partition. By Murphy's Law it Edward> always seems to be root that gets screwed up. And that Edward> also causes the biggest problems because then you have to Edward> yank the system apart and find another host disk for Edward> booting. Keep a spare root partition on another disk. If both disks (real root and spare root) have the same geometry, and you allocated identically sized root filesystems, you can dd the live root partition to the spare from cron. If they aren't the same size you would need to keep the spare mounted and do a 'dump ... | restore ...' instead. Alternatively, forgo all the cron-based sync magic (which *is* a bit dodgy when you're copying a live filesystem) and just manually sync the spare root to the real root whenever you make significant changes (new kernel, password file updates, etc). --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 14:27:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7495C37B423; Wed, 20 Sep 2000 14:27:02 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8KLQrf17936 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 20 Sep 2000 23:26:55 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8KLR5I04857; Wed, 20 Sep 2000 23:27:05 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8KLR0310239; Wed, 20 Sep 2000 23:27:00 +0200 (CEST) (envelope-from ticso) Date: Wed, 20 Sep 2000 23:26:59 +0200 From: Bernd Walter To: Alfred Perlstein Cc: Edward Elhauge , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20000920232659.A2086@cicely5.cicely.de> References: <20000920125128.F9141@fw.wintelcom.net> <200009202024.NAA45822@ns2.uncanny.net> <20000920224341.A74548@cicely5.cicely.de> <20000920134806.L9141@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000920134806.L9141@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Sep 20, 2000 at 01:48:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 01:48:06PM -0700, Alfred Perlstein wrote: > * Bernd Walter [000920 13:43] wrote: > > On Wed, Sep 20, 2000 at 01:24:34PM -0700, Edward Elhauge wrote: > > > OK, vinum is good. But my understanding is that you can't use vinum on > > > your root partition. By Murphy's Law it always seems to be root that gets > > > screwed up. And that also causes the biggest problems because then you > > > have to yank the system apart and find another host disk for booting. > > > > The root Filesytems doesn't really change. > > In general if you don't edit something in /etc or add accounts you can > > even be happy with a readonly /. > > I can't see any needs for mirrors beside that the host should keep running > > in case of a disk failure. A simple backup of the small /etc is sufficient. > > There's a "Zen of backup" somewhere that explains why you want to > backup system files. > > Basically: > hotswap spare read-only / and /usr == near 0 downtime, > reinstall the OS == 20-120 minutes of downtime. There is basicly no big difference in extracting the bin tgzs from the distribution compared to restoring it from a backup but the extra space won't hurt. Of course you need to have the binaries somewhere. Your numbers seem to be realistic to me but the restore case is missing here. Comparing a reinstall with a hotspare solution doesn't show a difference on wether to backup system files or not. And I was talking about / - That means for me no /var or /usr which can be mirrored (What doesn't mean that backups are not sensefull). -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 14:55:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 74A6037B422; Wed, 20 Sep 2000 14:55:37 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA28162; Thu, 21 Sep 2000 01:55:28 +0400 (MSD) Message-Id: <200009202155.BAA28162@aaz.links.ru> Subject: Re: Frustration with SCSI system In-Reply-To: <200009201958.MAA45703@ns2.uncanny.net> from "Edward Elhauge" at "Sep 20, 0 12:58:27 pm" To: ee@uncanny.net Date: Thu, 21 Sep 2000 01:55:28 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edward Elhauge writes: > I've been using FreeBSD over the last 6 years (since I switched from > NetBSD) to run a small ISP out of my basement. > > I've had about six disk crashes in as many years and still don't know how > to work reliably with them. > > I have installed UPS boxes on each machine and that seems to have lowered > the incidence of failure, but failures still happen; yesterday during our > heat wave in the San Francisco area (possible brownouts also) I had > another. > > OK, so you have to expect these things; but I never seem to find an easy > way to recover these systems. The only thing that I've seen work has been > to mount the disk on another system, back it up, reformat the drive, copy > things back over and find out what was trashed. THERE MUST BE A BETTER > WAY. > > It seems like SCSI systems can't use the bad144 program. They are supposed > to autorecover on bad sectors, but every system that I've had to recover > seems to be in a state where the bad sectors aren't remapping. I've tried > buying top of the line hardware, and it does work faster, but no more > reliably than the cheap stuff. Once you get in this state it is difficult > to mount the partitions so as to recover what is there. > > I really need some good advice here. Do I need to buy RAID hardware for > each and every server in my network? Is there some way to force the SCSI > system to remap bad drives? > > The error I'm getting is: > MEDIUM ERROR info:1010f asc:14,1 > > My configuration is: > 1) Pentium-S 100 Mz > 2) 128M > 3) Adaptec 2940 Ultra/Ultra SCSI with Bios 1.25 > 4) Seagate ST3437 4GB > 5) FreeBSD 3.4 > > Any advice on how to efficiently bring my server back up or how I can > reengineer my system to avoid this in the future, will be greatly > appreciated. I work since 1991 with computer hardware and know exact that SCSI drives is about ten times less reliability than IDE. Yes, I understand that SCSI was more ... extremal may be. I am wery glad that now mostly no need in SCSI drives at all. Just use good IDE drives, may be second root and regular dumps to, for example DDS-4 strimer. It is cost effective. If time to repare is critical, use spare IDE disk and special working place with direct crossover ethernet to dump server in addition to common ethernet. This helps you to paralelise repare work and do fast restore for low additional cost. Do not forget reblock dumps when write to tape. If your system is old enough - use Promise UDMA/66 controller. About temperature you already read. Some modern IDE drives has low power consumption and fast enough. If you need in big space - use RAID with IDE disks and SCSI external interface. Remember that most PCI are only 130 MB/sec wide. AND REMOVE FreeBSD 3.X AT ALL!!! 4.X is far more stable. It is easy, not expansive and works good. Sorry my English is not so good as I want. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 15: 2:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4466337B422; Wed, 20 Sep 2000 15:02:31 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA02271; Wed, 20 Sep 2000 16:02:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA50356; Wed, 20 Sep 2000 16:02:10 -0600 (MDT) Message-Id: <200009202202.QAA50356@harmony.village.org> To: Edward Elhauge Subject: Re: Frustration with SCSI system Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-reply-to: Your message of "Wed, 20 Sep 2000 12:58:27 PDT." <200009201958.MAA45703@ns2.uncanny.net> References: <200009201958.MAA45703@ns2.uncanny.net> Date: Wed, 20 Sep 2000 16:02:10 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009201958.MAA45703@ns2.uncanny.net> Edward Elhauge writes: : to autorecover on bad sectors, but every system that I've had to recover : seems to be in a state where the bad sectors aren't remapping. I've tried I've often wanted to write a bad block remapper. While SCSI is supposed to do this automatically, I've found that a scan on any adaptec controller will remap these blocks (forces the remapping). About 10% of the time that's all a drive with this problem needs to survive indefinitely. The other 90% of the time the disk is about to go tits up in a heap big time way and warrantee replacement is recommended. About 75% of the time a rescan + immmediate dump will save me. I've had 2 disks that seem to have lost their bad block mappings that the adaptec verify function has saved me from sending them back (they were out of warantee anyway). However, on the other 20ish disks I've tried this on have died within days of doing this. Even if we had bad144 support, the drive will need so many bad blocks remapped in a short period of time that it isn't worth while. Finally, I've found that climate controlled and dust free environments help a lot. RAID hardware/software is definitely the right way to deal when you go to the next level. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 15: 3:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 988AD37B422; Wed, 20 Sep 2000 15:03:34 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA02285; Wed, 20 Sep 2000 16:03:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA50383; Wed, 20 Sep 2000 16:03:13 -0600 (MDT) Message-Id: <200009202203.QAA50383@harmony.village.org> To: Marc Tardif Subject: Re: Frustration with SCSI system Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-reply-to: Your message of "Wed, 20 Sep 2000 16:09:13 EDT." References: Date: Wed, 20 Sep 2000 16:03:13 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marc Tardif writes: : What would be the incentives to using vinum instead of simply : concatenating drives in a RAID-1 array (or whatever) using ccd(4)? RAID-5 now seems to be supported, which lets you take the loss of a single disk more easily. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 15:28:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 7595037B422; Wed, 20 Sep 2000 15:28:46 -0700 (PDT) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id RAA40782; Wed, 20 Sep 2000 17:28:40 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 20 Sep 2000 17:28:40 -0500 (CDT) From: David Scheidt To: "Aleksandr A.Babaylov" Cc: ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <200009202155.BAA28162@aaz.links.ru> 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, 21 Sep 2000, Aleksandr A.Babaylov wrote: :I work since 1991 with computer hardware and know exact :that SCSI drives is about ten times less reliability than :IDE. Yes, I understand that SCSI was more ... extremal may be. :I am wery glad that now mostly no need in SCSI drives at all. :Just use good IDE drives, may be second root and regular :dumps to, for example DDS-4 strimer. It is cost effective. This is totatlly contrary to my experience. Heck, I've got a fair number of SCSI disks that predate 1991, happily spinning away. SCSI just works, on everything I've ever used it. I've had a occaisonal problems with things like termination. High quality cables and enclosures solve this. I wouldn't let an IDE disk get within thinking distance of machine whose reliability I cared about. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 15:50:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 5601637B423; Wed, 20 Sep 2000 15:50:53 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id CAA01922; Thu, 21 Sep 2000 02:50:45 +0400 (MSD) Message-Id: <200009202250.CAA01922@aaz.links.ru> Subject: Re: Frustration with SCSI system In-Reply-To: from "David Scheidt" at "Sep 20, 0 05:28:40 pm" To: dscheidt@enteract.com (David Scheidt) Date: Thu, 21 Sep 2000 02:50:45 +0400 (MSD) Cc: babolo@links.ru, ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt writes: > On Thu, 21 Sep 2000, Aleksandr A.Babaylov wrote: > :I work since 1991 with computer hardware and know exact > :that SCSI drives is about ten times less reliability than > :IDE. Yes, I understand that SCSI was more ... extremal may be. > :I am wery glad that now mostly no need in SCSI drives at all. > :Just use good IDE drives, may be second root and regular > :dumps to, for example DDS-4 strimer. It is cost effective. > This is totatlly contrary to my experience. Heck, I've got a fair > number of SCSI disks that predate 1991, happily spinning away. > SCSI just works, on everything I've ever used it. I've had a > occaisonal problems with things like termination. High quality > cables and enclosures solve this. I wouldn't let an IDE disk get within > thinking distance of machine whose reliability I cared about. Cabling... most of troubles caused by cables for me - it is reason I do not believe external devices. Most of IDE breaks was long ago - last about 3 or 4 years ago. SCSI drives breaks are quite regular - 1 or 2 in at least 5 last years. this is for about 50 SCSI drives near me and about 3 times more IDE drives. This is my expierency - you have another. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 16:19:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id EC2D737B422; Wed, 20 Sep 2000 16:19:28 -0700 (PDT) Received: by heorot.1nova.com (Postfix, from userid 1000) id 0B2D93288; Tue, 19 Sep 2000 15:43:13 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id E43C93287; Tue, 19 Sep 2000 15:43:13 +0000 (GMT) Date: Tue, 19 Sep 2000 15:43:13 +0000 (GMT) From: Rick Hamell To: "Aleksandr A.Babaylov" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <200009202250.CAA01922@aaz.links.ru> 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 > Cabling... most of troubles caused by cables for me - it is > reason I do not believe external devices. > Most of IDE breaks was long ago - last about 3 or 4 years ago. > SCSI drives breaks are quite regular - 1 or 2 in at least 5 > last years. > this is for about 50 SCSI drives near me and about 3 times more > IDE drives. > This is my expierency - you have another. Which is most likely heat related... that's been my experience anyways... :) In a well cooled system, that needs reliability... SCSI all the way... Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 17:46: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 50DD337B422; Wed, 20 Sep 2000 17:45:57 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-20.nnj.dialup.bellatlantic.net [151.198.117.20]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA18805; Wed, 20 Sep 2000 20:44:57 -0400 (EDT) Message-ID: <39C95AB7.D9DD318C@bellatlantic.net> Date: Wed, 20 Sep 2000 20:47:51 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: "Aleksandr A.Babaylov" Cc: David Scheidt , ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system References: <200009202250.CAA01922@aaz.links.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Aleksandr A.Babaylov" wrote: > > David Scheidt writes: > > On Thu, 21 Sep 2000, Aleksandr A.Babaylov wrote: > > :I work since 1991 with computer hardware and know exact > > :that SCSI drives is about ten times less reliability than > > :IDE. Yes, I understand that SCSI was more ... extremal may be. > > :I am wery glad that now mostly no need in SCSI drives at all. > > :Just use good IDE drives, may be second root and regular > > :dumps to, for example DDS-4 strimer. It is cost effective. > > This is totatlly contrary to my experience. Heck, I've got a fair > > number of SCSI disks that predate 1991, happily spinning away. > > SCSI just works, on everything I've ever used it. I've had a > > occaisonal problems with things like termination. High quality > > cables and enclosures solve this. I wouldn't let an IDE disk get within > > thinking distance of machine whose reliability I cared about. > Cabling... most of troubles caused by cables for me - it is > reason I do not believe external devices. Eh, that's something unusual. Unless you buy cheap bad cables or try to solder them by yourself. > Most of IDE breaks was long ago - last about 3 or 4 years ago. > SCSI drives breaks are quite regular - 1 or 2 in at least 5 > last years. > this is for about 50 SCSI drives near me and about 3 times more > IDE drives. > This is my expierency - you have another. Overheating. Newer SCSI disks can be found only in high-performance versions, so they tend to generate more heat and be more sensitive to cooling. Plus if your SCSI disks are used more intensely (and they probably are) this would affect their longevity. Plus different manufacturers have different reliability - if you use Seagate SCSI disks and someone else's IDE then you most certainly will see a lot more SCSI disk failures. -SB, Seagate Hater To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 18:11: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.mikesweb.com (saturn.mikesweb.com [216.91.66.1]) by hub.freebsd.org (Postfix) with SMTP id 7EE5537B423 for ; Wed, 20 Sep 2000 18:10:54 -0700 (PDT) Received: (qmail 20757 invoked from network); 21 Sep 2000 01:10:53 -0000 Received: from delta.futuredesigns.net (HELO SUN.mikesweb.com) (@216.91.66.252) by saturn.mikesweb.com with SMTP; 21 Sep 2000 01:10:53 -0000 Message-Id: <4.3.2.7.2.20000920210124.0f722908@mail.mikesweb.com> X-Sender: sturdee@mail.mikesweb.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 20 Sep 2000 21:09:49 -0400 To: Sergey Babkin , "Aleksandr A.Babaylov" From: Mike Subject: Re: Frustration with SCSI system Cc: David Scheidt , ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: <39C95AB7.D9DD318C@bellatlantic.net> References: <200009202250.CAA01922@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've used various Seagate SCSI drives exclusively in all of my boxes and only had one failure, which I was still able to recover all the data from before replacing it. The first box I built back in '97 had an UW Seagate in it that I bought used, and it was very heavily used for 2 years, and I still have that original configuration for various small projects. Right now I have 4 boxes with Barracuda drives (7200RPM) almost to the ceiling in a closet at one site that temps can get up to 80 degrees F, with a constant fan on them, all doing fine.. I build a couple boxes with Seagate Cheetah's in them, for a guy who has an ISP out of his house. He also has (literally) 12 cats and dogs whose hair ends up in the filters of his servers. They too are heavily used, and have had no problems. It's almost like it goes on luck. ;-) At 08:47 PM 9/20/2000 -0400, Sergey Babkin wrote: >"Aleksandr A.Babaylov" wrote: > > > > David Scheidt writes: > > > On Thu, 21 Sep 2000, Aleksandr A.Babaylov wrote: > > > :I work since 1991 with computer hardware and know exact > > > :that SCSI drives is about ten times less reliability than > > > :IDE. Yes, I understand that SCSI was more ... extremal may be. > > > :I am wery glad that now mostly no need in SCSI drives at all. > > > :Just use good IDE drives, may be second root and regular > > > :dumps to, for example DDS-4 strimer. It is cost effective. > > > This is totatlly contrary to my experience. Heck, I've got a fair > > > number of SCSI disks that predate 1991, happily spinning away. > > > SCSI just works, on everything I've ever used it. I've had a > > > occaisonal problems with things like termination. High quality > > > cables and enclosures solve this. I wouldn't let an IDE disk get within > > > thinking distance of machine whose reliability I cared about. > > Cabling... most of troubles caused by cables for me - it is > > reason I do not believe external devices. > >Eh, that's something unusual. Unless you buy cheap bad cables or >try to solder them by yourself. > > > Most of IDE breaks was long ago - last about 3 or 4 years ago. > > SCSI drives breaks are quite regular - 1 or 2 in at least 5 > > last years. > > this is for about 50 SCSI drives near me and about 3 times more > > IDE drives. > > This is my expierency - you have another. > >Overheating. Newer SCSI disks can be found only in high-performance >versions, so they tend to generate more heat and be more sensitive to >cooling. Plus if your SCSI disks are used more intensely (and they >probably are) this would affect their longevity. > >Plus different manufacturers have different reliability - >if you use Seagate SCSI disks and someone else's IDE then you most >certainly will see a lot more SCSI disk failures. > >-SB, Seagate Hater > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 18:50:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id B9D9737B422; Wed, 20 Sep 2000 18:50:29 -0700 (PDT) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id UAA84682; Wed, 20 Sep 2000 20:50:24 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 20 Sep 2000 20:50:24 -0500 (CDT) From: David Scheidt To: Sergey Babkin Cc: "Aleksandr A.Babaylov" , ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system In-Reply-To: <39C95AB7.D9DD318C@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Sergey Babkin wrote: :Plus different manufacturers have different reliability - :if you use Seagate SCSI disks and someone else's IDE then you most :certainly will see a lot more SCSI disk failures. : :-SB, Seagate Hater : I've had almost a thousand Seagates in service for about a year without a single failure. We've replaced 5 or 6 controllers, and a bunch of cables (when the machines first went into service. The techs are murder at bending pins.). I'm quite impressed. : David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 18:53:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 10FC537B422 for ; Wed, 20 Sep 2000 18:53:19 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8L1rCi98168 for ; Wed, 20 Sep 2000 18:53:12 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8L1pe603039 for hackers@FreeBSD.org; Wed, 20 Sep 2000 18:51:40 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 20 Sep 2000 18:51:39 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: hackers@FreeBSD.org Subject: Minor aio cleanup Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At http://www.FreeBSD.org/~jhb/patches/aio.patch there is a simple patch that teaches aio daemons to use kthread_create() and kthread_exit() and thus be slightly cleaner. However, I'm not familiar with using aio, so I'd appreciate it if people who _do_ use aio would test this and make sure it works for you. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 20:59:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 5A7DB37B422; Wed, 20 Sep 2000 20:59:29 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id HAA11262; Thu, 21 Sep 2000 07:59:15 +0400 (MSD) Message-Id: <200009210359.HAA11262@aaz.links.ru> Subject: Re: Frustration with SCSI system In-Reply-To: <39C95AB7.D9DD318C@bellatlantic.net> from "Sergey Babkin" at "Sep 20, 0 08:47:51 pm" To: babkin@bellatlantic.net (Sergey Babkin) Date: Thu, 21 Sep 2000 07:59:15 +0400 (MSD) Cc: babolo@links.ru, dscheidt@enteract.com, ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin writes: > "Aleksandr A.Babaylov" wrote: > > David Scheidt writes: ......... > > > SCSI just works, on everything I've ever used it. I've had a > > > occaisonal problems with things like termination. High quality > > > cables and enclosures solve this. I wouldn't let an IDE disk get within > > > thinking distance of machine whose reliability I cared about. > > Cabling... most of troubles caused by cables for me - it is > > reason I do not believe external devices. > Eh, that's something unusual. Unless you buy cheap bad cables or > try to solder them by yourself. No, good cable in bad place - after touch time to time some external cables change its state. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 21:50:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from facteur.in.grolier.fr (facteur.in.grolier.fr [194.117.196.5]) by hub.freebsd.org (Postfix) with ESMTP id 01B3237B424 for ; Wed, 20 Sep 2000 21:50:24 -0700 (PDT) Received: from kalou.in.grolier.fr (kalou.in.grolier.fr [194.117.197.111]) by facteur.in.grolier.fr (Postfix) with ESMTP id 007479D596; Thu, 21 Sep 2000 06:50:21 +0200 (MET DST) Received: (from pb@localhost) by kalou.in.grolier.fr (8.9.1b+Sun/8.9.1) id GAA03322; Thu, 21 Sep 2000 06:48:37 +0200 (MET DST) Date: Thu, 21 Sep 2000 06:48:37 +0200 From: Pascal Bouchareine To: Gustavo Vieira Goncalves Coelho Rios Cc: hackers@FreeBSD.ORG Subject: Re: cannot install freebsd over a 15 GB IDE Disk Message-ID: <20000921064837.A3313@kalou.in.grolier.fr> References: <39C8E94E.2EB59BC3@tdnet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39C8E94E.2EB59BC3@tdnet.com.br>; from kernel@tdnet.com.br on Wed, Sep 20, 2000 at 04:43:58PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the problem a *long* time ago while 'newfs'ing very large drives without partitions and with blocks that where too small. Can't remember exactly if this was vinum-specific or went from somewhere else. can't either remember the disk and block size i used.. But i think some signed int limited my block size choice. If this may help, try bigger blocks. By the way, what is "this error" ? :) On Wed, Sep 20, 2000 at 04:43:58PM +0000, Gustavo Vieira Goncalves Coelho Rios wrote: > Dear gentleman, > > i amgetting crazy since i cannot install my freebsd over a 15GB ide > disk! > I am sure i have seen messages in the questions mailing list about that, > but i could not find than from search web interface. > > Since, i would be glad if you could help getting this error out off. > > Thanks a lot for your time and cooperation. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kalou. ldiq t0, 0xbeeffedadeadbabe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 23:15:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 4963637B423; Wed, 20 Sep 2000 23:15:18 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bzda-0004tY-00; Thu, 21 Sep 2000 09:15:14 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bzdY-0001wq-00; Thu, 21 Sep 2000 09:15:12 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: Paul Saab , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Wed, 20 Sep 2000 23:09:35 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 09:15:12 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009210609.XAA01851@mass.osd.bsdi.com>you write: } }I think this is correct, actually. Danny, can you confirm that you're }using one of the class A address spaces (eg. 10.*.*.*?) } my net is class B. 132.65.0.0 }Actually, IMO the code around this is entirely wrong; we should always }respect the mask supplied by the server, and only use the canonical mask }if we don't get one at all. } my man! im cleaning up bootp and will let you know. }> bug report: }> in lib/libstand/bootp.c: }> }> if (IN_CLASSA(myip.s_addr)) }> nmask = htonl(IN_CLASSA_NET); }> else if (IN_CLASSB(myip.s_addr)) }> nmask = htonl(IN_CLASSB_NET); }> else }> nmask = htonl(IN_CLASSC_NET); }> should be: }> }> if (IN_CLASSA(ntohl(myip.s_addr))) }> nmask = htonl(IN_CLASSA_NET); }> else if (IN_CLASSB(ntohl(myip.s_addr))) }> nmask = htonl(IN_CLASSB_NET); }> else }> nmask = htonl(IN_CLASSC_NET); }> }> which explains why gateway was zero, even if it was provided by dhcp. }> it also explains why it hung trying to mount via nfs. }> }> danny }> }> In message <20000919164129.A39104@elvis.mu.org>you write: }> }Danny Braniss (danny@cs.huji.ac.il) wrote: }> }> In message <20000919024512.A27691@elvis.mu.org>you write: }> }> }> }> }set this in your dhcpd.conf, but yes, I will fix it. }> }> i know it should be in dhcpd.conf but what? :-) btw, i tried router but z }ilc }> }h. }> } }> }option routers ip; }> } }> }> } }> }> }> 2- if i set different hosts for dhcpd, tftpd, root and swap i get into }> }> }> all sort of problems. the most anoying one is that the bios-pxe boo }t w }> }ill }> }> }> try and tftpboot from the wrong server. so im using 'option swap-se }rve }> }r' }> }> } }> }> }I dont follow. }> }> } }> }> }> }> if i set: }> }> option root-path "132.65.16.6:/vol1/roots/fbsd-4.1S"; }> }> then the ip gets chunked, and it will try to mount from the tftp server - } }> }> bummer }> } }> }Yeah.. I have not wanted to do this. I'll look at this in a little while. }> } }> }> if i set }> }> option next-server myrootserver }> }> the pxe-bios will use it for the tftpd - bummer }> } }> }please read the PXE specs to see how to tell it to grab the tftp loader > }from a different server. }> } }> }> so, at the moment i use }> }> option swap-server myrootserver; }> }> and it works. but it should be less blackmagic. also, what if i want a }> }> different }> }> root and swap server? }> } }> }I'll fix it if I get time. }> }> }> }> }> } }-- }... every activity meets with opposition, everyone who acts has his }rivals and unfortunately opponents also. But not because people want }to be opponents, rather because the tasks and relationships force }people to take different points of view. [Dr. Fritz Todt] } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 23:37:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id E585237B422; Wed, 20 Sep 2000 23:37:20 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bzyw-0005AW-00; Thu, 21 Sep 2000 09:37:18 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13bzyu-0001xn-00; Thu, 21 Sep 2000 09:37:16 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Wed, 20 Sep 2000 23:26:00 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 09:37:16 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009210626.XAA02048@mass.osd.bsdi.com>you write: }> In message <200009210609.XAA01851@mass.osd.bsdi.com>you write: }> } }> }I think this is correct, actually. Danny, can you confirm that you're }> }using one of the class A address spaces (eg. 10.*.*.*?) }> } }> my net is class B. 132.65.0.0 } }Gotcha. What's your netmask? I bet it disagrees one way or the other }with the "canonical" netmask this code assumes. it's the host part 132.65.80.247, the 247 is 0xF7 and hence class C :-) my netmask is 255.255.0.0 for the time being till we go vlan. } }> }Actually, IMO the code around this is entirely wrong; we should always }> }respect the mask supplied by the server, and only use the canonical mask }> }if we don't get one at all. }> } }> my man! }> }> im cleaning up bootp and will let you know. } }You could make yourself *really* popular and teach it about DHCP, you }know. 8) } what have you in mind? it already knows some DHCP, the leasing stuff is yet a gray area with me (i dislike it totaly, but then i own a class B ;-) i've added hostname though. suggestions? on a different subject, but related: on my nfsroot client, im now stuck - again -, ls -ls /dev/null shows strange minor/major: 0, 0x00020002 instead od 2,2 which of course ruins rc.diskless. the same filesystem when accessed by another fbsd4.1S (no nfsrooted) is ok. hints? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 23:48:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 6123437B422; Wed, 20 Sep 2000 23:48:25 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id F30392B269; Thu, 21 Sep 2000 01:48:19 -0500 (CDT) Date: Wed, 20 Sep 2000 23:48:19 -0700 From: Paul Saab To: Mike Smith Cc: Danny Braniss , freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000920234819.A68513@elvis.mu.org> References: <200009210609.XAA01851@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009210609.XAA01851@mass.osd.bsdi.com>; from msmith@freebsd.org on Wed, Sep 20, 2000 at 11:09:35PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith (msmith@freebsd.org) wrote: > > I think this is correct, actually. Danny, can you confirm that you're > using one of the class A address spaces (eg. 10.*.*.*?) > > Actually, IMO the code around this is entirely wrong; we should always > respect the mask supplied by the server, and only use the canonical mask > if we don't get one at all. It does.. look futher down in the code. paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 20 23:53:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 212F337B422 for ; Wed, 20 Sep 2000 23:53:30 -0700 (PDT) Received: from sol.we.lc.ehu.es (sol [158.227.6.42]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id IAA05765 for ; Thu, 21 Sep 2000 08:53:20 +0200 (MET DST) From: Borja Marcos Received: (from borjam@localhost) by sol.we.lc.ehu.es (8.9.1/8.9.1) id IAA03944 for hackers@freebsd.org; Thu, 21 Sep 2000 08:53:19 +0200 (MET DST) Message-Id: <200009210653.IAA03944@sol.we.lc.ehu.es> Subject: Re: traceroute using tcp to a port? To: leif@neland.dk Date: Wed, 20 Sep 100 16:25:39 +0200 (MET DST) In-Reply-To: <00ac01c02218$7f91e080$0e00a8c0@neland.dk> from "Leif Neland" at Sep 19, 0 11:00:57 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I understand correctly, traceroute works by sending pings with ttl=1, > ttl=2,ttl=3 etc and records the names of the routers where the ttl reaches > zero. No, traceroute send UDP messages by default. Doing a traceroute with TCP (it has an option, -P tcp) can be really useful if you can use a fixed port. I made a trivial change to traceroute that allows you to specify a fixed port by using a negative number. For example, traceroute -P tcp -p -80 will do a "TCP SYN traceroute" for port 80. Comparing this output with a normal traceroute to the same destination (or a traceroute for a different TCP port) you can detect HTTP transparent proxies, man-in-the-middle attacks, policy routing, etc. I sent a patch to the traceroute development team but received no answer :-(. Perhaps it could be committed to FreeBSD? I work for an ISP and the feature has proved to be really useful! Borja. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 0:15:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id A21BE37B423; Thu, 21 Sep 2000 00:15:23 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13c0Zl-00063j-00; Thu, 21 Sep 2000 10:15:21 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13c0Zj-0001zL-00; Thu, 21 Sep 2000 10:15:19 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: dhcp boot was: Re: diskless workstation In-reply-to: Your message of Wed, 20 Sep 2000 23:48:46 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 10:15:19 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009210648.XAA02252@mass.osd.bsdi.com>you write: }Mostly I guess I'd really like it to simply save *all* of the DHCP }response in the environment. Just "dhcp.xxx" where xxx is the parameter }value would probably do it, or we can argue about names for everything if }there aren't established names already. } what's in a name ;-) the dhcp.xxx stuff is easy, the problem is that the DHCP options are not enough, so im trying to look into defining a FBSDclass ala PXEClient, and supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. }There should be no real problems with the lease, as most leases are more }than long enough to boot the system anyway, so I wouldn't bother with }that. } and this is not a MS system that needs allot of magic before it boots up ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 1: 1:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from belpak.minsk.by (belpak.minsk.by [193.232.248.10]) by hub.freebsd.org (Postfix) with ESMTP id A63C437B424 for ; Thu, 21 Sep 2000 01:01:12 -0700 (PDT) Received: from [kali.UUCP] (ident=uucp) by belpak.minsk.by with UUCP (Sendmail) for freebsd-hackers@FreeBSD.ORG id 13c1IS-00018R-00; Thu, 21 Sep 2000 11:01:32 +0300 Received: by kali.belpak.minsk.by (Mini-Host for Windows v3.1.160) Wed, 20 Sep 2000 16:26:34 +0200 Received: from fdv by kali.belpak.minsk.by via (Mini-Host for Windows v2.0); Internet Client with TCP; 20 SEP 2000 16:26:34 -0200 Date: Wed, 20 Sep 2000 16:26:39 +0300 From: pbf@kali.belpak.minsk.by X-Mailer: The Bat! (v1.41) Reply-To: pbf@kali.belpak.minsk.by X-Priority: 3 (Normal) Message-ID: <17685.000920@kali.belpak.minsk.by> To: freebsd-hackers@FreeBSD.ORG Subject: About imp 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 freebsd-hackers, Answer me, please: what do imp in your FreeBSD logo? P.S. I like FreeBSD but imp... It main trouble for me. It very bad. -- Best regards, pbf mailto:pbf@kali.belpak.minsk.by To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 1:46:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 38F3837B42C for ; Thu, 21 Sep 2000 01:46:34 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JUFKEQVZ8C000L4G@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Thu, 21 Sep 2000 10:46:29 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Thu, 21 Sep 2000 10:46:28 +0100 Content-return: allowed Date: Thu, 21 Sep 2000 10:46:25 +0100 From: "Koster, K.J." Subject: RE: About imp To: "'pbf@kali.belpak.minsk.by'" Cc: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D78E1@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Answer me, please: what do imp in your FreeBSD logo? > > P.S. I like FreeBSD but imp... It main trouble for me. It > very bad. > Read this first, then see if you still think it's bad. http://www.freebsd.org/copyright/daemon.html Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 3: 0:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.dcn-asu.ru (ns.dcn-asu.ru [212.192.20.33]) by hub.freebsd.org (Postfix) with ESMTP id D332337B424 for ; Thu, 21 Sep 2000 02:59:54 -0700 (PDT) Received: from aux1.uic.asu.ru (ic-mx [212.192.20.39]) by ns.dcn-asu.ru (8.9.3/8.9.1-BPO1) with ESMTP id QAA31201 for ; Thu, 21 Sep 2000 16:58:07 +0700 (NOVST) Received: from uic.asu.ru ([212.192.21.204]) by aux1.uic.asu.ru (8.11.0/8.11.0) with ESMTP id e8L9vnI04392 for ; Thu, 21 Sep 2000 16:57:52 +0700 Message-ID: <39C9DCA8.5E8D1C16@uic.asu.ru> Date: Thu, 21 Sep 2000 17:02:16 +0700 From: "Konstanten V. Muzalevskiy" X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12bc i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 4:39:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id E3E2437B422 for ; Thu, 21 Sep 2000 04:39:48 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13c4hb-0002ZW-00 for freebsd-hackers@freebsd.org; Thu, 21 Sep 2000 14:39:43 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13c4hZ-0002m6-00 for freebsd-hackers@freebsd.org; Thu, 21 Sep 2000 14:39:41 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@freebsd.org Subject: nfs3/2 strange problem Was: diskless workstation In-reply-to: Your message of Wed, 20 Sep 2000 23:48:46 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 14:39:41 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if i mount a fs with nfs/v3 all is fine. loo# ls -ls /net/nafs-tmp/vol1/roots/fbsd-4.1S/dev/null 0 crw-rw-rw- 1 root wheel 2, 2 Sep 20 14:33 /net/nafs-tmp/vol1/roots/fbsd-4.1S/dev/null but if i mount the same fs with nfs/v2 all is 'almost' ok :-( the special files have a wee-little-problem: loo# mount_nfs -2 nafs-tmp:/vol1/roots/fbsd-4.1S /mnt loo# ls -ls /mnt/dev/null 0 crw-rw-rw- 1 root wheel 0, 0x00020002 Sep 20 14:33 /mnt/dev/null btw, it's FreeBSD4.1-stable. any clues? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 7:22:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 99A2C37B423 for ; Thu, 21 Sep 2000 07:22:28 -0700 (PDT) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/8.9.1) id KAA16652; Thu, 21 Sep 2000 10:22:04 -0400 (EDT) Date: Thu, 21 Sep 2000 10:22:04 -0400 From: Christian Kuhtz To: "Koster, K.J." Cc: "'FreeBSD Hackers mailing list'" Subject: Re: Executable packages (long, sorry) Message-ID: <20000921102204.D6714@ns1.arch.bellsouth.net> References: <59063B5B4D98D311BC0D0001FA7E4522026D78DA@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D78DA@l04.research.kpn.com>; from Koster, K.J. on Wed, Sep 20, 2000 at 06:49:36PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seems one might just as well investigate the SUN pkgadd format and see whether such mechanism fits the bill... Ideally, the pkg also kows how to back itself out if it can't successfully install. (although doing so should be an option, not the default). On Wed, Sep 20, 2000 at 06:49:36PM +0100, Koster, K.J. wrote: > Dear All, > > While we're on the subject of packaging formats, I would like to present an > idea that has been running around in the back of my head. > > Years ago I had the pleasure of playing with a new RiscPC by Acorn. If you > create a directory on RiscOS and stick a little BASIC script in with exactly > the right name, RiscOS will treat that directory as an executable. You can > use the directory to stick in whatever the application needs, and the user > never needs to bother. Uninstalling it is as easy as the RiscOS equivalent > of "rm -rf". > > Riding on the wave of the unified BSD packages effort, this might be a good > time to rekindle that idea. Say that we agree on some form of uniform > package layout. You'd say that man pages go into $PKG_BASE/$PKG_NAME/man, > and that libraries go into $PKG_BASE/$PKG_NAME/lib, and that there is > probably a script named $PKG_BASE/$PKG_NAME/etc/rc that takes the arguments > "start" and "stop" for system startup. A script named > $PKG_BASE/$PKG_NAME/bin/run is invoked when a user types $PKG_NAME at the > command prompt (triggered by a script in /usr/local/bin, which is symlinked > to $PKG_NAME. > > We are already doing this now, but instead we scatter packages across the > filesystem, keeping file lists of where we left the various body parts of > the port. > > So is this a bad idea? I don't think so. Some programs already install > themselves in a similar fashion. If you'll allow me to use Tomcat as an > example. After you have installed it, only /usr/local/tomcat new on your > system. It has its own bin/, conf/ and lib/ directory. Deinstalling is as > simple as it is on a RiscPC. > > There are other places too, where you see this self-containment crop up. The > executable JAR files from Java, for example. And someone over at KDE or > Gnome (or some desktop kit like that, I can't tell them apart) mentioned > that they were going to do a ZIP archive abstraction, much like they did > with the file system. You could easily make a zip archive behave like an > executable. > > I do not think that this is the perfect solution to system clobbering. In > fact, there are some good examples of stuff that should really not be > installed in an executable directory. The GNU tools spring to mind. They > were written according to a UNIX utility philosophy, and should be treated > as such. Other things, such as a web server, or a word processor are much > more self contained. > > I hope that you will remember this idea when you find yourself staring at > traces of an old port, unsure if you should delete it or not. :-) > > Kees Jan > > ================================================ > You are only young once, > but you can stay immature all your life. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 7:40:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id C67DC37B422 for ; Thu, 21 Sep 2000 07:40:45 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 0850A6A901 for ; Thu, 21 Sep 2000 16:40:44 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AED3173F0266; Thu, 21 Sep 2000 16:44:35 +0200 Message-Id: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 21 Sep 2000 13:09:52 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: low-cost/low-speed HDLC WAN card Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm back again looking for a low-cost, 128 kbits/sec WAN card, even ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to drive leased-line links in France. etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 megabits. We use two now in our ISP and it works fine, but to use FreeBSD in a big nationwide VPN/IPsec project, we need to keep the price down. We can buy a Zyxel 153X WAN router for about that price, but it doesn't do VPN nor more than one ethernet i/f nor does it's non-loggable, limited packet filtering come anywhere near ipfilter. sdlcomm cards are even more expensive and up 10 megabits. tia, Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 7:58:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 2E0DA37B423 for ; Thu, 21 Sep 2000 07:58:57 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8LEwjN06043; Thu, 21 Sep 2000 16:58:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: low-cost/low-speed HDLC WAN card In-Reply-To: Your message of "Thu, 21 Sep 2000 13:09:52 +0200." <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Date: Thu, 21 Sep 2000 16:58:45 +0200 Message-ID: <6041.969548325@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com>, Len Conrad writes: >I'm back again looking for a low-cost, 128 kbits/sec WAN card, even >ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to >drive leased-line links in France. http://www.lanmedia.com model LMC1000P FreeBSD driver in src/sys/dev/lmc -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 8: 8:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id DB19D37B423 for ; Thu, 21 Sep 2000 08:08:38 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8LFP1C55848; Thu, 21 Sep 2000 11:25:01 -0400 (EDT) Date: Thu, 21 Sep 2000 11:25:01 -0400 (EDT) From: Jim Flowers To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: low-cost/low-speed HDLC WAN card In-Reply-To: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.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 Check out www.sangoma.com (Canada). They have both ISA and PCI that at least does V.35 and HDLC and supports multicast. They furnish and support FreeBSD driver (including source) and they have been trouble-free. Also have WinXX/NT GUI for remote monitoring. Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Thu, 21 Sep 2000, Len Conrad wrote: > I'm back again looking for a low-cost, 128 kbits/sec WAN card, even > ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to > drive leased-line links in France. > > etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 > megabits. We use two now in our ISP and it works fine, but to use > FreeBSD in a big nationwide VPN/IPsec project, we need to keep the price down. > > We can buy a Zyxel 153X WAN router for about that price, but it > doesn't do VPN nor more than one ethernet i/f nor does it's > non-loggable, limited packet filtering come anywhere near ipfilter. > > sdlcomm cards are even more expensive and up 10 megabits. > > tia, > Len > > http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 > http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 8:26:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id BFB9837B424 for ; Thu, 21 Sep 2000 08:26:14 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 10F696A905 for ; Thu, 21 Sep 2000 17:26:12 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A97DEC900086; Thu, 21 Sep 2000 17:30:05 +0200 Message-Id: <5.0.0.25.0.20000921172541.0316aa10@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 21 Sep 2000 17:26:09 +0200 To: freebsd-hackers@FreeBSD.ORG From: Len Conrad Subject: Re: low-cost/low-speed HDLC WAN card In-Reply-To: <6041.969548325@critter> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 16:58 21/09/00 +0200, you wrote: >In message <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com>, >Len Conrad >writes: > >I'm back again looking for a low-cost, 128 kbits/sec WAN card, even > >ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to > >drive leased-line links in France. > > >http://www.lanmedia.com > >model LMC1000P great card, $200 more that etinc 5025 thanks anyway, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 8:35:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id ACF1D37B422 for ; Thu, 21 Sep 2000 08:35:49 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 927BC6A901 for ; Thu, 21 Sep 2000 17:35:48 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id ABBD1E1C024C; Thu, 21 Sep 2000 17:39:41 +0200 Message-Id: <5.0.0.25.0.20000921173450.0316ab80@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 21 Sep 2000 17:35:45 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: low-cost/low-speed HDLC WAN card In-Reply-To: References: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:25 21/09/00 -0400, you wrote: >Check out www.sangoma.com (Canada). yes, but also +$200 compared to etinc 5025 that works fine here. www.sealevel.com has some interesting cards, but no FreeBSD support. Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:14: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by hub.freebsd.org (Postfix) with ESMTP id E3B3037B422 for ; Thu, 21 Sep 2000 09:14:01 -0700 (PDT) Received: from viper.cs.Virginia.EDU (viper.cs.Virginia.EDU [128.143.137.17]) by ares.cs.Virginia.EDU (8.9.2/8.9.2/UVACS-2000040300) with ESMTP id MAA28855 for ; Thu, 21 Sep 2000 12:14:00 -0400 (EDT) Received: from localhost (sl5b@localhost) by viper.cs.Virginia.EDU (8.9.2/8.9.2) with ESMTP id MAA02043 for ; Thu, 21 Sep 2000 12:13:59 -0400 (EDT) X-Authentication-Warning: viper.cs.Virginia.EDU: sl5b owned process doing -bs Date: Thu, 21 Sep 2000 12:13:59 -0400 (EDT) From: Song Li To: freebsd-hackers@FreeBSD.ORG Subject: Re: How to time a system call In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A friend asks me what will happen if more than one process trying to read > the stdin at the same time. There is no way to guarantee that any > particular keyboard input will be accepted by a particular process. how about using several psudo terminal? > Since a system call is atomic, this makes me wonder how long it takes to > do a system call, like read(), on a 500Mhz PC? How to time it? I later Usually 50us to several hundrends us, as what I remember. > write a program that forks. So that two processes tries to read the stdin > at the same time. I use read() to read one character at a time. Each > process read 1000 characters and write what they read to a file. I use I/O > redirect to let them read from the same file instead of keyboard. I find > out that one process always call 1000 read()s before the second has a > chance to call read(). > > I hope someone can give me a clue on how this is happening. Maybe the > scheduling quantum (100ms?) is just enough for doing 1000 read() system I guess so, unless the read cannot return instantly and cause the volunteer context switch. > calls. Is there any easy way to time a system call (perhaps with minor > modifications of the kernel)? You may set the ktrace flag when the program was forked or execve-ed. You should also provide the file to which the output will be written when setting the flag. Then you can go to the file /usr/src/sys/kern/kern_ktrace.c and modify the function ktrsyscall(), ktrsysret(), ktrwrite(), etc to decide what kind of information and the format to write. If you want to exclude the idle time of the process, you also need to modify the mi_switch() in file /usr/src/sys/kern_synch.c so that the switch time stamps can be recorded and excluded later. That's what I did before. Probably there is simpler method. > > Any help is appreciated. > > -Zhihui > > > > 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 Sep 21 9:28:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mazurek.man.lodz.pl (mazurek.man.lodz.pl [212.51.192.15]) by hub.freebsd.org (Postfix) with ESMTP id D030F37B422 for ; Thu, 21 Sep 2000 09:27:06 -0700 (PDT) Received: from adas (pb6.lodz.ppp.tpnet.pl [212.160.29.6]) by mazurek.man.lodz.pl (8.9.3/8.9.3) with ESMTP id SAA08356; Thu, 21 Sep 2000 18:21:24 +0200 From: "Piotr Sroczynski" To: "Matthew N. Dodd" Date: Thu, 21 Sep 2000 16:22:04 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: PnP & 4.1 Release Cc: hackers@FreeBSD.ORG Message-ID: <39CA35AC.22149.3A0F38@localhost> References: <39C89827.31219.15DAE5@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 20 Sep 2000, Piotr Sroczynski wrote: > > I know about it but 'ed' in 4.1R doesn't support SMC 8416 in any mode > > set (PnP /not PnP, PIO/shared mem.), because it aways treat 'ed' as > > PnP device and reprogram it on his own. With SMC 8216 (no PnP dev.) I > > haven't any problem. > > You're configuring the card using the EZSetup DOS config utility? You > need to get the right version of the utility and run it with the flags > that tell it to disable PnP on ALL cards in the box. I've had problems > disabling PnP with the wrong config utility version and wrong flags. Mine config utility is: MD5 (ezstart.exe) = 2f6511d72192cc5d899f5f517e5c35fa Have you different? If so, may I ask you, send it to me via e-mail. Piotr Sroczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:54:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 6023537B423 for ; Thu, 21 Sep 2000 09:54:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA02428; Wed, 20 Sep 2000 23:59:25 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210659.XAA02428@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Saab Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Wed, 20 Sep 2000 23:48:19 PDT." <20000920234819.A68513@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 23:59:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith (msmith@freebsd.org) wrote: > > > > I think this is correct, actually. Danny, can you confirm that you're > > using one of the class A address spaces (eg. 10.*.*.*?) > > > > Actually, IMO the code around this is entirely wrong; we should always > > respect the mask supplied by the server, and only use the canonical mask > > if we don't get one at all. > > It does.. look futher down in the code. No, if the supplied mask is wider than the canonical mask (as in eg. Danny's case), the supplied mask is discarded. See the "toss if bogus" test: if (IN_CLASSA(myip.s_addr)) nmask = htonl(IN_CLASSA_NET); else if (IN_CLASSB(myip.s_addr)) nmask = htonl(IN_CLASSB_NET); else nmask = htonl(IN_CLASSC_NET); #ifdef BOOTP_DEBUG if (debug) printf("'native netmask' is %s\n", intoa(nmask)); #endif /* Check subnet mask against net mask; toss if bogus */ if ((nmask & smask) != nmask) { #ifdef BOOTP_DEBUG if (debug) printf("subnet mask (%s) bad\n", intoa(smask)); #endif smask = 0; } /* Get subnet (or natural net) mask */ netmask = nmask; if (smask) netmask = smask; -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:54:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 4DE8337B424 for ; Thu, 21 Sep 2000 09:54:22 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA02252; Wed, 20 Sep 2000 23:48:47 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210648.XAA02252@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Thu, 21 Sep 2000 09:37:16 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 23:48:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > }> }I think this is correct, actually. Danny, can you confirm that you're > }> }using one of the class A address spaces (eg. 10.*.*.*?) > }> } > }> my net is class B. 132.65.0.0 > } > }Gotcha. What's your netmask? I bet it disagrees one way or the other > }with the "canonical" netmask this code assumes. > it's the host part 132.65.80.247, the 247 is 0xF7 and hence class C :-) > my netmask is 255.255.0.0 for the time being till we go vlan. Hmm, I would expect this to be rejected by the offending code, so your original fix is actually wrong, rather it's a bug in the code insisiting that you ought to be using a class C netmask. > }> }Actually, IMO the code around this is entirely wrong; we should always > }> }respect the mask supplied by the server, and only use the canonical mask > }> }if we don't get one at all. > }> } > }> my man! > }> > }> im cleaning up bootp and will let you know. > } > }You could make yourself *really* popular and teach it about DHCP, you > }know. 8) > } > what have you in mind? it already knows some DHCP, the leasing stuff is > yet a gray area with me (i dislike it totaly, but then i own a class B ;-) > i've added hostname though. suggestions? Mostly I guess I'd really like it to simply save *all* of the DHCP response in the environment. Just "dhcp.xxx" where xxx is the parameter value would probably do it, or we can argue about names for everything if there aren't established names already. There should be no real problems with the lease, as most leases are more than long enough to boot the system anyway, so I wouldn't bother with that. > on a different subject, but related: > on my nfsroot client, im now stuck - again -, ls -ls /dev/null shows > strange minor/major: 0, 0x00020002 instead od 2,2 > which of course ruins rc.diskless. Do you have NFSv3 mounts for any of your filesystems listed in /etc/ fstab? The loader only does v2 NFS, and that's the way / is mounted. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:54:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id CCDEA37B42C for ; Thu, 21 Sep 2000 09:54:22 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA02048; Wed, 20 Sep 2000 23:26:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210626.XAA02048@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Thu, 21 Sep 2000 09:15:12 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 23:26:00 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200009210609.XAA01851@mass.osd.bsdi.com>you write: > } > }I think this is correct, actually. Danny, can you confirm that you're > }using one of the class A address spaces (eg. 10.*.*.*?) > } > my net is class B. 132.65.0.0 Gotcha. What's your netmask? I bet it disagrees one way or the other with the "canonical" netmask this code assumes. > }Actually, IMO the code around this is entirely wrong; we should always > }respect the mask supplied by the server, and only use the canonical mask > }if we don't get one at all. > } > my man! > > im cleaning up bootp and will let you know. You could make yourself *really* popular and teach it about DHCP, you know. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:54:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 4752037B43C; Thu, 21 Sep 2000 09:54:23 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA01851; Wed, 20 Sep 2000 23:09:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210609.XAA01851@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: Paul Saab , Mike Smith , freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Wed, 20 Sep 2000 11:57:40 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 23:09:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this is correct, actually. Danny, can you confirm that you're using one of the class A address spaces (eg. 10.*.*.*?) Actually, IMO the code around this is entirely wrong; we should always respect the mask supplied by the server, and only use the canonical mask if we don't get one at all. > bug report: > in lib/libstand/bootp.c: > > if (IN_CLASSA(myip.s_addr)) > nmask = htonl(IN_CLASSA_NET); > else if (IN_CLASSB(myip.s_addr)) > nmask = htonl(IN_CLASSB_NET); > else > nmask = htonl(IN_CLASSC_NET); > should be: > > if (IN_CLASSA(ntohl(myip.s_addr))) > nmask = htonl(IN_CLASSA_NET); > else if (IN_CLASSB(ntohl(myip.s_addr))) > nmask = htonl(IN_CLASSB_NET); > else > nmask = htonl(IN_CLASSC_NET); > > which explains why gateway was zero, even if it was provided by dhcp. > it also explains why it hung trying to mount via nfs. > > danny > > In message <20000919164129.A39104@elvis.mu.org>you write: > }Danny Braniss (danny@cs.huji.ac.il) wrote: > }> In message <20000919024512.A27691@elvis.mu.org>you write: > }> > }> }set this in your dhcpd.conf, but yes, I will fix it. > }> i know it should be in dhcpd.conf but what? :-) btw, i tried router but zilc > }h. > } > }option routers ip; > } > }> } > }> }> 2- if i set different hosts for dhcpd, tftpd, root and swap i get into > }> }> all sort of problems. the most anoying one is that the bios-pxe boot w > }ill > }> }> try and tftpboot from the wrong server. so im using 'option swap-serve > }r' > }> } > }> }I dont follow. > }> } > }> > }> if i set: > }> option root-path "132.65.16.6:/vol1/roots/fbsd-4.1S"; > }> then the ip gets chunked, and it will try to mount from the tftp server - > }> bummer > } > }Yeah.. I have not wanted to do this. I'll look at this in a little while. > } > }> if i set > }> option next-server myrootserver > }> the pxe-bios will use it for the tftpd - bummer > } > }please read the PXE specs to see how to tell it to grab the tftp loader > }from a different server. > } > }> so, at the moment i use > }> option swap-server myrootserver; > }> and it works. but it should be less blackmagic. also, what if i want a > }> different > }> root and swap server? > } > }I'll fix it if I get time. > > > > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:54:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 5D69C37B43F for ; Thu, 21 Sep 2000 09:54:26 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA01260; Wed, 20 Sep 2000 22:29:45 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210529.WAA01260@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: Serial port locks up 4.1 In-reply-to: Your message of "Wed, 20 Sep 2000 12:08:45 EDT." <200009201610.MAA21433@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 22:29:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 04:41 PM 09/19/2000 -0700, you wrote: > >> > >> FYI: It seems that if you try to access the serial port on a MB with the > >> port disabled, freebsd 4.1 will freeze up solid. Enabling the serial > >> console will cause a lock up on boot, and any access to the port will do it > >> as well. > > > >This is probably a feature of the board/super-IO chipset in question. > > > >In particular, the port should never have probed successfully if the port > >was really "disabled", so you should never have been able to access it in > >the first place. > > Its displays an error, but installs it anyway, so it seems that the driver > is at least partially at fault. It happens on several very different MBs > (both SBCs and ATX MBs), so its not an isolated issue. I think you've mentioned this before, but could you tell us again which error it is that the driver is emitting? > >The correct solution, of course, is "don't do that". > > Easy to say , but it might be very hard to find if you have a serial > console enabled and the machine just wont boot. If you had a serial console enabled and the port off and the driver *didn't* attach, you'd still be very unpleasantly surprised. For sure, we should fail attach of the port if it's truly disabled, but I suspect that the BIOS isn't doing a good enough job. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 9:57:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 0397537B422 for ; Thu, 21 Sep 2000 09:57:44 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id JAA00670; Thu, 21 Sep 2000 09:58:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009211658.JAA00670@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation In-reply-to: Your message of "Thu, 21 Sep 2000 10:15:19 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 09:58:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200009210648.XAA02252@mass.osd.bsdi.com>you write: > > }Mostly I guess I'd really like it to simply save *all* of the DHCP > }response in the environment. Just "dhcp.xxx" where xxx is the parameter > }value would probably do it, or we can argue about names for everything if > }there aren't established names already. > } > what's in a name ;-) > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not > enough, so im trying to look into defining a FBSDclass ala PXEClient, and > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. You don't need those; you can get them out of /etc/fstab. In particular, the whole idea of passing the NFS swap details in at this stage is just *totally* bogus. > }There should be no real problems with the lease, as most leases are more > }than long enough to boot the system anyway, so I wouldn't bother with > }that. > } > and this is not a MS system that needs allot of magic before it boots up ;-) Correct. Another thing that needs fixing is dhclient in the diskless case; if you run dhclient it kills the NFS mount for /, so that when it pages some more of itself in (or goes to run /bin/sh to run the dhclient-script) you're screwed... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 10:14:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9D12137B422 for ; Thu, 21 Sep 2000 10:14:51 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA24595 for ; Thu, 21 Sep 2000 13:16:23 -0400 (EDT) Message-Id: <200009211716.NAA24595@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 21 Sep 2000 13:14:29 -0400 To: freebsd-hackers@FreeBSD.ORG From: Dennis Subject: Re: low-cost/low-speed HDLC WAN card In-Reply-To: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:09 PM 09/21/2000 +0200, Len Conrad wrote: >I'm back again looking for a low-cost, 128 kbits/sec WAN card, even >ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to >drive leased-line links in France. > >etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 >megabits. We use two now in our ISP and it works fine, but to use >FreeBSD in a big nationwide VPN/IPsec project, we need to keep the price down. > >We can buy a Zyxel 153X WAN router for about that price, but it >doesn't do VPN nor more than one ethernet i/f nor does it's >non-loggable, limited packet filtering come anywhere near ipfilter. > Every hear of a quantity discount len? Kind of silly looking at list price if you need a lot of cards. We give you a $395. discount on bandwidth management when you buy a card, so the $475. list is flexible if the quanity is there. I can give you 10Mb/s PCI cards including bandwidth management for less than you'd think, and you cant get that from anywhere else. Dennis The price goes down if you guy more than one silly....I have a bunch of 16-bit boards I can give you a good deal on.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 10:34:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 0DB6B37B423; Thu, 21 Sep 2000 10:34:44 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13cAF6-00002a-00; Thu, 21 Sep 2000 20:34:40 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13cAF4-00030c-00; Thu, 21 Sep 2000 20:34:38 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation In-reply-to: Your message of Thu, 21 Sep 2000 09:58:31 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 20:34:38 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009211658.JAA00670@mass.osd.bsdi.com>you write: }> In message <200009210648.XAA02252@mass.osd.bsdi.com>you write: }> }> }Mostly I guess I'd really like it to simply save *all* of the DHCP }> }response in the environment. Just "dhcp.xxx" where xxx is the parameter }> }value would probably do it, or we can argue about names for everything if }> }there aren't established names already. }> } }> what's in a name ;-) }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } }You don't need those; you can get them out of /etc/fstab. In particular, }the whole idea of passing the NFS swap details in at this stage is just }*totally* bogus. } the problem with /etc/fstab it doesn't scale nicely - i have a few hundred hosts that are currently running nfsroot linux, and it's not easy to manage. so having the basic stuff in one file dhcp.conf - even if it has a lousy syntax - seems to me better than having many little fstabs around, specialy if things change. hum, what about the info to mount root? v2/v3, blocksize, timeouts etc? } }Another thing that needs fixing is dhclient in the diskless case; if you }run dhclient it kills the NFS mount for /, so that when it pages some }more of itself in (or goes to run /bin/sh to run the dhclient-script) }you're screwed... well, dhclient is some hack, and probably will be useless, albait the leasing stuff, but i only looked/used it briefly - (i got it to work with my laptop running bsdi/os) im looking at the dhcp.xxxx options, and they are many, what do you think would be the best way to store them? sysctl come to mind, but it's not dynamic, ie, only available if it was set by dhcp. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 10:42:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 3A64A37B42C for ; Thu, 21 Sep 2000 10:42:29 -0700 (PDT) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13cAMW-000ACD-00 for hackers@freebsd.org; Thu, 21 Sep 2000 13:42:20 -0400 Date: Thu, 21 Sep 2000 13:42:20 -0400 From: James FitzGibbon To: hackers@freebsd.org Subject: syslogd patch for n-tier logging topologies Message-ID: <20000921134220.A98032@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://people.targetnet.com/~james/syslog-forwarding-hints.diff.gz (patch relative to 4.1-STABLE, but should apply to -current) I was trying to build a 3 tier logging system, where boxes send syslog messages to a server on the local segment, and then that machine forwards the logs on to the "master" logging machine. The problem I had was that I use the '!progname' syntax in syslog.conf on the master host extensively. This syntax matches any message which *starts* with the given string. However, when a message is received from a remote host and subsequently forwarded to a remote host, the message is prepended with the string "Forwarded from hostname ". The message no longer starts with the program name, so it doesn't get selected by the '!progname' line in syslog.conf. One could just move the forwarding note to the end, but then you have to train your eyes to look at the end of the line instead of the beginning for the hostname. What is really needed is a way for the middle tier to tell the top tier machine the hostname of the machine who sent the message in the first place. My solution isn't the best, but it does have the advantage of not breaking the syslog protocol, and you can mix-and-match the old and new forwarding methods in syslog.conf. Basically, if you specify a hostname in syslog.conf but precede it with a % sign instead of an @, the forwarded message will look like this on the way out (presume the original host is bar, the middle is baz and the top is foo): old: <#>Sep 20 10:52:45 Forwarded from bar: progname: message new: <#>%bar Sep 20 10:52:45 progname: message If syslogd is started with the -h switch (hints), it will look at the first character of the message. If it is a %, syslogd reads the text following the % up to the next space, then reads the message as usual. When the log message is processed by logmsg(), I send the hint hostname instead of the gethostbyaddr-derived hostname. As a result, the top host logs the message with the proper hostname of the bottom host. The message still starts with the program name, so the '!progname' syntax works. If the remote host receiving the message doesn't use the -h switch or is running a non-modified copy of syslogd, the message will still get logged, but the hint will appear literally in the log. This isn't pretty, but it prevents the hints from crashing older syslog daemons. One other advantage to this system is that you only have to update syslogd or syslog.conf on the middle and top tiers (or more specifically, every tier except the bottom one). The majority of machines are in the lower tier, so rolling this out isn't too painful. I expect there will be a few comments on this, so bear in mind that the code isn't polished much. I don't know if using '%' as the selector character is a good idea, and there is the issue of spoofing: > logger "%af.mil Sep 21 13:37:30 icbmd[378] Launch commit in 39 seconds" Comments are appreciated. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 10:44:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id A5E5637B424 for ; Thu, 21 Sep 2000 10:44:50 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id E6C3D9B26; Thu, 21 Sep 2000 18:44:49 +0100 (BST) Date: Thu, 21 Sep 2000 18:44:49 +0100 From: Josef Karthauser To: Brian Somers Cc: Christian Weisgerber , freebsd-hackers@FreeBSD.ORG Subject: Re: mergemaster RFC (long) Message-ID: <20000921184449.K1694@pavilion.net> Mail-Followup-To: Josef Karthauser , Brian Somers , Christian Weisgerber , freebsd-hackers@FreeBSD.ORG References: <8q62st$1nkh$1@ganerc.mips.inka.de> <200009202034.e8KKY3s18401@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009202034.e8KKY3s18401@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Sep 20, 2000 at 09:34:03PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another thing that would be very useful is that during a merge of two files that it's possible to specify both the left hand side and the right hand side. That would fix cases like: Orig: # $FreeBSD: src/etc/shells,v 1.4 SOMEDATE$ # # List of acceptable shells for chpass(1). # Ftpd will not allow users to connect who are not using # one of these shells. /bin/sh /bin/csh /usr/local/bin/zsh The new 1.5 version has: /bin/tcsh in it. Mergemaster won't let me have both my /usr/local/bin/zsh and the /bin/tcsh. During merge I can have either but not both :( Joe annoying when you onl On Wed, Sep 20, 2000 at 09:34:03PM +0100, Brian Somers wrote: > > Brian Somers wrote: > > > > > > First, the things I am definitely going to do. Christian "naddy" > > > > Weisgerber has taken on the task of porting mm to openbsd. > > > > > > I think it would be nice to aim to keep the two scripts exactly the > > > same, using `uname` when it's really necessary. > > > > If I have interpreted the noises Theo has made correctly, he wants > > mergemaster in the base tree. I don't think he'll keep a "case > > `uname` ..." in there. > > Of course if we didn't need it... that'd be far better :-) > > > Most of the diff deals with two simple differences: > > - mergemaster uses "read -p " throughout. That fails for > > OpenBSD's /bin/sh (pdksh), where "read -p" means something entirely > > different. > > That's not too bad as the read -p can be changed to echo/read. > > > - On OpenBSD, "install" is synonymous to "install -c". FreeBSD still > > has the old behavior where plain "install" deletes the source file. > > Maybe the best bet here is to have ``INSTALL=install'' at the top of > the script (``INSTALL="install -c" for FreeBSD). It's a difference, > but managable. > > > If we can get rid of those, the actual differences become more > > visible. > > > > Oh, and changing every instance of "FreeBSD" into "${OPSYS}" or > > some such would remove another few diff lines. > > Aye. Looks like we're thinking along the same lines. > > I'll have to talk to Wes at BSDCon about trying to get the NetBSD > guys to introduce it there too - maybe some of the NetBSD developers > will be there too. > > > -- > > Christian "naddy" Weisgerber naddy@mips.inka.de > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 11:36: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 52ECF37B61D for ; Thu, 21 Sep 2000 11:35:53 -0700 (PDT) Received: (qmail 23762 invoked from network); 21 Sep 2000 18:36:03 -0000 Received: from arsenic.theshell.com (HELO tequila) (63.236.138.5) by arsenic.theshell.com with SMTP; 21 Sep 2000 18:36:03 -0000 From: "Peter Avalos" To: "Josef Karthauser" Cc: Subject: RE: mergemaster RFC (long) Date: Thu, 21 Sep 2000 13:35:42 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20000921184449.K1694@pavilion.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %? l: use the left version r: use the right version e l: edit then use the left version e r: edit then use the right version e b: edit then use the left and right versions concatenated e: edit a new version s: silently include common lines v: verbosely include common lines q: quit Look like 'e b' was designed for that. Peter Avalos TheShell.com -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/ED/B d-(+) s:+> a-- C++$ UBLO++++$ P+ L++++ E- W+ N+ o? K? w(++) !O M- V- PS+ PE++ Y+ PGP++ t+@ 5 X- R- tv+ b++ DI- D-- G e>+++ h-- r++ y++ ------END GEEK CODE BLOCK------ > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Josef Karthauser > Sent: Thursday, September 21, 2000 12:45 PM > To: Brian Somers > Cc: Christian Weisgerber; freebsd-hackers@FreeBSD.ORG > Subject: Re: mergemaster RFC (long) > > > > Another thing that would be very useful is that during a > merge of two files that it's possible to specify both > the left hand side and the right hand side. That would > fix cases like: > > Orig: > > # $FreeBSD: src/etc/shells,v 1.4 SOMEDATE$ > # > # List of acceptable shells for chpass(1). > # Ftpd will not allow users to connect who are not using > # one of these shells. > > /bin/sh > /bin/csh > /usr/local/bin/zsh > > > The new 1.5 version has: /bin/tcsh in it. Mergemaster won't let > me have both my /usr/local/bin/zsh and the /bin/tcsh. During merge > I can have either but not both :( > > Joe > > > annoying when you onl > On Wed, Sep 20, 2000 at 09:34:03PM +0100, Brian Somers wrote: > > > Brian Somers wrote: > > > > > > > > First, the things I am definitely going to do. > Christian "naddy" > > > > > Weisgerber has taken on the task of porting mm to openbsd. > > > > > > > > I think it would be nice to aim to keep the two scripts exactly the > > > > same, using `uname` when it's really necessary. > > > > > > If I have interpreted the noises Theo has made correctly, he wants > > > mergemaster in the base tree. I don't think he'll keep a "case > > > `uname` ..." in there. > > > > Of course if we didn't need it... that'd be far better :-) > > > > > Most of the diff deals with two simple differences: > > > - mergemaster uses "read -p " throughout. That fails for > > > OpenBSD's /bin/sh (pdksh), where "read -p" means something entirely > > > different. > > > > That's not too bad as the read -p can be changed to echo/read. > > > > > - On OpenBSD, "install" is synonymous to "install -c". FreeBSD still > > > has the old behavior where plain "install" deletes the source file. > > > > Maybe the best bet here is to have ``INSTALL=install'' at the top of > > the script (``INSTALL="install -c" for FreeBSD). It's a difference, > > but managable. > > > > > If we can get rid of those, the actual differences become more > > > visible. > > > > > > Oh, and changing every instance of "FreeBSD" into "${OPSYS}" or > > > some such would remove another few diff lines. > > > > Aye. Looks like we're thinking along the same lines. > > > > I'll have to talk to Wes at BSDCon about trying to get the NetBSD > > guys to introduce it there too - maybe some of the NetBSD developers > > will be there too. > > > > > -- > > > Christian "naddy" Weisgerber > naddy@mips.inka.de > > > > -- > > Brian > > > > > > Don't _EVER_ lose your sense of humour ! > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, > joe@tao.org.uk] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 11:40:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id BB9A037B423 for ; Thu, 21 Sep 2000 11:40:53 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA22713; Thu, 21 Sep 2000 14:40:26 -0400 (EDT) Date: Thu, 21 Sep 2000 14:40:26 -0400 (EDT) From: "Matthew N. Dodd" To: Piotr Sroczynski Cc: hackers@FreeBSD.ORG Subject: Re: PnP & 4.1 Release In-Reply-To: <39CA35AC.22149.3A0F38@localhost> 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, 21 Sep 2000, Piotr Sroczynski wrote: > Mine config utility is: > MD5 (ezstart.exe) = 2f6511d72192cc5d899f5f517e5c35fa > Have you different? If so, may I ask you, send it to me via e-mail. You should really just go to the SMC FTP/WEB site and get the right one. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 11:42:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 8C18F37B443; Thu, 21 Sep 2000 11:42:16 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e8LIgGG54397; Thu, 21 Sep 2000 11:42:16 -0700 (PDT) (envelope-from dillon) Date: Thu, 21 Sep 2000 11:42:16 -0700 (PDT) From: Matt Dillon Message-Id: <200009211842.e8LIgGG54397@earth.backplane.com> To: Mike Smith Cc: Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: dhcp boot was: Re: diskless workstation References: <200009211658.JAA00670@mass.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> In message <200009210648.XAA02252@mass.osd.bsdi.com>you write: :> :> }Mostly I guess I'd really like it to simply save *all* of the DHCP :> }response in the environment. Just "dhcp.xxx" where xxx is the parameter :> }value would probably do it, or we can argue about names for everything if :> }there aren't established names already. :> } :> what's in a name ;-) :> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not :> enough, so im trying to look into defining a FBSDclass ala PXEClient, and :> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. : :You don't need those; you can get them out of /etc/fstab. In particular, :the whole idea of passing the NFS swap details in at this stage is just :*totally* bogus. You can specify swap paritions with dhcpd just fine, just use the the numerical IP: option root-path "999.999.99.99:/"; option option-128 "999.999.99.99:/images/swap"; -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 12:57:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B33A37B424; Thu, 21 Sep 2000 12:57:54 -0700 (PDT) Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC136E328B; Thu, 21 Sep 2000 12:57:47 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e8LJtkF55089; Thu, 21 Sep 2000 12:55:46 -0700 (PDT) (envelope-from dillon) Date: Thu, 21 Sep 2000 12:55:46 -0700 (PDT) From: Matt Dillon Message-Id: <200009211955.e8LJtkF55089@earth.backplane.com> To: Matt Dillon Cc: Mike Smith , Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: dhcp boot was: Re: diskless workstation References: <200009211658.JAA00670@mass.osd.bsdi.com> <200009211842.e8LIgGG54397@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : You can specify swap paritions with dhcpd just fine, just use : the the numerical IP: : : option root-path "999.999.99.99:/"; : option option-128 "999.999.99.99:/images/swap"; : : -Matt You know, my written english is getting *really* bad! I meant, just use the numerical dhcp (really the bootp protocol) option '128' to specify the swap. You can specify any option you want numerically, whether dhcp has named it or not. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 13:10:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 8BDB537B43C for ; Thu, 21 Sep 2000 13:10:06 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8LK5sv68414; Thu, 21 Sep 2000 21:05:54 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8LK1Fs84072; Thu, 21 Sep 2000 21:01:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009212001.e8LK1Fs84072@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Josef Karthauser , Brian Somers , Christian Weisgerber , freebsd-hackers@FreeBSD.ORG Subject: Re: mergemaster RFC (long) In-Reply-To: Message from Josef Karthauser of "Thu, 21 Sep 2000 18:44:49 BST." <20000921184449.K1694@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 21:01:15 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Another thing that would be very useful is that during a > merge of two files that it's possible to specify both > the left hand side and the right hand side. That would > fix cases like: > > Orig: > > # $FreeBSD: src/etc/shells,v 1.4 SOMEDATE$ > # > # List of acceptable shells for chpass(1). > # Ftpd will not allow users to connect who are not using > # one of these shells. > > /bin/sh > /bin/csh > /usr/local/bin/zsh > > > The new 1.5 version has: /bin/tcsh in it. Mergemaster won't let > me have both my /usr/local/bin/zsh and the /bin/tcsh. During merge > I can have either but not both :( > > Joe You can ``e b'' (edit both) from the sdiff prompt. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 15:30: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spok.premier1.net (spok.premier1.net [64.38.159.38]) by hub.freebsd.org (Postfix) with ESMTP id 13C6337B42C; Thu, 21 Sep 2000 15:29:59 -0700 (PDT) Received: from kemp (ip-64-38-158-182.dialup.seanet.com [64.38.158.182]) by spok.premier1.net (8.9.3/8.9.3) with SMTP id PAA06398; Thu, 21 Sep 2000 15:28:48 -0700 (PDT) From: "Keith Kemp" To: "Alfred Perlstein" , "Edward Elhauge" Cc: , Subject: RE: Frustration with SCSI system Date: Thu, 21 Sep 2000 15:29:17 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000920125128.F9141@fw.wintelcom.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the topic of Vinum, what do you guys do about the / partion since it appears that a vinum partion can not be the boot partion. I would hate to have the drive with my boot partion fail and be left with a non working server. Keith Kemp > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Alfred Perlstein > Sent: Wednesday, September 20, 2000 12:51 PM > To: Edward Elhauge > Cc: freebsd-hackers@FreeBSD.ORG; freebsd-isp@FreeBSD.ORG > Subject: Re: Frustration with SCSI system > > > * Edward Elhauge [000920 12:48] wrote: > > Hello Freebsders, > > > > I've been using FreeBSD over the last 6 years (since I switched from > > NetBSD) to run a small ISP out of my basement. > > > > I've had about six disk crashes in as many years and still > don't know how > > to work reliably with them. > > "man vinum" > > software mirroring == good. > > :) > > -Alfred > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" 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 Sep 21 15:31:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.dtix.com (alpha.dtix.com [198.62.174.1]) by hub.freebsd.org (Postfix) with ESMTP id 612A837B505 for ; Thu, 21 Sep 2000 15:31:12 -0700 (PDT) Received: from gigabit (beta.dtix.com [198.62.174.3]) by alpha.dtix.com (8.9.3/8.8.7) with SMTP id RAA27065 for ; Thu, 21 Sep 2000 17:48:51 -0400 Message-ID: <02a901c0241c$95d56b90$e1ae3ec6@dtix.com> From: "Ashish Lal" To: Subject: question on BSD driver Date: Thu, 21 Sep 2000 18:37:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello: Is there an online driver (and code/docs) for a packet-over-sonet (POS) card in Free BSD? Any help would be greatly appreciated. Thanks --Ashish To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 16:24:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by hub.freebsd.org (Postfix) with ESMTP id 5308537B43E for ; Thu, 21 Sep 2000 16:24:18 -0700 (PDT) Received: from staff3.texas.net (staff3.texas.net [207.207.0.40]) by mw2.texas.net (2.4/2.4) with ESMTP id SAA11368; Thu, 21 Sep 2000 18:24:06 -0500 (CDT) Received: (from doug@localhost) by staff3.texas.net (8.9.3/8.9.2) id SAA82948; Thu, 21 Sep 2000 18:24:06 -0500 (CDT) (envelope-from doug@texas.net) Date: Thu, 21 Sep 2000 18:24:05 -0500 From: Douglas Swarin To: freebsd-hackers@freebsd.org Cc: kkemp@nwcr.net Subject: Re: Frustration with SCSI system Message-ID: <20000921182405.A82919@staff.texas.net> References: <20000920125128.F9141@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kkemp@nwcr.net on Thu, Sep 21, 2000 at 03:29:17PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ideally, I would use one of the IDE flash-based drives on the market. One brand is SanDisk, and they take a standard IDE connector and fit into a 3.5" drive bay. You can get them very reasonably priced up to 128MB or so, which is just fine for a boot partition. Since flash drives have no moving parts, mechanical failure is not an issue, and since the root partition is not written to much, the flash will not wear out for a long time (flash cells wear out after about 100,000 writes; the flash drives do load balancing and stuff to ensure that the (many) cells in the drive are written to evenly). Doug On Thu, Sep 21, 2000 at 03:29:17PM -0700, Keith Kemp wrote: > On the topic of Vinum, what do you guys do about the / partion since it > appears that a vinum partion can not be the boot partion. > > I would hate to have the drive with my boot partion fail and be left with a > non working server. > > Keith Kemp > > > -----Original Message----- > > From: owner-freebsd-isp@FreeBSD.ORG > > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Alfred Perlstein > > Sent: Wednesday, September 20, 2000 12:51 PM > > To: Edward Elhauge > > Cc: freebsd-hackers@FreeBSD.ORG; freebsd-isp@FreeBSD.ORG > > Subject: Re: Frustration with SCSI system > > > > > > * Edward Elhauge [000920 12:48] wrote: > > > Hello Freebsders, > > > > > > I've been using FreeBSD over the last 6 years (since I switched from > > > NetBSD) to run a small ISP out of my basement. > > > > > > I've had about six disk crashes in as many years and still > > don't know how > > > to work reliably with them. > > > > "man vinum" > > > > software mirroring == good. > > > > :) > > > > -Alfred > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 16:44:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 368CC37B423 for ; Thu, 21 Sep 2000 16:44:42 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA07456; Thu, 21 Sep 2000 17:44:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA63251; Thu, 21 Sep 2000 17:44:32 -0600 (MDT) Message-Id: <200009212344.RAA63251@harmony.village.org> To: Douglas Swarin Subject: Re: Frustration with SCSI system Cc: freebsd-hackers@FreeBSD.ORG, kkemp@nwcr.net In-reply-to: Your message of "Thu, 21 Sep 2000 18:24:05 CDT." <20000921182405.A82919@staff.texas.net> References: <20000921182405.A82919@staff.texas.net> <20000920125128.F9141@fw.wintelcom.net> Date: Thu, 21 Sep 2000 17:44:32 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000921182405.A82919@staff.texas.net> Douglas Swarin writes: : Ideally, I would use one of the IDE flash-based drives on the market. One : brand is SanDisk, and they take a standard IDE connector and fit into a : 3.5" drive bay. You can get them very reasonably priced up to 128MB or : so, which is just fine for a boot partition. Since flash drives have no : moving parts, mechanical failure is not an issue, and since the root : partition is not written to much, the flash will not wear out for a : long time (flash cells wear out after about 100,000 writes; the flash : drives do load balancing and stuff to ensure that the (many) cells in : the drive are written to evenly). We use these devices heavily at Timing Solutions. Or rather we use a IDE <-> CF adapter and haven't had any devices wear out. And some of these devices have had rather heavy use. I think that it is closer to 1 million writes per cell, but I don't have my spec sheets handy. Are you sure that they do write balancing? The indications I have from the base chip technology is that they don't. I could have missed that in the data sheets. It has been a little while since I looked at them, so I might be misremembering. I can't seem to find the data sheets I looked at before. In any event, this works well. I usually have / be read only. This can be practacle if you don't have any users that desire to change their passwords... Since I have serveral machines that have an extremely limited number of users on, this works well. One can also mount / rw if you need to do maintenance on it for whatever reason. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 17: 6:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id CBDE337B43F; Thu, 21 Sep 2000 17:06:43 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-236.nnj.dialup.bellatlantic.net [151.198.117.236]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA23170; Thu, 21 Sep 2000 20:06:11 -0400 (EDT) Message-ID: <39CAA323.20C6A0E5@bellatlantic.net> Date: Thu, 21 Sep 2000 20:09:07 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Mike Cc: "Aleksandr A.Babaylov" , David Scheidt , ee@uncanny.net, freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system References: <200009202250.CAA01922@aaz.links.ru> <4.3.2.7.2.20000920210124.0f722908@mail.mikesweb.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike wrote: > > I've used various Seagate SCSI drives exclusively in all of my boxes and > only had one failure, which I was still able to recover all the data from > before replacing it. The first box I built back in '97 had an UW Seagate in > it that I bought used, and it was very heavily used for 2 years, and I > still have that original configuration for various small projects. Right > now I have 4 boxes with Barracuda drives (7200RPM) almost to the ceiling in > a closet at one site that temps can get up to 80 degrees F, with a constant > fan on them, all doing fine.. I build a couple boxes with Seagate Cheetah's I had quite bad experience with Seagate disks of series Medalist (IDE), Hawk and Barracuda. Any failures for any taste: bed blocks developed over time, disks just dying, disks occasionally self-erasing the boot sector, disks agreeing to start only after 15 minutes in front of air conditioning cold air duct. The worst case was when both disks in a mirror developed bad blocks with half an hour interval. Luckily the bad block on the second disk happened within the Oracle's TEMP tablespace, so the actual data were not lost. Of 40 IDE medalist disks 1/3 developed various kinds of problems within a year. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 18:24:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3a105.neo.rr.com [24.93.180.105]) by hub.freebsd.org (Postfix) with ESMTP id 3975737B42C for ; Thu, 21 Sep 2000 18:24:24 -0700 (PDT) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id e8M1J9h26898 for ; Thu, 21 Sep 2000 21:19:09 -0400 Date: Thu, 21 Sep 2000 21:19:08 -0400 (EDT) From: Mike Nowlin To: freebsd-hackers@freebsd.org Subject: udma file system corruption 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 Had an interesting one tonight... I've been using rrestore to duplicate the filesystems on a bunch of machines that I'm mass-producing. Things seemed to be going OK, but one of these machines (Compaq Presario 5340) booted up twice, started throwing up strange warnings about UDMA not working correctly (and falling back to PIO), then refused to boot - when it tried to mount /, it would panic every time... Took the HD out and popped it into another machine, and half of the files in / and /var were basically worthless - "ls" would show them, "ls -l" wouldn't, couldn't remove the entries, etc... Realizing that there's not enough detail here to get an accurate answer, is this something that can likely be contributed to iffy UDMA support on this particular machine? I'm just gonna turn this box into another diskless machine, but I'm curious... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 18:39: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 4160937B440 for ; Thu, 21 Sep 2000 18:39:02 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8M1cCR29352; Fri, 22 Sep 2000 11:08:12 +0930 (CST) (envelope-from grog) Date: Fri, 22 Sep 2000 11:08:12 +0930 From: Greg Lehey To: Mohan Krishna P Cc: freebsd-hackers@FreeBSD.ORG, arch@wantadilla.lemis.com Subject: Re: semaphores inside kernel??? Message-ID: <20000922110812.J66887@wantadilla.lemis.com> References: <20000919035519.24195.qmail@web115.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000919035519.24195.qmail@web115.yahoomail.com>; from penumetcha@yahoo.com on Mon, Sep 18, 2000 at 08:55:19PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Monday, 18 September 2000 at 20:55:19 -0700, Mohan Krishna P wrote: > hi, It would make things a *lot* easier to read if you made your lines all the same length. I've fixed it here. > i am implementing a pseudo-devicer, many instaces of this device may > be active, all have to share a resource. all instances have to > synchronize their access to the resource. trying to implement this, > i ended up with a less powerful version of semaphores. since the > resultant code became little complex, i want to replace that with > the more generic semaphores. > > i checked the include files, but i couldn't find any semaphore > functions(semget,semctl,semop) which are specific or meant for use > inside kernel. does it mean they aren't available inside kernel?? > if i am wrong, can someone suggest me how to use them?? You're probably thinking about System V user-accessible semaphores. This particular semaphore implementation is complicated and slow, and the implementation is flawed. You don't want them in the kernel, and yes, they're not available at the moment, though you could probably do it. > does it mean they aren't available inside kernel?? if i am wrong, > can someone suggest me how to use them?? Well, the real question is, what exactly do you want to use them for? As John Baldwin says, we now have mutexes, though they won't show in a -RELEASE version for quite some time. We're still discussing the evolution of locking primitives, but at the moment it looks like we can distinguish between semaphores and "mutexes" in the following way: - A "mutex" (in quotes because "mutex" is also a generic term; this is more like a simple lock) is used for short term serialization when accessing critical data or code. Only one process can take the mutex at a time. - A semaphore may be held for longer periods of time. Multiple processes (for small values of "multiple") can take the semaphore at the same time. This means that, unlike mutexes, semaphores don't have "owners", and the process which "releases" the semaphore may not be the one that took it. Which better describes your usage? Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 19:37:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 80DBF37B423; Thu, 21 Sep 2000 19:37:49 -0700 (PDT) Received: (from jgreco@localhost) by aurora.sol.net (8.9.3/8.9.2/SNNS-1.02) id VAA16401; Thu, 21 Sep 2000 21:37:47 -0500 (CDT) From: Joe Greco Message-Id: <200009220237.VAA16401@aurora.sol.net> Subject: Re: Frustration with SCSI system To: imp@village.org Date: Thu, 21 Sep 2000 21:37:46 -0500 (CDT) Cc: hackers@freebsd.org, isp@freebsd.org X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops, sorry about the previous misfire... > In message <200009201958.MAA45703@ns2.uncanny.net> Edward Elhauge writes: > : to autorecover on bad sectors, but every system that I've had to recover > : seems to be in a state where the bad sectors aren't remapping. I've tried > > I've often wanted to write a bad block remapper. While SCSI is > supposed to do this automatically, I've found that a scan on any > adaptec controller will remap these blocks (forces the remapping). I've got a program which attempts to read all blocks and may be able to rewrite bad blocks. It's nothing fancy. Only works if you've got auto-reallocate turned on in the drive. % cat diskscan.c #include #include #include #include int fixup(off, fd) off_t off; int fd; { char buffer[512]; int i, rval; for (i = 0; i < 65536; i += 512) { if (lseek(fd, off + i, SEEK_SET) < 0) { doerror("lseek", off + i, 0); } if ((rval = read(fd, buffer, sizeof(buffer))) != sizeof(buffer)) { if (errno) { if (lseek(fd, off + i, SEEK_SET) < 0) { doerror("lseek", off + i, 0); } write(fd, buffer, sizeof(buffer)); } } } } int doerror(str, off, type) char *str; off_t off; int type; { static int ign = 0; char buffer[80]; fprintf(stderr, "\nError at %qx, ", (quad_t) off); perror(str); if (! ign) { if (type) { fprintf(stderr, "Attempt to correct? (y/n/a) "); } else { fprintf(stderr, "Press 'y' to continue: "); } while (! ign) { fgets(buffer, sizeof(buffer), stdin); if (*buffer == 'y') { return(0); } if (*buffer == 'n') { return(1); } if (*buffer == 'a') { ign++; return(0); } } } return(0); } int main(argc, argv) int argc; char *argv[]; { int fd, rval; char buffer[65536]; off_t off = 0; int eof = 0; int count = 0; if (argc != 2) { fprintf(stderr, "usage: diskscan \n"); exit(1); } if ((fd = open(argv[1], O_RDWR, 0644)) < 0) { perror(argv[1]); } while (! eof) { if (! count) { fprintf(stderr, "%qx, ", (quad_t) off); } count++; count %= 8; if (lseek(fd, off, SEEK_SET) < 0) { doerror("lseek", off, 0); } if ((rval = read(fd, buffer, sizeof(buffer))) != sizeof(buffer)) { if (errno) { if (! doerror("read", off, 1)) { fixup(off, fd); } } } off += sizeof(buffer); } } I don't even guarantee that it's correct, but I do use it with some success... vinum takes an entire drive offline when it sees an error, and I use this to scan for and fix errors before turning the drive back on. -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 20:29:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 1056337B424; Thu, 21 Sep 2000 20:29:00 -0700 (PDT) Received: (from jgreco@localhost) by aurora.sol.net (8.9.3/8.9.2/SNNS-1.02) id VAA16041; Thu, 21 Sep 2000 21:33:03 -0500 (CDT) From: Joe Greco Message-Id: <200009220233.VAA16041@aurora.sol.net> Subject: Re: Frustration with SCSI system To: imp@village.org, hackers@freebsd.org, isp@freebsd.org Date: Thu, 21 Sep 2000 21:33:03 -0500 (CDT) In-Reply-To: <200009220229.VAA06232@earth.execpc.com> from "jgreco@execpc.com" at Sep 21, 2000 09:29:39 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Path: news.sol.net!newsops.execpc.com!169.207.30.19.MISMATCH!spool0-nwblwi.newsops.execpc.com!newspump.sol.net!news.execpc.com!newshub.sol.net!sol.net!newspeer.sol.net!ns.sol.net!lists.sol.net!not-for-mail > Newsgroups: sol.lists.freebsd.hackers,sol.lists.freebsd.isp > Date: 20 Sep 2000 22:02:50 +0000 > Sender: news@ns.sol.net > Approved: news@ns.sol.net > Organization: sol.net Network Services - Milwaukee, WI > References: <200009201958.MAA45703_ns2.uncanny.net@ns.sol.net> > X-To: ee@uncanny.net > X-Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG > From: imp@village.org > Subject: Re: Frustration with SCSI system > Message-ID: <200009202202.QAA50356_harmony.village.org@ns.sol.net> > Xref: news.sol.net sol.lists.freebsd.hackers:21298 sol.lists.freebsd.isp:6352 > > In message <200009201958.MAA45703@ns2.uncanny.net> Edward Elhauge writes: > : to autorecover on bad sectors, but every system that I've had to recover > : seems to be in a state where the bad sectors aren't remapping. I've tried > > I've often wanted to write a bad block remapper. While SCSI is > supposed to do this automatically, I've found that a scan on any > adaptec controller will remap these blocks (forces the remapping). > About 10% of the time that's all a drive with this problem needs to > survive indefinitely. The other 90% of the time the disk is about to > go tits up in a heap big time way and warrantee replacement is > recommended. About 75% of the time a rescan + immmediate dump will > save me. > > I've had 2 disks that seem to have lost their bad block mappings that > the adaptec verify function has saved me from sending them back (they > were out of warantee anyway). However, on the other 20ish disks I've > tried this on have died within days of doing this. > > Even if we had bad144 support, the drive will need so many bad blocks > remapped in a short period of time that it isn't worth while. > > Finally, I've found that climate controlled and dust free environments > help a lot. RAID hardware/software is definitely the right way to > deal when you go to the next level. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 22:26:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by hub.freebsd.org (Postfix) with ESMTP id 3B2D837B422 for ; Thu, 21 Sep 2000 22:26:27 -0700 (PDT) Received: from staff3.texas.net (staff3.texas.net [207.207.0.40]) by mw2.texas.net (2.4/2.4) with ESMTP id AAA19207; Fri, 22 Sep 2000 00:26:25 -0500 (CDT) Received: (from doug@localhost) by staff3.texas.net (8.9.3/8.9.2) id AAA84307; Fri, 22 Sep 2000 00:26:24 -0500 (CDT) (envelope-from doug@texas.net) Date: Fri, 22 Sep 2000 00:26:24 -0500 From: Douglas Swarin To: Warner Losh Cc: freebsd-hackers@freebsd.org Subject: Re: Frustration with SCSI system Message-ID: <20000922002624.A84288@staff.texas.net> References: <20000921182405.A82919@staff.texas.net> <20000920125128.F9141@fw.wintelcom.net> <20000921182405.A82919@staff.texas.net> <200009212344.RAA63251@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009212344.RAA63251@harmony.village.org>; from imp@village.org on Thu, Sep 21, 2000 at 05:44:32PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 21, 2000 at 05:44:32PM -0600, Warner Losh wrote: > In message <20000921182405.A82919@staff.texas.net> Douglas Swarin writes: > : Ideally, I would use one of the IDE flash-based drives on the market. One > : brand is SanDisk, and they take a standard IDE connector and fit into a > : 3.5" drive bay. You can get them very reasonably priced up to 128MB or > : so, which is just fine for a boot partition. Since flash drives have no > : moving parts, mechanical failure is not an issue, and since the root > : partition is not written to much, the flash will not wear out for a > : long time (flash cells wear out after about 100,000 writes; the flash > : drives do load balancing and stuff to ensure that the (many) cells in > : the drive are written to evenly). > > We use these devices heavily at Timing Solutions. Or rather we use > a IDE <-> CF adapter and haven't had any devices wear out. And some > of these devices have had rather heavy use. I think that it is closer > to 1 million writes per cell, but I don't have my spec sheets handy. > > Are you sure that they do write balancing? The indications I have > from the base chip technology is that they don't. I could have missed > that in the data sheets. It has been a little while since I looked at > them, so I might be misremembering. I can't seem to find the data > sheets I looked at before. > > In any event, this works well. I usually have / be read only. This > can be practacle if you don't have any users that desire to change > their passwords... Since I have serveral machines that have an > extremely limited number of users on, this works well. One can also > mount / rw if you need to do maintenance on it for whatever reason. I was being pessimistic as to the number of writes. I have heard figures in the range of a million writes per cell as well. The technology is always improving, of course. As to the write balancing, I've seen no hard technical data on it, but I've heard it quoted from many sources. So I may be completely wrong. A brief Google search gives http://www.embedded.com/98/9801spec.htm which mentions that ATA flash can indeed do such balancing about 1/3 of the way down the page (search for 'evenly' in the text). The technical term appears to be 'wear leveling'. But I digress. I'm glad to hear this method validated by someone with much more experience in the field. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 22:39:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 10A3337B422 for ; Thu, 21 Sep 2000 22:39:46 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13cFAt-0000RP-00; Thu, 21 Sep 2000 16:50:39 -0600 Message-ID: <39CA90BF.8DEC13D0@softweyr.com> Date: Thu, 21 Sep 2000 16:50:39 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: low-cost/low-speed HDLC WAN card References: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > > I'm back again looking for a low-cost, 128 kbits/sec WAN card, even > ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to > drive leased-line links in France. > > etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 > megabits. We use two now in our ISP and it works fine, but to use > FreeBSD in a big nationwide VPN/IPsec project, we need to keep the price down. > > We can buy a Zyxel 153X WAN router for about that price, but it > doesn't do VPN nor more than one ethernet i/f nor does it's > non-loggable, limited packet filtering come anywhere near ipfilter. This may sound heretical, but have you considered using the router AND a FreeBSD firewall? Last I checked, ethernet cards to plug into the router and the local net(s) are quite inexpensive. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 21 23:27:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 14D8137B423 for ; Thu, 21 Sep 2000 23:27:39 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 18CDB6A901; Fri, 22 Sep 2000 08:27:37 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id ACB0CA210086; Fri, 22 Sep 2000 08:31:12 +0200 Message-Id: <5.0.0.25.0.20000922081407.02ed6370@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 22 Sep 2000 08:27:26 +0200 To: Wes Peters From: Len Conrad Subject: Re: low-cost/low-speed HDLC WAN card Cc: freebsd-hackers@freebsd.org In-Reply-To: <39CA90BF.8DEC13D0@softweyr.com> References: <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm back again looking for a low-cost, 128 kbits/sec WAN card, even > > ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to > > drive leased-line links in France. > > > > etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 > > megabits. We use two now in our ISP and it works fine, but to use > > FreeBSD in a big nationwide VPN/IPsec project, we need to keep > the price down. > > > > We can buy a Zyxel 153X WAN router for about that price, but it > > doesn't do VPN nor more than one ethernet i/f nor does it's > > non-loggable, limited packet filtering come anywhere near ipfilter. > >This may sound heretical, but have you considered using the router AND a >FreeBSD firewall? Yes, of course, this is precisely our approach for the ISDN local loop, with the sweet little Zyxel 128 ISDN router/bridge as our "ISDN-to-Ethernet" bridge (no ip in Zyxel), since we think Zyxel ISDN functions are well ahead/proven vs what we can accomplish with the ISDN card/drivers for FreeBSD. Dennis/etinc is calling me silly for not asking for a discount on his cards, so I'll see how low he can go. But we've realized that the 1U and 2U boxes have PCI risers, not ISA risers. Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 0: 1:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tristero.cryptocourier.com (black-3.dsl.speakeasy.net [216.231.56.189]) by hub.freebsd.org (Postfix) with SMTP id 2351937B423 for ; Fri, 22 Sep 2000 00:01:29 -0700 (PDT) Received: (qmail 10342 invoked from network); 22 Sep 2000 07:04:18 -0000 Received: from cx435051-d.fed1.sdca.home.com (HELO thirteen.flargh.com) (u3708@24.5.33.77) by tristero.cryptocourier.com with SMTP; 22 Sep 2000 07:04:18 -0000 From: jdb-lists-freebsd-hackers@layer8.net To: hackers@freebsd.org Subject: Re: Frustration with SCSI system In-Reply-To: Your message of "Thu, 21 Sep 2000 18:24:05 CDT." <20000921182405.A82919@staff.texas.net> Date: Thu, 21 Sep 2000 23:55:58 -0700 Message-Id: <20000922070129.2351937B423@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ideally, I would use one of the IDE flash-based drives on the market. One > brand is SanDisk, and they take a standard IDE connector and fit into a > 3.5" drive bay. You can get them very reasonably priced up to 128MB or > so, which is just fine for a boot partition. Since flash drives have no > moving parts, mechanical failure is not an issue, and since the root > partition is not written to much, the flash will not wear out for a > long time (flash cells wear out after about 100,000 writes; the flash > drives do load balancing and stuff to ensure that the (many) cells in > the drive are written to evenly). I would suggest just not writing them at all if you can avoid it. They seem to need (and are spec'd for) about 500ms of power after a write which isn't feasible with some power-off situations. I've had them occasionally behave worse and develop "bad" sectors under what i thought to be normal operating conditions (meaning, I thought I satisfied the above limitation). The bright side is that reclaiming "bad" sectors is just rewriting them, but if that's in the middle of something useful, like an inode for something in /lib, your superblock, the data portion of /etc/passwd, etc., you're in uncomfortable shape. I would definitely advocate (and actively use them for) completely readonly disks, either by running completely readonly straight from the SanDisk or by keeping a (compressed?) readonly filesystem on the disk, booting readonly into a bootstrap environment, and copying or expanding a read/write root disk into a memory-based disk device (MD, MFS), and calling that your / partition. it's admittedly a rather klunky solution for a general purpose install. It also makes putting /etc on non-volatile media difficult, but it is still workable with a bit of ingenuity, or maybe by using a small bootstrap /etc which is remounted with a stable vinum partition (I haven't actually tried this; implementation is left as an exercise for the reader). Another consideration is that they have slow write performance relative to typical IDE or (especially) memory-based media. - joel > > Doug > > On Thu, Sep 21, 2000 at 03:29:17PM -0700, Keith Kemp wrote: > > On the topic of Vinum, what do you guys do about the / partion since it > > appears that a vinum partion can not be the boot partion. > > > > I would hate to have the drive with my boot partion fail and be left with a > > non working server. > > > > Keith Kemp > > > > > -----Original Message----- > > > From: owner-freebsd-isp@FreeBSD.ORG > > > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Alfred Perlstein > > > Sent: Wednesday, September 20, 2000 12:51 PM > > > To: Edward Elhauge > > > Cc: freebsd-hackers@FreeBSD.ORG; freebsd-isp@FreeBSD.ORG > > > Subject: Re: Frustration with SCSI system > > > > > > > > > * Edward Elhauge [000920 12:48] wrote: > > > > Hello Freebsders, > > > > > > > > I've been using FreeBSD over the last 6 years (since I switched from > > > > NetBSD) to run a small ISP out of my basement. > > > > > > > > I've had about six disk crashes in as many years and still > > > don't know how > > > > to work reliably with them. > > > > > > "man vinum" > > > > > > software mirroring == good. > > > > > > :) > > > > > > -Alfred > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-isp" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 5:30: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 92F3937B423; Fri, 22 Sep 2000 05:30:06 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id FAA89008; Fri, 22 Sep 2000 05:30:06 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 22 Sep 2000 05:30:06 -0700 (PDT) From: Kris Kennaway To: Christian Kuhtz Cc: "Koster, K.J." , "'FreeBSD Hackers mailing list'" Subject: Re: Executable packages (long, sorry) In-Reply-To: <20000921102204.D6714@ns1.arch.bellsouth.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Sep 2000, Christian Kuhtz wrote: > Seems one might just as well investigate the SUN pkgadd format and see whether > such mechanism fits the bill... > > Ideally, the pkg also kows how to back itself out if it can't successfully > install. (although doing so should be an option, not the default). Guys, random chatter about what features it would be nice to have in a packaging format doesnt really lead anywhere. If you're going to commit to actually working on the next-generation package system then there are resources you should work with, otherwise it's just wasting bits. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 7: 9: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sm3.texas.rr.com (sm3.texas.rr.com [24.93.35.210]) by hub.freebsd.org (Postfix) with ESMTP id 3A18E37B424 for ; Fri, 22 Sep 2000 07:09:04 -0700 (PDT) Received: from bleep.craftncomp.com (cs2777-164.houston.rr.com [24.27.77.164]) by sm3.texas.rr.com (8.10.1/8.10.1) with ESMTP id e8M1RUm15131 for ; Thu, 21 Sep 2000 20:27:31 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8ME8nG00966 for ; Fri, 22 Sep 2000 09:08:49 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1] (may be forged)) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8ME8wG06483 for ; Fri, 22 Sep 2000 09:08:58 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009221408.e8ME8wG06483@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Converting Sun Automounter maps Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Sep 2000 09:08:58 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've stumbling into the wonderful world of auto-mounting, and trying to convert some maps from a Sun box to the FreeBSD format. I have amd.conf set up OK as per the man page, but keep on getting errors when changing into the relevant directorys (like amd can't find an appropriate match). Has anyone been down this path? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 7:24: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id A496737B422 for ; Fri, 22 Sep 2000 07:24:04 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e8MENeO39835; Fri, 22 Sep 2000 16:23:40 +0200 (CEST) (envelope-from adrian) Date: Fri, 22 Sep 2000 16:23:37 +0200 From: Adrian Chadd To: Douglas Swarin Cc: freebsd-hackers@FreeBSD.ORG, kkemp@nwcr.net Subject: Re: Frustration with SCSI system Message-ID: <20000922162336.A18474@roaming.cacheboy.net> References: <20000920125128.F9141@fw.wintelcom.net> <20000921182405.A82919@staff.texas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000921182405.A82919@staff.texas.net>; from doug@staff.texas.net on Thu, Sep 21, 2000 at 06:24:05PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 21, 2000, Douglas Swarin wrote: > Ideally, I would use one of the IDE flash-based drives on the market. One > brand is SanDisk, and they take a standard IDE connector and fit into a > 3.5" drive bay. You can get them very reasonably priced up to 128MB or > so, which is just fine for a boot partition. Since flash drives have no > moving parts, mechanical failure is not an issue, and since the root > partition is not written to much, the flash will not wear out for a > long time (flash cells wear out after about 100,000 writes; the flash > drives do load balancing and stuff to ensure that the (many) cells in > the drive are written to evenly). The neater magic will come out later when the only thing that needs to be machine-boot-readable is /boot, and your / can be vinum. Then all you need to have "hotswap" is your kernel+loader, which you could possibly get away even on a floppy disk. Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 7:52: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9438F37B423 for ; Fri, 22 Sep 2000 07:52:00 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA26859; Fri, 22 Sep 2000 10:53:04 -0400 (EDT) Message-Id: <200009221453.KAA26859@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 22 Sep 2000 10:50:52 -0400 To: Len Conrad , Wes Peters From: Dennis Subject: Re: low-cost/low-speed HDLC WAN card Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <5.0.0.25.0.20000922081407.02ed6370@mail.Go2France.com> References: <39CA90BF.8DEC13D0@softweyr.com> <5.0.0.25.0.20000921123747.05ec3600@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:27 AM 09/22/2000 +0200, Len Conrad wrote: > >> > I'm back again looking for a low-cost, 128 kbits/sec WAN card, even >> > ISA, single-port with HDLC V.35/X.21/V.11/EIA530. I need this to >> > drive leased-line links in France. >> > >> > etinc.com's got a 10-year-old model 5025 ISA card but it's $475 and 2 >> > megabits. We use two now in our ISP and it works fine, but to use >> > FreeBSD in a big nationwide VPN/IPsec project, we need to keep >> the price down. >> > >> > We can buy a Zyxel 153X WAN router for about that price, but it >> > doesn't do VPN nor more than one ethernet i/f nor does it's >> > non-loggable, limited packet filtering come anywhere near ipfilter. >> >>This may sound heretical, but have you considered using the router AND a >>FreeBSD firewall? > >Yes, of course, this is precisely our approach for the ISDN local >loop, with the sweet little Zyxel 128 ISDN router/bridge as our >"ISDN-to-Ethernet" bridge (no ip in Zyxel), since we think Zyxel ISDN >functions are well ahead/proven vs what we can accomplish with the >ISDN card/drivers for FreeBSD. > >Dennis/etinc is calling me silly for not asking for a discount on his >cards, so I'll see how low he can go. But we've realized that the 1U >and 2U boxes have PCI risers, not ISA risers. PCI cards are cheaper in volume than ISA cards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 8:27:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id B214937B423 for ; Fri, 22 Sep 2000 08:27:29 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA18214; Fri, 22 Sep 2000 11:27:02 -0400 (EDT) Date: Fri, 22 Sep 2000 11:27:02 -0400 (EDT) From: Daniel Eischen To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: Converting Sun Automounter maps In-Reply-To: <200009221408.e8ME8wG06483@bloop.craftncomp.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, 22 Sep 2000, Stephen Hocking wrote: > I've stumbling into the wonderful world of auto-mounting, and trying to > convert some maps from a Sun box to the FreeBSD format. I have amd.conf set up > OK as per the man page, but keep on getting errors when changing into the > relevant directorys (like amd can't find an appropriate match). Has anyone > been down this path? Somewhat related to this... I've tried to get FreeBSD to behave with Sun automount home directories. When all the (Sun) home directories are on one system, I could get by by exporting the home directory on the Sun and automounting this as /home on the FreeBSD box. But we're now expanding so that home directories will exist on 2 different Sun boxen, and this will no longer work. I've resorted to disable automounting of users home directories on the Suns (where /home/ could be automounted to any Sun box/filesystem) and am now auotmounting /home/ instead. So home directories are /home/box1/user23 or /home/box2/user134. FreeBSD can now deal with this by automounting box1 and box2 under /home. amd-utils doesn't seem to support the autofs mapping needed to allow FreeBSD to exist in such an environment where each users home directory is automounted. I remember searching the newsgroups regarding this issue, and there did seem to be some initial support for autofs though. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 9:24:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mb1i0.ns.pitt.edu (mb1i0.ns.pitt.edu [136.142.186.35]) by hub.freebsd.org (Postfix) with ESMTP id 9BBE837B424 for ; Fri, 22 Sep 2000 09:24:51 -0700 (PDT) Received: from bioe-design-1.bioe.pitt.edu ("port 1912"@[136.142.178.184]) by pitt.edu (PMDF V5.2-32 #41462) with ESMTP id <01JUH250X1Z0000Z8U@mb1i0.ns.pitt.edu> for freebsd-hackers@FreeBSD.ORG; Fri, 22 Sep 2000 12:24:50 EST Date: Fri, 22 Sep 2000 12:24:10 -0400 From: "Pedro F. Giffuni" Subject: Re: Executable packages (long, sorry) In-reply-to: Originator-info: login-id=pfg1; server=imap.pitt.edu To: 'FreeBSD Hackers mailing list' Message-id: <3257808680.969625450@bioe-design-1.bioe.pitt.edu> MIME-version: 1.0 X-Mailer: Mulberry (Win32) [1.4.4, s/n S-398070] Content-type: text/plain; charset=us-ascii Content-disposition: inline Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... While I will not be contributing to this project, I wanted to remember everyone that the source code for UnixWare's packaging utility is available in Skunkware. FWIW, he Unixware stuff is very similar to Jordan's packaging utilities, in fact it has the same limitations. One thing I did like about the Unixware way of doing things was that when you install a package the Motif tool would launch and individual xterm with a report of the installation. cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 9:45: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f262.law9.hotmail.com [64.4.8.137]) by hub.freebsd.org (Postfix) with ESMTP id 1A42A37B424 for ; Fri, 22 Sep 2000 09:44:56 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 22 Sep 2000 09:44:55 -0700 Received: from 194.65.14.68 by lw9fd.law9.hotmail.msn.com with HTTP; Fri, 22 Sep 2000 16:44:55 GMT X-Originating-IP: [194.65.14.68] From: "John Lispton" To: freebsd-hackers@freebsd.org Subject: [book] how "compatible" are FreeBSD and "Advanced Programming in the UNIX ..."? Date: Fri, 22 Sep 2000 22:14:55 IST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 22 Sep 2000 16:44:55.0834 (UTC) FILETIME=[70031FA0:01C024B4] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am a fair C programmer, and would like to start developing under FreeBSD; would you consider the classic «Advanced Programming in the UNIX Environment», by W. Richard Stevens to be a good choice for a programming book? Does current FreeBSD programming differ much from the "generic" UNIX programming described in the book? Or can I rest assured that the book contents apply well to FreeBSD? TIA J Lispton _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 10:44: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neutron.cichlids.com (p3E9C110C.dip.t-dialin.net [62.156.17.12]) by hub.freebsd.org (Postfix) with ESMTP id 1FF0237B424 for ; Fri, 22 Sep 2000 10:44:01 -0700 (PDT) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 4FF1CAB91; Fri, 22 Sep 2000 19:44:21 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id E774114A69; Fri, 22 Sep 2000 19:44:06 +0200 (CEST) Date: Fri, 22 Sep 2000 19:44:06 +0200 To: John Lispton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [book] how "compatible" are FreeBSD and "Advanced Programming in the UNIX ..."? Message-ID: <20000922194406.B18550@cichlids.cichlids.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jlispton@hotmail.com on Fri, Sep 22, 2000 at 10:14:55PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake John Lispton (jlispton@hotmail.com): > programming described in the book? Or can I rest assured that the book > contents apply well to FreeBSD? Yes, the book explains everything on 4.3BSD, so everything applies to FreeBSD as well. Of course, FreeBSD (and the other BSD's, too) have had some improvements on various points in the meanwhile. However, since Stevens covers most things related to the Posix and other standards, you can expect everything in the book to work. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 11:50:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bonsai.nougat.org (189.193.6.64.reflexcom.com [64.6.193.189]) by hub.freebsd.org (Postfix) with ESMTP id 93E8937B422 for ; Fri, 22 Sep 2000 11:50:47 -0700 (PDT) Received: by bonsai.nougat.org (Postfix, from userid 1001) id 3538F6CB1; Fri, 22 Sep 2000 11:50:44 -0700 (PDT) Date: Fri, 22 Sep 2000 11:50:44 -0700 From: Travis Cole To: Stephen Hocking Cc: hackers@freebsd.org Subject: Re: Converting Sun Automounter maps Message-ID: <20000922115044.A2432@bonsai.nougat.org> References: <200009221408.e8ME8wG06483@bloop.craftncomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us In-Reply-To: <200009221408.e8ME8wG06483@bloop.craftncomp.com>; from shocking@houston.rr.com on Fri, Sep 22, 2000 at 09:08:58AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am-utils http://www.cs.columbia.edu/~ezk/am-utils/ comes with a nice perl script called automount2amd that does a fine job of converting sun automount maps to amd maps. At work we have Solaris, Linux, and FreeBSD all hapily automounting and talking nis. I did have to hack automount2amd so FreeBSD defaults to nfsv2 otherwise Linux freaks (I'm guessing it thinks it can talk nfsv3, but then when it tries things don't work out). On Fri, Sep 22, 2000 at 09:08:58AM -0500, Stephen Hocking wrote: > I've stumbling into the wonderful world of auto-mounting, and trying to > convert some maps from a Sun box to the FreeBSD format. I have amd.conf set up > OK as per the man page, but keep on getting errors when changing into the > relevant directorys (like amd can't find an appropriate match). Has anyone > been down this path? > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- --tcole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 12: 0:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sword.cisco.com (sword.cisco.com [161.44.208.100]) by hub.freebsd.org (Postfix) with ESMTP id 0034337B42C for ; Fri, 22 Sep 2000 12:00:31 -0700 (PDT) Received: from sjt-u10.cisco.com (sjt-u10.cisco.com [161.44.208.184]) by sword.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA16248; Fri, 22 Sep 2000 14:58:54 -0400 (EDT) From: Steve Tremblett Received: (sjt@localhost) by sjt-u10.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) id PAA24818; Fri, 22 Sep 2000 15:00:45 -0400 (EDT) Message-Id: <200009221900.PAA24818@sjt-u10.cisco.com> Subject: Re: [book] how "compatible" are FreeBSD and "Advanced Programming in the UNIX ..."? To: jlispton@hotmail.com (John Lispton) Date: Fri, 22 Sep 2000 15:00:45 -0400 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "John Lispton" at Sep 22, 2000 10:14:55 PM X-Mailer: ELM [version 2.5 PL1] 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 That book is actually quite BSD-specific - it would be a wonderful choice. The FreeBSD installation contains a package of the libraries from that book! Good luck! +--- John Lispton wrote: | | Hi | | I am a fair C programmer, and would like to start developing under FreeBSD; | would you consider the classic «Advanced Programming in the UNIX | Environment», by W. Richard Stevens to be a good choice for a programming | book? Does current FreeBSD programming differ much from the "generic" UNIX | programming described in the book? Or can I rest assured that the book | contents apply well to FreeBSD? | -- Steve Tremblett Cisco Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 12: 7:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id B4EA437B422 for ; Fri, 22 Sep 2000 12:07:45 -0700 (PDT) Received: from plapla.palnet.com (mustafa.palnet.com [192.116.17.10]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id VAA41673 for ; Fri, 22 Sep 2000 21:11:22 +0200 (IST) Message-Id: <5.0.0.25.0.20000922220450.00a31790@mail.palnet.com> X-Sender: mustafa@mail.palnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 22 Sep 2000 22:05:53 +0200 To: freebsd-hackers@freebsd.org From: "Mustafa N. Deeb" Subject: Monitoring user activity Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi , I'm look for a way to monitor what happens on my servers I need to know each command being executed? is there away to do that . cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 12:55:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 6EE3437B422 for ; Fri, 22 Sep 2000 12:55:46 -0700 (PDT) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA82294; Fri, 22 Sep 2000 14:55:39 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 22 Sep 2000 14:55:39 -0500 (CDT) From: David Scheidt To: "Mustafa N. Deeb" Cc: freebsd-hackers@freebsd.org Subject: Re: Monitoring user activity In-Reply-To: <5.0.0.25.0.20000922220450.00a31790@mail.palnet.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, 22 Sep 2000, Mustafa N. Deeb wrote: :hi , : :I'm look for a way to monitor what happens on my servers :I need to know each command being executed? : :is there away to do that . System accounting should do most of what you want. See accton(8), sa(8), lastcomm(1) to start with. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 13:35:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from theartofwar.org (adslppp17.tcsn.uswest.net [216.161.144.17]) by hub.freebsd.org (Postfix) with SMTP id 79EC337B422 for ; Fri, 22 Sep 2000 13:35:46 -0700 (PDT) Received: (qmail 28050 invoked by uid 1001); 22 Sep 2000 20:35:45 -0000 Date: Fri, 22 Sep 2000 13:35:45 -0700 From: Hartoyo Cc: freebsd-hackers@freebsd.org Subject: Re: [book] how "compatible" are FreeBSD and "Advanced Programming in the UNIX ..."? Message-ID: <20000922133545.B1033@theartofwar.org> References: <200009221900.PAA24818@sjt-u10.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009221900.PAA24818@sjt-u10.cisco.com>; from sjt@cisco.com on Fri, Sep 22, 2000 at 03:00:45PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 22, 2000 at 03:00:45PM -0400, Steve Tremblett wrote: > > That book is actually quite BSD-specific - it would be a wonderful > choice. The FreeBSD installation contains a package of the libraries > from that book! > Just wandering if anyone has another recommendation about BSD programming? Linux got tons of them (introduction to linux programming). I have been reading O'Rielly Unix System Programming for SVR4 (pretty good book, and explain about BSD specific feature as well) and wondering if there is BSD specific book about system programming... who knows, I might be able to contribute some codes to FreeBSD in the future! =P Thank you... =) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 15:17:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id DE1F437B423 for ; Fri, 22 Sep 2000 15:17:50 -0700 (PDT) Received: (qmail 15326 invoked by uid 1001); 22 Sep 2000 22:17:53 -0000 Date: Sat, 23 Sep 2000 01:17:53 +0300 From: Peter Pentchev To: freebsd-hackers@freebsd.org Subject: virtual console 'snapshot'? Message-ID: <20000923011753.A15311@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anything like Linux's /dev/vcs* in FreeBSD? That is, some way to obtain the complete view of a virtual console - characters, attributes, everything? The snoop device gives deltas, but never the complete picture, unless the program running on that console decides to redraw the whole thing. G'luck, Peter -- I am jealous of the first word in this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 15:57:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5]) by hub.freebsd.org (Postfix) with ESMTP id 1557E37B440 for ; Fri, 22 Sep 2000 15:57:47 -0700 (PDT) Received: from [206.246.249.98] (helo=escape) by wilma.widomaker.com with esmtp (Exim 3.16 #2) id 13cblF-0005Cv-00 for freebsd-hackers@freebsd.org; Fri, 22 Sep 2000 18:57:41 -0400 Received: from shannon by escape with local (Exim 3.12 #1 (Debian)) id 13cblA-0001au-00 for ; Fri, 22 Sep 2000 18:57:36 -0400 Date: Fri, 22 Sep 2000 18:57:36 -0400 From: Shannon Hendrix To: freebsd-hackers@freebsd.org Subject: SCSI tape speed Message-ID: <20000922185736.C5978@widomaker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm interested in hearing from anyone who uses DAT drives on a DPT SCSI controller, preferrably with FreeBSD 4.1 and an Intel system. I find the speed is very slow, and I know in the past these drives were fine with FreeBSD, though I can't remember which release now. With my most recent install of FreeBSD 4.1, I am lucky to get 3MB/minute on a drive and controller combination that I know can hit 45MB/min. Right now, with NetBSD on an old Sparc 5, they still get 20MB/min or better. No errors, even large restores are perfect, but take many hours to finish. The controller I have is a DPT-2044W, and it currently has the ROM version DPT suggested for use with tape drives. The drives in question are an Archive Python 4-tape robot and a Seagate Scorpion. Both are DDS2 drives. No load on the DPT except for tapes and a CD-ROM burner. I haven't been able to find much information on this particular setup, and most tape woes seem error related, or related to another platform. -- "Those who trade liberty for security will have neither -- | | | (??)" | | | ________________________________________________________________ / | \ s h a n n o n @ w i d o m a k e r . c o m _/ | \_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 16: 0:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CE8D037B422 for ; Fri, 22 Sep 2000 16:00:32 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA14666; Fri, 22 Sep 2000 16:00:20 -0700 Date: Fri, 22 Sep 2000 16:00:14 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Shannon Hendrix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI tape speed In-Reply-To: <20000922185736.C5978@widomaker.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 How about some more details? I'm beginning to wonder if buffered mode got broken. I do know I just did some tests with a DDS3 drive and I consistently got 1MB/s or better on dumps. On Fri, 22 Sep 2000, Shannon Hendrix wrote: > > > I'm interested in hearing from anyone who uses DAT drives on a DPT SCSI > controller, preferrably with FreeBSD 4.1 and an Intel system. > > I find the speed is very slow, and I know in the past these drives were fine > with FreeBSD, though I can't remember which release now. With my most recent > install of FreeBSD 4.1, I am lucky to get 3MB/minute on a drive and controller > combination that I know can hit 45MB/min. > > Right now, with NetBSD on an old Sparc 5, they still get 20MB/min or better. > > No errors, even large restores are perfect, but take many hours to finish. > > The controller I have is a DPT-2044W, and it currently has the ROM version DPT > suggested for use with tape drives. The drives in question are an Archive > Python 4-tape robot and a Seagate Scorpion. Both are DDS2 drives. > > No load on the DPT except for tapes and a CD-ROM burner. > > I haven't been able to find much information on this particular setup, and > most tape woes seem error related, or related to another platform. > > > -- > "Those who trade liberty for security will have neither -- | | | > (??)" | | | > ________________________________________________________________ / | \ > s h a n n o n @ w i d o m a k e r . c o m _/ | \_ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 18:14:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 0A6E137B422 for ; Fri, 22 Sep 2000 18:14:40 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id FAA09700; Sat, 23 Sep 2000 05:14:30 +0400 (MSD) Message-Id: <200009230114.FAA09700@aaz.links.ru> Subject: Re: SCSI tape speed In-Reply-To: <20000922185736.C5978@widomaker.com> from "Shannon Hendrix" at "Sep 22, 0 06:57:36 pm" To: shannon@widomaker.com (Shannon Hendrix) Date: Sat, 23 Sep 2000 05:14:30 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shannon Hendrix writes: > I'm interested in hearing from anyone who uses DAT drives on a DPT SCSI > controller, preferrably with FreeBSD 4.1 and an Intel system. > > I find the speed is very slow, and I know in the past these drives were fine > with FreeBSD, though I can't remember which release now. With my most recent > install of FreeBSD 4.1, I am lucky to get 3MB/minute on a drive and controller > combination that I know can hit 45MB/min. > > Right now, with NetBSD on an old Sparc 5, they still get 20MB/min or better. > > No errors, even large restores are perfect, but take many hours to finish. > > The controller I have is a DPT-2044W, and it currently has the ROM version DPT > suggested for use with tape drives. The drives in question are an Archive > Python 4-tape robot and a Seagate Scorpion. Both are DDS2 drives. I have DDS4 Seagate (IBM) streamer. When I do 'dump something > /dev/sa0' then write is by 1K blocks. The read spead of such a tape is very slow; 'dd if=/dev/sa0 of=/dev/null bs=something' is about 200 Kbyte/sec Just do 'dump something | buffer -s 64K > /dev/sa0' and read from such tape is normal (more than 2 Mbyte/sec, depends on compression) > No load on the DPT except for tapes and a CD-ROM burner. I have 2940UW with lot of devises - I think that low read speed with little blocks is not controller dependant. > I haven't been able to find much information on this particular setup, and > most tape woes seem error related, or related to another platform. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 18:18:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f294.law9.hotmail.com [64.4.8.169]) by hub.freebsd.org (Postfix) with ESMTP id 1131C37B424 for ; Fri, 22 Sep 2000 18:18:35 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 22 Sep 2000 18:18:34 -0700 Received: from 194.65.14.68 by lw9fd.law9.hotmail.msn.com with HTTP; Sat, 23 Sep 2000 01:18:34 GMT X-Originating-IP: [194.65.14.68] From: "John Lispton" To: freebsd-hackers@freebsd.org Subject: RE: [book] how "compatible" are FreeBSD and "Advanced Programming in the UNIX ..."? Date: Sat, 23 Sep 2000 06:48:34 IST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Sep 2000 01:18:34.0892 (UTC) FILETIME=[319A2CC0:01C024FC] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Thank you for all the helpful replies. Tomorrow I'll go shopping. :) Cheers, J Lispton _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 22 23:26: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 1006337B43E for ; Fri, 22 Sep 2000 23:25:50 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13ci4j-0000Sb-00; Fri, 22 Sep 2000 23:42:13 -0600 Message-ID: <39CC42B5.42FB21FD@softweyr.com> Date: Fri, 22 Sep 2000 23:42:13 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Douglas Swarin , freebsd-hackers@FreeBSD.ORG, kkemp@nwcr.net Subject: Re: Frustration with SCSI system References: <20000921182405.A82919@staff.texas.net> <20000920125128.F9141@fw.wintelcom.net> <200009212344.RAA63251@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <20000921182405.A82919@staff.texas.net> Douglas Swarin writes: > : Ideally, I would use one of the IDE flash-based drives on the market. One > : brand is SanDisk, and they take a standard IDE connector and fit into a > : 3.5" drive bay. You can get them very reasonably priced up to 128MB or > : so, which is just fine for a boot partition. Since flash drives have no > : moving parts, mechanical failure is not an issue, and since the root > : partition is not written to much, the flash will not wear out for a > : long time (flash cells wear out after about 100,000 writes; the flash > : drives do load balancing and stuff to ensure that the (many) cells in > : the drive are written to evenly). > > We use these devices heavily at Timing Solutions. Or rather we use > a IDE <-> CF adapter and haven't had any devices wear out. And some > of these devices have had rather heavy use. I think that it is closer > to 1 million writes per cell, but I don't have my spec sheets handy. The newer devices do 1 million writes per cell. When I left Xylan earlier this year, some of our early (late '94 or early '95) flash devices were just beginning to fail. These were development machines that saw a lot of write cycles, and their home-grown flash filesystem does a pessimal job of rewriting the same cells over and over again. > Are you sure that they do write balancing? The indications I have > from the base chip technology is that they don't. I could have missed > that in the data sheets. It has been a little while since I looked at > them, so I might be misremembering. I can't seem to find the data > sheets I looked at before. SanDisk does, in the controller chip. Good technology. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 2:29: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 96B4437B424 for ; Sat, 23 Sep 2000 02:28:59 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA07272; Sat, 23 Sep 2000 16:27:48 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Sat, 23 Sep 2000 16:27:47 +0700 (NSS) From: Max Khon To: Daniel Eischen Cc: Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: Converting Sun Automounter maps In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 22 Sep 2000, Daniel Eischen wrote: > On Fri, 22 Sep 2000, Stephen Hocking wrote: > > I've stumbling into the wonderful world of auto-mounting, and trying to > > convert some maps from a Sun box to the FreeBSD format. I have amd.conf set up > > OK as per the man page, but keep on getting errors when changing into the > > relevant directorys (like amd can't find an appropriate match). Has anyone > > been down this path? > > Somewhat related to this... > > I've tried to get FreeBSD to behave with Sun automount home directories. > When all the (Sun) home directories are on one system, I could get > by by exporting the home directory on the Sun and automounting this > as /home on the FreeBSD box. But we're now expanding so that home > directories will exist on 2 different Sun boxen, and this will no > longer work. I've resorted to disable automounting of users home > directories on the Suns (where /home/ could be automounted to > any Sun box/filesystem) and am now auotmounting /home/ > instead. So home directories are /home/box1/user23 or /home/box2/user134. > FreeBSD can now deal with this by automounting box1 and box2 under /home. > > amd-utils doesn't seem to support the autofs mapping needed to > allow FreeBSD to exist in such an environment where each users home > directory is automounted. I remember searching the newsgroups > regarding this issue, and there did seem to be some initial support > for autofs though. we do automounting user homes this way: --- cut here (amd.home amd map) --- /defaults type:=nfs;opts:=rw,vers=3,proto=tcp,intr,soft,nodevs,nosuid,rsize=8192,wsize=8192; # # master users ros host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} oleg host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} nik host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} [...] sol host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} ilnar host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} eug host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} paul host==master;type:=link;fs:=/usr/home/${key} || rhost:=master;rfs:=/usr/home;sublink:=${key} # # biboca users al host==biboca;type:=link;fs:=/usr/home/${key} || rhost:=biboca;rfs:=/usr;sublink:=home/${key} # # lark users fjoe host==lark;type:=link;fs:=/usr/home/${key} || rhost:=lark;rfs:=/usr;sublink:=home/${key} # # tiamat users osya host==tiamat;type:=link;fs:=/usr/home/${key} || rhost:=tiamat;rfs:=/usr;sublink:=home/${key} # # lizard users cs host==lizard;type:=link;fs:=/usr/home/${key} || rhost:=lizard;rfs:=/usr;sublink:=home/${key} # # xaa users xaa host==xaa;type:=link;fs:=/usr/home/${key} || rhost:=xaa;rfs:=/usr;sublink:=home/${key} # # drugon users als host==drugon;type:=link;fs:=/usr/home/${key} || rhost:=drugon;rfs:=/usr;sublink:=home/${key} blay host==drugon;type:=link;fs:=/usr/home/${key} || rhost:=drugon;rfs:=/usr/home;sublink:=${key} plesk host==drugon;type:=link;fs:=/usr/home/${key} || rhost:=drugon;rfs:=/usr;sublink:=home/${key} --- cut here --- /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 8:22:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CC7D737B422 for ; Sat, 23 Sep 2000 08:22:28 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA16252; Sat, 23 Sep 2000 09:22:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA06153; Sat, 23 Sep 2000 09:22:21 -0600 (MDT) Message-Id: <200009231522.JAA06153@harmony.village.org> To: Wes Peters Subject: Re: Frustration with SCSI system Cc: Douglas Swarin , freebsd-hackers@FreeBSD.ORG, kkemp@nwcr.net In-reply-to: Your message of "Fri, 22 Sep 2000 23:42:13 MDT." <39CC42B5.42FB21FD@softweyr.com> References: <39CC42B5.42FB21FD@softweyr.com> <20000921182405.A82919@staff.texas.net> <20000920125128.F9141@fw.wintelcom.net> <200009212344.RAA63251@harmony.village.org> Date: Sat, 23 Sep 2000 09:22:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39CC42B5.42FB21FD@softweyr.com> Wes Peters writes: : SanDisk does, in the controller chip. Good technology. Ah. that explains why I didn't see it in the datasheets on the cell chips... That, or I'm starting to come down with CRS :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 10:29:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id BBABB37B424 for ; Sat, 23 Sep 2000 10:29:14 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id 5982FDC74; Sat, 23 Sep 2000 13:24:07 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 4CF76DC73 for ; Sat, 23 Sep 2000 13:24:07 -0400 (EDT) Date: Sat, 23 Sep 2000 13:24:07 -0400 (EDT) From: David Miller To: freebsd-hackers@freebsd.org Subject: Limits of TCP 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 Hi All:) I'm looking at building an eight or twelve port fast ethernet router, and I got to wondering how well a FreeBSD box could handle that much traffic. Assume, for the moment, that hardware is not an issue. Assume that I have a gigahertz processor, 4 way interleaved memory, 4 separate fast/wide PCI busses. (Thanks to the guys on -hardware for helping me locate it) I tried ping -f localhost on an 800 MHz athlon, and netstat -w 1 -I lo0 indicated about 80,000 pps. The system was 100% busy doing this, about 85% system usage. I'm thinking this is probably spent largely switching in and out of kernel mode to a) have ping send the packet and b) respond to it. If this is correct, the number of packets it could handle while staying within kernel mode would be considerably larger. Or I could be sniffing glue and the cost of copying packets in and out would exceed that of context switching. How many packets per second could I expect to get under ideal circumstances? Thanks in advance:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 11:24:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6C20B37B424 for ; Sat, 23 Sep 2000 11:24:10 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA16897; Sat, 23 Sep 2000 12:24:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA06904; Sat, 23 Sep 2000 12:24:08 -0600 (MDT) Message-Id: <200009231824.MAA06904@harmony.village.org> To: David Miller Subject: Re: Limits of TCP in FreeBSD kernel? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 23 Sep 2000 13:24:07 EDT." References: Date: Sat, 23 Sep 2000 12:24:08 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message David Miller writes: : I tried ping -f localhost on an 800 MHz athlon, and netstat -w 1 -I lo0 ping -f doesn't use TCP at all. : indicated about 80,000 pps. The system was 100% busy doing this, about : 85% system usage. Sounds about right. You asked ping to do as much work as it can and it is doing it. : I'm thinking this is probably spent largely switching : in and out of kernel mode to a) have ping send the packet and b) respond : to it. If this is correct, the number of packets it could handle while : staying within kernel mode would be considerably larger. Or I could be : sniffing glue and the cost of copying packets in and out would exceed that : of context switching. The number of packets is limited by the bandwidth of the pipe coming into the machine, even for gigabit ethernet. Also, larger packets generally do better than smaller ones due to decreated interrupt overhead. ping -f isn't a good measure of throughput because it uses ICMP packets and isn't coded for maximum speed. ftp may be a better way to estimate this, but you may need have a really large file in order to get good measurements. Since you are doing 5MB/s with ping's 64 byte packets, you should likely get 50-100MB/s with TCP/IP and ftp, plus or minus. Make sure that the file you pick is in the buffer cache so that you don't take the hit of reading it into RAM. Also, you might want to consider using the ttcp testing program to get numbers. Since you are using the loopback device, you don't need to worry about a quality ethernet card, but might if you want to go external to the box. : How many packets per second could I expect to get under ideal : circumstances? 80,000 pps is a 5MB/s or 41Mb/s. For a TCP streaming connection, you can expect much higher data rates. 100Mb/s ethernet easily can be saturated, while 1Gb/s ethernet can be saturated with a few tweaks and using jumbo-frames. Zero copy operations are important for gigabit ethernet because the data rates are so high. Ken Merry and others have done some work in this area. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 12:55: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id D98C037B422 for ; Sat, 23 Sep 2000 12:54:57 -0700 (PDT) Received: from plapla.palnet.com (mustafa.palnet.com [192.116.17.10]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id VAA56969 for ; Sat, 23 Sep 2000 21:58:42 +0200 (IST) Message-Id: <5.0.0.25.0.20000923225141.009f9dc0@mail.palnet.com> X-Sender: mustafa@mail.palnet.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 23 Sep 2000 22:52:59 +0200 To: freebsd-hackers@freebsd.org From: "Mustafa N. Deeb" Subject: Denying ISDN using Radius Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I don't know if someone did this before, I want to deny ISDN connections to my PRI's, unless the user is in the ISDN group. can I make radius allow/deny ISDN based on GID cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 15:19: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.icsfm.com (ns1.icsfm.com [206.117.178.120]) by hub.freebsd.org (Postfix) with ESMTP id EE77C37B422 for ; Sat, 23 Sep 2000 15:19:00 -0700 (PDT) Received: from jossee (dlci57-1.icsfm.com [207.151.141.57]) by ns1.icsfm.com (8.9.2/8.9.2) with SMTP id PAA84163 for ; Sat, 23 Sep 2000 15:32:22 -0700 (PDT) (envelope-from steveb99@earthlink.net) From: "steveb99" To: Subject: FreeBSD, BSDi differences Date: Sat, 23 Sep 2000 15:23:53 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-reply-to: <200009231824.MAA06904@harmony.village.org> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still new to FreeBSD and like it so far, but I'm thinking of ways I can use it at work. I hear about BSDi and that it is used in many network appliances like f5's BigIP load balancers and other similar products. What I've read BSDi is used because of it excellent TCP stack and other networking. So how different is FreeBSD TCP stack and networking from BSDi's? Steve B. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 15:22:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EBE7A37B422; Sat, 23 Sep 2000 15:22:45 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA71953; Sat, 23 Sep 2000 15:22:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 23 Sep 2000 15:22:45 -0700 (PDT) From: Kris Kennaway To: steveb99 Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD, BSDi differences In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Sep 2000, steveb99 wrote: > I'm still new to FreeBSD and like it so far, but I'm thinking of ways I can > use it at work. I hear about BSDi and that it is used in many network > appliances like f5's BigIP load balancers and other similar products. What > I've read BSDi is used because of it excellent TCP stack and other > networking. So how different is FreeBSD TCP stack and networking from > BSDi's? Very little. Both FreeBSD and BSDi are derived from the same code. There are no doubt a few differences, but based on what I've seen in other parts of the BSD/OS code I'd be surprised if theirs had received as much work as our network code has. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 17:51:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 22AA437B422 for ; Sat, 23 Sep 2000 17:51:18 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id UAA06048 for ; Sat, 23 Sep 2000 20:51:00 -0400 (EDT) Date: Sat, 23 Sep 2000 20:50:43 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: putting FreeBSD in an extended partition Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am wondering whether there is a good reason for not putting FreeBSD in a DOS extended partition. I have installed four O.S.es on my laptop and know that could be a limitation if FreeBSD can not be put into a DOS extended partition. I do not see any limitations in the boot loader or kernel that prevent this. Thanks for any enlightment. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 23 19:19: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop3.gte.net (smtppop3pub.gte.net [206.46.170.22]) by hub.freebsd.org (Postfix) with ESMTP id 5C4D137B424 for ; Sat, 23 Sep 2000 19:19:01 -0700 (PDT) Received: from c410342b (1Cust34.tnt6.san-jose.ca.da.uu.net [63.36.207.34]) by smtppop3.gte.net with SMTP for ; id VAA26738766 Sat, 23 Sep 2000 21:15:00 -0500 (CDT) Message-ID: <000001c025ce$76ba85c0$22cf243f@c410342b> Reply-To: "Soumen Biswas" From: "Soumen Biswas" To: Subject: Turning off KMEMSTATS in kern_malloc.h Date: Sat, 23 Sep 2000 19:20:50 -0700 Organization: Netscaler Inc. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C3_01C02593.6283D100" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00C3_01C02593.6283D100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello , What might be the side effects of undefining KMEMSTATS in=20 /usr/src/sys/kern/kern_malloc.h ( I am using FBSD 2.2.5 )=20 Regards=20 Soumen ------=_NextPart_000_00C3_01C02593.6283D100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello ,
 
What might be the side effects of undefining = KMEMSTATS in
/usr/src/sys/kern/kern_malloc.h  ( I am using = FBSD 2.2.5=20 )
 
Regards
Soumen
 
 
------=_NextPart_000_00C3_01C02593.6283D100-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message