vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

* docs/grub.texi (Filesystems): Mention AFS.

Browse source
This commit is contained in:
Vladimir 'phcoder' Serbinenko 2011-12-25 15:40:43 +01:00
parent f63d6bf4a1
commit bbc47747ad
2 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
ChangeLog
View file

@ -1,3 +1,7 @@
2011-12-25 Vladimir Serbinenko <phcoder@gmail.com>
* docs/grub.texi (Filesystems): Mention AFS.
2011-12-25 Vladimir Serbinenko <phcoder@gmail.com> 2011-12-25 Vladimir Serbinenko <phcoder@gmail.com>
* docs/grub.texi (Filesystems): Clarify restrictions. * docs/grub.texi (Filesystems): Clarify restrictions.

6
docs/grub.texi
View file

@ -3933,9 +3933,9 @@ assumed to be encoded in UTF-8.
@chapter Filesystems @chapter Filesystems
NTFS, JFS, UDF, HFS+, exFAT, long filenames in FAT, Joliet part of 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, ISO9660 are treated as UTF-16 as per specification. AFS and BFS are read
again according to specification. BtrFS, cpio, tar, squash4, minix, minix2, as UTF-8, again according to specification. BtrFS, cpio, tar, squash4, minix,
minix3, ROMFS, ReiserFS, XFS, ext2, ext3, ext4, FAT (short names), minix2, minix3, ROMFS, ReiserFS, XFS, ext2, ext3, ext4, FAT (short names),
ISO9660 (plain and RockRidge), nilfs2, UFS1, UFS2 and ZFS are assumed 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 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 but as long as the charset used is superset of ASCII you should be able to