anyway, and there can't be any solution that will universally work in any
case (make world, cross-compilation, simple `make' without `make world'
after incompatible options have been added to strfile, ...)
data is copyin()'ed to a properly aligned buffer.)
Return EFAULT rather than EINVAL if the sigcontext is inaccessible,
as specified by the documentation.
Submitted by: bde
As of GCC 2.95 these files from libiberty are absolutely required:
ansidecl.h libiberty.h splay-tree.h splay-tree.c
To keep from having to import all of libiberty, they are imported here
for now. Before all is said and done, libiberty might be imported, or
these files might move elsewhere.
As of GCC 2.95 these files:
choose-temp.c demangle.h getopt.h obstack.c pexecute.c
cplus-dem.c getopt.c getopt1.c obstack.h
were removed from the GCC compilers proper to libiberty. To continue our
revision history, and to keep from having to import all of libiberty,
they are imported here as if they were never moved.
breaks the cross-compilation case, but I'm not the one doing it.
$$PATH *will* have a new strfile in /usr/bin built at build-tools
time, unless you defined NOTOOLS.
If you defined NOTOOLS and it breaks for you, don't do that.
If you did not define NOTOOLS but things are not working, the error is
elsewhere. See logs for src/Makefine.inc1, particularly rev 1.36, and
revision 1.14 of this file.
We currently only search SCSI and IDE CDROMs; if there's felt to be a
need for supporting the very old and rare soundcard etc. drives for this
application they can be trivially added.
the soft updates changes: only report the link count to be i_effnlink
in ufs_getattr() for file systems that maintain i_effnlink.
Tested by: Mike Dracopoulos <mdraco@math.uoa.gr>
In order to achieve this, root filesystem mount is moved from
SI_ORDER_FIRST to SI_ORDER_SECOND in the SI_SUB_MOUNT_ROOT sysinit
group. Now, modules which wish to usurp the default root mount
can use SI_ORDER_FIRST.
A compiled-in or preloaded MFS filesystem will become the root
filesystem unless the vfs.root.mountfrom environment variable refers
to a valid bootable device. This will normally only be the case when
the kernel and MFS image have been loaded from a disk which has a
valid /etc/fstab file. In this case, the variable should be manually
overridden in the loader, or the kernel booted with -a. In either
case "mfs:" should be supplied as the new value.
Also fix a typo in one DFLTROOT case that would not have compiled.
