search for: cappabl

I have an application that uses opengl. If no hardware opengl support is available it works fine (not a highend application). If opengl hw support is available on the mac platform it fails because of the not complete opengl cappabilities in xquartz. So: can I enforce the use of software opengl renderin instead of hardware rendering? If yes: how can i configure this?

On 08/02/2018 02:05 PM, Nir Soffer wrote: > When using file systems not supporting ZERO_RANGE (e.g. NFS 4.2) or > block device on kernel < 4.9, we used to call fallocate() for every > zero, fail with EOPNOTSUPP, and fallback to manual zeroing. When > trimming, we used to try unsupported fallocate() on every call. > > Change file handle to remember if punching holes or

On Thu, Aug 2, 2018 at 10:30 PM Eric Blake <eblake@redhat.com> wrote: > On 08/02/2018 02:05 PM, Nir Soffer wrote: > > When using file systems not supporting ZERO_RANGE (e.g. NFS 4.2) or > > block device on kernel < 4.9, we used to call fallocate() for every > > zero, fail with EOPNOTSUPP, and fallback to manual zeroing. When > > trimming, we used to try

...a kernel and an initrd with some drivers to boot from network (I have a lot of boot ROMS and their sucks) I tested on a lot of PCs using the Andrea Mazzoleni makebootfat script with syslinux 3.10. with no problems just one old PC I noticed that green led on the reader turns off, on every BIOS cappable to boot from USB it stay on. I want to buy a USB Pen drive, or another Card, like MS SD CF or what is better, to play with? I want to play with more than 8MB ;) Cheers, syslinux rocks. -- Gustavo Guillermo P?rez Compunauta uLinux www.ulinux.tk

Hi guys, I'm just about to shoot on my foot so I wanted to check if there is something else to blow my full leg actually ;-)) I have setup a working Samba 3 PDC controller with user authentication and roaming profiles. I want to lock down [*] the desktop on client machines (win xp) as I did with poledit (NTConfig.POL) on Win9x/WinNT4 machines. [*] Lock downs suck as : disabling msn

When using file systems not supporting ZERO_RANGE (e.g. NFS 4.2) or block device on kernel < 4.9, we used to call fallocate() for every zero, fail with EOPNOTSUPP, and fallback to manual zeroing. When trimming, we used to try unsupported fallocate() on every call. Change file handle to remember if punching holes or zeroing range are supported, and avoid unsupported calls. - can_trim changed

This is the second version to support efficient zero for block devices on older kernels (e.g. RHEL 7.5), and file systems that do not support yet FALLOC_FS_ZERO_RANGE (e.g. NFS 4.2). Changes since v1: - Split to smaller patches - Skip linux only includes on other systems - Skip code using BLKZEROOUT if the macro is not defined - Try BLKZEROOUT only if the offset and count are aligned to device

Hi, I found a link: http://xenbits.xensource.com/ext/xen-smartio.hg for Xen-IB source codes, but it did''t exist anymore. Are there other ways to get the Xen-IB source codes? Thanks. Regards, Yi-Man _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel