9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt@proweb.co.uk
To: 9fans@cse.psu.edu, /usr/matt/9fans@yourdomain.dom
Subject: [9fans] hack for /usr/$user/lib/face
Date: Tue,  2 Sep 2003 15:49:20 -0400	[thread overview]
Message-ID: <9e1325479927d8bc9af31de6553e031e@yourdomain.dom> (raw)


>>By the way, is there anyway to make some portion of the user's file
>> avoid from writing to venti, such those private or secret portrait
>>of someone. ☺  Of course, this should be set by that user, not 
>>system administrator.
>>  
>>
> 
> Put them on a different file server and bind them into your name space
> in your profile.

You could even write a script to download them from a web page and build your lib/face in a ramfs 


You can also choose to get rid of the
a/ b/ c/ d/ ... z/ folders, 
facesdb doesn't care about the directory names. It does a linear search through the .dict and then walks to $dir/$face

so in .dict
proweb.co.uk/matt 9fans/matt.1

works just fine

then you can 

bind -bc /n/ftp/secret_faces/9fans /usr/$user/lib/face/48x48x8/9fans

and keep a secret matt.1 on your ftp place



             reply	other threads:[~2003-09-02 19:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 19:49 matt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-02 19:57 matt
2003-09-02 19:50 matt
2003-09-02  3:55 matt
2003-09-02  6:44 ` okamoto
2003-09-02 14:16   ` Russ Cox
2003-09-02 14:48   ` boyd, rounin
2003-09-02 14:54     ` David Presotto
2003-09-02 15:04       ` andrey mirtchovski
2003-09-02 15:04       ` boyd, rounin
2003-09-02 17:05       ` Russ Cox
2003-09-02 22:15         ` david presotto
2003-09-03  2:00           ` Dan Cross
2003-09-03  7:15             ` Fco.J.Ballesteros
2003-09-02 21:33       ` Geoff Collyer
2003-09-03  1:07         ` okamoto
2003-09-03  2:00           ` Geoff Collyer
2003-09-03  2:29             ` okamoto
2003-09-03  2:33               ` Geoff Collyer
2003-09-03  2:38                 ` okamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e1325479927d8bc9af31de6553e031e@yourdomain.dom \
    --to=matt@proweb.co.uk \
    --cc=/usr/matt/9fans@yourdomain.dom \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).