| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
time initializing them. This almost finishes centralizing (in-core)
timestamp updates in ufs_itimes().
|
| |
|
|
|
|
|
|
|
|
| |
is enough to satisfy things like StarOffice. This is a hack, but doing
it properly would be a LOT of work, and would require extensive grovelling
around in the user address space to find the argv[].
Obtained from: Mostly from Andrzej Bialecki <abial@nask.pl>.
|
|
|
|
| |
without traces of Win95 default to short file names, as before.
|
|
|
|
|
|
|
|
|
| |
Noticed by: Carl Mascott <cmascott@world.std.com>
Don't write access time of a file more than once per day. (Its precision is
1 day anyway). Don't try to write access and creation time in nonwin95 case.
Suggested by: bde (long time ago).
|
| |
|
|
|
|
|
| |
since before rev.1.1, so UMAPFS_DIAGNOSTIC should not be trusted.
UMAPFS_DIAGNOSTIC is commented out in LINT to hide various bugs.
|
| |
|
| |
|
|
|
|
| |
and local variables, goto labels, and functions declared but not defined.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for possible buffer overflow problems. Replaced most sprintf()'s
with snprintf(); for others cases, added terminating NUL bytes where
appropriate, replaced constants like "16" with sizeof(), etc.
These changes include several bug fixes, but most changes are for
maintainability's sake. Any instance where it wasn't "immediately
obvious" that a buffer overflow could not occur was made safer.
Reviewed by: Bruce Evans <bde@zeta.org.au>
Reviewed by: Matthew Dillon <dillon@apollo.backplane.com>
Reviewed by: Mike Spengler <mks@networkcs.com>
|
| |
|
|
|
|
|
| |
PR: 8383
Submitted by: Carl Mascott <cmascott@world.std.com>
|
|
|
|
|
| |
tcsetpgrp() on controlling terminals that are no longer associated
with the session of the calling process, not to mention ioctl.2.
|
|
|
|
|
| |
PR: 8383
(Mostly) Submitted by: Carl Mascott <cmascott@world.std.com>
|
| |
|
|
|
|
| |
modeventhand_t.
|
|
|
|
|
|
|
| |
be ok; new veni will check /dev/cfs0 to make sure that a new
kernel is running.
Also, a bug in vc_nb_close iff CODA_SIGNAL's were seen has been
fixed.
|
| |
|
|
|
|
|
| |
of temporary variables since they are only used once and their types
were the cause of the warnings.
|
|
|
|
|
|
|
|
|
| |
via VFS_SET(), and "codadev" for the cdevsw entry. From kldstat -v:
3 1 0xf02c5000 115d8 coda.ko
Contains modules:
Id Name
2 codadev
3 coda
|
|
|
|
| |
set up when unionfs is present, either statically or as a kld module.
|
|
|
|
| |
rather than abusing the list next pointer with a magic number.
|
| |
|
|
|
|
|
|
|
| |
client programs are allowed to finish up (coda_call is
forced to complete) and release their locks. Thus there
is a reasonable chance that the vflush implicit in the
unmount will not get hung on held locks.
|
|
|
|
|
|
| |
a creat so that we can will allow a mode 444 file to be
written into. Sync with the latest coda.h and deal with
collateral damage.
|
|
|
|
| |
the caller can select either inactive or active queue to put the page on.
|
|
|
|
| |
them.
|
|
|
|
|
| |
when bdevsw[] became sparse. We still depend on magic to avoid having to
check that (v_rdev) device numbers in vnodes are not NODEV.
|
|
|
|
| |
about unused variables, labels and other lint.
|
|
|
|
|
| |
1. use VFS_LKM vs ACTUALLY_LKM_NOT_KERNEL
2. don't pass -DCODA to lkm build
|
| |
|
| |
|
|
|
|
|
| |
with DEBUG on. Add support for lkm. (The macro's don't work
for me; for a good chuckle look at the end of coda_fbsd.c.)
|
|
|
|
|
| |
This clearly needs alot more thought, and we dont need this to hunt
us down in 3.0-RELEASE.
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
|
|
| |
Cejka Rudolf <cejkar@dcse.fee.vutbr.cz> on freebsd-current in Messaage-Id
<199807141023.MAA09803@kazi.dcse.fee.vutbr.cz>.
Reviewed by: bde
|
| |
|
| |
|
|
|
|
| |
have been changed to coda. (Same for CFS.)
|
|
|
|
|
|
|
|
|
| |
references to them.
The change a couple of days ago to ignore these numbers in statically
configured vfsconf structs was slightly premature because the cd9660,
cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number
in their vfsconf struct.
|
|
|
|
|
| |
for non-root users. Fortunately, the default for vfs.usermount is 0.
Tested by: "Jan B. Koum " <jkb@best.com
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
device drivers about sectors no longer in use.
Device-drivers receive the call through d_strategy, if they have
D_CANFREE in d_flags.
This allows flash based devices to erase the sectors and avoid
pointlessly carrying them around in compactions.
Reviewed by: Kirk Mckusick, bde
Sponsored by: M-Systems (www.m-sys.com)
|
|
|
|
| |
the other objects in vm.
|
| |
|
| |
|
| |
|