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.
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 there a way to override this new mount point location and restore back to /media?
Unfortunately no, /media is going to be obsolete now.
However there are few thing you could do, at least for now. Get rid of udisks2 and stick with udisks as long as posible or apply this patch (http://paste.lisp.org/display/129168), but it isn't long-term solution.
Apparently udisks developers decided that instead of implementing certain feature (actually useful one) the right way (read: harder), they simply break standards (FHS in this case) without worrying "what could possibly go wrong?". Sounds familiar? Yes, it's the same systemd-like mindset - "I like it that way, so it'll become new standard. XYZ isn't relevant anymore." I guess only long-term solution is to fork udisks2 and let GNOME (udisks2 will be it's default auto-mounter) , udev+systemd guys live in their Perfect World (TM) alone, while we'll be using saner software in saner way.
Distribution: Linux Mint 19.1 & Slackware64-Current
Posts: 221
Rep:
That's what I don't understand. Why /run? What are you running? usually when I mount a cd or dvd it is to view files. /media is perfect name for it. You don't "run" media.
I really like the new xfce4 weather module, but what's happened to the xfce4 power manager? I can't find it.
Oh, nevermind...
It seems slackpkg was having trouble with the new xfce 'diskset' -- it didn't install xfce4 at all the first time, so I tried again and it found several more packages, but not all of them.
I ftp'd the current install sets and tried again and now I have everything I was looking for.
Maybe a lot of that 'cruft' I lost was actually packages that got missed. I'll keep looking for other missing pieces...
It seems slackpkg was having trouble with the new xfce 'diskset' -- it didn't install xfce4 at all the first time, so I tried again and it found several more packages, but not all of them.
If you run -current it is recommended that you also read the changelog. From Sun Jul 22 22:38:36 UTC 2012:
Quote:
ap/slackpkg-2.82.0-noarch-6.tgz: Rebuilt.
Support XFCE series. Note that slackpkg will upgrade itself, but it still
won't know about the XFCE series during that run, so you'll need to run it
a second time to install Xfce.
If you run -current it is recommended that you also read the changelog. From Sun Jul 22 22:38:36 UTC 2012:
Thanks, I missed that line...
upgradepkg --install-new says I now have everything installed. Looks like the xfce group was the only one missed the first time and brushed over the second time.
I wonder why it didn't install all of /xfce the second time?
you could also alternatively, on a 32bit host, do a
Code:
slackpkg install slackware
or if are using the 64bit version
Code:
slackpkg install slackware64
to install al the stuff in the distribution, exactly the remaining beside the one you already have installed (minus what you have in /etc/slackpkg/blacklist).
Unfortunately no, /media is going to be obsolete now.
Yet Another WTF moment. And I wonder why part of me grows ever more cynical with free/libre software.
One of the reasons I left the Microsoft world is the proprietary mindset. Over the past two years, with the RedHat people controlling more and more of upstream code, I am seeing that same mindset starting to infect free/libre software. There no longer seems to be a spirit of cooperation and instead I see a push toward domination and control. I'm not discounting the contributions RedHat people make to free/libre software, I'm noting attitudes and the complete lack of concern of what happens to anybody else.
I suppose ideally Slack users and others who would rather not deal with these sorts of arbitrary changes should patch and/or produce alternative components to replace functionality although of course its not always that simple
Yet Another WTF moment. And I wonder why part of me grows ever more cynical with free/libre software.
One of the reasons I left the Microsoft world is the proprietary mindset. Over the past two years, with the RedHat people controlling more and more of upstream code, I am seeing that same mindset starting to infect free/libre software. There no longer seems to be a spirit of cooperation and instead I see a push toward domination and control. I'm not discounting the contributions RedHat people make to free/libre software, I'm noting attitudes and the complete lack of concern of what happens to anybody else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.