Simply download nfs.app.bin, place it on a harddrive/flashdisk & boot your WDTV with the device connected.

In the next version of this app.bin I will include the binaries & libs necessary to enable exporting of NFS shares…which will allow you then to mount one WDTV on another

Exporting of NFS shares is now possible!!! It is disabled by default, since not everyone needs it, but if you do:

# config_tool -c NFSD='ON'

Enables the NFS server. After that you’ll need an exports file located either in /conf (for persistence) or along with nfs.app.bin on the root of an attached device. Heres the contents of a sample exports file:

/tmp/media/usb/USB1/49CE-E55E 192.168.0.100(rw,async)

What this means is I’m exporting /tmp/media/usb/USB1/49CE-E55E to 192.168.0.100 as a asynchronous writeable share.

To find more about exports, google nfs exports or check here or here.

Note: you cannot export /tmp/media/usb directly, you must export device paths seperately.

** nfs.app.bin-0.3 **

Simply download pure-ftpd.app.bin, place it on a harddrive/flashdisk & boot your WDTV with the device connected.

** pure-ftpd.app.bin-0.1 **

Simply unzip wirelesmod-wdlxtv.app.bin.zip, then place wirelessmod-wdlxtv.app.bin onto a harddrive/flashdisk & boot your WDTV with the device connected.

Wireless connectivity is not exactly plug & play with this pack, you’re required to do most of the config yourself. I have been unable to get a compatible wireless adapter locally, so I am of little help configuring this pack. Luckily theres this tutorial and this forum topic, where you can read and ask questions. When I eventually get a compatible adapter I’ll be sure to update this page and perhaps make the app.bin pack a bit more plug&play. If there are any issues with this pack, report them to me (and send me any fixes/mods) and I’ll get them taken care of.

Anyone want to buy me an adapter?

** wirelessmod-wdlxtv.app.bin-0.2 **

Thanks to Pibos for assembling all the libraries, modules, and binaries required to get this nice bit of functionality.

Simply place screen-dump.app.bin onto a harddrive/flashdisk & boot your WDTV with the device connected.

To use:

# screendump <filename.png>

Your screen grab will be saved to the current directory so make sure that you are in a writeable location.

Limitations:

• The system will become unstable if you remove the device containing the app.bin while the wdtv is on.

• Only the OSD overlays show up in the screen grabs and not the video.

** screen-dump.app.bin 0.1 **

This app.bin pack provides the drivers necessary to access Ximeta’s proprietary NDAS device[s]. A configuration file is provided to handle automagic mounting at boot. Much thanks to Sarantos (sda_gr) for sponsoring this addition and helping out with the debugging (half way around the planet)

Simply unzip ndas.app.bin.zip, then place ndas.app.bin and ndas.config onto a harddrive/flashdisk & boot your WDTV with the device connected. You will now have any NDAS devices which are listed in ndas.config mounted and available to you. The pack is currently based on the 1-1.15 driver.

Configuration:

# YOU MAY COPY THIS FILE TO /conf FOR PERSISTENT SETTINGS
# IF YOU DO THIS THEN YOU MAY DELETE ndas.conf
# FROM THE DEVICE CONTAINING ndas.app.bin
#
# IF THERE IS AN ndas.conf LOCATED ON THE DEVICE WITH ndas.app.bin
# IT WILL BE USED *INSTEAD* OF THE VERSION IN /conf
#
#
# format is as follows
# NDASX=,
#
# X = 0 - 7
#
# modes are:
# r - read-only
# w - read/write
# s - GFS
#
# for example
#
#NDAS0=SXTTS-1ME1U-ML5FA-R45VA-6V6Q2,w
#
#NDAS1=FIBL2-F9BK1-KL1KS-G0K2F-FIHK2,R
#
# this would initialize two NDAS's
# one in write mode the other read-only
#


Note the above ndas.config file. You may list up to 8 NDAS devices in this file. They are named like such: NDAS0, NDAS1, …, NDAS7. Also note that the write mode is mandatory for each NDAS device listed.

For persistent settings you may copy ndas.config to /conf and delete it from the device containing the app.bin.

Limitations:

• The system will become unstable if you remove the device containing the app.bin while the wdtv is on.

** ndas.app.bin 0.3.1 **

Remember CIFS is much slower than NFS, so if you can get NFS working that is the preferred way to go. NFS will stream 1080p, whereas CIFS cannot.

Simply unzip samba.app.bin.zip, then place samba.app.bin onto a harddrive/flashdisk & boot your WDTV with the device connected.

You will now have an SAMBA server running and can mount your WDTV from any windows machine. You can also now mount your windows shares.

In order to have WDLXTV mount your windows shares at boot you must include a line similar to below inside of your net.mounts file.

xmount //ip/shareName label cifs user=XXX,password=YYY

Change ip to the ip of your windows machine.
Change shareName to the name of your windows share.
Change label to what you’d like the windows share to be mounted as.
Change XXX to your windows username.
Change YYY to your windows password.

Note: If the default smb.conf I provided is not what you desire you may supply your own, by placing it on the root of the drive with samba.app.bin. You may also save your custom smb.conf to /conf for persistent SAMBA settings

Limitations:

• You must use WDLXTV-0.3+

• The system will become unstable if you remove the device containing the app.bin while the wdtv is on.

Note:

• Zoranders ext3-boot already contains this functionality, this is for WDLXTV.

Changelog:

0.2
* added dfree script to return available disk space.

** samba.app.bin 0.2 **

Simply unzip dropbear-ssh.app.bin.zip, then place dropbear-ssh.app.bin onto a harddrive/flashdisk & boot your WDTV with the device connected.

You will now have an SSH server running and can use it instead of telnet. Any standard client will do: putty, xterm, etc. The application will be mounted in /apps/dropbear-ssh.

NOTE: before you can remotely log into your WDTV via ssh you will have to set a root password. This is done like so:

$ telnet wdtv-01
Trying 192.168.0.109...
Connected to 192.168.0.109.
Escape character is '^]'.
wdtv-01 login: root
Password:

BusyBox v1.10.0 (2009-02-15 05:09:42 CST) built-in shell (msh)
Enter 'help' for a list of built-in commands.

# passwd
Changing password for root
New password:
Retype password:
Password for root changed by root
#

If you are told:

passwd: cannot update password file /etc/shadow

then you need to upgrade to WDLXTV-0.2, I spaced and forgot to do something important in 0.1 : S

Limitations:

• You must use WDLXTV-0.2 (rectifies password issue)

• Passwordless login is disabled (for you own good)
• The system will become unstable if you remove the device containing the app.bin.

Note:

• Zoranders ext3-boot already contains this functionality, this is for WDLXTV.

** dropbear-ssh.app.bin 0.1**

Limitations:

• The system will become unstable if you remove the device containing the app.bin.

Note:

• Zoranders ext3-boot already contains this functionality, this is for WDLXTV.

** nls-codepages.app.bin-0.1 **

Simply download core-extras.app.bin, then place it on a harddrive/flashdisk & boot your WDTV with the device connected.

The only additional functionality this adds really is XFS and ReiserFS partition mounting, with hotplugging. HFS/HFS+ users should download and use this, as it includes a binary relating to the HFS. The other included binaries will help advanced users, with such actions as filesystem formatting and tuning.

Limitations:

• core-extras.app.bin cannot be on an XFS/ReiserFS drive at boot, this is chicken&egg.

• The system will become unstable if you remove the device containing the app.bin.

Note:

• Zoranders ext3-boot already contains this functionality, this is for WDLXTV.

** core-extras.app.bin 0.2**

]]>