Very Computer

I am relatively new to linux and have 2 unrelated problems.

first,
I have a cable modem and I load my network card driver as a module.
I would like to know how do I make this happen automatically during the boot
process and how to I modify the order in whuch certain commands are
executed.

Right now my system tries to start the network, then loads dhcpcd but it
does not load the kernel module for the network card. I have to manually
load the driver (modprobe ne2k-pci) then issue the network command. I looked
in the init scripts but these are so complex I have no idea what they mean
or how to change things. Any one knows how to help?

second problem - lilo
I have windows nt and linux. I use NT OS Loader to choose either NT or Linux
when i boot. I also have 2 hard disks, NT is on the first (primary master)
and Linux is on the second (secondary master). drive C uses NTFS. Originally
I had RedHat 5.1 and could load linux from NT OS Loader without problem.
Since i upgraded to RedHat 5.2 I have been unable to load Linux from NT OS
Loader. I can only use a floppy to boot to Linux. The thing is I don't think
the problem is the OS Loader. I get the LILO prompt after  select linux but
nothings happens afterwards. Does anyone have a clue how I can proceed from
here?

Any help on either problem will be appreciated.

Thanx
Ron

Quote:>I am relatively new to linux and have 2 unrelated problems.

>second problem - lilo
>I have windows nt and linux. I use NT OS Loader to choose either NT or
Linux
>when i boot. I also have 2 hard disks, NT is on the first (primary master)
>and Linux is on the second (secondary master). drive C uses NTFS.
Originally
>I had RedHat 5.1 and could load linux from NT OS Loader without problem.
>Since i upgraded to RedHat 5.2 I have been unable to load Linux from NT OS
>Loader. I can only use a floppy to boot to Linux. The thing is I don't
think
>the problem is the OS Loader. I get the LILO prompt after  select linux but
>nothings happens afterwards. Does anyone have a clue how I can proceed from
>here?

Now  the problem here is that Linux cannot see NTFS partitions without an
additional driver.  I am uncertian how you set this up originally, but
usually, it is done by running a  command like dd if=/dev/null of=/ntboot
bs=512  which will create a 512 byte file as /ntboot.  Then modify the boot=
line in the /etc/lilo.conf file to read /ntboot.  Save the /etc/lilo.conf
file and then run the command lilo.
Assuming the rest of the lilo.conf file is setup correctly, you now have a
file which can boot linux.  Copy this file to a DOS formatted floppy.  Now
reboot into NT.  Look at the file c:\boot.ini and find which file the Linux
line of boot.ini points to.  Now copy the file from floppy to the file named
in the boot.ini file.
Everytime you install a new kernel, you will have to go through the same
process.  The reason is that lilo stores the offset of the kernel image in
this file to allow it to boot.  When you put a new boot image into the
filesystem, eg when upgrading, the position of the boot image changes, so
lilo must be re-run to update the image.

I have heard that it is possible to get a module for Linux which allows you
to write to an NT partition.  If this is possible, you could mount your NT
partition under linux and point LILO at the appropriate file to ease the
process.

    Hope this helps,

            Martin

Quote:

>Any help on either problem will be appreciated.

>Thanx
>Ron