Baslinux mailing list

[andy AT andyashbaugh.com]

Steven:
     Thanks for the response! Yes, go is in my /usr/lib/setup directory. When 
I
run setup, it just gives me that "File not found" error and returns me to the
command prompt, so you are correct in stating that go is not executing. Any
ideas why?
      Could the fact that the slakware packages reside on a mounted Linux
partition be the problem? It seemed silly to create a boot partition for DOS
when I want this strictly as a Linux box, so I just created and formatted my
four linux partitions, mounted the bootable one as /hd, stored the Slakware
packages and directory structure on a different partition mounted as /cd, and
assumed that install would copy the kernel to the /hd directory without a
hitch. I woundn't think that storing the Slakware packages on a DOS file
structure would offer significant advantages over a native linux stucture. Am 
I
misunderstanding something?

Andy


Quoting 3aoo-cvfd AT dea.spamcon.org:

> Andy Ashbaugh wrote:
> >
> > I'm trying to install BL2 on an old 75 Mhz processor
> > I've successfully partitioned the hard drive into four linux file
> > systems (one for boot, one for swap) and formatted them with mke2fs.
>
> Make the first partition a (bootable) DOS partition.  Boot the
> BL2 ramdisk from there.
>
> > I copied the necessary Slakware packages into tmp from floppy
> > disks.
>
> Put the packages in C:\slakware (on the DOS partition).
>
> > gunzip: go.gz: No such file or directory
>
> go.gz is in /usr/lib/setup.  The first time you run the install
> routine, it unzips go.gz (and the name changes to go).  The
> second time run the install routine, go.gz is no longer there
> so get the error message.  But you shouldn't see that error message.
> Immediately thereafter the install routine should launch (and clear
> the screen).  So if you see the error message about go.gz, it means
> go itself is not launching.  Do you have go in /usr/lib/setup?
>
> Cheers,
> Steven
>