Age | Commit message (Collapse) | Author |
|
|
|
by implementing the rules:
Only '/' is neither nodev nor nosuid. i.e. it can obviously *always*
contain devices or setuid programs.
Every other mounted filesystem is nodev. If the user chooses to mount
/dev as a separate filesystem, then on the user's head be it.
The only directories that install puts suid binaries into (as of 3.2)
are:
/sbin
/usr/bin
/usr/sbin
/usr/libexec
/usr/libexec/auth
/usr/X11R6/bin
and ports and users can do who knows what to /usr/local and sub
directories thereof.
So try to ensure that only filesystems that are mounted at or above
these directories can contain suid programs. In the case of
/usr/libexec, give blanket permission for subdirectories.
Note that if *all* the above are split into separate filesystems the
install process will attempt a couple of cross-device links when
installing base32.tgz, and fail.
ok deraadt@.
|
|
|
|
|
|
separating items.
This allows a compaction of the displayed lines for device selection.
Customize the device selection routine so the actual device type is
shown (disk or CD-ROM). Rename ask_fordev to ask_which so the
invocations (with device type) read better.
|
|
|
|
|
|
|
|
|
|
$ROOTDEV and ${ROOTDISK}b can be used for swap. Also shortens output
generated during (successful) install.
Fix problem with upgrade on systems with many disk devices by
automatically creating devices encountered during the fsck'ing of fstab
filesystems. Problem noted by Dethlef Madsen and Nick Nauwelaerts.
Adjust some verbiage in i386 install.md to make it more consistant.
Reformat welcome message to make sure all lines are <80 characters wide.
Minor cleanups.
|
|
output produced when the user opts to have the install script use the
entire disk for OpenBSD.
ok deraadt@.
|
|
|
|
|
|
|
|
|
|
the install example will easily fit on the CD insert at some
reasonable font size. Reword many messages and questions for same
reason.
In addition:
1) Add '...done.' to match 'Installing boot block...'
2) During install, after asking which is the root disk, start
initializing it immediately rather than asking again which disk to
work on.
3) Move munged fstab filesystem mounting to *before* network
initialization so that if you bail out during network initialization
and restart you do not have to go through disk initialization again.
Also puts fsck and mount messages close to each other rather than
spitting out the latter just before root password questions.
4) Make 'usr/obj' nosuid,nodev by default, /home nodev by default.
5) For network interfaces only show the complete list of media options
if the user indicates they want to change the default.
6) Move the question about the ftp server supporting passive ftp to
*after* selecting the ftp server where it is more 'rational' and can
easily be made more concise.
7) Don't bother umount'ing filesystems or stopping the dhclient after
a successful install/upgrade. The next step is a reboot after all.
Some minor code tweaks and comment cleanup while in the area.
Tested in recent snapshots. Suggested by & ok deraadt@.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the VSIMM in the dmesg.
|
|
this series.
Thanks to Andrey Smagin (andrey at smagin dot com) for providing a VS10 card.
|
|
|
|
|
|
disabling of '(U)pgrade' in architectures by adding
REMOVE upgrade
to the end of the 'list' file for that architecture.
Add code to dot.profile to check for the presence of the upgrade
script before offering to (U)pgrade.
Use the new verb to disable upgrades for sparc.
ok deraadt@.
|
|
|
|
|
|
routine to install.sh so it is displayed only once.
Strongly advise /, /tmp, /var, /usr and /home have their own
disk partitions as requested by deraadt@.
Rather than rely on users not re-selecting an already initialized
disk, just allow them to choose from un-initialized disks.
Move get_root invocation into install.sub as both install.sh and
upgrade.sh did it first thing.
Remove the 'workaround' to a 'vnode aliasing bug' that came in
with the initial import of upgrade.sh from NetBSD. ok millert@.
Rework verbiage in a few places. Clean up logic around looping
through disk units by handling root disk better.
|
|
|
|
1) Correctly sort >10 total partitions.
2) Don't allow user to specify duplicate mount points via
disklabel.
3) Fix mount point checking so that empty mount points
do not confuse logic.
4) Fix mount point checking so that duplicate mount points
from previous disk initialization are correctly detected.
5) Show configured partitions/mount points in partition order
(i.e. sorted by disk and then partition) rather than mount
point order. This seems easier to read to me and reflects the
order of user action. Sort the entries after user approval.
6) Clarify, clean up some verbiage and logic.
|
|
|
|
|
|
|
|
|
|
1) Fix 'already mounted' checking so a mount point name can be the same
as the leading substring of a previously specified mount point.
Now you can specify /usr after /usr/obj, and since the mount points
are sorted before writing to fstab, it should work.
This also fixes the error message generated when a requested mount
point matches the leading substring of multiple mount points. e.g.
trying to mount '/' again.
2) Fix fstab sorting so that it works across all initialized disks, not
just on a disk by disk basis.
3) For additional paranoia during multiple disk installs, unset _partitions,
_psizes, and _mount_points before processing a disk. Eliminate individual
blanking of _mount_points entries.
4) Shorten/simplify logic by storing ${DISK} in _partitions entries rather
than always adding it back in when referencing _partitions.
5) Rework verbiage a bit, eliminating the duplicate display of configured
devices before making new filesystems.
Some code clean up, eliminating '{}'s, better loops, ifs, etc.
Appox. 67 bytes net bloat.
|
|
name to be repeatedly appended to the host name. Simply strip
the domain name from the host name read from /tmp/myname.
Problem noted by Nick Holland.
|
|
|
|
|
|
|
|
|
|
complete, documentation is missing, but I'll let someone who knows
the sets fix this properly.
Those pieces at least allow me to finish a usable snapshot.
|
|
of rdsetroot.
|
|
|