similar to: [klibc:master] losetup: Use LOOP_CTL_GET_FREE to find free device

hello hpa, please review this unsorted patch queue, as I wasn't sure about them they didn't land yet in todays pull request. thanks max git clone git://git.debian.org/users/maks/klibc.git test Thomas B?chler (1): klcc: compile shared by default jeremy buisson (1): [klibc] sparc64: fix bad 32 bits socket syscalls maximilian attems (1): [klibc] add losetup utils the

I have released version 2.0.8. This is available in the git repository at: https://git.kernel.org/pub/scm/libs/klibc/klibc.git and as a tarball at: https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/ New features: - Support for building with clang and lld, at least on x86 - Defined sysconf(), initially supporting only _SC_PAGE_SIZE - Defined clearerr() as extern - Defined stdio

Hi, I''ve been trying to boot from a RHEL4 install iso without much luck (the xen way). The Host is: RHEL 5.1 xen-3.0.3-41.el5 Here is my guest config: # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using

From: Karel Zak <kzak at redhat.com> ported to klibc losetup version from util-linux 108591d2b7860ca0b8d27d114bed1e504a31fa72, also add -h option. -maks Reported-by: Kamalesh Babulal <kamalesh at linux.vnet.ibm.com> Signed-off-by: Karel Zak <kzak at redhat.com> Signed-off-by: maximilian attems <max at stro.at> --- Other patches might be useful too, that one just

Hi, I have a legacy AES excrypted file system with a 256 key size. RHEL kernel is cryptoloop enabled but the losetup package is not. It needs additional patch. Does anybody have a patched losetup rpm I could use? Thank you! A. Georgiev

Commit-ID: 8443e57e5ba71e462e31e3b5aad9f7dd1b4736f5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8443e57e5ba71e462e31e3b5aad9f7dd1b4736f5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 00:39:53 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 00:44:32 +0000 [klibc] losetup: Fix char signedness

I have problem with smbmount and losetup working together. The data seems to be corrupted. Description: I have an NT4 server with a share. On my linux box i use smbmount to mount the share. I have created a big file on the share and use losetup to configure a loop-back device on which i try to create/use a filesystem. It seems to work at first with ext2fs, but after copying some files to the

Commit-ID: 209676c9a3d057c0eba48f633eb541b17c7d1eba Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=209676c9a3d057c0eba48f633eb541b17c7d1eba Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 00:33:37 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 19:55:37 +0000 [klibc] losetup: Delete fallbacks to

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

Hi There, I''ve installed xen 3 and xen-tools on my Debian etch server and all seems well, until I try to start a guest domain. debian:/home/xen# xm create /etc/xen/D4G3.cfg Using config file "/etc/xen/D4G3.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device