#2 slan_setup unattended operation?
Apparently, in order to install SLan correctly, I need
to run a slan_setup app. I'm assuming I need to run
this, because the install of the binary absolutely
fails, without any supporting info, without this app
being run.
However, the 'installation' of the slan binary is being
done non-interactively, because I'm marshalling up the
files as part of a standard RPM build and packaging.
Therefore, we're now in this chicken and egg problem -
can't run the slan_setup because we're building, can't
build because we need to run slan_setup.
It's a nice tool, but can I skip it and rompt the user
to run it during the actual installation of the RPM?
It seems to suggest that it is a dependency that is
fulfilled by the host on installation, as it needs to
set host keys and whatnot, so I'm thinking I can
instruct the user to run it on, say, startup of the
server in /etc/rc.d/init.d/slan or so, if it detects a
missing config file.
As I'm already unable to use a make-install to install
the app (see subsequent bug report), I think that this
is a small alteration to make, this removal of
slan-config check and slan_setup execution. Agreed?
Thanks.
Logged In: YES
user_id=236673
Hello,
Before trying to make RPM packages out of SLAN, please try
to see if you can make it work for you at all. I'd be very
interested to learn that it works for someone other than me.
The make-install and slan_setup stuff is very very green.
Now that the virtual network doesn't form its own subnet,
the slan_setup part can probably be completely automated
with a "--accept-default" flag or something, the user no
longer has critically important decisions to make.
I will add this modification to the next release. There are
so many "issues" regarding the design and correct usage of
SLAN that fully automating its install (as a server) is
rather dangerous, 9 times out of 10 the user/administrator
installing it will be confused why it doesn't work as they
expected. The answer (in more complete versions) will
usually be "it's not intended to replace SSH" or something
like that.
As for --client-only builds, for users that want to connect
to an existing SLAN server, this surely can be fully
automated and easily rolled into an RPM. However, the only
SLAN server in the world at this time (to my knowledge) is
my own... so focus on this aspect has been low priority thus
far.