summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Use intmax_t instead of long when casting time_t.jkim2008-03-071-3/+4
| | | | | Suggested by: mlaier Tested with: make universe
* Merge revisions 1.10 and 1.11 from DragonFly:delphij2008-03-071-68/+61
| | | | | | | | | | | | | | | | | | | | | - Use real getopt() handling instead of the hand-rolled and IOCCC-worthy "Micro getopt()" macros, plus clean up to the option handling code: * Sort the options in the switch statement; * Plug piddling memory leaks when processing repeated options by freeing strings before allocating them for a second time; * Die with a fatal error if the requested report file cannot be opened for appending; * Don't call init() before usage() (to prevent the usage message being mangled by changes to the terminal settings;) - Clean up the usage message, both in usage() and in the main program comment, both stylistically (sort and combine options) and for accuracy (following the manual page, make note of the -s and -S flags, and use the term 'send' instead of 'say' to reduce confusion (SAY is the name of a command for output to the user, not the connection.)) Obtained from: DragonFly
* Change auditon(2) so that if somebody supplies an invalid command, itcsjp2008-03-061-0/+3
| | | | | | | | returns EINVAL. Right now we return 0 or success for invalid commands, which could be quite problematic in certain conditions. MFC after: 1 week Discussed with: rwatson
* MFi386:cognet2008-03-061-1/+3
| | | | | | | | | | | | revision 1.6 date: 2004/08/21 18:50:34; author: alc; state: Exp; lines: +3 -1 Properly free the temporary sf_buf in uiomove_fromphys() if a copyin or copyout fails. Obtained from: DragonFlyBSD Spotted out by: Mark Tinguely MFC After: 3 days
* Remove unused pv_list_count from the vm_page, and pm_count from the structcognet2008-03-062-6/+0
| | | | | | pmap. Submitted by: Mark Tinguely
* MFP4:piso2008-03-067-77/+67
| | | | | | restrict the utilization of direct pointers to the content of ip packet. These modifications are functionally nop()s thus can be merged with no side effects.
* Style tweak to the 5722 chipid to match the rest of this file.jhb2008-03-061-1/+1
|
* In the PROBE_KEYBOARD case, always enable multiple consoles and set thejhb2008-03-061-2/+4
| | | | | | serial console as the primary console if the keyboard probe fails. MFC after: 1 week
* Flesh out support for the BCM5722 by recognizing the phy on the 5722 andjhb2008-03-064-1/+5
| | | | | | | the specific ASIC revision. MFC after: 1 week Obtained from: OpenBSD (mii/phy bits)
* - Add a missing unlock to cpuset_setaffinity(CPU_LEVEL_CPUSET, CPU_WHICH_PID)jeff2008-03-061-0/+1
| | | | Found by: gallatin
* Improve EtherIP interaction with the bridgethompsa2008-03-061-2/+30
| | | | | | | | - Set M_BCAST|M_MCAST for incoming frames - Send the frame to a local interface if the bridge returns the mbuf Submitted by: Eugene Grosbein Tested by: Boris Kochergin
* Move the PCPU_MD_FIELDS last in struct pcpu. While this header ismarcel2008-03-061-1/+11
| | | | | | | | | | | | private to the kernel, some ports define _KERNEL and include this header. While arguably this is wrong, it's also reality. By having the MD fields last, architectures that have CPU-specific variations of PCPU_MD_FIELDS will at least have the MI fields at a constant offset. Of course, having all MI fields first helps kernel debugging as well, so this is not a change without some benefits to us. This change does not result in an ABI breakage, because this header is not part of the ABI. Recompilation of lsof is required though :-)
* Add a catch-all for PCPU_MD_FIELDS. While we expect this to bemarcel2008-03-061-0/+7
| | | | | | | | | used in the kernel only (by virtue of checking for _KERNEL), ports like lsof (part of gtop) cheat. It sets _KERNEL, but does not set either AIM or E500. As such, PCPU_MD_FIELDS didn't get defined and the build broke. The catch-all is to define PCPU_MD_FIELDS with a dummy integer when at the end of line we ended up without a definition for it.
* The check for errors from the mount command did not work as intendedmtm2008-03-062-2/+8
| | | | | | | | because another command (echo) is executed between the mount command and the check. Reported by: Sergey Baturov <sergey@toor.org.ru> MFC after: 2 weeks
* The rarpd(8) daemon must be instructed to start on all interfaces or amtm2008-03-061-1/+1
| | | | | | | | | specific one. Instruct it to listen on all interfaces so that enabling it in rc.conf(5) works "out of the box." PR: conf/121406 Submited by: trasz MFC after: 1 week
* When redrawing an input line, count backspaces to get to the beginning ofrwatson2008-03-061-1/+1
| | | | | | | | | | | the input field from the current cursor location, rather than the end of the input line, as the cursor may not be at the end of the line. Otherwise, we may overshoot, overwriting a bit of the previous line and failing to fully overwrite the current line. MFC after: 3 days PR: 119079 Submitted by: Michael Plass <mfp49_freebsd@plass-family.net>
* Added missing BSD license text to the cmx.4 manpage.rink2008-03-061-0/+25
| | | | Noticed by: brueffer
* Commit cmx(4), a driver for Omnikey CardMan 4040 PCMCIA smartcard readers.rink2008-03-0611-0/+1101
| | | | | | | | PR: kern/114582 Submitted by: Daniel Roethlisberger <daniel@roe.ch> Reviewed by: imp, myself Tested by: johans, myself MFC after: 2 weeks
* The breakage from increased warns has been fixed, back out my back outimp2008-03-061-1/+1
|
* Fix a bug when calculating remnant size.davidxu2008-03-061-1/+1
|
* Cast time_t to long to mute tinderbox build failure.jkim2008-03-061-2/+2
|
* This breaks the arm build, back it out until that's fixedimp2008-03-061-1/+1
|
* Don't report death event to debugger if it is a forced exit.davidxu2008-03-061-1/+1
|
* Restore code setting new thread's scheduler parameters, I was thinkingdavidxu2008-03-061-15/+11
| | | | | | that there might be starvations, but because we have already locked the thread, the cpuset settings will always be done before the new thread does real-world work.
* Nuke local jumbo allocator and switch to use of UMA backed pageyongari2008-03-063-185/+6
| | | | | | | | allocator for jumbo frame. Also remove unneeded jlist lock which is no longer required to protect jumbo buffers. With these changes jumbo frame performance of nfe(4) was slightly increased and users should not encounter jumbo buffer allocation failure anymore.
* Add an option to register DUN (Dial-Up Networking) service on the sameemax2008-03-062-3/+43
| | | | | | | RFCOMM channel if needed. There is really no good reason to not to support this. AT-command exchange can be faked with chat script in ppp.conf. MFC after: 1 week
* Mark moused(8) WARNS=6 clean.jkim2008-03-061-0/+2
|
* Fix compiler warnings and style(9) bugs.jkim2008-03-061-192/+201
|
* Prefer clock_gettime(2) over gettimeofday(2) and use CLOCK_MONOTONIC_FAST.jkim2008-03-061-63/+82
| | | | It is only used to track elapsed time and it does not have to be precise.
* Add an alias for glabel(8).delphij2008-03-051-0/+1
|
* Make it possible to build glabel into rescue geom(8) utility.delphij2008-03-053-5/+18
| | | | | Ok'ed by: marcel No objection: -current@
* Use calloc().delphij2008-03-051-2/+1
|
* - Add PHY ID for BCM5709C 1000Base-T controllers.davidch2008-03-052-2/+6
| | | | MFC after: 1 week
* Increase default queue items allocation limit from 512 to 4096 itemsmav2008-03-051-2/+16
| | | | | | | | | to avoid terrible unpredicted effects for netgraph operation of their exhaustion while allocating control messages. Add separate configurable 512 items limit for data items allocation for DoS/overload protection. Discussed with: julian
* For users of FreeBSD <= 6.2 we recommend during the x.org 7.x upgradekris2008-03-052-1/+19
| | | | | | | | | | | | | | | | | | | | | that they add X11BASE=${LOCALBASE} to /etc/make.conf since X11BASE was hard-wired to the now-wrong location in old releases. However, both X11BASE and LOCALBASE have moved out of scope of src/ into ports/ now, which causes problems for upgraded users who have old make.conf files still containing the above setting. X11BASE becomes null and we instruct ssh and sshd to look for xauth in /bin/xauth where it is unlikely to be found. Instead, provide a copy of the default LOCALBASE?=/usr/local setting here. We also have to deal with the case where the user only overrides LOCALBASE and doesn't set an explicit X11BASE (in ports it will be set implicitly but not here), which will also move the location of xauth. MFC after: 3 days Reported by: rwatson
* The non-POSIX environment variable MAKE was supersededyar2008-03-051-1/+1
| | | | | | by MAKEFLAGS ages ago, so don't mention it in comments. Tested with: cmp(1)
* Don't forget to set MAKEFLAGS in the childs' environmentyar2008-03-052-31/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from the .MAKEFLAGS global variable even if it's empty or unset. This means setting MAKEFLAGS to just an empty string in the latter case. If not doing so, make(1) behaved inconsistently WRT MAKEFLAGS. In particular, it would let a `-f foo' option down to sub-makes if .MAKEFLAGS was unset. E.g., env MAKEFLAGS="-f mymakefile" make would pass `-f mymakefile' down to sub-makes via their environment (unless mymakefile added something to .MAKEFLAGS). But any additional options appearing would change this behaviour to not passing `-f mymakefile' to sub-makes, as in: env MAKEFLAGS="-f mymakefile" make -D DUMMY or env MAKEFLAGS="-f mymakefile -D DUMMY" make (unless mymakefile cleared .MAKEFLAGS). Also make(1) would leave MAKEFLAGS at its initial value if the makefile set .MAKEFLAGS to an empty value. I.e., it was impossible to override MAKEFLAGS with an empty value. (Note well that makefiles are not to touch MAKEFLAGS directly, they alter .MAKEFLAGS instead. So make(1) can filter out things such as -f when copying MAKEFLAGS to .MAKEFLAGS at startup. Direct modifications to MAKEFLAGS just go nowhere.) While the original intentions of the BSD make authors are somewhat unclear here, the bug proves that NOT passing -f options down is the settled behaviour because the opposite behaviour is totally unreliable in the presence of any other options. In addition, not passing down -f's found in the environment is consistent with doing so WRT the command line. Update the manpage accordingly and make the whole description of MAKEFLAGS and .MAKEFLAGS more consistent as this change indeed brings more consistency into the reliable behaviour of make(1). Submitted by: ru (main.c) Tested with: make world
* o We don't have to keep track of the PIC, nor do we have to make suremarcel2008-03-051-28/+39
| | | | | | | it's probed first. The PowerPC platform code deals with everything. As such, probe devices in order of their location in the memory map. o Refactor the ocpbus_alloc_resource for readability and make sure we set the RID in the resource as per the new convention.
* Use the new command file feature of ddb(8) to support setting ddb(4)brooks2008-03-056-2/+64
| | | | | | | | | scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps
* mdoc changes to make this manpage consistent with our other section 4 manpages.brueffer2008-03-051-8/+19
|
* Add the ability to read a file of commands to ddb(8) modeled after thebrooks2008-03-052-5/+81
| | | | feature in ipfw(8).
* o Various fixes related to PCI Express:marcel2008-03-051-37/+65
| | | | | | | | | | | | | | | | | | | | | | | | | - Even for the PCI Express host controller we need to use bus 0 for configuration space accesses to devices directly on the host controller's bus. - Pass the maximum number of slots to pci_ocp_init() because the caller knows how many slots the bus has. Previously a PCI or PCI-X bus underneath a PCI Express host controller would not be enumerated properly. o Pull the interrupt routing logic out of pci_ocp_init() and into its own function. The logic is not quite right and is expected to be a bit more complex. o Fix/add support for PCI domains. The PCI domain is the unit number as per other PCI host controller drivers. As such, we can use logical bus numbers again and don't have to guarantee globally unique bus numbers. Remove pci_ocp_busnr. Return the highest bus number ito the caller of pci_ocp_init() now that we don't have a global variable anymore. o BAR programming fixes: - Non-type0 headers have at most 1 BAR, not 0. - First write ~0 to the BAR in question and then read back its size. Obtained from: Juniper Networks (mostly)
* Initialize mnt_stat.f_iosize before autostarting UFS1 extattrs.kib2008-03-051-0/+1
| | | | | | | | | | | | | | It is normally initialized by ffs_statfs() after ffs_mount finished. The extattr autostart code calls the ufs_lookup(), that uses value above to iterate over the directory blocks, see bmask initialization in the ufs_lookup() and ufsdirhash. Having the filesystem with root directory spanning more then one block would result in reading a random kernel memory. PR: kern/120781 Test case provided by: rwatson MFC after: 1 week
* Oops, I accidently concatenated uslcom.[c4] multiple times before therink2008-03-052-2012/+0
| | | | | | commit :-/ Quickly fix before things get broken... Pointyhat to: me
* Import uslcom(4) from OpenBSD - this is a driver for Silicon Laboratoriesrink2008-03-0510-0/+2560
| | | | | | | | CP2101/CP2102 based USB serial adapters. Reviewed by: imp, emaste Obtained from: OpenBSD MFC after: 2 weeks
* Add info about few missing GEOM classes that use geom(8).pjd2008-03-051-1/+13
|
* Change float_t and double_t to long double on i386. All floating pointbde2008-03-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | expressions on i386 are evaluated in the range of the long double type, so this is wrong in a different but hopefully less worse way than before. Since expressions are evaluated in long double registers, there is no runtime cost to using long double instead of double to declare intermediate values (except in cases where this avoids compiler bugs), and by careful use of float_t or double_t it is possible to avoid some of the compiler bugs in this area, provided these types are declared as long double. I was going to change float.h to be less broken and more usable in combination with the change here (in particular, it is more necessary to know the effective number of bits in a double_t when double_t != double, since DBL_MANT_DIG no longer logically gives this, and LDBL_MANT_DIG doesn't give it either with FreeBSD-i386's default rounding precision. However, this was too hard for now. In particular, LDBL_MANT_DIG is used a lot in libm, so it cannot be changed. One thing that is completely broken now is LDBL_MAX. This may have sort of worked when it was changed from DBL_MAX in 2002 (adding 0 to it at runtime gave +Inf, but you could at least compare with it), but starting with gcc-3.3.1 in 2003, it is always +Inf due to evaluating it at compile time in the default rounding precision.
* Oops, back out previous commit since it was to the wrong file.bde2008-03-051-5/+4
|
* Change float_t and double_t to long double on i386. All floating pointbde2008-03-051-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | expressions on i386 are evaluated in the range of the long double type, so this is wrong in a different but hopefully less worse way than before. Since expressions are evaluated in long double registers, there is no runtime cost to using long double instead of double to declare intermediate values (except in cases where this avoids compiler bugs), and by careful use of float_t or double_t it is possible to avoid some of the compiler bugs in this area, provided these types are declared as long double. I was going to change float.h to be less broken and more usable in combination with the change here (in particular, it is more necessary to know the effective number of bits in a double_t when double_t != double, since DBL_MANT_DIG no longer logically gives this, and LDBL_MANT_DIG doesn't give it either with FreeBSD-i386's default rounding precision. However, this was too hard for now. In particular, LDBL_MANT_DIG is used a lot in libm, so it cannot be changed. One thing that is completely broken now is LDBL_MAX. This may have sort of worked when it was changed from DBL_MAX in 2002 (adding 0 to it at runtime gave +Inf, but you could at least compare with it), but starting with gcc-3.3.1 in 2003, it is always +Inf due to evaluating it at compile time in the default rounding precision.
* Expand the nfs_opts array to include all possible stringrodrigc2008-03-051-1/+4
| | | | | | | | | | | mount options that mount_nfs could pass down, if it passed down string mount options. Right now, mount_nfs jut passes down a single mount option named "nfs_args" with a fully initialized 'struct nfs_args'. In future commits, we will add code to the kernel for parsing stringified NFS mount options, so that we can convert mount_nfs to pass string options from userspace to kernel, instead of an initialized struct nfs_args.
OpenPOWER on IntegriCloud