| Age | Commit message (Collapse) | Author |
|---|
|
installboot'ing due to incorrect d_type (must be 'floppy' not
'vnd') in disklabel.
Noticed by deraadt@ and sthen@
|
|
invocations, making the geometry information written to the
disklabel a bit more logically related to the disktab information
from whence it came. Also makes FSDISKTYPE usage consistent.
Flip the disklabel(8) invocations to the "echo '/ *'"
idiom to make it obvious that the desire is to create a single
'a' partition containing all free space.
No intentional functional change. MBRs, disklabels and newfs
outputs appear identical.
reads good to kn@
|
|
confusing users with FFS attributes that only experts should
fiddle with. Actual use has withered away with functionality
rendered moot or moved elsewhere.
'-e' remains for the truly obscure corner cases.
Simply excise the code for now to see if hidden users/uses are
exposed. Further simplifications are possible if no such
users/uses surface.
ok with sthen@ millert@ kn@ otto@
|
|
Tested with Comfast CF-WU710N v4.
"go ahead" deraadt@
OK stsp@
|
|
values for the block/fragment sizes that some install media need.
Hoist the desired values into the newfs(8) invocations to make it
obvious non-default values are required and what the values are.
No functional change.
ok kn@
|
|
ramdisk, so just keep or remove the conditional sections.
ok kn@ miod@
|
|
One new question to cover the most common use case, such that manual setup
in (S)hell or '!' prior to install is no longer required:
Encrypt the root disk? (disk, 'no' or '?' for details) [no] ?
Create a passphrase protected CRYPTO softraid volume to be used as root disk.
Available disks are: sd0.
Encrypt the root disk? (disk, 'no' or '?' for details) [no]
Use of keydisk or different disciplines are not covered.
Only asked in interactive installations; no autoinstall(8) or upgrades.
Only reachable on i386, amd64, sparc64 and riscv64 for now (arm64 WIP).
Tested by cheloha naddy and a few users
Feedback from cheloha deraadt claudio
OK cheloha
"get it in now" deraadt
|
|
|
|
|
|
ok deraadt@
|
|
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.
|
|
When dealing with install floppies, the Makefiles will need to carry
some differences.
|
|
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
|
|
|
|
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@
|
|
DESTDIR rather than reaching around in src. ok deraadt
|
|
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@
|
