linux-AMD:~ # growisofs -dry-run -Z /dev/dvd -R
/home/digz/debian-31r4-amd64-binary-1.iso
Executing 'mkisofs -R /home/digz/debian-31r4-amd64-binary-1.iso |
builtin_dd of=/dev/dvd obs=32k seek=0'
I: -input-charset not specified, using UTF-8 (detected in locale settings)
mkisofs: Value too large for defined data type. File
/home/digz/debian-31r4-amd64-binary-1.iso is too large
X86_64 growisofs does not support files greater than 4.0 G,
linux-AMD:~ # du -sch /home/digz/debian-31r4-amd64-binary-1.iso
4.4G /home/digz/debian-31r4-amd64-binary-1.iso
--Digz
On 1/2/07, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2007-01-02 at 14:38 -0600, Darryl Gregorash wrote:
FWIW, when I create a 4000 MB slice, K3B shows it as 3.9 GB and 482 MB As we already know, sizes depend on whether you are a programmer, or
On 2007-01-01 13:27, James Knott wrote: live in the real world:
4 GB = 4*1024 MB = 4096 MB, and 4000 MB = 4000/1024 GB = 3.906 GB
Actually, no.
4 GB = 4*1000 MB = 4000 MB and 4000 MB = 4000/1000 GB = 4.00 GB
And:
4 GiB = 4*1024 MiB = 4096 MiB, and 4000 MiB = 4000/1024 GiB = 3.906 GiB
Programmers are using the wrong units: prefixes like mega or giga were invented way earlier than programmers were born; they (we) must change and use the new names (mebibyte).
The easiest reference I can find: http://en.wikipedia.org/wiki/MiB:
| The unit was defined by the International Electrotechnical Commission | (IEC) in December 1998. Use of mebibyte and related units is strongly | endorsed by IEEE and CIPM.
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFmurttTMYHG2NR9URAsxAAJ9qSFC8143V9a2jcnH8bek/jCF2XgCfexhX PoT9KaZK4skFbFOjSlo6lm4= =qPBR -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org