From owner-freebsd-arch Sun Aug 6 10: 9: 1 2000 Delivered-To: freebsd-arch@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D573D37B769; Sun, 6 Aug 2000 10:08:57 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 6 Aug 2000 12:45:20 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Alexander Langer Cc: freebsd-arch@freebsd.org Subject: Re: ln -i ? In-Reply-To: <20000805213903.A3285@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Aug 2000, Alexander Langer wrote: > Hello! > > Linux's ln(1) has an -i option, which means "interactive" as rm/mv/cp > etc have, too. > > I wonder if that could be an option for our ln(1) as well. > > Could be useful. I agree; I haven't used it on Linux, but as long as it's unambiguous, like $ ln -i foo bar Link bar to foo? I must say that ln is the only utility I regularly have to think about every time I want to use both arguments. After losing a good 5 files to it, I stopped using the -f argument :) Anyway, it makes sense that if rm/mv/cp have -i and -v, ln should, too. > Alex > -- > cat: /home/alex/.sig: No such file or directory > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message