9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] floppy based standalone auth server
Date: Mon,  2 Dec 2002 10:33:26 +0200	[thread overview]
Message-ID: <20021202103326.J22558@cackle.proxima.alt.za> (raw)
In-Reply-To: <850f05e346d014be5db03a148993b4bd@orthanc.cc.titech.ac.jp>; from YAMANASHI Takeshi on Mon, Dec 02, 2002 at 05:05:16PM +0900

On Mon, Dec 02, 2002 at 05:05:16PM +0900, YAMANASHI Takeshi wrote:
>
> I use two floppies for the auth serv.
> One for kernel, and the other for fs.

In two floppy drives, I presume.  Pity that 2.88M floppies never
became common.  But then we'd find ways to exceed their capacity :-)

> Both are DOS formatted floppies.
> Attached at the end of this mail is
> the output of `du -a' of the fs floppy.
>
Thank you.  I think I'll post a "proto" file to the wiki, this has
bugged me for a long time.

> It seems that dossrv is serving as an cache mechanism.
>
Hm, interesting.  I never considered that, but there are lots of
little things in Plan 9 that keep surprising me.

> 	1	./plan9.nvr
> 	79	./386/init
> 	124	./386/bin/rc
> 	29	./386/bin/cat
> 	46	./386/bin/echo
> 	61	./386/bin/ls
> 	51	./386/bin/ps
> 	36	./386/bin/date
> 	86	./386/bin/ip/ipconfig
> 	86	./386/bin/ip

I think you'll get away without ip and ip/ipconfig as /ipconfig should
be built into the kernel. /rc/bin/cpurc will need to be adjusted.

> 	122	./386/bin/ndb/cs
> 	122	./386/bin/ndb
> 	95	./386/bin/aux/listen
> 	95	./386/bin/aux
> 	94	./386/bin/auth/keyfs
> 	85	./386/bin/auth/changeuser
> 	126	./386/bin/auth/auth.srv
> 	305	./386/bin/auth
> 	955	./386/bin
> 	1034	./386
> 	1	./adm/timezone/local
> 	1	./adm/timezone
> 	1	./adm/keys
> 	1	./adm/keys.who
> 	3	./adm
> 	0	./bin
> 	1	./rc/bin/cpurc (*)

Did you forget some comments here?

> 	0	./rc/bin/service
> 	1	./rc/bin/service.auth/il565
> 	1	./rc/bin/service.auth/il566
> 	1	./rc/bin/service.auth/tcp567
> 	3	./rc/bin/service.auth
> 	4	./rc/bin
> 	1	./rc/lib/rcmain
> 	1	./rc/lib
> 	5	./rc
> 	1	./lib/namespace
> 	1	./lib/ndb/local

+ /lib/ndb/common - I think that appeared in 3ed, but maybe you don't
need it.

> 	1	./lib/ndb/auth
> 	2	./lib/ndb
> 	3	./lib
> 	0	./mnt/keys/nashi
> 	0	./mnt/keys
> 	0	./mnt
> 	1046	.
>
Sounds excellent, I must give it a try.

++L


  reply	other threads:[~2002-12-02  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  8:05 YAMANASHI Takeshi
2002-12-02  8:33 ` Lucio De Re [this message]
2002-12-02 14:26 ` Ronald G. Minnich
  -- strict thread matches above, loose matches on Subject: below --
2002-12-03  5:06 Russ Cox
2002-12-03  2:31 Russ Cox
2002-12-03  4:52 ` Lucio De Re
2002-12-03  1:39 YAMANASHI Takeshi
2002-12-02 21:11 Russ Cox
2002-12-03  4:26 ` Lucio De Re
2002-12-02 13:18 Russ Cox
2002-12-02 13:29 ` Lucio De Re
2002-12-02  7:37 YAMANASHI Takeshi
2002-12-02  7:49 ` Lucio De Re
2002-12-02 14:25 ` Ronald G. Minnich

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=20021202103326.J22558@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).