SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
notice that a new empty file is created, /etc/udev/rules.d/99-udisks-ntfs3g.rules.
this really shouldn't be empty , but maybe it's better this way so you can choose
if you want to force your desktop environment to automount your external ntfs drives and memories using the fuse ntfs-3g driver instead of the kernel one (preferred here), fill that file with this content
Probably a better way to handle that is to make /sbin/mount.ntfs-3g symlink at /sbin/mount.ntfs -- then it "just works" without any changes on the user end. I think the ntfs-3g driver is stable enough at this point that it should be safe to do that.
Probably a better way to handle that is to make /sbin/mount.ntfs-3g symlink at /sbin/mount.ntfs -- then it "just works" without any changes on the user end. I think the ntfs-3g driver is stable enough at this point that it should be safe to do that.
Been working here fine for the past month or so too =)
The new lxdm.conf wants to remove the correct location of lxdm-greeter-gtk and add an incorrect one.
Code:
-greeter=/usr/libexec/lxdm-greeter-gtk
+
+## set this if you don't want to put xauth file at ~/.Xauthority
+# xauth_path=/tmp
+
+## greeter used to welcome the user
+greeter=/usr/local/libexec/lxdm-greeter-gtk
Yet,
Code:
[lxde@slackware-x86 ~]$ ls -al /usr/libexec/lxdm-greeter-gtk
-rwxr-xr-x 1 root root 48844 Sep 30 18:36 /usr/libexec/lxdm-greeter-gtk
[lxde@slackware-x86 ~]$ ls -al /usr/local/libexec/lxdm-greeter-gtk
ls: cannot access /usr/local/libexec/lxdm-greeter-gtk: No such file or directory
If you overwrite the old config file with the /etc/lxdm/lxdm.conf.new, then on boot you are greeted with a blank screen.
I think that path has been hardcoded by some commit by the lxde devs in the new lxdm sources, so will be better to report the thing upstream.
BTW, I'm gonna patch it soon in the slackbuild on github, as I return from holidays (it's hard to do it by cell phone), just wait a little.
you can check for dependencies on slackbuilds.org if you need single packages,
but all you need besides a current full default installation should be
already in this folders
(latest global rebuild 29 september 2012)
- - -
- ./testing
some testing stuff
- ./32bit-stuff
some 32bit packages that I use on slackware64-14.0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
, but maybe it's better this way 
so you can choose 
