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.
I saw a SCSI disk, but nothing was attached to it. Restarting did recognize the stick, and the desktop sees it as Hard Disk Partition uba1, /deb/uba1 at /mnt/uba1.
After making it as writable as possible, I was able to save folders to it. However, W*doze didn't see the content. So, I went back to square 2 and formatted the stick to FAT32.
After returning it to the laptop, I'm copying content again; it's populating as I type.
However, I know they'll have to read this in W*doze. Should I be formatting the stick with a dual-compatible OS, or can I find an applet which they can install on their new MS machine to read the files from the stick?
Thanks; the reason I believe uba1 is the stick is that I can see the text file that I had copied to it in W*doze after formatting the stick to FAT32. I'm not on the machine now, but I'm pretty sure that the hard drive was listed as hda1.
When I open uba1, the W*doze text file shows up in its apparent root (/mnt/uba1/New Text Document.txt), while all the documents I think I copied to it in knoppix show up on uba1's desktop - but only in knoppix.
I'm either confused, or I'm confused and missing something. Where should I see those files, and why can't I put them on the root of uba1?
/dev/root on / type ext2 (rw)
/dev/hdb on /cdrom type iso9660 (ro)
/dev/cloop on /KNOPPIX type iso9660 (ro)
/ramdisk on /ramdisk type tmpfs (rw,size=401524k)
/UNIONFS on /UNIONFS type unionfs (rw,noatime,dirs=/ramdisk=rw:/KNOPPIX=ro)
/UNIONFS/dev/pts on /UNIONFS/dev/pts type devpts (rw)
/proc/bus/usb on /proc/bus/usb type usbfs (rw,devmode=0666)
automount(pid2309) on /mnt/auto type autofs (rw,fd=4,pgrp=2309,minproto=2,maxproto=4)
/UNIONFS/dev/uba1 on /mnt/uba1 type vfat (ro,nosuid,nodev,umask=000,uid=1000,gid=1000)
If I read this right, it claims that the fat volume on uba1 is read-only, even though I set its permissions as open as possible. User knoppix is owner, in knoppix group. I just created a text file on the desktop, and it won't copy to the /mnt/uba1 volume.
Aha! The context menu has Actions! The volume has a read/write lock! We've got it!
Unmount... Connect to XP... Voila - copied files are visible! We are in business! Thank you so much for leading me through Lesson One!