SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i finished copy the unzipped folder of zipslack to hdd..
i run linux.. but it stop/hang, the error message I receive is:
UMSDOS_NOTIFY_CHANGE: Run/utemp not in EMD ret=-2
UMSDOS_NOTIFY_CHANGE: ETC/ioctl.save not in EMD. ret=-2
what should i do next??
FYI my pc spec is:
processor 100 mhz (i think..)
hdd 170 mb
memory 8 mb
You should unzip the zipslack.zip file directly to a FAT32 partition. You can't simply copy the stuff over to a Linux filesystem while it's mounted as a FAT. If you want to simply copy the files over, unmount the FAT partition (with the Linux folder) and remount it as as type umsdos (mount -t umsdos /dev/hd?? /your/mount-point). Or follow the ZipSlack FAQ and actually boot the system after unzipping and copy(migrate) it over to a Linux partition with whichever filesystem you plan to use.
u lost me there.. hehehe.. please note, this is my first time using linux.. =(
u r rite, i unzip the file using windows, and then i copy the files to cd and copy it to hdd..
what software to use to unzip the zip files to hdd (note: from cd).
cant do it on hdd, becoz of the low disk space.. i tried to put it as a slave with other pc, but xp can't recognize it.. dont know why..
btw, does zipslack have to be unzip to fat32 partition? coz, i think mine is fat16..
digiot: well, the pc is company's pc.. still works well.. can run win95 without trouble.. just playing with it now though, since it has no longer use... =P
The UMSDOS filesystem is kind of weird/tricky and I believe it's getting 'lost in translation' when you're doing a straight copy to ISO9660 CD and back to FAT.
As far as the unzipper, unless you're using a WinZip left over from Win3 or something, you're probably okay there. ZipSlack doesn't work from NTFS, but it works from any FAT. The 'display' option of DOS' fdisk will tell you what you've got, though.
And sure it has a use - an educational tool if nothing else.
Unzipping the zip file straight from CD is fine. Just be sure it's being unzipped onto a FAT -if it'S a 16 it will still work. I always had good luck with winzip ar ALzip. Once it is unzipped onto the FAT it is ready to run. This is the beauty of the umsdos file system it uses. Find the zipslack boot floppy image and burn it to a floppy using rawrite. Then use the floppy to boot the machine and mount the FAT/umsdos partition as the root partition.
As I mentioned, you can't simply copy the files from the FAT to some other place HDD, CD or whatever. Only when the FAT partition is mounted under linux using the umsdos file system are the files there 'valid' linux files. When you view the partition after unzipping and still mounted as FAT, you'll be able to see that every directory contains a sepcial file with a .--- suffix. These files are used by the umsdos file system to add the additional ownership and file permission attributes which are not available under FAT. When you mount the partition as umsdos you can't see these files at all.
ZipSlack uses the umsdosfs as the root partition. The kernel(2.4 series only), when directed to mount the FAT partition as umsdos looks for the folder called linux with a linux file/directory structure inside that. It hides the /linux subdirectory from the file paths so that the kernel (VFS)thinks that the subdir is the root(toplevel) of the partition. When you use umsdos as rootfs you don't see the /linux directory at all, but all other files and directories on the FAT not under the /linux directory are seen under a pseudo-directory called DOS which is created dynamically.
While possible, it is not a good idea to copy files into the /linux directory while running Windows. Better to copy them over under Linux when possible.
There used to be a cool 13MB umsdos system with GUI and lots of bins with an InstallShield Wizard installer. You could, under Windows 95/98 install and boot directly into Linux from your running windows desktop. I used to have a distro that did this also(the Kill Bill feature).