was developed as part of Google's Summer of Code 2005 program. This
change adds the kernel code, the mount_tmpfs utility, a regression test
suite and does all other related changes to integrate these.
The file-system is still *experimental*. Therefore, it is disabled by
default in all kernels. However, as typically done, a commented-out
entry is added in them to ease its setup.
Note that I haven't commited the required mountd(8) changes to be able
to export tmpfs file-systems because NFS support is still very unstable
and because, before enabling it, I'd like to do some other changes.
OK'ed by my project mentor, William Studenmund (wrstuden@).
per floppy for a while. (The rest of the sums are ok).
Change the 'padded' size to include all the space in the last 8k block
of the tar file.
Similarly if the image doesn't fit, report the exact amount of overflow.
Since all the x_<prog> get build into crunched binaries (which does a
reachover build these days) I suspect this is entirely unnecessary.
But having deleted x_dmesg we must ensure it doesn't go there.
SPECIAL dmesg srcdir distrib/utils/x_dmesg
line from all the ramdisk 'list' files. dmesg/Makefile will add -DSMALL
if SMALLPROG is defined (which it is by Makefile.crunch).
Recreating the makefile when the crunchgen program has changed is probably
adequate, and it allows a lot of later optimisations to still apply.
In particular:
- the final link for ramdiskbin
- the create of the embedded filesystem
- the inclusion of the ramdisk into the kernel
- compressing the kernel
Unless something else actually requires one of the above.
of 'boot' and 'netbsd'.
This makes it possible for the tar archive to end at the end of the 2.88M
floppy, instead of either 4k before, or 6k after.
Gives us a whole extra 4k.
The very observant might realise that we don't need the final 1024 bytes
of nulls written to the floppy either, so they could be deleted!
named(8) looks for it. You can now really get a caching name server
by simply setting "named=yes" in "/etc/rc.conf" as documented in
The NetBSD Guide. This fixes PR bin/30662 by Christian Hattemer.
used in ioctl routines to do the right thing when the FKIOCTL flag is
passed to the IOCTL routine indicating its a in-kernel VOP_IOCTL call and
indirect addresses provided in the arguments are to be seen as kernel
adresses rather than userland adresses.
A simple substitution and prepending of the `flags' passed on to the ioctl
handler is enough to DTRT.
backing file per attribute type indexed by inode number to hold the extended
attributes.
This is working pretty well on my test systems, except for the "autostart"
feature. I need someone with a better handle on the VFS locking protocol
to go over that.
This is a work-in-progress. There are parts of this that could be re-factored
allowing this approach to be used on other types of file systems.
Adapted from FreeBSD.
It is worth remembering that trailing spaces are significant in the message
files - they cause a line break if the text is auto-filled to the RH margin.
(This is often the case when the text is a format string.)
Note: nothing (yet) checks the number (or type) of the format effectors in
the message strings. I found and fixed one big error, but others will
cause core dumps.
http://www.netbsd.org/People/port-maintainers.html .
Also, clarify some comments, escape a backlash so that the correct
macro for ø is generated, and make sure it's substituted everywhere
in the name.
This script is still not perfect - it will produce incorrect output
the first time that the second portmaster has a hyperlink associated
with his name. For now, though, it generates correct output for
what we've got.
