Mailinglist Archive: opensuse (3261 mails)

["crrey" <crrey@xxxxxxxx>]

ROFL

-----Original Message-----
From: marsaro@xxxxxxxxxxxxxx [mailto:marsaro@xxxxxxxxxxxxxx]
Sent: Monday, April 23, 2001 2359
To: Rafael E. Herrera
Cc: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] Support vs Support (Was: [SLE] util-linux and Kernel
2.4.3)




Wow....is everyone on dope or something?.........why not use this list
instead of a rant...if there are those that just cannot stand using the
product (which ever it may be you will find an issue) go hang out at
Venice Beach with a G-string and cry about it....


Regards,


Jon

On Tue, 24 Apr 2001, Rafael E. Herrera wrote:

> Brooklyn Linux Solutions CEO wrote:
> >
> > >
> > > > modules.conf was invisible to the 7.0 system with a hand compile
> > >
> > > What are you talking about??? This file is a standard.
> >
> > This file was ignored - not looked at, as i it didn't exist to the
> > astounishment of several expereiced users.
> >
> > It's functionality depends on it being initated correctly by the kernel.
> >
> > mkinitrd does this for RH.  This file does not exist in SuSe.
> > Instead it is done with /etc/rc.d files.....
>
> wrong, modules.conf is part of the modutils packages and is integral
> part of suse. /etc/rc.d files are part of the sys V init mechanism and
> has nothing to do with modules.conf.
>
> There is no mkinitrd script in SuSE. To create initrd files under suse
> you use mk_initrd. It's been mentioned already:
>
> Michael Hasenstein wrote:
> >
> > ??? /sbin/mk_initrd. _Very_ convenient. The entire SuSE lilo-kernel
> > setup is one big piece of convenience:
> > - no need for you to edit lilo.conf for installing a new kernel you made
> > yourself, just do "make bzlilo". The old default suse kernel is always
> > available as entry "suse" when you overwrite "linux", should you've
> > forgotten a module or to create the initrd or the new kernel has
> > problems for whatever other reason.
> > - creating a config file for a new kernel is _very_ convenient: just use
> > the working, running kernel config as input by issuing "make
> > cloneconfig", which takes the config from the running kernel and applies
> > it to the source tree.
> > - mk_initrd: if you use all the above, all you ever need to do when you
> > compile your own is
> > make cloneconfig [maybe: menuconfig, if you want to change something]
> > dep clean bzlilo modules modules_install; mk_initrd; lilo
> > (if the new kernel has the _same_ version as the old one it's also a
> > good idea to edit linux/Lakefile line 3 and add some string to
> > EXTRAVERSION in order to avoid overwriting the existing modules
> > directory in /lib/modules/)
>
> --
>      Rafael
>
> --
> To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the FAQ at http://www.suse.com/support/faq and the
> archives at http://lists.suse.com
>
>


--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/support/faq and the
archives at http://lists.suse.com