summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sade/install.c
Commit message (Collapse)AuthorAgeFilesLines
* Switch to using XFree86 version 4. We do this thru installing the package,obrien2002-04-021-0/+17
| | | | | | | | so know we have proper PKG registration and dependency information. This is a WIP for 5.0 DP #1, so it is still rough around the edges and does not GC the old XFree86 3.3.6 handling stuff that should be GC'ed. Sponsored by: FreeBSD Mall, Inc.
* Our persistent-state, large temporary file dir is /VAR/tmp, not /USR/tmp.obrien2002-04-011-1/+1
|
* Reword the ``Please remove the FreeBSD fixit CDROM now.'' tobrian2002-02-081-1/+1
| | | | | | ``Please remove the FreeBSD fixit CDROM/DVD now.''. MFC after: 2 weeks
* Unbreak installation for the CD-ROM and possiblhy other media types.green2002-01-141-2/+2
| | | | | Obtained from: LOMAC project Sponsored by: DARPA, NAI Labs
* Revert rev 1.316 now that the bootstrap issues with filesystems usingsheldonh2002-01-141-4/+0
| | | | | | | | block sizees larger than 8192 bytes have been resolved, as per the following deltas: rev 1.34 src/sys/boot/i386/boot2/boot2.c rev 1.5 src/sys/boot/alpha/boot1/sys.c
* According to jhb, the alpha bootstrap code depends on the rootsheldonh2002-01-071-0/+4
| | | | | | | | | filesystem using a block size of 8192. Since this seems unlikely to be fixed soon (specifically in time for 4.5-RELEASE on the RELENG_4 branch), fall back to the old default block and frag sizes of 8192 and 1024 in sysinstall on the alpha. Reported by: jhb
* Update the default newfs block and fragment sizes from 8192/1024 tosheldonh2001-12-111-1/+1
| | | | | | | | | | | | | | | | | | | 16384/2048. Following recent discussions on the -arch mailing list, involving dillon and mckusick, this change parallels the one made over a decade ago when the default was bumped up from 4096/512. This should provide significant performance improvements for most folks, less significant performance losses for a few folks and wasted space lost to large fragments for many folks. For discussion, please see the following thread in the -arch archive: Subject: Using a larger block size on large filesystems The discussion ceases to be relevant when the issue of partitioning schemes is raised.
* Fix the mouse question again to only run the mouse menu if a user doesn'tjhb2001-12-101-1/+1
| | | | | | | | | | have a USB mouse. Here's the deal on how this works: USB mouse have moused run for them automatically by usbd so we don't need to setup moused for them. We do need to setup moused for other mice though, so if the user has a USB mouse, we don't need to do anything. Hence the wording "Do you have a non-USB mouse installed?" for the question. The question can be reworded as "Do you have a PS/2 or Serial mouse installed?" instead if that is preferred.
* Add auto-fill-on-delete. When deleting an 'A'uto created partitiondillon2001-12-091-12/+12
| | | | | | | | | | | | | | | | sysinstall will automatically expand the previous partition to take up the freed up space. So you can 'D'elete /home and /usr will get the combined space, or you can 'D'elete /tmp and /var will get the combined space. This gives the user, developer, or lay person a huge amount of flexibility in constructing partitions from an 'A'uto base. It takes only 3 or 4 keystrokes to achieve virtually any combination of having or not having a /tmp and/or /home after doing an 'A'uto create. Change 'A'uto creation of /var/tmp to 'A'uto creation /tmp, which should be less controversial. MFC after: 6 days
* Cleanup sysinstall's 'A'uto partitioning mode to provide more reasonabledillon2001-12-091-9/+53
| | | | | | | | | | | | | | defaults both in regards to the size of the partitions that are created and in regards to safety and functional separation. Still TODO: extend the previous partition to cover a deleted partition if the previous partiton was auto-created, and supply some sort of solution for /tmp. Reviewed by: Just about everyone Approved by: Nobody except maybe my pet mouse fred Obtained from: God, so complain to HIM MFC after: 1 week
* Sysinstall cleanups for installation:matusita2001-12-021-19/+28
| | | | | | | | | 1) Use devfs to mount filesystems. If mounting devfs is fail, fallback to old code. 2) When fscking filesystems, use 'fsck_ffs' explicitly. As a result, we no longer need 'fsck' the wrapper program. Reviewed by: jkh
* Remove kget() feature, which is removed from 5-current kernel.matusita2001-12-011-9/+0
| | | | | | | | | Since userconfig feature is implemented by tweaking variables (hint.*) with loader(8), we can put back an equivalent feature. Maybe the first step for this is to commit yokota-san's patch (add userconfig command for loader). Approved by: jkh
* Remove the ``-c 22'' option from newfs command line. Changes in newfs(8)roberto2001-10-201-1/+1
| | | | | | | | makes that obsolete. The jury^W-arch is still out about the block and fragment sizes so I'll that for later. Reminded by: obrien MFC after: 2 days
* DTRT in the restart casejkh2001-10-121-1/+1
|
* Silence more warnings.murray2001-09-221-1/+1
|
* Add missing {}. This made most/all scripted installs fail.phk2001-09-141-1/+2
| | | | Approved by: jkh
* Update the inetd configuration prompt for clarity.murray2001-09-051-1/+1
| | | | | Submitted by: chern Committed from: "Make sysinstall suck less party", D1031 WRS campus, Alameda
* Revisions 1.117 and 1.118 of tcpip.c fixed the logic dealing with DHCPmurray2001-09-041-2/+0
| | | | | | | | | | | | | | | | and RTSOL in sysinstall. If the respective TRY_FOO variable is set to "YES" then it will be tried without prompting the user. However, if the TRY_FOO variable is set to "NO" then the user will not be prompted for a choice. This is the correct behavior, since we want people to be able to script sysinstall in either case. However, the default TRY_FOO variable has been "NO" since 1999. This is incorrect, and when the logic was corrected in tcpip.c this has the effect of never giving the user a choice to use DHCP or IPv6. The value should be undefined until it is set by a script or by the user. Submitted by: Randy Pratt, Chern Lee, many others.
* Since we now install sysinstall in /usr/sbin, encourage the user torwatson2001-09-041-1/+1
| | | | run that version, rather than the copy in /stand.
* o Improve terminology consistency for security profile functionality:rwatson2001-08-151-1/+1
| | | | | | | | | the name for the moderate security profile is "moderate", not "medium", so update this one reference to it as "medium". This is a 4.4-RELEASE MFC candidate. MFC after: 2 days
* Compensate for default disabling of network services in inetd.conf(5)rwatson2001-08-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | by providing the opportunity to edit inetd.conf during the system installation process. The following modifications were made: (1) Expand the Anonymous FTP description dialog to indicate that inetd and ftpd must be enabled before it can be used. (2) Introduce a new configInetd() pair of dialogs, the first describing inetd, giving a couple of examples of services that require it, and hinting at potential risk, then asking the user if they wish to enable it. The second indicates that inetd.conf must be configured to enabled specific services, and asks if the user would like to load inetd.conf into the editor to modify it. Add this configuration action to the index. There are some further improvements that might be considered: (1) Provide a more inetd.conf-specific configuration tool that speaks inetd.conf(5). However, this is made difficult by the "yet another configuration format" nature of inetd.conf, as well as its use of commenting to disable services, rather than an in-syntax way to disable a service without commenting it out. Submissions here would probably be welcome. (2) There's some overlap between settings in the somewhat obtuse Security Profile mechanism and other settings, including the inetd setting, and NFS server configuration. As features become individually tunable, they should probably be removed from the security profile mechanism. Otherwise, somewhat counter-intuitively, sysinstall (in practice) queries multiple times whether inetd, nfsd, etc, should be enabled/disabled. A possible future direction might be to drive profiles not by degree of paranoia, rather, the set of services desired. Or simply to remove the Security Profile mechanism and resort to feature-driven configuration. Reviewed by: imp, chris, jake, nate, -arch, -stable
* Add ability to configure console terminal type in /etc/ttysache2001-07-171-0/+1
| | | | Reviewed by: audit, jkh's silence
* Fix the type of the NULL arg to execl()brian2001-07-091-1/+1
| | | | Idea from: Theo de Raadt <deraadt@openbsd.org>
* Bring back part of rev. 1.296 I accidently reverted in the previousdd2001-07-021-1/+1
| | | | commit.
* Introduce DEVICE_INIT, DEVICE_GET, and DEVICE_SHUTDOWN macros. As thedd2001-07-021-5/+6
| | | | | | | | | names suggest, they perform methods on Device's. In addition, they check that the pointer passed to them is valid; if it isn't, they pretend that the action failed. This fixes some crashes due to NULL dereferences (e.g., PR 26509). Approved by: jkh (some time ago)
* Various changes to the messages so that they are now appropriate for bothnik2001-06-271-5/+5
| | | | CD and DVD releases of FreeBSD.
* - sys/msdosfs moved to sys/fs/msdosfsru2001-05-251-1/+1
| | | | | - msdos.ko renamed to msdosfs.ko - /usr/include/msdosfs moved to /usr/include/fs/msdosfs
* Make /compat a relative symlink instead of an absolute symlink.jkh2001-05-191-2/+2
| | | | Requested by: jens
* Mirror the newfs(8) defaults change I made in rev 1.33 of newfs.c whereobrien2001-03-271-1/+1
| | | | I made `22' the default number of cylinders per group.
* Switch from lynx to "links" as the default doc browser.jkh2001-03-231-2/+2
| | | | Submitted by: jim
* Allow a script-using to disable the emergency holographic shell asjkh2001-03-121-1/+2
| | | | | | a security measure. Requested by: "David E. Cross" <crossd@enterprise.cs.rpi.edu>
* Support setting soft updates from the label editor.jkh2001-03-101-0/+7
|
* Fix an informational message a little and properly check status of a yes/nojkh2000-12-161-1/+1
| | | | question which I bollicked up in my previous commit.
* Adapt sysinstall to use the new msgNoYes() function which assumesjkh2000-12-141-12/+10
| | | | | | no as a default. Sysinstall should be both less dangerous and less annoying as a result of this change, though that's just my opinion (since they're the defaults which annoy ME the least :).
* Remove extra ")".kuriyama2000-11-231-1/+1
|
* Back out change to prepend /sbin:/bin to $PATH, just overwrite $PATHtruckman2000-11-051-0/+2
| | | | | | | with these in the normal case. Set MAKEDEVPATH in sysinstall to include the /mnt2 stuff before starting the fixit shell.
* Changes have been made to support a concept of VAR_FIXIT_TTY beingjkh2000-10-301-16/+25
| | | | | | | | | | | | | | | | | standard or serial. This change needs to be done to the entire system that depends on this. This way we don't have some code using OnVTY checks and other doing strcmp(variable_get(VAR_FIXIT_TTY), "standard") == 0 checks. Also we need to set VAR_FIXIT_TTY to "serial" if we come up on a serial console. Also fixed a dialog problem in that dialog was used when dialog was disabled causing some troubles such as not letting the cursor keys work when exiting the fixit mode on media (ie. not the fixit shell but for example fixit on a floppy). Submitted by: Doug Ambrisko <ambrisko@whistle.com> PR: 22352
* If user selects no distributions at all, assume "User" asjkh2000-10-051-3/+6
| | | | | | | | a default. This should prevent people from whacking return at the Distributions menu and getting nothing selected as a result (a minimal "standard" system will at least install). Flagged as big tech support headache by: Chris Shumway <cshumway@osd.bsdi.com>
* Adjust for new location and name of kernel.jkh2000-09-291-33/+17
| | | | | PR: 21423 Reported by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
* Fix a small bogon with a boolean yes/no question check.jkh2000-09-251-2/+2
|
* One small tweak on the security profile code; don't be verbose ifjkh2000-09-241-2/+2
| | | | | setting up default values for an express/custom install. It would be confusing to see the informational popup completely out of context.
* One whack at the idea of having "security profiles" which select thejkh2000-09-221-0/+15
| | | | | | | | appropriate(?) defaults for "low", "medium" and "high" security environments. Medium is basically what we currently have with a little seat-belt tightening where it made sense. Low is the same as medium but without the tightening. High is positively fascist with nothing turned on by default and an automatic call to 911 if it can find a modem.
* MFS: sync with -stable by removing the now-vestigal X_AS_PKG stuff.jkh2000-09-071-17/+0
|
* Terminate, with extreme prejudice, the USAResident hack whichjkh2000-07-241-38/+0
| | | | | | does bad things to /etc/make.conf in certain situations. Also soften the "don't install crypto from the USA!" messages since, except for RSA (which is still noted), that's not so true anymore.
* Add a terminal entry for xterm; a lot of people are using xtermsjkh2000-07-211-1/+2
| | | | in the serial-installation of FreeBSD.
* Allow the Fix-it functionality to detect that we are on a serial console,obrien2000-07-181-0/+5
| | | | | | | | and DTRT rather than start the fixit shell on a non-existant vty. PR: 19837 Submitted by: Doug Ambrisko <ambrisko@whistle.com> Approved by: JKH
* IPv6 support.ume2000-07-141-0/+1
| | | | | | | | | | | IPv6 configuration is only done by rtsol. Does someone really need manual configuration? :-) You can specify IPv6 DNS server as well. We have only one server ftp7.jp.freebsd.org that speaks IPv6 in this time. ftp7.jp speaks IPv4 as well and also listed as Japan #7. Approved by: jkh
* Finish the /dev/rXXX removal job. With the libdisk fixes, this shouldmsmith2000-05-311-3/+3
| | | | actually work again.
* Add an option to select the Fix-it tty. The current behavior is utterlyobrien2000-05-161-9/+19
| | | | *useless* on serial consoled machines.
* Add support for USB to sysinstall. This includes running usbd andjhb2000-05-121-1/+1
| | | | | | setting 'usbd_enable' in rc.conf during nwe installs if USB is detected. Also, since usbd already handles USB mice automatically, note that the mouse setup section in sysinstall only applies to non-USB mice.
OpenPOWER on IntegriCloud