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.
As I wrote to MasterC, PartitionMagic refuses to allow me to "unhide" that partition (drive). I do not know if this behavior is a "bug or a feature" and PowerQuest ignores most e-mail sent to its support staff. (They apologize to me and promise that it won't happen again -- every time that I complain.)
Thanks for the alternative method, whansard:
> fdisk /dev/hde
> i think
The last line of your suggestion ("I think") causes me minor concern, although you are obviously the expert. How confident is your "I think," whansard?
Incidentally, as I told MasterC, Win2k Pro can "see" the partition (drive), but then I have PartitionMagic, Drive Image, and BootMagic installed under Windows 2000 Pro. (Windows XP Pro cannot see that drive.)
Originally posted by whansard i didn't want to post cause my number of posts was
1337, and i wanted to leave it that way for a few days,
but i can't take it. i have to answer.
partition magic makes primary partitions of that type,
cause microsoft says there can't be more than 1
primary partition on a computer. when you make a
primary, it makes it hidden, then you have to unhide it.
the type 1c is just a partition entry that will be ignored by
windows. PM has another menu entry that says,
"unhide partition", but the easy way is just to use
and that changes your type 1c partition to c, which is
a normal fat32.
you would have been able to mount the partition in
linux with it either way, but you wouldn't be able to view
the partition in windows the way it is.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
you just use fdisk to change the type of the partition
from 1c to c, i was trying to remember the exact steps,
but trying to do that type of stuff is often where i make
a mistake when i'm not actually doing it. you know, like
giving somebody directions to your house, and you say
third stopsign or something, but you forgot one of the
start fdisk on the drive
and change the type of the partition from 1c to c.
save and exit.
Thank you for the tip on cleaning out '/tmp'/. I will exercise due care!
The hidden attribute is a function of PartitionMagic. I have a primary and a logical partition on '/dev/hda'. The primary partition contains Win2k Pro, and the PowerQuest utilities, and it can "see" '/dev/hde'; I run my backups from Win2k Pro.
The secondary partition contains WinXP Pro, which cannot "see" '/dev/hde', although I have repeatedly deselected the hidden attribute in PartitionMagic so that WinXP Pro can access it -- a capability that I want very much, but which PartitionMagic denies, for a good reason, I assume.
> ...that $ on the end of your fstab line, remove that....
When I installed SuSE Linux 8.2 Professional, MasterC, it set up 'fstab' as I have shared it in this thread, with the dollar sign. I do not know why the dollar sign is there, but I assume that SuSE had a reason for having YaST2 set up 'fstab' in that particular manner.
How critical is it that I make that change? Are you suggesting that I make it for all of 'fstab' or just the line for '/dev/hde'? I realize, of course, that distribution-specific utilities are far from perfect, but SuSE Linux has been rock solid with this exact 'fstab' configuration.
My experience has shown that a $ is usually a place holder for either user or a defined function elsewhere. So if you have $ defined as your dump/fsck (I'll discuss below) then it's certainly fine to leave it there. Also, if it's been working so far with that option, there is certainly no need to change it, "If it ain't broke, why's MasterC tryin to fix it"
Finally, MasterC, what is the signifigance of the two zeros separated by a space? What exactly do the two zeros mean? Do you happen to know what the dollar sign means in my current 'fstab', MasterC?
The dollar sign I discussed above, but being not-too-familiar with it's use in fstab ( I don't recall it being present in my 8.0 setup of SuSE ) I really can't comment on it too much. If you can post up your entire fstab there might be clues within it that someone here can speak intelligently about.
The 2 zeros:
The first one (also known as the fifth field in fstab) is your dump number. Basically, if a zero is there, then it will be assumed this filesystem does not need to be dumped. For more information on dump (it's sort of a backup function of the ext2 filesystem...) see the man page (oh and btw, just read the fstab man page, you do not need this number, if it's not present a zero is assumed )
The second zero:
This is the fsck number. Again, a number need not be present, if there is not one, a zero is assumed and fsck will not be done in this drive (such might be the case with NTFS drives or fat32). This is the order with which to process fsck on boot up (initial mounting). So the root partition ( / ) should have a 1 here, meaning process this one first, then the other partitions (with linux filesystems) should have 2's saying to check them next (and it will check them parallel-ly (word?). fsck is the drive checker, similar to scandisk in windoze.
I apologize for the additional questions, but I am truly a Linux neophyte ("newbie") and I am extremely cautious.