summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* More save_userconfig to a more appropriate spot.jkh1998-09-303-18/+18
|
* Make devfs update the atime timestamp so that 'w' works when usingsos1998-09-302-5/+12
| | | | options DEVFS.
* Allow NOSUIDPERL to DTRT.markm1998-09-301-2/+6
|
* Turn on i386-elfpeter1998-09-301-1/+3
|
* i386 ELF loader startup backend. On an ELF kernel booted with the 3-stagepeter1998-09-304-2/+521
| | | | | | | | | | | | | bootblocks, the kernel shows up as the primary module: [3:24am]~-100# kldstat Id Refs Address Size Name 1 1 0xf0100000 ff00000 /kernel ^^^^ oops.. :-) Based heavily on aout_freebsd.c. Hmm.. There's so much in common that these could probably be combined and just check the metadata to see which format it is.
* Save booted kernel name. Cosmetic cleanups.peter1998-09-301-3/+15
|
* Fix typos.. The vector for "int 0x12" (get base mem) is not written inpeter1998-09-301-2/+2
| | | | | hex as "0x1a". :-) Fix a comment about the extended memory checks, that's int 0x15.
* ELF loader, part 1. It works with ELF kernels generated on the i386peter1998-09-302-2/+278
| | | | | | | | | | | | | | | | | | | so far, and should probably be able to be made to work for the alpha without too much trouble once it's connected up and my assumptions tested. I think (but have not tested) it will also load "old" ELF kernels that were not linked with DYNAMIC headers. The module glue is yet to come. (oh fun.. :-) It does not explicitly load symbols [yet]. The _DYNAMIC data contains a runtime symbol set that ddb can use via ddb/db_kld.c. It'll be missing some detail that stabs normally provides (eg: number of args to a function, line numbers, etc). On the other hand, those minimal symbols will always be available even on a stripped kernel. This is mostly stolen from load_aout.c with some ideas from alpha/libalpha/elf_freebsd.c.
* Move variable into proper scope.jkh1998-09-301-2/+3
|
* s/out_loadmodule/aout_loadmodule/ in a printf diagnostic.peter1998-09-301-2/+2
|
* Uncomment prototype for elf_loadmodulepeter1998-09-301-2/+2
|
* Debug when an environment variable set, no when it is unset.dt1998-09-302-4/+4
|
* Limit the fingerd daemon to:wosch1998-09-301-2/+2
| | | | | runs only 3 simultaneous fingerd processes and limit the connections-per-ip-per-minute to 10.
* Put guard shells around stuff started from $local_startup. If you typecracauer1998-09-301-2/+3
| | | | | SIGINT (C-c), you'll get control passed to the next script even if the current one blocks signals. The child is not killed, though.
* Document that we support the CS4236B.des1998-09-301-0/+1
|
* Add PnP ID for Crystal Semiconductors CS4236B codecs (register-des1998-09-303-0/+9
| | | | | | compatible with CS4236, so no driver changes are required) Reviewed by: Luigi Rizzo <luigi@iet.unipi.it>
* Simplify gunzip usage even more (doh!).jkh1998-09-303-6/+6
|
* Sync with sys/i386/i386/machdep.c revision 1.311.kato1998-09-302-8/+50
|
* Fix english in prompt.jkh1998-09-303-6/+6
|
* Make the ELF kernel build produce a dynamic executable (!). This enablespeter1998-09-306-9/+432
| | | | | | | | | | | | | | | | | the in-kernel linker to access the _DYNAMIC data for doing loadable elf modules. The alpha kernel is already done this way, I've borrowed some of the hacks from there. This is primarily aimed at the 3-stage boot process which is intended to be able to do pre-loading of kernel modules. Note that the entry point isn't 0xf0100000 any more, it'll be a little further on - but this value is stored in the headers. I don't think this will be a problem, but I'm sure somebody will tell me if it is. :-) I'm not sure if btxboot is going to like this, it doesn't do proper ELF header checking and assumes that there are exactly two program header entries and that they are both PT_LOAD entries - a bad assumption.
* Add missing free()jkh1998-09-301-3/+1
| | | | Submitted by: Anatoly A. Orehovsky <tolik@mpeks.tomsk.su>
* Add missing free().jkh1998-09-301-1/+2
| | | | Submitted by: Anatoly A. Orehovsky <tolik@mpeks.tomsk.su>
* various bits of overdue cleanup.jkh1998-09-309-111/+21
|
* Call gunzip correctly.jkh1998-09-303-6/+12
|
* Correct source file corruption in last checkingrog1998-09-301-2/+1
| | | | Observed by: jkh
* Revise test code for sigwait and add test code for sigsuspend.jb1998-09-302-0/+281
| | | | Submitted by: Daniel M. Eischen <eischen@vigrid.com>
* Revise test code for sigwait and add test code for sigsuspend.jb1998-09-304-18/+116
| | | | Submitted by: Daniel M. Eischen <eischen@vigrid.com>
* Fix a comment.jb1998-09-301-1/+1
|
* Cosmetic cleansing. This code requires extra work to keep the garbagejb1998-09-303-6/+9
| | | | collector thread running after a fork.
* Move the cleanup code that frees memory allocated for a dead thread fromjb1998-09-3020-390/+700
| | | | | | | | | | | | | | the thread kernel into a garbage collector thread which is started when the fisrt thread is created (other than the initial thread). This removes the window of opportunity where a context switch will cause a thread that has locked the malloc spinlock, to enter the thread kernel, find there is a dead thread and try to free memory, therefore trying to lock the malloc spinlock against itself. The garbage collector thread acts just like any other thread, so instead of having a spinlock to control accesses to the dead thread list, it uses a mutex and a condition variable so that it can happily wait to be signalled when a thread exists.
* Use snprintf instead of sprintf to avoid long source file paths fromjb1998-09-303-36/+93
| | | | | | | launching an application into space when someone tries to debug it. The dead thread list now has it's own link pointer, so use that when reporting the grateful dead.
* Implementation of an additional state called SIGWAIT (with the previousjb1998-09-3012-204/+348
| | | | | | one renamed to SIGSUSPEND) to fix sigwait(). Submitted by: Daniel M. Eischen <eischen@vigrid.com>
* NULL a pointer after it is freed to avoid trying to free it again.jb1998-09-303-0/+6
|
* - Fix the debug macros.jb1998-09-303-12/+63
| | | | | | | | | | | - Add support of a thread being listed in the dead thread list as well as the thread list. - Add a new thread state to make sigwait work properly. (Submitted by Daniel M. Eischen <eischen@vigrid.com>) - Add global variable for the garbage collector mutex and condition variable. - Delete a couple of prototypes that are no longer required. - Add a prototype for the garbage collector thread.
* Delete the XXX comments that refer to spinlock recursion. The malloc/free/jb1998-09-301-15/+1
| | | | | | | | | realloc functions check for recursion within the malloc code itself. In a thread-safe library, the single spinlock ensures that no two threads go inside the protected code at the same time. The thread implementation is responsible for ensuring that the spinlock does in fact protect malloc. There was a window of opportunity in which this was not the case. I'll fix that with a commit RSN.
* Remove SCSI support as the only driver in this kernel config, aic, is notgibbs1998-09-301-6/+6
| | | | currently supported by CAM.
* Fix typo in message.danny1998-09-303-6/+6
|
* Add several missing ioctl handlers. One needed by Sybase, the othersjfieber1998-09-304-4/+58
| | | | found while looking for the one.
* Do not allow a mounted on directory to be rmdir'ed. This removal canmckusick1998-09-301-2/+8
| | | | | | | happen when an NFS exported filesystem tries to remove a locally mounted on directory. PR: kern/7272 Submitted by: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
* Perform a hard reset on cards when the command fails. This should helpimp1998-09-301-2/+2
| | | | | those people that have cards that become wedged when a bogus command is issued that are too wedged to have a soft reset help.
* In nfs_link(), check for a cross-device mount *before* lookingmckusick1998-09-292-4/+6
| | | | | in the v_data field. Obtained from: Charles Hannum, via Frank van der Linden <frank@wins.uva.nl>
* Missing vput when cross-device link error is detected in nfs_link.mckusick1998-09-292-0/+2
|
* During truncation, have to notify the VM about the new sizemckusick1998-09-292-6/+10
| | | | | of the NFS file *before* doing the nfs_vinvalbuf operation. Otherwise some invalid data may show up in an mmap.
* Don't require an argument for -v flaggrog1998-09-292-11/+18
| | | | | | | Correct checks for null special file names Add Usage entry for -v flag Get terminology straight in man page Reviewed by: bde
* Frank sez: 'It fixes a problem with servers that return 0 valuesmckusick1998-09-292-14/+20
| | | | | | | | for some of the fsinfo RPC fields. It is strictly speaking not wrong to do this, as the spec says that "it is expected that a server will make a best effort at supporting all the attributes", but pretty unusual. You guessed it, it's NT servers that do it.' Obtained from: Frank van der Linden <frank@wins.uva.nl>
* Do not need (or want) to take a reference on an NFS file thatmckusick1998-09-292-12/+24
| | | | | | | | | is being deleted due to an forcible unmount. The problem is that vgone calls vclean() which then calls calls nfs_inactive() with VXLOCK set on the vnode. Nfs_inactive() was calling vget() to get a reference on the vnode, which in turn hung on VXLOCK. Nfs_inactive() now checks v_usecount to make sure that the vnode is not coming from vclean() before it does a vget().
* The code checks each fragment mark to see if it's valid; if the fragmentmckusick1998-09-293-6/+6
| | | | | | | | | | | | | | | | | | | | | is less than NFS_MINPACKET or greater than NFS_MAXPACKET in size, it barfs and, I think, drops the connection. However, there's no guarantee that in a multi-fragment RPC, all the fragments will be at least as large as NFS_MINPACKET. In fact, with the version of "tclnfs" we have here, which supports NFS over TCP, at least when built under SunOS 4.1.3 (i.e., with 4.1.3's user-mode ONC RPC library), I can *repeatably* cause "tclnfs" to send a request with more than one fragment, one of which is only 8 bytes long. I just do a 3877-byte write to a file, at an offset of 0. The check that "slp->ns_reclen" is greater than or equal to NFS_MINPACKET serves no useful purpose - if the NFS server code can't handle packets < NFS_MINPACKET bytes, it can't handle them over *any* protocol, so the check has to be done above the RPC-over-TCP layer - and should be removed. Obtained from: Fix from Guy Harris, forwarded by Rick Macklem.
* In the bootverbose case, print out error messages for all errors that willken1998-09-292-8/+18
| | | | | | not be retried again, even if the SF_NO_PRINT flag is set. Reviewed by: gibbs
* vm86_datacall: always use workaround since temp. malloced buffer or stackache1998-09-291-22/+18
| | | | | area can be passed (and mapped to page1!) as vesa.c does. Use contigmalloc now to get proper alignment. Bump max buffer size to PAGE_SIZE
* Add back a few useful targets lost in the reshuffle.jkh1998-09-292-8/+8
| | | | Reviewed by: jb
OpenPOWER on IntegriCloud