[ILUG] Commands have stopped working - Some Success

[Darragh]

Just be fore I start.  I've being calling the rong script when replying to
messages.  I've fixed it now so it asks me if I'm sure bla bla bla so I
shouldn't mistakenly send messages to people instead of to the list again.

>  what are you going to change in the startx script?!  **ANY**
>  customisation for startx should go in your ~/.xinitrc scrips.
>
oh no, I'm just putting the path to x in the path line in`~/.bashrc

>  in general the lesson from this experience is that you should avoid doing
>  things as root wherever possible.  if you'd like to do an overall quick
>  check of the packages on your system i'd do this (which you need to do
>  as root sadly):
>
True.  However, I find that getting everything set up and then messing with
permissions is better than messing with permissions from the start.
However, I'm more than likely rong.

>      su -
>      cd /tmp
>      rpm -a --verify --nodeps --nomd5 --noscripts > /tmp/changed
>
>  you can then review the files that have been changed.  to find the
>  package that belongs to an individual file, do this:
>
>      rpm -qf /path/file
>
>  and lastly rpm doesn't tend to delete files.  that /etc/passwd file
>  earlier shouldn't have been overwritten.  there should be a
>  /etc/passwd.rpm* file somewhere.

Thanks I saved the output of the file when I did the first rpm command.  I
didn't see anything there of interest but then again, I don't really know
what I'm looking for so if someone wants a look give me a shout and I'll
send it off list, its kind of long.

I also found the rpmsave files, that's a nice little feature isn't it?  Any
way, I've replaced the new files with the .rpmsave ones and the start up and
shut down errors are gone.  At least that's one problem out of the way.

I put the path /usr/X11R6/bin/ into the path line in .bashrc and I have
gnome Gnopernicus Open office and even the Access-Bridge working so again
I'm happy enough.  As these are only tempory measures though I'd like to get
to the cause of the problem.  The errors are still appearing at start up.
Their listed below again for any one interested:

-bash: id: command not found
-bash: id: command not found
-bash: id: command not found
-bash: [: too many arguements
-bash: put: command not found
-bash: put: command not found
-bash: wc: command not found
-bash: [: : integer expression expected

I saw a mention of GlibC on the open office.org site.  Could replacing this
program have caused these problems?  I ask as I think someone mentioned it
today.

Thanks

Darragh