Mailinglist Archive: opensuse (3419 mails)
| < Previous | Next > |
Re: [opensuse] Creating a custom LiveCD / auto discover and load modules
- From: tleslie <tleslie@xxxxxxx>
- Date: Tue, 10 Apr 2007 01:35:26 -0400
- Message-id: <1176183326.4848.23.camel@xxxxxxxxxxx>
what your looking for is the init (binary, compiled C) in the openSuse
live DVD/CD distro.
not sure what this wouldn't do for you , that you want?
works fine for the liveDVD i produce.
All needed modules are in the initrd.gz on the liveDVD,
if you mkinitrd on a installed distro it is only going to include
modules you need, not the standard shit load you need on a live distro.
The init binary on the liveDVD will run through pci-ids and modprobe the
necessary modules for you.
-tl
On Mon, 2007-04-09 at 18:34 -0500, Kevin Adler wrote:
> I'm trying to create my own live cd and in the process learn more about how
> linux works. I started out by modifying my initrd from my laptop and things
> were working nicely until I tried to test it on my desktop. Unfortunately, I
> could not detect any of the hard drives on my desktop machine because none of
> the correct modules were loaded. So I kompared the two init scripts from my
> laptop and desktop initrd and it seems they are tailored to each system. In
> order to boot on other sorts of hardware I need a more generalized form. I
> decided to try and see how the initrd works from the installation disk, but
> that runs the linuxrc program. Although this method does determine all the
> correct modules to load, it is written in C, isn't commented very well, and
> includes everything needed to get the installer going, which is way more than
> I need and more than I care to wade through. I think there must be something
> simpler.
>
> So what I'm looking for is a way to discover which modules a system needs to
> load and then load them. It seems like it should be somewhat simple to do
> once I get over the initial hurdle.
>
> Any hints or pointers to other resources would be helpful. I've found quite a
> lot already, but I just can't seem to figure out this one particular.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
live DVD/CD distro.
not sure what this wouldn't do for you , that you want?
works fine for the liveDVD i produce.
All needed modules are in the initrd.gz on the liveDVD,
if you mkinitrd on a installed distro it is only going to include
modules you need, not the standard shit load you need on a live distro.
The init binary on the liveDVD will run through pci-ids and modprobe the
necessary modules for you.
-tl
On Mon, 2007-04-09 at 18:34 -0500, Kevin Adler wrote:
> I'm trying to create my own live cd and in the process learn more about how
> linux works. I started out by modifying my initrd from my laptop and things
> were working nicely until I tried to test it on my desktop. Unfortunately, I
> could not detect any of the hard drives on my desktop machine because none of
> the correct modules were loaded. So I kompared the two init scripts from my
> laptop and desktop initrd and it seems they are tailored to each system. In
> order to boot on other sorts of hardware I need a more generalized form. I
> decided to try and see how the initrd works from the installation disk, but
> that runs the linuxrc program. Although this method does determine all the
> correct modules to load, it is written in C, isn't commented very well, and
> includes everything needed to get the installer going, which is way more than
> I need and more than I care to wade through. I think there must be something
> simpler.
>
> So what I'm looking for is a way to discover which modules a system needs to
> load and then load them. It seems like it should be somewhat simple to do
> once I get over the initial hurdle.
>
> Any hints or pointers to other resources would be helpful. I've found quite a
> lot already, but I just can't seem to figure out this one particular.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |