Direkt zum Hauptbereich

Mounted my USB stick (sitting at the Fritz!Box) to my Raspi

1. Plug the USB stick into the Fritz!Box 7362 SL. It is ready to use then.

2. Create a user in your Fritz!Box with only the permission to use NAS content.

3. Add your NAS content folder to the permissions for your new user.
4. Create a directory on your Raspberry # sudo mkdir /mnt/usb
5. Add an entry to your /etc/fstab # sudo vi /etc/fstab
//192.168.178.1/fritz.nas/SanDisk-CruzerBlade-01/FRITZ/mediabox /mnt/usb        cifs    defaults,username=piusb,password=***** 0       0

You'll have to use your plaintext password for your fstab. If you do not want to do this then use a credential file like credentials=/etc/samba/share.cred.

6. Reload your /etc/fstab # mount -a

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc)

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) pdadmin sec_master> user create dg1234 uid=dg1234,cn=team1,cn=users,o=company lala lala ********** Could not perform the administration request Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) Description: After the upgrade from Policy Director (policy server) V5.1 to V6.0 the errors above occured when trying to write to the registry. Solution: The task of updating the ldap schema did not work well for some reason. After doing it again the errors did not occur again: # ivrgy_tool -d -h ldap_host -p port -D ldap_admin -w pwd schema
Kommentar veröffentlichen
Mehr anzeigen

WebSphere Application Server LDAP: The administrative user ID does not exist in the user repository.

When you try to enable global security with ldap authentication you get the following error when configuring your ldap repository (IBM Directory Server): The administrative user ID does not exist in the user repository. Reason: The bind user must be searchable. This means that an ldapsearch with this user as bind user must return his own entry. If this does not work, you have to add an aclEntry: vi change-was7101-aclentry.ldif dn: uid=was7101,cn=mygroup,cn=admusr,o=mycomp aclentry: access-id:UID=WAS7101,CN=MYGROUP,CN=ADMUSR,O=MYCOMP:normal:rsc $ ldapmodify -h myhost -x -D "cn=root" -w ******* -f change-was7101-aclentry.ldif modifying entry "uid=was7101,cn=mygroup,cn=admusr,o=mycomp" Now user was7101 can do an ldapsearch to find itself and therefore you can use it to configure you LDAP repository. This article gave me the hint: http://www-01.ibm.com/support/docview.wss?rs=767&uid=swg21219253
1 Kommentar
Mehr anzeigen