search for: msg00034

...ary inflating the size by a factor of around 10000. (Clang 8 and older GCCs work "correctly") It would be possible to remove the "const" qualifier or use some compiler attribute trickery to get the previous behavior back. Thanks, Thomas [0] https://gcc.gnu.org/ml/gcc/2019-04/msg00034.html [1] https://gcc.gnu.org/ml/gcc/2019-04/msg00049.html

On Wed, Jan 28, 2015 at 03:43:19PM +0000, Richard W.M. Jones wrote: > On Wed, Jan 28, 2015 at 02:24:15PM +0800, Hu Tao wrote: > > On Wed, Dec 17, 2014 at 03:07:11PM +0800, Hu Tao wrote: > > > On Thu, Oct 30, 2014 at 10:46:52AM +0800, Hu Tao wrote: > > > > Hi Rich, > > > > > > > > This is rebase of v5 series. Meanwhile, I found a bug when

...gt; > What I can think of is adding a type extended_partition which is similar > to type partition, except that it has a member partitions of type > partition list to hold logical partitions. However this way is rejected once. See https://www.redhat.com/archives/libguestfs/2014-September/msg00034.html. I'm just having no idea what is the right way now. Looking for your suggestions on how to do it right! Regards, Hu

Folks, I have installed openssh-3.1.p1 and 3.4.p1 successfully int the past. When I tried to install 3.6.p1 it would not start. The init script created an error message to the affect the it could not find *ELF*. I the tried to reinstall 3.4.p1. It's startup said Error 255 .../sshd .. bailing. I then installed Solaris patch for /dev/random and reinstalled 3.4.p1... I got error .... sshd:

On 5/25/19 3:22 PM, Eric Blake wrote: > On 5/25/19 1:33 PM, Richard W.M. Jones wrote: >> I also made the code a bit more robust about closing the socket along >> error paths. >> --- >> generator/states-connect.c | 21 ++++++++++++++++++--- >> 1 file changed, 18 insertions(+), 3 deletions(-) >> > >> assert (!h->sock); >> assert

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

Hi there, I own a domestic lan with two computers, mine and my mother's one. Mine is called GREENDEMON and the other one is called BLUEDEMON and they both are configured to run on the REDLOCAL workgroup. I've Debian Woody running on GREENDEMON and Windows 98 running on BLUDEMON, with an attached Nec Silentwriter Superscript 610 printer. This printer is only compatible with Windows 9x

Hey, There has been some discussion about EFI and SecureBoot and such. Most of the time I get questions in the form of "How do I get Fedora 17 with Xen to do EFI", I am going to concentrate on Fedora, but I think this applies to other distros too. From my reading (I hadn't actually tried EFI yet), there are two ways to bootup a system: - Using grub2.efi. Grub2 does the EFI API

The "--disable-strip" configure option is required as the Solaris9-X86 linker/loader will not be able to load any of the executables and will display a "Killed" message. Similarly, 'ldd' will fail with a "file has insecure interpreter" error message. Performing a loader or ldd test from the OpenSSH installation directory on the compiled executables within the

I just upgraded to OpenSSH3.2.3p1 as it seemed that UsePrivilegeSeparation yes might help with my problem (connections forwarded are owned by root instead of the user I logged in as on the server), but instead, sshd barfs on receiving a connection. Without UsePrivilegeSeparation the server works fine. # strace -o /tmp/sshd.str sshd -d debug1: sshd version OpenSSH_3.2.3p1 debug1: private host

v1: https://www.redhat.com/archives/libguestfs/2018-September/msg00024.html v2: https://www.redhat.com/archives/libguestfs/2018-September/msg00034.html v3: - Fixed is_config_key zero length test. - Fixed is_config_key so it uses strspn and is not O(n^2). - Changed >= 1.7 to >= 1.8 in the documentation. Rich.