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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Is udev setting the correct permissions on /dev/shm at drwxr-xr-x ?
Real time audio, e.g. Jack Audio Connection Kit, doesn't have write permission if started as a user of group, root...
Due to unresolved problems reading optical discs, some of us must constantly reload udev's rules which naturally resets permissions to their defaults so modifying rc.local or fstab isn't a solution unfortunately.
I have "drwxrwxrwt" for /dev/shm/ here, same on a slackware64-13.37 box.
Maybe check if you have an option set for /dev/shm in /etc/fstab (umask maybe or something).
When saving a file using mcedit, mcedit tries to create a temporary file "tmp/cooleditXXXXXX" which should actually be "/tmp/cooleditXXXXXX". So mcedit cannot save files unless there happened to be a "tmp" dir.
However, the "save as" function works as expected. And this bug is not there when I'm root.
Not tried yet, but 3.2.28 + udev-182 is causing a 30s delay on startup here. Very, very annoying!
Searching the web for "udev 30 seconds" redirected me to ArchWiki. I tried the solution from there (to add the problematic module, ipw2200 in my case, to the initrd) and everything is ok now.
I thought it won't be solved, until someone fix udev or ipw2200. The harmless error (error: cfg80211: failed to add phy80211 symlink to netdev!) still appears, but udev no longer timeout with ipw2200 module. Thank you!
Yes, I know what you meant and showed an image of the strength indicator in my setup in a previous post a few messages back.
Edit in: Actually, it doesn't really matter. I just re-installed the NM icon to the system tray and it looks just like the one on the panel, just smaller, of course. It would appear the solution to your problem is really a matter of picking the right combination of desktop "decorations" and "themes" to make the NM icon appear brighter against a dark background.
Here is another image of both the NM widget on the panel and the NM icon in the system tray.
Last edited by cwizardone; 09-07-2012 at 02:48 PM.
Yes, I know what you meant and showed an image of the strength indicator in my setup in a previous post a few messages back. As I've already said, remove the NM icon from the system tray and install the NM widget on the panel.
I replied your previous post of "remove the NM icon from the system tray and install the NM widget on the panel" to say that that does not mend at all. Maybe you did not see my reply in this long thread. I attach my screenshots again here: