search for: frigged

RHEL 4's mkinitrd will fail to recognise that root is on LVM when running on a recent kernel/udev due to changes in naming. This patch detects LVM root for RHEL 4, and uses a dirty hack to frig mkinitrd if required. Fixes RHBZ#580461 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 21 +++++++++++++++++++-- 1 files changed, 19 insertions(+), 2 deletions(-) diff --git

Hi all, I know this issue has been discussed over and over again, but I'd like to voice my opinion while 3.0 is still fairly early-ish in the pipeline. So the issue is... API breakage. I understand and agree with the rationale why, namely faster development. But this principle should mean that for each breakage, the dude who makes the breakage should accompany the final commit (or something

On 13 July 2011 15:47, fly language <flylanguage at gmail.com> wrote: > I don't really buy the manpower argument. Updating the release doc when > breaking the frigging API is the Right Thing To Do and shouldn't take that > long, when done when the change is fresh in memory. I regularly make small API-breaking changes in the name of cleaning things up. Sorry! I'd be

I've been struggling with a test * install for a couple months now in a small office and am just about ready to give up on it. It's not that the system itself is a problem. I've got everything (attendant, voicemail, FXS extensions, Cisco and Polycom hard-IP phones, and 2 VOIP carriers) working except for the frigging analog FXO interfaces. These things are driving me completely mad.

> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote: > >> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: >> I was hoping to hear this from you :-) If I am to suggest how we can >> move forward I'd propose: >> - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling >> is supported). >> -

> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote: > >> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: >> I was hoping to hear this from you :-) If I am to suggest how we can >> move forward I'd propose: >> - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling >> is supported). >> -

On Jul 13, 2011, at 8:09 AM, Jay Foad wrote: > On 13 July 2011 15:47, fly language <flylanguage at gmail.com> wrote: >> I don't really buy the manpower argument. Updating the release doc when >> breaking the frigging API is the Right Thing To Do and shouldn't take that >> long, when done when the change is fresh in memory. > > I regularly make small

On Tue, Jun 23, 2020 at 12:51:03PM +0100, Andrew Cooper wrote: > There are cases which are definitely non-recoverable. > > For both ES and SNP, a malicious hypervisor can mess with the guest > physmap to make the the NMI, #VC and #DF stacks all alias. > > For ES, this had better result in the #DF handler deciding that crashing > is the way out, whereas for SNP, this had

I've got a Zhone 24 port FXS to configure. The configuration is beyond stupid. The people that designed this unit should be chased down and fired. I'm going around in circles frigging with all the options. Does anyone have a config file for this unit that I can use as a starting point? -bill wlloyd@slap.net

I just experienced something I'd rather not experience again. Using a SPA-841 SIP phone connected to our Asterisk server, someone dialed their own extension, answered, and then transferred the call using the phone's "XFER" soft key. This does a SIP REFER. Now, the phone has dropped out of the loop, and Asterisk has connected the two call legs into a loop, as far as I can tell.

We've recently discovered that libguestfs can't handle guests which use md. There are (at least) 2 reasons for this: Firstly, the appliance doesn't include mdadm. Without this, md devices aren't detected during the boot process. Simply adding mdadm to the appliance package list fixes this. Secondly, md devices referenced in fstab as, e.g. /dev/md0, aren't handled

On Tue, Aug 9, 2016 at 2:48 PM, Michael Adam <obnox at samba.org> wrote: > On 2016-08-09 at 11:58 -0300, francis picabia via samba wrote: > > On Tue, Aug 9, 2016 at 10:21 AM, Rowland Penny <rpenny at samba.org> wrote: > > > > > On Tue, 9 Aug 2016 09:37:13 -0300 > > > francis picabia <fpicabia at gmail.com> wrote: > > > > > >

Marcelo Tosatti <mtosatti at redhat.com> writes: > On Wed, Oct 03, 2018 at 11:22:58AM +0200, Vitaly Kuznetsov wrote: >> >> There is a very long history of different (hardware) issues Marcelo was >> fighting with and the current code is the survived Frankenstein. > > Right, the code has to handle different TSC modes. > >> E.g. it >> is very, very

Marcelo Tosatti <mtosatti at redhat.com> writes: > On Wed, Oct 03, 2018 at 11:22:58AM +0200, Vitaly Kuznetsov wrote: >> >> There is a very long history of different (hardware) issues Marcelo was >> fighting with and the current code is the survived Frankenstein. > > Right, the code has to handle different TSC modes. > >> E.g. it >> is very, very

Tony Brian Albers writes: > >> Hmm.. could this somehow be related to the fast startup thing in win10? > >> I mean, if fast startup is disabled, will that help? > >> > >> Just a thought. > > > > Fast startup does not get utilized for reboots, only for regular > > shutdowns. The actual option in Windows settings reads: > > > >

On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: > I was hoping to hear this from you :-) If I am to suggest how we can > move forward I'd propose: > - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling > is supported). > - Check if non-masterclock mode is still needed. E.g. HyperV's TSC page > clocksource is a single page for the whole

On Thu, Oct 04, 2018 at 07:00:45AM -0700, Andy Lutomirski wrote: > > On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote: > > > >> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: > >> I was hoping to hear this from you :-) If I am to suggest how we can > >> move forward I'd propose: > >> - Check if

http://bugzilla.mindrot.org/show_bug.cgi?id=1116 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #2 from djm at mindrot.org 2005-12-27 10:36

Hi people, i was experimenting with the pdbedit and i found the "user must change password at next logon". The thing i wan't able to make it work. I just can login and im not asked to change my password! How's that? The other thing.. i want to make my password expire after 30 days. I did this too, but it dosen't apply until i change my password one more time. I can make

I've been going in circles for a few weeks now with Realtime SIP. My extconfig.conf has: sipusers => mysql,dbname,ast_sip_users sippeers => mysql,dbname,ast_sip_users When I do a 'sip show peers' I see all my phones. When I do a 'sip show users' I only see a few of them. I can't work out why this is the case. They are also coming up with NAT as