Re: fs customization (was: Re: [9fans] Terminals)

Re: fs customization (was: Re: [9fans] Terminals)

[forsyth]

: Remove /rc/bin/service/il566 and /rc/bin/service/tcp567. They proxy
: calls for the authentication services to the authentication server.
: On the authentication server itself, you'll want to run different
: services on those ports. To run them,

>>If I remove files from /rc/bin/service, they also disappear for
>>the non-auth cpu servers.

that's the way i run the systems at home and work.
i haven't noticed a need for the proxy listeners in either environment,
but it could be a part of the system that i haven't prodded yet.
perhaps the proxies are useful in a more elaborate network
configuration than i've used thus far.

Re: fs customization (was: Re: [9fans] Terminals)

[Russ Cox]

If you're going to run both, you'll want to remove the
proxy il566 and tcp567 as per the instructions.  They're
not necessary and are only to allow misconfiguration.
If you have everyone pointing at the right auth server,
they're not necessary.

Then you'll want to put the real il566 and tcp567 in
service.auth as documented and start those only
on the auth server:

switch($sysname){
case your-auth-server
	aux/listen -t /rc/bin/service.auth il
	aux/listen -t /rc/bin/service.auth tcp
case other-servers
	# don't do the above lines
}

aux/listen -d /rc/bin/service il
aux/listen -d /rc/bin/service tcp

Russ

Re: fs customization (was: Re: [9fans] Terminals)

[Russ Cox]

> To make the question more general: how do I customize the file
> server such that I can have multiple cpu servers booting from it
> (by which I mean: using its filesystem, the cpu kernels may still
> come from local disk or boot flop).

We use a switch on $sysname:

	switch($sysname){
	case thresher
		...

	case achille
		...

	}

etc.  An alternative is to use

	if(test -x /sys/lib/sysconfig/cpurc/$sysname)
		/sys/lib/sysconfig/cpurc/$sysname

which scales a bit better, makes it easier to let different
people administer different systems, but splits the config
info into multiple places making it harder to read.

To answer your specific questions, you'd probably want
to start the auth services only in the case for your auth
server; we let all the cpu servers share the same ssh
host key.

Russ

Re: fs customization (was: Re: [9fans] Terminals)

[Axel Belinfante]

Thanks for the general reply!

> To answer your specific questions, you'd probably want
> to start the auth services only in the case for your auth
> server.

To focus in: how does the following instruction for setting up
a standalone auth server translate to the fs situation?
If I remove files from /rc/bin/service, they also disappear for
the non-auth cpu servers.
Is the trick to add an /rc/bin/service.cpu containing the forwarding
services, together with listen lines for that directory?

: Remove /rc/bin/service/il566 and /rc/bin/service/tcp567. They proxy
: calls for the authentication services to the authentication server.
: On the authentication server itself, you'll want to run different
: services on those ports. To run them,
:
: cd /rc/bin/service.auth
: mv authsrv.il566 il566
: mv authsrv.tcp567 tcp567

I'm sorry to keep asking, but I want to make sure I understand.
Axel.

[9fans] Terminals

[Dave Iafrate - CSCI/F1997]

OK, we're trying to setup terminals.  Should he be booting off the
fileserver? Also, are the bootars supposed to be set to il?  And in the
termrc, it can contain multiple ip definitions for each terminal, right??

Thanks

Re: [9fans] Terminals

[Dan Cross]

In article <3AD65782.CEDDA44B@san.rr.com> you write:
>My core cpu server boots via a floppy into dhcp and gets its
>kernel from auth, but doesn't run dhcp itself by using a switch
>in cpurc.

Speaking of which....  Why doesn't the default cpurc do a switch
on $sysname so that one doesn't have to modify it after installation
to run the auth server services on the auth server, and the
``normal'' CPU server services on ``normal'' CPU servers (usually
by adding a switch ;-)?

	- Dan C.

fs customization (was: Re: [9fans] Terminals)

[Axel Belinfante]

Dan wrote:
> >My core cpu server boots via a floppy into dhcp and gets its
> >kernel from auth, but doesn't run dhcp itself by using a switch
> >in cpurc.
>
> Speaking of which....  Why doesn't the default cpurc do a switch
> on $sysname so that one doesn't have to modify it after installation
> to run the auth server services on the auth server, and the
> ``normal'' CPU server services on ``normal'' CPU servers (usually
> by adding a switch ;-)?

Speaking of which... When I set up my fileserver, to boot the cpu/auth
server from it (kernel from local disk, filesystem from fileserver),
I made the same changes to /rc/bin/service(.auth) as I did when I
set up the auth server on its local disk. Is that correct?
Or do people set this up differently?
(The changes I made will probably cause a second 'ordinary' cpu
 server to fail, I assume)

On a related note: what about the ssh host key: if I use the fs,
all cpu servers share the same key? Or is this part of the same
switch?

To make the question more general: how do I customize the file
server such that I can have multiple cpu servers booting from it
(by which I mean: using its filesystem, the cpu kernels may still
come from local disk or boot flop).
Is there a document describing this that I missed?

Axel.