Quesions about Slackware Command.
Hi,folks
These days,I just finished the installation of slackware 11.And before this I use Fedora and Centos.When came to the world that make by slackware,I am very excited about its speed.But the its commands drive me crazy. The question is I don't know how to get some commands to let it work.For instance,I used "service vsftpd start" to open the vsftp,but it can't work.And I tried to initialized the rp-pppoe,but "adsl-setup" can't work too,then I know "pppoe-setup" will work in Slackware. So,could you guys can give me some suggestions on how to learn it's commands?:confused: snowball |
The equivalent to Fedora's service commands will be to look at the /etc/rc.d/ directory. In there, you will see the scripts to start samba, apache, nfs, etc. Since Slackware doesn't use init.d, all you have to do is chmod -x to prevent a service from starting or chmod +x to allow it. To start a service on the fly, do /etc/rc.d/rc.(service) start - stop - restart.
I hope this helps. |
You can start services on Slackware (and any Linux distro) by doing something like
Code:
#/etc/init.d/service start Code:
#/etc/init.d/vsftpd start |
Quote:
|
Quote:
|
Thanks,
but if i want to check if a package is installed?what should i do? how you guys learn that? I wanna some methods that i can access the slackware quickly. any good doc about the slackware command ? |
Two problems here.
Firstly, there is no /etc/init.d on Slackware. I'm sure reddaz should know that. Services are in /etc/rc.d as stated. However, the second problem is that there is no /etc/rc.d/rc.vsftpd. To start the ftp service, open /etc/inetd.conf in a text editor, and uncomment the following line: #ftp stream tcp nowait root /usr/bin/tcpd vsftpd Reboot to initialise it. |
All packages are listed in /var/log/packages.
|
Quote:
|
Quote:
|
Quote:
Personally, I couldn't care less what the other distros do, I've tried them all, and I can tell you, this is absolutely and completely irrelevant and meaningless with respect to everything. I chose Slackware because ... Quote:
it is the most, if not one of the most standards compliant distros in existence. And, it just works. And it's set up in a way that makes sense, and is easy to configure (at least for me). Hey, if you don't like it, don't use it. @ snowball0916 Read the Slackbook (link in my sig) |
I think you misinterpreted what I was saying above. It is now a standard in Linux distros that services should be in /etc/init.d. Most distros that have been released over the last few years now follow this convention (but many still keep their old way of managing services as well,), so I thought that the same would apply for newer versions of Slackware. I wasn't implying that Slackware was behind other distros in terms of features just because they are using a non standard way of managing services. And there is nowhere in my posts that would suggest that I don't like Slackware.
Anyway the OP has received help from others who are up to date with Slackware and there is no point in engaging in discussions that deviate from the original question. |
Thanks reddazz ,
You give me a lamp. I will read it first before asking. |
Hi,
Welcome to Slackware! You could look at my sig for some good online reference. |
All times are GMT -5. The time now is 09:07 PM. |