| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
getwd() -> getcwd()
wait3() -> waitpid()
|
|
|
|
| |
Noticed by: Nick Leuta <skynick -at- mail.sc.ru> (some of them)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
for status replies on file system objects:
212 Directory status.
213 File status.
Reported by: Oleg Koreshkov <okor -at- zone.salut.ru>
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In the old world (as the surrounding comment in makefile says), there
was the /usr/libexec/ld-elf.so.1 binary which is now a symlink to
/libexec/ld-elf.so.1. To symlink, we need to make sure that the
_target_ (and the target is /usr/libexec/ld-elf.so.1) doesn't have
"schg" flag set. A real solution is to protect the chflags call only if
target exists, like we do in usr.bin/tip/tip/Makefile.
Requested by: ru
|
|
|
|
|
|
|
|
| |
symlink.
PR: kern/73016
Submitted by: John E. Hein <jhein@timing.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
If turned on no NIS support and related programs will be built.
Lost parts rediscovered by: Danny Braniss <danny at cs.huji.ac.il>
PR: bin/68303
No objections: des, gshapiro, nectar
Reviewed by: ru
Approved by: rwatson (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
The size_t type is better suited for that, particularly because
the "blksize" argument is to be passed to malloc() and read().
On 64-bit archs it's more to a style issue, but the good style
of coding in C is also important.
|
|
|
|
| |
They're unneeded and sometimes erroneous now.
|
|
|
|
| |
file.
|
|
|
|
|
| |
running on an amd64 kernel. Use the recently exposed direct %fs/%gs set
routines instead for the TLS setup of 32 bit binaries.
|
|
|
|
|
|
|
|
| |
to PRECIOUSLIB from bsd.lib.mk. The side effect of this
is making installing the world under jail(8) possible by
using another knob, NOFSCHG.
Reviewed by: oliver
|
|
|
|
|
|
|
|
| |
Previously logxfer() used to record bogus pathnames to the log
in some cases, namely, when cwd was / or "name" was absolute.
Noticed by: Nick Leuta
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
(intmax_t) and %jd, which is the right way to printf
an off_t in the presence of <stdint.h>.
Submitted by: Nick Leuta
|
|
|
|
| |
Approved by: grehan (mentor)
|
|
|
|
|
|
|
| |
can be overlap in the TLS offsets, if the relocations are done in a
certain order.
Approved by: dfr, grehan (mentor)
|
|
|
|
|
|
|
|
|
| |
that the creation of a PAM context has failed.
N.B. This does not apply to pam_strerror() in RELENG_4, it
will mishandle a NULL "pamh".
Discussed with: des
|
|
|
|
|
|
|
|
|
| |
- Stop calling pam_strerror() with NULL pamh.
- Add a missing call to pam_end().
PR: bin/59776
Submitted by: Nick Leuta <see PR for email>
MFC after: 2 weeks
|
|
|
|
|
| |
in the comment above it so that nobody will save pointers
returned inside "struct passwd" across the calls to the function.
|
|
|
|
|
|
|
|
|
|
| |
instead of the disk size of the file sent. Since the log file
is intended to provide data for anonymous ftp traffic accounting,
the disk size of the file isn't really informative in this case.
PR: bin/72687
Submitted by: Oleg Koreshkov
MFC after: 1 week
|
|
|
|
| |
any fake value.
|
|
|
|
| |
unnecessary since src/include/rpcsvc/ypclnt.h's revision 1.10.
|
|
|
|
|
|
|
|
| |
if sendfile() transferred some data before throwing
a error condition because sendfile() won't move the
file offset for read() to start from.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
prematurely, e.g., if the file has been truncated by someone else.
PR: bin/72649
Submitted by: Oleg Koreshkov (portions)
MFC after: 2 weeks
|
|
|
|
| |
especially third party junk^Wpages, like emulators/mtools(1) and friends.
|
|
|
|
|
| |
filter the errno values. They don't make as much sense as they used
to given how we do devices in /dev.
|
|
|
|
| |
been done before.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not unconditionally fork() after accept(). accept() can
return -1 due to an interrupted system call (i.e. SIGCHLD).
If we fork in that case ftpd can get into an
accept()/SIGCHLD/fork/[fail]/repeat loop.
Reported-by: fabian <fabian.duelli@bluewin.ch>
Obtained from: DragonflyBSD
MFC after: 1 month
|
|
|
|
| |
Arbitraly choose the 2nd variant until I figure out which one I should use.
|
| |
|
|
|
|
|
|
| |
Submitted by: (in part) dougb@, trhodes@
Reviewed by: dougb@, trhodes@, re@
MFC after: 5 days
|
|
|
|
|
| |
Spotted by: Pawel Worach
Obtained from: NetBSD (rev. 1.11, 1.13)
|
| |
|
| |
|
|
|
|
|
|
| |
"Open Firmware" from IEEE 1275 and OpenFirmware.org (no pun intended).
Ok'ed by: tmm
|
|
|
|
|
|
|
|
|
|
| |
of releases. The -DNOCRYPT build option still exists for anyone who
really wants to build non-cryptographic binaries, but the "crypto"
release distribution is now part of "base", and anyone installing from a
release will get cryptographic binaries.
Approved by: re (scottl), markm
Discussed on: freebsd-current, in late April 2004
|
|
|
|
| |
Submitted by: ssouhlal
|
| |
|
|
|
|
| |
Tested on: i386, ia64, amd64, sparc64, alpha
|
|
|
|
|
|
|
| |
(and it appears possible throughout ftpd(8) source.)
It is not a mere issue of style: Null pointers in C
seem to have been mistaken one way or another quite often.
|
|
|
|
|
|
| |
Thank Fortune, the C compiler can figure out by itself the proper
conversion for assignments, comparisons, and prototyped function
arguments.
|
|
|
|
| |
we've got <stdint.h> et al now. (This makes ftpd(8) WARNS=2 clean.)
|
| |
|
|
|
|
| |
(Heading to WARNS=2.)
|