similar to: nfs4 support

On Thu, Oct 27, 2005 at 10:22:08PM -0700, H. Peter Anvin wrote: > > >So it looks like as long as dash can link with klibc then: OK, I've got it to build with klibc using klcc: $ size src/dash text data bss dec hex filename 63333 356 5940 69629 10ffd src/dash Unfortunately there seems to be something fishy in parameter expansion as it fails three

Hi, Any reason why the scsi headers and malloc.h are not installed as well for klibc 'make install' ? Thanks, -- Martin Schlemmer -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url :

Well, as of right now, both Linus and Andrew have rejected klibc in the kernel based on "it doesn't add anything new" (Linus) and "lack of interest" (Andrew). It seems that there is little hope of getting it into the kernel any time soon, unless there is additional features, and/or people start actively asking for it. I would appreciate hearing suggestions. The

It's probably difting slightly off the topic, but I know that there are some people listening here, who have a decent expertise. I'm trying to setup a file server (nfs4 at ad.domain) and mount from a client (hunin at ad.domain) using the user database and especially Kerberos provided by my AD (samba at ad.domain). It already works nicely, if I forget about krb5, i.e. idmapd is

Hi, On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote: > > The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. > This patch enables the ARCH=ppc64 make env var in debian/rules, in order > for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem

Hi Currently I am trying to get device-mapper and dmraid ported to compile against klibc. So far there was no real issues, as the only thing they used was fscanf and feof not available presently in klibc (but easy to work around). Other than that there are really no way to easily check for installed klibc's other than trying to mangle the output of klcc (from adjusted configure.in): -----

This patch make it possible to run udev with the latest klibc. One patch for the udev/Makefile to match the moved include/ dir. Another one for klibc's string fuctions, that are causing segfaults: strncpy.c: the while() gets n == -1 and memset() dies strncat.c: cat's only strlen(dest) count of chars from src to dest Thanks, Kay -------------- next part -------------- ===== Makefile

Hi, trying to build klibc 1.1.8 on x86 fails on my machine as follows: KLIBCCC dash/trap.o KLIBCCC dash/output.o dash/trap.c: In function 'trapcmd': dash/trap.c:94: warning: unused parameter 'argc' dash/trap.c:94: warning: unused parameter 'argv' dash/trap.c: In function 'decode_signal': dash/trap.c:398: error: 'SIGRTMIN' undeclared (first use in this

Hi, I have a port here of device-mapper to use klibc (still trying to get it upstream, but oh well). It used to work fine, but with latish klibc's I seem to have issues with fread(). Same code with glibc works just fine, but with klibc fread only seems to read the first two lines when it tries to get the major device number for misc and device-mapper from /proc/devices - then it keeps

On Tue, 2022-02-01 at 16:23 +0000, Thorsten Glaser wrote: > retitle 925358 qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, ?) > affects 925358 klibc-dev > thanks > > This still happens. (And retitling because I almost filed a bug > against klibc again? oops?) > > Look for ?mtest-external? (second occurrence) in: >

Hi everyone We're really struggling with nfs4 <--> windows acls. Scenario Samba4 share --> cifs --> win7. No problem Samba4 share --> nfs4 --> Linux. acls not inherited Neither is there inheritance vica versa. e.g. It is not possible to create files with group rw on a umask 0022 nfs4 share. nfs4_setfacl cannot override umask. Using POSIX or windows acls this works

I'm thinking it's time to release klibc-1.5; however, before releasing klibc-1.4.31 as klibc-1.5, I wanted to give a call to see if there is anything that either really needs to be done, or any bug reports I've missed... -hpa

Commit-ID: c3110b853f667d544717a9cdd6d96b1a2a7365bf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c3110b853f667d544717a9cdd6d96b1a2a7365bf Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Thu, 24 May 2012 07:43:31 -0700 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Thu, 24 May 2012 07:43:31 -0700 [klibc] sys/sysmacros.h: match glibc and

Hi all, I'm working on a klibc gcc wrapper, which of course needs to know where everything is installed to know where to pull stuff from. This means making a working "make install". My current thinking is to drop /usr/include/klibc, and instead put the whole tree under /usr/lib/klibc. In particular, I'd like to have: $(CROSS) is the cross-compilation prefix if any.

Hello, I have a CentOS 5.2 server that exports /home on the local network for 2 users by secure nfs4 with kerberos krb5p. The clients are a notebook and a desktop pc. The following error is always reproducible on all clients. If running the clients on high load, that means for example 5 firefox windows open and connected with www pages from the internet, installing the new qt development

Commit-ID: d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Author: Steve McIntyre <steve at einval.com> AuthorDate: Fri, 29 Jun 2012 18:13:34 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Sun, 1 Jul 2012 22:51:00 +0200 [klibc] arm/setjmp.S: fix longjmp

I've added this to our klibc copy in the udev tree to support the recently added Inotify. Thanks, Kay -------------- next part -------------- diff --git a/klibc/klibc/SYSCALLS.def b/klibc/klibc/SYSCALLS.def --- a/klibc/klibc/SYSCALLS.def +++ b/klibc/klibc/SYSCALLS.def @@ -114,6 +114,9 @@ int lchown32,lchown::lchown(const char * int getcwd::__getcwd(char *, size_t) <?> int utime(const

Hi everyone, I'm sorry if this has already been covered somewhere, but I've had a look and can't find it. Also if there is a better place for this question, please let me know. I know that the CTDB documentation states that only NFS2/3 are supported with CTDB but what I'd really like to know is why NFS4 won't work and if NFS4 support is planned for the future (timeline?).

All test machines are CentOS 5.5 (RHEL subscriptions purchased). We've had NFS3 storage working fine and decided to try NFS4. We can mount an NFS4 share on our KVM host, but the SELinux file context on the mountpoint directory is magically changed from virt_image_t to nfs_t. Restorecon refuses to change it back. Adding the mount option context=system_u:object_r:virt_image_t on either server

Hi everyone Version 4.0.0alpha18-GIT-bfc7481 openSUSE 12.1 Conventional nfs4 export works fine, but I'm having trouble kerberizing it for Samba 4 for my Samba 4 users. I've setup the nfs4 pseudo stuff like this: hh3:/ # mkdir /export hh3:/ # mkdir /export/home hh3:/ # mount --bind /home /export/home Here is /etc/exports: /export