Re: Why are modules and modules.conf not versioned?
On Fri, Nov 08, 2002 at 05:33:02PM -0500, Michael Stone wrote:
> On Fri, Nov 08, 2002 at 11:57:56AM -0700, Eric Richardson wrote:
> >The problem I am trying to solve in this. Anyone using a laptop that
> >installed or upgraded to woody that decided to update to 2.4 series
> >kernel would have had to used the modules.conf file language to make
> >both the 2.2 and the 2.4 kernel to work. Normally it is nice to have a
>
> I don't understand why upgrading from 2.2 to to 2.4 on a laptop involves
> touching /etc/modules at all. I don't have anything in /etc/modules
> having anything to do with pcmcia (I assume that's what you mean by the
> laptop reference?)
I had similar experience. PCMCIA service and NAT are the issues.
2.2 Kernel had more things in the kernel and I did not need to do worry
about modules (In the same way, 2.4 kernel used in boot-floppy has more
things as a part of kernel than other standard kernel-image.)
I was expecting auto-loading modules shall work for 2.4, but it did not.
I had to chaange it too. I am on i486 laptop (At least 2.4.12 days).
Since then, I never touched but system is working with 2.4.18.
I added isa-pnp and many iptables things. Without them, it did not work
as my router. This was crucial. As I see /etc/modules.
sunrpc
lockd
nfsd
isa-pnp
ip_gre
ipip
ip_tables
ip_conntrack
ip_conntrack_ftp
iptable_nat
iptable_filter
iptable_mangle
...
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <osamu@debian.org> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Reply to: