Linked by Thom Holwerda on Fri 31st Aug 2007 08:35 UTC, submitted by lomax
FreeBSD "Welcome to the home page of the finstall project, accepted for Google's Summer of Code 2007. This project aims to create a user-friendly graphical installer for FreeBSD & FreeBSD-derived systems. The project should yield something usable for 7.0-RELEASE, but the intention is to keep it as a "second" installer system during 7.x, alongside sysinstall. In any case, sysinstall will be kept for architectures not supported by finstall (e.g. all except i386 and amd64)." A first version has been released.
Thread beginning with comment 267368
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Configuration
by Flatland_Spider on Fri 31st Aug 2007 13:41 UTC in reply to "Configuration"
Flatland_Spider
Member since:
2006-09-01

That would be very nice. I'm not afraid of the command line, but the more that can be done from the installer to have a fully configured system after reboot the better.

It would also be helpful if it would have options for adding scripts from /usr/local/etc/rc.d to rc.conf as well. Newbies may not know that added apps put scripts there, and they don't have default lines in rc.conf.

Reply Parent Score: 2

RE[2]: Configuration
by Doc Pain on Sun 2nd Sep 2007 14:42 in reply to "RE: Configuration"
Doc Pain Member since:
2006-10-08

"It would also be helpful if it would have options for adding scripts from /usr/local/etc/rc.d to rc.conf as well. Newbies may not know that added apps put scripts there, and they don't have default lines in rc.conf."

This is correct because of the separation between OS and added applications or services. OS parts are controlled via /etc/rc.conf and the respective /etc/rc.d/* scripts. Local additions reside in /usr/local/etc/rc.d/*, maybe there could be an /usr/local/etc/rc.conf for locally installed services? Usually, you configure local service foo via /usr/local/etc/foo.conf and start / restart / stop it via /usr/local/etc/rc.d/foo.sh followed by the desired parameter.

Of course, FreeBSD preconfiguration and example section (e. g. /etc/defaults/rc.conf, man rc.conf) cannot handle every idea of rc options an additional piece of software that does not belong to the OS itself could have.

NB: FreeBSD is "just" an OS, not a Linux-like OS + applications distributions (such as PC-BSD and DesktopBSD are, built upon FreeBSD OS). Cannot say it often enough. :-)

Reply Parent Score: 2

RE[2]: Configuration
by phoenix on Mon 3rd Sep 2007 19:10 in reply to "RE: Configuration"
phoenix Member since:
2005-07-11

It would also be helpful if it would have options for adding scripts from /usr/local/etc/rc.d to rc.conf as well. Newbies may not know that added apps put scripts there, and they don't have default lines in rc.conf.


An OS installer should do nothing more than install the OS. All OS configuration should be done via the standard OS tools once the OS has been installed and booted.

Why do people keep trying to cram everything under the sun into an install tool?

An installer should let you partition the disk, configure the boot loader, select which parts of the OS to install, then copy bits to the disk.

It shouldn't include configuration tools for applications.

Reply Parent Score: 2

RE[3]: Configuration
by Doc Pain on Tue 4th Sep 2007 22:43 in reply to "RE[2]: Configuration"
Doc Pain Member since:
2006-10-08

"An OS installer should do nothing more than install the OS. All OS configuration should be done via the standard OS tools once the OS has been installed and booted."

These standard tools are sysinstall and your favourite text editor, in most cases. Of course I agree here. Because FreeBSD is "just" an OS, the installer should care about the OS and its settings, not the settings of additional applications.

"Why do people keep trying to cram everything under the sun into an install tool?"

I think this is because users (average ones) cannot see a difference between an OS (which FreeBSD is) and a distribution containing an OS and additional software (which PC-BSD or DesktopBSD are, using the FreeBSD OS). They want to install one medium, run through an installation procedure, and assume to have a full featured, preconfigured and automatically reconfigured system - a unit containing of OS and applications.

"An installer should let you partition the disk, configure the boot loader, select which parts of the OS to install, then copy bits to the disk.

It shouldn't include configuration tools for applications."


To be honest - it cannot include them. The maintainers of the OS and its installer do not have the time to care about every installable piece of software existing out there. So why should the OS installer care? Every additional software should provice a setup tool belonging to this particular piece of software.

Use one tool per task. Use the right tool.

Installation is one thing (package management tools provided by the OS in order to install or update installeble software), configuration is another thing which is best kept inside the respective installable software.

Reply Parent Score: 2