Age | Commit message (Collapse) | Author |
|
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@
|
|
multiple bsd.rd. hppa builds one. Fold into one file.
|
|
multiple bsd.rd. hppa builds one. Fold into one file.
|
|
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.
|
|
|
|
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@
|
|
|
|
ok deraadt@
|
|
discussed with deraadt@ mpi@
ok deraadt@ kettenis@ 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@
|
|
|
|
tracked that permission. Make the copy in $RELEASEDIR a+r
|
|
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe
|
|
|
|
as required.
much help from natano and tb.
|
|
The instbin stuff looks good to deraadt@
|
|
Saves precious 896 bytes as a side effect.
OK deraadt
|
|
/tmp with proper permissions so that unprivileged programs can not
tamper with them.
positive feedback from deraadt
OK halex
|
|
/tmp with proper permissions so that unprivileged programs can not
tamper with them.
positive feedback from deraadt
OK halex
|
|
OK halex, tb, deraadt
|
|
- merge upgrade.sh into install.sub as do_upgrade()
- delete install.sh and upgrade.sh
- make install.sub executable
- turn install and upgrade into symbolic links to install.sub
- add autoinstall symbolic link to install.sub
- change dot.profile to use these symlinks
- introduce a -m option to set MODE in install.sub
- alternativly set MODE and AUTO depending on PROGNAME
- execute the do_{install,upgrade) functions depending on $MODE
OK halex@, krw@
'go for it' deraadt@
|
|
verbiage explaining what disklabels are.
If you don't know, you should be using (A)uto!
ok rpe@ halex@
|
|
uses disklabel UIDs unconditionally for a while already.
OK krw@
"looks good" deraadt@
|
|
MI function disklabel_autolayout() which now handles all aspects of
the disklabel auto-layout and autopartitioning case for the root disk.
Remove get_disklabel_template() and merge it with the new function.
"move forward" deraadt@
|
|
to the OpenBSD installer. It is available during unattended installation.
The template file is fetched from an url, provided as answer to a new
question in the response file:
URL to autopartitioning template for disklabel = url
Original diff from and OK henning@
'no objection' krw@
|
|
|
|
|
|
|
|
goal of eventually refactoring them)
|
|
1) add link, so that installboot works by default
2) edit install.md to add sdboot as a parameter, but then default
bsd.rd commandline use fails
3) modify hppa*_installboot.c
for now, we do 1, though i think 3 is the right way
diagnosed with krw, ok jsing
|
|
for LIF/header creation, pre-disklabel. post-install/upgrade, this
gets redone, this time with -r /mnt to pick up the new sdboot file
ok krw jsing miod
|
|
|
|
|
|
bootable, which do contain a LIF yet). It should also be run in
md_installboot for the upgrade case.
Diagnosis with jsing and kettenis, buglet spotted by rpe
Testing... waiting for that.
|
|
version in just installed base.
|
|
|
|
OK deraadt@
|
|
so that valid bytes exist at the end of the kernel image.
Since the lif image stores files size in 256-byte unit, we can not report EOF
while reading the kernel image until the remainder of the 256-byte sector has
been read. But these zero bytes would cause the gzip readahead machinery in
libsa to believe the kernel is followed by an uncompressed file, and switch to
transparent mode, preventing backwards seeks into the kernel image from working.
This fixes the ``read section header string table failed(0)'' errors when
attempting to boot lif.fs since loadfile_elf.c 1.9.
|