> for example, if you have 0 dirty blocks and then temporarily create
> 100MB file and then delete it *before* it is dumped. then you got
> 100MB of dirty blocks in the cache. these blocks will not be cleaned
> out by dump as the blocks are not referneced in the filesystem. these
> blocks belong to
thanks erik,
some careless misses.
int
checkname(char *s)
{
int i, n;
- Rune c;
+ Rune r;
if(s == nil || *s == 0)
return Ename;
if(*s == '.' && (s[1] == 0 || (s[1] == '.' && s[2] == 0)))
return Edot;
for(i = 0;; i += n)
this is correct. in general, the filesystem repairing aside, dump
will always just visit blocks that are referenced in the filesystem.
for example, if you have 0 dirty blocks and then temporarily create
100MB file and then delete it *before* it is dumped. then you got
100MB of dirty blocks in the
This is just a guess, but what does your $PATH look like?
On Sat, Mar 9, 2013 at 11:10 AM, Rubén Berenguel wrote:
> Hi everyone,
>
> I'm trying (just for the sake of getting it to work!) to read my (imap) mail
> via acme from plan9ports. I got the mail file server started in my namespace
> (I can
Hi everyone,
I'm trying (just for the sake of getting it to work!) to read my (imap)
mail via acme from plan9ports. I got the mail file server started in my
namespace (I can 9p ls mail and see my folders in INBOX for my work
account, but I can't get gmail to work... Probably needs TLS support and
i would think that a more complete solution
would be something like this. (not tested)
0xff isn't delete, and isn't valid utf. 0x7f is
valid utf, but also not useful in a file name.
- erik
int
checkname(char *s)
{
int i, n;
Rune c;
if(s == nil || *s == 0)
Hello,
DEL code is allowed in file name?
I find the following code in cwfs/sub.c.
/*
* what are legal characters in a name?
* only disallow control characters.
* a) utf avoids control characters.
* b) '/' may not be the separator
*/
int
checkname(char *n)
{
int i, c;
if(n =
