Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
On 02/17/2016 06:16 PM, Samuli Seppänen wrote: > I don't think there are many (any?) 32-bit Windows operating systems > being bundled with new computers. The reason why Microsoft backpedaled > on dropping 32-bit support in Windows 10 seemed to be their free upgrade > program: they wanted the 32-bit operating systems to be upgradeable too. There are a lot of tablets on Intel Atom with 32 bit Windows 10. signature.asc Description: OpenPGP digital signature
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
Hi, On Wed, Feb 17, 2016 at 04:31:09PM +0200, Samuli Seppänen wrote: > Yes, that is big part of the appeal. Plus the results of the > installations would be more consistent: > > - Registry keys would always be in the main registry > - OpenVPN always under "C:\Program Files\OpenVPN" (unless customized) I do like this :-) The installer would need some way to deal with "legacy" prior setups, namely "the new and magic 32/64 bit installer hits a 64-bit system that has a 32-bit OpenVPN on it". But that's not truly different than today (64bit installer running on a system that has the 32bit version pre- installed), so we need to fix this some way or the other anyway... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de signature.asc Description: PGP signature
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
Hi, In 4 years I have not seen a single complaint on the forum nor can remember a single complaint on the mailing list referring to downloading the wrong bitness installer. Or that the download page is misleading in this way. This is actually rather surprising. That said, I can't recall any incidents, either. Perhaps this is an exception to the rule "people don't read what is written on a webpage" :). On top of that, as 32b it phased out by retail, it is likely that anybody who still requires 32b will have the intelligence to follow a separate link to 32b installers. I don't think there are many (any?) 32-bit Windows operating systems being bundled with new computers. The reason why Microsoft backpedaled on dropping 32-bit support in Windows 10 seemed to be their free upgrade program: they wanted the 32-bit operating systems to be upgradeable too. I suggest that for OpenVPN 2.4* releases we emphasize the 64-bit installer links. For example: Source tarball (gzip) openvpn-2.4.0.tar.gz GPG sig Source tarball (xz)openvpn-2.4.0.tar.xz GPG sig Source zip openvpn-2.4.0.zip GPG sig Installer (64-bit) openvpn-install-2.4.0-I601-x64_64.exe GPG sig A 32-bit installer is available (<- link). You should only use it on 32-bit systems. ... followed by the rest of the release notes/comments... -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
- Original Message - From: "Arne Schwabe" To: ; ; "Samuli Seppänen" Sent: Wednesday, February 17, 2016 1:44 PM Subject: Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers Am 17.02.16 um 14:37 schrieb debbie...@gmail.com: I would say option 3 is better .. doubling the installer size for 32bit seems like bloat! to me plus .. why do all that extra work for something that will have diminishing value ? A combined installer will need less support because people do not download a wrong installer. In 4 years I have not seen a single complaint on the forum nor can remember a single complaint on the mailing list referring to downloading the wrong bitness installer. Or that the download page is misleading in this way. On top of that, as 32b it phased out by retail, it is likely that anybody who still requires 32b will have the intelligence to follow a separate link to 32b installers. regards
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
Am 17.02.16 um 14:37 schrieb debbie...@gmail.com: I would say option 3 is better .. doubling the installer size for 32bit seems like bloat! to me plus .. why do all that extra work for something that will have diminishing value ? A combined installer will need less support because people do not download a wrong installer. Yes, that is big part of the appeal. Plus the results of the installations would be more consistent: - Registry keys would always be in the main registry - OpenVPN always under "C:\Program Files\OpenVPN" (unless customized) I would love 32-bit Windows to go away, but that will probably take at least a decade. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
Am 17.02.16 um 14:37 schrieb debbie...@gmail.com: > I would say option 3 is better .. > doubling the installer size for 32bit seems like bloat! to me > plus .. why do all that extra work for something that will have > diminishing value ? > A combined installer will need less support because people do not download a wrong installer. Arne
Re: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers
I would say option 3 is better .. doubling the installer size for 32bit seems like bloat! to me plus .. why do all that extra work for something that will have diminishing value ? my2c - Original Message - From: "Samuli Seppänen" To: Sent: Tuesday, February 16, 2016 2:01 PM Subject: [Openvpn-devel] Handling bitness (32/64) for OpenVPN Windowsinstallers Hi, We currently produce four installers per OpenVPN 2.3.x release: - 64-bit for Windows Vista+ - 32-bit for Windows vista+ - 64-bit for Windows XP - 32-bit for Windows XP The latter two will be dropped in OpenVPN 2.4 alpha releases, which are due fairly soon[*]. That leaves us with one 32-bit and one 64-bit installer. While that is not too bad, things could be simpler. Here are a few suggestions: 1) Combine 32-bit and 64-bit installers into one Is there a use-case for installing 32-bit OpenVPN on a 64-bit system? If not, we could combine both 32-bit and 64-bit binaries into a single installers and, at install time, select the correct ones to install. This would increase installer size from ~1.8MB to ~3.3MB. 2) Drop the 64-bit installer altogether This option was brought forth earlier, and while it felt to me like a step back, I could not point my finger at any concrete issues. If you know of any pros or cons, please speak up. 3) Hide the 32-bit installers better, but keep them available Currently both 32-bit and 64-bit installers are displayed side-by-side on the download page. Because of this it is difficult to tell how many people really _need_ the 32-bit version, and how many just download it out of habit, or by mistake. Making the download link for 32-bit installer(s) less prominent would probably give us the answer. If complaints started coming in we could backpedal real quickly. Unfortunately 32-bit Windows systems are not going away anytime soon, so "64-bit only" is not an option[**]. 4) Maintain the status quo Do not change anything. --- Let me know which of the options seems most reasonable. It would be good to reach some consensus before OpenVPN 2.4-alpha1 is released. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock [*] All the major functionality is in Git "master" or is being actively reviewed. [**] E.g. <http://news.softpedia.com/news/Microsoft-Explains-Why-Windows-10-32-Bit-Is-Still-Needed-469563.shtml> -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
