public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel
Date: Thu, 10 Dec 2009 20:42:17 +0000	[thread overview]
Message-ID: <200912102042.29454.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20091210142313.2d50e02e@digimed.co.uk>

[-- Attachment #1: Type: Text/Plain, Size: 1344 bytes --]

On Thursday 10 December 2009 14:23:13 Neil Bothwick wrote:
> On Thu, 10 Dec 2009 10:36:41 +0000, Alan Mackenzie wrote:
> > The machine I was installing on was a laptop with no available desk top
> > to place it on.  Therefore I decided to get SSH up and running as early
> > as possible so as to do the bulk of the installation from my nice comfy
> > desktop, monitor and keyboard.  Starting sshd from inside the chrooted
> > system was obviously the Right Thing.
> 
> Surely starting sshd from the live environment is The Right Thing if you
> want to get SSH running as soon as possible? That's how I've always done
> it.

Last time I read the docs (and that was some years ago) you would also launch 
screen, then detach/reattach the session after you ssh'ed into your LiveCD 
env.  In that sense rebooting the LiveCD is not something you would do more 
than once - unless there was something wrong with kernel you just rolled up.  
Hold on, I found it:

http://www.gentoo.org/doc/en/gentoo-x86-tipsntricks.xml#leave_terminal

However, I find what Alan Mackenzie says fairly sensible and something which 
is a rather simple amendment for the gentoo handbook.  The suggested change 
should not (I think) cause any side effects on a conventional install, so it 
should be accepted.

Just my 2c's.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-12-10 20:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 14:48 [gentoo-user] Problems setting up sshd on an installation kernel Alan Mackenzie
2009-12-06 16:28 ` Mick
2009-12-06 20:23   ` Alan Mackenzie
2009-12-06 22:22     ` Mick
2009-12-06 16:59 ` Florian Philipp
2009-12-06 18:56   ` Joshua Murphy
2009-12-06 20:45     ` Alan Mackenzie
2009-12-09 15:24     ` Alan Mackenzie
2009-12-09 15:43       ` Alan McKinnon
2009-12-09 16:46         ` Alan Mackenzie
2009-12-09 19:42           ` Alan McKinnon
2009-12-09 21:57             ` Stroller
2009-12-09 22:20               ` Alan McKinnon
2009-12-10 10:36               ` Alan Mackenzie
2009-12-10 14:23                 ` Neil Bothwick
2009-12-10 18:41                   ` William Hubbs
2009-12-10 20:42                   ` Mick [this message]
2009-12-10 15:27                 ` Willie Wong
2009-12-10 16:52                   ` Joshua Murphy
2009-12-09 22:35             ` Alan Mackenzie
2009-12-10  5:00               ` Stroller
2009-12-09 21:27           ` Stroller
2009-12-10  0:23             ` Dale
2009-12-06 20:17   ` Alan Mackenzie
2009-12-06 18:36 ` Walter Dnes
2009-12-06 21:31   ` Joshua Murphy
2009-12-06 21:49     ` Boy Hartsuiker

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=200912102042.29454.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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