Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Now before I get into my first question, let me clarify that I have done some research on this. I've found all the rc.6, etc. startup files as well as the two places to launch the SAMBA daemons... I'm just not sure which runs first or where I need to put these commands.
Basically, every time my computer starts up, I want it to do the following:
ifconfig eth0 22.214.171.124
Where should I set these SAMBA commands and where should I put the ifconfig so that the ifconfig runs first? If nmbd gets run before ifconfig, it won't start properly, and I'm not sure the startup order of things.
Second, I thought I'd just throw in a quick question about kernel modules. I assume vfat is already built into the default Slack 9 kernel because I am able to access my windows partition just fine (even though the /etc/rc.d/rc.modules #/sbin/modprobe vfat line is still commented out). However, I am trying to mount a smbfs... on my connected Windows computer to access files there, and it tells me I don't have smbfs support in my kernel. I tried uncommenting the line in rc.modules, but it can't find it. modprobe and insmod both tell me it can't be found. I have the Slack 9 kernel source installed in /usr/src/linux with all that stuff in there, but its not finding the smbfs modules in there. Is there any way I can compile this module or something and make it so modprobe will find it?
on slack there is /etc/rc.d/rc.local this is one good place to add things to your startup. commands in this file are executed in line order. im pretty sure that rc.local is the last script run for each runlevel so you can probably leave the ifconfig out since networking will be all setup before rc.local get run.
Ok, so rc.local looks like the place to put that. There are two other files where you can start samba daemons, and I was just wondering if those are a better place to start them (and, if so, if those files get run before or after rc.local).
The reason I need ifconfig to run is that it is not automatically being assigned on startup. ppp and one other interface are assigned, but eth0 isn't. How do I get this to automatically configure itself on startup?
I'm not sure if you understood my second question, since I'm pretty sure it has to do with kernel modules. I type mount -t smbfs etc. to try to mount my remote windows share and I get an error saying smbfs file system is not supported by the kernel.
Well, good ideas, but they didn't work for one reason or another. I tried doing all of the above, and I ended up getting a couple of errors. The /etc/modules.conf line just gave me a bunch of errors that I was using the wrong syntax when I started up. The rc.local lines said that eth0 didn't exist or something along those lines... I think that script gets run too early. I know a place where I can get the samba daemons to start up automatically, but before I do that I need to find a way to get my eth0 to bind to the interface automatically... and there has to be a way to do that without putting an ifconfig in one of the rc files. Is there?
Thank you very much for the rc.inet1 and 2 info. I haven't checked yet but that looks like it is exactly what I am looking for. As far as modules though, I have uncommented the smbfs line in rc.modules, but it still doesn't work. I don't think the module was compiled in the first place, but I still don't completely understand how it all works. Any other suggestions?
I got all that working now, thanks a lot for all your help.
I still am a little confused about the module issue. When I use mount -t smbfs or smbmount or anything like that, I get the error that smbfs is not compiled into my kernel. However, I can use smbclient to successfully browse files on my other computer. Its not a huge issue now since I don't need to do much on the other computer from here, but I'd eventually like to be able to print to its shared printer so I'd like all the smbfs tools to work properly.