| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
without needing to set special environment variables, testing the 'sh' from
PATH.
|
|
|
|
|
|
| |
and why. The first case is correct usage which has but one correct output.
The 2nd and 3rd cases are incorrect usage in which the exact output is
not standardized and various shells give various allowable output.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
immediately written into the stack after the call. Instead let the caller
manage the "space left".
Previously, growstackstr()'s assumption causes problems with STACKSTRNUL()
where we want to be able to turn a stack into a C string, and later
pretend the NUL is not there.
This fixes a bug in STACKSTRNUL() (that grew the stack) where:
1. STADJUST() called after a STACKSTRNUL() results in an improper adjust.
This can be seen in ${var%pattern} and ${var%%pattern} evaluation.
2. Memory leak in STPUTC() called after a STACKSTRNUL().
Reviewed by: jilles
|
|
|
|
| |
a potentially bad /bin/sh first.
|
| |
|
|
|
|
|
| |
Mailwrapper can provide a perfectly good rmail with other
mailers.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- tcpconnect incorrectly uses err() in usage() with errx() semantics [1]
That produces dirty error message:
tcpconnect: usage: tcpconnect [ip]: Unknown error: 0
- 64-bit aware fixes in printf() usage [2]
o netrate/juggle: time_t has arch-dependent size
o netrate/tcpconnect: don't assume %ll has always 64bit.
PR: 146088 [1], 146086 [2] (modified)
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
| |
Submitted by: Paul B Mahol <onemda@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
of printing a long list.
Add a default base port, and default mulitcast address to the
runner script.
Add support for specifying a different local and remote interface
in the runner script.
MFC after: 1 week
|
|
|
|
|
|
| |
- use label for mounting
- use GENERIC kernel
- create empty Pkg directory
|
|
|
|
|
|
|
|
|
|
|
| |
A closing bracket immediately after '[=' should not be treated as special.
Different from the submitted patch, a string ending with '[=' does not cause
access beyond the terminating '\0'.
PR: bin/150384
Submitted by: Richard Lowe
MFC after: 2 weeks
|
|
|
|
|
| |
Pointed out by: jhb
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
Reported by: Ronald Klop <ronald-freebsd8@klop.yi.org>
|
| |
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
present.
- Correct message - we create GPT, not MBR.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
| |
slice they are on. When NANO_LABEL is not defined, the fstab
generates entries that specify /dev/ad0s1a. When NANO_LABEL is
defined, it generates /dev/usb/${NANO_LABEL}s1a. The prior code
created the file system with a label of ${NANO_LABEL}s1, leading to
problems on boot.
Pointy hat to: imp@
|
|
|
|
|
|
| |
PR: misc/146119
Submitted by: pluknet <pluknet@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
nanobsd will build a system that uses this label (via
/dev/ufs/${NANO_LABEL}sX) in preference to NANO_DRIVE (well, it forces
NANO_DRIVE to be ufs/${NANO_LABEL}). This allows images that will
boot off usb stick or CF card easily well.
There is no change if you don't set this variable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to growing the filesystem.
Refuse to attach providers where the metadata provider size is
wrong. This makes post-boot attaches behave consistently with
pre-boot attaches. Also refuse to restore metadata to a provider
of the wrong size without the new -f switch. The new -f switch
forces the metadata restoration despite the provider size, and
updates the provider size in the restored metadata to the correct
value.
Helped by: pjd
Reviewed by: pjd
|
|
|
|
|
|
|
| |
And perhaps other 64-bit platforms.
Submitted by: Fabian Keil <freebsd-listen@fabiankeil.de>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
into un-zeroed storage.
The original patch was questioned by Kirk as it forces the filesystem
to do excessive work initialising inodes on first use, and was never
MFC'd. This change mimics the newfs(8) approach of zeroing two
blocks of inodes for each new cylinder group.
Reviewed by: mckusick
MFC after: 3 weeks
|
| |
|
|
|
|
|
| |
Example:
HOME=foo HOME=bar cd
|
|
|
|
|
|
| |
Backslash-escaped characters did not set the flag for a non-IFS character.
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Naive buffering would break the common while read x... construct, which did
not appear to be tested yet.
|
| |
|
|
|
|
|
| |
PR: 149729
Submitted by: Thomas Quinot <thomas@cuivre.fr.eu.org>
|
|
|
|
|
|
|
| |
This matches what is in POSIX; various other shells use different exit
statuses.
Note that it is still required that there be no output.
|
|
|
|
|
|
| |
pax/Makefile.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
are too long. Filenames escaping this test are caught later on,
so the bug doesn't cause any breakage.
Document the correct ustar limitations in pax. As I have no access
to the IEEE 1003.2 spec, I can only assume that the limitations
imposed are in fact correct.
Add regression tests for the filename limitations imposed by pax.
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
WITH_BSD_GREP knob.
- Bump __FreeBSD_version
Requested by: dougb
Approved by: delphij (mentor)
|
|
|
|
|
|
|
|
| |
This Almquist extension was disabled long ago.
In pathname generation, components starting with '!!' were treated as
containing wildcards, causing unnecessary readdir (which could fail, causing
pathname generation to fail while it should not).
|
|
|
|
|
|
| |
To avoid multibyte issues, this test forces ISO8859-1 charset.
This also passes on stable/8.
|
|
|
|
| |
It is unwise to rely on this but I'd like to know if this would break.
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
pagesize()/pagesizes() after change to use aux vector. Note that
public function getosreldate() is different from libc-internal
__getosreldate() and does not use aux to fetch osreldate value.
MFC after: 1 month
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
POSIX does not allow constructs like:
if cmd; then fi
{ }
Add a colon dummy command, except in a test that verifies that such empty
lists do not cause crashes when used as a function definition.
|
| |
|