[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: deleted /tmp ruined X, how to recover?



> Bryan, thanks a lot for reply.
> I tried to set the permission to the new /tmp to 777. startx as root,
> still get the same result. the error msg are as followed:

It needs to also be sticky:
	chmod +t /tmp 

> _Font TransSocketUNIXConnect - can't connect:error=111
> failed to set default path 'unix/:-1'
> Fatal server error
> could not open default font 'fixed'
> 
> I also install the font server  but still the same. What can I do still?
> 
> thank you
> Ben
>  
> 
> 
> 
> On Sat, 28 Oct 2000, Bryan K. Walton wrote:
> 
> > Recreate /tmp and make sure that the permissions are set correctly so that users other than root can read the directory.
> > 
> > -Bryan
> > 
> > 
> > 
> > On Sat, Oct 28, 2000 at 04:28:21PM -0400, Benjamin F. Zhou wrote:
> > > Hi,
> > > 
> > > I got a message saying the file system on which /tmp is located is full.
> > > 
> > > Thinking /tmp contains only temperary files, I deleted them all. But after that
> > > I can no longer start X. I can still run Xconfigurator and configured
> > > successfully.
> > > But startx keeps failing.
> > > 
> > > what should I reinstall? I want to avoid reinstalling from scratch.
> > > 
> > > thanks a lot for your hint
> > > 
> > > Ben
> > > 
> > > 
> > > --  
> > > To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > 
> > -- 
> > Bryan K. Walton
> > Network Operations Center Analyst
> > Berbee
> > 5520 Research Park Drive  Madison, Wisconsin 53711
> > 608.288.3000
> > 
> > Berbee...putting the E in business
> > 
> > 
> > --  
> > To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > 
> > 
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 



Reply to: