Author Archives: kalle

Mail reception failed after ports update

Posted on by
Reply

It turned out to be due to that Perl got updated and by default perl disables SUIDPERL. I tried several things to activate it like configuring /etc/make.conf but it didn’t help.

This is how I solved it:

make config

And chech SUIDPERL and then make

make showconfig

to make sure it is set.

To build and reinstall do:

make deinstall

make reinstall

Turned out the above even didn’t help, though found this which finally solved it. Not so easy when there is a bug in the code!!

It’s been reported officially too.

Problems upgrading Cairo…

Posted on by
Reply

I tried to make a ports upgrade but missed to read UPDATING so did a full upgrade without doing some pre-requisites which led to a lot of problems…. one odd thing was that the cairo package didn’t recognize I had X installed… the configuration said no x. but then I did:
cd work/cairo-1.6.4/
./configure –enable-xlib=yes –enable-xlib_xrender=yes
make
cd ../..
make install

and now it seems to be alright…. don’t get it.

Problems installing GTK20

Posted on by
1

When doing a port upgrade several X-based ports failed. After some struggling I found out the reason, the graphics/cairo port didnt default to include X11 libraries as it should. Strange….

I solved it by starting a make for Cairo and interupt it.
cd work/cairo-1.2.60
./configure—enable-xlib
cd ../..
make
make deinstall
make reinstall

ÅÄÖ all over

Posted on by
Reply

I have never really got ÅÄÖ to work properly on my system before. I got it working in samba but when doing ls at a tcsh prompt the files were full of questionsmarks. So started to search and read what to do. First I found that one could in newer versions of samba set different character codings for dos and unix. But still in my shell things looked weird. After a bit of more searches I found that there is a .login_conf to set these things. So by setting the charset to iso-8859-1 it all worked.

.login_conf

me:
        :charset=iso-8859-1:
        :lang=sv_SE.ISO8859-1:

smb.conf
# Charset settings
display charset = iso-8859-1
unix charset = iso-8859-1
dos charset = utf-8

Continued problems with mount_smbfs

Posted on by
Reply

So mounted some samba directories and seemed to work fine. One of these was the root for a virtual host on my apache server and I got some really wierd problems. The HTML code seemed to load fine but not images and css….

Apparently: “When trying to serve a directory mounted with mount_smbfs on FreeBSD with the Apache 2.0.x server, large files (over 100K or so) won’t transfer correctly. To fix this problem use the EnableSendfile off directive within your Global, Directory or VirtualHost config.” So adding that directive solved everything.

Found that at unixtips.org – the source for unix tips.

Using fstab to automatically mount samba drives

Posted on by
2

It is possible to specify mount_smbfs-mounts in /etc/fstab. For instance it can be used to automatically mount Samba drives automatically at boot up. When I configured this I ran into a number of small problems. To not be needed to enter a password each time one can use /etc/nsmb.conf. Though I could not really get it to work, every time I got queried about the password even if I had given it in nsmb.conf. I tried both with unencrypted and crypted password. Nothing worked. By coincidense I tired to change the user name to only capital letters, and that solved it!

So in you nsmb.conf it should look like this:
[YELLOWORB:JOHN]
password=$$342342425435453

PS. Still have the noauto option and a mount script eventhough I have read it should work without noauto, though I had problems with it before and also it makes your system very dependent on the other machine with the samba drives. If that is not up and running if when you FreeBSD machine boots, the mounting will fail and the boot process will halt and your system will not go up.

Update 2007-05-24:
Yesterday I discovered after a reboot that my shares from a Windows machine wasnt mounted any more. I tried to use mount_smbfs manually but failed. It reported:
mount_smbfs: can't get server address: syserr = Permission denied

I spent quite some time searching for a solution and finally after posting on a mailinglist I figured it out. I’t nothing to do wiht permissions, Samba cannot locate the server, thats the problem! So if you specify its real address and not only WINS name it works:
mount_smbfs -I 192.168.0.2 //joe@FILESERVER/share /mnt

But how to solve it for fstab?
Again comes nsmb.conf into play. Under the each server section in nsmb.conf one parameter you can give is the address to the machine. Either the ip number or its realy networkname works, e.g. fileserver.mynetwork.com.