Clean Core - Revision history

Mcefan at 21:16, 19 October 2012

2012-10-19T21:16:54Z

←Older revision		Revision as of 21:16, 19 October 2012
Line 1:		Line 1:
	{{versioninfo\|710Status=Relevant to 0710 and older\|710UpdatedDate=2nd June 2011\|710UpdatedBy=purps\|810Status=Not applicable\|810UpdatedDate=2nd June 2011\|810UpdatedBy=purps\|1004Status=Not applicable\|1004UpdatedDate=3rd August 2011\|1004UpdatedBy=foxi352}}		{{versioninfo\|710Status=Relevant to 0710 and older\|710UpdatedDate=2nd June 2011\|710UpdatedBy=purps\|810Status=Not applicable\|810UpdatedDate=2nd June 2011\|810UpdatedBy=purps\|1004Status=Not applicable\|1004UpdatedDate=3rd August 2011\|1004UpdatedBy=foxi352}}
	~~[[category: tutorials]]~~		[[Category:LinuxMCE Configuration]]
	[[Category: ~~User Setups~~]]
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__
	\|}		\|}


	== Introduction ==		== Introduction ==

Line 10:		Line 11:

	Please don't be shy to add any related knowledge you have.		Please don't be shy to add any related knowledge you have.

			{{p}}

	== Runlevels ==		== Runlevels ==
Line 23:		Line 26:

	Of course you can just adapt the example to your specific wishes or needs.		Of course you can just adapt the example to your specific wishes or needs.

			{{p}}

	=== Starting another runlevel ===		=== Starting another runlevel ===
Line 39:		Line 44:
	Before starting it is always wise to make a backup of a few things, just in case:		Before starting it is always wise to make a backup of a few things, just in case:
	tar cjvf ~/backup-`date '+%Y%m%d:%H%M'`.tar.bz2 /etc/init.d /etc/rc*.d		tar cjvf ~/backup-`date '+%Y%m%d:%H%M'`.tar.bz2 /etc/init.d /etc/rc*.d

			{{p}}

	==== Preparation ====		==== Preparation ====
Line 209:		Line 216:
	EOF		EOF
	chmod +x usr/pluto/bin/startDevices.sh		chmod +x usr/pluto/bin/startDevices.sh
			{{p}}

	===== On a Mainly Personal Computer installation =====		===== On a Mainly Personal Computer installation =====
Line 225:		Line 232:
	EOF		EOF
	chmod +x etc/init.d/launch-manager		chmod +x etc/init.d/launch-manager
			{{p}}

	===== On a Dedicated Media Center installation =====		===== On a Dedicated Media Center installation =====
Line 235:		Line 242:
	mv -iv etc/init.d/kdm etc/init.d/launch-manager		mv -iv etc/init.d/kdm etc/init.d/launch-manager
	cp -iv etc/init.d/kdm.saved etc/init.d/kdm		cp -iv etc/init.d/kdm.saved etc/init.d/kdm
			{{p}}

	==== Changing the symlinks ====		==== Changing the symlinks ====
Line 292:		Line 300:

	On a sidenote: ''/etc/event.d/pluto-dhcpd-plugin'' seems redundant as it appears to be started from ''/usr/pluto/bin/startup-script.sh'' as well.		On a sidenote: ''/etc/event.d/pluto-dhcpd-plugin'' seems redundant as it appears to be started from ''/usr/pluto/bin/startup-script.sh'' as well.

			{{p}}

	=== Changing the default runlevel ===		=== Changing the default runlevel ===
Line 309:		Line 319:

	Note that the ''runlevel='' options specified in the grub menu override this, at least if you have updated the ''/etc/event.d/rc-default'' file as described below.		Note that the ''runlevel='' options specified in the grub menu override this, at least if you have updated the ''/etc/event.d/rc-default'' file as described below.

			{{p}}

	=== Selecting a runlevel at boot time ===		=== Selecting a runlevel at boot time ===

Foxi352 at 11:44, 3 August 2011

2011-08-03T11:44:21Z

←Older revision		Revision as of 11:44, 3 August 2011
Line 1:		Line 1:
	{{versioninfo\|710Status=Relevant to 0710 and older\|710UpdatedDate=2nd June 2011\|710UpdatedBy=purps\|810Status=Not applicable\|810UpdatedDate=2nd June 2011\|810UpdatedBy=purps}}		{{versioninfo\|710Status=Relevant to 0710 and older\|710UpdatedDate=2nd June 2011\|710UpdatedBy=purps\|810Status=Not applicable\|810UpdatedDate=2nd June 2011\|810UpdatedBy=purps\|1004Status=Not applicable\|1004UpdatedDate=3rd August 2011\|1004UpdatedBy=foxi352}}
	[[category: tutorials]]		[[category: tutorials]]
	[[Category: User Setups]]		[[Category: User Setups]]

Purps at 15:03, 2 June 2011

2011-06-02T15:03:08Z

←Older revision		Revision as of 15:03, 2 June 2011
Line 1:		Line 1:
	{{~~Versioninfo~~}}		{{versioninfo\|710Status=Relevant to 0710 and older\|710UpdatedDate=2nd June 2011\|710UpdatedBy=purps\|810Status=Not applicable\|810UpdatedDate=2nd June 2011\|810UpdatedBy=purps}}
	[[category: tutorials]]		[[category: tutorials]]
	[[Category: User Setups]]		[[Category: User Setups]]

Langstonius at 23:33, 29 July 2010

2010-07-29T23:33:21Z

←Older revision		Revision as of 23:33, 29 July 2010
Line 1:		Line 1:
			{{Versioninfo}}
	[[category: tutorials]]		[[category: tutorials]]
	[[Category: User Setups]]		[[Category: User Setups]]

Chris Caven: /* Introduction */

2010-04-24T17:14:48Z

Introduction

←Older revision		Revision as of 17:14, 24 April 2010
Line 6:		Line 6:
	== Introduction ==		== Introduction ==

	This page is meant to document the efforts to turn the LinuxMCE core into one or more Linux "services" that are ~~automaticly~~ started at boot time. In other words we would like to be able to boot a dedicated LinuxMCE Core server without using the Launch Manager application and without the dependency upon a graphic environment.		This page is meant to document the efforts to turn the LinuxMCE core into one or more Linux "services" that are automatically started at boot time. In other words, we would like to be able to boot a dedicated LinuxMCE Core server without using the Launch Manager application and without the dependency upon a graphic environment.

	Please don't be shy to add any related knowledge you have.		Please don't be shy to add any related knowledge you have.

Zaerc: added calling checkforRaids.sh and UpdateAvailableSerialPorts.sh

2009-02-25T13:47:22Z

added calling checkforRaids.sh and UpdateAvailableSerialPorts.sh

←Older revision		Revision as of 13:47, 25 February 2009
Line 85:		Line 85:
	$BASEDIR/Start_DCERouter.sh		$BASEDIR/Start_DCERouter.sh

			$BASEDIR/checkforRaids.sh
			$BASEDIR/UpdateAvailableSerialPorts.sh

	QUERY="SELECT PK_Device FROM Device JOIN DeviceTemplate ON Device.FK_DeviceTemplate=DeviceTemplate.PK_DeviceTemplate WHERE PK_DeviceTemplate=${DeviceTemplate_Core}"		QUERY="SELECT PK_Device FROM Device JOIN DeviceTemplate ON Device.FK_DeviceTemplate=DeviceTemplate.PK_DeviceTemplate WHERE PK_DeviceTemplate=${DeviceTemplate_Core}"

Zaerc: /* Selecting a runlevel at boot time */ single quotes are better suited

2008-11-14T00:50:45Z

Selecting a runlevel at boot time: single quotes are better suited

←Older revision		Revision as of 00:50, 14 November 2008
Line 329:		Line 329:
	RL="S"		RL="S"
	else		else
	RL="$(sed -n -e "s/.runlevel=$[1-5]$./\1/p" /proc/cmdline \|\| true)"		RL="$(sed -n -e 's/.runlevel=$[1-5]$./\1/p' /proc/cmdline \|\| true)"
	fi		fi

Langstonius at 17:08, 12 June 2008

2008-06-12T17:08:01Z

←Older revision		Revision as of 17:08, 12 June 2008
Line 1:		Line 1:
			[[category: tutorials]]
			[[Category: User Setups]]
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Perspectoff at 03:18, 15 May 2008

2008-05-15T03:18:25Z

←Older revision		Revision as of 03:18, 15 May 2008
Line 4:		Line 4:
	== Introduction ==		== Introduction ==

	This page is meant to document the efforts to turn the ~~LMCE~~ core into one or more "services" that are automaticly started at boot time. In other words we would like to be able to boot a LinuxMCE ~~machine~~ without using the Launch Manager application, and the dependency ~~uppon~~ a graphic environment~~, at least for starting a (dedicated) core~~.		This page is meant to document the efforts to turn the LinuxMCE core into one or more Linux "services" that are automaticly started at boot time. In other words we would like to be able to boot a dedicated LinuxMCE Core server without using the Launch Manager application and without the dependency upon a graphic environment.

	~~Due to the lack of documentation we will have to figure a lot of things out on our own.~~ Please don't be shy to add any related knowledge you have, we don't really know what we're doing, so why should you? At least by adding stuff here we'll be able to build uppon each others experience without having to reverse-engineer the wheel every time. And who knows, one day we might even achieve our common goal.		Please don't be shy to add any related knowledge you have.

	== Runlevels ==		== Runlevels ==

Zaerc: made all commands relative to the root directory for convenience

2008-03-05T16:04:22Z

made all commands relative to the root directory for convenience

←Older revision		Revision as of 16:04, 5 March 2008
Line 234:		Line 234:

	In order to make the system boot only the core in runlevel 3, simply copy the symlinks of runlevel 2 and replace the ones that start KDE and the AVWizard with a symlink to the init script we created earlier during the preparations:		In order to make the system boot only the core in runlevel 3, simply copy the symlinks of runlevel 2 and replace the ones that start KDE and the AVWizard with a symlink to the init script we created earlier during the preparations:
	rm -rfv /etc/rc3.d/*		cd /
	cp -av /etc/rc2.d/* /etc/rc3.d/		rm -rfv etc/rc3.d/*
	ln -sfv ../init.d/core /etc/rc3.d/S99core		cp -av etc/rc2.d/* etc/rc3.d/
	rm -fv /etc/rc3.d/S99kdm /etc/rc3.d/S990start_avwizard		ln -sfv ../init.d/core etc/rc3.d/S99core
			rm -fv etc/rc3.d/S99kdm etc/rc3.d/S990start_avwizard


	Making the system boot the core + KDE in runlevel 4 is even simpeler as we don't even have to remove the symlinks:		Making the system boot the core + KDE in runlevel 4 is even simpeler as we don't even have to remove the symlinks:
	rm -rfv /etc/rc4.d/*		cd /
	cp -av /etc/rc2.d/* /etc/rc4.d/		rm -rfv etc/rc4.d/*
	ln -sfv ../init.d/core /etc/rc4.d/S99core		cp -av etc/rc2.d/* etc/rc4.d/
			ln -sfv ../init.d/core etc/rc4.d/S99core


	Starting the launchmanager in runlevel 5:		Starting the launchmanager in runlevel 5:
	rm -rfv /etc/rc5.d/*		cd /
	cp -av /etc/rc2.d/* /etc/rc5.d/		rm -rfv etc/rc5.d/*
	ln -sfv ../init.d/launch-manager /etc/rc5.d/S99launch-manager		cp -av etc/rc2.d/* etc/rc5.d/
	rm -fv /etc/rc5.d/S99kdm		ln -sfv ../init.d/launch-manager etc/rc5.d/S99launch-manager
			rm -fv etc/rc5.d/S99kdm


Line 288:		Line 291:

	The default runlevel is 2, unless specified otherwise in the ''/etc/inittab'' file, here is an example on how to create such a file (it will override an existing one):		The default runlevel is 2, unless specified otherwise in the ''/etc/inittab'' file, here is an example on how to create such a file (it will override an existing one):
	cat >/etc/inittab <<"EOF"		cd /
			cat >etc/inittab <<"EOF"
	# WARNING: Do NOT set the default runlevel to 0 (shutdown) or 6 (reboot).		# WARNING: Do NOT set the default runlevel to 0 (shutdown) or 6 (reboot).
	id:2:initdefault: # KDE		id:2:initdefault: # KDE
Line 306:		Line 310:

	First we need to replace one of ''upstart'''s files, ''/etc/event.d/rc-default''. (It wasn't a big addition, but I didn't like the inconsistent way it was written originally, so I just cleaned it up a bit.)		First we need to replace one of ''upstart'''s files, ''/etc/event.d/rc-default''. (It wasn't a big addition, but I didn't like the inconsistent way it was written originally, so I just cleaned it up a bit.)
	cat >/etc/event.d/rc-default <<"EOF"		cd /
			cat >etc/event.d/rc-default <<"EOF"
	# rc - runlevel compatibility		# rc - runlevel compatibility
	#		#