Dan Nelson dnel...@allantgroup.com wrote:
... ufs filenames have no assumed character set.
I take it the / character is the same across all encodings then?
Last I knew the pathname separator was treated specially.
___
freebsd-questions@freebsd.org
Pieter de Goeje pie...@degoeje.nl wrote:
% touch ??? ? ?? ?? ???
% ls
??? ? ?? ?? ???
% rm ???\ ?\ ??\ \ ??\ ???\
%
(I don't have a clue what that means btw)
Here it
On Friday 29 May 2009 10:20:15 per...@pluto.rain.com wrote:
Pieter de Goeje pie...@degoeje.nl wrote:
% touch ??? ? ?? ?? ???
% ls
??? ? ?? ?? ???
% rm ???\ ?\ ??\ \
On 5/28/09 3:01 PM, Pieter de Goeje pie...@degoeje.nl wrote:
If you set your locale to UTF-8, you can use unicode characters in filenames.
works like a charm. thanks for the tip!
tom
___
freebsd-questions@freebsd.org mailing list
On Fri, 29 May 2009 01:20:15 -0700, per...@pluto.rain.com wrote:
Pieter de Goeje pie...@degoeje.nl wrote:
% touch ??? ? ?? ?? ???
% ls
??? ? ?? ?? ???
% rm ???\ ?\ ??\
In the last episode (May 28), Tom Worster said:
what character set/encoding is used for file names in freebsd when i have
a default ufs fs?
Whatever you want; ufs filenames have no assumed character set. zfs
defaults to the same rules, but can enforce only valid utf8 filenames if the
utf8only
On Thursday 28 May 2009 19:51:45 Tom Worster wrote:
what character set/encoding is used for file names in freebsd when i have a
default ufs fs?
tom
None.
UFS is 8 bit clean, so you can basically use it with any 8bit character set.
No encoding is enforced and no conversion is ever applied to
what character set/encoding is used for file names in freebsd when i have a
default ufs fs?
it just write whatever program will give it. UFS does not recode anything.
___
freebsd-questions@freebsd.org mailing list
