You are not logged in.
Hi all,
I have subsonic media streaming running on a raspberry pi, which allows me to stream my music to anywhere I have internet. I would like to connect to it through mocp, but have been struggling, and not sure if it is possible anyway.
I've been trying to add raspi ip address, using sftp. Not sure if it would stream via sftp- I guess probably not.
Other ip combinations also seem to not work- or I just haven't been able to figure it out.
I think other people have network streams or folders up that mocp can access.
When I hit @ for the second fast directory I just get 'Fastdir2 not set'- but I am setting it in config.
Edit: Would Samba be the best way of going about this, then mounting the networked drive to /media or something?
Can anyone help me with this? How do others access networked drives through mocp?
Thanks 
Last edited by dura (2012-10-06 17:15:44)
Offline
Ok, so I'm working with cifs now.
I do not have an fstab file- something to do with Waldorf's growing strains I think
So when I try to mount the network drive I get this:
mount.cifs: permission denied: no match for /media/sharename found in /etc/fstab
Any idea how to remedy this anyone? I'm a bit unsure writing an fstab out- have only done that with raspi before, and this #! is my everyday computer (i.e. a production machine).
I guess I would have to write out the /dev/sda1 bits and everything else too......or do I?

Offline
Its not that hard at all. Depends on you having separate boot, root, home, usr partitions.
Post output of
df -ahplease.
That and the output of
sudo blkidshould make it possible to create your /etc/fstab.
bootinfoscript - emacs primer - I ♥ #!
Offline
Yay. Thanks!
$ df -ah
Filesystem Size Used Avail Use% Mounted on
rootfs 292G 8.5G 269G 4% /
sysfs 0 0 0 - /sys
proc 0 0 0 - /proc
udev 10M 0 10M 0% /dev
devpts 0 0 0 - /dev/pts
tmpfs 294M 900K 293M 1% /run
/dev/disk/by-uuid/fbbf929b-c8fd-4186-a7d8-df67ccac2972 292G 8.5G 269G 4% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 588M 84K 588M 1% /tmp
tmpfs 588M 272K 588M 1% /run/shm/dev/sda1: UUID="fbbf929b-c8fd-4186-a7d8-df67ccac2972" TYPE="ext4"
/dev/sda5: UUID="89d44e9f-5a3a-4c04-805e-ac6163f5651f" TYPE="swap" 
Offline
So, I'm getting this far on /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults 1 1
UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap swap defaults 0 0Last edited by dura (2012-10-06 18:55:45)
Offline
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=0ffd042d-d1b5-4d9b-a824-94d4d8ac22eb / ext4 noatime,nodiratime,commit=30,nobarrier,delalloc,errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=dc284d12-db35-4fe9-b2d9-a72c2d05070e none swap sw 0 0Here is an old version of mine - I am using LVM now, so that is a little bit different.
The mount options for the root device is for optimizing purposes. And I dont really need atime for anything... ymmv
hope this helps 
bootinfoscript - emacs primer - I ♥ #!
Offline
Thanks again xaos52
# <file system> <dir> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults 1 1
UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap swap defaults 0 0 Once I'm a bit more certain of my fstab writing capabilities, and have woken up a bit, I will probably use this one above. I copied it from the debian wiki, and from xaos52 above. I think everything is in order.
Is there risk here? If I get fstab wrong might I expect some nasty roblems after rebooting?

Last edited by dura (2012-10-07 10:21:11)
Offline
On the 'swap' line change the second 'swap' to 'sw'.
The rest looks OK.
Is there risk here? If I get fstab wrong might I expect some nasty roblems after rebooting?
A 'mild' risk.
Nothing that cant be cured if you are able to boot from live media.
bootinfoscript - emacs primer - I ♥ #!
Offline
On the 'swap' line change the second 'swap' to 'sw'.
The rest looks OK.Is there risk here? If I get fstab wrong might I expect some nasty roblems after rebooting?
A 'mild' risk.
Nothing that cant be cured if you are able to boot from live media.
Thanks. I'm guessing just deleting /etc/fstab using a live usb, and thus returning it to its original state (no /etc/fstab) would be the solution if anything went wrong.

Last edited by dura (2012-10-07 12:49:01)
Offline
Thanks again xaos52
# <file system> <dir> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults 1 1 UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap swap defaults 0 0
This:
proc /proc proc defaults 0 0
UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults,noatime,errors=remount-ro 0 1
UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap swap defaults 0 0 is what you want, trust me. atime is the biggest slowdown in an ext4 filesystem. We can set your cifs share to mount later.
Last edited by el_koraco (2012-10-07 13:05:16)
Offline
Thanks el koraco
proc /proc proc defaults 0 0
UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults,noatime,errors=remount-ro 0 1
UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap swap defaults 0 0 or
proc /proc proc defaults 0 0
UUID=fbbf929b-c8fd-4186-a7d8-df67ccac2972 / ext4 defaults,noatime,errors=remount-ro 0 1
UUID=89d44e9f-5a3a-4c04-805e-ac6163f5651f swap sw defaults 0 0 In the second I have changed swap to sw, as xaos52 suggested. It doesn't say that is necessary on the debian wiki, but it is the Good Doctor's word afterall...
Also, could you explain el koraco why you have changed the numbers, from 1 0 to 0 1 please?
I know its pretty lame having you guys hold my hand with this, but I need to work on this thing tomorrow morning!
Last edited by dura (2012-10-07 16:38:17)
Offline
The 0 number refers to the dump utility, which does filesystem backups for etx2 and ext3 filesystems. It is unnecessary for ext4 filesystems, it isn't even installed by default, and hence you don't need it referenced in fstab. It doesn't hurt though.
Offline
You Sir, are a star.
And the swap or sw thing?

Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.