Fedora Installation Notes - Revision history

Paul Blankenbaker: /* Fedora 7 Installation Notes */

2010-09-22T14:57:32Z

Fedora 7 Installation Notes

← Older revision		Revision as of 10:57, 22 September 2010
Line 1:		Line 1:
			<p class="wikiNote">'''NOTE''': This page is outdated and should no longer be used as a reference for building a NST development system. If you are interested in putting together a system for the purpose of building the NST distribution from source, please refer to the [[Developer Info]] section.</p>

			__TOC__

	= Fedora 7 Installation Notes =		= Fedora 7 Installation Notes =

	<p class="wikiNote">'''NOTE''': This page is outdated and should no longer be used as a reference for building a NST development system. If you are interested in putting together a system for the purpose of building the NST distribution from source, please refer to the [[Developer Info]] section.</p>

	== VMware Server ==		== VMware Server ==

Paul Blankenbaker: /* Fedora 7 Installation Notes */

2010-09-22T14:55:56Z

Fedora 7 Installation Notes

← Older revision		Revision as of 10:55, 22 September 2010
Line 1:		Line 1:
	= Fedora 7 Installation Notes =		= Fedora 7 Installation Notes =

	'''~~*~~NOTE~~*~~''' This page is outdated and should no longer be used as a reference for building a NST development system. If you are interested in putting together a system for the purpose of building the NST distribution from source, please refer to the [[Developer Info]] section.		<p class="wikiNote">'''NOTE''': This page is outdated and should no longer be used as a reference for building a NST development system. If you are interested in putting together a system for the purpose of building the NST distribution from source, please refer to the [[Developer Info]] section.</p>

	== VMware Server ==		== VMware Server ==

Paul Blankenbaker: Removed old building from source reference - no longer applicable

2010-09-22T14:54:24Z

Removed old building from source reference - no longer applicable

← Older revision		Revision as of 10:54, 22 September 2010
Line 1:		Line 1:
	= Fedora 7 Installation Notes =		= Fedora 7 Installation Notes =

			'''*NOTE*''' This page is outdated and should no longer be used as a reference for building a NST development system. If you are interested in putting together a system for the purpose of building the NST distribution from source, please refer to the [[Developer Info]] section.

	== VMware Server ==		== VMware Server ==
Line 41:		Line 43:
	I undertook a challenge to see if I could make a working NST under VMWARE. The motivation was to obtain extra functions beyond what was available in the NST 1.5 VMWARE image; e.g. gain access to the VMWARE hgfs function and add additional tools. Samba was an alternative to hgfs. But to add the additional tools I needed to build an FC image anyway. So why not just build FC7/NST under VMWARE?		I undertook a challenge to see if I could make a working NST under VMWARE. The motivation was to obtain extra functions beyond what was available in the NST 1.5 VMWARE image; e.g. gain access to the VMWARE hgfs function and add additional tools. Samba was an alternative to hgfs. But to add the additional tools I needed to build an FC image anyway. So why not just build FC7/NST under VMWARE?

	I started by following the instructions~~, [[Building From Source]]~~, that were developed by the primary NST developers. FC7 was built under Fusion using the "split" option for an 8GB virtual drive. The split option was chosen to make the image portable using the FAT file system.		I started by following the building instructions on the NST WIKI, that were developed by the primary NST developers. FC7 was built under Fusion using the "split" option for an 8GB virtual drive. The split option was chosen to make the image portable using the FAT file system.

	During the FC7 install, I generally chose not to install packages that dealt with (to be filled in later).		During the FC7 install, I generally chose not to install packages that dealt with (to be filled in later).

Vagab0nd: /* Development Case Study Using VMWARE by a newbie */

2007-09-13T19:52:20Z

Development Case Study Using VMWARE by a newbie

← Older revision		Revision as of 15:52, 13 September 2007
Line 52:		Line 52:
	* rpm -Uvh VMwareTools-e.x.p-51348.i386.rpm		* rpm -Uvh VMwareTools-e.x.p-51348.i386.rpm

	And then configured by executing vmware-config-tools.pl. The configuration output can be found at [[Fedora Installation Notes#Development Case Study Using VMWARE - vmware-config output\| vmware config output]].		And then configured by executing:
			* vmware-config-tools.pl.
			The configuration output can be found at [[Fedora Installation Notes#Development Case Study Using VMWARE - vmware-config output\| vmware config output]].

	As the subsequent NST creation steps unfolded, the VMWARE image was moved back and forth using an 8GB flash drive. The movement from Fusion was to VMPLAYER running under SUSE 10.x. This provided initial validation that the image had, at minimum, some portability. Fusion was still needed to tweak the "settings." After some tweaking, the following "settings" configuration was used:		As the subsequent NST creation steps unfolded, the VMWARE image was moved back and forth using an 8GB flash drive. The movement from Fusion was to VMPLAYER running under SUSE 10.x. This provided initial validation that the image had, at minimum, some portability. Fusion was still needed to tweak the "settings." After some tweaking, the following "settings" configuration was used:

Vagab0nd: /* Development Case Study Using VMWARE - make package-check */

2007-09-13T19:38:05Z

Development Case Study Using VMWARE - make package-check

← Older revision		Revision as of 15:38, 13 September 2007
Line 2,725:		Line 2,725:

	== Development Case Study Using VMWARE - make package-check ==		== Development Case Study Using VMWARE - make package-check ==
	firefox (version 2.0.0.4) [failed]		egrep -i fail output.of.make package-check
	autohide (version 1.1.5) [failed]		<ul>
	colorful_tabs (version 2.0.1) [failed]		<li>firefox (version 2.0.0.4) [failed]
	dictionarysearch (version 2.0.1) [failed]		<li>autohide (version 1.1.5) [failed]
	image_zoom (version 0.2.7) [failed]		<li>colorful_tabs (version 2.0.1) [failed]
	LinkChecker (version 0.6.1) [failed]		<li>dictionarysearch (version 2.0.1) [failed]
	long_titles (version 1.2.4) [failed]		<li>image_zoom (version 0.2.7) [failed]
	madwifi (version 0.9.3.2-rc1) [failed]		<li>LinkChecker (version 0.6.1) [failed]
	metasploit (version 2.7) [failed]		<li>long_titles (version 1.2.4) [failed]
	nessus (version 2.2.10) [failed]		<li>madwifi (version 0.9.3.2-rc1) [failed]
	netw (version 5.34.0) [failed]		<li>metasploit (version 2.7) [failed]
	ntop (version 3.3.1) [failed]		<li>nessus (version 2.2.10) [failed]
	quickrestart (version 1.1.0) [failed]		<li>netw (version 5.34.0) [failed]
	reloadevery (version 2.0) [failed]		<li>ntop (version 3.3.1) [failed]
	snorter (version 2.1) [failed]		<li>quickrestart (version 1.1.0) [failed]
	tcl (version 8.4.13-16nothreads) [failed]		<li>reloadevery (version 2.0) [failed]
	tidy (version 0.8.3.9) [failed]		<li>snorter (version 2.1) [failed]
	vmware-tools (version 1.0.3) [failed]		<li>tcl (version 8.4.13-16nothreads) [failed]
	webdeveloper (version 1.1.4) [failed]		<li>tidy (version 0.8.3.9) [failed]
	wireshark (version 0.99.6) [failed]		<li>vmware-tools (version 1.0.3) [failed]
			<li>webdeveloper (version 1.1.4) [failed]
			<li>wireshark (version 0.99.6) [failed]
			</ul>

Vagab0nd: /* Development Case Study Using VMWARE by a newbie */

2007-09-13T19:30:46Z

Development Case Study Using VMWARE by a newbie

← Older revision		Revision as of 15:30, 13 September 2007
Line 88:		Line 88:
	Being a newbie at building NST, the next command was [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check-url\| make package-check-url]]		Being a newbie at building NST, the next command was [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check-url\| make package-check-url]]

	Bing 'failed' the url check. So I edited nst/.../bing.sh and corrected the url. ntop and php-base were more important, but ~~the~~ seemed like better candidates for make package-check. Note that nessus and metasploit are not reported as problems in the url check.		Bing 'failed' the url check. So I edited nst/.../bing.sh and corrected the url. ntop and php-base were more important, but they seemed like better candidates for make package-check. Note that nessus and metasploit are not reported as problems in the url check.

	Bing succeeded in the [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-update\| make package-update]].		Bing succeeded in the [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-update\| make package-update]].
Line 99:		Line 99:

	The output of [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check\| make package-check]]		The output of [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check\| make package-check]]
	was a useful quality control check.		was a useful quality control check.

	== Development Case Study Using VMWARE - vmware-config output ==		== Development Case Study Using VMWARE - vmware-config output ==

Vagab0nd: /* Development Case Study Using VMWARE by a newbie */

2007-09-13T19:28:35Z

Development Case Study Using VMWARE by a newbie

← Older revision		Revision as of 15:28, 13 September 2007
Line 55:		Line 55:

	As the subsequent NST creation steps unfolded, the VMWARE image was moved back and forth using an 8GB flash drive. The movement from Fusion was to VMPLAYER running under SUSE 10.x. This provided initial validation that the image had, at minimum, some portability. Fusion was still needed to tweak the "settings." After some tweaking, the following "settings" configuration was used:		As the subsequent NST creation steps unfolded, the VMWARE image was moved back and forth using an 8GB flash drive. The movement from Fusion was to VMPLAYER running under SUSE 10.x. This provided initial validation that the image had, at minimum, some portability. Fusion was still needed to tweak the "settings." After some tweaking, the following "settings" configuration was used:
	3 NICs		<ul>
	eth0 - NATed to be used as the NST management interface		<li>3 NICs
	eth1 - custom to be used as a promiscuous interface		<li>eth0 - NATed to be used as the NST management interface
	eth2 - host to be assigned for future use		<li>eth1 - custom to be used as a promiscuous interface
			<li>eth2 - host to be assigned for future use
	Parallel - not connected		<li>Parallel - not connected
	Serial 1 - not connected		<li>Serial 1 - not connected
	Serial 2 - not connected		<li>Serial 2 - not connected
	Floppy1 - not connected but pointed to an empty floppy 1.4M image stored within the image folder		<li>Floppy1 - not connected but pointed to an empty floppy 1.4M image stored within the image folder
	CD - connected and pointed to an empty iso image stored within the image folder		<li>CD - connected and pointed to an empty iso image stored within the image folder
	CD2 - not connected and pointed to an empty iso image stored within the image folder		<li>CD2 - not connected and pointed to an empty iso image stored within the image folder
			</ul>

	The empty ISO files for the CD and the empty image for the floppy minimized obstacles to moving the image, while still allowing flexibility on what device to have connected during the boot process. One can adjust what is connected by using F2 during the boot process and making sure an empty image is not selected 'first' during the boot process.		The empty ISO files for the CD and the empty image for the floppy minimized obstacles to moving the image, while still allowing flexibility on what device to have connected during the boot process. One can adjust what is connected by using F2 during the boot process and making sure an empty image is not selected 'first' during the boot process.
Line 74:		Line 75:
	/root/nst was the CVS sandbox. The update to .bashrc to set up CVS worked smoothly. The CVS checkout was satisfactory.		/root/nst was the CVS sandbox. The update to .bashrc to set up CVS worked smoothly. The CVS checkout was satisfactory.

	I already had Java from the FC7 install.		I already had Java from the FC7 install.
	egrep -i jre (output of rpm -qa)		* egrep -i jre (output of rpm -qa)
	jre-1.6.0_02-fcs		jre-1.6.0_02-fcs

	One error I made was caused by an interruption. When I returned to building NST after a hiatus of a couple of days, a new kernel had been released. So when I tried to build NST I got messages suggesting a kernel update. I used the FC7 package update feature and reran vmware-config-tools.pl.		One error I made was caused by an interruption. When I returned to building NST after a hiatus of a couple of days, a new kernel had been released. So when I tried to build NST I got messages suggesting a kernel update. I used the FC7 package update feature and reran vmware-config-tools.pl.

	The output of [[Fedora Installation Notes#Development Case Study Using VMWARE - configure output\| configure]] ~~and make package-update improved after updating the kernel~~.		The output of [[Fedora Installation Notes#Development Case Study Using VMWARE - configure output\| configure]] seems clean.

	My exact yum update command line entry is lost but it was something close to:		My exact yum update command line entry is lost but it was something close to:
	yum install docbook-utils docbook-utils-pdf ncftp php-pear		* yum install docbook-utils docbook-utils-pdf ncftp php-pear

	Being a newbie at building NST, the next command was [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check-url\| make package-check-url]]		Being a newbie at building NST, the next command was [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check-url\| make package-check-url]]

	Bing 'failed' the url check. So I edited nst/.../bing.sh and corrected the url. ntop and php-base were more important, but the seemed like better candidates for make package-check.		Bing 'failed' the url check. So I edited nst/.../bing.sh and corrected the url. ntop and php-base were more important, but the seemed like better candidates for make package-check. Note that nessus and metasploit are not reported as problems in the url check.

	Bing succeeded in the [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-update\| make package-update]].		Bing succeeded in the [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-update\| make package-update]].

			The approach to failures in package-update was:
			* tcl - bit of a puzzle since the binary rpm came with FC7
			* vmware tool - was already installed via rpm
			* unicornscan was expected based on [[Building From Source#Installing Packages]]
			* Wireshark was already installed by FC7

			The output of [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check\| make package-check]]
			was a useful quality control check.

	== Development Case Study Using VMWARE - vmware-config output ==		== Development Case Study Using VMWARE - vmware-config output ==

Vagab0nd: /* Development Case Study Using VMWARE - make package-update */

2007-09-13T19:27:07Z

Development Case Study Using VMWARE - make package-update

← Older revision		Revision as of 15:27, 13 September 2007
Line 2,711:		Line 2,711:
	-------------------------------------------------------------------------------		-------------------------------------------------------------------------------
	make: *** [tsv-update] Error 1		make: *** [tsv-update] Error 1



			== Development Case Study Using VMWARE - make package-check ==
			firefox (version 2.0.0.4) [failed]
			autohide (version 1.1.5) [failed]
			colorful_tabs (version 2.0.1) [failed]
			dictionarysearch (version 2.0.1) [failed]
			image_zoom (version 0.2.7) [failed]
			LinkChecker (version 0.6.1) [failed]
			long_titles (version 1.2.4) [failed]
			madwifi (version 0.9.3.2-rc1) [failed]
			metasploit (version 2.7) [failed]
			nessus (version 2.2.10) [failed]
			netw (version 5.34.0) [failed]
			ntop (version 3.3.1) [failed]
			quickrestart (version 1.1.0) [failed]
			reloadevery (version 2.0) [failed]
			snorter (version 2.1) [failed]
			tcl (version 8.4.13-16nothreads) [failed]
			tidy (version 0.8.3.9) [failed]
			vmware-tools (version 1.0.3) [failed]
			webdeveloper (version 1.1.4) [failed]
			wireshark (version 0.99.6) [failed]

Vagab0nd: /* Development Case Study Using VMWARE - make package-check-url */

2007-09-13T18:59:46Z

Development Case Study Using VMWARE - make package-check-url

Show changes

Vagab0nd: /* Development Case Study Using VMWARE by a newbie */

2007-09-13T18:35:49Z

Development Case Study Using VMWARE by a newbie

← Older revision		Revision as of 14:35, 13 September 2007
Line 74:		Line 74:
	/root/nst was the CVS sandbox. The update to .bashrc to set up CVS worked smoothly. The CVS checkout was satisfactory.		/root/nst was the CVS sandbox. The update to .bashrc to set up CVS worked smoothly. The CVS checkout was satisfactory.

	~~One error~~ I ~~made was caused by an interruption. When I returned to building NST after a hiatus of a couple of days, a new kernel~~ had ~~been released. So when I rn tried to build NST I got messages suggesting a kernel update. I used~~ the FC7 ~~package update feature and reran vmware~~-~~config~~-~~tools~~.pl.		I already had Java from the FC7 install.
			egrep -i jre (output of rpm -qa)
			jre-1.6.0_02-fcs

	The output of configure and make package-update improved after updating the kernel.		One error I made was caused by an interruption. When I returned to building NST after a hiatus of a couple of days, a new kernel had been released. So when I tried to build NST I got messages suggesting a kernel update. I used the FC7 package update feature and reran vmware-config-tools.pl.

			The output of [[Fedora Installation Notes#Development Case Study Using VMWARE - configure output\| configure]] and make package-update improved after updating the kernel.

			My exact yum update command line entry is lost but it was something close to:
			yum install docbook-utils docbook-utils-pdf ncftp php-pear

			Being a newbie at building NST, the next command was [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-check-url\| make package-check-url]]

			Bing 'failed' the url check. So I edited nst/.../bing.sh and corrected the url. ntop and php-base were more important, but the seemed like better candidates for make package-check.

			Bing succeeded in the [[Fedora Installation Notes# Development Case Study Using VMWARE - make package-update\| make package-update]].

	== Development Case Study Using VMWARE - vmware-config output ==		== Development Case Study Using VMWARE - vmware-config output ==