hi..
I'm using slack 12...
I've 2 problems...

1)

whenever i insert my pen drive in USB it automatically gets detected.. but then i cant access the contents...
i get the following message...

i intended to modify the file /etc/dbus-1/system.d/hal.conf
but i couldn't understand what should i do...
that file seems greek n latin to me...

the following is the file....


problem 2)

i cant write into my ntfs partitions(mine is a dual boot with windowsXP)

while booting i see that it is read only file system..

i cannot change the permissions through chmod ...it gives a message read only.... why??

then i go to /etc/fstab
and change the

filesytem(the ntfs partitions) from "ro" to "defaults"

and the numbers 1 0 to 1 1

... then i reboot..
i'm able to change the permissions of the partions(directories) through chmod... even when i right click i get the option of "paste file"..
but if i try to paste

i get "ACCESS denied .. couldn't write to /c/anil.c"

Please read:
http://www.linuxquestions.org/questi...d-this-566862/

Is the user account that you are trying to access the pen drive
in the groups plugdev and messagebus?
if not run kuser from a root prompt and add your users into that
group.. Hope this helps.

easiest way is to add this line to your FSTAB:
i believe that the code is right. if not please correct me.

The code is correct (except the 'auto' mount option is probably not wanted), but it still won't allow the user to mount the device with HAL/DBUS unless he's in the appropriate groups. That's why he was properly pointed to the sticky thread on HAL - all of the relevant information (including making an fstab line if desired) is in there.

I can't confirm this, but I've seen numerous reports that kuser didn't always "do the right thing" when adding/editing users/groups.
I prefer to do this manually anyway -- vipw(8) and vigr(8) are quite sufficient for my purposes.

Oh, and users should NOT be in the 'messagebus' group - it serves no purpose at all.

The code can be right all it wants. This is still the wrong solution to the problem. If the user will read the post referenced in the first response he got then his problem would go away.

Everything that has been said since has been steps in the wrong direction.

a1ora0,

Welcome to LQ!

I'll save you a lot of time and confusion and make it very plain.

Problem #1:

No need to edit "/etc/dbus-1/system.d/hal.conf" or "/etc/fstab" at all.

Slackware-12.0 will automount your devices if you put your user into the appropriate groups. Edit the file /etc/group as root with whichever editor you're most comfortable using. There is no need to change /etc/fstab -- just add your user to the plugdev group and it will mount automatically. If you don't have a preference, use Konsole and login as root. Then open it with vi by issuing "vigr" (which is the standard method of editing /etc/group). Then press the I key, which means insert. Move your cursor, using the arrow keys, to this line:
and type your normal username after that last : (colon). Then to save and exit the file, press the Esc key, then : (colon) and wq (which means write, quit), then Enter. After the vi editor closes and it returns to a prompt, issue "/etc/rc.d/rc.messagebus reload" and it will output "Reloading system message bus configuration..." and return you to a prompt. Then stick your flash device in and KDE (if you're using it) should give you a popup box and allow you to open a window to view it's files.

NB: You should also add yourself to the wheel, audio, video and cdrom groups while you have /etc/group open. They will become important later on.

Problem #2:

Linux cannot reliably write to NTFS file systems. There is a project which some say works okay. I forget it's name. Writing to FAT32 (or before) file systems is reliable, and what you can use with a default Slackware install. If you have some free space on that drive, or space that can be repartitioned, it would be preferable to make a FAT32 partition to share data between the OSes.

Your line in /etc/fstab should look something like this:
where /dev/sda1 represents your Windows OS, and /WinXP represents the mount point name you gave it when you installed Slackware. You want to leave it ro (read-only) and leave it as 1 0. In a terminal (Konsole) issue and read "/etc/fstab" and "man mount". Every command in a Linux system (properly installed) will have a manual (man) page in the system for it.

Bruce Hill,

I really appreciate your reply.
I know i should do a lot of reading.But then where to start it from?
please help me here.


and the solution You provided didnot work..

i hope u expected me to write this

and then save the /etc/group file....
after that i did run the command "/etc/rc.d/rc.messagebus reload"
I even did get the reply u told , from the shell.
But the same message as i've quoted in my first message appeared!!!
No difference.


also would like to add another query.
i can read and execute the ntfs partitions as root but not otherwise.
how can i make normal users access those files?

Don't put the : after your user name.

For the NTFS partition:
should give you read-only access for all users on your system. If you really want to write to it, perhaps you can figure out past there how to make it read/write. Please issue and read "/etc/fstab" and "man mount".

NB: Reading is important. If you write to a NTFS filesystem without proper configuration and support, you may damage the data and the Windows operating system.

Thanks for the tip I removed myself from messagebus and everything works fine... I never had a problem with kuser, but I don't do to much group editing.