summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add a new DDB(4) facility, output capture. Input and output from DDB may berwatson2007-12-257-0/+330
| | | | | | | | | | | | | captured to a memory buffer for later inspection using sysctl(8), or in the future, to a textdump. A new DDB command, "capture", is added, which accepts arguments "on", "off", "reset", and "status". A new DDB sysctl tree, debug.ddb.capture, is added, which can be used to resize the capture buffer and extract buffer contents. MFC after: 3 months
* "vt" doesn't refer to any existing device anymore. Remove it.wkoszek2007-12-252-3/+1
| | | | | Reviewed by: cognet@ (mentor) Approved by: cognet@ (mentor)
* Just copy long months names to alternative.ache2007-12-251-6/+6
| | | | Alternative does not means ASCIIsizing of months names.
* Add reference to mnemonic char namesache2007-12-251-0/+1
|
* Just copy long months names to (alternative).ache2007-12-251-6/+6
| | | | Alternative means another form and not ASCIIsizing of month names.
* Rewrite kern.console handling in sbuf(9). My intention is to leavewkoszek2007-12-251-21/+16
| | | | | | | | kern.console format as is. Thus, no difference in output format should appear after this commit. Reviewed by: cognet@ (mentor) Approved by: cognet@ (mentor)
* Implement Turkish localeache2007-12-252-2/+50
| | | | Submitted by: Ismail YENIGUL <ismail.yenigul@endersys.com.tr>
* Mention support for the 5722 driver in bge.4 as well.remko2007-12-251-3/+3
|
* Add support for the BMC5722.remko2007-12-252-0/+2
| | | | | Reported by: Chris Shenton <chris at shenton dot org> on current@ Approved by: imp (mentor)
* Bump __FreeBSD_version to 800007 to reflect kdb_enter change.rwatson2007-12-251-1/+1
|
* Add a new kernel startup event for DDB services, which will include DDBrwatson2007-12-251-0/+1
| | | | output capture, scripting, and textdumps.
* Add a new privilage category for DDB(4), and add PRIV_DDB_CAPTURE torwatson2007-12-251-1/+6
| | | | control access to the DDB capture buffer.
* Add a new 'why' argument to kdb_enter(), and a set of constants to userwatson2007-12-2533-48/+95
| | | | | | | | | for that argument. This will allow DDB to detect the broad category of reason why the debugger has been entered, which it can use for the purposes of deciding which DDB script to run. Assign approximate why values to all current consumers of the kdb_enter() interface.
* Typos corrected.schweikh2007-12-251-2/+2
|
* Rename "mbuf_jumbo_pagesize" to "mbuf_jumbo_page". It makes it aligned correctlywkoszek2007-12-251-1/+1
| | | | | | | | | within ddb(4) and in the vmstat(8) output. This change requires netstat(8) to be recompiled. Reviewed by: rwatson@ Tested by: make LINT
* Use __FBSDID() in the kernel BPF implementation.rwatson2007-12-252-4/+6
| | | | MFC after: 3 days
* Change "audit_pipe_preselect" to "audit_pipe_presel" to make it printwkoszek2007-12-251-1/+1
| | | | | | with proper alignment in ddb(4) and vmstat(8). Reviewed by: rwatson@
* Workaround p->numbytes overflow, which can result in infinite loop insideoleg2007-12-251-7/+22
| | | | | | dummynet module (prerequisite is using queues with "fat" pipe). PR: kern/113548
* 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).
* Add the ability to clean up all shared memory segments which areedwin2007-12-257-214/+468
| | | | | | | | | | | | | | | | | | | | | unused in one go. From the original PR: I've observed that linux apps running under the linuxulator have a habit of leaving behind shared memory segments which are unused, but which eventually cause the system to run out of free segments and these apps will stop working. ipcrm(1) currently only allows removal of unused message queues, shared memory segments and semaphores on an individual basis, or those having a matching (non-zero) key. However it would often be convenient to just do a complete cleanup of everything, usually as root. PR: bin/118292 Submitted by: Callum Gibson <callumgibson@optusnet.com.au> Not reviewed by: grog@ Approved by: grog@
* When copying multiple files to a directory, make sure that a properedwin2007-12-251-1/+1
| | | | | | | | | warning is given when the directory doesn't exist. PR: bin/50656 Submitted by: Edwin Groothuis <edwin@mavetju.org> Approved by: grog@ Not reviewed by: grog@
* Add sysctl mibs for _TSP, _TC1 and _TC2 which is user overridableume2007-12-241-0/+40
| | | | | | | | but is blocked on user_override mib. Not a few people want to use a passive cooling without their ACPI BIOS support. Reviewed by: njl
* Move the check for the snp device being already attached after thekib2007-12-241-11/+6
| | | | | | | | | | | | | | | | fget() call, that is sleeping point, and possibly dropping Giant. The snp_target == NULL implies the snp_tty == NULL. Remove the code that is put under snp_target == NULL and snp_tty != NULL clause. In snpclose(), do the snp_detach() before scheduling the snp device destruction. Otherwise, after the return from snpclose(), the snp device is already removed from the snp_list, but tty is still in snooped state. Any attempt to do i/o on such tty cause panic because ttytosnp() returns NULL. Tested by: Peter Holm MFC after: 1 week
* Add Turkish collateache2007-12-243-2/+213
| | | | | PR: 118976 Submitted by: Ismail YENIGUL <ismail.yenigul@endersys.com.tr>
* Various fixes:marcel2007-12-241-41/+25
| | | | | | | | | | | | | | | o BSD disklabels have relative offsets. Even for the BSD in MBR slice setup, except when the mbroffset ioctl is supported. Since we don't support that ioctl, bsdlabel(8) expects relative offsets. So, when reading an existing disklabel, correct for disklabels that mistakenly have the mbroffset offsets. o Don't take the geometry seriously, because it's untrustworthy. We do expect the numbers to be within range. This means that the secperunit field will not be computed from secpercyl and ncyls, but simply is the mediasize in sectors. o Don't enforce partitions to be aligned to track boundaries. The default label, constructed by bsdlabel(8), puts partition a at offset BBSIZE bytes, which commonly means sector 16.
* 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...
* - Fix a typo in comments.stas2007-12-231-1/+1
| | | | | MFC after: 1 week Approved by: cognet
* On Christmas lights.wilko2007-12-231-0/+11
|
* - remove code from oroginal file, which is not required on BWCT boardsticso2007-12-231-52/+86
| | | | | | | - Be more chatty on startup, since we have enough code space on AT91RM9200 - init DS1672 charging - init USART GPIO
* BWCT boards uses two different SPI flash chipsticso2007-12-231-2/+3
| | | | check for both status codes
* Remove trailing whitespace from lines in BPF.rwatson2007-12-232-7/+7
| | | | MFC after: 3 days
* Revert previous commit and fix OpenPAM issue properly.des2007-12-221-6/+6
|
* Add usage example:mav2007-12-221-0/+11
| | | | | Limit outgoing data rate over fxp0 Ethernet interface to 20Mbit/s and incoming packet rate to 5000pps.
* When IPSEC fails to allocate policy state for an inpcb, and MAC is in use,rwatson2007-12-221-1/+5
| | | | | | | | free the MAC label on the inpcb before freeing the inpcb. MFC after: 3 days Submitted by: tanyong <tanyong at ercist dot iscas dot ac dot cn>, zhouzhouyi
* give thread0 the tid 100000 and bumpt the others to start at 100001julian2007-12-222-1/+3
| | | | MFC after: 1 week
* Make SCHED_ULE buildable with gcc3.wkoszek2007-12-211-17/+17
| | | | | Reviewed by: cognet (mentor), jeffr Approved by: cognet (mentor), jeffr
* - Remove incomplete sentence fragmentgabor2007-12-211-2/+0
| | | | | | PR: docs/117451 Submitted by: Warren Block <wblock@wonkity.com> MFC after: 3 days
* 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
* - Document PORT_DBDIRgabor2007-12-211-0/+11
| | | | | PR: docs/114731 Submitted by: Matthew Seaman <m.seaman@infracaninophile.co.uk>
* - Document icase variable of make search, which can be used to controlgabor2007-12-211-2/+12
| | | | | | | case-sensitivity PR: docs/117593 Submitted by: Nikolay Bachiyski <nbachiyski@developer.bg>
* Clean up some of the pts(4) vs pty(4) stuff in grantpt(3) and friends:jhb2007-12-211-22/+23
| | | | | | | | | | - Use PTY* for all pty(4) related constants. - Use PTMX* for all pts(4) related constants. - Consistently use _PATH_DEV PTMX rather than "/dev/ptmx". - Revert 1.7 and properly fix it by using the correct prefix string for pts(4) masters. MFC after: 3 days
* 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>
* More properly handle links who only have 1 valid IRQ in their bitmask. Thejhb2007-12-211-13/+12
| | | | | | | | | | | | | | | | | | | | | old code special cased them too early which caused a few differences for these sort of links relative to other PCI links: - They were always re-routed via the BIOS call instead of assuming that they were already routed if the BIOS had programmed the IRQ into a matching device during POST. - If the BIOS did route that link to a different IRQ that was marked as invalid, we trusted the $PIR table rather than the BIOS IRQ. This change moves the special casing for "unique IRQ" links to only take that into account when picking an IRQ for an unrouted link so that these links will now not be routed if the BIOS appears to have routed it already (some BIOSen have problems with that) and so that if the BIOS uses a different IRQ than the $PIR, we trust the BIOS routing instead (this is what we do for all other links as well). Reported by: Bruce Walter walter of fortean com MFC after: 1 week
* Adjust for OpenPAM Hydrangea.des2007-12-214-7/+8
|
* This commit was generated by cvs2svn to compensate for changes in r174835,des2007-12-215-3445/+0
| | | | which included commits to RCS files with non-trunk default branches.
* This commit was generated by cvs2svn to compensate for changes in r174832,des2007-12-21157-8893/+9922
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Vendor import of OpenPAM Hydrangea.des2007-12-21157-8893/+9922
| |
* | usbhidctl appears to not report features and write size correctlyimp2007-12-211-4/+4
| | | | | | | | | | | | | | | | This turns out to be due to an argument botch for hid_report_size. The PR contained patches to fix the argument botch. Submitted by: Maurice Castro PR: usb/118915
* | Update the comment describing vm_phys_unfree_page().alc2007-12-211-1/+3
| |
* | Minor initialization change to not trigger bogus gcc warning aboutimp2007-12-211-1/+1
| | | | | | | | passing literal strings to the constructors of string.
OpenPOWER on IntegriCloud