SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Then leave the permission rights alone... even though it says you can exicute an mp3.. the mp3 contains no header or any actul exicutible data.. so it's perfectly safe... on the other hand try copying 1 mp3 to your home folder and see if it has the same permissions if it doesn't then something is wrong with your install.. I would suggust a reinstall because who knows what else is also exicutible.
I would suggust a reinstall because who knows what else is also exicutible.
Don't be expeditive, it is normal behaviour in some case, for example file permission for photos from my numeric canon are all 755, and 755 too for files from macintosh data cds, I won't reinstall slackware for that !
Depending on how you burned the CD (specifically how you created the ISO), that's perfectly normal. Check out the following from the mkisofs man page:
Code:
-r This is like the -R option, but file ownership and
modes are set to more useful values. The uid and
gid are set to zero, because they are usually only
useful on the author's system, and not useful to
the client. All the file read bits are set true,
so that files and directories are globally readable
on the client. If any execute bit is set for a
file, set all of the execute bits, so that executa-
bles are globally executable on the client. If any
search bit is set for a directory, set all of the
search bits, so that directories are globally
searchable on the client. All write bits are
cleared, because the CD-Rom will be mounted read-
only in any case. If any of the special mode bits
are set, clear them, because file locks are not
useful on a read-only file system, and set-id bits
are not desirable for uid 0 or gid 0. When used on
Win32, the execute bit is set on all files. This is
a result of the lack of file permissions on Win32
and the Cygwin POSIX emulation layer. See also
-uid -gid, -dir-mode, -file-mode and -new-dir-mode.
The relevant part here is the text which I emphasized.
Since CDs are usually intended to be platform independent, they have to be kept simple enough for windows systems to understand them.
I was wodering because i have rox-filer installed in fluxbox but i found the option that ignore's the executable bit for known file types. Im a noob lol.
You can always do TAB + ! to open little field in the bottom of the window and play with command instead of clickin', but for preview thundbail...it is out
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.