Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Originally posted by jdogg2001 I had the same problem. To fix it, just pass "nobiospnp" option to the kernel. If you boot with lilo, open /etc/lilo.conf, find the kernel you want to boot, and add the above option to the end of the line that says append="..., ..., ..., nobiospnp".
That should fix it. Hope it works. Later.
Yep. That did the trick. There's a note about this problem over at the Mandrake site on the Errata page.
Type: Block Device
Size: O B (0)
Points to: floppy/0
"Points to floppy/0"? is this a sym link? It should be the other way around, /dev/floppy should be a link to /dev/fd0
Properties for 0:
Type: Block Device
Size: O B (0)
This entry should be the link
Also, in the Control Center, in the area where the drives are, on the tab for removable drives, my cdrom and cdrw are there but there is no floppy drive. Shouldn't it be there with the other removable drives?
One its working it will be there.
You might want to try running the makedev script to recreate your floppy dev entries, see "man MAKEDEV" for the commands.
Ah yes...links, it helps if you think of hyperlinks but instead of html think of internal links on your computer. A hard link is between things in the same directory and a sym link can span directories....IIRC.
Because I put them there. You can only do a sym link or a hyperlink on the desktop...well you could do a hard link but it would have to be a link to something else on the desktop, so there would be not much point in it.
A hard link is between things in the same directory and a sym link can span directories
Actually, that's incorrect. A hard link can be anywhere on the same filesystem, not just in the same directory. It actually points to the same spot on the disk, so for all intents and purposes, it's the same as the origional file except with a different name. If the origional file is deleted, the hard link remains intact. With a sym[bolic] link, if the origional is deleted, you just have a broken link... the file (or directory) is gone.