i need help with the following:

* automount all disks in their proper name
* autodetect soundcard (alsa installed and working)
* autologin as root


this is for a gaming project geared for DOS/windows users.

I'd suggest that you make a new thread for each question you have and don't put zipslack in the title. Not very many people use zipslack anymore, so when they see that they will ignore your thread. All three of your questions will have pretty much the same answer, no matter what version of slackware you are using -just say that you are usng slack-11.0.

I'd also like to add that we're really big fans of things like;

1. Output from some commands showing the problem you're having.

2. In the case of hardware, output from "lspci", "lsusb" or "dmesg" that shows the hardware info.

3. Regarding Security, the reason why you'd want to do something like "autologin as root".

Because, you know, like, we're not exactly dealing with Windows here.

Kisses!

thank you. i have been trying to search the forums but have not really come up with the answer i needed. my goal is a portable zipslack on a usbdisk that can be use on different computers. i'll post on different threads after a few more searches.


i'm assuming this is regarding automounting disks. i can follow linux commands, so far, i just need to know the correct one for the job. i want my setup to make the disks readily accessible and enumerated with the correct mountpoint name.


i've managed to install the alsa packages and it's working for my setup. i need now to force re-detection and automatic enabling of audio drivers for when i move the usbdisk to a different pc.


for now, root is the hassle-free way of configuring the setup. when everything is finalized i will add a default user. i still don't know how to manage users and groups in linux.

i've managed to put "su" or "su - root" in /etc/rc.d/rc.local. the first one seems to skip the final few steps of the boot process and dumps me in the "bash-3.x" prompt. the second one gives me "no job control in this shell" message. i have no idea what it means and it has me worried. i would prefer a no-compile solution.

What you are trying to do is a pretty advanced task -but certainly not impossible if you are willing to learn and have the patience. Some years ago I created a system nearly exactly what you describe.
You need to devise a way so that the first time (or any time) the system boots, that it will discover the hardware present and set it up. It helps that you are concentrating on just mounting disks and getting sound working. The best way forward is for you to examine and learn from (or copy from), systems that already do some or all of what you want. This mostly means studying the way LiveCD's boot and run. You might have a look at the old Slackware liveCD (cd #2) from older versions of slackware -I don't remember when it was dropped, but I am sure that slack-9.1 still had it. As an example of a way to do things, it serves as well as any, but the slack LiveCD is quite different from most others in the way it works.
zipslack actually serves as an excellent base to start from for several reasons. All liveCD's use an initrd which does some heavy lifting before turning the boot process over to the 'normal' init scripts. You might wish to encapsulate some of the first steps into a custom initrd as it makes it less necessaryr to alter the normal init scripts.

I'd try using 'blkid' to discover the disks on the system -then loop through them creating fstab entries for each one.
BTW, there is no need to su to root from rc.local -all the init scripts are already running as root.