my 2.064 experience: telnet, twonky

Post Reply
jezzo
Posts: 4
Joined: Thu Sep 02, 2010 11:32 am

my 2.064 experience: telnet, twonky

Post by jezzo » Thu Sep 02, 2010 12:12 pm

Hi,

Thanks to NAS-Central, Mijzelf and everyone for a great wiki/forum.

As I am running 2.064 had to do a manual telnet did a few thing a little different.

Telnet:

For the telnet password (/etc/passwd) to work I removed "/" at the end of the password:
root:$1$$goRzr7Z2nQvrAoiRJGUhr:0:0:root:/root:/bin/bash

btw: The password didn't work the first time for me, so I used the web frontend to set the password for the 'nascentral' account then I copied it to the root.

For the shadow password (/etc/shadow) added a '*' to match the others:
nascentral:*:14517:0:99999:7:::

Modifying twonky:
Copied of the ini in the default location (/usr/local/TwonkyVision)
Modified the ini with enableweb=2, change the file name to twonkyvision-mediaserver-fixed.ini
Modified the /etc/init.d/twonky
INIFILE="${WORKDIR}/twonkyvision-mediaserver-fixed.ini"

Outstanding:
* resolve issues with my ps3 to read the files correctly via the twonky (upgrade?)
* investigate adding NFS to NAS
* upgrade of twonkymedia server to version 6?
* upload throughput\data rate is 8-10MB/sec

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: my 2.064 experience: telnet, twonky

Post by Mijzelf » Thu Sep 02, 2010 12:37 pm

As I am running 2.064 had to do a manual telnet
Did you get your box with 2.064 on it, or didn't you install telnet the easy way when you had the chance? Anyway, I'll look if I can provide a 'telnet enabling' update which works with 2.064
* investigate adding NFS to NAS
Haven't tested it yet, but I *think* you can enable apt, install nfsd server

Code: Select all

apt-get install nfs-kernel-server nfs-common portmap
and use the kernel modules nfsd.ko and exportfs.ko from my modules tarball.

jezzo
Posts: 4
Joined: Thu Sep 02, 2010 11:32 am

Re: my 2.064 experience: telnet, twonky

Post by jezzo » Sat Sep 04, 2010 1:00 am

Hi,

My device start with 2.040, i upgrade to 2.064 in a attempt to fix my ps3 issue & before find nas-central.
Thanks for the NFS details, I will give it a go and report back.
-----

I did some damage to my device and had to rollback.
People if you get a chance while the device is connected to your linux box, perform a backup using dd or pcopy of the Linux partition (sdc1 for me).
-----
For the telnet password (/etc/passwd) to work I removed "/" at the end of the password:
Going to take back my telnet password issue, must of been me. The second time I did it it all worked. Still leaving the shadow password in place to see the impact.
-----

Investigating mediatomb (http://mediatomb.cc) instead of twonky as my media server. will test and report back.

mediatomb-common: The main package consisting of the MediaTomb binary and all files necessary to run MediaTomb from the command line as a regular user. The other packages depend on this package, so it is needed in all cases.
mediatomb-daemon: This package has additional files to allow MediaTomb to start as a daemon at startup. Use this package if you want to run MediaTomb at boot time.

PS3 needs in config.xml <protocolInfo extend="yes"/>

DO NOT install the "mediatomb" package... bad things will happen :cry:

jezzo
Posts: 4
Joined: Thu Sep 02, 2010 11:32 am

Re: my 2.064 experience: telnet, twonky

Post by jezzo » Sat Sep 04, 2010 2:25 am

Hi Mijzelf

I attempted to extract the modules nfsd.ko and exportfs.ko from the modules tarball.
I received this error..

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors

could you re upload them?

cheers
jezzo

jezzo
Posts: 4
Joined: Thu Sep 02, 2010 11:32 am

Re: my 2.064 experience: telnet, twonky

Post by jezzo » Sat Sep 04, 2010 3:38 am

Managed to get access the modules.tgz
used the archive mounter in ubuntu to gain access to the files :-)

Mediatomb installed and up, letting it do a index of the files.

more info to follow.

cheers

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: my 2.064 experience: telnet, twonky

Post by Mijzelf » Sat Sep 04, 2010 8:51 am

jezzo wrote:Managed to get access the modules.tgzused the archive mounter in ubuntu to gain access to the files
The file is bzip2'ed and not gzipped. I renamed the tarball to reflect that status.

hptasins
Posts: 3
Joined: Wed Dec 07, 2011 5:13 am

Re: my 2.064 experience: telnet, twonky

Post by hptasins » Wed Dec 07, 2011 11:59 pm

Was there ever any success enabling NFS using these modules on 2.064? I unpacked the modules and tried loading nfsd but end up with some unresolved symbols that I can't track down:

# insmod kernel/fs/exportfs/exportfs.ko
# insmod kernel/net/sunrpc/sunrpc.ko
# insmod kernel/fs/lockd/lockd.ko
# insmod kernel/net/sunrpc/auth_gss/auth_rpcgss.ko
# insmod kernel/fs/nfsd/nfsd.ko
# dmesg | grep nfsd
nfsd: Unknown symbol posix_acl_from_mode
nfsd: Unknown symbol posix_acl_from_xattr
nfsd: Unknown symbol posix_acl_valid
nfsd: Unknown symbol posix_acl_alloc
nfsd: Unknown symbol posix_acl_to_xattr

Would it be possible to build a loadable module (e.g. posix_acl.ko) to provide these functions? Or is replacing the kernel as described in the NFS twiki the only solution?

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: my 2.064 experience: telnet, twonky

Post by Mijzelf » Thu Dec 08, 2011 10:43 am

From the wiki:
Wiki wrote:To get a nfs server running you'll need kernel support. The stock kernel isn't able to load the needed modules,

Post Reply