search for: hopefull

Erik de Castro Lopo wrote: > Hopefull the final release candidate: > > http://mega-nerd.com/tmp/flac-1.3.3rc3.tar.xz > http://mega-nerd.com/tmp/flac-1.3.3rc3.tar.xz.asc I am assuming everyone was happy with that and that I can release a new version. Cheers, Erik -- --------------------------------------------------...

...rens wich language and version of PM i run? Does it help to copy dlls from a naitive NT system (which?). Is a wine snapshot more stable than daily builds? Please, any hits are greatly appreciated. I've heard rumors on people running Pagemaker rock stable under wine and that makes me curius and hopefull. TIA and regards, -- Fredrik Jonson

Hi all, I have a new pre-reelase (with a GPG signature) up here: http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz.asc This code is built from commit 10a28d482a8e48b806f61ab766992b2add98ec43 plus another commmit to change the version numbers which I will not be pushing to the public repo before the final release. Note that audio files encoded

...endif > > From maintenance effort point of view, it is minimized, > but not exactly what X86 pv_ops look like. > > Both approach will cause code size issue, but altB is > much worse in this area, while AltA need one additional BR clobber > register Pros: - single code - hopefull less maintenance cost compared to #1 Cons: - requires restriction on register usage. And we need to define its convension. When modifying ivt.S in the future after converting ivt.S, those convesion must be kept in mind. - suboptimal for paravirtualized case compared to #1 case > 3: Sin...

...endif > > From maintenance effort point of view, it is minimized, > but not exactly what X86 pv_ops look like. > > Both approach will cause code size issue, but altB is > much worse in this area, while AltA need one additional BR clobber > register Pros: - single code - hopefull less maintenance cost compared to #1 Cons: - requires restriction on register usage. And we need to define its convension. When modifying ivt.S in the future after converting ivt.S, those convesion must be kept in mind. - suboptimal for paravirtualized case compared to #1 case > 3: Sin...

...ff). I suspect this is likely a problem with DocMemory, but I don't know how to troubleshoot it. It runs off a FreeDOS bootable disk, and is a free download. I don't know how docmemory figures out where it shouldn't write, or what mechanisms exist to communicate that information, but hopefull people on this mailing list will 8-) As other points of interest: Windows 98 Gold and Windows ME boot disks fail, but Windows 98 SE boot disk images work (go figure). I've also managed to get Driveimager and Partition Magic to work by rolling the two doot disks into a single 2.88mb image usi...

How do I get my wine programs to access the internet through a proxy server? tom_a_sparks "It's a nerdy thing I like to do"

...n you help, or do you need more information from me. Please help, I am having a tough time with Linux and really want to like it. I own a NoNameClone type of computer which is basically giving me headache after headache. Still, being dumped in the deep end forces one to learn. Yours in profound hopefullness Toby Russell ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

On Mon, Dec 11, 2017 at 4:32 PM, Larry Martell <larry.martell at gmail.com> wrote: > On Mon, Dec 11, 2017 at 4:25 PM, Clint Dilks <clintd at scms.waikato.ac.nz> wrote: >> On Tue, Dec 12, 2017 at 10:09 AM, Larry Martell <larry.martell at gmail.com> >> wrote: >> >>> On Tue, Dec 5, 2017 at 8:22 AM, Pete Biggs <pete at biggs.org.uk> wrote:

Call drm_dev_unregister() first in bochs_pci_remove(). Hook bochs_unload() into the new .release callback, to make sure cleanup is done when all users are gone. Add ready bool to state struct and move bochs_hw_fini() call from bochs_unload() to bochs_pci_remove() to make sure hardware is not touched after bochs_pci_remove returns. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> ---

I asked about this ability a few weeks ago and the reply was basically that folks would be interested in seeing it happen. Well, the client insisted, so I've put together a hack that accomplishes it. The basic design requirement was that users would not see files/directories that they did not have at least read access to. This request came about because we were migrating from a Novell server,

I have moved onto the next phase and committed r229185, which makes VS2013 our minimum version. I will revert if issues arise, and we can rinse and repeat as necessary. Once it sticks for a bit I’ll update the docs too. -Chris > On Feb 9, 2015, at 10:07 AM, Chris Bieneman <beanz at apple.com> wrote: > > I agree with Aaron, this should not be a blocker because the workaround is

I''d like to be able to use a CD drive on the Dom0 to be accessible on the DomU systems. I do see some notes involving cdrom drives in the Xen 3.1 Enterprise notes, and in the VT notes, but not for systems without that on-board virtualization feature. And the syntax of the cdrom command options are documented nowhere in 3.0.3. I found completely useless notes at

Please excuse my ignorance as I''m a linux newbie. Basically I have a setup of an adsl ethernet modem (nated and then everything forwarded to the external ip of my Mandrake mnf firewall) connected to the mnf firewall which then connects to the lan. internet <--> adsl modem <--> mnf firewall <--> lan There''s only 2 nics in the mnf firewall so it''s a

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches...

...core for CPU bound guests. In essence the Xen hypervisor requires that information to work efficiently. There are some other ways of solving this problem as well that have been tossed around. I am enumerating them here, but I don''t have the full records of the disadvantages/advantges so hopefully some other people can chime in. - Parse the information in userspace. I am not really sure how that would work, but one thought was export in SysFS the Pxx/Cxx states and other ones (hand-waving here) and the libvirt/xend/xl toolstack would parse those as needed and push them up (say whe...