Re: hexdump(1)/od(1) skip function off-by-one when offset == file length

2010-08-30 Thread Alexander Best
On Sun Aug 29 10, Garrett Cooper wrote: On Sun, Aug 29, 2010 at 9:27 AM, Alexander Best arun...@freebsd.org wrote: just discovered this issue while going through some linux mailinglists: otaku% dd if=/dev/urandom of=testfile bs=1 count=42 42+0 records in 42+0 records out 42 bytes

Re: hexdump(1)/od(1) skip function off-by-one when offset == file length

2010-08-30 Thread Dag-Erling Smørgrav
Alexander Best arun...@freebsd.org writes: *hehehe* that might be true. maybe they've bought the src from ATT? anyway i don't think the BSD license restricts you releasing code under a new license. so what they did seems fine to me. You can release the code under a different license, but you

Re: hexdump(1)/od(1) skip function off-by-one when offset == file length

2010-08-30 Thread Alexander Best
On Mon Aug 30 10, Dag-Erling Smørgrav wrote: Alexander Best arun...@freebsd.org writes: *hehehe* that might be true. maybe they've bought the src from ATT? anyway i don't think the BSD license restricts you releasing code under a new license. so what they did seems fine to me. You

hexdump(1)/od(1) skip function off-by-one when offset == file length

2010-08-29 Thread Alexander Best
just discovered this issue while going through some linux mailinglists: otaku% dd if=/dev/urandom of=testfile bs=1 count=42 42+0 records in 42+0 records out 42 bytes transferred in 0.000393 secs (106894 bytes/sec) otaku% hexdump -s 42 testfile 02a 134d b7b9 e085 da16 63b0 554a 1603 ead0

Re: hexdump(1)/od(1) skip function off-by-one when offset == file length

2010-08-29 Thread Garrett Cooper
On Sun, Aug 29, 2010 at 9:27 AM, Alexander Best arun...@freebsd.org wrote: just discovered this issue while going through some linux mailinglists: otaku% dd if=/dev/urandom of=testfile bs=1 count=42 42+0 records in 42+0 records out 42 bytes transferred in 0.000393 secs (106894 bytes/sec)