Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Eitan Adler
The attached patch adds an x option to rm(1) to avoid cross filesystem boundaries. This has been committed to DragonFlyBSD and FreeBSD. It has been submitted to NetBSD as well. -- Eitan Adler [demime 1.01d removed an attachment of type application/octet-stream which had a name of

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Eitan Adler
On 26 April 2013 14:30, Eitan Adler li...@eitanadler.com wrote: The attached patch adds an x option to rm(1) to avoid cross filesystem boundaries. This has been committed to DragonFlyBSD and FreeBSD. It has been submitted to NetBSD as well. Inline: Index: rm.c

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Stuart Henderson
On 2013/04/26 14:30, Eitan Adler wrote: The attached patch adds an x option to rm(1) to avoid cross filesystem boundaries. Isn't it better to just use find(1)'s -x option for this? It would be silly to add an option like this to all the places where it might be useful (besides rm this type of

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Eitan Adler
On 26 April 2013 18:34, Stuart Henderson s...@spacehopper.org wrote: On 2013/04/26 14:30, Eitan Adler wrote: The attached patch adds an x option to rm(1) to avoid cross filesystem boundaries. Isn't it better to just use find(1)'s -x option for this? It would be silly to add an option like

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Philip Guenther
On Fri, 26 Apr 2013, Eitan Adler wrote: On 26 April 2013 18:34, Stuart Henderson s...@spacehopper.org wrote: On 2013/04/26 14:30, Eitan Adler wrote: The attached patch adds an x option to rm(1) to avoid cross filesystem boundaries. Isn't it better to just use find(1)'s -x option for

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Eitan Adler
On 26 April 2013 20:05, Philip Guenther guent...@sendmail.com wrote: We had a similar conversion on -hackers: http://freebsd.1045724.n5.nabble.com/Some-improvements-to-rm-1-td5806672.html#none Note that OpenBSD doesn't have cp -x either. Ah, I see. I sent this patch because { Free, Net,

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Ted Unangst
On Fri, Apr 26, 2013 at 20:17, Eitan Adler wrote: Ah, I see. I sent this patch because { Free, Net, DragonFly } BSD all have this feature. After some private discussion I found out that OpenBSD has a much strong aversion to non-POSIX features than the others. fwiw, they did this, you

Re: Add x option to rm(1) to avoid cross filesystem boundaries.

2013-04-26 Thread Eitan Adler
On 27 April 2013 00:57, Ted Unangst t...@tedunangst.com wrote: On Fri, Apr 26, 2013 at 20:17, Eitan Adler wrote: Ah, I see. I sent this patch because { Free, Net, DragonFly } BSD all have this feature. After some private discussion I found out that OpenBSD has a much strong aversion to