Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
So now I have my HTML files, and my mandrake server partition with all of the proper software, running KDE (on the good computer.) I have a domain name: www.crdp.tk my IP is 192.168.1.25, and the GA is 192.168.1.1
This may sound incredibly stupid, but how would I get the HTML files to be served through the domain when I'm running that partition?
Your www.crdp.tk URL brings up a page about the Columbia River Delta Project, plus a pop-up. Are you sure that this is your domain?
The 192.168.x.x series of addresses are strictly local to your LAN and won't go through the routers on the Internet. Depending on how you're connecting to the outside world, you should have another IP address that's your external one.
To get your web server available to the outside world, you need to be sure that the httpd service is running and that you have TCP port 80, as a minimum, open and listening. At the command line or in a terminal window, use "service httpd status" to determine whether it's running, and "service httpd start" to launch it. To find out the status of ports, use "netstat" and look for TCP 80.
NFS is Network Filesystem - NFS is a more-or-less UNIX centric way of sharing files between computers. All major UNIX distributions can share directories to NFS and mount shares from NFS. Samba - SMB protocol - is the same, but Windows -to- UNIX based. Although Linux machines can mount shares between eachother using Samba.
SSH is a remote "terminal" interface. it allows you to access to command line shell functions. SSH functions the same way as "telnet", except it encrypts all of the data between the host and client - thus is considered more secure.
I think you probably need SAMBA to share files and maps and printers and all other stuff between Linux and Windows.
For your web you need a webserver (Apache - MySQL)
and you have to place you webpages in /var/www
For FTP i recommend proftpd
for remote control: SSH
If you have never installed a Linux distro I recommend you to start with KNOPPIX because it works from the CD. It's easy and you can't do anything wrong, once you reboot, everything is normal again. And it's a good distro to get familiar with Linux and it's environment. You can learn easily the commands and other stuff
Then you proceed to a distro that needs to be install on hard drive. E.g. Red Hat or Mandrake (or perhaps SuSe) because these have the ease of a nice and easy GUI for installing the distro.
Thanks for the information, guys I already have mandrake with all of the necessary server software installed.
Apparently my ISP does not block any ports.
On the topic of ports, I'm not sure, but I *think* 80 is working. It says that apache is up and running, and typing in netstat brings up a whole bunch of threes and two's - and numbers in the thousands. No 80 is listed (I assume I could forward this port on my router?)
yup - www.crdp.tk is my 'domain' name. Currently it's pointing to my geocities site since the webserver isn't running yet.
And I found out my ip, Perhaps it isn't safe to post on here, but it starts wiith 66.222.XXX.XXX.
So what would I type into another computer to access the index.html inside /var/www?
I think Its getting close to working
Also, it's funny because the book I read recommended wuftp over *everything* else. But the linux community seems to prefer pro-ftp.
Last edited by flamesrock; 10-16-2003 at 07:44 PM.
Originally posted by flamesrock And I found out my ip, Perhaps it isn't safe to post on here, but it starts wiith 66.222.XXX.XXX.
So what would I type into another computer to access the index.html inside /var/www?
Just to verify things from another location, try doing http://66.222.XXX.XXX:80/ (where the XXX's are replaced by the corresponding numbers of your IP) and see if you get anything. This bypasses the entire question of the domain name.
If you're not on a static IP (one that never changes) you may need to use a DNS-forwarding service such as dns2go.com or one of the others. If you are on a static IP, have your domain pointed to it instead of to your Geocities page, to use it.
As for the numbers you see on a netstat report, those at the left edge of each entry are PID numbers, process ID values. Try "netstat -n" and look for "0.0.0.0:80" or "*:80" in the address columns. Without the "-n" netstat translates the port numbers to service names...
I don't have an answer, since I use Linux to do my routing rather than a separate box. I would expect using your IP address from another machine (not on your LAN) to go through the router and reach the Apache server, but you may need to configure the router to let TCP ports 80-83 and 443 through. Hopefully someone who's using a Linksys will jump in with the solution!
have you tried logging on to the router page using port 88 instead of 80?
on my router, when i enable port forwarding at port 80, the settings server (or whatever its called) changes the port to 88 as default if im correct.
NFS like (Network File System like GAV said) is used to mount file systems over a network.
Explaination: If you have a Linux box in your living room and one in your bedroom, you could run NFS server on the Living room box and EXPORT the /home directory and allow it to be MOUNTED by the box in the bedroom (IP based access stuff).
This way, when you boot your bedroom box, it goes out and connects to the living room box and MOUNTS he /home directory and treats it as if the /home is actually on the Bedroom box itself. This is very useful if you have a lab full of linux boxes and dont want to have to give every machine a home directory for every user that has to log in. You can centralize the home directory in 1 file server and use NFS to mount it so that the user has his/her files no matter which computer he/she logs into (neat stuff). You can use NFS and mount stuff as needed but you'll still have to add users (NIS takes care of that but that's nother discussion).
SSH (Secure shell) is for logging into a machine securely. You can manipulate the box as much as your permissions allow remotely (via the command line interface).
things like intsalling/removing software, downloading files, ftping...anything. you can even reboot the machine from london if the compuer is in Canada. I've downloaded, configed and compiled kernels remotely then rebooted the machine.
note: if u reboot the machine or "kill" sshd, you loose your connection to the box, compiling a kernel remotely then rebooting and praying that it works is not a good idea, i did it becaue the box was down the hall and i could go fix it if it didnt work.
hope that explains the difference between the 2 a little more clearly. if i left something out, anyone feel free to correct me or add on.
a note on Samba: Samba is more-or-less for sharing files with Windows machines. There is more to Samba than just that but for starting out, that's good enough for now. Think of Samba as a way to see your Linux box in "Network Neighborhood" on your win2k box. (again, it does more but that's the more common use it seems for normal home users).
Last edited by Robert0380; 10-22-2003 at 01:02 AM.