From owner-freebsd-hackers Sun Jun 29 02:49:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA25685 for hackers-outgoing; Sun, 29 Jun 1997 02:49:24 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25680 for ; Sun, 29 Jun 1997 02:49:19 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA19003; Sun, 29 Jun 1997 19:19:01 +0930 (CST) From: Michael Smith Message-Id: <199706290949.TAA19003@genesis.atrad.adelaide.edu.au> Subject: Re: Disk built-in hw cache In-Reply-To: from Andrzej Bialecki at "Jun 27, 97 11:52:59 am" To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Sun, 29 Jun 1997 19:19:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andrzej Bialecki stands accused of saying: > > > I just read certain discussion on Linux list concerning > > > bad/missing/removed disk cache in "repaired" (and sold as new) hard disks. > > > Linux prints during probing the size of disk cache (at least that what the ... > > Uhh, this sounds pretty bogus. Do you have a reference to anything > > authoratative on the subject? > > No :-(. AFAIR from that discussion, IDE disks answer certain query by > returning the info stored somwhere on cyl 0. How this info relates to > reality is of course highly disputable (unless there are any specs on > this). How it gets updated if the chip gets bad/missing is similarly > vague. I think Bruce has sunk this one fairly categorically. > > size using a vendor-specific command, but the thought of "removing" > > the cache memory from a repaired disk is laughable. The PCBA on a > > modern disk is worth no more than a few dollars; the _only_ economical > > means for "reapairing" it would be to throw it away and replace it. > > Except when it is done by home-grown expert, and then sold as new or > a bargain. This is a joke, right? You rip the cache RAM (not what one would call an unreliable component, really) off the PCBA on the bottom of the drive, and expect the firmware and/or the bus interface controller to keep working? No, I don't think so. I'm inclined to go with Bruce on this one in that the Linuxers were panicking at nothing; it's possible the vendor decided that they didn't want the buffer size reported in one particular firmware revision, or that the buffer size was variable and thus couldn't be usefully reported, or something like that. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 29 02:58:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA26122 for hackers-outgoing; Sun, 29 Jun 1997 02:58:50 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA26108 for ; Sun, 29 Jun 1997 02:58:47 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA19062; Sun, 29 Jun 1997 19:28:13 +0930 (CST) From: Michael Smith Message-Id: <199706290958.TAA19062@genesis.atrad.adelaide.edu.au> Subject: Re: Tcl loadable packages In-Reply-To: from Narvi at "Jun 23, 97 01:30:47 pm" To: narvi@haldjas.folklore.ee (Narvi) Date: Sun, 29 Jun 1997 19:28:13 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG, hasty@rah.star-gate.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Narvi stands accused of saying: > > > > > > If one was to make a port of tcl loadable package, how would one > > > go about it? > > > > > > Well, I know I have to make a shared library. How am I to name it > > > - the original makefile, that does not work on FreeBSD tries to > > > just make a xxxx.so file. > > > > There are a couple of approaches. You can hack the Makefile to build > > shared libraries the BSD way, or you can write a replacement Makefile that > > uses bsd.lib.mk. Looking at the latter will at least make it clear how > > shared libraries are made, and let you name it appropriately. > > I find it easier to write a new Makefile. OK; have a look at how the tcl76 port achieves it. Basically it throws in another Makefile which contains the appropriate data for building the shared library. > > scripts, I'd suggest putting them in /usr/local/libdata/... > > Hm... I don't have libdata here... Is it an official directory? It's used in /usr for the Tcl stuff. > Or perhaps there should be a separate hierachie for installation and easy > finding of tcl packages? Perhaps. The Perl stuff (of which there is _lots_) uses lib/perl5/site_perl. Is this a Perl-ism, or something we should emulate for Tcl? It's less clear with so many Tcl versions to choose from 8( > I take it that there really should be a standard place to hold the "loader > files" for loadable (that is - in the form of shared libraries) tcl > packages - if a given packages exists, just call /usr/local/.../load_$pkg > and it gets loaded. It will avoid a lot of compatibilty problems and the > need to re-write the scripts every time we move to a newer tcl version and > newer versions of the packages. Hmm. lib/tcl/site_tcl// sounds pretty good to me. > Sander -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 29 03:14:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26595 for hackers-outgoing; Sun, 29 Jun 1997 03:14:01 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26590 for ; Sun, 29 Jun 1997 03:13:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA29898; Sun, 29 Jun 1997 20:05:50 +1000 Date: Sun, 29 Jun 1997 20:05:50 +1000 From: Bruce Evans Message-Id: <199706291005.UAA29898@godzilla.zeta.org.au> To: bde@zeta.org.au, Shimon@i-Connect.Net Subject: Re: Clists limited to 1024 bytes? Cc: bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Anyway, 19200 bps is not a heavy load unless there are a lot of active >> ports. With 32 active 16550 ports it would be fairly heavy, but still >> gives less than 6% of the throughput of a single 10Mb/s ethernet. > >I was thinking more (on a 16550) about what happens at 115,200, 230,400, >and more. These are speeds we see already today with ISDN lines. >The option of an external TA (such as a Motorola BitSRFR) is very apealing, >but behavior at these speeds needs careful consideration. > >How would you adjust the drivers to acomodate these speeds? 115200 was fast 10 years ago, but 230400 is currently not well support (if you change the hardware clock to get it, then then the buffer sizes are too small). How many ports do you need? >We experienced a lot of complex problems with SCSI transactions until we >bumped the sio interrupt bufferto double its size. While performance (on >the sio ports - we use them only for PPP) did not drop visibly, the strange >incidence of dropping biodone() calls virtually stopped. This probably just made a race less common. Bruce From owner-freebsd-hackers Sun Jun 29 03:14:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26660 for hackers-outgoing; Sun, 29 Jun 1997 03:14:37 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26646 for ; Sun, 29 Jun 1997 03:14:33 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA30013; Sun, 29 Jun 1997 20:10:53 +1000 Date: Sun, 29 Jun 1997 20:10:53 +1000 From: Bruce Evans Message-Id: <199706291010.UAA30013@godzilla.zeta.org.au> To: bde@zeta.org.au, Shimon@i-Connect.Net Subject: Re: com console, and h/w flow control... Cc: freebsd-hackers@FreeBSD.ORG, mburgett@cmnsens.zoom.com, tom@sdf.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >How about NOT completing the open until DCD is true? And sending a SIGHUP >when DCD drops? If init is responsible, then we can change that easily. >This is what O/S sources are for. Right? :-) That is normal behaviour for dialin ports unless CLOCAL is set, but CLOCAL is set for the console when init opens it. You can change the default in /etc/rc.local before the port is first opened except for the console. Hanging in open in init would normally be wrong for a local console, so the console defaults to CLOCAL. Bruce From owner-freebsd-hackers Sun Jun 29 03:51:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA27834 for hackers-outgoing; Sun, 29 Jun 1997 03:51:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA27829 for ; Sun, 29 Jun 1997 03:51:39 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA13453 for freebsd-hackers@FreeBSD.ORG; Sun, 29 Jun 1997 12:51:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id MAA07004; Sun, 29 Jun 1997 12:31:59 +0200 (MET DST) Message-ID: <19970629123156.YG34940@uriah.heep.sax.de> Date: Sun, 29 Jun 1997 12:31:56 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: com console, and h/w flow control... References: <199706281513.BAA32119@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Simon Shapiro on Jun 28, 1997 20:57:08 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote: > > There's nothing to prevent a suitably timed call from interrupting the > > boot. I think there's something to prevent single user shells. > > Anyone knows what that is? Mark the console as `insecure' in /etc/ttys, this will require the root password for the single-user shell. If i were you, i'd use a modem configured to callback. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jun 29 07:59:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04813 for hackers-outgoing; Sun, 29 Jun 1997 07:59:48 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA04807 for ; Sun, 29 Jun 1997 07:59:40 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id PAA17890; Sun, 29 Jun 1997 15:47:06 +0100 (BST) Message-Id: <199706291447.PAA17890@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Tom Samplonius cc: Tom , hackers@FreeBSD.ORG Subject: Re: PPTP? In-reply-to: Your message of "Sat, 28 Jun 1997 18:45:02 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Jun 1997 15:47:05 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Sat, 28 Jun 1997, Tom wrote: > > > I read through the mailing list archives looking for something, but I > > didn't find anything concrete. Is there a program that supports > > Point To Point Tunneling Protocol? My workplace is going > > to implement an NT RAS server to do this, and I don't want to have to > > built an NT machine to do this for me... > > Someone mentioned that IJPPP supported this in more recent versions, > > but I haven't checked that out yet. > > > > Anyone? jkh told me to ask here, so I am :) > > Do need to use PPTP, or will any VPN solution do? > > I believe that iijppp can do PPP over TCP, which can create a tunnel, > which you can use to make a VPN. I don't know how to configure the PPP > over TCP feature. There's an example in the manual in RELENG_2_2 & -current. If you don't sup/ctm, get http://www.freebsd.org/~brian/ppp-2.2-970624.tar.gz. > Tom I've just checked out the ppp man page on www.de.freebsd.org, Wasn't this going to be updated weekly ? Oh well. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 29 10:58:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10248 for hackers-outgoing; Sun, 29 Jun 1997 10:58:14 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA10239 for ; Sun, 29 Jun 1997 10:58:06 -0700 (PDT) Received: (qmail 11939 invoked by uid 1000); 29 Jun 1997 17:42:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706291010.UAA30013@godzilla.zeta.org.au> Date: Sun, 29 Jun 1997 10:42:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: com console, and h/w flow control... Cc: tom@sdf.com, mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 29-Jun-97 you wrote: > >How about NOT completing the open until DCD is true? And sending a > SIGHUP > >when DCD drops? If init is responsible, then we can change that easily. > >This is what O/S sources are for. Right? :-) > > That is normal behaviour for dialin ports unless CLOCAL is set, but > CLOCAL is set for the console when init opens it. You can change the > default in /etc/rc.local before the port is first opened except for > the console. Hanging in open in init would normally be wrong for a > local console, so the console defaults to CLOCAL. That pretty much confirms it. Thanx! Simon From owner-freebsd-hackers Sun Jun 29 10:58:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10256 for hackers-outgoing; Sun, 29 Jun 1997 10:58:16 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA10238 for ; Sun, 29 Jun 1997 10:58:06 -0700 (PDT) Received: (qmail 11937 invoked by uid 1000); 29 Jun 1997 17:42:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706291005.UAA29898@godzilla.zeta.org.au> Date: Sun, 29 Jun 1997 10:42:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: Clists limited to 1024 bytes? Cc: hackers@FreeBSD.ORG, bmcgover@cisco.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 29-Jun-97 you wrote: > >> Anyway, 19200 bps is not a heavy load unless there are a lot of active > >> ports. With 32 active 16550 ports it would be fairly heavy, but still > >> gives less than 6% of the throughput of a single 10Mb/s ethernet. > > > >I was thinking more (on a 16550) about what happens at 115,200, 230,400, > >and more. These are speeds we see already today with ISDN lines. > >The option of an external TA (such as a Motorola BitSRFR) is very > apealing, > >but behavior at these speeds needs careful consideration. > > > >How would you adjust the drivers to acomodate these speeds? > > 115200 was fast 10 years ago, but 230400 is currently not well support > (if you change the hardware clock to get it, then then the buffer sizes > are too small). How many ports do you need? Actually, about 15 years ago we used 384Kbps on terminals hooked to a Unix box (the tahoe was capable of supporting 256 of these, if i remember correctly), so even 10 years ago... :-) Yes, we use a doubled hardware clock. 2 ports is well enough. > >We experienced a lot of complex problems with SCSI transactions until we > >bumped the sio interrupt bufferto double its size. While performance > (on > >the sio ports - we use them only for PPP) did not drop visibly, the > strange > >incidence of dropping biodone() calls virtually stopped. > > This probably just made a race less common. It would be interesting to actually solve this mystery; how does a buffer overflow in the sio (under PPP) cause biodone to lose a completion. We know, with very high degree of certainty, that we do not lose interrupts, nor miss a call to scsi_done (which calls biodone, somehow). It appears that from scsi_done() up things drop in this case. Not every time. Nasty... Simon From owner-freebsd-hackers Sun Jun 29 11:32:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA11831 for hackers-outgoing; Sun, 29 Jun 1997 11:32:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11826 for ; Sun, 29 Jun 1997 11:32:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id EAA08361; Mon, 30 Jun 1997 04:30:50 +1000 Date: Mon, 30 Jun 1997 04:30:50 +1000 From: Bruce Evans Message-Id: <199706291830.EAA08361@godzilla.zeta.org.au> To: bde@zeta.org.au, Shimon@i-Connect.Net Subject: Re: Clists limited to 1024 bytes? Cc: bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >We experienced a lot of complex problems with SCSI transactions until we >> >bumped the sio interrupt bufferto double its size. While performance >> (on >> >the sio ports - we use them only for PPP) did not drop visibly, the >> strange >> >incidence of dropping biodone() calls virtually stopped. >> >> This probably just made a race less common. > >It would be interesting to actually solve this mystery; how does a buffer >overflow in the sio (under PPP) cause biodone to lose a completion. >We know, with very high degree of certainty, that we do not lose >interrupts, nor miss a call to scsi_done (which calls biodone, somehow). >It appears that from scsi_done() up things drop in this case. Not every >time. Nasty... Logging the error may delay completion for a long time. Disks shouldn't be very sensitive to this, but... Try turning of log() and printf(). I usually do this by temporarily replacing the first byte in the routine by 0xc3 (ret). Bruce From owner-freebsd-hackers Sun Jun 29 12:58:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15678 for hackers-outgoing; Sun, 29 Jun 1997 12:58:50 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15673 for ; Sun, 29 Jun 1997 12:58:43 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id WAA07946; Sun, 29 Jun 1997 22:58:18 +0300 (EEST) Date: Sun, 29 Jun 1997 22:58:17 +0300 (EEST) From: Narvi To: Michael Smith cc: hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Tcl loadable packages In-Reply-To: <199706290958.TAA19062@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2122234539-867614297=:7826" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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-2122234539-867614297=:7826 Content-Type: TEXT/PLAIN; charset=US-ASCII I included the to-be port as an attacment. It currently installs the script (one line :-)) in ${PREFIX}/libdata. as for ../lib/tcl/site_tcl/..., it seems a bit unnceesarily too long. How about lib/tcl_packages? The hiercharchy would look like: lib/tcl_packages lib/tcl_packages/package_1 lib/tcl_packages/package_2 lib/tcl_packages/package_3 . . . lib/tcl_packages/package_xyz All of these would contain a mandatory load script (named just load?) that would load the appropriate package (and possibly any dependancies). Version dependance - well, there realy is not much we can do. We could, of course, have the load files have ineligence enough to load the right library if present (but if not, etc.) Just my view. Sander There is no love, no good, no happiness and no future - all these are just illusions. --0-2122234539-867614297=:7826 Content-Type: APPLICATION/octet-stream; name="random.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sIAHLttDMAA+1ZbW/iOBDuV/wrRup+uNtTQ0ISsqClKgfZXnZ5U4Kut9JJ lUkc8DUvbJxot7vHfz+bpBRoK9pVoaoujwTEmRmP8XhmbE+CIy8Oq0f7BGiy oetwBKAYurL+ewMZoK7qulLXdUPhZEVV1CPQ9zqqAhlLcQJwxPhEkORhvl30 V4okt79PA8L2tQqebv+apuil/Q+BDfv38RURT8+sQ5HluqY9bH9d1bbsrymq dgTyM4/jXvzP7d+zfm9VKqkb5AsBOX/wN5f99seh3aooN01rIJoycuyOw9lz XslF1mBs2oN2b9nLZ9NBg+HIHn6wembeRDTi0xsETVR588MaOGPOuoA3PzrD 0ecFnMT8kYsOLwa8Mc0b5/aIN8K80R92zQX8jSqVgE5Wg5RYLCmSzFlGtvnB +mtR5VRUOXNxCkGMvcuCLQ3n8C8w4sEJAdbMmZsrqSacbrK7wb3D3OLZVOvh FCMk0cgNMo/A+wnzJP5aCq9O0Uvb9jHY8P/Q20vI3eX/UDe2/F+V63rp/4dA v6vDLzeLGyfS9Puv0AIXG17NaDTeEVlzfa+hygrWcMPVFL/mue/0V7G0SzwC G/6/FTyfS8dO/9fVLf/XNV0p/f8QECaHPJ+JdFa9L8/a+dbgpYdaYg8o/H9+ Nd3fHcBPnP9kQyvPf4fAmv07w37fHIyfX8eu+K+o2/FfVQy1jP+HQG8t3gNl gMG7jnBIXX5qu14effAkICDOPeRbSiJG4wjSGT9pYc9jwLL5PE5S8OMEFZ1E WTghCZPKfPEasOb/XdPp2PvQscP/OflO/De00v8Pgp/y/68z6s42AgDiAQC2 AwByciLxACekiVDlLfg08mg05Xo2uMFPxHOchDgAj7I0oZMs5bp2ypBv8zgi UUqfKujOaO1pEllE+d8M7wi5szhmQiq6kSIBCfmYWC6HIeAS693PSRJmKRYd QOxzOUHMX+baxXwLIUCoDcxN6Dy9cw/FrVVcr/EJptHdeykRlYFgdo2EqOiY 60pn5NaSElrz/1HPcvaQ/R9z/1P6/0vhgTMfKpZQdfuC9KXHW+J5Ufj/nio/ OXb5v1Ff7f/rmqEv73+1Wun/h8AxDMhXEFmaQVgsgmXeuC0JHcOfPJ2LVJWQ LxlNiNcEESKOoYtTAm5C+A9/V1PhYxYRUBoNgxMvZnHYBGc5bbwHRq/gfT6J ZzMceP9gJvlxcBXECZEIOUXHCHV5Ahq0+2ar0Dz6dL5srsZyIvT2287YtC8d a2w6rYqfzpvVKv+WIhKz2E8ll6/nAEfTDE8Jq3LZKltuQqohTmfVYsGjTnts ng9ty3R+a4n6Fwgq79sajPnHtFuVhweL0IX9ybE7LZ5z+VPXshdFvwjNE3Iy yWjgNUVFag6bldVcgIsu1qnbRatbJoT9lCQnt2W0s8Bz48in07xGdrcAttrJ b1elhI1fTVmqRIkSJUrsGf8BCtyYSwAoAAA= --0-2122234539-867614297=:7826-- From owner-freebsd-hackers Sun Jun 29 16:59:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22527 for hackers-outgoing; Sun, 29 Jun 1997 16:59:14 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22522; Sun, 29 Jun 1997 16:59:11 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id TAA22389; Sun, 29 Jun 1997 19:54:53 -0400 (EDT) Message-ID: <19970629195452.32243@vinyl.quickweb.com> Date: Sun, 29 Jun 1997 19:54:52 -0400 From: Mark Mayo To: multimedia@freebsd.org Cc: hackers@freebsd.org Subject: Monitor shadows? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I'm noticing a strange thing happening on my computer. At higher refresh rates (above 72Hz), I see what I can only describe as "shadows". For example, the borders of windows seem to have a little grey fading border on the right side. If the mouse is over a simple green background, I can really see the "shadow". It's quite annoying - even the black letters on the white background of my rxvt leave a little grey silhouette to the right. I'm guessing it happens (or more likely is visible) whenver you have sharp contrasting colors next to each other. Has anyone ever seen anything like this before? I'm not sure if it's the video card or the monitor. I'm going to bring another monitor home from school some day to see if it behaves similarly (which would mean it's the video card). I suspect it's the monitor though; The problem seems to get worse as I approach the maximum refresh rate of the monitor (which is why my hunch leans towards a monitor problem). I'm hoping this is some sort of gun alignment problem or something.. Specifics: Matrox Millenium (original, 175MHz RAMDAC) with 2MB WRAM. MAG Innovision MX17F G (the one with the LCD thing on the front). Same behaviour under FreeBSD (with AccelX), Windows95, WindowsNT. If anyone has any clues, I'd LOVE to know what you think!! -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Sun Jun 29 17:44:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24624 for hackers-outgoing; Sun, 29 Jun 1997 17:44:05 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24619; Sun, 29 Jun 1997 17:44:01 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id TAA09721; Sun, 29 Jun 1997 19:43:54 -0500 (EST) From: "John S. Dyson" Message-Id: <199706300043.TAA09721@dyson.iquest.net> Subject: Re: Monitor shadows? In-Reply-To: <19970629195452.32243@vinyl.quickweb.com> from Mark Mayo at "Jun 29, 97 07:54:52 pm" To: mark@quickweb.com (Mark Mayo) Date: Sun, 29 Jun 1997 19:43:54 -0500 (EST) Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi. I'm noticing a strange thing happening on my computer. At higher refresh > rates (above 72Hz), I see what I can only describe as "shadows". For example, > the borders of windows seem to have a little grey fading border on the right > side. If the mouse is over a simple green background, I can really see the > "shadow". It's quite annoying - even the black letters on the white background > of my rxvt leave a little grey silhouette to the right. > > I'm guessing it happens (or more likely is visible) whenver you have sharp > contrasting colors next to each other. > What you are seeing is a transient response problem. That problem can be due to many causes. It can even happen with a supurb monitor and an excellent display adaptor, if you have a lousy transmission line between them. The problem becomes more pronouced at higher and higher freqs. (So high scan rates will show the problem more than lower ones.) Most often, we have seen the problem with transmission line problems (the cable between the CRT and adapter.) However, I usually use good monitors, and good display adapters -- so the only thing left is a lousy cable. The next most likely cause would be a monitor limitation. Note that cables cause problems only because people don't think that the cable is very critical. Well, the cables are critical -- and I am not talking about guilded audio cables (which are mostly hype, IMO). Video is a very different animal. You can get by with fairly long cables, IF and only IF you match the impedance of the cable and driving/receiving devices. Cheap cables have widely varying and uncontrolled impedance characteristics. Such attributes can lead to reflections (similar to SWR in Ham/CB radio parlance), and that can ringing or delayed rise/fall times. Those delayed rise/fall times can make the video look smeary. After this long explanation, your problem could still be a bad video card, or a CRT that just can't handle the bandwidth also. Note that a reasonable CRT mostly gets soft looking though. Smearing biases my guess about the problem a little bit more towards the cable. John From owner-freebsd-hackers Sun Jun 29 17:50:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24856 for hackers-outgoing; Sun, 29 Jun 1997 17:50:30 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24851; Sun, 29 Jun 1997 17:50:27 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA22072; Mon, 30 Jun 1997 10:20:14 +0930 (CST) From: Michael Smith Message-Id: <199706300050.KAA22072@genesis.atrad.adelaide.edu.au> Subject: Re: Monitor shadows? In-Reply-To: <19970629195452.32243@vinyl.quickweb.com> from Mark Mayo at "Jun 29, 97 07:54:52 pm" To: mark@quickweb.com (Mark Mayo) Date: Mon, 30 Jun 1997 10:20:14 +0930 (CST) Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mark Mayo stands accused of saying: > Hi. I'm noticing a strange thing happening on my computer. At higher > refresh rates (above 72Hz), I see what I can only describe as > "shadows". For example, the borders of windows seem to have a little > grey fading border on the right side. If the mouse is over a simple > green background, I can really see the "shadow". It's quite annoying > - even the black letters on the white background of my rxvt leave a > little grey silhouette to the right. > > I'm guessing it happens (or more likely is visible) whenver you have sharp > contrasting colors next to each other. > Has anyone ever seen anything like this before? I'm not sure if it's > the video card or the monitor. I'm going to bring another monitor > home from school some day to see if it behaves similarly (which > would mean it's the video card). I suspect it's the monitor though; > The problem seems to get worse as I approach the maximum refresh > rate of the monitor (which is why my hunch leans towards a monitor > problem). Yes, many times. It's an indication that you've exceeded the video bandwidth of your monitor, either because you are overdriving it frequency-wise, overdriving it signal wise (so the input amplifiers are driven into clipping), or because the bandwidth has degraded, often due to aging of capacitors (particularly electrolytics). > I'm hoping this is some sort of gun alignment problem or something.. Nope. > MAG Innovision MX17F G (the one with the LCD thing on the front). Same I've got one of them; bleagh. Mostly mine is just fading; it jitters a little too, but it certainly isn't ringing or smearing, and I drive it pretty hard at times. > Mark Mayo mark@quickweb.com -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 29 19:27:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28215 for hackers-outgoing; Sun, 29 Jun 1997 19:27:45 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28205 for ; Sun, 29 Jun 1997 19:27:41 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id TAA00860 for ; Sun, 29 Jun 1997 19:27:39 -0700 (PDT) Date: Sun, 29 Jun 1997 19:27:39 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Make world broken in RELENG_2_2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cvsup'd today: /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:8875: Validation error. `Prev' field points to node `Using History Interactively', which doesn't exist. /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:173: Validation error. `Menu' field points to node `Using History Interactively', which doesn't exist. /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:172: Validation error. `Menu' field points to node `Command Line Editing', which doesn't exist. *** Error code 2 Stop. *** Error code 1 Stop. From owner-freebsd-hackers Sun Jun 29 20:26:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00561 for hackers-outgoing; Sun, 29 Jun 1997 20:26:59 -0700 (PDT) Received: from super-g.inch.com (super-g.inch.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA00556; Sun, 29 Jun 1997 20:26:56 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id XAA13191; Sun, 29 Jun 1997 23:36:14 GMT Date: Sun, 29 Jun 1997 23:36:14 +0000 (GMT) From: spork X-Sender: spork@super-g.inch.com To: Mark Mayo cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Monitor shadows? In-Reply-To: <19970629195452.32243@vinyl.quickweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've seen this when going through an A/B switch, and also on cheaper monitors where they haven't fully sheilded the cable enough. The shadowing is usually indicative of something low quality in the path between your card and your monitor. My monitor actually looks a bit better if I fully screw in the cable to the card... Charles On Sun, 29 Jun 1997, Mark Mayo wrote: > Hi. I'm noticing a strange thing happening on my computer. At higher refresh > rates (above 72Hz), I see what I can only describe as "shadows". For example, > the borders of windows seem to have a little grey fading border on the right > side. If the mouse is over a simple green background, I can really see the > "shadow". It's quite annoying - even the black letters on the white background > of my rxvt leave a little grey silhouette to the right. > > I'm guessing it happens (or more likely is visible) whenver you have sharp > contrasting colors next to each other. > > Has anyone ever seen anything like this before? I'm not sure if it's the video > card or the monitor. I'm going to bring another monitor home from school > some day to see if it behaves similarly (which would mean it's the video card). > I suspect it's the monitor though; The problem seems to get worse as I approach > the maximum refresh rate of the monitor (which is why my hunch leans towards > a monitor problem). > > I'm hoping this is some sort of gun alignment problem or something.. > > Specifics: Matrox Millenium (original, 175MHz RAMDAC) with 2MB WRAM. > MAG Innovision MX17F G (the one with the LCD thing on the front). Same > behaviour under FreeBSD (with AccelX), Windows95, WindowsNT. > > If anyone has any clues, I'd LOVE to know what you think!! > > -Mark > > -- > ---------------------------------------------------------------------------- > Mark Mayo mark@quickweb.com > RingZero Comp. http://vinyl.quickweb.com/mark > > finger mark@quickweb.com for my PGP key and GCS code > ---------------------------------------------------------------------------- > University degrees are a bit like adultery: you may not want to > get involved with that sort of thing, but you don't want to be > thought incapable. -Sir Peter Imbert > From owner-freebsd-hackers Sun Jun 29 21:40:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03349 for hackers-outgoing; Sun, 29 Jun 1997 21:40:39 -0700 (PDT) Received: from dry.jps.net (root@dry.jps.net [207.105.167.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03343; Sun, 29 Jun 1997 21:40:35 -0700 (PDT) Received: from Default (istk-port631.jps.net [208.25.63.156]) by dry.jps.net (8.8.5/8.8.5) with SMTP id VAA12307; Sun, 29 Jun 1997 21:40:32 -0700 (PDT) Date: Sun, 29 Jun 1997 21:40:32 -0700 (PDT) Message-Id: <199706300440.VAA12307@dry.jps.net> X-Sender: cybthrill@jps.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: owner-hackers@freebsd.org, hackers@freebsd.org From: Cyber Thrill Subject: unsubscribe Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe /* matt@jps.net */ /* `Feel the thrill' */ /* Nick: Cyber Thrill */ /* http://www.jps.net/rstrom */ From owner-freebsd-hackers Sun Jun 29 21:41:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03382 for hackers-outgoing; Sun, 29 Jun 1997 21:41:19 -0700 (PDT) Received: from dry.jps.net (root@dry.jps.net [207.105.167.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03373; Sun, 29 Jun 1997 21:41:13 -0700 (PDT) Received: from Default (istk-port631.jps.net [208.25.63.156]) by dry.jps.net (8.8.5/8.8.5) with SMTP id VAA12375; Sun, 29 Jun 1997 21:41:02 -0700 (PDT) Date: Sun, 29 Jun 1997 21:41:02 -0700 (PDT) Message-Id: <199706300441.VAA12375@dry.jps.net> X-Sender: cybthrill@jps.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: owner-hackers@freebsd.org, hackers@freebsd.org From: Cyber Thrill Subject: unsubscribe cybthrill Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe cybthrill /* matt@jps.net */ /* `Feel the thrill' */ /* Nick: Cyber Thrill */ /* http://www.jps.net/rstrom */ From owner-freebsd-hackers Sun Jun 29 21:42:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03435 for hackers-outgoing; Sun, 29 Jun 1997 21:42:21 -0700 (PDT) Received: from dry.jps.net (root@dry.jps.net [207.105.167.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03424; Sun, 29 Jun 1997 21:42:16 -0700 (PDT) Received: from Default (istk-port631.jps.net [208.25.63.156]) by dry.jps.net (8.8.5/8.8.5) with SMTP id VAA12586; Sun, 29 Jun 1997 21:42:14 -0700 (PDT) Date: Sun, 29 Jun 1997 21:42:14 -0700 (PDT) Message-Id: <199706300442.VAA12586@dry.jps.net> X-Sender: cybthrill@jps.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: owner-hackers@freebsd.org, hackers@freebsd.org From: Cyber Thrill Subject: unsubscribe cybthrill cybthrill@jps.ent Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe cybthrill cybthrill@jps.net /* matt@jps.net */ /* `Feel the thrill' */ /* Nick: Cyber Thrill */ /* http://www.jps.net/rstrom */ From owner-freebsd-hackers Sun Jun 29 21:43:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03473 for hackers-outgoing; Sun, 29 Jun 1997 21:43:09 -0700 (PDT) Received: from dry.jps.net (root@dry.jps.net [207.105.167.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03467; Sun, 29 Jun 1997 21:43:07 -0700 (PDT) Received: from Default (istk-port631.jps.net [208.25.63.156]) by dry.jps.net (8.8.5/8.8.5) with SMTP id VAA12713; Sun, 29 Jun 1997 21:42:55 -0700 (PDT) Date: Sun, 29 Jun 1997 21:42:55 -0700 (PDT) Message-Id: <199706300442.VAA12713@dry.jps.net> X-Sender: cybthrill@jps.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: owner-hackers@freebsd.org, hackers@freebsd.org From: Cyber Thrill Subject: unsubscribe cybthrill@jps.net Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe cybthrill@jps.net /* matt@jps.net */ /* `Feel the thrill' */ /* Nick: Cyber Thrill */ /* http://www.jps.net/rstrom */ From owner-freebsd-hackers Sun Jun 29 21:51:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03860 for hackers-outgoing; Sun, 29 Jun 1997 21:51:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA03855 for ; Sun, 29 Jun 1997 21:50:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA24389 for hackers@FreeBSD.ORG; Mon, 30 Jun 1997 06:50:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id GAA02917; Mon, 30 Jun 1997 06:47:02 +0200 (MET DST) Message-ID: <19970630064702.UJ55456@uriah.heep.sax.de> Date: Mon, 30 Jun 1997 06:47:02 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Monitor shadows? References: <19970629195452.32243@vinyl.quickweb.com> <199706300043.TAA09721@dyson.iquest.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706300043.TAA09721@dyson.iquest.net>; from John S. Dyson on Jun 29, 1997 19:43:54 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: > Video is a very different animal. You can get by with fairly long cables, > IF and only IF you match the impedance of the cable and driving/receiving > devices. Needless to say that this is almost impossible to get with these crappy VGA connectors that are so `modern' these days. I really wonder why the industry didn't adopt something like the Sun solution when the VGA cards grew up to the dot-clock range of 100 or even 200 MHz. The DB-15 might have been appropriate for 28 MHz, but it can only lose in this respect at the higher frequencies. (No, i don't wonder. It's PeeCee, they always continue the currently used solution, however crappy it might be. See IDE. See ISA ``PnP''.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jun 30 08:45:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA00344 for hackers-outgoing; Mon, 30 Jun 1997 08:45:28 -0700 (PDT) Received: from calvary.pascal.org ([207.21.96.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA00333 for ; Mon, 30 Jun 1997 08:45:19 -0700 (PDT) Received: from calvary.pascal.org (calvary [207.21.96.1]) by calvary.pascal.org (8.8.5/8.8.5) with ESMTP id IAA19422; Mon, 30 Jun 1997 08:44:17 -0700 (PDT) Message-ID: <33B7D451.443B8236@compute.com> Date: Mon, 30 Jun 1997 08:44:17 -0700 From: "Freeman P. Pascal IV" Organization: Compute Intensive, Inc. X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org CC: Freeman Pascal , demasi@informix.com Subject: Problems with onboard Adaptec 7870 on Intel ALTServer motherboard... X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm experiencing problems with 2.2.1-RELEASE on an Intel ALTServer motherboard. The system installed fine, but it randomly generates SCSI timeouts that hang the controller and the system. I've read in the freebsd-questions archive that the fix was to move up to 2.1-STABLE. I assume that the fixes would also be in 2.2.1-RELEASE. Has anyone else seen this problem and is there a fix? Please say "yes" - I have four of these systems and I want them to work with FreeBSD. -Freeman -- --------------------------------------------------------------------------- C O M P U T E I N T E N S I V E , I N C . (A Member of the Verio Group) --------------------------------------------------------------------------- Freeman P. Pascal IV Phone Work: (800) 273-5600 Compute Intensive, Inc. Home: (510) 232-0914 8001 Irvine Center Drive FAX: (510) 236-2396 Suite 1130 Email Work: pascal@compute.com Irvine, CA 92618 Home: pascal@pascal.org URL: Work: http://www.compute.com Work: http://www.verio.com Home: http://www.pascal.org --------------------------------------------------------------------------- For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. - John 3:16 (KJV) From owner-freebsd-hackers Mon Jun 30 08:58:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA00997 for hackers-outgoing; Mon, 30 Jun 1997 08:58:34 -0700 (PDT) Received: from cliff.bms.com (cliff.bms.com [140.176.1.102]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA00992 for ; Mon, 30 Jun 1997 08:58:30 -0700 (PDT) Received: from synapse.bms.com (synapse1.bms.com) by cliff.bms.com (PMDF V5.1-8 #22413) with SMTP id <01IKOLADANOA003GAP@cliff.bms.com> for hackers@freebsd.org; Mon, 30 Jun 1997 11:57:18 EST Received: by synapse.bms.com (4.1/SMI-4.1) id AA29429; Mon, 30 Jun 1997 11:57:58 -0400 (EDT) Date: Mon, 30 Jun 1997 11:57:57 -0400 (EDT) From: metcalfj@synapse.bms.com (Jeffrey M. Metcalf) Subject: Documentation for PAS16 SCSI adapter To: hackers@freebsd.org Cc: metcalf@snet.net Message-id: <9706301557.AA29429@synapse.bms.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I am writing to ask if there is any kind soul reading this mailing list who knows how I can get my hands on documentation for the SCSI adapter on a ProAudioStudio sound card. The adapter is buggy in that writing to my SCSI Zip 100 drive results in corrupted files. The author of the device driver according to the FreeBSD source code has not responded to any of my questions. Media Vision is discontinuing all support for the card as of today and charges $20.00 just to ask them about how I can get documentation. It seems that I will have to fix the driver myself, and that's fine. I need the practice. But I can't do it without explicit documentation. Is there anybody in this group who has copies of the documentation or knows who to contact who might. I vaguely remember reading something some time back saying that Trantor would be the contact and that Trantor has been acquired by Adaptec. Would Adaptec be the place to go for technical documantation for writing this device driver? Thanks for any suggestions, JM --- Jeffrey M. Metcalf metcalfj@synapse.bms.com http://ruddles.stat.uconn.edu/~jeff From owner-freebsd-hackers Mon Jun 30 09:30:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02408 for hackers-outgoing; Mon, 30 Jun 1997 09:30:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02394 for ; Mon, 30 Jun 1997 09:30:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id CAA26718; Tue, 1 Jul 1997 02:00:02 +0930 (CST) From: Michael Smith Message-Id: <199706301630.CAA26718@genesis.atrad.adelaide.edu.au> Subject: Re: Documentation for PAS16 SCSI adapter In-Reply-To: <9706301557.AA29429@synapse.bms.com> from "Jeffrey M. Metcalf" at "Jun 30, 97 11:57:57 am" To: metcalfj@synapse.bms.com (Jeffrey M. Metcalf) Date: Tue, 1 Jul 1997 02:00:02 +0930 (CST) Cc: hackers@FreeBSD.ORG, metcalf@snet.net X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jeffrey M. Metcalf stands accused of saying: > > I am writing to ask if there is any kind soul reading this > mailing list who knows how I can get my hands on documentation > for the SCSI adapter on a ProAudioStudio sound card. The > adapter is buggy in that writing to my SCSI Zip 100 drive > results in corrupted files. The author of the device driver > according to the FreeBSD source code has not responded to any > of my questions. Media Vision is discontinuing all support > for the card as of today and charges $20.00 just to ask them > about how I can get documentation. The PAS16 uses (IIRC) the NCR 53c400, which is a derivative of the 53c80. Datasheets for both these parts should be available from your local NCR/Symbios Logic parts supplier. There is also sample driver code available for these parts from the ncr ftp site. The 53c80 is a fairly ancient, but well-understood SCSI controller. It may be of benefit to you to study the NetBSD/sun3 sources for the 'si' driver and possibly other NetBSD 53c80 drivers in order to hunt for possible differences in handling. It should be possible to glean enough implementation-specific information from the existing driver, as it wouldn't work at all if that was fundamentally wrong. You may also want to spend some time mapping out the PCB traces on the PAS16 if you don't trust this. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 30 09:55:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA03780 for hackers-outgoing; Mon, 30 Jun 1997 09:55:31 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA03775 for ; Mon, 30 Jun 1997 09:55:28 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wijgL-00042R-00; Mon, 30 Jun 1997 09:52:05 -0700 Date: Mon, 30 Jun 1997 09:52:05 -0700 (PDT) From: Tom Samplonius To: "Freeman P. Pascal IV" cc: freebsd-hackers@freebsd.org, demasi@informix.com Subject: Re: Problems with onboard Adaptec 7870 on Intel ALTServer motherboard... In-Reply-To: <33B7D451.443B8236@compute.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Freeman P. Pascal IV wrote: > I'm experiencing problems with 2.2.1-RELEASE on an Intel ALTServer > motherboard. The system installed fine, but it randomly generates > SCSI timeouts that hang the controller and the system. > > I've read in the freebsd-questions archive that the fix was to move > up to 2.1-STABLE. I assume that the fixes would also be in > 2.2.1-RELEASE. You should move to 2.2-stable, or even 2.2.2-RELEASE. Both 2.1-stable and 2.2-stable have the same ahc driver. The SCSI timeout problem is drive related. I used to use an ancient version of the ahc driver for nearly a year of continous operation (209 days of uptime) without any problems, before one of the drives started to timeout and hang the system. I upgraded the ahc driver, and now the drive still times out, but it no longer hangs the system. Tom From owner-freebsd-hackers Mon Jun 30 10:50:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06595 for hackers-outgoing; Mon, 30 Jun 1997 10:50:41 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06589 for ; Mon, 30 Jun 1997 10:50:37 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Mon, 30 Jun 1997 12:49:42 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freebsd.org'" Subject: /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Date: Mon, 30 Jun 1997 12:49:39 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Should I worry ? Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Jun 29 02:06:07 kiyoko /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) The kernel is compiled with controller ahc0 options AHC_TAGENABLE options AHC_ALLOW_MEMIO the disk system: Jun 20 11:29:35 myname /kernel: ahc0 rev 0 int a irq 10 on pci0:13 Jun 20 11:29:35 myname /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs Jun 20 11:29:35 myname /kernel: ahc0 waiting for scsi devices to settle Jun 20 11:29:35 myname /kernel: ahc0: target 0 Tagged Queuing Device Jun 20 11:29:36 myname /kernel: (ahc0:0:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 Jun 20 11:29:36 myname /kernel: sd0(ahc0:0:0): Direct-Access 8669MB (17755614 512 byte sectors) Jun 20 11:29:36 myname /kernel: ahc0: target 1 Tagged Queuing Device Jun 20 11:29:36 myname /kernel: (ahc0:1:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 Jun 20 11:29:36 myname /kernel: sd1(ahc0:1:0): Direct-Access 8669MB (17755614 512 byte sectors) Jun 20 11:29:36 myname /kernel: ahc0: target 2 Tagged Queuing Device Jun 20 11:29:36 myname /kernel: (ahc0:2:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 Jun 20 11:29:36 myname /kernel: sd4(ahc0:2:0): Direct-Access 8669MB (17755614 512 byte sectors) Jun 20 11:29:36 myname /kernel: ahc0: target 3 Tagged Queuing Device Jun 20 11:29:36 myname /kernel: (ahc0:3:0): "Quantum XP34300W L912" type 0 fixed SCSI 2 Jun 20 11:29:36 myname /kernel: sd2(ahc0:3:0): Direct-Access 4303MB (8813920 512 byte sectors) Jun 20 11:29:36 myname /kernel: ahc0: target 4 Tagged Queuing Device Jun 20 11:29:36 myname /kernel: (ahc0:4:0): "Quantum XP34300W L912" type 0 fixed SCSI 2 Jun 20 11:29:37 myname /kernel: sd3(ahc0:4:0): Direct-Access 4303MB (8813920 512 byte sectors) From owner-freebsd-hackers Mon Jun 30 10:51:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06663 for hackers-outgoing; Mon, 30 Jun 1997 10:51:55 -0700 (PDT) Received: from odin.INS.CWRU.Edu (odin.INS.CWRU.Edu [129.22.8.102]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06658 for ; Mon, 30 Jun 1997 10:51:51 -0700 (PDT) Received: (chet@localhost) by odin.INS.CWRU.Edu (8.7.6+cwru/CWRU-2.3-ins) id NAA06544; Mon, 30 Jun 1997 13:51:37 -0400 (EDT) (from chet) Date: Mon, 30 Jun 1997 13:48:50 -0400 From: Chet Ramey To: jkh@time.cdrom.com Subject: Re: use of readline() Cc: hackers@freebsd.org, chet@odin.INS.CWRU.Edu Reply-To: chet@po.CWRU.Edu In-Reply-To: Message from jkh@time.cdrom.com of Mon, 23 Jun 1997 10:01:03 -0700 (id <9964.867085263@time.cdrom.com>) Message-ID: <9706301748.AA06347.SM@odin.INS.CWRU.Edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Go read the copyright that is actually attached to libreadline. > > Right you are, unfortunately - I went looking for it in > the wrong place and assumed the LGPL when I couldn't find > a COPYING file. > > This is unusual, of course, since the FSF switched to the LGPL for > just about every other GNU lib I can find and I can only assume that > either the author was feeling particularly restrictive or, in fact, > nobody ever bothered to update the copyright. :) I was neither feeling restrictive nor inattentive. The last time I asked the FSF people, they requested that I continue to release readline under the GPL. (Sorry if I sound short; I'm trying to dig out from the mail accumulated during a (refreshingly) long trip to Europe.) -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu From owner-freebsd-hackers Mon Jun 30 11:19:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07950 for hackers-outgoing; Mon, 30 Jun 1997 11:19:48 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07941 for ; Mon, 30 Jun 1997 11:19:32 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA12131; Mon, 30 Jun 1997 19:17:38 +0200 Date: Mon, 30 Jun 1997 19:17:38 +0200 From: Luigi Rizzo Message-Id: <199706301717.TAA12131@labinfo.iet.unipi.it> To: luigi@labinfo.iet.unipi.it, hackers@freebsd.org Subject: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Apologies if this is off topic, but I found this on the news, and it sounds interesting. I haven't been able to try it because the site is quite slow from here. Now if only they had the ability of running telnet sessions over the ppp link that would be even more useful for me... [of course we can dump an installed FreeBSD version on a bootable CD and achieve the same effect...] Cheers Luigi In article <5opuds$td@qnx.com>, danh@qnx.com (Dan Hildebrand) writes: |> The challenge: Put a Web browser, a web server, a POSIX-certified |> realtime OS, TCP/IP and a windowing system on a single 1.44 Mbyte |> floppy disk. |> |> Impossible? |> |> QNX Software Systems Ltd. announces the QNX Demo Disk (downloadable |> from http://www.qnx.com/iat/). This single 1.44 Mbyte floppy disk |> contains: |> |> 1. Voyager Web Browser (Full HTML 3.2, frames, tables, etc.) |> 2. Voyager Embedded Web Server |> 3. The QNX Realtime Operating System |> 4. TCP/IP (with PPP including CHAP/PAP support) |> 5. Photon microGUI Windowing System |> 6. A "remote control" device to simulate a TV set top box |> 7. An Internet Phone Dialer |> 8. A Graphical File Browser |> 9. A Graphical Text Editor |> 10. A Vector Graphics Animation |> 11. Over 180 Kbytes of HTML and image content |> |> With this floppy disk and a desktop PC, you can browse the web or |> turn that PC into a web server accessible to other computers on the |> Internet. |> |> To download a copy, visit the http://www.qnx.com/iat/ website. To |> run the demodisk, you'll need a PC with a 386 or better, 6 Mbytes |> of RAM minimum, a mouse, VGA or better video and, optionally, a |> modem. |> |> A floppy drive is required, but the hard drive is not. :-) |> -- |> Dan Hildebrand (danh@qnx.com) QNX Software Systems, Ltd. |> http://www.qnx.com/~danh 175 Terence Matthews |> phone: +1 (613) 591-0931 Kanata, Ontario, Canada |> fax: +1 (613) 591-3579 K2M 1W8 -- -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Jun 30 11:48:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA09337 for hackers-outgoing; Mon, 30 Jun 1997 11:48:17 -0700 (PDT) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA09303 for ; Mon, 30 Jun 1997 11:47:35 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.8.5/8.8.5) id NAA28068; Mon, 30 Jun 1997 13:47:05 -0500 (CDT) Message-ID: <19970630134705.05887@shell.futuresouth.com> Date: Mon, 30 Jun 1997 13:47:05 -0500 From: Tim Tsai To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) References: <199706301717.TAA12131@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199706301717.TAA12131@labinfo.iet.unipi.it>; from Luigi Rizzo on Mon, Jun 30, 1997 at 07:17:38PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Jun 30, 1997 at 07:17:38PM +0200, Luigi Rizzo wrote: > Now if only they had the ability of running telnet sessions over the > ppp link that would be even more useful for me... That can be done easily enough in QNX. It's just not in the 1.44M bundle. Tim From owner-freebsd-hackers Mon Jun 30 12:20:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10601 for hackers-outgoing; Mon, 30 Jun 1997 12:20:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10594 for ; Mon, 30 Jun 1997 12:20:31 -0700 (PDT) Received: (qmail 20535 invoked by uid 1000); 30 Jun 1997 17:21:11 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706291830.EAA08361@godzilla.zeta.org.au> Date: Mon, 30 Jun 1997 10:21:11 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: Clists limited to 1024 bytes? Cc: bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 29-Jun-97 you wrote: ... > Logging the error may delay completion for a long time. Disks shouldn't > be very sensitive to this, but... Try turning of log() and printf(). > I usually do this by temporarily replacing the first byte in the routine > by 0xc3 (ret). [ Backwards ] The `ret' trick is as old as I am. wonder how well it (C3) will work on an Alpha :-) BTW, this is an 8080 opcode, methinks.. I think the problem we suffer from is not necessarily due to delays but something else. What we see is either completions reported by calling scsi_done being lost, or something that scsi_done does when called getting lost. The symptom is; A calling user process (dd, cpio, compilation, etc.) simply blocks indefinitely in biowait. This is manifested by having a PPP session running. Load is not very important. Without PPP I can bring the system to LA of 120 or so, without problem. With PPP connected, all you have to do is receive email while running make world. Somewhere in the middle, things wil start dying. This is much mode so on a P6 than a P5. Simon From owner-freebsd-hackers Mon Jun 30 12:38:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA11535 for hackers-outgoing; Mon, 30 Jun 1997 12:38:23 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA11528 for ; Mon, 30 Jun 1997 12:38:17 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id PAA16852 for ; Mon, 30 Jun 1997 15:38:13 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id PAA19919 for ; Mon, 30 Jun 1997 15:38:12 -0400 Date: Mon, 30 Jun 1997 15:37:56 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: mounting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm stumped here, could I get some help? I'm trying to do an NFS mount of a directory on a 3.0 machine onto another machine that's running 2.2.1, for the purpose of transferring /usr/src. I can mount the 3.0 machine's /usr/src onto my (current) machine and transfer files with no problem. When I do the mount onto the 2.2.1 machine, the first ls works, then everything afterwards fails, and hangs. I have tried, as a test, just to transfer the Makefile into another directory, here's the ps from it: 207 p1 D 0:00.01 cp /usr/src/Makefile I don't understand the "D" status. All the nfsd and nfsiod's are running, as is portmap and mountd, on both machines. Since I can successfully mount and tranfer files from the source machine to my own, I think maybe it's in the target machine (the 2.2.1 machine) that has the trouble, but I can't guess what it is. Can you? I've tried this several times, and done some reboot cycles that seemed to work just fine. I'm willing to do some experimentation ... ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 13:13:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA13370 for hackers-outgoing; Mon, 30 Jun 1997 13:13:19 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13353 for ; Mon, 30 Jun 1997 13:13:04 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id QAA06206; Thu, 12 Jun 1997 16:15:56 GMT Date: Thu, 12 Jun 1997 16:15:55 +0000 (GMT) From: BRiGHTMN To: Chuck Robey cc: FreeBSD-Hackers Subject: Re: mounting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm stumped here, could I get some help? yes the man pages, a man on ps states: state The state is given by a sequence of letters, for example, ``RWNA''. The first letter indicates the run state of the pro-cess: D Marks a process in disk (or other short term, uninter-ruptible) wait. your NFS servers aren't responding correctly try using NFS version 2 instead of 3 it worked for me. Alfred Perlstein perlsta@cs.sunyit.edu > I'm trying to do an NFS mount of a directory on a 3.0 machine onto another > machine that's running 2.2.1, for the purpose of transferring /usr/src. I > can mount the 3.0 machine's /usr/src onto my (current) machine and > transfer files with no problem. When I do the mount onto the 2.2.1 > machine, the first ls works, then everything afterwards fails, and hangs. > I have tried, as a test, just to transfer the Makefile into another > directory, here's the ps from it: > > 207 p1 D 0:00.01 cp /usr/src/Makefile > > I don't understand the "D" status. All the nfsd and nfsiod's are running, > as is portmap and mountd, on both machines. Since I can successfully > mount and tranfer files from the source machine to my own, I think maybe > it's in the target machine (the 2.2.1 machine) that has the trouble, but I > can't guess what it is. Can you? > > I've tried this several times, and done some reboot cycles that seemed to > work just fine. I'm willing to do some experimentation ... > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > From owner-freebsd-hackers Mon Jun 30 13:30:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA14426 for hackers-outgoing; Mon, 30 Jun 1997 13:30:32 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14408 for ; Mon, 30 Jun 1997 13:30:25 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id QAA27261; Mon, 30 Jun 1997 16:30:20 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id QAA22531; Mon, 30 Jun 1997 16:30:17 -0400 Date: Mon, 30 Jun 1997 16:30:02 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: BRiGHTMN cc: FreeBSD-Hackers Subject: Re: mounting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 12 Jun 1997, BRiGHTMN wrote: > > > > I'm stumped here, could I get some help? > yes the man pages, a man on ps states: > > state The state is given by a sequence of letters, for example, > ``RWNA''. The first letter indicates the run state of the > pro-cess: > > D Marks a process in disk (or other short term, > uninter-ruptible) wait. > > your NFS servers aren't responding correctly try using NFS version 2 > instead of 3 it worked for me. I think I now have it figured out. Desperation does wonderful things for the mind ... Michael Smith had told me previously about the abysmal performance of the 3C503 card that machine has, about some buffer incompatibility it has, and I think it's ibtten me now. I found disk space, tarred up what I wanted to transfer, and I sent it over that way, which worked like a charm. Means I can't get nfs mounting to work, but at least I can get what I want up, going along. > > Alfred Perlstein > perlsta@cs.sunyit.edu > > > I'm trying to do an NFS mount of a directory on a 3.0 machine onto another > > machine that's running 2.2.1, for the purpose of transferring /usr/src. I > > can mount the 3.0 machine's /usr/src onto my (current) machine and > > transfer files with no problem. When I do the mount onto the 2.2.1 > > machine, the first ls works, then everything afterwards fails, and hangs. > > I have tried, as a test, just to transfer the Makefile into another > > directory, here's the ps from it: > > > > 207 p1 D 0:00.01 cp /usr/src/Makefile > > > > I don't understand the "D" status. All the nfsd and nfsiod's are running, > > as is portmap and mountd, on both machines. Since I can successfully > > mount and tranfer files from the source machine to my own, I think maybe > > it's in the target machine (the 2.2.1 machine) that has the trouble, but I > > can't guess what it is. Can you? > > > > I've tried this several times, and done some reboot cycles that seemed to > > work just fine. I'm willing to do some experimentation ... > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > > (301) 220-2114 | version 3.0 current -- and great FUN! > > ----------------------------+----------------------------------------------- > > > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 14:13:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA16264 for hackers-outgoing; Mon, 30 Jun 1997 14:13:12 -0700 (PDT) Received: from lister.bogon.net (0@[204.137.132.49]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16256 for ; Mon, 30 Jun 1997 14:13:06 -0700 (PDT) Received: from kryten.bogon.net (500@kryten.bogon.net [204.137.132.58]) by lister.bogon.net (8.8.5/8.8.5) with ESMTP id OAA28941 for ; Mon, 30 Jun 1997 14:12:05 -0700 (PDT) From: Wes Santee Received: (from wes@localhost) by kryten.bogon.net (8.8.5/8.8.5) id OAA08470 for hackers@freebsd.org; Mon, 30 Jun 1997 14:12:00 -0700 (PDT) Message-Id: <199706302112.OAA08470@kryten.bogon.net> Subject: make world still broken To: hackers@freebsd.org Date: Mon, 30 Jun 1997 14:11:59 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cvsup'd at ~1:00pm PDT June 30th. Previous commit to fix gnu info files got it farther along, but it's still complaining. ===> gnu/usr.bin/gdb/doc makeinfo -I /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc -I /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/readline/doc -I /usr/src/gnu/usr.bin/gdb/doc/../../../lib/libreadline/doc --no-split -I /usr/src/gnu/usr.bin/gdb/doc -I /usr/src/gnu/usr.bin/gdb/doc /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo -o gdb.info.new Making info file `gdb.info.new' from `/usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo'. /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:8752: `@include rluser.texinfo': No such file or directory. /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:8513: Validation error. `Next' field points to node `Command Line Editing', which doesn't exist. /usr/src/gnu/usr.bin/gdb/doc/inc-hist.texi:34: Validation error. `Prev' field points to node `Command Line Editing', which doesn't exist. /usr/src/gnu/usr.bin/gdb/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:172: Validation error. `Menu' field points to node `Command Line Editing', which doesn't exist. *** Error code 2 Stop. Cheers, -- ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) ( mailto:wes@bogon.net ) From owner-freebsd-hackers Mon Jun 30 14:56:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA18208 for hackers-outgoing; Mon, 30 Jun 1997 14:56:13 -0700 (PDT) Received: from lister.bogon.net (0@gw.bogon.net [204.137.132.49]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18202 for ; Mon, 30 Jun 1997 14:56:09 -0700 (PDT) Received: from kryten.bogon.net (500@kryten.bogon.net [204.137.132.58]) by lister.bogon.net (8.8.5/8.8.5) with ESMTP id OAA29320; Mon, 30 Jun 1997 14:56:02 -0700 (PDT) From: Wes Santee Received: (from wes@localhost) by kryten.bogon.net (8.8.5/8.8.5) id OAA08657; Mon, 30 Jun 1997 14:55:56 -0700 (PDT) Message-Id: <199706302155.OAA08657@kryten.bogon.net> Subject: Re: make world still broken In-Reply-To: <199706302112.OAA08470@kryten.bogon.net> from Wes Santee at "Jun 30, 97 02:11:59 pm" To: wes@bogon.net (Wes Santee) Date: Mon, 30 Jun 1997 14:55:56 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From the desk of Wes Santee comes: > cvsup'd at ~1:00pm PDT June 30th. Previous commit to fix gnu info > files got it farther along, but it's still complaining. > Oops. I should mention this is 2.2.2-STABLE. Sorry. Cheers, -- ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) ( mailto:wes@bogon.net ) From owner-freebsd-hackers Mon Jun 30 15:10:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18756 for hackers-outgoing; Mon, 30 Jun 1997 15:10:45 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18749 for ; Mon, 30 Jun 1997 15:10:40 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id RAA23578 for ; Mon, 30 Jun 1997 17:10:02 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id RAA24759 for ; Mon, 30 Jun 1997 17:10:01 -0500 (CDT) Received: from lmcpc1.lmc.ericsson.se (lmcpc1.lmc.ericsson.se [142.133.17.200]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id SAA07915 for ; Mon, 30 Jun 1997 18:09:59 -0400 (EDT) Received: from sunshine (sunshine.lmc.ericsson.se [142.133.16.78]) by lmcpc1.lmc.ericsson.se (8.8.5/8.8.5) with SMTP id SAA00586 for ; Mon, 30 Jun 1997 18:11:34 -0400 (EDT) Date: Mon, 30 Jun 1997 18:09:51 -0400 (EDT) From: Samy Touati X-Sender: lmcsato@sunshine To: freebsd-hackers@freebsd.org Subject: NFS V3 is it stable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm using fbsd2.2.2 acting as a mail server with a bunch of solaris 2 client workstations. >From time to time I'm getting a read or write failure (RPC error 5). I log into the fbsd server and everything seems fine. Rebooting the solairs client seems to solve the problem for a while until it restarts again. I noticed that the used nfs is ver3, should I turn on the vers 2 nfs to be able to get a reliable nfs. For now I lost 2 mailboxes because of these errors. Is frebsd 2.2.2 a recommended nfs v3 server? Thanks. From owner-freebsd-hackers Mon Jun 30 15:42:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20217 for hackers-outgoing; Mon, 30 Jun 1997 15:42:34 -0700 (PDT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20211 for ; Mon, 30 Jun 1997 15:42:27 -0700 (PDT) Received: (from vivek@localhost) by cs.rice.edu (8.8.5/8.7.1) id RAA12342; Mon, 30 Jun 1997 17:42:20 -0500 (CDT) Date: Mon, 30 Jun 1997 17:42:20 -0500 (CDT) From: Vivek Sadananda Pai Message-Id: <199706302242.RAA12342@cs.rice.edu> To: freebsd-hackers@FreeBSD.ORG Subject: mbuf external storage Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Forgive me if you've seen this question already. I submitted it first to freebsd-stable, having somehow missed this list in the list of charters. I'm interested in mbufs with external storage, particularly when that storage is not in the form of mbufs clusters. I've examined the mbuf.h file, and the structure for external storage is: struct m_ext { caddr_t ext_buf; /* start of buffer */ void (*ext_free) /* free routine if not the usual */ __P((caddr_t, u_int)); u_int ext_size; /* size of buffer, for ext_free */ void (*ext_ref) /* add a reference to the ext object */ __P((caddr_t, u_int)); }; I also searched through old mail on this topic, and it seems that this structure used to be a lot richer, with some form of "opaque" argument (ext_arg) that could be used by whatever was allocating/freeing the external memory. Having something like this would be extremely useful in certain scenarios, and I've used it to good effect in Digital Unix. We're examining FreeBSD as a platform for doing some I/O research, and the package we want to port uses this "ext_arg" convention. Does anyone know if there are any plans of (re)including this, or if there's some reason why it was removed? Thanks, Vivek From owner-freebsd-hackers Mon Jun 30 15:44:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20298 for hackers-outgoing; Mon, 30 Jun 1997 15:44:31 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20278 for ; Mon, 30 Jun 1997 15:44:27 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id SAA22572; Mon, 30 Jun 1997 18:44:25 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA27830; Mon, 30 Jun 1997 18:44:23 -0400 Date: Mon, 30 Jun 1997 18:44:07 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Samy Touati cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Samy Touati wrote: > > Hi, > > > I'm using fbsd2.2.2 acting as a mail server with a bunch of solaris 2 > client workstations. > From time to time I'm getting a read or write failure (RPC error 5). > I log into the fbsd server and everything seems fine. > Rebooting the solairs client seems to solve the problem for a while until > it restarts again. > > I noticed that the used nfs is ver3, should I turn on the vers 2 nfs to be > able to get a reliable nfs. For now I lost 2 mailboxes because of these > errors. > Is frebsd 2.2.2 a recommended nfs v3 server? Samy, are you using NFS to mount the mail sppol directories? Since nfs locking isn't in a very good condition, it's almost guaranteed to fail. The mail directories are accessed bot for mail delivery and mail pickup, and reliable locking is a top requirement. > > Thanks. > > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 15:51:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20661 for hackers-outgoing; Mon, 30 Jun 1997 15:51:26 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20655 for ; Mon, 30 Jun 1997 15:51:23 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id PAA00212; Mon, 30 Jun 1997 15:50:40 -0700 (PDT) Date: Mon, 30 Jun 1997 15:50:39 -0700 (PDT) From: Annelise Anderson To: Wes Santee cc: hackers@FreeBSD.ORG Subject: Re: make world still broken In-Reply-To: <199706302155.OAA08657@kryten.bogon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Wes Santee wrote: > >From the desk of Wes Santee comes: > > cvsup'd at ~1:00pm PDT June 30th. Previous commit to fix gnu info > > files got it farther along, but it's still complaining. > > > > Oops. I should mention this is 2.2.2-STABLE. Sorry. > > Cheers, > -- > ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) > ( mailto:wes@bogon.net ) > I'm really glad to know it wasn't me....I got the same message trying to do a make world. I did get it to build, though, by taking the "doc" out of the subdir list in the Makefile in /usr/src/gnu/usr.bin/gdb, and then finishing it (libexec hadn't been built yet) by hand. Guess it's okay because the new kernel compiled and booted. I suppose I'm missing some gnu docs, but other than that everything should be okay? Annelise From owner-freebsd-hackers Mon Jun 30 16:34:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22096 for hackers-outgoing; Mon, 30 Jun 1997 16:34:01 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA22091 for ; Mon, 30 Jun 1997 16:33:54 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wiptx-0004EU-00; Mon, 30 Jun 1997 16:30:33 -0700 Date: Mon, 30 Jun 1997 16:30:32 -0700 (PDT) From: Tom Samplonius To: Chuck Robey cc: Samy Touati , freebsd-hackers@freebsd.org Subject: Re: NFS V3 is it stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Chuck Robey wrote: > Samy, are you using NFS to mount the mail sppol directories? Since nfs > locking isn't in a very good condition, it's almost guaranteed to fail. > The mail directories are accessed bot for mail delivery and mail pickup, > and reliable locking is a top requirement. I've had sites report that even going Solaris to Solaris using the Solaris propietary lockd stuff, they still can get trashed mailboxes. Locking of any kind over NFS just isn't reliable. Use IMAP as an alternative. Set up your mail server as a IMAP server, and use Pine, Simeon (www.esys.ca), or Netscape 4 on your clients. > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > Tom From owner-freebsd-hackers Mon Jun 30 16:44:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22595 for hackers-outgoing; Mon, 30 Jun 1997 16:44:32 -0700 (PDT) Received: from hydrogen.nike.efn.org (metriclient-8.uoregon.edu [128.223.172.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22551 for ; Mon, 30 Jun 1997 16:43:52 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id QAA01377; Mon, 30 Jun 1997 16:42:06 -0700 (PDT) Message-ID: <19970630164206.27593@hydrogen.nike.efn.org> Date: Mon, 30 Jun 1997 16:42:06 -0700 From: John-Mark Gurney To: Chuck Robey Cc: BRiGHTMN , FreeBSD-Hackers Subject: Re: mounting References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chuck Robey on Mon, Jun 30, 1997 at 04:30:02PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey scribbled this message on Jun 30: > On Thu, 12 Jun 1997, BRiGHTMN wrote: > I think I now have it figured out. Desperation does wonderful things for > the mind ... Michael Smith had told me previously about the abysmal > performance of the 3C503 card that machine has, about some buffer > incompatibility it has, and I think it's ibtten me now. I found disk > space, tarred up what I wanted to transfer, and I sent it over that way, > which worked like a charm. Means I can't get nfs mounting to work, but at > least I can get what I want up, going along. have you tried to use a smaller nfs block size?? i.e. 1k instead of the default 8k? I vaguely remeber something about that fixing some problems with the 3c503... > > > I'm trying to do an NFS mount of a directory on a 3.0 machine onto another > > > machine that's running 2.2.1, for the purpose of transferring /usr/src. I > > > can mount the 3.0 machine's /usr/src onto my (current) machine and > > > transfer files with no problem. When I do the mount onto the 2.2.1 > > > machine, the first ls works, then everything afterwards fails, and hangs. > > > I have tried, as a test, just to transfer the Makefile into another > > > directory, here's the ps from it: > > > > > > 207 p1 D 0:00.01 cp /usr/src/Makefile > > > > > > I don't understand the "D" status. All the nfsd and nfsiod's are running, > > > as is portmap and mountd, on both machines. Since I can successfully > > > mount and tranfer files from the source machine to my own, I think maybe > > > it's in the target machine (the 2.2.1 machine) that has the trouble, but I > > > can't guess what it is. Can you? > > > > > > I've tried this several times, and done some reboot cycles that seemed to > > > work just fine. I'm willing to do some experimentation ... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Jun 30 16:47:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22699 for hackers-outgoing; Mon, 30 Jun 1997 16:47:57 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22694 for ; Mon, 30 Jun 1997 16:47:53 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id SAA27846; Mon, 30 Jun 1997 18:47:20 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id SAA27202; Mon, 30 Jun 1997 18:47:19 -0500 (CDT) Received: from lmcpc1.lmc.ericsson.se (lmcpc1.lmc.ericsson.se [142.133.17.200]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id TAA09061; Mon, 30 Jun 1997 19:45:16 -0400 (EDT) Received: from orca (orca.lmc.ericsson.se [142.133.17.20]) by lmcpc1.lmc.ericsson.se (8.8.5/8.8.5) with SMTP id TAA00728; Mon, 30 Jun 1997 19:44:55 -0400 (EDT) Date: Mon, 30 Jun 1997 19:43:04 -0400 (EDT) From: Samy Touati X-Sender: lmcsato@orca To: Chuck Robey cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes I'm using the fbsd machine as a mail server: the solaris 2 workstations are mounting via nfs their mail directory from the fbsd machine. Samy On Mon, 30 Jun 1997, Chuck Robey wrote: > On Mon, 30 Jun 1997, Samy Touati wrote: > > > > > Hi, > > > > > > I'm using fbsd2.2.2 acting as a mail server with a bunch of solaris 2 > > client workstations. > > From time to time I'm getting a read or write failure (RPC error 5). > > I log into the fbsd server and everything seems fine. > > Rebooting the solairs client seems to solve the problem for a while until > > it restarts again. > > > > I noticed that the used nfs is ver3, should I turn on the vers 2 nfs to be > > able to get a reliable nfs. For now I lost 2 mailboxes because of these > > errors. > > Is frebsd 2.2.2 a recommended nfs v3 server? > > Samy, are you using NFS to mount the mail sppol directories? Since nfs > locking isn't in a very good condition, it's almost guaranteed to fail. > The mail directories are accessed bot for mail delivery and mail pickup, > and reliable locking is a top requirement. > > > > > Thanks. > > > > > > > > > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > From owner-freebsd-hackers Mon Jun 30 16:48:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22751 for hackers-outgoing; Mon, 30 Jun 1997 16:48:43 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22746 for ; Mon, 30 Jun 1997 16:48:41 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id TAA04493; Mon, 30 Jun 1997 19:48:36 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id TAA02423; Mon, 30 Jun 1997 19:48:34 -0400 Date: Mon, 30 Jun 1997 19:48:18 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: John-Mark Gurney cc: BRiGHTMN , FreeBSD-Hackers Subject: Re: mounting In-Reply-To: <19970630164206.27593@hydrogen.nike.efn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, John-Mark Gurney wrote: > Chuck Robey scribbled this message on Jun 30: > > On Thu, 12 Jun 1997, BRiGHTMN wrote: > > I think I now have it figured out. Desperation does wonderful things for > > the mind ... Michael Smith had told me previously about the abysmal > > performance of the 3C503 card that machine has, about some buffer > > incompatibility it has, and I think it's ibtten me now. I found disk > > space, tarred up what I wanted to transfer, and I sent it over that way, > > which worked like a charm. Means I can't get nfs mounting to work, but at > > least I can get what I want up, going along. > > have you tried to use a smaller nfs block size?? i.e. 1k instead of the > default 8k? I vaguely remeber something about that fixing some problems > with the 3c503... I'll try that in a little while, and report the results here. I assume that means mount -t nfs -I512 -o -r1024 -w1024 remote_machine:/path /path If there's equal signs that have to go in there, I guess I'll find out. The man page isn't clear on that. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 17:21:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24605 for hackers-outgoing; Mon, 30 Jun 1997 17:21:50 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA24593 for ; Mon, 30 Jun 1997 17:21:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA10515; Mon, 30 Jun 1997 17:18:13 -0700 From: Terry Lambert Message-Id: <199707010018.RAA10515@phaeton.artisoft.com> Subject: Re: NFS V3 is it stable? To: tom@sdf.com (Tom Samplonius) Date: Mon, 30 Jun 1997 17:18:13 -3100 (MST) Cc: chuckr@glue.umd.edu, lmcsato@lmc.ericsson.se, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 30, 97 04:30:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Samy, are you using NFS to mount the mail sppol directories? Since nfs > > locking isn't in a very good condition, it's almost guaranteed to fail. > > The mail directories are accessed bot for mail delivery and mail pickup, > > and reliable locking is a top requirement. > > I've had sites report that even going Solaris to Solaris using the > Solaris propietary lockd stuff, they still can get trashed mailboxes. > Locking of any kind over NFS just isn't reliable. This is only true if your NFS violates the NFS write guarantees, which SVR4 and Solaris do, by default. Turn off write gathering and write caching (the "adb" commands are listed in the Network Administration Manual) and the problem will go away. Note that FreeBSD's lockd doesn't enforce locking; it lies and grants the lock in all cases, mostly to shut up diskless SunOS/Solaris clients booting from FreeBSD boxes. Server locking kernel patches (rpc.lockd still needs fixes on top of them) have been available for some time now. > Use IMAP as an alternative. Set up your mail server as a IMAP server, > and use Pine, Simeon (www.esys.ca), or Netscape 4 on your clients. Netscape is a known rogue client. Among other things, it does not cache the correct seperator character on a per "#xxx" namespace escape. So if you were reading news in "#news" (seperator "."), and went to create a new mail folder, it wouldn't use "/" as the component seperator when communicating the new forlder path to the server. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jun 30 18:23:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28515 for hackers-outgoing; Mon, 30 Jun 1997 18:23:18 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA28508 for ; Mon, 30 Jun 1997 18:23:15 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Mon, 30 Jun 1997 20:22:19 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freebsd.org'" Subject: FW: /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Date: Mon, 30 Jun 1997 20:22:17 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello there! It has been pointed out to me that the following is important :-) -----grep aic7870 aic7870 $Id: aic7870.c,v 1.41.2.8 1997/03/16 07:22:03 gibbs Exp $ and----- tail -1000 debug | grep -i release Jun 27 08:53:46 kiyoko /kernel: FreeBSD 2.2.2-RELEASE #0: Sun Jun 22 04:11:17 CDT 1997 thanks again. > -----Original Message----- > From: Raul Zighelboim > Sent: Monday, June 30, 1997 12:50 PM > To: 'hackers@freebsd.org' > Subject: /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) > > > Should I worry ? > > Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:03 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:04 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:05 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:06 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > Jun 29 02:06:07 kiyoko /kernel: ahc0: WARNING no command for scb 6 > (cmdcmplt) > > The kernel is compiled with > controller ahc0 > options AHC_TAGENABLE > options AHC_ALLOW_MEMIO > > > the disk system: > > Jun 20 11:29:35 myname /kernel: ahc0 adapter> rev 0 int a irq 10 on pci0:13 > Jun 20 11:29:35 myname /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, > 16 SCBs > Jun 20 11:29:35 myname /kernel: ahc0 waiting for scsi devices to > settle > Jun 20 11:29:35 myname /kernel: ahc0: target 0 Tagged Queuing Device > Jun 20 11:29:36 myname /kernel: (ahc0:0:0): "SEAGATE ST410800W 0006" > type 0 fixed SCSI 2 > Jun 20 11:29:36 myname /kernel: sd0(ahc0:0:0): Direct-Access 8669MB > (17755614 512 byte sectors) > Jun 20 11:29:36 myname /kernel: ahc0: target 1 Tagged Queuing Device > Jun 20 11:29:36 myname /kernel: (ahc0:1:0): "SEAGATE ST410800W 0006" > type 0 fixed SCSI 2 > Jun 20 11:29:36 myname /kernel: sd1(ahc0:1:0): Direct-Access 8669MB > (17755614 512 byte sectors) > Jun 20 11:29:36 myname /kernel: ahc0: target 2 Tagged Queuing Device > Jun 20 11:29:36 myname /kernel: (ahc0:2:0): "SEAGATE ST410800W 0006" > type 0 fixed SCSI 2 > Jun 20 11:29:36 myname /kernel: sd4(ahc0:2:0): Direct-Access 8669MB > (17755614 512 byte sectors) > Jun 20 11:29:36 myname /kernel: ahc0: target 3 Tagged Queuing Device > Jun 20 11:29:36 myname /kernel: (ahc0:3:0): "Quantum XP34300W L912" > type 0 fixed SCSI 2 > Jun 20 11:29:36 myname /kernel: sd2(ahc0:3:0): Direct-Access 4303MB > (8813920 512 byte sectors) > Jun 20 11:29:36 myname /kernel: ahc0: target 4 Tagged Queuing Device > Jun 20 11:29:36 myname /kernel: (ahc0:4:0): "Quantum XP34300W L912" > type 0 fixed SCSI 2 > Jun 20 11:29:37 myname /kernel: sd3(ahc0:4:0): Direct-Access 4303MB > (8813920 512 byte sectors) > From owner-freebsd-hackers Mon Jun 30 18:50:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29912 for hackers-outgoing; Mon, 30 Jun 1997 18:50:23 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29907 for ; Mon, 30 Jun 1997 18:50:20 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA06058; Mon, 30 Jun 1997 18:46:01 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd006055; Tue Jul 1 01:45:50 1997 Message-ID: <33B860FD.31DFF4F5@whistle.com> Date: Mon, 30 Jun 1997 18:44:29 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Vivek Sadananda Pai CC: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf external storage References: <199706302242.RAA12342@cs.rice.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Vivek Sadananda Pai wrote: > I'm interested in mbufs with external storage, particularly when that > storage is not in the form of mbufs clusters. I've examined the mbuf.h > file, and the structure for external storage is: > > struct m_ext { > caddr_t ext_buf; /* start of buffer */ > void (*ext_free) /* free routine if not the usual */ > __P((caddr_t, u_int)); > u_int ext_size; /* size of buffer, for ext_free */ > void (*ext_ref) /* add a reference to the ext object */ > __P((caddr_t, u_int)); > }; Yes I added this to version 1.17 of mbuf.h this was inspired by code in the old BSD4.3 code that I needed for some applications. This was also in OSF1 which became Digital Unix. > > I also searched through old mail on this topic, and it seems that this > structure used to be a lot richer, with some form of "opaque" argument > (ext_arg) that could be used by whatever was allocating/freeing the > external memory. Having something like this would be extremely useful > in certain scenarios, and I've used it to good effect in Digital Unix. > We're examining FreeBSD as a platform for doing some I/O research, and > the package we want to port uses this "ext_arg" convention. The struct was actually not so rich. there was TALK of adding even more than I did. do a search in current and hackers using "mbuf AND external" I agree that the opaque argument would be useful. > > Does anyone know if there are any plans of (re)including this, or if > there's some reason why it was removed? It was never there. It might be useful to include it.. I just overload the 'ext_size' argument. (as nothing uses it). I wanted to do more, but was afraid of backlash :) julian From owner-freebsd-hackers Mon Jun 30 19:06:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA00662 for hackers-outgoing; Mon, 30 Jun 1997 19:06:37 -0700 (PDT) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00657 for ; Mon, 30 Jun 1997 19:06:27 -0700 (PDT) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.5/8.8.5) with ESMTP id WAA28727; Mon, 30 Jun 1997 22:05:50 -0400 (EDT) Message-Id: <199707010205.WAA28727@spooky.rwwa.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Chuck Robey cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-reply-to: Your message of "Mon, 30 Jun 1997 18:44:07 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Jun 1997 22:05:49 -0400 From: Robert Withrow Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk chuckr@glue.umd.edu said: :- Samy, are you using NFS to mount the mail sppol directories? Since :- nfs locking isn't in a very good condition, it's almost guaranteed to :- fail. The mail directories are accessed bot for mail delivery and mail :- pickup, and reliable locking is a top requirement. But... I am doing this without *any* problems with FBSD 2.1.[567], where the mail spools are served by a Solaris system. I was going to upgrade a bunch of systems to 2.2-release, but now I'm worried. IMO, This *must* be made to work at least as well as it does in 2.1.[567]. And suggesting doing this another way is a non-starter, since in this >1000 system shop, they aren't going to change things 'cause a dozen or so FreeBSD systems get gas. They barely tolerate me as it is... (Hell, I only got them to NIS-serve AMD maps because they wanted to try out AMD on some *sun* systems...) ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM From owner-freebsd-hackers Mon Jun 30 19:12:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA00947 for hackers-outgoing; Mon, 30 Jun 1997 19:12:07 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00908 for ; Mon, 30 Jun 1997 19:11:59 -0700 (PDT) Received: (from root@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id WAA04523 for hackers@freebsd.org; Mon, 30 Jun 1997 22:11:52 -0400 (EDT) Date: Mon, 30 Jun 1997 22:11:52 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707010211.WAA04523@pandora.hh.kew.com> To: hackers@freebsd.org Subject: NEC and bootable CD-ROMS Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reference to the QNX bootable floppy, my NEC Ready 9618 is quite happy to boot off the IDE CD-ROM -- the recovery CD-ROM runs DOS (gack!) to restore the hard drive back to the factory state. Any clue how standard their method is and it is worth including the proper boot blocks on the FreeBSD CD-ROM? It would be _real_ nice to be able to boot a new or toasted FreeBSD system without going into DOS Mode. I'll be happy to dump the first first blocks of the CD if an interested party sends a command line (dd?) along to have me dump it. -ahd- From owner-freebsd-hackers Mon Jun 30 19:19:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01207 for hackers-outgoing; Mon, 30 Jun 1997 19:19:13 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA01197 for ; Mon, 30 Jun 1997 19:19:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id TAA27715; Mon, 30 Jun 1997 19:15:02 -0700 (PDT) Message-Id: <199707010215.TAA27715@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Julian Elischer Cc: Vivek Sadananda Pai , freebsd-hackers@freebsd.org Subject: Re: mbuf external storage Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 30 Jun 1997 19:15:01 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997 18:44:29 -0700 Julian Elischer wrote: > > I'm interested in mbufs with external storage, particularly when that > > storage is not in the form of mbufs clusters. I've examined the mbuf.h > > file, and the structure for external storage is: > > > > struct m_ext { > > caddr_t ext_buf; /* start of buffer */ > > void (*ext_free) /* free routine if not the usual */ > > __P((caddr_t, u_int)); > > u_int ext_size; /* size of buffer, for ext_free */ > > void (*ext_ref) /* add a reference to the ext object */ > > __P((caddr_t, u_int)); > > }; > > Yes I added this to version 1.17 of mbuf.h > this was inspired by code in the old BSD4.3 code that I needed for > some applications. This was also in OSF1 which became Digital Unix. I also recommend taking a look at the external storage mbuf code in NetBSD that was done by Matt Thomas and myself. NetBSD actively uses it in the handling of UNIX domain sockets, and I'm experimenting using it for DMA buffer loan-out for high performance network interfaces (such as Myrinet and Hippi); doing this really effectively is going to require an additional function call interface to deal with the transmit case, however... that's to-be-attacked later. The reference counting scheme is done with a ring, and the (*ext_free)() function takes an additional opaque cookie for use by that routine. > > I also searched through old mail on this topic, and it seems that this > > structure used to be a lot richer, with some form of "opaque" argument > > (ext_arg) that could be used by whatever was allocating/freeing the > > external memory. Having something like this would be extremely useful > > in certain scenarios, and I've used it to good effect in Digital Unix. ...yes... a struct buf *, for a biodone() call, for example. Or a softc for a device (if you're freeing a loaned-out DMA buffer). > > We're examining FreeBSD as a platform for doing some I/O research, and > > the package we want to port uses this "ext_arg" convention. > > > > The struct was actually not so rich. > there was TALK of adding even more than I did. > > do a search in current and hackers using > "mbuf AND external" > > > I agree that the opaque argument would be useful. > > > > Does anyone know if there are any plans of (re)including this, or if > > there's some reason why it was removed? > It was never there. > It might be useful to include it.. I just overload the 'ext_size' > argument. (as nothing uses it). That's seriously bogus... ext_size _is_ used in e.g. NetBSD's NFS code, and when you think about running on 64-bit architectures (like the Alpha, which FreeBSD has ambitions about running on), then you can't resort to such a kludge. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Mon Jun 30 19:25:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01480 for hackers-outgoing; Mon, 30 Jun 1997 19:25:37 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA01475 for ; Mon, 30 Jun 1997 19:25:34 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id VAA15611; Mon, 30 Jun 1997 21:29:24 -0500 (CDT) Message-Id: <199707010229.VAA15611@iworks.InterWorks.org> Date: Mon, 30 Jun 1997 21:29:24 -0500 (CDT) From: "Daniel M. Eischen" To: hackers@freebsd.org, mango@staff.communique.net Subject: Re: FW: /kernel: ahc0: WARNING no command for scb 6 (cmdcmplt) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It has been pointed out to me that the following is important :-) > > -----grep aic7870 aic7870 > $Id: aic7870.c,v 1.41.2.8 1997/03/16 07:22:03 gibbs Exp $ ... > > Jun 20 11:29:36 myname /kernel: ahc0: target 3 Tagged Queuing Device > > Jun 20 11:29:36 myname /kernel: (ahc0:3:0): "Quantum XP34300W L912" > > type 0 fixed SCSI 2 > > Jun 20 11:29:36 myname /kernel: sd2(ahc0:3:0): Direct-Access 4303MB > > (8813920 512 byte sectors) > > Jun 20 11:29:36 myname /kernel: ahc0: target 4 Tagged Queuing Device > > Jun 20 11:29:36 myname /kernel: (ahc0:4:0): "Quantum XP34300W L912" > > type 0 fixed SCSI 2 > > Jun 20 11:29:37 myname /kernel: sd3(ahc0:4:0): Direct-Access 4303MB > > (8813920 512 byte sectors) If these drives are being accessed under FreeBSD, then you'll need firmware upgrades to take them from L912 to L915. There's a known firmware bug in these Quantum drives that cause them to return QUEUE_FULL conditions. Firmware upgrade files/tools/instructions can be found at ftp.quantum.com in /Firmware/Atlas-I. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Mon Jun 30 19:34:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01789 for hackers-outgoing; Mon, 30 Jun 1997 19:34:14 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA01783 for ; Mon, 30 Jun 1997 19:34:10 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id WAA14335; Mon, 30 Jun 1997 22:36:10 -0400 Date: Mon, 30 Jun 1997 22:36:09 -0400 (EDT) From: Ben Black To: hackers@freebsd.org Subject: sfio Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk has anyone played with sfio? it looks like a valuable replacement for stdio... http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html From owner-freebsd-hackers Mon Jun 30 19:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02106 for hackers-outgoing; Mon, 30 Jun 1997 19:38:13 -0700 (PDT) Received: from pent.vnet.net (pent.vnet.net [166.82.194.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02097 for ; Mon, 30 Jun 1997 19:38:10 -0700 (PDT) Received: (from root@localhost) by pent.vnet.net (8.8.5/8.8.5) id WAA09263; Mon, 30 Jun 1997 22:37:58 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707010211.WAA04523@pandora.hh.kew.com> Date: Mon, 30 Jun 1997 22:35:59 -0400 (EDT) From: "Adam W. Hawks" To: Drew Derbyshire Subject: RE: NEC and bootable CD-ROMS Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've duplicated whole cd's with dd if=/dev/cd0c of=/usr/cd.img You could get the boot blocks/track out like that I would think. On 01-Jul-97 Drew Derbyshire wrote: >In reference to the QNX bootable floppy, my NEC Ready 9618 is quite >happy to boot off the IDE CD-ROM -- the recovery CD-ROM runs DOS >(gack!) to restore the hard drive back to the factory state. Any >clue how standard their method is and it is worth including the >proper boot blocks on the FreeBSD CD-ROM? It would be _real_ nice >to be able to boot a new or toasted FreeBSD system without going >into DOS Mode. > >I'll be happy to dump the first first blocks of the CD if an >interested party sends a command line (dd?) along to have me dump >it. > >-ahd- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzOl6OoAAAEEALvhjGsURxeru2XemXqWy/799eZzuGJ3jM20jE2jn9teVoHq 5inbFr/m1zFJl1x41Ni0oe8qLX36ekDy1goTDyOzeFEuXnTrGBsEXvNwF4S/T6K4 8TI2o7Qm4oB3nv5m4yP7sQFDP0u8thi/LLdDyR2eb8d5OBjd7eTueZeHCNXRAAUR tCBBZGFtIFcuIEhhd2tzIDxhd2hhd2tzQHZuZXQubmV0Pg== =TVj5 -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hackers Mon Jun 30 19:48:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02543 for hackers-outgoing; Mon, 30 Jun 1997 19:48:01 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02527 for ; Mon, 30 Jun 1997 19:47:57 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id WAA03126; Mon, 30 Jun 1997 22:47:49 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id WAA12656; Mon, 30 Jun 1997 22:47:48 -0400 Date: Mon, 30 Jun 1997 22:47:30 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Robert Withrow cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-Reply-To: <199707010205.WAA28727@spooky.rwwa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Robert Withrow wrote: > > chuckr@glue.umd.edu said: > :- Samy, are you using NFS to mount the mail sppol directories? Since > :- nfs locking isn't in a very good condition, it's almost guaranteed to > :- fail. The mail directories are accessed bot for mail delivery and mail > :- pickup, and reliable locking is a top requirement. > > But... I am doing this without *any* problems with FBSD 2.1.[567], where the > mail spools are served by a Solaris system. I was going to upgrade > a bunch of systems to 2.2-release, but now I'm worried. IMO, This *must* > be made to work at least as well as it does in 2.1.[567]. > > And suggesting doing this another way is a non-starter, since in this > >1000 system shop, they aren't going to change things 'cause a dozen or > so FreeBSD systems get gas. They barely tolerate me as it is... > > (Hell, I only got them to NIS-serve AMD maps because they wanted to try > out AMD on some *sun* systems...) I don't know what to say to you. Must have been working by a freak timing accident. > ----------------------------------------------------------------------------- > Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 19:54:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02844 for hackers-outgoing; Mon, 30 Jun 1997 19:54:22 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA02837 for ; Mon, 30 Jun 1997 19:54:19 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wit1v-0004K5-00; Mon, 30 Jun 1997 19:50:59 -0700 Date: Mon, 30 Jun 1997 19:50:58 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: chuckr@glue.umd.edu, lmcsato@lmc.ericsson.se, freebsd-hackers@freebsd.org Subject: Re: NFS V3 is it stable? In-Reply-To: <199707010018.RAA10515@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Terry Lambert wrote: > > I've had sites report that even going Solaris to Solaris using the > > Solaris propietary lockd stuff, they still can get trashed mailboxes. > > Locking of any kind over NFS just isn't reliable. > > This is only true if your NFS violates the NFS write guarantees, > which SVR4 and Solaris do, by default. Turn off write gathering > and write caching (the "adb" commands are listed in the Network > Administration Manual) and the problem will go away. So you make a trade reliable locking for performance? I'd take performance any day, and just forget about exporting mailboxes. ... > > Use IMAP as an alternative. Set up your mail server as a IMAP server, > > and use Pine, Simeon (www.esys.ca), or Netscape 4 on your clients. > > Netscape is a known rogue client. Among other things, it does not > cache the correct seperator character on a per "#xxx" namespace > escape. So if you were reading news in "#news" (seperator "."), > and went to create a new mail folder, it wouldn't use "/" as the > component seperator when communicating the new forlder path to the > server. Works with the Cyrus server, which is all I care about. I don't think the imap spec hides enougth server implementation details, which makes clients overly complex. > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom From owner-freebsd-hackers Mon Jun 30 20:00:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03149 for hackers-outgoing; Mon, 30 Jun 1997 20:00:39 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03144 for ; Mon, 30 Jun 1997 20:00:36 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA07901; Mon, 30 Jun 1997 19:54:01 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd007884; Tue Jul 1 02:53:56 1997 Message-ID: <33B870F3.2F1CF0FB@whistle.com> Date: Mon, 30 Jun 1997 19:52:35 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jason Thorpe CC: Vivek Sadananda Pai , freebsd-hackers@freebsd.org Subject: Re: mbuf external storage References: <199707010215.TAA27715@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe wrote: > > I also recommend taking a look at the external storage mbuf code in > NetBSD that was done by Matt Thomas and myself. NetBSD actively uses > it in the handling of UNIX domain sockets, and I'm experimenting using > it for DMA buffer loan-out for high performance network interfaces > (such as Myrinet and Hippi); doing this really effectively is going > to require an additional function call interface to deal with the > transmit case, however... that's to-be-attacked later. I agrree that the OSF idea has merrit. it's also possible to make a hybrid scheme that allows even more flexibility. (I had code for that somewhere..) > > > there's some reason why it was removed? > > It was never there. > > It might be useful to include it.. I just overload the 'ext_size' > > argument. (as nothing uses it). > > That's seriously bogus... ext_size _is_ used in e.g. NetBSD's NFS code, > and when you think about running on 64-bit architectures (like the > Alpha, which FreeBSD has ambitions about running on), then you can't > resort to such a kludge. > > Jason I agree and it was a temporary 'kludge'. in special purpose code that will get rewritten eventually. From owner-freebsd-hackers Mon Jun 30 20:17:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03823 for hackers-outgoing; Mon, 30 Jun 1997 20:17:39 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03816 for ; Mon, 30 Jun 1997 20:17:36 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA09663; Mon, 30 Jun 1997 23:17:32 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA15067; Mon, 30 Jun 1997 23:17:19 -0400 Date: Mon, 30 Jun 1997 23:16:59 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Ben Black cc: hackers@FreeBSD.ORG Subject: Re: sfio In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Ben Black wrote: > has anyone played with sfio? it looks like a valuable replacement for > stdio... > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html > Nice to look at, but for something that's so very pivotally important to nearly everything, I think some more experience with it is needed. > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 20:34:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04580 for hackers-outgoing; Mon, 30 Jun 1997 20:34:34 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04575 for ; Mon, 30 Jun 1997 20:34:30 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA24404; Mon, 30 Jun 1997 20:32:41 -0700 (PDT) To: Robert Withrow cc: Chuck Robey , freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-reply-to: Your message of "Mon, 30 Jun 1997 22:05:49 EDT." <199707010205.WAA28727@spooky.rwwa.com> Date: Mon, 30 Jun 1997 20:32:41 -0700 Message-ID: <24401.867727961@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But... I am doing this without *any* problems with FBSD 2.1.[567], where the > mail spools are served by a Solaris system. I was going to upgrade > a bunch of systems to 2.2-release, but now I'm worried. IMO, This *must* > be made to work at least as well as it does in 2.1.[567]. It never worked at all, not in 2.1.[67] or now, so your degree of risk is essentially the same. We've been waiting forever for someone to take an active enough interest in this to implement an NFS locking daemon. We're still waiting. ;) Jordan P.S. Terry sent me the skeleton of something way back when I was actually masochistically considering this myself, but I came to my senses and backed away in time. :) From owner-freebsd-hackers Mon Jun 30 20:53:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05666 for hackers-outgoing; Mon, 30 Jun 1997 20:53:27 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05655 for ; Mon, 30 Jun 1997 20:53:25 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id XAA15744; Mon, 30 Jun 1997 23:55:23 -0400 Date: Mon, 30 Jun 1997 23:55:22 -0400 (EDT) From: Ben Black To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: sfio In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk as i said, *looks* like a valuable replacement. i think it is worth investigating further. my experience has been it is faster than stdio. also, the sfdesc library is *very* nice. On Mon, 30 Jun 1997, Chuck Robey wrote: > On Mon, 30 Jun 1997, Ben Black wrote: > > > has anyone played with sfio? it looks like a valuable replacement for > > stdio... > > > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html > > > > Nice to look at, but for something that's so very pivotally important to > nearly everything, I think some more experience with it is needed. > > > > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > From owner-freebsd-hackers Mon Jun 30 21:10:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06651 for hackers-outgoing; Mon, 30 Jun 1997 21:10:21 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06630 for ; Mon, 30 Jun 1997 21:10:17 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id AAA20649; Tue, 1 Jul 1997 00:10:14 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id AAA17500; Tue, 1 Jul 1997 00:10:12 -0400 Date: Tue, 1 Jul 1997 00:09:56 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Ben Black cc: hackers@FreeBSD.ORG Subject: Re: sfio In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Ben Black wrote: > as i said, *looks* like a valuable replacement. i think it is worth > investigating further. my experience has been it is faster than stdio. > also, the sfdesc library is *very* nice. I'm just wary of exchanging a knows set of bugs for an unknown set. If you have comments on it, I'd be really interested in that. > > On Mon, 30 Jun 1997, Chuck Robey wrote: > > > On Mon, 30 Jun 1997, Ben Black wrote: > > > > > has anyone played with sfio? it looks like a valuable replacement for > > > stdio... > > > > > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html > > > > > > > Nice to look at, but for something that's so very pivotally important to > > nearly everything, I think some more experience with it is needed. > > > > > > > > > > > > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > > (301) 220-2114 | version 3.0 current -- and great FUN! > > ----------------------------+----------------------------------------------- > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 30 22:11:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08996 for hackers-outgoing; Mon, 30 Jun 1997 22:11:02 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA08990 for ; Mon, 30 Jun 1997 22:10:57 -0700 (PDT) Received: from rain (portC7.bonn-online.com [195.52.214.78]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id HAA08089 for ; Tue, 1 Jul 1997 07:10:38 +0200 Message-ID: <33B89142.41C67EA6@bonn-online.com> Date: Tue, 01 Jul 1997 07:10:26 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: NFS V3 is it stable? References: <24401.867727961@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > But... I am doing this without *any* problems with FBSD 2.1.[567], where the > > mail spools are served by a Solaris system. I was going to upgrade > > a bunch of systems to 2.2-release, but now I'm worried. IMO, This *must* > > be made to work at least as well as it does in 2.1.[567]. > > It never worked at all, not in 2.1.[67] or now, so your degree of risk > is essentially the same. > > We've been waiting forever for someone to take an active enough interest > in this to implement an NFS locking daemon. We're still waiting. ;) > > Jordan > > P.S. Terry sent me the skeleton of something way back when I was > actually masochistically considering this myself, but I came to > my senses and backed away in time. :) What would be the requirements for this ? It does not seem too complicated to me, at least the rpc.lockd framework is already in place. So the "only" thing left to do would be to manage lists of locks from a set of hosts and processes, probably merging adjacent locks etc, and using the F_RSETLK fcntls to actually set the locks in the kernel. Probably the interaction with rpc.statd would also need some attention. Or am I grossly missing something? If not, then I could probably spend some time to work on this, if nobody else is already doing it. From owner-freebsd-hackers Mon Jun 30 23:19:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11350 for hackers-outgoing; Mon, 30 Jun 1997 23:19:18 -0700 (PDT) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.202]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11336 for ; Mon, 30 Jun 1997 23:19:08 -0700 (PDT) Received: (from root@localhost) by innocence.interface-business.de (8.6.11/8.6.9) with UUCP id IAA25368; Tue, 1 Jul 1997 08:16:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA04701; Tue, 1 Jul 1997 07:37:39 +0200 (MET DST) Message-ID: <19970701073739.TT45372@uriah.heep.sax.de> Date: Tue, 1 Jul 1997 07:37:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-Hackers@FreeBSD.ORG (FreeBSD-Hackers) Cc: chuckr@glue.umd.edu (Chuck Robey) Subject: Re: mounting References: <19970630164206.27593@hydrogen.nike.efn.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on Jun 30, 1997 19:48:18 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > mount -t nfs -I512 -o -r1024 -w1024 remote_machine:/path /path > > If there's equal signs that have to go in there, I guess I'll find out. > The man page isn't clear on that. The -I is IMHO unnecessary. However, you ought to group -o options by commas: mount [-t nfs] -o -r1024,-w1024 remote:/path /path The -t nfs is not really required. The -w1024 ain't required either, since your machine with the slow card is of course allowed to send full packets. It's only that it can't receive a full 8 KB NFS packet. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jun 30 23:19:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11391 for hackers-outgoing; Mon, 30 Jun 1997 23:19:43 -0700 (PDT) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.202]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11377 for ; Mon, 30 Jun 1997 23:19:37 -0700 (PDT) Received: (from root@localhost) by innocence.interface-business.de (8.6.11/8.6.9) with UUCP id IAA25371; Tue, 1 Jul 1997 08:17:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA04737; Tue, 1 Jul 1997 07:50:06 +0200 (MET DST) Message-ID: <19970701075006.MG05597@uriah.heep.sax.de> Date: Tue, 1 Jul 1997 07:50:06 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: ahd@kew.com (Drew Derbyshire) Cc: hackers@FreeBSD.ORG Subject: Re: NEC and bootable CD-ROMS References: <199707010211.WAA04523@pandora.hh.kew.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707010211.WAA04523@pandora.hh.kew.com>; from Drew Derbyshire on Jun 30, 1997 22:11:52 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Drew Derbyshire wrote: > Any > clue how standard their method is and it is worth including the > proper boot blocks on the FreeBSD CD-ROM? It's a little more than just a few blocks of a CD. There's a so- called standard called `El Torito'. Once you dig into it, you'll learn that it's basically the same sort of crappy definitions you can find all over the place in the PeeCee world. They went great lengths about totally unimportant things, forgot quite a number of very important things, and finally, you won't ever find a vendor who's even implementing everything that's standardized I) at all, and II) correctly. Making a bootable installation CD-ROM is not too difficult, and Jordan did it for FreeBSD >= 2.2.1. Making a bootable `generic filesystem' CD-ROM turned out to be more trouble, and i've still not yet finished debugging all the work in this area i did so far. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jun 30 23:20:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11603 for hackers-outgoing; Mon, 30 Jun 1997 23:20:43 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11593 for ; Mon, 30 Jun 1997 23:20:37 -0700 (PDT) Received: from axon.axnet.com (axnet.com [207.153.100.2]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id XAA16800 for ; Mon, 30 Jun 1997 23:20:26 -0700 (PDT) X-ROUTED: Tue, 1 Jul 1997 01:16:06 -0400 Received: from purple.axnet.com [207.153.100.27] by axon.axnet.com with smtp id ABAPDAEB ; Tue, 1 Jul 1997 01:15:48 -0400 Message-ID: <33B89F80.3B54E2CD@email.com> Date: Tue, 01 Jul 1997 01:11:13 -0500 From: purple X-Mailer: Mozilla 4.0 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: to join the mail list X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk who: me what: i want to suscribe to the mail list.(Please..., I'll be nice>) where:Purple@axon.axnet.com when: at your convinence How: you know what to do Why: because I know you like me.. -purple purple@axon.axnet.com From owner-freebsd-hackers Mon Jun 30 23:21:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11703 for hackers-outgoing; Mon, 30 Jun 1997 23:21:43 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11690 for ; Mon, 30 Jun 1997 23:21:38 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA26580; Mon, 30 Jun 1997 23:21:10 -0700 (PDT) To: Sebastian Lederer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-reply-to: Your message of "Tue, 01 Jul 1997 07:10:26 +0200." <33B89142.41C67EA6@bonn-online.com> Date: Mon, 30 Jun 1997 23:21:09 -0700 Message-ID: <26576.867738069@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What would be the requirements for this ? It does not seem too > complicated to me, at least the rpc.lockd framework is already in place. > So the "only" thing left to do would be to manage lists of locks from a > set of hosts and processes, probably merging adjacent locks etc, and > using the F_RSETLK fcntls to actually set the locks in the kernel. > Probably the interaction with rpc.statd would also need some attention. > Or am I grossly missing something? No, that sounds about right (without giving it a lot of thought - what happens on locker death, for example? I'm sure once you actually start in on this, you will find lots of amusing corner cases. :-). > If not, then I could probably spend some time to work on this, if nobody > else is already doing it. That would be great! Many would be those who would kiss your feet for doing such a thing. :-) Jordan From owner-freebsd-hackers Mon Jun 30 23:31:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12761 for hackers-outgoing; Mon, 30 Jun 1997 23:31:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA12755 for ; Mon, 30 Jun 1997 23:31:17 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA29699; Tue, 1 Jul 1997 16:00:13 +0930 (CST) From: Michael Smith Message-Id: <199707010630.QAA29699@genesis.atrad.adelaide.edu.au> Subject: Re: Tcl loadable packages In-Reply-To: from Narvi at "Jun 29, 97 10:58:17 pm" To: narvi@haldjas.folklore.ee (Narvi) Date: Tue, 1 Jul 1997 16:00:12 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG, hasty@rah.star-gate.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Narvi stands accused of saying: > > I included the to-be port as an attacment. It currently installs the > script (one line :-)) in ${PREFIX}/libdata. > > as for ../lib/tcl/site_tcl/..., it seems a bit unnceesarily too long. It's not really unnecessarily long; there should be one entry in lib for all the tcl stuff. You could argue that lib/tcl/pkgname would be adequate. > All of these would contain a mandatory load script (named just load?) that > would load the appropriate package (and possibly any dependancies). load, or pkgname_load (the latter would be more friendly) would be OK. > Version dependance - well, there realy is not much we can do. We could, of > course, have the load files have ineligence enough to load the right > library if present (but if not, etc.) Either that or usr lib/tcl/packages; install the package for the version it's built for... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jul 1 00:31:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA15681 for hackers-outgoing; Tue, 1 Jul 1997 00:31:08 -0700 (PDT) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA15676 for ; Tue, 1 Jul 1997 00:31:04 -0700 (PDT) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.6/8.7.3) id JAA00906 for freebsd-hackers@FreeBSD.ORG; Tue, 1 Jul 1997 09:30:57 +0200 (MET DST) From: Holm Tiffe Message-Id: <199707010730.JAA00906@magnet.geophysik.tu-freiberg.de> Subject: quad ints implemented ? To: freebsd-hackers@FreeBSD.ORG Date: Tue, 1 Jul 1997 09:30:56 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I've tried to get postgreSQL V6.1 working with the int8 package on -current. It seems that FreeBSD has not jet fully implemented the 64bit int in the stdio library, %q is not documented. It works for printf(3), but scanf fails. Is anyone working on this ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Strasse der Einheit 26 * * 09599 Freiberg Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* From owner-freebsd-hackers Tue Jul 1 01:17:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA17979 for hackers-outgoing; Tue, 1 Jul 1997 01:17:56 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17974 for ; Tue, 1 Jul 1997 01:17:48 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id SAA18413; Tue, 1 Jul 1997 18:17:16 +1000 (EST) Date: Tue, 1 Jul 1997 18:17:15 +1000 (EST) From: "Daniel O'Callaghan" To: Holm Tiffe cc: freebsd-hackers@FreeBSD.ORG Subject: Re: quad ints implemented ? In-Reply-To: <199707010730.JAA00906@magnet.geophysik.tu-freiberg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, Holm Tiffe wrote: > I've tried to get postgreSQL V6.1 working with the int8 package on -current. > It seems that FreeBSD has not jet fully implemented the 64bit int in the > stdio library, %q is not documented. It works for printf(3), but scanf fails. Yes, I've noticed this, too. Danny From owner-freebsd-hackers Tue Jul 1 01:26:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18356 for hackers-outgoing; Tue, 1 Jul 1997 01:26:07 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18351 for ; Tue, 1 Jul 1997 01:26:04 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id EAA20655; Tue, 1 Jul 1997 04:28:00 -0400 Date: Tue, 1 Jul 1997 04:27:59 -0400 (EDT) From: Ben Black To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: sfio In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i will comment to the list when i have more experience with it. looks good so far. On Tue, 1 Jul 1997, Chuck Robey wrote: > On Mon, 30 Jun 1997, Ben Black wrote: > > > as i said, *looks* like a valuable replacement. i think it is worth > > investigating further. my experience has been it is faster than stdio. > > also, the sfdesc library is *very* nice. > > I'm just wary of exchanging a knows set of bugs for an unknown set. If > you have comments on it, I'd be really interested in that. > > > > > On Mon, 30 Jun 1997, Chuck Robey wrote: > > > > > On Mon, 30 Jun 1997, Ben Black wrote: > > > > > > > has anyone played with sfio? it looks like a valuable replacement for > > > > stdio... > > > > > > > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html > > > > > > > > > > Nice to look at, but for something that's so very pivotally important to > > > nearly everything, I think some more experience with it is needed. > > > > > > > > > > > > > > > > > > > > > ----------------------------+----------------------------------------------- > > > Chuck Robey | Interests include any kind of voice or data > > > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > > > 213 Lakeside Drive Apt T-1 | > > > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > > > (301) 220-2114 | version 3.0 current -- and great FUN! > > > ----------------------------+----------------------------------------------- > > > > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > From owner-freebsd-hackers Tue Jul 1 01:32:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18639 for hackers-outgoing; Tue, 1 Jul 1997 01:32:10 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18634 for ; Tue, 1 Jul 1997 01:32:05 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id KAA01748; Tue, 1 Jul 1997 10:30:55 +0200 (MET DST) Date: Tue, 1 Jul 1997 10:30:54 +0200 (MET DST) From: Andrzej Bialecki To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: <199706301717.TAA12131@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Luigi Rizzo wrote: > Apologies if this is off topic, but I found this on the news, and it > sounds interesting. I haven't been able to try it because the site is > quite slow from here. I tried it - their dealer had this demo on his server in Poland. Well, to be frank - it's really, really COOOLLL. It's probably impossible with Xfree86 size to beat this as a whole. BUT, perhaps this is a neat idea to make a FreeBSD demo disk, only using the libdialog instead. Or, to make it a "2,88 Mbyte Web Challenge" for free Unices. :-) I mean it. Such a demo disk would be very helpful for those, who want FreeBSD give a try. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Tue Jul 1 01:35:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18835 for hackers-outgoing; Tue, 1 Jul 1997 01:35:28 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18830 for ; Tue, 1 Jul 1997 01:35:24 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id SAA12740; Tue, 1 Jul 1997 18:35:03 +1000 (EST) Message-ID: <19970701183503.31861@rf900.physics.usyd.edu.au> Date: Tue, 1 Jul 1997 18:35:03 +1000 From: David Dawes To: Holm Tiffe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: quad ints implemented ? References: <199707010730.JAA00906@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199707010730.JAA00906@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Tue, Jul 01, 1997 at 09:30:56AM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jul 01, 1997 at 09:30:56AM +0200, Holm Tiffe wrote: >I've tried to get postgreSQL V6.1 working with the int8 package on -current. >It seems that FreeBSD has not jet fully implemented the 64bit int in the >stdio library, %q is not documented. It works for printf(3), but scanf fails. >Is anyone working on this ? I submitted a pr (bin/2080) with a fix for this a while ago. David From owner-freebsd-hackers Tue Jul 1 02:04:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19883 for hackers-outgoing; Tue, 1 Jul 1997 02:04:01 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19867 for ; Tue, 1 Jul 1997 02:03:56 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id TAA12846; Tue, 1 Jul 1997 19:03:53 +1000 (EST) Message-ID: <19970701190353.50830@rf900.physics.usyd.edu.au> Date: Tue, 1 Jul 1997 19:03:53 +1000 From: David Dawes To: hackers@freebsd.org Subject: Determining FreeBSD versions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As of X11R6.3, imake parses the output of 'uname -r' to automatically set the OSMajorVersion, OSMinorVersion and OSTeenyVersion parameters. I recently updated a box with 2.1.7.1 to the latest on the RELENG_2_1_0 branch, and as a consequence, 'uname -r' now reports "2.1-STABLE" rather than "2.1.7.1-RELEASE". This results in imake setting OSTeenyVersion to 0 rather than 7, and this does make a difference with the current FreeBSD.cf. Is there a better way to reliably distinguish between versions, particularly the vintage of one of the "-STABLE" versions? The imake config allows these version parameters to be manually overriden, and that's what I'm doing for now. It would be good if the auto-detect mechanism could be made to work in this case though. I don't mind so much about -CURRENT, since that's known to be more of a moving target. David From owner-freebsd-hackers Tue Jul 1 03:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA22800 for hackers-outgoing; Tue, 1 Jul 1997 03:21:33 -0700 (PDT) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.132.209]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22793 for ; Tue, 1 Jul 1997 03:21:25 -0700 (PDT) Received: from negara.fokus.gmd.de (negara [193.175.132.101]) by mailhub.fokus.gmd.de (8.8.6/8.8.6) with ESMTP id MAA28439 for ; Tue, 1 Jul 1997 12:21:21 +0200 (MET DST) From: Joerg Micheel Received: (jbm@localhost) by negara.fokus.gmd.de (SMI-8.6/8.6.12) id MAA18509 for hackers@freebsd.org; Tue, 1 Jul 1997 12:20:45 +0200 Date: Tue, 1 Jul 1997 12:20:45 +0200 Message-Id: <199707011020.MAA18509@negara.fokus.gmd.de > To: hackers@freebsd.org Subject: PDP-11 UNIX source licenses Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, the history of making UNIX freely available is old, but I thought hackers@freebsd might be a community to look for fellows of Warren Toomey's initiative to get V1-7 source code licenses from SCO for personal use. So, if you are interested, please take a look at: http://minnie.cs.adfa.oz.au/PUPS/petition.html Thanks, Joerg From owner-freebsd-hackers Tue Jul 1 03:49:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA23746 for hackers-outgoing; Tue, 1 Jul 1997 03:49:40 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA23741 for ; Tue, 1 Jul 1997 03:49:37 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id LAA19913 for ; Tue, 1 Jul 1997 11:49:34 +0100 (BST) Date: Tue, 1 Jul 1997 11:49:34 +0100 (BST) From: Stephen Roome To: freebsd-hackers@freebsd.org Subject: compilation fails.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When trying to make world on 3.0-970618-SNAP with 2 CPU's, (apparently working fine) I always get this error, although sometimes cc1 dies with signal 10 instead. -- cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 -- This is from a compile of a fairly standard kernel on 2.2.2-RELEASE... -- cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 -- This isn't reliably faulty either, I don't usually get the fun of having it die on exactly the same bit of code either, some times it will compile, some times it won't. That sounds hardware related, but the hardware on the SMP system worked for about over a month from cvsup of smp (no fixed date sorry.) but without a single error, and when I had no problem with 3.0-970209-SNAP on the other box for the same period of time. Both these systems are using gcc 2.7.2.1, but so is the my workstation which is 3.0-970209-SNAP, and hasn't failed to compile anything since I installed it in early February. I originally thought this was an SMP related issue but now I am seeing it on a 2.2.2 box I'm really starting to worry. I'd send-pr, but I haven't the faintest idea of what category this would go in and I don't think it's a gnu thing. So what's changed since 9 February in -current and gone into 2.2.2 that could give me mad signal all over the place. Can anyone either verify that this is happening, or explain how to stop it, or have any solutions on tracing it, or anything. Many Thanks. -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-hackers Tue Jul 1 05:44:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27837 for hackers-outgoing; Tue, 1 Jul 1997 05:44:11 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27830 for ; Tue, 1 Jul 1997 05:44:08 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id OAA14341; Tue, 1 Jul 1997 14:43:43 +0200 (MET DST) Date: Tue, 1 Jul 1997 14:43:43 +0200 (MET DST) Message-Id: <199707011243.OAA14341@bitbox.follo.net> From: Eivind Eklund To: David Dawes CC: hackers@FreeBSD.ORG In-reply-to: David Dawes's message of Tue, 1 Jul 1997 19:03:53 +1000 Subject: Re: Determining FreeBSD versions References: <19970701190353.50830@rf900.physics.usyd.edu.au> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Is there a better way to reliably distinguish between versions, > particularly the vintage of one of the "-STABLE" versions? The imake > config allows these version parameters to be manually overriden, and > that's what I'm doing for now. It would be good if the auto-detect > mechanism could be made to work in this case though. I don't mind so > much about -CURRENT, since that's known to be more of a moving target. /usr/include/osreldate.h should be fairly easy to parse, and give very good data, especially after the format was fixed :) Eivind. From owner-freebsd-hackers Tue Jul 1 06:16:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA29300 for hackers-outgoing; Tue, 1 Jul 1997 06:16:17 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA29295 for ; Tue, 1 Jul 1997 06:16:11 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id XAA13296; Tue, 1 Jul 1997 23:15:48 +1000 (EST) Message-ID: <19970701231548.62722@rf900.physics.usyd.edu.au> Date: Tue, 1 Jul 1997 23:15:48 +1000 From: David Dawes To: Eivind Eklund Cc: hackers@FreeBSD.ORG Subject: Re: Determining FreeBSD versions References: <19970701190353.50830@rf900.physics.usyd.edu.au> <199707011243.OAA14341@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199707011243.OAA14341@bitbox.follo.net>; from Eivind Eklund on Tue, Jul 01, 1997 at 02:43:43PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jul 01, 1997 at 02:43:43PM +0200, Eivind Eklund wrote: >> >> Is there a better way to reliably distinguish between versions, >> particularly the vintage of one of the "-STABLE" versions? The imake >> config allows these version parameters to be manually overriden, and >> that's what I'm doing for now. It would be good if the auto-detect >> mechanism could be made to work in this case though. I don't mind so >> much about -CURRENT, since that's known to be more of a moving target. > >/usr/include/osreldate.h should be fairly easy to parse, and give very >good data, especially after the format was fixed :) OK, I think that will do what I need. David From owner-freebsd-hackers Tue Jul 1 08:30:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA04167 for hackers-outgoing; Tue, 1 Jul 1997 08:30:10 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA04162 for ; Tue, 1 Jul 1997 08:30:07 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wj4qy-00069K-00; Tue, 1 Jul 1997 09:28:29 -0600 To: "Daniel O'Callaghan" Subject: Re: quad ints implemented ? Cc: Holm Tiffe , freebsd-hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 18:17:15 +1000." References: Date: Tue, 01 Jul 1997 09:28:28 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message "Daniel O'Callaghan" writes: : > I've tried to get postgreSQL V6.1 working with the int8 package on -current. : > It seems that FreeBSD has not jet fully implemented the 64bit int in the : > stdio library, %q is not documented. It works for printf(3), but scanf fails. : : Yes, I've noticed this, too. I've also noticed that things liked %lld and %llu don't work on FreeBSD. This is from code ported from Solaris. Waht, if anything, does the standard have to say on this? And would people object if I implemented %ll as a long long modifier? Warner From owner-freebsd-hackers Tue Jul 1 08:32:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA04252 for hackers-outgoing; Tue, 1 Jul 1997 08:32:03 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA04219 for ; Tue, 1 Jul 1997 08:32:00 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wj4rw-00069T-00; Tue, 1 Jul 1997 09:29:28 -0600 To: Andrzej Bialecki Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) Cc: Luigi Rizzo , hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 10:30:54 +0200." References: Date: Tue, 01 Jul 1997 09:29:28 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Andrzej Bialecki writes: : BUT, perhaps this is a neat idea to make a FreeBSD demo disk, only using : the libdialog instead. Or, to make it a "2,88 Mbyte Web Challenge" for : free Unices. :-) Heck, with the number of JAZ and ZIP drives out there, why limit yourself to 2.88M :-) Warner From owner-freebsd-hackers Tue Jul 1 08:33:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA04326 for hackers-outgoing; Tue, 1 Jul 1997 08:33:35 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA04321 for ; Tue, 1 Jul 1997 08:33:31 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wj4vd-0006AC-00; Tue, 1 Jul 1997 09:33:17 -0600 To: David Dawes Subject: Re: Determining FreeBSD versions Cc: hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 19:03:53 +1000." <19970701190353.50830@rf900.physics.usyd.edu.au> References: <19970701190353.50830@rf900.physics.usyd.edu.au> Date: Tue, 01 Jul 1997 09:33:17 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970701190353.50830@rf900.physics.usyd.edu.au> David Dawes writes: : branch, and as a consequence, 'uname -r' now reports "2.1-STABLE" rather Hmmm. Why not report 2.1.x-STABLE? Where x is incremented whenever a release happens. Then people know that things are newer than 2.1.x or 2.2.x or whatever. I'm not completely sure that parsing osversion.h (or is that osreldate.h) is the right answer here. Warner From owner-freebsd-hackers Tue Jul 1 08:52:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05286 for hackers-outgoing; Tue, 1 Jul 1997 08:52:07 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05281 for ; Tue, 1 Jul 1997 08:52:05 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA21748; Tue, 1 Jul 1997 09:48:14 -0600 (MDT) Date: Tue, 1 Jul 1997 09:48:14 -0600 (MDT) Message-Id: <199707011548.JAA21748@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Robert Withrow Cc: Chuck Robey , freebsd-hackers@freebsd.org Subject: Re: NFS V3 is it stable? In-Reply-To: <199707010205.WAA28727@spooky.rwwa.com> References: <199707010205.WAA28727@spooky.rwwa.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > chuckr@glue.umd.edu said: > :- Samy, are you using NFS to mount the mail sppol directories? Since > :- nfs locking isn't in a very good condition, it's almost guaranteed to > :- fail. The mail directories are accessed bot for mail delivery and mail > :- pickup, and reliable locking is a top requirement. > > But... I am doing this without *any* problems with FBSD 2.1.[567], where the > mail spools are served by a Solaris system. I was going to upgrade > a bunch of systems to 2.2-release, but now I'm worried. IMO, This *must* > be made to work at least as well as it does in 2.1.[567]. You're simply lucky in this case. You may/may not have problems, because I have *no* idea why it works the way it's configured now. There is no locking in older versions of FreeBSD, and as been pointed out in the past NFS locking is broken in almost every version of Unix out there, including most releases SUN has made. Nate From owner-freebsd-hackers Tue Jul 1 09:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA07253 for hackers-outgoing; Tue, 1 Jul 1997 09:32:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA07223 for ; Tue, 1 Jul 1997 09:31:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA18500; Tue, 1 Jul 1997 09:28:10 -0700 From: Terry Lambert Message-Id: <199707011628.JAA18500@phaeton.artisoft.com> Subject: Re: NFS V3 is it stable? To: tom@sdf.com (Tom Samplonius) Date: Tue, 1 Jul 1997 09:28:10 -0700 (MST) Cc: terry@lambert.org, chuckr@glue.umd.edu, lmcsato@lmc.ericsson.se, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 30, 97 07:50:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I've had sites report that even going Solaris to Solaris using the > > > Solaris propietary lockd stuff, they still can get trashed mailboxes. > > > Locking of any kind over NFS just isn't reliable. > > > > This is only true if your NFS violates the NFS write guarantees, > > which SVR4 and Solaris do, by default. Turn off write gathering > > and write caching (the "adb" commands are listed in the Network > > Administration Manual) and the problem will go away. > > So you make a trade reliable locking for performance? I'd take > performance any day, and just forget about exporting mailboxes. No, you make a trade: reliable data commits for any software which requires them (CVS, databases, etc.) for "performance". Note the quotation marks: I can make any software run as fast as you want me to make it run, so long as it doesn't have to work. > > Netscape is a known rogue client. Among other things, it does not > > cache the correct seperator character on a per "#xxx" namespace > > escape. So if you were reading news in "#news" (seperator "."), > > and went to create a new mail folder, it wouldn't use "/" as the > > component seperator when communicating the new forlder path to the > > server. > > Works with the Cyrus server, which is all I care about. > I don't think the imap spec hides enougth server implementation details, > which makes clients overly complex. Well, the Cyrus server doesn't handle namespaces other than the mailbox namespace, so it's not an issue. IMAP4 *does* hide a number of things from the client, like the requirement that the client implement MIME, or that the client implement a ".newsrc" for article "seen/not seen" marking in the #news namespace, etc.. The most annoying thing is the parenthetical presentation of headers in the "FETCH" command. Mostly, I'd say it hides different things than previous specifiactions. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 09:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA07944 for hackers-outgoing; Tue, 1 Jul 1997 09:45:43 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA07939 for ; Tue, 1 Jul 1997 09:45:41 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA18554; Tue, 1 Jul 1997 09:43:45 -0700 From: Terry Lambert Message-Id: <199707011643.JAA18554@phaeton.artisoft.com> Subject: Re: sfio To: black@zen.cypher.net (Ben Black) Date: Tue, 1 Jul 1997 09:43:45 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Ben Black" at Jun 30, 97 10:36:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > has anyone played with sfio? it looks like a valuable replacement for > stdio... > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html It isn't significantly faster on FreeBSD because of the cache unification making normal I/O faster. Last time I checked, there were still a couple of coherency problems (missing msync() calls, if I recall correctly). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 10:02:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA08539 for hackers-outgoing; Tue, 1 Jul 1997 10:02:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA08534 for ; Tue, 1 Jul 1997 10:02:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA18573; Tue, 1 Jul 1997 09:58:25 -0700 From: Terry Lambert Message-Id: <199707011658.JAA18573@phaeton.artisoft.com> Subject: Re: NFS V3 is it stable? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Jul 1997 09:58:25 -0700 (MST) Cc: witr@rwwa.com, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <24401.867727961@time.cdrom.com> from "Jordan K. Hubbard" at Jun 30, 97 08:32:41 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We've been waiting forever for someone to take an active enough interest > in this to implement an NFS locking daemon. We're still waiting. ;) > > Jordan > > P.S. Terry sent me the skeleton of something way back when I was > actually masochistically considering this myself, but I came to > my senses and backed away in time. :) The rpc.lockd stuff is nothing more than grunt-work, actually, after the SunOS 4.1.3 compatible fcntl() calls are implemented. The big problem that BSD4.4-Lite2 introduced is the POSIX semantics for a single close removing all locks. If you seperate this into a veto interface, it's fairly trivial to implement things such that server locking is supported and client locking is not actively prevented by the locking architecture. My current problem is that I can't do the NFS testing locally. I sent Doug Rabson my kernel memory leak test framework, and in combination with other patches, I've introduced a small namei() buffer leak into the NFS code, which is localizable by VOP using the test framework. I think this has to do with the NFSv3 lookup changes. The big magic is to make VOP_ADVLOCK return 0 to accept or an errno.h value to veto a given lock. Then the locking is seperated into: assert check veto coelesce ...in other words, the coeslesce is delayed. This has to be done because of the side effects of locking from the client to the server means that the lock must be asserted on both ends to preserve semantics, but if either end fails the lock, then both ends must be backed out. Obviously, it's impossible to back out a lock that has been coelesced with another lock, without potentially damaging the existing lock; this is especially true if the lock represents a type promotion or demotion between read/write locking. The veto is done on the client rather than on the server because: 1) It is useful to be able to deny some locks without generating a wire delay in order to do it. 2) A wire-based veto would require a change to the NFS locking protocol as defined in the ISO standard, which would make it non-interoperable with all other NFS locking interfaces. 3) In the event of a server failure, the client lock state is recoverable when the server comes back up (this is also the reson the lock must be asserted on both the client and the server). I can go over rpc.lock fd conservation and handle conversion in the face of POSIX close semantics, if anyone is interested in doing the user space code; as I said before, once you understand the issues, the code is trivial: just grunt work, nothing more. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 10:11:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA08954 for hackers-outgoing; Tue, 1 Jul 1997 10:11:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA08949 for ; Tue, 1 Jul 1997 10:11:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18598; Tue, 1 Jul 1997 10:09:45 -0700 From: Terry Lambert Message-Id: <199707011709.KAA18598@phaeton.artisoft.com> Subject: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Tue, 1 Jul 1997 10:09:45 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <33B89142.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 1, 97 07:10:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > P.S. Terry sent me the skeleton of something way back when I was > > actually masochistically considering this myself, but I came to > > my senses and backed away in time. :) > > What would be the requirements for this ? It does not seem too > complicated to me, at least the rpc.lockd framework is already in place. > So the "only" thing left to do would be to manage lists of locks from a > set of hosts and processes, probably merging adjacent locks etc, and > using the F_RSETLK fcntls to actually set the locks in the kernel. > Probably the interaction with rpc.statd would also need some attention. > Or am I grossly missing something? See my other posting; but basically the big obstacles are: 1) The POSIX semantics make it difficult for rpc.lockd to have only one file handle per file regardless of the number of clients with the file open. This is a bit of a pain to overcome, and requires a semantic override. 2) The assertion of a lock can not immediately result in a coelesce if the operation may be backed out. But the assertion must have the force of having already been coelesced for the purposes of denying subsequent lock requests before the server has completed the initial request. 3) The interface must be veto based, so that it is possible to have both local and remote assertion. This is a requirement for client locking, both for preemptive denial as an optimization to save wire traffic, AND to allow the client to recover lock state in the event of a transient server failure (ie: the server is rebooted, etc.). 4) So that server locking works on all file systems, the lock list must be hung off the vnode instead of the inode; one consequence of this is that it drastically simplifies the locking code, and makes it general to all FS's, instead of per FS. As it currently stands, there are FS's on which locking will fail (ie: MSDOSFS, ISOFS, etc.). > If not, then I could probably spend some time to work on this, if nobody > else is already doing it. Doug Rabson has the kernel patches for everything, minus the handle conversion call, and minus the POSIX semantic override. There *IS* a bug in the namei() code, which I was able to test everywhere but the NFS client (I only have one FreeBSD box at this location). If you are interested in helping locate this bug, I can send you a test framework for kernel memory leak detection, and my test set for the namei() buffers, specifically. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 10:19:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA09268 for hackers-outgoing; Tue, 1 Jul 1997 10:19:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA09263 for ; Tue, 1 Jul 1997 10:19:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18612; Tue, 1 Jul 1997 10:14:13 -0700 From: Terry Lambert Message-Id: <199707011714.KAA18612@phaeton.artisoft.com> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) To: imp@village.org (Warner Losh) Date: Tue, 1 Jul 1997 10:14:12 -0700 (MST) Cc: abial@korin.warman.org.pl, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: from "Warner Losh" at Jul 1, 97 09:29:28 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > : BUT, perhaps this is a neat idea to make a FreeBSD demo disk, only using > : the libdialog instead. Or, to make it a "2,88 Mbyte Web Challenge" for > : free Unices. :-) > > Heck, with the number of JAZ and ZIP drives out there, why limit > yourself to 2.88M :-) How about "OpenBSD and NetBSD can boot from one, but FreeBSD can not"? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 10:21:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA09415 for hackers-outgoing; Tue, 1 Jul 1997 10:21:22 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA09408 for ; Tue, 1 Jul 1997 10:21:18 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wj6a9-0006Np-00; Tue, 1 Jul 1997 11:19:13 -0600 To: Terry Lambert Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) Cc: abial@korin.warman.org.pl, luigi@labinfo.iet.unipi.it, hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 10:14:12 PDT." <199707011714.KAA18612@phaeton.artisoft.com> References: <199707011714.KAA18612@phaeton.artisoft.com> Date: Tue, 01 Jul 1997 11:19:13 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707011714.KAA18612@phaeton.artisoft.com> Terry Lambert writes: : How about "OpenBSD and NetBSD can boot from one, but FreeBSD can not"? Then why was I able to boot FreeBSD on my PPro off my JAZ drive when the disk that was supposed to come with it hadn't arrived? Warner From owner-freebsd-hackers Tue Jul 1 10:50:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11036 for hackers-outgoing; Tue, 1 Jul 1997 10:50:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA11029 for ; Tue, 1 Jul 1997 10:50:32 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id KAA28632; Tue, 1 Jul 1997 10:48:47 -0700 (PDT) To: David Dawes cc: Holm Tiffe , freebsd-hackers@FreeBSD.ORG Subject: Re: quad ints implemented ? In-reply-to: Your message of "Tue, 01 Jul 1997 18:35:03 +1000." <19970701183503.31861@rf900.physics.usyd.edu.au> Date: Tue, 01 Jul 1997 10:48:47 -0700 Message-ID: <28628.867779327@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I submitted a pr (bin/2080) with a fix for this a while ago. Sorry it fell throug the cracks - committed! Jordan From owner-freebsd-hackers Tue Jul 1 11:17:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA12452 for hackers-outgoing; Tue, 1 Jul 1997 11:17:06 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA12447 for ; Tue, 1 Jul 1997 11:17:04 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA20605; Tue, 1 Jul 1997 11:13:26 -0700 From: Terry Lambert Message-Id: <199707011813.LAA20605@phaeton.artisoft.com> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) To: imp@village.org (Warner Losh) Date: Tue, 1 Jul 1997 11:13:25 -0700 (MST) Cc: terry@lambert.org, abial@korin.warman.org.pl, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: from "Warner Losh" at Jul 1, 97 11:19:13 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In message <199707011714.KAA18612@phaeton.artisoft.com> Terry Lambert writes: > : How about "OpenBSD and NetBSD can boot from one, but FreeBSD can not"? > > Then why was I able to boot FreeBSD on my PPro off my JAZ drive when > the disk that was supposed to come with it hadn't arrived? Did you hack the controller configuration on an Adaptec controller? Or are you running an NCR? The boot code does not like removable media which shows up as removable (from what I can tell). In all fairness, NetBSD Alpha has a hell of a time booting from a JAZ disk as well (NCR53C810 as well, actually), unless I hack the timeouts up. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 11:37:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13472 for hackers-outgoing; Tue, 1 Jul 1997 11:37:35 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13463 for ; Tue, 1 Jul 1997 11:37:30 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA02135; Tue, 1 Jul 1997 11:26:11 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002126; Tue Jul 1 18:26:01 1997 Message-ID: <33B94B67.446B9B3D@whistle.com> Date: Tue, 01 Jul 1997 11:24:39 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Terry Lambert CC: Ben Black , hackers@FreeBSD.ORG Subject: Re: sfio References: <199707011643.JAA18554@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > has anyone played with sfio? it looks like a valuable replacement for > > stdio... > > > > http://www.oasis.leo.org/perl/src/independent/sfio.dsc.html > > It isn't significantly faster on FreeBSD because of the cache > unification making normal I/O faster. > > Last time I checked, there were still a couple of coherency > problems (missing msync() calls, if I recall correctly). but the authors have a good pedigree. From owner-freebsd-hackers Tue Jul 1 11:39:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13581 for hackers-outgoing; Tue, 1 Jul 1997 11:39:57 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13576 for ; Tue, 1 Jul 1997 11:39:51 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA02311; Tue, 1 Jul 1997 11:30:21 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002309; Tue Jul 1 18:30:17 1997 Message-ID: <33B94C67.15FB7483@whistle.com> Date: Tue, 01 Jul 1997 11:28:55 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Terry Lambert CC: "Jordan K. Hubbard" , witr@rwwa.com, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? References: <199707011658.JAA18573@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > We've been waiting forever for someone to take an active enough interest > > in this to implement an NFS locking daemon. We're still waiting. ;) > > > LINUX now has one so there is an example that can be used.. From owner-freebsd-hackers Tue Jul 1 12:33:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA16225 for hackers-outgoing; Tue, 1 Jul 1997 12:33:07 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16219 for ; Tue, 1 Jul 1997 12:33:02 -0700 (PDT) Received: from rain (portC5.bonn-online.com [195.52.214.76]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id VAA20154; Tue, 1 Jul 1997 21:32:44 +0200 Message-ID: <33B95B56.41C67EA6@bonn-online.com> Date: Tue, 01 Jul 1997 21:32:38 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: NFS locking, was: Re: NFS V3 is it stable? References: <199707011709.KAA18598@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > See my other posting; but basically the big obstacles are: Let me see if I understand all issues correctly: > 1) The POSIX semantics make it difficult for rpc.lockd > to have only one file handle per file regardless of > the number of clients with the file open. This is >[...] So the rpc.lockd (on the server) would have to keep a list of all active locks on a file and only close the file when all locks are cleared. > > 2) The assertion of a lock can not immediately result in > a coelesce if the operation may be backed out. But >[...] This should only affect the client, since if the lock fails on the server, nothing happens there, only a nlm_denied rpc is sent back. Then the client has to deal with the mess, because he had already set the lock locally. >[...] > allow the client to recover lock state in the event of > a transient server failure (ie: the server is rebooted, > etc.). For lock recovery, the lockd on the client would also keep a list of all active locks, and, in case of a server crash, would be notified by the rpc.statd and reissue all lock requests. If a lock request can't be reissued, the lockd should send a SIGLOST signal to the involved processes. Correct ? > 4) So that server locking works on all file systems, the > lock list must be hung off the vnode instead of the > inode; one consequence of this is that it drastically And I thought that this was already the case... >[...] > Doug Rabson has the kernel patches for everything, minus the handle > conversion call, and minus the POSIX semantic override. There *IS* > a bug in the namei() code, which I was able to test everywhere but > the NFS client (I only have one FreeBSD box at this location). If > you are interested in helping locate this bug, I can send you a test > framework for kernel memory leak detection, and my test set for > the namei() buffers, specifically. Sure, go ahead. I don't have a SUN or something like that here, however, for testing with a "real" rpc.lockd. I do have two FreeBSD machines connected via ethernet, so I can do some non-local testing. As I have already pointed out, I would be willing to invest some time in implementing the rpc.lockd. The main problems (from my point of view) are: Details of the locking protocol: * How are blocking locks implemented? * On which side are the locks coalesced? On the client's or on the server's rpc.lockd ? * What is the cookie in the nlm_lockargs struct ? (probably used by the client to identify the result messages) * What is the file handle in the nlm_lock struct ? (seems to be device/inode/generation number) * What is the owner handle in the nlm_lock struct ? (IP Address of the client? process id ?) Converting the nfs file handle into an open file: This seems to me the most important point for the lockd implementation. Without this, I can't actually lock the file. Client side locking: The lock requests must somehow be communicated from the kernel to local lockd, which then forwards it to the server's lockd. If I know all these details, it should be possible for me to complete the rpc.lockd implementation. So, if anybody has any knowledge on these issues, please contact me. It would be greatly appreciated. And of course, if someone else also wants to work on this, you are welcome. It may still possible that we end up with an at least basically working nfs locking implementation :-) Best regards, Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Tue Jul 1 12:34:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA16303 for hackers-outgoing; Tue, 1 Jul 1997 12:34:20 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA16295 for ; Tue, 1 Jul 1997 12:34:14 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wj8cM-0000V7-00; Tue, 1 Jul 1997 12:29:38 -0700 Date: Tue, 1 Jul 1997 12:29:37 -0700 (PDT) From: Tom Samplonius To: Julian Elischer cc: Terry Lambert , Ben Black , hackers@freebsd.org Subject: Re: sfio In-Reply-To: <33B94B67.446B9B3D@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, Julian Elischer wrote: > but the authors have a good pedigree. Ahh... that's what I look for in software: good breeding. Tom From owner-freebsd-hackers Tue Jul 1 12:37:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA16490 for hackers-outgoing; Tue, 1 Jul 1997 12:37:57 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16485 for ; Tue, 1 Jul 1997 12:37:55 -0700 (PDT) Received: from rain (portC5.bonn-online.com [195.52.214.76]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id VAA20174; Tue, 1 Jul 1997 21:37:10 +0200 Message-ID: <33B95C60.167EB0E7@bonn-online.com> Date: Tue, 01 Jul 1997 21:37:04 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Julian Elischer CC: Terry Lambert , "Jordan K. Hubbard" , witr@rwwa.com, chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? References: <199707011658.JAA18573@phaeton.artisoft.com> <33B94C67.15FB7483@whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > > Terry Lambert wrote: > > > > > We've been waiting forever for someone to take an active enough interest > > > in this to implement an NFS locking daemon. We're still waiting. ;) > > > > > > LINUX now has one so there is an example that can be used.. Well, if those linux guys can do it, then on FreeBSD we can damn well do it, too! Right? -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Tue Jul 1 13:26:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA18909 for hackers-outgoing; Tue, 1 Jul 1997 13:26:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA18904 for ; Tue, 1 Jul 1997 13:25:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA27875; Tue, 1 Jul 1997 13:24:00 -0700 From: Terry Lambert Message-Id: <199707012024.NAA27875@phaeton.artisoft.com> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Tue, 1 Jul 1997 13:23:59 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <33B95B56.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 1, 97 09:32:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Let me see if I understand all issues correctly: > > > 1) The POSIX semantics make it difficult for rpc.lockd > > to have only one file handle per file regardless of > > the number of clients with the file open. This is > >[...] > > So the rpc.lockd (on the server) would have to keep a list of all active > locks on a file and only close the file when all locks are cleared. No. The rpc.lockd could not convert a handle into an fd, and subsequently close the fd, until all fd's for that file had been closed by all clients. In general, you want to: 1) Convert handle to fd 2) fstat( fd, ...) 3) Compare st_ino and st_dev to see if it's already open 4) If it is, add a reference count to the already open struct and close the new fd Step #4 destroys all locks with the new POSIX close semantics. See, you are assuming, incorrectly, that each FS will generate file handles using the same schema. File handles are, in fact, FS specific opaque data. If you don't believe me, look at the ISOFS handle code. > > 2) The assertion of a lock can not immediately result in > > a coelesce if the operation may be backed out. But > >[...] > > This should only affect the client, since if the lock fails on the > server, nothing happens there, only a nlm_denied rpc is sent back. Then > the client has to deal with the mess, because he had already set the > lock locally. Yes. Unless you are not using a veto interface (ie: if you are using the current locking code). If you do not use a veto interface, you could fail to assert the lock locally after asserting the lock remotely. In that case, now it's a server problem. Either case only occurs when there is client locking, though. By delaying the coelesce, and doing it seperately from the assert (ie: having a "commit" phase), you resolve the race window. > > allow the client to recover lock state in the event of > > a transient server failure (ie: the server is rebooted, > > etc.). > > For lock recovery, the lockd on the client would also keep a list of all > active locks, and, in case of a server crash, would be notified by the > rpc.statd and reissue all lock requests. If a lock request can't be > reissued, the lockd should send a SIGLOST signal to the involved > processes. > Correct ? No. NFS client locks are not forwarded through a local lockd, they are reissued as a result of an rpc.statd server notification. If the client crashes, the lock state on the server is destroyed. If the server crashes, the clients have an idea of the lock state at the time of the crash, and it must be restored. > > 4) So that server locking works on all file systems, the > > lock list must be hung off the vnode instead of the > > inode; one consequence of this is that it drastically > > And I thought that this was already the case... No. Look at the code. It is hung off the inode. > > Doug Rabson has the kernel patches for everything, minus the handle > > conversion call, and minus the POSIX semantic override. There *IS* > > a bug in the namei() code, which I was able to test everywhere but > > the NFS client (I only have one FreeBSD box at this location). If > > you are interested in helping locate this bug, I can send you a test > > framework for kernel memory leak detection, and my test set for > > the namei() buffers, specifically. > > Sure, go ahead. I don't have a SUN or something like that here, however, > for testing with a "real" rpc.lockd. I do have two FreeBSD machines > connected via ethernet, so I can do some non-local testing. The testing in this case is collateral bugs in the namei() code changes, which I didn't seperate from the rpc.lockd changes. If I can resolve the namei() leaks, Doug will commit the code to the FreeBSD source repository, and it will show up on the next CVSup. Are you running -current? I can probably make a set of diffs against a -current source treee this coming weekend (sorry, that's the fastest I can get to it; I'm currently job-hunting). > As I have already pointed out, I would be willing to invest some time in > implementing the rpc.lockd. The main problems (from my point of view) > are: > > Details of the locking protocol: > > * How are blocking locks implemented? Blocking locks are rather trivial, compared to some of the other issues; I'd be happy to discuss straegy on them with you once you get going. > * On which side are the locks coalesced? On the client's or > on the server's rpc.lockd ? The locks are coelesced on the client in the lock code, and on the server in the lock code. The rpc.lockd only proxies the locking calls. One problem here: FreeBSD does not have NFS client locking code. Andrew (the guy who wrote the rpc.lockd) has the ISO standard, and is probably a good reference on that. Without a working client, you won't be able to test the server. > * What is the cookie in the nlm_lockargs struct ? > (probably used by the client to identify the > result messages) > * What is the file handle in the nlm_lock struct ? > (seems to be device/inode/generation number) Andrew knows both of these for sure. I don't, or I would have made the handle conversion call already. The answer on the handle is "it's opaque data; you are not allowed to interpret it as anything other than a hash key, if that". > * What is the owner handle in the nlm_lock struct ? > (IP Address of the client? process id ?) There is a 32 bit system ID and a process ID for that system. This may be problematic at some later time, if threads are supposed to be able to lock against each other. 8-(. > Converting the nfs file handle into an open file: This seems to me the > most important point for the lockd implementation. Without this, > I can't actually lock the file. Yes, this is the conversion call. I nee to know the ire handle format so I can change it into the FS specific parameter in the kernel when it is passed to the fcntl() for the conversion. This is Andrew's ball park here, since he has the docs. > Client side locking: The lock requests must somehow be communicated > from the kernel to local lockd, which then forwards it > to the server's lockd. No. The calls are rpc'ed from the NFS FS module, which is the NFS client. The only question here is how the connection state is established and maintained by rpc.statd. > If I know all these details, it should be possible for me to > complete the rpc.lockd implementation. Yes. > So, if anybody has any knowledge on these issues, please contact > me. It would be greatly appreciated. And of course, if someone else > also wants to work on this, you are welcome. We need the information from Andrew to proceed on the handle conversion, and on the client code. I suspect it will be a much better idea to get an interoperable server before going after the client code. The only caveat here is that the architecture of the kernel code must not preclude a later client implementation. > It may still possible that we end up with an at least basically > working nfs locking implementation :-) It should be pretty easy, in fact. The hardest part, which is the adjustment to the kernel code, has already been done (twice, now). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 15:43:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27406 for hackers-outgoing; Tue, 1 Jul 1997 15:43:34 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27396 for ; Tue, 1 Jul 1997 15:43:31 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA11743; Tue, 1 Jul 1997 15:36:00 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011741; Tue Jul 1 22:35:57 1997 Message-ID: <33B985FA.3F54BC7E@whistle.com> Date: Tue, 01 Jul 1997 15:34:34 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Terry Lambert CC: Sebastian Lederer , freebsd-hackers@FreeBSD.ORG Subject: POSIX locking ( was NFS locking) References: <199707012024.NAA27875@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > Let me see if I understand all issues correctly: > > > > > 1) The POSIX semantics make it difficult for rpc.lockd > > > to have only one file handle per file regardless of > > > the number of clients with the file open. This is > > >[...] > > > > So the rpc.lockd (on the server) would have to keep a list of all active > > locks on a file and only close the file when all locks are cleared. > > No. The rpc.lockd could not convert a handle into an fd, and > subsequently close the fd, until all fd's for that file had been > closed by all clients. basically the posix locking is a pain in the rear-end. It's quite amazing that they managed to get something SO WRONG without being stopped in the process by at least one person with a clue. SAMBA has to go to great lengths to get around this.. I suggest that we have a per-process flag that allows the locks to be done per-fd. it would break posix, but if you had posix by default, and this only if you set it, then it would still be posix complient. such things as samba and nfslockd could flip the bit and get useful semantics. Anyone think this is a TERRIBLE idea? certainly Once the semantics and mechanism of 'turning the bit on' were settled, the code changes would be quite easy. I'm sure the same interface could be added to Linux if the samba people asked for it (and I know they would). From owner-freebsd-hackers Tue Jul 1 16:07:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA28801 for hackers-outgoing; Tue, 1 Jul 1997 16:07:23 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA28795 for ; Tue, 1 Jul 1997 16:07:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA05274; Tue, 1 Jul 1997 16:05:27 -0700 From: Terry Lambert Message-Id: <199707012305.QAA05274@phaeton.artisoft.com> Subject: Re: POSIX locking ( was NFS locking) To: julian@whistle.com (Julian Elischer) Date: Tue, 1 Jul 1997 16:05:26 -0700 (MST) Cc: terry@lambert.org, lederer@bonn-online.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <33B985FA.3F54BC7E@whistle.com> from "Julian Elischer" at Jul 1, 97 03:34:34 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ ... POSIX brain damage ... ] > I suggest that we have a per-process flag that allows the locks to be > done per-fd. > it would break posix, but if you had posix by default, and this > only if you set it, then it would still be posix complient. I was thinking of an fcntl-based semantic overide, set on a per fd basis. Something like: int i = 1; fcntl( fd, F_NONPOSIX, &i); or even fcntl( fd, F_NONPOSIXCLOSE, &i); if we wanted to be anal about the meaning of the flag. This would really be the best way to handle it, without really breaking POSIX (default it to on). That way the per process semantics are still POSIX. I could easily envision a process that was mixed POSIX and non-POSIX I/O. A per fd overide makes a lot more sense than a per process overrride in that case. Plus the file struct has to be there anyway for you to close it or anything else, for that matter. > such things as samba and nfslockd could flip the bit and get > useful semantics. Yes. I thought that proxy locking would be useful for service as well. I left enough spare space in the compatability struct that I defined for communicating the remote system ID and process ID such that versioning could be done without having to change the struct in an incompatible way. The trick on versioning it for the remote ops is that the local ops have implied field values (ie: you can't get the lock data for a remote lock locally). This leaves the call binarily backward comaptible, which was the main design goal. > Anyone think this is a TERRIBLE idea? Nope. 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 1 18:36:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA05797 for hackers-outgoing; Tue, 1 Jul 1997 18:36:21 -0700 (PDT) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA05767 for ; Tue, 1 Jul 1997 18:36:08 -0700 (PDT) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.5/8.8.5) with ESMTP id VAA02691; Tue, 1 Jul 1997 21:35:56 -0400 (EDT) Message-Id: <199707020135.VAA02691@spooky.rwwa.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Chuck Robey cc: Robert Withrow , freebsd-hackers@FreeBSD.ORG Subject: Re: NFS V3 is it stable? In-reply-to: Your message of "Mon, 30 Jun 1997 22:47:30 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Jul 1997 21:35:56 -0400 From: Robert Withrow Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk chuckr@glue.umd.edu said: :- I don't know what to say to you. Must have been working by a freak :- timing accident. Well, I always said I'd rather be lucky than good. Still, there are many hundreds of unix workstations at this site, runing Solaris, SunOs, Hpux, Aix, Linux, Sco, and FreeBSD, all mounting /var/mail (or whatever) via NFS, and, presumably, getting mail correctly (Since people don't often complain about missing mail, and when they do it turns out to be something identifyable), so I guess we are *very* lucky... ;-) For example from FreeBSD: bash$ ls -l /var/mail lrwxr-xr-x 1 root wheel 11 Feb 4 16:33 /var/mail -> /mail/bldg2 bash$ ls -l /mail/bldg2 lr-xr-xr-x 1 root wheel 13 Jul 1 21:24 /mail/bldg2 -> /a/pobox/mail bash$ mount | grep pobox pobox:/mail on /a/pobox/mail (nosuid) bash$ telnet pobox Trying ... Connected to ... UNIX(r) System V Release 4.0 (pobox) And From SunOs: bash$ ls -l /var/spool/mail lrwxrwxrwx 1 root 11 Apr 2 17:31 /var/spool/mail -> /mail/bldg2 bash$ ls -l /mail/bldg2 lrwxrwxrwx 1 root 25 Jul 1 21:27 /mail/bldg2 -> /tmp_mnt/mail/bldg2 bash$ mount | grep bldg2 pobox:/mail on /tmp_mnt/mail/bldg2 type nfs (rw,soft,intr) And on solaris: bash$ ls -l /var/mail lrwxrwxrwx 1 root other 11 Oct 24 1996 /var/mail -> /mail/bldg2 bash$ /etc/mount | grep bldg2 /mail/bldg2 on pobox:/mail read/write/soft/intr/remote on Tue Jul 1 21:33:41 1997 ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM From owner-freebsd-hackers Tue Jul 1 21:02:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA11178 for hackers-outgoing; Tue, 1 Jul 1997 21:02:58 -0700 (PDT) Received: from warrane.connect.com.au (warrane.connect.com.au [192.189.54.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11173 for ; Tue, 1 Jul 1997 21:02:51 -0700 (PDT) Received: from gurney.zeta.org.au (d31.syd2.zeta.org.au [203.26.11.31]) by warrane.connect.com.au with ESMTP id OAA29053 (8.8.5/IDA-1.6 for ); Wed, 2 Jul 1997 14:02:46 +1000 (EST) Received: (from andrew@localhost) by gurney.zeta.org.au (8.7.5/8.7.3) id JAA09201; Wed, 2 Jul 1997 09:03:21 +1000 (EST) Message-ID: <19970702090321.33909@gurney.zeta.org.au> Date: Wed, 2 Jul 1997 09:03:21 +1000 From: Andrew Reilly To: hackers@FreeBSD.ORG Subject: Re: PDP-11 UNIX source licenses References: <199707011020.MAA18509@negara.fokus.gmd.de > Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67e In-Reply-To: <199707011020.MAA18509@negara.fokus.gmd.de >; from Joerg Micheel on Tue, Jul 01, 1997 at 12:20:45PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As an interesting "potted history" demonstration, it ought to be possible with today's hardware to run this on a PDP-11 simulator if such exists. It would probably be faster than the real thing. Does anyone know of a PDP-11 simulator? (Couldn't be too hard.) On Tue, Jul 01, 1997 at 12:20:45PM +0200, Joerg Micheel wrote: > the history of making UNIX freely available is old, > but I thought hackers@freebsd might be a community to > look for fellows of Warren Toomey's initiative to get > V1-7 source code licenses from SCO for personal use. -- Andrew "The steady state of disks is full." -- Ken Thompson From owner-freebsd-hackers Tue Jul 1 21:18:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA12071 for hackers-outgoing; Tue, 1 Jul 1997 21:18:06 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA12061 for ; Tue, 1 Jul 1997 21:17:57 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wjGqP-00075D-00; Tue, 1 Jul 1997 22:16:41 -0600 To: Terry Lambert Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) Cc: abial@korin.warman.org.pl, luigi@labinfo.iet.unipi.it, hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 11:13:25 PDT." <199707011813.LAA20605@phaeton.artisoft.com> References: <199707011813.LAA20605@phaeton.artisoft.com> Date: Tue, 01 Jul 1997 22:16:41 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707011813.LAA20605@phaeton.artisoft.com> Terry Lambert writes: : Did you hack the controller configuration on an Adaptec controller? It just worked. I may have set something to treat removable devices as fixed. Warner From owner-freebsd-hackers Tue Jul 1 21:38:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA12896 for hackers-outgoing; Tue, 1 Jul 1997 21:38:51 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12891 for ; Tue, 1 Jul 1997 21:38:45 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id OAA15240; Wed, 2 Jul 1997 14:37:48 +1000 (EST) Message-ID: <19970702143748.33147@rf900.physics.usyd.edu.au> Date: Wed, 2 Jul 1997 14:37:48 +1000 From: David Dawes To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Determining FreeBSD versions References: <19970701190353.50830@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Warner Losh on Tue, Jul 01, 1997 at 09:33:17AM -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jul 01, 1997 at 09:33:17AM -0600, Warner Losh wrote: >In message <19970701190353.50830@rf900.physics.usyd.edu.au> David Dawes writes: >: branch, and as a consequence, 'uname -r' now reports "2.1-STABLE" rather > >Hmmm. Why not report 2.1.x-STABLE? Where x is incremented whenever a >release happens. Then people know that things are newer than 2.1.x or >2.2.x or whatever. Agreed. >I'm not completely sure that parsing osversion.h (or is that >osreldate.h) is the right answer here. I've ended up getting imake to look at the kern.osreldate sysctl value when it can't determine the dot revision from the uname -r output. At least then both methods are consistent in that they are getting the version information from the kernel. David From owner-freebsd-hackers Tue Jul 1 21:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA13004 for hackers-outgoing; Tue, 1 Jul 1997 21:41:06 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust74.Max17.Washington.DC.MS.UU.NET [153.34.57.74]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12999 for ; Tue, 1 Jul 1997 21:41:01 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id AAA25374; Wed, 2 Jul 1997 00:38:38 -0400 (EDT) Message-ID: <19970702003838.28818@wakky.dyn.ml.org> Date: Wed, 2 Jul 1997 00:38:38 -0400 From: Lee Cremeans To: Andrew Reilly Cc: hackers@freebsd.org Subject: Re: PDP-11 UNIX source licenses References: <199707011020.MAA18509@negara.fokus.gmd.de <19970702090321.33909@gurney.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e Reply-to: hcremean@vt.edu X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone know of a PDP-11 simulator? (Couldn't be too > hard.) > I actually found quite a few a while back, but I don't remember where and I deleted my bookmark to the PDP-11 FAQ... :/ Anyway, I found all this in Yahoo about a month ago, so it should all be there still. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower)|A! JW223 "People are idiots who deserve to be mocked."--Dogbert|YWD+++i P&B+++ SL+++^i My home page:http://wakky.dyn.ml.org/~lee | MD+++r P+ I++ Di "Whoa, dumber than advertised!" | $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi From owner-freebsd-hackers Tue Jul 1 22:04:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13885 for hackers-outgoing; Tue, 1 Jul 1997 22:04:30 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13877 for ; Tue, 1 Jul 1997 22:04:24 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id AAA00337; Wed, 2 Jul 1997 00:03:59 -0500 (EST) From: "John S. Dyson" Message-Id: <199707020503.AAA00337@dyson.iquest.net> Subject: Re: PDP-11 UNIX source licenses In-Reply-To: <19970702090321.33909@gurney.zeta.org.au> from Andrew Reilly at "Jul 2, 97 09:03:21 am" To: andrew@zeta.org.au (Andrew Reilly) Date: Wed, 2 Jul 1997 00:03:58 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As an interesting "potted history" demonstration, it ought > to be possible with today's hardware to run this on a PDP-11 > simulator if such exists. It would probably be faster than > the real thing. > > Does anyone know of a PDP-11 simulator? (Couldn't be too > hard.) > I know of a really good one at ftp://ftp.digital.com/pub/DEC/sim There is a simulator called sim_2_2 or somesuch that actually works pretty well. I have booted the UNIX V7 that also resides in a subdir below there... The simulator isn't very fast, but looking at the code, it appears that it might be very complete. John From owner-freebsd-hackers Tue Jul 1 22:12:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA14155 for hackers-outgoing; Tue, 1 Jul 1997 22:12:00 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA14147 for ; Tue, 1 Jul 1997 22:11:50 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id BAA09016; Wed, 2 Jul 1997 01:11:48 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id BAA12291; Wed, 2 Jul 1997 01:11:46 -0400 Date: Wed, 2 Jul 1997 01:11:50 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Joerg Wunsch cc: FreeBSD-Hackers Subject: Re: mounting In-Reply-To: <19970701073739.TT45372@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, J Wunsch wrote: > As Chuck Robey wrote: > > > mount -t nfs -I512 -o -r1024 -w1024 remote_machine:/path /path > > > > If there's equal signs that have to go in there, I guess I'll find out. > > The man page isn't clear on that. > > The -I is IMHO unnecessary. However, you ought to group -o options > by commas: > > mount [-t nfs] -o -r1024,-w1024 remote:/path /path > > The -t nfs is not really required. The -w1024 ain't required either, > since your machine with the slow card is of course allowed to send > full packets. It's only that it can't receive a full 8 KB NFS packet. Just thought I'd comment that this does indeed work for the 3C503 card. I have tested it and I'll keep this around! > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Tue Jul 1 23:20:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16355 for hackers-outgoing; Tue, 1 Jul 1997 23:20:25 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA16350; Tue, 1 Jul 1997 23:20:19 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA24988; Tue, 1 Jul 1997 23:14:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024985; Wed Jul 2 06:14:39 1997 Date: Tue, 1 Jul 1997 23:13:17 -0700 (PDT) From: Julian Elischer To: dyson@FreeBSD.ORG cc: Andrew Reilly , hackers@FreeBSD.ORG Subject: Re: PDP-11 UNIX source licenses In-Reply-To: <199707020503.AAA00337@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On my P6-200 I should be able to fit the entire address space, kernel and a couple of users worth, into the cpu cache.. heh (I cut my teeth on the 11, what a nice instruction set.. sigh) On Wed, 2 Jul 1997, John S. Dyson wrote: > > As an interesting "potted history" demonstration, it ought > > to be possible with today's hardware to run this on a PDP-11 > > simulator if such exists. It would probably be faster than > > the real thing. > > > > Does anyone know of a PDP-11 simulator? (Couldn't be too > > hard.) > > > I know of a really good one at ftp://ftp.digital.com/pub/DEC/sim > There is a simulator called sim_2_2 or somesuch that actually > works pretty well. I have booted the UNIX V7 that also resides in > a subdir below there... The simulator isn't very fast, but looking > at the code, it appears that it might be very complete. > > John > > From owner-freebsd-hackers Tue Jul 1 23:21:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16392 for hackers-outgoing; Tue, 1 Jul 1997 23:21:09 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA16385 for ; Tue, 1 Jul 1997 23:21:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA22975 for FreeBSD-Hackers@FreeBSD.ORG; Wed, 2 Jul 1997 08:20:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA09226; Wed, 2 Jul 1997 07:55:34 +0200 (MET DST) Message-ID: <19970702075534.AY33258@uriah.heep.sax.de> Date: Wed, 2 Jul 1997 07:55:34 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-Hackers@FreeBSD.ORG (FreeBSD-Hackers) Subject: Re: mounting References: <19970701073739.TT45372@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on Jul 2, 1997 01:11:50 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > Just thought I'd comment that this does indeed work for the 3C503 card. > I have tested it and I'll keep this around! I should know. :) I've been using a 3C503-equipped box for quite some time... They always hung when mounting `fast' workstation NFS servers in the past, but these days, even a fast PCI machine running FreeBSD with a WD8013 card classifies as `fast' (i. e., it can send the 6 Ethernet frames that form one 8 KB NFS block back-to-back). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 1 23:30:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16766 for hackers-outgoing; Tue, 1 Jul 1997 23:30:29 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA16752; Tue, 1 Jul 1997 23:30:16 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA25164; Tue, 1 Jul 1997 23:22:52 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd025162; Wed Jul 2 06:22:47 1997 Date: Tue, 1 Jul 1997 23:21:25 -0700 (PDT) From: Julian Elischer To: peter@freebsd.org, hackers@freebsd.org Subject: CVS upgrade really a downgrade.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The new CVS breaks our build environment here in one particular way. We have a 'warehouse' of modules (e.g. samba, apache etc.) which we check out into a tree for building a specific product. differnt products might use different modules in a differnt configuration. thus our build tree has sub branches that come from differnt parts of the CVS tree. The new CVS doesn't handle this as easily as the old one. In particular the CVS/Entries file seems to get updated with a D/dirname//// entry whenever it traverses into such a subdirectory, however if we remove the subdirectory, (in a "make clean") (it was only checkied out there during the build) CVS then throws up a the next build because it has an entry for the dir, but it isn't in teh repository in that place (because it came from somewhere else). does anyone know why this was changed? Aren't composite trees supported any more? julian From owner-freebsd-hackers Wed Jul 2 00:09:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18275 for hackers-outgoing; Wed, 2 Jul 1997 00:09:06 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA18232 for ; Wed, 2 Jul 1997 00:08:24 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id JAA03375; Wed, 2 Jul 1997 09:07:06 +0200 (MET DST) Date: Wed, 2 Jul 1997 09:07:06 +0200 (MET DST) From: Andrzej Bialecki To: Warner Losh cc: "Daniel O'Callaghan" , Holm Tiffe , freebsd-hackers@FreeBSD.ORG Subject: Re: quad ints implemented ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, Warner Losh wrote: > In message "Daniel O'Callaghan" writes: > : > I've tried to get postgreSQL V6.1 working with the int8 package on -current. > : > It seems that FreeBSD has not jet fully implemented the 64bit int in the > : > stdio library, %q is not documented. It works for printf(3), but scanf fails. > : > : Yes, I've noticed this, too. > > I've also noticed that things liked %lld and %llu don't work on > FreeBSD. This is from code ported from Solaris. Waht, if anything, > does the standard have to say on this? And would people object if I > implemented %ll as a long long modifier? I would not object. I had exactly the same situation backwards -I had to port some code from FreeBSD to Solaris, when I noticed this quirk. I hope it means you'll leave the %q as well, to avoid breaking the code which already uses it. Then we could deprecate usage of what is considered nonstandard... Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Wed Jul 2 00:12:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18438 for hackers-outgoing; Wed, 2 Jul 1997 00:12:04 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA18410 for ; Wed, 2 Jul 1997 00:11:53 -0700 (PDT) Received: (qmail 838 invoked by uid 1000); 2 Jul 1997 07:06:46 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-PRIORITY: 2 (High) Priority: urgent Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 02 Jul 1997 00:06:46 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: timeout/untimeout - How? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I KNOW I am doing something foolish. But what? [at the beginning of a driver] ... static void dpt_timeout_losers(void *dpt); ... [in dpt_scsi_cmd] ... ospl = splbio(); if ( !(dpt->state & DPT_STATE_LOSERS_TIMEOUT_SET) ) { dpt->state |= DPT_STATE_LOSERS_TIMEOUT_SET; timeout((timeout_func_t)dpt_timeout_losers, dpt, hz * 10); } splx(ospl); ... static void dpt_timeout_losers(void *arg) { dpt_softc_t *dpt = (dpt_softc_t *)arg; if ( !(dpt->state & DPT_STATE_LOSERS_TIMEOUT_ACTIVE) ) dpt_abort_losers(dpt); timeout((timeout_func_t)dpt_timeout_losers, (caddr_t)dpt, hz * 10); } What I am trying to do is have the function dpt_abort_losers() run once every 10 seconds. (Please don't ask why - nasty hardware problems) What I am getting is a panic due to timeout table being full. Where is my stupidity? Simon From owner-freebsd-hackers Wed Jul 2 00:12:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18444 for hackers-outgoing; Wed, 2 Jul 1997 00:12:05 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA18409 for ; Wed, 2 Jul 1997 00:11:53 -0700 (PDT) Received: (qmail 840 invoked by uid 1000); 2 Jul 1997 07:06:46 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 02 Jul 1997 00:06:46 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: vm_page_alloc error Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In stress-testing a new P6-200 system (128MB RAM), we are getting: vm_page_alloc(ZERO): missing pages on cache queue: 1 Sometimes it will say (NORMAL) instead of (ZERO). Sometimes it will say queue: 2 instead of queue: 1 Stress testing means running 50-500 copies of dd, all reading the same raw disk. Top says: last pid: 286; load averages: 1.49, 1.31, 0.64 23:45:21 51 processes: 1 running, 50 sleeping CPU states: 0.4% user, 0.0% nice, 1.6% system, 0.8% interrupt, 97.3% idle Mem: 26M Active, 4044K Inact, 7056K Wired, 32K Cache, 1958K Buf, 26M Free Swap: 256M Total, 37M Used, 219M Free, 14% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 282 root 28 0 648K 532K RUN 0:00 0.38% 0.38% top 266 root -6 0 2272K 1064K physst 0:00 0.04% 0.04% dd 255 root -6 0 2272K 1064K physst 0:00 0.04% 0.04% dd 133 root 18 0 332K 160K pause 0:00 0.00% 0.00% cron ... Thanx, Simon From owner-freebsd-hackers Wed Jul 2 00:30:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19291 for hackers-outgoing; Wed, 2 Jul 1997 00:30:06 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA19259 for ; Wed, 2 Jul 1997 00:29:54 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id JAA23254; Wed, 2 Jul 1997 09:29:06 +0200 Message-ID: <33BA0339.167EB0E7@bonn-online.com> Date: Wed, 02 Jul 1997 09:28:57 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707012024.NAA27875@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > No. The rpc.lockd could not convert a handle into an fd, and > subsequently close the fd, until all fd's for that file had been > closed by all clients. > > In general, you want to: > > 1) Convert handle to fd > 2) fstat( fd, ...) > 3) Compare st_ino and st_dev to see if it's already open > 4) If it is, add a reference count to the already open > struct and close the new fd > > Step #4 destroys all locks with the new POSIX close semantics. > So you still have to keep a list of all active locks (with the corresponding file handles), and if you encounter a filehandle which is already on the list, there will be already am open fd for it, and you don't do the conversion again. No need to close a fd. The only assumption I am making about the file handle is that it uniquely identifies a file on the server (and that it can be converted into an open file,of course). That F_NONPOSIX fnctl would still make things easier, though. In fact, it might be extremely useful for all sorts of other things, I presume. > > No. NFS client locks are not forwarded through a local lockd, > they are reissued as a result of an rpc.statd server notification. > If the client crashes, the lock state on the server is destroyed. > If the server crashes, the clients have an idea of the lock state > at the time of the crash, and it must be restored. Well, at least the Sun manual page for lockd says : [...] DESCRIPTION lockd is part of the NFS lock manager, which supports record locking operations on NFS files. See fcntl(2) and lockf(3C). The lock manager provides two functions: o it forwards fcntl(2) locking requests for NFS mounted file systems to the lock manager on the NFS server o it generates local file locking operations in response to requests forwarded from lock managers running on NFS client machines. [...] I believe in SunOS there is an extension to the nfssys (=nfs_svc in BSD) system call, using the LM_SVC flag, for this purpose. > > The testing in this case is collateral bugs in the namei() code > changes, which I didn't seperate from the rpc.lockd changes. If > I can resolve the namei() leaks, Doug will commit the code to the > FreeBSD source repository, and it will show up on the next CVSup. > > Are you running -current? I can probably make a set of diffs against > a -current source treee this coming weekend (sorry, that's the fastest > I can get to it; I'm currently job-hunting). > Weekend would be fine. However, I need to upgrade to -current first, my system is a rather out-of-date 2.2-SNAP. I am still looking for someone in the vincinity who can put me -current on a tape... > > One problem here: FreeBSD does not have NFS client locking code. > Andrew (the guy who wrote the rpc.lockd) has the ISO standard, > and is probably a good reference on that. Without a working > client, you won't be able to test the server. In the rpc.lockd source directory is a test program that issues fake rpc locking calls. I've already used it for a little testing. I could also probably get the free version of SCO UNIX and install it on one of my boxes. IF SCO UNIX actually does nfs locking, that could be used for "real life" testing. The only commercial unix for PCs that I have used myself was NEXTSTEP 3.2, a few years ago. And what would you say? It didn't support nfs locking... Best regards, Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Wed Jul 2 01:51:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA22727 for hackers-outgoing; Wed, 2 Jul 1997 01:51:34 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA22718 for ; Wed, 2 Jul 1997 01:51:29 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.8.5/8.6.9) with SMTP id JAA19074 for ; Wed, 2 Jul 1997 09:51:29 +0100 (BST) Date: Wed, 2 Jul 1997 09:51:28 +0100 (BST) From: Developer To: freebsd-hackers@freebsd.org Subject: Any ideas? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know this is a bit off topic, but any ideas why this code does not move the pointer:- int main(int argc,char** argv) { Window root; Display *display; char* displayname=NULL; int screen; display=XOpenDisplay(displayname); if (!display) exit(0); screen=DefaultScreen(display); root=VirtualRootWindow(display,screen); XWarpPointer(display,NULL,NULL,0,0,0,0,100,100); } Cheers. Trefor S. From owner-freebsd-hackers Wed Jul 2 02:03:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23448 for hackers-outgoing; Wed, 2 Jul 1997 02:03:13 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA23441 for ; Wed, 2 Jul 1997 02:03:07 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA06766; Wed, 2 Jul 1997 18:32:54 +0930 (CST) From: Michael Smith Message-Id: <199707020902.SAA06766@genesis.atrad.adelaide.edu.au> Subject: Re: timeout/untimeout - How? In-Reply-To: from Simon Shapiro at "Jul 2, 97 00:06:46 am" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Wed, 2 Jul 1997 18:32:54 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro stands accused of saying: [Charset iso-8859-8 unsupported, filtering to ASCII...] > I KNOW I am doing something foolish. But what? > > [at the beginning of a driver] > ... > static void > dpt_timeout_losers(void *dpt); > ... > > [in dpt_scsi_cmd] > ... > ospl = splbio(); > if ( !(dpt->state & DPT_STATE_LOSERS_TIMEOUT_SET) ) { > dpt->state |= DPT_STATE_LOSERS_TIMEOUT_SET; > timeout((timeout_func_t)dpt_timeout_losers, dpt, hz * 10); > } > splx(ospl); > ... > > static void > dpt_timeout_losers(void *arg) > { > dpt_softc_t *dpt = (dpt_softc_t *)arg; > > if ( !(dpt->state & DPT_STATE_LOSERS_TIMEOUT_ACTIVE) ) > dpt_abort_losers(dpt); > > timeout((timeout_func_t)dpt_timeout_losers, (caddr_t)dpt, hz * 10); > } > > What I am trying to do is have the function dpt_abort_losers() run once > every 10 seconds. (Please don't ask why - nasty hardware problems) > > What I am getting is a panic due to timeout table being full. > > Where is my stupidity? At startup, you start one loop of dpt_timeout_losers. Then, every time your code in dpt_scsi_cmd runs, you start another loop. Eventually, you have hundreds or thousands of these loops running, and your timeout table overflows. It's not clear what you actually want from the timeout; do you just want something that runs every 10 seconds and reaps all the losers? If so, don't call your timeout function from dpt_scsi_cmd, because the loop started when the driver is initialised will still be running. > Simon -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jul 2 02:50:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA26133 for hackers-outgoing; Wed, 2 Jul 1997 02:50:45 -0700 (PDT) Received: from mailbox.uq.edu.au (zzshocki.slip.cc.uq.edu.au [130.102.221.173]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA26125 for ; Wed, 2 Jul 1997 02:50:37 -0700 (PDT) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by mailbox.uq.edu.au (8.8.6/8.6.12) with ESMTP id TAA05570 for ; Wed, 2 Jul 1997 19:53:58 +1000 (EST) Message-Id: <199707020953.TAA05570@mailbox.uq.edu.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: pppd chat script with multiple phone numbers? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Jul 1997 19:53:55 +1000 From: Stephen Hocking Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone hacked together a a chat script or even a little shell script that handles trying multiple numbers and retrys in the really neat way that userland ppp does? Stephen From owner-freebsd-hackers Wed Jul 2 04:47:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29587 for hackers-outgoing; Wed, 2 Jul 1997 04:47:57 -0700 (PDT) Received: from lab321.ru (root@anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29582 for ; Wed, 2 Jul 1997 04:47:47 -0700 (PDT) Received: from localhost (kev@localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru SLmail95 v1.0.32 with SMTP id SAA00653; Wed, 2 Jul 1997 18:44:25 +0700 (OSD) Date: Wed, 2 Jul 1997 18:44:24 +0700 (OSD) From: Eugeny Kuzakov To: Stephen Hocking cc: hackers@FreeBSD.ORG Subject: Re: pppd chat script with multiple phone numbers? In-Reply-To: <199707020953.TAA05570@mailbox.uq.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Jul 1997, Stephen Hocking wrote: > Has anyone hacked together a a chat script or even a little shell > script that handles trying multiple numbers and retrys in the really neat way > that userland ppp does? I will send it to you by e-mail. Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Wed Jul 2 06:25:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA03445 for hackers-outgoing; Wed, 2 Jul 1997 06:25:23 -0700 (PDT) Received: from argus.tfs.net (pm3-p19.tfs.net [206.154.183.211]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA03434 for ; Wed, 2 Jul 1997 06:25:20 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id TAA01703; Tue, 1 Jul 1997 19:11:21 -0500 (CDT) From: Jim Bryant Message-Id: <199707020011.TAA01703@argus.tfs.net> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: from Andrzej Bialecki at "Jul 1, 97 10:30:54 am" To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Tue, 1 Jul 1997 19:10:05 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > On Mon, 30 Jun 1997, Luigi Rizzo wrote: > > > Apologies if this is off topic, but I found this on the news, and it > > sounds interesting. I haven't been able to try it because the site is > > quite slow from here. > > I tried it - their dealer had this demo on his server in Poland. Well, to > be frank - it's really, really COOOLLL. It's probably impossible with > Xfree86 size to beat this as a whole. > > BUT, perhaps this is a neat idea to make a FreeBSD demo disk, only using > the libdialog instead. Or, to make it a "2,88 Mbyte Web Challenge" for > free Unices. :-) I don't know much about Poland, but I'm the only one I know that even owns a 2.88M floppy drive, and i live in the USA, plus have you ever seen the prices on the blanks? how about this, a single boot floppy, loads in everything into a MFS, then unmounts, and mounts a second application floppy. both floppies being 1.44M. still won't do X, but might be able to do some neet things... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Wed Jul 2 07:52:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA08397 for hackers-outgoing; Wed, 2 Jul 1997 07:52:52 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08390 for ; Wed, 2 Jul 1997 07:52:45 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id QAA03895; Wed, 2 Jul 1997 16:11:21 +0200 (MET DST) Date: Wed, 2 Jul 1997 16:11:20 +0200 (MET DST) From: Andrzej Bialecki To: jbryant@tfs.net cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: <199707020011.TAA01703@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Jul 1997, Jim Bryant wrote: > I don't know much about Poland, but I'm the only one I know that even > owns a 2.88M floppy drive, and i live in the USA, plus have you ever > seen the prices on the blanks? > > how about this, a single boot floppy, loads in everything into a MFS, > then unmounts, and mounts a second application floppy. both floppies > being 1.44M. still won't do X, but might be able to do some neet > things... Ahh, well, I meant exactly this, perhaps I made myself unclear. Forget the 2,88 floppies - they are very much like dinosaurs or kiwi birds - I've never seen one :-) As for the X, I suspect it could be possible to squeeze a VGA server with basic libs on one diskette. I didn't try to do this though :-) OTOH, the gzipped VGA server takes ca. 670 kB (still some place left to fill up the diskette), and some more knowledgable person could cut off unneeded chunks of it. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Wed Jul 2 08:09:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA09394 for hackers-outgoing; Wed, 2 Jul 1997 08:09:40 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA09382 for ; Wed, 2 Jul 1997 08:09:35 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id IAA13729; Wed, 2 Jul 1997 08:09:31 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id IAA11298; Wed, 2 Jul 1997 08:09:29 -0700 (PDT) Date: Wed, 2 Jul 1997 08:09:28 -0700 (PDT) From: Chris Timmons To: Joerg Micheel cc: hackers@FreeBSD.ORG Subject: Re: PDP-11 UNIX source licenses In-Reply-To: <199707011020.MAA18509@negara.fokus.gmd.de > Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think it has also been mentioned in this group that Lions Commentary on UNIX 6th Edition is in print and available from various booksellers on the web. -Chris On Tue, 1 Jul 1997, Joerg Micheel wrote: > Hello, > > the history of making UNIX freely available is old, > but I thought hackers@freebsd might be a community to > look for fellows of Warren Toomey's initiative to get > V1-7 source code licenses from SCO for personal use. > > So, if you are interested, please take a look at: > > http://minnie.cs.adfa.oz.au/PUPS/petition.html > > Thanks, > Joerg > From owner-freebsd-hackers Wed Jul 2 08:32:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10499 for hackers-outgoing; Wed, 2 Jul 1997 08:32:24 -0700 (PDT) Received: from smtp.enteract.com (qmailr@char-star.rdist.org [206.54.252.22]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA10494 for ; Wed, 2 Jul 1997 08:32:21 -0700 (PDT) Received: (qmail 27974 invoked from network); 2 Jul 1997 15:32:19 -0000 Received: from enteract.com (mrfoine@206.54.252.1) by char-star.rdist.org with SMTP; 2 Jul 1997 15:32:19 -0000 Date: Wed, 2 Jul 1997 10:32:18 -0500 (CDT) From: Wayne Baety To: Eugeny Kuzakov cc: Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: pppd chat script with multiple phone numbers? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Jul 1997, Eugeny Kuzakov wrote: > On Wed, 2 Jul 1997, Stephen Hocking wrote: > > > Has anyone hacked together a a chat script or even a little shell > > script that handles trying multiple numbers and retrys in the really neat way > > that userland ppp does? > I will send it to you by e-mail. > > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > kev@lab321.ru > > better yet plz post it so we all can look at it....including myself :) thanx From owner-freebsd-hackers Wed Jul 2 08:37:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10721 for hackers-outgoing; Wed, 2 Jul 1997 08:37:38 -0700 (PDT) Received: from calvary.pascal.org ([207.21.96.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10716 for ; Wed, 2 Jul 1997 08:37:35 -0700 (PDT) Received: from calvary.pascal.org (calvary [207.21.96.1]) by calvary.pascal.org (8.8.5/8.8.5) with ESMTP id IAA03449; Wed, 2 Jul 1997 08:36:31 -0700 (PDT) Message-ID: <33BA757E.344C05E1@compute.com> Date: Wed, 02 Jul 1997 08:36:30 -0700 From: "Freeman P. Pascal IV" Organization: Compute Intensive, Inc. X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, Freeman Pascal Subject: Re: Problems with onboard Adaptec 7870 on Intel ALTServer motherboard... X-Priority: 3 (Normal) References: <33B7D451.443B8236@compute.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have upgraded to 2.2.2-RELEASE as recommended, and that has fixed the system from hanging. The SCSI resets happen quite often, especially during invokations of "find" (no surprise here). Each night the system panics and I find it in the morning asking for a manual fsck. Usually the file-system is trashed, dups and lots of files removed. There's no record of a cause. I suspect that the system is panicing while freeing an inode or something (this would explain lack of messages). I've swapped out the complete machine - only the disks are the same, and the problem persists. I wish I knew more about the scsi drivers, I'd put sometime into tracing the problem. All I've been able to determine is that the error messages are coming from aic7xxx.c. The errors I'm seeing are: sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3 sd0(ahc0:0:0): abort message in message buffer sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3 ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Clearing bus reset Clearing 'in-reset' flag sd0(ahc0:0:0): no longer in timeout sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:2 sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 sd2(ahc0:2:0): Power on, reset, or bus device reset occurred , retries:2 It happens on all of the disks, mostly sd0 since it is the most accessed. Any help would be appreciated - if I can't fix this, I'll have to switch to Solaris 2.5.1 X86 which I don't want to do. -Freeman Freeman P. Pascal IV wrote: > > I'm experiencing problems with 2.2.1-RELEASE on an Intel ALTServer > motherboard. The system installed fine, but it randomly generates > SCSI timeouts that hang the controller and the system. > > I've read in the freebsd-questions archive that the fix was to move > up to 2.1-STABLE. I assume that the fixes would also be in > 2.2.1-RELEASE. > > Has anyone else seen this problem and is there a fix? > > Please say "yes" - I have four of these systems and I want them to > work with FreeBSD. > > -Freeman > -- --------------------------------------------------------------------------- C O M P U T E I N T E N S I V E , I N C . (A Member of the Verio Group) --------------------------------------------------------------------------- Freeman P. Pascal IV Phone Work: (800) 273-5600 Compute Intensive, Inc. Home: (510) 232-0914 8001 Irvine Center Drive FAX: (510) 236-2396 Suite 1130 Email Work: pascal@compute.com Irvine, CA 92618 Home: pascal@pascal.org URL: Work: http://www.compute.com Work: http://www.verio.com Home: http://www.pascal.org --------------------------------------------------------------------------- For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. - John 3:16 (KJV) From owner-freebsd-hackers Wed Jul 2 09:35:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA13253 for hackers-outgoing; Wed, 2 Jul 1997 09:35:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA13234 for ; Wed, 2 Jul 1997 09:34:57 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA06741; Wed, 2 Jul 1997 09:32:32 -0700 From: Terry Lambert Message-Id: <199707021632.JAA06741@phaeton.artisoft.com> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Wed, 2 Jul 1997 09:32:31 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <33BA0339.167EB0E7@bonn-online.com> from "Sebastian Lederer" at Jul 2, 97 09:28:57 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So you still have to keep a list of all active locks (with the > corresponding file handles), and if you encounter a filehandle > which is already on the list, there will be already am open fd for it, > and you don't do the conversion again. No need to close a fd. > The only assumption I am making about the file handle is that it > uniquely identifies a file on the server (and that it can be > converted into an open file,of course). Yes. This is a bad assumption, since the handle is opaque data. An FS is free to give whatever handle it wants to back for any given inode. This includes different handles for two instances of the same inode. Consider the case where the file handle is actually a reference to a "node" in a unioned FS which has been exported. > That F_NONPOSIX fnctl would still make things easier, though. > In fact, it might be extremely useful for all sorts of other things, > I presume. Yes, especially if it overrode other braindamage, or allowed flags that would override othe brain damage. > > No. NFS client locks are not forwarded through a local lockd, [ ... ] > Well, at least the Sun manual page for lockd says : > > [...] > DESCRIPTION > lockd is part of the NFS lock manager, which supports record > locking operations on NFS files. See fcntl(2) and > lockf(3C). The lock manager provides two functions: > > o it forwards fcntl(2) locking requests for NFS > mounted file systems to the lock manager on the > NFS server > > o it generates local file locking operations in > response to requests forwarded from lock managers > running on NFS client machines. > [...] > > I believe in SunOS there is an extension to the nfssys (=nfs_svc in BSD) > system call, using the LM_SVC flag, for this purpose. The nfs_svc system call is a System V -ism. SunOS 4.1.3, the OS on which NFS locking was first implemented, and therefore the reference platform for interoperability testing, does not run a lockd unless you export FS's for other machines to mount. The NFS client code makes the RPC calls directly. Also note that "lockd is /part/ of the NFS lock manager" and "The /lock manager/ provides...". I believe even under SVR4, the lockd does not make the remote requests, the lock manger does... which is to say the NFS VFS module in the kernel. > > The testing in this case is collateral bugs in the namei() code > > changes, which I didn't seperate from the rpc.lockd changes. If > > I can resolve the namei() leaks, Doug will commit the code to the > > FreeBSD source repository, and it will show up on the next CVSup. > > > > Are you running -current? I can probably make a set of diffs against > > a -current source treee this coming weekend (sorry, that's the fastest > > I can get to it; I'm currently job-hunting). > > > > Weekend would be fine. However, I need to upgrade to -current first, my > system is a rather out-of-date 2.2-SNAP. I am still looking for someone > in the vincinity who can put me -current on a tape... Let me know when you have completed the upgrade. It may take you a while. After that, give me the CVS mirroring time, and I will try to come as close as possible when cutting the patches. > In the rpc.lockd source directory is a test program that issues fake rpc > locking calls. I've already used it for a little testing. I will look at it. Since I've been doing the kernel code for this, I might be able to use it as a basis for the client. > I could also probably get the free version of SCO UNIX and install it on > one of my boxes. IF SCO UNIX actually does nfs locking, that could be > used for "real life" testing. Actually, I believe there is a similar offer for a 2 user Solaris. I was waiting until I got a second JAZ drive for this, myself. I think the SCO offer is SVR3 based (I may be wrong), and the SVR3 lockd code is notoriously flawed. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 2 09:44:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA13688 for hackers-outgoing; Wed, 2 Jul 1997 09:44:22 -0700 (PDT) Received: from quasi.bis.co.il (quasi.bis.co.il [192.115.114.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA13680 for ; Wed, 2 Jul 1997 09:44:17 -0700 (PDT) Received: (from mdukhan@localhost) by quasi.bis.co.il (8.8.3/8.8.3) id TAA00505; Wed, 2 Jul 1997 19:55:02 GMT Date: Wed, 2 Jul 1997 19:55:02 GMT From: Meir Dukhan Message-Id: <199707021955.TAA00505@quasi.bis.co.il> To: freebsd-hackers@freebsd.org Subject: Help with a tcpdump output Cc: mdukhan@bis.co.il Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, We encounter some trouble while trying to print from an IBM Mainframe to a printer connected to a Freebsd 2.1.5 system. Here the tcpdump of the tentative, which failed with a EPIPE (Broken pipe) error message in the Mainframe log file. Could someone explain why 4 SYN packet (when I was expecting only 2: SYN and SYN/ACK), and why so many RST ? Also, when viewing the data with tcpshow one packet contain "lpd: malformed from address", maybe it can help. 12:30:08.472197 mainframe.1136 > freebsd-215.printer: S 3428224:3428224(0) win 8192 12:30:08.472197 freebsd-215.printer > mainframe.1136: S 586300417:586300417(0) ack 3428225 win 16616 (DF) 12:30:11.472197 mainframe.1136 > freebsd-215.printer: S 3428224:3428224(0) win 8192 12:30:11.472197 freebsd-215.printer > mainframe.1136: . ack 1 win 16616 (DF) 12:30:14.192197 freebsd-215.printer > mainframe.1136: S 586300417:586300417(0) ack 3428225 win 16616 (DF) 12:30:14.232197 mainframe.1136 > freebsd-215.printer: . ack 1 win 8192 12:30:14.242197 mainframe.1136 > freebsd-215.printer: P 1:83(82) ack 1 win 8192 12:30:14.292197 freebsd-215.printer > mainframe.1136: P 1:29(28) ack 83 win 16534 (DF) 12:30:14.292197 freebsd-215.printer > mainframe.1136: F 29:29(0) ack 83 win 16616 (DF) 12:30:14.372197 mainframe.1136 > freebsd-215.printer: . 83:619(536) ack 1 win 8192 12:30:14.372197 freebsd-215.printer > mainframe.1136: R 586300418:586300418(0) win 0 12:30:14.412197 mainframe.1136 > freebsd-215.printer: . 619:1155(536) ack 1 win 8192 12:30:14.412197 freebsd-215.printer > mainframe.1136: R 586300418:586300418(0) win 16384 12:30:14.412197 mainframe.1136 > freebsd-215.printer: . ack 29 win 8164 12:30:14.412197 freebsd-215.printer > mainframe.1136: R 586300446:586300446(0) win 16384 12:30:14.412197 mainframe.1136 > freebsd-215.printer: . ack 30 win 8163 12:30:14.412197 freebsd-215.printer > mainframe.1136: R 586300447:586300447(0) win 16384 12:30:14.422197 mainframe.1136 > freebsd-215.printer: R 3429379:3429379(0) win 0 Thanks in advance, -- Meir ps: please cc to mdukhan@bis.co.il, as I am not on this list, thanks. From owner-freebsd-hackers Wed Jul 2 09:57:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14201 for hackers-outgoing; Wed, 2 Jul 1997 09:57:49 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA14193 for ; Wed, 2 Jul 1997 09:57:45 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wjSeN-00018c-00; Wed, 2 Jul 1997 09:53:03 -0700 Date: Wed, 2 Jul 1997 09:53:03 -0700 (PDT) From: Tom Samplonius To: "Freeman P. Pascal IV" cc: freebsd-hackers@freebsd.org Subject: Re: Problems with onboard Adaptec 7870 on Intel ALTServer motherboard... In-Reply-To: <33BA757E.344C05E1@compute.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Jul 1997, Freeman P. Pascal IV wrote: > I have upgraded to 2.2.2-RELEASE as recommended, and that has You should now cvsup to 2.2-stable, which contains additional patches. .. > lots of files removed. There's no record of a cause. I suspect > that the system is panicing while freeing an inode or something > (this would explain lack of messages). Did you check "dmesg" for a cause? If the disk is unwritable, kernel messages are written into a RAM message buffer which is preserved accross warm boots. > I've swapped out the complete machine - only the disks are the > same, and the problem persists. Somes drives just suck, and you will have problems with every os. The Grand Prix is notorious. I hear this everywhere I go, whether Windows NT or Netware. > I wish I knew more about the scsi drivers, I'd put sometime into > tracing the problem. All I've been able to determine is that the > error messages are coming from aic7xxx.c. > > The errors I'm seeing are: > > sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3 > sd0(ahc0:0:0): abort message in message buffer > sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3 > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > Clearing bus reset > Clearing 'in-reset' flag > sd0(ahc0:0:0): no longer in timeout > sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 > , retries:3 > sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 > sd1(ahc0:1:0): Power on, reset, or bus device reset occurred > , retries:2 This is bad. The drive is saying it was power cycled. You should swap this drive. > sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 > sd2(ahc0:2:0): Power on, reset, or bus device reset occurred > , retries:2 > > > It happens on all of the disks, mostly sd0 since it is the most > accessed. > > Any help would be appreciated - if I can't fix this, I'll have to > switch to Solaris 2.5.1 X86 which I don't want to do. > > -Freeman Tom From owner-freebsd-hackers Wed Jul 2 10:42:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16642 for hackers-outgoing; Wed, 2 Jul 1997 10:42:46 -0700 (PDT) Received: from yacko.netgazer.net (yacko.netgazer.net [208.12.177.63]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA16637 for ; Wed, 2 Jul 1997 10:42:41 -0700 (PDT) Received: from [208.12.177.224] (furball.netgazer.com [208.12.177.224]) by yacko.netgazer.net (8.8.3/8.7.3) with ESMTP id MAA09440 for ; Wed, 2 Jul 1997 12:47:41 GMT Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 2 Jul 1997 12:49:08 -0500 To: freebsd-hackers@freebsd.org From: "Darrin R. Woods" Subject: Make world problems Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Flame retardent suit on} Ok, I know that I should read all of the mail that goes through my mailbox, but I have to tell the truth, most of the time if it does not involve something that I'm interested in or something that I might find useful I delete it without reading it. My problem is this, I loaded 2.2.2 on one of my systems and am now trying to make world so that all the binaries will work with longer usernames. Make world dies, and I seem to remember a thread about a week ago of people also having a make world problem. I have tried to search the archives but have been unable to find them. Could someone please tell me what I might be able to do to get make world working or if there is a fix in the works. If this was not what the earlier thread was on, I can provide you with more detail of what is dying. Thanks, Darrin R. Woods | "I'm so happy that I, can't stop crying." Director Operations | --- Sting Netgazer Solutions, Inc. | Dallas, Texas 972.702.9119 | work: http://www.netgazer.net My employer most whole-heartedly denies everything I say From owner-freebsd-hackers Wed Jul 2 11:19:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA17972 for hackers-outgoing; Wed, 2 Jul 1997 11:19:48 -0700 (PDT) Received: from monoid.cs.tcd.ie (ts19-12.dublin.indigo.ie [194.125.134.162]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17967 for ; Wed, 2 Jul 1997 11:19:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by monoid.cs.tcd.ie (8.8.5/8.8.5) with SMTP id TAA01764 for ; Wed, 2 Jul 1997 19:19:41 +0100 (BST) Message-Id: <199707021819.TAA01764@monoid.cs.tcd.ie> X-Authentication-Warning: monoid.cs.tcd.ie: localhost [127.0.0.1] didn't use HELO protocol To: freebsd-hackers@freebsd.org Subject: Is the union filesystem still broken? X-Address: Department of Computer Science, Trinity College, Dublin 2, Ireland. X-Phone: (Home)+353-(0)1-8204643 (College)+353-(0)1-7021321 X-PGP: Public Key on Request MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1759.867867579.1@monoid> Date: Wed, 02 Jul 1997 19:19:40 +0100 From: Colman Reilly Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If so, how broken is it? Colman From owner-freebsd-hackers Wed Jul 2 11:54:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19577 for hackers-outgoing; Wed, 2 Jul 1997 11:54:57 -0700 (PDT) Received: from yacko.netgazer.net (yacko.netgazer.net [208.12.177.63]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA19572 for ; Wed, 2 Jul 1997 11:54:54 -0700 (PDT) Received: from [208.12.177.224] (furball.netgazer.com [208.12.177.224]) by yacko.netgazer.net (8.8.3/8.7.3) with ESMTP id NAA09992 for ; Wed, 2 Jul 1997 13:59:28 GMT Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 2 Jul 1997 14:00:54 -0500 To: freebsd-hackers@freebsd.org From: "Darrin R. Woods" Subject: Re: Make world problems Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Could someone please tell me what I might be able to do to get make world >>working or if there is a fix in the works. If this was not what the >>earlier thread was on, I can provide you with more detail of what is dying. > >If it looks like it's dying from a problem with include files, (either can't >find one explicitly, or is complaining about non-existent definitions), you >might win by doing a 'make includes' in /usr/src, before re-starting your >'make world'... Well I think it got further, but not sure. Here is where it stops: ===> rtld /usr/src/gnu/usr.bin/ld/rtld -> /usr/obj/gnu/usr.bin/ld/rtld cd /usr/src/usr.bin/ar && make depend all install cleandir obj rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a -I/usr/src/usr.bin/ar $files; fi files="/usr/src/usr.bin/ar/append.c /usr/src/usr.bin/ar/ar.c /usr/src/usr.bin/ar /archive.c /usr/src/usr.bin/ar/contents.c /usr/src/usr.bin/ar/delete.c /usr/src/ usr.bin/ar/extract.c /usr/src/usr.bin/ar/misc.c /usr/src/usr.bin/ar/move.c /usr/ src/usr.bin/ar/print.c /usr/src/usr.bin/ar/replace.c"; if [ "$files" != "" ]; t hen mkdep -a -I/usr/src/usr.bin/ar $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a -I/usr/src/usr.bin/ar $fi les; fi cc -O -I/usr/src/usr.bin/ar -c /usr/src/usr.bin/ar/append.c cc -O -I/usr/src/usr.bin/ar -c /usr/src/usr.bin/ar/ar.c cc -O -I/usr/src/usr.bin/ar -c /usr/src/usr.bin/ar/archive.c /usr/src/usr.bin/ar/archive.c: In function `put_arobj': /usr/src/usr.bin/ar/archive.c:228: structure has no member named `ts_sec' /usr/src/usr.bin/ar/archive.c:234: structure has no member named `ts_sec' /usr/src/usr.bin/ar/archive.c:238: structure has no member named `ts_sec' *** Error code 1 Stop. *** Error code 1 Stop. Any ideas? Darrin R. Woods | "I'm so happy that I, can't stop crying." Director Operations | --- Sting Netgazer Solutions, Inc. | Dallas, Texas 972.702.9119 | work: http://www.netgazer.net My employer most whole-heartedly denies everything I say From owner-freebsd-hackers Wed Jul 2 13:43:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA24972 for hackers-outgoing; Wed, 2 Jul 1997 13:43:46 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA24953 for ; Wed, 2 Jul 1997 13:43:37 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id WAA31593; Wed, 2 Jul 1997 22:42:10 +0200 Message-ID: <33BABD1C.41C67EA6@bonn-online.com> Date: Wed, 02 Jul 1997 22:42:04 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707021632.JAA06741@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > Yes. This is a bad assumption, since the handle is opaque data. > An FS is free to give whatever handle it wants to back for any > given inode. This includes different handles for two instances > of the same inode. > > Consider the case where the file handle is actually a reference to > a "node" in a unioned FS which has been exported. > > > That F_NONPOSIX fnctl would still make things easier, though. > > In fact, it might be extremely useful for all sorts of other things, > > I presume. > > Yes, especially if it overrode other braindamage, or allowed flags > that would override othe brain damage. So if we didn't have the F_NONPOSIX fcntl we would only be able to support locking on exported ufs filesystems, nothing else. That would still seem to be quite useful. > The nfs_svc system call is a System V -ism. SunOS 4.1.3, the OS on > which NFS locking was first implemented, and therefore the reference > platform for interoperability testing, does not run a lockd unless > you export FS's for other machines to mount. The NFS client code > makes the RPC calls directly. But then the kernel on the nfs client would need to act as an rpc server, since the replies from the server's lockd are sent explicitly to the client's nlockmgr rpc service as seperate rpc calls. The rpc.lockd skeleton from Andrew Gordon does the replies this way, I've already checked that. You can simply start the rpc.lockd and use the "test" program to make a fake locking rpc to localhost, and the reply will not go to the test program, but to the lockd itself. Another problem would be that the nlockmgr service port is dynamically allocated, unlike the nfs service port. You could probably specify the nlockmgr port as a mount option, but what if the server reboots and the port number changes? The kernel would have to do portmapper lookups? > > I could also probably get the free version of SCO UNIX and install it on > > one of my boxes. IF SCO UNIX actually does nfs locking, that could be > > used for "real life" testing. > > Actually, I believe there is a similar offer for a 2 user Solaris. > I was waiting until I got a second JAZ drive for this, myself. I > think the SCO offer is SVR3 based (I may be wrong), and the SVR3 > lockd code is notoriously flawed. You're right, the free SCO Version is SVR3 based. And you can bet that its lockd code is flawed (one could of course consider SVR3 itself as a flaw). Solaris would surely be preferable, but the current price list shows Solaris 2.5.1 for x86 as about 5000 DM (about 2700 US-$). As soon as I see any special offer there I will probably get it. Best regard, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Wed Jul 2 13:55:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA25586 for hackers-outgoing; Wed, 2 Jul 1997 13:55:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA25579 for ; Wed, 2 Jul 1997 13:55:13 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA08047; Wed, 2 Jul 1997 13:52:54 -0700 From: Terry Lambert Message-Id: <199707022052.NAA08047@phaeton.artisoft.com> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Wed, 2 Jul 1997 13:52:54 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <33BABD1C.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 2, 97 10:42:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But then the kernel on the nfs client would need to act as an rpc > server, since the replies from the server's lockd are sent > explicitly to the client's nlockmgr rpc service as seperate rpc calls. > The rpc.lockd skeleton from Andrew Gordon does the replies this way, > I've already checked that. > You can simply start the rpc.lockd and use the "test" program to make > a fake locking rpc to localhost, and the reply will not go to the > test program, but to the lockd itself. > Another problem would be that the nlockmgr service port is dynamically > allocated, unlike the nfs service port. You could probably specify the > nlockmgr port as a mount option, but what if the server reboots and the > port number changes? The kernel would have to do portmapper lookups? How do you think NFS server to NFS client responses operate? The NFS client has to do the same types of things. > Solaris would surely be preferable, but the current price list shows > Solaris 2.5.1 for x86 as about 5000 DM (about 2700 US-$). > As soon as I see any special offer there I will probably get it. I believe there is a student offer, if you know a student. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 2 17:05:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA02554 for hackers-outgoing; Wed, 2 Jul 1997 17:05:09 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02532 for ; Wed, 2 Jul 1997 17:05:02 -0700 (PDT) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id UAA13602 for ; Wed, 2 Jul 1997 20:02:38 -0400 (EDT) Date: Wed, 2 Jul 1997 20:14:52 -0400 (EDT) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: hackers list FreeBSD Subject: Rod Grimes on vacation? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Maybe not the right list for this... but he's a hacker of freebsd, right? ;-) I've been trying to reach Rod Grimes of Accurate Automation for a week or two with no luck. Is he on vacation or something? Is he still in the business of selling FreBSD make-world-tested motherboards? Thanks, --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 2 17:21:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA03448 for hackers-outgoing; Wed, 2 Jul 1997 17:21:46 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA03440 for ; Wed, 2 Jul 1997 17:21:41 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Wed, 2 Jul 1997 20:21:10 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA06134; Wed, 2 Jul 97 20:21:09 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id UAA04829; Wed, 2 Jul 1997 20:19:25 -0400 Message-Id: <19970702201925.23792@ct.picker.com> Date: Wed, 2 Jul 1997 20:19:25 -0400 From: Randall Hopper To: hackers@freebsd.org Subject: suid "mountzip" -- UFS works but MSDOS doesn't (?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a suid perl script that I use to mount file systems on my ZIP drive (attached). It works fine for for UFS, but the MSDOS mount denies permission. Any ideas why? > mountzip /dev/sd0s1 on /zip: Incorrect super block. msdos: /dev/sd0s4: Permission denied Mount failed __________________________________________________________________________ > cat /opt/bin/mountzip # cat /opt/bin/mountzip #!/usr/bin/suidperl -w $ENV{'PATH'} = '/bin:/usr/bin:/usr/sbin:/sbin'; $ENV{'SHELL'} = '/bin/sh' if defined $ENV{'SHELL'}; $ENV{'IFS'} = '' if defined $ENV{'IFS'}; ( !system( "mount /zip" ) && print "/zip mounted\n" ) || ( !system( "mount /doszip" ) && print "/doszip mounted\n" ) || die "Mount failed\n"; __________________________________________________________________________ > ls -l /opt/bin/mountzip -rws--x--- 1 root wheel 326 May 4 09:34 /opt/bin/mountzip* > ls -l /sbin/mount /sbin/mount_msdos -r-xr-xr-x 1 bin bin 69632 Mar 25 14:42 /sbin/mount* -r-xr-xr-x 1 bin bin 139264 Mar 25 14:43 /sbin/mount_msdos* > grep zip /etc/fstab /dev/sd0s1 /zip ufs rw,noauto 0 0 /dev/sd0s4 /doszip msdos ro,noauto 0 0 > ls -l /dev/sd0s[14] brw-r----- 1 root operator 4, 0x00020002 May 5 19:36 /dev/sd0s1 brw-r----- 1 root operator 4, 0x00050002 May 5 19:36 /dev/sd0s4 > ls -ld /zip /doszip drwxr-xr-x 2 root wheel 512 May 5 19:44 /doszip/ drwxr-xr-x 2 root wheel 512 May 5 19:44 /zip/ BTW, this is on 2.2.1. Randall Hopper From owner-freebsd-hackers Wed Jul 2 20:06:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15003 for hackers-outgoing; Wed, 2 Jul 1997 20:06:16 -0700 (PDT) Received: from argus.tfs.net (pm3-p26.tfs.net [206.154.183.218]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14981 for ; Wed, 2 Jul 1997 20:05:43 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id WAA02500; Wed, 2 Jul 1997 22:04:41 -0500 (CDT) From: Jim Bryant Message-Id: <199707030304.WAA02500@argus.tfs.net> Subject: Re: PDP-11 UNIX source licenses In-Reply-To: from Chris Timmons at "Jul 2, 97 08:09:28 am" To: skynyrd@opus.cts.cwu.edu (Chris Timmons) Date: Wed, 2 Jul 1997 22:04:40 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > I think it has also been mentioned in this group that Lions Commentary on > UNIX 6th Edition is in print and available from various booksellers on the > web. > > -Chris > > On Tue, 1 Jul 1997, Joerg Micheel wrote: > > > Hello, > > > > the history of making UNIX freely available is old, > > but I thought hackers@freebsd might be a community to > > look for fellows of Warren Toomey's initiative to get > > V1-7 source code licenses from SCO for personal use. > > > > So, if you are interested, please take a look at: > > > > http://minnie.cs.adfa.oz.au/PUPS/petition.html > > > > Thanks, > > Joerg hmmm... neet! i am running "multi-user" in another window... this thing will run real sco v7 binaries, does anyone have a copy of rsx-11m i can borrow, rsts/e, etc...? dd it for me puleeze!!!!! i had so much phun with that os!@# any sources for 2BSD around?!@ this is cool! jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Wed Jul 2 21:59:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA19130 for hackers-outgoing; Wed, 2 Jul 1997 21:59:34 -0700 (PDT) Received: from lab321.ru (root@anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19122 for ; Wed, 2 Jul 1997 21:59:27 -0700 (PDT) Received: from localhost (kev@localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru SLmail95 v1.0.32 with SMTP id LAA04448 for ; Thu, 3 Jul 1997 11:59:56 +0700 (OSD) Date: Thu, 3 Jul 1997 11:59:55 +0700 (OSD) From: Eugeny Kuzakov To: hackers@freebsd.org Subject: Re: pppd chat script with multiple phone numbers? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-765050143-867905995=:3602" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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-765050143-867905995=:3602 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 2 Jul 1997, Wayne Baety wrote: I am sending it to maillist, because of big number of people who wanted it. Put it to /etc/ppp and try... Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru --0-765050143-867905995=:3602 Content-Type: APPLICATION/octet-stream; name="multiphoneisp.tar.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sIAAAAAAAAA+1ZbXMayRH2V/ZXtDE57DKCXZYXWVckwRKKKUuCAlx3TpTy DbsjMcXuDtnZBeFU8tvTPbMLEuacD+Z8VQkDkmreenr69elRmAaJWMxkxIVa 1J79Jg0adrvZhGdAzd75m3Wg5TZbLdeut+oATt1uO8+g+duw87SlKmExwLNY yuRr61YzzoPvwdD3beET/S8WixMZHfoMx7bbjcav6t912g2j/0bDsdsu6t91 XfsZ2IdmZF/7P9f/i+e1qYhqama9sF7A2IvFIoFEgohEIljCgQEaBXgyiriX CBlVYTITCvCbzDjciVglsGBxAvKORpDIgomYekoTU9sNkUyQnOJeGvPdVcAM QU/6XCERhkuWQolpwGElkpmeLC9UGVeEIYv8KsA7ueJLHldAJEReiXAR8Kq+ yPNvakhA82x4gzsZkxB8qFfdqVuF/h2sZQqpEtE9jtUB2QGeeBXcRxMR5z7E PJRLDkWfE7fFH4oLHiuhkiJJi4U8ifU9N7S4OWJJq2QEAd4txkuzyJxa0ctm bMmjcgK+YAE66okhXj17dZgrc+SCBE+yzrhEdqpwjmzcc1IRXY37VetqcN69 +tQfdh6q9GGFF3AlPRZAfwjM9/FuqPE7mEdyhRZzsY5YKDzogF3VH2vUux5M elsCUyQwQomhwT2lgNYgYjwRbmQcsiBYb0jc9CbX3fH7Tr3ZrOY/dkFfAxax RHEjt0nI1JzoGMat4WA06dR8vqx5KWM/W+Nhr3fRcU8btq3t5rFtB3ghsvjM snNrWM2EN9MaMMt08NQmEMh7UqnAG8Mw4AylSXqlRWyqZJAm5DBo0CgNnht8 adidvIMliwUjWzduglRwpw94uHEK7X0gF8YD4eVEgi9BSVrBoEzBqwzM82Qa IYcyDXyYki9m7iaSNcwkkle0jywIxVJFq7Eu+t2r3ujT+HzUH6Jk0IopCdRQ 5HhBHmuh9PNY8IgX5ANnaBIWaQKhVHkE0A5KUtPMKnMHvNbGb41oKoYRpIDu dc8T4+Ao83k52wrodkqGWpv3aIzojylKHuUW4nq80UoEQSatlYznVa16ptaR F7KFcUrlsQU3C9EgQmGOGQ6HEIhoToGOduoIo6WV8ACNhk6OUZsiehL4PqIH knuseOARX7g7ZHPS/Ro87SI6cqmt0V5oWedGUPb5HcN8G0u0hM0thYkAqKWY R0mwRhLk5shMthz0ejoNgwFHQjGxeI8KWbE1hTv+wD2opSquKYrlOo74fJre kwnPUTcYJsCLE+VhnC2RC0BJGz7cWgXho1m07K3c6nbXxpbL7vIS5oaYDaXc 7c9KGwcmGiYMbdytlLkmZCFvY7+lJ9Zm/d6579h28V/u9oc947/gv5bdbG/w f6tpE/5rO/Uj/vseDfEfBQ7KdYFGglNGWPAb0YQBFP0s12gUUMHEuSak5kuu aFSjOhR+5BN6VLPqYU799pYBAQJDWxBEMQwDd2CyeZIwDKzkKwQBFf9HyiOP oCd/wBs6msI1exBhGkKUhlOuoS5u4yFhXQzlMWeeAbWYcrjBEGblS/XKuu7+ /Kk7mfSuh5Nxx7GQ2gUP2BpzerLiHLMAbc7SbU51i7PZlm86SgWcL5AE5n7K REWnqYoa0zpNQgcy8lUFR8NsEEIRYb6pEKKtWuOrXm/46aJ31f3YcZRl9W8u B5PJR4OhMAkvpwcUec5+IDI0sSMavGPXpzyzygfy7LkS2mopCylusu1dGum8 DWU07QC/ZRQfwmp9S1pA6iNs4SHUrFrDd4ObntOpN5oNp2l6dexhe2N6Lvbc 07pjeg2aa9ZbptdEFNp2G67ptWju1Mn2tXWvlc2ddupuo+Vm+97QeadO27IO JsVHBYVGp7qiz7BrhYY0pMyA/oIpgploJBqiEdAQkcaNaSJDRL8kurUGVnGG TU11gzsQneBaIhYCTeu6CNGYOSQrhQxEy3aoDOUtWZByRcile34++HAz6Wis RajYGnbH458Go4sOsYbYzLeobXRpytJAfObwEl5Z/7Qogei4xb2ZhJMoA6u4 gjxTQ58qNvgjlDLTNVso6NE2xG0JnCxh0r/uDT5MwIVyGcrdyV/x9+D9yevX r2+9k8F77LEkrAfuQ+OHmbMzpynGPEnjyPrX4TS5Lca1pbKtO+D0RiKkoSxw kDy2spjEaxLB1odKzmMp7EqgQA2xXPct4sNCoXwbvf0w/ngbl3eHbwbQvRn/ 1Bvtnzvvjkb9bHJ3juAfTNDuv5wd9W/+gt/b+Dain023TMsy5RQKp3bGZRn3 dycXkzerkmNGzgc3N71zIlbO1pBNnZ2c6D+FUmZqZkpbFg7m1vbF3f8AXY/i Alp5JLiPfGglY7T5GxRLfypiKVu0i/D3H42xZ0hGR39b9+7El6Z5JZKEajCK x/tsUj/E0CRmkKebe1Q37Sz/7Q0Oy5rdCLxrefh9+aUbFvPMmOWmbPMZmSCG 9dLj9FaExxfThLYmjdWKDsv7h+v7h939w439w839w639w+39w6f7h98cUjuX udw3r3M6DFJANRWeLngjleoHHPRp8yqma1hdeRMESLBqzIBCiHiCXuSmPHsc qcA0TR4jtFkaJ/o57UA36O/jGm+zl+n8JUGndGIbSWgqF2SbXyADSKNEBGCe YtQKR3BxZn4d21rN6N3lDH7Ey2ld5VO/8IcFqis31Nfg/GI8fcPr1vGff8X1 t8bP41jG6N5KxvEa/16mCBVvn9Nn14XzkOHsDxmDOW4fpQH//Cv7Mw/csP84 RmVDmt0dh8tZLzw5vLAbhIqlR+CvaPmUeH7vcuXYDtye1v+jXvfiunfoM7D+ b32l/oeG29zU/023TfW/7TaP9f/3aO9EBboYQp5bls4KyUpu/iVDz5j3EWL3 zT9AdDCmp88szWnDUZTTEezH0B8Pq1YfUwrLHq/5A6P/ySgT2+9kivsxtpsX SizyYoEpR7+tWlbhEk8hzIHFtNKJbr3z3oo8npxYhbc4rQs+jnVrL73nuOd9 +pnN5dIqFK7YVMYskfEa3LqDVcIgVPMKjFKlBMOSoVCY8+WfAzbF2WqcYn+W JIuzWm21WlU3w7V/46pjtDu2Yzu2Yzu2Yzu2/8X2H6flkXgAKAAA --0-765050143-867905995=:3602-- From owner-freebsd-hackers Thu Jul 3 00:01:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA24845 for hackers-outgoing; Thu, 3 Jul 1997 00:01:50 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA24827 for ; Thu, 3 Jul 1997 00:01:32 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id JAA02704; Thu, 3 Jul 1997 09:57:24 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Thu, 3 Jul 1997 09:57:23 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: jbryant@tfs.net cc: Chris Timmons , freebsd-hackers@FreeBSD.ORG Subject: Re: PDP-11 UNIX source licenses In-Reply-To: <199707030304.WAA02500@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Jul 1997, Jim Bryant wrote: > In reply: > > I think it has also been mentioned in this group that Lions Commentary on > > UNIX 6th Edition is in print and available from various booksellers on the > > web. > > > > -Chris > > > > On Tue, 1 Jul 1997, Joerg Micheel wrote: > > > > > Hello, > > > > > > the history of making UNIX freely available is old, > > > but I thought hackers@freebsd might be a community to > > > look for fellows of Warren Toomey's initiative to get > > > V1-7 source code licenses from SCO for personal use. > > > > > > So, if you are interested, please take a look at: > > > > > > http://minnie.cs.adfa.oz.au/PUPS/petition.html > > > > > > Thanks, > > > Joerg > > hmmm... neet! i am running "multi-user" in another window... > > this thing will run real sco v7 binaries, does anyone have a copy of > rsx-11m i can borrow, rsts/e, etc...? dd it for me puleeze!!!!! i > had so much phun with that os!@# There was an article in one of the last issues of DTJ (Digital Technical Journal) about preserving the history of computing. It had a lot of info both on actual preserved ancient PDPs (not just -11s, but also the more obscure 18bit models), and on emulators for these. The URL is: http://www.digital.com/info/DTJN00/ > > any sources for 2BSD around?!@ > > this is cool! > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam > Nadav From owner-freebsd-hackers Thu Jul 3 01:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA28161 for hackers-outgoing; Thu, 3 Jul 1997 01:21:26 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA28155 for ; Thu, 3 Jul 1997 01:21:05 -0700 (PDT) Received: (qmail 8152 invoked by uid 1000); 3 Jul 1997 08:18:58 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 03 Jul 1997 01:18:58 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: PPP Panic in RELENG_2_@ (29-Jun-97) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Under medium load (128Kbps ISDN, large nfs recursive copy + ftp mirror of a large archive), the system panics with: ... page not present at pppgterm + 0x143 lccb 0(%edx, %eax,1) Trace: pppgetm pppinput siopoll doreti_swi Any suggestions? Simon From owner-freebsd-hackers Thu Jul 3 02:42:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA01232 for hackers-outgoing; Thu, 3 Jul 1997 02:42:43 -0700 (PDT) Received: from gw.mark-itt.ru (root@gw.MARK-ITT.ru [193.124.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01185 for ; Thu, 3 Jul 1997 02:41:13 -0700 (PDT) Received: from szan.UUCP (uucp@localhost) by gw.mark-itt.ru (8.7.5.R.ML.S/Mark-ITT) with UUCP id OAA01315 for hackers@freebsd.org;Thu, 3 Jul 1997 14:38:09 +0500 (KSD) Received: by szan.udm.ru (UUPC/@ v7.00, 07Jan97) id AA08544; Thu, 3 Jul 1997 14:22:39 +0500 (MSD) From: "Juri A. Kuniver" To: hackers@freebsd.org Date: Thu, 3 Jul 1997 14:15:09 Subject: Help, please ! X-Confirm-Reading-To: Juri A. Kuniver X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail v3.22 Message-Id: Lines: 9 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Can you help us ? We have the net equipment 100 VG LAN. Is there the way to use this equipment together with FreeBSD 2.2.1 ? We are interested how and where to find the drivers for lan card 10/100 VG ISA LAN so that this card can work together with FreeBSD. Help us, please ! --- Juri A. Kuniver War is too serious to entrust it to soldiers From owner-freebsd-hackers Thu Jul 3 03:12:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA02187 for hackers-outgoing; Thu, 3 Jul 1997 03:12:58 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA02178 for ; Thu, 3 Jul 1997 03:12:52 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id MAA02196; Thu, 3 Jul 1997 12:12:37 +0200 Message-ID: <33BB7B0C.41C67EA6@bonn-online.com> Date: Thu, 03 Jul 1997 12:12:28 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707022052.NAA08047@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > How do you think NFS server to NFS client responses operate? The > NFS client has to do the same types of things. No,it does not. That's exactly the point. The nfs client does a rpc call (e.g. NFSPROC_READ) to the nfs rpc service on the nfs server, and gets an ordinary rpc reply as a result. The locking client does a rpc call to the nlockmgr rpc service on the nfs server (e.g. NLM_LOCK_MSG). No rpc reply is sent back. The result of the locking operation is then sent as an entirely different rpc call from the nfs server to the nlockmgr service on the nfs client (NLM_LOCK_RES). That is, for the moment the nfs client becomes a server for the nlockmgr service, and the rpc.lockd becomes the rpc client. So there MUST be a rpc.lockd running on the nfs client to gather these result messages. And this cannot be done in the kernel because the nlockmgr service must provide the service for both sides of the locking protocol simultaneously. There is only one service with functions for both sides of the protocol. And since rpc.lockd does provide the nlockmgr service, it has to run on the server and the client. If you don't believe me, please take a look at /usr/include/rpcsvc/nlm_prot.x and Andrew's rpc.lockd code. It handles the protocol the way I described it. Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Thu Jul 3 03:59:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA03545 for hackers-outgoing; Thu, 3 Jul 1997 03:59:21 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA03537 for ; Thu, 3 Jul 1997 03:59:16 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id MAA05444 for ; Thu, 3 Jul 1997 12:59:06 +0200 (MET DST) Date: Thu, 3 Jul 1997 12:59:06 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: Crypto (MD5,DES) filesystem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! I'm looking for an implementation of crypto filesystem for FreeBSD. Perhaps it doesn't exist at all (yet). I'm ignorant in filesystems intrinsics, so don't laugh, but here's my idea how it could be done: * take the nullfs and modify it, so that in every write it makes an XOR of md5-hashed password with the actual block contents. On every read do the contrary. In other words, to slide in encryption between vnode and nullfs layers. * modify the mount_null (let's call it mount_crypto) to get a password from user. Then user could issue the following command (as it is not required to be superuser to do such mounts): mount_crypto -e md5 /home/user/plaintext/locked /home/user/unlocked and every file in directory 'locked' would be encrypted/decrypted on the fly. The most important being the contents of the disk blocks are always encrypted (no need to write decrypted blocks anywhere). Now, be kind, but what do you think of it? Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Thu Jul 3 05:22:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA06622 for hackers-outgoing; Thu, 3 Jul 1997 05:22:14 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA06616 for ; Thu, 3 Jul 1997 05:22:08 -0700 (PDT) Received: from ws6303-f.gud.siemens.co.at (root@firix [10.1.143.100]) by zwei.siemens.at with ESMTP id OAA28945; Thu, 3 Jul 1997 14:21:33 +0200 (MET DST) Received: from ws6423.gud.siemens.at (ws6423-f) by ws6303-f.gud.siemens.co.at with ESMTP (1.40.112.8/16.2) id AA095032491; Thu, 3 Jul 1997 14:21:31 +0200 Received: by ws6423.gud.siemens.at (SMI-8.6/SMI-SVR4) id OAA18858; Thu, 3 Jul 1997 14:12:20 +0200 Date: Thu, 3 Jul 1997 14:12:20 +0200 From: lada@ws6303.gud.siemens.at (marino.ladavac@siemens.at) Message-Id: <199707031212.OAA18858@ws6423.gud.siemens.at> To: freebsd-hackers@FreeBSD.ORG, abial@korin.warman.org.pl Subject: Re: Crypto (MD5,DES) filesystem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Md5: zzZ/vKEQei5J2XC9yvQVUA== Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 3 13:08:44 MET 1997 > Date: Thu, 3 Jul 1997 12:59:06 +0200 (MET DST) > From: Andrzej Bialecki > To: freebsd-hackers@FreeBSD.ORG > Subject: Crypto (MD5,DES) filesystem > Mime-Version: 1.0 > X-Loop: FreeBSD.org > > > Hi! > > I'm looking for an implementation of crypto filesystem for FreeBSD. > Perhaps it doesn't exist at all (yet). Not that I know of. Crypto filesystems that are not worse than useless are not easy. > > I'm ignorant in filesystems intrinsics, so don't laugh, but here's my idea > how it could be done: > > * take the nullfs and modify it, so that in every write it makes an XOR of > md5-hashed password with the actual block contents. On every read do the > contrary. In other words, to slide in encryption between vnode and nullfs > layers. Hopefully not. You really should use an encryption method that needs more than a couple of seconds to break it. Otherwise, the layering sounds logical. > > * modify the mount_null (let's call it mount_crypto) to get a password > from user. > > Then user could issue the following command (as it is not required to be > superuser to do such mounts): > > mount_crypto -e md5 /home/user/plaintext/locked /home/user/unlocked > And then everyone who has read access to the mounted files gets to see them as plaintext. Anyone who happens to be root gets all of the contents for free. This is worse than useless because it conveys a false feeling of security unless you consider the implications (then it becomes just plain useless:) > and every file in directory 'locked' would be encrypted/decrypted on the > fly. The most important being the contents of the disk blocks are always > encrypted (no need to write decrypted blocks anywhere). But just as bad, if not worse. > > Now, be kind, but what do you think of it? It does not seem very workable, wouldn't you agree :( Sorry, I don't have any better ideas at this time, but please reconsider the semantics of the unix filesystem and access rights. cryptofs seems a fine idea, but it actually relies to the security offered by the access rights and superuser's goodwill--you cannot count on either :( /Marino > > Sincerely yours, > > --- > Andrzej Bialecki FreeBSD: Turning PCs Into Workstations > http://www.freebsd.org > Research and Academic Network in Poland > > From owner-freebsd-hackers Thu Jul 3 06:42:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA10246 for hackers-outgoing; Thu, 3 Jul 1997 06:42:33 -0700 (PDT) Received: from omnivax (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA10222 for ; Thu, 3 Jul 1997 06:42:24 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA18306; Thu, 3 Jul 1997 09:26:28 -0400 From: Bill Paul Message-Id: <199707031326.JAA18306@skynet.ctr.columbia.edu> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Thu, 3 Jul 1997 09:26:25 -0400 (EDT) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <33BB7B0C.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 3, 97 12:12:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Sebastian Lederer had to walk into mine and say: > > Terry Lambert wrote: > > > > How do you think NFS server to NFS client responses operate? The > > NFS client has to do the same types of things. > > No,it does not. That's exactly the point. > > The nfs client does a rpc call (e.g. NFSPROC_READ) to the nfs rpc > service on the nfs server, and gets an ordinary rpc reply as a result. > > The locking client does a rpc call to the nlockmgr rpc service on the > nfs server (e.g. NLM_LOCK_MSG). No rpc reply is sent back. > The result of the locking operation is then sent as an entirely > different > rpc call from the nfs server to the nlockmgr service on the nfs client > (NLM_LOCK_RES). This is not that hard to do: in the server side stubs, you just return NULL to the dispatcher. This prevents it from automatically calling svc_sendreply(). The client can do this by setting the RPC call timeout to 0; in this case it always gets back an RPC_TIMEDOUT error, but the call returns immediately. > That is, for the moment the nfs client becomes a server for the > nlockmgr service, and the rpc.lockd becomes the rpc client. NIS+ callbacks work somewhat like this too (except that you have to keep processing callbacks while waiting for other requests in the server; this requires either fork()ing, threading, or very clever programming. > So there MUST be a rpc.lockd running on the nfs client > to gather these result messages. And this cannot be done in the kernel > because the nlockmgr service must provide the service for > both sides of the locking protocol simultaneously. Mmmnnn... I have to differ with you here. With SGI IRIX 6.2, the NFS lock manager is in fact implemented inside the kernel. There is a /usr/etc/rpc.lockd, but it's just a small program that launches the lock manager as a kernel-space process. Actually, it may really be a kernel-space thread: no lock manager process shows up when you do a 'ps -ef' however the 'nlockmgr' service is registered with the portmapper. (It's registered on port 2049 too, which is significant because that's where nfs is registered too.) There is no llockmgr service registered anymore since it's no longer required (the kernel can calk to the lock manager process/thread directly instead of needing to use RPCs.) I'm not certain if I like this approach or not; on the one hand, it makes the llockmgr protocol unnecessary, but on the other hand, if the lock manager kernel process/thread goes insane (as the NFS lock manager is wont to do, in my experience), there's no way to kill/restart it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Thu Jul 3 07:08:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA11291 for hackers-outgoing; Thu, 3 Jul 1997 07:08:49 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA11284 for ; Thu, 3 Jul 1997 07:08:41 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id QAA03863; Thu, 3 Jul 1997 16:09:41 +0200 (CEST) From: Mikael Karpberg Message-Id: <199707031409.QAA03863@ocean.campus.luth.se> Subject: Re: Crypto (MD5,DES) filesystem In-Reply-To: <199707031212.OAA18858@ws6423.gud.siemens.at> from "marino.ladavac@siemens.at" at "Jul 3, 97 02:12:20 pm" To: lada@ws6303.gud.siemens.at Date: Thu, 3 Jul 1997 16:09:41 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to marino.ladavac@siemens.at: > > Hi! > > > > I'm looking for an implementation of crypto filesystem for FreeBSD. > > Perhaps it doesn't exist at all (yet). > > Not that I know of. Crypto filesystems that are not worse than useless > are not easy. > > > > I'm ignorant in filesystems intrinsics, so don't laugh, but here's my idea > > how it could be done: [...] > > mount_crypto -e md5 /home/user/plaintext/locked /home/user/unlocked > > > > And then everyone who has read access to the mounted files gets to see > them as plaintext. Anyone who happens to be root gets all of the contents > for free. > > This is worse than useless because it conveys a false feeling of security > unless you consider the implications (then it becomes just plain useless:) What's so useless about it? Root can go in and read to his hearts content from /dev/mem, if needed. You can't really stop root from reading anything, as long as it is not encrypted all the time while it's passing that computer. And a crypted filesystem is impossible, then. That is, unless you do something like NFS (where you can also mount it locally) where the client is responsible for (de/en)crypting all the data. Then you could be safe, if the root at the other machine had no power on your client machine, but just the server. If you can't trust the superuser on a machine, then don't use that machine for things that you care a lot about. It should be possible to make a filesystem visible only to the person that mounted it, no? I know basically nothing about the filesystem code, but I can't imagine it would be very difficult. Just store the user id in the "mount struct" (or whatever). /Mikael From owner-freebsd-hackers Thu Jul 3 08:30:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15179 for hackers-outgoing; Thu, 3 Jul 1997 08:30:00 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15167 for ; Thu, 3 Jul 1997 08:29:45 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id VAA19934; Thu, 3 Jul 1997 21:22:57 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707031522.VAA19934@hq.icb.chel.su> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Thu, 3 Jul 1997 21:22:57 +0600 (ESD) Cc: luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Jul 1, 97 10:30:54 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 30 Jun 1997, Luigi Rizzo wrote: > > > Apologies if this is off topic, but I found this on the news, and it > > sounds interesting. I haven't been able to try it because the site is > > quite slow from here. > > I tried it - their dealer had this demo on his server in Poland. Well, to > be frank - it's really, really COOOLLL. It's probably impossible with > Xfree86 size to beat this as a whole. I did not saw this demo but probably it does not use X. QNX has its own windowing system that is much less in size than X. -SB From owner-freebsd-hackers Thu Jul 3 08:38:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15544 for hackers-outgoing; Thu, 3 Jul 1997 08:38:39 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15539 for ; Thu, 3 Jul 1997 08:38:33 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id RAA05918; Thu, 3 Jul 1997 17:37:46 +0200 (MET DST) Date: Thu, 3 Jul 1997 17:37:45 +0200 (MET DST) From: Andrzej Bialecki To: "marino.ladavac@siemens.at" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Crypto (MD5,DES) filesystem In-Reply-To: <199707031212.OAA18858@ws6423.gud.siemens.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 3 Jul 1997, marino.ladavac@siemens.at wrote: > > * take the nullfs and modify it, so that in every write it makes an XOR of > > md5-hashed password with the actual block contents. On every read do the > > contrary. In other words, to slide in encryption between vnode and nullfs > > layers. > > Hopefully not. You really should use an encryption method that needs more > than a couple of seconds to break it. This was just an example. It could be DES instead. > > Otherwise, the layering sounds logical. > > > > > * modify the mount_null (let's call it mount_crypto) to get a password > > from user. > > > > Then user could issue the following command (as it is not required to be > > superuser to do such mounts): > > > > mount_crypto -e md5 /home/user/plaintext/locked /home/user/unlocked > > > > And then everyone who has read access to the mounted files gets to see > them as plaintext. Anyone who happens to be root gets all of the contents > for free. Well.... you're right. But.. it (vfs layer???) could ask your password every time you open the file. As it decrypts only blocks read from disk, and stores the plaintext in disk buffers, it would require much tweaking even of SUPERUser to get their contents right. > This is worse than useless because it conveys a false feeling of security > unless you consider the implications (then it becomes just plain useless:) Well, then how you can have secure access to your files placed on multiuser machine? I'd like to have additional level of protection, so that even root wouldn't be able to get at my data. Normal way to do it is to encrypt the data. But I hate the idea of having to deal with thousands of files, and every one of them needs to be en/decrypted every time I want to use it, and, besides, leaves the traces of its plaintext contents on disk. Cryptofs seemed a good idea. > > and every file in directory 'locked' would be encrypted/decrypted on the > > fly. The most important being the contents of the disk blocks are always > > encrypted (no need to write decrypted blocks anywhere). > > But just as bad, if not worse. > > > > Now, be kind, but what do you think of it? > > It does not seem very workable, wouldn't you agree :( Sorry, I don't have Sigh... So it seems. So here's another idea: what about the situation where only one (strongly authenticated) user process sees the encrypted filesystem as plaintext. E.g. I could have a filesystem image, and the user daemon would "mount" it only for itself, so that it wouldn't be visible in other filesystem's space. Hmmm.... and then I'd send it {NFS,SMB,whatnot} queries? :-) (as the other person mentioned). Anyway, these ideas came to me while I was reading mount_null(8), and I liked the idea of stackable vfs layers. Many interesting things could be done this way, it seems. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Thu Jul 3 18:41:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03304 for hackers-outgoing; Thu, 3 Jul 1997 18:41:29 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03299 for ; Thu, 3 Jul 1997 18:41:26 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id BAA13067; Fri, 4 Jul 1997 01:40:58 GMT Date: Fri, 4 Jul 1997 10:40:58 +0900 (JST) From: Michael Hancock To: Andrzej Bialecki cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Crypto (MD5,DES) filesystem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 3 Jul 1997, Andrzej Bialecki wrote: > > Hi! > > I'm looking for an implementation of crypto filesystem for FreeBSD. > Perhaps it doesn't exist at all (yet). Matt Blaze has a cryptofs that he built on top of NFS. I heard there was an International version somewhere in Europe. Try ftp://ftp.research.att.com/dist/mab/ Regards, Mike Hancock From owner-freebsd-hackers Thu Jul 3 19:12:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA03945 for hackers-outgoing; Thu, 3 Jul 1997 19:12:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA03935 for ; Thu, 3 Jul 1997 19:12:38 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA15932; Fri, 4 Jul 1997 11:38:53 +0930 (CST) From: Michael Smith Message-Id: <199707040208.LAA15932@genesis.atrad.adelaide.edu.au> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: <199707031522.VAA19934@hq.icb.chel.su> from "Serge A. Babkin" at "Jul 3, 97 09:22:57 pm" To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Fri, 4 Jul 1997 11:38:52 +0930 (CST) Cc: abial@korin.warman.org.pl, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Serge A. Babkin stands accused of saying: > > I tried it - their dealer had this demo on his server in Poland. Well, to > > be frank - it's really, really COOOLLL. It's probably impossible with > > Xfree86 size to beat this as a whole. > > I did not saw this demo but probably it does not use X. QNX has its > own windowing system that is much less in size than X. XFree86 runs on QNX (naturally 8), but you're right, the IAT demo disk uses the Photon MicroGUI, which is a remarkable piece of work. In fact, the whole thing is an excellent example of what embedded OS' are good for; however, you'll note after using it for a few minutes that you quickly run up against their limitations - you can't _do_ much with it! > -SB -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 3 19:46:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05166 for hackers-outgoing; Thu, 3 Jul 1997 19:46:47 -0700 (PDT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05152 for ; Thu, 3 Jul 1997 19:46:42 -0700 (PDT) Received: from mrsclaus.cs.rice.edu (mrsclaus.cs.rice.edu [128.42.1.108]) by cs.rice.edu (8.8.5/8.7.1) with ESMTP id VAA04908; Thu, 3 Jul 1997 21:46:34 -0500 (CDT) From: John Paul Campbell Received: (from jpc@localhost) by mrsclaus.cs.rice.edu (8.8.5/8.7.3) id VAA03573; Thu, 3 Jul 1997 21:46:38 -0500 (CDT) Message-Id: <199707040246.VAA03573@mrsclaus.cs.rice.edu> Subject: compile errors in GENERIC 2.2.2 To: hackers@freebsd.org, jpc@cs.rice.edu (John Paul Campbell) Date: Thu, 3 Jul 1997 21:46:37 -0500 (CDT) In-Reply-To: from "Doug White" at Jul 3, 97 05:38:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was advised to send this problem to the group. Hopefully, someone can help. I just installed 2.2.2 from scratch and was able to configure and compile a custom kernel. However, I tried a week later and got this error: gcc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../kern/kern_clock.c machine/cpufunc.h: In function `hardclock': machine/cpufunc.h:331: inconsistent operand constraints in an `asm' *** Error code 1 Stop. I have removed and reinstalled the sources and still the error occurs. This happens for every config, even GENERIC. I'm compiling with gcc2.7.2.1 on a Compaq Presario P60. Any ideas? John From owner-freebsd-hackers Thu Jul 3 20:03:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05673 for hackers-outgoing; Thu, 3 Jul 1997 20:03:10 -0700 (PDT) Received: from pobox.com (ott-on6-39.netcom.ca [207.181.91.166]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05668 for ; Thu, 3 Jul 1997 20:03:01 -0700 (PDT) Received: (from brianc@localhost) by pobox.com (8.8.5/8.8.5) id XAA04922; Thu, 3 Jul 1997 23:01:46 -0400 (EDT) Message-ID: <19970703230145.53129@pobox.com> Date: Thu, 3 Jul 1997 23:01:45 -0400 From: Brian Campbell To: freebsd-hackers@FreeBSD.org Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) References: <199707031522.VAA19934@hq.icb.chel.su> <199707040208.LAA15932@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199707040208.LAA15932@genesis.atrad.adelaide.edu.au>; from Michael Smith on Fri, Jul 04, 1997 at 11:38:52AM +0930 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 04, 1997 at 11:38:52AM +0930, Michael Smith wrote: > Serge A. Babkin stands accused of saying: > > > I tried it - their dealer had this demo on his server in Poland. Well, to > > > be frank - it's really, really COOOLLL. It's probably impossible with > > > Xfree86 size to beat this as a whole. > > > > I did not saw this demo but probably it does not use X. QNX has its > > own windowing system that is much less in size than X. > > XFree86 runs on QNX (naturally 8), but you're right, the IAT demo disk > uses the Photon MicroGUI, which is a remarkable piece of work. hmm ... where can I get XFree for QNX? Last I heard only Metro-X was available. > In fact, the whole thing is an excellent example of what embedded OS' > are good for; however, you'll note after using it for a few minutes > that you quickly run up against their limitations - you can't _do_ > much with it! You can't do much with embedded OS's or the just the demo? ;-) From owner-freebsd-hackers Thu Jul 3 22:46:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09981 for hackers-outgoing; Thu, 3 Jul 1997 22:46:21 -0700 (PDT) Received: from argus.tfs.net (tc1-p4.tfs.net [139.146.197.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA09975 for ; Thu, 3 Jul 1997 22:46:16 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id AAA04513 for freebsd-hackers@freebsd.org; Fri, 4 Jul 1997 00:46:03 -0500 (CDT) From: Jim Bryant Message-Id: <199707040546.AAA04513@argus.tfs.net> Subject: is something wrong with the list remailer? To: freebsd-hackers@freebsd.org Date: Fri, 4 Jul 1997 00:46:01 -0500 (CDT) Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk just wondering, the volume has been really low for the last day... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Fri Jul 4 00:18:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13213 for hackers-outgoing; Fri, 4 Jul 1997 00:18:46 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13206 for ; Fri, 4 Jul 1997 00:18:34 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id JAA10093; Fri, 4 Jul 1997 09:17:16 +0200 Message-ID: <33BCA373.41C67EA6@bonn-online.com> Date: Fri, 04 Jul 1997 09:17:07 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Bill Paul CC: hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707031326.JAA18306@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Paul wrote: > > > > The locking client does a rpc call to the nlockmgr rpc service on the > > nfs server (e.g. NLM_LOCK_MSG). No rpc reply is sent back. > > The result of the locking operation is then sent as an entirely > > different > > rpc call from the nfs server to the nlockmgr service on the nfs client > > (NLM_LOCK_RES). > > This is not that hard to do: in the server side stubs, you just return > NULL to the dispatcher. This prevents it from automatically calling > svc_sendreply(). The client can do this by setting the RPC call timeout > to 0; in this case it always gets back an RPC_TIMEDOUT error, but the > call returns immediately. You're right, this not a problem, in fact it's already implemented in Andrew Gordon's rpc.lockd (which does no actual locking, only the nlockmgr rpc protocol). > Mmmnnn... I have to differ with you here. With SGI IRIX 6.2, the NFS > lock manager is in fact implemented inside the kernel. There is a > /usr/etc/rpc.lockd, but it's just a small program that launches the > lock manager as a kernel-space process. Actually, it may really be a > kernel-space thread: no lock manager process shows up when you do a > 'ps -ef' however the 'nlockmgr' service is registered with the portmapper. > (It's registered on port 2049 too, which is significant because that's > where nfs is registered too.) There is no llockmgr service registered > anymore since it's no longer required (the kernel can calk to the > lock manager process/thread directly instead of needing to use RPCs.) Right, one could also implement the lockd as a kernel process, just like the nfs server. But even then there would be still an nlockmgr rpc service running on the nfs client, as you have pointed out. The nlockmgr protocol cannot be handled just by the client code. It's interesting that the nlockmgr port is the same as the nfs port, that would probably mean that the lock manager has been combined with the in-kernel nfs service (maybe that's what nfssys(LM_SVC) is for, but at least on Sun, nfssys is undocumented, so I'm only guessing) It's also interesting that you mention a llockmgr protocol. Does that mean there *was* a (user process) rpc.lockd on the nfs client in earlier versions of IRIX, and that the llockmgr protocol was used by the kernel to communicate with it? > I'm not certain if I like this approach or not; on the one hand, it > makes the llockmgr protocol unnecessary, but on the other hand, if the > lock manager kernel process/thread goes insane (as the NFS lock manager > is wont to do, in my experience), there's no way to kill/restart it. Assuming that an in-kernel lockd implementation is much more difficult than a user-process implementation, I would suggest that we should try a user-process based implementation first. If that works, maybe later we could move to a kernel process for performance optimization. But I think for now it's more important to have something working than to have improved performance. The overall performance of nfs locking is not / won't be great anyway. What do you think? Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Fri Jul 4 01:09:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15028 for hackers-outgoing; Fri, 4 Jul 1997 01:09:15 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.DPCSYS.com [209.25.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15019 for ; Fri, 4 Jul 1997 01:09:09 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id IAA02069 for ; Fri, 4 Jul 1997 08:09:08 GMT Date: Fri, 4 Jul 1997 01:09:07 -0700 (PDT) From: Dan Busarow cc: hackers@FreeBSD.ORG Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: <199707040208.LAA15932@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Jul 1997, Michael Smith wrote: > In fact, the whole thing is an excellent example of what embedded OS' > are good for; however, you'll note after using it for a few minutes > that you quickly run up against their limitations - you can't _do_ > much with it! That's exactly what I found :) (it wouldn't do anything I wanted it to) Neat demo though. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Fri Jul 4 01:18:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15450 for hackers-outgoing; Fri, 4 Jul 1997 01:18:37 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15445 for ; Fri, 4 Jul 1997 01:18:31 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id KAA07066 for ; Fri, 4 Jul 1997 10:18:25 +0200 (MET DST) Date: Fri, 4 Jul 1997 10:18:25 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: Re: Crypto (MD5,DES) filesystem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! Thanks to all of you who pointed to me some available resources, and the specific risks involved. I think I'll give it a try anyway. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Fri Jul 4 01:44:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16386 for hackers-outgoing; Fri, 4 Jul 1997 01:44:32 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16381 for ; Fri, 4 Jul 1997 01:44:29 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id JAA13658; Fri, 4 Jul 1997 09:43:56 +0100 (BST) Message-ID: <19970704094356.60962@pavilion.net> Date: Fri, 4 Jul 1997 09:43:56 +0100 From: Josef Karthauser To: freebsd-hackers@FreeBSD.ORG Subject: Re: is something wrong with the list remailer? References: <199707040546.AAA04513@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199707040546.AAA04513@argus.tfs.net>; from Jim Bryant on Fri, Jul 04, 1997 at 12:46:01AM -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 04, 1997 at 12:46:01AM -0500, Jim Bryant wrote: > just wondering, the volume has been really low for the last day... > There appeared to be some network problems near MCI. We couldn't resolve any freebsd.org dns entries for a while yesterday. Jo. -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Fri Jul 4 01:49:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16579 for hackers-outgoing; Fri, 4 Jul 1997 01:49:00 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16560; Fri, 4 Jul 1997 01:48:54 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id LAA21055; (8.8.3/zah/2.1) Fri, 4 Jul 1997 11:44:58 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id JAA07426; (8.6.11/zah/2.1) Fri, 4 Jul 1997 09:32:42 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id LAA08469; (8.6.9/zah/1.1) Fri, 4 Jul 1997 11:30:51 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id LAA05452; Fri, 4 Jul 1997 11:29:20 +0300 (EET DST) Message-ID: <33BCA6B8.56C@cki.ipri.kiev.ua> Date: Fri, 04 Jul 1997 10:31:03 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: ports@freebsd.org CC: hackers@freebsd.org Subject: gcc versions Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I try to install guavac port on 2.2.1 --- compilation is fail. It looks, like guavac requare gcc-2.7.2.9 , instead 2.7.2.1 So: what stable version of FreeBSD have gcc-2.7.2.9 ? if only FreeBSD-current, If I want to get scontrib from -current, all ather sources from stable --- it would be work ? From owner-freebsd-hackers Fri Jul 4 03:28:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19910 for hackers-outgoing; Fri, 4 Jul 1997 03:28:38 -0700 (PDT) Received: from lab321.ru (root@anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19900; Fri, 4 Jul 1997 03:28:19 -0700 (PDT) Received: from kev.l321.omsk.net.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru SLmail95 v1.0.32 with SMTP id RAA27617; Fri, 4 Jul 1997 17:27:21 +0700 (OSD) Message-ID: <33BCCFE3.FF6D5DF@lab321.ru> Date: Fri, 04 Jul 1997 17:26:43 +0700 From: Eugeny Kuzakov Organization: Internet - POINT OF NO RETURN ! X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: rssh@cki.ipri.kiev.ua CC: ports@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: gcc versions References: <33BCA6B8.56C@cki.ipri.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ruslan Shevchenko wrote: > > I try to install guavac port on 2.2.1 --- compilation is fail. It looks, > like guavac > requare gcc-2.7.2.9 , instead 2.7.2.1 I have 2.2.2. Compile and install of guavac successfully. gcc 2.7.2.1. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Fri Jul 4 03:46:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20552 for hackers-outgoing; Fri, 4 Jul 1997 03:46:24 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20547 for ; Fri, 4 Jul 1997 03:46:21 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id GAA28498; Fri, 4 Jul 1997 06:46:50 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id GAA01355; Fri, 4 Jul 1997 06:47:02 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Fri, 4 Jul 1997 06:47:02 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: jbryant@tfs.net cc: freebsd-hackers@FreeBSD.ORG Subject: Re: is something wrong with the list remailer? In-Reply-To: <199707040546.AAA04513@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Jul 1997, Jim Bryant wrote: > just wondering, the volume has been really low for the last day... Well, I received some interesting mail from majordomo@freebsd.org which insisted that none of the freebsd-* mailinglists existed... The extra peace and quite _was_ nice, though! ;-) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Fri Jul 4 05:07:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA22744 for hackers-outgoing; Fri, 4 Jul 1997 05:07:02 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA22731; Fri, 4 Jul 1997 05:06:47 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199707041206.FAA22731@hub.freebsd.org> Subject: Re: Crypto (MD5,DES) filesystem To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Fri, 4 Jul 1997 05:06:47 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Jul 3, 97 12:59:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andrzej Bialecki wrote: > > > Hi! > > I'm looking for an implementation of crypto filesystem for FreeBSD. > Perhaps it doesn't exist at all (yet). Matt Blaze wrote CFS, cryptographic filesystem. Crypto is very hard to get right. Matt is a professional cryptographer. try a search fro "Matt Blaze" and "CFS" on one of the search engines (alta vista, etc.) jmb From owner-freebsd-hackers Fri Jul 4 08:37:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27967 for hackers-outgoing; Fri, 4 Jul 1997 08:37:25 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA27962 for ; Fri, 4 Jul 1997 08:37:18 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA19945; Fri, 4 Jul 1997 11:37:22 -0400 From: Bill Paul Message-Id: <199707041537.LAA19945@skynet.ctr.columbia.edu> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Fri, 4 Jul 1997 11:37:20 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <33BCA373.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 4, 97 09:17:07 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Sebastian Lederer had to walk into mine and say: > > > Mmmnnn... I have to differ with you here. With SGI IRIX 6.2, the NFS > > lock manager is in fact implemented inside the kernel. There is a > > /usr/etc/rpc.lockd, but it's just a small program that launches the > > lock manager as a kernel-space process. Actually, it may really be a > > kernel-space thread: no lock manager process shows up when you do a > > 'ps -ef' however the 'nlockmgr' service is registered with the portmapper. > > (It's registered on port 2049 too, which is significant because that's > > where nfs is registered too.) There is no llockmgr service registered > > anymore since it's no longer required (the kernel can calk to the > > lock manager process/thread directly instead of needing to use RPCs.) > > Right, one could also implement the lockd as a kernel process, just > like the nfs server. But even then there would be still an nlockmgr rpc > service > running on the nfs client, as you have pointed out. The nlockmgr > protocol > cannot be handled just by the client code. > > It's interesting that the nlockmgr port is the same as the nfs port, > that would probably mean that the lock manager has been combined with > the in-kernel nfs service (maybe that's what nfssys(LM_SVC) is for, > but at least on Sun, nfssys is undocumented, so I'm only guessing) I can tell you at least one thing nfssys() does: if you look at the keylogin(1) and chkey(1) source code from the tirpcsrc-2.3 distribution (on playground.sun.com:/pub/rpc, among other places), you'll see that it's used for revoking Secure RPC credentials for use with 'Secure NFS' (nfssys(NFS_REVAUTH, &foo)). What I don't know is how Secure RPC credentials are established for secure NFS in the first place. I think the kernel may actually communicate with the keyserv daemon to do it, but I'm not certain. > It's also interesting that you mention a llockmgr protocol. Does that > mean there *was* a (user process) rpc.lockd on the nfs client > in earlier versions of IRIX, and that the llockmgr protocol was > used by the kernel to communicate with it? Yes: before IRIX 6.2 came out, previous versions of IRIX had both a user-space rpc.statd and rpc.lockd, and lockd contained both an nlockmgr and llockmgr service implementation. This is the usual way it's done on commercial UNIXes that have licensed Sun's NFS code: rpc.lockd processes communicate with each other over the network using the nlockmgr protocol, but each rpc.lockd communicates with the kernel on the local host using the llockmgr protocol. That's what the /usr/include/rpcsvc/klm_prot.x protocol is for. Here's how it works (I think): - A process on a client decides it wants to lock something so it uses the flock() or fcntl() system calls. - The kernel eventually works out that the filesystem on which the process is trying to establish the lock is an NFS filesystem. - The kernel uses the klm_prot (llockmgr) protocol to ask the local rpc.lockd to go out and talk to the rpc.lockd on the NFS server and ask it for a lock. - The rpc.lockd on the server gets the request, locks the file, then replies back to the client. - The rpc.lockd on the client gets the remote lockd's reply and replies back to the kernel to tell it what happened. In IRIX 6.2, the extra RPC between the kernel and the local rpc.lockd goes away since the kernel has the nlm_prot (nlockmgr) protocol already implemented inside it. > > I'm not certain if I like this approach or not; on the one hand, it > > makes the llockmgr protocol unnecessary, but on the other hand, if the > > lock manager kernel process/thread goes insane (as the NFS lock manager > > is wont to do, in my experience), there's no way to kill/restart it. > > Assuming that an in-kernel lockd implementation is much more difficult > than a user-process implementation, I would suggest that we should try > a user-process based implementation first. > If that works, maybe later we could move to a kernel process for > performance optimization. > But I think for now it's more important to have something working > than to have improved performance. > The overall performance of nfs locking is not / won't be > great anyway. What do you think? I think somebody should start working on a klm_prot implementation for FreeBSD so we can tie everything together. This implies writing the client-side NFS locking support first though. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Fri Jul 4 09:02:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28799 for hackers-outgoing; Fri, 4 Jul 1997 09:02:53 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28770; Fri, 4 Jul 1997 09:02:40 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id SAA22567; (8.8.3/zah/2.1) Fri, 4 Jul 1997 18:53:22 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id QAA15523; (8.6.11/zah/2.1) Fri, 4 Jul 1997 16:03:31 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id RAA09782; (8.6.9/zah/1.1) Fri, 4 Jul 1997 17:51:19 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id RAA06002; Fri, 4 Jul 1997 17:49:45 +0300 (EET DST) Message-ID: <33BCFFE4.64E9@cki.ipri.kiev.ua> Date: Fri, 04 Jul 1997 16:51:31 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Eugeny Kuzakov CC: ports@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: gcc versions References: <33BCA6B8.56C@cki.ipri.kiev.ua> <33BCCFE3.FF6D5DF@lab321.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eugeny Kuzakov wrote: > > Ruslan Shevchenko wrote: > > > > I try to install guavac port on 2.2.1 --- compilation is fail. It looks, > > like guavac > > requare gcc-2.7.2.9 , instead 2.7.2.1 > I have 2.2.2. > Compile and install of guavac successfully. > gcc 2.7.2.1. Hmm, can anybody try to build it on 2.2.1 ? I have errors, looks, like template inline functions is not expands. (after adding the definitions of it's it work) Can it be bug in configure ? > > -- > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > kev@lab321.ru From owner-freebsd-hackers Fri Jul 4 10:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01383 for hackers-outgoing; Fri, 4 Jul 1997 10:21:45 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA01372 for ; Fri, 4 Jul 1997 10:21:40 -0700 (PDT) Received: from stuyts by ns.NL.net (5.65b/NLnet1.3) id AA28691; Fri, 4 Jul 1997 19:12:50 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.8.6/8.8.5) with UUCP id TAA07597 for freebsd-hackers@FreeBSD.ORG; Fri, 4 Jul 1997 19:03:33 +0200 (MET DST) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.8.6/8.8.5) with ESMTP id TAA00468 for ; Fri, 4 Jul 1997 19:02:40 +0200 (MET DST) Message-Id: <199707041702.TAA00468@trantor.stuyts.nl> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-hackers@FreeBSD.ORG Subject: Probing cdrom for presence of disk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Jul 1997 19:02:39 +0200 From: Paul van der Zwan Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is there a way to probe a cdrom drive for the presence of a disk without getting any messages on the console? I am trying to write some software to automatically mount a cd if it is inserted in the drive, but filling the console with errors is not something I want to happen. Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." From owner-freebsd-hackers Fri Jul 4 11:08:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02823 for hackers-outgoing; Fri, 4 Jul 1997 11:08:02 -0700 (PDT) Received: from relay.ucb.crimea.ua (ru@relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02793; Fri, 4 Jul 1997 11:07:41 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.5/8.8.5) id VAA01496; Fri, 4 Jul 1997 21:02:03 +0300 (EET DST) From: Ruslan Ermilov Message-Id: <199707041802.VAA01496@relay.ucb.crimea.ua> Subject: SLIP DRIVER needs to be rewritten!!! To: freebsd-hackers@freebsd.org Date: Fri, 4 Jul 1997 21:02:02 +0300 (EET DST) Cc: freebsd-bugs@freebsd.org X-My-Interests: Unix,Oracle,Networking X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I'm using 2.2.1-RELEASE of FreeBSD now. I have a proposal of how to solve the problem when SC_STATIC flag is used. First, I'll try to explain the problem(s): I've configured 4 slip units in kernel and need to attach two slip interfaces. And I WANT to use STATIC FEATURE of the driver (using -S switch of slattach). Well, I run `slattach -s 38400 /dev/cuaa0 -S 1' and here is what I see: 1) netstat -in shows the sl0 and sl1 in the reversed order. This is because slopen() allocates first free element of slsoftc[], i.e. slsoftc[0], and then, when slattach proceeds the -S1 switch, sltioctl(SLIOCSUNIT) assigns to it "slip unit 1" and sets on it SC_STATIC flag. 2) `ifconfig -a' shows the sl0 and sl1 in the normal order. 3) what happens when I try to `ifconfig sl1 x.x.x.x y.y.y.y' is that ifconfig configures sl0 instead of sl1. (To be more exactly, `ifconfig -a' shows that sl0 (but not sl1) has been configured. 4) Moreover, when I then kill my slattach process and then start it again slopen() skips slsoftc[0] because it has SC_STATIC flag set. Note that SC_STATIC flag is not cleared in slclose() to avoid allocation of this unit to the "dynamic slip allocation requests" (i.e. when `slattach' started without -S switch, or when `sliplogin' is started). So, when I kill and start `slattach' 4 times (i.e. the number of slip units configured), slopen() returns ENXIO. If you don't believe me, try to run your kernel.GENERIC (it has been compiled with only 1 slip unit), then start `slattach' with -S switch, kill it, and then try to start `slattach' again. Oops... You'll believe me now ;-) In my point of view, there is the WRONG LOGIC in the if_sl.c. My patch uses the following ideas: 1) Do not `attach the given tty to the first available sl unit' when in the slopen(). 2) Attach the SPECIFIED sl unit to the tty if the sltioctl(SLIOCSUNIT) has been invoked. 3) Or attach `first free, not SC_STATIC sl unit' when the sltioctl(SLIOCGUNIT) has been invoked. The driver version which I've modified is: $Id: if_sl.c,v 1.45.2.1 1997/03/11 19:40:37 bde Exp $ I.e. this is the current version of this driver in RELENG_2_2 branch. My diff is: [**********cut here**********] --- if_sl.c.orig Thu Jul 3 11:10:34 1997 +++ if_sl.c Thu Jul 3 11:17:12 1997 @@ -186,6 +186,7 @@ static struct mbuf *sl_btom __P((struct sl_softc *, int)); static timeout_t sl_keepalive; static timeout_t sl_outfill; +static int slalloc __P((int, struct tty *)); static int slclose __P((struct tty *,int)); static int slinput __P((int, struct tty *)); static int slioctl __P((struct ifnet *, int, caddr_t)); @@ -265,8 +266,6 @@ register struct tty *tp; { struct proc *p = curproc; /* XXX */ - register struct sl_softc *sc; - register int nsl; int s, error; error = suser(p->p_ucred, &p->p_acflag); @@ -276,38 +275,62 @@ if (tp->t_line == SLIPDISC) return (0); - for (nsl = NSL, sc = sl_softc; --nsl >= 0; sc++) - if (sc->sc_ttyp == NULL && !(sc->sc_flags & SC_STATIC)) { - if (slinit(sc) == 0) - return (ENOBUFS); - tp->t_sc = (caddr_t)sc; - sc->sc_ttyp = tp; - sc->sc_if.if_baudrate = tp->t_ospeed; - ttyflush(tp, FREAD | FWRITE); - - tp->t_line = SLIPDISC; - /* - * We don't use t_canq or t_rawq, so reduce their - * cblock resources to 0. Reserve enough cblocks - * for t_outq to guarantee that we can fit a full - * packet if the SLIP_HIWAT check allows slstart() - * to loop. Use the same value for the cblock - * limit since the reserved blocks should always - * be enough. Reserving cblocks probably makes - * the CLISTRESERVE check unnecessary and wasteful. - */ - clist_alloc_cblocks(&tp->t_canq, 0, 0); - clist_alloc_cblocks(&tp->t_outq, - SLIP_HIWAT + 2 * sc->sc_if.if_mtu + 1, - SLIP_HIWAT + 2 * sc->sc_if.if_mtu + 1); - clist_alloc_cblocks(&tp->t_rawq, 0, 0); - - s = splnet(); - if_up(&sc->sc_if); - splx(s); - return (0); - } - return (ENXIO); + ttyflush(tp, FREAD | FWRITE); + + tp->t_line = SLIPDISC; + return (0); +} + +static int +slalloc(unit, tp) + int unit; + struct tty *tp; +{ + register struct sl_softc *sc; + int s, static_unit = 1; + + if (unit == -1) { + static_unit = 0; + for (unit = 0; unit < NSL; unit++) + if (sl_softc[unit].sc_ttyp == NULL && + !(sl_softc[unit].sc_flags & SC_STATIC) ) + break; + } + + if (unit < 0 || unit >= NSL || tp->t_sc != NULL) + return (ENXIO); + + sc = &sl_softc[unit]; + if (sc->sc_ttyp != NULL) + return (EBUSY); + if (slinit(sc) == 0) + return (ENOBUFS); + + tp->t_sc = (caddr_t)sc; + sc->sc_ttyp = tp; + sc->sc_if.if_baudrate = tp->t_ospeed; + if (static_unit != 0) + sc->sc_flags |= SC_STATIC; + /* + * We don't use t_canq or t_rawq, so reduce their + * cblock resources to 0. Reserve enough cblocks + * for t_outq to guarantee that we can fit a full + * packet if the SLIP_HIWAT check allows slstart() + * to loop. Use the same value for the cblock + * limit since the reserved blocks should always + * be enough. Reserving cblocks probably makes + * the CLISTRESERVE check unnecessary and wasteful. + */ + clist_alloc_cblocks(&tp->t_canq, 0, 0); + clist_alloc_cblocks(&tp->t_outq, + SLIP_HIWAT + 2 * sc->sc_if.if_mtu + 1, + SLIP_HIWAT + 2 * sc->sc_if.if_mtu + 1); + clist_alloc_cblocks(&tp->t_rawq, 0, 0); + + s = splnet(); + if_up(&sc->sc_if); + splx(s); + return (0); } /* @@ -368,34 +391,34 @@ struct proc *p; { struct sl_softc *sc = (struct sl_softc *)tp->t_sc, *nc; - int s, nsl; + int s, nsl, ret; + + if (sc == NULL && (cmd != SLIOCGUNIT && cmd != SLIOCSUNIT)) + return (ENXIO); s = splimp(); switch (cmd) { case SLIOCGUNIT: + if (sc == NULL) { + ret = slalloc(-1, tp); + if (ret != 0) { + splx(s); + return (ret); + } + sc = (struct sl_softc *)tp->t_sc; + } *(int *)data = sc->sc_if.if_unit; break; case SLIOCSUNIT: - if (sc->sc_if.if_unit != *(u_int *)data) { - for (nsl = NSL, nc = sl_softc; --nsl >= 0; nc++) { - if ( nc->sc_if.if_unit == *(u_int *)data - && nc->sc_ttyp == NULL - ) { - nc->sc_if.if_unit = sc->sc_if.if_unit; - nc->sc_flags &= ~SC_STATIC; - nc->sc_flags |= sc->sc_flags & SC_STATIC; - sc->sc_if.if_unit = *(u_int *)data; - goto slfound; - } - } - splx(s); - return (ENXIO); - } - slfound: - sc->sc_flags |= SC_STATIC; + if (sc == NULL) + ret = slalloc(*(int *)data, tp); + else + ret = EEXIST; + splx(s); + return (ret); break; - + case SLIOCSKEEPAL: sc->sc_keepalive = *(u_int *)data * hz; if (sc->sc_keepalive) { [**********cut here**********] Thanks in advance, --- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247 647 Simferopol, Crimea From owner-freebsd-hackers Fri Jul 4 11:10:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02922 for hackers-outgoing; Fri, 4 Jul 1997 11:10:34 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02906 for ; Fri, 4 Jul 1997 11:10:28 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21335; Fri, 4 Jul 1997 11:05:05 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021327; Fri Jul 4 18:04:58 1997 Date: Fri, 4 Jul 1997 11:03:32 -0700 (PDT) From: Julian Elischer To: Paul van der Zwan cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Probing cdrom for presence of disk In-Reply-To: <199707041702.TAA00468@trantor.stuyts.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Workman does it.. see what they do.. I believe they use a direct SCSI command via the user-scsi facility. On Fri, 4 Jul 1997, Paul van der Zwan wrote: > Is there a way to probe a cdrom drive for the presence of a disk without > getting any messages on the console? I am trying to write some software to > automatically mount a cd if it is inserted in the drive, but filling the > console with errors is not something I want to happen. > > Paul > > -- > Paul van der Zwan paulz @ trantor.stuyts.nl > "I think I'll move to theory, everything works in theory..." > > > From owner-freebsd-hackers Fri Jul 4 12:25:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05103 for hackers-outgoing; Fri, 4 Jul 1997 12:25:12 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05098 for ; Fri, 4 Jul 1997 12:25:10 -0700 (PDT) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by freefall.freebsd.org (8.8.6/8.8.5) with SMTP id MAA02376 for ; Fri, 4 Jul 1997 12:25:05 -0700 (PDT) Received: (qmail 4696 invoked by uid 128); 4 Jul 1997 19:24:40 -0000 Date: 4 Jul 1997 19:24:40 -0000 Message-ID: <19970704192440.4695.qmail@squirrel.tgsoft.com> From: mark thompson To: freebsd-hackers@freebsd.com Subject: more corruption Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have written a couple of times about data corruption problems on my floppy drive, which turn out to only happen when the IDE drive is also in use. The symptoms include data being moved from their proper position by a few bytes. I found this really fascinating note on the partition magic install disk, which i quote here without permission of any kind - because i think this may be a concern to users of FreeBSD on PCI computers (like mine). Personally, i have decided to junk my IDE drive. -mark DMATEST 1.01 - Dual-DMA Data-Transfer Reliability Test Copyright 1995 PowerQuest Corporation All Rights Reserved PowerQuest Corporation 1083 N State Orem, UT 84057 voice: 801-226-8977 fax: 801-226-8941 email: scotl@powerquest.com ***** PLEASE READ THIS VERY CAREFULLY!! ***** IF YOU DO NOT, IT COULD COST YOU YOUR DATA! ALL OF YOUR FILES ON ALL OF YOUR DRIVES COULD BE DESTROYED BY A DMA-TRANSFER BUG!! We have found a serious data-corruption bug when using dual-DMA transfer on some computers. It shows up when multitasking between the hard drive and another device such as a floppy drive or a network. When this happens, the data can get shifted by 2 or more bytes. This has serious implications, and has already destroyed many partitions. If the operating system happens to write to the hard drive at the same time that you access a another peripheral device (floppy, network, CD_ROM, etc.), the drive can become corrupted, and the entire partition destroyed. Every PCI EIDE system we have in house has this problem. We have found a work-around for some BIOSes: Changing the "PCI IDE prefetch buffers" BIOS setting to DISABLED prevents the error. Unfortunately, not all machines with the problem allow this setting to be changed by the user. From owner-freebsd-hackers Fri Jul 4 15:36:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09947 for hackers-outgoing; Fri, 4 Jul 1997 15:36:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09939 for ; Fri, 4 Jul 1997 15:36:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id IAA07886; Sat, 5 Jul 1997 08:33:32 +1000 Date: Sat, 5 Jul 1997 08:33:32 +1000 From: Bruce Evans Message-Id: <199707042233.IAA07886@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, jpc@cs.rice.edu Subject: Re: compile errors in GENERIC 2.2.2 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just installed 2.2.2 from scratch and was able to configure and > compile a custom kernel. However, I tried a week later and got this > error: > > gcc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit ^^^ >... > machine/cpufunc.h: In function `hardclock': > machine/cpufunc.h:331: inconsistent operand constraints in an `asm' > I'm compiling with gcc2.7.2.1 on a Compaq Presario P60. Are you sure? This bug is probably caused by compiling with an old or broken version of gcc. The standard version of gcc is named cc and has no problems. Bruce From owner-freebsd-hackers Fri Jul 4 18:04:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA15953 for hackers-outgoing; Fri, 4 Jul 1997 18:04:38 -0700 (PDT) Received: from ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA15948 for ; Fri, 4 Jul 1997 18:04:34 -0700 (PDT) Received: from brianjr.haskin.org (210R1.ptway.com [199.176.148.77]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with ESMTP id UAA05467; Fri, 4 Jul 1997 20:57:27 -0400 (EDT) Message-ID: <33BD9D12.381D2B0@ptway.com> Date: Fri, 04 Jul 1997 21:02:10 -0400 From: Brian Haskin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: Andrzej Bialecki CC: freebsd-hackers@freebsd.org Subject: Re: Crypto (MD5,DES) filesystem X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andrzej Bialecki wrote: > > Hi! > > Thanks to all of you who pointed to me some available resources, and the > specific risks involved. I think I'll give it a try anyway. > > Sincerely yours, > > --- > Andrzej Bialecki FreeBSD: Turning PCs Into Workstations > http://www.freebsd.org > Research and Academic Network in Poland Please if your going through all the work find a better Encryption scheme than what was posted early. What you had posted before would take all of a couple of seconds to crack. no joke. Brian Haskin From owner-freebsd-hackers Fri Jul 4 19:59:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA19185 for hackers-outgoing; Fri, 4 Jul 1997 19:59:10 -0700 (PDT) Received: from java.cc.mcgill.ca (java.CC.McGill.CA [132.216.30.26]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA19178 for ; Fri, 4 Jul 1997 19:59:07 -0700 (PDT) Received: from localhost (yves@localhost) by java.cc.mcgill.ca (8.8.5/8.8.5) with SMTP id WAA07991 for ; Fri, 4 Jul 1997 22:59:06 -0400 (EDT) Date: Fri, 4 Jul 1997 22:59:06 -0400 (EDT) From: Yves LePage To: freebsd-hackers@freebsd.org Subject: kern.maxopenfiles Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I just installed 2.2.2-RELEASE. The server (ircd) that I'll be running on it needs to have a large number of open fd's. Currently my system is set with a hard limit of 360 open files. I wish to increase that to 4096. I tried with sysctl -w kern.maxopenfiles=4096 but that didn't work when I used the limit command as root after that to increase my limit. How can I increase this value (ideally permanently)? Thanks alot, Yves Lepage From owner-freebsd-hackers Fri Jul 4 20:22:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19728 for hackers-outgoing; Fri, 4 Jul 1997 20:22:47 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA19723 for ; Fri, 4 Jul 1997 20:22:43 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wkLMI-0002R6-00; Fri, 4 Jul 1997 20:18:02 -0700 Date: Fri, 4 Jul 1997 20:18:01 -0700 (PDT) From: Tom Samplonius To: Yves LePage cc: freebsd-hackers@freebsd.org Subject: Re: kern.maxopenfiles In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Jul 1997, Yves LePage wrote: > How can I increase this value (ideally permanently)? Yes, build a new kernel. See docs. Start with GENERIC, increase maxusers to 128 (or higher), then probably add MAX_OPEN (see LINT examples). Tom From owner-freebsd-hackers Fri Jul 4 22:51:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA23318 for hackers-outgoing; Fri, 4 Jul 1997 22:51:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA23311 for ; Fri, 4 Jul 1997 22:51:35 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA05833; Sat, 5 Jul 1997 07:51:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA21105; Sat, 5 Jul 1997 07:34:20 +0200 (MET DST) Message-ID: <19970705073420.IP50835@uriah.heep.sax.de> Date: Sat, 5 Jul 1997 07:34:20 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: paulz@trantor.stuyts.nl (Paul van der Zwan) Subject: Re: Probing cdrom for presence of disk References: <199707041702.TAA00468@trantor.stuyts.nl> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Julian Elischer on Jul 4, 1997 11:03:32 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > Workman does it.. > see what they do.. > I believe they use a direct SCSI command via the user-scsi facility. On an ATAPI drive? Glad they don't do it this way. However, they don't do it the way Paul wants it to be done, workman's probing causes blatant SCSI error messages (not ready, medium not present). Perhaps we should implement an open(O_NONBLOCK) in the SCSI subsystem? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jul 5 00:05:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA25550 for hackers-outgoing; Sat, 5 Jul 1997 00:05:52 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA25544 for ; Sat, 5 Jul 1997 00:05:47 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA21614; Sat, 5 Jul 1997 16:35:41 +0930 (CST) From: Michael Smith Message-Id: <199707050705.QAA21614@genesis.atrad.adelaide.edu.au> Subject: Re: Fwd: ANNOUNCE: The 1.44 Mbyte Web Challenge (comp.windows.x.apps) In-Reply-To: <19970703230145.53129@pobox.com> from Brian Campbell at "Jul 3, 97 11:01:45 pm" To: brianc@pobox.com (Brian Campbell) Date: Sat, 5 Jul 1997 16:35:41 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Campbell stands accused of saying: > > > > XFree86 runs on QNX (naturally 8), but you're right, the IAT demo disk > > uses the Photon MicroGUI, which is a remarkable piece of work. > > hmm ... where can I get XFree for QNX? Last I heard only Metro-X > was available. Ok, rephrase. "I head that XF86 was running on QNX". I can't find it, so I'll have to assume that _is_ blood leaking from my shoes... 8) > > In fact, the whole thing is an excellent example of what embedded OS' > > are good for; however, you'll note after using it for a few minutes > > that you quickly run up against their limitations - you can't _do_ > > much with it! > > You can't do much with embedded OS's or the just the demo? ;-) Er, both (sort of 8) For a user expecting a GP OS, an RT OS can be very disorienting and the user-interface model often feels very cramped. The QNX demo disk, for example, doesn't have a shell on it. Shock horror! -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 5 08:55:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA09705 for hackers-outgoing; Sat, 5 Jul 1997 08:55:38 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA09700 for ; Sat, 5 Jul 1997 08:55:36 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.6/8.7.3) with SMTP id LAA17232; Sat, 5 Jul 1997 11:55:32 -0400 (EDT) Message-Id: <199707051555.LAA17232@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers), paulz@trantor.stuyts.nl (Paul van der Zwan) From: "Louis A. Mamakos" Subject: Re: Probing cdrom for presence of disk References: <199707041702.TAA00468@trantor.stuyts.nl> <19970705073420.IP50835@uriah.heep.sax.de> In-reply-to: Your message of "Sat, 05 Jul 1997 07:34:20 +0200." <19970705073420.IP50835@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Jul 1997 11:55:31 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk How about hacking up a script using scsi(8) to perform a test unit ready SCSI command? This should complete without error even with no media inserted in the device. louie From owner-freebsd-hackers Sat Jul 5 11:04:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13252 for hackers-outgoing; Sat, 5 Jul 1997 11:04:43 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13246 for ; Sat, 5 Jul 1997 11:04:34 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.6/8.8.5) with SMTP id UAA03401; Sat, 5 Jul 1997 20:05:49 +0200 (CEST) Date: Sat, 5 Jul 1997 20:05:49 +0200 (CEST) From: Andrzej Bialecki To: Brian Haskin cc: freebsd-hackers@freebsd.org Subject: Re: Crypto (MD5,DES) filesystem In-Reply-To: <33BD9D12.381D2B0@ptway.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Jul 1997, Brian Haskin wrote: > Please if your going through all the work find a better Encryption > scheme > than what was posted early. What you had posted before would take all of > a > couple of seconds to crack. no joke. > > Brian Haskin Yes, I know -this was only an idea. In the meantime I found two already existing implementations - CFS by Matt Blaze, and newer version called TCFS (Transparent Crypto FS). The latter was developed in Italy, and expands the basic idea of CFS. Current version is decidedly for Linux (millions of includes :-( ) but I'll try to run it under Linux first, and (if it shows promising) maybe I'll do a port of it to FreeBSD. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Sat Jul 5 18:35:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28783 for hackers-outgoing; Sat, 5 Jul 1997 18:35:57 -0700 (PDT) Received: from glacier.wise.edt.ericsson.se (glacier-ext.wise.edt.ericsson.se [193.180.251.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA28778 for ; Sat, 5 Jul 1997 18:35:54 -0700 (PDT) Received: from erlang (erlang.ericsson.se [147.214.36.16]) by glacier.wise.edt.ericsson.se (8.7.5/8.7.3/glacier-0.9) with SMTP id DAA16351 for ; Sun, 6 Jul 1997 03:35:52 +0200 (MET DST) Received: from townsend.ericsson.se by erlang (SMI-8.6/LME-2.2.4) id DAA03221; Sun, 6 Jul 1997 03:35:50 +0200 Received: from townsend by townsend.ericsson.se (SMI-8.6/client-1.5) id DAA28936; Sun, 6 Jul 1997 03:36:18 +0200 Message-Id: <199707060136.DAA28936@townsend.ericsson.se> To: freebsd-hackers@freebsd.org Cc: kent@erlang.ericsson.se Subject: Application os version compatibility? Reply-To: kent@erlang.ericsson.se X-Mailer: Mew version 1.70 on Emacs 19.34.1 X-URL: http://www.ericsson.se/erlang Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 06 Jul 1997 03:36:17 +0200 From: Kent Boortz Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know some just link "libc.2.2" to "libc.3.0" to get *some* applications working that was built for another os version than the one running but there must be a better way to create applications that will survive over os version? A reasonable rule would be that - If changing the third version number applications with shared libraries will still work. - If changing the second number staticly linked will still work. - If changing the first number we may have to recompile the whole thing and do a new release. Is there an official rule similar to this in FreeBSD? If the application in question was distributed with full source this wouldn't be a big problem but unfortunately it isn't. Please include my email address in the "To" or "Cc" field because I'm not on the "freebsd-hackers" list. Thank you in advance, /kgb From owner-freebsd-hackers Sat Jul 5 20:22:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03266 for hackers-outgoing; Sat, 5 Jul 1997 20:22:12 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA03256 for ; Sat, 5 Jul 1997 20:22:07 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wkhpE-0003JX-00; Sat, 5 Jul 1997 20:17:24 -0700 Date: Sat, 5 Jul 1997 20:17:24 -0700 (PDT) From: Tom Samplonius To: Kent Boortz cc: freebsd-hackers@freebsd.org Subject: Re: Application os version compatibility? In-Reply-To: <199707060136.DAA28936@townsend.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997, Kent Boortz wrote: > I know some just link "libc.2.2" to "libc.3.0" to get *some* > applications working that was built for another os version than > the one running but there must be a better way to create > applications that will survive over os version? > > A reasonable rule would be that > > - If changing the third version number applications with > shared libraries will still work. The libc version is ONLY changed if the interface changes. If the interface changes, some applications will not work. Hence, the version number change. > - If changing the second number staticly linked will still work. Huh? Statically linked applications ALWAYS work. > - If changing the first number we may have to recompile the > whole thing and do a new release. Unless it is statically linked, in which case it will still work. > Is there an official rule similar to this in FreeBSD? > > If the application in question was distributed with full source > this wouldn't be a big problem but unfortunately it isn't. Well, FreeBSD 3.0 isn't released yet. The libc API COULD still change, because it is still in development. In other words, applications linked with 3.0 from Jan, may not work with 3.0 July. It is foolish to make binary-only releases to support an unreleases os version. Statically link it, and it will work on any version, or dynamically link it to the oldest good release (probably 2.1.7), and 2.2 users can install the 2.1 compat package (basically just a copy of libc.2.2). It really is quite simple. > Please include my email address in the "To" or "Cc" field because > I'm not on the "freebsd-hackers" list. > > Thank you in advance, > > /kgb > > Tom From owner-freebsd-hackers Sat Jul 5 23:03:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08577 for hackers-outgoing; Sat, 5 Jul 1997 23:03:33 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08564 for ; Sat, 5 Jul 1997 23:03:26 -0700 (PDT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id WAA27121 for ; Sat, 5 Jul 1997 22:53:57 -0700 (PDT) Received: from new-world.cs.rice.edu (new-world.cs.rice.edu [128.42.6.103]) by cs.rice.edu (8.8.5/8.7.1) with ESMTP id AAA05143 for ; Sun, 6 Jul 1997 00:53:41 -0500 (CDT) From: "Mark W. Krentel" Received: (from krentel@localhost) by new-world.cs.rice.edu (8.8.5/8.7.3) id AAA05251 for freebsd-hackers@FreeBSD.ORG; Sun, 6 Jul 1997 00:53:52 -0500 (CDT) Date: Sun, 6 Jul 1997 00:53:52 -0500 (CDT) Message-Id: <199707060553.AAA05251@new-world.cs.rice.edu> To: freebsd-hackers@freebsd.org Subject: NFS v3 slower than v2 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I suspect there is a bug in the nfs code causing nfs3 to perform somewhat slower than v2. It doesn't fall over dead, but I can produce examples where v3 takes twice as long as v2. Here's a simple way to reproduce the problem. First, create a large tar file. I used /usr/src/sys, about 24 meg, 2300 files. For each test, unpack the tar file on the server, so the freebsd client can't use its cache (is there a recursive touch?). In my case, the server is an Ultrasparc/Solaris 2.5.1 with 100 MB link. Then, read the new directory with: % nfsstat ; time tar cf - sys > /dev/null ; nfsstat I tried this three times each, mounting the same partition under v2 and v3. V2 took 10.6, 13.5 and 8.8 seconds wall clock time, but v3 took 24.0, 21.0 and 22.1. Looking at the diffs of nfsstat, everything is the same for v2/v3, except v3 produces a large number of Accesses, but v2 produced none. I see a similar problem for writes, but the effect is smaller. 1. What is Access in nfsstat? Is it a symptom of trouble for reads? 2. Can anyone else verify this problem, or is it known? For all I know, it may be specific to Solaris servers and Freebsd clients with 100 MB link. Mark Krentel Rice University krentel@cs.rice.edu Hardware: 200 MHz PPro (512K cache), Intel Venus board, 128 meg RAM, Adaptec 2940U, SMC 9332 100 MB ethernet. This is version 2: Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 27299 4209 15235 117 8602 13999 1969 2038 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 718 5 7 195 192 640 0 138327 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 14 13 0 1861 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 6 70 215440 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 288424 27299 148601 13805 42147 8602 3419 13999 BioRLHits Misses BioD Hits Misses DirE Hits Misses 13794 117 5000 632 1148 0 0.061u 1.225s 0:10.62 12.0% 336+401k 0+1io 3pf+0w Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 29545 4209 17512 120 12626 13999 1969 2038 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 718 5 7 195 192 727 0 138327 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 14 13 0 1861 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 6 70 224077 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 330444 29545 163947 16082 44208 12626 3419 13999 BioRLHits Misses BioD Hits Misses DirE Hits Misses 13794 120 5082 718 1231 0 This is version 3: Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 29647 4209 17552 123 12645 14022 1970 2038 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 718 5 7 195 192 736 0 138397 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 14 14 0 1864 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 6 72 224348 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 330749 29647 164052 16122 44248 12645 3453 14022 BioRLHits Misses BioD Hits Misses DirE Hits Misses 13831 123 5094 726 1241 0 0.084u 2.272s 0:24.03 9.7% 276+328k 0+1io 0pf+0w Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 31892 4209 19829 126 16669 14022 1970 2038 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 718 5 7 195 192 823 0 155988 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 14 14 0 1864 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 8 74 250575 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 355179 31892 179398 18399 46309 16669 3453 14022 BioRLHits Misses BioD Hits Misses DirE Hits Misses 13831 126 5176 812 1324 0 From owner-freebsd-hackers Sat Jul 5 23:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09007 for hackers-outgoing; Sat, 5 Jul 1997 23:11:00 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09002 for ; Sat, 5 Jul 1997 23:10:56 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA24003; Sun, 6 Jul 1997 15:40:47 +0930 (CST) From: Michael Smith Message-Id: <199707060610.PAA24003@genesis.atrad.adelaide.edu.au> Subject: Re: Application os version compatibility? In-Reply-To: <199707060136.DAA28936@townsend.ericsson.se> from Kent Boortz at "Jul 6, 97 03:36:17 am" To: kent@erlang.ericsson.se Date: Sun, 6 Jul 1997 15:40:47 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG, kent@erlang.ericsson.se X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kent Boortz stands accused of saying: > > I know some just link "libc.2.2" to "libc.3.0" to get *some* > applications working that was built for another os version than > the one running but there must be a better way to create > applications that will survive over os version? Link statically. Or suggest to your users that they install the compat_x distributions. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[