SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I use XEmacs at home and at work and I'm having a problem in slackware that I've not had on Windows or PCLinuxOS. I just installed Slackware and got X up and running by installing a new kernel (2.6etc) -- actually X was fine, it was the mouse that was having problems with the old kernel.
Last night I was doing some customizing, so I copied my custom.el and init.el from my work computer (which I'm just realizing could have caused the problem...I use Windows at work) and copied them into a .xemacs directory for root and one for joel (that's me when I'm non-root).
First there were some problems reading init.el:
did not work and gave me a warning.
Then, whenever I edited init.el, it would save under root ownership. I did
chown joel:adamson init.el
a few times before I realized it was reverting to root:root each time I edited and then saved it.
Any ideas? Does slackware have any security policies that might do this?
I mistakenly said "I put" when I should have said "custom saved" -- the "quote" was a result of the save by custom in custom.el.
Good suggestion on the Xresources, I'll try it.
The funny thing is that when I raise new frames (a new habit for me), they're the right size. So it seems that the initial frame is set by Xresources and the rest are sized according to custom.el. The only problem is that 'initial-frame-plist is supposed to override Xresources (or so says Customize).