term% for(i in`{seq 1 5000}) touch $i
touch: 4091: cannot create: '4091' no space on device
looks to me like readdir() only reads the direct blocks, but that
doesn't seem right since 4090*264 ~= 1mb.
- erik
unicode codepoints (runes) are abstract. we need to deal with encodings.
the encoding utf-8 uses is not a single byte for anything above 0x7f.
so essentially the encoding phase would be name[i] = (uchar)r. the decoding
phase
would be r = (Rune)name[i].
Thank you. I modified trfs.c and
I have some files on an external ext2 drive that have whitespace and
umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv
presents umlauts as a question mark symbol (�) and won't let me access
the file (error: file does not exist).
Where is the problem? These files show correctly
On Thursday 13 of October 2011 13:15:57 slash wrote:
I have some files on an external ext2 drive that have whitespace and
umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv
presents umlauts as a question mark symbol (�) and won't let me access
the file (error: file does not
On Oct 13, 2011 at 07:16, slash wrote:
I have some files on an external ext2 drive that have whitespace and
umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv
presents umlauts as a question mark symbol (�) and won't let me access
the file (error: file does not exist).
On Thu Oct 13 07:38:54 EDT 2011, dexen.devr...@gmail.com wrote:
On Thursday 13 of October 2011 13:15:57 slash wrote:
I have some files on an external ext2 drive that have whitespace and
umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv
presents umlauts as a question mark
if you know what the charset on disk is, you could probablly hack ext2fs
into translating names. or (less hacky) you could write a transliterating fs,
or add this to trfs' duties.
Thank you. So now I know ext2srv is not doing any file name conversion. Good.
Say I wanted to add the following
example of whitespace handling etc in trfs.c and recompile. Now, where
is the latin-1 code table again...
latin-1 bytes 00-FF turn into unicode runes 00-FF.
On Thu Oct 13 11:27:00 EDT 2011, slash.9f...@gmail.com wrote:
latin-1 bytes 00-FF turn into unicode runes 00-FF.
Then why doesn't it Just Work? Now I am confused (again).
unicode codepoints (runes) are abstract. we need to deal with encodings.
the encoding utf-8 uses is not a single byte
latin-1 bytes 00-FF turn into unicode runes 00-FF.
Then why doesn't it Just Work? Now I am confused (again).
] on behalf of Iruata Souza
Sent: Tue 5/13/2008 8:40 PM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] ext2srv
On Tue, May 13, 2008 at 9:07 AM, [EMAIL PROTECTED] wrote:
would help me much until I get rid of linux completely. I have dirs with big
photos (~ 300MB each) so I had
Does it still suffer from the 2GB size problem, or s it solved already?
Thanks,
++pac
On 5/12/08, Iruata Souza [EMAIL PROTECTED] wrote:
9fans,
I have hacked ext2srv to support symlinks so that now, when resolving
a name, a walk will present the client with the file pointed to by the
On Tue, May 13, 2008 at 7:32 AM, [EMAIL PROTECTED] wrote:
Does it still suffer from the 2GB size problem, or s it solved already?
Thanks,
sincerely, I added symlinks because of fgb's (and others) needs.
I can take a look on the 2GB issue too if that would help someone.
iru
] on behalf of Iruata Souza
Sent: Tue 5/13/2008 1:40 PM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] ext2srv
On Tue, May 13, 2008 at 7:32 AM, [EMAIL PROTECTED] wrote:
Does it still suffer from the 2GB size problem, or s it solved already?
Thanks,
sincerely, I added symlinks
On Tue, May 13, 2008 at 9:07 AM, [EMAIL PROTECTED] wrote:
would help me much until I get rid of linux completely. I have dirs with big
photos (~ 300MB each) so I had to split them into subdirs to hadle them via
ext2srv. i also tried tofiddle with the source, but I gave up.
since i already
15 matches
Mail list logo
