Hi,
On Mon, Jan 23, 2017 at 3:20 PM, Jerome Shidel wrote:
>
> I do agree that it makes little sense to automatically load SHARE with boot
> config option 2.
> After all, no other boot option starts SHARE. Also, only a couple situations
> require its use.
>
> Either of these options will most li
Hello again,
I do agree that it makes little sense to automatically load SHARE with boot
config option 2. After all, no other boot option starts SHARE. Also, only a
couple situations require its use.
Mostly, those would be running a multitasking system like Windows or exporting
network filesy
>are really multiple machines accessing the same files at the same
>time?
umm-yes as a matter of fact one upstairs and one downstairs.
On Mon, Jan 23, 2017 at 9:17 AM, Tom Ehlert wrote:
>
> > Why not use the CHOICE option to let the user decide?
>
> because 99,9 % of all user have no need fo
> Why not use the CHOICE option to let the user decide?
because 99,9 % of all user have no need for SHARE.
> I have a
> menu system which is designed to be used on a network and requires share to
> be loaded
are really multiple machines accessing the same files at the same
time?
> IMHO this
Why not use the CHOICE option to let the user decide? I have a menu system
which is designed to be used on a network and requires share to be loaded
IMHO this should be used of the FDNET option as well to allow users to copy
their specific packet driver to the /FDOS/NETWORK dir to avoid an error
Update:
The solution I found last night seems to work only for older OpenSSH servers.
For Ubuntu 16.04 LTS (with OpenSSH 7.2.) I also had to add:
HostKeyAlgorithms ssh-dss
to /etc/ssh/sshd_config because ssh-dss seems to have been deactivated by
default since OpenSSH 6.9.
But in the end SSH2D
