Linux.com

BT module in Slackware

Link to this post 19 May 11

linustorvalds wrote:

I hope, I almost know who is the 2012 Linux Guru?. any guess mathew ? :-)

and why there is no default permission to execute "/etc/rc.d/rc.bluetooth", even for root ? what reason ?

That looks like a bug.

If you feel up to it, check the Slackware bugtracker and submit a bug report if it's not already there.

Regards

PS: in *nix like permission system execute bit is not for "root" rather than for the owner, group or everybody else ;)

Link to this post 19 May 11

"If you feel up to it, check the Slackware bugtracker and submit a bug report if it's not already there."

ok

" "in *nix like permission system execute bit is not for "root" rather than for the owner, group or everybody else"
ya, its user-group-others.
thanks man :-)

Link to this post 19 May 11

I am hoping that someone else gets ultimate guru this year, we have plenty of very knowledgeable and active people on the site that can easily take that title next year. Rather than focusing on the title, I try more to built an active community on the site with knowledgeable and helpful people. Marc and Eric Layton are my two top hopefuls for the top spot next year.

Sorry, the correct command that you were to run on /etc/rc.d/rc.bluetooth was "/etc/rc.d/rc.bluetooth start", I guess I forgot to type a single word.

The starting permissions of the files in /etc/rc.d were set by you in the initial installation, when it asked what services you want it changed each of the chosen files to executable, so you did not select to use the bluetooth service when you installed. That can be changed at any time in the terminal by tunning pkgtool, which will allow you to change most of the options that were chosen when you installed slackware.

The way the slackware init system works is that, in most cases when a service setup script in /etc/rc.d is set to executable it will be launched by the system when it is booted. You must remember that slackware does not really use any defaults, most things that will effect you are chosen when you install the OS, in this case you skipped through the step about choosing which services to use.

Link to this post 19 May 11

marc wrote:

[b]linustorvalds wrote:[/b]
[quote]I hope, I almost know who is the 2012 Linux Guru?. any guess mathew ? :-)

and why there is no default permission to execute "/etc/rc.d/rc.bluetooth", even for root ? what reason ?

That looks like a bug.

If you feel up to it, check the Slackware bugtracker and submit a bug report if it's not already there.

Regards

PS: in *nix like permission system execute bit is not for "root" rather than for the owner, group or everybody else ;)[/quote]

As explained in my other post, not setting the script as executable by default is a feature, not a bug, the user forgot to choose to enable the Bluetooth service when it was installed. Plus, Slackware does not have a bug-tracker it only has Pat..lol

You will find that the lack of assumptions and the different organization by the development team in Slackware defy what other distros do. These differences are considered strengths by many of their users, but tend to confused people who come from more user-friendly distros

Link to this post 19 May 11

" Rather than focusing on the title, I try more to built an active community on the site with knowledgeable and helpful people."

Great :-)

" Marc and Eric Layton are my two top hopefuls for the top spot next year. "

we are also waiting. I feel like waiting for my school results

" Sorry, the correct command that you were to run on /etc/rc.d/rc.bluetooth was "/etc/rc.d/rc.bluetooth start", I guess I forgot to type a single word. "

No problem. It happens to everyone

"you did not select to use the bluetooth service when you installed"

may be. Next time, I will be more alert during installation.

" slackware does not really use any defaults, most things that will effect you are chosen when you install the OS "

thats why more people are afraid to use this beast. For the same reason, I want to use this lovely OS :-)

thank you matt.

Link to this post 19 May 11

mfillpot wrote:


The starting permissions of the files in /etc/rc.d were set by you in the initial installation, when it asked what services you want it changed each of the chosen files to executable, so you did not select to use the bluetooth service when you installed. That can be changed at any time in the terminal by tunning pkgtool, which will allow you to change most of the options that were chosen when you installed slackware.

I don't think that's usefull. At all.

It could sound correct from a security point of view but... it's not as you could always just


sh /what/ever/script

And you'd still be able to run the script.

Therefore, removing the executable possibility from a script that is there for, well, be executed looks like nonsense to me.

Regards

Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board