summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* make these more useful for lint(1). Minor diff-reductions while I'mmarkm2003-01-266-1/+7
| | | | about it.
* Fix namespace pollution introduced in previous commit.mbr2003-01-262-5/+5
| | | | Reviewed by: phk
* Remove the get_term() function. It pretty much can't work formarkm2003-01-261-36/+7
| | | | | | | | FreeBSD, and makes ugly diffs with the other crt1.c's. Leave behind a comment (words supplied by Thomas Moestl) that explain the issue. OK'ed by: tmm
* Fix a typo and reword a bit the description of the new SCHED_xxx stuff.keramida2003-01-261-4/+4
| | | | Reviewed by: jeff
* If we fail to open O_RDWR, try opening O_RDONLY, if we use ioctlsphk2003-01-262-0/+12
| | | | | | to fiddle the disk we can get away with it. Try to use DIOCBSDBB to write boot code.
* Implement DIOCBSDBB ioctl which overwrites first BBSIZE bytes of BSDphk2003-01-261-0/+62
| | | | | | | | | | | | | | | | | | | | | | | | | labeled disk. This is complicated by the fact that BBSIZE is greater than the PAGE_SIZE limit ioctl inflicts on arguments which are automatically copied in. As long as we don't need access to userland memory (copyin/out) we can deal with the ioctl using g_callme() which executes it from the GEOM event thread. Once we need copyin/out, we need to return the bio with EDIRIOCTL in order to make geom_dev call us back in the original process context where copyin will work. Unfortunately, that results in us getting called with Giant, so we have to DROP_GIANT/PICKUP_GIANT around the code where we diddle GEOMs internals. Sometimes you just can't win... ... But it does make geom_bsd.c an almost complete example of the GEOM beastiarium.
* Add ioctl which overwrites the first BBSIZE bytes of a BSD labeled disk.phk2003-01-261-0/+1
|
* Fix KSE related patch.julian2003-01-266-12/+6
| | | | | Make it compile for the SMP case.. statclock_process() has changed prototypes.
* Correct typo.murray2003-01-262-2/+2
| | | | Submitted by: Andreas Kohn <andreas.kohn@gmx.net> (via -STABLE)
* regenalfred2003-01-261-2/+2
|
* Add const qualifier to data argument for msgsnd.alfred2003-01-264-6/+5
| | | | | PR: standards/45274 Submitted by: Craig Rodrigues <rodrigc@attbi.com>
* Put DIOCWLABEL under #ifdef NO_GEOMphk2003-01-261-0/+2
|
* Extend the format of /etc/ftpchroot so an alternative chrootyar2003-01-264-24/+171
| | | | | | | | | | | directory can be specified for a user or a group. Add the manpage ftpchroot(5) since the file's format has grown complex enough. PR: bin/45327 Portions submitted by: Hideki SAKAMOTO <sakamoto@hlla.is.tsukuba.ac.jp> MFC after: 1 week
* - Split db.desc.cmd into desc.control and desc.reqcount.simokawa2003-01-262-103/+127
| | | | - remove unncessary descriptor updates.
* IA64 still needs to be able to run on MBR+BSD combination, so put disklabelphk2003-01-263-0/+3
| | | | | | back. Pointed out by: peter
* - Improve IT/IR DMA queue management.simokawa2003-01-264-428/+235
| | | | | - Improve debug message for mbuf handling. - Wait 1 sec for DMA stop in fwohci_i{t,r}x_disable() before freeing buffers.
* Drop the silly notion that i386 has two bootstrap files now that sys/bootphk2003-01-264-326/+70
| | | | | | | | creates a single file named just "boot". Apart from the fact that the option "-s" is now gone and that "-b" should be pointed at /boot/boot instead of /boot/boot1, this patch should be a no-op.
* Link /boot/boot1 to the name /boot/boot to avoid per-arch naming of thephk2003-01-261-0/+1
| | | | bootstrap code for disklabel using architectures.
* Remove #if checks for NUMBOOT==0, it's not relevant for any architecturephk2003-01-262-60/+0
| | | | | and if we get such an architecture, we can just avoid using the relevant options.
* Build a file "boot" which consists of boot1 and boot2 concatenated.phk2003-01-262-2/+12
| | | | | There is little if any reason to treat the two components separately and it will simplify disklabel(8) and libdisk if we didn't.
* This file is no longer needed.phk2003-01-261-79/+0
| | | | Spotted by: tjr
* Offer better advice in #error.phk2003-01-262-10/+6
| | | | Remove yet a usage message about -N/-W
* Spell libufs correctly in DPADD.ru2003-01-262-2/+2
| | | | Reviewed by: juli
* Remove ia64 and powerpc #ifdefs: this is i386/pc98/alpha only code.phk2003-01-262-6/+6
|
* Make disklabel(8) MD for i386/pc98 and alpha only.phk2003-01-261-1/+5
|
* Remove part of my stateful locale patch that slipped into the previous rev.tjr2003-01-261-3/+0
|
* Remove #ifdef __sparc64__ code. GEOM uses native SUN labels on this arch,phk2003-01-262-118/+4
| | | | so no hacks are needed.
* Fix typo in last commit.phk2003-01-262-168/+174
| | | | Rearrange bits in writelabel() a bit for improved readability.
* Move UPCALL related data structure out of kse, introduce a newdavidxu2003-01-2639-1510/+1663
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | data structure called kse_upcall to manage UPCALL. All KSE binding and loaning code are gone. A thread owns an upcall can collect all completed syscall contexts in its ksegrp, turn itself into UPCALL mode, and takes those contexts back to userland. Any thread without upcall structure has to export their contexts and exit at user boundary. Any thread running in user mode owns an upcall structure, when it enters kernel, if the kse mailbox's current thread pointer is not NULL, then when the thread is blocked in kernel, a new UPCALL thread is created and the upcall structure is transfered to the new UPCALL thread. if the kse mailbox's current thread pointer is NULL, then when a thread is blocked in kernel, no UPCALL thread will be created. Each upcall always has an owner thread. Userland can remove an upcall by calling kse_exit, when all upcalls in ksegrp are removed, the group is atomatically shutdown. An upcall owner thread also exits when process is in exiting state. when an owner thread exits, the upcall it owns is also removed. KSE is a pure scheduler entity. it represents a virtual cpu. when a thread is running, it always has a KSE associated with it. scheduler is free to assign a KSE to thread according thread priority, if thread priority is changed, KSE can be moved from one thread to another. When a ksegrp is created, there is always N KSEs created in the group. the N is the number of physical cpu in the current system. This makes it is possible that even an userland UTS is single CPU safe, threads in kernel still can execute on different cpu in parallel. Userland calls kse_create to add more upcall structures into ksegrp to increase concurrent in userland itself, kernel is not restricted by number of upcalls userland provides. The code hasn't been tested under SMP by author due to lack of hardware. Reviewed by: julian
* Put use of DIOCWLABEL under #ifdef NO_GEOMphk2003-01-262-1/+8
|
* Remember to remove -N and -W from usage.phk2003-01-262-4/+0
|
* Don't fiddle write-protect status of disklabel, it's a discontinued feature.phk2003-01-262-16/+0
|
* Don't call DIOCWLABEL on disks, it is not implemented, and calling itphk2003-01-261-7/+1
| | | | like this negated any practical value of the feature.
* Retire the "-N" and "-W" options which implemented write-protectionphk2003-01-264-98/+6
| | | | | | | | | | | | | | | | | | | for the disklabel: This facility is OBE. First of all, we cannot sensibly implement this in a properly stacked environment. Second, if we did, it would confuse the heck out of users who wouldn't be able to "start from scratch" by dd(8)'ing /dev/zero onto /dev/da0. Third, the offered protection is not comprehensive: no other software would respect it. Fourth and finally, the disklabel is already protected against tampering if it controls open partitions. Uselessness of these options discussed with: peter
* Initial implementation of the C99 feature whereby calling freopen() withtjr2003-01-262-2/+94
| | | | | | | | | | a NULL filename argument allows a stream's mode to be changed. At the moment it just recycles the old file descriptor instead of storing the filename somewhere and using that to reopen the file, as the standard seems to require. Strictly conforming C99 applications probably can't tell the difference but POSIX ones can. PR: 46791
* Change the -x option so that it does an actual REAL test ofsilby2003-01-261-11/+35
| | | | | | the correctness of this program. Previously, it printed out the MD5 values of some test strings, but did not tell you if they were correct or not!
* - Remove a redundant scheduler option.jeff2003-01-262-2/+0
| | | | | Pointy hat to: jeff Spotted by: dillon
* Move e450 to supported systems and add e3500 to partially supported.jake2003-01-261-3/+6
| | | | | Thanks to Bill Fenner for providing access to an e450, and to Tomi Vainio for testing on an e3500 (any many other machines).
* - Add entries for scheduler selectionjeff2003-01-261-0/+17
|
* - Add an entry about the new scheduler options.jeff2003-01-261-0/+8
|
* - Introduce the SCHED_ULE and SCHED_4BSD options for compile time selectionjeff2003-01-2612-1/+17
| | | | | of the scheduler. - Add SCHED_4BSD as the scheduler for all kernel config files in cvs.
* - Add the ule scheduler. This is intended to be a general purpose processjeff2003-01-261-0/+697
| | | | | scheduler with many SMP benefits. It is still very experimental and should be used only in test environments.
* Disable DRA to fix problems with recording.orion2003-01-261-14/+19
|
* - Call sched_sleep() instead of rolling our own in cv_waitq_add().jeff2003-01-261-2/+2
|
* Merge some code paths back together so that we only instantiate 1 copy ofjake2003-01-261-121/+97
| | | | the user tlb fault handlers.
* Convert references to other manpages to .Xr and addkeramida2003-01-261-4/+7
| | | | entries to the SEE ALSO section.
* Reword the description of -R a bit and add a note about being carefulkeramida2003-01-261-2/+6
| | | | | | | when -R is combined with patterns that might match ".." (like ".*"). PR: 46415 Submitted by: Gary W. Swearingen <swear@attbi.com>
* Allow defaulting the console to ttya when it sets to screen and keyboardjake2003-01-262-10/+16
| | | | in the prom but no keyboard is plugged in.
* Merge the best parts of maxfragpackets and maxnipq together. (Bothsilby2003-01-261-13/+5
| | | | | | | | | | | functions implemented approximately the same limits on fragment memory usage, but in different fashions.) End user visible changes: - Fragment reassembly queues are freed in a FIFO manner when maxfragpackets has been reached, rather than all reassembly stopping. MFC after: 5 days
* Merge Multi-DLT support.fenner2003-01-262-9/+147
|
OpenPOWER on IntegriCloud