On Sun, Oct 15, 2006 at 02:24:09PM -0500, John and Holly Klug wrote:
> I am using kernel 2.6.14-2-386 and yaird 0.0.12-8.
>
> It appears that yaird requires that one be running the kernel that is
> being targeted when creating an initrd image. This is because it gets
> the sy
I am using kernel 2.6.14-2-386 and yaird 0.0.12-8.
It appears that yaird requires that one be running the kernel that is
being targeted when creating an initrd image. This is because it gets
the system configured release kernel name (uname -r) to generate paths.
This means one cannot use a
on Wed, May 09, 2001 at 12:09:38AM -0600, Stefan Srdic ([EMAIL PROTECTED])
wrote:
> I though that its possible to use the ext2 filesystem to use with
> initrd? Is there an advantage of using the minixfs filesystem over
> the ext2 filesytem in this application?
minixfs is reputed to have lower o
On Wed, May 09, 2001 at 07:18:02PM +1000, Herbert Xu wrote:
> Joey Hess <[EMAIL PROTECTED]> wrote:
>
> > Well there is a package in unstable called mkcramfs that makes initrds
> > for debian, and it is supported by kernel packages for unstable.
>
> Actually, mkcramfs just makes a cramfs image. I
Joey Hess <[EMAIL PROTECTED]> wrote:
> Well there is a package in unstable called mkcramfs that makes initrds
> for debian, and it is supported by kernel packages for unstable.
Actually, mkcramfs just makes a cramfs image. It's initrd-tools that
contains mkinitrd which makes initrd images.
--
D
Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
> Fairly easy to make, biggest snag is you really have to be root to make them
> properly.
If you're building a cramfs or romfs image, then root is unnecessary as
fakeroot works just fine.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
E
> >
> > either way...you need to make sure you have minixfs and /dev/ram enabled
> > in your kernel to be able to create initrd files
> >
>
> I though that its possible to use the ext2 filesystem to use with initrd>? Is
> there
> an advantage of using the minixfs filesystem over the ext2 filesyt
hi ya will
there is no initrd howto that i could find...
those docs i did find in google searches were out of date
and incomplete in terms of getting a flash disk that you can boot
into /dev/ram0
-- lets assume that tomsrtbt is too small on the 1.77Mb floppy
and cdrom is too much hassle
Alvin Oga wrote:
> hi stefan...
>
> mkinitrd ...
>
> or take an existing initrd.gz file...decompress it
> into /dev/ram or /dev/loop
>
> than change the kernel to your version, add your libs/commands
> and other stuff you want in the initrd to make your system
> bootable
>
> and compress that /d
On Tue, May 08, 2001 at 08:32:01PM -0700, Alvin Oga wrote:
> mkinitrd ...
>
> or take an existing initrd.gz file...decompress it
> into /dev/ram or /dev/loop
>
> than change the kernel to your version, add your libs/commands
> and other stuff you want in the initrd to make your system
> b
hi stefan...
mkinitrd ...
or take an existing initrd.gz file...decompress it
into /dev/ram or /dev/loop
than change the kernel to your version, add your libs/commands
and other stuff you want in the initrd to make your system
bootable
and compress that /dev/loop image into your_init
Stefan Srdic wrote:
> I've compiled the 2.4.3 kernel on my patato box. I'm interrested in
> creating my own initial RAM disk (initrd) to speed up my boot process.
>
> Does anybody know of any good HOW-TO's on initrd's?
>
> Does anybody have some insight to share?
Well there is a package in unsta
On 08-May-2001 Stefan Srdic wrote:
> I've compiled the 2.4.3 kernel on my patato box. I'm interrested in
> creating my own initial RAM disk (initrd) to speed up my boot process.
>
> Does anybody know of any good HOW-TO's on initrd's?
>
> Does anybody have some insight to share?
>
Fairly easy t
I've compiled the 2.4.3 kernel on my patato box. I'm interrested in
creating my own initial RAM disk (initrd) to speed up my boot process.
Does anybody know of any good HOW-TO's on initrd's?
Does anybody have some insight to share?
Stef
14 matches
Mail list logo
