| Age | Commit message (Collapse) | Author |
|---|
|
OK jmc@ krw@
|
|
on the eBenton EBT700, for the PMON flavour found on these systems won't
recognize the filesystem correctly otherwise; researched and reported by
Ban Keong Yee.
|
|
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@
|
|
Found by inspection while curious... not though actual experience...
ok miod
|
|
|
|
|
|
goal of eventually refactoring them)
|
|
|
|
Noted by todd@
OK krw@ halex@
|
|
version in just installed base.
|
|
|
|
OK deraadt@
|
|
- { foo ; bar ; } -> { foo; bar; }
- if foo ; then -> if foo; then
OK halex@
|
|
|
|
|
|
We can remove the hashing support.
|
|
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@
|
|
have been *.core files for a very long time. That's a lot of unlink()
calls saved.
|
|
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@.
|
|
|
|
since the latter may insert holes in the target files, which could
be bad for the boot process
ok deraadt@ guenther@
|
|
while the former does not
pointed out by and ok naddy@
|
|
|
|
ok deraadt@ otto@
|
|
ok krw@
|
|
|
|
to elfrdsetroot. Does not yet fix sparc
|
|
Enables developers to build arm ramdisk kernels on amd64 archs
OK deraadt@ 'looked fine' miod@
|
|
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@
|
|
|
|
|
|
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.
|
|
system, or something else.
Derive the fdisk instructions in `use the whole disk for OpenBSD' from this
knowledge, and set up a 32MB ext2fs partition on Gdium, and the 1MB elsewhere
(as was already been done).
On Gdium, format this partition in fancy mode (-O 1) and 4KB blocks, so that
PMON has a chance to load files larger than 4MB (such as bsd.rd)
without failing in a pathetic way, and also copy the kernel image to the ext2fs
partition after the installation has completed.
Note that, apart from creating a larger ext2fs partition on Gdium, there should
be no need for this.
Unfortunately, since regular PMON does not have ext2fs code, Lemote wrote its
own code to access ext2 filesystems. Saying that this code is full of
shortcomings and bugs would be an understatement. What is worse is that this
code has been written by people with no knowledge (or even insight) of how
error conditions ought to be handled, and their ext2fs code will happily
abort a read upon error with no error; if one does not compare the final
read size to the file size obtained by stat(), there is no way to figure out
that the read has been aborted. Of course since regular (upstream) PMON code
is written correctly, it does not expect this, so it is easy to end up with
PMON not loading a kernel image completely, yet proceeding happily to transfer
control to this broken image.
I guess the morale behind this is that system software is too difficult to get
done correctly, to be done by hardware people.
|
|
|
|
redundant comment
|
|
|
|
|
|
existing one) to install the bootloader on.
|
|
|
|
|
|
|
