From: "Gorka guardiola" <paurea@gmail.com>
To: csant <csant@csant.info>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Best installation for a standalone desktop
Date: Thu, 3 Aug 2006 09:08:44 -0500 [thread overview]
Message-ID: <599f06db0608030708k59bca74ejbae0b8b9ffba4216@mail.gmail.com> (raw)
In-Reply-To: <op.tdo5yjqcd84skq@fiore.malebolge>
On 8/3/06, csant <csant@csant.info> wrote:
> Hola,
>
> I have been wondering what the best Plan 9 installation for a standalone
> desktop machine would be. Initially I had been thinking the default
> terminal installation was a good choice, but it seems to not require the
> user to actually log in - or is there a way on a standalone terminal to
> require authentication?
A terminal doesnt listen to services on the net, so authentication is
not an issue.
If what you want is simply to put a password to go to take a coffee, there is
a lock command, but I am not sure if it comes with the regular distribution.
>
> As far as I am understanding things, I need to configure the machine as a
> cpu and authentication server to use it as a standalone desktop machine
> where users need to authenticate to log in?
You need at least to set an authentication server if you want that
machine to listen to the network and authenticate users.
>
> What is the reccomended installation for a standalone desktop machine?
> /c
>
Depends on your needs/wants. For one user I'd say terminal. No remote
connection,
the owner booting the machine owns all of its resources. If you want
to login remotely
but are on a good network you may consider just using vnc to that machine though
it is not very secure and wastes your resources.
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2006-08-03 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:33 csant
2006-08-03 14:08 ` Gorka guardiola [this message]
2006-08-03 14:39 ` "Nils O. Selåsdal"
2006-08-03 16:25 ` Gorka guardiola
2006-08-03 20:50 ` [9fans] Plan9 on Microsoft Virtual PC 2004 Drew Hohmann
2006-08-03 22:53 ` John Floren
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=599f06db0608030708k59bca74ejbae0b8b9ffba4216@mail.gmail.com \
--to=paurea@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=csant@csant.info \
/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).