summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Better handling of word splitting. Don't record the same regiontegge1998-09-067-49/+231
| | | | | | multiple times when performing nested variable expansion, and preserve some quoting information in order to avoid removing apparently empty expansion result.
* Don't blindly eliminate `..' and the previous pathname component.tegge1998-09-062-19/+160
| | | | | PR: 2541 Obtained from: NetBSD
* Fix calls to mmap. It returns void *, and on failure it returnsjdp1998-09-061-11/+11
| | | | | | | | | | | MAP_FAILED. Don't try to extend the mapping in place if it is too short. There's no guarantee it will be possible. Remap the file instead. Put in a few style fixes. Submitted by: Bruce Evans <bde>
* Clean LINTrvb1998-09-069-30/+54
|
* Patch the transmit error handler to avoid following NULL pointers andwpaul1998-09-061-3/+4
| | | | | | | | | | | | | | | | | | | | | | generating a trap 12 panic. The code blindly assumed that in the event of a transmit error, the packet that caused the error would still be at the head of the driver's transmit queue (sc->xl_cdata.xl_tx_head). However in the case of error 82 (which indicates that a transmit error occurred after part of the transmit FIFO memory has been reclaimed) this is not true: the TX queue has already been flushed, and the pointer to the head of the queue is NULL, so trying to dereference the pointer to find the transmit descriptor address causes a crash. The code now checks for a NULL pointer before trying to reload the chip's download pointer register. There may still be error messages printed warning of the transmit error, but no panic should occur. Note that this eror code is only generated with "cyclone" chipsets (3c900B, 3c905B, and presumeably the 3c980 server adapter). It should only appear during periods of heavy traffic, probably only on non-switched networks. Problem reported by: Darcy Buskermolen <darcy@ok-connect.com>
* Add a compuserve example.brian1998-09-061-1/+15
| | | | Detailed by: Masahiro Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>
* Fix tons of cut-n-paste errors in the WANT_NFS3 code.obrien1998-09-061-14/+16
|
* Reviewed by: Andrey A. Chernov <ache@nagual.pp.ru>, Doug Rabson ↵dillon1998-09-061-17/+29
| | | | | | | <dfr@nlsystems.com> Rewrote sleep() to remove int/long typing assumptions between the argument to the function and the timespec structure.
* Use a varargs style prototype in the manual page, with accompanyingjkoshy1998-09-061-1/+14
| | | | explanation in the text.
* tcp_extensions now only applies to RFC1323phk1998-09-068-16/+9
|
* RFC 1644 has the status "Experimental Protocol", which means:phk1998-09-062-4/+4
| | | | | | | | | | 4.1.4. Experimental Protocol A system should not implement an experimental protocol unless it is participating in the experiment and has coordinated its use of the protocol with the developer of the protocol. Pointed out by: Steinar Haug <sthaug@nethelp.no>
* Store formatted panic string in static buffer to make it available laterache1998-09-063-7/+22
| | | | | for savecore. Previous code give only panic format to savecore
* Change the ELF64_R_SYM() to shift 32 bits instead of 8 bits to matchjb1998-09-051-23/+24
| | | | | | | | | | binutils. Ensure that three of the structures are the size that binutils writes them. I just love code that doesn't share header files to avoid problems like these. With this change rtld-elf works on alpha.
* NFS can use TCP now daysobrien1998-09-051-1/+2
|
* Don't recognize a file as an a.out shared library unless it has atjdp1998-09-051-6/+4
| | | | | | | | | | | | least 2 version numbers. This fixes the bug where the dynamic linker would try to load an ELF shared library if it found one. Note, this change also fixes the same thing in "ld", because the code is shared. For "ld" there is still a problem with ".a" libraries, which cannot be distinguished by name. I haven't decided what, if anything, to do about that.
* Ignore the statically configured vfs type numbers and assign vfsbde1998-09-056-25/+73
| | | | | | | | | | | type numbers in vfs attach order (modulo incomplete reuse of old numbers after vfs LKMs are unloaded). This requires reinitializing the sysctl tree (or at least the vfs subtree) for vfs's that support sysctls (currently only nfs). sysctl_order() already handled reinitialization reasonably except it checked for annulled self references in the wrong place. Fixed sysctls for vfs LKMs.
* For a.out mode, ignore shared libraries that don't have at least 2jdp1998-09-051-1/+3
| | | | version numbers.
* Don't do anything special to prevent access to created files - honourbde1998-09-051-1/+3
| | | | the default umask. World unreadable files broke installing over nfs.
* Instantiate `nfs_mount_type' in a standard file so that it is presentbde1998-09-059-16/+13
| | | | | | | | when nfs is an LKM. Declare it in a header file. Don't forget to use it in non-Lite2 code. Initialize it to -1 instead of to 0, since 0 will soon be the mount type number for the first vfs loaded. NetBSD uses strcmp() to avoid this ugly global.
* Disable gcc's builtin memcpy for alpha since it doesn't cope with unaligneddfr1998-09-051-1/+4
| | | | regions properly and this triggers an unaligned access trap.
* Fixed bogotification of pseudocode for syscall args by rev.1.53 ofbde1998-09-053-10/+10
| | | | syscalls.master.
* Sysctl nodes are written to, so don't put them in the text section.bde1998-09-051-4/+4
| | | | | | | | Our write protection of the kernel text on i386's doesn't actually work in many cases: - use of the 4MB page completely breaks it. - CR0_WP isn't set until just before init is started, so the kernel text is not write protected during kernel initialization.
* Add a new vnode op, VOP_FREEBLKS(), which filesystems can use to informphk1998-09-059-19/+99
| | | | | | | | | | | | | device drivers about sectors no longer in use. Device-drivers receive the call through d_strategy, if they have D_CANFREE in d_flags. This allows flash based devices to erase the sectors and avoid pointlessly carrying them around in compactions. Reviewed by: Kirk Mckusick, bde Sponsored by: M-Systems (www.m-sys.com)
* Fixed recently perpetrated printf format errors.bde1998-09-053-8/+6
|
* Don't comment out dead code. Remove it.bde1998-09-051-18/+16
| | | | | | Fixed disgustingly long lines. Improved English in some comments.
* Remove tcl from src/contrib.asami1998-09-05395-173953/+0
|
* Remove tcl from /usr/src, according to prior agreement. BTW, tcl-8.0 *is*asami1998-09-057-417/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a port so there is nothing to be done on that side now. Approved by: jkh === To: "Jordan K. Hubbard" <jkh@time.cdrom.com> cc: Andreas Klemm <andreas@klemm.gtn.com>, current@freebsd.org Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued) From: David Greenman <dg@root.com> Date: Sun, 03 Aug 1997 20:23:31 -0700 >decision is, I'll respect it. Another chance to architect people's principles...I can hardly wait. Seems quite appropriate for a Sunday - I just need to get one of those collection plates (and money envelopes) so I can profit, too. :-) Tcl stays in /usr/src for now, but it needs to be kept up to date; same for perl. If Jordan doesn't have "setup" (written in tcl) ready for 3.0, then tcl will be yanked prior to the 3.0 release (and made into a port). As for the ports tree only supporting the last FreeBSD release, this seems sensible to me. The "ports" have always been a moving target between releases and the problem is only going to get worse when we expand to supporting other processor architectures. In any case, Satoshi is and always has been in charge of the ports tree and whatever he wants to do with it (within reason :-)) is his decision. Does this cover the issue completely? I admit to deleting messages in this thread with unusual fervor (people have FAR too much time on their hands!). There's a fair bit of reasoning behind the above, but since everyone is sick of arguing about this, I'll spare you the analysis. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
* Change i386 in a few paths to ${MACHINE} to support MACHINE=pc98.jb1998-09-051-4/+4
|
* Change MACHINE to MACHINE_ARCH when testing for i386 to supportjb1998-09-051-2/+2
| | | | | | MACHINE=pc98. There are a lot unsupported machines here.
* Chaneg MACHINE to MACHINE_ARCH to support MACHINE=pc98.jb1998-09-051-7/+3
| | | | Remove a couple of unsupported machines.
* Chaneg MACHINE to MACHINE_ARCH to support MACHINE=pc98.jb1998-09-051-3/+3
|
* Change MACHINE to MACHINE_ARCH to support MACHINE=pc98.jb1998-09-051-3/+3
|
* Add support for MACHINE=pc98. This leaves a single legacy entry forjb1998-09-051-8/+3
| | | | the old aout bootloader.
* Change MACHINE to MACHINE_ARCH to support MACHINE=pc98.jb1998-09-053-3/+3
|
* Add a GENERICupgrade config file for pc98 users to upgrade to elfjb1998-09-051-0/+212
| | | | in the same way as i386 users. This is a copy of GENERIC98.
* Change a hardcoded i386 reference to ${MACHINE} so that MACHINE=pc98jb1998-09-051-2/+2
| | | | is supported properly.
* Use INT_MAX instead of LONG_MAX since the variable being comparedjb1998-09-051-4/+4
| | | | is an int, not a long.
* Change a test for NETBSD_SYSCALLS to __alpha__. We're not ready tojb1998-09-051-2/+2
| | | | do profiling on alpha yet.
* Change the profile data file name from gmon.out to progname.gmonjb1998-09-052-7/+14
| | | | where progname comes from __progname in crt0 or crt1.
* Set CHROOTDIR's initial object type also.jkh1998-09-051-1/+2
| | | | Suggested by: jb
* Now that ldconfig does elf work too, build it on alpha as well.jb1998-09-051-2/+2
|
* More sorting of references.obrien1998-09-054-16/+14
|
* Add OBJFORMAT to list of variables passed into /mk script since it seemsjkh1998-09-051-1/+2
| | | | | | to think you're using aout otherwise (and emits a rather confusing and inaccurate diagnostic about OBJFORMAT being set in /etc/make.conf when it most demonstrably is not set there).
* MFO: rev 1.3 - correct man page xrefs.obrien1998-09-051-2/+2
|
* compare getopt() with -1, not EOFobrien1998-09-051-2/+2
|
* MFO rev 1.4 - sort cross referencesobrien1998-09-051-5/+5
|
* Explicitly pass the "-aout" option to ldconfig, until I've had ajdp1998-09-051-3/+3
| | | | | chance to work out a better scheme to handle the separate invocations necessary for a.out and ELF.
* Implement ldconfig functionality for ELF. The hints are stored injdp1998-09-056-34/+515
| | | | | | | | | | | | | | | | | | | | | | | a different file than the a.out hints, namely, "/var/run/ld-elf.so.hints". These hints consist only of the directory search path. There is no hash table as in the a.out hints, because ELF doesn't have to search for the file with the highest minor version number. (It doesn't have minor version numbers at all.) A single run of ldconfig updates either the a.out hints or the ELF hints, but not both. The set of hints to process is selected in the usual way, via /etc/objformat, or ${OBJFORMAT}, or the "-aout" or "-elf" command line option. The rationale is that you probably want to search different directories for ELF than for a.out. "ldconfig -r" is faked up to produce output like we are used to, except that for ELF there are no minor version numbers. This should enable "ldconfig -r" to be used for checking LIB_DEPENDS in ports even for ELF. I implemented the ELF functionality in a new source file, with an eye toward eliminating the a.out code entirely at some point in the future.
* Sync with sys/i386/conf/files.i386 revision 1.201.kato1998-09-052-2/+4
|
* Sync with sys/i386/conf/Makefile.i386 revision 1.121.kato1998-09-052-4/+8
|
OpenPOWER on IntegriCloud