Does this fstab look OK?

mouldy_punk · 09-28-2005, 11:06 AM

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hdc3       /               ext3    defaults,errors=remount-ro 0       1
/dev/hdc1	/mnt/C		ntfs	ro		0	0
/dev/hdc5       /mnt/D     	fat	defaults	0       0
/dev/hdc6	/mnt/E		ntfs	ro		0	0
/dev/hdc7       none            swap    sw              0       0
/dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/hdb        /media/cdrom1   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

Before I save and reboot, and probably mess up my computer - does that look OK? The only lines I added were:

Code:

/dev/hdc1	/mnt/C		ntfs	ro		0	0
/dev/hdc5       /mnt/D     	fat	defaults	0       0
/dev/hdc6	/mnt/E		ntfs	ro		0	0

/dev/hdc1 being an NTFS windows C drive
/dev/hdc5 being a FAT windows D drive
/dev/hdc6 being an NTFS windows E drive. Does that look OK?

bunnyrage · 09-28-2005, 11:12 AM

they dont have to line up, init, is your proccess that mounts all your hardware in your fstab file,

fstab reads in whitespace to separate fields, init knows what feild is which so spacing doesnt matter,

if you SWITCHED the feilds around, init would take a big poop on you

bunnyrage · 09-28-2005, 11:16 AM

sorry wasnt paying attention,

that works most of the time if you are adding entries maunally to your fstab,

ive had problems though, init would take that entry method sometimes

have the system enter those into fstab for you, because i think the system links them for init

i tried adding a HD as a slave manually, and init didnt recognize

mouldy_punk · 09-28-2005, 11:18 AM

Yeah I know, it's just easier to read by people if it's set out all nicely

Perhaps I worded it wrong - not if it looks OK, but is the actual text OK? Like, that configuration won't mess up my system or anything and it'll do what I'm expecting it to do, Eg, mount my C, D and E drives as /mnt/C /mnt/D and /mnt/E respectively?

What's this about init? You kinda lost me there xD

bunnyrage · 09-28-2005, 11:43 AM

init is short for initialization proccess

it is like the 2nd most powerfull proccess on unix

the first is called root

a proccess is just a daemon, a set of code that is executable by thr root proccess (the parent)
proccesses have PID's or proccess id's

root = pid 0
init = pid 1
pid's 2 - like 14 or 15
are all reserved for system proccesses that make the core run

root proccess is the kernel itself, the parent

the parents spawns child proccesses that do jobs in your system

try going to your terminal and type in the command "top"

this will list all active proccesses on you CPU in real time

do you understand, or is it still cryptic
no insults

just sharing info

bunnyrage · 09-28-2005, 11:49 AM

the entries in your fstab follow correct syntax,

abd its likley that unix will see the physical drive itself

but the information will not likely be accessable

like if you had a win sys file of word document, you wont be able to just mount it and get it,

your HD has a MBR that contains a file system type, linux can access foreign types like fat and ntfs, but not use them, do you understand,

you may be able to see files, but unix will say "this file system is speaking greek"
if you tell it to USE the file system.

it might want to see them a slave partitions.

Charred · 09-28-2005, 11:54 AM

You might want to throw the "user" option in so your users can access your Win partitions.

I've never had any problems adding partitions to my fstab, in fact the only problem I can forsee, other than crappy syntax, is if your kernel isn't configured to support the necessary filesystem.

bunnyrage · 09-28-2005, 12:15 PM

hey there you go, never messed with filesystems when configing the kernel

mouldy_punk · 09-28-2005, 12:46 PM

Quote:

Originally posted by bunnyrage
init is short for initialization proccess

it is like the 2nd most powerfull proccess on unix

the first is called root

a proccess is just a daemon, a set of code that is executable by thr root proccess (the parent)
proccesses have PID's or proccess id's

root = pid 0
init = pid 1
pid's 2 - like 14 or 15
are all reserved for system proccesses that make the core run

root proccess is the kernel itself, the parent

the parents spawns child proccesses that do jobs in your system

try going to your terminal and type in the command "top"

this will list all active proccesses on you CPU in real time

do you understand, or is it still cryptic
no insults

just sharing info

Thanks for clearing that up

Quote:

the entries in your fstab follow correct syntax,

That is mainly what I was hoping somebody would check for me, just to make sure.

Quote:

You might want to throw the "user" option in so your users can access your Win partitions.

Would that be along side default? Eg;

Code:

<snip> defaults, user <snip>

and

Code:

<snip> ro, user <snip>

Quote:

if your kernel isn't configured to support the necessary filesystem.

I think it does, I've had it working before - but I mesed up something pretty badly and had to start again. Same kernel though.

p_garg · 09-28-2005, 03:16 PM

no u added three lines, out of three, two r wrong. first thing, linux cannot read data from a partition formated with ntfs. It is able to read data from fat partition only. so do one thing delete the two lines of ntfs and third line keep as it is.

parveen

bunnyrage · 09-28-2005, 03:21 PM

if anything linux will be able to "see" those partitions but youll get errors

p_garg · 09-28-2005, 03:37 PM

no u cann't access the window partitions formated with ntfs. bcaz linux did not give this permission. there is no other tool with which u can access ntfs formated partition data.

parveen

mouldy_punk · 09-28-2005, 04:23 PM

I thought linux could read and write to NTFS - but writing to NTFS is too risky at the moment and will probably corrupt your data so they disabled it in the kernel. But as far as I'm aware, it can still read NTFS partitions?

mouldy_punk · 09-28-2005, 04:30 PM

ok, I just rebooted and it did mount the NTFS partitions, and they are readable

There is one problem though - I must be logged in as root to access them. How can I make it so that any user can access them?

Edit: Proof that they are readable - incase someone doesn't believe me :\ /mnt/C and /mnt/E are NTFS, /mnt/D is fat.

bunnyrage · 09-28-2005, 04:57 PM

chmod 777 /dev/hd*

i know you can access them but i dont know what good its going to do, who knows you may very weel be able to

chmod should change your permissions