ZipSlack


Recommended Posts

I installed Slackware via its ZipSlack option onto my FAT32 partition. (WinXP's built-in extractor) Worked fine the first few times.

After downloading a few packages, I would boot into Linux and the downloaded packages would have strange names

like gcc#.$00 rather than their standard names. Why did this happen? So of course pkgtool couldn't recognize...

I deleted the installation, then went back and extracted again (always using WinXP's built in extactor)

Afterwards, the kernel went into a panic. I had edited the loadlin.bat each time, the same way as before.

Do I download ZipSlack again, or chuck it altogether? I really like Slackware, and want a small distro I can 'see' from Windows.

Answers/suggestions appreciated!

Link to comment
Share on other sites

rem list was not commented out appopriately! (ah, the basics)

still unsure about the wacky file names, though.

why would it show as 'linux-2.6.#.$00' rather than 'linux-2.6.3.tar.bz2', for example?

Link to comment
Share on other sites

Thats just how the umsdos filesystem driver works. It should not show up as that under Linux however. It will also create permission files called --linux-.--- in each directory.

Link to comment
Share on other sites

it does show up this way in linux, actually. boot header says something about 'can't synchronize files', 'renaming to gcc-3~/.tgz to gcc#-$00.' in other words, file names are originally too long, but they are the standard names, so i'm not sure why it has to rename them.

in any case, i've ditched zipslack for the topologi version - much less headache.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.