[Mono-devel-list] Re: [Gtk-sharp-list] kernel support.
Carlos Perelló Marín
carlos at pemas.net
Wed Jun 18 13:53:47 EDT 2003
El mié, 18-06-2003 a las 11:29, Dag Wieers escribió:
> On 18 Jun 2003, Carlos [ISO-8859-1] Perelló Marín wrote:
> > El mar, 17-06-2003 a las 23:46, Dag Wieers escribió:
> > > Ok, now try to convince Red Hat, SuSE, TurboLinux, Mandrake, Lindows to
> > > fix their packages and release updates to their wine package now.
> > >
> > > And I'm sure you can overwrite what other packages do, but that's not a
> > > real clean solution and you may not have control what an upgrade will do.
> > >
> > I think that the solution does not change wine files, as you can read
> > with the attached file, it's only a modification inside binfmt-support
> I didn't say it changes wine files.
> Ok. Red Hat uses sysv files currently to make sure wine is started when a
> Windows binary is run. How would you add your wrapper to binfmt_misc ? As
> a sysv-script ? Would your script undo what the wine-package does ? Make
> sure it does work after an upgrade of a wine package ? If you have
> multiple entries, it's undetermined what exactly happens afaik (I've seen
> strange things here, while testing)
One note, this script/program is not mine.
I don't know how RedHat solve the "problem" I was just pointing the best
solution (for me). Perhaps you can just ask the RedHat's maintainer if
he/she will accept a patch before supposing that it will not work ever
with RedHat/Mandrake, etc...
> > > "It works" doesn't necessarily make it the best solution. A shell wrapper
> > > works too.
> > It works for all .net executables and the user does not need to know
> > that she needs a wrapper to execute a mono program.
> That's not why I said that. The user doesn't know it's starting a
> shell-wrapper either, so it's transparant to the user and works on _all_
> systems, not only those that have shipped the binary wrapper.
> BTW I made that comment because "a shell wrapper works too" but is
> clearly not a prefered solution either. It would be a temporary solution
> that works everywhere.
> > I think it's the best option :-P
> I think a binfmt_exe kernel module would be the best option. Transparant,
> can't be undone by binfmt_misc, and works just the same way as other files
> are made to work that can't take advantage of binfmt_misc.
If you look at the kernel development you will see that binfmt was moved
from a concrete binary submodules to a general support so user-space
applications could plug any support without the need of kernel
> Of course, it hasn't been written yet.
I doubt it will be ever written as a kernel module and if someone does
that, I doubt that it enters inside the official Linux Kernel
Btw, I don't know if *BSD or MacOS have something like binfmt, so
perhaps the "wrapper" you are talking is a better global solution...
> -- dag wieers, dag at wieers.com, http://dag.wieers.com/ --
> [Any errors in spelling, tact or fact are transmission errors]
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Carlos Perelló Marín
Debian GNU/Linux Sid (PowerPC)
Linux Registered User #121232
mailto:carlos at pemas.net || mailto:carlos at gnome.org
Valencia - Spain
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20030618/b03c3d0f/attachment.bin
More information about the Mono-devel-list