Need a Network card driver

[tinypoodle]

That's ok, but having in mind future users reading posts is a good idea  
(And I have observed more than once users failing for taking something too literally)

[tinypoodle]

ifconfig eth0 = no such device
modprobe = device found and module installed
ifconfig eth0 = there, but didn't get an address from dhcp server

...as expected

Code: [Select]

udhcpc -i eth0

[Rich]

Hi mattrix
OK, that's good news, it took the driver. Click on the control panel icon and use the network setup
tool to disable DHCP and assign an IP address.

[mattrix]

Thanks muchly for the help,

more than once users failing for taking something too literally)

whats a noob to do? its the noob's condition
I've seen command sequences that just make no sense to me,
but noone else sees anything wrong with them

udhcpc -i eth0

worked a treat - thankyou

Click on the control panel icon and use the network setup

a bit difficult in micro core

Now how do I make all this persitent? Does bootlocal.sh execute after mydata is restored? More to the point is it run as root?

ps wheres the pretty picture, I thought I read the wiki from front to back, including the page on investing in gold!
EDIT found it, not in the wiki, http://www.tinycorelinux.com/architecture.html

pps how do I run e2fsck on the same partition as microcore, e2fsck tells me to umount it first?

[curaga]

Now how do I make all this persitent? Does bootlocal.sh execute after mydata is restored? More to the point is it run as root?

Add the modprobe and udhcp to bootlocal.sh. Yes. Yes.

ps wheres the pretty picture, I thought I read the wiki from front to back, including the page on investing in gold!

vga=xxx

pps how do I run e2fsck on the same partition as microcore, e2fsck tells me to umount it first?

Boot without mounting it "base norestore" and then you can operate on the HD.

[tinypoodle]

Wondering why you would use MC while concurrently asking so many most basic questions about the system...
I would highly recommend to use TC and included tools to explore and become a bit more familiar with the system and it's basic architecture, under the condition that you have at least 48-64MB of RAM.

[mattrix]

Wondering why you would use MC while concurrently asking so many most basic questions

sorry for the stupid questions.

Tiny core seems somewhat different, in the way it does things, than other unix's. And its a bit hard to separate whats tiny core and whats linux.

I'm not unfamiliar with computers, pre se,  just with how linux does things.
The object is to learn about linux, the command line seemed to be a good place to start with hardware that I've discovered is, from a linux point of view, very minimal. (besides my mouse is not working properly )
Admittedly tiny core seems better documented than microcore for the distro specific stuff.

If I really wanted to do "something" with this hardware, microsoft seems to squeeze more functionality from it, (running win98se and off97). ( I know old)

But maybe thats just because I'm unfamiliar with linux.

Any way thanks so much for your help.

[Rich]

Click on the control panel icon and use the network setup

a bit difficult in micro core

Doh!  And it was the very first thing he mentioned in his first post.

[tinypoodle]

Yes but...
Running microcore does not necessarily mean running without a GUI equivalent to tinycore, i.e. core elements.

You can see that in Reply #2 also I gave the approximate size of mem usage of tinycore.

And as hinted already, difficult to imagine that someone who has a lot of most basic questions would not use a GUI to get familiar with the system first...

[mattrix]

...  difficult to imagine that someone who has a lot of most basic questions would not use a GUI to get familiar with the system first...

Its all about levels of abstraction.
A good GUI is designed to hide the system from you.
Ask almost any (old) windows user about their  VMM32.VXD and they'll look at you blank, but ask a dos user about their config.sys and at least they'll know what your talking about.
As you can tell from the 16bit network card, this isn't the most recent hardware.
Besides I thought it would fit better with my previous Unix experience.

Yes but...
Running microcore does not necessarily mean running without a GUI equivalent to tinycore, i.e. core elements.

Now that I've got networking, after I work out what all the tce-* files are for, I will install the GUI components to see all the info about mounted filesystems.

...   most basic questions ...

I've got questions that are way more basic than this.

Anyway, did I thank you both for helping me.

[tinypoodle]

A good GUI is designed to hide the system from you.

With TC, the particular GUI tool may become the initial motivation to explore their backends, for those who are interested   

[hiro]

I found it a bit more difficult to find and read the source of a gui tool. cat `which tce-load` is very simple.

All extensions are mounted to /tmp/tcloop/ and then linked into the root filesystem.

[tinypoodle]

with 'cp -ais' for accuracy

[hiro]

OT: Heh, I didn't know cp was able to do this. In my view it shouldn't.
The use of yes y in order to answer the prompts is also indicating the problem I have with modern cp.

[tinypoodle]

The use of yes y in order to answer the prompts is also indicating the problem I have with modern cp.

Code: [Select]

cat ~/.ashrc