D&C Lug - Home Page
Devon & Cornwall Linux Users' Group

[ Date Index ][ Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] problem starting kde with separate /tmp partition



On Tue, 14 Jan 2003 20:42:32 +0000, Neil Stone <Neil@xxxxxxxxxxxxx>
wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>dave morgan wrote:
>> On Tue, 14 Jan 2003 19:38:31 +0000, Neil Stone <Neil@xxxxxxxxxxxxx>
>> wrote:
>> 
>> 
>>>-----BEGIN PGP SIGNED MESSAGE-----
>>>Hash: SHA1
>>>
>>>dave morgan wrote:
>>>
>>>>hi,
>>>>
>>>>  Having a spare partition on one of my drives I
>>>>modified (in single user mode) /etc/fstab so it
>>>>looked like this:
>>>>
>>>># /etc/fstab: static file system information.
>>>>#
>>>># <file system>	<mount point>	<type>	<options>		<dump>
>>>><pass>
>>>>/dev/hde3	/		ext2	errors=remount-ro	0
>>>>1
>>>>/dev/hde2	none		swap	sw,pri=5		0
>>>>0
>>>>/dev/hda3	none		swap	sw,pri=5		0
>>>>0
>>>>/dev/hda4	/mp3		ext2	defaults		0
>>>>2
>>>>#/dev/hda2	/tmp		ext2	defaults		0
>>>>2
>>>>proc		/proc		proc	defaults		0
>>>>0
>>>>/dev/fd0	/floppy		auto	user,noauto		0
>>>>0
>>>>/dev/cdrom	/cdrom		iso9660	ro,user,noauto		0
>>>>0
>>>>/dev/hde1	/boot		ext2	defaults		0
>>>>2
>>>>
>>>>
>>>>If I uncomment the line that mounts /tmp, then after rebooting and
>>>>logging into KDE, it immediately dumps me back to the KDE login
>>>>prompt again ! the partition is approx 20Gb, it used to
>>>>be my old root on a previous installation.
>>>>
>>>>It took the reboot 15mins to get past the 'clearing /tmp' line 
>>>>the first time (wiping out my old system) !
>>>>
>>>>Any ideas what causes KDE not to like having this separate /tmp
>>>>partition, where to look for error messages ?
>>>>
>>>>best regards
>>>>dave morgan
>>>>
>>>
>>>Unsure, I had this problem with Gnome ages back... IF you copy the files 
>> 
>>>from the old /tmp to the new /tmp (ie a temporary mount of the 
>> 
>>>partitioned /tmp to /mnt then cp -R /tmp* /mnt) does that work ?
>>>
>>>Neil
>>>-----BEGIN PGP SIGNATURE-----
>>>Version: GnuPG v1.2.0 (GNU/Linux)
>>>
>>>iD8DBQE+JGc3ETbMU8Wu6mERAi5kAJ4rkvd/pp2K/AcL/FmYP2+nSNmDvACgg3so
>>>I9t0HQF8F4t8wFsHsm1cfeU=
>>>=YqEl
>>>-----END PGP SIGNATURE-----
>> 
>> 
>> Tried this, no difference at all !
>> any ideas where to look for error logs ?
>> 
>> I am assuming having separate /tmp partition
>> directly mounted is legal !
>
>Yes, thats what i have now... The only solution i found was to re run 
>the configuration for X, I have no idea what caused the problem and why 
>clearing out my /tmp broke X but.. hey I found a work around !
>
>Neil
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.0 (GNU/Linux)
>
>iD8DBQE+JHY4ETbMU8Wu6mERAoB6AJ9OTYOgbmjO/e4HoHUn+NJ/vCQb6wCcCdRe
>sAMVKlW9ju6sNWI07jqb7h8=
>=b+if
>-----END PGP SIGNATURE-----


Neil,

after some digging it could be a permissions problem:

the normal /tmp is     drwxrwxrwt
my mounted attempt is  drwxr-xr-t

any ideas how to get mount permissions right ?

best regards
dave morgan
-- 
http://www.eclipse.co.uk/morgad/index.html
UKRA#1243
from address killfiled. use reply-to address for replies !

--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe.


Lynx friendly