BEFORE new loader:
/dist/RH/7.1/ONE_CD/images/boot.img.junk
1.4M 1.4M 10k 100% /mnt/boot
/tmp/initrd.ext2 2.2M 1.3M 860k 59% /mnt/initrd
AFTER new loader:
/dist/RH/7.1/ONE_CD/images/boot.img.junk
1.4M 1.4M 10k 100% /mnt/boot
/tmp/initrd.ext2 2.2M 1.3M 788k 63% /mnt/initrd
I tried the gzip -9c but I still got the same error. This is the error I
get:
gzip: stdout: No space left on device
After this error, I check the df -h again, and this is what I get:
/dist/RH/7.1/ONE_CD/images/boot.img.junk
1.4M 1.4M 3.0k 100% /mnt/boot
It looks like it might have copied some of the file there, but not all.
The boot.img that I am actually using is a patched one (for the SCSI/440GX
bug). But, I don't see how this would affect this. It looks like something
else is wrong.
I am confused!
thanks,
--brett
On Mon, 29 Oct 2001 11:38:25 -0800
"Taylor, ForrestX" <forrestx.taylor@xxxxxxxxx> wrote:
> Mine was the same size, and it worked just fine. Did you add anything
else
> to the initrd.img? You may need to take out the old ks.cfg files. What
> does df -h show on your initrd.img?
>
> Forrest
>
> > I did strip it. It came out to be: 718636 bytes. I think the
> > old one was
> > 644264 bytes. I was puzzled, since I didn't think it was that
> > much bigger,
> > but I still could not copy it to the initrd. I was under the
> > gun, so I did
> > not have time to investigate it. I resorted to the workaround about
> > putting the KS files in the initrd image, and using file:/...
> >
> > It still is bugging me though that it would not copy over?????
> >
> > thanks,
> >
> > --brett
> >
> > p.s. This is what I did to copy it over:
> >
> > - mkdir /mnt/boot
> > - mount -o loop -t msdos boot.img /mnt/boot
> > - gzip -dc /mnt/boot/initrd.img > /tmp/initrd.ext2
> > - mkdir /mnt/initrd
> > - mount -o loop /tmp/initrd.ext2 /mnt/initrd
> > - cp /usr/src/redhat/SOURCES/anaconda-7.1/loader/loader
> > /mnt/initrd/sbin/
> > - umount /mnt/initrd
> > - gzip -c /tmp/initrd.ext2 > /mnt/boot/initrd.img
> >
> > This is where I get the message:
> > gzip: stdout: No space left on device
> >
> > I also tried to gzip it up to a different directory, and then copy it
> > over, but it still would not work (when I tried the copy).
> >
> > Hummmmmm????????
> >
> >
> >
> > On Mon, 29 Oct 2001 10:34:04 -0800
> > "Taylor, ForrestX" <forrestx.taylor@xxxxxxxxx> wrote:
> >
> > > Yeah. Once you build the loader, it is over 2 MB. You
> > have to strip
> > the
> > > loader:
> > >
> > > strip loader
> > >
> > > That should make it a manageable size.
> > >
> > > Forrest
> > >
> > > > -----Original Message-----
> > > > From: Brett Schwarz [mailto:brett_schwarz@xxxxxxxxx]
> > > > Sent: Monday, October 29, 2001 10:17 AM
> > > > To: kickstart-list@xxxxxxxxxx
> > > > Subject: Re: ks cdrom:
> > > >
> > > >
> > > > Actually, I would be interested to see that procedure to
> > add the new
> > > > loader patch. I tried to do it, but the loader executable was
> > > > larger than
> > > > the original, and I was getting "no space left on device"
> > > > errors when I
> > > > tried to copy the new loader to the initrd image.
> > > >
> > > > thanks,
> > > >
> > > > --brett
> > > >
> > > >
> > > > On Mon, 29 Oct 2001 09:52:37 -0800
> > > > "Taylor, ForrestX" <forrestx.taylor@xxxxxxxxx> wrote:
> > > >
> > > > > I haven't tried it in 7.2 yet. Did you want this for 7.1
> > > > or 7.2? The
> > > > fix I
> > > > > have is for 7.1. I haven't got around to testing it on
> > 7.2 yet.
> > > > Sometime
> > > > > this week...
> > > > >
> > > > > Forrest
> > > > >
> > > > > > That wasn't fixed in 7.2?? I thought that problem was around
> > > > > > since early
> > > > > > 7.1 ? If you could send those to me offline that
> > would be great.
> > > > > > *grumbles*
> > > > > >
> > > > > > Dan
> > > > > >
> > > > > >
> > > > > > On Fri, 26 Oct 2001, Taylor, ForrestX wrote:
> > > > > >
> > > > > > > You need an updated loader to put in the initrd. I
> > can give you
> > > > > > > instructions or just send it to you off-list.
> > > > > > >
> > > > > > > Forrest
> > > > > > >
> > > > > > > > I'm trying to do this:
> > > > > > > > kernel vmlinuz
> > > > > > > > append ks=cdrom:/misc/kickstart/server-ks.cfg
> > > > > > > > initrd=initrd.img lang= text devfs=nomount
> > > > > > > >
> > > > > > > > where on 7.1 and before I always put the server-ks.cfg in
> > > > > > tmp on the
> > > > > > > > initrd.img, but I'd like to maintain it outside of the
> > > > > > > > initrd.img. When
> > > > > > > > it boots it complains that it can't find
> > /tmp/ks.cfg. What
> > > > > > > > is it still
> > > > > > > > looking there and not where I told it ?
> > > > > > > >
> > > > > > > > Dan
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Kickstart-list mailing list
> > > > > Kickstart-list@xxxxxxxxxx
> > > > > https://listman.redhat.com/mailman/listinfo/kickstart-list
> > > >
> > > > _________________________________________________________
> > > > Do You Yahoo!?
> > > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Kickstart-list mailing list
> > > > Kickstart-list@xxxxxxxxxx
> > > > https://listman.redhat.com/mailman/listinfo/kickstart-list
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Kickstart-list mailing list
> > > Kickstart-list@xxxxxxxxxx
> > > https://listman.redhat.com/mailman/listinfo/kickstart-list
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://listman.redhat.com/mailman/listinfo/kickstart-list
> >
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
