| Age | Commit message (Collapse) | Author |
|---|
|
- 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.
|
|
|
|
|
|
- { foo ; bar ; } -> { foo; bar; }
- if foo ; then -> if foo; then
OK halex@
|
|
|
|
internal-signing, because the procedures ran into some snags we can't
fix in time for release...
|
|
|
|
|
|
ok todd
|
|
We can remove the hashing support.
|
|
media to give some upcoming changes a chance of working.
Long discussions with todd and rpe
|
|
not support cpio anymore.
|
|
this is because the md5/sha256/sha512 are in the same binary, found in the
md5 directory, but the version on the media lacks md5 support. Understand?
|
|
|
|
abomination.
install.sub chunk tested by rpe
|
|
pick binaries up must be compiled -static or at least in some safe
model for reuse. Since we now use distrib/special for those, we can
safely remove usr.bin and usr.sbin from this list.
|
|
diff from Philipp e1c1bac6253dc54a1e89ddc046585792 at osteo dot net
ok krw@ halex@
|
|
|
|
|
|
Add the new files to the clean target's rm list.
"why not get it tested?" deraadt@
|
|
interface and route configuration via ioctl's and routing sockets.
This will break configurations using local enhancements of
dhclient-script, which will now require alternate arrangements.
Committing early to allow time to identify and develop required
alternatives.
Several proddings by deraadt@.
|
|
disk, rather than including it in the ramdisk
tested by landry
|
|
ok krw@
|
|
Note: more stays, though we currently use less on the media -- that is
because if less grows too fat in the future, we would be able to switch
to more.
Discussed with nicm.
|
|
|
|
we could as well pull the 'mv bsd.mp bsd' and the associated checks
out of there.
ok deraadt@ "makes sense" todd@
|
|
In effect, this removes the "old" vndX nodes, and renames
the svndX nodes to vndX.
Old svndX nodes will still continue to work though, for now.
Cleanup accordingly.
ok deraadt@, todd@
comments and ok on the man page bits from jmc@
|
|
/etc/fstab, after asking user. Current default is existing behaviour.
Feedback & suggestions deraadt@, halex@, jsing@, todd@.
ok deraadt@
|
|
|
|
|
|
|
|
like this
|
|
|
