similar to: problem when compiling samba-3.0.21c on power PC platform

Hello all, I am attempting to cross-compile Samba 3.0.24 for the ARM platform using on an Ubuntu Dapper box using arm-linux-gcc 3.4.0. I am using the following script to call configure: #!/bin/bash ac_cv_func_prctl=no linux_getgrouplist_ok=no ./configure --without-krb5 --without-ldap --without-ads --disable-cups --without-swat --prefix=/home/tropem/samba-build --host=arm-linux

Hi. I'm trying to compile 3.0.20b on my i686 host to run on a mipsel host. For this, I got a cross compile toolchain from <http://linkstationwiki.org/Projects/CrossToolchains>. The toolchain is installed at /usr/local/linkstation/gcc-3.3.5-glibc-2.3.2/mipsel-hdhlan-linux I ran configure with the help of a little wrapper script: version=gcc-3.4.4-glibc-2.3.5

On 3/15/23 18:25, Eric Blake wrote: > On Wed, Mar 15, 2023 at 12:01:57PM +0100, Laszlo Ersek wrote: >> Don't try to test async-signal-safety, only that >> NBD_INTERNAL_FORK_SAFE_ASSERT() works similarly to assert(): >> >> - it prints diagnostics to stderr, >> >> - it calls abort(). >> >> Some unfortunate gymnastics are necessary to avoid

On Thu, Mar 16, 2023 at 10:50:06AM +0100, Laszlo Ersek wrote: > On 3/15/23 18:25, Eric Blake wrote: > > On Wed, Mar 15, 2023 at 12:01:57PM +0100, Laszlo Ersek wrote: > >> Don't try to test async-signal-safety, only that > >> NBD_INTERNAL_FORK_SAFE_ASSERT() works similarly to assert(): > >> > >> - it prints diagnostics to stderr, > >> >

I was wondering if it might be possible for an rsync developer to look over the attached patch (tested on Linux 2.4.24 against the rsync-2.6.0 release), and offer suggestions on how I could improve it. Basically I want to use Linux finer grained capabilities to retain only CAP_SYS_CHROOT & CAP_DAC_READ_SEARCH when rsync drops root privs. That way I can take whole system backups as a (mostly)

Hi. Mac OS X has a PT_DENY_ATTACH argument to ptrace(2) which does what it says on the tin: PT_DENY_ATTACH This request is the other operation used by the traced process; it allows a process that is not currently being traced to deny future traces by its parent. All other arguments are ignored. If the process is currently being traced, it

Hello all, I''m looking for answers about a question that i did post on ZFS/UFS discuss... without success, now i''m here to see your points. Any tips? As you know, i''m making some "screencasts" about a few solaris features. That screencasts is one point of many tests that i''m making with solaris 10. Now, with some tests with dtrace, i have saw a

At the risk of beating a dead horse, I'd like to see the chroot security checks relaxed a bit. On newer Linux kernels, there's a prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0) that prevents privilege elevation (via setuid binaries, etc) for the caller and all of its descendants. That means that chroot(untrusted directory), prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0), setreuid(uid, uid), execve(a

I know it is just after a release, but I'm trying to see how the regression tests look on Tru64. I hadn't had a chance to really look at them before because I didn't have sudo installed on Tru64 (now I do). Anyway, for the 3.9p1 release, all of them run except for a couple of problems: - agent-ptrace fails; it looks like setgid isn't enough to kill tracing under Tru64, and I

Thanks Michael. Here is my (slightly corrected) version of the script, after I''ve done a bit of investment in the dtrace manual (always knew it''s powerful, but it''s more than that...). While it appears to run, and when I tried lowering the limit I started getting results, I''d appreciate it if you could please explain the actions attached to the last few probes

This patch adds the ability to kinit to allow the dropping of POSIX capabilities. kinit is modified by this change, such that it understands the new kernel command line "drop_capabilities=" that specifies a comma separated list of capability names that should be dropped before switching over to the next init in the boot strap (typically on the root disk). When processing capabilities

Am 31. J?nner 2017 16:36:35 MEZ schrieb Kristian Pedersen <kp at asom-net.dk>: >Hi list, > >We still did not manage to get quota-status working. >We're hoping someone can provide some feedback/ideas on how we may >investigate this issue further? >Is it likely to be a bug fixed in a newer version? > >Regards, > >Kristian > > [...] >> >>

Hi list, while preparing for the changed ACL/mode_t mapping semantics coming with onnv-147 [1], I discovered that in onnv-134 on my system ACLs are not inherited when aclmode is set to passthrough for the filesystem. This very much puzzles me. Example: $ uname -a SunOS os 5.11 snv_134 i86pc i386 i86pc $ pwd /Volumes/ACLs/dir1 $ zfs list | grep /Volumes rpool/Volumes 7,00G 39,7G 6,84G

Hi list, I am attempting to get quota-status service working, so I can deny email at the initial smtp dialog instead of generating bounces with lda. I can't seem to get quota-status to return quota_status_overquota, even when an email would put an account over quota. Quota in general works fine: Jan 22 06:39:23 mail dovecot: lda(xx at yy.dk): msgid=<25c5bdb20d58fc4f649f716a947613dc at

Dear developers, OpenSSH 4.3 (both p1 and p2) has a number of issues on IRIX 5.3 which were not present with 4.2p1: configure thinks that a number of header files are unusable. This is because in order to use them other headers such as sys/types.h must be included as well, and configure's test code does not do so. checking ia.h usability... no checking ia.h presence... yes configure:

I am wondering what is the interaction between SE Linux and the kernel "capabilities" in CentOS 5.1? I'm trying to open a raw socket and keep getting permission denied errors. I've tried using the lcap library to find that CAP_SETPCAP appears to be off in the kernel. For compliance reasons, I don't want to turn this on. I've also tried a hand-crafted SE Linux

Hello, I'm working on implementing hwasan instrumentation in GCC, and have just started discussing my current work-in-progress on the gcc-patches mailing list. (https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00387.html -- the email that Kostya saw and added people to). I've gotten about as basic a user-space implementation as possible (using the interceptor ABI) up and running, and would

https://bugzilla.mindrot.org/show_bug.cgi?id=3639 Bug ID: 3639 Summary: server thread aborts during client login after receiving SSH2_MSG_KEXINIT Product: Portable OpenSSH Version: 9.2p1 Hardware: ARM OS: Linux Status: NEW Severity: critical Priority: P5 Component:

With these patches, a majority of tests pass. The notable things which are still broken: - Because FreeBSD links /home -> /usr/home, $(pwd) gives a different result from realpath(2). Therefore some tests which implicitly rely on (eg) a plugin which calls nbdkit_realpath internally and then checking that path against $(pwd) fail. - Shebangs (#!) don't seem to work the same way

Could this be why I am getting a problem with the initial configure? checking for Active Directory and krb5 support... yes checking for ldap_initialize... (cached) no configure: error: Active Directory support requires ldap_initialize -------------- next part -------------- SAMBA VERSION: 3.2.0 LIBREPLACE_LOCATION_CHECKS: START checking build system type... sparc-sun-solaris2.9 checking