How To Get A Job As A Waitress At A Strip Club

How to disable AAAA queries for IPv6 / configure your resolver

I have just stumbled again over some small things that just are angry.

A couple of really small bugs, but still infinitely annoying!

Gnome binds Samba shares (ie Windows shares) within the virtual file system

~ /. gvfs

inside the homes of the user. So far so good.

First Act: Access!

One could assume that Gnome will also allow transparent access to it. When I launch a terminal, I can go to the directory and write with normal command line tools on the shares. All great.

But in Gnome dive these shares in the ordinary file-not open to dialogue. Accordingly, even in Firefox, Galeon, Epiphany. How should now save an end user to easily download to the Share? Maybe I also see what, but something is just plain annoying. Not only because the under Windows works without problems.

Navigates to manually folds ~ /. Gvfs / it but ...

Act II: Links

Who knows it from Windows, it tried under Linux. Has been found after a lot of seeking the right to release the correct server, pull the release from the Network Neighborhood icon on the desktop and now has a link to the share that will be restored when double.

not the case with our favorite Frick same drive system with Gnome. First, it complains that the share is not a normal folder. Oh! Then it creates an empty folder on the desktop with the name of the share. Great! How then should an end user now have the idea that everything that he saved in that folder does not just end up on the server?

Well, we try right-clicking the share name in the network environment to create, then Shortcut. Ooops. I'm at the top level of the server so no write rights, so error dialog, link can not be created. Unfortunately, there is also no way as with Windows (sic) the links instead directly and automatically create on the desktop leave. Ergo: links you created manually by smb a starter with the aim nautilus: / / server port / . How should

for an end user ....

If a lot Fortunately, this is also mostly. But how many times I have Windows Server only blank entries or get weird dbus error messages, can not browse the network, etc. Yes, iptables is empty and on ACCEPT.

Third Act: From a shell, everything is better?

No, not really. The Gnomefs example, function

fchmod

is not implemented. And that leads to unnecessary errors.

situation: The Share is a file that we want to compress.

So command line

cd ~ / .gvfs sharename /; bzip2 file

- and we get a nice IO Error carved around the ears. Previously, bzip2 has the File compressed by the way properly. Complete. And once again written share. Then deleted.

The same experiment with gzip: It is also thrown an error, but the file is stored properly and deleted the source. What behavior is better? gzip, which is not the rights and does not care, or bzip2, the file over the network takes time, compressed, and writes back end and then delete?

What surprises me most, however: why is the

fchmod Only after writing the user data done? The really cool thing: The fashion, the want to pass bzip2 here differs not a fashion that the file has been so when it is created -.-

Conclusion: All except stupid mom!