| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
uudecode(1), as this behaviour was explicitly added in revision 1.12 as
the result of PR 2882. Remove space (' ') from the delimiter characters
handed to strtok(3).
Reviewed by: mike
Approved by: mike
Pointy hat to: me
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chmodding using an octal mode, as uudecode needs to handle symbolic modes
as chmod and such do.
Suggested by: Tim J. Robbins <tim@robbins.id.au>
Also move meta-character (~ in this case) globbing to only if we are reading
the filename from the encoded file, as otherwise it is the shell's job.
Reviewed by: mike
Approved by: mike
|
| |
|
|
|
|
|
|
|
| |
chpass(8). The relations between libc, libpam, chpass, passwd, and
vipw are a mess and probably should be cleaned up.
Submitted by: Peter Pentchev <roam@ringlet.net>
|
|
|
|
|
|
|
|
| |
2002? It is a bug. Might as well close the PR.
PR: misc/14511
Submitted by: Mike Pritchard <mpp@mpp.pro-ns.net>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
information (no one else can vipw(8), chpass(1), or even passwd(1)),
either on purpose or by accident, until an administrator manually
intervened. Instead, do not lock the master.passwd file while a user
is editing his information. But once we go to write the new
information, check that the modified user's information has not
changed in the password database since we started. Abort the changes
if it has.
Add a $FreeBSD$ to pw_copy.h.
PR: i386/35816
Obtained from: NetBSD
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
PR: docs/35956
Submitted by: Gary W. Swearingen <swear@blarg.net>
MFC after: 3 days
|
|
|
|
|
| |
Reviewed by: mike
Approved by: mike
|
| |
|
| |
|
|
|
|
|
| |
Restore fixes from revision 1.20 that got lost in revision 1.21 merge.
Fixed some more.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
the correct userid, instead of random garbage. This bug does not
exist in -stable.
Reviewed by: freebsd-audit
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
this in this file is the correct way round. (Maybe our definition of
__assert is wrong?)
Anyway, perhaps we should revisit this later. For the time being,
building lint libraries here does not blow up.
|
| |
|
| |
|
|
|
|
| |
Pointed by: phantom
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
fails, errno is saved to a volatile variable that the parent later inspects.
PR: bin/34898
Submitted by: Tim J. Robbins <tim@robbins.dropbear.id.au>
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the unused global var.
|
|
|
|
|
|
| |
doing some fixing...
...asked for by: bde
|
|
|
|
|
|
|
| |
1) place __FBSDID() correctly IAW style(9).
2) revert (and slightly correct) a "complex" expression in an if()
statement.
|
| |
|
|
|
|
|
|
| |
is to put a copyright in the object file.
Submitted by: bde
|
|
|
|
|
|
| |
need the -funsigned-char hack."
Also add needed CLEANSFILE.
|
| |
|
| |
|
|
|
|
| |
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
| |
PR: bin/35590
Submitted by: "Tim J. Robbins" <tim@robbins.dropbear.id.au>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generated the gmon data. The support is currently limited to what is
easy to implement and/or needed:
signedess: signed or insigned
size: 8, 16, 32 or 64 bits
format: a binary integer in gprof's format (gprof is not a cross-tool).
High-resolution kernel profiling uses signed 64-bit counters. Normal
kernel profiling and user profiling use unsigned 16-bit counters but
should use 32-bit ones.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
things when sizeof(UNIT) becomes a runtime parameter. The relevant 2
is the one in profil(2)'s scaling of pc's to bucket numbers:
bucket = (pc - offset) / 2 * profil_scale / 65536
gprof(1) must duplicate this scaling, bug for bug compatibly, so it
must first do an integer division by 2 although this mainly makes
scales larger than 65536 useless. sizeof(UNIT) was already wrong in
gprof4, but there were no problems because the fake profil scale is a
multiple of 2.
There are also some rounding bugs in the scaling, but these are only
problems if profil(2) is used directly to create unusual (and not
useful) scales.
|
|
|
|
|
|
|
|
|
| |
applications linked with Linux-PAM will still work.
Remove pam_get_pass(); OpenPAM has pam_get_authtok().
Remove pam_prompt(); OpenPAM has pam_{,v}{error,info,prompt}().
Remove pam_set_item(3) man page as OpenPAM has its own.
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
| |
platforms we install as "nawk".
At the moment Gawk is borked on sparc64, however BWK AWK works fine.
|
| |
|
|
|
|
| |
Submitted by: roam
|
| |
|