looking for trouble shooting resouces

2005-05-04 Thread germ germ
I just Install Debian and am unable to pull an IP. I
think I may have configured something incorrectly or
don't have a driver for the NIC.  Does anyone have any
resouces they could recommend so I can fix this?

thanks

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: looking for trouble shooting resouces

2005-05-04 Thread Tony Vandiver
I'm a newbie, but have you tried modconf to add the correct driver and
remove the bad one?  What kind of NIC do you have?  What distribution did
you install?
Tony Vandiver
- Original Message - 
From: germ germ [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Wednesday, May 04, 2005 8:19 PM
Subject: looking for trouble shooting resouces


I just Install Debian and am unable to pull an IP. I
think I may have configured something incorrectly or
don't have a driver for the NIC.  Does anyone have any
resouces they could recommend so I can fix this?
thanks
__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact 
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: looking for trouble shooting resouces

2005-05-04 Thread Monique Y. Mudama
On 2005-05-05, germ germ penned:
 I just Install Debian and am unable to pull an IP. I think I may
 have configured something incorrectly or don't have a driver for the
 NIC.  Does anyone have any resouces they could recommend so I can
 fix this?

Well, maybe a few questions will help you formulate an attack plan.

Are you trying to get a dynamic or a static IP?

What does a search of 'eth' in the output of `dmesg` produce?

What is the output of `ifconfig -a`?

What do you remember about your choices in the network configuration
portion of the installation process?

A google search on 'debian network configuration' turned up a number
of promising links, including this one:

http://www.debian.org/doc/manuals/reference/ch-gateway.en.html

-- 
monique

Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Looking for trouble.

1999-04-20 Thread Bob Hilliard
Oliver Elphick olly@lfix.co.uk writes:

 Bob Hilliard wrote:
   Oliver Elphick olly@lfix.co.uk writes:
   
To go to the directory you were in last:
cd ~-
   
What is the purpose of the tilde in this command?  In bash and
   sh, at least, `cd -' is what I was taught, and it works fine.  Do some
   other shells require `cd ~-'?
  
 That is the Korn shell convention; I did not know that bash supported the
 simpler form.
 
 -- 
 Oliver Elphick[EMAIL PROTECTED]
 Isle of Wight  http://www.lfix.co.uk/oliver


 I have learned two things from this exchange:

 1.  I learned how the Korn Shell handles this.

 2.  I learned to specify the applicable shell when answering a
question about shell commands.

Bob
-- 
   _
  |_)  _  |_   Robert D. Hilliard[EMAIL PROTECTED]
  |_) (_) |_)  Palm City, FL  USAPGP Key ID: A8E40EB9


Re: Looking for trouble.

1999-04-19 Thread Bob Hilliard
Oliver Elphick olly@lfix.co.uk writes:

 To go to the directory you were in last:
 cd ~-

 What is the purpose of the tilde in this command?  In bash and
sh, at least, `cd -' is what I was taught, and it works fine.  Do some
other shells require `cd ~-'?

Bob
-- 
   _
  |_)  _  |_   Robert D. Hilliard[EMAIL PROTECTED]
  |_) (_) |_)  Palm City, FL  USAPGP Key ID: A8E40EB9


Re: Looking for trouble.

1999-04-19 Thread Oliver Elphick
Bob Hilliard wrote:
  Oliver Elphick olly@lfix.co.uk writes:
  
   To go to the directory you were in last:
   cd ~-
  
   What is the purpose of the tilde in this command?  In bash and
  sh, at least, `cd -' is what I was taught, and it works fine.  Do some
  other shells require `cd ~-'?
 
That is the Korn shell convention; I did not know that bash supported the
simpler form.

-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight  http://www.lfix.co.uk/oliver
   PGP key from public servers; key ID 32B8FAA1
 
 For by grace are ye saved through faith; and that not 
  of yourselves; it is the gift of God, not of works, 
  lest any man should boast.   Ephesians 2:8,9 



Re: Looking for trouble.

1999-04-19 Thread Hamish Moffatt
On Mon, Apr 19, 1999 at 09:58:21AM +0100, Oliver Elphick wrote:
 Bob Hilliard wrote:
   Oliver Elphick olly@lfix.co.uk writes:
   
To go to the directory you were in last:
cd ~-
   
What is the purpose of the tilde in this command?  In bash and
   sh, at least, `cd -' is what I was taught, and it works fine.  Do some
   other shells require `cd ~-'?
  
 That is the Korn shell convention; I did not know that bash supported the
 simpler form.

Do you mean that ~- is the ksh convention, or just - is? Just - works fine
on the ksh I'm used to (HP-UX). tcsh also supports cd -.


Hamish
-- 
Hamish Moffatt VK3TYD. 
CCs of replies from mailing lists are welcome.


Re: Looking for trouble.

1999-04-19 Thread Carl Johnson
Oliver Elphick olly@lfix.co.uk writes:

 Bob Hilliard wrote:
   Oliver Elphick olly@lfix.co.uk writes:
   
To go to the directory you were in last:
cd ~-
   
What is the purpose of the tilde in this command?  In bash and
   sh, at least, `cd -' is what I was taught, and it works fine.  Do some
   other shells require `cd ~-'?
  
 That is the Korn shell convention; I did not know that bash supported the
 simpler form.

Bash also supports the ~- (and ~+) forms.  They are shell expansions,
whereas 'cd -' is a shortcut for the cd program itself.  Look up
Tilde Expansion in the bash (or ksh) man page for details.
-- 
Carl Johnson[EMAIL PROTECTED]


Looking for trouble.

1999-04-18 Thread Hans van den Boogert
There doesn't seem to be a special group for Debian Newbies, so I hope
y'all don't mind me bringing up some questions here. I did a lot of reading
on Linux and Debian, but I now have a copy of Debian 2.1 and am trying to
get a system up.

Background: Dutch, teacher, location: Taiwan, 32, shortwave DXer. 
System1: Pentium 200MMX, 64 MB RAM, 3.2+6.1 GB HD, S3 Trio64, Soundblaster
AWE64.
System2: Twinhead Slimnote 486-33, 8 MB RAM, 305 MB HD, VGA monochrome
monitor.

What I did sofar: Installed Debian 2.1 with base system on the Twinhead,
with 9 floppies.
Aim: Connect a parallel port CD-ROM (Shuttle EPIA) and install the rest of
the system.

Remarks: I cleaned the HD and reformatted it as one partition (305 MB).
However, Debian 2.1 installation couldn't get cfdisk going and thus I used
the second console to manually partition and set the swap. 

Questions:
1) What is an easy way to go to the previous directory, e.g. I am in
/usr/bin and want to go to /usr?
2) With the base system installed I can't open man pages, that is, when
typing man ls for example, the system returns with command not found.
In /bin and /sbin I also can't see any man-binary. There are man pages
stored, but in .gz format. Is it normal that the man command is not
installed? How to open/read .gz files.
3) I tried to create some scripts, very simple ones, but they refuse to
run, or the system says command not found. Example:

#! /bin/bash
#
echo The time and date is..
date

Saved as telltime, then mode changed with chmod -v u+x telltime. With cat
I can still see the contents of the file as plain text. Is this normal?
As said, when executing telltime the system returns command not found.
I know that you have to watch the path, but even when I put this script in
/ or /bin it still won't run, while installed commands like date do run
from almost every directory. What do I do wrong?
4) Any hints to where to find some in dept Debian specific FAQs? I know
there is a lot around, and believe me I've been reading, but most
tutorials/FAQs assume that the system is running smoothly and hardly deal
with problem solving.

Thanks for the help.

Hans

I was riding on the e-train
I was whistling to the rhythm
I was thinking 'bout my livin'
I was feeling pretty fineI asked the time
.Got a poke in the eye.

(Sheryl Crow, The Globe Sessions)


Re: Looking for trouble.

1999-04-18 Thread James Mastros
On Sun, Apr 18, 1999 at 02:34:57PM +0800, Hans van den Boogert wrote:
 There doesn't seem to be a special group for Debian Newbies, so I hope
 y'all don't mind me bringing up some questions here.
Don't worry; this is a large part of what this mailinglist is here for.  And
we're glad that you RTFMed before you got here G.

 Background: Dutch, teacher, location: Taiwan, 32, shortwave DXer. 
 System1: Pentium 200MMX, 64 MB RAM, 3.2+6.1 GB HD, S3 Trio64, Soundblaster
 AWE64.
 System2: Twinhead Slimnote 486-33, 8 MB RAM, 305 MB HD, VGA monochrome
 monitor.

 Questions:
 1) What is an easy way to go to the previous directory, e.g. I am in
 /usr/bin and want to go to /usr?
Try cd ~-.

 2) With the base system installed I can't open man pages, that is, when
 typing man ls for example, the system returns with command not found.
 In /bin and /sbin I also can't see any man-binary. There are man pages
 stored, but in .gz format. Is it normal that the man command is not
 installed? How to open/read .gz files.
The man reader is in the package man-db; run apt-get install man-db to
install it if you are connected to the 'net.  If you just want to read some
random textual .gz file, run zless on it -- it's in the package zgip, but
you need the package less to run it.  (Install them with apt-get too.)

 3) I tried to create some scripts, very simple ones, but they refuse to
 run, or the system says command not found. Example:
From the following (cut), it looks like it, but did you try ./telltime?

 4) Any hints to where to find some in dept Debian specific FAQs? I know
 there is a lot around, and believe me I've been reading, but most
 tutorials/FAQs assume that the system is running smoothly and hardly deal
 with problem solving.
Try http://www.debain.org/doc/ -- I did just look, and there isn't much with
problem solving there.  One of the few bad things about the current state of
Linux is that there aren't detailed problem-solving docs around -- perhaps
it has somthing to do with the incidance rate of such problems.

-=- James Mastros
-- 
My friend Data: You see the world with the wonder of a child, and that
makes you more human then any of us.
-=- Lt. Tasha Yar, upon the occasion of her death.


Re: Looking for trouble.

1999-04-18 Thread Oliver Elphick
Hans van den Boogert wrote:
  1) What is an easy way to go to the previous directory, e.g. I am in
  /usr/bin and want to go to /usr?

To go to the parent directory:
cd ..

To go to the directory you were in last:
cd ~-

  2) With the base system installed I can't open man pages, that is, when
  typing man ls for example, the system returns with command not found.
  In /bin and /sbin I also can't see any man-binary. There are man pages
  stored, but in .gz format. Is it normal that the man command is not
  installed? How to open/read .gz files.

man is not part of the base system, which has to fit on a few floppies;
install man-db

  3) I tried to create some scripts, very simple ones, but they refuse to
  run, or the system says command not found. Example:
  
  #! /bin/bash
  #
  echo The time and date is..
  date
  
  Saved as telltime, then mode changed with chmod -v u+x telltime. With cat
  I can still see the contents of the file as plain text. Is this normal?
  As said, when executing telltime the system returns command not found.
  I know that you have to watch the path, but even when I put this script in
  / or /bin it still won't run, while installed commands like date do run
  from almost every directory. What do I do wrong?

On the face of it you are doing the right thing, and it ought to run from
/bin, if your path is normal.  To see what your path is, type `echo $PATH'.
The normal place to put home-grown commands is /usr/local/bin, or ~/bin (~/
is your own home directory).  These directories should be in your path.
The command `type' will tell you where the system thinks a command is:

$ type telltime
telltime is hashed (./telltime)
$ type ar
ar is /usr/bin/ar

Sometimes you may find that the system is looking at a file you weren't 
expecting.

  4) Any hints to where to find some in dept Debian specific FAQs? I know
  there is a lot around, and believe me I've been reading, but most
  tutorials/FAQs assume that the system is running smoothly and hardly deal
  with problem solving.

You want the Debian Tutorial: links from documentation on www.debian.org

-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight  http://www.lfix.co.uk/oliver
   PGP key from public servers; key ID 32B8FAA1
 
 For by grace are ye saved through faith; and that not 
  of yourselves; it is the gift of God, not of works, 
  lest any man should boast.   Ephesians 2:8,9 



Re: Looking for trouble.

1999-04-18 Thread Jan Muszynski
Can't help you much, but some of the smaller questions I can answer.

On 18 Apr 99, at 14:34,  Hans van den Boogert 
 wrote about Looking for trouble.:

[snipped to conserve bandwidth]
 Questions:
 1) What is an easy way to go to the previous directory, e.g. I am in
 /usr/bin and want to go to /usr?

try cd ..
This will take you to the parent directory of any directory you're in.
Another handy shortcut along these lines is
cd -
this will take you to the most recent directory you were in. For 
example - you're in /etc and you issue a cd /usr/src
you're now in /usr/src; if you issue a cd - you will end up in /etc, 
if you then issue another cd - you will be back in /usr/src

 2) With the base system installed I can't open man pages, that is, when
[snipped to conserve bandwidth]
 installed? How to open/read .gz files.

you need to get the man page package installed - catch22 :) I'm not 
sure if you have gzip, gunzip installed at this point or not. if so 
you can issue a gunzip name.gz to unzip the file, then look at the 
file, then followed by a gzip name to zip it up again (don't forget 
this last step).

 3) I tried to create some scripts, very simple ones, but they refuse to
 run, or the system says command not found. Example:
[snipped to conserve bandwidth]
 Saved as telltime, then mode changed with chmod -v u+x telltime.
 With cat I can still see the contents of the file as plain text. Is
 this normal? As said, when executing telltime the system returns
yes - it is normal
 command not found. I know that you have to watch the path, but
try - while in directory with script, issuing ./telltime
I'm not sure what your current path is. Issue an echo $PATH to find 
out.
 even when I put this script in / or /bin it still won't run, while
 installed commands like date do run from almost every directory.
 What do I do wrong? 

try, while in the directory with the script, issuing ./telltime

 4) Any hints to where to find some in dept Debian specific FAQs? I know
 there is a lot around, and believe me I've been reading, but most
 tutorials/FAQs assume that the system is running smoothly and hardly deal
 with problem solving.

That's because no-one ever has any problems to solve VBG

It appears that most of the Debian specific stuff is still in the 
process of being written, and they probably want to get all the base 
documentation down first.

 
 Thanks for the help.
what little it was - you're welcome.

==
   Jan M.-  mailto:[EMAIL PROTECTED]

   PGP key mailto:[EMAIL PROTECTED]
   Fingerprint:397D 093C E802 964E  5316 B90A 93CE 6696
  
Thought for the day:
Only someone who understands something absolutely
can explain it so no one else can understand it.
   -- Rudnicki's Nobel Prize Principle



Re: Looking for trouble.

1999-04-18 Thread William R Pentney
 3) I tried to create some scripts, very simple ones, but they refuse to
 run, or the system says command not found. Example:
 
 #! /bin/bash
 #
 echo The time and date is..
 date
 
 Saved as telltime, then mode changed with chmod -v u+x telltime. With cat
 I can still see the contents of the file as plain text. Is this normal?
 As said, when executing telltime the system returns command not found.
 I know that you have to watch the path, but even when I put this script in
 / or /bin it still won't run, while installed commands like date do run
 from almost every directory. What do I do wrong?


Re: Looking for trouble.

1999-04-18 Thread Randy Edwards
 3) I tried to create some scripts, very simple ones, but they refuse to
 run, or the system says command not found. Example: [...]
 Saved as telltime, then mode changed with chmod -v u+x telltime. With cat
 I can still see the contents of the file as plain text. Is this normal?
 As said, when executing telltime the system returns command not found.

   Are you executing this as root?  If so, root only runs programs in its'
path -- you'd have to do something like a ./telltime if that were the case.

   Yes, you should be able to cat the file as a plain text file (that's what
it is).  Try doing a chmod +x telltime to give everyone executable access
and see if that works.

-- 
 Regards,  | Debian GNU/Linux - http://www.debian.org - More software than
 . | *any* distribution, rock solid reliability, quality control,
 Randy | seamless upgrades via ftp or CD-ROM, strict filesystem layout
   | and adherence to standards, and militantly 100% FREE Linux!