| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also, add the default #!/bin/sh for shellscripts, as well as $FreeBSD$.
|
|
|
|
|
| |
devs other than the first, and allowed to clone a nonexistent
device..
|
|
|
|
| |
Compatability is not an existing english word.
|
|
|
|
|
|
| |
Compatability is not an existing english word.
Add $FreeBSD$.
|
|
|
|
| |
Seperate does not exist in the english language.
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Also add $FreeBSD$ to README.
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Submitted to look at by: kris
|
|
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Also add $FreeBSD$
Submitted to look at by: kris
|
|
|
|
|
|
| |
operations.
Reviewed by: sheldonh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a child is receiving SIGSTOP, eval continues with the next
command. While that is correct for the interactive case (Control-Z
and you get the prompt back), it is wrong for a shellscript, which
just continues with the next command, never again waiting for the
stopped child. Noted when childs from cronjobs were stopped, just to
make more processes (by wosch).
The fix is not to return from a job wait when the wait returned for a
stopped child while in non-interactive mode. This bahaviour seems to
be what bash2 and ksh implement. I tested for correct behaviour for
finnaly killing the child with and without forgrounding it first.
When not foregrouding before killing, the shell continues with the
script, which is what the other shells do as well.
Reviewed by: Silence on -current
|
| |
|
|
|
|
|
|
| |
backwards in the three drivers which want to do that.
Reviewed by: mikeh
|
|
|
|
| |
There is no such thing as wierd in the english language.
|
|
|
|
| |
There is no such thing as wierd in the english language.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Touched up a bit and added some consistency to the text by your's truly.
PR: 23745
Submitted by: Andrew Stevenson <andrew@ugh.net.au>
|
|
|
|
|
|
|
| |
the commit logs - I just found the reason for the self-pointing symlink, as
documented in revision 1.517 by phk, who committed the change over a year
ago. Accordingly, put the feature back and drop all plans to MFC the previous
"fix".
|
|
|
|
|
|
| |
asking what it's for and I can't answer since I can't see any conceivable
use for it. Unless someone corrects that impression, I'll also MFC this
change in a few days.
|
|
|
|
|
|
|
|
|
| |
These are not enabled in the pkg_install Makefile as of yet;
adding the "sign" directory to the SUBDIR list will enable
building of sign.
Submitted by: Wes Peters
Obtained from: Original framework from OpenBSD 2.7, X.509 bits from DoBox.
|
|
|
|
|
|
|
|
|
|
|
| |
default syslog target for console messages (when enabled in
syslog.conf). Use the same rotation defaults as with
/var/log/messages -- every 100kb of log, compress back logs,
and keep five rotated logs.
o Note: phk also thought it would be useful to force rotation
each boot. This commit does not introduce such a rotation.
Reviewed by: phk
|
| |
|
|
|
|
|
| |
only required when dev/ppbus wasn't installed, and they should not
been delimited by <> even then.
|
|
|
|
| |
for almost everything.
|
|
|
|
|
| |
duplicated in libc_r/man/*.3 but were fixed years ago there. Here
they were hiding under mdoc errors.
|
| |
|
| |
|
| |
|
|
|
|
| |
poisoning having not reached here).
|
|
|
|
| |
Declare all the interfaces documented in usb.3 (2 were missing).
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: olgeni
|
|
|
|
|
|
| |
new drivers, pkg_info(1) -g, tftp(1)/tftpd(8) large file transfers.
MFCs noted: pkg_create(1)/pkg_install(1) and bzip2-ed packages.
|
| |
|
|
|
|
|
| |
space when it calls the disconnect PRU function without checking that it
there.
|
|
|
|
|
|
|
|
|
|
|
|
| |
only covers about 3-4 lines.
- Don't lower the IPL while we are on the interrupt stack. Instead, save
the raised IPL and change the saved IPL in sched_lock to IPL_0 before
calling mi_switch(). When we are resumed, restore the saved IPL in
sched_lock to the saved raised IPL so that when we release sched_lock
we won't lower the IPL. Without this, we would get nested interrupts
that would overflow the kernel stack.
Tested by: mjacob
|
|
|
|
|
|
| |
also try implement teh documented behaviour in socket nodes
so that when there is only one hook, an unaddressed write/send
will DTRT and send the data to that hook.
|
| |
|