Samba Shares

[Kevintimm]

the samba shares on the sage seem to have write protection on. is there a way to turn this off so i can use showanayler from a different comp?

[laurenglenn]

Originally Posted by Kevintimm

the samba shares on the sage seem to have write protection on. is there a way to turn this off so i can use showanayler from a different comp?

Add this line to the startsage file (near the other chmod commands):
chmod 777 /var/media/tv

I noticed that all the other directories have write permissions on, so hopefully this command should work too.

Lauren

[Kevintimm]

i'm really new to linux. could you tell me which file that is and do i type nano to edit it? i only have a prompt to work with and i dont know then commands.
thanks

[laurenglenn]

Originally Posted by Kevintimm

i'm really new to linux. could you tell me which file that is and do i type nano to edit it? i only have a prompt to work with and i dont know then commands.
thanks

No problem.

cd /opt/sagetv/app
nano startsage

(now use the text editor there)

Control-X exits... It should say something along the lines of "do you want to save?" type Y, hit ENTER on the filename.

Start SageTV up with "./startsage" and see if it works.

Lauren

[Kevintimm]

thanks for your instructions but unfortunately i couldnt get it to work. i added the chmod command to the startsage by all the others but i still can't write to the share. is there anything else that could be causing this problem? just to note i can write to the other shares just fine. its only the tv folder

[cbhatt]

Hi,
I encountered the same problem, I can't write to the TV directory. Running chmod changes the gentoo permissions but not the samba permissions. To edit the samba permissions:

1- log in as root
2- type 'cd /etc/samba' and then 'nano smb.conf' (without quotes)
3- look for the [TV] line
4- under that line is the block for the TV share
5- change the attribute "writtable = no" to "writtable = yes"
6- hit ctrl - x, save, and exit
7- reboot the box by typing 'reboot'
8- you should be good to go

let me know how it turns out.

[sulphurlad]

why the hell would you want SMB. I just bought The linux version, and I can't believe how crippled it is. Not Sage mind you, but Linux.

On the install, when the fstab was up, I was like cool, edited it, and added my storage servers NFS export volumes, and saved. After the initial boot for activation, I saw the error about no mount point, no problem , mkdir /mnt/media, then tried to - mount /mnt/media, I get an RCP error. HUH? A Remote Procedure Call error on Linux?

Then I tried to emerge --sync , emerge --update world , emerge nfs, and I get an error about not having the kernel config. What the hell, I'm not a newb to linux, but I'm new to Gentoo.

So is there away to mount NFS shares, not SMB? I'm Fleeing M$, I run Mac's and Linux, and NFS is way better, scales better, and doesn't freak out during a large file transfer.

[AboveUnrefined]

Most people want to deal with samba because it's easier to deal with if you're on Windows. NFS is probably better but it's not native for the common environment, though I can't see why you couldn't tweak it out for this to work with NFS instead of SMB.

[Dekard]

Originally Posted by cbhatt

Hi,
I encountered the same problem, I can't write to the TV directory. Running chmod changes the gentoo permissions but not the samba permissions. To edit the samba permissions:

1- log in as root
2- type 'cd /etc/samba' and then 'nano smb.conf' (without quotes)
3- look for the [TV] line
4- under that line is the block for the TV share
5- change the attribute "writtable = no" to "writtable = yes"
6- hit ctrl - x, save, and exit
7- reboot the box by typing 'reboot'
8- you should be good to go

let me know how it turns out.

I tried exactly this and no success. Anything else needed?

[Dekard]

Originally Posted by laurenglenn

Add this line to the startsage file (near the other chmod commands):
chmod 777 /var/media/tv

I noticed that all the other directories have write permissions on, so hopefully this command should work too.

Lauren

this seems to have worked in combination with setting writeable to yes from smb.conf