From bbc47747adfd7659d75eb24192b14799047ac4cc Mon Sep 17 00:00:00 2001 From: Vladimir 'phcoder' Serbinenko Date: Sun, 25 Dec 2011 15:40:43 +0100 Subject: [PATCH] * docs/grub.texi (Filesystems): Mention AFS. --- ChangeLog | 4 ++++ docs/grub.texi | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 2fc512655..6d5c704a7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2011-12-25 Vladimir Serbinenko + + * docs/grub.texi (Filesystems): Mention AFS. + 2011-12-25 Vladimir Serbinenko * docs/grub.texi (Filesystems): Clarify restrictions. diff --git a/docs/grub.texi b/docs/grub.texi index ddd44b11c..0ebdcf4c4 100644 --- a/docs/grub.texi +++ b/docs/grub.texi @@ -3933,9 +3933,9 @@ assumed to be encoded in UTF-8. @chapter Filesystems NTFS, JFS, UDF, HFS+, exFAT, long filenames in FAT, Joliet part of -ISO9660 are treated as UTF-16 as per specification. BFS is read as UTF-8, -again according to specification. BtrFS, cpio, tar, squash4, minix, minix2, -minix3, ROMFS, ReiserFS, XFS, ext2, ext3, ext4, FAT (short names), +ISO9660 are treated as UTF-16 as per specification. AFS and BFS are read +as UTF-8, again according to specification. BtrFS, cpio, tar, squash4, minix, +minix2, minix3, ROMFS, ReiserFS, XFS, ext2, ext3, ext4, FAT (short names), ISO9660 (plain and RockRidge), nilfs2, UFS1, UFS2 and ZFS are assumed to be UTF-8. This might be false on systems configured with legacy charset but as long as the charset used is superset of ASCII you should be able to