Wednesday, August 7, 2013
Fast apt-get with apt-fast
Ever experience slow download even with 10Mbps++ internet? The author has written a very useful article to share how to speed everything up with apt-fast:
[Linux] file_mode, dir_mode or permission not working correctly in Samba Share or Mount folder
Users permission in Linux is really complicated, for samba share, you need to take care:
- the folder permission of the parents folder where your samba share is located (at server side)
- the folder permission of the parents folder where your fstab mounted folder is located
- the create mask and directory mask in /etc/samba/smb.conf on your server
- the file_mode, directory_mode, noperm, rw and credentials in your /etc/fstab on client PC
General rules are parent folders permission will always overwrite the smb.conf & fstab.
When do I need to check the parents folder permission?
- If you have set everything in both files and still cannot get the correct permission for new created file/directory in your samba shares. Check client PCs mount folder's parent's permission
- If client PCs has problem access the samba shares, even with the correct username & password entered. Check server samba share parent's folder permission
- When you need valid users = xxx, xxx to give access to client PCs. Check server samba share parent's folder permission
I have set the samba/fstab/parent folder permission, but I still don't have write permission?
- you need to add uid=***your current user name*** at the fstab mount option.
Known Issue
- When creating file/directory in the mount folder (using Ubuntu 12.10), it does not honor the create mask & directory mask set by the server's smb.conf. I'm still looking for a solution... appreciate if anyone can help.
Saturday, August 3, 2013
[Ubuntu] Can access samba network share by IP but not Netbios name from Windows
After whole long day of troubleshooting why we cannot resolve samba shared folders using the NetBIOS Name defined in smb.conf.. finally I have figured out the root of the problem:
From Windows 7 / OSX we can access the samba shares using \\10.0.0.2\share, as well as \\server1.local\share (the .local is a result of running avahi-daemon). We can also ping 10.0.0.2 or server1 or server1.local, but we simply cannot access with \\server1\share
By changing the Hostname in /etc/hosts & /etc/hostname to any name other than "server1", or change the NetBIOS name in smb.conf to any other name, we can now get it work.
This is rather weird for a Windows user like me, where only hostname need to be set and we can access directly from other PC in the network without bothering what is NetBIOS. Linux is indeed too tricky!
Anyway, kind of fun when able to figure out what's wrong. It makes me love and hate Linux at the same moment!
Hostname CANNOT equal to NetBIOS name!!!A bit of background...
- our server hostname is server1
- our NetBIOS name is server1 (defined in smb.conf)
- IP-address is 10.0.0.2
From Windows 7 / OSX we can access the samba shares using \\10.0.0.2\share, as well as \\server1.local\share (the .local is a result of running avahi-daemon). We can also ping 10.0.0.2 or server1 or server1.local, but we simply cannot access with \\server1\share
By changing the Hostname in /etc/hosts & /etc/hostname to any name other than "server1", or change the NetBIOS name in smb.conf to any other name, we can now get it work.
This is rather weird for a Windows user like me, where only hostname need to be set and we can access directly from other PC in the network without bothering what is NetBIOS. Linux is indeed too tricky!
Anyway, kind of fun when able to figure out what's wrong. It makes me love and hate Linux at the same moment!
[Ubuntu] Can ping internet IP address but cannot resolve web address
If you got error when trying to ping any web address e.g. www.google.com, but can ping its IP address, there could be something wrong with the resolv.conf.
Despite you could have set the dns-nameservers in /etc/network/interfaces, the resolv.conf may not be updated yet. And if you have some running process and could not do ifdown / ifup, you can do nano /etc/resolv.conf, comment the original nameserver 127.0.0.1 to nameserver 8.8.8.8 (or the DNS provided by your ISP).
Ubuntu should now resolve the web address correctly!
Despite you could have set the dns-nameservers in /etc/network/interfaces, the resolv.conf may not be updated yet. And if you have some running process and could not do ifdown / ifup, you can do nano /etc/resolv.conf, comment the original nameserver 127.0.0.1 to nameserver 8.8.8.8 (or the DNS provided by your ISP).
Ubuntu should now resolve the web address correctly!
Subscribe to:
Posts (Atom)