util-linux/.gitignore

190 lines
1.6 KiB
Plaintext
Raw Permalink Normal View History

#
# generic stuff
#
*.gcda
*.gcno
*.gcov
*.la
*.lo
*.pc
*.pyc
*.so
*.so.*
*.static
*.swp
*.vim
*.[ao]
*~
*.1
*.3
*.5
*.8
*.stamp
.clang_complete
.deps
.dirstamp
.libs
.tarball-version
.version
ABOUT-NLS
aclocal.m4
ar-lib
autom4te.cache
compile
config.cache
config.guess
config.h
config.h.in
config.log
config.rpath
config.status
config.sub
config/ltmain.sh
config/py-compile
config/test-driver
configure
cscope.out
depcomp
INSTALL
install-sh
libtool
m4/*.m4
Makefile
Makefile.in
missing
mkinstalldirs
stamp-h
stamp-h.in
stamp-h1
tags
test-suite.log
tests/run.sh.log
tests/run.sh.trs
update.log
ylwrap
#
# binaries
#
/addpart
/agetty
/blkdiscard
/blkzone
/blkid
/blockdev
/cal
/cfdisk
/chcpu
/chfn
/choom
chmem: new tool Move the s390 specific chmem tool to util-linux. The chmem tool was originally written in perl and is part of the s390-tools package which can be found here: https://www.ibm.com/developerworks/linux/linux390/s390-tools.html Given that the tool is architecture independent, there is no reason to keep it in an s390 specific repository. It seems to be useful for other architectures as well. This patch converts the tool to C and adds it to util-linux, while the command line options stay compatible. The only exception is the option "-v" which used to be the short form of "--version". That got changed to "-V" so it behaves like most other tools contained within util-linux. The chmem tool can be used to set memory online or offline. This can be achieved by specifying a memory range: Memory Block 19 (0x0000000130000000-0x000000013fffffff) disabled or by specifying a size where chmem will automatically select memory blocks: Memory Block 21 (0x0000000150000000-0x000000015fffffff) disable failed Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled or by specifying memory block numbers instead of address ranges: Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled This is based on a patch from Clemens von Mann. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
2016-10-12 07:00:46 -05:00
/chmem
/chrt
/chsh
/col
/colcrt
/colrm
/column
/ctrlaltdel
/delpart
/dmesg
/eject
/fallocate
/fdformat
/fdisk
/fincore
/findfs
/findmnt
/flock
/fsck
/fsck.cramfs
/fsck.minix
/fsfreeze
/fstrim
/getopt
/hardlink
/hexdump
/hwclock
/ionice
/ipcmk
/ipcrm
/ipcs
/irqtop
/isosize
/kill
/last
/ldattach
/line
/logger
/login
/look
/losetup
/lsblk
/lsipc
/lsirq
/lscpu
/lslocks
/lslogins
lsmem: new tool Move the s390 specific lsmem tool to util-linux. The lsmem tool was originally written in perl and is part of the s390-tools package which can be found here: https://www.ibm.com/developerworks/linux/linux390/s390-tools.html Given that the tool is architecture independent, there is no reason to keep it in an s390 specific repository. It seems to be useful for other architectures as well. This patch converts the tool to C and adds it to util-linux, while the command line options stay compatible. The only exception is the option "-v" which used to be the short form of "--version". That got changed to "-V" so it behaves like most other tools contained within util-linux. The lsmem tool inspect the contents of /sys/devices/system/memory and prints a summary output similar to what lscpu does: RANGE SIZE STATE REMOVABLE BLOCK 0x0000000000000000-0x000000005fffffff 1,5G online yes 0-5 0x0000000060000000-0x000000007fffffff 512M online no 6-7 0x0000000080000000-0x000000013fffffff 3G online yes 8-19 0x0000000140000000-0x000000014fffffff 256M offline - 20 0x0000000150000000-0x000000017fffffff 768M online no 21-23 Memory block size : 256M Total online memory : 5,8G Total offline memory: 256M In order to keep the output small the tool merges subsequent address ranges where the attributes are identical. To avoid merging of line the "-a" option can be used. The lsmem tool also has "--extendend" and "--parsable" option which can be used to customize the output, e.g. limit the output to specified columns. This is quite similar to what the lscpu tool does. This is based on a patch from Clemens von Mann. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
2016-10-12 07:00:45 -05:00
/lsmem
/lsns
/mcookie
/mesg
/mkfs
/mkfs.bfs
/mkfs.cramfs
/mkfs.minix
/mkswap
/more
/mount
/mountpoint
/namei
/newgrp
/nologin
/nsenter
/partx
/pg
/pivot_root
/prlimit
/raw
/readprofile
/rename
/renice
/resizepart
/rev
/rfkill
/rtcwake
/runuser
/sample-*
/script
/scriptreplay
/scriptlive
/setarch
/setpriv
/setsid
/setterm
/sfdisk
/su
/sulogin
/swaplabel
/swapoff
/swapon
/switch_root
/taskset
/test_*
/tunelp
/ul
/umount
/unshare
/utmpdump
/uuidd
/uuidgen
/uuidparse
/vipw
/wall
/wdctl
/whereis
/wipefs
/write
/zramctl
/uclampset
meson: add second build system To build: meson build && ninja -C build To run tests: ninja -C build check To install for packaging: DESTDIR=/var/tmp/inst ninja -C build install To install for realz: sudo ninja -C build install v2: - Optional items are now based on the 'feature' feature in meson. Built libraries which are disabled turn into disabler() objects and also poison any executables which link to them. What is there: - building of the binaries and libs and the python module - installation of binaries, libs, python module, localization files, man pages, pkgconfig files - running of tests - most options to configure build equivalently to the ./configure settings Partially implemented: - disabling of stuff when things missing. In the C code, the defines are all used, so that should be fine. In the build system, some files should be skipped, but that is probably not always done properly. Getting this right might require some testing of various build option combinations to get the details right. Not implemented: - static builds of fdisk and other binaries - things marked with XXX or FIXME - ??? Differences: - .la files are not created. They are useless and everybody hates them. - Requires.private in pkgconfig files are not present in the autogenerated .pc file. Not sure if they should be there or not. If necessary, they can be added by hand. - man pages and systemd units are installed by the install target. Not sure why 'make install' doesn't do that. - the split between / and /usr is probably wrong. But it's all pointless anyway, so maybe we could simplify things but not implementing it at all under meson?
2020-02-23 12:42:55 -06:00
/build*/