Sponsored Content
Full Discussion: What happened to mkisofs ?
Top Forums UNIX for Dummies Questions & Answers What happened to mkisofs ? Post 302142434 by Bobby on Friday 26th of October 2007 06:37:37 AM
Old 10-26-2007
Question What happened to mkisofs ?

I've been using a mkisofs line like this for years without problem

# mkisofs -J -R -V 'Vol Label' -o /output/path/FILE.ISO /input/path/

Now, however, it gives a UTR-8 character message at the start

Code:
INFO:   UTF-8 character encoding detected by locale settings.
        Assuming UTF-8 encoded filenames on source filesystem,
        use -input-charset to override.

And if there are any files with, er, special characters the program aborts with this message.

Code:
Incorrectly encoded string (Brobälläri.jpg) encountered.
Possibly creating an invalid Joliet extension. Aborting.

After considerable reading, I've come up with this added option and the ISO finishes being made.

-input-charset default

My problem is that I no longer feel confident with the file being generated and want to ask whether this is an appropriate solution. I'm on fedora 6 and I'm sure that has something to do with it. It's the first time on FC6 and I've never run into this problem before.

Issuing this command

# mkisofs -input-charset help

yeilds the following list of character sets but I'm unsure which gives the broadest coverage, or whether the 'default' option is good enough.

Known charsets are:, cp10081, cp10079, cp10029, cp10007, cp10006, cp10000, koi8-u, koi8-r, cp1251, cp1250, cp874, cp869, cp866, cp865, cp864, cp863, cp862, cp861, cp860, cp857, cp855, cp852, cp850, cp775, cp737, cp437, iso8859-15, iso8859-14, iso8859-9, iso8859-8, iso8859-7, iso8859-6, iso8859-5, iso8859-4, iso8859-3, iso8859-2, iso8859-1.


Comments, remarks, ideas, suggestions?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ISO creation problem :-: mkisofs

Hi, I am trying to burn a directory containing some install scripts/executables etc onto a cd. I am using redhat v7.0. I have tried using mkisofs, but so far have not been able to get the case of the filenames to be correct. one file is called: startInstaller but it always comes out as... (1 Reply)
Discussion started by: ghoti
1 Replies

2. Post Here to Contact Site Administrators and Moderators

what happened?

A few hours ago I made several reasonable posts to this forum and now they have dissapeared. I read and followed the rules, and I sure didn't break any, but gone they are :( I know I only joined the forum today, but do the posts have to be authorised or something? ... (14 Replies)
Discussion started by: cw1972
14 Replies

3. What is on Your Mind?

what happened to ygor..??

:D anyone hear from ygor..? haven't seen him post in a while... wonder what he is up to..! the last i heard he was the D25khan.. that was him right guys ??? being a newbie myself that is one dude that i admire. him Norsk, Perdebro, RTM , Google and Zazzybob all real genius.. and the most... (2 Replies)
Discussion started by: moxxx68
2 Replies

4. Shell Programming and Scripting

What happened with AWK?

The second script seems not to work. (3 Replies)
Discussion started by: endeavour1985
3 Replies

5. Solaris

mkisofs and long file names

Well im using mkisofs to create iso images in Solaris 10 and then i use cdrw -i to burn the images to the cd the problem which i noticed recent ( im new to mkisofs) i noticed its break the long file names making them shorter i searched in its help and i find two parameters one -l and one... (2 Replies)
Discussion started by: XP_2600
2 Replies

6. UNIX for Dummies Questions & Answers

What Happened :(

Hello, I have created a dosrename script and it was working fine unitl today. I can't think what i have changed (don't think i have to be honest). The error is when i run the script it says the file i am trying to rename does not exist when it blatently does. Or is it a typo when i run the... (4 Replies)
Discussion started by: jazz8146
4 Replies

7. UNIX for Dummies Questions & Answers

Help with mkisofs

Hello, I am attempting to recreate an iso from a set of files. At this point I seem to be stuck on the creation process. I have reviewed man mkisofs, which returns genisofs. Below is the actual command, and what each piece of information seems to provide mike@presario:~$ sudo mkisofs -V... (2 Replies)
Discussion started by: mg92865
2 Replies

8. Shell Programming and Scripting

Mp3 backup using find, mkisofs

Hi. I want to create a Linux script to find all local mp3 files, create an ISO image. Later I will attempt to use growisofs Something like this: find ~ -name "*.mp3" | xargs mkisofs -o musicbackup tried variations on this but no luck. (4 Replies)
Discussion started by: lancest
4 Replies

9. Solaris

How use the cdrw and mkisofs command...

Hi Guys. I am trying to tranfer the explorer output to a CD .... But I have serious doubt about use the cdrw and mkisofs command.. with the proupose of to make and tranfer the contents. Thank in Advance. AGADEA (5 Replies)
Discussion started by: aggadtech08
5 Replies

10. Shell Programming and Scripting

mkisofs to create iso

Hi all, I got the following problem. I run this command. mkisofs -o mynew.iso -l -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table base images isolinux pc_doc and I get all files from base, images, isolinux and pc_doc in the root dir of the iso. I want a... (2 Replies)
Discussion started by: stinkefisch
2 Replies
code_page(5)							File Formats Manual						      code_page(5)

NAME
code_page, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861, cp862, cp863, cp865, cp866, cp869, cp874, cp932, cp936, cp949, cp950, cp1250, cp1251, cp1252, cp1253, cp1254, cp1255, cp1256, cp1257, cp1258, dingbats, symbol - Coded character sets that are used on Mi- crosoft Windows and NT systems DESCRIPTION
Code pages are coded character sets that are used on Microsoft Windows, Windows 95, and NT systems. Just as there are different UNIX code- sets, there are different PC code pages, each supporting a particular set of character encodings. A Tru64 UNIX system supplies one locale, en_US.cp850, that directly supports a PC code-page format (MS-DOS Latin 1). For all other locales, data in code-page format is supported only through codeset converters. These converters can be run directly by users or by software or applications that exchange data between PC and Tru64 UNIX systems. Fonts and other kinds of character support are available only for the native UNIX codeset to which a code page can be converted. See the i18n_intro(5) reference page for introductory information on locales and codesets. See the iconv_intro(5) reference page for an introduction to codeset conversion and the name format and location of codeset con- verters. The following table lists and describes the code pages that have conversion support on a Tru64 UNIX system. An asterisk (*) follows the names of code pages that include support for the Euro currency sign (C=). ------------------------------------------------------ Code Page Description ------------------------------------------------------ cp437 MS-DOS United States cp737 Greek cp775 Baltic languages (1) cp850 MS-DOS Multilingual (Latin-1) cp852 MS-DOS Slavic (Latin-2) cp855 IBM Cyrillic cp857 IBM Turkish cp860 MS-DOS Portuguese cp861 MS-DOS Icelandic cp862 Hebrew cp863 MS-DOS Canadian French cp865 MS-DOS Nordic languages cp866 MS-DOS Russian cp869 IBM Modern Greek cp874 * MS-DOS Thai cp932 Japanese cp936 Chinese (People's Republic of China) cp949 Korean cp950 Chinese (Hong Kong) cp1250 * Windows Latin-2 cp1251 * Windows Cyrillic cp1252 * Windows Latin-1 cp1253 * Windows Greek cp1254 * Windows Turkish cp1255 * Windows Hebrew cp1256 * Windows Arabic cp1257 * Windows Baltic (1) cp1258 * Windows Vietnamese dingbats Microsoft dingbat characters symbol Microsoft miscellaneous symbol characters ------------------------------------------------------ (1) Baltic languages include Estonian, Latvian, and Lithuanian. (2) Latin-2 languages include Albanian, Croatian, Czech, Faeroese, Hungarian, Polish, Romanian, Latin Serbian, Slovak, and Slovenian. (3) Cyrillic languages include Byelorussian, Bulgarian, and Russian. In all cases, a code page can be converted to and from the UCS-2, UCS-4, and UTF-8 codesets. In addition, some code pages can be converted directly to ISO codesets as shown in the following table, although some data loss may occur. ------------------------------------------ Code Page Can Be Converted Directly to: ------------------------------------------ cp437 ISO8859-1 cp737 ISO8859-7 cp775 ISO8859-4 cp850 ISO8859-1 cp852 ISO8859-2 cp855 ISO8859-5 cp857 ISO8859-9 cp860 ISO8859-1 cp861 ISO8859-1 cp862 ISO8859-8 cp863 ISO8859-1 cp865 ISO8859-1 cp866 ISO8859-5 cp869 ISO8859-7 cp874 TACTIS cp1252 ISO8859-1, ISO8859-15 ------------------------------------------ See Unicode(5) for information about UCS-2, UCS-4, and UTF-8. Reference pages for UNIX implementations of the ISO codesets have the name format iso8859-number(5). For Traditional Chinese and Japanese, there are no codeset converters whose names include the name of a code page because identical charac- ter encoding is provided in existing UNIX codesets. For Traditional Chinese, character encoding in PC code-page format (cp950) is identical to that in the Big-5 (big5) codeset. For Japanese, character encoding in PC code-page format (cp932) is identical to that in the Shift JIS (SJIS) codeset. Therefore, the codeset converters whose names include big5 and SJIS can be used to convert data in and out of PC code-page format for the supported languages. Caution for Conversion of Korean and Simplified Chinese Conversion of text that starts out in code-page format (cp949) to the DEC Korean (deckorean) codeset may result in loss of data. All of the Tru64 UNIX codeset equivalents for cp949 support all the Hanja and miscellaneous characters also supported by the code page. However, only the UCS-2, UCS-4, and UTF-8 codesets support the complete set of Hangul characters supported by the cp949 code page. The deckorean codeset supports only a subset of these Hangul characters. Therefore, if data is converted from cp949 format to UCS-2, UCS-4, or UTF-8, no data is lost. However, if the data is then converted from UCS-2, UCS-4, or UTF-8 to deckorean, the unsupported Hangul characters will be lost. The DEC Hanzi (dechanzi) codeset uses the same encoding format as the PC code page used for Simplified Chinese (cp936) but does not support all the characters supported by the code page. Therefore, you can use converters with dechanzi in the converter name to convert text to and from cp936 format, but the operation may result in some loss of data. SEE ALSO
Commands: iconv(1) Functions: iconv(3), iconv_close(3), iconv_open(3) Others: i18n_intro(5), iconv_intro(5), iso8859-1(5), iso8859-2(5), iso8859-4(5), iso8859-5(5), iso8859-7(5), iso8859-8(5), iso8859-15(5), Unicode(5) code_page(5)
All times are GMT -4. The time now is 09:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy