From owner-freebsd-security Sun Mar 14 13:40:15 1999 Delivered-To: freebsd-security@freebsd.org Received: from relay.acadiau.ca (relay.acadiau.ca [131.162.2.90]) by hub.freebsd.org (Postfix) with ESMTP id C7D5114C3D for ; Sun, 14 Mar 1999 13:40:11 -0800 (PST) (envelope-from 026809r@dragon.acadiau.ca) Received: from dragon.acadiau.ca (dragon.acadiau.ca [131.162.1.79]) by relay.acadiau.ca (8.8.5/8.8.5) with ESMTP id RAA29135 for ; Sun, 14 Mar 1999 17:39:20 -0400 (AST) Received: from localhost (026809r@localhost) by dragon.acadiau.ca (8.8.8+Sun/8.8.8) with ESMTP id RAA03126 for ; Sun, 14 Mar 1999 17:39:20 -0400 (AST) Date: Sun, 14 Mar 1999 17:39:20 -0400 (AST) From: Michael Richards <026809r@dragon.acadiau.ca> X-Sender: 026809r@dragon To: security@freebsd.org Subject: Getting rid of hard links? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. Just my $0.02. I hope you don't decide to get rid of hard links. We do a lot of stuff that requires hard links as a result of custom coded databases. I'm not familliar with the internals as I did not write it, however I am told our system can be ported over to OpenBSD with less trouble than fixing whatever requires the hard links. FreeBSD has served us well and I hope we don't have to abandon it :( It seems to me that the changes to rm/cp would be the smartest route because it wouldn't break anything and would seemingly address most of the issues brought up. -Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message