![]() |
Unslung.UnslungLanguageSupport HistoryHide minor edits - Show changes to markup September 09, 2008, at 12:39 PM
by -- standard names used by Linksys firmware
Changed lines 10-11 from:
firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". to:
firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "Western Europe/Latin 1(850)". Changed lines 18-19 from:
Note: code page 850 is included by default with Unslung 6.10-beta. to:
Note: code page 850 (Western Europe/Latin 1) is included by default with Unslung 6.10-beta and dos not need to be installed manually. Changed lines 24-25 from:
to:
September 03, 2008, at 09:53 PM
by -- undid spam
Changed lines 1-57 from:
<url>http://heroii.webhosting4free.info/sarahpal8b/|sensacion</url> to:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for Additional Languages to Unslung 6.xNote: code page 850 is included by default with Unslung 6.10-beta. To add support for other languages, all that is required is to add the necessary kernel module, according to the necessary code page, and arrange for the module to be loaded at boot time. The list of modules currently available for Unslung 6.x is:
First, install the desired kernel module using (:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
Test by manually loading the module: Finally, arrange for the language support module to be automatically loaded at boot via a diversion script. See DiversionScripts for information on diversion scripts. Create a file called (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp852 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. September 03, 2008, at 06:41 PM
by -- NpTtlJrIgnAjKGUiJMd
Changed lines 1-57 from:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for Additional Languages to Unslung 6.xNote: code page 850 is included by default with Unslung 6.10-beta. To add support for other languages, all that is required is to add the necessary kernel module, according to the necessary code page, and arrange for the module to be loaded at boot time. The list of modules currently available for Unslung 6.x is:
First, install the desired kernel module using (:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
Test by manually loading the module: Finally, arrange for the language support module to be automatically loaded at boot via a diversion script. See DiversionScripts for information on diversion scripts. Create a file called (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp852 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
<url>http://heroii.webhosting4free.info/sarahpal8b/|sensacion</url> September 02, 2008, at 01:44 PM
by -- updated info and formatting
Added line 5:
Changed lines 10-26 from:
firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
to:
firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for Additional Languages to Unslung 6.xNote: code page 850 is included by default with Unslung 6.10-beta. To add support for other languages, all that is required is to add the necessary kernel module, according to the necessary code page, and arrange for the module to be loaded at boot time. The list of modules currently available for Unslung 6.x is:
First, install the desired kernel module using Changed line 41 from:
to:
Changed line 44 from:
to:
Test by manually loading the module: Changed lines 46-47 from:
to:
Finally, arrange for the language support module to be automatically loaded at boot via a diversion script. See DiversionScripts for information on diversion scripts. Create a file called Changed line 51 from:
insmod nls_cp850 to:
insmod nls_cp852 Changed lines 54-58 from:
Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. August 31, 2008, at 08:21 PM
by -- undid spam
Changed lines 1-45 from:
HvFDgc? Great site, <a href="http://how-does-home-insurance-work.supertodayusa.info/map.html">how does home insurance work</a>, [url="http://how-does-home-insurance-work.supertodayusa.info/map.html"]how does home insurance work[/url], http://how-does-home-insurance-work.supertodayusa.info/map.html how does home insurance work, pzfvo, to:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. August 31, 2008, at 01:12 PM
by -- MhfiYAVyr
Changed lines 1-45 from:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
HvFDgc? Great site, <a href="http://how-does-home-insurance-work.supertodayusa.info/map.html">how does home insurance work</a>, [url="http://how-does-home-insurance-work.supertodayusa.info/map.html"]how does home insurance work[/url], http://how-does-home-insurance-work.supertodayusa.info/map.html how does home insurance work, pzfvo, August 31, 2008, at 10:16 AM
by -- Removed spam
Changed lines 1-45 from:
Interesting, <a href="http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html">britney spears vma video</a>, [url="http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html"]britney spears vma video[/url], http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html britney spears vma video, sawu, to:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. August 31, 2008, at 06:13 AM
by -- rAytesSNC
Changed lines 1-45 from:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
Interesting, <a href="http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html">britney spears vma video</a>, [url="http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html"]britney spears vma video[/url], http://destor.nookiehost.com/britneysa1/britney-spears-vma-video.html britney spears vma video, sawu, July 16, 2008, at 09:59 AM
by -- trolling
Changed lines 1-45 from:
to:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. July 13, 2008, at 11:39 PM
by -- NWIZqIQCdwmP
Changed lines 1-45 from:
This article pertains to:
Language Support in Unslung 6.xThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
(:table border=0 width=100% bgcolor=#eeffee:)
(:cell:)
(:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount. NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
December 31, 2007, at 01:51 AM
by -- Update for Unslung 6.10-beta
Changed lines 2-4 from:
Language Support in Unslung 6.8-betato:
Language Support in Unslung 6.xChanged line 9 from:
firmware only has support for "USA (437)" Language Support. Additional languages can be added to:
firmware only has support for "USA (437)" Language Support. Unslung 6.10-beta supports both "USA (437)" and "(850)". Additional languages can be added Changed lines 17-20 from:
Adding Support for CP 850 (Western Europe/Latin 1)to:
Adding Support for CP 850 (Western Europe/Latin 1) to Unslung 6.8-betaNB: Code page 850 is built-in with Unslung 6.10-beta. June 15, 2007, at 04:56 AM
by --
Added lines 23-24:
(:table border=0 width=100% bgcolor=#eeffee:) (:cell:) Changed lines 26-27 from:
to:
(:tableend:) June 15, 2007, at 04:54 AM
by --
Changed lines 22-23 from:
to:
Changed lines 39-65 from:
NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. PROBLEMSI run (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) ipkg install kernel-module-nls-cp850 (:tableend:) And get an error: (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) Nothing to be done An error ocurred, return value: 4. Collected errors: Cannot find package kernel-module-nls-cp850. Check the spelling or perhaps run 'ipkg update' (:tableend:) No matter what I do. Also I'm not able to start the module so I cannot mount NTFS drives. SOLVED: I just ensured the disk works with "USA (437)" on my PC. After that and changing CP it worked. Din't find package. Try: (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) ipkg install http://ipkg.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/kernel-module-nls-cp850_2.4.22.l2.3r63-r10_ixp4xxbe.ipk (:tableend:) to:
NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. June 15, 2007, at 04:51 AM
by -- Fixed link
Changed lines 63-66 from:
ipkg install http://ipkg-us-dyoung.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/kernel-module-nls-cp850_2.4.22.l2.3r63-r10_ixp4xxbe.ipk (:tableend:) THIS LINK DON'T WORKS :( to:
ipkg install http://ipkg.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/kernel-module-nls-cp850_2.4.22.l2.3r63-r10_ixp4xxbe.ipk (:tableend:) June 14, 2007, at 04:01 PM
by --
Changed lines 64-66 from:
(:tableend:) to:
(:tableend:) THIS LINK DON'T WORKS :( December 02, 2006, at 11:17 AM
by -- !!! Solution
Changed lines 57-64 from:
Din't find package. to:
Din't find package. Try: (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) ipkg install http://ipkg-us-dyoung.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/kernel-module-nls-cp850_2.4.22.l2.3r63-r10_ixp4xxbe.ipk (:tableend:) November 12, 2006, at 10:01 PM
by -- Solution (RTFM)
Changed lines 55-57 from:
No matter what I do. Also I'm not able to start the module so I cannot mount NTFS drives. Any help appreciated to:
No matter what I do. Also I'm not able to start the module so I cannot mount NTFS drives. SOLVED: I just ensured the disk works with "USA (437)" on my PC. After that and changing CP it worked. Din't find package. November 12, 2006, at 09:53 PM
by -- Add an error. When solved I will add solution
Added lines 39-55:
PROBLEMSI run (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) ipkg install kernel-module-nls-cp850 (:tableend:) And get an error: (:table border=0 width=80% bgcolor=#eeeeff:) (:cell:) Nothing to be done An error ocurred, return value: 4. Collected errors: Cannot find package kernel-module-nls-cp850. Check the spelling or perhaps run 'ipkg update' (:tableend:) No matter what I do. Also I'm not able to start the module so I cannot mount NTFS drives. Any help appreciated April 14, 2006, at 12:00 AM
by --
Changed line 38 from:
NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted with the external disk attached (i.e. in "unslung" mode). If it is booted without external disks, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. to:
NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted in "unslung" mode -- external root disk or flash disk attached. If it is booted without external root device, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. April 13, 2006, at 11:54 PM
by -- typo
Changed line 24 from:
to:
April 13, 2006, at 11:48 PM
by --
Added lines 1-3:
This article pertains to:
Deleted line 4:
Changed lines 22-27 from:
Test the by manually loading the module: "
Create the file to:
Changed lines 31-32 from:
insmod nls_cp850 return 1=] to:
insmod nls_cp850 return 1=] Deleted line 33:
Added lines 37-38:
NOTE: Be aware that this change, by design, will only take effect if the NSLU2 is booted with the external disk attached (i.e. in "unslung" mode). If it is booted without external disks, it will boot from internal flash, and will lack support for the added code page(s). This will have the side effect that your NSLU2 will not be able to mount FAT or NTFS volumes when booted up from the internal flash. April 13, 2006, at 11:40 PM
by --
Added lines 1-35:
Language Support in Unslung 6.8-betaThe NSLU2 permits the user to select the character set most appropriate for the user's language. This is normally set on the "Administration -> System" web page in the Linksys GUI. Due to kernel size constraints and limited space in the NSLU2 flash, the base Unslung 6.8-beta firmware only has support for "USA (437)" Language Support. Additional languages can be added if desired, however. One of the symptoms of selecting a language that is not supported by the your configuration of Unslung is that it will be unable to automatically mount FAT or NTFS volumes. First, if it's not broken, don't fix it. If you can use the "USA (437)" setting, do so - it's simpler, and will work if the NSLU2 is booted from the disk or from internal flash. Adding Support for CP 850 (Western Europe/Latin 1)Adding support for code page 850, Western Europe/Latin 1, is fairly simple because the Samba files for that code page are already present. All that is required is to add the necessary kernel module, and arrange for the kernel module to be loaded at boot time.
Test the by manually loading the module: "
Create the file #!/bin/sh insmod nls_cp850 return 1 (:tableend:) Now leave the FAT/NTFS drive attached, reboot the NSLU2, and you should see the drive automatically mount.
view ·
edit ·
print ·
history ·
Last edited by fcarolo.
Based on work by fcarolo, sarah palin, Dimitri, pembo, Dighenis, kralikba, girls, mwester, Natalia Pujol, mg660a yahoodotcom, and Pijama Master. Originally by mwester. Page last modified on September 09, 2008, at 12:39 PM
|