Movatterモバイル変換


[0]ホーム

URL:


summaryrefslogtreecommitdiff
path:root/README
blob: 424e3f064125cd5b25cc0f637afb8b982acf0ea8 (plain)
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141
These are the GNU core utilities.  This package is the union ofthe GNU fileutils, sh-utils, and textutils packages.Most of these programs have significant advantages over their Unixcounterparts, such as greater speed, additional options, and fewerarbitrary limits.The programs that can be built with this package are:  [ arch b2sum base32 base64 basename basenc cat chcon chgrp chmod chown  chroot cksum comm coreutils cp csplit cut date dd df dir dircolors dirname  du echo env expand expr factor false fmt fold groups head hostid hostname  id install join kill link ln logname ls md5sum mkdir mkfifo mknod mktemp  mv nice nl nohup nproc numfmt od paste pathchk pinky pr printenv printf ptx  pwd readlink realpath rm rmdir runcon seq sha1sum sha224sum sha256sum  sha384sum sha512sum shred shuf sleep sort split stat stdbuf stty sum sync  tac tail tee test timeout touch tr true truncate tsort tty uname unexpand  uniq unlink uptime users vdir wc who whoami yesSee the file NEWS for a list of major changes in the current release.If you obtained this file as part of a "git clone", then see theREADME-hacking file.  If this file came to you as part of a tar archive,then see the file INSTALL for general compilation and installationinstructions, or README-install for system and coreutils specific instructions.Like the rest of the GNU system, these programs mostly conform toPOSIX, with BSD and other extensions.  For closer conformance, orconformance to a particular POSIX version, set the POSIXLY_CORRECTand the _POSIX2_VERSION environment variables, as described inthe documentation under "Standards conformance".The ls, dir, and vdir commands are all separate executables instead ofone program that checks argv[0] because people often rename theseprograms to things like gls, gnuls, l, etc.  Renaming a programfile shouldn't affect how it operates, so that people can get thebehavior they want with whatever name they want.Special thanks to Paul Eggert, Brian Matthews, Bruce Evans, Karl Berry,Kaveh Ghazi, and François Pinard for help with debugging and portingthese programs.  Many thanks to all of the people who have taken thetime to submit problem reports and fixes.  All contributed changes areattributed in the commit logs.And thanks to the following people who have provided accounts forportability testing on many different types of systems: Bob Proulx,Christian Robert, François Pinard, Greg McGary, Harlan Stenn,Joel N. Weber, Mark D. Roth, Matt Schalit, Nelson H. F. Beebe,Réjean Payette, Sam Tardieu.Thanks to Michael Stone for inflicting test releases of this packageon Debian's unstable distribution, and to all the kind folks who usedthat distribution and found and reported bugs.Note that each man page is now automatically generated from a templateand from the corresponding --help usage message.  Patches to the templatefiles (man/*.x) are welcome.  However, the authoritative documentationis in texinfo form in the doc directory.***************Feature requests:---------------If you would like to add a new feature, please try to get some sort ofconsensus that it is a worthwhile change.  One way to do that is to sendmail to coreutils@gnu.org including as much description and justificationas you can.  Based on the feedback that generates, you may be able toconvince us that it's worth adding.  Please also consult the list ofpreviously discussed but ultimately rejected feature requests at:https://www.gnu.org/software/coreutils/rejected_requests.html***************Reporting bugs:---------------Send bug reports, questions, comments, etc. to bug-coreutils@gnu.org.To suggest a patch, see the files README-hacking and HACKING for tips.All of these programs except 'test' recognize the '--version' option.When reporting bugs, please include in the subject line both the packagename/version and the name of the program for which you found a problem.If you have a problem with 'sort', try running 'sort --debug', as itcan often help find and fix problems without having to wait for ananswer to a bug report.  If the debug output does not suffice to fixthe problem on your own, please compress and attach it to the rest ofyour bug report.IMPORTANT: if you take the time to report a test failure,please be sure to include the output of running 'make check'in verbose mode for each failing test.  For example,if the test that fails is tests/df/df-P.sh, then you wouldrun this command:  make check TESTS=tests/df/df-P.sh VERBOSE=yes SUBDIRS=. >> log 2>&1For some tests, particularly perl tests, you can get even more detail by addingDEBUG=yes. Then include the contents of the file 'log' in your bug report.***************************************There are many tests, but nowhere near as many as we need.Additions and corrections are very welcome.If you see a problem that you've already reported, feel free to re-reportit -- it won't bother us to get a reminder.  Besides, the more messages weget regarding a particular problem the sooner it'll be fixed -- usually.If you sent a complete patch and, after a couple weeks you haven'treceived any acknowledgement, please ping us.  A complete patch includesa well-written ChangeLog entry, unified (diff -u format) diffs relativeto the most recent test release (or, better, relative to the latestsources in the public repository), an explanation for why the patch isnecessary or useful, and if at all possible, enough information toreproduce whatever problem prompted it.  Plus, you'll earn lots ofkarma if you include a test case to exercise any bug(s) you fix.Here are instructions for checking out the latest development sources:  https://savannah.gnu.org/git/?group=coreutilsFor general documentation on the coding and usage standardsthis distribution follows, see the GNU Coding Standards at:https://www.gnu.org/prep/standards/For any copyright year range specified as YYYY-ZZZZ in this packagenote that the range specifies every single year in that closed interval.Please see the file COPYING for copying conditions.========================================================================Copyright (C) 1998-2026 Free Software Foundation, Inc.Permission is granted to copy, distribute and/or modify this documentunder the terms of the GNU Free Documentation License, Version 1.3 orany later version published by the Free Software Foundation; with noInvariant Sections, with no Front-Cover Texts, and with no Back-CoverTexts.  A copy of the license is included in the "GNU FreeDocumentation License" file as part of this distribution.

[8]ページ先頭

©2009-2026 Movatter.jp