Displaying 20 results from an estimated 300 matches similar to: "[klibc:master] Remove open_cloexec()"
2007 Aug 15
0
[git patch] fstype support + minor stuff
hello hpa,
rebased my branch, please pull latest
git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks
for the following shortlog
maximilian attems (6):
fstype: add squashfs v3 support
reiser4_fs.h: add attribute packed to reiser4_master_sb
fstype: add ext4 support
.gitignore: add subdir specific entries
usr/klibc/Kbuild: beautify klibc build
fstype:
2011 Feb 27
4
[PATCH] Add minimal mkstemp(3) implementation.
This uses time, ASLR and pid for randomisation. (Closes: #516774)
Signed-off-by: Thorsten Glaser <tg at mirbsd.org>
---
usr/include/stdlib.h | 2 +
usr/klibc/Kbuild | 2 +-
usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 96 insertions(+), 1 deletions(-)
create mode 100644 usr/klibc/mkstemp.c
diff --git a/usr/include/stdlib.h
2010 Apr 16
0
[PATCH] add minimal faccessat()
Implement as wrapper around sys_faccessat().
Latest dash started using it, also define AT_EACCESS:
usr/dash/bltin/test.c: In function ?test_file_access?:
usr/dash/bltin/test.c:490: error: too many arguments to function ?faccessat?
Signed-off-by: maximilian attems <max at stro.at>
---
usr/include/fcntl.h | 5 +++++
usr/include/unistd.h | 2 +-
usr/klibc/Kbuild | 2 +-
2011 Aug 29
0
[PATCH] Add mempcpy() as wrapper around memcpy
Newer udev versions asks for it:
libudev/libudev-util.c:168:12: warning: incompatible implicit declaration of built-in function 'mempcpy' [enabled by default]
Signed-off-by: maximilian attems <max at stro.at>
---
usr/include/string.h | 1 +
usr/klibc/Kbuild | 2 +-
usr/klibc/mempcpy.c | 7 +++++++
3 files changed, 9 insertions(+), 1 deletions(-)
create mode 100644
2012 Mar 07
1
libvirt for spice
Hi all:
I tried kvm on my ubuntu with the libvirt.xml file as follows:
<domain type='kvm'>
<name>instance-00000011</name>
<memory>2097152</memory>
<os>
<type>hvm</type>
<boot dev="hd" />
</os>
<features>
<acpi/>
2019 Jan 19
1
[ANNOUNCE] klibc 2.0.5
As a new co-maintainer of klibc, I have just released version 2.0.5.
The git repository remains at:
https://git.kernel.org/pub/scm/libs/klibc/klibc.git
A tarball will be available from the usual place later, but I'm not
currently able to upload there.
This new release fixes various build and run-time failures with current
versions of Linux, gcc, and binutils on mips, sparc and x86; and
2020 Jan 23
0
[Announce] Samba 4.10.13 Available for Download
========================================================
"It's better to be a lion for a
day than a sheep all your
life."
Elizabeth Kenny
========================================================
Release Announcements
---------------------
This is the latest stable release of the Samba 4.10 release series.
Changes since 4.10.12
----------------------
o Jeremy
2017 Jun 19
0
VM fails to start on boot-up
Hi,
I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up:
2017-06-19 07:15:18.491+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem
2016 Jan 06
0
[klibc:master] Add pread and pwrite 32bit syscall wrappers for parisc
Commit-ID: 75895304280f597f46551deb8b87c27ac18a013c
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=75895304280f597f46551deb8b87c27ac18a013c
Author: Helge Deller <deller at gmx.de>
AuthorDate: Wed, 6 Jan 2016 00:43:50 +0000
Committer: H. Peter Anvin <hpa at linux.intel.com>
CommitDate: Tue, 5 Jan 2016 17:45:50 -0800
[klibc] Add pread and pwrite 32bit syscall
2017 Jun 20
0
Re: VM fails to start on boot-up
On Tue, Jun 20, 2017 at 06:23:39AM +0000, Andy Gibbs wrote:
>Hi,
>
>
>I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up:
>
>
>2017-06-19 07:15:18.491+0000: starting up
2016 Feb 25
2
Building with LLVM_PARALLEL_XXX_JOBS
Hi,
I switched from "configure and make" to "cmake" build-system and
wanted to speedup my build.
In my build-script I use...
CMAKE_JOBS="1"
##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1))
JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS
-DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS"
[1] says in "LLVM-specific variables" section...
***
2007 Aug 24
2
[git patch] klibc bzero, mount fixes + random stuff
hello hpa,
please pull for the latest
git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks
with the following shortlog:
maximilian attems (9):
mount: add nodev, noexec and nosuid options
mount: add -n option
cpio: small cleanups
readlink: s/link/link_name/
kinit, mknod: s/(major|minor)/\1_num/
klibc: strcspn, strpbrk, strspn include string.h
2016 Jan 22
3
lld: ELF/COFF main() interface
I think I have an idea to cover your need and possibly other people's on
this thread. It provides the "main() as a library function" feature,
input/output files wouldn't go through disks nor file systems, and it
doesn't require any major design changes. Sounds too good?
That is, we can provide a function that takes command line parameters, do
fork, and call the linker's
2016 Jan 22
2
lld: ELF/COFF main() interface
If you want to link ELF object files, you are likely to be using a Unix
machine. I'm not trying to address all possible problems but suggesting a
practical solution.
On Fri, Jan 22, 2016 at 9:49 AM, Yaron Keren <yaron.keren at gmail.com> wrote:
> On Windows fork() is not available. If exec() is used instead, process
> creation time is several times slower than Linux. This may be
2000 Aug 07
1
shm_open (667) & locking_init(174), not 2.3.xx kernel
This weekend, we upgraded our server to Linux-Mandrake 7.1, which uses
a (slightly customized by Mandrake) 2.2.15 kernel. Since then, users are
unable to log in, and log.smb shows
locking/shmem_sysv_shm_open(667). Can't create or use use IPC area. Error
was File exists
locking/locking.c:locking_init(174). ERROR: Failed to initialise share
modes
There have been several messages posted about
2019 Sep 20
2
Building LLVM with LLVM with no dependence on GCC
Thus wrote David Demelier via llvm-dev:
> Also you will need to add more options to the components. See for example:
>
> LIBCXX_CXX_ABI=libcxxabi
> LIBCXX_USE_COMPILER_RT=On
> LIBCXXABI_USE_LLVM_UNWINDER=On
> LIBCXXABI_USE_COMPILER_RT=On
> LIBCXX_HAS_GCC_S_LIB=Off
> LIBUNWIND_USE_COMPILER_RT=On
>
> And as mentioned above
>
> CLANG_DEFAULT_CXX_STDLIB=libc++
2019 Sep 17
2
Building LLVM with LLVM with no dependence on GCC
Hi folks!
I'm trying to get rid of any dependency on libgcc*, but without success so
far. The following commands were executed on a freshliy installed and updated
Ubuntu 16.04 LTS:
=== snip ===
sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed
sudo mv /usr/local /usr/local.orig
git clone https://github.com/llvm/llvm-project.git
cd llvm-project; git
2009 Aug 01
3
write_freedesktop_mime_type_entry error writing file
Whenever I run any file I get the following:
> mark at mark-desktop:~/Desktop$ winecfg
> err:menubuilder:write_freedesktop_mime_type_entry error writing file /home/mark/.local/share/mime/packages/x-wine-extension-cpl.xml
> err:menubuilder:write_freedesktop_mime_type_entry error writing file /home/mark/.local/share/mime/packages/x-wine-extension-dib.xml
>
2023 Jan 26
0
[klibc:time64] time: Use clock_* system calls for time-of-day and sleep
Commit-ID: 8b44cc180f664532821211e8261534b0c9e6c01c
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8b44cc180f664532821211e8261534b0c9e6c01c
Author: Ben Hutchings <ben at decadent.org.uk>
AuthorDate: Sat, 14 Jan 2023 02:15:10 +0100
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sun, 15 Jan 2023 21:28:18 +0100
[klibc] time: Use clock_* system
2023 May 30
1
O_PATH, FreeBSD & acl_xx_fd
Urgh?
I modified the FreeBSD kernel to allow all_xx_fd() calls on O_PATH descriptors and that seems make vfs_zfsacl to work fine. Not 100% tested but I could atleast view and modify the ACL on some stuff from a Windows client via Samba that way.
I?m not sure I?ll be able to get them to implement this ?officially? though. Reading ACLs via an O_PATH-opened descriptor seems to be on the way of