From owner-freebsd-doc Sun Oct 29 10:48:10 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12523 for doc-outgoing; Sun, 29 Oct 1995 10:48:10 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA12501 ; Sun, 29 Oct 1995 10:48:05 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26329; Sun, 29 Oct 1995 13:47:49 -0500 Date: Sun, 29 Oct 1995 13:47:49 -0500 From: "Garrett A. Wollman" Message-Id: <9510291847.AA26329@halloran-eldar.lcs.mit.edu> To: Dmitry Khrustalev Cc: freebsd-bugs@freebsd.org, doc@freebsd.org Reply-To: wollman@lcs.mit.edu Subject: Re: 2.0.5-RELEASE: NFS cannot export 2 dirs on 1 partition? In-Reply-To: References: <199510281408.QAA06981@dog.farm.org> Sender: owner-doc@freebsd.org Precedence: bulk [Sorry for the cross-post. This should go into the handbook if it hasn't already. Note Reply-To.] < said: >> can't change attributes for /usr/ports >> bad exports list line /usr/ports [machines where dir in exported to] >> >> and same for /xvar/pubhome. >> > This is intended behavior. You can have only one export per filesystem. > Check -alldirs export option, maybe it will help you. Just to expand the story a little bit... In the beginning, Sun's kernel NFS server didn't make any (host) access-control checks at all. If you give it a file handle, it will believe out of the goodness of its heart that your intentions are pure and you obtained that handle legitimately. Sun's NFS implementation relied solely on `mountd' to perform ALL of its host access-control checking. Naturally, with packet-sniffing being as common as it is, this is a really, really bad idea (and one of the reasons why people say that NFS combines all the wonderful filesystem semantics of MS-DOS with all the security of MS-DOS). In FreeBSD, by contrast, all accesses are checked /by the kernel/ against a per-mount-point host access-control list. This can raise some problems for people because there is only one such list per mount point, so it is impossible to provide different access control for different directories in the same filesystem. Rather than permit an even greater false sense of security, FreeBSD simply disallows the operation. It is theoretically possible to hang per-host access controls off of every directory or even file, but that would be an incredibly large amount of work and overhead for a miniscule gain in security. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-doc Mon Oct 30 12:33:50 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA14459 for doc-outgoing; Mon, 30 Oct 1995 12:33:50 -0800 Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA14452 for ; Mon, 30 Oct 1995 12:33:42 -0800 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.jdl.com (8.6.11/8.6.9) with SMTP id OAA18294; Mon, 30 Oct 1995 14:32:40 -0600 Message-Id: <199510302032.OAA18294@chrome.jdl.com> X-Authentication-Warning: chrome.jdl.com: Host localhost.jdl.com didn't use HELO protocol To: freebsd-doc@freebsd.org, kelly@fsl.noaa.gov Subject: Printing Clarity-Index: null Reply-To: jdl@chromatic.com Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Mon, 30 Oct 1995 14:32:39 -0600 From: Jon Loeliger Sender: owner-doc@freebsd.org Precedence: bulk Hi folks, Just wanted to let you know that I finally got tired of NOT being able to print straight ASCII files on my Postscript printer, and decided to do something about it. Well, I hit the ol' "Printing" section of the Handbook, and found exactly what I needed and it all worked great! Appriciate the hard work! jdl From owner-freebsd-doc Tue Oct 31 10:19:35 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA14162 for doc-outgoing; Tue, 31 Oct 1995 10:19:35 -0800 Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA14153 for ; Tue, 31 Oct 1995 10:19:20 -0800 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id TAA07582 for freebsd-doc@freefall.cdrom.com; Tue, 31 Oct 1995 19:16:23 +0100 Date: Tue, 31 Oct 1995 19:16:23 +0100 From: "Christoph P. Kukulies" Message-Id: <199510311816.TAA07582@gilberto.physik.rwth-aachen.de> To: freebsd-doc@freefall.FreeBSD.org Subject: routing.sgml typos Sender: owner-doc@FreeBSD.org Precedence: bulk Browsing through the handbook I produced today from a .ps file (tex->dvips - the TeX fonts are really ugly - much too thin) a typo sprung into my eyes: *** routing.sgml Tue Oct 31 19:07:46 1995 --- routing.sgml.orig Tue Oct 31 19:07:19 1995 *************** *** 220,226 **** often used when we need to implement packet filtering or firewall security in either or both directions. ! Routing propagation

We have already talked about how we define our routes to the outside world, but not about how the outside world --- 220,226 ---- often used when we need to implement packet filtering or firewall security in either or both directions. ! Routing propogation

We have already talked about how we define our routes to the outside world, but not about how the outside world *************** *** 252,258 **** It is the task of your service provider to advertise to the backbone sites that they are the point of connection (and thus the path inward) for your site. This is known ! as route propagation.