Re: [Freedos-user] freedo
Hi, On Mon, Jan 23, 2017 at 3:20 PM, Jerome Shidelwrote: > > 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 likely require some hand tuning of the > system configuration. > So, leaving it in there but commented out is probably the best solution. A > user will see it with > customizing their configuration and enable it manually. > > I don't think that going down the CHOICE route is how this should be handled. > > I think it is much easier and less annoying to just hand edit the > configuration afterwards. You forgot about this: http://help.fdos.org/en/hhstndrd/cnfigsys/question.htm -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
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 filesystems. Either of these options will most likely require some hand tuning of the system configuration. So, leaving it in there but commented out is probably the best solution. A user will see it with customizing their configuration and enable it manually. I don't think that going down the CHOICE route is how this should be handled. Would you want to encounter the following when performing an installation? Do you want to load DOSLFN? yes/no If no, Do you want to load LFNDOS? Do you want to load FreeDOS High, UMB? How many files do you want to support opening at once? Do you want to enable hard drive caching? Do you want to enable floppy caching? Do you want .. Do you want to load SHARE? Do you want ... :-) I think it is much easier and less annoying to just hand edit the configuration afterwards. Jerome -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
>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 Ehlertwrote: > > > 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 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 msg after initial installation.. > > Tom > > > On Sat, Jan 21, 2017 at 6:21 PM, Jerome Shidel > wrote: > > > Tom, > > >> what purpose is SHARE supposed to have? > >> SHARE is useful when the machine is running as a server, or with > >> windows (or any other multitasking OS). > >> > >> don't install this. > > > You are probably correct that it should load it by default. > > > I rem’d it out for future releases. > > > Jerome > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > > > Mit freundlichen Grüßen/Kind regards > Tom Ehlert > +49-241-79886 > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
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 msg after initial installation.. On Sat, Jan 21, 2017 at 6:21 PM, Jerome Shidelwrote: > Tom, > > > what purpose is SHARE supposed to have? > > SHARE is useful when the machine is running as a server, or with > > windows (or any other multitasking OS). > > > > don't install this. > > You are probably correct that it should load it by default. > > I rem’d it out for future releases. > > Jerome > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SSH2DOS - no connection with recent servers
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 SSH2DOS was still not able to connect to OpenSSH 7.2. Perhaps someone has an idea? At the moment SSH2DOS can only be used to connect to older servers, running f.i. Debian Wheezy (OpenSSH 6.0) or Jessie (OpenSSH 6.7). So soon there will be no functioning SSH client anymore for FreeDOS. :-( Here are the messages: SSH2DOS error message is: C:\> ssh2d386 username 192.168.1.131 SSH2DOS v0.2.1. 386+ version Expected KEX_DH_GEX_GROUP DH key exchange failed Remote host closed connection Socket write error. File: transprt.c, line:698 Connection closed by peer On the server, Ubuntu 16.04 LTS (with OpenSSH 7.2.), /var/log/auth.log says: Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: kex protocol error: type 30 seq 1 [preauth] Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: Received disconnect from 192.168.1.110 port 564:3: Expected KEX_DH_GEX_GROUP [preauth] Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: Disconnected from 192.168.1.110 port 564 [preauth] C:\> ssh2d386 -d username 192.168.1.131 wrote the following output in C:\SSH2DOS\DEBUG.PKT: --- RECEIVED packet: 14 BE 6D 01 48 D3 E5 EB 2A C1 81 DE E7 31 AB DB B2 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E 67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64 73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00 00 ..m.H...*1.. "diffie-hell man-group-exchan ge-sha1ssh-d ssaes128-cbc aes128-cbc.. ..umac-64-etm@op enssh.com,umac-1 28-etm@openssh.c om,hmac-sha2-256 -e...@openssh.com ,hmac-sha2-512-e t...@openssh.com,h mac-sha1-etm@ope nssh.com,umac-64 @openssh.com,uma c-...@openssh.co m,hmac-sha2-256, hmac-sha2-512,hm ac-sha1umac- 64-etm@openssh.c om,umac-128-etm@ openssh.com,hmac -sha2-256-etm@op enssh.com,hmac-s ha2-512-etm@open ssh.com,hmac-sha 1-...@openssh.co m,umac-64@openss h.com,umac-128@o penssh.com,hmac- sha2-256,hmac-sh a2-512,hmac-sha1 none,zlib@op enssh.comnon e,zlib@openssh.c om. SENT packet: 14 25 81 88 A7 CD 90 15 0E 5E 3B 7C B4 0B 1E 9D CA 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E 67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64 73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00 00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65 2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C 69 62 00 00 00 00 00 00 00 00 00 00 00 00 00 .%...^;| "diffie-hell man-group-exchan ge-sha1ssh-d ssaes128-cbc aes128-cbc.. ..hmac-sha1h mac-sha1none ,zlibnone,zl ib. SENT packet: 1E 00 00 04 00 . RECEIVED packet: 03 00 00 00 01 . SENT packet: 03 00 00 00 02 . SENT packet: 01 00 00 00 03 00 00 00 19 45 78 70 65 63 74 65 64 20 4B 45 58 5F 44 48 5F 47 45 58 5F 47 52 4F 55 50 00 00 00 00 .Expecte d KEX_DH_GEX_GRO UP SENT packet: 62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71 01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 bpty-req .xterm...P..