9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] remote access to console of auth/console server?
Date: Thu,  6 Jun 2002 12:57:48 +0200	[thread overview]
Message-ID: <200206061057.g56AvnK26670@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Sun, 02 Jun 2002 00:18:29 +0200." <200206012218.g51MITW09894@zamenhof.cs.utwente.nl>

To answer some of my own questions:
 - the console= line in plan9.ini just _adds_ console access via COM[12],
   instead of _replacing_ the normal access via keyboard/monitor
   (so no need for old terminal to watch/influence the boot process)
 - the loop from one serial port (specified in console= line in plan9.ini)
   to another (specified in /lib/ndb/consoledb) works, but 'costs'
   two serial ports.

New questions:
 - would it be possible to replace the fysical loop by some
   'loopback' code (that makes the console availabe via a 'virtual'
   serial port)?
 - would that make sense?   rephrased:
 - do I really need/want remote console access to the auth server, or can
   'every' administration task be done via normal remote login?
   How is this done at bell labs (where, as I understand, the auth server
   doubles as console server)?
   One advantage of access via consolefs rather than via normal remote
   login seems to be that clog can be used to log 'everything'.

Thanks,
Axel.



  reply	other threads:[~2002-06-06 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 22:18 [9fans] access to console of consolefs server? Axel Belinfante
2002-06-06 10:57 ` Axel Belinfante [this message]
2002-06-27 17:53   ` [9fans] remote access to console of auth/console server? Axel Belinfante

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=200206061057.g56AvnK26670@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).