"apparently the rev 1 r5000 chips implement 'cvt' incorrectly. the irix
kernel works around this problem by checking each text page mapped into
memory and doing a fixup on the cvt instructions. it tries to maintain
a hash of these pages using fid2() or fid() if fid2() returns ENOSYS.
afs, in an effort to prevent people from doing checkpoints on an afs
filesystem, makes fid2() return EINVAL. this also keeps the kernel from
mapping executables that are in afs space on the broken r5000's.
this is the patch i have been using for the past couple years while
waiting for an official fix. it makes fid2() return ENOSYS, so you
now need to have to have v_ckpt. however i disabled the rest of the
CKPT code since i have no idea how well that code actually works.
additionally, this behavior is only functional on machines with the
'broken' r5000 h/w. i cant think of a better way to fix this problem
since i cant change the irix kernel."
let hash_enum iterate so we get the right interface
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
undo chas's earlier patch
fix another flub
rxi_MatchIfnet() always returns 0 (i.e. not a match). so rxi_FindIfnet()
will always return 0 and the ADAPT_MTU code can never determine the
interface (and its mtu)
fix by returning 1 if we have a match_value
don't succeed configuring if we can't build for them
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
don't look at the generated files
first pass at afs-nfs translator for solaris. it has not a prayer of
working. i don't really have time to work on it, hopefully someone will
see it and care.
based on complaint from and work with jimmy@e.kth.se
h_OtherHolds_r will never return 0 if we mask our own hold
bit before calling it. however we must be careful to mask before h_TossStuff_r
so we aren't still "holding" then
otherwise just release our hold
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
mask holdbit in case i missed
Modularize the Linux RC file(s) a bit. In particular, add more
options for larger caches, allow autogeneration of the cacheinfo file,
make sure AFS only starts if the network is running, add SuSE header
information, and cope with the Red Hat initscripts better (on Red Hat
only, but should work on all systems).
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
fix silly typo
The result is that if afsd is started with "-dynroot", /afs
will be a locally-generated directory, with mountpoints for every
cell in CellServDB (and /afs/.cellname as the rw mountpoint). If
AFSDB support is also enabled, attempting to access /afs/foo will
cause the cache manager to do an AFSDB lookup on foo, similar to
an automounter. Cell aliases become symlinks to the real cell
names under /afs.
This patch adds support for "cell aliases": a cell alias allows a
single cell to be known by multiple names (one of them the primary).
This is useful in conjunction with AFSDB support, where you want all
the possible names for the same cell to share the same tokens, etc.
For instance, if the local resolver has "mit.edu" in its search
domain, an AFSDB lookup on cell "athena" will cause the primary
cell "athena.mit.edu" to be created, and "athena" made an alias
for it.
make the buffer cache release
the buffer hash lock before trying to open the corresponding file.
Since we're already holding a buffer cache entry, we can lock it
instead and let other threads obtain the big hash lock.
not tsm support can be configure'd on
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
gmake wasn't part of the deal
use a single file for most of both configure scripts
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
except don't require autoconf 2.50
The attached patch adds a program named 'livesys' to the venus directory.
This program has exactly the same interface as 'sys', but actually does a
pioctl to find out the current sysname instead of printing a value
compiled into it. It is intended for sites who want 'sys' to report the
active, locally-assigned sysname of the machine on which it is run.
The bosserver now logs the exit status of processes under its control.
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Messages generated as the result of assertion failures now include
timestamps.
- Adds the -crypt option, which causes rx connections to be encrypted
- Adds the 'vos setfields' command, which allows volume info fields to
be set. Currently, this command allows a volume's quota to be set,
and allows its dayuse counter to be manually cleared. At present,
no other changes are supported by the volserver RPC interface.
- Adds the 'vos changeloc' command, which allows the VLDB's idea of the
location of an RW volume to be explicitly changed without actually
moving the volume. This can be used in cases where the VLDB has the
wrong idea of the location of a volume for some reason. It is
somewhat more predictable and easy to understand than the syncserv
and syncvldb commands.
- Adds the -offline option to 'vos restore'. This option causes the
restored volume to be left offline. This functionality was already
present in the code but previously had no user interface.
- Adds the -readonly option to 'vos restore'. This option causes the
restored volume to be an RO volume. It is not permitted to restore
an RO volume when the associated RW volume already exists. While
it is possible to restore an RW volume where an RO volume exists,
caution should be used to avoid doing this with VLDB entries created
by 'vos restore -readonly', since such entries have their ROVOL and
RWVOL ID's set to the same thing.
