Age | Commit message (Collapse) | Author |
|
resistant against memory correctup, if a corrupt filesystem is given to them.
ok krw
|
|
to build boot blocks.
ok miod@
|
|
it are now using MI installboot for that purpose.
ok krw@ deraadt@
|
|
Found by jsg@. OK jsg@ deraadt@
|
|
the changes for handling template files in r1.293, alloc_table became
a pointer to an array of structs (rather than the array itself), so
nitems(alloc_table) no longer returns the number of elements. As found
by sebastia@, autosize would only try the first allocation scheme,
so installation would fail on small disks. ok henning@
|
|
|
|
template gives mountpoints, min-max size ranges and percentage of disk
foremost intended for autoinstalls, installer bits to follow soon.
with input from many, ok theo
|
|
min, otherwise the constraint cannot be satisfied; ok deraadt@ okan@
|
|
delete <sys/param.h> if now possible
ok guenther
|
|
list.
ok krw@ millert@
|
|
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
Avoid potential integer overflow in the size argument of malloc() and
realloc() by using reallocarray() to avoid unchecked multiplication.
ok deraadt@
|
|
OK miod@, deraadt@
|
|
ok otto@ krw@
|
|
Should fix mysterious crashes when twiddling mount points. Too
much Marrakesh sun.
Pointed out by Owain G. Ainsworth. Thanks!
|
|
that appears to fix mysterious crashes seen with previous version that
tried to sneak in to 5.5.
ok otto@
|
|
|
|
permits before release, and is pointless without other following diffs
to justify it that will not make release.
Should fix segfault's during install reported by Rod Whitworth on tech@
|
|
memory to NULL.
|
|
when calling mpfree() with the array.
|
|
mountpoints array.
|
|
Careful second audit by millert
|
|
|
|
|
|
requested by deraadt@
|
|
instead of binary operators for comparison.
OK krw@
|
|
|
|
DEV_BSIZE blocks. Counts of possibly other-sized blocks (e.g. disk
sector addresses) are u_int64_t. The values stored in disklabels are
counts of possibly other-sized blocks and hence should be handled with
u_int64_t variables.
Start enforcing this rule. No intended functional change.
Rule strongly suggested by deraadt@
|
|
test period; i think 3 years ago the last bugs fell out.
ok otto beck others
|
|
|
|
not sectors, since the values being tested/manipulated in the auto_alloc
tables are blocks at that point. Use MEG(256) instead of hand
expanding it when testing physmem.
|
|
change.
|
|
change to executable.
|
|
ok krw@ otto@
|
|
create ffs partitions with invalid fsize and bsize values newfs
will croak on. However, they should be able to set them to whatever
consistent values they want, not just make them smaller.
Also tweak some verbiage.
|
|
i.e. when rounding off various values.
ok deraadt@ sthen@
|
|
editor. Use logic from calculating fragsize for an auto-allocated
partition. Noted when trying to add a small ffs partition to a 4K
sector device.
|
|
|
|
interest of rope sales allow the 'X'pert to suppress the rounding of
partition locations to bsize boundaries. Also mention that such rounding
is being done, so as to not surprise the user.
ok otto@ a while ago
|
|
THEN negate. Fixes issues with 'b' and 'k' size suffixes. Make error
message more clear while here.
Found, and fix provided, by David Imhoff via bugs@. Thanks!
|
|
|
|
place it was missing. Delete now redundant calls to DIOCGDINFO when
getting physical disk info in disklabel(8) and fdisk(8).
Reminded by a fdisk discussion with Andres Perera on tech@.
ok deraadt@
|
|
a ffs frag size can be less than the d_secsize of the disk. Make
sure amd64 writedisklabel() puts the disklabel where readdoslabel()
will read it. Tweak i386/amd64 installboot/biosboot so sectors are
indeed used where sectors are claimed.
Lets me fdisk, newfs, mount and installboot onto 2048 and 4096
byte sector devices. Other filesystem utilites will still hold
surprises.
Note that actually booting from such devices will await BIOSen that
acknowledge such devices as bootable.
ok guenther@
|
|
|
|
bit too small. ok krw@
|
|
partitions); ok krw@
|
|
in auto-allocated labels. ok krw@ sthen@
|
|
updates to follow. This will simplify install script fstab
creation.
ok deraadt@
|
|
information to the specified file. After every label write, read the
label to get current UID info.
Some internal code cleanup with no intended functional change.
ok deraadt@
|
|
available partitions (e.g. many spoofed logical partitions) try
the next scheme rather than giving up.
"sane" deraadt@ ok matthew@
|