| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Reduce overlinking
|
| |
|
|
|
|
|
| |
human-friendly power-of-two numbers (i.e. 2k, 5M etc).
Suggested by: many
MFC after: 1 week
|
| |
|
|
| |
Submitted by: Marius Nünnerich <marius@nuenneri.ch>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
want to prepare disk images for emulators (though 'makefs' in port
can do something similar).
This relies on:
+ minor changes to pass the consistency checks even when working on a file;
+ an additional option, '-p partition' , to specify the disk partition to
initialize;
+ some changes on the I/O routines to deal with partition offsets.
The latter was a bit tricky to implement, see the details in newfs.h:
in newfs, I/O is done through libufs which assumes that the file
descriptor refers to the whole partition. Introducing support for
the offset in libufs would require a non-backward compatible change
in the library, to be dealt with a version bump or with symbol
versioning.
I felt both approaches to be overkill for this specific application,
especially because there might be other changes to libufs that might
become necessary in the near future.
So I used the following trick:
- read access is always done by calling bread() directly, so we just add
the offset in the (few) places that call bread();
- write access is done through bwrite() and sbwrite(), which in turn
calls bwrite(). To avoid rewriting sbwrite(), we supply our own version
of bwrite() here, which takes precedence over the version in libufs.
MFC after: 4 weeks
|
| |
|
|
|
|
|
| |
version of such. Differences in filesystems generated were found to be
from 1) sbwrite with the "all" parameter 2) removal of writecache. The
sbwrite call was made to perform as the original version, and otherwise
this was checked against a version of newfs with the write cache removed.
|
| |
|
|
| |
Reported by: phk
|
| |
|
|
| |
keramida, and all seems well.
|
| |
|
|
|
|
|
|
| |
Add a couple of simple regression tests accessible with "make test", they
depend on the md(4) driver.
FYI I have also tried running the test against a week old newfs and it
passed.
|
| |
|
|
|
|
| |
anyone needs a newfs without it. Remove the #ifdef's from around
the code and the -DFSIRAND from the Makefile. Also remove redundant
declarations of random() and srandomdev().
|
| | |
|
| |
|
|
| |
0 was bad and setting it unconditionally to 2 was worse.
|
| |
|
|
|
|
|
|
| |
Set WARNS=2
This is the beginning of a pre-UFS2 cleanup of newfs.
Sponsored by: DARPA, NAI Labs
|
| |
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
|
|
| |
Don't clutter this Makefile (not to mention the error output) with
$(BDECFLAGS}.
|
| | |
|
| |
|
|
| |
XXX: This program badly needs a style(9) + BDECFLAGS treatment.
|
| | |
|
| |
|
|
| |
- MAN[1-9] -> MAN.
|
| | |
|
| |
|
|
| |
Change its type to u_int_16_t.
|
| |
|
|
| |
the default.
|
| |
|
|
|
|
|
|
|
| |
automatically have random generation numbers. The kenel way of handling those
also changed. Further it is advised to run fsirand on all your nfs exported
filesystems. the code is mostly copied from OpenBSD, with the randomization
chanegd to use /dev/urandom
Reviewed by: Garrett
Obtained from: OpenBSD
|
| |
|
|
|
|
| |
- use new getvfsbyname() and mount(2) interface (mount_mfs)
- use new fs include files
- updated inode / cg layout calculations (?)
|
| | |
|
| |
|
|
|
| |
in `fastboot'/`fasthalt' in which the interpreter would hang around
after `reboot' or `halt' is run, causing an irritating ``Killed'' message.
|
|
|
Note: XNSrouted and routed NOT imported here, they shall be imported with
usr.sbin.
|
