summaryrefslogtreecommitdiffstats
path: root/usr.sbin
Commit message (Collapse)AuthorAgeFilesLines
* Second round of floppy disk driver documentation updates: document thejoerg2001-12-252-117/+312
| | | | | | | changes in the userland utilities. For fdcontrol(8), i now finally keep my promise made more than 7 years ago that ``the fdcontrol utility is currently under development and the user interface will likely change''. :-)
* Argh...save buffer before committing. NO_WERROR takes a value ofmikeh2001-12-241-1/+1
| | | | 'yes', not 2.
* WARNS=2 fixup. Set NO_WERROR due to use of 'j' format specifier.mikeh2001-12-242-12/+15
| | | | PR: bin/32567
* Add a manpage for the ifpi2 driver.gj2001-12-222-1/+65
| | | | MFC after: 4 weeks
* Add support for the AVM Fritz!Card PCI version 2 controller.gj2001-12-221-0/+1
| | | | MFC after: 4 weeks
* o Wording and spelling fixes for security menu description.rwatson2001-12-212-10/+10
|
* o Expand the text describing the Security options menu.rwatson2001-12-215-10/+12
| | | | | | | | | | | | | | | | o Move nfs_reserved_port_only out of security profiles (where it was set somewhat improperly) to the Security options menu directly. Previously, the variable was set to true for Moderate, but not for Extreme, which is at best inconsistent. o Update the Security Profiles help file to remove reference to the NFS reserved port. o Note that the kernel currently defaults the sysctl to '0', but sysinstall has changed it to '1' as a default as of late; however, rc.conf sets the value to NO as the default. This change brings them relatively into sync. Sponsored by: DARPA, NAI Labs
* o Add a configSecurity menu to generally configure security settings,rwatson2001-12-216-6/+62
| | | | | | | | | | and pull configSecurityProfile under that menu. Add a menu option to determine whether LOMAC is enabled at boot. Probably, eventually, many of the 'Security Profile' menu choices should be pulled out independently into the Security Menu, so as to make them individually selectable. Sponsored by: DARPA, NAI Labs
* o Don't make 'Moderate Security Settings' the DEFAULT, as otherwiserwatson2001-12-212-4/+4
| | | | | | selecting 'Cancel' to avoid making changes doesn't work. Really, we should deprecate security profiles and move to a more fine-grained model.
* mdoc(7) police: fix markup, remove stray .Xr.ru2001-12-211-2/+1
|
* Enable soft updates by default for everything but the root filesystem.jkh2001-12-202-2/+2
| | | | | | | | The user can still toggle it back off in the label editor (or post-install for that matter) if they explicitly do not want soft updates to be used for some reason. Agreed to be a good thing by: kirk
* Use correct mode for temporary file.nectar2001-12-201-1/+1
| | | | Reported by: ryan beasley <ryanb@goddamnbastard.org>
* Fix typo in usage (power same -> power save).pb2001-12-181-1/+1
|
* Install files via FILES.ru2001-12-173-21/+9
|
* FILES support for bsd.prog.mk. See bsd.README for details.ru2001-12-176-49/+16
| | | | Stolen from: NetBSD
* Add another level of checking to 'chkprintcap', which is done bygad2001-12-154-6/+352
| | | | | | | | | | | | | "skimming thru" the printcap file looking for some common mistakes that people make. These are the kinds of mistakes where the printcap file probably looks correct to human eyes, but is wrong in some subtle way which causes a problem in some queue definitions. The program treats these as "warnings" not "errors". Note that I'm flexible on the m.f.c. schedule, if people would rather this waited until after 4.5-release. Reviewed by: no screams from freebsd-audit freebsd-print@bostonradio.org MFC after: 4 days
* Long promised major enhancement set for the floppy disk driver:joerg2001-12-155-244/+663
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | . The main device node now supports automatic density selection for commonly used media densities. So you can stuff your 1.44 MB and 720 KB media into your drive and just access /dev/fd0, no questions asked. It's all that easy, isn't it? :) . Device density handling has been completely overhauled. The old way of hardwired kernel density knowledge is no longer there. Instead, the kernel now implements 16 subdevices per drive. The first subdevice uses automatic density selection, while the remaining 15 devices are freely programmable. They can be assigned an arbitrary name of the form /dev/fd[:digit]+.[:digit:]{1,4}, where the second number is meant to either implement device names that are mnemonic for their raw capacity (as it used to be), or they can alternatively be created as "anonymous" devices like fd0.1 through fd0.15, depending on the taste of the administrator. After creating a subdevice, it is initialized to the maximal native density of the respective drive type, so it needs to be customized for other densities by using fdcontrol(8). Pseudo-partition devices (fd0a through fd0h) are still supported as symlinks. . The old hack to use flags 0x1 to always assume drive 0 were there is no longer supported; this is now supposed to be done by wiring the devices down from the loader via device flags. On IA32 architectures, the first two drives are looked up in the CMOS configuration records though. On PCMCIA (i. e., the Y-E Data controller of the Toshiba Libretto), a single drive is always assumed. . Other specialities like disabling the FIFO and not probing the drive at boot-time are selected by per-controller or per-drive flags, too. . Unit attentions (media has been changed) are supposed to be detected now; density autoselection only occurs after a unit attention. (Can be turned off by a per-drive flag, this will cause each Fdopen() to perform the autoselection.) . FM floppies can be handled now (on controllers that actually support it -- not all do these days). . Fdopen() can be told to avoid density selection by setting O_NONBLOCK; this leaves the descriptor in a half-opened state where only a few ioctls are accepted. This is necessary to run fdformat on a device that uses automatic density selection (since you cannot autoselect on an unformatted medium, obviously). . Just differentiate between a plain old NE765 and the enhanced chips, but don't try more; the existing code was wrong and only misdetected the chips anyway. BUGS and TODOs: . All documentation update still needs to be done. . Formatting not-so-standard format yields unpredictable results; i have yet to figure out why this happens. "Standard" formats like 720 and 1440 KB do work, however. . rc scripts are needed to setup device nodes with nonstandard densities (like the old /dev/fdN.MMM we used to have). . Obtaining device flags from the kernel environment doesn't work yet, thus currently only drives that are present in (IA32) CMOS are really detected. Someone who knows the odds and ends about device flags is needed here, i can't figure out what i'm doing wrong. . 2.88 MB still needs to be done.
* Better document gif interface cloning intrastructure.brooks2001-12-141-3/+9
| | | | MFC After: 2 days
* Add some wisdom to the jail setup instructions.phk2001-12-141-1/+11
|
* Add prototypes for main() so that these programs compile with -Werrorluigi2001-12-142-0/+2
| | | | | | | | | | | | (which somehow now seems to be the default for compiling -current). This error popped up while doing a PicoBSD cross-compile on a 4.3-ish system, it may well be that there are other apps which have similar problems, but I did not spot them as they are not included in my picobsd config. Whether adding prototypes for main() is the correct solution or not I have no idea, a request to -current on the matter went basically unanswered. Those who have better ideas are welcome to back this out and replace it with the correct fix.
* Add bmake glue for src/contrib/smbfs and connect userland smbfssheldonh2001-12-141-0/+23
| | | | | | | | | | support to the build. The MFC reminder below is subject to <re@FreeBSD.org> approval prior to 4.5-RELEASE. Reviewed by: bp, fjoe MFC: 1 week
* mdoc(7) police overhaul.ru2001-12-141-118/+155
|
* Bump configvers for different handling of maxusers.peter2001-12-141-1/+1
|
* - Update the sysctl mibs in order to reflect the recent kern_jail.carr2001-12-121-9/+9
| | | | | | | changes. Approved by: rwatson Reviewed by: rwatson
* Update the default newfs block and fragment sizes from 8192/1024 tosheldonh2001-12-112-2/+2
| | | | | | | | | | | | | | | | | | | 16384/2048. Following recent discussions on the -arch mailing list, involving dillon and mckusick, this change parallels the one made over a decade ago when the default was bumped up from 4096/512. This should provide significant performance improvements for most folks, less significant performance losses for a few folks and wasted space lost to large fragments for many folks. For discussion, please see the following thread in the -arch archive: Subject: Using a larger block size on large filesystems The discussion ceases to be relevant when the issue of partitioning schemes is raised.
* Fix a typo.sheldonh2001-12-111-1/+1
| | | | Reported by: Jurrien Koopmans <jjkoopmans@home.nl>
* s/sysctl -w/sysctl/ru2001-12-112-4/+4
|
* WARNS=2 cleanup.mikeh2001-12-112-7/+12
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* Fix the mouse question again to only run the mouse menu if a user doesn'tjhb2001-12-102-2/+2
| | | | | | | | | | have a USB mouse. Here's the deal on how this works: USB mouse have moused run for them automatically by usbd so we don't need to setup moused for them. We do need to setup moused for other mice though, so if the user has a USB mouse, we don't need to do anything. Hence the wording "Do you have a non-USB mouse installed?" for the question. The question can be reworded as "Do you have a PS/2 or Serial mouse installed?" instead if that is preferred.
* Reorder WARNS line for style.mikeh2001-12-109-18/+9
| | | | Pointed out by: bde
* Install i4bing.4. It lives for more than year in the tree, butphantom2001-12-101-4/+3
| | | | | | never was installed. MFC After: 3 days
* Provide a more specific help line for PLIP installs, reminding themurray2001-12-101-0/+5
| | | | | | | user that they must provide the peer's IP address in the 'extra options to ifconfig' box. PR: misc/21273
* Add the Bulgarian BDS and Phonetic keymaps.roam2001-12-104-2/+8
| | | | | | Reviewed by: jhb Approved by: jhb, silence on -qa MFC after: 1 week
* WARNS=2 cleanup.mikeh2001-12-102-58/+70
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* WARNS=2 cleanup.mikeh2001-12-102-12/+17
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* WARNS=2 cleanup.mikeh2001-12-102-33/+35
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* An XFree86 install should not depend on any compat libs any longer.obrien2001-12-101-9/+0
| | | | | | (1) We don't need compat3x and compat4x as we build the bits on the proper release now (vs. getting them from the XFree people). (2) We handle the compat2x needs thru proper port dependancies now.
* We do have a compat4x dist for Alpha.obrien2001-12-101-1/+1
|
* Update the list of public NTP servers fromobrien2001-12-102-64/+820
| | | | | | | | | http://www.eecis.udel.edu/~mills/ntp/clock2.htm Also remove any Stratum 1 servers and only include Stratum 2 and higher servers. PR: 32586 Submitted by: Arnaud Launay <asl@launay.org>
* cleanupdillon2001-12-104-18/+18
|
* Add auto-fill-on-delete. When deleting an 'A'uto created partitiondillon2001-12-094-66/+94
| | | | | | | | | | | | | | | | sysinstall will automatically expand the previous partition to take up the freed up space. So you can 'D'elete /home and /usr will get the combined space, or you can 'D'elete /tmp and /var will get the combined space. This gives the user, developer, or lay person a huge amount of flexibility in constructing partitions from an 'A'uto base. It takes only 3 or 4 keystrokes to achieve virtually any combination of having or not having a /tmp and/or /home after doing an 'A'uto create. Change 'A'uto creation of /var/tmp to 'A'uto creation /tmp, which should be less controversial. MFC after: 6 days
* WARNS=2 cleanup.mikeh2001-12-092-1/+3
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* Turn on WARNS=2, no code fixes needed.mikeh2001-12-091-0/+2
| | | | | Submitted by: Maxime Henrion <mux@qualys.com> MFC after: 2 weeks
* Don't ignore SIGINT and SIGQUIT. The comment said "Ignore SIGINTiedowse2001-12-091-4/+0
| | | | | | | | | and SIGQUIT during shutdown", but rpc.umntall is also run at boot time, so ignoring these signals is a really bad idea: it makes it impossible to ^C the process as it waits for a server response. I can't see any reason to block these signals during shutdown either. MFC after: 3 days
* style(9) cleanup: spaces -> tabs.mikeh2001-12-091-94/+95
| | | | MFC after: 2 weeks
* WARNS=2 cleanup.mikeh2001-12-092-10/+20
| | | | | PR: bin/32646 MFC after: 2 weeks
* Cleanup sysinstall's 'A'uto partitioning mode to provide more reasonabledillon2001-12-096-244/+602
| | | | | | | | | | | | | | defaults both in regards to the size of the partitions that are created and in regards to safety and functional separation. Still TODO: extend the previous partition to cover a deleted partition if the previous partiton was auto-created, and supply some sort of solution for /tmp. Reviewed by: Just about everyone Approved by: Nobody except maybe my pet mouse fred Obtained from: God, so complain to HIM MFC after: 1 week
* WARNS=2 cleanup.mikeh2001-12-092-15/+41
| | | | | PR: bin/32567 MFC after: 2 weeks
* WARNS=2 cleanup and fix potential unitialized variable bug.mikeh2001-12-092-4/+13
| | | | | PR: bin/32567 MFC after: 2 weeks
* WARNS=2 cleanup.mikeh2001-12-093-3/+16
| | | | | PR: bin/32567 MFC after: 2 weeks
OpenPOWER on IntegriCloud