permissions

Asked by Ian Brownlie

 Hello me again, my Azureus tells me I should update, when I do it says I do not have permission to write to "usr/share/azureus". It also says "you are not the owner". I am the only user on this computer and am certainly the owner. How on earth do I get past this to update. Another problem, when I tried to erase a file on my USB drive I get the same rubbish, "you are not the owner". I tried " sudo chmod 777 disk" then it tells me there is no such file or folder as "disk", when that is the name in the File system. Help me please, my computer doesn't wanna play.
     Ian

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Jim Hutchinson
Solved:
Last query:
Last reply:
Revision history for this message
Jim Hutchinson (jphutch) said :
#1

Changing permissions and owners is a good way to bork your system. In Linux there is a Root owner that is all powerful. You are not root and you shouldn't be. Being root all the time is a good way to bork your system too. However, you can become root temporarily. To do this you use sudo or gksudo (for gui apps). You will also be asked for your password when you install things. As the first user you have sudo rights and your user password is your sudo password. I don't use azureus so I don't know why it isn't updating properly (i.e. asking for your password). See https://help.ubuntu.com/community/RootSudo for more info.

Revision history for this message
Jim Hutchinson (jphutch) said :
#2

PS do NOT chmod or chown your whole system.

Revision history for this message
Ian Brownlie (ibrownlie) said :
#3

   Thanks for answering Jim, but this still doesn't help me erase my USB drive. I did it by borrowing a windows computer (oh! the shame). I would like to be able to do it myself. As for the Azureus thing, I guess the only other thing is to change bittorrent clients.
       Thanks, Ian

Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#4

Please insert your usb pen and please open a Terminal from the menu Applications->Accessories->Terminal and type:

sudo fdisk -l

give your user password when requested, you don't see nothing when you type it, then press enter.

Copy and paste result here.

Thank you

Revision history for this message
Ian Brownlie (ibrownlie) said :
#5

 Hi Marcoba I'm confused, what is the character at the end of statement.
         Ian

Revision history for this message
Jim Hutchinson (jphutch) said :
#6

Ian, it's a small letter L. It will output the device names and characteristics for the various drives including any USB drives connected.

Revision history for this message
Ian Brownlie (ibrownlie) said :
#7

Thanks again Jim,
 Here is the information you asked for Marcoba.
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x33f233f1

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 19269 154778211 83 Linux
/dev/sda2 19270 19457 1510110 5 Extended
/dev/sda5 19270 19457 1510078+ 82 Linux swap / Solaris

Disk /dev/sdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x34243423

   Device Boot Start End Blocks Id System
/dev/sdb1 1 4864 39070048+ 7 HPFS/NTFS

Disk /dev/sdc: 1014 MB, 1014497280 bytes
65 heads, 32 sectors/track, 952 cylinders
Units = cylinders of 2080 * 512 = 1064960 bytes
Disk identifier: 0xc3072e18

   Device Boot Start End Blocks Id System
/dev/sdc1 * 1 953 990704 6 FAT16
Partition 1 has different physical/logical endings:
     phys=(967, 64, 32) logical=(952, 39, 32)

   Hope this helps
 Ian

Revision history for this message
Best Jim Hutchinson (jphutch) said :
#8

Ian, not sure what marcobra has in mind, but any chance you used that flash drive in windows and didn't properly eject it? If so, try opening on windows again and then properly ejecting.

Revision history for this message
Ian Brownlie (ibrownlie) said :
#9

Thanks Jim Hutchinson, that solved my question.

Revision history for this message
Ian Brownlie (ibrownlie) said :
#10

 Thanks Jim, I used my mates windows computer again ( I'll never live it down) That fixed it.

Revision history for this message
Jim Hutchinson (jphutch) said :
#11

Well, just remind him that it was windows that broke it so naturally windows should have to fix it. It's only fair. Glad I could help.