similar to: [patch] fix defintion of struct statfs64

From: Sjoerd Simons <sjoerd@spring.luon.net> It seems that klibc uses __sparc64__ to determine if it's compiled in 64 bit mode on sparc, unfortunatly gcc doesn't define __sparc64__ :) It does define __arch64__ though. Signed-off-by: maximilian attems <maks@sternwelten.at> --- klibc-1.2.2.orig/include/sys/vfs.h 2006-02-15 18:32:10.000000000 +0100 +++

It's checked in, it seems to work, it didn't bloat the system significantly, but it makes life a lot easier... I just released klibc-0.124 with the 64-bit off_t and statfs64 changes. The API shouldn't have changed, but the ABI is now 64 bits in (hopefully) all the right places. It's probably buggy... beat me up or (better) send a patch... -hpa

It seems that klibc uses __sparc64__ to determine if it's compiled in 64 bit mode on sparc, gcc doesn't define __sparc64__ use __sparc_v9__ instead as proposed by Kyle McMartin <kyle@parisc-linux.org>, based on a patch by Sjoerd Simons <sjoerd@spring.luon.net> Signed-off-by: maximilian attems <maks@sternwelten.at> --- resend --- klibc-1.2.2.orig/include/sys/vfs.h

please pull from git://charm.itp.tuwien.ac.at/mattems/klibc/.git branch maks. arch/mips/klibc/archconfig.h | 3 +++ klibc/sysconfig.h | 10 ++++++++++ sys/vfs.h | 17 +++++++++++++++++ 3 files changed, 30 insertions(+)

If you export two subvolumes of a btrfs filesystem, they will both be given the same uuid so lookups will be confused. blkid cannot differentiate the two, so we must use the fsid from statfs64 to identify the filesystem. We cannot tell if blkid or statfs is best without knowing internal details of the filesystem in question, so we need to encode specific knowledge of btrfs in mountd. This is

The latest version that Western Digital has shipped with the My cloud devices accesses the disk about twice a minute. The access to /dev/sda2 is causing the system to keep the disk from going into standby mode. I don't understand the call to quotactl every minute when no one is trying to access the share. An strace of one of the processes shows the following: poll([{fd=13,

Hi Louis, On Wed, Apr 22, 2015 at 01:15:21PM +0200, L.P.H. van Belle wrote: > Or.. > get the sources and recompile agains 14.04 > > use the following commands. > enable the deb-src in /etc/apt/sources.list > and run : > > apt-get build-dep sernet-samba > apt-get source sernet-samba -b > > you wil end up with .deb files ;-) yep, thanks - I'll check it

Thanks for the report.? According to my reading, this use of "mv" is ok and the renameat2() call which the invocation of "mv" leads to is also ok and allowed by POSIX in this context. It could only fail with EEXIST if the target directory (path/pkg) was not empty. So far I've not been able to reproduce but we could fall back to copy like on Windows. Best Tomas On

On 5/7/19 6:18 PM, Henrik Bengtsson wrote: > On Tue, May 7, 2019 at 9:05 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> Thanks for the report. According to my reading, this use of "mv" is ok >> and the renameat2() call which the invocation of "mv" leads to is also >> ok and allowed by POSIX in this context. It could only fail with EEXIST

hi, all. I had an problem with rsync-2.5.4/5 related to filename length. On Linux box (kernel-2.4.18 + ext3 fs), filename length limits to 255byte, but rsync can't handle fn > (255 -9) byte. So I had an instant hack to avoid this problem. Patch file attatched works fine in my case, but I'm not sure that it is correct or not. Any suggestions ? Please cc me, I'm not on this

I'm observing that the new staged installation in R 3.6.0 can produce: mv: cannot move ?/home/alice/R/x86_64-pc-linux-gnu-library/3.6/00LOCK-codetools/00new/codetools? to ?/home/alice/R/x86_64-pc-linux-gnu-library/3.6/codetools?: File exists ERROR: moving to final location failed on some file systems. # EXAMPLE $ R --vanilla R version 3.6.0 (2019-04-26) -- "Planting of a Tree"

On Tue, May 7, 2019 at 9:05 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > Thanks for the report. According to my reading, this use of "mv" is ok > and the renameat2() call which the invocation of "mv" leads to is also > ok and allowed by POSIX in this context. It could only fail with EEXIST > if the target directory (path/pkg) was not empty.

I created a 1TB RAID1. So far it is just for testing, no important data on there. After a reboot, I tried to mount it again # mount /dev/mapper/vg00-btrfsvol0_0 /mnt/btrfs0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg00-btrfsvol0_0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or

Hi, I found what seems to be a bug in smbd (and smbclient?) from samba-2.2.8a-1. Scenario is the following: All users have accounts in linux box "mate", with homes mounted via NFS from linux box "fserver". mate and fserver run samba-2.2.8a-1, mate ONLY validates passwords and has no shares; fserver in turn, ONLY shares [homes] and [netlogon], but has no users, so samba uses

Hi, I have a virtual user defined in class users Class A inherits users and uses override to add another group to the user with User[''user''} {group +> ''group''} class B inherits users and does the same for another group. in rare cases, class A and class B are on the same machine. I know that if class B inherits class A which inherits users works, but I

You can compile an empty C source code with clang -S -emit-llvm and copy the data layout from there. 2011/10/27 Seb <babslachem at gmail.com> > Hi all, > > Can someone give me advice on what should be a good definition of target > datalayout for an ARM cortex-A9 + neon target and x86 32-bit ? > Shall I use a different definition for a cortex-A9 without neon ? > Thanks for

https://bugzilla.mindrot.org/show_bug.cgi?id=1607 Summary: compile errors buliding OpenSSH for older Red Hat Product: Portable OpenSSH Version: 5.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org

I don't really know exactly why you're getting this, but it seems like you forgot the last line in your Builtins<Target>.def. Namely, the line: #undef BUILTIN On Thu, May 26, 2016 at 1:29 AM, Rail Shafigulin via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I've introduced intrinsics for my target however when I compile llvm+clang > I get a a redefinition warning:

Hi all, Can someone give me advice on what should be a good definition of target datalayout for an ARM cortex-A9 + neon target and x86 32-bit ? Shall I use a different definition for a cortex-A9 without neon ? Thanks for your advices Best Regards Seb -------------- next part -------------- An HTML attachment was scrubbed... URL:

I've introduced intrinsics for my target however when I compile llvm+clang I get a a redefinition warning: llvm/tools/clang/lib/Basic/Targets.cpp:904:0: warning: "BUILTIN" redefined [enabled by default] #define BUILTIN(ID, TYPE, ATTRS) { #ID, TYPE, ATTRS, 0, ALL_LANGUAGES }, ^ In file included from llvm/tools/clang/lib/Basic/Targets.cpp:26:0: