similar to: Re: udevinfo output broken

Commit-ID: 8c056cab6c8cce0b5dbc2c3141060f89a6ffc905 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8c056cab6c8cce0b5dbc2c3141060f89a6ffc905 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 25 Jul 2020 21:18:30 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 21:44:14 +0100 [klibc] stdio: Define all the

check_hotplug fails on one of my machines running ubunto 4.10 "Warty Warhog", due to misparsing the udevinfo version string. The problem is caused by an old version of sed that does not appreciate the regexp. This patch fixes it, and also works on debian unstable and SLES9SP2. Please apply... Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> Signed-Off-By: Orna Agmon

Processing commands for control at bugs.debian.org: > reassign 456330 xen-3 Bug#456330: use udevadm instead of udevinfo Warning: Unknown package 'xen-3.1' Bug reassigned from package `xen-3.1' to `xen-3'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

fwrite() takes a const void *p, but stdio declares just a void *p. Is there a reason for the difference? diff -p -purN klibc-0.186/include/stdio.h klibc-0.186.fwrite/include/stdio.h --- klibc-0.186/include/stdio.h 2004-07-28 23:09:59.000000000 +0200 +++ klibc-0.186.fwrite/include/stdio.h 2004-10-19 20:06:30.000000000 +0200 @@ -90,7 +90,7 @@ fread(void *__p, size_t __s, size_t __n, } extern

Commit-ID: 1aacafeba630135c2d8377887486f5e369b598f9 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=1aacafeba630135c2d8377887486f5e369b598f9 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 25 Jul 2020 18:14:41 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 21:43:01 +0100 [klibc] stdio: Add extern

flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

flight 10458 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10458/ Failures and problems with tests :-( Tests which did not succeed and are blocking: test-amd64-i386-xl-credit2 3 host-install(3) broken test-amd64-amd64-xl-sedf 3 host-install(3) broken test-amd64-amd64-xl-winxpsp3 3 host-install(3) broken

I have 2 video devices LML33 and PV155 $ lspci 06:00.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video cutting chipset (rev 02) 07:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 07:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 07:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture

On Wed, May 1, 2013 at 09:21:17AM -0700, Matt Wilson wrote: > On Mon, Apr 29, 2013 at 03:40:13PM +0200, Olaf Hering wrote: > > Ping > > Makes sense. > > Acked-by: Matt Wilson <msw@amazon.com> > > > On Wed, Jan 16, Olaf Hering wrote: > > > > > Ping > > > > > > On Wed, Dec 05, Olaf Hering wrote: > > > > > > >

dash didn't compile in DEBUG mode against klibc for all long time. Now it fails at link stage for not having setlinebuf(3). Fixes: usr/dash/show.o: In function `opentrace': show.c:(.text+0x86): undefined reference to `setlinebuf' Signed-off-by: maximilian attems <max at stro.at> --- the last open error, looks more like a klibc bug to me, will fix it

flight 12252 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12252/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12249 build-i386 4 xen-build fail REGR. vs. 12249 Tests which are failing intermittently

flight 9194 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/9194/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 7 debian-install fail REGR. vs. 9185 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1325788840 -3600 # Node ID 2f5a98692acde9e74d4009f50f83a8aa08296310 # Parent 3a22ed3ec534799b3cab55b0dc0a7380e701ecbe add feature flag to xenstore for XS_RESET_WATCHES Tell guest about availibilty of xenstoreds XS_RESET_WATCHES function. Guests can not issue this command unconditionally because some buggy toolstacks (such as

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1329300057 -3600 # Node ID 5a1cbd1af275e6ed1ef673852f8ac5247c09669c # Parent 5fb2aa61197db9676c11fbcf3ed24f30ac8fab9f man/xl.cfg: mention not yet documented options Add dummy entries for parsed but undocumented cfg file options to xl.cfg: for i in ` grep -Ew

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1350143934 -7200 # Node ID 5aa14d5afe6b1f35b23029ae90b7edb20367bbeb # Parent e0e1350dfe9b7a6cacb1378f75d8e6536d22eb2d hotplug/Linux: close lockfd after lock attempt When a HVM guest is shutdown some of the ''remove'' events can not claim the lock for some reason. Instead they try to grab the lock in a busy

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1333120147 -7200 # Node ID 34d9828185501f6e7ea2c3c2a397176a8e54ef0a # Parent 80653c8ea1d19dfe6130396bbc77f766eb9f9fab xenpaging: add error code to indicate iommem passthrough Similar to the existing ENODEV and EXDEV error codes, add EMDEV to indicate that iommu passthrough is not compatible with paging. All error codes are

Commit-ID: 0e725b1ec953aafa7cec75a22436319e945f93e1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0e725b1ec953aafa7cec75a22436319e945f93e1 Author: H. Peter Anvin <hpa at linux.intel.com> AuthorDate: Mon, 13 May 2013 11:36:38 -0700 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Mon, 13 May 2013 11:36:38 -0700 [klibc] Framework and trivial

flight 12043 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12043/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-xl-winxpsp3-vcpus1 7

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional