[Sussex] permissions & crashes?

[John D.]

On Thu, 2005-01-06 at 23:39 +0000, Thomas Adam wrote:
> On Thu, Jan 06, 2005 at 11:31:27PM +0000, John D. wrote:
> > Done that Thomas, but now the app (gnubg) tries to start but stops
> > after about a second or two.
> 
> The permissions on that binary are weird. There's nothing stopping you
> from issuing the command (as root):
> 
> chmod 755 $(which gnubg)
> 
> ... in fact, this is what I *would* do. None of this crap with group
> ownership. It's nonsensical for an application such as gnubg.


Which gives me:-

johns root # chmod 755 $(`which gnubg`)
which: no gnubg in
(/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3:/usr/X11R6/bin:/opt/blackdown-jdk-1.4.2.01/bin:/opt/blackdown-jdk-1.4.2.01/jre/bin:/usr/qt/3/bin:/usr/kde/3.3/sbin:/usr/kde/3.3/bin:/usr/kde/3.2/sbin:/usr/kde/3.2/bin)
chmod: too few arguments
Try `chmod --help' for more information.
johns root #                             

I presume that's a system based "pair of fingers"?

Weirdly enough, it seems that it will "fire up" in a terminal but then I
get loads of this

(gnubg:11685): GdkGLExt-CRITICAL **: file gdkgldrawable.c: line 141
(gdk_gl_drawable_gl_begin): assertion `GDK_IS_GL_DRAWABLE (gldrawable)'
failed

pages and pages of it, in the terminal, as soon as I quit the terminal,
the gnubg game quits as well

> > I haven't got a clue as to where I'd find a log for gnubg - cos it
> > doesn't seem to have an entry of any kind in /var/log?
> 
> Applications rarely log to /var/log/messages -- only daemons. I note
> that gnubg uses libguile (scheme) -- have you run "gnubg" in an xterm?
> Do you see any output from that? Failing that, we might have to go down
> the strace route, but I'll wait and see.
> 
> > I have absolutely no idea of how I'd accomplish cd ripping/encoding
> > with CLI anyway. even the link that was posted for me last week
> > about a "dictionary" of commands isn't much help, as it's just an
> > alphabetical list of commands i.e. more of a glossary, rather than a
> > list of "stuff" that then identifies the command that I'd need to do
> > something.
> 
> Just what kind of dictionary are you after, John? I could quite happily
> put something together for you.

Nah, it would be impractical Thomas, it's not so much of a dictionary,
but more of a Thesaurus that I'd need i.e. look up one of the words and
it cross references any commands that might even be vaguely associated,
or even a command database, and a dropdown box for I want to ...........
which would then generate a page of whatever and maybe a link to a
manpage to show all the possible switches/arguements etc etc.

Even if it was just plain text and a link, if it caught on, imagine the
bandwidth consumption (it'd probably give me bloody consumption or at
least a coughing fit when I saw the bill!) still, I might think about
it, as it could be something that could be downloaded as a package ???
(thinking about it though, the idea could work with something that's
already up and running, I might just suggest the idea to Jeremy Garcia
at Linuxquestions.org).


> > Plus, even though I have a link about decyphering man pages, they're
> > still pretty much a total mystery too me.
> 
> Manpages have always caused contention (don't even get me started on
> info pages). Can you elaborate?

This http://www.cs.mcgill.ca/~guide/help/man.html is the link I've used
in the past to try and understand what a man page is telling me, but as
you can probably see, it's trying to cover such a multitude of sins, you
can't always get your head round what the man page your'e trying to read
is telling you - especially the ones that stretch to many pages!

Where I fall over, is that so often I don't even know what command I'm
actually looking for (and it doesn't help that if, like me, you happen
to be a little impatient). Which is the main drawback of the list here
http://www.onlamp.com/linux/cmd/ and as you could probably see, that's
it's just stuff extracted from an O'really book - and I find reading
O'really as dry as buzzards arse at the height of summer! i.e. Hard
work!

regards

John D.
--