Linux-Setup Digest #364, Volume #21 Sun, 3 Jun 01 18:13:11 EDT
Contents:
Art's Linux for Newbies FAQ (Arthur Sowers)
LILO?? (KCmaniac)
linuxconf command doesn't work! ([EMAIL PROTECTED])
Re: ATA100 Card (Rinaldi J. Montessi)
Urgent: scrwed up glibc library. now nothing worked. ("david yuan")
Top 10 posters for the 7 day period ending 2001-06-03 (Michael Heiming)
Re: CRON won't run my executable (David Efflandt)
Re: linuxconf command doesn't work! (David Hines)
Re: linuxconf command doesn't work! (Bit Twister)
----------------------------------------------------------------------------
From: Arthur Sowers <[EMAIL PROTECTED]>
Subject: Art's Linux for Newbies FAQ
Date: 3 Jun 2001 20:58:45 GMT
Art's Linux For Newbies FAQ (ver 1.0, May, 2001)
by Arthur E. Sowers ([EMAIL PROTECTED])
Written in the public interest
for those who want to get into Linux.
I now have Linux and StarOffice 5.x and printers configured and
internet access on five different boxes and I learned some things the
hard way. Read below to avoid some of the "hard way" I had. If you
are an advanced newbie or above and have a contribution, please
email me or add it in a reply posting. Copyright info: This version of
this document is placed in the public domain and may be reproduced
as long as it is unmodified. If it is modified in any way, the author of
the modifications must indicate his name and designate what is his/her
modification and what is my content. This document is meant to be
a "hint list" rather than a detailed "how-to." It is in no way complete
or extensive. It carries no warranty whatsoever. The information below
represent MY experiences which may differ from others. Lastly I have no
connection, whatsoever in any way, with any sources or book authors
or companies or any other entities I mention below.
Getting Linux and StarOffice installed onto a box can be as easy as
any other commercial software (eg. the Evil Empire [EE]) or it can
crash or have problems at many earlier steps or not be totally
functional after install or display some misbehavior or all three. For
me, I've learned enough to be comfortable with LINUX and have
decided to put LINUX on all of my boxes that will run it instead of
my EE software and operating systems unless there is a good
reason to use them.
Questions:
1. Which LINUX distro to use?
2. Biggest LINUX problems and how to avoid them
2a. Backing out of Locked keyboard, frozen screen.
2b. Operator-induced crashes; avoiding need for re-install.
2c. X-server (you get command line, but can't get graphical desktop).
2d. When "shutdown -h now" does not work.
2e. CD-ROM drive access.
3. What are the best LINUX books to read?
================
Answers:
1. WHICH DISTRO TO USE?
There are two answers to this question. FIRST, visit you local large
bookstore instead of your local computer store and find a thick book
on LINUX that has a CDROM distro on one or more disks included
inside the back cover (You don't have to read all of this book before
you do the install, but it will help a lot if you read it before you get in
too deep). Your local computer store will have a distro on one or more
CDROM disks along with a totally inadequate thin comic book inside a
mostly empty box with about the same price tag on it. At least one
local public library has indicated to me the intention to obtain LINUX
distro disks for loan to library card holders, so check your local
libraries. SECOND, my experience with at least five distros is that,
usually, not all distros install completely and functionally on all boxes.
There may be some dimensional "tolerance" or quality problem, but
one distro installed without glitches on one of my boxes, but crashed
at many points and crashed on multiple attempts to install on another
of my boxes. Only one, Red Hat 5.2, could be installed on all of my
boxes without any problems. This does not mean this is for you.
People have told me some other distro installs on THEIR boxes, but
not RH 5.2. So, the answer is, use the distro that installs without
crashes AND ends up with everything being functional (including the
graphical desktop). Yes, this may mean going out and buying or
acquiring more than one distro.
2. BIGGEST PROBLEMS AND HOW TO AVOID THEM:
2A. LOCKED KEYBOARD, FROZEN SCREEN
My early newbie experience included me getting into things that I did
not know anything about but that I did not know how to get OUT of
those things. You can launch something off the command line and
your cursor stops blinking. What to do? Press CTRL + ALT + F2 (or
any F key up to F6) to get a new login prompt. Log in again, get the
command prompt, then type "ps" (or better, type "ps waux") to get all
processes (or even better, type in "ps waux | less" to get all processes
that you can scroll forward and backward with pageup or pagedown)
and do a "kill -9 <process number>" to stop the process that locked
you up on the first terminal. You should be able to do CTRL + ALT +
F1 to get back to the terminal you left. Try this a few times before you
try anything fancy.
2B. OPERATOR-INDUCED, POWER-FAILURE CRASHES, HOW TO
AVOID THEM.
I've had to reinstall my OS a few times when I would be fooling
around and get into something where either I did not know how to
back out or exit or my screen/keyboard would lock up. What to do?
You turn off the power switch and on the next boot, it hangs
somewhere during bootup with an abstract and useless error message
before even getting to the command prompt. I've found that the default
OS install starts more processes (sometimes called "services") than
are necessary. You don't need all of these if you are just learning
LINUX. Later you can start them up on boot if you want, but in the
meantime shut them off. At the command line, type in "ntsysv" and hit
enter. You'll get a menu and for each daemon, you can hit the "F1"
key and it will tell you what it does and sometimes a sentence whether
you need it or not. By minimizing the number of daemons, your OS
install becomes more "resistant" to an ungraceful shutdown. Some
people have told me they can shut off the power switch on their
LINUX box and it doesn't hurt anything. Generally you should not do
this, but some have. What happens on my boxes is that "fsck" runs
during boot up but not much else. I've even done a power shutoff with
StarOffice running and turned the power back on and all it does is run
"fsck". Again, power off without an OS "shutdown" should not be part
of your habits, but this change may save you from having to re-install
your OS.
2C.X-SERVER CRASHES, CRASHES ON LAUNCH, WHAT TO DO?
I've had a number of installs take place and end up with a boot
into the command line, but my X-server would not launch. Usually,
during install, there would be a glitch during the probe of the monitor-
video card and config file, too, but sometimes I got running X-servers
even with a glitch. You can run, from the command line, XConfigurator
which will give you a terminal-based set of menus that will help get
your X-server config file, XF86Config (which should be in your /etc/X11
directory), set up but this might fail. There is another command line
executable, XF86Setup, that sometimes works when XConfigurator does
not. Both should be in your /usr/X11R6/bin directory. One downside,
I could not find XF86Setup among the collection of files in one very
recent LINUX distro.
I've done things a few times and everything on my desktop
either goes blank (black) or freezes up. When you don't know what to
do, you may be in deep trouble. Once I read the book, and tried it, it
works: CTRL + ALT + Backspace should kill the X-server. Then you
can launch it again. Next time write down what you did if you can
reproduce the X-server crash. On a 486-33 box, with RH 5.2 I can
reproducibly generate a X-server crash by launching a second Xfishtank
screensaver (yes, I get two fishtank screensavers going
simultaneously and virtually nothing on the desktop works any more).
I've had some process running that did not respond to "kill -9
<process number>" and as a last resort, issued a shutdown and
reboot. This has worked for me so far.
2D. "SHUTDOWN -H NOW" DOES NOT WORK?
I had this happen once after doing some things and it is a cause for
worry since its not a good idea to shut off the power switch before
shutting down the OS. If it does not work, type "./shutdown -h now"
and hit enter. This has worked for me.
2E. CDROM access.
For months I could not boot from my HD into my RH 5.2 LINUX and
mount my CD-ROM drive and months of reading NGs did not help.
I could, however, boot into my RH 5.2 from a boot disk and get
my CDROM drive to mount. Finally, one post had the answer. You
may have a HD with a DOS/Windows partition in early cylinders and
have your LINUX native and LINUX swap files on later cylinders. What
may help you is to put still another LINUX partition during install on "/boot".
So, you will have three partitions: "/" for root on a LINUX native
partition, a swap on a swap partition, and a "/boot" partition on a
LINUX native partition. Do this with the Disk Druid. This worked for
me for all boxes and regardless of HD size.
3. BEST BOOKS TO READ
Out of more than a dozen UNIX and LINUX books I own, I can
say that there is no such thing as "LINUX in 24 Hours" or "LINUX
COMPLETE" even though you can find titles like that (I also strongly
advise anyone to read at least one LINUX book before getting on a
newsgroup with questions like "My Z does not work, please help." You
need a lot more detail and it helps to show that you really tried to
figure it out on your own before making a post). Don't overlook
"remainder & over-run" bookstores. Often I've been able to find a
LINUX book, complete with a distro CDROM, which is just two years
old but half price or less. Another thing is that I've had the feeling that
many of the more recent books for the newer distros are more poorly
written, possibly because of the pressure and competition to produce
something newer and better and the authors and programmers don't
have time to match the functionality with the book contents. Do not be
surprised if commands and functionality in any of these books do not
always match what your installation does. Also, I think even the best
books still don't tell you enough. LINUX is very complex and lots of
things are going on that the books don't tell you enough about. It also
helps to spend quite a bit of time looking around your directories and
sub-directories to see what is there and where it is.
The best book that can help you, in my opinion, is actually "The
Complete FreeBSD" 3rd Edition, (I bought my copy at a local Staples
store) by Greg Lehey (by Walnut Creek CDROM, Suite 260, 1547
Palos Verdes Mall, Walnut Creek, CA 94596, or www.cdrom.com).
The book is 800 pages long, but its the first 300 that are really really
useful. I think they have undergone some business reorganization so
some of this may be obsolete. The BSD is very different in many ways
from LINUX, but the command similarities and X-Window setup seems
very similar.
Another book which is surprisingly good but hard to find is "The
Complete Red Hat Linux Installation Guide 5.2" by Red Hat Software,
Inc., (ISBN 1-57595-199-1B) and came with RH 5.2 disks. The book
title, with the word "Complete" in it, is inaccurate (none of the books
are "complete") but never the less is one of the more readable and
coherent books out there.
Another book is "Red Hat Linux" 3rd Edition, by David Pitts and
Bill Ball, (1998, Sams Publishing Company). This is also a thick book
with the RH 5.2 distro in back.
A UNIX book which I found most useful is: "UNIX Complete" by
Peter Dyson, Stan Kelly-Bootle, and John Heilborn (a SYBEX book,
1999, and over a thousand pages for $19.95, new). Its the first 400
pages or so that are most useful, the rest looks like MAN PAGES
which you should already have on your install.
------------------------------
From: KCmaniac <[EMAIL PROTECTED]>
Subject: LILO??
Date: Sun, 03 Jun 2001 17:02:01 -0400
I was wondering if anybody could tell me what in the sam hill is going
on in this LILO config file ...
these two lines are confusing the hell out of me.
*
*
*
default=Linux
*
*
*
image=vmlinuz
In the /boot directory the only "images" that are there is one called
vmlinuz-2.2.19-idepci and another called vmlinuz-2.2.19pre17-idepci.
There are two system.map files that looks like they represent these two
images. There is also just a file called map.
There is not a file called vmlinuz or Linux anywhere in this directory.
When I use "uname -r" I get "2.2.19pre17-idepci".
Can anyone explain how this version is derived through the lines in LILO
that I showed above. I am using LILO to boot and it is installed in the
MBR.
I am using Debian. I ran apt-get update and apt-get install, not
knowing really what to expect. It apparently wanted to install a
kernal-image or something. It asked me if I wanted to make a boot disk,
I guess in case of a problem. I did. I used the boot disk just to see
what would happen. When the system booted up I used "uname -r" and it
gave me "Linux"????
I am really confused about what damn kernal I am using, how is it that
it is being used and what in the hell is a kernal version called just
plain Linux or just plain vmlinuz???
Thanks for any insight ...
RLH
------------------------------
From: [EMAIL PROTECTED]
Subject: linuxconf command doesn't work!
Date: Sun, 03 Jun 2001 17:41:25 -0400
Hello. I typed linuxconf, but nothing happens. Is there any reason
for that?
I am using:
RedHat 7.1 (on hdc2)
Gnome and KDE instolled (Using Gnome)
I also have Win2K on hda1, having Lilo on the first sector of
hdc2.
Does this dual boot have anything to do with failing to do linuxconf
command?
I also tried as root, but was the same result.
Any help will be appreciated , thanks.
tsug
------------------------------
From: [EMAIL PROTECTED] (Rinaldi J. Montessi)
Subject: Re: ATA100 Card
Date: Sun, 03 Jun 2001 21:26:00 GMT
John L. Sielke wrote:
> OK, I decided I needed a bigger HSD, so I got a Quantum 40GB drive. My old PII
> 300Mhz had an onboard IDE interface, which wouldn't work with the new drive, so
> I go aSIIG UltraATA100 PCI card. Everything works in Windows, but Linux doesn't
> see the card or drive. I have been running Linux 6.2, (kernel 2.2.5) but tried
> installing RH 7.0 with the new HD, but it still didn't see it. Any suggestions
> please?
>
> John
I think RH 7.0 shipped with a 2.2.19 kernel which could not "see" off
board ide ports. 7.1 ships with the 2.4.2 kernel which can.
There are parameters that can be passed if you must use 7.0. Read the
main screen closely after boot; it may contain the information.
Rinaldi
--
We all know Linux is great...it does infinite loops in 5 seconds.
--Linus Torvalds
------------------------------
From: "david yuan" <[EMAIL PROTECTED]>
Subject: Urgent: scrwed up glibc library. now nothing worked.
Date: Sun, 03 Jun 2001 21:51:43 GMT
Hi all,
I stupidly applied glibc.2.2.1-3.2.4.rpm to my RH6.1 using (force and
no-dependency checking). i thought i might resolve the problem a bad glibc
version for java(1.3).
Now seems every command failed:
FATAL: kernel too old.
How do I have the original glibc back? I really do not want to re-install
from scratch since the machine is a gateway which has dhcpd, named, firewall
etc and I cannot copy their config files to other places. I cannot use RPM
and TAR commands any more because above FATA problem either. basically no
shell commands work except "ls".
Please someone helps me to bring old glibc back.
thanks
--
====================================
Make Unlimited phone calls from your PC to ANY phone in the World!
http://www.eboom.com/free/
------------------------------
Date: Sun, 03 Jun 2001 23:54:57 +0200
From: Michael Heiming <[EMAIL PROTECTED]>
Subject: Top 10 posters for the 7 day period ending 2001-06-03
Top 10 posters for the 7 day period ending 2001-06-03.
(comp.os.linux.setup)
posts kbytes name address
1 28 77.2 Peter T. Breuer [EMAIL PROTECTED]
2 21 39.8 Dave Uhring [EMAIL PROTECTED]
3 20 44.6 David Efflandt [EMAIL PROTECTED]
4 14 46.0 KCmaniac [EMAIL PROTECTED]
5 13 24.4 =?ISO-8859-1?Q?Rasmus_B=F moffespam@amagerkollegiet
6 11 20.8 Dave Uhring [EMAIL PROTECTED]
7 7 15.0 Riyaz Mansoor [EMAIL PROTECTED]
8 7 14.8 Sasan Iman [EMAIL PROTECTED]
9 7 12.5 Rand Simberg simberg.interglobal@trash
10 7 11.9 Michael Heiming [EMAIL PROTECTED]
--- -----
135 307.0 Total for top 10
Totals for the newsgroup:
428 posters
809 articles
1566.7 kbytes
The top 10 accounted for:
2.3% of the posters
16.7% of the articles
19.6% of the bytes
Averages:
1.9 articles / poster
1.9 kbytes / article
3.7 kbytes / poster
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: CRON won't run my executable
Date: Sun, 3 Jun 2001 21:59:07 +0000 (UTC)
Reply-To: [EMAIL PROTECTED]
On Sun, 03 Jun 2001 18:23:25 GMT, Mark Johnson <[EMAIL PROTECTED]> wrote:
> Could this be a path problem. I'm thinking maybe cron doesn't have the
> correct libraries in its PATH. Is there a way that I can check to make
> sure cron has access to the PATHs?
Do I sound like a broken record when I say you still have told us nothing
at all about your 'timestamp' which is apparently where the problem lies.
You should assume that cron has minimal environment. If you need a
specific PATH or other environment, you should set that at the beginning
of the crontab or use full paths for everything. If you don't have your
mail server properly set up to mail cron errors, adding 2>&1 to the end of
the line that runs your timestamp (within the backticks) could be
enlightening when it logs that.
--
David Efflandt (Reply-To is valid) http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
------------------------------
From: David Hines <[EMAIL PROTECTED]>
Subject: Re: linuxconf command doesn't work!
Date: Sun, 3 Jun 2001 14:59:19 -0700
[EMAIL PROTECTED] wrote:
> Hello. I typed linuxconf, but nothing happens. Is there any reason
> for that?
>
> I am using:
>
> RedHat 7.1 (on hdc2)
> Gnome and KDE instolled (Using Gnome)
>
> I also have Win2K on hda1, having Lilo on the first sector of
> hdc2.
> Does this dual boot have anything to do with failing to do linuxconf
> command?
> I also tried as root, but was the same result.
>
> Any help will be appreciated , thanks.
>
>
> tsug
>
>
>
Type rpm -q linuxconf and see if the package is installed.
Dave
------------------------------
From: [EMAIL PROTECTED] (Bit Twister)
Subject: Re: linuxconf command doesn't work!
Reply-To: [EMAIL PROTECTED]
Date: Sun, 03 Jun 2001 22:07:52 GMT
Click on the rpm manager and see if you can install from the cd.
Depending on what type install you picked, it may not installed it.
On Sun, 3 Jun 2001 14:59:19 -0700, David Hines
><[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] wrote:
>
>> Hello. I typed linuxconf, but nothing happens. Is there any reason
>> for that?
>>
>> I am using:
>>
>> RedHat 7.1 (on hdc2)
>> Gnome and KDE instolled (Using Gnome)
>>
>> I also have Win2K on hda1, having Lilo on the first sector of
>> hdc2.
>> Does this dual boot have anything to do with failing to do linuxconf
>> command?
>> I also tried as root, but was the same result.
>>
>> Any help will be appreciated , thanks.
>>
>>
>> tsug
>>
>>
>>
>Type rpm -q linuxconf and see if the package is installed.
>
>Dave
--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a, man command_here or cat command_here, before using it.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
