[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Moving F7



Lots of side tracking that is not solving your problem.

Someone asked that you run the following and post the output:

# fdisk -l

This was in the thread "Grub is hard to make work".  When you post an
issue you have to stick to the same subject line in order to keep all
advice in order.

If you post that along with your grub.conf file (which youv'e done
unless you've since changed it).  It is possible that your problem is
as simple as the root command in grub.conf pointing to the wrong
drive/partition.

A person cannot trouble shoot your grub.conf file with any degree of
confidence in their advice  without knowing what drives you have in
the box (how many, including if they are SATA or IDE) and the
partition (hence the fdisk -l request) along with your grub.conf file.

Regards modules I am no expert on it.  But one simple example of a
module is for NTFS support.  You can compile a kernel with a bunch of
modules to support a bunch of different stuff.  But then your kernel
is bloated with stuff you may only need once in a while.  Instead you
can insert modules as you need them (insmod or modprobe) so that you
are not running a bloated kernel.  So a module is just some code to
provide support/functionality.  And you can add that
support/functionality by installing that module (again with insmod or
modprobe) into the running kernel.  And you can remove it if
necessary.  Beyond that I can't explain it nor is it likely needed
anyhow to trouble shoot your situation.

So fdisk -l and provide the output.

Jacques B.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]