Puppy Japanese Forum considered to treat multi-byte charactor file name by following ways. Please mind to take our ways in Puppy 5.x.
1. ntfs: Using latest ntfs-3g in initrd
2. vfat: Changing mount option as "-o shortname=mixed,quiet,utf8" in init script, '/usr/sbin/pmount', ' /usr/local/bin/drive_all'
3. iso9660: Changing mount option as "-o iocharset=utf8" in init script, '/usr/sbin/pmount', ' /usr/local/bin/drive_all'
Especially, we strongly demand to use utf8 option in case handling vfat partition and Asian people easily use Puppy Linux without locale setting.
http://www.nslu2-linux.org/wiki/HowTo/M ... ileSystems
Suggestion from Japanese Forum
pup_xxx.sfs duplication problem
In case we save pup_save.2fs under sub-directory, but rc.shutdown try to copy pup_xxx.sfs to root-directory like below.
- /dev/sda1/puppy/pup_save.2fs
/dev/sda1/pup_xxx.sfs
- /dev/sda1/puppy/pup_save.2fs
/dev/sda1/puppy/pup_xxx.sfs
/dev/sda1/pup_xxx.sfs
Code: Select all
# diff rc.shutdown-upup476 rc.shutdown
724,725c724,727
< if [ "$DEV1FS" = "iso9660" ];then #test if booted off cd.
< if [ ! -f ${SMNTPT}/${DISTRO_FILE_PREFIX}-${DISTRO_VERSION}*.sfs ];then
---
> # 22 May 2009 - sfs file to be copied in same directory as pup_save
> FOLDER=$(dirname $SAVEFILE)
> if [ "$DEV1FS" = "iso9660" ];then #test if booted off cd.
> if [ ! -f ${SMNTPT}$FOLDER/${DISTRO_FILE_PREFIX}-${DISTRO_VERSION}*.sfs ];then
766c768
< cp -f $ONESFS $SMNTPT/
---
> cp -f $ONESFS $SMNTPT$FOLDER/
Password check at creating light encrypted pup_save.2fs
In case we select to make light encrypted pup_save.2fs, password input is required three times.
But then, there is no password checking system.
If we mistype password, rc.shutdown makes unreadable pup_save.2fs.
That is problem we think.
Since in rc.shutdown of Puppy Linux 4.2.0-JP, there is a password checking system developed by Mr. Voice.
http://sakurapup.browserloadofcoolness. ... 6&start=19
And Mr. Shino-Bar made the patch file which modifies rc.shutdown of upup-476 to get the password checking system.
(Also it works for the pup_xxx.sfs duplication problem above.)
http://shino.pos.to/linux/puppy/rc.shut ... etry.patch
But then, there is no password checking system.
If we mistype password, rc.shutdown makes unreadable pup_save.2fs.
That is problem we think.
Since in rc.shutdown of Puppy Linux 4.2.0-JP, there is a password checking system developed by Mr. Voice.
http://sakurapup.browserloadofcoolness. ... 6&start=19
And Mr. Shino-Bar made the patch file which modifies rc.shutdown of upup-476 to get the password checking system.
(Also it works for the pup_xxx.sfs duplication problem above.)
http://shino.pos.to/linux/puppy/rc.shut ... etry.patch
Creating pup_save.2fs before X shutdown
Mr. Shino-Bar made an I18N GUI tool "PupSave" for creating pup_save.2fs before X shutdown.
Puppy Linux 4.2.0-JP uses "PupSave" and we can read explanation of pup_save.2fs creating options in Japanese.
Now, "PupSave" for upup-476 is also released.
Please consider to apply "PupSave" in next Puppy Linux for non-English, multi-byte language users.
The page of "PupSave"
http://shino.pos.to/linux/pupsave.html
Puppy Linux 4.2.0-JP uses "PupSave" and we can read explanation of pup_save.2fs creating options in Japanese.
Now, "PupSave" for upup-476 is also released.
Please consider to apply "PupSave" in next Puppy Linux for non-English, multi-byte language users.
The page of "PupSave"
http://shino.pos.to/linux/pupsave.html
I totally agree with Bizuayeu's suggestions for 5.x development. Puppy was
developed originally for "English only" Linux distribution but it has been used
and loved by many non-English speaking Linux enthusiasts around the world.
Puppy needs to speak more languages to grow.
Can someone please tell me how to implement Bizuayeu's suggestions for
5.x development? So far, I have not seen people replying to his messages.
Thanks,
nyu
developed originally for "English only" Linux distribution but it has been used
and loved by many non-English speaking Linux enthusiasts around the world.
Puppy needs to speak more languages to grow.
Can someone please tell me how to implement Bizuayeu's suggestions for
5.x development? So far, I have not seen people replying to his messages.
Thanks,
nyu