I may be wildly off base here but I think a couple of people were
asking about how to setup the new trinux distrib to suit their cards
and I was stupidly saying "just go edit your modules file". OK, 0.62
doesn't load stuff the way the old trinux distribs did so now I
recant.
I got 0.62 and had some problems that I don't have time to investigate
right now. They pay me to do non-trinux here. 0.62 config is
different than the previous trinux versions I have. I like it more.
I am glad that the idea of sourcing shell envar files from the boot
disk is being used.
My first boot of 0.62 did not work well and I could not run bash or vi
(elvis) but after booting a 2nd time it worked beautifully. Must have
been swamp gas of something ...
Observations:
In linuxrc, $MODULES is not set before it is used. I suspect this is
a left over from the previous init scheme or is a peek into a future
or undocumented scheme. If I have missed something about this please
correct me.
Also linuxrc copies /floppy/modules to / instead of /etc. Since many
of the net drivers (I don't know how many) are compiled in now, it
probably isn't needed for most users.
Anyone know where I can see the .config file from the kernel compile
or where a list of the compiled in NIC drivers are versus those
compiled as modules?
In the netcfg script there is a typo in the line:
"if [ -f /etc/con/dhcp" this should read "if [ -f /etc/conf/dhcp".
Finally, Michael, the original issue about setting up the modules file
no longer matters since the arguments you want to pass to the driver
can be passed on the command line to the kernel during the boot.
Those are setup as an APPEND argument in the syslinux.cfg file.
>From BootPrompt-HowTo by Paul Gortmaker.
<http://metalab.unc.edu/pub/Linux/docs/HOWTO/BootPrompt-HOWTO>
10.1. Ethernet Devices (`ether=')
Different drivers make use of different parameters, but they all at
least share having an IRQ, an I/O port base value, and a name. In its
most generic form, it looks something like this:
ether=irq,iobase[,param_1[,param_2,...param_8]]],name
The first non-numeric argument is taken as the name. The param_n
values (if applicable) usually have different meanings for each
different card/driver. Typical param_n values are used to specify
things like shared memory address, interface selection, DMA channel
and the like.
Hope this helps. Sorry for the confusion.
Is there a config guide that applies to the new trinux versions?
Should I be undertaking it?
Thanks,
Costa
Date: Tue, 23 Nov 1999 15:01:33 -0700 (MST)
From: Michael Taylor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Trinux questions
On Tue, 23 Nov 1999, CD Rasmussen wrote:
> What level of trinux are you running? The init sequence has changed.
I am using the newest version. I just downloaded it yesterday.
-Mike Taylor-
[EMAIL PROTECTED]
> Costa
------------------------------------------------------------------------------------
www.trinux.org hosted by The Vnode Connector Services
www.vnode.com *** Special Discounts For Trinux Users
*** Email [EMAIL PROTECTED]
------------------------------------------------------------------------------------
