I'm posting my experiences with this device, which I've recently bought for home, because at some stage we may consider one of the Synology devices as the successor to Rutabaga. Also the blog now substitutes almost entirely for my memory, so if I don't post this stuff here, I'll never remember what I did.
My drive was uninitialized, so the first thing to do was to create a volume. In this case, because I have only one drive, the only kind of volume I could create was a "Basic volume"; if you have more drives, you can create JBOD or RAID volumes of many kinds. My plan is to keep all my drives as separate volumes, and have them backing up to each other, so that I have lots of copies of data on standalone drives that I can pull out of the DS and mount elsewhere if necessary.
It takes a long time to create a volume; it formats the drive (ext3) completely, rather than using a "quick format", and presumably checks every sector. It then mounts the volume as "volume1".
While that was going on, I turned on SSH, and logged in from the terminal. Only the admin user can log in as SSH; my guess is that "users" (see below) are not real users on the BusyBox system it's running. I was able to determine that it's running BusyBox, and that the Ash shell you get is pretty limited in what it can do.
A new version of the firmware had been released since the CD I got with the device, so I downloaded it (a .pat file), and installed it through the web interface. Worked a treat. I got a couple of new features with it.
There's a web-based interface for file management called FileStation, which is handy if you need to upload a couple of files quickly, or look through the directories, but mainly I'll be mounting drives and using robocopy and rsync to back things up.
sudo apt-get install portmap nfs-common).
sudo mount 192.168.xxx.xxx/volume1/mholmes /home/mholmes/DiskStation/mholmes
\\DiskStation\volume1\whatever, in Windows explorer, and it prompts you for a login. It needed
DiskStation\[username]rather than just [username].
Lots more stuff to learn -- I have to set up the scheduled shutdown and startup (a wonderful feature), figure out which of the built-in apps I might want to use, and figure out how I can make it back up between its own drives (for which I need another drive, of course).
We have long struggled with the issue of how to provide easy access to data on the TAPoR servers for students and researchers working on projects. The ideal, especially for XML markup projects, is to have a TAPoR share mounted as a network drive; this enables oXygen to provide an easy project editing interface through "Link to external folders", and files can be opened and saved transparently on the server in this way. On Linux this is (naturally) easy. This is what I have learned from trying to do this for CC on her Mac and Windows laptops over the last two days:
All in all, very unsatisfactory. This precludes people working remotely on our project data unless they're relatively sophisticated and can use something like subversion, can be relied upon to use a client such as WinSCP or Cyberduck correctly, or are using Linux.
There are a couple of CANJAS lectures scheduled while I'm gone, and Dr. Iles will be handling the hardware. He asked me to write up a brief outline of what to do:
In the boardroom, the optimal location is at the window end of the room; the curtains are not sufficient to stop glare on the screen.
I generally need to get in to the room a bit ahead of schedule to move the table and chairs around to fit the VC equipment in to the space.
The boardroom is already sorted out, network wise, and should just work. That said, the network port is at the opposite end of the room from the best location for the VC equipment. There is a long network cable for this (the end of which is sticking out of a blue-grommeted hole in the bottom left side of the cart). I run it under the tables to keep it out of the way.
*** Networking note: If another node is dialing (cascade call from UofA or similar) in you'll need to know your IP address beforehand and give it to the dialer. If you dial out (make your own call to another node) your IP doesn't matter.
in the boardroom, you should be able to get away with a single microphone, but if you have a full house you might want to use two. I run the cable (sticking out of the same hole as the network cable) down the middle of the table (on the floor, running it up to the mic's location). Remember that the mic displays a green light when broadcasting and a red one when turned off. They can be manually turned on and off with the switch on each mic, or through the remote mute function.
*** Audio note: the mic cables plug in to the mic only one way. It's a bit like an S-Video cable in that it requires a delicate touch to attach. Take a close look at the cable end and the mic before trying to connect them.
The VC equipment is plugged in to the S-Video plug on the TV (which displays as "AV1" on the TV screen). Use the "Source" button on the TV remote to adjust the input.
The bigger VC box (on the right) has a power (toggle) switch that should already be on. When you plug in the cart and turn on the power on the VC remote (silver one) the camera should turn around a bit and settle in a forward position (away from the TV). If the TV is on the right input you should see a view of the room on the TV screen.
If the blue Sony IPELA screen is displaying on the TV, you'll notice in the lower middle section of the screen some info about the network connection. It should display an IP address here - if it doesn't, you don't have a connection. Fix this first!
To dial in to a node, use the IPELA remote and choose "Phone Book" in the top right of the main screen. When you click it, you get a new screen with about 6 big, cryptically titled, icons (Sony, Clare@UofA etc.). Look at the bottom left of the screen and you'll see the IP address that will get dialed if you choose one of the icons. (***Remember, if UofA is going to do a cascade call (dials you) you need to know your IP address and make sure the outside caller knows what it is.)
If you need a separate monitor for a Powerpoint presentation, you need to make sure that it's working ahead of time. I normally dial up UofA and ask to do a test to make sure everything is functional.
To connect things, put the small LCD monitor where you want it and connect the VGA extension cable to the one already on the monitor. The extension cable is already attached to the SONY box; you'll find the cable inside the cart.
This blog is the location for all work involving software and hardware maintenance, updates, installs, etc., both routine and urgent, in the server room, the labs and the R&D rooms.
|<< <||Current||> >>|