Has anyone managed to get any network file systems to mount on the firetv?
I've tried nfs (no nfs module), smb (no cifs module) and even sshfs (no fuse). I would like to connect to my home NAS and would rather mount directly then having to sync with the file system.
Ebrius said:
Has anyone managed to get any network file systems to mount on the firetv?
I've tried nfs (no nfs module), smb (no cifs module) and even sshfs (no fuse). I would like to connect to my home NAS and would rather mount directly then having to sync with the file system.
Click to expand...
Click to collapse
I'm using smb shares coming off a synology in xbmc without any problem, but haven't tried it at the ftv OS level.
I forget the command but there is a command you can issue to see what filesystems the kernel supports. in 4.2 some kernels did support NFS.
roustabout said:
I'm using smb shares coming off a synology in xbmc without any problem, but haven't tried it at the ftv OS level.
I forget the command but there is a command you can issue to see what filesystems the kernel supports. in 4.2 some kernels did support NFS.
Click to expand...
Click to collapse
Looks like it's the /proc/filesystems file. It appears that the fire tv supports nfs, and apparently fuse as well:
Code:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev nfs
nodev nfs4
nodev cifs
fuseblk
nodev fuse
nodev fusectl
nodev oprofilefs
Looks like I'll go back to trying to get nfs to work. Since I didn't see an nfs module I assumed it wasn't supported, guess it's built into the kernel
Hi
Any update on this?
I have my FTV rooted and updated to the latest pre-rooted firmware available, I've installed MountMangaer (licensed) and mounted my SMB share and while it doesn't throw out any errors, when I access the folder (sdcard/cifs/) it appears empty, and it's the same with 2 differente file explorers (Es FileExplorer and Atom File Explorer).
The reson I need the SMB share is to load the STRM files from 1Channel in XBMC directly to my NAS to make them available to all devices using the MySQL Library... Should I use NFS instead of SMB?? I don't have NFS setup on my NAS but I suppose I could configure it if it will make mountign easier on my FTV...
Any info would be much apreciated..
Related
many of you, including me, may find that it's time consuming to rebuild the kernel even for minor changes to init.rc, or to modify the init itself. with this small tip, you can change the init process on boot time and perhaps to perform different init processes easily.
reminded and inspired by sztupy's work, i change the whole init for easy customization and be able to let the init to process in a more dynamic way (for the term 'dynamic', it's borrowed from the internet - dynamic and static internet web pages)
let's start
the original file structure on the root looks like this (extracted):
init.rc
init
where init will be processed on boot time, and init.rc will be read to create dir/mount and services, etc
with dynamic init, the root will look like (sample):
init --> myinit.sh
init.original
myinit.sh
the original init is moved/renamed to init.original, with a symlink created named init pointing to a shell script or program, in this case, myinit.sh. a sample myinit.sh looks like this (u need to have a busybox resides on /sbin in this case):
#!/sbin/busybox sh
mount -t ext2 -o rw,noatime,nodiratime /dev/block/stl9 /system
mount -t rfs -o rw,noatime,nodiratime /dev/block/stl9 /system
/system/scripts/init/myinit2.sh
exec /init.original
###end###
in this example, the /system will be mounted, by attempt to mout it as ext2 first (it wont mount if /system is not in ext2), followed by mounting it as rfs. note that only one mount command line will be succeessfully performed here (PS -o remount is needed for remounting the system, so no need to worry the system will be mounted as ext2 first, and then mounted again as rfs).
i also added a file called myinit2.sh under /system/scripts/init/ (you can choose other dir but make sure u've mounted it), which contains some commmands you want to perform like a while loop, etc (becareful, if a infinite loop is used in myinit2.sh, append a "&" at the end to run it in background, so it will look like:
/system/scripts/init/myinit2.sh &
and finally, call init.original (if you wish)
the reason i call it dynamic is, the original init can be replaced or generated base on certain criteria in myinit.sh or myinit2.sh. below is an example which the original init is completely replaced in myinit2.sh:
#!/sbin/busybox sh
mount -o remount,rw rootfs /
rm /init.rc
rm /init.original
ln -s /system/scripts/init/myinit.rc /init.rc
ln -s /system/scripts/init/myinit /init.original
### end
since root is mounted as rw, the original init and init.rc can be removed and link to your own init and init.rc
that's it! you can now modify init and init.rc without the need to recmpile the kernel again
some possible usages:
- add/remove/modify services contained in init.rc
- change the filesystem for specific mount point in init.rc like switching from rfs to ext2 or jfs
- remove repeating dir creations in init.rc, and much more..
hope this help!
PS do it at ur own risk
Have you tried this? I don't think it's going to work without 'mknod' before doing the mounts.
RyanZA said:
Have you tried this? I don't think it's going to work without 'mknod' before doing the mounts.
Click to expand...
Click to collapse
Yes.
I don need mknod
Hey everyone.
I'm hoping I haven't screwed the pooch on this one. I'm still used to my samsung moment where I could log in, remount /system as RW and delete apk's. I tried following this method with my Evo4g, but when I try to remount the filesystem as RO after performing the deletions its not letting me. Its saying that the resource is busy.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
mount: Device or resource busy
Click to expand...
Click to collapse
I know with the moment if you didn't remount back to RO afterwards you'd get stuck in a boot loop. Does the same apply here? Any help/assurances would be appreciated.
My firetv is rooted and has busybox and terminal emulator loaded.
I want to mount a cifs share from my nas.
1. The following does not work and fails with "invalid argument" error:
mount -t cifs username=<username>,password=<password> //192.168.0.1/<sharename> /mnt/obb/<foldername>
2. However, the following works, mounts and I can see the folder contents inside the terminal emulator:
mount -t cifs unc=\\\\192.168.0.1\\<sharename>,username=<username>,password=<password> none /mnt/obb/<foldername>
But, I cannot see the shared folder contents outside the terminal emulator - i.e., say in ES file explorer or in xbmc.
Can someone help me how to fix this - i.e., how to do a proper mount. Thanks.
ps. the first mount given above works great in linux. thanks.
EDIT on Nov 25 2014: Now I am on rbox custom rom 51.1.4.1 and the above same command works like a charm via adb. No idea how though. Now, my xbmc can use the mounted folder and play videos flawlessly.
Hello,
I want to mount a shared Folder of my Fritzbox.
I'm searching for a while now, I found out i need the cifs.ko module but all i can find is for other devices, isn't there a way for the M8 despite a custom kernel?
As far as is remember i managed it with my One S with something like "busyboy mount -t cifs //Ip.ip.ip.ip/sharename /mnt/name -o user=xxx,password=www" But all i get is "failed: No such device"
ElementalX supports CIFS: http://goo.gl/jFKhfy
You can use ES file Explorer (without cifs module) to enter the drive of your Fritzbox, if it's a smb mount in your network
Hi. I have a rooted aftv 1 running 5.2.1.1 with busybox installed.
I try to mount my nas via nfs.
I open up a terminal via adbFire,
#su
#mkdir /mnt/obb/nas300
#busybox mount -t nfs -o nolock,ro 192.168.0.300:/mnt/Share /mnt/obb/nas300
That will mount my share to nas300 where I can access it as root.
But how can I access that share, that directory as a normal user? (I want to access it from within retroarch)
Because when I #exit the superuser, and look into /mnt/obb/nas300, it's empty.
Also #mount doesn't show the share anymore.
As soon as I become #su again, the nas is still mounted and the share is still there.
Please help, I'm too stupid, it's killing me.
Do I have to set another mount point on the aftv? Chose a more convenient folder? Give the folder other rights?
I actually have the exact same question.
Did you ever find a solution?
Thanks!