Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-15 Thread Eric van Gyzen
On 08/14/2013 10:13, Eric van Gyzen wrote: On 08/14/2013 09:53, Glen Barber wrote: On Wed, Aug 14, 2013 at 09:33:01AM -0500, Eric van Gyzen wrote: On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-15 Thread Glen Barber
On Thu, Aug 15, 2013 at 04:18:06PM -0500, Eric van Gyzen wrote: Is there any chance this will be fixed in 9.2? It would be nice to avoid introducing incompatibility in a release. I will commit it in a few hours, with 3-day scheduled MFC. I will send to RE for approval afterwards. Glen

makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Eric van Gyzen
NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI compatibility with NetBSD. NetBSD committed first (by one month), and neither change has gone into a

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Glen Barber
On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI compatibility with NetBSD. NetBSD

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Eric van Gyzen
On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Glen Barber
On Wed, Aug 14, 2013 at 09:33:01AM -0500, Eric van Gyzen wrote: On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Eric van Gyzen
On 08/14/2013 09:53, Glen Barber wrote: On Wed, Aug 14, 2013 at 09:33:01AM -0500, Eric van Gyzen wrote: On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Mehmet Erol Sanliturk
On Wed, Aug 14, 2013 at 10:06 AM, Glen Barber g...@freebsd.org wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Simon J. Gerraty
On Wed, 14 Aug 2013 08:10:41 -0500, Eric van Gyzen writes: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? No, the -p should have been dropped before we committed to FreeBSD. But it is

Re: makefs Sparse Files: NetBSD CLI Compatibility

2013-08-14 Thread Eric van Gyzen
On 08/14/2013 14:05, Simon J. Gerraty wrote: On Wed, 14 Aug 2013 08:10:41 -0500, Eric van Gyzen writes: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? No, the -p should have been dropped