Hi,

Maybe I was to critical in my read.

I think you took my response to your pages the wrong way. I didn't intend to cause offense but to assist in the presentation. Your pages as I stated are great. I keep system logs for all my systems to help in the diagnosis of problems. The technique has gotten me out of some deep holes.

I maintain my systems through a ssh as root via a console. But when logged physically I root only when needed for system edits or changes.

As for the reboot issue, I have at times had to reboot because of problems. I tend to want to know what is not working and why, instead of just shirking it off. Sometimes to ignore a problem via a reboot, the same problem can then come back to bite you after the reboot. Rebooting without solving a problem can create other questions that could have been resolved by investigation of an issue instead just rebooting in hopes of solving the problem. Just my style!

I'm not saying that first person can't be used. You just need to complete the thought. I'm not standing behind you therefore the console is blurry through the crystal ball. Really, I have a tendency to not complete my thoughts to paper but when 'I' re-read an entry, a annotation is then made to complete the thought or expand on it. I see your reasoning to my comment but feel you should expand on the idea of reflection of the thought you place on paper/console. Sure the errors are a good trail but the idea here is to provide the means for someone to see a roadmap to getting something to work. Therefore the writing should implement a means to compile the process into a functional operation or presentation.

As I said, Your pages are great! Just my comments to what 'I' feel could be added to help someone who has problems with getting things functional.

BTW, I do take it easy!

That is one of my points, if the install or maintenance is for system wide then root is required. You don't have to be root to ./configure, make or make check. Instead you could just su or sudo which depends on method of choice as long as the tar files have been expanded as user.

Sure this example may not be the best choice since most would choose xmmx system wide use.

No need to defend yourself! I've been in the field a long time and thankfully still learn something new everyday. I appreciate the thanks! Maybe I should have made a salutation;
'Welcomed To Slackware' to you!

As to the cd and dvd problem in 2.4.33. The 2.4.33 kernel uses the ide-cdrom driver to control. The device(s) usually are assigned the /dev/hdc(1st device seen) and /dev/hdd (second device seen) on ide1 if that is how your system is configured. I've got a system configured with /dev/hda as the cdrom on ide0 with the ide-cdrom driver.

My original response referred to 2.4.31(ide-scsi) vs 2.6 (ide-cd) in error. Mixing releases again. Requires reboot!



This is a can of worms! System wide permisions should be used sparingly to avoid security issues.

As stated above! But what about the system?

Hi gwsandvik,

All good points. I agree with them all.

With regards to the device issue (which still really bugs me, system wide is bad), I am thinking of just upgrading the kernel to one of the 2.6.X versions that come with Slackware 11.
I remember when I upgraded the kernel to version 2.6.x (something) on Slackware 10, all my devices worked straight away without issue.

Also, you are right about the root thing for ./configure for example, I just never really thought about it properly. I have so much to change! But it is all good. I think writing the document was really good for me, I needed people to point out the things I am doing wrong. I think it is easy to say "Oh, I know how this works, I know how to do this..." it is only when you hand it to someone else to see, that you realise what you are doing wrong.

Also, I never took offence to what you said, seriously Just by talking to you and the other people who posted, I learned a great deal. So much so, that I will change how I configure Slackware in the future. Good job! It is difficult to convey ones thoughts on a forum without the chance of being misunderstood.

Take it easy,

Moschops.

PS, the document will be changed this weekend!

Hi,

Your log styles are good. Don't bias them, just polish.

To give a simplistic viewpoint! To make something open or system wide, it is like leaving the key in the lock for your front door. Just an invite for someone to do something. When you could place the key in a safe place that allows the people who know where to look to get the key to perform the operation that you want done. Thus guarding your system by allowing trusted users to perform a wanted action.

Sometimes the upgrade to the 2.6 kernel can resolve the device(s) issue. Usually due to the udev vs hotplug differences.

I feel everyone needs to expand thier abilities. Sometimes we all get into a habit that will come back an cause a problem. The root thing I mentioned is just that, a habit. You can get yourself into some real problems if your not careful when using root. Even su or sudo can get you if not careful but the commands are there to help in the prevention or to safeguard;

As pointed by the "man" output, the safeguards are there to inhibit and also provide a means to trace the use. Typos can get you either way. Semantics especially will create more havic than syntax.

I agree whole heartily! It can be difficult to convey thoughts across a forum. Especially for understanding between cultures and societies with difference. I just re-read 'How to Ask Questions the Smart Way' and a few things jumped out and whacked me! So we all learn or re-learn things from others. I do re-read my references periodically to keep up with possible changes and to be sure that the material is still solid. Plus I do this to keep the old mind active!

I do take it easy! The document will be a great contribution to the Slackware community. Thank You!

So that's your own package that you built. I'll download it since I definitely need wine to play Day of Defeat. Many thanks for putting your thoughts on an easy to read web page. Good work.