Re: Fail to start the openssh-server in live-config 2.0.12 - Too many arguments
On 11/25/2010 02:38 AM, Steven Shiau wrote:
> maybe it's useful to have
> a boot parameter to disable this sshkey-gen, e.g.
> live-config.nosshkeygen or nosshkeygen. Some people might want to have a
> fixed ssh host key.
there are two ideals to persue here, one is to have as less boot
parameters as possible to make sure live-config stays as simple as
possible (both from a maintenance and users point of view), the other is
to make sure live-config provides a framework with maximum fine granular
control on what gets configured and what not.
since obviously both can't be acchieved at the same time, the compromise
so far was that:
a) a new bootparameter gets added if it provides a shortcut
(e.g. 'noautologin' that disables both the tty and graphical
autologin, rather than specifying both)
b) if a certain config script has more than one functionality that
is reasonable to be able to disable on its own.
given that openssh-server currently doesn't have more than one function,
and, that there's no 'shorcut' here (nosshkeygen vs
noconfig=openssh-server; which is both just one parameter each), i think
we shouldn't add a destinctive parameter for it just yet.
what do you think about that? and unrelated to that, do you have any
other usefull thing that the openssh-server config script should do?
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist