X Windows on LSPro - Revision history

Biscuit at 21:33, 8 December 2008

Biscuit — Mon, 08 Dec 2008 21:33:52 GMT

← Older revision		Revision as of 21:33, 8 December 2008
Line 92:		Line 92:
	===== Update 12/08/08 =====		===== Update 12/08/08 =====

-	I had bricked my box a while ago; however, I managed to recover it to the etch distribution I had before. I then performed an update to Lenny and updated the kernel to 2.6.12 (need to verify). Now everything seems to work fine. No crashes with X and performance within X is a lot better than before.	+	I had bricked my box a while ago; however, I managed to recover it to the etch distribution I had before. I then performed an update to Lenny and updated the kernel to 2.6.26 (need to verify). Now everything seems to work fine. No crashes with X and performance within X is a lot better than before.

Biscuit at 21:32, 8 December 2008

Biscuit — Mon, 08 Dec 2008 21:32:36 GMT

← Older revision		Revision as of 21:32, 8 December 2008
Line 89:		Line 89:

	I have had, what seem to be, kernel panics at a couple of points. None of the logs contain any useful information regarding this.		I have had, what seem to be, kernel panics at a couple of points. None of the logs contain any useful information regarding this.
		+
		+	===== Update 12/08/08 =====
		+
		+	I had bricked my box a while ago; however, I managed to recover it to the etch distribution I had before. I then performed an update to Lenny and updated the kernel to 2.6.12 (need to verify). Now everything seems to work fine. No crashes with X and performance within X is a lot better than before.

Ramuk at 06:30, 12 March 2008

Ramuk — Wed, 12 Mar 2008 06:30:09 GMT

← Older revision		Revision as of 06:30, 12 March 2008
Line 1:		Line 1:
-	{{Articles\|~~Freelink~~\|LSPro}}	+	{{Articles\|FreeLink\|LSPro}}
	== Reasons for doing this ==		== Reasons for doing this ==

Ramuk at 06:28, 12 March 2008

Ramuk — Wed, 12 Mar 2008 06:28:49 GMT

← Older revision		Revision as of 06:28, 12 March 2008
Line 1:		Line 1:
		+	{{Articles\|Freelink\|LSPro}}
	== Reasons for doing this ==		== Reasons for doing this ==

Biscuit at 08:12, 27 November 2007

Biscuit — Tue, 27 Nov 2007 08:12:02 GMT

← Older revision		Revision as of 08:12, 27 November 2007
Line 49:		Line 49:
	* '''rm -rf /usr'''		* '''rm -rf /usr'''
	* '''mv /oldusr /usr'''		* '''mv /oldusr /usr'''
-	* '''cp /etc/fstab.original /etc/fstab'	+	* '''cp /etc/fstab.original /etc/fstab'''
	* Reboot.		* Reboot.

Line 61:		Line 61:
	* '''apt-get install gnome'''		* '''apt-get install gnome'''
	8. Modify /etc/gdm/gdm.conf.		8. Modify /etc/gdm/gdm.conf.
-	* Below the section marked [Security] add the following:	+	* Below the section marked '''[Security]''' add the following:
	** '''AllowRoot=1'''		** '''AllowRoot=1'''
	** '''AllowRemoteRoot=1'''		** '''AllowRemoteRoot=1'''
-	* Below the section marked [xdmcp] add the following:	+	* Below the section marked '''[xdmcp]''' add the following:
	** '''Enable=1'''		** '''Enable=1'''
	9. Restart gdm:		9. Restart gdm:
Line 71:		Line 71:
	At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.		At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.

-	==== Current Status ====	+	=== Current Status ===

	I have also installed firefox.		I have also installed firefox.

Biscuit at 08:09, 27 November 2007

Biscuit — Tue, 27 Nov 2007 08:09:47 GMT

← Older revision		Revision as of 08:09, 27 November 2007
Line 42:		Line 42:
	3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.		3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.
	* '''mv /usr /oldusr''' - can be deleted later.		* '''mv /usr /oldusr''' - can be deleted later.
-	4. Create a new mount point for the new /usr tree. I actually forgot this step. However,[[LS_PRO_modified_initrd\|~~lb_worms~~ initrd]] helped to recover from that.	+	4. Create a new mount point for the new /usr tree. I actually forgot this step. However, [[LS_PRO_modified_initrd\|lb_worm's initrd]] helped to recover from that.
	* '''mkdir /mnt'''		* '''mkdir /mnt'''
	5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.		5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.

Biscuit at 08:08, 27 November 2007

Biscuit — Tue, 27 Nov 2007 08:08:48 GMT

← Older revision		Revision as of 08:08, 27 November 2007
Line 42:		Line 42:
	3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.		3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.
	* '''mv /usr /oldusr''' - can be deleted later.		* '''mv /usr /oldusr''' - can be deleted later.
-	4. Create a new mount point for the new /usr tree. I actually forgot this step. However, ~~lb_worms~~ [LS_PRO_modified_initrd] helped to recover from that.	+	4. Create a new mount point for the new /usr tree. I actually forgot this step. However,[[LS_PRO_modified_initrd\|lb_worms initrd]] helped to recover from that.
	* '''mkdir /mnt'''		* '''mkdir /mnt'''
	5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.		5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.

Biscuit: /* Current Status */

Biscuit — Tue, 27 Nov 2007 07:53:20 GMT

Current Status

← Older revision		Revision as of 07:53, 27 November 2007
Line 78:		Line 78:

	As to where to go from here, I am still exploring the reasons for the failures but could really do with some assistance.		As to where to go from here, I am still exploring the reasons for the failures but could really do with some assistance.
		+
		+	===== What I've tried so far =====
		+
		+	# Installed a dummy X Server. '''apt-get install xserver-xorg-video-dummy'''. Didn't make any difference.
		+	# Installed locales. '''apt-get install locales''' and set a US based locale. Didn't make any difference.
		+	# Searched the net for suggestions, made sure priviliges were set properly on /dev/pts and mounts were all ok, nothing made any difference.
		+	# Installed kde. Works, but fails in slightly different ways. Shell will not open with a similar error to gnome-shell. So I removed it.
		+	# Running epiphany with a url seems to work to some extent. For example, at the shell (logged in as root - this makes gnome-terminal work), typing in '''epiphany www.google.com''' works. However, opening up the default, debian, page fails.
		+
		+	I have had, what seem to be, kernel panics at a couple of points. None of the logs contain any useful information regarding this.

Biscuit at 07:45, 27 November 2007

Biscuit — Tue, 27 Nov 2007 07:45:40 GMT

Biscuit at 07:43, 27 November 2007

Biscuit — Tue, 27 Nov 2007 07:43:09 GMT

← Older revision		Revision as of 07:45, 27 November 2007
Line 35:		Line 35:

	1. Copy everything from /usr to /mnt/disk1/. Make sure you preserve all file right information.		1. Copy everything from /usr to /mnt/disk1/. Make sure you preserve all file right information.
-	** '''cp -a /usr/* /mnt/disk1/'''	+	* '''cp -a /usr/* /mnt/disk1/'''
	2. Modify /etc/fstab to mount /dev/sda6 to /usr. Remove the old /dev/sda6 fstab entry and replace it with the one below. This will mean you'll need to redirect all your shares if already set up. Make sure you make a backup of the original fstab for recovery if things don't quite go right.		2. Modify /etc/fstab to mount /dev/sda6 to /usr. Remove the old /dev/sda6 fstab entry and replace it with the one below. This will mean you'll need to redirect all your shares if already set up. Make sure you make a backup of the original fstab for recovery if things don't quite go right.
-	** '''cp /etc/fstab /etc/fstab.original'''	+	* '''cp /etc/fstab /etc/fstab.original'''
	The fstab entry should be:		The fstab entry should be:
-	** '''/dev/sda6 /usr xfs,acl defaults,noatime,nodiratime 0 0'''	+	* '''/dev/sda6 /usr xfs,acl defaults,noatime,nodiratime 0 0'''
	3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.		3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.
-	** '''mv /usr /oldusr''' - can be deleted later.	+	* '''mv /usr /oldusr''' - can be deleted later.
	4. Create a new mount point for the new /usr tree. I actually forgot this step. However, lb_worms [LS_PRO_modified_initrd] helped to recover from that.		4. Create a new mount point for the new /usr tree. I actually forgot this step. However, lb_worms [LS_PRO_modified_initrd] helped to recover from that.
-	** '''mkdir /mnt'''	+	* '''mkdir /mnt'''
	5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.		5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.
	If you do not see the login prompt, something may be wrong with the steps above. You should easily be able to recover from these modifications by rebooting the LinkStation 3 times and it should drop in to the safe mode shell. At this point, recovery should be done like so:		If you do not see the login prompt, something may be wrong with the steps above. You should easily be able to recover from these modifications by rebooting the LinkStation 3 times and it should drop in to the safe mode shell. At this point, recovery should be done like so:

-	** '''rm -rf /usr'''	+	* '''rm -rf /usr'''
-	** '''mv /oldusr /usr'''	+	* '''mv /oldusr /usr'''
-	** '''cp /etc/fstab.original /etc/fstab'	+	* '''cp /etc/fstab.original /etc/fstab'
-	** Reboot.	+	* Reboot.

	If this fails, I suggest getting on to the forums to see what can be done.		If this fails, I suggest getting on to the forums to see what can be done.

	6. Next, you will need to move the apt working directory. The root volume will be too small for installing gnome. To do this:		6. Next, you will need to move the apt working directory. The root volume will be too small for installing gnome. To do this:
-	** '''cp -a /var/cache/apt /usr/local/apt'''	+	* '''cp -a /var/cache/apt /usr/local/apt'''
-	** '''mv /var/cache/apt /var/cache/apt.old''' - can be deleted later.	+	* '''mv /var/cache/apt /var/cache/apt.old''' - can be deleted later.
-	** '''ln -s /usr/local/apt /var/cache/apt'''	+	* '''ln -s /usr/local/apt /var/cache/apt'''
	7. Install gnome. This will take some time. Go make a cup of tea.		7. Install gnome. This will take some time. Go make a cup of tea.
-	** '''apt-get install gnome'''	+	* '''apt-get install gnome'''
	8. Modify /etc/gdm/gdm.conf.		8. Modify /etc/gdm/gdm.conf.
-	** Below the section marked [Security] add the following:	+	* Below the section marked [Security] add the following:
-	*** '''AllowRoot=1'''	+	** '''AllowRoot=1'''
-	*** '''AllowRemoteRoot=1'''	+	** '''AllowRemoteRoot=1'''
-	** Below the section marked [xdmcp] add the following:	+	* Below the section marked [xdmcp] add the following:
-	*** '''Enable=1'''	+	** '''Enable=1'''
	9. Restart gdm:		9. Restart gdm:
-	** '''/etc/init.d/gdm restart'''	+	* '''/etc/init.d/gdm restart'''

	At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.		At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.

← Older revision		Revision as of 07:43, 27 November 2007
Line 34:		Line 34:
	So, this is how I proceeded (be careful not to reboot during these steps until needed):		So, this is how I proceeded (be careful not to reboot during these steps until needed):

-	~~# Copied~~ everything from /usr to /mnt/disk1/. Make sure you preserve all file right information.	+	1. Copy everything from /usr to /mnt/disk1/. Make sure you preserve all file right information.
	** '''cp -a /usr/* /mnt/disk1/'''		** '''cp -a /usr/* /mnt/disk1/'''
-	# Modify /etc/fstab to mount /dev/sda6 to /usr. Remove the old /dev/sda6 fstab entry and replace it with the one below. This will mean you'll need to redirect all your shares if already set up. Make sure you make a backup of the original fstab for recovery if things don't quite go right.	+	2. Modify /etc/fstab to mount /dev/sda6 to /usr. Remove the old /dev/sda6 fstab entry and replace it with the one below. This will mean you'll need to redirect all your shares if already set up. Make sure you make a backup of the original fstab for recovery if things don't quite go right.
	** '''cp /etc/fstab /etc/fstab.original'''		** '''cp /etc/fstab /etc/fstab.original'''
	The fstab entry should be:		The fstab entry should be:
	** '''/dev/sda6 /usr xfs,acl defaults,noatime,nodiratime 0 0'''		** '''/dev/sda6 /usr xfs,acl defaults,noatime,nodiratime 0 0'''
-	# Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.	+	3. Rename /usr to /oldusr. There may be some issues with processes that may be accessing /usr. I didn't have any problem with this, but you should be able to use fuser -m /usr to find out which process might be accessing that path.
	** '''mv /usr /oldusr''' - can be deleted later.		** '''mv /usr /oldusr''' - can be deleted later.
-	# Create a new mount point for the new /usr tree. I actually forgot this step. However, lb_worms [LS_PRO_modified_initrd] helped to recover from that.	+	4. Create a new mount point for the new /usr tree. I actually forgot this step. However, lb_worms [LS_PRO_modified_initrd] helped to recover from that.
	** '''mkdir /mnt'''		** '''mkdir /mnt'''
-	# Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.	+	5. Reboot the LinkStation. You should, once reboot is complete, see the normal Debian login prompt.
	If you do not see the login prompt, something may be wrong with the steps above. You should easily be able to recover from these modifications by rebooting the LinkStation 3 times and it should drop in to the safe mode shell. At this point, recovery should be done like so:		If you do not see the login prompt, something may be wrong with the steps above. You should easily be able to recover from these modifications by rebooting the LinkStation 3 times and it should drop in to the safe mode shell. At this point, recovery should be done like so:

Line 54:		Line 54:
	If this fails, I suggest getting on to the forums to see what can be done.		If this fails, I suggest getting on to the forums to see what can be done.

-	# Next, you will need to move the apt working directory. The root volume will be too small for installing gnome. To do this:	+	6. Next, you will need to move the apt working directory. The root volume will be too small for installing gnome. To do this:
	** '''cp -a /var/cache/apt /usr/local/apt'''		** '''cp -a /var/cache/apt /usr/local/apt'''
	** '''mv /var/cache/apt /var/cache/apt.old''' - can be deleted later.		** '''mv /var/cache/apt /var/cache/apt.old''' - can be deleted later.
	** '''ln -s /usr/local/apt /var/cache/apt'''		** '''ln -s /usr/local/apt /var/cache/apt'''
-	# Install gnome. This will take some time. Go make a cup of tea.	+	7. Install gnome. This will take some time. Go make a cup of tea.
	** '''apt-get install gnome'''		** '''apt-get install gnome'''
-	# Modify /etc/gdm/gdm.conf.	+	8. Modify /etc/gdm/gdm.conf.
	** Below the section marked [Security] add the following:		** Below the section marked [Security] add the following:
	*** '''AllowRoot=1'''		*** '''AllowRoot=1'''
Line 66:		Line 66:
	** Below the section marked [xdmcp] add the following:		** Below the section marked [xdmcp] add the following:
	*** '''Enable=1'''		*** '''Enable=1'''
-	# Restart gdm:	+	9. Restart gdm:
	** '''/etc/init.d/gdm restart'''		** '''/etc/init.d/gdm restart'''

	At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.		At this point, you should be able to launch xming and you will, hopefully, see the Debian login screen appear.
		+
		+	==== Current Status ====
		+
		+	I have also installed firefox.
		+
		+	Unfortunately, things don't quite seem right. I tried to open a gnome-terminal (not as root) and it would complain about not being able to create the child process. firefox, epiphany just never seemed to get working. As root, things behave differently, but still not quite right.
		+
		+	As to where to go from here, I am still exploring the reasons for the failures but could really do with some assistance.