summaryrefslogtreecommitdiffstats
path: root/usr.sbin
Commit message (Collapse)AuthorAgeFilesLines
* quiet compiler complaint about comparing &v against NULLsam2008-01-101-2/+2
|
* Revise the TECHNICAL DETAILS section.ru2008-01-091-68/+87
| | | | Reviewed by: skv
* Honour the logical current working directory ($PWD) when using config'semaste2008-01-081-0/+18
| | | | | | | | -d destdir option. For an automounted src tree using the logical cwd in the Makefile keeps amd(8)'s mount timeout refreshed. Code to check $PWD's validity cribbed from pwd(1). Discussed on hackers@.
* When the ms/req fields exceed 1 second, drop the fractions to fit more digits.phk2008-01-061-3/+12
| | | | | This is unfortunately necessary with some flash based devices which can get hundreds of seconds behind with softupdates enabled.
* Add the mtree.5 manpage. I'll come back soon andkientzle2008-01-012-1/+271
| | | | | | | | | remove the format specification from mtree.8. I also need to reconcile a few issues between this mtree.5 and what is actually implemented in FreeBSD's mtree utility. MFC after: 30 days
* Change sysinstall's handling of X11 stuff. Doing it in pieces waskensmith2008-01-014-268/+5
| | | | | | | | | | | | | | | | | probably the right thing to do a while ago but xorg has progressed to the point that for novice users (who are the ones expected to think installing X11 during an install...) it's best to just install the whole x11/xorg metaport for them. This removes the X11 sub-menus and sets it up so you just select whether or not you want X11. While here garbage collect an X11 configuration menu I missed removing when I removed support for attempting xorg configuration from inside sysinstall a while ago. Discussed with: rwatson, kris No objection from: re Release build tested by: rwatson MFC after: 1 week
* Plug a memory leak. Once any given package (e.g. perl) was installedkensmith2007-12-291-1/+3
| | | | | | | | | | we would leak a saved screen for every other package we tried to install that listed perl as one of its dependencies. When installing things like gnome and kde that wound up being a LOT of leaked memory. Insta-MFC request coming so this can be tested as part of 6.3-RC2... Testing help from: kris
* Adjust the some error messages as suggested during re@ review, andkensmith2007-12-291-3/+10
| | | | adjust a comment that won't be true shortly.
* Attempt to reduce the rate of foot-shooting injuries by adding a newcperciva2007-12-281-0/+9
| | | | | | | | paragraph clarifying that portsnap does not behave the same way as cvs and cvsup where local modifications are concerned. Submitted by: peter Feet shot: peter, kris, obrien, + many others
* The limit on datasize in the install environment is 128M. That's a bitkensmith2007-12-281-0/+10
| | | | | | | | | | | | | | | too small for today's standards. While loading packages sysinstall blows past this by a LOT but I think (hope...) that's caused by other bugs. I'll look more into why sysinstall's memory use has gotten so out of control as it loads packages but independent of that there really is no reason to leave the limits on datasize and stacksize in place. And they can cause problems for some of the things "modern packages" might be doing via pkg_add which gets run by sysinstall and would inherit the limits. Another insta-MFC probably coming, this is holding up 6.3-RC2. Sysinstall's memory use is so out of control it blows past the current limit before it finishes loading either of the meta-packages kde or gnome...
* Spring forward into the late 1970's by following item 5 in the yaccimp2007-12-251-51/+34
| | | | | | | | | | | | | manual's Appendix D ("Old Features Supported but not Encouraged") in the Seventh Edition Unix Programmer's Manual (January, 1979) by retiring the " = {" method of of action specification in favor of a plain "{". It is no longer necessary for this bootstrap program to be compatible with 6th Edition systems. Some yaccs in the wild do not support this old syntax any more, and compatibility with those systems is more important these days (as there are easily 7 orders of magnitude more of them than real v6 systems today). Reviewed by: jhb@ and dds@ (the latter gave the reference).
* For the INDEX file to be used on disc1 of the 7.0-RELEASE the longestkensmith2007-12-241-5/+17
| | | | | | | | | | "build dependencies" field is 5,108 characters which overflows the length of the junk buffer by a teeny bit. This whole section needs much more error checking but for now just completely ignore stuff we have no interest in instead of copying it to someplace we don't use in the process. Insta-MFC probably coming since this is holding up 7.0-RC1...
* Revert previous commit and fix OpenPAM issue properly.des2007-12-221-6/+6
|
* Fix/workaround build breakage caused by PAM importkmacy2007-12-211-1/+1
| | | | | struct pam_conv takes a void * for the appdata_ptr but is being passed a const char * - explicitly cast away the const
* In the following scenario:dougb2007-12-211-0/+7
| | | | | | | | | | | | | | | 1. Start mergemaster 2. Interrupt it 3. < Somehow the temproot directory disappears > 4. mergemaster -r Many bad things can happen, especially if the -i option is in use. Therefore, add a check to make sure it still exists before we start comparing files. Brought to my attention by: PR: bin/40538 Submitted by: Cyrille Lefevre <cyrille.lefevre@laposte.net>
* - Adjust INDEX file name to INDEX-8 so that it matches the major FreeBSDgabor2007-12-201-5/+5
| | | | | | | version number, as it is named after that PR: docs/118053 Submitted by: Michael Plass <mfp49_freebsd@plass-family.net>
* enable wired driver supportsam2007-12-201-0/+2
| | | | | Submitted by: "Paul B. Mahol" <onemda@gmail.com> MFC after: 1 week
* Correct typo in usage message.imp2007-12-191-1/+1
|
* A few more adjustments needed because of changes in xorg. Just installingkensmith2007-12-172-2/+6
| | | | | | | | | xorg-server doesn't include any video drivers so install xorg-drivers as well. And if font-alias isn't installed the X server won't start, complaining it can't find the font "fixed". Insta-MFC coming, this was tested with a RELENG_6_3 release build and the necessary packages as part of the first round of testing for 6.3-RC2.
* o Get missed "%" in output back.maxim2007-12-161-2/+2
| | | | | Submitted by: sem MFC after: 1 week
* + Open ctty in non-blocking mode to avoid hangs during open and close(waitingobrien2007-12-111-9/+20
| | | | | | | | | | | | | | for the port to drain). + Handle "*" as a priority properly. + Test what is free'ed. + Dynamically determine length vs. hardcoding it. + Free the previous message buffer (f_prevline) only after logging all the messages and just before the process exit. Also check f_prevline for NULL before using it. + The time displayed is not synchornized with the other log destinations. + Fix a comment. Obtained from: Juniper Networks
* Backout previous commit, since it's done without maintainerskrion2007-12-0910-173/+1
| | | | | | | approval. These changes were approved by adding it as port to ports/ tree, but not for src/. I talked to PR submitter and miwi@ some days ago and explained the reasons for it, the both were agree to add it to ports/ only.
* Be more consistant and use UNZIPPER everywhere.obrien2007-12-092-6/+5
|
* Add the 'pkg_search' script.obrien2007-12-0910-1/+173
| | | | | | This makes it easier to figure what packages you want to install. Submitted by: Matthias Schmidt <schmidtm @ mathematik . uni-marburg . de>
* Enhance descriptions in the timed manual.remko2007-12-081-7/+32
| | | | | | PR: docs/115445 Submitted by: "Julian Stacey" <jhs at berklix dot org> MFC After: 3 days
* When applying a spec, traverse the existing directory tree in lexicaldes2007-12-071-1/+7
| | | | | | | | order. This allows direct comparison of the output of two different runs, regardless of the order in which readdir(2) returns directory entries. MFC after: 3 weeks
* Introduce pmcstat(8) changes for summarizing hwpmc(4) callchain records injkoshy2007-12-075-209/+1075
| | | | | | | | in textual form and in gmon.out format. Update manual page. Sponsored by: FreeBSD Foundation and Google Inc.
* style(9)obrien2007-12-051-15/+15
|
* Reenable the Amd build. 'make world' passed on my amd64 8-CURRENT system.obrien2007-12-051-0/+1
|
* Teach Amd how to unmount.obrien2007-12-051-0/+3
|
* Accidently created the file with the wrong name.obrien2007-12-051-8/+0
|
* 'amu_autofs_prot.h'obrien2007-12-051-0/+8
|
* Adjust for new files added to 6.1.5, and files retired from 6.0.10p1.obrien2007-12-051-9/+10
| | | | | Also TCP Wrappers is now supported. Also tweak the MK_HESIOD.
* Update for version 6.1.5.obrien2007-12-051-117/+253
|
* We now have to use part of the vendor supplied xdr_func.c.obrien2007-12-051-3/+8
| | | | util renamed to strutil to be more clear of its purpose.
* These now need to link with libamu.obrien2007-12-052-0/+6
|
* Add new BUILD_* knobs, and switch our definition & setting of BUILD_*obrien2007-12-052-6/+8
| | | | and configured settings.
* Autoconf would have created a symlink from conf/autofs/autofs_default.hobrien2007-12-051-0/+8
| | | | | | | to autoamu_autofs_prot.h. It is easier to just create shell header within the Bmake framework. For now it's a stub - fill out when we know our Autofs direction.
* Temporarily disable amd for import.obrien2007-12-051-1/+0
|
* zic(8) should exit the loop when the end of the string is reached duekevlo2007-12-031-1/+4
| | | | | | to the call to error(). The problem found by doing fuzz testing. MFC after: 3 days
* When printing the contents of a HWPMC log in human readable form:jkoshy2007-12-031-3/+8
| | | | | | | | | - Print a warning if the version number recorded in the log is not what the tool expects. - Print a tidier error message when an unrecognized event is encountered in the log. - Don't print a spurious 'Unknown error: 0' when exiting after a parse error.
* s/effect/affect/remko2007-11-271-2/+2
| | | | | | PR: docs/118266 Submitted by: "Kim Scarborough" <sluggo at unknown dot nu> MFC After: 3 days
* These are the things that the tinderbox has problems with because itjb2007-11-204-0/+4
| | | | | | | | doesn't use the default CFLAGS which contain -fno-strict-aliasing. Until the code is cleaned up, just add -fno-strict-aliasing to the CFLAGS of these for the tinderboxes' sake, allowing the rest of the tree to have -Werror enabled again.
* Use an explicit pointer cast since NULL isn't guaranteed to be definedjb2007-11-181-1/+1
| | | | | | as a pointer type. Submitted by: Christoph Mallon - christoph mallon at gmx de
* Use a NULL instead of a zero to avoid a compiler warning about a missing ↵jb2007-11-181-1/+1
| | | | sentinel.
* Reduce the WARNS levels in a couple of places so that we can enablejb2007-11-181-1/+1
| | | | -Werror at higher WARNS levels like we did before gcc4 was imported.
* Fix a compiler warning by using a printf format matching the variablejb2007-11-171-1/+1
| | | | type.
* Use uintptr_t to cast a pointer to an integer to avoid compiler warningsjb2007-11-172-2/+2
| | | | on processors where sizeof(void *) > sizeof(int).
* Use printf formats which match the variable types without casts so wejb2007-11-171-4/+4
| | | | can go back to using -Werror in higher WARNS levels.
* Add change missing from previous commit: Remove temporary file.cperciva2007-11-161-1/+1
|
OpenPOWER on IntegriCloud