I removed all partition of an IDE HD mounted as slave in the disk controller and formatted it as extf3 in one single partition(I used Mandriva Control Center to do the operations)

Everything seems to be find, but my user can't write in the new created partition. It appears a directory "LOST+FOUND" and nothing more.

What can I do to turn the new partition available to write as non-superuser user? Must I create a swap partition? I can't understand why the new disk although mounted is not available for normal I/O operations.

Additional question: How can I set a name for my new partition? I've tried with partition magic under windows but it doesn't recognize the partition. If I try with Mandriva Control Center, it corrupts the /etc/fstab file. I think there is a bug in the Mandriva Control Center.

Greetings from Sao Paulo - Brazil

Ricardo

What is the output of
fdisk -l
mount
and an ls -l of the parent directory of the
mount-point of the new hdd.



Cheers,
Tink

Here we go:


What is the output of
fdisk -l
==================================================
[root@localhost ricardo]# fdisk -l

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes

Dispositivo Boot Start End Blocks Id System
/dev/hda1 * 1 6119 49150836 7 HPFS ou NTFS
/dev/hda2 6120 6377 2072385 f W95 Ext'd (LBA)
/dev/hda3 6378 17851 92164905 83 Linux
/dev/hda4 17852 19457 12900195 c W95 FAT32 (LBA)
/dev/hda5 6120 6377 2072353+ 82 Linux swap / Solaris

Disk /dev/hdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes

Dispositivo Boot Start End Blocks Id System
/dev/hdb1 * 1 4866 39082648+ 83 Linux
[root@localhost ricardo]#
===================================================
mount
===================================================
[root@localhost ricardo]# mount
/dev/hda3 on / type ext3 (rw)
none on /proc type proc (rw)
/dev/hdb1 on /mnt/dsk40GB type ext3 (rw)
none on /mnt/floppy type supermount (rw,sync,dev=/dev/fd0,fs=ext2:vfat,--)
/dev/hda1 on /mnt/win_c type ntfs (ro,umask=0,nls=utf8)
/dev/hda4 on /mnt/win_d type vfat (rw,umask=0,iocharset=utf8)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
[root@localhost ricardo]#
===================================================
and an ls -l of the parent directory of the
mount-point of the new hdd.
===================================================
[root@localhost ricardo]# cd /mnt/dsk40GB
[root@localhost dsk40GB]# ls -l
total 16
drwx-w--w- 2 root root 16384 Fev 28 16:21 lost+found/
[root@localhost dsk40GB]#
===================================================

What are the permissions for /mnt/dsk40GB ?

Edit - sorry, this was Tinkster' last question. You actually need

ls -l /mnt

[root@localhost dsk40GB]# ls -l /mnt
total 23
drwxr-xr-x 2 root root 1024 Fev 24 05:50 cdrom/
drwxr-xr-x 2 root root 1024 Fev 24 05:50 cdrom2/
drwxr-xr-x 3 root root 4096 Fev 28 16:21 dsk40GB/
drwxrwxrwx 0 root root 0 Fev 28 16:28 floppy/
dr-xr-xr-x 1 root root 8192 Fev 28 10:02 win_c/
drwxr-xr-x 2 root root 1024 Fev 24 05:49 win_c2/
drwxrwxrwx 4 root root 8192 Dez 31 1969 win_d/
[root@localhost dsk40GB]#

I saw the light:

[root@localhost mnt]# chmod a+w dsk40GB
[root@localhost mnt]# ls -l /mnt
total 23
drwxr-xr-x 2 root root 1024 Fev 24 05:50 cdrom/
drwxr-xr-x 2 root root 1024 Fev 24 05:50 cdrom2/
drwxrwxrwx3 root root 4096 Fev 28 16:21 dsk40GB/
drwxrwxrwx 0 root root 0 Fev 28 16:28 floppy/
dr-xr-xr-x 1 root root 8192 Fev 28 10:02 win_c/
drwxr-xr-x 2 root root 1024 Fev 24 05:49 win_c2/
drwxrwxrwx 4 root root 8192 Dez 31 1969 win_d/
[root@localhost mnt]#

Congratulations!

That's ONLY sane if you're the only user on the system
or trust everyone not to stuff up ...



Cheers,
Tink

May you develop please? Suppose I don't trust or I'm not the only one in the system. Let me learn a little bit more. Let me catch the idea, please

Well .. write access to the whole directory means that anyone could
delete stuff underneath it. Also anyone can read everything - if you
have documents or files stored there that you consider private the
pre-existing global read/execute permissions are too permissive, too.


Cheers,
Tink

Thank you very much. By this time I'm the only user. But I know about root/group/user permissions.

Cheers

Ricardo