| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
similarly to read_archive.
Note we no longer bother seeking back to the start of the header, as only
ArchTouch accesses that header, and can do the seek itself.
With this, arch handling should be working, more or less.
thanks to Todd, Miod, Naddy for reviewing those patches.
|
|
Hence, read_archive must be very careful to parse stuff correctly: don't
use str* when mem* are appropriate, copy numeric fields and ensure they're
terminated...
|
|
and put it into a specific structure (it is wasteful to keep lugging
SVR4 structures once an archive is parsed).
By tweaking read_archive slightly, we can achieve a nicer interface
to ArchSVR4Entry.
Note a bug in make: ArchFindMember does (currently) not use the SVR4 code,
hence some archive members won't be found in non-caching mode...
|
|
|
|
contents start with a '-' test becomes unhappy (since it interprets it
as another option).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
umask specified for ftpd on the command line. Closed PR #1530
|
|
Fixes ' no more 'WARNING: preposterous clock chip time' on 164SX
|
|
|
|
|
|
(XXX - I couldn't find a better place to put it.).
|
|
Call system() with a list to avoid a call to sh
|
|
specify a username (and thus avoid rebuilding the while database).
|
|
This lives in libutil because it uses pw_lock(3) and friends. Needs
a man page (soon!).
|
|
Crank the shlib major number due to the interface change.
|
|
I've also restructured things a bit to cut the number of master.passwd
parses in half from 6 to 3. We can't really get away with fewer than
that without sacrificing locality in the .db files.
|
|
The powerpc specific code was previously handling system call errors
as if kernel threads existed (currently only userlang threads are modeled).
Thus if multiple threads existed in a process, the process would not
get the correct errno from a system call. This would cause _many_ tests
to fail. Fixing this causes a number of the tests in libc_r/TEST to now work,
that did not before, however a few still fail.
|
|
In adduser, use /etc/ptmp as a lock file like the other passwd programs.
Currently it is just kept empty which is not so great.
Use sysopen() with explicit file modes so there is no race whereby
a user could see the contents on the master.passwd temp file in rmuser.
Fix order of file opens in rmuser so we don't try and remove anything
unless we can lock all our files.
|
|
wording to something unambiguous.
|
|
|
|
Looks like only vax cares about this.
|
|
reasonable defaults for RSA1/RSA/DSA keys.
|
|
|
|
|
|
|
|
From NetBSD.
Fixes pciide on 164sx.
|
|
|
|
Include errno.h, not sys/errno.h since this is userland
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Its main failing is that ar headers are NOT null terminated.
This code is atrocious. This change starts cleaning that up.
Replace the list of cached archives with a hash,
streamline the logic of ArchMTimeMember,
by taking out the actual function that does the reading (read_archive).
More fixes to come.
|
|
Define two possible interfaces: the classic one,
and the new one (used where available) that depends on timespec.
Better granularity, make is now able to distinguish between files that
were built during the same second.
|
|
and expand it directly, without needing a variable context.
Use it in Var_SubstVar, so that .for loops values don't need to be entered
into any context nor looked up.
This speeds up .for loops some, and avoids nasty variable capture
side-effects.
Ok'd millert@, miod@, naddy@ (naddy spotted a problem with the first
version of that change).
|
|
* Buf_Destroy can be a macro
* X_ instead of _X for struct names, to avoid infringing on the system's
namespace.
* better wildcard detection heuristics
* fix #ifdef CLEANUP code
* a few comments
|
|
modifier keys (SHIFT, CTRL, ALT, etc.), and a key "up" event is received,
only delete the key repeat timeout if the key that generated the "up"
event is the key currently being repeated. When a key "down" event is
received, the opposite -- only delete the key repeat if the key that generated
the "down" event is _not_ the key currently being repeated.
Playing here is a bit dangerous since we are constraining the conditions in
which a timeout(9) is deleted (we don't want to mistakenly get stuck in a
non-legitamite key repeat).
Using timeout(9) for this is kind of gross. I guess it is done here to avoid
key repeat code in all of the actual hardware keyboard drivers.
There is still a bug here. If you have a key held down and detach your
keyboard (by either unplugging it or doing a KVM switch), the timeout is not
deleted and the key continues to repeat until it gets the keyboard back and
receives an interrupt. Perhaps we should not be ignoring typematic keys after
all?
|
|
|
|
- on AF_INET6, :: does not mean local node.
|
|
|
