search for: frig

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 a/lib/Sys/VirtV2V/GuestOS/RedHat.pm b/lib/Sys/VirtV2V/GuestOS/RedHat.pm index 101a64b..74b9de1 100644 --- a/lib/Sys/VirtV2V/Gue...

...and no stable dot release scheme, things are getting rather frustrating. I'm thinkering about using the more stable C wrapper, but that's pretty lame given the fact that my compiler is written in C++. 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. This is my only gripe with llvm, but it's a pretty big one. The lack of stable releases is a slightly lesser one, but in that case, I totally buy the manpower argument. Thanks for...

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 happy to update the release notes if folks reckon this is the right thing to do. Wo...

...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. Since this is obvioiusly a deal breaker, I'm looking for any more suggestions on how I might fet these things working. The hitch is pretty clearly the quality of the lines I have from BellSouth but I can't get thim to...

...non-masterclock mode is still needed. E.g. HyperV's TSC page >> clocksource is a single page for the whole VM, not a per-cpu thing. Can >> we think that all the buggy hardware is already gone? > > No, and it is not the hardware you have to worry about (mostly), it is > the frigging PoS firmware people put on it. > > Ever since Nehalem TSC is stable (unless you get to >4 socket systems, > after which it still can be, but bets are off). But even relatively > recent systems fail the TSC sync test because firmware messes it up by > writing to either MSR_TSC...

...non-masterclock mode is still needed. E.g. HyperV's TSC page >> clocksource is a single page for the whole VM, not a per-cpu thing. Can >> we think that all the buggy hardware is already gone? > > No, and it is not the hardware you have to worry about (mostly), it is > the frigging PoS firmware people put on it. > > Ever since Nehalem TSC is stable (unless you get to >4 socket systems, > after which it still can be, but bets are off). But even relatively > recent systems fail the TSC sync test because firmware messes it up by > writing to either MSR_TSC...

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 API-breaking changes in the name of cleaning > things up. Sorry! I'd be happy to update the release notes if folks > reckon this is t...

...whereas for SNP, this had better escalate to Shutdown. > Crashing out hard if the hypervisor is misbehaving is acceptable. Then I'm thinking the only sensible option is to crash hard for any SNP #VC from kernel mode. Sadly that doesn't help with #VC needing to be IST :-( IST is such a frigging nightmare.

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.

...t. I don't currently think we'll need any new apis for this. I'm not convinced we need apis for creating and managing md devices, for example. We could do with a test for inspection of a guest which uses md devices, which would obviously require creating that guest. However, we can frig that for the test using debug sh "mdadm ...". Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

...for people who think the range beginning at 1000 was some magic solution). Look, you get into your car, and do you look at an RPM value and gear indicator, compute the tire size P215R16 and figure out the speed? No, there is a calibrated instrument for it. Well, what is sitting in front of us, a frigging computer! Why can't samba/winbind look at nsswitch, determine there is nothing like NIS and LDAP, lookup the UID values in /etc/passwd, and make ranges on the fly? The end user does not care what their values are - they only want "Map Network Drive" to work and get something don...

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

...retty quickly, after a reboot. Which kind of makes sense, actually, now that I'm aware of the fast startup "feature", and I find it absolutely hillarious. See: if Windows was really hibernating, then after it boots up the dumb thing obviously wants to immediately kick off every frigging last scheduled task it has, since it probably came due during the time the whole bloody thing was off. I always had a laugh looking at virt-manager showing the guest pegging the CPU at 100% for 10-30 minutes after I start up the VM. That's Windows for you. Well, now, with the fast s...

...rted). > - Check if non-masterclock mode is still needed. E.g. HyperV's TSC page > clocksource is a single page for the whole VM, not a per-cpu thing. Can > we think that all the buggy hardware is already gone? No, and it is not the hardware you have to worry about (mostly), it is the frigging PoS firmware people put on it. Ever since Nehalem TSC is stable (unless you get to >4 socket systems, after which it still can be, but bets are off). But even relatively recent systems fail the TSC sync test because firmware messes it up by writing to either MSR_TSC or MSR_TSC_ADJUST. But...

...till needed. E.g. HyperV's TSC page > >> clocksource is a single page for the whole VM, not a per-cpu thing. Can > >> we think that all the buggy hardware is already gone? > > > > No, and it is not the hardware you have to worry about (mostly), it is > > the frigging PoS firmware people put on it. > > > > Ever since Nehalem TSC is stable (unless you get to >4 socket systems, > > after which it still can be, but bets are off). But even relatively > > recent systems fail the TSC sync test because firmware messes it up by > >...

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