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.
YAHI (yet another HAL issue) I'm afraid. Does anybody know if
it's possible to force mount options on devices using HAL?
Specifically, I want to force the noexec option on removable media
mounted by HAL. This is a slack 12.0 issue. I haven't tried it
on 12.1, yet.
I've also tried the deprecated volume.policy.mount_option.noexec
option, but that's completely fruitless, too.
The keys all get added to the devices in question, but get ignored
As yet, the only way I've managed to force this is by changing
line 70 of hal-storage-mount.c from
#define MOUNT_OPTIONS "nosuid,nodev"
#define MOUNT_OPTIONS "noexec,nosuid,nodev"
Is there a better way (without mucking about with KDE)?
a) Have I understood it correctly that HAL is designed
specifically only to provide a list of valid mount options to some
user proggy like a KDE app? Can any user proggy - given that
it's authorised via a group (eg plugdev) membership to speak to
HAL via the message bus - decide what options to use or NOT to
use and request hald, a root process, to do its bidding?
b) Is it true that whilst HAL provides for a list of allowed mount
options (volume.mount.valid_options), it provides no way of
enforcing important options like nosuid, nodev and noexec (BY
DESIGN)? Is it true that it is up to the discretion of a user
proggy what it uses and doesn't use to mount? So if
hal-storage-mount.c did not define nosuid at line 70, then there
would be no method available in HAL's complex xml config files of
stopping users mounting their disks, and gaining root privs.
c) Does this demonstrate something very broken in HAL's design?
If not, what am I missing?
Thanks for getting back to me. I guess there are many
ways of auto-mounting, and imposing policies. I really
was posting to see if I was wrong regarding
one's inability to impose system mount policies in HAL
without resorting to patching the hal-storage-mount.c. I'm
still unsure if I'm right or wrong.
I think they (or David Zeuthen) removed volume.policy.mount_option
because people were putting stuff in there that they should have
been devolved to the user proggy, an that broke their/his vision, and
the cleanness of the idea. For me, it makes HAL less of a system.