[maxim2]

Hey!!!! How goes it?

I'm gonna try to install Slackware 8.0 again. Umm...are there any good guides on the internet? It's been a VERY long time. However, I"m going to try it again.

Any help is appreciated!

--maxim2

[codejockey]

You might take a look at www.slackware.org and www.linuxnewbie.org. Both contain some good information on installation and configuration issues.

Hope this helps.

[maxim2]

I can't get X to work now. Everytime I configure it and such, and I always take a look at my xf86, it lists commands, then says "Command not found". Um, maybe my onboard intel i810e graphics 'card' doesn't work with Slackware 8.0?

Thanks!

--maxim2

[codejockey]

If the message you get is "command not found" or something similar, I wonder if it's not coming from your xinitrc file rather than your XF86Config file. Typically, the xinitrc file contains commands (scripts, etc.) to be run at X startup, and the XF86Config file contains configuration information for X itself (hardware info, etc.). If your XF86Config file is incorrect, usually X won't even start, or if it does, the display is hosed. Could you post the last few messages you receive before the "command not found" one? That may help isolate the problem.

Any info appreciated.

[maxim2]

/var/log/XFree86.0.log: protocol: Command not found.
/var/log/XFree86.0.log: release: Command not found.
/var/log/XFree86.0.log: if: Command not found
newer: need exactly 2 arguments
Try 'newer --help' for more information
/var/log/XFree86.0.log: line 7: syntax error near unexpected token '(s)
/var/log/XFree86.0.log: line 7: 'reporting problems.

that's what it says.

Any ideas?

--maxim2

[codejockey]

I know this sounds crazy, but ... is it possible that you are attempting to execute the /var/log/XFree86.0.log file when you invoke X? If you look at this file, you will find that it contains each of the words referenced in the error messages in the order in which they appear ... not to mention the reference to line 7, which, on my system is:

reporting problems. (See http://www.XFree86.Org/FAQ)

Are you using the startx command or perhaps a different script to run X? If you could provide the actual command(s) you are typing in order to start X (or the script(s) that are doing it) that would be helpful. Right now, I'd suspect a misplaced argument or missing option on the X command line during startup.

Hope this helps.

[maxim2]

I just type startx.

I don't think I'm trying to execute the /var/log/XFree86.0.log file. To bring it up, I just type /var/log/XFree86.0.log (I think).

Oh no...
"reporting problems. (See http://www.XFree86.Org/FAQ)"

Yes, it says that too. umm...Ok, as the kiddies say: "My bad"

hope that helps!

--maxim2

[maxim2]

<a href=http://www.lilug.org/pipermail/lilug/2001-July/002988.html>This</a> and <a href=http://www.lilug.org/pipermail/lilug/2001-July/002989.html>this</a> possibly might be of use.



--maxim2

[codejockey]

You might try running the startx script in debug mode. If you don't know where the startx script lives (likely /usr/X11R6/bin), give the command: type startx and take note of the output. Then invoke startx using: sh -x full-pathname-of-startx-script (e.g., sh -x /usr/X11R6/bin/startx) and see how far you get. The -x option prints each line before executing, and includes variable substitutions, etc. which can help identify a problem.

Also, you're probably not just typing /var/log/XFree86.0.log at the command line to look at the file. If you are, you are, in fact, trying to execute this file (and of course it will fail). You are more likely typing something like: more /var/log/XFree86.0.log or vi /var/log/XFree86.0.log or something similar (i.e., you are using a pager or an editor to look at the contents of the file). Unlike Windoze, Unix/Linux does not automatically invoke an application associated with a particular file; you are free to use any and every application you wish to operate on a file (of course, you have to be prepared for the results if you, for example, choose to open a binary file with a text editor ... 8-)).

Hope this helps -- and keep the info coming!