Re: wine64 (devel) and NetBSD 8.0
On Sat, Apr 18, 2020 at 04:29:07PM +0100, Sad Clouds wrote: > On Sat, 18 Apr 2020 16:51:12 +0200 > tlaro...@polynum.com wrote: > > > I would have liked to test piping the processes just invoking wine > > (for console programs) as a part of the pipe, not writing huge amount > > of temporary data being a huge win... > > If you can get Wine to work reliably on NetBSD this may work. > Otherwise, you could try other approaches: > > 1. Generating data on a Windows VM and piping/sending it across the > network to a NetBSD process, i.e. netcat. This avoids writing data to > some storage medium, but your VM environment may need fast networking > implementation, depending on how much data you generate. Perhaps a solution but as you write, this will depend on the efficiency of the networking implementation and if the cards are supported or if the emulated card is fast enough (I would have to look too if there is tricks to send data between VM and guest rapidly by sending it in some stage in the localhost network stack). > > 2. Do all processing on a Windows VM or physical host. You can compile > Posix code inside a Cygwin environment. There is even "Windows > subsystem for Linux" from Microsoft, but I've never used, so don't know > how well it works. If your code is mostly Posix and doesn't require > special BSD extensions, this could work for you. The code is POSIX, I always stick to it when there is no reason to deviate. I have made some experiments about this (mainly for kerTeX and Windows support). As usual with Microsoft, what used to work in this area (SUA) has been deprecated and replaced with installing a Linux distribution; and this and Cygwin are huge beasts and I'd much prefer the other way round since, if the Windows kernel since NT is now a good one, and if there is amazing compatibility work done in MS Windows, I can't like the user level stuff and even less the administration tools. I like NetBSD precisely for this: you can have easy access to what you want; you know where you have to look (/etc) and administration can be done with basic text tools and with the minimal amount of stuff and without beating around the bush. I never managed to like Pascal as a programming language; I never managed to like MS Windows for the user interface and the administration... Best, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: wine64 (devel) and NetBSD 8.0
Hello, On Sat, Apr 18, 2020 at 03:15:22PM +0100, Sad Clouds wrote: > On Fri, 17 Apr 2020 09:31:19 +0200 > tlaro...@polynum.com wrote: > > > Hello, > > > > Has anybody managed to have a working version of Wine on NetBSD 8.0 > > amd64? > > Never tried it, so not really answering your question, however wouldn't > it be easier to run a separate Windows VM for such binaries? This is for processing data and the Windows "imposed" binaries (because of libraries) are only the first part of the process: the bulk of the treatment is afterwards on a POSIX node (actually a NetBSD one). For sharing data with Windows (and MacOSX), a good work has been done, on NetBSD by Reinoud Zandijk, for UDF support. But this will impose to process data under Windows (in a VM) and, later, when this is done, to retrieve the data in a shared storage to process it afterwards. Since I have Windows nodes available (almost just for this), it is not a problem and a VM will just take processors time on a node (with NetBSD) that is already doing quite some work. I would have liked to test piping the processes just invoking wine (for console programs) as a part of the pipe, not writing huge amount of temporary data being a huge win... Best, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: wine64 (devel) and NetBSD 8.0
On Sat, 18 Apr 2020 16:51:12 +0200 tlaro...@polynum.com wrote: > I would have liked to test piping the processes just invoking wine > (for console programs) as a part of the pipe, not writing huge amount > of temporary data being a huge win... If you can get Wine to work reliably on NetBSD this may work. Otherwise, you could try other approaches: 1. Generating data on a Windows VM and piping/sending it across the network to a NetBSD process, i.e. netcat. This avoids writing data to some storage medium, but your VM environment may need fast networking implementation, depending on how much data you generate. 2. Do all processing on a Windows VM or physical host. You can compile Posix code inside a Cygwin environment. There is even "Windows subsystem for Linux" from Microsoft, but I've never used, so don't know how well it works. If your code is mostly Posix and doesn't require special BSD extensions, this could work for you.
Re: wine64 (devel) and NetBSD 8.0
On Fri, 17 Apr 2020 09:31:19 +0200 tlaro...@polynum.com wrote: > Hello, > > Has anybody managed to have a working version of Wine on NetBSD 8.0 > amd64? Never tried it, so not really answering your question, however wouldn't it be easier to run a separate Windows VM for such binaries?
Re: wine64 (devel) and NetBSD 8.0
Hello, On Sat, Apr 18, 2020 at 10:29:27AM +, r0ller wrote: > Hi, > > As far as I can recall, it will work only on 9.0 if the GSoC project got > merged. If not, then you shall try current. Here's the last report from the > GSoC project: > > http://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1 > Thank you for the pointer. I will try with current when I have a slot of time. Best regards, T. Laronde > Best regards, > r0ller > > Eredeti levél > Feladó: tlaro...@polynum.com (Link -> mailto:tlaro...@polynum.com) > Dátum: 2020 április 17 10:50:31 > Tárgy: wine64 (devel) and NetBSD 8.0 > Címzett: netbsd-users@NetBSD.org (Link -> mailto:netbsd-users@NetBSD.org) > > Hello, > > Has anybody managed to have a working version of Wine on NetBSD 8.0 > amd64? > The only one compilable with pkgsrc is the wine-dev leading to a wine64. > I have set the USER_LDT option in the kernel and tried the > sysctl -w vm.user_va0_disable=0 > but to no avail. > even trying, under X11 (native version), to run: > $ wine64 uninstaller > (uninstaller being an exe provided with Wine) it coredumps. > Trying a console only program (this is really for these ones I'm trying > Wine since some closed source libraries are provided only for > Windows---coordinates conversion for GIS programs) doesn't work. > Does it work only with 9.x? Only for x86 and not amd64 ? Is there a way > to track down? (there are messages about stack overflow so is > FORTIFY_SOURCE a problem too?) > Any hint will be greatly appreciated. > TIA, > -- > Thierry Laronde > http://www.kergis.com/ > http://www.sbfa.fr/ > Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: wine64 (devel) and NetBSD 8.0
Hi, As far as I can recall, it will work only on 9.0 if the GSoC project got merged. If not, then you shall try current. Here's the last report from the GSoC project: http://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1 Best regards, r0ller Eredeti levél Feladó: tlaro...@polynum.com (Link -> mailto:tlaro...@polynum.com) Dátum: 2020 április 17 10:50:31 Tárgy: wine64 (devel) and NetBSD 8.0 Címzett: netbsd-users@NetBSD.org (Link -> mailto:netbsd-users@NetBSD.org) Hello, Has anybody managed to have a working version of Wine on NetBSD 8.0 amd64? The only one compilable with pkgsrc is the wine-dev leading to a wine64. I have set the USER_LDT option in the kernel and tried the sysctl -w vm.user_va0_disable=0 but to no avail. even trying, under X11 (native version), to run: $ wine64 uninstaller (uninstaller being an exe provided with Wine) it coredumps. Trying a console only program (this is really for these ones I'm trying Wine since some closed source libraries are provided only for Windows---coordinates conversion for GIS programs) doesn't work. Does it work only with 9.x? Only for x86 and not amd64 ? Is there a way to track down? (there are messages about stack overflow so is FORTIFY_SOURCE a problem too?) Any hint will be greatly appreciated. TIA, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
