| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
old version of bzlib.h can be picked up from the /usr/include.
|
| |
|
|
|
|
|
|
|
| |
bzip2 support provided, and amd64 depended on. Amd64 has a custom
${.OBJDIR}/machine symlink in it and the -I. picked this up. Without
it, the libstand code was being compiled in 32 bit mode, but with 64 bit
machine headers.
|
| |
|
| |
|
| |
|
|
|
|
| |
maintainable why of handling them is created.
|
| |
|
|
|
|
|
| |
PR: 75574
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp> (original version)
|
|
|
|
|
|
|
|
| |
NOINFO -> NO_INFO
NOINFOCOMPRESS -> NO_INFOCOMPRESS
NOLINT -> NO_LINT
NOPIC -> NO_PIC
NOPROFILE -> NO_PROFILE
|
|
|
|
| |
any fake value.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
since otherwise the initial seek offset will contain the directory
offset of the filesystem block that contained its directory entry.
This bug was mostly harmless because typically the directory is
less than one filesystem block in size so the offset would be zero.
It did however generally break loading a kernel from the (large)
kernel compile directory.
Also reset the seek pointer when a new inode is opened in read_inode(),
though this is not actually necessary now because all callers set
it afterwards.
|
|
|
|
| |
Discussed with: ru
|
|
|
|
|
|
| |
PR: 68849
Submitted by: Michel Lavondes <fox@vader.aacc.cc.md.us>
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
unsigned char by default). This is a no-op on all other current arches.
Tested by: md5 sum before/after same on i386
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- bzipfs and gzipfs now properly return errno values directly from their
read routines rather than returning -1.
- missing errno values on error returns for the seek routines on almost
all filesystems were added.
- fstat() now returns -1 if an error occurs rather than ignoring it.
- nfs's readdir() routine now reports valid errno values if an error or
EOF occurs rather than EPERM (It was just returning 0 for success and
1 for failure).
- nullfs used the wrong semantics for every function besides close() and
seek(). Getting it right for close() appears to be an accident at that.
- read() for buffered files no longer returns 0 (EOF) if an error occurs,
but returns -1 instead.
|
|
|
|
|
|
|
| |
associated floppy if needed into a static split_openfile() function.
- Use this function in splitfs_open() to open the first chunk rather
than using open() directly. This allows the first chunk to be located
on a different disk than the actual foo.split file.
|
|
|
|
| |
within a single function.
|
|
|
|
|
|
| |
numbers aren't pointers.
- Add a __printflike() attribute to libstand's panic() prototype to catch
such bogons in the future.
|
| |
|
|
|
|
|
| |
to e.g. correctly load all .ko.gz's I've tried, as opposed to messing
up trying to read section headers on some of them.
|
|
|
|
|
|
| |
- include ashldi3.c/ashrdi3.c from libc for UFS 64-bit arith
- pull in syncicache.c from libc, and define _STANDALONE for
loader usage
|
|
|
|
| |
it gets passed through the filter functions.
|
| |
|
|
|
|
|
|
|
| |
symbols from intermediate object files, so these hacks to
get AMD64 compile are no longer needed.
Tested on: sledge.FreeBSD.org
|
| |
|
|
|
|
| |
malloc() to Malloc(), and free() to Free(), in zalloc_malloc.c.
|
|
|
|
|
| |
statements about pointer data type sizes, which spread probably
by copy-and-paste.
|
| |
|
|
|
|
| |
The .Nm library
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file in the NFS file system when the underlying device is not a
network device. A Sparc64 specific hack for this exact problem was
already present (nfs.c:1.9, tftp.c:1.10), but the problem is not
specific to Sparc64. The hack has been promoted to a non-i386 test
because on non-i386 architectures it's either impossible to have
non-network devices coexist in the same loader with the NFS FS, or
network and non-network device coexist and NFS filesystems can only
be used on top of network devices. I believe i386 pxeboot is where
this does not hold.
The root cause of this problem is in open.c where each file system
is tried until no more file systems exist or a file system returns
success. There's no notion of a list of valid file systems given
the underlying device and the non-existence of a file can cause
the invalid combination to be tried.
|
|
|
|
|
|
| |
contiguous chunks of memory. It happens to do so in the bootstrap
code, but not necessarily in other places.
MFC after: 7 days
|
| |
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
| |
format. The one in sys/boot/libstand is not connected to the build.
Approved by: re
|
|
|
|
| |
CLEANFILES. We were not cleaning up after ourselves.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
called <machine/_types.h>.
o <machine/ansi.h> will continue to live so it can define MD clock
macros, which are only MD because of gratuitous differences between
architectures.
o Change all headers to make use of this. This mainly involves
changing:
#ifdef _BSD_FOO_T_
typedef _BSD_FOO_T_ foo_t;
#undef _BSD_FOO_T_
#endif
to:
#ifndef _FOO_T_DECLARED
typedef __foo_t foo_t;
#define _FOO_T_DECLARED
#endif
Concept by: bde
Reviewed by: jake, obrien
|
| |
|
|
|
|
| |
to pick up, ala pxe.
|
|
|
|
|
|
|
|
|
|
|
|
| |
info. This turned out to be rather useful on ia64 for tracking down
malloc/free problems.
Detect duplicate free()'s - otherwise these show up as a guard1 failure
and it looks like corruption instead of something simple like a second
free() where there shouldn't be.
Deal with libz using libc headers and not seeing the malloc/free stuff that
we provide in libstand. Do similar nastiness to what is done for bzlib.
Tested on: i386, ia64 (compile, run)
|