results of my try.

Karen Lewellen klewellen at shellworld.net
Wed Jan 28 23:28:45 UTC 2015


To paraphrase Tim, those suggestions require eyeballs.  If you read 
the information, it should be clear I had to get someone else to do that, 
and it took some arranging.


On Wed, 28 Jan 2015, Cheryl Homiak wrote:

> Actually, the suggestions don't require any more experimentation than what you did. But the command you did as a regular user really does have to be done as root. Also the only difference between ifconfig eth0 and ifconfig is that the ifconfig without the argument allows debian to show you which interfaces if any are working. It is quite possible that your setup is working but under a different interface than eth0.
>
> --
> Cheryl
>
> "Move forward by looking back!
> "Above all, fear the Lord
> and worship Him faithfully with all your heart;
> consider the great things He has done for you."
> (1 Samuel 12:24 (HCSB)
>
>
>
>
>
> On Jan 28, 2015, at 10:34 AM, Karen Lewellen <klewellen at shellworld.net> wrote:
>
> I believe I have made it very clear how much experimentation is possible in prior discussions.
> I followed Tim's directions, there are  the results.
> Karen
>
>
> On Wed, 28 Jan 2015, Willem van der Walt wrote:
>
>> Hi,
>> As root, do:
>> ifconfig and check which interfaces show up.  Your ethernet might be picked up as another interface, e.g. eth1.
>> You should simply first test by pinging your router.
>> HTH, Willem
>>
>>
>> On Tue, 27 Jan 2015, Karen Lewellen wrote:
>>
>>> Hi all,
>>> here is what happened when seeking the ip address.
>>> Let me explain how I set up the machine.
>>> before even booting I put the dsl cable I am using now to send
>>> this message into the linux box, keeping it connected to my
>>> modem/rooter  as usual.
>>> Because  we were pressed for time,  after letting speakup start,
>>> and entering my username, Karen, and my password, I simply used
>>> the print screen key to  silence speakup.
>>> the error message we got is below.
>>> I saw karen at suburst:~s and there was no other place to type so
>>> after karen at sunburst:~s I typed /sbin/ifconfig eth0 as instructed
>>> the message we got was:  eth0: error fetching interface
>>> information: Device not Found
>>>
>>> We tried the step more than once to be sure.
>>> let me add that typing shutdown -h  also produced an error, so I
>>> simply turned off the machine after restoring speakup.
>>> The Ethernet card was in the computer before the hard drive
>>> containing Debian was installed, so was the rest of the hardware
>>> Linux identified.
>>> thoughts?
>>> Karen
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>> --
>>> This message is subject to the CSIR's copyright terms and conditions,
>>> e-mail legal notice, and implemented Open Document Format (ODF) standard.
>>> The full disclaimer details can be found at
>>> http://www.csir.co.za/disclaimer.html.
>>>
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> Please consider the environment before printing this email.
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>>
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>




More information about the Blinux-list mailing list