|
Home > Archive > Linux/Unix > November 2002 > Advice needed - im new to Linux
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Advice needed - im new to Linux
|
|
| Margus 2002-10-21, 7:46 pm |
| Well finally I installed Linux Redhat 7.3 to my pc (this free version).
I chose to have GNOME desktop environment and TEXT startup (like MS-DOS command prompt)
Well, now I have no idea what to do next -
I would like to learn how to use this Linux/UNIX command-line environment and also how to be able to go to graphical mode of Linux.
Since Linux/Unix skills are neede in working environments I would probably like to go for some certification,
So could someone please advise me which books (free ones preferred) to get and about which certification to think about
(I think that there are several different Linux certifications + Unix certs)
Im grateful to anyone who can help to get started with Linux! | |
|
|
| tabath 2002-10-22, 8:08 am |
| See www.basiclinux.net , its mentioned somewhere else on this forum by linux guy | |
| bass2k1 2002-10-22, 8:37 am |
| This is not really a "must-have", but I would recommend you get your linux box on a network if it isn't already. Personally, I think the real power of Linux/UNIX is in it's networking capabilities.
Just my 2 cents
sebastiaan.rothman@bhpbilliton.com | |
| Margus 2002-10-22, 11:58 am |
| Thnx Guys,
But how do I get from Linux-commandline to Graphical Linux Redhat? | |
| Mr. Linux Guy 2002-10-22, 1:01 pm |
| quote:
Originally posted by Margus
Thnx Guys,
But how do I get from Linux-commandline to Graphical Linux Redhat?
startx | |
| bass2k1 2002-10-23, 12:35 am |
| you could also use gdm , but I see that you haven't got any other desktop environments installed, so startx should work better. | |
| Margus 2002-10-23, 1:33 am |
| quote:
Originally posted by bass2k1
you could also use gdm , but I see that you haven't got any other desktop environments installed, so startx should work better.
Well, startx doesnt seem to work -->
I boot Linux up with boot-up floppy which I made during installation.
I have no idea how to put Linux to boot.ini | |
| Mr. Linux Guy 2002-10-23, 7:17 am |
| When you type 'startx' what error messages do you get? | |
| Margus 2002-10-23, 11:26 am |
| quote:
Originally posted by Mr. Linux Guy
When you type 'startx' what error messages do you get?
It just says that no such command (believe it or not)
typing- help startx
doesnt bring anything up either... | |
| Mr. Linux Guy 2002-10-23, 1:25 pm |
| Are you logged in as root? The 'startx' command is usually stored in /usr/X11R6/bin. If that directory is not in your path, the shell will not be able to find the command. See if that is the case. If you really do not have that command installed, X may have not installed correctly. | |
| Margus 2002-11-01, 6:59 pm |
| quote:
Originally posted by Mr. Linux Guy
Are you logged in as root?
Of course I didnt log in as root --> so now I logged in as a root and "startx" worked.
However, I tried login in as a user and startx still worked... Maybe I had trouble spelling startx rigth?!?
Well, I have still couple of Qs:
1) How do I connect to internet from Linux --> I have road-runner hi-speed cable
2) I seem to have no sound, How do i configure that
3) Is it possible from RHL 7.3 (ext3 filesystem) to see NTFS partitions and files on those partitions?
thnx for helping! | |
| Mr. Linux Guy 2002-11-01, 7:54 pm |
| 1) There are several steps. Usually you add your domain and nameservers in your /etc/resolv.conf file. Make sure your interface is configured correctly. There should be some graphical utitlties that should make this easier for you if you have KDE or GNOME up and running.
2) sndconfig might be an idea. 
3) You better beleive it! You usually need to find out what partition your NTFS filesystem is lacted on and then mount it to a suitable mount point then browse away. | |
| Margus 2002-11-01, 8:01 pm |
| Im sorry but Im a real beginner in Linux,
and those things I need to have configured b4 I can start playing around on my own (with the help of books)
quote:
Originally posted by Mr. Linux Guy
1) There are several steps. Usually you add your domain and nameservers in your /etc/resolv.conf file. Make sure your interface is configured correctly. There should be some graphical utitlties that should make this easier for you if you have KDE or GNOME up and running.
How do I figure out what are my DOMAIN and nameservers? (I have only a vague idea what they mean), What You mean interface configured correctly?
quote:
2) sndconfig might be an idea.
CommandPrompt --. Look for sndconfig ?
quote:
3) You better beleive it! You usually need to find out what partition your NTFS filesystem is lacted on and then mount it to a suitable mount point then browse away.
How do I figure out that?
And how to do tha mounting? | |
| Mr. Linux Guy 2002-11-01, 8:04 pm |
| You may want to do a mount listing by looking at your /etc/fstab file or by using
$ /sbin/fdisk -L
Then you mount the NTFS partition by using the mount command:
mount /dev/hdb2 /mnt/windoze
Then you can cd to the Windoze partition and have at it. | |
| Mr. Linux Guy 2002-11-01, 8:10 pm |
| quote:
Originally posted by Margus
How do I figure out what are my DOMAIN and nameservers? (I have only a vague idea what they mean), What You mean interface configured correctly?
Cntact your ISP. You name servers are the servees that are running DNS/BIND and resolve your IP addresses to FQDNs.
Interface . . . NIC card. You can set your IP address , netmask and so on by the "ifconfig" command. Use man pages for particulars.
The file usually looks like this:
search foo.net
domain foo.net
nameserver 192.123.45.009
nameserver 112.34.56.9
nameserver 12.34.56.61
quote:
Originally posted by Margus
CommandPrompt --. Look for sndconfig ?
$ find / -name 'sndconfig' 2>/dev/null | |
| Margus 2002-11-02, 9:05 am |
| quote:
Originally posted by Mr. Linux Guy
Cntact your ISP. You name servers are the servees that are running DNS/BIND and resolve your IP addresses to FQDNs.
Well, my ISP is roadrunner and I have hispeed cable modem (its 1 home pc) which connects through USB 1.1 .
I read from somewhere that for cable USB modem You need to install some extra drivers or something?
When I called to ISP (roadrunner) and asked how to set up internet in Linux - the (black)b*tch who answered didnt have any idea what Linux was (or I suspect she didnt know even what OS is) but somehow she figured out that roadrunner doesnt have any support for other OS-s than Windows ,
Do You think that I migth still be able to connect to internet from Linux?
And HOW???
(I need something which explains it deeply... Maybe there is something on the web?) | |
| Mr. Linux Guy 2002-11-02, 2:56 pm |
| You will need:
1) The IP address of your ISP's name servers.
2) Your ISP's dial-up phone number or IP address.
3) Your username and password.
In DOS, the serial ports are mapped to COM1 through COM4. In Linux, they are designated a little bit differently:
DOS or Windows Linux Linux (Old)
COM1 /dev/ttyS0 /dev/cua0
COM2 /dev/ttyS1 /dev/cua2
COM3 /dev/ttyS2 /dev/cua2
COM4 /dev/ttyS3 /dev/cua3
Avoid using the cuax designations for your serial devices -- they are generally referred to as "callout" devices and are obsolete as of Linux kernel version 2.2. The ttySx naming convention strikes Windows users as very odd usually, but the logic behind it is simple: a tty can refer to almost any device (usually a serial device or a terminal), the "S" stands for "serial" and in Linux, you start numbering things at zero usually, and not at one.
The resolv.conf File
--------------------
The resolv.conf file is located in the /etc directory. It contains the information necessary for your machine to locate your ISP's domain name servers, which convert the IP addresses to sensible names that you can use to locate various web sites. Your resolv.conf file should be in this format:
domain {domain}
search {name of your ISP}
nameserver {IP address of your ISP nameserver}
I use earthlink, so my resolv.conf file looks like this:
domain earthlink.net
search earthlink.net
nameserver 207.217.77.82
nameserver 207.217.120.83
nameserver 207.217.126.81
If it doesn't work, review /var/log/messages for details concerning the attempt. Use these details to troubleshoot the interface or to get help online.
The /etc/HOSTNAME File
-----------------------
Make sure that you have the name of your machine in this file. That's all you need. Mine looks like:
gsibbery
The /etc/ppp/options File
----------------------------
The options file is used to specify certain options (big surprise there!) for your method of connexion. Mine looks like this:
###
# /etc/ppp/options - options for pppd
#
#!/bin/sh
/dev/ttyS0
115200
connect /etc/ppp/earthlink-connect
user ELN/gsibbery
lock
crtscts
defaultroute
noipdefault
The first line is the serial port that your modem is on. My modem is on serial port ttyS0 (or COM1 in Windows). By the way, make sure you only have one device specified as your modem. Some people get confused and try to use both /dev/ttyS0 and /dev/modem as the device file for their modem. This will produce an error. It would be OK, however, to make /dev/modem a symbolic link (shortcut) to refer to your modem. The "connect" line specifies the name and location of the chat script that I will describe below. You may have to figure which one yours is on by trial and error, or with t a tool like kermit or minicom. The next line specifies the speed at which the transmissions are to take place . . . I have a Rockwell 56K modem and the standard speed for a 56K is 115200. The "lock" option writes out a lock file to the /var/lock directory that ensures that no one else can use the modem while I am using it. Linux does this with a number of devices; if you use a device like a modem once and then find that when you try to dial out a second time, you get an error message, chances are that your modem lock file is not being deleted when you relinquish control of the device. This may seem a bit uncalled for, but remember, that Linux is a multi-user system -- only one person can have exclusive access to some devices at a time. My ISP uses a version of PAP and so I need the line "user {username}". If your ISP uses a different authentication protocol, you may not need this line. The line "crtscts" means that the modem is using hardware flow control (this is almost always true under Linux). The "defaultroute" option adds a default route to your local routing table using the remote IP address as the gateway. The "noipdefault" line is used because I connect using a modem and not a cable, and my machine does not have one fixed IP address, but is assigned one from a pool of available IP addresses each time I dial in to Earthlink. If you have problems connecting, then place "debug" at the end of this file and it will write out error messages to the /var/log/ppp log and if you read over it, you will get some idea of what is going wrong. Once you've found the problem, however, remove the "debug" line from this file or it will keep writing out messages to your log file and it will get larger and larger, taking up more space without performing any useful function. (By the way, you are generally best off by using as few of these "options" as is necessary to get your PPP connexion to work . . . if you don't need it, don't use it!)
The Chat Script File
-----------------------
The chat script is the file that actually does the handshaking with your ISP. Unfortunately, it israther difficult to say exactly what information you need in this file as the details depend somewhat on your ISP. This script can have a variety of names, but is located in the /etc/ppp directory. The name of this chat script will need to be placed in your options file after the "connect" command. I use Earthlink as my ISP, so I call my chat script earthlink-connect, but I could have chosen any name I wanted to as long as I specified it in the options file. Your ISP may be of some help in telling you what their authentication daemon expects to see in this file -- you may want to ask them whether their server requires the use of a script with certain specific expect/send pairs (what you send must be what the authenticating server expects to receive -- otherwise the server won't understand the information you are sending to it) -- if so, ask them to specify exactly what they are, so that you can configure your script correctly. Again, do not be surprised if you are given some incorrect information -- this sometimes requires a good bit of trial and error in order to figure out exactly what the server expects. by the way, this was the most annoying aspect of the whole operation to me, but once you figure out the correct options to be used, you'll find that it was rather simple all along. These expect/send pairs represent command responses that must be passed by the script in order to turn on the PPP server at the ISP but it usually looks something like this:
#!/bin/sh
# earthlink-connect: a script for dialing into Earthlink
exec /usr/sbin/chat -v
TIMEOUT 120
ABORT BUSY
ABORT 'NO CARRIER'
'' ATZ
OK ATDT344-0514
CONNECT ''
ogin: ELN/gsibbery
ssword: topsecret
This probably looks a little mysterious, so let me try to explain it a little. The crunches (#) signify that the line is a comment. The "exec /usr/sbin/chat -v" line means that the program called chat, located in /usr/sbin will be executed (this is necessary for connexion to take place). The -v option stands for verbose -- this specifies that any output in the logs will be more easily readable by humans -- extremely helpful when reading trying to troubleshoot the connexion by reading the message logs. The next few lines deal with the modem. "TIMEOUT" is the time (in seconds) before the dial-up attempt is aborted (OK, I'll admit that two minutes is a bit excessive, but if you have problems, you may want to increase the number . . . the default is usually like 30 seconds or something -- usually, but not always enough). The next two lines tell the chat program to "abort" the attempted dial-up if the phone line is busy or if there is no dial tone. The next line resets the modem to the factory defaults. The next line actually dials the ISP phone number (keep in mind that this number can change with little warning). If this line doesn't work, you may want to check your ISP's dial-up number, or if you have a pulse rather than a tone telephone line, replace the "ATDT" with "ATPT". I don't think the hyphen separating the two sections of the number is necessary . . . remember to include the area code if you are dialing long-distance. The next line is
the instruction to actually complete the connexion, and the next two lines are my login and password. With Earthlink, you need to prefix ELN/ to your username -- this is just one of the peculiarities of dealing with that ISP; this is because the Earthlink server that I dial into is an Windows NT server and it requires that requires that you put the domain name before your username and Earthlink's domain name happens to be "ELN". Others may not require this, or may expect something different, so try to find out what your ISP expects. The reason the initial letter is left off of "login" and "password" is to allow for the fact that your ISP may use upper-case or lower-case initial letters for these words. By truncating the first letter, you avoid this difficulty. Again, there may be some difficulty here, as your ISP may expect "Name" or "userid" instead of "login". If you try a number of these and nothing works, ask them and find out. mentioning "AOL" in your conversation with a rep often works wonders, by the way.
If you try to connect, but are unsuccessful, add the "debug" line at the end of yout /etc/ppp/options file like I mentioned above, then check your your /var/log/ppp and /var/log/messages files. If you see something like "auth pap" or "auth chap", then you need to use those authentication protocols. CHAP and PAP are "authentication protocols" which determine that you are really the person who should be using your account. Your pap-secrets and chap-secrets files are located in the /etc/ppp directory and should look something like this (with the appropriate username and password, of course):
#!/bin/sh
# /etc/pap-secrets
#username password
ELN/gsibbery topsecret
I think I should mention that there are many versions of each of these protocols and this might not work for each and every one, and of course some ISP's may require you to log on using more than one of these authentication schemes, so if none of this works, ask them.
The ppp-on File
------------------
One last file that you have to add is your ppp-on file, which will be located in your /usr/sbin or / directory. This is what actually turns on PPP. I couldn't start my PPP services without this file, and as it turned out, this was my main problem in getting connected. The same rules apply as before, but you need to know the subnet mask of your ISP (most are class "C" masks nowadays; that is,
255.255.255.0).
TELEPHONE=344-0514
ACCOUNT=ELN/gsibbery
PASSWORD=topsecret
LOCAL_IP=
REMOTE_IP=0.0.0.0
NETMASK=255.255.255.0
That should get you online.
Lemme know if this doesn't work.
The pgone sypport you get for mosr ISPs are idiots, don't listen to what they say. Might want to email tech support, there are usually Linux dudes at most ISPs that can give you some particular instructions as to how to get set up. | |
| Margus 2002-11-02, 3:27 pm |
| quote:
Originally posted by Mr. Linux Guy
The pgone sypport you get for mosr ISPs are idiots, don't listen to what they say. Might want to email tech support, there are usually Linux dudes at most ISPs that can give you some particular instructions as to how to get set up.
You are absolutely rigth - there's no point CALLING tech-help, (I wonder why they hire idiots to answer the phones) but the online help was a little better -->
They at least gave me couple of links about cablemodems and Linux:
http://usmcug.usm.maine.edu/~kpesce/rr/
http://www.cablemodeminfo.com/linbasics.x.html-ssi | |
| Mr. Linux Guy 2002-11-02, 5:42 pm |
| quote:
Originally posted by Mr. Linux Guy
The pgone sypport . . .
Yeesh, must have not had my caffeine fix when I wrote that! Phone support at ISPs I have found in *most* but not all cases, to be useless. The problem is usually that they put drones on the phones who are not techies, but just people with nice voices. Most ISPs do have some knowledgeable people, but the trick is to get to them. I have found that making on online help request while being as specific as possible usually works quite well, since if it looks Greek to someone they will usually get a tier 2 or 3 support guy or the local geek to deal with it. Most ISPs should support UNIX and Linux, although don't expect the phone drones to know it, and most of the work is done on *your* end. But it is pretty simple, once you know what to do. AOL is out since they use those bogus proprietary protocols, but most others should be OK. Just demand that you talk to someone who knows more than how to point and click and you will get your necessary info. Getting a few numbers really should NOT be this much of a pain, but a lot of these "user-friendly" outfits make things harder for those with a little technical know-how. | |
| redhat1 2002-11-04, 6:49 pm |
| lets say:
after booting the machine up and askin for login type a username and password
after login ing
do this
startX
" the X is capital"
and boom | |
| Margus 2002-11-04, 6:52 pm |
| quote:
Originally posted by redhat1
lets say:
after booting the machine up and askin for login type a username and password
after login ing
do this
startX
" the X is capital"
and boom
thnx, aga mulle tundub et Linux t88tab nigu ise tahab - kord t88tab nigu ilma ime aga teinekord j2lle nussib ajusid iga kylje pealt
MS is still the ruler (though not the perfect one) | |
|
|
|
|
|