summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* While we're building kernels -g (ie, makeoptions DEBUG=-g), use -O as itobrien2005-01-181-1/+1
| | | | | | | | | | provides truer debugger stack traces. For those that want to stick with -O2 kernel builds, one should probably add -fno-optimize-sibling-calls so that each stack frame as a frame pointer. It is semi-promissed by the Release Engineers that when RELENG_6 is created we go back to -O2. Desired by: scottl, jhb
* Fix building for non-i386 platforms.sam2005-01-181-4/+7
| | | | Submitted by: Coleman Kane
* S_ISVTX -> S_ISTXT to reflect the code.trhodes2005-01-181-1/+1
|
* Correctly hide the command arguments.dds2005-01-171-15/+2
| | | | | PR: bin/76374 MFC after: 2 weeks
* If su(1) is run without an effective uid of 0, generate an error torwatson2005-01-171-3/+33
| | | | | | | | | the user indicating that su is not running setuid, which may help suggest to the user that it should be setuid, or should not be running from a file system mounted nosuid. Suggsted by: Ivan Voras <ivoras at fer dot hr> MFC after: 2 weeks
* s/ntpdate_command/ntpdate_program/ to match rc.conf(5) andceri2005-01-171-1/+1
| | | | | | | | | /etc/defaults/rc.conf. PR: conf/76188 Submitted by: Arne Wörner <arne_woerner at yahoo dot com> Approved by: murray MFC After: 7 days
* Cleanup:delphij2005-01-172-17/+18
| | | | | - Change signedness of nxtfld() to make msgs(1) WARNS=6 clean - Add several static's
* Oops... Remove the line leaked in the last commit which is notdelphij2005-01-171-1/+0
| | | | intended to be there...
* WARNS=6 cleanup:delphij2005-01-172-17/+18
| | | | | | | - Initialize everything in the struct array, not only the mentioned ones - Unconditionally initialize hs to 0 to avoid repeatly doing so - Cast to unsigned int when comparing to unsigned variables.
* WARNS=6 cleanup:delphij2005-01-172-4/+9
| | | | | | | - signed/unsigned conform. - Better initialization of nlist[]. I think we should have something like NLIST_NULL instead of the current (ugly) form...
* Bump WARNS=6 by adding const constraint and initialize the pointerdelphij2005-01-172-2/+3
| | | | to NULL at start.
* The submitter of bin/75786 turned out to not have removable interfaces,ceri2005-01-171-1/+1
| | | | | | | | | | and so the fix committed in r1.42 was not quite correct for the case where there are two or more DHCP consuming removable interfaces - dhclient must be restarted so that the other interfaces continue to function correctly. Approved by: murray MFC After: 7 days
* Minor bit of advice.phk2005-01-171-0/+4
|
* Add -frandom-seed=RepeatabilityConsideredGood to CFLAGS for building thiscperciva2005-01-171-0/+1
| | | | | | | | | | | | | library. As the value suggests, this allows the library to be built repeatably; without this flag, gcc uses a random value in its parsing. Since the random seed is only used when handling files which do not have any externally-visible symbols, this change is not needed for any other libraries in the FreeBSD base system. Discussed on: freebsd-arch (in early November) Approved by: kan MFC after: 1 week
* MFi386: fix a comment.ru2005-01-171-1/+1
|
* Fix a comment to match reality.ru2005-01-171-1/+1
|
* Rearrange the kninit calls for both directions of a pipe so thatsilby2005-01-171-1/+3
| | | | | | | | | they both happen before pipe backing allocation occurs. Previously, a pipe memory shortage would cause a panic due to a KNOTE call on an uninitialized si_note. Reported by: Peter Holm MFC after: 1 week
* Added the EXIT STATUS section where appropriate.ru2005-01-17143-161/+158
|
* Discontinue zero-length g_ctl arguments as "just give him this pointer"phk2005-01-171-6/+1
| | | | | transfers. The necessary context for calling copyin() isn't available anyway and automatic code-validation chokes on this.
* Go ahead and match on CIS3 and CIS4 strings as well. These are NULLimp2005-01-171-1/+14
| | | | | | | | | for the vast majority of our cards. However, they are critically needed to distinguish different fe based PC Cards (the FMV-182 from the 182A) which need to be treated differently (the ethernet address is loaded not from the standard CIS-based ethernet tuples, but from differing locations in attribute space based on the version string in CIS3. This should have no impact for other users of this function.
* Ups, misprint, change and => add.rik2005-01-161-1/+1
| | | | Submitted by: ru
* Document the new EXIT STATUS section.ru2005-01-161-1/+4
|
* Added the EXIT STATUS section.ru2005-01-161-2/+3
|
* Implement a custom print formatter (archive_string_vsprintf)kientzle2005-01-164-14/+90
| | | | | | | | | | | | | | for libarchive error messages. Mostly, this avoids a portability headache related to copying va_list arguments (some FreeBSD 5 platforms require va_copy; FreeBSD 4 doesn't support va_copy at all). It also dramatically reduces the size of libarchive for embedded applications: a minimal "untar" program using libarchive can now be under 64k statically linked (as opposed to ~100k using library *printf() functions). MFC after: 14 days
* Move -Wunused-parameter from WARNS level 3 level 4.obrien2005-01-161-2/+4
| | | | | | | Also break long lines -- note that the '\' must be up against the last character of a line to keep command-line spacing proper. Requested by: rwatson
* Fix a bug I introduced in 1.561 which has caused considerable filesystemphk2005-01-161-5/+5
| | | | | | | | | unhappiness lately. As far as I can tell, no files that have made it safely to disk have been endangered, but stuff in transit has been in peril. Pointy hat: phk
* Use >= so we can use the actual WARNS levels.obrien2005-01-161-6/+6
|
* Fix comment. Code 0x95 means locking shift to codeset 5 according torik2005-01-161-2/+2
| | | | | | | T1.617 AnnexD. Locking shift procedure is described in ANSI T1.607. MFC after: 3 days
* Fix variable name in comment num=>alen. (Lost part of commit rev 1.2)rik2005-01-161-1/+1
| | | | MFC after: 3 days
* Removed .Re without a matching .Rs.ru2005-01-161-1/+0
|
* Use the \*(If string provided by mdoc(7), to represent infinity.ru2005-01-162-18/+11
|
* Removed redundant .br call.ru2005-01-161-1/+0
|
* Add the new standard EXIT STATUS section where appropriate.ru2005-01-1626-220/+220
| | | | Sort standard sections in the (documented) preferred order.
* In refactoring the test before committing, a pointer was passed insteadrwatson2005-01-161-2/+2
| | | | | | | of a structure for the sockaddr_in. Pass the pointer to connect() instead of the pointer to the pointer. Specify a port number to connect to.
* Remove \n at the end of err(3) stringscharnier2005-01-161-7/+5
|
* Add a new sysctl, hw.sevenseg.freq, to control the update frequency.cognet2005-01-161-1/+6
|
* Erm, don't forget to store the mbuf in the dmamap in bus_dmamap_load_mbuf_sg(),cognet2005-01-161-5/+6
| | | | | so that bus_dmamap_sync() knows what to invalidate. This makes em(4) work again. While I'm there, remove the unused "first" variable.
* Add udpconnectjail, a simple regression test to exercise an (as yet)rwatson2005-01-162-0/+117
| | | | | | | unfixed bug in the jail() implementation relating to using the connect() system call on UDP sockets. PR: 26506
* Standardize 2 error messages: start with lowercase letter.charnier2005-01-161-2/+2
|
* - Reduce number of arguments passed to dummynet_io(), we already have cookieglebius2005-01-165-11/+7
| | | | | in struct ip_fw_args itself. - Remove redundant &= 0xffff from dummynet_io().
* no need to have break; after return;charnier2005-01-161-1/+1
|
* Add prototypes and remove unused variables for WARNS=6 compliance. Addcharnier2005-01-161-25/+28
| | | | | 'usage: ' in front of usage string. Use warnx(3) instead of fprintf in error messages to get progname prepended.
* Remove debugging that made it into the commit.obrien2005-01-161-2/+0
|
* Lock the AMR driver:scottl2005-01-165-106/+120
| | | | | | | | | | - Introduce the amr_io_lock to control access to command queues, bio queues, and the hardware. - Eliminate the taskqueue and do all completion processing in the ithread. - Assign a static slot number to each command instead of doing a linear search for free slots each time a command is needed. - Modify the interrupt handler to more closely match what Linux does, for safety.
* "REQUIRE: cleanvar" for all RC's writing into /var/run.obrien2005-01-1618-18/+20
|
* Fix kernel builds with INVARIANTS.obrien2005-01-161-1/+1
|
* Use bus_dmamap_load_mbuf_sg() for loading rx buffers.scottl2005-01-151-19/+7
|
* Remove ip_fw.h and ip_dummynet.h from includes.glebius2005-01-151-2/+0
|
* Latest IERS Bulletin C (#29): no leap second on 2005-06-30.wollman2005-01-151-19/+29
| | | | Obtained from: http://hpiers.obspm.fr/eoppc/bul/bulc/bulletinc.dat
* Consider three objects, O, BO, and BBO, where BO is O's backing objectalc2005-01-151-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | and BBO is BO's backing object. Now, suppose that O and BO are being collapsed. Furthermore, suppose that BO has been marked dead (OBJ_DEAD) by vm_object_backing_scan() and that either vm_object_backing_scan() has been forced to sleep due to encountering a busy page or vm_object_collapse() has been forced to sleep due to memory allocation in the swap pager. If vm_object_deallocate() is then called on BBO and BO is BBO's only shadow object, vm_object_deallocate() will collapse BO and BBO. In doing so, it adds a necessary temporary reference to BO. If this collapse also sleeps and the prior collapse resumes first, the temporary reference will cause vm_object_collapse to panic with the message "backing_object %p was somehow re-referenced during collapse!" Resolve this race by changing vm_object_deallocate() such that it doesn't collapse BO and BBO if BO is marked dead. Once O and BO are collapsed, vm_object_collapse() will attempt to collapse O and BBO. So, vm_object_deallocate() on BBO need do nothing. Reported by: Peter Holm on 20050107 URL: http://www.holm.cc/stress/log/cons102.html In collaboration with: tegge@ Candidate for RELENG_4 and RELENG_5 MFC after: 2 weeks
OpenPOWER on IntegriCloud