Hi, hope someone can help with this:
I was looking for a small install since Im fairly new to linux and also on a slow net connection, so I d/led zipslack and followed the instructions for installing to HD.

First problem: when I tried to boot it gave error that there was no ReiserFS, which was strange because I thought Zipslack was for fat/fat32?

Anyway I made a Reiser partition and copied all files to that using a Damn Small Linux CD.

2nd problem: Booting gets further now, but stops with kernel panic about not find init, try passing init= to kernel

This is where I am now. After searching forum I found there should be /etc/inittab file, so I opened it and found these lines:

# System initialization (runs when system boots).
si:S:sysinit:/etc/rc.d/rc.S

but I dont have a rc.S file. Though I do have a file called rc_s.{_5 which I opened and reads:

#!/bin/sh
#
# /etc/rc.d/rc.S: System initialization script.

at the top.

So do I have some problems with filenames being wrong (I have a lot with {xx extension ) ? Or are there meant to be named like this??

Any help would be great

In order to get help, you must give more information. For example, what version of Zipslack are you using?

When You say 'installing to HD' do you mean just unzipping the ZIPSLACK.ZIP file to your windows (or DOS) partition, or are you talking about moving the system to a native partition? You should have followed the directions at these two links:

http://www.slackware.com/zipslack/install.php

http://www.slackware.com/zipslack/booting.php

What method are you using to boot? Linux.bat? Loadlin command? Or boot disk?

What is the exact error message that you get when you boot?

As to the file names, you cannot just copy the file system to a ReiserFS partition because those funny names are used by the loopback system that zipslack employs, and if you aren't booting into a loopback filesystem it won't find any of the files.

Give us some more info.

Enjoy!
--- Cerbere

ZipSlack 9.0
Trying to boot with SlackWare boot floppy

First error was (from badly scribbled notes):

read_super_block: cant find ReiserFS Filesystem on (dev 03:05, block 64, size 1024)
Kernel Panic: VFS: mount root fs on 03:05

After making ReiserFS partition error is:

Warning: unable to open an initial console
Kernel Panic: No init found. Try passing init= option to kernel


Is the loopback system very different to 'normal' slackware and other linux distros? How would it affect things if I want to install packages later on?

I think you should give up on the Reiser partition for now. If you are trying to boot into that in ro (read-only) mode, it just won't work because of the filenames. For the present, just stick with your FAT partition.

What OS are you running (other than Linux)? If you can boot into DOS, then you should try the loadlin or linux.bat methods of booting.

What kernel are you using for the boot disk? And what command are you passing on the 'boot:' prompt? Should be similar to:

mount root=/dev/hda1 rw

Notice the 'rw' this is very important for the UMSDOS loopback.

Sorry to keep answering your questions with questions, but it's part of the process of narrowing down your problem.

The loopback system is slower than the 'normal' linux filesystems, but it's a good way to try out Slack and if you like, later on you can transfer it to another filesystem (even Reiser). You can still add normal slack packages, they'll just have their names translated similar to those you've seen. When you're booted into the loopback system however they'll appear normal.

Enjoy!
--- Cerbere

[edit] Also, what partition is DOS (the one you initially had Zipslack on)? The error you get shows that you're trying to mount it on /dev/hda5, which may be incorrect. [/edit]

Win2K Pro SP4 is what Im running atm, but I have a 98 boot CD I made some time ago with full DOS on it.

I was booting in rw mode in DOS with LoadLin = didnt work
so I reformatted in Reiser and been trying booting in ro
which also didnt work. I will try again in rw

My Zipslack partition is actually hda9 I discovered later. But it came up with same error messages.

Ive been thinking about d/ling the bare minimum of normal Slackware and trying to boot up with that.
I would rather have a more normal install than this loopback system since Ive used linux enough now to know that I would find it useful, and would want to expand it in the future

hi!!
i am having the same problem.
i downloaded zipslack from slackware 8.1.
i used winzip to unzip it to my e:\ directory.
as stated it installed everything in e:\linux
i edited linux.bat to say: loadlin root=/dev/hdb5(my e:\ directory) rw
i reboot windows to dos mode (or boot a dos6 partition)
i cd to e:\linux
i command linux
it starts to boot
it ends up saying "can't find reiser fs(whuy is the xxxxx thing even looking for a reiser fs when it is supposed to be on a fat16 partition?????)
then last statement is
kernel panic can't find root i could scream)
then to exit this condition i have to cold boot, the usual result of a kernel panic
help didn't some one test this system??
should i move every thing to e:\ instead of e:\linux?
help!
jjwilkman

new observation:
i just finished (finnished?, i'm a finn) doing the same thing with zipslack fron 7.1. it works as advertized, flies like a kite.
so.... what is the difference? what is wrong. i can't believe that no one from slackware.com test flew the installation process..,.
i'm becoming a firm believer that just get the minimum that will do what you want. the only reason i went to 8.1 is to get support for my conexant hsf winmodem. i think it would be better to invest in an external 56k modem and be done with it forever.
just my thoughts and if i helped solve this situacion, better
thanks
jeffrey j wilkman