From: "W. Trevor King" <wking@tremily.us>
To: Brian Dolbec <dolsen@gentoo.org>
Cc: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH] livecdfs-update.sh: Fix '/etc/sshd' check for sshd_config tweaks
Date: Sun, 03 Mar 2013 11:21:21 -0500 [thread overview]
Message-ID: <20130303162121.GA3437@odin.tremily.us> (raw)
In-Reply-To: <1362327217.25081.12.camel@big_daddy.dol-sen.ca>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Sun, Mar 03, 2013 at 08:13:37AM -0800, Brian Dolbec wrote:
> On Sun, 2013-03-03 at 08:01 -0500, W. Trevor King wrote:
> > sshd_config lives in /etc/ssh, not /etc/sshd. This typo has been
> > present since the block was introduced by c06264e (Initial import of
> > Catalyst 2.0.0, 2005-04-04), so it's obviously not a widely used
> > feature ;). It might be better to just remove the block entirely.
> > ---
> > …
> It would be better to move the hard coding out of the bash script and
> either into the config defaults or in this case (it's only used in the
> one target) added to the target stage py file. In that way the default
> value can be overwritten in the target spec file.
I think I'd rather remove this block entirely. Adding a separate
“enable root logins via SSH” option (and phase?) doesn't sound very
appealing. This sort of thing is better suited to a per-user
fsscript, especially if the in-catalyst support has always been
broken.
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-03 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 13:01 [gentoo-catalyst] [PATCH] livecdfs-update.sh: Fix '/etc/sshd' check for sshd_config tweaks W. Trevor King
2013-03-03 16:13 ` Brian Dolbec
2013-03-03 16:21 ` W. Trevor King [this message]
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=20130303162121.GA3437@odin.tremily.us \
--to=wking@tremily.us \
--cc=dolsen@gentoo.org \
--cc=gentoo-catalyst@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