Slak 12 does not see CD/DVD drives
Marv Soloff
tiny problem:
it does not see my two CD/DVD RW drives (hdc and hdd). When I try to
access them or
mount via KwikDisk, I get a panel saying I do not have
rights/permissions to open these
items etc.
Any Ideas?
Marv
Two Ravens
> Installed Slack 12 on a test 40GB drive this afternoon. Very slick.
> One tiny problem:
> it does not see my two CD/DVD RW drives (hdc and hdd).
>
> Any Ideas?
Read the thread Alt.OS.Linux.Slackware FAQ pointer, you'll find that
whilst I had the same problem there was a solution.
--
Two Ravens
"...hit the squirrel..."
Marv Soloff
> Marv Soloff wrote:
>
>
>>Installed Slack 12 on a test 40GB drive this afternoon. Very slick.
>>One tiny problem:
>>it does not see my two CD/DVD RW drives (hdc and hdd).
>>
>>Any Ideas?
>
>
> Read the thread Alt.OS.Linux.Slackware FAQ pointer, you'll find that
> whilst I had the same problem there was a solution.
OK - what you seem to be saying (FAQ) is that Slack 12 has some
libraries missing
from the distribution. Not quite ready for prime time are we? For the
nonce, I'll stick
to Slack 10.2.
Marv
Two Ravens
> OK - what you seem to be saying (FAQ) is that Slack 12 has some
> libraries missing from the distribution...
Not quite, for some reason when I installed the installation system
wouldn't accept kdeedulibs-3.5.7, in order ot ge them in I had first to
sort out how and what HAL did, which with the guidance fo Robby
Workman's excellent advice I did. Having done so, I could then read the
CD and install using pkgtool the missing lib.
> ...Not quite ready for prime time are we? For the nonce, I'll stick
> to Slack 10.2.
I did whilst I installed and used 11.0, however as 12 seems so much an
improvement I'll put that, (12.0), onto the partition on the other disk
where 10.2 is.
Marv Soloff
simple comment "out" of
the /dev/cdrom line in /etc/fstab. Removed the "#" , rebooted, and voila
- the cd/dvd drive
is recognized. We go forward. Thanks for your help.
Marv
Two Ravens
> AN UPDATE: - problem appears to be not missing libraries but just a
> simple comment "out" of
> the /dev/cdrom line in /etc/fstab. Removed the "#" , rebooted, and
> voila - the cd/dvd drive
> is recognized. We go forward. Thanks for your help.
I don't think that you've got that quite right, put the # back where it
was, and add the user to the appropriate part of /etc/groups. Do what I
did, re-read the advice from Robby Workman again.
Although it may be that you have got it right, and I have got it wrong,
but it all seems to be working for me, and I can't believe that the
maintainer would have commented out part of the fstab without good
reason.
Marv Soloff
Works for me. At this point, it is the fix of my choice - i.e. least
effort.
I spent half a lifetime scrutinizing code for mistakes. Now that I am
retired
and am not getting paid for it, the least effort method is the one I go to.
Try it. You and Workman may have it wrong.
Thanks again.
Marv
Thomas Overgaard
Two Ravens wrote :
> Do what I did, re-read the advice from Robby Workman again.
I guess there's more ways to skin a cat. I cant get Robby Workman's
method working so I have to have an entry in /etc/fstab for the
devices.
One thing is that you have to set the owner in fstab to "user" or else
the users cant mount the devises.
--
Thomas O.
This area is designed to become quite warm during normal operation.
Two Ravens
> I guess there's more ways to skin a cat. I cant get Robby Workman's
> method working so I have to have an entry in /etc/fstab for the
> devices.
>
> One thing is that you have to set the owner in fstab to "user" or else
> the users cant mount the devises.
From what I remember that was always the way I did it, I used the
example from that excellent resource 'Userlocal'
http://www.userlocal.com/tips/usermounting.php for several versions.
In fact it was mRgOBLIN's printing article that I also used to run
printing in Slackware, I could never remember how I'd set it up last
time when the next version came out so I'd turn to 'Userlocal' with
each new version. Its just that Robby Workman's way of making devices
work for users was on this newsgroup, perhaps 'Userlocal' should get
him to let them put it in with all their other useful stuff, and maybe
it could also be a contribution to the FAQ.
Thomas Overgaard
Two Ravens wrote :
> Its just that Robby Workman's way of making devices work for users was
> on this newsgroup
For another reason I rebooted the computer and now it works like its
supposed to without the entry in /etc/fstab
I hate it when shit like this happens. I'm a slacker and I'm supposed to
be in control! But f?cking no.
Robby Workman
>
> Two Ravens wrote :
>
>> Its just that Robby Workman's way of making devices work for users was
>> on this newsgroup
>
> For another reason I rebooted the computer and now it works like its
> supposed to without the entry in /etc/fstab
Almost certainly due to the fact that the messagebus service had not
been restarted. Rebooting, of course, fixes that :-)
RW
Thomas Overgaard
Robby Workman wrote :
> Almost certainly due to the fact that the messagebus service had not
> been restarted. Rebooting, of course, fixes that :-)
Maybe, but I thought that '/etc/rc.d/rc.messagebus reload' would fix
that. But HAL is something completely new to me. so I could be wrong-
Robby Workman
>
> Robby Workman wrote :
>
>> Almost certainly due to the fact that the messagebus service had not
>> been restarted. Rebooting, of course, fixes that :-)
>
> Maybe, but I thought that '/etc/rc.d/rc.messagebus reload' would fix
> that. But HAL is something completely new to me. so I could be wrong-
Well, it should have. The only other thing you *should* have needed
to do is log out and back in...
RW
Thomas Overgaard
Robby Workman wrote :
> Well, it should have. The only other thing you *should* have needed
> to do is log out and back in...
Oho. Forgot that one, now I understand what did happen. Thanx.
Sylvain Robitaille
>> Maybe, but I thought that '/etc/rc.d/rc.messagebus reload' would fix
>> that. But HAL is something completely new to me. so I could be wrong-
>
> Well, it should have. The only other thing you *should* have needed
> to do is log out and back in...
I'm coming into this discussion fairly late (still catching up; you guys
were busy while I was on vacation!), but (and perhaps it's just me) I
was under the impression that HAL and DBUS and the rest of these things
were supposed to make it *easier* to use removable devices. It looks to
me (though I've not yet seen Slackware-12.0) as though it has been made
more complicated.
They (the kernel and "rest of the system" developpers) had something
that worked just fine: add a line to fstab with appropriate options and
ordinary users would be able to mount removable disks. Now they've gone
and broken that so the kernel can mount the disks for you???
--
----------------------------------------------------------------------
Sylvain Robitaille s...@alcor.concordia.ca
Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------
Michael Black
> Robby Workman wrote:
>
>>> Maybe, but I thought that '/etc/rc.d/rc.messagebus reload' would fix
>>> that. But HAL is something completely new to me. so I could be wrong-
>>
>> Well, it should have. The only other thing you *should* have needed
>> to do is log out and back in...
>
> I'm coming into this discussion fairly late (still catching up; you guys
> were busy while I was on vacation!), but (and perhaps it's just me) I
> was under the impression that HAL and DBUS and the rest of these things
> were supposed to make it *easier* to use removable devices. It looks to
> me (though I've not yet seen Slackware-12.0) as though it has been made
> more complicated.
>
wording was) seemed apt, not the thread but the question, because
Slackware 12 is the first I've heard of it. I looked it up, and
the "d-bus" too, but I haven't really studied what I searched for,
so I still only have a basic idea of it all. Before we can really
make it work, we've got to figure out what its purpose is.
When I installed Slack 12 on Monday, I simply told the install to
not start the two relevant daemons. It seemed to be the simplest
solution, not that I've gotten far enough to play with it but just
given the posts and the lack of clarity about its purpose. I can
always turn them on later.
I basically haven't done anything with the install, it's on a different
partition, so I can't say whether or not things work with the daemons
off, like they used to, or if there is some other problem.
We don't have to adapt it, unless something else has had to be
adjusted to compensate. I don't use a GUI that much, and the introduction
seems to be for the GUI-users. One thing I did catch from the quick
glance is that some later version of KDE will depend on it.
Michael
Robby Workman
Sorry for the long delay on this -- I've had it marked for reply now
for quite some time :/
On 2007-08-03, Sylvain Robitaille <s...@alcor.concordia.ca> wrote:
>
> I'm coming into this discussion fairly late (still catching up; you guys
> were busy while I was on vacation!), but (and perhaps it's just me) I
> was under the impression that HAL and DBUS and the rest of these things
> were supposed to make it *easier* to use removable devices. It looks to
> me (though I've not yet seen Slackware-12.0) as though it has been made
> more complicated.
>
> They (the kernel and "rest of the system" developpers) had something
> that worked just fine: add a line to fstab with appropriate options and
> ordinary users would be able to mount removable disks. Now they've gone
> and broken that so the kernel can mount the disks for you???
Nothing is broken in that regard. If you prefer the old behavior, it
still works exactly like it used to work; you don't even have to disable
HAL, contrary to what a lot of whiners have posted in various places.
In fact, you can get the best of both worlds if you want. You can add
lines to fstab with appropriate options and ordinary users can mount
removable disks -- either via HAL/DBUS or the "old" way. It all hinges
on "appropriate options" - it seems that many people "forgot" that
the default option of "owner" on /dev/cdrom does *NOT* allow normal
users to mount it, so this happens:
1. Uncomment /dev/cdrom line in /etc/fstab
2. Try to mount it from command line - permission denied
3. Try to mount it via DBUS/HAL - permission denied
4. Whine
5. Blame HAL/DBUS for all that is wrong in the world
6. Whine
Hope that helps :-)
RW
Sylvain Robitaille
> Nothing is broken in that regard. If you prefer the old behavior, it
> still works exactly like it used to work; you don't even have to
> disable HAL, ...
Yes, I've been finding that, having finally installed Slackware-12.0 on
a couple of laptops. I'm still working on getting these "fully
configured" but they're certainly in a usable state, and work quite well
(one is low on disk space for some things I want to do, but that's not
Slackware's fault).
> In fact, you can get the best of both worlds if you want. You can add
> lines to fstab with appropriate options and ordinary users can mount
> removable disks -- either via HAL/DBUS or the "old" way. ...
Yes, I see. In my case, at this point, I've opted for a slightly
different approach than any that I've seen discussed so far: I modified
/etc/dbus-1/system.d/hal.conf as follows to permit any human users to be
able to mount and unmount pluggable devices (and removable disks) via
HAL/DBUS, so far without any difficulty:
--- /etc/dbus-1/system.d/hal.conf.original ...
+++ /etc/dbus-1/system.d/hal.conf ...
@@ -66,8 +66,8 @@
<allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
</policy>
- <!-- Allow members of the 'plugdev' group to mount volumes -->
- <policy group="plugdev">
+ <!-- Allow members of the 'users' group to mount volumes -->
+ <policy group="users">
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy>
Basically my intention was to permit mounting of devices without needing
to always remember to add new users to the "plugdev" group: all human
users (and only the human users) on my systems are in the "users" group
by default. The group file is cleaner, and in the long run this
achieves the result with the least amount of work. Granted, I feel it's
still too soon to know whether I've broken anything by this, but I've
tested with two different types of USB storage devices (one a flash
"disk" and the other a portable hard-drive) and some CDs without any
trouble. In fact, I find it works quite well.
My fstab on this system has no mention of any of the removable devices.
I'd be interested in knowing if anyone is aware of any caveats I should
consider regarding this approach, of course ...
Robby Workman
Nothing at all wrong with this approach. In fact, this is exactly how
I configured HAL in the first build that went on SlackBuilds.org, and
I *think* there is/was a note in the README about editing the hal.conf
file this way if that behavior is desired. In short, that's a perfectly
valid configuration, and for some purposes (including yours), it's by far
the easiest way to do it.
RW