COMP 3000 2011 Report II:PC-BSD - Revision history

Qliu1: /* Initialization */

2011-12-18T16:19:21Z

Initialization

← Older revision		Revision as of 16:19, 18 December 2011
Line 191:		Line 191:
	'''End of Initialization'''		'''End of Initialization'''

	The initialization of PC-BSD is ~~complete~~ after all the thirty two shell scripts from /etc/rc.d have been initialized. The /etc/rc script describes how system startup scripts run by init. There is a loop which reads through and runs all the startup scripts. Initialization is ~~complete~~ when the loop is over. Then all the processes start running on this fully initialized system.		The initialization of PC-BSD is completed after all the thirty two shell scripts from /etc/rc.d have been initialized. The /etc/rc script describes how system startup scripts run by init. There is a loop which reads through and runs all the startup scripts. Initialization is completed when the loop is over. Then all the processes start running on this fully initialized system.

	== Reference ==		== Reference ==
	<references/>		<references/>

Qliu1: /* Initialization */

2011-12-18T16:16:13Z

Initialization

← Older revision		Revision as of 16:16, 18 December 2011
Line 161:		Line 161:
	'''Start Initialization'''		'''Start Initialization'''

	Because PC-BSD is based on FreeBSD, the initialization will be BSD-style~~[1]~~. The init runs the initialization shell script located in /etc/rc.d, then launches a windowing system such as X on graphical terminals under the control of /etc/ttys. There are no runlevels in PC-BSD. The script file, /etc/rc, determines what programs are run by init. The configuration is read from the master configuration file /etc/rc.conf. When we check the /etc/rc.conf file, we can find that the local startup scripts are in /usr/local/etc/rc.d and /Program/rc.d.		Because PC-BSD is based on FreeBSD, the initialization will be BSD-style. The init runs the initialization shell script located in /etc/rc.d, then launches a windowing system such as X on graphical terminals under the control of /etc/ttys. There are no runlevels in PC-BSD. The script file, /etc/rc, determines what programs are run by init. The configuration is read from the master configuration file /etc/rc.conf. When we check the /etc/rc.conf file, we can find that the local startup scripts are in /usr/local/etc/rc.d and /Program/rc.d.

	'''Major Programs'''		'''Major Programs'''

Qliu1: /* Major package versions */

2011-12-18T16:15:48Z

Major package versions

← Older revision		Revision as of 16:15, 18 December 2011
Line 129:		Line 129:
	\|-		\|-
	\| Qt		\| Qt
	\| Qt SDK combines the Qt framework with tools designed to streamline the creation of applications for Symbian and Maemo, MeeGo (Nokia N9) as well as desktop platforms, such as Microsoft Windows, Mac OS X, and Linux. PC-BSD ~~needs that platform~~.		\| Qt SDK combines the Qt framework with tools designed to streamline the creation of applications for Symbian and Maemo, MeeGo (Nokia N9) as well as desktop platforms, such as Microsoft Windows, Mac OS X, and Linux. It satisfies PC-BSD's goal.
	\|-		\|-
	\| GTK+		\| GTK+
	\| Gimp toolkit for X11 GUI. It is a multi-platform toolkit for creating graphical user interfaces, which is PC-BSD~~'s need~~.		\| Gimp toolkit for X11 GUI. It is a multi-platform toolkit for creating graphical user interfaces, which provides desktop environment for PC-BSD.
	\|-		\|-
	\| bash		\| bash
	\| The GNU Project's Bourne Again Shell. Bash is the shell, or command language interpreter, that will appear in the GNU operating system.		\| The GNU Project's Bourne Again Shell. Bash is the shell, or command language interpreter, that will appear in the GNU operating system. It is UNIX shell, and PC-BSD is based on UNIX. So that's the reason why we need bash.
	\|-		\|-
	\| pth		\| pth
	\| Pth is a very portable POSIX/ANSI-C based library for Unix platforms which provides non-preemptive priority-based scheduling for multiple threads of execution inside event-driven applications. PC-BSD strives to give users a better experience in desktop environments like Windows or Mac OS. ~~Also,~~ multi-~~thread~~ is required.		\| Pth is a very portable POSIX/ANSI-C based library for Unix platforms which provides non-preemptive priority-based scheduling for multiple threads of execution inside event-driven applications. PC-BSD strives to give users a better experience in desktop environments like Windows or Mac OS. Then multi-threads is required.
	\|-		\|-
	\| rpm		\| rpm
Line 150:		Line 150:
	\|-		\|-
	\| Gwenview		\| Gwenview
	\| Gwenview is part of the ~~kdegraphics~~ module. Gwenview is a fast and easy way to use image viewer/browser for KDE. PC-BSD uses KDE for better user experience. Gwenview is inside KDE.		\| Gwenview is part of the KDE graphics module. Gwenview is a fast and easy way to use image viewer/browser for KDE. PC-BSD uses KDE for better user experience. Gwenview is inside KDE.
	\|-		\|-
	\| amarok		\| amarok

Qliu1: /* Software Management */

2011-12-18T16:04:53Z

Software Management

← Older revision		Revision as of 16:04, 18 December 2011
Line 36:		Line 36:


	Following the user's decision, the software can be downloaded by clicking the download link. After ~~which~~ it will automatically download and install the packages/software.		Following the user's decision, the software can be downloaded by clicking the download link. After that it will automatically download and install the packages/software.

	[[File:install_software.png\|300px]]		[[File:install_software.png\|300px]]

Qliu1: /* Software Catelog */

2011-12-18T16:03:11Z

Software Catelog

← Older revision		Revision as of 16:03, 18 December 2011
Line 21:		Line 21:

	=== Software Catelog ===		=== Software Catelog ===
	The PC-BSD repository<ref>Package Management in PC-BSD. http://en.wikipedia.org/wiki/PC-BSD#Package_management Retrieved Nov 16, 2011.</ref> is http://www.pbidir.com/. The software catalog is organized in alphabetical order of package categories as in the following picture:		The PC-BSD repository<ref>Package Management in PC-BSD. http://en.wikipedia.org/wiki/PC-BSD#Package_management Retrieved Nov 16, 2011.</ref> is http://www.pbidir.com/. The software catalog is organized in alphabetical order of package categories as shown in the following picture:

	[[File:software_catalog.png\|300px]]		[[File:software_catalog.png\|300px]]

Qliu1: /* Software Packaging */

2011-12-18T16:00:28Z

Software Packaging

← Older revision		Revision as of 16:00, 18 December 2011
Line 3:		Line 3:
	== Software Packaging ==		== Software Packaging ==
	=== Package Format and Utilities ===		=== Package Format and Utilities ===
	PC-BSD's package management system takes a different approach to ~~installing~~ software ~~than~~ many other Unix-like operating systems. Instead of using the FreeBSD ports<ref>FreeBSD ports. http://en.wikipedia.org/wiki/FreeBSD_ports Retrieved Dec 7, 2011.</ref> tree directly, PC-BSD uses files with the .pbi<ref>PBI Package Management. http://www.pcbsd.org/about/pc-bsd-project/package-management Retrieved Nov 16, 2011.</ref> file-name extension which, when double-clicked, bring up an installation wizard program. PBI (PC-BSD Installer or Push-Button Installer) is Binary Packaging format. This distribution uses a wide variety of graphic utilities<ref>PC-BSD Utilities. http://www.pcbsd.org/about/pc-bsd-project/utilities Retrieved Nov 16, 2011.</ref> to supply a front-end to useful FreeBSD features, such as Software Management Utility, Virtual Environment Utility, Backup Utility, Ports Jails Utility and so on. In the distribution, the package management relies on pkg tool, which is also used in FreeBSD, and Software Manager.		PC-BSD's package management system takes a different approach to install software from many other Unix-like operating systems. Instead of using the FreeBSD ports<ref>FreeBSD ports. http://en.wikipedia.org/wiki/FreeBSD_ports Retrieved Dec 7, 2011.</ref> tree directly, PC-BSD uses files with the .pbi<ref>PBI Package Management. http://www.pcbsd.org/about/pc-bsd-project/package-management Retrieved Nov 16, 2011.</ref> file-name extension which, when double-clicked, bring up an installation wizard program. PBI (PC-BSD Installer or Push-Button Installer) is Binary Packaging format. This distribution uses a wide variety of graphic utilities<ref>PC-BSD Utilities. http://www.pcbsd.org/about/pc-bsd-project/utilities Retrieved Nov 16, 2011.</ref> to supply a front-end to useful FreeBSD features, such as Software Management Utility, Virtual Environment Utility, Backup Utility, Ports Jails Utility and so on. In the distribution, the package management relies on pkg tool, which is also used in FreeBSD, and Software Manager.

	=== List Installed Packages ===		=== List Installed Packages ===

Qliu1: /* Major package versions */

2011-12-17T07:02:08Z

Major package versions

← Older revision		Revision as of 07:02, 17 December 2011
Line 116:		Line 116:
	'''Major Difference and Purpose'''		'''Major Difference and Purpose'''

	PC-BSD is based on FreeBSD, but PC-BSD is for desktop use ~~while~~ FreeBSD is for server use. They are generally similar but some differences still exist. PC-BSD has added some utilities or kernel tweaks or GUI to make PC-BSD suitable for desktop use. For the KDE part, the author just used the one in FreeBSD, so there is no modification in the KDE packages. Therefore the major modification is the kernel. The difference between PC-BSD and FreeBSD can be found [http://www.spreadbsd.org/?q=pcbsd here]. The purposes of the packages are shown below:		PC-BSD is based on FreeBSD, but PC-BSD is for desktop use and FreeBSD is for server use. They are generally similar but some differences still exist. PC-BSD has added some utilities or kernel tweaks or GUI to make PC-BSD suitable for desktop use. For the KDE part, the author just used the one in FreeBSD, so there is no modification in the KDE packages. Therefore the major modification is the kernel. The difference between PC-BSD and FreeBSD can be found [http://www.spreadbsd.org/?q=pcbsd here]. The purposes of the packages are shown below:

	{\| border="1"		{\| border="1"

Qliu1: /* Initialization */

2011-12-17T06:50:11Z

Initialization

← Older revision		Revision as of 06:50, 17 December 2011
Line 181:		Line 181:

	* '''netatalk''' - Netatalk is a freely-available open source AFP fileserver. It also provides a kernel level implementation of the AppleTalk Protocol Suite. It makes NIX/BSD system to be capable of serving many Macintosh clients simultaneously as an AppleShare file server (AFP), AppleTalk router, NIX/*BSD print server, and for accessing AppleTalk printers via Printer Access Protocol (PAP). In the script, netatalk will start with netatalk_start() and stop with netatalk_stop(). It runs after DAEMON, and it implements the following major utilities while on booting :		* '''netatalk''' - Netatalk is a freely-available open source AFP fileserver. It also provides a kernel level implementation of the AppleTalk Protocol Suite. It makes NIX/BSD system to be capable of serving many Macintosh clients simultaneously as an AppleShare file server (AFP), AppleTalk router, NIX/*BSD print server, and for accessing AppleTalk printers via Printer Access Protocol (PAP). In the script, netatalk will start with netatalk_start() and stop with netatalk_stop(). It runs after DAEMON, and it implements the following major utilities while on booting :
	1) atalkd - an implementation of the AppleTalk protocol <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.		1) atalkd - an implementation of the AppleTalk protocol <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.
	2) papd - a print server that enables Macintosh computers to access printers which are connected to UNIX server <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.		2) papd - a print server that enables Macintosh computers to access printers which are connected to UNIX server <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.
	3) afpd - a file server that implements the Apple Filing Protocol, allowing clients running MacOS to access Unix file servers.<ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.		3) afpd - a file server that implements the Apple Filing Protocol, allowing clients running MacOS to access Unix file servers.<ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.

	* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card. It starts with snddetect_start(), which call /usr/PCBSD/soundDetect/sound_detect, and stops with snddetect_stop().		* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card. It starts with snddetect_start(), which call /usr/PCBSD/soundDetect/sound_detect, and stops with snddetect_stop().

Qliu1: /* Initialization */

2011-12-17T06:49:31Z

Initialization

← Older revision		Revision as of 06:49, 17 December 2011
Line 167:		Line 167:
	The scripts provide information about how to start service or disable service. Most of services can be disabled or disabled by adding some codes to /etc/rc.conf. For example, in the following programs, fusefs shows how to disable its service.		The scripts provide information about how to start service or disable service. Most of services can be disabled or disabled by adding some codes to /etc/rc.conf. For example, in the following programs, fusefs shows how to disable its service.

	* '''fusefs''' - It runs after sysctl and before mountlate. It is used to implement a fully functional filesystem in a ~~userspace~~ program, with its API library as the key feature. The filesystem works when the fuse kernel module and the fuse library communicate through a special file descriptor which is obtained by opening /dev/fuse. This file can be opened multiple times, and the obtained file descriptor is passed to the mount syscall, to match up the descriptor with the mounted filesystem. To disable the fusefs service, add the following line to /etc/rc.conf :		* '''fusefs''' - It runs after sysctl and before mountlate. It is used to implement a fully functional filesystem in a user-space program, with its API library as the key feature. The filesystem works when the fuse kernel module and the fuse library communicate through a special file descriptor which is obtained by opening /dev/fuse. This file can be opened multiple times, and the obtained file descriptor is passed to the mount syscall, to match up the descriptor with the mounted filesystem. To disable the fusefs service, add the following line to /etc/rc.conf :
	fusefs_enable="NO"		fusefs_enable="NO"
	fusefs_safe="NO"		fusefs_safe="NO"
Line 187:		Line 187:
	* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card. It starts with snddetect_start(), which call /usr/PCBSD/soundDetect/sound_detect, and stops with snddetect_stop().		* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card. It starts with snddetect_start(), which call /usr/PCBSD/soundDetect/sound_detect, and stops with snddetect_stop().

	* '''wacom''' - It runs after filesystem, and it offers setup and cleanup to configure Xorg for use of the driver or ~~removes~~ the configuration settings. It ~~is an input device driver for wacom devices, and it~~ functions as a pointer input device. It is ~~useful~~ to ~~define multiple devices with diferent active zones. Various entries are supported~~ by ~~wacom, but the most important entry or the most general entry is the OPtion "Type" entry~~. ~~This entry sets the type of tool the device represents~~, ~~which could be stylus, eraser, cursor, pad or touch. Note that the tool can represent more than one device~~. ~~There are other options that come with wacom for pcbsd such as "device", "forceDrive", "suppress" etc, depending on what tool we are looking at~~.		* '''wacom''' - This is Wacom input driver. It runs after filesystem, and it offers setup and cleanup to configure Xorg for use of the driver or remove the configuration settings. It functions as a pointer input device. There is two function in scripts: do_start() to start service by /sbin/kldload and boot/modules/uwacom.ko, and do_stop() to stop service by /sbin/kldunload /boot/modules/uwacom.ko.

	'''End of Initialization'''		'''End of Initialization'''

Qliu1: /* Initialization */

2011-12-17T06:33:20Z

Initialization

← Older revision		Revision as of 06:33, 17 December 2011
Line 178:		Line 178:
	* '''gpsd''' - gpsd is an interface daemon for GPS receivers. It runs after networking DAEMON, cleanvar, and devfs. It also runs before ntpd. It collects information from GPSes, differential-GPS radios, or AIS receivers attached to the host machine. Each GPS, DGPS radio or AIS receiver is expected to be direct-connected to the host via sub or R232C serial device.		* '''gpsd''' - gpsd is an interface daemon for GPS receivers. It runs after networking DAEMON, cleanvar, and devfs. It also runs before ntpd. It collects information from GPSes, differential-GPS radios, or AIS receivers attached to the host machine. Each GPS, DGPS radio or AIS receiver is expected to be direct-connected to the host via sub or R232C serial device.

	* '''oss''' - It runs after DAEMON, and it handles the sound system. It is the open sound system which provides support for PCM audio play and capture. ~~Various systcall variables are stored in~~ /~~etc~~/~~systcl.conf so it is automatically set during the boot process~~.		* '''oss''' - Open Sound System (OSS) is the first attempt in unifying the digital audio architecture for UNIX. It runs after DAEMON, and it handles the sound system. It is the open sound system which provides support for PCM audio play and capture. It is started by function oss_start() and stopped by function oss_stop(). The two function will call system calls: /usr/local/sbin/soundon and /usr/local/sbin/soundoff.

	* '''netatalk''' - It is a freely-~~availabe~~ open source AFP fileserver ~~package thats helps deal with~~ the ~~Appletalk protocol suite and its relatives~~. It ~~can perform~~ file and ~~print sharing~~ for ~~macintosh~~. It ~~comes with small~~ utilities ~~that help ease dealing with macintosh files from unix~~. ~~To start~~ netatalk ~~from boot time~~, ~~add these lines~~<ref>~~Initilization~~ Netatalk in PC-BSD. http://~~openports~~.se/~~net~~/~~netatalk~~ Retrieved Dec 15, 2011.</ref>./~~etc~~/rc.~~local:~~		* '''netatalk''' - Netatalk is a freely-available open source AFP fileserver. It also provides a kernel level implementation of the AppleTalk Protocol Suite. It makes NIX/BSD system to be capable of serving many Macintosh clients simultaneously as an AppleShare file server (AFP), AppleTalk router, NIX/*BSD print server, and for accessing AppleTalk printers via Printer Access Protocol (PAP). In the script, netatalk will start with netatalk_start() and stop with netatalk_stop(). It runs after DAEMON, and it implements the following major utilities while on booting :
			1) atalkd - an implementation of the AppleTalk protocol <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.
			2) papd - a print server that enables Macintosh computers to access printers which are connected to UNIX server <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.
			3) afpd - a file server that implements the Apple Filing Protocol, allowing clients running MacOS to access Unix file servers.<ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.

	~~if [ -f ${SYSCONFDIR}/netatalk/rc.atalk ]; then~~		* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card. It starts with snddetect_start(), which call /usr/PCBSD/soundDetect/sound_detect, and stops with snddetect_stop().
	~~. ${SYSCONFDIR}/netatalk/rc.atalk~~
	fi
	~~It runs after DAEMON, and it implements the following major utilities while on booting :~~
	~~1)atalkd - an implementation of the AppleTalk protocol <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.~~
	2) papd - a print server that enables macintosh computers to access printers that are connected to unix servers <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.
	3) afpd - File server that implements the Apple filing protocol, which allows clients the run MasOs to access unix file servers <ref>Netatalk functions in PC-BSD. http://netatalk.sourceforge.net/2.2/ReleaseNotes2.2.1.html Retrieved Dec 15, 2011.</ref>.

	~~Other less important utilities it implements are cnid_metad, timelord .~~
	It is an appletalk daemon whose data structures must have time to stabilize before running the other processes. One must also make sure that atalkd has not started in the background before it starts running.

	* '''snddetect''' - It runs after DAEMON, and detects sound. It first removes sound flag then detects an unknown sound card.

	* '''wacom''' - It runs after filesystem, and it offers setup and cleanup to configure Xorg for use of the driver or removes the configuration settings. It is an input device driver for wacom devices, and it functions as a pointer input device. It is useful to define multiple devices with diferent active zones. Various entries are supported by wacom, but the most important entry or the most general entry is the OPtion "Type" entry. This entry sets the type of tool the device represents, which could be stylus, eraser, cursor, pad or touch. Note that the tool can represent more than one device. There are other options that come with wacom for pcbsd such as "device", "forceDrive", "suppress" etc, depending on what tool we are looking at.		* '''wacom''' - It runs after filesystem, and it offers setup and cleanup to configure Xorg for use of the driver or removes the configuration settings. It is an input device driver for wacom devices, and it functions as a pointer input device. It is useful to define multiple devices with diferent active zones. Various entries are supported by wacom, but the most important entry or the most general entry is the OPtion "Type" entry. This entry sets the type of tool the device represents, which could be stylus, eraser, cursor, pad or touch. Note that the tool can represent more than one device. There are other options that come with wacom for pcbsd such as "device", "forceDrive", "suppress" etc, depending on what tool we are looking at.