Fernando Meira schreef: > On 6/19/05, Richard Fish <[EMAIL PROTECTED]> wrote: > > >>If so, you either need to set UseFBDev to Off, or build your kernel with >>the radeon frame-buffer driver into the kernel or as a module. > > > > The UseFBDev is commented.. does that means that is Off ? >
Not necessarily, if the internal default for this setting is ON (which I don't know), but in any case, when commented settings revert to their internla default, so in this case it might be better to explicitly set it to "Off". > Anyway, I managed to start KDE. To do that, I created a new user. The > difference was that the HOME of my first user is located in a FAT32 > filesystem, while I placed the new one is at /tmp/ (ReiserFS). Thus, I would > say the problem is with the partition. I also noticed that when creating a > new user, the files from /etc/skel are not copied to the users' home-dir. > Something is wrong with this partition.. i mount it as follows: > > /dev/hda5 /home vfat defaults,umask=000 0 0 > > Both root and users are able to write in that partition, I seems that only > scripts fail... Well, of course they do-- you're using the 'defaults' option, which implies (among other things) 'noexec'-- which means scripts may not be run (no executables may be run) from the partition. You might want to add the 'exec' option *after* the 'defaults' option (so that it overrides the 'noexec' included by 'defaults', if you put 'exec' before defaults, the 'noexec' witll override the exlplicit 'exec', which is not what you want). Also not quite sure what is the usefulness of 'umask=000', since that just says "leave the umask as it is" by default rather than changing it in any way (umask removes permissions from the default settings, which in this case would be something like rw (root), r (root), and r (others), because the default permissions of 777 and 666 have been changed by use of the 'defaults' option). You would probably do better to 1) set the uid= and/or gid= options to give users some ownership rights; 2) change the permissions of the mount point itself to give users some ownership rights; and 3) set an appropriate umask to block rights of others (I was always fond of 007-- all rights for owner <who was me>, all rights for group <which was a custom group to which samba users belonged> and no rights whatsoever for others <I don't know who these 'others' are, but I don't like em ;-) >. You probably want to read 'man mount', but I also wrote a tutorial that discusses managing shared partitions of this nature: http://www.shell-shocked.org/article.php?id=230 (:: Shell-Shocked :: Tutorial: Multiple Linux Distros). Scroll down to "The fast explanation of fstab entries" for a 'how-tolet' on a successful /etc/fstab entry for vfat partitions. HTH, Holly -- gentoo-user@gentoo.org mailing list
