summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Allow GCC to recognize -fformat-extensions flag.kan2004-07-292-0/+11
|
* Fix ACPI floppy enumeration for three types of divergent behavior.njl2004-07-281-40/+90
| | | | | | | | | | | | | | | | | * Some systems have _FDE and child floppy devices, but no _FDI. This seems to be compatible with the standard. Don't error out if there is no _FDI. Instead, continue on to the next device. The normal fd probe will take care of this device. * Some systems have _FDE but no child devices in AML. For these, add a second pass that compares the results of _FDE to the presence of devices. If not present, add the missing device. * Some BIOS authors didn't read the spec. They use tape drive values for all fdc(4) devices. Since this isn't grossly incompatible with the required boolean value, use them. They also define the _FDE items as a package instead of buffer. Regenerate the buffer from the package if it is present. Tested by: tjr, marcel
* Disable memory locking that could keep watchdogd from deadlocking itselfgreen2004-07-281-4/+0
| | | | | | if the swap subsystem failed. Requested by: phk
* Move a relic to its correct location(s): Put nfs diskless initializationphk2004-07-286-98/+17
| | | | calls with the code they call. (Yet another example of mindless copy&paste).
* Leaving the '.Pp' before '.Sh' is a style bug. This should have beentrhodes2004-07-281-1/+0
| | | | removed in my previous commit.
* Remove buggy (root filesystems may not have cdev) and pointlessphk2004-07-281-8/+3
| | | | customization of an error message.
* Remove global variable rootdevs and rootvp, they are unused as such.phk2004-07-2811-15/+14
| | | | | | | | Add local rootvp variables as needed. Remove checks for miniroot's in the swappartition. We never did that and most of the filesystems could never be used for that, but it had still been copy&pasted all over the place.
* Correct a very old error in both vm_object_madvise() (originating inalc2004-07-281-2/+2
| | | | | | | | | | | | vm/vm_object.c revision 1.88) and vm_object_sync() (originating in vm/vm_map.c revision 1.36): When descending a chain of backing objects, both use the wrong object's backing offset. Consequently, both may operate on the wrong pages. Quoting Matt, "This could be responsible for all of the sporatic madvise oddness that has been reported over the years." Reviewed by: Matt Dillon
* Print link level address on vlan interfaces using ether_ntoa(), to makeglebius2004-07-281-0/+1
| | | | | | | | | | output on bare ethernet and vlan interfaces the same. PR: bin/69674 Submitted by: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> Reviewed by: ru Approved by: julian (mentor) MFC after: 1 week
* Remove the ERRORS section in favor of a DIAGNOSTICS section.trhodes2004-07-282-29/+27
| | | | Requested by: ru
* No need to include if_var.h.harti2004-07-281-1/+0
|
* Get rid of several unneeded includes (if.h, if_var.h, if_mib.h).harti2004-07-281-3/+0
|
* Use the length modifier 'll' instead of 'q' to print long longs.stefanf2004-07-286-12/+12
|
* Document incorrect handling of multibyte characters due to limitationstjr2004-07-281-1/+6
| | | | of sh(1).
* Wrap the supported adapters list into an .Sh HARDWARE section.trhodes2004-07-281-13/+51
| | | | | Use a list to make reading the list easier on the eyes. Add cardbus(4) and pccard(4) to the SEE ALSO section.
* Remove an empty default: case to please GCC 3.4.2.mux2004-07-281-2/+0
|
* Set fpu context flags to known values, zero is illegal.davidxu2004-07-281-0/+2
|
* Disallow a particular kind of port theft described by the following scenario:yar2004-07-282-15/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Alice is too lazy to write a server application in PF-independent manner. Therefore she knocks up the server using PF_INET6 only and allows the IPv6 socket to accept mapped IPv4 as well. An evil hacker known on IRC as cheshire_cat has an account in the same system. He starts a process listening on the same port as used by Alice's server, but in PF_INET. As a consequence, cheshire_cat will distract all IPv4 traffic supposed to go to Alice's server. Such sort of port theft was initially enabled by copying the code that implemented the RFC 2553 semantics on IPv4/6 sockets (see inet6(4)) for the implied case of the same owner for both connections. After this change, the above scenario will be impossible. In the same setting, the user who attempts to start his server last will get EADDRINUSE. Of course, using IPv4 mapped to IPv6 leads to security complications in the first place, but there is no reason to make it even more unsafe. This change doesn't apply to KAME since it affects a FreeBSD-specific part of the code. It doesn't modify the out-of-box behaviour of the TCP/IP stack either as long as mapping IPv4 to IPv6 is off by default. MFC after: 1 month
* ANSIfy and constify; this now builds with GCC 3.4.des2004-07-281-22/+19
|
* Remove (at least temporarily) the check that prevents us from includingmux2004-07-281-4/+0
| | | | | | | | | this file from userland. Since we export struct ifnet to userland, and that struct ifnet now contains a struct task, userland needs to know what struct task looks like. We need to consider having a pointer to a struct task here instead and forward declare struct task in the !_KERNEL case.
* Damage control. Correcly advance symtab and strtab pointers, notkan2004-07-281-2/+2
| | | | | | table length values. Spotted by: iedowse
* Avoid casts as lvalues.kan2004-07-282-5/+8
|
* Downgrade WARNS level to more tolerable value. Attempt to fixkan2004-07-287-14/+16
| | | | casts as lvalue usage whenever possible.
* Move __iniline function definition before its first usage in the file.kan2004-07-281-8/+7
|
* Temporarily disable kernbb utility. It has to learn about new gcov datakan2004-07-281-1/+0
| | | | format first.
* Remove local malloc prototypes, which are incorrect and conflict withkan2004-07-284-7/+0
| | | | both GCC builtin and system declared ones.
* Do not predeclare __inline functions, this makes no sense and generateskan2004-07-281-2/+2
| | | | a warning with gcc 3.4.x.
* Introduce SYSCTL_CHILDREN_SET macro which can be used in place ofkan2004-07-281-0/+2
| | | | cast as a value.
* Emply __used attribute to prevent compiler from removing unreferencedkan2004-07-281-1/+1
| | | | | | static symbols. This wasn't a problem with previous GCC releases, but unit-at-a-time mode of GCC 3.4.2 prevents linker set components from being emitted at all.
* Introduce __used attribute which serves as logical conuterpart ofkan2004-07-281-0/+2
| | | | preexisting __unused.
* Introduce SLOT_SET macro and use it in place of casts as lvalues.kan2004-07-283-12/+16
|
* Avoid casts as lvalues.kan2004-07-2811-24/+37
|
* Avoid casts as lvalues. Declare local variable as u_char * instead ofkan2004-07-281-6/+6
| | | | declaring it as u_short * and casting it back to uchar * all over the place.
* Initialize ; variable eraly to shut up GCC warning.kan2004-07-281-0/+1
|
* Forced commit to note that prevois commit has nothing to do with castskan2004-07-280-0/+0
| | | | as lvalues. I meant to replace a bogus function cast with less bogus one.
* Avoid casts as lvalues.kan2004-07-283-7/+6
|
* Avoid using casts as lvalues. Introduce DIP_SET macro which sets properkan2004-07-2811-109/+120
| | | | | inode field based on UFS version. Use DIP ro read values and DIP_SET to modify them throughout FFS code base.
* Avoid casts as lvalues. While here, avoid storing 32bit quantities inkan2004-07-281-6/+6
| | | | 16bit locations.
* Use P_SINGLE_EXIT to check single-threading case, P_WEXIT is not for thatdavidxu2004-07-281-1/+1
| | | | purpose.
* Avoid casts as lvalues.kan2004-07-283-4/+4
|
* Avoid casts as lvalues.kan2004-07-286-17/+33
|
* Make __packed attribute apply to structs themselves, not their typedefs.kan2004-07-281-14/+17
| | | | GCC 3.4.2 issues warning about that.
* Name non-physical devices.ps2004-07-281-1/+1
|
* Initialize s variable early to shut up GCC warnings.kan2004-07-284-14/+31
| | | | | | | Do not declare inline functions without body as this is useless in general and generates a warning with GCC 3.4.x. Glanced over by: dhartmei
* Allow for aggressive function inlining. This might have to be fine-tunedkan2004-07-281-1/+3
| | | | later.
* Avoid casts as lvalues.kan2004-07-282-2/+2
|
* Define our own memcpy here instead of relying on GCC to provide one.kan2004-07-282-8/+0
|
* Downgrade WARNS level until GCC 3.4.2 warning are fixed.kan2004-07-282-1/+2
|
* Avoid casts as lvalues.kan2004-07-282-4/+11
|
* Downgrade WARNS level until GCC 3.4.2 warning have been fixed.kan2004-07-281-1/+1
|
OpenPOWER on IntegriCloud