linux-ftools
linux-ftools copied to clipboard
yazgoo
Automatically exported from code.google.com/p/linux-ftools
``` Hello, Is this project dead? I've been having problems building from source. I think these are mainly down to a few changes in build tools since this was written....
``` just use unistd.h ``` Original issue reported on code.google.com by `jxinging` on 27 Dec 2013 at 8:03 Attachments: - [linux-fadvise.c.patch](https://storage.googleapis.com/google-code-attachments/linux-ftools/issue-8/comment-0/linux-fadvise.c.patch)
``` What steps will reproduce the problem? 1. Run linux-fincore on a file >2GB on a 32-bit system What is the expected output? What do you see instead? I see...
``` What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what...
``` Allow build on both Debian and RHEL - unistd_64.h is debian specific. unistd.h has a ifdef that selects the right distribution specific file. ``` Original issue reported on code.google.com...
``` What steps will reproduce the problem? 1. gcc fallocate.c 2. ./a.out file.txt 10000000 3. ls -al What is the expected output? What do you see instead? upon ls -al...
``` I'd suggest to change building instructions on debian to be: = Making Debian packages apt-get install autoconf automake fakeroot debhelper dpkg-dev dpkg-buildpackage -I'.git' -I'.svn' -I'.hg' -i -sd -us -uc...
``` Hello! I've tryed to build linux-ftools into Debian Lenny amd64 package and met issue: parsechangelog/debian: warning: debian/changelog(l4): found start of entry where expected more change data or trailer LINE:...
``` See man 3 sprintf, first argument is a buffer, not format string. Patch attached. Also squeeze the output (should squeeze even more), open files read-only, do not call mmap...