similar to: Bug#710522: Problem found

Displaying 20 results from an estimated 3000 matches similar to: "Bug#710522: Problem found"

2013 Sep 06
0
Bug#710522: marked as done (xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw)
Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem
2019 Dec 27
2
Disabling TLS 1.1 in Centos 7 cockpit
Thanks, Randal for the response. But it did not work. Here the results: #yum info cockpit Name : cockpit Arch : x86_64 Version : 195.1 Release : 1.el7.centos.0.1 Size : 51 k Repo : installed >From repo : extras Summary : Web Console for Linux servers URL : https://cockpit-project.org/ License : LGPLv2+ [root at cockpit ~]# cat
2019 Dec 27
0
Disabling TLS 1.1 in Centos 7 cockpit
Oops, excuse my typo Create /etc/systemd/system/cockpit.service.d/ssl.conf containing [Service] Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1 Then systemctl daemon-reload systemctl restart cockpit To verify that TLS 1.1 is disabled, echo test | openssl s_client -connect localhost:9090 -tls1_1 2>&1 | grep -e Protocol -e Cipher The expected result is:
2019 Dec 27
1
Disabling TLS 1.1 in Centos 7 cockpit
Sure did! I am even playing with different options (including NONE) and it seems to ignore the contents of ssl.conf I have tried Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA: Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA Environment=G_TLS_GNUTLS_PRIORITY=PFS
2019 Apr 12
1
Cockpit within httpd
Folks I'd love to use Cockpit, but I cannot open port 9090 for the access in all cases. I'd like to access it via my usual http port (such as 80) where I'm limited to a single HTTP port. I understand the security implications, and can deal with them later. My attempt was to allow the following URL to access the cockpit functionality: http://xxx.example.com/cockpit (not the
2015 Jun 15
0
Add on argument in seq()
Regardless of the value of the other arguments, the first element in the output of seq() is _always_ `from`. Hadley On Mon, Jun 15, 2015 at 9:56 AM, Millot Gael <Gael.Millot at curie.fr> wrote: > Thanks for your answer. > > The rational behind my proposal is why taking "from" when length.out=1, more than "to" or "NA", or " integer(0) " ?
2019 Dec 27
0
Disabling TLS 1.1 in Centos 7 cockpit
On Dec 27, 2019, at 16:28, Erick Perez - Quadrian Enterprises <eperez at quadrianweb.com> wrote: > > [root at cockpit ~]# cat /etc/systemd/system/cockpit.service.d/ssl.conf > Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1 > > [root at cockpit ~]# > [root at cockpit ~]# systemctl start cockpit > [root at cockpit ~]# systemctl status
2019 Mar 19
0
CESA-2019:0482 Moderate CentOS 7 cockpit Security Update
CentOS Errata and Security Advisory 2019:0482 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2019:0482 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 74a113078cc5e8cd7951623e396da24712f5c99cb5156bc58c91f35cefd0801f cockpit-173.2-1.el7.centos.x86_64.rpm
2020 Oct 30
0
Re: virsh rights voor normal users
On Thu, Oct 29, 2020 at 11:34:09PM +0100, Natxo Asenjo wrote: > On Thu, Oct 29, 2020 at 8:39 PM Michal Privoznik <mprivozn@redhat.com> > wrote: > > > On 10/29/20 4:47 PM, Natxo Asenjo wrote: > > > ah, yes. I try this: > > > > > > $ virsh -c qemu:///system > > > > > > But it then I get a prompt: > > > > > > ====
2015 Jun 15
1
Add on argument in seq()
Millot, On Mon, Jun 15, 2015 at 9:19 AM, Hadley Wickham <h.wickham at gmail.com> wrote: > Regardless of the value of the other arguments, the first element in > the output of seq() is _always_ `from`. > Indeed, as Hadley says, the output of seq must always start with* from*. It is a sequence starting at *from* and ending wherever the other arguments cause it to end. A sequence
2017 Oct 20
0
CEBA-2017:2961 CentOS 7 cockpit BugFix Update
CentOS Errata and Bugfix Advisory 2017:2961 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2961 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0b38a0e520340bae44134042c2500bf57b3c2a393bafaecbb26f65b2e0070858 cockpit-138-10.el7_4.x86_64.rpm
2015 Jun 15
2
Add on argument in seq()
Thanks for your answer. The rational behind my proposal is why taking "from" when length.out=1, more than "to" or "NA", or " integer(0) " ? This question seems basic. But is is not in certain situations, like when length.out = unpredictable positive integer. And I haven't found in ?seq() the particular behavior of this function when length.out = 1.
2020 Oct 29
2
Re: virsh rights voor normal users
On Thu, Oct 29, 2020 at 8:39 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 10/29/20 4:47 PM, Natxo Asenjo wrote: > > ah, yes. I try this: > > > > $ virsh -c qemu:///system > > > > But it then I get a prompt: > > > > ==== AUTHENTICATING FOR org.libvirt.unix.manage ============= > > System policy prevents management of local
2013 May 31
1
Bug#710522: xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw
Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [
2012 Oct 30
0
lapply and kernelUD (adehabitatHR package): Home Range kernel estimation for a list of individuals
Dear R experts, I'm using the adehabitatHR package in order to perform a kernel analysis and estimate the home range of my input data (GPS relocations of 42 individuals). I've done the analysis for one of the individuals and it worked perfectly (see code below). But now I'm trying to use a list and call the function lapply to do the same thing through all the 42 individuals (also see
2024 Sep 13
1
[PATCH v3 1/2] drm/panic: Add ABGR2101010 support
Add support for ABGR2101010, used by the nouveau driver. Signed-off-by: Jocelyn Falempe <jfalempe at redhat.com> --- drivers/gpu/drm/drm_panic.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/gpu/drm/drm_panic.c b/drivers/gpu/drm/drm_panic.c index 74412b7bf936..0a9ecc1380d2 100644 --- a/drivers/gpu/drm/drm_panic.c +++ b/drivers/gpu/drm/drm_panic.c @@ -209,6 +209,14
2024 Sep 13
1
[PATCH v3 1/2] drm/panic: Add ABGR2101010 support
Jocelyn Falempe <jfalempe at redhat.com> writes: Hello Jocelyn, > Add support for ABGR2101010, used by the nouveau driver. > > Signed-off-by: Jocelyn Falempe <jfalempe at redhat.com> > --- > drivers/gpu/drm/drm_panic.c | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/drivers/gpu/drm/drm_panic.c b/drivers/gpu/drm/drm_panic.c > index
2024 Sep 13
1
[PATCH v3 1/2] drm/panic: Add ABGR2101010 support
On 13/09/2024 09:22, Javier Martinez Canillas wrote: > Jocelyn Falempe <jfalempe at redhat.com> writes: > > Hello Jocelyn, > >> Add support for ABGR2101010, used by the nouveau driver. >> >> Signed-off-by: Jocelyn Falempe <jfalempe at redhat.com> >> --- >> drivers/gpu/drm/drm_panic.c | 10 ++++++++++ >> 1 file changed, 10
2019 Dec 27
3
Disabling TLS 1.1 in Centos 7 cockpit
Hi, I'm using cockpit in standard port 9090 in a Centos 7 system. Due to a suggestion from management, they want TLS 1.1 disabled system-wide in all Linux boxes and TLS 1.2 enabled. I have not found proper documentation on how to disable it for cockpit (version 195.1 ships with Centos 7) So far I have tried (https://cockpit-project.org/guide/149/https.html):
2015 Jun 15
0
Add on argument in seq()
Millot, I think the problem with that is that what you propose isn't a sequence starting at from in any meaningful way, and thus does not satisfy the contract of the seq function. Best, ~G On Jun 15, 2015 7:12 AM, "Millot Gael" <Gael.Millot at curie.fr> wrote: > Hi. > > I have a problem with the default behavior of seq(), which gives the > argument