12.0 and HAL - READ THIS!

rworkman · 09-17-2007, 09:00 AM

Quote:

Originally Posted by erickFis

ok people!

I'm poor guy, not so greed as you...

The only thing I need is to be able to read and write
freely is a fat32 partition, as a normal user, not root

My fstab:

dev/hda2 /geral vfat auto,user,rw 1 0

this doesn't work, only root can write this way.

How should fstab look like?

http://slackwiki.org/Windows_Partitions

erickFis · 09-17-2007, 09:38 AM

hey man: it works!

thank u so much!

and what about the other question:
writing to a ntfs harm windows xp?

pappy_mcfae · 09-17-2007, 01:43 PM

Quote:

Originally Posted by erickFis

and what about the other question:
writing to a ntfs harm windows xp?

Well, I can't speak for the long term since I just set this up, but in the space of the time it took to do the set up and to test it, I created directories and folders on both NTFS partitions on one machine, and one on another. I also deleted said directories and files, and moved some directories and files around.

Once this was done, to insure nothing bad had happened, I booted into the Windoze installations (Windoze 2000 and Windoze XP respectively), and the chkdsk utility didn't come up telling me that there was NTFS corruption. The files and directories were visible and deletable under Windoze as well. Therefore, I have to think that there is no more danger in writing to an NTFS partition using FUSE and ntfs-3g set up as I described earlier than there is doing the deed in a native Windoze session.

While researching this, I found only one caveat. At the ntfs-3g web site, there is a warning that states...

Quote:

Make sure that the basic Linux development tools and the full FUSE package is already installed correctly on the computer. Please note, FUSE 2.6.0 or later is required to guarantee full data safety... (emphasis added by Pappy)

Considering this warning comes on their web site, I'd think that the folks at ntfs-3g know what they are saying. Fortunately, at the time of this writing, the current stable version of FUSE is 2.7.0. So far, so good; everything appears to be working normally.

EDIT! Since the time of this writing, I have also installed this set up on my new laptop, which runs Slack-11. Therefore, I can only conclude that it works as well on Slack-11. Cool!

EDIT 2! For those interested, you can activate FUSE support directly by compiling it into your kernel. FUSE support has been a the kernel option since version 2.6.14-rc1. To activate it, use your favorite kernel configuration program, and set the "File systems-->Filesystem in Userspace support" option to "module". Recompile and install your kernel. Also note, you will still have to install FUSE for the library file libfuse, but you will only need to do it once, instead of every time you recompile your kernel.

Blessed be!
Pappy

iiv · 09-19-2007, 01:20 PM

Quote:

Originally Posted by szob

2. Go to this file:

/usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi

and next adjust the code...

Thanks for that. Very disappointed by the fact i have to edit config files in /usr, they all are supposed to be readonly. All config files are to be in /etc. Is it Pat's fault?

rworkman · 09-19-2007, 02:56 PM

Quote:

Originally Posted by iiv

Thanks for that. Very disappointed by the fact i have to edit config files in /usr, they all are supposed to be readonly. All config files are to be in /etc. Is it Pat's fault?

No, it's not Pat's fault. If anyone is at fault, it's the individual who gave that advice.
Place the modified file in /etc/hal/fdi/policy/... -- that location overrides /usr/share/hal/...
The intent is to ship defaults in /usr/share/hal/, and if the sysadmin needs overrides, then use /etc/hal/

rworkman · 09-19-2007, 03:00 PM

Also, I seem to recall somewhere in this thread about partitions in /etc/fstab of type ntfs-3g not mounting automatically if they're supposed to -- this is due to an oversight in /etc/rc.d/rc.M

It appears that at some point in the 10.2 --> 11.0 development cycle, the "mount -a" in there was removed while making other changes. Most people don't notice it, as nfs and smbfs filesystems are mounted in /etc/rc.d/rc.inet2

Anyway, to remedy this, add the following line to /etc/rc.d/rc.M after the call to /etc/rc.d/rc.inet2:

Code:

mount -a -v 2> /dev/null | grep -v "already mounted"

NightSky · 09-21-2007, 01:20 AM

Can you add /home/usr to the /etc/group - so that the particular user has permission only from their home/user directory (ie. Console)? Now I am new to command line configuration and using Xfce and did not install kde. Since I did a full install do I have PyGTK installed? I have read man usrmod but could use a sample of syntax:
# usrmod -a -G power :x:84: tonyChange existing user tony primary group to /etc/group
# usermod -g /etc/group tony --is this correct before I mess up my files? I found this in some FAQ. Thanks for your work rworkman. I

Bruce Hill · 09-21-2007, 06:56 PM

Quote:

Originally Posted by perry

by the way it's the vmlinuz-generic-smp-2.6.21.5-smp under slackware 12 with the latest patches from slackware.com applied.

feel free to enlighten me...

- perry

Okay, here's for your enlightenment: Slackware does not patch kernels it releases with; there have been no patches, nor will there be, to the Slackware-12.0 release's kernels.

H_TeXMeX_H · 10-08-2007, 03:05 AM

I recently got this working, so I'm going to summarize what I did, since some people said they were confused with the original post.

I want to make this a simple as possible so anyone can fix this problem easily.

Steps:

1) Login to root:
Open a terminal, like rxvt or konsole or Terminal, then run the following commands pressing <Enter> after every line. Note that if a line begins with a # then it is a comment and you should not type it but instead take note of what it says.

Code:

su
# type in your root password

you should now be running as root

2) As root run:

Code:

for group in floppy audio video cdrom plugdev; do gpasswd -a $USER $group; done

this will add you to the right groups

3) As root run:

Code:

/etc/rc.d/rc.messagebus reload

to have d-bus recognize changes made to your group status

Everything should work right now.

OPTIONAL) This step is optional and only if you want to specify where things should be mounted.
Edit '/etc/fstab' to for example:

Code:

/dev/cdrom       /mnt/cdrom       auto        noauto,users,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,users     0   0
/dev/sdb         /mnt/zip         auto        noauto,users     0   0

Note that here you are allowing users to mount these devices, you can use 'users' or 'user', and you can also add the 'rw' option, to have it mount the media read-write, but I think the default is mount read-write, that's why you only need to specify 'ro' read-only for the cd-rom drive.

H_TeXMeX_H · 11-13-2007, 02:26 PM

Quote:

Originally Posted by H_TeXMeX_H

1) As root run:

Code:

# NOTE: do NOT run this, it's dangerous, see one post down
useradd -G users,floppy,audio,video,cdrom,plugdev $USER

where $USER is you, here obviously you're adding yourself to these groups. What's neat is that if you just use 'su' to login to root, $USER is actually equal to your user, not root.

I just tried this on my newer machine and it did not work. It said the user already exists, which is true, but it's also true that I'm not trying to add a new user, only to change the groups. To fix it I had to manually edit '/etc/group'. There must be a better way, but if not, this works.

Alien Bob · 11-13-2007, 02:57 PM

Quote:

Originally Posted by H_TeXMeX_H

I just tried this on my newer machine and it did not work. It said the user already exists, which is true, but it's also true that I'm not trying to add a new user, only to change the groups. To fix it I had to manually edit '/etc/group'. There must be a better way, but if not, this works.

That is because the command is wrong (dangerously so!).
The correct and safe set of commands to add your user to these additional groups (if you do not want to edit the /etc/group file manually), is

Code:

gpasswd -a $USER floppy
gpasswd -a $USER audio
gpasswd -a $USER video
gpasswd -a $USER cdrom
gpasswd -a $USER plugdev

Eric

H_TeXMeX_H · 11-13-2007, 03:14 PM

Ok then, thanks. I edited my earlier post.

BiafraRepublic · 12-13-2007, 06:34 PM

Quick little blurb regarding the nVidia drivers

If you are compiling your own kernel and have "Enable Paravirtualization support" built into it or as a module, the nVidia Installer will fail in the module compile (wish I had some output for you, but I'm not at my computer at the moment...)

Used: Comp #2 (neo-thunderball), Slackware 12.0 (CD ISO version), Kernel 2.6.21.5, and nVidia driver installer 100.14.19

Bruce Hill · 12-13-2007, 08:29 PM

If I'm not mistaken, the standard (normal, proper) way to add users to groups is using the command "vigr" as root. When I've done this since Slackware-9.1, there have been none of the problems discussed in these posts. Issue "vigr" and you see something like this:

Code:

root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin,adm
adm::4:root,adm,daemon
tty::5:
disk::6:root,adm
lp::7:lp
mem::8:
kmem::9:
wheel::10:root,mingdao
floppy::11:root
mail::12:mail
news::13:news
uucp::14:uucp
man::15:
audio::17:mingdao
video::18:mingdao
cdrom::19:mingdao
games::20:
slocate::21:
utmp::22:
smmsp::25:smmsp
mysql::27:
rpc::32:
sshd::33:sshd
gdm::42:
shadow::43:
ftp::50:
apache:x:80:
messagebus:x:81:
haldaemon:x:82:
plugdev:x:83:mingdao
power:x:84:
pop::90:pop
scanner::93:
nobody::98:nobody
nogroup::99:
users::100:
console::101:
~
~
~
~
~
~
~
~
~
~
~
Read /etc/group.edit, 40 lines, 575 chars

NB: That file as been edited ... it only requires you to press the "I" or "Insert" key and move your cursor to the position, then type what you want.

If you read "man vigr" you can get the skinny on it.

Toods · 01-12-2008, 02:05 PM

I have read this all this thread and would just like to clarify my understanding of two points:

Quote:

Originally Posted by pappy_mcfae

-- I think it's a good thing to let those people, and everyone else here know that they need to have smp support compiled in, and an initrd.gz file to get everything going as expected under hal.-----
Pappy

1.)That 'smp support' needs to be compiled into a custom kernel even when a uni-processor cpu is used? If this is really so, then HAL would not work with kernel-generic-2.6.21.5 supplied with the distribution would it?

2.)That an 'initrd.gz' file is needed to get HAL working even when using 'ext2' and support for this filesystem type is directly 'built-in' to the kernel?

If these are both true, is there any logical reason why these should be so?.

Bill.