recentpopularlog in

kme : readynas   11

Bug 3002 – parameter "guest account" in smb.conf seems to be ignored. - https://bugzilla.samba.org/
NETGEAR has "map to guest = 'Bad User'" in \etc\frontview\samba\smb.conf.WfWg. The single quotes are unnecessary.
samba  netgear  readynas  networking  bug  sortofsolution 
july 2014 by kme
NETGEAR ReadyNAS • View topic - Share visible from Windows Explorer but not in Web GUI
The second way is to try manually editing Shares.conf. There is a command line editor in linux called vi, but it is not that easy to learn. A simpler option is to download notepad++ from http://notepad-plus-plus.org/download/v6.3.1.html and install it on your PC. Copy Shares.conf to one of your shares with ssh, then edit it with notepad++ from the PC. Then rename the existing Shares.conf, and copy the revised version back into /etc/frontview/samba/ After all that you'd need to restart.
almostsolution  readynas  cifs  smb  configfile 
january 2014 by kme
Tech, Life, and Triathlon...: NFS mount Ubuntu linux drive on Mac OS X Leopard
The 'map_static' mount option is an interesting solution, although the ReadyNAS may not support it (see: http://www.readynas.com/forum/viewtopic.php?f=23&t=33526)
Now we need to make a map of our user and group IDs we obtained in #1 and #2 above. This will ensure that when we NFS mount our drive on our Mac, the permissions and file ownership will all be set correctly. A common directory for this file is in /etc/nfs. If this directory doesn't exist for you, go ahead and create it.

Create a file in this directory called foo.map - it can be called anything, but the naming convention is to use the name of the accessing server, in this case the hostname of your Mac. Mine, creatively enough, has a hostname of mac so my file is called mac.map.

Here's what my file looks like:

# mapping for client: mac
# remote local
uid 501 1000
gid 20 1000

The first two lines are just comments. The second two map the uid and gid from steps 1 and 2 above. Here, remote means your Mac, and local means your Linux box.

NFS gets its export information (the directories that are allowed to be NFS mounted) from the file /etc/exports. If this file does not exist, just create it. Here's what my file looks like:

/home/doej mac(rw,insecure,map_static=/etc/nfs/mac.map)

The first argument is the directory on Linux that you want to be able to NFS mount. In this case, I've chosen to mount my home directory. The second parameter are the mount options. To see a full list of options, execute man exports. I've listed my Mac hostname as the server that is allowed to NFS mount this directory. The options I've chosen are:

rw - read/write
insecure - allow non-root user to NFS mount directory
map_static - the file we created above that maps our user and group IDs from Mac to Linux box. If you want to be able to write to your NFS mount, you MUST have this option set and set correctly.
mac  linux  nfs  filesharing  networking  tipsandtricks  readynas 
january 2014 by kme
man-db up and running on Maemo 5 - maemo.org - Talk
pager: applet not found

'less' was already installed on the ReadyNAS, but I had to set the 'PAGER' environment variable in ~/.bashrc. That did it.
readynas  debian  solution 
december 2013 by kme
NETGEAR ReadyNAS • View topic - Non-root user ssh access
I had to enable root ssh access and do a usermod command to set the accounts shell to a valid shell.
readynas  nas  sysadmin  ssh  solution 
august 2012 by kme

Copy this bookmark:





to read