| Age | Commit message (Collapse) | Author |
|---|
|
Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.
Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.
Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)
This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.
OK deraadt
|
|
is required because of TLS servername for contacting ftp.openbsd.org, and
there is no point doing that in resolv.conf.tail because it is no longer used.
ok florian kn
|
|
OK deraadt who also helped making some space.
|
|
|
|
bsd.rd
It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.
ok danj@ deraadt@
|
|
ok deraadt@
|
|
remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.
ok deraadt@ danj@
|
|
the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.
ok deraadt@ danj@
|
|
ok deraadt@ danj@
|
|
"strip -R section" command run "strip" (without option) as well.
there is no need to call both.
(binaries checked with sha1)
original diff from danj@
ok deraadt@
|
|
methods support it. if anyone finds a method which does not work, please
speak up.
|
|
|
|
|
|
|
|
|
|
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@
|
|
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn
|
|
Makes room for upcoming FFS2 support for the installer. ok deraadt@
|
|
|
|
|
|
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..
|
|
moving progress bar during auto upgrade/install and a clean log
afterwards. ok deraadt@
|
|
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)
|
|
|
|
|
|
|
|
|
|
|
|
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..
|
|
|
|
|
|
the sme.
|
|
|
|
|
|
|
|
having two mysterious names, let's settle on one.
|
|
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.
|
|
tightly-built ramdisk kernels, set the option in per-arch Makefile.inc
based upon SMALL_KERNEL
|
|
|
|
|
|
|
|
|
|
ok kevlo@
|
|
random cookies to protect access to function return instructions, with the
effect that the integrity of the return address is protected, and function
return instructions are harder to use in ROP gadgets.
On function entry the return address is combined with a per-function random
cookie and stored in the stack frame. The integrity of this value is verified
before function return, and if this check fails, the program aborts. In this way
RETGUARD is an improved stack protector, since the cookies are per-function. The
verification routine is constructed such that the binary space immediately
before each ret instruction is padded with int03 instructions, which makes these
return instructions difficult to use in ROP gadgets. In the kernel, this has the
effect of removing approximately 50% of total ROP gadgets, and 15% of unique
ROP gadgets compared to the 6.3 release kernel. Function epilogues are
essentially gadget free, leaving only the polymorphic gadgets that result from
jumping into the instruction stream partway through other instructions. Work to
remove these gadgets will continue through other mechanisms.
Remaining work includes adding this mechanism to assembly routines, which must
be done by hand. Many thanks to all those who helped test and provide feedback,
especially deaadt, tb, espie and naddy.
ok deraadt@
|
|
DESTDIR rather than reaching around in src. ok deraadt
|
|
Some resizing scenarios can be done from within single user mode, but
resizing the root partition required you to bring your own growfs(8)
binary into the ramdisk environment. This commit adds growfs(8) to the
ramdisks (the ones that don't have space constraints) to simplify such
operations.
OK deraadt@
|
|
broke amd64/ramdisk_cd as it no longer fit; spotted by jsg@
ok deraadt@ mpi@
|
|
according to the same logic for all architectures but sgi.
Consolidate setting them in one place in install.sub and incorporate
the sgi specific MDSETS and MDSANESETS.
Introduce MDSANESETS complementing MDSETS which makes the construction
of DEFAULTSETS, THESETS and SANESETS clearer in install.sub.
While here, adjust the comment about how MDSETS used now.
OK deraadt@
|
|
clang optimizes better for size with -Oz so use that as a default to avoid
overflowing the ramdisk floppies. gcc now accepts -Oz as an alias for -Os.
ok kettenis@
|
|
|
