similar to: [PATCH] New API: is_whole_device

The reimplemented APIs are: * list_devices * list_partitions * part_to_dev * part_to_partnum * is_whole_device --- daemon/Makefile.am | 2 + daemon/daemon.h | 3 - daemon/devsparts.c | 257 ---------------------------------------------- daemon/devsparts.ml | 109 ++++++++++++++++++++ daemon/devsparts.mli | 25 +++++ daemon/guestfsd.c | 75

On Sat, Sep 27, 2014 at 10:44:42AM +0000, VONDRA Alain wrote: > Hi, > Now with the new libguestfs-1.27.55-1.1 I have this new issue : > > libguestfs: trace: is_file = 0 > libguestfs: trace: is_file "/freedos/freedos.ico" > libguestfs: trace: is_file = 0 > libguestfs: trace: is_file "/boot/loader.rc" > libguestfs: trace: is_file = 0 > libguestfs:

Hi, Now with the new libguestfs-1.27.55-1.1 I have this new issue : libguestfs: trace: is_file = 0 libguestfs: trace: is_file "/freedos/freedos.ico" libguestfs: trace: is_file = 0 libguestfs: trace: is_file "/boot/loader.rc" libguestfs: trace: is_file = 0 libguestfs: trace: umount_all libguestfs: trace: umount_all = 0 libguestfs: trace: vfs_type "/dev/sda2"

Hi Julien > On some board, there is no alias to the UART. To avoid modification in > the device tree, dt-uart should also search device by path. > > To distinguish an alias from a path, dt-uart will check the first character. > If it''s a / then it''s path, otherwise it''s an alias. > > Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> >

Hi, I am trying to convert a Windows 2008 version, and I have libguestfs-winsupport-7.1-3.el7.x86_64 installed. Regards Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com]

On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. >> >> >> There's a lot of variation. Do you have a shell option >> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 >

>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. > > There's a lot of variation. Do you have a shell option > in your boot selections? None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 (firmware A16) seem have a built-in EFI shell option, but in all three cases I had success running the external EFI shell from

Hi Maxime, Quoting Maxime Accadia (2020-02-03 14:20:47) > Hi, > > We have a VM with several USB devices attached. Everything works well, > but sometimes, after a reboot of the host, some usb device get a > different bus/device number and that prevent the reboot of the VM : > ... > Any idea on how to handle this case ? > > We were thinking about using udev, but it

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

When CONFIG_KLIBC_ZLIB is not set, related functions shall not be called otherwise build failure is encountered: KLIBCLD usr/kinit/static/kinit usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed': /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_' /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined

Commit-ID: 534a04d85defc627b031906d27cd9d09a913adc4 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=534a04d85defc627b031906d27cd9d09a913adc4 Author: Christophe Leroy <christophe.leroy at c-s.fr> AuthorDate: Wed, 23 Jan 2019 06:16:01 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 24 Jan 2019 23:11:11 +0000 [klibc] fix build failure

Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger

https://bugs.freedesktop.org/show_bug.cgi?id=64645 Priority: medium Bug ID: 64645 Assignee: nouveau at lists.freedesktop.org Summary: Massive corruption QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: roucaries.bastien+bugs at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=27905 Summary: DVI monitor is blank - DVI detected as Display Port ? Product: xorg Version: 7.5 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

When CONFIG_KLIBC_ZLIB is not set, related functions shall not be called otherwise build failure is encountered: KLIBCLD usr/kinit/static/kinit usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed': /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_' /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined

OK there are problems. From https://sourceforge.net/p/edk2/mailman/message/31604654/ ""In current EDKII implementation, all the network servicebinding protocols for a NIC device are installed together on the NIC's device handle, so you can get all of them when you have chosen a special NIC handle."" Unfortunately there are PCs with UEFI implementations not following the

On Thu, Jul 2, 2015 at 9:58 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > OK there are problems. > > From > https://sourceforge.net/p/edk2/mailman/message/31604654/ > ""In current EDKII implementation, all the network servicebinding protocols for a > NIC device are installed together on the NIC's device handle, so you can get all > of them when you

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it

Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc

On Fri, Jul 3, 2015 at 11:05 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Lovely, the ServiceBindings are on a handle that resembles the NIC > while the Pxebc is IP-type specific. Looks like we should try to do a > ServiceBinding based on Pxebc but fall back to MAC-based searching, > saving all 3 handles, the image handle, Pxebc handle, and