Help restoring messed up settings

[Chris Green]

On Tue, Nov 05, 2002 at 09:54:03AM -0500, Net Llama! wrote:
> > I did 'poke around' but since I hadn't a clue what file or directory
> > it needed to write my poking around was rather undirected.  If it had
> > simply said in the error message *what* file it couldn't write (full
> > path needed of course) then I'd have known immediately what was wrong.
> 
> It did.  You conveniently snipped that out of this email.
> 
Huh?  What I was talking about was the pop-up message box which says
*only* "Cannot create file" with no indication as to the file name or
the path to it.  I didn't snip it out of the E-Mail, it's simply not
there.  OK, so there's more information in the .xsession-errors but
that file is not immediately obvious or visible and I only found it
later.

> > > > > As root:
> > > > >
> > > > > # chmod 666 /dev/dsp
> > > > >
> > > > I wonder why it doesn't get installed this way?
> > >
> > > What makes you so sure it doesn't?  I think the problem is your backups.
> > >
> > If you'd read my original message you would have noted that the disk
> > I lost was the /home disk.  /dev/dsp is most definitely not on /home.
> 
> Then perhaps the problem extends beyond your backups.  At any rate,
> permissions on /dev/dsp are not universal, they're specific to your setup.
> 
All I said was "I wonder why it doesn't get installed this way?" which
it presumably does on my SuSE system as I certainly haven't changed it
since install time.

-- 
Chris Green (chris at areti.co.uk)